From f66ac28dc09315e8a6db860905b736171045c54d Mon Sep 17 00:00:00 2001
From: Zied
Date: Wed, 25 Feb 2026 09:48:50 +0100
Subject: [PATCH 01/11] docs: detail auto-update via START_APP.bat
---
README.md | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/README.md b/README.md
index 55d765c3..90a72042 100644
--- a/README.md
+++ b/README.md
@@ -250,13 +250,9 @@ Install to the tool-specific path. Use installer flags: `--antigravity` (default
### Update an existing installation
-```bash
-# If you used the default installer (Antigravity global):
-git -C ~/.gemini/antigravity/skills pull
+**Good news!** You no longer need to manually run `git pull` or `npx antigravity-awesome-skills` to update your skills.
-# If you installed to a custom path (e.g. ~/.agent/skills):
-git -C ~/.agent/skills pull
-```
+Simply double-click **`START_APP.bat`** (or run it in your terminal). It will automatically fetch and merge the latest skills from the original repository every time you open the Web App, ensuring you always have the most up-to-date catalog!
### Reinstall from scratch
From 338420a92404d8b2660a7a8b101d479cd1f21d45 Mon Sep 17 00:00:00 2001
From: Zied
Date: Wed, 25 Feb 2026 10:05:30 +0100
Subject: [PATCH 02/11] feat: add interactive prompt builder to skill detail
page
---
web-app/src/pages/SkillDetail.jsx | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/web-app/src/pages/SkillDetail.jsx b/web-app/src/pages/SkillDetail.jsx
index 8f08eb77..4d7c99df 100644
--- a/web-app/src/pages/SkillDetail.jsx
+++ b/web-app/src/pages/SkillDetail.jsx
@@ -11,6 +11,7 @@ export function SkillDetail() {
const [loading, setLoading] = useState(true);
const [copied, setCopied] = useState(false);
const [error, setError] = useState(null);
+ const [customContext, setCustomContext] = useState('');
useEffect(() => {
// 1. Fetch index to get skill metadata and path
@@ -50,7 +51,12 @@ export function SkillDetail() {
}, [id]);
const copyToClipboard = () => {
- navigator.clipboard.writeText(`Use @${skill.name} ...`);
+ const basePrompt = `Use @${skill.name}`;
+ const finalPrompt = customContext.trim()
+ ? `${basePrompt}\n\nContext:\n${customContext}`
+ : basePrompt;
+
+ navigator.clipboard.writeText(finalPrompt);
setCopied(true);
setTimeout(() => setCopied(false), 2000);
};
@@ -111,6 +117,23 @@ export function SkillDetail() {
{copied ? 'Copied!' : 'Copy Prompt'}
+
+
+
+
+ Add specific details below (e.g. "Use React 19 and Tailwind"). The "Copy Prompt" button will automatically attach your context.
+
+
From 0fb8b52bcb2bea1292a3de78080f08513c13424a Mon Sep 17 00:00:00 2001
From: Zied
Date: Wed, 25 Feb 2026 10:14:44 +0100
Subject: [PATCH 03/11] Add a robust auto-update mechanism to the Web App
launcher and introduce the Interactive Prompt Builder.
---
START_APP.bat | 77 +-
web-app/public/skills.json | 4846 +++++++++--------
.../public/skills/3d-web-experience/SKILL.md | 6 +-
web-app/public/skills/ab-test-setup/SKILL.md | 7 +-
.../SKILL.md | 2 +
.../skills/active-directory-attacks/SKILL.md | 9 +-
.../skills/activecampaign-automation/SKILL.md | 5 +
.../skills/address-github-comments/SKILL.md | 7 +-
.../public/skills/agent-evaluation/SKILL.md | 6 +-
.../agent-framework-azure-ai-py/SKILL.md | 15 +-
.../skills/agent-manager-skill/SKILL.md | 4 +-
.../public/skills/agent-memory-mcp/SKILL.md | 7 +-
.../skills/agent-memory-systems/SKILL.md | 6 +-
.../SKILL.md | 2 +
.../SKILL.md | 2 +
.../public/skills/agent-tool-builder/SKILL.md | 6 +-
web-app/public/skills/agents-v2-py/SKILL.md | 11 +-
.../skills/ai-agent-development/SKILL.md | 174 +
.../skills/ai-agents-architect/SKILL.md | 6 +-
web-app/public/skills/ai-engineer/SKILL.md | 4 +-
web-app/public/skills/ai-ml/SKILL.md | 253 +
web-app/public/skills/ai-product/SKILL.md | 6 +-
.../public/skills/ai-wrapper-product/SKILL.md | 6 +-
.../skills/airflow-dag-patterns/SKILL.md | 4 +-
.../skills/airtable-automation/SKILL.md | 5 +
web-app/public/skills/algolia-search/SKILL.md | 4 +
.../public/skills/algorithmic-art/SKILL.md | 9 +-
.../skills/amplitude-automation/SKILL.md | 5 +
.../public/skills/analytics-tracking/SKILL.md | 7 +-
.../android-jetpack-compose-expert/SKILL.md | 152 +
.../skills/angular-best-practices/SKILL.md | 5 +-
.../public/skills/angular-migration/SKILL.md | 4 +-
.../skills/angular-state-management/SKILL.md | 2 +-
.../skills/angular-ui-patterns/SKILL.md | 5 +-
web-app/public/skills/angular/SKILL.md | 2 +-
.../skills/anti-reversing-techniques/SKILL.md | 4 +-
.../skills/api-design-principles/SKILL.md | 4 +-
.../api-documentation-generator/SKILL.md | 2 +
.../public/skills/api-documentation/SKILL.md | 164 +
web-app/public/skills/api-documenter/SKILL.md | 4 +-
.../skills/api-fuzzing-bug-bounty/SKILL.md | 9 +-
web-app/public/skills/api-patterns/SKILL.md | 7 +-
.../api-security-best-practices/SKILL.md | 2 +
.../skills/api-security-testing/SKILL.md | 172 +
.../SKILL.md | 2 +
web-app/public/skills/app-builder/SKILL.md | 7 +-
.../skills/app-builder/templates/SKILL.md | 7 +-
.../skills/app-store-optimization/SKILL.md | 7 +-
.../SKILL.md | 2 +
.../public/skills/architect-review/SKILL.md | 2 +
.../architecture-decision-records/SKILL.md | 12 +-
.../skills/architecture-patterns/SKILL.md | 4 +-
web-app/public/skills/architecture/SKILL.md | 7 +-
.../public/skills/arm-cortex-expert/SKILL.md | 4 +-
.../public/skills/asana-automation/SKILL.md | 5 +
.../skills/async-python-patterns/SKILL.md | 4 +-
.../skills/attack-tree-construction/SKILL.md | 4 +-
.../public/skills/audio-transcriber/SKILL.md | 1 +
.../auth-implementation-patterns/SKILL.md | 4 +-
.../public/skills/automate-whatsapp/SKILL.md | 20 +-
.../skills/autonomous-agent-patterns/SKILL.md | 4 +-
.../public/skills/autonomous-agents/SKILL.md | 6 +-
.../skills/avalonia-layout-zafiro/SKILL.md | 7 +-
.../avalonia-viewmodels-zafiro/SKILL.md | 7 +-
.../avalonia-zafiro-development/SKILL.md | 7 +-
.../public/skills/aws-cost-cleanup/SKILL.md | 309 ++
.../public/skills/aws-cost-optimizer/SKILL.md | 192 +
.../skills/aws-penetration-testing/SKILL.md | 9 +-
web-app/public/skills/aws-serverless/SKILL.md | 6 +-
web-app/public/skills/azd-deployment/SKILL.md | 13 +-
.../SKILL.md | 7 +-
.../azure-ai-agents-persistent-java/SKILL.md | 7 +-
.../azure-ai-anomalydetector-java/SKILL.md | 7 +-
.../azure-ai-contentsafety-java/SKILL.md | 7 +-
.../skills/azure-ai-contentsafety-py/SKILL.md | 7 +-
.../skills/azure-ai-contentsafety-ts/SKILL.md | 7 +-
.../azure-ai-contentunderstanding-py/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-ai-formrecognizer-java/SKILL.md | 7 +-
web-app/public/skills/azure-ai-ml-py/SKILL.md | 7 +-
.../skills/azure-ai-openai-dotnet/SKILL.md | 7 +-
.../skills/azure-ai-projects-dotnet/SKILL.md | 7 +-
.../skills/azure-ai-projects-java/SKILL.md | 7 +-
.../skills/azure-ai-projects-py/SKILL.md | 43 +-
.../skills/azure-ai-projects-ts/SKILL.md | 7 +-
.../skills/azure-ai-textanalytics-py/SKILL.md | 7 +-
.../skills/azure-ai-transcription-py/SKILL.md | 7 +-
.../azure-ai-translation-document-py/SKILL.md | 7 +-
.../azure-ai-translation-text-py/SKILL.md | 7 +-
.../skills/azure-ai-translation-ts/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-ai-vision-imageanalysis-py/SKILL.md | 7 +-
.../skills/azure-ai-voicelive-dotnet/SKILL.md | 7 +-
.../skills/azure-ai-voicelive-java/SKILL.md | 7 +-
.../skills/azure-ai-voicelive-py/SKILL.md | 13 +-
.../skills/azure-ai-voicelive-ts/SKILL.md | 7 +-
.../azure-appconfiguration-java/SKILL.md | 7 +-
.../skills/azure-appconfiguration-py/SKILL.md | 7 +-
.../skills/azure-appconfiguration-ts/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-communication-chat-java/SKILL.md | 7 +-
.../azure-communication-common-java/SKILL.md | 7 +-
.../azure-communication-sms-java/SKILL.md | 7 +-
.../skills/azure-compute-batch-java/SKILL.md | 7 +-
.../azure-containerregistry-py/SKILL.md | 7 +-
.../public/skills/azure-cosmos-db-py/SKILL.md | 29 +-
.../public/skills/azure-cosmos-java/SKILL.md | 7 +-
.../public/skills/azure-cosmos-py/SKILL.md | 13 +-
.../public/skills/azure-cosmos-rust/SKILL.md | 7 +-
.../public/skills/azure-cosmos-ts/SKILL.md | 7 +-
.../skills/azure-data-tables-java/SKILL.md | 7 +-
.../skills/azure-data-tables-py/SKILL.md | 7 +-
.../skills/azure-eventgrid-dotnet/SKILL.md | 7 +-
.../skills/azure-eventgrid-java/SKILL.md | 7 +-
.../public/skills/azure-eventgrid-py/SKILL.md | 7 +-
.../skills/azure-eventhub-dotnet/SKILL.md | 7 +-
.../skills/azure-eventhub-java/SKILL.md | 7 +-
.../public/skills/azure-eventhub-py/SKILL.md | 13 +-
.../skills/azure-eventhub-rust/SKILL.md | 7 +-
.../public/skills/azure-eventhub-ts/SKILL.md | 7 +-
.../public/skills/azure-functions/SKILL.md | 6 +-
.../skills/azure-identity-dotnet/SKILL.md | 7 +-
.../skills/azure-identity-java/SKILL.md | 7 +-
.../public/skills/azure-identity-py/SKILL.md | 7 +-
.../skills/azure-identity-rust/SKILL.md | 7 +-
.../public/skills/azure-identity-ts/SKILL.md | 7 +-
.../azure-keyvault-certificates-rust/SKILL.md | 7 +-
.../skills/azure-keyvault-keys-rust/SKILL.md | 7 +-
.../skills/azure-keyvault-keys-ts/SKILL.md | 7 +-
.../public/skills/azure-keyvault-py/SKILL.md | 7 +-
.../azure-keyvault-secrets-rust/SKILL.md | 7 +-
.../skills/azure-keyvault-secrets-ts/SKILL.md | 7 +-
.../skills/azure-maps-search-dotnet/SKILL.md | 7 +-
.../azure-messaging-webpubsub-java/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-mgmt-apicenter-dotnet/SKILL.md | 7 +-
.../skills/azure-mgmt-apicenter-py/SKILL.md | 7 +-
.../azure-mgmt-apimanagement-dotnet/SKILL.md | 15 +-
.../azure-mgmt-apimanagement-py/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-mgmt-botservice-dotnet/SKILL.md | 7 +-
.../skills/azure-mgmt-botservice-py/SKILL.md | 7 +-
.../skills/azure-mgmt-fabric-dotnet/SKILL.md | 7 +-
.../skills/azure-mgmt-fabric-py/SKILL.md | 7 +-
.../azure-mgmt-mongodbatlas-dotnet/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../azure-monitor-ingestion-java/SKILL.md | 9 +-
.../azure-monitor-ingestion-py/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 4 +-
.../azure-monitor-opentelemetry-py/SKILL.md | 7 +-
.../azure-monitor-opentelemetry-ts/SKILL.md | 7 +-
.../skills/azure-monitor-query-java/SKILL.md | 7 +-
.../skills/azure-monitor-query-py/SKILL.md | 7 +-
.../public/skills/azure-postgres-ts/SKILL.md | 7 +-
.../SKILL.md | 13 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 13 +-
.../azure-search-documents-dotnet/SKILL.md | 15 +-
.../skills/azure-search-documents-py/SKILL.md | 15 +-
.../skills/azure-search-documents-ts/SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../SKILL.md | 7 +-
.../skills/azure-servicebus-dotnet/SKILL.md | 7 +-
.../skills/azure-servicebus-py/SKILL.md | 13 +-
.../skills/azure-servicebus-ts/SKILL.md | 11 +-
.../azure-speech-to-text-rest-py/SKILL.md | 9 +-
.../skills/azure-storage-blob-java/SKILL.md | 7 +-
.../skills/azure-storage-blob-py/SKILL.md | 7 +-
.../skills/azure-storage-blob-rust/SKILL.md | 7 +-
.../skills/azure-storage-blob-ts/SKILL.md | 7 +-
.../azure-storage-file-datalake-py/SKILL.md | 7 +-
.../azure-storage-file-share-py/SKILL.md | 7 +-
.../azure-storage-file-share-ts/SKILL.md | 7 +-
.../skills/azure-storage-queue-py/SKILL.md | 7 +-
.../skills/azure-storage-queue-ts/SKILL.md | 7 +-
.../skills/azure-web-pubsub-ts/SKILL.md | 7 +-
.../public/skills/backend-architect/SKILL.md | 4 +-
.../skills/backend-dev-guidelines/SKILL.md | 7 +-
.../resources/architecture-overview.md | 2 +-
.../resources/async-and-errors.md | 2 +-
.../resources/complete-examples.md | 2 +-
.../resources/configuration.md | 2 +-
.../resources/database-patterns.md | 2 +-
.../resources/middleware-guide.md | 2 +-
.../resources/routing-and-controllers.md | 2 +-
.../resources/sentry-and-monitoring.md | 2 +-
.../resources/services-and-repositories.md | 2 +-
.../resources/testing-guide.md | 2 +-
.../resources/validation-patterns.md | 2 +-
.../SKILL.md | 2 +
.../skills/backend-security-coder/SKILL.md | 4 +-
.../skills/backtesting-frameworks/SKILL.md | 4 +-
.../skills/bamboohr-automation/SKILL.md | 5 +
.../skills/basecamp-automation/SKILL.md | 5 +
.../skills/bash-defensive-patterns/SKILL.md | 4 +-
web-app/public/skills/bash-linux/SKILL.md | 7 +-
web-app/public/skills/bash-pro/SKILL.md | 4 +-
web-app/public/skills/bash-scripting/SKILL.md | 197 +
.../skills/bats-testing-patterns/SKILL.md | 4 +-
.../skills/bazel-build-optimization/SKILL.md | 4 +-
.../public/skills/behavioral-modes/SKILL.md | 7 +-
.../public/skills/bevy-ecs-expert/SKILL.md | 133 +
.../public/skills/billing-automation/SKILL.md | 4 +-
.../skills/binary-analysis-patterns/SKILL.md | 4 +-
.../skills/bitbucket-automation/SKILL.md | 5 +
.../skills/blockchain-developer/SKILL.md | 4 +-
web-app/public/skills/blockrun/SKILL.md | 4 +-
web-app/public/skills/box-automation/SKILL.md | 7 +-
web-app/public/skills/brainstorming/SKILL.md | 11 +-
.../brand-guidelines-anthropic/SKILL.md | 9 +-
.../brand-guidelines-community/SKILL.md | 9 +-
.../public/skills/brevo-automation/SKILL.md | 7 +-
.../skills/broken-authentication/SKILL.md | 9 +-
.../public/skills/browser-automation/SKILL.md | 6 +-
.../skills/browser-extension-builder/SKILL.md | 6 +-
.../public/skills/bullmq-specialist/SKILL.md | 4 +
.../public/skills/bun-development/SKILL.md | 4 +-
.../public/skills/burp-suite-testing/SKILL.md | 9 +-
.../public/skills/business-analyst/SKILL.md | 4 +-
.../public/skills/busybox-on-windows/SKILL.md | 7 +-
web-app/public/skills/c-pro/SKILL.md | 2 +
.../c4-architecture-c4-architecture/SKILL.md | 2 +
web-app/public/skills/c4-code/SKILL.md | 4 +-
web-app/public/skills/c4-component/SKILL.md | 12 +-
web-app/public/skills/c4-container/SKILL.md | 6 +-
web-app/public/skills/c4-context/SKILL.md | 8 +-
.../public/skills/cal-com-automation/SKILL.md | 5 +
.../skills/calendly-automation/SKILL.md | 5 +
.../public/skills/canva-automation/SKILL.md | 5 +
web-app/public/skills/canvas-design/SKILL.md | 9 +-
.../skills/cc-skill-backend-patterns/SKILL.md | 11 +-
.../skills/cc-skill-clickhouse-io/SKILL.md | 11 +-
.../skills/cc-skill-coding-standards/SKILL.md | 11 +-
.../cc-skill-continuous-learning/SKILL.md | 7 +-
.../cc-skill-frontend-patterns/SKILL.md | 11 +-
.../SKILL.md | 4 +-
.../skills/cc-skill-security-review/SKILL.md | 11 +-
.../cc-skill-strategic-compact/SKILL.md | 7 +-
web-app/public/skills/cdk-patterns/SKILL.md | 79 +
.../skills/changelog-automation/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../skills/circleci-automation/SKILL.md | 5 +
.../public/skills/claude-code-guide/SKILL.md | 9 +-
.../public/skills/claude-d3js-skill/SKILL.md | 6 +-
web-app/public/skills/clean-code/SKILL.md | 2 +-
web-app/public/skills/clerk-auth/SKILL.md | 4 +
.../public/skills/clickup-automation/SKILL.md | 5 +
.../public/skills/close-automation/SKILL.md | 5 +
.../public/skills/cloud-architect/SKILL.md | 4 +-
web-app/public/skills/cloud-devops/SKILL.md | 236 +
.../skills/cloud-penetration-testing/SKILL.md | 9 +-
.../cloudformation-best-practices/SKILL.md | 80 +
.../public/skills/coda-automation/SKILL.md | 5 +
.../code-documentation-code-explain/SKILL.md | 4 +-
.../code-documentation-doc-generate/SKILL.md | 4 +-
.../resources/implementation-playbook.md | 2 +-
.../code-refactoring-context-restore/SKILL.md | 2 +
.../code-refactoring-refactor-clean/SKILL.md | 4 +-
.../code-refactoring-tech-debt/SKILL.md | 2 +
.../skills/code-review-ai-ai-review/SKILL.md | 2 +
.../skills/code-review-checklist/SKILL.md | 2 +
.../skills/code-review-excellence/SKILL.md | 4 +-
web-app/public/skills/code-reviewer/SKILL.md | 2 +
.../codebase-cleanup-deps-audit/SKILL.md | 4 +-
.../codebase-cleanup-refactor-clean/SKILL.md | 4 +-
.../codebase-cleanup-tech-debt/SKILL.md | 2 +
web-app/public/skills/codex-review/SKILL.md | 4 +-
web-app/public/skills/commit/SKILL.md | 2 +-
.../skills/competitive-landscape/SKILL.md | 4 +-
.../skills/competitor-alternatives/SKILL.md | 7 +-
.../comprehensive-review-full-review/SKILL.md | 2 +
.../comprehensive-review-pr-enhance/SKILL.md | 4 +-
.../skills/computer-use-agents/SKILL.md | 6 +-
.../skills/computer-vision-expert/SKILL.md | 4 +-
.../public/skills/concise-planning/SKILL.md | 7 +-
.../skills/conductor-implement/SKILL.md | 4 +-
.../public/skills/conductor-manage/SKILL.md | 2 +
.../resources/implementation-playbook.md | 2 +-
.../skills/conductor-new-track/SKILL.md | 14 +-
.../public/skills/conductor-revert/SKILL.md | 4 +-
.../public/skills/conductor-setup/SKILL.md | 14 +-
.../public/skills/conductor-status/SKILL.md | 4 +-
.../skills/conductor-validator/SKILL.md | 4 +-
.../skills/confluence-automation/SKILL.md | 5 +
.../public/skills/content-creator/SKILL.md | 8 +-
.../public/skills/content-marketer/SKILL.md | 4 +-
.../skills/context-compression/SKILL.md | 6 +-
.../skills/context-degradation/SKILL.md | 2 +-
.../context-driven-development/SKILL.md | 4 +-
.../skills/context-fundamentals/SKILL.md | 2 +-
.../SKILL.md | 2 +
.../context-management-context-save/SKILL.md | 2 +
.../public/skills/context-manager/SKILL.md | 4 +-
.../skills/context-optimization/SKILL.md | 2 +-
.../skills/context-window-management/SKILL.md | 6 +-
.../skills/context7-auto-research/SKILL.md | 4 +-
.../skills/conversation-memory/SKILL.md | 4 +
.../skills/convertkit-automation/SKILL.md | 5 +
web-app/public/skills/copilot-sdk/SKILL.md | 7 +-
web-app/public/skills/copy-editing/SKILL.md | 4 +-
web-app/public/skills/copywriting/SKILL.md | 7 +-
.../public/skills/core-components/SKILL.md | 7 +-
.../public/skills/cost-optimization/SKILL.md | 4 +-
web-app/public/skills/cpp-pro/SKILL.md | 4 +-
.../skills/cqrs-implementation/SKILL.md | 4 +-
web-app/public/skills/crewai/SKILL.md | 6 +-
.../public/skills/crypto-bd-agent/SKILL.md | 2 +-
web-app/public/skills/csharp-pro/SKILL.md | 4 +-
.../public/skills/customer-support/SKILL.md | 4 +-
.../public/skills/daily-news-report/SKILL.md | 9 +-
web-app/public/skills/data-engineer/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../data-engineering-data-pipeline/SKILL.md | 2 +
.../skills/data-quality-frameworks/SKILL.md | 4 +-
web-app/public/skills/data-scientist/SKILL.md | 4 +-
.../public/skills/data-storytelling/SKILL.md | 4 +-
.../skills/data-structure-protocol/SKILL.md | 198 +
web-app/public/skills/database-admin/SKILL.md | 4 +-
.../public/skills/database-architect/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../public/skills/database-design/SKILL.md | 7 +-
.../public/skills/database-migration/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../SKILL.md | 35 +-
.../public/skills/database-optimizer/SKILL.md | 4 +-
web-app/public/skills/database/SKILL.md | 213 +
.../public/skills/datadog-automation/SKILL.md | 5 +
web-app/public/skills/dbos-golang/SKILL.md | 2 +-
.../references/advanced-versioning.md | 6 +-
.../dbos-golang/references/comm-events.md | 6 +-
.../dbos-golang/references/comm-messages.md | 2 +-
.../dbos-golang/references/comm-streaming.md | 4 +-
.../references/workflow-background.md | 2 +-
.../references/workflow-constraints.md | 2 +-
.../references/workflow-control.md | 9 +-
web-app/public/skills/dbos-python/SKILL.md | 2 +-
.../public/skills/dbos-typescript/SKILL.md | 2 +-
.../dbt-transformation-patterns/SKILL.md | 4 +-
.../skills/ddd-context-mapping/SKILL.md | 51 +
.../references/context-map-patterns.md | 25 +
.../skills/ddd-strategic-design/SKILL.md | 51 +
.../references/strategic-design-template.md | 22 +
.../skills/ddd-tactical-patterns/SKILL.md | 52 +
.../references/tactical-checklist.md | 25 +
web-app/public/skills/debugger/SKILL.md | 4 +-
.../skills/debugging-strategies/SKILL.md | 4 +-
.../debugging-toolkit-smart-debug/SKILL.md | 2 +
web-app/public/skills/deep-research/SKILL.md | 2 +-
.../skills/defi-protocol-templates/SKILL.md | 4 +-
.../dependency-management-deps-audit/SKILL.md | 4 +-
.../public/skills/dependency-upgrade/SKILL.md | 4 +-
.../skills/deployment-engineer/SKILL.md | 4 +-
.../deployment-pipeline-design/SKILL.md | 4 +-
.../skills/deployment-procedures/SKILL.md | 7 +-
.../SKILL.md | 2 +
.../skills/design-orchestration/SKILL.md | 7 +-
web-app/public/skills/development/SKILL.md | 263 +
.../skills/devops-troubleshooter/SKILL.md | 4 +-
.../public/skills/discord-automation/SKILL.md | 5 +
.../skills/discord-bot-architect/SKILL.md | 4 +
.../dispatching-parallel-agents/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../resources/implementation-playbook.md | 2 +-
.../skills/distributed-tracing/SKILL.md | 4 +-
web-app/public/skills/django-pro/SKILL.md | 4 +-
.../public/skills/doc-coauthoring/SKILL.md | 7 +-
web-app/public/skills/docker-expert/SKILL.md | 9 +-
web-app/public/skills/docs-architect/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../resources/implementation-playbook.md | 2 +-
.../skills/documentation-templates/SKILL.md | 11 +-
web-app/public/skills/documentation/SKILL.md | 261 +
.../skills/docusign-automation/SKILL.md | 5 +
web-app/public/skills/docx-official/SKILL.md | 11 +-
.../skills/domain-driven-design/SKILL.md | 73 +
.../references/ddd-deliverables.md | 24 +
.../public/skills/dotnet-architect/SKILL.md | 4 +-
.../skills/dotnet-backend-patterns/SKILL.md | 4 +-
web-app/public/skills/dotnet-backend/SKILL.md | 2 +-
.../public/skills/dropbox-automation/SKILL.md | 5 +
web-app/public/skills/dx-optimizer/SKILL.md | 4 +-
.../skills/e2e-testing-patterns/SKILL.md | 4 +-
web-app/public/skills/e2e-testing/SKILL.md | 166 +
web-app/public/skills/elixir-pro/SKILL.md | 4 +-
web-app/public/skills/email-sequence/SKILL.md | 7 +-
web-app/public/skills/email-systems/SKILL.md | 6 +-
.../skills/embedding-strategies/SKILL.md | 4 +-
.../employment-contract-templates/SKILL.md | 4 +-
.../skills/environment-setup-guide/SKILL.md | 2 +
.../error-debugging-error-analysis/SKILL.md | 2 +
.../error-debugging-error-trace/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../public/skills/error-detective/SKILL.md | 4 +-
.../error-diagnostics-error-analysis/SKILL.md | 2 +
.../error-diagnostics-error-trace/SKILL.md | 2 +
.../error-diagnostics-smart-debug/SKILL.md | 2 +
.../skills/error-handling-patterns/SKILL.md | 4 +-
.../ethical-hacking-methodology/SKILL.md | 9 +-
web-app/public/skills/evaluation/SKILL.md | 2 +-
.../skills/event-sourcing-architect/SKILL.md | 4 +-
.../public/skills/event-store-design/SKILL.md | 4 +-
.../resources/implementation-playbook.md | 25 +
web-app/public/skills/exa-search/SKILL.md | 4 +-
.../public/skills/executing-plans/SKILL.md | 7 +-
web-app/public/skills/fastapi-pro/SKILL.md | 4 +-
.../public/skills/fastapi-router-py/SKILL.md | 9 +-
.../public/skills/fastapi-templates/SKILL.md | 4 +-
.../public/skills/figma-automation/SKILL.md | 5 +
web-app/public/skills/file-organizer/SKILL.md | 4 +-
.../skills/file-path-traversal/SKILL.md | 9 +-
web-app/public/skills/file-uploads/SKILL.md | 6 +-
.../finishing-a-development-branch/SKILL.md | 7 +-
web-app/public/skills/firebase/SKILL.md | 6 +-
.../public/skills/firecrawl-scraper/SKILL.md | 4 +-
.../public/skills/firmware-analyst/SKILL.md | 4 +-
web-app/public/skills/flutter-expert/SKILL.md | 4 +-
web-app/public/skills/form-cro/SKILL.md | 7 +-
web-app/public/skills/fp-ts-errors/SKILL.md | 2 +-
.../public/skills/fp-ts-pragmatic/SKILL.md | 2 +-
web-app/public/skills/fp-ts-react/SKILL.md | 2 +-
.../framework-migration-code-migrate/SKILL.md | 2 +
.../framework-migration-deps-upgrade/SKILL.md | 2 +
.../resources/implementation-playbook.md | 6 +-
.../SKILL.md | 2 +
.../public/skills/free-tool-strategy/SKILL.md | 7 +-
.../skills/freshdesk-automation/SKILL.md | 5 +
.../skills/freshservice-automation/SKILL.md | 5 +
.../public/skills/frontend-design/SKILL.md | 7 +-
.../skills/frontend-dev-guidelines/SKILL.md | 7 +-
.../public/skills/frontend-developer/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../SKILL.md | 2 +
.../skills/frontend-security-coder/SKILL.md | 4 +-
.../public/skills/frontend-slides/SKILL.md | 5 +-
.../skills/frontend-ui-dark-ts/SKILL.md | 13 +-
.../SKILL.md | 2 +
.../skills/game-development/2d-games/SKILL.md | 7 +-
.../skills/game-development/3d-games/SKILL.md | 7 +-
.../public/skills/game-development/SKILL.md | 4 +-
.../skills/game-development/game-art/SKILL.md | 7 +-
.../game-development/game-audio/SKILL.md | 7 +-
.../game-development/game-design/SKILL.md | 7 +-
.../game-development/mobile-games/SKILL.md | 7 +-
.../game-development/multiplayer/SKILL.md | 7 +-
.../skills/game-development/pc-games/SKILL.md | 7 +-
.../skills/game-development/vr-ar/SKILL.md | 7 +-
.../game-development/web-games/SKILL.md | 7 +-
web-app/public/skills/gcp-cloud-run/SKILL.md | 6 +-
.../public/skills/gdpr-data-handling/SKILL.md | 4 +-
web-app/public/skills/gemini-api-dev/SKILL.md | 7 +-
.../public/skills/geo-fundamentals/SKILL.md | 7 +-
.../skills/git-advanced-workflows/SKILL.md | 4 +-
.../git-pr-workflows-git-workflow/SKILL.md | 2 +
.../skills/git-pr-workflows-onboard/SKILL.md | 2 +
.../git-pr-workflows-pr-enhance/SKILL.md | 2 +
web-app/public/skills/git-pushing/SKILL.md | 4 +-
.../skills/github-actions-templates/SKILL.md | 4 +-
.../public/skills/github-automation/SKILL.md | 5 +
.../skills/github-issue-creator/SKILL.md | 11 +-
.../github-workflow-automation/SKILL.md | 4 +-
.../public/skills/gitlab-automation/SKILL.md | 5 +
.../public/skills/gitlab-ci-patterns/SKILL.md | 4 +-
.../public/skills/gitops-workflow/SKILL.md | 4 +-
.../public/skills/gmail-automation/SKILL.md | 7 +-
.../skills/go-concurrency-patterns/SKILL.md | 4 +-
web-app/public/skills/go-playwright/SKILL.md | 2 +-
.../public/skills/godot-4-migration/SKILL.md | 126 +
.../skills/godot-gdscript-patterns/SKILL.md | 4 +-
web-app/public/skills/golang-pro/SKILL.md | 4 +-
.../google-analytics-automation/SKILL.md | 5 +
.../google-calendar-automation/SKILL.md | 7 +-
.../skills/google-drive-automation/SKILL.md | 7 +-
.../skills/googlesheets-automation/SKILL.md | 5 +
.../public/skills/grafana-dashboards/SKILL.md | 4 +-
.../public/skills/graphql-architect/SKILL.md | 4 +-
web-app/public/skills/graphql/SKILL.md | 6 +-
web-app/public/skills/haskell-pro/SKILL.md | 2 +
.../skills/helm-chart-scaffolding/SKILL.md | 4 +-
.../skills/helpdesk-automation/SKILL.md | 5 +
.../skills/hig-components-content/SKILL.md | 91 +
.../references/activity-views.md | 79 +
.../references/charts.md | 180 +
.../references/collections.md | 48 +
.../references/color-wells.md | 42 +
.../references/image-views.md | 82 +
.../references/image-wells.md | 34 +
.../references/lockups.md | 78 +
.../references/web-views.md | 36 +
.../skills/hig-components-controls/SKILL.md | 93 +
.../references/combo-boxes.md | 40 +
.../references/controls.md | 112 +
.../references/gauges.md | 74 +
.../references/labels.md | 92 +
.../references/pickers.md | 128 +
.../references/rating-indicators.md | 38 +
.../references/segmented-controls.md | 94 +
.../references/sliders.md | 92 +
.../references/steppers.md | 40 +
.../references/text-fields.md | 88 +
.../references/text-views.md | 56 +
.../references/toggles.md | 127 +
.../references/token-fields.md | 48 +
.../references/virtual-keyboards.md | 156 +
.../skills/hig-components-dialogs/SKILL.md | 81 +
.../references/action-sheets.md | 74 +
.../references/alerts.md | 158 +
.../references/digit-entry-views.md | 32 +
.../references/popovers.md | 81 +
.../references/sheets.md | 157 +
.../skills/hig-components-layout/SKILL.md | 104 +
.../hig-components-layout/references/boxes.md | 48 +
.../references/column-views.md | 44 +
.../references/lists-and-tables.md | 99 +
.../references/ornaments.md | 56 +
.../references/outline-views.md | 64 +
.../references/panels.md | 75 +
.../references/scroll-views.md | 123 +
.../references/sidebars.md | 109 +
.../references/split-views.md | 110 +
.../references/tab-bars.md | 173 +
.../references/tab-views.md | 68 +
.../references/windows.md | 188 +
.../skills/hig-components-menus/SKILL.md | 86 +
.../references/action-button.md | 61 +
.../references/buttons.md | 261 +
.../references/context-menus.md | 105 +
.../references/disclosure-controls.md | 84 +
.../references/dock-menus.md | 40 +
.../references/edit-menus.md | 88 +
.../hig-components-menus/references/menus.md | 171 +
.../references/pop-up-buttons.md | 70 +
.../references/pull-down-buttons.md | 77 +
.../references/the-menu-bar.md | 303 ++
.../references/toolbars.md | 256 +
.../skills/hig-components-search/SKILL.md | 73 +
.../references/page-controls.md | 120 +
.../references/path-controls.md | 40 +
.../references/search-fields.md | 189 +
.../skills/hig-components-status/SKILL.md | 91 +
.../references/activity-rings.md | 105 +
.../references/progress-indicators.md | 116 +
.../references/status-bars.md | 38 +
.../skills/hig-components-system/SKILL.md | 111 +
.../references/app-clips.md | 387 ++
.../references/app-shortcuts.md | 114 +
.../references/complications.md | 425 ++
.../references/home-screen-quick-actions.md | 42 +
.../references/live-activities.md | 442 ++
.../references/notifications.md | 153 +
.../references/top-shelf.md | 135 +
.../references/watch-faces.md | 40 +
.../references/widgets.md | 517 ++
.../public/skills/hig-foundations/SKILL.md | 103 +
.../references/accessibility.md | 291 +
.../hig-foundations/references/app-icons.md | 210 +
.../hig-foundations/references/branding.md | 44 +
.../hig-foundations/references/color.md | 274 +
.../hig-foundations/references/dark-mode.md | 116 +
.../hig-foundations/references/icons.md | 263 +
.../hig-foundations/references/images.md | 176 +
.../references/immersive-experiences.md | 174 +
.../hig-foundations/references/inclusion.md | 189 +
.../hig-foundations/references/layout.md | 425 ++
.../hig-foundations/references/materials.md | 238 +
.../hig-foundations/references/motion.md | 103 +
.../hig-foundations/references/privacy.md | 231 +
.../references/right-to-left.md | 206 +
.../hig-foundations/references/sf-symbols.md | 310 ++
.../references/spatial-layout.md | 142 +
.../hig-foundations/references/typography.md | 1146 ++++
.../hig-foundations/references/writing.md | 91 +
web-app/public/skills/hig-inputs/SKILL.md | 121 +
.../references/apple-pencil-and-scribble.md | 148 +
.../hig-inputs/references/camera-control.md | 107 +
.../hig-inputs/references/digital-crown.md | 83 +
.../skills/hig-inputs/references/eyes.md | 120 +
.../references/focus-and-selection.md | 120 +
.../hig-inputs/references/game-controls.md | 156 +
.../skills/hig-inputs/references/gestures.md | 208 +
.../references/gyro-and-accelerometer.md | 40 +
.../skills/hig-inputs/references/keyboards.md | 234 +
.../references/nearby-interactions.md | 70 +
.../hig-inputs/references/pointing-devices.md | 237 +
.../skills/hig-inputs/references/remotes.md | 67 +
.../references/spatial-interactions.md | 70 +
web-app/public/skills/hig-patterns/SKILL.md | 109 +
.../hig-patterns/references/charting-data.md | 81 +
.../references/collaboration-and-sharing.md | 86 +
.../hig-patterns/references/drag-and-drop.md | 134 +
.../hig-patterns/references/entering-data.md | 69 +
.../hig-patterns/references/feedback.md | 67 +
.../references/file-management.md | 135 +
.../references/going-full-screen.md | 79 +
.../hig-patterns/references/launching.md | 81 +
.../references/live-viewing-apps.md | 79 +
.../skills/hig-patterns/references/loading.md | 59 +
.../references/managing-accounts.md | 107 +
.../references/managing-notifications.md | 99 +
.../hig-patterns/references/modality.md | 82 +
.../hig-patterns/references/multitasking.md | 131 +
.../hig-patterns/references/offering-help.md | 117 +
.../hig-patterns/references/onboarding.md | 69 +
.../hig-patterns/references/playing-audio.md | 124 +
.../references/playing-haptics.md | 280 +
.../hig-patterns/references/playing-video.md | 180 +
.../hig-patterns/references/printing.md | 50 +
.../references/ratings-and-reviews.md | 48 +
.../hig-patterns/references/searching.md | 70 +
.../hig-patterns/references/settings.md | 84 +
.../hig-patterns/references/undo-and-redo.md | 58 +
.../hig-patterns/references/workouts.md | 76 +
web-app/public/skills/hig-platforms/SKILL.md | 89 +
.../references/designing-for-games.md | 159 +
.../references/designing-for-ios.md | 66 +
.../references/designing-for-ipados.md | 64 +
.../references/designing-for-macos.md | 70 +
.../references/designing-for-tvos.md | 68 +
.../references/designing-for-visionos.md | 85 +
.../references/designing-for-watchos.md | 74 +
.../skills/hig-project-context/SKILL.md | 138 +
.../public/skills/hig-technologies/SKILL.md | 136 +
.../hig-technologies/references/airplay.md | 125 +
.../hig-technologies/references/always-on.md | 62 +
.../hig-technologies/references/apple-pay.md | 441 ++
.../references/augmented-reality.md | 247 +
.../hig-technologies/references/carekit.md | 224 +
.../hig-technologies/references/carplay.md | 119 +
.../references/game-center.md | 343 ++
.../references/generative-ai.md | 110 +
.../hig-technologies/references/healthkit.md | 120 +
.../hig-technologies/references/homekit.md | 343 ++
.../hig-technologies/references/icloud.md | 52 +
.../references/id-verifier.md | 73 +
.../references/imessage-apps-and-stickers.md | 105 +
.../references/in-app-purchase.md | 263 +
.../references/live-photos.md | 54 +
.../references/mac-catalyst.md | 216 +
.../references/machine-learning.md | 394 ++
.../hig-technologies/references/maps.md | 221 +
.../skills/hig-technologies/references/nfc.md | 51 +
.../references/photo-editing.md | 40 +
.../references/researchkit.md | 134 +
.../hig-technologies/references/shareplay.md | 142 +
.../hig-technologies/references/shazamkit.md | 47 +
.../references/sign-in-with-apple.md | 288 +
.../hig-technologies/references/siri.md | 523 ++
.../references/tap-to-pay-on-iphone.md | 208 +
.../hig-technologies/references/voiceover.md | 90 +
.../hig-technologies/references/wallet.md | 420 ++
.../skills/hosted-agents-v2-py/SKILL.md | 11 +-
web-app/public/skills/hr-pro/SKILL.md | 4 +-
.../skills/html-injection-testing/SKILL.md | 9 +-
.../public/skills/hubspot-automation/SKILL.md | 7 +-
.../skills/hubspot-integration/SKILL.md | 6 +-
.../public/skills/hugging-face-cli/SKILL.md | 6 +-
.../public/skills/hugging-face-jobs/SKILL.md | 2 +-
.../skills/hybrid-cloud-architect/SKILL.md | 4 +-
.../skills/hybrid-cloud-networking/SKILL.md | 4 +-
.../hybrid-search-implementation/SKILL.md | 4 +-
.../public/skills/i18n-localization/SKILL.md | 7 +-
web-app/public/skills/idor-testing/SKILL.md | 9 +-
web-app/public/skills/imagen/SKILL.md | 2 +-
.../public/skills/incident-responder/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../incident-response-smart-fix/SKILL.md | 2 +
.../incident-runbook-templates/SKILL.md | 4 +-
.../public/skills/infinite-gratitude/SKILL.md | 4 +-
web-app/public/skills/inngest/SKILL.md | 6 +-
.../skills/instagram-automation/SKILL.md | 5 +
.../skills/interactive-portfolio/SKILL.md | 6 +-
.../skills/intercom-automation/SKILL.md | 5 +
.../skills/internal-comms-anthropic/SKILL.md | 6 +-
.../skills/internal-comms-community/SKILL.md | 6 +-
web-app/public/skills/ios-developer/SKILL.md | 4 +-
.../skills/istio-traffic-management/SKILL.md | 4 +-
web-app/public/skills/java-pro/SKILL.md | 4 +-
.../public/skills/javascript-mastery/SKILL.md | 4 +-
web-app/public/skills/javascript-pro/SKILL.md | 4 +-
.../javascript-testing-patterns/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../public/skills/jira-automation/SKILL.md | 5 +
web-app/public/skills/julia-pro/SKILL.md | 4 +-
.../skills/k8s-manifest-generator/SKILL.md | 4 +-
.../skills/k8s-security-policies/SKILL.md | 4 +-
web-app/public/skills/kaizen/SKILL.md | 4 +-
.../public/skills/klaviyo-automation/SKILL.md | 5 +
.../skills/kotlin-coroutines-expert/SKILL.md | 100 +
.../skills/kpi-dashboard-design/SKILL.md | 4 +-
.../skills/kubernetes-architect/SKILL.md | 4 +-
.../skills/kubernetes-deployment/SKILL.md | 167 +
.../skills/langchain-architecture/SKILL.md | 4 +-
web-app/public/skills/langfuse/SKILL.md | 6 +-
web-app/public/skills/langgraph/SKILL.md | 6 +-
web-app/public/skills/laravel-expert/SKILL.md | 2 +-
.../skills/laravel-security-audit/SKILL.md | 2 +-
web-app/public/skills/last30days/SKILL.md | 7 +-
.../public/skills/launch-strategy/SKILL.md | 7 +-
.../public/skills/legacy-modernizer/SKILL.md | 4 +-
web-app/public/skills/legal-advisor/SKILL.md | 4 +-
.../public/skills/libreoffice/base/SKILL.md | 188 +
.../public/skills/libreoffice/calc/SKILL.md | 201 +
.../public/skills/libreoffice/draw/SKILL.md | 165 +
.../skills/libreoffice/impress/SKILL.md | 174 +
.../public/skills/libreoffice/writer/SKILL.md | 200 +
.../public/skills/linear-automation/SKILL.md | 5 +
.../skills/linear-claude-skill/SKILL.md | 28 +-
.../skills/linkedin-automation/SKILL.md | 5 +
.../public/skills/linkerd-patterns/SKILL.md | 4 +-
.../public/skills/lint-and-validate/SKILL.md | 7 +-
.../linux-privilege-escalation/SKILL.md | 9 +-
.../skills/linux-shell-scripting/SKILL.md | 9 +-
.../skills/linux-troubleshooting/SKILL.md | 221 +
.../public/skills/llm-app-patterns/SKILL.md | 6 +-
.../llm-application-dev-ai-assistant/SKILL.md | 2 +
.../resources/implementation-playbook.md | 2 +-
.../SKILL.md | 2 +
.../SKILL.md | 2 +
web-app/public/skills/llm-evaluation/SKILL.md | 4 +-
web-app/public/skills/loki-mode/SKILL.md | 7 +-
.../public/skills/m365-agents-dotnet/SKILL.md | 9 +-
web-app/public/skills/m365-agents-py/SKILL.md | 17 +-
web-app/public/skills/m365-agents-ts/SKILL.md | 9 +-
.../machine-learning-ops-ml-pipeline/SKILL.md | 2 +
.../skills/mailchimp-automation/SKILL.md | 5 +
.../public/skills/make-automation/SKILL.md | 5 +
.../public/skills/malware-analyst/SKILL.md | 4 +-
web-app/public/skills/manifest/SKILL.md | 126 +
.../skills/market-sizing-analysis/SKILL.md | 4 +-
.../public/skills/marketing-ideas/SKILL.md | 7 +-
.../skills/marketing-psychology/SKILL.md | 7 +-
web-app/public/skills/mcp-builder-ms/SKILL.md | 44 +-
web-app/public/skills/mcp-builder/SKILL.md | 7 +-
.../public/skills/memory-forensics/SKILL.md | 4 +-
.../skills/memory-safety-patterns/SKILL.md | 4 +-
web-app/public/skills/memory-systems/SKILL.md | 2 +-
web-app/public/skills/mermaid-expert/SKILL.md | 4 +-
.../skills/metasploit-framework/SKILL.md | 9 +-
.../skills/micro-saas-launcher/SKILL.md | 6 +-
.../skills/microservices-patterns/SKILL.md | 4 +-
.../SKILL.md | 7 +-
.../microsoft-teams-automation/SKILL.md | 5 +
.../skills/minecraft-bukkit-pro/SKILL.md | 4 +-
.../public/skills/miro-automation/SKILL.md | 5 +
.../skills/mixpanel-automation/SKILL.md | 5 +
web-app/public/skills/ml-engineer/SKILL.md | 4 +-
.../skills/ml-pipeline-workflow/SKILL.md | 4 +-
web-app/public/skills/mlops-engineer/SKILL.md | 4 +-
web-app/public/skills/mobile-design/SKILL.md | 7 +-
.../public/skills/mobile-developer/SKILL.md | 4 +-
.../skills/mobile-security-coder/SKILL.md | 4 +-
.../modern-javascript-patterns/SKILL.md | 4 +-
.../public/skills/monday-automation/SKILL.md | 5 +
.../public/skills/monorepo-architect/SKILL.md | 2 +
.../skills/monorepo-management/SKILL.md | 4 +-
.../moodle-external-api-development/SKILL.md | 4 +-
.../public/skills/mtls-configuration/SKILL.md | 4 +-
.../skills/multi-agent-brainstorming/SKILL.md | 7 +-
.../skills/multi-agent-patterns/SKILL.md | 2 +-
.../skills/multi-cloud-architecture/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../public/skills/n8n-code-python/SKILL.md | 22 +-
.../skills/n8n-mcp-tools-expert/SKILL.md | 20 +-
.../skills/n8n-node-configuration/SKILL.md | 6 +-
web-app/public/skills/neon-postgres/SKILL.md | 6 +-
.../skills/nerdzao-elite-gemini-high/SKILL.md | 50 +
web-app/public/skills/nerdzao-elite/SKILL.md | 31 +
web-app/public/skills/nestjs-expert/SKILL.md | 9 +-
web-app/public/skills/network-101/SKILL.md | 9 +-
.../public/skills/network-engineer/SKILL.md | 4 +-
.../nextjs-app-router-patterns/SKILL.md | 4 +-
.../skills/nextjs-best-practices/SKILL.md | 7 +-
.../skills/nextjs-supabase-auth/SKILL.md | 4 +
web-app/public/skills/nft-standards/SKILL.md | 4 +-
.../skills/nodejs-backend-patterns/SKILL.md | 4 +-
.../skills/nodejs-best-practices/SKILL.md | 8 +-
web-app/public/skills/nosql-expert/SKILL.md | 2 +
web-app/public/skills/notebooklm/SKILL.md | 4 +-
.../public/skills/notion-automation/SKILL.md | 5 +
.../skills/notion-template-business/SKILL.md | 6 +-
.../skills/nx-workspace-patterns/SKILL.md | 4 +-
.../skills/observability-engineer/SKILL.md | 4 +-
.../SKILL.md | 2 +
.../SKILL.md | 4 +-
.../public/skills/observe-whatsapp/SKILL.md | 8 +-
.../SKILL.md | 7 +-
.../skills/office-productivity/SKILL.md | 219 +
.../skills/on-call-handoff-patterns/SKILL.md | 4 +-
web-app/public/skills/onboarding-cro/SKILL.md | 7 +-
.../skills/one-drive-automation/SKILL.md | 5 +
.../skills/openapi-spec-generation/SKILL.md | 4 +-
web-app/public/skills/os-scripting/SKILL.md | 429 ++
web-app/public/skills/oss-hunter/SKILL.md | 2 +-
.../public/skills/outlook-automation/SKILL.md | 5 +
.../outlook-calendar-automation/SKILL.md | 5 +
web-app/public/skills/page-cro/SKILL.md | 7 +-
.../skills/pagerduty-automation/SKILL.md | 5 +
web-app/public/skills/paid-ads/SKILL.md | 7 +-
.../public/skills/parallel-agents/SKILL.md | 4 +-
.../skills/payment-integration/SKILL.md | 4 +-
.../public/skills/paypal-integration/SKILL.md | 4 +-
.../skills/paywall-upgrade-cro/SKILL.md | 7 +-
web-app/public/skills/pci-compliance/SKILL.md | 4 +-
web-app/public/skills/pdf-official/SKILL.md | 9 +-
.../public/skills/pentest-checklist/SKILL.md | 9 +-
.../public/skills/pentest-commands/SKILL.md | 9 +-
.../skills/performance-engineer/SKILL.md | 2 +
.../skills/performance-profiling/SKILL.md | 7 +-
.../SKILL.md | 2 +
.../SKILL.md | 2 +
.../skills/personal-tool-builder/SKILL.md | 6 +-
web-app/public/skills/php-pro/SKILL.md | 4 +-
.../skills/pipedrive-automation/SKILL.md | 5 +
web-app/public/skills/plaid-fintech/SKILL.md | 6 +-
web-app/public/skills/plan-writing/SKILL.md | 4 +-
.../skills/planning-with-files/SKILL.md | 4 +-
.../public/skills/playwright-skill/SKILL.md | 7 +-
.../public/skills/podcast-generation/SKILL.md | 13 +-
web-app/public/skills/popup-cro/SKILL.md | 7 +-
.../public/skills/posix-shell-pro/SKILL.md | 4 +-
.../skills/postgres-best-practices/SKILL.md | 9 +-
.../skills/postgresql-optimization/SKILL.md | 175 +
web-app/public/skills/postgresql/SKILL.md | 4 +-
.../public/skills/posthog-automation/SKILL.md | 5 +
.../skills/postmark-automation/SKILL.md | 5 +
.../public/skills/postmortem-writing/SKILL.md | 8 +-
.../public/skills/powershell-windows/SKILL.md | 7 +-
web-app/public/skills/pptx-official/SKILL.md | 11 +-
.../public/skills/pricing-strategy/SKILL.md | 7 +-
web-app/public/skills/prisma-expert/SKILL.md | 7 +-
.../privilege-escalation-methods/SKILL.md | 9 +-
.../skills/product-manager-toolkit/SKILL.md | 7 +-
.../skills/production-code-audit/SKILL.md | 2 +
.../public/skills/programmatic-seo/SKILL.md | 7 +-
.../skills/projection-patterns/SKILL.md | 4 +-
.../skills/prometheus-configuration/SKILL.md | 4 +-
web-app/public/skills/prompt-caching/SKILL.md | 6 +-
.../public/skills/prompt-engineer/README.md | 2 +-
.../public/skills/prompt-engineer/SKILL.md | 1 +
.../prompt-engineering-patterns/SKILL.md | 4 +-
.../public/skills/prompt-engineering/SKILL.md | 7 +-
web-app/public/skills/prompt-library/SKILL.md | 4 +-
.../protocol-reverse-engineering/SKILL.md | 4 +-
.../public/skills/pydantic-models-py/SKILL.md | 9 +-
.../SKILL.md | 2 +
.../python-fastapi-development/SKILL.md | 216 +
.../public/skills/python-packaging/SKILL.md | 4 +-
.../public/skills/python-patterns/SKILL.md | 8 +-
.../python-performance-optimization/SKILL.md | 4 +-
web-app/public/skills/python-pro/SKILL.md | 4 +-
.../skills/python-testing-patterns/SKILL.md | 4 +-
web-app/public/skills/quant-analyst/SKILL.md | 4 +-
.../skills/radix-ui-design-system/SKILL.md | 2 +-
web-app/public/skills/rag-engineer/SKILL.md | 6 +-
.../public/skills/rag-implementation/SKILL.md | 514 +-
.../skills/react-best-practices/SKILL.md | 9 +-
.../skills/react-flow-architect/SKILL.md | 7 +-
.../public/skills/react-flow-node-ts/SKILL.md | 13 +-
.../skills/react-modernization/SKILL.md | 4 +-
.../skills/react-native-architecture/SKILL.md | 4 +-
.../skills/react-nextjs-development/SKILL.md | 229 +
web-app/public/skills/react-patterns/SKILL.md | 7 +-
.../skills/react-state-management/SKILL.md | 4 +-
.../public/skills/react-ui-patterns/SKILL.md | 7 +-
web-app/public/skills/readme/SKILL.md | 2 +-
.../skills/receiving-code-review/SKILL.md | 7 +-
.../public/skills/red-team-tactics/SKILL.md | 7 +-
web-app/public/skills/red-team-tools/SKILL.md | 9 +-
.../public/skills/reddit-automation/SKILL.md | 7 +-
.../public/skills/reference-builder/SKILL.md | 4 +-
.../public/skills/referral-program/SKILL.md | 7 +-
.../skills/remotion-best-practices/SKILL.md | 4 +-
.../remotion-best-practices/rules/charts.md | 2 +-
.../public/skills/render-automation/SKILL.md | 5 +
.../skills/requesting-code-review/SKILL.md | 7 +-
.../public/skills/research-engineer/SKILL.md | 7 +-
.../public/skills/reverse-engineer/SKILL.md | 4 +-
web-app/public/skills/risk-manager/SKILL.md | 4 +-
.../skills/risk-metrics-calculation/SKILL.md | 4 +-
web-app/public/skills/ruby-pro/SKILL.md | 4 +-
.../skills/rust-async-patterns/SKILL.md | 4 +-
web-app/public/skills/rust-pro/SKILL.md | 4 +-
.../public/skills/saga-orchestration/SKILL.md | 4 +-
.../resources/implementation-playbook.md | 26 +
.../public/skills/sales-automator/SKILL.md | 4 +-
.../skills/salesforce-automation/SKILL.md | 5 +
.../skills/salesforce-development/SKILL.md | 6 +-
.../public/skills/sast-configuration/SKILL.md | 22 +-
web-app/public/skills/scala-pro/SKILL.md | 4 +-
web-app/public/skills/scanning-tools/SKILL.md | 9 +-
web-app/public/skills/schema-markup/SKILL.md | 7 +-
.../skills/screen-reader-testing/SKILL.md | 4 +-
.../public/skills/scroll-experience/SKILL.md | 6 +-
.../public/skills/search-specialist/SKILL.md | 2 +
.../public/skills/secrets-management/SKILL.md | 4 +-
web-app/public/skills/security-audit/SKILL.md | 218 +
.../public/skills/security-auditor/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../security-requirement-extraction/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../SKILL.md | 2 +
.../security-scanning-security-sast/SKILL.md | 4 +-
.../security/aws-compliance-checker/SKILL.md | 516 ++
.../security/aws-iam-best-practices/SKILL.md | 397 ++
.../security/aws-secrets-rotation/SKILL.md | 465 ++
.../security/aws-security-audit/SKILL.md | 369 ++
.../public/skills/segment-automation/SKILL.md | 5 +
web-app/public/skills/segment-cdp/SKILL.md | 6 +-
.../skills/sendgrid-automation/SKILL.md | 7 +-
.../public/skills/senior-architect/SKILL.md | 7 +-
.../public/skills/senior-fullstack/SKILL.md | 7 +-
.../public/skills/sentry-automation/SKILL.md | 5 +
web-app/public/skills/seo-audit/SKILL.md | 7 +-
.../skills/seo-authority-builder/SKILL.md | 4 +-
.../seo-cannibalization-detector/SKILL.md | 4 +-
.../skills/seo-content-auditor/SKILL.md | 4 +-
.../skills/seo-content-planner/SKILL.md | 4 +-
.../skills/seo-content-refresher/SKILL.md | 4 +-
.../public/skills/seo-content-writer/SKILL.md | 4 +-
.../public/skills/seo-fundamentals/SKILL.md | 7 +-
.../skills/seo-keyword-strategist/SKILL.md | 4 +-
.../public/skills/seo-meta-optimizer/SKILL.md | 4 +-
.../public/skills/seo-snippet-hunter/SKILL.md | 4 +-
.../skills/seo-structure-architect/SKILL.md | 4 +-
.../public/skills/server-management/SKILL.md | 7 +-
.../skills/service-mesh-expert/SKILL.md | 2 +
.../service-mesh-observability/SKILL.md | 4 +-
.../skills/shader-programming-glsl/SKILL.md | 121 +
.../skills/shellcheck-configuration/SKILL.md | 4 +-
.../skills/shodan-reconnaissance/SKILL.md | 9 +-
web-app/public/skills/shopify-apps/SKILL.md | 6 +-
.../public/skills/shopify-automation/SKILL.md | 5 +
.../skills/shopify-development/SKILL.md | 5 +
.../public/skills/signup-flow-cro/SKILL.md | 7 +-
.../similarity-search-patterns/SKILL.md | 4 +-
.../public/skills/skill-creator-ms/SKILL.md | 17 +-
web-app/public/skills/skill-creator/SKILL.md | 3 +-
.../public/skills/skill-developer/SKILL.md | 4 +-
.../public/skills/slack-automation/SKILL.md | 7 +-
.../public/skills/slack-bot-builder/SKILL.md | 6 +-
.../public/skills/slack-gif-creator/SKILL.md | 7 +-
.../public/skills/slo-implementation/SKILL.md | 4 +-
.../skills/smtp-penetration-testing/SKILL.md | 9 +-
web-app/public/skills/social-content/SKILL.md | 7 +-
.../skills/software-architecture/SKILL.md | 7 +-
.../public/skills/solidity-security/SKILL.md | 4 +-
.../public/skills/spark-optimization/SKILL.md | 4 +-
.../skills/sql-injection-testing/SKILL.md | 9 +-
.../skills/sql-optimization-patterns/SKILL.md | 4 +-
web-app/public/skills/sql-pro/SKILL.md | 4 +-
.../sqlmap-database-pentesting/SKILL.md | 9 +-
.../public/skills/square-automation/SKILL.md | 5 +
.../skills/ssh-penetration-testing/SKILL.md | 9 +-
.../public/skills/startup-analyst/SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../SKILL.md | 4 +-
.../startup-financial-modeling/SKILL.md | 4 +-
.../skills/startup-metrics-framework/SKILL.md | 4 +-
.../public/skills/stitch-ui-design/SKILL.md | 5 +-
.../skills/stride-analysis-patterns/SKILL.md | 4 +-
.../public/skills/stripe-automation/SKILL.md | 5 +
.../public/skills/stripe-integration/SKILL.md | 4 +-
.../subagent-driven-development/SKILL.md | 4 +-
.../skills/supabase-automation/SKILL.md | 5 +
.../skills/swiftui-expert-skill/SKILL.md | 2 +-
.../skills/systematic-debugging/SKILL.md | 4 +-
.../systems-programming-rust-project/SKILL.md | 2 +
.../skills/tailwind-design-system/SKILL.md | 4 +-
.../public/skills/tailwind-patterns/SKILL.md | 8 +-
web-app/public/skills/tavily-web/SKILL.md | 4 +-
.../public/skills/tdd-orchestrator/SKILL.md | 4 +-
web-app/public/skills/tdd-workflow/SKILL.md | 7 +-
.../skills/tdd-workflows-tdd-cycle/SKILL.md | 2 +
.../skills/tdd-workflows-tdd-green/SKILL.md | 4 +-
.../skills/tdd-workflows-tdd-red/SKILL.md | 4 +-
.../tdd-workflows-tdd-refactor/SKILL.md | 2 +
.../skills/team-collaboration-issue/SKILL.md | 2 +
.../team-collaboration-standup-notes/SKILL.md | 2 +
.../resources/implementation-playbook.md | 6 +-
.../skills/team-composition-analysis/SKILL.md | 4 +-
.../skills/telegram-automation/SKILL.md | 5 +
.../skills/telegram-bot-builder/SKILL.md | 6 +-
.../public/skills/telegram-mini-app/SKILL.md | 6 +-
.../skills/temporal-python-pro/SKILL.md | 4 +-
.../skills/temporal-python-testing/SKILL.md | 4 +-
.../skills/terraform-aws-modules/SKILL.md | 79 +
.../skills/terraform-infrastructure/SKILL.md | 164 +
.../skills/terraform-module-library/SKILL.md | 4 +-
.../public/skills/terraform-skill/SKILL.md | 38 +-
.../skills/terraform-specialist/SKILL.md | 4 +-
web-app/public/skills/test-automator/SKILL.md | 4 +-
.../skills/test-driven-development/SKILL.md | 4 +-
web-app/public/skills/test-fixing/SKILL.md | 4 +-
.../public/skills/testing-patterns/SKILL.md | 7 +-
web-app/public/skills/testing-qa/SKILL.md | 231 +
web-app/public/skills/theme-factory/SKILL.md | 7 +-
.../skills/threat-mitigation-mapping/SKILL.md | 4 +-
.../skills/threat-modeling-expert/SKILL.md | 4 +-
web-app/public/skills/threejs-skills/SKILL.md | 2 +-
.../public/skills/tiktok-automation/SKILL.md | 5 +
.../public/skills/todoist-automation/SKILL.md | 5 +
web-app/public/skills/tool-design/SKILL.md | 6 +-
.../skills/top-web-vulnerabilities/SKILL.md | 9 +-
.../public/skills/track-management/SKILL.md | 4 +-
.../resources/implementation-playbook.md | 8 +-
.../public/skills/trello-automation/SKILL.md | 7 +-
web-app/public/skills/trigger-dev/SKILL.md | 6 +-
.../public/skills/turborepo-caching/SKILL.md | 4 +-
.../public/skills/tutorial-engineer/SKILL.md | 4 +-
.../skills/twilio-communications/SKILL.md | 6 +-
.../public/skills/twitter-automation/SKILL.md | 5 +
.../skills/typescript-advanced-types/SKILL.md | 4 +-
.../public/skills/typescript-expert/SKILL.md | 7 +-
web-app/public/skills/typescript-pro/SKILL.md | 4 +-
web-app/public/skills/ui-ux-designer/SKILL.md | 4 +-
web-app/public/skills/ui-ux-pro-max/SKILL.md | 7 +-
.../skills/ui-visual-validator/SKILL.md | 4 +-
.../unit-testing-test-generate/SKILL.md | 4 +-
.../public/skills/unity-developer/SKILL.md | 4 +-
.../public/skills/unity-ecs-patterns/SKILL.md | 4 +-
.../skills/unreal-engine-cpp-pro/SKILL.md | 2 +-
web-app/public/skills/upstash-qstash/SKILL.md | 6 +-
.../skills/using-git-worktrees/SKILL.md | 7 +-
web-app/public/skills/using-neon/SKILL.md | 2 +-
.../public/skills/using-superpowers/SKILL.md | 7 +-
.../public/skills/uv-package-manager/SKILL.md | 4 +-
.../skills/vector-database-engineer/SKILL.md | 2 +
.../skills/vector-index-tuning/SKILL.md | 4 +-
.../public/skills/vercel-automation/SKILL.md | 5 +
.../skills/vercel-deploy-claimable/SKILL.md | 2 +-
.../verification-before-completion/SKILL.md | 7 +-
.../skills/viral-generator-builder/SKILL.md | 6 +-
web-app/public/skills/voice-agents/SKILL.md | 6 +-
.../skills/voice-ai-development/SKILL.md | 6 +-
.../voice-ai-engine-development/SKILL.md | 2 +
.../skills/vulnerability-scanner/SKILL.md | 7 +-
.../skills/wcag-audit-patterns/SKILL.md | 4 +-
.../skills/web-artifacts-builder/SKILL.md | 9 +-
.../skills/web-design-guidelines/SKILL.md | 7 +-
.../web-performance-optimization/SKILL.md | 2 +
.../skills/web-security-testing/SKILL.md | 184 +
web-app/public/skills/web3-testing/SKILL.md | 4 +-
web-app/public/skills/webapp-testing/SKILL.md | 9 +-
.../public/skills/webflow-automation/SKILL.md | 5 +
.../skills/whatsapp-automation/SKILL.md | 5 +
web-app/public/skills/wiki-architect/SKILL.md | 7 +-
web-app/public/skills/wiki-changelog/SKILL.md | 7 +-
.../public/skills/wiki-onboarding/SKILL.md | 7 +-
.../public/skills/wiki-page-writer/SKILL.md | 7 +-
web-app/public/skills/wiki-qa/SKILL.md | 7 +-
.../public/skills/wiki-researcher/SKILL.md | 7 +-
web-app/public/skills/wiki-vitepress/SKILL.md | 7 +-
.../windows-privilege-escalation/SKILL.md | 9 +-
.../public/skills/wireshark-analysis/SKILL.md | 9 +-
.../wordpress-penetration-testing/SKILL.md | 9 +-
.../wordpress-plugin-development/SKILL.md | 204 +
.../wordpress-theme-development/SKILL.md | 189 +
.../SKILL.md | 188 +
web-app/public/skills/wordpress/SKILL.md | 319 ++
.../public/skills/workflow- bundlesREADME.md | 185 +
.../skills/workflow-automation/SKILL.md | 6 +-
.../workflow-orchestration-patterns/SKILL.md | 4 +-
.../public/skills/workflow-patterns/SKILL.md | 4 +-
.../public/skills/workflow_bundles_readme.md | 185 +
.../public/skills/wrike-automation/SKILL.md | 5 +
web-app/public/skills/writing-plans/SKILL.md | 7 +-
web-app/public/skills/writing-skills/SKILL.md | 6 +-
.../anthropic-best-practices.md | 26 +-
.../public/skills/writing-skills/examples.md | 2 +-
.../public/skills/writing-skills/gotchas.md | 2 +-
.../references/standards/README.md | 4 +-
.../references/templates/reference.md | 4 +-
web-app/public/skills/xlsx-official/SKILL.md | 11 +-
.../public/skills/xss-html-injection/SKILL.md | 9 +-
.../public/skills/youtube-automation/SKILL.md | 5 +
.../skills/youtube-summarizer/README.md | 2 +-
.../public/skills/youtube-summarizer/SKILL.md | 1 +
.../skills/zapier-make-patterns/SKILL.md | 6 +-
.../public/skills/zendesk-automation/SKILL.md | 5 +
.../skills/zoho-crm-automation/SKILL.md | 5 +
.../public/skills/zoom-automation/SKILL.md | 5 +
.../public/skills/zustand-store-ts/SKILL.md | 9 +-
1092 files changed, 41407 insertions(+), 3566 deletions(-)
create mode 100644 web-app/public/skills/ai-agent-development/SKILL.md
create mode 100644 web-app/public/skills/ai-ml/SKILL.md
create mode 100644 web-app/public/skills/android-jetpack-compose-expert/SKILL.md
create mode 100644 web-app/public/skills/api-documentation/SKILL.md
create mode 100644 web-app/public/skills/api-security-testing/SKILL.md
create mode 100644 web-app/public/skills/aws-cost-cleanup/SKILL.md
create mode 100644 web-app/public/skills/aws-cost-optimizer/SKILL.md
create mode 100644 web-app/public/skills/bash-scripting/SKILL.md
create mode 100644 web-app/public/skills/bevy-ecs-expert/SKILL.md
create mode 100644 web-app/public/skills/cdk-patterns/SKILL.md
create mode 100644 web-app/public/skills/cloud-devops/SKILL.md
create mode 100644 web-app/public/skills/cloudformation-best-practices/SKILL.md
create mode 100644 web-app/public/skills/data-structure-protocol/SKILL.md
create mode 100644 web-app/public/skills/database/SKILL.md
create mode 100644 web-app/public/skills/ddd-context-mapping/SKILL.md
create mode 100644 web-app/public/skills/ddd-context-mapping/references/context-map-patterns.md
create mode 100644 web-app/public/skills/ddd-strategic-design/SKILL.md
create mode 100644 web-app/public/skills/ddd-strategic-design/references/strategic-design-template.md
create mode 100644 web-app/public/skills/ddd-tactical-patterns/SKILL.md
create mode 100644 web-app/public/skills/ddd-tactical-patterns/references/tactical-checklist.md
create mode 100644 web-app/public/skills/development/SKILL.md
create mode 100644 web-app/public/skills/documentation/SKILL.md
create mode 100644 web-app/public/skills/domain-driven-design/SKILL.md
create mode 100644 web-app/public/skills/domain-driven-design/references/ddd-deliverables.md
create mode 100644 web-app/public/skills/e2e-testing/SKILL.md
create mode 100644 web-app/public/skills/event-store-design/resources/implementation-playbook.md
create mode 100644 web-app/public/skills/godot-4-migration/SKILL.md
create mode 100644 web-app/public/skills/hig-components-content/SKILL.md
create mode 100644 web-app/public/skills/hig-components-content/references/activity-views.md
create mode 100644 web-app/public/skills/hig-components-content/references/charts.md
create mode 100644 web-app/public/skills/hig-components-content/references/collections.md
create mode 100644 web-app/public/skills/hig-components-content/references/color-wells.md
create mode 100644 web-app/public/skills/hig-components-content/references/image-views.md
create mode 100644 web-app/public/skills/hig-components-content/references/image-wells.md
create mode 100644 web-app/public/skills/hig-components-content/references/lockups.md
create mode 100644 web-app/public/skills/hig-components-content/references/web-views.md
create mode 100644 web-app/public/skills/hig-components-controls/SKILL.md
create mode 100644 web-app/public/skills/hig-components-controls/references/combo-boxes.md
create mode 100644 web-app/public/skills/hig-components-controls/references/controls.md
create mode 100644 web-app/public/skills/hig-components-controls/references/gauges.md
create mode 100644 web-app/public/skills/hig-components-controls/references/labels.md
create mode 100644 web-app/public/skills/hig-components-controls/references/pickers.md
create mode 100644 web-app/public/skills/hig-components-controls/references/rating-indicators.md
create mode 100644 web-app/public/skills/hig-components-controls/references/segmented-controls.md
create mode 100644 web-app/public/skills/hig-components-controls/references/sliders.md
create mode 100644 web-app/public/skills/hig-components-controls/references/steppers.md
create mode 100644 web-app/public/skills/hig-components-controls/references/text-fields.md
create mode 100644 web-app/public/skills/hig-components-controls/references/text-views.md
create mode 100644 web-app/public/skills/hig-components-controls/references/toggles.md
create mode 100644 web-app/public/skills/hig-components-controls/references/token-fields.md
create mode 100644 web-app/public/skills/hig-components-controls/references/virtual-keyboards.md
create mode 100644 web-app/public/skills/hig-components-dialogs/SKILL.md
create mode 100644 web-app/public/skills/hig-components-dialogs/references/action-sheets.md
create mode 100644 web-app/public/skills/hig-components-dialogs/references/alerts.md
create mode 100644 web-app/public/skills/hig-components-dialogs/references/digit-entry-views.md
create mode 100644 web-app/public/skills/hig-components-dialogs/references/popovers.md
create mode 100644 web-app/public/skills/hig-components-dialogs/references/sheets.md
create mode 100644 web-app/public/skills/hig-components-layout/SKILL.md
create mode 100644 web-app/public/skills/hig-components-layout/references/boxes.md
create mode 100644 web-app/public/skills/hig-components-layout/references/column-views.md
create mode 100644 web-app/public/skills/hig-components-layout/references/lists-and-tables.md
create mode 100644 web-app/public/skills/hig-components-layout/references/ornaments.md
create mode 100644 web-app/public/skills/hig-components-layout/references/outline-views.md
create mode 100644 web-app/public/skills/hig-components-layout/references/panels.md
create mode 100644 web-app/public/skills/hig-components-layout/references/scroll-views.md
create mode 100644 web-app/public/skills/hig-components-layout/references/sidebars.md
create mode 100644 web-app/public/skills/hig-components-layout/references/split-views.md
create mode 100644 web-app/public/skills/hig-components-layout/references/tab-bars.md
create mode 100644 web-app/public/skills/hig-components-layout/references/tab-views.md
create mode 100644 web-app/public/skills/hig-components-layout/references/windows.md
create mode 100644 web-app/public/skills/hig-components-menus/SKILL.md
create mode 100644 web-app/public/skills/hig-components-menus/references/action-button.md
create mode 100644 web-app/public/skills/hig-components-menus/references/buttons.md
create mode 100644 web-app/public/skills/hig-components-menus/references/context-menus.md
create mode 100644 web-app/public/skills/hig-components-menus/references/disclosure-controls.md
create mode 100644 web-app/public/skills/hig-components-menus/references/dock-menus.md
create mode 100644 web-app/public/skills/hig-components-menus/references/edit-menus.md
create mode 100644 web-app/public/skills/hig-components-menus/references/menus.md
create mode 100644 web-app/public/skills/hig-components-menus/references/pop-up-buttons.md
create mode 100644 web-app/public/skills/hig-components-menus/references/pull-down-buttons.md
create mode 100644 web-app/public/skills/hig-components-menus/references/the-menu-bar.md
create mode 100644 web-app/public/skills/hig-components-menus/references/toolbars.md
create mode 100644 web-app/public/skills/hig-components-search/SKILL.md
create mode 100644 web-app/public/skills/hig-components-search/references/page-controls.md
create mode 100644 web-app/public/skills/hig-components-search/references/path-controls.md
create mode 100644 web-app/public/skills/hig-components-search/references/search-fields.md
create mode 100644 web-app/public/skills/hig-components-status/SKILL.md
create mode 100644 web-app/public/skills/hig-components-status/references/activity-rings.md
create mode 100644 web-app/public/skills/hig-components-status/references/progress-indicators.md
create mode 100644 web-app/public/skills/hig-components-status/references/status-bars.md
create mode 100644 web-app/public/skills/hig-components-system/SKILL.md
create mode 100644 web-app/public/skills/hig-components-system/references/app-clips.md
create mode 100644 web-app/public/skills/hig-components-system/references/app-shortcuts.md
create mode 100644 web-app/public/skills/hig-components-system/references/complications.md
create mode 100644 web-app/public/skills/hig-components-system/references/home-screen-quick-actions.md
create mode 100644 web-app/public/skills/hig-components-system/references/live-activities.md
create mode 100644 web-app/public/skills/hig-components-system/references/notifications.md
create mode 100644 web-app/public/skills/hig-components-system/references/top-shelf.md
create mode 100644 web-app/public/skills/hig-components-system/references/watch-faces.md
create mode 100644 web-app/public/skills/hig-components-system/references/widgets.md
create mode 100644 web-app/public/skills/hig-foundations/SKILL.md
create mode 100644 web-app/public/skills/hig-foundations/references/accessibility.md
create mode 100644 web-app/public/skills/hig-foundations/references/app-icons.md
create mode 100644 web-app/public/skills/hig-foundations/references/branding.md
create mode 100644 web-app/public/skills/hig-foundations/references/color.md
create mode 100644 web-app/public/skills/hig-foundations/references/dark-mode.md
create mode 100644 web-app/public/skills/hig-foundations/references/icons.md
create mode 100644 web-app/public/skills/hig-foundations/references/images.md
create mode 100644 web-app/public/skills/hig-foundations/references/immersive-experiences.md
create mode 100644 web-app/public/skills/hig-foundations/references/inclusion.md
create mode 100644 web-app/public/skills/hig-foundations/references/layout.md
create mode 100644 web-app/public/skills/hig-foundations/references/materials.md
create mode 100644 web-app/public/skills/hig-foundations/references/motion.md
create mode 100644 web-app/public/skills/hig-foundations/references/privacy.md
create mode 100644 web-app/public/skills/hig-foundations/references/right-to-left.md
create mode 100644 web-app/public/skills/hig-foundations/references/sf-symbols.md
create mode 100644 web-app/public/skills/hig-foundations/references/spatial-layout.md
create mode 100644 web-app/public/skills/hig-foundations/references/typography.md
create mode 100644 web-app/public/skills/hig-foundations/references/writing.md
create mode 100644 web-app/public/skills/hig-inputs/SKILL.md
create mode 100644 web-app/public/skills/hig-inputs/references/apple-pencil-and-scribble.md
create mode 100644 web-app/public/skills/hig-inputs/references/camera-control.md
create mode 100644 web-app/public/skills/hig-inputs/references/digital-crown.md
create mode 100644 web-app/public/skills/hig-inputs/references/eyes.md
create mode 100644 web-app/public/skills/hig-inputs/references/focus-and-selection.md
create mode 100644 web-app/public/skills/hig-inputs/references/game-controls.md
create mode 100644 web-app/public/skills/hig-inputs/references/gestures.md
create mode 100644 web-app/public/skills/hig-inputs/references/gyro-and-accelerometer.md
create mode 100644 web-app/public/skills/hig-inputs/references/keyboards.md
create mode 100644 web-app/public/skills/hig-inputs/references/nearby-interactions.md
create mode 100644 web-app/public/skills/hig-inputs/references/pointing-devices.md
create mode 100644 web-app/public/skills/hig-inputs/references/remotes.md
create mode 100644 web-app/public/skills/hig-inputs/references/spatial-interactions.md
create mode 100644 web-app/public/skills/hig-patterns/SKILL.md
create mode 100644 web-app/public/skills/hig-patterns/references/charting-data.md
create mode 100644 web-app/public/skills/hig-patterns/references/collaboration-and-sharing.md
create mode 100644 web-app/public/skills/hig-patterns/references/drag-and-drop.md
create mode 100644 web-app/public/skills/hig-patterns/references/entering-data.md
create mode 100644 web-app/public/skills/hig-patterns/references/feedback.md
create mode 100644 web-app/public/skills/hig-patterns/references/file-management.md
create mode 100644 web-app/public/skills/hig-patterns/references/going-full-screen.md
create mode 100644 web-app/public/skills/hig-patterns/references/launching.md
create mode 100644 web-app/public/skills/hig-patterns/references/live-viewing-apps.md
create mode 100644 web-app/public/skills/hig-patterns/references/loading.md
create mode 100644 web-app/public/skills/hig-patterns/references/managing-accounts.md
create mode 100644 web-app/public/skills/hig-patterns/references/managing-notifications.md
create mode 100644 web-app/public/skills/hig-patterns/references/modality.md
create mode 100644 web-app/public/skills/hig-patterns/references/multitasking.md
create mode 100644 web-app/public/skills/hig-patterns/references/offering-help.md
create mode 100644 web-app/public/skills/hig-patterns/references/onboarding.md
create mode 100644 web-app/public/skills/hig-patterns/references/playing-audio.md
create mode 100644 web-app/public/skills/hig-patterns/references/playing-haptics.md
create mode 100644 web-app/public/skills/hig-patterns/references/playing-video.md
create mode 100644 web-app/public/skills/hig-patterns/references/printing.md
create mode 100644 web-app/public/skills/hig-patterns/references/ratings-and-reviews.md
create mode 100644 web-app/public/skills/hig-patterns/references/searching.md
create mode 100644 web-app/public/skills/hig-patterns/references/settings.md
create mode 100644 web-app/public/skills/hig-patterns/references/undo-and-redo.md
create mode 100644 web-app/public/skills/hig-patterns/references/workouts.md
create mode 100644 web-app/public/skills/hig-platforms/SKILL.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-games.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-ios.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-ipados.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-macos.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-tvos.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-visionos.md
create mode 100644 web-app/public/skills/hig-platforms/references/designing-for-watchos.md
create mode 100644 web-app/public/skills/hig-project-context/SKILL.md
create mode 100644 web-app/public/skills/hig-technologies/SKILL.md
create mode 100644 web-app/public/skills/hig-technologies/references/airplay.md
create mode 100644 web-app/public/skills/hig-technologies/references/always-on.md
create mode 100644 web-app/public/skills/hig-technologies/references/apple-pay.md
create mode 100644 web-app/public/skills/hig-technologies/references/augmented-reality.md
create mode 100644 web-app/public/skills/hig-technologies/references/carekit.md
create mode 100644 web-app/public/skills/hig-technologies/references/carplay.md
create mode 100644 web-app/public/skills/hig-technologies/references/game-center.md
create mode 100644 web-app/public/skills/hig-technologies/references/generative-ai.md
create mode 100644 web-app/public/skills/hig-technologies/references/healthkit.md
create mode 100644 web-app/public/skills/hig-technologies/references/homekit.md
create mode 100644 web-app/public/skills/hig-technologies/references/icloud.md
create mode 100644 web-app/public/skills/hig-technologies/references/id-verifier.md
create mode 100644 web-app/public/skills/hig-technologies/references/imessage-apps-and-stickers.md
create mode 100644 web-app/public/skills/hig-technologies/references/in-app-purchase.md
create mode 100644 web-app/public/skills/hig-technologies/references/live-photos.md
create mode 100644 web-app/public/skills/hig-technologies/references/mac-catalyst.md
create mode 100644 web-app/public/skills/hig-technologies/references/machine-learning.md
create mode 100644 web-app/public/skills/hig-technologies/references/maps.md
create mode 100644 web-app/public/skills/hig-technologies/references/nfc.md
create mode 100644 web-app/public/skills/hig-technologies/references/photo-editing.md
create mode 100644 web-app/public/skills/hig-technologies/references/researchkit.md
create mode 100644 web-app/public/skills/hig-technologies/references/shareplay.md
create mode 100644 web-app/public/skills/hig-technologies/references/shazamkit.md
create mode 100644 web-app/public/skills/hig-technologies/references/sign-in-with-apple.md
create mode 100644 web-app/public/skills/hig-technologies/references/siri.md
create mode 100644 web-app/public/skills/hig-technologies/references/tap-to-pay-on-iphone.md
create mode 100644 web-app/public/skills/hig-technologies/references/voiceover.md
create mode 100644 web-app/public/skills/hig-technologies/references/wallet.md
create mode 100644 web-app/public/skills/kotlin-coroutines-expert/SKILL.md
create mode 100644 web-app/public/skills/kubernetes-deployment/SKILL.md
create mode 100644 web-app/public/skills/libreoffice/base/SKILL.md
create mode 100644 web-app/public/skills/libreoffice/calc/SKILL.md
create mode 100644 web-app/public/skills/libreoffice/draw/SKILL.md
create mode 100644 web-app/public/skills/libreoffice/impress/SKILL.md
create mode 100644 web-app/public/skills/libreoffice/writer/SKILL.md
create mode 100644 web-app/public/skills/linux-troubleshooting/SKILL.md
create mode 100644 web-app/public/skills/manifest/SKILL.md
create mode 100644 web-app/public/skills/nerdzao-elite-gemini-high/SKILL.md
create mode 100644 web-app/public/skills/nerdzao-elite/SKILL.md
create mode 100644 web-app/public/skills/office-productivity/SKILL.md
create mode 100644 web-app/public/skills/os-scripting/SKILL.md
create mode 100644 web-app/public/skills/postgresql-optimization/SKILL.md
create mode 100644 web-app/public/skills/python-fastapi-development/SKILL.md
create mode 100644 web-app/public/skills/react-nextjs-development/SKILL.md
create mode 100644 web-app/public/skills/saga-orchestration/resources/implementation-playbook.md
create mode 100644 web-app/public/skills/security-audit/SKILL.md
create mode 100644 web-app/public/skills/security/aws-compliance-checker/SKILL.md
create mode 100644 web-app/public/skills/security/aws-iam-best-practices/SKILL.md
create mode 100644 web-app/public/skills/security/aws-secrets-rotation/SKILL.md
create mode 100644 web-app/public/skills/security/aws-security-audit/SKILL.md
create mode 100644 web-app/public/skills/shader-programming-glsl/SKILL.md
create mode 100644 web-app/public/skills/terraform-aws-modules/SKILL.md
create mode 100644 web-app/public/skills/terraform-infrastructure/SKILL.md
create mode 100644 web-app/public/skills/testing-qa/SKILL.md
create mode 100644 web-app/public/skills/web-security-testing/SKILL.md
create mode 100644 web-app/public/skills/wordpress-plugin-development/SKILL.md
create mode 100644 web-app/public/skills/wordpress-theme-development/SKILL.md
create mode 100644 web-app/public/skills/wordpress-woocommerce-development/SKILL.md
create mode 100644 web-app/public/skills/wordpress/SKILL.md
create mode 100644 web-app/public/skills/workflow- bundlesREADME.md
create mode 100644 web-app/public/skills/workflow_bundles_readme.md
diff --git a/START_APP.bat b/START_APP.bat
index d7669c7a..85a78ffe 100644
--- a/START_APP.bat
+++ b/START_APP.bat
@@ -14,19 +14,74 @@ IF %ERRORLEVEL% NEQ 0 (
exit /b 1
)
+:: ===== Auto-Update Skills from GitHub =====
+WHERE git >nul 2>nul
+IF %ERRORLEVEL% NEQ 0 goto :NO_GIT
+goto :HAS_GIT
+
+:NO_GIT
+echo [WARN] Git is not installed. Skipping auto-update.
+goto :SKIP_UPDATE
+
+:HAS_GIT
+:: Add upstream remote if not already set
+git remote get-url upstream >nul 2>nul
+IF %ERRORLEVEL% EQU 0 goto :DO_FETCH
+echo [INFO] Adding upstream remote...
+git remote add upstream https://github.com/sickn33/antigravity-awesome-skills.git
+
+:DO_FETCH
+echo [INFO] Checking for skill updates from original repo...
+git fetch upstream >nul 2>nul
+IF %ERRORLEVEL% NEQ 0 goto :FETCH_FAIL
+goto :DO_MERGE
+
+:FETCH_FAIL
+echo [WARN] Could not fetch updates. Continuing with local version...
+goto :SKIP_UPDATE
+
+:DO_MERGE
+git merge upstream/main --ff-only >nul 2>nul
+IF %ERRORLEVEL% NEQ 0 goto :MERGE_FAIL
+echo [INFO] Skills updated successfully from original repo!
+goto :SKIP_UPDATE
+
+:MERGE_FAIL
+echo [WARN] Could not merge updates. Continuing with local version...
+
+:SKIP_UPDATE
+
:: Check/Install dependencies
-if not exist "web-app\node_modules" (
- echo [INFO] First time run detected. Installing dependencies...
- cd web-app
- call npm install
- if %ERRORLEVEL% NEQ 0 (
- echo [ERROR] Failed to install dependencies.
- pause
- exit /b 1
- )
- cd ..
+cd web-app
+
+:CHECK_DEPS
+if not exist "node_modules\" (
+ echo [INFO] Dependencies not found. Installing...
+ goto :INSTALL_DEPS
)
+:: Verify dependencies aren't corrupted (e.g. esbuild arch mismatch after update)
+echo [INFO] Verifying app dependencies...
+call npx -y vite --version >nul 2>nul
+if %ERRORLEVEL% NEQ 0 (
+ echo [WARN] Dependencies appear corrupted or outdated.
+ echo [INFO] Cleaning up and reinstalling fresh dependencies...
+ rmdir /s /q "node_modules" >nul 2>nul
+ goto :INSTALL_DEPS
+)
+goto :DEPS_OK
+
+:INSTALL_DEPS
+call npm install
+if %ERRORLEVEL% NEQ 0 (
+ echo [ERROR] Failed to install dependencies. Please check your internet connection.
+ pause
+ exit /b 1
+)
+
+:DEPS_OK
+cd ..
+
:: Run setup script
echo [INFO] Updating skills data...
call npm run app:setup
@@ -35,6 +90,6 @@ call npm run app:setup
echo [INFO] Starting Web App...
echo [INFO] Opening default browser...
cd web-app
-call npx vite --open
+call npx -y vite --open
endlocal
diff --git a/web-app/public/skills.json b/web-app/public/skills.json
index a6475cc5..10357d7e 100644
--- a/web-app/public/skills.json
+++ b/web-app/public/skills.json
@@ -6,7 +6,7 @@
"name": "2d-games",
"description": "2D game development principles. Sprites, tilemaps, physics, camera.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "3d-games",
@@ -15,14 +15,14 @@
"name": "3d-games",
"description": "3D game development principles. Rendering, shaders, physics, cameras.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "3d-web-experience",
"path": "skills/3d-web-experience",
"category": "uncategorized",
"name": "3d-web-experience",
- "description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.",
+ "description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -33,7 +33,7 @@
"name": "ab-test-setup",
"description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "accessibility-compliance-accessibility-audit",
@@ -42,16 +42,16 @@
"name": "accessibility-compliance-accessibility-audit",
"description": "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "active-directory-attacks",
"path": "skills/active-directory-attacks",
"category": "uncategorized",
- "name": "Active Directory Attacks",
- "description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", \"Silver Ticket\", \"AS-REP roasting\", \"NTLM relay\", or needs guidance on Windows domain penetration testing.",
+ "name": "active-directory-attacks",
+ "description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "activecampaign-automation",
@@ -60,7 +60,7 @@
"name": "activecampaign-automation",
"description": "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "address-github-comments",
@@ -69,14 +69,14 @@
"name": "address-github-comments",
"description": "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-evaluation",
"path": "skills/agent-evaluation",
"category": "uncategorized",
"name": "agent-evaluation",
- "description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.",
+ "description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -85,9 +85,9 @@
"path": "skills/agent-framework-azure-ai-py",
"category": "uncategorized",
"name": "agent-framework-azure-ai-py",
- "description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code interpreter, file search, web search), integrating MCP servers, managing conversation threads, or implementing streaming responses. Covers function tools, structured outputs, and multi-tool agents.",
+ "description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-manager-skill",
@@ -96,7 +96,7 @@
"name": "agent-manager-skill",
"description": "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-memory-mcp",
@@ -105,14 +105,14 @@
"name": "agent-memory-mcp",
"description": "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-memory-systems",
"path": "skills/agent-memory-systems",
"category": "uncategorized",
"name": "agent-memory-systems",
- "description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm",
+ "description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -123,7 +123,7 @@
"name": "agent-orchestration-improve-agent",
"description": "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-orchestration-multi-agent-optimize",
@@ -132,14 +132,14 @@
"name": "agent-orchestration-multi-agent-optimize",
"description": "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "agent-tool-builder",
"path": "skills/agent-tool-builder",
"category": "uncategorized",
"name": "agent-tool-builder",
- "description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa",
+ "description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -148,34 +148,52 @@
"path": "skills/agents-v2-py",
"category": "uncategorized",
"name": "agents-v2-py",
- "description": "Build container-based Foundry Agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition.\nUse when creating hosted agents that run custom code in Azure AI Foundry with your own container images.\nTriggers: \"ImageBasedHostedAgentDefinition\", \"hosted agent\", \"container agent\", \"Foundry Agent\",\n\"create_version\", \"ProtocolVersionRecord\", \"AgentProtocol.RESPONSES\", \"custom agent image\".\n",
+ "description": "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "ai-engineer",
+ "path": "skills/ai-engineer",
+ "category": "uncategorized",
+ "name": "Ai Engineer",
+ "description": "You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "ai-agent-development",
+ "path": "skills/ai-agent-development",
+ "category": "uncategorized",
+ "name": "ai-agent-development",
+ "description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "ai-agents-architect",
"path": "skills/ai-agents-architect",
"category": "uncategorized",
"name": "ai-agents-architect",
- "description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool use, function calling.",
+ "description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
{
- "id": "ai-engineer",
- "path": "skills/ai-engineer",
+ "id": "ai-ml",
+ "path": "skills/ai-ml",
"category": "uncategorized",
- "name": "ai-engineer",
- "description": "Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM features, chatbots, AI agents, or AI-powered applications.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "ai-ml",
+ "description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "ai-product",
"path": "skills/ai-product",
"category": "uncategorized",
"name": "ai-product",
- "description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt engineering that scales, AI UX that users trust, and cost optimization that doesn't bankrupt you. Use when: keywords, file_patterns, code_patterns.",
+ "description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -184,7 +202,7 @@
"path": "skills/ai-wrapper-product",
"category": "uncategorized",
"name": "ai-wrapper-product",
- "description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Covers prompt engineering for products, cost management, rate limiting, and building defensible AI businesses. Use when: AI wrapper, GPT product, AI tool, wrap AI, AI SaaS.",
+ "description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -195,7 +213,7 @@
"name": "airflow-dag-patterns",
"description": "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "airtable-automation",
@@ -204,7 +222,7 @@
"name": "airtable-automation",
"description": "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "algolia-search",
@@ -220,9 +238,9 @@
"path": "skills/algorithmic-art",
"category": "uncategorized",
"name": "algorithmic-art",
- "description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",
+ "description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "amplitude-automation",
@@ -231,25 +249,34 @@
"name": "amplitude-automation",
"description": "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "analytics-tracking",
"path": "skills/analytics-tracking",
"category": "uncategorized",
- "name": "analytics-tracking",
- "description": "Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation\u2014 not just firing events.",
+ "name": "Analytics Tracking",
+ "description": "You are an expert in **analytics implementation and measurement design**. Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "android-jetpack-compose-expert",
+ "path": "skills/android-jetpack-compose-expert",
+ "category": "uncategorized",
+ "name": "android-jetpack-compose-expert",
+ "description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "angular",
"path": "skills/angular",
"category": "uncategorized",
- "name": "angular",
- "description": "Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.",
- "risk": "safe",
- "source": "self"
+ "name": "Angular",
+ "description": "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration, and the latest reactive patterns.",
+ "risk": "unknown",
+ "source": "unknown"
},
{
"id": "angular-best-practices",
@@ -265,9 +292,9 @@
"path": "skills/angular-migration",
"category": "uncategorized",
"name": "angular-migration",
- "description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.",
+ "description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "angular-state-management",
@@ -292,9 +319,9 @@
"path": "skills/anti-reversing-techniques",
"category": "uncategorized",
"name": "anti-reversing-techniques",
- "description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.",
+ "description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "antigravity-workflows",
@@ -306,11 +333,11 @@
"source": "self"
},
{
- "id": "api-fuzzing-bug-bounty",
- "path": "skills/api-fuzzing-bug-bounty",
+ "id": "api-documenter",
+ "path": "skills/api-documenter",
"category": "uncategorized",
- "name": "API Fuzzing for Bug Bounty",
- "description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug bounty API testing\", or needs guidance on API security assessment techniques.",
+ "name": "Api Documenter",
+ "description": "You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.",
"risk": "unknown",
"source": "unknown"
},
@@ -319,9 +346,18 @@
"path": "skills/api-design-principles",
"category": "uncategorized",
"name": "api-design-principles",
- "description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.",
+ "description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "api-documentation",
+ "path": "skills/api-documentation",
+ "category": "uncategorized",
+ "name": "api-documentation",
+ "description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "api-documentation-generator",
@@ -330,16 +366,16 @@
"name": "api-documentation-generator",
"description": "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
- "id": "api-documenter",
- "path": "skills/api-documenter",
+ "id": "api-fuzzing-bug-bounty",
+ "path": "skills/api-fuzzing-bug-bounty",
"category": "uncategorized",
- "name": "api-documenter",
- "description": "Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.",
+ "name": "api-fuzzing-bug-bounty",
+ "description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "api-patterns",
@@ -348,7 +384,7 @@
"name": "api-patterns",
"description": "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "api-security-best-practices",
@@ -357,7 +393,16 @@
"name": "api-security-best-practices",
"description": "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "api-security-testing",
+ "path": "skills/api-security-testing",
+ "category": "uncategorized",
+ "name": "api-security-testing",
+ "description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "api-testing-observability-api-mock",
@@ -366,7 +411,7 @@
"name": "api-testing-observability-api-mock",
"description": "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "app-builder",
@@ -375,7 +420,7 @@
"name": "app-builder",
"description": "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "app-store-optimization",
@@ -384,7 +429,7 @@
"name": "app-store-optimization",
"description": "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "application-performance-performance-optimization",
@@ -393,7 +438,7 @@
"name": "application-performance-performance-optimization",
"description": "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "architect-review",
@@ -402,7 +447,7 @@
"name": "architect-review",
"description": "Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "architecture",
@@ -411,32 +456,32 @@
"name": "architecture",
"description": "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "architecture-decision-records",
"path": "skills/architecture-decision-records",
"category": "uncategorized",
"name": "architecture-decision-records",
- "description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.",
+ "description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "architecture-patterns",
"path": "skills/architecture-patterns",
"category": "uncategorized",
"name": "architecture-patterns",
- "description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.",
+ "description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "arm-cortex-expert",
"path": "skills/arm-cortex-expert",
"category": "uncategorized",
- "name": "arm-cortex-expert",
- "description": "Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.\n",
+ "name": "Arm Cortex Expert",
+ "description": "- Working on @arm-cortex-expert tasks or workflows - Needing guidance, best practices, or checklists for @arm-cortex-expert",
"risk": "unknown",
"source": "unknown"
},
@@ -447,16 +492,16 @@
"name": "asana-automation",
"description": "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "async-python-patterns",
"path": "skills/async-python-patterns",
"category": "uncategorized",
"name": "async-python-patterns",
- "description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.",
+ "description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "attack-tree-construction",
@@ -465,7 +510,7 @@
"name": "attack-tree-construction",
"description": "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "audio-transcriber",
@@ -474,23 +519,23 @@
"name": "audio-transcriber",
"description": "Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration",
"risk": "safe",
- "source": "unknown"
+ "source": "community"
},
{
"id": "auth-implementation-patterns",
"path": "skills/auth-implementation-patterns",
"category": "uncategorized",
"name": "auth-implementation-patterns",
- "description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.",
+ "description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "automate-whatsapp",
"path": "skills/automate-whatsapp",
"category": "uncategorized",
"name": "automate-whatsapp",
- "description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automating WhatsApp conversations and event handling.",
+ "description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...",
"risk": "safe",
"source": "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp"
},
@@ -499,16 +544,16 @@
"path": "skills/autonomous-agent-patterns",
"category": "uncategorized",
"name": "autonomous-agent-patterns",
- "description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.",
+ "description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "autonomous-agents",
"path": "skills/autonomous-agents",
"category": "uncategorized",
"name": "autonomous-agents",
- "description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability. This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability. Key insight: compounding error rates kill autonomous agents. A 95% success rate per step drops to 60% b",
+ "description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -519,7 +564,7 @@
"name": "avalonia-layout-zafiro",
"description": "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "avalonia-viewmodels-zafiro",
@@ -528,7 +573,7 @@
"name": "avalonia-viewmodels-zafiro",
"description": "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "avalonia-zafiro-development",
@@ -537,23 +582,77 @@
"name": "avalonia-zafiro-development",
"description": "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "aws-compliance-checker",
+ "path": "skills/security/aws-compliance-checker",
+ "category": "security",
+ "name": "aws-compliance-checker",
+ "description": "Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks",
+ "risk": "safe",
+ "source": "community"
+ },
+ {
+ "id": "aws-cost-cleanup",
+ "path": "skills/aws-cost-cleanup",
+ "category": "uncategorized",
+ "name": "aws-cost-cleanup",
+ "description": "Automated cleanup of unused AWS resources to reduce costs",
+ "risk": "safe",
+ "source": "community"
+ },
+ {
+ "id": "aws-cost-optimizer",
+ "path": "skills/aws-cost-optimizer",
+ "category": "uncategorized",
+ "name": "aws-cost-optimizer",
+ "description": "Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer",
+ "risk": "safe",
+ "source": "community"
+ },
+ {
+ "id": "aws-iam-best-practices",
+ "path": "skills/security/aws-iam-best-practices",
+ "category": "security",
+ "name": "aws-iam-best-practices",
+ "description": "IAM policy review, hardening, and least privilege implementation",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "aws-penetration-testing",
"path": "skills/aws-penetration-testing",
"category": "uncategorized",
- "name": "AWS Penetration Testing",
- "description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing\", \"metadata SSRF\", \"Lambda exploitation\", or needs guidance on Amazon Web Services security assessment.",
+ "name": "aws-penetration-testing",
+ "description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "aws-secrets-rotation",
+ "path": "skills/security/aws-secrets-rotation",
+ "category": "security",
+ "name": "aws-secrets-rotation",
+ "description": "Automate AWS secrets rotation for RDS, API keys, and credentials",
+ "risk": "safe",
+ "source": "community"
+ },
+ {
+ "id": "aws-security-audit",
+ "path": "skills/security/aws-security-audit",
+ "category": "security",
+ "name": "aws-security-audit",
+ "description": "Comprehensive AWS security posture assessment using AWS CLI and security best practices",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "aws-serverless",
"path": "skills/aws-serverless",
"category": "uncategorized",
"name": "aws-serverless",
- "description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization.",
+ "description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -571,16 +670,16 @@
"path": "skills/azd-deployment",
"category": "uncategorized",
"name": "azd-deployment",
- "description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Container Apps, configuring remote builds with ACR, implementing idempotent deployments, managing environment variables across local/.azure/Bicep, or troubleshooting azd up failures. Triggers on requests for azd configuration, Container Apps deployment, multi-service deployments, and infrastructure-as-code with Bicep.",
+ "description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-agents-persistent-dotnet",
"path": "skills/azure-ai-agents-persistent-dotnet",
"category": "uncategorized",
- "name": "azure-ai-agents-persistent-dotnet",
- "description": "Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: \"PersistentAgentsClient\", \"persistent agents\", \"agent threads\", \"agent runs\", \"streaming agents\", \"function calling agents .NET\".\n",
+ "name": "Azure Ai Agents Persistent Dotnet",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
"risk": "unknown",
"source": "unknown"
},
@@ -588,8 +687,710 @@
"id": "azure-ai-agents-persistent-java",
"path": "skills/azure-ai-agents-persistent-java",
"category": "uncategorized",
- "name": "azure-ai-agents-persistent-java",
- "description": "Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.\nTriggers: \"PersistentAgentsClient\", \"persistent agents java\", \"agent threads java\", \"agent runs java\", \"streaming agents java\".\n",
+ "name": "Azure Ai Agents Persistent Java",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-contentsafety-py",
+ "path": "skills/azure-ai-contentsafety-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Contentsafety Py",
+ "description": "Detect harmful user-generated and AI-generated content in applications.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-contentunderstanding-py",
+ "path": "skills/azure-ai-contentunderstanding-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Contentunderstanding Py",
+ "description": "Multimodal AI service that extracts semantic content from documents, video, audio, and image files for RAG and automated workflows.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-document-intelligence-dotnet",
+ "path": "skills/azure-ai-document-intelligence-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Ai Document Intelligence Dotnet",
+ "description": "Extract text, tables, and structured data from documents using prebuilt and custom models.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-ml-py",
+ "path": "skills/azure-ai-ml-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Ml Py",
+ "description": "Client library for managing Azure ML resources: workspaces, jobs, models, data, and compute.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-openai-dotnet",
+ "path": "skills/azure-ai-openai-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Ai Openai Dotnet",
+ "description": "Client library for Azure OpenAI Service providing access to OpenAI models including GPT-4, GPT-4o, embeddings, DALL-E, and Whisper.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-projects-dotnet",
+ "path": "skills/azure-ai-projects-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Ai Projects Dotnet",
+ "description": "High-level SDK for Azure AI Foundry project operations including agents, connections, datasets, deployments, evaluations, and indexes.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-projects-java",
+ "path": "skills/azure-ai-projects-java",
+ "category": "uncategorized",
+ "name": "Azure Ai Projects Java",
+ "description": "High-level SDK for Azure AI Foundry project management with access to connections, datasets, indexes, and evaluations.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-textanalytics-py",
+ "path": "skills/azure-ai-textanalytics-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Textanalytics Py",
+ "description": "Client library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-transcription-py",
+ "path": "skills/azure-ai-transcription-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Transcription Py",
+ "description": "Client library for Azure AI Transcription (speech-to-text) with real-time and batch transcription.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-translation-document-py",
+ "path": "skills/azure-ai-translation-document-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Translation Document Py",
+ "description": "Client library for Azure AI Translator document translation service for batch document translation with format preservation.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-translation-text-py",
+ "path": "skills/azure-ai-translation-text-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Translation Text Py",
+ "description": "Client library for Azure AI Translator text translation service for real-time text translation, transliteration, and language operations.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-vision-imageanalysis-py",
+ "path": "skills/azure-ai-vision-imageanalysis-py",
+ "category": "uncategorized",
+ "name": "Azure Ai Vision Imageanalysis Py",
+ "description": "Client library for Azure AI Vision 4.0 image analysis including captions, tags, objects, OCR, and more.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-voicelive-dotnet",
+ "path": "skills/azure-ai-voicelive-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Ai Voicelive Dotnet",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-voicelive-java",
+ "path": "skills/azure-ai-voicelive-java",
+ "category": "uncategorized",
+ "name": "Azure Ai Voicelive Java",
+ "description": "Real-time, bidirectional voice conversations with AI assistants using WebSocket technology.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-ai-voicelive-ts",
+ "path": "skills/azure-ai-voicelive-ts",
+ "category": "uncategorized",
+ "name": "Azure Ai Voicelive Ts",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI in Node.js and browser environments.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-appconfiguration-java",
+ "path": "skills/azure-appconfiguration-java",
+ "category": "uncategorized",
+ "name": "Azure Appconfiguration Java",
+ "description": "Client library for Azure App Configuration, a managed service for centralizing application configurations.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-appconfiguration-py",
+ "path": "skills/azure-appconfiguration-py",
+ "category": "uncategorized",
+ "name": "Azure Appconfiguration Py",
+ "description": "Centralized configuration management with feature flags and dynamic settings.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-compute-batch-java",
+ "path": "skills/azure-compute-batch-java",
+ "category": "uncategorized",
+ "name": "Azure Compute Batch Java",
+ "description": "Client library for running large-scale parallel and high-performance computing (HPC) batch jobs in Azure.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-containerregistry-py",
+ "path": "skills/azure-containerregistry-py",
+ "category": "uncategorized",
+ "name": "Azure Containerregistry Py",
+ "description": "Manage container images, artifacts, and repositories in Azure Container Registry.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-cosmos-java",
+ "path": "skills/azure-cosmos-java",
+ "category": "uncategorized",
+ "name": "Azure Cosmos Java",
+ "description": "Client library for Azure Cosmos DB NoSQL API with global distribution and reactive patterns.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-cosmos-py",
+ "path": "skills/azure-cosmos-py",
+ "category": "uncategorized",
+ "name": "Azure Cosmos Py",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-cosmos-rust",
+ "path": "skills/azure-cosmos-rust",
+ "category": "uncategorized",
+ "name": "Azure Cosmos Rust",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-cosmos-ts",
+ "path": "skills/azure-cosmos-ts",
+ "category": "uncategorized",
+ "name": "Azure Cosmos Ts",
+ "description": "Data plane SDK for Azure Cosmos DB NoSQL API operations \u2014 CRUD on documents, queries, bulk operations.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-data-tables-py",
+ "path": "skills/azure-data-tables-py",
+ "category": "uncategorized",
+ "name": "Azure Data Tables Py",
+ "description": "NoSQL key-value store for structured data (Azure Storage Tables or Cosmos DB Table API).",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-eventgrid-dotnet",
+ "path": "skills/azure-eventgrid-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Eventgrid Dotnet",
+ "description": "Client library for publishing events to Azure Event Grid topics, domains, and namespaces.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-eventgrid-py",
+ "path": "skills/azure-eventgrid-py",
+ "category": "uncategorized",
+ "name": "Azure Eventgrid Py",
+ "description": "Event routing service for building event-driven applications with pub/sub semantics.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-eventhub-dotnet",
+ "path": "skills/azure-eventhub-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Eventhub Dotnet",
+ "description": "High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-eventhub-py",
+ "path": "skills/azure-eventhub-py",
+ "category": "uncategorized",
+ "name": "Azure Eventhub Py",
+ "description": "Big data streaming platform for high-throughput event ingestion.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-eventhub-rust",
+ "path": "skills/azure-eventhub-rust",
+ "category": "uncategorized",
+ "name": "Azure Eventhub Rust",
+ "description": "Client library for Azure Event Hubs \u2014 big data streaming platform and event ingestion service.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-identity-dotnet",
+ "path": "skills/azure-identity-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Identity Dotnet",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-identity-py",
+ "path": "skills/azure-identity-py",
+ "category": "uncategorized",
+ "name": "Azure Identity Py",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-identity-rust",
+ "path": "skills/azure-identity-rust",
+ "category": "uncategorized",
+ "name": "Azure Identity Rust",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-keyvault-certificates-rust",
+ "path": "skills/azure-keyvault-certificates-rust",
+ "category": "uncategorized",
+ "name": "Azure Keyvault Certificates Rust",
+ "description": "Client library for Azure Key Vault Certificates \u2014 secure storage and management of certificates.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-keyvault-keys-rust",
+ "path": "skills/azure-keyvault-keys-rust",
+ "category": "uncategorized",
+ "name": "Azure Keyvault Keys Rust",
+ "description": "Client library for Azure Key Vault Keys \u2014 secure storage and management of cryptographic keys.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-keyvault-py",
+ "path": "skills/azure-keyvault-py",
+ "category": "uncategorized",
+ "name": "Azure Keyvault Py",
+ "description": "Secure storage and management for secrets, cryptographic keys, and certificates.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-keyvault-secrets-rust",
+ "path": "skills/azure-keyvault-secrets-rust",
+ "category": "uncategorized",
+ "name": "Azure Keyvault Secrets Rust",
+ "description": "Client library for Azure Key Vault Secrets \u2014 secure storage for passwords, API keys, and other secrets.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-maps-search-dotnet",
+ "path": "skills/azure-maps-search-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Maps Search Dotnet",
+ "description": "Azure Maps SDK for .NET providing location-based services: geocoding, routing, rendering, geolocation, and weather.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-messaging-webpubsubservice-py",
+ "path": "skills/azure-messaging-webpubsubservice-py",
+ "category": "uncategorized",
+ "name": "Azure Messaging Webpubsubservice Py",
+ "description": "Real-time messaging with WebSocket connections at scale.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-apicenter-dotnet",
+ "path": "skills/azure-mgmt-apicenter-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Apicenter Dotnet",
+ "description": "Centralized API inventory and governance SDK for managing APIs across your organization.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-apicenter-py",
+ "path": "skills/azure-mgmt-apicenter-py",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Apicenter Py",
+ "description": "Manage API inventory, metadata, and governance in Azure API Center.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-dotnet",
+ "path": "skills/azure-mgmt-apimanagement-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Apimanagement Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure API Management resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-py",
+ "path": "skills/azure-mgmt-apimanagement-py",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Apimanagement Py",
+ "description": "Manage Azure API Management services, APIs, products, and policies.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-applicationinsights-dotnet",
+ "path": "skills/azure-mgmt-applicationinsights-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Applicationinsights Dotnet",
+ "description": "Azure Resource Manager SDK for managing Application Insights resources for application performance monitoring.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "path": "skills/azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Arizeaiobservabilityeval Dotnet",
+ "description": ".NET SDK for managing Arize AI Observability and Evaluation resources on Azure.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-botservice-dotnet",
+ "path": "skills/azure-mgmt-botservice-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Botservice Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure Bot Service resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-botservice-py",
+ "path": "skills/azure-mgmt-botservice-py",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Botservice Py",
+ "description": "Manage Azure Bot Service resources including bots, channels, and connections.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-fabric-dotnet",
+ "path": "skills/azure-mgmt-fabric-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Fabric Dotnet",
+ "description": "Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-fabric-py",
+ "path": "skills/azure-mgmt-fabric-py",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Fabric Py",
+ "description": "Manage Microsoft Fabric capacities and resources programmatically.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-mgmt-weightsandbiases-dotnet",
+ "path": "skills/azure-mgmt-weightsandbiases-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Mgmt Weightsandbiases Dotnet",
+ "description": "Azure Resource Manager SDK for deploying and managing Weights & Biases ML experiment tracking instances via Azure Marketplace.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-ingestion-java",
+ "path": "skills/azure-monitor-ingestion-java",
+ "category": "uncategorized",
+ "name": "Azure Monitor Ingestion Java",
+ "description": "Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-ingestion-py",
+ "path": "skills/azure-monitor-ingestion-py",
+ "category": "uncategorized",
+ "name": "Azure Monitor Ingestion Py",
+ "description": "Send custom logs to Azure Monitor Log Analytics workspace using the Logs Ingestion API.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-java",
+ "path": "skills/azure-monitor-opentelemetry-exporter-java",
+ "category": "uncategorized",
+ "name": "Azure Monitor Opentelemetry Exporter Java",
+ "description": "> **\u26a0\ufe0f DEPRECATION NOTICE**: This package is deprecated. Migrate to `azure-monitor-opentelemetry-autoconfigure`. > > See [Migration Guide](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/MIGRATIO",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-py",
+ "path": "skills/azure-monitor-opentelemetry-exporter-py",
+ "category": "uncategorized",
+ "name": "Azure Monitor Opentelemetry Exporter Py",
+ "description": "Low-level exporter for sending OpenTelemetry traces, metrics, and logs to Application Insights.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-py",
+ "path": "skills/azure-monitor-opentelemetry-py",
+ "category": "uncategorized",
+ "name": "Azure Monitor Opentelemetry Py",
+ "description": "One-line setup for Application Insights with OpenTelemetry auto-instrumentation.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-query-java",
+ "path": "skills/azure-monitor-query-java",
+ "category": "uncategorized",
+ "name": "Azure Monitor Query Java",
+ "description": "> **DEPRECATION NOTICE**: This package is deprecated in favor of: > - `azure-monitor-query-logs` \u2014 For Log Analytics queries > - `azure-monitor-query-metrics` \u2014 For metrics queries > > See migration guides: [Logs Migration](https://github.com/Azure/a",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-monitor-query-py",
+ "path": "skills/azure-monitor-query-py",
+ "category": "uncategorized",
+ "name": "Azure Monitor Query Py",
+ "description": "Query logs and metrics from Azure Monitor and Log Analytics workspaces.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-postgres-ts",
+ "path": "skills/azure-postgres-ts",
+ "category": "uncategorized",
+ "name": "Azure Postgres Ts",
+ "description": "Connect to Azure Database for PostgreSQL Flexible Server using the `pg` (node-postgres) package with support for password and Microsoft Entra ID (passwordless) authentication.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-cosmosdb-dotnet",
+ "path": "skills/azure-resource-manager-cosmosdb-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Cosmosdb Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure Cosmos DB resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-durabletask-dotnet",
+ "path": "skills/azure-resource-manager-durabletask-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Durabletask Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-mysql-dotnet",
+ "path": "skills/azure-resource-manager-mysql-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Mysql Dotnet",
+ "description": "Azure Resource Manager SDK for managing MySQL Flexible Server deployments.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-playwright-dotnet",
+ "path": "skills/azure-resource-manager-playwright-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Playwright Dotnet",
+ "description": "Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-postgresql-dotnet",
+ "path": "skills/azure-resource-manager-postgresql-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Postgresql Dotnet",
+ "description": "Azure Resource Manager SDK for managing PostgreSQL Flexible Server deployments.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-redis-dotnet",
+ "path": "skills/azure-resource-manager-redis-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Redis Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure Cache for Redis resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-resource-manager-sql-dotnet",
+ "path": "skills/azure-resource-manager-sql-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Resource Manager Sql Dotnet",
+ "description": "Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-search-documents-dotnet",
+ "path": "skills/azure-search-documents-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Search Documents Dotnet",
+ "description": "Build search applications with full-text, vector, semantic, and hybrid search capabilities.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-search-documents-py",
+ "path": "skills/azure-search-documents-py",
+ "category": "uncategorized",
+ "name": "Azure Search Documents Py",
+ "description": "Full-text, vector, and hybrid search with AI enrichment capabilities.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-security-keyvault-keys-dotnet",
+ "path": "skills/azure-security-keyvault-keys-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Security Keyvault Keys Dotnet",
+ "description": "Client library for managing cryptographic keys in Azure Key Vault and Managed HSM.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-servicebus-dotnet",
+ "path": "skills/azure-servicebus-dotnet",
+ "category": "uncategorized",
+ "name": "Azure Servicebus Dotnet",
+ "description": "Enterprise messaging SDK for reliable message delivery with queues, topics, subscriptions, and sessions.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-servicebus-py",
+ "path": "skills/azure-servicebus-py",
+ "category": "uncategorized",
+ "name": "Azure Servicebus Py",
+ "description": "Enterprise messaging for reliable cloud communication with queues and pub/sub topics.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-speech-to-text-rest-py",
+ "path": "skills/azure-speech-to-text-rest-py",
+ "category": "uncategorized",
+ "name": "Azure Speech To Text Rest Py",
+ "description": "Simple REST API for speech-to-text transcription of short audio files (up to 60 seconds). No SDK required - just HTTP requests.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-blob-py",
+ "path": "skills/azure-storage-blob-py",
+ "category": "uncategorized",
+ "name": "Azure Storage Blob Py",
+ "description": "Client library for Azure Blob Storage \u2014 object storage for unstructured data.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-blob-rust",
+ "path": "skills/azure-storage-blob-rust",
+ "category": "uncategorized",
+ "name": "Azure Storage Blob Rust",
+ "description": "Client library for Azure Blob Storage \u2014 Microsoft's object storage solution for the cloud.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-blob-ts",
+ "path": "skills/azure-storage-blob-ts",
+ "category": "uncategorized",
+ "name": "Azure Storage Blob Ts",
+ "description": "SDK for Azure Blob Storage operations \u2014 upload, download, list, and manage blobs and containers.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-file-datalake-py",
+ "path": "skills/azure-storage-file-datalake-py",
+ "category": "uncategorized",
+ "name": "Azure Storage File Datalake Py",
+ "description": "Hierarchical file system for big data analytics workloads.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-file-share-py",
+ "path": "skills/azure-storage-file-share-py",
+ "category": "uncategorized",
+ "name": "Azure Storage File Share Py",
+ "description": "Manage SMB file shares for cloud-native and lift-and-shift scenarios.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-file-share-ts",
+ "path": "skills/azure-storage-file-share-ts",
+ "category": "uncategorized",
+ "name": "Azure Storage File Share Ts",
+ "description": "SDK for Azure File Share operations \u2014 SMB file shares, directories, and file operations.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-queue-py",
+ "path": "skills/azure-storage-queue-py",
+ "category": "uncategorized",
+ "name": "Azure Storage Queue Py",
+ "description": "Simple, cost-effective message queuing for asynchronous communication.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "azure-storage-queue-ts",
+ "path": "skills/azure-storage-queue-ts",
+ "category": "uncategorized",
+ "name": "Azure Storage Queue Ts",
+ "description": "SDK for Azure Queue Storage operations \u2014 send, receive, peek, and manage messages in queues.",
"risk": "unknown",
"source": "unknown"
},
@@ -600,169 +1401,70 @@
"name": "azure-ai-anomalydetector-java",
"description": "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-contentsafety-java",
"path": "skills/azure-ai-contentsafety-java",
"category": "uncategorized",
"name": "azure-ai-contentsafety-java",
- "description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual content, and self-harm.",
+ "description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentsafety-py",
- "path": "skills/azure-ai-contentsafety-py",
- "category": "uncategorized",
- "name": "azure-ai-contentsafety-py",
- "description": "Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.\nTriggers: \"azure-ai-contentsafety\", \"ContentSafetyClient\", \"content moderation\", \"harmful content\", \"text analysis\", \"image analysis\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-contentsafety-ts",
"path": "skills/azure-ai-contentsafety-ts",
"category": "uncategorized",
"name": "azure-ai-contentsafety-ts",
- "description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual content, or self-harm, or managing custom blocklists.",
+ "description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentunderstanding-py",
- "path": "skills/azure-ai-contentunderstanding-py",
- "category": "uncategorized",
- "name": "azure-ai-contentunderstanding-py",
- "description": "Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.\nTriggers: \"azure-ai-contentunderstanding\", \"ContentUnderstandingClient\", \"multimodal analysis\", \"document extraction\", \"video analysis\", \"audio transcription\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-document-intelligence-dotnet",
- "path": "skills/azure-ai-document-intelligence-dotnet",
- "category": "uncategorized",
- "name": "azure-ai-document-intelligence-dotnet",
- "description": "Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: \"Document Intelligence\", \"DocumentIntelligenceClient\", \"form recognizer\", \"invoice extraction\", \"receipt OCR\", \"document analysis .NET\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-document-intelligence-ts",
"path": "skills/azure-ai-document-intelligence-ts",
"category": "uncategorized",
"name": "azure-ai-document-intelligence-ts",
- "description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building custom document models.",
+ "description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-formrecognizer-java",
"path": "skills/azure-ai-formrecognizer-java",
"category": "uncategorized",
"name": "azure-ai-formrecognizer-java",
- "description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or building custom document models.",
+ "description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-ml-py",
- "path": "skills/azure-ai-ml-py",
- "category": "uncategorized",
- "name": "azure-ai-ml-py",
- "description": "Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.\nTriggers: \"azure-ai-ml\", \"MLClient\", \"workspace\", \"model registry\", \"training jobs\", \"datasets\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-openai-dotnet",
- "path": "skills/azure-ai-openai-dotnet",
- "category": "uncategorized",
- "name": "azure-ai-openai-dotnet",
- "description": "Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: \"Azure OpenAI\", \"AzureOpenAIClient\", \"ChatClient\", \"chat completions .NET\", \"GPT-4\", \"embeddings\", \"DALL-E\", \"Whisper\", \"OpenAI .NET\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-dotnet",
- "path": "skills/azure-ai-projects-dotnet",
- "category": "uncategorized",
- "name": "azure-ai-projects-dotnet",
- "description": "Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: \"AI Projects\", \"AIProjectClient\", \"Foundry project\", \"versioned agents\", \"evaluations\", \"datasets\", \"connections\", \"deployments .NET\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-java",
- "path": "skills/azure-ai-projects-java",
- "category": "uncategorized",
- "name": "azure-ai-projects-java",
- "description": "Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.\nTriggers: \"AIProjectClient java\", \"azure ai projects java\", \"Foundry project java\", \"ConnectionsClient\", \"DatasetsClient\", \"IndexesClient\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-projects-py",
"path": "skills/azure-ai-projects-py",
"category": "uncategorized",
"name": "azure-ai-projects-py",
- "description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evaluations, managing connections/deployments/datasets/indexes, or using OpenAI-compatible clients. This is the high-level Foundry SDK - for low-level agent operations, use azure-ai-agents-python skill.",
+ "description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-projects-ts",
"path": "skills/azure-ai-projects-ts",
"category": "uncategorized",
"name": "azure-ai-projects-ts",
- "description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluations, or getting OpenAI clients.",
+ "description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-textanalytics-py",
- "path": "skills/azure-ai-textanalytics-py",
- "category": "uncategorized",
- "name": "azure-ai-textanalytics-py",
- "description": "Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.\nTriggers: \"text analytics\", \"sentiment analysis\", \"entity recognition\", \"key phrase\", \"PII detection\", \"TextAnalyticsClient\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-transcription-py",
- "path": "skills/azure-ai-transcription-py",
- "category": "uncategorized",
- "name": "azure-ai-transcription-py",
- "description": "Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.\nTriggers: \"transcription\", \"speech to text\", \"Azure AI Transcription\", \"TranscriptionClient\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-document-py",
- "path": "skills/azure-ai-translation-document-py",
- "category": "uncategorized",
- "name": "azure-ai-translation-document-py",
- "description": "Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.\nTriggers: \"document translation\", \"batch translation\", \"translate documents\", \"DocumentTranslationClient\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-text-py",
- "path": "skills/azure-ai-translation-text-py",
- "category": "uncategorized",
- "name": "azure-ai-translation-text-py",
- "description": "Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.\nTriggers: \"text translation\", \"translator\", \"translate text\", \"transliterate\", \"TextTranslationClient\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-translation-ts",
"path": "skills/azure-ai-translation-ts",
"category": "uncategorized",
"name": "azure-ai-translation-ts",
- "description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliteration, language detection, or batch document translation.",
+ "description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-vision-imageanalysis-java",
@@ -771,106 +1473,52 @@
"name": "azure-ai-vision-imageanalysis-java",
"description": "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-vision-imageanalysis-py",
- "path": "skills/azure-ai-vision-imageanalysis-py",
- "category": "uncategorized",
- "name": "azure-ai-vision-imageanalysis-py",
- "description": "Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.\nTriggers: \"image analysis\", \"computer vision\", \"OCR\", \"object detection\", \"ImageAnalysisClient\", \"image caption\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-dotnet",
- "path": "skills/azure-ai-voicelive-dotnet",
- "category": "uncategorized",
- "name": "azure-ai-voicelive-dotnet",
- "description": "Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant .NET\", \"bidirectional audio\", \"speech-to-speech\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-java",
- "path": "skills/azure-ai-voicelive-java",
- "category": "uncategorized",
- "name": "azure-ai-voicelive-java",
- "description": "Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.\nTriggers: \"VoiceLiveClient java\", \"voice assistant java\", \"real-time voice java\", \"audio streaming java\", \"voice activity detection java\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-voicelive-py",
"path": "skills/azure-ai-voicelive-py",
"category": "uncategorized",
"name": "azure-ai-voicelive-py",
- "description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with Azure AI, including voice assistants, voice-enabled chatbots, real-time speech-to-speech translation, voice-driven avatars, or any WebSocket-based audio streaming with AI models. Supports Server VAD (Voice Activity Detection), turn-based conversation, function calling, MCP tools, avatar integration, and transcription.",
+ "description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-ts",
- "path": "skills/azure-ai-voicelive-ts",
- "category": "uncategorized",
- "name": "azure-ai-voicelive-ts",
- "description": "Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant TypeScript\", \"bidirectional audio\", \"speech-to-speech JavaScript\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-java",
- "path": "skills/azure-appconfiguration-java",
- "category": "uncategorized",
- "name": "azure-appconfiguration-java",
- "description": "Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.\nTriggers: \"ConfigurationClient java\", \"app configuration java\", \"feature flag java\", \"configuration setting java\", \"azure config java\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-py",
- "path": "skills/azure-appconfiguration-py",
- "category": "uncategorized",
- "name": "azure-appconfiguration-py",
- "description": "Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.\nTriggers: \"azure-appconfiguration\", \"AzureAppConfigurationClient\", \"feature flags\", \"configuration\", \"key-value settings\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-appconfiguration-ts",
"path": "skills/azure-appconfiguration-ts",
"category": "uncategorized",
"name": "azure-appconfiguration-ts",
- "description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, or centralized configuration management.",
+ "description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-communication-callautomation-java",
"path": "skills/azure-communication-callautomation-java",
"category": "uncategorized",
"name": "azure-communication-callautomation-java",
- "description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-powered call flows.",
+ "description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-communication-callingserver-java",
"path": "skills/azure-communication-callingserver-java",
"category": "uncategorized",
"name": "azure-communication-callingserver-java",
- "description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining legacy code.",
+ "description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-communication-chat-java",
"path": "skills/azure-communication-chat-java",
"category": "uncategorized",
"name": "azure-communication-chat-java",
- "description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.",
+ "description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-communication-common-java",
@@ -879,7 +1527,7 @@
"name": "azure-communication-common-java",
"description": "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-communication-sms-java",
@@ -888,97 +1536,25 @@
"name": "azure-communication-sms-java",
"description": "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-compute-batch-java",
- "path": "skills/azure-compute-batch-java",
- "category": "uncategorized",
- "name": "azure-compute-batch-java",
- "description": "Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.\nTriggers: \"BatchClient java\", \"azure batch java\", \"batch pool java\", \"batch job java\", \"HPC java\", \"parallel computing java\".",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-containerregistry-py",
- "path": "skills/azure-containerregistry-py",
- "category": "uncategorized",
- "name": "azure-containerregistry-py",
- "description": "Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.\nTriggers: \"azure-containerregistry\", \"ContainerRegistryClient\", \"container images\", \"docker registry\", \"ACR\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-cosmos-db-py",
"path": "skills/azure-cosmos-db-py",
"category": "uncategorized",
"name": "azure-cosmos-db-py",
- "description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers on phrases like \"Cosmos DB\", \"NoSQL database\", \"document store\", \"add persistence\", \"database service layer\", or \"Python Cosmos SDK\".",
+ "description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-java",
- "path": "skills/azure-cosmos-java",
- "category": "uncategorized",
- "name": "azure-cosmos-java",
- "description": "Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.\nTriggers: \"CosmosClient java\", \"CosmosAsyncClient\", \"cosmos database java\", \"cosmosdb java\", \"document database java\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-py",
- "path": "skills/azure-cosmos-py",
- "category": "uncategorized",
- "name": "azure-cosmos-py",
- "description": "Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db\", \"CosmosClient\", \"container\", \"document\", \"NoSQL\", \"partition key\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-rust",
- "path": "skills/azure-cosmos-rust",
- "category": "uncategorized",
- "name": "azure-cosmos-rust",
- "description": "Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db rust\", \"CosmosClient rust\", \"container\", \"document rust\", \"NoSQL rust\", \"partition key\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-ts",
- "path": "skills/azure-cosmos-ts",
- "category": "uncategorized",
- "name": "azure-cosmos-ts",
- "description": "Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: \"Cosmos DB\", \"@azure/cosmos\", \"CosmosClient\", \"document CRUD\", \"NoSQL queries\", \"bulk operations\", \"partition key\", \"container.items\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-data-tables-java",
"path": "skills/azure-data-tables-java",
"category": "uncategorized",
"name": "azure-data-tables-java",
- "description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at scale.",
+ "description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-data-tables-py",
- "path": "skills/azure-data-tables-py",
- "category": "uncategorized",
- "name": "azure-data-tables-py",
- "description": "Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.\nTriggers: \"table storage\", \"TableServiceClient\", \"TableClient\", \"entities\", \"PartitionKey\", \"RowKey\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-dotnet",
- "path": "skills/azure-eventgrid-dotnet",
- "category": "uncategorized",
- "name": "azure-eventgrid-dotnet",
- "description": "Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: \"Event Grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events .NET\", \"event-driven\", \"pub/sub\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-eventgrid-java",
@@ -987,25 +1563,7 @@
"name": "azure-eventgrid-java",
"description": "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-py",
- "path": "skills/azure-eventgrid-py",
- "category": "uncategorized",
- "name": "azure-eventgrid-py",
- "description": "Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.\nTriggers: \"event grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-dotnet",
- "path": "skills/azure-eventhub-dotnet",
- "category": "uncategorized",
- "name": "azure-eventhub-dotnet",
- "description": "Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: \"Event Hubs\", \"event streaming\", \"EventHubProducerClient\", \"EventProcessorClient\", \"send events\", \"receive events\", \"checkpointing\", \"partition\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-eventhub-java",
@@ -1014,106 +1572,43 @@
"name": "azure-eventhub-java",
"description": "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-py",
- "path": "skills/azure-eventhub-py",
- "category": "uncategorized",
- "name": "azure-eventhub-py",
- "description": "Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.\nTriggers: \"event hubs\", \"EventHubProducerClient\", \"EventHubConsumerClient\", \"streaming\", \"partitions\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-rust",
- "path": "skills/azure-eventhub-rust",
- "category": "uncategorized",
- "name": "azure-eventhub-rust",
- "description": "Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.\nTriggers: \"event hubs rust\", \"ProducerClient rust\", \"ConsumerClient rust\", \"send event rust\", \"streaming rust\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-eventhub-ts",
"path": "skills/azure-eventhub-ts",
"category": "uncategorized",
"name": "azure-eventhub-ts",
- "description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event-driven architectures with partitioned consumers.",
+ "description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-functions",
"path": "skills/azure-functions",
"category": "uncategorized",
"name": "azure-functions",
- "description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models. Use when: azure function, azure functions, durable functions, azure serverless, function app.",
+ "description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
- {
- "id": "azure-identity-dotnet",
- "path": "skills/azure-identity-dotnet",
- "category": "uncategorized",
- "name": "azure-identity-dotnet",
- "description": "Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: \"Azure Identity\", \"DefaultAzureCredential\", \"ManagedIdentityCredential\", \"ClientSecretCredential\", \"authentication .NET\", \"Azure auth\", \"credential chain\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "azure-identity-java",
"path": "skills/azure-identity-java",
"category": "uncategorized",
"name": "azure-identity-java",
- "description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applications.",
+ "description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-py",
- "path": "skills/azure-identity-py",
- "category": "uncategorized",
- "name": "azure-identity-py",
- "description": "Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.\nTriggers: \"azure-identity\", \"DefaultAzureCredential\", \"authentication\", \"managed identity\", \"service principal\", \"credential\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-rust",
- "path": "skills/azure-identity-rust",
- "category": "uncategorized",
- "name": "azure-identity-rust",
- "description": "Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.\nTriggers: \"azure-identity\", \"DeveloperToolsCredential\", \"authentication rust\", \"managed identity rust\", \"credential rust\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-identity-ts",
"path": "skills/azure-identity-ts",
"category": "uncategorized",
"name": "azure-identity-ts",
- "description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or interactive browser login.",
+ "description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-certificates-rust",
- "path": "skills/azure-keyvault-certificates-rust",
- "category": "uncategorized",
- "name": "azure-keyvault-certificates-rust",
- "description": "Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.\nTriggers: \"keyvault certificates rust\", \"CertificateClient rust\", \"create certificate rust\", \"import certificate rust\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-keys-rust",
- "path": "skills/azure-keyvault-keys-rust",
- "category": "uncategorized",
- "name": "azure-keyvault-keys-rust",
- "description": "Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.\nTriggers: \"keyvault keys rust\", \"KeyClient rust\", \"create key rust\", \"encrypt rust\", \"sign rust\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-keyvault-keys-ts",
@@ -1122,25 +1617,7 @@
"name": "azure-keyvault-keys-ts",
"description": "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-py",
- "path": "skills/azure-keyvault-py",
- "category": "uncategorized",
- "name": "azure-keyvault-py",
- "description": "Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.\nTriggers: \"key vault\", \"SecretClient\", \"KeyClient\", \"CertificateClient\", \"secrets\", \"encryption keys\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-secrets-rust",
- "path": "skills/azure-keyvault-secrets-rust",
- "category": "uncategorized",
- "name": "azure-keyvault-secrets-rust",
- "description": "Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.\nTriggers: \"keyvault secrets rust\", \"SecretClient rust\", \"get secret rust\", \"set secret rust\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-keyvault-secrets-ts",
@@ -1149,16 +1626,7 @@
"name": "azure-keyvault-secrets-ts",
"description": "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-maps-search-dotnet",
- "path": "skills/azure-maps-search-dotnet",
- "category": "uncategorized",
- "name": "azure-maps-search-dotnet",
- "description": "Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: \"Azure Maps\", \"MapsSearchClient\", \"MapsRoutingClient\", \"MapsRenderingClient\", \"geocoding .NET\", \"route directions\", \"map tiles\", \"geolocation\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-messaging-webpubsub-java",
@@ -1167,313 +1635,43 @@
"name": "azure-messaging-webpubsub-java",
"description": "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-messaging-webpubsubservice-py",
- "path": "skills/azure-messaging-webpubsubservice-py",
- "category": "uncategorized",
- "name": "azure-messaging-webpubsubservice-py",
- "description": "Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.\nTriggers: \"azure-messaging-webpubsubservice\", \"WebPubSubServiceClient\", \"real-time\", \"WebSocket\", \"pub/sub\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-dotnet",
- "path": "skills/azure-mgmt-apicenter-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-apicenter-dotnet",
- "description": "Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: \"API Center\", \"ApiCenterService\", \"ApiCenterWorkspace\", \"ApiCenterApi\", \"API inventory\", \"API governance\", \"API versioning\", \"API catalog\", \"API discovery\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-py",
- "path": "skills/azure-mgmt-apicenter-py",
- "category": "uncategorized",
- "name": "azure-mgmt-apicenter-py",
- "description": "Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.\nTriggers: \"azure-mgmt-apicenter\", \"ApiCenterMgmtClient\", \"API Center\", \"API inventory\", \"API governance\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-dotnet",
- "path": "skills/azure-mgmt-apimanagement-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-apimanagement-dotnet",
- "description": "Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: \"API Management\", \"APIM service\", \"create APIM\", \"manage APIs\", \"ApiManagementServiceResource\", \"API policies\", \"APIM products\", \"APIM subscriptions\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-py",
- "path": "skills/azure-mgmt-apimanagement-py",
- "category": "uncategorized",
- "name": "azure-mgmt-apimanagement-py",
- "description": "Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.\nTriggers: \"azure-mgmt-apimanagement\", \"ApiManagementClient\", \"APIM\", \"API gateway\", \"API Management\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-applicationinsights-dotnet",
- "path": "skills/azure-mgmt-applicationinsights-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-applicationinsights-dotnet",
- "description": "Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: \"Application Insights\", \"ApplicationInsights\", \"App Insights\", \"APM\", \"application monitoring\", \"web tests\", \"availability tests\", \"workbooks\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "path": "skills/azure-mgmt-arizeaiobservabilityeval-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "description": "Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations \non Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability \ninto .NET applications. Triggers: \"Arize AI\", \"ML observability\", \"ArizeAIObservabilityEval\", \"Arize organization\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-dotnet",
- "path": "skills/azure-mgmt-botservice-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-botservice-dotnet",
- "description": "Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: \"Bot Service\", \"BotResource\", \"Azure Bot\", \"DirectLine channel\", \"Teams channel\", \"bot management .NET\", \"create bot\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-py",
- "path": "skills/azure-mgmt-botservice-py",
- "category": "uncategorized",
- "name": "azure-mgmt-botservice-py",
- "description": "Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.\nTriggers: \"azure-mgmt-botservice\", \"AzureBotService\", \"bot management\", \"conversational AI\", \"bot channels\".",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-dotnet",
- "path": "skills/azure-mgmt-fabric-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-fabric-dotnet",
- "description": "Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: \"Fabric capacity\", \"create capacity\", \"suspend capacity\", \"resume capacity\", \"Fabric SKU\", \"provision Fabric\", \"ARM Fabric\", \"FabricCapacityResource\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-py",
- "path": "skills/azure-mgmt-fabric-py",
- "category": "uncategorized",
- "name": "azure-mgmt-fabric-py",
- "description": "Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.\nTriggers: \"azure-mgmt-fabric\", \"FabricMgmtClient\", \"Fabric capacity\", \"Microsoft Fabric\", \"Power BI capacity\".",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-mgmt-mongodbatlas-dotnet",
"path": "skills/azure-mgmt-mongodbatlas-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-mongodbatlas-dotnet",
- "description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.",
+ "description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-weightsandbiases-dotnet",
- "path": "skills/azure-mgmt-weightsandbiases-dotnet",
- "category": "uncategorized",
- "name": "azure-mgmt-weightsandbiases-dotnet",
- "description": "Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: \"Weights and Biases\", \"W&B\", \"WeightsAndBiases\", \"ML experiment tracking\", \"model registry\", \"experiment management\", \"wandb\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-microsoft-playwright-testing-ts",
"path": "skills/azure-microsoft-playwright-testing-ts",
"category": "uncategorized",
"name": "azure-microsoft-playwright-testing-ts",
- "description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.",
+ "description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-java",
- "path": "skills/azure-monitor-ingestion-java",
- "category": "uncategorized",
- "name": "azure-monitor-ingestion-java",
- "description": "Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).\nTriggers: \"LogsIngestionClient java\", \"azure monitor ingestion java\", \"custom logs java\", \"DCR java\", \"data collection rule java\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-py",
- "path": "skills/azure-monitor-ingestion-py",
- "category": "uncategorized",
- "name": "azure-monitor-ingestion-py",
- "description": "Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.\nTriggers: \"azure-monitor-ingestion\", \"LogsIngestionClient\", \"custom logs\", \"DCR\", \"data collection rule\", \"Log Analytics\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-java",
- "path": "skills/azure-monitor-opentelemetry-exporter-java",
- "category": "uncategorized",
- "name": "azure-monitor-opentelemetry-exporter-java",
- "description": "Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.\nTriggers: \"AzureMonitorExporter java\", \"opentelemetry azure java\", \"application insights java otel\", \"azure monitor tracing java\".\nNote: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-py",
- "path": "skills/azure-monitor-opentelemetry-exporter-py",
- "category": "uncategorized",
- "name": "azure-monitor-opentelemetry-exporter-py",
- "description": "Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.\nTriggers: \"azure-monitor-opentelemetry-exporter\", \"AzureMonitorTraceExporter\", \"AzureMonitorMetricExporter\", \"AzureMonitorLogExporter\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-py",
- "path": "skills/azure-monitor-opentelemetry-py",
- "category": "uncategorized",
- "name": "azure-monitor-opentelemetry-py",
- "description": "Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.\nTriggers: \"azure-monitor-opentelemetry\", \"configure_azure_monitor\", \"Application Insights\", \"OpenTelemetry distro\", \"auto-instrumentation\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-monitor-opentelemetry-ts",
"path": "skills/azure-monitor-opentelemetry-ts",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-ts",
- "description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Application Insights.",
+ "description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-java",
- "path": "skills/azure-monitor-query-java",
- "category": "uncategorized",
- "name": "azure-monitor-query-java",
- "description": "Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.\nTriggers: \"LogsQueryClient java\", \"MetricsQueryClient java\", \"kusto query java\", \"log analytics java\", \"azure monitor query java\".\nNote: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-py",
- "path": "skills/azure-monitor-query-py",
- "category": "uncategorized",
- "name": "azure-monitor-query-py",
- "description": "Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.\nTriggers: \"azure-monitor-query\", \"LogsQueryClient\", \"MetricsQueryClient\", \"Log Analytics\", \"Kusto queries\", \"Azure metrics\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-postgres-ts",
- "path": "skills/azure-postgres-ts",
- "category": "uncategorized",
- "name": "azure-postgres-ts",
- "description": "Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: \"PostgreSQL\", \"postgres\", \"pg client\", \"node-postgres\", \"Azure PostgreSQL connection\", \"PostgreSQL TypeScript\", \"pg Pool\", \"passwordless postgres\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-cosmosdb-dotnet",
- "path": "skills/azure-resource-manager-cosmosdb-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-cosmosdb-dotnet",
- "description": "Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: \"Cosmos DB account\", \"create Cosmos account\", \"manage Cosmos resources\", \"ARM Cosmos\", \"CosmosDBAccountResource\", \"provision Cosmos DB\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-durabletask-dotnet",
- "path": "skills/azure-resource-manager-durabletask-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-durabletask-dotnet",
- "description": "Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: \"Durable Task Scheduler\", \"create scheduler\", \"task hub\", \"DurableTaskSchedulerResource\", \"provision Durable Task\", \"orchestration scheduler\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-mysql-dotnet",
- "path": "skills/azure-resource-manager-mysql-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-mysql-dotnet",
- "description": "Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"MySQL\", \"MySqlFlexibleServer\", \"MySQL Flexible Server\", \"Azure Database for MySQL\", \"MySQL database management\", \"MySQL firewall\", \"MySQL backup\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-playwright-dotnet",
- "path": "skills/azure-resource-manager-playwright-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-playwright-dotnet",
- "description": "Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: \"Playwright workspace\", \"create Playwright Testing workspace\", \"manage Playwright resources\", \"ARM Playwright\", \"PlaywrightWorkspaceResource\", \"provision Playwright Testing\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-postgresql-dotnet",
- "path": "skills/azure-resource-manager-postgresql-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-postgresql-dotnet",
- "description": "Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"PostgreSQL\", \"PostgreSqlFlexibleServer\", \"PostgreSQL Flexible Server\", \"Azure Database for PostgreSQL\", \"PostgreSQL database management\", \"PostgreSQL firewall\", \"PostgreSQL backup\", \"Postgres\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-redis-dotnet",
- "path": "skills/azure-resource-manager-redis-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-redis-dotnet",
- "description": "Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: \"Redis cache\", \"create Redis\", \"manage Redis\", \"ARM Redis\", \"RedisResource\", \"provision Redis\", \"Azure Cache for Redis\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-sql-dotnet",
- "path": "skills/azure-resource-manager-sql-dotnet",
- "category": "uncategorized",
- "name": "azure-resource-manager-sql-dotnet",
- "description": "Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: \"SQL server\", \"create SQL database\", \"manage SQL resources\", \"ARM SQL\", \"SqlServerResource\", \"provision Azure SQL\", \"elastic pool\", \"firewall rule\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-dotnet",
- "path": "skills/azure-search-documents-dotnet",
- "category": "uncategorized",
- "name": "azure-search-documents-dotnet",
- "description": "Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: \"Azure Search .NET\", \"SearchClient\", \"SearchIndexClient\", \"vector search C#\", \"semantic search .NET\", \"hybrid search\", \"Azure.Search.Documents\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-py",
- "path": "skills/azure-search-documents-py",
- "category": "uncategorized",
- "name": "azure-search-documents-py",
- "description": "Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.\nTriggers: \"azure-search-documents\", \"SearchClient\", \"SearchIndexClient\", \"vector search\", \"hybrid search\", \"semantic search\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-search-documents-ts",
"path": "skills/azure-search-documents-ts",
"category": "uncategorized",
"name": "azure-search-documents-ts",
- "description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building agentic retrieval with knowledge bases.",
+ "description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-security-keyvault-keys-dotnet",
- "path": "skills/azure-security-keyvault-keys-dotnet",
- "category": "uncategorized",
- "name": "azure-security-keyvault-keys-dotnet",
- "description": "Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: \"Key Vault keys\", \"KeyClient\", \"CryptographyClient\", \"RSA key\", \"EC key\", \"encrypt decrypt .NET\", \"key rotation\", \"HSM\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-security-keyvault-keys-java",
@@ -1482,7 +1680,7 @@
"name": "azure-security-keyvault-keys-java",
"description": "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-security-keyvault-secrets-java",
@@ -1491,140 +1689,50 @@
"name": "azure-security-keyvault-secrets-java",
"description": "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-dotnet",
- "path": "skills/azure-servicebus-dotnet",
- "category": "uncategorized",
- "name": "azure-servicebus-dotnet",
- "description": "Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: \"Service Bus\", \"ServiceBusClient\", \"ServiceBusSender\", \"ServiceBusReceiver\", \"ServiceBusProcessor\", \"message queue\", \"pub/sub .NET\", \"dead letter queue\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-py",
- "path": "skills/azure-servicebus-py",
- "category": "uncategorized",
- "name": "azure-servicebus-py",
- "description": "Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.\nTriggers: \"service bus\", \"ServiceBusClient\", \"queue\", \"topic\", \"subscription\", \"message broker\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-servicebus-ts",
"path": "skills/azure-servicebus-ts",
"category": "uncategorized",
"name": "azure-servicebus-ts",
- "description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterprise messaging patterns.",
+ "description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-speech-to-text-rest-py",
- "path": "skills/azure-speech-to-text-rest-py",
- "category": "uncategorized",
- "name": "azure-speech-to-text-rest-py",
- "description": "Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.\nTriggers: \"speech to text REST\", \"short audio transcription\", \"speech recognition REST API\", \"STT REST\", \"recognize speech REST\".\nDO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-storage-blob-java",
"path": "skills/azure-storage-blob-java",
"category": "uncategorized",
"name": "azure-storage-blob-java",
- "description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming data operations.",
+ "description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-py",
- "path": "skills/azure-storage-blob-py",
- "category": "uncategorized",
- "name": "azure-storage-blob-py",
- "description": "Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.\nTriggers: \"blob storage\", \"BlobServiceClient\", \"ContainerClient\", \"BlobClient\", \"upload blob\", \"download blob\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-rust",
- "path": "skills/azure-storage-blob-rust",
- "category": "uncategorized",
- "name": "azure-storage-blob-rust",
- "description": "Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.\nTriggers: \"blob storage rust\", \"BlobClient rust\", \"upload blob rust\", \"download blob rust\", \"container rust\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-ts",
- "path": "skills/azure-storage-blob-ts",
- "category": "uncategorized",
- "name": "azure-storage-blob-ts",
- "description": "Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: \"blob storage\", \"@azure/storage-blob\", \"BlobServiceClient\", \"ContainerClient\", \"upload blob\", \"download blob\", \"SAS token\", \"block blob\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-datalake-py",
- "path": "skills/azure-storage-file-datalake-py",
- "category": "uncategorized",
- "name": "azure-storage-file-datalake-py",
- "description": "Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.\nTriggers: \"data lake\", \"DataLakeServiceClient\", \"FileSystemClient\", \"ADLS Gen2\", \"hierarchical namespace\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-py",
- "path": "skills/azure-storage-file-share-py",
- "category": "uncategorized",
- "name": "azure-storage-file-share-py",
- "description": "Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.\nTriggers: \"azure-storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"file share\", \"SMB\".",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-ts",
- "path": "skills/azure-storage-file-share-ts",
- "category": "uncategorized",
- "name": "azure-storage-file-share-ts",
- "description": "Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: \"file share\", \"@azure/storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"SMB\", \"Azure Files\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-py",
- "path": "skills/azure-storage-queue-py",
- "category": "uncategorized",
- "name": "azure-storage-queue-py",
- "description": "Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.\nTriggers: \"queue storage\", \"QueueServiceClient\", \"QueueClient\", \"message queue\", \"dequeue\".\n",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-ts",
- "path": "skills/azure-storage-queue-ts",
- "category": "uncategorized",
- "name": "azure-storage-queue-ts",
- "description": "Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: \"queue storage\", \"@azure/storage-queue\", \"QueueServiceClient\", \"QueueClient\", \"send message\", \"receive message\", \"dequeue\", \"visibility timeout\".\n",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-web-pubsub-ts",
"path": "skills/azure-web-pubsub-ts",
"category": "uncategorized",
"name": "azure-web-pubsub-ts",
- "description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub messaging, group chat, or live notifications.",
+ "description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "backend-architect",
"path": "skills/backend-architect",
"category": "uncategorized",
- "name": "backend-architect",
- "description": "Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.",
+ "name": "Backend Architect",
+ "description": "You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "backend-security-coder",
+ "path": "skills/backend-security-coder",
+ "category": "uncategorized",
+ "name": "Backend Security Coder",
+ "description": "- Working on backend security coder tasks or workflows - Needing guidance, best practices, or checklists for backend security coder",
"risk": "unknown",
"source": "unknown"
},
@@ -1633,9 +1741,9 @@
"path": "skills/backend-dev-guidelines",
"category": "uncategorized",
"name": "backend-dev-guidelines",
- "description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.",
+ "description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "backend-development-feature-development",
@@ -1644,34 +1752,16 @@
"name": "backend-development-feature-development",
"description": "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "cc-skill-backend-patterns",
- "path": "skills/cc-skill-backend-patterns",
- "category": "uncategorized",
- "name": "backend-patterns",
- "description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "backend-security-coder",
- "path": "skills/backend-security-coder",
- "category": "uncategorized",
- "name": "backend-security-coder",
- "description": "Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "backtesting-frameworks",
"path": "skills/backtesting-frameworks",
"category": "uncategorized",
"name": "backtesting-frameworks",
- "description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.",
+ "description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "bamboohr-automation",
@@ -1680,7 +1770,16 @@
"name": "bamboohr-automation",
"description": "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "base",
+ "path": "skills/libreoffice/base",
+ "category": "libreoffice",
+ "name": "base",
+ "description": "Database management, forms, reports, and data operations with LibreOffice Base.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "basecamp-automation",
@@ -1689,6 +1788,15 @@
"name": "basecamp-automation",
"description": "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "bash-pro",
+ "path": "skills/bash-pro",
+ "category": "uncategorized",
+ "name": "Bash Pro",
+ "description": "- Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -1698,7 +1806,7 @@
"name": "bash-defensive-patterns",
"description": "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "bash-linux",
@@ -1707,16 +1815,16 @@
"name": "bash-linux",
"description": "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
- "id": "bash-pro",
- "path": "skills/bash-pro",
+ "id": "bash-scripting",
+ "path": "skills/bash-scripting",
"category": "uncategorized",
- "name": "bash-pro",
- "description": "Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "bash-scripting",
+ "description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "bats-testing-patterns",
@@ -1725,7 +1833,7 @@
"name": "bats-testing-patterns",
"description": "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "bazel-build-optimization",
@@ -1734,7 +1842,7 @@
"name": "bazel-build-optimization",
"description": "Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "beautiful-prose",
@@ -1752,25 +1860,34 @@
"name": "behavioral-modes",
"description": "AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "bevy-ecs-expert",
+ "path": "skills/bevy-ecs-expert",
+ "category": "uncategorized",
+ "name": "bevy-ecs-expert",
+ "description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "billing-automation",
"path": "skills/billing-automation",
"category": "uncategorized",
"name": "billing-automation",
- "description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.",
+ "description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "binary-analysis-patterns",
"path": "skills/binary-analysis-patterns",
"category": "uncategorized",
"name": "binary-analysis-patterns",
- "description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.",
+ "description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "bitbucket-automation",
@@ -1779,14 +1896,14 @@
"name": "bitbucket-automation",
"description": "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "blockchain-developer",
"path": "skills/blockchain-developer",
"category": "uncategorized",
- "name": "blockchain-developer",
- "description": "Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3 apps, DeFi protocols, or blockchain infrastructure.",
+ "name": "Blockchain Developer",
+ "description": "- Working on blockchain developer tasks or workflows - Needing guidance, best practices, or checklists for blockchain developer",
"risk": "unknown",
"source": "unknown"
},
@@ -1795,70 +1912,70 @@
"path": "skills/blockrun",
"category": "uncategorized",
"name": "blockrun",
- "description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\"blockrun\", \"use grok\", \"use gpt\", \"dall-e\", \"deepseek\")",
+ "description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "box-automation",
"path": "skills/box-automation",
"category": "uncategorized",
"name": "box-automation",
- "description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for current schemas.",
+ "description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "brainstorming",
"path": "skills/brainstorming",
"category": "uncategorized",
"name": "brainstorming",
- "description": "Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functionality). This skill transforms vague ideas into validated designs through disciplined, incremental reasoning and collaboration.",
+ "description": "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "brand-guidelines-anthropic",
"path": "skills/brand-guidelines-anthropic",
"category": "uncategorized",
- "name": "brand-guidelines",
- "description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",
+ "name": "brand-guidelines-anthropic",
+ "description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "brand-guidelines-community",
"path": "skills/brand-guidelines-community",
"category": "uncategorized",
- "name": "brand-guidelines",
- "description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",
+ "name": "brand-guidelines-community",
+ "description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "brevo-automation",
"path": "skills/brevo-automation",
"category": "uncategorized",
"name": "brevo-automation",
- "description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.",
+ "description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "broken-authentication",
"path": "skills/broken-authentication",
"category": "uncategorized",
- "name": "Broken Authentication Testing",
- "description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate password policies\", \"test for session fixation\", or \"identify authentication bypass flaws\". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.",
+ "name": "broken-authentication",
+ "description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "browser-automation",
"path": "skills/browser-automation",
"category": "uncategorized",
"name": "browser-automation",
- "description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202",
+ "description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -1867,7 +1984,7 @@
"path": "skills/browser-extension-builder",
"category": "uncategorized",
"name": "browser-extension-builder",
- "description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.",
+ "description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -1885,25 +2002,25 @@
"path": "skills/bun-development",
"category": "uncategorized",
"name": "bun-development",
- "description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun.",
+ "description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "burp-suite-testing",
"path": "skills/burp-suite-testing",
"category": "uncategorized",
- "name": "Burp Suite Web Application Testing",
- "description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp Repeater\", \"analyze HTTP history\", or \"configure proxy for web testing\". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.",
+ "name": "burp-suite-testing",
+ "description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "business-analyst",
"path": "skills/business-analyst",
"category": "uncategorized",
- "name": "business-analyst",
- "description": "Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.",
+ "name": "Business Analyst",
+ "description": "- Working on business analyst tasks or workflows - Needing guidance, best practices, or checklists for business analyst",
"risk": "unknown",
"source": "unknown"
},
@@ -1914,7 +2031,7 @@
"name": "busybox-on-windows",
"description": "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "c-pro",
@@ -1923,6 +2040,42 @@
"name": "c-pro",
"description": "Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-code",
+ "path": "skills/c4-code",
+ "category": "uncategorized",
+ "name": "C4 Code",
+ "description": "- Working on c4 code level: [directory name] tasks or workflows - Needing guidance, best practices, or checklists for c4 code level: [directory name]",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "c4-component",
+ "path": "skills/c4-component",
+ "category": "uncategorized",
+ "name": "C4 Component",
+ "description": "- Working on c4 component level: [component name] tasks or workflows - Needing guidance, best practices, or checklists for c4 component level: [component name]",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "c4-container",
+ "path": "skills/c4-container",
+ "category": "uncategorized",
+ "name": "C4 Container",
+ "description": "- Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "c4-context",
+ "path": "skills/c4-context",
+ "category": "uncategorized",
+ "name": "C4 Context",
+ "description": "- Working on c4 context level: system context tasks or workflows - Needing guidance, best practices, or checklists for c4 context level: system context",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -1932,43 +2085,7 @@
"name": "c4-architecture-c4-architecture",
"description": "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-code",
- "path": "skills/c4-code",
- "category": "uncategorized",
- "name": "c4-code",
- "description": "Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-component",
- "path": "skills/c4-component",
- "category": "uncategorized",
- "name": "c4-component",
- "description": "Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-container",
- "path": "skills/c4-container",
- "category": "uncategorized",
- "name": "c4-container",
- "description": "Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting system deployment architecture.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-context",
- "path": "skills/c4-context",
- "category": "uncategorized",
- "name": "c4-context",
- "description": "Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating the highest-level C4 system context documentation.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cal-com-automation",
@@ -1977,7 +2094,16 @@
"name": "cal-com-automation",
"description": "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "calc",
+ "path": "skills/libreoffice/calc",
+ "category": "libreoffice",
+ "name": "calc",
+ "description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "calendly-automation",
@@ -1986,7 +2112,7 @@
"name": "calendly-automation",
"description": "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "canva-automation",
@@ -1995,16 +2121,43 @@
"name": "canva-automation",
"description": "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "canvas-design",
"path": "skills/canvas-design",
"category": "uncategorized",
"name": "canvas-design",
- "description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",
+ "description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "cc-skill-backend-patterns",
+ "path": "skills/cc-skill-backend-patterns",
+ "category": "uncategorized",
+ "name": "cc-skill-backend-patterns",
+ "description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "cc-skill-clickhouse-io",
+ "path": "skills/cc-skill-clickhouse-io",
+ "category": "uncategorized",
+ "name": "cc-skill-clickhouse-io",
+ "description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "cc-skill-coding-standards",
+ "path": "skills/cc-skill-coding-standards",
+ "category": "uncategorized",
+ "name": "cc-skill-coding-standards",
+ "description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "cc-skill-continuous-learning",
@@ -2013,7 +2166,16 @@
"name": "cc-skill-continuous-learning",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "cc-skill-frontend-patterns",
+ "path": "skills/cc-skill-frontend-patterns",
+ "category": "uncategorized",
+ "name": "cc-skill-frontend-patterns",
+ "description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "cc-skill-project-guidelines-example",
@@ -2022,7 +2184,16 @@
"name": "cc-skill-project-guidelines-example",
"description": "Project Guidelines Skill (Example)",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "cc-skill-security-review",
+ "path": "skills/cc-skill-security-review",
+ "category": "uncategorized",
+ "name": "cc-skill-security-review",
+ "description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "cc-skill-strategic-compact",
@@ -2031,7 +2202,16 @@
"name": "cc-skill-strategic-compact",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "cdk-patterns",
+ "path": "skills/cdk-patterns",
+ "category": "uncategorized",
+ "name": "cdk-patterns",
+ "description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "changelog-automation",
@@ -2040,16 +2220,16 @@
"name": "changelog-automation",
"description": "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cicd-automation-workflow-automate",
"path": "skills/cicd-automation-workflow-automate",
"category": "uncategorized",
"name": "cicd-automation-workflow-automate",
- "description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.",
+ "description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "circleci-automation",
@@ -2058,7 +2238,7 @@
"name": "circleci-automation",
"description": "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "clarity-gate",
@@ -2069,15 +2249,6 @@
"risk": "safe",
"source": "https://github.com/frmoretto/clarity-gate"
},
- {
- "id": "claude-code-guide",
- "path": "skills/claude-code-guide",
- "category": "uncategorized",
- "name": "Claude Code Guide",
- "description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \"Thinking\" keywords, debugging techniques, and best practices for interacting with the agent.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "claude-ally-health",
"path": "skills/claude-ally-health",
@@ -2087,6 +2258,24 @@
"risk": "safe",
"source": "https://github.com/huifer/Claude-Ally-Health"
},
+ {
+ "id": "claude-code-guide",
+ "path": "skills/claude-code-guide",
+ "category": "uncategorized",
+ "name": "claude-code-guide",
+ "description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "claude-d3js-skill",
+ "path": "skills/claude-d3js-skill",
+ "category": "uncategorized",
+ "name": "claude-d3js-skill",
+ "description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "claude-scientific-skills",
"path": "skills/claude-scientific-skills",
@@ -2119,7 +2308,7 @@
"path": "skills/clean-code",
"category": "uncategorized",
"name": "clean-code",
- "description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design.",
+ "description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...",
"risk": "safe",
"source": "ClawForge (https://github.com/jackjin1997/ClawForge)"
},
@@ -2132,15 +2321,6 @@
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
- {
- "id": "cc-skill-clickhouse-io",
- "path": "skills/cc-skill-clickhouse-io",
- "category": "uncategorized",
- "name": "clickhouse-io",
- "description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "clickup-automation",
"path": "skills/clickup-automation",
@@ -2148,7 +2328,7 @@
"name": "clickup-automation",
"description": "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "close-automation",
@@ -2157,26 +2337,44 @@
"name": "close-automation",
"description": "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "cloud-penetration-testing",
- "path": "skills/cloud-penetration-testing",
- "category": "uncategorized",
- "name": "Cloud Penetration Testing",
- "description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfigurations\", \"test O365 security\", \"extract secrets from cloud environments\", or \"audit cloud infrastructure\". It provides comprehensive techniques for security assessment across major cloud platforms.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cloud-architect",
"path": "skills/cloud-architect",
"category": "uncategorized",
- "name": "cloud-architect",
- "description": "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies.",
+ "name": "Cloud Architect",
+ "description": "- Working on cloud architect tasks or workflows - Needing guidance, best practices, or checklists for cloud architect",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "cloud-devops",
+ "path": "skills/cloud-devops",
+ "category": "uncategorized",
+ "name": "cloud-devops",
+ "description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "cloud-penetration-testing",
+ "path": "skills/cloud-penetration-testing",
+ "category": "uncategorized",
+ "name": "cloud-penetration-testing",
+ "description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "cloudformation-best-practices",
+ "path": "skills/cloudformation-best-practices",
+ "category": "uncategorized",
+ "name": "cloudformation-best-practices",
+ "description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "coda-automation",
"path": "skills/coda-automation",
@@ -2184,25 +2382,25 @@
"name": "coda-automation",
"description": "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-documentation-code-explain",
"path": "skills/code-documentation-code-explain",
"category": "uncategorized",
"name": "code-documentation-code-explain",
- "description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations.",
+ "description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-documentation-doc-generate",
"path": "skills/code-documentation-doc-generate",
"category": "uncategorized",
"name": "code-documentation-doc-generate",
- "description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.",
+ "description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-refactoring-context-restore",
@@ -2211,16 +2409,16 @@
"name": "code-refactoring-context-restore",
"description": "Use when working with code refactoring context restore",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-refactoring-refactor-clean",
"path": "skills/code-refactoring-refactor-clean",
"category": "uncategorized",
"name": "code-refactoring-refactor-clean",
- "description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.",
+ "description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-refactoring-tech-debt",
@@ -2229,7 +2427,7 @@
"name": "code-refactoring-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-review-ai-ai-review",
@@ -2238,7 +2436,7 @@
"name": "code-review-ai-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-review-checklist",
@@ -2247,16 +2445,16 @@
"name": "code-review-checklist",
"description": "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-review-excellence",
"path": "skills/code-review-excellence",
"category": "uncategorized",
"name": "code-review-excellence",
- "description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.",
+ "description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "code-reviewer",
@@ -2265,25 +2463,25 @@
"name": "code-reviewer",
"description": "Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "codebase-cleanup-deps-audit",
"path": "skills/codebase-cleanup-deps-audit",
"category": "uncategorized",
"name": "codebase-cleanup-deps-audit",
- "description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.",
+ "description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "codebase-cleanup-refactor-clean",
"path": "skills/codebase-cleanup-refactor-clean",
"category": "uncategorized",
"name": "codebase-cleanup-refactor-clean",
- "description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.",
+ "description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "codebase-cleanup-tech-debt",
@@ -2292,7 +2490,7 @@
"name": "codebase-cleanup-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "codex-review",
@@ -2301,23 +2499,14 @@
"name": "codex-review",
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "cc-skill-coding-standards",
- "path": "skills/cc-skill-coding-standards",
- "category": "uncategorized",
- "name": "coding-standards",
- "description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "commit",
"path": "skills/commit",
"category": "uncategorized",
"name": "commit",
- "description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.",
+ "description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...",
"risk": "safe",
"source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit"
},
@@ -2325,8 +2514,8 @@
"id": "competitive-landscape",
"path": "skills/competitive-landscape",
"category": "uncategorized",
- "name": "competitive-landscape",
- "description": "This skill should be used when the user asks to \"analyze competitors\", \"assess competitive landscape\", \"identify differentiation\", \"evaluate market positioning\", \"apply Porter's Five Forces\", or requests competitive strategy analysis.",
+ "name": "Competitive Landscape",
+ "description": "Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.",
"risk": "unknown",
"source": "unknown"
},
@@ -2335,9 +2524,9 @@
"path": "skills/competitor-alternatives",
"category": "uncategorized",
"name": "competitor-alternatives",
- "description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.",
+ "description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "comprehensive-review-full-review",
@@ -2346,23 +2535,23 @@
"name": "comprehensive-review-full-review",
"description": "Use when working with comprehensive review full review",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "comprehensive-review-pr-enhance",
"path": "skills/comprehensive-review-pr-enhance",
"category": "uncategorized",
"name": "comprehensive-review-pr-enhance",
- "description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.",
+ "description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "computer-use-agents",
"path": "skills/computer-use-agents",
"category": "uncategorized",
"name": "computer-use-agents",
- "description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when: computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation.",
+ "description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -2373,7 +2562,7 @@
"name": "computer-vision-expert",
"description": "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "concise-planning",
@@ -2382,6 +2571,24 @@
"name": "concise-planning",
"description": "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "conductor-setup",
+ "path": "skills/conductor-setup",
+ "category": "uncategorized",
+ "name": "Conductor Setup",
+ "description": "Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "conductor-validator",
+ "path": "skills/conductor-validator",
+ "category": "uncategorized",
+ "name": "Conductor Validator",
+ "description": "ls -la conductor/",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -2391,7 +2598,7 @@
"name": "conductor-implement",
"description": "Execute tasks from a track's implementation plan following TDD workflow",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "conductor-manage",
@@ -2400,7 +2607,7 @@
"name": "conductor-manage",
"description": "Manage track lifecycle: archive, restore, delete, rename, and cleanup",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "conductor-new-track",
@@ -2409,7 +2616,7 @@
"name": "conductor-new-track",
"description": "Create a new track with specification and phased implementation plan",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "conductor-revert",
@@ -2418,16 +2625,7 @@
"name": "conductor-revert",
"description": "Git-aware undo by logical work unit (track, phase, or task)",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "conductor-setup",
- "path": "skills/conductor-setup",
- "category": "uncategorized",
- "name": "conductor-setup",
- "description": "Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "conductor-status",
@@ -2436,16 +2634,7 @@
"name": "conductor-status",
"description": "Display project status, active tracks, and next actions",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "conductor-validator",
- "path": "skills/conductor-validator",
- "category": "uncategorized",
- "name": "conductor-validator",
- "description": "Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "confluence-automation",
@@ -2454,6 +2643,15 @@
"name": "confluence-automation",
"description": "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "content-marketer",
+ "path": "skills/content-marketer",
+ "category": "uncategorized",
+ "name": "Content Marketer",
+ "description": "- Working on content marketer tasks or workflows - Needing guidance, best practices, or checklists for content marketer",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -2461,16 +2659,25 @@
"path": "skills/content-creator",
"category": "uncategorized",
"name": "content-creator",
- "description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.",
+ "description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "context-driven-development",
+ "path": "skills/context-driven-development",
+ "category": "uncategorized",
+ "name": "Context Driven Development",
+ "description": "Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.",
"risk": "unknown",
"source": "unknown"
},
{
- "id": "content-marketer",
- "path": "skills/content-marketer",
+ "id": "context-manager",
+ "path": "skills/context-manager",
"category": "uncategorized",
- "name": "content-marketer",
- "description": "Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content marketing.",
+ "name": "Context Manager",
+ "description": "- Working on context manager tasks or workflows - Needing guidance, best practices, or checklists for context manager",
"risk": "unknown",
"source": "unknown"
},
@@ -2492,15 +2699,6 @@
"risk": "safe",
"source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation"
},
- {
- "id": "context-driven-development",
- "path": "skills/context-driven-development",
- "category": "uncategorized",
- "name": "context-driven-development",
- "description": "Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "context-fundamentals",
"path": "skills/context-fundamentals",
@@ -2517,7 +2715,7 @@
"name": "context-management-context-restore",
"description": "Use when working with context management context restore",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "context-management-context-save",
@@ -2526,16 +2724,7 @@
"name": "context-management-context-save",
"description": "Use when working with context management context save",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "context-manager",
- "path": "skills/context-manager",
- "category": "uncategorized",
- "name": "context-manager",
- "description": "Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI orchestration.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "context-optimization",
@@ -2551,7 +2740,7 @@
"path": "skills/context-window-management",
"category": "uncategorized",
"name": "context-window-management",
- "description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.",
+ "description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -2562,7 +2751,7 @@
"name": "context7-auto-research",
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "conversation-memory",
@@ -2580,32 +2769,32 @@
"name": "convertkit-automation",
"description": "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "copilot-sdk",
"path": "skills/copilot-sdk",
"category": "uncategorized",
"name": "copilot-sdk",
- "description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session management, custom tools, streaming, hooks, MCP servers, BYOK providers, session persistence, and custom agents. Requires GitHub Copilot CLI installed and a GitHub Copilot subscription (unless using BYOK).",
+ "description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "copy-editing",
"path": "skills/copy-editing",
"category": "uncategorized",
"name": "copy-editing",
- "description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.",
+ "description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "copywriting",
"path": "skills/copywriting",
"category": "uncategorized",
- "name": "copywriting",
- "description": "Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.",
+ "name": "Copywriting",
+ "description": "Produce **clear, credible, and action-oriented marketing copy** that aligns with user intent and business goals.",
"risk": "unknown",
"source": "unknown"
},
@@ -2616,23 +2805,23 @@
"name": "core-components",
"description": "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cost-optimization",
"path": "skills/cost-optimization",
"category": "uncategorized",
"name": "cost-optimization",
- "description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.",
+ "description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cpp-pro",
"path": "skills/cpp-pro",
"category": "uncategorized",
- "name": "cpp-pro",
- "description": "Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.",
+ "name": "Cpp Pro",
+ "description": "- Working on cpp pro tasks or workflows - Needing guidance, best practices, or checklists for cpp pro",
"risk": "unknown",
"source": "unknown"
},
@@ -2643,7 +2832,7 @@
"name": "cqrs-implementation",
"description": "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "create-pr",
@@ -2659,34 +2848,25 @@
"path": "skills/crewai",
"category": "uncategorized",
"name": "crewai",
- "description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when: crewai, multi-agent team, agent roles, crew of agents, role-based agents.",
+ "description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
- {
- "id": "xss-html-injection",
- "path": "skills/xss-html-injection",
- "category": "uncategorized",
- "name": "Cross-Site Scripting and HTML Injection Testing",
- "description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "crypto-bd-agent",
"path": "skills/crypto-bd-agent",
"category": "uncategorized",
- "name": "crypto-bd-agent",
- "description": "Autonomous crypto business development patterns \u2014 multi-chain token discovery, 100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain identity, LLM cascade routing, and pipeline automation for CEX/DEX listing acquisition. Use when building AI agents for crypto BD, token evaluation, exchange listing outreach, or autonomous commerce with payment protocols.\n",
- "risk": "safe",
- "source": "community"
+ "name": "Crypto Bd Agent",
+ "description": "> Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.",
+ "risk": "unknown",
+ "source": "unknown"
},
{
"id": "csharp-pro",
"path": "skills/csharp-pro",
"category": "uncategorized",
- "name": "csharp-pro",
- "description": "Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.",
+ "name": "Csharp Pro",
+ "description": "- Working on csharp pro tasks or workflows - Needing guidance, best practices, or checklists for csharp pro",
"risk": "unknown",
"source": "unknown"
},
@@ -2703,17 +2883,8 @@
"id": "customer-support",
"path": "skills/customer-support",
"category": "uncategorized",
- "name": "customer-support",
- "description": "Elite AI-powered customer support specialist mastering conversational AI, automated ticketing, sentiment analysis, and omnichannel support experiences. Integrates modern support tools, chatbot platforms, and CX optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive customer experience management.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "claude-d3js-skill",
- "path": "skills/claude-d3js-skill",
- "category": "uncategorized",
- "name": "d3-viz",
- "description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.",
+ "name": "Customer Support",
+ "description": "- Working on customer support tasks or workflows - Needing guidance, best practices, or checklists for customer support",
"risk": "unknown",
"source": "unknown"
},
@@ -2724,14 +2895,23 @@
"name": "daily-news-report",
"description": "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-engineer",
"path": "skills/data-engineer",
"category": "uncategorized",
- "name": "data-engineer",
- "description": "Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.",
+ "name": "Data Engineer",
+ "description": "You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "data-scientist",
+ "path": "skills/data-scientist",
+ "category": "uncategorized",
+ "name": "Data Scientist",
+ "description": "- Working on data scientist tasks or workflows - Needing guidance, best practices, or checklists for data scientist",
"risk": "unknown",
"source": "unknown"
},
@@ -2742,7 +2922,7 @@
"name": "data-engineering-data-driven-feature",
"description": "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-engineering-data-pipeline",
@@ -2751,7 +2931,7 @@
"name": "data-engineering-data-pipeline",
"description": "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-quality-frameworks",
@@ -2760,32 +2940,41 @@
"name": "data-quality-frameworks",
"description": "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "data-scientist",
- "path": "skills/data-scientist",
- "category": "uncategorized",
- "name": "data-scientist",
- "description": "Expert data scientist for advanced analytics, machine learning, and statistical modeling. Handles complex data analysis, predictive modeling, and business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling, statistical analysis, and data-driven insights.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-storytelling",
"path": "skills/data-storytelling",
"category": "uncategorized",
"name": "data-storytelling",
- "description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.",
+ "description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "data-structure-protocol",
+ "path": "skills/data-structure-protocol",
+ "category": "uncategorized",
+ "name": "data-structure-protocol",
+ "description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
+ "risk": "safe",
+ "source": "https://github.com/k-kolomeitsev/data-structure-protocol"
+ },
+ {
+ "id": "database",
+ "path": "skills/database",
+ "category": "uncategorized",
+ "name": "database",
+ "description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "database-admin",
"path": "skills/database-admin",
"category": "uncategorized",
- "name": "database-admin",
- "description": "Expert database administrator specializing in modern cloud databases, automation, and reliability engineering. Masters AWS/Azure/GCP database services, Infrastructure as Code, high availability, disaster recovery, performance optimization, and compliance. Handles multi-cloud strategies, container databases, and cost optimization. Use PROACTIVELY for database architecture, operations, or reliability engineering.",
+ "name": "Database Admin",
+ "description": "- Working on database admin tasks or workflows - Needing guidance, best practices, or checklists for database admin",
"risk": "unknown",
"source": "unknown"
},
@@ -2793,8 +2982,17 @@
"id": "database-architect",
"path": "skills/database-architect",
"category": "uncategorized",
- "name": "database-architect",
- "description": "Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.",
+ "name": "Database Architect",
+ "description": "You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "database-optimizer",
+ "path": "skills/database-optimizer",
+ "category": "uncategorized",
+ "name": "Database Optimizer",
+ "description": "- Working on database optimizer tasks or workflows - Needing guidance, best practices, or checklists for database optimizer",
"risk": "unknown",
"source": "unknown"
},
@@ -2803,9 +3001,9 @@
"path": "skills/database-cloud-optimization-cost-optimize",
"category": "uncategorized",
"name": "database-cloud-optimization-cost-optimize",
- "description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.",
+ "description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-design",
@@ -2814,16 +3012,16 @@
"name": "database-design",
"description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-migration",
"path": "skills/database-migration",
"category": "uncategorized",
"name": "database-migration",
- "description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies.",
+ "description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-migrations-migration-observability",
@@ -2832,25 +3030,16 @@
"name": "database-migrations-migration-observability",
"description": "Migration monitoring, CDC, and observability infrastructure",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-migrations-sql-migrations",
"path": "skills/database-migrations-sql-migrations",
"category": "uncategorized",
"name": "database-migrations-sql-migrations",
- "description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server",
+ "description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "database-optimizer",
- "path": "skills/database-optimizer",
- "category": "uncategorized",
- "name": "database-optimizer",
- "description": "Expert database optimizer specializing in modern performance tuning, query optimization, and scalable architectures. Masters advanced indexing, N+1 resolution, multi-tier caching, partitioning strategies, and cloud database optimization. Handles complex query analysis, migration strategies, and performance monitoring. Use PROACTIVELY for database optimization, performance issues, or scalability challenges.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "datadog-automation",
@@ -2859,14 +3048,14 @@
"name": "datadog-automation",
"description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dbos-golang",
"path": "skills/dbos-golang",
"category": "uncategorized",
"name": "dbos-golang",
- "description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Client from external applications, or building Go applications that need to be resilient to failures.",
+ "description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie...",
"risk": "safe",
"source": "https://docs.dbos.dev/"
},
@@ -2875,7 +3064,7 @@
"path": "skills/dbos-python",
"category": "uncategorized",
"name": "dbos-python",
- "description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSClient from external applications, or building applications that need to be resilient to failures.",
+ "description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC...",
"risk": "safe",
"source": "https://docs.dbos.dev/"
},
@@ -2884,7 +3073,7 @@
"path": "skills/dbos-typescript",
"category": "uncategorized",
"name": "dbos-typescript",
- "description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, using DBOSClient from external applications, or building applications that need to be resilient to failures.",
+ "description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi...",
"risk": "safe",
"source": "https://docs.dbos.dev/"
},
@@ -2893,16 +3082,43 @@
"path": "skills/dbt-transformation-patterns",
"category": "uncategorized",
"name": "dbt-transformation-patterns",
- "description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.",
+ "description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "ddd-context-mapping",
+ "path": "skills/ddd-context-mapping",
+ "category": "uncategorized",
+ "name": "ddd-context-mapping",
+ "description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
+ "risk": "safe",
+ "source": "self"
+ },
+ {
+ "id": "ddd-strategic-design",
+ "path": "skills/ddd-strategic-design",
+ "category": "uncategorized",
+ "name": "ddd-strategic-design",
+ "description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
+ "risk": "safe",
+ "source": "self"
+ },
+ {
+ "id": "ddd-tactical-patterns",
+ "path": "skills/ddd-tactical-patterns",
+ "category": "uncategorized",
+ "name": "ddd-tactical-patterns",
+ "description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "debugger",
"path": "skills/debugger",
"category": "uncategorized",
- "name": "debugger",
- "description": "Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.",
+ "name": "Debugger",
+ "description": "- Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger",
"risk": "unknown",
"source": "unknown"
},
@@ -2911,9 +3127,9 @@
"path": "skills/debugging-strategies",
"category": "uncategorized",
"name": "debugging-strategies",
- "description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.",
+ "description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "debugging-toolkit-smart-debug",
@@ -2922,14 +3138,14 @@
"name": "debugging-toolkit-smart-debug",
"description": "Use when working with debugging toolkit smart debug",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deep-research",
"path": "skills/deep-research",
"category": "uncategorized",
"name": "deep-research",
- "description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 minutes but produces detailed, cited reports. Costs $2-5 per task.",
+ "description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ...",
"risk": "safe",
"source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research"
},
@@ -2940,32 +3156,32 @@
"name": "defi-protocol-templates",
"description": "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dependency-management-deps-audit",
"path": "skills/dependency-management-deps-audit",
"category": "uncategorized",
"name": "dependency-management-deps-audit",
- "description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.",
+ "description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dependency-upgrade",
"path": "skills/dependency-upgrade",
"category": "uncategorized",
"name": "dependency-upgrade",
- "description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.",
+ "description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deployment-engineer",
"path": "skills/deployment-engineer",
"category": "uncategorized",
- "name": "deployment-engineer",
- "description": "Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.",
+ "name": "Deployment Engineer",
+ "description": "You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.",
"risk": "unknown",
"source": "unknown"
},
@@ -2974,9 +3190,9 @@
"path": "skills/deployment-pipeline-design",
"category": "uncategorized",
"name": "deployment-pipeline-design",
- "description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.",
+ "description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deployment-procedures",
@@ -2985,7 +3201,7 @@
"name": "deployment-procedures",
"description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deployment-validation-config-validate",
@@ -2994,7 +3210,7 @@
"name": "deployment-validation-config-validate",
"description": "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "design-md",
@@ -3012,14 +3228,23 @@
"name": "design-orchestration",
"description": "Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "development",
+ "path": "skills/development",
+ "category": "uncategorized",
+ "name": "development",
+ "description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "devops-troubleshooter",
"path": "skills/devops-troubleshooter",
"category": "uncategorized",
- "name": "devops-troubleshooter",
- "description": "Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.",
+ "name": "Devops Troubleshooter",
+ "description": "- Working on devops troubleshooter tasks or workflows - Needing guidance, best practices, or checklists for devops troubleshooter",
"risk": "unknown",
"source": "unknown"
},
@@ -3030,7 +3255,7 @@
"name": "discord-automation",
"description": "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "discord-bot-architect",
@@ -3048,32 +3273,32 @@
"name": "dispatching-parallel-agents",
"description": "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "distributed-debugging-debug-trace",
"path": "skills/distributed-debugging-debug-trace",
"category": "uncategorized",
"name": "distributed-debugging-debug-trace",
- "description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.",
+ "description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "distributed-tracing",
"path": "skills/distributed-tracing",
"category": "uncategorized",
"name": "distributed-tracing",
- "description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.",
+ "description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "django-pro",
"path": "skills/django-pro",
"category": "uncategorized",
- "name": "django-pro",
- "description": "Master Django 5.x with async views, DRF, Celery, and Django Channels. Build scalable web applications with proper architecture, testing, and deployment. Use PROACTIVELY for Django development, ORM optimization, or complex Django patterns.",
+ "name": "Django Pro",
+ "description": "- Working on django pro tasks or workflows - Needing guidance, best practices, or checklists for django pro",
"risk": "unknown",
"source": "unknown"
},
@@ -3082,36 +3307,45 @@
"path": "skills/doc-coauthoring",
"category": "uncategorized",
"name": "doc-coauthoring",
- "description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",
+ "description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "docker-expert",
"path": "skills/docker-expert",
"category": "uncategorized",
"name": "docker-expert",
- "description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY for Dockerfile optimization, container issues, image size problems, security hardening, networking, and orchestration challenges.",
+ "description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "docs-architect",
"path": "skills/docs-architect",
"category": "uncategorized",
- "name": "docs-architect",
- "description": "Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.",
+ "name": "Docs Architect",
+ "description": "- Working on docs architect tasks or workflows - Needing guidance, best practices, or checklists for docs architect",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "documentation",
+ "path": "skills/documentation",
+ "category": "uncategorized",
+ "name": "documentation",
+ "description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "documentation-generation-doc-generate",
"path": "skills/documentation-generation-doc-generate",
"category": "uncategorized",
"name": "documentation-generation-doc-generate",
- "description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.",
+ "description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "documentation-templates",
@@ -3120,7 +3354,7 @@
"name": "documentation-templates",
"description": "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "docusign-automation",
@@ -3129,23 +3363,32 @@
"name": "docusign-automation",
"description": "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "docx-official",
"path": "skills/docx-official",
"category": "uncategorized",
- "name": "docx",
- "description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks",
+ "name": "docx-official",
+ "description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "domain-driven-design",
+ "path": "skills/domain-driven-design",
+ "category": "uncategorized",
+ "name": "domain-driven-design",
+ "description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "dotnet-architect",
"path": "skills/dotnet-architect",
"category": "uncategorized",
- "name": "dotnet-architect",
- "description": "Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns. Masters async/await, dependency injection, caching strategies, and performance optimization. Use PROACTIVELY for .NET API development, code review, or architecture decisions.",
+ "name": "Dotnet Architect",
+ "description": "- Working on dotnet architect tasks or workflows - Needing guidance, best practices, or checklists for dotnet architect",
"risk": "unknown",
"source": "unknown"
},
@@ -3163,9 +3406,18 @@
"path": "skills/dotnet-backend-patterns",
"category": "uncategorized",
"name": "dotnet-backend-patterns",
- "description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.",
+ "description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "draw",
+ "path": "skills/libreoffice/draw",
+ "category": "libreoffice",
+ "name": "draw",
+ "description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "dropbox-automation",
@@ -3174,32 +3426,41 @@
"name": "dropbox-automation",
"description": "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dx-optimizer",
"path": "skills/dx-optimizer",
"category": "uncategorized",
- "name": "dx-optimizer",
- "description": "Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.",
+ "name": "Dx Optimizer",
+ "description": "- Working on dx optimizer tasks or workflows - Needing guidance, best practices, or checklists for dx optimizer",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "e2e-testing",
+ "path": "skills/e2e-testing",
+ "category": "uncategorized",
+ "name": "e2e-testing",
+ "description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "e2e-testing-patterns",
"path": "skills/e2e-testing-patterns",
"category": "uncategorized",
"name": "e2e-testing-patterns",
- "description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.",
+ "description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "elixir-pro",
"path": "skills/elixir-pro",
"category": "uncategorized",
- "name": "elixir-pro",
- "description": "Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM optimizations.",
+ "name": "Elixir Pro",
+ "description": "- Working on elixir pro tasks or workflows - Needing guidance, best practices, or checklists for elixir pro",
"risk": "unknown",
"source": "unknown"
},
@@ -3208,16 +3469,16 @@
"path": "skills/email-sequence",
"category": "uncategorized",
"name": "email-sequence",
- "description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campaign,\" \"nurture sequence,\" \"onboarding emails,\" \"welcome sequence,\" \"re-engagement emails,\" \"email automation,\" or \"lifecycle emails.\" For in-app onboarding, see onboarding-cro.",
+ "description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "email-systems",
"path": "skills/email-systems",
"category": "uncategorized",
"name": "email-systems",
- "description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.",
+ "description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -3226,18 +3487,18 @@
"path": "skills/embedding-strategies",
"category": "uncategorized",
"name": "embedding-strategies",
- "description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.",
+ "description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "employment-contract-templates",
"path": "skills/employment-contract-templates",
"category": "uncategorized",
"name": "employment-contract-templates",
- "description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.",
+ "description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "environment-setup-guide",
@@ -3246,6 +3507,15 @@
"name": "environment-setup-guide",
"description": "Guide developers through setting up development environments with proper tools, dependencies, and configurations",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "error-detective",
+ "path": "skills/error-detective",
+ "category": "uncategorized",
+ "name": "Error Detective",
+ "description": "- Working on error detective tasks or workflows - Needing guidance, best practices, or checklists for error detective",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -3255,16 +3525,16 @@
"name": "error-debugging-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-debugging-error-trace",
"path": "skills/error-debugging-error-trace",
"category": "uncategorized",
"name": "error-debugging-error-trace",
- "description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.",
+ "description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-debugging-multi-agent-review",
@@ -3273,16 +3543,7 @@
"name": "error-debugging-multi-agent-review",
"description": "Use when working with error debugging multi agent review",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "error-detective",
- "path": "skills/error-detective",
- "category": "uncategorized",
- "name": "error-detective",
- "description": "Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-diagnostics-error-analysis",
@@ -3291,7 +3552,7 @@
"name": "error-diagnostics-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-diagnostics-error-trace",
@@ -3300,7 +3561,7 @@
"name": "error-diagnostics-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-diagnostics-smart-debug",
@@ -3309,25 +3570,25 @@
"name": "error-diagnostics-smart-debug",
"description": "Use when working with error diagnostics smart debug",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "error-handling-patterns",
"path": "skills/error-handling-patterns",
"category": "uncategorized",
"name": "error-handling-patterns",
- "description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.",
+ "description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ethical-hacking-methodology",
"path": "skills/ethical-hacking-methodology",
"category": "uncategorized",
- "name": "Ethical Hacking Methodology",
- "description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit vulnerabilities\", or \"write penetration test reports\". It provides comprehensive ethical hacking methodology and techniques.",
+ "name": "ethical-hacking-methodology",
+ "description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "evaluation",
@@ -3343,9 +3604,9 @@
"path": "skills/event-sourcing-architect",
"category": "uncategorized",
"name": "event-sourcing-architect",
- "description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries.",
+ "description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "event-store-design",
@@ -3354,7 +3615,7 @@
"name": "event-store-design",
"description": "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "exa-search",
@@ -3363,7 +3624,7 @@
"name": "exa-search",
"description": "Semantic search, similar content discovery, and structured research using Exa API",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "executing-plans",
@@ -3372,7 +3633,7 @@
"name": "executing-plans",
"description": "Use when you have a written implementation plan to execute in a separate session with review checkpoints",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "expo-deployment",
@@ -3441,8 +3702,8 @@
"id": "fastapi-pro",
"path": "skills/fastapi-pro",
"category": "uncategorized",
- "name": "fastapi-pro",
- "description": "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.",
+ "name": "Fastapi Pro",
+ "description": "- Working on fastapi pro tasks or workflows - Needing guidance, best practices, or checklists for fastapi pro",
"risk": "unknown",
"source": "unknown"
},
@@ -3451,9 +3712,9 @@
"path": "skills/fastapi-router-py",
"category": "uncategorized",
"name": "fastapi-router-py",
- "description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.",
+ "description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fastapi-templates",
@@ -3462,7 +3723,7 @@
"name": "fastapi-templates",
"description": "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ffuf-claude-skill",
@@ -3480,32 +3741,32 @@
"name": "figma-automation",
"description": "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "file-path-traversal",
- "path": "skills/file-path-traversal",
- "category": "uncategorized",
- "name": "File Path Traversal Testing",
- "description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vulnerabilities\", or \"access files outside web root\". It provides comprehensive file path traversal attack and testing methodologies.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "file-organizer",
"path": "skills/file-organizer",
"category": "uncategorized",
"name": "file-organizer",
- "description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.",
+ "description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "file-path-traversal",
+ "path": "skills/file-path-traversal",
+ "category": "uncategorized",
+ "name": "file-path-traversal",
+ "description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu...",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "file-uploads",
"path": "skills/file-uploads",
"category": "uncategorized",
"name": "file-uploads",
- "description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: file upload, S3, R2, presigned URL, multipart.",
+ "description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -3525,14 +3786,14 @@
"name": "finishing-a-development-branch",
"description": "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "firebase",
"path": "skills/firebase",
"category": "uncategorized",
"name": "firebase",
- "description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I",
+ "description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -3543,14 +3804,14 @@
"name": "firecrawl-scraper",
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "firmware-analyst",
"path": "skills/firmware-analyst",
"category": "uncategorized",
- "name": "firmware-analyst",
- "description": "Expert firmware analyst specializing in embedded systems, IoT security, and hardware reverse engineering. Masters firmware extraction, analysis, and vulnerability research for routers, IoT devices, automotive systems, and industrial controllers. Use PROACTIVELY for firmware security audits, IoT penetration testing, or embedded systems research.",
+ "name": "Firmware Analyst",
+ "description": "wget http://vendor.com/firmware/update.bin",
"risk": "unknown",
"source": "unknown"
},
@@ -3567,8 +3828,8 @@
"id": "flutter-expert",
"path": "skills/flutter-expert",
"category": "uncategorized",
- "name": "flutter-expert",
- "description": "Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.",
+ "name": "Flutter Expert",
+ "description": "- Working on flutter expert tasks or workflows - Needing guidance, best practices, or checklists for flutter expert",
"risk": "unknown",
"source": "unknown"
},
@@ -3576,8 +3837,8 @@
"id": "form-cro",
"path": "skills/form-cro",
"category": "uncategorized",
- "name": "form-cro",
- "description": "Optimize any form that is NOT signup or account registration \u2014 including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.",
+ "name": "Form Cro",
+ "description": "You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**.",
"risk": "unknown",
"source": "unknown"
},
@@ -3615,7 +3876,7 @@
"name": "framework-migration-code-migrate",
"description": "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "framework-migration-deps-upgrade",
@@ -3624,7 +3885,7 @@
"name": "framework-migration-deps-upgrade",
"description": "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "framework-migration-legacy-modernize",
@@ -3633,16 +3894,16 @@
"name": "framework-migration-legacy-modernize",
"description": "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "free-tool-strategy",
"path": "skills/free-tool-strategy",
"category": "uncategorized",
"name": "free-tool-strategy",
- "description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as marketing,\" \"free tool,\" \"marketing tool,\" \"calculator,\" \"generator,\" \"interactive tool,\" \"lead gen tool,\" \"build a tool for leads,\" or \"free resource.\" This skill bridges engineering and marketing \u2014 useful for founders and technical marketers.",
+ "description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "freshdesk-automation",
@@ -3651,7 +3912,7 @@
"name": "freshdesk-automation",
"description": "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "freshservice-automation",
@@ -3660,6 +3921,24 @@
"name": "freshservice-automation",
"description": "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "frontend-developer",
+ "path": "skills/frontend-developer",
+ "category": "uncategorized",
+ "name": "Frontend Developer",
+ "description": "You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "frontend-security-coder",
+ "path": "skills/frontend-security-coder",
+ "category": "uncategorized",
+ "name": "Frontend Security Coder",
+ "description": "- Working on frontend security coder tasks or workflows - Needing guidance, best practices, or checklists for frontend security coder",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -3667,27 +3946,18 @@
"path": "skills/frontend-design",
"category": "uncategorized",
"name": "frontend-design",
- "description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboards, or frontend applications.",
+ "description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "frontend-dev-guidelines",
"path": "skills/frontend-dev-guidelines",
"category": "uncategorized",
"name": "frontend-dev-guidelines",
- "description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router, performance optimization, and strict TypeScript practices.",
+ "description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "frontend-developer",
- "path": "skills/frontend-developer",
- "category": "uncategorized",
- "name": "frontend-developer",
- "description": "Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "frontend-mobile-development-component-scaffold",
@@ -3696,7 +3966,7 @@
"name": "frontend-mobile-development-component-scaffold",
"description": "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "frontend-mobile-security-xss-scan",
@@ -3705,32 +3975,14 @@
"name": "frontend-mobile-security-xss-scan",
"description": "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "cc-skill-frontend-patterns",
- "path": "skills/cc-skill-frontend-patterns",
- "category": "uncategorized",
- "name": "frontend-patterns",
- "description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "frontend-security-coder",
- "path": "skills/frontend-security-coder",
- "category": "uncategorized",
- "name": "frontend-security-coder",
- "description": "Expert in secure frontend coding practices specializing in XSS prevention, output sanitization, and client-side security patterns. Use PROACTIVELY for frontend security implementations or client-side security code reviews.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "frontend-slides",
"path": "skills/frontend-slides",
"category": "uncategorized",
"name": "frontend-slides",
- "description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.",
+ "description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a...",
"risk": "safe",
"source": "https://github.com/zarazhangrui/frontend-slides"
},
@@ -3739,9 +3991,9 @@
"path": "skills/frontend-ui-dark-ts",
"category": "uncategorized",
"name": "frontend-ui-dark-ts",
- "description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.",
+ "description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "full-stack-orchestration-full-stack-feature",
@@ -3750,7 +4002,7 @@
"name": "full-stack-orchestration-full-stack-feature",
"description": "Use when working with full stack orchestration full stack feature",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "game-art",
@@ -3759,7 +4011,7 @@
"name": "game-art",
"description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "game-audio",
@@ -3768,7 +4020,7 @@
"name": "game-audio",
"description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "game-design",
@@ -3777,7 +4029,7 @@
"name": "game-design",
"description": "Game design principles. GDD structure, balancing, player psychology, progression.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "game-development",
@@ -3786,14 +4038,14 @@
"name": "game-development",
"description": "Game development orchestrator. Routes to platform-specific skills based on project needs.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gcp-cloud-run",
"path": "skills/gcp-cloud-run",
"category": "uncategorized",
"name": "gcp-cloud-run",
- "description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.",
+ "description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -3802,18 +4054,18 @@
"path": "skills/gdpr-data-handling",
"category": "uncategorized",
"name": "gdpr-data-handling",
- "description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.",
+ "description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gemini-api-dev",
"path": "skills/gemini-api-dev",
"category": "uncategorized",
"name": "gemini-api-dev",
- "description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript), model selection, and API capabilities.",
+ "description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "geo-fundamentals",
@@ -3822,16 +4074,16 @@
"name": "geo-fundamentals",
"description": "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "git-advanced-workflows",
"path": "skills/git-advanced-workflows",
"category": "uncategorized",
"name": "git-advanced-workflows",
- "description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.",
+ "description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "git-pr-workflows-git-workflow",
@@ -3840,7 +4092,7 @@
"name": "git-pr-workflows-git-workflow",
"description": "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "git-pr-workflows-onboard",
@@ -3849,7 +4101,7 @@
"name": "git-pr-workflows-onboard",
"description": "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "git-pr-workflows-pr-enhance",
@@ -3858,25 +4110,25 @@
"name": "git-pr-workflows-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "git-pushing",
"path": "skills/git-pushing",
"category": "uncategorized",
"name": "git-pushing",
- "description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says \"push changes\", \"commit and push\", \"push this\", \"push to github\", or similar git workflow requests.",
+ "description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "github-actions-templates",
"path": "skills/github-actions-templates",
"category": "uncategorized",
"name": "github-actions-templates",
- "description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.",
+ "description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "github-automation",
@@ -3885,25 +4137,25 @@
"name": "github-automation",
"description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "github-issue-creator",
"path": "skills/github-issue-creator",
"category": "uncategorized",
"name": "github-issue-creator",
- "description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.",
+ "description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "github-workflow-automation",
"path": "skills/github-workflow-automation",
"category": "uncategorized",
"name": "github-workflow-automation",
- "description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creating GitHub Actions, or triaging issues.",
+ "description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gitlab-automation",
@@ -3912,25 +4164,25 @@
"name": "gitlab-automation",
"description": "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gitlab-ci-patterns",
"path": "skills/gitlab-ci-patterns",
"category": "uncategorized",
"name": "gitlab-ci-patterns",
- "description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.",
+ "description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gitops-workflow",
"path": "skills/gitops-workflow",
"category": "uncategorized",
"name": "gitops-workflow",
- "description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.",
+ "description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "gmail-automation",
@@ -3939,7 +4191,7 @@
"name": "gmail-automation",
"description": "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "go-concurrency-patterns",
@@ -3948,7 +4200,7 @@
"name": "go-concurrency-patterns",
"description": "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "go-playwright",
@@ -3968,6 +4220,15 @@
"risk": "safe",
"source": "https://github.com/go-rod/rod"
},
+ {
+ "id": "godot-4-migration",
+ "path": "skills/godot-4-migration",
+ "category": "uncategorized",
+ "name": "godot-4-migration",
+ "description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "godot-gdscript-patterns",
"path": "skills/godot-gdscript-patterns",
@@ -3975,14 +4236,14 @@
"name": "godot-gdscript-patterns",
"description": "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "golang-pro",
"path": "skills/golang-pro",
"category": "uncategorized",
- "name": "golang-pro",
- "description": "Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.",
+ "name": "Golang Pro",
+ "description": "You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.",
"risk": "unknown",
"source": "unknown"
},
@@ -3993,25 +4254,25 @@
"name": "google-analytics-automation",
"description": "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "google-calendar-automation",
"path": "skills/google-calendar-automation",
"category": "uncategorized",
"name": "google-calendar-automation",
- "description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatically.",
+ "description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "google-drive-automation",
"path": "skills/google-drive-automation",
"category": "uncategorized",
"name": "google-drive-automation",
- "description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives programmatically.",
+ "description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "googlesheets-automation",
@@ -4020,23 +4281,23 @@
"name": "googlesheets-automation",
"description": "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "grafana-dashboards",
"path": "skills/grafana-dashboards",
"category": "uncategorized",
"name": "grafana-dashboards",
- "description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces.",
+ "description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "graphql",
"path": "skills/graphql",
"category": "uncategorized",
"name": "graphql",
- "description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.",
+ "description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4044,8 +4305,8 @@
"id": "graphql-architect",
"path": "skills/graphql-architect",
"category": "uncategorized",
- "name": "graphql-architect",
- "description": "Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems. Use PROACTIVELY for GraphQL architecture or performance optimization.",
+ "name": "Graphql Architect",
+ "description": "- Working on graphql architect tasks or workflows - Needing guidance, best practices, or checklists for graphql architect",
"risk": "unknown",
"source": "unknown"
},
@@ -4056,16 +4317,16 @@
"name": "haskell-pro",
"description": "Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "helm-chart-scaffolding",
"path": "skills/helm-chart-scaffolding",
"category": "uncategorized",
"name": "helm-chart-scaffolding",
- "description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.",
+ "description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "helpdesk-automation",
@@ -4074,6 +4335,132 @@
"name": "helpdesk-automation",
"description": "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "hig-components-content",
+ "path": "skills/hig-components-content",
+ "category": "uncategorized",
+ "name": "Hig Components Content",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-controls",
+ "path": "skills/hig-components-controls",
+ "category": "uncategorized",
+ "name": "Hig Components Controls",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-dialogs",
+ "path": "skills/hig-components-dialogs",
+ "category": "uncategorized",
+ "name": "Hig Components Dialogs",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-layout",
+ "path": "skills/hig-components-layout",
+ "category": "uncategorized",
+ "name": "Hig Components Layout",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-menus",
+ "path": "skills/hig-components-menus",
+ "category": "uncategorized",
+ "name": "Hig Components Menus",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-search",
+ "path": "skills/hig-components-search",
+ "category": "uncategorized",
+ "name": "Hig Components Search",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-status",
+ "path": "skills/hig-components-status",
+ "category": "uncategorized",
+ "name": "Hig Components Status",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-components-system",
+ "path": "skills/hig-components-system",
+ "category": "uncategorized",
+ "name": "Hig Components System",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-foundations",
+ "path": "skills/hig-foundations",
+ "category": "uncategorized",
+ "name": "Hig Foundations",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-inputs",
+ "path": "skills/hig-inputs",
+ "category": "uncategorized",
+ "name": "Hig Inputs",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-patterns",
+ "path": "skills/hig-patterns",
+ "category": "uncategorized",
+ "name": "Hig Patterns",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-platforms",
+ "path": "skills/hig-platforms",
+ "category": "uncategorized",
+ "name": "Hig Platforms",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-project-context",
+ "path": "skills/hig-project-context",
+ "category": "uncategorized",
+ "name": "Hig Project Context",
+ "description": "Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "hig-technologies",
+ "path": "skills/hig-technologies",
+ "category": "uncategorized",
+ "name": "Hig Technologies",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -4081,16 +4468,16 @@
"path": "skills/hosted-agents-v2-py",
"category": "uncategorized",
"name": "hosted-agents-v2-py",
- "description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition.\nUse when creating container-based agents that run custom code in Azure AI Foundry.\nTriggers: \"ImageBasedHostedAgentDefinition\", \"hosted agent\", \"container agent\", \n\"create_version\", \"ProtocolVersionRecord\", \"AgentProtocol.RESPONSES\".\n",
+ "description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hr-pro",
"path": "skills/hr-pro",
"category": "uncategorized",
- "name": "hr-pro",
- "description": "Professional, ethical HR partner for hiring, onboarding/offboarding, PTO and leave, performance, compliant policies, and employee relations. Ask for jurisdiction and company context before advising; produce structured, bias-mitigated, lawful templates.",
+ "name": "Hr Pro",
+ "description": "- Working on hr pro tasks or workflows - Needing guidance, best practices, or checklists for hr pro",
"risk": "unknown",
"source": "unknown"
},
@@ -4098,10 +4485,10 @@
"id": "html-injection-testing",
"path": "skills/html-injection-testing",
"category": "uncategorized",
- "name": "HTML Injection Testing",
- "description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test content injection vulnerabilities\". It provides comprehensive HTML injection attack techniques and testing methodologies.",
+ "name": "html-injection-testing",
+ "description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hubspot-automation",
@@ -4110,14 +4497,14 @@
"name": "hubspot-automation",
"description": "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hubspot-integration",
"path": "skills/hubspot-integration",
"category": "uncategorized",
"name": "hubspot-integration",
- "description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubspot, hubspot api, hubspot crm, hubspot integration, contacts api.",
+ "description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4126,7 +4513,7 @@
"path": "skills/hugging-face-cli",
"category": "uncategorized",
"name": "hugging-face-cli",
- "description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run compute jobs on HF infrastructure. Covers authentication, file transfers, repository creation, cache operations, and cloud compute.",
+ "description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...",
"risk": "safe",
"source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli"
},
@@ -4135,7 +4522,7 @@
"path": "skills/hugging-face-jobs",
"category": "uncategorized",
"name": "hugging-face-jobs",
- "description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tokens, secrets management, timeout configuration, and result persistence. Designed for general-purpose compute workloads including data processing, inference, experiments, batch jobs, and any Python-based tasks. Should be invoked for tasks involving cloud compute, GPU workloads, or when users mention running jobs on Hugging Face infrastructure without local setup.",
+ "description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok...",
"risk": "safe",
"source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs"
},
@@ -4143,8 +4530,8 @@
"id": "hybrid-cloud-architect",
"path": "skills/hybrid-cloud-architect",
"category": "uncategorized",
- "name": "hybrid-cloud-architect",
- "description": "Expert hybrid cloud architect specializing in complex multi-cloud solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters hybrid connectivity, workload placement optimization, edge computing, and cross-cloud automation. Handles compliance, cost optimization, disaster recovery, and migration strategies. Use PROACTIVELY for hybrid architecture, multi-cloud strategy, or complex infrastructure integration.",
+ "name": "Hybrid Cloud Architect",
+ "description": "- Working on hybrid cloud architect tasks or workflows - Needing guidance, best practices, or checklists for hybrid cloud architect",
"risk": "unknown",
"source": "unknown"
},
@@ -4153,9 +4540,9 @@
"path": "skills/hybrid-cloud-networking",
"category": "uncategorized",
"name": "hybrid-cloud-networking",
- "description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.",
+ "description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hybrid-search-implementation",
@@ -4164,7 +4551,7 @@
"name": "hybrid-search-implementation",
"description": "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "i18n-localization",
@@ -4173,32 +4560,41 @@
"name": "i18n-localization",
"description": "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "idor-testing",
"path": "skills/idor-testing",
"category": "uncategorized",
- "name": "IDOR Vulnerability Testing",
- "description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or object references,\" or \"bypass authorization to access other users' data.\" It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.",
+ "name": "idor-testing",
+ "description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "imagen",
"path": "skills/imagen",
"category": "uncategorized",
"name": "imagen",
- "description": "This skill generates images using Google Gemini's image generation model (`gemini-3-pro-image-preview`). It enables seamless image creation during any Claude Code session - whether you're building frontend UIs, creating documentation, or need visual",
+ "description": "|",
"risk": "safe",
"source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
},
+ {
+ "id": "impress",
+ "path": "skills/libreoffice/impress",
+ "category": "libreoffice",
+ "name": "impress",
+ "description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "incident-responder",
"path": "skills/incident-responder",
"category": "uncategorized",
- "name": "incident-responder",
- "description": "Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.",
+ "name": "Incident Responder",
+ "description": "- Working on incident responder tasks or workflows - Needing guidance, best practices, or checklists for incident responder",
"risk": "unknown",
"source": "unknown"
},
@@ -4209,7 +4605,7 @@
"name": "incident-response-incident-response",
"description": "Use when working with incident response incident response",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "incident-response-smart-fix",
@@ -4218,22 +4614,22 @@
"name": "incident-response-smart-fix",
"description": "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "incident-runbook-templates",
"path": "skills/incident-runbook-templates",
"category": "uncategorized",
"name": "incident-runbook-templates",
- "description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.",
+ "description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "infinite-gratitude",
"path": "skills/infinite-gratitude",
"category": "uncategorized",
- "name": "Infinite Gratitude",
+ "name": "infinite-gratitude",
"description": "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).",
"risk": "safe",
"source": "https://github.com/sstklen/infinite-gratitude"
@@ -4243,7 +4639,7 @@
"path": "skills/inngest",
"category": "uncategorized",
"name": "inngest",
- "description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven workflow, step function, durable execution.",
+ "description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4254,14 +4650,14 @@
"name": "instagram-automation",
"description": "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "interactive-portfolio",
"path": "skills/interactive-portfolio",
"category": "uncategorized",
"name": "interactive-portfolio",
- "description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities. Use when: portfolio, personal website, showcase work, developer portfolio, designer portfolio.",
+ "description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4272,32 +4668,32 @@
"name": "intercom-automation",
"description": "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "internal-comms-anthropic",
"path": "skills/internal-comms-anthropic",
"category": "uncategorized",
- "name": "internal-comms",
- "description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",
+ "name": "internal-comms-anthropic",
+ "description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "internal-comms-community",
"path": "skills/internal-comms-community",
"category": "uncategorized",
- "name": "internal-comms",
- "description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",
+ "name": "internal-comms-community",
+ "description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ios-developer",
"path": "skills/ios-developer",
"category": "uncategorized",
- "name": "ios-developer",
- "description": "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.",
+ "name": "Ios Developer",
+ "description": "- Working on ios developer tasks or workflows - Needing guidance, best practices, or checklists for ios developer",
"risk": "unknown",
"source": "unknown"
},
@@ -4306,9 +4702,9 @@
"path": "skills/istio-traffic-management",
"category": "uncategorized",
"name": "istio-traffic-management",
- "description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.",
+ "description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "iterate-pr",
@@ -4323,8 +4719,17 @@
"id": "java-pro",
"path": "skills/java-pro",
"category": "uncategorized",
- "name": "java-pro",
- "description": "Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.",
+ "name": "Java Pro",
+ "description": "- Working on java pro tasks or workflows - Needing guidance, best practices, or checklists for java pro",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "javascript-pro",
+ "path": "skills/javascript-pro",
+ "category": "uncategorized",
+ "name": "Javascript Pro",
+ "description": "You are a JavaScript expert specializing in modern JS and async programming.",
"risk": "unknown",
"source": "unknown"
},
@@ -4333,27 +4738,18 @@
"path": "skills/javascript-mastery",
"category": "uncategorized",
"name": "javascript-mastery",
- "description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional programming. Use when explaining JS concepts, debugging JavaScript issues, or teaching JavaScript fundamentals.",
+ "description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "javascript-pro",
- "path": "skills/javascript-pro",
- "category": "uncategorized",
- "name": "javascript-pro",
- "description": "Master modern JavaScript with ES6+, async patterns, and Node.js APIs. Handles promises, event loops, and browser/Node compatibility. Use PROACTIVELY for JavaScript optimization, async debugging, or complex JS patterns.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "javascript-testing-patterns",
"path": "skills/javascript-testing-patterns",
"category": "uncategorized",
"name": "javascript-testing-patterns",
- "description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.",
+ "description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "javascript-typescript-typescript-scaffold",
@@ -4362,7 +4758,7 @@
"name": "javascript-typescript-typescript-scaffold",
"description": "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "jira-automation",
@@ -4371,14 +4767,14 @@
"name": "jira-automation",
"description": "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "julia-pro",
"path": "skills/julia-pro",
"category": "uncategorized",
- "name": "julia-pro",
- "description": "Master Julia 1.10+ with modern features, performance optimization, multiple dispatch, and production-ready practices. Expert in the Julia ecosystem including package management, scientific computing, and high-performance numerical code. Use PROACTIVELY for Julia development, optimization, or advanced Julia patterns.",
+ "name": "Julia Pro",
+ "description": "- Working on julia pro tasks or workflows - Needing guidance, best practices, or checklists for julia pro",
"risk": "unknown",
"source": "unknown"
},
@@ -4387,18 +4783,18 @@
"path": "skills/k8s-manifest-generator",
"category": "uncategorized",
"name": "k8s-manifest-generator",
- "description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.",
+ "description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "k8s-security-policies",
"path": "skills/k8s-security-policies",
"category": "uncategorized",
"name": "k8s-security-policies",
- "description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards.",
+ "description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "kaizen",
@@ -4407,7 +4803,7 @@
"name": "kaizen",
"description": "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "klaviyo-automation",
@@ -4416,41 +4812,59 @@
"name": "klaviyo-automation",
"description": "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "kotlin-coroutines-expert",
+ "path": "skills/kotlin-coroutines-expert",
+ "category": "uncategorized",
+ "name": "kotlin-coroutines-expert",
+ "description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "kpi-dashboard-design",
"path": "skills/kpi-dashboard-design",
"category": "uncategorized",
"name": "kpi-dashboard-design",
- "description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data visualization layouts.",
+ "description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "kubernetes-architect",
"path": "skills/kubernetes-architect",
"category": "uncategorized",
- "name": "kubernetes-architect",
- "description": "Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost optimization, and developer experience. Use PROACTIVELY for K8s architecture, GitOps implementation, or cloud-native platform design.",
+ "name": "Kubernetes Architect",
+ "description": "You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "kubernetes-deployment",
+ "path": "skills/kubernetes-deployment",
+ "category": "uncategorized",
+ "name": "kubernetes-deployment",
+ "description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "langchain-architecture",
"path": "skills/langchain-architecture",
"category": "uncategorized",
"name": "langchain-architecture",
- "description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM workflows.",
+ "description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "langfuse",
"path": "skills/langfuse",
"category": "uncategorized",
"name": "langfuse",
- "description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.",
+ "description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4459,7 +4873,7 @@
"path": "skills/langgraph",
"category": "uncategorized",
"name": "langgraph",
- "description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern. Used in production at LinkedIn, Uber, and 400+ companies. This is LangChain's recommended approach for building agents. Use when: langgraph, langchain agent, stateful agent, agent graph, react agent.",
+ "description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4488,23 +4902,23 @@
"name": "last30days",
"description": "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "launch-strategy",
"path": "skills/launch-strategy",
"category": "uncategorized",
"name": "launch-strategy",
- "description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.",
+ "description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "legacy-modernizer",
"path": "skills/legacy-modernizer",
"category": "uncategorized",
- "name": "legacy-modernizer",
- "description": "Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.",
+ "name": "Legacy Modernizer",
+ "description": "- Working on legacy modernizer tasks or workflows - Needing guidance, best practices, or checklists for legacy modernizer",
"risk": "unknown",
"source": "unknown"
},
@@ -4512,8 +4926,8 @@
"id": "legal-advisor",
"path": "skills/legal-advisor",
"category": "uncategorized",
- "name": "legal-advisor",
- "description": "Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.",
+ "name": "Legal Advisor",
+ "description": "- Working on legal advisor tasks or workflows - Needing guidance, best practices, or checklists for legal advisor",
"risk": "unknown",
"source": "unknown"
},
@@ -4524,7 +4938,7 @@
"name": "linear-automation",
"description": "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linear-claude-skill",
@@ -4542,52 +4956,61 @@
"name": "linkedin-automation",
"description": "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linkerd-patterns",
"path": "skills/linkerd-patterns",
"category": "uncategorized",
"name": "linkerd-patterns",
- "description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.",
+ "description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "lint-and-validate",
"path": "skills/lint-and-validate",
"category": "uncategorized",
"name": "lint-and-validate",
- "description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.",
+ "description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linux-privilege-escalation",
"path": "skills/linux-privilege-escalation",
"category": "uncategorized",
- "name": "Linux Privilege Escalation",
- "description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"exploit cron jobs for root access\", \"enumerate Linux systems for privilege escalation\", or \"gain root access from low-privilege shell\". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.",
+ "name": "linux-privilege-escalation",
+ "description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linux-shell-scripting",
"path": "skills/linux-shell-scripting",
"category": "uncategorized",
- "name": "Linux Production Shell Scripts",
- "description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production shell scripts\". It provides ready-to-use shell script templates for system administration.",
+ "name": "linux-shell-scripting",
+ "description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "linux-troubleshooting",
+ "path": "skills/linux-troubleshooting",
+ "category": "uncategorized",
+ "name": "linux-troubleshooting",
+ "description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "llm-app-patterns",
"path": "skills/llm-app-patterns",
"category": "uncategorized",
"name": "llm-app-patterns",
- "description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.",
+ "description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "llm-application-dev-ai-assistant",
@@ -4596,7 +5019,7 @@
"name": "llm-application-dev-ai-assistant",
"description": "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "llm-application-dev-langchain-agent",
@@ -4605,7 +5028,7 @@
"name": "llm-application-dev-langchain-agent",
"description": "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "llm-application-dev-prompt-optimize",
@@ -4614,32 +5037,32 @@
"name": "llm-application-dev-prompt-optimize",
"description": "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "llm-evaluation",
"path": "skills/llm-evaluation",
"category": "uncategorized",
"name": "llm-evaluation",
- "description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or establishing evaluation frameworks.",
+ "description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "loki-mode",
"path": "skills/loki-mode",
"category": "uncategorized",
"name": "loki-mode",
- "description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.",
+ "description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "m365-agents-dotnet",
"path": "skills/m365-agents-dotnet",
"category": "uncategorized",
- "name": "m365-agents-dotnet",
- "description": "Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"Microsoft.Agents\", \"AddAgentApplicationOptions\", \"AgentApplication\", \"AddAgentAspNetAuthentication\", \"Copilot Studio client\", \"IAgentHttpAdapter\".\n",
+ "name": "M365 Agents Dotnet",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft.Agents SDK with ASP.NET Core hosting, agent routing, and MSAL-based authentication.",
"risk": "unknown",
"source": "unknown"
},
@@ -4647,8 +5070,8 @@
"id": "m365-agents-py",
"path": "skills/m365-agents-py",
"category": "uncategorized",
- "name": "m365-agents-py",
- "description": "Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"microsoft_agents\", \"AgentApplication\", \"start_agent_process\", \"TurnContext\", \"Copilot Studio client\", \"CloudAdapter\".\n",
+ "name": "M365 Agents Py",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft Agents SDK with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based authentication.",
"risk": "unknown",
"source": "unknown"
},
@@ -4656,8 +5079,8 @@
"id": "m365-agents-ts",
"path": "skills/m365-agents-ts",
"category": "uncategorized",
- "name": "m365-agents-ts",
- "description": "Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: \"Microsoft 365 Agents SDK\", \"@microsoft/agents-hosting\", \"AgentApplication\", \"startServer\", \"streamingResponse\", \"Copilot Studio client\", \"@microsoft/agents-copilotstudio-client\".\n",
+ "name": "M365 Agents Ts",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft 365 Agents SDK with Express hosting, AgentApplication routing, streaming responses, and Copilot Studio client integrations.",
"risk": "unknown",
"source": "unknown"
},
@@ -4668,7 +5091,7 @@
"name": "machine-learning-ops-ml-pipeline",
"description": "Design and implement a complete ML pipeline for: $ARGUMENTS",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mailchimp-automation",
@@ -4677,7 +5100,7 @@
"name": "mailchimp-automation",
"description": "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "make-automation",
@@ -4686,7 +5109,7 @@
"name": "make-automation",
"description": "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "makepad-skills",
@@ -4701,17 +5124,26 @@
"id": "malware-analyst",
"path": "skills/malware-analyst",
"category": "uncategorized",
- "name": "malware-analyst",
- "description": "Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.",
+ "name": "Malware Analyst",
+ "description": "file sample.exe sha256sum sample.exe",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "manifest",
+ "path": "skills/manifest",
+ "category": "uncategorized",
+ "name": "manifest",
+ "description": "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "market-sizing-analysis",
"path": "skills/market-sizing-analysis",
"category": "uncategorized",
- "name": "market-sizing-analysis",
- "description": "This skill should be used when the user asks to \"calculate TAM\", \"determine SAM\", \"estimate SOM\", \"size the market\", \"calculate market opportunity\", \"what's the total addressable market\", or requests market sizing analysis for a startup or business opportunity.",
+ "name": "Market Sizing Analysis",
+ "description": "Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.",
"risk": "unknown",
"source": "unknown"
},
@@ -4722,7 +5154,7 @@
"name": "marketing-ideas",
"description": "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "marketing-psychology",
@@ -4731,43 +5163,43 @@
"name": "marketing-psychology",
"description": "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mcp-builder",
"path": "skills/mcp-builder",
"category": "uncategorized",
"name": "mcp-builder",
- "description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).",
+ "description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mcp-builder-ms",
"path": "skills/mcp-builder-ms",
"category": "uncategorized",
- "name": "mcp-builder",
- "description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).",
+ "name": "mcp-builder-ms",
+ "description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "memory-forensics",
"path": "skills/memory-forensics",
"category": "uncategorized",
"name": "memory-forensics",
- "description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.",
+ "description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "memory-safety-patterns",
"path": "skills/memory-safety-patterns",
"category": "uncategorized",
"name": "memory-safety-patterns",
- "description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.",
+ "description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "memory-systems",
@@ -4782,8 +5214,8 @@
"id": "mermaid-expert",
"path": "skills/mermaid-expert",
"category": "uncategorized",
- "name": "mermaid-expert",
- "description": "Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling. Use PROACTIVELY for visual documentation, system diagrams, or process flows.",
+ "name": "Mermaid Expert",
+ "description": "- Working on mermaid expert tasks or workflows - Needing guidance, best practices, or checklists for mermaid expert",
"risk": "unknown",
"source": "unknown"
},
@@ -4791,17 +5223,17 @@
"id": "metasploit-framework",
"path": "skills/metasploit-framework",
"category": "uncategorized",
- "name": "Metasploit Framework",
- "description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exploitation\", \"use auxiliary modules for scanning\", or \"develop custom exploits\". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.",
+ "name": "metasploit-framework",
+ "description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "micro-saas-launcher",
"path": "skills/micro-saas-launcher",
"category": "uncategorized",
"name": "micro-saas-launcher",
- "description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.",
+ "description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -4810,16 +5242,16 @@
"path": "skills/microservices-patterns",
"category": "uncategorized",
"name": "microservices-patterns",
- "description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.",
+ "description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"path": "skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"category": "uncategorized",
- "name": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
- "description": "Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: \"Authentication Events\", \"WebJobsAuthenticationEventsTrigger\", \"OnTokenIssuanceStart\", \"OnAttributeCollectionStart\", \"custom claims\", \"token enrichment\", \"Entra custom extension\", \"authentication extension\".",
+ "name": "Microsoft Azure Webjobs Extensions Authentication Events Dotnet",
+ "description": "Azure Functions extension for handling Microsoft Entra ID custom authentication events.",
"risk": "unknown",
"source": "unknown"
},
@@ -4830,14 +5262,14 @@
"name": "microsoft-teams-automation",
"description": "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "minecraft-bukkit-pro",
"path": "skills/minecraft-bukkit-pro",
"category": "uncategorized",
- "name": "minecraft-bukkit-pro",
- "description": "Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.",
+ "name": "Minecraft Bukkit Pro",
+ "description": "- Working on minecraft bukkit pro tasks or workflows - Needing guidance, best practices, or checklists for minecraft bukkit pro",
"risk": "unknown",
"source": "unknown"
},
@@ -4848,7 +5280,7 @@
"name": "miro-automation",
"description": "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mixpanel-automation",
@@ -4857,14 +5289,14 @@
"name": "mixpanel-automation",
"description": "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ml-engineer",
"path": "skills/ml-engineer",
"category": "uncategorized",
- "name": "ml-engineer",
- "description": "Build production ML systems with PyTorch 2.x, TensorFlow, and modern ML frameworks. Implements model serving, feature engineering, A/B testing, and monitoring. Use PROACTIVELY for ML model deployment, inference optimization, or production ML infrastructure.",
+ "name": "Ml Engineer",
+ "description": "- Working on ml engineer tasks or workflows - Needing guidance, best practices, or checklists for ml engineer",
"risk": "unknown",
"source": "unknown"
},
@@ -4873,16 +5305,34 @@
"path": "skills/ml-pipeline-workflow",
"category": "uncategorized",
"name": "ml-pipeline-workflow",
- "description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.",
+ "description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mlops-engineer",
"path": "skills/mlops-engineer",
"category": "uncategorized",
- "name": "mlops-engineer",
- "description": "Build comprehensive ML pipelines, experiment tracking, and model registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated training, deployment, and monitoring across cloud platforms. Use PROACTIVELY for ML infrastructure, experiment management, or pipeline automation.",
+ "name": "Mlops Engineer",
+ "description": "- Working on mlops engineer tasks or workflows - Needing guidance, best practices, or checklists for mlops engineer",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "mobile-developer",
+ "path": "skills/mobile-developer",
+ "category": "uncategorized",
+ "name": "Mobile Developer",
+ "description": "- Working on mobile developer tasks or workflows - Needing guidance, best practices, or checklists for mobile developer",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "mobile-security-coder",
+ "path": "skills/mobile-security-coder",
+ "category": "uncategorized",
+ "name": "Mobile Security Coder",
+ "description": "- Working on mobile security coder tasks or workflows - Needing guidance, best practices, or checklists for mobile security coder",
"risk": "unknown",
"source": "unknown"
},
@@ -4891,18 +5341,9 @@
"path": "skills/mobile-design",
"category": "uncategorized",
"name": "mobile-design",
- "description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.",
+ "description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-developer",
- "path": "skills/mobile-developer",
- "category": "uncategorized",
- "name": "mobile-developer",
- "description": "Develop React Native, Flutter, or native mobile apps with modern architecture patterns. Masters cross-platform development, native integrations, offline sync, and app store optimization. Use PROACTIVELY for mobile features, cross-platform code, or app optimization.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mobile-games",
@@ -4911,25 +5352,16 @@
"name": "mobile-games",
"description": "Mobile game development principles. Touch input, battery, performance, app stores.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-security-coder",
- "path": "skills/mobile-security-coder",
- "category": "uncategorized",
- "name": "mobile-security-coder",
- "description": "Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "modern-javascript-patterns",
"path": "skills/modern-javascript-patterns",
"category": "uncategorized",
"name": "modern-javascript-patterns",
- "description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.",
+ "description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "monday-automation",
@@ -4938,7 +5370,7 @@
"name": "monday-automation",
"description": "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "monorepo-architect",
@@ -4947,25 +5379,25 @@
"name": "monorepo-architect",
"description": "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "monorepo-management",
"path": "skills/monorepo-management",
"category": "uncategorized",
"name": "monorepo-management",
- "description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.",
+ "description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "moodle-external-api-development",
"path": "skills/moodle-external-api-development",
"category": "uncategorized",
"name": "moodle-external-api-development",
- "description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.",
+ "description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mtls-configuration",
@@ -4974,7 +5406,7 @@
"name": "mtls-configuration",
"description": "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "multi-agent-brainstorming",
@@ -4983,7 +5415,7 @@
"name": "multi-agent-brainstorming",
"description": "Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "multi-agent-patterns",
@@ -4999,9 +5431,9 @@
"path": "skills/multi-cloud-architecture",
"category": "uncategorized",
"name": "multi-cloud-architecture",
- "description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.",
+ "description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "multi-platform-apps-multi-platform",
@@ -5010,7 +5442,7 @@
"name": "multi-platform-apps-multi-platform",
"description": "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "multiplayer",
@@ -5019,7 +5451,7 @@
"name": "multiplayer",
"description": "Multiplayer game development principles. Architecture, networking, synchronization.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "n8n-code-python",
@@ -5035,7 +5467,7 @@
"path": "skills/n8n-mcp-tools-expert",
"category": "uncategorized",
"name": "n8n-mcp-tools-expert",
- "description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns.",
+ "description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele...",
"risk": "safe",
"source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert"
},
@@ -5044,7 +5476,7 @@
"path": "skills/n8n-node-configuration",
"category": "uncategorized",
"name": "n8n-node-configuration",
- "description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type.",
+ "description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo...",
"risk": "safe",
"source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration"
},
@@ -5062,16 +5494,43 @@
"path": "skills/neon-postgres",
"category": "uncategorized",
"name": "neon-postgres",
- "description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless.",
+ "description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "nerdzao-elite",
+ "path": "skills/nerdzao-elite",
+ "category": "uncategorized",
+ "name": "nerdzao-elite",
+ "description": "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.",
+ "risk": "safe",
+ "source": "community"
+ },
+ {
+ "id": "nerdzao-elite-gemini-high",
+ "path": "skills/nerdzao-elite-gemini-high",
+ "category": "uncategorized",
+ "name": "nerdzao-elite-gemini-high",
+ "description": "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade m\u00e1xima e efici\u00eancia de tokens.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "nestjs-expert",
"path": "skills/nestjs-expert",
"category": "uncategorized",
"name": "nestjs-expert",
- "description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.",
+ "description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "network-engineer",
+ "path": "skills/network-engineer",
+ "category": "uncategorized",
+ "name": "Network Engineer",
+ "description": "- Working on network engineer tasks or workflows - Needing guidance, best practices, or checklists for network engineer",
"risk": "unknown",
"source": "unknown"
},
@@ -5079,28 +5538,19 @@
"id": "network-101",
"path": "skills/network-101",
"category": "uncategorized",
- "name": "Network 101",
- "description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or needs guidance on configuring and testing network services for penetration testing labs.",
+ "name": "network-101",
+ "description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "network-engineer",
- "path": "skills/network-engineer",
- "category": "uncategorized",
- "name": "network-engineer",
- "description": "Expert network engineer specializing in modern cloud networking, security architectures, and performance optimization. Masters multi-cloud connectivity, service mesh, zero-trust networking, SSL/TLS, global load balancing, and advanced troubleshooting. Handles CDN optimization, network automation, and compliance. Use PROACTIVELY for network design, connectivity issues, or performance optimization.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nextjs-app-router-patterns",
"path": "skills/nextjs-app-router-patterns",
"category": "uncategorized",
"name": "nextjs-app-router-patterns",
- "description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.",
+ "description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nextjs-best-practices",
@@ -5109,7 +5559,7 @@
"name": "nextjs-best-practices",
"description": "Next.js App Router principles. Server Components, data fetching, routing patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nextjs-supabase-auth",
@@ -5125,18 +5575,18 @@
"path": "skills/nft-standards",
"category": "uncategorized",
"name": "nft-standards",
- "description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.",
+ "description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nodejs-backend-patterns",
"path": "skills/nodejs-backend-patterns",
"category": "uncategorized",
"name": "nodejs-backend-patterns",
- "description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.",
+ "description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nodejs-best-practices",
@@ -5145,7 +5595,7 @@
"name": "nodejs-best-practices",
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "nosql-expert",
@@ -5154,16 +5604,16 @@
"name": "nosql-expert",
"description": "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "notebooklm",
"path": "skills/notebooklm",
"category": "uncategorized",
"name": "notebooklm",
- "description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.",
+ "description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth....",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "notion-automation",
@@ -5172,14 +5622,14 @@
"name": "notion-automation",
"description": "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "notion-template-business",
"path": "skills/notion-template-business",
"category": "uncategorized",
"name": "notion-template-business",
- "description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad.",
+ "description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -5190,14 +5640,14 @@
"name": "nx-workspace-patterns",
"description": "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "observability-engineer",
"path": "skills/observability-engineer",
"category": "uncategorized",
- "name": "observability-engineer",
- "description": "Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.",
+ "name": "Observability Engineer",
+ "description": "You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.",
"risk": "unknown",
"source": "unknown"
},
@@ -5208,23 +5658,23 @@
"name": "observability-monitoring-monitor-setup",
"description": "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "observability-monitoring-slo-implement",
"path": "skills/observability-monitoring-slo-implement",
"category": "uncategorized",
"name": "observability-monitoring-slo-implement",
- "description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity.",
+ "description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "observe-whatsapp",
"path": "skills/observe-whatsapp",
"category": "uncategorized",
"name": "observe-whatsapp",
- "description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message failures, or webhook delivery problems.",
+ "description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f...",
"risk": "safe",
"source": "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp"
},
@@ -5235,25 +5685,34 @@
"name": "obsidian-clipper-template-creator",
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "office-productivity",
+ "path": "skills/office-productivity",
+ "category": "uncategorized",
+ "name": "office-productivity",
+ "description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "on-call-handoff-patterns",
"path": "skills/on-call-handoff-patterns",
"category": "uncategorized",
"name": "on-call-handoff-patterns",
- "description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.",
+ "description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "onboarding-cro",
"path": "skills/onboarding-cro",
"category": "uncategorized",
"name": "onboarding-cro",
- "description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"user activation,\" \"first-run experience,\" \"empty states,\" \"onboarding checklist,\" \"aha moment,\" or \"new user experience.\" For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.",
+ "description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "one-drive-automation",
@@ -5262,7 +5721,7 @@
"name": "one-drive-automation",
"description": "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "openapi-spec-generation",
@@ -5271,7 +5730,16 @@
"name": "openapi-spec-generation",
"description": "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "os-scripting",
+ "path": "skills/os-scripting",
+ "category": "uncategorized",
+ "name": "os-scripting",
+ "description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "oss-hunter",
@@ -5289,7 +5757,7 @@
"name": "outlook-automation",
"description": "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "outlook-calendar-automation",
@@ -5298,14 +5766,14 @@
"name": "outlook-calendar-automation",
"description": "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "page-cro",
"path": "skills/page-cro",
"category": "uncategorized",
- "name": "page-cro",
- "description": "Analyze and optimize individual pages for conversion performance. Use when the user wants to improve conversion rates, diagnose why a page is underperforming, or increase the effectiveness of marketing pages (homepage, landing pages, pricing, feature pages, or blog posts). This skill focuses on diagnosis, prioritization, and testable recommendations\u2014 not blind optimization.",
+ "name": "Page Cro",
+ "description": "You are an expert in **page-level conversion optimization**. Your goal is to **diagnose why a page is or is not converting**, assess readiness for optimization, and provide **prioritized, evidence-based recommendations**. You do **not** guarantee con",
"risk": "unknown",
"source": "unknown"
},
@@ -5316,16 +5784,16 @@
"name": "pagerduty-automation",
"description": "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "paid-ads",
"path": "skills/paid-ads",
"category": "uncategorized",
"name": "paid-ads",
- "description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.",
+ "description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "parallel-agents",
@@ -5334,14 +5802,14 @@
"name": "parallel-agents",
"description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "payment-integration",
"path": "skills/payment-integration",
"category": "uncategorized",
- "name": "payment-integration",
- "description": "Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.",
+ "name": "Payment Integration",
+ "description": "- Working on payment integration tasks or workflows - Needing guidance, best practices, or checklists for payment integration",
"risk": "unknown",
"source": "unknown"
},
@@ -5350,18 +5818,18 @@
"path": "skills/paypal-integration",
"category": "uncategorized",
"name": "paypal-integration",
- "description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows.",
+ "description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "paywall-upgrade-cro",
"path": "skills/paywall-upgrade-cro",
"category": "uncategorized",
"name": "paywall-upgrade-cro",
- "description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,\" \"upsell,\" \"feature gate,\" \"convert free to paid,\" \"freemium conversion,\" \"trial expiration screen,\" \"limit reached screen,\" \"plan upgrade prompt,\" or \"in-app pricing.\" Distinct from public pricing pages (see page-cro) \u2014 this skill focuses on in-product upgrade moments where the user has already experienced value.",
+ "description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pc-games",
@@ -5370,43 +5838,43 @@
"name": "pc-games",
"description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pci-compliance",
"path": "skills/pci-compliance",
"category": "uncategorized",
"name": "pci-compliance",
- "description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card security measures.",
+ "description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pdf-official",
"path": "skills/pdf-official",
"category": "uncategorized",
- "name": "pdf",
- "description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.",
+ "name": "pdf-official",
+ "description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pentest-checklist",
"path": "skills/pentest-checklist",
"category": "uncategorized",
- "name": "Pentest Checklist",
- "description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"follow security testing best practices\", or needs a structured methodology for penetration testing engagements.",
+ "name": "pentest-checklist",
+ "description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pentest-commands",
"path": "skills/pentest-commands",
"category": "uncategorized",
- "name": "Pentest Commands",
- "description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities with nikto\", \"enumerate networks\", or needs essential penetration testing command references.",
+ "name": "pentest-commands",
+ "description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "performance-engineer",
@@ -5415,7 +5883,7 @@
"name": "performance-engineer",
"description": "Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "performance-profiling",
@@ -5424,7 +5892,7 @@
"name": "performance-profiling",
"description": "Performance profiling principles. Measurement, analysis, and optimization techniques.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "performance-testing-review-ai-review",
@@ -5433,7 +5901,7 @@
"name": "performance-testing-review-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "performance-testing-review-multi-agent-review",
@@ -5442,14 +5910,14 @@
"name": "performance-testing-review-multi-agent-review",
"description": "Use when working with performance testing review multi agent review",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "personal-tool-builder",
"path": "skills/personal-tool-builder",
"category": "uncategorized",
"name": "personal-tool-builder",
- "description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when: build a tool, personal tool, scratch my itch, solve my problem, CLI tool.",
+ "description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -5457,8 +5925,8 @@
"id": "php-pro",
"path": "skills/php-pro",
"category": "uncategorized",
- "name": "php-pro",
- "description": "Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.",
+ "name": "Php Pro",
+ "description": "- Working on php pro tasks or workflows - Needing guidance, best practices, or checklists for php pro",
"risk": "unknown",
"source": "unknown"
},
@@ -5469,14 +5937,14 @@
"name": "pipedrive-automation",
"description": "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "plaid-fintech",
"path": "skills/plaid-fintech",
"category": "uncategorized",
"name": "plaid-fintech",
- "description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when: plaid, bank account linking, bank connection, ach, account aggregation.",
+ "description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -5487,34 +5955,34 @@
"name": "plan-writing",
"description": "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "planning-with-files",
"path": "skills/planning-with-files",
"category": "uncategorized",
"name": "planning-with-files",
- "description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.",
+ "description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "playwright-skill",
"path": "skills/playwright-skill",
"category": "uncategorized",
"name": "playwright-skill",
- "description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.",
+ "description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "podcast-generation",
"path": "skills/podcast-generation",
"category": "uncategorized",
"name": "podcast-generation",
- "description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.",
+ "description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "popup-cro",
@@ -5523,17 +5991,26 @@
"name": "popup-cro",
"description": "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "posix-shell-pro",
"path": "skills/posix-shell-pro",
"category": "uncategorized",
- "name": "posix-shell-pro",
- "description": "Expert in strict POSIX sh scripting for maximum portability across Unix-like systems. Specializes in shell scripts that run on any POSIX-compliant shell (dash, ash, sh, bash --posix).",
+ "name": "Posix Shell Pro",
+ "description": "- Working on posix shell pro tasks or workflows - Needing guidance, best practices, or checklists for posix shell pro",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "postgres-best-practices",
+ "path": "skills/postgres-best-practices",
+ "category": "uncategorized",
+ "name": "postgres-best-practices",
+ "description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "postgresql",
"path": "skills/postgresql",
@@ -5541,7 +6018,16 @@
"name": "postgresql",
"description": "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "postgresql-optimization",
+ "path": "skills/postgresql-optimization",
+ "category": "uncategorized",
+ "name": "postgresql-optimization",
+ "description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "posthog-automation",
@@ -5550,7 +6036,7 @@
"name": "posthog-automation",
"description": "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "postmark-automation",
@@ -5559,16 +6045,16 @@
"name": "postmark-automation",
"description": "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "postmortem-writing",
"path": "skills/postmortem-writing",
"category": "uncategorized",
"name": "postmortem-writing",
- "description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.",
+ "description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "powershell-windows",
@@ -5577,16 +6063,16 @@
"name": "powershell-windows",
"description": "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pptx-official",
"path": "skills/pptx-official",
"category": "uncategorized",
- "name": "pptx",
- "description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks",
+ "name": "pptx-official",
+ "description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pricing-strategy",
@@ -5595,34 +6081,34 @@
"name": "pricing-strategy",
"description": "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prisma-expert",
"path": "skills/prisma-expert",
"category": "uncategorized",
"name": "prisma-expert",
- "description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.",
+ "description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "privilege-escalation-methods",
"path": "skills/privilege-escalation-methods",
"category": "uncategorized",
- "name": "Privilege Escalation Methods",
- "description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"Kerberoasting\", \"pass-the-ticket\", \"token impersonation\", or needs guidance on post-exploitation privilege escalation for Linux or Windows systems.",
+ "name": "privilege-escalation-methods",
+ "description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "product-manager-toolkit",
"path": "skills/product-manager-toolkit",
"category": "uncategorized",
"name": "product-manager-toolkit",
- "description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.",
+ "description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "production-code-audit",
@@ -5631,14 +6117,14 @@
"name": "production-code-audit",
"description": "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "programmatic-seo",
"path": "skills/programmatic-seo",
"category": "uncategorized",
- "name": "programmatic-seo",
- "description": "Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design\u2014not execution unless explicitly requested.",
+ "name": "Programmatic Seo",
+ "description": "---",
"risk": "unknown",
"source": "unknown"
},
@@ -5649,23 +6135,23 @@
"name": "projection-patterns",
"description": "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prometheus-configuration",
"path": "skills/prometheus-configuration",
"category": "uncategorized",
"name": "prometheus-configuration",
- "description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.",
+ "description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prompt-caching",
"path": "skills/prompt-caching",
"category": "uncategorized",
"name": "prompt-caching",
- "description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augmented.",
+ "description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -5676,7 +6162,7 @@
"name": "prompt-engineer",
"description": "Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)",
"risk": "safe",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prompt-engineering",
@@ -5685,43 +6171,43 @@
"name": "prompt-engineering",
"description": "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prompt-engineering-patterns",
"path": "skills/prompt-engineering-patterns",
"category": "uncategorized",
"name": "prompt-engineering-patterns",
- "description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.",
+ "description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "prompt-library",
"path": "skills/prompt-library",
"category": "uncategorized",
"name": "prompt-library",
- "description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.",
+ "description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "protocol-reverse-engineering",
"path": "skills/protocol-reverse-engineering",
"category": "uncategorized",
"name": "protocol-reverse-engineering",
- "description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.",
+ "description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pydantic-models-py",
"path": "skills/pydantic-models-py",
"category": "uncategorized",
"name": "pydantic-models-py",
- "description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation in Python applications using Pydantic v2.",
+ "description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pypict-skill",
@@ -5732,6 +6218,15 @@
"risk": "safe",
"source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md"
},
+ {
+ "id": "python-pro",
+ "path": "skills/python-pro",
+ "category": "uncategorized",
+ "name": "Python Pro",
+ "description": "You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
{
"id": "python-development-python-scaffold",
"path": "skills/python-development-python-scaffold",
@@ -5739,16 +6234,25 @@
"name": "python-development-python-scaffold",
"description": "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "python-fastapi-development",
+ "path": "skills/python-fastapi-development",
+ "category": "uncategorized",
+ "name": "python-fastapi-development",
+ "description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "python-packaging",
"path": "skills/python-packaging",
"category": "uncategorized",
"name": "python-packaging",
- "description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.",
+ "description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "python-patterns",
@@ -5757,7 +6261,7 @@
"name": "python-patterns",
"description": "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "python-performance-optimization",
@@ -5766,16 +6270,7 @@
"name": "python-performance-optimization",
"description": "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "python-pro",
- "path": "skills/python-pro",
- "category": "uncategorized",
- "name": "python-pro",
- "description": "Master Python 3.12+ with modern features, async programming, performance optimization, and production-ready practices. Expert in the latest Python ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY for Python development, optimization, or advanced Python patterns.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "python-testing-patterns",
@@ -5784,14 +6279,14 @@
"name": "python-testing-patterns",
"description": "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "quant-analyst",
"path": "skills/quant-analyst",
"category": "uncategorized",
- "name": "quant-analyst",
- "description": "Build financial models, backtest trading strategies, and analyze market data. Implements risk metrics, portfolio optimization, and statistical arbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or risk analysis.",
+ "name": "Quant Analyst",
+ "description": "- Working on quant analyst tasks or workflows - Needing guidance, best practices, or checklists for quant analyst",
"risk": "unknown",
"source": "unknown"
},
@@ -5809,7 +6304,7 @@
"path": "skills/rag-engineer",
"category": "uncategorized",
"name": "rag-engineer",
- "description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, vector search, embeddings, semantic search, document retrieval.",
+ "description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -5818,45 +6313,63 @@
"path": "skills/rag-implementation",
"category": "uncategorized",
"name": "rag-implementation",
- "description": "Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases.",
+ "description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "react-best-practices",
+ "path": "skills/react-best-practices",
+ "category": "uncategorized",
+ "name": "react-best-practices",
+ "description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-flow-architect",
"path": "skills/react-flow-architect",
"category": "uncategorized",
"name": "react-flow-architect",
- "description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or optimize ReactFlow applications for: (1) Interactive process graphs with expand/collapse navigation, (2) Hierarchical tree structures with drag & drop, (3) Performance-optimized large datasets with incremental rendering, (4) Auto-layout integration with Dagre, (5) Complex state management for nodes and edges, or any advanced ReactFlow visualization requirements.",
+ "description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-flow-node-ts",
"path": "skills/react-flow-node-ts",
"category": "uncategorized",
"name": "react-flow-node-ts",
- "description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing node-based UI components.",
+ "description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-modernization",
"path": "skills/react-modernization",
"category": "uncategorized",
"name": "react-modernization",
- "description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.",
+ "description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-native-architecture",
"path": "skills/react-native-architecture",
"category": "uncategorized",
"name": "react-native-architecture",
- "description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.",
+ "description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "react-nextjs-development",
+ "path": "skills/react-nextjs-development",
+ "category": "uncategorized",
+ "name": "react-nextjs-development",
+ "description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "react-patterns",
@@ -5865,7 +6378,7 @@
"name": "react-patterns",
"description": "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-state-management",
@@ -5874,7 +6387,7 @@
"name": "react-state-management",
"description": "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "react-ui-patterns",
@@ -5883,14 +6396,14 @@
"name": "react-ui-patterns",
"description": "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "readme",
"path": "skills/readme",
"category": "uncategorized",
"name": "readme",
- "description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.",
+ "description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...",
"risk": "safe",
"source": "https://github.com/Shpigford/skills/tree/main/readme"
},
@@ -5899,18 +6412,9 @@
"path": "skills/receiving-code-review",
"category": "uncategorized",
"name": "receiving-code-review",
- "description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation",
+ "description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "red-team-tools",
- "path": "skills/red-team-tools",
- "category": "uncategorized",
- "name": "Red Team Tools and Methodology",
- "description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate subdomains\", or needs security researcher techniques and tool configurations from top bug bounty hunters.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "red-team-tactics",
@@ -5919,7 +6423,16 @@
"name": "red-team-tactics",
"description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "red-team-tools",
+ "path": "skills/red-team-tools",
+ "category": "uncategorized",
+ "name": "red-team-tools",
+ "description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su...",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "reddit-automation",
@@ -5928,14 +6441,14 @@
"name": "reddit-automation",
"description": "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "reference-builder",
"path": "skills/reference-builder",
"category": "uncategorized",
- "name": "reference-builder",
- "description": "Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.",
+ "name": "Reference Builder",
+ "description": "- Working on reference builder tasks or workflows - Needing guidance, best practices, or checklists for reference builder",
"risk": "unknown",
"source": "unknown"
},
@@ -5944,9 +6457,9 @@
"path": "skills/referral-program",
"category": "uncategorized",
"name": "referral-program",
- "description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.",
+ "description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "remotion-best-practices",
@@ -5955,7 +6468,7 @@
"name": "remotion-best-practices",
"description": "Best practices for Remotion - Video creation in React",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "render-automation",
@@ -5964,7 +6477,7 @@
"name": "render-automation",
"description": "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "requesting-code-review",
@@ -5973,23 +6486,23 @@
"name": "requesting-code-review",
"description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "research-engineer",
"path": "skills/research-engineer",
"category": "uncategorized",
"name": "research-engineer",
- "description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.",
+ "description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "reverse-engineer",
"path": "skills/reverse-engineer",
"category": "uncategorized",
- "name": "reverse-engineer",
- "description": "Expert reverse engineer specializing in binary analysis, disassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra, radare2, x64dbg, and modern RE toolchains. Handles executable analysis, library inspection, protocol extraction, and vulnerability research. Use PROACTIVELY for binary analysis, CTF challenges, security research, or understanding undocumented software.",
+ "name": "Reverse Engineer",
+ "description": "- IDAPython (IDA Pro scripting) - Ghidra scripting (Java/Python via Jython) - r2pipe (radare2 Python API) - pwntools (CTF/exploitation toolkit) - capstone (disassembly framework) - keystone (assembly framework) - unicorn (CPU emulator framework) - an",
"risk": "unknown",
"source": "unknown"
},
@@ -5997,8 +6510,8 @@
"id": "risk-manager",
"path": "skills/risk-manager",
"category": "uncategorized",
- "name": "risk-manager",
- "description": "Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.",
+ "name": "Risk Manager",
+ "description": "- Working on risk manager tasks or workflows - Needing guidance, best practices, or checklists for risk manager",
"risk": "unknown",
"source": "unknown"
},
@@ -6009,14 +6522,23 @@
"name": "risk-metrics-calculation",
"description": "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ruby-pro",
"path": "skills/ruby-pro",
"category": "uncategorized",
- "name": "ruby-pro",
- "description": "Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.",
+ "name": "Ruby Pro",
+ "description": "- Working on ruby pro tasks or workflows - Needing guidance, best practices, or checklists for ruby pro",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "rust-pro",
+ "path": "skills/rust-pro",
+ "category": "uncategorized",
+ "name": "Rust Pro",
+ "description": "You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.",
"risk": "unknown",
"source": "unknown"
},
@@ -6027,32 +6549,23 @@
"name": "rust-async-patterns",
"description": "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "rust-pro",
- "path": "skills/rust-pro",
- "category": "uncategorized",
- "name": "rust-pro",
- "description": "Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "saga-orchestration",
"path": "skills/saga-orchestration",
"category": "uncategorized",
"name": "saga-orchestration",
- "description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.",
+ "description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "sales-automator",
"path": "skills/sales-automator",
"category": "uncategorized",
- "name": "sales-automator",
- "description": "Draft cold emails, follow-ups, and proposal templates. Creates pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales outreach or lead nurturing.",
+ "name": "Sales Automator",
+ "description": "- Working on sales automator tasks or workflows - Needing guidance, best practices, or checklists for sales automator",
"risk": "unknown",
"source": "unknown"
},
@@ -6063,14 +6576,14 @@
"name": "salesforce-automation",
"description": "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "salesforce-development",
"path": "skills/salesforce-development",
"category": "uncategorized",
"name": "salesforce-development",
- "description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP). Use when: salesforce, sfdc, apex, lwc, lightning web components.",
+ "description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6079,25 +6592,34 @@
"path": "skills/sast-configuration",
"category": "uncategorized",
"name": "sast-configuration",
- "description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.",
+ "description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "scala-pro",
"path": "skills/scala-pro",
"category": "uncategorized",
- "name": "scala-pro",
- "description": "Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.",
+ "name": "Scala Pro",
+ "description": "- Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "scanning-tools",
+ "path": "skills/scanning-tools",
+ "category": "uncategorized",
+ "name": "scanning-tools",
+ "description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec...",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "schema-markup",
"path": "skills/schema-markup",
"category": "uncategorized",
- "name": "schema-markup",
- "description": "Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.\n",
+ "name": "Schema Markup",
+ "description": "---",
"risk": "unknown",
"source": "unknown"
},
@@ -6106,9 +6628,9 @@
"path": "skills/screen-reader-testing",
"category": "uncategorized",
"name": "screen-reader-testing",
- "description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.",
+ "description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "screenshots",
@@ -6124,7 +6646,7 @@
"path": "skills/scroll-experience",
"category": "uncategorized",
"name": "scroll-experience",
- "description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.",
+ "description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6135,35 +6657,44 @@
"name": "search-specialist",
"description": "Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "secrets-management",
"path": "skills/secrets-management",
"category": "uncategorized",
"name": "secrets-management",
- "description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.",
+ "description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "scanning-tools",
- "path": "skills/scanning-tools",
- "category": "uncategorized",
- "name": "Security Scanning Tools",
- "description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detect malware\", \"check cloud security\", or \"evaluate system compliance\". It provides comprehensive guidance on security scanning tools and methodologies.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "security-auditor",
"path": "skills/security-auditor",
"category": "uncategorized",
- "name": "security-auditor",
- "description": "Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits, DevSecOps, or compliance implementation.",
+ "name": "Security Auditor",
+ "description": "You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "security-scanning-security-sast",
+ "path": "skills/security-scanning-security-sast",
+ "category": "uncategorized",
+ "name": "Security Scanning Security Sast",
+ "description": "Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "security-audit",
+ "path": "skills/security-audit",
+ "category": "uncategorized",
+ "name": "security-audit",
+ "description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "security-bluebook-builder",
"path": "skills/security-bluebook-builder",
@@ -6178,9 +6709,9 @@
"path": "skills/security-compliance-compliance-check",
"category": "uncategorized",
"name": "security-compliance-compliance-check",
- "description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide implementation guidance.",
+ "description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "security-requirement-extraction",
@@ -6189,25 +6720,16 @@
"name": "security-requirement-extraction",
"description": "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "cc-skill-security-review",
- "path": "skills/cc-skill-security-review",
- "category": "uncategorized",
- "name": "security-review",
- "description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "security-scanning-security-dependencies",
"path": "skills/security-scanning-security-dependencies",
"category": "uncategorized",
"name": "security-scanning-security-dependencies",
- "description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, assess risks, and recommend remediation.",
+ "description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "security-scanning-security-hardening",
@@ -6216,16 +6738,7 @@
"name": "security-scanning-security-hardening",
"description": "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "security-scanning-security-sast",
- "path": "skills/security-scanning-security-sast",
- "category": "uncategorized",
- "name": "security-scanning-security-sast",
- "description": "Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "segment-automation",
@@ -6234,14 +6747,14 @@
"name": "segment-automation",
"description": "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "segment-cdp",
"path": "skills/segment-cdp",
"category": "uncategorized",
"name": "segment-cdp",
- "description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices. Use when: segment, analytics.js, customer data platform, cdp, tracking plan.",
+ "description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6250,27 +6763,27 @@
"path": "skills/sendgrid-automation",
"category": "uncategorized",
"name": "sendgrid-automation",
- "description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
+ "description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "senior-architect",
"path": "skills/senior-architect",
"category": "uncategorized",
"name": "senior-architect",
- "description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.",
+ "description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "senior-fullstack",
"path": "skills/senior-fullstack",
"category": "uncategorized",
"name": "senior-fullstack",
- "description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.",
+ "description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "sentry-automation",
@@ -6279,14 +6792,14 @@
"name": "sentry-automation",
"description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-audit",
"path": "skills/seo-audit",
"category": "uncategorized",
- "name": "seo-audit",
- "description": "Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.",
+ "name": "Seo Audit",
+ "description": "You are an **SEO diagnostic specialist**. Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility\u2014**not to implement fixes unless explicitly requested**.",
"risk": "unknown",
"source": "unknown"
},
@@ -6294,8 +6807,8 @@
"id": "seo-authority-builder",
"path": "skills/seo-authority-builder",
"category": "uncategorized",
- "name": "seo-authority-builder",
- "description": "Analyzes content for E-E-A-T signals and suggests improvements to build authority and trust. Identifies missing credibility elements. Use PROACTIVELY for YMYL topics.",
+ "name": "Seo Authority Builder",
+ "description": "- Working on seo authority builder tasks or workflows - Needing guidance, best practices, or checklists for seo authority builder",
"risk": "unknown",
"source": "unknown"
},
@@ -6303,8 +6816,8 @@
"id": "seo-cannibalization-detector",
"path": "skills/seo-cannibalization-detector",
"category": "uncategorized",
- "name": "seo-cannibalization-detector",
- "description": "Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.",
+ "name": "Seo Cannibalization Detector",
+ "description": "- Working on seo cannibalization detector tasks or workflows - Needing guidance, best practices, or checklists for seo cannibalization detector",
"risk": "unknown",
"source": "unknown"
},
@@ -6312,8 +6825,8 @@
"id": "seo-content-auditor",
"path": "skills/seo-content-auditor",
"category": "uncategorized",
- "name": "seo-content-auditor",
- "description": "Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines. Use PROACTIVELY for content review.",
+ "name": "Seo Content Auditor",
+ "description": "- Working on seo content auditor tasks or workflows - Needing guidance, best practices, or checklists for seo content auditor",
"risk": "unknown",
"source": "unknown"
},
@@ -6321,8 +6834,8 @@
"id": "seo-content-planner",
"path": "skills/seo-content-planner",
"category": "uncategorized",
- "name": "seo-content-planner",
- "description": "Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.",
+ "name": "Seo Content Planner",
+ "description": "- Working on seo content planner tasks or workflows - Needing guidance, best practices, or checklists for seo content planner",
"risk": "unknown",
"source": "unknown"
},
@@ -6330,8 +6843,8 @@
"id": "seo-content-refresher",
"path": "skills/seo-content-refresher",
"category": "uncategorized",
- "name": "seo-content-refresher",
- "description": "Identifies outdated elements in provided content and suggests updates to maintain freshness. Finds statistics, dates, and examples that need updating. Use PROACTIVELY for older content.",
+ "name": "Seo Content Refresher",
+ "description": "- Working on seo content refresher tasks or workflows - Needing guidance, best practices, or checklists for seo content refresher",
"risk": "unknown",
"source": "unknown"
},
@@ -6339,8 +6852,8 @@
"id": "seo-content-writer",
"path": "skills/seo-content-writer",
"category": "uncategorized",
- "name": "seo-content-writer",
- "description": "Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.",
+ "name": "Seo Content Writer",
+ "description": "- Working on seo content writer tasks or workflows - Needing guidance, best practices, or checklists for seo content writer",
"risk": "unknown",
"source": "unknown"
},
@@ -6348,8 +6861,8 @@
"id": "seo-fundamentals",
"path": "skills/seo-fundamentals",
"category": "uncategorized",
- "name": "seo-fundamentals",
- "description": "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.\n",
+ "name": "Seo Fundamentals",
+ "description": "---",
"risk": "unknown",
"source": "unknown"
},
@@ -6357,8 +6870,8 @@
"id": "seo-keyword-strategist",
"path": "skills/seo-keyword-strategist",
"category": "uncategorized",
- "name": "seo-keyword-strategist",
- "description": "Analyzes keyword usage in provided content, calculates density, suggests semantic variations and LSI keywords based on the topic. Prevents over-optimization. Use PROACTIVELY for content optimization.",
+ "name": "Seo Keyword Strategist",
+ "description": "- Working on seo keyword strategist tasks or workflows - Needing guidance, best practices, or checklists for seo keyword strategist",
"risk": "unknown",
"source": "unknown"
},
@@ -6366,8 +6879,8 @@
"id": "seo-meta-optimizer",
"path": "skills/seo-meta-optimizer",
"category": "uncategorized",
- "name": "seo-meta-optimizer",
- "description": "Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.",
+ "name": "Seo Meta Optimizer",
+ "description": "- Working on seo meta optimizer tasks or workflows - Needing guidance, best practices, or checklists for seo meta optimizer",
"risk": "unknown",
"source": "unknown"
},
@@ -6375,8 +6888,8 @@
"id": "seo-snippet-hunter",
"path": "skills/seo-snippet-hunter",
"category": "uncategorized",
- "name": "seo-snippet-hunter",
- "description": "Formats content to be eligible for featured snippets and SERP features. Creates snippet-optimized content blocks based on best practices. Use PROACTIVELY for question-based content.",
+ "name": "Seo Snippet Hunter",
+ "description": "- Working on seo snippet hunter tasks or workflows - Needing guidance, best practices, or checklists for seo snippet hunter",
"risk": "unknown",
"source": "unknown"
},
@@ -6384,8 +6897,8 @@
"id": "seo-structure-architect",
"path": "skills/seo-structure-architect",
"category": "uncategorized",
- "name": "seo-structure-architect",
- "description": "Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization. Use PROACTIVELY for content structuring.",
+ "name": "Seo Structure Architect",
+ "description": "- Working on seo structure architect tasks or workflows - Needing guidance, best practices, or checklists for seo structure architect",
"risk": "unknown",
"source": "unknown"
},
@@ -6396,7 +6909,7 @@
"name": "server-management",
"description": "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "service-mesh-expert",
@@ -6405,16 +6918,25 @@
"name": "service-mesh-expert",
"description": "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "service-mesh-observability",
"path": "skills/service-mesh-observability",
"category": "uncategorized",
"name": "service-mesh-observability",
- "description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.",
+ "description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "shader-programming-glsl",
+ "path": "skills/shader-programming-glsl",
+ "category": "uncategorized",
+ "name": "shader-programming-glsl",
+ "description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "sharp-edges",
@@ -6432,23 +6954,23 @@
"name": "shellcheck-configuration",
"description": "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "shodan-reconnaissance",
"path": "skills/shodan-reconnaissance",
"category": "uncategorized",
- "name": "Shodan Reconnaissance and Pentesting",
- "description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges with Shodan,\" or \"discover IoT devices and open ports.\" It provides comprehensive guidance for using Shodan's search engine, CLI, and API for penetration testing reconnaissance.",
+ "name": "shodan-reconnaissance",
+ "description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "shopify-apps",
"path": "skills/shopify-apps",
"category": "uncategorized",
"name": "shopify-apps",
- "description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. Use when: shopify app, shopify, embedded app, polaris, app bridge.",
+ "description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6459,25 +6981,25 @@
"name": "shopify-automation",
"description": "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "shopify-development",
"path": "skills/shopify-development",
"category": "uncategorized",
"name": "shopify-development",
- "description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"",
+ "description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "signup-flow-cro",
"path": "skills/signup-flow-cro",
"category": "uncategorized",
"name": "signup-flow-cro",
- "description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" or \"account creation flow.\" For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.",
+ "description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "similarity-search-patterns",
@@ -6486,34 +7008,34 @@
"name": "similarity-search-patterns",
"description": "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "skill-creator",
"path": "skills/skill-creator",
"category": "uncategorized",
"name": "skill-creator",
- "description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation.",
+ "description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s...",
"risk": "safe",
- "source": "unknown"
+ "source": "community"
},
{
"id": "skill-creator-ms",
"path": "skills/skill-creator-ms",
"category": "uncategorized",
- "name": "skill-creator",
+ "name": "skill-creator-ms",
"description": "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "skill-developer",
"path": "skills/skill-developer",
"category": "uncategorized",
"name": "skill-developer",
- "description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.",
+ "description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "skill-rails-upgrade",
@@ -6538,16 +7060,16 @@
"path": "skills/slack-automation",
"category": "uncategorized",
"name": "slack-automation",
- "description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatically.",
+ "description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "slack-bot-builder",
"path": "skills/slack-bot-builder",
"category": "uncategorized",
"name": "slack-bot-builder",
- "description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and Workflow Builder integration. Focus on best practices for production-ready Slack apps. Use when: slack bot, slack app, bolt framework, block kit, slash command.",
+ "description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6556,36 +7078,36 @@
"path": "skills/slack-gif-creator",
"category": "uncategorized",
"name": "slack-gif-creator",
- "description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"",
+ "description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "slo-implementation",
"path": "skills/slo-implementation",
"category": "uncategorized",
"name": "slo-implementation",
- "description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.",
+ "description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "smtp-penetration-testing",
"path": "skills/smtp-penetration-testing",
"category": "uncategorized",
- "name": "SMTP Penetration Testing",
- "description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email credentials\", or \"assess mail server security\". It provides comprehensive techniques for testing SMTP server security.",
+ "name": "smtp-penetration-testing",
+ "description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "social-content",
"path": "skills/social-content",
"category": "uncategorized",
"name": "social-content",
- "description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.",
+ "description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "software-architecture",
@@ -6594,16 +7116,16 @@
"name": "software-architecture",
"description": "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "solidity-security",
"path": "skills/solidity-security",
"category": "uncategorized",
"name": "solidity-security",
- "description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.",
+ "description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "spark-optimization",
@@ -6612,43 +7134,43 @@
"name": "spark-optimization",
"description": "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "sql-pro",
+ "path": "skills/sql-pro",
+ "category": "uncategorized",
+ "name": "Sql Pro",
+ "description": "You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.",
+ "risk": "unknown",
"source": "unknown"
},
{
"id": "sql-injection-testing",
"path": "skills/sql-injection-testing",
"category": "uncategorized",
- "name": "SQL Injection Testing",
- "description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database information through injection\", \"detect SQL injection flaws\", or \"exploit database query vulnerabilities\". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.",
+ "name": "sql-injection-testing",
+ "description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "sql-optimization-patterns",
"path": "skills/sql-optimization-patterns",
"category": "uncategorized",
"name": "sql-optimization-patterns",
- "description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.",
+ "description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "sql-pro",
- "path": "skills/sql-pro",
- "category": "uncategorized",
- "name": "sql-pro",
- "description": "Master modern SQL with cloud-native databases, OLTP/OLAP optimization, and advanced query techniques. Expert in performance tuning, data modeling, and hybrid analytical systems. Use PROACTIVELY for database optimization or complex analysis.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "sqlmap-database-pentesting",
"path": "skills/sqlmap-database-pentesting",
"category": "uncategorized",
- "name": "SQLMap Database Penetration Testing",
- "description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns from a vulnerable database,\" or \"perform automated database penetration testing.\" It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.",
+ "name": "sqlmap-database-pentesting",
+ "description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "square-automation",
@@ -6657,23 +7179,23 @@
"name": "square-automation",
"description": "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ssh-penetration-testing",
"path": "skills/ssh-penetration-testing",
"category": "uncategorized",
- "name": "SSH Penetration Testing",
- "description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tunneling\", or \"audit SSH security\". It provides comprehensive SSH penetration testing methodologies and techniques.",
+ "name": "ssh-penetration-testing",
+ "description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-analyst",
"path": "skills/startup-analyst",
"category": "uncategorized",
- "name": "startup-analyst",
- "description": "Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.",
+ "name": "Startup Analyst",
+ "description": "- Working on startup analyst tasks or workflows - Needing guidance, best practices, or checklists for startup analyst",
"risk": "unknown",
"source": "unknown"
},
@@ -6681,8 +7203,8 @@
"id": "startup-business-analyst-business-case",
"path": "skills/startup-business-analyst-business-case",
"category": "uncategorized",
- "name": "startup-business-analyst-business-case",
- "description": "Generate comprehensive investor-ready business case document with market, solution, financials, and strategy",
+ "name": "Startup Business Analyst Business Case",
+ "description": "Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.",
"risk": "unknown",
"source": "unknown"
},
@@ -6690,8 +7212,8 @@
"id": "startup-business-analyst-financial-projections",
"path": "skills/startup-business-analyst-financial-projections",
"category": "uncategorized",
- "name": "startup-business-analyst-financial-projections",
- "description": "Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios",
+ "name": "Startup Business Analyst Financial Projections",
+ "description": "Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.",
"risk": "unknown",
"source": "unknown"
},
@@ -6699,8 +7221,8 @@
"id": "startup-business-analyst-market-opportunity",
"path": "skills/startup-business-analyst-market-opportunity",
"category": "uncategorized",
- "name": "startup-business-analyst-market-opportunity",
- "description": "Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations",
+ "name": "Startup Business Analyst Market Opportunity",
+ "description": "Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.",
"risk": "unknown",
"source": "unknown"
},
@@ -6708,8 +7230,8 @@
"id": "startup-financial-modeling",
"path": "skills/startup-financial-modeling",
"category": "uncategorized",
- "name": "startup-financial-modeling",
- "description": "This skill should be used when the user asks to \"create financial projections\", \"build a financial model\", \"forecast revenue\", \"calculate burn rate\", \"estimate runway\", \"model cash flow\", or requests 3-5 year financial planning for a startup.",
+ "name": "Startup Financial Modeling",
+ "description": "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.",
"risk": "unknown",
"source": "unknown"
},
@@ -6717,8 +7239,8 @@
"id": "startup-metrics-framework",
"path": "skills/startup-metrics-framework",
"category": "uncategorized",
- "name": "startup-metrics-framework",
- "description": "This skill should be used when the user asks about \"key startup metrics\", \"SaaS metrics\", \"CAC and LTV\", \"unit economics\", \"burn multiple\", \"rule of 40\", \"marketplace metrics\", or requests guidance on tracking and optimizing business performance metrics.",
+ "name": "Startup Metrics Framework",
+ "description": "Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.",
"risk": "unknown",
"source": "unknown"
},
@@ -6727,7 +7249,7 @@
"path": "skills/stitch-ui-design",
"category": "uncategorized",
"name": "stitch-ui-design",
- "description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.",
+ "description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra...",
"risk": "safe",
"source": "self"
},
@@ -6738,7 +7260,7 @@
"name": "stride-analysis-patterns",
"description": "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "stripe-automation",
@@ -6747,16 +7269,16 @@
"name": "stripe-automation",
"description": "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "stripe-integration",
"path": "skills/stripe-integration",
"category": "uncategorized",
"name": "stripe-integration",
- "description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.",
+ "description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "subagent-driven-development",
@@ -6765,7 +7287,7 @@
"name": "subagent-driven-development",
"description": "Use when executing implementation plans with independent tasks in the current session",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "supabase-automation",
@@ -6774,16 +7296,7 @@
"name": "supabase-automation",
"description": "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "postgres-best-practices",
- "path": "skills/postgres-best-practices",
- "category": "uncategorized",
- "name": "supabase-postgres-best-practices",
- "description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "superpowers-lab",
@@ -6799,7 +7312,7 @@
"path": "skills/swiftui-expert-skill",
"category": "uncategorized",
"name": "swiftui-expert-skill",
- "description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.",
+ "description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil...",
"risk": "safe",
"source": "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill"
},
@@ -6810,7 +7323,7 @@
"name": "systematic-debugging",
"description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "systems-programming-rust-project",
@@ -6819,16 +7332,16 @@
"name": "systems-programming-rust-project",
"description": "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tailwind-design-system",
"path": "skills/tailwind-design-system",
"category": "uncategorized",
"name": "tailwind-design-system",
- "description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.",
+ "description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tailwind-patterns",
@@ -6837,7 +7350,7 @@
"name": "tailwind-patterns",
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tavily-web",
@@ -6846,14 +7359,14 @@
"name": "tavily-web",
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-orchestrator",
"path": "skills/tdd-orchestrator",
"category": "uncategorized",
- "name": "tdd-orchestrator",
- "description": "Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.",
+ "name": "Tdd Orchestrator",
+ "description": "- Working on tdd orchestrator tasks or workflows - Needing guidance, best practices, or checklists for tdd orchestrator",
"risk": "unknown",
"source": "unknown"
},
@@ -6864,7 +7377,7 @@
"name": "tdd-workflow",
"description": "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflows-tdd-cycle",
@@ -6873,7 +7386,7 @@
"name": "tdd-workflows-tdd-cycle",
"description": "Use when working with tdd workflows tdd cycle",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflows-tdd-green",
@@ -6882,7 +7395,7 @@
"name": "tdd-workflows-tdd-green",
"description": "Implement the minimal code needed to make failing tests pass in the TDD green phase.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflows-tdd-red",
@@ -6891,7 +7404,7 @@
"name": "tdd-workflows-tdd-red",
"description": "Generate failing tests for the TDD red phase to define expected behavior and edge cases.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflows-tdd-refactor",
@@ -6900,6 +7413,15 @@
"name": "tdd-workflows-tdd-refactor",
"description": "Use when working with tdd workflows tdd refactor",
"risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "team-composition-analysis",
+ "path": "skills/team-composition-analysis",
+ "category": "uncategorized",
+ "name": "Team Composition Analysis",
+ "description": "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.",
+ "risk": "unknown",
"source": "unknown"
},
{
@@ -6909,7 +7431,7 @@
"name": "team-collaboration-issue",
"description": "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "team-collaboration-standup-notes",
@@ -6918,16 +7440,7 @@
"name": "team-collaboration-standup-notes",
"description": "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "team-composition-analysis",
- "path": "skills/team-composition-analysis",
- "category": "uncategorized",
- "name": "team-composition-analysis",
- "description": "This skill should be used when the user asks to \"plan team structure\", \"determine hiring needs\", \"design org chart\", \"calculate compensation\", \"plan equity allocation\", or requests organizational design and headcount planning for a startup.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "telegram-automation",
@@ -6936,14 +7449,14 @@
"name": "telegram-automation",
"description": "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "telegram-bot-builder",
"path": "skills/telegram-bot-builder",
"category": "uncategorized",
"name": "telegram-bot-builder",
- "description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.",
+ "description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6952,7 +7465,7 @@
"path": "skills/telegram-mini-app",
"category": "uncategorized",
"name": "telegram-mini-app",
- "description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.",
+ "description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -6963,14 +7476,14 @@
"name": "templates",
"description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "temporal-python-pro",
"path": "skills/temporal-python-pro",
"category": "uncategorized",
- "name": "temporal-python-pro",
- "description": "Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.",
+ "name": "Temporal Python Pro",
+ "description": "- Working on temporal python pro tasks or workflows - Needing guidance, best practices, or checklists for temporal python pro",
"risk": "unknown",
"source": "unknown"
},
@@ -6979,18 +7492,45 @@
"path": "skills/temporal-python-testing",
"category": "uncategorized",
"name": "temporal-python-testing",
- "description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.",
+ "description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "terraform-specialist",
+ "path": "skills/terraform-specialist",
+ "category": "uncategorized",
+ "name": "Terraform Specialist",
+ "description": "You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.",
"risk": "unknown",
"source": "unknown"
},
+ {
+ "id": "terraform-aws-modules",
+ "path": "skills/terraform-aws-modules",
+ "category": "uncategorized",
+ "name": "terraform-aws-modules",
+ "description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "terraform-infrastructure",
+ "path": "skills/terraform-infrastructure",
+ "category": "uncategorized",
+ "name": "terraform-infrastructure",
+ "description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "terraform-module-library",
"path": "skills/terraform-module-library",
"category": "uncategorized",
"name": "terraform-module-library",
- "description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.",
+ "description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "terraform-skill",
@@ -7001,21 +7541,12 @@
"risk": "safe",
"source": "https://github.com/antonbabenko/terraform-skill"
},
- {
- "id": "terraform-specialist",
- "path": "skills/terraform-specialist",
- "category": "uncategorized",
- "name": "terraform-specialist",
- "description": "Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "test-automator",
"path": "skills/test-automator",
"category": "uncategorized",
- "name": "test-automator",
- "description": "Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.",
+ "name": "Test Automator",
+ "description": "- Working on test automator tasks or workflows - Needing guidance, best practices, or checklists for test automator",
"risk": "unknown",
"source": "unknown"
},
@@ -7026,16 +7557,16 @@
"name": "test-driven-development",
"description": "Use when implementing any feature or bugfix, before writing implementation code",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "test-fixing",
"path": "skills/test-fixing",
"category": "uncategorized",
"name": "test-fixing",
- "description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.",
+ "description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "testing-patterns",
@@ -7044,16 +7575,25 @@
"name": "testing-patterns",
"description": "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "testing-qa",
+ "path": "skills/testing-qa",
+ "category": "uncategorized",
+ "name": "testing-qa",
+ "description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "theme-factory",
"path": "skills/theme-factory",
"category": "uncategorized",
"name": "theme-factory",
- "description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.",
+ "description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "threat-mitigation-mapping",
@@ -7062,16 +7602,16 @@
"name": "threat-mitigation-mapping",
"description": "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "threat-modeling-expert",
"path": "skills/threat-modeling-expert",
"category": "uncategorized",
"name": "threat-modeling-expert",
- "description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture reviews, threat identification, and secure-by-design planning.",
+ "description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "threejs-skills",
@@ -7089,7 +7629,7 @@
"name": "tiktok-automation",
"description": "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "todoist-automation",
@@ -7098,7 +7638,7 @@
"name": "todoist-automation",
"description": "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tool-design",
@@ -7113,17 +7653,17 @@
"id": "top-web-vulnerabilities",
"path": "skills/top-web-vulnerabilities",
"category": "uncategorized",
- "name": "Top 100 Web Vulnerabilities Reference",
- "description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about injection attacks\", \"review access control weaknesses\", \"analyze API security issues\", \"assess security misconfigurations\", \"understand client-side vulnerabilities\", \"examine mobile and IoT security flaws\", or \"reference the OWASP-aligned vulnerability taxonomy\". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.",
+ "name": "top-web-vulnerabilities",
+ "description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "track-management",
"path": "skills/track-management",
"category": "uncategorized",
- "name": "track-management",
- "description": "Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.",
+ "name": "Track Management",
+ "description": "Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.",
"risk": "unknown",
"source": "unknown"
},
@@ -7134,14 +7674,14 @@
"name": "trello-automation",
"description": "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "trigger-dev",
"path": "skills/trigger-dev",
"category": "uncategorized",
"name": "trigger-dev",
- "description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.",
+ "description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7152,14 +7692,14 @@
"name": "turborepo-caching",
"description": "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tutorial-engineer",
"path": "skills/tutorial-engineer",
"category": "uncategorized",
- "name": "tutorial-engineer",
- "description": "Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.",
+ "name": "Tutorial Engineer",
+ "description": "- Working on tutorial engineer tasks or workflows - Needing guidance, best practices, or checklists for tutorial engineer",
"risk": "unknown",
"source": "unknown"
},
@@ -7168,7 +7708,7 @@
"path": "skills/twilio-communications",
"category": "uncategorized",
"name": "twilio-communications",
- "description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems and multi-channel authentication. Critical focus on compliance, rate limits, and error handling. Use when: twilio, send SMS, text message, voice call, phone verification.",
+ "description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7179,23 +7719,14 @@
"name": "twitter-automation",
"description": "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "typescript-advanced-types",
- "path": "skills/typescript-advanced-types",
- "category": "uncategorized",
- "name": "typescript-advanced-types",
- "description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "typescript-expert",
"path": "skills/typescript-expert",
"category": "uncategorized",
- "name": "typescript-expert",
- "description": "TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.",
+ "name": "Typescript Expert",
+ "description": "You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.",
"risk": "unknown",
"source": "unknown"
},
@@ -7203,8 +7734,35 @@
"id": "typescript-pro",
"path": "skills/typescript-pro",
"category": "uncategorized",
- "name": "typescript-pro",
- "description": "Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns. Use PROACTIVELY for TypeScript architecture, type inference optimization, or advanced typing patterns.",
+ "name": "Typescript Pro",
+ "description": "You are a TypeScript expert specializing in advanced typing and enterprise-grade development.",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "typescript-advanced-types",
+ "path": "skills/typescript-advanced-types",
+ "category": "uncategorized",
+ "name": "typescript-advanced-types",
+ "description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "ui-ux-designer",
+ "path": "skills/ui-ux-designer",
+ "category": "uncategorized",
+ "name": "Ui Ux Designer",
+ "description": "- Working on ui ux designer tasks or workflows - Needing guidance, best practices, or checklists for ui ux designer",
+ "risk": "unknown",
+ "source": "unknown"
+ },
+ {
+ "id": "ui-visual-validator",
+ "path": "skills/ui-visual-validator",
+ "category": "uncategorized",
+ "name": "Ui Visual Validator",
+ "description": "- Working on ui visual validator tasks or workflows - Needing guidance, best practices, or checklists for ui visual validator",
"risk": "unknown",
"source": "unknown"
},
@@ -7217,32 +7775,14 @@
"risk": "safe",
"source": "https://github.com/ibelick/ui-skills"
},
- {
- "id": "ui-ux-designer",
- "path": "skills/ui-ux-designer",
- "category": "uncategorized",
- "name": "ui-ux-designer",
- "description": "Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "ui-ux-pro-max",
"path": "skills/ui-ux-pro-max",
"category": "uncategorized",
"name": "ui-ux-pro-max",
- "description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.",
+ "description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "ui-visual-validator",
- "path": "skills/ui-visual-validator",
- "category": "uncategorized",
- "name": "ui-visual-validator",
- "description": "Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "unit-testing-test-generate",
@@ -7251,14 +7791,14 @@
"name": "unit-testing-test-generate",
"description": "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "unity-developer",
"path": "skills/unity-developer",
"category": "uncategorized",
- "name": "unity-developer",
- "description": "Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.",
+ "name": "Unity Developer",
+ "description": "- Working on unity developer tasks or workflows - Needing guidance, best practices, or checklists for unity developer",
"risk": "unknown",
"source": "unknown"
},
@@ -7267,9 +7807,9 @@
"path": "skills/unity-ecs-patterns",
"category": "uncategorized",
"name": "unity-ecs-patterns",
- "description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.",
+ "description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "unreal-engine-cpp-pro",
@@ -7294,7 +7834,7 @@
"path": "skills/upstash-qstash",
"category": "uncategorized",
"name": "upstash-qstash",
- "description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, scheduled http, message queue serverless.",
+ "description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7303,16 +7843,16 @@
"path": "skills/using-git-worktrees",
"category": "uncategorized",
"name": "using-git-worktrees",
- "description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification",
+ "description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "using-neon",
"path": "skills/using-neon",
"category": "uncategorized",
"name": "using-neon",
- "description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.",
+ "description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/...",
"risk": "safe",
"source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres"
},
@@ -7323,16 +7863,16 @@
"name": "using-superpowers",
"description": "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "uv-package-manager",
"path": "skills/uv-package-manager",
"category": "uncategorized",
"name": "uv-package-manager",
- "description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.",
+ "description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "varlock-claude-skill",
@@ -7350,7 +7890,7 @@
"name": "vector-database-engineer",
"description": "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vector-index-tuning",
@@ -7359,7 +7899,7 @@
"name": "vector-index-tuning",
"description": "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vercel-automation",
@@ -7368,14 +7908,14 @@
"name": "vercel-automation",
"description": "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vercel-deploy-claimable",
"path": "skills/vercel-deploy-claimable",
"category": "uncategorized",
"name": "vercel-deploy-claimable",
- "description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and give me the link', or 'Push this live'. No authentication required - returns preview URL and claimable deployment link.",
+ "description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...",
"risk": "safe",
"source": "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
},
@@ -7388,23 +7928,14 @@
"risk": "safe",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
- {
- "id": "react-best-practices",
- "path": "skills/react-best-practices",
- "category": "uncategorized",
- "name": "vercel-react-best-practices",
- "description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "verification-before-completion",
"path": "skills/verification-before-completion",
"category": "uncategorized",
"name": "verification-before-completion",
- "description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always",
+ "description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vexor",
@@ -7420,7 +7951,7 @@
"path": "skills/viral-generator-builder",
"category": "uncategorized",
"name": "viral-generator-builder",
- "description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Use when: generator tool, quiz maker, name generator, avatar creator, viral tool.",
+ "description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7429,7 +7960,7 @@
"path": "skills/voice-agents",
"category": "uncategorized",
"name": "voice-agents",
- "description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flow with sub-800ms latency while handling interruptions, background noise, and emotional nuance. This skill covers two architectures: speech-to-speech (OpenAI Realtime API, lowest latency, most natural) and pipeline (STT\u2192LLM\u2192TTS, more control, easier to debug). Key insight: latency is the constraint. Hu",
+ "description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7438,7 +7969,7 @@
"path": "skills/voice-ai-development",
"category": "uncategorized",
"name": "voice-ai-development",
- "description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis, LiveKit for real-time infrastructure, and WebRTC fundamentals. Knows how to build low-latency, production-ready voice experiences. Use when: voice ai, voice agent, speech to text, text to speech, realtime voice.",
+ "description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7449,7 +7980,7 @@
"name": "voice-ai-engine-development",
"description": "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vr-ar",
@@ -7458,7 +7989,7 @@
"name": "vr-ar",
"description": "VR/AR development principles. Comfort, interaction, performance requirements.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "vulnerability-scanner",
@@ -7467,34 +7998,34 @@
"name": "vulnerability-scanner",
"description": "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wcag-audit-patterns",
"path": "skills/wcag-audit-patterns",
"category": "uncategorized",
"name": "wcag-audit-patterns",
- "description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.",
+ "description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "web-artifacts-builder",
"path": "skills/web-artifacts-builder",
"category": "uncategorized",
"name": "web-artifacts-builder",
- "description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.",
+ "description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "web-design-guidelines",
"path": "skills/web-design-guidelines",
"category": "uncategorized",
"name": "web-design-guidelines",
- "description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".",
+ "description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "web-games",
@@ -7503,7 +8034,7 @@
"name": "web-games",
"description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "web-performance-optimization",
@@ -7512,25 +8043,34 @@
"name": "web-performance-optimization",
"description": "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "web-security-testing",
+ "path": "skills/web-security-testing",
+ "category": "uncategorized",
+ "name": "web-security-testing",
+ "description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "web3-testing",
"path": "skills/web3-testing",
"category": "uncategorized",
"name": "web3-testing",
- "description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.",
+ "description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "webapp-testing",
"path": "skills/webapp-testing",
"category": "uncategorized",
"name": "webapp-testing",
- "description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.",
+ "description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "webflow-automation",
@@ -7539,7 +8079,7 @@
"name": "webflow-automation",
"description": "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "whatsapp-automation",
@@ -7548,95 +8088,140 @@
"name": "whatsapp-automation",
"description": "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-architect",
"path": "skills/wiki-architect",
"category": "uncategorized",
"name": "wiki-architect",
- "description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.",
+ "description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-changelog",
"path": "skills/wiki-changelog",
"category": "uncategorized",
"name": "wiki-changelog",
- "description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.",
+ "description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-onboarding",
"path": "skills/wiki-onboarding",
"category": "uncategorized",
"name": "wiki-onboarding",
- "description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.",
+ "description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-page-writer",
"path": "skills/wiki-page-writer",
"category": "uncategorized",
"name": "wiki-page-writer",
- "description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.",
+ "description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-qa",
"path": "skills/wiki-qa",
"category": "uncategorized",
"name": "wiki-qa",
- "description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.",
+ "description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-researcher",
"path": "skills/wiki-researcher",
"category": "uncategorized",
"name": "wiki-researcher",
- "description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how something works across multiple files, or asks for comprehensive analysis of a specific system or pattern.",
+ "description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wiki-vitepress",
"path": "skills/wiki-vitepress",
"category": "uncategorized",
"name": "wiki-vitepress",
- "description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.",
+ "description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "windows-privilege-escalation",
"path": "skills/windows-privilege-escalation",
"category": "uncategorized",
- "name": "Windows Privilege Escalation",
- "description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows misconfigurations,\" or \"perform post-exploitation privilege escalation.\" It provides comprehensive guidance for discovering and exploiting privilege escalation vulnerabilities in Windows environments.",
+ "name": "windows-privilege-escalation",
+ "description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wireshark-analysis",
"path": "skills/wireshark-analysis",
"category": "uncategorized",
- "name": "Wireshark Network Traffic Analysis",
- "description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"detect network anomalies\", \"investigate suspicious traffic\", or \"perform protocol analysis\". It provides comprehensive techniques for network packet capture, filtering, and analysis using Wireshark.",
+ "name": "wireshark-analysis",
+ "description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "wordpress",
+ "path": "skills/wordpress",
+ "category": "uncategorized",
+ "name": "wordpress",
+ "description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "wordpress-penetration-testing",
"path": "skills/wordpress-penetration-testing",
"category": "uncategorized",
- "name": "WordPress Penetration Testing",
- "description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.",
+ "name": "wordpress-penetration-testing",
+ "description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu...",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "wordpress-plugin-development",
+ "path": "skills/wordpress-plugin-development",
+ "category": "uncategorized",
+ "name": "wordpress-plugin-development",
+ "description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "wordpress-theme-development",
+ "path": "skills/wordpress-theme-development",
+ "category": "uncategorized",
+ "name": "wordpress-theme-development",
+ "description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "wordpress-woocommerce-development",
+ "path": "skills/wordpress-woocommerce-development",
+ "category": "uncategorized",
+ "name": "wordpress-woocommerce-development",
+ "description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "workflow-patterns",
+ "path": "skills/workflow-patterns",
+ "category": "uncategorized",
+ "name": "Workflow Patterns",
+ "description": "Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.",
"risk": "unknown",
"source": "unknown"
},
@@ -7645,7 +8230,7 @@
"path": "skills/workflow-automation",
"category": "uncategorized",
"name": "workflow-automation",
- "description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility",
+ "description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7654,18 +8239,9 @@
"path": "skills/workflow-orchestration-patterns",
"category": "uncategorized",
"name": "workflow-orchestration-patterns",
- "description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.",
+ "description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ...",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "workflow-patterns",
- "path": "skills/workflow-patterns",
- "category": "uncategorized",
- "name": "workflow-patterns",
- "description": "Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "wrike-automation",
@@ -7674,7 +8250,16 @@
"name": "wrike-automation",
"description": "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "writer",
+ "path": "skills/libreoffice/writer",
+ "category": "libreoffice",
+ "name": "writer",
+ "description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
+ "risk": "safe",
+ "source": "personal"
},
{
"id": "writing-plans",
@@ -7683,7 +8268,7 @@
"name": "writing-plans",
"description": "Use when you have a spec or requirements for a multi-step task, before touching code",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "writing-skills",
@@ -7692,7 +8277,7 @@
"name": "writing-skills",
"description": "Use when creating, updating, or improving agent skills.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "x-article-publisher-skill",
@@ -7707,10 +8292,19 @@
"id": "xlsx-official",
"path": "skills/xlsx-official",
"category": "uncategorized",
- "name": "xlsx",
- "description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas",
+ "name": "xlsx-official",
+ "description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "xss-html-injection",
+ "path": "skills/xss-html-injection",
+ "category": "uncategorized",
+ "name": "xss-html-injection",
+ "description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection...",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "youtube-automation",
@@ -7719,7 +8313,7 @@
"name": "youtube-automation",
"description": "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "youtube-summarizer",
@@ -7728,14 +8322,14 @@
"name": "youtube-summarizer",
"description": "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks",
"risk": "safe",
- "source": "unknown"
+ "source": "community"
},
{
"id": "zapier-make-patterns",
"path": "skills/zapier-make-patterns",
"category": "uncategorized",
"name": "zapier-make-patterns",
- "description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power ",
+ "description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
@@ -7746,7 +8340,7 @@
"name": "zendesk-automation",
"description": "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "zoho-crm-automation",
@@ -7755,7 +8349,7 @@
"name": "zoho-crm-automation",
"description": "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "zoom-automation",
@@ -7764,15 +8358,15 @@
"name": "zoom-automation",
"description": "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "zustand-store-ts",
"path": "skills/zustand-store-ts",
"category": "uncategorized",
"name": "zustand-store-ts",
- "description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.",
+ "description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
}
]
\ No newline at end of file
diff --git a/web-app/public/skills/3d-web-experience/SKILL.md b/web-app/public/skills/3d-web-experience/SKILL.md
index 7a7ae4af..5a2692d4 100644
--- a/web-app/public/skills/3d-web-experience/SKILL.md
+++ b/web-app/public/skills/3d-web-experience/SKILL.md
@@ -1,7 +1,8 @@
---
name: 3d-web-experience
-description: "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience."
+description: "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# 3D Web Experience
@@ -252,3 +253,6 @@ Optimize model size.
## Related Skills
Works well with: `scroll-experience`, `interactive-portfolio`, `frontend`, `landing-page-design`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ab-test-setup/SKILL.md b/web-app/public/skills/ab-test-setup/SKILL.md
index 2c5ae483..12ead27c 100644
--- a/web-app/public/skills/ab-test-setup/SKILL.md
+++ b/web-app/public/skills/ab-test-setup/SKILL.md
@@ -1,6 +1,8 @@
---
name: ab-test-setup
-description: Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
+description: "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
+risk: unknown
+source: community
---
# A/B Test Setup
@@ -230,3 +232,6 @@ It is about **learning the truth with confidence**.
If you feel tempted to rush, simplify, or “just try it” —
that is the signal to **slow down and re-check the design**.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/accessibility-compliance-accessibility-audit/SKILL.md b/web-app/public/skills/accessibility-compliance-accessibility-audit/SKILL.md
index db667511..172a8f37 100644
--- a/web-app/public/skills/accessibility-compliance-accessibility-audit/SKILL.md
+++ b/web-app/public/skills/accessibility-compliance-accessibility-audit/SKILL.md
@@ -1,6 +1,8 @@
---
name: accessibility-compliance-accessibility-audit
description: "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance."
+risk: unknown
+source: community
---
# Accessibility Audit and Testing
diff --git a/web-app/public/skills/active-directory-attacks/SKILL.md b/web-app/public/skills/active-directory-attacks/SKILL.md
index 654fbae3..10ffb5fa 100644
--- a/web-app/public/skills/active-directory-attacks/SKILL.md
+++ b/web-app/public/skills/active-directory-attacks/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Active Directory Attacks
-description: This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
+name: active-directory-attacks
+description: "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Active Directory Attacks
@@ -381,3 +383,6 @@ python3 printerbug.py domain.local/user:pass@target 10.10.10.12
## Additional Resources
For advanced techniques including delegation attacks, GPO abuse, RODC attacks, SCCM/WSUS deployment, ADCS exploitation, trust relationships, and Linux AD integration, see [references/advanced-attacks.md](references/advanced-attacks.md).
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/activecampaign-automation/SKILL.md b/web-app/public/skills/activecampaign-automation/SKILL.md
index f618bc0e..f2f447c7 100644
--- a/web-app/public/skills/activecampaign-automation/SKILL.md
+++ b/web-app/public/skills/activecampaign-automation/SKILL.md
@@ -3,6 +3,8 @@ name: activecampaign-automation
description: "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# ActiveCampaign Automation via Rube MCP
@@ -207,3 +209,6 @@ Automate ActiveCampaign CRM and marketing automation operations through Composio
| Subscribe/unsubscribe | ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION | action, list_id, email |
| Add to automation | ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION | contact_email, automation_id |
| Create task | ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK | relid, duedate, dealTasktype, title |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/address-github-comments/SKILL.md b/web-app/public/skills/address-github-comments/SKILL.md
index 424fab73..39abb26b 100644
--- a/web-app/public/skills/address-github-comments/SKILL.md
+++ b/web-app/public/skills/address-github-comments/SKILL.md
@@ -1,6 +1,8 @@
---
name: address-github-comments
-description: Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
+description: "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI."
+risk: unknown
+source: community
---
# Address GitHub Comments
@@ -53,3 +55,6 @@ gh pr comment --body "Addressed in latest commit."
- **Applying fixes without understanding context**: Always read the surrounding code of a comment.
- **Not verifying auth**: Check `gh auth status` before starting.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agent-evaluation/SKILL.md b/web-app/public/skills/agent-evaluation/SKILL.md
index 964c6184..d0329bb3 100644
--- a/web-app/public/skills/agent-evaluation/SKILL.md
+++ b/web-app/public/skills/agent-evaluation/SKILL.md
@@ -1,7 +1,8 @@
---
name: agent-evaluation
-description: "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent."
+description: "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Agent Evaluation
@@ -62,3 +63,6 @@ Actively try to break agent behavior
## Related Skills
Works well with: `multi-agent-orchestration`, `agent-communication`, `autonomous-agents`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agent-framework-azure-ai-py/SKILL.md b/web-app/public/skills/agent-framework-azure-ai-py/SKILL.md
index 74da0813..a4a0ddb0 100644
--- a/web-app/public/skills/agent-framework-azure-ai-py/SKILL.md
+++ b/web-app/public/skills/agent-framework-azure-ai-py/SKILL.md
@@ -1,7 +1,9 @@
---
name: agent-framework-azure-ai-py
-description: Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code interpreter, file search, web search), integrating MCP servers, managing conversation threads, or implementing streaming responses. Covers function tools, structured outputs, and multi-tool agents.
+description: "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int..."
package: agent-framework-azure-ai
+risk: unknown
+source: community
---
# Agent Framework Azure Hosted Agents
@@ -327,7 +329,10 @@ if __name__ == "__main__":
## Reference Files
-- [references/tools.md](references/tools.md): Detailed hosted tool patterns
-- [references/mcp.md](references/mcp.md): MCP integration (hosted + local)
-- [references/threads.md](references/threads.md): Thread and conversation management
-- [references/advanced.md](references/advanced.md): OpenAPI, citations, structured outputs
+- references/tools.md: Detailed hosted tool patterns
+- references/mcp.md: MCP integration (hosted + local)
+- references/threads.md: Thread and conversation management
+- references/advanced.md: OpenAPI, citations, structured outputs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agent-manager-skill/SKILL.md b/web-app/public/skills/agent-manager-skill/SKILL.md
index 2660641f..2df4b9cc 100644
--- a/web-app/public/skills/agent-manager-skill/SKILL.md
+++ b/web-app/public/skills/agent-manager-skill/SKILL.md
@@ -1,6 +1,8 @@
---
name: agent-manager-skill
-description: Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
+description: "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling."
+risk: unknown
+source: community
---
# Agent Manager Skill
diff --git a/web-app/public/skills/agent-memory-mcp/SKILL.md b/web-app/public/skills/agent-memory-mcp/SKILL.md
index 45d96513..24964e98 100644
--- a/web-app/public/skills/agent-memory-mcp/SKILL.md
+++ b/web-app/public/skills/agent-memory-mcp/SKILL.md
@@ -1,7 +1,9 @@
---
name: agent-memory-mcp
author: Amit Rathiesh
-description: A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
+description: "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions)."
+risk: unknown
+source: community
---
# Agent Memory Skill
@@ -80,3 +82,6 @@ npm run start-dashboard
```
Access at: `http://localhost:3333`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agent-memory-systems/SKILL.md b/web-app/public/skills/agent-memory-systems/SKILL.md
index ee791180..c9580e0b 100644
--- a/web-app/public/skills/agent-memory-systems/SKILL.md
+++ b/web-app/public/skills/agent-memory-systems/SKILL.md
@@ -1,7 +1,8 @@
---
name: agent-memory-systems
-description: "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm"
+description: "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Agent Memory Systems
@@ -65,3 +66,6 @@ Breaking documents into retrievable chunks
## Related Skills
Works well with: `autonomous-agents`, `multi-agent-orchestration`, `llm-architect`, `agent-tool-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agent-orchestration-improve-agent/SKILL.md b/web-app/public/skills/agent-orchestration-improve-agent/SKILL.md
index 74f211bb..2ed4aacd 100644
--- a/web-app/public/skills/agent-orchestration-improve-agent/SKILL.md
+++ b/web-app/public/skills/agent-orchestration-improve-agent/SKILL.md
@@ -1,6 +1,8 @@
---
name: agent-orchestration-improve-agent
description: "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration."
+risk: unknown
+source: community
---
# Agent Performance Optimization Workflow
diff --git a/web-app/public/skills/agent-orchestration-multi-agent-optimize/SKILL.md b/web-app/public/skills/agent-orchestration-multi-agent-optimize/SKILL.md
index 03214ca5..6bb75c78 100644
--- a/web-app/public/skills/agent-orchestration-multi-agent-optimize/SKILL.md
+++ b/web-app/public/skills/agent-orchestration-multi-agent-optimize/SKILL.md
@@ -1,6 +1,8 @@
---
name: agent-orchestration-multi-agent-optimize
description: "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability."
+risk: unknown
+source: community
---
# Multi-Agent Optimization Toolkit
diff --git a/web-app/public/skills/agent-tool-builder/SKILL.md b/web-app/public/skills/agent-tool-builder/SKILL.md
index 635043fe..473e17ae 100644
--- a/web-app/public/skills/agent-tool-builder/SKILL.md
+++ b/web-app/public/skills/agent-tool-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: agent-tool-builder
-description: "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa"
+description: "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Agent Tool Builder
@@ -51,3 +52,6 @@ Returning errors that help the LLM recover
## Related Skills
Works well with: `multi-agent-orchestration`, `api-designer`, `llm-architect`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/agents-v2-py/SKILL.md b/web-app/public/skills/agents-v2-py/SKILL.md
index 8405a3ff..c7879aad 100644
--- a/web-app/public/skills/agents-v2-py/SKILL.md
+++ b/web-app/public/skills/agents-v2-py/SKILL.md
@@ -1,11 +1,9 @@
---
name: agents-v2-py
-description: |
- Build container-based Foundry Agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition.
- Use when creating hosted agents that run custom code in Azure AI Foundry with your own container images.
- Triggers: "ImageBasedHostedAgentDefinition", "hosted agent", "container agent", "Foundry Agent",
- "create_version", "ProtocolVersionRecord", "AgentProtocol.RESPONSES", "custom agent image".
+description: "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry."
package: azure-ai-projects
+risk: unknown
+source: community
---
# Azure AI Hosted Agents (Python)
@@ -323,3 +321,6 @@ async def create_hosted_agent_async():
- [Azure AI Projects SDK](https://pypi.org/project/azure-ai-projects/)
- [Hosted Agents Documentation](https://learn.microsoft.com/azure/ai-services/agents/how-to/hosted-agents)
- [Azure Container Registry](https://learn.microsoft.com/azure/container-registry/)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ai-agent-development/SKILL.md b/web-app/public/skills/ai-agent-development/SKILL.md
new file mode 100644
index 00000000..b0086e2b
--- /dev/null
+++ b/web-app/public/skills/ai-agent-development/SKILL.md
@@ -0,0 +1,174 @@
+---
+name: ai-agent-development
+description: "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents."
+source: personal
+risk: safe
+domain: ai-ml
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# AI Agent Development Workflow
+
+## Overview
+
+Specialized workflow for building AI agents including single autonomous agents, multi-agent systems, agent orchestration, tool integration, and human-in-the-loop patterns.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building autonomous AI agents
+- Creating multi-agent systems
+- Implementing agent orchestration
+- Adding tool integration to agents
+- Setting up agent memory
+
+## Workflow Phases
+
+### Phase 1: Agent Design
+
+#### Skills to Invoke
+- `ai-agents-architect` - Agent architecture
+- `autonomous-agents` - Autonomous patterns
+
+#### Actions
+1. Define agent purpose
+2. Design agent capabilities
+3. Plan tool integration
+4. Design memory system
+5. Define success metrics
+
+#### Copy-Paste Prompts
+```
+Use @ai-agents-architect to design AI agent architecture
+```
+
+### Phase 2: Single Agent Implementation
+
+#### Skills to Invoke
+- `autonomous-agent-patterns` - Agent patterns
+- `autonomous-agents` - Autonomous agents
+
+#### Actions
+1. Choose agent framework
+2. Implement agent logic
+3. Add tool integration
+4. Configure memory
+5. Test agent behavior
+
+#### Copy-Paste Prompts
+```
+Use @autonomous-agent-patterns to implement single agent
+```
+
+### Phase 3: Multi-Agent System
+
+#### Skills to Invoke
+- `crewai` - CrewAI framework
+- `multi-agent-patterns` - Multi-agent patterns
+
+#### Actions
+1. Define agent roles
+2. Set up agent communication
+3. Configure orchestration
+4. Implement task delegation
+5. Test coordination
+
+#### Copy-Paste Prompts
+```
+Use @crewai to build multi-agent system with roles
+```
+
+### Phase 4: Agent Orchestration
+
+#### Skills to Invoke
+- `langgraph` - LangGraph orchestration
+- `workflow-orchestration-patterns` - Orchestration
+
+#### Actions
+1. Design workflow graph
+2. Implement state management
+3. Add conditional branches
+4. Configure persistence
+5. Test workflows
+
+#### Copy-Paste Prompts
+```
+Use @langgraph to create stateful agent workflows
+```
+
+### Phase 5: Tool Integration
+
+#### Skills to Invoke
+- `agent-tool-builder` - Tool building
+- `tool-design` - Tool design
+
+#### Actions
+1. Identify tool needs
+2. Design tool interfaces
+3. Implement tools
+4. Add error handling
+5. Test tool usage
+
+#### Copy-Paste Prompts
+```
+Use @agent-tool-builder to create agent tools
+```
+
+### Phase 6: Memory Systems
+
+#### Skills to Invoke
+- `agent-memory-systems` - Memory architecture
+- `conversation-memory` - Conversation memory
+
+#### Actions
+1. Design memory structure
+2. Implement short-term memory
+3. Set up long-term memory
+4. Add entity memory
+5. Test memory retrieval
+
+#### Copy-Paste Prompts
+```
+Use @agent-memory-systems to implement agent memory
+```
+
+### Phase 7: Evaluation
+
+#### Skills to Invoke
+- `agent-evaluation` - Agent evaluation
+- `evaluation` - AI evaluation
+
+#### Actions
+1. Define evaluation criteria
+2. Create test scenarios
+3. Measure agent performance
+4. Test edge cases
+5. Iterate improvements
+
+#### Copy-Paste Prompts
+```
+Use @agent-evaluation to evaluate agent performance
+```
+
+## Agent Architecture
+
+```
+User Input -> Planner -> Agent -> Tools -> Memory -> Response
+ | | | |
+ Decompose LLM Core Actions Short/Long-term
+```
+
+## Quality Gates
+
+- [ ] Agent logic working
+- [ ] Tools integrated
+- [ ] Memory functional
+- [ ] Orchestration tested
+- [ ] Evaluation passing
+
+## Related Workflow Bundles
+
+- `ai-ml` - AI/ML development
+- `rag-implementation` - RAG systems
+- `workflow-automation` - Workflow patterns
diff --git a/web-app/public/skills/ai-agents-architect/SKILL.md b/web-app/public/skills/ai-agents-architect/SKILL.md
index 10f97b60..c9a637b6 100644
--- a/web-app/public/skills/ai-agents-architect/SKILL.md
+++ b/web-app/public/skills/ai-agents-architect/SKILL.md
@@ -1,7 +1,8 @@
---
name: ai-agents-architect
-description: "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool use, function calling."
+description: "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# AI Agents Architect
@@ -88,3 +89,6 @@ Dynamic tool discovery and management
## Related Skills
Works well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ai-engineer/SKILL.md b/web-app/public/skills/ai-engineer/SKILL.md
index e9d2cde0..0f949484 100644
--- a/web-app/public/skills/ai-engineer/SKILL.md
+++ b/web-app/public/skills/ai-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: ai-engineer
-description: Build production-ready LLM applications, advanced RAG systems, and
+description: "Build production-ready LLM applications, advanced RAG systems, and"
intelligent agents. Implements vector search, multimodal AI, agent
orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM
features, chatbots, AI agents, or AI-powered applications.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.
diff --git a/web-app/public/skills/ai-ml/SKILL.md b/web-app/public/skills/ai-ml/SKILL.md
new file mode 100644
index 00000000..350681e5
--- /dev/null
+++ b/web-app/public/skills/ai-ml/SKILL.md
@@ -0,0 +1,253 @@
+---
+name: ai-ml
+description: "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features."
+source: personal
+risk: safe
+domain: artificial-intelligence
+category: workflow-bundle
+version: 1.0.0
+---
+
+# AI/ML Workflow Bundle
+
+## Overview
+
+Comprehensive AI/ML workflow for building LLM applications, implementing RAG systems, creating AI agents, and developing machine learning pipelines. This bundle orchestrates skills for production AI development.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building LLM-powered applications
+- Implementing RAG (Retrieval-Augmented Generation)
+- Creating AI agents
+- Developing ML pipelines
+- Adding AI features to applications
+- Setting up AI observability
+
+## Workflow Phases
+
+### Phase 1: AI Application Design
+
+#### Skills to Invoke
+- `ai-product` - AI product development
+- `ai-engineer` - AI engineering
+- `ai-agents-architect` - Agent architecture
+- `llm-app-patterns` - LLM patterns
+
+#### Actions
+1. Define AI use cases
+2. Choose appropriate models
+3. Design system architecture
+4. Plan data flows
+5. Define success metrics
+
+#### Copy-Paste Prompts
+```
+Use @ai-product to design AI-powered features
+```
+
+```
+Use @ai-agents-architect to design multi-agent system
+```
+
+### Phase 2: LLM Integration
+
+#### Skills to Invoke
+- `llm-application-dev-ai-assistant` - AI assistant development
+- `llm-application-dev-langchain-agent` - LangChain agents
+- `llm-application-dev-prompt-optimize` - Prompt engineering
+- `gemini-api-dev` - Gemini API
+
+#### Actions
+1. Select LLM provider
+2. Set up API access
+3. Implement prompt templates
+4. Configure model parameters
+5. Add streaming support
+6. Implement error handling
+
+#### Copy-Paste Prompts
+```
+Use @llm-application-dev-ai-assistant to build conversational AI
+```
+
+```
+Use @llm-application-dev-langchain-agent to create LangChain agents
+```
+
+```
+Use @llm-application-dev-prompt-optimize to optimize prompts
+```
+
+### Phase 3: RAG Implementation
+
+#### Skills to Invoke
+- `rag-engineer` - RAG engineering
+- `rag-implementation` - RAG implementation
+- `embedding-strategies` - Embedding selection
+- `vector-database-engineer` - Vector databases
+- `similarity-search-patterns` - Similarity search
+- `hybrid-search-implementation` - Hybrid search
+
+#### Actions
+1. Design data pipeline
+2. Choose embedding model
+3. Set up vector database
+4. Implement chunking strategy
+5. Configure retrieval
+6. Add reranking
+7. Implement caching
+
+#### Copy-Paste Prompts
+```
+Use @rag-engineer to design RAG pipeline
+```
+
+```
+Use @vector-database-engineer to set up vector search
+```
+
+```
+Use @embedding-strategies to select optimal embeddings
+```
+
+### Phase 4: AI Agent Development
+
+#### Skills to Invoke
+- `autonomous-agents` - Autonomous agent patterns
+- `autonomous-agent-patterns` - Agent patterns
+- `crewai` - CrewAI framework
+- `langgraph` - LangGraph
+- `multi-agent-patterns` - Multi-agent systems
+- `computer-use-agents` - Computer use agents
+
+#### Actions
+1. Design agent architecture
+2. Define agent roles
+3. Implement tool integration
+4. Set up memory systems
+5. Configure orchestration
+6. Add human-in-the-loop
+
+#### Copy-Paste Prompts
+```
+Use @crewai to build role-based multi-agent system
+```
+
+```
+Use @langgraph to create stateful AI workflows
+```
+
+```
+Use @autonomous-agents to design autonomous agent
+```
+
+### Phase 5: ML Pipeline Development
+
+#### Skills to Invoke
+- `ml-engineer` - ML engineering
+- `mlops-engineer` - MLOps
+- `machine-learning-ops-ml-pipeline` - ML pipelines
+- `ml-pipeline-workflow` - ML workflows
+- `data-engineer` - Data engineering
+
+#### Actions
+1. Design ML pipeline
+2. Set up data processing
+3. Implement model training
+4. Configure evaluation
+5. Set up model registry
+6. Deploy models
+
+#### Copy-Paste Prompts
+```
+Use @ml-engineer to build machine learning pipeline
+```
+
+```
+Use @mlops-engineer to set up MLOps infrastructure
+```
+
+### Phase 6: AI Observability
+
+#### Skills to Invoke
+- `langfuse` - Langfuse observability
+- `manifest` - Manifest telemetry
+- `evaluation` - AI evaluation
+- `llm-evaluation` - LLM evaluation
+
+#### Actions
+1. Set up tracing
+2. Configure logging
+3. Implement evaluation
+4. Monitor performance
+5. Track costs
+6. Set up alerts
+
+#### Copy-Paste Prompts
+```
+Use @langfuse to set up LLM observability
+```
+
+```
+Use @evaluation to create evaluation framework
+```
+
+### Phase 7: AI Security
+
+#### Skills to Invoke
+- `prompt-engineering` - Prompt security
+- `security-scanning-security-sast` - Security scanning
+
+#### Actions
+1. Implement input validation
+2. Add output filtering
+3. Configure rate limiting
+4. Set up access controls
+5. Monitor for abuse
+6. Implement audit logging
+
+## AI Development Checklist
+
+### LLM Integration
+- [ ] API keys secured
+- [ ] Rate limiting configured
+- [ ] Error handling implemented
+- [ ] Streaming enabled
+- [ ] Token usage tracked
+
+### RAG System
+- [ ] Data pipeline working
+- [ ] Embeddings generated
+- [ ] Vector search optimized
+- [ ] Retrieval accuracy tested
+- [ ] Caching implemented
+
+### AI Agents
+- [ ] Agent roles defined
+- [ ] Tools integrated
+- [ ] Memory working
+- [ ] Orchestration tested
+- [ ] Error handling robust
+
+### Observability
+- [ ] Tracing enabled
+- [ ] Metrics collected
+- [ ] Evaluation running
+- [ ] Alerts configured
+- [ ] Dashboards created
+
+## Quality Gates
+
+- [ ] All AI features tested
+- [ ] Performance benchmarks met
+- [ ] Security measures in place
+- [ ] Observability configured
+- [ ] Documentation complete
+
+## Related Workflow Bundles
+
+- `development` - Application development
+- `database` - Data management
+- `cloud-devops` - Infrastructure
+- `testing-qa` - AI testing
diff --git a/web-app/public/skills/ai-product/SKILL.md b/web-app/public/skills/ai-product/SKILL.md
index 5239cccf..5120c9b4 100644
--- a/web-app/public/skills/ai-product/SKILL.md
+++ b/web-app/public/skills/ai-product/SKILL.md
@@ -1,7 +1,8 @@
---
name: ai-product
-description: "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt engineering that scales, AI UX that users trust, and cost optimization that doesn't bankrupt you. Use when: keywords, file_patterns, code_patterns."
+description: "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# AI Product Development
@@ -52,3 +53,6 @@ Version prompts in code and test with regression suite
| App breaks when LLM API fails | high | # Defense in depth: |
| Not validating facts from LLM responses | critical | # For factual claims: |
| Making LLM calls in synchronous request handlers | high | # Async patterns: |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ai-wrapper-product/SKILL.md b/web-app/public/skills/ai-wrapper-product/SKILL.md
index f7216906..fa317f5a 100644
--- a/web-app/public/skills/ai-wrapper-product/SKILL.md
+++ b/web-app/public/skills/ai-wrapper-product/SKILL.md
@@ -1,7 +1,8 @@
---
name: ai-wrapper-product
-description: "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Covers prompt engineering for products, cost management, rate limiting, and building defensible AI businesses. Use when: AI wrapper, GPT product, AI tool, wrap AI, AI SaaS."
+description: "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# AI Wrapper Product
@@ -271,3 +272,6 @@ Post-process for consistency.
## Related Skills
Works well with: `llm-architect`, `micro-saas-launcher`, `frontend`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/airflow-dag-patterns/SKILL.md b/web-app/public/skills/airflow-dag-patterns/SKILL.md
index 76415d47..4017e79f 100644
--- a/web-app/public/skills/airflow-dag-patterns/SKILL.md
+++ b/web-app/public/skills/airflow-dag-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: airflow-dag-patterns
-description: Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
+description: "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs."
+risk: unknown
+source: community
---
# Apache Airflow DAG Patterns
diff --git a/web-app/public/skills/airtable-automation/SKILL.md b/web-app/public/skills/airtable-automation/SKILL.md
index 1a39963c..01b635c4 100644
--- a/web-app/public/skills/airtable-automation/SKILL.md
+++ b/web-app/public/skills/airtable-automation/SKILL.md
@@ -3,6 +3,8 @@ name: airtable-automation
description: "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Airtable Automation via Rube MCP
@@ -168,3 +170,6 @@ Automate Airtable operations through Composio's Airtable toolkit via Rube MCP.
| Update field | AIRTABLE_UPDATE_FIELD | baseId, tableIdOrName, fieldId |
| Update table | AIRTABLE_UPDATE_TABLE | baseId, tableIdOrName, name |
| List comments | AIRTABLE_LIST_COMMENTS | baseId, tableIdOrName, recordId |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/algolia-search/SKILL.md b/web-app/public/skills/algolia-search/SKILL.md
index 0e0dd6dc..82504bd4 100644
--- a/web-app/public/skills/algolia-search/SKILL.md
+++ b/web-app/public/skills/algolia-search/SKILL.md
@@ -2,6 +2,7 @@
name: algolia-search
description: "Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Algolia Search Integration
@@ -64,3 +65,6 @@ Best practices:
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | medium | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/algorithmic-art/SKILL.md b/web-app/public/skills/algorithmic-art/SKILL.md
index 634f6fa4..e8557c27 100644
--- a/web-app/public/skills/algorithmic-art/SKILL.md
+++ b/web-app/public/skills/algorithmic-art/SKILL.md
@@ -1,7 +1,9 @@
---
name: algorithmic-art
-description: Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
+description: "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).
@@ -402,4 +404,7 @@ This skill includes helpful templates and documentation:
- The **template is the STARTING POINT**, not inspiration
- The **algorithm is where to create** something unique
- Don't copy the flow field example - build what the philosophy demands
-- But DO keep the exact UI structure and Anthropic branding from the template
\ No newline at end of file
+- But DO keep the exact UI structure and Anthropic branding from the template
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/amplitude-automation/SKILL.md b/web-app/public/skills/amplitude-automation/SKILL.md
index c9b23c0f..710dc04d 100644
--- a/web-app/public/skills/amplitude-automation/SKILL.md
+++ b/web-app/public/skills/amplitude-automation/SKILL.md
@@ -3,6 +3,8 @@ name: amplitude-automation
description: "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Amplitude Automation via Rube MCP
@@ -214,3 +216,6 @@ For cohort membership updates:
| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |
| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |
| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/analytics-tracking/SKILL.md b/web-app/public/skills/analytics-tracking/SKILL.md
index 475e43d8..d25e5f1c 100644
--- a/web-app/public/skills/analytics-tracking/SKILL.md
+++ b/web-app/public/skills/analytics-tracking/SKILL.md
@@ -1,11 +1,13 @@
---
name: analytics-tracking
-description: >
+description: ">"
Design, audit, and improve analytics tracking systems that produce reliable,
decision-ready data. Use when the user wants to set up, fix, or evaluate
analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs).
This skill focuses on measurement strategy, signal quality, and validation—
not just firing events.
+risk: unknown
+source: community
---
# Analytics Tracking & Measurement Strategy
@@ -402,3 +404,6 @@ Analytics that violate trust undermine optimization.
* **programmatic-seo** – Scale requires reliable signals
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/android-jetpack-compose-expert/SKILL.md b/web-app/public/skills/android-jetpack-compose-expert/SKILL.md
new file mode 100644
index 00000000..93daf87d
--- /dev/null
+++ b/web-app/public/skills/android-jetpack-compose-expert/SKILL.md
@@ -0,0 +1,152 @@
+---
+name: android-jetpack-compose-expert
+description: Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.
+risk: safe
+source: community
+---
+
+# Android Jetpack Compose Expert
+
+## Overview
+
+A comprehensive guide for building production-quality Android applications using Jetpack Compose. This skill covers architectural patterns, state management with ViewModels, navigation type-safety, and performance optimization techniques.
+
+## When to Use This Skill
+
+- Use when starting a new Android project with Jetpack Compose.
+- Use when migrating legacy XML layouts to Compose.
+- Use when implementing complex UI state management and side effects.
+- Use when optimizing Compose performance (recomposition counts, stability).
+- Use when setting up Navigation with type safety.
+
+## Step-by-Step Guide
+
+### 1. Project Setup & Dependencies
+
+Ensure your `libs.versions.toml` includes the necessary Compose BOM and libraries.
+
+```kotlin
+[versions]
+composeBom = "2024.02.01"
+activityCompose = "1.8.2"
+
+[libraries]
+androidx-compose-bom = { group = "androidx.compose", name = "compose-bom", version.ref = "composeBom" }
+androidx-ui = { group = "androidx.compose.ui", name = "ui" }
+androidx-ui-graphics = { group = "androidx.compose.ui", name = "ui-graphics" }
+androidx-ui-tooling-preview = { group = "androidx.compose.ui", name = "ui-tooling-preview" }
+androidx-material3 = { group = "androidx.compose.material3", name = "material3" }
+androidx-activity-compose = { group = "androidx.activity", name = "activity-compose", version.ref = "activityCompose" }
+```
+
+### 2. State Management Pattern (MVI/MVVM)
+
+Use `ViewModel` with `StateFlow` to expose UI state. Avoid exposing `MutableStateFlow`.
+
+```kotlin
+// UI State Definition
+data class UserUiState(
+ val isLoading: Boolean = false,
+ val user: User? = null,
+ val error: String? = null
+)
+
+// ViewModel
+class UserViewModel @Inject constructor(
+ private val userRepository: UserRepository
+) : ViewModel() {
+
+ private val _uiState = MutableStateFlow(UserUiState())
+ val uiState: StateFlow = _uiState.asStateFlow()
+
+ fun loadUser() {
+ viewModelScope.launch {
+ _uiState.update { it.copy(isLoading = true) }
+ try {
+ val user = userRepository.getUser()
+ _uiState.update { it.copy(user = user, isLoading = false) }
+ } catch (e: Exception) {
+ _uiState.update { it.copy(error = e.message, isLoading = false) }
+ }
+ }
+ }
+}
+```
+
+### 3. Creating the Screen Composable
+
+Consume the state in a "Screen" composable and pass data down to stateless components.
+
+```kotlin
+@Composable
+fun UserScreen(
+ viewModel: UserViewModel = hiltViewModel()
+) {
+ val uiState by viewModel.uiState.collectAsStateWithLifecycle()
+
+ UserContent(
+ uiState = uiState,
+ onRetry = viewModel::loadUser
+ )
+}
+
+@Composable
+fun UserContent(
+ uiState: UserUiState,
+ onRetry: () -> Unit
+) {
+ Scaffold { padding ->
+ Box(modifier = Modifier.padding(padding)) {
+ when {
+ uiState.isLoading -> CircularProgressIndicator()
+ uiState.error != null -> ErrorView(uiState.error, onRetry)
+ uiState.user != null -> UserProfile(uiState.user)
+ }
+ }
+ }
+}
+```
+
+## Examples
+
+### Example 1: Type-Safe Navigation
+
+Using the new Navigation Compose Type Safety (available in recent versions).
+
+```kotlin
+// Define Destinations
+@Serializable
+object Home
+
+@Serializable
+data class Profile(val userId: String)
+
+// Setup NavHost
+@Composable
+fun AppNavHost(navController: NavHostController) {
+ NavHost(navController, startDestination = Home) {
+ composable {
+ HomeScreen(onNavigateToProfile = { id ->
+ navController.navigate(Profile(userId = id))
+ })
+ }
+ composable { backStackEntry ->
+ val profile: Profile = backStackEntry.toRoute()
+ ProfileScreen(userId = profile.userId)
+ }
+ }
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `remember` and `derivedStateOf` to minimize unnecessary calculations during recomposition.
+- ✅ **Do:** Mark data classes used in UI state as `@Immutable` or `@Stable` if they contain `List` or other unstable types to enable smart recomposition skipping.
+- ✅ **Do:** Use `LaunchedEffect` for one-off side effects (like showing a Snackbar) triggered by state changes.
+- ❌ **Don't:** Perform expensive operations (like sorting a list) directly inside the Composable function body without `remember`.
+- ❌ **Don't:** Pass `ViewModel` instances down to child components. Pass only the data (state) and lambda callbacks (events).
+
+## Troubleshooting
+
+**Problem:** Infinite Recomposition loop.
+**Solution:** Check if you are creating new object instances (like `List` or `Modifier`) inside the composition without `remember`, or if you are updating state inside the composition phase instead of a side-effect or callback. Use Layout Inspector to debug recomposition counts.
diff --git a/web-app/public/skills/angular-best-practices/SKILL.md b/web-app/public/skills/angular-best-practices/SKILL.md
index c2920a58..599fcfe5 100644
--- a/web-app/public/skills/angular-best-practices/SKILL.md
+++ b/web-app/public/skills/angular-best-practices/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular-best-practices
-description: Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
+description: "Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency."
risk: safe
source: self
---
@@ -557,3 +557,6 @@ export class Component implements OnInit, OnDestroy {
- [Zoneless Angular](https://angular.dev/guide/experimental/zoneless)
- [Angular SSR Guide](https://angular.dev/guide/ssr)
- [Change Detection Deep Dive](https://angular.dev/guide/change-detection)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/angular-migration/SKILL.md b/web-app/public/skills/angular-migration/SKILL.md
index 89a255c3..19a9d714 100644
--- a/web-app/public/skills/angular-migration/SKILL.md
+++ b/web-app/public/skills/angular-migration/SKILL.md
@@ -1,6 +1,8 @@
---
name: angular-migration
-description: Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.
+description: "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ..."
+risk: unknown
+source: community
---
# Angular Migration
diff --git a/web-app/public/skills/angular-state-management/SKILL.md b/web-app/public/skills/angular-state-management/SKILL.md
index c57b1885..c1cb2a21 100644
--- a/web-app/public/skills/angular-state-management/SKILL.md
+++ b/web-app/public/skills/angular-state-management/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular-state-management
-description: Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.
+description: "Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns."
risk: safe
source: self
---
diff --git a/web-app/public/skills/angular-ui-patterns/SKILL.md b/web-app/public/skills/angular-ui-patterns/SKILL.md
index 57b40126..9f243afb 100644
--- a/web-app/public/skills/angular-ui-patterns/SKILL.md
+++ b/web-app/public/skills/angular-ui-patterns/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular-ui-patterns
-description: Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.
+description: "Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states."
risk: safe
source: self
---
@@ -506,3 +506,6 @@ Before completing any UI component:
- **angular-state-management**: Use Signal stores for state
- **angular**: Apply modern patterns (Signals, @defer)
- **testing-patterns**: Test all UI states
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/angular/SKILL.md b/web-app/public/skills/angular/SKILL.md
index 7352d107..964a8cc8 100644
--- a/web-app/public/skills/angular/SKILL.md
+++ b/web-app/public/skills/angular/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular
-description: >-
+description: ">-"
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone
Components, Zoneless applications, SSR/Hydration, and reactive patterns.
Use PROACTIVELY for Angular development, component architecture, state
diff --git a/web-app/public/skills/anti-reversing-techniques/SKILL.md b/web-app/public/skills/anti-reversing-techniques/SKILL.md
index 7b2579ed..9ebebfe6 100644
--- a/web-app/public/skills/anti-reversing-techniques/SKILL.md
+++ b/web-app/public/skills/anti-reversing-techniques/SKILL.md
@@ -1,6 +1,8 @@
---
name: anti-reversing-techniques
-description: Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.
+description: "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u..."
+risk: unknown
+source: community
---
> **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:
diff --git a/web-app/public/skills/api-design-principles/SKILL.md b/web-app/public/skills/api-design-principles/SKILL.md
index 707220a3..836094bb 100644
--- a/web-app/public/skills/api-design-principles/SKILL.md
+++ b/web-app/public/skills/api-design-principles/SKILL.md
@@ -1,6 +1,8 @@
---
name: api-design-principles
-description: Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
+description: "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing..."
+risk: unknown
+source: community
---
# API Design Principles
diff --git a/web-app/public/skills/api-documentation-generator/SKILL.md b/web-app/public/skills/api-documentation-generator/SKILL.md
index 631aa330..572f9342 100644
--- a/web-app/public/skills/api-documentation-generator/SKILL.md
+++ b/web-app/public/skills/api-documentation-generator/SKILL.md
@@ -1,6 +1,8 @@
---
name: api-documentation-generator
description: "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices"
+risk: unknown
+source: community
---
# API Documentation Generator
diff --git a/web-app/public/skills/api-documentation/SKILL.md b/web-app/public/skills/api-documentation/SKILL.md
new file mode 100644
index 00000000..e8b77394
--- /dev/null
+++ b/web-app/public/skills/api-documentation/SKILL.md
@@ -0,0 +1,164 @@
+---
+name: api-documentation
+description: "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation."
+source: personal
+risk: safe
+domain: documentation
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# API Documentation Workflow
+
+## Overview
+
+Specialized workflow for creating comprehensive API documentation including OpenAPI/Swagger specs, developer guides, code examples, and interactive documentation.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating API documentation
+- Generating OpenAPI specs
+- Writing developer guides
+- Adding code examples
+- Setting up API portals
+
+## Workflow Phases
+
+### Phase 1: API Discovery
+
+#### Skills to Invoke
+- `api-documenter` - API documentation
+- `api-design-principles` - API design
+
+#### Actions
+1. Inventory endpoints
+2. Document request/response
+3. Identify authentication
+4. Map error codes
+5. Note rate limits
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to discover and document API endpoints
+```
+
+### Phase 2: OpenAPI Specification
+
+#### Skills to Invoke
+- `openapi-spec-generation` - OpenAPI
+- `api-documenter` - API specs
+
+#### Actions
+1. Create OpenAPI schema
+2. Define paths
+3. Add schemas
+4. Configure security
+5. Add examples
+
+#### Copy-Paste Prompts
+```
+Use @openapi-spec-generation to create OpenAPI specification
+```
+
+### Phase 3: Developer Guide
+
+#### Skills to Invoke
+- `api-documentation-generator` - Documentation
+- `documentation-templates` - Templates
+
+#### Actions
+1. Create getting started
+2. Write authentication guide
+3. Document common patterns
+4. Add troubleshooting
+5. Create FAQ
+
+#### Copy-Paste Prompts
+```
+Use @api-documentation-generator to create developer guide
+```
+
+### Phase 4: Code Examples
+
+#### Skills to Invoke
+- `api-documenter` - Code examples
+- `tutorial-engineer` - Tutorials
+
+#### Actions
+1. Create example requests
+2. Write SDK examples
+3. Add curl examples
+4. Create tutorials
+5. Test examples
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to generate code examples
+```
+
+### Phase 5: Interactive Docs
+
+#### Skills to Invoke
+- `api-documenter` - Interactive docs
+
+#### Actions
+1. Set up Swagger UI
+2. Configure Redoc
+3. Add try-it functionality
+4. Test interactivity
+5. Deploy docs
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to set up interactive documentation
+```
+
+### Phase 6: Documentation Site
+
+#### Skills to Invoke
+- `docs-architect` - Documentation architecture
+- `wiki-page-writer` - Documentation
+
+#### Actions
+1. Choose platform
+2. Design structure
+3. Create pages
+4. Add navigation
+5. Configure search
+
+#### Copy-Paste Prompts
+```
+Use @docs-architect to design API documentation site
+```
+
+### Phase 7: Maintenance
+
+#### Skills to Invoke
+- `api-documenter` - Doc maintenance
+
+#### Actions
+1. Set up auto-generation
+2. Configure validation
+3. Add review process
+4. Schedule updates
+5. Monitor feedback
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to set up automated doc generation
+```
+
+## Quality Gates
+
+- [ ] OpenAPI spec complete
+- [ ] Developer guide written
+- [ ] Code examples working
+- [ ] Interactive docs functional
+- [ ] Documentation deployed
+
+## Related Workflow Bundles
+
+- `documentation` - Documentation
+- `api-development` - API development
+- `development` - Development
diff --git a/web-app/public/skills/api-documenter/SKILL.md b/web-app/public/skills/api-documenter/SKILL.md
index 1b672b9e..aa613598 100644
--- a/web-app/public/skills/api-documenter/SKILL.md
+++ b/web-app/public/skills/api-documenter/SKILL.md
@@ -1,11 +1,13 @@
---
name: api-documenter
-description: Master API documentation with OpenAPI 3.1, AI-powered tools, and
+description: "Master API documentation with OpenAPI 3.1, AI-powered tools, and"
modern developer experience practices. Create interactive docs, generate SDKs,
and build comprehensive developer portals. Use PROACTIVELY for API
documentation or developer portal creation.
metadata:
model: sonnet
+risk: unknown
+source: community
---
You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.
diff --git a/web-app/public/skills/api-fuzzing-bug-bounty/SKILL.md b/web-app/public/skills/api-fuzzing-bug-bounty/SKILL.md
index 7f5f17cd..4b91f492 100644
--- a/web-app/public/skills/api-fuzzing-bug-bounty/SKILL.md
+++ b/web-app/public/skills/api-fuzzing-bug-bounty/SKILL.md
@@ -1,9 +1,11 @@
---
-name: API Fuzzing for Bug Bounty
-description: This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
+name: api-fuzzing-bug-bounty
+description: "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# API Fuzzing for Bug Bounty
@@ -431,3 +433,6 @@ curl -X POST https://target.com/graphql \
| GraphQL introspection disabled | Use clairvoyance for schema reconstruction |
| Rate limited | Use IP rotation or batch requests |
| Can't find endpoints | Check Swagger, archive.org, JS files |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/api-patterns/SKILL.md b/web-app/public/skills/api-patterns/SKILL.md
index fbd4bef4..48a0cfc8 100644
--- a/web-app/public/skills/api-patterns/SKILL.md
+++ b/web-app/public/skills/api-patterns/SKILL.md
@@ -1,7 +1,9 @@
---
name: api-patterns
-description: API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
+description: "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# API Patterns
@@ -79,3 +81,6 @@ Before designing an API:
|--------|---------|---------|
| `scripts/api_validator.py` | API endpoint validation | `python scripts/api_validator.py ` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/api-security-best-practices/SKILL.md b/web-app/public/skills/api-security-best-practices/SKILL.md
index cccde944..6d8f1783 100644
--- a/web-app/public/skills/api-security-best-practices/SKILL.md
+++ b/web-app/public/skills/api-security-best-practices/SKILL.md
@@ -1,6 +1,8 @@
---
name: api-security-best-practices
description: "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities"
+risk: unknown
+source: community
---
# API Security Best Practices
diff --git a/web-app/public/skills/api-security-testing/SKILL.md b/web-app/public/skills/api-security-testing/SKILL.md
new file mode 100644
index 00000000..f8999350
--- /dev/null
+++ b/web-app/public/skills/api-security-testing/SKILL.md
@@ -0,0 +1,172 @@
+---
+name: api-security-testing
+description: "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices."
+source: personal
+risk: safe
+domain: security
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# API Security Testing Workflow
+
+## Overview
+
+Specialized workflow for testing REST and GraphQL API security including authentication, authorization, rate limiting, input validation, and API-specific vulnerabilities.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Testing REST API security
+- Assessing GraphQL endpoints
+- Validating API authentication
+- Testing API rate limiting
+- Bug bounty API testing
+
+## Workflow Phases
+
+### Phase 1: API Discovery
+
+#### Skills to Invoke
+- `api-fuzzing-bug-bounty` - API fuzzing
+- `scanning-tools` - API scanning
+
+#### Actions
+1. Enumerate endpoints
+2. Document API methods
+3. Identify parameters
+4. Map data flows
+5. Review documentation
+
+#### Copy-Paste Prompts
+```
+Use @api-fuzzing-bug-bounty to discover API endpoints
+```
+
+### Phase 2: Authentication Testing
+
+#### Skills to Invoke
+- `broken-authentication` - Auth testing
+- `api-security-best-practices` - API auth
+
+#### Actions
+1. Test API key validation
+2. Test JWT tokens
+3. Test OAuth2 flows
+4. Test token expiration
+5. Test refresh tokens
+
+#### Copy-Paste Prompts
+```
+Use @broken-authentication to test API authentication
+```
+
+### Phase 3: Authorization Testing
+
+#### Skills to Invoke
+- `idor-testing` - IDOR testing
+
+#### Actions
+1. Test object-level authorization
+2. Test function-level authorization
+3. Test role-based access
+4. Test privilege escalation
+5. Test multi-tenant isolation
+
+#### Copy-Paste Prompts
+```
+Use @idor-testing to test API authorization
+```
+
+### Phase 4: Input Validation
+
+#### Skills to Invoke
+- `api-fuzzing-bug-bounty` - API fuzzing
+- `sql-injection-testing` - Injection testing
+
+#### Actions
+1. Test parameter validation
+2. Test SQL injection
+3. Test NoSQL injection
+4. Test command injection
+5. Test XXE injection
+
+#### Copy-Paste Prompts
+```
+Use @api-fuzzing-bug-bounty to fuzz API parameters
+```
+
+### Phase 5: Rate Limiting
+
+#### Skills to Invoke
+- `api-security-best-practices` - Rate limiting
+
+#### Actions
+1. Test rate limit headers
+2. Test brute force protection
+3. Test resource exhaustion
+4. Test bypass techniques
+5. Document limitations
+
+#### Copy-Paste Prompts
+```
+Use @api-security-best-practices to test rate limiting
+```
+
+### Phase 6: GraphQL Testing
+
+#### Skills to Invoke
+- `api-fuzzing-bug-bounty` - GraphQL fuzzing
+
+#### Actions
+1. Test introspection
+2. Test query depth
+3. Test query complexity
+4. Test batch queries
+5. Test field suggestions
+
+#### Copy-Paste Prompts
+```
+Use @api-fuzzing-bug-bounty to test GraphQL security
+```
+
+### Phase 7: Error Handling
+
+#### Skills to Invoke
+- `api-security-best-practices` - Error handling
+
+#### Actions
+1. Test error messages
+2. Check information disclosure
+3. Test stack traces
+4. Verify logging
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @api-security-best-practices to audit API error handling
+```
+
+## API Security Checklist
+
+- [ ] Authentication working
+- [ ] Authorization enforced
+- [ ] Input validated
+- [ ] Rate limiting active
+- [ ] Errors sanitized
+- [ ] Logging enabled
+- [ ] CORS configured
+- [ ] HTTPS enforced
+
+## Quality Gates
+
+- [ ] All endpoints tested
+- [ ] Vulnerabilities documented
+- [ ] Remediation provided
+- [ ] Report generated
+
+## Related Workflow Bundles
+
+- `security-audit` - Security auditing
+- `web-security-testing` - Web security
+- `api-development` - API development
diff --git a/web-app/public/skills/api-testing-observability-api-mock/SKILL.md b/web-app/public/skills/api-testing-observability-api-mock/SKILL.md
index c422541f..b8c42d36 100644
--- a/web-app/public/skills/api-testing-observability-api-mock/SKILL.md
+++ b/web-app/public/skills/api-testing-observability-api-mock/SKILL.md
@@ -1,6 +1,8 @@
---
name: api-testing-observability-api-mock
description: "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development."
+risk: unknown
+source: community
---
# API Mocking Framework
diff --git a/web-app/public/skills/app-builder/SKILL.md b/web-app/public/skills/app-builder/SKILL.md
index 2850e08e..5474dd63 100644
--- a/web-app/public/skills/app-builder/SKILL.md
+++ b/web-app/public/skills/app-builder/SKILL.md
@@ -1,7 +1,9 @@
---
name: app-builder
-description: Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
+description: "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent
+risk: unknown
+source: community
---
# App Builder - Application Building Orchestrator
@@ -73,3 +75,6 @@ App Builder Process:
5. Report progress
6. Start preview
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/app-builder/templates/SKILL.md b/web-app/public/skills/app-builder/templates/SKILL.md
index 3c077190..b971cd8f 100644
--- a/web-app/public/skills/app-builder/templates/SKILL.md
+++ b/web-app/public/skills/app-builder/templates/SKILL.md
@@ -1,7 +1,9 @@
---
name: templates
-description: Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
+description: "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Project Templates
@@ -37,3 +39,6 @@ allowed-tools: Read, Glob, Grep
2. Match to appropriate template
3. Read ONLY that template's TEMPLATE.md
4. Follow its tech stack and structure
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/app-store-optimization/SKILL.md b/web-app/public/skills/app-store-optimization/SKILL.md
index c6fc1397..ff376df8 100644
--- a/web-app/public/skills/app-store-optimization/SKILL.md
+++ b/web-app/public/skills/app-store-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: app-store-optimization
-description: Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
+description: "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store"
+risk: unknown
+source: community
---
# App Store Optimization (ASO) Skill
@@ -401,3 +403,6 @@ This skill is based on current Apple App Store and Google Play Store requirement
- Google Play Console updates (play.google.com/console/about/guides/releasewithconfidence)
- iOS/Android version adoption rates (affects device testing)
- Store algorithm changes (follow ASO blogs and communities)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/application-performance-performance-optimization/SKILL.md b/web-app/public/skills/application-performance-performance-optimization/SKILL.md
index a9917dec..6d10be75 100644
--- a/web-app/public/skills/application-performance-performance-optimization/SKILL.md
+++ b/web-app/public/skills/application-performance-performance-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: application-performance-performance-optimization
description: "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack."
+risk: unknown
+source: community
---
Optimize application performance end-to-end using specialized performance and optimization agents:
diff --git a/web-app/public/skills/architect-review/SKILL.md b/web-app/public/skills/architect-review/SKILL.md
index a000409d..2067f790 100644
--- a/web-app/public/skills/architect-review/SKILL.md
+++ b/web-app/public/skills/architect-review/SKILL.md
@@ -6,6 +6,8 @@ description: Master software architect specializing in modern architecture
scalability, and maintainability. Use PROACTIVELY for architectural decisions.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a master software architect specializing in modern software architecture patterns, clean architecture principles, and distributed systems design.
diff --git a/web-app/public/skills/architecture-decision-records/SKILL.md b/web-app/public/skills/architecture-decision-records/SKILL.md
index dfaf558d..84f6a5e0 100644
--- a/web-app/public/skills/architecture-decision-records/SKILL.md
+++ b/web-app/public/skills/architecture-decision-records/SKILL.md
@@ -1,6 +1,8 @@
---
name: architecture-decision-records
-description: Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
+description: "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect..."
+risk: unknown
+source: community
---
# Architecture Decision Records
@@ -348,10 +350,10 @@ This directory contains Architecture Decision Records (ADRs) for [Project Name].
| ADR | Title | Status | Date |
|-----|-------|--------|------|
-| [0001](0001-use-postgresql.md) | Use PostgreSQL as Primary Database | Accepted | 2024-01-10 |
-| [0002](0002-caching-strategy.md) | Caching Strategy with Redis | Accepted | 2024-01-12 |
-| [0003](0003-mongodb-user-profiles.md) | MongoDB for User Profiles | Deprecated | 2023-06-15 |
-| [0020](0020-deprecate-mongodb.md) | Deprecate MongoDB | Accepted | 2024-01-15 |
+| 0001 | Use PostgreSQL as Primary Database | Accepted | 2024-01-10 |
+| 0002 | Caching Strategy with Redis | Accepted | 2024-01-12 |
+| 0003 | MongoDB for User Profiles | Deprecated | 2023-06-15 |
+| 0020 | Deprecate MongoDB | Accepted | 2024-01-15 |
## Creating a New ADR
diff --git a/web-app/public/skills/architecture-patterns/SKILL.md b/web-app/public/skills/architecture-patterns/SKILL.md
index 089a4965..20ff5e0a 100644
--- a/web-app/public/skills/architecture-patterns/SKILL.md
+++ b/web-app/public/skills/architecture-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: architecture-patterns
-description: Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
+description: "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ..."
+risk: unknown
+source: community
---
# Architecture Patterns
diff --git a/web-app/public/skills/architecture/SKILL.md b/web-app/public/skills/architecture/SKILL.md
index 3e4f6ad3..dad00c98 100644
--- a/web-app/public/skills/architecture/SKILL.md
+++ b/web-app/public/skills/architecture/SKILL.md
@@ -1,7 +1,9 @@
---
name: architecture
-description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
+description: "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Architecture Decision Framework
@@ -53,3 +55,6 @@ Before finalizing architecture:
- [ ] Simpler alternatives considered
- [ ] ADRs written for significant decisions
- [ ] Team expertise matches chosen patterns
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/arm-cortex-expert/SKILL.md b/web-app/public/skills/arm-cortex-expert/SKILL.md
index d1fab7ab..0512c5b9 100644
--- a/web-app/public/skills/arm-cortex-expert/SKILL.md
+++ b/web-app/public/skills/arm-cortex-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: arm-cortex-expert
-description: >
+description: ">"
Senior embedded software engineer specializing in firmware and driver
development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
Decades of experience writing reliable, optimized, and maintainable embedded
@@ -8,6 +8,8 @@ description: >
interrupt-driven I/O, and peripheral drivers.
metadata:
model: inherit
+risk: unknown
+source: community
---
# @arm-cortex-expert
diff --git a/web-app/public/skills/asana-automation/SKILL.md b/web-app/public/skills/asana-automation/SKILL.md
index 63e7b83a..dd0d4038 100644
--- a/web-app/public/skills/asana-automation/SKILL.md
+++ b/web-app/public/skills/asana-automation/SKILL.md
@@ -3,6 +3,8 @@ name: asana-automation
description: "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Asana Automation via Rube MCP
@@ -169,3 +171,6 @@ Automate Asana operations through Composio's Asana toolkit via Rube MCP.
| Workspace users | ASANA_GET_USERS_FOR_WORKSPACE | workspace_gid |
| Current user | ASANA_GET_CURRENT_USER | (none) |
| Parallel requests | ASANA_SUBMIT_PARALLEL_REQUESTS | actions |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/async-python-patterns/SKILL.md b/web-app/public/skills/async-python-patterns/SKILL.md
index 79c37c6b..59de49a0 100644
--- a/web-app/public/skills/async-python-patterns/SKILL.md
+++ b/web-app/public/skills/async-python-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: async-python-patterns
-description: Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
+description: "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-..."
+risk: unknown
+source: community
---
# Async Python Patterns
diff --git a/web-app/public/skills/attack-tree-construction/SKILL.md b/web-app/public/skills/attack-tree-construction/SKILL.md
index bfe23032..b937cfff 100644
--- a/web-app/public/skills/attack-tree-construction/SKILL.md
+++ b/web-app/public/skills/attack-tree-construction/SKILL.md
@@ -1,6 +1,8 @@
---
name: attack-tree-construction
-description: Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
+description: "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders."
+risk: unknown
+source: community
---
# Attack Tree Construction
diff --git a/web-app/public/skills/audio-transcriber/SKILL.md b/web-app/public/skills/audio-transcriber/SKILL.md
index d28cdcb5..adcbf012 100644
--- a/web-app/public/skills/audio-transcriber/SKILL.md
+++ b/web-app/public/skills/audio-transcriber/SKILL.md
@@ -9,6 +9,7 @@ platforms: [github-copilot-cli, claude-code, codex]
category: content
tags: [audio, transcription, whisper, meeting-minutes, speech-to-text]
risk: safe
+source: community
---
## Purpose
diff --git a/web-app/public/skills/auth-implementation-patterns/SKILL.md b/web-app/public/skills/auth-implementation-patterns/SKILL.md
index 8f1b32cf..4bfee17d 100644
--- a/web-app/public/skills/auth-implementation-patterns/SKILL.md
+++ b/web-app/public/skills/auth-implementation-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: auth-implementation-patterns
-description: Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
+description: "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A..."
+risk: unknown
+source: community
---
# Authentication & Authorization Implementation Patterns
diff --git a/web-app/public/skills/automate-whatsapp/SKILL.md b/web-app/public/skills/automate-whatsapp/SKILL.md
index 4dde7962..53de7bac 100644
--- a/web-app/public/skills/automate-whatsapp/SKILL.md
+++ b/web-app/public/skills/automate-whatsapp/SKILL.md
@@ -1,6 +1,6 @@
---
name: automate-whatsapp
-description: "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automating WhatsApp conversations and event handling."
+description: "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin..."
source: "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp"
risk: safe
---
@@ -211,17 +211,17 @@ node scripts/openapi-explore.mjs --spec platform op queryDatabaseRows
## References
Read before editing:
-- [references/graph-contract.md](references/graph-contract.md) - Graph schema, computed vs editable fields, lock_version
-- [references/node-types.md](references/node-types.md) - Node types and config shapes
-- [references/workflow-overview.md](references/workflow-overview.md) - Execution flow and states
+- references/graph-contract.md - Graph schema, computed vs editable fields, lock_version
+- references/node-types.md - Node types and config shapes
+- references/workflow-overview.md - Execution flow and states
Other references:
-- [references/execution-context.md](references/execution-context.md) - Context structure and variable substitution
-- [references/triggers.md](references/triggers.md) - Trigger types and setup
-- [references/app-integrations.md](references/app-integrations.md) - App integration and variable_definitions
-- [references/functions-reference.md](references/functions-reference.md) - Function management
-- [references/functions-payloads.md](references/functions-payloads.md) - Payload shapes for functions
-- [references/databases-reference.md](references/databases-reference.md) - Database operations
+- references/execution-context.md - Context structure and variable substitution
+- references/triggers.md - Trigger types and setup
+- references/app-integrations.md - App integration and variable_definitions
+- references/functions-reference.md - Function management
+- references/functions-payloads.md - Payload shapes for functions
+- references/databases-reference.md - Database operations
## Assets
diff --git a/web-app/public/skills/autonomous-agent-patterns/SKILL.md b/web-app/public/skills/autonomous-agent-patterns/SKILL.md
index ff5b79c3..e25824aa 100644
--- a/web-app/public/skills/autonomous-agent-patterns/SKILL.md
+++ b/web-app/public/skills/autonomous-agent-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: autonomous-agent-patterns
-description: "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants."
+description: "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ..."
+risk: unknown
+source: community
---
# 🕹️ Autonomous Agent Patterns
diff --git a/web-app/public/skills/autonomous-agents/SKILL.md b/web-app/public/skills/autonomous-agents/SKILL.md
index 77543a4e..dc02d90c 100644
--- a/web-app/public/skills/autonomous-agents/SKILL.md
+++ b/web-app/public/skills/autonomous-agents/SKILL.md
@@ -1,7 +1,8 @@
---
name: autonomous-agents
-description: "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability. This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability. Key insight: compounding error rates kill autonomous agents. A 95% success rate per step drops to 60% b"
+description: "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Autonomous Agents
@@ -66,3 +67,6 @@ Self-evaluation and iterative improvement
## Related Skills
Works well with: `agent-tool-builder`, `agent-memory-systems`, `multi-agent-orchestration`, `agent-evaluation`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/avalonia-layout-zafiro/SKILL.md b/web-app/public/skills/avalonia-layout-zafiro/SKILL.md
index e1848984..74b332f7 100644
--- a/web-app/public/skills/avalonia-layout-zafiro/SKILL.md
+++ b/web-app/public/skills/avalonia-layout-zafiro/SKILL.md
@@ -1,7 +1,9 @@
---
name: avalonia-layout-zafiro
-description: Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
+description: "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Avalonia Layout with Zafiro.Avalonia
@@ -57,3 +59,6 @@ For a real-world example, refer to the **Angor** project:
- Use `DynamicResource` for colors and brushes.
- Extract repeated layouts into generic components.
- Leverage `Zafiro.Avalonia` specific panels like `EdgePanel` for common UI patterns.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/avalonia-viewmodels-zafiro/SKILL.md b/web-app/public/skills/avalonia-viewmodels-zafiro/SKILL.md
index 1c6371cd..23d3c76d 100644
--- a/web-app/public/skills/avalonia-viewmodels-zafiro/SKILL.md
+++ b/web-app/public/skills/avalonia-viewmodels-zafiro/SKILL.md
@@ -1,6 +1,8 @@
---
name: avalonia-viewmodels-zafiro
-description: Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.
+description: "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI."
+risk: unknown
+source: community
---
# Avalonia ViewModels with Zafiro
@@ -27,3 +29,6 @@ This skill provides a set of best practices and patterns for creating ViewModels
For real-world implementations, refer to the **Angor** project:
- `CreateProjectFlowV2.cs`: Excellent example of complex Wizard building.
- `HomeViewModel.cs`: Simple section ViewModel using functional-reactive commands.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/avalonia-zafiro-development/SKILL.md b/web-app/public/skills/avalonia-zafiro-development/SKILL.md
index ff77591d..39a4c13d 100644
--- a/web-app/public/skills/avalonia-zafiro-development/SKILL.md
+++ b/web-app/public/skills/avalonia-zafiro-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: avalonia-zafiro-development
-description: Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
+description: "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit."
+risk: unknown
+source: community
---
# Avalonia Zafiro Development
@@ -27,3 +29,6 @@ This skill defines the mandatory conventions and behavioral rules for developing
1. **Search First**: Search the codebase for similar implementations or existing Zafiro helpers.
2. **Reusable Extensions**: If a helper is missing, propose a new reusable extension method instead of inlining complex logic.
3. **Reactive Pipelines**: Ensure DynamicData operators are used instead of plain Rx where applicable.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/aws-cost-cleanup/SKILL.md b/web-app/public/skills/aws-cost-cleanup/SKILL.md
new file mode 100644
index 00000000..b2072195
--- /dev/null
+++ b/web-app/public/skills/aws-cost-cleanup/SKILL.md
@@ -0,0 +1,309 @@
+---
+name: aws-cost-cleanup
+description: Automated cleanup of unused AWS resources to reduce costs
+risk: safe
+source: community
+---
+
+# AWS Cost Cleanup
+
+Automate the identification and removal of unused AWS resources to eliminate waste.
+
+## When to Use This Skill
+
+Use this skill when you need to automatically clean up unused AWS resources to reduce costs and eliminate waste.
+
+## Automated Cleanup Targets
+
+**Storage**
+- Unattached EBS volumes
+- Old EBS snapshots (>90 days)
+- Incomplete multipart S3 uploads
+- Old S3 versions in versioned buckets
+
+**Compute**
+- Stopped EC2 instances (>30 days)
+- Unused AMIs and associated snapshots
+- Unused Elastic IPs
+
+**Networking**
+- Unused Elastic Load Balancers
+- Unused NAT Gateways
+- Orphaned ENIs
+
+## Cleanup Scripts
+
+### Safe Cleanup (Dry-Run First)
+
+```bash
+#!/bin/bash
+# cleanup-unused-ebs.sh
+
+echo "Finding unattached EBS volumes..."
+VOLUMES=$(aws ec2 describe-volumes \
+ --filters Name=status,Values=available \
+ --query 'Volumes[*].VolumeId' \
+ --output text)
+
+for vol in $VOLUMES; do
+ echo "Would delete: $vol"
+ # Uncomment to actually delete:
+ # aws ec2 delete-volume --volume-id $vol
+done
+```
+
+```bash
+#!/bin/bash
+# cleanup-old-snapshots.sh
+
+CUTOFF_DATE=$(date -d '90 days ago' --iso-8601)
+
+aws ec2 describe-snapshots --owner-ids self \
+ --query "Snapshots[?StartTime<='$CUTOFF_DATE'].[SnapshotId,StartTime,VolumeSize]" \
+ --output text | while read snap_id start_time size; do
+
+ echo "Snapshot: $snap_id (Created: $start_time, Size: ${size}GB)"
+ # Uncomment to delete:
+ # aws ec2 delete-snapshot --snapshot-id $snap_id
+done
+```
+
+```bash
+#!/bin/bash
+# release-unused-eips.sh
+
+aws ec2 describe-addresses \
+ --query 'Addresses[?AssociationId==null].[AllocationId,PublicIp]' \
+ --output text | while read alloc_id public_ip; do
+
+ echo "Would release: $public_ip ($alloc_id)"
+ # Uncomment to release:
+ # aws ec2 release-address --allocation-id $alloc_id
+done
+```
+
+### S3 Lifecycle Automation
+
+```bash
+# Apply lifecycle policy to transition old objects to cheaper storage
+cat > lifecycle-policy.json <90 days)
+aws ec2 describe-snapshots \
+ --owner-ids self \
+ --query 'Snapshots[?StartTime<=`'$(date -d '90 days ago' --iso-8601)'`].[SnapshotId,StartTime,VolumeSize]' \
+ --output table
+```
+
+### Rightsizing Analysis
+```bash
+# List EC2 instances with their types
+aws ec2 describe-instances \
+ --query 'Reservations[*].Instances[*].[InstanceId,InstanceType,State.Name,Tags[?Key==`Name`].Value|[0]]' \
+ --output table
+
+# Get RDS instance utilization
+aws cloudwatch get-metric-statistics \
+ --namespace AWS/RDS \
+ --metric-name CPUUtilization \
+ --dimensions Name=DBInstanceIdentifier,Value=mydb \
+ --start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
+ --end-time $(date -u +%Y-%m-%dT%H:%M:%S) \
+ --period 86400 \
+ --statistics Average,Maximum
+```
+
+## Optimization Workflow
+
+1. **Baseline Assessment**
+ - Pull 3-6 months of cost data
+ - Identify top 5 spending services
+ - Calculate growth rate
+
+2. **Quick Wins**
+ - Delete unattached EBS volumes
+ - Release unused Elastic IPs
+ - Stop/terminate idle EC2 instances
+ - Delete old snapshots
+
+3. **Strategic Optimization**
+ - Analyze Reserved Instance coverage
+ - Review instance types vs. workload
+ - Implement S3 lifecycle policies
+ - Consider Spot instances for non-critical workloads
+
+4. **Ongoing Monitoring**
+ - Set up AWS Budgets with alerts
+ - Enable Cost Anomaly Detection
+ - Tag resources for cost allocation
+ - Monthly cost review meetings
+
+## Cost Optimization Checklist
+
+- [ ] Enable AWS Cost Explorer
+- [ ] Set up cost allocation tags
+- [ ] Create AWS Budget with alerts
+- [ ] Review and delete unused resources
+- [ ] Analyze Reserved Instance opportunities
+- [ ] Implement S3 Intelligent-Tiering
+- [ ] Review data transfer costs
+- [ ] Optimize Lambda memory allocation
+- [ ] Use CloudWatch Logs retention policies
+- [ ] Consider multi-region cost differences
+
+## Example Prompts
+
+**Analysis**
+- "Show me AWS costs for the last 3 months broken down by service"
+- "What are my top 10 most expensive resources?"
+- "Compare this month's spending to last month"
+
+**Optimization**
+- "Find all unattached EBS volumes and calculate savings"
+- "Identify EC2 instances with <5% CPU utilization"
+- "Suggest Reserved Instance purchases based on usage"
+- "Calculate savings from deleting snapshots older than 90 days"
+
+**Implementation**
+- "Create a script to delete unattached volumes"
+- "Set up a budget alert for $1000/month"
+- "Generate a cost optimization report for leadership"
+
+## Best Practices
+
+- Always test in non-production first
+- Verify resources are truly unused before deletion
+- Document all cost optimization actions
+- Calculate ROI for optimization efforts
+- Automate recurring optimization tasks
+- Use AWS Trusted Advisor recommendations
+- Enable AWS Cost Anomaly Detection
+
+## Integration with Kiro CLI
+
+This skill works seamlessly with Kiro CLI's AWS integration:
+
+```bash
+# Use Kiro to analyze costs
+kiro-cli chat "Use aws-cost-optimizer to analyze my spending"
+
+# Generate optimization report
+kiro-cli chat "Create a cost optimization plan using aws-cost-optimizer"
+```
+
+## Safety Notes
+
+- **Risk Level: Low** - Read-only analysis is safe
+- **Deletion Actions: Medium Risk** - Always verify before deleting resources
+- **Production Changes: High Risk** - Test rightsizing in dev/staging first
+- Maintain backups before any deletion
+- Use `--dry-run` flag when available
+
+## Additional Resources
+
+- [AWS Cost Optimization Best Practices](https://aws.amazon.com/pricing/cost-optimization/)
+- [AWS Well-Architected Framework - Cost Optimization](https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/welcome.html)
+- [AWS Cost Explorer API](https://docs.aws.amazon.com/cost-management/latest/APIReference/Welcome.html)
diff --git a/web-app/public/skills/aws-penetration-testing/SKILL.md b/web-app/public/skills/aws-penetration-testing/SKILL.md
index 644bdc1d..a549d0a5 100644
--- a/web-app/public/skills/aws-penetration-testing/SKILL.md
+++ b/web-app/public/skills/aws-penetration-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: AWS Penetration Testing
-description: This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing", "metadata SSRF", "Lambda exploitation", or needs guidance on Amazon Web Services security assessment.
+name: aws-penetration-testing
+description: "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# AWS Penetration Testing
@@ -403,3 +405,6 @@ aws sts get-caller-identity
## Additional Resources
For advanced techniques including Lambda/API Gateway exploitation, Secrets Manager & KMS, Container security (ECS/EKS/ECR), RDS/DynamoDB exploitation, VPC lateral movement, and security checklists, see [references/advanced-aws-pentesting.md](references/advanced-aws-pentesting.md).
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/aws-serverless/SKILL.md b/web-app/public/skills/aws-serverless/SKILL.md
index 237f34c6..8ae988a5 100644
--- a/web-app/public/skills/aws-serverless/SKILL.md
+++ b/web-app/public/skills/aws-serverless/SKILL.md
@@ -1,7 +1,8 @@
---
name: aws-serverless
-description: "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization."
+description: "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# AWS Serverless
@@ -321,3 +322,6 @@ Blocking DNS lookups or connections worsen cold starts.
| Issue | medium | ## Tell Lambda not to wait for event loop |
| Issue | medium | ## For large file uploads |
| Issue | high | ## Use different buckets/prefixes |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azd-deployment/SKILL.md b/web-app/public/skills/azd-deployment/SKILL.md
index 88ead12f..9e008a4d 100644
--- a/web-app/public/skills/azd-deployment/SKILL.md
+++ b/web-app/public/skills/azd-deployment/SKILL.md
@@ -1,6 +1,8 @@
---
name: azd-deployment
-description: Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Container Apps, configuring remote builds with ACR, implementing idempotent deployments, managing environment variables across local/.azure/Bicep, or troubleshooting azd up failures. Triggers on requests for azd configuration, Container Apps deployment, multi-service deployments, and infrastructure-as-code with Bicep.
+description: "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont..."
+risk: unknown
+source: community
---
# Azure Developer CLI (azd) Container Apps Deployment
@@ -283,9 +285,9 @@ az containerapp logs show -n -g --follow # Stream logs
## Reference Files
-- **Bicep patterns**: See [references/bicep-patterns.md](references/bicep-patterns.md) for Container Apps modules
-- **Troubleshooting**: See [references/troubleshooting.md](references/troubleshooting.md) for common issues
-- **azure.yaml schema**: See [references/azure-yaml-schema.md](references/azure-yaml-schema.md) for full options
+- **Bicep patterns**: See references/bicep-patterns.md for Container Apps modules
+- **Troubleshooting**: See references/troubleshooting.md for common issues
+- **azure.yaml schema**: See references/azure-yaml-schema.md for full options
## Critical Reminders
@@ -294,3 +296,6 @@ az containerapp logs show -n -g --follow # Stream logs
3. **Use `azd env set` for secrets** - Not main.parameters.json defaults
4. **Service tags (`azd-service-name`)** - Required for azd to find Container Apps
5. **`|| true` in hooks** - Prevent RBAC "already exists" errors from failing deploy
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md b/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
index 90075e1b..3979d282 100644
--- a/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-agents-persistent-dotnet
-description: |
+description: "|"
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
package: Azure.AI.Agents.Persistent
+risk: unknown
+source: community
---
# Azure.AI.Agents.Persistent (.NET)
@@ -347,3 +349,6 @@ catch (RequestFailedException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.ai.agents.persistent |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.Agents.Persistent |
| Samples | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.Agents.Persistent/samples |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md b/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
index 1d36b02c..9c34fc37 100644
--- a/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-agents-persistent-java
-description: |
+description: "|"
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.
Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".
package: com.azure:azure-ai-agents-persistent
+risk: unknown
+source: community
---
# Azure AI Agents Persistent SDK for Java
@@ -135,3 +137,6 @@ try {
|----------|-----|
| Maven Package | https://central.sonatype.com/artifact/com.azure/azure-ai-agents-persistent |
| GitHub Source | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/azure-ai-agents-persistent |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-anomalydetector-java/SKILL.md b/web-app/public/skills/azure-ai-anomalydetector-java/SKILL.md
index 8943ddad..0e4e07ce 100644
--- a/web-app/public/skills/azure-ai-anomalydetector-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-anomalydetector-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-anomalydetector-java
-description: Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.
+description: "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring."
package: com.azure:azure-ai-anomalydetector
+risk: unknown
+source: community
---
# Azure AI Anomaly Detector SDK for Java
@@ -254,3 +256,6 @@ AZURE_ANOMALY_DETECTOR_API_KEY=
- "streaming anomaly detection"
- "change point detection"
- "Azure AI Anomaly Detector"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-contentsafety-java/SKILL.md b/web-app/public/skills/azure-ai-contentsafety-java/SKILL.md
index 20ea06d1..25ad68db 100644
--- a/web-app/public/skills/azure-ai-contentsafety-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentsafety-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-contentsafety-java
-description: Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual content, and self-harm.
+description: "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten..."
package: com.azure:azure-ai-contentsafety
+risk: unknown
+source: community
---
# Azure AI Content Safety SDK for Java
@@ -280,3 +282,6 @@ CONTENT_SAFETY_KEY=
- "blocklist management"
- "hate speech detection"
- "harmful content filter"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md b/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
index 86171dc0..672acfbc 100644
--- a/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-contentsafety-py
-description: |
+description: "|"
Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.
Triggers: "azure-ai-contentsafety", "ContentSafetyClient", "content moderation", "harmful content", "text analysis", "image analysis".
package: azure-ai-contentsafety
+risk: unknown
+source: community
---
# Azure AI Content Safety SDK for Python
@@ -212,3 +214,6 @@ request = AnalyzeTextOptions(
5. **Log analysis results** for audit and improvement
6. **Consider 8-severity mode** for finer-grained control
7. **Pre-moderate AI outputs** before showing to users
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-contentsafety-ts/SKILL.md b/web-app/public/skills/azure-ai-contentsafety-ts/SKILL.md
index 89b64c57..d7bb60e2 100644
--- a/web-app/public/skills/azure-ai-contentsafety-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentsafety-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-contentsafety-ts
-description: Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual content, or self-harm, or managing custom blocklists.
+description: "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten..."
package: "@azure-rest/ai-content-safety"
+risk: unknown
+source: community
---
# Azure AI Content Safety REST SDK for TypeScript
@@ -298,3 +300,6 @@ import ContentSafetyClient, {
3. **Use blocklists for domain-specific terms** - Supplement AI detection with custom rules
4. **Log moderation decisions** - Keep audit trail for compliance
5. **Handle edge cases** - Empty text, very long text, unsupported image formats
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md b/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
index d3cc8232..d6936e74 100644
--- a/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-contentunderstanding-py
-description: |
+description: "|"
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
Triggers: "azure-ai-contentunderstanding", "ContentUnderstandingClient", "multimodal analysis", "document extraction", "video analysis", "audio transcription".
package: azure-ai-contentunderstanding
+risk: unknown
+source: community
---
# Azure AI Content Understanding SDK for Python
@@ -271,3 +273,6 @@ from azure.ai.contentunderstanding.models import (
5. **Use async client** for high-throughput scenarios with `azure.identity.aio` credentials
6. **Handle long-running operations** — video/audio analysis can take minutes
7. **Use URL sources** when possible to avoid upload overhead
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md b/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
index f68da659..bf04b40f 100644
--- a/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-document-intelligence-dotnet
-description: |
+description: "|"
Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: "Document Intelligence", "DocumentIntelligenceClient", "form recognizer", "invoice extraction", "receipt OCR", "document analysis .NET".
package: Azure.AI.DocumentIntelligence
+risk: unknown
+source: community
---
# Azure.AI.DocumentIntelligence (.NET)
@@ -335,3 +337,6 @@ catch (RequestFailedException ex)
| GitHub Samples | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/documentintelligence/Azure.AI.DocumentIntelligence/samples |
| Document Intelligence Studio | https://documentintelligence.ai.azure.com/ |
| Prebuilt Models | https://aka.ms/azsdk/formrecognizer/models |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-document-intelligence-ts/SKILL.md b/web-app/public/skills/azure-ai-document-intelligence-ts/SKILL.md
index 91d3e54c..dfcb50b5 100644
--- a/web-app/public/skills/azure-ai-document-intelligence-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-document-intelligence-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-document-intelligence-ts
-description: Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building custom document models.
+description: "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu..."
package: "@azure-rest/ai-document-intelligence"
+risk: unknown
+source: community
---
# Azure Document Intelligence REST SDK for TypeScript
@@ -321,3 +323,6 @@ import DocumentIntelligence, {
4. **Handle confidence scores** - Fields have confidence values, set thresholds for your use case
5. **Use pagination** - Use `paginate()` helper for listing models
6. **Prefer neural mode** - For custom models, neural handles more variation than template
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-formrecognizer-java/SKILL.md b/web-app/public/skills/azure-ai-formrecognizer-java/SKILL.md
index f63e954e..ce085d26 100644
--- a/web-app/public/skills/azure-ai-formrecognizer-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-formrecognizer-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-formrecognizer-java
-description: Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or building custom document models.
+description: "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi..."
package: com.azure:azure-ai-formrecognizer
+risk: unknown
+source: community
---
# Azure Document Intelligence (Form Recognizer) SDK for Java
@@ -339,3 +341,6 @@ FORM_RECOGNIZER_KEY=
- "analyze invoice receipt"
- "custom document model"
- "document classification"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-ml-py/SKILL.md b/web-app/public/skills/azure-ai-ml-py/SKILL.md
index 30733cb8..d3edddb1 100644
--- a/web-app/public/skills/azure-ai-ml-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-ml-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-ml-py
-description: |
+description: "|"
Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.
Triggers: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
package: azure-ai-ml
+risk: unknown
+source: community
---
# Azure Machine Learning SDK v2 for Python
@@ -269,3 +271,6 @@ print(f"Default: {default_ds.name}")
5. **Register models** after successful training jobs
6. **Use pipelines** for multi-step workflows
7. **Tag resources** for organization and cost tracking
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md b/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
index 989984b1..97437f44 100644
--- a/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-openai-dotnet
-description: |
+description: "|"
Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: "Azure OpenAI", "AzureOpenAIClient", "ChatClient", "chat completions .NET", "GPT-4", "embeddings", "DALL-E", "Whisper", "OpenAI .NET".
package: Azure.AI.OpenAI
+risk: unknown
+source: community
---
# Azure.AI.OpenAI (.NET)
@@ -453,3 +455,6 @@ catch (RequestFailedException ex)
| Migration Guide (1.0→2.0) | https://learn.microsoft.com/azure/ai-services/openai/how-to/dotnet-migration |
| Quickstart | https://learn.microsoft.com/azure/ai-services/openai/quickstart |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/openai/Azure.AI.OpenAI |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md b/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
index db41a665..e9199ef3 100644
--- a/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-projects-dotnet
-description: |
+description: "|"
Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents", "evaluations", "datasets", "connections", "deployments .NET".
package: Azure.AI.Projects
+risk: unknown
+source: community
---
# Azure.AI.Projects (.NET)
@@ -346,3 +348,6 @@ catch (RequestFailedException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.ai.projects |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.Projects |
| Samples | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.Projects/samples |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-projects-java/SKILL.md b/web-app/public/skills/azure-ai-projects-java/SKILL.md
index 66993a90..1e4b9167 100644
--- a/web-app/public/skills/azure-ai-projects-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-projects-java
-description: |
+description: "|"
Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.
Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".
package: com.azure:azure-ai-projects
+risk: unknown
+source: community
---
# Azure AI Projects SDK for Java
@@ -150,3 +152,6 @@ try {
| API Reference | https://learn.microsoft.com/rest/api/aifoundry/aiprojects/ |
| GitHub Source | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/azure-ai-projects |
| Samples | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/azure-ai-projects/src/samples |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-projects-py/SKILL.md b/web-app/public/skills/azure-ai-projects-py/SKILL.md
index 8965b175..ec5d5286 100644
--- a/web-app/public/skills/azure-ai-projects-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-py/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-projects-py
-description: Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evaluations, managing connections/deployments/datasets/indexes, or using OpenAI-compatible clients. This is the high-level Foundry SDK - for low-level agent operations, use azure-ai-agents-python skill.
+description: "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua..."
package: azure-ai-projects
+risk: unknown
+source: community
---
# Azure AI Projects Python SDK (Foundry SDK)
@@ -122,7 +124,7 @@ agent_version = client.agents.create_version(
)
```
-See [references/agents.md](references/agents.md) for detailed agent patterns.
+See references/agents.md for detailed agent patterns.
## Tools Overview
@@ -138,7 +140,7 @@ See [references/agents.md](references/agents.md) for detailed agent patterns.
| Memory Search | `MemorySearchTool` | Search agent memory stores |
| SharePoint | `SharepointGroundingTool` | Search SharePoint content |
-See [references/tools.md](references/tools.md) for all tool patterns.
+See references/tools.md for all tool patterns.
## Thread and Message Flow
@@ -179,7 +181,7 @@ for conn in connections:
connection = client.connections.get(connection_name="my-search-connection")
```
-See [references/connections.md](references/connections.md) for connection patterns.
+See references/connections.md for connection patterns.
## Deployments
@@ -190,7 +192,7 @@ for deployment in deployments:
print(f"{deployment.name}: {deployment.model}")
```
-See [references/deployments.md](references/deployments.md) for deployment patterns.
+See references/deployments.md for deployment patterns.
## Datasets and Indexes
@@ -202,7 +204,7 @@ datasets = client.datasets.list()
indexes = client.indexes.list()
```
-See [references/datasets-indexes.md](references/datasets-indexes.md) for data operations.
+See references/datasets-indexes.md for data operations.
## Evaluation
@@ -225,7 +227,7 @@ eval_run = openai_client.evals.runs.create(
)
```
-See [references/evaluation.md](references/evaluation.md) for evaluation patterns.
+See references/evaluation.md for evaluation patterns.
## Async Client
@@ -240,7 +242,7 @@ async with AIProjectClient(
# ... async operations
```
-See [references/async-patterns.md](references/async-patterns.md) for async patterns.
+See references/async-patterns.md for async patterns.
## Memory Stores
@@ -282,14 +284,17 @@ agent = client.agents.create_agent(
## Reference Files
-- [references/agents.md](references/agents.md): Agent operations with PromptAgentDefinition
-- [references/tools.md](references/tools.md): All agent tools with examples
-- [references/evaluation.md](references/evaluation.md): Evaluation operations overview
-- [references/built-in-evaluators.md](references/built-in-evaluators.md): Complete built-in evaluator reference
-- [references/custom-evaluators.md](references/custom-evaluators.md): Code and prompt-based evaluator patterns
-- [references/connections.md](references/connections.md): Connection operations
-- [references/deployments.md](references/deployments.md): Deployment enumeration
-- [references/datasets-indexes.md](references/datasets-indexes.md): Dataset and index operations
-- [references/async-patterns.md](references/async-patterns.md): Async client usage
-- [references/api-reference.md](references/api-reference.md): Complete API reference for all 373 SDK exports (v2.0.0b4)
-- [scripts/run_batch_evaluation.py](scripts/run_batch_evaluation.py): CLI tool for batch evaluations
+- references/agents.md: Agent operations with PromptAgentDefinition
+- references/tools.md: All agent tools with examples
+- references/evaluation.md: Evaluation operations overview
+- references/built-in-evaluators.md: Complete built-in evaluator reference
+- references/custom-evaluators.md: Code and prompt-based evaluator patterns
+- references/connections.md: Connection operations
+- references/deployments.md: Deployment enumeration
+- references/datasets-indexes.md: Dataset and index operations
+- references/async-patterns.md: Async client usage
+- references/api-reference.md: Complete API reference for all 373 SDK exports (v2.0.0b4)
+- scripts/run_batch_evaluation.py: CLI tool for batch evaluations
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-projects-ts/SKILL.md b/web-app/public/skills/azure-ai-projects-ts/SKILL.md
index 8c9fbc1b..5c9e32dd 100644
--- a/web-app/public/skills/azure-ai-projects-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-projects-ts
-description: Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluations, or getting OpenAI clients.
+description: "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation..."
package: "@azure/ai-projects"
+risk: unknown
+source: community
---
# Azure AI Projects SDK for TypeScript
@@ -287,3 +289,6 @@ import {
3. **Clean up resources** - Delete agents, conversations when done
4. **Use connections** - Get credentials from project connections, don't hardcode
5. **Filter deployments** - Use `modelPublisher` filter to find specific models
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md b/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
index d9fb573e..ae54fb5c 100644
--- a/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-textanalytics-py
-description: |
+description: "|"
Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.
Triggers: "text analytics", "sentiment analysis", "entity recognition", "key phrase", "PII detection", "TextAnalyticsClient".
package: azure-ai-textanalytics
+risk: unknown
+source: community
---
# Azure AI Text Analytics SDK for Python
@@ -225,3 +227,6 @@ async def analyze():
4. **Handle document errors** — results list may contain errors for some docs
5. **Specify language** when known to improve accuracy
6. **Use context manager** or close client explicitly
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-transcription-py/SKILL.md b/web-app/public/skills/azure-ai-transcription-py/SKILL.md
index 8b5d1ec7..216c20b0 100644
--- a/web-app/public/skills/azure-ai-transcription-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-transcription-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-transcription-py
-description: |
+description: "|"
Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.
Triggers: "transcription", "speech to text", "Azure AI Transcription", "TranscriptionClient".
package: azure-ai-transcription
+risk: unknown
+source: community
---
# Azure AI Transcription SDK for Python
@@ -67,3 +69,6 @@ for event in stream:
4. **Specify language** to improve recognition accuracy
5. **Handle streaming backpressure** for real-time transcription
6. **Close transcription sessions** when complete
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-translation-document-py/SKILL.md b/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
index 106bbe71..c7e1ee0f 100644
--- a/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-translation-document-py
-description: |
+description: "|"
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
package: azure-ai-translation-document
+risk: unknown
+source: community
---
# Azure AI Document Translation SDK for Python
@@ -247,3 +249,6 @@ async def translate_documents():
5. **Separate target containers** for each language
6. **Use async client** for multiple concurrent jobs
7. **Check supported formats** before submitting documents
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-translation-text-py/SKILL.md b/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
index 31ecd7a5..7bf2779b 100644
--- a/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-translation-text-py
-description: |
+description: "|"
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.
Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
package: azure-ai-translation-text
+risk: unknown
+source: community
---
# Azure AI Text Translation SDK for Python
@@ -272,3 +274,6 @@ async def translate_text():
5. **Handle profanity** appropriately for your application
6. **Use html text_type** when translating HTML content
7. **Include alignment** for applications needing word mapping
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-translation-ts/SKILL.md b/web-app/public/skills/azure-ai-translation-ts/SKILL.md
index e232051a..11e41d92 100644
--- a/web-app/public/skills/azure-ai-translation-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-translation-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-translation-ts
-description: Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliteration, language detection, or batch document translation.
+description: "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter..."
package: "@azure-rest/ai-translation-text, @azure-rest/ai-translation-document"
+risk: unknown
+source: community
---
# Azure Translation SDKs for TypeScript
@@ -284,3 +286,6 @@ import type {
3. **Use SAS tokens** - For document translation, use time-limited SAS URLs
4. **Handle errors** - Always check `isUnexpected(response)` before accessing body
5. **Regional endpoints** - Use regional endpoints for lower latency
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-vision-imageanalysis-java/SKILL.md b/web-app/public/skills/azure-ai-vision-imageanalysis-java/SKILL.md
index e3ff19a2..4efcc5db 100644
--- a/web-app/public/skills/azure-ai-vision-imageanalysis-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-vision-imageanalysis-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-vision-imageanalysis-java
-description: Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.
+description: "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping."
package: com.azure:azure-ai-vision-imageanalysis
+risk: unknown
+source: community
---
# Azure AI Vision Image Analysis SDK for Java
@@ -287,3 +289,6 @@ Caption and Dense Captions require GPU-supported regions. Check [supported regio
- "object detection image"
- "smart crop thumbnail"
- "detect people image"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md b/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
index 69dbc9ac..572781cb 100644
--- a/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-vision-imageanalysis-py
-description: |
+description: "|"
Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.
Triggers: "image analysis", "computer vision", "OCR", "object detection", "ImageAnalysisClient", "image caption".
package: azure-ai-vision-imageanalysis
+risk: unknown
+source: community
---
# Azure AI Vision Image Analysis SDK for Python
@@ -258,3 +260,6 @@ except HttpResponseError as e:
5. **Specify language** for localized captions
6. **Use smart_crops_aspect_ratios** matching your thumbnail requirements
7. **Cache results** when analyzing the same image multiple times
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md b/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
index 19324cd8..e52481a5 100644
--- a/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-voicelive-dotnet
-description: |
+description: "|"
Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant .NET", "bidirectional audio", "speech-to-speech".
package: Azure.AI.VoiceLive
+risk: unknown
+source: community
---
# Azure.AI.VoiceLive (.NET)
@@ -263,3 +265,6 @@ if (serverEvent is SessionUpdateError error)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.ai.voicelive |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.VoiceLive |
| Quickstart | https://learn.microsoft.com/azure/ai-services/speech-service/voice-live-quickstart |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-voicelive-java/SKILL.md b/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
index aefa513d..9c3e1306 100644
--- a/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-ai-voicelive-java
-description: |
+description: "|"
Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.
Triggers: "VoiceLiveClient java", "voice assistant java", "real-time voice java", "audio streaming java", "voice activity detection java".
package: com.azure:azure-ai-voicelive
+risk: unknown
+source: community
---
# Azure AI VoiceLive SDK for Java
@@ -223,3 +225,6 @@ session.receiveEvents()
|----------|-----|
| GitHub Source | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/azure-ai-voicelive |
| Samples | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/ai/azure-ai-voicelive/src/samples |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-voicelive-py/SKILL.md b/web-app/public/skills/azure-ai-voicelive-py/SKILL.md
index 0b22c55e..304da306 100644
--- a/web-app/public/skills/azure-ai-voicelive-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-py/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-ai-voicelive-py
-description: Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with Azure AI, including voice assistants, voice-enabled chatbots, real-time speech-to-speech translation, voice-driven avatars, or any WebSocket-based audio streaming with AI models. Supports Server VAD (Voice Activity Detection), turn-based conversation, function calling, MCP tools, avatar integration, and transcription.
+description: "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with..."
package: azure-ai-voicelive
+risk: unknown
+source: community
---
# Azure AI Voice Live SDK
@@ -304,6 +306,9 @@ except ConnectionError as e:
## References
-- **Detailed API Reference**: See [references/api-reference.md](references/api-reference.md)
-- **Complete Examples**: See [references/examples.md](references/examples.md)
-- **All Models & Types**: See [references/models.md](references/models.md)
+- **Detailed API Reference**: See references/api-reference.md
+- **Complete Examples**: See references/examples.md
+- **All Models & Types**: See references/models.md
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md b/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
index 8180affe..5e13f368 100644
--- a/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-ai-voicelive-ts
-description: |
+description: "|"
Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant TypeScript", "bidirectional audio", "speech-to-speech JavaScript".
package: "@azure/ai-voicelive"
+risk: unknown
+source: community
---
# @azure/ai-voicelive (JavaScript/TypeScript)
@@ -463,3 +465,6 @@ const audioContext = new AudioContext({ sampleRate: 24000 });
| GitHub Source | https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/ai/ai-voicelive |
| Samples | https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/ai/ai-voicelive/samples |
| API Reference | https://learn.microsoft.com/javascript/api/@azure/ai-voicelive |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-appconfiguration-java/SKILL.md b/web-app/public/skills/azure-appconfiguration-java/SKILL.md
index 087d8c16..e4560c24 100644
--- a/web-app/public/skills/azure-appconfiguration-java/SKILL.md
+++ b/web-app/public/skills/azure-appconfiguration-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-appconfiguration-java
-description: |
+description: "|"
Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.
Triggers: "ConfigurationClient java", "app configuration java", "feature flag java", "configuration setting java", "azure config java".
package: com.azure:azure-data-appconfiguration
+risk: unknown
+source: community
---
# Azure App Configuration SDK for Java
@@ -468,3 +470,6 @@ try {
| Product Docs | https://learn.microsoft.com/azure/azure-app-configuration |
| Samples | https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/appconfiguration/azure-data-appconfiguration/src/samples |
| Troubleshooting | https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/appconfiguration/azure-data-appconfiguration/TROUBLESHOOTING.md |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-appconfiguration-py/SKILL.md b/web-app/public/skills/azure-appconfiguration-py/SKILL.md
index 414194d3..c1da4e42 100644
--- a/web-app/public/skills/azure-appconfiguration-py/SKILL.md
+++ b/web-app/public/skills/azure-appconfiguration-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-appconfiguration-py
-description: |
+description: "|"
Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.
Triggers: "azure-appconfiguration", "AzureAppConfigurationClient", "feature flags", "configuration", "key-value settings".
package: azure-appconfiguration
+risk: unknown
+source: community
---
# Azure App Configuration SDK for Python
@@ -247,3 +249,6 @@ async def main():
5. **Use Entra ID** instead of connection strings in production
6. **Refresh settings periodically** in long-running applications
7. **Use feature flags** for gradual rollouts and A/B testing
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-appconfiguration-ts/SKILL.md b/web-app/public/skills/azure-appconfiguration-ts/SKILL.md
index 2a388473..3513b415 100644
--- a/web-app/public/skills/azure-appconfiguration-ts/SKILL.md
+++ b/web-app/public/skills/azure-appconfiguration-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-appconfiguration-ts
-description: Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, or centralized configuration management.
+description: "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o..."
package: "@azure/app-configuration"
+risk: unknown
+source: community
---
# Azure App Configuration SDK for TypeScript
@@ -347,3 +349,6 @@ import {
5. **Use snapshots** - For immutable release configurations
6. **Sentinel pattern** - Use a sentinel key to trigger full refresh
7. **RBAC roles** - `App Configuration Data Reader` for read-only access
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-communication-callautomation-java/SKILL.md b/web-app/public/skills/azure-communication-callautomation-java/SKILL.md
index 29eb1218..75337aaf 100644
--- a/web-app/public/skills/azure-communication-callautomation-java/SKILL.md
+++ b/web-app/public/skills/azure-communication-callautomation-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-communication-callautomation-java
-description: Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-powered call flows.
+description: "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-..."
package: com.azure:azure-communication-callautomation
+risk: unknown
+source: community
---
# Azure Communication Call Automation (Java)
@@ -252,3 +254,6 @@ CALLBACK_BASE_URL=https://your-app.com/api/callbacks
- "text to speech call", "speech recognition call"
- "answer incoming call", "transfer call Java"
- "Azure Communication Services call automation"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-communication-callingserver-java/SKILL.md b/web-app/public/skills/azure-communication-callingserver-java/SKILL.md
index bf764711..37b3099b 100644
--- a/web-app/public/skills/azure-communication-callingserver-java/SKILL.md
+++ b/web-app/public/skills/azure-communication-callingserver-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-communication-callingserver-java
-description: Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining legacy code.
+description: "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le..."
package: com.azure:azure-communication-callingserver
+risk: unknown
+source: community
---
# Azure Communication CallingServer (Java) - DEPRECATED
@@ -89,3 +91,6 @@ See the `azure-communication-callautomation-java` skill for:
- "callingserver legacy", "deprecated calling SDK"
- "migrate callingserver to callautomation"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-communication-chat-java/SKILL.md b/web-app/public/skills/azure-communication-chat-java/SKILL.md
index a48efd1e..590730d1 100644
--- a/web-app/public/skills/azure-communication-chat-java/SKILL.md
+++ b/web-app/public/skills/azure-communication-chat-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-communication-chat-java
-description: Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
+description: "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha..."
package: com.azure:azure-communication-chat
+risk: unknown
+source: community
---
# Azure Communication Chat (Java)
@@ -308,3 +310,6 @@ AZURE_COMMUNICATION_USER_TOKEN=
- "chat thread", "chat participants", "chat messages"
- "read receipts", "typing notifications"
- "Azure Communication Services chat"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-communication-common-java/SKILL.md b/web-app/public/skills/azure-communication-common-java/SKILL.md
index 776d4b72..93f5a93c 100644
--- a/web-app/public/skills/azure-communication-common-java/SKILL.md
+++ b/web-app/public/skills/azure-communication-common-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-communication-common-java
-description: Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
+description: "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services."
package: com.azure:azure-communication-common
+risk: unknown
+source: community
---
# Azure Communication Common (Java)
@@ -302,3 +304,6 @@ private String refreshToken() {
- "user access token", "token refresh"
- "CommunicationUserIdentifier", "PhoneNumberIdentifier"
- "Azure Communication Services authentication"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-communication-sms-java/SKILL.md b/web-app/public/skills/azure-communication-sms-java/SKILL.md
index 9b9507b0..86072fa2 100644
--- a/web-app/public/skills/azure-communication-sms-java/SKILL.md
+++ b/web-app/public/skills/azure-communication-sms-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-communication-sms-java
-description: Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.
+description: "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports."
package: com.azure:azure-communication-sms
+risk: unknown
+source: community
---
# Azure Communication SMS (Java)
@@ -272,3 +274,6 @@ SMS_FROM_NUMBER=+14255550100
- "send SMS Java", "text message Java"
- "SMS notification", "OTP SMS", "bulk SMS"
- "delivery report SMS", "Azure Communication Services SMS"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-compute-batch-java/SKILL.md b/web-app/public/skills/azure-compute-batch-java/SKILL.md
index 5e5aa048..993554e9 100644
--- a/web-app/public/skills/azure-compute-batch-java/SKILL.md
+++ b/web-app/public/skills/azure-compute-batch-java/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-compute-batch-java
-description: |
+description: "|"
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
Triggers: "BatchClient java", "azure batch java", "batch pool java", "batch job java", "HPC java", "parallel computing java".
+risk: unknown
+source: community
---
# Azure Batch SDK for Java
@@ -377,3 +379,6 @@ try {
| Product Docs | https://learn.microsoft.com/azure/batch/ |
| REST API | https://learn.microsoft.com/rest/api/batchservice/ |
| Samples | https://github.com/azure/azure-batch-samples |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-containerregistry-py/SKILL.md b/web-app/public/skills/azure-containerregistry-py/SKILL.md
index 5d830ea9..76f76a65 100644
--- a/web-app/public/skills/azure-containerregistry-py/SKILL.md
+++ b/web-app/public/skills/azure-containerregistry-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-containerregistry-py
-description: |
+description: "|"
Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".
package: azure-containerregistry
+risk: unknown
+source: community
---
# Azure Container Registry SDK for Python
@@ -250,3 +252,6 @@ for manifest in client.list_manifest_properties("my-image"):
5. **Use async client** for high-throughput operations
6. **Order by last_updated** to find recent/old images
7. **Check manifest.tags** before deleting to avoid removing tagged images
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-cosmos-db-py/SKILL.md b/web-app/public/skills/azure-cosmos-db-py/SKILL.md
index 33b4307c..76315cfa 100644
--- a/web-app/public/skills/azure-cosmos-db-py/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-db-py/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-cosmos-db-py
-description: Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers on phrases like "Cosmos DB", "NoSQL database", "document store", "add persistence", "database service layer", or "Python Cosmos SDK".
+description: "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service..."
package: azure-cosmos
+risk: unknown
+source: community
---
# Cosmos DB Service Implementation
@@ -108,7 +110,7 @@ async def get_container():
return _cosmos_container
```
-**Full implementation**: See [references/client-setup.md](references/client-setup.md)
+**Full implementation**: See references/client-setup.md
### 2. Pydantic Model Hierarchy
@@ -148,7 +150,7 @@ class ProjectService:
return self._doc_to_model(doc)
```
-**Full patterns**: See [references/service-layer.md](references/service-layer.md)
+**Full patterns**: See references/service-layer.md
## Core Principles
@@ -191,25 +193,25 @@ async def test_get_project_by_id_returns_project(mock_cosmos_container):
assert result.name == "Test"
```
-**Full testing guide**: See [references/testing.md](references/testing.md)
+**Full testing guide**: See references/testing.md
## Reference Files
| File | When to Read |
|------|--------------|
-| [references/client-setup.md](references/client-setup.md) | Setting up Cosmos client with dual auth, SSL config, singleton pattern |
-| [references/service-layer.md](references/service-layer.md) | Implementing full service class with CRUD, conversions, graceful degradation |
-| [references/testing.md](references/testing.md) | Writing pytest tests, mocking Cosmos, integration test setup |
-| [references/partitioning.md](references/partitioning.md) | Choosing partition keys, cross-partition queries, move operations |
-| [references/error-handling.md](references/error-handling.md) | Handling CosmosResourceNotFoundError, logging, HTTP error mapping |
+| references/client-setup.md | Setting up Cosmos client with dual auth, SSL config, singleton pattern |
+| references/service-layer.md | Implementing full service class with CRUD, conversions, graceful degradation |
+| references/testing.md | Writing pytest tests, mocking Cosmos, integration test setup |
+| references/partitioning.md | Choosing partition keys, cross-partition queries, move operations |
+| references/error-handling.md | Handling CosmosResourceNotFoundError, logging, HTTP error mapping |
## Template Files
| File | Purpose |
|------|---------|
-| [assets/cosmos_client_template.py](assets/cosmos_client_template.py) | Ready-to-use client module |
-| [assets/service_template.py](assets/service_template.py) | Service class skeleton |
-| [assets/conftest_template.py](assets/conftest_template.py) | pytest fixtures for Cosmos mocking |
+| assets/cosmos_client_template.py | Ready-to-use client module |
+| assets/service_template.py | Service class skeleton |
+| assets/conftest_template.py | pytest fixtures for Cosmos mocking |
## Quality Attributes (NFRs)
@@ -237,3 +239,6 @@ async def test_get_project_by_id_returns_project(mock_cosmos_container):
- Partition key queries avoid cross-partition scans
- Async wrapping prevents blocking FastAPI event loop
- Minimal document conversion overhead
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-cosmos-java/SKILL.md b/web-app/public/skills/azure-cosmos-java/SKILL.md
index 0a61a633..d71dfa6d 100644
--- a/web-app/public/skills/azure-cosmos-java/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-cosmos-java
-description: |
+description: "|"
Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.
Triggers: "CosmosClient java", "CosmosAsyncClient", "cosmos database java", "cosmosdb java", "document database java".
package: azure-cosmos
+risk: unknown
+source: community
---
# Azure Cosmos DB SDK for Java
@@ -256,3 +258,6 @@ try {
| Samples | https://github.com/Azure-Samples/azure-cosmos-java-sql-api-samples |
| Performance Guide | https://learn.microsoft.com/azure/cosmos-db/performance-tips-java-sdk-v4-sql |
| Troubleshooting | https://learn.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-cosmos-py/SKILL.md b/web-app/public/skills/azure-cosmos-py/SKILL.md
index f395ba6d..11903d99 100644
--- a/web-app/public/skills/azure-cosmos-py/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-cosmos-py
-description: |
+description: "|"
Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db", "CosmosClient", "container", "document", "NoSQL", "partition key".
package: azure-cosmos
+risk: unknown
+source: community
---
# Azure Cosmos DB SDK for Python
@@ -275,6 +277,9 @@ except CosmosHttpResponseError as e:
| File | Contents |
|------|----------|
-| [references/partitioning.md](references/partitioning.md) | Partition key strategies, hierarchical keys, hot partition detection and mitigation |
-| [references/query-patterns.md](references/query-patterns.md) | Query optimization, aggregations, pagination, transactions, change feed |
-| [scripts/setup_cosmos_container.py](scripts/setup_cosmos_container.py) | CLI tool for creating containers with partitioning, throughput, and indexing |
+| references/partitioning.md | Partition key strategies, hierarchical keys, hot partition detection and mitigation |
+| references/query-patterns.md | Query optimization, aggregations, pagination, transactions, change feed |
+| scripts/setup_cosmos_container.py | CLI tool for creating containers with partitioning, throughput, and indexing |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-cosmos-rust/SKILL.md b/web-app/public/skills/azure-cosmos-rust/SKILL.md
index 1fb9d452..d8e3ad7a 100644
--- a/web-app/public/skills/azure-cosmos-rust/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-cosmos-rust
-description: |
+description: "|"
Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db rust", "CosmosClient rust", "container", "document rust", "NoSQL rust", "partition key".
package: azure_data_cosmos
+risk: unknown
+source: community
---
# Azure Cosmos DB SDK for Rust
@@ -133,3 +135,6 @@ cargo add azure_data_cosmos --features key_auth
| API Reference | https://docs.rs/azure_data_cosmos |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/cosmos/azure_data_cosmos |
| crates.io | https://crates.io/crates/azure_data_cosmos |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-cosmos-ts/SKILL.md b/web-app/public/skills/azure-cosmos-ts/SKILL.md
index 9f408754..a6a2a5cf 100644
--- a/web-app/public/skills/azure-cosmos-ts/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-cosmos-ts
-description: |
+description: "|"
Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: "Cosmos DB", "@azure/cosmos", "CosmosClient", "document CRUD", "NoSQL queries", "bulk operations", "partition key", "container.items".
package: "@azure/cosmos"
+risk: unknown
+source: community
---
# @azure/cosmos (TypeScript/JavaScript)
@@ -469,3 +471,6 @@ export class ProductService {
| `@azure/cosmos` | Data plane (this SDK) | `npm install @azure/cosmos` |
| `@azure/arm-cosmosdb` | Management plane (ARM) | `npm install @azure/arm-cosmosdb` |
| `@azure/identity` | Authentication | `npm install @azure/identity` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-data-tables-java/SKILL.md b/web-app/public/skills/azure-data-tables-java/SKILL.md
index a05c03e9..49461e7e 100644
--- a/web-app/public/skills/azure-data-tables-java/SKILL.md
+++ b/web-app/public/skills/azure-data-tables-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-data-tables-java
-description: Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at scale.
+description: "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at..."
package: com.azure:azure-data-tables
+risk: unknown
+source: community
---
# Azure Tables SDK for Java
@@ -332,3 +334,6 @@ COSMOS_TABLE_ENDPOINT=https://.table.cosmosdb.azure.com
- "NoSQL key-value storage"
- "partition key row key"
- "table entity CRUD"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-data-tables-py/SKILL.md b/web-app/public/skills/azure-data-tables-py/SKILL.md
index 3c668fd2..7abbdcd5 100644
--- a/web-app/public/skills/azure-data-tables-py/SKILL.md
+++ b/web-app/public/skills/azure-data-tables-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-data-tables-py
-description: |
+description: "|"
Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.
Triggers: "table storage", "TableServiceClient", "TableClient", "entities", "PartitionKey", "RowKey".
package: azure-data-tables
+risk: unknown
+source: community
---
# Azure Tables SDK for Python
@@ -241,3 +243,6 @@ asyncio.run(table_operations())
5. **Use parameterized queries** to prevent injection
6. **Keep entities small** — max 1MB per entity
7. **Use async client** for high-throughput scenarios
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md b/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
index bcf87fd8..0f180e9c 100644
--- a/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-eventgrid-dotnet
-description: |
+description: "|"
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven", "pub/sub".
package: Azure.Messaging.EventGrid
+risk: unknown
+source: community
---
# Azure.Messaging.EventGrid (.NET)
@@ -486,3 +488,6 @@ catch (RequestFailedException)
| Quickstart | https://learn.microsoft.com/azure/event-grid/custom-event-quickstart |
| Pull Delivery | https://learn.microsoft.com/azure/event-grid/pull-delivery-overview |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/eventgrid/Azure.Messaging.EventGrid |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventgrid-java/SKILL.md b/web-app/public/skills/azure-eventgrid-java/SKILL.md
index f456da84..8891c917 100644
--- a/web-app/public/skills/azure-eventgrid-java/SKILL.md
+++ b/web-app/public/skills/azure-eventgrid-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-eventgrid-java
-description: Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.
+description: "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events."
package: com.azure:azure-messaging-eventgrid
+risk: unknown
+source: community
---
# Azure Event Grid SDK for Java
@@ -303,3 +305,6 @@ EVENT_GRID_ACCESS_KEY=
- "event-driven messaging"
- "pub/sub Azure"
- "webhook events"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventgrid-py/SKILL.md b/web-app/public/skills/azure-eventgrid-py/SKILL.md
index f9233204..ddfe5c1f 100644
--- a/web-app/public/skills/azure-eventgrid-py/SKILL.md
+++ b/web-app/public/skills/azure-eventgrid-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-eventgrid-py
-description: |
+description: "|"
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
Triggers: "event grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events".
package: azure-eventgrid
+risk: unknown
+source: community
---
# Azure Event Grid SDK for Python
@@ -166,3 +168,6 @@ async with EventGridPublisherClient(
4. **Use async client** for high-throughput scenarios
5. **Handle retries** — Event Grid has built-in retry
6. **Set appropriate event types** for routing and filtering
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventhub-dotnet/SKILL.md b/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
index 10995f80..1ba7c843 100644
--- a/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-eventhub-dotnet
-description: |
+description: "|"
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming", "EventHubProducerClient", "EventProcessorClient", "send events", "receive events", "checkpointing", "partition".
package: Azure.Messaging.EventHubs
+risk: unknown
+source: community
---
# Azure.Messaging.EventHubs (.NET)
@@ -360,3 +362,6 @@ processor.ProcessEventAsync += async args =>
| `Azure.Messaging.EventHubs.Processor` | Production processing | `dotnet add package Azure.Messaging.EventHubs.Processor` |
| `Azure.ResourceManager.EventHubs` | Management plane (create hubs) | `dotnet add package Azure.ResourceManager.EventHubs` |
| `Microsoft.Azure.WebJobs.Extensions.EventHubs` | Azure Functions binding | `dotnet add package Microsoft.Azure.WebJobs.Extensions.EventHubs` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventhub-java/SKILL.md b/web-app/public/skills/azure-eventhub-java/SKILL.md
index 14c8264c..fb4c9d73 100644
--- a/web-app/public/skills/azure-eventhub-java/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-eventhub-java
-description: Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.
+description: "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures."
package: com.azure:azure-messaging-eventhubs
+risk: unknown
+source: community
---
# Azure Event Hubs SDK for Java
@@ -354,3 +356,6 @@ STORAGE_CONNECTION_STRING=
- "EventProcessorClient"
- "event hub producer consumer"
- "partition processing"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventhub-py/SKILL.md b/web-app/public/skills/azure-eventhub-py/SKILL.md
index 2020084d..3914b7c8 100644
--- a/web-app/public/skills/azure-eventhub-py/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-eventhub-py
-description: |
+description: "|"
Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.
Triggers: "event hubs", "EventHubProducerClient", "EventHubConsumerClient", "streaming", "partitions".
package: azure-eventhub
+risk: unknown
+source: community
---
# Azure Event Hubs SDK for Python
@@ -235,6 +237,9 @@ with producer:
| File | Contents |
|------|----------|
-| [references/checkpointing.md](references/checkpointing.md) | Checkpoint store patterns, blob checkpointing, checkpoint strategies |
-| [references/partitions.md](references/partitions.md) | Partition management, load balancing, starting positions |
-| [scripts/setup_consumer.py](scripts/setup_consumer.py) | CLI for Event Hub info, consumer setup, and event sending/receiving |
+| references/checkpointing.md | Checkpoint store patterns, blob checkpointing, checkpoint strategies |
+| references/partitions.md | Partition management, load balancing, starting positions |
+| scripts/setup_consumer.py | CLI for Event Hub info, consumer setup, and event sending/receiving |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventhub-rust/SKILL.md b/web-app/public/skills/azure-eventhub-rust/SKILL.md
index 429915c4..702cc64e 100644
--- a/web-app/public/skills/azure-eventhub-rust/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-eventhub-rust
-description: |
+description: "|"
Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.
Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust".
package: azure_messaging_eventhubs
+risk: unknown
+source: community
---
# Azure Event Hubs SDK for Rust
@@ -125,3 +127,6 @@ cargo add azure_messaging_eventhubs_checkpointstore_blob
| API Reference | https://docs.rs/azure_messaging_eventhubs |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/eventhubs/azure_messaging_eventhubs |
| crates.io | https://crates.io/crates/azure_messaging_eventhubs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-eventhub-ts/SKILL.md b/web-app/public/skills/azure-eventhub-ts/SKILL.md
index 1626a34e..f8327f7e 100644
--- a/web-app/public/skills/azure-eventhub-ts/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-eventhub-ts
-description: Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event-driven architectures with partitioned consumers.
+description: "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event..."
package: "@azure/event-hubs"
+risk: unknown
+source: community
---
# Azure Event Hubs SDK for TypeScript
@@ -266,3 +268,6 @@ consumer.subscribe({
5. **Handle errors gracefully** - Don't checkpoint on processing failures
6. **Close clients** - Always close producer/consumer when done
7. **Monitor lag** - Track `lastEnqueuedSequenceNumber` vs processed sequence
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-functions/SKILL.md b/web-app/public/skills/azure-functions/SKILL.md
index 55e6b195..fd281284 100644
--- a/web-app/public/skills/azure-functions/SKILL.md
+++ b/web-app/public/skills/azure-functions/SKILL.md
@@ -1,7 +1,8 @@
---
name: azure-functions
-description: "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models. Use when: azure function, azure functions, durable functions, azure serverless, function app."
+description: "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Azure Functions
@@ -40,3 +41,6 @@ Decorator-based approach for Python functions
| Issue | medium | ## Configure Application Insights properly |
| Issue | medium | ## Check extension bundle (most common) |
| Issue | medium | ## Add warmup trigger to initialize your code |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-identity-dotnet/SKILL.md b/web-app/public/skills/azure-identity-dotnet/SKILL.md
index c2c49d2d..d8e4b54e 100644
--- a/web-app/public/skills/azure-identity-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-identity-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-identity-dotnet
-description: |
+description: "|"
Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: "Azure Identity", "DefaultAzureCredential", "ManagedIdentityCredential", "ClientSecretCredential", "authentication .NET", "Azure auth", "credential chain".
package: Azure.Identity
+risk: unknown
+source: community
---
# Azure.Identity (.NET)
@@ -337,3 +339,6 @@ All credential implementations are thread-safe. A single credential instance can
| Credential Chains | https://learn.microsoft.com/dotnet/azure/sdk/authentication/credential-chains |
| Best Practices | https://learn.microsoft.com/dotnet/azure/sdk/authentication/best-practices |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/identity/Azure.Identity |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-identity-java/SKILL.md b/web-app/public/skills/azure-identity-java/SKILL.md
index ddb74269..7541f987 100644
--- a/web-app/public/skills/azure-identity-java/SKILL.md
+++ b/web-app/public/skills/azure-identity-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-identity-java
-description: Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applications.
+description: "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic..."
package: com.azure:azure-identity
+risk: unknown
+source: community
---
# Azure Identity (Java)
@@ -364,3 +366,6 @@ AZURE_AUTHORITY_HOST=https://login.microsoftonline.com/
- "managed identity Java", "service principal Java"
- "Azure login Java", "Azure credentials Java"
- "AZURE_CLIENT_ID", "AZURE_TENANT_ID"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-identity-py/SKILL.md b/web-app/public/skills/azure-identity-py/SKILL.md
index a456d7c7..88555e3c 100644
--- a/web-app/public/skills/azure-identity-py/SKILL.md
+++ b/web-app/public/skills/azure-identity-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-identity-py
-description: |
+description: "|"
Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.
Triggers: "azure-identity", "DefaultAzureCredential", "authentication", "managed identity", "service principal", "credential".
package: azure-identity
+risk: unknown
+source: community
---
# Azure Identity SDK for Python
@@ -190,3 +192,6 @@ async def main():
5. **Close async credentials** explicitly or use context managers
6. **Set AZURE_CLIENT_ID** for user-assigned managed identities
7. **Exclude unused credentials** to speed up authentication
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-identity-rust/SKILL.md b/web-app/public/skills/azure-identity-rust/SKILL.md
index 91c72965..8ed389ce 100644
--- a/web-app/public/skills/azure-identity-rust/SKILL.md
+++ b/web-app/public/skills/azure-identity-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-identity-rust
-description: |
+description: "|"
Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.
Triggers: "azure-identity", "DeveloperToolsCredential", "authentication rust", "managed identity rust", "credential rust".
package: azure_identity
+risk: unknown
+source: community
---
# Azure Identity SDK for Rust
@@ -113,3 +115,6 @@ let credential = ClientSecretCredential::new(
| API Reference | https://docs.rs/azure_identity |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/identity/azure_identity |
| crates.io | https://crates.io/crates/azure_identity |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-identity-ts/SKILL.md b/web-app/public/skills/azure-identity-ts/SKILL.md
index 05ef7358..077bb2c2 100644
--- a/web-app/public/skills/azure-identity-ts/SKILL.md
+++ b/web-app/public/skills/azure-identity-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-identity-ts
-description: Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or interactive browser login.
+description: "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i..."
package: "@azure/identity"
+risk: unknown
+source: community
---
# Azure Identity SDK for TypeScript
@@ -301,3 +303,6 @@ AzureLogger.log = (...args) => {
4. **Scope credentials appropriately** - Use user-assigned identity for multi-tenant scenarios
5. **Handle token refresh** - Azure SDK handles this automatically
6. **Use ChainedTokenCredential** - For custom fallback scenarios
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md b/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
index adb800e9..60452370 100644
--- a/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-keyvault-certificates-rust
-description: |
+description: "|"
Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.
Triggers: "keyvault certificates rust", "CertificateClient rust", "create certificate rust", "import certificate rust".
package: azure_security_keyvault_certificates
+risk: unknown
+source: community
---
# Azure Key Vault Certificates SDK for Rust
@@ -175,3 +177,6 @@ Assign these Key Vault roles:
| API Reference | https://docs.rs/azure_security_keyvault_certificates |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/keyvault/azure_security_keyvault_certificates |
| crates.io | https://crates.io/crates/azure_security_keyvault_certificates |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md b/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
index 6b17a945..c88a11e3 100644
--- a/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-keyvault-keys-rust
-description: |
+description: "|"
Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.
Triggers: "keyvault keys rust", "KeyClient rust", "create key rust", "encrypt rust", "sign rust".
package: azure_security_keyvault_keys
+risk: unknown
+source: community
---
# Azure Key Vault Keys SDK for Rust
@@ -165,3 +167,6 @@ Assign these Key Vault roles:
| API Reference | https://docs.rs/azure_security_keyvault_keys |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/keyvault/azure_security_keyvault_keys |
| crates.io | https://crates.io/crates/azure_security_keyvault_keys |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-keys-ts/SKILL.md b/web-app/public/skills/azure-keyvault-keys-ts/SKILL.md
index d439ef22..d75bc555 100644
--- a/web-app/public/skills/azure-keyvault-keys-ts/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-keys-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-keyvault-keys-ts
-description: Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.
+description: "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys."
package: "@azure/keyvault-keys"
+risk: unknown
+source: community
---
# Azure Key Vault Keys SDK for TypeScript
@@ -267,3 +269,6 @@ try {
4. **Use key rotation policies** - Automate key rotation
5. **Limit key operations** - Only grant needed operations (encrypt, sign, etc.)
6. **Browser not supported** - These SDKs are Node.js only
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-py/SKILL.md b/web-app/public/skills/azure-keyvault-py/SKILL.md
index a26c2283..0709c5fa 100644
--- a/web-app/public/skills/azure-keyvault-py/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-keyvault-py
-description: |
+description: "|"
Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.
Triggers: "key vault", "SecretClient", "KeyClient", "CertificateClient", "secrets", "encryption keys".
package: azure-keyvault-secrets, azure-keyvault-keys, azure-keyvault-certificates
+risk: unknown
+source: community
---
# Azure Key Vault SDK for Python
@@ -245,3 +247,6 @@ except HttpResponseError as e:
6. **Use Key Vault references** in App Service/Functions config
7. **Cache secrets** appropriately to reduce API calls
8. **Use async clients** for high-throughput scenarios
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md b/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
index 7b1fdb79..af92fbd3 100644
--- a/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-keyvault-secrets-rust
-description: |
+description: "|"
Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.
Triggers: "keyvault secrets rust", "SecretClient rust", "get secret rust", "set secret rust".
package: azure_security_keyvault_secrets
+risk: unknown
+source: community
---
# Azure Key Vault Secrets SDK for Rust
@@ -140,3 +142,6 @@ Assign these Key Vault roles:
| API Reference | https://docs.rs/azure_security_keyvault_secrets |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/keyvault/azure_security_keyvault_secrets |
| crates.io | https://crates.io/crates/azure_security_keyvault_secrets |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-keyvault-secrets-ts/SKILL.md b/web-app/public/skills/azure-keyvault-secrets-ts/SKILL.md
index 5ceb3416..64435c90 100644
--- a/web-app/public/skills/azure-keyvault-secrets-ts/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-secrets-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-keyvault-secrets-ts
-description: Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.
+description: "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values."
package: "@azure/keyvault-secrets"
+risk: unknown
+source: community
---
# Azure Key Vault Secrets SDK for TypeScript
@@ -267,3 +269,6 @@ try {
4. **Use key rotation policies** - Automate key rotation
5. **Limit key operations** - Only grant needed operations (encrypt, sign, etc.)
6. **Browser not supported** - These SDKs are Node.js only
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-maps-search-dotnet/SKILL.md b/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
index ee44dfd5..7fd23ea8 100644
--- a/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-maps-search-dotnet
-description: |
+description: "|"
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route directions", "map tiles", "geolocation".
package: Azure.Maps.Search
+risk: unknown
+source: community
---
# Azure Maps (.NET)
@@ -492,3 +494,6 @@ catch (RequestFailedException ex)
| Routing API Reference | https://learn.microsoft.com/dotnet/api/azure.maps.routing |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/maps |
| Pricing | https://azure.microsoft.com/pricing/details/azure-maps/ |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-messaging-webpubsub-java/SKILL.md b/web-app/public/skills/azure-messaging-webpubsub-java/SKILL.md
index 3c2ce2ff..9c602962 100644
--- a/web-app/public/skills/azure-messaging-webpubsub-java/SKILL.md
+++ b/web-app/public/skills/azure-messaging-webpubsub-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-messaging-webpubsub-java
-description: Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
+description: "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications."
package: com.azure:azure-messaging-webpubsub
+risk: unknown
+source: community
---
# Azure Web PubSub SDK for Java
@@ -300,3 +302,6 @@ WEB_PUBSUB_ACCESS_KEY=
- "server-sent events"
- "chat application backend"
- "live updates broadcasting"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md b/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
index 8fd5a85d..e0c1f565 100644
--- a/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
+++ b/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-messaging-webpubsubservice-py
-description: |
+description: "|"
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.
Triggers: "azure-messaging-webpubsubservice", "WebPubSubServiceClient", "real-time", "WebSocket", "pub/sub".
package: azure-messaging-webpubsubservice
+risk: unknown
+source: community
---
# Azure Web PubSub Service SDK for Python
@@ -243,3 +245,6 @@ async def broadcast():
5. **Handle reconnection** in client applications
6. **Use JSON** content type for structured data
7. **Close connections** gracefully with reasons
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
index 7e30ec36..e5052bb2 100644
--- a/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-apicenter-dotnet
-description: |
+description: "|"
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API inventory", "API governance", "API versioning", "API catalog", "API discovery".
package: Azure.ResourceManager.ApiCenter
+risk: unknown
+source: community
---
# Azure.ResourceManager.ApiCenter (.NET)
@@ -409,3 +411,6 @@ catch (RequestFailedException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.resourcemanager.apicenter |
| Product Documentation | https://learn.microsoft.com/azure/api-center/ |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/apicenter/Azure.ResourceManager.ApiCenter |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md b/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
index 0942083c..2a07de6d 100644
--- a/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-mgmt-apicenter-py
-description: |
+description: "|"
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
Triggers: "azure-mgmt-apicenter", "ApiCenterMgmtClient", "API Center", "API inventory", "API governance".
package: azure-mgmt-apicenter
+risk: unknown
+source: community
---
# Azure API Center Management SDK for Python
@@ -240,3 +242,6 @@ metadata = client.metadata_schemas.create_or_update(
4. **Import specifications** to enable API analysis and linting
5. **Use lifecycle stages** to track API maturity
6. **Add contacts** for API ownership and support
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
index 28d8e98a..19df092d 100644
--- a/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-apimanagement-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: "API Management", "APIM service", "create APIM", "manage APIs", "ApiManagementServiceResource", "API policies", "APIM products", "APIM subscriptions".
package: Azure.ResourceManager.ApiManagement
+risk: unknown
+source: community
---
# Azure.ResourceManager.ApiManagement (.NET)
@@ -296,10 +298,10 @@ catch (RequestFailedException ex)
| File | When to Read |
|------|--------------|
-| [references/service-management.md](references/service-management.md) | Service CRUD, SKUs, networking, backup/restore |
-| [references/apis-operations.md](references/apis-operations.md) | APIs, operations, schemas, versioning |
-| [references/products-subscriptions.md](references/products-subscriptions.md) | Products, subscriptions, access control |
-| [references/policies.md](references/policies.md) | Policy XML patterns, scopes, common policies |
+| references/service-management.md | Service CRUD, SKUs, networking, backup/restore |
+| references/apis-operations.md | APIs, operations, schemas, versioning |
+| references/products-subscriptions.md | Products, subscriptions, access control |
+| references/policies.md | Policy XML patterns, scopes, common policies |
## Related Resources
@@ -308,3 +310,6 @@ catch (RequestFailedException ex)
| [API Management Documentation](https://learn.microsoft.com/en-us/azure/api-management/) | Official Azure docs |
| [Policy Reference](https://learn.microsoft.com/en-us/azure/api-management/api-management-policies) | Complete policy reference |
| [SDK Reference](https://learn.microsoft.com/en-us/dotnet/api/azure.resourcemanager.apimanagement) | .NET API reference |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md b/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
index dfd9855c..64d63bd0 100644
--- a/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-mgmt-apimanagement-py
-description: |
+description: "|"
Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.
Triggers: "azure-mgmt-apimanagement", "ApiManagementClient", "APIM", "API gateway", "API Management".
package: azure-mgmt-apimanagement
+risk: unknown
+source: community
---
# Azure API Management SDK for Python
@@ -276,3 +278,6 @@ user = client.user.create_or_update(
4. **Enable Application Insights** for monitoring
5. **Use backends** to abstract backend services
6. **Version your APIs** using APIM's versioning features
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
index 1506fe02..d94beffc 100644
--- a/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-applicationinsights-dotnet
-description: |
+description: "|"
Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: "Application Insights", "ApplicationInsights", "App Insights", "APM", "application monitoring", "web tests", "availability tests", "workbooks".
package: Azure.ResourceManager.ApplicationInsights
+risk: unknown
+source: community
---
# Azure.ResourceManager.ApplicationInsights (.NET)
@@ -484,3 +486,6 @@ builder.Services.AddApplicationInsightsTelemetry(options =>
| API Reference | https://learn.microsoft.com/dotnet/api/azure.resourcemanager.applicationinsights |
| Product Documentation | https://learn.microsoft.com/azure/azure-monitor/app/app-insights-overview |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/applicationinsights/Azure.ResourceManager.ApplicationInsights |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
index 29ac4576..4330e176 100644
--- a/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
@@ -1,10 +1,12 @@
---
name: azure-mgmt-arizeaiobservabilityeval-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations
on Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability
into .NET applications. Triggers: "Arize AI", "ML observability", "ArizeAIObservabilityEval", "Arize organization".
package: Azure.ResourceManager.ArizeAIObservabilityEval
+risk: unknown
+source: community
---
# Azure.ResourceManager.ArizeAIObservabilityEval
@@ -228,3 +230,6 @@ var data = await org.GetAsync();
- [NuGet Package](https://www.nuget.org/packages/Azure.ResourceManager.ArizeAIObservabilityEval)
- [Azure SDK for .NET](https://github.com/Azure/azure-sdk-for-net)
- [Arize AI](https://arize.com/)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
index ae9f134a..94d8824f 100644
--- a/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-botservice-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
package: Azure.ResourceManager.BotService
+risk: unknown
+source: community
---
# Azure.ResourceManager.BotService (.NET)
@@ -332,3 +334,6 @@ catch (RequestFailedException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.resourcemanager.botservice |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/botservice/Azure.ResourceManager.BotService |
| Azure Bot Service Docs | https://learn.microsoft.com/azure/bot-service/ |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md b/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
index 240b8226..c6b851be 100644
--- a/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-botservice-py
-description: |
+description: "|"
Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.
Triggers: "azure-mgmt-botservice", "AzureBotService", "bot management", "conversational AI", "bot channels".
+risk: unknown
+source: community
---
# Azure Bot Service Management SDK for Python
@@ -318,3 +320,6 @@ for conn in connections:
5. **Rotate Direct Line keys** periodically
6. **Use managed identity** when possible for bot connections
7. **Configure proper CORS** for Web Chat channel
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
index a61bcbf3..9721d0dd 100644
--- a/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-fabric-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity", "Fabric SKU", "provision Fabric", "ARM Fabric", "FabricCapacityResource".
package: Azure.ResourceManager.Fabric
+risk: unknown
+source: community
---
# Azure.ResourceManager.Fabric (.NET)
@@ -336,3 +338,6 @@ catch (RequestFailedException ex)
- [GitHub Source](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/fabric/Azure.ResourceManager.Fabric)
- [Microsoft Fabric Documentation](https://learn.microsoft.com/fabric/)
- [Fabric Capacity Management](https://learn.microsoft.com/fabric/admin/service-admin-portal-capacity-settings)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md b/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
index 0b969ea4..2e2ff79b 100644
--- a/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-fabric-py
-description: |
+description: "|"
Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.
Triggers: "azure-mgmt-fabric", "FabricMgmtClient", "Fabric capacity", "Microsoft Fabric", "Power BI capacity".
+risk: unknown
+source: community
---
# Azure Fabric Management SDK for Python
@@ -256,3 +258,6 @@ capacity = poller.result()
6. **Handle LRO properly** — don't assume immediate completion
7. **Set up capacity admins** — specify users who can manage workspaces
8. **Monitor capacity usage** via Azure Monitor metrics
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-mongodbatlas-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-mongodbatlas-dotnet/SKILL.md
index f7055e75..7a7e6a2b 100644
--- a/web-app/public/skills/azure-mgmt-mongodbatlas-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-mongodbatlas-dotnet/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-mgmt-mongodbatlas-dotnet
-description: Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.
+description: "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M..."
package: Azure.ResourceManager.MongoDBAtlas
+risk: unknown
+source: community
---
# Azure.ResourceManager.MongoDBAtlas SDK
@@ -352,3 +354,6 @@ var response = await orgResource.GetAsync();
- [Microsoft Learn: MongoDB Atlas on Azure](https://learn.microsoft.com/en-us/azure/partner-solutions/mongodb-atlas/)
- [API Reference](https://learn.microsoft.com/en-us/dotnet/api/azure.resourcemanager.mongodbatlas)
- [Azure SDK for .NET](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/mongodbatlas)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
index 0c194cbb..c08a2fd3 100644
--- a/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-mgmt-weightsandbiases-dotnet
-description: |
+description: "|"
Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: "Weights and Biases", "W&B", "WeightsAndBiases", "ML experiment tracking", "model registry", "experiment management", "wandb".
package: Azure.ResourceManager.WeightsAndBiases
+risk: unknown
+source: community
---
# Azure.ResourceManager.WeightsAndBiases (.NET)
@@ -326,3 +328,6 @@ run.finish()
| W&B Documentation | https://docs.wandb.ai/ |
| Azure Marketplace | https://azuremarketplace.microsoft.com/marketplace/apps/wandb.wandb-pay-as-you-go |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/weightsandbiases |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-microsoft-playwright-testing-ts/SKILL.md b/web-app/public/skills/azure-microsoft-playwright-testing-ts/SKILL.md
index 99c072d9..32fedf77 100644
--- a/web-app/public/skills/azure-microsoft-playwright-testing-ts/SKILL.md
+++ b/web-app/public/skills/azure-microsoft-playwright-testing-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-microsoft-playwright-testing-ts
-description: Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
+description: "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline..."
package: "@azure/playwright"
+risk: unknown
+source: community
---
# Azure Playwright Workspaces SDK for TypeScript
@@ -300,3 +302,6 @@ export default defineConfig(
4. **Scale workers** — Use `--workers=20` or higher for parallel execution
5. **Region selection** — Choose region closest to your test targets
6. **HTML reporter first** — When using Azure reporter, list HTML reporter before Azure reporter
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md b/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
index e87f9dac..a288b279 100644
--- a/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-monitor-ingestion-java
-description: |
+description: "|"
Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).
Triggers: "LogsIngestionClient java", "azure monitor ingestion java", "custom logs java", "DCR java", "data collection rule java".
package: com.azure:azure-monitor-ingestion
+risk: unknown
+source: community
---
# Azure Monitor Ingestion SDK for Java
@@ -211,7 +213,7 @@ try {
## Querying Uploaded Logs
-Use [azure-monitor-query](../query/SKILL.md) to query ingested logs:
+Use azure-monitor-query to query ingested logs:
```java
// See azure-monitor-query skill for LogsQueryClient usage
@@ -228,3 +230,6 @@ String query = "MyTable_CL | where TimeGenerated > ago(1h) | limit 10";
| DCE Overview | https://learn.microsoft.com/azure/azure-monitor/essentials/data-collection-endpoint-overview |
| DCR Overview | https://learn.microsoft.com/azure/azure-monitor/essentials/data-collection-rule-overview |
| Troubleshooting | https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-ingestion/TROUBLESHOOTING.md |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md b/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
index 01ca6e15..c14e9c95 100644
--- a/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-monitor-ingestion-py
-description: |
+description: "|"
Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.
Triggers: "azure-monitor-ingestion", "LogsIngestionClient", "custom logs", "DCR", "data collection rule", "Log Analytics".
package: azure-monitor-ingestion
+risk: unknown
+source: community
---
# Azure Monitor Ingestion SDK for Python
@@ -202,3 +204,6 @@ Stream names follow patterns:
6. **Batch uploads** — SDK handles batching, but send reasonable chunks
7. **Monitor ingestion** — Check Log Analytics for ingestion status
8. **Use context manager** — Ensures proper client cleanup
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
index 6cfdf8b2..5cbddf1d 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
@@ -1,10 +1,12 @@
---
name: azure-monitor-opentelemetry-exporter-java
-description: |
+description: "|"
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.
Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java".
Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.
package: com.azure:azure-monitor-opentelemetry-exporter
+risk: unknown
+source: community
---
# Azure Monitor OpenTelemetry Exporter for Java
@@ -282,3 +284,6 @@ The `azure-monitor-opentelemetry-autoconfigure` package provides:
| Autoconfigure Package | https://central.sonatype.com/artifact/com.azure/azure-monitor-opentelemetry-autoconfigure |
| OpenTelemetry Java | https://opentelemetry.io/docs/languages/java/ |
| Application Insights | https://learn.microsoft.com/azure/azure-monitor/app/app-insights-overview |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
index b76d8b43..b78077e4 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-monitor-opentelemetry-exporter-py
-description: |
+description: "|"
Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.
Triggers: "azure-monitor-opentelemetry-exporter", "AzureMonitorTraceExporter", "AzureMonitorMetricExporter", "AzureMonitorLogExporter".
package: azure-monitor-opentelemetry-exporter
+risk: unknown
+source: community
---
# Azure Monitor OpenTelemetry Exporter for Python
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
index b051a4d5..93739fcf 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-monitor-opentelemetry-py
-description: |
+description: "|"
Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.
Triggers: "azure-monitor-opentelemetry", "configure_azure_monitor", "Application Insights", "OpenTelemetry distro", "auto-instrumentation".
package: azure-monitor-opentelemetry
+risk: unknown
+source: community
---
# Azure Monitor OpenTelemetry Distro for Python
@@ -222,3 +224,6 @@ configure_azure_monitor(
5. **Use structured logging** for better log analytics queries
6. **Add custom attributes** to spans for better debugging
7. **Use AAD authentication** for production workloads
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-ts/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-ts/SKILL.md
index ec450a88..6b0e9859 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-ts/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-monitor-opentelemetry-ts
-description: Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Application Insights.
+description: "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli..."
package: "@azure/monitor-opentelemetry"
+risk: unknown
+source: community
---
# Azure Monitor OpenTelemetry SDK for TypeScript
@@ -317,3 +319,6 @@ import {
4. **Set sampling ratio** - For high-traffic applications
5. **Add custom dimensions** - Use span processors for enrichment
6. **Graceful shutdown** - Call `shutdownAzureMonitor()` to flush telemetry
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-query-java/SKILL.md b/web-app/public/skills/azure-monitor-query-java/SKILL.md
index b744a66d..f03398d1 100644
--- a/web-app/public/skills/azure-monitor-query-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-query-java/SKILL.md
@@ -1,10 +1,12 @@
---
name: azure-monitor-query-java
-description: |
+description: "|"
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
Triggers: "LogsQueryClient java", "MetricsQueryClient java", "kusto query java", "log analytics java", "azure monitor query java".
Note: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.
package: com.azure:azure-monitor-query
+risk: unknown
+source: community
---
# Azure Monitor Query SDK for Java
@@ -415,3 +417,6 @@ try {
| Kusto Query Language | https://learn.microsoft.com/azure/data-explorer/kusto/query/ |
| Log Analytics Limits | https://learn.microsoft.com/azure/azure-monitor/service-limits#la-query-api |
| Troubleshooting | https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-query/TROUBLESHOOTING.md |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-monitor-query-py/SKILL.md b/web-app/public/skills/azure-monitor-query-py/SKILL.md
index 3784f0a5..44c5028e 100644
--- a/web-app/public/skills/azure-monitor-query-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-query-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-monitor-query-py
-description: |
+description: "|"
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
Triggers: "azure-monitor-query", "LogsQueryClient", "MetricsQueryClient", "Log Analytics", "Kusto queries", "Azure metrics".
package: azure-monitor-query
+risk: unknown
+source: community
---
# Azure Monitor Query SDK for Python
@@ -250,3 +252,6 @@ AppExceptions
5. **Convert to DataFrame** for easier data analysis
6. **Use aggregations** to summarize metric data
7. **Filter by dimensions** to narrow metric results
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-postgres-ts/SKILL.md b/web-app/public/skills/azure-postgres-ts/SKILL.md
index 9455d433..23ebed5f 100644
--- a/web-app/public/skills/azure-postgres-ts/SKILL.md
+++ b/web-app/public/skills/azure-postgres-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-postgres-ts
-description: |
+description: "|"
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL connection", "PostgreSQL TypeScript", "pg Pool", "passwordless postgres".
package: pg
+risk: unknown
+source: community
---
# Azure PostgreSQL for TypeScript (node-postgres)
@@ -475,3 +477,6 @@ import {
| GitHub Repository | https://github.com/brianc/node-postgres |
| Azure PostgreSQL Docs | https://learn.microsoft.com/azure/postgresql/flexible-server/ |
| Passwordless Connection | https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-connect-with-managed-identity |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
index ac02d170..b5a1633e 100644
--- a/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-cosmosdb-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: "Cosmos DB account", "create Cosmos account", "manage Cosmos resources", "ARM Cosmos", "CosmosDBAccountResource", "provision Cosmos DB".
package: Azure.ResourceManager.CosmosDB
+risk: unknown
+source: community
---
# Azure.ResourceManager.CosmosDB (.NET)
@@ -238,9 +240,9 @@ catch (RequestFailedException ex)
| File | When to Read |
|------|--------------|
-| [references/account-management.md](references/account-management.md) | Account CRUD, failover, keys, connection strings, networking |
-| [references/sql-resources.md](references/sql-resources.md) | SQL databases, containers, stored procedures, triggers, UDFs |
-| [references/throughput.md](references/throughput.md) | Manual/autoscale throughput, migration between modes |
+| references/account-management.md | Account CRUD, failover, keys, connection strings, networking |
+| references/sql-resources.md | SQL databases, containers, stored procedures, triggers, UDFs |
+| references/throughput.md | Manual/autoscale throughput, migration between modes |
## Related SDKs
@@ -248,3 +250,6 @@ catch (RequestFailedException ex)
|-----|---------|---------|
| `Microsoft.Azure.Cosmos` | Data plane (document CRUD, queries) | `dotnet add package Microsoft.Azure.Cosmos` |
| `Azure.ResourceManager.CosmosDB` | Management plane (this SDK) | `dotnet add package Azure.ResourceManager.CosmosDB` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
index a7fa410e..40f79c81 100644
--- a/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-durabletask-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision Durable Task", "orchestration scheduler".
package: Azure.ResourceManager.DurableTask
+risk: unknown
+source: community
---
# Azure.ResourceManager.DurableTask (.NET)
@@ -375,3 +377,6 @@ await scheduler.DeleteAsync(WaitUntil.Completed);
- [GitHub: Azure.ResourceManager.DurableTask](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/durabletask/Azure.ResourceManager.DurableTask)
- [NuGet: Azure.ResourceManager.DurableTask](https://www.nuget.org/packages/Azure.ResourceManager.DurableTask)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
index 9c4df3cc..6a5140d9 100644
--- a/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-mysql-dotnet
-description: |
+description: "|"
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database management", "MySQL firewall", "MySQL backup".
package: Azure.ResourceManager.MySql
+risk: unknown
+source: community
---
# Azure.ResourceManager.MySql (.NET)
@@ -390,3 +392,6 @@ string connectionString = $"Server={server.Data.FullyQualifiedDomainName};" +
| API Reference | https://learn.microsoft.com/dotnet/api/azure.resourcemanager.mysql |
| Product Documentation | https://learn.microsoft.com/azure/mysql/flexible-server/ |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/mysql/Azure.ResourceManager.MySql |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
index 6cb39fa2..ad780184 100644
--- a/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-playwright-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
package: Azure.ResourceManager.Playwright
+risk: unknown
+source: community
---
# Azure.ResourceManager.Playwright (.NET)
@@ -295,3 +297,6 @@ Environment.SetEnvironmentVariable("PLAYWRIGHT_SERVICE_URL", serviceUrl.ToString
- [Azure.ResourceManager.Playwright API Reference](https://learn.microsoft.com/en-us/dotnet/api/azure.resourcemanager.playwright)
- [Microsoft Playwright Testing Overview](https://learn.microsoft.com/en-us/azure/playwright-testing/overview-what-is-microsoft-playwright-testing)
- [Quickstart: Run Playwright Tests at Scale](https://learn.microsoft.com/en-us/azure/playwright-testing/quickstart-run-end-to-end-tests)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
index 328f963d..c3cefe84 100644
--- a/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-postgresql-dotnet
-description: |
+description: "|"
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
package: Azure.ResourceManager.PostgreSql
+risk: unknown
+source: community
---
# Azure.ResourceManager.PostgreSql (.NET)
@@ -430,3 +432,6 @@ string connectionString = $"Host={server.Data.FullyQualifiedDomainName};" +
| API Reference | https://learn.microsoft.com/dotnet/api/azure.resourcemanager.postgresql |
| Product Documentation | https://learn.microsoft.com/azure/postgresql/flexible-server/ |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/postgresql/Azure.ResourceManager.PostgreSql |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
index 9ff9eabf..96175c18 100644
--- a/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-redis-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".
package: Azure.ResourceManager.Redis
+risk: unknown
+source: community
---
# Azure.ResourceManager.Redis (.NET)
@@ -354,3 +356,6 @@ var value = await db.StringGetAsync("key");
| `StackExchange.Redis` | Data plane (get/set, pub/sub, streams) | `dotnet add package StackExchange.Redis` |
| `Azure.ResourceManager.Redis` | Management plane (this SDK) | `dotnet add package Azure.ResourceManager.Redis` |
| `Microsoft.Azure.StackExchangeRedis` | Azure-specific Redis extensions | `dotnet add package Microsoft.Azure.StackExchangeRedis` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
index d3175afc..0f98adf5 100644
--- a/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-resource-manager-sql-dotnet
-description: |
+description: "|"
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
package: Azure.ResourceManager.Sql
+risk: unknown
+source: community
---
# Azure.ResourceManager.Sql (.NET)
@@ -306,9 +308,9 @@ catch (RequestFailedException ex)
| File | When to Read |
|------|--------------|
-| [references/server-management.md](references/server-management.md) | Server CRUD, admin credentials, Azure AD auth, networking |
-| [references/database-operations.md](references/database-operations.md) | Database CRUD, scaling, backup, restore, copy |
-| [references/elastic-pools.md](references/elastic-pools.md) | Pool management, adding/removing databases, scaling |
+| references/server-management.md | Server CRUD, admin credentials, Azure AD auth, networking |
+| references/database-operations.md | Database CRUD, scaling, backup, restore, copy |
+| references/elastic-pools.md | Pool management, adding/removing databases, scaling |
## Related SDKs
@@ -317,3 +319,6 @@ catch (RequestFailedException ex)
| `Microsoft.Data.SqlClient` | Data plane (execute queries, stored procedures) | `dotnet add package Microsoft.Data.SqlClient` |
| `Azure.ResourceManager.Sql` | Management plane (this SDK) | `dotnet add package Azure.ResourceManager.Sql` |
| `Microsoft.EntityFrameworkCore.SqlServer` | ORM for SQL Server | `dotnet add package Microsoft.EntityFrameworkCore.SqlServer` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-search-documents-dotnet/SKILL.md b/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
index 4a5d07dc..954fad18 100644
--- a/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-search-documents-dotnet
-description: |
+description: "|"
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET", "SearchClient", "SearchIndexClient", "vector search C#", "semantic search .NET", "hybrid search", "Azure.Search.Documents".
package: Azure.Search.Documents
+risk: unknown
+source: community
---
# Azure.Search.Documents (.NET)
@@ -207,7 +209,7 @@ var suggestions = await searchClient.SuggestAsync("lux", "suggester-name"
## Vector Search
-See [references/vector-search.md](references/vector-search.md) for detailed patterns.
+See references/vector-search.md for detailed patterns.
```csharp
using Azure.Search.Documents.Models;
@@ -232,7 +234,7 @@ var results = await searchClient.SearchAsync(null, options);
## Semantic Search
-See [references/semantic-search.md](references/semantic-search.md) for detailed patterns.
+See references/semantic-search.md for detailed patterns.
```csharp
var options = new SearchOptions
@@ -335,5 +337,8 @@ catch (RequestFailedException ex)
| File | Contents |
|------|----------|
-| [references/vector-search.md](references/vector-search.md) | Vector search, hybrid search, vectorizers |
-| [references/semantic-search.md](references/semantic-search.md) | Semantic ranking, captions, answers |
+| references/vector-search.md | Vector search, hybrid search, vectorizers |
+| references/semantic-search.md | Semantic ranking, captions, answers |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-search-documents-py/SKILL.md b/web-app/public/skills/azure-search-documents-py/SKILL.md
index 7d613c76..a481063b 100644
--- a/web-app/public/skills/azure-search-documents-py/SKILL.md
+++ b/web-app/public/skills/azure-search-documents-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-search-documents-py
-description: |
+description: "|"
Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.
Triggers: "azure-search-documents", "SearchClient", "SearchIndexClient", "vector search", "hybrid search", "semantic search".
package: azure-search-documents
+risk: unknown
+source: community
---
# Azure AI Search SDK for Python
@@ -309,9 +311,9 @@ indexer_client.create_or_update_indexer(indexer)
| File | Contents |
|------|----------|
-| [references/vector-search.md](references/vector-search.md) | HNSW configuration, integrated vectorization, multi-vector queries |
-| [references/semantic-ranking.md](references/semantic-ranking.md) | Semantic configuration, captions, answers, hybrid patterns |
-| [scripts/setup_vector_index.py](scripts/setup_vector_index.py) | CLI script to create vector-enabled search index |
+| references/vector-search.md | HNSW configuration, integrated vectorization, multi-vector queries |
+| references/semantic-ranking.md | Semantic configuration, captions, answers, hybrid patterns |
+| scripts/setup_vector_index.py | CLI script to create vector-enabled search index |
---
@@ -470,7 +472,7 @@ results = search_client.search(
## Agentic Retrieval (Knowledge Bases)
-For LLM-powered Q&A with answer synthesis, see [references/agentic-retrieval.md](references/agentic-retrieval.md).
+For LLM-powered Q&A with answer synthesis, see references/agentic-retrieval.md.
Key concepts:
- **Knowledge Source**: Points to a search index
@@ -526,3 +528,6 @@ except ResourceNotFoundError:
except HttpResponseError as e:
print(f"Search error: {e.message}")
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-search-documents-ts/SKILL.md b/web-app/public/skills/azure-search-documents-ts/SKILL.md
index c35b2085..e196e097 100644
--- a/web-app/public/skills/azure-search-documents-ts/SKILL.md
+++ b/web-app/public/skills/azure-search-documents-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-search-documents-ts
-description: Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building agentic retrieval with knowledge bases.
+description: "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag..."
package: "@azure/search-documents"
+risk: unknown
+source: community
---
# Azure AI Search SDK for TypeScript
@@ -264,3 +266,6 @@ import {
4. **Use filters for security** - Implement document-level security with filters
5. **Index incrementally** - Use `mergeOrUploadDocuments` for updates
6. **Monitor query performance** - Use `includeTotalCount: true` sparingly in production
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md b/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
index 87f12c75..ba20d0e2 100644
--- a/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-security-keyvault-keys-dotnet
-description: |
+description: "|"
Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: "Key Vault keys", "KeyClient", "CryptographyClient", "RSA key", "EC key", "encrypt decrypt .NET", "key rotation", "HSM".
package: Azure.Security.KeyVault.Keys
+risk: unknown
+source: community
---
# Azure.Security.KeyVault.Keys (.NET)
@@ -404,3 +406,6 @@ catch (RequestFailedException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.security.keyvault.keys |
| Quickstart | https://learn.microsoft.com/azure/key-vault/keys/quick-create-net |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/keyvault/Azure.Security.KeyVault.Keys |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-security-keyvault-keys-java/SKILL.md b/web-app/public/skills/azure-security-keyvault-keys-java/SKILL.md
index 3d8415af..3c0770ac 100644
--- a/web-app/public/skills/azure-security-keyvault-keys-java/SKILL.md
+++ b/web-app/public/skills/azure-security-keyvault-keys-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-security-keyvault-keys-java
-description: Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.
+description: "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys."
package: com.azure:azure-security-keyvault-keys
+risk: unknown
+source: community
---
# Azure Key Vault Keys (Java)
@@ -360,3 +362,6 @@ AZURE_KEYVAULT_URL=https://.vault.azure.net
- "encrypt decrypt Java", "sign verify Java"
- "RSA key", "EC key", "HSM key"
- "key rotation", "wrap unwrap key"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-security-keyvault-secrets-java/SKILL.md b/web-app/public/skills/azure-security-keyvault-secrets-java/SKILL.md
index c396d4a7..c35d43fc 100644
--- a/web-app/public/skills/azure-security-keyvault-secrets-java/SKILL.md
+++ b/web-app/public/skills/azure-security-keyvault-secrets-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-security-keyvault-secrets-java
-description: Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.
+description: "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data."
package: com.azure:azure-security-keyvault-secrets
+risk: unknown
+source: community
---
# Azure Key Vault Secrets (Java)
@@ -354,3 +356,6 @@ secretClient.setSecret(new KeyVaultSecret("cert-password", "CertP@ss!")
- "store password", "store API key", "connection string"
- "retrieve secret", "rotate secret"
- "Azure secrets", "vault secrets"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-servicebus-dotnet/SKILL.md b/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
index e49abb6e..22fb9891 100644
--- a/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-servicebus-dotnet
-description: |
+description: "|"
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
package: Azure.Messaging.ServiceBus
+risk: unknown
+source: community
---
# Azure.Messaging.ServiceBus (.NET)
@@ -331,3 +333,6 @@ catch (ServiceBusException ex)
| API Reference | https://learn.microsoft.com/dotnet/api/azure.messaging.servicebus |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/servicebus/Azure.Messaging.ServiceBus |
| Troubleshooting | https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/TROUBLESHOOTING.md |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-servicebus-py/SKILL.md b/web-app/public/skills/azure-servicebus-py/SKILL.md
index fd29fa81..6e82b598 100644
--- a/web-app/public/skills/azure-servicebus-py/SKILL.md
+++ b/web-app/public/skills/azure-servicebus-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-servicebus-py
-description: |
+description: "|"
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
Triggers: "service bus", "ServiceBusClient", "queue", "topic", "subscription", "message broker".
package: azure-servicebus
+risk: unknown
+source: community
---
# Azure Service Bus SDK for Python
@@ -262,6 +264,9 @@ with ServiceBusClient(
| File | Contents |
|------|----------|
-| [references/patterns.md](references/patterns.md) | Competing consumers, sessions, retry patterns, request-response, transactions |
-| [references/dead-letter.md](references/dead-letter.md) | DLQ handling, poison messages, reprocessing strategies |
-| [scripts/setup_servicebus.py](scripts/setup_servicebus.py) | CLI for queue/topic/subscription management and DLQ monitoring |
+| references/patterns.md | Competing consumers, sessions, retry patterns, request-response, transactions |
+| references/dead-letter.md | DLQ handling, poison messages, reprocessing strategies |
+| scripts/setup_servicebus.py | CLI for queue/topic/subscription management and DLQ monitoring |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-servicebus-ts/SKILL.md b/web-app/public/skills/azure-servicebus-ts/SKILL.md
index 9240f31c..f1f93522 100644
--- a/web-app/public/skills/azure-servicebus-ts/SKILL.md
+++ b/web-app/public/skills/azure-servicebus-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-servicebus-ts
-description: Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterprise messaging patterns.
+description: "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri..."
package: "@azure/service-bus"
+risk: unknown
+source: community
---
# Azure Service Bus SDK for TypeScript
@@ -229,5 +231,8 @@ const receiver = client.createReceiver("my-queue", { receiveMode: "receiveAndDel
For detailed patterns, see:
-- [Queues vs Topics Patterns](references/queues-topics.md) - Queue/topic patterns, sessions, receive modes, message settlement
-- [Error Handling and Reliability](references/error-handling.md) - ServiceBusError codes, DLQ handling, lock renewal, graceful shutdown
+- Queues vs Topics Patterns - Queue/topic patterns, sessions, receive modes, message settlement
+- Error Handling and Reliability - ServiceBusError codes, DLQ handling, lock renewal, graceful shutdown
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md b/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
index b7af8072..a9781432 100644
--- a/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
+++ b/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-speech-to-text-rest-py
-description: |
+description: "|"
Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.
Triggers: "speech to text REST", "short audio transcription", "speech recognition REST API", "STT REST", "recognize speech REST".
DO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.
+risk: unknown
+source: community
---
# Azure Speech to Text REST API for Short Audio
@@ -369,4 +371,7 @@ Use the Speech SDK or Batch Transcription API instead when you need:
| File | Contents |
|------|----------|
-| [references/pronunciation-assessment.md](references/pronunciation-assessment.md) | Pronunciation assessment parameters and scoring |
+| references/pronunciation-assessment.md | Pronunciation assessment parameters and scoring |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-blob-java/SKILL.md b/web-app/public/skills/azure-storage-blob-java/SKILL.md
index 0f06b119..588b8cf1 100644
--- a/web-app/public/skills/azure-storage-blob-java/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-java/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-storage-blob-java
-description: Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming data operations.
+description: "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da..."
package: com.azure:azure-storage-blob
+risk: unknown
+source: community
---
# Azure Storage Blob SDK for Java
@@ -386,3 +388,6 @@ AZURE_STORAGE_ACCOUNT_URL=https://.blob.core.windows.net
- "storage streaming"
- "SAS token generation"
- "blob metadata properties"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-blob-py/SKILL.md b/web-app/public/skills/azure-storage-blob-py/SKILL.md
index 4eb9d2d6..6ebe6b36 100644
--- a/web-app/public/skills/azure-storage-blob-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-storage-blob-py
-description: |
+description: "|"
Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.
Triggers: "blob storage", "BlobServiceClient", "ContainerClient", "BlobClient", "upload blob", "download blob".
package: azure-storage-blob
+risk: unknown
+source: community
---
# Azure Blob Storage SDK for Python
@@ -217,3 +219,6 @@ async def download_async():
5. **Prefer `readinto()`** over `readall()` for memory efficiency
6. **Use `walk_blobs()`** for hierarchical listing
7. **Set appropriate content types** for web-served blobs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-blob-rust/SKILL.md b/web-app/public/skills/azure-storage-blob-rust/SKILL.md
index bf279907..2b43e56b 100644
--- a/web-app/public/skills/azure-storage-blob-rust/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-rust/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-storage-blob-rust
-description: |
+description: "|"
Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.
Triggers: "blob storage rust", "BlobClient rust", "upload blob rust", "download blob rust", "container rust".
package: azure_storage_blob
+risk: unknown
+source: community
---
# Azure Blob Storage SDK for Rust
@@ -130,3 +132,6 @@ For Entra ID auth, assign one of these roles:
| API Reference | https://docs.rs/azure_storage_blob |
| Source Code | https://github.com/Azure/azure-sdk-for-rust/tree/main/sdk/storage/azure_storage_blob |
| crates.io | https://crates.io/crates/azure_storage_blob |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-blob-ts/SKILL.md b/web-app/public/skills/azure-storage-blob-ts/SKILL.md
index 24bab504..f941ba21 100644
--- a/web-app/public/skills/azure-storage-blob-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-storage-blob-ts
-description: |
+description: "|"
Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: "blob storage", "@azure/storage-blob", "BlobServiceClient", "ContainerClient", "upload blob", "download blob", "SAS token", "block blob".
package: "@azure/storage-blob"
+risk: unknown
+source: community
---
# @azure/storage-blob (TypeScript/JavaScript)
@@ -480,3 +482,6 @@ import {
| SAS generation | ✅ | ❌ |
| DefaultAzureCredential | ✅ | ❌ |
| Anonymous/SAS access | ✅ | ✅ |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md b/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
index 641fb5be..05c70fd8 100644
--- a/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-storage-file-datalake-py
-description: |
+description: "|"
Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.
Triggers: "data lake", "DataLakeServiceClient", "FileSystemClient", "ADLS Gen2", "hierarchical namespace".
package: azure-storage-file-datalake
+risk: unknown
+source: community
---
# Azure Data Lake Storage Gen2 SDK for Python
@@ -209,3 +211,6 @@ asyncio.run(datalake_operations())
5. **Use `get_paths` with `recursive=True`** for full directory listing
6. **Set metadata** for custom file attributes
7. **Consider Blob API** for simple object storage use cases
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-file-share-py/SKILL.md b/web-app/public/skills/azure-storage-file-share-py/SKILL.md
index 18055bb9..2889a9ff 100644
--- a/web-app/public/skills/azure-storage-file-share-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-share-py/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-storage-file-share-py
-description: |
+description: "|"
Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.
Triggers: "azure-storage-file-share", "ShareServiceClient", "ShareClient", "file share", "SMB".
+risk: unknown
+source: community
---
# Azure Storage File Share SDK for Python
@@ -236,3 +238,6 @@ async def upload_file():
5. **Set quotas** to prevent unexpected storage costs
6. **Use ranges** for partial file updates
7. **Close async clients** explicitly
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-file-share-ts/SKILL.md b/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
index 501e06d9..6e9bae7f 100644
--- a/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-storage-file-share-ts
-description: |
+description: "|"
Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: "file share", "@azure/storage-file-share", "ShareServiceClient", "ShareClient", "SMB", "Azure Files".
package: "@azure/storage-file-share"
+risk: unknown
+source: community
---
# @azure/storage-file-share (TypeScript/JavaScript)
@@ -491,3 +493,6 @@ import {
| SAS generation | ✅ | ❌ |
| DefaultAzureCredential | ✅ | ❌ |
| Anonymous/SAS access | ✅ | ✅ |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-queue-py/SKILL.md b/web-app/public/skills/azure-storage-queue-py/SKILL.md
index b32199ca..38c91d03 100644
--- a/web-app/public/skills/azure-storage-queue-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-queue-py/SKILL.md
@@ -1,9 +1,11 @@
---
name: azure-storage-queue-py
-description: |
+description: "|"
Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.
Triggers: "queue storage", "QueueServiceClient", "QueueClient", "message queue", "dequeue".
package: azure-storage-queue
+risk: unknown
+source: community
---
# Azure Queue Storage SDK for Python
@@ -211,3 +213,6 @@ queue_client.send_message(b"Binary content")
5. **Use `peek_messages`** for monitoring without affecting queue
6. **Set `time_to_live`** to prevent stale messages
7. **Consider Service Bus** for advanced features (sessions, topics)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-storage-queue-ts/SKILL.md b/web-app/public/skills/azure-storage-queue-ts/SKILL.md
index 8e63d5bb..d06d259f 100644
--- a/web-app/public/skills/azure-storage-queue-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-queue-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: azure-storage-queue-ts
-description: |
+description: "|"
Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: "queue storage", "@azure/storage-queue", "QueueServiceClient", "QueueClient", "send message", "receive message", "dequeue", "visibility timeout".
package: "@azure/storage-queue"
+risk: unknown
+source: community
---
# @azure/storage-queue (TypeScript/JavaScript)
@@ -522,3 +524,6 @@ import {
| DefaultAzureCredential | ✅ | ❌ |
| Anonymous/SAS access | ✅ | ✅ |
| All message operations | ✅ | ✅ |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/azure-web-pubsub-ts/SKILL.md b/web-app/public/skills/azure-web-pubsub-ts/SKILL.md
index c3498744..5216c25f 100644
--- a/web-app/public/skills/azure-web-pubsub-ts/SKILL.md
+++ b/web-app/public/skills/azure-web-pubsub-ts/SKILL.md
@@ -1,7 +1,9 @@
---
name: azure-web-pubsub-ts
-description: Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub messaging, group chat, or live notifications.
+description: "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me..."
package: "@azure/web-pubsub, @azure/web-pubsub-client"
+risk: unknown
+source: community
---
# Azure Web PubSub SDKs for TypeScript
@@ -308,3 +310,6 @@ import {
4. **Handle reconnection** - Client auto-reconnects by default
5. **Validate in handleConnect** - Reject unauthorized connections early
6. **Use noEcho** - Prevent message echo back to sender when needed
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/backend-architect/SKILL.md b/web-app/public/skills/backend-architect/SKILL.md
index 42fcf333..e2283367 100644
--- a/web-app/public/skills/backend-architect/SKILL.md
+++ b/web-app/public/skills/backend-architect/SKILL.md
@@ -1,6 +1,6 @@
---
name: backend-architect
-description: Expert backend architect specializing in scalable API design,
+description: "Expert backend architect specializing in scalable API design,"
microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC
APIs, event-driven architectures, service mesh patterns, and modern backend
frameworks. Handles service boundary definition, inter-service communication,
@@ -8,6 +8,8 @@ description: Expert backend architect specializing in scalable API design,
backend services or APIs.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.
diff --git a/web-app/public/skills/backend-dev-guidelines/SKILL.md b/web-app/public/skills/backend-dev-guidelines/SKILL.md
index eebeb728..ed63c07a 100644
--- a/web-app/public/skills/backend-dev-guidelines/SKILL.md
+++ b/web-app/public/skills/backend-dev-guidelines/SKILL.md
@@ -1,6 +1,8 @@
---
name: backend-dev-guidelines
-description: Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
+description: "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid..."
+risk: unknown
+source: community
---
# Backend Development Guidelines
@@ -340,3 +342,6 @@ Before finalizing backend work:
**Status:** Stable · Enforceable · Production-grade
**Intended Use:** Long-lived Node.js microservices with real traffic and real risk
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/architecture-overview.md b/web-app/public/skills/backend-dev-guidelines/resources/architecture-overview.md
index 9828570b..d472845f 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/architecture-overview.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/architecture-overview.md
@@ -446,6 +446,6 @@ async findByEmail(email: string): Promise {
---
**Related Files:**
-- [SKILL.md](SKILL.md) - Main guide
+- SKILL.md - Main guide
- [routing-and-controllers.md](routing-and-controllers.md) - Routes and controllers details
- [services-and-repositories.md](services-and-repositories.md) - Service and repository patterns
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/async-and-errors.md b/web-app/public/skills/backend-dev-guidelines/resources/async-and-errors.md
index 37a90499..2a1ca99f 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/async-and-errors.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/async-and-errors.md
@@ -302,6 +302,6 @@ process.on('uncaughtException', (error) => {
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [sentry-and-monitoring.md](sentry-and-monitoring.md)
- [complete-examples.md](complete-examples.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/complete-examples.md b/web-app/public/skills/backend-dev-guidelines/resources/complete-examples.md
index 51af140e..ab62578d 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/complete-examples.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/complete-examples.md
@@ -632,7 +632,7 @@ Controller formats response
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [routing-and-controllers.md](routing-and-controllers.md)
- [services-and-repositories.md](services-and-repositories.md)
- [validation-patterns.md](validation-patterns.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/configuration.md b/web-app/public/skills/backend-dev-guidelines/resources/configuration.md
index 9917a753..bba45d64 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/configuration.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/configuration.md
@@ -271,5 +271,5 @@ const jwtSecret = config.tokens.jwt;
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [testing-guide.md](testing-guide.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/database-patterns.md b/web-app/public/skills/backend-dev-guidelines/resources/database-patterns.md
index fbfaf195..413445dc 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/database-patterns.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/database-patterns.md
@@ -219,6 +219,6 @@ try {
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [services-and-repositories.md](services-and-repositories.md)
- [async-and-errors.md](async-and-errors.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/middleware-guide.md b/web-app/public/skills/backend-dev-guidelines/resources/middleware-guide.md
index d3423b65..ae7b0a2d 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/middleware-guide.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/middleware-guide.md
@@ -208,6 +208,6 @@ app.use(Sentry.Handlers.errorHandler());
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [routing-and-controllers.md](routing-and-controllers.md)
- [async-and-errors.md](async-and-errors.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/routing-and-controllers.md b/web-app/public/skills/backend-dev-guidelines/resources/routing-and-controllers.md
index a28296be..ec39a468 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/routing-and-controllers.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/routing-and-controllers.md
@@ -751,6 +751,6 @@ export class ActionRepository {
---
**Related Files:**
-- [SKILL.md](SKILL.md) - Main guide
+- SKILL.md - Main guide
- [services-and-repositories.md](services-and-repositories.md) - Service layer details
- [complete-examples.md](complete-examples.md) - Full refactoring examples
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/sentry-and-monitoring.md b/web-app/public/skills/backend-dev-guidelines/resources/sentry-and-monitoring.md
index 015998ae..7888cdd0 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/sentry-and-monitoring.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/sentry-and-monitoring.md
@@ -331,6 +331,6 @@ async function good() {
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [routing-and-controllers.md](routing-and-controllers.md)
- [async-and-errors.md](async-and-errors.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/services-and-repositories.md b/web-app/public/skills/backend-dev-guidelines/resources/services-and-repositories.md
index 749b26b6..3bee4bf7 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/services-and-repositories.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/services-and-repositories.md
@@ -783,7 +783,7 @@ describe('UserService', () => {
---
**Related Files:**
-- [SKILL.md](SKILL.md) - Main guide
+- SKILL.md - Main guide
- [routing-and-controllers.md](routing-and-controllers.md) - Controllers that use services
- [database-patterns.md](database-patterns.md) - Prisma and repository patterns
- [complete-examples.md](complete-examples.md) - Full service/repository examples
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/testing-guide.md b/web-app/public/skills/backend-dev-guidelines/resources/testing-guide.md
index 21e3820d..5e468bfe 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/testing-guide.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/testing-guide.md
@@ -230,6 +230,6 @@ npm test -- --coverage
---
**Related Files:**
-- [SKILL.md](SKILL.md)
+- SKILL.md
- [services-and-repositories.md](services-and-repositories.md)
- [complete-examples.md](complete-examples.md)
diff --git a/web-app/public/skills/backend-dev-guidelines/resources/validation-patterns.md b/web-app/public/skills/backend-dev-guidelines/resources/validation-patterns.md
index 6eceb477..8d941d14 100644
--- a/web-app/public/skills/backend-dev-guidelines/resources/validation-patterns.md
+++ b/web-app/public/skills/backend-dev-guidelines/resources/validation-patterns.md
@@ -748,7 +748,7 @@ router.post('/users',
---
**Related Files:**
-- [SKILL.md](SKILL.md) - Main guide
+- SKILL.md - Main guide
- [routing-and-controllers.md](routing-and-controllers.md) - Using validation in controllers
- [services-and-repositories.md](services-and-repositories.md) - Using DTOs in services
- [async-and-errors.md](async-and-errors.md) - Error handling patterns
diff --git a/web-app/public/skills/backend-development-feature-development/SKILL.md b/web-app/public/skills/backend-development-feature-development/SKILL.md
index 1acb4cd5..1dae66b3 100644
--- a/web-app/public/skills/backend-development-feature-development/SKILL.md
+++ b/web-app/public/skills/backend-development-feature-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: backend-development-feature-development
description: "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services."
+risk: unknown
+source: community
---
Orchestrate end-to-end feature development from requirements to production deployment:
diff --git a/web-app/public/skills/backend-security-coder/SKILL.md b/web-app/public/skills/backend-security-coder/SKILL.md
index 35fb3f88..799b496d 100644
--- a/web-app/public/skills/backend-security-coder/SKILL.md
+++ b/web-app/public/skills/backend-security-coder/SKILL.md
@@ -1,10 +1,12 @@
---
name: backend-security-coder
-description: Expert in secure backend coding practices specializing in input
+description: "Expert in secure backend coding practices specializing in input"
validation, authentication, and API security. Use PROACTIVELY for backend
security implementations or security code reviews.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/backtesting-frameworks/SKILL.md b/web-app/public/skills/backtesting-frameworks/SKILL.md
index e377e979..5d6ae2c8 100644
--- a/web-app/public/skills/backtesting-frameworks/SKILL.md
+++ b/web-app/public/skills/backtesting-frameworks/SKILL.md
@@ -1,6 +1,8 @@
---
name: backtesting-frameworks
-description: Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
+description: "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg..."
+risk: unknown
+source: community
---
# Backtesting Frameworks
diff --git a/web-app/public/skills/bamboohr-automation/SKILL.md b/web-app/public/skills/bamboohr-automation/SKILL.md
index 7c075a85..6e47b471 100644
--- a/web-app/public/skills/bamboohr-automation/SKILL.md
+++ b/web-app/public/skills/bamboohr-automation/SKILL.md
@@ -3,6 +3,8 @@ name: bamboohr-automation
description: "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# BambooHR Automation via Rube MCP
@@ -218,3 +220,6 @@ For keeping external systems in sync with BambooHR:
| Update employee | BAMBOOHR_UPDATE_EMPLOYEE | id, (field updates) |
| List dependents | BAMBOOHR_DEPENDENTS_GET_ALL | employeeId |
| Benefit coverages | BAMBOOHR_BENEFIT_GET_COVERAGES | (check schema) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/basecamp-automation/SKILL.md b/web-app/public/skills/basecamp-automation/SKILL.md
index 6f27369e..957631c9 100644
--- a/web-app/public/skills/basecamp-automation/SKILL.md
+++ b/web-app/public/skills/basecamp-automation/SKILL.md
@@ -3,6 +3,8 @@ name: basecamp-automation
description: "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Basecamp Automation via Rube MCP
@@ -232,3 +234,6 @@ Basecamp uses page-based pagination on list endpoints:
| List all people | `BASECAMP_GET_PEOPLE` | (none) |
| List project people | `BASECAMP_LIST_PROJECT_PEOPLE` | `project_id` |
| Manage access | `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` | `project_id`, `grant`, `revoke`, `create` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/bash-defensive-patterns/SKILL.md b/web-app/public/skills/bash-defensive-patterns/SKILL.md
index b055ef65..270dca57 100644
--- a/web-app/public/skills/bash-defensive-patterns/SKILL.md
+++ b/web-app/public/skills/bash-defensive-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: bash-defensive-patterns
-description: Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.
+description: "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety."
+risk: unknown
+source: community
---
# Bash Defensive Patterns
diff --git a/web-app/public/skills/bash-linux/SKILL.md b/web-app/public/skills/bash-linux/SKILL.md
index 4776fcf7..cc3d59bb 100644
--- a/web-app/public/skills/bash-linux/SKILL.md
+++ b/web-app/public/skills/bash-linux/SKILL.md
@@ -1,7 +1,9 @@
---
name: bash-linux
-description: Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
+description: "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Bash Linux Patterns
@@ -197,3 +199,6 @@ trap cleanup EXIT
---
> **Remember:** Bash is text-based. Use `&&` for success chains, `set -e` for safety, and quote your variables!
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/bash-pro/SKILL.md b/web-app/public/skills/bash-pro/SKILL.md
index 107462b1..3beb7730 100644
--- a/web-app/public/skills/bash-pro/SKILL.md
+++ b/web-app/public/skills/bash-pro/SKILL.md
@@ -1,10 +1,12 @@
---
name: bash-pro
-description: Master of defensive Bash scripting for production automation, CI/CD
+description: "Master of defensive Bash scripting for production automation, CI/CD"
pipelines, and system utilities. Expert in safe, portable, and testable shell
scripts.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/bash-scripting/SKILL.md b/web-app/public/skills/bash-scripting/SKILL.md
new file mode 100644
index 00000000..f939781b
--- /dev/null
+++ b/web-app/public/skills/bash-scripting/SKILL.md
@@ -0,0 +1,197 @@
+---
+name: bash-scripting
+description: "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing."
+source: personal
+risk: safe
+domain: system-administration
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Bash Scripting Workflow
+
+## Overview
+
+Specialized workflow for creating robust, production-ready bash scripts with defensive programming patterns, comprehensive error handling, and automated testing.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating automation scripts
+- Writing system administration tools
+- Building deployment scripts
+- Developing backup solutions
+- Creating CI/CD scripts
+
+## Workflow Phases
+
+### Phase 1: Script Design
+
+#### Skills to Invoke
+- `bash-pro` - Professional scripting
+- `bash-defensive-patterns` - Defensive patterns
+
+#### Actions
+1. Define script purpose
+2. Identify inputs/outputs
+3. Plan error handling
+4. Design logging strategy
+5. Document requirements
+
+#### Copy-Paste Prompts
+```
+Use @bash-pro to design production-ready bash script
+```
+
+### Phase 2: Script Structure
+
+#### Skills to Invoke
+- `bash-pro` - Script structure
+- `bash-defensive-patterns` - Safety patterns
+
+#### Actions
+1. Add shebang and strict mode
+2. Create usage function
+3. Implement argument parsing
+4. Set up logging
+5. Add cleanup handlers
+
+#### Copy-Paste Prompts
+```
+Use @bash-defensive-patterns to implement strict mode and error handling
+```
+
+### Phase 3: Core Implementation
+
+#### Skills to Invoke
+- `bash-linux` - Linux commands
+- `linux-shell-scripting` - Shell scripting
+
+#### Actions
+1. Implement main functions
+2. Add input validation
+3. Create helper functions
+4. Handle edge cases
+5. Add progress indicators
+
+#### Copy-Paste Prompts
+```
+Use @bash-linux to implement system commands
+```
+
+### Phase 4: Error Handling
+
+#### Skills to Invoke
+- `bash-defensive-patterns` - Error handling
+- `error-handling-patterns` - Error patterns
+
+#### Actions
+1. Add trap handlers
+2. Implement retry logic
+3. Create error messages
+4. Set up exit codes
+5. Add rollback capability
+
+#### Copy-Paste Prompts
+```
+Use @bash-defensive-patterns to add comprehensive error handling
+```
+
+### Phase 5: Logging
+
+#### Skills to Invoke
+- `bash-pro` - Logging patterns
+
+#### Actions
+1. Create logging function
+2. Add log levels
+3. Implement timestamps
+4. Configure log rotation
+5. Add debug mode
+
+#### Copy-Paste Prompts
+```
+Use @bash-pro to implement structured logging
+```
+
+### Phase 6: Testing
+
+#### Skills to Invoke
+- `bats-testing-patterns` - Bats testing
+- `shellcheck-configuration` - ShellCheck
+
+#### Actions
+1. Write Bats tests
+2. Run ShellCheck
+3. Test edge cases
+4. Verify error handling
+5. Test with different inputs
+
+#### Copy-Paste Prompts
+```
+Use @bats-testing-patterns to write script tests
+```
+
+```
+Use @shellcheck-configuration to lint bash script
+```
+
+### Phase 7: Documentation
+
+#### Skills to Invoke
+- `documentation-templates` - Documentation
+
+#### Actions
+1. Add script header
+2. Document functions
+3. Create usage examples
+4. List dependencies
+5. Add troubleshooting section
+
+#### Copy-Paste Prompts
+```
+Use @documentation-templates to document bash script
+```
+
+## Script Template
+
+```bash
+#!/usr/bin/env bash
+set -euo pipefail
+
+readonly SCRIPT_NAME=$(basename "$0")
+readonly SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)
+
+log() { echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*"; }
+error() { log "ERROR: $*" >&2; exit 1; }
+
+usage() { cat <,
+ mut query: Query<(&mut Transform, &Velocity), With>,
+) {
+ for (mut transform, velocity) in &mut query {
+ transform.translation.x += velocity.x * time.delta_seconds();
+ transform.translation.y += velocity.y * time.delta_seconds();
+ }
+}
+```
+
+### 3. Managing Resources
+
+Use `Resource` for global data (score, game state).
+
+```rust
+#[derive(Resource)]
+struct GameState {
+ score: u32,
+}
+
+fn score_system(mut game_state: ResMut) {
+ game_state.score += 10;
+}
+```
+
+### 4. Scheduling Systems
+
+Add systems to the `App` builder, defining execution order if needed.
+
+```rust
+fn main() {
+ App::new()
+ .add_plugins(DefaultPlugins)
+ .init_resource::()
+ .add_systems(Update, (movement_system, score_system).chain())
+ .run();
+}
+```
+
+## Examples
+
+### Example 1: Spawning Entities with Bundles
+
+```rust
+#[derive(Bundle)]
+struct PlayerBundle {
+ player: Player,
+ velocity: Velocity,
+ sprite: SpriteBundle,
+}
+
+fn setup(mut commands: Commands, asset_server: Res) {
+ commands.spawn(PlayerBundle {
+ player: Player,
+ velocity: Velocity { x: 10.0, y: 0.0 },
+ sprite: SpriteBundle {
+ texture: asset_server.load("player.png"),
+ ..default()
+ },
+ });
+}
+```
+
+### Example 2: Query Filters
+
+Use `With` and `Without` to filter entities efficiently.
+
+```rust
+fn enemy_behavior(
+ query: Query<&Transform, (With, Without)>,
+) {
+ for transform in &query {
+ // Only active enemies processed here
+ }
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `Query` filters (`With`, `Without`, `Changed`) to reduce iteration count.
+- ✅ **Do:** Prefer `Res` over `ResMut` when read-only access is sufficient to allow parallel execution.
+- ✅ **Do:** Use `Bundle` to spawn complex entities atomically.
+- ❌ **Don't:** Store heavy logic inside Components; keep them as pure data.
+- ❌ **Don't:** Use `RefCell` or interior mutability inside components; let the ECS handle borrowing.
+
+## Troubleshooting
+
+**Problem:** System panic with "Conflict" error.
+**Solution:** You are likely trying to access the same component mutably in two systems running in parallel. Use `.chain()` to order them or split the logic.
diff --git a/web-app/public/skills/billing-automation/SKILL.md b/web-app/public/skills/billing-automation/SKILL.md
index cd043e97..0688a129 100644
--- a/web-app/public/skills/billing-automation/SKILL.md
+++ b/web-app/public/skills/billing-automation/SKILL.md
@@ -1,6 +1,8 @@
---
name: billing-automation
-description: Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
+description: "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu..."
+risk: unknown
+source: community
---
# Billing Automation
diff --git a/web-app/public/skills/binary-analysis-patterns/SKILL.md b/web-app/public/skills/binary-analysis-patterns/SKILL.md
index 23836cd2..31b21dfd 100644
--- a/web-app/public/skills/binary-analysis-patterns/SKILL.md
+++ b/web-app/public/skills/binary-analysis-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: binary-analysis-patterns
-description: Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
+description: "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing..."
+risk: unknown
+source: community
---
# Binary Analysis Patterns
diff --git a/web-app/public/skills/bitbucket-automation/SKILL.md b/web-app/public/skills/bitbucket-automation/SKILL.md
index 3fcbcc48..26a9962f 100644
--- a/web-app/public/skills/bitbucket-automation/SKILL.md
+++ b/web-app/public/skills/bitbucket-automation/SKILL.md
@@ -3,6 +3,8 @@ name: bitbucket-automation
description: "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Bitbucket Automation via Rube MCP
@@ -222,3 +224,6 @@ Bitbucket Query Language is available on list endpoints:
| Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` |
| Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |
| List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/blockchain-developer/SKILL.md b/web-app/public/skills/blockchain-developer/SKILL.md
index 50a8f632..192c89fb 100644
--- a/web-app/public/skills/blockchain-developer/SKILL.md
+++ b/web-app/public/skills/blockchain-developer/SKILL.md
@@ -1,11 +1,13 @@
---
name: blockchain-developer
-description: Build production-ready Web3 applications, smart contracts, and
+description: "Build production-ready Web3 applications, smart contracts, and"
decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and
enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3
apps, DeFi protocols, or blockchain infrastructure.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/blockrun/SKILL.md b/web-app/public/skills/blockrun/SKILL.md
index 334b74a9..6bb2c5e6 100644
--- a/web-app/public/skills/blockrun/SKILL.md
+++ b/web-app/public/skills/blockrun/SKILL.md
@@ -1,7 +1,9 @@
---
name: blockrun
-description: Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models ("blockrun", "use grok", "use gpt", "dall-e", "deepseek")
+description: "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da..."
allowed-tools: Read, Bash(python:*), Bash(python3:*), Bash(pip:*), Bash(source:*)
+risk: unknown
+source: community
---
# BlockRun
diff --git a/web-app/public/skills/box-automation/SKILL.md b/web-app/public/skills/box-automation/SKILL.md
index e59707db..9bdd221e 100644
--- a/web-app/public/skills/box-automation/SKILL.md
+++ b/web-app/public/skills/box-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: box-automation
-description: "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for current schemas."
+description: "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Box Automation via Rube MCP
@@ -231,3 +233,6 @@ Box tools use double underscore notation for nested objects:
| Cancel sign request | `BOX_CANCEL_BOX_SIGN_REQUEST` | `sign_request_id` |
| Recent items | `BOX_LIST_RECENTLY_ACCESSED_ITEMS` | (none) |
| Create zip download | `BOX_CREATE_ZIP_DOWNLOAD` | item IDs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/brainstorming/SKILL.md b/web-app/public/skills/brainstorming/SKILL.md
index a21f1629..ea2d0bfb 100644
--- a/web-app/public/skills/brainstorming/SKILL.md
+++ b/web-app/public/skills/brainstorming/SKILL.md
@@ -1,10 +1,8 @@
---
name: brainstorming
-description: >
- Use this skill before any creative or constructive work
- (features, components, architecture, behavior changes, or functionality).
- This skill transforms vague ideas into validated designs through
- disciplined, incremental reasoning and collaboration.
+description: "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration."
+risk: unknown
+source: community
---
# Brainstorming Ideas Into Designs
@@ -228,3 +226,6 @@ If any criterion is unmet:
---
If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/brand-guidelines-anthropic/SKILL.md b/web-app/public/skills/brand-guidelines-anthropic/SKILL.md
index 47c72c60..ea65410f 100644
--- a/web-app/public/skills/brand-guidelines-anthropic/SKILL.md
+++ b/web-app/public/skills/brand-guidelines-anthropic/SKILL.md
@@ -1,7 +1,9 @@
---
-name: brand-guidelines
-description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
+name: brand-guidelines-anthropic
+description: "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Anthropic Brand Styling
@@ -71,3 +73,6 @@ To access Anthropic's official brand identity and style resources, use this skil
- Uses RGB color values for precise brand matching
- Applied via python-pptx's RGBColor class
- Maintains color fidelity across different systems
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/brand-guidelines-community/SKILL.md b/web-app/public/skills/brand-guidelines-community/SKILL.md
index 47c72c60..f64cc7d9 100644
--- a/web-app/public/skills/brand-guidelines-community/SKILL.md
+++ b/web-app/public/skills/brand-guidelines-community/SKILL.md
@@ -1,7 +1,9 @@
---
-name: brand-guidelines
-description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
+name: brand-guidelines-community
+description: "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Anthropic Brand Styling
@@ -71,3 +73,6 @@ To access Anthropic's official brand identity and style resources, use this skil
- Uses RGB color values for precise brand matching
- Applied via python-pptx's RGBColor class
- Maintains color fidelity across different systems
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/brevo-automation/SKILL.md b/web-app/public/skills/brevo-automation/SKILL.md
index 55b6a8cb..d7edf501 100644
--- a/web-app/public/skills/brevo-automation/SKILL.md
+++ b/web-app/public/skills/brevo-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: brevo-automation
-description: "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas."
+description: "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Brevo Automation via Rube MCP
@@ -195,3 +197,6 @@ Automate Brevo (formerly Sendinblue) email marketing operations through Composio
| Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent |
| Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId |
| List senders | BREVO_GET_ALL_SENDERS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/broken-authentication/SKILL.md b/web-app/public/skills/broken-authentication/SKILL.md
index ff3c8cd8..2630446e 100644
--- a/web-app/public/skills/broken-authentication/SKILL.md
+++ b/web-app/public/skills/broken-authentication/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Broken Authentication Testing
-description: This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
+name: broken-authentication
+description: "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Broken Authentication Testing
@@ -474,3 +476,6 @@ https://target.com/reset?token=a1b2c3d4e5f6&email=admin@example.com
| Session analysis inconclusive | Collect 1000+ tokens; use statistical tools; check for timestamps; compare accounts |
| MFA cannot be bypassed | Document as secure; test backup/recovery mechanisms; check MFA fatigue; verify enrollment |
| Account lockout prevents testing | Request multiple test accounts; test threshold first; use slower timing |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/browser-automation/SKILL.md b/web-app/public/skills/browser-automation/SKILL.md
index a4a51cba..e97db722 100644
--- a/web-app/public/skills/browser-automation/SKILL.md
+++ b/web-app/public/skills/browser-automation/SKILL.md
@@ -1,7 +1,8 @@
---
name: browser-automation
-description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202"
+description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Browser Automation
@@ -68,3 +69,6 @@ Let Playwright wait automatically, never add manual waits
## Related Skills
Works well with: `agent-tool-builder`, `workflow-automation`, `computer-use-agents`, `test-architect`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/browser-extension-builder/SKILL.md b/web-app/public/skills/browser-extension-builder/SKILL.md
index b1aa1d6b..91376793 100644
--- a/web-app/public/skills/browser-extension-builder/SKILL.md
+++ b/web-app/public/skills/browser-extension-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: browser-extension-builder
-description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3."
+description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Browser Extension Builder
@@ -259,3 +260,6 @@ Update quickly when broken.
## Related Skills
Works well with: `frontend`, `micro-saas-launcher`, `personal-tool-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/bullmq-specialist/SKILL.md b/web-app/public/skills/bullmq-specialist/SKILL.md
index f1d86d42..ccc72772 100644
--- a/web-app/public/skills/bullmq-specialist/SKILL.md
+++ b/web-app/public/skills/bullmq-specialist/SKILL.md
@@ -2,6 +2,7 @@
name: bullmq-specialist
description: "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# BullMQ Specialist
@@ -55,3 +56,6 @@ Complex multi-step job processing with parent-child relationships
## Related Skills
Works well with: `redis-specialist`, `backend`, `nextjs-app-router`, `email-systems`, `ai-workflow-automation`, `performance-hunter`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/bun-development/SKILL.md b/web-app/public/skills/bun-development/SKILL.md
index 4dfb8adf..8b975d7e 100644
--- a/web-app/public/skills/bun-development/SKILL.md
+++ b/web-app/public/skills/bun-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: bun-development
-description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun."
+description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o..."
+risk: unknown
+source: community
---
# ⚡ Bun Development
diff --git a/web-app/public/skills/burp-suite-testing/SKILL.md b/web-app/public/skills/burp-suite-testing/SKILL.md
index cb97ab42..d019fcf9 100644
--- a/web-app/public/skills/burp-suite-testing/SKILL.md
+++ b/web-app/public/skills/burp-suite-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Burp Suite Web Application Testing
-description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
+name: burp-suite-testing
+description: "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Burp Suite Web Application Testing
@@ -378,3 +380,6 @@ javascript:alert(1)
- Check intercept rules aren't filtering target
- Ensure browser is using Burp proxy
- Verify target isn't using unsupported protocol
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/business-analyst/SKILL.md b/web-app/public/skills/business-analyst/SKILL.md
index 0e30d0de..ca931200 100644
--- a/web-app/public/skills/business-analyst/SKILL.md
+++ b/web-app/public/skills/business-analyst/SKILL.md
@@ -1,11 +1,13 @@
---
name: business-analyst
-description: Master modern business analysis with AI-powered analytics,
+description: "Master modern business analysis with AI-powered analytics,"
real-time dashboards, and data-driven insights. Build comprehensive KPI
frameworks, predictive models, and strategic recommendations. Use PROACTIVELY
for business intelligence or strategic analysis.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/busybox-on-windows/SKILL.md b/web-app/public/skills/busybox-on-windows/SKILL.md
index 81f17cbd..66e1c791 100644
--- a/web-app/public/skills/busybox-on-windows/SKILL.md
+++ b/web-app/public/skills/busybox-on-windows/SKILL.md
@@ -1,7 +1,9 @@
---
name: busybox-on-windows
-description: How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
+description: "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows."
license: MIT
+risk: unknown
+source: community
---
BusyBox is a single binary that implements many common Unix tools.
@@ -28,3 +30,6 @@ If you need to run a UNIX command under another CWD, then use the absolute path
Documentation: https://frippery.org/busybox/
Original BusyBox: https://busybox.net/
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/c-pro/SKILL.md b/web-app/public/skills/c-pro/SKILL.md
index 60df9fd3..eaeaa980 100644
--- a/web-app/public/skills/c-pro/SKILL.md
+++ b/web-app/public/skills/c-pro/SKILL.md
@@ -6,6 +6,8 @@ description: Write efficient C code with proper memory management, pointer
or system programming.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/c4-architecture-c4-architecture/SKILL.md b/web-app/public/skills/c4-architecture-c4-architecture/SKILL.md
index bf5386d9..b1bd200a 100644
--- a/web-app/public/skills/c4-architecture-c4-architecture/SKILL.md
+++ b/web-app/public/skills/c4-architecture-c4-architecture/SKILL.md
@@ -1,6 +1,8 @@
---
name: c4-architecture-c4-architecture
description: "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach."
+risk: unknown
+source: community
---
# C4 Architecture Documentation Workflow
diff --git a/web-app/public/skills/c4-code/SKILL.md b/web-app/public/skills/c4-code/SKILL.md
index 591d31c8..333ab01b 100644
--- a/web-app/public/skills/c4-code/SKILL.md
+++ b/web-app/public/skills/c4-code/SKILL.md
@@ -1,12 +1,14 @@
---
name: c4-code
-description: Expert C4 Code-level documentation specialist. Analyzes code
+description: "Expert C4 Code-level documentation specialist. Analyzes code"
directories to create comprehensive C4 code-level documentation including
function signatures, arguments, dependencies, and code structure. Use when
documenting code at the lowest C4 level for individual directories and code
modules.
metadata:
model: haiku
+risk: unknown
+source: community
---
# C4 Code Level: [Directory Name]
diff --git a/web-app/public/skills/c4-component/SKILL.md b/web-app/public/skills/c4-component/SKILL.md
index 72ad21dc..64c14978 100644
--- a/web-app/public/skills/c4-component/SKILL.md
+++ b/web-app/public/skills/c4-component/SKILL.md
@@ -1,12 +1,14 @@
---
name: c4-component
-description: Expert C4 Component-level documentation specialist. Synthesizes C4
+description: "Expert C4 Component-level documentation specialist. Synthesizes C4"
Code-level documentation into Component-level architecture, defining component
boundaries, interfaces, and relationships. Creates component diagrams and
documentation. Use when synthesizing code-level documentation into logical
components.
metadata:
model: sonnet
+risk: unknown
+source: community
---
# C4 Component Level: [Component Name]
@@ -49,8 +51,8 @@ metadata:
This component contains the following code-level elements:
-- [c4-code-file-1.md](./c4-code-file-1.md) - [Description]
-- [c4-code-file-2.md](./c4-code-file-2.md) - [Description]
+- c4-code-file-1.md - [Description]
+- c4-code-file-2.md - [Description]
## Interfaces
@@ -114,12 +116,12 @@ C4Component
### [Component 1]
- **Name**: [Component name]
- **Description**: [Short description]
-- **Documentation**: [c4-component-name-1.md](./c4-component-name-1.md)
+- **Documentation**: c4-component-name-1.md
### [Component 2]
- **Name**: [Component name]
- **Description**: [Short description]
-- **Documentation**: [c4-component-name-2.md](./c4-component-name-2.md)
+- **Documentation**: c4-component-name-2.md
## Component Relationships
[Mermaid diagram showing all components and their relationships]
diff --git a/web-app/public/skills/c4-container/SKILL.md b/web-app/public/skills/c4-container/SKILL.md
index 369da448..c41f6586 100644
--- a/web-app/public/skills/c4-container/SKILL.md
+++ b/web-app/public/skills/c4-container/SKILL.md
@@ -1,12 +1,14 @@
---
name: c4-container
-description: Expert C4 Container-level documentation specialist. Synthesizes
+description: "Expert C4 Container-level documentation specialist. Synthesizes"
Component-level documentation into Container-level architecture, mapping
components to deployment units, documenting container interfaces as APIs, and
creating container diagrams. Use when synthesizing components into deployment
containers and documenting system deployment architecture.
metadata:
model: sonnet
+risk: unknown
+source: community
---
# C4 Container Level: System Deployment
@@ -47,7 +49,7 @@ metadata:
This container deploys the following components:
- [Component Name]: [Description]
- - Documentation: [c4-component-name.md](./c4-component-name.md)
+ - Documentation: c4-component-name.md
## Interfaces
diff --git a/web-app/public/skills/c4-context/SKILL.md b/web-app/public/skills/c4-context/SKILL.md
index 630ad58f..cf5688d0 100644
--- a/web-app/public/skills/c4-context/SKILL.md
+++ b/web-app/public/skills/c4-context/SKILL.md
@@ -1,6 +1,6 @@
---
name: c4-context
-description: Expert C4 Context-level documentation specialist. Creates
+description: "Expert C4 Context-level documentation specialist. Creates"
high-level system context diagrams, documents personas, user journeys, system
features, and external dependencies. Synthesizes container and component
documentation with system documentation to create comprehensive context-level
@@ -8,6 +8,8 @@ description: Expert C4 Context-level documentation specialist. Creates
documentation.
metadata:
model: sonnet
+risk: unknown
+source: community
---
# C4 Context Level: System Context
@@ -86,8 +88,8 @@ metadata:
## Related Documentation
-- [Container Documentation](./c4-container.md)
-- [Component Documentation](./c4-component.md)
+- Container Documentation
+- Component Documentation
```
## Context Diagram Template
diff --git a/web-app/public/skills/cal-com-automation/SKILL.md b/web-app/public/skills/cal-com-automation/SKILL.md
index 22d57659..848b21e6 100644
--- a/web-app/public/skills/cal-com-automation/SKILL.md
+++ b/web-app/public/skills/cal-com-automation/SKILL.md
@@ -3,6 +3,8 @@ name: cal-com-automation
description: "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Cal.com Automation via Rube MCP
@@ -201,3 +203,6 @@ Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube M
| Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug |
| Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId |
| Get org ID | CAL_GET_ORGANIZATION_ID | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/calendly-automation/SKILL.md b/web-app/public/skills/calendly-automation/SKILL.md
index 0f864c0a..7cbf555e 100644
--- a/web-app/public/skills/calendly-automation/SKILL.md
+++ b/web-app/public/skills/calendly-automation/SKILL.md
@@ -3,6 +3,8 @@ name: calendly-automation
description: "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Calendly Automation via Rube MCP
@@ -209,3 +211,6 @@ Most Calendly list endpoints use token-based pagination:
| List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` |
| Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID |
| Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/canva-automation/SKILL.md b/web-app/public/skills/canva-automation/SKILL.md
index 05f8017e..f19be302 100644
--- a/web-app/public/skills/canva-automation/SKILL.md
+++ b/web-app/public/skills/canva-automation/SKILL.md
@@ -3,6 +3,8 @@ name: canva-automation
description: "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Canva Automation via Rube MCP
@@ -215,3 +217,6 @@ Many Canva operations are asynchronous:
| Move to folder | CANVA_MOVE_ITEM_TO_SPECIFIED_FOLDER | item_id, folder_id |
| List templates | CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST | (none) |
| Autofill template | CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB | brand_template_id, data |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/canvas-design/SKILL.md b/web-app/public/skills/canvas-design/SKILL.md
index 9f63fee8..836e9e5f 100644
--- a/web-app/public/skills/canvas-design/SKILL.md
+++ b/web-app/public/skills/canvas-design/SKILL.md
@@ -1,7 +1,9 @@
---
name: canvas-design
-description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
+description: "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
@@ -127,4 +129,7 @@ Take a second pass. Go back to the code and refine/polish further to make this a
## MULTI-PAGE OPTION
-To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.
\ No newline at end of file
+To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-backend-patterns/SKILL.md b/web-app/public/skills/cc-skill-backend-patterns/SKILL.md
index a31db2b7..bdebf29b 100644
--- a/web-app/public/skills/cc-skill-backend-patterns/SKILL.md
+++ b/web-app/public/skills/cc-skill-backend-patterns/SKILL.md
@@ -1,8 +1,10 @@
---
-name: backend-patterns
-description: Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
+name: cc-skill-backend-patterns
+description: "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes."
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# Backend Development Patterns
@@ -581,4 +583,7 @@ export async function GET(request: Request) {
}
```
-**Remember**: Backend patterns enable scalable, maintainable server-side applications. Choose patterns that fit your complexity level.
\ No newline at end of file
+**Remember**: Backend patterns enable scalable, maintainable server-side applications. Choose patterns that fit your complexity level.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-clickhouse-io/SKILL.md b/web-app/public/skills/cc-skill-clickhouse-io/SKILL.md
index ebb85249..8f362e47 100644
--- a/web-app/public/skills/cc-skill-clickhouse-io/SKILL.md
+++ b/web-app/public/skills/cc-skill-clickhouse-io/SKILL.md
@@ -1,8 +1,10 @@
---
-name: clickhouse-io
-description: ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
+name: cc-skill-clickhouse-io
+description: "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads."
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# ClickHouse Analytics Patterns
@@ -428,4 +430,7 @@ pgClient.on('notification', async (msg) => {
- Check merge operations
- Review slow query log
-**Remember**: ClickHouse excels at analytical workloads. Design tables for your query patterns, batch inserts, and leverage materialized views for real-time aggregations.
\ No newline at end of file
+**Remember**: ClickHouse excels at analytical workloads. Design tables for your query patterns, batch inserts, and leverage materialized views for real-time aggregations.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-coding-standards/SKILL.md b/web-app/public/skills/cc-skill-coding-standards/SKILL.md
index 03841e3f..39f61925 100644
--- a/web-app/public/skills/cc-skill-coding-standards/SKILL.md
+++ b/web-app/public/skills/cc-skill-coding-standards/SKILL.md
@@ -1,8 +1,10 @@
---
-name: coding-standards
-description: Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
+name: cc-skill-coding-standards
+description: "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development."
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# Coding Standards & Best Practices
@@ -519,4 +521,7 @@ if (retryCount > MAX_RETRIES) { }
setTimeout(callback, DEBOUNCE_DELAY_MS)
```
-**Remember**: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.
\ No newline at end of file
+**Remember**: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-continuous-learning/SKILL.md b/web-app/public/skills/cc-skill-continuous-learning/SKILL.md
index d8e11d19..63c21459 100644
--- a/web-app/public/skills/cc-skill-continuous-learning/SKILL.md
+++ b/web-app/public/skills/cc-skill-continuous-learning/SKILL.md
@@ -1,10 +1,15 @@
---
name: cc-skill-continuous-learning
-description: Development skill from everything-claude-code
+description: "Development skill from everything-claude-code"
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# cc-skill-continuous-learning
Development skill skill.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-frontend-patterns/SKILL.md b/web-app/public/skills/cc-skill-frontend-patterns/SKILL.md
index 372f0d2a..4226ec28 100644
--- a/web-app/public/skills/cc-skill-frontend-patterns/SKILL.md
+++ b/web-app/public/skills/cc-skill-frontend-patterns/SKILL.md
@@ -1,8 +1,10 @@
---
-name: frontend-patterns
-description: Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
+name: cc-skill-frontend-patterns
+description: "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices."
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# Frontend Development Patterns
@@ -630,4 +632,7 @@ export function Modal({ isOpen, onClose, children }: ModalProps) {
}
```
-**Remember**: Modern frontend patterns enable maintainable, performant user interfaces. Choose patterns that fit your project complexity.
\ No newline at end of file
+**Remember**: Modern frontend patterns enable maintainable, performant user interfaces. Choose patterns that fit your project complexity.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-project-guidelines-example/SKILL.md b/web-app/public/skills/cc-skill-project-guidelines-example/SKILL.md
index 89b7340f..d87166ff 100644
--- a/web-app/public/skills/cc-skill-project-guidelines-example/SKILL.md
+++ b/web-app/public/skills/cc-skill-project-guidelines-example/SKILL.md
@@ -1,8 +1,10 @@
---
name: cc-skill-project-guidelines-example
-description: Project Guidelines Skill (Example)
+description: "Project Guidelines Skill (Example)"
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# Project Guidelines Skill (Example)
diff --git a/web-app/public/skills/cc-skill-security-review/SKILL.md b/web-app/public/skills/cc-skill-security-review/SKILL.md
index d74c12a3..5b734954 100644
--- a/web-app/public/skills/cc-skill-security-review/SKILL.md
+++ b/web-app/public/skills/cc-skill-security-review/SKILL.md
@@ -1,8 +1,10 @@
---
-name: security-review
-description: Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
+name: cc-skill-security-review
+description: "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a..."
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# Security Review Skill
@@ -493,4 +495,7 @@ Before ANY production deployment:
---
-**Remember**: Security is not optional. One vulnerability can compromise the entire platform. When in doubt, err on the side of caution.
\ No newline at end of file
+**Remember**: Security is not optional. One vulnerability can compromise the entire platform. When in doubt, err on the side of caution.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cc-skill-strategic-compact/SKILL.md b/web-app/public/skills/cc-skill-strategic-compact/SKILL.md
index a128e02b..8372b80b 100644
--- a/web-app/public/skills/cc-skill-strategic-compact/SKILL.md
+++ b/web-app/public/skills/cc-skill-strategic-compact/SKILL.md
@@ -1,10 +1,15 @@
---
name: cc-skill-strategic-compact
-description: Development skill from everything-claude-code
+description: "Development skill from everything-claude-code"
author: affaan-m
version: "1.0"
+risk: unknown
+source: community
---
# cc-skill-strategic-compact
Development skill skill.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cdk-patterns/SKILL.md b/web-app/public/skills/cdk-patterns/SKILL.md
new file mode 100644
index 00000000..d3d0c820
--- /dev/null
+++ b/web-app/public/skills/cdk-patterns/SKILL.md
@@ -0,0 +1,79 @@
+---
+name: cdk-patterns
+description: "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs."
+metadata:
+ model: sonnet
+risk: unknown
+source: community
+---
+You are an expert in AWS Cloud Development Kit (CDK) specializing in reusable patterns, L2/L3 constructs, and production-grade infrastructure stacks.
+
+## Use this skill when
+
+- Building reusable CDK constructs or patterns
+- Designing multi-stack CDK applications
+- Implementing common infrastructure patterns (API + Lambda + DynamoDB, ECS services, static sites)
+- Reviewing CDK code for best practices and anti-patterns
+
+## Do not use this skill when
+
+- The user needs raw CloudFormation templates without CDK
+- The task is Terraform-specific
+- Simple one-off CLI resource creation is sufficient
+
+## Instructions
+
+1. Identify the infrastructure pattern needed (e.g., serverless API, container service, data pipeline).
+2. Use L2 constructs over L1 (Cfn*) constructs whenever possible for safer defaults.
+3. Apply the principle of least privilege for all IAM roles and policies.
+4. Use `RemovalPolicy` and `Tags` appropriately for production readiness.
+5. Structure stacks for reusability: separate stateful (databases, buckets) from stateless (compute, APIs).
+6. Enable monitoring by default (CloudWatch alarms, X-Ray tracing).
+
+## Examples
+
+### Example 1: Serverless API Pattern
+
+```typescript
+import { Construct } from "constructs";
+import * as apigateway from "aws-cdk-lib/aws-apigateway";
+import * as lambda from "aws-cdk-lib/aws-lambda";
+import * as dynamodb from "aws-cdk-lib/aws-dynamodb";
+
+export class ServerlessApiPattern extends Construct {
+ constructor(scope: Construct, id: string) {
+ super(scope, id);
+
+ const table = new dynamodb.Table(this, "Table", {
+ partitionKey: { name: "pk", type: dynamodb.AttributeType.STRING },
+ billingMode: dynamodb.BillingMode.PAY_PER_REQUEST,
+ removalPolicy: cdk.RemovalPolicy.RETAIN,
+ });
+
+ const handler = new lambda.Function(this, "Handler", {
+ runtime: lambda.Runtime.NODEJS_20_X,
+ handler: "index.handler",
+ code: lambda.Code.fromAsset("lambda"),
+ environment: { TABLE_NAME: table.tableName },
+ tracing: lambda.Tracing.ACTIVE,
+ });
+
+ table.grantReadWriteData(handler);
+
+ new apigateway.LambdaRestApi(this, "Api", { handler });
+ }
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `cdk.Tags.of(this).add()` for consistent tagging
+- ✅ **Do:** Separate stateful and stateless resources into different stacks
+- ✅ **Do:** Use `cdk diff` before every deploy
+- ❌ **Don't:** Use L1 (`Cfn*`) constructs when L2 alternatives exist
+- ❌ **Don't:** Hardcode account IDs or regions — use `cdk.Aws.ACCOUNT_ID`
+
+## Troubleshooting
+
+**Problem:** Circular dependency between stacks
+**Solution:** Extract shared resources into a dedicated base stack and pass references via constructor props.
diff --git a/web-app/public/skills/changelog-automation/SKILL.md b/web-app/public/skills/changelog-automation/SKILL.md
index c36afe72..31e6fc7a 100644
--- a/web-app/public/skills/changelog-automation/SKILL.md
+++ b/web-app/public/skills/changelog-automation/SKILL.md
@@ -1,6 +1,8 @@
---
name: changelog-automation
-description: Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
+description: "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions."
+risk: unknown
+source: community
---
# Changelog Automation
diff --git a/web-app/public/skills/cicd-automation-workflow-automate/SKILL.md b/web-app/public/skills/cicd-automation-workflow-automate/SKILL.md
index 2567dcdc..47e3679b 100644
--- a/web-app/public/skills/cicd-automation-workflow-automate/SKILL.md
+++ b/web-app/public/skills/cicd-automation-workflow-automate/SKILL.md
@@ -1,6 +1,8 @@
---
name: cicd-automation-workflow-automate
-description: "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security."
+description: "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i..."
+risk: unknown
+source: community
---
# Workflow Automation
diff --git a/web-app/public/skills/circleci-automation/SKILL.md b/web-app/public/skills/circleci-automation/SKILL.md
index bc2ee72e..076d4ccb 100644
--- a/web-app/public/skills/circleci-automation/SKILL.md
+++ b/web-app/public/skills/circleci-automation/SKILL.md
@@ -3,6 +3,8 @@ name: circleci-automation
description: "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# CircleCI Automation via Rube MCP
@@ -175,3 +177,6 @@ Format: {vcs_type}/{org_name}/{repo_name}
| Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number |
| Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number |
| Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/claude-code-guide/SKILL.md b/web-app/public/skills/claude-code-guide/SKILL.md
index 45a10eb9..4d5b41eb 100644
--- a/web-app/public/skills/claude-code-guide/SKILL.md
+++ b/web-app/public/skills/claude-code-guide/SKILL.md
@@ -1,6 +1,8 @@
---
-name: Claude Code Guide
-description: Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.
+name: claude-code-guide
+description: "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit..."
+risk: unknown
+source: community
---
# Claude Code Guide
@@ -66,3 +68,6 @@ If the agent is stuck or behaving unexpectedly:
## Reference
Based on [Claude Code Guide by zebbern](https://github.com/zebbern/claude-code-guide).
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/claude-d3js-skill/SKILL.md b/web-app/public/skills/claude-d3js-skill/SKILL.md
index 20234426..bb93229a 100644
--- a/web-app/public/skills/claude-d3js-skill/SKILL.md
+++ b/web-app/public/skills/claude-d3js-skill/SKILL.md
@@ -1,6 +1,8 @@
---
-name: d3-viz
-description: Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.
+name: claude-d3js-skill
+description: "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua..."
+risk: unknown
+source: community
---
# D3.js Visualisation
diff --git a/web-app/public/skills/clean-code/SKILL.md b/web-app/public/skills/clean-code/SKILL.md
index 931ed815..dd5367ca 100644
--- a/web-app/public/skills/clean-code/SKILL.md
+++ b/web-app/public/skills/clean-code/SKILL.md
@@ -1,6 +1,6 @@
---
name: clean-code
-description: "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design."
+description: "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio..."
user-invocable: true
risk: safe
source: "ClawForge (https://github.com/jackjin1997/ClawForge)"
diff --git a/web-app/public/skills/clerk-auth/SKILL.md b/web-app/public/skills/clerk-auth/SKILL.md
index ff54840a..57f16a2f 100644
--- a/web-app/public/skills/clerk-auth/SKILL.md
+++ b/web-app/public/skills/clerk-auth/SKILL.md
@@ -2,6 +2,7 @@
name: clerk-auth
description: "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Clerk Authentication
@@ -54,3 +55,6 @@ Key functions:
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | medium | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/clickup-automation/SKILL.md b/web-app/public/skills/clickup-automation/SKILL.md
index 91c2c384..d3ca7bf1 100644
--- a/web-app/public/skills/clickup-automation/SKILL.md
+++ b/web-app/public/skills/clickup-automation/SKILL.md
@@ -3,6 +3,8 @@ name: clickup-automation
description: "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# ClickUp Automation via Rube MCP
@@ -232,3 +234,6 @@ Always resolve names to IDs through the hierarchy:
| List user groups | `CLICKUP_GET_TEAMS` | `team_id` |
| Get user details | `CLICKUP_GET_USER` | `team_id`, `user_id` |
| Custom roles | `CLICKUP_GET_CUSTOM_ROLES` | `team_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/close-automation/SKILL.md b/web-app/public/skills/close-automation/SKILL.md
index 4453b108..e0089566 100644
--- a/web-app/public/skills/close-automation/SKILL.md
+++ b/web-app/public/skills/close-automation/SKILL.md
@@ -3,6 +3,8 @@ name: close-automation
description: "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Close CRM Automation via Rube MCP
@@ -210,3 +212,6 @@ Close data model:
| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |
| Get note | CLOSE_GET_NOTE | note_id |
| Delete call | CLOSE_DELETE_CALL | call_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cloud-architect/SKILL.md b/web-app/public/skills/cloud-architect/SKILL.md
index 0b677a8c..e3679697 100644
--- a/web-app/public/skills/cloud-architect/SKILL.md
+++ b/web-app/public/skills/cloud-architect/SKILL.md
@@ -1,6 +1,6 @@
---
name: cloud-architect
-description: Expert cloud architect specializing in AWS/Azure/GCP multi-cloud
+description: "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud"
infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost
optimization, and modern architectural patterns. Masters serverless,
microservices, security, compliance, and disaster recovery. Use PROACTIVELY
@@ -8,6 +8,8 @@ description: Expert cloud architect specializing in AWS/Azure/GCP multi-cloud
strategies.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/cloud-devops/SKILL.md b/web-app/public/skills/cloud-devops/SKILL.md
new file mode 100644
index 00000000..7897dfd8
--- /dev/null
+++ b/web-app/public/skills/cloud-devops/SKILL.md
@@ -0,0 +1,236 @@
+---
+name: cloud-devops
+description: "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development."
+source: personal
+risk: safe
+domain: cloud-devops
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Cloud/DevOps Workflow Bundle
+
+## Overview
+
+Comprehensive cloud and DevOps workflow for infrastructure provisioning, container orchestration, CI/CD pipelines, monitoring, and cloud-native application development.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Setting up cloud infrastructure
+- Implementing CI/CD pipelines
+- Deploying Kubernetes applications
+- Configuring monitoring and observability
+- Managing cloud costs
+- Implementing DevOps practices
+
+## Workflow Phases
+
+### Phase 1: Cloud Infrastructure Setup
+
+#### Skills to Invoke
+- `cloud-architect` - Cloud architecture
+- `aws-skills` - AWS development
+- `azure-functions` - Azure development
+- `gcp-cloud-run` - GCP development
+- `terraform-skill` - Terraform IaC
+- `terraform-specialist` - Advanced Terraform
+
+#### Actions
+1. Design cloud architecture
+2. Set up accounts and billing
+3. Configure networking
+4. Provision resources
+5. Set up IAM
+
+#### Copy-Paste Prompts
+```
+Use @cloud-architect to design multi-cloud architecture
+```
+
+```
+Use @terraform-skill to provision AWS infrastructure
+```
+
+### Phase 2: Container Orchestration
+
+#### Skills to Invoke
+- `kubernetes-architect` - Kubernetes architecture
+- `docker-expert` - Docker containerization
+- `helm-chart-scaffolding` - Helm charts
+- `k8s-manifest-generator` - K8s manifests
+- `k8s-security-policies` - K8s security
+
+#### Actions
+1. Design container architecture
+2. Create Dockerfiles
+3. Build container images
+4. Write K8s manifests
+5. Deploy to cluster
+6. Configure networking
+
+#### Copy-Paste Prompts
+```
+Use @kubernetes-architect to design K8s architecture
+```
+
+```
+Use @docker-expert to containerize application
+```
+
+```
+Use @helm-chart-scaffolding to create Helm chart
+```
+
+### Phase 3: CI/CD Implementation
+
+#### Skills to Invoke
+- `deployment-engineer` - Deployment engineering
+- `cicd-automation-workflow-automate` - CI/CD automation
+- `github-actions-templates` - GitHub Actions
+- `gitlab-ci-patterns` - GitLab CI
+- `deployment-pipeline-design` - Pipeline design
+
+#### Actions
+1. Design deployment pipeline
+2. Configure build automation
+3. Set up test automation
+4. Configure deployment stages
+5. Implement rollback strategies
+6. Set up notifications
+
+#### Copy-Paste Prompts
+```
+Use @cicd-automation-workflow-automate to set up CI/CD pipeline
+```
+
+```
+Use @github-actions-templates to create GitHub Actions workflow
+```
+
+### Phase 4: Monitoring and Observability
+
+#### Skills to Invoke
+- `observability-engineer` - Observability engineering
+- `grafana-dashboards` - Grafana dashboards
+- `prometheus-configuration` - Prometheus setup
+- `datadog-automation` - Datadog integration
+- `sentry-automation` - Sentry error tracking
+
+#### Actions
+1. Design monitoring strategy
+2. Set up metrics collection
+3. Configure log aggregation
+4. Implement distributed tracing
+5. Create dashboards
+6. Set up alerts
+
+#### Copy-Paste Prompts
+```
+Use @observability-engineer to set up observability stack
+```
+
+```
+Use @grafana-dashboards to create monitoring dashboards
+```
+
+### Phase 5: Cloud Security
+
+#### Skills to Invoke
+- `cloud-penetration-testing` - Cloud pentesting
+- `aws-penetration-testing` - AWS security
+- `k8s-security-policies` - K8s security
+- `secrets-management` - Secrets management
+- `mtls-configuration` - mTLS setup
+
+#### Actions
+1. Assess cloud security
+2. Configure security groups
+3. Set up secrets management
+4. Implement network policies
+5. Configure encryption
+6. Set up audit logging
+
+#### Copy-Paste Prompts
+```
+Use @cloud-penetration-testing to assess cloud security
+```
+
+```
+Use @secrets-management to configure secrets
+```
+
+### Phase 6: Cost Optimization
+
+#### Skills to Invoke
+- `cost-optimization` - Cloud cost optimization
+- `database-cloud-optimization-cost-optimize` - Database cost optimization
+
+#### Actions
+1. Analyze cloud spending
+2. Identify optimization opportunities
+3. Right-size resources
+4. Implement auto-scaling
+5. Use reserved instances
+6. Set up cost alerts
+
+#### Copy-Paste Prompts
+```
+Use @cost-optimization to reduce cloud costs
+```
+
+### Phase 7: Disaster Recovery
+
+#### Skills to Invoke
+- `incident-responder` - Incident response
+- `incident-runbook-templates` - Runbook creation
+- `postmortem-writing` - Postmortem documentation
+
+#### Actions
+1. Design DR strategy
+2. Set up backups
+3. Create runbooks
+4. Test failover
+5. Document procedures
+6. Train team
+
+#### Copy-Paste Prompts
+```
+Use @incident-runbook-templates to create runbooks
+```
+
+## Cloud Provider Workflows
+
+### AWS
+```
+Skills: aws-skills, aws-serverless, aws-penetration-testing
+Services: EC2, Lambda, S3, RDS, ECS, EKS
+```
+
+### Azure
+```
+Skills: azure-functions, azure-ai-projects-py, azure-monitor-opentelemetry-py
+Services: Functions, App Service, AKS, Cosmos DB
+```
+
+### GCP
+```
+Skills: gcp-cloud-run
+Services: Cloud Run, GKE, Cloud Functions, BigQuery
+```
+
+## Quality Gates
+
+- [ ] Infrastructure provisioned
+- [ ] CI/CD pipeline working
+- [ ] Monitoring configured
+- [ ] Security measures in place
+- [ ] Cost optimization applied
+- [ ] DR procedures documented
+
+## Related Workflow Bundles
+
+- `development` - Application development
+- `security-audit` - Security testing
+- `database` - Database operations
+- `testing-qa` - Testing workflows
diff --git a/web-app/public/skills/cloud-penetration-testing/SKILL.md b/web-app/public/skills/cloud-penetration-testing/SKILL.md
index dd91a0ae..dfa1e408 100644
--- a/web-app/public/skills/cloud-penetration-testing/SKILL.md
+++ b/web-app/public/skills/cloud-penetration-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Cloud Penetration Testing
-description: This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
+name: cloud-penetration-testing
+description: "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Cloud Penetration Testing
@@ -499,3 +501,6 @@ gcloud beta compute ssh instance-name --zone us-central1-a --project target-proj
## References
- [Advanced Cloud Scripts](references/advanced-cloud-scripts.md) - Azure Automation runbooks, Function Apps enumeration, AWS data exfiltration, GCP advanced exploitation
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cloudformation-best-practices/SKILL.md b/web-app/public/skills/cloudformation-best-practices/SKILL.md
new file mode 100644
index 00000000..ad7a3b56
--- /dev/null
+++ b/web-app/public/skills/cloudformation-best-practices/SKILL.md
@@ -0,0 +1,80 @@
+---
+name: cloudformation-best-practices
+description: "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates."
+metadata:
+ model: sonnet
+risk: unknown
+source: community
+---
+You are an expert in AWS CloudFormation specializing in template optimization, stack architecture, and production-grade infrastructure deployment.
+
+## Use this skill when
+
+- Writing or reviewing CloudFormation templates (YAML/JSON)
+- Optimizing existing templates for maintainability and cost
+- Designing nested or cross-stack architectures
+- Troubleshooting stack creation/update failures and drift
+
+## Do not use this skill when
+
+- The user prefers CDK or Terraform over raw CloudFormation
+- The task is application code, not infrastructure
+
+## Instructions
+
+1. Use YAML over JSON for readability.
+2. Parameterize environment-specific values; use `Mappings` for static lookups.
+3. Apply `DeletionPolicy: Retain` on stateful resources (RDS, S3, DynamoDB).
+4. Use `Conditions` to support multi-environment templates.
+5. Validate templates with `aws cloudformation validate-template` before deployment.
+6. Prefer `!Sub` over `!Join` for string interpolation.
+
+## Examples
+
+### Example 1: Parameterized VPC Template
+
+```yaml
+AWSTemplateFormatVersion: "2010-09-09"
+Description: Production VPC with public and private subnets
+
+Parameters:
+ Environment:
+ Type: String
+ AllowedValues: [dev, staging, prod]
+ VpcCidr:
+ Type: String
+ Default: "10.0.0.0/16"
+
+Conditions:
+ IsProd: !Equals [!Ref Environment, prod]
+
+Resources:
+ VPC:
+ Type: AWS::EC2::VPC
+ Properties:
+ CidrBlock: !Ref VpcCidr
+ EnableDnsSupport: true
+ EnableDnsHostnames: true
+ Tags:
+ - Key: Name
+ Value: !Sub "${Environment}-vpc"
+
+Outputs:
+ VpcId:
+ Value: !Ref VPC
+ Export:
+ Name: !Sub "${Environment}-VpcId"
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `Outputs` with `Export` for cross-stack references
+- ✅ **Do:** Add `DeletionPolicy` and `UpdateReplacePolicy` on stateful resources
+- ✅ **Do:** Use `cfn-lint` and `cfn-nag` in CI pipelines
+- ❌ **Don't:** Hardcode ARNs or account IDs — use `!Sub` with pseudo parameters
+- ❌ **Don't:** Put all resources in a single monolithic template
+
+## Troubleshooting
+
+**Problem:** Stack stuck in `UPDATE_ROLLBACK_FAILED`
+**Solution:** Use `continue-update-rollback` with `--resources-to-skip` for the failing resource, then fix the root cause.
diff --git a/web-app/public/skills/coda-automation/SKILL.md b/web-app/public/skills/coda-automation/SKILL.md
index 55a0eba1..1cdaef6a 100644
--- a/web-app/public/skills/coda-automation/SKILL.md
+++ b/web-app/public/skills/coda-automation/SKILL.md
@@ -3,6 +3,8 @@ name: coda-automation
description: "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Coda Automation via Rube MCP
@@ -239,3 +241,6 @@ Automate Coda document and data operations through Composio's Coda toolkit via R
| Publish doc | CODA_PUBLISH_DOC | docId, slug |
| Unpublish doc | CODA_UNPUBLISH_DOC | docId |
| List packs | CODA_LIST_PACKS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/code-documentation-code-explain/SKILL.md b/web-app/public/skills/code-documentation-code-explain/SKILL.md
index 1b291738..da6695ef 100644
--- a/web-app/public/skills/code-documentation-code-explain/SKILL.md
+++ b/web-app/public/skills/code-documentation-code-explain/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-documentation-code-explain
-description: "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations."
+description: "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl..."
+risk: unknown
+source: community
---
# Code Explanation and Analysis
diff --git a/web-app/public/skills/code-documentation-doc-generate/SKILL.md b/web-app/public/skills/code-documentation-doc-generate/SKILL.md
index db9900b0..8cfdc185 100644
--- a/web-app/public/skills/code-documentation-doc-generate/SKILL.md
+++ b/web-app/public/skills/code-documentation-doc-generate/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-documentation-doc-generate
-description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices."
+description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI..."
+risk: unknown
+source: community
---
# Automated Documentation Generation
diff --git a/web-app/public/skills/code-documentation-doc-generate/resources/implementation-playbook.md b/web-app/public/skills/code-documentation-doc-generate/resources/implementation-playbook.md
index b361f364..e1c4f9d9 100644
--- a/web-app/public/skills/code-documentation-doc-generate/resources/implementation-playbook.md
+++ b/web-app/public/skills/code-documentation-doc-generate/resources/implementation-playbook.md
@@ -359,7 +359,7 @@ pytest --cov=your_package
## License
-This project is licensed under the ${LICENSE} License - see the [LICENSE](LICENSE) file for details.
+This project is licensed under the ${LICENSE} License - see the LICENSE file for details.
```
### Example 5: Function Documentation Generator
diff --git a/web-app/public/skills/code-refactoring-context-restore/SKILL.md b/web-app/public/skills/code-refactoring-context-restore/SKILL.md
index 6837a692..dd80e2c8 100644
--- a/web-app/public/skills/code-refactoring-context-restore/SKILL.md
+++ b/web-app/public/skills/code-refactoring-context-restore/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-refactoring-context-restore
description: "Use when working with code refactoring context restore"
+risk: unknown
+source: community
---
# Context Restoration: Advanced Semantic Memory Rehydration
diff --git a/web-app/public/skills/code-refactoring-refactor-clean/SKILL.md b/web-app/public/skills/code-refactoring-refactor-clean/SKILL.md
index cfe8ab1b..2233d22d 100644
--- a/web-app/public/skills/code-refactoring-refactor-clean/SKILL.md
+++ b/web-app/public/skills/code-refactoring-refactor-clean/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-refactoring-refactor-clean
-description: "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance."
+description: "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its..."
+risk: unknown
+source: community
---
# Refactor and Clean Code
diff --git a/web-app/public/skills/code-refactoring-tech-debt/SKILL.md b/web-app/public/skills/code-refactoring-tech-debt/SKILL.md
index fc57c10a..11970db8 100644
--- a/web-app/public/skills/code-refactoring-tech-debt/SKILL.md
+++ b/web-app/public/skills/code-refactoring-tech-debt/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-refactoring-tech-debt
description: "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti"
+risk: unknown
+source: community
---
# Technical Debt Analysis and Remediation
diff --git a/web-app/public/skills/code-review-ai-ai-review/SKILL.md b/web-app/public/skills/code-review-ai-ai-review/SKILL.md
index 918e99e2..502aebbb 100644
--- a/web-app/public/skills/code-review-ai-ai-review/SKILL.md
+++ b/web-app/public/skills/code-review-ai-ai-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-review-ai-ai-review
description: "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C"
+risk: unknown
+source: community
---
# AI-Powered Code Review Specialist
diff --git a/web-app/public/skills/code-review-checklist/SKILL.md b/web-app/public/skills/code-review-checklist/SKILL.md
index a00a47b5..527eb2e4 100644
--- a/web-app/public/skills/code-review-checklist/SKILL.md
+++ b/web-app/public/skills/code-review-checklist/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-review-checklist
description: "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability"
+risk: unknown
+source: community
---
# Code Review Checklist
diff --git a/web-app/public/skills/code-review-excellence/SKILL.md b/web-app/public/skills/code-review-excellence/SKILL.md
index d2972e54..d3ad8825 100644
--- a/web-app/public/skills/code-review-excellence/SKILL.md
+++ b/web-app/public/skills/code-review-excellence/SKILL.md
@@ -1,6 +1,8 @@
---
name: code-review-excellence
-description: Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
+description: "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing..."
+risk: unknown
+source: community
---
# Code Review Excellence
diff --git a/web-app/public/skills/code-reviewer/SKILL.md b/web-app/public/skills/code-reviewer/SKILL.md
index 98ddda1f..335740f8 100644
--- a/web-app/public/skills/code-reviewer/SKILL.md
+++ b/web-app/public/skills/code-reviewer/SKILL.md
@@ -7,6 +7,8 @@ description: Elite code review expert specializing in modern AI-powered code
quality assurance.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/codebase-cleanup-deps-audit/SKILL.md b/web-app/public/skills/codebase-cleanup-deps-audit/SKILL.md
index ae7ecadd..e03c44bc 100644
--- a/web-app/public/skills/codebase-cleanup-deps-audit/SKILL.md
+++ b/web-app/public/skills/codebase-cleanup-deps-audit/SKILL.md
@@ -1,6 +1,8 @@
---
name: codebase-cleanup-deps-audit
-description: "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies."
+description: "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,..."
+risk: unknown
+source: community
---
# Dependency Audit and Security Analysis
diff --git a/web-app/public/skills/codebase-cleanup-refactor-clean/SKILL.md b/web-app/public/skills/codebase-cleanup-refactor-clean/SKILL.md
index b4889f0b..89974ad3 100644
--- a/web-app/public/skills/codebase-cleanup-refactor-clean/SKILL.md
+++ b/web-app/public/skills/codebase-cleanup-refactor-clean/SKILL.md
@@ -1,6 +1,8 @@
---
name: codebase-cleanup-refactor-clean
-description: "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance."
+description: "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its..."
+risk: unknown
+source: community
---
# Refactor and Clean Code
diff --git a/web-app/public/skills/codebase-cleanup-tech-debt/SKILL.md b/web-app/public/skills/codebase-cleanup-tech-debt/SKILL.md
index be3ff3d1..85b1d553 100644
--- a/web-app/public/skills/codebase-cleanup-tech-debt/SKILL.md
+++ b/web-app/public/skills/codebase-cleanup-tech-debt/SKILL.md
@@ -1,6 +1,8 @@
---
name: codebase-cleanup-tech-debt
description: "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti"
+risk: unknown
+source: community
---
# Technical Debt Analysis and Remediation
diff --git a/web-app/public/skills/codex-review/SKILL.md b/web-app/public/skills/codex-review/SKILL.md
index 9bea297d..c2aff284 100644
--- a/web-app/public/skills/codex-review/SKILL.md
+++ b/web-app/public/skills/codex-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: codex-review
-description: Professional code review with auto CHANGELOG generation, integrated with Codex AI
+description: "Professional code review with auto CHANGELOG generation, integrated with Codex AI"
+risk: unknown
+source: community
---
# codex-review
diff --git a/web-app/public/skills/commit/SKILL.md b/web-app/public/skills/commit/SKILL.md
index 7e0846cb..d483b603 100644
--- a/web-app/public/skills/commit/SKILL.md
+++ b/web-app/public/skills/commit/SKILL.md
@@ -1,6 +1,6 @@
---
name: commit
-description: "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references."
+description: "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re..."
source: "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit"
risk: safe
---
diff --git a/web-app/public/skills/competitive-landscape/SKILL.md b/web-app/public/skills/competitive-landscape/SKILL.md
index d08144f6..70510375 100644
--- a/web-app/public/skills/competitive-landscape/SKILL.md
+++ b/web-app/public/skills/competitive-landscape/SKILL.md
@@ -1,11 +1,13 @@
---
name: competitive-landscape
-description: This skill should be used when the user asks to "analyze
+description: "This skill should be used when the user asks to \\\"analyze"
competitors", "assess competitive landscape", "identify differentiation",
"evaluate market positioning", "apply Porter's Five Forces", or requests
competitive strategy analysis.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Competitive Landscape Analysis
diff --git a/web-app/public/skills/competitor-alternatives/SKILL.md b/web-app/public/skills/competitor-alternatives/SKILL.md
index 9cf4083a..373df22a 100644
--- a/web-app/public/skills/competitor-alternatives/SKILL.md
+++ b/web-app/public/skills/competitor-alternatives/SKILL.md
@@ -1,6 +1,8 @@
---
name: competitor-alternatives
-description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables."
+description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa..."
+risk: unknown
+source: community
---
# Competitor & Alternative Pages
@@ -748,3 +750,6 @@ If you need more context:
- **copywriting**: For writing compelling comparison copy
- **seo-audit**: For optimizing competitor pages
- **schema-markup**: For FAQ and comparison schema
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/comprehensive-review-full-review/SKILL.md b/web-app/public/skills/comprehensive-review-full-review/SKILL.md
index ec52bb9c..f0c4d80e 100644
--- a/web-app/public/skills/comprehensive-review-full-review/SKILL.md
+++ b/web-app/public/skills/comprehensive-review-full-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: comprehensive-review-full-review
description: "Use when working with comprehensive review full review"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/comprehensive-review-pr-enhance/SKILL.md b/web-app/public/skills/comprehensive-review-pr-enhance/SKILL.md
index 8ed009c0..260a7e4e 100644
--- a/web-app/public/skills/comprehensive-review-pr-enhance/SKILL.md
+++ b/web-app/public/skills/comprehensive-review-pr-enhance/SKILL.md
@@ -1,6 +1,8 @@
---
name: comprehensive-review-pr-enhance
-description: "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability."
+description: "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e..."
+risk: unknown
+source: community
---
# Pull Request Enhancement
diff --git a/web-app/public/skills/computer-use-agents/SKILL.md b/web-app/public/skills/computer-use-agents/SKILL.md
index ab0daa87..11804157 100644
--- a/web-app/public/skills/computer-use-agents/SKILL.md
+++ b/web-app/public/skills/computer-use-agents/SKILL.md
@@ -1,7 +1,8 @@
---
name: computer-use-agents
-description: "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when: computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation."
+description: "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Computer Use Agents
@@ -313,3 +314,6 @@ class AnthropicComputerUse:
| Issue | high | ## Implement context management |
| Issue | high | ## Monitor and limit costs |
| Issue | critical | ## ALWAYS use sandboxing |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/computer-vision-expert/SKILL.md b/web-app/public/skills/computer-vision-expert/SKILL.md
index eebb5d11..7cb5bc81 100644
--- a/web-app/public/skills/computer-vision-expert/SKILL.md
+++ b/web-app/public/skills/computer-vision-expert/SKILL.md
@@ -1,6 +1,8 @@
---
name: computer-vision-expert
-description: SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.
+description: "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis."
+risk: unknown
+source: community
---
# Computer Vision Expert (SOTA 2026)
diff --git a/web-app/public/skills/concise-planning/SKILL.md b/web-app/public/skills/concise-planning/SKILL.md
index 51746315..aa057bdb 100644
--- a/web-app/public/skills/concise-planning/SKILL.md
+++ b/web-app/public/skills/concise-planning/SKILL.md
@@ -1,6 +1,8 @@
---
name: concise-planning
-description: Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
+description: "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist."
+risk: unknown
+source: community
---
# Concise Planning
@@ -60,3 +62,6 @@ Use the following structure:
- **Atomic**: Each step should be a single logical unit of work.
- **Verb-first**: "Add...", "Refactor...", "Verify...".
- **Concrete**: Name specific files or modules when possible.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/conductor-implement/SKILL.md b/web-app/public/skills/conductor-implement/SKILL.md
index cc406268..b03b98b7 100644
--- a/web-app/public/skills/conductor-implement/SKILL.md
+++ b/web-app/public/skills/conductor-implement/SKILL.md
@@ -1,8 +1,10 @@
---
name: conductor-implement
-description: Execute tasks from a track's implementation plan following TDD workflow
+description: "Execute tasks from a track's implementation plan following TDD workflow"
metadata:
argument-hint: "[track-id] [--task X.Y] [--phase N]"
+risk: unknown
+source: community
---
# Implement Track
diff --git a/web-app/public/skills/conductor-manage/SKILL.md b/web-app/public/skills/conductor-manage/SKILL.md
index 9d82cdf8..18dcf7f1 100644
--- a/web-app/public/skills/conductor-manage/SKILL.md
+++ b/web-app/public/skills/conductor-manage/SKILL.md
@@ -3,6 +3,8 @@ name: conductor-manage
description: "Manage track lifecycle: archive, restore, delete, rename, and cleanup"
metadata:
argument-hint: "[--archive | --restore | --delete | --rename | --list | --cleanup]"
+risk: unknown
+source: community
---
# Track Manager
diff --git a/web-app/public/skills/conductor-manage/resources/implementation-playbook.md b/web-app/public/skills/conductor-manage/resources/implementation-playbook.md
index 8b4c3f51..4c54396d 100644
--- a/web-app/public/skills/conductor-manage/resources/implementation-playbook.md
+++ b/web-app/public/skills/conductor-manage/resources/implementation-playbook.md
@@ -299,7 +299,7 @@ Type 'YES' to proceed, or anything else to cancel:
**Reason:** {reason}
**Archived:** YYYY-MM-DD
- **Folder:** [./tracks/\_archive/{track-id}/](./tracks/_archive/{track-id}/)
+ **Folder:** ./tracks/\_archive/{track-id}/
```
5. Git commit:
diff --git a/web-app/public/skills/conductor-new-track/SKILL.md b/web-app/public/skills/conductor-new-track/SKILL.md
index d4e00b32..32364038 100644
--- a/web-app/public/skills/conductor-new-track/SKILL.md
+++ b/web-app/public/skills/conductor-new-track/SKILL.md
@@ -1,8 +1,10 @@
---
name: conductor-new-track
-description: Create a new track with specification and phased implementation plan
+description: "Create a new track with specification and phased implementation plan"
metadata:
argument-hint:
+risk: unknown
+source: community
---
# New Track
@@ -261,7 +263,7 @@ After spec approval, generate `conductor/tracks/{trackId}/plan.md`:
# Implementation Plan: {Track Title}
**Track ID:** {trackId}
-**Spec:** [spec.md](./spec.md)
+**Spec:** spec.md
**Created:** {YYYY-MM-DD}
**Status:** [ ] Not Started
@@ -385,8 +387,8 @@ After plan approval:
## Documents
- - [Specification](./spec.md)
- - [Implementation Plan](./plan.md)
+ - Specification
+ - Implementation Plan
## Progress
@@ -395,8 +397,8 @@ After plan approval:
## Quick Links
- - [Back to Tracks](../../tracks.md)
- - [Product Context](../../product.md)
+ - Back to Tracks
+ - Product Context
```
4. Register in `conductor/tracks.md`:
diff --git a/web-app/public/skills/conductor-revert/SKILL.md b/web-app/public/skills/conductor-revert/SKILL.md
index b00021b4..ba88b549 100644
--- a/web-app/public/skills/conductor-revert/SKILL.md
+++ b/web-app/public/skills/conductor-revert/SKILL.md
@@ -1,8 +1,10 @@
---
name: conductor-revert
-description: Git-aware undo by logical work unit (track, phase, or task)
+description: "Git-aware undo by logical work unit (track, phase, or task)"
metadata:
argument-hint: "[track-id | track-id:phase | track-id:task]"
+risk: unknown
+source: community
---
# Revert Track
diff --git a/web-app/public/skills/conductor-setup/SKILL.md b/web-app/public/skills/conductor-setup/SKILL.md
index 1e09a670..cd21bc30 100644
--- a/web-app/public/skills/conductor-setup/SKILL.md
+++ b/web-app/public/skills/conductor-setup/SKILL.md
@@ -1,9 +1,11 @@
---
name: conductor-setup
-description: Initialize project with Conductor artifacts (product definition,
+description: "Initialize project with Conductor artifacts (product definition,"
tech stack, workflow, style guides)
metadata:
argument-hint: "[--resume]"
+risk: unknown
+source: community
---
# Conductor Setup
@@ -308,11 +310,11 @@ Navigation hub for project context.
## Quick Links
-- [Product Definition](./product.md)
-- [Product Guidelines](./product-guidelines.md)
-- [Tech Stack](./tech-stack.md)
-- [Workflow](./workflow.md)
-- [Tracks](./tracks.md)
+- Product Definition
+- Product Guidelines
+- Tech Stack
+- Workflow
+- Tracks
## Active Tracks
diff --git a/web-app/public/skills/conductor-status/SKILL.md b/web-app/public/skills/conductor-status/SKILL.md
index aabcf2d1..bd9aaaa2 100644
--- a/web-app/public/skills/conductor-status/SKILL.md
+++ b/web-app/public/skills/conductor-status/SKILL.md
@@ -1,8 +1,10 @@
---
name: conductor-status
-description: Display project status, active tracks, and next actions
+description: "Display project status, active tracks, and next actions"
metadata:
argument-hint: "[track-id] [--detailed]"
+risk: unknown
+source: community
---
# Conductor Status
diff --git a/web-app/public/skills/conductor-validator/SKILL.md b/web-app/public/skills/conductor-validator/SKILL.md
index e011c453..e06ee2d7 100644
--- a/web-app/public/skills/conductor-validator/SKILL.md
+++ b/web-app/public/skills/conductor-validator/SKILL.md
@@ -1,12 +1,14 @@
---
name: conductor-validator
-description: Validates Conductor project artifacts for completeness,
+description: "Validates Conductor project artifacts for completeness,"
consistency, and correctness. Use after setup, when diagnosing issues, or
before implementation to verify project context.
allowed-tools: Read Glob Grep Bash
metadata:
model: opus
color: cyan
+risk: unknown
+source: community
---
# Check if conductor directory exists
diff --git a/web-app/public/skills/confluence-automation/SKILL.md b/web-app/public/skills/confluence-automation/SKILL.md
index 386798e2..60c1d37e 100644
--- a/web-app/public/skills/confluence-automation/SKILL.md
+++ b/web-app/public/skills/confluence-automation/SKILL.md
@@ -3,6 +3,8 @@ name: confluence-automation
description: "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Confluence Automation via Rube MCP
@@ -206,3 +208,6 @@ Confluence uses two pagination styles:
| Add label | `CONFLUENCE_ADD_CONTENT_LABEL` | content ID, label |
| Page versions | `CONFLUENCE_GET_PAGE_VERSIONS` | `id` |
| Space labels | `CONFLUENCE_GET_LABELS_FOR_SPACE` | space ID |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/content-creator/SKILL.md b/web-app/public/skills/content-creator/SKILL.md
index 0600addf..36b41962 100644
--- a/web-app/public/skills/content-creator/SKILL.md
+++ b/web-app/public/skills/content-creator/SKILL.md
@@ -1,6 +1,6 @@
---
name: content-creator
-description: Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.
+description: "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati..."
license: MIT
metadata:
version: 1.0.0
@@ -10,12 +10,18 @@ metadata:
updated: 2025-10-20
python-tools: brand_voice_analyzer.py, seo_optimizer.py
tech-stack: SEO, social-media-platforms
+risk: unknown
+source: community
---
# Content Creator
Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
+## When to Use
+
+Use this skill when writing blog posts, creating social media content, establishing brand voice, optimizing content for SEO, or planning content calendars.
+
## Keywords
content creation, blog posts, SEO, brand voice, social media, content calendar, marketing content, content strategy, content marketing, brand consistency, content optimization, social media marketing, content planning, blog writing, content frameworks, brand guidelines, social media strategy
diff --git a/web-app/public/skills/content-marketer/SKILL.md b/web-app/public/skills/content-marketer/SKILL.md
index 33228a9b..7feed188 100644
--- a/web-app/public/skills/content-marketer/SKILL.md
+++ b/web-app/public/skills/content-marketer/SKILL.md
@@ -1,12 +1,14 @@
---
name: content-marketer
-description: Elite content marketing strategist specializing in AI-powered
+description: "Elite content marketing strategist specializing in AI-powered"
content creation, omnichannel distribution, SEO optimization, and data-driven
performance marketing. Masters modern content tools, social media automation,
and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for
comprehensive content marketing.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/context-compression/SKILL.md b/web-app/public/skills/context-compression/SKILL.md
index 451993ae..d2fa3270 100644
--- a/web-app/public/skills/context-compression/SKILL.md
+++ b/web-app/public/skills/context-compression/SKILL.md
@@ -8,6 +8,10 @@ risk: safe
When agent sessions generate millions of tokens of conversation history, compression becomes mandatory. The naive approach is aggressive compression to minimize tokens per request. The correct optimization target is tokens per task: total tokens consumed to complete a task, including re-fetching costs when compression loses critical information.
+## When to Use
+
+Use this skill when designing or evaluating context compression for long-running agent sessions, when codebases exceed context windows, or when debugging agent memory/forgetting issues.
+
## When to Activate
Activate this skill when:
@@ -243,7 +247,7 @@ This skill connects to several others in the collection:
## References
Internal reference:
-- [Evaluation Framework Reference](./references/evaluation-framework.md) - Detailed probe types and scoring rubrics
+- Evaluation Framework Reference - Detailed probe types and scoring rubrics
Related skills in this collection:
- context-degradation - Understanding what compression prevents
diff --git a/web-app/public/skills/context-degradation/SKILL.md b/web-app/public/skills/context-degradation/SKILL.md
index eb5ccc7c..40acf9f6 100644
--- a/web-app/public/skills/context-degradation/SKILL.md
+++ b/web-app/public/skills/context-degradation/SKILL.md
@@ -216,7 +216,7 @@ This skill builds on context-fundamentals and should be studied after understand
## References
Internal reference:
-- [Degradation Patterns Reference](./references/patterns.md) - Detailed technical reference
+- Degradation Patterns Reference - Detailed technical reference
Related skills in this collection:
- context-fundamentals - Context basics
diff --git a/web-app/public/skills/context-driven-development/SKILL.md b/web-app/public/skills/context-driven-development/SKILL.md
index 2ed45732..5e52726e 100644
--- a/web-app/public/skills/context-driven-development/SKILL.md
+++ b/web-app/public/skills/context-driven-development/SKILL.md
@@ -1,10 +1,12 @@
---
name: context-driven-development
-description: Use this skill when working with Conductor's context-driven
+description: "Use this skill when working with Conductor's context-driven"
development methodology, managing project context artifacts, or understanding
the relationship between product.md, tech-stack.md, and workflow.md files.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Context-Driven Development
diff --git a/web-app/public/skills/context-fundamentals/SKILL.md b/web-app/public/skills/context-fundamentals/SKILL.md
index a142f718..3078c0cd 100644
--- a/web-app/public/skills/context-fundamentals/SKILL.md
+++ b/web-app/public/skills/context-fundamentals/SKILL.md
@@ -171,7 +171,7 @@ This skill provides foundational context that all other skills build upon. It sh
## References
Internal reference:
-- [Context Components Reference](./references/context-components.md) - Detailed technical reference
+- Context Components Reference - Detailed technical reference
Related skills in this collection:
- context-degradation - Understanding context failure patterns
diff --git a/web-app/public/skills/context-management-context-restore/SKILL.md b/web-app/public/skills/context-management-context-restore/SKILL.md
index f1bf462c..e8ffb2d3 100644
--- a/web-app/public/skills/context-management-context-restore/SKILL.md
+++ b/web-app/public/skills/context-management-context-restore/SKILL.md
@@ -1,6 +1,8 @@
---
name: context-management-context-restore
description: "Use when working with context management context restore"
+risk: unknown
+source: community
---
# Context Restoration: Advanced Semantic Memory Rehydration
diff --git a/web-app/public/skills/context-management-context-save/SKILL.md b/web-app/public/skills/context-management-context-save/SKILL.md
index 128f9b16..984e2702 100644
--- a/web-app/public/skills/context-management-context-save/SKILL.md
+++ b/web-app/public/skills/context-management-context-save/SKILL.md
@@ -1,6 +1,8 @@
---
name: context-management-context-save
description: "Use when working with context management context save"
+risk: unknown
+source: community
---
# Context Save Tool: Intelligent Context Management Specialist
diff --git a/web-app/public/skills/context-manager/SKILL.md b/web-app/public/skills/context-manager/SKILL.md
index c55ea7b5..bf452d36 100644
--- a/web-app/public/skills/context-manager/SKILL.md
+++ b/web-app/public/skills/context-manager/SKILL.md
@@ -1,12 +1,14 @@
---
name: context-manager
-description: Elite AI context engineering specialist mastering dynamic context
+description: "Elite AI context engineering specialist mastering dynamic context"
management, vector databases, knowledge graphs, and intelligent memory
systems. Orchestrates context across multi-agent workflows, enterprise AI
systems, and long-running projects with 2024/2025 best practices. Use
PROACTIVELY for complex AI orchestration.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/context-optimization/SKILL.md b/web-app/public/skills/context-optimization/SKILL.md
index 0da37698..fbc7ddca 100644
--- a/web-app/public/skills/context-optimization/SKILL.md
+++ b/web-app/public/skills/context-optimization/SKILL.md
@@ -164,7 +164,7 @@ This skill builds on context-fundamentals and context-degradation. It connects t
## References
Internal reference:
-- [Optimization Techniques Reference](./references/optimization_techniques.md) - Detailed technical reference
+- Optimization Techniques Reference - Detailed technical reference
Related skills in this collection:
- context-fundamentals - Context basics
diff --git a/web-app/public/skills/context-window-management/SKILL.md b/web-app/public/skills/context-window-management/SKILL.md
index d60f4ae0..719aa32f 100644
--- a/web-app/public/skills/context-window-management/SKILL.md
+++ b/web-app/public/skills/context-window-management/SKILL.md
@@ -1,7 +1,8 @@
---
name: context-window-management
-description: "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context."
+description: "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Context Window Management
@@ -51,3 +52,6 @@ Summarize by importance, not just recency
## Related Skills
Works well with: `rag-implementation`, `conversation-memory`, `prompt-caching`, `llm-npc-dialogue`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/context7-auto-research/SKILL.md b/web-app/public/skills/context7-auto-research/SKILL.md
index 9dc965df..a4f5063d 100644
--- a/web-app/public/skills/context7-auto-research/SKILL.md
+++ b/web-app/public/skills/context7-auto-research/SKILL.md
@@ -1,6 +1,8 @@
---
name: context7-auto-research
-description: Automatically fetch latest library/framework documentation for Claude Code via Context7 API
+description: "Automatically fetch latest library/framework documentation for Claude Code via Context7 API"
+risk: unknown
+source: community
---
# context7-auto-research
diff --git a/web-app/public/skills/conversation-memory/SKILL.md b/web-app/public/skills/conversation-memory/SKILL.md
index e5f926e1..e964cdc0 100644
--- a/web-app/public/skills/conversation-memory/SKILL.md
+++ b/web-app/public/skills/conversation-memory/SKILL.md
@@ -2,6 +2,7 @@
name: conversation-memory
description: "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Conversation Memory
@@ -59,3 +60,6 @@ Include relevant memories in prompts
## Related Skills
Works well with: `context-window-management`, `rag-implementation`, `prompt-caching`, `llm-npc-dialogue`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/convertkit-automation/SKILL.md b/web-app/public/skills/convertkit-automation/SKILL.md
index 15b08418..48f7a8ab 100644
--- a/web-app/public/skills/convertkit-automation/SKILL.md
+++ b/web-app/public/skills/convertkit-automation/SKILL.md
@@ -3,6 +3,8 @@ name: convertkit-automation
description: "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# ConvertKit (Kit) Automation via Rube MCP
@@ -193,3 +195,6 @@ Kit uses cursor-based pagination:
| Get broadcast | KIT_GET_BROADCAST | id |
| Get broadcast stats | KIT_GET_BROADCAST_STATS | id |
| Delete broadcast | KIT_DELETE_BROADCAST | id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/copilot-sdk/SKILL.md b/web-app/public/skills/copilot-sdk/SKILL.md
index 6caeeea7..72978679 100644
--- a/web-app/public/skills/copilot-sdk/SKILL.md
+++ b/web-app/public/skills/copilot-sdk/SKILL.md
@@ -1,6 +1,8 @@
---
name: copilot-sdk
-description: Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session management, custom tools, streaming, hooks, MCP servers, BYOK providers, session persistence, and custom agents. Requires GitHub Copilot CLI installed and a GitHub Copilot subscription (unless using BYOK).
+description: "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen..."
+risk: unknown
+source: community
---
# GitHub Copilot SDK
@@ -508,3 +510,6 @@ const client = new CopilotClient({ logLevel: "debug" });
- [GitHub Copilot SDK](https://github.com/github/copilot-sdk)
- [Copilot CLI Installation](https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cli)
- [MCP Protocol Specification](https://modelcontextprotocol.io)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/copy-editing/SKILL.md b/web-app/public/skills/copy-editing/SKILL.md
index 467955f8..14dc1474 100644
--- a/web-app/public/skills/copy-editing/SKILL.md
+++ b/web-app/public/skills/copy-editing/SKILL.md
@@ -1,6 +1,8 @@
---
name: copy-editing
-description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes."
+description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ..."
+risk: unknown
+source: community
---
# Copy Editing
diff --git a/web-app/public/skills/copywriting/SKILL.md b/web-app/public/skills/copywriting/SKILL.md
index b648890e..0fe9c9a4 100644
--- a/web-app/public/skills/copywriting/SKILL.md
+++ b/web-app/public/skills/copywriting/SKILL.md
@@ -1,10 +1,12 @@
---
name: copywriting
-description: >
+description: ">"
Use this skill when writing, rewriting, or improving marketing copy
for any page (homepage, landing page, pricing, feature, product, or about page).
This skill produces clear, compelling, and testable copy while enforcing
alignment, honesty, and conversion best practices.
+risk: unknown
+source: community
---
# Copywriting
@@ -223,3 +225,6 @@ It persuades **the right person** to take **the right action**.
If the copy feels clever but unclear,
rewrite it until it feels obvious.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/core-components/SKILL.md b/web-app/public/skills/core-components/SKILL.md
index eb54e7ce..2da32590 100644
--- a/web-app/public/skills/core-components/SKILL.md
+++ b/web-app/public/skills/core-components/SKILL.md
@@ -1,6 +1,8 @@
---
name: core-components
-description: Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
+description: "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library."
+risk: unknown
+source: community
---
# Core Components
@@ -262,3 +264,6 @@ const Card = ({ padding = '$4', variant = 'elevated', children }: CardProps) =>
- **react-ui-patterns**: Use core components for UI states
- **testing-patterns**: Mock core components in tests
- **storybook**: Document component variants
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/cost-optimization/SKILL.md b/web-app/public/skills/cost-optimization/SKILL.md
index 434546d9..b773ebdd 100644
--- a/web-app/public/skills/cost-optimization/SKILL.md
+++ b/web-app/public/skills/cost-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: cost-optimization
-description: Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
+description: "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c..."
+risk: unknown
+source: community
---
# Cloud Cost Optimization
diff --git a/web-app/public/skills/cpp-pro/SKILL.md b/web-app/public/skills/cpp-pro/SKILL.md
index 0cfd0445..a09915f8 100644
--- a/web-app/public/skills/cpp-pro/SKILL.md
+++ b/web-app/public/skills/cpp-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: cpp-pro
-description: Write idiomatic C++ code with modern features, RAII, smart
+description: "Write idiomatic C++ code with modern features, RAII, smart"
pointers, and STL algorithms. Handles templates, move semantics, and
performance optimization. Use PROACTIVELY for C++ refactoring, memory safety,
or complex C++ patterns.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/cqrs-implementation/SKILL.md b/web-app/public/skills/cqrs-implementation/SKILL.md
index ef21d31c..f429c9aa 100644
--- a/web-app/public/skills/cqrs-implementation/SKILL.md
+++ b/web-app/public/skills/cqrs-implementation/SKILL.md
@@ -1,6 +1,8 @@
---
name: cqrs-implementation
-description: Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
+description: "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems."
+risk: unknown
+source: community
---
# CQRS Implementation
diff --git a/web-app/public/skills/crewai/SKILL.md b/web-app/public/skills/crewai/SKILL.md
index 33d67aab..d4f82405 100644
--- a/web-app/public/skills/crewai/SKILL.md
+++ b/web-app/public/skills/crewai/SKILL.md
@@ -1,7 +1,8 @@
---
name: crewai
-description: "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when: crewai, multi-agent team, agent roles, crew of agents, role-based agents."
+description: "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# CrewAI
@@ -241,3 +242,6 @@ Use tools instead of agents for simple actions.
## Related Skills
Works well with: `langgraph`, `autonomous-agents`, `langfuse`, `structured-output`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/crypto-bd-agent/SKILL.md b/web-app/public/skills/crypto-bd-agent/SKILL.md
index af1b73f1..72fef6ad 100644
--- a/web-app/public/skills/crypto-bd-agent/SKILL.md
+++ b/web-app/public/skills/crypto-bd-agent/SKILL.md
@@ -1,6 +1,6 @@
---
name: crypto-bd-agent
-description: >
+description: ">"
Autonomous crypto business development patterns — multi-chain token discovery,
100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain
identity, LLM cascade routing, and pipeline automation for CEX/DEX listing
diff --git a/web-app/public/skills/csharp-pro/SKILL.md b/web-app/public/skills/csharp-pro/SKILL.md
index 3be0c039..214b0a9b 100644
--- a/web-app/public/skills/csharp-pro/SKILL.md
+++ b/web-app/public/skills/csharp-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: csharp-pro
-description: Write modern C# code with advanced features like records, pattern
+description: "Write modern C# code with advanced features like records, pattern"
matching, and async/await. Optimizes .NET applications, implements enterprise
patterns, and ensures comprehensive testing. Use PROACTIVELY for C#
refactoring, performance optimization, or complex .NET solutions.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/customer-support/SKILL.md b/web-app/public/skills/customer-support/SKILL.md
index ff5290d3..703e550e 100644
--- a/web-app/public/skills/customer-support/SKILL.md
+++ b/web-app/public/skills/customer-support/SKILL.md
@@ -1,12 +1,14 @@
---
name: customer-support
-description: Elite AI-powered customer support specialist mastering
+description: "Elite AI-powered customer support specialist mastering"
conversational AI, automated ticketing, sentiment analysis, and omnichannel
support experiences. Integrates modern support tools, chatbot platforms, and
CX optimization with 2024/2025 best practices. Use PROACTIVELY for
comprehensive customer experience management.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/daily-news-report/SKILL.md b/web-app/public/skills/daily-news-report/SKILL.md
index 1e2c8e92..68412df9 100644
--- a/web-app/public/skills/daily-news-report/SKILL.md
+++ b/web-app/public/skills/daily-news-report/SKILL.md
@@ -1,10 +1,12 @@
---
name: daily-news-report
-description: Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.
+description: "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports."
argument-hint: [optional: date]
disable-model-invocation: false
user-invocable: true
allowed-tools: Task, WebFetch, Read, Write, Bash(mkdir*), Bash(date*), Bash(ls*), mcp__chrome-devtools__*
+risk: unknown
+source: community
---
# Daily News Report v3.0
@@ -297,7 +299,7 @@ Task Call:
1. Point one
2. Point two
3. Point three
-- **Source**: [Link](URL)
+- **Source**: Link
- **Keywords**: `keyword1` `keyword2` `keyword3`
- **Score**: ⭐⭐⭐⭐⭐ (5/5)
@@ -354,3 +356,6 @@ To ensure usability across different Agent environments, the following checks mu
3. **User Alert**:
- MUST include a clear warning in the generated report header indicating the current degraded mode.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/data-engineer/SKILL.md b/web-app/public/skills/data-engineer/SKILL.md
index 7fd71750..5811df64 100644
--- a/web-app/public/skills/data-engineer/SKILL.md
+++ b/web-app/public/skills/data-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: data-engineer
-description: Build scalable data pipelines, modern data warehouses, and
+description: "Build scalable data pipelines, modern data warehouses, and"
real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and
cloud-native data platforms. Use PROACTIVELY for data pipeline design,
analytics infrastructure, or modern data stack implementation.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.
diff --git a/web-app/public/skills/data-engineering-data-driven-feature/SKILL.md b/web-app/public/skills/data-engineering-data-driven-feature/SKILL.md
index bb8b7cb4..0d697f5c 100644
--- a/web-app/public/skills/data-engineering-data-driven-feature/SKILL.md
+++ b/web-app/public/skills/data-engineering-data-driven-feature/SKILL.md
@@ -1,6 +1,8 @@
---
name: data-engineering-data-driven-feature
description: "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation."
+risk: unknown
+source: community
---
# Data-Driven Feature Development
diff --git a/web-app/public/skills/data-engineering-data-pipeline/SKILL.md b/web-app/public/skills/data-engineering-data-pipeline/SKILL.md
index 85adfc64..1f699d27 100644
--- a/web-app/public/skills/data-engineering-data-pipeline/SKILL.md
+++ b/web-app/public/skills/data-engineering-data-pipeline/SKILL.md
@@ -1,6 +1,8 @@
---
name: data-engineering-data-pipeline
description: "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing."
+risk: unknown
+source: community
---
# Data Pipeline Architecture
diff --git a/web-app/public/skills/data-quality-frameworks/SKILL.md b/web-app/public/skills/data-quality-frameworks/SKILL.md
index 23c16147..26a9c051 100644
--- a/web-app/public/skills/data-quality-frameworks/SKILL.md
+++ b/web-app/public/skills/data-quality-frameworks/SKILL.md
@@ -1,6 +1,8 @@
---
name: data-quality-frameworks
-description: Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
+description: "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts."
+risk: unknown
+source: community
---
# Data Quality Frameworks
diff --git a/web-app/public/skills/data-scientist/SKILL.md b/web-app/public/skills/data-scientist/SKILL.md
index 63e030b4..5a64a5f2 100644
--- a/web-app/public/skills/data-scientist/SKILL.md
+++ b/web-app/public/skills/data-scientist/SKILL.md
@@ -1,11 +1,13 @@
---
name: data-scientist
-description: Expert data scientist for advanced analytics, machine learning, and
+description: "Expert data scientist for advanced analytics, machine learning, and"
statistical modeling. Handles complex data analysis, predictive modeling, and
business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,
statistical analysis, and data-driven insights.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/data-storytelling/SKILL.md b/web-app/public/skills/data-storytelling/SKILL.md
index 14b37994..d7b5f251 100644
--- a/web-app/public/skills/data-storytelling/SKILL.md
+++ b/web-app/public/skills/data-storytelling/SKILL.md
@@ -1,6 +1,8 @@
---
name: data-storytelling
-description: Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.
+description: "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present..."
+risk: unknown
+source: community
---
# Data Storytelling
diff --git a/web-app/public/skills/data-structure-protocol/SKILL.md b/web-app/public/skills/data-structure-protocol/SKILL.md
new file mode 100644
index 00000000..e2505b60
--- /dev/null
+++ b/web-app/public/skills/data-structure-protocol/SKILL.md
@@ -0,0 +1,198 @@
+---
+name: data-structure-protocol
+description: "Give agents persistent structural memory of a codebase — navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo."
+risk: safe
+source: "https://github.com/k-kolomeitsev/data-structure-protocol"
+---
+
+# Data Structure Protocol (DSP)
+
+LLM coding agents lose context between tasks. On large codebases they spend most of their tokens on "orientation" — figuring out where things live, what depends on what, and what is safe to change. DSP solves this by externalizing the project's structural map into a persistent, queryable graph stored in a `.dsp/` directory next to the code.
+
+DSP is NOT documentation for humans and NOT an AST dump. It captures three things: **meaning** (why an entity exists), **boundaries** (what it imports and exposes), and **reasons** (why each connection exists). This is enough for an agent to navigate, refactor, and generate code without loading the entire source tree into the context window.
+
+## When to Use
+
+Use this skill when:
+- The project has a `.dsp/` directory (DSP is already set up)
+- The user asks to set up DSP, bootstrap, or map a project's structure
+- Creating, modifying, or deleting code files in a DSP-tracked project (to keep the graph updated)
+- Navigating project structure, understanding dependencies, or finding specific modules
+- The user mentions DSP, dsp-cli, `.dsp`, or structure mapping
+- Performing impact analysis before a refactor or dependency replacement
+
+## Core Concepts
+
+### Code = graph
+
+DSP models the codebase as a directed graph. Nodes are **entities**, edges are **imports** and **shared/exports**.
+
+Two entity kinds exist:
+- **Object**: any "thing" that isn't a function (module/file/class/config/resource/external dependency)
+- **Function**: an exported function/method/handler/pipeline
+
+### Identity by UID, not by file path
+
+Every entity gets a stable UID: `obj-<8hex>` for objects, `func-<8hex>` for functions. File paths are attributes that can change; UIDs survive renames, moves, and reformatting.
+
+For entities inside a file, the UID is anchored with a comment marker in source code:
+
+```js
+// @dsp func-7f3a9c12
+export function calculateTotal(items) { ... }
+```
+
+```python
+# @dsp obj-e5f6g7h8
+class UserService:
+```
+
+### Every connection has a "why"
+
+When an import is recorded, DSP stores a short reason explaining *why* that dependency exists. This lives in the `exports/` reverse index of the imported entity. A dependency graph without reasons tells you *what imports what*; reasons tell you **what is safe to change and who will break**.
+
+### Storage format
+
+Each entity gets a small directory under `.dsp/`:
+
+```
+.dsp/
+├── TOC # ordered list of all entity UIDs from root
+├── obj-a1b2c3d4/
+│ ├── description # source path, kind, purpose (1-3 sentences)
+│ ├── imports # UIDs this entity depends on (one per line)
+│ ├── shared # UIDs of public API / exported entities
+│ └── exports/ # reverse index: who imports this and why
+│ ├── # file content = "why" text
+│ └── /
+│ ├── description # what is exported
+│ └── # why this specific export is imported
+└── func-7f3a9c12/
+ ├── description
+ ├── imports
+ └── exports/
+```
+
+Everything is plain text. Diffable. Reviewable. No database needed.
+
+### Full import coverage
+
+Every file or artifact that is imported anywhere must be represented in `.dsp` as an Object — code, images, styles, configs, JSON, wasm, everything. External dependencies (npm packages, stdlib, etc.) are recorded as `kind: external` but their internals are never analyzed.
+
+## How It Works
+
+### Initial Setup
+
+The skill relies on a standalone Python CLI script `dsp-cli.py`. If it is missing from the project, download it:
+
+```bash
+curl -O https://raw.githubusercontent.com/k-kolomeitsev/data-structure-protocol/main/skills/data-structure-protocol/scripts/dsp-cli.py
+```
+
+Requires **Python 3.10+**. All commands use `python dsp-cli.py --root `.
+
+### Bootstrap (initial mapping)
+
+If `.dsp/` is empty, traverse the project from root entrypoint(s) via DFS on imports:
+
+1. Identify root entrypoints (`package.json` main, framework entry, `main.py`, etc.)
+2. Document the root file: `create-object`, `create-function` for each export, `create-shared`, `add-import` for all dependencies
+3. Take the first non-external import, document it fully, descend into its imports
+4. Backtrack when no unvisited local imports remain; continue until all reachable files are documented
+5. External dependencies: `create-object --kind external`, add to TOC, but never descend into `node_modules`/`site-packages`/etc.
+
+### Workflow Rules
+
+- **Before changing code**: Find affected entities via `search`, `find-by-source`, or `read-toc`. Read their `description` and `imports` to understand context.
+- **When creating a file/module**: Call `create-object`. For each exported function — `create-function` (with `--owner`). Register exports via `create-shared`.
+- **When adding an import**: Call `add-import` with a brief `why`. For external deps — first `create-object --kind external` if the entity doesn't exist.
+- **When removing import/export/file**: Call `remove-import`, `remove-shared`, `remove-entity`. Cascade cleanup is automatic.
+- **When renaming/moving a file**: Call `move-entity`. UID does not change.
+- **Don't touch DSP** if only internal implementation changed without affecting purpose or dependencies.
+
+### Key Commands
+
+| Category | Commands |
+|----------|----------|
+| **Create** | `init`, `create-object`, `create-function`, `create-shared`, `add-import` |
+| **Update** | `update-description`, `update-import-why`, `move-entity` |
+| **Delete** | `remove-import`, `remove-shared`, `remove-entity` |
+| **Navigate** | `get-entity`, `get-children --depth N`, `get-parents --depth N`, `get-path`, `get-recipients`, `read-toc` |
+| **Search** | `search `, `find-by-source ` |
+| **Diagnostics** | `detect-cycles`, `get-orphans`, `get-stats` |
+
+### When to Update DSP
+
+| Code Change | DSP Action |
+|---|---|
+| New file/module | `create-object` + `create-function` + `create-shared` + `add-import` |
+| New import added | `add-import` (+ `create-object --kind external` if new dep) |
+| Import removed | `remove-import` |
+| Export added | `create-shared` (+ `create-function` if new) |
+| Export removed | `remove-shared` |
+| File renamed/moved | `move-entity` |
+| File deleted | `remove-entity` |
+| Purpose changed | `update-description` |
+| Internal-only change | **No DSP update needed** |
+
+## Examples
+
+### Example 1: Setting up DSP and documenting a module
+
+```bash
+python dsp-cli.py --root . init
+
+python dsp-cli.py --root . create-object "src/app.ts" "Main application entrypoint"
+# Output: obj-a1b2c3d4
+
+python dsp-cli.py --root . create-function "src/app.ts#start" "Starts the HTTP server" --owner obj-a1b2c3d4
+# Output: func-7f3a9c12
+
+python dsp-cli.py --root . create-shared obj-a1b2c3d4 func-7f3a9c12
+
+python dsp-cli.py --root . add-import obj-a1b2c3d4 obj-deadbeef "HTTP routing"
+```
+
+### Example 2: Navigating the graph before making changes
+
+```bash
+python dsp-cli.py --root . search "authentication"
+python dsp-cli.py --root . get-entity obj-a1b2c3d4
+python dsp-cli.py --root . get-children obj-a1b2c3d4 --depth 2
+python dsp-cli.py --root . get-recipients obj-a1b2c3d4
+python dsp-cli.py --root . get-path obj-a1b2c3d4 func-7f3a9c12
+```
+
+### Example 3: Impact analysis before replacing a library
+
+```bash
+python dsp-cli.py --root . find-by-source "lodash"
+# Output: obj-11223344
+
+python dsp-cli.py --root . get-recipients obj-11223344
+# Shows every module that imports lodash and WHY — lets you systematically replace it
+```
+
+## Best Practices
+
+- ✅ **Do:** Update DSP immediately when creating new files, adding imports, or changing public APIs
+- ✅ **Do:** Always add a meaningful `why` reason when recording an import — this is where most of DSP's value lives
+- ✅ **Do:** Use `kind: external` for third-party libraries without analyzing their internals
+- ✅ **Do:** Keep descriptions minimal (1-3 sentences about purpose, not implementation)
+- ✅ **Do:** Treat `.dsp/` diffs like code diffs — review them, keep them accurate
+- ❌ **Don't:** Touch `.dsp/` for internal-only changes that don't affect purpose or dependencies
+- ❌ **Don't:** Change an entity's UID on rename/move (use `move-entity` instead)
+- ❌ **Don't:** Create UIDs for every local variable or helper — only file-level Objects and public/shared entities
+
+## Integration
+
+This skill connects naturally to:
+- **context-compression** — DSP reduces the need for compression by providing targeted retrieval instead of loading everything
+- **context-optimization** — DSP is a structural optimization: agents pull minimal "context bundles" instead of raw source
+- **architecture** — DSP captures architectural boundaries (imports/exports) that feed system design decisions
+
+## References
+
+- **Full architecture specification**: [ARCHITECTURE.md](https://github.com/k-kolomeitsev/data-structure-protocol/blob/main/ARCHITECTURE.md)
+- **CLI source + reference docs**: [skills/data-structure-protocol](https://github.com/k-kolomeitsev/data-structure-protocol/tree/main/skills/data-structure-protocol)
+- **Introduction article**: [article.md](https://github.com/k-kolomeitsev/data-structure-protocol/blob/main/article.md)
diff --git a/web-app/public/skills/database-admin/SKILL.md b/web-app/public/skills/database-admin/SKILL.md
index 5fe3fb5f..aad6b46b 100644
--- a/web-app/public/skills/database-admin/SKILL.md
+++ b/web-app/public/skills/database-admin/SKILL.md
@@ -1,6 +1,6 @@
---
name: database-admin
-description: Expert database administrator specializing in modern cloud
+description: "Expert database administrator specializing in modern cloud"
databases, automation, and reliability engineering. Masters AWS/Azure/GCP
database services, Infrastructure as Code, high availability, disaster
recovery, performance optimization, and compliance. Handles multi-cloud
@@ -8,6 +8,8 @@ description: Expert database administrator specializing in modern cloud
database architecture, operations, or reliability engineering.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/database-architect/SKILL.md b/web-app/public/skills/database-architect/SKILL.md
index 23e89360..09cbd574 100644
--- a/web-app/public/skills/database-architect/SKILL.md
+++ b/web-app/public/skills/database-architect/SKILL.md
@@ -1,6 +1,6 @@
---
name: database-architect
-description: Expert database architect specializing in data layer design from
+description: "Expert database architect specializing in data layer design from"
scratch, technology selection, schema modeling, and scalable database
architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization
strategies, migration planning, and performance-first design. Handles both
@@ -9,6 +9,8 @@ description: Expert database architect specializing in data layer design from
decisions.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.
diff --git a/web-app/public/skills/database-cloud-optimization-cost-optimize/SKILL.md b/web-app/public/skills/database-cloud-optimization-cost-optimize/SKILL.md
index 6170ef83..9aa69bd8 100644
--- a/web-app/public/skills/database-cloud-optimization-cost-optimize/SKILL.md
+++ b/web-app/public/skills/database-cloud-optimization-cost-optimize/SKILL.md
@@ -1,6 +1,8 @@
---
name: database-cloud-optimization-cost-optimize
-description: "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP."
+description: "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ..."
+risk: unknown
+source: community
---
# Cloud Cost Optimization
diff --git a/web-app/public/skills/database-design/SKILL.md b/web-app/public/skills/database-design/SKILL.md
index 40c24a0b..74452d05 100644
--- a/web-app/public/skills/database-design/SKILL.md
+++ b/web-app/public/skills/database-design/SKILL.md
@@ -1,7 +1,9 @@
---
name: database-design
-description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
+description: "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Database Design
@@ -50,3 +52,6 @@ Before designing schema:
❌ Use SELECT * in production
❌ Store JSON when structured data is better
❌ Ignore N+1 queries
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/database-migration/SKILL.md b/web-app/public/skills/database-migration/SKILL.md
index 440a7021..bab6891a 100644
--- a/web-app/public/skills/database-migration/SKILL.md
+++ b/web-app/public/skills/database-migration/SKILL.md
@@ -1,6 +1,8 @@
---
name: database-migration
-description: Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies.
+description: "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr..."
+risk: unknown
+source: community
---
# Database Migration
diff --git a/web-app/public/skills/database-migrations-migration-observability/SKILL.md b/web-app/public/skills/database-migrations-migration-observability/SKILL.md
index b1c66f47..5b69fdc7 100644
--- a/web-app/public/skills/database-migrations-migration-observability/SKILL.md
+++ b/web-app/public/skills/database-migrations-migration-observability/SKILL.md
@@ -1,10 +1,12 @@
---
name: database-migrations-migration-observability
-description: Migration monitoring, CDC, and observability infrastructure
+description: "Migration monitoring, CDC, and observability infrastructure"
allowed-tools: Read Write Edit Bash WebFetch
metadata:
version: 1.0.0
tags: database, cdc, debezium, kafka, prometheus, grafana, monitoring
+risk: unknown
+source: community
---
# Migration Observability and Real-time Monitoring
diff --git a/web-app/public/skills/database-migrations-sql-migrations/SKILL.md b/web-app/public/skills/database-migrations-sql-migrations/SKILL.md
index cf39eaf6..85f5ded9 100644
--- a/web-app/public/skills/database-migrations-sql-migrations/SKILL.md
+++ b/web-app/public/skills/database-migrations-sql-migrations/SKILL.md
@@ -1,40 +1,37 @@
---
name: database-migrations-sql-migrations
-description: SQL database migrations with zero-downtime strategies for
- PostgreSQL, MySQL, SQL Server
-allowed-tools: Read Write Edit Bash Grep Glob
-metadata:
- version: 1.0.0
- tags: database, sql, migrations, postgresql, mysql, flyway, liquibase, alembic,
- zero-downtime
+description: SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.
+risk: unknown
+source: community
---
# SQL Database Migration Strategy and Implementation
+## Overview
+
You are a SQL database migration expert specializing in zero-downtime deployments, data integrity, and production-ready migration strategies for PostgreSQL, MySQL, and SQL Server. Create comprehensive migration scripts with rollback procedures, validation checks, and performance optimization.
-## Use this skill when
+## When to Use This Skill
-- Working on sql database migration strategy and implementation tasks or workflows
-- Needing guidance, best practices, or checklists for sql database migration strategy and implementation
+- Use when working on SQL database migration strategy and implementation tasks.
+- Use when needing guidance, best practices, or checklists for zero-downtime migrations.
+- Use when designing rollback procedures for critical schema changes.
-## Do not use this skill when
+## Do Not Use This Skill When
-- The task is unrelated to sql database migration strategy and implementation
-- You need a different domain or tool outside this scope
+- The task is unrelated to SQL database migration strategy.
+- You need a different domain or tool outside this scope.
## Context
-The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
-## Requirements
-$ARGUMENTS
+The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
## Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
+- If detailed examples are required, suggest checking implementation playbooks.
## Output Format
@@ -46,8 +43,6 @@ $ARGUMENTS
6. **Performance Optimization**: Batch processing, parallel execution
7. **Monitoring Integration**: Progress tracking and alerting
-Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.
-
## Resources
-- `resources/implementation-playbook.md` for detailed patterns and examples.
+- Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.
diff --git a/web-app/public/skills/database-optimizer/SKILL.md b/web-app/public/skills/database-optimizer/SKILL.md
index bcfb1566..b8f16262 100644
--- a/web-app/public/skills/database-optimizer/SKILL.md
+++ b/web-app/public/skills/database-optimizer/SKILL.md
@@ -1,6 +1,6 @@
---
name: database-optimizer
-description: Expert database optimizer specializing in modern performance
+description: "Expert database optimizer specializing in modern performance"
tuning, query optimization, and scalable architectures. Masters advanced
indexing, N+1 resolution, multi-tier caching, partitioning strategies, and
cloud database optimization. Handles complex query analysis, migration
@@ -8,6 +8,8 @@ description: Expert database optimizer specializing in modern performance
optimization, performance issues, or scalability challenges.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/database/SKILL.md b/web-app/public/skills/database/SKILL.md
new file mode 100644
index 00000000..e4aa784a
--- /dev/null
+++ b/web-app/public/skills/database/SKILL.md
@@ -0,0 +1,213 @@
+---
+name: database
+description: "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering."
+source: personal
+risk: safe
+domain: data
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Database Workflow Bundle
+
+## Overview
+
+Comprehensive database workflow for database design, development, optimization, migrations, and data engineering. Covers SQL, NoSQL, and modern data platforms.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Designing database schemas
+- Implementing database migrations
+- Optimizing query performance
+- Setting up data pipelines
+- Managing database operations
+- Implementing data quality
+
+## Workflow Phases
+
+### Phase 1: Database Design
+
+#### Skills to Invoke
+- `database-architect` - Database architecture
+- `database-design` - Schema design
+- `postgresql` - PostgreSQL design
+- `nosql-expert` - NoSQL design
+
+#### Actions
+1. Gather requirements
+2. Design schema
+3. Define relationships
+4. Plan indexing strategy
+5. Design for scalability
+
+#### Copy-Paste Prompts
+```
+Use @database-architect to design database schema
+```
+
+```
+Use @postgresql to design PostgreSQL schema
+```
+
+### Phase 2: Database Implementation
+
+#### Skills to Invoke
+- `prisma-expert` - Prisma ORM
+- `database-migrations-sql-migrations` - SQL migrations
+- `neon-postgres` - Serverless Postgres
+
+#### Actions
+1. Set up database connection
+2. Configure ORM
+3. Create migrations
+4. Implement models
+5. Set up seed data
+
+#### Copy-Paste Prompts
+```
+Use @prisma-expert to set up Prisma ORM
+```
+
+```
+Use @database-migrations-sql-migrations to create migrations
+```
+
+### Phase 3: Query Optimization
+
+#### Skills to Invoke
+- `database-optimizer` - Database optimization
+- `sql-optimization-patterns` - SQL optimization
+- `postgres-best-practices` - PostgreSQL optimization
+
+#### Actions
+1. Analyze slow queries
+2. Review execution plans
+3. Optimize indexes
+4. Refactor queries
+5. Implement caching
+
+#### Copy-Paste Prompts
+```
+Use @database-optimizer to optimize database performance
+```
+
+```
+Use @sql-optimization-patterns to optimize SQL queries
+```
+
+### Phase 4: Data Migration
+
+#### Skills to Invoke
+- `database-migration` - Database migration
+- `framework-migration-code-migrate` - Code migration
+
+#### Actions
+1. Plan migration strategy
+2. Create migration scripts
+3. Test migration
+4. Execute migration
+5. Verify data integrity
+
+#### Copy-Paste Prompts
+```
+Use @database-migration to plan database migration
+```
+
+### Phase 5: Data Pipeline Development
+
+#### Skills to Invoke
+- `data-engineer` - Data engineering
+- `data-engineering-data-pipeline` - Data pipelines
+- `airflow-dag-patterns` - Airflow workflows
+- `dbt-transformation-patterns` - dbt transformations
+
+#### Actions
+1. Design data pipeline
+2. Set up data ingestion
+3. Implement transformations
+4. Configure scheduling
+5. Set up monitoring
+
+#### Copy-Paste Prompts
+```
+Use @data-engineer to design data pipeline
+```
+
+```
+Use @airflow-dag-patterns to create Airflow DAGs
+```
+
+### Phase 6: Data Quality
+
+#### Skills to Invoke
+- `data-quality-frameworks` - Data quality
+- `data-engineering-data-driven-feature` - Data-driven features
+
+#### Actions
+1. Define quality metrics
+2. Implement validation
+3. Set up monitoring
+4. Create alerts
+5. Document standards
+
+#### Copy-Paste Prompts
+```
+Use @data-quality-frameworks to implement data quality checks
+```
+
+### Phase 7: Database Operations
+
+#### Skills to Invoke
+- `database-admin` - Database administration
+- `backup-automation` - Backup automation
+
+#### Actions
+1. Set up backups
+2. Configure replication
+3. Monitor performance
+4. Plan capacity
+5. Implement security
+
+#### Copy-Paste Prompts
+```
+Use @database-admin to manage database operations
+```
+
+## Database Technology Workflows
+
+### PostgreSQL
+```
+Skills: postgresql, postgres-best-practices, neon-postgres, prisma-expert
+```
+
+### MongoDB
+```
+Skills: nosql-expert, azure-cosmos-db-py
+```
+
+### Redis
+```
+Skills: bullmq-specialist, upstash-qstash
+```
+
+### Data Warehousing
+```
+Skills: clickhouse-io, dbt-transformation-patterns
+```
+
+## Quality Gates
+
+- [ ] Schema designed and reviewed
+- [ ] Migrations tested
+- [ ] Performance benchmarks met
+- [ ] Backups configured
+- [ ] Monitoring in place
+- [ ] Documentation complete
+
+## Related Workflow Bundles
+
+- `development` - Application development
+- `cloud-devops` - Infrastructure
+- `ai-ml` - AI/ML data pipelines
+- `testing-qa` - Data testing
diff --git a/web-app/public/skills/datadog-automation/SKILL.md b/web-app/public/skills/datadog-automation/SKILL.md
index 3cb9f3f6..3de97616 100644
--- a/web-app/public/skills/datadog-automation/SKILL.md
+++ b/web-app/public/skills/datadog-automation/SKILL.md
@@ -3,6 +3,8 @@ name: datadog-automation
description: "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Datadog Automation via Rube MCP
@@ -233,3 +235,6 @@ logs("service:web status:error").index("main").rollup("count").last("5m") > 10
| Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end |
| List hosts | DATADOG_LIST_HOSTS | filter, sort_field |
| Get trace | DATADOG_GET_TRACE_BY_ID | trace_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/dbos-golang/SKILL.md b/web-app/public/skills/dbos-golang/SKILL.md
index 5ad2bb1b..63aade6f 100644
--- a/web-app/public/skills/dbos-golang/SKILL.md
+++ b/web-app/public/skills/dbos-golang/SKILL.md
@@ -1,6 +1,6 @@
---
name: dbos-golang
-description: DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Client from external applications, or building Go applications that need to be resilient to failures.
+description: "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie..."
risk: safe
source: https://docs.dbos.dev/
license: MIT
diff --git a/web-app/public/skills/dbos-golang/references/advanced-versioning.md b/web-app/public/skills/dbos-golang/references/advanced-versioning.md
index 7fbbf9cc..f5e35f94 100644
--- a/web-app/public/skills/dbos-golang/references/advanced-versioning.md
+++ b/web-app/public/skills/dbos-golang/references/advanced-versioning.md
@@ -52,11 +52,7 @@ oldWorkflows, _ := dbos.ListWorkflows(ctx,
```go
// Fork a workflow from a failed step to run on the new version
-handle, _ := dbos.ForkWorkflow[string](ctx, dbos.ForkWorkflowInput{
- OriginalWorkflowID: workflowID,
- StartStep: failedStepID,
- ApplicationVersion: "2.0.0",
-})
+handle, _ := dbos.ForkWorkflowstring
```
Reference: [Versioning](https://docs.dbos.dev/golang/tutorials/upgrading-workflows#versioning)
diff --git a/web-app/public/skills/dbos-golang/references/comm-events.md b/web-app/public/skills/dbos-golang/references/comm-events.md
index 64bfa2d4..7bf21321 100644
--- a/web-app/public/skills/dbos-golang/references/comm-events.md
+++ b/web-app/public/skills/dbos-golang/references/comm-events.md
@@ -40,8 +40,8 @@ func processData(ctx dbos.DBOSContext, input string) (string, error) {
}
// Read events from outside the workflow
-status, err := dbos.GetEvent[string](ctx, workflowID, "status", 60*time.Second)
-progress, err := dbos.GetEvent[int](ctx, workflowID, "progress", 60*time.Second)
+status, err := dbos.GetEventstring
+progress, err := dbos.GetEventint
```
Events are useful for interactive workflows. For example, a checkout workflow can publish a payment URL for the caller to redirect to:
@@ -61,7 +61,7 @@ func checkoutWorkflow(ctx dbos.DBOSContext, order Order) (string, error) {
// HTTP handler starts workflow and reads the payment URL
handle, _ := dbos.RunWorkflow(ctx, checkoutWorkflow, order)
-url, _ := dbos.GetEvent[string](ctx, handle.GetWorkflowID(), "paymentURL", 300*time.Second)
+url, _ := dbos.GetEventstring, "paymentURL", 300*time.Second)
```
`GetEvent` blocks until the event is set or the timeout expires. It returns the zero value of the type if the timeout is reached.
diff --git a/web-app/public/skills/dbos-golang/references/comm-messages.md b/web-app/public/skills/dbos-golang/references/comm-messages.md
index bfc802f6..bb89ce36 100644
--- a/web-app/public/skills/dbos-golang/references/comm-messages.md
+++ b/web-app/public/skills/dbos-golang/references/comm-messages.md
@@ -21,7 +21,7 @@ ch := make(chan string) // Not durable!
```go
func checkoutWorkflow(ctx dbos.DBOSContext, orderID string) (string, error) {
// Wait for payment notification (timeout 120 seconds)
- notification, err := dbos.Recv[string](ctx, "payment_status", 120*time.Second)
+ notification, err := dbos.Recvstring
if err != nil {
return "", err
}
diff --git a/web-app/public/skills/dbos-golang/references/comm-streaming.md b/web-app/public/skills/dbos-golang/references/comm-streaming.md
index 2b213fca..752bb932 100644
--- a/web-app/public/skills/dbos-golang/references/comm-streaming.md
+++ b/web-app/public/skills/dbos-golang/references/comm-streaming.md
@@ -43,13 +43,13 @@ func processWorkflow(ctx dbos.DBOSContext, items []string) (string, error) {
// Read the stream synchronously (blocks until closed)
handle, _ := dbos.RunWorkflow(ctx, processWorkflow, items)
-values, closed, err := dbos.ReadStream[string](ctx, handle.GetWorkflowID(), "results")
+values, closed, err := dbos.ReadStreamstring, "results")
```
**Async stream reading with channels:**
```go
-ch, err := dbos.ReadStreamAsync[string](ctx, handle.GetWorkflowID(), "results")
+ch, err := dbos.ReadStreamAsyncstring, "results")
if err != nil {
log.Fatal(err)
}
diff --git a/web-app/public/skills/dbos-golang/references/workflow-background.md b/web-app/public/skills/dbos-golang/references/workflow-background.md
index c927e34e..563cbac4 100644
--- a/web-app/public/skills/dbos-golang/references/workflow-background.md
+++ b/web-app/public/skills/dbos-golang/references/workflow-background.md
@@ -53,7 +53,7 @@ func main() {
Retrieve a handle later by workflow ID:
```go
-handle, err := dbos.RetrieveWorkflow[string](ctx, workflowID)
+handle, err := dbos.RetrieveWorkflowstring
result, err := handle.GetResult()
```
diff --git a/web-app/public/skills/dbos-golang/references/workflow-constraints.md b/web-app/public/skills/dbos-golang/references/workflow-constraints.md
index fba99afc..15b65fa9 100644
--- a/web-app/public/skills/dbos-golang/references/workflow-constraints.md
+++ b/web-app/public/skills/dbos-golang/references/workflow-constraints.md
@@ -53,7 +53,7 @@ func myWorkflow(ctx dbos.DBOSContext, input string) (string, error) {
return "", err
}
// Receive messages from the workflow
- msg, err := dbos.Recv[string](ctx, "topic", 60*time.Second)
+ msg, err := dbos.Recvstring
// Set events from the workflow
dbos.SetEvent(ctx, "status", "done")
return data, nil
diff --git a/web-app/public/skills/dbos-golang/references/workflow-control.md b/web-app/public/skills/dbos-golang/references/workflow-control.md
index 20dea2c3..56542b39 100644
--- a/web-app/public/skills/dbos-golang/references/workflow-control.md
+++ b/web-app/public/skills/dbos-golang/references/workflow-control.md
@@ -24,7 +24,7 @@ handle, _ := dbos.RunWorkflow(ctx, processTask, "data")
err := dbos.CancelWorkflow(ctx, workflowID)
// Resume from the last completed step
-handle, err := dbos.ResumeWorkflow[string](ctx, workflowID)
+handle, err := dbos.ResumeWorkflowstring
result, err := handle.GetResult()
```
@@ -39,12 +39,7 @@ Fork a workflow from a specific step:
steps, err := dbos.GetWorkflowSteps(ctx, workflowID)
// Fork from a specific step
-forkHandle, err := dbos.ForkWorkflow[string](ctx, dbos.ForkWorkflowInput{
- OriginalWorkflowID: workflowID,
- StartStep: 2, // Fork from step 2
- ForkedWorkflowID: "new-wf-id", // Optional
- ApplicationVersion: "2.0.0", // Optional
-})
+forkHandle, err := dbos.ForkWorkflowstring
result, err := forkHandle.GetResult()
```
diff --git a/web-app/public/skills/dbos-python/SKILL.md b/web-app/public/skills/dbos-python/SKILL.md
index 5bfe261a..f516acf5 100644
--- a/web-app/public/skills/dbos-python/SKILL.md
+++ b/web-app/public/skills/dbos-python/SKILL.md
@@ -1,6 +1,6 @@
---
name: dbos-python
-description: DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSClient from external applications, or building applications that need to be resilient to failures.
+description: "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC..."
risk: safe
source: https://docs.dbos.dev/
license: MIT
diff --git a/web-app/public/skills/dbos-typescript/SKILL.md b/web-app/public/skills/dbos-typescript/SKILL.md
index 33ef7823..5504f648 100644
--- a/web-app/public/skills/dbos-typescript/SKILL.md
+++ b/web-app/public/skills/dbos-typescript/SKILL.md
@@ -1,6 +1,6 @@
---
name: dbos-typescript
-description: DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, using DBOSClient from external applications, or building applications that need to be resilient to failures.
+description: "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi..."
risk: safe
source: https://docs.dbos.dev/
license: MIT
diff --git a/web-app/public/skills/dbt-transformation-patterns/SKILL.md b/web-app/public/skills/dbt-transformation-patterns/SKILL.md
index 1a5ae9f4..63831f68 100644
--- a/web-app/public/skills/dbt-transformation-patterns/SKILL.md
+++ b/web-app/public/skills/dbt-transformation-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: dbt-transformation-patterns
-description: Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.
+description: "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ..."
+risk: unknown
+source: community
---
# dbt Transformation Patterns
diff --git a/web-app/public/skills/ddd-context-mapping/SKILL.md b/web-app/public/skills/ddd-context-mapping/SKILL.md
new file mode 100644
index 00000000..ff71c0f3
--- /dev/null
+++ b/web-app/public/skills/ddd-context-mapping/SKILL.md
@@ -0,0 +1,51 @@
+---
+name: ddd-context-mapping
+description: "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns."
+risk: safe
+source: self
+tags: [ddd, context-map, anti-corruption-layer, integration]
+---
+
+# DDD Context Mapping
+
+## Use this skill when
+
+- Defining integration patterns between bounded contexts.
+- Preventing domain leakage across service boundaries.
+- Planning anti-corruption layers during migration.
+- Clarifying upstream and downstream ownership for contracts.
+
+## Do not use this skill when
+
+- You have a single-context system with no integrations.
+- You only need internal class design.
+- You are selecting cloud infrastructure tooling.
+
+## Instructions
+
+1. List all context pairs and dependency direction.
+2. Choose relationship patterns per pair.
+3. Define translation rules and ownership boundaries.
+4. Add failure modes, fallback behavior, and versioning policy.
+
+If detailed mapping structures are needed, open `references/context-map-patterns.md`.
+
+## Output requirements
+
+- Relationship map for all context pairs
+- Contract ownership matrix
+- Translation and anti-corruption decisions
+- Known coupling risks and mitigation plan
+
+## Examples
+
+```text
+Use @ddd-context-mapping to define how Checkout integrates with Billing,
+Inventory, and Fraud contexts, including ACL and contract ownership.
+```
+
+## Limitations
+
+- This skill does not replace API-level schema design.
+- It does not guarantee organizational alignment by itself.
+- It should be revisited when team ownership changes.
diff --git a/web-app/public/skills/ddd-context-mapping/references/context-map-patterns.md b/web-app/public/skills/ddd-context-mapping/references/context-map-patterns.md
new file mode 100644
index 00000000..c9019b2a
--- /dev/null
+++ b/web-app/public/skills/ddd-context-mapping/references/context-map-patterns.md
@@ -0,0 +1,25 @@
+# Context Mapping Patterns
+
+## Common relationship patterns
+
+- Partnership
+- Shared Kernel
+- Customer-Supplier
+- Conformist
+- Anti-Corruption Layer
+- Open Host Service
+- Published Language
+
+## Mapping template
+
+| Upstream context | Downstream context | Pattern | Contract owner | Translation needed |
+| --- | --- | --- | --- | --- |
+| Billing | Checkout | Customer-Supplier | Billing | Yes |
+| Identity | Checkout | Conformist | Identity | No |
+
+## ACL checklist
+
+- Define canonical domain model for receiving context.
+- Translate external terms into local ubiquitous language.
+- Keep ACL code at boundary, not inside domain core.
+- Add contract tests for mapped behavior.
diff --git a/web-app/public/skills/ddd-strategic-design/SKILL.md b/web-app/public/skills/ddd-strategic-design/SKILL.md
new file mode 100644
index 00000000..e34c549b
--- /dev/null
+++ b/web-app/public/skills/ddd-strategic-design/SKILL.md
@@ -0,0 +1,51 @@
+---
+name: ddd-strategic-design
+description: "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains."
+risk: safe
+source: self
+tags: [ddd, strategic-design, bounded-context, ubiquitous-language]
+---
+
+# DDD Strategic Design
+
+## Use this skill when
+
+- Defining core, supporting, and generic subdomains.
+- Splitting a monolith or service landscape by domain boundaries.
+- Aligning teams and ownership with bounded contexts.
+- Building a shared ubiquitous language with domain experts.
+
+## Do not use this skill when
+
+- The domain model is stable and already well bounded.
+- You need tactical code patterns only.
+- The task is purely infrastructure or UI oriented.
+
+## Instructions
+
+1. Extract domain capabilities and classify subdomains.
+2. Define bounded contexts around consistency and ownership.
+3. Establish a ubiquitous language glossary and anti-terms.
+4. Capture context boundaries in ADRs before implementation.
+
+If detailed templates are needed, open `references/strategic-design-template.md`.
+
+## Required artifacts
+
+- Subdomain classification table
+- Bounded context catalog
+- Glossary with canonical terms
+- Boundary decisions with rationale
+
+## Examples
+
+```text
+Use @ddd-strategic-design to map our commerce domain into bounded contexts,
+classify subdomains, and propose team ownership.
+```
+
+## Limitations
+
+- This skill does not produce executable code.
+- It cannot infer business truth without stakeholder input.
+- It should be followed by tactical design before implementation.
diff --git a/web-app/public/skills/ddd-strategic-design/references/strategic-design-template.md b/web-app/public/skills/ddd-strategic-design/references/strategic-design-template.md
new file mode 100644
index 00000000..d98c262d
--- /dev/null
+++ b/web-app/public/skills/ddd-strategic-design/references/strategic-design-template.md
@@ -0,0 +1,22 @@
+# Strategic Design Template
+
+## Subdomain classification
+
+| Capability | Subdomain type | Why | Owner team |
+| --- | --- | --- | --- |
+| Pricing | Core | Differentiates business value | Commerce |
+| Identity | Supporting | Needed but not differentiating | Platform |
+
+## Bounded context catalog
+
+| Context | Responsibility | Upstream dependencies | Downstream consumers |
+| --- | --- | --- | --- |
+| Catalog | Product data lifecycle | Supplier feed | Checkout, Search |
+| Checkout | Order placement and payment authorization | Catalog, Pricing | Fulfillment, Billing |
+
+## Ubiquitous language
+
+| Term | Definition | Context |
+| --- | --- | --- |
+| Order | Confirmed purchase request | Checkout |
+| Reservation | Temporary inventory hold | Fulfillment |
diff --git a/web-app/public/skills/ddd-tactical-patterns/SKILL.md b/web-app/public/skills/ddd-tactical-patterns/SKILL.md
new file mode 100644
index 00000000..9cc459ee
--- /dev/null
+++ b/web-app/public/skills/ddd-tactical-patterns/SKILL.md
@@ -0,0 +1,52 @@
+---
+name: ddd-tactical-patterns
+description: "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants."
+risk: safe
+source: self
+tags: [ddd, tactical, aggregates, value-objects, domain-events]
+---
+
+# DDD Tactical Patterns
+
+## Use this skill when
+
+- Translating domain rules into code structures.
+- Designing aggregate boundaries and invariants.
+- Refactoring an anemic model into behavior-rich domain objects.
+- Defining repository contracts and domain event boundaries.
+
+## Do not use this skill when
+
+- You are still defining strategic boundaries.
+- The task is only API documentation or UI layout.
+- Full DDD complexity is not justified.
+
+## Instructions
+
+1. Identify invariants first and design aggregates around them.
+2. Model immutable value objects for validated concepts.
+3. Keep domain behavior in domain objects, not controllers.
+4. Emit domain events for meaningful state transitions.
+5. Keep repositories at aggregate root boundaries.
+
+If detailed checklists are needed, open `references/tactical-checklist.md`.
+
+## Example
+
+```typescript
+class Order {
+ private status: "draft" | "submitted" = "draft";
+
+ submit(itemsCount: number): void {
+ if (itemsCount === 0) throw new Error("Order cannot be submitted empty");
+ if (this.status !== "draft") throw new Error("Order already submitted");
+ this.status = "submitted";
+ }
+}
+```
+
+## Limitations
+
+- This skill does not define deployment architecture.
+- It does not choose databases or transport protocols.
+- It should be paired with testing patterns for invariant coverage.
diff --git a/web-app/public/skills/ddd-tactical-patterns/references/tactical-checklist.md b/web-app/public/skills/ddd-tactical-patterns/references/tactical-checklist.md
new file mode 100644
index 00000000..fa1e2cd1
--- /dev/null
+++ b/web-app/public/skills/ddd-tactical-patterns/references/tactical-checklist.md
@@ -0,0 +1,25 @@
+# Tactical Pattern Checklist
+
+## Aggregate design
+
+- One aggregate root per transaction boundary
+- Invariants enforced inside aggregate methods
+- Avoid cross-aggregate synchronous consistency rules
+
+## Value objects
+
+- Immutable by default
+- Validation at construction
+- Equality by value, not identity
+
+## Repositories
+
+- Persist and load aggregate roots only
+- Expose domain-friendly query methods
+- Avoid leaking ORM entities into domain layer
+
+## Domain events
+
+- Past-tense event names (for example, `OrderSubmitted`)
+- Include minimal, stable event payloads
+- Version event schema before breaking changes
diff --git a/web-app/public/skills/debugger/SKILL.md b/web-app/public/skills/debugger/SKILL.md
index d197878e..303c9145 100644
--- a/web-app/public/skills/debugger/SKILL.md
+++ b/web-app/public/skills/debugger/SKILL.md
@@ -1,9 +1,11 @@
---
name: debugger
-description: Debugging specialist for errors, test failures, and unexpected
+description: "Debugging specialist for errors, test failures, and unexpected"
behavior. Use proactively when encountering any issues.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/debugging-strategies/SKILL.md b/web-app/public/skills/debugging-strategies/SKILL.md
index 95c006d0..f97d3d54 100644
--- a/web-app/public/skills/debugging-strategies/SKILL.md
+++ b/web-app/public/skills/debugging-strategies/SKILL.md
@@ -1,6 +1,8 @@
---
name: debugging-strategies
-description: Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
+description: "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss..."
+risk: unknown
+source: community
---
# Debugging Strategies
diff --git a/web-app/public/skills/debugging-toolkit-smart-debug/SKILL.md b/web-app/public/skills/debugging-toolkit-smart-debug/SKILL.md
index d79ed178..bcd2a2cd 100644
--- a/web-app/public/skills/debugging-toolkit-smart-debug/SKILL.md
+++ b/web-app/public/skills/debugging-toolkit-smart-debug/SKILL.md
@@ -1,6 +1,8 @@
---
name: debugging-toolkit-smart-debug
description: "Use when working with debugging toolkit smart debug"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/deep-research/SKILL.md b/web-app/public/skills/deep-research/SKILL.md
index 57fdccdb..cf6adc7e 100644
--- a/web-app/public/skills/deep-research/SKILL.md
+++ b/web-app/public/skills/deep-research/SKILL.md
@@ -1,6 +1,6 @@
---
name: deep-research
-description: "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 minutes but produces detailed, cited reports. Costs $2-5 per task."
+description: "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ..."
source: "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research"
risk: safe
---
diff --git a/web-app/public/skills/defi-protocol-templates/SKILL.md b/web-app/public/skills/defi-protocol-templates/SKILL.md
index e2d8a292..81229277 100644
--- a/web-app/public/skills/defi-protocol-templates/SKILL.md
+++ b/web-app/public/skills/defi-protocol-templates/SKILL.md
@@ -1,6 +1,8 @@
---
name: defi-protocol-templates
-description: Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.
+description: "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols."
+risk: unknown
+source: community
---
# DeFi Protocol Templates
diff --git a/web-app/public/skills/dependency-management-deps-audit/SKILL.md b/web-app/public/skills/dependency-management-deps-audit/SKILL.md
index 3df519a5..f8071de7 100644
--- a/web-app/public/skills/dependency-management-deps-audit/SKILL.md
+++ b/web-app/public/skills/dependency-management-deps-audit/SKILL.md
@@ -1,6 +1,8 @@
---
name: dependency-management-deps-audit
-description: "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies."
+description: "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,..."
+risk: unknown
+source: community
---
# Dependency Audit and Security Analysis
diff --git a/web-app/public/skills/dependency-upgrade/SKILL.md b/web-app/public/skills/dependency-upgrade/SKILL.md
index f290347f..f0285705 100644
--- a/web-app/public/skills/dependency-upgrade/SKILL.md
+++ b/web-app/public/skills/dependency-upgrade/SKILL.md
@@ -1,6 +1,8 @@
---
name: dependency-upgrade
-description: Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
+description: "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea..."
+risk: unknown
+source: community
---
# Dependency Upgrade
diff --git a/web-app/public/skills/deployment-engineer/SKILL.md b/web-app/public/skills/deployment-engineer/SKILL.md
index 8bc40dd5..78ec5db7 100644
--- a/web-app/public/skills/deployment-engineer/SKILL.md
+++ b/web-app/public/skills/deployment-engineer/SKILL.md
@@ -1,6 +1,6 @@
---
name: deployment-engineer
-description: Expert deployment engineer specializing in modern CI/CD pipelines,
+description: "Expert deployment engineer specializing in modern CI/CD pipelines,"
GitOps workflows, and advanced deployment automation. Masters GitHub Actions,
ArgoCD/Flux, progressive delivery, container security, and platform
engineering. Handles zero-downtime deployments, security scanning, and
@@ -8,6 +8,8 @@ description: Expert deployment engineer specializing in modern CI/CD pipelines,
implementation, or deployment automation.
metadata:
model: haiku
+risk: unknown
+source: community
---
You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.
diff --git a/web-app/public/skills/deployment-pipeline-design/SKILL.md b/web-app/public/skills/deployment-pipeline-design/SKILL.md
index ee9ce36e..edffe482 100644
--- a/web-app/public/skills/deployment-pipeline-design/SKILL.md
+++ b/web-app/public/skills/deployment-pipeline-design/SKILL.md
@@ -1,6 +1,8 @@
---
name: deployment-pipeline-design
-description: Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
+description: "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi..."
+risk: unknown
+source: community
---
# Deployment Pipeline Design
diff --git a/web-app/public/skills/deployment-procedures/SKILL.md b/web-app/public/skills/deployment-procedures/SKILL.md
index 450e46bf..3b8dbebd 100644
--- a/web-app/public/skills/deployment-procedures/SKILL.md
+++ b/web-app/public/skills/deployment-procedures/SKILL.md
@@ -1,7 +1,9 @@
---
name: deployment-procedures
-description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
+description: "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts."
allowed-tools: Read, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Deployment Procedures
@@ -239,3 +241,6 @@ Before deploying:
---
> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/deployment-validation-config-validate/SKILL.md b/web-app/public/skills/deployment-validation-config-validate/SKILL.md
index c25303d5..31ba4718 100644
--- a/web-app/public/skills/deployment-validation-config-validate/SKILL.md
+++ b/web-app/public/skills/deployment-validation-config-validate/SKILL.md
@@ -1,6 +1,8 @@
---
name: deployment-validation-config-validate
description: "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat"
+risk: unknown
+source: community
---
# Configuration Validation
diff --git a/web-app/public/skills/design-orchestration/SKILL.md b/web-app/public/skills/design-orchestration/SKILL.md
index 991fbe34..f41b654a 100644
--- a/web-app/public/skills/design-orchestration/SKILL.md
+++ b/web-app/public/skills/design-orchestration/SKILL.md
@@ -1,10 +1,12 @@
---
name: design-orchestration
-description: >
+description:
Orchestrates design workflows by routing work through
brainstorming, multi-agent review, and execution readiness
in the correct order. Prevents premature implementation,
skipped validation, and unreviewed high-risk designs.
+risk: unknown
+source: community
---
# Design Orchestration (Meta-Skill)
@@ -165,3 +167,6 @@ Good systems fail early.
Bad systems fail in production.
This meta-skill exists to enforce the former.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/development/SKILL.md b/web-app/public/skills/development/SKILL.md
new file mode 100644
index 00000000..0ff988da
--- /dev/null
+++ b/web-app/public/skills/development/SKILL.md
@@ -0,0 +1,263 @@
+---
+name: development
+description: "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery."
+source: personal
+risk: safe
+domain: software-development
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Development Workflow Bundle
+
+## Overview
+
+Consolidated workflow for end-to-end software development covering web, mobile, and backend development. This bundle orchestrates skills for building production-ready applications from scaffolding to deployment.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building new web or mobile applications
+- Adding features to existing applications
+- Refactoring or modernizing legacy code
+- Setting up new projects with best practices
+- Full-stack feature development
+- Cross-platform application development
+
+## Workflow Phases
+
+### Phase 1: Project Setup and Scaffolding
+
+#### Skills to Invoke
+- `app-builder` - Main application building orchestrator
+- `senior-fullstack` - Full-stack development guidance
+- `environment-setup-guide` - Development environment setup
+- `concise-planning` - Task planning and breakdown
+
+#### Actions
+1. Determine project type (web, mobile, full-stack)
+2. Select technology stack
+3. Scaffold project structure
+4. Configure development environment
+5. Set up version control and CI/CD
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to scaffold a new React + Node.js full-stack application
+```
+
+```
+Use @senior-fullstack to set up a Next.js 14 project with App Router
+```
+
+```
+Use @environment-setup-guide to configure my development environment
+```
+
+### Phase 2: Frontend Development
+
+#### Skills to Invoke
+- `frontend-developer` - React/Next.js component development
+- `frontend-design` - UI/UX design implementation
+- `react-patterns` - Modern React patterns
+- `typescript-pro` - TypeScript best practices
+- `tailwind-patterns` - Tailwind CSS styling
+- `nextjs-app-router-patterns` - Next.js 14+ patterns
+
+#### Actions
+1. Design component architecture
+2. Implement UI components
+3. Set up state management
+4. Configure routing
+5. Apply styling and theming
+6. Implement responsive design
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create a dashboard component with React and TypeScript
+```
+
+```
+Use @react-patterns to implement proper state management with Zustand
+```
+
+```
+Use @tailwind-patterns to style components with a consistent design system
+```
+
+### Phase 3: Backend Development
+
+#### Skills to Invoke
+- `backend-architect` - Backend architecture design
+- `backend-dev-guidelines` - Backend development standards
+- `nodejs-backend-patterns` - Node.js/Express patterns
+- `fastapi-pro` - FastAPI development
+- `api-design-principles` - REST/GraphQL API design
+- `auth-implementation-patterns` - Authentication implementation
+
+#### Actions
+1. Design API architecture
+2. Implement REST/GraphQL endpoints
+3. Set up database connections
+4. Implement authentication/authorization
+5. Configure middleware
+6. Set up error handling
+
+#### Copy-Paste Prompts
+```
+Use @backend-architect to design a microservices architecture for my application
+```
+
+```
+Use @nodejs-backend-patterns to create Express.js API endpoints
+```
+
+```
+Use @auth-implementation-patterns to implement JWT authentication
+```
+
+### Phase 4: Database Development
+
+#### Skills to Invoke
+- `database-architect` - Database design
+- `database-design` - Schema design principles
+- `prisma-expert` - Prisma ORM
+- `postgresql` - PostgreSQL optimization
+- `neon-postgres` - Serverless Postgres
+
+#### Actions
+1. Design database schema
+2. Create migrations
+3. Set up ORM
+4. Optimize queries
+5. Configure connection pooling
+
+#### Copy-Paste Prompts
+```
+Use @database-architect to design a normalized schema for an e-commerce platform
+```
+
+```
+Use @prisma-expert to set up Prisma ORM with TypeScript
+```
+
+### Phase 5: Testing
+
+#### Skills to Invoke
+- `test-driven-development` - TDD workflow
+- `javascript-testing-patterns` - Jest/Vitest testing
+- `python-testing-patterns` - pytest testing
+- `e2e-testing-patterns` - Playwright/Cypress E2E
+- `playwright-skill` - Browser automation testing
+
+#### Actions
+1. Write unit tests
+2. Create integration tests
+3. Set up E2E tests
+4. Configure CI test runners
+5. Achieve coverage targets
+
+#### Copy-Paste Prompts
+```
+Use @test-driven-development to implement features with TDD
+```
+
+```
+Use @playwright-skill to create E2E tests for critical user flows
+```
+
+### Phase 6: Code Quality and Review
+
+#### Skills to Invoke
+- `code-reviewer` - AI-powered code review
+- `clean-code` - Clean code principles
+- `lint-and-validate` - Linting and validation
+- `security-scanning-security-sast` - Static security analysis
+
+#### Actions
+1. Run linters and formatters
+2. Perform code review
+3. Fix code quality issues
+4. Run security scans
+5. Address vulnerabilities
+
+#### Copy-Paste Prompts
+```
+Use @code-reviewer to review my pull request
+```
+
+```
+Use @lint-and-validate to check code quality
+```
+
+### Phase 7: Build and Deployment
+
+#### Skills to Invoke
+- `deployment-engineer` - Deployment orchestration
+- `docker-expert` - Containerization
+- `vercel-deployment` - Vercel deployment
+- `github-actions-templates` - CI/CD workflows
+- `cicd-automation-workflow-automate` - CI/CD automation
+
+#### Actions
+1. Create Dockerfiles
+2. Configure build pipelines
+3. Set up deployment workflows
+4. Configure environment variables
+5. Deploy to production
+
+#### Copy-Paste Prompts
+```
+Use @docker-expert to containerize my application
+```
+
+```
+Use @vercel-deployment to deploy my Next.js app to production
+```
+
+```
+Use @github-actions-templates to set up CI/CD pipeline
+```
+
+## Technology-Specific Workflows
+
+### React/Next.js Development
+```
+Skills: frontend-developer, react-patterns, nextjs-app-router-patterns, typescript-pro, tailwind-patterns
+```
+
+### Python/FastAPI Development
+```
+Skills: fastapi-pro, python-pro, python-patterns, pydantic-models-py
+```
+
+### Node.js/Express Development
+```
+Skills: nodejs-backend-patterns, javascript-pro, typescript-pro, express (via nodejs-backend-patterns)
+```
+
+### Full-Stack Development
+```
+Skills: senior-fullstack, app-builder, frontend-developer, backend-architect, database-architect
+```
+
+### Mobile Development
+```
+Skills: mobile-developer, react-native-architecture, flutter-expert, ios-developer
+```
+
+## Quality Gates
+
+Before moving to next phase, verify:
+- [ ] All tests passing
+- [ ] Code review completed
+- [ ] Security scan passed
+- [ ] Linting/formatting clean
+- [ ] Documentation updated
+
+## Related Workflow Bundles
+
+- `wordpress` - WordPress-specific development
+- `security-audit` - Security testing workflow
+- `testing-qa` - Comprehensive testing workflow
+- `documentation` - Documentation generation workflow
diff --git a/web-app/public/skills/devops-troubleshooter/SKILL.md b/web-app/public/skills/devops-troubleshooter/SKILL.md
index 33c72a5e..94a3fbfc 100644
--- a/web-app/public/skills/devops-troubleshooter/SKILL.md
+++ b/web-app/public/skills/devops-troubleshooter/SKILL.md
@@ -1,6 +1,6 @@
---
name: devops-troubleshooter
-description: Expert DevOps troubleshooter specializing in rapid incident
+description: "Expert DevOps troubleshooter specializing in rapid incident"
response, advanced debugging, and modern observability. Masters log analysis,
distributed tracing, Kubernetes debugging, performance optimization, and root
cause analysis. Handles production outages, system reliability, and preventive
@@ -8,6 +8,8 @@ description: Expert DevOps troubleshooter specializing in rapid incident
troubleshooting.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/discord-automation/SKILL.md b/web-app/public/skills/discord-automation/SKILL.md
index ebe29470..c2b1d909 100644
--- a/web-app/public/skills/discord-automation/SKILL.md
+++ b/web-app/public/skills/discord-automation/SKILL.md
@@ -3,6 +3,8 @@ name: discord-automation
description: "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Discord Automation via Rube MCP
@@ -185,3 +187,6 @@ Permissions are combined using bitwise OR:
| Clear reactions | DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS | channel_id, message_id |
| Test auth | DISCORDBOT_TEST_AUTH | (none) |
| Get channel | DISCORDBOT_GET_CHANNEL | channel_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/discord-bot-architect/SKILL.md b/web-app/public/skills/discord-bot-architect/SKILL.md
index cd823a15..ae9cc70b 100644
--- a/web-app/public/skills/discord-bot-architect/SKILL.md
+++ b/web-app/public/skills/discord-bot-architect/SKILL.md
@@ -2,6 +2,7 @@
name: discord-bot-architect
description: "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Discord Bot Architect
@@ -275,3 +276,6 @@ cause missed heartbeats and disconnections.
| Issue | medium | ## Development: Use guild commands |
| Issue | medium | ## Never block the event loop |
| Issue | medium | ## Show modal immediately |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/dispatching-parallel-agents/SKILL.md b/web-app/public/skills/dispatching-parallel-agents/SKILL.md
index 33b14859..9fb6d3ec 100644
--- a/web-app/public/skills/dispatching-parallel-agents/SKILL.md
+++ b/web-app/public/skills/dispatching-parallel-agents/SKILL.md
@@ -1,6 +1,8 @@
---
name: dispatching-parallel-agents
-description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
+description: "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies"
+risk: unknown
+source: community
---
# Dispatching Parallel Agents
diff --git a/web-app/public/skills/distributed-debugging-debug-trace/SKILL.md b/web-app/public/skills/distributed-debugging-debug-trace/SKILL.md
index 7b8d99aa..dc8875c8 100644
--- a/web-app/public/skills/distributed-debugging-debug-trace/SKILL.md
+++ b/web-app/public/skills/distributed-debugging-debug-trace/SKILL.md
@@ -1,6 +1,8 @@
---
name: distributed-debugging-debug-trace
-description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments."
+description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an..."
+risk: unknown
+source: community
---
# Debug and Trace Configuration
diff --git a/web-app/public/skills/distributed-debugging-debug-trace/resources/implementation-playbook.md b/web-app/public/skills/distributed-debugging-debug-trace/resources/implementation-playbook.md
index 01e8f4bd..9ce7baef 100644
--- a/web-app/public/skills/distributed-debugging-debug-trace/resources/implementation-playbook.md
+++ b/web-app/public/skills/distributed-debugging-debug-trace/resources/implementation-playbook.md
@@ -1031,7 +1031,7 @@ class ProductionDebugger {
['log', 'debug', 'info', 'warn', 'error'].forEach(method => {
console[method] = (...args) => {
req.debugContext.log(req.id, method, args[0], args.slice(1));
- originalConsole[method](...args);
+ originalConsolemethod;
};
});
diff --git a/web-app/public/skills/distributed-tracing/SKILL.md b/web-app/public/skills/distributed-tracing/SKILL.md
index 1721b8ba..3c2c6e95 100644
--- a/web-app/public/skills/distributed-tracing/SKILL.md
+++ b/web-app/public/skills/distributed-tracing/SKILL.md
@@ -1,6 +1,8 @@
---
name: distributed-tracing
-description: Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
+description: "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem..."
+risk: unknown
+source: community
---
# Distributed Tracing
diff --git a/web-app/public/skills/django-pro/SKILL.md b/web-app/public/skills/django-pro/SKILL.md
index b9f14e9d..06737455 100644
--- a/web-app/public/skills/django-pro/SKILL.md
+++ b/web-app/public/skills/django-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: django-pro
-description: Master Django 5.x with async views, DRF, Celery, and Django
+description: "Master Django 5.x with async views, DRF, Celery, and Django"
Channels. Build scalable web applications with proper architecture, testing,
and deployment. Use PROACTIVELY for Django development, ORM optimization, or
complex Django patterns.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/doc-coauthoring/SKILL.md b/web-app/public/skills/doc-coauthoring/SKILL.md
index a5a69839..0239ed57 100644
--- a/web-app/public/skills/doc-coauthoring/SKILL.md
+++ b/web-app/public/skills/doc-coauthoring/SKILL.md
@@ -1,6 +1,8 @@
---
name: doc-coauthoring
-description: Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
+description: "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ..."
+risk: unknown
+source: community
---
# Doc Co-Authoring Workflow
@@ -373,3 +375,6 @@ Announce document completion. Provide a few final tips:
- Don't rush through stages
- Each iteration should make meaningful improvements
- The goal is a document that actually works for readers
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/docker-expert/SKILL.md b/web-app/public/skills/docker-expert/SKILL.md
index 381a5ca0..48082f75 100644
--- a/web-app/public/skills/docker-expert/SKILL.md
+++ b/web-app/public/skills/docker-expert/SKILL.md
@@ -1,9 +1,11 @@
---
name: docker-expert
-description: Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY for Dockerfile optimization, container issues, image size problems, security hardening, networking, and orchestration challenges.
+description: "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f..."
category: devops
color: blue
displayName: Docker Expert
+risk: unknown
+source: community
---
# Docker Expert
@@ -406,4 +408,7 @@ When reviewing Docker configurations, focus on:
- Establish container standards for CI/CD integration
- Define security baselines for production orchestration
-I provide comprehensive Docker containerization expertise with focus on practical optimization, security hardening, and production-ready patterns. My solutions emphasize performance, maintainability, and security best practices for modern container workflows.
\ No newline at end of file
+I provide comprehensive Docker containerization expertise with focus on practical optimization, security hardening, and production-ready patterns. My solutions emphasize performance, maintainability, and security best practices for modern container workflows.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/docs-architect/SKILL.md b/web-app/public/skills/docs-architect/SKILL.md
index 39dc4d16..4f7a0fa1 100644
--- a/web-app/public/skills/docs-architect/SKILL.md
+++ b/web-app/public/skills/docs-architect/SKILL.md
@@ -1,11 +1,13 @@
---
name: docs-architect
-description: Creates comprehensive technical documentation from existing
+description: "Creates comprehensive technical documentation from existing"
codebases. Analyzes architecture, design patterns, and implementation details
to produce long-form technical manuals and ebooks. Use PROACTIVELY for system
documentation, architecture guides, or technical deep-dives.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/documentation-generation-doc-generate/SKILL.md b/web-app/public/skills/documentation-generation-doc-generate/SKILL.md
index 3a069407..385bb57f 100644
--- a/web-app/public/skills/documentation-generation-doc-generate/SKILL.md
+++ b/web-app/public/skills/documentation-generation-doc-generate/SKILL.md
@@ -1,6 +1,8 @@
---
name: documentation-generation-doc-generate
-description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices."
+description: "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI..."
+risk: unknown
+source: community
---
# Automated Documentation Generation
diff --git a/web-app/public/skills/documentation-generation-doc-generate/resources/implementation-playbook.md b/web-app/public/skills/documentation-generation-doc-generate/resources/implementation-playbook.md
index b361f364..e1c4f9d9 100644
--- a/web-app/public/skills/documentation-generation-doc-generate/resources/implementation-playbook.md
+++ b/web-app/public/skills/documentation-generation-doc-generate/resources/implementation-playbook.md
@@ -359,7 +359,7 @@ pytest --cov=your_package
## License
-This project is licensed under the ${LICENSE} License - see the [LICENSE](LICENSE) file for details.
+This project is licensed under the ${LICENSE} License - see the LICENSE file for details.
```
### Example 5: Function Documentation Generator
diff --git a/web-app/public/skills/documentation-templates/SKILL.md b/web-app/public/skills/documentation-templates/SKILL.md
index 37b55c55..0955b6e8 100644
--- a/web-app/public/skills/documentation-templates/SKILL.md
+++ b/web-app/public/skills/documentation-templates/SKILL.md
@@ -1,7 +1,9 @@
---
name: documentation-templates
-description: Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
+description: "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Documentation Templates
@@ -48,8 +50,8 @@ Brief one-line description.
## Documentation
-- [API Reference](./docs/api.md)
-- [Architecture](./docs/architecture.md)
+- API Reference
+- Architecture
## License
@@ -192,3 +194,6 @@ For RAG indexing:
---
> **Remember:** Templates are starting points. Adapt to your project's needs.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/documentation/SKILL.md b/web-app/public/skills/documentation/SKILL.md
new file mode 100644
index 00000000..02111220
--- /dev/null
+++ b/web-app/public/skills/documentation/SKILL.md
@@ -0,0 +1,261 @@
+---
+name: documentation
+description: "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing."
+source: personal
+risk: safe
+domain: documentation
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Documentation Workflow Bundle
+
+## Overview
+
+Comprehensive documentation workflow for generating API documentation, architecture documentation, README files, code comments, and technical content from codebases.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating project documentation
+- Generating API documentation
+- Writing architecture docs
+- Documenting code
+- Creating user guides
+- Maintaining wikis
+
+## Workflow Phases
+
+### Phase 1: Documentation Planning
+
+#### Skills to Invoke
+- `docs-architect` - Documentation architecture
+- `documentation-templates` - Documentation templates
+
+#### Actions
+1. Identify documentation needs
+2. Choose documentation tools
+3. Plan documentation structure
+4. Define style guidelines
+5. Set up documentation site
+
+#### Copy-Paste Prompts
+```
+Use @docs-architect to plan documentation structure
+```
+
+```
+Use @documentation-templates to set up documentation
+```
+
+### Phase 2: API Documentation
+
+#### Skills to Invoke
+- `api-documenter` - API documentation
+- `api-documentation-generator` - Auto-generation
+- `openapi-spec-generation` - OpenAPI specs
+
+#### Actions
+1. Extract API endpoints
+2. Generate OpenAPI specs
+3. Create API reference
+4. Add usage examples
+5. Set up auto-generation
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to generate API documentation
+```
+
+```
+Use @openapi-spec-generation to create OpenAPI specs
+```
+
+### Phase 3: Architecture Documentation
+
+#### Skills to Invoke
+- `c4-architecture-c4-architecture` - C4 architecture
+- `c4-context` - Context diagrams
+- `c4-container` - Container diagrams
+- `c4-component` - Component diagrams
+- `c4-code` - Code diagrams
+- `mermaid-expert` - Mermaid diagrams
+
+#### Actions
+1. Create C4 diagrams
+2. Document architecture
+3. Generate sequence diagrams
+4. Document data flows
+5. Create deployment docs
+
+#### Copy-Paste Prompts
+```
+Use @c4-architecture-c4-architecture to create C4 diagrams
+```
+
+```
+Use @mermaid-expert to create architecture diagrams
+```
+
+### Phase 4: Code Documentation
+
+#### Skills to Invoke
+- `code-documentation-code-explain` - Code explanation
+- `code-documentation-doc-generate` - Doc generation
+- `documentation-generation-doc-generate` - Auto-generation
+
+#### Actions
+1. Extract code comments
+2. Generate JSDoc/TSDoc
+3. Create type documentation
+4. Document functions
+5. Add usage examples
+
+#### Copy-Paste Prompts
+```
+Use @code-documentation-code-explain to explain code
+```
+
+```
+Use @code-documentation-doc-generate to generate docs
+```
+
+### Phase 5: README and Getting Started
+
+#### Skills to Invoke
+- `readme` - README generation
+- `environment-setup-guide` - Setup guides
+- `tutorial-engineer` - Tutorial creation
+
+#### Actions
+1. Create README
+2. Write getting started guide
+3. Document installation
+4. Add usage examples
+5. Create troubleshooting guide
+
+#### Copy-Paste Prompts
+```
+Use @readme to create project README
+```
+
+```
+Use @tutorial-engineer to create tutorials
+```
+
+### Phase 6: Wiki and Knowledge Base
+
+#### Skills to Invoke
+- `wiki-architect` - Wiki architecture
+- `wiki-page-writer` - Wiki pages
+- `wiki-onboarding` - Onboarding docs
+- `wiki-qa` - Wiki Q&A
+- `wiki-researcher` - Wiki research
+- `wiki-vitepress` - VitePress wiki
+
+#### Actions
+1. Design wiki structure
+2. Create wiki pages
+3. Write onboarding guides
+4. Document processes
+5. Set up wiki site
+
+#### Copy-Paste Prompts
+```
+Use @wiki-architect to design wiki structure
+```
+
+```
+Use @wiki-page-writer to create wiki pages
+```
+
+```
+Use @wiki-onboarding to create onboarding docs
+```
+
+### Phase 7: Changelog and Release Notes
+
+#### Skills to Invoke
+- `changelog-automation` - Changelog generation
+- `wiki-changelog` - Changelog from git
+
+#### Actions
+1. Extract commit history
+2. Categorize changes
+3. Generate changelog
+4. Create release notes
+5. Publish updates
+
+#### Copy-Paste Prompts
+```
+Use @changelog-automation to generate changelog
+```
+
+```
+Use @wiki-changelog to create release notes
+```
+
+### Phase 8: Documentation Maintenance
+
+#### Skills to Invoke
+- `doc-coauthoring` - Collaborative writing
+- `reference-builder` - Reference docs
+
+#### Actions
+1. Review documentation
+2. Update outdated content
+3. Fix broken links
+4. Add new features
+5. Gather feedback
+
+#### Copy-Paste Prompts
+```
+Use @doc-coauthoring to collaborate on docs
+```
+
+## Documentation Types
+
+### Code-Level
+- JSDoc/TSDoc comments
+- Function documentation
+- Type definitions
+- Example code
+
+### API Documentation
+- Endpoint reference
+- Request/response schemas
+- Authentication guides
+- SDK documentation
+
+### Architecture Documentation
+- System overview
+- Component diagrams
+- Data flow diagrams
+- Deployment architecture
+
+### User Documentation
+- Getting started guides
+- User manuals
+- Tutorials
+- FAQs
+
+### Process Documentation
+- Runbooks
+- Onboarding guides
+- SOPs
+- Decision records
+
+## Quality Gates
+
+- [ ] All APIs documented
+- [ ] Architecture diagrams current
+- [ ] README up to date
+- [ ] Code comments helpful
+- [ ] Examples working
+- [ ] Links valid
+
+## Related Workflow Bundles
+
+- `development` - Development workflow
+- `testing-qa` - Documentation testing
+- `ai-ml` - AI documentation
diff --git a/web-app/public/skills/docusign-automation/SKILL.md b/web-app/public/skills/docusign-automation/SKILL.md
index b3cb0c9a..f013ad10 100644
--- a/web-app/public/skills/docusign-automation/SKILL.md
+++ b/web-app/public/skills/docusign-automation/SKILL.md
@@ -3,6 +3,8 @@ name: docusign-automation
description: "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# DocuSign Automation via Rube MCP
@@ -206,3 +208,6 @@ created (draft) -> sent -> delivered -> signed -> completed
| Send envelope | DOCUSIGN_SEND_ENVELOPE | envelopeId |
| Get envelope status | DOCUSIGN_GET_ENVELOPE | envelopeId |
| Add template to envelope | DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE | envelopeId, documentId, templateId |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/docx-official/SKILL.md b/web-app/public/skills/docx-official/SKILL.md
index 66466389..60d32c37 100644
--- a/web-app/public/skills/docx-official/SKILL.md
+++ b/web-app/public/skills/docx-official/SKILL.md
@@ -1,7 +1,9 @@
---
-name: docx
-description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+name: docx-official
+description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document..."
license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
---
# DOCX creation, editing, and analysis
@@ -194,4 +196,7 @@ Required dependencies (install if not available):
- **docx**: `npm install -g docx` (for creating new documents)
- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
\ No newline at end of file
+- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/domain-driven-design/SKILL.md b/web-app/public/skills/domain-driven-design/SKILL.md
new file mode 100644
index 00000000..5273cd07
--- /dev/null
+++ b/web-app/public/skills/domain-driven-design/SKILL.md
@@ -0,0 +1,73 @@
+---
+name: domain-driven-design
+description: "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns."
+risk: safe
+source: self
+tags: [ddd, domain, bounded-context, architecture]
+---
+
+# Domain-Driven Design
+
+## Use this skill when
+
+- You need to model a complex business domain with explicit boundaries.
+- You want to decide whether full DDD is worth the added complexity.
+- You need to connect strategic design decisions to implementation patterns.
+- You are planning CQRS, event sourcing, sagas, or projections from domain needs.
+
+## Do not use this skill when
+
+- The problem is simple CRUD with low business complexity.
+- You only need localized bug fixes.
+- There is no access to domain knowledge and no proxy product expert.
+
+## Instructions
+
+1. Run a viability check before committing to full DDD.
+2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary.
+3. Route to specialized skills based on current task.
+4. Define success criteria and evidence for each stage.
+
+### Viability check
+
+Use full DDD only when at least two of these are true:
+
+- Business rules are complex or fast-changing.
+- Multiple teams are causing model collisions.
+- Integration contracts are unstable.
+- Auditability and explicit invariants are critical.
+
+### Routing map
+
+- Strategic model and boundaries: `@ddd-strategic-design`
+- Cross-context integrations and translation: `@ddd-context-mapping`
+- Tactical code modeling: `@ddd-tactical-patterns`
+- Read/write separation: `@cqrs-implementation`
+- Event history as source of truth: `@event-sourcing-architect` and `@event-store-design`
+- Long-running workflows: `@saga-orchestration`
+- Read models: `@projection-patterns`
+- Decision log: `@architecture-decision-records`
+
+If templates are needed, open `references/ddd-deliverables.md`.
+
+## Output requirements
+
+Always return:
+
+- Scope and assumptions
+- Current stage (strategic, tactical, or evented)
+- Explicit artifacts produced
+- Open risks and next step recommendation
+
+## Examples
+
+```text
+Use @domain-driven-design to assess if this billing platform should adopt full DDD.
+Then route to the right next skill and list artifacts we must produce this week.
+```
+
+## Limitations
+
+- This skill does not replace direct workshops with domain experts.
+- It does not provide framework-specific code generation.
+- It should not be used as a justification to over-engineer simple systems.
diff --git a/web-app/public/skills/domain-driven-design/references/ddd-deliverables.md b/web-app/public/skills/domain-driven-design/references/ddd-deliverables.md
new file mode 100644
index 00000000..49eeeae1
--- /dev/null
+++ b/web-app/public/skills/domain-driven-design/references/ddd-deliverables.md
@@ -0,0 +1,24 @@
+# DDD Deliverables Checklist
+
+Use this checklist to keep DDD adoption practical and measurable.
+
+## Strategic deliverables
+
+- Subdomain map (core, supporting, generic)
+- Bounded context map and ownership
+- Ubiquitous language glossary
+- 1-2 ADRs documenting critical boundary decisions
+
+## Tactical deliverables
+
+- Aggregate list with invariants
+- Value object list
+- Domain events list
+- Repository contracts and transaction boundaries
+
+## Evented deliverables (only when required)
+
+- Command and query separation rationale
+- Event schema versioning policy
+- Saga compensation matrix
+- Projection rebuild strategy
diff --git a/web-app/public/skills/dotnet-architect/SKILL.md b/web-app/public/skills/dotnet-architect/SKILL.md
index 485d16b2..4c1b4a9d 100644
--- a/web-app/public/skills/dotnet-architect/SKILL.md
+++ b/web-app/public/skills/dotnet-architect/SKILL.md
@@ -1,12 +1,14 @@
---
name: dotnet-architect
-description: Expert .NET backend architect specializing in C#, ASP.NET Core,
+description: "Expert .NET backend architect specializing in C#, ASP.NET Core,"
Entity Framework, Dapper, and enterprise application patterns. Masters
async/await, dependency injection, caching strategies, and performance
optimization. Use PROACTIVELY for .NET API development, code review, or
architecture decisions.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/dotnet-backend-patterns/SKILL.md b/web-app/public/skills/dotnet-backend-patterns/SKILL.md
index 0f0b7328..f4041e9e 100644
--- a/web-app/public/skills/dotnet-backend-patterns/SKILL.md
+++ b/web-app/public/skills/dotnet-backend-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: dotnet-backend-patterns
-description: Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
+description: "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio..."
+risk: unknown
+source: community
---
# .NET Backend Development Patterns
diff --git a/web-app/public/skills/dotnet-backend/SKILL.md b/web-app/public/skills/dotnet-backend/SKILL.md
index 32549754..190b8702 100644
--- a/web-app/public/skills/dotnet-backend/SKILL.md
+++ b/web-app/public/skills/dotnet-backend/SKILL.md
@@ -1,6 +1,6 @@
---
name: dotnet-backend
-description: Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.
+description: "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns."
risk: safe
source: self
allowed-tools: Read, Write, Edit, Bash
diff --git a/web-app/public/skills/dropbox-automation/SKILL.md b/web-app/public/skills/dropbox-automation/SKILL.md
index 2763dfb4..0ea52f9c 100644
--- a/web-app/public/skills/dropbox-automation/SKILL.md
+++ b/web-app/public/skills/dropbox-automation/SKILL.md
@@ -3,6 +3,8 @@ name: dropbox-automation
description: "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Dropbox Automation via Rube MCP
@@ -228,3 +230,6 @@ Several Dropbox operations run asynchronously:
| Delete batch | `DROPBOX_DELETE_BATCH` | `entries` |
| Copy file/folder | `DROPBOX_COPY_FILE_OR_FOLDER` | `from_path`, `to_path` |
| Check batch status | `DROPBOX_CHECK_MOVE_BATCH` | `async_job_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/dx-optimizer/SKILL.md b/web-app/public/skills/dx-optimizer/SKILL.md
index 39ae6674..b42d5745 100644
--- a/web-app/public/skills/dx-optimizer/SKILL.md
+++ b/web-app/public/skills/dx-optimizer/SKILL.md
@@ -1,10 +1,12 @@
---
name: dx-optimizer
-description: Developer Experience specialist. Improves tooling, setup, and
+description: "Developer Experience specialist. Improves tooling, setup, and"
workflows. Use PROACTIVELY when setting up new projects, after team feedback,
or when development friction is noticed.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/e2e-testing-patterns/SKILL.md b/web-app/public/skills/e2e-testing-patterns/SKILL.md
index 1fee476a..a7c7e0f6 100644
--- a/web-app/public/skills/e2e-testing-patterns/SKILL.md
+++ b/web-app/public/skills/e2e-testing-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: e2e-testing-patterns
-description: Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
+description: "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky..."
+risk: unknown
+source: community
---
# E2E Testing Patterns
diff --git a/web-app/public/skills/e2e-testing/SKILL.md b/web-app/public/skills/e2e-testing/SKILL.md
new file mode 100644
index 00000000..78d7215c
--- /dev/null
+++ b/web-app/public/skills/e2e-testing/SKILL.md
@@ -0,0 +1,166 @@
+---
+name: e2e-testing
+description: "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration."
+source: personal
+risk: safe
+domain: testing-qa
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# E2E Testing Workflow
+
+## Overview
+
+Specialized workflow for end-to-end testing using Playwright including browser automation, visual regression testing, cross-browser testing, and CI/CD integration.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Setting up E2E testing
+- Automating browser tests
+- Implementing visual regression
+- Testing across browsers
+- Integrating tests with CI/CD
+
+## Workflow Phases
+
+### Phase 1: Test Setup
+
+#### Skills to Invoke
+- `playwright-skill` - Playwright setup
+- `e2e-testing-patterns` - E2E patterns
+
+#### Actions
+1. Install Playwright
+2. Configure test framework
+3. Set up test directory
+4. Configure browsers
+5. Create base test setup
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to set up Playwright testing
+```
+
+### Phase 2: Test Design
+
+#### Skills to Invoke
+- `e2e-testing-patterns` - Test patterns
+- `test-automator` - Test automation
+
+#### Actions
+1. Identify critical flows
+2. Design test scenarios
+3. Plan test data
+4. Create page objects
+5. Set up fixtures
+
+#### Copy-Paste Prompts
+```
+Use @e2e-testing-patterns to design E2E test strategy
+```
+
+### Phase 3: Test Implementation
+
+#### Skills to Invoke
+- `playwright-skill` - Playwright tests
+- `webapp-testing` - Web app testing
+
+#### Actions
+1. Write test scripts
+2. Add assertions
+3. Implement waits
+4. Handle dynamic content
+5. Add error handling
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to write E2E test scripts
+```
+
+### Phase 4: Browser Automation
+
+#### Skills to Invoke
+- `browser-automation` - Browser automation
+- `playwright-skill` - Playwright features
+
+#### Actions
+1. Configure headless mode
+2. Set up screenshots
+3. Implement video recording
+4. Add trace collection
+5. Configure mobile emulation
+
+#### Copy-Paste Prompts
+```
+Use @browser-automation to automate browser interactions
+```
+
+### Phase 5: Visual Regression
+
+#### Skills to Invoke
+- `playwright-skill` - Visual testing
+- `ui-visual-validator` - Visual validation
+
+#### Actions
+1. Set up visual testing
+2. Create baseline images
+3. Add visual assertions
+4. Configure thresholds
+5. Review differences
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to implement visual regression testing
+```
+
+### Phase 6: Cross-Browser Testing
+
+#### Skills to Invoke
+- `playwright-skill` - Multi-browser
+- `webapp-testing` - Browser testing
+
+#### Actions
+1. Configure Chromium
+2. Add Firefox tests
+3. Add WebKit tests
+4. Test mobile browsers
+5. Compare results
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to run cross-browser tests
+```
+
+### Phase 7: CI/CD Integration
+
+#### Skills to Invoke
+- `github-actions-templates` - GitHub Actions
+- `cicd-automation-workflow-automate` - CI/CD
+
+#### Actions
+1. Create CI workflow
+2. Configure parallel execution
+3. Set up artifacts
+4. Add reporting
+5. Configure notifications
+
+#### Copy-Paste Prompts
+```
+Use @github-actions-templates to integrate E2E tests with CI
+```
+
+## Quality Gates
+
+- [ ] Tests passing
+- [ ] Coverage adequate
+- [ ] Visual tests stable
+- [ ] Cross-browser verified
+- [ ] CI integration working
+
+## Related Workflow Bundles
+
+- `testing-qa` - Testing workflow
+- `development` - Development
+- `web-performance-optimization` - Performance
diff --git a/web-app/public/skills/elixir-pro/SKILL.md b/web-app/public/skills/elixir-pro/SKILL.md
index 91f99ce6..ab0d10ef 100644
--- a/web-app/public/skills/elixir-pro/SKILL.md
+++ b/web-app/public/skills/elixir-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: elixir-pro
-description: Write idiomatic Elixir code with OTP patterns, supervision trees,
+description: "Write idiomatic Elixir code with OTP patterns, supervision trees,"
and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed
systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM
optimizations.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/email-sequence/SKILL.md b/web-app/public/skills/email-sequence/SKILL.md
index f685d40d..4b34558e 100644
--- a/web-app/public/skills/email-sequence/SKILL.md
+++ b/web-app/public/skills/email-sequence/SKILL.md
@@ -1,6 +1,8 @@
---
name: email-sequence
-description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
+description: "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa..."
+risk: unknown
+source: community
---
# Email Sequence Design
@@ -923,3 +925,6 @@ If you need more context:
- **copywriting**: For landing pages emails link to
- **ab-test-setup**: For testing email elements
- **popup-cro**: For email capture popups
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/email-systems/SKILL.md b/web-app/public/skills/email-systems/SKILL.md
index 76b34463..c03e933e 100644
--- a/web-app/public/skills/email-systems/SKILL.md
+++ b/web-app/public/skills/email-systems/SKILL.md
@@ -1,7 +1,8 @@
---
name: email-systems
-description: "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns."
+description: "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Email Systems
@@ -52,3 +53,6 @@ Version email templates for rollback and A/B testing
| Sending high volume from new IP immediately | high | # IP warm-up schedule: |
| Emailing people who did not opt in | critical | # Permission requirements: |
| Emails that are mostly or entirely images | medium | # Balance images and text: |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/embedding-strategies/SKILL.md b/web-app/public/skills/embedding-strategies/SKILL.md
index 5c62713f..fbc99301 100644
--- a/web-app/public/skills/embedding-strategies/SKILL.md
+++ b/web-app/public/skills/embedding-strategies/SKILL.md
@@ -1,6 +1,8 @@
---
name: embedding-strategies
-description: Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.
+description: "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom..."
+risk: unknown
+source: community
---
# Embedding Strategies
diff --git a/web-app/public/skills/employment-contract-templates/SKILL.md b/web-app/public/skills/employment-contract-templates/SKILL.md
index c063c51e..289ef10a 100644
--- a/web-app/public/skills/employment-contract-templates/SKILL.md
+++ b/web-app/public/skills/employment-contract-templates/SKILL.md
@@ -1,6 +1,8 @@
---
name: employment-contract-templates
-description: Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.
+description: "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume..."
+risk: unknown
+source: community
---
# Employment Contract Templates
diff --git a/web-app/public/skills/environment-setup-guide/SKILL.md b/web-app/public/skills/environment-setup-guide/SKILL.md
index 5dbf083d..f82c24a2 100644
--- a/web-app/public/skills/environment-setup-guide/SKILL.md
+++ b/web-app/public/skills/environment-setup-guide/SKILL.md
@@ -1,6 +1,8 @@
---
name: environment-setup-guide
description: "Guide developers through setting up development environments with proper tools, dependencies, and configurations"
+risk: unknown
+source: community
---
# Environment Setup Guide
diff --git a/web-app/public/skills/error-debugging-error-analysis/SKILL.md b/web-app/public/skills/error-debugging-error-analysis/SKILL.md
index a140173e..0de638f8 100644
--- a/web-app/public/skills/error-debugging-error-analysis/SKILL.md
+++ b/web-app/public/skills/error-debugging-error-analysis/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-debugging-error-analysis
description: "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions."
+risk: unknown
+source: community
---
# Error Analysis and Resolution
diff --git a/web-app/public/skills/error-debugging-error-trace/SKILL.md b/web-app/public/skills/error-debugging-error-trace/SKILL.md
index a335745c..1705099a 100644
--- a/web-app/public/skills/error-debugging-error-trace/SKILL.md
+++ b/web-app/public/skills/error-debugging-error-trace/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-debugging-error-trace
-description: "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues."
+description: "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi..."
+risk: unknown
+source: community
---
# Error Tracking and Monitoring
diff --git a/web-app/public/skills/error-debugging-multi-agent-review/SKILL.md b/web-app/public/skills/error-debugging-multi-agent-review/SKILL.md
index 736dd4d1..a5e929c3 100644
--- a/web-app/public/skills/error-debugging-multi-agent-review/SKILL.md
+++ b/web-app/public/skills/error-debugging-multi-agent-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-debugging-multi-agent-review
description: "Use when working with error debugging multi agent review"
+risk: unknown
+source: community
---
# Multi-Agent Code Review Orchestration Tool
diff --git a/web-app/public/skills/error-detective/SKILL.md b/web-app/public/skills/error-detective/SKILL.md
index be4a9abc..8af4f438 100644
--- a/web-app/public/skills/error-detective/SKILL.md
+++ b/web-app/public/skills/error-detective/SKILL.md
@@ -1,11 +1,13 @@
---
name: error-detective
-description: Search logs and codebases for error patterns, stack traces, and
+description: "Search logs and codebases for error patterns, stack traces, and"
anomalies. Correlates errors across systems and identifies root causes. Use
PROACTIVELY when debugging issues, analyzing logs, or investigating production
errors.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/error-diagnostics-error-analysis/SKILL.md b/web-app/public/skills/error-diagnostics-error-analysis/SKILL.md
index 3be6b518..d0c11d42 100644
--- a/web-app/public/skills/error-diagnostics-error-analysis/SKILL.md
+++ b/web-app/public/skills/error-diagnostics-error-analysis/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-diagnostics-error-analysis
description: "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions."
+risk: unknown
+source: community
---
# Error Analysis and Resolution
diff --git a/web-app/public/skills/error-diagnostics-error-trace/SKILL.md b/web-app/public/skills/error-diagnostics-error-trace/SKILL.md
index d1c9f274..cea9061f 100644
--- a/web-app/public/skills/error-diagnostics-error-trace/SKILL.md
+++ b/web-app/public/skills/error-diagnostics-error-trace/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-diagnostics-error-trace
description: "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,"
+risk: unknown
+source: community
---
# Error Tracking and Monitoring
diff --git a/web-app/public/skills/error-diagnostics-smart-debug/SKILL.md b/web-app/public/skills/error-diagnostics-smart-debug/SKILL.md
index 845a1b45..755073c9 100644
--- a/web-app/public/skills/error-diagnostics-smart-debug/SKILL.md
+++ b/web-app/public/skills/error-diagnostics-smart-debug/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-diagnostics-smart-debug
description: "Use when working with error diagnostics smart debug"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/error-handling-patterns/SKILL.md b/web-app/public/skills/error-handling-patterns/SKILL.md
index 2e2a5736..20ade749 100644
--- a/web-app/public/skills/error-handling-patterns/SKILL.md
+++ b/web-app/public/skills/error-handling-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: error-handling-patterns
-description: Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
+description: "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling..."
+risk: unknown
+source: community
---
# Error Handling Patterns
diff --git a/web-app/public/skills/ethical-hacking-methodology/SKILL.md b/web-app/public/skills/ethical-hacking-methodology/SKILL.md
index 999334d7..589cdcf4 100644
--- a/web-app/public/skills/ethical-hacking-methodology/SKILL.md
+++ b/web-app/public/skills/ethical-hacking-methodology/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Ethical Hacking Methodology
-description: This skill should be used when the user asks to "learn ethical hacking", "understand penetration testing lifecycle", "perform reconnaissance", "conduct security scanning", "exploit vulnerabilities", or "write penetration test reports". It provides comprehensive ethical hacking methodology and techniques.
+name: ethical-hacking-methodology
+description: "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Ethical Hacking Methodology
@@ -464,3 +466,6 @@ umount /mnt/usb
2. Check payload compatibility
3. Adjust exploit parameters
4. Try alternative exploits
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/evaluation/SKILL.md b/web-app/public/skills/evaluation/SKILL.md
index 0a79bd1d..f1c16391 100644
--- a/web-app/public/skills/evaluation/SKILL.md
+++ b/web-app/public/skills/evaluation/SKILL.md
@@ -216,7 +216,7 @@ This skill connects to all other skills as a cross-cutting concern:
## References
Internal reference:
-- [Metrics Reference](./references/metrics.md) - Detailed evaluation metrics and implementation
+- Metrics Reference - Detailed evaluation metrics and implementation
## References
diff --git a/web-app/public/skills/event-sourcing-architect/SKILL.md b/web-app/public/skills/event-sourcing-architect/SKILL.md
index 707ae80c..c7bd217f 100644
--- a/web-app/public/skills/event-sourcing-architect/SKILL.md
+++ b/web-app/public/skills/event-sourcing-architect/SKILL.md
@@ -1,6 +1,8 @@
---
name: event-sourcing-architect
-description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries."
+description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e..."
+risk: unknown
+source: community
---
# Event Sourcing Architect
diff --git a/web-app/public/skills/event-store-design/SKILL.md b/web-app/public/skills/event-store-design/SKILL.md
index d7ef396b..0ebd1338 100644
--- a/web-app/public/skills/event-store-design/SKILL.md
+++ b/web-app/public/skills/event-store-design/SKILL.md
@@ -1,6 +1,8 @@
---
name: event-store-design
-description: Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
+description: "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns."
+risk: unknown
+source: community
---
# Event Store Design
diff --git a/web-app/public/skills/event-store-design/resources/implementation-playbook.md b/web-app/public/skills/event-store-design/resources/implementation-playbook.md
new file mode 100644
index 00000000..4d39074b
--- /dev/null
+++ b/web-app/public/skills/event-store-design/resources/implementation-playbook.md
@@ -0,0 +1,25 @@
+# Event Store Design Playbook
+
+## Schema and stream strategy
+
+- Use append-only writes with optimistic concurrency.
+- Keep per-stream ordering and global ordering indexes.
+- Include metadata fields for causation and correlation IDs.
+
+## Operational guardrails
+
+- Never mutate historical events in production.
+- Version event schema with explicit upcasters/downcasters policy.
+- Define retention and archival strategy by stream type.
+
+## Subscription and projection safety
+
+- Track per-subscriber checkpoint positions.
+- Make handlers idempotent and replay-safe.
+- Support projection rebuild from a clean checkpoint.
+
+## Performance checklist
+
+- Index stream id + version.
+- Index global position.
+- Add snapshot policy for long-lived aggregates.
diff --git a/web-app/public/skills/exa-search/SKILL.md b/web-app/public/skills/exa-search/SKILL.md
index 567f5b91..f8289cc2 100644
--- a/web-app/public/skills/exa-search/SKILL.md
+++ b/web-app/public/skills/exa-search/SKILL.md
@@ -1,6 +1,8 @@
---
name: exa-search
-description: Semantic search, similar content discovery, and structured research using Exa API
+description: "Semantic search, similar content discovery, and structured research using Exa API"
+risk: unknown
+source: community
---
# exa-search
diff --git a/web-app/public/skills/executing-plans/SKILL.md b/web-app/public/skills/executing-plans/SKILL.md
index ca77290c..b0aa4711 100644
--- a/web-app/public/skills/executing-plans/SKILL.md
+++ b/web-app/public/skills/executing-plans/SKILL.md
@@ -1,6 +1,8 @@
---
name: executing-plans
-description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
+description: "Use when you have a written implementation plan to execute in a separate session with review checkpoints"
+risk: unknown
+source: community
---
# Executing Plans
@@ -74,3 +76,6 @@ After all tasks complete and verified:
- Reference skills when plan says to
- Between batches: just report and wait
- Stop when blocked, don't guess
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/fastapi-pro/SKILL.md b/web-app/public/skills/fastapi-pro/SKILL.md
index 8e2c3672..f07b0e60 100644
--- a/web-app/public/skills/fastapi-pro/SKILL.md
+++ b/web-app/public/skills/fastapi-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: fastapi-pro
-description: Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and
+description: "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and"
Pydantic V2. Master microservices, WebSockets, and modern Python async
patterns. Use PROACTIVELY for FastAPI development, async optimization, or API
architecture.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/fastapi-router-py/SKILL.md b/web-app/public/skills/fastapi-router-py/SKILL.md
index ed3cf1cf..e453e790 100644
--- a/web-app/public/skills/fastapi-router-py/SKILL.md
+++ b/web-app/public/skills/fastapi-router-py/SKILL.md
@@ -1,6 +1,8 @@
---
name: fastapi-router-py
-description: Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
+description: "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add..."
+risk: unknown
+source: community
---
# FastAPI Router
@@ -9,7 +11,7 @@ Create FastAPI routers following established patterns with proper authentication
## Quick Start
-Copy the template from [assets/template.py](assets/template.py) and replace placeholders:
+Copy the template from assets/template.py and replace placeholders:
- `{{ResourceName}}` → PascalCase name (e.g., `Project`)
- `{{resource_name}}` → snake_case name (e.g., `project`)
- `{{resource_plural}}` → plural form (e.g., `projects`)
@@ -50,3 +52,6 @@ async def list_items() -> list[Item]:
3. Create corresponding Pydantic models
4. Create service layer if needed
5. Add frontend API functions
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/fastapi-templates/SKILL.md b/web-app/public/skills/fastapi-templates/SKILL.md
index 003f340e..4f4b61df 100644
--- a/web-app/public/skills/fastapi-templates/SKILL.md
+++ b/web-app/public/skills/fastapi-templates/SKILL.md
@@ -1,6 +1,8 @@
---
name: fastapi-templates
-description: Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
+description: "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects."
+risk: unknown
+source: community
---
# FastAPI Project Templates
diff --git a/web-app/public/skills/figma-automation/SKILL.md b/web-app/public/skills/figma-automation/SKILL.md
index b2f6bf33..eb9aced7 100644
--- a/web-app/public/skills/figma-automation/SKILL.md
+++ b/web-app/public/skills/figma-automation/SKILL.md
@@ -3,6 +3,8 @@ name: figma-automation
description: "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Figma Automation via Rube MCP
@@ -179,3 +181,6 @@ Extract IDs from Figma URLs:
| Team styles | FIGMA_GET_TEAM_STYLES | team_id |
| File styles | FIGMA_GET_FILE_STYLES | file_key |
| Image fills | FIGMA_GET_IMAGE_FILLS | file_key |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/file-organizer/SKILL.md b/web-app/public/skills/file-organizer/SKILL.md
index 0af136e9..3bf224ef 100644
--- a/web-app/public/skills/file-organizer/SKILL.md
+++ b/web-app/public/skills/file-organizer/SKILL.md
@@ -1,6 +1,8 @@
---
name: file-organizer
-description: Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.
+description: "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo..."
+risk: unknown
+source: community
---
# File Organizer
diff --git a/web-app/public/skills/file-path-traversal/SKILL.md b/web-app/public/skills/file-path-traversal/SKILL.md
index af4fa47b..9ea79eb6 100644
--- a/web-app/public/skills/file-path-traversal/SKILL.md
+++ b/web-app/public/skills/file-path-traversal/SKILL.md
@@ -1,9 +1,11 @@
---
-name: File Path Traversal Testing
-description: This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access files outside web root". It provides comprehensive file path traversal attack and testing methodologies.
+name: file-path-traversal
+description: "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# File Path Traversal Testing
@@ -484,3 +486,6 @@ def safe_file_access(base_dir, filename):
| No response difference | Try encoding, blind traversal, different files |
| Payload blocked | Use encoding variants, nested sequences, case variations |
| Cannot escalate to RCE | Check logs, PHP wrappers, file upload, session poisoning |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/file-uploads/SKILL.md b/web-app/public/skills/file-uploads/SKILL.md
index 2665e203..6447296a 100644
--- a/web-app/public/skills/file-uploads/SKILL.md
+++ b/web-app/public/skills/file-uploads/SKILL.md
@@ -1,7 +1,8 @@
---
name: file-uploads
-description: "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: file upload, S3, R2, presigned URL, multipart."
+description: "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# File Uploads & Storage
@@ -20,3 +21,6 @@ Prefers presigned URLs over server proxying.
| No upload size restrictions | high | # SET SIZE LIMITS |
| User-controlled filename allows path traversal | critical | # SANITIZE FILENAMES |
| Presigned URL shared or cached incorrectly | medium | # CONTROL PRESIGNED URL DISTRIBUTION |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/finishing-a-development-branch/SKILL.md b/web-app/public/skills/finishing-a-development-branch/SKILL.md
index c308b43b..3d7abd8a 100644
--- a/web-app/public/skills/finishing-a-development-branch/SKILL.md
+++ b/web-app/public/skills/finishing-a-development-branch/SKILL.md
@@ -1,6 +1,8 @@
---
name: finishing-a-development-branch
-description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
+description: "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup"
+risk: unknown
+source: community
---
# Finishing a Development Branch
@@ -198,3 +200,6 @@ git worktree remove
**Pairs with:**
- **using-git-worktrees** - Cleans up worktree created by that skill
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/firebase/SKILL.md b/web-app/public/skills/firebase/SKILL.md
index 4c18e980..122c5acf 100644
--- a/web-app/public/skills/firebase/SKILL.md
+++ b/web-app/public/skills/firebase/SKILL.md
@@ -1,7 +1,8 @@
---
name: firebase
-description: "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I"
+description: "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Firebase
@@ -54,3 +55,6 @@ Design Firestore data structure around query patterns
## Related Skills
Works well with: `nextjs-app-router`, `react-patterns`, `authentication-oauth`, `stripe`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/firecrawl-scraper/SKILL.md b/web-app/public/skills/firecrawl-scraper/SKILL.md
index 86c42650..5646238a 100644
--- a/web-app/public/skills/firecrawl-scraper/SKILL.md
+++ b/web-app/public/skills/firecrawl-scraper/SKILL.md
@@ -1,6 +1,8 @@
---
name: firecrawl-scraper
-description: Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API
+description: "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API"
+risk: unknown
+source: community
---
# firecrawl-scraper
diff --git a/web-app/public/skills/firmware-analyst/SKILL.md b/web-app/public/skills/firmware-analyst/SKILL.md
index 4d9eefb8..83f56424 100644
--- a/web-app/public/skills/firmware-analyst/SKILL.md
+++ b/web-app/public/skills/firmware-analyst/SKILL.md
@@ -1,12 +1,14 @@
---
name: firmware-analyst
-description: Expert firmware analyst specializing in embedded systems, IoT
+description: "Expert firmware analyst specializing in embedded systems, IoT"
security, and hardware reverse engineering. Masters firmware extraction,
analysis, and vulnerability research for routers, IoT devices, automotive
systems, and industrial controllers. Use PROACTIVELY for firmware security
audits, IoT penetration testing, or embedded systems research.
metadata:
model: opus
+risk: unknown
+source: community
---
# Download from vendor
diff --git a/web-app/public/skills/flutter-expert/SKILL.md b/web-app/public/skills/flutter-expert/SKILL.md
index 4692d360..7b8ee06a 100644
--- a/web-app/public/skills/flutter-expert/SKILL.md
+++ b/web-app/public/skills/flutter-expert/SKILL.md
@@ -1,12 +1,14 @@
---
name: flutter-expert
-description: Master Flutter development with Dart 3, advanced widgets, and
+description: "Master Flutter development with Dart 3, advanced widgets, and"
multi-platform deployment. Handles state management, animations, testing, and
performance optimization for mobile, web, desktop, and embedded platforms. Use
PROACTIVELY for Flutter architecture, UI implementation, or cross-platform
features.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/form-cro/SKILL.md b/web-app/public/skills/form-cro/SKILL.md
index 9f405867..d6ec718a 100644
--- a/web-app/public/skills/form-cro/SKILL.md
+++ b/web-app/public/skills/form-cro/SKILL.md
@@ -1,10 +1,12 @@
---
name: form-cro
-description: >
+description: ">"
Optimize any form that is NOT signup or account registration — including lead
capture, contact, demo request, application, survey, quote, and checkout forms.
Use when the goal is to increase form completion rate, reduce friction, or
improve lead quality without breaking compliance or downstream workflows.
+risk: unknown
+source: community
---
# Form Conversion Rate Optimization (Form CRO)
@@ -439,3 +441,6 @@ Do **not** test:
* **ab-test-setup** – Testing form changes
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/fp-ts-errors/SKILL.md b/web-app/public/skills/fp-ts-errors/SKILL.md
index b4d74470..88bfce78 100644
--- a/web-app/public/skills/fp-ts-errors/SKILL.md
+++ b/web-app/public/skills/fp-ts-errors/SKILL.md
@@ -1,6 +1,6 @@
---
name: fp-ts-errors
-description: Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.
+description: "Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts."
risk: safe
source: https://github.com/whatiskadudoing/fp-ts-skills
---
diff --git a/web-app/public/skills/fp-ts-pragmatic/SKILL.md b/web-app/public/skills/fp-ts-pragmatic/SKILL.md
index 3200fa29..6d476568 100644
--- a/web-app/public/skills/fp-ts-pragmatic/SKILL.md
+++ b/web-app/public/skills/fp-ts-pragmatic/SKILL.md
@@ -1,6 +1,6 @@
---
name: fp-ts-pragmatic
-description: A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.
+description: "A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library."
risk: safe
source: https://github.com/whatiskadudoing/fp-ts-skills
---
diff --git a/web-app/public/skills/fp-ts-react/SKILL.md b/web-app/public/skills/fp-ts-react/SKILL.md
index 0f47656a..0b04902d 100644
--- a/web-app/public/skills/fp-ts-react/SKILL.md
+++ b/web-app/public/skills/fp-ts-react/SKILL.md
@@ -1,6 +1,6 @@
---
name: fp-ts-react
-description: Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.
+description: "Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15."
risk: safe
source: https://github.com/whatiskadudoing/fp-ts-skills
---
diff --git a/web-app/public/skills/framework-migration-code-migrate/SKILL.md b/web-app/public/skills/framework-migration-code-migrate/SKILL.md
index be864e23..657e102e 100644
--- a/web-app/public/skills/framework-migration-code-migrate/SKILL.md
+++ b/web-app/public/skills/framework-migration-code-migrate/SKILL.md
@@ -1,6 +1,8 @@
---
name: framework-migration-code-migrate
description: "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and"
+risk: unknown
+source: community
---
# Code Migration Assistant
diff --git a/web-app/public/skills/framework-migration-deps-upgrade/SKILL.md b/web-app/public/skills/framework-migration-deps-upgrade/SKILL.md
index f9272c37..f15c0dd5 100644
--- a/web-app/public/skills/framework-migration-deps-upgrade/SKILL.md
+++ b/web-app/public/skills/framework-migration-deps-upgrade/SKILL.md
@@ -1,6 +1,8 @@
---
name: framework-migration-deps-upgrade
description: "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa"
+risk: unknown
+source: community
---
# Dependency Upgrade Strategy
diff --git a/web-app/public/skills/framework-migration-deps-upgrade/resources/implementation-playbook.md b/web-app/public/skills/framework-migration-deps-upgrade/resources/implementation-playbook.md
index 2eecb016..f8dd0fd2 100644
--- a/web-app/public/skills/framework-migration-deps-upgrade/resources/implementation-playbook.md
+++ b/web-app/public/skills/framework-migration-deps-upgrade/resources/implementation-playbook.md
@@ -292,9 +292,9 @@ git branch -D upgrade/{package_name}-{target_version}
## Resources
-- [Official Migration Guide]({get_official_guide_url(package_name, target_version)})
-- [Changelog]({get_changelog_url(package_name, target_version)})
-- [Community Discussions]({get_community_url(package_name)})
+- Official Migration Guide})
+- Changelog})
+- Community Discussions})
"""
return guide
diff --git a/web-app/public/skills/framework-migration-legacy-modernize/SKILL.md b/web-app/public/skills/framework-migration-legacy-modernize/SKILL.md
index 44b56e1f..0a618813 100644
--- a/web-app/public/skills/framework-migration-legacy-modernize/SKILL.md
+++ b/web-app/public/skills/framework-migration-legacy-modernize/SKILL.md
@@ -1,6 +1,8 @@
---
name: framework-migration-legacy-modernize
description: "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex"
+risk: unknown
+source: community
---
# Legacy Code Modernization Workflow
diff --git a/web-app/public/skills/free-tool-strategy/SKILL.md b/web-app/public/skills/free-tool-strategy/SKILL.md
index ecf0a1e5..3e4bb498 100644
--- a/web-app/public/skills/free-tool-strategy/SKILL.md
+++ b/web-app/public/skills/free-tool-strategy/SKILL.md
@@ -1,6 +1,8 @@
---
name: free-tool-strategy
-description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
+description: "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar..."
+risk: unknown
+source: community
---
# Free Tool Strategy (Engineering as Marketing)
@@ -574,3 +576,6 @@ If you need more context:
- **analytics-tracking**: For measuring tool usage
- **email-sequence**: For nurturing leads from the tool
- **programmatic-seo**: For building tool-based pages at scale
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/freshdesk-automation/SKILL.md b/web-app/public/skills/freshdesk-automation/SKILL.md
index 70453b44..c6d4dfb0 100644
--- a/web-app/public/skills/freshdesk-automation/SKILL.md
+++ b/web-app/public/skills/freshdesk-automation/SKILL.md
@@ -3,6 +3,8 @@ name: freshdesk-automation
description: "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Freshdesk Automation via Rube MCP
@@ -217,3 +219,6 @@ Freshdesk uses page-based pagination:
| List companies | `FRESHDESK_GET_COMPANIES` | `page` |
| List ticket fields | `FRESHDESK_LIST_TICKET_FIELDS` | (none) |
| List company fields | `FRESHDESK_LIST_COMPANY_FIELDS` | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/freshservice-automation/SKILL.md b/web-app/public/skills/freshservice-automation/SKILL.md
index 18aeb0dd..f8707b74 100644
--- a/web-app/public/skills/freshservice-automation/SKILL.md
+++ b/web-app/public/skills/freshservice-automation/SKILL.md
@@ -3,6 +3,8 @@ name: freshservice-automation
description: "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Freshservice Automation via Rube MCP
@@ -211,3 +213,6 @@ Automate Freshservice IT Service Management operations through Composio's Freshs
| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |
| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |
| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/frontend-design/SKILL.md b/web-app/public/skills/frontend-design/SKILL.md
index 4efede84..629b99f9 100644
--- a/web-app/public/skills/frontend-design/SKILL.md
+++ b/web-app/public/skills/frontend-design/SKILL.md
@@ -1,7 +1,9 @@
---
name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboards, or frontend applications.
+description: "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Frontend Design (Distinctive, Production-Grade)
@@ -270,3 +272,6 @@ Before finalizing output:
5. What should users *feel* in the first 3 seconds?
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/frontend-dev-guidelines/SKILL.md b/web-app/public/skills/frontend-dev-guidelines/SKILL.md
index fcd3ea5c..82008787 100644
--- a/web-app/public/skills/frontend-dev-guidelines/SKILL.md
+++ b/web-app/public/skills/frontend-dev-guidelines/SKILL.md
@@ -1,6 +1,8 @@
---
name: frontend-dev-guidelines
-description: Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router, performance optimization, and strict TypeScript practices.
+description: "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router..."
+risk: unknown
+source: community
---
@@ -357,3 +359,6 @@ Before finalizing code:
**Status:** Stable, opinionated, and enforceable
**Intended Use:** Production React codebases with long-term maintenance horizons
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/frontend-developer/SKILL.md b/web-app/public/skills/frontend-developer/SKILL.md
index 47edea06..9076ec20 100644
--- a/web-app/public/skills/frontend-developer/SKILL.md
+++ b/web-app/public/skills/frontend-developer/SKILL.md
@@ -1,11 +1,13 @@
---
name: frontend-developer
-description: Build React components, implement responsive layouts, and handle
+description: "Build React components, implement responsive layouts, and handle"
client-side state management. Masters React 19, Next.js 15, and modern
frontend architecture. Optimizes performance and ensures accessibility. Use
PROACTIVELY when creating UI components or fixing frontend issues.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.
diff --git a/web-app/public/skills/frontend-mobile-development-component-scaffold/SKILL.md b/web-app/public/skills/frontend-mobile-development-component-scaffold/SKILL.md
index 2bd383c7..b1632cb4 100644
--- a/web-app/public/skills/frontend-mobile-development-component-scaffold/SKILL.md
+++ b/web-app/public/skills/frontend-mobile-development-component-scaffold/SKILL.md
@@ -1,6 +1,8 @@
---
name: frontend-mobile-development-component-scaffold
description: "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s"
+risk: unknown
+source: community
---
# React/React Native Component Scaffolding
diff --git a/web-app/public/skills/frontend-mobile-security-xss-scan/SKILL.md b/web-app/public/skills/frontend-mobile-security-xss-scan/SKILL.md
index 6e236e6e..b53efe02 100644
--- a/web-app/public/skills/frontend-mobile-security-xss-scan/SKILL.md
+++ b/web-app/public/skills/frontend-mobile-security-xss-scan/SKILL.md
@@ -1,6 +1,8 @@
---
name: frontend-mobile-security-xss-scan
description: "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi"
+risk: unknown
+source: community
---
# XSS Vulnerability Scanner for Frontend Code
diff --git a/web-app/public/skills/frontend-security-coder/SKILL.md b/web-app/public/skills/frontend-security-coder/SKILL.md
index fefe59fd..fd8d22dc 100644
--- a/web-app/public/skills/frontend-security-coder/SKILL.md
+++ b/web-app/public/skills/frontend-security-coder/SKILL.md
@@ -1,11 +1,13 @@
---
name: frontend-security-coder
-description: Expert in secure frontend coding practices specializing in XSS
+description: "Expert in secure frontend coding practices specializing in XSS"
prevention, output sanitization, and client-side security patterns. Use
PROACTIVELY for frontend security implementations or client-side security code
reviews.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/frontend-slides/SKILL.md b/web-app/public/skills/frontend-slides/SKILL.md
index 9c2e7ede..a2fedfdc 100644
--- a/web-app/public/skills/frontend-slides/SKILL.md
+++ b/web-app/public/skills/frontend-slides/SKILL.md
@@ -1,6 +1,6 @@
---
name: frontend-slides
-description: Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
+description: "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a..."
source: https://github.com/zarazhangrui/frontend-slides
risk: safe
---
@@ -768,3 +768,6 @@ class TiltEffect {
6. User picks a style
7. Skill generates HTML presentation with preserved assets
8. Final presentation delivered
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/frontend-ui-dark-ts/SKILL.md b/web-app/public/skills/frontend-ui-dark-ts/SKILL.md
index 7b220f10..b0d65a85 100644
--- a/web-app/public/skills/frontend-ui-dark-ts/SKILL.md
+++ b/web-app/public/skills/frontend-ui-dark-ts/SKILL.md
@@ -1,6 +1,8 @@
---
name: frontend-ui-dark-ts
-description: Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
+description: "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces..."
+risk: unknown
+source: community
---
# Frontend UI Dark Theme (TypeScript)
@@ -583,6 +585,9 @@ export function PageTransition({ children }: PageTransitionProps) {
## Related Files
-- [Design Tokens](./references/design-tokens.md) — Complete color system, spacing, typography scales
-- [Components](./references/components.md) — Button, Card, Input, Dialog, Tabs, and more
-- [Patterns](./references/patterns.md) — Page layouts, navigation, lists, forms
+- Design Tokens — Complete color system, spacing, typography scales
+- Components — Button, Card, Input, Dialog, Tabs, and more
+- Patterns — Page layouts, navigation, lists, forms
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/full-stack-orchestration-full-stack-feature/SKILL.md b/web-app/public/skills/full-stack-orchestration-full-stack-feature/SKILL.md
index 06497bda..825274df 100644
--- a/web-app/public/skills/full-stack-orchestration-full-stack-feature/SKILL.md
+++ b/web-app/public/skills/full-stack-orchestration-full-stack-feature/SKILL.md
@@ -1,6 +1,8 @@
---
name: full-stack-orchestration-full-stack-feature
description: "Use when working with full stack orchestration full stack feature"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/game-development/2d-games/SKILL.md b/web-app/public/skills/game-development/2d-games/SKILL.md
index a3f8d24b..9bafd2a1 100644
--- a/web-app/public/skills/game-development/2d-games/SKILL.md
+++ b/web-app/public/skills/game-development/2d-games/SKILL.md
@@ -1,7 +1,9 @@
---
name: 2d-games
-description: 2D game development principles. Sprites, tilemaps, physics, camera.
+description: "2D game development principles. Sprites, tilemaps, physics, camera."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# 2D Game Development
@@ -117,3 +119,6 @@ allowed-tools: Read, Write, Edit, Glob, Grep
---
> **Remember:** 2D is about clarity. Every pixel should communicate.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/3d-games/SKILL.md b/web-app/public/skills/game-development/3d-games/SKILL.md
index 6f489304..0f189699 100644
--- a/web-app/public/skills/game-development/3d-games/SKILL.md
+++ b/web-app/public/skills/game-development/3d-games/SKILL.md
@@ -1,7 +1,9 @@
---
name: 3d-games
-description: 3D game development principles. Rendering, shaders, physics, cameras.
+description: "3D game development principles. Rendering, shaders, physics, cameras."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# 3D Game Development
@@ -133,3 +135,6 @@ allowed-tools: Read, Write, Edit, Glob, Grep
---
> **Remember:** 3D is about illusion. Create the impression of detail, not the detail itself.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/SKILL.md b/web-app/public/skills/game-development/SKILL.md
index 20886339..68fbcda0 100644
--- a/web-app/public/skills/game-development/SKILL.md
+++ b/web-app/public/skills/game-development/SKILL.md
@@ -1,7 +1,9 @@
---
name: game-development
-description: Game development orchestrator. Routes to platform-specific skills based on project needs.
+description: "Game development orchestrator. Routes to platform-specific skills based on project needs."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Game Development
diff --git a/web-app/public/skills/game-development/game-art/SKILL.md b/web-app/public/skills/game-development/game-art/SKILL.md
index 87a6ab3c..a6d40e5a 100644
--- a/web-app/public/skills/game-development/game-art/SKILL.md
+++ b/web-app/public/skills/game-development/game-art/SKILL.md
@@ -1,7 +1,9 @@
---
name: game-art
-description: Game art principles. Visual style selection, asset pipeline, animation workflow.
+description: "Game art principles. Visual style selection, asset pipeline, animation workflow."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Game Art Principles
@@ -183,3 +185,6 @@ assets/
---
> **Remember:** Art serves gameplay. If it doesn't help the player, it's decoration.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/game-audio/SKILL.md b/web-app/public/skills/game-development/game-audio/SKILL.md
index 77ad3c25..dd7e758e 100644
--- a/web-app/public/skills/game-development/game-audio/SKILL.md
+++ b/web-app/public/skills/game-development/game-audio/SKILL.md
@@ -1,7 +1,9 @@
---
name: game-audio
-description: Game audio principles. Sound design, music integration, adaptive audio systems.
+description: "Game audio principles. Sound design, music integration, adaptive audio systems."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Game Audio Principles
@@ -188,3 +190,6 @@ Game State → Music Response
---
> **Remember:** 50% of the game experience is audio. A muted game loses half its soul.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/game-design/SKILL.md b/web-app/public/skills/game-development/game-design/SKILL.md
index 4dea97a8..3dd147f8 100644
--- a/web-app/public/skills/game-development/game-design/SKILL.md
+++ b/web-app/public/skills/game-development/game-design/SKILL.md
@@ -1,7 +1,9 @@
---
name: game-design
-description: Game design principles. GDD structure, balancing, player psychology, progression.
+description: "Game design principles. GDD structure, balancing, player psychology, progression."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Game Design Principles
@@ -127,3 +129,6 @@ Just Right → Flow → Engagement
---
> **Remember:** Fun is discovered through iteration, not designed on paper.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/mobile-games/SKILL.md b/web-app/public/skills/game-development/mobile-games/SKILL.md
index f91d0065..d4453cb8 100644
--- a/web-app/public/skills/game-development/mobile-games/SKILL.md
+++ b/web-app/public/skills/game-development/mobile-games/SKILL.md
@@ -1,7 +1,9 @@
---
name: mobile-games
-description: Mobile game development principles. Touch input, battery, performance, app stores.
+description: "Mobile game development principles. Touch input, battery, performance, app stores."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Mobile Game Development
@@ -106,3 +108,6 @@ allowed-tools: Read, Write, Edit, Glob, Grep
---
> **Remember:** Mobile is the most constrained platform. Respect battery and attention.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/multiplayer/SKILL.md b/web-app/public/skills/game-development/multiplayer/SKILL.md
index 8fd8cf18..015f8d30 100644
--- a/web-app/public/skills/game-development/multiplayer/SKILL.md
+++ b/web-app/public/skills/game-development/multiplayer/SKILL.md
@@ -1,7 +1,9 @@
---
name: multiplayer
-description: Multiplayer game development principles. Architecture, networking, synchronization.
+description: "Multiplayer game development principles. Architecture, networking, synchronization."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Multiplayer Game Development
@@ -130,3 +132,6 @@ Server: Validate → did projectile actually hit?
---
> **Remember:** Never trust the client. The server is the source of truth.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/pc-games/SKILL.md b/web-app/public/skills/game-development/pc-games/SKILL.md
index 6be120e7..283f6cdd 100644
--- a/web-app/public/skills/game-development/pc-games/SKILL.md
+++ b/web-app/public/skills/game-development/pc-games/SKILL.md
@@ -1,7 +1,9 @@
---
name: pc-games
-description: PC and console game development principles. Engine selection, platform features, optimization strategies.
+description: "PC and console game development principles. Engine selection, platform features, optimization strategies."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# PC/Console Game Development
@@ -142,3 +144,6 @@ Map ACTIONS, not buttons:
---
> **Remember:** Engine is a tool. Master the principles, then adapt to any engine.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/vr-ar/SKILL.md b/web-app/public/skills/game-development/vr-ar/SKILL.md
index bd42475e..2adb9a83 100644
--- a/web-app/public/skills/game-development/vr-ar/SKILL.md
+++ b/web-app/public/skills/game-development/vr-ar/SKILL.md
@@ -1,7 +1,9 @@
---
name: vr-ar
-description: VR/AR development principles. Comfort, interaction, performance requirements.
+description: "VR/AR development principles. Comfort, interaction, performance requirements."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# VR/AR Development
@@ -121,3 +123,6 @@ allowed-tools: Read, Write, Edit, Glob, Grep
---
> **Remember:** Comfort is not optional. Sick players don't play.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/game-development/web-games/SKILL.md b/web-app/public/skills/game-development/web-games/SKILL.md
index 13d25c1f..cbe3c822 100644
--- a/web-app/public/skills/game-development/web-games/SKILL.md
+++ b/web-app/public/skills/game-development/web-games/SKILL.md
@@ -1,7 +1,9 @@
---
name: web-games
-description: Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
+description: "Web browser game development principles. Framework selection, WebGPU, optimization, PWA."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Web Browser Game Development
@@ -148,3 +150,6 @@ What type of game?
---
> **Remember:** Browser is the most accessible platform. Respect its constraints.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/gcp-cloud-run/SKILL.md b/web-app/public/skills/gcp-cloud-run/SKILL.md
index 9c2f491f..bd344b3c 100644
--- a/web-app/public/skills/gcp-cloud-run/SKILL.md
+++ b/web-app/public/skills/gcp-cloud-run/SKILL.md
@@ -1,7 +1,8 @@
---
name: gcp-cloud-run
-description: "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub."
+description: "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# GCP Cloud Run
@@ -286,3 +287,6 @@ requests. Background tasks will be extremely slow or stall.
| Issue | high | ## Enable startup CPU boost |
| Issue | medium | ## Explicitly set execution environment |
| Issue | medium | ## Set consistent timeouts |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/gdpr-data-handling/SKILL.md b/web-app/public/skills/gdpr-data-handling/SKILL.md
index d7eaf83d..c8a3cd8c 100644
--- a/web-app/public/skills/gdpr-data-handling/SKILL.md
+++ b/web-app/public/skills/gdpr-data-handling/SKILL.md
@@ -1,6 +1,8 @@
---
name: gdpr-data-handling
-description: Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.
+description: "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o..."
+risk: unknown
+source: community
---
# GDPR Data Handling
diff --git a/web-app/public/skills/gemini-api-dev/SKILL.md b/web-app/public/skills/gemini-api-dev/SKILL.md
index f5deb715..7855ab48 100644
--- a/web-app/public/skills/gemini-api-dev/SKILL.md
+++ b/web-app/public/skills/gemini-api-dev/SKILL.md
@@ -1,6 +1,8 @@
---
name: gemini-api-dev
-description: Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript), model selection, and API capabilities.
+description: "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n..."
+risk: unknown
+source: community
---
# Gemini API Development Skill
@@ -125,3 +127,6 @@ This index contains links to all documentation pages in `.md.txt` format. Use we
- [Embeddings](https://ai.google.dev/gemini-api/docs/embeddings.md.txt)
- [Interactions API](https://ai.google.dev/gemini-api/docs/interactions.md.txt)
- [SDK migration guide](https://ai.google.dev/gemini-api/docs/migrate.md.txt)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/geo-fundamentals/SKILL.md b/web-app/public/skills/geo-fundamentals/SKILL.md
index d69bdc08..e9022151 100644
--- a/web-app/public/skills/geo-fundamentals/SKILL.md
+++ b/web-app/public/skills/geo-fundamentals/SKILL.md
@@ -1,7 +1,9 @@
---
name: geo-fundamentals
-description: Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
+description: "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity)."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# GEO Fundamentals
@@ -154,3 +156,6 @@ How AI engines select content to cite:
|--------|---------|---------|
| `scripts/geo_checker.py` | GEO audit (AI citation readiness) | `python scripts/geo_checker.py ` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/git-advanced-workflows/SKILL.md b/web-app/public/skills/git-advanced-workflows/SKILL.md
index 940edc78..2b5eb3bb 100644
--- a/web-app/public/skills/git-advanced-workflows/SKILL.md
+++ b/web-app/public/skills/git-advanced-workflows/SKILL.md
@@ -1,6 +1,8 @@
---
name: git-advanced-workflows
-description: Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
+description: "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co..."
+risk: unknown
+source: community
---
# Git Advanced Workflows
diff --git a/web-app/public/skills/git-pr-workflows-git-workflow/SKILL.md b/web-app/public/skills/git-pr-workflows-git-workflow/SKILL.md
index 984fba94..f459e424 100644
--- a/web-app/public/skills/git-pr-workflows-git-workflow/SKILL.md
+++ b/web-app/public/skills/git-pr-workflows-git-workflow/SKILL.md
@@ -1,6 +1,8 @@
---
name: git-pr-workflows-git-workflow
description: "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g"
+risk: unknown
+source: community
---
# Complete Git Workflow with Multi-Agent Orchestration
diff --git a/web-app/public/skills/git-pr-workflows-onboard/SKILL.md b/web-app/public/skills/git-pr-workflows-onboard/SKILL.md
index 6da52e8a..619fb081 100644
--- a/web-app/public/skills/git-pr-workflows-onboard/SKILL.md
+++ b/web-app/public/skills/git-pr-workflows-onboard/SKILL.md
@@ -1,6 +1,8 @@
---
name: git-pr-workflows-onboard
description: "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You"
+risk: unknown
+source: community
---
# Onboard
diff --git a/web-app/public/skills/git-pr-workflows-pr-enhance/SKILL.md b/web-app/public/skills/git-pr-workflows-pr-enhance/SKILL.md
index 9e982373..e26b0f91 100644
--- a/web-app/public/skills/git-pr-workflows-pr-enhance/SKILL.md
+++ b/web-app/public/skills/git-pr-workflows-pr-enhance/SKILL.md
@@ -1,6 +1,8 @@
---
name: git-pr-workflows-pr-enhance
description: "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu"
+risk: unknown
+source: community
---
# Pull Request Enhancement
diff --git a/web-app/public/skills/git-pushing/SKILL.md b/web-app/public/skills/git-pushing/SKILL.md
index 218f88e4..448ea0a7 100644
--- a/web-app/public/skills/git-pushing/SKILL.md
+++ b/web-app/public/skills/git-pushing/SKILL.md
@@ -1,6 +1,8 @@
---
name: git-pushing
-description: Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
+description: "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate..."
+risk: unknown
+source: community
---
# Git Push Workflow
diff --git a/web-app/public/skills/github-actions-templates/SKILL.md b/web-app/public/skills/github-actions-templates/SKILL.md
index 2409087a..1005c9b6 100644
--- a/web-app/public/skills/github-actions-templates/SKILL.md
+++ b/web-app/public/skills/github-actions-templates/SKILL.md
@@ -1,6 +1,8 @@
---
name: github-actions-templates
-description: Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
+description: "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre..."
+risk: unknown
+source: community
---
# GitHub Actions Templates
diff --git a/web-app/public/skills/github-automation/SKILL.md b/web-app/public/skills/github-automation/SKILL.md
index 7a73015d..30aa4d67 100644
--- a/web-app/public/skills/github-automation/SKILL.md
+++ b/web-app/public/skills/github-automation/SKILL.md
@@ -3,6 +3,8 @@ name: github-automation
description: "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# GitHub Automation via Rube MCP
@@ -225,3 +227,6 @@ All list endpoints use page-based pagination:
| Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref |
| List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` |
| Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/github-issue-creator/SKILL.md b/web-app/public/skills/github-issue-creator/SKILL.md
index 4351dcd3..c9a699d3 100644
--- a/web-app/public/skills/github-issue-creator/SKILL.md
+++ b/web-app/public/skills/github-issue-creator/SKILL.md
@@ -1,6 +1,8 @@
---
name: github-issue-creator
-description: Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
+description: "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan..."
+risk: unknown
+source: community
---
# GitHub Issue Creator
@@ -64,7 +66,7 @@ Transform messy input (error logs, voice notes, screenshots) into clean, actiona
- Medium: Feature impaired, workaround exists
- Low: Minor inconvenience, cosmetic
-**Image/GIF handling**: Reference attachments inline. Format: ``
+**Image/GIF handling**: Reference attachments inline. Format: `!Description`
## Examples
@@ -134,4 +136,7 @@ Code: 403
## Additional Context
Was working yesterday - possible permission/config change or service regression
-```
\ No newline at end of file
+```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/github-workflow-automation/SKILL.md b/web-app/public/skills/github-workflow-automation/SKILL.md
index 975dfa7b..ac5f3ed7 100644
--- a/web-app/public/skills/github-workflow-automation/SKILL.md
+++ b/web-app/public/skills/github-workflow-automation/SKILL.md
@@ -1,6 +1,8 @@
---
name: github-workflow-automation
-description: "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creating GitHub Actions, or triaging issues."
+description: "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati..."
+risk: unknown
+source: community
---
# 🔧 GitHub Workflow Automation
diff --git a/web-app/public/skills/gitlab-automation/SKILL.md b/web-app/public/skills/gitlab-automation/SKILL.md
index a14f31b7..a3f5e709 100644
--- a/web-app/public/skills/gitlab-automation/SKILL.md
+++ b/web-app/public/skills/gitlab-automation/SKILL.md
@@ -3,6 +3,8 @@ name: gitlab-automation
description: "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# GitLab Automation via Rube MCP
@@ -252,3 +254,6 @@ When using project paths as identifiers:
| User status | `GITLAB_GET_USERS_ID_STATUS` | user ID |
| List project members | `GITLAB_LIST_ALL_PROJECT_MEMBERS` | `id`, `query`, `state` |
| List project users | `GITLAB_LIST_PROJECT_USERS` | `id`, `search` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/gitlab-ci-patterns/SKILL.md b/web-app/public/skills/gitlab-ci-patterns/SKILL.md
index 9e6609fb..3a696d86 100644
--- a/web-app/public/skills/gitlab-ci-patterns/SKILL.md
+++ b/web-app/public/skills/gitlab-ci-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: gitlab-ci-patterns
-description: Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
+description: "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up..."
+risk: unknown
+source: community
---
# GitLab CI Patterns
diff --git a/web-app/public/skills/gitops-workflow/SKILL.md b/web-app/public/skills/gitops-workflow/SKILL.md
index d39e6d1f..ab77584d 100644
--- a/web-app/public/skills/gitops-workflow/SKILL.md
+++ b/web-app/public/skills/gitops-workflow/SKILL.md
@@ -1,6 +1,8 @@
---
name: gitops-workflow
-description: Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
+description: "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo..."
+risk: unknown
+source: community
---
# GitOps Workflow
diff --git a/web-app/public/skills/gmail-automation/SKILL.md b/web-app/public/skills/gmail-automation/SKILL.md
index 3708bc47..251c5019 100644
--- a/web-app/public/skills/gmail-automation/SKILL.md
+++ b/web-app/public/skills/gmail-automation/SKILL.md
@@ -3,6 +3,8 @@ name: gmail-automation
description: "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Gmail Automation via Rube MCP
@@ -267,4 +269,7 @@ Automate Gmail operations through Composio's Gmail toolkit via Rube MCP.
| Send draft | GMAIL_SEND_DRAFT | draft_id |
| Get attachment | GMAIL_GET_ATTACHMENT | message_id, attachment_id |
| Search contacts | GMAIL_SEARCH_PEOPLE | query |
-| Get profile | GMAIL_GET_PROFILE | (none) |
\ No newline at end of file
+| Get profile | GMAIL_GET_PROFILE | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/go-concurrency-patterns/SKILL.md b/web-app/public/skills/go-concurrency-patterns/SKILL.md
index dc829c3f..451d10b9 100644
--- a/web-app/public/skills/go-concurrency-patterns/SKILL.md
+++ b/web-app/public/skills/go-concurrency-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: go-concurrency-patterns
-description: Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.
+description: "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions."
+risk: unknown
+source: community
---
# Go Concurrency Patterns
diff --git a/web-app/public/skills/go-playwright/SKILL.md b/web-app/public/skills/go-playwright/SKILL.md
index a1e2e678..cfca3069 100644
--- a/web-app/public/skills/go-playwright/SKILL.md
+++ b/web-app/public/skills/go-playwright/SKILL.md
@@ -1,6 +1,6 @@
---
name: go-playwright
-description: Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.
+description: "Expert capability for robust, stealthy, and efficient browser automation using Playwright Go."
risk: safe
source: https://github.com/playwright-community/playwright-go
---
diff --git a/web-app/public/skills/godot-4-migration/SKILL.md b/web-app/public/skills/godot-4-migration/SKILL.md
new file mode 100644
index 00000000..5296f63b
--- /dev/null
+++ b/web-app/public/skills/godot-4-migration/SKILL.md
@@ -0,0 +1,126 @@
+---
+name: godot-4-migration
+description: Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.
+risk: safe
+source: community
+---
+
+# Godot 4 Migration Guide
+
+## Overview
+
+A critical guide for developers transitioning from Godot 3.x to Godot 4. This skill focuses on the major syntax changes in GDScript 2.0, the new `Tween` system, and `export` annotation updates.
+
+## When to Use This Skill
+
+- Use when porting a Godot 3 project to Godot 4.
+- Use when encountering syntax errors after upgrading.
+- Use when replacing deprecated nodes (like `Tween` node vs `create_tween`).
+- Use when updating `export` variables to `@export` annotations.
+
+## Key Changes
+
+### 1. Annotations (`@`)
+
+Godot 4 uses `@` for keywords that modify behavior.
+- `export var x` -> `@export var x`
+- `onready var y` -> `@onready var y`
+- `tool` -> `@tool` (at top of file)
+
+### 2. Setters and Getters
+
+Properties now define setters/getters inline.
+
+**Godot 3:**
+```gdscript
+var health setget set_health, get_health
+
+func set_health(value):
+ health = value
+```
+
+**Godot 4:**
+```gdscript
+var health: int:
+ set(value):
+ health = value
+ emit_signal("health_changed", health)
+ get:
+ return health
+```
+
+### 3. Tween System
+
+The `Tween` node is deprecated. Use `create_tween()` in code.
+
+**Godot 3:**
+```gdscript
+$Tween.interpolate_property(...)
+$Tween.start()
+```
+
+**Godot 4:**
+```gdscript
+var tween = create_tween()
+tween.tween_property($Sprite, "position", Vector2(100, 100), 1.0)
+tween.parallel().tween_property($Sprite, "modulate:a", 0.0, 1.0)
+```
+
+### 4. Signal Connections
+
+String-based connections are discouraged. Use callables.
+
+**Godot 3:**
+```gdscript
+connect("pressed", self, "_on_pressed")
+```
+
+**Godot 4:**
+```gdscript
+pressed.connect(_on_pressed)
+```
+
+## Examples
+
+### Example 1: Typed Arrays
+
+GDScript 2.0 supports typed arrays for better performance and type safety.
+
+```gdscript
+# Godot 3
+var enemies = []
+
+# Godot 4
+var enemies: Array[Node] = []
+
+func _ready():
+ for child in get_children():
+ if child is Enemy:
+ enemies.append(child)
+```
+
+### Example 2: Awaiting Signals (Coroutines)
+
+`yield` is replaced by `await`.
+
+**Godot 3:**
+```gdscript
+yield(get_tree().create_timer(1.0), "timeout")
+```
+
+**Godot 4:**
+```gdscript
+await get_tree().create_timer(1.0).timeout
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `@export_range`, `@export_file`, etc., for better inspector UI.
+- ✅ **Do:** Type all variables (`var x: int`) for performance gains in GDScript 2.0.
+- ✅ **Do:** Use `super()` to call parent methods instead of `.function_name()`.
+- ❌ **Don't:** Use string names for signals (`emit_signal("name")`) if you can use the signal object (`name.emit()`).
+
+## Troubleshooting
+
+**Problem:** "Identifier 'Tween' is not a valid type."
+**Solution:** `Tween` is now `SceneTreeTween` or just an object returned by `create_tween()`. You rarely type it explicitly, just use `var tween = create_tween()`.
diff --git a/web-app/public/skills/godot-gdscript-patterns/SKILL.md b/web-app/public/skills/godot-gdscript-patterns/SKILL.md
index ec1bcbf7..2bd3c637 100644
--- a/web-app/public/skills/godot-gdscript-patterns/SKILL.md
+++ b/web-app/public/skills/godot-gdscript-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: godot-gdscript-patterns
-description: Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.
+description: "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices."
+risk: unknown
+source: community
---
# Godot GDScript Patterns
diff --git a/web-app/public/skills/golang-pro/SKILL.md b/web-app/public/skills/golang-pro/SKILL.md
index 4a7214a0..807a3552 100644
--- a/web-app/public/skills/golang-pro/SKILL.md
+++ b/web-app/public/skills/golang-pro/SKILL.md
@@ -1,12 +1,14 @@
---
name: golang-pro
-description: Master Go 1.21+ with modern patterns, advanced concurrency,
+description: "Master Go 1.21+ with modern patterns, advanced concurrency,"
performance optimization, and production-ready microservices. Expert in the
latest Go ecosystem including generics, workspaces, and cutting-edge
frameworks. Use PROACTIVELY for Go development, architecture design, or
performance optimization.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.
diff --git a/web-app/public/skills/google-analytics-automation/SKILL.md b/web-app/public/skills/google-analytics-automation/SKILL.md
index 68aa6c11..92c6646f 100644
--- a/web-app/public/skills/google-analytics-automation/SKILL.md
+++ b/web-app/public/skills/google-analytics-automation/SKILL.md
@@ -3,6 +3,8 @@ name: google-analytics-automation
description: "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Google Analytics Automation via Rube MCP
@@ -225,3 +227,6 @@ Automate Google Analytics 4 (GA4) reporting and property management through Comp
| Pivot report | GOOGLE_ANALYTICS_RUN_PIVOT_REPORT | property, dateRanges, pivots |
| Funnel report | GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT | property, dateRanges, funnel |
| List key events | GOOGLE_ANALYTICS_LIST_KEY_EVENTS | parent, pageSize |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/google-calendar-automation/SKILL.md b/web-app/public/skills/google-calendar-automation/SKILL.md
index c69d675f..d18a0f9c 100644
--- a/web-app/public/skills/google-calendar-automation/SKILL.md
+++ b/web-app/public/skills/google-calendar-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: google-calendar-automation
-description: "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatically."
+description: "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Google Calendar Automation via Rube MCP
@@ -174,3 +176,6 @@ Automate Google Calendar workflows including event creation, scheduling, availab
| Remove attendee | `GOOGLECALENDAR_REMOVE_ATTENDEE` | `event_id`, `attendee_email` |
| Get current time | `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` | `timezone` |
| Get calendar | `GOOGLECALENDAR_GET_CALENDAR` | `calendar_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/google-drive-automation/SKILL.md b/web-app/public/skills/google-drive-automation/SKILL.md
index 34b8713c..89fe3d59 100644
--- a/web-app/public/skills/google-drive-automation/SKILL.md
+++ b/web-app/public/skills/google-drive-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: google-drive-automation
-description: "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives programmatically."
+description: "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Google Drive Automation via Rube MCP
@@ -191,3 +193,6 @@ For Google Workspace files, set `mime_type` to export:
| List shared drives | `GOOGLEDRIVE_LIST_SHARED_DRIVES` | `pageSize` |
| Drive info | `GOOGLEDRIVE_GET_ABOUT` | (none) |
| Create shortcut | `GOOGLEDRIVE_CREATE_SHORTCUT_TO_FILE` | target file_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/googlesheets-automation/SKILL.md b/web-app/public/skills/googlesheets-automation/SKILL.md
index d0c49590..ac7ac6ed 100644
--- a/web-app/public/skills/googlesheets-automation/SKILL.md
+++ b/web-app/public/skills/googlesheets-automation/SKILL.md
@@ -3,6 +3,8 @@ name: googlesheets-automation
description: "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Google Sheets Automation via Rube MCP
@@ -195,3 +197,6 @@ Google Sheets enforces strict rate limits:
| Delete rows/cols | `GOOGLESHEETS_DELETE_DIMENSION` | `spreadsheet_id`, `sheet_name`, dimension |
| Spreadsheet info | `GOOGLESHEETS_GET_SPREADSHEET_INFO` | `spreadsheet_id` |
| Update tab props | `GOOGLESHEETS_UPDATE_SHEET_PROPERTIES` | `spreadsheetId`, properties |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/grafana-dashboards/SKILL.md b/web-app/public/skills/grafana-dashboards/SKILL.md
index 7f62512b..4f869a54 100644
--- a/web-app/public/skills/grafana-dashboards/SKILL.md
+++ b/web-app/public/skills/grafana-dashboards/SKILL.md
@@ -1,6 +1,8 @@
---
name: grafana-dashboards
-description: Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces.
+description: "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ..."
+risk: unknown
+source: community
---
# Grafana Dashboards
diff --git a/web-app/public/skills/graphql-architect/SKILL.md b/web-app/public/skills/graphql-architect/SKILL.md
index 87a96670..b6f5fb25 100644
--- a/web-app/public/skills/graphql-architect/SKILL.md
+++ b/web-app/public/skills/graphql-architect/SKILL.md
@@ -1,11 +1,13 @@
---
name: graphql-architect
-description: Master modern GraphQL with federation, performance optimization,
+description: "Master modern GraphQL with federation, performance optimization,"
and enterprise security. Build scalable schemas, implement advanced caching,
and design real-time systems. Use PROACTIVELY for GraphQL architecture or
performance optimization.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/graphql/SKILL.md b/web-app/public/skills/graphql/SKILL.md
index 90cc3600..bdd6c753 100644
--- a/web-app/public/skills/graphql/SKILL.md
+++ b/web-app/public/skills/graphql/SKILL.md
@@ -1,7 +1,8 @@
---
name: graphql
-description: "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully."
+description: "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# GraphQL
@@ -66,3 +67,6 @@ Normalized cache with type policies
## Related Skills
Works well with: `backend`, `postgres-wizard`, `nextjs-app-router`, `react-patterns`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/haskell-pro/SKILL.md b/web-app/public/skills/haskell-pro/SKILL.md
index 210053b5..f29160b1 100644
--- a/web-app/public/skills/haskell-pro/SKILL.md
+++ b/web-app/public/skills/haskell-pro/SKILL.md
@@ -5,6 +5,8 @@ description: Expert Haskell engineer specializing in advanced type systems, pure
type-level programming, concurrency, and architecture guidance.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/helm-chart-scaffolding/SKILL.md b/web-app/public/skills/helm-chart-scaffolding/SKILL.md
index 8d1848ac..376b7db0 100644
--- a/web-app/public/skills/helm-chart-scaffolding/SKILL.md
+++ b/web-app/public/skills/helm-chart-scaffolding/SKILL.md
@@ -1,6 +1,8 @@
---
name: helm-chart-scaffolding
-description: Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.
+description: "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl..."
+risk: unknown
+source: community
---
# Helm Chart Scaffolding
diff --git a/web-app/public/skills/helpdesk-automation/SKILL.md b/web-app/public/skills/helpdesk-automation/SKILL.md
index 0b2b4287..239820c4 100644
--- a/web-app/public/skills/helpdesk-automation/SKILL.md
+++ b/web-app/public/skills/helpdesk-automation/SKILL.md
@@ -3,6 +3,8 @@ name: helpdesk-automation
description: "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# HelpDesk Automation via Rube MCP
@@ -164,3 +166,6 @@ Backward pagination:
| List views | HELPDESK_LIST_VIEWS | (none) |
| List canned responses | HELPDESK_LIST_CANNED_RESPONSES | (none) |
| List custom fields | HELPDESK_LIST_CUSTOM_FIELDS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-content/SKILL.md b/web-app/public/skills/hig-components-content/SKILL.md
new file mode 100644
index 00000000..5e6e86d9
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/SKILL.md
@@ -0,0 +1,91 @@
+---
+name: hig-components-content
+version: 1.0.0
+description: ">"
+ Apple Human Interface Guidelines for content display components. Use this skill when the user asks about
+ "charts component", "collection view", "image view", "web view", "color well", "image well",
+ "activity view", "lockup", "data visualization", "content display", displaying images, rendering
+ web content, color pickers, or presenting collections of items in Apple apps.
+ Also use when the user says "how should I display charts", "what's the best way to show images",
+ "should I use a web view", "how do I build a grid of items", "what component shows media",
+ or "how do I present a share sheet".
+ Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data
+ visualization patterns, hig-components-layout for structural containers, hig-platforms for
+ platform-specific component behavior.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Content Components
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Adapt to different sizes and contexts.** Content components must work across screen sizes, orientations, and multitasking configurations. Use Auto Layout and size classes.
+
+2. **Make content accessible.** Charts need audio graph support. Images need alt text. Collections need proper VoiceOver navigation order. All content components need labels and descriptions.
+
+3. **Maintain visual hierarchy.** Use spacing, sizing, and grouping to establish clear information hierarchy. Primary content should be visually prominent.
+
+4. **Use system components first.** Evaluate UICollectionView, SwiftUI Charts, WKWebView before building custom. System components come with built-in accessibility and platform adaptation.
+
+5. **Respect platform conventions.** A collection on tvOS uses large lockups with parallax. The same collection on iOS uses compact cells with touch targets. On visionOS, content gains depth and hover effects.
+
+6. **Handle empty states.** Show a meaningful empty state with guidance on how to populate it, not a blank screen.
+
+7. **Optimize for performance.** Use lazy loading, cell reuse, pagination, and prefetching for large datasets.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [charts.md](references/charts.md) | Charts | Swift Charts, bar/line/area/point marks, chart accessibility, audio graphs |
+| [collections.md](references/collections.md) | Collections | Grid/list layouts, compositional layout, selection, reordering, diffable data sources |
+| [image-views.md](references/image-views.md) | Image Views | Aspect ratio handling, content modes, SF Symbol images, accessibility |
+| [image-wells.md](references/image-wells.md) | Image Wells | Drag-and-drop image selection, macOS-specific, placeholder content |
+| [color-wells.md](references/color-wells.md) | Color Wells | Color selection UI, system color picker, custom color spaces |
+| [web-views.md](references/web-views.md) | Web Views | WKWebView, SFSafariViewController, navigation controls, content restrictions |
+| [activity-views.md](references/activity-views.md) | Activity Views | Share sheets, activity items, custom activities, action extensions |
+| [lockups.md](references/lockups.md) | Lockups | Image+text elements, tvOS card layouts, focus effects, shelf layouts |
+
+## Component Selection Guide
+
+| Content Need | Recommended Component | Platform Notes |
+|---|---|---|
+| Visualizing quantitative data | Charts (Swift Charts) | iOS 16+, macOS 13+, watchOS 9+ |
+| Browsing a grid or list of items | Collection View | Compositional layout for complex arrangements |
+| Displaying a single image | Image View | Support aspect ratio fitting; provide accessibility description |
+| Selecting an image via drag or browse | Image Well | macOS primarily; use image pickers on iOS |
+| Selecting a color | Color Well | Triggers system color picker; macOS, iOS 14+ |
+| Showing web content inline | Web View (WKWebView) | Use SFSafariViewController for external browsing |
+| Sharing content to other apps | Activity View | System share sheet with configurable activity types |
+| Content card (image + text) | Lockup | Primarily tvOS; adaptable to other platforms |
+
+## Output Format
+
+1. **Component recommendation with rationale**, referencing the relevant HIG reference file.
+2. **Configuration guidance** -- key properties and setup.
+3. **Accessibility requirements** for the recommended component.
+4. **Platform-specific notes** for targeted platforms.
+
+## Questions to Ask
+
+1. What type of content? (Quantitative data, images, web content, browsable collection, share action?)
+2. Which platforms?
+3. Static or dynamic content?
+4. How much content? (Few items vs hundreds/thousands affects component choice and optimization.)
+
+## Related Skills
+
+- **hig-foundations** -- Color, typography, accessibility, and image guidelines
+- **hig-patterns** -- Data visualization, sharing, and loading patterns
+- **hig-components-layout** -- Structural containers (scroll views, lists, split views) hosting content
+- **hig-platforms** -- Platform-specific component behavior (lockups on tvOS, web views on macOS)
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-content/references/activity-views.md b/web-app/public/skills/hig-components-content/references/activity-views.md
new file mode 100644
index 00000000..f02c7b2a
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/activity-views.md
@@ -0,0 +1,79 @@
+---
+title: "Activity views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/activity-views
+
+# Activity views
+
+An activity view — often called a _share sheet_ — presents a range of tasks that people can perform in the current context.
+
+
+
+Activity views present sharing activities like messaging and actions like Copy and Print, in addition to quick access to frequently used apps. People typically reveal a share sheet by choosing an Action button while viewing a page or document, or after they’ve selected an item. An activity view can appear as a sheet or a popover, depending on the device and orientation.
+
+You can provide app-specific activities that can appear in a share sheet when people open it within your app or game. For example, Photos provides app-specific actions like Copy Photo, Add to Album, and Adjust Location. By default, the system lists app-specific actions before actions — such as Add to Files or AirPlay — that are available in multiple apps or throughout the system. People can edit the list of actions to ensure that it displays the ones they use most and to add new ones.
+
+You can also create app extensions to provide custom share and action activities that people can use in other apps. (An _app extension_ is code you provide that people can install and use outside of your app.) For example, you might create a custom share activity that people can install to help them share a webpage with a specific social media service. Even though macOS doesn’t provide an activity view, you can create share and action app extensions that people can use on a Mac. For guidance, see [Share and action extensions](https://developer.apple.com/design/human-interface-guidelines/activity-views#Share-and-action-extensions).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/activity-views#Best-practices)
+
+**Avoid creating duplicate versions of common actions that are already available in the activity view.** For example, providing a duplicate Print action is unnecessary and confusing because people wouldn’t know how to distinguish your action from the system-provided one. If you need to provide app-specific functionality that’s similar to an existing action, give it a custom title. For example, if you let people use custom formatting to print a bank transaction, use a title that helps people understand what your print activity does, like “Print Transaction.”
+
+**Consider using a symbol to represent your custom activity.** [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) provides a comprehensive set of configurable symbols you can use to communicate items and concepts in an activity view. If you need to create a custom interface icon, center it in an area measuring about 70x70 pixels. For guidance, see [Icons](https://developer.apple.com/design/human-interface-guidelines/icons).
+
+**Write a succinct, descriptive title for each custom action you provide.** If a title is too long, the system wraps it and may truncate it. Prefer a single verb or a brief verb phrase that clearly communicates what the action does. Avoid including your company or product name in an action title. In contrast, the share sheet displays the title of a share activity — typically a company name — below the icon that represents it.
+
+**Make sure activities are appropriate for the current context.** Although you can’t reorder system-provided tasks in an activity view, you can exclude tasks that aren’t applicable to your app. For example, if it doesn’t make sense to print from within your app, you can exclude the Print activity. You can also identify which custom tasks to show at any given time.
+
+**Use the Share button to display an activity view.** People are accustomed to accessing system-provided activities when they choose the Share button. Avoid confusing people by providing an alternative way to do the same thing.
+
+
+
+
+
+## [Share and action extensions](https://developer.apple.com/design/human-interface-guidelines/activity-views#Share-and-action-extensions)
+
+Share extensions give people a convenient way to share information from the current context with apps, social media accounts, and other services. Action extensions let people initiate content-specific tasks — like adding a bookmark, copying a link, editing an inline image, or displaying selected text in another language — without leaving the current context.
+
+The system presents share and action extensions differently depending on the platform:
+
+ * In iOS and iPadOS, share and action extensions are displayed in the share sheet that appears when people choose an Action button.
+
+ * In macOS, people access share extensions by clicking a Share button in the toolbar or choosing Share in a context menu. People can access an action extension by holding the pointer over certain types of embedded content — like an image they add to a Mail compose window — clicking a toolbar button, or choosing a quick action in a Finder window.
+
+
+
+
+**If necessary, create a custom interface that feels familiar to people.** For a share extension, prefer the system-provided composition view because it provides a consistent sharing experience that people already know. For an action extension, include your app name. If you need to present an interface, include elements of your app’s interface to help people understand that your extension and your app are related.
+
+**Streamline and limit interaction.** People appreciate extensions that let them perform a task in just a few steps. For example, a share extension might immediately post an image to a social media account with a single tap or click.
+
+**Avoid placing a modal view above your extension.** By default, the system displays an extension within a modal view. While it might be necessary to display an alert above an extension, avoid displaying additional modal views.
+
+**If necessary, provide an image that communicates the purpose of your extension.** A share extension automatically uses your app icon, helping give people confidence that your app provided the extension. For an action extension, prefer using a [symbol](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) or creating an interface [icon](https://developer.apple.com/design/human-interface-guidelines/icons) that clearly identifies the task.
+
+**Use your main app to denote the progress of a lengthy operation.** An activity view dismisses immediately after people complete the task in your share or action extension. If a task is time-consuming, continue it in the background, and give people a way to check the status in your main app. Although you can use a notification to tell people about a problem, don’t notify them simply because the task completes.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/activity-views#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or visionOS. Not supported in macOS, tvOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/activity-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/activity-views#Related)
+
+[Sheets](https://developer.apple.com/design/human-interface-guidelines/sheets)
+
+[Popovers](https://developer.apple.com/design/human-interface-guidelines/popovers)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/activity-views#Developer-documentation)
+
+[`UIActivityViewController`](https://developer.apple.com/documentation/UIKit/UIActivityViewController) — UIKit
+
+[`UIActivity`](https://developer.apple.com/documentation/UIKit/UIActivity) — UIKit
+
+[App Extension Support](https://developer.apple.com/documentation/Foundation/app-extension-support) — Foundation
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/activity-views#Videos)
+
+[ Design for Collaboration with Messages ](https://developer.apple.com/videos/play/wwdc2022/10015)
+
diff --git a/web-app/public/skills/hig-components-content/references/charts.md b/web-app/public/skills/hig-components-content/references/charts.md
new file mode 100644
index 00000000..72e49afc
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/charts.md
@@ -0,0 +1,180 @@
+---
+title: "Charts | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/charts
+
+# Charts
+
+Organize data in a chart to communicate information with clarity and visual appeal.
+
+
+
+An effective chart highlights a few key pieces of information in a dataset, helping people gain insights and make decisions. For example, people might use a chart to:
+
+ * Learn how upcoming weather conditions might affect their plans.
+
+ * Analyze stock prices to understand past performance and discover trends.
+
+ * Review fitness data to monitor their progress and set new goals.
+
+
+
+
+To learn about designing charts to enhance your experience, see [Charting data](https://developer.apple.com/design/human-interface-guidelines/charting-data); for developer guidance, see [Creating a chart using Swift Charts](https://developer.apple.com/documentation/Charts/Creating-a-chart-using-Swift-Charts).
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/charts#Anatomy)
+
+A chart comprises several graphical elements that depict the values in a dataset and convey information about them.
+
+
+
+A _mark_ is a visual representation of a data value. You create a chart by supplying one or more series of data values, assigning each value to a mark. To specify the style of chart you want to display — such as bar chart, line chart, or scatter plot — you choose a mark type, such as bar, line, or point (for guidance, see [Marks](https://developer.apple.com/design/human-interface-guidelines/charts#Marks)). The general task of depicting individual data values in a chart is called _plotting_ , and the area that contains the marks is called the _plot area_.
+
+To depict a value, each type of mark uses visual attributes that are determined by a scale, which maps data values like numbers, dates, or categories to visual characteristics like position, color, or height. For example, a bar mark can use a particular height to represent the magnitude of a value and a particular position to represent the time at which the value occurred.
+
+To give people the context they need to interpret a chart’s visual characteristics, you supply descriptive content that can take a few different forms.
+
+You can use an _axis_ to help define a frame of reference for the data represented by a set of marks. Many charts display a pair of axes at the edges of the plot area — one horizontal and one vertical — where each axis represents a variable like time, amount, or category.
+
+An axis can include _ticks_ , which are reference points that help people visually locate the position of important values along the axis, such as a 0, 50%, and 100%. Many charts display _grid lines_ that each extend from a tick across the plot area to help people visually estimate a data value when its mark isn’t near an axis.
+
+You also have multiple ways to describe chart elements to help people interpret the data and to highlight the key information you want to communicate. For example, you can supply _labels_ that name items like axes, grid lines, ticks, or marks, and _accessibility labels_ that describe chart elements for people who use assistive technologies. To provide context and additional details, you can create descriptive titles, subtitles, and annotations. When needed, you can also create a legend, which describes chart properties that aren’t related to a mark’s position, such as the use of color or shape to denote different value categories.
+
+Clear, accurate descriptions can help make a chart more approachable and accessible; to learn about additional ways to improve the accessibility of your chart, see [Enhancing the accessibility of a chart](https://developer.apple.com/design/human-interface-guidelines/charts#Enhancing-the-accessibility-of-a-chart).
+
+## [Marks](https://developer.apple.com/design/human-interface-guidelines/charts#Marks)
+
+**Choose a mark type based on the information you want to communicate about the data.** Some of the most familiar mark types are bar, line, and point; for developer guidance on these and other mark types, see [Swift Charts](https://developer.apple.com/documentation/Charts).
+
+_Bar_ marks work well in charts that help people compare values in different categories or view the relative proportions of various parts in a whole. When used to help people understand data that changes over time, bar charts work especially well when each value can represent a sum, like the total number of steps taken in a day.
+
+
+
+_Line_ marks can also show how values change over time. In a line chart, a line connects all data values in one series of data. The slope of the line reveals the magnitude of change between data values and can help people visualize overall trends.
+
+
+
+_Point_ marks help you depict individual data values as visually distinct marks. A set of point marks can show how two different properties of your data relate to each other, helping people inspect individual data values and identify outliers and clusters.
+
+
+
+**Consider combining mark types when it adds clarity to your chart.** For example, if you use a line chart to show a change over time, you might want to add point marks on top of the line to highlight individual data points. By combining points with a line, you can help people understand the overall trend while also drawing their attention to individual values.
+
+## [Axes](https://developer.apple.com/design/human-interface-guidelines/charts#Axes)
+
+**Use a fixed or dynamic axis range depending on the meaning of your chart.** In a _fixed_ range, the upper and lower bounds of the axis never change, whereas in a _dynamic_ range, the upper and lower bounds can vary with the current data. Consider using a fixed range when specific minimum and maximum values are meaningful for all possible data values. For example, people expect a chart that shows a battery’s current charge to have a minimum value of 0% (completely empty) and a maximum value of 100% (completely full).
+
+
+
+In contrast, consider using a dynamic range when the possible data values can vary widely and you want the marks to fill the available plot area. For example, the upper bound of the Y axis range in the Health app’s Steps chart varies so that the largest number of steps in a particular time period is close to the top of the chart.
+
+Weekly range
+
+Monthly range
+
+**Define the value of the lower bound based on mark type and chart usage.** For example, bar charts can work well when you use zero for the lower bound of the Y axis, because doing so lets people visually compare the relative heights of individual bars to get a reasonable estimate of their values. In contrast, defining a lower bound of zero can sometimes make meaningful differences between values more difficult to discern. For example, a heart rate chart that always uses zero for the lower bound could obscure important differences between resting and active readings because the differences occur in a range that’s far from zero.
+
+**Prefer familiar sequences of values in the tick and grid-line labels for an axis.** For example, if you use a common number sequence like 0, 5, 10, etc., people are likely to know at a glance that each tick value equals the previous value plus five. Even though a sequence like 1, 6, 11, etc., follows the same rule, it’s not common, so most people are likely to spend extra time thinking about the interval between values.
+
+**Tailor the appearance of grid lines and labels to a chart’s use cases.** Too many grid lines can be visually overwhelming, distracting people from the data; too few grid lines can make it difficult to estimate a mark’s value. To help you determine the appropriate density and visual weight of these elements, consider a chart’s context in the interface, the interactions you support, and the tasks people can do in the chart. For example, if people can inspect individual data points by interacting with a chart, you might use fewer grid lines and light label colors to ensure the data remains visually prominent.
+
+## [Descriptive content](https://developer.apple.com/design/human-interface-guidelines/charts#Descriptive-content)
+
+**Write descriptions that help people understand what a chart does before they view it.** When you provide information-rich titles and labels that describe the purpose and functionality of a chart, you give people the context they need before they dive in and examine the details. Providing context in this way is especially important for VoiceOver users and those with certain types of cognitive disabilities because they rely on your descriptions to understand the purpose and primary message of your chart before they decide to investigate it further.
+
+**Summarize the main message of your chart to help make it approachable and useful for everyone.** Although a primary reason to use a chart is to display the data that supports the main message, it’s essential to summarize key information so that people can grasp it quickly. For example, Weather provides a title and subtitle that succinctly describe the expected precipitation for the next hour, giving people the most important information without requiring them to examine the details of the chart.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/charts#Best-practices)
+
+**Establish a consistent visual hierarchy that helps communicate the relative importance of various chart elements.** Typically, you want the data itself to be most prominent, while letting the descriptions and axes provide additional context without competing with the data.
+
+**In a compact environment, maximize the width of the plot area to give people enough space to comfortably examine a chart.** To help important data fit well in a given width, ensure that labels on a vertical axis are as short as possible without losing clarity. You might also consider describing units in other areas of the chart, such as in a title, and placing a longer axis label, such as a category name, inside the plot area when doing so doesn’t obscure important information.
+
+**Make every chart in your app accessible.** Charts — like all infographics — need to be fully accessible to everyone, regardless of how they perceive content. For example, it’s essential to support VoiceOver, which describes onscreen content to help people get information and navigate without needing to see the screen (to learn more about VoiceOver, see [Vision](https://www.apple.com/accessibility/vision/)). In addition to supplying accessibility labels that describe the components of your chart, you can enhance the VoiceOver experience by also using Audio Graphs. [Audio graphs](https://developer.apple.com/documentation/Accessibility/audio-graphs) provides chart information to VoiceOver, which constructs a set of tones that audibly represent a chart’s data values and their trend; it also lets you present high-level text summaries that provide additional context. For guidance, see [Enhancing the accessibility of a chart](https://developer.apple.com/design/human-interface-guidelines/charts#Enhancing-the-accessibility-of-a-chart).
+
+**Let people interact with the data when it makes sense, but don’t require interaction to reveal critical information.** In Stocks, for example, people are often most interested in a stock’s performance over time, so the app displays a line graph that depicts performance during the time period people choose, such as one day, three months, or five years. If people want to explore additional details, they can drag a vertical indicator through the line graph, revealing the value at the selected time.
+
+**Make it easy for everyone to interact with a chart.** Sometimes, chart marks are too small to target with a finger or a pointer, making your chart hard to use for people with reduced motor control and uncomfortable for everyone. When this is the case, consider expanding the hit target to include the entire plot area, letting people scrub across the area to reveal various values.
+
+**Make an interactive chart easy to navigate when using keyboard commands (including full keyboard access) or Switch Control.** By default, these input types tend to visit individual onscreen elements in a linear sequence, such as the sequence of values in a data file. If you want to provide a custom navigation experience in your chart, here are two main ways to do so. The first way is to use accessibility APIs (such as [`accessibilityRespondsToUserInteraction(_:)`](https://developer.apple.com/documentation/SwiftUI/View/accessibilityRespondsToUserInteraction\(_:\))) to specify a logical and predictable path through your chart’s information. For example, you might want to let people navigate along the X axis instead of jumping back and forth. The second way — which is particularly useful if you need to present a very large dataset — is to let people move focus among subsets of values instead of navigating through all individual data points. Note that both of these customizations can also enhance the VoiceOver experience, even when your chart isn’t interactive. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Help people notice important changes in a chart.** For example, if people don’t notice when marks or axes change, they can misread a chart. Animating such changes can help people notice them, but you need to highlight the changes in other ways, too, to ensure that VoiceOver users and people who turn off animations know about them. For developer guidance, see [`UIAccessibility.Notification`](https://developer.apple.com/documentation/UIKit/UIAccessibility/Notification) (UIKit) or [`NSAccessibility.Notification`](https://developer.apple.com/documentation/AppKit/NSAccessibility-swift.struct/Notification) (AppKit).
+
+**Align a chart with surrounding interface elements.** For example, it often works well to align the leading edge of a chart with the leading edge of other views in a screen. One way to maintain a clean leading edge in a chart is to display the label for each vertical grid line on its trailing side. You might also consider shifting the Y axis to the trailing side of the chart so that its tick labels don’t protrude past the chart’s leading edge. If you end up with a label that doesn’t appear to be associated with anything, you can use a tick to anchor it to a grid line.
+
+## [Color](https://developer.apple.com/design/human-interface-guidelines/charts#Color)
+
+As in all other parts of your interface, using color in a chart can help you clarify information, evoke your brand, and provide visual continuity. For general guidance on using color in ways that everyone can appreciate, see [Inclusive color](https://developer.apple.com/design/human-interface-guidelines/color#Inclusive-color).
+
+**Avoid relying solely on color to differentiate between different pieces of data or communicate essential information in a chart.** Using meaningful color in a chart works well to highlight differences and elevate key details, but it’s crucial to include alternative ways to convey this information so that people can use your chart regardless of whether they can discern colors. One way to supplement color is to use different shapes or patterns to depict different parts of data. For example, in addition to using red and black or red and white colors, Health uses two different shapes in the point marks that represent the two components of blood pressure.
+
+
+
+**Aid comprehension by adding visual separation between contiguous areas of color.** For example, in a bar chart that stacks marks in a single row or column, it’s common to assign a different color to each mark. In this design, adding separators between the marks can help people distinguish individual ones.
+
+
+
+## [Enhancing the accessibility of a chart](https://developer.apple.com/design/human-interface-guidelines/charts#Enhancing-the-accessibility-of-a-chart)
+
+When you use Swift Charts to create a chart, you get a default implementation of [Audio graphs](https://developer.apple.com/documentation/Accessibility/audio-graphs), in addition to a default accessibility element for each mark (or group of marks) that describes its value.
+
+**Consider using Audio Graphs to give VoiceOver users more information about your chart.** You can customize the default Audio Graphs implementation that Swift Charts provides by supplying a chart title and descriptive summary that VoiceOver speaks to help people understand the purpose and main features of your chart. If you don’t use Audio Graphs, you need to provide an overview of the chart’s structure and purpose. For example, you need to identify the chart’s type — such as bar or line — explain what each axis represents, and describe details like the upper and lower axis bounds.
+
+Important
+
+Unlike an image — which requires one descriptive accessibility label — a chart often needs to offer an accessibility label for each important or interactive element. Depending on the purpose of your chart and the scope and density of its marks, you need to decide whether it’s essential to describe each mark or whether it improves the accessibility experience to describe groups of marks. In some cases, it can make sense to use a single accessibility label that provides a succinct, high-level description of the chart, such as when you use a small version of a chart in a button that reveals a more detailed version.
+
+**Write accessibility labels that support the purpose of your chart.** For example, Maps shows elevation for a cycling route using a chart that represents the change in elevation over the course of the route. The purpose of the chart is to give people a sense of the terrain for the entire route, not to provide individual elevations. For this reason, Maps provides accessibility labels that summarize the elevation changes over a portion of the route, rather than providing labels for each individual moment. In contrast, Health offers an accessibility label for each bar in the Steps chart, because the purpose of the chart is to give people their actual step count for each tracking period.
+
+For the focused section of this cycling elevation chart, VoiceOver provides information about that portion of the route, including distance and elevation changes.
+
+The following guidelines can help you write useful accessibility labels for chart elements.
+
+ * **Prioritize clarity and comprehensiveness.** In general, it’s rarely enough to merely report a data value unless you also include context that helps people understand it, like the date or location that’s associated with it. Aim to concisely describe the context for a value without repeating information that people can get in other ways, like an axis name that Audio Graphs or your overview provides. Follow context-setting information with a succinct description of the element’s details.
+
+ * **Avoid using subjective terms.** Subjective words — like rapidly, gradually, and almost — communicate your interpretation of the data. To help people form their own interpretations, use actual values in your descriptions.
+
+ * **Maximize clarity in data descriptions by avoiding potentially ambiguous formats and abbreviations.** For example, using “June 6” is clearer than using “6/6”; similarly, spelling out “60 minutes” or “60 meters” is clearer than using the abbreviation “60m.”
+
+ * **Describe what the chart’s details represent, not what they look like.** Consider a chart that uses red and blue colors to help people visually distinguish two different data series. It’s crucial to create accessibility labels that identify what each series represents, but describing the colors that visually represent them can add unnecessary information and be distracting.
+
+ * **Be consistent throughout your app when referring to a specific axis.** For example, if you always mention the X axis first, people can spend less time figuring out which axis is relevant in a description.
+
+
+
+
+**Hide visible text labels for axes and ticks from assistive technologies.** Axis and tick labels help people visually assess trends in a chart and estimate mark values. VoiceOver users can get mark values and trend information through accessibility labels and Audio Graphs, so they don’t generally need the content in the visible labels.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/charts#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/charts#watchOS)
+
+**In general, avoid requiring complex chart interactions in your watchOS app.** As much as possible, prefer displaying useful information people can get at a glance and supporting simple interactions when they add value. If you also offer a version of your app in another platform, consider using it to display more details and to support additional interactions with your chart. For example, Heart Rate in watchOS displays a chart of the wearer’s heart-rate data for the current day, whereas the Health app on iPhone displays heart-rate data for several different periods of time and lets people examine individual marks.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/charts#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/charts#Related)
+
+[Charting data](https://developer.apple.com/design/human-interface-guidelines/charting-data)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/charts#Developer-documentation)
+
+[Swift Charts](https://developer.apple.com/documentation/Charts)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/charts#Videos)
+
+[ Bring Swift Charts to the third dimension ](https://developer.apple.com/videos/play/wwdc2025/313)
+
+[ Design app experiences with charts ](https://developer.apple.com/videos/play/wwdc2022/110342)
+
+[ Design an effective chart ](https://developer.apple.com/videos/play/wwdc2022/110340)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/charts#Change-log)
+
+Date| Changes
+---|---
+September 23, 2022| New page.
+
diff --git a/web-app/public/skills/hig-components-content/references/collections.md b/web-app/public/skills/hig-components-content/references/collections.md
new file mode 100644
index 00000000..4aa63662
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/collections.md
@@ -0,0 +1,48 @@
+---
+title: "Collections | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/collections
+
+# Collections
+
+A collection manages an ordered set of content and presents it in a customizable and highly visual layout.
+
+
+
+Generally speaking, collections are ideal for showing image-based content.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/collections#Best-practices)
+
+**Use the standard row or grid layout whenever possible.** Collections display content by default in a horizontal row or a grid, which are simple, effective appearances that people expect. Avoid creating a custom layout that might confuse people or draw undue attention to itself.
+
+**Consider using a table instead of a collection for text.** It’s generally simpler and more efficient to view and digest textual information when it’s displayed in a scrollable list.
+
+**Make it easy to choose an item.** If it’s too difficult to get to an item in your collection, people will get frustrated and lose interest before reaching the content they want. Use adequate padding around images to keep focus or hover effects easy to see and prevent content from overlapping.
+
+**Add custom interactions when necessary.** By default, people can tap to select, touch and hold to edit, and swipe to scroll. If your app requires it, you can add more gestures for performing custom actions.
+
+**Consider using animations to provide feedback when people insert, delete, or reorder items.** Collections support standard animations for these actions, and you can also use custom animations.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/collections#Platform-considerations)
+
+ _No additional considerations for macOS, tvOS, or visionOS. Not supported in watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/collections#iOS-iPadOS)
+
+**Use caution when making dynamic layout changes.** The layout of a collection can change dynamically. Be sure any changes make sense and are easy to track. If possible, try to avoid changing the layout while people are viewing and interacting with it, unless it’s in response to an explicit action.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/collections#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/collections#Related)
+
+[Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables)
+
+[Image views](https://developer.apple.com/design/human-interface-guidelines/image-views)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/collections#Developer-documentation)
+
+[`UICollectionView`](https://developer.apple.com/documentation/UIKit/UICollectionView) — UIKit
+
+[`NSCollectionView`](https://developer.apple.com/documentation/AppKit/NSCollectionView) — AppKit
+
diff --git a/web-app/public/skills/hig-components-content/references/color-wells.md b/web-app/public/skills/hig-components-content/references/color-wells.md
new file mode 100644
index 00000000..53fda514
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/color-wells.md
@@ -0,0 +1,42 @@
+---
+title: "Color wells | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/color-wells
+
+# Color wells
+
+A color well lets people adjust the color of text, shapes, guides, and other onscreen elements.
+
+
+
+A color well displays a color picker when people tap or click it. This color picker can be the system-provided one or a custom interface that you design.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/color-wells#Best-practices)
+
+**Consider the system-provided color picker for a familiar experience.** Using the built-in color picker provides a consistent experience, in addition to letting people save a set of colors they can access from any app. The system-defined color picker can also help provide a familiar experience when developing apps across iOS, iPadOS, and macOS.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/color-wells#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or visionOS. Not supported in tvOS or watchOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/color-wells#macOS)
+
+When people click a color well, it receives a highlight to provide visual confirmation that it’s active. It then opens a color picker so people can choose a color. After they make a selection, the color well updates to show the new color.
+
+Color wells also support drag and drop, so people can drag colors from one color well to another, and from the color picker to a color well.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/color-wells#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/color-wells#Related)
+
+[Color](https://developer.apple.com/design/human-interface-guidelines/color)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/color-wells#Developer-documentation)
+
+[`UIColorWell`](https://developer.apple.com/documentation/UIKit/UIColorWell) — UIKit
+
+[`UIColorPickerViewController`](https://developer.apple.com/documentation/UIKit/UIColorPickerViewController) — UIKit
+
+[`NSColorWell`](https://developer.apple.com/documentation/AppKit/NSColorWell) — AppKit
+
+[Color Programming Topics](https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/DrawColor/DrawColor.html)
+
diff --git a/web-app/public/skills/hig-components-content/references/image-views.md b/web-app/public/skills/hig-components-content/references/image-views.md
new file mode 100644
index 00000000..823ee343
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/image-views.md
@@ -0,0 +1,82 @@
+---
+title: "Image views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/image-views
+
+# Image views
+
+An image view displays a single image — or in some cases, an animated sequence of images — on a transparent or opaque background.
+
+
+
+Within an image view, you can stretch, scale, size to fit, or pin the image to a specific location. Image views are typically not interactive.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/image-views#Best-practices)
+
+**Use an image view when the primary purpose of the view is simply to display an image.** In rare cases where you might want an image to be interactive, configure a system-provided [button](https://developer.apple.com/design/human-interface-guidelines/buttons) to display the image instead of adding button behaviors to an image view.
+
+**If you want to display an icon in your interface, consider using a symbol or interface icon instead of an image view.** [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) provides a large library of streamlined, vector-based images that you can render with various colors and opacities. An [icon](https://developer.apple.com/design/human-interface-guidelines/icons) (also called a glyph or template image) is typically a bitmap image in which the nontransparent pixels can receive color. Both symbols and interface icons can use the accent colors people choose.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/image-views#Content)
+
+An image view can contain rich image data in various formats, like PNG, JPEG, and PDF. For more guidance, see [Images](https://developer.apple.com/design/human-interface-guidelines/images).
+
+**Take care when overlaying text on images.** Compositing text on top of images can decrease both the clarity of the image and the legibility of the text. To help improve the results, ensure the text contrasts well with the image, and consider ways to make the text object stand out, like adding a text shadow or background layer.
+
+**Aim to use a consistent size for all images in an animated sequence.** When you prescale images to fit the view, the system doesn’t have to perform any scaling. In cases where the system must do the scaling, performance is generally better when all images are the same size and shape.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/image-views#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/image-views#macOS)
+
+**If your app needs an editable image view, use an image well.** An [image well](https://developer.apple.com/design/human-interface-guidelines/image-wells) is an image view that supports copying, pasting, dragging, and using the Delete key to clear its content.
+
+**Use an image button instead of an image view to make a clickable image.** An [image button](https://developer.apple.com/design/human-interface-guidelines/buttons#Image-buttons) contains an image or icon, appears in a view, and initiates an instantaneous app-specific action.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/image-views#tvOS)
+
+Many tvOS images combine multiple layers with transparency to create a feeling of depth. For guidance, see [Layered images](https://developer.apple.com/design/human-interface-guidelines/images#Layered-images).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/image-views#visionOS)
+
+Windows in visionOS apps and games can use image views to display 2D and stereoscopic images, as well as spatial photos. If your app uses RealityKit, you can also display images of any type outside of image views next to 3D content, or generate a spatial scene from an existing 2D image. For design guidance, see [Images > visionOS](https://developer.apple.com/design/human-interface-guidelines/images#visionOS); for developer guidance, see [`ImagePresentationComponent`](https://developer.apple.com/documentation/RealityKit/ImagePresentationComponent).
+
+For guidance on presenting other 3D content in a window or volume, see [Windows > visionOS](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/image-views#watchOS)
+
+**Use SwiftUI to create animations when possible.** Alternatively, you can use WatchKit to animate a sequence of images within an image element if necessary. For developer guidance, see [`WKImageAnimatable`](https://developer.apple.com/documentation/WatchKit/WKImageAnimatable).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/image-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/image-views#Related)
+
+[Images](https://developer.apple.com/design/human-interface-guidelines/images)
+
+[Image wells](https://developer.apple.com/design/human-interface-guidelines/image-wells)
+
+[Image buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Image-buttons)
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/image-views#Developer-documentation)
+
+[`Image`](https://developer.apple.com/documentation/SwiftUI/Image) — SwiftUI
+
+[`UIImageView`](https://developer.apple.com/documentation/UIKit/UIImageView) — UIKit
+
+[`NSImageView`](https://developer.apple.com/documentation/AppKit/NSImageView) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/image-views#Videos)
+
+[ Support HDR images in your app ](https://developer.apple.com/videos/play/wwdc2023/10181)
+
+[ Add rich graphics to your SwiftUI app ](https://developer.apple.com/videos/play/wwdc2021/10021)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/image-views#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-content/references/image-wells.md b/web-app/public/skills/hig-components-content/references/image-wells.md
new file mode 100644
index 00000000..ec631e31
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/image-wells.md
@@ -0,0 +1,34 @@
+---
+title: "Image wells | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/image-wells
+
+# Image wells
+
+An image well is an editable version of an image view.
+
+
+
+After selecting an image well, people can copy and paste its image or delete it. People can also drag a new image into an image well without selecting it first.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/image-wells#Best-practices)
+
+**Revert to a default image when necessary.** If your image well requires an image, display the default image again if people clear the content of the image well.
+
+**If your image well supports copy and paste, make sure the standard copy and paste menu items are available.** People generally expect to choose these menu items — or use the standard keyboard shortcuts — to interact with an image well. For guidance, see [Edit menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Edit-menu).
+
+For related guidance, see [Image views](https://developer.apple.com/design/human-interface-guidelines/image-views).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/image-wells#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/image-wells#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/image-wells#Related)
+
+[Image views](https://developer.apple.com/design/human-interface-guidelines/image-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/image-wells#Developer-documentation)
+
+[`NSImageView`](https://developer.apple.com/documentation/AppKit/NSImageView) — AppKit
+
diff --git a/web-app/public/skills/hig-components-content/references/lockups.md b/web-app/public/skills/hig-components-content/references/lockups.md
new file mode 100644
index 00000000..1ecf9dd0
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/lockups.md
@@ -0,0 +1,78 @@
+---
+title: "Lockups | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/lockups
+
+# Lockups
+
+Lockups combine multiple separate views into a single, interactive unit.
+
+
+
+Each lockup consists of a content view, a header, and a footer. Headers appear above the main content for a lockup, and footers appear below the main content. All three views expand and contract together as the lockup gets focus.
+
+According to the needs of your app, you can combine four types of lockup: cards, caption buttons, monograms, and posters.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/lockups#Best-practices)
+
+**Allow adequate space between lockups.** A focused lockup expands in size, so leave enough room between lockups to avoid overlapping or displacing other lockups. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout).
+
+
+
+**Use consistent lockup sizes within a row or group.** A group of buttons or a row of content images is more visually appealing when the widths and heights of all elements match.
+
+For developer guidance, see [`TVLockupView`](https://developer.apple.com/documentation/TVUIKit/TVLockupView) and [`TVLockupHeaderFooterView`](https://developer.apple.com/documentation/TVUIKit/TVLockupHeaderFooterView).
+
+## [Cards](https://developer.apple.com/design/human-interface-guidelines/lockups#Cards)
+
+A card combines a header, footer, and content view to present ratings and reviews for media items.
+
+
+
+For developer guidance, see [`TVCardView`](https://developer.apple.com/documentation/TVUIKit/TVCardView).
+
+## [Caption buttons](https://developer.apple.com/design/human-interface-guidelines/lockups#Caption-buttons)
+
+A caption button can include a title and a subtitle beneath the button. A caption button can contain either an image or text.
+
+Make sure that when people focus on them, caption buttons tilt with the motion that they swipe. When aligned vertically, caption buttons tilt up and down. When aligned horizontally, caption buttons tilt left and right. When displayed in a grid, caption buttons tilt both vertically and horizontally.
+
+
+
+For developer guidance, see [`TVCaptionButtonView`](https://developer.apple.com/documentation/TVUIKit/TVCaptionButtonView).
+
+## [Monograms](https://developer.apple.com/design/human-interface-guidelines/lockups#Monograms)
+
+Monograms identify people, usually the cast and crew for a media item. Each monogram consists of a circular picture of the person and their name. If an image isn’t available, the person’s initials appear in place of an image.
+
+**Prefer images over initials.** An image of a person creates a more intimate connection than text.
+
+
+
+For developer guidance, see [`TVMonogramContentView`](https://developer.apple.com/documentation/TVUIKit/TVMonogramContentView).
+
+## [Posters](https://developer.apple.com/design/human-interface-guidelines/lockups#Posters)
+
+Posters consist of an image and an optional title and subtitle, which are hidden until the poster comes into focus. Posters can be any size, but the size needs to be appropriate for their content. For related guidance, see [Image views](https://developer.apple.com/design/human-interface-guidelines/image-views).
+
+
+
+For developer guidance, see [`TVPosterView`](https://developer.apple.com/documentation/TVUIKit/TVPosterView).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/lockups#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/lockups#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/lockups#Related)
+
+[Designing for tvOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/lockups#Developer-documentation)
+
+[`TVLockupView`](https://developer.apple.com/documentation/TVUIKit/TVLockupView) — TVUIKit
+
+[`TVLockupHeaderFooterView`](https://developer.apple.com/documentation/TVUIKit/TVLockupHeaderFooterView) — TVUIKit
+
diff --git a/web-app/public/skills/hig-components-content/references/web-views.md b/web-app/public/skills/hig-components-content/references/web-views.md
new file mode 100644
index 00000000..d8637e46
--- /dev/null
+++ b/web-app/public/skills/hig-components-content/references/web-views.md
@@ -0,0 +1,36 @@
+---
+title: "Web views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/web-views
+
+# Web views
+
+A web view loads and displays rich web content, such as embedded HTML and websites, directly within your app.
+
+
+
+For example, Mail uses a web view to show HTML content in messages.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/web-views#Best-practices)
+
+**Support forward and back navigation when appropriate.** Web views support forward and back navigation, but this behavior isn’t available by default. If people are likely to use your web view to visit multiple pages, allow forward and back navigation, and provide corresponding controls to initiate these features.
+
+**Avoid using a web view to build a web browser.** Using a web view to let people briefly access a website without leaving the context of your app is fine, but Safari is the primary way people browse the web. Attempting to replicate the functionality of Safari in your app is unnecessary and discouraged.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/web-views#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or visionOS. Not supported in tvOS or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/web-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/web-views#Related)
+
+[Webkit.org](https://webkit.org/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/web-views#Developer-documentation)
+
+[`WKWebView`](https://developer.apple.com/documentation/WebKit/WKWebView) — WebKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/web-views#Videos)
+
+[ Explore WKWebView additions ](https://developer.apple.com/videos/play/wwdc2021/10032)
+
diff --git a/web-app/public/skills/hig-components-controls/SKILL.md b/web-app/public/skills/hig-components-controls/SKILL.md
new file mode 100644
index 00000000..3bfe5397
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/SKILL.md
@@ -0,0 +1,93 @@
+---
+name: hig-components-controls
+version: 1.0.0
+description: ">-"
+ Apple HIG guidance for selection and input controls including pickers, toggles,
+ sliders, steppers, segmented controls, combo boxes, text fields, text views,
+ labels, token fields, virtual keyboards, rating indicators, and gauges. Use
+ this skill when the user says "picker or segmented control," "how should my
+ form look," "what keyboard type should I use," "toggle vs checkbox," or asks
+ about picker design, toggle, switch, slider, stepper, text field, text input,
+ segmented control, combo box, label, token field, virtual keyboard, rating
+ indicator, gauge, form design, input validation, or control state management.
+ Cross-references: hig-components-menus, hig-components-dialogs,
+ hig-components-search.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Selection and Input Controls
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Clear current state.** Users must always see what is selected. Toggles show on/off, segmented controls highlight the active segment, pickers display the current selection.
+
+2. **Prefer standard system controls.** Built-in controls provide consistency and accessibility. Custom controls introduce a learning curve and may break assistive features.
+
+3. **Toggles for binary states.** On or off. In Settings-style screens, changes take effect immediately. In modal forms, changes commit on confirmation.
+
+4. **Segmented controls for mutually exclusive options.** 2-5 items, roughly equal importance, short labels.
+
+5. **Sliders for continuous values.** When precise numeric input is not critical. Provide min/max labels or icons for range endpoints.
+
+6. **Pickers for long option lists.** Too many options for a segmented control. Works well for dates, times, structured data.
+
+7. **Steppers for small, precise adjustments.** Increment/decrement in fixed steps. Display current value next to the stepper with reasonable min/max bounds.
+
+8. **Text fields for short, single-line input.** Text views for multi-line. Configure keyboard type to match expected input (email, URL, number).
+
+9. **Combo boxes: text input + selection list.** macOS. Type a value or choose from a predefined list when custom values are valid.
+
+10. **Token fields: discrete values as visual tokens.** macOS. For email recipients, tags, or collections of discrete items.
+
+11. **Gauges and rating indicators display values.** Gauges show a value within a range. Rating indicators show ratings (often stars). Display-only; use interactive variants for input.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [controls.md](references/controls.md) | General controls | States, affordance, system controls |
+| [toggles.md](references/toggles.md) | Toggles | On/off, immediate effect |
+| [segmented-controls.md](references/segmented-controls.md) | Segmented controls | 2-5 options, equal weight |
+| [sliders.md](references/sliders.md) | Sliders | Continuous range, min/max labels |
+| [steppers.md](references/steppers.md) | Steppers | Fixed steps, bounded values |
+| [pickers.md](references/pickers.md) | Pickers | Dates, times, long option sets |
+| [combo-boxes.md](references/combo-boxes.md) | Combo boxes | macOS, type or select, custom values |
+| [text-fields.md](references/text-fields.md) | Text fields | Short input, keyboard types, validation |
+| [text-views.md](references/text-views.md) | Text views | Multi-line, comments, descriptions |
+| [labels.md](references/labels.md) | Labels | Placement, VoiceOver support |
+| [token-fields.md](references/token-fields.md) | Token fields | macOS, chips, tags, recipients |
+| [virtual-keyboards.md](references/virtual-keyboards.md) | Virtual keyboards | Email, URL, number keyboard types |
+| [rating-indicators.md](references/rating-indicators.md) | Rating indicators | Star ratings, display-only |
+| [gauges.md](references/gauges.md) | Gauges | Level indicators, range display |
+
+## Output Format
+
+1. **Control recommendation with rationale** and why alternatives are less suitable.
+2. **State management** -- how the control communicates current state and whether changes apply immediately or on confirmation.
+3. **Validation approach** -- when to show errors and how to communicate rules.
+4. **Accessibility** -- labels, traits, hints for VoiceOver.
+
+## Questions to Ask
+
+1. What type of data? (Boolean, choice from fixed set, numeric, free-form text?)
+2. How many options?
+3. Which platforms? (Combo boxes and token fields are macOS-only)
+4. Settings screen or inline form?
+
+## Related Skills
+
+- **hig-components-menus** -- Buttons and pop-up buttons complementing selection controls
+- **hig-components-dialogs** -- Sheets and popovers containing forms
+- **hig-components-search** -- Search fields sharing text input patterns
+- **hig-inputs** -- Keyboard, pointer, gesture interactions with controls
+- **hig-foundations** -- Typography, color, layout for control styling
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-controls/references/combo-boxes.md b/web-app/public/skills/hig-components-controls/references/combo-boxes.md
new file mode 100644
index 00000000..c0e40575
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/combo-boxes.md
@@ -0,0 +1,40 @@
+---
+title: "Combo boxes | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/combo-boxes
+
+# Combo boxes
+
+A combo box combines a text field with a pull-down button in a single control.
+
+
+
+People can enter a custom value into the field or click the button to choose from a list of predefined values. When people enter a custom value, it’s not added to the list of choices.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/combo-boxes#Best-practices)
+
+**Populate the field with a meaningful default value from the list.** Although the field can be empty by default, it’s best when the default value refers to the hidden choices. The default value doesn’t have to be the first item in the list.
+
+**Use an introductory label to let people know what types of items to expect.** Generally, use title-style capitalization for labels and end them with a colon. For related guidance, see [Labels](https://developer.apple.com/design/human-interface-guidelines/labels).
+
+**Provide relevant choices.** People appreciate the ability to enter a custom value, as well as the convenience of choosing from a list of the most likely choices.
+
+**Make sure list items aren’t wider than the text field.** If an item is too wide, the text field might truncate it, which is hard for people to read.
+
+For guidance, see [Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields) and [Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/combo-boxes#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/combo-boxes#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/combo-boxes#Related)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/combo-boxes#Developer-documentation)
+
+[`NSComboBox`](https://developer.apple.com/documentation/AppKit/NSComboBox) — AppKit
+
diff --git a/web-app/public/skills/hig-components-controls/references/controls.md b/web-app/public/skills/hig-components-controls/references/controls.md
new file mode 100644
index 00000000..ae9955f4
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/controls.md
@@ -0,0 +1,112 @@
+---
+title: "Controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/controls
+
+# Controls
+
+In iOS and iPadOS, a control provides quick access to a feature of your app from Control Center, the Lock Screen, or the Action button.
+
+
+
+A control is a button or toggle that provides quick access to your app’s features from other areas of the system. Control buttons perform an action, link to a specific area of your app, or launch a [camera experience on a locked device](https://developer.apple.com/design/human-interface-guidelines/controls#Camera-experiences-on-a-locked-device). Control toggles switch between two states, such as on and off.
+
+People can add controls to Control Center by pressing and holding in an empty area of Control Center, to the Lock Screen by customizing their Lock Screen, and to the Action button by configuring the Action button in the Settings app.
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/controls#Anatomy)
+
+Controls contain a symbol image, a title, and, optionally, a value. The symbol visually represents what the control does and can be a symbol from [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) or a custom symbol. The title describes what the control relates to, and the value represents the state of the control. For example, the title can display the name of a light in a room, while the value can display whether it’s on or off.
+
+
+
+Controls display their information differently depending on where they appear:
+
+ * In Control Center, a control displays its symbol and, at larger sizes, its title and value.
+
+ * On the Lock Screen, a control displays its symbol.
+
+ * On iPhone devices with a control assigned to the Action button, pressing and holding it displays the control’s symbol in the Dynamic Island, as well as its value (if present).
+
+
+
+
+
+
+Control toggle in Control Center
+
+
+
+Control toggle on the Lock Screen
+
+
+
+Control toggle in the Dynamic Island
+performed from the Action button
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/controls#Best-practices)
+
+**Offer controls for actions that provide the most benefit without having to launch your app.** For example, launching a Live Activity from a control creates an easy and seamless experience that informs someone about progress without having to navigate to your app to stay up to date. For guidance, see [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities).
+
+**Update controls when someone interacts with them, when an action completes, or remotely with a push notification.** Update the contents of a control to accurately reflect the state and show if an action is still in progress.
+
+**Choose a descriptive symbol that suggests the behavior of the control.** Depending on where a person adds a control, it may not display the title and value, so the symbol needs to convey enough information about the control’s action. For control toggles, provide a symbol for both the on and off states. For example, use the SF Symbols `door.garage.open` and `door.garage.closed` to represent a control that opens and closes a garage door. For guidance, see [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+**Use symbol animations to highlight state changes.** For control toggles, animate the transition between both on and off states. For control buttons with actions that have a duration, animate indefinitely while the action performs and stop animating when the action is complete. For developer guidance, see [Symbols](https://developer.apple.com/documentation/Symbols) and [`SymbolEffect`](https://developer.apple.com/documentation/Symbols/SymbolEffect).
+
+**Select a tint color that works with your app’s brand.** The system applies this tint color to a control toggle’s symbol in its on state. When a person performs the action of a control from the Action button, the system also uses this tint color to display the value and symbol in the Dynamic Island. For guidance, see [Branding](https://developer.apple.com/design/human-interface-guidelines/branding).
+
+Nontinted control toggle in the off state
+
+Tinted control toggle in the on state
+
+**Help people provide additional information the system needs to perform an action.** A person may need to configure a control to perform a desired action — for example, select a specific light in a house to turn on and off. If a control requires configuration, prompt people to complete this step when they first add it. People can reconfigure the control at any time. For developer guidance, see [`promptsForUserConfiguration()`](https://developer.apple.com/documentation/SwiftUI/ControlWidgetConfiguration/promptsForUserConfiguration\(\)).
+
+
+
+**Provide hint text for the Action button.** When a person presses the Action button, the system displays hint text to help them understand what happens when they press and hold. When someone presses and holds the Action button, the system performs the action configured to it. Use verbs to construct the hint text. For developer guidance, see [`controlWidgetActionHint(_:)`](https://developer.apple.com/documentation/SwiftUI/View/controlWidgetActionHint\(_:\)-5yoyh).
+
+
+
+
+
+**If your control title or value can vary, include a placeholder.** Placeholder information tells people what your control does when the title and value are situational. The system displays this information when someone brings up the controls gallery in Control Center or the Lock Screen and chooses your control, or before they assign it to the Action button.
+
+**Hide sensitive information when the device is locked.** When the device is locked, consider having the system redact the title and value to hide personal or security-related information. Specify if the system needs to redact the symbol state as well. If specified, the system redacts the title and value, and displays the symbol in its off state.
+
+Control toggle with no information hidden
+
+Control toggle with information hidden on a locked device
+
+**Require authentication for actions that affect security.** For example, require people to unlock their device to access controls to lock or unlock the door to their house or start their car. For developer guidance, see [`IntentAuthenticationPolicy`](https://developer.apple.com/documentation/AppIntents/IntentAuthenticationPolicy).
+
+## [Camera experiences on a locked device](https://developer.apple.com/design/human-interface-guidelines/controls#Camera-experiences-on-a-locked-device)
+
+If your app supports camera capture, starting with iOS 18 you can create a control that launches directly to your app’s camera experience while the device is locked. For any task beyond capture, a person must authenticate and unlock their device to complete the task in your app. For developer guidance, see [LockedCameraCapture](https://developer.apple.com/documentation/LockedCameraCapture).
+
+**Use the same camera UI in your app and your camera experience.** Sharing UI leverages people’s familiarity with the app. By using the same UI, the transition to the app is seamless when someone captures content and taps a button to perform additional tasks, such as posting to a social network or editing a photo.
+
+**Provide instructions for adding the control.** Help people understand how to add the control that launches this camera experience.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/controls#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, watchOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/controls#Related)
+
+[Widgets](https://developer.apple.com/design/human-interface-guidelines/widgets)
+
+[Action button](https://developer.apple.com/design/human-interface-guidelines/action-button)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/controls#Developer-documentation)
+
+[LockedCameraCapture](https://developer.apple.com/documentation/LockedCameraCapture)
+
+[WidgetKit](https://developer.apple.com/documentation/WidgetKit)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/controls#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| New page.
+
diff --git a/web-app/public/skills/hig-components-controls/references/gauges.md b/web-app/public/skills/hig-components-controls/references/gauges.md
new file mode 100644
index 00000000..ec1a3d37
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/gauges.md
@@ -0,0 +1,74 @@
+---
+title: "Gauges | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/gauges
+
+# Gauges
+
+A gauge displays a specific numerical value within a range of values.
+
+
+
+In addition to indicating the current value in a range, a gauge can provide more context about the range itself. For example, a temperature gauge can use text to identify the highest and lowest temperatures in the range and display a spectrum of colors that visually reinforce the changing values.
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/gauges#Anatomy)
+
+A gauge uses a circular or linear path to represent a range of values, mapping the current value to a specific point on the path. A standard gauge displays an indicator that shows the current value’s location; a gauge that uses the capacity style displays a fill that stops at the value’s location on the path.
+
+Circular and linear gauges in both standard and capacity styles are also available in a variant that’s visually similar to watchOS complications. This variant — called accessory — works well in iOS Lock Screen widgets and anywhere you want to echo the appearance of complications.
+
+Note
+
+In addition to gauges, macOS also supports level indicators, some of which have visual styles that are similar to gauges. For guidance, see [macOS](https://developer.apple.com/design/human-interface-guidelines/gauges#macOS).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/gauges#Best-practices)
+
+**Write succinct labels that describe the current value and both endpoints of the range.** Although not every gauge style displays all labels, VoiceOver reads the visible labels to help people understand the gauge without seeing the screen.
+
+**Consider filling the path with a gradient to help communicate the purpose of the gauge.** For example, a temperature gauge might use colors that range from red to blue to represent temperatures that range from hot to cold.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/gauges#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, visionOS, or watchOS. Not supported in tvOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/gauges#macOS)
+
+In addition to supporting gauges, macOS also defines a level indicator that displays a specific numerical value within a range. You can configure a level indicator to convey capacity, rating, or — rarely — relevance.
+
+The capacity style can depict discrete or continuous values.
+
+
+
+**Continuous.** A horizontal translucent track that fills with a solid bar to indicate the current value.
+
+
+
+**Discrete.** A horizontal row of separate, equally sized, rectangular segments. The number of segments matches the total capacity, and the segments fill completely — never partially — with color to indicate the current value.
+
+**Consider using the continuous style for large ranges.** A large value range can make the segments of a discrete capacity indicator too small to be useful.
+
+**Consider changing the fill color to inform people about significant parts of the range.** By default, the fill color for both capacity indicator styles is green. If it makes sense in your app, you can change the fill color when the current value reaches certain levels, such as very low, very high, or just past the middle. You can change the fill color of the entire indicator or you can use the tiered state to show a sequence of several colors in one indicator, as shown below.
+
+Tiered level appearance
+
+For guidance using the rating style to help people rank something, see [Rating indicators](https://developer.apple.com/design/human-interface-guidelines/rating-indicators).
+
+Although rarely used, the relevance style can communicate relevancy using a shaded horizontal bar. For example, a relevance indicator might appear in a list of search results, helping people visualize the relevancy of the results when sorting or comparing multiple items.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/gauges#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/gauges#Related)
+
+[Ratings and reviews](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/gauges#Developer-documentation)
+
+[`Gauge`](https://developer.apple.com/documentation/SwiftUI/Gauge) — SwiftUI
+
+[`NSLevelIndicator`](https://developer.apple.com/documentation/AppKit/NSLevelIndicator) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/gauges#Change-log)
+
+Date| Changes
+---|---
+September 23, 2022| New page.
+
diff --git a/web-app/public/skills/hig-components-controls/references/labels.md b/web-app/public/skills/hig-components-controls/references/labels.md
new file mode 100644
index 00000000..f3ad7730
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/labels.md
@@ -0,0 +1,92 @@
+---
+title: "Labels | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/labels
+
+# Labels
+
+A label is a static piece of text that people can read and often copy, but not edit.
+
+
+
+Labels display text throughout the interface, in buttons, menu items, and views, helping people understand the current context and what they can do next.
+
+The term _label_ refers to uneditable text that can appear in various places. For example:
+
+ * Within a button, a label generally conveys what the button does, such as Edit, Cancel, or Send.
+
+ * Within many lists, a label can describe each item, often accompanied by a symbol or an image.
+
+ * Within a view, a label might provide additional context by introducing a control or describing a common action or task that people can perform in the view.
+
+
+
+
+Developer note
+
+To display uneditable text, SwiftUI defines two components: [`Label`](https://developer.apple.com/documentation/SwiftUI/Label) and [`Text`](https://developer.apple.com/documentation/SwiftUI/Text).
+
+The guidance below can help you use a label to display text. In some cases, guidance for specific components — such as [action buttons](https://developer.apple.com/design/human-interface-guidelines/buttons), [menus](https://developer.apple.com/design/human-interface-guidelines/menus), and [lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables) — includes additional recommendations for using text.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/labels#Best-practices)
+
+**Use a label to display a small amount of text that people don’t need to edit.** If you need to let people edit a small amount of text, use a [text field](https://developer.apple.com/design/human-interface-guidelines/text-fields). If you need to display a large amount of text, and optionally let people edit it, use a [text view](https://developer.apple.com/design/human-interface-guidelines/text-views).
+
+**Prefer system fonts.** A label can display plain or styled text, and it supports Dynamic Type (where available) by default. If you adjust the style of a label or use custom fonts, make sure the text remains legible.
+
+**Use system-provided label colors to communicate relative importance.** The system defines four label colors that vary in appearance to help you give text different levels of visual importance. For additional guidance, see [Color](https://developer.apple.com/design/human-interface-guidelines/color).
+
+System color| Example usage| iOS, iPadOS, tvOS, visionOS| macOS
+---|---|---|---
+Label| Primary information| [`label`](https://developer.apple.com/documentation/UIKit/UIColor/label)| [`labelColor`](https://developer.apple.com/documentation/AppKit/NSColor/labelColor)
+Secondary label| A subheading or supplemental text| [`secondaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/secondaryLabel)| [`secondaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/secondaryLabelColor)
+Tertiary label| Text that describes an unavailable item or behavior| [`tertiaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/tertiaryLabel)| [`tertiaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/tertiaryLabelColor)
+Quaternary label| Watermark text| [`quaternaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/quaternaryLabel)| [`quaternaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/quaternaryLabelColor)
+
+**Make useful label text selectable.** If a label contains useful information — like an error message, a location, or an IP address — consider letting people select and copy it for pasting elsewhere.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/labels#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, or visionOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/labels#macOS)
+
+Developer note
+
+To display uneditable text in a label, use the [`isEditable`](https://developer.apple.com/documentation/AppKit/NSTextField/isEditable) property of [`NSTextField`](https://developer.apple.com/documentation/AppKit/NSTextField).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/labels#watchOS)
+
+Date and time text components (shown below on the left) display the current date, the current time, or a combination of both. You can configure a date text component to use a variety of formats, calendars, and time zones. A countdown timer text component (shown below on the right) displays a precise countdown or count-up timer. You can configure a timer text component to display its count value in a variety of formats.
+
+Date and time labels
+
+Timer label
+
+When you use the system-provided date and timer text components, watchOS automatically adjusts the label’s presentation to fit the available space. The system also updates the content without further input from your app.
+
+Consider using date and timer components in complications. For design guidance, see [Complications](https://developer.apple.com/design/human-interface-guidelines/components/system-experiences/complications); for developer guidance, see [`Text`](https://developer.apple.com/documentation/SwiftUI/Text).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/labels#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/labels#Related)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+[Text views](https://developer.apple.com/design/human-interface-guidelines/text-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/labels#Developer-documentation)
+
+[`Label`](https://developer.apple.com/documentation/SwiftUI/Label) — SwiftUI
+
+[`Text`](https://developer.apple.com/documentation/SwiftUI/Text) — SwiftUI
+
+[`UILabel`](https://developer.apple.com/documentation/UIKit/UILabel) — UIKit
+
+[`NSTextField`](https://developer.apple.com/documentation/AppKit/NSTextField) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/labels#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Updated guidance to reflect changes in watchOS 10.
+
diff --git a/web-app/public/skills/hig-components-controls/references/pickers.md b/web-app/public/skills/hig-components-controls/references/pickers.md
new file mode 100644
index 00000000..0b5b11de
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/pickers.md
@@ -0,0 +1,128 @@
+---
+title: "Pickers | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/pickers
+
+# Pickers
+
+A picker displays one or more scrollable lists of distinct values that people can choose from.
+
+
+
+The system provides several styles of pickers, each of which offers different types of selectable values and has a different appearance. The exact values shown in a picker, and their order, depend on the device language.
+
+Pickers help people enter information by letting them choose single or multipart values. Date pickers specifically offer additional ways to choose values, like selecting a day in a calendar view or entering dates and times using a numeric keypad.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/pickers#Best-practices)
+
+**Consider using a picker to offer medium-to-long lists of items.** If you need to display a fairly short list of choices, consider using a [pull-down button](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons) instead of a picker. Although a picker makes it easy to scroll quickly through many items, it may add too much visual weight to a short list of items. On the other hand, if you need to present a very large set of items, consider using a [list or table](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables). Lists and tables can adjust in height, and tables can include an index, which makes it much faster to target a section of the list.
+
+**Use predictable and logically ordered values.** Before people interact with a picker, many of its values can be hidden. It’s best when people can predict what the hidden values are, such as with an alphabetized list of countries, so they can move through the items quickly.
+
+**Avoid switching views to show a picker.** A picker works well when displayed in context, below or in proximity to the field people are editing. A picker typically appears at the bottom of a window or in a popover.
+
+**Consider providing less granularity when specifying minutes in a date picker.** By default, a minute list includes 60 values (0 to 59). You can optionally increase the minute interval as long as it divides evenly into 60. For example, you might want quarter-hour intervals (0, 15, 30, and 45).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/pickers#Platform-considerations)
+
+ _No additional considerations for visionOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/pickers#iOS-iPadOS)
+
+A date picker is an efficient interface for selecting a specific date, time, or both, using touch, a keyboard, or a pointing device. You can display a date picker in one of the following styles:
+
+ * Compact — A button that displays editable date and time content in a modal view.
+
+ * Inline — For time only, a button that displays wheels of values; for dates and times, an inline calendar view.
+
+ * Wheels — A set of scrolling wheels that also supports data entry through built-in or external keyboards.
+
+ * Automatic — A system-determined style based on the current platform and date picker mode.
+
+
+
+
+A date picker has four modes, each of which presents a different set of selectable values.
+
+ * Date — Displays months, days of the month, and years.
+
+ * Time — Displays hours, minutes, and (optionally) an AM/PM designation.
+
+ * Date and time — Displays dates, hours, minutes, and (optionally) an AM/PM designation.
+
+ * Countdown timer — Displays hours and minutes, up to a maximum of 23 hours and 59 minutes. This mode isn’t available in the inline or compact styles.
+
+
+
+
+The exact values shown in a date picker, and their order, depend on the device location.
+
+Here are several examples of date pickers showing different combinations of style and mode.
+
+ * Compact
+ * Inline
+ * Wheels
+
+
+
+In a compact layout, a picker opens as a popover over your content.
+
+In an inline layout, a picker opens inline with your content.
+
+Another example of an inline picker uses wheels to choose values for date and time.
+
+**Use a compact date picker when space is constrained.** The compact style displays a button that shows the current value in your app’s accent color. When people tap the button, the date picker opens a modal view, providing access to a familiar calendar-style editor and time picker. Within the modal view, people can make multiple edits to dates and times before tapping outside the view to confirm their choices.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/pickers#macOS)
+
+**Choose a date picker style that suits your app.** There are two styles of date pickers in macOS: textual and graphical. The textual style is useful when you’re working with limited space and you expect people to make specific date and time selections. The graphical style is useful when you want to give people the option of browsing through days in a calendar or selecting a range of dates, or when the look of a clock face is appropriate for your app.
+
+For developer guidance, see [`NSDatePicker`](https://developer.apple.com/documentation/AppKit/NSDatePicker).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/pickers#tvOS)
+
+Pickers are available in tvOS with SwiftUI. For developer guidance, see [`Picker`](https://developer.apple.com/documentation/SwiftUI/Picker).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/pickers#watchOS)
+
+Pickers display lists of items that people navigate using the Digital Crown, which helps people manage selections in a precise and engaging way.
+
+A picker can display a list of items using the wheels style. watchOS can also display date and time pickers using the wheels style. For developer guidance, see [`Picker`](https://developer.apple.com/documentation/SwiftUI/Picker) and [`DatePicker`](https://developer.apple.com/documentation/SwiftUI/DatePicker).
+
+
+
+
+
+
+
+You can configure a picker to display an outline, caption, and scrolling indicator.
+
+For longer lists, the navigation link displays the picker as a button. When someone taps the button, the system shows the list of options. The person can also scrub through the options using the Digital Crown without tapping the button. For developer guidance, see [`navigationLink`](https://developer.apple.com/documentation/SwiftUI/PickerStyle/navigationLink).
+
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/pickers#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/pickers#Related)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+[Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/pickers#Developer-documentation)
+
+[`Picker`](https://developer.apple.com/documentation/SwiftUI/Picker) — SwiftUI
+
+[`UIDatePicker`](https://developer.apple.com/documentation/UIKit/UIDatePicker) — UIKit
+
+[`UIPickerView`](https://developer.apple.com/documentation/UIKit/UIPickerView) — UIKit
+
+[`NSDatePicker`](https://developer.apple.com/documentation/AppKit/NSDatePicker) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/pickers#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Updated guidance for using pickers in watchOS.
+
diff --git a/web-app/public/skills/hig-components-controls/references/rating-indicators.md b/web-app/public/skills/hig-components-controls/references/rating-indicators.md
new file mode 100644
index 00000000..968a5bc3
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/rating-indicators.md
@@ -0,0 +1,38 @@
+---
+title: "Rating indicators | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/rating-indicators
+
+# Rating indicators
+
+A rating indicator uses a series of horizontally arranged graphical symbols — by default, stars — to communicate a ranking level.
+
+
+
+A rating indicator doesn’t display partial symbols; it rounds the value to display complete symbols only. Within a rating indicator, symbols are always the same distance apart and don’t expand or shrink to fit the component’s width.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Best-practices)
+
+**Make it easy to change rankings.** When presenting a list of ranked items, let people adjust the rank of individual items inline without navigating to a separate editing screen.
+
+**If you replace the star with a custom symbol, make sure that its purpose is clear.** The star is a very recognizable ranking symbol, and people may not associate other symbols with a rating scale.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Platform-considerations)
+
+ _No additional considerations for macOS. Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Related)
+
+[Ratings and reviews](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Developer-documentation)
+
+[`NSLevelIndicator.Style.rating`](https://developer.apple.com/documentation/AppKit/NSLevelIndicator/Style/rating) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/rating-indicators#Change-log)
+
+Date| Changes
+---|---
+September 23, 2022| New page.
+
diff --git a/web-app/public/skills/hig-components-controls/references/segmented-controls.md b/web-app/public/skills/hig-components-controls/references/segmented-controls.md
new file mode 100644
index 00000000..473121e7
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/segmented-controls.md
@@ -0,0 +1,94 @@
+---
+title: "Segmented controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/segmented-controls
+
+# Segmented controls
+
+A segmented control is a linear set of two or more segments, each of which functions as a button.
+
+
+
+Within a segmented control, all segments are usually equal in width. Like [buttons](https://developer.apple.com/design/human-interface-guidelines/buttons), segments can contain text or images. Segments can also have text labels beneath them (or beneath the control as a whole).
+
+A segmented control offers a single choice from among a set of options, or in macOS, either a single choice or multiple choices. For example, in macOS Keynote people can select only one segment in the alignment options control to align selected text. In contrast, people can choose multiple segments in the font attributes control to combine styles like bold, italics, and underline. The toolbar of a Keynote window also uses a segmented control to let people show and hide various editing panes within the main window area.
+
+Single choice
+
+Multiple choices
+
+In addition to representing the state of a single or multiple-choice selection, a segmented control can function as a set of buttons that perform actions without showing a selection state. For example, the Reply, Reply all, and Forward buttons in macOS Mail. For developer guidance, see [`isMomentary`](https://developer.apple.com/documentation/UIKit/UISegmentedControl/isMomentary) and [`NSSegmentedControl.SwitchTracking.momentary`](https://developer.apple.com/documentation/AppKit/NSSegmentedControl/SwitchTracking/momentary).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Best-practices)
+
+**Use a segmented control to provide closely related choices that affect an object, state, or view.** For example, a segmented control in an inspector could let people choose one or more attributes to apply to a selection, or a segmented control in a toolbar could offer a set of actions to perform on the current view.
+
+
+
+In the iOS Health app, a segmented control provides a choice of time ranges for the activity graphs to display.
+
+**Consider a segmented control when it’s important to group functions together, or to clearly show their selection state.** Unlike other button styles, segmented controls preserve their grouping regardless of the view size or where they appear. This grouping can also help people understand at a glance which controls are currently selected.
+
+**Keep control types consistent within a single segmented control.** Don’t assign actions to segments in a control that otherwise represents selection state, and don’t show a selection state for segments in a control that otherwise performs actions.
+
+**Limit the number of segments in a control.** Too many segments can be hard to parse and time-consuming to navigate. Aim for no more than about five to seven segments in a wide interface and no more than about five segments on iPhone.
+
+**In general, keep segment size consistent.** When all segments have equal width, a segmented control feels balanced. To the extent possible, it’s best to keep icon and title widths consistent too.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Content)
+
+**Prefer using either text or images — not a mix of both — in a single segmented control.** Although individual segments can contain text labels or images, mixing the two in a single control can lead to a disconnected and confusing interface.
+
+**As much as possible, use content with a similar size in each segment.** Because all segments typically have equal width, it doesn’t look good if content fills some segments but not others.
+
+**Use nouns or noun phrases for segment labels.** Write text that describes each segment and uses [title-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64). A segmented control that displays text labels doesn’t need introductory text.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Platform-considerations)
+
+ _Not supported in watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#iOS-iPadOS)
+
+**Consider a segmented control to switch between closely related subviews.** A segmented control can be useful as a way to quickly switch between related subviews. For example, the segmented control in Calendar’s New Event sheet switches between the subviews for creating a new event and a new reminder. For switching between completely separate sections of an app, use a [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars) instead.
+
+
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#macOS)
+
+**Consider using introductory text to clarify the purpose of a segmented control.** When the control uses symbols or interface icons, you could also add a label below each segment to clarify its meaning. If your app includes tooltips, provide one for each segment in a segmented control.
+
+**Use a tab view in the main window area — instead of a segmented control — for view switching.** A [tab view](https://developer.apple.com/design/human-interface-guidelines/tab-views) supports efficient view switching and is similar in appearance to a [box](https://developer.apple.com/design/human-interface-guidelines/boxes) combined with a segmented control. Consider using a segmented control to help people switch views in a toolbar or inspector pane.
+
+
+
+**Consider supporting spring loading.** On a Mac equipped with a Magic Trackpad, spring loading lets people activate a segment by dragging selected items over it and force clicking without dropping the selected items. People can also continue dragging the items after a segment activates.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#tvOS)
+
+**Consider using a split view instead of a segmented control on screens that perform content filtering.** People generally find it easy to navigate back and forth between content and filtering options using a split view. Depending on its placement, a segmented control may not be as easy to access.
+
+**Avoid putting other focusable elements close to segmented controls.** Segments become selected when focus moves to them, not when people click them. Carefully consider where you position a segmented control relative to other interface elements. If other focusable elements are too close, people might accidentally focus on them when attempting to switch between segments.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#visionOS)
+
+When people look at a segmented control that uses icons, the system displays a tooltip that contains the descriptive text you supply.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Related)
+
+[Split views](https://developer.apple.com/design/human-interface-guidelines/split-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Developer-documentation)
+
+[`segmented`](https://developer.apple.com/documentation/SwiftUI/PickerStyle/segmented) — SwiftUI
+
+[`UISegmentedControl`](https://developer.apple.com/documentation/UIKit/UISegmentedControl) — UIKit
+
+[`NSSegmentedControl`](https://developer.apple.com/documentation/AppKit/NSSegmentedControl) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-controls/references/sliders.md b/web-app/public/skills/hig-components-controls/references/sliders.md
new file mode 100644
index 00000000..58dd6901
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/sliders.md
@@ -0,0 +1,92 @@
+---
+title: "Sliders | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/sliders
+
+# Sliders
+
+A slider is a horizontal track with a control, called a thumb, that people can adjust between a minimum and maximum value.
+
+
+
+As a slider’s value changes, the portion of track between the minimum value and the thumb fills with color. A slider can optionally display left and right icons that illustrate the meaning of the minimum and maximum values.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/sliders#Best-practices)
+
+**Customize a slider’s appearance if it adds value.** You can adjust a slider’s appearance — including track color, thumb image and tint color, and left and right icons — to blend with your app’s design and communicate intent. A slider that adjusts image size, for example, could show a small image icon on the left and a large image icon on the right.
+
+**Use familiar slider directions.** People expect the minimum and maximum sides of sliders to be consistent in all apps, with minimum values on the leading side and maximum values on the trailing side (for horizontal sliders) and minimum values at the bottom and maximum values at the top (for vertical sliders). For example, people expect to be able to move a horizontal slider that represents a percentage from 0 percent on the leading side to 100 percent on the trailing side.
+
+**Consider supplementing a slider with a corresponding text field and stepper.** Especially when a slider represents a wide range of values, people may appreciate seeing the exact slider value and having the ability to enter a specific value in a text field. Adding a stepper provides a convenient way for people to increment in whole values. For related guidance, see [Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields) and [Steppers](https://developer.apple.com/design/human-interface-guidelines/steppers).
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/sliders#Platform-considerations)
+
+ _Not supported in tvOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/sliders#iOS-iPadOS)
+
+**Don’t use a slider to adjust audio volume.** If you need to provide volume control in your app, use a volume view, which is customizable and includes a volume-level slider and a control for changing the active audio output device. For guidance, see [Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/sliders#macOS)
+
+Sliders in macOS can also include tick marks, making it easier for people to pinpoint a specific value within the range.
+
+In a linear slider either with or without tick marks, the thumb is a narrow lozenge shape, and the portion of track between the minimum value and the thumb is filled with color. A linear slider often includes supplementary icons that illustrate the meaning of the minimum and maximum values.
+
+In a circular slider, the thumb appears as a small circle. Tick marks, when present, appear as evenly spaced dots around the circumference of the slider.
+
+Linear slider without tick marks
+
+Linear slider with tick marks
+
+Circular slider
+
+**Consider giving live feedback as the value of a slider changes.** Live feedback shows people results in real time. For example, your Dock icons are dynamically scaled when adjusting the Size slider in Dock settings.
+
+**Choose a slider style that matches peoples’ expectations.** A horizontal slider is ideal when moving between a fixed starting and ending point. For example, a graphics app might offer a horizontal slider for setting the opacity level of an object between 0 and 100 percent. Use circular sliders when values repeat or continue indefinitely. For example, a graphics app might use a circular slider to adjust the rotation of an object between 0 and 360 degrees. An animation app might use a circular slider to adjust how many times an object spins when animated — four complete rotations equals four spins, or 1440 degrees of rotation.
+
+**Consider using a label to introduce a slider.** Labels generally use [sentence-style capitalization](https://help.apple.com/applestyleguide/#/apsgb744e4a3?sub=apdca93e113f1d64) and end with a colon. For guidance, see [Labels](https://developer.apple.com/design/human-interface-guidelines/labels).
+
+**Use tick marks to increase clarity and accuracy.** Tick marks help people understand the scale of measurements and make it easier to locate specific values.
+
+
+
+**Consider adding labels to tick marks for even greater clarity.** Labels can be numbers or words, depending on the slider’s values. It’s unnecessary to label every tick mark unless doing so is needed to reduce confusion. In many cases, labeling only the minimum and maximum values is sufficient. When the values of the slider are nonlinear, like in the Energy Saver settings pane, periodic labels provide context. It’s also a good idea to provide a [tooltip](https://developer.apple.com/design/human-interface-guidelines/offering-help#macOS-visionOS) that displays the value of the thumb when people hold their pointer over it.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/sliders#visionOS)
+
+**Prefer horizontal sliders.** It’s generally easier for people to gesture from side to side than up and down.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/sliders#watchOS)
+
+A slider is a horizontal track — appearing as a set of discrete steps or as a continuous bar — that represents a finite range of values. People can tap buttons on the sides of the slider to increase or decrease its value by a predefined amount.
+
+Discrete
+
+Continuous
+
+**If necessary, create custom glyphs to communicate what the slider does.** The system displays plus and minus signs by default.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/sliders#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/sliders#Related)
+
+[Steppers](https://developer.apple.com/design/human-interface-guidelines/steppers)
+
+[Pickers](https://developer.apple.com/design/human-interface-guidelines/pickers)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/sliders#Developer-documentation)
+
+[`Slider`](https://developer.apple.com/documentation/SwiftUI/Slider) — SwiftUI
+
+[`UISlider`](https://developer.apple.com/documentation/UIKit/UISlider) — UIKit
+
+[`NSSlider`](https://developer.apple.com/documentation/AppKit/NSSlider) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/sliders#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-controls/references/steppers.md b/web-app/public/skills/hig-components-controls/references/steppers.md
new file mode 100644
index 00000000..2fac9ba7
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/steppers.md
@@ -0,0 +1,40 @@
+---
+title: "Steppers | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/steppers
+
+# Steppers
+
+A stepper is a two-segment control that people use to increase or decrease an incremental value.
+
+
+
+A stepper sits next to a field that displays its current value, because the stepper itself doesn’t display a value.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/steppers#Best-practices)
+
+**Make the value that a stepper affects obvious.** A stepper itself doesn’t display any values, so make sure people know which value they’re changing when they use a stepper.
+
+**Consider pairing a stepper with a text field when large value changes are likely.** Steppers work well by themselves for making small changes that require a few taps or clicks. By contrast, people appreciate the option to use a field to enter specific values, especially when the values they use can vary widely. On a printing screen, for example, it can help to have both a stepper and a text field to set the number of copies.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/steppers#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or visionOS. Not supported in watchOS or tvOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/steppers#macOS)
+
+**For large value ranges, consider supporting Shift-click to change the value quickly.** If your app benefits from larger changes in a stepper’s value, it can be useful to let people Shift-click the stepper to change the value by more than the default increment (by 10 times the default, for example).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/steppers#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/steppers#Related)
+
+[Pickers](https://developer.apple.com/design/human-interface-guidelines/pickers)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/steppers#Developer-documentation)
+
+[`UIStepper`](https://developer.apple.com/documentation/UIKit/UIStepper) — UIKit
+
+[`NSStepper`](https://developer.apple.com/documentation/AppKit/NSStepper) — AppKit
+
diff --git a/web-app/public/skills/hig-components-controls/references/text-fields.md b/web-app/public/skills/hig-components-controls/references/text-fields.md
new file mode 100644
index 00000000..00dd41a6
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/text-fields.md
@@ -0,0 +1,88 @@
+---
+title: "Text fields | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/text-fields
+
+# Text fields
+
+A text field is a rectangular area in which people enter or edit small, specific pieces of text.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/text-fields#Best-practices)
+
+**Use a text field to request a small amount of information, such as a name or an email address.** To let people input larger amounts of text, use a [text view](https://developer.apple.com/design/human-interface-guidelines/text-views) instead.
+
+**Show a hint in a text field to help communicate its purpose.** A text field can contain placeholder text — such as “Email” or “Password” — when there’s no other text in the field. Because placeholder text disappears when people start typing, it can also be useful to include a separate label describing the field to remind people of its purpose.
+
+**Use secure text fields to hide private data.** Always use a secure text field when your app asks for sensitive data, such as a password. For developer guidance, see [`SecureField`](https://developer.apple.com/documentation/SwiftUI/SecureField).
+
+**To the extent possible, match the size of a text field to the quantity of anticipated text.** The size of a text field helps people visually gauge the amount of information to provide.
+
+**Evenly space multiple text fields.** If your layout includes multiple text fields, leave enough space between them so people can easily see which input field belongs with each introductory label. Stack multiple text fields vertically when possible, and use consistent widths to create a more organized layout. For example, the first and last name fields on an address form might be one width, while the address and city fields might be a different width.
+
+**Ensure that tabbing between multiple fields flows as people expect.** When tabbing between fields, move focus in a logical sequence. The system attempts to achieve this result automatically, so you won’t need to customize this too often.
+
+**Validate fields when it makes sense.** For example, if the only legitimate value for a field is a string of digits, your app needs to alert people if they’ve entered characters other than digits. The appropriate time to check the data depends on the context: when entering an email address, it’s best to validate when people switch to another field; when creating a user name or password, validation needs to happen before people switch to another field.
+
+**Use a number formatter to help with numeric data.** A number formatter automatically configures the text field to accept only numeric values. It can also display the value in a specific way, such as with a certain number of decimal places, as a percentage, or as currency. Don’t assume the actual presentation of data, however, as formatting can vary significantly based on people’s locale.
+
+Formatted text
+
+**Adjust line breaks according to the needs of the field.** By default, the system clips any text extending beyond the bounds of a text field. Alternatively, you can set up a text field to wrap text to a new line at the character or word level, or to truncate (indicated by an ellipsis) at the beginning, middle, or end.
+
+Clipped text
+
+Wrapped text
+
+Truncated text
+
+**Consider using an expansion tooltip to show the full version of clipped or truncated text.** An expansion tooltip behaves like a regular [tooltip](https://developer.apple.com/design/human-interface-guidelines/offering-help#macOS-visionOS) and appears when someone places the pointer over the field.
+
+**In iOS, iPadOS, tvOS, and visionOS apps, show the appropriate keyboard type.** Several different keyboard types are available, each designed to facilitate a different type of input, such as numbers or URLs. To streamline data entry, display the keyboard that’s appropriate for the type of content people are entering. For guidance, see [Virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards).
+
+**Minimize text entry in your tvOS and watchOS apps.** Entering long passages of text or filling out numerous text fields is time-consuming on Apple TV and Apple Watch. Minimize text input and consider gathering information more efficiently, such as with buttons.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/text-fields#Platform-considerations)
+
+ _No additional considerations for tvOS or visionOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/text-fields#iOS-iPadOS)
+
+**Display a Clear button in the trailing end of a text field to help people erase their input.** When this element is present, people can tap it to clear the text field’s contents, without having to keep tapping the Delete key.
+
+**Use images and buttons to provide clarity and functionality in text fields.** You can display custom images in both ends of a text field, or you can add a system-provided button, such as the Bookmarks button. In general, use the leading end of a text field to indicate a field’s purpose and the trailing end to offer additional features, such as bookmarking.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/text-fields#macOS)
+
+**Consider using a combo box if you need to pair text input with a list of choices.** For related guidance, see [Combo boxes](https://developer.apple.com/design/human-interface-guidelines/combo-boxes).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/text-fields#watchOS)
+
+**Present a text field only when necessary.** Whenever possible, prefer displaying a list of options rather than requiring text entry.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/text-fields#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/text-fields#Related)
+
+[Text views](https://developer.apple.com/design/human-interface-guidelines/text-views)
+
+[Combo boxes](https://developer.apple.com/design/human-interface-guidelines/combo-boxes)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/text-fields#Developer-documentation)
+
+[`TextField`](https://developer.apple.com/documentation/SwiftUI/TextField) — SwiftUI
+
+[`SecureField`](https://developer.apple.com/documentation/SwiftUI/SecureField) — SwiftUI
+
+[`UITextField`](https://developer.apple.com/documentation/UIKit/UITextField) — UIKit
+
+[`NSTextField`](https://developer.apple.com/documentation/AppKit/NSTextField) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/text-fields#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Updated guidance to reflect changes in watchOS 10.
+
diff --git a/web-app/public/skills/hig-components-controls/references/text-views.md b/web-app/public/skills/hig-components-controls/references/text-views.md
new file mode 100644
index 00000000..c3c63037
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/text-views.md
@@ -0,0 +1,56 @@
+---
+title: "Text views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/text-views
+
+# Text views
+
+A text view displays multiline, styled text content, which can optionally be editable.
+
+
+
+Text views can be any height and allow scrolling when the content extends outside of the view. By default, content within a text view is aligned to the leading edge and uses the system label color. In iOS, iPadOS, and visionOS, if a text view is editable, a keyboard appears when people select the view.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/text-views#Best-practices)
+
+**Use a text view when you need to display text that’s long, editable, or in a special format.** Text views differ from [text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields) and [labels](https://developer.apple.com/design/human-interface-guidelines/labels) in that they provide the most options for displaying specialized text and receiving text input. If you need to display a small amount of text, it’s simpler to use a label or — if the text is editable — a text field.
+
+**Keep text legible.** Although you can use multiple fonts, colors, and alignments in creative ways, it’s essential to maintain the readability of your content. It’s a good idea to adopt Dynamic Type so your text still looks good if people change text size on their device. Be sure to test your content with accessibility options turned on, such as bold text. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility) and [Typography](https://developer.apple.com/design/human-interface-guidelines/typography).
+
+**Make useful text selectable.** If a text view contains useful information such as an error message, a serial number, or an IP address, consider letting people select and copy it for pasting elsewhere.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/text-views#Platform-considerations)
+
+ _No additional considerations for macOS, visionOS, or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/text-views#iOS-iPadOS)
+
+**Show the appropriate keyboard type.** Several different keyboard types are available, each designed to facilitate a different type of input. To streamline data entry, the keyboard you display when editing a text view needs to be appropriate for the type of content. For guidance, see [Virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/text-views#tvOS)
+
+You can display text in tvOS using a text view. Because text input in tvOS is minimal by design, tvOS uses [text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields) for editable text instead.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/text-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/text-views#Related)
+
+[Labels](https://developer.apple.com/design/human-interface-guidelines/labels)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+[Combo boxes](https://developer.apple.com/design/human-interface-guidelines/combo-boxes)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/text-views#Developer-documentation)
+
+[`Text`](https://developer.apple.com/documentation/SwiftUI/Text) — SwiftUI
+
+[`UITextView`](https://developer.apple.com/documentation/UIKit/UITextView) — UIKit
+
+[`NSTextView`](https://developer.apple.com/documentation/AppKit/NSTextView) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/text-views#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Updated guidance to reflect changes in watchOS 10.
+
diff --git a/web-app/public/skills/hig-components-controls/references/toggles.md b/web-app/public/skills/hig-components-controls/references/toggles.md
new file mode 100644
index 00000000..e61003ce
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/toggles.md
@@ -0,0 +1,127 @@
+---
+title: "Toggles | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/toggles
+
+# Toggles
+
+A toggle lets people choose between a pair of opposing states, like on and off, using a different appearance to indicate each state.
+
+
+
+A toggle can have various styles, such as switch and checkbox, and different platforms can use these styles in different ways. For guidance, see [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/toggles#Platform-considerations).
+
+In addition to toggles, all platforms also support buttons that behave like toggles by using a different appearance for each state. For developer guidance, see [`ToggleStyle`](https://developer.apple.com/documentation/SwiftUI/ToggleStyle).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/toggles#Best-practices)
+
+**Use a toggle to help people choose between two opposing values that affect the state of content or a view.** A toggle always lets people manage the state of something, so if you need to support other types of actions — such as choosing from a list of items — use a different component, like a [pop-up button](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons).
+
+**Clearly identify the setting, view, or content the toggle affects.** In general, the surrounding context provides enough information for people to understand what they’re turning on or off. In some cases, often in macOS apps, you can also supply a label to describe the state the toggle controls. If you use a button that behaves like a toggle, you generally use an interface icon that communicates its purpose, and you update its appearance — typically by changing the background — based on the current state.
+
+**Make sure the visual differences in a toggle’s state are obvious.** For example, you might add or remove a color fill, show or hide the background shape, or change the inner details you display — like a checkmark or dot — to show that a toggle is on or off. Avoid relying solely on different colors to communicate state, because not everyone can perceive the differences.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/toggles#Platform-considerations)
+
+ _No additional considerations for tvOS, visionOS, or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/toggles#iOS-iPadOS)
+
+**Use the switch toggle style only in a list row.** You don’t need to supply a label in this situation because the content in the row provides the context for the state the switch controls.
+
+**Change the default color of a switch only if necessary.** The default green color tends to work well in most cases, but you might want to use your app’s accent color instead. Be sure to use a color that provides enough contrast with the uncolored appearance to be perceptible.
+
+Standard switch color
+
+Custom switch color
+
+**Outside of a list, use a button that behaves like a toggle, not a switch.** For example, the Phone app uses a toggle on the filter button to let users filter their recent calls. The app adds a blue highlight to indicate when the toggle is active, and removes it when the toggle is inactive.
+
+
+
+The Phone app uses a toggle to switch between all recent calls and various filter options. When someone chooses a filter, the toggle appears with a custom background drawn behind the symbol.
+
+
+
+When someone returns to the main Recents view, the toggle appears without anything behind the symbol.
+
+**Avoid supplying a label that explains the button’s purpose.** The interface icon you create — combined with the alternative background appearances you supply — help people understand what the button does. For developer guidance, see [`changesSelectionAsPrimaryAction`](https://developer.apple.com/documentation/UIKit/UIButton/changesSelectionAsPrimaryAction).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/toggles#macOS)
+
+In addition to the switch toggle style, macOS supports the checkbox style and also defines radio buttons that can provide similar behaviors.
+
+**Use switches, checkboxes, and radio buttons in the window body, not the window frame.** In particular, avoid using these components in a toolbar or status bar.
+
+#### [Switches](https://developer.apple.com/design/human-interface-guidelines/toggles#Switches)
+
+**Prefer a switch for settings that you want to emphasize.** A switch has more visual weight than a checkbox, so it looks better when it controls more functionality than a checkbox typically does. For example, you might use a switch to let people turn on or off a group of settings, instead of just one setting. For developer guidance, see [`switch`](https://developer.apple.com/documentation/SwiftUI/ToggleStyle/switch).
+
+**Within a grouped form, consider using a mini switch to control the setting in a single row.** The height of a mini switch is similar to the height of buttons and other controls, resulting in rows that have a consistent height. If you need to present a hierarchy of settings within a grouped form, you can use a regular switch for the primary setting and mini switches for the subordinate settings. For developer guidance, see [`GroupedFormStyle`](https://developer.apple.com/documentation/SwiftUI/GroupedFormStyle) and [`ControlSize`](https://developer.apple.com/documentation/SwiftUI/ControlSize).
+
+**In general, don’t replace a checkbox with a switch.** If you’re already using a checkbox in your interface, it’s probably best to keep using it.
+
+#### [Checkboxes](https://developer.apple.com/design/human-interface-guidelines/toggles#Checkboxes)
+
+A checkbox is a small, square button that’s empty when the button is off, contains a checkmark when the button is on, and can contain a dash when the button’s state is mixed. Typically, a checkbox includes a title on its trailing side. In an editable checklist, a checkbox can appear without a title or any additional content.
+
+**Use a checkbox instead of a switch if you need to present a hierarchy of settings.** The visual style of checkboxes helps them align well and communicate grouping. By using alignment — generally along the leading edge of the checkboxes — and indentation, you can show dependencies, such as when the state of a checkbox governs the state of subordinate checkboxes.
+
+
+
+**Consider using radio buttons if you need to present a set of more than two mutually exclusive options.** When people need to choose from options in addition to just “on” or “off,” using multiple radio buttons can help you clarify each option with a unique label.
+
+**Consider using a label to introduce a group of checkboxes if their relationship isn’t clear.** Describe the set of options, and align the label’s baseline with the first checkbox in the group.
+
+**Accurately reflect a checkbox’s state in its appearance.** A checkbox’s state can be on, off, or mixed. If you use a checkbox to globally turn on and off multiple subordinate checkboxes, show a mixed state when the subordinate checkboxes have different states. For example, you might need to present a text-style setting that turns all styles on or off, but also lets people choose a subset of individual style settings like bold, italic, or underline. For developer guidance, see [`allowsMixedState`](https://developer.apple.com/documentation/AppKit/NSButton/allowsMixedState).
+
+On
+
+Off
+
+Mixed
+
+#### [Radio buttons](https://developer.apple.com/design/human-interface-guidelines/toggles#Radio-buttons)
+
+A radio button is a small, circular button followed by a label. Typically displayed in groups of two to five, radio buttons present a set of mutually exclusive choices.
+
+
+
+A radio button’s state is either selected (a filled circle) or deselected (an empty circle). Although a radio button can also display a mixed state (indicated by a dash), this state is rarely useful because you can communicate multiple states by using additional radio buttons. If you need to show that a setting or item has a mixed state, consider using a checkbox instead.
+
+Selected
+
+Deselected
+
+**Prefer a set of radio buttons to present mutually exclusive options.** If you need to let people choose multiple options in a set, use checkboxes instead.
+
+**Avoid listing too many radio buttons in a set.** A long list of radio buttons takes up a lot of space in the interface and can be overwhelming. If you need to present more than about five options, consider using a component like a [pop-up button](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons) instead.
+
+**To present a single setting that can be on or off, prefer a checkbox.** Although a single radio button can also turn something on or off, the presence or absence of the checkmark in a checkbox can make the current state easier to understand at a glance. In rare cases where a single checkbox doesn’t clearly communicate the opposing states, you can use a pair of radio buttons, each with a label that specifies the state it controls.
+
+**Use consistent spacing when you display radio buttons horizontally.** Measure the space needed to accommodate the longest button label, and use that measurement consistently.
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/toggles#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/toggles#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/toggles#Developer-documentation)
+
+[`Toggle`](https://developer.apple.com/documentation/SwiftUI/Toggle) — SwiftUI
+
+[`UISwitch`](https://developer.apple.com/documentation/UIKit/UISwitch) — UIKit
+
+[`NSButton.ButtonType.toggle`](https://developer.apple.com/documentation/AppKit/NSButton/ButtonType/toggle) — AppKit
+
+[`NSSwitch`](https://developer.apple.com/documentation/AppKit/NSSwitch) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/toggles#Change-log)
+
+Date| Changes
+---|---
+March 29, 2024| Enhanced guidance for using switches in macOS apps, clarified when a checkbox has a title, and added artwork for radio buttons.
+September 12, 2023| Updated artwork.
+
diff --git a/web-app/public/skills/hig-components-controls/references/token-fields.md b/web-app/public/skills/hig-components-controls/references/token-fields.md
new file mode 100644
index 00000000..a319c9a0
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/token-fields.md
@@ -0,0 +1,48 @@
+---
+title: "Token fields | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/token-fields
+
+# Token fields
+
+A token field is a type of text field that can convert text into _tokens_ that are easy to select and manipulate.
+
+
+
+For example, Mail uses token fields for the address fields in the compose window. As people enter recipients, Mail converts the text that represents each recipient’s name into a token. People can select these recipient tokens and drag to reorder them or move them into a different field.
+
+You can configure a token field to present people with a list of suggestions as they enter text into the field. For example, Mail suggests recipients as people type in an address field. When people select a suggested recipient, Mail inserts the recipient into the field as a token.
+
+
+
+An individual token can also include a contextual menu that offers information about the token or editing options. For example, a recipient token in Mail includes a contextual menu with commands for editing the recipient name, marking the recipient as a VIP, and viewing the recipient’s contact card, among others.
+
+
+
+Tokens can also represent search terms in some situations; for guidance, see [Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/token-fields#Best-practices)
+
+**Add value with a context menu.** People often benefit from a [context menu](https://developer.apple.com/design/human-interface-guidelines/context-menus) with additional options or information about a token.
+
+**Consider providing additional ways to convert text into tokens.** By default, text people enter turns into a token whenever they type a comma. You can specify additional shortcuts, such as pressing Return, that also invoke this action.
+
+**Consider customizing the delay the system uses before showing suggested tokens.** By default, suggestions appear immediately. However, suggestions that appear too quickly may distract people while they’re typing. If your app suggests tokens, consider adjusting the delay to a comfortable level.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/token-fields#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, and watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/token-fields#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/token-fields#Related)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+[Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields)
+
+[Context menus](https://developer.apple.com/design/human-interface-guidelines/context-menus)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/token-fields#Developer-documentation)
+
+[`NSTokenField`](https://developer.apple.com/documentation/AppKit/NSTokenField) — AppKit
+
diff --git a/web-app/public/skills/hig-components-controls/references/virtual-keyboards.md b/web-app/public/skills/hig-components-controls/references/virtual-keyboards.md
new file mode 100644
index 00000000..330196d6
--- /dev/null
+++ b/web-app/public/skills/hig-components-controls/references/virtual-keyboards.md
@@ -0,0 +1,156 @@
+---
+title: "Virtual keyboards | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards
+
+# Virtual keyboards
+
+On devices without physical keyboards, the system offers various types of virtual keyboards people can use to enter data.
+
+
+
+A virtual keyboard can provide a specific set of keys that are optimized for the current task; for example, a keyboard that supports entering email addresses can include the “@” character and a period or even “.com”. A virtual keyboard doesn’t support keyboard shortcuts.
+
+When it makes sense in your app, you can replace the system-provided keyboard with a custom view that supports app-specific data entry. In iOS, iPadOS, and tvOS, you can also create an app extension that offers a custom keyboard people can install and use in place of the standard keyboard.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Best-practices)
+
+**Choose a keyboard that matches the type of content people are editing.** For example, you can help people enter numeric data by providing the numbers and punctuation keyboard. When you specify a semantic meaning for a text input area, the system can automatically provide a keyboard that matches the type of input you expect, potentially using this information to refine the keyboard corrections it offers. For developer guidance, see [`keyboardType(_:)`](https://developer.apple.com/documentation/SwiftUI/View/keyboardType\(_:\)) (SwiftUI), [`textContentType(_:)`](https://developer.apple.com/documentation/SwiftUI/View/textContentType\(_:\))(SwiftUI), [`UIKeyboardType`](https://developer.apple.com/documentation/UIKit/UIKeyboardType) (UIKit), and [`UITextContentType`](https://developer.apple.com/documentation/UIKit/UITextContentType) (UIKit).
+
+ * ASCII capable
+ * ASCII capable number pad
+ * Decimal pad
+ * Default
+ * Email address
+ * Name phone pad
+ * Number pad
+ * Numbers and punctuation
+ * Phone pad
+ * Twitter
+ * URL
+ * Web search
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+**Consider customizing the Return key type if it helps clarify the text-entry experience.** The Return key type is based on the keyboard type you choose, but you can change this if it makes sense in your app. For example, if your app initiates a search, you can use a search Return key type rather than the standard one so the experience is consistent with other places people initiate search. For developer guidance, see [`submitLabel(_:)`](https://developer.apple.com/documentation/SwiftUI/View/submitLabel\(_:\)) (SwiftUI) and [`UIReturnKeyType`](https://developer.apple.com/documentation/UIKit/UIReturnKeyType) (UIKit).
+
+## [Custom input views](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Custom-input-views)
+
+In some cases, you can create an _input view_ if you want to provide custom functionality that enhances data-entry tasks in your app. For example, Numbers provides a custom input view for entering numeric values while editing a spreadsheet. A custom input view replaces the system-provided keyboard while people are in your app. For developer guidance, see [`ToolbarItemPlacement`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement) (SwiftUI) and [`inputViewController`](https://developer.apple.com/documentation/UIKit/UIResponder/inputViewController) (UIKit).
+
+**Make sure your custom input view makes sense in the context of your app.** In addition to making data entry simple and intuitive, you want people to understand the benefits of using your custom input view. Otherwise, they may wonder why they can’t regain the system keyboard while in your app.
+
+**Play the standard keyboard sound while people type.** The keyboard sound provides familiar feedback when people tap a key on the system keyboard, so they’re likely to expect the same sound when they tap keys in your custom input view. People can turn keyboard sounds off for all keyboard interactions in Settings > Sounds. For developer guidance, see [`playInputClick()`](https://developer.apple.com/documentation/UIKit/UIDevice/playInputClick\(\)) (UIKit).
+
+## [Custom keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Custom-keyboards)
+
+In iOS, iPadOS, and tvOS, you can provide a custom keyboard that replaces the system keyboard by creating an app extension. An _app extension_ is code you provide that people can install and use to extend the functionality of a specific area of the system; to learn more, see [App extensions](https://developer.apple.com/app-extensions/).
+
+After people choose your custom keyboard in Settings, they can use it for text entry within any app, except when editing secure text fields and phone number fields. People can choose multiple custom keyboards and switch between them at any time. For developer guidance, see [Creating a custom keyboard](https://developer.apple.com/documentation/UIKit/creating-a-custom-keyboard).
+
+Custom keyboards make sense when you want to expose unique keyboard functionality systemwide, such as a novel way of inputting text or the ability to type in a language the system doesn’t support. If you want to provide a custom keyboard for people to use only while they’re in your app, consider creating a custom input view instead.
+
+**Provide an obvious and easy way to switch between keyboards.** People know that the Globe key on the standard keyboard — which replaces the dedicated Emoji key when multiple keyboards are available — quickly switches to other keyboards, and they expect a similarly intuitive experience in your keyboard.
+
+**Avoid duplicating system-provided keyboard features.** On some devices, the Emoji/Globe key and Dictation key automatically appear beneath the keyboard, even when people are using custom keyboards. Your app can’t affect these keys, and it’s likely to be confusing if you repeat them in your keyboard.
+
+**Consider providing a keyboard tutorial in your app.** People are used to the standard keyboard, and learning how to use a new keyboard can take time. You can help make the process easier by providing usage instructions in your app — for example, you might tell people how to choose your keyboard, activate it during text entry, use it, and switch back to the standard keyboard. Avoid displaying help content within the keyboard itself.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Platform-considerations)
+
+ _Not supported in macOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#iOS-iPadOS)
+
+**Use the keyboard layout guide to make the keyboard feel like an integrated part of your interface.** Using the layout guide also helps you keep important parts of your interface visible while the virtual keyboard is onscreen. For developer guidance, see [Adjusting your layout with keyboard layout guide](https://developer.apple.com/documentation/UIKit/adjusting-your-layout-with-keyboard-layout-guide).
+
+
+
+The keyboard layout guide helps ensure that app UI and the keyboard work well together.
+
+
+
+Without the layout guide, the keyboard could make entering text more difficult.
+
+
+
+Without the layout guide, the keyboard could make tapping a button more difficult.
+
+**Place custom controls above the keyboard thoughtfully.** Some apps position an input accessory view containing custom controls above the keyboard to offer app-specific functionality related to the data people are working with. For example, Numbers displays controls that help people apply standard or custom calculations to spreadsheet data. If your app offers custom controls that augment the keyboard, make sure they’re relevant to the current task. If other views in your app use Liquid Glass, or if your view looks out of place above the keyboard, apply Liquid Glass to the view that contains your controls to maintain consistency. If you use a standard toolbar to contain your controls, it automatically adopts Liquid Glass. Use the keyboard layout guide and standard padding to ensure the system positions your controls as expected within the view. For developer guidance, see [`ToolbarItemPlacement`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement) (SwiftUI), [`inputAccessoryView`](https://developer.apple.com/documentation/UIKit/UIResponder/inputAccessoryView) (UIKit), and [`UIKeyboardLayoutGuide`](https://developer.apple.com/documentation/UIKit/UIKeyboardLayoutGuide) (UIKit).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#tvOS)
+
+tvOS displays a linear virtual keyboard when people select a text field using the Siri Remote.
+
+Note
+
+A grid keyboard screen appears when people use devices other than the Siri Remote, and the layout of content automatically adapts to the keyboard.
+
+When people activate a digit entry view, tvOS displays a digit-specific keyboard. For guidance, see [Digit entry views](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#visionOS)
+
+In visionOS, the system-provided virtual keyboard supports both direct and indirect gestures and appears in a separate window that people can move where they want. You don’t need to account for the location of the keyboard in your layouts.
+
+Video with custom controls.
+
+Content description: A recording showing a person typing on a virtual keyboard in visionOS.
+
+Play
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#watchOS)
+
+On Apple Watch, a text field can show a keyboard if the device screen is large enough. Otherwise, the system lets people use dictation or Scribble to enter information. You can’t change the keyboard type in watchOS, but you can set the content type of the text field. The system uses this information to make text entry easier, such as by offering suggestions. For developer guidance, see [`textContentType(_:)`](https://developer.apple.com/documentation/SwiftUI/View/textContentType\(_:\)) (SwiftUI).
+
+People can also use a nearby paired iPhone to enter text on Apple Watch.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Related)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+[Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Developer-documentation)
+
+[`keyboardType(_:)`](https://developer.apple.com/documentation/SwiftUI/View/keyboardType\(_:\)) — SwiftUI
+
+[`textContentType(_:)`](https://developer.apple.com/documentation/SwiftUI/View/textContentType\(_:\)) — SwiftUI
+
+[`UIKeyboardType`](https://developer.apple.com/documentation/UIKit/UIKeyboardType) — UIKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance for displaying custom controls above the keyboard, and updated to reflect virtual keyboard availability in watchOS.
+February 2, 2024| Clarified the virtual keyboard’s support for direct and indirect gestures in visionOS.
+December 5, 2023| Added artwork for visionOS.
+June 21, 2023| Changed page title from Onscreen keyboards and updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-dialogs/SKILL.md b/web-app/public/skills/hig-components-dialogs/SKILL.md
new file mode 100644
index 00000000..1242ca6c
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/SKILL.md
@@ -0,0 +1,81 @@
+---
+name: hig-components-dialogs
+version: 1.0.0
+description: ">-"
+ Apple HIG guidance for presentation components including alerts, action sheets,
+ popovers, sheets, and digit entry views. Use this skill when the user says
+ "should I use an alert or a sheet," "how do I show a confirmation dialog,"
+ "when should I use a popover," "my modals are annoying users," or asks about
+ alert design, action sheet, popover, sheet, modal, dialog, digit entry,
+ confirmation dialog, warning dialog, modal presentation, non-modal content,
+ destructive action confirmation, or overlay UI patterns. Cross-references:
+ hig-components-menus, hig-components-controls, hig-components-search,
+ hig-patterns.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Presentation Components
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Alerts: sparingly, for critical situations.** Errors needing attention, destructive action confirmations, or information requiring acknowledgment. They interrupt flow and demand a response.
+
+2. **Sheets: focused tasks that maintain context.** Slides in from the edge (or attaches to a window on macOS). Use for creating items, editing settings, multi-step forms.
+
+3. **Popovers: non-modal on iPad and Mac.** Appear next to the trigger element, dismissed by tapping outside. For additional information, options, or controls without taking over the screen.
+
+4. **Action sheets: choosing among actions.** Present when picking from multiple actions, especially if one is destructive. iPhone: slide up from bottom. iPad: appear as popovers.
+
+5. **Minimize interruptions.** Before reaching for a modal, consider inline presentation or making the action undoable instead.
+
+6. **Concise, actionable alert text.** Short descriptive title. Brief message body if needed. Button labels should be specific verbs ("Delete", "Save"), not "OK".
+
+7. **Mark destructive actions clearly.** Destructive button style (red text). Place destructive buttons where users are less likely to tap reflexively.
+
+8. **Provide a cancel option** for alerts and action sheets with multiple actions. On action sheets, cancel appears at the bottom, separated.
+
+9. **Digit entry: focused and accessible.** Appropriately sized input fields, automatic advancement between digits, support for paste and autofill.
+
+10. **Adapt presentation to platform.** The same interaction may use different components on iPhone, iPad, Mac, and visionOS.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [alerts.md](references/alerts.md) | Alerts | Button ordering, title/message text, confirmation, destructive actions |
+| [action-sheets.md](references/action-sheets.md) | Action sheets | Multiple actions, cancel option, destructive handling |
+| [popovers.md](references/popovers.md) | Popovers | Non-modal, dismiss on tap outside, iPad/Mac |
+| [sheets.md](references/sheets.md) | Sheets | Modal task, context preservation |
+| [digit-entry-views.md](references/digit-entry-views.md) | Digit entry | PIN input, autofill, auto-advance |
+
+## Output Format
+
+1. **Recommended presentation type with rationale** and why alternatives are less suitable.
+2. **Content guidelines** -- title, message, button labels per Apple's tone and brevity rules.
+3. **Dismiss behavior** -- how the user dismisses and what happens (save, discard, cancel).
+4. **Alternatives** -- when the scenario might not need a modal at all (inline feedback, undo, progressive disclosure).
+
+## Questions to Ask
+
+1. What information or action does the presentation need?
+2. Blocking or non-blocking?
+3. Which platforms?
+4. How often does this appear?
+
+## Related Skills
+
+- **hig-components-menus** -- Buttons and toolbar items triggering presentations
+- **hig-components-controls** -- Input controls within sheets and popovers
+- **hig-components-search** -- Search and navigation within presented views
+- **hig-patterns** -- Modality, interruptions, user flow management
+- **hig-foundations** -- Color, typography, layout for presentation components
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-dialogs/references/action-sheets.md b/web-app/public/skills/hig-components-dialogs/references/action-sheets.md
new file mode 100644
index 00000000..96a55592
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/references/action-sheets.md
@@ -0,0 +1,74 @@
+---
+title: "Action sheets | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/action-sheets
+
+# Action sheets
+
+An action sheet is a modal view that presents choices related to an action people initiate.
+
+
+
+Developer note
+
+When you use SwiftUI, you can offer action sheet functionality in all platforms by specifying a [presentation modifier](https://developer.apple.com/documentation/swiftui/view-presentation) for a confirmation dialog. If you use UIKit, you use the [`UIAlertController.Style.actionSheet`](https://developer.apple.com/documentation/UIKit/UIAlertController/Style/actionSheet) to display an action sheet in iOS, iPadOS, and tvOS.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/action-sheets#Best-practices)
+
+**Use an action sheet — not an alert — to offer choices related to an intentional action.** For example, when people cancel the message they’re editing in Mail on iPhone, an action sheet provides two choices: delete the draft, or save the draft. Although an alert can also help people confirm or cancel an action that has destructive consequences, it doesn’t provide additional choices related to the action. More importantly, an alert is usually unexpected, generally telling people about a problem or a change in the current situation that might require them to act. For guidance, see [Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts).
+
+
+
+
+
+**Use action sheets sparingly.** Action sheets give people important information and choices, but they interrupt the current task to do so. To encourage people to pay attention to action sheets, avoid using them more than necessary.
+
+**Aim to keep titles short enough to display on a single line.** A long title is difficult to read quickly and might get truncated or require people to scroll.
+
+**Provide a message only if necessary.** In general, the title — combined with the context of the current action — provides enough information to help people understand their choices.
+
+**If necessary, provide a Cancel button that lets people reject an action that might destroy data.** Place the Cancel button at the bottom of the action sheet (or in the upper-left corner of the sheet in watchOS). A SwiftUI confirmation dialog includes a Cancel button by default.
+
+**Make destructive choices visually prominent.** Use the destructive style for buttons that perform destructive actions, and place these buttons at the top of the action sheet where they tend to be most noticeable. For developer guidance, see [`destructive`](https://developer.apple.com/documentation/SwiftUI/ButtonRole/destructive) (SwiftUI) or [`UIAlertAction.Style.destructive`](https://developer.apple.com/documentation/UIKit/UIAlertAction/Style-swift.enum/destructive) (UIKit).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/action-sheets#Platform-considerations)
+
+ _No additional considerations for macOS or tvOS. Not supported in visionOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/action-sheets#iOS-iPadOS)
+
+**Use an action sheet — not a menu — to provide choices related to an action.** People are accustomed to having an action sheet appear when they perform an action that might require clarifying choices. In contrast, people expect a menu to appear when they choose to reveal it.
+
+**Avoid letting an action sheet scroll.** The more buttons an action sheet has, the more time and effort it takes for people to make a choice. Also, scrolling an action sheet can be hard to do without inadvertently tapping a button.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/action-sheets#watchOS)
+
+The system-defined style for action sheets includes a title, an optional message, a Cancel button, and one or more additional buttons. The appearance of this interface is different depending on the device.
+
+
+
+Each button has an associated style that conveys information about the button’s effect. There are three system-defined button styles:
+
+Style| Meaning
+---|---
+Default| The button has no special meaning.
+Destructive| The button destroys user data or performs a destructive action in the app.
+Cancel| The button dismisses the view without taking any action.
+
+**Avoid displaying more than four buttons in an action sheet, including the Cancel button.** When there are fewer buttons onscreen, it’s easier for people to view all their options at once. Because the Cancel button is required, aim to provide no more than three additional choices.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/action-sheets#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/action-sheets#Related)
+
+[Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
+
+[Sheets](https://developer.apple.com/design/human-interface-guidelines/sheets)
+
+[Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/action-sheets#Developer-documentation)
+
+[`confirmationDialog(_:isPresented:titleVisibility:actions:)`](https://developer.apple.com/documentation/SwiftUI/View/confirmationDialog\(_:isPresented:titleVisibility:actions:\)-46zbb) — SwiftUI
+
+[`UIAlertController.Style.actionSheet`](https://developer.apple.com/documentation/UIKit/UIAlertController/Style/actionSheet) — UIKit
+
diff --git a/web-app/public/skills/hig-components-dialogs/references/alerts.md b/web-app/public/skills/hig-components-dialogs/references/alerts.md
new file mode 100644
index 00000000..d91ebb5d
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/references/alerts.md
@@ -0,0 +1,158 @@
+---
+title: "Alerts | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/alerts
+
+# Alerts
+
+An alert gives people critical information they need right away.
+
+
+
+For example, an alert can tell people about a problem, warn them when their action might destroy data, and give them an opportunity to confirm a purchase or another important action they initiated.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/alerts#Best-practices)
+
+**Use alerts sparingly.** Alerts give people important information, but they interrupt the current task to do so. Encourage people to pay attention to your alerts by making certain that each one offers only essential information and useful actions.
+
+**Avoid using an alert merely to provide information.** People don’t appreciate an interruption from an alert that’s informative, but not actionable. If you need to provide only information, prefer finding an alternative way to communicate it within the relevant context. For example, when a server connection is unavailable, Mail displays an indicator that people can choose to learn more.
+
+**Avoid displaying alerts for common, undoable actions, even when they’re destructive.** For example, you don’t need to alert people about data loss every time they delete an email or file because they do so with the intention of discarding data, and they can undo the action. In comparison, when people take an uncommon destructive action that they can’t undo, it’s important to display an alert in case they initiated the action accidentally.
+
+**Avoid showing an alert when your app starts.** If you need to inform people about new or important information the moment they open your app, design a way to make the information easily discoverable. If your app detects a problem at startup, like no network connection, consider alternative ways to let people know. For example, you could show cached or placeholder data and a nonintrusive label that describes the problem.
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/alerts#Anatomy)
+
+An alert is a modal view that can look different in different platforms and devices.
+
+ * iOS
+ * macOS
+ * tvOS
+ * visionOS
+ * watchOS
+
+
+
+
+
+
+
+
+
+
+
+
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/alerts#Content)
+
+In all platforms, alerts display a title, optional informative text, and up to three buttons. On some platforms, alerts can include additional elements.
+
+ * In iOS, iPadOS, macOS, and visionOS, an alert can include a text field.
+
+ * Alerts in macOS and visionOS can include an icon and an accessory view.
+
+ * macOS alerts can add a suppression [checkbox](https://developer.apple.com/design/human-interface-guidelines/toggles#Checkboxes) and a [Help button](https://developer.apple.com/design/human-interface-guidelines/buttons#Help-buttons).
+
+
+
+
+**In all alert copy, be direct, and use a neutral, approachable tone.** Alerts often describe problems and serious situations, so avoid being oblique or accusatory, or masking the severity of the issue.
+
+**Write a title that clearly and succinctly describes the situation.** You need to help people quickly understand the situation, so be complete and specific, without being verbose. As much as possible, describe what happened, the context in which it happened, and why. Avoid writing a title that doesn’t convey useful information — like “Error” or “Error 329347 occurred” — but also avoid overly long titles that wrap to more than two lines. If the title is a complete sentence, use [sentence-style capitalization](https://help.apple.com/applestyleguide/#/apsgb744e4a3?sub=apdca93e113f1d64) and appropriate ending punctuation. If the title is a sentence fragment, use title-style capitalization, and don’t add ending punctuation.
+
+**Include informative text only if it adds value.** If you need to add an informative message, keep it as short as possible, using complete sentences, sentence-style capitalization, and appropriate punctuation.
+
+**Avoid explaining alert buttons.** If your alert text and button titles are clear, you don’t need to explain what the buttons do. In rare cases where you need to provide guidance on choosing a button, use a term like _choose_ to account for people’s current device and interaction method, and refer to a button using its exact title without quotes. For guidance, see [Buttons](https://developer.apple.com/design/human-interface-guidelines/alerts#Buttons).
+
+**If supported, include a text field only if you need people’s input to resolve the situation.** For example, you might need to present a secure text field to receive a password.
+
+## [Buttons](https://developer.apple.com/design/human-interface-guidelines/alerts#Buttons)
+
+**Create succinct, logical button titles.** Aim for a one- or two-word title that describes the result of selecting the button. Prefer verbs and verb phrases that relate directly to the alert text — for example, “View All,” “Reply,” or “Ignore.” In informational alerts only, you can use “OK” for acceptance, avoiding “Yes” and “No.” Always use “Cancel” to title a button that cancels the alert’s action. As with all button titles, use [title-style capitalization](https://help.apple.com/applestyleguide/#/apsgb744e4a3?sub=apdca93e113f1d64) and no ending punctuation.
+
+**Avoid using OK as the default button title unless the alert is purely informational.** The meaning of “OK” can be unclear even in alerts that ask people to confirm that they want to do something. For example, does “OK” mean “OK, I want to complete the action” or “OK, I now understand the negative results my action would have caused”? A specific button title like “Erase,” “Convert,” “Clear,” or “Delete” helps people understand the action they’re taking.
+
+**Place buttons where people expect.** In general, place the button people are most likely to choose on the trailing side in a row of buttons or at the top in a stack of buttons. Always place the default button on the trailing side of a row or at the top of a stack. Cancel buttons are typically on the leading side of a row or at the bottom of a stack.
+
+**Use the destructive style to identify a button that performs a destructive action people didn’t deliberately choose.** For example, when people deliberately choose a destructive action — such as Empty Trash — the resulting alert doesn’t apply the destructive style to the Empty Trash button because the button performs the person’s original intent. In this scenario, the convenience of pressing Return to confirm the deliberately chosen Empty Trash action outweighs the benefit of reaffirming that the button is destructive. In contrast, people appreciate an alert that draws their attention to a button that can perform a destructive action they didn’t originally intend.
+
+**If there’s a destructive action, include a Cancel button to give people a clear, safe way to avoid the action.** Always use the title “Cancel” for a button that cancels an alert’s action. Note that you don’t want to make a Cancel button the default button. If you want to encourage people to read an alert and not just automatically press Return to dismiss it, avoid making any button the default button. Similarly, if you must display an alert with a single button that’s also the default, use a Done button, not a Cancel button.
+
+**Provide alternative ways to cancel an alert when it makes sense.** In addition to choosing a Cancel button, people appreciate using keyboard shortcuts or other quick ways to cancel an onscreen alert. For example:
+
+Action| Platform
+---|---
+Exit to the Home Screen| iOS, iPadOS
+Pressing Escape (Esc) or Command-Period (.) on an attached keyboard| iOS, iPadOS, macOS, visionOS
+Pressing Menu on the remote| tvOS
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/alerts#Platform-considerations)
+
+ _No additional considerations for tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/alerts#iOS-iPadOS)
+
+**Use an action sheet — not an alert — to offer choices related to an intentional action.** For example, when people cancel the Mail message they’re editing, an action sheet provides three choices: delete the edits (or the entire draft), save the draft, or return to editing. Although an alert can also help people confirm or cancel an action that has destructive consequences, it doesn’t provide additional choices related to the action. For guidance, see [Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets).
+
+**When possible, avoid displaying an alert that scrolls.** Although an alert might scroll if the text size is large enough, be sure to minimize the potential for scrolling by keeping alert titles short and including a brief message only when necessary.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/alerts#macOS)
+
+macOS automatically displays your app icon in an alert, but you can supply an alternative icon or symbol. In addition, macOS lets you:
+
+ * Configure repeating alerts to let people suppress subsequent occurrences of the same alert.
+
+ * Append a custom view if it’s necessary to provide additional information (for developer guidance, see [`accessoryView`](https://developer.apple.com/documentation/AppKit/NSAlert/accessoryView)).
+
+ * Include a Help button that opens your help documentation (see [Help buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Help-buttons)).
+
+
+
+
+**Use a caution symbol sparingly.** Using a caution symbol like `exclamationmark.triangle` too frequently in your alerts diminishes its significance. Use the symbol only when extra attention is really needed, as when confirming an action that might result in unexpected loss of data. Don’t use the symbol for tasks whose only purpose is to overwrite or remove data, such as a save or empty trash.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/alerts#visionOS)
+
+When your app is running in the Shared Space, visionOS displays an alert in front of the app’s window, slightly forward along the z-axis.
+
+Video with custom controls.
+
+Content description: A video of an alert in the Freeform app running in the Shared Space in visionOS. When the video plays, someone chooses to permanently delete a recently deleted Freeform board. An alert then appears in front of the Freeform window to ask for confirmation.
+
+Play
+
+If someone moves a window without dismissing its alert, the alert remains anchored to the window. If your app is running in a Full Space, the system displays the alert centered in the wearer’s [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view).
+
+Video with custom controls.
+
+Content description: A video of an alert in the Freeform app running in the Shared Space in visionOS. When the video plays, someone chooses to permanently delete a recently deleted Freeform board. An alert then appears in front of the Freeform window to ask for confirmation. The alert is not dismissed and remains anchored to the Freeform window as it’s moved around the Shared Space.
+
+Play
+
+If you need to display an accessory view in a visionOS alert, create a view that has a maximum height of 154 pt and a 16-pt corner radius.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/alerts#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/alerts#Related)
+
+[Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
+
+[Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets)
+
+[Sheets](https://developer.apple.com/design/human-interface-guidelines/sheets)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/alerts#Developer-documentation)
+
+[`alert(_:isPresented:actions:)`](https://developer.apple.com/documentation/SwiftUI/View/alert\(_:isPresented:actions:\)-1bkka) — SwiftUI
+
+[`UIAlertController`](https://developer.apple.com/documentation/UIKit/UIAlertController) — UIKit
+
+[`NSAlert`](https://developer.apple.com/documentation/AppKit/NSAlert) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/alerts#Change-log)
+
+Date| Changes
+---|---
+February 2, 2024| Enhanced guidance for using default and Cancel buttons.
+September 12, 2023| Added anatomy artwork for visionOS.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-dialogs/references/digit-entry-views.md b/web-app/public/skills/hig-components-dialogs/references/digit-entry-views.md
new file mode 100644
index 00000000..70f577d9
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/references/digit-entry-views.md
@@ -0,0 +1,32 @@
+---
+title: "Digit entry views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/digit-entry-views
+
+# Digit entry views
+
+A digit entry view fills the entire screen and prompts people to enter a series of digits, like a PIN, using a digit-specific keyboard.
+
+
+
+You can add an optional title and prompt above the line of digits.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views#Best-practices)
+
+**Use secure digit fields.** Secure digit fields display asterisks instead of the entered digit onscreen. Always use a secure digit field when your app asks for sensitive data.
+
+**Clearly state the purpose of the digit entry view.** Use a title and prompt that explains why someone needs to enter digits.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views#Related)
+
+[Virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views#Developer-documentation)
+
+[`TVDigitEntryViewController`](https://developer.apple.com/documentation/TVUIKit/TVDigitEntryViewController) — TVUIKit
+
diff --git a/web-app/public/skills/hig-components-dialogs/references/popovers.md b/web-app/public/skills/hig-components-dialogs/references/popovers.md
new file mode 100644
index 00000000..b2d91e94
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/references/popovers.md
@@ -0,0 +1,81 @@
+---
+title: "Popovers | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/popovers
+
+# Popovers
+
+A popover is a transient view that appears above other content when people click or tap a control or interactive area.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/popovers#Best-practices)
+
+**Use a popover to expose a small amount of information or functionality.** Because a popover disappears after people interact with it, limit the amount of functionality in the popover to a few related tasks. For example, a calendar event popover makes it easy for people to change the date or time of an event, or to move it to another calendar. The popover disappears after the change, letting people continue reviewing the events on their calendar.
+
+**Consider using popovers when you want more room for content.** Views like sidebars and panels take up a lot of space. If you need content only temporarily, displaying it in a popover can help streamline your interface.
+
+**Position popovers appropriately.** Make sure a popover’s arrow points as directly as possible to the element that revealed it. Ideally, a popover doesn’t cover the element that revealed it or any essential content people may need to see while using it.
+
+**Use a Close button for confirmation and guidance only.** A Close button, including Cancel or Done, is worth including if it provides clarity, like exiting with or without saving changes. Otherwise, a popover generally closes when people click or tap outside its bounds or select an item in the popover. If multiple selections are possible, make sure the popover remains open until people explicitly dismiss it or they click or tap outside its bounds.
+
+**Always save work when automatically closing a nonmodal popover.** People can unintentionally dismiss a nonmodal popover by clicking or tapping outside its bounds. Discard people’s work only when they click or tap an explicit Cancel button.
+
+**Show one popover at a time.** Displaying multiple popovers clutters the interface and causes confusion. Never show a cascade or hierarchy of popovers, in which one emerges from another. If you need to show a new popover, close the open one first.
+
+**Don’t show another view over a popover.** Make sure nothing displays on top of a popover, except for an alert.
+
+**When possible, let people close one popover and open another with a single click or tap.** Avoiding extra gestures is especially desirable when several different bar buttons each open a popover.
+
+**Avoid making a popover too big.** Make a popover only big enough to display its contents and point to the place it came from. If necessary, the system can adjust the size of a popover to ensure it fits well in the interface.
+
+**Provide a smooth transition when changing the size of a popover.** Some popovers provide both condensed and expanded views of the same information. If you adjust the size of a popover, animate the change to avoid giving the impression that a new popover replaced the old one.
+
+**Avoid using the word _popover_ in help documentation.** Instead, refer to a specific task or selection. For example, instead of “Select the Show button at the bottom of the popover,” you might write “Select the Show button.”
+
+**Avoid using a popover to show a warning.** People can miss a popover or accidentally close it. If you need to warn people, use an [alert](https://developer.apple.com/design/human-interface-guidelines/alerts) instead.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/popovers#Platform-considerations)
+
+ _No additional considerations for visionOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/popovers#iOS-iPadOS)
+
+**Avoid displaying popovers in compact views.** Make your app or game dynamically adjust its layout based on the size class of the content area. Reserve popovers for wide views; for compact views, use all available screen space by presenting information in a full-screen modal view like a sheet instead. For related guidance, see [Modality](https://developer.apple.com/design/human-interface-guidelines/modality).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/popovers#macOS)
+
+You can make a popover detachable in macOS, which becomes a separate panel when people drag it. The panel remains visible onscreen while people interact with other content.
+
+ * Attached popover
+ * Detached popover
+
+
+
+
+
+
+
+**Consider letting people detach a popover.** People might appreciate being able to convert a popover into a panel if they want to view other information while the popover remains visible.
+
+**Make minimal appearance changes to a detached popover.** A panel that looks similar to the original popover helps people maintain context.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/popovers#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/popovers#Related)
+
+[Sheets](https://developer.apple.com/design/human-interface-guidelines/sheets)
+
+[Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets)
+
+[Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)
+
+[Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/popovers#Developer-documentation)
+
+[`popover(isPresented:attachmentAnchor:arrowEdge:content:)`](https://developer.apple.com/documentation/SwiftUI/View/popover\(isPresented:attachmentAnchor:arrowEdge:content:\)) — SwiftUI
+
+[`UIPopoverPresentationController`](https://developer.apple.com/documentation/UIKit/UIPopoverPresentationController) — UIKit
+
+[`NSPopover`](https://developer.apple.com/documentation/AppKit/NSPopover) — AppKit
+
diff --git a/web-app/public/skills/hig-components-dialogs/references/sheets.md b/web-app/public/skills/hig-components-dialogs/references/sheets.md
new file mode 100644
index 00000000..5a3c8a17
--- /dev/null
+++ b/web-app/public/skills/hig-components-dialogs/references/sheets.md
@@ -0,0 +1,157 @@
+---
+title: "Sheets | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/sheets
+
+# Sheets
+
+A sheet helps people perform a scoped task that’s closely related to their current context.
+
+
+
+By default, a sheet is _modal_ , presenting a targeted experience that prevents people from interacting with the parent view until they dismiss the sheet (for more on modal presentation, see [Modality](https://developer.apple.com/design/human-interface-guidelines/modality)). A modal sheet is useful for requesting specific information from people or presenting a simple task that they can complete before returning to the parent view. For example, a sheet might let people supply information needed to complete an action, such as attaching a file, choosing the location for a move or save, or specifying the format for a selection.
+
+In macOS, visionOS, and watchOS, a sheet is always modal, but in iOS and iPadOS, a sheet can also be nonmodal. When a nonmodal sheet is onscreen, people use its functionality to directly affect the current task in the parent view without dismissing the sheet. For example, Notes on iPhone and iPad uses a nonmodal sheet to help people apply different formatting to various text selections as they edit a note.
+
+
+
+The Notes format sheet lets people apply formatting to selected text in the editing view.
+
+
+
+Because the sheet is nonmodal, people can make additional text selections without dismissing the sheet.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/sheets#Best-practices)
+
+**Use a sheet to present simple content or tasks.** A sheet allows some of the parent view to remain visible, helping people retain their original context as they interact with the sheet.
+
+**For complex or prolonged user flows, consider alternatives to sheets.** For example, iOS and iPadOS offer a full-screen style of modal view that can work well to display content like videos, photos, or camera views or to help people perform multistep tasks like document or photo editing. (For developer guidance, see [`UIModalPresentationStyle.fullScreen`](https://developer.apple.com/documentation/UIKit/UIModalPresentationStyle/fullScreen).) In a macOS experience, you might want to open a new window or let people enter full-screen mode instead of using a sheet. For example, a self-contained task like editing a document tends to work well in a separate window, whereas [going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen) can help people view media. In visionOS, you can give people a way to transition your app to a Full Space where they can dive into content or a task; for guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+**Display only one sheet at a time from the main interface.** When people close a sheet, they expect to return to the parent view or window. If closing a sheet takes people back to another sheet, they can lose track of where they are in your app. If something people do within a sheet results in another sheet appearing, close the first sheet before displaying the new one. If necessary, you can display the first sheet again after people dismiss the second one.
+
+**Use a nonmodal view when you want to present supplementary items that affect the main task in the parent view.** To give people access to information and actions they need while continuing to interact with the main window, consider using a [split view](https://developer.apple.com/design/human-interface-guidelines/split-views) in visionOS or a [panel](https://developer.apple.com/design/human-interface-guidelines/panels) in macOS; in iOS and iPadOS, you can use a nonmodal sheet for this workflow. For guidance, see [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/sheets#iOS-iPadOS).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/sheets#Platform-considerations)
+
+ _No additional considerations for tvOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/sheets#iOS-iPadOS)
+
+A resizable sheet expands when people scroll its contents or drag the _grabber_ , which is a small horizontal indicator that can appear at the top edge of a sheet. Sheets resize according to their _detents_ , which are particular heights at which a sheet naturally rests. Designed for iPhone, detents specify particular heights at which a sheet naturally rests. The system defines two detents: _large_ is the height of a fully expanded sheet and _medium_ is about half of the fully expanded height.
+
+
+
+Large detent
+
+
+
+Medium detent
+
+Sheets automatically support the large detent. Adding the medium detent allows the sheet to rest at both heights, whereas specifying only medium prevents the sheet from expanding to full height. For developer guidance, see [`detents`](https://developer.apple.com/documentation/UIKit/UISheetPresentationController/detents).
+
+**In an iPhone app, consider supporting the medium detent to allow progressive disclosure of the sheet’s content.** For example, a share sheet displays the most relevant items within the medium detent, where they’re visible without resizing. To view more items, people can scroll or expand the sheet. In contrast, you might not want to support the medium detent if a sheet’s content is more useful when it displays at full height. For example, the compose sheets in Messages and Mail display only at full height to give people enough room to create content.
+
+**Include a grabber in a resizable sheet.** A grabber shows people that they can drag the sheet to resize it; they can also tap it to cycle through the detents. In addition to providing a visual indicator of resizability, a grabber also works with VoiceOver so people can resize the sheet without seeing the screen. For developer guidance, see [`prefersGrabberVisible`](https://developer.apple.com/documentation/UIKit/UISheetPresentationController/prefersGrabberVisible).
+
+**Support swiping to dismiss a sheet.** People expect to swipe vertically to dismiss a sheet instead of tapping a dismiss button. If people have unsaved changes in the sheet when they begin swiping to dismiss it, use an action sheet to let them confirm their action.
+
+**Position Done and Cancel buttons as people expect.** Typically, a Done or Dismiss button belongs in a sheet’s top-right corner in a left-to-right layout. The Cancel button belongs in a sheet’s top-left corner.
+
+The exception to this is for sheets with additional subviews, where the Cancel button belongs in the top-right; this provides room for the Back button in the top-left on pages after the first. At the end of the navigation flow, replace the Cancel button with the Done button.
+
+
+
+Placement of the Cancel button when it appears by itself
+
+
+
+Placement of the Cancel button when it appears as part of a multi-step flow
+
+**Prefer using the page or form sheet presentation styles in an iPadOS app.** Each style uses a default size for the sheet, centering its content on top of a dimmed background view and providing a consistent experience. For developer guidance, see [`UIModalPresentationStyle`](https://developer.apple.com/documentation/UIKit/UIModalPresentationStyle).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/sheets#macOS)
+
+In macOS, a sheet is a cardlike view with rounded corners that floats on top of its parent window. The parent window is dimmed while the sheet is onscreen, signaling that people can’t interact with it until they dismiss the sheet. However, people expect to interact with other app windows before dismissing a sheet.
+
+
+
+**Present a sheet in a reasonable default size.** People don’t generally expect to resize sheets, so it’s important to use a size that’s appropriate for the content you display. In some cases, however, people appreciate a resizable sheet — such as when they need to expand the contents for a clearer view — so it’s a good idea to support resizing.
+
+**Let people interact with other app windows without first dismissing a sheet.** When a sheet opens, you bring its parent window to the front — if the parent window is a document window, you also bring forward its modeless document-related panels. When people want to interact with other windows in your app, make sure they can bring those windows forward even if they haven’t dismissed the sheet yet.
+
+**Position a sheet’s dismiss buttons as people expect.** People expect to find all buttons that dismiss a sheet — including Done, OK, and Cancel — at the bottom of the view, in the trailing corner.
+
+**Use a panel instead of a sheet if people need to repeatedly provide input and observe results.** A find and replace panel, for example, might let people initiate replacements individually, so they can observe the result of each search for correctness. For guidance, see [Panels](https://developer.apple.com/design/human-interface-guidelines/panels).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/sheets#visionOS)
+
+While a sheet is visible in a visionOS app, it floats in front of its parent window, dimming it, and becoming the target of people’s interactions with the app.
+
+Video with custom controls.
+
+Content description: A recording showing a sheet opening above a blank window in visionOS.
+
+Play
+
+**Avoid displaying a sheet that emerges from the bottom edge of a window.** To help people view the sheet, prefer centering it in their [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view).
+
+**Present a sheet in a default size that helps people retain their context.** Avoid displaying a sheet that covers most or all of its window, but consider letting people resize the sheet if they want.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/sheets#watchOS)
+
+In watchOS, a sheet is a full-screen view that slides over your app’s current content. The sheet is semitransparent to help maintain the current context, but the system applies a material to the background that blurs and desaturates the covered content.
+
+
+
+**Use a sheet only when your modal task requires a custom title or custom content presentation.** If you need to give people important information or present a set of choices, consider using an [alert](https://developer.apple.com/design/human-interface-guidelines/alerts) or [action sheet](https://developer.apple.com/design/human-interface-guidelines/action-sheets).
+
+**Keep sheet interactions brief and occasional.** Use a sheet only as a temporary interruption to the current workflow, and only to facilitate an important task. Avoid using a sheet to help people navigate your app’s content.
+
+**Change the default label of the dismiss control only if it makes sense in your app.** By default, the sheet displays a round Cancel button in the upper left corner. Use this button when the sheet lets people make changes to the app’s behavior or to their data. If your sheet simply presents information without enabling a task, use the standard Done button instead. You can use a [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars) to display multiple buttons.
+
+
+
+The standard Done button
+
+**If you change the default label, prefer using SF Symbols to represent the action.** Avoid using a label that might mislead people into thinking that the sheet is part of a hierarchical navigation interface. Also, if the text in the top-leading corner looks like a page or app title, people won’t know how to dismiss the sheet. For guidance, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons).
+
+
+
+
+
+
+
+
+
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/sheets#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/sheets#Related)
+
+[Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
+
+[Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets)
+
+[Popovers](https://developer.apple.com/design/human-interface-guidelines/popovers)
+
+[Panels](https://developer.apple.com/design/human-interface-guidelines/panels)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/sheets#Developer-documentation)
+
+[`sheet(item:onDismiss:content:)`](https://developer.apple.com/documentation/SwiftUI/View/sheet\(item:onDismiss:content:\)) — SwiftUI
+
+[`UISheetPresentationController`](https://developer.apple.com/documentation/UIKit/UISheetPresentationController) — UIKit
+
+[`presentAsSheet(_:)`](https://developer.apple.com/documentation/AppKit/NSViewController/presentAsSheet\(_:\)) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/sheets#Change-log)
+
+Date| Changes
+---|---
+March 29, 2024| Added guidance to use form or page sheet styles in iPadOS apps.
+December 5, 2023| Recommended using a split view to offer supplementary items in a visionOS app.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance for using sheets in watchOS.
+
diff --git a/web-app/public/skills/hig-components-layout/SKILL.md b/web-app/public/skills/hig-components-layout/SKILL.md
new file mode 100644
index 00000000..fd26bda2
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/SKILL.md
@@ -0,0 +1,104 @@
+---
+name: hig-components-layout
+version: 1.0.0
+description: ">"
+ Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user
+ asks about "sidebar", "split view", "tab bar", "tab view", "scroll view", "window design", "panel",
+ "list view", "table view", "column view", "outline view", "navigation structure", "app layout",
+ "boxes", "ornaments", or organizing content hierarchically in Apple apps.
+ Also use when the user says "how should I organize my app", "what navigation pattern should I use",
+ "my layout breaks on iPad", "how do I build a sidebar", "should I use tabs or a sidebar",
+ or "my app doesn't adapt to different screen sizes".
+ Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific
+ navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Layout and Navigation Components
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Organize hierarchically.** Structure information from broad categories to specific details. Sidebars for top-level sections, lists for browsable items, detail views for individual content.
+
+2. **Use standard navigation patterns.** Tab bars for flat navigation between peer sections (iPhone). Sidebars for deep hierarchical navigation (iPad, Mac). Match the pattern to the information architecture and platform.
+
+3. **Adapt to screen size.** Three-column on iPad collapses to single-column on iPhone. Use size classes and adaptive APIs (NavigationSplitView) for automatic adaptation.
+
+4. **Support multitasking on iPad.** Respond gracefully to Split View, Slide Over, and Stage Manager. Test at every split ratio and size class transition.
+
+5. **Maintain spatial consistency on visionOS.** Windows, volumes, and ornaments in shared space. Position predictably. Use ornaments for toolbars and controls without occluding content.
+
+6. **Use scroll views for overflow content.** Enable paging for discrete content units. Support pull-to-refresh where appropriate. Respect safe areas.
+
+7. **Keep navigation predictable.** Users should always know where they are, how they got there, and how to go back. Use back buttons, breadcrumbs, and clear section titles.
+
+8. **Prefer system components.** UINavigationController, UISplitViewController, NavigationSplitView, and TabView provide built-in adaptivity, accessibility, and state restoration.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [sidebars.md](references/sidebars.md) | Sidebars | Source lists, selection state, collapsible sections, iPad/Mac patterns |
+| [column-views.md](references/column-views.md) | Column Views | Finder-style browsing, progressive disclosure through columns |
+| [outline-views.md](references/outline-views.md) | Outline Views | Expandable hierarchies, disclosure triangles, tree structures |
+| [split-views.md](references/split-views.md) | Split Views | Two/three column layouts, NavigationSplitView, adaptive collapse |
+| [tab-views.md](references/tab-views.md) | Tab Views | Segmented tabs, page-style tabs, macOS tab grouping |
+| [tab-bars.md](references/tab-bars.md) | Tab Bars | Bottom tab bars (iOS), badge counts, max tab count |
+| [scroll-views.md](references/scroll-views.md) | Scroll Views | Paging, scroll indicators, content insets, pull-to-refresh |
+| [windows.md](references/windows.md) | Windows | macOS/visionOS window management, sizing, full-screen, restoration |
+| [panels.md](references/panels.md) | Panels | Inspector panels, utility panels, floating panels, macOS conventions |
+| [lists-and-tables.md](references/lists-and-tables.md) | Lists and Tables | Plain/grouped/inset-grouped styles, swipe actions, section headers |
+| [boxes.md](references/boxes.md) | Boxes | Content grouping containers, labeled boxes, macOS grouping |
+| [ornaments.md](references/ornaments.md) | Ornaments | visionOS toolbar attachments, positioning, visibility |
+
+## Navigation Pattern Selection
+
+| App Structure | Recommended Pattern | Platform Adaptation |
+|---|---|---|
+| 3-5 peer top-level sections | Tab Bar | iPhone: bottom tab bar. iPad: sidebar (`.sidebarAdaptable`, iPadOS 18+). Mac: sidebar or toolbar tabs |
+| Deep hierarchical content | Sidebar + NavigationSplitView | iPhone: single column stack. iPad: two/three columns. Mac: full multi-column |
+| Deep file/folder tree | Column View | Mac: Finder-style. iPad: adaptable. iPhone: push navigation |
+| Flat list with detail | Split View (two column) | iPhone: push/pop stack. iPad/Mac: primary + detail columns |
+| Document-based with inspectors | Window + Panels | Mac: main window with inspector. iPad: sheet or popover |
+| Spatial app with tools | Window + Ornaments | visionOS: ornaments on window. Other platforms: toolbars |
+
+## Layout Adaptation Checklist
+
+- [ ] **Compact width (iPhone portrait):** Navigation collapses to single stack? Tab bars visible?
+- [ ] **Regular width (iPad landscape, Mac):** Navigation expands to sidebar + detail? Space used well?
+- [ ] **Multitasking (iPad):** Adapts at every split ratio? Works in Slide Over?
+- [ ] **Accessibility:** Supports Dynamic Type at all sizes? VoiceOver order logical?
+- [ ] **Orientation:** Content reflows between portrait and landscape?
+- [ ] **visionOS:** Windows positioned ergonomically? Ornaments accessible? Depth meaningful?
+
+## Output Format
+
+1. **Recommended navigation pattern** with rationale for the app's information architecture.
+2. **Layout hierarchy** from root container down (e.g., TabView > NavigationSplitView > List > Detail).
+3. **Platform adaptation** across targeted platforms and size classes.
+4. **Size class behavior** at each transition.
+
+## Questions to Ask
+
+1. What is the app's information architecture? (Sections, hierarchy depth, top-level categories?)
+2. How many top-level sections?
+3. Which platforms?
+4. Need multitasking on iPad?
+5. SwiftUI or UIKit?
+
+## Related Skills
+
+- **hig-foundations** -- Layout spacing, margins, safe areas, alignment
+- **hig-platforms** -- Platform-specific navigation conventions
+- **hig-patterns** -- Multitasking, full-screen, and launching patterns
+- **hig-components-content** -- Content displayed within layout containers
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-layout/references/boxes.md b/web-app/public/skills/hig-components-layout/references/boxes.md
new file mode 100644
index 00000000..df7b2bd6
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/boxes.md
@@ -0,0 +1,48 @@
+---
+title: "Boxes | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/boxes
+
+# Boxes
+
+A box creates a visually distinct group of logically related information and components.
+
+
+
+By default, a box uses a visible border or background color to separate its contents from the rest of the interface. A box can also include a title.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/boxes#Best-practices)
+
+**Prefer keeping a box relatively small in comparison with its containing view.** As a box’s size gets close to the size of the containing window or screen, it becomes less effective at communicating the separation of grouped content, and it can crowd other content.
+
+**Consider using padding and alignment to communicate additional grouping within a box.** A box’s border is a distinct visual element — adding nested boxes to define subgroups can make your interface feel busy and constrained.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/boxes#Content)
+
+**Provide a succinct introductory title if it helps clarify the box’s contents.** The appearance of a box helps people understand that its contents are related, but it might make sense to provide more detail about the relationship. Also, a title can help VoiceOver users predict the content they encounter within the box.
+
+**If you need a title, write a brief phrase that describes the contents.** Use sentence-style capitalization. Avoid ending punctuation unless you use a box in a settings pane, where you append a colon to the title.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/boxes#Platform-considerations)
+
+ _No additional considerations for visionOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/boxes#iOS-iPadOS)
+
+By default, iOS and iPadOS use the secondary and tertiary background [colors](https://developer.apple.com/design/human-interface-guidelines/color) in boxes.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/boxes#macOS)
+
+By default, macOS displays a box’s title above it.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/boxes#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/boxes#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/boxes#Developer-documentation)
+
+[`GroupBox`](https://developer.apple.com/documentation/SwiftUI/GroupBox) — SwiftUI
+
+[`NSBox`](https://developer.apple.com/documentation/AppKit/NSBox) — AppKit
+
diff --git a/web-app/public/skills/hig-components-layout/references/column-views.md b/web-app/public/skills/hig-components-layout/references/column-views.md
new file mode 100644
index 00000000..8ef7ab30
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/column-views.md
@@ -0,0 +1,44 @@
+---
+title: "Column views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/column-views
+
+# Column views
+
+A column view — also called a _browser_ — lets people view and navigate a data hierarchy using a series of vertical columns.
+
+
+
+Each column represents one level of the hierarchy and contains horizontal rows of data items. Within a column, any parent item that contains nested child items is marked with a triangle icon. When people select a parent, the next column displays its children. People can continue navigating in this way until they reach an item with no children, and can also navigate back up the hierarchy to explore other branches of data.
+
+Note
+
+If you need to manage the presentation of hierarchical content in your iPadOS or visionOS app, consider using a [split view](https://developer.apple.com/design/human-interface-guidelines/split-views).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/column-views#Best-practices)
+
+Consider using a column view when you have a deep data hierarchy in which people tend to navigate back and forth frequently between levels, and you don’t need the sorting capabilities that a [list or table](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables) provides. For example, Finder offers a column view (in addition to icon, list, and gallery views) for navigating directory structures.
+
+**Show the root level of your data hierarchy in the first column.** People know they can quickly scroll back to the first column to begin navigating the hierarchy from the top again.
+
+**Consider showing information about the selected item when there are no nested items to display.** The Finder, for example, shows a preview of the selected item and information like the creation date, modification date, file type, and size.
+
+**Let people resize columns.** This is especially important if the names of some data items are too long to fit within the default column width.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/column-views#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/column-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/column-views#Related)
+
+[Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables)
+
+[Outline views](https://developer.apple.com/design/human-interface-guidelines/outline-views)
+
+[Split views](https://developer.apple.com/design/human-interface-guidelines/split-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/column-views#Developer-documentation)
+
+[`NSBrowser`](https://developer.apple.com/documentation/AppKit/NSBrowser) — AppKit
+
diff --git a/web-app/public/skills/hig-components-layout/references/lists-and-tables.md b/web-app/public/skills/hig-components-layout/references/lists-and-tables.md
new file mode 100644
index 00000000..71515003
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/lists-and-tables.md
@@ -0,0 +1,99 @@
+---
+title: "Lists and tables | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/lists-and-tables
+
+# Lists and tables
+
+Lists and tables present data in one or more columns of rows.
+
+
+
+A table or list can represent data that’s organized in groups or hierarchies, and it can support user interactions like selecting, adding, deleting, and reordering. Apps and games in all platforms can use tables to present content and options; many apps use lists to express an overall information hierarchy and help people navigate it. For example, iOS Settings uses a hierarchy of lists to help people choose options, and several apps — such as Mail in iPadOS and macOS — use a table within a [split view](https://developer.apple.com/design/human-interface-guidelines/split-views).
+
+Sometimes, people need to work with complex data in a multicolumn table or a spreadsheet. Apps that offer productivity tasks often use a table to represent various characteristics or attributes of the data in separate, sortable columns.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Best-practices)
+
+**Prefer displaying text in a list or table.** A table can include any type of content, but the row-based format is especially well suited to making text easy to scan and read. If you have items that vary widely in size — or you need to display a large number of images — consider using a [collection](https://developer.apple.com/design/human-interface-guidelines/collections) instead.
+
+**Let people edit a table when it makes sense.** People appreciate being able to reorder a list, even if they can’t add or remove items. In iOS and iPadOS, people must enter an edit mode before they can select table items.
+
+**Provide appropriate feedback when people select a list item.** The feedback can vary depending on whether selecting the item reveals a new view or toggles the item’s state. In general, a table that helps people navigate through a hierarchy persistently highlights the selected row to clarify the path people are taking. In contrast, a table that lists options often highlights a row only briefly before adding an image — such as a checkmark — indicating that the item is selected.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Content)
+
+**Keep item text succinct so row content is comfortable to read.** Short, succinct text can help minimize truncation and wrapping, making text easier to read and scan. If each item consists of a large amount of text, consider alternatives that help you avoid displaying over-large table rows. For example, you could list item titles only, letting people choose an item to reveal its content in a detail view.
+
+**Consider ways to preserve readability of text that might otherwise get clipped or truncated.** When a table is narrow — for example, if people can vary its width — you want content to remain recognizable and easy to read. Sometimes, an ellipsis in the middle of text can make an item easier to distinguish because it preserves both the beginning and the end of the content.
+
+**Use descriptive column headings in a multicolumn table.** Use nouns or short noun phrases with [title-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64), and don’t add ending punctuation. If you don’t include a column heading in a single-column table view, use a label or a header to help people understand the context.
+
+## [Style](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Style)
+
+**Choose a table or list style that coordinates with your data and platform.** Some styles use visual details to help communicate grouping and hierarchy or to provide specific experiences. In iOS and iPadOS, for example, the grouped style uses headers, footers, and additional space to separate groups of data; the elliptical style available in watchOS makes items appear as if they’re rolling off a rounded surface as people scroll; and macOS defines a bordered style that uses alternating row backgrounds to help make large tables easier to use. For developer guidance, see [`ListStyle`](https://developer.apple.com/documentation/SwiftUI/ListStyle).
+
+**Choose a row style that fits the information you need to display.** For example, you might need to display a small image in the leading end of a row, followed by a brief explanatory label. Some platforms provide built-in row styles you can use to arrange content in list rows, such as the [`UIListContentConfiguration`](https://developer.apple.com/documentation/UIKit/UIListContentConfiguration-swift.struct) API you can use to lay out content in a list’s rows, headers, and footers in iOS, iPadOS, and tvOS.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Platform-considerations)
+
+### [iOS, iPadOS, visionOS](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#iOS-iPadOS-visionOS)
+
+**Use an info button only to reveal more information about a row’s content.** An info button — called a _detail disclosure button_ when it appears in a list row — doesn’t support navigation through a hierarchical table or list. If you need to let people drill into a list or table row’s subviews, use a disclosure indicator accessory control. For developer guidance, see [`UITableViewCell.AccessoryType.disclosureIndicator`](https://developer.apple.com/documentation/UIKit/UITableViewCell/AccessoryType-swift.enum/disclosureIndicator).
+
+An info button shows details about a list item; it doesn’t support navigation.
+
+A disclosure indicator reveals the next level in a hierarchy; it doesn’t show details about the item.
+
+**Avoid adding an index to a table that displays controls — like disclosure indicators — in the trailing ends of its rows.** An _index_ typically consists of the letters in an alphabet, displayed vertically at the trailing side of a list. People can jump to a specific section in the list by choosing the index letter that maps to it. Because both the index and elements like disclosure indicators appear on the trailing side of a list, it can be difficult for people to use one element without activating the other.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#macOS)
+
+**When it provides value, let people click a column heading to sort a table view based on that column**. If people click the heading of a column that’s already sorted, re-sort the data in the opposite direction.
+
+**Let people resize columns.** Data displayed in a table view often varies in width. People appreciate resizing columns to help them concentrate on different areas or reveal clipped data.
+
+**Consider using alternating row colors in a multicolumn table.** Alternating colors can help people track row values across columns, especially in a wide table.
+
+**Use an outline view instead of a table view to present hierarchical data.** An [outline view](https://developer.apple.com/design/human-interface-guidelines/outline-views) looks like a table view, but includes disclosure triangles for exposing nested levels of data. For example, an outline view might display folders and the items they contain.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#tvOS)
+
+**Confirm that images near a table still look good as each row highlights and slightly increases in size when it becomes focused.** A focused row’s corners can also become rounded, which may affect the appearance of images on either side of it. Account for this effect as you prepare images, and don’t add your own masks to round the corners.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#watchOS)
+
+**When possible, limit the number of rows.** Short lists are easier for people to scan, but sometimes people expect a long list of items. For example, if people subscribe to a large number of podcasts, they might think something’s wrong if they can’t view all their items. You can help make a long list more manageable by listing the most relevant items and providing a way for people to view more.
+
+**Constrain the length of detail views if you want to support vertical page-based navigation.** People use vertical page-based navigation to swipe vertically among the detail items of different list rows. Navigating in this way saves time because people don’t need to return to the list to tap a new detail item, but it works only when detail views are short. If your detail views scroll, people won’t be able to use vertical page-based navigation to swipe among them.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Related)
+
+[Collections](https://developer.apple.com/design/human-interface-guidelines/collections)
+
+[Outline views](https://developer.apple.com/design/human-interface-guidelines/outline-views)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Developer-documentation)
+
+[`List`](https://developer.apple.com/documentation/SwiftUI/List) — SwiftUI
+
+[Tables](https://developer.apple.com/documentation/SwiftUI/Tables) — SwiftUI
+
+[`UITableView`](https://developer.apple.com/documentation/UIKit/UITableView) — UIKit
+
+[`NSTableView`](https://developer.apple.com/documentation/AppKit/NSTableView) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Videos)
+
+[ Stacks, Grids, and Outlines in SwiftUI ](https://developer.apple.com/videos/play/wwdc2020/10031)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance to reflect changes in watchOS 10.
+
diff --git a/web-app/public/skills/hig-components-layout/references/ornaments.md b/web-app/public/skills/hig-components-layout/references/ornaments.md
new file mode 100644
index 00000000..ae943ee4
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/ornaments.md
@@ -0,0 +1,56 @@
+---
+title: "Ornaments | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/ornaments
+
+# Ornaments
+
+In visionOS, an ornament presents controls and information related to a window, without crowding or obscuring the window’s contents.
+
+
+
+An ornament floats in a plane that’s parallel to its associated window and slightly in front of it along the z-axis. If the associated window moves, the ornament moves with it, maintaining its relative position; if the window’s contents scroll, the controls or information in the ornament remain unchanged.
+
+Ornaments can appear on any edge of a window and can contain UI components like buttons, segmented controls, and other views. The system uses ornaments to create and manage components like [toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars), [tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars), and video playback controls; you can use an ornament to create a custom component.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/ornaments#Best-practices)
+
+**Consider using an ornament to present frequently needed controls or information in a consistent location that doesn’t clutter the window.** Because an ornament stays close to its window, people always know where to find it. For example, Music uses an ornament to offer Now Playing controls, ensuring that these controls remain in a predictable location that’s easy to find.
+
+**In general, keep an ornament visible.** It can make sense to hide an ornament when people dive into a window’s content — for example, when they watch a video or view a photo — but in most cases, people appreciate having consistent access to an ornament’s controls.
+
+**If you need to display multiple ornaments, prioritize the overall visual balance of the window.** Ornaments help elevate important actions, but they can sometimes distract from your content. When necessary, consider constraining the total number of ornaments to avoid increasing a window’s visual weight and making your app feel more complicated. If you decide to remove an ornament, you can relocate its elements into the main window.
+
+**Aim to keep an ornament’s width the same or narrower than the width of the associated window.** If an ornament is wider than its window, it can interfere with a tab bar or other vertical content on the window’s side.
+
+**Consider using borderless buttons in an ornament.** By default, an ornament’s background is [glass](https://developer.apple.com/design/human-interface-guidelines/materials#visionOS), so if you place a button directly on the background, it may not need a visible border. When people look at a borderless button in an ornament, the system automatically applies the hover affect to it (for guidance, see [Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes)).
+
+**Use system-provided toolbars and tab bars unless you need to create custom components.** In visionOS, toolbars and tab bars automatically appear as ornaments, so you don’t need to use an ornament to create these components. For developer guidance, see [Toolbars](https://developer.apple.com/documentation/SwiftUI/Toolbars) and [`TabView`](https://developer.apple.com/documentation/SwiftUI/TabView).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/ornaments#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/ornaments#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/ornaments#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/ornaments#Developer-documentation)
+
+[`ornament(visibility:attachmentAnchor:contentAlignment:ornament:)`](https://developer.apple.com/documentation/SwiftUI/View/ornament\(visibility:attachmentAnchor:contentAlignment:ornament:\)) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/ornaments#Videos)
+
+[ Design for spatial user interfaces ](https://developer.apple.com/videos/play/wwdc2023/10076)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/ornaments#Change-log)
+
+Date| Changes
+---|---
+February 2, 2024| Added guidance on using multiple ornaments.
+December 5, 2023| Removed a statement about using ornaments to present supplementary items.
+June 21, 2023| New page.
+
diff --git a/web-app/public/skills/hig-components-layout/references/outline-views.md b/web-app/public/skills/hig-components-layout/references/outline-views.md
new file mode 100644
index 00000000..da03e0ef
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/outline-views.md
@@ -0,0 +1,64 @@
+---
+title: "Outline views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/outline-views
+
+# Outline views
+
+An outline view presents hierarchical data in a scrolling list of cells that are organized into columns and rows.
+
+![A stylized representation of a list of folders and images, displayed in an outline view containing four columns: \[Name\], \[Date Modified\], \[Size\], and \[Kind\]. The image is tinted red to subtly reflect the red in the original six-color Apple logo.](https://docs-assets.developer.apple.com/published/30462b13b59c89c7ba9e142a2fcef05b/components-outline-view-intro%402x.png)
+
+An outline view includes at least one column that contains primary hierarchical data, such as a set of parent containers and their children. You can add columns, as needed, to display attributes that supplement the primary data; for example, sizes and modification dates. Parent containers have disclosure triangles that expand to reveal their children.
+
+Finder windows offer an outline view for navigating the file system.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/outline-views#Best-practices)
+
+Outline views work well to display text-based content and often appear in the leading side of a [split view](https://developer.apple.com/design/human-interface-guidelines/split-views), with related content on the opposite side.
+
+**Use a table instead of an outline view to present data that’s not hierarchical.** For guidance, see [Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables).
+
+**Expose data hierarchy in the first column only.** Other columns can display attributes that apply to the hierarchical data in the primary column.
+
+**Use descriptive column headings to provide context.** Use nouns or short noun phrases with [title-style capitalization](https://help.apple.com/applestyleguide/#/apsgb744e4a3?sub=apdca93e113f1d64) and no punctuation; in particular, avoid adding a trailing colon. Always provide column headings in a multi-column outline view. If you don’t include a column heading in a single-column outline view, use a label or other means to make sure there’s enough context.
+
+**Consider letting people click column headings to sort an outline view.** In a sortable outline view, people can click a column heading to perform an ascending or descending sort based on that column. You can implement additional sorting based on secondary columns behind the scenes, if necessary. If people click the primary column heading, sorting occurs at each hierarchy level. For example, in the Finder, all top-level folders are sorted, then the items within each folder are sorted. If people click the heading of a column that’s already sorted, the folders and their contents are sorted again in the opposite direction.
+
+**Let people resize columns.** Data displayed in an outline view often varies in width. It’s important to let people adjust column width as needed to reveal data that’s wider than the column.
+
+**Make it easy for people to expand or collapse nested containers.** For example, clicking a disclosure triangle for a folder in a Finder window expands only that folder. However, Option-clicking the disclosure triangle expands all of its subfolders.
+
+**Retain people’s expansion choices.** If people expand various levels of an outline view to reach a specific item, store the state so you can display it again the next time. This way, people won’t need to navigate back to the same place again.
+
+**Consider using alternating row colors in multi-column outline views.** Alternating colors can make it easier for people to track row values across columns, especially in wide outline views.
+
+**Let people edit data if it makes sense in your app.** In an editable outline view cell, people expect to be able to single-click a cell to edit its contents. Note that a cell can respond differently to a double click. For example, an outline view listing files might let people single-click a file’s name to edit it, but double-click a file’s name to open the file. You can also let people reorder, add, and remove rows if it would be useful.
+
+**Consider using a centered ellipsis to truncate cell text instead of clipping it.** An ellipsis in the middle preserves the beginning and end of the cell text, which can make the content more distinct and recognizable than clipped text.
+
+**Consider offering a search field to help people find values quickly in a lengthy outline view.** Windows with an outline view as the primary feature often include a search field in the toolbar. For guidance, see [Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/outline-views#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/outline-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/outline-views#Related)
+
+[Column views](https://developer.apple.com/design/human-interface-guidelines/column-views)
+
+[Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables)
+
+[Split views](https://developer.apple.com/design/human-interface-guidelines/split-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/outline-views#Developer-documentation)
+
+[`OutlineGroup`](https://developer.apple.com/documentation/SwiftUI/OutlineGroup) — SwiftUI
+
+[`NSOutlineView`](https://developer.apple.com/documentation/AppKit/NSOutlineView) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/outline-views#Videos)
+
+[ Stacks, Grids, and Outlines in SwiftUI ](https://developer.apple.com/videos/play/wwdc2020/10031)
+
diff --git a/web-app/public/skills/hig-components-layout/references/panels.md b/web-app/public/skills/hig-components-layout/references/panels.md
new file mode 100644
index 00000000..c3d0cc57
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/panels.md
@@ -0,0 +1,75 @@
+---
+title: "Panels | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/panels
+
+# Panels
+
+In a macOS app, a panel typically floats above other open windows providing supplementary controls, options, or information related to the active window or current selection.
+
+
+
+In general, a panel has a less prominent appearance than an app’s [main window](https://developer.apple.com/design/human-interface-guidelines/windows#macOS-window-states). When the situation calls for it, a panel can also use a dark, translucent style to support a heads-up display (or _HUD_) experience.
+
+When your app runs in other platforms, consider using a modal view to present supplementary content that’s relevant to the current task or selection. For guidance, see [Modality](https://developer.apple.com/design/human-interface-guidelines/modality).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/panels#Best-practices)
+
+**Use a panel to give people quick access to important controls or information related to the content they’re working with.** For example, you might use a panel to provide controls or settings that affect the selected item in the active document or window.
+
+**Consider using a panel to present inspector functionality.** An _inspector_ displays the details of the currently selected item, automatically updating its contents when the item changes or when people select a new item. In contrast, if you need to present an _Info_ window — which always maintains the same contents, even when the selected item changes — use a regular window, not a panel. Depending on the layout of your app, you might also consider using a [split view](https://developer.apple.com/design/human-interface-guidelines/split-views) pane to present an inspector.
+
+**Prefer simple adjustment controls in a panel.** As much as possible, avoid including controls that require typing text or selecting items to act upon because these actions can require multiple steps. Instead, consider using controls like sliders and steppers because these components can give people more direct control.
+
+**Write a brief title that describes the panel’s purpose.** Because a panel often floats above other open windows in your app, it needs a title bar so people can position it where they want. Create a short title using a noun — or a noun phrase with [title-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64) — that can help people recognize the panel onscreen. For example, macOS provides familiar panels titled “Fonts” and “Colors,” and many apps use the title “Inspector.”
+
+**Show and hide panels appropriately.** When your app becomes active, bring all of its open panels to the front, regardless of which window was active when the panel opened. When your app is inactive, hide all of its panels.
+
+**Avoid including panels in the Window menu’s documents list.** It’s fine to include commands for showing or hiding panels in the [Window menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Window-menu), but panels aren’t documents or standard app windows, and they don’t belong in the Window menu’s list.
+
+**In general, avoid making a panel’s minimize button available.** People don’t usually need to minimize a panel, because it displays only when needed and disappears when the app is inactive.
+
+**Refer to panels by title in your interface and in help documentation.** In menus, use the panel’s title without including the term _panel_ : for example, “Show Fonts,” “Show Colors,” and “Show Inspector.” In help documentation, it can be confusing to introduce “panel” as a different type of window, so it’s generally best to refer to a panel by its title or — when it adds clarity — by appending _window_ to the title. For example, the title “Inspector” often supplies enough context to stand on its own, whereas it can be clearer to use “Fonts window” and “Colors window” instead of just “Fonts” and “Colors.”
+
+## [HUD-style panels](https://developer.apple.com/design/human-interface-guidelines/panels#HUD-style-panels)
+
+A HUD-style panel serves the same function as a standard panel, but its appearance is darker and translucent. HUDs work well in apps that present highly visual content or that provide an immersive experience, such as media editing or a full-screen slide show. For example, QuickTime Player uses a HUD to display inspector information without obstructing too much content.
+
+
+
+**Prefer standard panels.** People can be distracted or confused by a HUD when there’s no logical reason for its presence. Also, a HUD might not match the current appearance setting. In general, use a HUD only:
+
+ * In a media-oriented app that presents movies, photos, or slides
+
+ * When a standard panel would obscure essential content
+
+ * When you don’t need to include controls — with the exception of the disclosure triangle, most system-provided controls don’t match a HUD’s appearance.
+
+
+
+
+**Maintain one panel style when your app switches modes.** For example, if you use a HUD when your app is in full-screen mode, prefer maintaining the HUD style when people take your app out of full-screen mode.
+
+**Use color sparingly in HUDs.** Too much color in the dark appearance of a HUD can be distracting. Often, you need only small amounts of high-contrast color to highlight important information in a HUD.
+
+**Keep HUDs small.** HUDs are designed to be unobtrusively useful, so letting them grow too large defeats their primary purpose. Don’t let a HUD obscure the content it adjusts, and make sure it doesn’t compete with the content for people’s attention.
+
+For developer guidance, see [`hudWindow`](https://developer.apple.com/documentation/AppKit/NSWindow/StyleMask-swift.struct/hudWindow).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/panels#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/panels#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/panels#Related)
+
+[Windows](https://developer.apple.com/design/human-interface-guidelines/windows)
+
+[Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/panels#Developer-documentation)
+
+[`NSPanel`](https://developer.apple.com/documentation/AppKit/NSPanel) — AppKit
+
+[`hudWindow`](https://developer.apple.com/documentation/AppKit/NSWindow/StyleMask-swift.struct/hudWindow) — AppKit
+
diff --git a/web-app/public/skills/hig-components-layout/references/scroll-views.md b/web-app/public/skills/hig-components-layout/references/scroll-views.md
new file mode 100644
index 00000000..0f10a347
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/scroll-views.md
@@ -0,0 +1,123 @@
+---
+title: "Scroll views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/scroll-views
+
+# Scroll views
+
+A scroll view lets people view content that’s larger than the view’s boundaries by moving the content vertically or horizontally.
+
+
+
+The scroll view itself has no appearance, but it can display a translucent _scroll indicator_ that typically appears after people begin scrolling the view’s content. Although the appearance and behavior of scroll indicators can vary per platform, all indicators provide visual feedback about the scrolling action. For example, in iOS, iPadOS, macOS, visionOS, and watchOS, the indicator shows whether the currently visible content is near the beginning, middle, or end of the view.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Best-practices)
+
+**Support default scrolling gestures and keyboard shortcuts.** People are accustomed to the systemwide scrolling behavior and expect it to work everywhere. If you build custom scrolling for a view, make sure your scroll indicators use the elastic behavior that people expect.
+
+**Make it apparent when content is scrollable.** Because scroll indicators aren’t always visible, it can be helpful to make it obvious when content extends beyond the view. For example, displaying partial content at the edge of a view indicates that there’s more content in that direction. Although most people immediately try scrolling a view to discover if additional content is available, it’s considerate to draw their attention to it.
+
+**Avoid putting a scroll view inside another scroll view with the same orientation.** Nesting scroll views that have the same orientation can create an unpredictable interface that’s difficult to control. It’s alright to place a horizontal scroll view inside a vertical scroll view (or vice versa), however.
+
+**Consider supporting page-by-page scrolling if it makes sense for your content.** In some situations, people appreciate scrolling by a fixed amount of content per interaction instead of scrolling continuously. On most platforms, you can define the size of such a _page_ — typically the current height or width of the view — and define an interaction that scrolls one page at a time. To help maintain context during page-by-page scrolling, you can define a unit of overlap, such as a line of text, a row of glyphs, or part of a picture, and subtract the unit from the page size. For developer guidance, see [`PagingScrollTargetBehavior`](https://developer.apple.com/documentation/SwiftUI/PagingScrollTargetBehavior).
+
+**In some cases, scroll automatically to help people find their place.** Although people initiate almost all scrolling, automatic scrolling can be helpful when relevant content is no longer in view, such as when:
+
+ * Your app performs an operation that selects content or places the insertion point in an area that’s currently hidden. For example, when your app locates text that people are searching for, scroll the content to bring the new selection into view.
+
+ * People start entering information in a location that’s not currently visible. For example, if the insertion point is on one page and people navigate to another page, scroll back to the insertion point as soon as they begin to enter text.
+
+ * The pointer moves past the edge of the view while people are making a selection. In this case, follow the pointer by scrolling in the direction it moves.
+
+ * People select something and scroll to a new location before acting on the selection. In this case, scroll until the selection is in view before performing the operation.
+
+
+
+
+In all cases, automatically scroll the content only as much as necessary to help people retain context. For example, if part of a selection is visible, you don’t need to scroll the entire selection into view.
+
+**If you support zoom, set appropriate maximum and minimum scale values.** For example, zooming in on text until a single character fills the screen doesn’t make sense in most situations.
+
+## [Scroll edge effects](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Scroll-edge-effects)
+
+In iOS, iPadOS, and macOS, a _scroll edge effect_ is a variable blur that provides a transition between a content area and an area with [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) controls, such as [toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars). In most cases, the system applies a scroll edge effect automatically when a pinned element overlaps with scrolling content. If you use custom controls or layouts, the effect might not appear, and you may need to add it manually. For developer guidance, see [`ScrollEdgeEffectStyle`](https://developer.apple.com/documentation/SwiftUI/ScrollEdgeEffectStyle) and [`UIScrollEdgeEffect`](https://developer.apple.com/documentation/UIKit/UIScrollEdgeEffect).
+
+There are two styles of scroll edge effect: soft and hard.
+
+ * Use a [`soft`](https://developer.apple.com/documentation/SwiftUI/ScrollEdgeEffectStyle/soft) edge effect in most cases, especially in iOS and iPadOS, to provide a subtle transition that works well for toolbars and interactive elements like buttons.
+
+ * Use a [`hard`](https://developer.apple.com/documentation/SwiftUI/ScrollEdgeEffectStyle/hard) edge effect primarily in macOS for a stronger, more opaque boundary that’s ideal for interactive text, backless controls, or pinned table headers that need extra clarity.
+
+
+
+
+**Only use a scroll edge effect when a scroll view is adjacent to floating interface elements.** Scroll edge effects aren’t decorative. They don’t block or darken like overlays; they exist to clarify where controls and content meet.
+
+**Apply one scroll edge effect per view.** In split view layouts on iPad and Mac, each pane can have its own scroll edge effect; in this case, keep them consistent in height to maintain alignment.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/scroll-views#iOS-iPadOS)
+
+**Consider showing a page control when a scroll view is in page-by-page mode.** [Page controls](https://developer.apple.com/design/human-interface-guidelines/page-controls) show how many pages, screens, or other chunks of content are available and indicates which one is currently visible. For example, Weather uses a page control to indicate movement between people’s saved locations. If you show a page control with a scroll view, don’t show the scrolling indicator on the same axis to avoid confusing people with redundant controls.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/scroll-views#macOS)
+
+In macOS, a _scroll indicator_ is commonly called a _scroll bar_.
+
+**If necessary, use small or mini scroll bars in a panel.** When space is tight, you can use smaller scroll bars in panels that need to coexist with other windows. Be sure to use the same size for all controls in such a panel.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/scroll-views#tvOS)
+
+Views in tvOS can scroll, but they aren’t treated as distinct objects with scroll indicators. Instead, when content exceeds the size of the screen, the system automatically scrolls the interface to keep focused items visible.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/scroll-views#visionOS)
+
+In visionOS, the scroll indicator has a small, fixed size to help communicate that people can scroll efficiently without making large movements. To make it easy to find, the scroll indicator always appears in a predictable location with respect to the window: vertically centered at the trailing edge during vertical scrolling and horizontally centered at the window’s bottom edge during horizontal scrolling.
+
+When people begin swiping content in the direction they want it to scroll, the scroll indicator appears at the window’s edge, visually reinforcing the effect of their gesture and providing feedback about the content’s current position and overall length. When people look at the scroll indicator and begin a drag gesture, the indicator enables a jog bar experience that lets people manipulate the scrolling speed instead of the content’s position. In this experience, the scroll indicator reveals tick marks that speed up or slow down as people make small adjustments to their gesture, providing visual feedback that helps people precisely control scrolling acceleration.
+
+Video with custom controls.
+
+Content description: A recording showing a scroll indicator on a long page in the Notes app. As the viewer drags the page quickly, the indicator shows tick marks that match the scrolling speed.
+
+Play
+
+**If necessary, account for the size of the scroll indicator.** Although the indicator’s overall size is small, it’s a little thicker than the same component in iOS. If your content uses tight margins, consider increasing them to prevent the scroll indicator from overlapping the content.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/scroll-views#watchOS)
+
+**Prefer vertically scrolling content.** People are accustomed to using the Digital Crown to navigate to and within apps on Apple Watch. If your app contains a single list or content view, rotating the Digital Crown scrolls vertically when your app’s content is taller than the height of the display.
+
+**Use tab views to provide page-by-page scrolling.** watchOS displays tab views as pages. If you place tab views in a vertical stack, people can rotate the Digital Crown to move vertically through full-screen pages of content. In this scenario, the system displays a page indicator next to the Digital Crown that shows people where they are in the content, both within the current page and within a set of pages. For guidance, see [Tab views](https://developer.apple.com/design/human-interface-guidelines/tab-views).
+
+**When displaying paged content, consider limiting the content of an individual page to a single screen height.** Embracing this constraint clarifies the purpose of each page, helping you create a more glanceable design. However, if your app has long pages, people can still use the Digital Crown both to navigate between shorter pages and to scroll content in a longer page because the page indicator expands into a scroll indicator when necessary. Use variable-height pages judiciously and place them after fixed-height pages when possible.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Related)
+
+[Page controls](https://developer.apple.com/design/human-interface-guidelines/page-controls)
+
+[Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+[Pointing devices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Developer-documentation)
+
+[`ScrollView`](https://developer.apple.com/documentation/SwiftUI/ScrollView)
+
+[`UIScrollView`](https://developer.apple.com/documentation/UIKit/UIScrollView)
+
+[`NSScrollView`](https://developer.apple.com/documentation/AppKit/NSScrollView)
+
+[`WKPageOrientation`](https://developer.apple.com/documentation/WatchKit/WKPageOrientation)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/scroll-views#Change-log)
+
+Date| Changes
+---|---
+July 28, 2025| Added guidance for scroll edge effects.
+February 2, 2024| Added artwork showing the behavior of the visionOS scroll indicator.
+December 5, 2023| Described the visionOS scroll indicator and added guidance for integrating it with window layout.
+June 5, 2023| Updated guidance for using scroll views in watchOS.
+
diff --git a/web-app/public/skills/hig-components-layout/references/sidebars.md b/web-app/public/skills/hig-components-layout/references/sidebars.md
new file mode 100644
index 00000000..cbf43b08
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/sidebars.md
@@ -0,0 +1,109 @@
+---
+title: "Sidebars | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/sidebars
+
+# Sidebars
+
+A sidebar appears on the leading side of a view and lets people navigate between sections in your app or game.
+
+
+
+A sidebar floats above content without being anchored to the edges of the view. It provides a broad, flat view of an app’s information hierarchy, giving people access to several peer content areas or modes at the same time.
+
+A sidebar requires a large amount of vertical and horizontal space. When space is limited or you want to devote more of the screen to other information or functionality, a more compact control such as a [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars) may provide a better navigation experience. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/sidebars#Best-practices)
+
+**Extend content beneath the sidebar.** In iOS, iPadOS, and macOS, as with other controls such as toolbars and tab bars, sidebars float above content in the [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) layer. To reinforce the separation and floating appearance of the sidebar, extend content beneath it either by letting it horizontally scroll or applying a background extension view, which mirrors adjacent content to give the impression of stretching it under the sidebar. For developer guidance, see [`backgroundExtensionEffect()`](https://developer.apple.com/documentation/SwiftUI/View/backgroundExtensionEffect\(\)).
+
+
+
+
+
+
+
+
+
+**When possible, let people customize the contents of a sidebar.** A sidebar lets people navigate to important areas in your app, so it works well when people can decide which areas are most important and in what order they appear.
+
+**Group hierarchy with disclosure controls if your app has a lot of content.** Using [disclosure controls](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls) helps keep the sidebar’s vertical space to a manageable level.
+
+**Consider using familiar symbols to represent items in the sidebar.** [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) provides a wide range of customizable symbols you can use to represent items in your app. If you need to use a custom icon, consider creating a [custom symbol](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Custom-symbols) rather than using a bitmap image. Download the SF Symbols app from [Apple Design Resources](https://developer.apple.com/design/resources/#sf-symbols).
+
+**Consider letting people hide the sidebar.** People sometimes want to hide the sidebar to create more room for content details or to reduce distraction. When possible, let people hide and show the sidebar using the platform-specific interactions they already know. For example, in iPadOS, people expect to use the built-in edge swipe gesture; in macOS, you can include a show/hide button or add Show Sidebar and Hide Sidebar commands to your app’s View menu. In visionOS, a window typically expands to accommodate a sidebar, so people rarely need to hide it. Avoid hiding the sidebar by default to ensure that it remains discoverable.
+
+**In general, show no more than two levels of hierarchy in a sidebar.** When a data hierarchy is deeper than two levels, consider using a split view interface that includes a content list between the sidebar items and detail view.
+
+**If you need to include two levels of hierarchy in a sidebar, use succinct, descriptive labels to title each group.** To help keep labels short, omit unnecessary words.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/sidebars#Platform-considerations)
+
+ _No additional considerations for tvOS. Not supported in watchOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/sidebars#iOS)
+
+**Avoid using a sidebar.** A sidebar takes up a lot of space in landscape orientation and isn’t available in portrait orientation. Instead, consider using a [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars), which takes less space and remains visible in both orientations.
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/sidebars#iPadOS)
+
+When you use the [`sidebarAdaptable`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/sidebarAdaptable) style of tab view to present a sidebar, you choose whether to display a sidebar or a tab bar when your app opens. Both variations include a button that people can use to switch between them. This style also responds automatically to rotation and window resizing, providing a version of the control that’s appropriate to the width of the view.
+
+Developer note
+
+To display a sidebar only, use [`NavigationSplitView`](https://developer.apple.com/documentation/SwiftUI/NavigationSplitView) to present a sidebar in the primary pane of a split view, or use [`UISplitViewController`](https://developer.apple.com/documentation/UIKit/UISplitViewController).
+
+**Consider using a tab bar first.** A tab bar provides more space to feature content, and offers enough flexibility to navigate between many apps’ main areas. If you need to expose more areas than fit in a tab bar, the tab bar’s convertible sidebar-style appearance can provide access to content that people use less frequently. For guidance, see [Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars).
+
+**If necessary, apply the correct appearance to a sidebar.** If you’re not using SwiftUI to create a sidebar, you can use the [`UICollectionLayoutListConfiguration.Appearance.sidebar`](https://developer.apple.com/documentation/UIKit/UICollectionLayoutListConfiguration-swift.struct/Appearance-swift.enum/sidebar) appearance of a collection view list layout. For developer guidance, see [`UICollectionLayoutListConfiguration.Appearance`](https://developer.apple.com/documentation/UIKit/UICollectionLayoutListConfiguration-swift.struct/Appearance-swift.enum).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/sidebars#macOS)
+
+A sidebar’s row height, text, and glyph size depend on its overall size, which can be small, medium, or large. You can set the size programmatically, but people can also change it by selecting a different sidebar icon size in General settings.
+
+**Avoid stylizing your app by specifying a fixed color for all sidebar icons.** By default, sidebar icons use the current [accent color](https://developer.apple.com/design/human-interface-guidelines/color#App-accent-colors) and people expect to see their chosen accent color throughout all the apps they use. Although a fixed color can help clarify the meaning of an icon, you want to make sure that most sidebar icons display the color people choose.
+
+**Consider automatically hiding and revealing a sidebar when its container window resizes.** For example, reducing the size of a Mail viewer window can automatically collapse its sidebar, making more room for message content.
+
+**Avoid putting critical information or actions at the bottom of a sidebar.** People often relocate a window in a way that hides its bottom edge.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/sidebars#visionOS)
+
+**If your app’s hierarchy is deep, consider using a sidebar within a tab in a tab bar.** In this situation, a sidebar can support secondary navigation within the tab. If you do this, be sure to prevent selections in the sidebar from changing which tab is currently open.
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/sidebars#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/sidebars#Related)
+
+[Split views](https://developer.apple.com/design/human-interface-guidelines/split-views)
+
+[Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/sidebars#Developer-documentation)
+
+[`sidebarAdaptable`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/sidebarAdaptable) — SwiftUI
+
+[`NavigationSplitView`](https://developer.apple.com/documentation/SwiftUI/NavigationSplitView) — SwiftUI
+
+[`sidebar`](https://developer.apple.com/documentation/SwiftUI/ListStyle/sidebar) — SwiftUI
+
+[`UICollectionLayoutListConfiguration`](https://developer.apple.com/documentation/UIKit/UICollectionLayoutListConfiguration-swift.struct) — UIKit
+
+[`NSSplitViewController`](https://developer.apple.com/documentation/AppKit/NSSplitViewController) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/sidebars#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/sidebars#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance for extending content beneath the sidebar.
+August 6, 2024| Updated guidance to include the SwiftUI adaptable sidebar style.
+December 5, 2023| Added artwork for iPadOS.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-layout/references/split-views.md b/web-app/public/skills/hig-components-layout/references/split-views.md
new file mode 100644
index 00000000..2dc62e1d
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/split-views.md
@@ -0,0 +1,110 @@
+---
+title: "Split views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/split-views
+
+# Split views
+
+A split view manages the presentation of multiple adjacent panes of content, each of which can contain a variety of components, including tables, collections, images, and custom views.
+
+
+
+Typically, you use a split view to show multiple levels of your app’s hierarchy at once and support navigation between them. In this scenario, selecting an item in the view’s primary pane displays the item’s contents in the secondary pane. Similarly, a split view can display a tertiary pane if items in the secondary pane contain additional content.
+
+It’s common to use a split view to display a [sidebar](https://developer.apple.com/design/human-interface-guidelines/sidebars) for navigation, where the leading pane lists the top-level items or collections in an app, and the secondary and optional tertiary panes can present child collections and item details. Rarely, you might also use a split view to provide groups of functionality that supplement the primary view — for example, Keynote in macOS uses split view panes to present the slide navigator, the presenter notes, and the inspector pane in areas that surround the main slide canvas.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/split-views#Best-practices)
+
+**To support navigation, persistently highlight the current selection in each pane that leads to the detail view.** The selected appearance clarifies the relationship between the content in various panes and helps people stay oriented.
+
+**Consider letting people drag and drop content between panes.** Because a split view provides access to multiple levels of hierarchy, people can conveniently move content from one part of your app to another by dragging items to different panes. For guidance, see [Drag and drop](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/split-views#Platform-considerations)
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/split-views#iOS)
+
+**Prefer using a split view in a regular — not a compact — environment.** A split view needs horizontal space in which to display multiple panes. In a compact environment, such as iPhone in portrait orientation, it’s difficult to display multiple panes without wrapping or truncating the content, making it less legible and harder to interact with.
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/split-views#iPadOS)
+
+In iPadOS, a split view can include either two vertical panes, like Mail, or three vertical panes, like Keynote.
+
+**Account for narrow, compact, and intermediate window widths.** Since iPad windows are fluidly resizable, it’s important to consider the design of a split view layout at multiple widths. In particular, ensure that it’s possible to navigate between the various panes in a logical way. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout). For developer guidance, see [`NavigationSplitView`](https://developer.apple.com/documentation/SwiftUI/NavigationSplitView) and [`UISplitViewController`](https://developer.apple.com/documentation/UIKit/UISplitViewController).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/split-views#macOS)
+
+In macOS, you can arrange the panes of a split view vertically, horizontally, or both. A split view includes dividers between panes that can support dragging to resize them. For developer guidance, see [`VSplitView`](https://developer.apple.com/documentation/SwiftUI/VSplitView) and [`HSplitView`](https://developer.apple.com/documentation/SwiftUI/HSplitView).
+
+ * Vertical
+ * Horizontal
+ * Multiple
+
+
+
+
+
+
+
+
+
+**Set reasonable defaults for minimum and maximum pane sizes.** If people can resize the panes in your app’s split view, make sure to use sizes that keep the divider visible. If a pane gets too small, the divider can seem to disappear, becoming difficult to use.
+
+**Consider letting people hide a pane when it makes sense.** If your app includes an editing area, for example, consider letting people hide other panes to reduce distractions or allow more room for editing — in Keynote, people can hide the navigator and presenter notes panes when they want to edit slide content.
+
+**Provide multiple ways to reveal hidden panes.** For example, you might provide a toolbar button or a menu command — including a keyboard shortcut — that people can use to restore a hidden pane.
+
+**Prefer the thin divider style.** The thin divider measures one point in width, giving you maximum space for content while remaining easy for people to use. Avoid using thicker divider styles unless you have a specific need. For example, if both sides of a divider present table rows that use strong linear elements that might make a thin divider hard to distinguish, it might work to use a thicker divider. For developer guidance, see [`NSSplitView.DividerStyle`](https://developer.apple.com/documentation/AppKit/NSSplitView/DividerStyle-swift.enum).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/split-views#tvOS)
+
+In tvOS, a split view can work well to help people filter content. When people choose a filter category in the primary pane, your app can display the results in the secondary pane.
+
+**Choose a split view layout that keeps the panes looking balanced.** By default, a split view devotes a third of the screen width to the primary pane and two-thirds to the secondary pane, but you can also specify a half-and-half layout.
+
+**Display a single title above a split view, helping people understand the content as a whole.** People already know how to use a split view to navigate and filter content; they don’t need titles that describe what each pane contains.
+
+**Choose the title’s alignment based on the type of content the secondary pane contains.** Specifically, when the secondary pane contains a content collection, consider centering the title in the window. In contrast, if the secondary pane contains a single main view of important content, consider placing the title above the primary view to give the content more room.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/split-views#visionOS)
+
+**To display supplementary information, prefer a split view instead of a new window.** A split view gives people convenient access to more information without leaving the current context, whereas a new window may confuse people who are trying to navigate or reposition content. Opening more windows also requires you to carefully manage the relationship between views in your app or game. If you need to request a small amount of information or present a simple task that someone must complete before returning to their main task, use a [sheet](https://developer.apple.com/design/human-interface-guidelines/sheets).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/split-views#watchOS)
+
+In watchOS, the split view displays either the list view or a detail view as a full-screen view.
+
+**Automatically display the most relevant detail view.** When your app launches, show people the most pertinent information. For example, display information relevant to their location, the time, or their recent actions.
+
+**If your app displays multiple detail pages, place the detail views in a vertical[tab view](https://developer.apple.com/design/human-interface-guidelines/tab-views).** People can then use the Digital Crown to scroll between the detail view’s tabs. watchOS also displays a page indicator next to the Digital Crown, indicating the number of tabs and the currently selected tab.
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/split-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/split-views#Related)
+
+[Sidebars](https://developer.apple.com/design/human-interface-guidelines/sidebars)
+
+[Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/split-views#Developer-documentation)
+
+[`NavigationSplitView`](https://developer.apple.com/documentation/SwiftUI/NavigationSplitView) — SwiftUI
+
+[`UISplitViewController`](https://developer.apple.com/documentation/UIKit/UISplitViewController) — UIKit
+
+[`NSSplitViewController`](https://developer.apple.com/documentation/AppKit/NSSplitViewController) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/split-views#Videos)
+
+[ Make your UIKit app more flexible ](https://developer.apple.com/videos/play/wwdc2025/282)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/split-views#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added iOS and iPadOS platform considerations.
+December 5, 2023| Added guidance for split views in visionOS.
+June 5, 2023| Added guidance for split views in watchOS.
+
diff --git a/web-app/public/skills/hig-components-layout/references/tab-bars.md b/web-app/public/skills/hig-components-layout/references/tab-bars.md
new file mode 100644
index 00000000..4d42f566
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/tab-bars.md
@@ -0,0 +1,173 @@
+---
+title: "Tab bars | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/tab-bars
+
+# Tab bars
+
+A tab bar lets people navigate between top-level sections of your app.
+
+
+
+Tab bars help people understand the different types of information or functionality that an app provides. They also let people quickly switch between sections of the view while preserving the current navigation state within each section.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Best-practices)
+
+**Use a tab bar to support navigation, not to provide actions.** A tab bar lets people navigate among different sections of an app, like the Alarm, Stopwatch, and Timer tabs in the Clock app. If you need to provide controls that act on elements in the current view, use a [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars) instead.
+
+**Make sure the tab bar is visible when people navigate to different sections of your app.** If you hide the tab bar, people can forget which area of the app they’re in. The exception is when a modal view covers the tab bar, because a modal is temporary and self-contained.
+
+**Use the appropriate number of tabs required to help people navigate your app.** As a representation of your app’s hierarchy, it’s important to weigh the complexity of additional tabs against the need for people to frequently access each section; keep in mind that it’s generally easier to navigate among fewer tabs. Where available, consider a sidebar or a tab bar that adapts to a sidebar as an alternative for an app with a complex information structure.
+
+**Avoid overflow tabs.** Depending on device size and orientation, the number of visible tabs can be smaller than the total number of tabs. If horizontal space limits the number of visible tabs, the trailing tab becomes a More tab in iOS and iPadOS, revealing the remaining items in a separate list. The More tab makes it harder for people to reach and notice content on tabs that are hidden, so limit scenarios in your app where this can happen.
+
+**Don’t disable or hide tab bar buttons, even when their content is unavailable.** Having tab bar buttons available in some cases but not others makes your app’s interface appear unstable and unpredictable. If a section is empty, explain why its content is unavailable.
+
+**Include tab labels to help with navigation.** A tab label appears beneath or beside a tab bar icon, and can aid navigation by clearly describing the type of content or functionality the tab contains. Use single words whenever possible.
+
+**Consider using SF Symbols to provide familiar, scalable tab bar icons.** When you use [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols), tab bar icons automatically adapt to different contexts. For example, the tab bar can be regular or compact, depending on the device and orientation. Tab bar icons appear above tab labels in compact views, whereas in regular views, the icons and labels appear side by side. Prefer filled symbols or icons for consistency with the platform.
+
+
+
+If you’re creating custom tab bar icons, see [Apple Design Resources](https://developer.apple.com/design/resources/) for tab bar icon dimensions.
+
+
+
+**Use a badge to indicate that critical information is available.** You can display a badge — a red oval containing white text and either a number or an exclamation point — on a tab to indicate that there’s new or updated information in the section that warrants a person’s attention. Reserve badges for critical information so you don’t dilute their impact and meaning. For guidance, see [Notifications](https://developer.apple.com/design/human-interface-guidelines/notifications).
+
+
+
+**Avoid applying a similar color to tab labels and content layer backgrounds.** If your app already has bright, colorful content in the content layer, prefer a monochromatic appearance for tab bars, or choose an accent color with sufficient visual differentiation. For more guidance, see [Liquid Glass color](https://developer.apple.com/design/human-interface-guidelines/color#Liquid-Glass-color).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Platform-considerations)
+
+ _No additional considerations for macOS. Not supported in watchOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/tab-bars#iOS)
+
+A tab bar floats above content at the bottom of the screen. Its items rest on a [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) background that allows content beneath to peek through.
+
+For tab bars with an attached accessory, like the MiniPlayer in Music, you can choose to minimize the tab bar and move the accessory inline with it when a person scrolls down. A person can exit the minimized state by tapping a tab or scrolling to the top of the view. For developer guidance, see [`TabBarMinimizeBehavior`](https://developer.apple.com/documentation/SwiftUI/TabBarMinimizeBehavior) and [`UITabBarController.MinimizeBehavior`](https://developer.apple.com/documentation/UIKit/UITabBarController/MinimizeBehavior).
+
+
+
+A tab bar with an attached accessory, expanded
+
+
+
+A tab bar with an attached accessory, minimized
+
+A tab bar can include a distinct search item at the trailing end. For guidance, see [Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields).
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/tab-bars#iPadOS)
+
+The system displays a tab bar near the top of the screen. You can choose to have the tab bar appear as a fixed element, or with a button that converts it to a sidebar. For developer guidance, see [`tabBarOnly`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/tabBarOnly) and [`sidebarAdaptable`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/sidebarAdaptable).
+
+ * Tab bar
+ * Sidebar
+
+
+
+
+
+
+
+Note
+
+To present a sidebar without the option to convert it to a tab bar, use a [navigation split view](https://developer.apple.com/documentation/swiftui/navigationsplitview) instead of a tab view. For guidance, see [Sidebars](https://developer.apple.com/design/human-interface-guidelines/sidebars).
+
+**Prefer a tab bar for navigation.** A tab bar provides access to the sections of your app that people use most. If your app is more complex, you can provide the option to convert the tab bar to a sidebar so people can access a wider set of navigation options.
+
+**Let people customize the tab bar.** In apps with a lot of sections that people might want to access, it can be useful to let people select items that they use frequently and add them to the tab bar, or remove items that they use less frequently. For example, in the Music app, a person can choose a favorite playlist to display in the tab bar. If you let people select their own tabs, aim for a default list of five or fewer to preserve continuity between compact and regular view sizes. For developer guidance, see [`TabViewCustomization`](https://developer.apple.com/documentation/SwiftUI/TabViewCustomization) and [`UITab.Placement`](https://developer.apple.com/documentation/UIKit/UITab/Placement).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/tab-bars#tvOS)
+
+A tab bar is highly customizable. For example, you can:
+
+ * Specify a tint, color, or image for the tab bar background
+
+ * Choose a font for tab items, including a different font for the selected item
+
+ * Specify tints for selected and unselected items
+
+ * Add button icons, like settings and search
+
+
+
+
+By default, a tab bar is translucent, and only the selected tab is opaque. When people use the remote to focus on the tab bar, the selected tab includes a drop shadow that emphasizes its selected state. The height of a tab bar is 68 points, and its top edge is 46 points from the top of the screen; you can’t change either of these values.
+
+If there are more items than can fit in the tab bar, the system truncates the rightmost item by applying a fade effect that begins at the right side of the tab bar. If there are enough items to cause scrolling, the system also applies a truncating fade effect that starts from the left side.
+
+**Be aware of tab bar scrolling behaviors.** By default, people can scroll the tab bar offscreen when the current tab contains a single main view. You can see examples of this behavior in the Watch Now, Movies, TV Show, Sports, and Kids tabs in the TV app. The exception is when a screen contains a split view, such as the TV app’s Library tab or an app’s Settings screen. In this case, the tab bar remains pinned at the top of the view while people scroll the content within the primary and secondary panes of the split view. Regardless of a tab’s contents, focus always returns to the tab bar at the top of the page when people press Menu on the remote.
+
+**In a live-viewing app, organize tabs in a consistent way.** For the best experience, organize content in live-streaming apps with tabs in the following order:
+
+ * Live content
+
+ * Cloud DVR or other recorded content
+
+ * Other content
+
+
+
+
+For additional guidance, see [Live-viewing apps](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/tab-bars#visionOS)
+
+In visionOS, a tab bar is always vertical, floating in a position that’s fixed relative to the window’s leading side. When people look at a tab bar, it automatically expands; to open a specific tab, people look at the tab and tap. While a tab bar is expanded, it can temporarily obscure the content behind it.
+
+Video with custom controls.
+
+Content description: A recording showing a closeup of a tab bar along the side of an app's window in visionOS. The tab bar includes only symbols. The currently selected tab receives the hover effect, showing that someone is looking at it, and the bar expands to display both symbols and labels.
+
+Play
+
+**Supply a symbol and a text label for each tab.** A tab’s symbol is always visible in the tab bar. When people look at the tab bar, the system reveals tab labels, too. Even though the tab bar expands, you need to keep tab labels short so people can read them at a glance.
+
+Collapsed
+
+Expanded
+
+**If it makes sense in your app, consider using a sidebar within a tab.** If your app’s hierarchy is deep, you might want to use a [sidebar](https://developer.apple.com/design/human-interface-guidelines/sidebars) to support secondary navigation within a tab. If you do this, be sure to prevent selections in the sidebar from changing which tab is currently open.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Related)
+
+[Tab views](https://developer.apple.com/design/human-interface-guidelines/tab-views)
+
+[Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars)
+
+[Sidebars](https://developer.apple.com/design/human-interface-guidelines/sidebars)
+
+[Materials](https://developer.apple.com/design/human-interface-guidelines/materials)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Developer-documentation)
+
+[`TabView`](https://developer.apple.com/documentation/SwiftUI/TabView) — SwiftUI
+
+[`TabViewBottomAccessoryPlacement`](https://developer.apple.com/documentation/SwiftUI/TabViewBottomAccessoryPlacement) — SwiftUI
+
+[Enhancing your app’s content with tab navigation](https://developer.apple.com/documentation/SwiftUI/Enhancing-your-app-content-with-tab-navigation) — SwiftUI
+
+[`UITabBar`](https://developer.apple.com/documentation/UIKit/UITabBar) — UIKit
+
+[Elevating your iPad app with a tab bar and sidebar](https://developer.apple.com/documentation/UIKit/elevating-your-ipad-app-with-a-tab-bar-and-sidebar) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Videos)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/tab-bars#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for Liquid Glass.
+July 28, 2025| Added guidance for Liquid Glass.
+September 9, 2024| Added art representing the tab bar in iPadOS 18.
+August 6, 2024| Updated with guidance for the tab bar in iPadOS 18.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-layout/references/tab-views.md b/web-app/public/skills/hig-components-layout/references/tab-views.md
new file mode 100644
index 00000000..fb3b0310
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/tab-views.md
@@ -0,0 +1,68 @@
+---
+title: "Tab views | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/tab-views
+
+# Tab views
+
+A tab view presents multiple mutually exclusive panes of content in the same area, which people can switch between using a tabbed control.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/tab-views#Best-practices)
+
+**Use a tab view to present closely related areas of content.** The appearance of a tab view provides a strong visual indication of enclosure. People expect each tab to display content that is in some way similar or related to the content in the other tabs.
+
+**Make sure the controls within a pane affect content only in the same pane.** Panes are mutually exclusive, so ensure they’re fully self-contained.
+
+**Provide a label for each tab that describes the contents of its pane.** A good label helps people predict the contents of a pane before clicking or tapping its tab. In general, use nouns or short noun phrases for tab labels. A verb or short verb phrase may make sense in some contexts. Use title-style capitalization for tab labels.
+
+**Avoid using a pop-up button to switch between tabs.** A tabbed control is efficient because it requires a single click or tap to make a selection, whereas a pop-up button requires two. A tabbed control also presents all choices onscreen at the same time, whereas people must click a pop-up button to see its choices. Note that a pop-up button can be a reasonable alternative in cases where there are too many panes of content to reasonably display with tabs.
+
+**Avoid providing more than six tabs in a tab view.** Having more than six tabs can be overwhelming and create layout issues. If you need to present six or more tabs, consider another way to implement the interface. For example, you could instead present each tab as a view option in a pop-up button menu.
+
+For developer guidance, see [`NSTabView`](https://developer.apple.com/documentation/AppKit/NSTabView).
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/tab-views#Anatomy)
+
+The tabbed control appears on the top edge of the content area. You can choose to hide the control, which is appropriate for an app that switches between panes programmatically.
+
+
+
+When you hide the tabbed control, the content area can be borderless, bezeled, or bordered with a line. A borderless view can be solid or transparent.
+
+**In general, inset a tab view by leaving a margin of window-body area on all sides of a tab view.** This layout looks clean and leaves room for additional controls that aren’t directly related to the contents of the tab view. You can extend a tab view to meet the window edges, but this layout is unusual.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/tab-views#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, or visionOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/tab-views#iOS-iPadOS)
+
+For similar functionality, consider using a [segmented control](https://developer.apple.com/design/human-interface-guidelines/segmented-controls) instead.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/tab-views#watchOS)
+
+watchOS displays tab views using [page controls](https://developer.apple.com/design/human-interface-guidelines/components/presentation/page-controls). For developer guidance, see [`TabView`](https://developer.apple.com/documentation/SwiftUI/TabView) and [`verticalPage`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/verticalPage).
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/tab-views#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/tab-views#Related)
+
+[Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars)
+
+[Segmented controls](https://developer.apple.com/design/human-interface-guidelines/segmented-controls)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/tab-views#Developer-documentation)
+
+[`TabView`](https://developer.apple.com/documentation/SwiftUI/TabView) — SwiftUI
+
+[`NSTabView`](https://developer.apple.com/documentation/AppKit/NSTabView) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/tab-views#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Added guidance for using tab views in watchOS.
+
diff --git a/web-app/public/skills/hig-components-layout/references/windows.md b/web-app/public/skills/hig-components-layout/references/windows.md
new file mode 100644
index 00000000..17fd3813
--- /dev/null
+++ b/web-app/public/skills/hig-components-layout/references/windows.md
@@ -0,0 +1,188 @@
+---
+title: "Windows | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/windows
+
+# Windows
+
+A window presents UI views and components in your app or game.
+
+
+
+In iPadOS, macOS, and visionOS, windows help define the visual boundaries of app content and separate it from other areas of the system, and enable multitasking workflows both within and between apps. Windows include system-provided interface elements such as frames and window controls that let people open, close, resize, and relocate them.
+
+Conceptually, apps use two types of windows to display content:
+
+ * A _primary_ window presents the main navigation and content of an app, and actions associated with them.
+
+ * An _auxiliary_ window presents a specific task or area in an app. Dedicated to one experience, an auxiliary window doesn’t allow navigation to other app areas, and it typically includes a button people use to close it after completing the task.
+
+
+
+
+For guidance laying out content within a window on any platform, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout); for guidance laying out content in Apple Vision Pro space, see [Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout). For developer guidance, see [Windows](https://developer.apple.com/documentation/SwiftUI/Windows).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/windows#Best-practices)
+
+**Make sure that your windows adapt fluidly to different sizes to support multitasking and multiwindow workflows.** For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout) and [Multitasking](https://developer.apple.com/design/human-interface-guidelines/multitasking).
+
+**Choose the right moment to open a new window.** Opening content in a separate window is great for helping people multitask or preserve context. For example, Mail opens a new window whenever someone selects the Compose action, so both the new message and the existing email are visible at the same time. However, opening new windows excessively creates clutter and can make navigating your app more confusing. Avoid opening new windows as default behavior unless it makes sense for your app.
+
+**Consider providing the option to view content in a new window.** While it’s best to avoid opening new windows as default behavior unless it benefits your user experience, it’s also great to give people the flexibility of viewing content in multiple ways. Consider letting people view content in a new window using a command in a [context menu](https://developer.apple.com/design/human-interface-guidelines/context-menus) or in the [File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu). For developer guidance, see [`OpenWindowAction`](https://developer.apple.com/documentation/SwiftUI/OpenWindowAction).
+
+**Avoid creating custom window UI.** System-provided windows look and behave in a way that people understand and recognize. Avoid making custom window frames or controls, and don’t try to replicate the system-provided appearance. Doing so without perfectly matching the system’s look and behavior can make your app feel broken.
+
+**Use the term _window_ in user-facing content.** The system refers to app windows as _windows_ regardless of type. Using different terms — including _scene_ , which refers to window implementation — is likely to confuse people.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/windows#Platform-considerations)
+
+ _Not supported in iOS, tvOS, or watchOS._
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/windows#iPadOS)
+
+Windows present in one of two ways depending on a person’s choice in Multitasking & Gestures settings.
+
+ * **Full screen.** App windows fill the entire screen, and people switch between them — or between multiple windows of the same app — using the app switcher.
+
+ * **Windowed.** People can freely resize app windows. Multiple windows can be onscreen at once, and people can reposition them and bring them to the front. The system remembers window size and placement even when an app is closed.
+
+
+
+
+ * Full screen
+ * Windowed
+
+
+
+
+
+
+
+**Make sure window controls don’t overlap toolbar items.** When windowed, app windows include window controls at the leading edge of the toolbar. If your app has toolbar buttons at the leading edge, they might be hidden by window controls when they appear. To prevent this, instead of placing buttons directly on the leading edge, move them inward when the window controls appear.
+
+**Consider letting people use a gesture to open content in a new window.** For example, people can use the pinch gesture to expand a Notes item into a new window. For developer guidance, see [`collectionView(_:sceneActivationConfigurationForItemAt:point:)`](https://developer.apple.com/documentation/UIKit/UICollectionViewDelegate/collectionView\(_:sceneActivationConfigurationForItemAt:point:\)) (to transition from a collection view item), or [`UIWindowScene.ActivationInteraction`](https://developer.apple.com/documentation/UIKit/UIWindowScene/ActivationInteraction) (to transition from an item in any other view).
+
+Tip
+
+If you only need to let people view one file, you can present it without creating your own window, but you must support multiple windows in your app. For developer guidance, see [`QLPreviewSceneActivationConfiguration`](https://developer.apple.com/documentation/QuickLook/QLPreviewSceneActivationConfiguration).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/windows#macOS)
+
+In macOS, people typically run several apps at the same time, often viewing windows from multiple apps on one desktop and switching frequently between different windows — moving, resizing, minimizing, and revealing the windows to suit their work style.
+
+To learn about setting up a window to display your game in macOS, see [Managing your game window for Metal in macOS](https://developer.apple.com/documentation/Metal/managing-your-game-window-for-metal-in-macos).
+
+#### [macOS window anatomy](https://developer.apple.com/design/human-interface-guidelines/windows#macOS-window-anatomy)
+
+A macOS window consists of a frame and a body area. People can move a window by dragging the frame and can often resize the window by dragging its edges.
+
+The _frame_ of a window appears above the body area and can include window controls and a [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars). In rare cases, a window can also display a bottom bar, which is a part of the frame that appears below body content.
+
+#### [macOS window states](https://developer.apple.com/design/human-interface-guidelines/windows#macOS-window-states)
+
+A macOS window can have one of three states:
+
+ * **Main.** The frontmost window that people view is an app’s main window. There can be only one main window per app.
+
+ * **Key.** Also called the _active window_ , the key window accepts people’s input. There can be only one key window onscreen at a time. Although the front app’s main window is usually the key window, another window — such as a panel floating above the main window — might be key instead. People typically click a window to make it key; when people click an app’s Dock icon to bring all of that app’s windows forward, only the most recently accessed window becomes key.
+
+ * **Inactive.** A window that’s not in the foreground is an inactive window.
+
+
+
+
+The system gives main, key, and inactive windows different appearances to help people visually identify them. For example, the key window uses color in the title bar options for closing, minimizing, and zooming; inactive windows and main windows that aren’t key use gray in these options. Also, inactive windows don’t use [vibrancy](https://developer.apple.com/design/human-interface-guidelines/materials) (an effect that can pull color into a window from the content underneath it), which makes them appear subdued and seem visually farther away than the main and key windows.
+
+
+
+Note
+
+Some windows — typically, panels like Colors or Fonts — become the key window only when people click the window’s title bar or a component that requires keyboard input, such as a text field.
+
+**Make sure custom windows use the system-defined appearances.** People rely on the visual differences between windows to help them identify the foreground window and know which window will accept their input. When you use system-provided components, a window’s background and button appearances update automatically when the window changes state; if you use custom implementations, you need to do this work yourself.
+
+**Avoid putting critical information or actions in a bottom bar, because people often relocate a window in a way that hides its bottom edge.** If you must include one, use it only to display a small amount of information directly related to a window’s contents or to a selected item within it. For example, Finder uses a bottom bar (called the status bar) to display the total number of items in a window, the number of selected items, and how much space is available on the disk. A bottom bar is small, so if you have more information to display, consider using an inspector, which typically presents information on the trailing side of a split view.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS)
+
+visionOS defines two main window styles: default and volumetric. Both a default window (called a _window_) and a volumetric window (called a _volume_) can display 2D and 3D content, and people can view multiple windows and volumes at the same time in both the Shared Space and a Full Space.
+
+A window
+
+A volume
+
+Note
+
+visionOS also defines the _plain_ window style, which is similar to the default style, except that the upright plane doesn’t use the glass background. For developer guidance, see [`PlainWindowStyle`](https://developer.apple.com/documentation/SwiftUI/PlainWindowStyle).
+
+The system defines the initial position of the first window or volume people open in your app or game. In both the Shared Space and a Full Space, people can move windows and volumes to new locations.
+
+#### [visionOS windows](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-windows)
+
+The default window style consists of an upright plane that uses an unmodifiable background [material](https://developer.apple.com/design/human-interface-guidelines/materials) called _glass_ and includes a close button, window bar, and resize controls that let people close, move, and resize the window. A window can also include a Share button, [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars), [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars), and one or more [ornaments](https://developer.apple.com/design/human-interface-guidelines/ornaments). By default, visionOS uses dynamic [scale](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Scale) to help a window’s size appear to remain consistent regardless of its proximity to the viewer. For developer guidance, see [`DefaultWindowStyle`](https://developer.apple.com/documentation/SwiftUI/DefaultWindowStyle).
+
+A window
+
+**Prefer using a window to present a familiar interface and to support familiar tasks.** Help people feel at home in your app by displaying an interface they’re already comfortable with, reserving more [immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences) for the meaningful content and activities you offer. If you want to showcase bounded 3D content like a game board, consider using a [volume](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-volumes).
+
+**Retain the window’s glass background.** The default glass background helps your content feel like part of people’s surroundings while adapting dynamically to lighting and using specular reflections and shadows to communicate the window’s scale and position. Removing the glass material tends to cause UI elements and text to become less legible and to no longer appear related to each other; using an opaque background obscures people’s surroundings and can make a window feel constricting and heavy.
+
+**Choose an initial window size that minimizes empty areas within it.** By default, a window measures 1280x720 pt. When a window first opens, the system places it about two meters in front of the wearer, giving it an apparent width of about three meters. Too much empty space inside a window can make it look unnecessarily large while also obscuring other content in people’s space.
+
+**Aim for an initial shape that suits a window’s content.** For example, a default Keynote window is wide because slides are wide, whereas a default Safari window is tall because most webpages are much longer than they are wide. For games, a tower-building game is likely to open in a taller window than a driving game.
+
+**Choose a minimum and maximum size for each window to help keep your content looking great.** People appreciate being able to resize windows as they customize their space, but you need to make sure your layout adjusts well across all sizes. If you don’t set a minimum and maximum size for a window, people could make it so small that UI elements overlap or so large that your app or game becomes unusable. For developer guidance, see [Positioning and sizing windows](https://developer.apple.com/documentation/visionOS/positioning-and-sizing-windows).
+
+A window containing 3D content
+
+**Minimize the depth of 3D content you display in a window.** The system adds highlights and shadows to the views and controls within a window, giving them the appearance of [depth](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Depth) and helping them feel more substantial, especially when people view the window from an angle. Although you can display 3D content in a window, the system clips it if the content extends too far from the window’s surface. To display 3D content that has greater depth, use a volume.
+
+#### [visionOS volumes](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-volumes)
+
+You can use a volume to display 2D or 3D content that people can view from any angle. A volume includes window-management controls just like a window, but unlike in a window, a volume’s close button and window bar shift position to face the viewer as they move around the volume. For developer guidance, see [`VolumetricWindowStyle`](https://developer.apple.com/documentation/SwiftUI/VolumetricWindowStyle).
+
+A volume
+
+**Prefer using a volume to display rich, 3D content.** In contrast, if you want to present a familiar, UI-centric interface, it generally works best to use a [window](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-windows).
+
+**Place 2D content so it looks good from multiple angles.** Because a person’s perspective changes as they move around a volume, the location of 2D content within it might appear to change in ways that don’t make sense. To pin 2D content to specific areas of 3D content inside a volume, you can use an attachment.
+
+**In general, use dynamic scaling.** Dynamic scaling helps a volume’s content remain comfortably legible and easy to interact with, even when it’s far away from the viewer. On the other hand, if you want a volume’s content to represent a real-world object, like a product in a retail app, you can use fixed scaling (this is the default).
+
+**Take advantage of the default baseplate appearance to help people discern the edges of a volume.** In visionOS 2 and later, the system automatically makes a volume’s horizontal “floor,” or _baseplate_ , visible by displaying a gentle glow around its border when people look at it. If your content doesn’t fill the volume, the system-provided glow can help people become aware of the volume’s edges, which can be particularly useful in keeping the resize control easy to find. On the other hand, if your content is full bleed or fills the volume’s bounds — or if you display a custom baseplate appearance — you may not want the default glow.
+
+**Consider offering high-value content in an ornament.** In visionOS 2 and later, a volume can include an ornament in addition to a toolbar and tab bar. You can use an ornament to reduce clutter in a volume and elevate important views or controls. When you use an attachment anchor to specify the ornament’s location, such as `topBack` or `bottomFront`, the ornament remains in the same position, relative to the viewer’s perspective, as they move around the volume. Be sure to avoid placing an ornament on the same edge as a toolbar or tab bar, and prefer creating only one additional ornament to avoid overshadowing the important content in your volume. For developer guidance, see [`ornament(visibility:attachmentAnchor:contentAlignment:ornament:)`](https://developer.apple.com/documentation/SwiftUI/View/ornament\(visibility:attachmentAnchor:contentAlignment:ornament:\)).
+
+**Choose an alignment that supports the way people interact with your volume.** As people move a volume, the baseplate can remain parallel to the floor of a person’s surroundings, or it can tilt to match the angle at which a person is looking. In general, a volume that remains parallel to the floor works well for content that people don’t interact with much, whereas a volume that tilts to match where a person is looking can keep content comfortably usable, even when the viewer is reclining.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/windows#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/windows#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Split views](https://developer.apple.com/design/human-interface-guidelines/split-views)
+
+[Multitasking](https://developer.apple.com/design/human-interface-guidelines/multitasking)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/windows#Developer-documentation)
+
+[Windows](https://developer.apple.com/documentation/SwiftUI/Windows) — SwiftUI
+
+[`WindowGroup`](https://developer.apple.com/documentation/SwiftUI/WindowGroup) — SwiftUI
+
+[`UIWindow`](https://developer.apple.com/documentation/UIKit/UIWindow) — UIKit
+
+[`NSWindow`](https://developer.apple.com/documentation/AppKit/NSWindow) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/windows#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/windows#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added best practices, and updated with guidance for resizable windows in iPadOS.
+June 10, 2024| Updated to include guidance for using volumes in visionOS 2 and added game-specific examples.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-components-menus/SKILL.md b/web-app/public/skills/hig-components-menus/SKILL.md
new file mode 100644
index 00000000..b75247a5
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/SKILL.md
@@ -0,0 +1,86 @@
+---
+name: hig-components-menus
+version: 1.0.0
+description: ">-"
+ Apple HIG guidance for menu and button components including menus, context menus,
+ dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons,
+ pull-down buttons, disclosure controls, and standard buttons. Use this skill
+ when the user says "how should my buttons look," "what goes in the menu bar,"
+ "should I use a context menu or action sheet," "how do I design a toolbar," or
+ asks about button design, menu design, context menu, toolbar, menu bar, action
+ button, pop-up button, pull-down button, disclosure control, dock menu, edit
+ menu, or any menu/button component layout and behavior. Cross-references:
+ hig-components-search, hig-components-controls, hig-components-dialogs.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Menus and Buttons
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Menus should be contextual and predictable.** Standard items in standard locations. Follow platform conventions for ordering and grouping.
+
+2. **Use standard button styles.** System-defined styles communicate affordance and maintain visual consistency. Prefer them over custom designs.
+
+3. **Toolbars for frequent actions.** Most commonly used commands in the toolbar. Rarely used actions belong in menus.
+
+4. **Menu bar is the primary command interface on macOS.** Every command reachable from the menu bar. Toolbars and context menus supplement, not replace.
+
+5. **Context menus for secondary actions.** Right-click or long-press, relevant to the item under the pointer. Never put a command only in a context menu.
+
+6. **Pop-up buttons for mutually exclusive choices.** Select exactly one option from a set.
+
+7. **Pull-down buttons for action lists.** No current selection; they offer a set of commands.
+
+8. **Action buttons consolidate related actions** behind a single icon in toolbars or title bars.
+
+9. **Disclosure controls for progressive disclosure.** Show or hide additional content.
+
+10. **Dock menus: short and focused** on the most useful actions when the app is running.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [menus.md](references/menus.md) | General menu design | Item ordering, grouping, shortcuts |
+| [context-menus.md](references/context-menus.md) | Context menus | Right-click, long press, secondary actions |
+| [dock-menus.md](references/dock-menus.md) | Dock menus | macOS app-level actions, running state |
+| [edit-menus.md](references/edit-menus.md) | Edit menus | Undo, copy, paste, standard items |
+| [the-menu-bar.md](references/the-menu-bar.md) | Menu bar | macOS primary command interface, structure |
+| [toolbars.md](references/toolbars.md) | Toolbars | Frequent actions, customization, placement |
+| [buttons.md](references/buttons.md) | Buttons | System styles, sizing, affordance |
+| [action-button.md](references/action-button.md) | Action button | Grouped secondary actions, toolbar use |
+| [pop-up-buttons.md](references/pop-up-buttons.md) | Pop-up buttons | Mutually exclusive choice selection |
+| [pull-down-buttons.md](references/pull-down-buttons.md) | Pull-down buttons | Action lists, no current selection |
+| [disclosure-controls.md](references/disclosure-controls.md) | Disclosure controls | Progressive disclosure, show/hide |
+
+## Output Format
+
+1. **Component recommendation** -- which menu or button type and why.
+2. **Visual hierarchy** -- placement, sizing, grouping within the interface.
+3. **Platform-specific behavior** across iOS, iPadOS, macOS, visionOS.
+4. **Keyboard shortcuts** (macOS) -- standard and custom shortcuts for menu items and toolbar actions.
+
+## Questions to Ask
+
+1. Which platforms?
+2. Primary or secondary action?
+3. How many actions need to be available?
+4. macOS menu bar app?
+
+## Related Skills
+
+- **hig-components-search** -- Search fields, page controls alongside toolbars and menus
+- **hig-components-controls** -- Toggles, pickers, segmented controls complementing buttons
+- **hig-components-dialogs** -- Alerts, sheets, popovers triggered by menu items or buttons
+- **hig-inputs** -- Keyboard shortcuts and pointer interactions with menus and toolbars
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-menus/references/action-button.md b/web-app/public/skills/hig-components-menus/references/action-button.md
new file mode 100644
index 00000000..77ae959c
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/action-button.md
@@ -0,0 +1,61 @@
+---
+title: "Action button | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/action-button
+
+# Action button
+
+The Action button gives people quick access to their favorite features on supported iPhone and Apple Watch models.
+
+
+
+On a supported device, people can use the Action button to run [App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts) or access system-provided functionality, like turning the flashlight on or off. On Apple Watch Ultra, the Action button supports activity-related actions, including workouts and dives.
+
+A person chooses a function for the Action button when they set up their device; later, they can adjust this choice in Settings. When someone associates an App Shortcut with the Action button, pressing the button runs the App Shortcut similarly to using their voice with Siri or tapping it in Spotlight.
+
+When designing your app or game, think of the Action button as another way for someone to quickly access a function that they use on a regular basis.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/action-button#Best-practices)
+
+**Support the Action button with a set of your app’s essential functions.** For example, if your cooking app includes an egg timer, a “Start Egg Timer” action might be one that people want to initiate when they press the Action button. You don’t need to offer an App Shortcut that opens your app, because the system provides this function already. Your app icon, widgets, and Apple Watch complications give people other quick ways to open your app. For additional guidance, see [App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts).
+
+**For each action you support, write a short label that succinctly describes it.** People see your labels when they visit Settings to configure the Action button’s behavior. Create labels that use [title-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64), begin with a verb, use present tense, and exclude articles and prepositions. Keep labels as short as possible, with a maximum of three words. For example, use “Start Race” instead of “Started Race” or “Start the Race.”
+
+**Prefer letting the system show people how to use the Action button with your app.** When you support the Action button, the system automatically helps people configure it to initiate one of your app’s functions. Avoid creating content that repeats the guidance offered in Settings for the Action button, or other usage tips the system provides.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/action-button#Platform-considerations)
+
+ _Not supported in iPadOS, macOS, tvOS, or visionOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/action-button#iOS)
+
+**Let people use your actions without leaving their current context.** When possible, make use of lightweight multitasking capabilities like [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities) and custom snippets to provide functionality without opening your app. For example, the “Set Timer” action doesn’t launch the Clock app; it prompts people to set a duration for the timer, and then launches a Live Activity with the countdown.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/action-button#watchOS)
+
+In watchOS, a person can assign the Action button’s first press to drop a waypoint, start a dive, or begin a specific workout. Beyond a single button press, the Action button also supports secondary actions like marking a segment or transitioning to the next modality during a multi-part workout.
+
+**Consider offering a secondary function that supports or advances the primary action people choose.** People often use the Action button without looking at the screen, so a subsequent button press needs to flow logically from the first press, while also making sense in the current context. If your app supports workout or dive actions, consider designing a simple, intuitive secondary function that people can easily learn and remember. Consider carefully before you offer more than one secondary function, because doing so can increase people’s cognitive load and make your app seem harder to use.
+
+**Prefer using subsequent button presses to support additional functionality rather than to stop or conclude a function.** If you need to let people stop their main task — as opposed to pausing the current function — offer this option within your interface instead.
+
+**Pause the current function when people press the Action button and side button together.** The exception is in a diving app where pausing a dive may be dangerous to the diver, causing them to lose track of their depth or not understand how long they’ve been underwater. Unless pausing the current function results in a negative experience, be sure to meet people’s expectations by letting them pause their current activity when they press both buttons at the same time.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/action-button#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/action-button#Related)
+
+[Workouts](https://developer.apple.com/design/human-interface-guidelines/workouts)
+
+[Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown)
+
+[App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts)
+
+[Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/action-button#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Updated to include guidance for iOS.
+September 14, 2022| New page.
+
diff --git a/web-app/public/skills/hig-components-menus/references/buttons.md b/web-app/public/skills/hig-components-menus/references/buttons.md
new file mode 100644
index 00000000..50dc8712
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/buttons.md
@@ -0,0 +1,261 @@
+---
+title: "Buttons | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/buttons
+
+# Buttons
+
+A button initiates an instantaneous action.
+
+
+
+Versatile and highly customizable, buttons give people simple, familiar ways to do tasks in your app. In general, a button combines three attributes to clearly communicate its function:
+
+ * **Style.** A visual style based on size, color, and shape.
+
+ * **Content.** A symbol (or icon), text label, or both that a button displays to convey its purpose.
+
+ * **Role.** A system-defined role that identifies a button’s semantic meaning and can affect its appearance.
+
+
+
+
+There are also many button-like components that have distinct appearances and behaviors for specific use cases, like [toggles](https://developer.apple.com/design/human-interface-guidelines/toggles), [pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons), and [segmented controls](https://developer.apple.com/design/human-interface-guidelines/segmented-controls).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/buttons#Best-practices)
+
+When buttons are instantly recognizable and easy to understand, an app tends to feel intuitive and well designed.
+
+**Make buttons easy for people to use.** It’s essential to include enough space around a button so that people can visually distinguish it from surrounding components and content. Giving a button enough space is also critical for helping people select or activate it, regardless of the method of input they use. As a general rule, a button needs a hit region of at least 44x44 pt — in visionOS, 60x60 pt — to ensure that people can select it easily, whether they use a fingertip, a pointer, their eyes, or a remote.
+
+**Always include a press state for a custom button.** Without a press state, a button can feel unresponsive, making people wonder if it’s accepting their input.
+
+## [Style](https://developer.apple.com/design/human-interface-guidelines/buttons#Style)
+
+System buttons offer a range of styles that support customization while providing built-in interaction states, accessibility support, and appearance adaptation. Different platforms define different styles that help you communicate hierarchies of actions in your app.
+
+**In general, use a button that has a prominent visual style for the most likely action in a view.** To draw people’s attention to a specific button, use a prominent button style so the system can apply an accent color to the button’s background. Buttons that use color tend to be the most visually distinctive, helping people quickly identify the actions they’re most likely to use. Keep the number of prominent buttons to one or two per view. Presenting too many prominent buttons increases cognitive load, requiring people to spend more time considering options before making a choice.
+
+**Use style — not size — to visually distinguish the preferred choice among multiple options.** When you use buttons of the same size to offer two or more options, you signal that the options form a coherent set of choices. By contrast, placing two buttons of different sizes near each other can make the interface look confusing and inconsistent. If you want to highlight the preferred or most likely option in a set, use a more prominent button style for that option and a less prominent style for the remaining ones.
+
+**Avoid applying a similar color to button labels and content layer backgrounds.** If your app already has bright, colorful content in the content layer, prefer using the default monochromatic appearance of button labels. For more guidance, see [Liquid Glass color](https://developer.apple.com/design/human-interface-guidelines/color#Liquid-Glass-color).
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/buttons#Content)
+
+**Ensure that each button clearly communicates its purpose.** Depending on the platform, a button can contain a symbol (or icon), a text label, or both to help people understand what it does.
+
+Note
+
+In macOS and visionOS, the system displays a tooltip after people hover over a button for a moment. A tooltip displays a brief phrase that explains what a button does; for guidance, see [Offering help](https://developer.apple.com/design/human-interface-guidelines/offering-help).
+
+**Try to associate familiar actions with familiar icons.** For example, people can predict that a button containing the `square.and.arrow.up` symbol will help them perform share-related activities. If it makes sense to use an icon in your button, consider using an existing or customized [symbol](https://developer.apple.com/design/human-interface-guidelines/sf-symbols). For a list of symbols that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons).
+
+**Consider using text when a short label communicates more clearly than an icon.** To use text, write a few words that succinctly describe what the button does. Using [title-style capitalization](https://help.apple.com/applestyleguide/#/apsgb744e4a3?sub=apdca93e113f1d64), consider starting the label with a verb to help convey the button’s action — for example, a button that lets people add items to their shopping cart might use the label “Add to Cart.”
+
+## [Role](https://developer.apple.com/design/human-interface-guidelines/buttons#Role)
+
+A system button can have one of the following roles:
+
+ * **Normal.** No specific meaning.
+
+ * **Primary.** The button is the default button — the button people are most likely to choose.
+
+ * **Cancel.** The button cancels the current action.
+
+ * **Destructive.** The button performs an action that can result in data destruction.
+
+
+
+
+A button’s role can have additional effects on its appearance. For example, a primary button uses an app’s accent color, whereas a destructive button uses the system red color.
+
+
+
+**Assign the primary role to the button people are most likely to choose.** When a primary button responds to the Return key, it makes it easy for people to quickly confirm their choice. In addition, when the button is in a temporary view — like a [sheet](https://developer.apple.com/design/human-interface-guidelines/sheets), an editable view, or an [alert](https://developer.apple.com/design/human-interface-guidelines/alerts) — assigning it the primary role means that the view can automatically close when people press Return.
+
+**Don’t assign the primary role to a button that performs a destructive action, even if that action is the most likely choice.** Because of its visual prominence, people sometimes choose a primary button without reading it first. Help people avoid losing content by assigning the primary role to nondestructive buttons.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/buttons#Platform-considerations)
+
+ _No additional considerations for tvOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/buttons#iOS-iPadOS)
+
+**Configure a button to display an activity indicator when you need to provide feedback about an action that doesn’t instantly complete.** Displaying an activity indicator within a button can save space in your user interface while clearly communicating the reason for the delay. To help clarify what’s happening, you can also configure the button to display a different label alongside the activity indicator. For example, the label “Checkout” could change to “Checking out…” while the activity indicator is visible. When a delay occurs after people click or tap your configured button, the system displays the activity indicator next to the original or alternative label, hiding the button image, if there is one.
+
+
+
+
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/buttons#macOS)
+
+Several specific button types are unique to macOS.
+
+#### [Push buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Push-buttons)
+
+The standard button type in macOS is known as a _push button_. You can configure a push button to display text, a symbol, an icon, or an image, or a combination of text and image content. Push buttons can act as the default button in a view and you can tint them.
+
+**Use a flexible-height push button only when you need to display tall or variable height content.** Flexible-height buttons support the same configurations as regular push buttons — and they use the same corner radius and content padding — so they look consistent with other buttons in your interface. If you need to present a button that contains two lines of text or a tall icon, use a flexible-height button; otherwise, use a standard push button. For developer guidance, see [`NSButton.BezelStyle.flexiblePush`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/flexiblePush).
+
+**Append a trailing ellipsis to the title when a push button opens another window, view, or app.** Throughout the system, an ellipsis in a control title signals that people can provide additional input. For example, the Edit buttons in the AutoFill pane of Safari Settings include ellipses because they open other views that let people modify autofill values.
+
+**Consider supporting spring loading.** On systems with a Magic Trackpad, _spring loading_ lets people activate a button by dragging selected items over it and force clicking — that is, pressing harder — without dropping the selected items. After force clicking, people can continue dragging the items, possibly to perform additional actions.
+
+#### [Square buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Square-buttons)
+
+A _square button_ (also known as a _gradient button_) initiates an action related to a view, like adding or removing rows in a table.
+
+Square buttons contain symbols or icons — not text — and you can configure them to behave like push buttons, toggles, or pop-up buttons. The buttons appear in close proximity to their associated view — usually within or beneath it — so people know which view the buttons affect.
+
+**Use square buttons in a view, not in the window frame.** Square buttons aren’t intended for use in toolbars or status bars. If you need a button in a [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars), use a toolbar item.
+
+**Prefer using a symbol in a square button.** [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) provides a wide range of symbols that automatically receive appropriate coloring in their default state and in response to user interaction.
+
+**Avoid using labels to introduce square buttons.** Because square buttons are closely connected with a specific view, their purpose is generally clear without the need for descriptive text.
+
+For developer guidance, see [`NSButton.BezelStyle.smallSquare`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/smallSquare).
+
+#### [Help buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Help-buttons)
+
+A _help button_ appears within a view and opens app-specific help documentation.
+
+Help buttons are circular, consistently sized buttons that contain a question mark. For guidance on creating help documentation, see [Offering help](https://developer.apple.com/design/human-interface-guidelines/offering-help).
+
+**Use the system-provided help button to display your help documentation.** People are familiar with the appearance of the standard help button and know that choosing it opens help content.
+
+**When possible, open the help topic that’s related to the current context.** For example, the help button in the Rules pane of Mail settings opens the Mail User Guide to a help topic that explains how to change these settings. If no specific help topic applies directly to the current context, open the top level of your app’s help documentation when people choose a help button.
+
+**Include no more than one help button per window.** Multiple help buttons in the same context make it hard for people to predict the result of clicking one.
+
+**Position help buttons where people expect to find them.** Use the following locations for guidance.
+
+View style| Help button location
+---|---
+Dialog with dismissal buttons (like OK and Cancel)| Lower corner, opposite to the dismissal buttons and vertically aligned with them
+Dialog without dismissal buttons| Lower-left or lower-right corner
+Settings window or pane| Lower-left or lower-right corner
+
+**Use a help button within a view, not in the window frame.** For example, avoid placing a help button in a toolbar or status bar.
+
+**Avoid displaying text that introduces a help button.** People know what a help button does, so they don’t need additional descriptive text.
+
+#### [Image buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#Image-buttons)
+
+An _image button_ appears in a view and displays an image, symbol, or icon. You can configure an image button to behave like a push button, toggle, or pop-up button.
+
+**Use an image button in a view, not in the window frame.** For example, avoid placing an image button in a toolbar or status bar. If you need to use an image as a button in a toolbar, use a toolbar item. See [Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars).
+
+**Include about 10 pixels of padding between the edges of the image and the button edges.** An image button’s edges define its clickable area even when they aren’t visible. Including padding ensures that a click registers correctly even if it’s not precisely within the image. In general, avoid including a system-provided border in an image button; for developer guidance, see [`isBordered`](https://developer.apple.com/documentation/AppKit/NSButton/isBordered).
+
+**If you need to include a label, position it below the image button.** For related guidance, see [Labels](https://developer.apple.com/design/human-interface-guidelines/labels).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/buttons#visionOS)
+
+A visionOS button typically includes a visible background that can help people see it, and the button plays sound to provide feedback when people interact with it.
+
+Video with custom controls.
+
+Content description: A recording showing the top portion of a window in visionOS. The window contains several buttons, including a 'More' button, which receives the hover effect. The button is selected and a menu containing additional options appears.
+
+Play
+
+There are three standard button shapes in visionOS. Typically, an icon-only button uses a [`circle`](https://developer.apple.com/documentation/SwiftUI/ButtonBorderShape/circle) shape, a text-only button uses a [`roundedRectangle`](https://developer.apple.com/documentation/SwiftUI/ButtonBorderShape/roundedRectangle) or [`capsule`](https://developer.apple.com/documentation/SwiftUI/ButtonBorderShape/capsule) shape, and a button that includes both an icon and text uses the capsule shape.
+
+visionOS buttons use different visual styles to communicate four different interaction states.
+
+Idle
+
+Hover
+
+Selected
+
+Unavailable
+
+Note
+
+In visionOS, buttons don’t support custom hover effects.
+
+In addition to the four states shown above, a button can also reveal a tooltip when people look at it for a brief time. In general, buttons that contain text don’t need to display a tooltip because the button’s descriptive label communicates what it does.
+
+Video with custom controls.
+
+Content description: An animation showing a tooltip appearing beneath a visionOS button.
+
+Play
+
+In visionOS, buttons can have the following sizes.
+
+Shape| Mini (28 pt)| Small (32 pt)| Regular (44 pt)| Large (52 pt)| Extra large (64 pt)
+---|---|---|---|---|---
+Circular| | | | | 
+Capsule (text only)| | | | |
+Capsule (text and icon)| | | | |
+Rounded rectangle| | | | |
+
+**Prefer buttons that have a discernible background shape and fill.** It tends to be easier for people to see a button when it’s enclosed in a shape that uses a contrasting background fill. The exception is a button in a toolbar, context menu, alert, or [ornament](https://developer.apple.com/design/human-interface-guidelines/ornaments) where the shape and material of the larger component make the button comfortably visible. The following guidelines can help you ensure that a button looks good in different contexts:
+
+ * When a button appears on top of a glass [window](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS), use the [`thin`](https://developer.apple.com/documentation/SwiftUI/Material/thin) material as the button’s background.
+
+ * When a button appears floating in space, use the [glass material](https://developer.apple.com/design/human-interface-guidelines/materials#visionOS) for its background.
+
+
+
+
+**Avoid creating a custom button that uses a white background fill and black text or icons.** The system reserves this visual style to convey the toggled state.
+
+**In general, prefer circular or capsule-shape buttons.** People’s eyes tend to be drawn toward the corners in a shape, making it difficult to keep looking at the shape’s center. The more rounded a button’s shape, the easier it is for people to look steadily at it. When you need to display a button by itself, prefer a capsule-shape button.
+
+**Provide enough space around a button to make it easy for people to look at it.** Aim to place buttons so their centers are always at least 60 pts apart. If your buttons measure 60 pts or larger, add 4 pts of padding around them to keep the hover effect from overlapping. Also, it’s usually best to avoid displaying small or mini buttons in a vertical stack or horizontal row.
+
+**Choose the right shape if you need to display text-labeled buttons in a stack or row.** Specifically, prefer the rounded-rectangle shape in a vertical stack of buttons and prefer the capsule shape in a horizontal row of buttons.
+
+**Use standard controls to take advantage of the audible feedback sounds people already know.** Audible feedback is especially important in visionOS, because the system doesn’t play haptics.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/buttons#watchOS)
+
+watchOS displays all inline buttons using the [`capsule`](https://developer.apple.com/documentation/SwiftUI/ButtonBorderShape/capsule) button shape. When you place a button inline with content, it gains a material effect that contrasts with the background to ensure legibility.
+
+
+
+**Use a toolbar to place buttons in the corners.** The system automatically moves the time and title to accommodate toolbar buttons. The system also applies the [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) appearance to toolbar buttons, providing a clear visual distinction from the content beneath them.
+
+
+
+**Prefer buttons that span the width of the screen for primary actions in your app.** Full-width buttons look better and are easier for people to tap. If two buttons must share the same horizontal space, use the same height for both, and use images or short text titles for each button’s content.
+
+**Use toolbar buttons to provide either navigation to related areas or contextual actions for the view’s content.** These buttons provide access to additional information or secondary actions for the view’s content.
+
+**Use the same height for vertical stacks of one- and two-line text buttons.** As much as possible, use identical button heights for visual consistency.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/buttons#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/buttons#Related)
+
+[Pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+[Toggles](https://developer.apple.com/design/human-interface-guidelines/toggles)
+
+[Segmented controls](https://developer.apple.com/design/human-interface-guidelines/segmented-controls)
+
+[Location button](https://developer.apple.com/design/human-interface-guidelines/privacy#Location-button)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/buttons#Developer-documentation)
+
+[`Button`](https://developer.apple.com/documentation/SwiftUI/Button) — SwiftUI
+
+[`UIButton`](https://developer.apple.com/documentation/UIKit/UIButton) — UIKit
+
+[`NSButton`](https://developer.apple.com/documentation/AppKit/NSButton) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/buttons#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for Liquid Glass.
+June 9, 2025| Updated guidance for button styles and content.
+February 2, 2024| Noted that visionOS buttons don’t support custom hover effects.
+December 5, 2023| Clarified some terminology and guidance for buttons in visionOS.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance for using buttons in watchOS.
+
diff --git a/web-app/public/skills/hig-components-menus/references/context-menus.md b/web-app/public/skills/hig-components-menus/references/context-menus.md
new file mode 100644
index 00000000..585a3731
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/context-menus.md
@@ -0,0 +1,105 @@
+---
+title: "Context menus | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/context-menus
+
+# Context menus
+
+A context menu provides access to functionality that’s directly related to an item, without cluttering the interface.
+
+
+
+Although a context menu provides convenient access to frequently used items, it’s hidden by default, so people might not know it’s there. To reveal a context menu, people generally choose a view or select some content and then perform an action, using the input modes their current configuration supports. For example:
+
+ * The system-defined touch or pinch and hold gesture in visionOS, iOS, and iPadOS
+
+ * Pressing the Control key while clicking a pointing device in macOS and iPadOS
+
+ * Using a secondary click on a Magic Trackpad in macOS or iPadOS
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/context-menus#Best-practices)
+
+**Prioritize relevancy when choosing items to include in a context menu.** A context menu isn’t for providing advanced or rarely used items; instead, it helps people quickly access the commands they’re most likely to need in their current context. For example, the context menu for a Mail message in the Inbox includes commands for replying and moving the message, but not commands for editing message content, managing mailboxes, or filtering messages.
+
+**Aim for a small number of menu items.** A context menu that’s too long can be difficult to scan and scroll.
+
+**Support context menus consistently throughout your app.** If you provide context menus for items in some places but not in others, people won’t know where they can use the feature and may think there’s a problem.
+
+**Always make context menu items available in the main interface, too.** For example, in Mail in iOS and iPadOS, the context menu items that are available for a message in the Inbox are also available in the toolbar of the message view. In macOS, an app’s menu bar menus list all the app’s commands, including those in various context menus.
+
+**If you need to use submenus to manage a menu’s complexity, keep them to one level.** A submenu is a menu item that reveals a secondary menu of logically related commands. Although submenus can shorten a context menu and clarify its commands, more than one level of submenu complicates the experience and can be difficult for people to navigate. If you need to include a submenu, give it an intuitive title that helps people predict its contents without opening it. For guidance, see [Submenus](https://developer.apple.com/design/human-interface-guidelines/menus#Submenus).
+
+**Hide unavailable menu items, don’t dim them.** Unlike a regular menu, which helps people discover actions they can perform even when the action isn’t available, a context menu displays only the actions that are relevant to the currently selected view or content. In macOS, the exceptions are the Cut, Copy, and Paste menu items, which may appear unavailable if they don’t apply to the current context.
+
+**Aim to place the most frequently used menu items where people are likely to encounter them first.** When a context menu opens, people often read it starting from the part that’s closest to where their finger or pointer revealed it. Depending on the location of the selected content, a context menu might open above or below it, so you might also need to reverse the order of items to match the position of the menu.
+
+**Show keyboard shortcuts in your app’s main menus, not in context menus.** Context menus already provide a shortcut to task-specific commands, so it’s redundant to display keyboard shortcuts too.
+
+**Follow best practices for using separators.** As with other types of menus, you can use separators to group items in a context menu and help people scan the menu more quickly. In general, you don’t want more than about three groups in a context menu. For guidance, see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+**In iOS, iPadOS, and visionOS, warn people about context menu items that can destroy data.** If you need to include potentially destructive items in your context menu — such as Delete or Remove — list them at the end of the menu and identify them as destructive (for developer guidance, see [`destructive`](https://developer.apple.com/documentation/UIKit/UIMenuElement/Attributes/destructive)). The system can display a destructive menu item using a red text color.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/context-menus#Content)
+
+A context menu seldom displays a title. In contrast, each item in a context menu needs to display a short label that clearly describes what it does. For guidance, see [Menus > Labels](https://developer.apple.com/design/human-interface-guidelines/menus#Labels).
+
+**Include a title in a context menu only if doing so clarifies the menu’s effect.** For example, when people select multiple Mail messages and tap the Mark toolbar button in iOS and iPadOS, the resulting context menu displays a title that states the number of selected messages, reminding people that the command they choose affects all the messages they selected.
+
+**Represent menu item actions with familiar icons.** Icons help people recognize common actions throughout your app. Use the same icons as the system to represent actions such as Copy, Share, and Delete, wherever they appear. For a list of icons that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons). For additional guidance, see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/context-menus#Platform-considerations)
+
+ _No additional considerations for tvOS. Not supported in watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/context-menus#iOS-iPadOS)
+
+**Provide either a context menu or an edit menu for an item, but not both.** If you provide both features for the same item, it can be confusing to people — and difficult for the system to detect their intent. See [Edit menus](https://developer.apple.com/design/human-interface-guidelines/edit-menus).
+
+**In iPadOS, consider using a context menu to let people create a new object in your app.** iPadOS lets you reveal a context menu when people perform a long press on the touchscreen or use a secondary click with an attached trackpad or keyboard. For example, Files lets people create a new folder by revealing a context menu in an area between existing files and folders.
+
+In iOS and iPadOS, a context menu can display a preview of the current content near the list of commands. People can choose a command in the menu or — in some cases — they can tap the preview to open it or drag it to another area.
+
+**Prefer a graphical preview that clarifies the target of a context menu’s commands.** For example, when people reveal a context menu on a list item in Notes or Mail, the preview shows a condensed version of the actual content to help people confirm that they’re working with the item they intend.
+
+**Ensure that your preview looks good as it animates.** As people reveal a context menu on an onscreen object, the system animates the preview image as it emerges from the content, dimming the screen behind the preview and the menu. It’s important to adjust the preview’s clipping path to match the shape of the preview image so that its contours, such as the rounded corners, don’t appear to change during animation. For developer guidance, see [`UIContextMenuInteractionDelegate`](https://developer.apple.com/documentation/UIKit/UIContextMenuInteractionDelegate).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/context-menus#macOS)
+
+On a Mac, a context menu is sometimes called a _contextual_ menu.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/context-menus#visionOS)
+
+**Consider using a context menu instead of a panel or inspector window to present frequently used functionality.** Minimizing the number of separate views or windows your app opens can help people keep their space uncluttered.
+
+**In general, avoid letting a context menu’s height exceed the height of the window.** In visionOS, a window includes system-provided components above and below its top and bottom edges, such as window-management controls and the Share menu, so a context menu that’s too tall could obscure them. As you consider the number of items to include, be guided by the ways people are likely to use your app. For example, people who use an app to accomplish in-depth, specialist tasks often expect to spend time learning a large number of sophisticated commands and might appreciate contextual access to them. On the other hand, people who use an app to perform a few simple actions may appreciate short contextual menus that are quick to scan and use.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/context-menus#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/context-menus#Related)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+[Edit menus](https://developer.apple.com/design/human-interface-guidelines/edit-menus)
+
+[Pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/context-menus#Developer-documentation)
+
+[`contextMenu(menuItems:)`](https://developer.apple.com/documentation/SwiftUI/View/contextMenu\(menuItems:\)) — SwiftUI
+
+[`UIContextMenuInteraction`](https://developer.apple.com/documentation/UIKit/UIContextMenuInteraction) — UIKit
+
+[`popUpContextMenu(_:with:for:)`](https://developer.apple.com/documentation/AppKit/NSMenu/popUpContextMenu\(_:with:for:\)) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/context-menus#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Added guidance on hiding unavailable menu items.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Refined guidance on including a submenu and added a guideline on using a context menu to support object creation in an iPadOS app.
+
diff --git a/web-app/public/skills/hig-components-menus/references/disclosure-controls.md b/web-app/public/skills/hig-components-menus/references/disclosure-controls.md
new file mode 100644
index 00000000..bd483286
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/disclosure-controls.md
@@ -0,0 +1,84 @@
+---
+title: "Disclosure controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/disclosure-controls
+
+# Disclosure controls
+
+Disclosure controls reveal and hide information and functionality related to specific controls or views.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Best-practices)
+
+**Use a disclosure control to hide details until they’re relevant.** Place controls that people are most likely to use at the top of the disclosure hierarchy so they’re always visible, with more advanced functionality hidden by default. This organization helps people quickly find the most essential information without overwhelming them with too many detailed options.
+
+## [Disclosure triangles](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Disclosure-triangles)
+
+A disclosure triangle shows and hides information and functionality associated with a view or a list of items. For example, Keynote uses a disclosure triangle to show advanced options when exporting a presentation, and the Finder uses disclosure triangles to progressively reveal hierarchy when navigating a folder structure in list view.
+
+ * Collapsed
+ * Expanded
+
+
+
+
+
+
+
+A disclosure triangle points inward from the leading edge when its content is hidden and down when its content is visible. Clicking or tapping the disclosure triangle switches between these two states, and the view expands or collapses accordingly to accommodate the content.
+
+**Provide a descriptive label when using a disclosure triangle.** Make sure your labels indicate what is disclosed or hidden, like “Advanced Options.”
+
+For developer guidance, see [`NSButton.BezelStyle.disclosure`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/disclosure).
+
+## [Disclosure buttons](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Disclosure-buttons)
+
+A disclosure button shows and hides functionality associated with a specific control. For example, the macOS Save sheet shows a disclosure button next to the Save As text field. When people click or tap this button, the Save dialog expands to give advanced navigation options for selecting an output location for their document.
+
+A disclosure button points down when its content is hidden and up when its content is visible. Clicking or tapping the disclosure button switches between these two states, and the view expands or collapses accordingly to accommodate the content.
+
+ * Collapsed
+ * Expanded
+
+
+
+
+
+
+
+**Place a disclosure button near the content that it shows and hides.** Establish a clear relationship between the control and the expanded choices that appear when a person clicks or taps a button.
+
+**Use no more than one disclosure button in a single view.** Multiple disclosure buttons add complexity and can be confusing.
+
+For developer guidance, see [`NSButton.BezelStyle.pushDisclosure`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/pushDisclosure).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Platform-considerations)
+
+ _No additional considerations for macOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS, visionOS](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#iOS-iPadOS-visionOS)
+
+Disclosure controls are available in iOS, iPadOS, and visionOS with the SwiftUI [`DisclosureGroup`](https://developer.apple.com/documentation/SwiftUI/DisclosureGroup) view.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Related)
+
+[Outline views](https://developer.apple.com/design/human-interface-guidelines/outline-views)
+
+[Lists and tables](https://developer.apple.com/design/human-interface-guidelines/lists-and-tables)
+
+[Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Developer-documentation)
+
+[`DisclosureGroup`](https://developer.apple.com/documentation/SwiftUI/DisclosureGroup) — SwiftUI
+
+[`NSButton.BezelStyle.disclosure`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/disclosure) — AppKit
+
+[`NSButton.BezelStyle.pushDisclosure`](https://developer.apple.com/documentation/AppKit/NSButton/BezelStyle-swift.enum/pushDisclosure) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls#Videos)
+
+[ Stacks, Grids, and Outlines in SwiftUI ](https://developer.apple.com/videos/play/wwdc2020/10031)
+
diff --git a/web-app/public/skills/hig-components-menus/references/dock-menus.md b/web-app/public/skills/hig-components-menus/references/dock-menus.md
new file mode 100644
index 00000000..180f83bf
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/dock-menus.md
@@ -0,0 +1,40 @@
+---
+title: "Dock menus | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/dock-menus
+
+# Dock menus
+
+On a Mac, people can secondary click an app’s or game’s icon in the Dock to reveal a Dock menu, which presents both system-provided and custom items.
+
+
+
+The system-provided Dock menu items can vary depending on whether the app is open. For example, the Dock menu for Safari includes menu items for actions like viewing a current window or creating a new window.
+
+Note
+
+Although iOS and iPadOS don’t support a Dock menu, people can reveal a similar menu of system-provided and custom items — called Home Screen quick actions — when they long press an app icon on the Home Screen or in the Dock. For guidance, see [Home Screen quick actions](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/dock-menus#Best-practices)
+
+As with all menus, you need to label Dock menu items succinctly and organize them logically. For guidance, see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+**Make custom Dock menu items available in other places, too.** Not everyone uses a Dock menu, so it’s important to offer the same commands elsewhere, like in your menu bar menus or within your interface.
+
+**Prefer high-value custom items for your Dock menu.** For example, a Dock menu can list all currently or recently open windows, making it a convenient way to jump to the window people want. Also consider listing a few of the actions that are most likely to be useful when your app isn’t frontmost or when there are no open windows. For example, Mail includes items for getting new mail and composing a new message in addition to listing all open windows.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/dock-menus#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/dock-menus#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/dock-menus#Related)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+[Home Screen quick actions](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/dock-menus#Developer-documentation)
+
+[`applicationDockMenu(_:)`](https://developer.apple.com/documentation/AppKit/NSApplicationDelegate/applicationDockMenu\(_:\)) — AppKit
+
diff --git a/web-app/public/skills/hig-components-menus/references/edit-menus.md b/web-app/public/skills/hig-components-menus/references/edit-menus.md
new file mode 100644
index 00000000..56d10e7a
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/edit-menus.md
@@ -0,0 +1,88 @@
+---
+title: "Edit menus | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/edit-menus
+
+# Edit menus
+
+An edit menu lets people make changes to selected content in the current view, in addition to offering related commands like Copy, Select, Translate, and Look Up.
+
+
+
+In addition to text, an edit menu’s commands can apply to many types of selectable content, such as images, files, and objects like contact cards, charts, or map locations. In iOS, iPadOS, and visionOS, the system automatically detects the data type of a selected item, which can result in the addition of a related action to the edit menu. For example, selecting an address can add an item like _Get directions_ to the edit menu.
+
+Edit menus can look and behave slightly differently in different platforms.
+
+ * In iOS, the edit menu displays commands in a compact, horizontal list that appears when people touch and hold or double-tap to select content in a view. People can tap a chevron on the trailing edge to expand it into a [context menu](https://developer.apple.com/design/human-interface-guidelines/context-menus).
+
+ * In iPadOS, the edit menu looks different depending on how people reveal it. When people use touch interactions to reveal the menu, it uses the compact, horizontal appearance. In contrast, when people use a keyboard or pointing device to reveal it, the edit menu opens directly in a context menu.
+
+ * In macOS, people can access editing commands in a context menu they can reveal while in an editing task, as well as through the app’s [Edit menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Edit-menu) in the menu bar.
+
+ * In visionOS, people use the standard [pinch and hold](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures) gesture to open the edit menu as a horizontal bar, or they can open it in a context menu.
+
+
+
+
+Editing content is rare in tvOS and watchOS experiences, so the system doesn’t provide an edit menu in these platforms.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Best-practices)
+
+**Prefer the system-provided edit menu.** People are familiar with the contents and behavior of the system-provided component, so creating a custom menu that presents the same commands is redundant and likely to be confusing. For a list of standard edit menu commands, see [`UIResponderStandardEditActions`](https://developer.apple.com/documentation/UIKit/UIResponderStandardEditActions).
+
+**Let people reveal an edit menu using the system-defined interactions they already know.** For example, people expect to touch and hold on a touchscreen, pinch and hold in visionOS, or use a secondary click with an attached trackpad or keyboard. Although the interactions to reveal an edit menu can differ based on platform, people don’t appreciate having to learn a custom interaction to perform a standard task.
+
+**Offer commands that are relevant in the current context, removing or dimming commands that don’t apply.** For example, if nothing is selected, avoid showing options that require a selection, such as Copy or Cut. Similarly, avoid showing a Paste option when there’s nothing to paste.
+
+**List custom commands near relevant system-provided ones.** For example, if you offer custom formatting commands, you can help maintain the ordering people expect by listing them after the system-provided commands in the format section. Avoid overwhelming people with too many custom commands.
+
+**When it makes sense, let people select and copy noneditable text.** People appreciate being able to paste static content — such as an image caption or social media status — into a message, note, or web search. In general, let people copy content text, but not control labels.
+
+**Support undo and redo when possible.** Like all menus, an edit menu doesn’t require confirmation before performing its actions, so people can easily use undo and redo to recover a previous state. For guidance, see [Undo and redo](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo).
+
+**In general, avoid implementing other controls that perform the same functions as edit menu items.** People typically expect to choose familiar edit commands in an edit menu, or use standard keyboard shortcuts. Offering redundant controls can crowd your interface, giving you less space for presenting actions that people might not already know about.
+
+**Differentiate different types of deletion commands when necessary.** For example, a Delete menu item behaves the same as pressing a Delete key, but a Cut menu item copies the selected content to the system pasteboard before deleting it.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Content)
+
+**Create short labels for custom commands.** Use verbs or short verb phrases that succinctly describe the action your command performs. For guidance, see [Labels](https://developer.apple.com/design/human-interface-guidelines/labels).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Platform-considerations)
+
+ _No additional considerations for visionOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/edit-menus#iOS-iPadOS)
+
+**Ensure your edit menu works well in both styles.** The system displays the compact, horizontal style when people use Multi-Touch gestures to reveal the edit menu, and the vertical style when people use a keyboard or pointing device to reveal it. For guidance using the vertical menu layout, see [Menus > iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/menus#iOS-iPadOS).
+
+**Adjust an edit menu’s placement, if necessary.** Depending on available space, the default menu position is above or below the insertion point or selection. The system also displays a visual indicator that points to the targeted content. Although you can’t change the shape of the menu or its pointer, you can change the menu’s position. For example, you might need to move the menu to prevent it from covering important content or parts of your interface.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/edit-menus#macOS)
+
+To learn about the order of items in a macOS app’s Edit menu, see [Edit menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Edit-menu).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Related)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+[Context menus](https://developer.apple.com/design/human-interface-guidelines/context-menus)
+
+[The menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar)
+
+[Undo and redo](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Developer-documentation)
+
+[`UIEditMenuInteraction`](https://developer.apple.com/documentation/UIKit/UIEditMenuInteraction) — UIKit
+
+[`NSMenu`](https://developer.apple.com/documentation/AppKit/NSMenu) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/edit-menus#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Added guidance on supporting both edit-menu styles in iPadOS.
+
diff --git a/web-app/public/skills/hig-components-menus/references/menus.md b/web-app/public/skills/hig-components-menus/references/menus.md
new file mode 100644
index 00000000..58fd3d3b
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/menus.md
@@ -0,0 +1,171 @@
+---
+title: "Menus | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/menus
+
+# Menus
+
+A menu reveals its options when people interact with it, making it a space-efficient way to present commands in your app or game.
+
+
+
+Menus are ubiquitous in apps and games, so most people already know how to use them. Whether you use system-provided components or custom ones, people expect menus to behave in familiar ways. For example, people understand that opening a menu reveals one or more _menu items_ , each of which represents a command, option, or state that affects the current selection or context. The guidance for labeling and organizing menu items applies to all types of menus in all experiences.
+
+Note
+
+Several system-provided components also include menus that support specific use cases. For example, a [pop-up button](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons) or [pull-down button](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons) can reveal a menu of options directly related to its action; a [context menu](https://developer.apple.com/design/human-interface-guidelines/context-menus) lets people access a small number of frequently used actions relevant to their current view or task; and in macOS and iPadOS, [menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar) menus contain all the commands people can perform in the app or game.
+
+## [Labels](https://developer.apple.com/design/human-interface-guidelines/menus#Labels)
+
+A menu item’s label describes what it does and may include a symbol if it helps to clarify meaning. In an app, a menu item can also display the associated keyboard command, if there is one; in a game, a menu item rarely displays a keyboard command because a game typically needs to handle input from a wider range of devices and may offer game-specific mappings for various keys.
+
+Note
+
+Depending on menu layout, an iOS, iPadOS, or visionOS app can display a few unlabeled menu items that use only symbols or icons to identify them. For guidance, see [visionOS](https://developer.apple.com/design/human-interface-guidelines/menus#visionOS) and [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/menus#iOS-iPadOS).
+
+**For each menu item, write a label that clearly and succinctly describes it.** In general, label a menu item that initiates an action using a verb or verb phrase that describes the action, such as View, Close, or Select. For guidance labeling menu items that show and hide something in the interface or show the currently selected state of something, see [Toggled items](https://developer.apple.com/design/human-interface-guidelines/menus#Toggled-items). As with all the copy you write, let your app’s or game’s communication style guide the tone of the menu-item labels you create.
+
+**To be consistent with platform experiences, use title-style capitalization.** Although a game might have a different writing style, generally prefer using title-style capitalization, which capitalizes every word except articles, coordinating conjunctions, and short prepositions, and capitalizes the last word in the label, regardless of the part of speech. For complete guidance on this style of capitalization in English, see [title-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64).
+
+**Remove articles like _a_ , _an_ , and _the_ from menu-item labels to save space.** In English, articles always lengthen labels, but rarely enhance understanding. For example, changing a menu-item label from View Settings to View the Settings doesn’t provide additional clarification.
+
+**Show people when a menu item is unavailable.** An unavailable menu item often appears dimmed and doesn’t respond to interactions. If all of a menu’s items are unavailable, the menu itself needs to remain available so people can open it and learn about the commands it contains.
+
+**Append an ellipsis to a menu item’s label when the action requires more information before it can complete.** The ellipsis character (…) signals that people need to input information or make additional choices, typically within another view.
+
+## [Icons](https://developer.apple.com/design/human-interface-guidelines/menus#Icons)
+
+**Represent menu item actions with familiar icons.** Icons help people recognize common actions throughout your app. Use the same icons as the system to represent actions such as Copy, Share, and Delete, wherever they appear. For a list of icons that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons).
+
+**Don’t display an icon if you can’t find one that clearly represents the menu item.** Not all menu items need an icon. Be careful when adding icons for custom menu items to avoid confusion with other existing actions, and don’t add icons just for the sake of ornamentation.
+
+
+
+
+
+
+
+
+
+**Use a single icon to introduce a group of similar items.** Instead of adding individual icons for each action, or reusing the same icon for all of them, establish a common theme with the symbol for the first item and rely on the menu item text to keep the remaining items distinct.
+
+
+
+
+
+
+
+
+
+
+
+
+
+## [Organization](https://developer.apple.com/design/human-interface-guidelines/menus#Organization)
+
+Organizing menu items in ways that reflect how people use your app or game can make your experience feel straightforward and easy to use.
+
+**Prefer listing important or frequently used menu items first.** People tend to start scanning a menu from the top, so listing high-priority items first often means that people can find what they want without reading the entire menu.
+
+**Consider grouping logically related items.** For example, grouping editing commands like Copy, Cut, and Paste or camera commands like Look Up, Look Down, and Look Left can help people remember where to find them. To help people visually distinguish such groups, use a separator. Depending on the platform and type of menu, a _separator_ appears between groups of items as a horizontal line or a short gap in the menu’s background appearance.
+
+**Prefer keeping all logically related commands in the same group, even if the commands don’t all have the same importance.** For example, people generally use Paste and Match Style much less often than they use Paste, but they expect to find both commands in the same group that contains more frequently used editing commands like Copy and Cut.
+
+**Be mindful of menu length.** People need more time and attention to read a long menu, which means they may miss the command they want. If a menu is too long, consider dividing it into separate menus. Alternatively, you might be able to use a submenu to shorten the list, such as listing difficulty levels in a submenu of a New Game menu item. The exception is when a menu contains user-defined or dynamically generated content, like the History and Bookmarks menus in Safari. People expect such a menu to accommodate all the items they add to it, so a long menu is fine, and scrolling is acceptable.
+
+## [Submenus](https://developer.apple.com/design/human-interface-guidelines/menus#Submenus)
+
+Sometimes, a menu item can reveal a set of closely related items in a subordinate list called a _submenu_. A menu item indicates the presence of a submenu by displaying a symbol — like a chevron — after its label. Submenus are functionally identical to menus, aside from their hierarchical positioning.
+
+**Use submenus sparingly.** Each submenu adds complexity to the interface and hides the items it contains. You might consider creating a submenu when a term appears in more than two menu items in the same group. For example, instead of offering separate menu items for Sort by Date, Sort by Score, and Sort by Time, a game could present a menu item that uses a submenu to list the sorting options Date, Score, and Time. It generally works well to use the repeated term — in this case, _Sort by_ — in the menu item’s label to help people predict the contents of the submenu.
+
+**Limit the depth and length of submenus.** It can be difficult for people to reveal multiple levels of hierarchical submenus, so it’s generally best to restrict them to a single level. Also, if a submenu contains more than about five items, consider creating a new menu.
+
+**Make sure a submenu remains available even when its nested menu items are unavailable.** A submenu item — like all menu items — needs to let people open it and learn about the commands it contains.
+
+**Prefer using a submenu to indenting menu items.** Using indentation is inconsistent with the system and doesn’t clearly express the relationships between the menu items.
+
+## [Toggled items](https://developer.apple.com/design/human-interface-guidelines/menus#Toggled-items)
+
+Menu items often represent attributes or objects that people can turn on or off. If you want to avoid listing a separate menu item for each state, it can be efficient to create a single, toggled menu item that communicates the current state and lets people change it.
+
+**Consider using a changeable label that describes an item’s current state.** For example, instead of listing two menu items like Show Map and Hide Map, you could include one menu item whose label changes from Show Map to Hide Map, depending on whether the map is visible.
+
+**Include a verb if a changeable label isn’t clear enough.** For example, people might not know whether the changeable labels HDR On and HDR Off describe actions or states. If you needed to clarify that these items represent actions, you could add verbs to the labels, like Turn HDR On and Turn HDR Off.
+
+**If necessary, display both menu items instead of one toggled item.** Sometimes, it helps people to view both actions or states at the same time. For example, a game could list both Take Account Online and Take Account Offline items, so when someone’s account is online, only the Take Account Offline menu item appears available.
+
+**Consider using a checkmark to show that an attribute is currently in effect.** It’s easy for people to scan for checkmarks in a list of attributes to find the ones that are selected. For example, in the standard Format > Font menu, checkmarks can make it easy for people notice the styles that apply to selected text.
+
+**Consider offering a menu item that makes it easy to remove multiple toggled attributes.** For example, if you let people apply several styles to selected text, it can work well to provide a menu item — such as Plain — that removes all applied formatting attributes at one time.
+
+## [In-game menus](https://developer.apple.com/design/human-interface-guidelines/menus#In-game-menus)
+
+In-game menus give players ways to control gameplay as well as determine [settings](https://developer.apple.com/design/human-interface-guidelines/settings) for the game as a whole.
+
+**Let players navigate in-game menus using the platform’s default interaction method.** People expect to use the same interactions to navigate your menus as they use for navigating other menus on the device. For example, players expect to navigate your game menus using touch in iOS and iPadOS, and direct and indirect gestures in visionOS.
+
+**Make sure your menus remain easy to open and read on all platforms you support.** Each platform defines specific sizes that work best for fonts and interaction targets. Sometimes, scaling your game content to display on a different screen — especially a mobile device screen — can make in-game menus too small for people to read or interact with. If this happens, modify the size of the tap targets and consider alternative ways to communicate the menu’s content. For guidance, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography) and [Touch controls](https://developer.apple.com/design/human-interface-guidelines/game-controls#Touch-controls).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/menus#Platform-considerations)
+
+ _No additional considerations for macOS, tvOS, or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/menus#iOS-iPadOS)
+
+In iOS and iPadOS, a menu can display items in one of the following three layouts.
+
+
+
+ * **Small.** A row of four items appears at the top of the menu, above a list that contains the remaining items. For each item in the top row, the menu displays a symbol or icon, but no label.
+
+ * **Medium.** A row of three items appears at the top of the menu, above a list that contains the remaining items. For each item in the top row, the menu displays a symbol or icon above a short label.
+
+ * **Large (the default).** The menu displays all items in a list.
+
+
+
+
+For developer guidance, see [`preferredElementSize`](https://developer.apple.com/documentation/UIKit/UIMenu/preferredElementSize).
+
+**Choose a small or medium menu layout when it can help streamline people’s choices.** Consider using the medium layout if your app has three important actions that people often want to perform. For example, Notes uses the medium layout to give people a quick way to perform the Scan, Lock, and Pin actions. Use the small layout only for closely related actions that typically appear as a group, such as Bold, Italic, Underline, and Strikethrough. For each action, use a recognizable symbol that helps people identify the action without a label.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/menus#visionOS)
+
+In visionOS, a menu can display items using the small or large layout styles that iOS and iPadOS define (for guidance, see [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/menus#iOS-iPadOS)). You can present a menu in your app or game from 3D content using a SwiftUI view. To ensure that your menu is always visible to people, even when other content occludes it, you can apply a [breakthrough effect](https://developer.apple.com/documentation/swiftui/view/presentationbreakthrougheffect\(_:\)). As in macOS, an open menu in a visionOS window can appear outside of the window’s boundaries.
+
+**Prefer displaying a menu near the content it controls.** Because people need to look at a menu item before tapping it, they might miss the item’s effect if the content it controls is too far away.
+
+
+
+**Prefer the subtle breakthrough effect in most cases.** This effect blends the presentation with its surrounding content, to maintain legibility and usability while preserving the depth and context of the scene. When you select [`automatic`](https://developer.apple.com/documentation/SwiftUI/BreakthroughEffect/automatic) for the breakthrough effect of a menu that overlaps with 3D content, the system applies [`subtle`](https://developer.apple.com/documentation/SwiftUI/BreakthroughEffect/subtle) by default. You can use [`prominent`](https://developer.apple.com/documentation/SwiftUI/BreakthroughEffect/prominent) if it’s important to display a menu prominently over the entire scene in your app or game, but this can disrupt the experience for people and potentially cause discomfort. Alternatively, you can use [`none`](https://developer.apple.com/documentation/SwiftUI/BreakthroughEffect/none) to fully occlude your menu behind other 3D content — for example, in a puzzle game that requires people to navigate around barriers — but this may make it difficult for people to see and access the menu.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/menus#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/menus#Related)
+
+[Pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+[Context menus](https://developer.apple.com/design/human-interface-guidelines/context-menus)
+
+[The menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/menus#Developer-documentation)
+
+[`Menu`](https://developer.apple.com/documentation/SwiftUI/Menu) — SwiftUI
+
+[Menus and shortcuts](https://developer.apple.com/documentation/UIKit/menus-and-shortcuts) — UIKit
+
+[Menus](https://developer.apple.com/documentation/AppKit/menus) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/menus#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Added guidance for presenting menus with breakthrough effects in visionOS.
+July 28, 2025| Added guidance for representing menu items with icons.
+June 10, 2024| Added guidance for in-game menus and included game-specific examples.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Added guidelines for using the small, medium, and large menu layouts in iPadOS.
+
diff --git a/web-app/public/skills/hig-components-menus/references/pop-up-buttons.md b/web-app/public/skills/hig-components-menus/references/pop-up-buttons.md
new file mode 100644
index 00000000..99521c67
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/pop-up-buttons.md
@@ -0,0 +1,70 @@
+---
+title: "Pop-up buttons | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons
+
+# Pop-up buttons
+
+A pop-up button displays a menu of mutually exclusive options.
+
+
+
+After people choose an item from a pop-up button’s menu, the menu closes, and the button can update its content to indicate the current selection.
+
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Best-practices)
+
+**Use a pop-up button to present a flat list of mutually exclusive options or states.** A pop-up button helps people make a choice that affects their content or the surrounding view. Use a [pull-down button](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons) instead if you need to:
+
+ * Offer a list of actions
+
+ * Let people select multiple items
+
+ * Include a submenu
+
+
+
+
+**Provide a useful default selection.** A pop-up button can update its content to identify the current selection, but if people haven’t made a selection yet, it shows the default item you specify. When possible, make the default selection an item that most people are likely to want.
+
+**Give people a way to predict a pop-up button’s options without opening it.** For example, you can use an introductory label or a button label that describes the button’s effect, giving context to the options.
+
+**Consider using a pop-up button when space is limited and you don’t need to display all options all the time.** Pop-up buttons are a space-efficient way to present a wide array of choices.
+
+**If necessary, include a Custom option in a pop-up button’s menu to provide additional items that are useful in some situations.** Offering a Custom option can help you avoid cluttering the interface with items or controls that people need only occasionally. You can also display explanatory text below the list to help people understand how the options work.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Platform-considerations)
+
+ _No additional considerations for iOS, macOS, or visionOS. Not supported in tvOS or watchOS._
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#iPadOS)
+
+**Within a popover or modal view, consider using a pop-up button instead of a disclosure indicator to present multiple options for a list item.** For example, people can quickly choose an option from the pop-up button’s menu without navigating to a detail view. Consider using a pop-up button in this scenario when you have a fairly small, well-defined set of options that work well in a menu.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Related)
+
+[Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons)
+
+[Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Developer-documentation)
+
+[`MenuPickerStyle`](https://developer.apple.com/documentation/SwiftUI/MenuPickerStyle) — SwiftUI
+
+[`changesSelectionAsPrimaryAction`](https://developer.apple.com/documentation/UIKit/UIButton/changesSelectionAsPrimaryAction) — UIKit
+
+[`NSPopUpButton`](https://developer.apple.com/documentation/AppKit/NSPopUpButton) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Added artwork.
+September 14, 2022| Added a guideline on using a pop-up button in a popover or modal view in iPadOS.
+
diff --git a/web-app/public/skills/hig-components-menus/references/pull-down-buttons.md b/web-app/public/skills/hig-components-menus/references/pull-down-buttons.md
new file mode 100644
index 00000000..46034f56
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/pull-down-buttons.md
@@ -0,0 +1,77 @@
+---
+title: "Pull-down buttons | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons
+
+# Pull-down buttons
+
+A pull-down button displays a menu of items or actions that directly relate to the button’s purpose.
+
+
+
+After people choose an item in a pull-down button’s menu, the menu closes, and the app performs the chosen action.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Best-practices)
+
+**Use a pull-down button to present commands or items that are directly related to the button’s action.** The menu lets you help people clarify the button’s target or customize its behavior without requiring additional buttons in your interface. For example:
+
+ * An Add button could present a menu that lets people specify the item they want to add.
+
+ * A Sort button could use a menu to let people select an attribute on which to sort.
+
+ * A Back button could let people choose a specific location to revisit instead of opening the previous one.
+
+
+
+
+If you need to provide a list of mutually exclusive choices that aren’t commands, use a [pop-up button](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons) instead.
+
+**Avoid putting all of a view’s actions in one pull-down button.** A view’s primary actions need to be easily discoverable, so you don’t want to hide them in a pull-down button that people have to open before they can do anything.
+
+**Balance menu length with ease of use.** Because people have to interact with a pull-down button before they can view its menu, listing a minimum of three items can help the interaction feel worthwhile. If you need to list only one or two items, consider using alternative components to present them, such as buttons to perform actions and toggles or switches to present selections. In contrast, listing too many items in a pull-down button’s menu can slow people down because it takes longer to find a specific item.
+
+**Display a succinct menu title only if it adds meaning.** In general, a pull-down button’s content — combined with descriptive menu items — provides all the context people need, making a menu title unnecessary.
+
+**Let people know when a pull-down button’s menu item is destructive, and ask them to confirm their intent.** Menus use red text to highlight actions that you identify as potentially destructive. When people choose a destructive action, the system displays an [action sheet](https://developer.apple.com/design/human-interface-guidelines/action-sheets) (iOS) or [popover](https://developer.apple.com/design/human-interface-guidelines/popovers) (iPadOS) in which they can confirm their choice or cancel the action. Because an action sheet appears in a different location from the menu and requires deliberate dismissal, it can help people avoid losing data by mistake.
+
+**Include an interface icon with a menu item when it provides value.** If you need to clarify an item’s meaning, you can display an [icon](https://developer.apple.com/design/human-interface-guidelines/icons) or image after its label. Using [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) for this purpose can help you provide a familiar experience while ensuring that the symbol remains aligned with the text at every scale.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Platform-considerations)
+
+ _No additional considerations for macOS or visionOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#iOS-iPadOS)
+
+Note
+
+You can also let people reveal a pull-down menu by performing a specific gesture on a button. For example, in iOS 14 and later, Safari responds to a touch and hold gesture on the Tabs button by displaying a menu of tab-related actions, like New Tab and Close All Tabs.
+
+**Consider using a More pull-down button to present items that don’t need prominent positions in the main interface.** A More button can help you offer a range of items where space is constrained, but it can also hinder discoverability. Although people generally understand that a More button offers additional functionality related to the current context, the ellipsis icon doesn’t necessarily help them predict its contents. To design an effective More button, weigh the convenience of its size against its impact on discoverability to find a balance that works in your app.
+
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Related)
+
+[Pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons)
+
+[Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Developer-documentation)
+
+[`MenuPickerStyle`](https://developer.apple.com/documentation/SwiftUI/MenuPickerStyle) — SwiftUI
+
+[`showsMenuAsPrimaryAction`](https://developer.apple.com/documentation/UIKit/UIControl/showsMenuAsPrimaryAction) — UIKit
+
+[`pullsDown`](https://developer.apple.com/documentation/AppKit/NSPopUpButton/pullsDown) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons#Change-log)
+
+Date| Changes
+---|---
+September 14, 2022| Refined guidance on designing a useful menu length.
+
diff --git a/web-app/public/skills/hig-components-menus/references/the-menu-bar.md b/web-app/public/skills/hig-components-menus/references/the-menu-bar.md
new file mode 100644
index 00000000..12e17d87
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/the-menu-bar.md
@@ -0,0 +1,303 @@
+---
+title: "The menu bar | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/the-menu-bar
+
+# The menu bar
+
+On a Mac or an iPad, the menu bar at the top of the screen displays the top-level menus in your app or game.
+
+
+
+Mac users are very familiar with the macOS menu bar, and they rely on it to help them learn what an app does and find the commands they need. To help your app or game feel at home in macOS, it’s essential to provide a consistent menu bar experience.
+
+Menu bar menus on iPad are similar to those on Mac, appearing in the same order and with familiar sets of menu items. When you adopt the menu structure that people expect from their experience on Mac, it helps them immediately understand and take advantage of the menu bar on iPad as well.
+
+Keyboard shortcuts in iPadOS use the same patterns as in macOS. For guidance, see [Standard keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Standard-keyboard-shortcuts).
+
+
+
+Menus in the menu bar share most of the appearance and behavior characteristics that all menu types have. To learn about menus in general — and how to organize and label menu items — see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Anatomy)
+
+When present in the menu bar, the following menus appear in the order listed below.
+
+ * _YourAppName_ (you supply a short version of your app’s name for this menu’s title)
+
+ * File
+
+ * Edit
+
+ * Format
+
+ * View
+
+ * App-specific menus, if any
+
+ * Window
+
+ * Help
+
+
+
+
+In addition, the macOS menu bar includes the Apple menu on the leading side and menu bar extras on the trailing side. See [macOS Platform considerations](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#macOS) for guidance.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Best-practices)
+
+**Support the default system-defined menus and their ordering.** People expect to find menus and menu items in an order they’re familiar with. In many cases, the system implements the functionality of standard menu items so you don’t have to. For example, when people select text in a standard text field, the system makes the Edit > Copy menu item available.
+
+**Always show the same set of menu items.** Keeping menu items visible helps people learn what actions your app supports, even if they’re unavailable in the current context. If a menu bar item isn’t actionable, disable the action instead of hiding it from the menu.
+
+**Represent menu item actions with familiar icons.** Icons help people recognize common actions throughout your app. Use the same icons as the system to represent actions such as Copy, Share, and Delete, wherever they appear. For a list of icons that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons). For additional guidance, see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+**Support the keyboard shortcuts defined for the standard menu items you include.** People expect to use the keyboard shortcuts they already know for standard menu items, like Copy, Cut, Paste, Save, and Print. Define custom keyboard shortcuts only when necessary. For guidance, see [Standard keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Standard-keyboard-shortcuts).
+
+**Prefer short, one-word menu titles.** Various factors — like different display sizes and the presence of menu bar extras — can affect the spacing and appearance of your menus. One-word menu titles work especially well in the menu bar because they take little space and are easy for people to scan. If you need to use more than one word in the menu title, use title-style capitalization.
+
+## [App menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#App-menu)
+
+The app menu lists items that apply to your app or game as a whole, rather than to a specific task, document, or window. To help people quickly identify the active app, the menu bar displays your app name in bold.
+
+The app menu typically contains the following menu items listed in the following order.
+
+Menu item| Action| Guidance
+---|---|---
+About _YourAppName_| Displays the About window for your app, which includes copyright and version information.| Prefer a short name of 16 characters or fewer. Don’t include a version number.
+Settings…| Opens your [settings](https://developer.apple.com/design/human-interface-guidelines/settings) window, or your app’s page in iPadOS Settings.| Use only for app-level settings. If you also offer document-specific settings, put them in the File menu.
+Optional app-specific items| Performs custom app-level setting or configuration actions.| List custom app-configuration items after the Settings item and within the same group.
+Services (macOS only)| Displays a submenu of services from the system and other apps that apply to the current context.|
+Hide _YourAppName_ (macOS only)| Hides your app and all of its windows, and then activates the most recently used app.| Use the same short app name you supply for the About item.
+Hide Others (macOS only)| Hides all other open apps and their windows.|
+Show All (macOS only)| Shows all other open apps and their windows behind your app’s windows.|
+Quit _YourAppName_| Quits your app. Pressing Option changes Quit _YourAppName_ to Quit and Keep Windows.| Use the same short app name you supply for the About item.
+
+**Display the About menu item first.** Include a separator after the About menu item so that it appears by itself in a group.
+
+## [File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu)
+
+The File menu contains commands that help people manage the files or documents an app supports. If your app doesn’t handle any types of files, you can rename or eliminate this menu.
+
+The File menu typically contains the following menu items listed in the following order.
+
+Menu item| Action| Guidance
+---|---|---
+New _Item_| Creates a new document, file, or window.| For _Item_ , use a term that names the type of item your app creates. For example, Calendar uses _Event_ and _Calendar_.
+Open| Can open the selected item or present an interface in which people select an item to open.| If people need to select an item in a separate interface, an ellipsis follows the command to indicate that more input is required.
+Open Recent| Displays a submenu that lists recently opened documents and files that people can select, and typically includes a _Clear Menu_ item.| List document and filenames that people recognize in the submenu; don’t display file paths. List the documents in the order people last opened them, with the most recently opened document first.
+Close| Closes the current window or document. Pressing Option changes Close to Close All. For a tab-based window, Close Tab replaces Close.| In a tab-based window, consider adding a Close Window item to let people close the entire window with one click or tap.
+Close Tab| Closes the current tab in a tab-based window. Pressing Option changes Close Tab to Close Other Tabs.|
+Close File| Closes the current file and all its associated windows.| Consider supporting this menu item if your app can open multiple views of the same file.
+Save| Saves the current document or file.| Automatically save changes periodically as people work so they don’t need to keep choosing File > Save. For a new document, prompt people for a name and location. If you need to let people save a file in multiple formats, prefer a pop-up menu that lets people choose a format in the Save sheet.
+Save All| Saves all open documents.|
+Duplicate| Duplicates the current document, leaving both documents open. Pressing Option changes Duplicate to Save As.| Prefer Duplicate to menu items like Save As, Export, Copy To, and Save To because these items don’t clarify the relationship between the original file and the new one.
+Rename…| Lets people change the name of the current document.|
+Move To…| Prompts people to choose a new location for the document.|
+Export As…| Prompts people for a name, output location, and export file format. After exporting the file, the current document remains open; the exported file doesn’t open.| Reserve the Export As item for when you need to let people export content in a format your app doesn’t typically handle.
+Revert To| When people turn on autosaving, displays a submenu that lists recent document versions and an option to display the version browser. After people choose a version to restore, it replaces the current document.|
+Page Setup…| Opens a panel for specifying printing parameters like paper size and printing orientation. A document can save the printing parameters that people specify.| Include the Page Setup item if you need to support printing parameters that apply to a specific document. Parameters that are global in nature, like a printer’s name, or that people change frequently, like the number of copies to print, belong in the Print panel.
+Print…| Opens the standard Print panel, which lets people print to a printer, send a fax, or save as a PDF.|
+
+## [Edit menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Edit-menu)
+
+The Edit menu lets people make changes to content in the current document or text container, and provides commands for interacting with the Clipboard. Because many editing commands apply to any editable content, the Edit menu is useful even in apps that aren’t document-based.
+
+**Determine whether Find menu items belong in the Edit menu.** For example, if your app lets people search for files or other types of objects, Find menu items might be more appropriate in the File menu.
+
+The Edit menu typically contains the following top-level menu items, listed in the following order.
+
+Menu item| Action| Guidance
+---|---|---
+Undo| Reverses the effect of the previous user operation.| Clarify the target of the undo. For example, if people just selected a menu item, you can append the item’s title, such as Undo Paste and Match Style. For a text entry operation, you might append the word _Typing_ to give Undo Typing.
+Redo| Reverses the effect of the previous Undo operation.| Clarify the target of the redo. For example, if people just reversed a menu item selection, you can append the item’s title, such as Redo Paste and Match Style. For a text entry operation, you might append the word _Typing_ to give Redo Typing.
+Cut| Removes the selected data and stores it on the Clipboard, replacing the previous contents of the Clipboard.|
+Copy| Duplicates the selected data and stores it on the Clipboard.|
+Paste| Inserts the contents of the Clipboard at the current insertion point. The Clipboard contents remain unchanged, permitting people to choose Paste multiple times.|
+Paste and Match Style| Inserts the contents of the Clipboard at the current insertion point, matching the style of the inserted text to the surrounding text.|
+Delete| Removes the selected data, but doesn’t place it on the Clipboard.| Provide a Delete menu item instead of an Erase or Clear menu item. Choosing Delete is the equivalent of pressing the Delete key, so it’s important for the naming to be consistent.
+Select All| Highlights all selectable content in the current document or text container.|
+Find| Displays a submenu containing menu items for performing search operations in the current document or text container. Standard submenus include: Find, Find and Replace, Find Next, Find Previous, Use Selection for Find, and Jump to Selection.|
+Spelling and Grammar| Displays a submenu containing menu items for checking for and correcting spelling and grammar in the current document or text container. Standard submenus include: Show Spelling and Grammar, Check Document Now, Check Spelling While Typing, Check Grammar With Spelling, and Correct Spelling Automatically.|
+Substitutions| Displays a submenu containing items that let people toggle automatic substitutions while they type in a document or text container. Standard submenus include: Show Substitutions, Smart Copy/Paste, Smart Quotes, Smart Dashes, Smart Links, Data Detectors, and Text Replacement.|
+Transformations| Displays a submenu containing items that transform selected text. Standard submenus include: Make Uppercase, Make Lowercase, and Capitalize.|
+Speech| Displays a submenu containing Start Speaking and Stop Speaking items, which control when the system audibly reads selected text.|
+Start Dictation| Opens the dictation window and converts spoken words into text that’s added at the current insertion point. The system automatically adds the Start Dictation menu item at the bottom of the Edit menu.|
+Emoji & Symbols| Displays a Character Viewer, which includes emoji, symbols, and other characters people can insert at the current insertion point. The system automatically adds the Emoji & Symbols menu item at the bottom of the Edit menu.|
+
+## [Format menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Format-menu)
+
+The Format menu lets people adjust text formatting attributes in the current document or text container. You can exclude this menu if your app doesn’t support formatted text editing.
+
+The Format menu typically contains the following top-level menu items, listed in the following order.
+
+Menu item| Action
+---|---
+Font| Displays a submenu containing items for adjusting font attributes of the selected text. Standard submenus include: Show Fonts, Bold, Italic, Underline, Bigger, Smaller, Show Colors, Copy Style, and Paste Style.
+Text| Displays a submenu containing items for adjusting text attributes of the selected text. Standard submenus include: Align Left, Align Center, Justify, Align Right, Writing Direction, Show Ruler, Copy Ruler, and Paste Ruler.
+
+## [View menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#View-menu)
+
+The View menu lets people customize the appearance of all an app’s windows, regardless of type.
+
+Important
+
+The View menu doesn’t include items for navigating between or managing specific windows; the [Window menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Window-menu) provides these commands.
+
+**Provide a View menu even if your app supports only a subset of the standard view functions.** For example, if your app doesn’t include a tab bar, toolbar, or sidebar, but does support full-screen mode, provide a View menu that includes only the Enter/Exit Full Screen menu item.
+
+**Ensure that each show/hide item title reflects the current state of the corresponding view.** For example, when the toolbar is hidden, provide a Show Toolbar menu item; when the toolbar is visible, provide a Hide Toolbar menu item.
+
+The View menu typically contains the following top-level menu items, listed in the following order.
+
+Menu item| Action
+---|---
+Show/Hide Tab Bar| Toggles the visibility of the [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars) above the body area in a tab-based window
+Show All Tabs/Exit Tab Overview| Enters and exits a view (similar to Mission Control) that provides an overview of all open tabs in a tab-based window
+Show/Hide Toolbar| In a window that includes a [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars), toggles the toolbar’s visibility
+Customize Toolbar| In a window that includes a toolbar, opens a view that lets people customize toolbar items
+Show/Hide Sidebar| In a window that includes a [sidebar](https://developer.apple.com/design/human-interface-guidelines/sidebars), toggles the sidebar’s visibility
+Enter/Exit Full Screen| In an app that supports a [full-screen experience](https://developer.apple.com/design/human-interface-guidelines/going-full-screen), opens the window at full-screen size in a new space
+
+## [App-specific menus](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#App-specific-menus)
+
+Your app’s custom menus appear in the menu bar between the View menu and the Window menu. For example, Safari’s menu bar includes app-specific History and Bookmarks menus.
+
+**Provide app-specific menus for custom commands.** People look in the menu bar when searching for app-specific commands, especially when using an app for the first time. Even when commands are available elsewhere in your app, it’s important to list them in the menu bar. Putting commands in the menu bar makes them easier for people to find, lets you assign keyboard shortcuts to them, and makes them more accessible to people using Full Keyboard Access. Excluding commands from the menu bar — even infrequently used or advanced commands — risks making them difficult for everyone to find.
+
+**As much as possible, reflect your app’s hierarchy in app-specific menus.** For example, Mail lists the Mailbox, Message, and Format menus in an order that mirrors the relationships of these items: mailboxes contain messages, and messages contain formatting.
+
+**Aim to list app-specific menus in order from most to least general or commonly used.** People tend to expect menus in the leading end of a list to be more specialized than menus in the trailing end.
+
+## [Window menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Window-menu)
+
+The Window menu lets people navigate, organize, and manage an app’s windows.
+
+Important
+
+The Window menu doesn’t help people customize the appearance of windows or close them. To customize a window, people use commands in the [View menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#View-menu); to close a window, people choose Close in the [File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu).
+
+**Provide a Window menu even if your app has only one window.** Include the Minimize and Zoom menu items so people using Full Keyboard Access can use the keyboard to invoke these functions.
+
+**Consider including menu items for showing and hiding panels.** A [panel](https://developer.apple.com/design/human-interface-guidelines/panels) provides information, configuration options, or tools for interacting with content in a primary window, and typically appears only when people need it. There’s no need to provide access to the font panel or text color panel because the Format menu lists these panels.
+
+The Window menu typically contains the following top-level menu items, listed in the following order.
+
+Menu item| Action| Guidance
+---|---|---
+Minimize| Minimizes the active window to the Dock. Pressing the Option key changes this item to Minimize All.|
+Zoom| Toggles between a predefined size appropriate to the window’s content and the window size people set. Pressing the Option key changes this item to Zoom All.| Avoid using Zoom to enter or exit full-screen mode. The [View menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#View-menu) supports these functions.
+Show Previous Tab| Shows the tab before the current tab in a tab-based window.|
+Show Next Tab| Shows the tab after the current tab in a tab-based window.|
+Move Tab to New Window| Opens the current tab in a new window.|
+Merge All Windows| Combines all open windows into a single tabbed window.|
+Enter/Exit Full Screen| In an app that supports a [full-screen experience](https://developer.apple.com/design/human-interface-guidelines/going-full-screen), opens the window at full-screen size in a new space.| Include this item in the Window menu only if your app doesn’t have a View menu. In this scenario, continue to provide separate Minimize and Zoom menu items.
+Bring All to Front| Brings all an app’s open windows to the front, maintaining their onscreen location, size, and layering order. (Clicking the app icon in the Dock has the same effect.) Pressing the Option key changes this item to Arrange in Front, which brings an app’s windows to the front in a neatly tiled arrangement.|
+_Name of an open app-specific window_| Brings the selected window to the front.| List the currently open windows in alphabetical order for easy scanning. Avoid listing panels or other modal views.
+
+## [Help menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Help-menu)
+
+The Help menu — located at the trailing end of the menu bar — provides access to an app’s help documentation. When you use the Help Book format for this documentation, macOS automatically includes a search field at the top of the Help menu.
+
+Menu item| Action| Guidance
+---|---|---
+Send _YourAppName_ Feedback to Apple| Opens the Feedback Assistant, in which people can provide feedback.|
+_YourAppName_ Help| When the content uses the Help Book format, opens the content in the built-in Help Viewer.|
+_Additional Item_| | Use a separator between your primary help documentation and additional items, which might include registration information or release notes. Keep the total the number of items you list in the Help menu small to avoid overwhelming people with too many choices when they need help. Alternatively, consider linking to additional items from within your help documentation.
+
+For guidance, see [Offering help](https://developer.apple.com/design/human-interface-guidelines/offering-help); for developer guidance, see [`NSHelpManager`](https://developer.apple.com/documentation/AppKit/NSHelpManager).
+
+## [Dynamic menu items](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Dynamic-menu-items)
+
+In rare cases, it can make sense to present a _dynamic menu item_ , which is a menu item that changes its behavior when people choose it while pressing a modifier key (Control, Option, Shift, or Command). For example, the _Minimize_ item in the Window menu changes to _Minimize All_ when people press the Option key.
+
+**Avoid making a dynamic menu item the only way to accomplish a task.** Dynamic menu items are hidden by default, so they’re best suited to offer shortcuts to advanced actions that people can accomplish in other ways. For example, if someone hasn’t discovered the _Minimize All_ dynamic menu item in the Window menu, they can still minimize each open window.
+
+**Use dynamic menu items primarily in menu bar menus.** Adding a dynamic menu item to contextual or Dock menus can make the item even harder for people to discover.
+
+**Require only a single modifier key to reveal a dynamic menu item.** It can be physically awkward to press more than one key while simultaneously opening a menu and choosing a menu item, in addition to reducing the discoverability of the dynamic behavior. For developer guidance, see [`isAlternate`](https://developer.apple.com/documentation/AppKit/NSMenuItem/isAlternate).
+
+Tip
+
+macOS automatically sets the width of a menu to hold the widest item, including dynamic menu items.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Platform-considerations)
+
+ _Not supported in iOS, tvOS, visionOS, or watchOS._
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#iPadOS)
+
+The menu bar displays the top-level menus for your app or game, including both system-provided menus and any custom ones you choose to add. People reveal the menu bar by moving the pointer to the top edge of the screen, or swiping down from it. When visible, the menu bar occupies the same vertical space as the [status bar](https://developer.apple.com/design/human-interface-guidelines/status-bars) at the top edge of the screen.
+
+As with the macOS menu bar, the iPadOS menu bar provides a familiar way for people to learn what an app does, find the commands they need, and discover keyboard shortcuts. While they are similar in most respects, there are a few key differences between the menu bars on each platform.
+
+| iPadOS| macOS
+---|---|---
+Menu bar visibility| Hidden until revealed| Visible by default
+Horizontal alignment| Centered| Leading side
+Menu bar extras| Not available| System default and custom
+Window controls| In the menu bar when the app is full screen| Never in the menu bar
+Apple menu| Not available| Always available
+App menu| About, Services, and app visibility-related items not available| Always available
+
+**Because the menu bar is often hidden when running an app full screen, ensure that people can access all of your app’s functions through its UI.** In particular, always offer other ways to accomplish tasks assigned to dynamic menu items, since these are only available when a hardware keyboard is connected. Avoid using the menu bar as a catch-all location for functionality that doesn’t fit in elsewhere.
+
+**Reserve the YourAppName > Settings menu item for opening your app’s page in iPadOS Settings.** If your app includes its own internal preferences area, link to it with a separate menu item beneath Settings in the same group. Place any other custom app-wide configuration options in this section as well.
+
+**For apps with tab-style navigation, consider adding each tab as a menu item in the View menu.** Since each tab is a different view of the app, the View menu is a natural place to offer an additional way to navigate between tabs. If you do this, consider assigning key bindings to each tab to make navigation even more convenient.
+
+**Consider grouping menu items into submenus to conserve vertical space.** Menu item rows on iPad use more space than on Mac to make them easier to tap. Because of this, and the smaller screen sizes of some iPads, it can be helpful to group related items into submenus more frequently than in the menu bar on Mac.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#macOS)
+
+The menu bar in macOS includes the Apple menu, which is always the first item on the leading side of the menu bar. The Apple menu includes system-defined menu items that are always available, and you can’t modify or remove it. Space permitting, the system can also display menu bar extras in the trailing end of the menu bar. For guidance, see [Menu bar extras](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Menu-bar-extras).
+
+When menu bar space is constrained, the system prioritizes the display of menus and essential menu bar extras. To ensure that menus remain readable, the system may decrease the space between the titles, truncating them if necessary.
+
+When people enter full-screen mode, the menu bar typically hides until they reveal it by moving the pointer to the top of the screen. For guidance, see [Going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen).
+
+#### [Menu bar extras](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Menu-bar-extras)
+
+A menu bar extra exposes app-specific functionality using an icon that appears in the menu bar when your app is running, even when it’s not the frontmost app. Menu bar extras are on the opposite side of the menu bar from your app’s menus. For developer guidance, see [`MenuBarExtra`](https://developer.apple.com/documentation/SwiftUI/MenuBarExtra).
+
+When necessary, the system hides menu bar extras to make room for app menus. Similarly, if there are too many menu bar extras, the system may hide some to avoid crowding app menus.
+
+
+
+**Consider using a symbol to represent your menu bar extra.** You can create an [icon](https://developer.apple.com/design/human-interface-guidelines/icons) or you can choose one of the [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols), using it as-is or customizing it to suit your needs. Both interface icons and symbols use black and clear colors to define their shapes; the system can apply other colors to the black areas in each image so it looks good on both dark and light menu bars, and when your menu bar extra is selected. The menu bar’s height is 24 pt.
+
+**Display a menu — not a popover — when people click your menu bar extra.** Unless the app functionality you want to expose is too complex for a menu, avoid presenting it in a [popover](https://developer.apple.com/design/human-interface-guidelines/popovers).
+
+**Let people — not your app — decide whether to put your menu bar extra in the menu bar.** Typically, people add a menu bar extra to the menu bar by changing a setting in an app’s settings window. To ensure discoverability, however, consider giving people the option of doing so during setup.
+
+**Avoid relying on the presence of menu bar extras.** The system hides and shows menu bar extras regularly, and you can’t be sure which other menu bar extras people have chosen to display or predict the location of your menu bar extra.
+
+**Consider exposing app-specific functionality in other ways, too.** For example, you can provide a [Dock menu](https://developer.apple.com/design/human-interface-guidelines/dock-menus) that appears when people Control-click your app’s Dock icon. People can hide or choose not to use your menu bar extra, but a Dock menu is aways available when your app is running.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Related)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+[Dock menus](https://developer.apple.com/design/human-interface-guidelines/dock-menus)
+
+[Standard keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Standard-keyboard-shortcuts)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Developer-documentation)
+
+[`CommandMenu`](https://developer.apple.com/documentation/SwiftUI/CommandMenu) — SwiftUI
+
+[Adding menus and shortcuts to the menu bar and user interface](https://developer.apple.com/documentation/UIKit/adding-menus-and-shortcuts-to-the-menu-bar-and-user-interface) — UIKit
+
+[`NSStatusBar`](https://developer.apple.com/documentation/AppKit/NSStatusBar) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance for the menu bar in iPadOS.
+
diff --git a/web-app/public/skills/hig-components-menus/references/toolbars.md b/web-app/public/skills/hig-components-menus/references/toolbars.md
new file mode 100644
index 00000000..aaf95a60
--- /dev/null
+++ b/web-app/public/skills/hig-components-menus/references/toolbars.md
@@ -0,0 +1,256 @@
+---
+title: "Toolbars | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/toolbars
+
+# Toolbars
+
+A toolbar provides convenient access to frequently used commands, controls, navigation, and search.
+
+
+
+A toolbar consists of one or more sets of controls arranged horizontally along the top or bottom edge of the view, grouped into logical sections.
+
+Toolbars act on content in the view, facilitate navigation, and help orient people in the app. They include three types of content:
+
+ * The title of the current view
+
+ * Navigation controls, like back and forward, and [search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields)
+
+ * Actions, or bar items, like [buttons](https://developer.apple.com/design/human-interface-guidelines/buttons) and [menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+
+
+
+In contrast to a toolbar, a [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars) is specifically for navigating between areas of an app.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/toolbars#Best-practices)
+
+**Choose items deliberately to avoid overcrowding.** People need to be able to distinguish and activate each item, so you don’t want to put too many items in the toolbar. To accommodate variable view widths, define which items move to the overflow menu as the toolbar becomes narrower.
+
+Note
+
+The system automatically adds an overflow menu in macOS or iPadOS when items no longer fit. Don’t add an overflow menu manually, and avoid layouts that cause toolbar items to overflow by default.
+
+**Add a More menu to contain additional actions.** Prioritize less important actions for inclusion in the More menu. Try to include all actions in the toolbar if possible, and only add this menu if you really need it.
+
+ * Standard
+ * Compact
+
+
+
+The standard toolbar in macOS Notes includes a More menu with extra commands.
+
+As the window narrows, the More menu moves into an overflow menu along with other toolbar items that no longer fit.
+
+**In iPadOS and macOS apps, consider letting people customize the toolbar to include their most common items.** Toolbar customization is especially useful in apps that provide a lot of items — or that include advanced functionality that not everyone needs — and in apps that people tend to use for long periods of time. For example, it works well to make a range of editing actions available for toolbar customization, because people often use different types of editing commands based on their work style and their current project.
+
+**Reduce the use of toolbar backgrounds and tinted controls.** Any custom backgrounds and appearances you use might overlay or interfere with background effects that the system provides. Instead, use the content layer to inform the color and appearance of the toolbar, and use a [`ScrollEdgeEffectStyle`](https://developer.apple.com/documentation/SwiftUI/ScrollEdgeEffectStyle) when necessary to distinguish the toolbar area from the content area. This approach helps your app express its unique personality without distracting from content.
+
+**Avoid applying a similar color to toolbar item labels and content layer backgrounds.** If your app already has bright, colorful content in the content layer, prefer using the default monochromatic appearance of toolbars. For more guidance, see [Liquid Glass color](https://developer.apple.com/design/human-interface-guidelines/color#Liquid-Glass-color).
+
+**Prefer using standard components in a toolbar.** By default, standard buttons, text fields, headers, and footers have corner radii that are concentric with bar corners. If you need to create a custom component, ensure that its corner radius is also concentric with the bar’s corners.
+
+**Consider temporarily hiding toolbars for a distraction-free experience.** Sometimes people appreciate a minimal interface to reduce distractions or reveal more content. If you support this, do so contextually when it makes the most sense, and offer ways to reliably restore hidden interface elements. For guidance, see [Going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen). For guidance specific to visionOS, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+## [Titles](https://developer.apple.com/design/human-interface-guidelines/toolbars#Titles)
+
+**Provide a useful title for each window.** A title helps people confirm their location as they navigate your app, and differentiates between the content of multiple open windows. If titling a toolbar seems redundant, you can leave the title area empty. For example, Notes doesn’t title the current note when a single window is open, because the first line of content typically supplies sufficient context. However, when opening notes in separate windows, the system titles them with the first line of content so people can tell them apart.
+
+**Don’t title windows with your app name.** Your app’s name doesn’t provide useful information about your content hierarchy or any window or area in your app, so it doesn’t work well as a title.
+
+**Write a concise title.** Aim for a word or short phrase that distills the purpose of the window or view, and keep the title under 15 characters long so you leave enough room for other controls.
+
+## [Navigation](https://developer.apple.com/design/human-interface-guidelines/toolbars#Navigation)
+
+A toolbar with navigation controls appears at the top of a window, helping people move through a hierarchy of content. A toolbar also often contains a [search field](https://developer.apple.com/design/human-interface-guidelines/search-fields) for quick navigation between areas or pieces of content. In iOS, a navigation-specific toolbar is sometimes called a navigation bar.
+
+**Use the standard Back and Close buttons.** People know that the standard Back button lets them retrace their steps through a hierarchy of information, and the standard Close button closes a modal view. Prefer the standard symbols for each, and don’t use a text label that says _Back_ or _Close_. If you create a custom version of either, make sure it still looks the same, behaves as people expect, and matches the rest of your interface, and ensure you consistently implement it throughout your app or game. For guidance, see [Icons](https://developer.apple.com/design/human-interface-guidelines/icons).
+
+
+
+
+
+
+
+
+
+## [Actions](https://developer.apple.com/design/human-interface-guidelines/toolbars#Actions)
+
+**Provide actions that support the main tasks people perform.** In general, prioritize the commands that people are most likely to want. These commands are often the ones people use most frequently, but in some apps it might make sense to prioritize commands that map to the highest level or most important objects people work with.
+
+**Make sure the meaning of each control is clear.** Don’t make people guess or experiment to figure out what a toolbar item does. Prefer simple, recognizable symbols for items instead of text, except for actions like _edit_ that aren’t well-represented by symbols. For guidance on symbols that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons).
+
+
+
+
+
+
+
+
+
+**Prefer system-provided symbols without borders.** System-provided symbols are familiar, automatically receive appropriate coloring and vibrancy, and respond consistently to user interactions. Borders (like outlined circle symbols) aren’t necessary because the section provides a visible container, and the system defines hover and selection state appearances automatically. For guidance, see [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+
+
+
+
+
+
+
+
+**Use the`.prominent` style for key actions such as Done or Submit.** This separates and tints the action so there’s a clear focal point. Only specify one primary action, and put it on the trailing side of the toolbar.
+
+
+
+## [Item groupings](https://developer.apple.com/design/human-interface-guidelines/toolbars#Item-groupings)
+
+You can position toolbar items in three locations: the leading edge, center area, and trailing edge of the toolbar. These areas provide familiar homes for navigation controls, window or document titles, common actions, and search.
+
+ * **Leading edge.** Elements that let people return to the previous document and show or hide a sidebar appear at the far leading edge, followed by the view title. Next to the title, the toolbar can include a document menu that contains standard and app-specific commands that affect the document as a whole, such as Duplicate, Rename, Move, and Export. To ensure that these items are always available, items on the toolbar’s leading edge aren’t customizable.
+
+ * **Center area.** Common, useful controls appear in the center area, and the view title can appear here if it’s not on the leading edge. In macOS and iPadOS, people can add, remove, and rearrange items here if you let them customize the toolbar, and items in this section automatically collapse into the system-managed overflow menu when the window shrinks enough in size.
+
+ * **Trailing edge.** The trailing edge contains important items that need to remain available, buttons that open nearby inspectors, an optional search field, and the More menu that contains additional items and supports toolbar customization. It also includes a primary action like Done when one exists. Items on the trailing edge remain visible at all window sizes.
+
+
+
+
+
+
+To position items in the groupings you want, pin them to the leading edge, center, or trailing edge, and insert space between buttons or other items where appropriate.
+
+**Group toolbar items logically by function and frequency of use.** For example, Keynote includes several sections that are based on functionality, including one for presentation-level commands, one for playback commands, and one for object insertion.
+
+**Group navigation controls and critical actions like Done, Close, or Save in dedicated, familiar, and visually distinct sections.** This reflects their importance and helps people discover and understand these actions.
+
+
+
+
+
+
+
+
+
+**Keep consistent groupings and placement across platforms.** This helps people develop familiarity with your app and trust that it behaves similarly regardless of where they use it.
+
+**Minimize the number of groups.** Too many groups of controls can make a toolbar feel cluttered and confusing, even with the added space on iPad and Mac. In general, aim for a maximum of three.
+
+**Keep actions with text labels separate.** Placing an action with a text label next to an action with a symbol can create the illusion of a single action with a combined text and symbol, leading to confusion and misinterpretation. If your toolbar includes multiple text-labeled buttons, the text of those buttons may appear to run together, making the buttons indistinguishable. Add separation by inserting fixed space between the buttons. For developer guidance, see [`UIBarButtonItem.SystemItem.fixedSpace`](https://developer.apple.com/documentation/UIKit/UIBarButtonItem/SystemItem/fixedSpace).
+
+
+
+
+
+
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/toolbars#Platform-considerations)
+
+ _No additional considerations for tvOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/toolbars#iOS)
+
+**Prioritize only the most important items for inclusion in the main toolbar area.** Because space is so limited, carefully consider which actions are essential to your app and include those first. Create a More menu to include additional items.
+
+**Use a large title to help people stay oriented as they navigate and scroll.** By default, a large title transitions to a standard title as people begin scrolling the content, and transitions back to large when people scroll to the top, reminding them of their current location. For developer guidance, see [`prefersLargeTitles`](https://developer.apple.com/documentation/UIKit/UINavigationBar/prefersLargeTitles).
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/toolbars#iPadOS)
+
+**Consider combining a toolbar with a tab bar.** In iPadOS, a toolbar and a [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars) can coexist in the same horizontal space at the top of the view. This is particularly useful for layouts where you want to navigate between a few main app areas while keeping the full width of the window available for content. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout) and [Windows](https://developer.apple.com/design/human-interface-guidelines/windows).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/toolbars#macOS)
+
+In a macOS app, the toolbar resides in the frame at the top of a window, either below or integrated with the title bar. Note that window titles can display inline with controls, and toolbar items don’t include a bezel.
+
+
+
+**Make every toolbar item available as a command in the menu bar.** Because people can customize the toolbar or hide it, it can’t be the only place that presents a command. In contrast, it doesn’t make sense to provide a toolbar item for every menu item, because not all menu commands are important enough or used often enough to warrant space in the toolbar.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/toolbars#visionOS)
+
+In visionOS, the system-provided toolbar appears along the bottom edge of a window, above the window-management controls, and in a parallel plane that’s slightly in front of the window along the z-axis.
+
+
+
+To maintain the legibility of toolbar items as content scrolls behind them, visionOS uses a variable blur in the bar background. The variable blur anchors the bar above the scrolling content while letting the view’s glass material remain uniform and undivided.
+
+In visionOS, you can supply either a symbol or a text label for each toolbar item. When people look at a toolbar item that contains a symbol, visionOS reveals the text label, providing additional information.
+
+**Prefer using a system-provided toolbar.** The standard toolbar has a consistent and familiar appearance and is optimized to work well with eye and hand input. In addition, the system automatically places a standard toolbar in the correct position in relation to its window.
+
+
+
+**Avoid creating a vertical toolbar.** In visionOS, [tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars) are vertical, so presenting a vertical toolbar could confuse people.
+
+**Try to prevent windows from resizing below the width of the toolbar.** visionOS doesn’t include a menu bar where each app lists all its actions, so it’s important for the toolbar to provide reliable access to essential controls regardless of a window’s size.
+
+**If your app can enter a modal state, consider offering contextually relevant toolbar controls.** For example, a photo-editing app might enter a modal state to help people perform a multistep editing task. In this scenario, the controls in the modal editing view are different from the controls in the main window. Be sure to reinstate the window’s standard toolbar controls when the app exits the modal state.
+
+**Avoid using a pull-down menu in a toolbar.** A pull-down menu lets you offer additional actions related to a toolbar item, but can be difficult for people to discover and may clutter your interface. Because a toolbar is located at the bottom edge of a window in visionOS, a pull-down menu might obscure the standard window controls that appear below the bottom edge. For guidance, see [Pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/toolbars#watchOS)
+
+A toolbar button lets you offer important app functionality in a view that displays related content. You can place toolbar buttons in the top corners or along the bottom. If you place these buttons above scrolling content, the buttons always remain visible, as the content scrolls under them.
+
+
+
+Top toolbar buttons
+
+
+
+Bottom toolbar buttons
+
+For developer guidance, see [`topBarLeading`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement/topBarLeading), [`topBarTrailing`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement/topBarTrailing), or [`bottomBar`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement/bottomBar).
+
+You can also place a button in the scrolling view. By default, a scrolling toolbar button remains hidden until people reveal it by scrolling up. People frequently scroll to the top of a scrolling view, so discovering a toolbar button is automatic.
+
+
+
+Toolbar button hidden
+
+
+
+Toolbar button shown
+
+For developer guidance, see [`primaryAction`](https://developer.apple.com/documentation/SwiftUI/ToolbarItemPlacement/primaryAction).
+
+**Use a scrolling toolbar button for an important action that isn’t a primary app function.** A toolbar button gives you the flexibility to offer important functionality in a view whose primary purpose is related to that functionality, but may not be the same. For example, Mail provides the essential New Message action in a toolbar button at the top of the Inbox view. The primary purpose of the Inbox is to display a scrollable list of email messages, so it makes sense to offer the closely related compose action in a toolbar button at the top of the view.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/toolbars#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/toolbars#Related)
+
+[Sidebars](https://developer.apple.com/design/human-interface-guidelines/sidebars)
+
+[Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons)
+
+[Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/toolbars#Developer-documentation)
+
+[Toolbars](https://developer.apple.com/documentation/SwiftUI/Toolbars) — SwiftUI
+
+[`UIToolbar`](https://developer.apple.com/documentation/UIKit/UIToolbar) — UIKit
+
+[`NSToolbar`](https://developer.apple.com/documentation/AppKit/NSToolbar) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/toolbars#Videos)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/toolbars#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for Liquid Glass.
+June 9, 2025| Added guidance for grouping bar items, updated guidance for using symbols, and incorporated navigation bar guidance.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance for using toolbars in watchOS.
+
diff --git a/web-app/public/skills/hig-components-search/SKILL.md b/web-app/public/skills/hig-components-search/SKILL.md
new file mode 100644
index 00000000..af722b5d
--- /dev/null
+++ b/web-app/public/skills/hig-components-search/SKILL.md
@@ -0,0 +1,73 @@
+---
+name: hig-components-search
+version: 1.0.0
+description: ">-"
+ Apple HIG guidance for navigation-related components including search fields,
+ page controls, and path controls. Use this skill when the user says "how should
+ search work in my app," "I need a breadcrumb," "how do I paginate content," or
+ asks about search field, search bar, page control, path control, breadcrumb,
+ navigation component, search UX, search suggestions, search scopes, paginated
+ content navigation, or file path hierarchy display. Cross-references:
+ hig-components-menus, hig-components-controls, hig-components-dialogs,
+ hig-patterns.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Navigation Components
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Search: discoverable with instant feedback.** Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types.
+
+2. **Page controls: position in a flat page sequence.** For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count.
+
+3. **Path controls: file hierarchy navigation.** macOS path controls display location within a directory structure and allow jumping to any ancestor.
+
+4. **Search scopes narrow large result sets.** Provide scope buttons so users can filter without complex queries.
+
+5. **Clear empty states for search.** Helpful message suggesting corrections or alternatives, not a blank screen.
+
+6. **Page controls are not for hierarchical navigation.** Flat, linear sequences only. Use navigation controllers, tab bars, or sidebars for hierarchy.
+
+7. **Keep path controls concise.** Show meaningful segments only. Users can click any segment to navigate directly.
+
+8. **Support keyboard for search.** Command-F and system search shortcuts should activate search.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [search-fields.md](references/search-fields.md) | Search fields | Scopes, tokens, instant results, placement |
+| [page-controls.md](references/page-controls.md) | Page controls | Dot indicators, flat page sequences |
+| [path-controls.md](references/path-controls.md) | Path controls | Breadcrumbs, ancestor navigation |
+
+## Output Format
+
+1. **Component recommendation** -- search field, page control, or path control, and why.
+2. **Behavior specification** -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths).
+3. **Platform differences** across iOS, iPadOS, macOS, visionOS.
+
+## Questions to Ask
+
+1. What type of content is being searched or navigated?
+2. Which platforms?
+3. How large is the dataset?
+4. Is search the primary interaction?
+
+## Related Skills
+
+- **hig-components-menus** -- Toolbars and menu bars hosting search and navigation controls
+- **hig-components-controls** -- Text fields, pickers, segmented controls in search interfaces
+- **hig-components-dialogs** -- Popovers and sheets for expanded search or filtering
+- **hig-patterns** -- Navigation patterns and information architecture
+- **hig-foundations** -- Typography and layout for navigation components
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-search/references/page-controls.md b/web-app/public/skills/hig-components-search/references/page-controls.md
new file mode 100644
index 00000000..0e22d504
--- /dev/null
+++ b/web-app/public/skills/hig-components-search/references/page-controls.md
@@ -0,0 +1,120 @@
+---
+title: "Page controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/page-controls
+
+# Page controls
+
+A page control displays a row of indicator images, each of which represents a page in a flat list.
+
+
+
+The scrolling row of indicators helps people navigate the list to find the page they want. Page controls can handle an arbitrary number of pages, making them particularly useful in situations where people can create custom lists.
+
+Page controls appear as a series of small indicator dots by default, representing the available pages. A solid dot denotes the current page. Visually, these dots are always equidistant, and are clipped if there are too many to fit in the window.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/page-controls#Best-practices)
+
+**Use page controls to represent movement between an ordered list of pages.** Page controls don’t represent hierarchical or nonsequential page relationships. For more complex navigation, consider using a sidebar or split view instead.
+
+**Center a page control at the bottom of the view or window.** To ensure people always know where to find a page control, center it horizontally and position it near the bottom of the view.
+
+**Although page controls can handle any number of pages, don’t display too many**. More than about 10 dots are hard to count at a glance. If your app needs to display more than 10 pages as peers, consider using a different arrangement‚ such as a grid, that lets people navigate the content in any order.
+
+## [Customizing indicators](https://developer.apple.com/design/human-interface-guidelines/page-controls#Customizing-indicators)
+
+By default, a page control uses the system-provided dot image for all indicators, but it can also display a unique image to help people identify a specific page. For example, Weather uses the `location.fill` symbol to distinguish the current location’s page.
+
+If it enhances your app or game, you can provide a custom image to use as the default image for all indicators and you can also supply a different image for a specific page. For developer guidance, see [`preferredIndicatorImage`](https://developer.apple.com/documentation/UIKit/UIPageControl/preferredIndicatorImage) and [`setIndicatorImage(_:forPage:)`](https://developer.apple.com/documentation/UIKit/UIPageControl/setIndicatorImage\(_:forPage:\)).
+
+**Make sure custom indicator images are simple and clear.** Avoid complex shapes, and don’t include negative space, text, or inner lines, because these details can make an icon muddy and indecipherable at very small sizes. Consider using simple [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) as indicators or design your own icons. For guidance, see [Icons](https://developer.apple.com/design/human-interface-guidelines/icons).
+
+**Customize the default indicator image only when it enhances the page control’s overall meaning.** For example, if every page you list contains bookmarks, you might use the `bookmark.fill` symbol as the default indicator image.
+
+**Avoid using more than two different indicator images in a page control.** If your list contains one page with special meaning — like the current-location page in Weather — you can make the page easy to find by giving it a unique indicator image. In contrast, a page control that uses several unique images to mark several important pages is hard to use because people must memorize the meaning of each image. A page control that displays more than two types of indicator images tends to look messy and haphazard, even when each image is clear.
+
+
+
+Using several different indicators can make a page control look busy and difficult to use.
+
+
+
+Using only two different indicators looks well-organized and provides a consistent experience.
+
+**Avoid coloring indicator images.** Custom colors can reduce the contrast that differentiates the current-page indicator and makes the page control visible on the screen. To ensure that your page control is easy to use and looks good in different contexts, let the system automatically color the indicators.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/page-controls#Platform-considerations)
+
+ _Not supported in macOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/page-controls#iOS-iPadOS)
+
+A page control can adjust the appearance of indicators to provide more information about the list. For example, the control highlights the indicator of the current page so people can estimate the page’s relative position in the list. When there are more indicators than fit in the space, the control can shrink indicators at both sides to suggest that more pages are available.
+
+
+
+People interact with page controls by tapping or scrubbing (to _scrub_ , people touch the control and drag left or right). Tapping on the leading or trailing side of the current-page indicator reveals the next or previous page; in iPadOS, people can also use the pointer to target a specific indicator. Scrubbing opens pages in sequence, and scrubbing past the leading or trailing edge of the control helps people quickly reach the first or last page.
+
+Developer note
+
+In the API, _tapping_ is a _discrete interaction_ , whereas _scrubbing_ is a _continuous interaction_ ; for developer guidance, see [`UIPageControl.InteractionState`](https://developer.apple.com/documentation/UIKit/UIPageControl/InteractionState-swift.enum).
+
+**Avoid animating page transitions during scrubbing.** People can scrub very quickly, and using the scrolling animation for every transition can make your app lag and cause distracting visual flashes. Use the animated scrolling transition only for tapping.
+
+A page control can include a translucent, rounded-rectangle background appearance that provides visual contrast for the indicators. You can choose one of the following background styles:
+
+ * Automatic — Displays the background only when people interact with the control. Use this style when the page control isn’t the primary navigational element in the UI.
+
+ * Prominent — Always displays the background. Use this style only when the control is the primary navigational control in the screen.
+
+ * Minimal — Never displays the background. Use this style when you just want to show the position of the current page in the list and you don’t need to provide visual feedback during scrubbing.
+
+
+
+
+For developer guidance, see [`backgroundStyle`](https://developer.apple.com/documentation/UIKit/UIPageControl/backgroundStyle-swift.property).
+
+**Avoid supporting the scrubber when you use the minimal background style.** The minimal style doesn’t provide visual feedback during scrubbing. If you want to let people scrub a list of pages in your app, use the automatic or prominent background styles.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/page-controls#tvOS)
+
+**Use page controls on collections of full-screen pages.** A page control is designed to operate in a full-screen environment where multiple content-rich pages are peers in the page hierarchy. Inclusion of additional controls makes it difficult to maintain focus while moving between pages.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/page-controls#visionOS)
+
+In visionOS, page controls represent available pages and indicate the current page, but people don’t interact with them.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/page-controls#watchOS)
+
+In watchOS, page controls can be displayed at the bottom of the screen for horizontal pagination, or next to the Digital Crown when presenting a vertical [tab view](https://developer.apple.com/design/human-interface-guidelines/components/layout-and-organization/tab-views). When using vertical tab views, the page indicator shows people where they are in the navigation, both within the current page and within the set of pages. The page control transitions between scrolling through a page’s content and scrolling to other pages.
+
+
+
+Vertical page control
+
+
+
+Horizontal page control
+
+**Use vertical pagination to separate multiple views into distinct, purposeful pages.** Give each page a clear purpose, and let people scroll through the pages using the Digital Crown. In watchOS, this design is more effective than horizontal pagination or many levels of hierarchical navigation.
+
+**Consider limiting the content of an individual page to a single screen height.** Embracing this constraint encourages each page to serve a clear and distinct purpose and results in a more glanceable design. Use variable-height pages judiciously and, if possible, only place them after fixed-height pages in your app design.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/page-controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/page-controls#Related)
+
+[Scroll views](https://developer.apple.com/design/human-interface-guidelines/scroll-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/page-controls#Developer-documentation)
+
+[`PageTabViewStyle`](https://developer.apple.com/documentation/SwiftUI/PageTabViewStyle) — SwiftUI
+
+[`UIPageControl`](https://developer.apple.com/documentation/UIKit/UIPageControl) — UIKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/page-controls#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance for using page controls in watchOS.
+
diff --git a/web-app/public/skills/hig-components-search/references/path-controls.md b/web-app/public/skills/hig-components-search/references/path-controls.md
new file mode 100644
index 00000000..50859e42
--- /dev/null
+++ b/web-app/public/skills/hig-components-search/references/path-controls.md
@@ -0,0 +1,40 @@
+---
+title: "Path controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/path-controls
+
+# Path controls
+
+A path control shows the file system path of a selected file or folder.
+
+
+
+For example, choosing View > Show Path Bar in the Finder displays a path bar at the bottom of the window. It shows the path of the selected item, or the path of the window’s folder if nothing is selected.
+
+There are two styles of path control.
+
+
+
+**Standard.** A linear list that includes the root disk, parent folders, and selected item. Each item appears with an icon and a name. If the list is too long to fit within the control, it hides names between the first and last items. If you make the control editable, people can drag an item onto the control to select the item and display its path in the control.
+
+
+
+**Pop up.** A control similar to a [pop-up button](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons) that shows the icon and name of the selected item. People can click the item to open a menu containing the root disk, parent folders, and selected item. If you make the control editable, the menu contains an additional Choose command that people can use to select an item and display it in the control. They can also drag an item onto the control to select it and display its path.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/path-controls#Best-practices)
+
+**Use a path control in the window body, not the window frame.** Path controls aren’t intended for use in toolbars or status bars. Note that the path control in the Finder appears at the bottom of the window body, not in the status bar.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/path-controls#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/path-controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/path-controls#Related)
+
+[File management](https://developer.apple.com/design/human-interface-guidelines/file-management)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/path-controls#Developer-documentation)
+
+[`NSPathControl`](https://developer.apple.com/documentation/AppKit/NSPathControl) — AppKit
+
diff --git a/web-app/public/skills/hig-components-search/references/search-fields.md b/web-app/public/skills/hig-components-search/references/search-fields.md
new file mode 100644
index 00000000..7dc9dbcb
--- /dev/null
+++ b/web-app/public/skills/hig-components-search/references/search-fields.md
@@ -0,0 +1,189 @@
+---
+title: "Search fields | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/search-fields
+
+# Search fields
+
+A search field lets people search a collection of content for specific terms they enter.
+
+
+
+A search field is an editable text field that displays a Search icon, a Clear button, and placeholder text where people can enter what they are searching for. Search fields can use a [scope control](https://developer.apple.com/design/human-interface-guidelines/search-fields#Scope-controls-and-tokens) as well as [tokens](https://developer.apple.com/design/human-interface-guidelines/search-fields#Scope-controls-and-tokens) to help filter and refine the scope of their search. Across each platform, there are different patterns for accessing search based on the goals and design of your app.
+
+For developer guidance, see [Adding a search interface to your app](https://developer.apple.com/documentation/SwiftUI/Adding-a-search-interface-to-your-app); for guidance related to systemwide search, see [Searching](https://developer.apple.com/design/human-interface-guidelines/searching).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/search-fields#Best-practices)
+
+**Display placeholder text that describes the type of information people can search for.** For example, the Apple TV app includes the placeholder text _Shows, Movies, and More_. Avoid using a term like _Search_ for placeholder text because it doesn’t provide any helpful information.
+
+**If possible, start search immediately when a person types.** Searching while someone types makes the search experience feel more responsive because it provides results that are continuously refined as the text becomes more specific.
+
+**Consider showing suggested search terms before search begins, or as a person types.** This can help someone search faster by suggesting common searches, even when the search itself doesn’t begin immediately.
+
+**Simplify search results.** Provide the most relevant search results first to minimize the need for someone to scroll to find what they’re looking for. In addition to prioritizing the most likely results, consider categorizing them to help people find what they want.
+
+**Consider letting people filter search results.** For example, you can include a scope control in the search results content area to help people quickly and easily filter search results.
+
+## [Scope controls and tokens](https://developer.apple.com/design/human-interface-guidelines/search-fields#Scope-controls-and-tokens)
+
+Scope controls and tokens are components you can use to let someone narrow the parameters of a search either before or after they make it.
+
+ * A _scope control_ acts like a [segmented control](https://developer.apple.com/design/human-interface-guidelines/segmented-controls) for choosing a category for the search.
+
+ * A _token_ is a visual representation of a search term that someone can select and edit, and acts as a filter for any additional terms in the search.
+
+
+
+
+
+
+**Use a scope control to filter among clearly defined search categories.** A scope control can help someone move from a broader scope to a narrower one. For example, in Mail on iPhone, a scope control helps people move from searching their entire mailbox to just the specific mailbox they’re viewing. For developer guidance, see [Scoping a search operation](https://developer.apple.com/documentation/SwiftUI/Scoping-a-search-operation).
+
+**Default to a broader scope and let people refine it as they need.** A broader scope provides context for the full set of available results, which helps guide people in a useful direction when they choose to narrow the scope.
+
+**Use tokens to filter by common search terms or items.** When you define a token, the term it represents gains a visual treatment that encapsulates it, indicating that people can select and edit it as a single item. Tokens can clarify a search term, like filtering by a specific contact in Mail, or focus a search to a specific set of attributes, like filtering by photos in Messages. For the related macOS component, see [Token fields](https://developer.apple.com/design/human-interface-guidelines/token-fields).
+
+**Consider pairing tokens with search suggestions.** People may not know which tokens are available, so pairing them with search suggestions can help people learn how to use them.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/search-fields#Platform-considerations)
+
+ _No additional considerations for visionOS_.
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/search-fields#iOS)
+
+There are three main places you can position the entry point for search:
+
+ * In a tab bar at the bottom of the screen
+
+ * In a toolbar at the bottom or top of the screen
+
+ * Directly inline with content
+
+
+
+
+Where search makes the most sense depends on the layout, content, and navigation of your app.
+
+#### [Search in a tab bar](https://developer.apple.com/design/human-interface-guidelines/search-fields#Search-in-a-tab-bar)
+
+You can place search as a visually distinct tab on the trailing side of a tab bar, which keeps search visible and always available as people switch between the sections of your app.
+
+
+
+When someone navigates to the search tab, the search field that appears can start as _focused_ or _unfocused_.
+
+
+
+Focused
+
+
+
+Unfocused
+
+**Start with the search field focused to help people quickly find what they need.** When the search field starts focused, the keyboard immediately appears with the search field above it, ready to begin the search. This provides a more transient experience that brings people directly back to their previous tab after they exit search, and is ideal when you want search to resolve quickly and seamlessly.
+
+**Start with the search field unfocused to promote discovery and exploration.** When the search field starts unfocused, the search tab expands into an unselected field at the bottom of the screen. This provides space on the rest of the screen for additional discovery or navigation before someone taps the field to begin the search. This is great for an app with a large collection of content to showcase, like Music or TV.
+
+#### [Search in a toolbar](https://developer.apple.com/design/human-interface-guidelines/search-fields#Search-in-a-toolbar)
+
+As an alternative to search in a tab bar, you can also place search in a toolbar either at the bottom or top of the screen.
+
+ * You can include search in a bottom toolbar either as an expanded field or as a toolbar button, depending on how much space is available and how important search is to your app. When someone taps it, it animates into a search field above the keyboard so they can begin typing.
+
+ * You can include search in a top toolbar, also called a navigation bar, where it appears as a toolbar button. When someone taps it, it animates into a search field that appears either above the keyboard or inline at the top if there isn’t space at the bottom.
+
+
+
+
+
+
+Search in a bottom toolbar
+
+
+
+Search in a top toolbar
+
+**Place search at the bottom if there’s room.** You can either add a search field to an existing toolbar, or as a new toolbar where search is the only item. Search at the bottom is useful in any situation where search is a priority, since it keeps the search experience easy to reach. Examples of apps with search at the bottom in various toolbar layouts include Settings, where it’s the only item, and Mail and Notes, where it fits alongside other important controls.
+
+**Place search at the top when itʼs important to defer to content at the bottom of the screen, or thereʼs no bottom toolbar.** Use search at the top in cases where covering the content might interfere with a primary function of the app. The Wallet app, for example, includes event passes in a stack at the bottom of the screen for easy access and viewing at a glance.
+
+#### [Search as an inline field](https://developer.apple.com/design/human-interface-guidelines/search-fields#Search-as-an-inline-field)
+
+In some cases you might want your app to include a search field inline with content.
+
+**Place search as an inline field when its position alongside the content it searches strengthens that relationship.** When you need to filter or search within a single view, it can be helpful to have search appear directly next to content to illustrate that the search applies to it, rather than globally. For example, although the main search in the Music app is in the tab bar, people can navigate to their library and use an inline search field to filter their songs and albums.
+
+**Prefer placing search at the bottom.** Generally, even for search that applies to a subset of your app’s content, it’s better to locate search where people can reach it easily. The Settings app, for example, places search at the bottom both for its top-level search and for search in the section for individual apps. If there isn’t space at the bottom (because it’s occupied by a tab bar or other important UI, for example), it’s okay to place search inline at the top.
+
+**When at the top, position an inline search field above the list it searches, and pin it to the top toolbar when scrolling.** This helps keep it distinct from search that appears in other locations.
+
+### [iPadOS, macOS](https://developer.apple.com/design/human-interface-guidelines/search-fields#iPadOS-macOS)
+
+The placement and behavior of the search field in iPadOS and macOS is similar; on both platforms, clearing the field exits search and dismisses the keyboard if present. If your app is available on both iPad and Mac, try to keep the search experience as consistent as possible across both platforms.
+
+iPadOS
+
+macOS
+
+**Put a search field at the trailing side of the toolbar for many common uses.** Many apps benefit from the familiar pattern of search in the toolbar, particularly apps with split views or apps that navigate between multiple sources, like Mail, Notes, and Voice Memos. The persistent availability of search at the side of the toolbar gives it a global presence within your app, so it’s generally appropriate to start with a global scope for the initial search.
+
+**Include search at the top of the sidebar when filtering content or navigation there.** Apps such as Settings take advantage of search to quickly filter the sidebar and expose sections that may be multiple levels deep, providing a simple way for people to search, preview, and navigate to the section or setting they’re looking for.
+
+
+
+**Include search as an item in the sidebar or tab bar when you want an area dedicated to discovery.** If your search is paired with rich suggestions, categories, or content that needs more space, it can be helpful to have a dedicated area for it. This is particularly true for apps where browsing and search go hand in hand, like Music and TV, where it provides a unified location to highlight suggested content, categories, and recent searches. A dedicated area also ensures search is always available as people navigate and switch sections of your app.
+
+
+
+**In a search field in a dedicated area, consider immediately focusing the field when a person navigates to the section to help people search faster and locate the field itself more easily.** An exception to this is on iPad when only a virtual keyboard is available, in which case it’s better to leave the field unfocused to prevent the keyboard from unexpectedly covering the view.
+
+**Account for window resizing with the placement of the search field.** On iPad, the search field fluidly resizes with the app window like it does on Mac. However, for compact views on iPad, itʼs important to ensure that search is available where it’s most contextually useful. For example, Notes and Mail place search above the column for the content list when they resize down to a compact view.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/search-fields#tvOS)
+
+A search screen is a specialized keyboard screen that helps people enter search text, displaying search results beneath the keyboard in a fully customizable view. For developer guidance, see [`UISearchController`](https://developer.apple.com/documentation/UIKit/UISearchController).
+
+
+
+**Provide suggestions to make searching easier.** People typically don’t want to do a lot of typing in tvOS. To improve the search experience, provide popular and context-specific search suggestions, including recent searches when available. For developer guidance, see [Using suggested searches with a search controller](https://developer.apple.com/documentation/UIKit/using-suggested-searches-with-a-search-controller).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/search-fields#watchOS)
+
+When someone taps the search field, the system displays a text-input control that covers the entire screen. The app only returns to the search field after they tap the Cancel or Search button.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/search-fields#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/search-fields#Related)
+
+[Searching](https://developer.apple.com/design/human-interface-guidelines/searching)
+
+[Token fields](https://developer.apple.com/design/human-interface-guidelines/token-fields)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/search-fields#Developer-documentation)
+
+[Adding a search interface to your app](https://developer.apple.com/documentation/SwiftUI/Adding-a-search-interface-to-your-app) — SwiftUI
+
+[`searchable(text:placement:prompt:)`](https://developer.apple.com/documentation/SwiftUI/View/searchable\(text:placement:prompt:\)) — SwiftUI
+
+[`UISearchBar`](https://developer.apple.com/documentation/UIKit/UISearchBar) — UIKit
+
+[`UISearchTextField`](https://developer.apple.com/documentation/UIKit/UISearchTextField) — UIKit
+
+[`NSSearchField`](https://developer.apple.com/documentation/AppKit/NSSearchField) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/search-fields#Videos)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+[ Discoverable design ](https://developer.apple.com/videos/play/wwdc2021/10126)
+
+[ Craft search experiences in SwiftUI ](https://developer.apple.com/videos/play/wwdc2021/10176)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/search-fields#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated guidance for search placement in iOS, consolidated iPadOS and macOS platform considerations, and added guidance for tokens.
+September 12, 2023| Combined guidance common to all platforms.
+June 5, 2023| Added guidance for using search fields in watchOS.
+
diff --git a/web-app/public/skills/hig-components-status/SKILL.md b/web-app/public/skills/hig-components-status/SKILL.md
new file mode 100644
index 00000000..de026f09
--- /dev/null
+++ b/web-app/public/skills/hig-components-status/SKILL.md
@@ -0,0 +1,91 @@
+---
+name: hig-components-status
+version: 1.0.0
+description: ">"
+ Apple HIG guidance for status and progress UI components including progress indicators,
+ status bars, and activity rings. Use this skill when asked about: "progress indicator",
+ "progress bar", "loading spinner", "status bar", "activity ring", "progress display",
+ determinate vs indeterminate progress, loading states, or fitness tracking rings.
+ Also use when the user says "how do I show loading state," "should I use a spinner
+ or progress bar," "what goes in the status bar," or asks about activity indicators.
+ Cross-references: hig-components-system for widgets and complications,
+ hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit
+ and activity ring data integration.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Status Components
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+### Progress Indicators
+
+1. **Show progress for operations longer than a second or two.**
+
+2. **Determinate when duration/percentage is known.** A filling progress bar gives users a clear sense of remaining work. Use for downloads, uploads, or any measurable process.
+
+3. **Indeterminate when duration is unknown.** A spinner communicates work is happening without promising a timeframe. Use for unpredictable network requests.
+
+4. **Prefer progress bars over spinners.** Determinate progress feels faster and more trustworthy.
+
+5. **Place indicators where content will appear.** Inline progress near the content area, not modal or distant.
+
+6. **Don't stack multiple indicators.** Aggregate simultaneous operations into one representation or show the most relevant.
+
+### Status Bars
+
+7. **Don't hide the status bar without good reason.** Reserve hiding for immersive experiences (full-screen media, games, AR).
+
+8. **Match status bar style to your content.** Light or dark for adequate contrast.
+
+9. **Respect safe areas.** No interactive content behind the status bar.
+
+10. **Restore promptly** when exiting immersive contexts.
+
+### Activity Rings
+
+11. **Activity rings are for Move, Exercise, and Stand goals.** Don't repurpose the ring metaphor for unrelated data.
+
+12. **Respect ring color conventions.** Red (Move), green (Exercise), blue (Stand) are strongly associated with Apple Fitness.
+
+13. **Use HealthKit APIs** for activity data rather than manual tracking.
+
+14. **Celebrate completions** with animation and haptics when rings close.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [progress-indicators.md](references/progress-indicators.md) | Progress bars and spinners | Determinate, indeterminate, inline placement, duration |
+| [status-bars.md](references/status-bars.md) | iOS/iPadOS status bar | System info, visibility, style, safe areas |
+| [activity-rings.md](references/activity-rings.md) | watchOS activity rings | Move/Exercise/Stand, HealthKit, fitness tracking, color |
+
+## Output Format
+
+1. **Indicator type recommendation** with rationale (determinate vs indeterminate).
+2. **Timing and animation guidance** -- duration thresholds, animation style, transitions.
+3. **Accessibility** -- VoiceOver progress announcements, live region updates.
+4. **Platform-specific behavior** across targeted platforms.
+
+## Questions to Ask
+
+1. Is the duration known or unknown?
+2. Which platforms?
+3. How long does the operation typically take?
+4. System-level or in-app indicator?
+
+## Related Skills
+
+- **hig-components-system** -- Widgets and complications displaying progress or status
+- **hig-inputs** -- Gestures triggering progress states (pull-to-refresh)
+- **hig-technologies** -- HealthKit for activity ring data; VoiceOver for progress announcements
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-status/references/activity-rings.md b/web-app/public/skills/hig-components-status/references/activity-rings.md
new file mode 100644
index 00000000..b129e551
--- /dev/null
+++ b/web-app/public/skills/hig-components-status/references/activity-rings.md
@@ -0,0 +1,105 @@
+---
+title: "Activity rings | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/activity-rings
+
+# Activity rings
+
+Activity rings show an individual’s daily progress toward Move, Exercise, and Stand goals.
+
+
+
+In watchOS, the Activity ring element always contains three rings, whose colors and meanings match those the Activity app provides. In iOS, the Activity ring element contains either a single Move ring representing an approximation of activity, or all three rings if an Apple Watch is paired.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Best-practices)
+
+**Display Activity rings when they’re relevant to the purpose of your app.** If your app is related to health or fitness, and especially if it contributes information to HealthKit, people generally expect to find Activity rings in your interface. For example, if you structure a workout or health session around the completion of Activity rings, consider displaying the element on a workout metrics screen so that people can track their progress during their session. Similarly, if you provide a summary screen that appears at the conclusion of a workout, you could display Activity rings to help people check on their progress toward their daily goals.
+
+
+
+**Use Activity rings only to show Move, Exercise, and Stand information.** Activity rings are designed to consistently represent progress in these specific areas. Don’t replicate or modify Activity rings for other purposes. Never use Activity rings to display other types of data. Never show Move, Exercise, and Stand progress in another ring-like element.
+
+**Use Activity rings to show progress for a single person.** Never use Activity rings to represent data for more than one person, and make sure it’s obvious whose progress you’re showing by using a label, a photo, or an avatar.
+
+**Always keep the visual appearance of Activity rings the same, regardless of where you display them.** Follow these guidelines to provide a consistent experience:
+
+ * Never change the colors of the rings; for example, don’t use filters or modify opacity.
+
+ * Always display Activity rings on a black background.
+
+ * Prefer enclosing the rings and background within a circle. To do this, adjust the corner radius of the enclosing view rather than applying a circular mask.
+
+ * Ensure that the black background remains visible around the outermost ring. If necessary, add a thin, black stroke around the outer edge of the ring, and avoid including a gradient, shadow, or any other visual effect.
+
+ * Always scale the rings appropriately so they don’t seem disconnected or out of place.
+
+ * When necessary, design the surrounding interface to blend with the rings; never change the rings to blend with the surrounding interface.
+
+
+
+
+**To display a label or value that’s directly associated with an Activity ring, use the colors that match it.** To display the ring-specific labels _Move_ , _Exercise_ , and _Stand_ , or to display a person’s current and goal values for each ring, use the following colors, specified as RGB values.
+
+Move| Exercise| Stand
+---|---|---
+| | 
+
+**Maintain Activity ring margins.** An Activity ring element must include a minimum outer margin of no less than the distance between rings. Never allow other elements to crop, obstruct, or encroach upon this margin or the rings themselves.
+
+**Differentiate other ring-like elements from Activity rings.** Mixing different ring styles can lead to a visually confusing interface. If you must include other rings, use padding, lines, or labels to separate them from Activity rings. Color and scale can also help provide visual separation.
+
+**Don’t send notifications that repeat the same information the Activity app sends.** The system already delivers Move, Exercise, and Stand progress updates, so it’s confusing for people to receive redundant information from your app. Also, don’t show an Activity ring element in your app’s notifications. It’s fine to reference Activity progress in a notification, but do so in a way that’s unique to your app and doesn’t replicate the same information the system provides.
+
+**Don’t use Activity rings for decoration.** Activity rings provide information to people; they don’t just embellish your app’s design. Never display Activity rings in labels or background graphics.
+
+**Don’t use Activity rings for branding.** Use Activity rings strictly to display Activity progress in your app. Never use Activity rings in your app’s icon or marketing materials.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Platform-considerations)
+
+ _No additional considerations for iPadOS or watchOS. Not supported in macOS, tvOS, or visionOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/activity-rings#iOS)
+
+Activity rings are available in iOS with [`HKActivityRingView`](https://developer.apple.com/documentation/HealthKitUI/HKActivityRingView). The appearance of the Activity ring element changes automatically depending on whether an Apple Watch is paired:
+
+ * With an Apple Watch paired, iOS shows all three Activity rings.
+
+ * Without an Apple Watch paired, iOS shows the Move ring only, which represents an approximation of a person’s activity based on their steps and workout information from other apps.
+
+
+
+
+
+
+Apple Watch paired
+
+
+
+No Apple Watch paired
+
+Because iOS shows Activity rings whether or not an Apple Watch is paired, activity history can include a combination of both styles. For example, Activity rings in Fitness have three rings when a person exercises with their Apple Watch paired, and only the Move ring when they exercise without their Apple Watch.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Related)
+
+[Workouts](https://developer.apple.com/design/human-interface-guidelines/workouts)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Developer-documentation)
+
+[`HKActivityRingView`](https://developer.apple.com/documentation/HealthKitUI/HKActivityRingView) — HealthKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Videos)
+
+[ Track workouts with HealthKit on iOS and iPadOS ](https://developer.apple.com/videos/play/wwdc2025/322)
+
+[ Build a workout app for Apple Watch ](https://developer.apple.com/videos/play/wwdc2021/10009)
+
+[ Build custom workouts with WorkoutKit ](https://developer.apple.com/videos/play/wwdc2023/10016)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/activity-rings#Change-log)
+
+Date| Changes
+---|---
+March 29, 2024| Enhanced guidance for displaying Activity rings and listed specific colors for displaying related content.
+December 5, 2023| Added artwork representing Activity rings in iOS.
+
diff --git a/web-app/public/skills/hig-components-status/references/progress-indicators.md b/web-app/public/skills/hig-components-status/references/progress-indicators.md
new file mode 100644
index 00000000..e268bf86
--- /dev/null
+++ b/web-app/public/skills/hig-components-status/references/progress-indicators.md
@@ -0,0 +1,116 @@
+---
+title: "Progress indicators | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/progress-indicators
+
+# Progress indicators
+
+Progress indicators let people know that your app isn’t stalled while it loads content or performs lengthy operations.
+
+
+
+Some progress indicators also give people a way to estimate how long they have to wait for something to complete. All progress indicators are transient, appearing only while an operation is ongoing and disappearing after it completes.
+
+Because the duration of an operation is either known or unknown, there are two types of progress indicators:
+
+ * _Determinate_ , for a task with a well-defined duration, such as a file conversion
+
+ * _Indeterminate_ , for unquantifiable tasks, such as loading or synchronizing complex data
+
+
+
+
+Both determinate and indeterminate progress indicators can have different appearances depending on the platform. A determinate progress indicator shows the progress of a task by filling a linear or circular track as the task completes. _Progress bars_ include a track that fills from the leading side to the trailing side. _Circular progress indicators_ have a track that fills in a clockwise direction.
+
+Progress bar
+
+Circular progress indicator
+
+An indeterminate progress indicator — also called an _activity indicator_ — uses an animated image to indicate progress. All platforms support a circular image that appears to spin; however, macOS also supports an indeterminate progress bar.
+
+macOS
+
+watchOS
+
+For developer guidance, see [`ProgressView`](https://developer.apple.com/documentation/SwiftUI/ProgressView).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Best-practices)
+
+**When possible, use a determinate progress indicator.** An indeterminate progress indicator shows that a process is occurring, but it doesn’t help people estimate how long a task will take. A determinate progress indicator can help people decide whether to do something else while waiting for the task to complete, restart the task at a different time, or abandon the task.
+
+**Be as accurate as possible when reporting advancement in a determinate progress indicator.** Consider evening out the pace of advancement to help people feel confident about the time needed for the task to complete. Showing 90 percent completion in five seconds and the last 10 percent in 5 minutes can make people wonder if your app is still working and can even feel deceptive.
+
+**Keep progress indicators moving so people know something is continuing to happen.** People tend to associate a stationary indicator with a stalled process or a frozen app. If a process stalls for some reason, provide feedback that helps people understand the problem and what they can do about it.
+
+**When possible, switch a progress bar from indeterminate to determinate.** If an indeterminate process reaches a point where you can determine its duration, switch to a determinate progress bar. People generally prefer a determinate progress indicator, because it helps them gauge what’s happening and how long it will take.
+
+**Don’t switch from the circular style to the bar style.** Activity indicators (also called _spinners_) and progress bars are different shapes and sizes, so transitioning between them can disrupt your interface and confuse people.
+
+**If it’s helpful, display a description that provides additional context for the task.** Be accurate and succinct. Avoid vague terms like _loading_ or _authenticating_ because they seldom add value.
+
+**Display a progress indicator in a consistent location.** Choosing a consistent location for a progress indicator helps people reliably find the status of an operation across platforms or within or between apps.
+
+**When it’s feasible, let people halt processing.** If people can interrupt a process without causing negative side effects, include a Cancel button. If interrupting the process might cause negative side effects — such as losing the downloaded portion of a file — it can be useful to provide a Pause button in addition to a Cancel button.
+
+**Let people know when halting a process has a negative consequence.** When canceling a process results in lost progress, it’s helpful to provide an [alert](https://developer.apple.com/design/human-interface-guidelines/alerts) that includes an option to confirm the cancellation or resume the process.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Platform-considerations)
+
+ _No additional considerations for tvOS or visionOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#iOS-iPadOS)
+
+#### [Refresh content controls](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Refresh-content-controls)
+
+A refresh control lets people immediately reload content, typically in a table view, without waiting for the next automatic content update to occur. A refresh control is a specialized type of activity indicator that’s hidden by default, becoming visible when people drag down the view they want to reload. In Mail, for example, people can drag down the list of Inbox messages to check for new messages.
+
+
+
+**Perform automatic content updates.** Although people appreciate being able to do an immediate content refresh, they also expect automatic refreshes to occur periodically. Don’t make people responsible for initiating every update. Keep data fresh by updating it regularly.
+
+**Supply a short title only if it adds value.** Optionally, a refresh control can include a title. In most cases, this is unnecessary, as the animation of the control indicates that content is loading. If you do include a title, don’t use it to explain how to perform a refresh. Instead, provide information of value about the content being refreshed. A refresh control in Podcasts, for example, uses a title to tell people when the last podcast update occurred.
+
+For developer guidance, see [`UIRefreshControl`](https://developer.apple.com/documentation/UIKit/UIRefreshControl).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#macOS)
+
+In macOS, an indeterminate progress indicator can have a bar or circular appearance. Both versions use an animated image to indicate that the app is performing a task.
+
+Indeterminate progress bar
+
+Indeterminate circular progress indicator
+
+**Prefer an activity indicator (spinner) to communicate the status of a background operation or when space is constrained.** Spinners are small and unobtrusive, so they’re useful for asynchronous background tasks, like retrieving messages from a server. Spinners are also good for communicating progress within a small area, such as within a text field or next to a specific control, such as a button.
+
+**Avoid labeling a spinning progress indicator.** Because a spinner typically appears when people initiate a process, a label is usually unnecessary.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#watchOS)
+
+By default the system displays the progress indicators in white over the scene’s background color. You can change the color of the progress indicator by setting its tint color.
+
+Progress bar
+
+Circular progress indicator
+
+Activity indicator
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Developer-documentation)
+
+[`ProgressView`](https://developer.apple.com/documentation/SwiftUI/ProgressView) — SwiftUI
+
+[`UIProgressView`](https://developer.apple.com/documentation/UIKit/UIProgressView) — UIKit
+
+[`UIActivityIndicatorView`](https://developer.apple.com/documentation/UIKit/UIActivityIndicatorView) — UIKit
+
+[`UIRefreshControl`](https://developer.apple.com/documentation/UIKit/UIRefreshControl) — UIKit
+
+[`NSProgressIndicator`](https://developer.apple.com/documentation/AppKit/NSProgressIndicator) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/progress-indicators#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Combined guidance common to all platforms.
+June 5, 2023| Updated guidance to reflect changes in watchOS 10.
+
diff --git a/web-app/public/skills/hig-components-status/references/status-bars.md b/web-app/public/skills/hig-components-status/references/status-bars.md
new file mode 100644
index 00000000..47f69951
--- /dev/null
+++ b/web-app/public/skills/hig-components-status/references/status-bars.md
@@ -0,0 +1,38 @@
+---
+title: "Status bars | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/status-bars
+
+# Status bars
+
+A status bar appears along the upper edge of the screen and displays information about the device’s current state, like the time, cellular carrier, and battery level.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/status-bars#Best-practices)
+
+**Obscure content under the status bar.** By default, the background of the status bar is transparent, allowing content beneath to show through. This transparency can make it difficult to see information presented in the status bar. If controls are visible behind the status bar, people may attempt to interact with them and be unable to do so. Be sure to keep the status bar readable, and don’t imply that content behind it is interactive. Prefer using a scroll edge effect to place a blurred view behind the status bar. For developer guidance, see [`ScrollEdgeEffectStyle`](https://developer.apple.com/documentation/SwiftUI/ScrollEdgeEffectStyle) and [`UIScrollEdgeEffect`](https://developer.apple.com/documentation/UIKit/UIScrollEdgeEffect).
+
+**Consider temporarily hiding the status bar when displaying full-screen media.** A status bar can be distracting when people are paying attention to media. Temporarily hide these elements to provide a more immersive experience. The Photos app, for example, hides the status bar and other interface elements when people browse full-screen photos.
+
+
+
+The Photos app with the status bar visible
+
+
+
+The Photos app with the status bar hidden
+
+**Avoid permanently hiding the status bar.** Without a status bar, people have to leave your app to check the time or see if they have a Wi-Fi connection. Let people redisplay a hidden status bar with a simple, discoverable gesture. For example, when browsing full-screen photos in the Photos app, a single tap shows the status bar again.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/status-bars#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/status-bars#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/status-bars#Developer-documentation)
+
+[`UIStatusBarStyle`](https://developer.apple.com/documentation/UIKit/UIStatusBarStyle) — UIKit
+
+[`preferredStatusBarStyle`](https://developer.apple.com/documentation/UIKit/UIViewController/preferredStatusBarStyle) — UIKit
+
diff --git a/web-app/public/skills/hig-components-system/SKILL.md b/web-app/public/skills/hig-components-system/SKILL.md
new file mode 100644
index 00000000..ccf7ed22
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/SKILL.md
@@ -0,0 +1,111 @@
+---
+name: hig-components-system
+version: 1.0.0
+description: ">"
+ Apple HIG guidance for system experience components: widgets, live activities,
+ notifications, complications, home screen quick actions, top shelf, watch faces,
+ app clips, and app shortcuts. Use when asked about: "widget design", "live activity",
+ "notification design", "complication", "home screen quick action",
+ "top shelf", "watch face", "app clip", "app shortcut", "system experience".
+ Also use when the user says "how do I design a widget," "what should my notification
+ look like," "how do Live Activities work," "should I make an App Clip," or asks about
+ surfaces outside the main app.
+ Cross-references: hig-components-status for progress in widgets, hig-inputs for
+ interaction patterns, hig-technologies for Siri and system integration.
+risk: unknown
+source: community
+---
+
+# Apple HIG: System Experiences
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+### General
+
+1. **Glanceable, immediate value.** System experiences bring your app's most important content to surfaces the user sees without launching your app. Design for seconds of attention.
+
+2. **Respect platform context.** A Lock Screen widget has different constraints than a Home Screen widget. A complication is far smaller than a top shelf item.
+
+### Widgets
+
+3. **Show relevant information, not everything.** Display the most useful subset, updated appropriately.
+
+4. **Support multiple sizes with distinct layouts.** Each size should be a thoughtful design, not a scaled version of another.
+
+5. **Deep-link on tap.** Take users to the relevant content, not the app's root screen.
+
+### Live Activities
+
+6. **Track events with a clear start and end.** Deliveries, scores, timers, rides. Design for both Dynamic Island and Lock Screen.
+
+7. **Stay updated and timely.** Stale data undermines trust. End promptly when the event concludes.
+
+### Notifications
+
+8. **Respect user attention.** Only send notifications for information users genuinely care about. No promotional or low-value notifications.
+
+9. **Actionable and self-contained.** Include enough context to understand and act without opening the app. Support notification actions. Use threading and grouping.
+
+### Complications
+
+10. **Focused data on the watch face.** Design for the smallest useful representation. Support multiple families. Budget updates wisely.
+
+### Home Screen Quick Actions
+
+11. **3-4 most common tasks.** Short titles, optional subtitles, relevant SF Symbol icons.
+
+### Top Shelf
+
+12. **tvOS showcase.** Feature content that entices: new episodes, featured items, recent content.
+
+### App Clips
+
+13. **Instant, focused functionality within a strict size budget.** Load quickly without App Store download. Only what's needed for the immediate task, then offer full app install.
+
+### App Shortcuts
+
+14. **Surface key actions to Siri and Spotlight.** Define shortcuts for frequent tasks. Use natural, conversational trigger phrases.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [widgets.md](references/widgets.md) | Widgets | Glanceable info, sizes, deep linking, timeline |
+| [live-activities.md](references/live-activities.md) | Live Activities | Real-time tracking, Dynamic Island, Lock Screen |
+| [notifications.md](references/notifications.md) | Notifications | Attention, actions, grouping, content |
+| [complications.md](references/complications.md) | Complications | Watch face data, families, budgeted updates |
+| [home-screen-quick-actions.md](references/home-screen-quick-actions.md) | Quick actions | Haptic Touch, common tasks, SF Symbols |
+| [top-shelf.md](references/top-shelf.md) | Top shelf | Featured content, showcase |
+| [app-clips.md](references/app-clips.md) | App Clips | Instant use, lightweight, focused task, NFC/QR |
+| [watch-faces.md](references/watch-faces.md) | Watch faces | Custom complications, face sharing |
+| [app-shortcuts.md](references/app-shortcuts.md) | App Shortcuts | Siri, Spotlight, voice triggers |
+
+## Output Format
+
+1. **System experience recommendation** -- which surface best fits the use case.
+2. **Content strategy** -- what to display, priority, what to omit.
+3. **Update frequency** -- refresh rate including system budget constraints.
+4. **Size/family variants** -- which to support and how layout adapts.
+5. **Deep link behavior** -- where tapping takes the user.
+
+## Questions to Ask
+
+1. What information needs to surface outside the app?
+2. Which platform?
+3. How frequently does the data update?
+4. What is the primary glanceable need?
+
+## Related Skills
+
+- **hig-components-status** -- Progress indicators in widgets or Live Activities
+- **hig-inputs** -- Interaction patterns for system experiences (Digital Crown for complications)
+- **hig-technologies** -- Siri for App Shortcuts, HealthKit for complications, NFC for App Clips
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-components-system/references/app-clips.md b/web-app/public/skills/hig-components-system/references/app-clips.md
new file mode 100644
index 00000000..62cf006f
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/app-clips.md
@@ -0,0 +1,387 @@
+---
+title: "App Clips | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/app-clips
+
+# App Clips
+
+An App Clip is a lightweight version of your app or game that provides an on-the-go or demo experience that’s instantly available.
+
+
+
+App Clips deliver an experience from your app or game without requiring people to download the full app from the App Store. App Clips focus on a fast solution to a task or contain a demo that showcases the full app or game, and they remain on the device for a limited amount of time while preserving people’s privacy.
+
+People discover and launch App Clips in a variety of situations and contexts. At a physical location, people launch an App Clip by scanning an App Clip Code, NFC tag, or a QR code. An App Clip Code tends to be the best way for people to discover and launch your App Clip because its distinct design is immediately recognizable, and people trust it to offer a fast, secure way to launch an App Clip.
+
+On their device, people launch an App Clip from location-based suggestions they permit in Siri Suggestions, the Maps app, Smart App Banners on websites, App Clip cards in Safari, and by tapping links others share with them in the Messages app. Starting with iOS 17, an app can include links and App Clip previews that people tap to launch another app’s App Clip.
+
+
+
+
+
+Consider creating an App Clip if your app provides an in-the-moment experience that helps people perform a task over a finite amount of time. For example:
+
+ * A rental bike could come with an App Clip Code that people tap or scan to launch an App Clip that lets them rent the bike.
+
+ * A coffee shop could offer an App Clip for fast advance orders that customers launch from a Smart App Banner or an App Clip card on the shop’s website. Customers could share a link to the website from the Messages app, which recipients then tap to launch the App Clip from within Messages.
+
+ * A food truck could create marketing material (for example, a poster to promote a seasonal dish) that includes an App Clip Code. People can scan the App Clip Code with the Camera app on their device and instantly launch the App Clip to order the seasonal dish.
+
+ * A restaurant could let diners pay for a meal by launching an App Clip from the Maps app or a suggestion from Siri Suggestions, or by holding their device close to an App Clip Code or NFC tag at their table.
+
+ * A museum could have visitors scan App Clip Codes or QR codes on labels next to displayed works to launch an App Clip that reveals augmented reality content or provides audio commentary.
+
+
+
+
+Consider creating an App Clip to let people experience your app or game before committing to a purchase or subscription. Focus on providing people with an opportunity to experience and understand your app or game. For example:
+
+ * A game might offer an App Clip that lets people play a demo version of the game, including a tutorial and the first level of the game.
+
+ * A fitness app might offer an App Clip with a free workout and a guided meditation.
+
+ * A text editor might allow people to create and save a document using the demo App Clip.
+
+
+
+
+For developer guidance, see [App Clips](https://developer.apple.com/documentation/AppClip).
+
+## [Designing your App Clip](https://developer.apple.com/design/human-interface-guidelines/app-clips#Designing-your-App-Clip)
+
+**Allow people to complete a task or a demo in your App Clip.** Don’t require people to install the full app to experience the entire demo, to complete a task, or to finish a level in a game.
+
+**Focus on essential features.** Interactions with App Clips are quick and focused. Limit features to what’s necessary to accomplish the task at hand. Reserve advanced or complex features for the app. If you offer a demo version of your full app, focus on essential features that give people a good sense of your game or your app’s functionality.
+
+**Don’t use App Clips solely for marketing purposes.** App Clips need to provide real value and help people accomplish tasks. Don’t use them as a means to advertise services or products, and don’t display ads in your App Clip.
+
+**Avoid using web views in your App Clip.** App Clips use native components and frameworks to offer an app-quality experience. If only web components are available to you, offer a quick link to your website instead of an App Clip.
+
+**Design a linear, easy-to-use, and focused user interface.** App Clips don’t need tab bars, complex navigation, or settings. Keep the number of screens and entry forms to a minimum. Remove extraneous information and reduce complexity in the user interface wherever possible.
+
+**On launch, show the most relevant part of your App Clip.** Skip unnecessary steps and take people immediately to the part of the App Clip that best fits their context.
+
+**Ensure people can use your App Clip immediately.** App Clips need to include all required assets, omit splash screens, and never make people wait on launch.
+
+**Ensure your App Clip is small.** The smaller your App Clip, the faster it will launch on a person’s device. Keeping your App Clip small is especially important when bandwidth is limited. As much as possible, reduce unnecessary code and remove unused assets. Avoid downloading additional data, which can take away the feeling of immediacy.
+
+**Make the App Clip shareable.** When someone shares a link to an App Clip in the Messages app, recipients can launch the App Clip from within the Messages app. Offer the ability to share links to specific points in your App Clip, and encourage people to share the App Clip with others.
+
+**Make it easy to pay for a service or product.** Entering payment information can be a long and error-prone task. Consider supporting [Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay) to offer express checkout and let people enter shipping information with no typing.
+
+**Avoid requiring people to create an account before they can benefit from your App Clip.** Creating an account is a complex task that takes time and effort. Consider not requiring an account, or think about asking people to create an account after they finish a task. If your App Clip requires an account to provide value, limit the amount of information people need to provide — for example, by offering [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple).
+
+**Provide a familiar, focused experience in your app.** When people install the full app, it replaces the App Clip on their device. From this moment, invocations that would have launched the App Clip launch the full app instead. Ensure your app provides a focused, familiar experience to people who previously used the App Clip. Don’t require additional steps that slow people down; for example, don’t require people to log in again when they transition from the App Clip to the app.
+
+### [Preserving privacy](https://developer.apple.com/design/human-interface-guidelines/app-clips#Preserving-privacy)
+
+The system imposes limits on App Clips to ensure people’s privacy. For example, App Clips can’t perform background operations. For developer guidance, see [Choosing the right functionality for your App Clip](https://developer.apple.com/documentation/AppClip/choosing-the-right-functionality-for-your-app-clip).
+
+**Limit the amount of data you store and handle yourself.** If you need to store people’s data — for example, login information — store it securely. In addition, don’t rely on the availability of data you previously stored on the device — the system may have removed the App Clip from the device between launches and deleted all of its data. If you store login information, securely store it off the device.
+
+**Consider offering Sign in with Apple.** Sign in with Apple securely retains login information off people’s devices and preserves their privacy. For guidance, see [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple).
+
+**Offer a secure way to pay for services or goods that also respects people’s privacy.** For example, consider offering [Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay).
+
+### [Showcasing your app](https://developer.apple.com/design/human-interface-guidelines/app-clips#Showcasing-your-app)
+
+People don’t manage App Clips themselves, and App Clips don’t appear on the Home screen. Instead, the system removes an App Clip after a period of inactivity.
+
+Because apps remain the best way to keep people engaged over time, the system helps them discover and install the full app:
+
+ * On the App Clip card, people can either launch the App Clip or visit the full app’s page on the App Store.
+
+ * When people first launch the App Clip, the system displays an app banner at the top of the screen. Like the App Clip card, the banner allows people to visit the app’s page on the App Store.
+
+
+
+
+In addition, you can display an overlay in your App Clip that allows people to download the full app from within the App Clip.
+
+**Don’t compromise the user experience by asking people to install the full app.** If your App Clip offers an on-the-go experience, consider whether the App Clip card and the system-provided app banner provide enough incentive for people to download the full app. If your App Clip offers a demo experience, let people fully experience the demo before asking them to install the full app.
+
+**Pick the right time to recommend your app.** When someone completes a task or reaches a natural pause, display an [`SKOverlay`](https://developer.apple.com/documentation/StoreKit/SKOverlay) that allows people to initiate a download of your full app or game from the context of the App Clip.
+
+**Recommend your app in a nonintrusive, polite way.** Don’t ask people to install the full app repeatedly or interrupt them during a task. Push notifications aren’t a good way to ask people to install the app either. Clearly communicate your app’s additional features.
+
+For developer guidance, see [Recommending your app to App Clip users](https://developer.apple.com/documentation/AppClip/recommending-your-app-to-app-clip-users).
+
+### [Limiting notifications](https://developer.apple.com/design/human-interface-guidelines/app-clips#Limiting-notifications)
+
+App Clips provide the option to schedule and receive notifications for up to 8 hours after launch, enough time to follow up and complete most common tasks.
+
+**Only ask for permission to use notifications for an extended period of time if it’s really needed.** If your App Clip’s functionality spans more than a day, explicitly request permission to schedule and receive notifications. For example, a car rental company’s App Clip can ask for permission to send a notification that reminds people that they need to return a rented car soon.
+
+**Keep notifications focused.** Don’t send purely promotional notifications, and only use notifications in response to an explicit user action. If a person completes their task without leaving the App Clip, you might not need to send any notifications at all.
+
+**Use notifications to help people complete a task.** Notifications for an App Clip relate directly to the task the App Clip helps to accomplish. For example, an App Clip that helps people order food could send notifications related to a scheduled delivery.
+
+For developer guidance, see [Enabling notifications in App Clips](https://developer.apple.com/documentation/AppClip/enabling-notifications-in-app-clips).
+
+### [Creating App Clips for businesses](https://developer.apple.com/design/human-interface-guidelines/app-clips#Creating-App-Clips-for-businesses)
+
+If you’re a platform provider who services businesses, you may create several App Clip experiences in [App Store Connect](https://appstoreconnect.apple.com) and use a single App Clip to power them all. To people using the App Clip, it appears with the branding of an individual business or location instead of your own branding.
+
+**Use consistent branding.** When people see the App Clip card for a business, the brand for that business is front and center. Tone down your own branding and make sure the branding for the business is clearly visible to avoid confusing people when they enter the App Clip experience.
+
+**Consider multiple businesses.** An App Clip may power many different businesses or a business that has multiple locations. In both scenarios, people may end up using the App Clip for more than one business or location at a time. The App Clip must handle this use case and update its user interface accordingly. For example, consider a way to switch between recent businesses or locations within your App Clip, and verify a person’s location when they launch it.
+
+For developer guidance, see [Configuring App Clip experiences](https://developer.apple.com/documentation/AppClip/configuring-the-launch-experience-of-your-app-clip).
+
+## [Creating content for an App Clip card](https://developer.apple.com/design/human-interface-guidelines/app-clips#Creating-content-for-an-App-Clip-card)
+
+The system-provided App Clip card is people’s first interaction with your App Clip, so give careful consideration to its images and copy.
+
+**Be informative.** Make sure the image on the App Clip card clearly communicates the features offered by your App Clip, supported tasks, or content.
+
+**Prefer photography and graphics.** Avoid using a screenshot of your app’s user interface because it’s unlikely to communicate the purpose of your App Clip. Instead, use an image that helps people understand the App Clip’s value, or a photo of the location of its associated business or point of interest.
+
+**Avoid using text.** Text in the header image isn’t localizable, can be difficult to read, and can make a card image less aesthetically pleasing.
+
+**Adhere to image requirements.** Use a 1800x1200 px PNG or JPEG image without transparency.
+
+**Use concise copy.** An App Clip card requires both a title and a subtitle. Clearly express the purpose of your App Clip within the available space so people can read and understand it at a glance. Create a title that has no more than 30 characters and a subtitle that has no more than 56 characters.
+
+**Pick a verb for the action button that best fits your App Clip.** Possible verbs are _View_ , _Play_ , or _Open_. Pick _View_ for media, or if your App Clip provides informational or educational content. Pick _Play_ for games. Choose _Open_ for all other App Clips.
+
+
+
+## [App Clip Codes](https://developer.apple.com/design/human-interface-guidelines/app-clips#App-Clip-Codes)
+
+App Clip Codes are the best way for people to discover your App Clip. Their distinct design is immediately recognizable, and they offer a fast, secure way to launch your App Clip.
+
+App Clip Code with the App Clip logo
+
+App Clip Code without the App Clip logo
+
+App Clip Codes always use the designs Apple provides and follow size, placement, and printing guidelines. Choose between the badge design that uses the App Clip logo ( App Clip) or, when space is at a premium, a design without it. Create App Clip Codes that use a default color pair, or choose custom foreground and background colors. For developer guidance, see [Creating App Clip Codes](https://developer.apple.com/documentation/AppClip/creating-app-clip-codes).
+
+### [Interacting with App Clip Codes](https://developer.apple.com/design/human-interface-guidelines/app-clips#Interacting-with-App-Clip-Codes)
+
+App Clip Codes come in two variants: _scan-only_ or with an embedded NFC tag (_NFC-integrated_).
+
+
+
+The scan-only variant uses a camera icon in its center to let people know to use the Camera app or the Code Scanner in Control Center to scan the App Clip Code. The NFC-integrated variant uses an iPhone icon at its center that guides people to hold their device close to the App Clip Code or to scan it using the NFC Tag Reader in Control Center. People can also scan an NFC-integrated App Clip Code with the Camera app or the Code Scanner in Control Center. For example:
+
+ * A coffee shop could place an App Clip Code on their menu. A guest could hold their device close to the App Clip Code and instantly launch the shop’s App Clip to order a drink.
+
+ * A gas station could have an NFC-integrated App Clip Code attached to each pump. A traveler could hold their device close to it to launch the gas station’s App Clip and use it to pay for their refill.
+
+ * A video game creator could hand out marketing material at an industry event that includes an App Clip Code. An event attendee could scan the code to launch an App Clip that’s a playable demo of their latest video game.
+
+
+
+
+
+
+### [Displaying App Clip Codes](https://developer.apple.com/design/human-interface-guidelines/app-clips#Displaying-App-Clip-Codes)
+
+When you start designing your App Clip Codes, choose the variant that works best for the way people use your App Clip. If people can physically access the App Clip Code, use the NFC-integrated variant. For example:
+
+ * On a tabletop at a restaurant
+
+ * Near a register at a retail store
+
+ * In a storefront window
+
+ * On signage
+
+ * On a gift card or coupon
+
+
+
+
+If you need to place your App Clip Code in an area that’s physically inaccessible or you need to display it digitally, use a scan-only App Clip Code. For example:
+
+ * On posters or printed advertising
+
+ * On signage behind a counter or unreachable in a storefront
+
+ * On digital materials such as digital displays, in emails, or on images you post to social media
+
+
+
+
+No matter which of the two variants you use, it’s important you carefully consider where you place your App Clip Code to ensure a reliable scanning experience.
+
+**Include the App Clip logo when space allows.** The logo helps make it clear that the code launches an App Clip; however, if you can’t meet the clear space requirements, use the App Clip Code design without the App Clip logo. Also, use the design without the App Clip logo if you place the App Clip Code on disposable paper or plastic items, or on items associated with gambling or drinking. For example, use the App Clip Code without the App Clip logo on playing cards, poker chips, or bar coasters. The App Clip logo is always part of the badge design where it appears below the App Clip Code; never use the App Clip logo on its own.
+
+**Place your App Clip Code on a flat or cylindrical surface only.** If you place your App Clip Code on a cylindrical surface — for example, on a scooter’s handlebar — make sure the width of the App Clip Code doesn’t exceed one-sixth of the cylinder’s circumference.
+
+
+
+**Help your App Clip Code remain as flat as possible so it’s easy for people to scan.** To provide the best scanning experience, avoid displaying App Clip Codes on deformable materials that readily fold or crumple, such as paper, plastic, or fabric. If you need to make your App Clip Code available on a bag, flexible box, or other deformable object, display it on something rigid — like a card — that you attach to the object. If you create an App Clip Code sticker, make sure it adheres well to flat surfaces.
+
+**Place your App Clip Code in a location that helps ensure reliable scanning.** For example, place a scan-only App Clip Code in a location that offers enough light to ensure reliable scanning, and don’t require people to scan from a wide angle.
+
+**Make sure the App Clip Code is unobstructed.** Don’t overlay the App Clip Code with text, logos, or images. Never animate the App Clip Code or dim it.
+
+**Display the App Clip Code in an upright position.** Don’t rotate the generated App Clip Code or display the center glyph at an angle.
+
+
+
+
+
+
+
+
+
+
+
+
+
+**Don’t create App Clip Codes that are too small.** App Clip Codes must adhere to the following specifications.
+
+Type| Minimum size
+---|---
+Printed communications| Minimum diameter of 3/4 inch (1.9 cm).
+Digital communications| Minimum size of 256×256 px. Use a PNG or SVG file.
+NFC-integrated App Clip Code| The embedded NFC tag needs to be at least 35 mm in diameter or of equivalent size. For example, if your embedded NFC tag is 35 mm in diameter, your printed App Clip Code needs to be at least 1.37 inches (3.48 cm) in diameter.
+
+
+
+
+
+When determining the dimensions of your App Clip Codes, consider a distance to code size ratio of no more than 20:1. If possible, use a ratio of 10:1 to ensure reliable scanning. For example, an App Clip that people scan from 40 inches (101 cm) away needs to be at least 4 inches (10.16 cm) in diameter.
+
+If you display an App Clip Code near a QR Code or other scannable item, choose a size for the App Clip Code that’s at least the other code’s or item’s size.
+
+
+
+**Provide enough space between an App Clip Code and adjacent App Clip Codes, graphics, or materials.** The minimum clear space around an App Clip Code is equal to the space between the center glyph and the circular code. If you place your App Clip Code next to another App Clip Code or other machine-readable code, leave enough clear space to allow for reliable scanning of each code.
+
+
+
+### [Using clear messaging](https://developer.apple.com/design/human-interface-guidelines/app-clips#Using-clear-messaging)
+
+Add clear messaging that informs people how they can use the App Clip Code to launch your App Clip, especially if you use the design without the App Clip logo. For example, add a call to action next to an App Clip Code you display in an email or on a poster. Use the suggested call-to-action messaging or your own copy. Always use a simple, clear call to action.
+
+
+
+For a scan-only App Clip Code, you can use the following call to action:
+
+ * Scan to [_describe what people can do with your App Clip_].
+
+ * Scan using the camera on your iPhone or iPad to [describe what people can do with your App Clip].
+
+
+
+
+For an NFC-integrated App Clip Code, you can use the following call to action:
+
+ * Scan to [_describe what people can do with your App Clip_].
+
+ * Hold your iPhone near the [_object name_] to launch an App Clip that [_describe what a person can do with your App Clip_].
+
+
+
+
+For more information, see [NFC](https://developer.apple.com/design/human-interface-guidelines/nfc).
+
+**Adhere to[Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html) when referring to your App Clip and App Clip Codes.** For example, Apple trademarks can’t appear in your app name or images, always use title case when using the terms App Clips or App Clip Code, and so on. For additional information, see [Legal requirements](https://developer.apple.com/design/human-interface-guidelines/app-clips#Legal-requirements).
+
+### [Customizing your App Clip Code](https://developer.apple.com/design/human-interface-guidelines/app-clips#Customizing-your-App-Clip-Code)
+
+Use [App Store Connect](https://appstoreconnect.apple.com) or the [App Clip Code Generator](https://developer.apple.com/app-clips/resources/) command-line tool to create App Clip Codes, and follow best practices to ensure a reliable scanning experience.
+
+
+
+**Always use the generated App Clip Code.** Don’t create your own App Clip Code design or modify a generated App Clip Code in any way. Don’t apply filters, augment its colors, or add glows, shadows, gradients, or reflections. They negatively impact people’s scanning experience. When scaling a generated App Clip Code, don’t change the generated code’s aspect ratio, and be sure to scale all attributes of the App Clip Code — for example the stroke widths.
+
+
+
+
+
+
+
+
+
+
+
+
+
+**Choose colors with enough contrast that ensure accurate scanning.** Each App Clip Code uses three colors: a foreground color, a background color, and a third color that’s generated for you based on the foreground and background colors. Both [App Store Connect](https://appstoreconnect.apple.com) and the [App Clip Code Generator](https://developer.apple.com/app-clips/resources/) command-line tool offer a selection of default color pairs. Alternatively, you can choose custom foreground and background colors. Note that you can’t choose custom colors that will lead to a suboptimal scanning experience. If your color selection doesn’t work well, neither App Store Connect nor the command-line tool will generate an App Clip Code. To help you choose a color combination that works well, both tools contain functionality to suggest a different foreground color based on your custom background color. For more information, see [Creating App Clip Codes with the App Clip Code Generator](https://developer.apple.com/documentation/AppClip/creating-app-clip-codes-with-the-app-clip-code-generator) and [Creating App Clip Codes with App Store Connect](https://developer.apple.com/documentation/AppClip/creating-app-clip-codes-with-app-store-connect).
+
+
+
+## [Printing guidelines](https://developer.apple.com/design/human-interface-guidelines/app-clips#Printing-guidelines)
+
+App Clip Codes offer the best experience to launch App Clips. As a result, it’s important to manufacture and display App Clip Codes that offer a reliable scanning experience for a long time. You can print App Clip Codes yourself, or work with a professional printing service — for example, [RR Donnelley](https://touchless.acc.rrd.com/).
+
+Always test printed App Clip Codes before you distribute them to be sure they’re scannable from a variety of angles.
+
+**Use high-quality, non-textured print materials.** Print App Clip Codes on matte finishes. Avoid shine, gloss, reflective or holographic overlays, as well as thin laminate finishes or materials. In case you need to laminate print material with an App Clip Code on it, use a matte laminate to avoid shine and reflections. If you place your App Clip Code outdoors, use UV-resistant materials or coatings to prevent fading from exposure to sunlight, rain, and other weather conditions. If you work with a professional printing service, use flexographic printing for best results. If you print the App Clip Codes yourself using a desktop printer, use an inkjet printer for best results.
+
+**Use high-resolution images and printer settings.** When rasterizing the SVG file, set the image resolution to at least 600 ppi, and print your App Clip Codes with a minimum resolution of 300 dpi. Consider leveling and calibrating your printer before printing to ensure a high print quality, and avoid poor color channel alignment, inaccurate gamma values, artifacts, or printing elliptical or otherwise distorted App Clip Codes. When using receipt printers, print App Clip Codes as close to the paper’s maximum bounds as possible.
+
+**Use correct color settings when you convert the generated SVG file to a CMYK image.** Both the [App Clip Code Generator](https://developer.apple.com/app-clips/resources/) command-line tool and [App Store Connect](https://appstoreconnect.apple.com) generate App Clip Codes as SVG files in the sRGB color space. To print colors that match the SVG file, convert the sRGB image to a CMYK image. Use a relative calorimetric (media-relative) intent when performing the conversion. Use “Generic CMYK ICC profile” on CMYK printers or “Gracol 2013 ICC profile” on CMYKOV printers and allow for a color tolerance CIELab Delta E of 2.5.
+
+**If you’re using a printer that only prints in grayscale, only generate grayscale App Clip Codes.** Codes generated in color and then printed in grayscale may work less reliably.
+
+**For NFC-integrated App Clip Codes, choose Type 5 NFC tags.** The embedded NFC tag needs to be at least 35 mm in diameter or of equivalent size.
+
+**If you create large batches of App Clip Codes, thoroughly test your printing workflow, and verify printed App Clip Codes.** For example, conduct small, inexpensive print runs using a subset of codes. Print your App Clip Codes on print templates with additional padded regions that allow you to display the encoded invocation URL and the SVG filename alongside each code for validation at the time of print.
+
+If you create many App Clip Codes with the [App Clip Code Generator](https://developer.apple.com/app-clips/resources/) tool or [App Store Connect](https://appstoreconnect.apple.com), you’ll likely work with a professional printing service. If this is the case, you need to handle a lot of SVG files. Because you have no way of knowing which App Clip Code encodes which URL by looking at an App Clip Code, you need to use a file that contains information about which SVG file maps to which invocation URL. Under any circumstance, careful file management, versioning, and change tracking are key to avoiding faulty print runs. For more information, see [Preparing multiple App Clip Codes for production](https://developer.apple.com/documentation/AppClip/preparing-multiple-app-clip-codes-for-production).
+
+### [Verifying your printer’s calibration](https://developer.apple.com/design/human-interface-guidelines/app-clips#Verifying-your-printers-calibration)
+
+A reliable scanning experience depends on the quality of your printed App Clip Codes. To ensure printing App Clip Codes results in a reliable scanning experience and to avoid using a printer that can’t print high-quality App Clip Codes, Apple offers [printer calibration test sheets](https://developer.apple.com/app-clips/resources/printer-calibration-test-sheets.zip) you can use to verify your printer’s settings and print quality.
+
+**Verify print quality of your chosen color pair with the printer calibration test sheet that shows text boxes for each default color pair.** Follow the instructions on the sheet to print it at the right scale and to verify that your printer can create high-quality App Clip Codes.
+
+**Verify your printer’s grayscale settings by printing the printer calibration test sheet that shows two grayscale bars.** If any of the specific gray colors are light or entirely missing, the printer may need calibration or may not be suitable for printing an App Clip Code that allows for reliable scanning.
+
+## [Legal requirements](https://developer.apple.com/design/human-interface-guidelines/app-clips#Legal-requirements)
+
+Only the Apple-provided App Clip Codes created in App Store Connect or with the App Clip Code Generator command-line tool and that follow these guidelines are approved for use.
+
+App Clip Codes are approved for use to indicate availability of an App Clip. Apple may update the App Clip Code design from time to time at Apple’s discretion.
+
+In the event your App Clip is no longer active, also stop displaying the App Clip Code associated with that inactive App Clip.
+
+You may not use the App Clip Code (including, without limitation, the Apple Logo, the App Clip mark, and the App Clip Code designs) as part of your own company name or as part of your product name. You may not seek copyright or trademark registration for the App Clip Codes or any elements contained therein.
+
+The App Clip Codes described in these guidelines must not be used in any manner that is likely to reduce, diminish, or damage the goodwill, value, or reputation associated with Apple or App Clips; or that infringes or violates the trademarks or other proprietary rights of any third party; or that is likely to cause confusion as to the source of products or services.
+
+Apple retains all rights to its trademarks, copyrights, or other intellectual property rights contained in the materials provided for use hereunder, including, without limitation, the App Clip Codes and any elements contained therein.
+
+Don’t add a symbol to App Clip Codes created in App Store Connect or with the App Clip Code Generator command-line tool.
+
+Don’t translate any Apple trademark. Apple trademarks must remain in English even when they appear within text in a language other than English. With Apple’s approval, a translation of the legal notice and credit lines (but not the trademarks) can be used in materials distributed outside the U.S.
+
+For more information about using Apple trademarks, see [Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/app-clips#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/app-clips#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/app-clips#Related)
+
+[Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay)
+
+[Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple)
+
+[Guidelines for Using Apple Trademarks and Copyrights](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/app-clips#Developer-documentation)
+
+[App Clips](https://developer.apple.com/documentation/AppClip)
+
+[App Store Connect](https://appstoreconnect.apple.com/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/app-clips#Videos)
+
+[ What's new in App Clips ](https://developer.apple.com/videos/play/wwdc2021/10012)
+
+[ Build light and fast App Clips ](https://developer.apple.com/videos/play/wwdc2021/10013)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/app-clips#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated guidance to include demo App Clips.
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-components-system/references/app-shortcuts.md b/web-app/public/skills/hig-components-system/references/app-shortcuts.md
new file mode 100644
index 00000000..6ff2c0ce
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/app-shortcuts.md
@@ -0,0 +1,114 @@
+---
+title: "App Shortcuts | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/app-shortcuts
+
+# App Shortcuts
+
+An App Shortcut gives people access to your app’s key functions or content throughout the system.
+
+
+
+People can initiate App Shortcuts using features like [Siri](https://developer.apple.com/design/human-interface-guidelines/siri), Spotlight, and the Shortcuts app; using hardware features like the [Action button](https://developer.apple.com/design/human-interface-guidelines/action-button) on iPhone or Apple Watch; or by [squeezing](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Squeeze) Apple Pencil.
+
+Because App Shortcuts are part of your app, they are available immediately when installation finishes. For example, a journaling app could offer an App Shortcut for making a new journal entry that’s available before a person opens the app for the first time. Once someone starts using your app, its App Shortcuts can reflect their choices, like those from FaceTime for calling recent contacts.
+
+
+
+App Shortcuts use [App Intents](https://developer.apple.com/documentation/AppIntents) to define actions within your app to make available to the system. Each App Shortcut includes one or more actions that represent a set of steps people might want to perform to accomplish a task. For example, a home security app might combine the two common actions of turning off the lights and locking exterior doors when a person goes to sleep at night into a single App Shortcut. Each app can include up to 10 App Shortcuts.
+
+Note
+
+When you use App Intents to make your app’s actions available to the system, in addition to the App Shortcuts that your app provides, people can also make their own custom shortcuts by combining actions in the Shortcuts app. Custom shortcuts give people flexibility to configure the behavior of actions, and enable workflows that perform tasks across multiple apps. For additional guidance, see the [Shortcuts User Guide](https://support.apple.com/guide/shortcuts/welcome/ios).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Best-practices)
+
+**Offer App Shortcuts for your app’s most common and important tasks.** Straightforward tasks that people can complete without leaving their current context work best, but you can also open your app if it helps people complete multistep tasks more easily.
+
+**Add flexibility by letting people choose from a set of options.** An App Shortcut can include a single optional value, or parameter, if it makes sense. For example, a meditation app could offer an App Shortcut that lets someone begin a specific type of meditation: “Start [morning, daily, sleep] meditation.” Include predictable and familiar values as options, because people won’t have the list in front of them for reference. For developer guidance, see [Adding parameters to an app intent](https://developer.apple.com/documentation/AppIntents/Adding-parameters-to-an-app-intent).
+
+
+
+**Ask for clarification in response to a request that’s missing optional information.** For example, someone might say “Start meditation” without specifying the type (morning, daily, or sleep); you could follow up by suggesting the one they used most recently, or one based on the current time of day. If one option is most likely, consider presenting it as the default, and provide a short list of alternatives to choose from if a person doesn’t want the default choice.
+
+**Keep voice interactions simple.** If your phrase feels too complicated when you say it aloud, it’s probably too difficult to remember or say correctly. For example, “Start [sleep] meditation with nature sounds” appears to have two possible parameters: the meditation type, and the accompanying sound. If additional information is absolutely required, ask for it in a subsequent step. For additional guidance on writing dialogue text for voice interactions, see [Siri](https://developer.apple.com/design/human-interface-guidelines/siri).
+
+**Make App Shortcuts discoverable in your app.** People are most likely to remember and use App Shortcuts for tasks they do often, once they know the shortcut is available. Consider showing occasional tips in your app when people perform common actions to let them know an App Shortcut exists. For developer guidance, see [`SiriTipUIView`](https://developer.apple.com/documentation/AppIntents/SiriTipUIView).
+
+### [Responding to App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Responding-to-App-Shortcuts)
+
+As a person engages with an App Shortcut, your app can respond in a variety of ways, including with dialogue that Siri speaks aloud and custom visuals like snippets and Live Activities.
+
+ * Snippets are great for custom views that display static information or dialog options, like showing the weather at a person’s location or confirming an order. For developer guidance, see [`ShowsSnippetView`](https://developer.apple.com/documentation/AppIntents/ShowsSnippetView).
+
+ * [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities) offer continuous access to information that’s likely to remain relevant and change over a period of time, and are great for timers and countdowns that appear until an event is complete. For developer guidance, see [`LiveActivityIntent`](https://developer.apple.com/documentation/AppIntents/LiveActivityIntent).
+
+
+
+
+
+
+
+
+**Provide enough detail for interaction on audio-only devices.** People can receive responses on audio-only devices such as AirPods and HomePod too, and may not always be able to see content onscreen. Include all critical information in the full dialogue text of your App Shortcuts. For developer guidance, see [`init(full:supporting:systemImageName:)`](https://developer.apple.com/documentation/AppIntents/IntentDialog/init\(full:supporting:systemImageName:\)).
+
+## [Editorial guidelines](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Editorial-guidelines)
+
+**Provide brief, memorable activation phrases and natural variants.** Because an App Shortcut phrase (or a variant you define) is what people say to run an App Shortcut with Siri, it’s important to keep it brief to make it easier to remember. You have to include your app name, but you can be creative with it. For example, Keynote accepts both “Create a Keynote” and “Add a new presentation in Keynote” as App Shortcut phrases for creating a new document. For developer guidance, see [`AppShortcutPhrase`](https://developer.apple.com/documentation/AppIntents/AppShortcutPhrase).
+
+**When referring to App Shortcuts or the Shortcuts app, always use title case and make sure that _Shortcuts_ is plural.** For example, _MyApp integrates with Shortcuts to provide a quick way to get things done with just a tap or by asking Siri, and offers App Shortcuts you can place on the Action button._
+
+**When referring to individual shortcuts (not App Shortcuts or the Shortcuts app), use lowercase.** For example, _Run a shortcut by asking Siri or tapping a suggestion on the Lock Screen._
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Platform-considerations)
+
+ _No additional considerations for visionOS or watchOS. Not supported in tvOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#iOS-iPadOS)
+
+App Shortcuts can appear in the Top Hit area of Spotlight when people search for your app, or in the Shortcuts area below. Each App Shortcut includes a symbol from [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) that you choose to represent its functionality, or a preview image of an item that the shortcut links to directly.
+
+
+
+**Order shortcuts based on importance.** The order you choose determines how App Shortcuts initially appear in both Spotlight and the Shortcuts app, so it’s helpful to include the most generally useful ones first. Once people start using your App Shortcuts, the system updates to prioritize the ones they use most frequently.
+
+**Offer an App Shortcut that starts a Live Activity.** Live Activities allow people to track an event or the progress of a task in glanceable locations across their devices. For example, a cooking app could offer a Live Activity to show the time left until a dish is ready to take out of the oven. To make it easy for people to start a cooking timer, the app offers an App Shortcut that people can place on the Action button. For more information about Live Activities, see [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#macOS)
+
+App Shortcuts aren’t supported in macOS. However, actions you create for your app using App Intents are supported, and people can build custom shortcuts using them with the Shortcuts app on Mac.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Related)
+
+[Siri](https://developer.apple.com/design/human-interface-guidelines/siri)
+
+[Siri Style Guide](https://developer.apple.com/siri/style-guide/)
+
+[Shortcuts User Guide](https://support.apple.com/guide/shortcuts/welcome/ios)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Developer-documentation)
+
+[App Intents](https://developer.apple.com/documentation/AppIntents)
+
+[SiriKit](https://developer.apple.com/documentation/SiriKit)
+
+[Making actions and content discoverable and widely available](https://developer.apple.com/documentation/AppIntents/Making-actions-and-content-discoverable-and-widely-available) — App Intents
+
+[Integrating custom data types into your intents](https://developer.apple.com/documentation/AppIntents/Integrating-custom-types-into-your-intents) — App Intents
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Videos)
+
+[ Design interactive snippets ](https://developer.apple.com/videos/play/wwdc2025/281)
+
+[ Get to know App Intents ](https://developer.apple.com/videos/play/wwdc2025/244)
+
+[ Bring your app’s core features to users with App Intents ](https://developer.apple.com/videos/play/wwdc2024/10210)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts#Change-log)
+
+Date| Changes
+---|---
+January 17, 2025| Updated and streamlined guidance.
+June 5, 2023| New page.
+
diff --git a/web-app/public/skills/hig-components-system/references/complications.md b/web-app/public/skills/hig-components-system/references/complications.md
new file mode 100644
index 00000000..2e833d51
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/complications.md
@@ -0,0 +1,425 @@
+---
+title: "Complications | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/complications
+
+# Complications
+
+A complication displays timely, relevant information on the watch face, where people can view it each time they raise their wrist.
+
+
+
+People often prefer apps that provide multiple, powerful complications, because it gives them quick ways to view the data they care about, even when they don’t open the app.
+
+Most watch faces can display at least one complication; some can display four or more.
+
+Starting in watchOS 9, the system organizes complications (also known as _accessories_) into several families — like [circular](https://developer.apple.com/design/human-interface-guidelines/complications#Circular) and [inline](https://developer.apple.com/design/human-interface-guidelines/complications#Inline) — and defines some recommended layouts you can use to display your complication data. A watch face can specify the family it supports in each complication slot. Complications that work in earlier versions of watchOS can use the [legacy templates](https://developer.apple.com/design/human-interface-guidelines/complications#Legacy-templates), which define nongraphic complication styles that don’t take on a wearer’s selected color.
+
+Developer note
+
+Prefer using [WidgetKit](https://developer.apple.com/documentation/WidgetKit) to develop complications for watchOS 9 and later. For guidance, see [Migrating ClockKit complications to WidgetKit](https://developer.apple.com/documentation/WidgetKit/Converting-A-ClockKit-App). To support earlier versions of watchOS, continue to implement the ClockKit complication data source protocol (see [`CLKComplicationDataSource`](https://developer.apple.com/documentation/ClockKit/CLKComplicationDataSource)).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/complications#Best-practices)
+
+**Identify essential, dynamic content that people want to view at a glance.** Although people can use a complication to quickly launch an app, the complication behavior they appreciate more is the display of relevant information that always feels up to date. A static complication that doesn’t display meaningful data may be less likely to remain in a prominent position on the watch face.
+
+**Support all complication families when possible.** Supporting more families means that your complications are available on more watch faces. If you can’t display useful information for a particular complication family, provide an image that represents your app — like your app icon — that still lets people launch your app from the watch face.
+
+**Consider creating multiple complications for each family.** Supporting multiple complications helps you take advantage of shareable watch faces and lets people configure a watch face that’s centered on an app they love. For example, an app that helps people train for triathlons could offer three circular complications — one for each segment of the race — each of which deep-links to the segment-specific area in the app. This app could also offer a shareable watch face that’s preconfigured to include its swimming, biking, and running complications and to use its custom images and colors. When people choose this watch face, they don’t have to do any configuration before they can start using it. For guidance, see [Watch faces](https://developer.apple.com/design/human-interface-guidelines/watch-faces).
+
+**Define a different deep link for each complication you support.** It works well when each complication opens your app to the most relevant area. If all the complications you support open the same area in your app, they can seem less useful.
+
+**Keep privacy in mind.** With the Always-On Retina display, information on the watch face might be visible to people other than the wearer. Make sure you help people prevent potentially sensitive information from being visible to others. For guidance, see [Always On](https://developer.apple.com/design/human-interface-guidelines/always-on).
+
+**Carefully consider when to update data.** You provide a complication’s data in the form of a timeline where each entry has a value that specifies the time at which to display your data on the watch face. Different data sets might require different time values. For example, a meeting app might display information about an upcoming meeting an hour before the meeting starts, but a weather app might display forecast information at the time those conditions are expected to occur. You can update the timeline a limited number of times each day, and the system stores a limited number of timeline entries for each app, so you need to choose times that enhance the usefulness of your data. For developer guidance, see [Migrating ClockKit complications to WidgetKit](https://developer.apple.com/documentation/WidgetKit/Converting-A-ClockKit-App#Configure-your-timeline-provider).
+
+## [Visual design](https://developer.apple.com/design/human-interface-guidelines/complications#Visual-design)
+
+**Choose a ring or gauge style based on the data you need to display.** Many families support a ring or gauge layout that provides consistent ways to represent numerical values that can change over time. For example:
+
+ * The closed style can convey a value that’s a percentage of a whole, such as for a battery gauge.
+
+ * The open style works well when the minimum and maximum values are arbitrary — or don’t represent a percentage of the whole — like for a speed indicator.
+
+ * Similar to the open style, the segmented style also displays values within an app-defined range, and can convey rapid value changes, such as in the Noise complication.
+
+
+
+
+**Make sure images look good in tinted mode.** In tinted mode, the system applies a solid color to a complication’s text, gauges, and images, and desaturates full-color images unless you provide tinted versions of them. For developer guidance, see [`WidgetRenderingMode`](https://developer.apple.com/documentation/WidgetKit/WidgetRenderingMode). (If you’re using legacy templates, tinted mode applies only to graphic complications.) To help your complications perform well in tinted mode:
+
+ * Avoid using color as the only way to communicate important information. You want people to get the same information in tinted mode as they do in nontinted mode.
+
+ * When necessary, provide an alternative tinted-mode version of a full-color image. If your full-color image doesn’t look good when it’s desaturated, you can supply a different version of the image for the system to use in tinted mode.
+
+
+
+
+**Recognize that people might prefer to use tinted mode for complications, instead of viewing them in full color.** When people choose tinted mode, the system automatically desaturates your complication, converting it to grayscale and tinting its images, gauges, and text using a single color that’s based on the wearer’s selected color.
+
+**When creating complication content, generally use line widths of two points or greater.** Thinner lines can be difficult to see at a glance, especially when the wearer is in motion. Use line weights that suit the size and complexity of the image.
+
+**Provide a set of static placeholder images for each complication you support.** The system uses placeholder images when there’s no other content to display for your complication’s data. For example, when people first install your app, the system can display a static placeholder while it checks to see if your app can generate a localized placeholder to use instead. Placeholder images can also appear in the carousel from which people select complications. Note that complication image sizes vary per layout (and per legacy template) and the size of a placeholder image may not match the size of the actual image you supply for that complication. For developer guidance, see [`placeholder(in:)`](https://developer.apple.com/documentation/WidgetKit/TimelineProvider/placeholder\(in:\)).
+
+## [Circular](https://developer.apple.com/design/human-interface-guidelines/complications#Circular)
+
+Circular layouts can include text, gauges, and full-color images in circular areas on the Infograph and Infograph Modular watch faces. The circular family also defines extra-large layouts for displaying content on the X-Large watch face.
+
+Closed gauge image
+
+Closed gauge text
+
+Open gauge image
+
+Open gauge text
+
+Open gauge range
+
+Image
+
+Stack image
+
+Stack text
+
+You can also add text to accompany a regular-size circular image, using a design that curves the text along the bezel of some watch faces, like Infograph. The text can fill nearly 180 degrees of the bezel before truncating.
+
+Closed gauge image
+
+As you design images for a regular-size circular complication, use the following values for guidance.
+
+Image| 40mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---
+Image| 42x42 pt (84x84 px @2x)| 44.5x44.5 pt (89x89 px @2x)| 47x47 pt (94x94 px @2x)| 50x50 pt (100x100 px @2x)
+Closed gauge| 27x27 pt (54x54 px @2x)| 28.5x28.5 pt (57x57 px @2x)| 31x31 pt (62x62 px @2x)| 32x32 pt (64x64 px @2x)
+Open gauge| 11x11 pt (22x22 px @2x)| 11.5x11.5 pt (23x23 px @2x)| 12x12 pt (24x24 px @2x)| 13x13 pt (26x26 px @2x)
+Stack (not text)| 28x14 pt (56x28 px @2x)| 29.5x15 pt (59X30 px @2x)| 31x16 pt (62x32px @ 2x)| 33.5x16.5 pt (67x33 px @2x)
+
+Note
+
+The system applies a circular mask to each image.
+
+A SwiftUI view that implements a regular-size circular complication uses the following default text values:
+
+ * Style: Rounded
+
+ * Weight: Medium
+
+ * Text size: 12 pt (40mm), 12.5 pt (41mm), 13 pt (44mm), 14.5 pt (45mm/49mm)
+
+
+
+
+If you want to design an oversized treatment of important information that can appear on the X-Large watch face — for example, the Contacts complication, which features a contact photo — use the extra-large versions of the circular family’s layouts. The following layouts let you display full-color images, text, and gauges in a large circular region that fills most of the X-Large watch face. Some of the text fields can support multicolor text.
+
+Closed gauge image
+
+Closed gauge text
+
+Open gauge image
+
+Open gauge text
+
+Open gauge range
+
+Image
+
+Stack image
+
+Stack text
+
+Use the following values for guidance as you create images for an extra-large circular complication.
+
+Image| 40mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---
+Image| 120x120 pt (240x240 px @2x)| 127x127 pt (254x254 px @2x)| 132x132 pt (264x264 px @2x)| 143x143 pt (286x286 px @2x)
+Open gauge| 31x31 pt (62x62 px @2x)| 33x33 pt (66x66 px @2x)| 33x33 pt (66x66 px @2x)| 37x37 pt (74x74 px @2x)
+Closed gauge| 77x77 pt (154x154 px @2x)| 81.5x81.5 (163x163 px @2x)| 87x87 pt (174x174 px @2x)| 91.5x91.5 (183x183 px @2x)
+Stack| 80x40 pt (160x80 px @2x)| 85x42 (170x84 px @2x)| 87x44 pt (174x88 px @2x)| 95x48 pt (190x96 px @2x )
+
+Note
+
+The system applies a circular mask to the circular, open-gauge, and closed-gauge images.
+
+Use the following values to create no-content placeholder images for your circular-family complications.
+
+Layout| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Circular| –| 42x42 pt (84x84 px @2x)| 44.5x44.5 pt (89x89 px @2x)| 47x47 pt (94x94 px @2x)| 50x50 pt (100x100 px @2x)
+Bezel| –| 42x42 pt (84x84 px @2x)| 44.5x44.5 pt (89x89 px @2x)| 47x47 pt (94x94 px @2x)| 50x50 pt (100x100 px @2x)
+Extra Large| –| 120x120 pt (240x240 px @2x)| 127x127 pt (254x254 px @2x)| 132x132 pt (264x264 px @2x)| 143x143 pt (286x286 px @2x)
+
+A SwiftUI view that implements an extra-large circular layout uses the following default text values:
+
+ * Style: Rounded
+
+ * Weight: Medium
+
+ * Text size: 34.5 pt (40mm), 36.5 pt (41mm), 36.5 pt (44mm), 41 pt (45mm/49mm)
+
+
+
+
+## [Corner](https://developer.apple.com/design/human-interface-guidelines/complications#Corner)
+
+Corner layouts let you display full-color images, text, and gauges in the corners of the watch face, like Infograph. Some of the templates also support multicolor text.
+
+Circular image
+
+Gauge image
+
+Gauge text
+
+Stack text
+
+Text image
+
+As you design images for a corner complication, use the following values for guidance.
+
+Image| 40mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---
+Circular| 32x32 pt (64x64 px @2x)| 34x34 pt (68x68 px @2x)| 36x36 pt (72x72 px @2x)| 38x38 pt (76x76 px @2x )
+Gauge| 20x20 pt (40x40 px @2x)| 21x21 pt (42x42 px @2x)| 22x22 pt (44x44 px @2x)| 24x24 pt (48x48 px @2x)
+Text| 20x20 pt (40x40 px @2x)| 21x21 pt (42x42 px @2x)| 22x22 pt (44x44 px @2x)| 24x24 pt (48x48 px @2x)
+
+Note
+
+The system applies a circular mask to each image.
+
+Use the following values to create no-content placeholder images for your corner-family complications.
+
+38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---
+–| 20x20 pt (40x40 px @2x)| 21x21 pt (42x42 px @2x)| 22x22 pt (44x44 px @2x)| 24x24 pt (48x48 px @2x)
+
+A SwiftUI view that implements a corner layout uses the following default text values:
+
+ * Style: Rounded
+
+ * Weight: Semibold
+
+ * Text size: 10 pt (40mm), 10.5 pt (41mm), 11 pt (44mm), 12 pt (45mm/49mm)
+
+
+
+
+## [Inline](https://developer.apple.com/design/human-interface-guidelines/complications#Inline)
+
+Inline layouts include utilitarian small and large layouts.
+
+Utilitarian small layouts are intended to occupy a rectangular area in the corner of a watch face, such as the Chronograph and Simple watch faces. The content can include an image, interface icon, or a circular graph.
+
+Flat
+
+Ring image
+
+Ring text
+
+Square
+
+As you design images for a utilitarian small layout, use the following values for guidance.
+
+Content| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Flat| 9-21x9 pt (18-42x18 px @2x)| 10-22x10 pt (20-44x20 px @2x)| 10.5-23.5x21 pt (21-47x21 @2x)| N/A| 12-26x12 pt (24-52x24 px @2x)
+Ring| 14x14 pt (28x28 px @2x)| 14x14 pt (28x28 px @2x)| 15x15 pt (30x30 px @2x)| 16x16 pt (32x32 px @2x)| 16.5x16.5 pt (33x33 px @2x)
+Square| 20x20 pt (40x40 px @2x)| 22x22 pt (44x44 px @2x)| 23.5x23.5 pt (47x47 px @2x)| 25x25 pt (50x50 px @2x)| 26x26 pt (52x52 px @2x)
+
+The utilitarian large layout is primarily text-based, but also supports an interface icon placed on the leading side of the text. This layout spans the bottom of a watch face, like the Utility or Motion watch faces.
+
+Large flat
+
+As you design images for a utilitarian large layout, use the following values for guidance.
+
+Content| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Flat| 9-21x9 pt (18-42x18 px @2x)| 10-22x10 pt (20-44x20 px @2x)| 10.5-23.5x10.5 pt (21-47x21 px @2x)| N/A| 12-26x12 pt (24-52x24 px @2x)
+
+## [Rectangular](https://developer.apple.com/design/human-interface-guidelines/complications#Rectangular)
+
+Rectangular layouts can display full-color images, text, a gauge, and an optional title in a large rectangular region. Some of the text fields can support multicolor text.
+
+The large rectangular region works well for showing details about a value or process that changes over time, because it provides room for information-rich charts, graphs, and diagrams. For example, the Heart Rate complication displays a graph of heart-rate values within a 24-hour period. The graph uses high-contrast white and red for the primary content and a lower-contrast gray for the graph lines and labels, making the data easy to understand at a glance.
+
+Starting with watchOS 10, if you have created a rectangular layout for your watchOS app, the system may display it in the Smart Stack. You can optimize this presentation in a few ways:
+
+ * By supplying background color or content that communicates information or aids in recognition
+
+ * By using [intents](https://developer.apple.com/documentation/appintents/app-intents) to specify relevancy, and help ensure that your widget is displayed in the Smart Stack at times that are most appropriate and useful to people
+
+ * By creating a custom layout of your information that is optimized for the Smart Stack
+
+
+
+
+For developer guidance, see [`WidgetFamily.accessoryRectangular`](https://developer.apple.com/documentation/WidgetKit/WidgetFamily/accessoryRectangular). See [Widgets](https://developer.apple.com/design/human-interface-guidelines/widgets) for additional guidance on designing widgets for the Smart Stack.
+
+Standard body
+
+Text gauge
+
+Large image
+
+Use the following values for guidance as you create images for a rectangular layout.
+
+Content| 40mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---
+Large image with title *| 150x47 pt (300x94 px @2x)| 159x50 pt (318x100 px @2x)| 171x54 pt (342x108 px @2x)| 178.5x56 pt (357x112 px @2x)
+Large image without title *| 162x69 pt (324x138 px @2x)| 171.5x73 pt (343x146 px @2x)| 184x78 pt (368x156 px @2x)| 193x82 pt (386x164 px @2x)
+Standard body| 12x12 pt (24x24 px @2x)| 12.5x12.5 pt (25x25 px @2x)| 13.5x13.5 pt (27x27 px @2x)| 14.5x14.5 pt (29x29 px @2x)
+Text gauge| 12x12 pt (24x24 px @2x)| 12.5x12.5 pt (25x25 px @2x)| 13.5x13.5 pt (27x27 px @2x)| 14.5x14.5 pt (29x29 px @2x)
+
+Note
+
+Both large-image layouts automatically include a four-point corner radius.
+
+A SwiftUI view that implements a rectangular layout uses the following default text values:
+
+ * Style: Rounded
+
+ * Weight: Medium
+
+ * Text size: 16.5 pt (40mm), 17.5 pt (41mm), 18 pt (44mm), 19.5 pt (45mm/49mm)
+
+
+
+
+## [Legacy templates](https://developer.apple.com/design/human-interface-guidelines/complications#Legacy-templates)
+
+### [Circular small](https://developer.apple.com/design/human-interface-guidelines/complications#Circular-small)
+
+Circular small templates display a small image or a few characters of text. They appear in the corner of the watch face (for example, in the Color watch face).
+
+Ring image
+
+Ring text
+
+Simple image
+
+Simple text
+
+Stack image
+
+Stack text
+
+As you design images for a circular small complication, use the following values for guidance.
+
+Image| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Ring| 20x20 pt (40x40 px @2x)| 22x22 pt (44x44 px @2x)| 23.5x23.5 pt (47x47 px @2x)| 24x24 pt (48x48 px @2x)| 26x26 pt (52x52 px @2x)
+Simple| 16x16 pt (32x32 px @2x)| 18x18 pt (36x36 px @2x)| 19x19 pt (38x38 px @2x)| 20x20 pt (40x40 px @2x)| 21.5x21.5 pt (43x43 px @2x)
+Stack| 16x7 pt (32x14 px @2x)| 17x8 pt (34x16 px @2x)| 18x8.5 pt (36x17 px @2x)| 19x9 pt (38x18 px @2x)| 19x9.5 pt (38x19 px @2x)
+Placeholder| 16x16 pt (32x32 px @2x)| 18x18x pt (36x36 px @2x)| 19x19 pt (38x38 px @2x)| 20x20 pt (40x40 px @2x)| 21.5x21.5 pt (43x43 px @2x)
+
+Note
+
+In each stack measurement, the width value represents the maximum size.
+
+### [Modular small](https://developer.apple.com/design/human-interface-guidelines/complications#Modular-small)
+
+Modular small templates display two stacked rows consisting of an icon and content, a circular graph, or a single larger item (for example, the bottom row of complications on the Modular watch face).
+
+Columns text
+
+Ring image
+
+Ring text
+
+Simple image
+
+Simple text
+
+Stack image
+
+Stack text
+
+As you design icons and images for a modular small complication, use the following values for guidance.
+
+Image| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Ring| 18x18 pt (36x36 px @2x)| 19x19 pt (38x38 px @2x)| 20x20 pt (40x40 px @2x)| 21x21 pt (42x42 px @2x)| 22.5x22.5 pt (45x45 px @2x)
+Simple| 26x26 pt (52x52 px @2x)| 29x29 pt (58x58 px @2x)| 30.5x30.5 pt (61x61 px @2x)| 32x32 pt (64x64 px @2x)| 34.5x34.5 pt (69x69 px @2x)
+Stack| 26x14 pt (52x28 px @2x)| 29x15 pt (58x30 px @2x)| 30.5x16 pt (61x32 px @2x)| 32x17 pt (64x34 px @2x)| 34.5x18 pt (69x36 px @2x)
+Placeholder| 26x26 pt (52x52 px @2x)| 29x29 pt (58x58 px @2x)| 30.5x30.5 pt (61x61 px @2x)| 32x32 pt (64x64 px @2x)| 34.5x34.5 pt (69x69 px @2x)
+
+Note
+
+In each stack measurement, the width value represents the maximum size.
+
+### [Modular large](https://developer.apple.com/design/human-interface-guidelines/complications#Modular-large)
+
+Modular large templates offer a large canvas for displaying up to three rows of content (for example, in the center of the Modular watch face).
+
+Columns
+
+Standard body
+
+Table
+
+Tall body
+
+As you design icons and images for a modular large complication, use the following values for guidance.
+
+Content| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Columns| 11-32x11 pt (22-64x22 px @2x)| 12-37x12 pt (24-74x24 px @2x)| 12.5-39x12.5 pt (25-78x25 px @2x)| 14-42x14 pt (28-84x28 px @2x)| 14.5-44x14.5 pt (29-88x29 px @2x)
+Standard body| 11-32x11 pt (22-64x22 px @2x)| 12-37x12 pt (24-74x24 px @2x)| 12.5-39x12.5 pt (25-78x25 px @2x)| 14-42x14 pt (28-84x28 px @2x)| 14.5-44x14.5 pt (29-88x29 px @2x)
+Table| 11-32x11 pt (22-64x22 px @2x)| 12-37x12 pt (24-74x24 px @2x)| 12.5-39x12.5 pt (25-78x25 px @2x)| 14-42x14 pt (28-84x28 px @2x)| 14.5-44x14.5 pt (29-88x29 px @2x)
+
+### [Extra large](https://developer.apple.com/design/human-interface-guidelines/complications#Extra-large)
+
+Extra large templates display larger text and images (for example, on the X-Large watch faces).
+
+Ring image
+
+Ring text
+
+Simple image
+
+Simple text
+
+Stack image
+
+Stack text
+
+As you design icons and images for an extra large complication, use the following values for guidance.
+
+Image| 38mm| 40mm/42mm| 41mm| 44mm| 45mm/49mm
+---|---|---|---|---|---
+Ring| 63x63 pt (126x126 px @2x)| 66.5x66.5 pt (133x133 px @2x)| 70.5x70.5 pt (141x141 px @2x)| 73x73 pt (146x146 px @2x)| 79x79 pt (158x158 px @2x)
+Simple| 91x91 pt (182x182 px @2x)| 101.5x101.5 pt (203x203 px @2x)| 107.5x107.5 pt (215x215 px @2x)| 112x112 pt (224x224 px @2x)| 121x121 pt (242x242 px @2x )
+Stack| 78x42 pt (156x84 px @2x)| 87x45 pt (174x90 px @2x)| 92x47.5 pt (184x95 px @2x)| 96x51 pt (192x102 px @2x)| 103.5x53.5 pt (207x107 px @2x)
+Placeholder| 91x91 pt (182x182 px @2x)| 101.5x101.5 pt (203x203 px @2x)| 107.5x107.5 pt (215x215 px @2x)| 112x112 pt (224x224 px @2x)| 121x121 pt (242x242 px @2x)
+
+Note
+
+In each stack measurement, the width value represents the maximum size.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/complications#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/complications#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/complications#Related)
+
+[Watch faces](https://developer.apple.com/design/human-interface-guidelines/watch-faces)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/complications#Developer-documentation)
+
+[WidgetKit](https://developer.apple.com/documentation/WidgetKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/complications#Videos)
+
+[ Design widgets for the Smart Stack on Apple Watch ](https://developer.apple.com/videos/play/wwdc2023/10309)
+
+[ Go further with Complications in WidgetKit ](https://developer.apple.com/videos/play/wwdc2022/10051)
+
+[ Complications and widgets: Reloaded ](https://developer.apple.com/videos/play/wwdc2022/10050)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/complications#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Replaced links to deprecated ClockKit documentation with links to WidgetKit documentation.
+June 5, 2023| Updated guidance for rectangular complications to support them as widgets in the Smart Stack.
+September 14, 2022| Added specifications for Apple Watch Ultra.
+
diff --git a/web-app/public/skills/hig-components-system/references/home-screen-quick-actions.md b/web-app/public/skills/hig-components-system/references/home-screen-quick-actions.md
new file mode 100644
index 00000000..ca4ca04d
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/home-screen-quick-actions.md
@@ -0,0 +1,42 @@
+---
+title: "Home Screen quick actions | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions
+
+# Home Screen quick actions
+
+Home Screen quick actions give people a way to perform app-specific actions from the Home Screen.
+
+
+
+People can get a menu of available quick actions when they touch and hold an app icon (on a 3D Touch device, people can press on the icon with increased pressure to see the menu). For example, Mail includes quick actions that open the Inbox or the VIP mailbox, initiate a search, and create a new message. In addition to app-specific actions, a Home Screen quick action menu also lists items for removing the app and editing the Home Screen.
+
+Each Home Screen quick action includes a title, an interface icon on the left or right (depending on your app’s position on the Home Screen), and an optional subtitle. The title and subtitle are always left-aligned in left-to-right languages. Your app can even dynamically update its quick actions when new information is available. For example, Messages provides quick actions for opening your most recent conversations.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions#Best-practices)
+
+**Create quick actions for compelling, high-value tasks.** For example, Maps lets people search near their current location or get directions home without first opening the Maps app. People tend to expect every app to provide at least one useful quick action; you can provide a total of four.
+
+**Avoid making unpredictable changes to quick actions.** Dynamic quick actions are a great way to keep actions relevant. For example, it may make sense to update quick actions based on the current location or recent activities in your app, time of day, or changes in settings. Make sure that actions change in ways that people can predict.
+
+**For each quick action, provide a succinct title that instantly communicates the results of the action.** For example, titles like “Directions Home,” “Create New Contact,” and “New Message” can help people understand what happens when they choose the action. If you need to give more context, provide a subtitle too. Mail uses subtitles to indicate whether there are unread messages in the Inbox and VIP folder. Don’t include your app name or any extraneous information in the title or subtitle, keep the text short to avoid truncation, and take localization into account as you write the text.
+
+**Provide a familiar interface icon for each quick action.** Prefer using [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) to represent actions. For a list of icons that represent common actions, see [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons); for additional guidance, see [Menus](https://developer.apple.com/design/human-interface-guidelines/menus).
+
+If you design your own interface icon, use the Quick Action Icon Template that’s included with [Apple Design Resources for iOS and iPadOS](https://developer.apple.com/design/resources/#ios-apps).
+
+**Don’t use an emoji in place of a symbol or interface icon.** Emojis are full color, whereas quick action symbols are monochromatic and change appearance in Dark Mode to maintain contrast.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions#Related)
+
+[Menus](https://developer.apple.com/design/human-interface-guidelines/menus)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions#Developer-documentation)
+
+[Add Home Screen quick actions](https://developer.apple.com/documentation/UIKit/add-home-screen-quick-actions) — UIKit
+
diff --git a/web-app/public/skills/hig-components-system/references/live-activities.md b/web-app/public/skills/hig-components-system/references/live-activities.md
new file mode 100644
index 00000000..4efc4239
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/live-activities.md
@@ -0,0 +1,442 @@
+---
+title: "Live Activities | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/live-activities
+
+# Live Activities
+
+A Live Activity lets people track the progress of an activity, event, or task at a glance.
+
+
+
+Live Activities let people keep track of tasks and events in glanceable locations across devices. They go beyond push notifications, delivering frequent content and status updates over a few hours and letting people interact with the displayed information.
+
+For example, a Live Activity might show the remaining time until a food delivery order arrives, live in-game information for a soccer match, or real-time fitness metrics and interactive controls to pause or cancel a workout.
+
+Live Activities start on iPhone or iPad and automatically appear in system locations across a person’s devices:
+
+Platform or system experience| Location
+---|---
+iPhone and iPad| Lock Screen, Home Screen, in the Dynamic Island and StandBy on iPhone
+Mac| The menu bar
+Apple Watch| Smart Stack
+CarPlay| CarPlay Dashboard
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/live-activities#Anatomy)
+
+Live Activities appear across the system in various locations like the _Dynamic Island_ and the Lock Screen. It serves as a unified home for alerts and indicators of ongoing activity. Depending on the device and system location where a Live Activity appears, the system chooses a _presentation_ style or a combination of styles to compose the appearance of your Live Activity. As a result, your Live Activity must support:
+
+ * [Compact](https://developer.apple.com/design/human-interface-guidelines/live-activities#Compact)
+
+ * [Minimal](https://developer.apple.com/design/human-interface-guidelines/live-activities#Minimal)
+
+ * [Expanded](https://developer.apple.com/design/human-interface-guidelines/live-activities#Expanded)
+
+ * [Lock Screen](https://developer.apple.com/design/human-interface-guidelines/live-activities#Lock-Screen)
+
+
+
+
+In iOS and iPadOS, your Live Activity appears throughout the system using these presentations. Additionally, the system uses them to create default appearances for other contexts. For example, the compact presentation appears in the Dynamic Island on iPhone and consists of two elements that the system combines into a single view for Apple Watch and in CarPlay.
+
+### [Compact](https://developer.apple.com/design/human-interface-guidelines/live-activities#Compact)
+
+In the Dynamic Island, the system uses the compact presentation when only one Live Activity is active. The presentation consists of two separate elements: one on the leading side of the TrueDepth camera and one on the trailing side. Despite its limited space, the compact presentation displays up-to-date information about your app’s Live Activity.
+
+
+
+For design guidance, see [Compact presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Compact-presentation).
+
+### [Minimal](https://developer.apple.com/design/human-interface-guidelines/live-activities#Minimal)
+
+When multiple Live Activities are active, the system uses the minimal presentation to display two of them in the Dynamic Island. One appears attached to the Dynamic Island while the other appears detached. Depending on its content size, the detached minimal presentation appears circular or oval. As with the compact presentation, people tap the minimal presentation to open its app or touch and hold it to see the expanded presentation.
+
+
+
+For design guidance, see [Minimal presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Minimal-presentation).
+
+### [Expanded](https://developer.apple.com/design/human-interface-guidelines/live-activities#Expanded)
+
+When people touch and hold a Live Activity in compact or minimal presentation, the system displays the expanded presentation.
+
+
+
+For design guidance, see [Expanded presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Expanded-presentation).
+
+### [Lock Screen](https://developer.apple.com/design/human-interface-guidelines/live-activities#Lock-Screen)
+
+The system uses the Lock Screen presentation to display a banner at the bottom of the Lock Screen. In this presentation, use a layout similar to the expanded presentation.
+
+
+
+When you alert people about Live Activity updates on devices that don’t support the Dynamic Island, the Lock Screen presentation briefly appears as a banner that overlays the Home Screen or other apps.
+
+
+
+For design guidance, see [Lock Screen presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Lock-Screen-presentation).
+
+### [StandBy](https://developer.apple.com/design/human-interface-guidelines/live-activities#StandBy)
+
+On iPhone in StandBy, your Live Activity appears in the minimal presentation. When someone taps it, it transitions to the Lock Screen presentation, scaled up by 2x to fill the screen. If your Lock Screen presentation uses a custom background color, the system automatically extends it to the whole screen to create a seamless, full-screen design.
+
+
+
+For design guidance, see [StandBy presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#StandBy-presentation).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/live-activities#Best-practices)
+
+**Offer Live Activities for tasks and events that have a defined beginning and end.** Live Activities work best for tracking short to medium duration activities that don’t exceed eight hours.
+
+**Focus on important information that people need to see at a glance.** Your Live Activity doesn’t need to display everything. Think about what information people find most useful and prioritize sharing it in a concise way. When a person wants to learn more, they can tap your Live Activity to open your app where you can provide additional detail.
+
+**Don’t use a Live Activity to display ads or promotions**. Live Activities help people stay informed about ongoing events and tasks, so it’s important to display only information that’s related to those events and tasks.
+
+**Avoid displaying sensitive information.** Live Activities are prominently visible and could be viewed by casual observers; for example, on the Lock Screen or in the Always-On display. For content people might consider sensitive or private, display an innocuous summary and let people tap the Live Activity to view the sensitive information in your app. Alternatively, redact views that may contain sensitive information and let people configure whether to show sensitive data. For developer guidance, see [Creating a widget extension](https://developer.apple.com/documentation/WidgetKit/Creating-a-Widget-Extension#Hide-sensitive-content).
+
+**Create a Live Activity that matches your app’s visual aesthetic and personality in both dark and light appearances.** This makes it easier for people to recognize your Live Activity and creates a visual connection to your app.
+
+**If you include a logo mark, display it without a container.** This better integrates the logo mark with your Live Activity layout. Don’t use the entire app icon.
+
+**Don’t add elements to your app that draw attention to the Dynamic Island.** Your Live Activity appears in the Dynamic Island while your app isn’t in use, and other items can appear in the Dynamic Island when your app is open.
+
+**Ensure text is easy to read.** Use large, heavier-weight text — a medium weight or higher. Use small text sparingly and make sure key information is legible at a glance.
+
+
+
+
+
+
+
+
+
+### [Creating Live Activity layouts](https://developer.apple.com/design/human-interface-guidelines/live-activities#Creating-Live-Activity-layouts)
+
+**Adapt to different screen sizes and presentations.** Live Activities scale to fit various device screens. Create layouts and assets for various devices and scale factors, recognizing that the actual size on screen may vary or change. Ensure they look great everywhere by using the values in [Specifications](https://developer.apple.com/design/human-interface-guidelines/live-activities#Specifications) as guidance and providing appropriately sized content.
+
+**Adjust element size and placement for efficient use of space.** Create a layout that only uses the space you need to clearly display its content. Adapt the size and placement of elements in your Live Activity so they fit well together.
+
+**Use familiar layouts for custom views and layouts.** Templates with default system margins and recommended text sizes are available in [Apple Design Resources](https://developer.apple.com/design/resources/). Using them helps your Live Activity remain legible at a glance and fit in with the visual language of its surroundings; for example, the Smart Stack on Apple Watch.
+
+
+
+**Use consistent margins and concentric placement.** Use even, matching margins between rounded shapes and the edges of the Live Activity, including corners, to ensure a harmonious fit. This prevents elements from poking into the rounded shape of the Live Activity and creating visual tension. For example, when placing a rounded rectangle near a corner of your Live Activity, match its corner radius to the outer corner radius of the Live Activity by subtracting the margin and using a SwiftUI container to apply the correct corner radius. For developer guidance, see [`ContainerRelativeShape`](https://developer.apple.com/documentation/SwiftUI/ContainerRelativeShape).
+
+
+
+Keep content compact and snug within a margin that’s concentric to the outer edge of the Live Activity.
+
+
+
+
+
+
+
+
+
+**When separating a block of content, place it in an inset container shape or use a thick line.** Don’t draw content all the way to the edge of the Dynamic Island.
+
+
+
+
+
+
+
+
+
+
+
+
+
+Tip
+
+To align nonrounded content in the rounded corners of the Live Activity view, it may be helpful to blur the nonrounded content in your drawing tool. When the content is blurred, it may be easier to find the positioning that best aligns with the outer perimeter of the view.
+
+
+
+
+
+
+
+
+
+**Dynamically change the height of your Live Activity on the Lock Screen or in the expanded presentation.** When there’s less information to show, reduce the height of the Live Activity to only use the space needed for the content. When more information becomes available, increase the height to display additional content. For example, a rideshare app might display a more compact Live Activity without additional details while it locates a driver. The app’s height extends as more information is available to display the estimated pickup time, driver details, and so on.
+
+### [Choosing colors](https://developer.apple.com/design/human-interface-guidelines/live-activities#Choosing-colors)
+
+**Carefully consider using a custom background color and opacity.** You can’t customize background colors for compact, minimal, and expanded presentations. However, you can use a custom background color for the Lock Screen presentation. If you set a custom background color or image for the Lock Screen presentation, ensure sufficient contrast — especially for tint colors on devices that feature an Always-On display with reduced luminance.
+
+**Use color to express the character and identity of your app.** Live Activities in the Dynamic Island use a black opaque background. Consider using bold colors for text and objects to convey the personality and brand of your app. Bold colors make your Live Activity recognizable at a glance, stand out from other Live Activities, and feel like a small, glanceable part of your app. Additionally, bold colors can help reinforce the relationship between elements in the Live Activity itself.
+
+**Tint your Live Activity’s key line color so that it matches your content.** When the background is dark — for example, in Dark Mode — a key line appears around the Dynamic Island to distinguish it from other content. Choose a key line color that’s consistent with the color of other elements in your Live Activity. For developer guidance, see [Creating custom views for Live Activities](https://developer.apple.com/documentation/ActivityKit/creating-custom-views-for-live-activities#Use-custom-colors).
+
+### [Adding transitions and animating content updates](https://developer.apple.com/design/human-interface-guidelines/live-activities#Adding-transitions-and-animating-content-updates)
+
+In addition to extending and contracting transitions, Live Activities use system and custom animations with a maximum duration of two seconds. Note that the system doesn’t perform animations on Always-On displays with reduced luminance.
+
+**Use animations to reinforce the information you’re communicating and to bring attention to updates.** In addition to moving the position of elements, you can animate elements in and out with the default content-replace transition, or create custom transitions using scale, opacity, and movement. For example, a sports app might use numeric content transitions for score changes or fade a timer in and out when it reaches zero.
+
+**Animate layout changes.** Content updates can require a change to your Live Activity layout — for example, when it expands to fill the screen in StandBy or when more information becomes available. During the transition to a new layout, preserve as much of the existing layout as possible by animating existing elements to their new positions rather than removing and animating them back in.
+
+**Try to avoid overlapping elements.** Sometimes, it’s best to animate out certain elements and then re-animate them in at a new position to avoid colliding with other parts of your transition. For example, when animating items in lists, only animate the element that moves to a new position and use fade-in-and-out transitions for the other list items.
+
+For developer guidance, see [Animating data updates in widgets and Live Activities](https://developer.apple.com/documentation/WidgetKit/Animating-data-updates-in-widgets-and-live-activities).
+
+### [Offering interactivity](https://developer.apple.com/design/human-interface-guidelines/live-activities#Offering-interactivity)
+
+**Make sure tapping the Live Activity opens your app at the right location.** Take people directly to related details and actions — don’t make them navigate to find relevant information. For developer guidance on SwiftUI views that support deep linking to specific screens, see [Linking to specific app scenes from your widget or Live Activity](https://developer.apple.com/documentation/WidgetKit/Linking-to-specific-app-scenes-from-your-widget-or-Live-Activity).
+
+**Focus on simple, direct actions.** Buttons or toggles take up space that might otherwise display useful information. Only include interactive elements for essential functionality that’s directly related to your Live Activity and that people activate once or temporarily pause and resume, like music playback, workouts, or apps that access the microphone to record live audio. If you offer interactivity, prefer limiting it to a single element to help people avoid accidentally tapping the wrong control.
+
+**Consider letting people respond to event or progress updates.** If an update to your Live Activity is something that a person could respond to, consider offering a button or toggle to let people take action. For example, the Live Activity of a rideshare app could include a button to contact the driver while waiting for a ride to arrive.
+
+### [Starting, updating, and ending a Live Activity](https://developer.apple.com/design/human-interface-guidelines/live-activities#Starting-updating-and-ending-a-Live-Activity)
+
+**Start Live Activities at appropriate times, and make it easy for people to turn them off in your app.** People expect Live Activities to start and provide important updates for a task at hand or at specific times, even automatically. For example, they might expect a Live Activity to start after a food order, making a rideshare request, or when their favorite sports team’s match begins. However, Live Activities that appear unexpectedly can be surprising or even unwanted. Consider offering controls that allow people to turn off a Live Activity in the app view that corresponds to the activity. For example, a sports app may offer a button that lets people unfollow a game or team. When people can’t easily control the appearance of Live Activities from your app, they may choose to turn off Live Activities in Settings altogether.
+
+**Offer an App Shortcut that starts your Live Activity.** App Shortcuts expose functionality to the system, allowing access in various contexts. For example, create an App Shortcut that allows people to start your Live Activity using the Action button on iPhone. For more information, see [App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts).
+
+**Update a Live Activity only when new content is available.** If the underlying content or status remains the same, maintain the same display until the underlying content or status changes.
+
+**Alert people only for essential updates that require their attention.** Live Activity alerts light up the screen and by default play the notification sound to alert people about updates they shouldn’t miss. Alerts also show the expanded presentation in the Dynamic Island or a banner on devices that don’t support the Dynamic Island. To ensure your Live Activities provide the most value, avoid alerting people too often or with updates that aren’t crucial, and don’t use push notifications alongside Live Activities for the same updates.
+
+**Let people track multiple events efficiently with a single Live Activity.** Instead of creating separate Live Activities people need to jump between to track different events, prefer a single Live Activity that uses a dynamic layout and rotates through events. For example, a sports app could offer a single Live Activity that cycles through scored points, substitutions, and fouls across multiple matches.
+
+**Always end a Live Activity immediately when the task or event ends, and consider setting a custom dismissal time.** When a Live Activity ends, the system immediately removes it from the Dynamic Island and in CarPlay. On the Lock Screen, in the Mac menu bar, and the watchOS Smart Stack, it remains for up to four hours. Depending on the Live Activity, showing a summary may only be relevant for a brief time after it ends. Consider choosing a custom dismissal time that’s proportional to the duration of your Live Activity. In most cases, 15 to 30 minutes is adequate. For example, a rideshare app could end its Live Activity when a ride completes and remain visible for 30 minutes to allow people to view the ride summary and leave a tip. For developer guidance, refer to [Displaying live data with Live Activities](https://developer.apple.com/documentation/ActivityKit/displaying-live-data-with-live-activities#End-the-Live-Activity).
+
+## [Presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Presentation)
+
+Your Live Activity needs to support all locations, devices, and their corresponding appearances. Because it appears across systems at different dimensions, create Live Activity layouts that best support each place they appear.
+
+**Start with the iPhone design, then refine it for other contexts.** Create standard designs for each presentation first. Then, depending on the functionality that your Live Activity provides, design additional custom layouts for specific contexts like iPhone in StandBy, CarPlay, or Apple Watch. For more information about custom layouts, refer to [StandBy](https://developer.apple.com/design/human-interface-guidelines/live-activities#StandBy), [CarPlay](https://developer.apple.com/design/human-interface-guidelines/live-activities#CarPlay), and [watchOS](https://developer.apple.com/design/human-interface-guidelines/live-activities#watchOS).
+
+### [Compact presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Compact-presentation)
+
+**Focus on the most important information.** Use the compact presentation to show dynamic, up-to-date information that’s essential to the Live Activity and easy to understand. For example, a sports app could display two team logos and the score.
+
+**Ensure unified information and design of the compact presentations in the Dynamic Island.** Though the TrueDepth camera separates the leading and trailing elements, design them to read as a single piece of information, and use consistent color and typography to help create a connection between both elements.
+
+**Keep content as narrow as possible and ensure it’s snug against the TrueDepth camera.** Try not to obscure key information in the status bar, and don’t add padding between content and the TrueDepth camera. Maintain a balanced layout with similarly sized views for both leading and trailing elements; for example, use shortened units or less precise data to maintain appropriate width and balance.
+
+
+
+
+
+
+
+
+
+**Link to relevant app content.** When people tap a compact Live Activity, open your app directly to the related details. Ensure both leading and trailing elements link to the same screen.
+
+### [Minimal presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Minimal-presentation)
+
+**Ensure that your Live Activity is recognizable in the minimal presentation.** If possible, display updated information rather than just a logo, while ensuring people can quickly recognize your app. For example, the Timer app’s minimal Live Activity presentation displays the remaining time instead of a static icon.
+
+### [Expanded presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Expanded-presentation)
+
+**Maintain the relative placement of elements to create a coherent layout between presentations.** The expanded presentation is an enlarged version of the compact or minimal presentation. Ensure information and layouts expand predictably when the Live Activity expands.
+
+**Wrap content tightly around the TrueDepth camera.** Arrange content close to the TrueDepth camera, and try to avoid leaving too much room around it to use space more efficiently and to help diminish the camera’s presence.
+
+
+
+
+
+
+
+
+
+### [Lock Screen presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Lock-Screen-presentation)
+
+**Don’t replicate notification layouts.** Create a unique layout that’s specific to the information that appears in the Live Activity.
+
+**Choose colors that work well on a personalized Lock Screen.** People customize their Lock Screen with wallpapers, custom tint colors, and widgets. To make a Live Activity fit a custom Lock Screen aesthetic while remaining legible, use custom background or tint colors and opacity sparingly.
+
+**Make sure your design, assets, and colors look great and offer enough contrast in Dark Mode and on an Always-On display.** By default, a Live Activity on the Lock Screen uses a light background color in the light appearance and a dark background color in the dark appearance. If you use a custom background color, choose a color that works well in both modes or a different color for each appearance. Verify your choices on a device with an Always-On display with reduced luminance because the system adapts colors as needed in this appearance. For guidance, see [Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode) and [Always On](https://developer.apple.com/design/human-interface-guidelines/always-on); for developer guidance, see [About asset catalogs](https://help.apple.com/xcode/mac/current/#/dev10510b1f7).
+
+**Verify the generated color of the dismiss button.** The system automatically generates a matching dismiss button based on the background and foreground colors of your Live Activity. Verify that the generated color matches your design and adjust it if needed using [`activitySystemActionForegroundColor(_:)`](https://developer.apple.com/documentation/SwiftUI/View/activitySystemActionForegroundColor\(_:\)).
+
+**Use standard margins to align your design with notifications.** The standard layout margin for Live Activities on the Lock Screen is 14 points. While tighter margins may be appropriate for elements like graphics or buttons, avoid crowding the edges and creating a cluttered appearance. For developer guidance, see [`padding(_:_:)`](https://developer.apple.com/documentation/SwiftUI/View/padding\(_:_:\)).
+
+### [StandBy presentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#StandBy-presentation)
+
+**Update your layout for StandBy.** Make sure assets look great at the larger scale, and consider creating a custom layout that makes use of the extra space. For developer guidance, see [Creating custom views for Live Activities](https://developer.apple.com/documentation/ActivityKit/creating-custom-views-for-live-activities).
+
+**Consider using the default background color in StandBy.** The default background color seamlessly blends your Live Activity with the device bezel, achieves a softer look that integrates with a person’s surroundings, and allows the system to scale the Live Activity slightly larger because it doesn’t need to account for the margins around the TrueDepth camera.
+
+**Use standard margins and avoid extending graphic elements to the edge of the screen.** Without standard margins, content gets cut off as the Live Activity extends, making it feel broken.
+
+**Verify your design in Night Mode.** In Night Mode, the system applies a red tint to your Live Activity. Check that your Live Activity design uses colors that provide enough contrast in Night Mode.
+
+
+
+## [CarPlay](https://developer.apple.com/design/human-interface-guidelines/live-activities#CarPlay)
+
+In CarPlay, the system automatically combines the leading and trailing elements of the compact presentation into a single layout that appears on CarPlay Dashboard.
+
+Your Live Activity design applies to both CarPlay and Apple Watch, so design for both contexts. While Live Activities on Apple Watch can be interactive, the system deactivates interactive elements in CarPlay. For more information, refer to [watchOS](https://developer.apple.com/design/human-interface-guidelines/live-activities#watchOS) below. For developer guidance, refer to [Creating custom views for Live Activities](https://developer.apple.com/documentation/ActivityKit/creating-custom-views-for-live-activities).
+
+**Consider creating a custom layout if your Live Activity would benefit from larger text or additional information.** Instead of using the default appearance in CarPlay, declare support for a [`ActivityFamily.small`](https://developer.apple.com/documentation/WidgetKit/ActivityFamily/small) supplemental activity family.
+
+**Carefully consider including buttons or toggles in your custom layout.** In CarPlay, the system deactivates interactive elements in your Live Activity. If people are likely to start or observe your Live Activity while driving, prefer displaying timely content rather than buttons and toggles.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/live-activities#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in tvOS or visionOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/live-activities#macOS)
+
+Active Live Activities automatically appear in the Menu bar of a paired Mac using the compact, minimal, and expanded presentations. Clicking the Live Activity launches iPhone Mirroring to display your app.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/live-activities#watchOS)
+
+When a Live Activity begins on iPhone, it appears on a paired Apple Watch at the top of the Smart Stack. By default, the view displayed in the Smart Stack combines the leading and trailing elements from the Live Activity’s compact presentation on iPhone.
+
+If you offer a watchOS app and someone taps the Live Activity in the Smart Stack, it opens your watchOS app. Without a watchOS app, tapping opens a full-screen view with a button to open your app on the paired iPhone.
+
+**Consider creating a custom watchOS layout.** While the system provides a default view automatically, a custom layout designed for Apple Watch can show more information and add interactive functionality like a button or toggle.
+
+**Carefully consider including buttons or toggles in your custom layout.** The custom watchOS layout also applies to your Live Activity in CarPlay where the system deactivates interactive elements. If people are likely to start or observe your Live Activity while driving, don’t include buttons or toggles in your custom watchOS layout. For developer guidance, see [Creating custom views for Live Activities](https://developer.apple.com/documentation/ActivityKit/creating-custom-views-for-live-activities).
+
+iPhone compact view
+
+Default Smart Stack view
+
+Custom Smart Stack view
+
+**Focus on essential information and significant updates.** Use space in the Smart Stack as efficiently as possible and think of the most useful information that a Live Activity can convey:
+
+ * Progress, like the estimated arrival time of a delivery
+
+ * Interactive elements, like stopwatch or timer controls
+
+ * Significant updates, like sports score changes
+
+
+
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/live-activities#Specifications)
+
+When you design your Live Activities, use the following values for guidance.
+
+### [CarPlay dimensions](https://developer.apple.com/design/human-interface-guidelines/live-activities#CarPlay-dimensions)
+
+The system may scale your Live Activity to best fit a vehicle’s screen size and resolution. Use the listed values to verify your design:
+
+Live Activity size (pt)
+---
+240x78
+240x100
+170x78
+
+Test your designs with the CarPlay Simulator and the following configurations for Smart Display Zoom — available in in Settings > Display in CarPlay:
+
+Configuration| Resolution (pt)
+---|---
+Widescreen| 1920x720
+Portrait| 900x1200
+Standard| 800x480
+
+### [iOS dimensions](https://developer.apple.com/design/human-interface-guidelines/live-activities#iOS-dimensions)
+
+All values listed in the tables below are in points.
+
+Screen dimensions (portrait)| Compact leading| Compact trailing| Minimal (width given as a range)| Expanded (height given as a range)| Lock Screen (height given as a range)
+---|---|---|---|---|---
+430x932| 62.33x36.67| 62.33x36.67| 36.67–45x36.67| 408x84–160| 408x84–160
+393x852| 52.33x36.67| 52.33x36.67| 36.67–45x36.67| 371x84–160| 371x84–160
+
+The Dynamic Island uses a corner radius of 44 points, and its rounded corner shape matches the TrueDepth camera.
+
+Presentation type| Device| Dynamic Island width (pt)
+---|---|---
+Compact or minimal| iPhone 17 Pro Max| 250
+| iPhone 17 Pro| 230
+| iPhone Air| 250
+| iPhone 17| 230
+| iPhone 16 Pro Max| 250
+| iPhone 16 Pro| 230
+| iPhone 16 Plus| 250
+| iPhone 16| 230
+| iPhone 15 Pro Max| 250
+| iPhone 15 Pro| 230
+| iPhone 15 Plus| 250
+| iPhone 15| 230
+| iPhone 14 Pro Max| 250
+| iPhone 14 Pro| 230
+Expanded| iPhone 17 Pro Max| 408
+| iPhone 17 Pro| 371
+| iPhone Air| 408
+| iPhone 17| 371
+| iPhone 16 Pro Max| 408
+| iPhone 16 Pro| 371
+| iPhone 16 Plus| 408
+| iPhone 16| 371
+| iPhone 15 Pro Max| 408
+| iPhone 15 Pro| 371
+| iPhone 15 Plus| 408
+| iPhone 15| 371
+| iPhone 14 Pro Max| 408
+| iPhone 14 Pro| 371
+
+### [iPadOS dimensions](https://developer.apple.com/design/human-interface-guidelines/live-activities#iPadOS-dimensions)
+
+All values listed in the table below are in points.
+
+Screen dimensions (portrait)| Lock Screen (height given as a range)
+---|---
+1366x1024| 500x84–160
+1194x834| 425x84–160
+1012x834| 425x84–160
+1080x810| 425x84–160
+1024x768| 425x84–160
+
+### [macOS dimensions](https://developer.apple.com/design/human-interface-guidelines/live-activities#macOS-dimensions)
+
+Use the provided iOS dimensions.
+
+### [watchOS dimensions](https://developer.apple.com/design/human-interface-guidelines/live-activities#watchOS-dimensions)
+
+Live Activities in the Smart Stack use the same dimensions as watchOS widgets.
+
+Apple Watch size| Size of a Live Activity in the Smart Stack (pt)
+---|---
+40mm| 152x69.5
+41mm| 165x72.5
+44mm| 173x76.5
+45mm| 184x80.5
+49mm| 191x81.5
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/live-activities#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/live-activities#Developer-documentation)
+
+[ActivityKit](https://developer.apple.com/documentation/ActivityKit)
+
+[SwiftUI](https://developer.apple.com/documentation/SwiftUI)
+
+[WidgetKit](https://developer.apple.com/documentation/WidgetKit)
+
+[Developing a WidgetKit strategy](https://developer.apple.com/documentation/WidgetKit/Developing-a-WidgetKit-strategy) — WidgetKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/live-activities#Videos)
+
+[ Turbocharge your app for CarPlay ](https://developer.apple.com/videos/play/wwdc2025/216)
+
+[ What’s new in widgets ](https://developer.apple.com/videos/play/wwdc2025/278)
+
+[ Design Live Activities for Apple Watch ](https://developer.apple.com/videos/play/wwdc2024/10098)
+
+[ Design dynamic Live Activities ](https://developer.apple.com/videos/play/wwdc2023/10194)
+
+[ Meet ActivityKit ](https://developer.apple.com/videos/play/wwdc2023/10184)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/live-activities#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for all platforms, and added guidance for macOS and CarPlay.
+June 10, 2024| Added guidance for Live Activities in watchOS.
+October 24, 2023| Expanded and updated guidance and added new artwork.
+June 5, 2023| Updated guidance to include features of iOS 17 and iPadOS 17.
+November 3, 2022| Updated artwork and specifications.
+September 23, 2022| New page.
+
diff --git a/web-app/public/skills/hig-components-system/references/notifications.md b/web-app/public/skills/hig-components-system/references/notifications.md
new file mode 100644
index 00000000..0db65b19
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/notifications.md
@@ -0,0 +1,153 @@
+---
+title: "Notifications | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/notifications
+
+# Notifications
+
+A notification gives people timely, high-value information they can understand at a glance.
+
+
+
+Before you can send any notifications to people, you have to get their consent (for developer guidance, see [Asking permission to use notifications](https://developer.apple.com/documentation/UserNotifications/asking-permission-to-use-notifications)). After agreeing, people generally use settings to specify the styles of notification they want to receive, and to specify delivery times for notifications that have different levels of urgency. To learn more about the ways people can customize the notification experience, see [Managing notifications](https://developer.apple.com/design/human-interface-guidelines/managing-notifications).
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/notifications#Anatomy)
+
+Depending on the platform, a notification can use various styles, such as:
+
+ * A banner or view on a Lock Screen, Home Screen, Home View, or desktop
+
+ * A badge on an app icon
+
+ * An item in Notification Center
+
+
+
+
+In addition, a notification related to direct communication — like a phone call or message — can provide an interface that’s distinct from noncommunication notifications, featuring prominent contact images (or _avatars_) and group names instead of the app icon.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/notifications#Best-practices)
+
+**Provide concise, informative notifications.** People turn on notifications to get quick updates, so you want to provide valuable information succinctly.
+
+**Avoid sending multiple notifications for the same thing, even if someone hasn’t responded.** People attend to notifications at their convenience. If you send multiple notifications for the same thing, you fill up Notification Center, and people may turn off all notifications from your app.
+
+**Avoid sending a notification that tells people to perform specific tasks within your app.** If it makes sense to offer simple tasks that people can perform without opening your app, you can provide [notification actions](https://developer.apple.com/design/human-interface-guidelines/notifications#Notification-actions). Otherwise, avoid telling people what to do because it’s hard for people to remember such instructions after they dismiss the notification.
+
+**Use an alert — not a notification — to display an error message.** People are familiar with both alerts and notifications, so you don’t want to cause confusion by using the wrong component. For guidance, see [Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts).
+
+**Handle notifications gracefully when your app is in the foreground.** Your app’s notifications don’t appear when your app is in the front, but your app still receives the information. In this scenario, present the information in a way that’s discoverable but not distracting or invasive, such as incrementing a badge or subtly inserting new data into the current view. For example, when a new message arrives in a mailbox that people are currently viewing, Mail simply adds it to the list of unread messages because sending a notification about it would be unnecessary and distracting.
+
+**Avoid including sensitive, personal, or confidential information in a notification.** You can’t predict what people will be doing when they receive a notification, so it’s essential to avoid including private information that could be visible to others.
+
+## [Content](https://developer.apple.com/design/human-interface-guidelines/notifications#Content)
+
+When a notification includes a title, the system displays it at the top where it’s most visible. In a notification related to direct communication, the system automatically displays the sender’s name in the title area; in a noncommunication notification, the system displays your app name if you don’t provide a title.
+
+**Create a short title if it provides context for the notification content.** Prefer brief titles that people can read at a glance, especially on Apple Watch, where space is limited. When possible, take advantage of the prominent notification title area to provide useful information, like a headline, event name, or email subject. If you can only provide a generic title for a noncommunication notification — like New Document — it can be better to let the system display your app name instead. Use title-style [capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64) and no ending punctuation.
+
+**Write succinct, easy-to-read notification content.** Use complete sentences, sentence case, and proper punctuation, and don’t truncate your message — the system does this automatically when necessary.
+
+**Provide generically descriptive text to display when notification previews aren’t available.** In Settings, people can choose to hide notification previews for all apps. In this situation, the system shows only your app icon and the default title _Notification_. To give people sufficient context to know whether they want to view the full notification, write body text that succinctly describes the notification content without revealing too many details, like “Friend request,” “New comment,” “Reminder,” or “Shipment” (for developer guidance, see [`hiddenPreviewsBodyPlaceholder`](https://developer.apple.com/documentation/UserNotifications/UNNotificationCategory/hiddenPreviewsBodyPlaceholder)). Use sentence-style [capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64) for this text.
+
+**Avoid including your app name or icon.** The system automatically displays a large version of your app icon at the leading edge of each notification; in a communication notification, the system displays the sender’s contact image badged with a small version of your icon.
+
+**Consider providing a sound to supplement your notifications.** Sound can be a great way to distinguish your app’s notifications and get someone’s attention when they’re not looking at the device. You can create a custom sound that coordinates with the style of your app or use a system-provided alert sound. If you use a custom sound, make sure it’s short, distinctive, and professionally produced. A notification sound can enhance the user experience, but don’t rely on it to communicate important information, because people may not hear it. Although people might also want a vibration to accompany alert sounds, you can’t provide such a vibration programmatically. For developer guidance, see [`UNNotificationSound`](https://developer.apple.com/documentation/UserNotifications/UNNotificationSound).
+
+## [Notification actions](https://developer.apple.com/design/human-interface-guidelines/notifications#Notification-actions)
+
+A notification can present a customizable detail view that contains up to four buttons people use to perform actions without opening your app. For example, a Calendar event notification provides a Snooze button that postpones the event’s alarm for a few minutes. For developer guidance, see [Handling notifications and notification-related actions](https://developer.apple.com/documentation/UserNotifications/handling-notifications-and-notification-related-actions).
+
+**Provide beneficial actions that make sense in the context of your notification.** Prefer actions that let people perform common, time-saving tasks that eliminate the need to open your app. For each button, use a short, title-case term or phrase that clearly describes the result of the action. Don’t include your app name or any extraneous information in the button label, keep the text brief to avoid truncation, and take localization into account as you write it.
+
+**Avoid providing an action that merely opens your app.** When people tap a notification or its preview, they expect your app to display related content, so presenting an action button that does the same thing clutters the detail view and can be confusing.
+
+**Prefer nondestructive actions.** If you must provide a destructive action, make sure people have enough context to avoid unintended consequences. The system gives a distinct appearance to the actions you identify as destructive.
+
+**Provide a simple, recognizable interface icon for each notification action.** An interface icon reinforces an action’s meaning, helping people instantly understand what it does. The system displays your interface icon on the trailing side of the action title. When you use [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols), you can choose an existing symbol that represents your command or edit a related symbol to create a custom icon.
+
+## [Badging](https://developer.apple.com/design/human-interface-guidelines/notifications#Badging)
+
+A badge is a small, filled oval containing a number that can appear on an app icon to indicate the number of unread notifications that are available. After people address unread notifications, the badge disappears from the app icon, reappearing when new notifications arrive. People can choose whether to allow an app to display badges in their notification settings.
+
+**Use a badge only to show people how many unread notifications they have.** Don’t use a badge to convey numeric information that isn’t related to notifications, such as weather-related data, dates and times, stock prices, or game scores.
+
+**Make sure badging isn’t the only method you use to communicate essential information.** People can turn off badging for your app, so if you rely on it to show people when there’s important information, people can miss the message. Always make sure that you make important information easy for people to find as soon as they open your app.
+
+**Keep badges up to date.** Update your app’s badge as soon as people open the corresponding notifications. You don’t want people to think there are new notifications available, only to find that they’ve already viewed them all. Note that reducing a badge’s count to zero removes all related notifications from Notification Center.
+
+**Avoid creating a custom image or component that mimics the appearance or behavior of a badge.** People can turn off notification badges if they choose, and will become frustrated if they have done so and then see what appears to be a badge.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/notifications#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/notifications#watchOS)
+
+On Apple Watch, notifications occur in two stages: _short look_ and _long look_. People can also view notifications in Notification Center. On supported devices, people can double-tap to respond to notifications.
+
+You can help people have a great notification experience by designing app-specific assets and actions that are relevant on Apple Watch. If your watchOS app has an iPhone companion that supports notifications, watchOS can automatically provide default short-look and long-look interfaces if necessary.
+
+#### [Short looks](https://developer.apple.com/design/human-interface-guidelines/notifications#Short-looks)
+
+A short look appears when the wearer’s wrist is raised and disappears when it’s lowered.
+
+
+
+**Avoid using a short look as the only way to communicate important information.** A short look appears only briefly, giving people just enough time to see what the notification is about and which app sent it. If your notification information is critical, make sure you deliver it in other ways, too.
+
+**Keep privacy in mind.** Short looks are intended to be discreet, so it’s important to provide only basic information. Avoid including potentially sensitive information in the notification’s title.
+
+#### [Long looks](https://developer.apple.com/design/human-interface-guidelines/notifications#Long-looks)
+
+Long looks provide more detail about a notification. If necessary, people can swipe vertically or use the Digital Crown to scroll a long look. After viewing a long look, people can dismiss it by tapping it or simply by lowering their wrist.
+
+
+
+A custom long-look interface can be static or dynamic. The _static_ interface lets you display a notification’s message along with additional static text and images. The _dynamic_ interface gives you access to the notification’s full content and offers more options for configuring the appearance of the interface.
+
+You can customize the content area for both static and dynamic long looks, but you can’t change the overall structure of the interface. The system-defined structure includes a _sash_ at the top of the interface and a Dismiss button at the bottom, below all custom buttons.
+
+**Consider using a rich, custom long-look notification to let people get the information they need without launching your app.** You can use SwiftUI [Animations](https://developer.apple.com/documentation/SwiftUI/Animations) to create engaging, interruptible animations; alternatively, you can use [SpriteKit](https://developer.apple.com/documentation/SpriteKit) or [SceneKit](https://developer.apple.com/documentation/SceneKit).
+
+**At the minimum, provide a static interface; prefer providing a dynamic interface too.** The system defaults to the static interface when the dynamic interface is unavailable, such as when there is no network or the iPhone companion app is unreachable. Be sure to create the resources for your static interface in advance and package them with your app.
+
+**Choose a background appearance for the sash.** The system-provided sash, at the top of the long-look interface, displays your app icon and name. You can customize the sash’s color or give it a blurred appearance. If you display a photo at the top of the content area, you’ll probably want to use the blurred sash, which has a light, translucent appearance that gives the illusion of overlapping the image.
+
+**Choose a background color for the content area.** By default, the long look’s background is transparent. If you want to match the background color of other system notifications, use white with 18% opacity; otherwise, you can use a custom color, such as a color within your brand’s palette.
+
+**Provide up to four custom actions below the content area.** For each long look, the system uses the notification’s type to determine which of your custom actions to display as buttons in the notification UI. In addition, the system always displays a Dismiss button at the bottom of the long-look interface, below all custom buttons. If your watchOS app has an iPhone companion that supports notifications, the system shares the actionable notification types already registered by your iPhone app and uses them to configure your custom action buttons.
+
+#### [Double tap](https://developer.apple.com/design/human-interface-guidelines/notifications#Double-tap)
+
+People can double-tap to respond to notifications on supported devices. When a person responds to a notification with a double tap, the system selects the first nondestructive action as the response.
+
+**Keep double tap in mind when choosing the order of custom actions you present as responses to a notification.** Because a double tap runs the first nondestructive action, consider placing the action that people use most frequently at the top of the list. For example, a parking app that provides custom actions for extending the time on a paid parking spot could offer options to extend the time by 5 minutes, 15 minutes, or an hour, with the most common choice listed first.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/notifications#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/notifications#Related)
+
+[Managing notifications](https://developer.apple.com/design/human-interface-guidelines/managing-notifications)
+
+[Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/notifications#Developer-documentation)
+
+[Asking permission to use notifications](https://developer.apple.com/documentation/UserNotifications/asking-permission-to-use-notifications) — User Notifications
+
+[User Notifications UI](https://developer.apple.com/documentation/UserNotificationsUI)
+
+[User Notifications](https://developer.apple.com/documentation/UserNotifications)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/notifications#Videos)
+
+[ Send communication and Time Sensitive notifications ](https://developer.apple.com/videos/play/wwdc2021/10091)
+
+[ The Push Notifications primer ](https://developer.apple.com/videos/play/wwdc2020/10095)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/notifications#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Updated watchOS platform considerations with guidance for presenting notification responses to double tap.
+
diff --git a/web-app/public/skills/hig-components-system/references/top-shelf.md b/web-app/public/skills/hig-components-system/references/top-shelf.md
new file mode 100644
index 00000000..d835a2fa
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/top-shelf.md
@@ -0,0 +1,135 @@
+---
+title: "Top Shelf | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/top-shelf
+
+# Top Shelf
+
+The Apple TV Home Screen provides an area called Top Shelf, which showcases your content in a rich, engaging way while also giving people access to their favorite apps in the Dock.
+
+
+
+When you support full-screen Top Shelf, people can swipe through multiple full-screen content views, play trailers and previews, and get more information about your content.
+
+Top Shelf is a unique opportunity to highlight new, featured, or recommended content and let people jump directly to your app or game to view it. For example, when people select Apple TV in the Dock, full-screen previews immediately begin playing and soon the Dock slides away. As people watch previews for the first show, they can swipe through previews of all other featured shows, stopping to select Play or More Info for a preview that interests them.
+
+The system defines several layout templates that you can use to give people a compelling Top Shelf experience when they select your app in the Dock. To help you position content, you can download these templates from [Apple Design Resources](https://developer.apple.com/design/resources/#tvos-apps).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Best-practices)
+
+**Help people jump right into your content.** Top Shelf provides a path to the content people care about most. Two of the system-provided layout templates — [carousel actions](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Carousel-actions) and [carousel details](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Carousel-details) — each include two buttons by default: A primary button intended to begin playback and a More Info button intended to open your app to a view that displays details about the content.
+
+**Feature new content.** For example, showcase new releases or episodes, highlight upcoming movies and shows, and avoid promoting content that people have already purchased, rented, or watched.
+
+**Personalize people’s favorite content.** People typically put the apps they use most often into Top Shelf. You can personalize their experience by showing targeted recommendations in the Top Shelf content you supply, letting people resume media playback or jump back into active gameplay.
+
+**Avoid showing advertisements or prices.** People put your app into Top Shelf because you’ve already sold them on it, so they may not appreciate seeing lots of ads from your app. Showing purchasable content in the Top Shelf is fine, but prefer putting the focus on new and exciting content, and consider displaying prices only when people show interest.
+
+**Showcase compelling dynamic content that can help draw people in and encourage them to view more.** If necessary, you can supply static images, but people typically prefer a captivating, dynamic Top Shelf experience that features the newest or highest rated content. To provide this experience, prefer creating [layered images](https://developer.apple.com/design/human-interface-guidelines/images#Layered-images) to display in Top Shelf.
+
+**If you don’t provide the recommended full-screen content, supply at least one static image as a fallback.** The system displays a static image when your app is in the Dock and in focus and full-screen content is unavailable. tvOS flips and blurs the image, ensuring that it fits into a width of 1920 pixels at the 16:9 aspect ratio. Use the following values for guidance.
+
+Image size
+---
+2320x720 pt (2320x720 px @1x, 4640x1440 px @2x)
+
+**Avoid implying interactivity in a static image.** A static Top Shelf image isn’t focusable, and you don’t want to make people think it’s interactive.
+
+## [Dynamic layouts](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Dynamic-layouts)
+
+Dynamic Top Shelf images can appear in several ways:
+
+ * A carousel of full-screen video and images that includes two buttons and optional details
+
+ * A row of focusable content
+
+ * A set of scrolling banners
+
+
+
+
+### [Carousel actions](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Carousel-actions)
+
+The carousel actions layout style focuses on full-screen video and images and includes a few unobtrusive controls that help people see more. This layout style works especially well to showcase content that people already know something about. For example, it’s great for displaying user-generated content, like photos, or new content from a franchise or show that people are likely to enjoy.
+
+**Provide a title.** Include a succinct title, like the title of the show or movie or the title of a photo album. If necessary, you can also provide a brief subtitle. For example, a subtitle for a photo album could be a range of dates; a subtitle for an episode could be the name of the show.
+
+### [Carousel details](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Carousel-details)
+
+This layout style extends the carousel actions layout style, giving you the opportunity to include some information about the content. For example, you might provide information like a plot summary, cast list, and other metadata that helps people decide whether to choose the content.
+
+**Provide a title that identifies the currently playing content.** The content title appears near the top of the screen so it’s easy for people to read it at a glance. Above the title, you can also provide a succinct phrase or app attribution, like “Featured on _My App_.”
+
+### [Sectioned content row](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Sectioned-content-row)
+
+This layout style shows a single labeled row of sectioned content, which can work well to highlight recently viewed content, new content, or favorites. Row content is focusable, which lets people scroll quickly through it. A label appears when an individual piece of content comes into focus, and small movements on the remote’s Touch surface bring the focused image to life. You can also configure a sectioned content row to show multiple labels.
+
+**Provide enough content to constitute a complete row.** At a minimum, load enough images in a sectioned content row to span the full width of the screen. In addition, include at least one label for greater platform consistency and to provide additional context.
+
+You can use the following image sizes in a sectioned content row.
+
+#### [Poster (2:3)](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Poster-23)
+
+
+
+Aspect| Image size
+---|---
+Actual size| 404x608 pt (404x608 px @1x, 808x1216 px @2x)
+Focused/Safe zone size| 380x570 pt (380x570 px @1x, 760x1140 px @2x)
+Unfocused size| 333x570 pt (333x570 px @1x, 666x1140 px @2x)
+
+#### [Square (1:1)](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Square-11)
+
+
+
+Aspect| Image size
+---|---
+Actual size| 608x608 pt (608x608 px @1x, 1216x1216 px @2x)
+Focused/Safe zone size| 570x570 pt (570x570 px @1x, 1140x1140 px @2x)
+Unfocused size| 500x500 pt (500x500 px @1x, 1000x1000 px @2x)
+
+#### [16:9](https://developer.apple.com/design/human-interface-guidelines/top-shelf#169)
+
+
+
+Aspect| Image size
+---|---
+Actual size| 908x512 pt (908x512 px @1x, 1816x1024 px @2x)
+Focused/Safe zone size| 852x479 pt (852x479 px @1x, 1704x958 px @2x)
+Unfocused size| 782x440 pt (782x440 px @1x, 1564x880 px @2x)
+
+**Be aware of additional scaling when combining image sizes.** If your Top Shelf design includes a mixture of image sizes, keep in mind that images will automatically scale up to match the height of the tallest image if necessary. For example, a 16:9 image scales to 500 pixels high if included in a row with a poster or square image.
+
+#### [Scrolling inset banner](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Scrolling-inset-banner)
+
+This layout shows a series of large images, each of which spans almost the entire width of the screen. Apple TV automatically scrolls through these banners on a preset timer until people bring one into focus. The sequence circles back to the beginning after the final image is reached.
+
+When a banner is in focus, a small, circular gesture on the remote’s Touch surface enacts the system focus effect, animating the item, applying lighting effects, and, if the banner contains layered images, producing a 3D effect. Swiping on the Touch surface pans to the next or previous banner in the sequence. Use this style to showcase rich, captivating content, such as a popular new movie.
+
+**Provide three to eight images.** A minimum of three images is recommended for a scrolling banner to feel effective. More than eight images can make it hard to navigate to a specific image.
+
+**If you need text, add it to your image.** This layout style doesn’t show labels under content, so all text must be part of the image itself. In layered images, consider elevating text by placing it on a dedicated layer above the others. Add the text to the accessibility label of the image too, so [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover) can read it.
+
+
+
+Use the following size for a scrolling inset banner image:
+
+Aspect| Image size
+---|---
+Actual size| 1940x692 pt (1940x692 px @1x, 3880x1384 px @2x)
+Focused/Safe zone size| 1740x620 pt (1740x620 px @1x, 3480x1240 px @2x)
+Unfocused size| 1740x560 pt (1740x560 px @1x, 3480x1120 px @2x)
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#tvos-apps)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/top-shelf#Videos)
+
+[ Mastering the Living Room With tvOS ](https://developer.apple.com/videos/play/wwdc2019/211)
+
diff --git a/web-app/public/skills/hig-components-system/references/watch-faces.md b/web-app/public/skills/hig-components-system/references/watch-faces.md
new file mode 100644
index 00000000..75b39ac3
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/watch-faces.md
@@ -0,0 +1,40 @@
+---
+title: "Watch faces | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/watch-faces
+
+# Watch faces
+
+A watch face is a view that people choose as their primary view in watchOS.
+
+
+
+The watch face is at the heart of the watchOS experience. People choose a watch face they want to see every time they raise their wrist, and they customize it with their favorite complications. People can even customize different watch faces for different activities, so they can switch to the watch face that fits their current context.
+
+In watchOS 7 and later, people can share the watch faces they configure. For example, a fitness instructor might configure a watch face to share with their students by choosing the Gradient watch face, customizing the color, and adding their favorite health and fitness complications. When the students add the shared watch face to their Apple Watch or the Watch app on their iPhone, they get a custom experience without having to configure it themselves.
+
+You can also configure a watch face to share from within your app, on your website, or through Messages, Mail, or social media. Offering shareable watch faces can help you introduce more people to your complications and your app.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/watch-faces#Best-practices)
+
+**Help people discover your app by sharing watch faces that feature your complications.** Ideally, you support multiple complications so that you can showcase them in a shareable watch face and provide a curated experience. For some watch faces, you can also specify a system accent color, images, or styles. If people add your watch face but haven’t installed your app, the system prompts them to install it.
+
+**Display a preview of each watch face you share.** Displaying a preview that highlights the advantages of your watch face can help people visualize its benefits. You can get a preview by using the iOS Watch app to email the watch face to yourself. The preview includes an illustrated device bezel that frames the face and is suitable for display on websites and in watchOS and iOS apps. Alternatively, you can replace the illustrated bezel with a high-fidelity hardware bezel that you can download from [Apple Design Resources](https://developer.apple.com/design/resources/#product-bezels) and composite onto the preview. For developer guidance, see [Sharing an Apple Watch face](https://developer.apple.com/documentation/ClockKit/sharing-an-apple-watch-face).
+
+**Aim to offer shareable watch faces for all Apple Watch devices.** Some watch faces are available on Series 4 and later — such as California, Chronograph Pro, Gradient, Infograph, Infograph Modular, Meridian, Modular Compact, and Solar Dial — and Explorer is available on Series 3 (with cellular) and later. If you use one of these faces in your configuration, consider offering a similar configuration using a face that’s available on Series 3 and earlier. To help people make a choice, you can clearly label each shareable watch face with the devices it supports.
+
+**Respond gracefully if people choose an incompatible watch face.** The system sends your app an error when people try to use an incompatible watch face on Series 3 or earlier. In this scenario, consider immediately offering an alternative configuration that uses a compatible face instead of displaying an error. Along with the previews you provide, help people understand that they might receive an alternative watch face if they choose a face that isn’t compatible with their Apple Watch.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/watch-faces#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/watch-faces#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/watch-faces#Related)
+
+[Apple Design Resources — Product Bezels](https://developer.apple.com/design/resources/#product-bezels)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/watch-faces#Developer-documentation)
+
+[Sharing an Apple Watch face](https://developer.apple.com/documentation/ClockKit/sharing-an-apple-watch-face) — ClockKit
+
diff --git a/web-app/public/skills/hig-components-system/references/widgets.md b/web-app/public/skills/hig-components-system/references/widgets.md
new file mode 100644
index 00000000..09384383
--- /dev/null
+++ b/web-app/public/skills/hig-components-system/references/widgets.md
@@ -0,0 +1,517 @@
+---
+title: "Widgets | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/widgets
+
+# Widgets
+
+A widget provides quick access to essential information and focused interactions from your app or game in additional contexts.
+
+
+
+Widgets help people organize and personalize their devices by displaying timely, glanceable content and offering specific functionality. They appear in various contexts for a consistent experience across platforms. For example, a person might place a Weather widget:
+
+ * On the Home Screen and Lock Screen of their iPhone and iPad
+
+ * On the desktop and Notification Center of their Mac
+
+ * On a horizontal or vertical surface when they wear Apple Vision Pro
+
+ * At a fixed position in the Smart Stack of Apple Watch
+
+
+
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/widgets#Anatomy)
+
+Widgets come in different sizes, ranging from small accessory widgets on iPhone, iPad, and Apple Watch to system family widgets that include an extra large size on iPad, Mac, and Apple Vision Pro. Additionally, widgets adapt their appearance to the context in which they appear and respond to a person’s device customization. Consider the following aspects when you design widgets:
+
+ * The widget size to support
+
+ * The context — devices and system experiences — in which the widget may appear
+
+ * The rendering modes and color treatment that the widget receives based on the size and context
+
+
+
+
+The WidgetKit framework provides default appearances and treatments for each widget size to fit the system experience or device where it appears. However, it’s important to consider creating a custom widget design that can provide the best experience for your content in each specific context.
+
+### [System family widgets](https://developer.apple.com/design/human-interface-guidelines/widgets#System-family-widgets)
+
+System family widgets offer a broad range of sizes and may include one or more interactive elements.
+
+ * Small
+ * Medium
+ * Large
+ * Extra large
+ * Extra large portrait
+
+
+
+
+
+
+
+
+
+
+
+
+
+The following table shows supported contexts for each system family widget size:
+
+Widget size| iPhone| iPad| Mac| Apple Vision Pro
+---|---|---|---|---
+System small| Home Screen, Today View, StandBy, and CarPlay| Home Screen, Today View, and Lock Screen| Desktop and Notification Center| Horizontal and vertical surfaces
+System medium| Home Screen and Today View| Home Screen and Today View| Desktop and Notification Center| Horizontal and vertical surfaces
+System large| Home Screen and Today View| Home Screen and Today View| Desktop and Notification Center| Horizontal and vertical surfaces
+System extra large| Not supported| Home Screen and Today View| Desktop and Notification Center| Horizontal and vertical surfaces
+System extra large portrait| Not supported| Not supported| Not supported| Horizontal and vertical surfaces
+
+### [Accessory widgets](https://developer.apple.com/design/human-interface-guidelines/widgets#Accessory-widgets)
+
+Accessory widgets display a very limited amount of information because of their size.
+
+ * Accessory circular
+ * Accessory corner
+ * Accessory inline
+ * Accessory rectangular
+
+
+
+
+
+
+
+
+
+
+
+They appear on the following devices:
+
+Widget size| iPhone| iPad| Apple Watch
+---|---|---|---
+Accessory circular| Lock Screen| Lock Screen| Watch complications and in the Smart Stack
+Accessory corner| Not supported| Not supported| Watch complications
+Accessory inline| Lock Screen| Lock Screen| Watch complications
+Accessory rectangular| Lock Screen| Lock Screen| Watch complications and in the Smart Stack
+
+### [Appearances](https://developer.apple.com/design/human-interface-guidelines/widgets#Appearances)
+
+A widget can appear in full-color, in monochrome with a tint color, or in a clear, translucent style. Depending on the location, device, and a person’s customization, the system may apply a tinted or clear appearance to the widget and its included full-color images, symbols, and glyphs.
+
+For example, a small system widget appears differently depending on the device and location:
+
+ * On the Home Screen of iPhone and iPad, people choose from different appearances for widgets: light, dark, clear, and tinted. In light and dark appearances, widgets have a full-color design. In a clear appearance, the system desaturates the widget and adds translucency, highlights, and the Liquid Glass material. In a tinted appearance, the system desaturates the widget and its content, then applies a person’s selected tint color.
+
+
+
+
+Full-color
+
+Clear
+
+Tinted
+
+ * On Apple Vision Pro, the widget appears as a 3D object, surrounded by a frame. It takes on a full-color appearance with a glass- or paper-like coating layer that responds to lighting conditions. Additionally, people can choose a tinted appearance that applies a color from a set of system-provided color palettes.
+
+
+
+
+
+
+ * On the Lock Screen of iPad, the widget takes on a monochromatic appearance without a tint color.
+
+
+
+
+
+
+ * On the Lock Screen of iPhone in StandBy, the widget appears scaled up in size with the background removed. When the ambient light falls below a threshold, the system renders the widget with a monochromatic red tint.
+
+
+
+
+StandBy
+
+iPhone in StandBy during low-light conditions
+
+Similarly, a rectangular accessory widget appears as follows:
+
+ * On the Lock Screen of iPhone and iPad, it takes on a monochromatic appearance without a tint color.
+
+ * On Apple Watch, the widget can appear as a watch complication in both full-color and tinted appearances, and it can also appear in the Smart Stack.
+
+
+
+
+ * iPhone Lock Screen
+ * Watch complication
+ * Smart Stack on Apple Watch
+
+
+
+
+
+
+
+
+
+Each appearance described above includes a [rendering mode](https://developer.apple.com/design/human-interface-guidelines/widgets#Rendering-modes) that depends on the platform and a person’s appearance settings:
+
+ * The system uses the [full color](https://developer.apple.com/documentation/WidgetKit/WidgetRenderingMode/fullColor) rendering mode for system family widgets across all platforms to display your widget in full color. It doesn’t change the color of your views.
+
+ * The system uses the [accented](https://developer.apple.com/documentation/WidgetKit/WidgetRenderingMode/accented) rendering mode for system family widgets across all platforms and for accessory widgets on Apple Watch. In the accented rendering mode, the system removes the background and replaces it with a tinted color effect for a tinted appearance and a Liquid Glass background for a clear appearance. Additionally, it divides the widget’s views into an accent group and a primary group, and then applies a solid color to each group.
+
+ * The system uses the [vibrant](https://developer.apple.com/documentation/WidgetKit/WidgetRenderingMode/vibrant) rendering mode for widgets on the Lock Screen of iPhone and iPad, and on iPhone in StandBy in low-light conditions. It desaturates text, images, and gauges, and creates a vibrant effect by coloring your content appropriately for the Lock Screen background or a macOS desktop. Note that people can customize the Lock Screen with a tint color, and the system applies a red tint for widgets that appear on iPhone in StandBy in low-light conditions.
+
+
+
+
+The following table lists the occurrences for each rendering mode per platform:
+
+Platform| Full-color| Accented| Vibrant
+---|---|---|---
+iPhone| Home Screen, Today view, StandBy and CarPlay (with the background removed)| Home Screen and Today view| Lock Screen, StandBy in low-light conditions
+iPad| Home Screen and Today view| Home Screen and Today view| Lock Screen
+Apple Watch| Smart Stack, complications| Smart Stack, complications| Not supported
+Mac| Desktop and Notification Center| Not supported| Desktop
+Apple Vision Pro| Horizontal and vertical surfaces| Horizontal and vertical surfaces| Not supported
+
+For additional design guidance, see [Rendering modes](https://developer.apple.com/design/human-interface-guidelines/widgets#Rendering-modes). For developer guidance, see [Preparing widgets for additional platforms, contexts, and appearances](https://developer.apple.com/documentation/WidgetKit/Preparing-widgets-for-additional-contexts-and-appearances) and [`WidgetRenderingMode`](https://developer.apple.com/documentation/WidgetKit/WidgetRenderingMode).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/widgets#Best-practices)
+
+**Choose simple ideas that relate to your app’s main purpose.** Include timely content and relevant functionality. For example, people who use the Weather app are often most interested in the current high and low temperatures and weather conditions, so the Weather widgets prioritize this information.
+
+
+
+**Aim to create a widget that gives people quick access to the content they want.** People appreciate widgets that display meaningful content and offer useful actions and deep links to key areas of your app. Replicating an app icon offers little additional value, and people may be less likely to keep it on their screens.
+
+**Prefer dynamic information that changes throughout the day.** If a widget’s content never appears to change, people may not keep it in a prominent position. Although widgets don’t update from minute to minute, it’s important to find ways to keep their content fresh to invite frequent viewing.
+
+**Look for opportunities to surprise and delight.** For example, you might design a unique visual treatment for your calendar widget to display on meaningful occasions, like birthdays or holidays.
+
+**Offer widgets in multiple sizes when doing so adds value.** Small widgets use their limited space to typically show a single piece of information while larger sizes support additional layers of information and actions. Avoid expanding a smaller widget’s content to simply fill a larger area. It’s more important to create one widget in the size that best represents the content than providing the widget in all sizes.
+
+**Balance information density.** Sparse layouts can make the widget seem unnecessary, while overly dense layouts are less glanceable. Create a layout that provides essential information at a glance and allows people to view additional details by taking a longer look. If your layout is too dense, consider improving its clarity by using a larger widget size or replacing text with graphics.
+
+**Display only the information that’s directly related to the widget’s main purpose.** In larger widgets, you can display more data — or more detailed visualizations of the data — but you don’t want to lose sight of the widget’s primary purpose. For example, all Calendar widgets display a person’s upcoming events. In each size, the widget remains centered on events while expanding the range of information as the size increases.
+
+**Use brand elements thoughtfully.** Incorporate brand colors, typefaces, and stylized glyphs to make your widget recognizable but don’t overpower useful information or make your widget look out of place. When you include brand elements, people seldom need your logo or app icon to help them recognize your widget. If your widget benefits from including a small logo — for example, if your widget displays content from multiple sources — a small logo in the top-right corner is sufficient.
+
+**Choose between automatically displaying content and letting people customize displayed information.** In some cases, people need to configure a widget to ensure it displays the information that’s most useful for them. For example, the Stocks widget lets people select the stocks they wish to track. In contrast, some widgets — like the Podcasts widget — automatically display recent content, so people don’t need to customize them. For developer guidance, see [Making a configurable widget](https://developer.apple.com/documentation/WidgetKit/Making-a-Configurable-Widget).
+
+**Avoid mirroring your widget’s appearance within your app.** Including an element in your app that looks like your widget but doesn’t behave like it can confuse people. Additionally, people may be less likely to try other ways to interact with such an element in your app because they expect it to behave like a widget.
+
+**Let people know when authentication adds value.** If your widget provides additional functionality when someone is signed in to your app, make sure people know that. For example, an app that shows upcoming reservations might include a message like “Sign in to view reservations” when people are signed out.
+
+### [Updating widget content](https://developer.apple.com/design/human-interface-guidelines/widgets#Updating-widget-content)
+
+To remain relevant and useful, widgets periodically refresh their information but don’t support continuous, real-time updates, and the system may adjust the limits for updates depending on various factors.
+
+**Keep your widget up to date.** Finding the appropriate update frequency for your widget depends on knowing how often the data changes and estimating when people need to see new data. For example, a widget that provides information about tidal conditions at a beach is useful if it updates on an hourly basis even though conditions change constantly. If people are likely to check your widget more frequently than you can update it, consider displaying text that describes when the data was last updated.
+
+**Use system functionality to refresh dates and times in your widget.** Because widget update frequency is limited, let the system automatically refresh date and time information to preserve update opportunities. Determine the update frequency that fits with the data you display and show content quickly without hiding stale data behind placeholder content. For developer guidance about widget updates, see [Keeping a widget up to date](https://developer.apple.com/documentation/WidgetKit/Keeping-a-Widget-Up-To-Date).
+
+**Use animated transitions to bring attention to data updates.** By default, many SwiftUI views animate content updates. Additionally, use standard and custom animations with a duration of up to two seconds to let people know when new information is available or when content displays differently. For developer guidance, see [Animating data updates in widgets and Live Activities](https://developer.apple.com/documentation/WidgetKit/Animating-data-updates-in-widgets-and-live-activities).
+
+### [Adding interactivity](https://developer.apple.com/design/human-interface-guidelines/widgets#Adding-interactivity)
+
+People tap or click a widget to launch its corresponding app. It can also include buttons and toggles to offer additional functionality without launching the app. For example, the Reminders widget includes toggles to mark a task as completed. When people interact with your widget in areas that aren’t buttons or toggles, the interaction launches your app.
+
+Incomplete tasks
+
+Completed tasks
+
+**Offer simple, relevant functionality and reserve complexity for your app.** Useful widgets offer an easy way to complete a task or action that’s directly related to its content.
+
+**Ensure that a widget interaction opens your app at the right location.** Deep link to details and actions that directly relate to the widget’s content, and don’t make people navigate to the relevant area in the app. For example, when people click or tap a medium Stocks widget, the Stocks app opens to a page that displays information about the symbol.
+
+
+
+**Offer interactivity while remaining glanceable and uncluttered.** Multiple interaction targets — SwiftUI links, buttons, and toggles — might make sense for your content, but avoid creating app-like layouts in your widgets. Pay attention to the size of targets and make sure people can tap or click them with confidence and without accidentally performing unintended interactions. Note that inline accessory widgets offer only one tap target.
+
+### [Choosing margins and padding](https://developer.apple.com/design/human-interface-guidelines/widgets#Choosing-margins-and-padding)
+
+Widgets scale to adapt to the screen sizes of different devices and onscreen areas. Supply content at appropriate sizes to make sure that your widget looks great on every device and let the system resize or scale it as necessary. In iOS, the system ensures that your widget looks good on small devices by resizing the content you design for large devices. In iPadOS, the system renders your widget at a large size before scaling it down for display on the Home Screen.
+
+As you design for various devices and scale factors, use the values listed in [Specifications](https://developer.apple.com/design/human-interface-guidelines/widgets#Specifications) and the [Apple Design Resources](https://developer.apple.com/design/resources/) for guidance; for your production widget, use [SwiftUI](https://developer.apple.com/documentation/SwiftUI) to ensure flexibility.
+
+**In general, use standard margins to ensure legibility.** Use the standard margin width for widgets — 16 points for most widgets — to avoid crowding their edges and creating a cluttered appearance. If you need to use tighter margins — for example, to create content groupings for graphics, buttons, or background shapes — setting margins of 11 points can work well. Additionally, note that widgets use smaller margins on the desktop on Mac and on the Lock Screen, including in StandBy. For developer guidance, see [`padding(_:_:)`](https://developer.apple.com/documentation/SwiftUI/View/padding\(_:_:\)).
+
+**Coordinate the corner radius of your content with the corner radius of the widget.** To ensure that your content looks good within a widget’s rounded corners, use a SwiftUI container to apply the correct corner radius. For developer guidance, see [`ContainerRelativeShape`](https://developer.apple.com/documentation/SwiftUI/ContainerRelativeShape).
+
+### [Displaying text in widgets](https://developer.apple.com/design/human-interface-guidelines/widgets#Displaying-text-in-widgets)
+
+**Prefer using the system font, text styles, and SF Symbols.** Using the system font helps your widget look at home on any platform, while making it easier for you to display great-looking text in a variety of weights, styles, and sizes. Use SF Symbols to align and scale symbols with text that uses the system font. If you use a custom font, do so sparingly, and be sure it’s easy for people to read at a glance. It often works well to use a custom font for the large text in a widget and SF Pro for the smaller text. For guidance, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography) and [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+**Avoid very small font sizes.** In general, display text using fonts at 11 points or larger. Text in a font that’s smaller than 11 points can be too hard for many people to read.
+
+**Avoid rasterizing text.** Always use text elements and styles to ensure that your text scales well and to allow VoiceOver to speak your content.
+
+Note
+
+In iOS, iPadOS, and visionOS, widgets support Dynamic Type sizes from Large to AX5 when you use [`Font`](https://developer.apple.com/documentation/SwiftUI/Font) to choose a system font or [`custom(_:size:)`](https://developer.apple.com/documentation/SwiftUI/Font/custom\(_:size:\)) to choose a custom font. For more information about Dynamic Type sizes, see [Supporting Dynamic Type](https://developer.apple.com/design/human-interface-guidelines/typography#Supporting-Dynamic-Type).
+
+### [Using color](https://developer.apple.com/design/human-interface-guidelines/widgets#Using-color)
+
+**Use color to enhance a widget’s appearance without competing with its content.** Beautiful colors draw the eye, but they’re best when they don’t prevent people from absorbing a widget’s information at a glance. In your asset catalog, you can also specify the colors you want the system to use as it generates your widget’s editing-mode user interface.
+
+**Convey meaning without relying on specific colors to represent information.** Widgets can appear monochromatic (with or without a custom tint color), and in watchOS, the system may invert colors depending on the watch face a person chooses. Use text and iconography in addition to color to express meaning.
+
+**Use full-color images judiciously.** When a person chooses a tinted or clear appearance for their widgets, the system by default desaturates full-color images. You can choose to render images in full-color, even when a person chooses a tinted or clear widget appearance. However, full-color images in these appearances draw special attention to the widget, which might make it feel as if the widget doesn’t belong to the platform. For example, a full-color image in a widget might appear out of place when a person chooses a clear widget appearance. Consider reserving full-color images to represent media content, such as album art for a music app’s widget, and use full-color images with smaller dimensions than the size of the widget.
+
+## [Rendering modes](https://developer.apple.com/design/human-interface-guidelines/widgets#Rendering-modes)
+
+### [Full-color](https://developer.apple.com/design/human-interface-guidelines/widgets#Full-color)
+
+**Support light and dark appearances.** Prefer light backgrounds for the light appearance and dark backgrounds for the dark appearance, and consider using the semantic system colors for text and backgrounds to let the colors dynamically adapt to the current appearance. You can also support different appearances by putting color variants in your asset catalog. For guidance, see [Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode); for developer guidance, see [Asset management](https://developer.apple.com/documentation/Xcode/asset-management) and [Supporting Dark Mode in your interface](https://developer.apple.com/documentation/UIKit/supporting-dark-mode-in-your-interface).
+
+
+
+
+
+### [Accented](https://developer.apple.com/design/human-interface-guidelines/widgets#Accented)
+
+**Group widget components into an accented and a primary group.** The accented rendering mode divides the widget’s view hierarchy into an accent group and a primary group. On iPhone, iPad, and Mac, the system tints primary and accented content white. On Apple Watch, the system tints primary content white and accented content in the color of the watch face.
+
+For developer guidance, see [`widgetAccentable(_:)`](https://developer.apple.com/documentation/SwiftUI/View/widgetAccentable\(_:\)) and [Optimizing your widget for accented rendering mode and Liquid Glass](https://developer.apple.com/documentation/WidgetKit/optimizing-your-widget-for-accented-rendering-mode-and-liquid-glass).
+
+### [Vibrant](https://developer.apple.com/design/human-interface-guidelines/widgets#Vibrant)
+
+**Offer enough contrast to ensure legibility.** In the vibrant rendering mode, the opacity of pixels within an image determines the strength of the blurred background material effect. Fully transparent pixels let the background material pass through as is. The brightness of pixels determines how vibrant they appear on the Lock Screen. Brighter gray values provide more contrast, and darker values provide less contrast.
+
+**Create optimized assets for the best vibrant effect.** Render content like images, numbers, and text at full opacity. Use white or light gray for the most prominent content and darker grayscale values for secondary elements to establish hierarchy. Confirm that image content has sufficient contrast in grayscale, and use opaque grayscale values, rather than opacities of white, to achieve the best vibrant material effect.
+
+## [Previews and placeholders](https://developer.apple.com/design/human-interface-guidelines/widgets#Previews-and-placeholders)
+
+**Design a realistic preview to display in the widget gallery.** Highlighting your widget’s capabilities — and clearly representing the experiences each widget type or size can provide — helps people make an informed decision. You can display real data in your widget preview, but if the data takes too long to generate or load, display realistic simulated data instead.
+
+**Design placeholder content that helps people recognize your widget.** An installed widget displays placeholder content while its data loads. Create an effective placeholder appearance by combining static interface components with semi-opaque shapes that stand in for dynamic content. For example, use rectangles of different widths to suggest lines of text, and circles or squares in place of glyphs and images.
+
+
+
+
+
+**Write a succinct widget description.** The widget gallery displays descriptions that help people understand what each widget does. Begin a description with an action verb — for example, “See the current weather conditions and forecast for a location” or “Keep track of your upcoming events and meetings.” Avoid including unnecessary phrases that reference the widget itself, like “This widget shows…,” “Use this widget to…,” or “Add this widget.” Use approachable language and [sentence-style capitalization](https://support.apple.com/guide/applestyleguide/c-apsgb744e4a3/web#apdca93e113f1d64).
+
+**Group your widget’s sizes together, and provide a single description.** If your widget is available in multiple sizes, group them together so people don’t think each size is a different widget. Provide a single description of your widget — regardless of how many sizes you offer — to avoid repetition and to help people understand how each size provides a slightly different perspective on the same content and functionality.
+
+**Consider coloring the Add button.** After people choose your app in the widget gallery, an Add button appears below the group of widgets you offer. You can specify a color for this button to help remind people of your brand.
+
+
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/widgets#Platform-considerations)
+
+ _No additional considerations for macOS. Not supported in tvOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/widgets#iOS-iPadOS)
+
+Widgets on the Lock Screen are functionally similar to watch complications and follow design principles for [Complications](https://developer.apple.com/design/human-interface-guidelines/complications) in addition to design principles for widgets. Provide useful information in your Lock Screen widget, and don’t treat it only as an additional way for people to launch into your app. In many cases, a design for complications also works well for widgets on the Lock Screen (and vice versa), so consider creating them in tandem.
+
+Your app can offer widgets on the Lock Screen in three different shapes: as inline text that appears above the clock, and as circular and rectangular shapes that appear below the clock.
+
+
+
+**Support the Always-On display on iPhone.** Devices with the Always-On display render widgets on the Lock Screen with reduced luminance. Use levels of gray that provide enough contrast in the Always-On display, and make sure your content remains legible.
+
+For developer guidance, see [Creating accessory widgets and watch complications](https://developer.apple.com/documentation/WidgetKit/Creating-accessory-widgets-and-watch-complications).
+
+**Offer Live Activities to show real-time updates.** Widgets don’t show real-time information. If your app allows people to track the progress of a task or event for a limited amount of time with frequent updates, consider offering Live Activities. Widgets and Live Activities use the same underlying frameworks and share design similarities. As a result, it can be a good idea to develop widgets and Live Activities in tandem and reuse code and design components for both features. For design guidance on Live Activities, see [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities); for developer guidance, see [ActivityKit](https://developer.apple.com/documentation/ActivityKit).
+
+#### [StandBy and CarPlay](https://developer.apple.com/design/human-interface-guidelines/widgets#StandBy-and-CarPlay)
+
+On iPhone in StandBy, the system displays two small system family widgets side-by-side, scaled up so they fill the Lock Screen. By supporting StandBy, you also ensure your widgets work well in CarPlay. CarPlay and StandBy widgets both use the small system family widget with the background removed and scaled up to best fit the grid on the Widgets screen. Glanceable information and large text are especially important in CarPlay to make your widget easy to read on a car’s display.
+
+**Limit usage of rich images or color to convey meaning in StandBy.** Instead, make use of the additional space by scaling up and rearranging text so people can glance at the widget content from a greater distance. To seamlessly blend with the black background, don’t use background colors for your widget when it appears in StandBy.
+
+ * Correct usage
+ * Incorrect usage
+
+
+
+
+
+
+
+
+
+
+
+For developer guidance, see [Displaying the right widget background](https://developer.apple.com/documentation/WidgetKit/Displaying-the-right-widget-background).
+
+On iPhone in StandBy in low-light conditions, the system renders widgets in a monochromatic look with a red tint.
+
+
+
+iPhone in low-light conditions
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/widgets#visionOS)
+
+Widgets in visionOS are 3D objects that people place on a horizontal or vertical surface. When a person places a widget on a surface, the widget persists in that location even when the person turns Apple Vision Pro off and back on. Widgets have a consistent, real-world scale. Their size, _mounting style_ , and _treatment style_ impact how a person perceives them.
+
+visionOS widgets appear in full-color by default, but they appear in the accented rendering mode when people personalize them with tint colors using a range of system-provided color palettes. Additionally, people can customize the frame width of widgets that use the elevated mounting style, and custom options that are unique to the widget. For example, visionOS doesn’t provide systemwide light or dark appearances. However, the Music poster widget offers its own customization option that lets people choose between a light and a dark theme that the app generates from the displayed album art.
+
+For developer guidance, see [Updating your widgets for visionOS](https://developer.apple.com/documentation/WidgetKit/Updating-your-widgets-for-visionOS).
+
+**Adapt your design and content for the spatial experience Apple Vision Pro provides.** In visionOS, widgets don’t float in isolation but are part of living rooms, kitchens, offices, and more. Consider this context early and think of widgets as part of someone’s surroundings when you bring your existing widgets to visionOS or design them from scratch. For example, the Music widget adapts to a poster-like appearance that’s glanceable across the room with large typography and a high-resolution image, and a productivity app might offer a small widget that easily fits on a desk.
+
+**Test your widgets across the full range of system color palettes and in different lighting conditions.** Make sure your widget’s tone, contrast, and legibility remain consistent and intentional. If you choose to exclude UI elements from tinting, test your widget in every provided tint color palette to make sure the untinted elements remain legible when a person customizes their widgets with tint colors.
+
+#### [Thresholds and sizes](https://developer.apple.com/design/human-interface-guidelines/widgets#Thresholds-and-sizes)
+
+Widgets on Apple Vision Pro can adapt based on a person’s proximity, and visionOS provides widgets with two key thresholds to design for: the [`simplified`](https://developer.apple.com/documentation/WidgetKit/LevelOfDetail/simplified) threshold for when a person views a widget at a distance, and the [`default`](https://developer.apple.com/documentation/WidgetKit/LevelOfDetail/default) threshold when a person views it nearby.
+
+Viewed from a distance
+
+Viewed from nearby
+
+Because widgets can appear throughout a person’s environment, it’s also important to match a widget’s size to the type of content it contains, and to be aware of how it appears at a variety of distances.
+
+**Design a responsive layout that shows the right level of detail for each of the two thresholds.** When a person views the widget at a distance, display a simplified version of your widget that shows fewer details and has a larger type size, and remove interactive elements like buttons or toggles. When a person views the widget from nearby, show more details and use a smaller type size. To create a smooth and consistent experience and help your layout feel continuous, maintain shared elements across both distance thresholds.
+
+**Offer widget family sizes that fit a person’s surroundings well.** Widgets map to real-world dimensions and have a permanent presence in a person’s spatial environment. Think about where people might place your widget — mounted to a wall, placed on a sideboard, or sitting next to a workplace — and choose a widget family size that’s right for that context. For example, offer a small system widget with content that people might place on a desk or an extra large widget to let people decorate their surroundings with something visually rich, like artwork or photography.
+
+**Display content in a way that remains legible from a range of distances.** To make a widget feel intentional and proportionate to where they place it, people can scale a widget from 75 to 125 percent in size. Use print design principles like clear hierarchy, strong typography, and scale to make sure your content remains glanceable. Include high-resolution assets that look good scaled up to every size.
+
+#### [Mounting styles](https://developer.apple.com/design/human-interface-guidelines/widgets#Mounting-styles)
+
+The way a widget appears on a surface plays a big role in how a person perceives it. To make it feel intentional and integrated into their surroundings, people place a widget on surfaces in distinct mounting styles.
+
+ * **[Elevated](https://developer.apple.com/documentation/WidgetKit/WidgetMountingStyle/elevated) style**. On horizontal surfaces — for example, on a desk — the widget always appears elevated and gently tilts backward, providing a subtle angle that improves readability, and casts a soft shadow that helps it feel grounded on the surface. On vertical surfaces — for example, on a wall — the widget either appears elevated, sitting flush on the surface and similar to how you mount a picture frame.
+
+ * **[Recessed](https://developer.apple.com/documentation/WidgetKit/WidgetMountingStyle/recessed) style**. On vertical surfaces — for example, on a wall — the widget can appear recessed, with content set back into the surface, creating a depth effect that gives the illusion of a cutout in the surface. Horizontal surfaces don’t use the recessed mounting style.
+
+
+
+
+By default, widgets use the elevated mounting style, because it works for horizontal and vertical surfaces.
+
+**Choose the mounting style that fits your content and the experience you want to create.** By default, visionOS widgets use the elevated mounting style, which is ideal for content that you want to stand out and feel present, like reminders, media, or glanceable data. Recessed widgets are ideal for immersive or ambient content, like weather or editorial content, and people can only place them on a vertical surface. If a style doesn’t suit your widget, you can opt out of it for each widget. If you choose to only support the recessed mounting style, people can’t place the widget on a horizontal surface. For example, a weather app might only support the recessed mounting style to give the illusion of looking out of a window for its large and extra-large system family widgets, and only support the elevated style for its small system family widget.
+
+Developer note
+
+Use the [`supportedMountingStyles(_:)`](https://developer.apple.com/documentation/SwiftUI/WidgetConfiguration/supportedMountingStyles\(_:\)) property of your [`WidgetConfiguration`](https://developer.apple.com/documentation/SwiftUI/WidgetConfiguration) to declare supported mounting styles — elevated, recessed, or both — for all widgets included in the configuration. To offer a widget that only supports one mounting style and other widgets that support both mounting styles, create separate widget configurations. For example, create one widget configuration for the widget that only supports the recessed mounting style, and a second configuration for the widgets that support both mounting styles.
+
+**Test your elevated widget designs with each system-provided frame width.** People can choose from different system-defined frame widths for widgets that use the elevated mounting style. You can’t change your layout based on the frame width a person chooses, so make sure your widget layout stays visually balanced for each frame width.
+
+#### [Treatment styles](https://developer.apple.com/design/human-interface-guidelines/widgets#Treatment-styles)
+
+In addition to size and mounting style, the system applies one of two treatment styles to visionOS widgets. Choosing the right treatment for your widget helps reinforce the experience you want to create.
+
+ * The [`paper`](https://developer.apple.com/documentation/WidgetKit/WidgetTexture/paper) style creates a more grounded, print-like style that feels solid and makes the widget feel like part of its surroundings. When lighting conditions change, widgets in the paper style become darker or lighter in response.
+
+ * The [`glass`](https://developer.apple.com/documentation/WidgetKit/WidgetTexture/glass) style creates a lighter, layered look that adds depth and visual separation between foreground and background elements to emphasize clarity and contrast. The foreground elements always stay bright and legible, and don’t dim or brighten, even as ambient light changes.
+
+
+
+
+**Choose the paper style for a print-like look that feels more like a real object in the room.** The entire widget responds to the ambient lighting and blends naturally into its surroundings. For example, the Music poster widget uses the paper style to display albums and playlists like framed artwork on a wall.
+
+**Choose the glass style for information-rich widgets.** Glass visually separates foreground and background elements, allowing you to decide which parts of your interface adapt to the surroundings and which stay visually consistent. Foreground elements appear in full color, unaffected by ambient lighting, to make sure important content stays sharp and legible. For example, a News widget appears with editorial images in the background with a soft, print-like look. Its headlines stay in the foreground, crisp and easy to read.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/widgets#watchOS)
+
+**Provide a colorful background that conveys meaning.** By default, widgets in the Smart Stack use a black background. Consider using a custom background color that provides additional meaning. For example, the Stocks app uses a red background for falling stock values and a green background if a stock’s value rises.
+
+**Encourage the system to display or elevate the position of your watchOS widget in the Smart Stack.** Relevancy information helps the system show your widget when people need it most. Relevance can be location-based or specific to ongoing system actions, like a workout. For developer guidance, see [RelevanceKit](https://developer.apple.com/documentation/RelevanceKit).
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/widgets#Specifications)
+
+As you design your widgets, use the following values for guidance.
+
+### [iOS dimensions](https://developer.apple.com/design/human-interface-guidelines/widgets#iOS-dimensions)
+
+Screen size (portrait, pt)| Small (pt)| Medium (pt)| Large (pt)| Circular (pt)| Rectangular (pt)| Inline (pt)
+---|---|---|---|---|---|---
+430×932| 170x170| 364x170| 364x382| 76x76| 172x76| 257x26
+428x926| 170x170| 364x170| 364x382| 76x76| 172x76| 257x26
+414x896| 169x169| 360x169| 360x379| 76x76| 160x72| 248x26
+414x736| 159x159| 348x157| 348x357| 76x76| 170x76| 248x26
+393x852| 158x158| 338x158| 338x354| 72x72| 160x72| 234x26
+390x844| 158x158| 338x158| 338x354| 72x72| 160x72| 234x26
+375x812| 155x155| 329x155| 329x345| 72x72| 157x72| 225x26
+375x667| 148x148| 321x148| 321x324| 68x68| 153x68| 225x26
+360x780| 155x155| 329x155| 329x345| 72x72| 157x72| 225x26
+320x568| 141x141| 292x141| 292x311| N/A| N/A| N/A
+
+### [iPadOS dimensions](https://developer.apple.com/design/human-interface-guidelines/widgets#iPadOS-dimensions)
+
+Screen size (portrait, pt)| Target| Small (pt)| Medium (pt)| Large (pt)| Extra large (pt)
+---|---|---|---|---|---
+768x1024| Canvas| 141x141| 305.5x141| 305.5x305.5| 634.5x305.5
+Device| 120x120| 260x120| 260x260| 540x260
+744x1133| Canvas| 141x141| 305.5x141| 305.5x305.5| 634.5x305.5
+Device| 120x120| 260x120| 260x260| 540x260
+810x1080| Canvas| 146x146| 320.5x146| 320.5x320.5| 669x320.5
+Device| 124x124| 272x124| 272x272| 568x272
+820x1180| Canvas| 155x155| 342x155| 342x342| 715.5x342
+Device| 136x136| 300x136| 300x300| 628x300
+834x1112| Canvas| 150x150| 327.5x150| 327.5x327.5| 682x327.5
+Device| 132x132| 288x132| 288x288| 600x288
+834x1194| Canvas| 155x155| 342x155| 342x342| 715.5x342
+Device| 136x136| 300x136| 300x300| 628x300
+954x1373 *| Canvas| 162x162| 350x162| 350x350| 726x350
+Device| 162x162| 350x162| 350x350| 726x350
+970x1389 *| Canvas| 162x162| 350x162| 350x350| 726x350
+Device| 162x162| 350x162| 350x350| 726x350
+1024x1366| Canvas| 170x170| 378.5x170| 378.5x378.5| 795x378.5
+Device| 160x160| 356x160| 356x356| 748x356
+1192x1590 *| Canvas| 188x188| 412x188| 412x412| 860x412
+Device| 188x188| 412x188| 412x412| 860x412
+
+* When Display Zoom is set to More Space.
+
+### [visionOS dimensions](https://developer.apple.com/design/human-interface-guidelines/widgets#visionOS-dimensions)
+
+Widget| Size in pt| Size in mm (scaled to 100%)
+---|---|---
+Small| 158x158| 268x268
+Medium| 338x158| 574x268
+Large| 338x354| 574x600
+Extra large| 450x338| 763x574
+Extra large portrait| 338x450| 574x763
+
+### [watchOS dimensions](https://developer.apple.com/design/human-interface-guidelines/widgets#watchOS-dimensions)
+
+Apple Watch size| Size of a widget in the Smart Stack (pt)
+---|---
+40mm| 152x69.5
+41mm| 165x72.5
+44mm| 173x76.5
+45mm| 184x80.5
+49mm| 191x81.5
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/widgets#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/widgets#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/widgets#Developer-documentation)
+
+[WidgetKit](https://developer.apple.com/documentation/WidgetKit)
+
+[Developing a WidgetKit strategy](https://developer.apple.com/documentation/WidgetKit/Developing-a-WidgetKit-strategy) — WidgetKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/widgets#Videos)
+
+[ What’s new in widgets ](https://developer.apple.com/videos/play/wwdc2025/278)
+
+[ Design widgets for visionOS ](https://developer.apple.com/videos/play/wwdc2025/255)
+
+[ Bring widgets to life ](https://developer.apple.com/videos/play/wwdc2023/10028)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/widgets#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for all platforms, and added guidance for visionOS and CarPlay.
+January 17, 2025| Corrected watchOS widget dimensions.
+June 10, 2024| Updated to include guidance for accented widgets in iOS 18 and iPadOS 18.
+June 5, 2023| Updated guidance to include widgets in watchOS, widgets on the iPad Lock Screen, and updates for iOS 17, iPadOS 17, and macOS 14.
+November 3, 2022| Added guidance for widgets on the iPhone Lock Screen and updated design comprehensives for iPhone 14, iPhone 14 Pro, and iPhone 14 Pro Max.
+
diff --git a/web-app/public/skills/hig-foundations/SKILL.md b/web-app/public/skills/hig-foundations/SKILL.md
new file mode 100644
index 00000000..294e1baa
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/SKILL.md
@@ -0,0 +1,103 @@
+---
+name: hig-foundations
+version: 1.0.0
+description: ">"
+ Apple Human Interface Guidelines design foundations. Use this skill when the user asks about
+ "HIG color", "Apple typography", "SF Symbols", "dark mode guidelines", "accessible design",
+ "Apple design foundations", "app icon", "layout guidelines", "materials", "motion", "privacy",
+ "right to left", "RTL", "inclusive design", branding, images, spatial layout, or writing style.
+ Also use when the user says "my colors look wrong in dark mode", "what font should I use",
+ "is my app accessible enough", "how do I support Dynamic Type", "what contrast ratio do I need",
+ "how do I pick system colors", or "my icons don't match the system style".
+ Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction
+ patterns, hig-components-layout for structural components, hig-components-content for display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Design Foundations
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Prioritize content over chrome.** Reduce visual clutter. Use system-provided materials and subtle separators rather than heavy borders and backgrounds.
+
+2. **Build in accessibility from the start.** Design for VoiceOver, Dynamic Type, Reduce Motion, Increase Contrast, and Switch Control from day one. Every interactive element needs an accessible label.
+
+3. **Use system colors and materials.** System colors adapt to light/dark mode, increased contrast, and vibrancy. Prefer semantic colors (`label`, `secondaryLabel`, `systemBackground`) over hard-coded values.
+
+4. **Use platform fonts and icons.** SF Pro, SF Compact, SF Mono by default. New York for serif. Follow the type hierarchy at recommended sizes. Use SF Symbols for iconography.
+
+5. **Match platform conventions.** Align look and behavior with system standards. Provide direct, responsive manipulation and clear feedback for every action.
+
+6. **Respect privacy.** Request permissions only when needed, explain why clearly, provide value before asking for data. Design for minimal data collection.
+
+7. **Support internationalization.** Accommodate text expansion, right-to-left scripts, and varying date/number formats. Use Auto Layout for dynamic content sizing.
+
+8. **Use motion purposefully.** Animation should communicate meaning and spatial relationships. Honor Reduce Motion by providing crossfade alternatives.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [accessibility.md](references/accessibility.md) | Accessibility | VoiceOver, Dynamic Type, color contrast, motor accessibility, Switch Control, audio descriptions |
+| [app-icons.md](references/app-icons.md) | App Icons | Icon grid, platform-specific sizes, single focal point, no transparency |
+| [branding.md](references/branding.md) | Branding | Integrating brand identity within Apple's design language, subtle branding, custom tints |
+| [color.md](references/color.md) | Color | System colors, Dynamic Colors, semantic colors, custom palettes, contrast ratios |
+| [dark-mode.md](references/dark-mode.md) | Dark Mode | Elevated surfaces, semantic colors, adapted palettes, vibrancy, testing in both modes |
+| [icons.md](references/icons.md) | Icons | Glyph icons, SF Symbols integration, custom icon design, icon weights, optical alignment |
+| [images.md](references/images.md) | Images | Image resolution, @2x/@3x assets, vector assets, image accessibility |
+| [immersive-experiences.md](references/immersive-experiences.md) | Immersive Experiences | AR/VR design, spatial immersion, comfort zones, progressive immersion levels |
+| [inclusion.md](references/inclusion.md) | Inclusion | Diverse representation, non-gendered language, cultural sensitivity, inclusive defaults |
+| [layout.md](references/layout.md) | Layout | Margins, spacing, alignment, safe areas, adaptive layouts, readable content guides |
+| [materials.md](references/materials.md) | Materials | Vibrancy, blur, translucency, system materials, material thickness |
+| [motion.md](references/motion.md) | Motion | Animation curves, transitions, continuity, Reduce Motion support, physics-based motion |
+| [privacy.md](references/privacy.md) | Privacy | Permission requests, usage descriptions, privacy nutrition labels, minimal data collection |
+| [right-to-left.md](references/right-to-left.md) | Right-to-Left | RTL layout mirroring, bidirectional text, icons that flip, exceptions |
+| [sf-symbols.md](references/sf-symbols.md) | SF Symbols | Symbol categories, rendering modes, variable color, custom symbols, weight matching |
+| [spatial-layout.md](references/spatial-layout.md) | Spatial Layout | visionOS window placement, depth, ergonomic zones, Z-axis design |
+| [typography.md](references/typography.md) | Typography | SF Pro, Dynamic Type sizes, text styles, custom fonts, font weight hierarchy, line spacing |
+| [writing.md](references/writing.md) | Writing | UI copy guidelines, tone, capitalization rules, error messages, button labels, conciseness |
+
+## Applying Foundations Together
+
+Consider how principles interact:
+
+1. **Color + Dark Mode + Accessibility** -- Custom palettes must work in both modes while maintaining WCAG contrast ratios. Start with system semantic colors.
+
+2. **Typography + Accessibility + Layout** -- Dynamic Type must scale without breaking layouts. Use text styles and Auto Layout for the full range of type sizes.
+
+3. **Icons + Branding + SF Symbols** -- Custom icons should match SF Symbols weight and optical sizing. Brand elements should integrate without overriding system conventions.
+
+4. **Motion + Accessibility + Feedback** -- Every animation must have a Reduce Motion alternative. Motion should reinforce spatial relationships, not decorate.
+
+5. **Privacy + Writing + Onboarding** -- Permission requests need clear, specific usage descriptions. Time them to when the user will understand the benefit.
+
+## Output Format
+
+1. **Cite the specific HIG foundation** with file and section.
+2. **Note platform differences** for the user's target platforms.
+3. **Provide concrete code patterns** (SwiftUI/UIKit/AppKit).
+4. **Explain accessibility impact** (contrast ratios, Dynamic Type scaling, VoiceOver behavior).
+
+## Questions to Ask
+
+1. Which platforms are you targeting?
+2. Do you have existing brand guidelines?
+3. What accessibility level are you targeting? (WCAG AA, AAA, Apple baseline?)
+4. System colors or custom?
+
+## Related Skills
+
+- **hig-platforms** -- How foundations apply per platform (e.g., type scale differences on watchOS vs macOS)
+- **hig-patterns** -- Interaction patterns where foundations like writing and accessibility are critical
+- **hig-components-layout** -- Structural components implementing layout principles
+- **hig-components-content** -- Content display using color, typography, and images
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-foundations/references/accessibility.md b/web-app/public/skills/hig-foundations/references/accessibility.md
new file mode 100644
index 00000000..11d9a347
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/accessibility.md
@@ -0,0 +1,291 @@
+---
+title: "Accessibility | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/accessibility
+
+# Accessibility
+
+Accessible user interfaces empower everyone to have a great experience with your app or game.
+
+
+
+When you design for accessibility, you reach a larger audience and create a more inclusive experience. An accessible interface allows people to experience your app or game regardless of their capabilities or how they use their devices. Accessibility makes information and interactions available to everyone. An accessible interface is:
+
+ * **Intuitive.** Your interface uses familiar and consistent interactions that make tasks straightforward to perform.
+
+ * **Perceivable.** Your interface doesn’t rely on any single method to convey information. People can access and interact with your content, whether they use sight, hearing, speech, or touch.
+
+ * **Adaptable.** Your interface adapts to how people want to use their device, whether by supporting system accessibility features or letting people personalize settings.
+
+
+
+
+As you design your app, audit the accessibility of your interface. Use [Accessibility Inspector](https://developer.apple.com/documentation/Accessibility/accessibility-inspector) to highlight accessibility issues with your interface and to understand how your app represents itself to people using system accessibility features. You can also communicate how accessible your app is on the App Store using Accessibility Nutrition Labels. To learn more about how to evaluate and indicate accessibility feature support, see [Accessibility Nutrition Labels](https://developer.apple.com/help/app-store-connect/manage-app-accessibility/overview-of-accessibility-nutrition-labels) in App Store Connect help.
+
+## [Vision](https://developer.apple.com/design/human-interface-guidelines/accessibility#Vision)
+
+
+
+The people who use your interface may be blind, color blind, or have low vision or light sensitivity. They may also be in situations where lighting conditions and screen brightness affect their ability to interact with your interface.
+
+**Support larger text sizes.** Make sure people can adjust the size of your text or icons to make them more legible, visible, and comfortable to read. Ideally, give people the option to enlarge text by at least 200 percent (or 140 percent in watchOS apps). Your interface can support font size enlargement either through custom UI, or by adopting Dynamic Type. Dynamic Type is a systemwide setting that lets people adjust the size of text for comfort and legibility. For more guidance, see [Supporting Dynamic Type](https://developer.apple.com/design/human-interface-guidelines/typography#Supporting-Dynamic-Type).
+
+**Use recommended defaults for custom type sizes.** Each platform has different default and minimum sizes for system-defined type styles to promote readability. If you’re using custom type styles, follow the recommended defaults.
+
+Platform| Default size| Minimum size
+---|---|---
+iOS, iPadOS| 17 pt| 11 pt
+macOS| 13 pt| 10 pt
+tvOS| 29 pt| 23 pt
+visionOS| 17 pt| 12 pt
+watchOS| 16 pt| 12 pt
+
+**Bear in mind that font weight can also impact how easy text is to read.** If you’re using a custom font with a thin weight, aim for larger than the recommended sizes to increase legibility. For more guidance, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography).
+
+Thicker weights are easier to read for smaller font sizes.
+
+Consider increasing the font size when using a thin weight.
+
+**Strive to meet color contrast minimum standards.** To ensure all information in your app is legible, it’s important that there’s enough contrast between foreground text and icons and background colors. Two popular standards of measure for color contrast are the [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/TR/WCAG/) and the Accessible Perceptual Contrast Algorithm (APCA). Use standard contrast calculators to ensure your UI meets acceptable levels. [Accessibility Inspector](https://developer.apple.com/documentation/Accessibility/accessibility-inspector) uses the following values from WCAG Level AA as guidance in determining whether your app’s colors have an acceptable contrast.
+
+Text size| Text weight| Minimum contrast ratio
+---|---|---
+Up to 17 pts| All| 4.5:1
+18 pts| All| 3:1
+All| Bold| 3:1
+
+If your app doesn’t provide this minimum contrast by default, ensure it at least provides a higher contrast color scheme when the system setting Increase Contrast is turned on. If your app supports [Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode), make sure to check the minimum contrast in both light and dark appearances.
+
+A button with insufficient color contrast
+
+
+
+A button with sufficient color contrast
+
+
+
+**Prefer system-defined colors.** These colors have their own accessible variants that automatically adapt when people adjust their color preferences, such as enabling Increase Contrast or toggling between the light and dark appearances. For guidance, see [Color](https://developer.apple.com/design/human-interface-guidelines/color).
+
+The `systemRed` default color in iOS
+
+The `systemRed` accessible color in iOS
+
+**Convey information with more than color alone.** Some people have trouble differentiating between certain colors and shades. For example, people who are color blind may have particular difficulty with pairings such as red-green and blue-orange. Offer visual indicators, like distinct shapes or icons, in addition to color to help people perceive differences in function and changes in state. Consider allowing people to customize color schemes such as chart colors or game characters so they can personalize your interface in a way that’s comfortable for them.
+
+For someone with red-green color blindness, these indicators might appear the same.
+
+
+
+Both visual indicators and color help differentiate between indicators.
+
+
+
+**Describe your app’s interface and content for VoiceOver.** VoiceOver is a screen reader that lets people experience your app’s interface without needing to see the screen. For more guidance, see [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover).
+
+## [Hearing](https://developer.apple.com/design/human-interface-guidelines/accessibility#Hearing)
+
+
+
+The people who use your interface may be deaf or hard of hearing. They may also be in noisy or public environments.
+
+**Support text-based ways to enjoy audio and video.** It’s important that dialogue and crucial information about your app or game isn’t communicated through audio alone. Depending on the context, give people different text-based ways to experience their media, and allow people to customize the visual presentation of that text:
+
+ * **Captions** give people the textual equivalent of audible information in video or audio-only content. Captions are great for scenarios like game cutscenes and video clips where text synchronizes live with the media.
+
+ * **Subtitles** allow people to read live onscreen dialogue in their preferred language. Subtitles are great for TV shows and movies.
+
+ * **Audio descriptions** are interspersed between natural pauses in the main audio of a video and supply spoken narration of important information that’s presented only visually.
+
+ * **Transcripts** provide a complete textual description of a video, covering both audible and visual information. Transcripts are great for longer-form media like podcasts and audiobooks where people may want to review content as a whole or highlight the transcript as media is playing.
+
+
+
+
+For developer guidance, see [Selecting subtitles and alternative audio tracks](https://developer.apple.com/documentation/AVFoundation/selecting-subtitles-and-alternative-audio-tracks).
+
+**Use haptics in addition to audio cues.** If your interface conveys information through audio cues — such as a success chime, error sound, or game feedback — consider pairing that sound with matching haptics for people who can’t perceive the audio or have their audio turned off. In iOS and iPadOS, you can also use [Music Haptics](https://developer.apple.com/documentation/MediaAccessibility/music-haptics) and [Audio graphs](https://developer.apple.com/documentation/Accessibility/audio-graphs) to let people experience music and infographics through vibration and texture. For guidance, see [Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics).
+
+
+
+**Augment audio cues with visual cues.** This is especially important for games and spatial apps where important content might be taking place off screen. When using audio to guide people towards a specific action, also add in visual indicators that point to where you want people to interact.
+
+## [Mobility](https://developer.apple.com/design/human-interface-guidelines/accessibility#Mobility)
+
+
+
+Ensure your interface offers a comfortable experience for people with limited dexterity or mobility.
+
+**Offer sufficiently sized controls.** Controls that are too small are hard for many people to interact with and select. Strive to meet the recommended minimum control size for each platform to ensure controls and menus are comfortable for all when tapping and clicking.
+
+Platform| Default control size| Minimum control size
+---|---|---
+iOS, iPadOS| 44x44 pt| 28x28 pt
+macOS| 28x28 pt| 20x20 pt
+tvOS| 66x66 pt| 56x56 pt
+visionOS| 60x60 pt| 28x28 pt
+watchOS| 44x44 pt| 28x28 pt
+
+**Consider spacing between controls as important as size.** Include enough padding between elements to reduce the chance that someone taps the wrong control. In general, it works well to add about 12 points of padding around elements that include a bezel. For elements without a bezel, about 24 points of padding works well around the element’s visible edges.
+
+Elements with insufficient padding
+
+
+
+Elements with sufficient padding
+
+
+
+**Support simple gestures for common interactions.** For many people, with or without disabilities, complex gestures can be challenging. For interactions people do frequently in your app or game, use the simplest gesture possible — avoid custom multifinger and multihand gestures — so repetitive actions are both comfortable and easy to remember.
+
+**Offer alternatives to gestures.** Make sure your UI’s core functionality is accessible through more than one type of physical interaction. Gestures can be less comfortable for people who have limited dexterity, so offer onscreen ways to achieve the same outcome. For example, if you use a swipe gesture to dismiss a view, also make a button available so people can tap or use an assistive device.
+
+Edit and tap to delete
+
+Swipe to delete
+
+**Let people use Voice Control to give guidance and enter information verbally.** With Voice Control, people can interact with their devices entirely by speaking commands. They can perform gestures, interact with screen elements, dictate and edit text, and more. To ensure a smooth experience, label interface elements appropriately. For developer guidance, see [Voice Control](https://developer.apple.com/documentation/Accessibility/voice-control).
+
+**Integrate with Siri and Shortcuts to let people perform tasks using voice alone.** When your app supports Siri and Shortcuts, people can automate the important and repetitive tasks they perform regularly. They can initiate these tasks from Siri, the Action button on their iPhone or Apple Watch, and shortcuts on their Home Screen or in Control Center. For guidance, see [Siri](https://developer.apple.com/design/human-interface-guidelines/siri).
+
+**Support mobility-related assistive technologies.** Features like [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover), AssistiveTouch, Full Keyboard Access, Pointer Control, and [Switch Control](https://developer.apple.com/documentation/Accessibility/switch-control) offer alternative ways for people with low mobility to interact with their devices. Conduct testing and verify that your app or game supports these technologies, and that your interface elements are appropriately labeled to ensure a great experience. For more information, see [Performing accessibility testing for your app](https://developer.apple.com/documentation/Accessibility/performing-accessibility-testing-for-your-app).
+
+## [Speech](https://developer.apple.com/design/human-interface-guidelines/accessibility#Speech)
+
+
+
+Apple’s accessibility features help people with speech disabilities and people who prefer text-based interactions to communicate effectively using their devices.
+
+**Let people use the keyboard alone to navigate and interact with your app.** People can turn on Full Keyboard Access to navigate apps using their physical keyboard. The system also defines accessibility keyboard shortcuts and a wide range of other [keyboard shortcuts](https://support.apple.com/en-us/102650) that many people use all the time. Avoid overriding system-defined keyboard shortcuts and evaluate your app to ensure it works well with Full Keyboard Access. For additional guidance, see [Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards). For developer guidance, see [Support Full Keyboard Access in your iOS app](https://developer.apple.com/videos/play/wwdc2021/10120).
+
+**Support Switch Control.** Switch Control is an assistive technology that lets people control their devices through separate hardware, game controllers, or sounds such as a click or a pop. People can perform actions like selecting, tapping, typing, and drawing when your app or game supports the ability to navigate using Switch Control. For developer guidance, see [Switch Control](https://developer.apple.com/documentation/Accessibility/switch-control).
+
+## [Cognitive](https://developer.apple.com/design/human-interface-guidelines/accessibility#Cognitive)
+
+
+
+When you minimize complexity in your app or game, all people benefit.
+
+**Keep actions simple and intuitive.** Ensure that people can navigate your interface using easy-to-remember and consistent interactions. Prefer system gestures and behaviors people are already familiar with over creating custom gestures people must learn and retain.
+
+**Minimize use of time-boxed interface elements.** Views and controls that auto-dismiss on a timer can be problematic for people who need longer to process information, and for people who use assistive technologies that require more time to traverse the interface. Prefer dismissing views with an explicit action.
+
+**Consider offering difficulty accommodations in games.** Everyone has their own way of playing and enjoying games. To support a variety of cognitive abilities, consider adding the ability to customize the difficulty level of your game, such as offering options for people to reduce the criteria for successfully completing a level, adjust reaction time, or enable control assistance.
+
+**Let people control audio and video playback.** Avoid autoplaying audio and video content without also providing controls to start and stop it. Make sure these controls are discoverable and easy to act upon, and consider global settings that let people opt out of auto-playing all audio and video. For developer guidance, see [Animated images](https://developer.apple.com/documentation/Accessibility/animated-images) and [`isVideoAutoplayEnabled`](https://developer.apple.com/documentation/UIKit/UIAccessibility/isVideoAutoplayEnabled).
+
+**Allow people to opt out of flashing lights in video playback.** People might want to avoid bright, frequent flashes of light in the media they consume. A Dim Flashing Lights setting allows the system to calculate, mitigate, and inform people about flashing lights in a piece of media. If your app supports video playback, ensure that it responds appropriately to the Dim Flashing Lights setting. For developer guidance, see [Flashing lights](https://developer.apple.com/documentation/MediaAccessibility/flashing-lights).
+
+**Be cautious with fast-moving and blinking animations.** When you use these effects in excess, it can be distracting, cause dizziness, and in some cases even result in epileptic episodes. People who are prone to these effects can turn on the Reduce Motion accessibility setting. When this setting is active, ensure your app or game responds by reducing automatic and repetitive animations, including zooming, scaling, and peripheral motion. Other best practices for reducing motion include:
+
+ * Tightening animation springs to reduce bounce effects
+
+ * Tracking animations directly with people’s gestures
+
+ * Avoiding animating depth changes in z-axis layers
+
+ * Replacing transitions in x-, y-, and z-axes with fades to avoid motion
+
+ * Avoiding animating into and out of blurs
+
+
+
+
+**Optimize your app’s UI for Assistive Access.** Assistive Access is an accessibility feature in iOS and iPadOS that allows people with cognitive disabilities to use a streamlined version of your app. Assistive Access sets a default layout and control presentation for apps that reduces cognitive load, such as the following layout of the Camera app.
+
+
+
+
+
+To optimize your app for this mode, use the following guidelines when Assistive Access is turned on:
+
+ * Identify the core functionality of your app and consider removing noncritical workflows and UI elements.
+
+ * Break up multistep workflows so people can focus on a single interaction per screen.
+
+ * Always ask for confirmation twice whenever people perform an action that’s difficult to recover from, such a deleting a file.
+
+
+
+
+For developer guidance, see [Assistive Access](https://developer.apple.com/documentation/Accessibility/assistive-access).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/accessibility#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/accessibility#visionOS)
+
+visionOS offers a variety of accessibility features people can use to interact with their surroundings in ways that are comfortable and work best for them, including head and hand Pointer Control, and a Zoom feature.
+
+ * Pointer Control (hand)
+ * Pointer Control (head)
+ * Zoom
+
+
+
+Video with custom controls.
+
+Content description: A recording of a person's hand using Pointer Control to interact with content in an app's visionOS window. A line with a pointer at the end extends from the person's hand. It changes position within the field of view as the person moves their hand.
+
+Play
+
+Video with custom controls.
+
+Content description: A recording of someone using Pointer Control to interact with content in an app's visionOS window. The person isn't visible in the recording. Only the pointer is visible. It's centered in the field of view, and the person uses their head movement to position content beneath the pointer.
+
+Play
+
+
+
+**Prioritize comfort.** The immersive nature of visionOS means that interfaces, animations, and interactions have a greater chance of causing motion sickness, and visual and ergonomic discomfort for people. To ensure the most comfortable experience, consider these tips:
+
+ * Keep interface elements within a person’s field of view. Prefer horizontal layouts to vertical ones that might cause neck strain, and avoid demanding the viewer’s attention in different locations in quick succession.
+
+ * Reduce the speed and intensity of animated objects, particularly in someone’s peripheral vision.
+
+ * Be gentle with camera and video motion, and avoid situations where someone may feel like the world around them is moving without their control.
+
+ * Avoid anchoring content to the wearer’s head, which may make them feel stuck and confined, and also prevent them from using assistive technologies like Pointer Control.
+
+ * Minimize the need for large and repetitive gestures, as these can become tiresome and may be difficult depending on a person’s surroundings.
+
+
+
+
+For additional guidance, see [Create accessible spatial experiences](https://developer.apple.com/videos/play/wwdc2023/10034) and [Design considerations for vision and motion](https://developer.apple.com/videos/play/wwdc2023/10078).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/accessibility#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/accessibility#Related)
+
+[Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+[Typography](https://developer.apple.com/design/human-interface-guidelines/typography)
+
+[VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/accessibility#Developer-documentation)
+
+[Building accessible apps](https://developer.apple.com/accessibility/)
+
+[Accessibility framework](https://developer.apple.com/documentation/Accessibility)
+
+[Overview of Accessibility Nutrition Labels](https://devcms.apple.com/help/app-store-connect/manage-app-accessibility/overview-of-accessibility-nutrition-labels)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/accessibility#Videos)
+
+[ Principles of inclusive app design ](https://developer.apple.com/videos/play/wwdc2025/316)
+
+[ Evaluate your app for Accessibility Nutrition Labels ](https://developer.apple.com/videos/play/wwdc2025/224)
+
+[ Catch up on accessibility in SwiftUI ](https://developer.apple.com/videos/play/wwdc2024/10073)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/accessibility#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance and links for Assistive Access, Switch Control, and Accessibility Nutrition Labels.
+March 7, 2025| Expanded and refined all guidance. Moved Dynamic Type guidance to the Typography page, and moved VoiceOver guidance to a new VoiceOver page.
+June 10, 2024| Added a link to Apple’s Unity plug-ins for supporting Dynamic Type.
+December 5, 2023| Updated visionOS Zoom lens artwork.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/app-icons.md b/web-app/public/skills/hig-foundations/references/app-icons.md
new file mode 100644
index 00000000..0b4d62a4
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/app-icons.md
@@ -0,0 +1,210 @@
+---
+title: "App icons | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/app-icons
+
+# App icons
+
+A unique, memorable icon expresses your app’s or game’s purpose and personality and helps people recognize it at a glance.
+
+
+
+Your app icon is a crucial aspect of your app’s or game’s branding and user experience. It appears on the Home Screen and in key locations throughout the system, including search results, notifications, system settings, and share sheets. A well-designed app icon conveys your app’s or game’s identity clearly and consistently across all Apple platforms.
+
+
+
+## [Layer design](https://developer.apple.com/design/human-interface-guidelines/app-icons#Layer-design)
+
+Although you can provide a flattened image for your icon, layers give you the most control over how your icon design is represented. A layered app icon comes together to produce a sense of depth and vitality. On each platform, the system applies visual effects that respond to the environment and people’s interactions.
+
+iOS, iPadOS, macOS, and watchOS app icons include a background layer and one or more foreground layers that coalesce to create dimensionality. These icons take on Liquid Glass attributes like specular highlights, frostiness, and translucency, which respond to changes in lighting and, in iOS and iPadOS, device movement.
+
+Video with custom controls.
+
+Content description: An animation of the Podcasts app icon for iOS. As the animation plays, the icon rotates to the side and expands to show how layers are separated. It then collapses and returns to its original position.
+
+Play
+
+iOS app icon
+
+tvOS app icons use between two and five layers to create a sense of dynamism as people bring them into focus. When focused, the app icon elevates to the foreground in response to someone’s finger movement on their remote, and gently sways while the surface illuminates. The separation between layers and the use of transparency produce a feeling of depth during the parallax effect.
+
+Video with custom controls.
+
+Content description: An animation of the Photos app icon in tvOS moving to show the parallax effect.
+
+Play
+
+tvOS app icon
+
+A visionOS app icon includes a background layer and one or two layers on top, producing a three-dimensional object that subtly expands when people view it. The system enhances the icon’s visual dimensionality by adding shadows that convey a sense of depth between layers and by using the alpha channel of the upper layers to create an embossed appearance.
+
+Video with custom controls.
+
+Content description: An animation of the Photos app icon in visionOS moving to show the parallax effect.
+
+Play
+
+visionOS app icon
+
+You use your favorite design tool to craft the individual foreground layers of your app icon. For iOS, iPadOS, macOS, and watchOS icons, you then import your icon layers into Icon Composer, a design tool included with Xcode and available from the [Apple Developer website](https://developer.apple.com/icon-composer). In Icon Composer, you define the background layer for your icon, adjust your foreground layer placement, apply visual effects like transparency, define default, dark, clear, and tinted appearance variants, and export your icon for use in Xcode. For additional guidance, see [Creating your app icon using Icon Composer](https://developer.apple.com/documentation/Xcode/creating-your-app-icon-using-icon-composer).
+
+Icon Composer
+
+For tvOS and visionOS app icons, you add your icon layers directly to an image stack in Xcode to form your complete icon. For developer guidance, see [Configuring your app icon using an asset catalog](https://developer.apple.com/documentation/Xcode/configuring-your-app-icon).
+
+**Prefer clearly defined edges in foreground layers.** To ensure system-drawn highlights and shadows look best, avoid soft and feathered edges on foreground layer shapes.
+
+**Vary opacity in foreground layers to increase the sense of depth and liveliness.** For example, the Photos icon separates its centerpiece into multiple layers that contain translucent pieces, bringing greater dynamism to the design. Importing fully opaque layers and adjusting transparency in Icon Composer lets you preview and make adjustments to your design based on how transparency and system effects impact one another.
+
+**Design a background that both stands out and emphasizes foreground content.** Subtle top-to-bottom, light-to-dark gradients tend to respond well to system lighting effects. Icon Composer supports solid colors and gradients for background layers, making it unnecessary to import custom background images in most cases. If you do import a background layer, make sure it’s full-bleed and opaque.
+
+**Prefer vector graphics when bringing layers into Icon Composer.** Unlike raster images, vector graphics (such as SVG or PDF) scale gracefully and appear crisp at any size. Outline artwork and convert text to outline in your design. For mesh gradients and raster artwork, prefer PNG format because it’s a lossless image format.
+
+## [Icon shape](https://developer.apple.com/design/human-interface-guidelines/app-icons#Icon-shape)
+
+An app icon’s shape varies based on a platform’s visual language. In iOS, iPadOS, and macOS, icons are square, and the system applies masking to produce rounded corners that precisely match the curvature of other rounded interface elements throughout the system and the bezel of the physical device itself. In tvOS, icons are rectangular, also with concentric edges. In visionOS and watchOS, icons are square and the system applies circular masking.
+
+ * iOS, iPadOS, macOS
+ * tvOS
+ * visionOS, watchOS
+
+
+
+
+
+
+
+
+
+**Produce appropriately shaped, unmasked layers.** The system masks all layer edges to produce an icon’s final shape. For iOS, iPadOS, and macOS icons, provide square layers so the system can apply rounded corners. For visionOS and watchOS, provide square layers so the system can create the circular icon shape. For tvOS, provide rectangular layers so the system can apply rounded corners. Providing layers with pre-defined masking negatively impacts specular highlight effects and makes edges look jagged.
+
+**Keep primary content centered to avoid truncation when the system adjusts corners or applies masking.** Pay particular attention to centering content in visionOS and watchOS icons. To help with icon placement, use the grids in the app icon production templates, which you can find in [Apple Design Resources](https://developer.apple.com/design/resources/).
+
+## [Design](https://developer.apple.com/design/human-interface-guidelines/app-icons#Design)
+
+Embrace simplicity in your icon design. Simple icons tend to be easiest for people to understand and recognize. An icon with fine visual features might look busy when rendered with system-provided shadows and highlights, and details may be hard to discern at smaller sizes. Find a concept or element that captures the essence of your app or game, make it the core idea of your icon, and express it in a simple, unique way with a minimal number of shapes. Prefer a simple background, such as a solid color or gradient, that puts the emphasis on your primary design — you don’t need to fill the entire icon canvas with content.
+
+The Podcasts app icon
+
+The Home app icon
+
+**Provide a visually consistent icon design across all the platforms your app supports.** A consistent design helps people quickly find your app wherever it appears and prevents people from mistaking your app for multiple apps.
+
+**Consider basing your icon design around filled, overlapping shapes.** Overlapping solid shapes in the foreground, particularly when paired with transparency and blurring, can give an icon a sense of depth.
+
+
+
+
+
+
+
+
+
+**Include text only when it’s essential to your experience or brand.** Text in icons doesn’t support accessibility or localization, is often too small to read easily, and can make an icon appear cluttered. In some contexts, your app name already appears nearby, making it redundant to display the name within the icon itself. Although displaying a mnemonic like the first letter of your app’s name can help people recognize your app or game, avoid including nonessential words that tell people what to do with it — like “Watch” or “Play” — or context-specific terms like “New” or “For visionOS.” If you include text in a tvOS app icon, make sure it’s above other layers so it’s not cropped by the parallax effect.
+
+**Prefer illustrations to photos and avoid replicating UI components.** Photos are full of details that don’t work well when displayed in different appearances, viewed at small sizes, or split into layers. Instead of using photos, create a graphic representation of the content that emphasizes the features you want people to notice. Similarly, if your app has an interface that people recognize, don’t just replicate standard UI components or use app screenshots in your icon.
+
+**Don’t use replicas of Apple hardware products.** Apple products are copyrighted and can’t be reproduced in your app icons.
+
+## [Visual effects](https://developer.apple.com/design/human-interface-guidelines/app-icons#Visual-effects)
+
+**Let the system handle blurring and other visual effects.** The system dynamically applies visual effects to your app icon layers, so there’s no need to include specular highlights, drop shadows between layers, beveled edges, blurs, glows, and other effects. In addition to interfering with system-provided effects, custom effects are static, whereas the system supplies dynamic ones. If you do include custom visual effects on your icon layers, use them intentionally and test carefully with Icon Composer, in Simulator, or on device to make sure they appear as expected and don’t conflict with system effects.
+
+**Create layer groupings to apply effects to multiple layers at once.** System effects typically occur on individual layers. If it makes sense for your design, however, you can group several layers together in Icon Composer or your design tool so effects occur at the group level.
+
+## [Appearances](https://developer.apple.com/design/human-interface-guidelines/app-icons#Appearances)
+
+In iOS, iPadOS, and macOS, people can choose whether their Home Screen app icons are default, dark, clear, or tinted in appearance. For example, someone may want to personalize their app icon appearance to complement their wallpaper. You can design app icon variants for every appearance variant, and the system automatically generates variants you don’t provide.
+
+
+
+**Keep your icon’s features consistent across appearances.** To create a seamless experience, keep your icon’s core visual features the same in the default, dark, clear, and tinted appearances. Avoid creating custom icon variants that swap elements in and out with each variant, which may make it harder for people to find your app when they switch appearances.
+
+**Design dark and tinted icons that feel at home beside system app icons and widgets.** You can preserve the color palette of your default icon, but be mindful that dark icons are more subdued, and clear and tinted icons are even more so. A great app icon is visible, legible, and recognizable, regardless of its appearance variant.
+
+**Use your light app icon as the basis for your dark icon.** Choose complementary colors that reflect the default design, and avoid excessively bright images. Color backgrounds generally offer the greatest contrast in dark icons. For guidance, see [Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode).
+
+**Consider offering alternate app icons.** In iOS, iPadOS, tvOS, and compatible apps running in visionOS, it’s possible to let people visit your app’s settings to choose an alternate version of your app icon. For example, a sports app might offer icons for different teams, letting someone choose their favorite. If you offer this capability, make sure each icon you design remains closely related to your content and experience. Avoid creating one someone might mistake for another app.
+
+Note
+
+Alternate app icons in iOS and iPadOS require their own dark, clear, and tinted variants. As with your default app icon, all alternate and variant icons are subject to app review and must adhere to the [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/#design).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/app-icons#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or macOS._
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/app-icons#tvOS)
+
+**Include a safe zone to ensure the system doesn’t crop your content.** When someone focuses your app icon, the system may crop content around the edges as the icon scales and moves. To ensure that your icon’s content is always visible, keep a safe zone around it. Be aware that the safe zone can vary, depending on the image size, layer depth, and motion, and the system crops foreground layers more than background layers.
+
+
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/app-icons#visionOS)
+
+**Avoid adding a shape that’s intended to look like a hole or concave area to the background layer.** The system-added shadow and specular highlights can make such a shape stand out instead of recede.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/app-icons#watchOS)
+
+**Avoid using black for your icon’s background.** Lighten a black background so the icon doesn’t blend into the display background.
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/app-icons#Specifications)
+
+The layout, size, style, and appearances of app icons vary by platform.
+
+Platform| Layout shape| Icon shape after system masking| Layout size| Style| Appearances
+---|---|---|---|---|---
+iOS, iPadOS, macOS| Square| Rounded rectangle (square)| 1024x1024 px| Layered| Default, dark, clear light, clear dark, tinted light, tinted dark
+tvOS| Rectangle (landscape)| Rounded rectangle (rectangular)| 800x480 px| Layered (Parallax)| N/A
+visionOS| Square| Circular| 1024x1024 px| Layered (3D)| N/A
+watchOS| Square| Circular| 1088x1088 px| Layered| N/A
+
+The system automatically scales your icon to produce smaller variants that appear in certain locations, such as Settings and notifications.
+
+App icons support the following color spaces:
+
+ * sRGB (color)
+
+ * Gray Gamma 2.2 (grayscale)
+
+ * Display P3 (wide-gamut color in iOS, iPadOS, macOS, tvOS, and watchOS only)
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/app-icons#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/app-icons#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+[Icon Composer](https://developer.apple.com/icon-composer/)
+
+[Icons](https://developer.apple.com/design/human-interface-guidelines/icons)
+
+[Images](https://developer.apple.com/design/human-interface-guidelines/images)
+
+[Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/app-icons#Developer-documentation)
+
+[Creating your app icon using Icon Composer](https://developer.apple.com/documentation/Xcode/creating-your-app-icon-using-icon-composer)
+
+[Configuring your app icon using an asset catalog](https://developer.apple.com/documentation/Xcode/configuring-your-app-icon)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/app-icons#Videos)
+
+[ Say hello to the new look of app icons ](https://developer.apple.com/videos/play/wwdc2025/220)
+
+[ Create icons with Icon Composer ](https://developer.apple.com/videos/play/wwdc2025/361)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/app-icons#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated guidance to reflect layered icons, consistency across platforms, and best practices for Liquid Glass.
+June 10, 2024| Added guidance for creating dark and tinted app icon variants for iOS and iPadOS.
+January 31, 2024| Clarified platform availability for alternate app icons.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Added specifications for Apple Watch Ultra.
+
diff --git a/web-app/public/skills/hig-foundations/references/branding.md b/web-app/public/skills/hig-foundations/references/branding.md
new file mode 100644
index 00000000..e8d70219
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/branding.md
@@ -0,0 +1,44 @@
+---
+title: "Branding | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/branding
+
+# Branding
+
+Apps and games express their unique brand identity in ways that make them instantly recognizable while feeling at home on the platform and giving people a consistent experience.
+
+
+
+In addition to expressing your brand in your [app icon](https://developer.apple.com/design/human-interface-guidelines/app-icons) and throughout your experience, you have several opportunities to highlight it within the App Store. For guidance, see [App Store Marketing Guidelines](https://developer.apple.com/app-store/marketing/guidelines/).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/branding#Best-practices)
+
+**Use your brand’s unique voice and tone in all the written communication you display.** For example, your brand might convey feelings of encouragement and optimism by using plain words, occasional exclamation marks and emoji, and simple sentence structures.
+
+**Consider choosing an accent color.** On most platforms, you can specify a color that the system applies to app elements like interface icons, buttons, and text. In macOS, people can also choose their own accent color that the system can use in place of the color an app specifies. For guidance, see [Color](https://developer.apple.com/design/human-interface-guidelines/color).
+
+**Consider using a custom font.** If your brand is strongly associated with a specific font, be sure that it’s legible at all sizes and supports accessibility features like bold text and larger type. It can work well to use a custom font for headlines and subheadings while using a system font for body copy and captions, because the system fonts are designed for optimal legibility at small sizes. For guidance, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography).
+
+**Ensure branding always defers to content.** Using screen space for an element that does nothing but display a brand asset can mean there’s less room for the content people care about. Aim to incorporate branding in refined, unobtrusive ways that don’t distract people from your experience.
+
+**Help people feel comfortable by using standard patterns consistently.** Even a highly stylized interface can be approachable if it maintains familiar behaviors. For example, place UI components in expected locations and use standard symbols to represent common actions.
+
+**Resist the temptation to display your logo throughout your app or game unless it’s essential for providing context.** People seldom need to be reminded which app they’re using, and it’s usually better to use the space to give people valuable information and controls.
+
+**Avoid using a launch screen as a branding opportunity.** Some platforms use a launch screen to minimize the startup experience, while simultaneously giving the app or game a little time to load resources (for guidance, see [Launch screens](https://developer.apple.com/design/human-interface-guidelines/launching#Launch-screens)). A launch screen disappears too quickly to convey any information, but you might consider displaying a welcome or onboarding screen that incorporates your branding content at the beginning of your experience. For guidance, see [Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding).
+
+**Follow Apple’s trademark guidelines.** Apple trademarks must not appear in your app name or images. See [Apple Trademark List](https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html) and [Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/branding#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/branding#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/branding#Related)
+
+[Marketing resources and identity guidelines](https://developer.apple.com/app-store/marketing/guidelines/)
+
+[Show more with app previews](https://developer.apple.com/app-store/app-previews/)
+
+[Color](https://developer.apple.com/design/human-interface-guidelines/color)
+
diff --git a/web-app/public/skills/hig-foundations/references/color.md b/web-app/public/skills/hig-foundations/references/color.md
new file mode 100644
index 00000000..8cfea29d
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/color.md
@@ -0,0 +1,274 @@
+---
+title: "Color | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/color
+
+# Color
+
+Judicious use of color can enhance communication, evoke your brand, provide visual continuity, communicate status and feedback, and help people understand information.
+
+
+
+The system defines colors that look good on various backgrounds and appearance modes, and can automatically adapt to vibrancy and accessibility settings. Using system colors is a convenient way to make your experience feel at home on the device.
+
+You may also want to use custom colors to enhance the visual experience of your app or game and express its unique personality. The following guidelines can help you use color in ways that people appreciate, regardless of whether you use system-defined or custom colors.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/color#Best-practices)
+
+**Avoid using the same color to mean different things.** Use color consistently throughout your interface, especially when you use it to help communicate information like status or interactivity. For example, if you use your brand color to indicate that a borderless button is interactive, using the same or similar color to stylize noninteractive text is confusing.
+
+**Make sure all your app’s colors work well in light, dark, and increased contrast contexts.** iOS, iPadOS, macOS, and tvOS offer both light and [dark](https://developer.apple.com/design/human-interface-guidelines/dark-mode) appearance settings. [System colors](https://developer.apple.com/design/human-interface-guidelines/color#System-colors) vary subtly depending on the system appearance, adjusting to ensure proper color differentiation and contrast for text, symbols, and other elements. With the Increase Contrast setting turned on, the color differences become far more apparent. When possible, use system colors, which already define variants for all these contexts. If you define a custom color, make sure to supply light and dark variants, and an increased contrast option for each variant that provides a significantly higher amount of visual differentiation. Even if your app ships in a single appearance mode, provide both light and dark colors to support Liquid Glass adaptivity in these contexts.
+
+
+
+Default (light)
+
+
+
+Increased contrast (light)
+
+
+
+Default (dark)
+
+
+
+Increased contrast (dark)
+
+**Test your app’s color scheme under a variety of lighting conditions.** Colors can look different when you view your app outside on a sunny day or in dim light. In bright surroundings, colors look darker and more muted. In dark environments, colors appear bright and saturated. In visionOS, colors can look different depending on the colors of a wall or object in a person’s physical surroundings and how it reflects light. Adjust app colors to provide an optimal viewing experience in the majority of use cases.
+
+**Test your app on different devices.** For example, the True Tone display — available on certain iPhone, iPad, and Mac models — uses ambient light sensors to automatically adjust the white point of the display to adapt to the lighting conditions of the current environment. Apps that primarily support reading, photos, video, and gaming can strengthen or weaken this effect by specifying a white point adaptivity style (for developer guidance, see [`UIWhitePointAdaptivityStyle`](https://developer.apple.com/documentation/BundleResources/Information-Property-List/UIWhitePointAdaptivityStyle)). Test tvOS apps on multiple brands of HD and 4K TVs, and with different display settings. You can also test the appearance of your app using different color profiles on a Mac — such as P3 and Standard RGB (sRGB) — by choosing a profile in System Settings > Displays. For guidance, see [Color management](https://developer.apple.com/design/human-interface-guidelines/color#Color-management).
+
+**Consider how artwork and translucency affect nearby colors.** Variations in artwork sometimes warrant changes to nearby colors to maintain visual continuity and prevent interface elements from becoming overpowering or underwhelming. Maps, for example, displays a light color scheme when in map mode but switches to a dark color scheme when in satellite mode. Colors can also appear different when placed behind or applied to a translucent element like a toolbar.
+
+**If your app lets people choose colors, prefer system-provided color controls where available.** Using built-in color pickers provides a consistent user experience, in addition to letting people save a set of colors they can access from any app. For developer guidance, see [`ColorPicker`](https://developer.apple.com/documentation/SwiftUI/ColorPicker).
+
+## [Inclusive color](https://developer.apple.com/design/human-interface-guidelines/color#Inclusive-color)
+
+**Avoid relying solely on color to differentiate between objects, indicate interactivity, or communicate essential information.** When you use color to convey information, be sure to provide the same information in alternative ways so people with color blindness or other visual disabilities can understand it. For example, you can use text labels or glyph shapes to identify objects or states.
+
+**Avoid using colors that make it hard to perceive content in your app.** For example, insufficient contrast can cause icons and text to blend with the background and make content hard to read, and people who are color blind might not be able to distinguish some color combinations. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Consider how the colors you use might be perceived in other countries and cultures.** For example, red communicates danger in some cultures, but has positive connotations in other cultures. Make sure the colors in your app send the message you intend.
+
+Green indicates a positive trend in the Stocks app in English.
+
+Red indicates a positive trend in the Stocks app in Chinese.
+
+## [System colors](https://developer.apple.com/design/human-interface-guidelines/color#System-colors)
+
+**Avoid hard-coding system color values in your app.** Documented color values are for your reference during the app design process. The actual color values may fluctuate from release to release, based on a variety of environmental variables. Use APIs like [`Color`](https://developer.apple.com/documentation/SwiftUI/Color) to apply system colors.
+
+iOS, iPadOS, macOS, and visionOS also define sets of _dynamic system colors_ that match the color schemes of standard UI components and automatically adapt to both light and dark contexts. Each dynamic color is semantically defined by its purpose, rather than its appearance or color values. For example, some colors represent view backgrounds at different levels of hierarchy and other colors represent foreground content, such as labels, links, and separators.
+
+**Avoid redefining the semantic meanings of dynamic system colors.** To ensure a consistent experience and ensure your interface looks great when the appearance of the platform changes, use dynamic system colors as intended. For example, don’t use the [separator](https://developer.apple.com/documentation/uikit/uicolor/separator) color as a text color, or [secondary text label](https://developer.apple.com/documentation/uikit/uicolor/secondarylabel) color as a background color.
+
+## [Liquid Glass color](https://developer.apple.com/design/human-interface-guidelines/color#Liquid-Glass-color)
+
+By default, [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) has no inherent color, and instead takes on colors from the content directly behind it. You can apply color to some Liquid Glass elements, giving them the appearance of colored or stained glass. This is useful for drawing emphasis to a specific control, like a primary call to action, and is the approach the system uses for prominent button styling. Symbols or text labels on Liquid Glass controls can also have color.
+
+Controls can use color in the Liquid Glass background, like in a primary action button.
+
+Symbols and text that appear on Liquid Glass can have color, like in a selected tab bar item.
+
+By default, Liquid Glass picks up the color from the content layer behind it.
+
+For smaller elements like toolbars and tab bars, the system can adapt Liquid Glass between a light and dark appearance in response to the underlying content. By default, symbols and text on these elements follow a monochromatic color scheme, becoming darker when the underlying content is light, and lighter when it’s dark. Liquid Glass appears more opaque in larger elements like sidebars to preserve legibility over complex backgrounds and accommodate richer content on the material’s surface.
+
+**Apply color sparingly to the Liquid Glass material, and to symbols or text on the material.** If you apply color, reserve it for elements that truly benefit from emphasis, such as status indicators or primary actions. To emphasize primary actions, apply color to the background rather than to symbols or text. For example, the system applies the app accent color to the background in prominent buttons — such as the Done button — to draw attention and elevate their visual prominence. Refrain from adding color to the background of multiple controls.
+
+
+
+
+
+
+
+
+
+**Avoid using similar colors in control labels if your app has a colorful background.** While color can make apps more visually appealing, playful, or reflective of your brand, too much color can be overwhelming and make control labels more difficult to read. If your app features colorful backgrounds or visually rich content, prefer a monochromatic appearance for toolbars and tab bars, or choose an accent color with sufficient visual differentiation. By contrast, in apps with primarily monochromatic content or backgrounds, choosing your brand color as the app accent color can be an effective way to tailor your app experience and reflect your company’s identity.
+
+**Be aware of the placement of color in the content layer.** Make sure your interface maintains sufficient contrast by avoiding overlap of similar colors in the content layer and controls when possible. Although colorful content might intermittently scroll underneath controls, make sure its default or resting state — like the top of a screen of scrollable content — maintains clear legibility.
+
+## [Color management](https://developer.apple.com/design/human-interface-guidelines/color#Color-management)
+
+A _color space_ represents the colors in a _color model_ like RGB or CMYK. Common color spaces — sometimes called _gamuts_ — are sRGB and Display P3.
+
+
+
+A _color profile_ describes the colors in a color space using, for example, mathematical formulas or tables of data that map colors to numerical representations. An image embeds its color profile so that a device can interpret the image’s colors correctly and reproduce them on a display.
+
+**Apply color profiles to your images.** Color profiles help ensure that your app’s colors appear as intended on different displays. The sRGB color space produces accurate colors on most displays.
+
+**Use wide color to enhance the visual experience on compatible displays.** Wide color displays support a P3 color space, which can produce richer, more saturated colors than sRGB. As a result, photos and videos that use wide color are more lifelike, and visual data and status indicators that use wide color can be more meaningful. When appropriate, use the Display P3 color profile at 16 bits per pixel (per channel) and export images in PNG format. Note that you need to use a wide color display to design wide color images and select P3 colors.
+
+**Provide color space–specific image and color variations if necessary.** In general, P3 colors and images appear fine on sRGB displays. Occasionally, it may be hard to distinguish two very similar P3 colors when viewing them on an sRGB display. Gradients that use P3 colors can also sometimes appear clipped on sRGB displays. To avoid these issues and to ensure visual fidelity on both wide color and sRGB displays, you can use the asset catalog of your Xcode project to provide different versions of images and colors for each color space.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/color#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/color#iOS-iPadOS)
+
+iOS defines two sets of dynamic background colors — _system_ and _grouped_ — each of which contains primary, secondary, and tertiary variants that help you convey a hierarchy of information. In general, use the grouped background colors ([`systemGroupedBackground`](https://developer.apple.com/documentation/UIKit/UIColor/systemGroupedBackground), [`secondarySystemGroupedBackground`](https://developer.apple.com/documentation/UIKit/UIColor/secondarySystemGroupedBackground), and [`tertiarySystemGroupedBackground`](https://developer.apple.com/documentation/UIKit/UIColor/tertiarySystemGroupedBackground)) when you have a grouped table view; otherwise, use the system set of background colors ([`systemBackground`](https://developer.apple.com/documentation/UIKit/UIColor/systemBackground), [`secondarySystemBackground`](https://developer.apple.com/documentation/UIKit/UIColor/secondarySystemBackground), and [`tertiarySystemBackground`](https://developer.apple.com/documentation/UIKit/UIColor/tertiarySystemBackground)).
+
+With both sets of background colors, you generally use the variants to indicate hierarchy in the following ways:
+
+ * Primary for the overall view
+
+ * Secondary for grouping content or elements within the overall view
+
+ * Tertiary for grouping content or elements within secondary elements
+
+
+
+
+For foreground content, iOS defines the following dynamic colors:
+
+Color| Use for…| UIKit API
+---|---|---
+Label| A text label that contains primary content.| [`label`](https://developer.apple.com/documentation/UIKit/UIColor/label)
+Secondary label| A text label that contains secondary content.| [`secondaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/secondaryLabel)
+Tertiary label| A text label that contains tertiary content.| [`tertiaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/tertiaryLabel)
+Quaternary label| A text label that contains quaternary content.| [`quaternaryLabel`](https://developer.apple.com/documentation/UIKit/UIColor/quaternaryLabel)
+Placeholder text| Placeholder text in controls or text views.| [`placeholderText`](https://developer.apple.com/documentation/UIKit/UIColor/placeholderText)
+Separator| A separator that allows some underlying content to be visible.| [`separator`](https://developer.apple.com/documentation/UIKit/UIColor/separator)
+Opaque separator| A separator that doesn’t allow any underlying content to be visible.| [`opaqueSeparator`](https://developer.apple.com/documentation/UIKit/UIColor/opaqueSeparator)
+Link| Text that functions as a link.| [`link`](https://developer.apple.com/documentation/UIKit/UIColor/link)
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/color#macOS)
+
+macOS defines the following dynamic system colors (you can also view them in the Developer palette of the standard Color panel):
+
+Color| Use for…| AppKit API
+---|---|---
+Alternate selected control text color| The text on a selected surface in a list or table.| [`alternateSelectedControlTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/alternateSelectedControlTextColor)
+Alternating content background colors| The backgrounds of alternating rows or columns in a list, table, or collection view.| [`alternatingContentBackgroundColors`](https://developer.apple.com/documentation/AppKit/NSColor/alternatingContentBackgroundColors)
+Control accent| The accent color people select in System Settings.| [`controlAccentColor`](https://developer.apple.com/documentation/AppKit/NSColor/controlAccentColor)
+Control background color| The background of a large interface element, such as a browser or table.| [`controlBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/controlBackgroundColor)
+Control color| The surface of a control.| [`controlColor`](https://developer.apple.com/documentation/AppKit/NSColor/controlColor)
+Control text color| The text of a control that is available.| [`controlTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/controlTextColor)
+Current control tint| The system-defined control tint.| [`currentControlTint`](https://developer.apple.com/documentation/AppKit/NSColor/currentControlTint)
+Unavailable control text color| The text of a control that’s unavailable.| [`disabledControlTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/disabledControlTextColor)
+Find highlight color| The color of a find indicator.| [`findHighlightColor`](https://developer.apple.com/documentation/AppKit/NSColor/findHighlightColor)
+Grid color| The gridlines of an interface element, such as a table.| [`gridColor`](https://developer.apple.com/documentation/AppKit/NSColor/gridColor)
+Header text color| The text of a header cell in a table.| [`headerTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/headerTextColor)
+Highlight color| The virtual light source onscreen.| [`highlightColor`](https://developer.apple.com/documentation/AppKit/NSColor/highlightColor)
+Keyboard focus indicator color| The ring that appears around the currently focused control when using the keyboard for interface navigation.| [`keyboardFocusIndicatorColor`](https://developer.apple.com/documentation/AppKit/NSColor/keyboardFocusIndicatorColor)
+Label color| The text of a label containing primary content.| [`labelColor`](https://developer.apple.com/documentation/AppKit/NSColor/labelColor)
+Link color| A link to other content.| [`linkColor`](https://developer.apple.com/documentation/AppKit/NSColor/linkColor)
+Placeholder text color| A placeholder string in a control or text view.| [`placeholderTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/placeholderTextColor)
+Quaternary label color| The text of a label of lesser importance than a tertiary label, such as watermark text.| [`quaternaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/quaternaryLabelColor)
+Secondary label color| The text of a label of lesser importance than a primary label, such as a label used to represent a subheading or additional information.| [`secondaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/secondaryLabelColor)
+Selected content background color| The background for selected content in a key window or view.| [`selectedContentBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedContentBackgroundColor)
+Selected control color| The surface of a selected control.| [`selectedControlColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedControlColor)
+Selected control text color| The text of a selected control.| [`selectedControlTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedControlTextColor)
+Selected menu item text color| The text of a selected menu.| [`selectedMenuItemTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedMenuItemTextColor)
+Selected text background color| The background of selected text.| [`selectedTextBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedTextBackgroundColor)
+Selected text color| The color for selected text.| [`selectedTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/selectedTextColor)
+Separator color| A separator between different sections of content.| [`separatorColor`](https://developer.apple.com/documentation/AppKit/NSColor/separatorColor)
+Shadow color| The virtual shadow cast by a raised object onscreen.| [`shadowColor`](https://developer.apple.com/documentation/AppKit/NSColor/shadowColor)
+Tertiary label color| The text of a label of lesser importance than a secondary label.| [`tertiaryLabelColor`](https://developer.apple.com/documentation/AppKit/NSColor/tertiaryLabelColor)
+Text background color| The background color behind text.| [`textBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/textBackgroundColor)
+Text color| The text in a document.| [`textColor`](https://developer.apple.com/documentation/AppKit/NSColor/textColor)
+Under page background color| The background behind a document’s content.| [`underPageBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/underPageBackgroundColor)
+Unemphasized selected content background color| The selected content in a non-key window or view.| [`unemphasizedSelectedContentBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/unemphasizedSelectedContentBackgroundColor)
+Unemphasized selected text background color| A background for selected text in a non-key window or view.| [`unemphasizedSelectedTextBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/unemphasizedSelectedTextBackgroundColor)
+Unemphasized selected text color| Selected text in a non-key window or view.| [`unemphasizedSelectedTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/unemphasizedSelectedTextColor)
+Window background color| The background of a window.| [`windowBackgroundColor`](https://developer.apple.com/documentation/AppKit/NSColor/windowBackgroundColor)
+Window frame text color| The text in the window’s title bar area.| [`windowFrameTextColor`](https://developer.apple.com/documentation/AppKit/NSColor/windowFrameTextColor)
+
+#### [App accent colors](https://developer.apple.com/design/human-interface-guidelines/color#App-accent-colors)
+
+Beginning in macOS 11, you can specify an _accent color_ to customize the appearance of your app’s buttons, selection highlighting, and sidebar icons. The system applies your accent color when the current value in General > Accent color settings is _multicolor_.
+
+
+
+If people set their accent color setting to a value other than multicolor, the system applies their chosen color to the relevant items throughout your app, replacing your accent color. The exception is a sidebar icon that uses a fixed color you specify. Because a fixed-color sidebar icon uses a specific color to provide meaning, the system doesn’t override its color when people change the value of accent color settings. For guidance, see [Sidebars](https://developer.apple.com/design/human-interface-guidelines/sidebars).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/color#tvOS)
+
+**Consider choosing a limited color palette that coordinates with your app logo.** Subtle use of color can help you communicate your brand while deferring to the content.
+
+**Avoid using only color to indicate focus.** Subtle scaling and responsive animation are the primary ways to denote interactivity when an element is in focus.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/color#visionOS)
+
+**Use color sparingly, especially on glass.** Standard visionOS windows typically use the system-defined glass [material](https://developer.apple.com/design/human-interface-guidelines/materials), which lets light and objects from people’s physical surroundings and their space show through. Because the colors in these physical and virtual objects are visible through the glass, they can affect the legibility of colorful app content in the window. Prefer using color in places where it can help call attention to important information or show the relationship between parts of the interface.
+
+**Prefer using color in bold text and large areas.** Color in lightweight text or small areas can make them harder to see and understand.
+
+**In a fully immersive experience, help people maintain visual comfort by keeping brightness levels balanced.** Although using high contrast can help direct people’s attention to important content, it can also cause visual discomfort if people’s eyes have adjusted to low light or darkness. Consider making content fully bright only when the rest of the visual context is also bright. For example, avoid displaying a bright object on a very dark or black background, especially if the object flashes or moves.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/color#watchOS)
+
+**Use background color to support existing content or supply additional information.** Background color can establish a sense of place and help people recognize key content. For example, in Activity, each infographic view for the Move, Exercise, and Stand Activity rings has a background that matches the color of the ring. Use background color when you have something to communicate, rather than as a solely visual flourish. Avoid using full-screen background color in views that are likely to remain onscreen for long periods of time, such as in a workout or audio-playing app.
+
+**Recognize that people might prefer graphic complications to use tinted mode instead of full color.** The system can use a single color that’s based on the wearer’s selected color in a graphic complication’s images, gauges, and text. For guidance, see [Complications](https://developer.apple.com/design/human-interface-guidelines/complications).
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/color#Specifications)
+
+### [System colors](https://developer.apple.com/design/human-interface-guidelines/color#System-colors)
+
+Name| SwiftUI API| Default (light)| Default (dark)| Increased contrast (light)| Increased contrast (dark)
+---|---|---|---|---|---
+Red| [`red`](https://developer.apple.com/documentation/SwiftUI/Color/red)| | | | 
+Orange| [`orange`](https://developer.apple.com/documentation/SwiftUI/Color/orange)| | | | 
+Yellow| [`yellow`](https://developer.apple.com/documentation/SwiftUI/Color/yellow)| | | | 
+Green| [`green`](https://developer.apple.com/documentation/SwiftUI/Color/green)| | | | 
+Mint| [`mint`](https://developer.apple.com/documentation/SwiftUI/Color/mint)| | | | 
+Teal| [`teal`](https://developer.apple.com/documentation/SwiftUI/Color/teal)| | | | 
+Cyan| [`cyan`](https://developer.apple.com/documentation/SwiftUI/Color/cyan)| | | | 
+Blue| [`blue`](https://developer.apple.com/documentation/SwiftUI/Color/blue)| | | | 
+Indigo| [`indigo`](https://developer.apple.com/documentation/SwiftUI/Color/indigo)| | | | 
+Purple| [`purple`](https://developer.apple.com/documentation/SwiftUI/Color/purple)| | | | 
+Pink| [`pink`](https://developer.apple.com/documentation/SwiftUI/Color/pink)| | | | 
+Brown| [`brown`](https://developer.apple.com/documentation/SwiftUI/Color/brown)| | | | 
+
+visionOS system colors use the default dark color values.
+
+### [iOS, iPadOS system gray colors](https://developer.apple.com/design/human-interface-guidelines/color#iOS-iPadOS-system-gray-colors)
+
+Name| UIKit API| Default (light)| Default (dark)| Increased contrast (light)| Increased contrast (dark)
+---|---|---|---|---|---
+Gray| [`systemGray`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray)| | | | 
+Gray (2)| [`systemGray2`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray2)| | | | 
+Gray (3)| [`systemGray3`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray3)| | | | 
+Gray (4)| [`systemGray4`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray4)| | | | 
+Gray (5)| [`systemGray5`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray5)| | | | 
+Gray (6)| [`systemGray6`](https://developer.apple.com/documentation/UIKit/UIColor/systemGray6)| | | | 
+
+In SwiftUI, the equivalent of `systemGray` is [`gray`](https://developer.apple.com/documentation/SwiftUI/Color/gray).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/color#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/color#Related)
+
+[Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[Materials](https://developer.apple.com/design/human-interface-guidelines/materials)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/color#Developer-documentation)
+
+[`Color`](https://developer.apple.com/documentation/SwiftUI/Color) — SwiftUI
+
+[`UIColor`](https://developer.apple.com/documentation/UIKit/UIColor) — UIKit
+
+[Color](https://developer.apple.com/documentation/AppKit/color) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/color#Videos)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/color#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Updated guidance for Liquid Glass.
+June 9, 2025| Updated system color values, and added guidance for Liquid Glass.
+February 2, 2024| Distinguished UIKit and SwiftUI gray colors in iOS and iPadOS, and added guidance for balancing brightness levels in visionOS apps.
+September 12, 2023| Enhanced guidance for using background color in watchOS views, and added color swatches for tvOS.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Updated guidance for using background color in watchOS.
+December 19, 2022| Corrected RGB values for system mint color (Dark Mode) in iOS and iPadOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/dark-mode.md b/web-app/public/skills/hig-foundations/references/dark-mode.md
new file mode 100644
index 00000000..a7ad3cac
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/dark-mode.md
@@ -0,0 +1,116 @@
+---
+title: "Dark Mode | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/dark-mode
+
+# Dark Mode
+
+Dark Mode is a systemwide appearance setting that uses a dark color palette to provide a comfortable viewing experience tailored for low-light environments.
+
+
+
+In iOS, iPadOS, macOS, and tvOS, people often choose Dark Mode as their default interface style, and they generally expect all apps and games to respect their preference. In Dark Mode, the system uses a dark color palette for all screens, views, menus, and controls, and may also use greater perceptual contrast to make foreground content stand out against the darker backgrounds.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Best-practices)
+
+**Avoid offering an app-specific appearance setting.** An app-specific appearance mode option creates more work for people because they have to adjust more than one setting to get the appearance they want. Worse, they may think your app is broken because it doesn’t respond to their systemwide appearance choice.
+
+**Ensure that your app looks good in both appearance modes.** In addition to using one mode or the other, people can choose the Auto appearance setting, which switches between the light and dark appearances as conditions change throughout the day, potentially while your app is running.
+
+**Test your content to make sure that it remains comfortably legible in both appearance modes.** For example, in Dark Mode with Increase Contrast and Reduce Transparency turned on (both separately and together), you may find places where dark text is less legible when it’s on a dark background. You might also find that turning on Increase Contrast in Dark Mode can result in reduced visual contrast between dark text and a dark background. Although people with strong vision might still be able to read lower contrast text, such text could be illegible for many. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**In rare cases, consider using only a dark appearance in the interface.** For example, it can make sense for an app that supports immersive media viewing to use a permanently dark appearance that lets the UI recede and helps people focus on the media.
+
+
+
+The Stocks app uses a dark-only appearance
+
+## [Dark Mode colors](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Dark-Mode-colors)
+
+The color palette in Dark Mode includes dimmer background colors and brighter foreground colors. It’s important to realize that these colors aren’t necessarily inversions of their light counterparts: while many colors are inverted, some are not. For more information, see [Specifications](https://developer.apple.com/design/human-interface-guidelines/color#Specifications).
+
+**Embrace colors that adapt to the current appearance.** Semantic colors (like [`labelColor`](https://developer.apple.com/documentation/AppKit/NSColor/labelColor) and [`controlColor`](https://developer.apple.com/documentation/AppKit/NSColor/controlColor) in macOS or [`separator`](https://developer.apple.com/documentation/UIKit/UIColor/separator) in iOS and iPadOS) automatically adapt to the current appearance. When you need a custom color, add a Color Set asset to your app’s asset catalog in Xcode, and specify the bright and dim variants of the color. Avoid using hard-coded color values or colors that don’t adapt.
+
+System colors in the light appearance
+
+System colors in the dark appearance
+
+**Aim for sufficient color contrast in all appearances.** Using system-defined colors can help you achieve a good contrast ratio between your foreground and background content. At a minimum, make sure the contrast ratio between colors is no lower than 4.5:1. For custom foreground and background colors, strive for a contrast ratio of 7:1, especially in small text. This ratio ensures that your foreground content stands out from the background, and helps your content meet recommended accessibility guidelines.
+
+**Soften the color of white backgrounds.** If you display a content image that includes a white background, consider slightly darkening the image to prevent the background from glowing in the surrounding Dark Mode context.
+
+### [Icons and images](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Icons-and-images)
+
+The system uses [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) (which automatically adapt to Dark Mode) and full-color images that are optimized for both the light and dark appearances.
+
+**Use SF Symbols wherever possible.** Symbols work well in both appearance modes when you use dynamic colors to tint them or when you add vibrancy. For guidance, see [Color](https://developer.apple.com/design/human-interface-guidelines/color).
+
+**Design separate interface icons for the light and dark appearances if necessary.** For example, an icon that depicts a full moon might need a subtle dark outline to contrast well with a light background, but need no outline when it displays on a dark background. Similarly, an icon that represents a drop of oil might need a slight border to make the edge visible against a dark background.
+
+Icon in the light appearance with no border
+
+Icon in the dark appearance with border for better contrast
+
+**Make sure full-color images and icons look good in both appearances.** Use the same asset if it looks good in both the light and dark appearances. If an asset looks good in only one mode, modify the asset or create separate light and dark assets. Use asset catalogs to combine your assets into a single named image.
+
+Illustration on a light background
+
+On a dark background, the same illustration has poor contrast and many details are lost
+
+Illustration adjusted for better contrast on a dark background
+
+### [Text](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Text)
+
+The system uses vibrancy and increased contrast to maintain the legibility of text on darker backgrounds.
+
+**Use the system-provided label colors for labels.** The primary, secondary, tertiary, and quaternary label colors adapt automatically to the light and dark appearances.
+
+Primary label in the light appearance
+
+Secondary label in the dark appearance
+
+**Use system views to draw text fields and text views.** System views and controls make your app’s text look good on all backgrounds, adjusting automatically for the presence or absence of vibrancy. When possible, use a system-provided view to display text instead of drawing the text yourself.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Platform-considerations)
+
+ _No additional considerations for tvOS. Dark Mode isn’t supported in visionOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/dark-mode#iOS-iPadOS)
+
+In Dark Mode, the system uses two sets of background colors — called _base_ and _elevated_ — to enhance the perception of depth when one dark interface is layered above another. The base colors are dimmer, making background interfaces appear to recede, and the elevated colors are brighter, making foreground interfaces appear to advance.
+
+Base
+
+Elevated
+
+Light
+
+**Prefer the system background colors.** Dark Mode is dynamic, which means that the background color automatically changes from base to elevated when an interface is in the foreground, such as a popover or modal sheet. The system also uses the elevated background color to provide visual separation between apps in a multitasking environment and between windows in a multiple-window context. Using a custom background color can make it harder for people to perceive these system-provided visual distinctions.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/dark-mode#macOS)
+
+When people choose the graphite accent color in General settings, macOS causes window backgrounds to pick up color from the current desktop picture. The result — called _desktop tinting_ — is a subtle effect that helps windows blend more harmoniously with their surrounding content.
+
+**Include some transparency in custom component backgrounds when appropriate.** Transparency lets your components pick up color from the window background when desktop tinting is active, creating a visual harmony that can persist even when the desktop picture changes. To help achieve this harmony, add transparency only to a custom component that has a visible background or bezel, and only when the component is in a neutral state, such as state that doesn’t use color. You don’t want to add transparency when the component is in a state that uses color, because doing so can cause the component’s color to fluctuate when the window background adjusts to a different location on the desktop or when the desktop picture changes.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Related)
+
+[Color](https://developer.apple.com/design/human-interface-guidelines/color)
+
+[Materials](https://developer.apple.com/design/human-interface-guidelines/materials)
+
+[Typography](https://developer.apple.com/design/human-interface-guidelines/typography)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Videos)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+[ Implementing Dark Mode on iOS ](https://developer.apple.com/videos/play/wwdc2019/214)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/dark-mode#Change-log)
+
+Date| Changes
+---|---
+August 6, 2024| Added art contrasting the light and dark appearances.
+
diff --git a/web-app/public/skills/hig-foundations/references/icons.md b/web-app/public/skills/hig-foundations/references/icons.md
new file mode 100644
index 00000000..69b46b4f
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/icons.md
@@ -0,0 +1,263 @@
+---
+title: "Icons | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/icons
+
+# Icons
+
+An effective icon is a graphic asset that expresses a single concept in ways people instantly understand.
+
+
+
+Apps and games use a variety of simple icons to help people understand the items, actions, and modes they can choose. Unlike [app icons](https://developer.apple.com/design/human-interface-guidelines/app-icons), which can use rich visual details like shading, texturing, and highlighting to evoke the app’s personality, an _interface icon_ typically uses streamlined shapes and touches of color to communicate a straightforward idea.
+
+You can design interface icons — also called _glyphs_ — or you can choose symbols from the SF Symbols app, using them as-is or customizing them to suit your needs. Both interface icons and symbols use black and clear colors to define their shapes; the system can apply other colors to the black areas in each image. For guidance, see [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/icons#Best-practices)
+
+**Create a recognizable, highly simplified design.** Too many details can make an interface icon confusing or unreadable. Strive for a simple, universal design that most people will recognize quickly. In general, icons work best when they use familiar visual metaphors that are directly related to the actions they initiate or content they represent.
+
+**Maintain visual consistency across all interface icons in your app.** Whether you use only custom icons or mix custom and system-provided ones, all interface icons in your app need to use a consistent size, level of detail, stroke thickness (or weight), and perspective. Depending on the visual weight of an icon, you may need to adjust its dimensions to ensure that it appears visually consistent with other icons.
+
+To help achieve visual consistency, adjust individual icon sizes as necessary…
+
+…and use the same stroke weight in every icon.
+
+**In general, match the weights of interface icons and adjacent text.** Unless you want to emphasize either the icons or the text, using the same weight for both gives your content a consistent appearance and level of emphasis.
+
+**If necessary, add padding to a custom interface icon to achieve optical alignment.** Some icons — especially asymmetric ones — can look unbalanced when you center them geometrically instead of optically. For example, the download icon shown below has more visual weight on the bottom than on the top, which can make it look too low if it’s geometrically centered.
+
+An asymmetric icon can look off center even though it’s not.
+
+In such cases, you can slightly adjust the position of the icon until it’s optically centered. When you create an asset that includes your adjustments as padding around an interface icon (as shown below on the right), you can optically center the icon by geometrically centering the asset.
+
+Moving the icon a few pixels higher optically centers it; including the pixels in padding simplifies centering.
+
+Adjustments for optical centering are typically very small, but they can have a big impact on your app’s appearance.
+
+Before optical centering (left) and after optical centering (right).
+
+**Provide a selected-state version of an interface icon only if necessary.** You don’t need to provide selected and unselected appearances for an icon that’s used in standard system components such as toolbars, tab bars, and buttons. The system updates the visual appearance of the selected state automatically.
+
+In a toolbar, a selected icon receives the app’s accent color.
+
+**Use inclusive images.** Consider how your icons can be understandable and welcoming to everyone. Prefer depicting gender-neutral human figures and avoid images that might be hard to recognize across different cultures or languages. For guidance, see [Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion).
+
+**Include text in your design only when it’s essential for conveying meaning.** For example, using a character in an interface icon that represents text formatting can be the most direct way to communicate the concept. If you need to display individual characters in your icon, be sure to localize them. If you need to suggest a passage of text, design an abstract representation of it, and include a flipped version of the icon to use when the context is right-to-left. For guidance, see [Right to left](https://developer.apple.com/design/human-interface-guidelines/right-to-left).
+
+Create localized versions of an icon that displays individual characters.
+
+Create a flipped version of an icon that suggests reading direction.
+
+**If you create a custom interface icon, use a vector format like PDF or SVG.** The system automatically scales a vector-based interface icon for high-resolution displays, so you don’t need to provide high-resolution versions of it. In contrast, PNG — used for app icons and other images that include effects like shading, textures, and highlighting — doesn’t support scaling, so you have to supply multiple versions for each PNG-based interface icon. Alternatively, you can create a custom SF Symbol and specify a scale that ensures the symbol’s emphasis matches adjacent text. For guidance, see [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+**Provide alternative text labels for custom interface icons.** Alternative text labels — or accessibility descriptions — aren’t visible, but they let VoiceOver audibly describe what’s onscreen, simplifying navigation for people with visual disabilities. For guidance, see [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover).
+
+**Avoid using replicas of Apple hardware products.** Hardware designs tend to change frequently and can make your interface icons and other content appear dated. If you must display Apple hardware, use only the images available in [Apple Design Resources](https://developer.apple.com/design/resources/) or the SF Symbols that represent various Apple products.
+
+## [Standard icons](https://developer.apple.com/design/human-interface-guidelines/icons#Standard-icons)
+
+For icons to represent common actions in [menus](https://developer.apple.com/design/human-interface-guidelines/menus), [toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars), [buttons](https://developer.apple.com/design/human-interface-guidelines/buttons), and other places in interfaces across Apple platforms, you can use these [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols).
+
+### [Editing](https://developer.apple.com/design/human-interface-guidelines/icons#Editing)
+
+Action| Icon| Symbol name
+---|---|---
+Cut| | `scissors`
+Copy| | `document.on.document`
+Paste| | `document.on.clipboard`
+Done| | `checkmark `
+Save
+Cancel| | `xmark`
+Close
+Delete| | `trash`
+Undo| | `arrow.uturn.backward`
+Redo| | `arrow.uturn.forward`
+Compose| | `square.and.pencil`
+Duplicate| | `plus.square.on.square`
+Rename| | `pencil`
+Move to| | `folder`
+Folder
+Attach| | `paperclip`
+Add| | `plus`
+More| | `ellipsis`
+
+### [Selection](https://developer.apple.com/design/human-interface-guidelines/icons#Selection)
+
+Action| Icon| Symbol name
+---|---|---
+Select| | `checkmark.circle`
+Deselect| | `xmark`
+Close
+Delete| | `trash`
+
+### [Text formatting](https://developer.apple.com/design/human-interface-guidelines/icons#Text-formatting)
+
+Action| Icon| Symbol name
+---|---|---
+Superscript| | `textformat.superscript`
+Subscript| | `textformat.subscript`
+Bold| | `bold`
+Italic| | `italic`
+Underline| | `underline`
+Align Left| | `text.alignleft`
+Center| | `text.aligncenter`
+Justified| | `text.justify`
+Align Right| | `text.alignright`
+
+### [Search](https://developer.apple.com/design/human-interface-guidelines/icons#Search)
+
+Action| Icon| Symbol name
+---|---|---
+Search| | `magnifyingglass`
+Find| | `text.page.badge.magnifyingglass`
+Find and Replace
+Find Next
+Find Previous
+Use Selection for Find
+Filter| | `line.3.horizontal.decrease`
+
+### [Sharing and exporting](https://developer.apple.com/design/human-interface-guidelines/icons#Sharing-and-exporting)
+
+Action| Icon| Symbol name
+---|---|---
+Share| | `square.and.arrow.up`
+Export
+Print| | `printer`
+
+### [Users and accounts](https://developer.apple.com/design/human-interface-guidelines/icons#Users-and-accounts)
+
+Action| Icon| Symbol name
+---|---|---
+Account| | `person.crop.circle`
+User
+Profile
+
+### [Ratings](https://developer.apple.com/design/human-interface-guidelines/icons#Ratings)
+
+Action| Icon| Symbol name
+---|---|---
+Dislike| | `hand.thumbsdown`
+Like| | `hand.thumbsup`
+
+### [Layer ordering](https://developer.apple.com/design/human-interface-guidelines/icons#Layer-ordering)
+
+Action| Icon| Symbol name
+---|---|---
+Bring to Front| | `square.3.layers.3d.top.filled`
+Send to Back| | `square.3.layers.3d.bottom.filled`
+Bring Forward| | `square.2.layers.3d.top.filled`
+Send Backward| | `square.2.layers.3d.bottom.filled`
+
+### [Other](https://developer.apple.com/design/human-interface-guidelines/icons#Other)
+
+Action| Icon| Symbol name
+---|---|---
+Alarm| | `alarm`
+Archive| | `archivebox`
+Calendar| | `calendar`
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/icons#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/icons#macOS)
+
+#### [Document icons](https://developer.apple.com/design/human-interface-guidelines/icons#Document-icons)
+
+If your macOS app can use a custom document type, you can create a document icon to represent it. Traditionally, a document icon looks like a piece of paper with its top-right corner folded down. This distinctive appearance helps people distinguish documents from apps and other content, even when icon sizes are small.
+
+If you don’t supply a document icon for a file type you support, macOS creates one for you by compositing your app icon and the file’s extension onto the canvas. For example, Preview uses a system-generated document icon to represent JPG files.
+
+
+
+In some cases, it can make sense to create a set of document icons to represent a range of file types your app handles. For example, Xcode uses custom document icons to help people distinguish projects, AR objects, and Swift code files.
+
+
+
+
+
+
+
+To create a custom document icon, you can supply any combination of background fill, center image, and text. The system layers, positions, and masks these elements as needed and composites them onto the familiar folded-corner icon shape.
+
+Background fill
+
+Center image
+
+Text
+
+macOS composites the elements you supply to produce your custom document icon.
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#macos-apps) provides a template you can use to create a custom background fill and center image for a document icon. As you use this template, follow the guidelines below.
+
+**Design simple images that clearly communicate the document type.** Whether you use a background fill, a center image, or both, prefer uncomplicated shapes and a reduced palette of distinct colors. Your document icon can display as small as 16x16 px, so you want to create designs that remain recognizable at every size.
+
+**Designing a single, expressive image for the background fill can be a great way to help people understand and recognize a document type.** For example, Xcode and TextEdit both use rich background images that don’t include a center image.
+
+
+
+
+
+**Consider reducing complexity in the small versions of your document icon.** Icon details that are clear in large versions can look blurry and be hard to recognize in small versions. For example, to ensure that the grid lines in the custom heart document icon remain clear in intermediate sizes, you might use fewer lines and thicken them by aligning them to the reduced pixel grid. In the 16x16 px size, you might remove the lines altogether.
+
+The 32x32 px icon has fewer grid lines and a thicker EKG line.
+
+The 16x16 px @2x icon retains the EKG line but has no grid lines.
+
+The 16x16 px @1x icon has no EKG line and no grid lines.
+
+**Avoid placing important content in the top-right corner of your background fill.** The system automatically masks your image to fit the document icon shape and draws the white folded corner on top of the fill. Create a set of background images in the sizes listed below.
+
+ * 512x512 px @1x, 1024x1024 px @2x
+
+ * 256x256 px @1x, 512x512 px @2x
+
+ * 128x128 px @1x, 256x256 px @2x
+
+ * 32x32 px @1x, 64x64 px @2x
+
+ * 16x16 px @1x, 32x32 px @2x
+
+
+
+
+**If a familiar object can convey a document’s type or its connection with your app, consider creating a center image that depicts it.** Design a simple, unambiguous image that’s clear and recognizable at every size. The center image measures half the size of the overall document icon canvas. For example, to create a center image for a 32x32 px document icon, use an image canvas that measures 16x16 px. You can provide center images in the following sizes:
+
+ * 256x256 px @1x, 512x512 px @2x
+
+ * 128x128 px @1x, 256x256 px @2x
+
+ * 32x32 px @1x, 64x64 px @2x
+
+ * 16x16 px @1x, 32x32 px @2x
+
+
+
+
+**Define a margin that measures about 10% of the image canvas and keep most of the image within it.** Although parts of the image can extend into this margin for optical alignment, it’s best when the image occupies about 80% of the image canvas. For example, most of the center image in a 256x256 px canvas would fit in an area that measures 205x205 px.
+
+
+
+**Specify a succinct term if it helps people understand your document type.** By default, the system displays a document’s extension at the bottom edge of the document icon, but if the extension is unfamiliar you can supply a more descriptive term. For example, the document icon for a SceneKit scene file uses the term _scene_ instead of the file extension _scn_. The system automatically scales the extension text to fit in the document icon, so be sure to use a term that’s short enough to be legible at small sizes. By default, the system capitalizes every letter in the text.
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/icons#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/icons#Related)
+
+[App icons](https://developer.apple.com/design/human-interface-guidelines/app-icons)
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/icons#Videos)
+
+[ Designing Glyphs ](https://developer.apple.com/videos/play/wwdc2017/823)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/icons#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added a table of SF Symbols that represent common actions.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/images.md b/web-app/public/skills/hig-foundations/references/images.md
new file mode 100644
index 00000000..6b841670
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/images.md
@@ -0,0 +1,176 @@
+---
+title: "Images | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/images
+
+# Images
+
+To make sure your artwork looks great on all devices you support, learn how the system displays content and how to deliver art at the appropriate scale factors.
+
+
+
+## [Resolution](https://developer.apple.com/design/human-interface-guidelines/images#Resolution)
+
+Different devices can display images at different resolutions. For example, a 2D device displays images according to the resolution of its screen.
+
+A _point_ is an abstract unit of measurement that helps visual content remain consistent regardless of how it’s displayed. In 2D platforms, a point maps to a number of pixels that can vary according to the resolution of the display; in visionOS, a point is an angular value that allows visual content to scale according to its distance from the viewer.
+
+When creating bitmap images, you specify a _scale factor_ which determines the resolution of an image. You can visualize scale factor by considering the density of pixels per point in 2D displays of various resolutions. For example, a scale factor of 1 (also called @1x) describes a 1:1 pixel density, where one pixel is equal to one point. High-resolution 2D displays have higher pixel densities, such as 2:1 or 3:1. A 2:1 density (called @2x) has a scale factor of 2, and a 3:1 density (called @3x) has a scale factor of 3. Because of higher pixel densities, high-resolution displays demand images with more pixels.
+
+1x (10x10 px)
+
+2x (20x20 px)
+
+3x (30x30 px)
+
+**Provide high-resolution assets for all bitmap images in your app, for every device you support.** As you add each image to your project’s asset catalog, identify its scale factor by appending “@1x,” “@2x,” or “@3x” to its filename. Use the following values for guidance; for additional scale factors, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout).
+
+Platform| Scale factors
+---|---
+iPadOS, watchOS| @2x
+iOS| @2x and @3x
+visionOS| @2x or higher (see [visionOS](https://developer.apple.com/design/human-interface-guidelines/images#visionOS))
+macOS, tvOS| @1x and @2x
+
+**In general, design images at the lowest resolution and scale them up to create high-resolution assets.** When you use resizable vectorized shapes, you might want to position control points at whole values so that they’re cleanly aligned at 1x. This positioning allows the points to remain cleanly aligned to the raster grid at higher resolutions, because 2x and 3x are multiples of 1x.
+
+## [Formats](https://developer.apple.com/design/human-interface-guidelines/images#Formats)
+
+As you create different types of images, consider the following recommendations.
+
+Image type| Format
+---|---
+Bitmap or raster work| De-interlaced PNG files
+PNG graphics that don’t require full 24-bit color| An 8-bit color palette
+Photos| JPEG files, optimized as necessary, or HEIC files
+Stereo or spatial photos| Stereo HEIC
+Flat icons, interface icons, and other flat artwork that requires high-resolution scaling| PDF or SVG files
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/images#Best-practices)
+
+**Include a color profile with each image.** Color profiles help ensure that your app’s colors appear as intended on different displays. For guidance, see [Color management](https://developer.apple.com/design/human-interface-guidelines/color#Color-management).
+
+**Always test images on a range of actual devices.** An image that looks great at design time may appear pixelated, stretched, or compressed when viewed on various devices.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/images#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or macOS._
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/images#tvOS)
+
+Layered images are at the heart of the Apple TV user experience. The system combines layered images, transparency, scaling, and motion to produce a sense of realism and vigor that evokes a personal connection as people interact with onscreen content.
+
+#### [Parallax effect](https://developer.apple.com/design/human-interface-guidelines/images#Parallax-effect)
+
+ _Parallax_ is a subtle visual effect the system uses to convey depth and dynamism when an element is in focus. As an element comes into focus, the system elevates it to the foreground, gently swaying it while applying illumination that makes the element’s surface appear to shine. After a period of inactivity, out-of-focus content dims and the focused element expands.
+
+Layered images are required to support the parallax effect.
+
+Video with custom controls.
+
+Content description: An animation of a tvOS app icon moving to show the parallax effect.
+
+Play
+
+#### [Layered images](https://developer.apple.com/design/human-interface-guidelines/images#Layered-images)
+
+A _layered image_ consists of two to five distinct layers that come together to form a single image. The separation between layers, along with use of transparency, creates a feeling of depth. As someone interacts with an image, layers closer to the surface elevate and scale, overlapping lower layers farther back and producing a 3D effect.
+
+Important
+
+Your tvOS [app icon](https://developer.apple.com/design/human-interface-guidelines/app-icons#tvOS) must use a layered image. For other focusable images in your app, including [Top Shelf](https://developer.apple.com/design/human-interface-guidelines/top-shelf) images, layered images are strongly encouraged, but optional.
+
+You can embed layered images in your app or retrieve them from a content server at runtime. For guidance on adding layered images to your app, see the [Parallax Previewer User Guide](https://help.apple.com/itc/parallaxpreviewer/).
+
+Developer note
+
+If your app retrieves layered images from a content server at runtime, you must provide runtime layered images (`.lcr`). You can generate them from LSR files or Photoshop files using the `layerutil` command-line tool that Xcode provides. Runtime layered images are intended to be downloaded — don’t embed them in your app.
+
+**Use standard interface elements to display layered images.** If you use standard views and system-provided focus APIs — such as [`FocusState`](https://developer.apple.com/documentation/SwiftUI/FocusState) — layered images automatically get the parallax treatment when people bring them into focus.
+
+**Identify logical foreground, middle, and background elements.** In foreground layers, display prominent elements like a character in a game, or text on an album cover or movie poster. Middle layers are perfect for secondary content and effects like shadows. Background layers are opaque backdrops that showcase the foreground and middle layers without upstaging them.
+
+**Generally, keep text in the foreground.** Unless you want to obscure text, bring it to the foreground layer for clarity.
+
+**Keep the background layer opaque.** Using varying levels of opacity to let content shine through higher layers is fine, but your background layer must be opaque — you’ll get an error if it’s not. An opaque background layer ensures your artwork looks great with parallax, drop shadows, and system backgrounds.
+
+**Keep layering simple and subtle.** Parallax is designed to be almost unnoticeable. Excessive 3D effects can appear unrealistic and jarring. Keep depth simple to bring your content to life and add delight.
+
+**Leave a safe zone around the foreground layers of your image.** When focused, content on some layers may be cropped as the layered image scales and moves. To ensure that essential content is always visible, keep it within a safe zone. For guidance, see [App icons](https://developer.apple.com/design/human-interface-guidelines/app-icons).
+
+**Always preview layered images.** To ensure your layered images look great on Apple TV, preview them throughout your design process using Xcode, the Parallax Previewer app for macOS, or the Parallax Exporter plug-in for Adobe Photoshop. Pay special attention as scaling and clipping occur, and readjust your images as needed to keep important content safe. After your layered images are final, preview them on an actual TV for the most accurate representation of what people will see. To download Parallax Previewer and Parallax Exporter, see [Resources](https://developer.apple.com/design/resources/#parallax-previewer).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/images#visionOS)
+
+In visionOS, people can view images at a much larger range of sizes than in any other platform, and the system dynamically scales the image resolution to match the current size. Because you can position images at specific angles within someone’s surroundings, image pixels may not line up 1:1 with screen pixels.
+
+**Create a layered app icon.** App icons in visionOS are composed of two to three layers that provide the appearance of depth by moving at subtly different rates when the icon is in focus. For guidance, see [Layer design](https://developer.apple.com/design/human-interface-guidelines/app-icons#Layer-design).
+
+**Prefer vector-based art for 2D images.** Avoid bitmap content because it might not look good when the system scales it up. If you use Core Animation layers, see [Drawing sharp layer-based content in visionOS](https://developer.apple.com/documentation/visionOS/drawing-sharp-layer-based-content) for developer guidance.
+
+**If you need to use rasterized images, balance quality with performance as you choose a resolution.** Although a @2x image looks fine at common viewing distances, its fixed resolution means that the system doesn’t dynamically scale it and it might not look sharp from close up. To help a rasterized image look sharp when people view it from a wide range of distances, you can use a higher resolution, but each increase in resolution results in a larger file size and may impact your app’s runtime performance, especially for resolutions over @6x. If you use images that have resolutions higher than @2x, be sure to also apply high-quality image filtering to help balance quality and performance (for developer guidance, see [`filters`](https://developer.apple.com/documentation/QuartzCore/CALayer/filters)).
+
+#### [Spatial photos and spatial scenes](https://developer.apple.com/design/human-interface-guidelines/images#Spatial-photos-and-spatial-scenes)
+
+In addition to 2D and stereoscopic images, visionOS apps and games can use RealityKit to display spatial photos and spatial scenes. A _spatial photo_ is a stereoscopic photo with additional spatial metadata, as captured on iPhone 15 Pro or later, Apple Vision Pro, or other compatible camera. A _spatial scene_ is a 3D image generated from a 2D image to add a parallax effect that responds to head movement. For developer guidance, see [`ImagePresentationComponent`](https://developer.apple.com/documentation/RealityKit/ImagePresentationComponent).
+
+**Make sure spatial photos render correctly in your app.** Use the stereo High-Efficiency Image Codec (HEIC) format to display a spatial photo in your app. When you add spatial metadata to a stereo HEIC, visionOS recognizes the photo as spatial and includes visual treatments that help minimize common causes of stereo-viewing discomfort.
+
+**Prefer the feathered glass background effect to display text over spatial photos.** If you need to place text over a spatial photo in your app or game, use the feathered glass background effect. The effect adds contrast to make the text readable, and it blurs out detail to help reduce visual discomfort when people view text over spatial photos. For developer guidance, see [`GlassBackgroundEffect`](https://developer.apple.com/documentation/SwiftUI/GlassBackgroundEffect).
+
+**Take visual comfort into consideration when you make spatial photos from existing 2D content.** When adjusting the spatial metadata of a photo for your app or game, consider how you want people to view your content. Metadata like disparity adjustment can alter how people perceive the 3D scene, and can cause visual discomfort from certain viewing positions. For developer guidance, see [Creating spatial photos and videos with spatial metadata](https://developer.apple.com/documentation/ImageIO/Creating-spatial-photos-and-videos-with-spatial-metadata).
+
+**Display spatial photos and spatial scenes in standalone views.** Avoid displaying spatial photos inline with other content, as this can cause visual discomfort. Instead, showcase spatial photos or spatial scenes in a separate view, like a sheet or window. If you must display stereoscopic images inline, provide generous spacing between the image and any inline content to help people’s eyes adjust to the depth changes.
+
+**Use spatial scenes in your app for specific moments.** Each spatial scene can take up to several seconds to generate from an existing image. Design experiences with this limitation in mind. For instance, the Photos app offers an explicit action to create a spatial scene while immersed in a single photo. Avoid displaying too many spatial scenes at once. Instead, use scroll views, pagination, or explicit actions to move to new photos and keep the visual information hierarchy simple.
+
+**When displaying immersively, prefer minimal UI.** For example, the Spatial Gallery app displays a single piece of content with a small caption and a single Back button, relying on swipe gestures to navigate between items.
+
+**Prefer displaying larger spatial scenes that you center in someone’s field of view.** When people view a spatial scene, they may move their head laterally to view the parallax effect. Smaller spatial scenes provide less of a parallax effect and may not be as impactful to viewers.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/images#watchOS)
+
+**In general, avoid transparency to keep image files small.** If you always composite an image on the same solid background color, it’s more efficient to include the background in the image. However, transparency is necessary in complication images, menu icons, and other interface icons that serve as template images, because the system uses it to determine where to apply color.
+
+**Use autoscaling PDFs to let you provide a single asset for all screen sizes.** Design your image for the 40mm and 42mm screens at 2x. When you load the PDF, WatchKit automatically scales the image based on the device’s screen size, using the values shown below:
+
+Screen size| Image scale
+---|---
+38mm| 90%
+40mm| 100%
+41mm| 106%
+42mm| 100%
+44mm| 110%
+45mm| 119%
+49mm| 119%
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/images#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/images#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/images#Developer-documentation)
+
+[Drawing sharp layer-based content in visionOS](https://developer.apple.com/documentation/visionOS/drawing-sharp-layer-based-content) — visionOS
+
+[Images](https://developer.apple.com/documentation/SwiftUI/Images) — SwiftUI
+
+[`UIImageView`](https://developer.apple.com/documentation/UIKit/UIImageView) — UIKit
+
+[`NSImageView`](https://developer.apple.com/documentation/AppKit/NSImageView) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/images#Videos)
+
+[ Support HDR images in your app ](https://developer.apple.com/videos/play/wwdc2023/10181)
+
+[ Get Started with Display P3 ](https://developer.apple.com/videos/play/wwdc2017/821)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/images#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Added guidance for spatial photos and spatial scenes in visionOS.
+December 5, 2023| Clarified guidance on choosing a resolution for a rasterized image in a visionOS app.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Added specifications for Apple Watch Ultra.
+
diff --git a/web-app/public/skills/hig-foundations/references/immersive-experiences.md b/web-app/public/skills/hig-foundations/references/immersive-experiences.md
new file mode 100644
index 00000000..580f8c47
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/immersive-experiences.md
@@ -0,0 +1,174 @@
+---
+title: "Immersive experiences | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/immersive-experiences
+
+# Immersive experiences
+
+In visionOS, you can design apps and games that extend beyond windows and volumes, immersing people in your content.
+
+
+
+You can choose whether your visionOS app or game launches in the Shared Space or in a Full Space. In the _Shared Space_ , your software runs alongside other experiences, and people can switch between them much as they do on a Mac; in a _Full Space_ , your app or game runs alone, hiding other experiences and helping people immerse themselves in your content. Apps and games can support different types of immersion, and can transition fluidly between the Shared Space and a Full Space at any time.
+
+## [Immersion and passthrough](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Immersion-and-passthrough)
+
+In visionOS, people use passthrough to see their physical surroundings. _Passthrough_ provides real-time video from the device’s external cameras, helping people feel comfortable and connected to their physical context.
+
+People can also use the [Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown) at any time to manage app or game content or adjust passthrough. For example, people can press and hold the Digital Crown to recenter content in their field of view or double-click it to briefly hide all content and show passthrough for a clear view of their surroundings.
+
+The system also helps people remain comfortable by automatically changing the opacity of content in certain situations. For example, if someone gets too close to a physical object in `mixed` immersion, the content in front of them dims briefly so they can see their immediate physical surroundings more clearly. In more immersive experiences — such as in the `progressive` and `full` styles described below — the system defines a boundary that extends about 1.5 meters from the initial position of the wearer’s head. As their head gets close to this boundary, the entire experience begins to fade and passthrough increases. When their head moves beyond this boundary, the immersive visuals are replaced in space by the app’s icon, and are restored when the wearer returns to their original location or recenters their view using the Digital Crown.
+
+### [Immersion styles](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Immersion-styles)
+
+When your app or game transitions to a Full Space, the system hides other apps so people can focus on yours. In a Full Space, you can display 3D content that isn’t bound by a window, in addition to content in standard windows and volumes. For developer guidance, see [`automatic`](https://developer.apple.com/documentation/SwiftUI/ImmersionStyle/automatic).
+
+visionOS offers several ways to immerse people in your content in the Shared Space as well as when you transition to a Full Space. For example, you can:
+
+ * **Use dimmed passthrough to bring attention to your content.** You can subtly dim or tint passthrough and other visible content to bring attention to your app in the Shared Space without hiding other apps and games, or create a more focused experience in a Full Space. While passthrough is tinted black by default, you can apply a custom tint color to create a dynamic experience in your app. For developer guidance, see [`SurroundingsEffect`](https://developer.apple.com/documentation/SwiftUI/SurroundingsEffect).
+
+
+
+
+ * Without dimmed passthrough
+ * With dimmed passthrough
+
+
+
+
+
+
+
+ * **Create unbounded 3D experiences.** Use the `mixed` immersion style in a Full Space to blend your content with passthrough. When your app or game runs in a Full Space, you can request access to information about nearby physical objects and room layout, helping you display virtual content in a person’s surroundings. The `mixed` immersion style doesn’t define a boundary. Instead, when a person gets too close to a physical object, the system automatically makes nearby content semi-opaque to help them remain aware of their surroundings. For developer guidance, see [`mixed`](https://developer.apple.com/documentation/SwiftUI/ImmersionStyle/mixed) and [ARKit](https://developer.apple.com/documentation/ARKit).
+
+ * **Use`progressive` immersion to blend your custom environment with a person’s surroundings.** You can use the `progressive` style in a Full Space to display a custom environment that partially replaces passthrough. You can also define a specific range of immersion that works best with your app or game, and display content in portrait or landscape orientation. While in your immersive experience, people can use the Digital Crown to adjust the amount of immersion within either the default range of 120- to 360-degrees or a custom range, if you specify one. The system automatically defines an approximately 1.5-meter boundary when an experience transitions to the `progressive` style. For developer guidance, see [`progressive`](https://developer.apple.com/documentation/SwiftUI/ImmersionStyle/progressive).
+
+
+
+
+Video with custom controls.
+
+Content description: A recording of a fully immersive experience in which a video player window appears on top of an Environment. As the viewer adjusts the Digital Crown, passthrough increases to reveal more of the person's physical surroundings.
+
+Play
+
+ * **Use`full` immersion to create a fully immersive experience.** You can use the `full` style in a Full Space to display a 360-degree custom environment that completely replaces passthrough and transports people to a new place. As with the `progressive` style, the system defines an approximately 1.5-meter boundary when a fully immersive experience starts. For developer guidance, see [`full`](https://developer.apple.com/documentation/SwiftUI/ImmersionStyle/full).
+
+
+
+
+ * Full Space (Mixed)
+ * Full Space (Progressive)
+ * Full Space (Immersive)
+
+
+
+Mixed immersion style in a Full Space blending in-app objects with real-world surroundings
+
+Progressive immersion style in a Full Space blending the app’s custom environment with real-world surroundings
+
+Full immersion style in a Full Space showing a 360-degree custom environment
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Best-practices)
+
+**Offer multiple ways to use your app or game.** In addition to giving people the freedom to choose their experiences, it’s essential to design your software to support the accessibility features people use to personalize the ways they interact with their devices. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Prefer launching your app or game in the Shared Space or using the`mixed` immersion style.** Launching in the Shared Space lets people reference your app or game while using other running software, and enables seamless switching between them. If your app or game provides a fully immersive or `progressive` style experience, launching in the `mixed` immersion style or with a window-based experience in the Shared Space gives people more control, letting them choose when to increase immersion.
+
+**Reserve immersion for meaningful moments and content.** Not every task benefits from immersion, and not every immersive task needs to be fully immersive. Although people sometimes want to enter a different world, they often want to stay grounded in their surroundings while they’re using your app or game, and they can appreciate being able to use other software and system features at the same time. Instead of assuming that your app or game needs to be fully immersive most of the time, design ways for people to immerse themselves in the individual tasks and content that make your experience unique. For example, people can browse their albums in Photos using a familiar app window in the Shared Space, but when they want to examine a single photo, they can temporarily transition to a more immersive experience in a Full Space where they can expand the photo and appreciate its details.
+
+**Help people engage with key moments in your app or game, regardless of the level of immersion.** Cues like dimming, tinting, [motion](https://developer.apple.com/design/human-interface-guidelines/motion), [scale](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Scale), and [Spatial Audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio#visionOS) can help draw people’s attention to a specific area of content, whether it’s in a window in the Shared Space or in a completely immersive experience in a Full Space. Start with subtle cues that gently guide people’s attention, strengthening the cues only when there’s a good reason to do so.
+
+**Prefer subtle tint colors for passthrough.** In visionOS 2 and later, you can tint passthrough to help a person’s surroundings visually coordinate with your content, while also making their hands look like they belong in your experience. Avoid bright or dramatic tints that can distract people and diminish the sense of immersion. For developer guidance, see [`SurroundingsEffect`](https://developer.apple.com/documentation/SwiftUI/SurroundingsEffect).
+
+## [Promoting comfort](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Promoting-comfort)
+
+**Be mindful of people’s visual comfort.** For example, although you can place 3D content anywhere while your app or game is running in a Full Space, prefer placing it within people’s [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view). Also, make sure you display motion in comfortable ways while your software runs in a Full Space to avoid causing distraction, confusion, or discomfort. For guidance, see [Motion](https://developer.apple.com/design/human-interface-guidelines/motion).
+
+**Choose a style of immersion that supports the movements people might make while they’re in your app or game.** It’s essential to choose the right style for your immersive experience because it allows the system to respond appropriately when people move. Although people can make minor physical movements while in an immersive experience — such as shifting their weight, turning around, or switching between sitting and standing — making excessive movements can cause the system to interrupt some experiences. In particular, avoid using the `progressive` or `full` immersion styles or transition back to the `mixed` immersion style if you think people might need to move beyond the 1.5-meter boundary.
+
+**Avoid encouraging people to move while they’re in a progressive or fully immersive experience.** Some people may not want to move, or are unable to move because of a disability or their physical surroundings. Design ways for people to interact with content without moving. For example, let people bring a virtual object closer to them instead of expecting them to move closer to the object.
+
+**If you use the`mixed` immersion style, avoid obscuring passthrough too much.** People use passthrough to help them understand and navigate their physical surroundings, so it’s important to avoid displaying virtual objects that block too much of their view. If your app or game displays virtual objects that could substantially obscure passthrough, use the `full` or `progressive` immersion styles instead of `mixed`.
+
+**Adopt ARKit if you want to blend custom content with someone’s surroundings.** For example, you might want to integrate virtual content into someone’s surroundings or use the wearer’s hand positions to inform your experience. If you need access to these types of sensitive data, you must request people’s permission. For guidance, see [Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy); for developer guidance, see [`SceneReconstructionProvider`](https://developer.apple.com/documentation/ARKit/SceneReconstructionProvider).
+
+## [Transitioning between immersive styles](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Transitioning-between-immersive-styles)
+
+**Design smooth, predictable transitions when changing immersion.** Help people prepare for different experiences by providing gentle transitions that let people visually track changes. Avoid sudden, jarring transitions that might be disorienting or uncomfortable. For developer guidance, see [`CoordinateSpaceProtocol`](https://developer.apple.com/documentation/SwiftUI/CoordinateSpaceProtocol).
+
+**Let people choose when to enter or exit a more immersive experience.** It can be disorienting for someone to suddenly enter a more immersive experience when they’re not expecting it. Instead, provide a clear action to enter or exit immersion so people can decide when to be more immersed in your content, and when to leave. For example, Keynote provides a prominent Exit button in its fully immersive Rehearsal environment to help people return to the slide-viewing window. Avoid requiring people to use system controls to reduce immersion in your experience.
+
+**Indicate the purpose of an exit control.** Make sure your button clarifies whether it returns people to a previous, less immersive context or quits an experience altogether. If exiting your immersive experience also quits your app or game, consider providing controls that let people pause or return to a place where they can save their progress before quitting.
+
+## [Displaying virtual hands](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Displaying-virtual-hands)
+
+When your immersive app or game transitions to a Full Space, it can ask permission to hide a person’s hands and instead show virtual hands that represent them.
+
+**Prefer virtual hands that match familiar characteristics.** For example, match the positions and gestures of the viewer’s hands so they can continue to interact with your app or game in ways that feel natural. Hands that work in familiar ways help people stay immersed in the experience when in fully virtual worlds.
+
+**Use caution if you create virtual hands that are larger than the viewer’s hands.** Virtual hands that are significantly bigger than human hands can prevent people from seeing the content they’re interested in and can make interactions feel clumsy. Also, large virtual hands can seem out of proportion with the space, appearing to be too close to the viewer’s face.
+
+**If there’s an interruption in hand-tracking data, fade out virtual hands and reveal the viewer’s own hands.** Don’t let the virtual hands become unresponsive and appear frozen. When hand-tracking data returns, fade the virtual hands back in.
+
+## [Creating an environment](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Creating-an-environment)
+
+When your app or game transitions to a Full Space, you can replace passthrough with a custom environment that partially or completely surrounds a person, transporting them to a new place. The following guidelines can help you design a beautiful environment that people appreciate.
+
+**Minimize distracting content.** To help immerse people in a primary task like watching a video, avoid displaying a lot of movement or high-contrast details in your environment. Alternatively, when you want to draw people’s attention to certain areas of your environment, consider techniques like using the highest quality textures and shapes in the important area while using lower quality assets and dimming in less important areas.
+
+**Help people distinguish interactive objects in your environment.** People often use an object’s proximity to help them decide if they can interact with it. For example, when you place a 3D object far away from people, they often don’t try to touch or move toward it, but when you place a 3D object close to people, they’re more likely to try interacting with it.
+
+**Keep animation subtle.** Small, gentle movements, like clouds drifting or transforming, can enrich your custom environment without distracting people or making them uncomfortable. Always avoid displaying too much movement near the edges of a person’s field of view. For guidance, see [Motion](https://developer.apple.com/design/human-interface-guidelines/motion).
+
+**Create an expansive environment, regardless of the place it depicts.** A small, restrictive environment can make people feel uncomfortable and even claustrophobic.
+
+**Use Spatial Audio to create atmosphere.** In visionOS, you use Spatial Audio to play sound that people can perceive as coming from specific locations in space, not just from speakers (for guidance, see [Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio)). As you design a soundscape that enhances your custom environment, keep the experience fresh and captivating by avoiding too much repetition or looping. If people can play other audio while they’re in your environment — for example, while watching a movie — be sure to lower the volume of the soundscape or stop it completely.
+
+**In general, avoid using a flat 360-degree image to create your environment.** A 360-degree image doesn’t tend to give people a sense of scale when they view it in an environment, so it can reduce the immersiveness of the experience. Prefer creating object meshes that include lighting, and use shaders to implement subtle animations like the movements of clouds or leaves or the reflections of objects.
+
+**Help people feel grounded.** Always provide a ground plane mesh so people don’t feel like they’re floating. If you must use a flat 360-degree image in your environment, adding a ground plane mesh can help it feel more realistic.
+
+**Minimize asset redundancy.** Using the same assets or models too frequently tends to make an environment feel less realistic.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Related)
+
+[Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout)
+
+[Motion](https://developer.apple.com/design/human-interface-guidelines/motion)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Developer-documentation)
+
+[Creating fully immersive experiences in your app](https://developer.apple.com/documentation/visionOS/creating-fully-immersive-experiences) — visionOS
+
+[Incorporating real-world surroundings in an immersive experience](https://developer.apple.com/documentation/visionOS/incorporating-real-world-surroundings-in-an-immersive-experience) — visionOS
+
+[`ImmersionStyle`](https://developer.apple.com/documentation/SwiftUI/ImmersionStyle) — visionOS
+
+[Immersive spaces](https://developer.apple.com/documentation/SwiftUI/Immersive-spaces) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Videos)
+
+[ Principles of spatial design ](https://developer.apple.com/videos/play/wwdc2023/10072)
+
+[ Design spatial SharePlay experiences ](https://developer.apple.com/videos/play/wwdc2023/10075)
+
+[ Create custom environments for your immersive apps in visionOS ](https://developer.apple.com/videos/play/wwdc2024/10087)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Clarified guidance and noted the availability of portrait-oriented progressive immersion.
+November 19, 2024| Refined immersion style guidance and added artwork.
+June 10, 2024| Added guidance for tinting passthrough and specifying initial, minimum, and maximum immersion levels.
+May 7, 2024| Added guidance for creating an environment.
+February 2, 2024| Clarified guidance for choosing an immersion style that matches the experience your app provides.
+October 24, 2023| Updated artwork.
+June 21, 2023| New page.
+
diff --git a/web-app/public/skills/hig-foundations/references/inclusion.md b/web-app/public/skills/hig-foundations/references/inclusion.md
new file mode 100644
index 00000000..7946182b
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/inclusion.md
@@ -0,0 +1,189 @@
+---
+title: "Inclusion | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/inclusion
+
+# Inclusion
+
+Inclusive apps and games put people first by prioritizing respectful communication and presenting content and functionality in ways that everyone can access and understand.
+
+
+
+To help you design an inclusive app or game, consider the following goals as you review the words and images you use and the experiences you offer.
+
+As with all design, designing an inclusive app is an iterative process that takes time to get right. Throughout the process, be prepared to examine your assumptions about how other people think and feel and be open to evolving knowledge and understanding.
+
+## [Inclusive by design](https://developer.apple.com/design/human-interface-guidelines/inclusion#Inclusive-by-design)
+
+Simple, intuitive experiences are at the core of well-designed apps and games. To design an intuitive experience, you start by investigating people’s goals and perspectives so you can present content that resonates with them.
+
+Empathy is an important tool in this investigation because it helps you understand how people with different perspectives might respond to the content and experiences you create. For example, you might discover that from some perspectives a word or image is incomprehensible or has a meaning you don’t intend.
+
+Although each person’s perspective comprises a unique intersection of human qualities that’s both distinct and dynamic, all perspectives arise from human characteristics and experiences that everyone shares, including:
+
+ * Age
+
+ * Gender and gender identity
+
+ * Race and ethnicity
+
+ * Sexuality
+
+ * Physical attributes
+
+ * Cognitive attributes
+
+ * Permanent, temporary, and situational disabilities
+
+ * Language and culture
+
+ * Religion
+
+ * Education
+
+ * Political or philosophical opinions
+
+ * Social and economic context
+
+
+
+
+As you examine your app or game through different perspectives, avoid framing the work as merely a search for content that might give offense. Although no design should contain offensive material or experiences, an inoffensive app or game isn’t necessarily an inclusive one. Focusing on inclusion can help you avoid potentially offensive content while also helping you create a welcoming experience that everyone can enjoy.
+
+## [Welcoming language](https://developer.apple.com/design/human-interface-guidelines/inclusion#Welcoming-language)
+
+Using plain, inclusive language welcomes everyone and helps them understand your app or game. Carefully review the writing in your experience to make sure that your tone and words don’t exclude people. Here are a few tips for writing text — also known as _copy_ — that’s direct, easy to understand, and inclusive.
+
+**Consider the tone of your copy from different perspectives.** The style of your writing communicates almost as much as the words you use. Although different apps use different communication styles, make sure the tone you use doesn’t send messages you don’t intend. For example, an academic tone can make an app or game seem like it welcomes only high levels of education. As you seek the style that’s right for your experience, be clear, direct, and respectful.
+
+**Pay attention to how you refer to people.** It typically works well to use _you_ and _your_ to address people directly. Referring to people indirectly as _the user_ or _the player_ can make your experience feel distant and unwelcoming. Also, consider reserving words like _we_ and _our_ to represent your software or company; otherwise, these terms can suggest a personal relationship with people that might be interpreted as insulting or condescending.
+
+**Avoid using specialized or technical terms without defining them.** Using specialized or technical terms can make your writing more succinct, but doing so excludes people who don’t know what the terms mean. If you must use such terms, be sure to define them first and make the definitions easy for people to look up. Even when people know the definition of a specialized or technical term in a sentence, the sentence is easier to read — and translate — when it uses plain language instead.
+
+**Replace colloquial expressions with plain language.** Colloquial expressions are often culture-specific and can be difficult to translate. Worse, some colloquial phrases have exclusionary meanings you might not know. For example, the phrases _peanut gallery_ and _grandfathered in_ both arose from oppressive contexts and continue to exclude people. Even when a colloquial phrase doesn’t have an exclusionary meaning, it can still exclude everyone who doesn’t understand it.
+
+**Consider carefully before including humor.** Humor is highly subjective and — similar to colloquial expressions — difficult to translate from one culture to another. Including humor in your experience risks confusing people who donʼt understand it, irritating people who tire of repeatedly encountering it, and insulting people who interpret it differently. For additional writing guidance, see [Writing inclusively](https://help.apple.com/applestyleguide/#/apdcb2a65d68).
+
+## [Being approachable](https://developer.apple.com/design/human-interface-guidelines/inclusion#Being-approachable)
+
+An approachable app or game doesn’t require people to have particular skills or knowledge before they can use it, and it gives people a clear path toward deepening their understanding over time. Here are two ways to help make an experience approachable.
+
+ * Present a clear, straightforward interface. To help you design a simple interface that fits in with other experiences on each platform, see [Designing for iOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios), [Designing for iPadOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados), [Designing for macOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos), [Designing for tvOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos), [Designing for visionOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos), [Designing for watchOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos), and [Designing for games](https://developer.apple.com/design/human-interface-guidelines/designing-for-games).
+
+ * Build in ways to learn how to use your app or game. Consider designing an onboarding flow that helps people who are new to your experience take a step-by-step approach while letting others skip straight to the content they want. For guidance, see [Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding).
+
+
+
+
+## [Gender identity](https://developer.apple.com/design/human-interface-guidelines/inclusion#Gender-identity)
+
+Throughout history, cultures around the world have recognized a spectrum of self-identity and expression that expands beyond the binary variants of woman and man.
+
+You can help everyone feel welcome in your app or game by avoiding unnecessary references to specific genders. For example, a recipe-sharing app that uses copy like “You can let a subscriber post his or her recipes to your shared folder” could avoid unnecessary gender references by using an alternative like “Subscribers can post recipes to your shared folder.” In addition to using the gender-neutral noun “subscribers,” the revised copy avoids the unnecessary singular pronouns “his” and “her,” helping the sentence remain inclusive when it’s localized for languages that use gendered pronouns.
+
+In addition, you can often avoid referencing a specific gender in an avatar, emoji, glyph, or game character. To welcome everyone to your app or game, prefer giving people the tools they need to customize such items as they choose.
+
+If you need to depict a generic person or people, use a nongendered human image to reinforce the message that _generic person_ means _human_ , not _man_ or _woman_. SF Symbols provides many nongendered glyphs you can use, such as the figure and person symbols shown here:
+
+person.crop.circle
+
+person.3.fill
+
+figure.wave
+
+Most apps and games don’t need to know a person’s gender, but if you require this information — such as for health or legal reasons — consider providing inclusive options, such as _nonbinary_ , _self-identify_ , and _decline to state_. In this situation, you could also let people specify the pronouns they use so you can address them properly when necessary.
+
+## [People and settings](https://developer.apple.com/design/human-interface-guidelines/inclusion#People-and-settings)
+
+Portraying human diversity is one of the most noticeable ways your app or game can welcome everyone. When people recognize others like themselves within an experience and its related materials, they’re less likely to feel excluded and can be more likely to think they’ll benefit from it.
+
+As you create copy and images that represent people, portray a range of human characteristics and activities. For example, a fitness app could feature exercise moves demonstrated by people with different racial backgrounds, body types, ages, and physical capabilities. If you need to depict occupations or behaviors, avoid stereotypical representations, such as showing only male doctors, female nurses, or heroes and villains that may perpetuate real-world racial or gender stereotypes.
+
+Also review the settings and objects you show. For example, showing high levels of affluence might make sense in some scenarios, but in other cases it can be unwelcoming and make an experience seem out of touch. When it makes sense in your app or game, prefer showing places, homes, activities, and items that are familiar and relatable to most people.
+
+## [Avoiding stereotypes](https://developer.apple.com/design/human-interface-guidelines/inclusion#Avoiding-stereotypes)
+
+Everyone holds biases and stereotypes — often unconsciously — and it can be challenging to discover how they affect your thoughts. A goal of inclusive design is to become aware of your biases and generalizations so you can recognize where they might influence your design decisions.
+
+For example, consider an app that helps people manage account access for various family members. If this app uses a stereotypical definition of _family_ — such as a woman, a man, and their biological children — it’s likely to communicate this perspective in its copy and images. Because the app assumes that people’s families fit this narrow definition, it excludes everyone whose family is different.
+
+Although the assumption made in the account-access app might seem like an obvious mistake, it’s important to realize that not all assumptions are so easy to spot. For example, consider an app or game that requires people to choose security questions they can answer for future identity confirmation, such as:
+
+ * What was your favorite subject in college?
+
+ * What was the make of your first car?
+
+ * How did you feel when you first saw a rainbow?
+
+
+
+
+From some perspectives these questions refer to commonplace events, but all are based on experiences that not everyone has. Using a context-specific experience to communicate something is useless for everyone who doesn’t share that context and effectively excludes them. To create alternatives to the culture- and capability-specific questions above, you might reference more universal human experiences like:
+
+ * What’s your favorite activity?
+
+ * What was the name of your first friend?
+
+ * What quality describes you best?
+
+
+
+
+Basing design decisions on stereotypes or assumptions inevitably leads to exclusion because generalizations can’t reflect the diversity of human perspectives. Avoiding assumptions and instead concentrating on inclusion can help you craft experiences that benefit everyone.
+
+## [Accessibility](https://developer.apple.com/design/human-interface-guidelines/inclusion#Accessibility)
+
+An inclusive app or game is accessible to everyone. People rely on Apple’s accessibility features — such as VoiceOver, Display Accommodations, closed captioning, Switch Control, and Speak Screen — to customize their devices for their individual needs, so it’s essential to support these features.
+
+It’s also essential to avoid assuming that any disability might prevent someone from wanting to enjoy the experience your software provides. Making an assumption like this can result in designs that limit the potential audience for your app or game. In contrast, when you make each experience accessible, you give everyone the opportunity to benefit from your app or game in ways that work for them.
+
+To help you design an app or game that everyone can enjoy, remember that:
+
+ * Each disability is a spectrum. For example, visual disabilities range from low vision to complete blindness, and include things like color blindness, blurry vision, light sensitivity, and peripheral vision loss.
+
+ * Everyone can experience disabilities. In addition to disabilities that most people experience as they age, there are _temporary disabilities_ — like short-term hearing loss due to an infection — and _situational disabilities_ — like being unable to hear while on a noisy train — that can affect everyone at various times.
+
+
+
+
+As you design content that welcomes people of all abilities, consider the following tips.
+
+**Avoid images and language that exclude people with disabilities.** For example, include people with disabilities when you represent a variety of people, and avoid language that uses a disability to express a negative quality.
+
+**Take a people-first approach when writing about people with disabilities.** For example, you could describe an individual’s accomplishments and goals before mentioning a disability they may have. If you’re writing about a specific person or community, find out how they self-identify; for more guidance, see [Writing about disability](https://help.apple.com/applestyleguide/#/apd49cbb2b06).
+
+**Prioritize simplicity and perceivability.** Prefer familiar, consistent interactions that make tasks simple to perform, and ensure that everyone can perceive your content, whether they use sight, hearing, or touch.
+
+To learn more about making your app or game accessible, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+## [Languages](https://developer.apple.com/design/human-interface-guidelines/inclusion#Languages)
+
+People expect to customize their device by choosing a language for text and a region for formatting values like date, time, and money. To welcome a global audience, first prepare your software to handle languages and regions other than your own — a process called _internationalization_ — and provide translated text and resources for specific locales. For an overview of internationalization, see [Expanding your app to new markets](https://developer.apple.com/localization/); for developer guidance on localization, see [Localization](https://developer.apple.com/documentation/Xcode/localization).
+
+Creating an inclusive experience can also help you prepare for localization. For example, using plain language, avoiding unnecessary gender references, representing a variety of people, and avoiding stereotypes and culture-specific content, can put you in a good position to create versions of your software localized into more languages. Using [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) for the glyphs in your app or game can also help streamline localization. In addition to providing many language-specific glyphs, SF Symbols includes glyphs you can use in both left-to-right and right-to-left contexts; for guidance, see [Right to left](https://developer.apple.com/design/human-interface-guidelines/right-to-left).
+
+As you localize your app or game and related content, also be aware of the ways you use color. Colors often have strong culture-specific meanings, so it’s essential to discover how people respond to specific colors in each locale you support. In some places, for example, white is associated with death or grief, whereas in other places, it’s associated with purity or peace. If you use color as a way to communicate, make sure your color choices communicate the same thing in each version of your software.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/inclusion#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/inclusion#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/inclusion#Related)
+
+[Writing inclusively](https://help.apple.com/applestyleguide/#/apdcb2a65d68)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/inclusion#Developer-documentation)
+
+[Localization](https://developer.apple.com/documentation/Xcode/localization) — Xcode
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/inclusion#Videos)
+
+[ Principles of inclusive app design ](https://developer.apple.com/videos/play/wwdc2025/316)
+
+[ The practice of inclusive design ](https://developer.apple.com/videos/play/wwdc2021/10275)
+
+[ The process of inclusive design ](https://developer.apple.com/videos/play/wwdc2021/10304)
+
diff --git a/web-app/public/skills/hig-foundations/references/layout.md b/web-app/public/skills/hig-foundations/references/layout.md
new file mode 100644
index 00000000..ddd54a29
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/layout.md
@@ -0,0 +1,425 @@
+---
+title: "Layout | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/layout
+
+# Layout
+
+A consistent layout that adapts to various contexts makes your experience more approachable and helps people enjoy their favorite apps and games on all their devices.
+
+
+
+Your app’s layout helps ground people in your content from the moment they open it. People expect familiar relationships between controls and content to help them use and discover your app’s features, and designing the layout to take advantage of this makes your app feel at home on the platform.
+
+Apple provides templates, guides, and other resources that can help you integrate Apple technologies and design your apps and games to run on all Apple platforms. See [Apple Design Resources](https://developer.apple.com/design/resources/).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/layout#Best-practices)
+
+**Group related items to help people find the information they want.** For example, you might use negative space, background shapes, colors, materials, or separator lines to show when elements are related and to separate information into distinct areas. When you do so, ensure that content and controls remain clearly distinct.
+
+**Make essential information easy to find by giving it sufficient space.** People want to view the most important information right away, so don’t obscure it by crowding it with nonessential details. You can make secondary information available in other parts of the window, or include it in an additional view.
+
+**Extend content to fill the screen or window.** Make sure backgrounds and full-screen artwork extend to the edges of the display. Also ensure that scrollable layouts continue all the way to the bottom and the sides of the device screen. Controls and navigation components like sidebars and tab bars appear on top of content rather than on the same plane, so it’s important for your layout to take this into account.
+
+When your content doesn’t span the full window, use a background extension view to provide the appearance of content behind the control layer on either side of the screen, such as beneath the sidebar or inspector. For developer guidance, see [`backgroundExtensionEffect()`](https://developer.apple.com/documentation/SwiftUI/View/backgroundExtensionEffect\(\)) and [`UIBackgroundExtensionView`](https://developer.apple.com/documentation/UIKit/UIBackgroundExtensionView).
+
+
+
+## [Visual hierarchy](https://developer.apple.com/design/human-interface-guidelines/layout#Visual-hierarchy)
+
+**Differentiate controls from content.** Take advantage of the Liquid Glass material to provide a distinct appearance for controls that’s consistent across iOS, iPadOS, and macOS. Instead of a background, use a scroll edge effect to provide a transition between content and the control area. For guidance, see [Scroll views](https://developer.apple.com/design/human-interface-guidelines/scroll-views).
+
+**Place items to convey their relative importance.** People often start by viewing items in reading order — that is, from top to bottom and from the leading to trailing side — so it generally works well to place the most important items near the top and leading side of the window, display, or [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view). Be aware that reading order varies by language, and take [right to left](https://developer.apple.com/design/human-interface-guidelines/right-to-left) languages into account as you design.
+
+**Align components with one another to make them easier to scan and to communicate organization and hierarchy.** Alignment makes an app look neat and organized and can help people track content while scrolling or moving their eyes, making it easier to find information. Along with indentation, alignment can also help people understand an information hierarchy.
+
+**Take advantage of progressive disclosure to help people discover content that’s currently hidden.** For example, if you can’t display all the items in a large collection at once, you need to indicate that there are additional items that aren’t currently visible. Depending on the platform, you might use a [disclosure control](https://developer.apple.com/design/human-interface-guidelines/disclosure-controls), or display parts of items to hint that people can reveal additional content by interacting with the view, such as by scrolling.
+
+**Make controls easier to use by providing enough space around them and grouping them in logical sections.** If unrelated controls are too close together — or if other content crowds them — they can be difficult for people to tell apart or understand what they do, which can make your app or game hard to use. For guidance, see [Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars).
+
+## [Adaptability](https://developer.apple.com/design/human-interface-guidelines/layout#Adaptability)
+
+Every app and game needs to adapt when the device or system context changes. In iOS, iPadOS, tvOS, and visionOS, the system defines a collection of _traits_ that characterize variations in the device environment that can affect the way your app or game looks. Using SwiftUI or Auto Layout can help you ensure that your interface adapts dynamically to these traits and other context changes; if you don’t use these tools, you need to use alternative methods to do the work.
+
+Here are some of the most common device and system variations you need to handle:
+
+ * Different device screen sizes, resolutions, and color spaces
+
+ * Different device orientations (portrait/landscape)
+
+ * System features like Dynamic Island and camera controls
+
+ * External display support, Display Zoom, and resizable windows on iPad
+
+ * Dynamic Type text-size changes
+
+ * Locale-based internationalization features like left-to-right/right-to-left layout direction, date/time/number formatting, font variation, and text length
+
+
+
+
+**Design a layout that adapts gracefully to context changes while remaining recognizably consistent.** People expect your experience to work well and remain familiar when they rotate their device, resize a window, add another display, or switch to a different device. You can help ensure an adaptable interface by respecting system-defined safe areas, margins, and guides (where available) and specifying layout modifiers to fine-tune the placement of views in your interface.
+
+**Be prepared for text-size changes.** People appreciate apps and games that respond when they choose a different text size. When you support [Dynamic Type](https://developer.apple.com/design/human-interface-guidelines/typography#Supporting-Dynamic-Type) — a feature that lets people choose the size of visible text in iOS, iPadOS, tvOS, visionOS, and watchOS — your app or game can respond appropriately when people adjust text size. To support Dynamic Type in your Unity-based game, use Apple’s accessibility plug-in (for developer guidance, see [Apple – Accessibility](https://github.com/apple/unityplugins/blob/main/plug-ins/Apple.Accessibility/Apple.Accessibility_Unity/Assets/Apple.Accessibility/Documentation~/Apple.Accessibility.md)). For guidance on displaying text in your app, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography).
+
+**Preview your app on multiple devices, using different orientations, localizations, and text sizes.** You can streamline the testing process by first testing versions of your experience that use the largest and the smallest layouts. Although it’s generally best to preview features like wide-gamut color on actual devices, you can use Xcode Simulator to check for clipping and other layout issues. For example, if your iOS app or game supports landscape mode, you can use Simulator to make sure your layouts look great whether the device rotates left or right.
+
+**When necessary, scale artwork in response to display changes.** For example, viewing your app or game in a different context — such as on a screen with a different aspect ratio — might make your artwork appear cropped, letterboxed, or pillarboxed. If this happens, don’t change the aspect ratio of the artwork; instead, scale it so that important visual content remains visible. In visionOS, the system automatically [scales](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Scale) a window when it moves along the z-axis.
+
+## [Guides and safe areas](https://developer.apple.com/design/human-interface-guidelines/layout#Guides-and-safe-areas)
+
+A _layout guide_ defines a rectangular region that helps you position, align, and space your content on the screen. The system includes predefined layout guides that make it easy to apply standard margins around content and restrict the width of text for optimal readability. You can also define custom layout guides. For developer guidance, see [`UILayoutGuide`](https://developer.apple.com/documentation/UIKit/UILayoutGuide) and [`NSLayoutGuide`](https://developer.apple.com/documentation/AppKit/NSLayoutGuide).
+
+A _safe area_ defines the area within a view that isn’t covered by a toolbar, tab bar, or other views a window might provide. Safe areas are essential for avoiding a device’s interactive and display features, like Dynamic Island on iPhone or the camera housing on some Mac models. For developer guidance, see [`SafeAreaRegions`](https://developer.apple.com/documentation/SwiftUI/SafeAreaRegions) and [Positioning content relative to the safe area](https://developer.apple.com/documentation/UIKit/positioning-content-relative-to-the-safe-area).
+
+**Respect key display and system features in each platform.** When an app or game doesn’t accommodate such features, it doesn’t feel at home in the platform and may be harder for people to use. In addition to helping you avoid display and system features, safe areas can also help you account for interactive components like bars, dynamically repositioning content when sizes change.
+
+For templates that include the guides and safe areas for each platform, see [Apple Design Resources](https://developer.apple.com/design/resources/).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/layout#Platform-considerations)
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/layout#iOS)
+
+**Aim to support both portrait and landscape orientations.** People appreciate apps and games that work well in different device orientations, but sometimes your experience needs to run in only portrait or only landscape. When this is the case, you can rely on people trying both orientations before settling on the one you support — there’s no need to tell people to rotate their device. If your app or game is landscape-only, make sure it runs equally well whether people rotate their device to the left or the right.
+
+**Prefer a full-bleed interface for your game.** Give players a beautiful interface that fills the screen while accommodating the corner radius, sensor housing, and features like Dynamic Island. If necessary, consider giving players the option to view your game using a letterboxed or pillarboxed appearance.
+
+**Avoid full-width buttons.** Buttons feel at home in iOS when they respect system-defined margins and are inset from the edges of the screen. If you need to include a full-width button, make sure it harmonizes with the curvature of the hardware and aligns with adjacent safe areas.
+
+**Hide the status bar only when it adds value or enhances your experience.** The status bar displays information people find useful and it occupies an area of the screen most apps don’t fully use, so it’s generally a good idea to keep it visible. The exception is if you offer an in-depth experience like playing a game or viewing media, where it might make sense to hide the status bar.
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/layout#iPadOS)
+
+People can freely resize windows down to a minimum width and height, similar to window behavior in macOS. It’s important to account for this resizing behavior and the full range of possible window sizes when designing your layout. For guidance, see [Multitasking](https://developer.apple.com/design/human-interface-guidelines/multitasking#iPadOS) and [Windows](https://developer.apple.com/design/human-interface-guidelines/windows#iPadOS).
+
+**As someone resizes a window, defer switching to a compact view for as long as possible.** Design for a full-screen view first, and only switch to a compact view when a version of the full layout no longer fits. This helps the UI feel more stable and familiar in as many situations as possible. For more complex layouts such as [split views](https://developer.apple.com/design/human-interface-guidelines/split-views), prefer hiding tertiary columns such as inspectors as the view narrows.
+
+**Test your layout at common system-provided sizes, and provide smooth transitions.** Window controls provide the option to arrange windows to fill halves, thirds, and quadrants of the screen, so it’s important to check your layout at each of these sizes on a variety of devices. Be sure to minimize unexpected UI changes as people adjust down to the minimum and up to the maximum window size.
+
+**Consider a convertible tab bar for adaptive navigation.** For many apps, you don’t need to choose between a tab bar or sidebar for navigation; instead, you can adopt a style of tab bar that provides both. The app first launches with your choice of a sidebar or a tab bar, and then people can tap to switch between them. As the view resizes, the presentation style changes to fit the width of the view. For guidance, see [Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars). For developer guidance, see [`sidebarAdaptable`](https://developer.apple.com/documentation/SwiftUI/TabViewStyle/sidebarAdaptable).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/layout#macOS)
+
+**Avoid placing controls or critical information at the bottom of a window.** People often move windows so that the bottom edge is below the bottom of the screen.
+
+**Avoid displaying content within the camera housing at the top edge of the window.** For developer guidance, see [`NSPrefersDisplaySafeAreaCompatibilityMode`](https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSPrefersDisplaySafeAreaCompatibilityMode).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/layout#tvOS)
+
+**Be prepared for a wide range of TV sizes.** On Apple TV, layouts don’t automatically adapt to the size of the screen like they do on iPhone or iPad. Instead, apps and games show the same interface on every display. Take extra care in designing your layout so that it looks great in a variety of screen sizes.
+
+**Adhere to the screen’s safe area.** Inset primary content 60 points from the top and bottom of the screen, and 80 points from the sides. It can be difficult for people to see content that close to the edges, and unintended cropping can occur due to overscanning on older TVs. Allow only partially displayed offscreen content and elements that deliberately flow offscreen to appear outside this zone.
+
+
+
+**Include appropriate padding between focusable elements.** When you use UIKit and the focus APIs, an element gets bigger when it comes into focus. Consider how elements look when they’re focused, and make sure you don’t let them overlap important information. For developer guidance, see [About focus interactions for Apple TV](https://developer.apple.com/documentation/UIKit/about-focus-interactions-for-apple-tv).
+
+
+
+#### [Grids](https://developer.apple.com/design/human-interface-guidelines/layout#Grids)
+
+The following grid layouts provide an optimal viewing experience. Be sure to use appropriate spacing between unfocused rows and columns to prevent overlap when an item comes into focus.
+
+If you use the UIKit collection view flow element, the number of columns in a grid is automatically determined based on the width and spacing of your content. For developer guidance, see [`UICollectionViewFlowLayout`](https://developer.apple.com/documentation/UIKit/UICollectionViewFlowLayout).
+
+ * Two-column
+ * Three-column
+ * Four-column
+ * Five-column
+ * Six-column
+ * Seven-column
+ * Eight-column
+ * Nine-column
+
+
+
+
+
+#### [Two-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Two-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 860 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Three-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Three-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 560 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Four-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Four-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 410 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Five-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Five-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 320 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Six-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Six-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 260 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Seven-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Seven-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 217 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Eight-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Eight-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 184 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+
+
+#### [Nine-column grid](https://developer.apple.com/design/human-interface-guidelines/layout#Nine-column-grid)
+
+Attribute| Value
+---|---
+Unfocused content width| 160 pt
+Horizontal spacing| 40 pt
+Minimum vertical spacing| 100 pt
+
+**Include additional vertical spacing for titled rows.** If a row has a title, provide enough spacing between the bottom of the previous unfocused row and the center of the title to avoid crowding. Also provide spacing between the bottom of the title and the top of the unfocused items in the row.
+
+**Use consistent spacing.** When content isn’t consistently spaced, it no longer looks like a grid and it’s harder for people to scan.
+
+**Make partially hidden content look symmetrical.** To help direct attention to the fully visible content, keep partially hidden offscreen content the same width on each side of the screen.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/layout#visionOS)
+
+The guidance below can help you lay out content within the windows of your visionOS app or game, making it feel familiar and easy to use. For guidance on displaying windows in space and best practices for using depth, scale, and field of view in your visionOS app, see [Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout). To learn more about visionOS window components, see [Windows > visionOS](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS).
+
+Note
+
+When you add depth to content in a standard window, the content extends beyond the window’s bounds along the z-axis. If content extends too far along the z-axis, the system clips it.
+
+**Consider centering the most important content and controls in your app or game.** Often, people can more easily discover and interact with content when it’s near the middle of a window, especially when the window is large.
+
+**Keep a window’s content within its bounds.** In visionOS, the system displays window controls just outside a window’s bounds in the XY plane. For example, the Share menu appears above the window and the controls for resizing, moving, and closing the window appear below it. Letting 2D or 3D content encroach on these areas can make the system-provided controls, especially those below the window, difficult for people to use.
+
+**If you need to display additional controls that don’t belong within a window, use an ornament.** An ornament lets you offer app controls that remain visually associated with a window without interfering with the system-provided controls. For example, a window’s toolbar and tab bar appear as ornaments. For guidance, see [Ornaments](https://developer.apple.com/design/human-interface-guidelines/ornaments).
+
+**Make a window’s interactive components easy for people to look at.** You need to include enough space around an interactive component so that visually identifying it is easy and comfortable, and to prevent the system-provided hover effect from obscuring other content. For example, place buttons so their centers are at least 60 points apart. For guidance, see [Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes), [Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout), and [Buttons > visionOS](https://developer.apple.com/design/human-interface-guidelines/buttons#visionOS).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/layout#watchOS)
+
+**Design your content to extend from one edge of the screen to the other.** The Apple Watch bezel provides a natural visual padding around your content. To avoid wasting valuable space, consider minimizing the padding between elements.
+
+
+
+**Avoid placing more than two or three controls side by side in your interface.** As a general rule, display no more than three buttons that contain glyphs — or two buttons that contain text — in a row. Although it’s usually better to let text buttons span the full width of the screen, two side-by-side buttons with short text labels can also work well, as long as the screen doesn’t scroll.
+
+
+
+**Support autorotation in views people might want to show others.** When people flip their wrist away, apps typically respond to the motion by sleeping the display, but in some cases it makes sense to autorotate the content. For example, a wearer might want to show an image to a friend or display a QR code to a reader. For developer guidance, see [`isAutorotating`](https://developer.apple.com/documentation/WatchKit/WKExtension/isAutorotating).
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/layout#Specifications)
+
+### [iOS, iPadOS device screen dimensions](https://developer.apple.com/design/human-interface-guidelines/layout#iOS-iPadOS-device-screen-dimensions)
+
+Model| Dimensions (portrait)
+---|---
+iPad Pro 12.9-inch| 1024x1366 pt (2048x2732 px @2x)
+iPad Pro 11-inch| 834x1194 pt (1668x2388 px @2x)
+iPad Pro 10.5-inch| 834x1194 pt (1668x2388 px @2x)
+iPad Pro 9.7-inch| 768x1024 pt (1536x2048 px @2x)
+iPad Air 13-inch| 1024x1366 pt (2048x2732 px @2x)
+iPad Air 11-inch| 820x1180 pt (1640x2360 px @2x)
+iPad Air 10.9-inch| 820x1180 pt (1640x2360 px @2x)
+iPad Air 10.5-inch| 834x1112 pt (1668x2224 px @2x)
+iPad Air 9.7-inch| 768x1024 pt (1536x2048 px @2x)
+iPad 11-inch| 820x1180 pt (1640x2360 px @2x)
+iPad 10.2-inch| 810x1080 pt (1620x2160 px @2x)
+iPad 9.7-inch| 768x1024 pt (1536x2048 px @2x)
+iPad mini 8.3-inch| 744x1133 pt (1488x2266 px @2x)
+iPad mini 7.9-inch| 768x1024 pt (1536x2048 px @2x)
+iPhone 17 Pro Max| 440x956 pt (1320x2868 px @3x)
+iPhone 17 Pro| 402x874 pt (1206x2622 px @3x)
+iPhone Air| 420x912 pt (1260x2736 px @3x)
+iPhone 17| 402x874 pt (1206x2622 px @3x)
+iPhone 16 Pro Max| 440x956 pt (1320x2868 px @3x)
+iPhone 16 Pro| 402x874 pt (1206x2622 px @3x)
+iPhone 16 Plus| 430x932 pt (1290x2796 px @3x)
+iPhone 16| 393x852 pt (1179x2556 px @3x)
+iPhone 16e| 390x844 pt (1170x2532 px @3x)
+iPhone 15 Pro Max| 430x932 pt (1290x2796 px @3x)
+iPhone 15 Pro| 393x852 pt (1179x2556 px @3x)
+iPhone 15 Plus| 430x932 pt (1290x2796 px @3x)
+iPhone 15| 393x852 pt (1179x2556 px @3x)
+iPhone 14 Pro Max| 430x932 pt (1290x2796 px @3x)
+iPhone 14 Pro| 393x852 pt (1179x2556 px @3x)
+iPhone 14 Plus| 428x926 pt (1284x2778 px @3x)
+iPhone 14| 390x844 pt (1170x2532 px @3x)
+iPhone 13 Pro Max| 428x926 pt (1284x2778 px @3x)
+iPhone 13 Pro| 390x844 pt (1170x2532 px @3x)
+iPhone 13| 390x844 pt (1170x2532 px @3x)
+iPhone 13 mini| 375x812 pt (1125x2436 px @3x)
+iPhone 12 Pro Max| 428x926 pt (1284x2778 px @3x)
+iPhone 12 Pro| 390x844 pt (1170x2532 px @3x)
+iPhone 12| 390x844 pt (1170x2532 px @3x)
+iPhone 12 mini| 375x812 pt (1125x2436 px @3x)
+iPhone 11 Pro Max| 414x896 pt (1242x2688 px @3x)
+iPhone 11 Pro| 375x812 pt (1125x2436 px @3x)
+iPhone 11| 414x896 pt (828x1792 px @2x)
+iPhone XS Max| 414x896 pt (1242x2688 px @3x)
+iPhone XS| 375x812 pt (1125x2436 px @3x)
+iPhone XR| 414x896 pt (828x1792 px @2x)
+iPhone X| 375x812 pt (1125x2436 px @3x)
+iPhone 8 Plus| 414x736 pt (1080x1920 px @3x)
+iPhone 8| 375x667 pt (750x1334 px @2x)
+iPhone 7 Plus| 414x736 pt (1080x1920 px @3x)
+iPhone 7| 375x667 pt (750x1334 px @2x)
+iPhone 6s Plus| 414x736 pt (1080x1920 px @3x)
+iPhone 6s| 375x667 pt (750x1334 px @2x)
+iPhone 6 Plus| 414x736 pt (1080x1920 px @3x)
+iPhone 6| 375x667 pt (750x1334 px @2x)
+iPhone SE 4.7-inch| 375x667 pt (750x1334 px @2x)
+iPhone SE 4-inch| 320x568 pt (640x1136 px @2x)
+iPod touch 5th generation and later| 320x568 pt (640x1136 px @2x)
+
+Note
+
+All scale factors in the table above are UIKit scale factors, which may differ from native scale factors. For developer guidance, see [`scale`](https://developer.apple.com/documentation/UIKit/UIScreen/scale) and [`nativeScale`](https://developer.apple.com/documentation/UIKit/UIScreen/nativeScale).
+
+### [iOS, iPadOS device size classes](https://developer.apple.com/design/human-interface-guidelines/layout#iOS-iPadOS-device-size-classes)
+
+A size class is a value that’s either regular or compact, where _regular_ refers to a larger screen or a screen in landscape orientation and _compact_ refers to a smaller screen or a screen in portrait orientation. For developer guidance, see [`UserInterfaceSizeClass`](https://developer.apple.com/documentation/SwiftUI/UserInterfaceSizeClass).
+
+Different size class combinations apply to the full-screen experience on different devices, based on screen size.
+
+Model| Portrait orientation| Landscape orientation
+---|---|---
+iPad Pro 12.9-inch| Regular width, regular height| Regular width, regular height
+iPad Pro 11-inch| Regular width, regular height| Regular width, regular height
+iPad Pro 10.5-inch| Regular width, regular height| Regular width, regular height
+iPad Air 13-inch| Regular width, regular height| Regular width, regular height
+iPad Air 11-inch| Regular width, regular height| Regular width, regular height
+iPad 11-inch| Regular width, regular height| Regular width, regular height
+iPad 9.7-inch| Regular width, regular height| Regular width, regular height
+iPad mini 7.9-inch| Regular width, regular height| Regular width, regular height
+iPhone 17 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 17 Pro| Compact width, regular height| Compact width, compact height
+iPhone Air| Compact width, regular height| Regular width, compact height
+iPhone 17| Compact width, regular height| Compact width, compact height
+iPhone 16 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 16 Pro| Compact width, regular height| Compact width, compact height
+iPhone 16 Plus| Compact width, regular height| Regular width, compact height
+iPhone 16| Compact width, regular height| Compact width, compact height
+iPhone 16e| Compact width, regular height| Compact width, compact height
+iPhone 15 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 15 Pro| Compact width, regular height| Compact width, compact height
+iPhone 15 Plus| Compact width, regular height| Regular width, compact height
+iPhone 15| Compact width, regular height| Compact width, compact height
+iPhone 14 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 14 Pro| Compact width, regular height| Compact width, compact height
+iPhone 14 Plus| Compact width, regular height| Regular width, compact height
+iPhone 14| Compact width, regular height| Compact width, compact height
+iPhone 13 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 13 Pro| Compact width, regular height| Compact width, compact height
+iPhone 13| Compact width, regular height| Compact width, compact height
+iPhone 13 mini| Compact width, regular height| Compact width, compact height
+iPhone 12 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 12 Pro| Compact width, regular height| Compact width, compact height
+iPhone 12| Compact width, regular height| Compact width, compact height
+iPhone 12 mini| Compact width, regular height| Compact width, compact height
+iPhone 11 Pro Max| Compact width, regular height| Regular width, compact height
+iPhone 11 Pro| Compact width, regular height| Compact width, compact height
+iPhone 11| Compact width, regular height| Regular width, compact height
+iPhone XS Max| Compact width, regular height| Regular width, compact height
+iPhone XS| Compact width, regular height| Compact width, compact height
+iPhone XR| Compact width, regular height| Regular width, compact height
+iPhone X| Compact width, regular height| Compact width, compact height
+iPhone 8 Plus| Compact width, regular height| Regular width, compact height
+iPhone 8| Compact width, regular height| Compact width, compact height
+iPhone 7 Plus| Compact width, regular height| Regular width, compact height
+iPhone 7| Compact width, regular height| Compact width, compact height
+iPhone 6s Plus| Compact width, regular height| Regular width, compact height
+iPhone 6s| Compact width, regular height| Compact width, compact height
+iPhone SE| Compact width, regular height| Compact width, compact height
+iPod touch 5th generation and later| Compact width, regular height| Compact width, compact height
+
+### [watchOS device screen dimensions](https://developer.apple.com/design/human-interface-guidelines/layout#watchOS-device-screen-dimensions)
+
+Series| Size| Width (pixels)| Height (pixels)
+---|---|---|---
+Apple Watch Ultra (3rd generation)| 49mm| 422| 514
+10, 11| 42mm| 374| 446
+10, 11| 46mm| 416| 496
+Apple Watch Ultra (1st and 2nd generations)| 49mm| 410| 502
+7, 8, and 9| 41mm| 352| 430
+7, 8, and 9| 45mm| 396| 484
+4, 5, 6, and SE (all generations)| 40mm| 324| 394
+4, 5, 6, and SE (all generations)| 44mm| 368| 448
+1, 2, and 3| 38mm| 272| 340
+1, 2, and 3| 42mm| 312| 390
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/layout#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/layout#Related)
+
+[Right to left](https://developer.apple.com/design/human-interface-guidelines/right-to-left)
+
+[Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout)
+
+[Layout and organization](https://developer.apple.com/design/human-interface-guidelines/layout-and-organization)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/layout#Developer-documentation)
+
+[Composing custom layouts with SwiftUI](https://developer.apple.com/documentation/SwiftUI/composing-custom-layouts-with-swiftui) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/layout#Videos)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+[ Compose custom layouts with SwiftUI ](https://developer.apple.com/videos/play/wwdc2022/10056)
+
+[ Essential Design Principles ](https://developer.apple.com/videos/play/wwdc2017/802)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/layout#Change-log)
+
+Date| Changes
+---|---
+September 9, 2025| Added specifications for iPhone 17, iPhone Air, iPhone 17 Pro, iPhone 17 Pro Max, Apple Watch SE 3, Apple Watch Series 11, and Apple Watch Ultra 3.
+June 9, 2025| Added guidance for Liquid Glass.
+March 7, 2025| Added specifications for iPhone 16e, iPad 11-inch, iPad Air 11-inch, and iPad Air 13-inch.
+September 9, 2024| Added specifications for iPhone 16, iPhone 16 Plus, iPhone 16 Pro, iPhone 16 Pro Max, and Apple Watch Series 10.
+June 10, 2024| Made minor corrections and organizational updates.
+February 2, 2024| Enhanced guidance for avoiding system controls in iPadOS app layouts, and added specifications for 10.9-inch iPad Air and 8.3-inch iPad mini.
+December 5, 2023| Clarified guidance on centering content in a visionOS window.
+September 15, 2023| Added specifications for iPhone 15 Pro Max, iPhone 15 Pro, iPhone 15 Plus, iPhone 15, Apple Watch Ultra 2, and Apple Watch SE.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| Added specifications for iPhone 14 Pro Max, iPhone 14 Pro, iPhone 14 Plus, iPhone 14, and Apple Watch Ultra.
+
diff --git a/web-app/public/skills/hig-foundations/references/materials.md b/web-app/public/skills/hig-foundations/references/materials.md
new file mode 100644
index 00000000..0452bf57
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/materials.md
@@ -0,0 +1,238 @@
+---
+title: "Materials | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/materials
+
+# Materials
+
+A material is a visual effect that creates a sense of depth, layering, and hierarchy between foreground and background elements.
+
+
+
+Materials help visually separate foreground elements, such as text and controls, from background elements, such as content and solid colors. By allowing color to pass through from background to foreground, a material establishes visual hierarchy to help people more easily retain a sense of place.
+
+Apple platforms feature two types of materials: Liquid Glass, and standard materials. [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) is a dynamic material that unifies the design language across Apple platforms, allowing you to present controls and navigation without obscuring underlying content. In contrast to Liquid Glass, the [standard materials](https://developer.apple.com/design/human-interface-guidelines/materials#Standard-materials) help with visual differentiation within the content layer.
+
+## [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass)
+
+Liquid Glass forms a distinct functional layer for controls and navigation elements — like tab bars and sidebars — that floats above the content layer, establishing a clear visual hierarchy between functional elements and content. Liquid Glass allows content to scroll and peek through from beneath these elements to give the interface a sense of dynamism and depth, all while maintaining legibility for controls and navigation.
+
+**Don’t use Liquid Glass in the content layer.** Liquid Glass works best when it provides a clear distinction between interactive elements and content, and including it in the content layer can result in unnecessary complexity and a confusing visual hierarchy. Instead, use [standard materials](https://developer.apple.com/design/human-interface-guidelines/materials#Standard-materials) for elements in the content layer, such as app backgrounds. An exception to this is for controls in the content layer with a transient interactive element like [sliders](https://developer.apple.com/design/human-interface-guidelines/sliders) and [toggles](https://developer.apple.com/design/human-interface-guidelines/toggles); in these cases, the element takes on a Liquid Glass appearance to emphasize its interactivity when a person activates it.
+
+**Use Liquid Glass effects sparingly.** Standard components from system frameworks pick up the appearance and behavior of this material automatically. If you apply Liquid Glass effects to a custom control, do so sparingly. Liquid Glass seeks to bring attention to the underlying content, and overusing this material in multiple custom controls can provide a subpar user experience by distracting from that content. Limit these effects to the most important functional elements in your app. For developer guidance, see [Applying Liquid Glass to custom views](https://developer.apple.com/documentation/SwiftUI/Applying-Liquid-Glass-to-custom-views).
+
+**Only use clear Liquid Glass for components that appear over visually rich backgrounds.** Liquid Glass provides two variants — [`regular`](https://developer.apple.com/documentation/SwiftUI/Glass/regular) and [`clear`](https://developer.apple.com/documentation/SwiftUI/Glass/clear) — that you can choose when building custom components or styling some system components. The appearance of these variants can differ in response to certain system settings, like if people choose a preferred look for Liquid Glass in their device’s display settings, or turn on accessibility settings that reduce transparency or increase contrast in the interface.
+
+The _regular_ variant blurs and adjusts the luminosity of background content to maintain legibility of text and other foreground elements. Scroll edge effects further enhance legibility by blurring and reducing the opacity of background content. Most system components use this variant. Use the regular variant when background content might create legibility issues, or when components have a significant amount of text, such as alerts, sidebars, or popovers.
+
+On dark background
+
+On light background
+
+The _clear_ variant is highly translucent, which is ideal for prioritizing the visibility of the underlying content and ensuring visually rich background elements remain prominent. Use this variant for components that float above media backgrounds — such as photos and videos — to create a more immersive content experience.
+
+
+
+For optimal contrast and legibility, determine whether to add a dimming layer behind components with clear Liquid Glass:
+
+ * If the underlying content is bright, consider adding a dark dimming layer of 35% opacity. For developer guidance, see [`clear`](https://developer.apple.com/documentation/SwiftUI/Glass/clear).
+
+ * If the underlying content is sufficiently dark, or if you use standard media playback controls from AVKit that provide their own dimming layer, you don’t need to apply a dimming layer.
+
+
+
+
+For guidance about the use of color, see [Liquid Glass color](https://developer.apple.com/design/human-interface-guidelines/color#Liquid-Glass-color).
+
+## [Standard materials](https://developer.apple.com/design/human-interface-guidelines/materials#Standard-materials)
+
+Use standard materials and effects — such as [blur](https://developer.apple.com/documentation/UIKit/UIBlurEffect), [vibrancy](https://developer.apple.com/documentation/UIKit/UIVibrancyEffect), and [blending modes](https://developer.apple.com/documentation/AppKit/NSVisualEffectView/BlendingMode-swift.enum) — to convey a sense of structure in the content beneath Liquid Glass.
+
+**Choose materials and effects based on semantic meaning and recommended usage.** Avoid selecting a material or effect based on the apparent color it imparts to your interface, because system settings can change its appearance and behavior. Instead, match the material or vibrancy style to your specific use case.
+
+**Help ensure legibility by using vibrant colors on top of materials.** When you use system-defined vibrant colors, you don’t need to worry about colors seeming too dark, bright, saturated, or low contrast in different contexts. Regardless of the material you choose, use vibrant colors on top of it. For guidance, see [System colors](https://developer.apple.com/design/human-interface-guidelines/color#System-colors).
+
+Poor contrast between the material and `systemGray3` label
+
+
+
+Good contrast between the material and vibrant color label
+
+
+
+**Consider contrast and visual separation when choosing a material to combine with blur and vibrancy effects.** For example, consider that:
+
+ * Thicker materials, which are more opaque, can provide better contrast for text and other elements with fine features.
+
+ * Thinner materials, which are more translucent, can help people retain their context by providing a visible reminder of the content that’s in the background.
+
+
+
+
+For developer guidance, see [`Material`](https://developer.apple.com/documentation/SwiftUI/Material).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/materials#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/materials#iOS-iPadOS)
+
+In addition to Liquid Glass, iOS and iPadOS continue to provide four standard materials — ultra-thin, thin, regular (default), and thick — which you can use in the content layer to help create visual distinction.
+
+`ultraThin`
+
+`thin`
+
+`regular`
+
+`thick`
+
+iOS and iPadOS also define vibrant colors for labels, fills, and separators that are specifically designed to work with each material. Labels and fills both have several levels of vibrancy; separators have one level. The name of a level indicates the relative amount of contrast between an element and the background: The default level has the highest contrast, whereas quaternary (when it exists) has the lowest contrast.
+
+Except for quaternary, you can use the following vibrancy values for labels on any material. In general, avoid using quaternary on top of the [`thin`](https://developer.apple.com/documentation/SwiftUI/Material/thin) and [`ultraThin`](https://developer.apple.com/documentation/SwiftUI/Material/ultraThin) materials, because the contrast is too low.
+
+ * [`UIVibrancyEffectStyle.label`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/label) (default)
+
+ * [`UIVibrancyEffectStyle.secondaryLabel`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/secondaryLabel)
+
+ * [`UIVibrancyEffectStyle.tertiaryLabel`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/tertiaryLabel)
+
+ * [`UIVibrancyEffectStyle.quaternaryLabel`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/quaternaryLabel)
+
+
+
+
+You can use the following vibrancy values for fills on all materials.
+
+ * [`UIVibrancyEffectStyle.fill`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/fill) (default)
+
+ * [`UIVibrancyEffectStyle.secondaryFill`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/secondaryFill)
+
+ * [`UIVibrancyEffectStyle.tertiaryFill`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/tertiaryFill)
+
+
+
+
+The system provides a single, default vibrancy value for a [separator](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/separator), which works well on all materials.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/materials#macOS)
+
+macOS provides several standard materials with designated purposes, and vibrant versions of all [system colors](https://developer.apple.com/design/human-interface-guidelines/color#Specifications). For developer guidance, see [`NSVisualEffectView.Material`](https://developer.apple.com/documentation/AppKit/NSVisualEffectView/Material-swift.enum).
+
+**Choose when to allow vibrancy in custom views and controls.** Depending on configuration and system settings, system views and controls use vibrancy to make foreground content stand out against any background. Test your interface in a variety of contexts to discover when vibrancy enhances the appearance and improves communication.
+
+**Choose a background blending mode that complements your interface design.** macOS defines two modes that blend background content: behind window and within window. For developer guidance, see [`NSVisualEffectView.BlendingMode`](https://developer.apple.com/documentation/AppKit/NSVisualEffectView/BlendingMode-swift.enum).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/materials#tvOS)
+
+In tvOS, Liquid Glass appears throughout navigation elements and system experiences such as Top Shelf and Control Center. Certain interface elements, like image views and buttons, adopt Liquid Glass when they gain focus.
+
+
+
+In addition to Liquid Glass, tvOS continues to provide standard materials, which you can use to help define structure in the content layer. The thickness of a standard material affects how prominently the underlying content shows through. For example, consider using standard materials in the following ways:
+
+Material| Recommended for
+---|---
+[`ultraThin`](https://developer.apple.com/documentation/SwiftUI/Material/ultraThin)| Full-screen views that require a light color scheme
+[`thin`](https://developer.apple.com/documentation/SwiftUI/Material/thin)| Overlay views that partially obscure onscreen content and require a light color scheme
+[`regular`](https://developer.apple.com/documentation/SwiftUI/Material/regular)| Overlay views that partially obscure onscreen content
+[`thick`](https://developer.apple.com/documentation/SwiftUI/Material/thick)| Overlay views that partially obscure onscreen content and require a dark color scheme
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/materials#visionOS)
+
+In visionOS, windows generally use an unmodifiable system-defined material called _glass_ that helps people stay grounded by letting light, the current Environment, virtual content, and objects in people’s surroundings show through. Glass is an adaptive material that limits the range of background color information so a window can continue to provide contrast for app content while becoming brighter or darker depending on people’s physical surroundings and other virtual content.
+
+Video with custom controls.
+
+Content description: A recording of the Music app window in visionOS. The window uses the glass material and adapts as the viewing angle and lighting change.
+
+Play
+
+Note
+
+visionOS doesn’t have a distinct Dark Mode setting. Instead, glass automatically adapts to the luminance of the objects and colors behind it.
+
+**Prefer translucency to opaque colors in windows.** Areas of opacity can block people’s view, making them feel constricted and reducing their awareness of the virtual and physical objects around them.
+
+
+
+
+
+
+
+
+
+**If necessary, choose materials that help you create visual separations or indicate interactivity in your app.** If you need to create a custom component, you may need to specify a system material for it. Use the following examples for guidance.
+
+ * The [`thin`](https://developer.apple.com/documentation/SwiftUI/Material/thin) material brings attention to interactive elements like buttons and selected items.
+
+ * The [`regular`](https://developer.apple.com/documentation/SwiftUI/Material/regular) material can help you visually separate sections of your app, like a sidebar or a grouped table view.
+
+ * The [`thick`](https://developer.apple.com/documentation/SwiftUI/Material/thick) material lets you create a dark element that remains visually distinct when it’s on top of an area that uses a `regular` background.
+
+
+
+
+
+
+To ensure foreground content remains legible when it displays on top of a material, visionOS applies vibrancy to text, symbols, and fills. Vibrancy enhances the sense of depth by pulling light and color forward from both virtual and physical surroundings.
+
+visionOS defines three vibrancy values that help you communicate a hierarchy of text, symbols, and fills.
+
+ * Use [`UIVibrancyEffectStyle.label`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/label) for standard text.
+
+ * Use [`UIVibrancyEffectStyle.secondaryLabel`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/secondaryLabel) for descriptive text like footnotes and subtitles.
+
+ * Use [`UIVibrancyEffectStyle.tertiaryLabel`](https://developer.apple.com/documentation/UIKit/UIVibrancyEffectStyle/tertiaryLabel) for inactive elements, and only when text doesn’t need high legibility.
+
+
+
+
+`label`
+
+`secondaryLabel`
+
+`tertiaryLabel`
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/materials#watchOS)
+
+**Use materials to provide context in a full-screen modal view.** Because full-screen modal views are common in watchOS, the contrast provided by material layers can help orient people in your app and distinguish controls and system elements from other content. Avoid removing or replacing material backgrounds for modal sheets when they’re provided by default.
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/materials#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/materials#Related)
+
+[Color](https://developer.apple.com/design/human-interface-guidelines/color)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[Dark Mode](https://developer.apple.com/design/human-interface-guidelines/dark-mode)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/materials#Developer-documentation)
+
+[Adopting Liquid Glass](https://developer.apple.com/documentation/TechnologyOverviews/adopting-liquid-glass)
+
+[`glassEffect(_:in:)`](https://developer.apple.com/documentation/SwiftUI/View/glassEffect\(_:in:\)) — SwiftUI
+
+[`Material`](https://developer.apple.com/documentation/SwiftUI/Material) — SwiftUI
+
+[`UIVisualEffectView`](https://developer.apple.com/documentation/UIKit/UIVisualEffectView) — UIKit
+
+[`NSVisualEffectView`](https://developer.apple.com/documentation/AppKit/NSVisualEffectView) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/materials#Videos)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/materials#Change-log)
+
+Date| Changes
+---|---
+September 9, 2025| Updated guidance for Liquid Glass.
+June 9, 2025| Added guidance for Liquid Glass.
+August 6, 2024| Added platform-specific art.
+December 5, 2023| Updated descriptions of the various material types, and clarified terms related to vibrancy and material thickness.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Added guidance on using materials to provide context and orientation in watchOS apps.
+
diff --git a/web-app/public/skills/hig-foundations/references/motion.md b/web-app/public/skills/hig-foundations/references/motion.md
new file mode 100644
index 00000000..262e739c
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/motion.md
@@ -0,0 +1,103 @@
+---
+title: "Motion | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/motion
+
+# Motion
+
+Beautiful, fluid motions bring the interface to life, conveying status, providing feedback and instruction, and enriching the visual experience of your app or game.
+
+
+
+Many system components automatically include motion, letting you offer familiar and consistent experiences throughout your app or game. System components might also adjust their motion in response to factors like accessibility settings or different input methods. For example, the movement of [Liquid Glass](https://developer.apple.com/design/human-interface-guidelines/materials#Liquid-Glass) responds to direct touch interaction with greater emphasis to reinforce the feeling of a tactile experience, but produces a more subdued effect when a person interacts using a trackpad.
+
+If you design custom motion, follow the guidelines below.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/motion#Best-practices)
+
+**Add motion purposefully, supporting the experience without overshadowing it.** Don’t add motion for the sake of adding motion. Gratuitous or excessive animation can distract people and may make them feel disconnected or physically uncomfortable.
+
+**Make motion optional.** Not everyone can or wants to experience the motion in your app or game, so it’s essential to avoid using it as the only way to communicate important information. To help everyone enjoy your app or game, supplement visual feedback by also using alternatives like [haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics) and [audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio) to communicate.
+
+## [Providing feedback](https://developer.apple.com/design/human-interface-guidelines/motion#Providing-feedback)
+
+**Strive for realistic feedback motion that follows people’s gestures and expectations.** In nongame apps, accurate, realistic motion can help people understand how something works, but feedback motion that doesn’t make sense can make them feel disoriented. For example, if someone reveals a view by sliding it down from the top, they don’t expect to dismiss the view by sliding it to the side.
+
+**Aim for brevity and precision in feedback animations.** When animated feedback is brief and precise, it tends to feel lightweight and unobtrusive, and it can often convey information more effectively than prominent animation. For example, when a game displays a succinct animation that’s precisely tied to a successful action, players can instantly get the message without being distracted from their gameplay. Another example is in visionOS: When people tap a panorama in Photos, it quickly and smoothly expands to fill the space in front of them, helping them track the transition without making them wait to enjoy the content.
+
+**In apps, generally avoid adding motion to UI interactions that occur frequently.** The system already provides subtle animations for interactions with standard interface elements. For a custom element, you generally want to avoid making people spend extra time paying attention to unnecessary motion every time they interact with it.
+
+**Let people cancel motion.** As much as possible, don’t make people wait for an animation to complete before they can do anything, especially if they have to experience the animation more than once.
+
+**Consider using animated symbols where it makes sense.** When you use SF Symbols 5 or later, you can apply animations to SF Symbols or custom symbols. For guidance, see [Animations](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Animations).
+
+## [Leveraging platform capabilities](https://developer.apple.com/design/human-interface-guidelines/motion#Leveraging-platform-capabilities)
+
+**Make sure your game’s motion looks great by default on each platform you support.** In most games, maintaining a consistent frame rate of 30 to 60 fps typically results in a smooth, visually appealing experience. For each platform you support, use the device’s graphics capabilities to enable default settings that let people enjoy your game without first having to change those settings.
+
+**Let people customize the visual experience of your game to optimize performance or battery life.** For example, consider letting people switch between power modes when the system detects the presence of an external power source.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/motion#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or tvOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/motion#visionOS)
+
+In addition to subtly communicating context, drawing attention to information, and enriching immersive experiences, motion in visionOS can combine with [depth](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Depth) to provide essential feedback when people look at interactive elements. Because motion is likely to be a large part of your visionOS experience, it’s crucial to avoid causing distraction, confusion, or discomfort.
+
+**As much as possible, avoid displaying motion at the edges of a person’s field of view.** People can be particularly sensitive to motion that occurs in their peripheral vision: in addition to being distracting, such motion can even cause discomfort because it can make people feel like they or their surroundings are moving. If you need to show an object moving in the periphery during an immersive experience, make sure the object’s brightness level is similar to the rest of the visible content.
+
+**Help people remain comfortable when showing the movement of large virtual objects.** If an object is large enough to fill a lot of the [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view), occluding most or all of [passthrough](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Immersion-and-passthrough), people can naturally perceive it as being part of their surroundings. To help people perceive the object’s movement without making them think that they or their surroundings are moving, you can increase the object’s translucency, helping people see through it, or lower its contrast to make its motion less noticeable.
+
+Note
+
+People can experience discomfort even when they’re the ones moving a large virtual object, such as a window. Although adjusting translucency and contrast can help in this scenario, consider also keeping a window’s size fairly small.
+
+**Consider using fades when you need to relocate an object.** When an object moves from one location to another, people naturally watch the movement. If such movement doesn’t communicate anything useful to people, you can fade the object out before moving it and fade it back in after it’s in the new location.
+
+**In general, avoid letting people rotate a virtual world.** When a virtual world rotates, the experience typically upsets people’s sense of stability, even when they control the rotation and the movement is subtle. Instead, consider using instantaneous directional changes during a quick fade-out.
+
+**Consider giving people a stationary frame of reference.** It can be easier for people to handle visual movement when it’s contained within an area that doesn’t move. In contrast, if the entire surrounding area appears to move — for example, in a game that automatically moves a player through space — people can feel unwell.
+
+**Avoid showing objects that oscillate in a sustained way.** In particular, you want to avoid showing an oscillation that has a frequency of around 0.2 Hz because people can be very sensitive to this frequency. If you need to show objects oscillating, aim to keep the amplitude low and consider making the content translucent.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/motion#watchOS)
+
+SwiftUI provides a powerful and streamlined way to add motion to your app. If you need to use WatchKit to animate layout and appearance changes — or create animated image sequences — see [`WKInterfaceImage`](https://developer.apple.com/documentation/WatchKit/WKInterfaceImage#1652345).
+
+Note
+
+All layout- and appearance-based animations automatically include built-in easing that plays at the start and end of the animation. You can’t turn off or customize easing.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/motion#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/motion#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Accessibility](https://www.apple.com/accessibility/)
+
+[Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout)
+
+[Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/motion#Developer-documentation)
+
+[Animating views and transitions](https://developer.apple.com/tutorials/SwiftUI/animating-views-and-transitions) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/motion#Videos)
+
+[ Enhance your UI animations and transitions ](https://developer.apple.com/videos/play/wwdc2024/10145)
+
+[ Create custom visual effects with SwiftUI ](https://developer.apple.com/videos/play/wwdc2024/10151)
+
+[ Design considerations for vision and motion ](https://developer.apple.com/videos/play/wwdc2023/10078)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/motion#Change-log)
+
+Date| Changes
+---|---
+September 9, 2025| Added guidance for Liquid Glass.
+June 10, 2024| Added game-specific examples and enhanced guidance for using motion in games.
+February 2, 2024| Enhanced guidance for minimizing peripheral motion in visionOS apps.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/privacy.md b/web-app/public/skills/hig-foundations/references/privacy.md
new file mode 100644
index 00000000..4d0811d6
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/privacy.md
@@ -0,0 +1,231 @@
+---
+title: "Privacy | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/privacy
+
+# Privacy
+
+Privacy is paramount: it’s critical to be transparent about the privacy-related data and resources you require and essential to protect the data people allow you to access.
+
+
+
+People use their devices in very personal ways and they expect apps to help them preserve their privacy.
+
+When you submit a new or updated app, you must provide details about your privacy practices and the privacy-relevant data you collect so the App Store can display the information on your product page. (You can manage this information at any time in [App Store Connect](https://help.apple.com/app-store-connect/#/dev1b4647c5b).) People use the privacy details on your product page to make an informed decision before they download your app. To learn more, see [App privacy details on the App Store](https://developer.apple.com/app-store/app-privacy-details/).
+
+
+
+An app’s App Store product page helps people understand the app’s privacy practices before they download it.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/privacy#Best-practices)
+
+**Request access only to data that you actually need.** Asking for more data than a feature needs — or asking for data before a person shows interest in the feature — can make it hard for people to trust your app. Give people precise control over their data by making your permission requests as specific as possible.
+
+**Be transparent about how your app collects and uses people’s data.** People are less likely to be comfortable sharing data with your app if they don’t understand exactly how you plan to use it. Always respect people’s choices to use system features like Hide My Email and Mail Privacy Protection, and be sure you understand your obligations with regard to app tracking. To learn more about Apple privacy features, see [Privacy](https://www.apple.com/privacy/); for developer guidance, see [User privacy and data use](https://developer.apple.com/app-store/user-privacy-and-data-use/).
+
+**Process data on the device where possible.** In iOS, for example, you can take advantage of the Apple Neural Engine and custom CreateML models to process the data right on the device, helping you avoid lengthy and potentially risky round trips to a remote server.
+
+**Adopt system-defined privacy protections and follow security best practices.** For example, in iOS 15 and later, you can rely on CloudKit to provide encryption and key management for additional data types, like strings, numbers, and dates.
+
+## [Requesting permission](https://developer.apple.com/design/human-interface-guidelines/privacy#Requesting-permission)
+
+Here are several examples of the things you must request permission to access:
+
+ * Personal data, including location, health, financial, contact, and other personally identifying information
+
+ * User-generated content like emails, messages, calendar data, contacts, gameplay information, Apple Music activity, HomeKit data, and audio, video, and photo content
+
+ * Protected resources like Bluetooth peripherals, home automation features, Wi-Fi connections, and local networks
+
+ * Device capabilities like camera and microphone
+
+ * In a visionOS app running in a Full Space, ARKit data, such as hand tracking, plane estimation, image anchoring, and world tracking
+
+ * The device’s advertising identifier, which supports app tracking
+
+
+
+
+The system provides a standard alert that lets people view each request you make. You supply copy that describes why your app needs access, and the system displays your description in the alert. People can also view the description — and update their choice — in Settings > Privacy.
+
+**Request permission only when your app clearly needs access to the data or resource.** It’s natural for people to be suspicious of a request for personal information or access to a device capability, especially if there’s no obvious need for it. Ideally, wait to request permission until people actually use an app feature that requires access. For example, you can use the [location button](https://developer.apple.com/design/human-interface-guidelines/privacy#Location-button) to give people a way to share their location after they indicate interest in a feature that needs that information.
+
+**Avoid requesting permission at launch unless the data or resource is required for your app to function.** People are less likely to be bothered by a launch-time request when it’s obvious why you’re making it. For example, people understand that a navigation app needs access to their location before they can benefit from it. Similarly, before people can play a visionOS game that lets them bounce virtual objects off walls in their surroundings, they need to permit the game to access information about their surroundings.
+
+**Write copy that clearly describes how your app uses the ability, data, or resource you’re requesting.** The standard alert displays your copy (called a _purpose string_ or _usage description string_) after your app name and before the buttons people use to grant or deny their permission. Aim for a brief, complete sentence that’s straightforward, specific, and easy to understand. Use sentence case, avoid passive voice, and include a period at the end. For developer guidance, see [Requesting access to protected resources](https://developer.apple.com/documentation/UIKit/requesting-access-to-protected-resources) and [App Tracking Transparency](https://developer.apple.com/documentation/AppTrackingTransparency).
+
+| Example purpose string| Notes
+---|---|---
+| The app records during the night to detect snoring sounds.| An active sentence that clearly describes how and why the app collects the data.
+| Microphone access is needed for a better experience.| A passive sentence that provides a vague, undefined justification.
+| Turn on microphone access.| An imperative sentence that doesn’t provide any justification.
+
+Here are several examples of the standard system alert:
+
+ * Example 1
+ * Example 2
+ * Example 3
+
+
+
+
+
+
+
+
+
+### [Pre-alert screens, windows, or views](https://developer.apple.com/design/human-interface-guidelines/privacy#Pre-alert-screens-windows-or-views)
+
+Ideally, the current context helps people understand why you’re requesting their permission. If it’s essential to provide additional details, you can display a custom screen or window before the system alert appears. The following guidelines apply to custom views that display before system alerts that request permission to access protected data and resources, including camera, microphone, location, contact, calendar, and tracking.
+
+**Include only one button and make it clear that it opens the system alert.** People can feel manipulated when a custom screen or window also includes a button that doesn’t open the alert because the experience diverts them from making their choice. Another type of manipulation is using a term like “Allow” to title the custom screen’s button. If the custom button seems similar in meaning and visual weight to the allow button in the alert, people can be more likely to choose the alert’s allow button without meaning to. Use a term like “Continue” or “Next” to title the single button in your custom screen or window, clarifying that its action is to open the system alert.
+
+
+
+
+
+**Don’t include additional actions in your custom screen or window.** For example, don’t provide a way for people to leave the screen or window without viewing the system alert — like offering an option to close or cancel.
+
+
+
+Don’t include an option to cancel.
+
+
+
+Don’t include an option to close the view.
+
+### [Tracking requests](https://developer.apple.com/design/human-interface-guidelines/privacy#Tracking-requests)
+
+App tracking is a sensitive issue. In some cases, it might make sense to display a custom screen or window that describes the benefits of tracking. If you want to perform app tracking as soon as people launch your app, you must display the system-provided alert before you collect any tracking data.
+
+**Never precede the system-provided alert with a custom screen or window that could confuse or mislead people.** People sometimes tap quickly to dismiss alerts without reading them. A custom messaging screen, window, or view that takes advantage of such behaviors to influence choices will lead to rejection by App Store review.
+
+There are several prohibited custom-screen designs that will cause rejection. Some examples are offering incentives, displaying a screen or window that looks like a request, displaying an image of the alert, and annotating the screen behind the alert (as shown below). To learn more, see [App Review Guidelines: 5.1.1 (iv)](https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage).
+
+ * Incentive
+ * Imitation request
+ * Alert image
+ * Alert annotation
+
+
+
+
+
+Don’t offer incentives for granting the request. You can’t offer people compensation for granting their permission, and you can’t withhold functionality or content or make your app unusable until people allow you to track them.
+
+
+
+Don’t display a custom screen that mirrors the functionality of the system alert. In particular, don’t create a button title that uses “Allow” or similar terms, because people don’t allow anything in a pre-alert screen.
+
+
+
+Don’t show an image of the standard alert and modify it in any way.
+
+
+
+Don’t add a visual cue that draws people’s attention to the system alert’s Allow buttons.
+
+## [Location button](https://developer.apple.com/design/human-interface-guidelines/privacy#Location-button)
+
+In iOS, iPadOS, and watchOS, Core Location provides a button so people can grant your app temporary authorization to access their location at the moment a task needs it. A location button’s appearance can vary to match your app’s UI and it always communicates the action of location sharing in a way that’s instantly recognizable.
+
+
+
+The first time people open your app and tap a location button, the system displays a standard alert. The alert helps people understand how using the button limits your app’s access to their location, and reminds them of the location indicator that appears when sharing starts.
+
+
+
+After people confirm their understanding of the button’s action, simply tapping the location button gives your app one-time permission to access their location. Although each one-time authorization expires when people stop using your app, they don’t need to reconfirm their understanding of the button’s behavior.
+
+Note
+
+If your app has no authorization status, tapping the location button has the same effect as when a person chooses _Allow Once_ in the standard alert. If people previously chose _While Using the App_ , tapping the location button doesn’t change your app’s status. For developer guidance, see [`LocationButton`](https://developer.apple.com/documentation/CoreLocationUI/LocationButton) (SwiftUI) and [`CLLocationButton`](https://developer.apple.com/documentation/CoreLocationUI/CLLocationButton) (Swift).
+
+**Consider using the location button to give people a lightweight way to share their location for specific app features.** For example, your app might help people attach their location to a message or post, find a store, or identify a building, plant, or animal they’ve encountered in their location. If you know that people often grant your app _Allow Once_ permission, consider using the location button to help them benefit from sharing their location without having to repeatedly interact with the alert.
+
+**Consider customizing the location button to harmonize with your UI.** Specifically, you can:
+
+ * Choose the system-provided title that works best with your feature, such as “Current Location” or “Share My Current Location.”
+
+ * Choose the filled or outlined location glyph.
+
+ * Select a background color and a color for the title and glyph.
+
+ * Adjust the button’s corner radius.
+
+
+
+
+To help people recognize and trust location buttons, you can’t customize the button’s other visual attributes. The system also ensures a location button remains legible by warning you about problems like low-contrast color combinations or too much translucency. In addition to fixing such problems, you’re responsible for making sure the text fits in the button — for example, button text needs to fit without truncation at all accessibility text sizes and when translated into other languages.
+
+Important
+
+If the system identifies consistent problems with your customized location button, it won’t give your app access to the device location when people tap it. Although such a button can perform other app-specific actions, people may lose trust in your app if your location button doesn’t work as they expect.
+
+## [Protecting data](https://developer.apple.com/design/human-interface-guidelines/privacy#Protecting-data)
+
+Protecting people’s information is paramount. Give people confidence in your app’s security and help preserve their privacy by taking advantage of system-provided security technologies when you need to store information locally, authorize people for specific operations, and transport information across a network.
+
+Here are some high-level guidelines.
+
+**Avoid relying solely on passwords for authentication.** Where possible, use [passkeys](https://developer.apple.com/documentation/authenticationservices/public-private_key_authentication/supporting_passkeys/) to replace passwords. If you need to continue using passwords for authentication, augment security by requiring two-factor authentication (for developer guidance, see [Securing Logins with iCloud Keychain Verification Codes](https://developer.apple.com/documentation/AuthenticationServices/securing-logins-with-icloud-keychain-verification-codes)). To further protect access to apps that people keep logged in on their device, use biometric identification like Face ID, Optic ID, or Touch ID. For developer guidance, see [Local Authentication](https://developer.apple.com/documentation/LocalAuthentication).
+
+**Store sensitive information in a keychain.** A keychain provides a secure, predictable user experience when handling someone’s private information. For developer guidance, see [Keychain services](https://developer.apple.com/documentation/Security/keychain-services).
+
+**Never store passwords or other secure content in plain-text files.** Even if you restrict access using file permissions, sensitive information is much safer in an encrypted keychain.
+
+**Avoid inventing custom authentication schemes.** If your app requires authentication, prefer system-provided features like [passkeys](https://developer.apple.com/documentation/authenticationservices/public-private_key_authentication/supporting_passkeys/), [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple) or [Password AutoFill](https://developer.apple.com/documentation/Security/password-autofill). For related guidance, see [Managing accounts](https://developer.apple.com/design/human-interface-guidelines/managing-accounts).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/privacy#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, or watchOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/privacy#macOS)
+
+**Sign your app with a valid Developer ID.** If you choose to distribute your app outside the store, signing your app with Developer ID identifies you as an Apple developer and confirms that your app is safe to use. For developer guidance, see [Xcode Help](https://developer.apple.com/go/?id=ios-app-distribution-guide).
+
+**Protect people’s data with app sandboxing.** Sandboxing provides your app with access to system resources and user data while protecting it from malware. All apps submitted to the Mac App Store require sandboxing. For developer guidance, see [Configuring the macOS App Sandbox](https://developer.apple.com/documentation/Xcode/configuring-the-macos-app-sandbox).
+
+**Avoid making assumptions about who is signed in.** Because of fast user switching, multiple people may be active on the same system.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/privacy#visionOS)
+
+By default, visionOS uses ARKit algorithms to handle features like persistence, world mapping, segmentation, matting, and environment lighting. These algorithms are always running, allowing apps and games to automatically benefit from ARKit while in the Shared Space.
+
+ARKit doesn’t send data to apps in the Shared Space; to access ARKit APIs, your app must open a Full Space. Additionally, features like Plane Estimation, Scene Reconstruction, Image Anchoring, and Hand Tracking require people’s permission to access any information. For developer guidance, see [Setting up access to ARKit data](https://developer.apple.com/documentation/visionOS/setting-up-access-to-arkit-data).
+
+In visionOS, user input is private by design. The system automatically displays hover effects when people look at interactive components you create using SwiftUI or RealityKit, giving people the visual feedback they need without exposing where they’re looking before they tap. For guidance, see [Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes) and [Gestures > visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS).
+
+Developer access to device cameras works differently in visionOS than it does in other platforms. Specifically, the back camera provides blank input and is only available as a compatibility convenience; the front camera provides input for [spatial Personas](https://developer.apple.com/design/human-interface-guidelines/shareplay#visionOS), but only after people grant their permission. If the iOS or iPadOS app you’re bringing to visionOS includes a feature that needs camera access, remove it or replace it with an option for people to import content instead. For developer guidance, see [Making your existing app compatible with visionOS](https://developer.apple.com/documentation/visionOS/making-your-app-compatible-with-visionos).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/privacy#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/privacy#Related)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+[Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/privacy#Developer-documentation)
+
+[Requesting access to protected resources](https://developer.apple.com/documentation/UIKit/requesting-access-to-protected-resources) — UIKit
+
+[Security](https://developer.apple.com/documentation/Security)
+
+[Requesting authorization to use location services](https://developer.apple.com/documentation/CoreLocation/requesting-authorization-to-use-location-services) — CoreLocation
+
+[App Tracking Transparency](https://developer.apple.com/documentation/AppTrackingTransparency)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/privacy#Videos)
+
+[ Integrate privacy into your development process ](https://developer.apple.com/videos/play/wwdc2025/246)
+
+[ What’s new in passkeys ](https://developer.apple.com/videos/play/wwdc2025/279)
+
+[ What’s new in privacy ](https://developer.apple.com/videos/play/wwdc2024/10123)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/privacy#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Consolidated guidance into new page and updated for visionOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/right-to-left.md b/web-app/public/skills/hig-foundations/references/right-to-left.md
new file mode 100644
index 00000000..73347391
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/right-to-left.md
@@ -0,0 +1,206 @@
+---
+title: "Right to left | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/right-to-left
+
+# Right to left
+
+Support right-to-left languages like Arabic and Hebrew by reversing your interface as needed to match the reading direction of the related scripts.
+
+
+
+When people choose a language for their device — or just your app or game — they expect the interface to adapt in various ways (to learn more, see [Localization](https://developer.apple.com/localization/)).
+
+System-provided UI frameworks support right-to-left (RTL) by default, allowing system-provided UI components to flip automatically in the RTL context. If you use system-provided elements and standard layouts, you might not need to make any changes to your app’s automatically reversed interface.
+
+If you want to fine-tune your layout or enhance specific localizations to adapt to different currencies, numerals, or mathematical symbols that can occur in various locales in countries that use RTL languages, follow these guidelines.
+
+## [Text alignment](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Text-alignment)
+
+**Adjust text alignment to match the interface direction, if the system doesn’t do so automatically.** For example, if you left-align text with content in the left-to-right (LTR) context, right-align the text to match the content’s mirrored position in the RTL context.
+
+Left-aligned text in the LTR context
+
+Right-aligned content in the RTL context
+
+**Align a paragraph based on its language, not on the current context.** When the alignment of a paragraph — defined as three or more lines of text — doesn’t match its language, it can be difficult to read. For example, right-aligning a paragraph that consists of LTR text can make the beginning of each line difficult to see. To improve readability, continue aligning one- and two-line text blocks to match the reading direction of the current context, but align a paragraph to match its language.
+
+A left-aligned paragraph in the RTL context
+
+
+
+A right-aligned paragraph in the RTL context
+
+
+
+**Use a consistent alignment for all text items in a list.** To ensure a comfortable reading and scanning experience, reverse the alignment of all items in a list, including items that are displayed in a different script.
+
+Right-aligned content in the RTL context
+
+
+
+Mixed alignment in the RTL content
+
+
+
+## [Numbers and characters](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Numbers-and-characters)
+
+Different RTL languages can use different number systems. For example, Hebrew text uses Western Arabic numerals, whereas Arabic text might use either Western or Eastern Arabic numerals. The use of Western and Eastern Arabic numerals varies among countries and regions and even among areas within the same country or region.
+
+If your app covers mathematical concepts or other number-centric topics, it’s a good idea to identify the appropriate way to display such information in each locale you support. In contrast, apps that don’t address number-related topics can generally rely on system-provided number representations.
+
+Western Arabic numerals
+
+Eastern Arabic numerals
+
+**Don’t reverse the order of numerals in a specific number.** Regardless of the current language or the surrounding content, the digits in a specific number — such as “541,” a phone number, or a credit card number — always appear in the same order.
+
+Latin
+
+Hebrew
+
+Arabic (Western Arabic numerals)
+
+Arabic (Eastern Arabic numerals)
+
+**Reverse the order of numerals that show progress or a counting direction; never flip the numerals themselves.** Controls like progress bars, sliders, and rating controls often include numerals to clarify their meaning. If you use numerals in this way, be sure to reverse the order of the numerals to match the direction of the flipped control. Also reverse a sequence of numerals if you use the sequence to communicate a specific order.
+
+Latin
+
+Arabic (Eastern Arabic numerals)
+
+Hebrew
+
+Arabic (Western Arabic numerals)
+
+## [Controls](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Controls)
+
+**Flip controls that show progress from one value to another.** Because people tend to view forward progress as moving in the same direction as the language they read, it makes sense to flip controls like sliders and progress indicators in the RTL context. When you do this, also be sure to reverse the positions of the accompanying glyphs or images that depict the beginning and ending values of the control.
+
+A directional control in the LTR context
+
+A directional control in the RTL context
+
+**Flip controls that help people navigate or access items in a fixed order.** For example, in the RTL context, a back button must point to the right so the flow of screens matches the reading order of the RTL language. Similarly, next or previous buttons that let people access items in an ordered list need to flip in the RTL context to match the reading order.
+
+**Preserve the direction of a control that refers to an actual direction or points to an onscreen area.** For example, if you provide a control that means “to the right,” it must always point right, regardless of the current context.
+
+**Visually balance adjacent Latin and RTL scripts when necessary.** In buttons, labels, and titles, Arabic or Hebrew text can appear too small when next to uppercased Latin text, because Arabic and Hebrew don’t include uppercase letters. To visually balance Arabic or Hebrew text with Latin text that uses all capitals, it often works well to increase the RTL font size by about 2 points.
+
+Arabic and Hebrew text can look too small next to uppercased Latin text of the same font size.
+
+You can slightly increase the font size of Arabic and Hebrew text to visually balance uppercased Latin text.
+
+## [Images](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Images)
+
+**Avoid flipping images like photographs, illustrations, and general artwork.** Flipping an image often changes the image’s meaning; flipping a copyrighted image could be a violation. If an image’s content is strongly connected to reading direction, consider creating a new version of the image instead of flipping the original.
+
+
+
+
+
+
+
+
+
+**Reverse the positions of images when their order is meaningful.** For example, if you display multiple images in a specific order like chronological, alphabetical, or favorite, reverse their positions to preserve the order’s meaning in the RTL context.
+
+Items with meaningful positions in the LTR context
+
+Items with meaningful positions in the RTL context
+
+## [Interface icons](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Interface-icons)
+
+When you use [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) to supply interface icons for your app, you get variants for the RTL context and localized symbols for Arabic and Hebrew, among other languages. If you create custom symbols, you can specify their directionality. For developer guidance, see [Creating custom symbol images for your app](https://developer.apple.com/documentation/UIKit/creating-custom-symbol-images-for-your-app).
+
+LTR variants of directional symbols
+
+RTL variants of directional symbols
+
+**Flip interface icons that represent text or reading direction.** For example, if an interface icon uses left-aligned bars to represent text in the LTR context, right-align the bars in the RTL context.
+
+LTR variant of a symbol that represents text
+
+RTL variant of a symbol that represents text
+
+**Consider creating a localized version of an interface icon that displays text.** Some interface icons include letters or words to help communicate a script-related concept, like font-size choice or a signature. If you have a custom interface icon that needs to display actual text, consider creating a localized version. For example, SF Symbols offers different versions of the signature, rich-text, and I-beam pointer symbols for use with Latin, Hebrew, and Arabic text, among others.
+
+Latin
+
+Hebrew
+
+Arabic
+
+If you have a custom interface icon that uses letters or words to communicate a concept unrelated to reading or writing, consider designing an alternative image that doesn’t use text.
+
+**Flip an interface icon that shows forward or backward motion.** When something moves in the same direction that people read, they typically interpret that direction as forward; when something moves in the opposite direction, people tend to interpret the direction as backward. An interface icon that depicts an object moving forward or backward needs to flip in the RTL context to preserve the meaning of the motion. For example, an icon that represents a speaker typically shows sound waves emanating forward from the speaker. In the LTR context, the sound waves come from the left, so in the RTL context, the icon needs to flip to show the waves coming from the right.
+
+LTR variant of a symbol that depicts forward motion
+
+RTL variant of a symbol that depicts forward motion
+
+**Don’t flip logos or universal signs and marks.** Displaying a flipped logo confuses people and can have legal repercussions. Always display a logo in its original form, even if it includes text. People expect universal symbols and marks like the checkmark to have a consistent appearance, so avoid flipping them.
+
+A logo
+
+A universal symbol or mark
+
+**In general, avoid flipping interface icons that depict real-world objects.** Unless you use the object to indicate directionality, it’s best to avoid flipping an icon that represents a familiar item. For example, clocks work the same everywhere, so a traditional clock interface icon needs to look the same regardless of language direction. Some interface icons might seem to reference language or reading direction because they represent items that are slanted for right-handed use. However, most people are right-handed, so flipping an icon that shows a right-handed tool isn’t necessary and might be confusing.
+
+
+
+
+
+
+
+**Before merely flipping a complex custom interface icon, consider its individual components and the overall visual balance.** In some cases, a component — like a badge, slash, or magnifying glass — needs to adhere to a visual design language regardless of localization. For example, SF Symbols maintains visual consistency by using the same backslash to represent the prohibition or negation of a symbol’s meaning in both LTR and RTL versions.
+
+LTR variant of a symbol that includes a backslash
+
+RTL variant of a symbol that includes a backslash
+
+In other cases, you might need to flip a component (or its position) to ensure the localized version of the icon still makes sense. For example, if a badge represents the actual UI that people see in your app, it needs to flip if your UI flips. Alternatively, if a badge modifies the meaning of an interface icon, consider whether flipping the badge preserves both the modified meaning and the overall visual balance of the icon. In the images shown below, the badge doesn’t depict an object in the UI, but keeping it in the top-right corner visually unbalances the cart.
+
+
+
+
+
+
+
+
+
+
+
+
+
+If your custom interface icon includes a component that can imply handedness, like a tool, consider preserving the orientation of the tool while flipping the base image if necessary.
+
+LTR variant of a symbol that depicts a tool
+
+RTL variant of a symbol that depicts a tool
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Developer-documentation)
+
+[Localization](https://developer.apple.com/localization/)
+
+[Preparing views for localization](https://developer.apple.com/documentation/SwiftUI/Preparing-views-for-localization) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Videos)
+
+[ Enhance your app’s multilingual experience ](https://developer.apple.com/videos/play/wwdc2025/222)
+
+[ Design for Arabic ](https://developer.apple.com/videos/play/wwdc2022/10034)
+
diff --git a/web-app/public/skills/hig-foundations/references/sf-symbols.md b/web-app/public/skills/hig-foundations/references/sf-symbols.md
new file mode 100644
index 00000000..881debfd
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/sf-symbols.md
@@ -0,0 +1,310 @@
+---
+title: "SF Symbols | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/sf-symbols
+
+# SF Symbols
+
+SF Symbols provides thousands of consistent, highly configurable symbols that integrate seamlessly with the San Francisco system font, automatically aligning with text in all weights and sizes.
+
+
+
+You can use a symbol to convey an object or concept wherever interface icons can appear, such as in toolbars, tab bars, context menus, and within text.
+
+Availability of individual symbols and features varies based on the version of the system you’re targeting. Symbols and symbol features introduced in a given year aren’t available in earlier operating systems.
+
+Visit [SF Symbols](https://developer.apple.com/sf-symbols/) to download the app and browse the full set of symbols. Be sure to understand the terms and conditions for using SF Symbols, including the prohibition against using symbols — or images that are confusingly similar — in app icons, logos, or any other trademarked use. For developer guidance, see [Configuring and displaying symbol images in your UI](https://developer.apple.com/documentation/UIKit/configuring-and-displaying-symbol-images-in-your-ui).
+
+## [Rendering modes](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Rendering-modes)
+
+SF Symbols provides four rendering modes — monochrome, hierarchical, palette, and multicolor — that give you multiple options when applying color to symbols. For example, you might want to use multiple opacities of your app’s accent color to give symbols depth and emphasis, or specify a palette of contrasting colors to display symbols that coordinate with various color schemes.
+
+To support the rendering modes, SF Symbols organizes a symbol’s paths into distinct layers. For example, the `cloud.sun.rain.fill` symbol consists of three layers: the primary layer contains the cloud paths, the secondary layer contains the paths that define the sun and its rays, and the tertiary layer contains the raindrop paths.
+
+Primary
+
+Secondary
+
+Tertiary
+
+Depending on the rendering mode you choose, a symbol can produce various appearances. For example, Hierarchical rendering mode assigns a different opacity of a single color to each layer, creating a visual hierarchy that gives depth to the symbol.
+
+
+
+To learn more about supporting rendering modes in custom symbols, see [Custom symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Custom-symbols).
+
+SF Symbols supports the following rendering modes.
+
+**Monochrome** — Applies one color to all layers in a symbol. Within a symbol, paths render in the color you specify or as a transparent shape within a color-filled path.
+
+
+
+**Hierarchical** — Applies one color to all layers in a symbol, varying the color’s opacity according to each layer’s hierarchical level.
+
+
+
+**Palette** — Applies two or more colors to a symbol, using one color per layer. Specifying only two colors for a symbol that defines three levels of hierarchy means the secondary and tertiary layers use the same color.
+
+
+
+**Multicolor** — Applies intrinsic colors to some symbols to enhance meaning. For example, the `leaf` symbol uses green to reflect the appearance of leaves in the physical world, whereas the `trash.slash` symbol uses red to signal data loss. Some multicolor symbols include layers that can receive other colors.
+
+
+
+Regardless of rendering mode, using system-provided colors ensures that symbols automatically adapt to accessibility accommodations and appearance modes like vibrancy and Dark Mode. For developer guidance, see [renderingMode(_:)](https://developer.apple.com/documentation/swiftui/image/renderingmode\(_:\)).
+
+**Confirm that a symbol’s rendering mode works well in every context.** Depending on factors like the size of a symbol and its contrast with the current background color, different rendering modes can affect how well people can discern the symbol’s details. You can use the automatic setting to get a symbol’s preferred rendering mode, but it’s still a good idea to check the results for places where a different rendering mode might improve a symbol’s legibility.
+
+## [Gradients](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Gradients)
+
+In SF Symbols 7 and later, gradient rendering generates a smooth linear gradient from a single source color. You can use gradients across all rendering modes for both system and custom colors and for custom symbols. Gradients render for symbols of any size, but look best at larger sizes.
+
+Solid fill
+
+Gradient fill
+
+## [Variable color](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Variable-color)
+
+With variable color, you can represent a characteristic that can change over time — like capacity or strength — regardless of rendering mode. To visually communicate such a change, variable color applies color to different layers of a symbol as a value reaches different thresholds between zero and 100 percent.
+
+For example, you could use variable color with the `speaker.wave.3` symbol to communicate three different ranges of sound — plus the state where there’s no sound — by mapping the layers that represent the curved wave paths to different ranges of decibel values. In the case of no sound, no wave layers get color. In all other cases, a wave layer receives color when the sound reaches a threshold the system defines based on the number of nonzero states you want to represent.
+
+
+
+Sometimes, it can make sense for some of a symbol’s layers to opt out of variable color. For example, in the `speaker.wave.3` symbol shown above, the layer that contains the speaker path doesn’t receive variable color because a speaker doesn’t change as the sound level changes. A symbol can support variable color in any number of layers.
+
+**Use variable color to communicate change — don’t use it to communicate depth.** To convey depth and visual hierarchy, use Hierarchical rendering mode to elevate certain layers and distinguish foreground and background elements in a symbol.
+
+## [Weights and scales](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Weights-and-scales)
+
+SF Symbols provides symbols in a wide range of weights and scales to help you create adaptable designs.
+
+
+
+Each of the nine symbol weights — from ultralight to black — corresponds to a weight of the San Francisco system font, helping you achieve precise weight matching between symbols and adjacent text, while supporting flexibility for different sizes and contexts.
+
+Each symbol is also available in three scales: small, medium (the default), and large. The scales are defined relative to the cap height of the San Francisco system font.
+
+Small
+
+Medium
+
+Large
+
+Specifying a scale lets you adjust a symbol’s emphasis compared to adjacent text, without disrupting the weight matching with text that uses the same point size. For developer guidance, see [`imageScale(_:)`](https://developer.apple.com/documentation/SwiftUI/View/imageScale\(_:\)) (SwiftUI), [`UIImage.SymbolScale`](https://developer.apple.com/documentation/UIKit/UIImage/SymbolScale) (UIKit), and [`NSImage.SymbolConfiguration`](https://developer.apple.com/documentation/AppKit/NSImage/SymbolConfiguration-swift.class) (AppKit).
+
+## [Design variants](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Design-variants)
+
+SF Symbols defines several design variants — such as fill, slash, and enclosed — that can help you communicate precise states and actions while maintaining visual consistency and simplicity in your UI. For example, you could use the slash variant of a symbol to show that an item or action is unavailable, or use the fill variant to indicate selection.
+
+Outline is the most common variant in SF Symbols. An outlined symbol has no solid areas, resembling the appearance of text. Most symbols are also available in a fill variant, in which the areas within some shapes are solid.
+
+In addition to outline and fill, SF Symbols also defines variants that include a slash or enclose a symbol within a shape like a circle, square, or rectangle. In many cases, enclosed and slash variants can combine with outline or fill variants.
+
+
+
+SF Symbols provides many variants for specific languages and writing systems, including Latin, Arabic, Hebrew, Hindi, Thai, Chinese, Japanese, Korean, Cyrillic, Devanagari, and several Indic numeral systems. Language- and script-specific variants adapt automatically when the device language changes. For guidance, see [Images](https://developer.apple.com/design/human-interface-guidelines/right-to-left#Images).
+
+
+
+Symbol variants support a range of design goals. For example:
+
+ * The outline variant works well in toolbars, lists, and other places where you display a symbol alongside text.
+
+ * Symbols that use an enclosing shape — like a square or circle — can improve legibility at small sizes.
+
+ * The solid areas in a fill variant tend to give a symbol more visual emphasis, making it a good choice for iOS tab bars and swipe actions and places where you use an accent color to communicate selection.
+
+
+
+
+In many cases, the view that displays a symbol determines whether to use outline or fill, so you don’t have to specify a variant. For example, an iOS tab bar prefers the fill variant, whereas a toolbar takes the outline variant.
+
+## [Animations](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Animations)
+
+SF Symbols provides a collection of expressive, configurable animations that enhance your interface and add vitality to your app. Symbol animations help communicate ideas, provide feedback in response to people’s actions, and signal changes in status or ongoing activities.
+
+Animations work on all SF Symbols in the library, in all rendering modes, weights, and scales, and on custom symbols. For considerations when animating custom symbols, see [Custom symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Custom-symbols). You can control the playback of an animation, whether you want the animation to run from start to finish, or run indefinitely, repeating its effect until a condition is met. You can customize behaviors, like changing the playback speed of an animation or determining whether to reverse an animation before repeating it. For developer guidance, see [Symbols](https://developer.apple.com/documentation/Symbols) and [`SymbolEffect`](https://developer.apple.com/documentation/Symbols/SymbolEffect).
+
+**Appear** — Causes a symbol to gradually emerge into view.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same appear animation effect applied to each. In each animation, the symbol layers gradually animate into view. From the left, the symbols are an antenna with radio waves that animate from the center outward, a photo stack with lines representing a stack animating from the bottom to the top, and a waveform animating from left to right.
+
+Play
+
+**Disappear** — Causes a symbol to gradually recede out of view.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same disappear animation effect applied to each. In each animation, all the symbol layers gradually animate out of view. From the left, the symbols are a folder with a badge plus icon, two overlapping lightbulbs, and two overlapping chat bubbles
+
+Play
+
+**Bounce** — Briefly scales a symbol with an elastic-like movement that goes either up or down and then returns to the symbol’s initial state. The bounce animation plays once by default and can help communicate that an action occurred or needs to take place.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same bounce animation effect applied to each. In each animation, the symbol layers individually bounce. From the left, the symbols are a music note with three lines, text that reads haha, and the Live Photos icon.
+
+Play
+
+**Scale** — Changes the size of a symbol, increasing or decreasing its scale. Unlike the bounce animation, which returns the symbol to its original state, the scale animation persists until you set a new scale or remove the effect. You might use the scale animation to draw people’s attention to a selected item or as feedback when people choose a symbol.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same scale animation effect applied to each. In each animation, the symbol decreases in size, and after a pause, increases back to the original size. From the left, the symbols are a PIP exit window, a 3D stack of three diagonally positioned squares, and an overlapping HomePod and HomePod mini.
+
+Play
+
+**Pulse** — Varies the opacity of a symbol over time. This animation automatically pulses only the layers within a symbol that are annotated to pulse, and optionally can pulse all layers within a symbol. You might use the pulse animation to communicate ongoing activity, playing it continuously until a condition is met.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same pulse animation effect applied to each. In each animation, one layer pulses its opacity. From the left, the symbols are the AirPlay icon with a pulsing screen, a chat bubble with a waveform that is overlapped with a pulsing pause button, and a pulsing rectangle to represent a screen that is overlapped with a person icon.
+
+Play
+
+**Variable color** — Incrementally varies the opacity of layers within a symbol. This animation can be cumulative or iterative. When cumulative, color changes persist for each layer until the animation cycle is complete. When iterative, color changes occur one layer at a time. You might use variable color to communicate progress or ongoing activity, such as playback, connecting, or broadcasting. You can customize the animation to autoreverse — meaning reverse the animation to the starting point and replay the sequence — as well as hide inactive layers rather than reduce their opacity.
+
+The arrangement of layers within a symbol determines how variable color behaves during a repeating animation. Symbols with layers that are arranged linearly where the start and end points don’t meet are annotated as _open loop_. Symbols with layers that follow a complete shape where the start and end points do meet, like in a circular progress indicator, are annotated as _closed loop_. Variable color animations for symbols with closed loop designs feature seamless, continuous playback.
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same variable color animation effect applied to each. In each animation, color is added one path at a time. From the left, the symbols are a speaker with color cycling through three sound waves, a Wi-Fi symbol with color cycling through two paths that represent signal strength before reversing and replaying the animation, and a sprinkler icon with color cycling through droplets.
+
+Play
+
+**Replace** — Replaces one symbol with another. The replace animation works between arbitrary symbols and across all weights and rendering modes. This animation features three configurations:
+
+ * Down-up, where the outgoing symbol scales down and the incoming symbol scales up, communicating a change in state.
+
+ * Up-up, where both the outgoing and incoming symbols scale up. This configuration communicates a change in state that includes a sense of forward progression.
+
+ * Off-up, where the outgoing symbol hides immediately and the incoming symbol scales up. This configuration communicates a state change that emphasizes the next available state or action.
+
+
+
+
+Video with custom controls.
+
+Content description: A video showing three symbols with the same replace animation effect applied to each. In each animation, one symbol is replaced by a new symbol, and then replaced by the original symbol. From the left, the symbols are a grid of four squares replaced by a bulleted list, a cloud with rain replaced by a cloud partly blocking the sun, and microphone symbol replaced by an x symbol in a circle.
+
+Play
+
+From left to right: down-up, up-up, off-up
+
+**Magic Replace** — Performs a smart transition between two symbols with related shapes. For example, slashes can draw on and off, and badges can appear or disappear, or you can replace them independently of the base symbol. Magic Replace is the new default replace animation, but doesn’t occur between unrelated symbols; the default down-up animation occurs instead. You can choose a custom direction for the fallback animation in these situations if you prefer one other than the default.
+
+Video with custom controls.
+
+Content description: A video showing three symbols each with a shape being added, removed, or replaced using the Magic Replace animation effect. In each animation, the symbol is transformed, and then the transformation is reverted. From the left, the symbols are a credit card with a triangle caution shape added, a microphone with a diagonal slash added, and a circular ID with a checkmark badge replaced by an X badge.
+
+Play
+
+**Wiggle** — Moves the symbol back and forth along a directional axis. You might use the wiggle animation to highlight a change or a call to action that a person might overlook. Wiggle can also add a dynamic emphasis to an interaction or reinforce what the symbol is representing, such as when an arrow points in a specific direction.
+
+Video with custom controls.
+
+Content description: A video showing three symbols that wiggle laterally, rotationally, or along a linear axis. From the left, the symbols are an arrow pointing down at a container that wiggles vertically; a stack of two photos that wiggles rotationally; and a top-down car between two lane markers with arrows pointing inward that wiggles horizontally.
+
+Play
+
+**Breathe** — Smoothly increases and decreases the presence of a symbol, giving it a living quality. You might use the breathe animation to convey status changes, or signal that an activity is taking place, like an ongoing recording session. Breathe is similar to pulse; however pulse animates by changing opacity alone, while breathe changes both opacity and size to convey ongoing activity.
+
+Video with custom controls.
+
+Content description: A video showing three symbols that breathe in and out, growing and shrinking in size and changing opacity in a smooth rhythm. From the left, the symbols are a stylized waveform of vertical lines that expand and contract from left to right with a pulse of variable opacity; a pair of translation word bubbles that grow with reduced opacity, then shrink with increased opacity; and three concentric mindfulness rings that pulse outward with reduced opacity, then inward with increased opacity.
+
+Play
+
+**Rotate** — Rotates the symbol to act as a visual indicator or imitate an object’s behavior in the real world. For example, when a task is in progress, rotation confirms that it’s working as expected. The rotate animation causes some symbols to rotate entirely, while in others only certain parts of the symbol rotate. Symbols like the desk fan, for example, use the By Layer rotation option to spin only the fan blades.
+
+Video with custom controls.
+
+Content description: A video showing three symbols that either rotate completely or contain a rotating shape. From the left, the symbols are a rotating gear; a desk fan with rotating fan blades; and two dots rotating on concentric orbital paths around a center circle.
+
+Play
+
+**Draw On / Draw Off** — In SF Symbols 7 and later, draws the symbol along a path through a set of guide points, either from offscreen to onscreen (Draw On) or from onscreen to offscreen (Draw Off). You can draw all layers at once, stagger them, or draw each layer one at a time. You might use the draw animation to convey progress, as with a download, or to reinforce the meaning of a symbol, like a directional arrow.
+
+**Apply symbol animations judiciously.** While there’s no limit to how many animations you can add to a view, too many animations can overwhelm an interface and distract people.
+
+**Make sure that animations serve a clear purpose in communicating a symbol’s intent.** Each type of animation has a discrete movement that communicates a certain type of action or elicits a certain response. Consider how people might interpret an animated symbol and whether the animation, or combination of animations, might be confusing.
+
+**Use symbol animations to communicate information more efficiently.** Animations provide visual feedback, reinforcing that something happened in your interface. You can use animations to present complex information in a simple way and without taking up a lot of visual space.
+
+**Consider your app’s tone when adding animations.** When animating a symbol, think about what the animation can convey and how that might align with your brand identity and your app’s overall style and tone. For guidance, see [Branding](https://developer.apple.com/design/human-interface-guidelines/branding).
+
+## [Custom symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Custom-symbols)
+
+If you need a symbol that SF Symbols doesn’t provide, you can create your own. To create a custom symbol, first export the template for a symbol that’s similar to the design you want, then use a vector-editing tool to modify it. For developer guidance, see [Creating custom symbol images for your app](https://developer.apple.com/documentation/UIKit/creating-custom-symbol-images-for-your-app).
+
+Important
+
+SF Symbols includes copyrighted symbols that depict Apple products and features. You can display these symbols in your app, but you can’t customize them. To help you identify a noncustomizable symbol, the SF Symbols app badges it with an Info icon; to help you use the symbol correctly, the inspector pane describes its usage restrictions.
+
+Using a process called _annotating_ , you can assign a specific color — or a specific hierarchical level, such as primary, secondary, or tertiary — to each layer in a custom symbol. Depending on the rendering modes you support, you can use a different mode in each instance of the symbol in your app.
+
+**Use the template as a guide.** Create a custom symbol that’s consistent with the ones the system provides in level of detail, optical weight, alignment, position, and perspective. Strive to design a symbol that is:
+
+ * Simple
+
+ * Recognizable
+
+ * Inclusive
+
+ * Directly related to the action or content it represents
+
+
+
+
+For guidance, see [Icons](https://developer.apple.com/design/human-interface-guidelines/icons).
+
+**Assign negative side margins to your custom symbol if necessary.** SF Symbols supports negative side margins to aid optical horizontal alignment when a symbol contains a badge or other elements that increase its width. For example, negative side margins can help you horizontally align a stack of folder symbols, some of which include a badge. The name of each margin includes the relevant configuration — such as “left-margin-Regular-M” — so be sure to use this naming pattern if you add margins to your custom symbols.
+
+**Optimize layers to use animations with custom symbols.** If you want to animate your symbol by layer, make sure to annotate the layers in the SF Symbols app. The Z-order determines the order that you want to apply colors to the layers of a variable color symbol, and you can choose whether to animate those changes from front-to-back, or back-to-front. You can also animate by layer groups to have related layers move together.
+
+**Test animations for custom symbols.** It’s important to test your custom symbols with all of the animation presets because the shapes and paths might not appear how you expect when the layers are in motion. To get the most out of this feature, consider drawing your custom symbols with whole shapes. For example, a custom symbol similar to the `person.2.fill` symbol doesn’t need to create a cutout for the shape representing the person on the left. Instead, you can draw the full shape of the person, and in addition to that, draw an offset path of the person on the right to help represent the gap between them. You can later annotate this offset path as an erase layer to render the symbol as you want. This method of drawing helps preserve additional layer information that allows for animations to perform as you expect.
+
+**Avoid making custom symbols that include common variants, such as enclosures or badges.** The SF Symbols app offers a component library for creating variants of your custom symbol. Using the component library allows you to create commonly used variants of your custom symbol while maintaining design consistency with the included SF Symbols.
+
+**Provide alternative text labels for custom symbols.** Alternative text labels — or accessibility descriptions — let VoiceOver describe visible UI and content, making navigation easier for people with visual disabilities. For guidance, see [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover).
+
+**Don’t design replicas of Apple products.** Apple products are copyrighted and you can’t reproduce them in your custom symbols. Also, you can’t customize a symbol that SF Symbols identifies as representing an Apple feature or product.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Related)
+
+[Download SF Symbols](https://developer.apple.com/sf-symbols/)
+
+[Typography](https://developer.apple.com/design/human-interface-guidelines/typography)
+
+[Icons](https://developer.apple.com/design/human-interface-guidelines/icons)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Developer-documentation)
+
+[Symbols](https://developer.apple.com/documentation/Symbols) — Symbols framework
+
+[Configuring and displaying symbol images in your UI](https://developer.apple.com/documentation/UIKit/configuring-and-displaying-symbol-images-in-your-ui) — UIKit
+
+[Creating custom symbol images for your app](https://developer.apple.com/documentation/UIKit/creating-custom-symbol-images-for-your-app) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Videos)
+
+[ What’s new in SF Symbols 7 ](https://developer.apple.com/videos/play/wwdc2025/337)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/sf-symbols#Change-log)
+
+Date| Changes
+---|---
+July 28, 2025| Updated with guidance for Draw animations and gradient rendering in SF Symbols 7.
+June 10, 2024| Updated with guidance for new animations and features of SF Symbols 6.
+June 5, 2023| Added a new section on animations. Included animation guidance for custom symbols.
+September 14, 2022| Added a new section on variable color. Removed instructions on creating custom symbol paths, exporting templates, and layering paths, deferring to developer articles that cover these topics.
+
diff --git a/web-app/public/skills/hig-foundations/references/spatial-layout.md b/web-app/public/skills/hig-foundations/references/spatial-layout.md
new file mode 100644
index 00000000..7e454d8b
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/spatial-layout.md
@@ -0,0 +1,142 @@
+---
+title: "Spatial layout | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/spatial-layout
+
+# Spatial layout
+
+Spatial layout techniques help you take advantage of the infinite canvas of Apple Vision Pro and present your content in engaging, comfortable ways.
+
+
+
+## [Field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view)
+
+A person’s _field of view_ is the space they can see without moving their head. The dimensions of an individual’s field of view while wearing Apple Vision Pro vary based on factors like the way people configure the Light Seal and the extent of their peripheral acuity.
+
+
+
+Important
+
+The system doesn’t provide information about a person’s field of view.
+
+**Center important content within the field of view.** By default, visionOS launches an app directly in front of people, placing it within their field of view. In an immersive experience, you can help people keep their attention on important content by keeping it centered and not displaying distracting motion or bright, high-contrast objects in the periphery.
+
+ * Upright viewing
+ * Angled viewing
+
+
+
+Video with custom controls.
+
+Content description: An animation of a person wearing Apple Vision Pro and sitting upright in a chair. The person is directly facing a square that represents an app window in visionOS that's centered in the person's field of view. A dotted line animates from the person's eyes to the center of the window.
+
+Play
+
+Video with custom controls.
+
+Content description: An animation of a person wearing Apple Vision Pro and reclining in a chair. The person is looking at a square that represents an app window in visionOS. The app window is positioned a short distance from the person, is raised in the air, and is tilted toward the person so it's centered within the person's field of view. A dotted line animates from the person's eyes to the center of the window.
+
+Play
+
+**Avoid anchoring content to the wearer’s head.** Although you generally want your app to stay within the field of view, anchoring content so that it remains statically in front of someone can make them feel stuck, confined, and uncomfortable, especially if the content obscures a lot of passthrough and decreases the apparent stability of their surroundings. Instead, anchor content in people’s space, giving them the freedom to look around naturally and view different objects in different locations.
+
+## [Depth](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Depth)
+
+People rely on visual cues like distance, occlusion, and shadow to perceive depth and make sense of their surroundings. On Apple Vision Pro, the system automatically uses visual effects like color temperature, reflections, and shadow to help people perceive the depth of virtual content. When people move a virtual object in space — or when they change their position relative to that object — the visual effects change the object’s apparent depth, making the experience feel more lifelike.
+
+Because people can view your content from any angle, incorporating small amounts of depth throughout your interface — even in standard windows — can help it look more natural. When you use SwiftUI, the system adds visual effects to views in a 2D window, making them appear to have depth. For developer guidance, see [Adding 3D content to your app](https://developer.apple.com/documentation/visionOS/adding-3d-content-to-your-app).
+
+
+
+If you need to present content with additional depth, you use RealityKit to create a 3D object (for developer guidance, see [RealityKit](https://developer.apple.com/documentation/RealityKit)). You can display the 3D object anywhere, or you can use a _volume_ , which is a component that displays 3D content. A volume is similar to a window, but without a visible frame. For guidance, see [visionOS volumes](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-volumes).
+
+Video with custom controls.
+
+Content description: A recording showing a 3D model of a satellite within a visionOS volume. As the viewer approaches the satellite and manipulates its orientation, light reflections adjust based on the position of the viewer and angle of the satellite.
+
+Play
+
+**Provide visual cues that accurately communicate the depth of your content.** If visual cues are missing or they conflict with a person’s real-world experience, people can experience visual discomfort.
+
+**Use depth to communicate hierarchy.** Depth helps an object appear to stand out from surrounding content, making it more noticeable. People also tend to notice changes in depth: for example, when a sheet appears over a window, the window recedes along the z-axis, allowing the sheet to come forward and become visually prominent.
+
+**In general, avoid adding depth to text.** Text that appears to hover above its background is difficult to read, which slows people down and can sometimes cause vision discomfort.
+
+**Make sure depth adds value.** In general, you want to use depth to clarify and delight — you don’t need to use it everywhere. As you add depth to your design, think about the size and relative importance of objects. Depth is great for visually separating large, important elements in your app, like making a tab bar or toolbar stand out from a window, but it may not work as well on small objects. For example, using depth to make a button’s symbol stand out from its background can make the button less legible and harder to use. Also review how often you use different depths throughout your app. People need to refocus their eyes to perceive each difference in depth, and doing so too often or quickly can be tiring.
+
+## [Scale](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Scale)
+
+visionOS defines two types of scale to preserve the appearance of depth while optimizing usability.
+
+_Dynamic scale_ helps content remain comfortably legible and interactive regardless of its proximity to people. Specifically, visionOS automatically increases a window’s scale as it moves away from the wearer and decreases it as the window moves closer, making the window appear to maintain the same size at all distances.
+
+Video with custom controls.
+
+Content description: An animation that shows a square representing an app window in a 3D space. The square animates to move back along its plane from its initial position. As it moves, it dynamically grows in size. A frame representing the original position remains visible for comparison. After the movement is complete, the entire environment rotates to convey that, from the viewer's angle, the window always remains the same size.
+
+Play
+
+_Fixed scale_ means that an object maintains the same scale regardless of its proximity to people. A fixed-scale object appears smaller when it moves farther from the viewer along the z-axis, similar to the way an object in a person’s physical surroundings looks smaller when it’s far away than it does when it’s close up.
+
+Video with custom controls.
+
+Content description: An animation that shows a square representing an app window in a 3D space. The square animates to move back along its plane from its initial position. As it moves, it becomes smaller. A frame representing the original position remains visible for comparison. After the movement is complete, the entire environment rotates to convey that, from the viewer's angle, the window appears to have receded into the distance.
+
+Play
+
+To support dynamic scaling and the appearance of depth, visionOS defines a point as an angle, in contrast to other platforms, which define a point as a number of pixels that can vary with the [resolution](https://developer.apple.com/design/human-interface-guidelines/images#Resolution) of a 2D display.
+
+**Consider using fixed scale when you want a virtual object to look exactly like a physical object.** For example, you might want to maintain the life-size scale of a product you offer so it can look more realistic when people view it in their space. Because interactive content needs to scale to maintain usability as it gets closer or farther away, prefer applying fixed scale sparingly, reserving it for noninteractive objects that need it.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Best-practices)
+
+**Avoid displaying too many windows.** Too many windows can obscure people’s surroundings, making them feel overwhelmed, constricted, and even uncomfortable. It can also make it cumbersome for people to relocate an app because it means moving a lot of windows.
+
+**Prioritize standard, indirect gestures.** People can make an _indirect_ gesture without moving their hand into their field of view. In contrast, making a _direct_ gesture requires people to touch the virtual object with their finger, which can be tiring, especially when the object is positioned at or above their line of sight. In visionOS, people use indirect gestures to perform the standard gestures they already know. When you prioritize indirect gestures, people can use them to interact with any object they look at, whatever its distance. If you support direct gestures, consider reserving them for nearby objects that invite close inspection or manipulation for short periods of time. For guidance, see [Gestures > visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS).
+
+**Rely on the Digital Crown to help people recenter windows in their field of view.** When people move or turn their head, content might no longer appear where they want it to. If this happens, people can press the [Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown) when they want to recenter content in front of them. Your app doesn’t need to do anything to support this action.
+
+**Include enough space around interactive components to make them easy for people to look at.** When people look at an interactive element, visionOS displays a visual hover effect that helps them confirm the element is the one they want. It’s crucial to include enough space around an interactive component so that looking at it is easy and comfortable, while preventing the hover effect from crowding other content. For example, place multiple, regular-size [buttons](https://developer.apple.com/design/human-interface-guidelines/buttons#visionOS) so their centers are at least 60 points apart, leaving 16 points or more of space between them. Also, don’t let controls overlap other interactive elements or views, because doing so can make selecting a single element difficult.
+
+**Let people use your app with minimal or no physical movement.** Unless some physical movement is essential to your experience, help everyone enjoy it while remaining stationary.
+
+**Use the floor to help you place a large immersive experience.** If your immersive experience includes content that extends up from the floor, place it using a flat horizontal plane. Aligning this plane with the floor can help it blend seamlessly with people’s surroundings and provide a more intuitive experience.
+
+To learn more about windows and volumes in visionOS, see [Windows > visionOS](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS); for guidance on laying content within a window, see [Layout > visionOS](https://developer.apple.com/design/human-interface-guidelines/layout#visionOS).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Related)
+
+[Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Developer-documentation)
+
+[Presenting windows and spaces](https://developer.apple.com/documentation/visionOS/presenting-windows-and-spaces) — visionOS
+
+[Positioning and sizing windows](https://developer.apple.com/documentation/visionOS/positioning-and-sizing-windows) — visionOS
+
+[Adding 3D content to your app](https://developer.apple.com/documentation/visionOS/adding-3d-content-to-your-app) — visionOS
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Videos)
+
+[ Meet SwiftUI spatial layout ](https://developer.apple.com/videos/play/wwdc2025/273)
+
+[ Principles of spatial design ](https://developer.apple.com/videos/play/wwdc2023/10072)
+
+[ Design for spatial user interfaces ](https://developer.apple.com/videos/play/wwdc2023/10076)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Change-log)
+
+Date| Changes
+---|---
+March 29, 2024| Emphasized the importance of keeping interactive elements from overlapping each other.
+June 21, 2023| New page.
+
diff --git a/web-app/public/skills/hig-foundations/references/typography.md b/web-app/public/skills/hig-foundations/references/typography.md
new file mode 100644
index 00000000..2f919329
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/typography.md
@@ -0,0 +1,1146 @@
+---
+title: "Typography | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/typography
+
+# Typography
+
+Your typographic choices can help you display legible text, convey an information hierarchy, communicate important content, and express your brand or style.
+
+
+
+## [Ensuring legibility](https://developer.apple.com/design/human-interface-guidelines/typography#Ensuring-legibility)
+
+**Use font sizes that most people can read easily.** People need to be able to read your content at various viewing distances and under a variety of conditions. Follow the recommended default and minimum text sizes for each platform — for both custom and system fonts — to ensure your text is legible on all devices. Keep in mind that font weight can also impact how easy text is to read. If you use a custom font with a thin weight, aim for larger than the recommended sizes to increase legibility.
+
+Platform| Default size| Minimum size
+---|---|---
+iOS, iPadOS| 17 pt| 11 pt
+macOS| 13 pt| 10 pt
+tvOS| 29 pt| 23 pt
+visionOS| 17 pt| 12 pt
+watchOS| 16 pt| 12 pt
+
+**Test legibility in different contexts.** For example, you need to test game text for legibility on each platform on which your game runs. If testing shows that some of your text is difficult to read, consider using a larger type size, increasing contrast by modifying the text or background colors, or using typefaces designed for optimized legibility, like the system fonts.
+
+
+
+Testing a game on a new platform can show where text is hard to read.
+
+
+
+Increasing text size and adding visible background shapes can help make text easier to read.
+
+**In general, avoid light font weights.** For example, if you’re using system-provided fonts, prefer Regular, Medium, Semibold, or Bold font weights, and avoid Ultralight, Thin, and Light font weights, which can be difficult to see, especially when text is small.
+
+## [Conveying hierarchy](https://developer.apple.com/design/human-interface-guidelines/typography#Conveying-hierarchy)
+
+**Adjust font weight, size, and color as needed to emphasize important information and help people visualize hierarchy.** Be sure to maintain the relative hierarchy and visual distinction of text elements when people adjust text sizes.
+
+**Minimize the number of typefaces you use, even in a highly customized interface.** Mixing too many different typefaces can obscure your information hierarchy and hinder readability, in addition to making an interface feel internally inconsistent or poorly designed.
+
+**Prioritize important content when responding to text-size changes.** Not all content is equally important. When someone chooses a larger text size, they typically want to make the content they care about easier to read; they don’t always want to increase the size of every word on the screen. For example, when people increase text size to read the content in a tabbed window, they don’t expect the tab titles to increase in size. Similarly, in a game, people are often more interested in a character’s dialog than in transient hit-damage values.
+
+## [Using system fonts](https://developer.apple.com/design/human-interface-guidelines/typography#Using-system-fonts)
+
+Apple provides two typeface families that support an extensive range of weights, sizes, styles, and languages.
+
+**San Francisco (SF)** is a sans serif typeface family that includes the SF Pro, SF Compact, SF Arabic, SF Armenian, SF Georgian, SF Hebrew, and SF Mono variants.
+
+
+
+The system also offers SF Pro, SF Compact, SF Arabic, SF Armenian, SF Georgian, and SF Hebrew in rounded variants you can use to coordinate text with the appearance of soft or rounded UI elements, or to provide an alternative typographic voice.
+
+**New York (NY)** is a serif typeface family designed to work well by itself and alongside the SF fonts.
+
+
+
+You can download the San Francisco and New York fonts [here](https://developer.apple.com/fonts/).
+
+The system provides the SF and NY fonts in the _variable_ font format, which combines different font styles together in one file, and supports interpolation between styles to create intermediate ones.
+
+Note
+
+Variable fonts support _optical sizing_ , which refers to the adjustment of different typographic designs to fit different sizes. On all platforms, the system fonts support _dynamic optical sizes_ , which merge discrete optical sizes (like Text and Display) and weights into a single, continuous design, letting the system interpolate each glyph or letterform to produce a structure that’s precisely adapted to the point size. With dynamic optical sizes, you don’t need to use discrete optical sizes unless you’re working with a design tool that doesn’t support all the features of the variable font format.
+
+To help you define visual hierarchies and create clear and legible designs in many different sizes and contexts, the system fonts are available in a variety of weights, ranging from Ultralight to Black, and — in the case of SF — several widths, including Condensed and Expanded. Because SF Symbols use equivalent weights, you can achieve precise weight matching between symbols and adjacent text, regardless of the size or style you choose.
+
+
+
+Note
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) provides a comprehensive library of symbols that integrate seamlessly with the San Francisco system font, automatically aligning with text in all weights and sizes. Consider using symbols when you need to convey a concept or depict an object, especially within text.
+
+The system defines a set of typographic attributes — called text styles — that work with both typeface families. A _text style_ specifies a combination of font weight, point size, and leading values for each text size. For example, the _body_ text style uses values that support a comfortable reading experience over multiple lines of text, while the _headline_ style assigns a font size and weight that help distinguish a heading from surrounding content. Taken together, the text styles form a typographic hierarchy you can use to express the different levels of importance in your content. Text styles also allow text to scale proportionately when people change the system’s text size or make accessibility adjustments, like turning on Larger Text in Accessibility settings.
+
+**Consider using the built-in text styles.** The system-defined text styles give you a convenient and consistent way to convey your information hierarchy through font size and weight. Using text styles with the system fonts also ensures support for Dynamic Type and larger accessibility type sizes (where available), which let people choose the text size that works for them. For guidance, see [Supporting Dynamic Type](https://developer.apple.com/design/human-interface-guidelines/typography#Supporting-Dynamic-Type).
+
+**Modify the built-in text styles if necessary.** System APIs define font adjustments — called _symbolic traits_ — that let you modify some aspects of a text style. For example, the bold trait adds weight to text, letting you create another level of hierarchy. You can also use symbolic traits to adjust leading if you need to improve readability or conserve space. For example, when you display text in wide columns or long passages, more space between lines (_loose leading_) can make it easier for people to keep their place while moving from one line to the next. Conversely, if you need to display multiple lines of text in an area where height is constrained — for example, in a list row — decreasing the space between lines (_tight leading_) can help the text fit well. If you need to display three or more lines of text, avoid tight leading even in areas where height is limited. For developer guidance, see [`leading(_:)`](https://developer.apple.com/documentation/SwiftUI/Font/leading\(_:\)).
+
+Developer note
+
+You can use the constants defined in [`Font.Design`](https://developer.apple.com/documentation/SwiftUI/Font/Design) to access all system fonts — don’t embed system fonts in your app or game. For example, use [`Font.Design.default`](https://developer.apple.com/documentation/SwiftUI/Font/Design/default) to get the system font on all platforms; use [`Font.Design.serif`](https://developer.apple.com/documentation/SwiftUI/Font/Design/serif) to get the New York font.
+
+**If necessary, adjust tracking in interface mockups.** In a running app, the system font dynamically adjusts tracking at every point size. To produce an accurate interface mockup of an interface that uses the variable system fonts, you don’t have to choose a discrete optical size at certain point sizes, but you might need to adjust the tracking. For guidance, see [Tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#Tracking-values).
+
+## [Using custom fonts](https://developer.apple.com/design/human-interface-guidelines/typography#Using-custom-fonts)
+
+**Make sure custom fonts are legible.** People need to be able to read your custom font easily at various viewing distances and under a variety of conditions. While using a custom font, be guided by the recommended minimum font sizes for various styles and weights in [Specifications](https://developer.apple.com/design/human-interface-guidelines/typography#Specifications).
+
+**Implement accessibility features for custom fonts.** System fonts automatically support Dynamic Type (where available) and respond when people turn on accessibility features, such as Bold Text. If you use a custom font, make sure it implements the same behaviors. For developer guidance, see [Applying custom fonts to text](https://developer.apple.com/documentation/SwiftUI/Applying-Custom-Fonts-to-Text). In a Unity-based game, you can use [Apple’s Unity plug-ins](https://github.com/apple/unityplugins) to support Dynamic Type. If the plug-in isn’t appropriate for your game, be sure to let players adjust text size in other ways.
+
+## [Supporting Dynamic Type](https://developer.apple.com/design/human-interface-guidelines/typography#Supporting-Dynamic-Type)
+
+Dynamic Type is a system-level feature in iOS, iPadOS, tvOS, visionOS, and watchOS that lets people adjust the size of visible text on their device to ensure readability and comfort. For related guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+
+
+Mail content at the default text size
+
+
+
+Mail content at the largest accessibility text size
+
+For a list of available Dynamic Type sizes, see [Specifications](https://developer.apple.com/design/human-interface-guidelines/typography#Specifications). You can also download Dynamic Type size tables in the [Apple Design Resources](https://developer.apple.com/design/resources/) for each platform.
+
+For developer guidance, see [Text input and output](https://developer.apple.com/documentation/SwiftUI/Text-input-and-output). To support Dynamic Type in Unity-based games, use [Apple’s Unity plug-ins](https://github.com/apple/unityplugins).
+
+**Make sure your app’s layout adapts to all font sizes.** Verify that your design scales, and that text and glyphs are legible at all font sizes. On iPhone or iPad, turn on Larger Accessibility Text Sizes in Settings > Accessibility > Display & Text Size > Larger Text, and confirm that your app remains comfortably readable.
+
+**Increase the size of meaningful interface icons as font size increases.** If you use interface icons to communicate important information, make sure they’re easy to view at larger font sizes too. When you use [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols), you get icons that scale automatically with Dynamic Type size changes.
+
+**Keep text truncation to a minimum as font size increases.** In general, aim to display as much useful text at the largest accessibility font size as you do at the largest standard font size. Avoid truncating text in scrollable regions unless people can open a separate view to read the rest of the content. You can prevent text truncation in a label by configuring it to use as many lines as needed to display a useful amount of text. For developer guidance, see [`numberOfLines`](https://developer.apple.com/documentation/UIKit/UILabel/numberOfLines).
+
+**Consider adjusting your layout at large font sizes.** When font size increases in a horizontally constrained context, inline items (like glyphs and timestamps) and container boundaries can crowd text and cause truncation or overlapping. To improve readability, consider using a stacked layout where text appears above secondary items. Multicolumn text can also be less readable at large sizes due to horizontal space constraints. Reduce the number of columns when the font size increases to avoid truncation and enhance readability. For developer guidance, see [`isAccessibilityCategory`](https://developer.apple.com/documentation/UIKit/UIContentSizeCategory/isAccessibilityCategory).
+
+**Maintain a consistent information hierarchy regardless of the current font size.** For example, keep primary elements toward the top of a view even when the font size is very large, so that people don’t lose track of these elements.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/typography#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/typography#iOS-iPadOS)
+
+SF Pro is the system font in iOS and iPadOS. iOS and iPadOS apps can also use NY.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/typography#macOS)
+
+SF Pro is the system font in macOS. NY is available for Mac apps built with Mac Catalyst. macOS doesn’t support Dynamic Type.
+
+**When necessary, use dynamic system font variants to match the text in standard controls.** Dynamic system font variants give your text the same look and feel of the text that appears in system-provided controls. Use the variants listed below to achieve a look that’s consistent with other apps on the platform.
+
+Dynamic font variant| API
+---|---
+Control content| [`controlContentFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/controlContentFont\(ofSize:\))
+Label| [`labelFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/labelFont\(ofSize:\))
+Menu| [`menuFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/menuFont\(ofSize:\))
+Menu bar| [`menuBarFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/menuBarFont\(ofSize:\))
+Message| [`messageFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/messageFont\(ofSize:\))
+Palette| [`paletteFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/paletteFont\(ofSize:\))
+Title| [`titleBarFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/titleBarFont\(ofSize:\))
+Tool tips| [`toolTipsFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/toolTipsFont\(ofSize:\))
+Document text (user)| [`userFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/userFont\(ofSize:\))
+Monospaced document text (user fixed pitch)| [`userFixedPitchFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/userFixedPitchFont\(ofSize:\))
+Bold system font| [`boldSystemFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/boldSystemFont\(ofSize:\))
+System font| [`systemFont(ofSize:)`](https://developer.apple.com/documentation/AppKit/NSFont/systemFont\(ofSize:\))
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/typography#tvOS)
+
+SF Pro is the system font in tvOS, and apps can also use NY.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/typography#visionOS)
+
+SF Pro is the system font in visionOS. If you use NY, you need to specify the type styles you want.
+
+visionOS uses bolder versions of the Dynamic Type body and title styles and it introduces Extra Large Title 1 and Extra Large Title 2 for wide, editorial-style layouts. For guidance using vibrancy to indicate hierarchy in text and symbols, see [Materials > visionOS](https://developer.apple.com/design/human-interface-guidelines/materials#visionOS).
+
+**In general, prefer 2D text.** The more visual depth text characters have, the more difficult they can be to read. Although a small amount of 3D text can provide a fun visual element that draws people’s attention, if you’re going to display content that people need to read and understand, prefer using text that has little or no visual depth.
+
+
+
+
+
+
+
+
+
+**Make sure text looks good and remains legible when people scale it.** Use a text style that makes the text look good at full scale, then test it for legibility at different scales.
+
+**Maximize the contrast between text and the background of its container.** By default, the system displays text in white, because this color tends to provide a strong contrast with the default system background material, making text easier to read. If you want to use a different text color, be sure to test it in a variety of contexts.
+
+**If you need to display text that’s not on a background, consider making it bold to improve legibility.** In this situation, you generally want to avoid adding shadows to increase text contrast. The current space might not include a visual surface on which to cast an accurate shadow, and you can’t predict the size and density of shadow that would work well with a person’s current Environment.
+
+**Keep text facing people as much as possible.** If you display text that’s associated with a point in space, such as a label for a 3D object, you generally want to use _billboarding_ — that is, you want the text to face the wearer regardless of how they or the object move. If you don’t rotate text to remain facing the wearer, the text can become impossible to read because people may view it from the side or a highly oblique angle. For example, imagine a virtual lamp that appears to be on a physical desk with a label anchored directly above it. For the text to remain readable, the label needs to rotate around the y-axis as people move around the desk; in other words, the baseline of the text needs to remain perpendicular to the person’s line of sight.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/typography#watchOS)
+
+SF Compact is the system font in watchOS, and apps can also use NY. In complications, watchOS uses SF Compact Rounded.
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/typography#Specifications)
+
+You can display emphasized variants of system text styles using symbolic traits. In SwiftUI, use the [`bold()`](https://developer.apple.com/documentation/SwiftUI/Text/bold\(\)) modifier; in UIKit, use [`traitBold`](https://developer.apple.com/documentation/UIKit/UIFontDescriptor/SymbolicTraits-swift.struct/traitBold) in the [`UIFontDescriptor`](https://developer.apple.com/documentation/UIKit/UIFontDescriptor) API. The emphasized weights can be medium, semibold, bold, or heavy. The following specifications include the emphasized weight for each text style.
+
+### [iOS, iPadOS Dynamic Type sizes](https://developer.apple.com/design/human-interface-guidelines/typography#iOS-iPadOS-Dynamic-Type-sizes)
+
+ * xSmall
+ * Small
+ * Medium
+ * Large (default)
+ * xLarge
+ * xxLarge
+ * xxxLarge
+
+
+
+#### [xSmall](https://developer.apple.com/design/human-interface-guidelines/typography#xSmall)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 31| 38| Bold
+Title 1| Regular| 25| 31| Bold
+Title 2| Regular| 19| 24| Bold
+Title 3| Regular| 17| 22| Semibold
+Headline| Semibold| 14| 19| Semibold
+Body| Regular| 14| 19| Semibold
+Callout| Regular| 13| 18| Semibold
+Subhead| Regular| 12| 16| Semibold
+Footnote| Regular| 12| 16| Semibold
+Caption 1| Regular| 11| 13| Semibold
+Caption 2| Regular| 11| 13| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [Small](https://developer.apple.com/design/human-interface-guidelines/typography#Small)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 32| 39| Bold
+Title 1| Regular| 26| 32| Bold
+Title 2| Regular| 20| 25| Bold
+Title 3| Regular| 18| 23| Semibold
+Headline| Semibold| 15| 20| Semibold
+Body| Regular| 15| 20| Semibold
+Callout| Regular| 14| 19| Semibold
+Subhead| Regular| 13| 18| Semibold
+Footnote| Regular| 12| 16| Semibold
+Caption 1| Regular| 11| 13| Semibold
+Caption 2| Regular| 11| 13| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [Medium](https://developer.apple.com/design/human-interface-guidelines/typography#Medium)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 33| 40| Bold
+Title 1| Regular| 27| 33| Bold
+Title 2| Regular| 21| 26| Bold
+Title 3| Regular| 19| 24| Semibold
+Headline| Semibold| 16| 21| Semibold
+Body| Regular| 16| 21| Semibold
+Callout| Regular| 15| 20| Semibold
+Subhead| Regular| 14| 19| Semibold
+Footnote| Regular| 12| 16| Semibold
+Caption 1| Regular| 11| 13| Semibold
+Caption 2| Regular| 11| 13| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [Large (default)](https://developer.apple.com/design/human-interface-guidelines/typography#Large-default)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 34| 41| Bold
+Title 1| Regular| 28| 34| Bold
+Title 2| Regular| 22| 28| Bold
+Title 3| Regular| 20| 25| Semibold
+Headline| Semibold| 17| 22| Semibold
+Body| Regular| 17| 22| Semibold
+Callout| Regular| 16| 21| Semibold
+Subhead| Regular| 15| 20| Semibold
+Footnote| Regular| 13| 18| Semibold
+Caption 1| Regular| 12| 16| Semibold
+Caption 2| Regular| 11| 13| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [xLarge](https://developer.apple.com/design/human-interface-guidelines/typography#xLarge)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 36| 43| Bold
+Title 1| Regular| 30| 37| Bold
+Title 2| Regular| 24| 30| Bold
+Title 3| Regular| 22| 28| Semibold
+Headline| Semibold| 19| 24| Semibold
+Body| Regular| 19| 24| Semibold
+Callout| Regular| 18| 23| Semibold
+Subhead| Regular| 17| 22| Semibold
+Footnote| Regular| 15| 20| Semibold
+Caption 1| Regular| 14| 19| Semibold
+Caption 2| Regular| 13| 18| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [xxLarge](https://developer.apple.com/design/human-interface-guidelines/typography#xxLarge)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 38| 46| Bold
+Title 1| Regular| 32| 39| Bold
+Title 2| Regular| 26| 32| Bold
+Title 3| Regular| 24| 30| Semibold
+Headline| Semibold| 21| 26| Semibold
+Body| Regular| 21| 26| Semibold
+Callout| Regular| 20| 25| Semibold
+Subhead| Regular| 19| 24| Semibold
+Footnote| Regular| 17| 22| Semibold
+Caption 1| Regular| 16| 21| Semibold
+Caption 2| Regular| 15| 20| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [xxxLarge](https://developer.apple.com/design/human-interface-guidelines/typography#xxxLarge)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 40| 48| Bold
+Title 1| Regular| 34| 41| Bold
+Title 2| Regular| 28| 34| Bold
+Title 3| Regular| 26| 32| Semibold
+Headline| Semibold| 23| 29| Semibold
+Body| Regular| 23| 29| Semibold
+Callout| Regular| 22| 28| Semibold
+Subhead| Regular| 21| 28| Semibold
+Footnote| Regular| 19| 24| Semibold
+Caption 1| Regular| 18| 23| Semibold
+Caption 2| Regular| 17| 22| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+### [iOS, iPadOS larger accessibility type sizes](https://developer.apple.com/design/human-interface-guidelines/typography#iOS-iPadOS-larger-accessibility-type-sizes)
+
+ * AX1
+ * AX2
+ * AX3
+ * AX4
+ * AX5
+
+
+
+#### [AX1](https://developer.apple.com/design/human-interface-guidelines/typography#AX1)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 44| 52| Bold
+Title 1| Regular| 38| 46| Bold
+Title 2| Regular| 34| 41| Bold
+Title 3| Regular| 31| 38| Semibold
+Headline| Semibold| 28| 34| Semibold
+Body| Regular| 28| 34| Semibold
+Callout| Regular| 26| 32| Semibold
+Subhead| Regular| 25| 31| Semibold
+Footnote| Regular| 23| 29| Semibold
+Caption 1| Regular| 22| 28| Semibold
+Caption 2| Regular| 20| 25| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [AX2](https://developer.apple.com/design/human-interface-guidelines/typography#AX2)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 48| 57| Bold
+Title 1| Regular| 43| 51| Bold
+Title 2| Regular| 39| 47| Bold
+Title 3| Regular| 37| 44| Semibold
+Headline| Semibold| 33| 40| Semibold
+Body| Regular| 33| 40| Semibold
+Callout| Regular| 32| 39| Semibold
+Subhead| Regular| 30| 37| Semibold
+Footnote| Regular| 27| 33| Semibold
+Caption 1| Regular| 26| 32| Semibold
+Caption 2| Regular| 24| 30| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [AX3](https://developer.apple.com/design/human-interface-guidelines/typography#AX3)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 52| 61| Bold
+Title 1| Regular| 48| 57| Bold
+Title 2| Regular| 44| 52| Bold
+Title 3| Regular| 43| 51| Semibold
+Headline| Semibold| 40| 48| Semibold
+Body| Regular| 40| 48| Semibold
+Callout| Regular| 38| 46| Semibold
+Subhead| Regular| 36| 43| Semibold
+Footnote| Regular| 33| 40| Semibold
+Caption 1| Regular| 32| 39| Semibold
+Caption 2| Regular| 29| 35| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [AX4](https://developer.apple.com/design/human-interface-guidelines/typography#AX4)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 56| 66| Bold
+Title 1| Regular| 53| 62| Bold
+Title 2| Regular| 50| 59| Bold
+Title 3| Regular| 49| 58| Semibold
+Headline| Semibold| 47| 56| Semibold
+Body| Regular| 47| 56| Semibold
+Callout| Regular| 44| 52| Semibold
+Subhead| Regular| 42| 50| Semibold
+Footnote| Regular| 38| 46| Semibold
+Caption 1| Regular| 37| 44| Semibold
+Caption 2| Regular| 34| 41| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [AX5](https://developer.apple.com/design/human-interface-guidelines/typography#AX5)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 60| 70| Bold
+Title 1| Regular| 58| 68| Bold
+Title 2| Regular| 56| 66| Bold
+Title 3| Regular| 55| 65| Semibold
+Headline| Semibold| 53| 62| Semibold
+Body| Regular| 53| 62| Semibold
+Callout| Regular| 51| 60| Semibold
+Subhead| Regular| 49| 58| Semibold
+Footnote| Regular| 44| 52| Semibold
+Caption 1| Regular| 43| 51| Semibold
+Caption 2| Regular| 40| 48| Semibold
+
+Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+### [macOS built-in text styles](https://developer.apple.com/design/human-interface-guidelines/typography#macOS-built-in-text-styles)
+
+Text style| Weight| Size (points)| Line height (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 26| 32| Bold
+Title 1| Regular| 22| 26| Bold
+Title 2| Regular| 17| 22| Bold
+Title 3| Regular| 15| 20| Semibold
+Headline| Bold| 13| 16| Heavy
+Body| Regular| 13| 16| Semibold
+Callout| Regular| 12| 15| Semibold
+Subheadline| Regular| 11| 14| Semibold
+Footnote| Regular| 10| 13| Semibold
+Caption 1| Regular| 10| 13| Medium
+Caption 2| Medium| 10| 13| Semibold
+
+Point size based on image resolution of 144 ppi for @2x designs.
+
+### [tvOS built-in text styles](https://developer.apple.com/design/human-interface-guidelines/typography#tvOS-built-in-text-styles)
+
+Text style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Title 1| Medium| 76| 96| Bold
+Title 2| Medium| 57| 66| Bold
+Title 3| Medium| 48| 56| Bold
+Headline| Medium| 38| 46| Bold
+Subtitle 1| Regular| 38| 46| Medium
+Callout| Medium| 31| 38| Bold
+Body| Medium| 29| 36| Bold
+Caption 1| Medium| 25| 32| Bold
+Caption 2| Medium| 23| 30| Bold
+
+Point size based on image resolution of 72 ppi for @1x and 144 ppi for @2x designs.
+
+### [watchOS Dynamic Type sizes](https://developer.apple.com/design/human-interface-guidelines/typography#watchOS-Dynamic-Type-sizes)
+
+ * xSmall
+ * Small
+ * Large
+ * xLarge
+ * xxLarge
+ * xxxLarge
+
+
+
+#### [xSmall](https://developer.apple.com/design/human-interface-guidelines/typography#xSmall)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 30| 32.5| Bold
+Title 1| Regular| 28| 30.5| Semibold
+Title 2| Regular| 24| 26.5| Semibold
+Title 3| Regular| 17| 19.5| Semibold
+Headline| Semibold| 14| 16.5| Semibold
+Body| Regular| 14| 16.5| Semibold
+Caption 1| Regular| 13| 15.5| Semibold
+Caption 2| Regular| 12| 14.5| Semibold
+Footnote 1| Regular| 11| 13.5| Semibold
+Footnote 2| Regular| 10| 12.5| Semibold
+
+#### [Small (default 38mm)](https://developer.apple.com/design/human-interface-guidelines/typography#Small-default-38mm)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 32| 34.5| Bold
+Title 1| Regular| 30| 32.5| Semibold
+Title 2| Regular| 26| 28.5| Semibold
+Title 3| Regular| 18| 20.5| Semibold
+Headline| Semibold| 15| 17.5| Semibold
+Body| Regular| 15| 17.5| Semibold
+Caption 1| Regular| 14| 16.5| Semibold
+Caption 2| Regular| 13| 15.5| Semibold
+Footnote 1| Regular| 12| 14.5| Semibold
+Footnote 2| Regular| 11| 13.5| Semibold
+
+#### [Large (default 40mm/41mm/42mm)](https://developer.apple.com/design/human-interface-guidelines/typography#Large-default-40mm41mm42mm)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 36| 38.5| Bold
+Title 1| Regular| 34| 36.5| Semibold
+Title 2| Regular| 27| 30.5| Semibold
+Title 3| Regular| 19| 21.5| Semibold
+Headline| Semibold| 16| 18.5| Semibold
+Body| Regular| 16| 18.5| Semibold
+Caption 1| Regular| 15| 17.5| Semibold
+Caption 2| Regular| 14| 16.5| Semibold
+Footnote 1| Regular| 13| 15.5| Semibold
+Footnote 2| Regular| 12| 14.5| Semibold
+
+#### [xLarge (default 44mm/45mm/49mm)](https://developer.apple.com/design/human-interface-guidelines/typography#xLarge-default-44mm45mm49mm)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 40| 42.5| Bold
+Title 1| Regular| 38| 40.5| Semibold
+Title 2| Regular| 30| 32.5| Semibold
+Title 3| Regular| 20| 22.5| Semibold
+Headline| Semibold| 17| 19.5| Semibold
+Body| Regular| 17| 19.5| Semibold
+Caption 1| Regular| 16| 18.5| Semibold
+Caption 2| Regular| 15| 17.5| Semibold
+Footnote 1| Regular| 14| 16.5| Semibold
+Footnote 2| Regular| 13| 15.5| Semibold
+
+#### [xxLarge](https://developer.apple.com/design/human-interface-guidelines/typography#xxLarge)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 41| 43.5| Bold
+Title 1| Regular| 39| 41.5| Semibold
+Title 2| Regular| 31| 33.5| Semibold
+Title 3| Regular| 21| 23.5| Semibold
+Headline| Semibold| 18| 20.5| Semibold
+Body| Regular| 18| 20.5| Semibold
+Caption 1| Regular| 17| 19.5| Semibold
+Caption 2| Regular| 15| 18.5| Semibold
+Footnote 1| Regular| 15| 17.5| Semibold
+Footnote 2| Regular| 14| 16.5| Semibold
+
+#### [xxxLarge](https://developer.apple.com/design/human-interface-guidelines/typography#xxxLarge)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 42| 44.5| Bold
+Title 1| Regular| 40| 42.5| Semibold
+Title 2| Regular| 32| 34.5| Semibold
+Title 3| Regular| 22| 24.5| Semibold
+Headline| Semibold| 19| 21.5| Semibold
+Body| Regular| 19| 21.5| Semibold
+Caption 1| Regular| 18| 20.5| Semibold
+Caption 2| Regular| 17| 19.5| Semibold
+Footnote 1| Regular| 16| 18.5| Semibold
+Footnote 2| Regular| 15| 17.5| Semibold
+
+### [watchOS larger accessibility type sizes](https://developer.apple.com/design/human-interface-guidelines/typography#watchOS-larger-accessibility-type-sizes)
+
+ * AX1
+ * AX2
+ * AX3
+
+
+
+#### [AX1](https://developer.apple.com/design/human-interface-guidelines/typography#AX1)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 44| 46.5| Bold
+Title 1| Regular| 42| 44.5| Semibold
+Title 2| Regular| 34| 41| Semibold
+Title 3| Regular| 24| 26.5| Semibold
+Headline| Semibold| 21| 23.5| Semibold
+Body| Regular| 21| 23.5| Semibold
+Caption 1| Regular| 18| 20.5| Semibold
+Caption 2| Regular| 17| 19.5| Semibold
+Footnote 1| Regular| 16| 18.5| Semibold
+Footnote 2| Regular| 15| 17.5| Semibold
+
+#### [AX2](https://developer.apple.com/design/human-interface-guidelines/typography#AX2)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 45| 47.5| Bold
+Title 1| Regular| 43| 46| Semibold
+Title 2| Regular| 35| 37.5| Semibold
+Title 3| Regular| 25| 27.5| Semibold
+Headline| Semibold| 22| 24.5| Semibold
+Body| Regular| 22| 24.5| Semibold
+Caption 1| Regular| 19| 21.5| Semibold
+Caption 2| Regular| 18| 20.5| Semibold
+Footnote 1| Regular| 17| 19.5| Semibold
+Footnote 2| Regular| 16| 17.5| Semibold
+
+#### [AX3](https://developer.apple.com/design/human-interface-guidelines/typography#AX3)
+
+Style| Weight| Size (points)| Leading (points)| Emphasized weight
+---|---|---|---|---
+Large Title| Regular| 46| 48.5| Bold
+Title 1| Regular| 44| 47| Semibold
+Title 2| Regular| 36| 38.5| Semibold
+Title 3| Regular| 26| 28.5| Semibold
+Headline| Semibold| 23| 25.5| Semibold
+Body| Regular| 23| 25.5| Semibold
+Caption 1| Regular| 20| 22.5| Semibold
+Caption 2| Regular| 19| 21.5| Semibold
+Footnote 1| Regular| 18| 20.5| Semibold
+Footnote 2| Regular| 17| 19.5| Semibold
+
+### [Tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#Tracking-values)
+
+#### [iOS, iPadOS, visionOS tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#iOS-iPadOS-visionOS-tracking-values)
+
+ * SF Pro
+ * SF Pro Rounded
+ * New York
+
+
+
+#### [SF Pro](https://developer.apple.com/design/human-interface-guidelines/typography#SF-Pro)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +41| +0.24
+7| +34| +0.23
+8| +26| +0.21
+9| +19| +0.17
+10| +12| +0.12
+11| +6| +0.06
+12| 0| 0.0
+13| -6| -0.08
+14| -11| -0.15
+15| -16| -0.23
+16| -20| -0.31
+17| -26| -0.43
+18| -25| -0.44
+19| -24| -0.45
+20| -23| -0.45
+21| -18| -0.36
+22| -12| -0.26
+23| -4| -0.10
+24| +3| +0.07
+25| +6| +0.15
+26| +8| +0.22
+27| +11| +0.29
+28| +14| +0.38
+29| +14| +0.40
+30| +14| +0.40
+31| +13| +0.39
+32| +13| +0.41
+33| +12| +0.40
+34| +12| +0.40
+35| +11| +0.38
+36| +10| +0.37
+37| +10| +0.36
+38| +10| +0.37
+39| +10| +0.38
+40| +10| +0.37
+41| +9| +0.36
+42| +9| +0.37
+43| +9| +0.38
+44| +8| +0.37
+45| +8| +0.35
+46| +8| +0.36
+47| +8| +0.37
+48| +8| +0.35
+49| +7| +0.33
+50| +7| +0.34
+51| +7| +0.35
+52| +6| +0.33
+53| +6| +0.31
+54| +6| +0.32
+56| +6| +0.30
+58| +5| +0.28
+60| +4| +0.26
+62| +4| +0.24
+64| +4| +0.22
+66| +3| +0.19
+68| +2| +0.17
+70| +2| +0.14
+72| +2| +0.14
+76| +1| +0.07
+80| 0| 0
+84| 0| 0
+88| 0| 0
+92| 0| 0
+96| 0| 0
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [SF Pro Rounded](https://developer.apple.com/design/human-interface-guidelines/typography#SF-Pro-Rounded)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +87| +0.51
+7| +80| +0.54
+8| +72| +0.57
+9| +65| +0.57
+10| +58| +0.57
+11| +52| +0.56
+12| +46| +0.54
+13| +40| +0.51
+14| +35| +0.48
+15| +30| +0.44
+16| +26| +0.41
+17| +22| +0.37
+18| +21| +0.37
+19| +20| +0.37
+20| +18| +0.36
+21| +17| +0.35
+22| +16| +0.34
+23| +16| +0.35
+24| +15| +0.35
+25| +14| +0.35
+26| +14| +0.36
+27| +14| +0.36
+28| +13| +0.36
+29| +13| +0.37
+30| +12| +0.37
+31| +12| +0.36
+32| +12| +0.38
+33| +12| +0.39
+34| +12| +0.38
+35| +11| +0.38
+36| +11| +0.39
+37| +10| +0.38
+38| +10| +0.39
+39| +10| +0.38
+40| +10| +0.39
+41| +10| +0.38
+42| +10| +0.39
+43| +9| +0.38
+44| +8| +0.37
+45| +8| +0.37
+46| +8| +0.36
+47| +8| +0.37
+48| +8| +0.35
+49| +8| +0.36
+50| +7| +0.34
+51| +6| +0.32
+52| +6| +0.33
+53| +6| +0.31
+54| +6| +0.32
+56| +6| +0.30
+58| +4| +0.25
+60| +4| +0.23
+62| +4| +0.21
+64| +3| +0.19
+66| +2| +0.16
+68| +2| +0.13
+70| +2| +0.14
+72| +2| +0.11
+76| +1| +0.07
+80| 0| 0.00
+84| 0| 0.00
+88| 0| 0.00
+92| 0| 0.00
+96| 0| 0.00
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [New York](https://developer.apple.com/design/human-interface-guidelines/typography#New-York)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +40| +0.23
+7| +32| +0.22
+8| +25| +0.20
+9| +20| +0.18
+10| +16| +0.15
+11| +11| +.12
+12| +6| +0.07
+13| +4| +0.05
+14| +2| +0.03
+15| +0| +0.00
+16| -2| -0.03
+17| -4| -0.07
+18| -6| -0.11
+19| -8| -0.15
+20| -10| -0.20
+21| -10| -0.21
+22| -10| -0.23
+23| -11| -0.25
+24| -11| -0.26
+25| -11| -0.27
+26| -12| -0.29
+27| -12| -0.32
+28| -12| -0.33
+29| -12| -0.34
+30| -12| -0.37
+31| -13| -0.39
+32| -13| -0.41
+33| -13| -0.42
+34| -14| -0.45
+35| -14| -0.48
+36| -14| -0.49
+38| -14| -0.52
+40| -14| -0.55
+42| -14| -0.57
+44| -14| -0.62
+46| -14| -0.65
+48| -14| -0.68
+50| -14| -0.71
+52| -14| -0.74
+54| -15| -0.79
+58| -15| -0.85
+62| -15| -0.91
+66| -15| -0.97
+70| -16| -1.06
+72| -16| -1.09
+80| -16| -1.21
+88| -16| -1.33
+96| -16| -1.50
+100| -16| -1.56
+120| -16| -1.88
+140| -16| -2.26
+160| -16| -2.58
+180| -17| -2.99
+200| -17| -3.32
+220| -18| -3.76
+240| -18| -4.22
+260| -18| -4.57
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [macOS tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#macOS-tracking-values)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +41| +0.24
+7| +34| +0.23
+8| +26| +0.21
+9| +19| +0.17
+10| +12| +0.12
+11| +6| +0.06
+12| 0| 0.0
+13| -6| -0.08
+14| -11| -0.15
+15| -16| -0.23
+16| -20| -0.31
+17| -26| -0.43
+18| -25| -0.44
+19| -24| -0.45
+20| -23| -0.45
+21| -18| -0.36
+22| -12| -0.26
+23| -4| -0.10
+24| +3| +0.07
+25| +6| +0.15
+26| +8| +0.22
+27| +11| +0.29
+28| +14| +0.38
+29| +14| +0.40
+30| +14| +0.40
+31| +13| +0.39
+32| +13| +0.41
+33| +12| +0.40
+34| +12| +0.40
+35| +11| +0.38
+36| +10| +0.37
+37| +10| +0.36
+38| +10| +0.37
+39| +10| +0.38
+40| +10| +0.37
+41| +9| +0.36
+42| +9| +0.37
+43| +9| +0.38
+44| +8| +0.37
+45| +8| +0.35
+46| +8| +0.36
+47| +8| +0.37
+48| +8| +0.35
+49| +7| +0.33
+50| +7| +0.34
+51| +7| +0.35
+52| +6| +0.31
+53| +6| +0.33
+54| +6| +0.32
+56| +6| +0.30
+58| +5| +0.28
+60| +4| +0.26
+62| +4| +0.24
+64| +4| +0.22
+66| +3| +0.19
+68| +2| +0.17
+70| +2| +0.14
+72| +2| +0.14
+76| +1| +0.07
+80| 0| 0
+84| 0| 0
+88| 0| 0
+92| 0| 0
+96| 0| 0
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [tvOS tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#tvOS-tracking-values)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +41| +0.24
+7| +34| +0.23
+8| +26| +0.21
+9| +19| +0.17
+10| +12| +0.12
+11| +6| +0.06
+12| 0| 0.0
+13| -6| -0.08
+14| -11| -0.15
+15| -16| -0.23
+16| -20| -0.31
+17| -26| -0.43
+18| -25| -0.44
+19| -24| -0.45
+20| -23| -0.45
+21| -18| -0.36
+22| -12| -0.26
+23| -4| -0.10
+24| +3| +0.07
+25| +6| +0.15
+26| +8| +0.22
+27| +11| +0.29
+28| +14| +0.38
+29| +14| +0.40
+30| +14| +0.40
+31| +13| +0.39
+32| +13| +0.41
+33| +12| +0.40
+34| +12| +0.40
+35| +11| +0.38
+36| +10| +0.37
+37| +10| +0.36
+38| +10| +0.37
+39| +10| +0.38
+40| +10| +0.37
+41| +9| +0.36
+42| +9| +0.37
+43| +9| +0.38
+44| +8| +0.37
+45| +8| +0.35
+46| +8| +0.36
+47| +8| +0.37
+48| +8| +0.35
+49| +7| +0.33
+50| +7| +0.34
+51| +7| +0.35
+52| +6| +0.31
+53| +6| +0.33
+54| +6| +0.32
+56| +6| +0.30
+58| +5| +0.28
+60| +4| +0.26
+62| +4| +0.24
+64| +4| +0.22
+66| +3| +0.19
+68| +2| +0.17
+70| +2| +0.14
+72| +2| +0.14
+76| +1| +0.07
+80| 0| 0
+84| 0| 0
+88| 0| 0
+92| 0| 0
+96| 0| 0
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x and 216 ppi for @3x designs.
+
+#### [watchOS tracking values](https://developer.apple.com/design/human-interface-guidelines/typography#watchOS-tracking-values)
+
+ * SF Compact
+ * SF Compact Rounded
+
+
+
+#### [SF Compact](https://developer.apple.com/design/human-interface-guidelines/typography#SF-Compact)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +50| +0.29
+7| +30| +0.21
+8| +30| +0.23
+9| +30| +0.26
+10| +30| +0.29
+11| +24| +0.26
+12| +20| +0.23
+13| +16| +0.20
+14| +14| +0.19
+15| +4| +0.06
+16| 0| 0.00
+17| -4| -0.07
+18| -8| -0.14
+19| -12| -0.22
+20| 0| 0.00
+21| -2| -0.04
+22| -4| -0.09
+23| -6| -0.13
+24| -8| -0.19
+25| -10| -0.24
+26| -11| -0.28
+27| -12| -0.30
+28| -12| -0.34
+29| -14| -0.38
+30| -14| -0.42
+31| -15| -0.45
+32| -16| -0.50
+33| -17| -0.55
+34| -18| -0.60
+35| -18| -0.63
+36| -20| -0.69
+37| -20| -0.72
+38| -20| -0.74
+39| -20| -0.76
+40| -20| -0.78
+41| -20| -0.80
+42| -20| -0.82
+43| -20| -0.84
+44| -20| -0.86
+45| -20| -0.88
+46| -20| -0.92
+47| -20| -0.94
+48| -20| -0.96
+49| -21| -1.00
+50| -21| -1.03
+51| -21| -1.05
+52| -21| -1.07
+53| -22| -1.11
+54| -22| -1.13
+56| -22| -1.20
+58| -22| -1.25
+60| -22| -1.32
+62| -22| -1.36
+64| -23| -1.44
+66| -24| -1.51
+68| -24| -1.56
+70| -24| -1.64
+72| -24| -1.69
+76| -25| -1.86
+80| -26| -1.99
+84| -26| -2.13
+88| -26| -2.28
+92| -28| -2.47
+96| -28| -2.62
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x designs.
+
+#### [SF Compact Rounded](https://developer.apple.com/design/human-interface-guidelines/typography#SF-Compact-Rounded)
+
+Size (points)| Tracking (1/1000 em)| Tracking (points)
+---|---|---
+6| +28| +0.16
+7| +26| +0.18
+8| +24| +0.19
+9| +22| +0.19
+10| +20| +0.20
+11| +18| +0.19
+12| +16| +0.19
+13| +14| +0.18
+14| +12| +0.16
+15| +10| +0.15
+16| +8| +0.12
+17| +6| +0.10
+18| +4| +0.07
+19| +2| +0.04
+20| 0| 0.00
+21| -2| -0.04
+22| -4| -0.09
+23| -6| -0.13
+24| -8| -0.19
+25| -10| -0.24
+26| -11| -0.28
+27| -12| -0.30
+28| -12| -0.34
+29| -14| -0.38
+30| -14| -0.42
+31| -15| -0.45
+32| -16| -0.50
+33| -17| -0.55
+34| -18| -0.60
+35| -18| -0.63
+36| -20| -0.69
+37| -20| -0.72
+38| -20| -0.74
+39| -20| -0.76
+40| -20| -0.78
+41| -20| -0.80
+42| -20| -0.82
+43| -20| -0.84
+44| -20| -0.86
+45| -20| -0.88
+46| -20| -0.92
+47| -20| -0.94
+48| -20| -0.96
+49| -21| -1.00
+50| -21| -1.03
+51| -21| -1.05
+52| -21| -1.07
+53| -22| -1.11
+54| -22| -1.13
+56| -22| -1.20
+58| -22| -1.25
+60| -22| -1.32
+62| -22| -1.36
+64| -23| -1.44
+66| -24| -1.51
+68| -24| -1.56
+70| -24| -1.64
+72| -24| -1.69
+76| -25| -1.86
+80| -26| -1.99
+84| -26| -2.13
+88| -26| -2.28
+92| -28| -2.47
+96| -28| -2.62
+
+Not all apps express tracking values as 1/1000 em. Point size based on image resolution of 144 ppi for @2x designs.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/typography#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/typography#Related)
+
+[Fonts for Apple platforms](https://developer.apple.com/fonts/)
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/typography#Developer-documentation)
+
+[Text input and output](https://developer.apple.com/documentation/SwiftUI/Text-input-and-output) — SwiftUI
+
+[Text display and fonts](https://developer.apple.com/documentation/UIKit/text-display-and-fonts) — UIKit
+
+[Fonts](https://developer.apple.com/documentation/AppKit/fonts) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/typography#Videos)
+
+[ Get started with Dynamic Type ](https://developer.apple.com/videos/play/wwdc2024/10074)
+
+[ Meet the expanded San Francisco font family ](https://developer.apple.com/videos/play/wwdc2022/110381)
+
+[ The details of UI typography ](https://developer.apple.com/videos/play/wwdc2020/10175)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/typography#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Added emphasized weights to the Dynamic Type style specifications for each platform.
+March 7, 2025| Expanded guidance for Dynamic Type.
+June 10, 2024| Added guidance for using Apple’s Unity plug-ins to support Dynamic Type in a Unity-based game and enhanced guidance on billboarding in a visionOS app or game.
+September 12, 2023| Added artwork illustrating system font weights, and clarified tvOS specification table descriptions.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-foundations/references/writing.md b/web-app/public/skills/hig-foundations/references/writing.md
new file mode 100644
index 00000000..af8b233e
--- /dev/null
+++ b/web-app/public/skills/hig-foundations/references/writing.md
@@ -0,0 +1,91 @@
+---
+title: "Writing | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/writing
+
+# Writing
+
+The words you choose within your app are an essential part of its user experience.
+
+
+
+Whether you’re building an onboarding experience, writing an alert, or describing an image for accessibility, designing through the lens of language will help people get the most from your app or game.
+
+## [Getting started](https://developer.apple.com/design/human-interface-guidelines/writing#Getting-started)
+
+**Determine your app’s voice.** Think about who you’re talking to, so you can figure out the type of vocabulary you’ll use. What types of words are familiar to people using your app? How do you want people to feel? The words for a banking app might convey trust and stability, for example, while the words in a game might convey excitement and fun. Create a list of common terms, and reference that list to keep your language consistent. Consistent language, along with a voice that reflects your app’s values, helps everything feel more cohesive.
+
+**Match your tone to the context.** Once you’ve established your app’s voice, vary your tone based on the situation. Consider what people are doing while they’re using your app — both in the physical world and within the app itself. Are they exercising and reached a goal? Or are they trying to make a payment and received an error? Situational factors affect both what you say and how you display the text on the screen.
+
+Compare the tone of these two examples from Apple Watch. In the first, the tone is straightforward and direct, reflecting the seriousness of the situation. In the second, the tone is light and congratulatory.
+
+
+
+
+
+**Be clear.** Choose words that are easily understood and convey the right thing. Check each word to be sure it needs to be there. If you can use fewer words, do so. When in doubt, read your writing out loud.
+
+**Write for everyone.** For your app to be useful for as many people as possible, it needs to speak to as many people as possible. Choose simple, plain language and write with accessibility and localization in mind, avoiding jargon and gendered terminology. For guidance, see [Writing inclusively](https://help.apple.com/applestyleguide/#/apdcb2a65d68) and [VoiceOver](https://developer.apple.com/design/human-interface-guidelines/voiceover); for developer guidance, see [Localization](https://developer.apple.com/documentation/xcode/localization).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/writing#Best-practices)
+
+**Consider each screen’s purpose**. Pay attention to the order of elements on a screen, and put the most important information first. Format your text to make it easy to read. If you’re trying to convey more than one idea, consider breaking up the text onto multiple screens, and think about the flow of information across those screens.
+
+**Be action oriented.** Active voice and clear labels help people navigate through your app from one step to the next, or from one screen to another. When labeling buttons and links, it’s almost always best to use a verb. Prioritize clarity and avoid the temptation to be too cute or clever with your labels. For example, just saying “Send” often works better than “Let’s do it!” For links, avoid using “Click here” in favor of more descriptive words or phrases, such as “Learn more about UX Writing.” This is especially important for people using screen readers to access your app.
+
+**Build language patterns.** Consistency builds familiarity, helping your app feel cohesive, intuitive, and thoughtfully designed. It also makes writing for your app easier, as you can return to these patterns again and again.
+
+**Adopt capitalization rules that align with your app’s style, then apply them consistently.** While certain components, like [button labels](https://developer.apple.com/design/human-interface-guidelines/buttons#Content), have specific guidelines, how you format text reflects your app’s voice. Title case is generally considered formal, while sentence case is more casual. Choose a style for each UI element type and use it consistently throughout your app — for example, title case for all alerts or sentence case for all headlines.
+
+**Give clear guidance and use consistent language throughout processes with multiple steps.** If your app has a flow that spans multiple screens, decide how you want to label the actions that take people from one step to the next. Begin with language like “Get Started” to indicate you’re starting a flow. You can use the button label to hint at the next step, or use terms like “Continue” or “Next,” but be consistent with what you choose. Make it clear when a flow is complete by using language like “Done.”
+
+**Use possessive pronouns sparingly.** Possessive pronouns like _my_ and _your_ are often unnecessary to establish context. For example, “Favorites” conveys the same message as “Your Favorites,” and is more succinct. If you do use possessive pronouns, use them consistently throughout your app, and try not to switch perspectives. Avoid using _we_ altogether because it may be unclear who the “we” in question refers to. This is particularly problematic in error messages like “We’re having trouble loading this content.” Something like “Unable to load content” is much clearer.
+
+**Write for how people use each device.** People may use your app on several types of devices. While your language needs to be consistent across them, think about where it would be helpful to adjust your text to make it suitable for different devices. Make sure you describe gestures correctly on each device — for example, not saying “click” for a touch device like iPhone or iPad where you mean “tap.”
+
+Where and how people use a device, its screen size, and its location all affect how you write for your app. iPhone and Apple Watch, for example, offer opportunities for personalization, but their small screens require brevity. TVs, on the other hand, are often in common living spaces, and several people are likely to see anything on the screen, so consider who you’re addressing. Bigger screens also require brevity, as the text must be large for people to see it from a distance.
+
+**Provide clear next steps on any blank screens.** An empty state, like a completed to-do list or bookmarks folder with nothing in it, can provide a good opportunity to make people feel welcome and educate them about your app. Empty states can also showcase your app’s voice, but make sure that the content is useful and fits the context. An empty screen can be daunting if it isn’t obvious what to do next, so guide people on actions they can take, and give them a button or link to do so if possible. Remember that empty states are usually temporary, so don’t show crucial information that could then disappear.
+
+**Write clear error messages.** It’s always best to help people avoid errors. When an error message is necessary, display it as close to the problem as possible, avoid blame, and be clear about what someone can do to fix it. For example, “That password is too short” isn’t as helpful as “Choose a password with at least 8 characters.” Remember that errors can be frustrating. Interjections like “oops!” or “uh-oh” are typically unnecessary and can sound insincere. If you find that language alone can’t address an error that’s likely to affect many people, use that as an opportunity to rethink the interaction.
+
+**Choose the right delivery method.** There are many ways to get people’s attention, whether or not they are actively using your app. When there’s something you want to communicate, consider the urgency and importance of the message. Think about the context in which someone might see the message, whether it requires immediate action, and how much supporting information someone might need. Choose the correct delivery method, and use a tone appropriate for the situation. For guidance, see [Notifications](https://developer.apple.com/design/human-interface-guidelines/notifications), [Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts), and [Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets).
+
+**Keep settings labels clear and simple.** Help people easily find the settings they need by labeling them as practically as possible. If the setting label isn’t enough, add an explanation. Describe what it does when turned on, and people can infer the opposite. In the Handwashing Timer setting for Apple Watch, for example, the description explains that a timer can start when you’re washing your hands. It isn’t necessary to tell you that a timer won’t start when this setting is off.
+
+
+
+If you need to direct someone to a setting, provide a direct link or button, rather than trying to describe its location. For guidance, see [Settings](https://developer.apple.com/design/human-interface-guidelines/settings).
+
+**Show hints in text fields.** If your app allows people to enter their own text, like account or contact information, label all fields clearly, and use hint or placeholder text so people know how to format the information. You can give an example in hint text, like “name@example.com,” or describe the information, such as “Your name.” Show errors right next to the field, and instruct people how to enter the information correctly, rather than scolding them for not following the rules. “Use only letters for your name” is better than “Don’t use numbers or symbols.” Avoid robotic error messages with no helpful information, like “Invalid name.” For guidance, see [Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/writing#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/writing#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/writing#Related)
+
+[Apple Style Guide](https://help.apple.com/applestyleguide/#/)
+
+[Writing inclusively](https://help.apple.com/applestyleguide/#/apdcb2a65d68)
+
+[Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[Color](https://developer.apple.com/design/human-interface-guidelines/color)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/writing#Videos)
+
+[ Make a big impact with small writing changes ](https://developer.apple.com/videos/play/wwdc2025/404)
+
+[ Writing for interfaces ](https://developer.apple.com/videos/play/wwdc2022/10037)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/writing#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Clarified guidance on language patterns, and added guidance for possessive pronouns.
+February 27, 2023| New page.
+
diff --git a/web-app/public/skills/hig-inputs/SKILL.md b/web-app/public/skills/hig-inputs/SKILL.md
new file mode 100644
index 00000000..199f52a5
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/SKILL.md
@@ -0,0 +1,121 @@
+---
+name: hig-inputs
+version: 1.0.0
+description: ">"
+ Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil,
+ keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system,
+ remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions.
+ Use when asked about: "gesture design", "Apple Pencil", "keyboard shortcuts",
+ "game controller", "pointer support", "mouse support", "trackpad", "Digital Crown",
+ "eye tracking", "visionOS input", "focus system", "remote control", "gyroscope",
+ "spatial interaction". Also use when the user says "what gestures should I support,"
+ "how do I add keyboard shortcuts," "how does input work on Apple TV," "should I
+ support Apple Pencil," or asks about input device handling.
+ Cross-references: hig-components-status, hig-components-system,
+ hig-technologies for VoiceOver and Siri.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Inputs
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+### General
+
+1. **Support multiple input methods.** Touch, pointer, keyboard, pencil, voice, eyes, hands, controllers. Design for the inputs available on each platform. On iPadOS, support both touch and pointer; on macOS, both pointer and keyboard.
+
+2. **Consistent feedback for every input action.** Visible, audible, or haptic response.
+
+### Gestures
+
+3. **Standard gestures must behave consistently.** Tap to activate, swipe to scroll/navigate, pinch to zoom, long press for context menus, drag to move. Don't override system gestures (edge swipes for back, Home, notifications).
+
+4. **Use standard recognizers; keep custom gestures discoverable.** Apple's built-in recognizers handle edge cases and accessibility. If you add non-standard gestures, provide hints or coaching to teach them.
+
+### Apple Pencil
+
+5. **Precision drawing, markup, and selection.** Support pressure, tilt, and hover. Distinguish finger from Pencil when appropriate (finger pans, Pencil draws).
+
+6. **Support Scribble in text fields.** Users expect to write with Pencil in any text input.
+
+### Keyboards
+
+7. **Keyboard shortcuts and full navigation.** Standard shortcuts (Cmd+C/V/Z) plus custom ones visible in the iPadOS Command key overlay. Logical tab order.
+
+8. **Respect the software keyboard.** Adjust layout when keyboard appears. Use keyboard-avoidance APIs.
+
+### Game Controllers
+
+9. **MFi controllers with on-screen fallbacks.** Map to extended gamepad profile, sensible defaults, remappable. Always offer touch or keyboard alternatives.
+
+### Pointer and Trackpad
+
+10. **Native feel.** Hover effects, pointer shape adaptation, standard cursor behaviors. Two-finger scroll, pinch to zoom, swipe to navigate.
+
+### Digital Crown
+
+11. **Primary scrolling and value-adjustment input on watchOS.** Scrolling lists, adjusting values, navigating views. Haptic feedback at detents.
+
+### Eyes and Spatial (visionOS)
+
+12. **Look and pinch.** Generous hit targets (eye tracking is less precise than touch). Avoid sustained gaze for activation. Direct hand manipulation in immersive experiences.
+
+### Focus System
+
+13. **Critical for tvOS and visionOS.** Predictable focus movement. Every interactive element focusable. Clear visual indicators (scale, highlight, elevation). Logical focus groups.
+
+### Remotes
+
+14. **Siri Remote: limited surface.** Touch area for swiping, clickpad for selection, few physical buttons. Keep interactions simple.
+
+### Motion and Nearby
+
+15. **Gyroscope, accelerometer, UWB: use judiciously.** Suits gaming, fitness, AR. Not for essential tasks. Provide calibration and reset. For UWB, communicate distance and direction with visual or haptic cues.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [gestures.md](references/gestures.md) | Touch gestures | Tap, swipe, pinch, long press, drag, system gestures |
+| [apple-pencil-and-scribble.md](references/apple-pencil-and-scribble.md) | Apple Pencil | Precision, pressure, tilt, hover, handwriting |
+| [keyboards.md](references/keyboards.md) | Keyboards | Shortcuts, navigation, software keyboard, Command key |
+| [game-controls.md](references/game-controls.md) | Game controllers | MFi, extended gamepad, remapping, fallbacks |
+| [pointing-devices.md](references/pointing-devices.md) | Pointer/trackpad | Hover, cursor morphing, trackpad gestures |
+| [digital-crown.md](references/digital-crown.md) | Digital Crown | Scrolling, value adjustment, haptic detents |
+| [eyes.md](references/eyes.md) | Eye tracking | Look and tap, gaze targeting, hit target sizing |
+| [spatial-interactions.md](references/spatial-interactions.md) | Spatial input | Hand gestures, direct manipulation, immersive input |
+| [focus-and-selection.md](references/focus-and-selection.md) | Focus system | tvOS/visionOS navigation, focus indicators, groups |
+| [remotes.md](references/remotes.md) | Remotes | Touch surface, clickpad, simple interactions |
+| [gyro-and-accelerometer.md](references/gyro-and-accelerometer.md) | Motion sensors | Gyroscope, accelerometer, calibration, gaming |
+| [nearby-interactions.md](references/nearby-interactions.md) | Nearby interactions | U1 chip, directional finding, proximity triggers |
+| [camera-control.md](references/camera-control.md) | Camera Control | iPhone camera hardware button, quick launch |
+
+## Output Format
+
+1. **Input method recommendations by platform** and how they interact.
+2. **Gesture specification table** -- standard and custom gestures with expected behaviors.
+3. **Keyboard shortcut recommendations** following system conventions.
+4. **Accessibility input alternatives** for VoiceOver, Switch Control, etc.
+
+## Questions to Ask
+
+1. Which platforms and input devices?
+2. Productivity or casual app?
+3. Custom gestures in the design?
+4. Game controller support needed?
+
+## Related Skills
+
+- **hig-components-status** -- Progress indicators responding to input (pull-to-refresh)
+- **hig-components-system** -- System experiences with unique input constraints
+- **hig-technologies** -- VoiceOver, Siri voice input, ARKit spatial gesture context
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-inputs/references/apple-pencil-and-scribble.md b/web-app/public/skills/hig-inputs/references/apple-pencil-and-scribble.md
new file mode 100644
index 00000000..36402fc9
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/apple-pencil-and-scribble.md
@@ -0,0 +1,148 @@
+---
+title: "Apple Pencil and Scribble | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble
+
+# Apple Pencil and Scribble
+
+Apple Pencil helps make drawing, handwriting, and marking effortless and natural, in addition to performing well as a pointer and UI interaction tool.
+
+
+
+Apple Pencil is a versatile, intuitive tool for iPad apps that offers pixel‑level precision when jotting notes, sketching, painting, marking up documents, and more. Scribble lets people use Apple Pencil to enter text in any text field through fast, private, on-device handwriting recognition.
+
+For details on Apple Pencil features and compatibility, see [Apple Pencil](https://www.apple.com/apple-pencil/).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Best-practices)
+
+**Support behaviors people intuitively expect when using a marking instrument.** Most people have a lot of experience with real-world marking tools, and this knowledge informs their expectations when they use Apple Pencil with your app. To provide a delightful experience, think about the ways people interact with nondigital pencils, pens, and other marking instruments, and proactively support actions that people may naturally attempt. For example, people often want to write in the margins of documents or books.
+
+**Let people choose when to switch between Apple Pencil and finger input.** For example, if your app supports Apple Pencil for marking, also ensure that your app’s controls respond to Apple Pencil so people don’t have to switch to using their finger to activate them. In this scenario, a control that doesn’t support Apple Pencil input might seem to be unresponsive, giving the impression of a malfunction or low battery. (Scribble only supports Apple Pencil input.)
+
+**Let people make a mark the moment Apple Pencil touches the screen**. You want the experience of putting Apple Pencil to screen to mirror the experience of putting a classic pencil to paper, so it’s essential to avoid requiring people to tap a button or enter a special mode before they can make a mark.
+
+**Help people express themselves by responding to the way they use Apple Pencil.** Apple Pencil may sense tilt (altitude), force (pressure), orientation (azimuth), and [barrel roll](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Barrel-roll). Use this information to affect the strokes Apple Pencil makes, such as by varying thickness and intensity. When responding to pressure, keep things simple and intuitive. For example, it feels natural to affect continuous properties — such as ink opacity or brush size — by varying the pressure.
+
+Altitude
+
+Pressure
+
+Azimuth
+
+**Provide visual feedback to indicate a direct connection with content.** Make sure Apple Pencil appears to directly and immediately manipulate content it touches onscreen. Avoid letting Apple Pencil appear to initiate seemingly disconnected actions, or affect content on other parts of the screen.
+
+**Design a great left- and right-handed experience.** Avoid placing controls in locations that may be obscured by either hand. If there’s a chance controls may become obscured, consider letting people reposition them.
+
+
+
+
+
+## [Hover](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Hover)
+
+**Use hover to help people predict what will happen when Apple Pencil touches the screen.** For example, as people hold Apple Pencil above the screen, a hover preview can show the dimensions and color of the mark that the current tool can make. As much as possible, avoid continuously modifying the preview as people move Apple Pencil closer or farther from the screen. A preview that changes according to height is unlikely to clarify the mark Apple Pencil will make, and frequent visual variations can be very distracting to people.
+
+**Avoid using hover to initiate an action.** Unlike tapping a button or marking the screen, hovering is a relatively imprecise motion that doesn’t require people to think about the actual distance between Apple Pencil and the display. You don’t want people to inadvertently perform an action — especially a destructive action that they might want to undo — just because they hold Apple Pencil near the screen.
+
+**Prefer showing a preview value that’s near the middle in a range of dynamic values.** Dynamic properties like opacity or flow can be difficult to depict at the highest or lowest ends of the spectrum. For example, previewing the appearance of a brush mark made with the maximum pressure could occlude the area in which people are marking; in contrast, depicting a mark made with the minimum pressure could be hard for people to detect, making the preview an inaccurate representation of an actual mark or even invisible.
+
+
+
+
+
+
+
+
+
+
+
+
+
+**Consider using hover to support relevant interactions close to where people are marking.** For example, you might respond to hover by displaying a contextual menu of tool sizes when people perform a gesture like [squeeze](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Squeeze) or press a modifier key on an attached keyboard. Revealing a menu near where people are marking lets them make choices without moving Apple Pencil or their hands to another part of the screen.
+
+**Prefer showing hover previews for Apple Pencil, not for a pointing device.** Although a pointing device can also respond to hover gestures, it might be confusing to provide the same visual feedback for both devices. If it makes sense in your app, you can restrict your hover preview to Apple Pencil only. For developer guidance, see [Adopting hover support for Apple Pencil](https://developer.apple.com/documentation/UIKit/adopting-hover-support-for-apple-pencil).
+
+## [Double tap](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Double-tap)
+
+**Respect people’s settings for the double-tap gesture when they make sense in your app.** By default, models of Apple Pencil that support the double-tap gesture respond by toggling between the current tool and the eraser, but people can set the gesture to toggle between the current and previous tool, show and hide the color picker, or do nothing at all. If your app supports these behaviors, let people use their preferred gestures to perform them. If the systemwide double-tap settings don’t make sense in your app, you can still use the gesture to change the interaction mode. For example, a 3D app that offers a mesh-editing tool could use double tap to toggle between the tool’s raise and lower modes.
+
+**Give people a way to specify custom double-tap behavior if necessary.** If you offer custom double-tap behavior in addition to some or all of the default behaviors, provide a control that lets people choose the custom behavior mode. People need to know which mode they’re in; otherwise, they may get confused when your app responds differently to their interactions. In this scenario, make sure it’s easy for people to discover the custom behavior your app supports, but don’t turn it on by default.
+
+**Avoid using the double-tap gesture to perform an action that modifies content.** In rare cases, it’s possible for people to double-tap accidentally, which means that they may not even be aware that your app has performed the action. Prefer using double tap to perform actions that are easy for people to undo. In particular, avoid using double tap to perform a potentially destructive action that might result in data loss.
+
+## [Squeeze](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Squeeze)
+
+Using Apple Pencil Pro, people can squeeze to perform an action. You can design a custom behavior that responds to squeeze, but recognize that people may choose to configure the squeeze gesture to run an [App Shortcut](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts) instead of app-specific actions.
+
+Note
+
+The squeeze gesture is available only when the paired iPad screen is on and while the Apple Pencil Pro is not directly contacting it. Because squeeze works when there’s distance between Apple Pencil Pro and iPad, people might not always be visually aware of the gesture’s onscreen result.
+
+**Treat squeeze as a single, quick gesture that performs a discrete — not continuous — action.** People sometimes squeeze with a lot of force, so holding a squeeze or squeezing several times quickly can be tiring. Help people remain comfortable by responding to a single squeeze and promptly displaying the result.
+
+**If you use squeeze to reveal app UI, like a contextual menu, display it close to Apple Pencil Pro.** Displaying the result of a squeeze near the tip of Apple Pencil Pro strengthens the connection between the device and the gesture, and can help people stay engaged with their task.
+
+**Define squeeze actions that are nondestructive and easy to undo.** As with the double-tap gesture, people can make the squeeze gesture without meaning to, so it’s essential to avoid using squeeze to perform an action that could result in data loss.
+
+## [Barrel roll](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Barrel-roll)
+
+While marking with Apple Pencil Pro, people can use a barrel-roll gesture to change the type of mark they’re making. For example, while using Apple Pencil Pro to highlight content in Notes, people can barrel-roll to rotate the angle of the mark.
+
+**Use barrel roll only to modify marking behavior, not to enable navigation or display other controls.** In contrast to double tap and squeeze, barrel roll is naturally related to marking and doesn’t make sense for performing an interface action.
+
+## [Scribble](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Scribble)
+
+With Scribble and Apple Pencil, people can simply write wherever text is accepted in your app — they don’t have to tap or switch modes first. Because Scribble is fully integrated into iPadOS, it’s available to all apps by default.
+
+**Make text entry feel fluid and effortless.** By default, Scribble works in all standard text components — such as text fields, text views, search fields, and editable fields in web content — except password fields. If you use a custom text field in your app, avoid making people tap or select it before they can begin writing.
+
+**Make Scribble available everywhere people might want to enter text.** Unlike using the keyboard, using Apple Pencil encourages people to treat the screen the way they treat a sheet of paper. Help strengthen this perception in your app by making Scribble consistently available in places where text entry seems natural. For example, in Reminders, it’s natural for people to create a new reminder by writing it in the blank space below the last item, even though the area doesn’t contain a text field. For developer guidance, see [`UIIndirectScribbleInteraction`](https://developer.apple.com/documentation/UIKit/UIIndirectScribbleInteraction-1nfjm).
+
+**Avoid distracting people while they write.** Some text field behaviors work well for keyboard input, but can disrupt the natural writing experience that Apple Pencil provides. For example, it’s best to avoid displaying autocompletion text as people write in a text field because the suggestions can visually interfere with their writing. It’s also a good idea to hide a field’s placeholder text the moment people begin to write so that their input doesn’t appear to overlap it.
+
+**While people are writing in a text field, make sure it remains stationary.** In some cases, it can make sense to move a text field when it becomes focused: for example, a search field might move to make more room to display results. Such a movement is fine when people are using the keyboard, but when they’re writing it can make them feel like they’ve lost control of where their input is going. If you can’t prevent a text field from moving or resizing, consider delaying the change until people pause their writing.
+
+**Prevent autoscrolling text while people are writing and editing in a text field.** When transcribed text autoscrolls, people might try to avoid writing on top of it. Worse, if text scrolls while people are using Apple Pencil to select it, they might select a different range of text than they want.
+
+**Give people enough space to write.** A small text field can feel uncomfortable to write in. When you know that Apple Pencil input is likely, improve the writing experience in your app by increasing the size of the text field before people begin to write in it or when they pause writing; avoid resizing a text field while people are writing. For developer guidance, see [`UIScribbleInteraction`](https://developer.apple.com/documentation/UIKit/UIScribbleInteraction).
+
+
+
+## [Custom drawing](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Custom-drawing)
+
+Using [PencilKit](https://developer.apple.com/documentation/PencilKit), you can let people take notes, annotate documents and images, and draw with the same low-latency experience that iOS provides. PencilKit also makes it easy to create a custom drawing canvas in your app and offer a state-of-the-art tool picker and ink palette.
+
+**Help people draw on top of existing content.** By default, the colors on your PencilKit canvas dynamically adjust to Dark Mode, so people can create content in either mode and the results will look great in both. However, when people draw on top of existing content like a PDF or a photo, you want to prevent the dynamic adjustment of colors so that the markup remains sharp and visible.
+
+**Consider displaying custom undo and redo buttons when your app runs in a compact environment.** In a regular environment, the tool picker includes undo and redo buttons, but in a compact environment it doesn’t. In a compact environment, you could display undo and redo buttons in a toolbar. You might also consider supporting the standard 3-finger undo/redo gesture, so people can use it in any environment. For guidance, see [Undo and redo](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo).
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Platform-considerations)
+
+ _Not supported in iOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Related)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Developer-documentation)
+
+[PencilKit](https://developer.apple.com/documentation/PencilKit)
+
+[PaperKit](https://developer.apple.com/documentation/PaperKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Videos)
+
+[ Meet PaperKit ](https://developer.apple.com/videos/play/wwdc2025/285)
+
+[ Squeeze the most out of Apple Pencil ](https://developer.apple.com/videos/play/wwdc2024/10214)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble#Change-log)
+
+Date| Changes
+---|---
+May 7, 2024| Added guidance for handling squeeze and barrel roll on Apple Pencil Pro.
+September 12, 2023| Updated artwork.
+November 3, 2022| Added guidelines for using hover to enhance your app.
+
diff --git a/web-app/public/skills/hig-inputs/references/camera-control.md b/web-app/public/skills/hig-inputs/references/camera-control.md
new file mode 100644
index 00000000..4b76a1a7
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/camera-control.md
@@ -0,0 +1,107 @@
+---
+title: "Camera Control | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/camera-control
+
+# Camera Control
+
+The Camera Control provides direct access to your app’s camera experience.
+
+
+
+On iPhone 16 and iPhone 16 Pro models, the Camera Control quickly opens your app’s camera experience to capture moments as they happen. When a person lightly presses the Camera Control, the system displays an overlay that extends from the device bezel.
+
+
+
+The overlay allows people to quickly adjust controls. A person can view the available controls by lightly double-pressing the Camera Control. After selecting a control, they can slide their finger on the Camera Control to adjust a value to capture their content as they want.
+
+Controls in the overlay
+
+## [Anatomy](https://developer.apple.com/design/human-interface-guidelines/camera-control#Anatomy)
+
+The Camera Control offers two types of controls for adjusting values or changing between options:
+
+ * A _slider_ provides a range of values to choose from, such as how much contrast to apply to the content.
+
+ * A _picker_ offers discrete options, such as turning a grid on and off in the viewfinder.
+
+
+
+
+Slider control
+
+Picker control
+
+In addition to custom controls that you create, the system provides a set of standard controls that you can optionally include in the overlay to allow someone to adjust their camera’s zoom and exposure.
+
+Zoom factor control
+
+Exposure bias control
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/camera-control#Best-practices)
+
+**Use SF Symbols to represent control functionality.** The system doesn’t support custom symbols; instead, pick a symbol from SF Symbols that clearly denotes a control’s behavior. iOS offers thousands of symbols you can use to represent the controls your app shows in the overlay. Symbols for controls don’t represent their current state. To view available symbols, see the Camera & Photos section in the [SF Symbols app](https://developer.apple.com/sf-symbols/).
+
+The `bolt.fill` symbol that represents a control for the camera flash
+
+The `camera.filters` symbol that represents a control for filters
+
+**Keep names of controls short.** Control labels adhere to Dynamic Type sizes, and longer names may obfuscate the camera’s viewfinder.
+
+**Include units or symbols with slider control values to provide context.** Providing descriptive information in the overlay, such as EV, %, or a custom string, helps people understand what the slider controls. For developer guidance, see [`localizedValueFormat`](https://developer.apple.com/documentation/AVFoundation/AVCaptureSlider/localizedValueFormat).
+
+
+
+Value with context
+
+
+
+Value without context
+
+**Define prominent values for a slider control.** Prominent values are ones people choose most frequently, or values that are evenly spaced, like the major increments of zoom factor. When a person slides on the Camera Control to adjust a slider control, the system more easily lands on prominent values you define. For developer guidance, see [`prominentValues`](https://developer.apple.com/documentation/AVFoundation/AVCaptureSlider/prominentValues-199dz).
+
+**Make space for the overlay in the viewfinder.** The overlay and control labels occupy the screen area adjacent to the Camera Control in both portrait and landscape orientations. To avoid overlapping the interface elements of your camera capture experience, place your UI outside of the overlay areas. Maximize the height and width of the viewfinder and allow the overlay to appear and disappear over it.
+
+
+
+**Minimize distractions in the viewfinder.** When capturing a photo or video, people appreciate a large preview image with as few visual distractions as possible. Avoid duplicating controls, like sliders and toggles, in your UI and the overlay when the system displays the overlay.
+
+
+
+Keep UI minimal.
+
+
+
+Avoid showing controls in the viewfinder that people access in the overlay.
+
+**Enable or disable controls depending on the camera mode.** For example, disable video controls when taking photos. The overlay supports multiple controls, but you can’t remove or add controls at runtime.
+
+**Consider how to arrange your controls.** Order commonly used controls toward the middle to allow quick access, and include lesser used controls on either side. When a person lightly presses the Camera Control to open the overlay again, the system remembers the last control they used in your app.
+
+**Allow people to use the Camera Control to launch your experience from anywhere.** Create a locked camera capture extension that lets people configure the Camera Control to launch your app’s camera experience from their locked device, the Home Screen, or from within other apps. For guidance, see [Camera experiences on a locked device](https://developer.apple.com/design/human-interface-guidelines/controls#Camera-experiences-on-a-locked-device).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/camera-control#Platform-considerations)
+
+ _Not supported in iPadOS, macOS, watchOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/camera-control#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/camera-control#Related)
+
+[SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols)
+
+[Controls](https://developer.apple.com/design/human-interface-guidelines/controls)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/camera-control#Developer-documentation)
+
+[Enhancing your app experience with the Camera Control](https://developer.apple.com/documentation/AVFoundation/enhancing-your-app-experience-with-the-camera-control) — AVFoundation
+
+[`AVCaptureControl`](https://developer.apple.com/documentation/AVFoundation/AVCaptureControl) — AVFoundation
+
+[LockedCameraCapture](https://developer.apple.com/documentation/LockedCameraCapture)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/camera-control#Change-log)
+
+Date| Changes
+---|---
+September 9, 2024| New page.
+
diff --git a/web-app/public/skills/hig-inputs/references/digital-crown.md b/web-app/public/skills/hig-inputs/references/digital-crown.md
new file mode 100644
index 00000000..26c1dd02
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/digital-crown.md
@@ -0,0 +1,83 @@
+---
+title: "Digital Crown | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/digital-crown
+
+# Digital Crown
+
+The Digital Crown is an important hardware input for Apple Vision Pro and Apple Watch.
+
+
+
+On both Apple Vision Pro and Apple Watch, people can use the Digital Crown to interact with the system; on Apple Watch, people can also use the Digital Crown to interact with apps.
+
+The Digital Crown on Apple Vision Pro
+
+The Digital Crown on Apple Watch
+
+## [Apple Vision Pro](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Apple-Vision-Pro)
+
+On Apple Vision Pro, people use the Digital Crown to:
+
+ * Adjust volume
+
+ * Adjust the amount of immersion in a portal, an Environment, or an app or game running in a Full Space (for guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences))
+
+ * Recenter content so it’s in front of them
+
+ * Open Accessibility settings
+
+ * Exit an app and return to the Home View
+
+
+
+
+## [Apple Watch](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Apple-Watch)
+
+As people turn the Digital Crown, it generates information you can use to enhance or facilitate interactions with your app, like scrolling or operating standard or custom controls.
+
+Starting with watchOS 10, the Digital Crown takes on an elevated role as the primary input for navigation. On the watch face, people turn the Digital Crown to view widgets in the Smart Stack, and on the Home Screen, people use it to move vertically through their collection of apps. Within apps, people turn the Digital Crown to switch between vertically paginated tabs, and to scroll through list views and variable height pages.
+
+Beyond its use for navigation, turning the Digital Crown generates information you can use to enhance or facilitate interactions with your app, such as inspecting data or operating standard or custom controls.
+
+Note
+
+Apps don’t respond to presses on the Digital Crown because watchOS reserves these interactions for system-provided functionality like revealing the Home Screen.
+
+Most Apple Watch models provide haptic feedback for the Digital Crown, which gives people a more tactile experience as they scroll through content. By default, the system provides linear haptic _detents_ — or taps — as people turn the Digital Crown a specific distance. Some system controls, like table views, provide detents as new items scroll onto the screen.
+
+**Anchor your app’s navigation to the Digital Crown.** Starting with watchOS 10, turning the Digital Crown is the main way people navigate within and between apps. List, tab, and scroll views are vertically oriented, allowing people to use the Digital Crown to easily move between the important elements of your app’s interface. When anchoring interactions to the Digital Crown, also be sure to back them up with corresponding touch screen interactions.
+
+**Consider using the Digital Crown to inspect data in contexts where navigation isn’t necessary.** In contexts where the Digital Crown doesn’t need to navigate through lists or between pages, it’s a great tool to inspect data in your app. For example, in World Clock, turning the Digital Crown advances the time of day at a selected location, allowing people to compare various times of day to their current time.
+
+**Provide visual feedback in response to Digital Crown interactions.** For example, pickers change the currently displayed value as people use the Digital Crown. If you track turns directly, use this data to update your interface programmatically. If you don’t provide visual feedback, people are likely to assume that turning the Digital Crown has no effect in your app.
+
+**Update your interface to match the speed with which people turn the Digital Crown.** People expect turning the Digital Crown to give them precise control over an interface, so it works well to use this speed to determine the speed at which you make changes. Avoid updating content at a rate that makes it difficult for people to select values.
+
+**Use the default haptic feedback when it makes sense in your app.** If haptic feedback doesn’t feel right in the context of your app — for example, if the default detents don’t match your app’s animation — turn off the detents. You can also adjust the haptic feedback behavior for tables, letting them use linear detents instead of row-based detents. For example, if your table has rows with significantly different heights, linear detents may give people a more consistent experience.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, or tvOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Action button](https://developer.apple.com/design/human-interface-guidelines/action-button)
+
+[Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Developer-documentation)
+
+[`WKCrownDelegate`](https://developer.apple.com/documentation/WatchKit/WKCrownDelegate) — WatchKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/digital-crown#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Added artwork for Apple Vision Pro and Apple Watch, and clarified that visionOS apps don’t receive direct information from the Digital Crown.
+June 21, 2023| Updated to include guidance for visionOS.
+June 5, 2023| Added guidelines emphasizing the central role of the Digital Crown for navigation.
+
diff --git a/web-app/public/skills/hig-inputs/references/eyes.md b/web-app/public/skills/hig-inputs/references/eyes.md
new file mode 100644
index 00000000..0b12d1e4
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/eyes.md
@@ -0,0 +1,120 @@
+---
+title: "Eyes | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/eyes
+
+# Eyes
+
+In visionOS, people look at a virtual object to identify it as a target they can interact with.
+
+
+
+When people look at an interactive element, visionOS highlights it, providing visual feedback that helps them confirm the item is one they want. The visual feedback, or _hover effect_ , shows people that they can use an [indirect gesture](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS) like tap to interact with the element.
+
+Video with custom controls.
+
+Content description: A recording of the Settings app showing the hover effect appear on several individual settings in turn as someone's eyes move from one to another.
+
+Play
+
+In some cases, the system can automatically display an expanded view of a component after people look at it. For example, when people look at a tab bar, the entire bar resizes to reveal text labels next to each tab. In this scenario, an individual tab also highlights before the tab bar expansion to let people select it before revealing the labels. Another example is a button that can reveal a tooltip when people look at it.
+
+Important
+
+To help preserve people’s privacy, visionOS doesn’t provide direct information about where people are looking before they tap. When you use system-provided components, visionOS automatically tells you when people tap the component. For developer guidance, see [Adopting best practices for privacy and user preferences](https://developer.apple.com/documentation/visionOS/adopting-best-practices-for-privacy).
+
+visionOS also supports _focus effects_ that help people navigate apps and the system using a connected input device like a keyboard or game controller. Focus effects are unrelated to the hover effect; to learn more, see [Focus and selection](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/eyes#Best-practices)
+
+**Always give people multiple ways to interact with your app.** Design your app to support the accessibility features people use to personalize the ways they interact with their devices. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Design for visual comfort.** Help people accomplish their primary task by making sure that the objects they need to use are within their [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view). When your app or game is running in the Shared Space or a Full Space, the system automatically places the first window or volume people open in a convenient location in front of them. While running in a Full Space, your app or game can also request access to information about a person’s head pose to help you place 3D content appropriately. In all cases, you can improve the visual comfort of your experience when you avoid requiring people to make multiple quick eye adjustments, either over a large area or through multiple levels of depth. For guidance, see [Depth](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Depth).
+
+**Place content at a comfortable viewing distance.** For example, to help people remain comfortable while they read or engage with content over time, aim to place it at least one meter away. In general, you don’t want to place content very close to people unless they’ll view or interact with it for only a little while.
+
+**Prefer using standard UI components.** System-provided components respond consistently when people look at them. If your custom components use different visual cues to provide visual feedback, it can be difficult for people to learn and remember how these components work.
+
+## [Making items easy to see](https://developer.apple.com/design/human-interface-guidelines/eyes#Making-items-easy-to-see)
+
+**Minimize visual distractions.** When there’s a lot of visual noise, it can be difficult for people to find the object they’re looking for. Visual movement can be even more distracting: When people sense movement — especially in their peripheral vision — they tend to respond automatically by looking at it, making it hard to keep looking at the object they’re interested in. For example, revealing content near a button people are looking at can cause them to involuntarily look at the new content instead of the button.
+
+**Make it easy for people to look at an item by providing enough space around it.** Because eyes naturally tend to make small, quick adjustments in direction even while people are looking at one place, crowding UI objects together can make it difficult for people to look at one of them without jumping to another. You can help ensure that there’s enough space between interactive items by using a margin of at least 16 points around the bounds of each item or by placing items so that their centers are always at least 60 points apart. For additional layout guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout) and [Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout).
+
+**Avoid using a repeating pattern or texture that fills the field of view.** In some cases, people’s eyes can lock onto different elements in a pattern or texture, making the elements appear to have different depths. To avoid this effect, consider using the pattern in a smaller area.
+
+## [Encouraging interaction](https://developer.apple.com/design/human-interface-guidelines/eyes#Encouraging-interaction)
+
+**Consider using subtle visual cues to encourage people to look at the item they’re most likely to want.** For example, it often works well to place the item near the center of the field of view or use techniques like gentle motion, increased contrast, or variations in color or scale to draw people’s attention. In general, prefer cues that are noticeable without being flashy or harsh.
+
+**In general, give an interactive item a rounded shape.** People’s eyes tend to be drawn toward the corners in a shape, making it difficult to keep looking at the shape’s center. The more rounded an item’s shape, the easier it is for people to use their eyes to target it.
+
+
+
+
+
+
+
+
+
+**If you create an interactive component that consists of more than one element, be sure to provide an overall containing shape that visionOS can highlight.** For example, if an image and a label below it combine to act as one interactive component, you need to define a custom region that encompasses both elements, allowing visionOS to highlight the entire region when people look at either element.
+
+## [Custom hover effects](https://developer.apple.com/design/human-interface-guidelines/eyes#Custom-hover-effects)
+
+When it makes sense in your app or game, you can design a hover effect that animates in a custom way when people look at an element, including system-provided or custom UI elements and RealityKit entities. You can use a custom hover effect to replace or augment a standard effect.
+
+Before you start designing custom hover effects, it’s important to understand how they work. To enable a custom hover effect for an element, you create two states or appearances for it: one that shows the custom hover effect and one that doesn’t. When someone looks at the element in your app or game, the system applies your predefined hover effect in a process that’s outside of your software’s process. This means that you don’t know when the system applies a custom hover effect or what state the element is in at that moment. The out-of-process nature of a custom hover effect also means that it can’t run code that requires knowing when people are looking at the element.
+
+As an example that shows what a custom hover effect can and can’t do, consider a photo-browsing app where a photo’s custom effect displays a different symbol depending on whether people have added the photo to Favorites. The app specifies the appropriate symbol for a photo’s custom hover effect and the system displays the effect if people look at the photo. However, the hover effect can’t perform the favoriting action because the system doesn’t tell the app when someone is looking at the photo.
+
+**Prefer using a custom hover effect to emphasize or enhance a special moment in your experience.** People are accustomed to the standard hover effects that provide visual feedback or, in the case of tab bars or tooltips, additional information, so a custom hover effect can be especially noticeable. Adding too many custom hover effects — or using them when standard effects are sufficient — can dilute the impact of your design, distract people from their task, and even cause visual discomfort.
+
+**Choose the right delay.** An element’s custom hover effect can appear instantly, after a short delay, or after a slightly longer delay, depending on how you expect people to interact with the element.
+
+ * **No delay (default).** A custom hover effect that appears without delay tends to be especially useful when the effect is subtle or invites interaction, like when a knob appears on a slider.
+
+ * **Short delay.** Consider using a short delay to let people look at an element and quickly interact with it without waiting for the effect to appear; for example, the expansion of tabs in a tab bar works this way.
+
+ * **Long delay.** If your custom hover effect shows additional information, like when a tooltip appears below a button, a slightly longer delay can work well because most people won’t need to view the additional information every time.
+
+
+
+
+**Aim to keep one or more of the element’s primary views unchanged in both states of a custom hover effect.** When at least one primary view remains constant during a hover effect’s animation, it provides visual stability that can help people follow the element’s transition. If all of an element’s views move or change during a custom hover effect, it can disorient people and make them lose track of what’s happening.
+
+**Thoroughly test custom hover effects.** Testing is the only way to determine whether a custom hover effect looks good, responds appropriately, and makes your experience feel alive without distracting people. Aim to test your custom hover effects while wearing Apple Vision Pro so you can develop intuition about how to use them to enhance your experience.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/eyes#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, tvOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/eyes#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/eyes#Related)
+
+[Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences)
+
+[Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+[Spatial layout](https://developer.apple.com/design/human-interface-guidelines/spatial-layout)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/eyes#Developer-documentation)
+
+[Adopting best practices for privacy and user preferences](https://developer.apple.com/documentation/visionOS/adopting-best-practices-for-privacy) — visionOS
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/eyes#Videos)
+
+[ Design hover interactions for visionOS ](https://developer.apple.com/videos/play/wwdc2025/303)
+
+[ Design for spatial input ](https://developer.apple.com/videos/play/wwdc2023/10073)
+
+[ Design considerations for vision and motion ](https://developer.apple.com/videos/play/wwdc2023/10078)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/eyes#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| Added guidance for custom hover effects.
+March 29, 2024| Added artwork showing the visionOS hover effect.
+October 24, 2023| Clarified the difference between focus effects and the visionOS hover effect.
+June 21, 2023| New page.
+
diff --git a/web-app/public/skills/hig-inputs/references/focus-and-selection.md b/web-app/public/skills/hig-inputs/references/focus-and-selection.md
new file mode 100644
index 00000000..d1e8518c
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/focus-and-selection.md
@@ -0,0 +1,120 @@
+---
+title: "Focus and selection | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/focus-and-selection
+
+# Focus and selection
+
+Focus helps people visually confirm the object that their interaction targets.
+
+
+
+Focus supports simplified, component-based navigation. Using inputs like a remote, game controller, or keyboard, people bring focus to the components they want to interact with.
+
+In many cases, focusing an item also selects it. The exception is when automatic selection might cause a distracting context shift, like opening a new view. In tvOS, for example, people use the remote to move focus from item to item as they seek the one they want, but because selecting a focused item opens or activates it, selection requires a separate gesture.
+
+Different platforms communicate focus in different ways. For example, iPadOS and macOS show focus by drawing a ring around an item or highlighting it; tvOS generally uses the [parallax effect](https://developer.apple.com/design/human-interface-guidelines/images#Parallax-effect) to give the focused item an appearance of depth and liveliness. The combination of focus effects and interactions is sometimes called a _focus system_ or _focus model_.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Best-practices)
+
+**Rely on system-provided focus effects.** System-defined focus effects are precisely tuned to complement interactions with Apple devices, providing experiences that feel responsive, fluid, and lifelike. Incorporating system-provided focus behaviors gives your app consistency and predictability, helping people understand it quickly. Consider creating custom focus effects only if it’s absolutely necessary.
+
+**Avoid changing focus without people’s interaction.** People rely on the focus system to help them know where they are in your app. If you change focus without their interaction, people have to spend time finding the newly focused item, delaying their current task. The exception is when people are moving focus using an input device that lets them make discrete, directional movements — like a keyboard, remote, or game controller — and a previously focused item disappears. In this scenario, there are only a small number of items within one discrete step of the previously focused item, so moving focus to one of these remaining items ensures that the focus indicator is in a location people can easily find. When people aren’t moving focus by using such an input device, you can’t predict the item they’ll target next, so it’s generally best to simply hide the focus indicator when the focused object disappears.
+
+**Be consistent with the platform as you help people bring focus to items in your app.** For example, in iPadOS and macOS, a full keyboard access mode helps people use the keyboard to reach every control, so you only need to support focus for content elements like list items, text fields, and search fields, and not for controls like buttons, sliders, and toggles. In contrast, tvOS users rely on using directional gestures on a remote or game controller (or pressing the arrow keys on an attached keyboard) to reach every onscreen element, so you need to make sure that people can bring focus to every element in your app.
+
+**Indicate focus using visual appearances that are consistent with the platform.** For example, consider a window that contains a list of items. In iPadOS and macOS, the system draws focused list items using white text and a background highlight that matches the app’s accent color, drawing unfocused items using the standard text color and a gray background highlight (for developer guidance, see [`UICollectionView`](https://developer.apple.com/documentation/UIKit/UICollectionView) and [`NSTableView`](https://developer.apple.com/documentation/AppKit/NSTableView)).
+
+**In general, use a focus ring for a text or search field, but use a highlight in a list or collection.** Although you can use a focus ring to draw attention to an item that fills a cell, like a photo, it’s usually easier for people to view lists and collections when an entire row is highlighted.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Platform-considerations)
+
+ _Not supported in iOS or watchOS._
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#iPadOS)
+
+iPadOS 15 and later defines a focus system that supports keyboard interactions for navigating text fields, text views, and sidebars, in addition to various types of collection views and other custom views in your app.
+
+The iPadOS and tvOS focus systems are similar. People perform actions by moving a focus indicator to an item and then selecting it (for guidance, see [tvOS](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#tvOS)). Although the underlying system is the same, the user experiences are a little different. tvOS uses _directional focus_ , which means people can use the same interaction — that is, swiping the Siri Remote or using only the arrow keys on a connected keyboard — to navigate to every onscreen component. In contrast, iPadOS defines _focus groups_ , which represent specific areas within an app, like a sidebar, grid, or list. Using focus groups, iPadOS can support two different keyboard interactions.
+
+ * Pressing the Tab key moves focus among focus groups, letting people navigate to sidebars, grids, and other app areas.
+
+ * Pressing an arrow key supports a directional focus interaction that’s similar to tvOS, but limited to navigation among items in the same focus group. For example, people can use an arrow key to move through the items in a list or a sidebar.
+
+
+
+
+Onscreen components can indicate focus by using the halo effect or the highlighted appearance.
+
+The _halo_ focus effect — also known as the _focus ring_ — displays a customizable outline around the component. You can apply the halo effect to custom views and to fully opaque content within a collection or list cell, such as an image.
+
+
+
+**Customize the halo focus effect when necessary.** By default, the system uses an item’s shape to infer the shape of its halo. If the system-provided halo doesn’t give you the appearance you want, you can refine it to match contours like rounded corners or shapes defined by Bézier paths. You can also adjust a halo’s position if another component occludes or clips it. For example, you might need to ensure that a badge appears above the halo or that a parent view doesn’t clip it. For developer guidance, see [`UIFocusHaloEffect`](https://developer.apple.com/documentation/UIKit/UIFocusHaloEffect).
+
+
+
+The _highlighted_ appearance — in which the component’s text uses the app’s accent color — also indicates focus, but it’s not a focus effect. The highlight appearance occurs automatically when people select a collection view cell on which you’ve set content configurations (for developer guidance, see [`UICollectionViewCell`](https://developer.apple.com/documentation/UIKit/UICollectionViewCell)).
+
+
+
+**Ensure that focus moves through your custom views in ways that make sense.** As people continue pressing the Tab key, focus moves through focus groups in reading order: leading to trailing, and top to bottom. Although focus moves through system-provided views in ways that people expect, you might need to adjust the order in which the focus system visits your custom views. For example, if you want focus to move down through a vertical stack of custom views before it moves in the trailing direction to the next view, you need to identify the stack container as a single focus group. For developer guidance, see [`focusGroupIdentifier`](https://developer.apple.com/documentation/UIKit/UIFocusEnvironment/focusGroupIdentifier).
+
+**Adjust the priority of an item to reflect its importance within a focus group.** When a group receives focus, its _primary item_ automatically receives focus too, making it easy for people to select the item they’re most likely to want. You can make an item primary by increasing its priority. For developer guidance, see [`UIFocusGroupPriority`](https://developer.apple.com/documentation/UIKit/UIFocusGroupPriority).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#tvOS)
+
+**In a full-screen experience, let people use gestures to interact with the content, not to move focus.** When an item displays in full screen, it doesn’t show focus, so people naturally assume that their gestures will affect the object, and not its focus state.
+
+**Avoid displaying a pointer.** People expect to navigate a fixed number of items by changing focus, not by trying to drag a tiny pointer around a huge screen. While free-form movement might make sense during gameplay, such as when looking for a hidden object or flying a plane, use the focus model when people navigate menus and other interface elements. If your app requires a pointer, make sure it’s highly visible and feels integrated with your experience.
+
+**Design your interface to accommodate components in various focus states.** In tvOS, focusable items can have up to five different states, each of which is visually distinct. Because focusing an item often increases its scale, you need to supply assets for the larger, focused size to ensure they always look sharp, and you need to make sure the larger item doesn’t crowd the surrounding interface.
+
+State| Description
+---|---
+| The viewer hasn’t brought focus to the item. Unfocused items appear less prominent than focused items.
+| The viewer brings focus to the item. A focused item visually stands out from the other onscreen content through elevation to the foreground, illumination, and animation.
+| The viewer chooses the focused item. A focused item provides instant visual feedback when people choose it. For example, a button might briefly invert its colors and animate before it transitions to its selected appearance.
+| The viewer has chosen or activated the item in some way. For example, a heart-shaped button that people can use to favorite a photo might appear filled in the selected state and empty in the deselected state.
+| The viewer can’t bring focus to the item or choose it. An unavailable item appears inactive.
+
+For developer guidance, see [Adding user-focusable elements to a tvOS app](https://developer.apple.com/documentation/UIKit/adding-user-focusable-elements-to-a-tvos-app).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#visionOS)
+
+visionOS supports the same focus system as in iPadOS and tvOS, letting people use a connected input device like a keyboard or game controller to interact with apps and the system.
+
+Note
+
+When people look at a virtual object to identify it as the object they want to interact with, the system uses the _hover effect_ , not a focus effect, to provide visual feedback (for guidance, see [Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes)). The hover effect isn’t related to the focus system.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Related)
+
+[Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes)
+
+[Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Developer-documentation)
+
+[Focus Attributes](https://developer.apple.com/documentation/TVML/focus-attributes) — TVML
+
+[Focus-based navigation](https://developer.apple.com/documentation/UIKit/focus-based-navigation) — UIKit
+
+[About focus interactions for Apple TV](https://developer.apple.com/documentation/UIKit/about-focus-interactions-for-apple-tv) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Videos)
+
+[ Design for spatial input ](https://developer.apple.com/videos/play/wwdc2023/10073)
+
+[ Design for spatial user interfaces ](https://developer.apple.com/videos/play/wwdc2023/10076)
+
+[ Design for the iPadOS pointer ](https://developer.apple.com/videos/play/wwdc2020/10640)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Clarified the difference between focus effects and the visionOS hover effect.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-inputs/references/game-controls.md b/web-app/public/skills/hig-inputs/references/game-controls.md
new file mode 100644
index 00000000..afdb6f95
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/game-controls.md
@@ -0,0 +1,156 @@
+---
+title: "Game controls | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/game-controls
+
+# Game controls
+
+Precise, intuitive game controls enhance gameplay and can increase a player’s immersion in the game.
+
+
+
+On Apple platforms, a game can support input from physical game controllers or default system interactions, like touch, a remote, or a mouse and keyboard. Players might prefer to use physical game controllers, but there are two important reasons to also support a platform’s default interaction methods:
+
+ * Even though all platforms except watchOS support physical game controllers, not every player might have access to one.
+
+ * Players appreciate games that let them use the platform interaction method they’re most familiar with.
+
+
+
+
+To reach the widest audience and provide the best experience for each platform, keep these factors in mind when choosing the input methods to support.
+
+## [Touch controls](https://developer.apple.com/design/human-interface-guidelines/game-controls#Touch-controls)
+
+For iOS and iPadOS games, supporting touch interaction means that you can provide virtual controls on top of game content while also letting players interact with game elements by touching them directly. You can use the [Touch Controller](https://developer.apple.com/documentation/TouchController) framework to add these virtual controls to your game. Keep the following guidelines in mind to create an enjoyable touch control experience.
+
+**Determine whether it makes sense to display virtual controls on top of game content.** In general, virtual game controls benefit games that offer a large number of actions or require players to control movement. However, sometimes gameplay is more immersive and effective when players can interact directly with in-game objects. Look for opportunities to reduce the amount of virtual controls that overlap your game content by associating actions with in-game gestures instead. For example, consider letting players tap objects to select them instead of adding a virtual selection button.
+
+**Place virtual buttons where they’re easy to access.** Take into account the device’s boundaries and [safe areas](https://developer.apple.com/design/human-interface-guidelines/layout#Guides-and-safe-areas) as well as comfortable locations for controls. Make sure to position buttons where they don’t overlap system features like the Home indicator or Dynamic Island on iPhone. Place frequently used buttons near a player’s thumb, avoiding the circular regions where players expect movement and camera input to happen. Place secondary controls, like menus, at the top of the screen.
+
+
+
+Placing virtual controls within reach of people’s thumbs can make your game more comfortable to play.
+
+**Make sure controls are large enough.** Make sure frequently used controls are a minimum size of 44x44 pt, and less important controls, such as menus, are a minimum size of 28x28 pt to accommodate people’s fingers.
+
+**Always include visible and tactile press states.** A virtual control feels unresponsive without a visual and physical press state. Help players understand when they successfully interact with a button by adding a visual press state effect, such as a glow, that they can see even when their finger is covering the control. Combine this press state with sound and haptics to enhance the feeling of feedback. For guidance, see [Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics).
+
+
+
+**Use symbols that communicate the actions they perform.** Choose artwork that visually represents the action each button performs, such as a graphic of a weapon to represent an attack. Avoid using abstract shapes or controller-based naming like A, X, or R1 as artwork, which makes it harder for players to understand and remember what specific controls do.
+
+
+
+**Show and hide virtual controls to reflect gameplay.** Take advantage of the dynamic nature of touch controls and adapt what controls players see onscreen depending on their context. You can hide controls when an action isn’t available or relevant, letting you reduce clutter and help players concentrate on what’s important. For example, consider hiding movement controls until a player touches the screen to reduce the amount of UI overlapping your game content.
+
+ * Visible control
+ * Hidden control
+
+
+
+
+
+When the thumbstick moves to the right, it becomes more visible and shows a highlight to indicate the movement direction.
+
+
+
+When the thumbstick is at rest, the virtual control fades to show it’s not in use.
+
+**Combine functionality into a single control.** Consider redesigning game mechanics that require players to press multiple buttons at the same time or in a sequence. Leverage gestures such as double tap and touch and hold to provide different variations of the same action, such as touch and hold to use a special powered up version of an attack. For multiple actions, such as walking or sprinting, consider combining the actions into a single control.
+
+
+
+**Map movement and camera controls to predictable behavior.** Typically, players expect to control movement using the left side of their screen, and control camera direction using the right side of their screen. Maximize the amount of space that players can control both movement and the camera direction by using as large of an input area as possible. For movement control, opt to show a virtual thumbstick wherever the player lands their thumb instead of a static thumbstick position. For camera control, opt to use direct touch to pan the camera instead of a virtual thumbstick.
+
+
+
+## [Physical controllers](https://developer.apple.com/design/human-interface-guidelines/game-controls#Physical-controllers)
+
+**Support the platform’s default interaction method.** A game controller is an optional purchase, but every iPhone and iPad has a touchscreen, every Mac has a keyboard and a trackpad or mouse, every Apple TV has a remote, and every Apple Vision Pro responds to gestures people make with their eyes and hands. If you support game controllers, try to make sure there’s a fallback for using the platform’s default interaction method. For developer guidance, see [Adding touch controls to games that support game controllers in iOS](https://developer.apple.com/documentation/GameController/adding-touch-controls-to-games-that-support-game-controllers-in-ios).
+
+**Tell people about game controller requirements.** In tvOS and visionOS, you can require the use of a physical game controller. The App Store displays a “Game Controller Required” badge to help people identify such apps. Remember that people can open your game at any time, even without a connected controller. If your app requires a game controller, check for its presence and gracefully prompt people to connect one. For developer guidance, see [`GCRequiresControllerUserInteraction`](https://developer.apple.com/documentation/BundleResources/Information-Property-List/GCRequiresControllerUserInteraction).
+
+**Automatically detect whether a controller is paired.** Instead of having players manually set up a physical game controller, you can automatically detect whether a controller is paired and get its profile. For developer documentation, see [Game Controller](https://developer.apple.com/documentation/GameController).
+
+
+
+**Customize onscreen content to match the connected game controller.** To simplify your game’s code, the Game Controller framework assigns standard names to controller elements based on their placement, but the colors and symbols on an actual game controller may differ. Be sure to use the connected controller’s labeling scheme when referring to controls or displaying related content in your interface. For developer guidance, see [`GCControllerElement`](https://developer.apple.com/documentation/GameController/GCControllerElement).
+
+**Map controller buttons to expected UI behavior.** Outside of gameplay, players expect to navigate your game’s UI in a way that matches the familiar behavior of the platform they’re playing on. When not controlling gameplay, follow these conventions across all Apple platforms:
+
+Button| Expected behavior for UI
+---|---
+A| Activates a control
+B| Cancels an action or returns to previous screen
+X| —
+Y| —
+Left shoulder| Navigates left to a different screen or section
+Right shoulder| Navigates right to a different screen or section
+Left trigger| —
+Right trigger| —
+Left/right thumbstick| Moves selection
+Directional pad| Moves selection
+Home/logo| Reserved for system controls
+Menu| Opens game settings or pauses gameplay
+
+**Support multiple connected controllers.** If there are multiple controllers connected, use labels and glyphs that match the one that the player is actively using. If your game supports multiplayer, use the appropriate labels and symbols when referring to a specific player’s controller. If you need to refer to buttons on multiple controllers, consider listing them together.
+
+**Prefer using symbols, not text, to refer to game controller elements.** The Game Controller framework makes [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) available for most elements, including the buttons on various brands of game controllers. Using symbols instead of text descriptions can be especially helpful for players who aren’t experienced with controllers because it doesn’t require them to hunt for a specific button label during gameplay.
+
+
+
+## [Keyboards](https://developer.apple.com/design/human-interface-guidelines/game-controls#Keyboards)
+
+Keyboard players appreciate using keyboard bindings to speed up their interactions with apps and games.
+
+**Prioritize single-key commands.** Single-key commands are generally easier and faster for players to perform, especially while they’re simultaneously using a mouse or trackpad. For example, you might use the first letter of a menu item as a shortcut, such as I for Inventory or M for Map; you might also map the game’s main action to the Space bar, taking advantage of the key’s relatively large size.
+
+**Test key binding comfort game using an Apple keyboard.** For example, if a key binding uses the Control key (^) on a non-Apple keyboard, consider remapping it to the Command key (⌘) on an Apple keyboard. On Apple keyboards, the Command key is conveniently located next to the Space bar, making it especially easy to reach when players are using the W, A, S, and D keys.
+
+**Take the proximity of keys into account.** For example, if players navigate using the W, A, S, and D keys, consider using nearby keys to define other high-value commands. Similarly, if there’s a group of closely related actions, it can work well to map their bindings to keys that are physically close together, such as using the number keys for inventory categories.
+
+**Let players customize key bindings.** Although players tend to expect a reasonable set of defaults, many people need to customize a game’s key bindings for personal comfort and play style.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/game-controls#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or tvOS. Not supported in watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/game-controls#visionOS)
+
+**Match spatial game controller behavior to hand input.** In addition to supporting a wide array of wireless game controllers, your visionOS game can also support spatial game controllers such as PlayStation VR2 Sense controller. Allow players to interact with your game in a similar manner to how they interact using their hands. Specifically, support looking at an object and pressing the controller’s left or right trigger button to indirectly interact, or reaching out and pressing the left or right trigger button to directly interact. For more information, see [visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/game-controls#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/game-controls#Related)
+
+[Designing for games](https://developer.apple.com/design/human-interface-guidelines/designing-for-games)
+
+[Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+[Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards)
+
+[Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/game-controls#Developer-documentation)
+
+[Create games for Apple platforms](https://developer.apple.com/games/)
+
+[Touch Controller](https://developer.apple.com/documentation/TouchController)
+
+[Game Controller](https://developer.apple.com/documentation/GameController)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/game-controls#Videos)
+
+[ Design advanced games for Apple platforms ](https://developer.apple.com/videos/play/wwdc2024/10085)
+
+[ Tap into virtual and physical game controllers ](https://developer.apple.com/videos/play/wwdc2021/10081)
+
+[ Explore game input in visionOS ](https://developer.apple.com/videos/play/wwdc2024/10094)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/game-controls#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated touch control best practices, updated game controller mapping for UI, and added guidance for spatial game controller support in visionOS.
+June 10, 2024| Added guidance for supporting touch controls and changed title from Game controllers.
+
diff --git a/web-app/public/skills/hig-inputs/references/gestures.md b/web-app/public/skills/hig-inputs/references/gestures.md
new file mode 100644
index 00000000..5dd2b692
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/gestures.md
@@ -0,0 +1,208 @@
+---
+title: "Gestures | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/gestures
+
+# Gestures
+
+A gesture is a physical motion that a person uses to directly affect an object in an app or game on their device.
+
+
+
+Depending on the device they’re using, people can make gestures on a touchscreen, in the air, or on a range of input devices such as a trackpad, mouse, remote, or game controller that includes a touch surface.
+
+Every platform supports basic gestures like tap, swipe, and drag. Although the precise movements that make up basic gestures can vary per platform and input device, people are familiar with the underlying functionality of these gestures and expect to use them everywhere. For a list of these gestures, see [Standard gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/gestures#Best-practices)
+
+**Give people more than one way to interact with your app.** People commonly prefer or need to use other inputs — such as their voice, keyboard, or Switch Control — to interact with their devices. Don’t assume that people can use a specific gesture to perform a given task. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**In general, respond to gestures in ways that are consistent with people’s expectations.** People expect most gestures to work the same regardless of their current context. For example, people expect tap to activate or select an object. Avoid using a familiar gesture like tap or swipe to perform an action that’s unique to your app; similarly, avoid creating a unique gesture to perform a standard action like activating a button or scrolling a long view.
+
+**Handle gestures as responsively as possible.** Useful gestures enhance the experience of direct manipulation and provide immediate feedback. As people perform a gesture in your app, provide feedback that helps them predict its results and, if necessary, communicates the extent and type of movement required to complete the action.
+
+**Indicate when a gesture isn’t available.** If you don’t clearly communicate why a gesture doesn’t work, people might think your app has frozen or they aren’t performing the gesture correctly, leading to frustration. For example, if someone tries to drag a locked object, the UI may not indicate that the object’s position has been locked; or if they try to activate an unavailable button, the button’s unavailable state may not be clearly distinct from its available state.
+
+## [Custom gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Custom-gestures)
+
+**Add custom gestures only when necessary.** Custom gestures work best when you design them for specialized tasks that people perform frequently and that aren’t covered by existing gestures, like in a game or drawing app. If you decide to implement a custom gesture, make sure it’s:
+
+ * Discoverable
+
+ * Straightforward to perform
+
+ * Distinct from other gestures
+
+ * Not the only way to perform an important action in your app or game
+
+
+
+
+**Make custom gestures easy to learn.** Offer moments in your app to help people quickly learn and perform custom gestures, and make sure to test your interactions in real use scenarios. If you’re finding it difficult to use simple language and graphics to describe a gesture, it may mean people will find the gesture difficult to learn and perform.
+
+**Use shortcut gestures to supplement standard gestures, not replace them.** While you may supply a custom gesture to quickly access parts of your app, people also need simple, familiar ways to navigate and perform actions, even if it means an extra tap or two. For example, in an app that supports navigation through a hierarchy of views, people expect to find a Back button in a top toolbar that lets them return to the previous view with a single tap. To help accelerate this action, many apps also offer a shortcut gesture — such as swiping from the side of a window or touchscreen — while continuing to provide the Back button.
+
+**Avoid conflicting with gestures that access system UI.** Several platforms offer gestures for accessing system behaviors, like edge swiping in watchOS or rolling your hand over to access system overlays in visionOS. It’s important to avoid defining custom gestures that might conflict with these interactions, as people expect these controls to work consistently. In specific circumstances within games or immersive experiences, developers can work around this area by deferring the system gesture. For more information, see the platform considerations for iOS, iPadOS, watchOS, and visionOS.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/gestures#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/gestures#iOS-iPadOS)
+
+In addition to the [standard gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures) supported in all platforms, iOS and iPadOS support a few other gestures that people expect.
+
+Gesture| Common action
+---|---
+Three-finger swipe| Initiate undo (left swipe); initiate redo (right swipe).
+Three-finger pinch| Copy selected text (pinch in); paste copied text (pinch out).
+Four-finger swipe (iPadOS only)| Switch between apps.
+Shake| Initiate undo; initiate redo.
+
+**Consider allowing simultaneous recognition of multiple gestures if it enhances the experience.** Although simultaneous gestures are unlikely to be useful in nongame apps, a game might include multiple onscreen controls — such as a joystick and firing buttons — that people can operate at the same time. For guidance on integrating touchscreen input with Apple Pencil input in your iPadOS app, see [Apple Pencil and Scribble](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/gestures#macOS)
+
+People primarily interact with macOS using a [keyboard](https://developer.apple.com/design/human-interface-guidelines/keyboards) and mouse. In addition, they can make [standard gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures) on a Magic Trackpad, Magic Mouse, or a [game controller](https://developer.apple.com/design/human-interface-guidelines/game-controls) that includes a touch surface.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/gestures#tvOS)
+
+People expect to use [standard gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures) to navigate tvOS apps and games with a compatible remote, Siri Remote, or [game controller](https://developer.apple.com/design/human-interface-guidelines/game-controls) that includes a touch surface. For guidance, see [Remotes](https://developer.apple.com/design/human-interface-guidelines/remotes).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS)
+
+visionOS supports two categories of gestures: indirect and direct.
+
+People use an _indirect_ gesture by looking at an object to target it, and then manipulating that object from a distance — indirectly — with their hands. For example, a person can look at a button to focus it and select it by quickly tapping their finger and thumb together. Indirect gestures are comfortable to perform at any distance, and let people quickly change focus between different objects and select items with minimal movement.
+
+Video with custom controls.
+
+Content description: A recording showing a closeup view of the top portion of a window in visionOS. A button in the window becomes highlighted. A picture-in-picture window is visible in the bottom-right corner of the recording. It shows a person's hand performing the indirect tap gesture. In response to the gesture, the highlighted button in the window activates.
+
+Play
+
+People use a _direct_ gesture to physically touch an interactive object. For example, people can directly type on the visionOS keyboard by tapping the virtual keys. Direct gestures work best when they are within reach. Because people may find it tiring to keep their arms raised for extended periods, direct gestures are best for infrequent use. visionOS also supports direct versions of all standard gestures, allowing people the choice to interact directly or indirectly with any standard component.
+
+Video with custom controls.
+
+Content description: A recording showing a table with a vertical stack of three virtual cubic blocks on it in visionOS. A person moves their hand toward the blocks from right to left, and their extended fingers touch and push aside the center block. The center block falls to the side, and the other block also tumbles onto the tabletop.
+
+Play
+
+Here are the standard direct gestures people use in visionOS; see [Specifications](https://developer.apple.com/design/human-interface-guidelines/gestures#Specifications) for a list of standard indirect gestures.
+
+Direct gesture| Common use
+---|---
+Touch| Directly select or activate an object.
+Touch and hold| Open a contextual menu.
+Touch and drag| Move an object to a new location.
+Double touch| Preview an object or file; select a word in an editing context.
+Swipe| Reveal actions and controls; dismiss views; scroll.
+With two hands, pinch and drag together or apart| Zoom in or out.
+With two hands, pinch and drag in a circular motion| Rotate an object.
+
+**Support standard gestures everywhere you can.** For example, as soon as someone looks at an object in your app or game, tap is the first gesture they’re likely to make when they want to select or activate it. Even if you also support custom gestures, supporting standard gestures such as tap helps people get comfortable with your app or game quickly.
+
+**Offer both indirect and direct interactions when possible.** Prefer indirect gestures for UI and common components like buttons. Reserve direct gestures and custom gestures for objects that invite close-up interaction or specific motions in a game or interactive experience.
+
+**Avoid requiring specific body movements or positions for input.** Not all people can perform specific body movements or position themselves in certain ways at all times, whether due to disability, spatial constraints, or other environmental factors. If your experience requires movement, consider supporting alternative inputs to let people choose the interaction method that works best for them.
+
+#### [Designing custom gestures in visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#Designing-custom-gestures-in-visionOS)
+
+If you want to offer a specific interaction for your experience that people can’t perform using an existing system gesture, consider designing a custom gesture. To offer this type of interaction, your app needs to be running in a Full Space, and you must request people’s permission to access information about their hands. For developer guidance, see [Setting up access to ARKit data](https://developer.apple.com/documentation/visionOS/setting-up-access-to-arkit-data).
+
+
+
+**Prioritize comfort.** Continually test ergonomics of all interactions that require custom gestures. A custom interaction that requires people to keep their arms raised for even a little while can be physically tiring, and repeating very similar movements many times in succession can stress people’s muscles and joints.
+
+**Carefully consider complex custom gestures that involve multiple fingers or both hands.** People may not always have both hands available when using your app or game. If you require a more complex gesture for your experience, consider also offering an alternative that requires less movement.
+
+**Avoid custom gestures that require using a specific hand.** It can increase someone’s cognitive load if they need to remember which hand to use to trigger a custom gesture. It may also make your experience less welcoming to people with strong hand-dominance or limb differences.
+
+#### [Working with system overlays in visionOS](https://developer.apple.com/design/human-interface-guidelines/gestures#Working-with-system-overlays-in-visionOS)
+
+In visionOS 2 and later, people can look at the palm of one hand and use gestures to quickly access system overlays for Home and Control Center. These interactions are available systemwide, and are reserved solely for accessing system overlays.
+
+Note
+
+The system overlay is the default method of accessing Control Center in visionOS 2 and later. The visionOS 1 behavior (looking upward) remains available as an accessibility setting.
+
+When designing apps and games that use custom gestures or anchor content to a person’s hands, it’s important to take interactions with the system overlays into consideration.
+
+**Reserve the area around a person’s hand for system overlays and their related gestures.** If possible, don’t anchor content to a person’s hands or wrists. If you’re designing a game that involves hand-anchored content, place it outside of the immediate area of someone’s hand to avoid colliding with the Home indicator.
+
+The area reserved for interacting with system overlays.
+
+A person looks at their palm to reveal the Home indicator.
+
+A person turns their hand to reveal the status bar, and can tap to open Control Center.
+
+**Consider deferring the system overlay behavior when designing an immersive app or game.** In certain circumstances, you may not want the Home indicator to appear when someone looks at the palm of their hand. For example, a game that uses virtual hands or gloves may want to keep someone within the world of the story, even if they happen to look at their hands from different angles. In such cases, when your app is running in a Full Space, you can choose to require a tap to reveal the Home indicator instead. For developer guidance, see [`persistentSystemOverlays(_:)`](https://developer.apple.com/documentation/SwiftUI/View/persistentSystemOverlays\(_:\)).
+
+Default behavior in the Shared Space
+
+Default behavior in a Full Space
+
+Deferred behavior in a Full Space
+
+Note
+
+Apps and games that you built for visionOS 1 defer the system overlay behavior by default. When a person looks at their palm with your app running in a Full Space, the Home indicator won’t appear unless they tap first.
+
+**Use caution when designing custom gestures that involve a rolling motion of the hand, wrist, and forearm.** This specific motion is reserved for revealing system overlays. Since system overlays always display on top of app content and your app isn’t aware of when they’re visible, it’s important to test any custom gestures or content that might conflict.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/gestures#watchOS)
+
+#### [Double tap](https://developer.apple.com/design/human-interface-guidelines/gestures#Double-tap)
+
+In watchOS 11 and later, people can use the double-tap gesture to scroll through lists and scroll views, and to advance between vertical tab views. Additionally, you can specify a toggle or button as the primary action in your app, or in your widget or Live Activity when the system displays it in the Smart Stack. Double-tapping in a view with a primary action highlights the control and then performs the action. The system also supports double tap for custom actions that you offer in [notifications](https://developer.apple.com/design/human-interface-guidelines/notifications), where it acts on the first nondestructive action in the notification.
+
+**Avoid setting a primary action in views with lists, scroll views, or vertical tabs.** This conflicts with the default navigation behaviors that people expect when they double-tap.
+
+**Choose the button that people use most commonly as the primary action in a view.** Double tap is helpful in a nonscrolling view when it performs the action that people use the most. For example, in a media controls view, you could assign the primary action to the play/pause button. For developer guidance, see [`handGestureShortcut(_:isEnabled:)`](https://developer.apple.com/documentation/SwiftUI/View/handGestureShortcut\(_:isEnabled:\)) and [`primaryAction`](https://developer.apple.com/documentation/SwiftUI/HandGestureShortcut/primaryAction).
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/gestures#Specifications)
+
+### [Standard gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Standard-gestures)
+
+The system provides APIs that support the familiar gestures people use with their devices, whether they use a touchscreen, an indirect gesture in visionOS, or an input device like a trackpad, mouse, remote, or game controller. For developer guidance, see [Gestures](https://developer.apple.com/documentation/SwiftUI/Gestures).
+
+Gesture| Supported in| Common action
+---|---|---
+Tap| iOS, iPadOS, macOS, tvOS, visionOS, watchOS| Activate a control; select an item.
+Swipe| iOS, iPadOS, macOS, tvOS, visionOS, watchOS| Reveal actions and controls; dismiss views; scroll.
+Drag| iOS, iPadOS, macOS, tvOS, visionOS, watchOS| Move a UI element.
+Touch (or pinch) and hold| iOS, iPadOS, tvOS, visionOS, watchOS| Reveal additional controls or functionality.
+Double tap| iOS, iPadOS, macOS, tvOS, visionOS, watchOS| Zoom in; zoom out if already zoomed in; perform a primary action on Apple Watch Series 9 and Apple Watch Ultra 2.
+Zoom| iOS, iPadOS, macOS, tvOS, visionOS| Zoom a view; magnify content.
+Rotate| iOS, iPadOS, macOS, tvOS, visionOS| Rotate a selected item.
+
+For guidance on supporting additional gestures and button presses on specific input devices, see [Pointing devices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices), [Remotes](https://developer.apple.com/design/human-interface-guidelines/remotes), and [Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/gestures#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/gestures#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Eyes](https://developer.apple.com/design/human-interface-guidelines/eyes)
+
+[Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/gestures#Developer-documentation)
+
+[Gestures](https://developer.apple.com/documentation/SwiftUI/Gestures) — SwiftUI
+
+[`UITouch`](https://developer.apple.com/documentation/UIKit/UITouch) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/gestures#Videos)
+
+[ Enhance your UI animations and transitions ](https://developer.apple.com/videos/play/wwdc2024/10145)
+
+[ Design for spatial input ](https://developer.apple.com/videos/play/wwdc2023/10073)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/gestures#Change-log)
+
+Date| Changes
+---|---
+September 9, 2024| Added guidance for working with system overlays in visionOS and made organizational updates.
+September 15, 2023| Updated specifications to include double tap in watchOS.
+June 21, 2023| Changed page title from Touchscreen gestures and updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-inputs/references/gyro-and-accelerometer.md b/web-app/public/skills/hig-inputs/references/gyro-and-accelerometer.md
new file mode 100644
index 00000000..ac65f94d
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/gyro-and-accelerometer.md
@@ -0,0 +1,40 @@
+---
+title: "Gyroscope and accelerometer | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer
+
+# Gyroscope and accelerometer
+
+On-device gyroscopes and accelerometers can supply data about a device’s movement in the physical world.
+
+
+
+You can use accelerometer and gyroscope data to provide experiences based on real-time, motion-based information in apps and games that run in iOS, iPadOS, and watchOS. tvOS apps can use gyroscope data from the Siri Remote. For developer guidance, see [Core Motion](https://developer.apple.com/documentation/CoreMotion).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Best-practices)
+
+**Use motion data only to offer a tangible benefit to people.** For example, a fitness app might use the data to provide feedback about people’s activity and general health, and a game might use the data to enhance gameplay. Avoid gathering data simply to have the data.
+
+Important
+
+If your experience needs to access motion data from a device, you must provide copy that explains why. The first time your app or game tries to access this type of data, the system includes your copy in a permission request, where people can grant or deny access.
+
+**Outside of active gameplay, avoid using accelerometers or gyroscopes for the direct manipulation of your interface.** Some motion-based gestures may be difficult to replicate precisely, may be physically challenging for some people to perform, and may affect battery usage.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Developer-documentation)
+
+[Getting processed device-motion data](https://developer.apple.com/documentation/CoreMotion/getting-processed-device-motion-data) — Core Motion
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer#Videos)
+
+[ Measure health with motion ](https://developer.apple.com/videos/play/wwdc2021/10287)
+
diff --git a/web-app/public/skills/hig-inputs/references/keyboards.md b/web-app/public/skills/hig-inputs/references/keyboards.md
new file mode 100644
index 00000000..7e85e5df
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/keyboards.md
@@ -0,0 +1,234 @@
+---
+title: "Keyboards | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/keyboards
+
+# Keyboards
+
+A physical keyboard can be an essential input device for entering text, playing games, controlling apps, and more.
+
+
+
+People can connect a physical keyboard to any device except Apple Watch. Mac users tend to use a physical keyboard all the time and iPad users often do. Many games work well with a physical keyboard, and people can prefer using one instead of a [virtual keyboard](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards) when entering a lot of text.
+
+Keyboard users often appreciate using keyboard shortcuts to speed up their interactions with apps and games. A _keyboard shortcut_ is a combination of a primary key and one or more modifier keys (Control, Option, Shift, and Command) that map to a specific command. A keyboard shortcut in a game — called a _key binding_ — often consists of a single key.
+
+Apple defines standard keyboard shortcuts to work consistently across the system and most apps, helping people transfer their knowledge to new experiences. Some apps define custom keyboard shortcuts for the app-specific commands people use most; most games define custom key bindings that make it quick and efficient to use the keyboard to control the game. For guidance, see [Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls#Keyboards).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/keyboards#Best-practices)
+
+**Support Full Keyboard Access when possible.** Available in iOS, iPadOS, macOS, and visionOS, Full Keyboard Access lets people navigate and activate windows, menus, controls, and system features using only the keyboard. To test Full Keyboard Access in your app or game, turn it on in the Accessibility area of the system-supplied Settings app. For developer guidance, see [Support Full Keyboard Access in your iOS app](https://developer.apple.com/videos/play/wwdc2021/10120/) and [`isFullKeyboardAccessEnabled`](https://developer.apple.com/documentation/AppKit/NSApplication/isFullKeyboardAccessEnabled).
+
+Important
+
+Although iPadOS supports keyboard navigation in text fields, text views, and sidebars, and provides APIs you can use to support it in collection views and other custom views, avoid supporting keyboard navigation for controls, such as buttons, segmented controls, and switches. Instead, let people use Full Keyboard Access to activate controls, navigate to all onscreen components, and perform gesture-based interactions like drag and drop. For guidance, see [iPadOS](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection#iPadOS); for developer guidance, see [Focus-based navigation](https://developer.apple.com/documentation/uikit/focus-based_navigation).
+
+**Respect standard keyboard shortcuts.** While using most apps, people generally expect to rely on the standard keyboard shortcuts that work in other apps and throughout the system. If your app offers a unique action that people perform frequently, prefer creating a [custom](https://developer.apple.com/design/human-interface-guidelines/keyboards#Custom-keyboard-shortcuts) shortcut for it instead of repurposing a standard one that people associate with a different action. While playing a game, people may expect to use certain standard keyboard shortcuts — such as Command–Q to quit the game — but they also expect to be able to modify each game’s key bindings to fit their personal play style. For guidance, see [Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls#Keyboards).
+
+## [Standard keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Standard-keyboard-shortcuts)
+
+**In general, don’t repurpose standard keyboard shortcuts for custom actions.** People can get confused when the shortcuts they know work differently in your app or game. Only consider redefining a standard shortcut if its action doesn’t make sense in your experience. For example, if your app doesn’t support text editing, it doesn’t need a text-styling command like Italic, so you might repurpose Command–I for an action that has more relevance, like Get Info.
+
+People expect each of the following standard keyboard shortcuts to perform the action listed in the table below.
+
+Primary key| Keyboard shortcut| Action
+---|---|---
+Space| Command-Space| Show or hide the Spotlight search field.
+| Shift-Command-Space| Varies.
+| Option-Command-Space| Show the Spotlight search results window.
+| Control-Command-Space| Show the Special Characters window.
+Tab| Shift-Tab| Navigate through controls in a reverse direction.
+| Command-Tab| Move forward to the next most recently used app in a list of open apps.
+| Shift-Command-Tab| Move backward through a list of open apps (sorted by recent use).
+| Control-Tab| Move focus to the next group of controls in a dialog or the next table (when Tab moves to the next cell).
+| Control-Shift-Tab| Move focus to the previous group of controls.
+Esc| Esc| Cancel the current action or process.
+Esc| Option-Command-Esc| Open the Force Quit dialog.
+Eject| Control-Command-Eject| Quit all apps (after changes have been saved to open documents) and restart the computer.
+| Control-Option-Command-Eject| Quit all apps (after changes have been saved to open documents) and shut the computer down.
+F1| Control-F1| Toggle full keyboard access on or off.
+F2| Control-F2| Move focus to the menu bar.
+F3| Control- F3| Move focus to the Dock.
+F4| Control-F4| Move focus to the active (or next) window.
+| Control-Shift-F4| Move focus to the previously active window.
+F5| Control-F5| Move focus to the toolbar.
+| Command-F5| Turn VoiceOver on or off.
+F6| Control-F6| Move focus to the first (or next) panel.
+| Control-Shift-F6| Move focus to the previous panel.
+F7| Control-F7| Temporarily override the current keyboard access mode in windows and dialogs.
+F8| | Varies.
+F9| | Varies.
+F10| | Varies.
+F11| | Show desktop.
+F12| | Hide or display Dashboard.
+Grave accent (`)| Command-Grave accent| Activate the next open window in the frontmost app.
+| Shift-Command-Grave accent| Activate the previous open window in the frontmost app.
+| Option-Command-Grave accent| Move focus to the window drawer.
+Hyphen (-)| Command-Hyphen| Decrease the size of the selection.
+| Option-Command-Hyphen| Zoom out when screen zooming is on.
+Left bracket ({)| Command-Left bracket| Left-align a selection.
+Right bracket (})| Command-Right bracket| Right-align a selection.
+Pipe (|)| Command-Pipe| Center-align a selection.
+Colon (:)| Command-Colon| Display the Spelling window.
+Semicolon (;)| Command-Semicolon| Find misspelled words in the document.
+Comma (,)| Command-Comma| Open the app’s settings window.
+| Control-Option-Command-Comma| Decrease screen contrast.
+Period (.)| Command-Period| Cancel an operation.
+| Control-Option-Command-Period| Increase screen contrast.
+Question mark (?)| Command-Question mark| Open the app’s Help menu.
+Forward slash (/)| Option-Command-Forward slash| Turn font smoothing on or off.
+Equal sign (=)| Shift-Command-Equal sign| Increase the size of the selection.
+| Option-Command-Equal sign| Zoom in when screen zooming is on.
+3| Shift-Command-3| Capture the screen to a file.
+| Control-Shift-Command-3| Capture the screen to the Clipboard.
+4| Shift-Command-4| Capture a selection to a file.
+| Control-Shift-Command-4| Capture a selection to the Clipboard.
+8| Option-Command-8| Turn screen zooming on or off.
+| Control-Option-Command-8| Invert the screen colors.
+A| Command-A| Select every item in a document or window, or all characters in a text field.
+| Shift-Command-A| Deselect all selections or characters.
+B| Command-B| Boldface the selected text or toggle boldfaced text on and off.
+C| Command-C| Copy the selection to the Clipboard.
+| Shift-Command-C| Display the Colors window.
+| Option-Command-C| Copy the style of the selected text.
+| Control-Command-C| Copy the formatting settings of the selection and store on the Clipboard.
+D| Option-Command-D| Show or hide the Dock.
+| Control-Command-D| Display the definition of the selected word in the Dictionary app.
+E| Command-E| Use the selection for a find operation.
+F| Command-F| Open a Find window.
+| Option-Command-F| Jump to the search field control.
+| Control-Command-F| Enter full screen.
+G| Command-G| Find the next occurrence of the selection.
+| Shift-Command-G| Find the previous occurrence of the selection.
+H| Command-H| Hide the windows of the currently running app.
+| Option-Command-H| Hide the windows of all other running apps.
+I| Command-I| Italicize the selected text or toggle italic text on or off.
+| Command-I| Display an Info window.
+| Option-Command-I| Display an inspector window.
+J| Command-J| Scroll to a selection.
+M| Command-M| Minimize the active window to the Dock.
+| Option-Command-M| Minimize all windows of the active app to the Dock.
+N| Command-N| Open a new document.
+O| Command-O| Display a dialog for choosing a document to open.
+P| Command-P| Display the Print dialog.
+| Shift-Command-P| Display the Page Setup dialog.
+Q| Command-Q| Quit the app.
+| Shift-Command-Q| Log out the person currently logged in.
+| Option-Shift-Command-Q| Log out the person currently logged in without confirmation.
+S| Command-S| Save a new document or save a version of a document.
+| Shift-Command-S| Duplicate the active document or initiate a Save As.
+T| Command-T| Display the Fonts window.
+| Option-Command-T| Show or hide a toolbar.
+U| Command-U| Underline the selected text or turn underlining on or off.
+V| Command-V| Paste the Clipboard contents at the insertion point.
+| Shift-Command-V| Paste as (Paste as Quotation, for example).
+| Option-Command-V| Apply the style of one object to the selection.
+| Option-Shift-Command-V| Paste the Clipboard contents at the insertion point and apply the style of the surrounding text to the inserted object.
+| Control-Command-V| Apply formatting settings to the selection.
+W| Command-W| Close the active window.
+| Shift-Command-W| Close a file and its associated windows.
+| Option-Command-W| Close all windows in the app.
+X| Command-X| Remove the selection and store on the Clipboard.
+Z| Command-Z| Undo the previous operation.
+| Shift-Command-Z| Redo (when Undo and Redo are separate commands rather than toggled using Command-Z).
+Right arrow| Command-Right arrow| Change the keyboard layout to current layout of Roman script.
+| Shift-Command-Right arrow| Extend selection to the next semantic unit, typically the end of the current line.
+| Shift-Right arrow| Extend selection one character to the right.
+| Option-Shift-Right arrow| Extend selection to the end of the current word, then to the end of the next word.
+| Control-Right arrow| Move focus to another value or cell within a view, such as a table.
+Left arrow| Command-Left arrow| Change the keyboard layout to current layout of system script.
+| Shift-Command-Left arrow| Extend selection to the previous semantic unit, typically the beginning of the current line.
+| Shift-Left arrow| Extend selection one character to the left.
+| Option-Shift-Left arrow| Extend selection to the beginning of the current word, then to the beginning of the previous word.
+| Control-Left arrow| Move focus to another value or cell within a view, such as a table.
+Up arrow| Shift-Command-Up arrow| Extend selection upward in the next semantic unit, typically the beginning of the document.
+| Shift-Up arrow| Extend selection to the line above, to the nearest character boundary at the same horizontal location.
+| Option-Shift-Up arrow| Extend selection to the beginning of the current paragraph, then to the beginning of the next paragraph.
+| Control-Up arrow| Move focus to another value or cell within a view, such as a table.
+Down arrow| Shift-Command-Down arrow| Extend selection downward in the next semantic unit, typically the end of the document.
+| Shift-Down arrow| Extend selection to the line below, to the nearest character boundary at the same horizontal location.
+| Option-Shift-Down arrow| Extend selection to the end of the current paragraph, then to the end of the next paragraph (include the paragraph terminator, such as Return, in cut, copy, and paste operations).
+| Control-Down arrow| Move focus to another value or cell within a view, such as a table.
+
+The system also defines several keyboard shortcuts for use with localized versions of the system, localized keyboards, keyboard layouts, and input methods. These shortcuts don’t correspond directly to menu commands.
+
+Keyboard shortcut| Action
+---|---
+Control-Space| Toggle between the current and last input source.
+Control-Option-Space| Switch to the next input source in the list.
+[Modifier key]-Command-Space| Varies.
+Command-Right arrow| Change keyboard layout to current layout of Roman script.
+Command-Left arrow| Change keyboard layout to current layout of system script.
+
+## [Custom keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Custom-keyboard-shortcuts)
+
+**Define custom keyboard shortcuts for only the most frequently used app-specific commands.** People appreciate using keyboard shortcuts for actions they perform frequently, but defining too many new shortcuts can make your app seem difficult to learn.
+
+**Use modifier keys in ways that people expect.** For example, pressing Command while dragging moves items as a group, and pressing Shift while drag-resizing constrains resizing to the item’s aspect ratio. In addition, holding an arrow key moves the selected item by the smallest app-defined unit of distance until people release the key.
+
+Here are the modifier keys and the symbols that represent them.
+
+Modifier key| Symbol| Recommended usage
+---|---|---
+Command| | Prefer the Command key as the main modifier key in a custom keyboard shortcut.
+Shift| | Prefer the Shift key as a secondary modifier that complements a related shortcut.
+Option| | Use the Option modifier sparingly for less-common commands or power features.
+Control| | Avoid using the Control key as a modifier. The system uses Control in many systemwide features and shortcuts, like moving focus or capturing screenshots.
+
+Tip
+
+Some languages require modifier keys to generate certain characters. For example, on a French keyboard, Option-5 generates the “{“ character. It’s usually safe to use the Command key as a modifier, but avoid using an additional modifier with characters that aren’t available on all keyboards. If you must use a modifier other than Command, prefer using it only with the alphabetic characters.
+
+**List modifier keys in the correct order.** If you use more than one modifier key in a custom shortcut, always list them in this order: Control, Option, Shift, Command.
+
+**Avoid adding Shift to a shortcut that uses the upper character of a two-character key.** People already understand that they must hold the Shift key to type the upper character of a two-character key, so it’s clearer to simply list the upper character in the shortcut. For example, the keyboard shortcut for Hide Status Bar is Command-Slash, whereas the keyboard shortcut for Help is Command-Question mark, not Shift-Command-Slash.
+
+**Let the system localize and mirror your keyboard shortcuts as needed.** The system automatically localizes a shortcut’s primary and modifier keys to support the currently connected keyboard; if your app or game switches to a right-to-left layout, the system automatically mirrors the shortcut. For guidance, see [Right to left](https://developer.apple.com/design/human-interface-guidelines/right-to-left).
+
+**Avoid creating a new shortcut by adding a modifier to an existing shortcut for an unrelated command.** For example, because people are accustomed to using Command-Z for undoing an action, it would be confusing to use Shift-Command-Z as the shortcut for a command that’s unrelated to undo and redo.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/keyboards#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or tvOS. Not supported in watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/keyboards#visionOS)
+
+In visionOS, an app’s keyboard shortcuts appear in the shortcut interface that displays when people hold the Command key on a connected keyboard. Similar in organization to an app’s [menu bar menus](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar) on iPad or Mac, the shortcut interface on Apple Vision Pro displays app commands in familiar system-defined menu categories such as File, Edit, and View. Unlike menu bar menus, the shortcut interface displays all relevant categories in one view, listing within each category only available commands that also have shortcuts.
+
+**Write descriptive shortcut titles.** Because the shortcut interface displays a flat list of all items in each category, submenu titles aren’t available to provide context for their child items. Make sure each shortcut title is descriptive enough to convey its action without the additional context a submenu title might provide. For developer guidance, see [`discoverabilityTitle`](https://developer.apple.com/documentation/UIKit/UIKeyCommand/discoverabilityTitle).
+
+**Recognize that people see an overlay when they use a physical keyboard with your visionOS app or game.** When people connect a physical keyboard while using your visionOS app or game, the system displays a virtual keyboard overlay that provides typing completion and other controls.
+
+Video with custom controls.
+
+Content description: A recording that shows two hands typing on a physical keyboard while the person runs an app in visionOS. A virtual window is visible above the physical keyboard, and displays the entered text and suggestions.
+
+Play
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/keyboards#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/keyboards#Related)
+
+[Virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+[Pointing devices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/keyboards#Developer-documentation)
+
+[`KeyboardShortcut`](https://developer.apple.com/documentation/SwiftUI/KeyboardShortcut) — SwiftUI
+
+[Input events](https://developer.apple.com/documentation/SwiftUI/Input-events) — SwiftUI
+
+[Handling key presses made on a physical keyboard](https://developer.apple.com/documentation/UIKit/handling-key-presses-made-on-a-physical-keyboard) — UIKit
+
+[Mouse, Keyboard, and Trackpad](https://developer.apple.com/documentation/AppKit/mouse-keyboard-and-trackpad) — AppKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/keyboards#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Moved game-specific key bindings guidance to the Game controls page.
+June 10, 2024| Added game-specific guidance and made organizational updates.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-inputs/references/nearby-interactions.md b/web-app/public/skills/hig-inputs/references/nearby-interactions.md
new file mode 100644
index 00000000..b68624b1
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/nearby-interactions.md
@@ -0,0 +1,70 @@
+---
+title: "Nearby interactions | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/nearby-interactions
+
+# Nearby interactions
+
+Nearby interactions support on-device experiences that integrate the presence of people and objects in the nearby environment.
+
+
+
+A great nearby interaction feels intuitive and natural to people, because it builds on their innate awareness of the world around them. For example, a person playing music on their iPhone can continue listening on their HomePod mini when they bring the devices close together, simply by transferring the audio output from their iPhone to the HomePod mini.
+
+Nearby interactions are available on devices that support Ultra Wideband technology (to learn more, see [Ultra Wideband availability](https://support.apple.com/en-us/HT212274)), and rely on the [Nearby Interaction](https://developer.apple.com/documentation/NearbyInteraction) framework. Before participating in nearby interaction experiences, people grant permission for their device to interact while they’re using your app. The Nearby Interaction APIs help you preserve people’s privacy by relying on randomly generated device identifiers that last only as long as the interaction session your app initiates.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Best-practices)
+
+**Consider a task from the perspective of the physical world to find inspiration for a nearby interaction.** For example, although people can easily use your app’s UI to transfer a song from their iPhone to their HomePod mini, initiating the transfer by bringing the devices close together makes the task feel rooted in the physical world. Discovering the physical actions that inform the concept of a task can help you create an engaging experience that makes performing it feel easy and natural.
+
+**Use distance, direction, and context to inform an interaction.** Although your app may get information from a variety of sources, prioritizing nearby, contextually relevant information can help you deliver experiences that feel organic. For example, if people want to share content with a friend in a crowded room, the iOS share sheet can suggest a likely recipient by using on-device knowledge about the person’s most frequent and recent contacts. Combining this knowledge with information from nearby devices that include the U1 chip can let the share sheet improve the experience by suggesting the closest contact the person is facing.
+
+**Consider how changes in physical distance can guide a nearby interaction.** In the physical world, people generally expect their perception of an object to sharpen as they get closer to it. A nearby interaction can mirror this experience by providing feedback that changes with the proximity of an object. For example, when people use iPhone to find an AirTag, the display transitions from a directional arrow to a pulsing circle as they get closer.
+
+**Provide continuous feedback.** Continuous feedback reflects the dynamism of the physical world and strengthens the connection between a nearby interaction and the task people are performing. For example, when looking for a lost item in Find My, people get continuous updates that communicate the item’s direction and proximity. Keep people engaged by providing uninterrupted feedback that responds to their movements.
+
+**Consider using multiple feedback types to create a holistic experience.** Fluidly transitioning among visual, audible, and haptic feedback can help a nearby interaction’s task feel more engaging and real. Using more than one type of feedback also lets you vary the experience to coordinate with both the task and the current context. For example, while people are interacting with the device screen, visual feedback makes sense; while people are interacting with their environment, audible and haptic feedback often work better.
+
+**Avoid using a nearby interaction as the only way to perform a task.** You can’t assume that everyone can experience a nearby interaction, so it’s essential to provide alternative ways to get things done in your app.
+
+## [Device usage](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Device-usage)
+
+**Encourage people to hold the device in portrait orientation.** Holding a device in landscape can decrease the accuracy and availability of information about the distance and relative direction of other devices. If you support only portrait orientation while your nearby interaction feature runs, prefer giving people implicit, visual feedback on how to hold the device for an optimal experience; when possible, avoid explicitly telling people to hold the device in portrait.
+
+**Design for the device’s directional field of view.** Nearby interaction relies on a hardware sensor with a specific field of view similar to that of the Ultra Wide camera in iPhone 11 and later. If a participating device is outside of this field of view, your app might receive information about its distance, but not its relative direction.
+
+**Help people understand how intervening objects can affect the nearby interaction experience in your app.** When other people, animals, or sufficiently large objects come between two participating devices, the accuracy or availability of distance and direction information can decrease. Consider adding advice on avoiding this situation to onboarding or tutorial content you present.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Platform-considerations)
+
+ _No additional considerations for iPadOS. Not supported in macOS, tvOS, or visionOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#iOS)
+
+On iPhone, Nearby Interaction APIs provide a peer device’s distance and direction.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#watchOS)
+
+On Apple Watch, Nearby Interaction APIs provide a peer device’s distance. Also, all watchOS apps participating in a nearby interaction experience must be in the foreground.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Developer-documentation)
+
+[Nearby Interaction](https://developer.apple.com/documentation/NearbyInteraction)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Videos)
+
+[ Design for spatial interaction ](https://developer.apple.com/videos/play/wwdc2021/10245)
+
+[ Meet Nearby Interaction ](https://developer.apple.com/videos/play/wwdc2020/10668)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Changed page title from Spatial interactions.
+
diff --git a/web-app/public/skills/hig-inputs/references/pointing-devices.md b/web-app/public/skills/hig-inputs/references/pointing-devices.md
new file mode 100644
index 00000000..8a5362d8
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/pointing-devices.md
@@ -0,0 +1,237 @@
+---
+title: "Pointing devices | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/pointing-devices
+
+# Pointing devices
+
+People can use a pointing device like a trackpad or mouse to navigate the interface and initiate actions.
+
+
+
+People appreciate the precision and flexibility that pointing devices offer. On a Mac, people typically expect to combine a pointing device with a keyboard as they navigate apps and the system. On iPad and Apple Vision Pro, a pointing device gives people an additional way to interact with apps and content, without replacing touch, eyes, or gestures.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Best-practices)
+
+**Be consistent when responding to mouse and trackpad gestures.** People expect most gestures to work the same throughout the system, regardless of the app or game they’re using. On a Mac, for example, people rely on the “Swipe between pages” gesture to behave the same way whether they’re browsing individual document pages, webpages, or images.
+
+**Avoid redefining systemwide trackpad gestures.** Even in a game that uses app-specific gestures in a custom way, people expect systemwide gestures to be available; for example, people expect to make familiar gestures to reveal the Dock or Mission Control in macOS. Remember that Mac users can customize the gestures for performing systemwide actions.
+
+**Provide a consistent experience in your app, whether people are using gestures, eyes, a pointing device, or a keyboard.** People expect to move fluidly between multiple types of input, and they don’t want to learn different interactions for each mode or for each app they use.
+
+**Let people use the pointer to reveal and hide controls that automatically minimize or fade out.** In iPadOS, for example, people can reveal the minimized Safari toolbar by holding the pointer over it (the toolbar minimizes again when the pointer moves away). People can also move the pointer to reveal or hide playback controls while they watch a full-screen video.
+
+**Provide a consistent experience when people press and hold a modifier key while interacting with objects in your app.** For example, if people can duplicate an object by pressing and holding the Option key while they drag that object, ensure the result is the same whether they drag using touch or the pointer.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Platform-considerations)
+
+ _No additional considerations for iOS. Not supported in tvOS or watchOS._
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#iPadOS)
+
+iPadOS builds on the traditional pointer experience, automatically adapting the pointer to the current context and providing rich visual feedback at a level of precision that enhances productivity and simplifies common tasks on a touchscreen device. The iPadOS pointing system gives people an additional way to interact with apps and content — it doesn’t replace touch.
+
+**Allow multiple selection in custom views when necessary.** In iPadOS 15 and later, people can click and drag the pointer over multiple items to select them. As people use the pointer in this way, it expands into a visible rectangle that selects the items it encompasses. Standard nonlist collection views support this interaction by default; if you want to support multiple selection in custom views, you need to implement it yourself. For developer guidance, see [`UIBandSelectionInteraction`](https://developer.apple.com/documentation/UIKit/UIBandSelectionInteraction).
+
+**Distinguish between pointer and finger input only if it provides value.** For example, a scrubber can give people an additional way to target a location in a video when they’re using the pointer. In this scenario, people can drag the playhead using either the pointer or touch, but they can use the pointer to click a precise seek destination.
+
+#### [Pointer shape and content effects](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Pointer-shape-and-content-effects)
+
+iPadOS integrates the appearance and behavior of both the pointer and the element it moves over, bringing focus to the item the pointer is targeting. You can support the system-provided pointer effects or modify them to suit your experience.
+
+By default, the pointer’s shape is a circle, but it can display a system-defined or custom shape when people move it over specific elements or regions. For example, the pointer automatically uses the familiar I-beam shape when people move it over a text-entry area.
+
+Video with custom controls.
+
+Content description: A video snippet showing the bottom half of a new event popover in Calendar. At the beginning of the video, the pointer is within the URL field and it uses the I-beam shape. As the pointer moves between the URL and Notes fields, it briefly reverts to its default circular shape; when the pointer enters the Notes field, it uses the I-beam shape again.
+
+Play
+
+With a _content effect_ , the UI element or region beneath the pointer can also change its appearance when people hold the pointer over it. Depending on the type of content effect, the pointer can retain its current shape or transform into a shape that integrates with the element’s new appearance.
+
+iPadOS defines three content effects that bring focus to different types of interactive elements in your app: highlight, lift, and hover.
+
+The _highlight_ effect transforms the pointer into a translucent, rounded rectangle that acts as a background for a control and includes a gentle parallax. The subtle highlighting and movement bring focus to the control without distracting people from their task. By default, iPadOS applies the highlight effect to bar buttons, tab bars, segmented controls, and edit menus.
+
+Video with custom controls.
+
+Content description: A video snippet showing a small area at the bottom of a Photos window. Nature photos that show purple flowers, rocks in a stream, and grass are visible just above the tab bar, which shows the Photos and For You tabs. At the beginning of the video, the Photos tab is highlighted. Because bar items receive the highlight effect, the pointer becomes the highlighted rounded rectangle that surrounds the tab’s glyph and title. The highlighted rounded rectangle slides from one tab to the other as the pointer moves.
+
+Play
+
+The _lift_ effect combines a subtle parallax with the appearance of elevation to make an element seem like it’s floating above the screen. As the pointer fades out beneath the element, iPadOS creates the illusion of lift by scaling the element up while adding a shadow below it and a soft specular highlight on top of it. By default, iPadOS applies the lift effect to app icons and to buttons in Control Center.
+
+Video with custom controls.
+
+Content description: A video snippet showing the left end of the Dock in front of the Home Screen. From the left, the visible app icons are Messages, Safari, Music, Mail, and Files. As the pointer moves across the first three icons from the left, it disappears beneath each icon in turn, lifting it slightly and letting it return to its original position before moving to the next icon.
+
+Play
+
+_Hover_ is a generic effect that lets you apply custom scale, tint, or shadow values to an element as the pointer moves over it. The hover effect combines your custom values to bring focus to an item, but it doesn’t transform the default pointer shape.
+
+Video with custom controls.
+
+Content description: A video snippet showing an alert floating above the top half of a new event popover in Calendar. The alert contains text that reads Are you sure you want to discard this new event? and a button titled Discard Changes. As the pointer moves into the alert button, the button background darkens.
+
+Play
+
+#### [Pointer accessories](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Pointer-accessories)
+
+Pointer accessories are visual indicators that help people understand how they can use the pointer to interact with the current UI element. For example, a pointer approaching a resizable element might display small arrows to indicate that the element allows resizing along a certain axis.
+
+Unlike pointer shapes and content effects, accessories are secondary items that can combine with any pointer to communicate additional information. For developer guidance, see [`UIPointerAccessory`](https://developer.apple.com/documentation/UIKit/UIPointerAccessory).
+
+**Use clear, simple images to create custom accessories.** A pointer accessory is small, so it’s essential to create an image that communicates the pointer interaction without using too many details.
+
+**Consider using the accessory transition to signal a change in an element’s state or behavior.** In addition to animating the appearance and disappearance of pointer accessories, the system also animates the transitions among accessory shapes and positions that can accompany content effects. For example, you could communicate that an add action has become unavailable by transitioning the pointer accessory from the `plus` symbol to the `circle.slash` symbol.
+
+#### [Pointer magnetism](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Pointer-magnetism)
+
+iPadOS helps people use the pointer to target an element by making the element appear to attract the pointer. People can experience this magnetic effect when they move the pointer close to an element and when they flick the pointer toward an element.
+
+When people move the pointer close to an element, the system starts transforming the pointer’s shape as soon as it reaches the element’s hit region. Because an element’s hit region typically extends beyond its visible boundaries, the pointer begins to transform before it appears to touch the element itself, creating the illusion that the element is pulling the pointer toward it.
+
+Video with custom controls.
+
+Content description: A video snippet showing an area at the bottom of Clock. The World Clock tab is selected and clock images and information for San Francisco, New York, and London are partially visible in the window. As the pointer moves in the tab bar, its highlighted rounded rectangle appearance seems to show a slight resistance as it slides from the World Clock tab to the Alarm tab and back again.
+
+Play
+
+When people flick the pointer toward an element, iPadOS examines the pointer’s trajectory to discover the element that’s the most likely target. When there’s an element in the pointer’s path, the system uses magnetism to pull the pointer toward the element’s center.
+
+By default, iPadOS applies magnetism to elements that use the lift effect (like app icons) and the highlight effect (like bar buttons), but not to elements that use hover. Because an element that supports hover doesn’t transform the default pointer shape, adding magnetism could be jarring and might make people feel that they’ve lost control of the pointer.
+
+The system also applies magnetism to text-entry areas, where it can help people avoid skipping to another line if they make unintended vertical movements while they’re selecting text.
+
+#### [Standard pointers and effects](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Standard-pointers-and-effects)
+
+**When possible, support the system-provided content effects.** People quickly become accustomed to the content effects they see throughout the system and generally expect their experience to apply to every app they use. To provide a consistent user experience, align your interactions with the design intent of each effect. Specifically:
+
+ * Use highlight for a small element that has a transparent background.
+
+ * Use lift for a small element that has an opaque background.
+
+ * Use hover for large elements and customize the scale, tint, and shadow attributes as needed (for guidance, see [Customizing pointers](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Customizing-pointers)).
+
+
+
+
+**Prefer the system-provided pointer appearances for standard buttons and text-entry areas.** You can help people feel more comfortable with your app when the pointer behaves in ways they expect.
+
+**Add padding around interactive elements to create comfortable hit regions.** You might need to experiment to determine the right size for an element’s hit region. If the hit region is too small, it can make people feel that they have to be extra precise when interacting with the element. On the other hand, when an element’s hit region is too large, people can feel that it takes a lot of effort to pull the pointer away from the element. In general, it works well to add about 12 points of padding around elements that include a bezel; for elements without a bezel, it works well to add about 24 points of padding around the element’s visible edges.
+
+
+
+
+
+
+
+**Create contiguous hit regions for custom bar buttons.** If there’s space between the hit regions of adjacent buttons in a bar, people may experience a distracting motion when the pointer reverts briefly to its default shape as it moves between buttons.
+
+**Specify the corner radius of a nonstandard element that receives the lift effect.** With the system-provided lift effect, the pointer transforms to match the element’s shape as it fades out. By default, the pointer uses the system-defined corner radius to transform into a rounded rectangle. If your element is a different shape — if it’s a circle, for example — you need to provide the radius so the pointer can animate seamlessly into the shape of the element. For developer guidance, see [`UIPointerShape.roundedRect(_:radius:)`](https://developer.apple.com/documentation/UIKit/UIPointerShape-swift.enum/roundedRect\(_:radius:\)).
+
+#### [Customizing pointers](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Customizing-pointers)
+
+**Prefer system-provided pointer effects for custom elements that behave like standard elements.** When a custom element behaves like a standard one, people generally expect to interact with it using familiar pointer interactions. For example, if buttons in a custom toolbar don’t use the standard highlight effect, people might think they’re broken.
+
+**Use pointer effects in consistent ways throughout your app.** For example, if your app helps people draw, provide a similar pointer experience for every drawing area in your app so that people can apply the knowledge they gain in one area to the others.
+
+**Avoid creating gratuitous pointer and content effects.** People notice when the appearance of the pointer or the UI element beneath it changes, and they expect the changes to be useful. Creating a purely decorative pointer effect can distract and even irritate people without providing any practical value.
+
+**Keep custom pointer shapes simple.** Ideally, the pointer’s shape signals the action people can take in the current context without drawing too much attention to itself. If people don’t instantly understand your custom pointer shape, they’re likely to waste time trying to discover what the shape means.
+
+**Consider enhancing the pointer experience by displaying custom annotations that provide useful information.** For example, you could display X and Y values when people hold the pointer over a graphing area in your app. Keynote uses annotations to display the current width and height of a resizable image.
+
+
+
+**Avoid displaying instructional text with a pointer.** A pointer that displays instructional text can make an app seem complicated and difficult to use. Instead of providing instructions, prioritize clarity and simplicity in your interface, so that people can quickly grasp how to use your app whether they’re using the pointer or touching the screen.
+
+**Consider the interplay of shadow, scale, and element spacing when defining custom hover effects.** In general, reserve scaling for elements that can increase in size without crowding nearby elements. For example, scaling doesn’t work well for a table row because a row can’t expand without overlapping adjacent rows. For an element that has little space around it, consider using a hover effect that includes tint, but not scale and shadow. Note that it doesn’t work well to use shadow without including scale, because an unscaled element doesn’t appear to get closer to the viewer even when its shadow implies that it’s elevated above the screen.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#macOS)
+
+macOS supports a wide range of standard mouse and trackpad interactions that people can customize. For example, when a click or gesture isn’t a primary way to interact with content, people can often turn it on or off based on their current workflow. People can also choose specific regions of a mouse or trackpad to invoke secondary clicks, and select specific finger combinations and movements for certain gestures.
+
+Click or gesture| Expected behavior| Mouse| Trackpad
+---|---|---|---
+Primary click| Select or activate an item, such as a file or button.| ●| ●
+Secondary click| Reveal contextual menus.| ●| ●
+Scrolling| Move content up, down, left, or right within a view.| ●| ●
+Smart zoom| Zoom in or out on content, such as a web page or PDF.| ●| ●
+Swipe between pages| Navigate forward or backward between individually displayed pages.| ●| ●
+Swipe between full-screen apps| Navigate forward or backward between full-screen apps and spaces.| ●| ●
+Mission Control (double-tap the mouse with two fingers or swipe up on the trackpad with three or four fingers)| Activate Mission Control.| ●| ●
+Lookup and data detectors (force click with one finger or tap with three fingers)| Display a lookup window above selected content.| | ●
+Tap to click| Perform the primary click action using a tap rather than a click.| | ●
+Force click| Click then press firmly to display a Quick Look window or lookup window above selected content. Apply a variable amount of pressure to affect pressure-sensitive controls, such as variable speed media controls.| | ●
+Zoom in or out (pinch with two fingers)| Zoom in or out.| | ●
+Rotate (move two fingers in a circular motion)| Rotate content, such as an image.| | ●
+Notification Center (swipe from the edge of the trackpad)| Display Notification Center.| | ●
+App Exposé (swipe down with three or four fingers)| Display the current app’s windows in Exposé.| | ●
+Launchpad (pinch with thumb and three fingers)| Display the Launchpad.| | ●
+Show Desktop (spread with thumb and three fingers)| Slide all windows out of the way to reveal the desktop.| | ●
+
+#### [Pointers](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Pointers)
+
+macOS offers a variety of standard pointer styles, which your app can use to communicate the interactive state of an interface element or the result of a drag operation.
+
+Pointer| Name| Meaning| AppKit API
+---|---|---|---
+| Arrow| Standard pointer for selecting and interacting with content and interface elements.| [`arrow`](https://developer.apple.com/documentation/AppKit/NSCursor/arrow)
+| Closed hand| Dragging to reposition the display of content within a view—for example, dragging a map around in Maps.| [`closedHand`](https://developer.apple.com/documentation/AppKit/NSCursor/closedHand)
+| Contextual menu| A contextual menu is available for the content below the pointer. This pointer is generally shown only when the Control key is pressed.| [`contextualMenu`](https://developer.apple.com/documentation/AppKit/NSCursor/contextualMenu)
+| Crosshair| Precise rectangular selection is possible, such as when viewing an image in Preview.| [`crosshair`](https://developer.apple.com/documentation/AppKit/NSCursor/crosshair)
+| Disappearing item| A dragged item will disappear when dropped. If the item references an original item, the original is unaffected. For example, when dragging a mailbox out of the favorites bar in Mail, the original mailbox isn’t removed.| [`disappearingItem`](https://developer.apple.com/documentation/AppKit/NSCursor/disappearingItem)
+| Drag copy| Duplicates a dragged—not moved—item when dropped into the destination. Appears when pressing the Option key during a drag operation.| [`dragCopy`](https://developer.apple.com/documentation/AppKit/NSCursor/dragCopy)
+| Drag link| During a drag and drop operation, creates an alias of the selected file when dropped. The alias points to the original file, which remains unmoved. Appears when pressing the Option and Command keys during a drag operation.| [`dragLink`](https://developer.apple.com/documentation/AppKit/NSCursor/dragLink)
+| Horizontal I beam| Selection and insertion of text is possible in a horizontal layout, such as a TextEdit or Pages document.| [`iBeam`](https://developer.apple.com/documentation/AppKit/NSCursor/iBeam)
+| Open hand| Dragging to reposition content within a view is possible.| [`openHand`](https://developer.apple.com/documentation/AppKit/NSCursor/openHand)
+| Operation not allowed| A dragged item can’t be dropped in the current location.| [`operationNotAllowed`](https://developer.apple.com/documentation/AppKit/NSCursor/operationNotAllowed)
+| Pointing hand| The content beneath the pointer is a URL link to a webpage, document, or other item.| [`pointingHand`](https://developer.apple.com/documentation/AppKit/NSCursor/pointingHand)
+| Resize down| Resize or move a window, view, or element downward.| [`resizeDown`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeDown)
+| Resize left| Resize or move a window, view, or element to the left.| [`resizeLeft`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeLeft)
+| Resize left/right| Resize or move a window, view, or element to the left or right.| [`resizeLeftRight`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeLeftRight)
+| Resize right| Resize or move a window, view, or element to the right.| [`resizeRight`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeRight)
+| Resize up| Resize or move a window, view, or element upward.| [`resizeUp`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeUp)
+| Resize up/down| Resize or move a window, view, or element upward or downward.| [`resizeUpDown`](https://developer.apple.com/documentation/AppKit/NSCursor/resizeUpDown)
+| Vertical I beam| Selection and insertion of text is possible in a vertical layout.| [`iBeamCursorForVerticalLayout`](https://developer.apple.com/documentation/AppKit/NSCursor/iBeamCursorForVerticalLayout)
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#visionOS)
+
+In visionOS, people can attach an external pointing device or keyboard, and use both devices while they continue to use their eyes and hands. If people look at an element and then move the pointer, the system brings focus to the element under the pointer. Your app doesn’t have to do anything to support this behavior.
+
+When a pointing device is attached, the area people are looking at determines the pointer’s context. For example, when people shift their eyes from one window to another, the pointer’s context seamlessly transitions to the new window.
+
+Video with custom controls.
+
+Content description: A recording that shows a pointer moving around, highlighting items, and scrolling content within a Safari window in visionOS. A picture-in-picture window is visible in the bottom left corner of the recording. It shows a person's hand operating a trackpad next to a keyboard outside the field of view. The person's gestures on the trackpad correspond to the pointer movements.
+
+Play
+
+When people use an attached pointing device that supports gestures, like a trackpad or mouse, the pointer hides while people are gesturing, minimizing visual distraction. In this scenario, the pointer remains hidden until people move it, when it reappears in the location they’re looking at.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Related)
+
+[Entering data](https://developer.apple.com/design/human-interface-guidelines/entering-data)
+
+[Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Developer-documentation)
+
+[Input events](https://developer.apple.com/documentation/SwiftUI/Input-events) — SwiftUI
+
+[Pointer interactions](https://developer.apple.com/documentation/UIKit/pointer-interactions) — UIKit
+
+[Mouse, Keyboard, and Trackpad](https://developer.apple.com/documentation/AppKit/mouse-keyboard-and-trackpad) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Videos)
+
+[ Design for the iPadOS pointer ](https://developer.apple.com/videos/play/wwdc2020/10640)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-inputs/references/remotes.md b/web-app/public/skills/hig-inputs/references/remotes.md
new file mode 100644
index 00000000..57a455f9
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/remotes.md
@@ -0,0 +1,67 @@
+---
+title: "Remotes | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/remotes
+
+# Remotes
+
+The Siri Remote is the primary input method for Apple TV, helping people feel connected to onscreen content from across the room.
+
+
+
+In addition to several specific buttons, the Siri Remote combines a clickpad and touch surface to support familiar gestures like swipe and press that people use to navigate tvOS apps, browse channels and content, play and pause media, and make selections.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/remotes#Best-practices)
+
+**Prefer using standard gestures to perform standard actions.** Unless people are actively playing a game, they expect the remote to behave in standard ways in every app they use. Redefining or repurposing standard remote behaviors can cause confusion and add complexity to your experience. For guidance, see [Gestures](https://developer.apple.com/design/human-interface-guidelines/remotes#Gestures).
+
+**Be consistent with the tvOS focus experience.** The [focus experience](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection) forges a strong connection between people and the content they’re viewing. Reinforce this link in your app by ensuring that you combine gestures with the focus experience in ways that are familiar to people, such as always moving focus in the same direction as the gesture.
+
+**Provide clear feedback that shows people what happens when they make gestures in your app.** For example, lightly resting a thumb on the remote shows people where to swipe down so that they can reveal an info area.
+
+**Define new gestures only when it makes sense in your app.** Within gameplay, for example, custom gestures can be a fun part of the experience. In most other situations, people expect to use standard gestures and may not appreciate having to discover or remember new ones.
+
+**Differentiate between press and tap, and avoid responding to an inadvertent tap.** Pressing is an intentional action, and it works well for choosing a button, confirming a selection, and initiating an action during gameplay. Tap gestures are fine for navigation or showing additional information, but keep in mind that people might cause an inadvertent tap when they rest a thumb on the remote, pick it up, move it around, or hand it to someone else, so it often works well to avoid responding to taps during live video playback.
+
+**Consider using the position of a tap to aid with navigation or gameplay.** The remote can differentiate between up, down, left, and right tap gestures on the touch surface. Respond to positional taps only if it makes sense in the context of your app and if such behavior is intuitive and discoverable.
+
+**In almost all cases, open the parent of the current screen when people press the Back button.** At the top level of an app or game, the parent is the Apple TV Home Screen; within an app, the parent is defined by the app hierarchy, and isn’t necessarily the previous screen. The exception to this standard behavior is when people are actively playing a game, where it can be easy to accidentally press the Back button repeatedly. To avoid disrupting gameplay in this scenario, respond to the Back button by opening an in-game pause menu that lets people use a different interaction to navigate back to the game’s main menu. When the in-game pause menu is open, respond to a Back-button press by closing the menu and resuming the game. Note that people press and hold the Back button to go to the Home Screen from any location. For guidance, see [Buttons](https://developer.apple.com/design/human-interface-guidelines/remotes#Buttons).
+
+**Respond correctly to the Play/Pause button during media playback.** When playing music or video, people expect pressing the Play/Pause button to play, pause, or resume playback.
+
+## [Gestures](https://developer.apple.com/design/human-interface-guidelines/remotes#Gestures)
+
+The clickpad’s touch surface detects swipes and presses.
+
+**Swipe.** Swiping lets people scroll effortlessly through large numbers of items with movement that starts fast and then slows down, based on the strength of the swipe. When people swipe up or down on the edge of the remote, they can speed through items very quickly.
+
+**Press.** People press to activate a control or select an item. Also, people press before swiping to activate scrubbing mode.
+
+## [Buttons](https://developer.apple.com/design/human-interface-guidelines/remotes#Buttons)
+
+Ensure that your app or game responds to specific presses in the following ways.
+
+Button or area| Expected behavior in an app| Expected behavior in a game
+---|---|---
+Touch surface (swipe)| Navigates. Changes focus.| Performs directional pad behavior.
+Touch surface (press)| Activates a control or an item. Navigates deeper.| Performs primary button behavior.
+Back| Returns to previous screen. Exits to Apple TV Home Screen.| Pauses/resumes gameplay. Returns to previous screen, exits to main game menu, or exits to Apple TV Home Screen.
+Play/Pause| Activates media playback. Pauses/resumes media playback.| Performs secondary button behavior. Skips intro video.
+
+## [Compatible remotes](https://developer.apple.com/design/human-interface-guidelines/remotes#Compatible-remotes)
+
+Some remotes that are compatible with Apple TV include buttons for browsing live TV or other channel-based content. For example, a remote might include a button people can use to open an electronic program guide (EPG) and other buttons they can use to browse the guide or change channels. For developer guidance, see [Providing Channel Navigation](https://developer.apple.com/documentation/TVServices/providing-channel-navigation); for design guidance, see [EPG experience](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#EPG-experience).
+
+**If your live-viewing app provides an EPG, respond to a remote’s EPG-browsing buttons in ways people expect.** When people press a “guide” or “browse” button, they expect your EPG to open. While they’re viewing your EPG, people expect to navigate through it by pressing a “page up” or “page down” button. Avoid responding to these buttons in other ways while people are browsing the EPG. On the Siri Remote and compatible remotes, people can also tap on the upper or lower area of the Touch surface to browse the EPG. If your app doesn’t support an EPG experience, the system routes these button presses to the default guide app on the viewer’s device.
+
+**While your content plays, respond to a compatible remote’s “page up” or “page down” button by changing the channel.** People expect these buttons to behave differently when they switch between viewing content and browsing an EPG.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/remotes#Platform-considerations)
+
+ _Not supported in iOS, iPadOS, macOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/remotes#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/remotes#Related)
+
+[Use your Siri Remote or Apple TV Remote with Apple TV](https://support.apple.com/en-us/HT205305)
+
diff --git a/web-app/public/skills/hig-inputs/references/spatial-interactions.md b/web-app/public/skills/hig-inputs/references/spatial-interactions.md
new file mode 100644
index 00000000..00edbfd8
--- /dev/null
+++ b/web-app/public/skills/hig-inputs/references/spatial-interactions.md
@@ -0,0 +1,70 @@
+---
+title: "Nearby interactions | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/spatial-interactions
+
+# Nearby interactions
+
+Nearby interactions support on-device experiences that integrate the presence of people and objects in the nearby environment.
+
+
+
+A great nearby interaction feels intuitive and natural to people, because it builds on their innate awareness of the world around them. For example, a person playing music on their iPhone can continue listening on their HomePod mini when they bring the devices close together, simply by transferring the audio output from their iPhone to the HomePod mini.
+
+Nearby interactions are available on devices that support Ultra Wideband technology (to learn more, see [Ultra Wideband availability](https://support.apple.com/en-us/HT212274)), and rely on the [Nearby Interaction](https://developer.apple.com/documentation/NearbyInteraction) framework. Before participating in nearby interaction experiences, people grant permission for their device to interact while they’re using your app. The Nearby Interaction APIs help you preserve people’s privacy by relying on randomly generated device identifiers that last only as long as the interaction session your app initiates.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Best-practices)
+
+**Consider a task from the perspective of the physical world to find inspiration for a nearby interaction.** For example, although people can easily use your app’s UI to transfer a song from their iPhone to their HomePod mini, initiating the transfer by bringing the devices close together makes the task feel rooted in the physical world. Discovering the physical actions that inform the concept of a task can help you create an engaging experience that makes performing it feel easy and natural.
+
+**Use distance, direction, and context to inform an interaction.** Although your app may get information from a variety of sources, prioritizing nearby, contextually relevant information can help you deliver experiences that feel organic. For example, if people want to share content with a friend in a crowded room, the iOS share sheet can suggest a likely recipient by using on-device knowledge about the person’s most frequent and recent contacts. Combining this knowledge with information from nearby devices that include the U1 chip can let the share sheet improve the experience by suggesting the closest contact the person is facing.
+
+**Consider how changes in physical distance can guide a nearby interaction.** In the physical world, people generally expect their perception of an object to sharpen as they get closer to it. A nearby interaction can mirror this experience by providing feedback that changes with the proximity of an object. For example, when people use iPhone to find an AirTag, the display transitions from a directional arrow to a pulsing circle as they get closer.
+
+**Provide continuous feedback.** Continuous feedback reflects the dynamism of the physical world and strengthens the connection between a nearby interaction and the task people are performing. For example, when looking for a lost item in Find My, people get continuous updates that communicate the item’s direction and proximity. Keep people engaged by providing uninterrupted feedback that responds to their movements.
+
+**Consider using multiple feedback types to create a holistic experience.** Fluidly transitioning among visual, audible, and haptic feedback can help a nearby interaction’s task feel more engaging and real. Using more than one type of feedback also lets you vary the experience to coordinate with both the task and the current context. For example, while people are interacting with the device screen, visual feedback makes sense; while people are interacting with their environment, audible and haptic feedback often work better.
+
+**Avoid using a nearby interaction as the only way to perform a task.** You can’t assume that everyone can experience a nearby interaction, so it’s essential to provide alternative ways to get things done in your app.
+
+## [Device usage](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Device-usage)
+
+**Encourage people to hold the device in portrait orientation.** Holding a device in landscape can decrease the accuracy and availability of information about the distance and relative direction of other devices. If you support only portrait orientation while your nearby interaction feature runs, prefer giving people implicit, visual feedback on how to hold the device for an optimal experience; when possible, avoid explicitly telling people to hold the device in portrait.
+
+**Design for the device’s directional field of view.** Nearby interaction relies on a hardware sensor with a specific field of view similar to that of the Ultra Wide camera in iPhone 11 and later. If a participating device is outside of this field of view, your app might receive information about its distance, but not its relative direction.
+
+**Help people understand how intervening objects can affect the nearby interaction experience in your app.** When other people, animals, or sufficiently large objects come between two participating devices, the accuracy or availability of distance and direction information can decrease. Consider adding advice on avoiding this situation to onboarding or tutorial content you present.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Platform-considerations)
+
+ _No additional considerations for iPadOS. Not supported in macOS, tvOS, or visionOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#iOS)
+
+On iPhone, Nearby Interaction APIs provide a peer device’s distance and direction.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#watchOS)
+
+On Apple Watch, Nearby Interaction APIs provide a peer device’s distance. Also, all watchOS apps participating in a nearby interaction experience must be in the foreground.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Developer-documentation)
+
+[Nearby Interaction](https://developer.apple.com/documentation/NearbyInteraction)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Videos)
+
+[ Design for spatial interaction ](https://developer.apple.com/videos/play/wwdc2021/10245)
+
+[ Meet Nearby Interaction ](https://developer.apple.com/videos/play/wwdc2020/10668)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/nearby-interactions#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Changed page title from Spatial interactions.
+
diff --git a/web-app/public/skills/hig-patterns/SKILL.md b/web-app/public/skills/hig-patterns/SKILL.md
new file mode 100644
index 00000000..2114dd74
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/SKILL.md
@@ -0,0 +1,109 @@
+---
+name: hig-patterns
+version: 1.0.0
+description: ">"
+ Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about
+ "onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern",
+ "settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics",
+ "undo redo", "file management", data entry, sharing, collaboration, full screen, audio, video,
+ haptic feedback, ratings, printing, help, or account management in Apple apps.
+ Also use when the user says "how should onboarding work", "my app takes too long to load",
+ "should I use a modal here", "how do I handle errors", "when should I ask for permissions",
+ "how to show progress", or "what's the right way to confirm a delete".
+ Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics,
+ hig-components-layout for navigation, hig-components-content for data display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Interaction Patterns
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Minimize modality.** Use modality only when it is critical to get attention, a task must be completed or abandoned, or saving changes is essential. Prefer non-modal alternatives.
+
+2. **Provide clear feedback.** Every action should produce visible, audible, or haptic response. Activity indicators for indeterminate waits, progress bars for determinate, haptics for physical confirmation.
+
+3. **Support undo over confirmation dialogs.** Destructive actions should be reversible when possible. Undo is almost always better than "Are you sure?"
+
+4. **Launch quickly.** Display a launch screen that transitions seamlessly into the first screen. No splash screens with logos. Restore previous state.
+
+5. **Defer sign-in.** Let users explore before requiring account creation. Support Sign in with Apple and passkeys.
+
+6. **Keep onboarding brief.** Three screens max. Let users skip. Teach through progressive disclosure and contextual hints.
+
+7. **Use progressive disclosure.** Show essentials first, let users drill into details. Don't overwhelm with every option on one screen.
+
+8. **Respect user attention.** Consolidate notifications, minimize interruptions, give users control over alerts. Never use notifications for marketing.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [charting-data.md](references/charting-data.md) | Charting Data | Data visualization patterns, accessible charts, interactive elements |
+| [collaboration-and-sharing.md](references/collaboration-and-sharing.md) | Collaboration & Sharing | Share sheets, activity views, collaborative editing, SharePlay |
+| [drag-and-drop.md](references/drag-and-drop.md) | Drag and Drop | Drag sources, drop targets, spring loading, multi-item drag, visual feedback |
+| [entering-data.md](references/entering-data.md) | Entering Data | Text fields, pickers, steppers, input validation, keyboard types, autofill |
+| [feedback.md](references/feedback.md) | Feedback | Alerts, action sheets, haptic patterns, sound feedback, visual indicators |
+| [file-management.md](references/file-management.md) | File Management | Document browser, file providers, iCloud integration, document lifecycle |
+| [going-full-screen.md](references/going-full-screen.md) | Going Full Screen | Full-screen transitions, immersive content, exiting full screen |
+| [launching.md](references/launching.md) | Launching | Launch screens, state restoration, cold vs warm launch |
+| [live-viewing-apps.md](references/live-viewing-apps.md) | Live Viewing Apps | Live content display, real-time updates, Live Activities, Dynamic Island |
+| [loading.md](references/loading.md) | Loading | Activity indicators, progress views, skeleton screens, lazy loading, placeholders |
+| [managing-accounts.md](references/managing-accounts.md) | Managing Accounts | Sign in with Apple, passkeys, account creation, credential autofill, account deletion |
+| [managing-notifications.md](references/managing-notifications.md) | Managing Notifications | Permission requests, grouping, actionable notifications, provisional delivery |
+| [modality.md](references/modality.md) | Modality | Sheets, alerts, popovers, full-screen modals, when to use each |
+| [multitasking.md](references/multitasking.md) | Multitasking | iPad Split View, Slide Over, Stage Manager, responsive layout, size class transitions |
+| [offering-help.md](references/offering-help.md) | Offering Help | Contextual tips, onboarding hints, help menus, support links |
+| [onboarding.md](references/onboarding.md) | Onboarding | Welcome screens, feature highlights, progressive onboarding, skip options |
+| [playing-audio.md](references/playing-audio.md) | Playing Audio | Audio sessions, background audio, Now Playing, audio routing, interruptions |
+| [playing-haptics.md](references/playing-haptics.md) | Playing Haptics | Core Haptics, UIFeedbackGenerator, haptic patterns, custom haptics |
+| [playing-video.md](references/playing-video.md) | Playing Video | Video player controls, picture-in-picture, AirPlay, full-screen video |
+| [printing.md](references/printing.md) | Printing | Print dialogs, page setup, AirPrint integration |
+| [ratings-and-reviews.md](references/ratings-and-reviews.md) | Ratings & Reviews | SKStoreReviewController, timing, frequency limits, in-app feedback |
+| [searching.md](references/searching.md) | Searching | Search bars, suggestions, scoped search, results display, recents |
+| [settings.md](references/settings.md) | Settings | In-app vs Settings app, preference organization, toggles, defaults |
+| [undo-and-redo.md](references/undo-and-redo.md) | Undo and Redo | Shake to undo, undo/redo stack, multi-level undo |
+| [workouts.md](references/workouts.md) | Workouts | Workout sessions, live metrics, Always On display, summaries, HealthKit |
+
+## Pattern Selection Guide
+
+| User Goal | Recommended Pattern | Avoid |
+|---|---|---|
+| First app experience | Brief onboarding (max 3 screens) + progressive disclosure | Long tutorials, mandatory sign-up |
+| Waiting for content | Skeleton screens or progress indicators | Blocking spinners with no context |
+| Confirming destructive action | Undo support | Excessive "Are you sure?" dialogs |
+| Collecting user input | Inline validation, smart defaults, autofill | Modal forms for simple inputs |
+| Requesting permissions | Contextual, just-in-time with explanation | Requesting all permissions at launch |
+| Providing feedback | Haptics + visual indicator | Silent actions with no confirmation |
+| Organizing preferences | In-app settings for frequent items | Burying all settings in system Settings app |
+
+## Output Format
+
+1. **Recommended pattern with rationale**, citing the relevant reference file.
+2. **Step-by-step implementation** covering each screen or state.
+3. **Platform variations** for targeted platforms.
+4. **Common pitfalls** that violate HIG for this pattern.
+
+## Questions to Ask
+
+1. Where in the app does this pattern appear? What comes before and after?
+2. Which platforms?
+3. Designing from scratch or improving an existing flow?
+4. Does this involve sensitive actions? (Destructive operations, payments, permissions)
+
+## Related Skills
+
+- **hig-foundations** -- Accessibility, color, typography, and privacy principles underlying every pattern
+- **hig-platforms** -- Platform-specific pattern implementations
+- **hig-components-layout** -- Structural components (tab bars, sidebars, split views) for navigation patterns
+- **hig-components-content** -- Content display within patterns (charts, collections, search results)
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-patterns/references/charting-data.md b/web-app/public/skills/hig-patterns/references/charting-data.md
new file mode 100644
index 00000000..305eba09
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/charting-data.md
@@ -0,0 +1,81 @@
+---
+title: "Charting data | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/charting-data
+
+# Charting data
+
+Presenting data in a chart can help you communicate information with clarity and appeal.
+
+
+
+Charts provide efficient ways to communicate complex information without requiring people to read and interpret a lot of text. The graphical nature of charts also gives you additional opportunities to express the personality of your experience and add visual interest to your interface. To learn about the components you use to create a chart, see [Charts](https://developer.apple.com/design/human-interface-guidelines/charts).
+
+A chart can range from a simple graphic that provides glanceable information to a rich, interactive experience that can form the centerpiece of your app and encourage people to explore the data from various perspectives. Whether simple or complex, you can use charts to help people perform data-driven tasks that are important to them, such as:
+
+ * Analyzing trends based on historical or predicted values
+
+ * Visualizing the current state of a process, system, or quantity that changes over time
+
+ * Evaluating different items — or the same item at different times — by comparing data across multiple categories
+
+
+
+
+Not every collection of data needs to be displayed in a chart. If you simply need to provide data — and you don’t need to convey information about it or help people analyze it — consider offering the data in other ways, such as in a list or table that people can scroll, search, and sort.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/charting-data#Best-practices)
+
+**Use a chart when you want to highlight important information about a dataset.** Charts are visually prominent, so they tend to draw people’s attention. Take advantage of this prominence by clearly communicating what people can learn from the data they care about.
+
+**Keep a chart simple, letting people choose when they want additional details.** Resist the temptation to pack as much data as possible into a chart. Too much data can make a chart visually overwhelming and difficult to use, obscuring the relationships and other information you want to convey. If you have a lot of data to present — or a lot of functionality to provide — consider giving people a way to reveal it gradually. For example, you might let people choose to view different levels of detail or subsets of data to match their interest. To help people learn how to use an interactive chart, you might offer several versions of the chart, each with more functionality than the last.
+
+**Make every chart in your app accessible.** A chart communicates visually through graphical representations of data and visual descriptions. In addition to the visual descriptions you display, it’s crucial to provide both accessibility labels that describe chart values and components, and accessibility elements that help people interact with the chart. For guidance, see [Enhancing the accessibility of a chart](https://developer.apple.com/design/human-interface-guidelines/charts#Enhancing-the-accessibility-of-a-chart).
+
+## [Designing effective charts](https://developer.apple.com/design/human-interface-guidelines/charting-data#Designing-effective-charts)
+
+**In general, prefer using common chart types.** People tend to be familiar with common chart types — such as bar charts and line charts — so using one of these types in your app can make it more likely that people will already know how to read your chart. For guidance, see [Charts](https://developer.apple.com/design/human-interface-guidelines/charts).
+
+**If you need to create a chart that presents data in a novel way, help people learn how to interpret the chart.** For example, when a Watch pairs with iPhone, Activity introduces the Activity rings by animating them individually, showing people how each ring maps to the move, exercise, and stand metrics.
+
+**Examine the data from multiple levels or perspectives to find details you can display to enhance the chart.** For example, viewing the data from a macro level can help you determine high-level summaries that people might be interested in, like totals or averages. From a mid-level perspective, you might find ways to help people identify useful subsets of the data, whereas examining individual data points might help you find ways to draw people’s attention to specific values or items. Displaying information that helps people view the chart from various perspectives can encourage them to engage with it.
+
+
+
+
+
+**Aid comprehension by adding descriptive text to the chart.** Descriptive text titles, subtitles, and annotations help emphasize the most important information in a chart and can highlight actionable takeaways. You can also display brief descriptive text that serves as a headline or summary for a chart, helping people grasp essential information at a glance. For example, Weather displays text that summarizes the information people need right now — such as “Chance of light rain in the next hour” — above the scrolling list of hourly forecasts for the next 24 hours. Although a descriptive headline or summary can make a chart more accessible, it doesn’t take the place of accessibility labels.
+
+**Match the size of a chart to its functionality, topic, and level of detail.** In general, a chart needs to be large enough to comfortably display the details you need to include and expansive enough for the interactivity you want to support. For example, you always want to make it easy for people to read a chart’s details and descriptive text — like labels and annotations — but you might also want to give people enough room to change the scope of a chart or investigate the data from different perspectives. On the other hand, you might want to use a small chart to offer glanceable information about an individual item or to provide a snapshot or preview of a larger version of the chart that people can reveal in a different view.
+
+**Prefer consistency across multiple charts, deviating only when you need to highlight differences.** If multiple charts in your app serve a similar purpose, you generally don’t want to imply that the charts are unrelated by using a different type or style for each one. Also, using a consistent visual approach for the charts in your app lets people use what they learn about one chart to help them understand another. Consider using different chart types and styles when you need to highlight meaningful differences between charts.
+
+**Maintain continuity among multiple charts that use the same data.** When you use multiple charts to help people explore one dataset from different perspectives, it’s important to use one chart type and consistent colors, annotations, layouts, and descriptive text to signal that the dataset remains the same. For example, the Health Trends screen shows small charts that each use a specific visual style to depict a recent trend in an area like steps or resting heart rate. When people choose a chart to reveal all their data in that area, the expanded version uses the same style, colors, marks, and annotations to strengthen the relationship between the versions.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/charting-data#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/charting-data#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/charting-data#Related)
+
+[Charts](https://developer.apple.com/design/human-interface-guidelines/charts)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/charting-data#Developer-documentation)
+
+[Swift Charts](https://developer.apple.com/documentation/Charts)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/charting-data#Videos)
+
+[ Bring Swift Charts to the third dimension ](https://developer.apple.com/videos/play/wwdc2025/313)
+
+[ Design app experiences with charts ](https://developer.apple.com/videos/play/wwdc2022/110342)
+
+[ Design an effective chart ](https://developer.apple.com/videos/play/wwdc2022/110340)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/charting-data#Change-log)
+
+Date| Changes
+---|---
+September 23, 2022| New page.
+
diff --git a/web-app/public/skills/hig-patterns/references/collaboration-and-sharing.md b/web-app/public/skills/hig-patterns/references/collaboration-and-sharing.md
new file mode 100644
index 00000000..59b96f1a
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/collaboration-and-sharing.md
@@ -0,0 +1,86 @@
+---
+title: "Collaboration and sharing | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing
+
+# Collaboration and sharing
+
+Great collaboration and sharing experiences are simple and responsive, letting people engage with the content while communicating effectively with others.
+
+
+
+System interfaces and the Messages app can help you provide consistent and convenient ways for people to collaborate and share. For example, people can share content or begin a collaboration by dropping a document into a Messages conversation or selecting a destination in the familiar share sheet.
+
+After a collaboration begins, people can use the Collaboration button in your app to communicate with others, perform custom actions, and manage details. In addition, people can receive Messages notifications when collaborators mention them, make changes, join, or leave.
+
+You can take advantage of Messages integration and the system-provided sharing interfaces whether you implement collaboration and sharing through CloudKit, iCloud Drive, or a custom solution. To offer these features when you use a custom collaboration infrastructure, make sure your app also supports universal links (for developer guidance, see [Supporting universal links in your app](https://developer.apple.com/documentation/Xcode/supporting-universal-links-in-your-app)).
+
+In addition to helping people share and collaborate on documents, visionOS supports immersive sharing experiences through SharePlay. For guidance, see [SharePlay](https://developer.apple.com/design/human-interface-guidelines/shareplay).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Best-practices)
+
+**Place the Share button in a convenient location, like a toolbar, to make it easy for people to start sharing or collaborating.** In iOS 16, the system-provided share sheet includes ways to choose a file-sharing method and set permissions for a new collaboration; iPadOS 16 and macOS 13 introduce similar appearance and functionality in the sharing popover. In your SwiftUI app, you can also enable sharing by presenting a share link that opens the system-provided share sheet when people choose it; for developer guidance, see [`ShareLink`](https://developer.apple.com/documentation/SwiftUI/ShareLink).
+
+
+
+**If necessary, customize the share sheet or sharing popover to offer the types of file sharing your app supports.** If you use CloudKit, you can add support for sending a copy of a file by passing both the file and your collaboration object to the share sheet. Because the share sheet has built-in support for multiple items, it automatically detects the file and makes the “send copy” functionality available. With iCloud Drive, your collaboration object supports “send copy” functionality by default. For custom collaboration, you can support “send copy” functionality in the share sheet by including a file — or a plain text representation of it — in your collaboration object.
+
+**Write succinct phrases that summarize the sharing permissions you support.** For example, you might write phrases like “Only invited people can edit” or “Everyone can make changes.” The system uses your permission summary in a button that reveals a set of sharing options that people use to define the collaboration.
+
+
+
+
+
+**Provide a set of simple sharing options that streamline collaboration setup.** You can customize the view that appears when people choose the permission summary button to provide choices that reflect your collaboration functionality. For example, you might offer options that let people specify who can access the content and whether they can edit it or just read it, and whether collaborators can add new participants. Keep the number of custom choices to a minimum and group them in ways that help people understand them at a glance.
+
+**Prominently display the Collaboration button as soon as collaboration starts.** The system-provided Collaboration button reminds people that the content is shared and identifies who’s sharing it. Because the Collaboration button typically appears after people interact with the share sheet or sharing popover, it works well to place it next to the Share button.
+
+
+
+**Provide custom actions in the collaboration popover only if needed.** Choosing the Collaboration button in your app reveals a popover that consists of three sections. The top section lists collaborators and provides communication buttons that can open Messages or FaceTime, the middle section contains your custom items, and the bottom section displays a button people use to manage the shared file. You don’t want to overwhelm people with too much information, so it’s crucial to offer only the most essential items that people need while they use your app to collaborate. For example, Notes summarizes the most recent updates and provides buttons that let people get more information about the updates or view more activities.
+
+
+
+**If it makes sense in your app, customize the title of the modal view’s collaboration-management button.** People choose this button — titled “Manage Shared File” by default — to reveal the collaboration-management view where they can change settings and add or remove collaborators. If you use CloudKit sharing, the system provides a management view for you; otherwise, you create your own.
+
+**Consider posting collaboration event notifications in Messages.** Choose the type of event that occurred — such as a change in the content or the collaboration membership, or the mention of a participant — and include a universal link people can use to open the relevant view in your app. For developer guidance, see [`SWHighlightEvent`](https://developer.apple.com/documentation/SharedWithYou/SWHighlightEvent).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or macOS. Not available in tvOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#visionOS)
+
+By default, the system supports screen sharing for an app running in the Shared Space by streaming the current window to other collaborators. If one person transitions the app to a Full Space while sharing is in progress, the system pauses the stream for other people until the app returns to the Shared Space. For guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#watchOS)
+
+In your SwiftUI app running in watchOS, use [`ShareLink`](https://developer.apple.com/documentation/SwiftUI/ShareLink) to present the system-provided share sheet.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Related)
+
+[Activity views](https://developer.apple.com/design/human-interface-guidelines/activity-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Developer-documentation)
+
+[Shared with You](https://developer.apple.com/documentation/SharedWithYou)
+
+[`ShareLink`](https://developer.apple.com/documentation/SwiftUI/ShareLink) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Videos)
+
+[ Design for Collaboration with Messages ](https://developer.apple.com/videos/play/wwdc2022/10015)
+
+[ Enhance collaboration experiences with Messages ](https://developer.apple.com/videos/play/wwdc2022/10095)
+
+[ Integrate your custom collaboration app with Messages ](https://developer.apple.com/videos/play/wwdc2022/10093)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/collaboration-and-sharing#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Added artwork illustrating button placement and various types of collaboration permissions.
+June 21, 2023| Updated to include guidance for visionOS.
+September 14, 2022| New page.
+
diff --git a/web-app/public/skills/hig-patterns/references/drag-and-drop.md b/web-app/public/skills/hig-patterns/references/drag-and-drop.md
new file mode 100644
index 00000000..586bb6e7
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/drag-and-drop.md
@@ -0,0 +1,134 @@
+---
+title: "Drag and drop | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/drag-and-drop
+
+# Drag and drop
+
+Using drag and drop, people can move or duplicate selected photos, text, and other content by dragging the selection from one location to another.
+
+
+
+To perform drag and drop, people select content in one location, called the _source_ , and drop it in another, called the _destination_. These locations can be in the same container — like a text view — or in different containers, like text views on opposite sides of a split view, or even in different apps.
+
+Depending on various factors, the drag and drop action might _move_ the selected content to the destination or _copy_ it. After a successful drop, moved content exists only in the destination; copied content exists in both locations. As a general rule, dropping selected content within the same container moves it, whereas dropping content in a different container copies it. Dragging and dropping content between apps always results in a copy.
+
+People use different interactions to perform drag and drop depending on platform. For example:
+
+ * In visionOS, people pinch and hold a virtual object while dragging it to a new location in any direction, including along the z-axis.
+
+ * iOS and iPadOS support drag and drop through gestures on the touchscreen, interactions with a pointing device, and through full keyboard-access mode.
+
+ * Universal Control lets people drag content between their Mac and iPad.
+
+ * On a Mac, people can interact with a pointing device, use full keyboard access mode, or use VoiceOver to perform drag and drop.
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Best-practices)
+
+**As much as possible, support drag and drop throughout your app.** Most people are familiar with drag and drop and they often try it everywhere. When you use system-provided components — such as text fields and text views — you get built-in support for drag and drop.
+
+**Offer alternative ways to accomplish drag-and-drop actions.** Sometimes, drag-and-drop operations are inconvenient or impossible for people to perform, so it’s important to provide other ways to do the same things. For example, you can include menu commands that people can use to copy an item and move it to another location. In iOS and iPadOS, you can use accessibility APIs to identify sources and destinations so that people can use assistive technologies to drag and drop in your app (for developer guidance, see [`accessibilityDragSourceDescriptors`](https://developer.apple.com/documentation/ObjectiveC/NSObject-swift.class/accessibilityDragSourceDescriptors) and [`accessibilityDropPointDescriptors`](https://developer.apple.com/documentation/ObjectiveC/NSObject-swift.class/accessibilityDropPointDescriptors)).
+
+**Determine when dragging and dropping content within your app results in a move or a copy.** In general, a move makes sense when the source and destination containers are the same — such as dragging text from one location to another within a document — and a copy makes sense when they’re different, like dragging an image from one document to another. Before you change these defaults, consider the behavior that most people expect and prefer the one that is least likely to result in frustration or data loss.
+
+**Support multi-item drag and drop when it makes sense.** People appreciate the convenience of dragging a group of items to a destination, instead of dragging each item separately. In iOS, iPadOS, macOS, and visionOS, people can select multiple items and drag them as a group; macOS also lets people select multiple items from several apps and drag them as a group. In iPadOS, people can select an item, start dragging it, and add other items to the group without stopping the drag operation.
+
+**Prefer letting people undo a drag-and-drop operation.** Sometimes, people inadvertently drop content in the wrong destination, so they appreciate being able to undo the action and return to their previous state. You might also be able to help people avoid mistakes by asking for confirmation before completing a drag-and-drop operation that can’t be undone. In macOS, for example, the Finder asks for confirmation when people drag a file into a write-only folder because they won’t be able to open the folder and remove the dropped item. In some situations, it might make sense to provide a way to reverse the results of drag and drop when people can’t undo it. For example, Photos lets people cancel photo sharing after dropping a photo into a shared photo stream.
+
+**Consider offering multiple versions of dragged content, ordered from highest to lowest fidelity.** By providing multiple alternatives, the destination can choose the highest quality version it can accept. For example, if people can drag a line drawing they created in your app, you could offer a PDF vector representation, a lossless PNG image with transparency, and a lossy JPEG image without transparency, in that order. Another example is an app that uses rich, complicated objects, like charts. This app might offer the native chart object followed by a simpler version — like an image of the chart — for destinations that don’t support chart objects.
+
+**Consider supporting spring loading.** Spring loading lets people activate certain controls, like buttons and segmented controls, by dragging selected content over them. For example, Calendar lets people drag a selected event over the day, week, month, or year segments in the toolbar, giving them a convenient way to move the event to a different date. On a Mac equipped with a Magic Trackpad, a button or segmented control can activate when people force-click it while continuing to hold the content; on iPad, these components can activate when people hover over them while holding the content.
+
+## [Providing feedback](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Providing-feedback)
+
+Drag and drop is a dynamic process that can result in multiple outcomes. To help people feel in control the process, it’s crucial to provide clear and continuous feedback throughout.
+
+**Display a drag image as soon as people drag a selection about three points.** It works well to create a translucent representation of the content people are dragging. Translucency helps distinguish the representation from the original content and lets people see destinations as they pass over them. Display the drag image until people drop the content.
+
+**If it adds clarity, modify the drag image to help people predict the result of a drag-and-drop operation.** For example, when dragging a photo into a document, the drag image could expand to show the default size of the photo in the document. You can also use drag _flocking_ to visually group multiple drag items — letting people confirm that they haven’t missed an item they want to drag — and then ungroup the items when people drop them. Although changing the drag image can provide valuable feedback, avoid creating a distracting experience in which the drag image is constantly and radically changing.
+
+**Show people whether a destination can accept dragged content.** For example, you might display an insertion point or highlight a containing view only when the destination can accept a dragged item, and show no visual feedback — or an explicit “not allowed” image, like the `circle.slash` from SF Symbols — when it can’t. Display highlighting or other visual cues only while the content is positioned above the destination, removing the visual feedback when people drag the content away. When there are multiple possible destinations, provide visual cues that help people identify one at a time.
+
+**When people drop an item on an invalid destination, or when dropping fails, provide visual feedback.** For example, the item can move back from its current location to its source (if the source is still visible) or it can scale up and fade out to give the impression of the item evaporating instead of landing successfully.
+
+## [Accepting drops](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Accepting-drops)
+
+**Scroll the contents of a destination when necessary.** When people drag an item within a scrolling container that has a lot of content, the content can automatically scroll as people move the item over it. This behavior makes it easy for people to find the right place to drop the item, but if they continue the drag operation outside of the container, automatic scrolling is no longer necessary. System-provided text views and text fields behave this way by default.
+
+**When there’s a choice, pick the richest version of dropped content your app can accept.** For example, if people drag a chart object from another app, the drag operation might offer both the rich, native chart object and a simple image of it. If your app supports charts, extract and display the native chart object; it it doesn’t, use the image instead.
+
+**Extract only the relevant portion of dropped content if necessary.** For example, when people drag a contact to a recipient field in an email, Mail displays only the name and email address, not the contact’s address information.
+
+**When a physical keyboard is attached, check for the Option key at drop time.** When people hold the Option key while dragging, they can force a drag-and-drop operation within the same container to behave like a copy. If people stop holding Option before dropping content in the same container, the drag operation results in a move.
+
+**Provide feedback when dropped content needs time to transfer.** For example, you might display a progress indicator to help people estimate how long the transfer will take. In collections, lists, and tables, you might also display a placeholder at the drop location so people know where to find the content after it finishes transferring. The system can display an alert when a time-consuming transfer occurs between apps.
+
+**Provide feedback when dropped content initiates a task or action.** If people drop content onto a control that initiates a task — such as printing — show people that the task has begun and keep them informed of its progress.
+
+**Apply appropriate styling to dropped text.** When the source and destination both support the same text styles, make sure dropped text maintains its original font, typeface, size, and other attributes. Otherwise, apply the destination’s style to dropped text.
+
+**After a drop, maintain the content’s selection state in the destination, updating it in the source as needed.** People expect the content they drop to remain selected so they can immediately act on it. When the source and destination are the same container, the content disappears from its original location when the drag operation performs a move. When a drag operation within the same container performs a copy, remove the selection state from the content that remains in the original location. When people drag selected content to a different container, deselect the content in the source.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Platform-considerations)
+
+ _Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#iOS-iPadOS)
+
+**Let people perform multiple simultaneous drag activities.** In iPadOS, people can sequentially add items to an in-progress drag session, gathering as many items as their fingers can handle. For example, people can select an app icon on the Home Screen, start dragging it, and select additional app icons before dropping all of them in a different Home Screen or in a folder. To support this interaction, you need to let people add items during a drag — providing visual feedback through flocking — and accept multiple, simultaneous drops.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#macOS)
+
+**Consider letting people drag content from your app into the Finder.** When you support this, be sure to present the content in a format your app can open later. For example, Calendar lets people drag an event to the Finder as a `.ics` file. People can share this file with others or drag it back to Calendar to open it. When necessary, you can output dragged content in a _clipping_ , which is a temporary container for storing dragged content. For example, most system apps let people drag text to the Finder, where it appears as a clipping. Later, people can drag the clipping into a text field or other location that accepts text. Note that a drag-and-drop clipping isn’t related to the Clipboard.
+
+**Let people drag selected content from an inactive window without first making the window active.** Selected content in an inactive window is known as a _background selection_ and has a different appearance from selected content in the active window. In general, people expect to drag a background selection to the active window without bringing the inactive window forward.
+
+**When possible, let people drag individual items from an inactive window without affecting an existing background selection.** For example, people can drag an unselected file from an inactive Finder window without deselecting any of the window’s selected files.
+
+**Consider displaying a badge during multi-item drag operations.** A badge is a small filled oval containing a number you can use to indicate the number of items people are dragging. If a destination can accept only a subset of dragged items, update the badge to show the new number.
+
+**Consider changing the pointer appearance to indicate what will happen when people drop content.** In addition to using the _copy_ pointer, you might want to use the _drag link_ , _disappearing item_ , and _operation not allowed_ pointers, depending on the situation. For guidance, see [Pointers](https://developer.apple.com/design/human-interface-guidelines/pointing-devices#Pointers).
+
+**As much as possible, let people select and drag content with a single motion.** Unless people are selecting multiple items, they appreciate it when they don’t have to pause between making a selection and starting the drag operation.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#visionOS)
+
+**When possible, launch your app to handle content that people drop into empty space.** When you associate a user activity with draggable app content, your app can open a window or scene that handles the content when people drop it. For example, when people drop a URL into empty space, it launches Safari; when people drop Quick Look–supported content, Quick Look launches to display it. For developer guidance, see [`NSUserActivity`](https://developer.apple.com/documentation/Foundation/NSUserActivity).
+
+Video with custom controls.
+
+Content description: A recording that shows a wearer dragging a 3D file named meteor out of a Finder window. The wearer drags the file into empty space, dropping it in an area that's visually near a table in their physical surroundings. The dropped file opens, showing a 3D meteor that appears to float above the table.
+
+Play
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Related)
+
+[Universal Control](https://support.apple.com/en-us/HT212757)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Developer-documentation)
+
+[Drag and drop](https://developer.apple.com/documentation/UIKit/drag-and-drop) — UIKit
+
+[Drag and Drop](https://developer.apple.com/documentation/AppKit/drag-and-drop) — AppKit
+
+[File Provider](https://developer.apple.com/documentation/FileProvider)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Videos)
+
+[ What's new in UIKit ](https://developer.apple.com/videos/play/wwdc2021/10059)
+
+[ SwiftUI on the Mac: The finishing touches ](https://developer.apple.com/videos/play/wwdc2021/10289)
+
+[ Designed for iPad ](https://developer.apple.com/videos/play/wwdc2020/10206)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Added artwork.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/entering-data.md b/web-app/public/skills/hig-patterns/references/entering-data.md
new file mode 100644
index 00000000..aae13e20
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/entering-data.md
@@ -0,0 +1,69 @@
+---
+title: "Entering data | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/entering-data
+
+# Entering data
+
+When you need information from people, design ways that make it easy for them to provide it without making mistakes.
+
+
+
+Entering information can be a tedious process regardless of the interaction methods people use. Improve the experience by:
+
+ * Pre-gathering as much information as possible to minimize the amount of data that people need to supply
+
+ * Supporting all available input methods so people can choose the method that works for them
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/entering-data#Best-practices)
+
+**Get information from the system whenever possible.** Don’t ask people to enter information that you can gather automatically — such as from settings — or by getting their permission, such as their location or calendar information.
+
+**Be clear about the data you need.** For example, you might display a prompt in a text field — like “username@company.com” — or provide an introductory label that describes the information, like “Email.” You can also prefill fields with reasonable default values, which can minimize decision making and speed data entry.
+
+**Use a secure text-entry field when appropriate.** If your app or game needs sensitive data, use a field that obscures people’s input as they enter it, typically by displaying a small filled circle symbol for each character. For developer guidance, see [`SecureField`](https://developer.apple.com/documentation/SwiftUI/SecureField). In tvOS, you can also configure a [digit entry view](https://developer.apple.com/design/human-interface-guidelines/digit-entry-views) to obscure the numerals people enter (for developer guidance, see [`isSecureDigitEntry`](https://developer.apple.com/documentation/TVUIKit/TVDigitEntryViewController/isSecureDigitEntry)). When you use the system-provided text field in visionOS, the system shows the entered data to the wearer, but not to anyone else; for example, a secure text field automatically blurs when people use AirPlay to stream their content.
+
+**Never prepopulate a password field.** Always ask people to enter their password or use biometric or keychain authentication. For guidance, see [Managing accounts](https://developer.apple.com/design/human-interface-guidelines/managing-accounts).
+
+**When possible, offer choices instead of requiring text entry.** It’s usually easier and more efficient to choose from lists of options than to type information, even when a keyboard is conveniently available. When it makes sense, consider using a picker, menu, or other selection component to give people an easy way to provide the information you need.
+
+**As much as possible, let people provide data by dragging and dropping it or by pasting it.** Supporting these interactions can ease data entry and make your experience feel more integrated with the rest of the system.
+
+**Dynamically validate field values.** People can get frustrated when they have to go back and correct mistakes after filling out a lengthy form. When you verify values as soon as people enter them — and provide feedback as soon as you detect a problem — you give them the opportunity to correct errors right away. For numeric data in particular, consider using a number formatter, which automatically configures a text field to accept only numeric values. You can also configure a formatter to display the value in a specific way, such as with a certain number of decimal places, as a percentage, or as currency.
+
+**When data entry is necessary, make sure people understand that they must provide the required data before they can proceed.** For example, if you include a Next or Continue button after a set of text fields, make the button available only after people enter the data you require.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/entering-data#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, visionOS, or watchOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/entering-data#macOS)
+
+**Consider using an expansion tooltip to show the full version of clipped or truncated text in a field.** An _expansion tooltip_ behaves like a regular tooltip, appearing when the pointer rests on top of a field. Apps running in macOS — including iOS and iPadOS apps running on a Mac — can use an expansion tooltip to help people view the complete data they entered when a text field is too small to display it. For guidance, see [Offering help > macOS, visionOS](https://developer.apple.com/design/human-interface-guidelines/offering-help#macOS-visionOS).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/entering-data#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/entering-data#Related)
+
+[Text fields](https://developer.apple.com/design/human-interface-guidelines/text-fields)
+
+[Virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards)
+
+[Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/entering-data#Developer-documentation)
+
+[Input events](https://developer.apple.com/documentation/SwiftUI/Input-events) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/entering-data#Videos)
+
+[ What's new in UIKit ](https://developer.apple.com/videos/play/wwdc2021/10059)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/entering-data#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/feedback.md b/web-app/public/skills/hig-patterns/references/feedback.md
new file mode 100644
index 00000000..1d76ac21
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/feedback.md
@@ -0,0 +1,67 @@
+---
+title: "Feedback | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/feedback
+
+# Feedback
+
+Feedback helps people know what’s happening, discover what they can do next, understand the results of actions, and avoid mistakes.
+
+
+
+Providing clear, consistent feedback as people interact with your app or game can make it feel intuitive and encourage deeper exploration. Feedback can communicate several different things, such as:
+
+ * The current status of something
+
+ * The success or failure of an important task or action
+
+ * A warning about an action that can have negative consequences
+
+ * An opportunity to correct a mistake or problematic situation
+
+
+
+
+The most effective feedback tends to match the significance of the information to the way it’s delivered. For example, it often works well to display status information in a passive way so that people can view it when they need it. In contrast, a warning about possible data loss needs to interrupt people so they have a chance to avoid the problem.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/feedback#Best-practices)
+
+**Make sure all feedback is accessible.** When you use multiple ways to provide feedback, you reach more people and give them the opportunity to receive the feedback in ways that work for them. For example, when you provide feedback using color, text, sound, and haptics, people can receive it whether they silence their device, look away from the screen, or use VoiceOver. (For guidance on providing haptic feedback, see [Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics).)
+
+**Consider integrating status feedback into your interface.** When status feedback is available near the items it describes, people get important information without having to take action or leave their current context. For example, Mail in iOS and iPadOS describes the most recent update and displays the number of unread messages in the toolbar of the mailbox screen, making the information unobtrusive but easy for people to check when they’re interested.
+
+**Use alerts to deliver critical — and ideally actionable — information.** By design, alerts disrupt the current context, so you need to match the importance of the information to the level of interruption. Alerts can lose their impact if you use them too often or to deliver unimportant information. For guidance, see [Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts).
+
+**Warn people when they initiate a task that can cause data loss that’s unexpected and irreversible.** In contrast, don’t warn people when data loss is the expected result of their action. For example, the Finder doesn’t warn people every time they throw away a file because deleting the file is the expected result.
+
+**When it makes sense, confirm that a significant action or task has completed.** For example, people appreciate getting feedback that confirms a successful Apple Pay transaction. It’s generally best to reserve this type of confirmation for activities that are sufficiently important — because people typically expect their action or task to succeed, they only need to know when it doesn’t.
+
+**Show people when a command can’t be carried out and help them understand why.** For example, if people request directions without specifying a destination, Maps tells them that it can’t provide directions to and from the same location.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/feedback#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/feedback#watchOS)
+
+**Avoid displaying an indeterminate progress indicator — such as a loading indicator — in a watchOS app.** An animated indicator can make people think they need to continue paying attention to the display, which isn’t a good user experience. To provide a better experience, reassure people that they’ll receive a notification when the process completes.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/feedback#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/feedback#Related)
+
+[Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio)
+
+[Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics)
+
+[Motion](https://developer.apple.com/design/human-interface-guidelines/motion)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/feedback#Developer-documentation)
+
+[Animation and haptics](https://developer.apple.com/documentation/UIKit/animation-and-haptics) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/feedback#Videos)
+
+[ Designing Fluid Interfaces ](https://developer.apple.com/videos/play/wwdc2018/803)
+
+[ Essential Design Principles ](https://developer.apple.com/videos/play/wwdc2017/802)
+
diff --git a/web-app/public/skills/hig-patterns/references/file-management.md b/web-app/public/skills/hig-patterns/references/file-management.md
new file mode 100644
index 00000000..fb9fda5a
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/file-management.md
@@ -0,0 +1,135 @@
+---
+title: "File management | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/file-management
+
+# File management
+
+Some apps can support documents and files that people expect to manage throughout the system.
+
+
+
+Document-based apps — such as Pages, Keynote, Photos, and Preview — help people create, edit, and save documents and files, often providing customized ways for people to browse for content they want to open in the app.
+
+People also expect to browse documents without first opening a document-based app. On a Mac, for example, people use the Finder to access the macOS file system; on iPhone, iPad, and Apple Vision Pro, people use the Files app to manage the documents and files on their device. In watchOS and tvOS, people don’t typically create, edit, or manage documents, so these systems don’t provide a document-browsing interface.
+
+## [Creating and opening files](https://developer.apple.com/design/human-interface-guidelines/file-management#Creating-and-opening-files)
+
+**Use app menus and keyboard shortcuts to give people convenient ways to create and open documents.** In iPadOS and macOS, people expect to create new documents or open existing ones using familiar menu commands. When you provide commands like New or Open, iPadOS presents them in the shortcuts interface that displays when people hold the Command key on a connected hardware keyboard, and macOS presents them in the menu bar File menu. Regardless of the availability of keyboard shortcuts, include an Add (+) button to help people create a new document. In a macOS app, you put the add action in the File menu (for guidance, see [File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu)).
+
+**If your app requires a custom file browser, support people’s understanding of the platform’s file system.** People who are familiar with the Finder and Files apps already understand the basic layout of their device’s file system. Although you might want to show the most relevant part of the file system when your custom file browser opens — for example, a Documents or iCloud folder or the most recently selected location — let people use your browser to view the rest of the file system if they want.
+
+## [Saving work](https://developer.apple.com/design/human-interface-guidelines/file-management#Saving-work)
+
+**Help people be confident that their work is always preserved unless they cancel or delete it.** In general, avoid making people take an explicit action to save their work. Instead, automatically perform periodic saves while they’re editing and when they close a file or switch to another app.
+
+**Hide file extensions by default, but let people view them if they choose.** Be sure to reflect the current choice in all the save or open interfaces you display.
+
+## [Quick Look previews](https://developer.apple.com/design/human-interface-guidelines/file-management#Quick-Look-previews)
+
+Quick Look helps you create previews of the files your app handles so that people can view them within your app and in some cases interact with them. For example, you can use Quick Look to let people listen to a preview of an audio file, add markup to a photo’s preview, or rotate and scale a 3D file preview to examine it in different ways.
+
+**Use a Quick Look viewer to let people preview a file even when your app can’t open it.** If your app lets people attach or otherwise interact with files that it doesn’t support, implementing a Quick Look viewer lets people preview those files without leaving your app.
+
+**Consider implementing a Quick Look generator if your app produces custom file types.** A Quick Look generator lets other apps — including the Finder, Files, and Spotlight — display previews of your documents, making it easier for people to find them.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/file-management#Platform-considerations)
+
+ _No additional considerations for tvOS, visionOS, or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/file-management#iOS-iPadOS)
+
+#### [Document launcher](https://developer.apple.com/design/human-interface-guidelines/file-management#Document-launcher)
+
+Starting in iOS 18 and iPadOS 18, document-based apps can use the system’s document launcher to give people a consistent, highly graphical way to browse, open, and create files. The document launcher presents a full-screen experience that highlights key elements of your app’s theme, while making it easy for people to create new documents. For developer guidance, see [`DocumentGroupLaunchScene`](https://developer.apple.com/documentation/SwiftUI/DocumentGroupLaunchScene).
+
+The document launcher consists of three main parts:
+
+ * A _title card_ that displays the app title and two app-specific buttons
+
+ * A background image that appears behind the title card and additional images — called _accessories_ — that can appear around it
+
+ * A sheet that contains a file browser and optional app-specific controls
+
+
+
+
+You can customize all three parts of the document launcher. Although the system automatically displays your app name in the title card, you specify the text and functions of the card’s primary and secondary buttons. You can also create a custom background image, one or more accessory images to surround the title card, and provide some custom controls that can appear in the file browser’s toolbar.
+
+
+
+**Assign the title card’s buttons to your app’s most important functions.** The primary button typically creates a new document, and the secondary button can provide additional options. For example, the primary button in Numbers is Start Writing and the secondary button is Choose a Template.
+
+**Provide a background that’s clearly distinct from the accessories and title card.** You can use a solid color, a gradient, or a pattern. Avoid including complex images or patterns that might distract from foreground elements.
+
+**Be mindful of accessory placement.** For example, you can place accessories both in front of and behind the title card to create the appearance of depth, but you need to make sure that your app name and both buttons remain clearly visible. Avoid cluttering the title card with too many accessories, and be sure to test its overall appearance across the range of screen sizes and device orientations that you support.
+
+**Use animation sparingly.** Too much motion on the display can confuse or disorient people. If you want to animate your accessories, consider creating gentle, repeating animations that subtly highlight and enhance your app’s content. For example, you might create an animation that makes an accessory appear to breathe or sway softly. For guidance, see [Motion](https://developer.apple.com/design/human-interface-guidelines/motion).
+
+#### [File provider app extension](https://developer.apple.com/design/human-interface-guidelines/file-management#File-provider-app-extension)
+
+If your app can share its files with other apps, you can create a file provider app extension that displays a custom interface for importing, exporting, opening, and moving your app’s documents. For developer guidance, see [File Provider](https://developer.apple.com/documentation/FileProvider). An _app extension_ is code you provide that people can install and use to extend the functionality of a specific area of the system; to learn more, see [App extensions](https://developer.apple.com/app-extensions/).
+
+**When someone uses your file provider extension to open or import documents, display only documents that are appropriate in the current context.** For example, if a PDF-editing app loads your extension, only list PDF files for opening or import. You might also want to display additional information, such as modification dates, sizes, and whether documents are local or remote.
+
+**Let people select a destination when exporting and moving documents.** Unless your app stores documents in a single directory, let people navigate to a specific destination in your directory hierarchy. You could also provide a way to add new subdirectories.
+
+**Avoid including a custom top toolbar.** Your extension loads within a modal view that already includes a toolbar. Providing a second toolbar is confusing and takes space away from your content.
+
+Your app can also let people browse and open files from other apps. For developer guidance, see [Adding a document browser to your app](https://developer.apple.com/documentation/UIKit/adding-a-document-browser-to-your-app).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/file-management#macOS)
+
+#### [Custom file management](https://developer.apple.com/design/human-interface-guidelines/file-management#Custom-file-management)
+
+People have strong associations with the familiar file browsing experience of the Finder and most document-based apps. Use the default file browser unless you have an important reason to create a custom one.
+
+**Make your custom file-opening interface convenient.** For example, people might appreciate an “open recent” action in addition to the simple “open” action. You might also want to let people choose criteria on which to filter the file-browsing experience, or select multiple documents to open at once. In a macOS open panel, you can customize the title of the Open button to reflect the task — for example, if your app lets people insert a file’s contents into the current document, you might change the title to Insert.
+
+**Provide a save interface to let people change a file’s name, format, or location.** By default, a new document’s title is “Untitled” until people choose a custom name. As with a document-opening interface, a save view can also provide a browsing experience that defaults to a logical location to help people place the saved document where they want. If you support saving content in different formats, also give people a way to choose a specific file format.
+
+**Consider extending the functionality of the Save dialog.** If it makes sense in your app, you can add a custom accessory view containing useful settings or options to the Save dialog. For example, the dialog for saving Mail messages as files contains an option to include attachments.
+
+#### [Finder Sync extensions](https://developer.apple.com/design/human-interface-guidelines/file-management#Finder-Sync-extensions)
+
+If your app syncs local and remote files, you can create a Finder Sync app extension to express file synchronization status and control within the Finder. For developer guidance, see [Finder Sync](https://developer.apple.com/documentation/FinderSync).
+
+For example, you can use a Finder Sync extension to:
+
+ * Display badges in the Finder to indicate the sync status of items
+
+ * Provide custom contextual menu items that perform file and folder management tasks, like favoriting and adding password-protection
+
+ * Provide custom toolbar buttons that perform global actions, like initiating a sync operation
+
+
+
+
+**Help people avoid losing work if they turn off autosaving.** People can turn off autosaving by selecting the “Ask to keep changes when closing documents” toggle in Desktop & Dock settings. In this scenario, show that a document has unsaved changes and present a save dialog when people choose to close the document, quit your app, log out, or restart.
+
+**When autosaving is off, make sure people know when a document has unsaved changes.** To show that there are unsaved changes, display a dot on the document window’s close button and next to the document’s name in your app’s Window menu. When autosaving is on, showing a dot in these locations is confusing, because it implies that people need to take action to avoid losing their work. Regardless of autosave status, you can append “Edited” to the document’s title in the title bar, but be sure to remove this suffix as soon as autosave occurs or when people explicitly save their work.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/file-management#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/file-management#Related)
+
+[Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars)
+
+[File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu)
+
+[Printing](https://developer.apple.com/design/human-interface-guidelines/printing)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/file-management#Developer-documentation)
+
+[Documents](https://developer.apple.com/documentation/SwiftUI/Documents) — SwiftUI
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/file-management#Videos)
+
+[ Build document-based apps in SwiftUI ](https://developer.apple.com/videos/play/wwdc2020/10039)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/file-management#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| Added guidelines for using the document launcher in iOS and iPadOS.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/going-full-screen.md b/web-app/public/skills/hig-patterns/references/going-full-screen.md
new file mode 100644
index 00000000..8dc8ff8f
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/going-full-screen.md
@@ -0,0 +1,79 @@
+---
+title: "Going full screen | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/going-full-screen
+
+# Going full screen
+
+iPhone, iPad, and Mac offer full-screen modes that let people expand a window to fill the screen, hiding system controls and providing a distraction-free environment.
+
+
+
+Apple TV and Apple Watch don’t offer full-screen modes because apps and games already fill the screen by default. Apple Vision Pro doesn’t offer a full-screen mode because people can expand a window to fill more of their view or use the Digital Crown to hide passthrough and transition to a more immersive experience (for guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences)).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Best-practices)
+
+**Support full-screen mode when it makes sense for your experience.** People appreciate full-screen mode when they want to concentrate on a task or be immersed in content. Consider offering a full-screen mode if your experience lets people play a game; view media like videos or photo slideshows; or perform an in-depth task that benefits from a distraction-free environment.
+
+**If necessary, adjust your layout in full-screen mode, but don’t programmatically resize your window.** When a window is larger in full-screen mode than in non-full-screen mode, you want to keep essential content prominent while making good use of the extra space. For example, it might make sense to adjust the proportions of your interface without changing which items appear. If you make such adjustments, be sure they’re subtle enough to maintain a consistent interface and avoid causing visually jarring transitions between modes.
+
+**Continue to provide access to essential features and controls so people can complete their task without exiting full-screen mode.** For example, a full-screen media experience needs to make playback controls persistently available or easy to reveal when people need them.
+
+**Except in games, let people reveal the Dock while your iPadOS or macOS app is in full-screen mode.** In iPadOS and macOS, it’s important to preserve access to the Dock so people can quickly open other apps and Dock items. To help prevent people from accidentally revealing the Dock while they’re playing your full-screen game, you can ask iPadOS to ignore an initial swipe up from the screen’s bottom edge or hide the Dock entirely in macOS. For developer guidance, see [`preferredScreenEdgesDeferringSystemGestures`](https://developer.apple.com/documentation/SwiftUI/UIHostingController/preferredScreenEdgesDeferringSystemGestures) (SwiftUI), [`preferredScreenEdgesDeferringSystemGestures`](https://developer.apple.com/documentation/UIKit/UIViewController/preferredScreenEdgesDeferringSystemGestures) (UIKit) and [`hideDock`](https://developer.apple.com/documentation/AppKit/NSApplication/PresentationOptions-swift.struct/hideDock) (AppKit).
+
+**After people switch away from your full-screen experience, help them resume where they left off when they return.** For example, a game or a slideshow needs to pause automatically when people leave the experience so they don’t miss anything.
+
+**Let people choose when to exit full-screen mode.** People generally don’t expect full-screen mode to end automatically when they switch to a different experience or finish an absorbing activity, like playing a game or viewing a movie.
+
+**Prioritize content by temporarily hiding toolbars and navigation controls.** You can offer a distraction-free environment by hiding elements when content is the primary focus, such as when viewing full-screen photos or reading a document. If you implement such behavior, let people restore the hidden elements with a familiar gesture or action like tapping, swiping down, or moving the cursor to the top of the screen. Be sure to keep controls visible when they’re essential for navigation or performing tasks. Although a visionOS window can hide its toolbars or navigation controls, people generally expect different types of immersive experiences while wearing Apple Vision Pro; for guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Platform-considerations)
+
+ _Not supported in tvOS, visionOS, or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#iOS-iPadOS)
+
+**Consider deferring system gestures to prevent accidental exits in a full-screen app or game.** By default, the Home Screen indicator automatically hides shortly after someone switches to your app or game. It reappears when someone interacts with the bottom portion of the screen, allowing them to swipe once to exit. Whenever possible, retain this behavior because it’s familiar and what people expect. If supporting this results in unexpected exits, you can enable two swipes rather than one to exit. For developer guidance, see [`preferredScreenEdgesDeferringSystemGestures`](https://developer.apple.com/documentation/SwiftUI/UIHostingController/preferredScreenEdgesDeferringSystemGestures).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#macOS)
+
+**Use the system-provided full-screen experience.** Using the system’s full-screen support ensures that your full-screen window works well in all contexts. For example, some Mac models include a camera housing that occupies an area at the top-center of the screen. Using the system’s full-screen support automatically accommodates this area. For developer guidance, see [`toggleFullScreen(_:)`](https://developer.apple.com/documentation/AppKit/NSWindow/toggleFullScreen\(_:\)).
+
+**In a game, don’t change the display mode when players go full screen.** People expect to be in control of their display mode, and changing it automatically doesn’t improve performance.
+
+For additional developer guidance, see [Managing your game window for Metal in macOS](https://developer.apple.com/documentation/Metal/managing-your-game-window-for-metal-in-macos).
+
+**Always let people choose when to enter full-screen mode.** Prefer letting people use your window’s Enter Full Screen button, View menu item, or the Control-Command-F keyboard shortcut. Avoid offering a custom menu of window modes. In a game, you might also provide a custom [toggle](https://developer.apple.com/design/human-interface-guidelines/toggles) that turns full-screen mode on and off.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Multitasking](https://developer.apple.com/design/human-interface-guidelines/multitasking)
+
+[Windows](https://developer.apple.com/design/human-interface-guidelines/windows)
+
+[The menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Developer-documentation)
+
+[`fullScreenCover(item:onDismiss:content:)`](https://developer.apple.com/documentation/SwiftUI/View/fullScreenCover\(item:onDismiss:content:\)) — SwiftUI
+
+[`NSScreen`](https://developer.apple.com/documentation/AppKit/NSScreen) — AppKit
+
+[`NSWindow.CollectionBehavior`](https://developer.apple.com/documentation/AppKit/NSWindow/CollectionBehavior-swift.struct) — AppKit
+
+[Managing your game window for Metal in macOS](https://developer.apple.com/documentation/Metal/managing-your-game-window-for-metal-in-macos) — Swift, Objective-C
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/going-full-screen#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated guidance for hiding toolbars and navigation controls, and deferring Home Screen indicator gestures in full-screen iOS and iPadOS apps and games.
+June 10, 2024| Enhanced guidance for playing a game in full-screen mode.
+
diff --git a/web-app/public/skills/hig-patterns/references/launching.md b/web-app/public/skills/hig-patterns/references/launching.md
new file mode 100644
index 00000000..5282163f
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/launching.md
@@ -0,0 +1,81 @@
+---
+title: "Launching | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/launching
+
+# Launching
+
+A streamlined launch experience helps people start using your app or game immediately.
+
+
+
+Launching begins when someone opens your app or game, includes an initial download, and ends when the first screen is ready. After launching completes, you might offer an [onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding) experience, which can give people a high-level view of your app or game.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/launching#Best-practices)
+
+**Launch instantly.** People want to start interacting with your app or game right away, and sometimes they don’t want to wait more than a couple of seconds.
+
+**If the platform requires it, provide a launch screen.** In iOS, iPadOS, and tvOS, the system displays your launch screen the moment your app or game starts and quickly replaces it with your first screen, giving people the impression that your experience is fast and responsive. For guidance, see [Launch screens](https://developer.apple.com/design/human-interface-guidelines/launching#Launch-screens). macOS, visionOS, and watchOS don’t require launch screens.
+
+**If you need a splash screen, consider displaying it at the beginning of your onboarding flow.** A splash screen is a beautiful graphic that succinctly communicates branding and other information you need to provide. If you don’t provide an onboarding experience, you might display your splash screen as soon as launching completes.
+
+**Restore the previous state when your app restarts so people can continue where they left off.** Avoid making people retrace steps to reach their previous location in your app or game. Restore granular details of the previous state as much as possible. For example, scroll the view to people’s most recent position, and display windows in the same state and location in which people left them.
+
+## [Launch screens](https://developer.apple.com/design/human-interface-guidelines/launching#Launch-screens)
+
+ _Not applicable for macOS, visionOS, or watchOS._
+
+**Downplay the launch experience.** A launch screen isn’t part of an onboarding experience or a splash screen, and it isn’t an opportunity for artistic expression. A launch screen’s sole function is to enhance the perception of your experience as quick to launch and immediately ready to use.
+
+**Design a launch screen that’s nearly identical to the first screen of your app or game.** If you include elements that look different when launching completes, people may experience an unpleasant flash between the launch screen and your first screen. If your app or game displays a solid color before transitioning to the first screen, create a launch screen that displays only that solid color. Also make sure that your launch screen matches the device’s current orientation and appearance mode.
+
+**Avoid including text on your launch screen, even if your first screen displays text.** Because the content in a launch screen doesn’t change, any text you display won’t be localized.
+
+**Don’t advertise.** The launch screen isn’t a branding opportunity. Avoid creating a screen that looks like a splash screen or an “About” window, and don’t include logos or other branding elements unless they’re a fixed part of your app’s first screen.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/launching#Platform-considerations)
+
+ _No additional considerations for macOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/launching#iOS-iPadOS)
+
+**Launch in the appropriate orientation.** If your app or game supports both portrait and landscape modes, launch using the device’s current orientation. If your interface only runs in one orientation, launch in that orientation and let people rotate the device if necessary. Ensure a landscape-only interface responds correctly, regardless of whether people enter landscape orientation by rotating the device left or right. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/launching#tvOS)
+
+Note
+
+Unlike the [layered images](https://developer.apple.com/design/human-interface-guidelines/images#Layered-images) throughout much of a tvOS app, the launch screen is static.
+
+**In a live-viewing app, consider automatically starting playback soon after people start the app.** People come to your app to watch TV, so you might want to start playing new or recently viewed live content after a few seconds of inactivity. For guidance, see [Live-viewing apps](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/launching#visionOS)
+
+**Consider launching in the Shared Space even if your app is fully immersive.** Opening a window in the Shared Space lets you provide more context about your app or game while giving it time to load, and it also lets you present a control that people can use to open your fully immersive experience. In general, people appreciate being able to choose when to transition to a Full Space, especially if they’re currently running other apps in the Shared Space. For guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/launching#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/launching#Related)
+
+[Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+[Loading](https://developer.apple.com/design/human-interface-guidelines/loading)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/launching#Developer-documentation)
+
+[Specifying your app’s launch screen](https://developer.apple.com/documentation/Xcode/specifying-your-apps-launch-screen) — Xcode
+
+[Responding to the launch of your app](https://developer.apple.com/documentation/UIKit/responding-to-the-launch-of-your-app) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/launching#Videos)
+
+[ Optimizing App Launch ](https://developer.apple.com/videos/play/wwdc2019/423)
+
+[ Love at First Launch ](https://developer.apple.com/videos/play/wwdc2017/816)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/launching#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| Added guidance on displaying a splash screen.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/live-viewing-apps.md b/web-app/public/skills/hig-patterns/references/live-viewing-apps.md
new file mode 100644
index 00000000..8249e796
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/live-viewing-apps.md
@@ -0,0 +1,79 @@
+---
+title: "Live-viewing apps | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps
+
+# Live-viewing apps
+
+As you design a live-viewing app, prioritize the content and create fun, fluid interactions that encourage immersion in the live-viewing experience.
+
+
+
+Live-viewing apps need to elevate and prioritize live content. In every screen, draw people’s attention to live content and make sure they can distinguish it from video-on-demand (VOD) content at a glance.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#Best-practices)
+
+**Feature live content prominently and make it easy to access.** People come to your app to watch content, so you want to minimize the interval between starting your app and playing content. When live content is in the first tab, people don’t have to tap more than once to start viewing it.
+
+**Let people tap once — or not at all — to start playback.** For example, you might display a Watch Now button on top of featured or recently viewed live content. When people tap this button, it immediately disappears and playback begins, replacing your app’s UI with a full-screen, immersive viewing experience.
+
+**Make sure live content looks live.** People need to be able to distinguish live content from VOD content. Although simply playing live content is the best way to make it feel live, you can also help people recognize live content by marking it in some way. For example, you might display other channels in a collection row titled “Live” and give each item a visual indicator — such as a badge, symbol, or sash — that identifies it as live.
+
+**Consider indicating the progress of currently playing live content.** People appreciate knowing where they’ll land when they jump into in-progress live content. You can use a progress bar or other indicator to show people how much content remains.
+
+**Give people additional actions and viewing alternatives.** In addition to playback, which always needs to be the primary action, make it easy for people to record, restart, download, and perform other actions that you support. Display these actions in the same order throughout your app — for example, Watch, Start Over, Record, and Favorite. Also, if the currently playing content is playing again at other times, show this information so that people can schedule their viewing.
+
+**Consider using a content footer for browsing channels during playback.** A content footer lets people browse without taking them out of the live playback experience. If you decide to use a content footer, be sure to:
+
+ * Give it a subtle treatment, such as a darkening, to keep text legible and help all items remain visually distinct from the content playing behind it.
+
+ * Make it easy for people to identify the thumbnail that represents the currently playing content by, for example, badging the thumbnail or tinting its progress bar.
+
+ * Match the categories in the content footer to those in your electronic program guide (for related guidance, see [EPG experience](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#EPG-experience)).
+
+ * Design a simple, predictable way for people to invoke and dismiss the content footer — for example, if swiping up invokes the footer, people would expect swiping down to dismiss it.
+
+
+
+
+**Provide instant visual feedback when people change channels.** This is essential for two reasons: people need confirmation that they’ve arrived at the channel they want, and providing feedback can give the streaming content some time to load.
+
+**Match audio to the current context.** When people start playing live content, they expect the audio to match even if they switch to browsing while the content plays in the background. However, when people navigate away from the live tab in your app, they leave the live-viewing context, so audio needs to stop.
+
+## [EPG experience](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#EPG-experience)
+
+Live-viewing apps typically provide an electronic program guide (EPG) that contains information about scheduled programming. Follow these guidelines to give people a streamlined EPG experience that feels designed specifically for your live-viewing app.
+
+**Prominently display current information and make it easy to return to playback.** When people first open the EPG, the current program, channel, and time needs to be easy to spot so they can instantly return to the current channel.
+
+**Make browsing the EPG effortless.** A typical EPG contains a lot of information, so it’s important to help people page, scroll, or jump through it easily. Also consider providing a My Channels group or a Favorites group that gives people quick access to the content they view most often.
+
+**Group content into familiar categories to help people find it more easily.** For example, you might use categories like Movies, TV Shows, Kids, Sports, and Popular. If your app includes a content footer, organize content thumbnails using the same categories as in the EPG.
+
+**Let people browse the EPG without leaving their current content.** For example, you can continue playing content in a picture-in-picture (PiP) mode or in the background while people browse the EPG.
+
+## [Cloud DVR](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#Cloud-DVR)
+
+If you support digital video recording (DVR) in the cloud, follow these guidelines to provide a great recording experience in your live-viewing app.
+
+**Let people start and stop recording from the info panel.** While live-streaming, people want to reveal the info panel to start recording immediately.
+
+**Let people record a future program in a view that provides details about the content.** Also, give people the option to record only that program or all future episodes.
+
+**Help people adapt the recording experience to their needs.** Let people specify precisely what they want to record, such as only the current episode, only new episodes, or only games that involve specific teams.
+
+**Allow playback and other content-specific actions within your cloud DVR area.** When people open a view that displays content details in your cloud DVR section, let them play or delete content and, if applicable, adjust recording settings.
+
+**Consider offering a control that lets people manage cloud DVR settings.** For example, you might let people delete recordings they’ve already watched or content that’s older than a certain number of days. Ideally, help people avoid running out of space by letting them set up automatic storage management, which overwrites the oldest or already viewed content.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/live-viewing-apps#Related)
+
+[Remotes](https://developer.apple.com/design/human-interface-guidelines/remotes)
+
+[Playing video](https://developer.apple.com/design/human-interface-guidelines/playing-video)
+
diff --git a/web-app/public/skills/hig-patterns/references/loading.md b/web-app/public/skills/hig-patterns/references/loading.md
new file mode 100644
index 00000000..1abe27a9
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/loading.md
@@ -0,0 +1,59 @@
+---
+title: "Loading | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/loading
+
+# Loading
+
+The best content-loading experience finishes before people become aware of it.
+
+
+
+If your app or game loads assets, levels, or other content, design the behavior so it doesn’t disrupt or negatively impact the user experience.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/loading#Best-practices)
+
+**Show something as soon as possible.** If you make people wait for loading to complete before displaying anything, they can interpret the lack of content as a problem with your app or game. Instead, consider showing placeholder text, graphics, or animations as content loads, replacing these elements as content becomes available.
+
+**Let people do other things in your app or game while they wait for content to load.** Loading content in the background helps give people access to other actions. For example, a game could load content in the background while players learn about the next level or view an in-game menu. For developer guidance, see [Improving the player experience for games with large downloads](https://developer.apple.com/documentation/GameKit/improving-the-player-experience-for-games-with-large-downloads).
+
+**If loading takes an unavoidably long time, give people something interesting to view while they wait.** For example, you might provide gameplay hints, display tips, or introduce people to new features. Gauge the remaining loading time as accurately as possible to help you avoid giving people too little time to enjoy your placeholder content or having so much time that you need to repeat it.
+
+**Improve installation and launch time by downloading large assets in the background.** Consider using the [Background Assets](https://developer.apple.com/documentation/BackgroundAssets) framework to schedule asset downloads — like game level packs, 3D character models, and textures — to occur immediately after installation, during updates, or at other nondisruptive times.
+
+## [Showing progress](https://developer.apple.com/design/human-interface-guidelines/loading#Showing-progress)
+
+**Clearly communicate that content is loading and how long it might take to complete.** Ideally, content displays instantly, but for situations where loading takes more than a moment or two, you can use system-provided components — called _progress indicators_ — to show that loading is ongoing. In general, you use a _determinate_ progress indicator when you know how long loading will take, and you use an _indeterminate_ progress indicator when you don’t. For guidance, see [Progress indicators](https://developer.apple.com/design/human-interface-guidelines/progress-indicators).
+
+**For games, consider creating a custom loading view.** Standard progress indicators work well in most apps, but can sometimes feel out of place in a game. Consider designing a more engaging experience by using custom animations and elements that match the style of your game.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/loading#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/loading#watchOS)
+
+**As much as possible, avoid showing a loading indicator in your watchOS experience.** People expect quick interactions with their Apple Watch, so aim to display content immediately. In situations where content needs a second or two to load, it’s better to display a loading indicator than a blank screen.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/loading#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/loading#Related)
+
+[Launching](https://developer.apple.com/design/human-interface-guidelines/launching)
+
+[Progress indicators](https://developer.apple.com/design/human-interface-guidelines/progress-indicators)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/loading#Developer-documentation)
+
+[Background Assets](https://developer.apple.com/documentation/BackgroundAssets)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/loading#Videos)
+
+[ Discover Apple-Hosted Background Assets ](https://developer.apple.com/videos/play/wwdc2025/325)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/loading#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Revised guidance for storing downloads to reflect downloading large assets in the background.
+June 10, 2024| Added guidelines for showing progress and storing downloads, and enhanced guidance for games.
+
diff --git a/web-app/public/skills/hig-patterns/references/managing-accounts.md b/web-app/public/skills/hig-patterns/references/managing-accounts.md
new file mode 100644
index 00000000..f5f20b9f
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/managing-accounts.md
@@ -0,0 +1,107 @@
+---
+title: "Managing accounts | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/managing-accounts
+
+# Managing accounts
+
+When it doesn’t create an unnecessary barrier to your experience, an account can be a convenient way for people to access their content and track personal details.
+
+
+
+Ask people to create an account only if your core functionality requires it; otherwise, let people enjoy your app or game without one. If you require an account, consider using [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple) to give people a consistent sign-in experience they can trust and the convenience of not having to remember multiple accounts and authentication methods.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Best-practices)
+
+**Explain the benefits of creating an account and how to sign up.** If your app or game requires an account, write a brief, friendly description of the reasons for the requirement and its benefits. Display this message in your sign-in view.
+
+**Delay sign-in for as long as possible.** People often abandon apps when they’re forced to sign in before they can do anything useful. To help avoid this situation, give people a chance to get a sense of what your app or game does before asking them to make a commitment to it. For example, a shopping app might let people browse as much as they want, requiring sign-in only when they’re ready to make a purchase.
+
+**If you don’t use Sign in with Apple in your iOS, iPadOS, macOS, or visionOS app, prefer using a passkey.** Passkeys simplify account creation and authentication, eliminating the need for people to create or enter passwords. When an app supports passkeys, people simply provide their user name when creating a new account or signing in to an existing one. For developer guidance, see [Supporting passkeys](https://developer.apple.com/documentation/AuthenticationServices/supporting-passkeys). If you need to continue using passwords for authentication, augment security by requiring two-factor authentication (for developer guidance, see [Securing Logins with iCloud Keychain Verification Codes](https://developer.apple.com/documentation/AuthenticationServices/securing-logins-with-icloud-keychain-verification-codes)).
+
+**Always identify the authentication method you offer.** For example, if you display a button for signing in to your app with Face ID, title it using a phrase like “Sign In with Face ID” instead of a generic phrase like “Sign In.”
+
+**Refer only to authentication methods that are available in the current context.** For example, don’t reference Face ID on a device that doesn’t offer it. Check the device’s capabilities and use the appropriate terminology. For developer guidance, see [`LABiometryType`](https://developer.apple.com/documentation/LocalAuthentication/LABiometryType).
+
+**In general, avoid offering an app-specific setting for opting in to biometric authentication.** People turn on biometric authentication at the system level, so presenting an in-app setting is redundant and could be confusing.
+
+**Avoid using the term _passcode_ to refer to account authentication.** People create a passcode to unlock their device or authenticate for Apple services. If you use the term in your interface, people might think you’re asking them to reuse their passcode in your app or game.
+
+## [Deleting accounts](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Deleting-accounts)
+
+If you help people create an account within your app or game, you must also help them delete it, not just deactivate it. In addition to following the guidelines below, be sure to understand and comply with your region’s legal requirements related to account deletion and the right to be forgotten.
+
+Important
+
+If legal requirements compel your app to maintain accounts or information — such as digital health records — or to follow a specific account-deletion process, clearly describe the situation so people can understand the information or accounts you must maintain and the process you must follow.
+
+**Provide a clear way to initiate account deletion within your app or game.** If people can’t perform account deletion within your app, you must provide a direct link to the webpage on which people can do so. Make the link easy to discover — for example, don’t bury it in your Privacy Policy or Terms of Service pages.
+
+Developer note
+
+If people used [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple) to create an account within your app, you revoke the associated tokens when they delete their account. See [`Token revocation`](https://developer.apple.com/documentation/SigninwithAppleRESTAPI/Revoke-tokens).
+
+**Provide a consistent account-deletion experience whether people perform it within your app or game or on the website.** For example, avoid making one version of the deletion flow longer or more complicated than the other.
+
+**Consider letting people schedule account deletion to occur in the future.** People can appreciate the opportunity to use their remaining services or wait until their subscription auto-renews before deleting their account. If you offer a way to schedule account deletion, offer an option for immediate deletion as well.
+
+**Tell people when account deletion will complete, and notify them when it’s finished.** Because it can sometimes take a while to fully delete an account, it’s essential to keep people informed about the status of the deletion process so they know what to expect.
+
+**If you support in-app purchases, help people understand how billing and cancellation work when they delete their account.** For example, you might need to help people understand the following scenarios:
+
+ * Billing for an auto-renewable subscription continues through Apple until people cancel the subscription, regardless of whether they delete their account.
+
+ * After they delete their account, people need to cancel their subscription or request a refund.
+
+
+
+
+In addition to helping people understand these scenarios, provide information that describes how to cancel subscriptions and manage purchases. For guidance, see [Helping people manage their subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Helping-people-manage-their-subscriptions) and [Providing help with in-app purchases](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Providing-help-with-in-app-purchases).
+
+Note
+
+Even if people didn’t use your app to purchase the subscription, you still need to support account deletion.
+
+## [TV provider accounts](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#TV-provider-accounts)
+
+Many popular TV providers let people sign in to their accounts at the system level, eliminating the need to authenticate on an app-by-app basis. If your TV provider app requires people to sign in, use TV Provider Authentication to provide the most efficient onboarding experience.
+
+**Avoid displaying a sign-out option when people are signed in at the system level.** If your app must include a sign-out option, invoking it needs to prompt people to navigate to Settings > TV Provider to sign out of their account.
+
+**Never instruct people to sign out by adjusting privacy controls.** The TV provider controls in Settings > Privacy aren’t a sign-out mechanism. These settings help people manage the apps that can access their TV provider account.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or visionOS._
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#tvOS)
+
+Most people interact with Apple TV using a remote, not a keyboard, so ask for the minimum amount of information necessary.
+
+**Prefer letting people use another device to sign up or authenticate.** When you configure your app’s associated domains, Apple TV can work with other devices to safely suggest sign-in credentials, including [Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple). For developer guidance, see [Configuring an associated domain](https://developer.apple.com/documentation/Xcode/configuring-an-associated-domain).
+
+**When people are signed in to a shared account, avoid asking them to choose their profile every time they become the current user.** In tvOS 16 and later, your app can share its credentials with all users while storing each individual’s profile and user data separately. When you support this type of sharing, your app can automatically use the current user’s profile without asking each person to sign in separately to a shared account. For developer guidance, see [`kSecUseUserIndependentKeychain`](https://developer.apple.com/documentation/Security/kSecUseUserIndependentKeychain) and [`User Management Entitlement`](https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.user-management).
+
+**Minimize data entry.** If you need to gather more than a small amount of information, ask people to visit a website from another device. If you need an email address, show the email keyboard screen, which includes a list of recently entered addresses.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#watchOS)
+
+Use iCloud synchronization to provide access to the Keychain, letting people autofill user names and passwords and preserve app settings.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Related)
+
+[Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+[Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Developer-documentation)
+
+[Supporting passkeys](https://developer.apple.com/documentation/AuthenticationServices/supporting-passkeys) — Authentication Services
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#Videos)
+
+[ What’s new in passkeys ](https://developer.apple.com/videos/play/wwdc2025/279)
+
+[ What’s new in device management ](https://developer.apple.com/videos/play/wwdc2024/10143)
+
diff --git a/web-app/public/skills/hig-patterns/references/managing-notifications.md b/web-app/public/skills/hig-patterns/references/managing-notifications.md
new file mode 100644
index 00000000..040250e1
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/managing-notifications.md
@@ -0,0 +1,99 @@
+---
+title: "Managing notifications | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/managing-notifications
+
+# Managing notifications
+
+Notifications can give people timely and important information, whether the device is locked or in use.
+
+
+
+You need to get permission before sending any notification. The system lets people change this decision in settings, where they can also silence all notifications (except for government alerts in some locales).
+
+## [Integrating with Focus](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Integrating-with-Focus)
+
+People appreciate receiving a notification for something they care about, but they don’t always appreciate being interrupted. To help people manage the experience, the system lets them specify delivery times and set up a Focus.
+
+ * A Focus helps people filter notifications during a time period they reserve for an activity like sleeping, working, reading, or driving.
+
+ * Delivery scheduling lets people choose whether to receive notification alerts immediately or in a summary that’s delivered at times they choose.
+
+
+
+
+People identify the contacts and apps that can break through a Focus to deliver notification alerts. In a Work Focus, for example, people might want to receive alerts from work colleagues, family members, and work-related apps as soon as notifications arrive. People might also want to receive all Time Sensitive notification alerts during a Focus. A _Time Sensitive_ notification contains essential information people appreciate getting right away.
+
+Important
+
+Even though a Focus might delay the delivery of a notification alert, the notification itself is available as soon as it arrives.
+
+To support these behavior customizations, you first identify the types of notifications your app or game can send. If you support direct communications — like phone calls and messages — you use _communication_ notifications; for all other types of tasks, you use _noncommunication_ notifications. To support communication notifications, you adopt SiriKit intents, which means people can use Siri to customize notification behaviors; for developer guidance, see [`INSendMessageIntent`](https://developer.apple.com/documentation/Intents/INSendMessageIntent) and [`UNNotificationContentProviding`](https://developer.apple.com/documentation/UserNotifications/UNNotificationContentProviding).
+
+You need to specify a system-defined interruption level for each noncommunication notification you send. The system uses the interruption level to help determine when to deliver the alert; when a communication notification arrives, the system uses the sender to determine when to deliver the alert.
+
+The system defines four interruption levels for noncommunication notifications:
+
+ * _Passive_. Information people can view at their leisure, like a restaurant recommendation.
+
+ * _Active_ (the default). Information people might appreciate knowing about when it arrives, like a score update on their favorite sports team.
+
+ * _Time Sensitive_. Information that directly impacts the person and requires their immediate attention, like an account security issue or a package delivery.
+
+ * _Critical_. Urgent information about health and safety that directly impacts the person and demands their immediate attention. Critical notifications are extremely rare and typically come from governmental and public agencies or apps that help people manage their health or home.
+
+
+
+
+Notification alerts in each system-defined interruption level can behave in the following ways:
+
+Interruption level| Overrides scheduled delivery| Breaks through Focus| Overrides Ring/Silent switch on iPhone and iPad
+---|---|---|---
+Passive| No| No| No
+Active| No| No| No
+Time Sensitive| Yes| Yes| No
+Critical| Yes| Yes| Yes
+
+Note
+
+Because a Critical notification can override the Ring/Silent switch and break through scheduled delivery and Focus, you must get an entitlement to send one.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Best-practices)
+
+**Build trust by accurately representing the urgency of each notification.** People have several ways to adjust how they receive your notifications — including turning off all notifications — so it’s essential to be as realistic as possible when assigning an interruption level. You don’t want people to feel that a notification uses a high level of urgency to interrupt them with low-priority information.
+
+**Use the Time Sensitive interruption level only for notifications that are relevant in the moment.** To help people understand the benefits of letting Time Sensitive notifications break through a Focus or scheduled delivery, make sure the notification is about an event that’s happening now or will happen within an hour. The first time a Time Sensitive notification arrives from your app, the system describes how such a notification works and gives people a way to turn it off if they don’t agree that the information requires their immediate attention. Going forward, the system periodically gives people additional opportunities to evaluate how your Time Sensitive notification is working for them. For developer guidance, see [`UNNotificationInterruptionLevel`](https://developer.apple.com/documentation/UserNotifications/UNNotificationInterruptionLevel).
+
+## [Sending marketing notifications](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Sending-marketing-notifications)
+
+Don’t use notifications to send marketing or promotional content unless people explicitly agree to receive such information. When people want to learn about new features, content, or events related to your app or game, they can grant their permission to receive marketing notifications. For example, people who use a subscription app might appreciate getting an offer to become a subscriber, and game players might want to receive a special offer related to a live game event.
+
+**Never use the Time Sensitive interruption level to send a marketing notification.** People may have agreed to receive marketing notifications from your app, but such a notification must never break through a Focus or scheduled delivery setting.
+
+**Get people’s permission if you want to send them promotional or marketing notifications.** Before you send these notifications to people, you must receive their explicit permission to do so. Create an alert, modal view, or other interface that describes the types of information you want to send and gives people a clear way to opt in or out.
+
+**Make sure people can manage their notification settings within your app.** In addition to requesting permission to send informational or marketing notifications, you must also provide an in-app settings screen that lets people change their choice. For guidance, see [Settings](https://developer.apple.com/design/human-interface-guidelines/settings).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#watchOS)
+
+By default, the notification settings people use for apps on their iPhone apply to the same apps on their Apple Watch. People can manage these settings in the Apple Watch app on iPhone, or they can access per-notification options — such as Mute 1 Hour or Turn off Time Sensitive — by swiping left when a notification arrives on their Apple Watch.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Related)
+
+[Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Developer-documentation)
+
+[User Notifications](https://developer.apple.com/documentation/UserNotifications)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/managing-notifications#Videos)
+
+[ Send communication and Time Sensitive notifications ](https://developer.apple.com/videos/play/wwdc2021/10091)
+
+[ The Push Notifications primer ](https://developer.apple.com/videos/play/wwdc2020/10095)
+
diff --git a/web-app/public/skills/hig-patterns/references/modality.md b/web-app/public/skills/hig-patterns/references/modality.md
new file mode 100644
index 00000000..1f4ba019
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/modality.md
@@ -0,0 +1,82 @@
+---
+title: "Modality | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/modality
+
+# Modality
+
+Modality is a design technique that presents content in a separate, dedicated mode that prevents interaction with the parent view and requires an explicit action to dismiss.
+
+
+
+Presenting content modally can:
+
+ * Ensure that people receive critical information and, if necessary, act on it
+
+ * Provide options that let people confirm or modify their most recent action
+
+ * Help people perform a distinct, narrowly scoped task without losing track of their previous context
+
+ * Give people an immersive experience or help them concentrate on a complex task
+
+
+
+
+Depending on the platform, you might use different components to present these types of modal experiences. For example, all platforms can present an _alert_ , which is a modal view that delivers important information related to your app or game. In addition, each platform may define various types of modal views for presenting context-specific options, such as _activity views,_ _sheets_ , and _confirmation dialogs_ or _action sheets_. To help people perform a distinct task, iOS, iPadOS, and macOS apps tend to use sheets or popovers, but iPadOS, macOS, and visionOS apps might also just use a separate window.
+
+To provide a temporary experience, like viewing media, or to help people perform a distinct, multistep task, like editing content, apps can offer a full-screen modal experience. In contrast, apps may also offer nonmodal types of full-screen experiences; for guidance, see [Going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen). visionOS apps can offer a range of immersive experiences; for guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/modality#Best-practices)
+
+**Present content modally only when there’s a clear benefit.** A modal experience takes people out of their current context and requires an action to dismiss, so it’s important to use modality only when it helps people focus or make choices that affect their content or device.
+
+**Aim to keep modal tasks simple, short, and streamlined.** If a modal task is too complicated, people can lose track of the task they suspended when they entered the modal view, especially if the modal view obscures their previous context.
+
+**Take care to avoid creating a modal experience that feels like an app within your app.** In particular, presenting a hierarchy of views within a modal task can make people forget how to retrace their steps. If a modal task must contain subviews, provide a single path through the hierarchy and avoid including buttons that people might mistake for the button that dismisses the modal view.
+
+**Consider using a full-screen modal style for in-depth content or a complex task.** A modal experience that fills a window or the device display minimizes distractions, so it can work well for presenting videos, photos, or camera views, or to support a multistep task like marking up a document or editing a photo. When a visionOS app runs alongside other apps in the Shared Space, a full-screen modal presentation fills a window; if people transition the app to a Full Space, the full-screen modal presentation can become a more immersive experience.
+
+**Always give people an obvious way to dismiss a modal view.** In general, it works well to follow the platform conventions people already know. For example, in iOS, iPadOS, and watchOS apps, people typically expect to find a button in the top toolbar or swipe down; in macOS and tvOS apps, people expect to find a button in the main content view.
+
+**When necessary, help people avoid data loss by getting confirmation before closing a modal view.** Regardless of whether people use a dismiss gesture or a button, if closing the view could result in the loss of user-generated content, be sure to explain the situation and give people ways to resolve it. For example, in iOS, you might present an action sheet that includes a save option.
+
+**Make it easy to identify a modal view’s task.** When people enter a modal view, they switch away from their previous context and might not return to it right away. When you provide a title that names the modal view’s task — or additional text that describes the task or provides guidance — you can help people keep their place in your app.
+
+**Let people dismiss a modal view before presenting another one.** Allowing multiple modal views to be visible at the same time tends to create visual clutter and can make your app seem scattered and disorganized. People need to remember the context they were in before a modal view appears, so presenting multiple views adds to people’s cognitive load, especially when a modal view hides another one by appearing on top of it. Although an alert can appear on top of all other content — including other modal views — you never want to display more than one alert at the same time.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/modality#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/modality#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/modality#Related)
+
+[Sheets](https://developer.apple.com/design/human-interface-guidelines/sheets)
+
+[Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)
+
+[Popovers](https://developer.apple.com/design/human-interface-guidelines/popovers)
+
+[Action sheets](https://developer.apple.com/design/human-interface-guidelines/action-sheets)
+
+[Activity views](https://developer.apple.com/design/human-interface-guidelines/activity-views)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/modality#Developer-documentation)
+
+[Presentation modifiers](https://developer.apple.com/documentation/SwiftUI/View-Presentation) — SwiftUI
+
+[`UIModalPresentationStyle`](https://developer.apple.com/documentation/UIKit/UIModalPresentationStyle) — UIKit
+
+[Modal Windows and Panels](https://developer.apple.com/documentation/AppKit/modal-windows-and-panels) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/modality#Videos)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/modality#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Enhanced guidance for in-depth modal experiences and clarified guidance on multiple modal views.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/multitasking.md b/web-app/public/skills/hig-patterns/references/multitasking.md
new file mode 100644
index 00000000..5788b1ad
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/multitasking.md
@@ -0,0 +1,131 @@
+---
+title: "Multitasking | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/multitasking
+
+# Multitasking
+
+Multitasking lets people switch quickly from one app to another, performing tasks in each.
+
+
+
+People expect to use multitasking on their devices, and they may think something is wrong if your app doesn’t allow it. With rare exceptions — such as some games, and Apple Vision Pro apps running in a Full Space — every app needs to work well with multitasking.
+
+In addition to app switching, multitasking can present different experiences on different devices; see [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/multitasking#Platform-considerations).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/multitasking#Best-practices)
+
+A great multitasking experience helps people accomplish tasks in multiple apps by managing content in a variety of simultaneous contexts. Because you don’t know when people will initiate multitasking, your app or game always needs to be prepared to save and restore their context.
+
+**Pause activities that require people’s attention or active participation when they switch away.** If your app is a game or a media-viewing app, for example, make sure people don’t miss anything when they switch to another app. When they switch back, let them continue as if they never left.
+
+**Respond smoothly to audio interruptions.** Occasionally, audio from another app or the system itself may interrupt your app’s audio. For example, an incoming phone call or a music playlist initiated by Siri might interrupt your app’s audio. When situations like these occur, people expect your app to respond in the following ways:
+
+ * Pause audio indefinitely for primary audio interruptions, such as playing music, podcasts, or audiobooks.
+
+ * Temporarily lower the volume or pause the audio for shorter interruptions, such as GPS directional notifications, and resume the original volume or playback when the interruption ends.
+
+
+
+
+For guidance, see [Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio).
+
+**Finish user-initiated tasks in the background.** When someone starts a task like downloading assets or processing a video file, they expect it to finish even if they switch away from your app. If your app is in the middle of performing a task that doesn’t need additional input, complete it in the background before suspending.
+
+**Use notifications sparingly.** Your app can send notifications when it’s suspended or running in the background. If people start an important or time-sensitive task in your app, and then switch away from it, they might appreciate receiving a notification when the task completes so they can switch back to your app and take the next step. In contrast, people don’t generally need to know the moment a routine or secondary task completes. In this scenario, avoid sending an unnecessary notification; instead, let people check on the task when they return to your app. For guidance, see [Managing notifications](https://developer.apple.com/design/human-interface-guidelines/managing-notifications).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/multitasking#Platform-considerations)
+
+ _Not supported in watchOS._
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/multitasking#iOS)
+
+On iPhone, multitasking lets people use FaceTime or watch a video in Picture in Picture while they also use a different app.
+
+
+
+The app switcher displays all currently open apps.
+
+
+
+A current FaceTime call can continue while people use another app.
+
+### [iPadOS](https://developer.apple.com/design/human-interface-guidelines/multitasking#iPadOS)
+
+On iPad, people can view and interact with the [windows](https://developer.apple.com/design/human-interface-guidelines/windows) of several different apps at the same time. An individual app can also support multiple open windows, which lets people view and interact with more than one window in the same app at one time.
+
+People can use iPad with either full-screen or windowed apps. When full screen, apps occupy the full screen, and people can switch between individual app windows using the app switcher.
+
+
+
+When using windowed apps, app windows are resizable, and people can arrange them to suit their needs with behavior similar to macOS. The system provides window controls for common tiling configurations, entering full screen, minimizing, and closing windows. The system identifies the frontmost window by coloring its window controls and casting a drop shadow on windows behind it. For guidance, see [Windows > iPadOS](https://developer.apple.com/design/human-interface-guidelines/windows#iPadOS).
+
+
+
+Additionally, videos and FaceTime calls can also play in a Picture in Picture overlay above other content regardless of whether apps are full screen or windowed.
+
+Note
+
+Apps don’t control multitasking configurations or receive any indication of the ones that people choose.
+
+To help your app respond correctly when people open it while windowed, make sure it adapts gracefully to different screen sizes. For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout) and [Windows](https://developer.apple.com/design/human-interface-guidelines/windows); for developer guidance, see [Multitasking on iPad, Mac, and Apple Vision Pro](https://developer.apple.com/documentation/UIKit/multitasking-on-ipad-mac-and-apple-vision-pro). To learn more about how people use iPad multitasking features, see [Use multitasking on your iPad](https://support.apple.com/en-us/HT207582).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/multitasking#macOS)
+
+On Mac, multitasking is the default experience because people typically run more than one app at a time, switching between windows and tasks as they work. When multiple app windows are open, macOS applies drop shadows that make the windows appear layered on the desktop, and applies other visual effects to help people distinguish different window states; for guidance, see [macOS window states](https://developer.apple.com/design/human-interface-guidelines/windows#macOS-window-states).
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/multitasking#tvOS)
+
+On Apple TV, people can play or browse content while also playing movies or TV shows in Picture in Picture (where supported).
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/multitasking#visionOS)
+
+On Apple Vision Pro, people can run multiple apps at the same time in the Shared Space, viewing and switching between windows and volumes throughout the space.
+
+Only one window is active at a time in the Shared Space. When people look from one window to another, the window they’re currently looking at becomes active while the previous window becomes more translucent and appears to recede along the z-axis. Closing an app window in the Shared Space transitions the app to the background without quitting it.
+
+Note
+
+When an app is the Now Playing app, closing its window automatically pauses audio playback; if people want to resume playback, they can do so in Control Center without opening the window.
+
+**Avoid interfering with the system-provided multitasking behavior.** When people look from one window to another, visionOS applies a feathered mask to the window they look away from to clarify its changed state. To avoid interfering with this visual feedback, don’t change the appearance of a window’s edges.
+
+Video with custom controls.
+
+Content description: A recording showing the Notes app and the Settings app in the Shared Space in visionOS. The viewer first repositions the Notes window to slightly overlap the Settings window before activating Settings and then switching back to Notes. Each time an app becomes active, the system applies feathering to the inactive app's window.
+
+Play
+
+**Don’t pause a window’s video playback when people look away from it.** In visionOS, as in macOS, people expect the playback they start in one window to continue while they view or perform a task in another window.
+
+**Be prepared for situations where your audio can duck.** Unless an app is currently the Now Playing app, its audio can duck when people look away from it to another app.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/multitasking#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/multitasking#Related)
+
+[Layout](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[Windows](https://developer.apple.com/design/human-interface-guidelines/windows)
+
+[Playing video](https://developer.apple.com/design/human-interface-guidelines/playing-video)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/multitasking#Developer-documentation)
+
+[Responding to the launch of your app](https://developer.apple.com/documentation/UIKit/responding-to-the-launch-of-your-app) — UIKit
+
+[Multitasking on iPad, Mac, and Apple Vision Pro](https://developer.apple.com/documentation/UIKit/multitasking-on-ipad-mac-and-apple-vision-pro) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/multitasking#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+[ Make your UIKit app more flexible ](https://developer.apple.com/videos/play/wwdc2025/282)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/multitasking#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Reorganized guidance in platform considerations, and added guidance for multitasking with multiple windows in iPadOS.
+December 5, 2023| Added artwork for primary and auxiliary windows in iPadOS.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/offering-help.md b/web-app/public/skills/hig-patterns/references/offering-help.md
new file mode 100644
index 00000000..38eabce6
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/offering-help.md
@@ -0,0 +1,117 @@
+---
+title: "Offering help | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/offering-help
+
+# Offering help
+
+Although the most effective experiences are approachable and intuitive, you can provide contextual help when necessary.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/offering-help#Best-practices)
+
+**Let your app’s tasks inform the types of help people might need.** For example, you might help people perform simple, one- or two-step tasks by displaying an inline view that succinctly describes the task. In contrast, if your app or game supports complex or multistep tasks you might want to provide a tutorial that teaches people how to accomplish larger goals. In general, directly relate the help you provide to the precise action or task people are doing right now and make it easy for people to dismiss or avoid the help if they don’t need it.
+
+**Use relevant and consistent language and images in your help content.** Always make sure guidance is appropriate for the current context. For example, if someone’s using the Siri Remote with your tvOS experience, don’t show tips or images that feature a game controller. Also be sure the terms and descriptions you use are consistent with the platform. For example, don’t write copy that tells people to click a button on an iPhone or tap a menu item on a Mac.
+
+**Make sure all help content is inclusive.** For guidance, see [Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion).
+
+**Avoid bloating your help content by explaining how standard components or patterns work.** Instead, describe the specific action or task that a standard element performs in your app or game. If your experience introduces a unique control or expects people to use an input device in a nonstandard way — such as holding the Siri Remote rotated 90 degrees — orient people quickly, preferring animation or graphics to educate instead of a lengthy description.
+
+## [Creating tips](https://developer.apple.com/design/human-interface-guidelines/offering-help#Creating-tips)
+
+A tip is a small, transient view that briefly describes how to use a feature in your app. Tips are a great way to teach people about new or less obvious features in your app, or help them discover faster ways to accomplish a task. For developer guidance, see [TipKit](https://developer.apple.com/documentation/TipKit).
+
+**Use the most appropriate tip type for your app’s user interface.** Display a popover tip when you want to preserve the content flow, or an inline tip when you want to ensure that surrounding information is visible. You can use an annotation-style inline tip when pointing to a specific UI element, or a hint-style tip when it’s not related to a specific piece of UI.
+
+
+
+Popover
+
+
+
+Annotation
+
+
+
+Hint
+
+**Use tips for simple features.** Tips work best on features that are easy to describe and that people can complete with a few simple steps. If a feature requires more than three actions, it’s probably too complicated for a tip.
+
+**Make tips short, actionable, and engaging.** A tip’s goal is to encourage people to try new features. Use direct, action-oriented language to describe what the feature does and explain how to use it. Keep your tips to one or two sentences and avoid including content that’s promotional or related to a different feature or user flow. Promotional content is anything that advertises, sells, or isn’t aligned with the current context of what the person is doing.
+
+**Define rules to help ensure your tips reach the intended audience.** Not everyone benefits from every tip. For example, people who’ve already used a feature won’t appreciate viewing a tip that describes it. Use parameter-based or event-based eligibility rules to control when a tip appears, and only display a tip if someone might benefit from its use. When your app has more than one tip, set the display frequency so tips display at a reasonable cadence — for example, once every 24 hours.
+
+**If there’s an image or symbol that people associate with the feature, consider including it in the tip, and prefer the filled variant.** For example, a tip with a star can help people understand that the tip is related to favorites.
+
+
+
+
+
+
+
+
+
+If the feature is represented by an image that the tip connects to directly, avoid repeating the same image in both the tip and the UI.
+
+
+
+
+
+
+
+
+
+**Use buttons to direct people to information or options.** If your feature has settings people can customize, or you want to redirect people to an area where they can learn more about a feature, consider adding a button. Buttons can take people directly to the settings where they make adjustments. Or if there’s more information people might find useful, add a button to take them to additional resources, such as a setup flow.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/offering-help#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, or watchOS._
+
+### [macOS, visionOS](https://developer.apple.com/design/human-interface-guidelines/offering-help#macOS-visionOS)
+
+A _tooltip_ (called a _help tag_ in user documentation) displays a small, transient view that briefly describes how to use a component in the interface. In apps that run on a Mac — including iPhone and iPad apps — tooltips can appear when a person holds the pointer over an element; in visionOS apps, a tooltip can appear when a person looks at an element or holds the pointer over it. For developer guidance, see [`help(_:)`](https://developer.apple.com/documentation/SwiftUI/View/help\(_:\)-6oiyb).
+
+
+
+**Describe only the control that people indicate interest in.** When people want to know how to use a specific control, they don’t want to learn how to use nearby controls or how to perform a larger task.
+
+**Explain the action or task the control initiates.** It often works well to begin the description with a verb — for example, “Restore default settings” or “Add or remove a language from the list.”
+
+**In general, avoid repeating a control’s name in its tooltip.** Repeating the name takes up space in the tooltip and rarely adds value to the description.
+
+**Be brief.** As much as possible, limit tooltip content to a maximum of 60 to 75 characters (note that localization often changes the length of text). To make a description brief and direct, consider using a sentence fragment and omitting articles. If you need a lot of text to describe a control, consider simplifying your interface design.
+
+**Use sentence case.** Sentence case tends to appear more casual and approachable. If you write complete sentences, omit ending punctuation unless it’s required to be consistent with your app’s style.
+
+**Consider offering context-sensitive tooltips.** For example, you could provide different text for a control’s different states.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/offering-help#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/offering-help#Related)
+
+[Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Writing](https://developer.apple.com/design/human-interface-guidelines/writing)
+
+[Help menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Help-menu)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/offering-help#Developer-documentation)
+
+[TipKit](https://developer.apple.com/documentation/TipKit)
+
+[`NSHelpManager`](https://developer.apple.com/documentation/AppKit/NSHelpManager) — AppKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/offering-help#Videos)
+
+[ Make features discoverable with TipKit ](https://developer.apple.com/videos/play/wwdc2023/10229)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/offering-help#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Included visionOS in guidance for creating tooltips.
+September 12, 2023| Added guidance for creating tips.
+
diff --git a/web-app/public/skills/hig-patterns/references/onboarding.md b/web-app/public/skills/hig-patterns/references/onboarding.md
new file mode 100644
index 00000000..c074cfcc
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/onboarding.md
@@ -0,0 +1,69 @@
+---
+title: "Onboarding | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/onboarding
+
+# Onboarding
+
+Onboarding can help people get a quick start using your app or game.
+
+
+
+Ideally, people can understand your app or game simply by experiencing it, but if onboarding is necessary, design a flow that’s fast, fun, and optional. When available, onboarding occurs after [launching](https://developer.apple.com/design/human-interface-guidelines/launching) is complete — it isn’t part of the launch experience.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/onboarding#Best-practices)
+
+**Teach through interactivity.** People tend to grasp and retain information better when they can actually perform the task they’re learning about instead of just viewing instructional material. As much as possible, provide an interactive onboarding experience where people can safely test an action, discover a feature, or try out a game mechanic.
+
+**Consider providing a collection of context-specific tips instead of a single onboarding flow.** Integrating contextually relevant tips into your experience can help people learn about their current task while they make progress in your app or game. A context-specific tip can also help people learn better because it lets them concentrate on a single action or task before encountering new information. When you have instructional content that refers to a specific area of the interface, display these instructions near that area. For developer guidance, see [TipKit](https://developer.apple.com/documentation/TipKit).
+
+**If you need to present a prerequisite onboarding flow, design a brief, enjoyable experience that doesn’t require people to memorize a lot of information.** When onboarding is quick and entertaining, people are more likely to complete it. In contrast, if you try to teach too much, people can feel overwhelmed and may be less likely to remember what they learned.
+
+**If it makes sense to offer a separate tutorial, consider making it optional.** If you let people skip the tutorial when they first launch your app or game, don’t present it again on subsequent launches, but make sure it’s easy for people to find if they want to view it later. For example, you could make the tutorial available in a help, account, or settings area within your app or game.
+
+**Keep onboarding content focused on the experience you provide.** People enter your onboarding flow to learn about your app or game; they don’t need to learn how to use the system or the device.
+
+## [Additional content](https://developer.apple.com/design/human-interface-guidelines/onboarding#Additional-content)
+
+**Briefly display a splash screen if necessary.** If you need to include a splash screen, design a beautiful graphic that communicates succinctly. Aim to display your splash screen just long enough for people to absorb the information at a glance without feeling that it’s delaying their experience.
+
+**Don’t let large downloads hinder onboarding.** People want to start using your app or game immediately after first launching it, whether they participate in an onboarding flow or skip it. Consider including enough media and other content in your software package to prevent people from having to wait for downloads to complete before they can start interacting with your app or game. For guidance, see [Launching](https://developer.apple.com/design/human-interface-guidelines/launching).
+
+**Avoid displaying licensing details within your onboarding flow.** Let the App Store display agreements and disclaimers so people can read them before downloading your app or game. If you must include these items within the onboarding flow, integrate them in a balanced way that doesn’t disrupt the experience.
+
+## [Additional requests](https://developer.apple.com/design/human-interface-guidelines/onboarding#Additional-requests)
+
+**Postpone nonessential setup flows or customization steps.** Provide reasonable default settings so most people can immediately start interacting with your app or game without performing additional configuration.
+
+**If your app or game needs access to private data or resources before it can function, consider integrating the permission request into your onboarding flow.** In this scenario, making the request during your onboarding flow gives you the opportunity to show people why your app or game needs their permission and the benefits of granting it. Otherwise, present a permission request when people first access the specific function that relies on private data or resources. For guidance, see [Requesting permission](https://developer.apple.com/design/human-interface-guidelines/privacy#Requesting-permission).
+
+**Prefer letting people experience your app or game before prompting them for ratings or purchases.** People can be more likely to respond positively to such requests when they’ve had a chance to become engaged with your app or game.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/onboarding#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/onboarding#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/onboarding#Related)
+
+[Launching](https://developer.apple.com/design/human-interface-guidelines/launching)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Offering help](https://developer.apple.com/design/human-interface-guidelines/offering-help)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/onboarding#Videos)
+
+[ Discoverable design ](https://developer.apple.com/videos/play/wwdc2021/10126)
+
+[ Designing Award Winning Apps and Games ](https://developer.apple.com/videos/play/wwdc2019/802)
+
+[ Love at First Launch ](https://developer.apple.com/videos/play/wwdc2017/816)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/onboarding#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| Clarified different approaches to onboarding and added a guideline on displaying a splash screen.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/playing-audio.md b/web-app/public/skills/hig-patterns/references/playing-audio.md
new file mode 100644
index 00000000..02767258
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/playing-audio.md
@@ -0,0 +1,124 @@
+---
+title: "Playing audio | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/playing-audio
+
+# Playing audio
+
+People expect rich audio experiences that automatically adjust when the context changes on the device.
+
+
+
+Devices can play audio in a variety of ways, such as through internal or external speakers, headphones, and wirelessly through devices that use Bluetooth or AirPlay. To manipulate sound on their devices people use several types of controls, including volume buttons, the Ring/Silent switch on iPhone, headphone controls, the Control Center volume slider, and sound controls in third-party accessories. Whether sound is a primary part of your experience or an embellishment, you need to make sure it behaves as people expect as they make changes to volume and output.
+
+**Silence.** People switch a device to silent when they want to avoid being interrupted by unexpected sounds like ringtones and incoming message tones. In this scenario, they also want to silence nonessential sounds, such as keyboard clicks, sound effects, game soundtracks, and other audible feedback. When a device is in silent mode, it plays only the audio that people explicitly initiate, like media playback, alarms, and audio/video messaging.
+
+**Volume.** People expect their volume settings to affect all sound in the system — including music and in-app sound effects — regardless of the method they use to adjust the volume. An exception is the ringer volume on iPhone, which people can adjust separately in Settings.
+
+**Headphones.** People use headphones to keep their listening private and in some cases to free their hands. When connecting headphones, people expect sound to reroute automatically without interruption; when disconnecting headphones, they expect playback to pause immediately.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Best-practices)
+
+**Adjust levels automatically when necessary — don’t adjust the overall volume.** Your app can adjust relative, independent volume levels to achieve a great mix of audio, but the system volume always governs the final output.
+
+**Permit rerouting of audio when possible.** People often want to select a different audio output device. For example, they may want to listen to music through their living room stereo, car radio, or Apple TV. Support this capability unless there’s a compelling reason not to.
+
+**Use the system-provided volume view to let people make audio adjustments.** The volume view includes a volume-level slider and a control for rerouting audio output. You can customize the appearance of the slider. For developer guidance, see [`MPVolumeView`](https://developer.apple.com/documentation/MediaPlayer/MPVolumeView).
+
+**Choose an audio category that fits the way your app or game uses sound.** Depending on the audio category you choose, your app’s sounds can mix with other audio, play while your app is in the background, or stop when people set the Ring/Silent switch to silent. As much as possible, pick a category that helps your app meet people’s expectations. For example, don’t make people stop listening to music from another app if you don’t need to. For developer guidance, see [`AVAudioSession.Category`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession/Category-swift.struct).
+
+Category| Meaning| Behavior
+---|---|---
+Solo ambient| Sound isn’t essential, but it silences other audio. For example, a game with a soundtrack.| Responds to the silence switch. Doesn’t mix with other sounds. Doesn’t play in the background.
+Ambient| Sound isn’t essential, and it doesn’t silence other audio. For example, a game that lets people play music from another app during gameplay in place of the game’s soundtrack.| Responds to the silence switch. Mixes with other sounds. Doesn’t play in the background.
+Playback| Sound is essential and might mix with other audio. For example, an audiobook or educational app that teaches a foreign language, which people might want to listen to after leaving the app.| Doesn’t respond to the silence switch. May or may not mix with other sounds. Can play in the background.
+Record| Sound is recorded. For example, a note-taking app that offers an audio recording mode. An app of this nature might switch its category to playback if it lets people play the recorded notes.| Doesn’t respond to the silence switch. Doesn’t mix with other sounds. Can record in the background.
+Play and record| Sound is recorded and played, potentially simultaneously. For example, an audio messaging or video calling app.| Doesn’t respond to the silence switch. May or may not mix with other sounds. Can record and play in the background.
+
+**Respond to audio controls only when it makes sense.** People can control audio playback from outside your app’s interface — such as in Control Center or with controls on their headphones — regardless of whether your app is in the foreground or background. If your app is actively playing audio, in a clear audio-related context, or connected to a device that uses Bluetooth or AirPlay, it’s fine to respond to audio controls. Otherwise, when people activate a control, avoid halting audio currently playing from another app.
+
+**Avoid repurposing audio controls.** People expect audio controls to behave consistently in all apps, so it’s essential to avoid redefining the meaning of an audio control in your app. If your app doesn’t support certain controls, don’t respond to them.
+
+**Consider creating custom audio player controls only if you need to offer commands that the system doesn’t support.** For example, you might want to define custom increments for skipping forward or backward, or present content that’s related to the playing audio, such as a sports score.
+
+**Let other apps know when your app finishes playing temporary audio.** If your app can temporarily interrupt the audio of other apps, be sure to flag your audio session in a way that lets other apps know when they can resume. For developer guidance, see [`notifyOthersOnDeactivation`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession/SetActiveOptions/notifyOthersOnDeactivation).
+
+## [Handling interruptions](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Handling-interruptions)
+
+Although most apps and games rely on the system’s default interruption behavior, you can customize this behavior to better accommodate your needs.
+
+**Determine how to respond to audio-session interruptions.** For example, if your app supports recording or other audio-related tasks that people don’t want interrupted, you can tell the system to avoid interrupting the currently playing audio for an incoming call unless people choose to accept it. Another example is a VoIP app, which must end a call when people close the Smart Folio of their iPad while they’re using the built-in microphone. Closing the Smart Folio automatically mutes the iPad microphone and by default interrupts the audio session associated with it. If a VoIP app restarts the audio session when people reopen their Smart Folio, it risks invading people’s privacy by unmuting the microphone without their knowledge. You can inspect an audio-session interruption to help determine the right way to respond; for developer guidance, see [Handling audio interruptions](https://developer.apple.com/documentation/AVFAudio/handling-audio-interruptions).
+
+**When an interruption ends, determine whether to resume audio playback automatically.** Sometimes, audio from a different app can interrupt the audio your app is playing. An interruption can be _resumable_ , like an incoming phone call, or _nonresumable_ , like when people start a new music playlist. Use the interruption type and your app’s type to decide whether to resume playback automatically. For example, a media playback app that’s actively playing audio when an interruption occurs can check to be sure the type is resumable before continuing playback when the interruption ends. On the other hand, a game doesn’t need to check the interruption type before automatically resuming playback, because a game plays audio without an explicit user choice. For developer guidance, see [`shouldResume`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession/InterruptionOptions/shouldResume).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Platform-considerations)
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#iOS-iPadOS)
+
+**Use the system’s sound services to play short sounds and vibrations.** For developer guidance, see [Audio Services](https://developer.apple.com/documentation/AudioToolbox/audio-services).
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#macOS)
+
+In macOS, notification sounds mix with other audio by default.
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#tvOS)
+
+In tvOS, the system plays audio only when people initiate it, through interactions within apps and games or when performing device calibrations. For example, tvOS doesn’t play sounds to accompany components like alerts or notifications.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#visionOS)
+
+Subtle, expressive sounds are everywhere in visionOS, enhancing experiences and providing essential feedback when people look at a virtual object and use gestures to interact with it. The system combines audio algorithms with information about a person’s physical surroundings to produce _Spatial Audio_ , which is sound that people can perceive as coming from specific locations in space, not just from speakers.
+
+Important
+
+In visionOS, as in every platform, avoid communicating important information using only sound. Always provide additional ways to help people understand your app. For guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+In visionOS, audio playback from the Now Playing app pauses automatically when people close the app’s window, and audio from an app that isn’t the Now Playing app can duck when people look away from it to different app.
+
+**Prefer playing sound.** People generally choose to keep sounds audible while they’re wearing the device, so an app that doesn’t play sound — especially in an immersive moment — can feel lifeless and may even seem broken. Throughout the design process, look for opportunities to create meaningful sounds that aid navigation and help people understand the spatial qualities of your app.
+
+**Design custom sounds for custom UI elements.** In general, a system-provided element plays sound to help people locate it and receive feedback when they interact with it. To help people interact with your custom elements, design sounds that provide feedback and enhance the spatial experience of your app.
+
+**Use Spatial Audio to create an intuitive, engaging experience.** Because people can perceive Spatial Audio as coming from anywhere around them, it works especially well in a fully immersive context as a way to help an experience feel lifelike. _Ambient audio_ provides pervasive sounds that can help anchor people in a virtual world and an _audio source_ can sound like it comes from a specific object. As you build the soundscape for your app, consider using both types of audio.
+
+**Consider defining a range of places from which your app sounds can originate.** Spatial Audio helps people locate the object that’s making sound, whether it’s stationary or moving in space. For example, when people move an app window that’s playing audio, the sound continues to come directly from the window, wherever people move it.
+
+**Consider varying sounds that people could perceive as repetitive over time.** For example, the system subtly varies the pitch and volume of the virtual keyboard’s sounds, suggesting the different sounds a physical keyboard can make as people naturally vary the speed and forcefulness of their typing. An efficient way to achieve a pleasing variation in sound is to randomize a sound file’s pitch and volume during playback, instead of creating different files.
+
+**Decide whether you need to play sound that’s fixed to the wearer or tracked by the wearer.** People perceive _fixed_ sound as if it’s pointed at them, regardless of the direction they look or the virtual objects they move. In contrast, people tend to perceive _tracked_ sound as coming from a particular object, so moving the object closer or farther away changes what they hear. In general, you want to use tracked sound to enhance the realism of your experience, but there could be cases where fixed sound is a good choice. For example, Mindfulness uses fixed sound to envelop the wearer in an engaging, peaceful setting.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#watchOS)
+
+In watchOS, the system manages audio playback. An app can play short audio clips while it’s active and running in the foreground, or it can play longer audio that continues even when people lower their wrist or switch to another app. For developer guidance, see [Playing Background Audio](https://developer.apple.com/documentation/WatchKit/playing-background-audio).
+
+**Use the recommended encoding values for media assets.** Specifically, use the 64 kbps HE-AAC (High-Efficiency Advanced Audio Coding) format to produce good-quality audio with lower data requirements.
+
+**Consider** **presenting a Now Playing view so people can control current or recently played audio without leaving your app.** The system-provided Now Playing view also displays information about the current audio source — which might be another app on a person’s Apple Watch or iPhone — and automatically selects the current or most recently used source. For developer guidance, see [Adding a Now Playing View](https://developer.apple.com/documentation/WatchKit/adding-a-now-playing-view).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Related)
+
+[Playing video](https://developer.apple.com/design/human-interface-guidelines/playing-video)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Developer-documentation)
+
+[Configuring your app for media playback](https://developer.apple.com/documentation/AVFoundation/configuring-your-app-for-media-playback) — AVFoundation
+
+[`AVAudioSession`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession) — AVFAudio
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Videos)
+
+[ Explore immersive sound design ](https://developer.apple.com/videos/play/wwdc2023/10271)
+
+[ Principles of spatial design ](https://developer.apple.com/videos/play/wwdc2023/10072)
+
+[ Immerse your app in Spatial Audio ](https://developer.apple.com/videos/play/wwdc2021/10265)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/playing-audio#Change-log)
+
+Date| Changes
+---|---
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/playing-haptics.md b/web-app/public/skills/hig-patterns/references/playing-haptics.md
new file mode 100644
index 00000000..f8fd3f6d
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/playing-haptics.md
@@ -0,0 +1,280 @@
+---
+title: "Playing haptics | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/playing-haptics
+
+# Playing haptics
+
+Playing haptics can engage people’s sense of touch and bring their familiarity with the physical world into your app or game.
+
+
+
+Depending on the platform and the device people are using, the system can play haptics in addition to visual and auditory feedback. For example, components like switches, sliders, and pickers automatically play haptic feedback on supported iPhone models; on Apple Watch, the Taptic Engine generates haptics for a number of built-in feedback patterns, which watchOS combines with an audible tone. On a Mac that’s equipped with a Force Touch trackpad, an app can play haptics while people drag content or when they force click to change the speed of media controls.
+
+In addition to built-in haptic capabilities, some external input devices can also play haptics. For example:
+
+ * In an iPadOS, macOS, tvOS, or visionOS app or game, [game controllers](https://developer.apple.com/design/human-interface-guidelines/game-controls) can provide haptic feedback (for developer guidance, see [Playing Haptics on Game Controllers](https://developer.apple.com/documentation/CoreHaptics/playing-haptics-on-game-controllers)).
+
+ * [Apple Pencil Pro](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble) and some trackpads can provide haptic feedback when connected to certain iPad models. (For details on Apple Pencil features and compatibility, see [Apple Pencil](https://www.apple.com/apple-pencil/).)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Best-practices)
+
+**Use system-provided haptic patterns according to their documented meanings.** People recognize standard haptics because the system plays them consistently on interactions with standard controls. If the documented use case for a pattern doesn’t make sense in your app or game, avoid using the pattern to mean something else. Instead, use a generic pattern or create your own, where supported. For guidance, see [Custom haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Custom-haptics).
+
+**Use haptics consistently throughout your app or game.** It’s important to build a clear, causal relationship between each haptic and the action that causes it so people learn to associate certain haptic patterns with certain experiences. If a haptic doesn’t reinforce a cause-and-effect relationship, it can be confusing and seem gratuitous. For example, if your game plays a specific haptic pattern when a character fails to finish a mission, people associate that pattern with a negative outcome. If you use the same haptic pattern for a positive outcome like a level completion, people will be confused.
+
+**Prefer using haptics to complement other feedback in your app or game.** When visual, auditory, and tactile feedback are in harmony — as they generally are in the physical world — the user experience is more coherent and can seem more natural. For example, you generally want to match the intensity and sharpness of a haptic with the intensity and sharpness of the animation it accompanies. You can also synchronize sound with haptics; for developer guidance, see [Delivering Rich App Experiences with Haptics](https://developer.apple.com/documentation/CoreHaptics/delivering-rich-app-experiences-with-haptics).
+
+**Avoid overusing haptics.** Sometimes a haptic can feel just right when it happens occasionally, but become tiresome when it plays frequently. Doing user testing can help you discover a balance that most people appreciate. Often, the best haptic experience is one that people may not be conscious of, but miss when it’s turned off.
+
+**In most apps, prefer playing short haptics that complement discrete events.** Although long-running haptics that accompany a gameplay flow can enhance the experience, long-running haptics in an app can dilute the meaning of the feedback and distract people from their task. On Apple Pencil Pro, for example, continuous or long-lasting haptics don’t tend to clarify the writing or drawing experience and can even make holding the pencil less pleasant.
+
+**Make haptics optional.** Let people turn off or mute haptics, and make sure people can still enjoy your app or game without them.
+
+**Be aware that playing haptics might impact other user experiences.** By design, haptics produce enough physical force for people to feel the vibration. Ensure that haptic vibrations don’t disrupt experiences involving device features like the camera, gyroscope, or microphone.
+
+## [Custom haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Custom-haptics)
+
+Games often use custom haptics to enhance gameplay. Although it’s less common, nongame apps might also use custom haptics to provide a richer, more delightful experience.
+
+You can design custom haptic patterns that vary dynamically, based on user input or context. For example, the impact players feel when a game character jumps from a tree can be stronger than when the character jumps in place, and substantial experiences — like a collision or a hit — can feel very different from subtle experiences like the approach of footsteps or a looming danger.
+
+There are two basic building blocks you can use to generate custom haptic patterns.
+
+ * _Transient_ events are brief and compact, often feeling like taps or impulses. The experience of tapping the Flashlight button on the Home Screen is an example of a transient event.
+
+ * _Continuous_ events feel like sustained vibrations, such as the experience of the lasers effect in a message.
+
+
+
+
+Regardless of the type of haptic event you use to generate a custom haptic, you can also control its _sharpness_ and _intensity_. You can think of sharpness as a way to abstract a haptic experience into the waveform that produces the corresponding physical sensations. Specifying sharpness lets you relay to the system your intent for the experience. For example, you might use sharpness values to convey an experience that’s soft, rounded, or organic, or one that’s crisp, precise, or mechanical. As the term implies, intensity means the strength of the haptic.
+
+By combining transient and continuous events, varying sharpness and intensity, and including optional audio content, you can create a wide range of different haptic experiences. For developer guidance, see [Core Haptics](https://developer.apple.com/documentation/CoreHaptics).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Platform-considerations)
+
+### [iOS](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#iOS)
+
+On supported iPhone models, you can add haptics to your experience in the following ways:
+
+ * Use standard UI components — like [toggles](https://developer.apple.com/design/human-interface-guidelines/toggles), [sliders](https://developer.apple.com/design/human-interface-guidelines/sliders), and [pickers](https://developer.apple.com/design/human-interface-guidelines/pickers) — that play Apple-designed system haptics by default.
+
+ * When it makes sense, use a feedback generator to play one of several predefined haptic patterns in the categories of [notification](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Notification), [impact](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Impact), and [selection](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Selection) (for developer guidance, see [`UIFeedbackGenerator`](https://developer.apple.com/documentation/UIKit/UIFeedbackGenerator)).
+
+
+
+
+#### [Notification](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Notification)
+
+Notification haptics provide feedback about the outcome of a task or action, such as depositing a check or unlocking a vehicle.
+
+Video with custom controls.
+
+Content description: An animation that represents a series of two haptic pulses of various durations and strengths by showing bars of different sizes and playing audio tones of different pitches. This particular pattern represents a success.
+
+Play
+
+**Success.** Indicates that a task or action has completed.
+
+Video with custom controls.
+
+Content description: An animation that represents a series of two haptic pulses of various durations and strengths by showing bars of different sizes and playing audio tones of different pitches. This particular pattern represents a warning.
+
+Play
+
+**Warning.** Indicates that a task or action has produced a warning of some kind.
+
+Video with custom controls.
+
+Content description: An animation that represents a series of four haptic pulses of various durations and strengths by showing bars of different sizes and playing audio tones of different pitches. This particular pattern represents an error.
+
+Play
+
+**Error.** Indicates that an error has occurred.
+
+#### [Impact](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Impact)
+
+Impact haptics provide a physical metaphor you can use to complement a visual experience. For example, people might feel a tap when a view snaps into place or a thud when two heavy objects collide.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a light impact.
+
+Play
+
+**Light.** Indicates a collision between small or lightweight UI objects.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a medium impact.
+
+Play
+
+**Medium.** Indicates a collision between medium-sized or medium-weight UI objects.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a heavy impact.
+
+Play
+
+**Heavy.** Indicates a collision between large or heavyweight UI objects.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a rigid impact.
+
+Play
+
+**Rigid.** Indicates a collision between hard or inflexible UI objects.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a soft impact.
+
+Play
+
+**Soft.** Indicates a collision between soft or flexible UI objects.
+
+#### [Selection](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Selection)
+
+Selection haptics provide feedback while the values of a UI element are changing.
+
+Video with custom controls.
+
+Content description: An animation that represents a single haptic pulse of a specific duration and strength by showing a bar of a specific size and playing an audio tone of a specific pitch. This particular pattern represents a selection.
+
+Play
+
+**Selection.** Indicates that a UI element’s values are changing.
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#macOS)
+
+When a Magic Trackpad is available, your app can provide one of the three following haptic patterns in response to a drag operation or force click.
+
+Haptic feedback pattern| Description
+---|---
+Alignment| Indicates the alignment of a dragged item. For example, this pattern could be used in a drawing app when the people drag a shape into alignment with another shape. Other scenarios where this type of feedback could be used might include scaling an object to fit within specific dimensions, positioning an object at a preferred location, or reaching the beginning/end or minimum/maximum of something like a scrubber in a video app.
+Level change| Indicates movement between discrete levels of pressure. For example, as people press a fast-forward button on a video player, playback could increase or decrease and haptic feedback could be provided as different levels of pressure are reached.
+Generic| Intended for providing general feedback when the other patterns don’t apply.
+
+For developer guidance, see [`NSHapticFeedbackPerformer`](https://developer.apple.com/documentation/AppKit/NSHapticFeedbackPerformer).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#watchOS)
+
+Apple Watch Series 4 and later provides haptic feedback for the Digital Crown, which gives people a more tactile experience as they scroll through content. By default, the system provides linear haptic detents that people can feel as they rotate the Digital Crown. Some system controls, like table views, provide detents as new items scroll onto the screen. For developer guidance, see [`WKHapticType`](https://developer.apple.com/documentation/WatchKit/WKHapticType).
+
+watchOS defines the following set of haptics, each of which conveys a specific meaning to people.
+
+ * Notification
+ * Up
+ * Down
+ * Success
+ * Failure
+ * Retry
+ * Start
+ * Stop
+ * Click
+
+
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Notification.** Tells the person that something significant or out of the ordinary has happened and requires their attention. The system plays this same haptic when a local or remote notification arrives.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Up.** Tells the person that an important value increased above a significant threshold.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Down.** Tells the person that an important value decreased below a significant threshold.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Success.** Tells the person that an action completed successfully.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Failure.** Tells the person that an action failed.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Retry.** Tells the person that an action failed but they can retry it.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Start.** Tells the person that an activity started. Use this haptic when starting a timer or any other activity that a person can explicitly start and stop. The stop haptic usually follows this haptic.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Stop.** Tells the person that an activity stopped. Use this haptic when stopping a timer or other activity that the person previously started.
+
+Video with custom controls.
+
+Content description: An animation that represents an arrangement of haptic pulses of various durations and strengths by showing a set of thin vertical lines that symbolize sound waves.
+
+Play
+
+**Click.** Provides the sensation of a dial clicking, helping you communicate progress at predefined increments or intervals. Overusing the click haptic tends to diminish its utility and can even be confusing when clicks overlap each other.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Developer-documentation)
+
+[Core Haptics](https://developer.apple.com/documentation/CoreHaptics)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Videos)
+
+[ Practice audio haptic design ](https://developer.apple.com/videos/play/wwdc2021/10278)
+
+[ Introducing Core Haptics ](https://developer.apple.com/videos/play/wwdc2019/520)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/playing-haptics#Change-log)
+
+Date| Changes
+---|---
+May 7, 2024| Added guidance for playing haptics on Apple Pencil Pro.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/playing-video.md b/web-app/public/skills/hig-patterns/references/playing-video.md
new file mode 100644
index 00000000..5d06e204
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/playing-video.md
@@ -0,0 +1,180 @@
+---
+title: "Playing video | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/playing-video
+
+# Playing video
+
+People expect to enjoy rich video experiences on their devices, regardless of the app or game they’re using.
+
+
+
+The system provides video players designed for you to use to embed playback experiences within your app or game in iOS, iPadOS, macOS, tvOS, and visionOS. You can also offer your content through the TV app in these platforms, which gives people a convenient and consistent viewing experience.
+
+The system-provided video players support different aspect-ratio playback modes and in most platforms, Picture in Picture (PiP) viewing mode. Although people can switch modes during playback, by default, the system selects one of the following playback modes based on a video’s aspect ratio:
+
+ * In full-screen — or _aspect-fill_ — mode, the video scales to fill the display, and some edge cropping may occur. This mode is the default for wide video (2:1 through 2.40:1). For developer guidance, see [`resizeAspectFill`](https://developer.apple.com/documentation/AVFoundation/AVLayerVideoGravity/resizeAspectFill).
+
+ * In fit-to-screen — or _aspect_ — mode, the entire video is visible onscreen, and letterboxing or pillarboxing occurs as needed. This mode is the default for standard video (4:3, 16:9, and anything up to 2:1) and ultrawide video (anything above 2.40:1). For developer guidance, see [`resizeAspect`](https://developer.apple.com/documentation/AVFoundation/AVLayerVideoGravity/resizeAspect).
+
+
+
+
+In visionOS and tvOS, the built-in video player also provides _transport controls,_ which let people perform playback tasks, like turning on subtitles or changing the audio language, and actions, like adding a show to a library or favoriting a clip. Below the transport controls, the video player displays _content tabs_ , like Info, Episodes, or Chapters, that can provide supporting information and help streamline navigation. In visionOS, the transport controls appear as an [ornament](https://developer.apple.com/design/human-interface-guidelines/ornaments).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/playing-video#Best-practices)
+
+**Use the system video player to give people a familiar and convenient experience.** The built-in video player provides an exceptional video playback experience that offers consistent interactions and behaviors that let people concentrate on enjoying immersive content. If your app truly requires a custom video player, reference the behavior and interface of the system video player to help you provide an experience that people can instantly understand. A custom experience that diverges slightly from the system-provided experience can cause frustration because people don’t know which of their habitual interactions they can continue to use.
+
+**Always display video content at its original aspect ratio.** When video content uses embedded letterbox or pillarbox padding to conform to a specific aspect ratio, the system may be unable to correctly scale the video based on the current playback mode. Padding embedded within the video frame can cause videos to appear smaller in both full-screen and fit-to-screen modes. It also prevents videos from displaying correctly in edge-to-edge, non-full-screen contexts, like Picture in Picture mode on iPad.
+
+Here are some examples that show how padding can affect video display on iPhone Xs.
+
+ * Result of padding a 4:3 video
+ * Result of padding a 21:9 video
+
+
+
+
+
+4:3 video in full-screen viewing mode
+
+
+
+4:3 video with embedded padding, in full-screen viewing mode
+
+
+
+
+
+21:9 video in fit-to-screen viewing mode
+
+
+
+21:9 video with embedded padding, in fit-to-screen viewing mode
+
+
+
+**Provide additional information when it adds value.** In iOS, iPadOS, tvOS, and visionOS, you can customize a video’s additional information by providing an image, title, description, and other useful information. In general, restrict this content so that it doesn’t obscure media playback. For developer guidance, see [`externalMetadata`](https://developer.apple.com/documentation/AVFoundation/AVPlayerItem/externalMetadata).
+
+**Support the interactions people expect, regardless of the input device they’re using to control playback.** For example, people expect to press Space on a connected keyboard to play or pause media playback on Apple Vision Pro, Mac, iPhone, iPad, and Apple TV. Similarly, people expect to move through their media on Apple TV by making familiar, intuitive gestures with the Siri Remote. For guidance, see Keyboards and Remotes.
+
+**If people need to access playback options or content-specific information in your tvOS app, consider adding a transport control or a custom content tab.** People typically open a transport control or content tab while they’re watching a video, so it’s essential to provide only the most useful actions and information. Help people return quickly to the viewing experience by making sure your actions don’t take more than a step or two and your content is succinct. Use a transport control to support a playback-related action like favoriting a video; use custom content tabs to display supplementary information or recommendations.
+
+**Avoid allowing audio from different sources to mix as viewers switch between modes.** Mixed audio is an unpleasant and frustrating user experience. In general, audio mixes when at least one of the audio sources fails to handle secondary audio correctly. Here is a typical scenario: While watching a full-screen video, the viewer moves it into the PiP window, where the system automatically mutes the video. In the full-screen window, the viewer starts a game that plays background music, then switches to the PiP window and unmutes the video. If the game doesn’t handle secondary audio appropriately, its audio mixes with the audio from the unmuted video. For developer guidance, see [`silenceSecondaryAudioHintNotification`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession/silenceSecondaryAudioHintNotification).
+
+## [Integrating with the TV app](https://developer.apple.com/design/human-interface-guidelines/playing-video#Integrating-with-the-TV-app)
+
+The TV app provides global access to favorite, recently played, and recommended video content from across the system. When people initiate content playback within your app, the TV app automatically opens your app and transitions to it. Follow these guidelines to help the TV app experience feel like an integrated part of your app.
+
+**Ensure a smooth transition to your app.** The TV app fades to black when transitioning to your app and doesn’t show your app’s launch screen. Maintain visual continuity with this transition by immediately presenting your own black screen before starting to play or resume content.
+
+**Show the expected content immediately.** People expect the content they choose to begin playing as soon as the transition to your app completes, especially when resuming playback. Jump right from your app’s black screen into content, and avoid displaying splash screens, detail screens, intro animations, or any other barriers that make it take longer to reach content. In rare situations where you must display an interstitial element before the selected media plays, people can choose Select to step through the element, or choose Play if they want to skip the interstitial content and start playback.
+
+**Avoid asking people if they want to resume playback.** If playback can be resumed, do so automatically without prompting for confirmation.
+
+**Play or pause playback when people press Space on a connected Bluetooth keyboard.** Pressing Space to control media playback is an interaction people expect, regardless of the keyboard they’re using.
+
+**Make sure content plays for the correct viewer.** If your app supports multiple user profiles, the TV app can specify a profile when issuing a playback request. Make your app automatically switch to this profile before starting playback. If a playback request doesn’t specify a profile, ask the viewer to choose one before playback begins so this information is available in the future.
+
+**Use the previous end time when resuming playback of a long video clip.** Resuming playback at the previous stopping point lets people quickly continue where they left off.
+
+### [Loading content](https://developer.apple.com/design/human-interface-guidelines/playing-video#Loading-content)
+
+**Avoid displaying loading screens when possible.** A loading screen is unnecessary if your content loads quickly, but if loading takes more than two seconds, consider showing a black loading screen with a centered activity spinner and no surrounding content.
+
+**Start playback immediately.** If you must display a loading screen, display it only until enough content loads for playback to begin. Continue loading remaining content in the background.
+
+**Minimize loading screen content.** If you include branding or images on your loading screen, do so minimally while maintaining the black background that helps provide a seamless transition to playback.
+
+### [Exiting playback](https://developer.apple.com/design/human-interface-guidelines/playing-video#Exiting-playback)
+
+After exiting playback, people remain in your app rather than returning to the TV app, so it’s a good idea to help them avoid becoming disoriented.
+
+**Show a contextually relevant screen.** When exiting playback, display a detail view for the content the viewer was just watching and include an option to resume playback. If a detail view isn’t available, show either a menu that lists this content or your app’s main menu.
+
+**Be prepared for an immediate exit.** Prepare an exit view as soon as possible after receiving a playback notification so you’re ready to display the view if people exit immediately after playback begins.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/playing-video#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or macOS._
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/playing-video#tvOS)
+
+**Defer to content when displaying logos or noninteractive overlays above video.** A small, unobtrusive logo or countdown timer may be appropriate for your video, but avoid large, distracting overlays that don’t enhance the viewing experience. Also, be aware that some devices are prone to image retention, so it’s generally better to keep overlays short and to prefer translucent graphics in Standard Dynamic Range (SDR) to bright, opaque content.
+
+**Show interactive overlays gracefully.** Some videos display interactive overlays, such as quizzes, surveys, and progress check-ins. For the best user experience, implement a minimum delay of 0.5 seconds to pause playing media, and display an interactive overlay. Give people a clear way to dismiss the overlay and resume media playback after they finish interacting.
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/playing-video#visionOS)
+
+**Help people stay comfortable when playing video in your app.** Often, an app doesn’t control the content in the videos it plays, but you can help people stay comfortable by:
+
+ * Letting them choose when to start playing a video
+
+ * Using a small window for playback, letting people resize it if they want
+
+ * Making sure people can see their surroundings during playback
+
+
+
+
+**In a fully immersive experience, avoid letting virtual content obscure playback or transport controls.** In a fully immersive context, the system automatically places the video player at a predictable location that provides an optimal viewing experience. Use this location to help make sure that no virtual content occludes the default playback or transport controls in the ornament near the bottom of the player.
+
+**Avoid automatically starting a fully immersive video playback experience.** People need control over their experience and they’re unlikely to appreciate being launched into a fully immersive video without warning.
+
+**Create a thumbnail track if you want to support scrubbing.** The system displays thumbnails as people scrub to different times in the video, helping them choose the section they want. To improve performance, supply a set of thumbnails that each measure 160 px in width. For developer guidance, see [HTTP Live Streaming (HLS) Authoring Specification for Apple Devices > Trick Play](https://developer.apple.com/documentation/http-live-streaming/hls-authoring-specification-for-apple-devices#Trick-Play).
+
+**Avoid expanding an inline video player to fill a window.** When you display the system-provided player view in a window, playback controls appear in the same plane as the player view and not in an ornament that floats above the window. Inline video needs to be 2D and you want to make sure that window content remains visible around the player so people don’t expect a more immersive playback experience. For developer guidance, see [`AVPlayerViewController`](https://developer.apple.com/documentation/AVKit/AVPlayerViewController).
+
+**Use a RealityKit video player if you need to play video in a view like a splash screen or a transitional view.** In situations like these, people generally expect the video to lead into the next experience, so they don’t need playback controls or system-provided integration, like dimming and view anchoring. The RealityKit video player automatically uses the correct aspect ratio for both 2D and 3D video and supports closed captions. RealityKit can also help you play video as a special effect on the surface of a custom view or object. For developer guidance, see [RealityKit](https://developer.apple.com/documentation/RealityKit).
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/playing-video#watchOS)
+
+In watchOS, the system manages video playback. Apps can play short video clips while the app is active and running in the foreground. You can use a movie element to embed clips in your interface and play video inline, or you can play a clip in a separate interface. For developer guidance, see [`VideoPlayer`](https://developer.apple.com/documentation/AVKit/VideoPlayer).
+
+**Keep video clips short.** Prefer shorter clips of no longer than 30 seconds. Long clips consume more disk space and require people to keep their wrists raised for longer periods of time, which can cause fatigue.
+
+**Use the recommended sizes and encoding values for media assets.** In particular, avoid scaling video clips, which affects performance and results in a suboptimal appearance. The following table lists the recommended encoding and resolution values for video assets. The audio encoding values apply to both movies and audio-only assets.
+
+Attribute| Value
+---|---
+Video codec| H.264 High Profile
+Video bit rate| 160 kbps at up to 30 fps
+Resolution (full screen)| 208x260 px (portrait orientation)
+Resolution (16:9)| 320x180 px (landscape orientation)
+Audio| 64 kbps HE-AAC
+
+**Avoid creating a poster image that looks like a system control.** You want people to understand that they can tap a movie element for playback; you don’t want to confuse people by making movie elements look like something else.
+
+**Consider creating a poster image that represents a video clip’s contents.** When people tap a poster image, the system replaces the image with the video and begins inline playback. A relevant poster image can help people make an informed decision about whether to view the video. In general, avoid creating a poster image that has nothing to do with the content or that people might mistake for a control.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/playing-video#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/playing-video#Related)
+
+[Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/playing-video#Developer-documentation)
+
+[Configuring your app for media playback](https://developer.apple.com/documentation/AVFoundation/configuring-your-app-for-media-playback) — AVFoundation
+
+[AVKit](https://developer.apple.com/documentation/AVKit)
+
+[HTTP Live Streaming](https://developer.apple.com/streaming/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/playing-video#Videos)
+
+[ Create a great video playback experience ](https://developer.apple.com/videos/play/wwdc2022/10147)
+
+[ Explore video experiences for visionOS ](https://developer.apple.com/videos/play/wwdc2025/304)
+
+[ Deliver a great playback experience on tvOS ](https://developer.apple.com/videos/play/wwdc2021/10191)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/playing-video#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Corrected the recommended width for a thumbnail in visionOS.
+June 21, 2023| Updated to include guidance for visionOS.
+
diff --git a/web-app/public/skills/hig-patterns/references/printing.md b/web-app/public/skills/hig-patterns/references/printing.md
new file mode 100644
index 00000000..32d743fb
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/printing.md
@@ -0,0 +1,50 @@
+---
+title: "Printing | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/printing
+
+# Printing
+
+An iOS, iPadOS, macOS, or visionOS app can integrate system-provided print functionality when it makes sense, presenting custom printer- and document-specific options if necessary.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/printing#Best-practices)
+
+**Make printing discoverable.** Help people find your print action by placing it in standard system locations. For example, include a Print item in your macOS app’s File menu; in your iOS or iPadOS app, add a toolbar button that opens an [action sheet](https://developer.apple.com/design/human-interface-guidelines/action-sheets). If your macOS app has a toolbar, you might want to put a Print button there, too, but consider making it an optional button that people can add when they customize the toolbar.
+
+**Present a printing option only when it’s possible.** If there’s nothing onscreen to print, or no printers are available, dim the Print item in a macOS app’s File menu and remove the Print action from the Action sheet in an iOS or iPadOS app. If you implement a custom print button, dim or hide it when printing isn’t possible.
+
+**Present relevant printing options.** If it makes sense to offer options like selecting a page range, requesting multiple copies, or printing on both sides — and the printer supports the options — use the system-provided view to present them.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/printing#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or visionOS. Not supported in tvOS or watchOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/printing#macOS)
+
+**If your macOS app offers app-specific print options that the system doesn’t offer, consider creating a custom category for the print panel.** By default, the print panel offers several categories of settings, such as Layout, Paper Handling, and Media & Quality. Give your custom category a unique name, such as your app name, and include options that help people have a great print experience in your app. For example, Keynote offers presentation-specific options, like the ability to print presenter notes, slide backgrounds, and skipped slides.
+
+**If your app supports document-specific page settings, consider presenting a page setup dialog.** A _page setup dialog_ includes rarely changed settings for page size, orientation, and scaling that apply to printing a particular document. If this makes sense in your app, avoid implementing features the system already provides. For example, you don’t need to include options like changing the page orientation or printing in reverse order because the system implements these options.
+
+**Make sure interdependencies between options are clear.** For example, if double-sided printing is available, an option to print on transparencies becomes unavailable.
+
+**Separate advanced features from frequently used features.** Consider using a disclosure control to hide advanced options until they’re needed. Label advanced options as _Advanced Options_.
+
+**Consider letting people preview the effect of a setting.** For example, you could update a thumbnail image to show the effect of changing a tone control.
+
+**Consider storing modified settings with the document.** At minimum, it makes sense to store print settings until the document is closed in case people want to print it again.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/printing#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/printing#Related)
+
+[File management](https://developer.apple.com/design/human-interface-guidelines/file-management)
+
+[File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/printing#Developer-documentation)
+
+[`UIPrintInteractionController`](https://developer.apple.com/documentation/UIKit/UIPrintInteractionController) — UIKit
+
+[`NSDocument`](https://developer.apple.com/documentation/AppKit/NSDocument) — AppKit
+
diff --git a/web-app/public/skills/hig-patterns/references/ratings-and-reviews.md b/web-app/public/skills/hig-patterns/references/ratings-and-reviews.md
new file mode 100644
index 00000000..9878415c
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/ratings-and-reviews.md
@@ -0,0 +1,48 @@
+---
+title: "Ratings and reviews | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews
+
+# Ratings and reviews
+
+People often view the ratings and reviews for an app or game before they download it.
+
+
+
+Delivering a great overall experience is the best way to encourage positive ratings and reviews, but it’s also crucial to choose the right time to ask people for feedback. Although every app is different, some possible ways to do this involve looking at how many times or how frequently people launch your app, the number of features someone explores, or the number of tasks they complete.
+
+People can always rate your app within the App Store.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Best-practices)
+
+**Ask for a rating only after people have demonstrated engagement with your app or game.** For example, you might prompt people when they complete a game level or a significant task. Avoid asking for a rating on first launch or during onboarding, because people haven’t had enough time to gain a clear understanding of your app’s value or form an opinion. People may even be more likely to leave negative feedback if they feel an app is asking for a rating before they get a chance to use it.
+
+
+
+**Avoid interrupting people while they’re performing a task or playing a game.** Asking for feedback can disrupt the user experience and feel like a burden. Look for natural breaks or stopping points in your app or game where a rating request is less likely to be bothersome.
+
+**Avoid pestering people.** Repeated rating requests can be irritating, and may even negatively influence people’s opinion of your app. Consider allowing at least a week or two between requests, prompting again after people demonstrate additional engagement with your experience.
+
+**Prefer the system-provided prompt.** iOS, iPadOS, and macOS offer a consistent, nonintrusive way for apps and games to request ratings and reviews. When you identify places in your experience where it makes sense to ask for feedback, the system checks for previous feedback and — if there isn’t any — displays an in-app prompt that asks for a rating and an optional written review. People can supply feedback or dismiss the prompt with a single tap or click; they can also opt out of receiving these prompts for all apps they have installed. The system automatically limits the display of the prompt to three occurrences per app within a 365-day period. For developer guidance, see [`RequestReviewAction`](https://developer.apple.com/documentation/StoreKit/RequestReviewAction).
+
+**Weigh the benefits of resetting your summary rating against the potential disadvantage of showing fewer ratings.** When you release a new version of your app or game, you can reset the summary of individual ratings you received since the last reset. Although resetting means that the ratings reflect the current version, it also tends to result in having fewer ratings overall, which can discourage some people from downloading your app. For developer guidance, see [Reset app summary rating](https://help.apple.com/app-store-connect/#/devfb7e87af8).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Related)
+
+[Ratings, reviews, and responses](https://developer.apple.com/app-store/ratings-and-reviews/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Developer-documentation)
+
+[`RequestReviewAction`](https://developer.apple.com/documentation/StoreKit/RequestReviewAction) — StoreKit
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Added artwork.
+
diff --git a/web-app/public/skills/hig-patterns/references/searching.md b/web-app/public/skills/hig-patterns/references/searching.md
new file mode 100644
index 00000000..7e9cfadd
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/searching.md
@@ -0,0 +1,70 @@
+---
+title: "Searching | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/searching
+
+# Searching
+
+People use various search techniques to find content on their device, within an app, and within a document or file.
+
+
+
+To search for content within an app, people generally expect to use a [search field](https://developer.apple.com/design/human-interface-guidelines/search-fields). When it makes sense, you can personalize the search experience by using what you know about how people interact with your app. For example, you might display recent searches, search suggestions, completions, or corrections based on terms people searched earlier in your app.
+
+In some cases, people appreciate the ability to scope a search or filter the results. For example, people might want to search for items by specifying attributes like creation date, file size, or file type. For guidance, see [Scope controls and tokens](https://developer.apple.com/design/human-interface-guidelines/search-fields#Scope-controls-and-tokens). You can also help people find content within an open document or file by implementing ways to find content in a window or page in your iOS, iPadOS, or macOS app.
+
+In iOS, iPadOS, and macOS, Spotlight helps people find content across all apps in the system and on the web. When you index and provide information about your app’s content, people can use Spotlight to find content your app contains without opening it first. For guidance, see [Systemwide search](https://developer.apple.com/design/human-interface-guidelines/searching#Systemwide-search).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/searching#Best-practices)
+
+**If search is important, consider making it a primary action.** For example, in the Apple TV, Photos, and Phone apps in iOS, search occupies a distinct tab in the [tab bar](https://developer.apple.com/design/human-interface-guidelines/tab-bars). In the Notes app, a search field is in the [toolbar](https://developer.apple.com/design/human-interface-guidelines/toolbars), making search clearly visible and easily accessible.
+
+**Aim to make your app’s content searchable through a single location.** People appreciate having one clearly identified location they can use to find anything in your app that they are looking for. For apps with clearly distinct sections, it may still be useful to offer a local search. For example, search acts as a filter on the current view when searching your Recents and Contacts in the iOS Phone app.
+
+**Use placeholder text to indicate what content is searchable.** For example, the Apple TV app includes the placeholder text _Shows, Movies, and More_.
+
+**Clearly display the current scope of a search.** Use a descriptive placeholder text, a [scope control](https://developer.apple.com/design/human-interface-guidelines/search-fields#Scope-controls-and-tokens), or a title to help reinforce what someone is currently searching. For example, in the Mail app there is always a clear reference to the mailbox someone is searching.
+
+**Provide suggestions to make searching easier.** When you display a personʼs recent searches or offer search suggestions both before and while they’re typing, you can help people search faster and type less. For developer guidance, see [`searchSuggestions(_:)`](https://developer.apple.com/documentation/SwiftUI/View/searchSuggestions\(_:\)).
+
+**Take privacy into consideration before displaying search history.** People might not appreciate having their search history appear where others might see it. Depending on the context, consider providing other ways to narrow the search instead. If you do show search history, provide a way for people to clear it if they want.
+
+## [Systemwide search](https://developer.apple.com/design/human-interface-guidelines/searching#Systemwide-search)
+
+**Make your app’s content searchable in Spotlight.** You can share content with Spotlight by making it indexable and specifying descriptive attributes known as _metadata_. Spotlight extracts, stores, and organizes this information to allow for fast, comprehensive searches.
+
+**Define metadata for custom file types you handle.** Supply a Spotlight File Importer plug-in that describes the types of metadata your file format contains. For developer guidance, see [`CSImportExtension`](https://developer.apple.com/documentation/CoreSpotlight/CSImportExtension).
+
+**Use Spotlight to offer advanced file-search capabilities within the context of your app.** For example, you might include a button that instantly initiates a Spotlight search based on the current selection. You might then display a custom view that presents the search results or a filtered subset of them.
+
+**Prefer using the system-provided open and save views.** The system-provided open and save views generally include a built-in search field that people can use to search and filter the entire system. For related guidance, see [File management](https://developer.apple.com/design/human-interface-guidelines/file-management).
+
+**Implement a Quick Look generator if your app produces custom file types.** A Quick Look generator helps Spotlight and other apps show previews of your documents. For developer guidance, see [Quick Look](https://developer.apple.com/documentation/QuickLook).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/searching#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/searching#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/searching#Related)
+
+[Search fields](https://developer.apple.com/design/human-interface-guidelines/search-fields)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/searching#Developer-documentation)
+
+[Adding your app’s content to Spotlight indexes](https://developer.apple.com/documentation/CoreSpotlight/adding-your-app-s-content-to-spotlight-indexes) — Core Spotlight
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/searching#Videos)
+
+[ Support semantic search with Core Spotlight ](https://developer.apple.com/videos/play/wwdc2024/10131)
+
+[ What’s new in iPad app design ](https://developer.apple.com/videos/play/wwdc2022/10009)
+
+[ Craft search experiences in SwiftUI ](https://developer.apple.com/videos/play/wwdc2021/10176)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/searching#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated best practices with general guidance from Search fields, and reorganized guidance for systemwide search.
+
diff --git a/web-app/public/skills/hig-patterns/references/settings.md b/web-app/public/skills/hig-patterns/references/settings.md
new file mode 100644
index 00000000..b77c06eb
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/settings.md
@@ -0,0 +1,84 @@
+---
+title: "Settings | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/settings
+
+# Settings
+
+People expect apps and games to just work, but they also appreciate having ways to customize the experience to fit their needs.
+
+
+
+On all Apple platforms, the system-provided Settings app lets people adjust things like the overall appearance of the system, network connections, account details, accessibility requirements, and language and region settings. On some platforms, the system-provided Settings app can also include settings for specific apps and games, often letting people adjust whether the app or game can access location information, use device features like microphone or camera, and integrate with system features like notifications, Siri, or Search.
+
+When necessary, you can provide a custom settings area within your app or game to offer general settings that affect your overall experience, like interface style or game-saving behavior. If you need to offer settings that affect only a specific task, you can provide these options within the task itself, so people don’t have to leave the experience to customize it.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/settings#Best-practices)
+
+**Aim to provide default settings that give the best experience to the largest number of people.** For example, you can automatically maximize performance for the device your game is running on instead of asking players to make this choice after your game launches (for developer guidance, see [Improving your game’s graphics performance and settings](https://developer.apple.com/documentation/Metal/improving-your-games-graphics-performance-and-settings)). When you choose appropriate default settings, people may not have to make any adjustments before they can start enjoying your app or game.
+
+**Minimize the number of settings you offer.** Although people appreciate having control over an app or game, too many settings can make the experience feel less approachable, while also making it hard to find a particular setting.
+
+**Make settings available in ways people expect.** For example, when a physical keyboard is connected, people often use the standard Command-Comma (,) keyboard shortcut to open an app’s settings, whereas in a game, players often use the Esc (Escape) key.
+
+**Avoid using settings to ask for setup information you can get in other ways.** For example, a game can automatically detect a connected controller or accessory instead of asking the player to identify it; an app can detect whether people are currently using Dark Mode.
+
+**Respect people’s systemwide settings and avoid including redundant versions of them in your custom settings area.** People expect to use the system-provided Settings app to manage global options like accessibility accommodations, scrolling behavior, and authentication methods, and they expect all apps and games to adhere to their choices. Including custom versions of global options in your settings area is likely to confuse people because it implies that systemwide settings may not apply to your app or game and that changing your custom version of a global setting may affect other apps and games, too.
+
+## [General settings](https://developer.apple.com/design/human-interface-guidelines/settings#General-settings)
+
+**Put general, infrequently changed settings in your custom settings area.** People must suspend what they’re doing to open an app’s or game’s settings area, so you want to include options that people don’t need to change all the time. For example, an app might list options for adjusting window configuration; a game might let players specify game-saving behavior or keyboard mappings; both apps and games might offer options related to people’s accounts.
+
+## [Task-specific options](https://developer.apple.com/design/human-interface-guidelines/settings#Task-specific-options)
+
+**When possible, prefer letting people modify task-specific options without going to your settings area.** For example, if people can adjust things like showing or hiding parts of the current view, reordering a collection of items, or filtering a list, make these options available in the screens they affect, where they’re discoverable and convenient. Putting this type of option in a separate settings area disconnects it from its context, requiring people to suspend their task to make adjustments, and often hiding the results until people resume the task.
+
+Note
+
+In games, players tend to adjust their approach to a specific task as part of the gameplay, not as a settings option to change.
+
+## [System settings](https://developer.apple.com/design/human-interface-guidelines/settings#System-settings)
+
+**Add only the most rarely changed options to the system-provided Settings app.** If it makes sense to add your app’s or game’s settings to the system-provided Settings app, consider providing a button that opens it directly from your interface.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/settings#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, tvOS, or visionOS._
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/settings#macOS)
+
+When people choose the Settings item in your app’s or game’s App menu, your custom settings window opens. Typically, a custom settings window contains a toolbar that includes buttons for switching between views — called _panes_ — that each contain a group of related settings.
+
+**Include a settings item in the[App menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#App-menu).** Avoid adding settings buttons to a window’s toolbar, because doing so decreases the space available for essential commands that people use frequently. If you provide document-level options, add this item to your app’s [File menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#File-menu).
+
+**Dim a settings window’s minimize and maximize buttons.** It’s quick to open a custom settings window using the standard Command–Comma (,) keyboard command, so there’s no need to keep the window in the Dock, and because a settings window accommodates the size of the current pane, people don’t need to expand the window to see more.
+
+**In your settings window, use a noncustomizable toolbar that remains visible and always indicates the active toolbar button.** A settings window’s toolbar identifies the areas people can customize and helps people navigate among those areas. People rely on a stable settings interface to help them find what they need.
+
+**Update the window’s title to reflect the currently visible pane.** If your settings window doesn’t have multiple panes, use the title _App Name_ Settings.
+
+**Restore the most recently viewed pane.** People often adjust related settings more than once, so it can be convenient when a settings window opens to the last pane people used.
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/settings#watchOS)
+
+In watchOS, apps and games don’t add custom settings to the system-provided Settings app. As an alternative, consider making a small number of essential options available at the bottom of the main view or letting people use a More menu to reconfigure objects.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/settings#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/settings#Related)
+
+[Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/settings#Developer-documentation)
+
+[`Settings`](https://developer.apple.com/documentation/SwiftUI/Settings) — SwiftUI
+
+[`UserDefaults`](https://developer.apple.com/documentation/Foundation/UserDefaults) — Foundation
+
+[Preference Panes](https://developer.apple.com/documentation/PreferencePanes)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/settings#Change-log)
+
+Date| Changes
+---|---
+June 10, 2024| Reorganized some guidance into new topics and added game-specific examples.
+
diff --git a/web-app/public/skills/hig-patterns/references/undo-and-redo.md b/web-app/public/skills/hig-patterns/references/undo-and-redo.md
new file mode 100644
index 00000000..16671563
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/undo-and-redo.md
@@ -0,0 +1,58 @@
+---
+title: "Undo and redo | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/undo-and-redo
+
+# Undo and redo
+
+Undo and redo gives people easy ways to reverse many types of actions, which can also help people explore and experiment safely as they learn a new interface or task.
+
+
+
+People expect undo and redo to let them reverse their recent actions, so they’re likely to try undoing — often multiple times — until something changes. In a situation like this, people might not remember which of their previous actions an undo is targeting, which can lead to unintended changes and frustration. To help people remain in control, it’s essential to help people predict the outcome of undoing and redoing and to highlight the results.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Best-practices)
+
+**Help people predict the results of undo and redo as much as possible.** On iPhone, for example, you can describe the result in the alert that displays when people shake the device, giving them the option of performing the undo or canceling it. If you provide undo and redo menu items, you can modify the menu item labels to identify the result. For example, a document-based app might use menu item labels like Undo Typing or Redo Bold.
+
+**Show the results of an undo or redo.** Sometimes, the most recent action that people want to undo affects content or an area that’s no longer visible. In cases like this, it’s crucial to highlight the result of each undo and redo to keep people from thinking that the action had no effect, which can lead them to perform it repeatedly. For example, if people undo after deleting a paragraph in a document area that’s no longer onscreen, you might scroll the document to show the restored paragraph.
+
+**Let people undo multiple times.** Avoid placing unnecessary limits on the number of times people can undo or redo. People generally expect to undo every action they’ve performed since taking a logical step like opening a document or saving their work.
+
+**Consider giving people the option to revert multiple changes at once.** In some scenarios, people might appreciate the ability to undo a batch of discrete but related actions — like incremental adjustments to a single property or attribute — so they don’t have to undo each individual adjustment. In other cases, it can make sense to give people a convenient way to undo all the changes they made since opening a document or saving their work.
+
+**Provide undo and redo buttons only when necessary.** People generally expect to initiate undo and redo in system-supported ways, such as choosing the items in a macOS app’s Edit menu, using keyboard shortcuts on a Mac or iPad, or shaking their iPhone. If it’s important to provide dedicated undo and redo buttons in your app, use the standard system-provided symbols and put the buttons in a toolbar.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Platform-considerations)
+
+ _No additional considerations for visionOS. Not supported in tvOS or watchOS._
+
+### [iOS, iPadOS](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#iOS-iPadOS)
+
+**Avoid redefining standard gestures for undo and redo.** For example, people can use a three-finger swipe to initiate an undo or redo, or shake their iPhone. As with all standard gestures, redefining them in your interface runs the risk of confusing people and making your experience unpredictable.
+
+**Briefly and precisely describe the operation to be undone or redone.** The undo and redo alert title automatically includes a prefix of “Undo ” or “Redo ” (including the trailing space). You need to provide an additional word or two that describes what’s being undone or redone, to appear after this prefix. For example, you might create alert titles such as “Undo Name” or “Redo Address Change.”
+
+### [macOS](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#macOS)
+
+**Place undo and redo commands in the Edit menu and support the standard keyboard shortcuts.** Mac users expect to find undo and redo at the top of the Edit menu; they also expect to use Command–Z and Shift–Command–Z to perform undo and redo, respectively.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Related)
+
+[Feedback](https://developer.apple.com/design/human-interface-guidelines/feedback)
+
+[Pointing devices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices)
+
+[Standard keyboard shortcuts](https://developer.apple.com/design/human-interface-guidelines/keyboards#Standard-keyboard-shortcuts)
+
+[Edit menu](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar#Edit-menu)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Developer-documentation)
+
+[`UndoManager`](https://developer.apple.com/documentation/Foundation/UndoManager) — Foundation
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/undo-and-redo#Videos)
+
+[ Essential Design Principles ](https://developer.apple.com/videos/play/wwdc2017/802)
+
diff --git a/web-app/public/skills/hig-patterns/references/workouts.md b/web-app/public/skills/hig-patterns/references/workouts.md
new file mode 100644
index 00000000..2dfd1d3b
--- /dev/null
+++ b/web-app/public/skills/hig-patterns/references/workouts.md
@@ -0,0 +1,76 @@
+---
+title: "Workouts | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/workouts
+
+# Workouts
+
+A great workout or fitness experience encourages people to engage with their current activity and helps them track their progress on their devices.
+
+
+
+People can wear their Apple Watch during many types of workouts, and they might carry their iPhone or iPad during fitness activities like walking, wheelchair pushing, and running. In contrast, people tend to use their larger or more stationary devices like iPad Pro, Mac, and Apple TV to participate in live or recorded workout sessions by themselves or with others.
+
+You can create a workout experience for Apple Watch, iPhone, or iPad that helps people reach their goals by leveraging activity data from the device and using familiar components to display fitness metrics.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/workouts#Best-practices)
+
+**In a watchOS fitness app, use workout sessions to provide useful data and relevant controls.** During a fitness app’s active workout sessions, watchOS continues to display the app as time passes between wrist raises, so it’s important to provide the workout data people are most likely to care about. For example, you might show elapsed or remaining time, calories burned, or distance traveled, and offer relevant controls like lap or interval markers.
+
+**Avoid distracting people from a workout with information that’s not relevant.** For example, people don’t need to review the list of workouts you offer or access other parts of your app while they’re working out. Here is an arrangement that many watchOS workout apps use, including Workout:
+
+
+
+Large buttons that control the in-progress session — such as End, Resume, and New — appear on the leftmost screen.
+
+
+
+Metrics and other data appear on a dedicated screen that people can read at a glance.
+
+
+
+If supported, media playback controls appear on the rightmost screen.
+
+**Use a distinct visual appearance to indicate an active workout.** During a workout, people appreciate being able to recognize an active session at a glance. The metrics page can be a good way to show that a session is active because the values update in real time. In addition to displaying updating values, you can further distinguish the metrics screen by using a unique layout.
+
+**Provide workout controls that are easy to find and tap.** In addition to making it easy for people to pause, resume, and stop a workout, be sure to provide clear feedback that indicates when a session starts or stops.
+
+**Help people understand the health information your app records if sensor data is unavailable during a workout.** For example, water may prevent a heart-rate measurement, but your app can still record data like the distance people swam and the number of calories they burned. If your app supports the _Swimming_ or _Other_ workout types, explain the situation using language that’s similar to the language used in the system-provided Workout app, as shown below:
+
+| Example text from the Workout app
+---|---
+| GPS is not used during a Pool Swim, and water may prevent a heart-rate measurement, but Apple Watch will still track your calories, laps, and distance using the built-in accelerometer.
+| In this type of workout, you earn the calorie equivalent of a brisk walk anytime sensor readings are unavailable.
+| GPS will only provide distance when you do a freestyle stroke. Water might prevent a heart-rate measurement, but calories will still be tracked using the built-in accelerometer.
+
+**Provide a summary at the end of a session.** A summary screen confirms that a workout is finished and displays the recorded information. Consider enhancing the summary by including Activity rings, so that people can easily check their current progress.
+
+**Discard extremely brief workout sessions.** If a session ends a few seconds after it starts, either discard the data automatically or ask people if they want to record the data as a workout.
+
+**Make sure text is legible for when people are in motion.** When a session requires movement, use large font sizes, high-contrast colors, and arrange text so that the most important information is easy to read.
+
+**Use Activity rings correctly.** The Activity rings view is an Apple-designed element featuring one or more rings whose colors and meanings match those in the Activity app. Use them only for their documented purpose.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/workouts#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or watchOS. Not supported in macOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/workouts#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/workouts#Related)
+
+[Activity rings](https://developer.apple.com/design/human-interface-guidelines/activity-rings)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/workouts#Developer-documentation)
+
+[WorkoutKit](https://developer.apple.com/documentation/WorkoutKit)
+
+[Workouts and activity rings](https://developer.apple.com/documentation/HealthKit/workouts-and-activity-rings) — HealthKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/workouts#Videos)
+
+[ Track workouts with HealthKit on iOS and iPadOS ](https://developer.apple.com/videos/play/wwdc2025/322)
+
+[ Build custom workouts with WorkoutKit ](https://developer.apple.com/videos/play/wwdc2023/10016)
+
+[ Build a workout app for Apple Watch ](https://developer.apple.com/videos/play/wwdc2021/10009)
+
diff --git a/web-app/public/skills/hig-platforms/SKILL.md b/web-app/public/skills/hig-platforms/SKILL.md
new file mode 100644
index 00000000..85eacd9e
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/SKILL.md
@@ -0,0 +1,89 @@
+---
+name: hig-platforms
+version: 1.0.0
+description: ">"
+ Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about
+ "designing for iOS", "iPad app design", "macOS design", "tvOS", "visionOS", "watchOS", "Apple platform",
+ "which platform", platform differences, platform-specific conventions, or multi-platform app design.
+ Also use when the user says "should I design differently for iPad vs iPhone", "how does my app work
+ on visionOS", "what's different about macOS apps", "porting my app to another platform",
+ "universal app design", or "what input methods does this platform use".
+ Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns,
+ hig-components-layout for navigation structures, hig-components-content for content display.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Platform Design
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+1. **Each platform has a distinct identity.** Do not port designs between platforms. Respect each platform's conventions, interaction models, and user expectations.
+
+2. **iOS: touch-first.** Direct manipulation on a handheld screen. Optimize for one-handed use. Navigation uses tab bars and push/pop stacks.
+
+3. **iPadOS: expanded canvas.** Support Split View, Slide Over, and Stage Manager. Use sidebars and multi-column layouts. Support pointer and keyboard alongside touch.
+
+4. **macOS: pointer and keyboard.** Dense information display is acceptable. Use menu bars, toolbars, and keyboard shortcuts extensively. Windows are resizable with precise control.
+
+5. **tvOS: remote and focus.** Viewed from a distance. Design for the Siri Remote with focus-based navigation. Large text, simple layouts, linear navigation.
+
+6. **visionOS: spatial interaction.** 3D environment using windows, volumes, and spaces. Eye tracking for targeting, indirect gestures for interaction. Respect ergonomic comfort zones.
+
+7. **watchOS: glanceable and brief.** Information consumable at a glance. Brief interactions. Digital Crown, haptics, and complications for timely content.
+
+8. **Games: own paradigm.** Free to define in-game interaction models, but still respect platform conventions for system interactions (notifications, accessibility, controllers).
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [designing-for-ios.md](references/designing-for-ios.md) | iOS | Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas |
+| [designing-for-ipados.md](references/designing-for-ipados.md) | iPadOS | Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager |
+| [designing-for-macos.md](references/designing-for-macos.md) | macOS | Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock |
+| [designing-for-tvos.md](references/designing-for-tvos.md) | tvOS | Focus engine, Siri Remote, lean-back experience, content-forward, parallax |
+| [designing-for-visionos.md](references/designing-for-visionos.md) | visionOS | Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth |
+| [designing-for-watchos.md](references/designing-for-watchos.md) | watchOS | Glanceable UI, Digital Crown, complications, notifications, haptics |
+| [designing-for-games.md](references/designing-for-games.md) | Games | Controllers, immersive experiences, platform-specific conventions, accessibility |
+
+## Decision Framework
+
+1. **Identify the primary use context.** On the go (iOS/watchOS), at a desk (macOS), on the couch (tvOS), spatial environment (visionOS)?
+
+2. **Match input to interaction.** Touch for direct manipulation, pointer for precision, gaze+gesture for spatial, Digital Crown for quick scrolling, remote for focus navigation.
+
+3. **Adapt, don't replicate.** A macOS sidebar becomes a tab bar on iPhone. A visionOS volume has no equivalent on watchOS. Translate intent, not implementation.
+
+4. **Leverage platform strengths.** Live Activities on iOS, Desktop Widgets on macOS, complications on watchOS, immersive spaces on visionOS.
+
+5. **Maintain brand consistency** while respecting each platform's visual language and interaction patterns.
+
+## Output Format
+
+1. **Platform-specific recommendations** citing relevant HIG sections.
+2. **Platform differences table** comparing navigation, input, layout, and conventions.
+3. **Implementation notes** per platform including recommended APIs and adaptation strategies.
+
+## Questions to Ask
+
+1. Which platforms are you targeting?
+2. New app or adapting an existing one? If existing, which platform is the base?
+3. SwiftUI or UIKit/AppKit?
+4. Need to support older OS versions?
+5. Primary use context? (On the go, desk, couch, spatial, glanceable?)
+
+## Related Skills
+
+- **hig-foundations** -- Shared principles (color, typography, accessibility, layout) across platforms
+- **hig-patterns** -- Interaction patterns that manifest differently per platform
+- **hig-components-layout** -- Navigation structures (tab bars, sidebars, split views) that vary by platform
+- **hig-components-content** -- Content display that adapts across platforms
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-games.md b/web-app/public/skills/hig-platforms/references/designing-for-games.md
new file mode 100644
index 00000000..a84942ed
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-games.md
@@ -0,0 +1,159 @@
+---
+title: "Designing for games | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-games
+
+# Designing for games
+
+When people play your game on an Apple device, they dive into the world you designed while relying on the platform features they love.
+
+
+
+As you create or adapt a game for Apple platforms, learn how to integrate the fundamental platform characteristics and patterns that help your game feel at home on all Apple devices. To learn what makes each platform unique, see [Designing for iOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios), [Designing for iPadOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados), [Designing for macOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos), [Designing for tvOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos), [Designing for visionOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos), and [Designing for watchOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos). For developer guidance, see [Games Pathway](https://developer.apple.com/games/pathway/).
+
+## [Jump into gameplay](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Jump-into-gameplay)
+
+**Let people play as soon as installation completes.** You don’t want a player’s first experience with your game to be waiting for a lengthy download. Include as much playable content as you can in your game’s initial installation while keeping the download time to 30 minutes or less. Download additional content in the background. For guidance, see [Loading](https://developer.apple.com/design/human-interface-guidelines/loading).
+
+**Provide great default settings.** People appreciate being able to start playing without first having to change a lot of settings. Use information about a player’s device to choose the best defaults for your game, such as the device resolution that makes your graphics look great, automatic recognition of paired accessories and game controllers, and the player’s accessibility settings. Also, make sure your game supports the platform’s most common interaction methods. For guidance, see [Settings](https://developer.apple.com/design/human-interface-guidelines/settings).
+
+**Teach through play.** Players often learn better when they discover new information and mechanics in the context of your game’s world, so it can work well to integrate configuration and onboarding flows into a playable tutorial that engages people quickly and helps them feel successful right away. If you also have a written tutorial, consider offering it as a resource players can refer to when they have questions instead of making it a prerequisite for gameplay. For guidance, see [Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding).
+
+**Defer requests until the right time.** You don’t want to bombard people with too many requests before they start playing, but if your game uses certain sensors on an Apple device or personalizes gameplay by accessing data like hand-tracking, you must first get the player’s permission (for guidance, see [Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy)). To help people understand why you’re making such a request, integrate it into the scenario that requires the data. For example, you could ask permission to track a player’s hands between an initial cutscene and the first time they can use their hands to control the action. Also, make sure people spend quality time with your game before you ask them for a rating or review (for guidance, see [Ratings and reviews](https://developer.apple.com/design/human-interface-guidelines/ratings-and-reviews)).
+
+[ Launching ](https://developer.apple.com/design/human-interface-guidelines/launching)
+
+[ Onboarding ](https://developer.apple.com/design/human-interface-guidelines/onboarding)
+
+[ Loading ](https://developer.apple.com/design/human-interface-guidelines/loading)
+
+## [Look stunning on every display](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Look-stunning-on-every-display)
+
+**Make sure text is always legible.** When game text is hard to read, people can struggle to follow the narrative, understand important instructions and information, and stay engaged in the experience. To keep text comfortably legible on each device, ensure that it contrasts well with the background and uses at least the recommended minimum text size in each platform. For guidance, see [Typography](https://developer.apple.com/design/human-interface-guidelines/typography); for developer guidance, see [Adapting your game interface for smaller screens](https://developer.apple.com/documentation/Metal/adapting-your-game-interface-for-smaller-screens).
+
+Platform| Default text size| Minimum text size
+---|---|---
+iOS, iPadOS| 17 pt| 11 pt
+macOS| 13 pt| 10 pt
+tvOS| 29 pt| 23 pt
+visionOS| 17 pt| 12 pt
+watchOS| 16 pt| 12 pt
+
+**Make sure buttons are always easy to use.** Buttons that are too small or too close together can frustrate players and make gameplay less fun. Each platform defines a recommended minimum button size based on its default interaction method. For example, buttons in iOS must be at least 44x44 pt to accommodate touch interaction. For guidance, see [Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons).
+
+Platform| Default button size| Minimum button size
+---|---|---
+iOS, iPadOS| 44x44 pt| 28x28 pt
+macOS| 28x28 pt| 20x20 pt
+tvOS| 66x66 pt| 56x56 pt
+visionOS| 60x60 pt| 28x28 pt
+watchOS| 44x44 pt| 28x28 pt
+
+**Prefer resolution-independent textures and graphics.** If creating resolution-independent assets isn’t possible, match the resolution of your game to the resolution of the device. In visionOS, prefer vector-based art that can continue to look good when the system dynamically scales it as people view it from different distances and angles. For guidance, see [Images](https://developer.apple.com/design/human-interface-guidelines/images).
+
+**Integrate device features into your layout.** For example, a device may have rounded corners or a camera housing that can affect parts of your interface. To help your game look at home on each device, accommodate such features during layout, relying on platform-provided safe areas when possible (for developer guidance, see [Positioning content relative to the safe area](https://developer.apple.com/documentation/UIKit/positioning-content-relative-to-the-safe-area)). For guidance, see [Layout](https://developer.apple.com/design/human-interface-guidelines/layout); for templates that include safe-area guides, see [Apple Design Resources](https://developer.apple.com/design/resources/).
+
+**Make sure in-game menus adapt to different aspect ratios.** Games need to look good and behave well at various aspect ratios, such as 16:10, 19.5:9, and 4:3. In particular, in-game menus need to remain legible and easy to use on every device — and, if you support them, in both orientations on iPhone and iPad — without obscuring other content. To help ensure your in-game menus render correctly, consider using dynamic layouts that rely on relative constraints to adjust to different contexts. Avoid fixed layouts as much as possible, and aim to create a custom, device-specific layout only when necessary. For guidance, see [In-game menus](https://developer.apple.com/design/human-interface-guidelines/menus#In-game-menus).
+
+**Design for the full-screen experience.** People often enjoy playing a game in a distraction-free, full-screen context. In macOS, iOS, and iPadOS, full-screen mode lets people hide other apps and parts of the system UI; in visionOS, a game running in a Full Space can completely surround people, transporting them somewhere else. For guidance, see [Going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen).
+
+[ Layout ](https://developer.apple.com/design/human-interface-guidelines/layout)
+
+[ Typography ](https://developer.apple.com/design/human-interface-guidelines/typography)
+
+[ Going full screen ](https://developer.apple.com/design/human-interface-guidelines/going-full-screen)
+
+## [Enable intuitive interactions](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Enable-intuitive-interactions)
+
+**Support each platform’s default interaction method.** For example, people generally use touch to play games on iPhone; on a Mac, players tend to expect keyboard and mouse or trackpad support; and in a visionOS game, people expect to use their eyes and hands while making indirect and direct gestures. As you work to ensure that your game supports each platform’s default interaction method, pay special attention to control sizing and menu behavior, especially when bringing your game from a pointer-based context to a touch-based one.
+
+Platform| Default interaction methods| Additional interaction methods
+---|---|---
+iOS| Touch| Game controller
+iPadOS| Touch| Game controller, keyboard, mouse, trackpad, Apple Pencil
+macOS| Keyboard, mouse, trackpad| Game controller
+tvOS| Remote| Game controller, keyboard, mouse, trackpad
+visionOS| Touch| Game controller, keyboard, mouse, trackpad, spatial game controller
+watchOS| Touch| –
+
+**Support physical game controllers, while also giving people alternatives.** Every platform except watchOS supports physical game controllers. Although the presence of a game controller makes it straightforward to port controls from an existing game and handle complex control mappings, recognize that not every player can use a physical game controller. To make your game available to as many players as possible, also offer alternative ways to interact with your game. For guidance, see [Physical controllers](https://developer.apple.com/design/human-interface-guidelines/game-controls#Physical-controllers).
+
+**Offer touch-based game controls that embrace the touchscreen experience on iPhone and iPad.** In iOS and iPadOS, your game can allow players to interact directly with game elements, and to control the game using virtual controls that appear on top of your game content. For design guidance, see [Touch controls](https://developer.apple.com/design/human-interface-guidelines/game-controls#Touch-controls).
+
+[ Game controls ](https://developer.apple.com/design/human-interface-guidelines/game-controls)
+
+[ Gestures ](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+[ Pointing devices ](https://developer.apple.com/design/human-interface-guidelines/pointing-devices)
+
+## [Welcome everyone](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Welcome-everyone)
+
+**Prioritize perceivability.** Make sure people can perceive your game’s content whether they use sight, hearing, or touch. For example, avoid relying solely on color to convey an important detail, or providing a cutscene that doesn’t include descriptive subtitles or offer other ways to read the content. For specific guidance, see:
+
+ * Text sizes
+
+ * Color and effects
+
+ * Motion
+
+ * Interactions
+
+ * Buttons
+
+
+
+
+**Help players personalize their experience.** Players have a variety of preferences and abilities that influence their interactions with your game. Because there’s no universal configuration that suits everyone, give players the ability to customize parameters like type size, game control mapping, motion intensity, and sound balance. You can take advantage of built-in [Apple accessibility technologies](https://developer.apple.com/accessibility/) to support accessibility personalizations, whether you’re using system frameworks or [Unity plug-ins](https://github.com/Apple/UnityPlugins).
+
+**Give players the tools they need to represent themselves.** If your game encourages players to create avatars or supply names or descriptions, support the spectrum of self-identity and provide options that represent as many human characteristics as possible.
+
+**Avoid stereotypes in your stories and characters.** Ask yourself whether you’re depicting game characters and scenarios in a way that perpetuates real-life stereotypes. For example, does your game depict enemies as having a certain race, gender, or cultural heritage? Review your game to uncover and remove biases and stereotypes and — if references to real-life cultures and languages are necessary — be sure they’re respectful.
+
+[ Accessibility ](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[ Inclusion ](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+## [Adopt Apple technologies](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Adopt-Apple-technologies)
+
+**Integrate Game Center to help players discover your game across their devices and connect with their friends.** [Game Center](https://developer.apple.com/game-center/) is Apple’s social gaming network, available on all platforms. Game Center lets players keep track of their progress and achievements and allows you to set up leaderboards, challenges, and multiplayer activities in your game. For design guidance, see [Game Center](https://developer.apple.com/design/human-interface-guidelines/game-center); for developer guidance, see [GameKit](https://developer.apple.com/documentation/GameKit).
+
+**Let players pick up their game on any of their devices.** People often have a single iCloud account that they use across multiple Apple devices. When you support [GameSave](https://developer.apple.com/documentation/GameSave), you can help people save their game state and start back up exactly where they left off on a different device.
+
+**Support haptics to help players feel the action.** When you adopt Core Haptics, you can compose and play custom haptic patterns, optionally combined with custom audio content. Core Haptics is available in iOS, iPadOS, tvOS, and visionOS, and supported on many game controllers. For guidance, see [Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics); for developer guidance, see [Core Haptics](https://developer.apple.com/documentation/CoreHaptics) and [Playing Haptics on Game Controllers](https://developer.apple.com/documentation/CoreHaptics/playing-haptics-on-game-controllers).
+
+**Use Spatial Audio to immerse players in your game’s soundscape.** Providing multichannel audio can help your game’s audio adapt automatically to the current device, enabling an immersive Spatial Audio experience where supported. For guidance, see [Playing audio > visionOS](https://developer.apple.com/design/human-interface-guidelines/playing-audio#visionOS); for developer guidance, see [Explore Spatial Audio](https://developer.apple.com/news/?id=fakg1z5b).
+
+**Take advantage of Apple technologies to enable unique gameplay mechanics.** For example, you can integrate technologies like augmented reality, machine learning, and [HealthKit](https://developer.apple.com/documentation/HealthKit), and request access to location data and functionality like camera and microphone. For a full list of Apple technologies, features, and services, see [Technologies](https://developer.apple.com/design/human-interface-guidelines/technologies).
+
+[ Game Center ](https://developer.apple.com/design/human-interface-guidelines/game-center)
+
+[ iCloud ](https://developer.apple.com/design/human-interface-guidelines/icloud)
+
+[ In-app purchase ](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase)
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Related)
+
+[Game Center](https://developer.apple.com/design/human-interface-guidelines/game-center)
+
+[Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Developer-documentation)
+
+[Games Pathway](https://developer.apple.com/games/get-started/)
+
+[Create games for Apple platforms](https://developer.apple.com/games/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Videos)
+
+[ Level up your games ](https://developer.apple.com/videos/play/wwdc2025/209)
+
+[ Design advanced games for Apple platforms ](https://developer.apple.com/videos/play/wwdc2024/10085)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/designing-for-games#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Updated guidance for touch-based controls and Game Center.
+June 10, 2024| New page.
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-ios.md b/web-app/public/skills/hig-platforms/references/designing-for-ios.md
new file mode 100644
index 00000000..b389da34
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-ios.md
@@ -0,0 +1,66 @@
+---
+title: "Designing for iOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-ios
+
+# Designing for iOS
+
+People depend on their iPhone to help them stay connected, play games, view media, accomplish tasks, and track personal data in any location and while on the go.
+
+
+
+As you begin designing your app or game for iOS, start by understanding the following fundamental device characteristics and patterns that distinguish the iOS experience. Using these characteristics and patterns to inform your design decisions can help you provide an app or game that iPhone users appreciate.
+
+**Display.** iPhone has a medium-size, high-resolution display.
+
+**Ergonomics.** People generally hold their iPhone in one or both hands as they interact with it, switching between landscape and portrait orientations as needed. While people are interacting with the device, their viewing distance tends to be no more than a foot or two.
+
+**Inputs.** Multi-Touch [gestures](https://developer.apple.com/design/human-interface-guidelines/gestures), [virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards), and [voice](https://developer.apple.com/design/human-interface-guidelines/siri) control let people perform actions and accomplish meaningful tasks while they’re on the go. In addition, people often want apps to use their [personal data](https://developer.apple.com/design/human-interface-guidelines/privacy) and input from the device’s [gyroscope and accelerometer](https://developer.apple.com/design/human-interface-guidelines/gyro-and-accelerometer), and they may also want to participate in [spatial interactions](https://developer.apple.com/design/human-interface-guidelines/spatial-interactions).
+
+**App interactions.** Sometimes, people spend just a minute or two checking on event or social media updates, tracking data, or sending messages. At other times, people can spend an hour or more browsing the web, playing games, or enjoying media. People typically have multiple apps open at the same time, and they appreciate switching frequently among them.
+
+**System features.** iOS provides several features that help people interact with the system and their apps in familiar, consistent ways.
+
+ * [Widgets](https://developer.apple.com/design/human-interface-guidelines/widgets)
+
+ * [Home Screen quick actions](https://developer.apple.com/design/human-interface-guidelines/home-screen-quick-actions)
+
+ * [Spotlight](https://developer.apple.com/design/human-interface-guidelines/searching)
+
+ * [Shortcuts](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions)
+
+ * [Activity views](https://developer.apple.com/design/human-interface-guidelines/activity-views)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios#Best-practices)
+
+Great iPhone experiences integrate the platform and device capabilities that people value most. To help your design feel at home in iOS, prioritize the following ways to incorporate these features and capabilities.
+
+ * Help people concentrate on primary tasks and content by limiting the number of onscreen controls while making secondary details and actions discoverable with minimal interaction.
+
+ * Adapt seamlessly to appearance changes — like device orientation, Dark Mode, and Dynamic Type — letting people choose the configurations that work best for them.
+
+ * Support interactions that accommodate the way people usually hold their device. For example, it tends to be easier and more comfortable for people to reach a control when it’s located in the middle or bottom area of the display, so it’s especially important let people swipe to navigate back or initiate actions in a list row.
+
+ * With people’s permission, integrate information available through platform capabilities in ways that enhance the experience without asking people to enter data. For example, you might accept payments, provide security through biometric authentication, or offer features that use the device’s location.
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#ios-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios#Developer-documentation)
+
+[iOS Pathway](https://developer.apple.com/ios/get-started/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios#Videos)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-ipados.md b/web-app/public/skills/hig-platforms/references/designing-for-ipados.md
new file mode 100644
index 00000000..1fdd308f
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-ipados.md
@@ -0,0 +1,64 @@
+---
+title: "Designing for iPadOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados
+
+# Designing for iPadOS
+
+People value the power, mobility, and flexibility of iPad as they enjoy media, play games, perform detailed productivity tasks, and bring their creations to life.
+
+
+
+As you begin designing your app or game for iPad, start by understanding the following fundamental device characteristics and patterns that distinguish the iPadOS experience. Using these characteristics and patterns to inform your design decisions can help you provide an app or game that iPad users appreciate.
+
+**Display.** iPad has a large, high-resolution display.
+
+**Ergonomics.** People often hold their iPad while using it, but they might also set it on a surface or place it on a stand. Positioning the device in different ways can change the viewing distance, although people are typically within about 3 feet of the device as they interact with it.
+
+**Inputs.** People can interact with iPad using Multi-Touch [gestures](https://developer.apple.com/design/human-interface-guidelines/gestures) and [virtual keyboards](https://developer.apple.com/design/human-interface-guidelines/virtual-keyboards), an attached [keyboard](https://developer.apple.com/design/human-interface-guidelines/keyboards) or [pointing device](https://developer.apple.com/design/human-interface-guidelines/pointing-devices), [Apple Pencil](https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble), or [voice](https://developer.apple.com/design/human-interface-guidelines/siri), and they often combine multiple input modes.
+
+**App interactions.** Sometimes, people perform a few quick actions on their iPad. At other times, they spend hours immersed in games, media, content creation, or productivity tasks. People frequently have multiple apps open at the same time, and they appreciate viewing more than one app onscreen at once and taking advantage of inter-app capabilities like drag and drop.
+
+**System features.** iPadOS provides several features that help people interact with the system and their apps in familiar, consistent ways.
+
+ * [Multitasking](https://developer.apple.com/design/human-interface-guidelines/multitasking)
+
+ * [Widgets](https://developer.apple.com/design/human-interface-guidelines/widgets)
+
+ * [Drag and drop](https://developer.apple.com/design/human-interface-guidelines/drag-and-drop)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados#Best-practices)
+
+Great iPad experiences integrate the platform and device capabilities that people value most. To help your experience feel at home in iPadOS, prioritize the following ways to incorporate these features and capabilities.
+
+ * Take advantage of the large display to elevate the content people care about, minimizing modal interfaces and full-screen transitions, and positioning onscreen controls where they’re easy to reach, but not in the way.
+
+ * Use viewing distance and input mode to help you determine the size and density of the onscreen content you display.
+
+ * Let people use Multi-Touch gestures, a physical keyboard or trackpad, or Apple Pencil, and consider supporting unique interactions that combine multiple input modes.
+
+ * Adapt seamlessly to appearance changes — like device orientation, multitasking modes, Dark Mode, and Dynamic Type — and transition effortlessly to running in macOS, letting people choose the configurations that work best for them.
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#ios-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados#Developer-documentation)
+
+[iPadOS Pathway](https://developer.apple.com/ipados/get-started/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados#Videos)
+
+[ Elevate the design of your iPad app ](https://developer.apple.com/videos/play/wwdc2025/208)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-macos.md b/web-app/public/skills/hig-platforms/references/designing-for-macos.md
new file mode 100644
index 00000000..f9c54d6d
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-macos.md
@@ -0,0 +1,70 @@
+---
+title: "Designing for macOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-macos
+
+# Designing for macOS
+
+People rely on the power, spaciousness, and flexibility of a Mac as they perform in-depth productivity tasks, view media or content, and play games, often using several apps at once.
+
+
+
+As you begin designing your app or game for macOS, start by understanding the fundamental device characteristics and patterns that distinguish the macOS experience. Using these characteristics and patterns to inform your design decisions can help you provide an app or game that Mac users appreciate.
+
+**Display.** A Mac typically has a large, high-resolution display, and people can extend their workspace by connecting additional displays, including their iPad.
+
+**Ergonomics.** People generally use a Mac while they’re stationary, often placing the device on a desk or table. In the typical use case, the viewing distance can range from about 1 to 3 feet.
+
+**Inputs.** People expect to enter data and control the interface using any combination of input modes, such as physical [Keyboards](https://developer.apple.com/design/human-interface-guidelines/keyboards), [Pointing devices](https://developer.apple.com/design/human-interface-guidelines/pointing-devices), [Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls), and [Siri](https://developer.apple.com/design/human-interface-guidelines/siri).
+
+**App interactions.** Interactions can last anywhere from a few minutes of performing some quick tasks to several hours of deep concentration. People frequently have multiple apps open at the same time, and they expect smooth transitions between active and inactive states as they switch from one app to another.
+
+**System features.** macOS provides several features that help people interact with the system and their apps in familiar, consistent ways.
+
+ * [The menu bar](https://developer.apple.com/design/human-interface-guidelines/the-menu-bar)
+
+ * [File management](https://developer.apple.com/design/human-interface-guidelines/file-management)
+
+ * [Going full screen](https://developer.apple.com/design/human-interface-guidelines/going-full-screen)
+
+ * [Dock menus](https://developer.apple.com/design/human-interface-guidelines/dock-menus)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos#Best-practices)
+
+Great Mac experiences integrate the platform and device capabilities that people value most. To help your design feel at home in macOS, prioritize the following ways to incorporate these features and capabilities.
+
+ * Leverage large displays to present more content in fewer nested levels and with less need for modality, while maintaining a comfortable information density that doesn’t make people strain to view the content they want.
+
+ * Let people resize, hide, show, and move your windows to fit their work style and device configuration, and support full-screen mode to offer a distraction-free context.
+
+ * Use the menu bar to give people easy access to all the commands they need to do things in your app.
+
+ * Help people take advantage of high-precision input modes to perform pixel-perfect selections and edits.
+
+ * Handle keyboard shortcuts to help people accelerate actions and use keyboard-only work styles.
+
+ * Support personalization, letting people customize toolbars, configure windows to display the views they use most, and choose the colors and fonts they want to see in the interface.
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#macos-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos#Developer-documentation)
+
+[macOS Pathway](https://developer.apple.com/macos/get-started/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos#Videos)
+
+[ Meet Liquid Glass ](https://developer.apple.com/videos/play/wwdc2025/219)
+
+[ Get to know the new design system ](https://developer.apple.com/videos/play/wwdc2025/356)
+
+[ Build an AppKit app with the new design ](https://developer.apple.com/videos/play/wwdc2025/310)
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-tvos.md b/web-app/public/skills/hig-platforms/references/designing-for-tvos.md
new file mode 100644
index 00000000..e50ca678
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-tvos.md
@@ -0,0 +1,68 @@
+---
+title: "Designing for tvOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos
+
+# Designing for tvOS
+
+People enjoy the vibrant content, immersive experiences, and streamlined interactions that tvOS delivers in media and games, as well as in fitness, education, and home utility apps.
+
+
+
+As you begin designing your app or game for tvOS, start by understanding the following fundamental device characteristics and patterns that distinguish the tvOS experience. Using these characteristics and patterns to inform your design decisions can help you provide an app or game that tvOS users appreciate.
+
+**Display.** A TV typically has a very large, high-resolution display.
+
+**Ergonomics.** Although people generally remain many feet away from their stationary TV — often 8 feet or more — they sometimes continue to interact with content as they move around the room.
+
+**Inputs.** People can use a [remote](https://developer.apple.com/design/human-interface-guidelines/remotes), a [game controller](https://developer.apple.com/design/human-interface-guidelines/game-controls), their [voice](https://developer.apple.com/design/human-interface-guidelines/siri), and apps running on their other devices to interact with Apple TV.
+
+**App interactions.** People can get deeply immersed in a single experience — often lasting hours — but they also appreciate using a picture-in-picture view to simultaneously follow an alternative app or video.
+
+**System features.** Apple TV users expect their apps and games to integrate well with the following system experiences.
+
+ * [Integrating with the TV app](https://developer.apple.com/design/human-interface-guidelines/playing-video#Integrating-with-the-TV-app)
+
+ * [SharePlay](https://developer.apple.com/design/human-interface-guidelines/shareplay)
+
+ * [Top Shelf](https://developer.apple.com/design/human-interface-guidelines/top-shelf)
+
+ * [TV provider accounts](https://developer.apple.com/design/human-interface-guidelines/managing-accounts#TV-provider-accounts)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Best-practices)
+
+Great tvOS experiences integrate the platform and device capabilities that people value most. To help your experience feel at home in tvOS, prioritize the following ways to incorporate these features and capabilities.
+
+ * Support powerful, delightful interactions through the fluid, familiar gestures people make with the Siri Remote.
+
+ * Embrace the tvOS focus system, letting it gently highlight and expand onscreen items as people move among them, helping them know what to do and where they are at all times.
+
+ * Deliver beautiful, edge-to-edge artwork, subtle and fluid animations, and engaging audio, wrapping people in a rich, cinematic experience that’s clear, legible, and captivating from across the room.
+
+ * Enhance multiuser support by making sign-in easy and infrequent, handling shared sign-in, and automatically switching profiles when people change the current viewer.
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#tvos-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Developer-documentation)
+
+[tvOS Pathway](https://developer.apple.com/tvos/get-started/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Videos)
+
+[ Build SwiftUI apps for tvOS ](https://developer.apple.com/videos/play/wwdc2020/10042)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/designing-for-tvos#Change-log)
+
+Date| Changes
+---|---
+September 14, 2022| Refined best practices for multiuser support.
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-visionos.md b/web-app/public/skills/hig-platforms/references/designing-for-visionos.md
new file mode 100644
index 00000000..96da90b5
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-visionos.md
@@ -0,0 +1,85 @@
+---
+title: "Designing for visionOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos
+
+# Designing for visionOS
+
+When people wear Apple Vision Pro, they enter an infinite 3D space where they can engage with your app or game while staying connected to their surroundings.
+
+
+
+As you begin designing your app or game for visionOS, start by understanding the fundamental device characteristics and patterns that distinguish the platform. Use these characteristics and patterns to inform your design decisions and help you create immersive and engaging experiences.
+
+**Space.** Apple Vision Pro offers a limitless canvas where people can view virtual content like [windows](https://developer.apple.com/design/human-interface-guidelines/windows), [volumes](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS-volumes), and 3D objects, and choose to enter deeply immersive experiences that can transport them to different places.
+
+**Immersion.** In a visionOS app, people can fluidly transition between different levels of [immersion](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences). By default, an app launches in the _Shared Space_ where multiple apps can run side-by-side and people can open, close, and relocate windows. People can also choose to transition an app to a _Full Space_ , where it’s the only app running. While in a Full Space app, people can view 3D content blended with their surroundings, open a portal to view another place, or enter a different world.
+
+**Passthrough.** [Passthrough](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences#Immersion-and-passthrough) provides live video from the device’s external cameras, and helps people interact with virtual content while also seeing their actual surroundings. When people want to see more or less of their surroundings, they use the [Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown) to control the amount of passthrough.
+
+**Spatial Audio.** Apple Vision Pro combines acoustic and visual-sensing technologies to model the sonic characteristics of a person’s surroundings, automatically making audio sound natural in their space. When an app receives a person’s permission to access information about their surroundings, it can fine-tune [Spatial Audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio#visionOS) to bring custom experiences to life.
+
+**Eyes and hands.** In general, people perform most actions by using their [eyes](https://developer.apple.com/design/human-interface-guidelines/eyes) to look at a virtual object and making an _indirect_ [gesture](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS), like a tap, to activate it. People can also interact with a virtual object by using a _direct_ gesture, like touching it with a finger.
+
+**Ergonomics.** While wearing Apple Vision Pro, people rely entirely on the device’s cameras for everything they see, both real and virtual, so maintaining visual comfort is paramount. The system helps maintain comfort by automatically placing content so it’s relative to the wearer’s head, regardless of the person’s height or whether they’re sitting, standing, or lying down. Because visionOS brings content to people — instead of making people move to reach the content — people can remain at rest while engaging with apps and games.
+
+**Accessibility.** Apple Vision Pro supports [accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility) technologies like VoiceOver, Switch Control, Dwell Control, Guided Access, Head Pointer, and many more, so people can use the interactions that work for them. In visionOS, as in all platforms, system-provided UI components build in accessibility support by default, while system frameworks give you ways to enhance the accessibility of your app or game.
+
+Important
+
+When building your app for Apple Vision Pro, be sure to consider the unique characteristics of the device and its spatial computing environment, and pay special attention to your user’s safety; for more details about these characteristics, see [Apple Vision Pro User Guide](https://support.apple.com/guide/apple-vision-pro). For example, Apple Vision Pro should not be used while operating a vehicle or heavy machinery. The device is also not designed to be used while moving around unsafe environments such as near balconies, streets, stairs, or other potential hazards. Note that Apple Vision Pro is designed to be fit and used only by individuals 13 years of age or older.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Best-practices)
+
+Great visionOS apps and games are approachable and familiar, while offering extraordinary experiences that can surround people with beautiful content, expanded capabilities, and captivating adventures.
+
+**Embrace the unique features of Apple Vision Pro.** Take advantage of space, Spatial Audio, and immersion to bring life to your experiences, while integrating passthrough and spatial input from eyes and hands in ways that feel at home on the device.
+
+**Consider different types of immersion as you design ways to present your app’s most distinctive moments.** You can present experiences in a windowed, UI-centric context, a fully immersive context, or something in between. For each key moment in your app, find the minimum level of immersion that suits it best — don’t assume that every moment needs to be fully immersive.
+
+**Use windows for contained, UI-centric experiences.** To help people perform standard tasks, prefer standard [windows](https://developer.apple.com/design/human-interface-guidelines/windows#visionOS) that appear as planes in space and contain familiar controls. In visionOS, people can relocate windows anywhere they want, and the system’s [dynamic scaling](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Scale) helps keep window content legible whether it’s near or far.
+
+**Prioritize comfort.** To help people stay comfortable and physically relaxed as they interact with your app or game, keep the following fundamentals in mind.
+
+ * Display content within a person’s [field of view](https://developer.apple.com/design/human-interface-guidelines/spatial-layout#Field-of-view), positioning it relative to their head. Avoid placing content in places where people have to turn their head or change their position to interact with it.
+
+ * Avoid displaying [motion](https://developer.apple.com/design/human-interface-guidelines/motion#visionOS) that’s overwhelming, jarring, too fast, or missing a stationary frame of reference.
+
+ * Support [indirect gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#visionOS) that let people interact with apps while their hands rest in their lap or at their sides.
+
+ * If you support direct gestures, make sure the interactive content isn’t too far away and that people don’t need to interact with it for extended periods.
+
+ * Avoid encouraging people to move too much while they’re in a fully [immersive experience](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+
+
+
+**Help people share activities with others.** When you use [SharePlay](https://developer.apple.com/design/human-interface-guidelines/shareplay#visionOS) to support shared activities, people can view the _spatial Personas_ of other participants, making it feel like everyone is together in the same space.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#visionos-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Developer-documentation)
+
+[visionOS Pathway](https://developer.apple.com/visionos/get-started/)
+
+[Creating your first visionOS app](https://developer.apple.com/documentation/visionOS/creating-your-first-visionos-app)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Videos)
+
+[ Design interactive experiences for visionOS ](https://developer.apple.com/videos/play/wwdc2024/10096)
+
+[ Design great visionOS apps ](https://developer.apple.com/videos/play/wwdc2024/10086)
+
+[ Principles of spatial design ](https://developer.apple.com/videos/play/wwdc2023/10072)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos#Change-log)
+
+Date| Changes
+---|---
+February 2, 2024| Included a link to Apple Vision Pro User Guide.
+September 12, 2023| Updated intro artwork.
+June 21, 2023| New page.
+
diff --git a/web-app/public/skills/hig-platforms/references/designing-for-watchos.md b/web-app/public/skills/hig-platforms/references/designing-for-watchos.md
new file mode 100644
index 00000000..69bd57cc
--- /dev/null
+++ b/web-app/public/skills/hig-platforms/references/designing-for-watchos.md
@@ -0,0 +1,74 @@
+---
+title: "Designing for watchOS | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos
+
+# Designing for watchOS
+
+When people glance at their Apple Watch, they know they can access essential information and perform simple, timely tasks whether they’re stationary or in motion.
+
+
+
+As you begin designing your app for Apple Watch, start by understanding the following fundamental device characteristics and patterns that distinguish the watchOS experience. Using these characteristics and patterns to inform your design decisions can help you provide an app that Apple Watch users appreciate.
+
+**Display.** The small Apple Watch display fits on the wrist while delivering an easy-to-read, high-resolution experience.
+
+**Ergonomics.** Because people wear Apple Watch, they’re usually no more than a foot away from the display as they raise their wrist to view it and use their opposite hand to interact with the device. In addition, the Always On display lets people view information on the watch face when they drop their wrist.
+
+**Inputs.** People can navigate vertically or inspect data by turning the [Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown), which offers consistent control on the watch face, the Home Screen, and within apps. They can provide input even while they’re in motion with standard [gestures](https://developer.apple.com/design/human-interface-guidelines/gestures) like tap, swipe, and drag. Pressing the [Action button](https://developer.apple.com/design/human-interface-guidelines/action-button) initiates an essential action without looking at the screen, and using [shortcuts](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions) helps people perform their routine tasks quickly and easily. People can also take advantage of data that device features provide, such as GPS, sensors for blood oxygen and heart function, and the altimeter, accelerometer, and gyroscope.
+
+**App interactions.** People glance at the Always On display many times throughout the day, performing concise app interactions that can last for less than a minute each. People frequently use a watchOS app’s related experiences — like complications, notifications, and Siri interactions — more than they use the app itself.
+
+**System features.** watchOS provides several features that help people interact with the system and their apps in familiar, consistent ways.
+
+ * [Complications](https://developer.apple.com/design/human-interface-guidelines/complications)
+
+ * [Notifications](https://developer.apple.com/design/human-interface-guidelines/notifications)
+
+ * [Always On](https://developer.apple.com/design/human-interface-guidelines/always-on)
+
+ * [Watch faces](https://developer.apple.com/design/human-interface-guidelines/watch-faces)
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Best-practices)
+
+Great Apple Watch experiences are streamlined and specialized, and integrate the platform and device capabilities that people value most. To help your experience feel at home in watchOS, prioritize the following ways to incorporate these features and capabilities.
+
+ * Support quick, glanceable, single-screen interactions that deliver critical information succinctly and help people perform targeted actions with a simple gesture or two.
+
+ * Minimize the depth of hierarchy in your app’s navigation, and use the [Digital Crown](https://developer.apple.com/design/human-interface-guidelines/digital-crown) to provide vertical navigation for scrolling or switching between screens.
+
+ * Personalize the experience by proactively anticipating people’s needs and using on-device data to provide actionable content that’s relevant in the moment or very soon.
+
+ * Use [complications](https://developer.apple.com/design/human-interface-guidelines/complications) to provide relevant, potentially dynamic data and graphics right on the watch face where people can view them on every wrist raise and tap them to dive straight into your app.
+
+ * Use [notifications](https://developer.apple.com/design/human-interface-guidelines/notifications) to deliver timely, high-value information and let people perform important actions without opening your app.
+
+ * Use background content such as [color](https://developer.apple.com/design/human-interface-guidelines/color) to convey useful supporting information, and use [materials](https://developer.apple.com/design/human-interface-guidelines/materials) to illustrate hierarchy and a sense of place.
+
+ * Design your app to function independently, complementing your notifications and complications by providing additional details and functionality.
+
+
+
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#watchos-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Developer-documentation)
+
+[watchOS Pathway](https://developer.apple.com/watchos/get-started/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Videos)
+
+[ What’s new in watchOS 26 ](https://developer.apple.com/videos/play/wwdc2025/334)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Enhanced guidance for providing a glanceable, focused app experience, and emphasized the importance of the Digital Crown in navigation.
+
diff --git a/web-app/public/skills/hig-project-context/SKILL.md b/web-app/public/skills/hig-project-context/SKILL.md
new file mode 100644
index 00000000..1a49d8d1
--- /dev/null
+++ b/web-app/public/skills/hig-project-context/SKILL.md
@@ -0,0 +1,138 @@
+---
+name: hig-project-context
+version: 1.0.0
+description: ">-"
+ Create or update a shared Apple design context document that other HIG skills
+ use to tailor guidance. Use when the user says "set up my project context,"
+ "what platforms am I targeting," "configure HIG settings," or when starting a
+ new Apple platform project. Also activates when other HIG skills need project
+ context but none exists yet. This skill creates .claude/apple-design-context.md
+ so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and
+ hig-technologies can provide targeted advice without repetitive questions.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Project Context
+
+Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Gathering Context
+
+Before asking questions, auto-discover context from:
+
+1. **README.md** -- Product description, platform targets
+2. **Package.swift / .xcodeproj** -- Supported platforms, minimum OS versions, dependencies
+3. **Info.plist** -- App category, required capabilities, supported orientations
+4. **Existing code** -- Import statements reveal frameworks (SwiftUI vs UIKit, HealthKit, etc.)
+5. **Assets.xcassets** -- Color assets, icon sets, dark mode variants
+6. **Accessibility audit** -- Grep for accessibility modifiers/attributes
+
+Present findings and ask the user to confirm or correct. Then gather anything still missing:
+
+### 1. Product Overview
+- What does the app do? (one sentence)
+- Category (productivity, social, health, game, utility, etc.)
+- Stage (concept, development, shipped, redesign)
+
+### 2. Target Platforms
+- Which Apple platforms? (iOS, iPadOS, macOS, tvOS, watchOS, visionOS)
+- Minimum OS versions
+- Universal or platform-specific?
+
+### 3. Technology Stack
+- UI framework: SwiftUI, UIKit, AppKit, or mixed?
+- Architecture: single-window, multi-window, document-based?
+- Apple technologies in use? (HealthKit, CloudKit, ARKit, etc.)
+
+### 4. Design System
+- System defaults or custom design system?
+- Brand colors, fonts, icon style?
+- Dark mode and Dynamic Type support status
+
+### 5. Accessibility Requirements
+- Target level (baseline, enhanced, comprehensive)
+- Specific considerations (VoiceOver, Switch Control, etc.)
+- Regulatory requirements (WCAG, Section 508)
+
+### 6. User Context
+- Primary personas (1-3)
+- Key use cases and environments (desk, on-the-go, glanceable, immersive)
+- Known pain points or design challenges
+
+### 7. Existing Design Assets
+- Figma/Sketch files?
+- Apple Design Resources in use?
+- Existing component library?
+
+## Context Document Template
+
+Generate `.claude/apple-design-context.md` using this structure:
+
+```markdown
+# Apple Design Context
+
+## Product
+- **Name**: [App name]
+- **Description**: [One sentence]
+- **Category**: [Category]
+- **Stage**: [Concept / Development / Shipped / Redesign]
+
+## Platforms
+| Platform | Supported | Min OS | Notes |
+|----------|-----------|--------|-------|
+| iOS | Yes/No | | |
+| iPadOS | Yes/No | | |
+| macOS | Yes/No | | |
+| tvOS | Yes/No | | |
+| watchOS | Yes/No | | |
+| visionOS | Yes/No | | |
+
+## Technology
+- **UI Framework**: [SwiftUI / UIKit / AppKit / Mixed]
+- **Architecture**: [Single-window / Multi-window / Document-based]
+- **Apple Technologies**: [List any: HealthKit, CloudKit, ARKit, etc.]
+
+## Design System
+- **Base**: [System defaults / Custom design system]
+- **Brand Colors**: [List or reference]
+- **Typography**: [System fonts / Custom fonts]
+- **Dark Mode**: [Supported / Not yet / N/A]
+- **Dynamic Type**: [Supported / Not yet / N/A]
+
+## Accessibility
+- **Target Level**: [Baseline / Enhanced / Comprehensive]
+- **Key Considerations**: [List any specific needs]
+
+## Users
+- **Primary Persona**: [Description]
+- **Key Use Cases**: [List]
+- **Known Challenges**: [List]
+```
+
+## Updating Context
+
+When updating an existing context document:
+
+1. Read the current `.claude/apple-design-context.md`
+2. Ask what has changed
+3. Update only the changed sections
+4. Preserve all unchanged information
+
+## Related Skills
+
+- **hig-platforms** -- Platform-specific guidance
+- **hig-foundations** -- Color, typography, layout decisions
+- **hig-patterns** -- UX pattern recommendations
+- **hig-components-*** -- Component recommendations
+- **hig-inputs** -- Input method coverage
+- **hig-technologies** -- Apple technology relevance
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-technologies/SKILL.md b/web-app/public/skills/hig-technologies/SKILL.md
new file mode 100644
index 00000000..abb66f63
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/SKILL.md
@@ -0,0 +1,136 @@
+---
+name: hig-technologies
+version: 1.0.0
+description: ">"
+ Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit,
+ HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple,
+ SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps,
+ Mac Catalyst, and more. Use when asked about: "Siri integration", "Apple Pay",
+ "HealthKit", "HomeKit", "ARKit", "augmented reality", "machine learning",
+ "generative AI", "iCloud sync", "Sign in with Apple", "SharePlay", "CarPlay",
+ "in-app purchase", "NFC", "VoiceOver", "Maps", "Mac Catalyst". Also use when
+ the user says "how do I integrate Siri," "what are the Apple Pay guidelines,"
+ "how should my AR experience work," "how do I use Sign in with Apple," or asks
+ about any Apple framework or service integration.
+ Cross-references: hig-inputs for input methods, hig-components-system for widgets.
+risk: unknown
+source: community
+---
+
+# Apple HIG: Technologies
+
+Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+
+## Key Principles
+
+### General
+
+1. **Apple technologies extend app capabilities through system integration.** Each technology has established user-facing patterns; deviating creates confusion and erodes trust.
+
+2. **Privacy and user control are paramount.** Especially for health, payment, and identity technologies. Request only needed data, explain why, respect choices.
+
+### Siri and Voice
+
+3. **Natural, predictable, recoverable.** Clear conversational intent phrases that complete quickly and confirm results. Support App Shortcuts for proactive suggestions. Handle errors with clear fallbacks.
+
+### Payments and Commerce
+
+4. **Transparent and frictionless.** Standard Apple Pay button styles. Never ask for card details when Apple Pay is available. Clearly describe what the user is buying, the price, and whether it's one-time or subscription.
+
+### Health and Fitness
+
+5. **Health data is deeply personal.** Explain the health benefit before requesting access. CareKit tasks should be encouraging. ResearchKit consent flows must be thorough, readable, and respect autonomy.
+
+### Smart Home
+
+6. **Simple and reliable.** Immediate response when controlling devices. Clear device state. Graceful handling of connectivity issues.
+
+### Augmented Reality
+
+7. **Genuine value, not gimmicks.** Use AR when spatial context improves understanding. Guide setup (surface, lighting, space). Provide clear exit back to standard interaction.
+
+### Machine Learning and Generative AI
+
+8. **Enhance without surprising.** Smart suggestions, image recognition, text prediction. Clearly attribute AI-generated content. Controls to edit, regenerate, or dismiss. Let users correct mistakes.
+
+### Identity and Authentication
+
+9. **Sign in with Apple as top option.** Standard button styles. Respect email hiding preference. ID Verifier: guided flows, don't store sensitive data beyond what verification requires.
+
+### Cloud and Data
+
+10. **Invisible and reliable sync.** Data appears on all devices without manual intervention. Handle conflicts gracefully. Never lose data.
+
+### Shared Experiences
+
+11. **Real-time participation.** SharePlay: support multiple participants, show presence, handle latency. AirPlay: appropriate Now Playing metadata.
+
+### Automotive
+
+12. **Driver safety first.** Minimize interaction complexity, large touch targets, no distracting content. Only permitted app types: audio, messaging, EV charging, navigation, parking, quick food ordering.
+
+### Accessibility
+
+13. **Baseline requirement.** Every element has a meaningful VoiceOver label, trait, and action. Support Dynamic Type, Switch Control, and other assistive technologies. Test entirely with VoiceOver enabled.
+
+## Reference Index
+
+| Reference | Topic | Key content |
+|---|---|---|
+| [siri.md](references/siri.md) | Siri | Intents, shortcuts, voice interaction, App Shortcuts |
+| [apple-pay.md](references/apple-pay.md) | Apple Pay | Payment buttons, checkout flow, security |
+| [tap-to-pay-on-iphone.md](references/tap-to-pay-on-iphone.md) | Tap to Pay | Merchant flows, contactless payment |
+| [in-app-purchase.md](references/in-app-purchase.md) | In-app purchase | Subscriptions, one-time purchases, transparency |
+| [healthkit.md](references/healthkit.md) | HealthKit | Health data access, privacy, permissions |
+| [carekit.md](references/carekit.md) | CareKit | Care plans, tasks, health management |
+| [researchkit.md](references/researchkit.md) | ResearchKit | Studies, informed consent, data collection |
+| [homekit.md](references/homekit.md) | HomeKit | Smart home control, device state, scenes |
+| [augmented-reality.md](references/augmented-reality.md) | ARKit | Spatial context, surface detection, setup |
+| [machine-learning.md](references/machine-learning.md) | Core ML | Predictions, smart features, confidence handling |
+| [generative-ai.md](references/generative-ai.md) | Generative AI | Attribution, editing, responsible AI, uncertainty |
+| [icloud.md](references/icloud.md) | iCloud | CloudKit, cross-device sync, conflict resolution |
+| [sign-in-with-apple.md](references/sign-in-with-apple.md) | Sign in with Apple | Authentication, privacy, button styles |
+| [id-verifier.md](references/id-verifier.md) | ID Verifier | Identity verification, document scanning |
+| [shareplay.md](references/shareplay.md) | SharePlay | Shared experiences, participant presence |
+| [airplay.md](references/airplay.md) | AirPlay | Media streaming, Now Playing, wireless display |
+| [carplay.md](references/carplay.md) | CarPlay | Driver safety, permitted app types, large targets |
+| [game-center.md](references/game-center.md) | Game Center | Achievements, leaderboards, multiplayer |
+| [voiceover.md](references/voiceover.md) | VoiceOver | Screen reader, labels, traits, accessibility |
+| [wallet.md](references/wallet.md) | Wallet | Passes, tickets, loyalty cards |
+| [nfc.md](references/nfc.md) | NFC | Tag reading, quick interactions, App Clips |
+| [maps.md](references/maps.md) | Maps | Location display, annotations, directions |
+| [mac-catalyst.md](references/mac-catalyst.md) | Mac Catalyst | iPad to Mac, menu bar, keyboard, pointer |
+| [live-photos.md](references/live-photos.md) | Live Photos | Motion capture, playback, editing |
+| [imessage-apps-and-stickers.md](references/imessage-apps-and-stickers.md) | iMessage apps | Messages extension, stickers, compact UI |
+| [shazamkit.md](references/shazamkit.md) | ShazamKit | Audio recognition, music identification |
+| [always-on.md](references/always-on.md) | Always-on display | Dimmed state, power efficiency, reduced updates |
+| [photo-editing.md](references/photo-editing.md) | Photo editing | System photo editor, filters, adjustments |
+
+## Output Format
+
+1. **Implementation checklist** -- step-by-step requirements per Apple's guidelines.
+2. **Required vs optional features** for approval.
+3. **Privacy and permission requirements** -- data access, usage descriptions.
+4. **User-facing flow** from permission prompt through task completion.
+5. **Testing guidance** -- key scenarios including edge cases.
+
+## Questions to Ask
+
+1. Which Apple technology?
+2. Core use case?
+3. Which platforms?
+4. API requirements and entitlements reviewed?
+5. What data or permissions needed?
+
+## Related Skills
+
+- **hig-inputs** -- Input methods interacting with technologies (voice for Siri, Pencil for AR, gestures for Maps)
+- **hig-components-system** -- Widgets, complications, Live Activities surfacing technology data
+- **hig-components-status** -- Progress indicators for technology operations (sync, payment, AR loading)
+
+---
+
+*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hig-technologies/references/airplay.md b/web-app/public/skills/hig-technologies/references/airplay.md
new file mode 100644
index 00000000..dd02b0f1
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/airplay.md
@@ -0,0 +1,125 @@
+---
+title: "AirPlay | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/airplay
+
+# AirPlay
+
+AirPlay lets people stream media content wirelessly from iOS, iPadOS, macOS, and tvOS devices to Apple TV, HomePod, and TVs and speakers that support AirPlay.
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/airplay#Best-practices)
+
+**Prefer the system-provided media player.** The built-in media player offers a standard set of controls and supports features like chapter navigation, subtitles, closed captioning, and AirPlay streaming. It’s also easy to implement, provides a consistent and familiar playback experience across the system, and accommodates the needs of most media apps. Consider designing a custom video player only if the system-provided player doesn’t meet your app’s needs. For developer guidance, see [`AVPlayerViewController`](https://developer.apple.com/documentation/AVKit/AVPlayerViewController).
+
+
+
+**Provide content in the highest possible resolution.** Your [HTTP Live Streaming](https://developer.apple.com/documentation/http-live-streaming) (HLS) playlist needs to include the full range of available resolutions so that people can experience your content in the resolution that’s appropriate for the device they’re using (AVFoundation automatically selects the resolution based on the device). If you don’t include a range of resolutions, your content looks low quality when people stream it to a device that can play at higher resolutions. For example, content that looks great on iPhone at 720p will look low quality when people use AirPlay to stream it to a 4K TV.
+
+**Stream only the content people expect.** Avoid streaming content like background loops and short video experiences that make sense only within the context of the app itself. For developer guidance, see [`usesExternalPlaybackWhileExternalScreenIsActive`](https://developer.apple.com/documentation/AVFoundation/AVPlayer/usesExternalPlaybackWhileExternalScreenIsActive).
+
+**Support both AirPlay streaming and mirroring.** Supporting both features gives people the most flexibility.
+
+**Support remote control events.** When you do, people can choose actions like play, pause, and fast forward on the lock screen, and through interaction with Siri or HomePod. For developer guidance, see [Remote command center events](https://developer.apple.com/documentation/MediaPlayer/remote-command-center-events).
+
+**Don’t stop playback when your app enters the background or when the device locks.** For example, people expect the TV show they started streaming from your app to continue while they check their mail or put their device to sleep. In this type of scenario, it’s also crucial to avoid automatic mirroring because people don’t want to stream other content on their device without explicitly choosing to do so.
+
+**Don’t interrupt another app’s playback unless your app is starting to play immersive content.** For example, if your app plays a video when it launches or auto-plays inline videos, play this content on only the local device, while allowing current playback to continue. For developer guidance, see [`ambient`](https://developer.apple.com/documentation/AVFAudio/AVAudioSession/Category-swift.struct/ambient).
+
+**Let people use other parts of your app during playback.** When AirPlay is active, your app needs to remain functional. If people navigate away from the playback screen, make sure other in-app videos don’t begin playing and interrupt the streaming content.
+
+**If necessary, provide a custom interface for controlling media playback.** If you can’t use the system-provided media player, you can create a custom media player that gives people an intuitive way to enter AirPlay. If you need to do this, be sure to provide custom buttons that match the appearance and behavior of the system-provided ones, including distinct visual states that indicate when playback starts, is occurring, or is unavailable. Use only Apple-provided symbols in custom controls that initiate AirPlay, and position the AirPlay icon correctly in your custom player — that is, in the lower-right corner (in iOS 16 and iPadOS 16 and later).
+
+## [Using AirPlay icons](https://developer.apple.com/design/human-interface-guidelines/airplay#Using-AirPlay-icons)
+
+You can download AirPlay icons in [Resources](https://developer.apple.com/design/resources/). You have the following options for displaying the AirPlay icon in your app.
+
+### [Black AirPlay icon](https://developer.apple.com/design/human-interface-guidelines/airplay#Black-AirPlay-icon)
+
+Use the black AirPlay icon on white or light backgrounds when other technology icons also appear in black.
+
+
+
+### [White AirPlay icon](https://developer.apple.com/design/human-interface-guidelines/airplay#White-AirPlay-icon)
+
+Use the white AirPlay icon on black or dark backgrounds when other technology icons also appear in white.
+
+
+
+### [Custom color AirPlay icon](https://developer.apple.com/design/human-interface-guidelines/airplay#Custom-color-AirPlay-icon)
+
+Use a custom color when other technology icons also appear in the same color.
+
+
+
+**Position the AirPlay icon consistently with other technology icons.** If you display other technology icons within shapes, you can display the AirPlay icon in the same manner.
+
+**Don’t use the AirPlay icon or name in custom buttons or interactive elements.** Use the icon and the name _AirPlay_ only in noninteractive ways.
+
+**Pair the icon with the name _AirPlay_ correctly.** You can show the name below or beside the icon if you also reference other technologies in this way. Use the same font you use in the rest of your layout. Avoid using the AirPlay icon within text or as a replacement for the name _AirPlay_.
+
+**Emphasize your app over AirPlay.** Make references to AirPlay less prominent than your app name or main identity.
+
+## [Referring to AirPlay](https://developer.apple.com/design/human-interface-guidelines/airplay#Referring-to-AirPlay)
+
+**Use correct capitalization when using the term _AirPlay_.** _AirPlay_ is one word, with an uppercase _A_ and uppercase _P_ , each followed by lowercase letters. If your layout displays only all-uppercase designations, you can typeset _AirPlay_ in all uppercase to match the style of the rest of the layout.
+
+**Always use _AirPlay_ as a noun.**
+
+| Example text
+---|---
+| Use AirPlay to listen on your speaker
+| AirPlay to your speaker
+| You can AirPlay with [App Name]
+
+**Use terms like _works with_ , _use_ , _supports_ , and _compatible_.**
+
+| Example text
+---|---
+| [App Name] is compatible with AirPlay
+| AirPlay-enabled speaker
+| You can use AirPlay with [App Name]
+| [App Name] has AirPlay
+
+**Use the name _Apple_ with the name _AirPlay_ if desired.**
+
+| Example text
+---|---
+| Compatible with Apple AirPlay
+
+**Refer to AirPlay if appropriate and to add clarity.** If your content is specific to AirPlay, you can use Airplay to make that clear. You can also refer to AirPlay in technical specifications.
+
+| Example text
+---|---
+| [App Name] now supports AirPlay
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/airplay#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS. Not supported in watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/airplay#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/airplay#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+[Apple Trademark List](https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html)
+
+[Guidelines for Using Apple Trademarks and Copyrights](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/airplay#Developer-documentation)
+
+[AVFoundation](https://developer.apple.com/documentation/AVFoundation)
+
+[AVKit](https://developer.apple.com/documentation/AVKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/airplay#Videos)
+
+[ Reaching the Big Screen with AirPlay 2 ](https://developer.apple.com/videos/play/wwdc2019/501)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/airplay#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/always-on.md b/web-app/public/skills/hig-technologies/references/always-on.md
new file mode 100644
index 00000000..b24ca652
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/always-on.md
@@ -0,0 +1,62 @@
+---
+title: "Always On | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/always-on
+
+# Always On
+
+On devices that include the Always On display, the system can continue to display an app’s interface when people suspend their interactions with the device.
+
+
+
+In the Always On state, a device can continue to give people useful, glanceable information in a low-power, privacy-preserving way by dimming the display and minimizing onscreen motion. The system can display different items depending on the device.
+
+ * On iPhone 14 Pro and iPhone 14 Pro Max, the system displays Lock Screen items like [Widgets](https://developer.apple.com/design/human-interface-guidelines/widgets) and [Live Activities](https://developer.apple.com/design/human-interface-guidelines/live-activities) when people set aside their device face up and stop interacting with it.
+
+ * When people drop their wrist while wearing Apple Watch, the system dims the watch face, continuing to display the interface of the app as long as it’s either frontmost or running a background session.
+
+
+
+
+On both devices, the system displays notifications while in Always On, and people can tap the display to exit Always On and resume interactions.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/always-on#Best-practices)
+
+**Hide sensitive information.** It’s crucial to redact personal information that people wouldn’t want casual observers to view, like bank balances or health data. You also need to hide personal information that might be visible in a notification; for guidance, see [Notifications](https://developer.apple.com/design/human-interface-guidelines/notifications).
+
+**Keep other types of personal information glanceable when it makes sense.** On Apple Watch, for example, people typically appreciate getting pace and heart rate updates while they’re working out; on iPhone, people appreciate getting a glanceable update on a flight arrival or a notification when a ride-sharing service arrives. If people don’t want any information to be visible, they can turn off Always On.
+
+**Keep important content legible and dim nonessential content.** You can increase dimming on secondary text, images, and color fills to give more prominence to the information that’s important to people. For example, a to-do list app might remove row backgrounds and dim each item’s additional details to highlight its title. Also, if you display rich images or large areas of color, consider removing the images and using dimmed colors.
+
+**Maintain a consistent layout.** Avoid making distracting interface changes when Always On begins or ends and throughout the Always On experience. For example, when Always On begins, prefer transitioning an interactive component to an unavailable appearance — don’t just remove it. Within the Always On context, aim to make infrequent, subtle updates to the interface. For example, a sports app might pause granular play-by-play updates while in Always On, only updating the score when it changes. Note that unnecessary changes during Always On can be especially distracting on iPhone, because people often put their device face up on a surface, making motion on the screen visible even when they’re not looking directly at it.
+
+**Gracefully transition motion to a resting state; don’t stop it instantly.** Smoothly finishing the current motion helps communicate the transition and avoids making people think that something went wrong.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/always-on#Platform-considerations)
+
+ _No additional considerations for iOS or watchOS. Not supported in iPadOS, macOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/always-on#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/always-on#Related)
+
+[Designing for watchOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-watchos)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/always-on#Developer-documentation)
+
+[Designing your app for the Always On state](https://developer.apple.com/documentation/watchOS-Apps/designing-your-app-for-the-always-on-state) — watchOS apps
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/always-on#Videos)
+
+[ What's new in watchOS 8 ](https://developer.apple.com/videos/play/wwdc2021/10002)
+
+[ Build a workout app for Apple Watch ](https://developer.apple.com/videos/play/wwdc2021/10009)
+
+[ What's new in SwiftUI ](https://developer.apple.com/videos/play/wwdc2021/10018)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/always-on#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Updated intro image artwork.
+September 23, 2022| Expanded guidance to cover the Always On display on iPhone 14 Pro and iPhone 14 Pro Max.
+
diff --git a/web-app/public/skills/hig-technologies/references/apple-pay.md b/web-app/public/skills/hig-technologies/references/apple-pay.md
new file mode 100644
index 00000000..a5ea65ec
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/apple-pay.md
@@ -0,0 +1,441 @@
+---
+title: "Apple Pay | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/apple-pay
+
+# Apple Pay
+
+Apple Pay is a secure, easy way to make payments for physical goods and services — as well as donations and subscriptions — in apps running on iPhone, iPad, Mac, Apple Vision Pro, Apple Watch, on websites, and on any browser.
+
+
+
+People authorize payments and provide shipping and contact information, using credentials that are securely stored on the device.
+
+Tip
+
+It’s important to understand the difference between Apple Pay and [In-app purchase](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase). Use Apple Pay in your app to sell physical goods like groceries, clothing, and appliances; for services such as club memberships, hotel reservations, and tickets for events; and for donations. Use In-App Purchase in your app to sell virtual goods, such as premium content for your app, and subscriptions for digital content.
+
+Apps and websites that accept Apple Pay display it as an available payment option, and include an Apple Pay button in the purchasing flow that people tap to bring up a payment sheet. During checkout, the payment sheet can show the credit or debit card linked to Apple Pay, purchase amount (including tax and fees), shipping options, and contact information. People make any necessary adjustments and then authorize payment and complete the purchase. For developer guidance, see [Apple Pay](https://developer.apple.com/documentation/PassKit/apple-pay).
+
+All websites that offer Apple Pay must include a privacy statement and adhere to the [Acceptable use guidelines for Apple Pay on the web](https://developer.apple.com/apple-pay/acceptable-use-guidelines-for-websites/). For developer guidance, see [Apple Pay on the Web](https://developer.apple.com/documentation/ApplePayontheWeb). For a hands-on demo of Apple Pay on the web, see [Apple Pay on the web interactive demo](https://applepaydemo.apple.com).
+
+
+
+The device performs payment authentication in most cases where the device supports Face ID, Touch ID, or Optic ID. In some cases, the system transfers payment authentication to a nearby iPhone, iPad, or Apple Watch via a secure Bluetooth connection or a scannable code.
+
+
+
+## [Offering Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Offering-Apple-Pay)
+
+**Offer Apple Pay on all devices and browsers that support it.** If the device doesn’t support Apple Pay, don’t present Apple Pay as a payment option. Use Apple Pay APIs to evaluate when a device can support Apple Pay. For developer guidance, see [`PKPaymentAuthorizationController`](https://developer.apple.com/documentation/PassKit/PKPaymentAuthorizationController) (iOS, watchOS) and [`canMakePayments`](https://developer.apple.com/documentation/ApplePayontheWeb/ApplePaySession/canMakePayments) (web).
+
+**If you use Apple Pay APIs to find out whether someone has an active card in Wallet, you must make Apple Pay the primary — but not necessarily sole — payment option everywhere you use the APIs.** For example, you might pre-select Apple Pay as the payment option when you display it alongside other options. For developer guidance, see [Offering Apple Pay in Your App](https://developer.apple.com/documentation/PassKit/offering-apple-pay-in-your-app) (iOS, watchOS) and [Checking for Apple Pay availability](https://developer.apple.com/documentation/ApplePayontheWeb/checking-for-apple-pay-availability) (web).
+
+**If you also offer other payment methods, offer Apple Pay at the same time.** Feature Apple Pay at least as prominently as the other options on every page or screen that offers or accepts payment methods.
+
+**If you use an Apple Pay button to start the Apple Pay payment process, you must use the Apple-provided API to display it.** Unlike a button graphic, the buttons produced by the API always have the correct appearance and are localized automatically.
+
+**If you use a custom button to start the Apple Pay payment process, make sure your custom button doesn’t display “Apple Pay” or the Apple Pay logo.** In this scenario, you must let people know that you accept Apple Pay by displaying the Apple Pay mark or referencing Apple Pay in text on the same page that displays your payment button.
+
+
+
+
+
+
+
+
+
+**Use Apple Pay buttons only to start the Apple Pay payment process and, when appropriate, the Apple Pay set-up process.** When people choose an Apple Pay button to make a purchase, but their device doesn’t have Apple Pay set up, they’re given the opportunity to set up Apple Pay. Don’t use Apple Pay buttons in any other ways.
+
+**Don’t hide an Apple Pay button or make it appear unavailable.** If an Apple Pay button can’t be used yet, such as when a product size or color hasn’t been selected, gracefully point out the problem after someone taps or clicks the button.
+
+**Use the Apple Pay mark only to communicate that Apple Pay is accepted.** The Apple Pay mark doesn’t facilitate payment. Never use it as a payment button or position it as a button. When using the Apple Pay mark to indicate Apple Pay as the selected payment method, you can create a separate custom button conforming to your app’s design to initiate the Apple Pay payment.
+
+**Inform search engines that Apple Pay is accepted on your website.** If your website uses semantic markup to provide product details to search engines, list Apple Pay as a payment option.
+
+For app developer guidance, see [Apple Pay](https://developer.apple.com/documentation/PassKit/apple-pay). For website developer guidance, including how to determine whether Apple Pay on the web is available, see [Apple Pay on the Web](https://developer.apple.com/documentation/ApplePayontheWeb).
+
+## [Streamlining checkout](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Streamlining-checkout)
+
+**Provide a cohesive checkout experience.** It’s best when the entire checkout flow feels tightly integrated with your app or website. To strengthen people’s perception of integration, use your branding throughout the checkout experience and avoid opening different pages or windows. For website checkout flows in particular, opening new windows during the process can cause confusion and may even lead people to think they’ve been handed off to a different website.
+
+**If Apple Pay is available, assume the person wants to use it.** Consider presenting the Apple Pay button as the first payment option, displaying it larger than other options, or using a line to visually separate it from other choices.
+
+**Accelerate single-item purchases with Apple Pay buttons on product detail pages.** In addition to offering a shopping cart, consider putting Apple Pay buttons on product detail pages so people can purchase an individual item quickly. Purchases initiated in this way need to be for an individual item only, excluding any items that already reside in the shopping cart. If the shopping cart contains an item purchased directly from a product detail page, remove the item from the cart after the purchase is complete.
+
+**Accelerate multi-item purchases with express checkout.** Consider providing an express checkout feature that immediately displays the payment sheet, allowing people to purchase multiple items quickly using a single shipping method and destination. If you offer a coupon or promotional code, you can enhance the express checkout experience by letting people enter it on the payment sheet.
+
+**Collect necessary information, like color and size options, before people reach the Apple Pay button.** When additional information is needed at checkout time — perhaps because the customer forgot to choose an option — gracefully point out the problem and help them correct it. Use highlighting or warning text to identify missing information, and automatically navigate to the problematic field so people can correct it quickly and complete their purchase.
+
+**Collect optional information before checkout begins.** There’s no way to input optional data — like gift messages or delivery instructions — on the payment sheet, so collect this information ahead of time or even after the purchase is complete.
+
+**Gather multiple shipping methods and destinations before showing the payment sheet.** The payment sheet lets people select a single shipping method and destination for an entire order. If your customers can choose different shipping methods and destinations for individual items in an order, collect those details before Apple Pay checkout begins, instead of on the payment sheet.
+
+**For in-store pickup, help people choose a pickup location before displaying the payment sheet.** After a customer chooses the pickup location they want, use the read-only format to display the location’s address on the payment sheet. For developer guidance, see [Displaying a Read-Only Pickup Address](https://developer.apple.com/documentation/PassKit/displaying-a-read-only-pickup-address).
+
+**Prefer information from Apple Pay.** Assume that Apple Pay information is complete and up to date. Even if your app or website has existing contact, shipping, and payment information, consider fetching the latest from Apple Pay during checkout to reduce potential corrections.
+
+**Avoid requiring account creation prior to purchase.** If you want people to register for an account, ask them to do so on the order confirmation page. Prepopulate as many registration fields as possible using information provided by the payment sheet during checkout.
+
+
+
+**Report the result of the transaction so that people can view it in the payment sheet.** In failure cases, the payment sheet can display the errors that you provide, so people can take steps to fix the problem.
+
+**Display an order confirmation or thank-you page.** After the payment sheet shows the result of the transaction, display an order confirmation page to thank people for their purchase, provide details about when the order will ship, and indicate how to check its status. Listing Apple Pay on the confirmation page isn’t necessary, but if you do, show it after the last four digits of the account used to process the transaction or as a separate note. For example, ”1234 (Apple Pay)” or ”Paid with Apple Pay.”
+
+### [Customizing the payment sheet](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Customizing-the-payment-sheet)
+
+**Only present and request essential information.** People may get confused or have privacy concerns if the payment sheet includes extraneous information. For example, it makes sense to see a contact email address but not a shipping address if the purchase is a gift card that will be delivered electronically. Showing or asking for a shipping address in this scenario may give the false impression that something will be physically delivered.
+
+**Display the active coupon or promotional code, or give people a way to enter it.** For example, if people can enter a code before the payment sheet appears, displaying it on the sheet can reassure them that the code works as they expect. Alternatively, allowing code entry on the payment sheet can be particularly beneficial in an express checkout flow.
+
+**Let people choose the shipping method in the payment sheet.** To the extent space permits, show a clear description, a cost, and, optionally, an estimated delivery or pickup date — or range of dates — for each available option. In iOS 15 and later, you can take advantage of the shipping method’s calendar and time-zone support to provide accurate delivery or pickup information, regardless of the customer’s current location. For developer guidance, see [`PKDateComponentsRange`](https://developer.apple.com/documentation/PassKit/PKDateComponentsRange).
+
+**For in-store pickup, consider letting people choose a pickup window that works for them.** You can use the shipping method to supply a range of dates and times from which people can choose.
+
+**Use line items to explain additional charges, discounts, pending costs, add-on donations, recurring, and future payments.** A line item includes a label and cost; a line item for a recurring payment can also include a frequency. Don’t use line items to show an itemized list of products that make up the purchase. For developer guidance, see [`paymentSummaryItems`](https://developer.apple.com/documentation/PassKit/PKPaymentRequest/paymentSummaryItems); for guidance on donations, see [Supporting donations](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Supporting-donations).
+
+ * iOS
+ * Web
+
+
+
+
+
+
+
+**Keep line items short.** Make line items specific and easily understandable at a glance. Whenever possible, fit line items on a single line.
+
+**Provide a business name after the word _Pay_ on the same line as the total.** Use the same business name people will see when they look for the charge on their bank or credit card statement. This provides reassurance that payment is going to the right place. For example, Pay [_Business_Name_].
+
+**If you’re not the end merchant, specify both your business name and the end merchant’s name in the payment sheet.** There are a few ways your app, App Clip, or website might help people make a purchase from an end merchant that’s unrelated to your company. For example, a marketplace app can help people make a purchase from an end merchant they might not recognize. Another example is an app that offers a self-checkout service people can use to pay for an item in an end merchant’s physical store without visiting the store’s checkout counter. In scenarios like these, people might not realize two businesses are involved in the transaction, so it’s essential to name both businesses and clarify their roles. When your app acts as an intermediary for an end merchant, clearly and succinctly describe the situation in the Pay line of the payment sheet, using something like Pay [_End_Merchant_Business_Name_ (via _Your_Business_Name_)].
+
+**Clearly disclose when additional costs may be incurred after payment authorization.** In some cases, the total cost may be unknown at checkout time. For example, the price of a car ride based on distance or time might change after checkout. Or, a customer might want to add a tip after a product is delivered. In situations like these, and when local regulations allow, you can provide a clear explanation in the payment sheet and a subtotal marked as Amount Pending. If you’re preauthorizing a specific amount, be sure the payment sheet accurately reflects this information.
+
+**Handle data entry and payment errors gracefully.** If an error occurs during checkout, help people resolve it quickly so they can complete their transaction. For related guidance, see [Data validation](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Data-validation).
+
+### [Displaying a website icon](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Displaying-a-website-icon)
+
+Many websites provide an icon that can display with bookmarks, in URL fields, or on a device’s Home screen. Websites that support Apple Pay can display this icon in a summary view and in the payment sheet of the connected device that’s used to authorize payment. The icon provides visual reassurance that payment is going to the right place.
+
+If your website supports Apple Pay, provide an icon in the following sizes for use in the summary view and the payment sheet:
+
+@2x| @3x
+---|---
+60x60 pt (120x120 px @2x)| 60x60 pt (180x180 px @3x)
+
+
+
+## [Handling errors](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Handling-errors)
+
+Provide clear, actionable guidance when problems occur during checkout or payment processing, so people can resolve problems quickly and complete their transaction.
+
+### [Data validation](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Data-validation)
+
+Your app or website can respond to user input when the payment sheet appears, when people change certain field values on the payment sheet, and after they authenticate the transaction. Use these opportunities to check for data entry problems and to provide clear and consistent messaging.
+
+ * iOS
+ * Web
+
+
+
+
+
+Payment sheet error messaging
+
+
+
+Custom detail view error messaging
+
+Payment sheet error messaging
+
+Custom detail view error messaging
+
+When data is invalid, system-provided error messaging calls attention to relevant fields on the payment sheet. People can choose a field to view additional details and resolve the problem. Provide customized error messages for the detail view that appears when people choose a problematic field.
+
+For developer guidance, see [`PKPaymentAuthorizationViewControllerDelegate`](https://developer.apple.com/documentation/PassKit/PKPaymentAuthorizationViewControllerDelegate) (iOS, watchOS) and [Apple Pay on the Web](https://developer.apple.com/documentation/ApplePayontheWeb) (web).
+
+Note
+
+For privacy reasons, your app or website has limited access to data until people attempt to authorize a transaction. Prior to authorization, only the card type and a redacted shipping address are accessible. It’s critical to display errors when authorization fails, but to the extent possible, you also need to attempt to validate available information and report problems before authorization.
+
+**Avoid forcing compliance with your business logic.** Design a data validation process that’s intelligent enough to ignore irrelevant data and infer missing data whenever possible. For example, if your app requires a five-digit zip code but someone enters a Zip+4 code, ignore the additional digits rather than asking for a correction. Let people enter phone numbers in multiple formats — such as with and without dashes, and with and without a country code — without producing an error.
+
+**Provide accurate status reporting to the system.** When a problem occurs, it’s essential that your app or website accurately indicate the type of problem so the system can show the most relevant error message on the payment sheet. This is done by accompanying your custom error message with the correct status code. For developer guidance, see [`PKPaymentError`](https://developer.apple.com/documentation/PassKit/PKPaymentError) (iOS, watchOS) and [Apple Pay Status Codes](https://developer.apple.com/documentation/ApplePayontheWeb/apple-pay-status-codes) (web).
+
+**Succinctly and specifically describe the problem when data is invalid or incorrectly formatted.** Reference the relevant field and indicate exactly what’s expected. For example, if people enter an invalid zip code, instead of showing “Address is invalid,” show a specific message like “Zip code doesn’t match city.” If the shipping address is unserviceable, indicate why with a message like “Shipping not available for this state.” Use noun phrases with sentence-style capitalization and no ending punctuation. Aim to keep messages at 128 characters or fewer to avoid truncation.
+
+### [Payment processing](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Payment-processing)
+
+**Handle interruptions correctly.** A user-driven event like a cancellation or a system-driven event like a timeout could cause an interruption in the payment flow, resulting in the payment sheet being dismissed. When such an event occurs, you must cancel any in-progress payment. After the payment sheet dismisses, people can restart the process by choosing the Apple Pay button again. For developer guidance, see [`PKPaymentAuthorizationViewControllerDelegate`](https://developer.apple.com/documentation/PassKit/PKPaymentAuthorizationViewControllerDelegate) (iOS, watchOS) and [`oncancel`](https://developer.apple.com/documentation/ApplePayontheWeb/ApplePaySession/oncancel) (web).
+
+## [Supporting subscriptions](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Supporting-subscriptions)
+
+Your app or website can use Apple Pay to request authorization for recurring fees. A recurring fee can be a fixed amount, such as a monthly movie ticket subscription, or — when local regulations allow — a variable amount like a weekly grocery order. The initial authorization can also include discounts and additional fees.
+
+ * iOS
+ * Web
+
+
+
+
+
+Fixed subscription
+
+
+
+Variable subscription (where local regulations allow)
+
+Fixed subscription
+
+Variable subscription (where local regulations allow)
+
+**Clarify subscription details before showing the payment sheet.** Before asking people to authorize a recurring payment, make sure they fully understand the billing frequency and any other terms of service. You can reiterate the billing frequency on the payment sheet.
+
+**Include line items that reiterate billing frequency, discounts, and additional upfront fees.** Use these line items to remind people what they’re authorizing. If no payment is required at authorization time, clearly disclose when billing will occur.
+
+ * iOS
+ * Web
+
+
+
+
+
+No payment required at authorization
+
+No payment required at authorization
+
+**Clarify the current payment amount in the total line.** Make sure people know the amount they’re being billed at the time of authorization.
+
+**Only show the payment sheet when a subscription change results in additional fees.** When the someone changes a subscription, authorization isn’t necessary if the cost decreases or remains the same.
+
+### [Supporting donations](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Supporting-donations)
+
+[Approved nonprofits](https://developer.apple.com/support/apple-pay-nonprofits/) can use Apple Pay to accept donations.
+
+**Use a line item to denote a donation.** Display a line item on the payment sheet that reminds people they’re authorizing a donation; for example, display Donation $50.00.
+
+**Streamline checkout by offering predefined donation amounts.** You can reduce steps in the donation process by offering one-step recommended donations, like $25, $50, $100. Be sure to include an Other Amount option too, so people can customize the donation if they prefer.
+
+## [Using Apple Pay buttons](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Using-Apple-Pay-buttons)
+
+The system provides several Apple Pay button types and styles you can use in your app or website. In contrast to the Apple Pay buttons, you use the [Apple Pay mark](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Apple-Pay-mark) to communicate the availability of Apple Pay as a payment option.
+
+Don’t create your own Apple Pay button design or attempt to mimic the system-provided button designs.
+
+For developer guidance, see [`PKPaymentButtonType`](https://developer.apple.com/documentation/PassKit/PKPaymentButtonType) and [`PKPaymentButtonStyle`](https://developer.apple.com/documentation/PassKit/PKPaymentButtonStyle) (iOS and macOS), [`WKInterfacePaymentButton`](https://developer.apple.com/documentation/WatchKit/WKInterfacePaymentButton) (watchOS), and [Apple Pay on the Web](https://developer.apple.com/documentation/ApplePayontheWeb) (web).
+
+### [Button types](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Button-types)
+
+Apple provides several types of buttons so you can choose the button type that fits best with the terminology and flow of your purchase or payment experience.
+
+Use the Apple-provided APIs to create Apple Pay buttons. When you use the system-provided APIs, you get:
+
+ * A button that is guaranteed to use an Apple-approved caption, font, color, and style
+
+ * Assurance that the button’s contents maintain ideal proportions as you change its size
+
+ * Automatic translation of the button’s caption into the language that’s set for the device
+
+ * Support for configuring the button’s corner radius to match the style of your UI
+
+ * A system-provided alternative text label that lets VoiceOver describe the button
+
+
+
+
+Payment button type| Example usage
+---|---
+| An area in an app or website where people can make a purchase, such as a product detail page or shopping cart page.
+| An app or website that lets people pay bills or invoices, such as those for a utility — like cable or electricity — or a service like plumbing or car repair.
+| An app or website offering a shopping cart or purchase experience that includes other payment buttons that start with the text _Check out_.
+| An app or website offering a shopping cart or purchase experience that includes other payment buttons that start with the text _Continue with_.
+| An app or website that helps people book flights, trips, or other experiences.
+| An app or website for an [approved nonprofit](https://developer.apple.com/support/apple-pay-nonprofits/) that lets people make donations.
+| An app or website that lets people purchase a subscription, such as a gym membership or a meal-kit delivery service.
+| An app or website that uses the term _reload_ to help people add money to a card, account, or payment system associated with a service, such as transit or a prepaid phone plan.
+| An app or website that uses the term _add money_ to help people add money to a card, account, or payment system associated with a service, such as transit or a prepaid phone plan.
+| An app or website that uses the term _top up_ to help people add money to a card, account, or payment system associated with a service, such as transit or a prepaid phone plan.
+| An app or website that lets people place orders for items like meals or flowers.
+| An app or website that lets people rent items like cars or scooters.
+| An app or website that uses the term _support_ to help people give money to projects, causes, organizations, and other entities.
+| An app or website that uses the term _contribute_ to help people give money to projects, causes, organizations, and other entities.
+| An app or website that lets people tip for goods or services.
+| An app or website that has stylistic reasons to use a button that can have a smaller minimum width or that doesn’t specify a call to action. If you choose a payment button type that isn’t supported on the version of the operating system your app or website is running in, the system may replace it with this button.
+
+When a device supports Apple Pay, but it hasn’t been set up yet, you can use the Set up Apple Pay button to show that Apple Pay is accepted and to give people an explicit opportunity to set it up.
+
+
+
+You can display the Set up Apple Pay button on pages such as a Settings page, a user profile screen, or an interstitial page. Tapping the button in any of these locations needs to initiate the process of adding a card.
+
+### [Button styles](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Button-styles)
+
+You can use the _automatic_ style to let the current system appearance determine the appearance of the Apple Pay buttons in your app (for developer guidance, see [`PKPaymentButtonStyle.automatic`](https://developer.apple.com/documentation/PassKit/PKPaymentButtonStyle/automatic)). If you want to control the button appearance yourself, you can use one of the following options. For web developer guidance, see [`ApplePayButtonStyle`](https://developer.apple.com/documentation/ApplePayontheWeb/ApplePayButtonStyle).
+
+#### [Black](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Black)
+
+Use on white or light-color backgrounds that provide sufficient contrast. Don’t use on black or dark backgrounds.
+
+
+
+
+
+
+
+
+
+#### [White with outline](https://developer.apple.com/design/human-interface-guidelines/apple-pay#White-with-outline)
+
+Use on white or light-color backgrounds that don’t provide sufficient contrast. Don’t place on dark or saturated backgrounds.
+
+
+
+
+
+
+
+
+
+#### [White](https://developer.apple.com/design/human-interface-guidelines/apple-pay#White)
+
+Use on dark-color backgrounds that provide sufficient contrast.
+
+
+
+
+
+
+
+
+
+### [Button size and position](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Button-size-and-position)
+
+**Prominently display the Apple Pay button.** Make the Apple Pay button no smaller than other payment buttons, and avoid making people scroll to see it.
+
+
+
+
+
+
+
+
+
+**Position the Apple Pay button correctly in relation to an Add to Cart button.** In a side-by-side layout, place the Apple Pay button to the right of an Add to Cart button.
+
+
+
+
+
+
+
+
+
+In a stacked layout, place the Apple Pay button above an Add to Cart button.
+
+
+
+
+
+
+
+
+
+**Adjust the corner radius to match the appearance of other buttons.** By default, an Apple Pay button has rounded corners. You can change the corner radius to produce a button with square corners or a capsule-shape button. For developer guidance, see [`cornerRadius`](https://developer.apple.com/documentation/PassKit/PKPaymentButton/cornerRadius).
+
+Minimum corner radius
+
+Default corner radius
+
+Maximum corner radius
+
+**Maintain the minimum button size and margins around the button.** Be mindful that the button title may vary in length depending on the locale.
+
+Note
+
+If the size you specify doesn’t accommodate the translated title for the type of payment button you’re using, the system automatically replaces it with the plain Apple Pay button shown below on the left. There is no automatic replacement for the Set up Apple Pay button.
+
+
+
+
+
+Use the following values for guidance.
+
+Button| Minimum width| Minimum height| Minimum margins
+---|---|---|---
+Apple Pay| 100pt (100px @1x, 200px @2x)| 30pt (30px @1x, 60px @2x)| 1/10 of the button’s height
+Book with Apple Pay| 140pt (140px @1x, 280px @2x)| 30pt (30px @1x, 60px @2x)| 1/10 of the button’s height
+Buy with Apple Pay
+Check out with Apple Pay
+Donate with Apple Pay
+Set up Apple Pay
+Subscribe with Apple Pay
+
+### [Apple Pay mark](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Apple-Pay-mark)
+
+Use the Apple Pay mark graphic to show that Apple Pay is an available payment option when showing other payment options in a similar manner. The Apple Pay mark isn’t a button; if you need an Apple Pay button, choose one of the buttons described in [Button types](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Button-types). For design guidance related to showing Apple Pay as a payment option, see [Offering Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Offering-Apple-Pay).
+
+
+
+**Use only the artwork provided by Apple, with no alterations other than height.** You can specify a height for the Apple Pay mark, but make sure that the height you use is equal to or larger than other payment brand marks in your payment flow. Don’t adjust the width, corner radius, or aspect ratio of the artwork; don’t add a trademark symbol or any other content; don’t remove the border; don’t add visual effects to the mark, such as shadows, glows, or reflections; and don’t flip, rotate, or animate the Apple Pay mark.
+
+**Maintain a minimum clear space around the mark of 1/10 of its height.** Don’t let the Apple Pay mark share its surrounding border with another graphic or button.
+
+Download the Apple Pay mark graphic and full usage guidelines [here](https://developer.apple.com/apple-pay/marketing/).
+
+## [Referring to Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Referring-to-Apple-Pay)
+
+As with all Apple product names, use Apple Pay exactly as shown in [Apple Trademark List](https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html) — never make it plural or possessive — and adhere to [Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
+
+You can use plain text to promote Apple Pay and indicate that Apple Pay is a payment option.
+
+**Capitalize Apple Pay in text as it appears in the Apple Trademark list.** Use two words with an uppercase _A_ , an uppercase _P_ , and lowercase for all other letters. Display Apple Pay entirely in uppercase only when doing so is necessary for conforming to an established, typographic interface style, such as in an app that capitalizes all text.
+
+**Never use the Apple logo to represent the name _Apple_ in text.** In the United States, use the registered trademark symbol (®) the first time Apple Pay appears in body text. Don’t include a registered trademark symbol when Apple Pay appears as a selection option during checkout.
+
+| Example text
+---|---
+| Purchase with Apple Pay
+| Purchase with Apple Pay®
+| Purchase with ApplePay
+| Purchase with Pay
+| Purchase with APPLE PAY
+
+**Coordinate the font face and size with your app.** Don’t mimic Apple typography. Instead, use text attributes that are consistent with the rest of your app or website.
+
+**Don’t translate _Apple Pay_ or any other Apple trademark.** Always use Apple trademarks in English, even when they appear within non-English text.
+
+**In a payment selection context, you can display a text-only description of Apple Pay only when all payment options have text-only descriptions.** If any other payment option description includes an icon or logo, you must use the Apple Pay mark as described in [Offering Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Offering-Apple-Pay).
+
+**When promoting your app’s use of Apple Pay, follow App Store guidelines.** Before promoting Apple Pay for your app, refer to the [App Store marketing guidelines](https://developer.apple.com/app-store/marketing/guidelines/).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, visionOS, or watchOS. Not supported in tvOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Related)
+
+[Apple Pay Marketing Guidelines](https://developer.apple.com/apple-pay/marketing/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Developer-documentation)
+
+[Apple Pay](https://developer.apple.com/documentation/PassKit/apple-pay) — PassKit
+
+[Apple Pay on the Web](https://developer.apple.com/documentation/ApplePayontheWeb)
+
+[`WKInterfacePaymentButton`](https://developer.apple.com/documentation/WatchKit/WKInterfacePaymentButton) — WatchKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Videos)
+
+[ What’s new in Apple Pay ](https://developer.apple.com/videos/play/wwdc2025/201)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/apple-pay#Change-log)
+
+Date| Changes
+---|---
+December 16, 2025| Clarified supported platforms, including web browsers and Apple Vision Pro.
+June 10, 2024| Updated links to developer guidance for offering Apple Pay on the web.
+September 12, 2023| Updated artwork.
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/augmented-reality.md b/web-app/public/skills/hig-technologies/references/augmented-reality.md
new file mode 100644
index 00000000..b965c226
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/augmented-reality.md
@@ -0,0 +1,247 @@
+---
+title: "Augmented reality | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/augmented-reality
+
+# Augmented reality
+
+Augmented reality (or AR) lets you deliver immersive, engaging experiences that seamlessly blend virtual objects with the real world.
+
+
+
+Using the device’s camera to present the physical world onscreen live, your app can superimpose three-dimensional virtual objects, creating the illusion that these objects actually exist. Depending on the platform and the experiences your app offers, people can reorient the device to explore the objects from different angles, interact with objects using gestures and movement, and even join other people in multiuser AR experiences. For developer guidance, see [ARKit](https://developer.apple.com/documentation/ARKit).
+
+**Offer AR features only on capable devices.** If your app’s primary purpose is AR, make your app available only to devices that support ARKit. If your app includes features that require specific AR capabilities, or if AR features are optional in your app, don’t show people an error if they try to use these features on a device that doesn’t support them; instead, simply avoid offering the feature on an unsupported device. For developer guidance, see [Verifying Device Support and User Permission](https://developer.apple.com/documentation/ARKit/verifying-device-support-and-user-permission).
+
+Note
+
+The following guidance applies to apps that run in iOS and iPadOS. To learn about using ARKit to create immersive augmented reality experiences in visionOS, see [ARKit](https://developer.apple.com/documentation/ARKit).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Best-practices)
+
+**Let people use the entire display.** Devote as much of the screen as possible to displaying the physical world and your app’s virtual objects. Avoid cluttering the screen with controls and information that diminish the immersive experience.
+
+**Strive for convincing illusions when placing realistic objects.** Design detailed 3D assets with lifelike textures to create objects that appear to inhabit the physical environment in which you place them. Using information from ARKit, you can scale objects properly and position them on detected real-world surfaces, reflect environmental lighting conditions and simulate camera grain, cast top-down diffuse object shadows on real-world surfaces, and update visuals as the camera’s position changes. To help avoid breaking the illusion you create, make sure your app updates scenes 60 times per second so objects don’t appear to jump or flicker.
+
+**Consider how virtual objects with reflective surfaces show the environment.** Reflections in ARKit are approximations based on the environment captured by the camera. To help maintain the illusion that an AR experience is real, prefer small or coarse reflective surfaces that downplay the effect of these approximations.
+
+**Use audio and haptics to enhance the immersive experience.** A sound effect or bump sensation is a great way to confirm that a virtual object has made contact with a physical surface or other virtual object. Background music can also help envelop people in the virtual world. For guidance, see [Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio) and [Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics).
+
+**Minimize text in the environment.** Display only the information that people need for your app experience.
+
+**If additional information or controls are necessary, consider displaying them in screen space.** Content in _screen space_ appears fixed to a consistent location either in the virtual world or, less commonly, on the device screen. It’s typically easy for people to find and view content in screen space because it remains stationary while the underlying AR environment moves with the device.
+
+**Consider using indirect controls when you need to provide persistent controls.** _Indirect controls_ are not part of the virtual environment — instead, they are 2D controls displayed in screen space. If people need access to persistent controls in your app, consider placing the controls so that people don’t have to adjust how they’re holding the device to reach them. Also, consider using translucency in an indirect control to help avoid blocking the underlying scene. For example, the Measure app uses screen space to display a mix of translucent and opaque controls that people use to measure objects in the real world.
+
+
+
+**Anticipate that people will use your app in a wide variety of real-world environments.** People may open your app in a place where there isn’t much room to move around or there aren’t any large, flat surfaces. Clearly communicate your app’s requirements and expectations to people up front to help them understand how their physical environment can affect their AR experience. You might also consider offering different sets of features for use in different environments.
+
+**Be mindful of people’s comfort.** Holding a device at a certain distance or angle for a prolonged period can be fatiguing. To help avoid causing fatigue, consider placing objects at a distance that reduces the need to move the device closer to the object; in a game, consider keeping levels short and intermixed with brief periods of downtime.
+
+**If your app encourages people to move, introduce motion gradually.** For example, you might not want to make people dodge a virtual projectile as soon as they enter your AR game. Give people time to adapt to the AR experience in your app and then progressively encourage movement.
+
+**Be mindful of people’s safety.** When people are immersed in an AR experience, they’re not necessarily aware of their physical surroundings, so making rapid, sweeping, or expansive motions might be dangerous. Consider ways of making your app safe to operate; for example, a game could avoid encouraging large or sudden movements.
+
+## [Providing coaching](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Providing-coaching)
+
+Before people can enjoy an AR experience in your app, they need to move their device in ways that lets ARKit evaluate the surroundings and detect surfaces. Consider using the built-in coaching view to show people what to do and provide feedback during the initialization process. You can also use the coaching view to help people reinitialize AR — a process known as _relocalization_ — after an AR experience is interrupted by, for example, people switching briefly to a different app. For guidance on relocalization, see [Handling interruptions](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Handling-interruptions); for developer guidance, see [`ARCoachingOverlayView`](https://developer.apple.com/documentation/ARKit/ARCoachingOverlayView).
+
+
+
+**Hide unnecessary app UI while people are using a coaching view.** By default, the coaching view appears automatically when initialization or relocalization starts, so be prepared to hide unrelated UI to help people concentrate on the coaching view’s instructions.
+
+**If necessary, offer a custom coaching experience.** Although you can configure the system-provided coaching view to help people provide specific information — such as the detection of a horizontal or vertical plane — you might need additional information or want to use a different visual style. If you want to design a custom coaching experience, use the system-provided coaching view for reference.
+
+## [Helping people place objects](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Helping-people-place-objects)
+
+**Show people when to locate a surface and place an object.** You can use the system-provided coaching view to help people find a horizontal or vertical flat surface on which to place an object. After ARKit detects a surface, your app can display a custom visual indicator to show when object placement is possible. You can help people understand how the placed object will look in the environment by aligning your indicator with the plane of the detected surface.
+
+App-specific indicator
+
+**When people place an object, immediately integrate that object into the AR environment.** Although surface detection quickly and progressively refines accuracy, it’s best to avoid waiting for more accurate data before placing an object. Use the information available to respond instantly when people place an object; then, when surface detection completes, subtly refine the object’s position if necessary. For example, if people place an object beyond the bounds of the detected surface, gently nudge the object back onto the surface. For developer guidance on refining an object’s position, see [`ARTrackedRaycast`](https://developer.apple.com/documentation/ARKit/ARTrackedRaycast).
+
+**Consider guiding people toward offscreen virtual objects.** Sometimes, it can be difficult for people to locate an object that’s positioned offscreen. When this is the case, you can help people find such objects by offering visual or audible cues. For example, if an object is offscreen to the left, you could display an indicator along the left edge of the screen that guides people to point the camera in that direction.
+
+**Avoid trying to precisely align objects with the edges of detected surfaces.** In AR, surface boundaries are approximations that may change as people’s surroundings are further analyzed.
+
+**Incorporate plane classification information to inform object placement.** For example, only let people place a virtual piece of furniture on a plane that’s classified as “floor,” or require a plane to be classified as “table” in order to place a virtual game board.
+
+## [Designing object interactions](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Designing-object-interactions)
+
+**Let people use direct manipulation to interact with objects when possible.** It’s more immersive and intuitive when people can interact with onscreen 3D objects by touching them directly, than by using indirect controls in screen space. However, in situations where people are moving around as they use your app, indirect controls can work better.
+
+Direct manipulation
+
+Indirect controls
+
+**Let people directly interact with virtual objects using standard, familiar gestures.** For example, consider supporting a single-finger drag gesture for moving objects, and a two-finger rotation gesture for spinning objects. For guidance, see [Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures).
+
+**In general, keep interactions simple.** Touch gestures are inherently two-dimensional, but an AR experience involves the three dimensions of the real world. Consider the following approaches to simplifying people’s interactions with virtual objects.
+
+Limit movement to the two-dimensional surface on which the object rests.
+
+Limit object rotation to a single axis.
+
+**Respond to gestures within reasonable proximity of interactive virtual objects.** It can be difficult for people to be precise when aiming to touch specific points on objects that are small, thin, or placed at a distance. When your app detects a gesture near an interactive object, it’s usually best to assume that people want to affect that object.
+
+**Let people initiate object scaling when it makes sense in your app.** For example, if your app lets people explore an imaginary environment, it probably makes sense to support object scaling because your app doesn’t need to represent the real world. On the other hand, if your app helps shoppers decide on furniture to buy, letting people scale a chair object doesn’t help them visualize how the chair will look in a room.
+
+Tip
+
+Regardless of the purpose of your app, don’t use scaling as a way to adjust the distance of an object. If you enlarge a distant object in an effort to make it appear closer, the result is a larger object that still looks far away.
+
+**Be wary of potentially conflicting gestures.** A two-finger pinch gesture, for example, is similar to a two-finger rotation gesture. If you implement two similar gestures like this, be sure to test your app and make sure they’re interpreted properly.
+
+**Strive for virtual object movement that’s consistent with the physics of your app’s AR environment.** People don’t necessarily expect an object to move smoothly over a rough or uneven surface, but they do expect objects to remain visible during movement. Aim to keep moving objects attached to real-world surfaces and avoid causing objects to jump or vanish and reappear as people resize, rotate, or move them.
+
+**Explore even more engaging methods of interaction.** Gestures aren’t the only way for people to interact with virtual objects in AR. Your app can use other factors, like motion and proximity, to bring content to life. A game character, for example, could turn its head to look at a person as they walk toward it.
+
+## [Offering a multiuser experience](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Offering-a-multiuser-experience)
+
+When multiple people share your app’s AR experience, each participant maps the environment independently and ARKit automatically merges the maps. For developer guidance, see [`isCollaborationEnabled`](https://developer.apple.com/documentation/ARKit/ARWorldTrackingConfiguration/isCollaborationEnabled).
+
+**Consider allowing people occlusion.** If your app supports placing virtual objects behind people who appear in the device’s camera feed, enhance the illusion of reality by letting the people occlude the objects. For developer guidance, see [Occluding virtual content with people](https://developer.apple.com/documentation/ARKit/occluding-virtual-content-with-people).
+
+**When possible, let new participants enter a multiuser AR experience.** Unless your app requires all participants to join before the experience begins, consider using implicit map merging to let new people quickly join an ongoing AR experience. For developer guidance, see [`isCollaborationEnabled`](https://developer.apple.com/documentation/ARKit/ARWorldTrackingConfiguration/isCollaborationEnabled).
+
+## [Reacting to real-world objects](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Reacting-to-real-world-objects)
+
+You can enhance an AR experience by using known images and objects in the real-world environment to make virtual content appear. For example, an app that recognizes theater posters for a sci-fi film could cause virtual space ships to emerge from the posters and fly around the environment. Another example is an app for an art museum that presents a virtual tour guide when it recognizes a sculpture. To support experiences like these, your app provides a set of 2D reference images or 3D reference objects, and ARKit indicates when and where it detects any of these items in the current environment. For developer guidance, see [Detecting Images in an AR Experience](https://developer.apple.com/documentation/ARKit/detecting-images-in-an-ar-experience).
+
+**When a detected image first disappears, consider delaying the removal of virtual objects that are attached to it.** ARKit doesn’t track changes to the position or orientation of each detected image. To help prevent virtual objects from flickering, consider waiting up to one second before fading them out or removing them.
+
+**Limit the number of reference images in use at one time.** Image detection performance works best when ARKit looks for 100 or fewer distinct images in the real-world environment. If you need more than 100 reference images, you can change the set of active reference images based on context. For example, a museum guide app could ask permission to use location services to determine the part of the museum a person is in, and then look only for images displayed in that area.
+
+**Limit the number of reference images requiring an accurate position.** Updating the position of a reference image requires more resources. Use a tracked image when the image may move in the environment or when an attached animation or virtual object is small compared to the size of the image.
+
+## [Communicating with people](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Communicating-with-people)
+
+**If you must display instructional text, use approachable terminology.** AR is an advanced concept that may be intimidating to some people. To help make it approachable, avoid using technical terms like ARKit, world detection, and tracking. Instead, use friendly, conversational terms that most people will understand.
+
+Do| Don’t
+---|---
+Unable to find a surface. Try moving to the side or repositioning your phone.| Unable to find a plane. Adjust tracking.
+Tap a location to place the _[name of object to be placed]_.| Tap a plane to anchor an object.
+Try turning on more lights and moving around.| Insufficient features.
+Try moving your phone more slowly.| Excessive motion detected.
+
+**In a three-dimensional context, prefer 3D hints.** For example, placing a 3D rotation indicator around an object is more intuitive than displaying text-based instructions in a 2D overlay. Avoid displaying textual overlay hints in a 3D context unless people aren’t responding to contextual hints.
+
+Prefer a 3D hint in a 3D context.
+
+If necessary, use a 2D hint in a 3D context.
+
+**Make important text readable.** Use screen space to display text used for critical labels, annotations, and instructions. If you need to display text in 3D space, make sure the text faces people and that you use the same type size regardless of the distance between the text and the labeled object.
+
+**If necessary, provide a way to get more information.** Design a visual indicator that fits with your app experience to show people that they can tap for more information.
+
+
+
+Camera view
+
+
+
+Detail view
+
+## [Handling interruptions](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Handling-interruptions)
+
+ARKit can’t track device position and orientation during an interruption, such as when people briefly switch to another app or accept a phone call. After an interruption ends, previously placed virtual objects are likely to appear in the wrong real-world positions. When you support relocalization, ARKit attempts to restore those virtual objects to their original real-world positions using new information. For developer guidance, see [Managing Session Life Cycle and Tracking Quality](https://developer.apple.com/documentation/ARKit/managing-session-life-cycle-and-tracking-quality).
+
+**Consider using the system-provided coaching view to help people relocalize.** During relocalization, ARKit attempts to reconcile its previous state with new observations of the current environment. To make these observations more useful, you can use the coaching view to help people return the device to its previous position and orientation.
+
+
+
+**Consider hiding previously placed virtual objects during relocalization.** To avoid flickering or other unpleasant visual effects during relocalization, it can be best to hide virtual objects and redisplay them in their new positions.
+
+**Minimize interruptions if your app supports both AR and non-AR experiences.** One way to avoid interruptions is by embedding a non-AR experience within an AR experience so that people can handle the task without exiting and re-entering AR. For example, if your app helps people decide on a piece of furniture to purchase by placing the item in a room, you might let them change the upholstery without leaving the AR experience.
+
+**Allow people to cancel relocalization.** If people don’t position and orient their device near where it was before an interruption, relocalization continues indefinitely without success. If coaching people to resume their session isn’t successful, consider providing a reset button or other way to restart the AR experience.
+
+**Indicate when the front-facing camera is unable to track a face for more than about half a second.** Use a visual indicator to indicate that the camera can no longer track the person’s face. If you need to provide text instructions in this situation, keep them to a minimum.
+
+## [Suggesting problem resolutions](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Suggesting-problem-resolutions)
+
+**Let people reset the experience if it doesn’t meet their expectations.** Don’t force people to wait for conditions to improve or struggle with object placement. Give them a way to start over again and see if they have better results.
+
+Sufficient lighting
+
+Insufficient lighting
+
+**Suggest possible fixes if problems occur.** Analysis of the real-world environment and surface detection can fail or take too long for a variety of reasons — insufficient light, an overly reflective surface, a surface without enough detail, or too much camera motion. If your app is notified of these problems, use straightforward, friendly language to offer suggestions for resolving them.
+
+Problem| Possible suggestion
+---|---
+Insufficient features detected.| Try turning on more lights and moving around.
+Excessive motion detected.| Try moving your phone slower.
+Surface detection takes too long.| Try moving around, turning on more lights, and making sure your phone is pointed at a sufficiently textured surface.
+
+## [Icons and badges](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Icons-and-badges)
+
+Apps can display an AR icon in controls that launch ARKit-based experiences. You can download this icon in [Resources](https://developer.apple.com/design/resources/#ios-apps).
+
+
+
+
+
+**Use the AR glyph as intended.** The glyph is strictly for initiating an ARKit-based experience. Never alter the glyph (other than adjusting its size and color), use it for other purposes, or use it in conjunction with AR experiences not created using ARKit.
+
+**Maintain minimum clear space.** The minimum amount of clear space required around an AR glyph is 10% of the glyph’s height. Don’t let other elements infringe on this space or occlude the glyph in any way.
+
+
+
+Apps that include collections of products or other objects can use badging to identify specific items that can be viewed in AR using ARKit. For example, an app that sells vintage collectibles might use a badge to mark items that people can preview in their home before making a purchase.
+
+
+
+**Use the AR badges as intended and don’t alter them.** You can download AR badges, available in collapsed and expanded form, in [Resources](https://developer.apple.com/design/resources/#ios-apps). Use these images exclusively to identify products or other objects that can be viewed in AR using ARKit. Never alter the badges, change their color, use them for other purposes, or use them in conjunction with AR experiences not created with ARKit.
+
+AR badge
+
+Glyph-only AR badge
+
+**Prefer the AR badge to the glyph-only badge.** In general, use the glyph-only badge for constrained spaces that can’t accommodate the AR badge. Both badges work well at their default size.
+
+**Use badging only when your app contains a mixture of objects that can be viewed in AR and objects that cannot.** If all objects in your app can be viewed in AR, then badging is redundant.
+
+**Keep badge placement consistent and clear.** A badge looks best when displayed in one corner of an object’s photo. Always place it in the same corner and make sure it’s large enough to be seen clearly (but not so large that it occludes important detail in the photo).
+
+**Maintain minimum clear space.** The minimum amount of clear space required around an AR badge is 10% of the badge’s height. Don’t allow other elements to infringe on this space and occlude the badge in any way.
+
+
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, or watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#visionOS)
+
+With the wearer’s [permission](https://developer.apple.com/design/human-interface-guidelines/privacy#visionOS), you can use ARKit in your visionOS app to detect surfaces in a person’s surroundings, use a person’s hand and finger postions to inform your [custom gestures](https://developer.apple.com/design/human-interface-guidelines/gestures#Designing-custom-gestures-in-visionOS), support interactions that incorporate nearby physical objects into your [immersive experience](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences), and more. For developer guidance, see [ARKit](https://developer.apple.com/documentation/ARKit).
+
+Video with custom controls.
+
+Content description: A recording showing a 3D model of a meteor in visionOS rotating above a physical table.
+
+Play
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Related)
+
+[Playing haptics](https://developer.apple.com/design/human-interface-guidelines/playing-haptics)
+
+[Gestures](https://developer.apple.com/design/human-interface-guidelines/gestures)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#ios-apps)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Developer-documentation)
+
+[ARKit](https://developer.apple.com/documentation/ARKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/augmented-reality#Videos)
+
+[ Qualities of great AR experiences ](https://developer.apple.com/videos/play/wwdc2022/10131)
+
+[ Explore ARKit 5 ](https://developer.apple.com/videos/play/wwdc2021/10073)
+
diff --git a/web-app/public/skills/hig-technologies/references/carekit.md b/web-app/public/skills/hig-technologies/references/carekit.md
new file mode 100644
index 00000000..5ea1553e
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/carekit.md
@@ -0,0 +1,224 @@
+---
+title: "CareKit | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/carekit
+
+# CareKit
+
+People can use CareKit apps to manage care plans related to a chronic illness like diabetes, recover from an injury or surgery, or achieve health and wellness goals.
+
+
+
+To learn more about CareKit, see [Research & Care > CareKit](https://www.researchandcare.org/carekit/).
+
+CareKit 2.0 contains two projects, CareKit UI and CareKit Store. CareKit UI provides a wide variety of prebuilt views you can use to create a custom CareKit app. CareKit Store defines a database scheme that incorporates CareKit entities — such as patients, care plans, tasks, and contacts — so you can store and manage data on the patient’s device. CareKit 2.0 provides seamless synchronization between your database and the UI, so you can always keep a care plan up to date. For developer guidance, see [CareKit](https://carekit-apple.github.io/CareKit/documentation/carekit).
+
+## [Data and privacy](https://developer.apple.com/design/human-interface-guidelines/carekit#Data-and-privacy)
+
+Nothing is more important than protecting people’s privacy and safeguarding the extremely sensitive data your CareKit app collects and stores.
+
+**Provide a coherent privacy policy.** During the app submission process, you must provide a URL to a clearly stated privacy policy, so that people can view the policy when they click the link in the App Store page for your app. For developer guidance, see [App information > App Store Connect help](https://help.apple.com/app-store-connect/#/dev219b53a88).
+
+In addition to the data that people enter into your CareKit app, you may be able to access data through iOS features and capabilities. You must receive people’s permission before accessing data through these features, and you must protect people’s data whether people enter it into your app or you get it from the device or the system. For developer guidance, see [Protecting user privacy](https://developer.apple.com/documentation/HealthKit/protecting-user-privacy).
+
+### [HealthKit integration](https://developer.apple.com/design/human-interface-guidelines/carekit#HealthKit-integration)
+
+HealthKit is the central repository for health and fitness data in iOS and watchOS. When you support HealthKit in your CareKit app, you can ask people for permission to access and share their health and fitness data with designated caregivers.
+
+**Request access to health data only when you need it.** It makes sense to request access to weight information when people log their weight, for example, but not immediately after your app launches. When your request is clearly related to the current context, you help people understand your app’s intentions. Also, people can change the permissions they grant, so it’s a good idea to make a request every time your app needs access. For developer guidance, see [`requestAuthorization(toShare:read:completion:)`](https://developer.apple.com/documentation/HealthKit/HKHealthStore/requestAuthorization\(toShare:read:completion:\)).
+
+**Clarify your app’s intent by adding descriptive messages to the standard permission screen.** People expect to see the system-provided permission screen when asked to approve access to health data. Write a few succinct sentences that explain why you need the information and how people can benefit from sharing it with your app. Avoid adding custom screens that replicate the standard permission screen’s behavior or content.
+
+**Manage health data sharing solely through the system’s privacy settings.** People expect to globally manage access to their health information in Settings > Privacy. Don’t confuse people by building additional screens in your app that affect the flow of health data.
+
+For related design guidance, see [HealthKit](https://developer.apple.com/design/human-interface-guidelines/healthkit). For developer guidance, see [HealthKit](https://developer.apple.com/documentation/HealthKit).
+
+### [Motion data](https://developer.apple.com/design/human-interface-guidelines/carekit#Motion-data)
+
+If it’s useful for treatment and if people give permission, your app can get motion information from the device to determine if people are standing still, walking, running, cycling, or driving. When people are walking or running, you can also determine the step count, pace, and number of flights of stairs ascended or descended.
+
+Motion information can also include custom data collected as part of physical therapy. For example, some ResearchKit tasks use device sensors to test flexibility, range of motion, and ambulatory capability.
+
+For developer guidance, see [Core Motion](https://developer.apple.com/documentation/CoreMotion).
+
+### [Photos](https://developer.apple.com/design/human-interface-guidelines/carekit#Photos)
+
+Pictures are a great way to communicate treatment progress. With people’s permission, your app can access the device’s camera and photos to share pictures with a care team. For example, a care plan might include a request for people to share periodic photos of an injury, so the physician can monitor the healing process.
+
+For developer guidance, see [`UIImagePickerController`](https://developer.apple.com/documentation/UIKit/UIImagePickerController).
+
+### [ResearchKit integration](https://developer.apple.com/design/human-interface-guidelines/carekit#ResearchKit-integration)
+
+A ResearchKit app lets people participate in important medical research studies. Your CareKit app can incorporate ResearchKit features to display related surveys, tasks, and charts, if appropriate. ResearchKit also includes an informed consent module, which your CareKit app can use to request people’s permission to collect and share data.
+
+For related design guidance, see [ResearchKit](https://developer.apple.com/design/human-interface-guidelines/researchkit). For developer guidance, see [Research & Care > Developers](https://www.researchandcare.org/developers/).
+
+## [CareKit views](https://developer.apple.com/design/human-interface-guidelines/carekit#CareKit-views)
+
+CareKit UI provides customizable views organized into three categories — tasks, charts, and contacts — and defines several default view styles in each. To design a CareKit app, you simply choose the view styles you need and supply CareKit Store data to display in them.
+
+Each view category is designed to support specific types of content and interaction. To ensure a consistent experience, use each view type for its intended purpose.
+
+Category| Purpose
+---|---
+[Tasks](https://developer.apple.com/design/human-interface-guidelines/carekit#Tasks)| Present tasks, like taking medication or doing physical therapy. Support logging of patient symptoms and other data.
+[Charts](https://developer.apple.com/design/human-interface-guidelines/carekit#Charts)| Display graphical data that can help people understand how their treatment is progressing.
+[Contact views](https://developer.apple.com/design/human-interface-guidelines/carekit#Contact-views)| Display contact information. Support communication through phone, message, and email, and link to a map of the contact’s location.
+
+
+
+Tasks and charts
+
+
+
+Contacts
+
+A CareKit UI view consists of a header and may include a stack of content subviews. Located at the top of the view, the header can display text, a symbol, and a disclosure indicator, and can include a separator at its bottom edge. The content stack appears below the header and displays your content subviews in a vertical arrangement.
+
+
+
+CareKit UI takes care of all the layout constraints within a view, so you don’t have to worry about breaking existing constraints when you add new subviews to the stack.
+
+### [Tasks](https://developer.apple.com/design/human-interface-guidelines/carekit#Tasks)
+
+A care plan generally presents a set of prescribed actions for people to perform, such as taking medication, eating specific foods, exercising, or reporting symptoms. CareKit UI defines several styles of task views you can use to display prescribed actions. Typically, you customize a task view by providing the information to display, often by specifying data stored in an on-device CareKit Store database. In some cases, you might also supply custom UI elements.
+
+A task can contain the following types of information.
+
+Information| Required| Description| Example value
+---|---|---|---
+Title| Yes| A word or short phrase that introduces the task.| _Ibuprofen_
+Schedule| Yes| The schedule on which a task must be completed.| _Four times a day_
+Instructions| No| Detailed instructions, recommendations, and warnings.| _Take 1 tablet every 4–6 hours (not to exceed 4 tablets daily)._
+Group ID| No| An identifier you can use to group similar tasks in ways that make sense in your app.| A category identifier like _medication_ or _exercise_.
+
+In CareKit 2.0, CareKit UI defines five styles of task views: simple, instructions, log, checklist, and grid. Each style is designed to support a particular use case.
+
+**Use the simple style for a one-step task.** The default simple-style view consists of a header area that contains a title, subtitle, and button. You provide the title and subtitle, and you can provide a custom image to display in the button when the task is complete. If you don’t supply an image, CareKit shows that a task is complete by filling in the button and displaying a checkmark. Because the default simple-style view doesn’t include a content stack, consider using a different task style if you need to display additional content.
+
+
+
+**Use the instructions style when you need to add informative text to a simple task.** For example, if a single-step medication task needs to include additional information — such as “Take on an empty stomach” or “Take at bedtime” — you can use an instructions-style task to display it.
+
+
+
+**Use the log style to help people log events.** For example, you could use this task style to display a button people can tap whenever they feel nauseated. The log-style task can automatically display a timestamp every time the patient logs an event.
+
+
+
+**Use the checklist style to display a list of actions or steps in a multistep task.** For example, if people must take a medication three times per day, you could display the three scheduled times in a checklist. Each checklist item can include a text description and a button that people can tap to mark the item as done. By default, a checklist task can also display instructional text below the list.
+
+
+
+**Use the grid style to display a grid of buttons in a multistep task.** Like the checklist style, the grid style also supports a multistep task, but it displays the steps in a more compact arrangement. You can supply a succinct title for each button (if you need to provide additional description for each button, you might want to use the checklist style instead). By default, a grid-style task can also display instructional text below the grid of buttons. Unlike other task styles, the grid style gives you access to its underlying collection view, which means that you can display custom UI elements in the grid layout.
+
+
+
+**Consider using color to reinforce the meaning of task items.** Color can be a good way to help people understand information at a glance. For example, you could use one color for medications and a different color for physical activities. Always avoid using color as the only way to convey information. For guidance, see [Color](https://developer.apple.com/design/human-interface-guidelines/color).
+
+**Combine accuracy with simplicity when describing a task and its steps.** For example, use a medication’s marketing name instead of its chemical description. Also, when the context of a task helps to clarify meaning, minimize the number of words you use. For example, a daily medication task generally tells people when to take specific medications, so it may be unnecessary to repeat words like _take_.
+
+**Consider supplementing multistep or complex tasks with videos or images.** Visually demonstrating how to perform a task can help people avoid mistakes.
+
+### [Charts](https://developer.apple.com/design/human-interface-guidelines/carekit#Charts)
+
+Chart views let you present data and trends in graphical ways that can help people visualize their progress in a care plan. CareKit chart views can display both current and historical data, and update automatically with new data.
+
+In CareKit 2.0, CareKit UI provides three chart styles: bar, scatter, and line. For each style, you provide a descriptive title and subtitle, supply axis markers — like days of the week — and specify the data set.
+
+Bar chart
+
+Scatter chart
+
+Line chart
+
+**Consider highlighting narratives and trends to illustrate progress.** For example, your app could display a bar chart that shows a correlation between the number of times people took medication and their level of pain. Displaying such data can encourage better adherence to a care plan.
+
+**Label chart elements clearly and succinctly.** Long, detailed labels can make a chart difficult to read and understand. Keep labels short and avoid repeating the same information. For example, a heart rate chart might use the term _BPM_ in an axis label instead of using it in the label of every data point.
+
+**Use distinct colors.** In general, avoid using different shades of the same color to mean different things. Also ensure that you use colors with sufficient contrast. For related guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Consider providing a legend to add clarity.** If the colors you use to represent different types of data aren’t immediately clear, include a legend that clearly and succinctly describes them.
+
+**Clearly denote units of time.** People need to know whether time-based data is represented in seconds, minutes, hours, days, weeks, months, or years. If you don’t want to include this information in individual data value labels, include it in an axis label or elsewhere on the chart.
+
+**Consolidate large data sets for greater readability.** A large amount of data can make a chart unreadable by reducing the size of individual data points and presenting too much visible information. Look for ways to group and organize data for clarity and simplicity.
+
+**If necessary, offset data to keep charts proportional.** It’s easy for very small data points to get lost or become unreadable in a chart that also contains very large data points. If the difference between data points is significant, find ways to offset or restructure the data so all data points are readable.
+
+For developer guidance, see [CareKit > Chart Interfaces](https://carekit-apple.github.io/CareKit/documentation/carekit/chart-interfaces). To learn about ResearchKit charts, see the [ResearchKit GitHub project](https://github.com/ResearchKit/ResearchKit).
+
+### [Contact views](https://developer.apple.com/design/human-interface-guidelines/carekit#Contact-views)
+
+A care plan typically includes a care team and other trusted individuals who can help patients follow the plan. CareKit UI defines a contact view you can use to help patients communicate with the people in their care plan.
+
+In CareKit 2.0, CareKit UI provides two styles of the contact view: simple and detailed.
+
+Simple
+
+Detailed
+
+**Consider using color to categorize care team members.** Color can help people identify care team members at a glance.
+
+## [Notifications](https://developer.apple.com/design/human-interface-guidelines/carekit#Notifications)
+
+Notifications can tell people when it’s time to take medication or complete a task, and badging your app icon can show that there’s an unread message from a caregiver. Apple Watch can also display a notification from your app; for guidance, see [Notifications](https://developer.apple.com/design/human-interface-guidelines/notifications).
+
+**Minimize notifications.** Care plans vary from patient to patient. While one individual may have only a few daily tasks to complete, another may have a long list. Use notifications sparingly so people don’t feel overwhelmed. When possible, consider coalescing multiple items into a single notification.
+
+**Consider providing a detail view.** In addition to providing more information, a notification detail view can help people take immediate action without leaving their current context to open your app. For example, you could use a notification detail view to display a list of pending tasks so that people can quickly mark them as complete.
+
+## [Symbols and branding](https://developer.apple.com/design/human-interface-guidelines/carekit#Symbols-and-branding)
+
+CareKit uses a variety of built-in symbols to help people understand what they can do in a care app. For example, CareKit can display the phone, messaging, and envelope symbols in a contact view and the clock symbol in a log-style task view.
+
+Although you can customize the default symbols, most view styles work best with the CareKit-provided symbols. The exception is the highly customizable grid-style task view, which can display your custom UI in a grid layout.
+
+In a grid view, you might want to display custom symbols that are relevant to the unique content and experience in your app. You could use symbols to indicate the grouping of tasks; for example, a pill to represent medication tasks, or a person walking to represent exercise tasks. In this scenario, consider using [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) to illustrate custom items in your app.
+
+Using SF Symbols in your app gives you:
+
+ * Designs that coordinate with CareKit’s visual design language
+
+ * Support for creating custom symbols to represent the unique content in your app
+
+
+
+
+**Design a relevant care symbol.** If you need to customize a symbol, be sure the design is closely related to your app or the general concept of health and wellness. Avoid creating a purely decorative symbol or using a corporate logo as a custom symbol.
+
+**Incorporate refined, unobtrusive branding.** People use CareKit apps to help them achieve their health and wellness goals; they don’t want to see advertising. To avoid distracting people from their care plan, subtly incorporate your brand through your app’s use of color and communication style.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/carekit#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/carekit#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/carekit#Related)
+
+[Research & Care > CareKit](https://www.researchandcare.org/carekit/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/carekit#Developer-documentation)
+
+[CareKit](https://carekit-apple.github.io/CareKit/documentation/carekit)
+
+[Research & Care > Developers](https://www.researchandcare.org/developers/)
+
+[Protecting user privacy](https://developer.apple.com/documentation/HealthKit/protecting-user-privacy) — HealthKit
+
+[HealthKit](https://developer.apple.com/documentation/HealthKit)
+
+[ResearchKit GitHub project](https://github.com/ResearchKit/ResearchKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/carekit#Videos)
+
+[ What's new in CareKit ](https://developer.apple.com/videos/play/wwdc2020/10151)
+
+[ Build a research and care app, part 1: Setup onboarding ](https://developer.apple.com/videos/play/wwdc2021/10068)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/carekit#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/carplay.md b/web-app/public/skills/hig-technologies/references/carplay.md
new file mode 100644
index 00000000..96f7ce50
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/carplay.md
@@ -0,0 +1,119 @@
+---
+title: "CarPlay | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/carplay
+
+# CarPlay
+
+CarPlay lets people get directions, make calls, send and receive messages, listen to music, and more from their car’s built-in display, all while staying focused on the road.
+
+
+
+People download CarPlay apps from the App Store and install them on iPhone like any other app. When people connect their iPhone with their vehicle, app icons for installed CarPlay apps appear on the CarPlay Home screen.
+
+CarPlay is designed for drivers to use while they’re driving. Keep this context in mind as you design your CarPlay app, providing features that help people perform tasks quickly and with minimal interaction.
+
+To create the interface of your CarPlay app, you use the system-defined templates that are appropriate for the type of app you’re developing, such as audio, communication, navigation, or fueling. For each template, your app provides the content and iOS renders it in CarPlay. Because the system displays UI components and handles the interface with the vehicle, you don’t need to adjust your layout for different screen resolutions, or manage input from different types of hardware like touchscreens, knobs, or touch pads.
+
+To learn how to create various types of CarPlay apps and use the system-provided templates, see [CarPlay App Programming Guide](https://developer.apple.com/carplay/documentation/CarPlay-App-Programming-Guide.pdf). The general design guidelines below apply to all types of CarPlay apps.
+
+## [iPhone interactions](https://developer.apple.com/design/human-interface-guidelines/carplay#iPhone-interactions)
+
+CarPlay shows compatible apps from the connected iPhone on the car’s built-in display, applying simplified interfaces that are optimized for use while driving.
+
+**Eliminate app interactions on iPhone when CarPlay is active.** Interactions with your app need to occur using the car’s built-in controls and display. If your app requires setup on iPhone, make sure people perform it before the vehicle is in motion.
+
+**Never lock people out of CarPlay because the connected iPhone requires input.** Your app needs to function when iPhone is inaccessible — for example, when people put it in a bag or in the trunk while driving. If people must resolve a problem on the connected iPhone, let them do so after the vehicle stops.
+
+**Make sure your app works without requiring people to unlock iPhone.** Most people use CarPlay while their iPhone is locked, so ensure that the features you provide in your CarPlay app work as expected in this scenario.
+
+### [Audio](https://developer.apple.com/design/human-interface-guidelines/carplay#Audio)
+
+In CarPlay, keep in mind that your app coexists with other audio sources, such as the car’s own built-in radio and voice prompts from the navigation system. Regardless of whether audio is a primary aspect of your app’s experience, you need to know how people expect audio to behave so you can meet those expectations.
+
+**Let people choose when to start playback.** In general, avoid beginning playback automatically unless your app’s purpose is to play a single source of audio, or your app is resuming previously interrupted audio. Also, avoid starting an audio session until you’re ready to actually play audio because starting a session silences other audio sources, like the car’s built-in radio.
+
+**Start playback as soon as audio has sufficiently loaded.** After people make a selection, it may take several seconds for audio to begin playing, depending on buffering and network conditions. The system keeps the selection highlighted and displays a spinning activity indicator until your app signals that the audio is ready to play.
+
+**Display the Now Playing screen when audio is ready to play.** Don’t delay playback until descriptive information completes loading. If necessary, continue loading such information in the background, and show it when it’s available.
+
+**Resume audio playback after an interruption only when it’s appropriate.** For example, your app can resume audio after a temporary interruption like a phone call. Permanent interruptions, such as a music playlist initiated by Siri, are nonresumable. When a resumable interruption occurs, your app needs to resume playback when the interruption ends if audio was actively playing when the interruption started.
+
+**When necessary, automatically adjust audio levels, but don’t change the overall volume.** Although your app can adjust relative, independent volume levels to achieve a great mix of audio, people need to control the final output volume.
+
+## [Layout](https://developer.apple.com/design/human-interface-guidelines/carplay#Layout)
+
+CarPlay supports a wide range of display resolutions with varying pixel densities and aspect ratios. The system automatically scales app icons and interfaces based on the resolution of the display, so they always appear onscreen at roughly the same size. Some common screen sizes are listed in the table below.
+
+Dimensions (pixels)| Aspect ratio
+---|---
+800x480| 5:3
+960x540| 16:9
+1280x720| 16:9
+1920x720| 8:3
+
+**Provide useful, high-value information in a clean layout that’s easy to scan from the driver’s seat.** Don’t clutter the screen with nonessential details and unnecessary visual embellishments.
+
+**Maintain an overall consistent appearance throughout your app.** In general, ensure that elements with similar functions look similar.
+
+**Ensure that primary content stands out and feels actionable.** Large items tend to appear more important than smaller ones and are easier for people to tap. In general, place the most important content and controls in the upper half of the screen.
+
+## [Color](https://developer.apple.com/design/human-interface-guidelines/carplay#Color)
+
+Color can indicate interactivity, impart vitality, and provide visual continuity.
+
+**In general, prefer a limited color palette that coordinates with your app logo.** Subtle use of color is a great way to communicate your brand.
+
+**Avoid using the same color for interactive and noninteractive elements.** If interactive and noninteractive elements have the same color, it’s hard for people to know where to tap.
+
+**Test your app’s color scheme under a variety of lighting conditions in an actual car.** Lighting varies significantly based on time of day, weather, window tinting, and more. Colors you see on your computer at design time won’t always look the same when your app is used in the real world. Consider how color brightness might affect the experience of driving at night, and how low-contrast colors can wash out in direct sunlight. If necessary, make adjustments to provide the best possible viewing experience in the majority of use cases.
+
+**Ensure your app looks great in both dark and light environments.** CarPlay supports both light and dark appearances, and may automatically adjust the current appearance based on lighting conditions.
+
+**Choose colors that help you communicate effectively with everyone.** Different people see and interpret colors differently. For guidance on using colors in ways that people appreciate, see [Inclusive color](https://developer.apple.com/design/human-interface-guidelines/color#Inclusive-color).
+
+## [Icons and images](https://developer.apple.com/design/human-interface-guidelines/carplay#Icons-and-images)
+
+CarPlay supports both landscape and portrait displays and both @2x (low resolution) and @3x (high resolution) scale factors.
+
+**Supply high-resolution images with scale factors of @2x and @3x for all CarPlay artwork in your app.** The system automatically shows the correct images and scales them appropriately, based on the resolution and size of the car’s display.
+
+**Mirror your iPhone app icon.** A well-designed app icon works well in CarPlay and on iPhone, without the need for a second design.
+
+**Don’t use black for your icon’s background.** Lighten a black background or add a border so the icon doesn’t blend into the display background.
+
+Create your CarPlay app icon in the following sizes:
+
+@2x (pixels)| @3x (pixels)
+---|---
+120x120| 180x180
+
+## [Error handling](https://developer.apple.com/design/human-interface-guidelines/carplay#Error-handling)
+
+A CarPlay app needs to handle errors gracefully and report them to people only when absolutely necessary.
+
+**Report errors in CarPlay, not on the connected iPhone.** If you must notify people of a problem, do so clearly in CarPlay. Never direct people to pick up their iPhone to read or resolve an error.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/carplay#Platform-considerations)
+
+ _No additional considerations for iOS. Not supported in iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/carplay#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/carplay#Related)
+
+[CarPlay](http://developer.apple.com/carplay/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/carplay#Developer-documentation)
+
+[CarPlay App Programming Guide](https://developer.apple.com/carplay/documentation/CarPlay-App-Programming-Guide.pdf)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/carplay#Videos)
+
+[ Turbocharge your app for CarPlay ](https://developer.apple.com/videos/play/wwdc2025/216)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/carplay#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/game-center.md b/web-app/public/skills/hig-technologies/references/game-center.md
new file mode 100644
index 00000000..66b4330c
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/game-center.md
@@ -0,0 +1,343 @@
+---
+title: "Game Center | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/game-center
+
+# Game Center
+
+Game Center is Apple’s social gaming network, which lets players track their progress and connect with friends across Apple platforms, and boosts the discovery of your game across players’ devices.
+
+
+
+Supporting Game Center in your game allows players to:
+
+ * Discover new games their friends are playing.
+
+ * Seamlessly invite friends to play.
+
+ * See the latest activity from their games across the system, in the Apple Games app, the App Store, notifications, and more.
+
+
+
+
+By enabling the player activities listed above, supporting Game Center also helps surface your game to more players across Apple platforms.
+
+You can add Game Center into your game using the GameKit framework, which provides a full-featured UI that makes it easy for players to access and view their Game Center data within your game. Alternatively, you can also use GameKit to present this data within your own custom UI. For developer guidance, see [GameKit](https://developer.apple.com/documentation/GameKit).
+
+## [Accessing Game Center](https://developer.apple.com/design/human-interface-guidelines/game-center#Accessing-Game-Center)
+
+To provide the best Game Center experience for your players, begin by determining whether the player is signed in to their Game Center account on the system when they launch your game. If they aren’t, initialize the player with Game Center at that time. This provides the most seamless user experience, and maximizes discovery opportunities for your game, such as in the Top Played chart and in social recommendations through players’ friends.
+
+### [Integrating the access point](https://developer.apple.com/design/human-interface-guidelines/game-center#Integrating-the-access-point)
+
+The Game Center _access point_ is an Apple-designed UI element that lets players view their Game Center profile and information without leaving your game. For developer guidance, see [Adding an access point to your game](https://developer.apple.com/documentation/GameKit/adding-an-access-point-to-your-game).
+
+
+
+In iOS, iPadOS, and macOS the access point leads players to the Game Overlay, a system overlay that allows players to view their progress and start game activities.
+
+
+
+In visionOS and tvOS, the access point leads players to the in-game dashboard, a full-screen view of a player’s Game Center activity that appears on top of your game.
+
+**Display the access point in menu screens.** Consider adding the access point to the main menu or the settings area of your game. Avoid displaying the access point during active gameplay or in temporary splash screens, cinematic flows, or tutorials that might precede your game’s main menu screen.
+
+**Avoid placing controls near the access point.** You can choose to present the access point at any of the four corners of the screen in a fixed position. Remember that the access point has both a collapsed and expanded version, so check whether the access point overlaps any important UI and controls and adjust your layout accordingly.
+
+Note
+
+In visionOS, the locations of the access point vary based on game type, such as immersive or volume-based. For developer guidance, see [Adding an access point to your game](https://developer.apple.com/documentation/GameKit/adding-an-access-point-to-your-game#Configure-the-access-point-on-visionOS).
+
+**Consider pausing your game while the Game Overlay or dashboard is present.** Pausing your game can help players view their Game Center information without feeling like the game is continuing without them.
+
+### [Using custom UI](https://developer.apple.com/design/human-interface-guidelines/game-center#Using-custom-UI)
+
+Your game can include custom links into the Game Overlay (in iOS, iPadOS, macOS) or the dashboard (in visionOS and tvOS). Your custom UI can deep-link into specific areas within both such as leaderboards or a player’s Game Center profile.
+
+**Use the artwork Game Center provides in custom links.** When referencing Game Center features in custom UI, use the official artwork from [Apple Design Resources](https://developer.apple.com/design/resources/#technologies). Preserve the appearance of this artwork and don’t adjust the dimensions or visual effects.
+
+**Use the correct terminology in custom links.** The following table describes how to use Game Center terminology correctly so that you can avoid confusing players in custom UI.
+
+Term| Incorrect terms| Localization
+---|---|---
+Game Center| GameKit, GameCenter, game center| Use the system-provided translation of _Game Center_
+Game Center Profile| Profile, Account, Player Info| Use the system-provided translation of _Game Center_ and localize _Profile_
+Achievements| Awards, Trophies, Medals|
+Leaderboards| Rankings, Scores, Leaders|
+Challenges| Competitions|
+Add Friends| Add, Add Profiles, Include Friends|
+
+## [Achievements](https://developer.apple.com/design/human-interface-guidelines/game-center#Achievements)
+
+Achievements give players an added incentive to stay engaged with your game. Game Center achievements appear in a collectible card format that highlights the player’s progress and showcases your artwork. For developer guidance, see [Rewarding players with achievements](https://developer.apple.com/documentation/GameKit/rewarding-players-with-achievements).
+
+
+
+Achievements overview
+
+
+
+Achievement detail
+
+### [Integrating achievements into your game](https://developer.apple.com/design/human-interface-guidelines/game-center#Integrating-achievements-into-your-game)
+
+**Align with Game Center achievement states.** Game Center defines four achievement states: locked, in-progress, hidden, and completed. The system groups achievements by completion status, displaying completed achievements in the Completed group and all other achievements in the Locked group. When you map your achievements to the four Game Center achievement states, you give players a consistent experience and you help them see at a glance the types of achievements your game offers.
+
+**Determine a display order.** The order in which you upload achievements is the order in which they appear, so consider the order you want before uploading files. For example, you might want your achievements to appear in an order that corresponds to the most common path through your game.
+
+**Be succinct when describing achievements.** The achievement card limits the title and description to two lines each. If your title or description wraps beyond two lines, the card truncates the text. Use title-style capitalization for the achievement title and sentence-style capitalization for the description.
+
+
+
+**Give players a sense of progress.** When you use progressive achievements, the system displays player progress and provides encouraging messages like “Youʼre more than halfway to completing Great Lakes Freighter in The Coast. Keep going!” to help motivate players to complete them.
+
+### [Creating achievement images](https://developer.apple.com/design/human-interface-guidelines/game-center#Creating-achievement-images)
+
+**Design rich, high-quality images that help players feel rewarded.** Achievements are a prominent feature in Game Center UI, so it’s essential to design high-quality assets that catch the eye and encourage players to return to your game. Avoid reusing the same asset to represent more than one achievement. If you don’t provide an asset for an achievement, the card shows a placeholder image instead.
+
+**Create artwork in the appropriate size and format.** The system applies a circular mask to your achievement image, so be sure to keep content centered. Use the following specifications to create images.
+
+ * iOS, iPadOS, macOS, visionOS
+ * tvOS
+
+
+
+
+
+Attribute| Value
+---|---
+Format| PNG, TIF, or JPG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 512x512 pt (1024x1024 px @2x)
+Mask diameter| 512 pt (1024 px @2x)
+
+
+
+Attribute| Value
+---|---
+Format| PNG, TIF, or JPG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 320x320 pt (640x640 px @2x)
+Mask diameter| 200 pt (400 px @2x)
+
+## [Leaderboards](https://developer.apple.com/design/human-interface-guidelines/game-center#Leaderboards)
+
+Leaderboards are a great way to encourage friendly competition within your game. When you adopt Game Center, players can easily check their ranking against friends and global players as well as receive notifications when their friends challenge them or pass their score on a leaderboard. You can take advantage of the system-designed UI or present leaderboard information within custom UI. For developer guidance, see [Encourage progress and competition with leaderboards](https://developer.apple.com/documentation/GameKit/encourage-progress-and-competition-with-leaderboards).
+
+
+
+Leaderboards overview
+
+
+
+Leaderboard detail
+
+**Choose a leaderboard type.** Game Center supports two types of leaderboards: _classic_ and _recurring_.
+
+ * A _classic leaderboard_ tracks a player’s best all-time score. Classic leaderboards are always active with no ending. The following are examples of goals you might include in a classic leaderboard:
+
+ * Strive for the most perfect score in a rhythm game.
+
+ * Collect the most coins in a single dungeon run.
+
+ * Achieve the longest continuous time in an endless runner.
+
+ * A _recurring leaderboard_ resets based on a time interval you define, such as every week or every day. Recurring leaderboards can increase engagement by giving players more chances to take the lead. The following are examples of features that work well with recurring leaderboards:
+
+ * Daily rotating puzzles
+
+ * Seasonal or holiday-themed events
+
+ * Weekly leaderboards for different battle modes
+
+
+
+
+**Take advantage of leaderboard sets for multiple leaderboards.** Leaderboard sets are an organization system that can make it easier for players to find the board they’re looking for. Consider grouping leaderboard sets by themes or gameplay experiences, such as:
+
+ * Difficulty modes (Easy, Standard, Hard)
+
+ * Activity types (Combat, Crafting, Farming)
+
+ * Genres and themes (Disco, Pop, Rock)
+
+
+
+
+**Add leaderboard images.** Leaderboard artwork gives you another opportunity to reinforce your game’s visual aesthetic. Aim to create a unique image for each leaderboard in your game that reflects and showcases the gameplay involved in leaderboard ranking. Leaderboards appear across the system, promoting ways for players to engage and compete with friends, and having compelling images helps attract players and gives them a sense of the experience.
+
+For games that run in iOS, iPadOS, and macOS, use a single image for your leaderboard image. For games that run in tvOS, provide a set of images that animate when the artwork is in focus. To learn more about focus effects, see [Focus and selection](https://developer.apple.com/design/human-interface-guidelines/focus-and-selection). For help creating focusable images, download the tvOS template from [Apple Design Resources](https://developer.apple.com/design/resources/#tvos-apps). Use the following specifications to create leaderboard artwork.
+
+ * iOS, iPadOS, macOS
+ * tvOS
+
+
+
+
+
+Attribute| Value
+---|---
+Format| JPEG, JPG, or PNG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 512x512 pt (1024x1024 px @2x)
+Cropped area| 512x312 pt (1024x624 px @2x)
+
+
+
+Attribute| Value
+---|---
+Format| PNG, TIF, or JPG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 659x371 pt (1318x742 px @2x)
+Focused size| 618x348 pt (1236x696 px @2x)
+Unfocused size| 548x309 pt (1096x618 px @2x)
+
+Note
+
+Be mindful of how cropping might affect your leaderboard artwork. In iOS, iPadOS, and macOS, the system crops artwork for leaderboards that are part of a leaderboard set. In tvOS, the focus effect on leaderboard artwork may crop your images at the edges of some layers. Make sure your primary content stays comfortably visible in both these scenarios.
+
+## [Challenges](https://developer.apple.com/design/human-interface-guidelines/game-center#Challenges)
+
+Challenges turn single player activities into multiplayer experiences with friends. Challenges are built on top of leaderboards and allow players to connect with their friends and participate in competitions with time limits. For developer documentation, see [Creating engaging challenges from leaderboards](https://developer.apple.com/documentation/GameKit/creating-engaging-challenges-from-leaderboards).
+
+
+
+Challenges overview
+
+
+
+Challenge detail
+
+**Create engaging challenges.** Challenges are great for short, skill-based gameplay activities that have a clear way of gauging players’ accomplishments. Create challenges that take 1-5 minutes to play, with gameplay that players can complete individually. Examples of compelling challenges are:
+
+ * Complete the fastest lap in a racing level.
+
+ * Defeat the most enemies in a single round.
+
+ * Solve a daily puzzle with the fewest mistakes.
+
+
+
+
+**Avoid creating challenges that track overall progress or personal best scores.** These can give regular players an unfair advantage. Instead, track players’ most recent score after each attempt at your challenge. This helps keep your challenge motivating by placing all players on a level playing field.
+
+**Make it easy to jump into your challenge.** Players can access challenges through invitation links, the Game Overlay, or in the Games app in iOS, iPadOS, and macOS. Always deep-link to the exact mode or level where your challenge begins, and help first-time players complete any initial onboarding before beginning the challenge. For example, if your game requires a tutorial level to understand basic controls, launch the player into the tutorial first and present UI that lets them know your game automatically jumps into the challenge afterward.
+
+
+
+**Create high-quality artwork that encourages players to engage with your challenges.** The system shows your challenge’s artwork in the Game Overlay, Games app, and in the preview of an invitation link. Avoid placing the primary content of your artwork in an area where the challenge’s title and description might cover it. If you need to use text in your challenge image, provide the appropriate localized versions through App Store Connect or Xcode. Use the following specifications to create challenge artwork.
+
+
+
+Attribute| Value
+---|---
+Format| JPEG, JPG, or PNG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 1920x1080 pt (3840x2160 px @2x)
+Cropped area| 1465x767 pt (2930x1534 px @2x)
+
+## [Multiplayer activities](https://developer.apple.com/design/human-interface-guidelines/game-center#Multiplayer-activities)
+
+Game Center supports both real-time and turn-based multiplayer activities that make it easy to connect players with friends or other players. Players can access multiplayer gameplay through party codes, the Game Overlay, the dashboard, or in the Games app. For developer documentation, see [Creating activities for your game](https://developer.apple.com/documentation/GameKit/creating-activities-for-your-game).
+
+
+
+Multiplayer levels overview
+
+
+
+Multiplayer level detail
+
+**Use party codes to invite players to multiplayer activities.** Game Center party codes are a great way to coordinate real-time multiplayer sessions whether you use Game Center matchmaking and networking facilities or provide your own. Game Center generates alpha-numeric party codes that are typically eight characters long, such as “2MP4-9CMF.” When integrating party codes into your multiplayer games, consider the following guidelines for the best player experience:
+
+ * Allow players to join gameplay late, leave early, and return later.
+
+ * Provide a way for players to view the current party code in your game.
+
+ * Allow players to enter a party code manually.
+
+
+
+
+
+
+**Support multiplayer activities through in-game UI.** The Game Overlay and Game Center dashboard help players find other people for a multiplayer match without leaving your game. Game Center’s default multiplayer interface lets a player invite nearby or recent players, Game Center friends, and contacts. You can also choose to present multiplayer functionality within your custom UI. For developer guidance, see [Finding multiple players for a game](https://developer.apple.com/documentation/GameKit/finding-multiple-players-for-a-game).
+
+
+
+**Provide engaging activity artwork.** Players see the preview image for a multiplayer activity throughout the system, such as in a party code, the Games app, or in-game UI. Use the following specifications to create your artwork.
+
+
+
+
+
+Attribute| Value
+---|---
+Format| JPEG, JPG, or PNG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+Image size| 1920x1080 pt (3840x2160 px @2x)
+Cropped area| 1465x767 pt (2930x1534 px @2x)
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/game-center#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or visionOS._
+
+### [tvOS](https://developer.apple.com/design/human-interface-guidelines/game-center#tvOS)
+
+**Display an optional image at the top of the dashboard.** In tvOS, you can add an additional piece of artwork to the dashboard to highlight your game’s aesthetic. Use a simple, easily recognizable image that looks great at a distance. Consider using your game’s logo or word mark; however, don’t use your app icon for this image. Use the following specifications to create a dashboard image.
+
+
+
+Attribute| Value
+---|---
+Image size| 600x180 pt (1200x360 px @2x)
+Format| PNG, TIF, or JPG
+Color space| sRGB or P3
+Resolution| 72 DPI (minimum)
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/game-center#watchOS)
+
+**Be aware of Game Center support on watchOS.** While GameKit features and API are available for watchOS games, keep in mind that there’s no system-supported Game Center UI that you can invoke on watchOS. Instead, Game Center content for watchOS games appears on a connected iPhone.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/game-center#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/game-center#Related)
+
+[Designing for games](https://developer.apple.com/design/human-interface-guidelines/designing-for-games)
+
+[Game controls](https://developer.apple.com/design/human-interface-guidelines/game-controls)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#technologies)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/game-center#Developer-documentation)
+
+[GameKit](https://developer.apple.com/documentation/GameKit)
+
+[Creating activities for your game](https://developer.apple.com/documentation/GameKit/creating-activities-for-your-game)
+
+[Creating engaging challenges from leaderboards](https://developer.apple.com/documentation/GameKit/creating-engaging-challenges-from-leaderboards)
+
+[Create games for Apple platforms](https://developer.apple.com/games/)
+
+[Game Porting Toolkit](https://developer.apple.com/games/game-porting-toolkit/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/game-center#Videos)
+
+[ Get started with Game Center ](https://developer.apple.com/videos/play/wwdc2025/214)
+
+[ Engage players with the Apple Games app ](https://developer.apple.com/videos/play/wwdc2025/215)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/game-center#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance for new challenges and multiplayer activities, and considerations for the Apple Games app and Game Overlay. Updated guidance and specifications for activity preview images.
+February 2, 2024| Added links to developer guidance on using the access point and dashboard in a visionOS game.
+September 12, 2023| Added artwork for the iOS achievement layout.
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/generative-ai.md b/web-app/public/skills/hig-technologies/references/generative-ai.md
new file mode 100644
index 00000000..48450a02
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/generative-ai.md
@@ -0,0 +1,110 @@
+---
+title: "Generative AI | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/generative-ai
+
+# Generative AI
+
+Generative AI empowers you to enhance your app or game with dynamic content and offer intelligent features that unlock new levels of creativity, connection, and productivity.
+
+
+
+Generative artificial intelligence uses [machine learning](https://developer.apple.com/design/human-interface-guidelines/machine-learning) models to create and transform text, images, and other content. Use it to offer novel, delightful features that help people express themselves creatively, communicate effectively, and complete tasks more easily. For instance, generative AI can enable people to edit text, create imaginative stories and images, or interact with a character in a game that uses AI-generated dialog.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Best-practices)
+
+**Design your experience responsibly.** Responsible AI is the intentional design and development of AI features that considers their direct and indirect impacts on people, systems, and society. With generative AI, it’s often easy to quickly prototype an exciting new feature for your app, yet challenging to create a robust experience that works in all real-world situations. Unlike classic programming, small changes to inputs (or even the same input, when given multiple times) often produce very different outcomes with generative AI. You also can’t always anticipate what requests people will make and how the AI will respond. Orient your design process around crafting AI experiences that are inclusive, designed with care, and protect privacy.
+
+**Keep people in control.** While AI can manipulate and create content, respect people’s agency and ensure they remain in charge of decision making and the overall experience. Honor their requests when in scope and the expected output is clear, and handle sensitive content carefully. Give them the ability to dismiss new content they don’t want, and revert or retry content transformations or other actions they don’t agree with. Clearly identify when and where you use AI.
+
+**Ensure an inclusive experience for all.** AI models learn from data and tend to favor the most common information. This may lead to harmful, unintended biases and stereotypes. Take extra care when designing your AI feature to consider how assumptions and personal attributes might impact the feature you have in mind. For example, if you generate images or descriptions of people, ask people to provide the information needed for the feature to work well rather than solely inferring personal or cultural characteristics. Seek clarity before making assumptions that may lead to common stereotypes, such as about gender identities or relationship types. Test your feature across a diverse set of people to identify and correct stereotypes, and ensure inclusive results. For guidance, see [Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion) and [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+**Design engaging and useful generative features.** Generative AI is a powerful tool, but it’s not the right solution for every situation. Offer generative features when and where they provide clear and specific value, like time savings, improved communication, or enhanced creativity.
+
+**Ensure a great experience even when generative features aren’t available or people opt not to use them.** In some cases, generative AI may be essential to an experience, and there’s no reasonable non-AI substitute. In other cases, AI may play a complementary role that enhances your app’s core functionality, but isn’t critical for people achieving their goals. For example, Genmoji offers a fun way to create new, original emoji, but people can still use regular emoji too. The Apple Intelligence summarization feature makes catching up with notifications faster, but people can still read notifications without it. When possible, consider offering a non-AI fallback so people can always enjoy your app or game.
+
+## [Transparency](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Transparency)
+
+**Communicate where your app uses AI.** Letting people know when and where your app uses AI sets expectations and gives people the opportunity to knowingly choose to use an AI-powered feature. Never trick someone into thinking they’re interacting with or viewing content authored by a human if they’re actually interacting with AI. Ensure your approach to disclosure aligns with any regulations in the regions where you offer your app.
+
+**Set clear expectations about what your AI-powered feature can and can’t do.** Clarifying your experience’s capabilities and limitations helps people establish a mental model of your feature. For example, when you introduce a feature, you might offer a brief tutorial. For open-ended features like a search bar or generation prompt, consider offering curated suggestions that make it easy to get started. If your feature has known limitations, let people know up front, show them how to get good results, and explain why when inferior results occur. For guidance, see [Limitations](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Limitations).
+
+## [Privacy](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Privacy)
+
+**Prefer on-device processing.** Depending on your needs, you may be able to get great responses using on-device models, which prevent people’s information from leaving the device. For example, you may choose to use the on-device models available through the Apple Foundation Models framework. On-device models may also respond quicker than server-based models, and are available even when the device is offline. Server-based models are usually good options in situations that need larger, powerful models that require more memory and power than is typically available on a person’s device. Always consider privacy and user experience tradeoffs when selecting a model type. If you’re using server-based processing, process as much information as you can locally first and minimize what’s shared. Make sure people know if their information may be sent to a server, can see what’s being shared, and understand what data may be stored off-device or even used for training.
+
+**Ask permission before using personal information and usage data.** Some interactions with an AI model may involve sensitive information, like personal details, messages, photos, and feature usage information. After obtaining permission, use the minimum data you need and always offer a clear way to opt out of its use. If you need sensitive data for model improvement or storage, get explicit permission and handle it with care. If you share data with third parties, understand their approach to privacy. Be aware that model outputs can inadvertently contain sensitive information. Note that [apps for kids](https://developer.apple.com/app-store/kids-apps/) have stricter rules and laws around what data you can use. For guidance, see [Requesting permission](https://developer.apple.com/design/human-interface-guidelines/privacy#Requesting-permission).
+
+**Clearly disclose how your app and its model use and store personal information.** People are more likely to be comfortable sharing data when they understand how it’s used. Empower people to make an informed decision about what data they share with your AI model. When asking for permission to use someone’s information, explain the benefits in a way that’s concise, specific, and easy to understand. Articulate whether your model uses personal information for training and improvement.
+
+## [Models and datasets](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Models-and-datasets)
+
+**Thoughtfully evaluate model capabilities.** There are different types of generative models, some of which possess general knowledge, while others are trained for specific tasks. It’s important to understand the capabilities of any model you consider. As early as you can, get a hands-on look at the models and data available to help orient your design. Keep in mind that some model types may be unavailable to people in certain situations due to factors like device compatibility, network access, and battery level. For example, the [Foundation Models](https://developer.apple.com/documentation/FoundationModels) framework requires a compatible device with Apple Intelligence turned on.
+
+**Be intentional when choosing or creating a dataset.** Whether you’re training a model from scratch or customizing an existing model, the data you choose greatly impacts the model’s behavior. When you teach and evaluate your AI model, choose datasets that include a diverse range of subject matter representations. Learn where your data comes from and how it was gathered. Ensure you have relevant licenses for all data you don’t personally own, and offer appropriate choices when using people’s data. Most datasets gathered from the real world are imperfect, so allow time for testing and evaluation to proactively mitigate bias and misinformation that a model might learn and replicate.
+
+## [Inputs](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Inputs)
+
+**Guide people on how to use your generative feature.** Consider how to steer and educate people toward producing great results. One technique is to offer diverse, predefined example inputs that hint at what’s possible for a feature.
+
+**Raise awareness about and minimize the chance of hallucinations.** When a generative model is unsure how to respond to a request, it may produce content that seems plausible but is made up. These hallucinations can misinform people because the model may convincingly present the information as factual, even when it’s not. Generative models sometimes get details wrong, like dates of important events or information about people, so it’s important to clearly communicate that AI-generated content may contain errors. You can minimize the chance of hallucinations and limit their impact by carefully scoping what you ask a model to generate. Avoid requesting factual information unless you’re confident the model has access to verified and up-to-date information for the task. Avoid using AI-generated content in situations where a possible hallucination could misinform and harm someone.
+
+**Consider consequences and get permission before performing destructive or potentially problematic tasks.** Before performing a task, consider whether a mistake or the inability to reverse the action might cause more work or stress for people. Avoid automating destructive actions, like deleting photos, and actions that are hard to undo, like making a purchase on a person’s behalf. Generally, ask for confirmation before performing a significant action on someone’s behalf. Keep in mind that certain situations may be prohibited or have extra rules. Review and adhere to model-specific usage policies, as well as government and regulatory AI policy as it applies to each locale in which the generative features will be available.
+
+## [Outputs](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Outputs)
+
+**Help people improve requests when blocked or undesirable results occur.** Minimize scoped or blocked output by coaching people how to be more successful next time. For example, if prompted to generate harmful content, Image Playground says that it’s “Unable to use that description.” When possible, consider offering example requests that might lead to better results.
+
+**Reduce unexpected and harmful outcomes with thoughtful design and thorough testing.** People generally use apps with good intentions, but harmful outcomes can still arise from both accidental and purposeful misuse, and when responding to potentially sensitive topics. It may not be possible to mitigate every harmful scenario, but taking a proactive approach to identify risks, devise policies to address them, and evaluate features can help minimize the chance of misuse and harm. Consider ways people might interact with your feature and test those scenarios. Challenge your policies and expected use cases. See what happens when requests are out-of-scope, unrelated to the app experience you designed, and not well-represented by the model’s training data. Try requests that are poorly phrased, vague, or ambiguous; include personal, sensitive, or controversial topics; and encourage harmful or incorrect results. Use what you learn to improve your model, inform prevention, and respond thoughtfully.
+
+**Strive to avoid replicating copyrighted content.** Large AI models are trained using vast datasets from the internet and other sources. This means most generative models are familiar with and can unintentionally produce content similar to published work, including copyrighted content. You can reduce the likelihood of copyright infringement by building upon existing models that already protect against this, and by carefully curating inputs. For example, you might let people choose from a set of pre-approved prompts. You could also explicitly tell the model to avoid mimicking certain content or styles.
+
+**Factor processing time into your design.** _Latency_ is how much time it takes for a model to produce an output. Non-generative models, such as [people tracking in ARKit](https://developer.apple.com/documentation/arkit/capturing-body-motion-in-3d) and the [Vision](https://developer.apple.com/documentation/Vision) machine learning framework, typically have low latency and are suitable to run in real-time on camera feeds. Generative models typically take longer to produce a result, so design a loading experience or generate in the background while a person uses another part of the app. For guidance, see [Loading](https://developer.apple.com/design/human-interface-guidelines/loading).
+
+**Consider offering alternate versions of results.** Depending on the design of your feature, it might work best to present a single result or multiple meaningfully different results from which people can choose. Offering people a choice can give them a greater sense of control and help bridge the gap between the model’s interpretation and what someone actually wants. For example, Image Playground can generate multiple images that represent a person, allowing someone to pick the one they prefer. For guidance, see [Multiple options](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Multiple-options).
+
+## [Continuous improvement](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Continuous-improvement)
+
+**Consider ways to improve your model over time.** You may want to update your model to adapt to people’s behavior, respond to feedback, include new data, and leverage enhanced capabilities. You can make some improvements, such as updating a list of blocked words, frequently and independent of the app development cycle, and you can plan significant improvements and new features around regular app updates. Plan for fine-tuning, retesting, and prompt engineering when updating to a newer, more capable base model. If you train your own model, retrain with additional data and fine-tune to improve performance. Thoroughly test and refine all model updates to identify and correct unexpected behavior.
+
+**Let people share feedback on outputs.** Feedback can help you identify and respond to unexpected outcomes and new potential issues that arise despite thorough testing. Feedback also gives people a way to celebrate what they like best about your AI experience and report concerns when outputs don’t match their expectations. Establish trust by taking feedback seriously and resolving issues quickly. Always make providing feedback voluntary. Respect people’s time by placing a feedback affordance in a clear location that doesn’t interrupt the experience. Consider offering a quick and easy way to give positive and negative feedback, like simple thumbs-up and thumbs-down buttons. You might also offer a way to share detailed feedback for complicated issues. For guidance, see [Explicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback) and [Implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback).
+
+**Design flexible, adaptable features.** Generative AI is a rapidly advancing technology, and models and their resource needs are constantly evolving. Consider ways your app or game can adapt as capabilities and models improve. For example, you may want to separate your model from your user experience so you can swap out the model for other models over time. Lay a foundation that allows for future adjustments like this, while still offering the same great user experience.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Related)
+
+[Machine learning](https://developer.apple.com/design/human-interface-guidelines/machine-learning)
+
+[Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy)
+
+[Loading](https://developer.apple.com/design/human-interface-guidelines/loading)
+
+[Acceptable Use Requirements for the Foundation Models Framework](https://developer.apple.com/apple-intelligence/acceptable-use-requirements-for-the-foundation-models-framework)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Videos)
+
+[ Explore prompt design & safety for on-device foundation models ](https://developer.apple.com/videos/play/wwdc2025/248)
+
+[ Discover machine learning & AI frameworks on Apple platforms ](https://developer.apple.com/videos/play/wwdc2025/360)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Developer-documentation)
+
+[Apple Intelligence and machine learning](https://developer.apple.com/documentation/TechnologyOverviews/ai-machine-learning)
+
+[Foundation Models](https://developer.apple.com/documentation/FoundationModels)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/generative-ai#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| New page.
+
diff --git a/web-app/public/skills/hig-technologies/references/healthkit.md b/web-app/public/skills/hig-technologies/references/healthkit.md
new file mode 100644
index 00000000..59c315cd
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/healthkit.md
@@ -0,0 +1,120 @@
+---
+title: "HealthKit | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/healthkit
+
+# HealthKit
+
+HealthKit is the central repository for health and fitness data in iOS, iPadOS, and watchOS.
+
+
+
+When you support HealthKit in your app, you can ask people for permission to access and update their health information.
+
+Important
+
+If your app doesn’t provide health and fitness functionality, don’t request access to people’s private health data.
+
+For example, a nutrition app might ask for permission to retrieve people’s weight and activity data, so it can define calorie consumption goals and make dietary recommendations. In this scenario, the nutrition app could also send data — such as the calories that people log — to HealthKit, which can include the data in its global progress metrics.
+
+
+
+For developer guidance, see [HealthKit](https://developer.apple.com/documentation/HealthKit).
+
+## [Privacy protection](https://developer.apple.com/design/human-interface-guidelines/healthkit#Privacy-protection)
+
+You must request permission to access people’s data, and you must take all necessary steps to protect that data. After you receive permission, it’s essential to maintain people’s trust by clearly showing them how you use their data. For developer guidance, see [Protecting user privacy](https://developer.apple.com/documentation/HealthKit/protecting-user-privacy).
+
+**Provide a coherent privacy policy.** During the app submission process, you must provide a URL to a clearly stated privacy policy, so that people can view the policy when they click the link in the App Store page for your app. For developer guidance, see [App Information > App Store Connect Help](https://help.apple.com/app-store-connect/#/dev219b53a88).
+
+**Request access to health data only when you need it.** It makes sense to request access to weight information when people log their weight, for example, but not immediately after your app launches. When your request is clearly related to the current context, you help people understand your app’s intentions. Also, people can change the permissions they grant, so your app needs to make a request every time it needs access. For developer guidance, see [`requestAuthorization(toShare:read:completion:)`](https://developer.apple.com/documentation/HealthKit/HKHealthStore/requestAuthorization\(toShare:read:completion:\)).
+
+**Clarify your app’s intent by adding descriptive messages to the standard permission screen.** People expect to see the system-provided permission screen when asked to approve access to health data. Write a few succinct sentences that explain why you need the information and how people can benefit from sharing it with your app. Avoid adding custom screens that replicate the standard permission screen’s behavior or content.
+
+
+
+**Manage health data sharing solely through the system’s privacy settings.** People expect to globally manage access to their health information in Settings > Privacy. Don’t confuse people by building additional screens in your app that affect the flow of health data.
+
+## [Activity rings](https://developer.apple.com/design/human-interface-guidelines/healthkit#Activity-rings)
+
+You can enhance your app’s health and wellness offerings by displaying the Activity ring element to show people’s progress toward their Move, Exercise, and Stand goals. The Activity app defines the position and color of each ring, so people are familiar with the element and understand what it means.
+
+
+
+**Use Activity rings for Move, Exercise, and Stand information only.** Activity rings consistently represent progress in these specific areas. Don’t attempt to replicate or modify Activity rings for other purposes or to display other types of data. Never show Move, Exercise, and Stand progress in another ring-like element.
+
+**Use Activity rings to show progress for a single person.** Never use Activity rings to represent data for more than one person, and make sure it’s obvious whose progress is shown, such as by using a label, a photo, or an avatar.
+
+**Don’t use Activity rings for ornamentation.** Activity rings provide information to people; they don’t merely embellish your app’s design. Never display Activity rings in labels or background graphics.
+
+**Don’t use Activity rings for branding.** Use Activity rings strictly to display Activity progress in your app. Never use Activity rings in your app’s icon or marketing materials.
+
+**Maintain Activity ring and background colors.** For a consistent user experience, the visual appearance of Activity rings must always be the same, regardless of the context in which they appear. Never change the look of the rings or background by using filters, changing colors, or modifying opacity. Instead, design the surrounding interface to blend with the rings. For example, enclose the rings within a circle. Always scale the rings appropriately so they don’t seem disconnected or out of place.
+
+**Maintain Activity ring margins.** An Activity ring element must include a minimum outer margin of no less than the distance between rings. Never allow other elements to crop, obstruct, or encroach upon this margin or the rings themselves. To display an Activity ring element within a circle, adjust the corner radius of the enclosing view rather than applying a circular mask.
+
+**Differentiate other ring-like elements from Activity rings.** Mixing different ring styles can lead to a visually confusing interface. If you must include other rings, use padding, lines, or labels to separate them from Activity rings. Color and scale can also help provide visual separation.
+
+**Provide app-specific information only in Activity notifications.** The system already delivers Move, Exercise, and Stand progress updates. Don’t repeat this same information, and never show an Activity ring element in your app’s notifications. It’s fine to reference Activity progress in a notification, but do so in a way that’s unique to your app and doesn’t replicate the same information provided by the system.
+
+For developer guidance, see [`HKActivityRingView`](https://developer.apple.com/documentation/HealthKitUI/HKActivityRingView).
+
+## [Apple Health icon](https://developer.apple.com/design/human-interface-guidelines/healthkit#Apple-Health-icon)
+
+The Apple Health icon shows that an app works with HealthKit and the Health app. The following guidelines help you use the icon correctly. To learn how to refer to HealthKit and the Health app in copy and UI text, see [Editorial guidelines](https://developer.apple.com/design/human-interface-guidelines/healthkit#Editorial-guidelines); to learn about using the “Works with Apple Health” badge in your marketing communications, see [Works with Apple Health](https://developer.apple.com/health-fitness/works-with-apple-health/).
+
+
+
+**Use only the Apple-provided icon.** Don’t create your own Apple Health icon design or attempt to mimic any Apple-provided designs. Download the Apple Health app icon from [Apple Design Resources](https://developer.apple.com/design/resources/#technologies).
+
+**Display the name _Apple Health_ close to the Apple Health icon.** Displaying both elements near each other reminds people that the icon represents the Health app.
+
+**Display the Apple Health icon consistently with other health-related app icons.** In a view that contains other app icons, make the Apple Health icon no smaller than other icons.
+
+**Don’t use the Apple Health icon as a button.** Use the icon only to indicate compatibility with the Health app.
+
+**Don’t alter the appearance of the Apple Health icon.** Don’t mask the icon to change its corner radius or present it in a circular shape. Don’t add embellishments like borders, color overlays, gradients, shadows, or other visual effects.
+
+**Maintain a minimum clear space around the Apple Health icon of 1/10 of its height.** Don’t composite the icon onto another graphic element.
+
+**Don’t use the Apple Health icon within text or as a replacement for the terms _Health_ , _Apple Health_ , or _HealthKit_.** See [Editorial guidelines](https://developer.apple.com/design/human-interface-guidelines/healthkit#Editorial-guidelines) to learn how to properly reference the Health app and HealthKit in text.
+
+**Don’t display Health app images or screenshots.** Like all Apple images, these designs are copyrighted and can’t appear in your app or marketing materials. You can include an Activity ring element in your app to display Move, Exercise, and Stand progress; for guidance, see [Activity rings](https://developer.apple.com/design/human-interface-guidelines/healthkit#Activity-rings).
+
+## [Editorial guidelines](https://developer.apple.com/design/human-interface-guidelines/healthkit#Editorial-guidelines)
+
+**Refer to the Health app as _Apple Health_ or _the Apple Health app_.** In your app and marketing text, using _Apple Health_ adds clarity.
+
+**Don’t use the term _HealthKit_.** _HealthKit_ is a developer-facing term that names the framework your app uses to access health data. If you need to explain to people how your app works with their data, use the term _the Apple Health app_. For example, you might say that your app “works with the Apple Health app” or “uses data from the Apple Health app.”
+
+**Use correct capitalization when using the term _Apple Health_.** _Apple Health_ is two words, with an uppercase A and uppercase H, followed by lowercase letters. You can display _Apple Health_ entirely in uppercase only when you need to conform to an established typographic interface style, such as in an app that capitalizes all text.
+
+**Use the system-provided translation of _Health_ to avoid confusing people.** It’s best to refer to the Apple Health app using the translation that people view on their device.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/healthkit#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or watchOS. Not supported in macOS, tvOS, or visionOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/healthkit#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/healthkit#Related)
+
+[Works with Apple Health](https://developer.apple.com/health-fitness/works-with-apple-health/)
+
+[Activity rings](https://developer.apple.com/design/human-interface-guidelines/activity-rings)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/#technologies)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/healthkit#Developer-documentation)
+
+[HealthKit](https://developer.apple.com/documentation/HealthKit)
+
+[Protecting user privacy](https://developer.apple.com/documentation/HealthKit/protecting-user-privacy) — HealthKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/healthkit#Videos)
+
+[ Meet the HealthKit Medications API ](https://developer.apple.com/videos/play/wwdc2025/321)
+
+[ Track workouts with HealthKit on iOS and iPadOS ](https://developer.apple.com/videos/play/wwdc2025/322)
+
+[ Explore wellbeing APIs in HealthKit ](https://developer.apple.com/videos/play/wwdc2024/10109)
+
diff --git a/web-app/public/skills/hig-technologies/references/homekit.md b/web-app/public/skills/hig-technologies/references/homekit.md
new file mode 100644
index 00000000..13cdd82b
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/homekit.md
@@ -0,0 +1,343 @@
+---
+title: "HomeKit | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/homekit
+
+# HomeKit
+
+HomeKit lets people securely control connected accessories in their homes using Siri or the Home app on iPhone, iPad, Apple Watch, and Mac.
+
+
+
+In iOS, the Home app also lets people manage and configure accessories.
+
+Your iOS, tvOS, or watchOS app can integrate with HomeKit (and by extension the Home app) to provide a custom or accessory-specific experience. For example, you can:
+
+ * Help people set up, name, and organize their accessories
+
+ * Allow fine-grained accessory configuration and control
+
+ * Provide access to custom accessory features
+
+ * Show people how to create powerful, hands-free automations
+
+ * Provide support
+
+
+
+
+For developer guidance, see [HomeKit](https://developer.apple.com/documentation/HomeKit). If you’re an MFi licensee, visit the [MFi portal](https://mfi.apple.com) for guidance on naming and messaging for accessory packaging.
+
+## [Terminology and layout](https://developer.apple.com/design/human-interface-guidelines/homekit#Terminology-and-layout)
+
+HomeKit models the home as a hierarchy of objects and defines a vocabulary of terms that refer to them. The Home app uses the HomeKit object model and terminology to give people intuitive control of accessories by voice, app, and automation.
+
+It’s crucial for your app to use the terminology and object model that HomeKit defines, so that you can reinforce people’s understanding and make home automation feel approachable.
+
+In the HomeKit model, the [home](https://developer.apple.com/design/human-interface-guidelines/homekit#Homes) object is the root of a hierarchy that contains all other objects, such as [rooms](https://developer.apple.com/design/human-interface-guidelines/homekit#Rooms), [accessories](https://developer.apple.com/design/human-interface-guidelines/homekit#Accessories-services-and-characteristics), and [zones](https://developer.apple.com/design/human-interface-guidelines/homekit#Zones). When there’s more than one home, each home is the root of a different hierarchy.
+
+**Acknowledge the hierarchical model that HomeKit uses.** Even if your app doesn’t organize accessories by rooms and zones in its UI, it’s useful to reference the HomeKit model when helping people set up or control their accessories. People need to know where accessories are located so they can use Siri and HomePod to control them by speaking commands like “Siri, turn on the lights upstairs,” or “It’s dark in here.” For more guidance, see [Siri interactions](https://developer.apple.com/design/human-interface-guidelines/homekit#Siri-interactions).
+
+**Make it easy for people to find an accessory’s related HomeKit details.** If your app’s organization is based on accessories, don’t hide other HomeKit information, such as an accessory’s zone or room, in a hard-to-discover settings screen. Instead, consider making the related HomeKit information easily available in an accessory detail view.
+
+**Recognize that people can have more than one home.** Even if your app doesn’t support the concept of multiple homes per user, consider providing the relevant home information in an accessory detail view.
+
+**Don’t present duplicate home settings.** If your app has a different perspective on the organization of a home, don’t confuse people by asking them to set up all or parts of their homes again or by showing a duplicate settings view. Always defer to the settings people made in the Home app and find an intuitive way to present these details in your UI.
+
+### [Homes](https://developer.apple.com/design/human-interface-guidelines/homekit#Homes)
+
+HomeKit uses the term _home_ to represent a physical home, office, or other location of relevance to people. One person might have multiple homes.
+
+### [Rooms](https://developer.apple.com/design/human-interface-guidelines/homekit#Rooms)
+
+A _room_ represents a physical room in a home. Rooms don’t have attributes like size or location; they’re simply names that have meaning to people, such as _Bedroom_ or _Office_. When people assign accessories to a room, they can use voice commands like “Siri, turn on all the lights except the bedroom,” or “Siri, turn on the kitchen and hallway lights.”
+
+### [Accessories, services, and characteristics](https://developer.apple.com/design/human-interface-guidelines/homekit#Accessories-services-and-characteristics)
+
+The term _accessory_ represents a physical, connected home accessory, like a ceiling fan, lamp, lock, or camera. HomeKit uses _category_ to represent a type of accessory, such as thermostat, fan, or light. Typically, an accessory manufacturer assigns each accessory to a category, but your app can help people make this assignment if necessary. For example, a switch that’s connected to a fan or a lamp needs to be assigned to the same category as the accessory it controls.
+
+A controllable feature of an accessory, such as the switch on a connected light, is known as a _service_. Some accessories offer multiple services. For example, a connected garage door might let people control the light and the door separately, or a connected outlet might support separate control of the top outlet and the bottom outlet. Apps don’t use the word _service_ in the UI; instead, they use names that describe the service, such as _garage door opener_ and _ceiling fan light_. When people use Siri to control the accessories in their homes, they speak the service name, not the accessory name. For more guidance on naming, see [Help people choose useful names](https://developer.apple.com/design/human-interface-guidelines/homekit#Help-people-choose-useful-names).
+
+A _characteristic_ is a controllable attribute of a service. For example, in a ceiling fan, the fan service might have a speed characteristic and the light service might have a brightness characteristic. Apps don’t use the word _characteristic_ in the UI; instead, they use terms that describe the attribute, such as _speed_ and _brightness_.
+
+A _service group_ represents a group of accessory services that someone might want to control as a unit. For example, if there’s a floor lamp and two table lamps in one corner of a room, people might assign all three services to a service group named _reading lamps_. Doing so would let people use the _reading lamps_ service group to control these three lights independently of all other lights in the room.
+
+### [Actions and scenes](https://developer.apple.com/design/human-interface-guidelines/homekit#Actions-and-scenes)
+
+The term _action_ refers to the changing of a service’s characteristic, such as adjusting the speed of a fan or the brightness of a light. People and automation can initiate actions.
+
+A _scene_ is a group of actions that control one or more services in one or more accessories. For example, people might create a _Movie Time_ scene that lowers the shades and dims the lights in the living room, or a _Good Morning_ scene that turns on the lights, raises the shades, and starts the coffee maker in the kitchen.
+
+Tip
+
+The HomeKit API uses the term _action set_ instead of _scene_. In your app’s UI, always use the term _scene_.
+
+### [Automations](https://developer.apple.com/design/human-interface-guidelines/homekit#Automations)
+
+ _Automations_ cause accessories to react to certain situations, such as when a person’s location changes, a particular time of day occurs, another accessory turns on or off, or a sensor detects something. For example, an automation could turn on the house lights at sunset or when people arrive home.
+
+### [Zones](https://developer.apple.com/design/human-interface-guidelines/homekit#Zones)
+
+A _zone_ represents an area in the home that contains multiple rooms, such as _upstairs_ or _downstairs_. Setting up a zone is optional, but doing so lets people control multiple accessories at one time. For example, assigning all downstairs lights to a zone named _downstairs_ lets people use voice commands like “Siri, turn off all the lights downstairs.”
+
+## [Setup](https://developer.apple.com/design/human-interface-guidelines/homekit#Setup)
+
+**Use the system-provided setup flow to give people a familiar experience.** The HomeKit setup flow works more quickly than traditional setup flows because it lets people name accessories, join networks, pair with HomeKit, assign room and service categories, and designate favorites in just a few steps. Using the system-provided setup flow lets you concentrate on promoting the custom functionality that makes your accessory unique. For developer guidance, see [`performAccessorySetup(using:completionHandler:)`](https://developer.apple.com/documentation/HomeKit/HMAccessorySetupManager/performAccessorySetup\(using:completionHandler:\)).
+
+**Provide context to explain why you need access to people’s Home data.** Create a purpose string with a phrase that describes why you’re asking for permission to access data, such as “Lets you control this accessory with the Apple Home app and Siri across your Apple devices.”
+
+**Don’t require people to create an account or supply personal information.** Instead, defer to HomeKit for any information you might need. If your app provides additional services that require an account, such as cloud services, make account setup optional and wait until after initial HomeKit setup to offer it.
+
+**Honor people’s setup choices.** When people choose to use HomeKit to set up your accessory, don’t force them to set up other platforms during the HomeKit setup flow. A cross-platform setup experience prevents people from using the accessory right away and can cause confusion by presenting too many ways to control the accessory.
+
+**Carefully consider how and when to provide a custom accessory setup experience.** Always begin by presenting the system-provided setup flow. Then, after the accessory’s basic functionality is available, offer a custom post-setup experience that highlights the unique features of your accessory and helps people get the most out of it. For example, a light manufacturer’s app could help people create personalized light scenes in their homes using key colors scanned in from photos in their library.
+
+### [Help people choose useful names](https://developer.apple.com/design/human-interface-guidelines/homekit#Help-people-choose-useful-names)
+
+**Suggest service names that suit your accessory.** If your app detects when someone creates a suboptimal name for Siri voice controls, recommend alternatives that you know will work well for most people. Never suggest company names or model numbers for use as service names.
+
+**Check that the names people provide follow HomeKit naming rules.** If your app lets people rename services, make sure that the new names follow the rules. (The system-provided setup flow automatically checks the original names.) If people enter a name that breaks one or more rules, briefly explain the problem and suggest some alternative names that work. Here are the rules:
+
+ * Use only alphanumeric, space, and apostrophe characters.
+
+ * Start and end with an alphabetic or numeric character.
+
+ * Don’t include emojis.
+
+
+
+
+| Example service names
+---|---
+| Reading lamp
+| 📚 lamp
+| 2nd garage door
+| #2 garage door
+
+**Help people avoid creating names that include location information.** Although it’s natural for someone to use “kitchen light” to name a light in the kitchen, including the room name in the service name can lead to unpredictable results when controlling the accessory by voice. Your app can detect service names that duplicate location information and help people fix them. For example, you might present a post-setup experience that removes the room or zone from a service name and encourages people to assign the accessory to that room or zone instead.
+
+## [Siri interactions](https://developer.apple.com/design/human-interface-guidelines/homekit#Siri-interactions)
+
+HomeKit supports powerful, hands-free control using voice commands. You can help people use Siri to interact with accessories, services, and zones in their home quickly and efficiently.
+
+**Present example voice commands to demonstrate using Siri to control accessories during setup.** As soon as people complete the setup of a new accessory, consider using the service name they chose in a few example Siri phrases and encourage people to try them out.
+
+**After setup, consider teaching people about more complex Siri commands.** People might not be aware of the broad range of natural language phrases they can use with Siri and HomePod to control their accessories. After setup is complete, find useful places throughout your app to help people learn about these types of commands. For example, in a scene detail view, you could tell people, _You can say “Hey Siri, set ‘Movie Time.’”_
+
+In addition to recognizing the names of homes, rooms, zones, services, and scenes, Siri can also use information such as accessory category and characteristic to identify a service. For example, when people use terms like _brighter_ or _dim_ , Siri recognizes that they’re referring to a service that has a brightness characteristic, even if they don’t speak the name of the service.
+
+To illustrate the power and flexibility of Siri commands, here are some examples of the types of phrases that people could use to control their accessories.
+
+Phrase| Siri understands
+---|---
+“Turn on the floor lamp”| Service (_floor lamp_)
+“Show me the entryway camera”| Service (_entryway camera_)
+“Turn on the light”| Accessory category (_light_)
+“Turn off the living room light”| Room (_living room_)
+Accessory category (_light_)
+“Make the living room a little bit brighter”| Room (_living room_)
+Accessory category (implied)
+Brightness characteristic (_brighter_)
+“Turn on the recessed lights”| Service group (_recessed lights_)
+“Turn off the lights upstairs”| Accessory category (_lights_)
+Zone (_upstairs_)
+“Dim the lights in the bedroom and nursery”| Accessory category (_lights_)
+Brightness characteristic (_dim_)
+Rooms (_bedroom_ , _nursery_)
+“Run Good night”| Scene (_Good night_)
+“Is someone in the living room?”| Accessory category (implied)
+Occupancy detection characteristic (implied)
+“Is my security system tripped?”| Accessory category (_security system_)
+“Did I leave the garage door open?”| Accessory category (_garage door_)
+Open characteristic (_open_)
+“Did I forget to turn off the lights in the Tahoe House?”| Accessory category (_lights_)
+Home (_Tahoe House_)
+“It’s dark in here”| Current home (_here_)
+Current room (via HomePod)
+Accessory category (implied)
+
+**Recommend that people create zones and service groups, if they make sense for your accessory.** If people might benefit from using context-specific voice commands to control your accessory, suggest these types of interactions and help people set them up. For example, if you provide an accessory such as a light, switch, or thermostat, you could suggest setting up a zone named “upstairs” or a service group named “media center” to support commands like “Siri, turn off the upstairs lights,” or “Siri, activate the media center.”
+
+**Offer shortcuts only for accessory-specific functionality that HomeKit doesn’t support.** HomeKit lets people use ordinary (or natural) language to control accessories without requiring any additional configuration, so you avoid confusing people by offering shortcuts that duplicate HomeKit functionality. Instead, consider offering shortcuts for complementary functionality that your app provides. For example, if people often want to order filters for an air conditioner that you support, you might offer a shortcut like “Order AC filters.” To learn how to provide phrases that people can use for shortcuts, see [Shortcuts and suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions).
+
+**If your app supports both HomeKit and shortcuts, help people understand the difference between these types of voice control.** People can get confused if they’re presented with multiple methods of voice control. Be sure you clearly indicate what’s possible with shortcuts, and never encourage people to create a shortcut for a scene or action that HomeKit already supports.
+
+## [Custom functionality](https://developer.apple.com/design/human-interface-guidelines/homekit#Custom-functionality)
+
+Your app is a great place to help people appreciate the unique functionality of your accessory. For example, an app for a light that displays different colors could help people create HomeKit scenes using colors imported from their photos.
+
+**Be clear about what people can do in your app and when they might want to use the Home app.** For example, if your app supports only lights, consider encouraging people to create a “Movie Time” scene that not only dims the lights, but also closes the shades, and turns on the TV to a specific input. To do this, first guide people to set up a scene that includes only your accessory’s actions — in this scenario, dimming the lights. Then, your app can suggest that people open the Home app to add their HomeKit-compatible shades and TV to the scene you helped them create. For guidance on how to refer to the Home app, see [Referring to HomeKit](https://developer.apple.com/design/human-interface-guidelines/homekit#Referring-to-HomeKit).
+
+**Defer to HomeKit if your database differs from the HomeKit database.** Give people a seamless experience by automatically reflecting changes made in the Home app or in other third-party HomeKit apps. If you must ask people to manage conflicts in your app, present the conflict visually so that they have a clear picture of the choice they need to confirm. For example, if someone changes an accessory’s service name in the Home app, your app can detect this change and could show both names side by side to confirm that the person wants to use the new name in your app, too.
+
+**Ask permission to update the HomeKit database when people make changes in your app.** You don’t want to surprise people by changing something in the Home app, so it’s essential to get permission or an indication of intent before you write to the database. In particular, never overwrite HomeKit database settings without a person’s explicit direction.
+
+### [Cameras](https://developer.apple.com/design/human-interface-guidelines/homekit#Cameras)
+
+Your app can display still images or streaming video from a connected HomeKit IP camera.
+
+**Don’t block camera images.** It’s fine to supplement the camera’s content with useful features, such as an alert calling attention to potentially interesting activity. However, avoid covering portions of the camera’s images with other content.
+
+**Show a microphone button only if the camera supports bidirectional audio.** A nonfunctioning microphone button takes up valuable display space in your app and risks confusing people.
+
+## [Using HomeKit icons](https://developer.apple.com/design/human-interface-guidelines/homekit#Using-HomeKit-icons)
+
+Use the HomeKit icon in setup or instructional communications related to HomeKit technology.
+
+
+
+In addition, you can use the Apple Home app icon when referencing the Apple Home app or in a button that opens the Apple Home app [product page](https://itunes.apple.com/us/app/home/id1110145103?mt=8) in the App Store.
+
+
+
+**Use only Apple-provided icons.** Don’t create your own HomeKit or Home app icon design or attempt to mimic the Apple-provided designs. Download HomeKit icons in [Resources](https://developer.apple.com/design/resources/).
+
+### [Styles](https://developer.apple.com/design/human-interface-guidelines/homekit#Styles)
+
+You have several options for displaying the HomeKit icon.
+
+#### [Black HomeKit icon](https://developer.apple.com/design/human-interface-guidelines/homekit#Black-HomeKit-icon)
+
+Use the HomeKit icon on white or light backgrounds when other technology icons appear in black.
+
+
+
+#### [White HomeKit icon](https://developer.apple.com/design/human-interface-guidelines/homekit#White-HomeKit-icon)
+
+Use the HomeKit icon on black or dark backgrounds when other technology icons appear in white.
+
+
+
+#### [Custom color HomeKit icon](https://developer.apple.com/design/human-interface-guidelines/homekit#Custom-color-HomeKit-icon)
+
+Use a custom color when other technology icons appear in the same color.
+
+
+
+**Position the HomeKit icon consistently with other technology icons.** When other technology icons are contained within shapes, treat the HomeKit icon in the same manner.
+
+
+
+**Use the HomeKit icon noninteractively.** Don’t use the icon and the name _HomeKit_ in custom interactive elements or buttons. You can use the Apple Home app icon to open the app’s product page in the App Store.
+
+
+
+
+
+
+
+
+
+**Don’t use the HomeKit icon within text or as a replacement for the word HomeKit.** See [Referring to HomeKit](https://developer.apple.com/design/human-interface-guidelines/homekit#Referring-to-HomeKit) to learn how to properly reference HomeKit in text.
+
+
+
+
+
+
+
+
+
+
+
+
+
+**Pair the icon with the name _HomeKit_ correctly.** You can show the name below or beside the icon if other technologies are referenced in this way. Use the same font that’s used on the rest of your layout. For related guidance, see [Referring to HomeKit](https://developer.apple.com/design/human-interface-guidelines/homekit#Referring-to-HomeKit).
+
+Using the icon and name in setup or instructional content
+
+Using the icon and name referencing the Apple Home app
+
+## [Referring to HomeKit](https://developer.apple.com/design/human-interface-guidelines/homekit#Referring-to-HomeKit)
+
+**Emphasize your app over HomeKit.** Make references to HomeKit or Apple Home less prominent than your app name or main identity.
+
+**Adhere to Apple’s trademark guidelines.** Apple trademarks can’t appear in your app name or images. In text, use Apple product names exactly as shown on the [Apple Trademark List](https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html).
+
+ * Use Apple product names in singular form only; do not make Apple product names possessive.
+
+ * Don’t translate Apple, Apple Home, HomeKit, or any other Apple trademark.
+
+ * Don’t use category descriptors. For example, say iPad, not tablet.
+
+ * Don’t indicate any kind of sponsorship, partnership, or endorsement from Apple.
+
+ * Attribute Apple, HomeKit, and all other Apple trademarks with the correct credit lines wherever legal information appears within your app.
+
+ * Refer to Apple devices and operating systems only in technical specifications or compatibility descriptions.
+
+
+
+
+| Example text
+---|---
+| Use HomeKit to turn on your lights from your iPhone or iPad.
+| Use HomeKit to turn on your lights from your iOS devices.
+
+See [Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
+
+### [Referencing HomeKit and the Home app](https://developer.apple.com/design/human-interface-guidelines/homekit#Referencing-HomeKit-and-the-Home-app)
+
+**Use correct capitalization when using the term _HomeKit_.** _HomeKit_ is one word, with an uppercase _H_ and uppercase _K_ , followed by lowercase letters. _Apple Home_ is two words, with an uppercase _A_ and uppercase _H_ , followed by lowercase letters. If your layout displays only all-uppercase designations, _HomeKit_ or _Apple Home_ can be typeset in all uppercase to match the style of the rest of the layout.
+
+**Don’t use the name _HomeKit_ as a descriptor.** Instead use terms like _works with_ , _use_ , _supports_ , or _compatible_.
+
+| Example text
+---|---
+| [Brand] lightbulbs work with HomeKit.
+| HomeKit-enabled thermostat.
+| You can use HomeKit with [App Name].
+| HomeKit lightbulbs.
+
+**Don’t suggest that HomeKit is performing an action or function.**
+
+| Example text
+---|---
+| Back door is unlocked with HomeKit.
+| HomeKit unlocked the back door.
+
+**Use the name _Apple_ with the name _HomeKit_ , if desired.**
+
+| Example text
+---|---
+| Compatible with Apple HomeKit.
+
+**Use the name _HomeKit_ for setup, configuration, and instructions, if desired.**
+
+| Example text
+---|---
+| Open HomeKit settings.
+
+**Use the app name _Apple Home_ whenever referring specifically to the app.** On the first mention of the app in body copy, use the complete name _Apple Home_. Subsequent mentions can refer to the Home app.
+
+| Example text
+---|---
+| Open the Apple Home app.
+| Open the Apple Home app. Your accessory and room will now appear in the Home app.
+| Open Home.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/homekit#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/homekit#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/homekit#Related)
+
+[Apple Design Resources](https://developer.apple.com/design/resources/)
+
+[Guidelines for Using Apple Trademarks and Copyrights](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/homekit#Developer-documentation)
+
+[HomeKit](https://developer.apple.com/documentation/HomeKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/homekit#Videos)
+
+[ Add support for Matter in your smart home app ](https://developer.apple.com/videos/play/wwdc2021/10298)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/homekit#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/icloud.md b/web-app/public/skills/hig-technologies/references/icloud.md
new file mode 100644
index 00000000..99e9ad29
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/icloud.md
@@ -0,0 +1,52 @@
+---
+title: "iCloud | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/icloud
+
+# iCloud
+
+iCloud is a service that lets people seamlessly access the content they care about — photos, videos, documents, and more — from any device, without performing explicit synchronization.
+
+
+
+A fundamental aspect of iCloud is transparency. People don’t need to know where content resides. They can just assume they’re always accessing the latest version.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/icloud#Best-practices)
+
+**Make it easy to use your app with iCloud.** People turn on iCloud in Settings and expect apps to work with it automatically. If you think people might want to choose whether to use iCloud with your app, show a simple option the first time your app opens that provides a choice between using iCloud for all data or not at all.
+
+**Avoid asking which documents to keep in iCloud.** Most people expect all of their content to be available in iCloud and don’t want to manage the storage of individual documents. Consider how your app handles and exposes content, and try to perform more file-management tasks automatically.
+
+**Keep content up to date when possible.** In an app that supports iCloud, it’s best when people always have access to the most recent content. However, you need to balance this experience with respect to device storage and bandwidth constraints. If your app works with very large documents, it may be better to let people control when updated content is downloaded. If your app fits in this category, design a way to indicate that a more recent version of a document is available in iCloud. When a document is updating, provide subtle feedback if the download takes more than a few seconds.
+
+**Respect iCloud storage space.** iCloud is a finite resource for which people pay. Use iCloud to store information people create and understand, and avoid using it for app resources or content you can regenerate. Even if your app doesn’t implement iCloud support, remember that iCloud backups include the contents of every app’s Documents folder. To avoid using up too much space, be picky about the content you place in the Documents folder.
+
+**Make sure your app behaves appropriately when iCloud is unavailable.** If someone manually turns off iCloud or turns on Airplane Mode, you don’t need to display an alert notifying them iCloud is unavailable. However, it may still be helpful to unobtrusively let people know that changes they make won’t be available on other devices until they restore iCloud access.
+
+**Keep app state information in iCloud.** In addition to storing documents and other files, you can use iCloud to store settings and information about the state of your app. For example, a magazine app might store the last page viewed so when the app is opened on another device, someone can continue reading from where they left off. If you use iCloud to store settings, make sure it’s for ones people want applied to all of their devices. For example, some settings might be more useful at work than at home.
+
+**Warn about the consequences of deleting a document.** When someone deletes a document in an app that supports iCloud, the document is removed from iCloud and all other devices too. Show a warning and ask for confirmation before performing the deletion.
+
+**Make conflict resolution prompt and easy.** To the extent possible, try to detect and resolve version conflicts automatically. If this can’t be done, display an unobtrusive notification that makes it easy to differentiate and choose between the conflicting versions. Ideally, conflict resolution occurs as early as possible, so time isn’t wasted in the wrong version.
+
+**Include iCloud content in search results.** People with iCloud accounts assume their content is universally available, and they expect search results to reflect this perspective.
+
+**For games, consider saving player progress in iCloud.** Although you can implement this functionality yourself, the GameSave framework offers an efficient solution. It synchronizes save data across devices and offers built-in alerts you can use to help players handle syncing issues during offline play or when conflicts arise. Alternatively, you can implement custom UI that uses GameSave data to resolve these situations. For developer guidance, see [GameSave](https://developer.apple.com/documentation/GameSave).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/icloud#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/icloud#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/icloud#Developer-documentation)
+
+[CloudKit](https://developer.apple.com/documentation/CloudKit)
+
+[GameSave](https://developer.apple.com/documentation/GameSave)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/icloud#Change-log)
+
+Date| Changes
+---|---
+June 9, 2025| Added guidance for synchronizing game data through iCloud.
+
diff --git a/web-app/public/skills/hig-technologies/references/id-verifier.md b/web-app/public/skills/hig-technologies/references/id-verifier.md
new file mode 100644
index 00000000..a2a7661c
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/id-verifier.md
@@ -0,0 +1,73 @@
+---
+title: "ID Verifier | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/id-verifier
+
+# ID Verifier
+
+ID Verifier lets your iPhone app read mobile IDs in person without requiring external hardware.
+
+
+
+Beginning in iOS 17, you can integrate ID Verifier into your app, letting iPhone read ISO18013-5 compliant mobile IDs and helping you support in-person ID verification. For example, personnel at a concert venue can use your app on iPhone to verify customers’ ages.
+
+Using ID Verifier has advantages for both customers and organizations.
+
+ * Customers only present the minimum data needed to prove their age or identity, without handing over their ID card or showing their device.
+
+ * Apple provides the key components of the certificate issuance, management, and validation process, simplifying app development and enabling a consistent and trusted ID verification experience.
+
+
+
+
+Depending on the needs of your app, you can use ID Verifier to make the following types of requests:
+
+ * **Display Only request.** Use a Display Only request to display data — such as a person’s name or age alongside their photo portrait — within system-provided UI on the requester’s iPhone, so the requester can visually confirm the person’s identity. When you make a Display Only request, the customer’s data remains within the system-provided UI and isn’t transmitted to your app. For developer guidance, see [`MobileDriversLicenseDisplayRequest`](https://developer.apple.com/documentation/ProximityReader/MobileDriversLicenseDisplayRequest).
+
+ * **Data Transfer request.** Use a Data Transfer request only when you have a legal verification requirement and you need to store or process information like a person’s address or date of birth. You must request an additional entitlement to make a Data Transfer request. To learn more, see [Get started with ID Verifier](https://developer.apple.com/wallet/id-verifier/); for developer guidance, see [`MobileDriversLicenseDataRequest`](https://developer.apple.com/documentation/ProximityReader/MobileDriversLicenseDataRequest) and [`MobileDriversLicenseRawDataRequest`](https://developer.apple.com/documentation/ProximityReader/MobileDriversLicenseRawDataRequest).
+
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Best-practices)
+
+**Ask only for the data you need.** People may lose trust in the experience if you ask for more data than you need to complete the current verification. For example, if you need to ensure that a customer is at least a minimum age, use a request that specifies an age threshold; avoid requesting the customer’s current age or birth date. For developer guidance, see [`ageAtLeast(_:)`](https://developer.apple.com/documentation/ProximityReader/MobileDriversLicenseDataRequest/Element/ageAtLeast\(_:\)).
+
+**If your app qualifies for Apple Business Register, register for ID Verifier to ensure that people can view essential information about your organization when you make a request.** Registering for ID Verifier with Apple Business Register lets you provide your official organization name and logo for the system to display on customers’ devices as part of the ID verification UI. To learn if your app qualifies and how to register, see [Apple Business Register](https://register.apple.com/services/login?returnTo=/signin/tap-to-present-id-on-iphone).
+
+**Provide a button that initiates the verification process.** Use a label like Verify Age in a button that performs a simple age check or Verify Identity for a more detailed identity data request. Avoid including a symbol that specifies a particular type of communication, like NFC or QR codes. Never include the Apple logo in any button label.
+
+Button type| Example usage
+---|---
+| An app that checks whether people are old enough to attend an event or access a venue, like a concert hall.
+| An app that verifies whether specific identity information matches expected values, such as name and birth date when picking up a rental car.
+
+**In a Display Only request, help the person using your app provide feedback on the visual confirmation they perform.** For example, when the reader displays the customer’s portrait, you might provide buttons labeled Matches Person and Doesn’t Match Person so your app can receive an approved or rejected value as part of the response.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Platform-considerations)
+
+ _No additional considerations for iOS. Not supported in iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Related)
+
+[Apple Business Register](https://register.apple.com/services/login?returnTo=/signin/tap-to-present-id-on-iphone)
+
+[IDs in Wallet](https://learn.wallet.apple/id)
+
+[Identity verification](https://developer.apple.com/design/human-interface-guidelines/wallet#Identity-verification)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Developer-documentation)
+
+[Adopting the Verifier API in your iPhone app](https://developer.apple.com/documentation/ProximityReader/adopting-the-verifier-api-in-your-iphone-app) — ProximityReader
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Videos)
+
+[ What’s new in Wallet and Apple Pay ](https://developer.apple.com/videos/play/wwdc2023/10114)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/id-verifier#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| New page.
+
diff --git a/web-app/public/skills/hig-technologies/references/imessage-apps-and-stickers.md b/web-app/public/skills/hig-technologies/references/imessage-apps-and-stickers.md
new file mode 100644
index 00000000..1a50b0e1
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/imessage-apps-and-stickers.md
@@ -0,0 +1,105 @@
+---
+title: "iMessage apps and stickers | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers
+
+# iMessage apps and stickers
+
+An iMessage app can help people share content, collaborate, and even play games with others in a conversation; stickers are images that people can use to decorate a conversation.
+
+
+
+An iMessage app or sticker pack is available within the context of a Messages conversation and also in effects in both Messages and FaceTime. You can create an iMessage app or sticker pack as a standalone app or as an app extension within your iOS or iPadOS app. For developer guidance, see [Messages](https://developer.apple.com/documentation/Messages) and [Adding Sticker packs and iMessage apps to the system Stickers app, Messages camera, and FaceTime](https://developer.apple.com/documentation/Messages/adding-sticker-packs-and-imessage-apps-to-the-system-stickers-app-messages-camera-and-facetime).
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Best-practices)
+
+**Prefer providing one primary experience in your iMessage app.** People are in a conversational flow when they choose your app, so your functionality or content needs to be easy to understand and immediately available. If you want to provide multiple types of functionality or different collections of content, consider creating a separate iMessage app for each one.
+
+**Consider surfacing content from your iOS or iPadOS app.** For example, your iMessage app could offer app-specific information that people might want to share — such as a shopping list or a trip itinerary — or support a simple, collaborative task, like deciding where to go for a meal or which movie to watch.
+
+**Present essential features in the compact view.** People can experience your iMessage app in a compact view that appears below the message transcript, or they can expand the view to occupy most of the window. Make sure the most frequently used items are available in the compact view, reserving additional content and features for the expanded view.
+
+**In general, let people edit text only in the expanded view.** The compact view occupies roughly the same space as the keyboard. To ensure that the iMessage app’s content remains visible while people edit, display the keyboard in the expanded view.
+
+**Create stickers that are expressive, inclusive, and versatile.** Whether your stickers are rich, static images or short animations, make sure that each one remains legible against a wide range of backgrounds and when rotated or scaled. You can also use transparency to help people visually integrate a sticker with text, photos, and other stickers.
+
+**For each sticker, provide a localized alternative description.** VoiceOver can help people use your sticker pack by speaking a sticker’s alternative description.
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Specifications)
+
+### [Icon sizes](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Icon-sizes)
+
+The icon for an iMessage app or sticker pack can appear in Messages, the App Store, notifications, and Settings. After people install your iMessage app or sticker pack, its icon also appears in the app drawer in the Messages app.
+
+You supply a square-cornered icon for each extension you offer, and the system automatically applies a mask that rounds the corners.
+
+To ensure that your icon looks great in any context and on various devices, create a square-cornered icon in the following sizes:
+
+Usage| @2x (pixels)| @3x (pixels)
+---|---|---
+Messages, notifications| 148x110| -
+| 143x100| -
+| 120x90| 180x135
+| 64x48| 96x72
+| 54x40| 81x60
+Settings| 58x58| 87x87
+App Store| 1024x1024| 1024x1024
+
+### [Sticker sizes](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Sticker-sizes)
+
+Messages supports small, regular, and large stickers. Pick the size that works best for your content and prepare all of your stickers at that size; don’t mix sizes within a single sticker pack. Messages displays stickers in a grid, organized differently for different sizes.
+
+
+
+Small
+
+
+
+Regular
+
+
+
+Large
+
+Create your sticker images using the following @3x dimensions for the sticker size you chose. If necessary, the system generates @2x and @1x versions by downscaling the images at runtime. For developer guidance, see [`MSStickerSize`](https://developer.apple.com/documentation/Messages/MSStickerSize).
+
+Sticker size| @3x dimensions (pixels)
+---|---
+Small| 300x300
+Regular| 408x408
+Large| 618x618
+
+A sticker file must be 500 KB or smaller in size. For each supported format, the table below provides guidance for using transparency and animation.
+
+Format| Transparency| Animation
+---|---|---
+PNG| 8-bit| No
+APNG| 8-bit| Yes
+GIF| Single-color| Yes
+JPEG| No| No
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Related)
+
+[iMessage Apps and Stickers](https://developer.apple.com/imessage/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Developer-documentation)
+
+[Messages](https://developer.apple.com/documentation/Messages)
+
+[Adding Sticker packs and iMessage apps to the system Stickers app, Messages camera, and FaceTime](https://developer.apple.com/documentation/Messages/adding-sticker-packs-and-imessage-apps-to-the-system-stickers-app-messages-camera-and-facetime) — Messages
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Videos)
+
+[ Express Yourself! ](https://developer.apple.com/videos/play/wwdc2017/820)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/imessage-apps-and-stickers#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/in-app-purchase.md b/web-app/public/skills/hig-technologies/references/in-app-purchase.md
new file mode 100644
index 00000000..e33da769
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/in-app-purchase.md
@@ -0,0 +1,263 @@
+---
+title: "In-app purchase | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/in-app-purchase
+
+# In-app purchase
+
+People can use in-app purchase to pay for virtual goods — like premium content, digital goods, and subscriptions — securely within your app.
+
+
+
+You can also promote and offer in-app purchases directly through the App Store. For developer guidance, see [In-App Purchase](https://developer.apple.com/documentation/StoreKit/in-app-purchase).
+
+Tip
+
+In-app purchase and [Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay) are different technologies that support different use cases. Use in-app purchase to sell virtual goods in your app, such as premium content for your app and subscriptions for digital content. Use Apple Pay in your app to sell physical goods like groceries, clothing, and appliances; for services such as club memberships, hotel reservations, and event tickets; and for donations.
+
+Using in-app purchase, there are four types of content you can offer:
+
+ * _Consumable_ content like lives or gems in a game. After purchase, consumable content depletes as people use it, and people can purchase it again.
+
+ * _Non-consumable_ content like premium features in an app. Purchased non-consumable content doesn’t expire.
+
+ * _Auto-renewable subscriptions_ to virtual content, services, and premium features in your app on an ongoing basis. An auto-renewable subscription continues to automatically renew at the end of each subscription period until people choose to cancel it.
+
+ * _Non-renewing subscriptions_ to a service or content that lasts for a limited time, like access to an in-game battle pass. People purchase a non-renewing subscription each time they want to extend their access to the service or content.
+
+
+
+
+
+
+For marketing and business guidance, see [In-app purchase](https://developer.apple.com/in-app-purchase/) and [Auto-renewable subscriptions](https://developer.apple.com/app-store/subscriptions/). For information about what you can and can’t sell in your app, including in-app purchase usage requirements and restrictions, see [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/).
+
+Note
+
+For apps with exceptionally large, frequently updated catalogs of one-time purchases or subscription content from multiple creators, or apps that provide subscriptions with optional add-on content as a single purchase within the app, the Advanced Commerce API allows you to manage your In-App Purchase catalog directly. See the Advanced Commerce API [App Store support page](https://developer.apple.com/in-app-purchase/advanced-commerce-api/) for an overview, and see [Advanced Commerce API](https://developer.apple.com/documentation/AdvancedCommerceAPI) for developer guidance.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Best-practices)
+
+**Let people experience your app before making a purchase.** People may be more inclined to invest in paid items or features after they’ve enjoyed your app and discovered its value. If you offer auto-renewable subscriptions, consider supporting limited free access to your content; for guidance, see [Auto-renewable subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Auto-renewable-subscriptions).
+
+**Design an integrated shopping experience.** You don’t want people to think they’ve entered a different app when they browse and purchase your digital products. Present products and handle transactions in ways that mirror the style of your app.
+
+**Use simple, succinct product names and descriptions.** Titles that don’t truncate or wrap and plain, direct language can help people find products quickly.
+
+**Display the total billing price for each in-app purchase you offer, regardless of type.** People need to know the total billing amount for every purchase they consider.
+
+**Display your store only when people can make payments.** If someone canʼt make payments — for example, because of parental restrictions — consider hiding your store or displaying UI that explains why the store isnʼt available. For developer guidance, see [`canMakePayments`](https://developer.apple.com/documentation/StoreKit/AppStore/canMakePayments).
+
+**Use the default confirmation sheet.** When someone initiates an in-app purchase, the system displays a confirmation sheet to help prevent accidental purchases. Don’t modify or replicate this sheet.
+
+### [Supporting Family Sharing](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Supporting-Family-Sharing)
+
+People can use Family Sharing to share access to their purchased content — such as auto-renewable subscriptions and non-consumable in-app purchases — with up to five additional family members, across all their Apple devices. To encourage people to take advantage of the Family Sharing support you offer, consider the following guidelines.
+
+**Prominently mention Family Sharing in places where people learn about the content you offer.** For example, including “Family” or “Shareable” in a subscription or item name and referring to Family Sharing in your sign-up screen can highlight the feature and help people make an informed choice.
+
+**Help people understand the benefits of Family Sharing and how to participate.** When you turn on Family Sharing, people can receive notifications about the change, depending on their current settings. For example, an existing subscriber whose sharing setting is turned off (the default) receives a notice from Apple that invites them to share their subscription with family members. Similarly, a family member can get a notification about content that’s being shared with them. (To learn more about the types of notifications people can receive, see [Auto-renewable subscriptions](https://developer.apple.com/app-store/subscriptions/).)
+
+**Aim to customize your in-app messaging so that it makes sense to both purchasers and family members.** For example, when a family member views shared content for the first time, you might welcome them with wording like “Your family subscription includes…”.
+
+### [Providing help with in-app purchases](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Providing-help-with-in-app-purchases)
+
+Sometimes, people need help with a purchase or want to request a refund. To help make this experience convenient, you can present custom UI within your app that provides assistance, offers alternative solutions, and helps people initiate the system-provided refund flow. For developer guidance, see [`beginRefundRequest(for:in:)`](https://developer.apple.com/documentation/StoreKit/Transaction/beginRefundRequest\(for:in:\)-65tph); for related guidance specific to auto-renewable subscriptions, see [Helping people manage their subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Helping-people-manage-their-subscriptions).
+
+**Provide help that customers can view before they request a refund.** In addition to including a link to the system-provided refund flow, your custom purchase-help screen can provide assistance you tailor to your app. For example, your custom screen might help people resolve problems with missing purchases, answer frequently asked questions about the in-app purchases you offer, and give people ways to submit feedback or contact you directly for support.
+
+
+
+**Use a simple title for the refund action, like “Refund” or “Request a Refund”.** The system-provided refund flow makes it clear that people request a refund from Apple, so there’s no need to reiterate this information.
+
+**Help people find the problematic purchase.** For each recent purchase you display, include contextual information that helps people identify the one they want. For example, you might display an image of the product — along with its name and description — and list the original purchase date.
+
+
+
+**Consider offering alternative solutions.** For example, if the customer didn’t receive the item they purchased, you might offer immediate fulfillment or a conciliatory item. Regardless of the alternatives you offer, make it clear that people can still request a refund.
+
+**Make it easy for people to request a refund.** Although your purchase-help screen can offer useful information and alternative solutions, make sure this content doesn’t create a barrier to requesting a refund. For example, avoid making people scroll or open another screen to reveal your refund-request button. When people choose your refund-request item, they automatically enter the system-provided refund flow shown below.
+
+
+
+
+
+**Avoid characterizing or providing guidance on Apple’s refund policies.** For example, don’t speculate about whether customers will receive the refund they request. To help people understand the refund-request process, you can provide a link to [Request a refund for apps or content that you bought from Apple](https://support.apple.com/en-us/HT204084).
+
+## [Auto-renewable subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Auto-renewable-subscriptions)
+
+**Call attention to subscription benefits during onboarding.** By showing the value of your subscription when people first launch your app, you can educate them on how the app works and help them understand what they’ll gain by subscribing. Include a strong call to action and a clear summary of subscription terms (see [Making signup effortless](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Making-signup-effortless)). For related guidance, see [Onboarding](https://developer.apple.com/design/human-interface-guidelines/onboarding).
+
+
+
+**Offer a range of content choices, service levels, and durations.** People appreciate the flexibility to choose the subscription that best meets their needs.
+
+**Consider letting people try your content for free before signing up.** Limited free access gives people the opportunity to sample your content and encourages people who already engaged with your content to sign up. For example, you might offer a freemium app, a metered paywall, or a free trial.
+
+ * Freemium app
+ * Metered paywall
+ * Free trial
+
+
+
+
+
+
+
+
+
+**Prompt people to subscribe at relevant times, like when they near their monthly limit of free content.** Additionally, consider making it easy for people to subscribe at any time by including prompts at relevant points throughout your app.
+
+**Encourage a new subscription only when someone isn’t already a subscriber.** Otherwise, people may believe their existing subscription has lapsed when that’s not actually the case. If you offer the same subscription options in multiple apps or through your website, provide a sign-in option so people don’t think they have to pay multiple times for the same service.
+
+### [Making signup effortless](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Making-signup-effortless)
+
+A simple and informative sign-up experience makes it easy for people to act on their interest in your content, whether they’re in your app or viewing your App Store product page.
+
+**Provide clear, distinguishable subscription options.** Use short, self-explanatory names that differentiate subscription options from one another, and specify the price and duration for each option. If you offer an introductory price, be sure to list the introductory price, the duration of the offer, and the standard price the customer pays after the offer ends.
+
+**Simplify initial signup by asking only for necessary information.** A lengthy sign-up process may lower your subscription conversion rate. Defer asking for additional information until after people have signed up.
+
+**In your tvOS app, help people sign up or authenticate using another device.** Instead of asking people to input information in your tvOS app, send a code to another device where they can enter the information you need.
+
+**Give people more information in your app’s sign-up screen.** In addition to including links to your Terms of Service and Privacy Policy in your app and App Store metadata, the in-app sign-up screen needs to include:
+
+ * The subscription name, duration, and the content or services provided during each subscription period
+
+ * The billing amount, correctly localized for the territories and currencies where the subscription is available for purchase
+
+ * A way for existing subscribers to sign in or restore purchases
+
+
+
+
+For example, the Forest Explorer sign-up screen displays billing totals for monthly, biannual, and annual subscriptions in the most prominent positions. In subordinate positions, it shows breakdowns of the biannual and annual prices, so that people can compare the values and make an informed choice. The sign-up screen also contains a button that existing subscribers can use to restore their purchases.
+
+
+
+**Clearly describe how a free trial works.** It’s particularly important to make sure people know that when the free trial is over, a payment will be automatically initiated for the next subscription period. For example, the Ocean Journal sign-up screen explicitly states both the duration of the free trial and the amount that’s billed when it ends.
+
+
+
+**Include a sign-up opportunity in your app’s settings.** App and account settings are common places for people to look for a way to subscribe.
+
+### [Supporting offer codes](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Supporting-offer-codes)
+
+In iOS and iPadOS, subscription offer codes let you use both online and offline channels to give new, existing, and lapsed subscribers free or discounted access to your subscription content. For example, you might provide offer codes through email, give them out at a store or event, or print one on a physical product.
+
+There are two types of offer codes you can support:
+
+ * A _one-time use code_ is a unique code you generate in App Store Connect. People can redeem a one-time use code through a [redemption URL](https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-offer-codes/#distribute-offer-codes) (a shareable link), within your app (when you support redemption), or by entering it in the App Store, where they’re prompted to install your app if they haven’t already. Consider using one-time use codes when your distribution is small or when you need to restrict access to a code.
+
+ * A _custom code_ is a code you create, such as NEWYEAR or SPRINGSALE. People can redeem a custom code through a redemption URL or within your app (when you support redemption). Consider using a custom code when you want to support a large campaign that requires a mass distribution of codes.
+
+
+
+
+For developer guidance on implementing offer codes, see [Offer codes](https://developer.apple.com/documentation/storekit/implementing-offer-codes-in-your-app) and [Set up offer codes](https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-offer-codes). For guidance on other types of offers, see [Providing subscription offers](https://developer.apple.com/app-store/subscriptions/#providing-subscription-offers).
+
+**Clearly explain offer details.** To help people make an informed decision, provide a straightforward and succinct description of your offer in your marketing materials.
+
+**Follow guidelines for creating a custom code.** A custom code can contain only alphanumeric ASCII characters. Don’t use special characters, including Chinese and Arabic characters.
+
+**Tell people how to redeem a custom code.** Because people can’t redeem a custom code by entering it in their App Store account settings, it’s important to let them know that they can redeem it through a redemption URL or within your app.
+
+**Consider supporting offer redemption within your app.** The system automatically provides screens that present the offer-redemption flow, whether people redeem the offer in your app or in the App Store. When you use StoreKit API to let people redeem offer codes within your app, the only custom UI you need to create is one that initiates the system-provided flow. For developer guidance, see [`presentOfferCodeRedeemSheet(in:)`](https://developer.apple.com/documentation/StoreKit/AppStore/presentOfferCodeRedeemSheet\(in:\)) and [`offerCodeRedemption(isPresented:onCompletion:)`](https://developer.apple.com/documentation/SwiftUI/View/offerCodeRedemption\(isPresented:onCompletion:\)). There are several natural places to provide this custom UI. For example, you could add a “Redeem Code” button to your paywall, onboarding screens, or your app’s settings screen.
+
+
+
+
+
+After people tap your custom redeem button, the system automatically provides a series of code-redemption screens like the ones shown below.
+
+
+
+
+
+**Supply an engaging and informative promotional image.** Creating this optional image can help people understand the value of your content. If you don’t supply a promotional image, the code redemption screens use your app icon by default. To learn more, see [Promoting your in-app purchases](https://developer.apple.com/app-store/promoting-in-app-purchases/).
+
+**Help people benefit from unlocked content as soon as they complete the redemption flow.** Think about ways to align the post-redemption experience in your app with the subscriber’s new status. For example, you might provide a welcome experience for new subscribers or a brief tour of new features for an existing subscriber who’s unlocked additional functionality. In particular, be prepared to welcome people who subscribe before they open your app for the first time. For example, if you require people to create an account or sign in before they can use your app, make this process as smooth as possible for new subscribers who haven’t experienced it before.
+
+### [Helping people manage their subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Helping-people-manage-their-subscriptions)
+
+Supporting subscription management means people can upgrade, downgrade, or cancel a subscription without leaving your app. Offering subscription management within your app also gives you a natural place to provide help for common subscriber issues and present alternative offers for people to consider.
+
+
+
+**Provide summaries of the customer’s subscriptions.** In particular, people appreciate viewing the upcoming renewal date without having to search for it. Consider displaying this information in a settings or account screen, near the subscription-management option. For developer guidance, see [`Product.SubscriptionInfo`](https://developer.apple.com/documentation/StoreKit/Product/SubscriptionInfo).
+
+**Consider using the system-provided subscription-management UI.** Using StoreKit APIs lets you present a consistent experience that helps people manage or cancel their subscriptions without leaving your app. For developer guidance, see [`showManageSubscriptions(in:)`](https://developer.apple.com/documentation/StoreKit/AppStore/showManageSubscriptions\(in:\)).
+
+
+
+
+
+**Consider ways to encourage a subscriber to keep their subscription or resubscribe later.** When you use StoreKit APIs, your app is notified when someone chooses to cancel their subscription. In this scenario, you might want to extend a personalized offer as an alternative to cancellation or invite people to describe their reasons for canceling in an exit survey. In addition to giving you insights into various customer problems, survey feedback can also help inform messaging for retention and win-back strategies.
+
+
+
+**Always make it easy for customers to cancel an auto-renewable subscription.** If the manage subscription action is deep within an app — or hard to recognize — subscribers can feel they’re being discouraged or prevented from canceling.
+
+**Consider creating a branded, contextual experience to complement the system-provided management UI.** Within your custom UI, you might offer a popular premium tier or provide personalized suggestions for alternative plans based on what you know about the customer’s preferences or how they use your app. For example, you can create a promotional offer that provides a discounted price for a specific period of time. You might also consider subscription [offer codes](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Supporting-offer-codes) to help you win back lapsed subscribers and encourage existing subscribers to upgrade.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#watchOS)
+
+The sign-up screen in your watchOS app needs to display the same set of information about your subscription options that you display in other versions of your app. For the complete list of required items, see [Making signup effortless](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Making-signup-effortless). The following guidelines can help you design a sign-up screen that feels at home on Apple Watch.
+
+**Clearly describe the differences between versions of your app that run on different devices.** If your watchOS app supports different functionality or provides a subset of the content that’s available on other devices, be sure to clarify these differences in your description. Be straightforward about the advantages of accessing subscription content through your watchOS app without implying that the experience is identical to the ones in other versions of your app.
+
+
+
+A description that might lead people to expect access to 90,000 maps on their Apple Watch
+
+
+
+A description that clarifies how the subscription works on Apple Watch in contrast with other devices
+
+**Consider using a modal sheet to display the required information.** After people respond to your call to action to learn more about your subscription offers, you can use a modal sheet to present all required items in a single view. Even though people must scroll the view to access all the information, displaying it in a modal sheet helps your app UI remain streamlined and concise. Also, a modal sheet’s default Close button makes it easy for people to return to your free content with one tap. If you create a custom sign-up view instead of using a modal sheet, design a complete, efficient flow and include a Close or Cancel button that lets people return to your free content.
+
+**Make subscription options easy to compare on a small screen.** People need to understand the terms of each subscription option before they can choose one. Aim to display the duration and discount information for each option in a compact way that’s easy to scan and compare. Here are two ways you might present subscription options in your watchOS app:
+
+ * Display each option in a separate button. Using one button per payment option lets people start the signup process with one tap. In this design, it’s important to lock up each button with its description so that people can see how these elements are related, especially while scrolling.
+
+ * Display a list of options, followed by a button people tap to start the signup process. Using a list to display one option per row gives you a compact design that minimizes scrolling while making subscription choices easy to scan and understand. In this design, the button’s title can update to reflect the chosen option.
+
+
+
+
+
+
+One payment option per button
+
+
+
+One payment option per list row, followed by a button that updates to display the chosen option
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Related)
+
+[In-App Purchase](https://developer.apple.com/in-app-purchase/)
+
+[Offering Subscriptions](https://developer.apple.com/app-store/subscriptions/)
+
+[App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Developer-documentation)
+
+[In-App Purchase](https://developer.apple.com/documentation/StoreKit/in-app-purchase) — StoreKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Videos)
+
+[ What’s new in StoreKit and In-App Purchase ](https://developer.apple.com/videos/play/wwdc2024/10061)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Updated artwork and guidance for redeeming offer codes.
+November 3, 2022| Added a guideline for displaying the total billing price for every in-app purchase item and consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/live-photos.md b/web-app/public/skills/hig-technologies/references/live-photos.md
new file mode 100644
index 00000000..c10517ea
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/live-photos.md
@@ -0,0 +1,54 @@
+---
+title: "Live Photos | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/live-photos
+
+# Live Photos
+
+Live Photos lets people capture favorite memories in a sound- and motion-rich interactive experience that adds vitality to traditional still photos.
+
+
+
+When Live Photos is available, the Camera app captures additional content — including audio and extra frames — before and after people take a photo. People press a Live Photo to see it spring to life.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/live-photos#Best-practices)
+
+**Apply adjustments to all frames.** If your app lets people apply effects or adjustments to a Live Photo, make sure those changes are applied to the entire photo. If you don’t support this, give people the option of converting it to a still photo.
+
+**Keep Live Photo content intact.** It’s important for people to experience Live Photos in a consistent way that uses the same visual treatment and interaction model across all apps. Don’t disassemble a Live Photo and present its frames or audio separately.
+
+**Implement a great photo sharing experience.** If your app supports photo sharing, let people preview the entire contents of Live Photos before deciding to share. Always offer the option to share Live Photos as traditional photos.
+
+**Clearly indicate when a Live Photo is downloading and when the photo is playable.** Show a progress indicator during the download process and provide some indication when the download is complete.
+
+**Display Live Photos as traditional photos in environments that don’t support Live Photos.** Don’t attempt to replicate the Live Photos experience provided in a supported environment. Instead, show a traditional, still representation of the photo.
+
+**Make Live Photos easily distinguishable from still photos.** The best way to identify a Live Photo is through a hint of movement. Because there are no built-in Live Photo motion effects, like the one that appears as you swipe through photos in the full-screen browser of Photos app, you need to design and implement custom motion effects.
+
+In cases where movement isn’t possible, show a system-provided badge above the photo, either with or without text. Never include a playback button that a viewer can interpret as a video playback button.
+
+
+
+
+
+**Keep badge placement consistent.** If you show a badge, put it in the same location on every photo. Typically, a badge looks best in a corner of a photo.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/live-photos#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or tvOS. Not supported in watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/live-photos#visionOS)
+
+In visionOS, people can view a Live Photo, but they can’t capture one.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/live-photos#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/live-photos#Developer-documentation)
+
+[`PHLivePhoto`](https://developer.apple.com/documentation/Photos/PHLivePhoto) — PhotoKit
+
+[LivePhotosKit JS](https://developer.apple.com/documentation/LivePhotosKitJS) — LivePhotosKit JS
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/live-photos#Videos)
+
+[ What’s new in camera capture ](https://developer.apple.com/videos/play/wwdc2021/10047)
+
diff --git a/web-app/public/skills/hig-technologies/references/mac-catalyst.md b/web-app/public/skills/hig-technologies/references/mac-catalyst.md
new file mode 100644
index 00000000..2692d814
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/mac-catalyst.md
@@ -0,0 +1,216 @@
+---
+title: "Mac Catalyst | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/mac-catalyst
+
+# Mac Catalyst
+
+When you use Mac Catalyst to create a Mac version of your iPad app, you give people the opportunity to enjoy the experience in a new environment.
+
+
+
+## [Before you start](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Before-you-start)
+
+Many iPad apps are great candidates for creating a Mac app built with Mac Catalyst. This is especially true for apps that already work well on iPad and support key iPad features, such as:
+
+**Drag and drop.** When you support drag and drop in your iPad app, you also get support for drag and drop in the Mac version.
+
+**Keyboard navigation and shortcuts.** Even though a physical keyboard may not always be available on iPad, iPad users appreciate using the keyboard to navigate and keyboard shortcuts to streamline their interactions. On the Mac, people expect apps to offer both keyboard navigation and shortcuts.
+
+**Multitasking.** Apps that do a good job scaling the interface to support Split View, Slide Over, and Picture in Picture lay the necessary groundwork to support the extensive window resizability that Mac users expect.
+
+**Multiple windows**. By supporting multiple scenes on iPad, you also get support for multiple windows in the macOS version of your app.
+
+Although great iPad apps can provide a solid foundation for creating a Mac app built with Mac Catalyst, some apps rely on frameworks or features that don’t exist on a Mac. For example, if the essential features of your experience require capabilities like gyroscope, accelerometer, or rear camera, frameworks like HealthKit or ARKit, or if the primary function you offer is something like marking, handwriting, or navigation, your app might not be suitable for the Mac.
+
+Creating a Mac version of your iPad app with Mac Catalyst gives the app automatic support for fundamental macOS features such as:
+
+ * Pointer interactions and keyboard-based focus and navigation
+
+ * Window management
+
+ * Toolbars
+
+ * Rich text interaction, including copy and paste as well as contextual menus for editing
+
+ * File management
+
+ * Menu bar menus
+
+ * App-specific settings in the system-provided Settings app
+
+
+
+
+System-provided UI elements take on a more Mac-like appearance, too; for example:
+
+ * Split view
+
+ * File browser
+
+ * Activity view
+
+ * Form sheet
+
+ * Contextual actions
+
+ * Color picker
+
+
+
+
+To learn more about the characteristics that distinguish the Mac experience, see [Designing for macOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos). For developer guidance, see [Mac Catalyst](https://developer.apple.com/documentation/UIKit/mac-catalyst).
+
+Developer note
+
+To discover how views and controls can change when you create a Mac app using Mac Catalyst, download [UIKit Catalog: Creating and customizing views and controls](https://developer.apple.com/documentation/UIKit/uikit-catalog-creating-and-customizing-views-and-controls) and build the macOS target.
+
+## [Choose an idiom](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Choose-an-idiom)
+
+When you first create your Mac app using Mac Catalyst, Xcode defaults to the “Scale Interface to Match iPad” setting, or _iPad idiom_. With this setting, the system ensures that your Mac app appears consistent with the macOS display environment without requiring significant changes to the app’s layout. However, text and graphics may appear slightly less detailed because iPadOS views and text scale down to 77% in macOS when you use the iPad idiom. For example, the system scales text that uses the iPadOS baseline font size of 17pt down to 13pt in macOS.
+
+When your app feels at home on the Mac using the iPad idiom, consider switching to the _Mac idiom_. With this setting, text and artwork render in more detail, some interface elements and views take on an even more Mac-like appearance, and graphics-intensive apps may see improved performance and lower power consumption.
+
+You’re most likely to benefit from the Mac idiom if your app displays a lot of text, detailed artwork, or animations, but choosing this idiom can also mean that you need to spend additional time updating your Mac app’s layout, text, and images.
+
+**When you adopt the Mac idiom, thoroughly audit your app’s layout, and plan to make changes to it.** To help with this effort, consider using a separate asset catalog to contain your Mac app’s assets instead of reusing the asset catalog that contains your iPad app’s assets.
+
+**Adjust font sizes as needed.** With the Mac idiom, text renders at 100% of its configured size, which can appear too large without adjustment. When possible, use text styles and avoid fixed font sizes.
+
+**Make sure views and images look good in the Mac version of your app.** With the Mac idiom, iPadOS views render at 100% of their size, making them appear more detailed. To help you visualize the difference, consider the two depictions of an image asset shown below. One version illustrates how the asset appears when you use the iPad idiom, and the other version shows how the asset appears when you adopt the Mac idiom. Both depictions are zoomed in to show how the image renders with more details when you use the Mac idiom.
+
+ * iPad idiom
+ * Mac idiom
+
+
+
+
+
+
+
+Developer note
+
+When you adopt the Mac idiom, the unscaled views and interface elements report different metrics, often resulting in a significant amount of additional work. To reduce the amount of work, avoid using fixed font, view, or layout sizes. For developer guidance, see [Choosing a user interface idiom for your Mac app](https://developer.apple.com/documentation/UIKit/choosing-a-user-interface-idiom-for-your-mac-app).
+
+**Limit your appearance customizations to standard macOS appearance customizations that are the same or similar to those available in iPadOS.** Not all appearance customizations available to iPadOS controls are available to macOS controls.
+
+## [Integrate the Mac experience](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Integrate-the-Mac-experience)
+
+When you use Mac Catalyst to create a Mac version of your iPad app, you need to ensure that your Mac app gives people a rich Mac experience. Regardless of the idiom you choose, it’s essential to go beyond simply displaying your iPadOS layout in a macOS window.
+
+iPadOS and macOS each define patterns and conventions that are rooted in the different ways people use their devices. Before you dive in and update specific views and controls, become familiar with the main differences between the platforms so you can create a great Mac app.
+
+### [Navigation](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Navigation)
+
+Many iPad and Mac apps organize data in similar ways, but they use different controls and visual indicators to help people understand and navigate through the data.
+
+Typically, iPad apps use the following components to organize their content and features:
+
+ * [Split views](https://developer.apple.com/design/human-interface-guidelines/split-views). A split view supports hierarchical navigation, which consists of a two- or three-column interface that shows a primary column, an optional supplementary column, and a secondary pane of content. Frequently, apps use the primary column to create a sidebar-based interface where changes in the sidebar drive changes in the optional supplementary column, which then affect the content in the content pane.
+
+ * [Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars). A tab bar supports flat navigation by displaying top-level categories in a persistent bar at the bottom of the screen.
+
+ * [Page controls](https://developer.apple.com/design/human-interface-guidelines/page-controls). A page control displays dots at the bottom of the screen that indicate the position of the current page in a flat list of pages.
+
+
+
+
+If you use a tab bar in your iPad app, consider using a split view with a sidebar or a segmented control. Both items are similar to macOS navigation conventions. To choose between a split view or a segmented control, consider the following:
+
+ * A split view with a sidebar displays a list of top-level items, each of which can disclose a list of child items. Using a sidebar streamlines navigation, because each tab’s contents are available within the sidebar. By using a sidebar on both iPad and Mac, you create a consistent layout that makes it easy for iPad users to start using the Mac version of your app.
+
+ * A segmented control and a tab bar both accommodate similar interactions, such as mutually exclusive selection. In general, using a split view instead of a tab bar works better than using a segmented control. However, a segmented control can work well on the Mac if your app uses a flat navigation hierarchy.
+
+
+
+
+**Make sure people retain access to important tab-bar items in the Mac version of your app.** Regardless of whether you use a split view or a segmented control instead of a tab bar in your iPad app, be sure to give people quick access to top-level items by listing them in the macOS View menu.
+
+**Offer multiple ways to move between pages.** Mac users — especially those who interact using a pointing device or only the keyboard — appreciate Next and Previous buttons in addition to iPad or trackpad gestures that let them swipe between pages.
+
+### [Inputs](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Inputs)
+
+Although both iPad and Mac accept user input from a range of devices — such as keyboard, mouse, and trackpad — touch interactions are the basis for iPadOS conventions. In contrast, keyboard and mouse interactions inform most macOS conventions.
+
+Most iPadOS gestures convert automatically when you create your Mac app using Mac Catalyst; for example:
+
+iPadOS gesture…| Translates to mouse interaction
+---|---
+Tap| Left or right click
+Touch and hold| Click and hold
+Pan| Left click and drag
+
+iPadOS gesture…| Translates to trackpad gesture
+---|---
+Tap| Click
+Touch and hold| Click and hold
+Pan| Click and drag
+Pinch| Pinch
+Rotate| Rotate
+
+Developer note
+
+The system sends the two touches in the pinch and rotate gestures to the view under the pointer, not the view under each touch.
+
+### [App icons](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#App-icons)
+
+**Create a macOS version of your app icon.** Great macOS app icons showcase the lifelike rendering style that people expect in macOS while maintaining a harmonious experience across all platforms.
+
+### [Layout](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Layout)
+
+To take advantage of the wider Mac screen in ways that give Mac users a great experience, consider updating your layout in the following ways:
+
+ * Divide a single column of content and actions into multiple columns.
+
+ * Use the regular-width and regular-height size classes, and consider reflowing elements in the content area to a side-by-side arrangement as people resize the window.
+
+ * Present an inspector UI next to the main content instead of using a popover.
+
+
+
+
+**Consider moving controls from the main UI of your iPad app to your Mac app’s toolbar.** Be sure to list the commands associated with these controls in the menus of your Mac app’s menu bar.
+
+**As much as possible, adopt a top-down flow.** Mac apps place the most important actions and content near the top of the window. If your iPad app provides controls in a toolbar, put these controls in the window toolbar of the macOS version of your app.
+
+**Relocate buttons from the side and bottom edges of the screen.** On iPad, placing buttons on these screen edges can help people reach them, but on a Mac, this ergonomic consideration doesn’t apply. You may want to relocate these controls to other areas or put them in the toolbar of your macOS window.
+
+### [Menus](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Menus)
+
+Mac users are familiar with the persistent menu bar and expect to find all of an app’s commands in it. In contrast, iPadOS doesn’t have a persistent menu bar, and iPad users expect to find app commands within the app’s UI or in the shortcut interface that displays when they hold the Command key on a connected keyboard.
+
+Developer note
+
+To support keyboard shortcuts for menu commands, use [`UIKeyCommand`](https://developer.apple.com/documentation/UIKit/UIKeyCommand). For developer guidance, see [Adding menus and shortcuts to the menu bar and user interface](https://developer.apple.com/documentation/UIKit/adding-menus-and-shortcuts-to-the-menu-bar-and-user-interface).
+
+If you provide [pop-up buttons](https://developer.apple.com/design/human-interface-guidelines/pop-up-buttons) or [pull-down buttons](https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons) that reveal a menu in your iPad app, the menu automatically takes on a macOS appearance in the Mac app you create with Mac Catalyst.
+
+Developer note
+
+To add and remove custom app menus, use [`UIMenuBuilder`](https://developer.apple.com/documentation/UIKit/UIMenuBuilder) and add menu items that represent your iPad app’s commands as menu items with [`UICommand`](https://developer.apple.com/documentation/UIKit/UICommand).
+
+The system automatically converts the context menus in your iPad app to context menus in the macOS version of your app. As you create the Mac version of your app, consider looking for additional places to support context menus. Mac users tend to expect every object in your app to offer a context menu of relevant actions. Note that on a Mac, a context menu is sometimes called a _contextual_ menu.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Platform-considerations)
+
+ _No additional considerations for iPadOS or macOS. Not supported in iOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Related)
+
+[Designing for macOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-macos)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Developer-documentation)
+
+[Mac Catalyst](https://developer.apple.com/documentation/UIKit/mac-catalyst) — UIKit
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Videos)
+
+[ Designing iPad Apps for Mac ](https://developer.apple.com/videos/play/wwdc2019/809)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/mac-catalyst#Change-log)
+
+Date| Changes
+---|---
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/machine-learning.md b/web-app/public/skills/hig-technologies/references/machine-learning.md
new file mode 100644
index 00000000..8ac9bacc
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/machine-learning.md
@@ -0,0 +1,394 @@
+---
+title: "Machine learning | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/machine-learning
+
+# Machine learning
+
+Machine learning enables apps and games to learn from data and usage patterns, letting you improve existing experiences and create engaging new ones.
+
+
+
+In addition to providing familiar features like image recognition and content recommendations, your app can use machine learning to forge deep connections with people and help them accomplish more with less effort.
+
+For related guidance on how to use machine learning models to enable intelligent content creation experiences, see [Generative AI](https://developer.apple.com/design/human-interface-guidelines/generative-ai).
+
+## [Planning your design](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Planning-your-design)
+
+Machine learning apps use _models_ to perform tasks like recognizing images or finding relationships among numerical data. A great machine learning app depends on well-designed models as much as it depends on a well-designed UI and user experience. For insight into the process of designing models, see [Create ML](https://developer.apple.com/documentation/CreateML).
+
+As you design your models, keep the intended experience of your app in mind. It can take a long time to adjust the behavior of models, so be prepared to change the way you use data and metrics if the app experience needs to change.
+
+Designing the UI and user experience of a machine learning app can be uniquely challenging. Because a machine learning app bases its behavior on the data it receives — reacting to changing information and conditions — you can’t design specific reactions to a static set of scenarios. Instead, you design the experience by teaching the app how to interpret data and react accordingly.
+
+To help you meet this challenge, first consider the role that machine learning plays in your app. Defining the [role](https://developer.apple.com/design/human-interface-guidelines/machine-learning#The-role-of-machine-learning-in-your-app) of machine learning in your app can help you discover areas in which you can explore the ways machine learning can affect the experience your app provides.
+
+Use the machine learning role you identify to help you define ways your app can receive and display data. There are several patterns — grouped into _inputs_ and _outputs_ — that provide guidance in areas such as getting feedback, displaying data, handling mistakes, and supporting corrections. Use the guidance in these patterns to help you integrate machine learning into your app in ways that people appreciate.
+
+## [The role of machine learning in your app](https://developer.apple.com/design/human-interface-guidelines/machine-learning#The-role-of-machine-learning-in-your-app)
+
+Machine learning systems vary widely, and the ways an app can use machine learning vary widely, too. As you approach the design of your app, think about how its features use machine learning in each of the following areas.
+
+### [Critical or complementary](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Critical-or-complementary)
+
+If an app can still work without the feature that machine learning supports, machine learning is complementary to the app; otherwise, it’s a critical dependency. For example:
+
+ * The keyboard uses machine learning to provide QuickType suggestions. Because the keyboard still works without these suggestions, machine learning plays a complementary role in the app.
+
+ * Face ID relies on machine learning to perform accurate face recognition. Without machine learning, Face ID would not work.
+
+
+
+
+In general, the more critical an app feature is, the more people need accurate and reliable results. On the other hand, if a complementary feature delivers results that aren’t always of the highest quality, people might be more forgiving.
+
+### [Private or public](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Private-or-public)
+
+Machine learning results depend on data. To make good design decisions, you need to know as much as possible about the types of data your app feature needs. In general, the more sensitive the data, the more serious the consequences of inaccurate or unreliable results. For example:
+
+ * If a health app misinterprets data and incorrectly recommends a visit to the doctor, people are likely to experience anxiety and may lose trust in the app.
+
+ * If a music app misinterprets data and recommends an artist that people don’t like, they’re likely to view the result as an inconsequential mistake.
+
+
+
+
+As with critical app features, features that use sensitive data must prioritize accuracy and reliability. Regardless of the sensitivity of the data, all apps must protect user privacy at all times.
+
+### [Proactive or reactive](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Proactive-or-reactive)
+
+A _proactive_ app feature provides results without people requesting it to do so. Proactive features can prompt new tasks and interactions by providing unexpected, sometimes serendipitous results. In contrast, a _reactive_ app feature provides results when people ask for them or when they take certain actions. Reactive features typically help people as they perform their current task. For example:
+
+ * QuickType suggests words in reaction to what people type.
+
+ * Siri Suggestions can proactively suggest a shortcut based on people’s recent routines.
+
+
+
+
+Because people don’t ask for the results that a proactive feature provides, they may have less tolerance for low-quality information. To reduce the possibility that people will find proactive results intrusive or irrelevant, you may need to use additional data for the feature.
+
+### [Visible or invisible](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Visible-or-invisible)
+
+Apps may use machine learning to support visible or invisible features. People are usually aware of visible app features because such features tend to offer suggestions or choices that people view and interact with. For example, a visible keyboard feature tries to guess the word that people are typing and presents the most likely words in a list from which people choose.
+
+As the name suggests, an invisible feature provides results that aren’t obvious to people. For example, the keyboard learns how people type over time so it can optimize the tap area for each key and help them make fewer typing mistakes. Because this app feature improves the typing experience without requiring people to make choices, many people aren’t aware that the feature exists.
+
+People’s impression of the reliability of results can differ depending on whether a feature is visible or invisible. With a visible feature, people form an opinion about the feature’s reliability as they choose from its results. It’s harder for an invisible feature to communicate its reliability — and potentially receive feedback — because people may not be aware of the feature at all.
+
+### [Dynamic or static](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Dynamic-or-static)
+
+All machine learning models can improve, but some improve dynamically, as people interact with the app feature, and others improve offline and affect the feature only when the app updates. For example:
+
+ * Face ID improves dynamically as people’s faces gradually change over time.
+
+ * Photos improves its object recognition capabilities with every new iOS release.
+
+
+
+
+In addition to the frequency of app updates, static or dynamic improvements can affect other parts of the user experience, too. For example, dynamic features often incorporate forms of [calibration](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Calibration) and feedback (either [implicit](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) or [explicit](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback)), whereas static features might not.
+
+## [Explicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback)
+
+Explicit feedback provides actionable information your app can use to improve the content and experience it presents to people. Unlike [implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) — which is information an app gleans from user actions — explicit feedback is information people provide in response to a specific request from the app.
+
+
+
+_Favoriting_ — marking an item for quick access in the future — and _social feedback_ — expressing emotions towards others — are common user interactions that seem like mechanisms that supply explicit feedback. However, these tools actually provide implicit feedback because they don’t support app-specific requests. People use favoriting and social feedback to accomplish their own goals and apps can gather implicit feedback from these interactions.
+
+**Request explicit feedback only when necessary.** People must take action to provide explicit feedback, so it’s best to avoid requesting it if possible. Instead, consider using implicit feedback to learn how people interact with your app without asking them to do extra work.
+
+**Always make providing explicit feedback a voluntary task.** You want to communicate that explicit feedback can help improve the experience without making people feel that providing it is mandatory.
+
+**Use simple, direct language to describe each explicit feedback option and its consequences.** Avoid using imprecise terms such as _dislike_ because such terms don’t convey consequences and can be hard to translate. Instead, describe each option in a way that helps people understand what happens when they choose the option, such as:
+
+ * Suggest less pop music
+
+ * Suggest more thrillers
+
+ * Mute politics for a week
+
+
+
+
+**Add icons to an option description if it helps people understand it.** Icons can help clarify or emphasize part of an option description. Avoid using an icon by itself, because it might not be clear enough to communicate granularity or consequences.
+
+**Consider offering multiple options when requesting explicit feedback.** Providing [multiple options](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Multiple-options) can give people a sense of control and help them identify unwanted suggestions and remove them from your app. To help people provide feedback, consider offering options that become progressively more specific so that it’s easy for people to clarify their response.
+
+**Act immediately when you receive explicit feedback and persist the resulting changes.** For example, if people identify content they don’t want to see, that the content instantly disappears from their view and doesn’t appear elsewhere in your app. When you react immediately to feedback and show that your app remembers it, you build people’s trust in the value of providing it.
+
+**Consider using explicit feedback to help improve when and where you show results.** For example, people might like a result, but they may not want to see it at certain times or in certain contexts. Explicit feedback on when and where to show results can help you fine-tune the experience people have in your app.
+
+## [Implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback)
+
+Implicit feedback is information that arises as people interact with your app’s features. Unlike the specific responses you get from [explicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback), implicit feedback gives you a wide range of information about user behavior and preferences. Although incorporating implicit feedback isn’t required for a great machine learning app, the feedback can help you improve your app’s user experience without asking people to do any extra work.
+
+
+
+**Always secure people’s information.** Implicit feedback can gather potentially sensitive user information, so you must be particularly careful to maintain strict controls on user privacy.
+
+**Help people control their information.** As an app developer, you know that the more you understand about the behavior of your users — both within your app and in other apps — the more you can improve the experience your app provides. Although most people understand the benefits of making their information available to multiple apps, they may still be surprised when things they do in one app affect experiences they have in a different app. Worse, people may assume that apps are sharing their private information, which can cause them to lose trust in the apps. It’s important to tell people how your app gets and shares their information and to give people ways to restrict the flow of their information.
+
+**Don’t let implicit feedback decrease people’s opportunities to explore.** Implicit feedback tends to reinforce people’s behavior, which can improve the user experience in the short term, but may worsen it in the long term. For example, it might seem like a good idea to give people a set of suggestions that matches all the things they’re interested in now, but doing so doesn’t encourage them to explore new things.
+
+**When possible, use multiple feedback signals to improve suggestions and mitigate mistakes.** Implicit feedback is indirect, so it can be difficult to discern a person’s actual intent in the information you gather. For example, if someone views a photo, shares it in a message, and adds it to a shared album, it doesn’t necessarily mean they have positive feelings about the photo. Incorporate implicit feedback from multiple sources and interactions to help you avoid misinterpreting people’s intentions.
+
+**Consider withholding private or sensitive suggestions.** People often share their accounts and devices with others, or switch from using a personal device to a communal one. If your app receives implicit feedback related to private or sensitive topics, avoid offering recommendations based on that feedback.
+
+**Prioritize recent feedback.** People’s tastes can change frequently, so base your recommendations on recent implicit feedback. For example, Face ID prioritizes recent facial input because it’s most likely to represent what the person looks like now. If recent feedback isn’t available, you can fall back to historical feedback.
+
+**Use feedback to update predictions on a cadence that matches the person’s mental model of the feature.** For example, people expect typing suggestions to update immediately as they’re typing. On the other hand, giving people continuously updated song recommendations makes it hard to consider individual songs and could make them feel rushed or overwhelmed.
+
+**Be prepared for changes in implicit feedback when you make changes to your app’s UI.** Even small UI changes can lead to noticeable changes in the amount and types of implicit feedback. For example, changing the location of a button can affect how people use it, even if there’s no change in the benefit they get from the button’s action. Take such changes into account when interpreting the implicit feedback you receive from interactions in your app.
+
+**Beware of confirmation bias.** Implicit feedback is constrained by what people can actually see and do in your app and other apps — it rarely gives you insight into new things they might like to do. Avoid relying solely on implicit feedback to inform your results.
+
+## [Calibration](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Calibration)
+
+Calibration is a process during which people provide information that an app feature needs before it can function. To use Face ID, for example, a person must first scan their face.
+
+
+
+In general, only use calibration when your feature can’t function without that initial information. If your feature can work without calibration, consider using other ways to gather the information you need, such as [implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) or possibly [explicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback).
+
+**Always secure people’s information.** During calibration, people may provide sensitive information and you must make sure it remains secure.
+
+**Be clear about why you need people’s information.** Typically, calibration is required before people can use a feature, so it’s essential that they understand the value of providing their information. As you briefly describe how people can benefit from your feature, emphasize what it does rather than how it works.
+
+**Collect only the most essential information.** Designing a unique experience that requests a minimal amount of information can make people more comfortable participating in the process and increase their trust in your app.
+
+**Avoid asking people to participate in calibration more than once.** Also, it’s best when calibration occurs early in the user experience. As people continue using your app or feature, you can use implicit or explicit feedback to evolve your information about them without asking them to participate again. An exception is a feature that needs calibration with an object instead of a person. For example, an app that helps people improve their baseball swing might need to calibrate with each new baseball field.
+
+**Make calibration quick and easy.** Even a brief calibration experience takes time and requires effort from people. An ideal calibration experience makes it easy for people to respond, without compromising the quality of the information they provide. The following guidelines can help you create a streamlined calibration experience.
+
+ * Prioritize getting a few pieces of important information and infer the rest from other sources or by getting people’s feedback.
+
+ * Avoid asking for information that most people would have to look up.
+
+ * Avoid asking people to perform actions that might be difficult.
+
+
+
+
+**Make sure people know how to perform calibration successfully.** After people decide to participate in calibration, give them an explicit goal and show their progress towards it. For example, Face ID calibration briefly describes what people need to do and changes the appearance of the tick marks encircling the face as people progress through scanning.
+
+**Immediately provide assistance if progress stalls.** When progress stalls, people can feel stuck or powerless, and they may lose trust in your app. In this situation, it’s crucial to give people actionable recommendations that quickly get them back on track. As you provide this guidance, never imply that something’s wrong or that people are at fault, and never leave people without a clear next step.
+
+**Confirm success.** The moment people successfully complete calibration, reward their time and effort by giving them a clear path towards using the feature. Providing an explicit completion to the calibration experience reinforces the unique nature of the experience and helps people switch their focus to your feature.
+
+**Let people cancel calibration at any time.** Make sure you give people an easy way to cancel the experience at any point and avoid implying any judgement about their choice. There’s no need to provide any messaging that mentions the canceled calibration, because the next time people attempt to use the feature, they’ll have another chance to participate.
+
+**Give people a way to update or remove information they provided during calibration.** Letting people edit their information gives them more control and can lead them to have greater trust in your app. Although the calibration experience can help people edit their responses, it’s a good idea to let people edit their information outside of the calibration experience so that they feel free to make changes at any time.
+
+## [Corrections](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Corrections)
+
+People use corrections to fix mistakes that apps make. For example, if a photo app automatically crops a photo in a way people don’t like, they can correct the mistake by cropping the photo in a different way.
+
+
+
+**Give people familiar, easy ways to make corrections.** When your app makes a mistake, you don’t want people to be confused about how to correct it. You can avoid causing confusion by showing the steps your app takes as it performs the automated task. For example, Photos highlights the controls it uses to auto-crop a photograph so that people can use the same controls to refine or undo the results.
+
+**Provide immediate value when people make a correction.** Reward people’s effort by instantly displaying corrected content, especially when the feature is critical or you’re responding to direct user input. Also, be sure to persist the updates so people don’t have to make the same corrections again.
+
+**Let people correct their corrections.** Sometimes, people make a correction without realizing that they’ve made a mistake. As you do with all corrections, respond immediately to an updated correction and persist the update.
+
+**Always balance the benefits of a feature with the effort required to make a correction.** People may not mind when a feature that automates a task makes a mistake, but they’re likely to stop using the feature if it seems easier to perform the task themselves.
+
+**Never rely on corrections to make up for low-quality results.** Although corrections can reduce the impact of a mistake, depending on them may erode people’s trust in your app and reduce the value of your feature.
+
+**Learn from corrections when it makes sense.** A correction is a type of [implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) that can give you valuable information about ways your app doesn’t meet people’s expectations. Before you use a correction to update your models, make sure that the correction will lead to higher quality results.
+
+**When possible, use guided corrections instead of freeform corrections.** Guided corrections suggest specific alternatives, so they require less user effort; freeform corrections don’t suggest specific alternatives, so they require more input from people. An example of guided correction is a speech-to-text feature that gives people a list of alternative text completions from which to choose. In contrast, Photos offers freeform correction so that people can adjust the auto-cropping of a photo as they see fit. If it makes sense in your app, you can support a combination of guided and freeform corrections.
+
+## [Mistakes](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Mistakes)
+
+It’s inevitable that your app will make mistakes. Although people may not expect perfection, mistakes can damage their experience and decrease their trust in your app. To help you avoid negative consequences, it’s crucial to:
+
+ * Anticipate mistakes. As much as possible, design ways to avoid mistakes and mitigate them when they happen.
+
+ * Help people handle mistakes. Mistakes can have a wide range of consequences, so the tools you provide to handle a mistake must be able to address those consequences.
+
+ * Learn from mistakes when doing so improves your app. In some cases, learning from a mistake might have undesirable effects, such as causing unpredictability in the user experience. When it makes sense, use each mistake as a data point that can refine your machine learning models and improve your app.
+
+
+
+
+There are several machine learning patterns that can help you address mistakes:
+
+ * [Limitations](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Limitations) help you set people’s expectations about the accuracy of your suggestions.
+
+ * [Corrections](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Corrections) give people a way to be successful even when your results are wrong.
+
+ * [Attribution](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Attribution) gives people insight into where suggestions come from, which can help them understand mistakes.
+
+ * [Confidence](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Confidence) helps you gauge the quality of your results, which can impact how you present them.
+
+ * Feedback — both [explicit](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Explicit-feedback) and [implicit](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) — lets people tell you about mistakes that you might not be aware of.
+
+
+
+
+**Understand the significance of a mistake’s consequences.** For example, incorrect keyboard suggestions might annoy people, but suggesting a travel route that results in a missed flight is a serious inconvenience. Show empathy by providing corrective actions or tools that match the seriousness of the mistake.
+
+**Make it easy for people to correct frequent or predictable mistakes.** If you don’t give people an easy way to correct mistakes, they can lose trust in your app.
+
+**Continuously update your feature to reflect people’s evolving interests and preferences and help avoid mistakes.** For example, you can use implicit feedback to discover changes in people’s tastes and habits. It’s also a good idea to update your feature with domain-specific information, such as current trends in popular entertainment. Ideally, people don’t have to do any work to benefit from improvements in your app.
+
+**When possible, address mistakes without complicating the UI.** Some patterns, such as corrections and limitations, tend to integrate seamlessly with an app’s UI, whereas others, like attributions, can be harder to integrate. Balance a pattern’s effect on the UI with its potential for compounding the mistake. For example, if you update the UI with an attribution that turns out to be wrong, the effect of the original mistake is magnified.
+
+**Be especially careful to avoid mistakes in proactive features.** A proactive feature — like a suggestion based on people’s behaviors — promises valuable results without asking people to do anything to get them. However, because people don’t request a proactive feature, they often have less patience with its mistakes. Mistakes made by proactive features can also cause people to feel that they have less control.
+
+**As you work on reducing mistakes in one area, always consider the effect your work has on other areas and overall accuracy.** For example, optimizing an image-recognition app to improve how it recognizes dogs might result in a decreased ability to recognize cats. As your models evolve, be prepared for mistakes to evolve, too. Use what you know about people’s preferences to help you determine the areas to work on.
+
+## [Multiple options](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Multiple-options)
+
+Depending on the design of your feature, it might work best to present a single result or multiple results from which people can choose. Providing multiple options can give people a greater sense of control and can help bridge the gap between your model’s predictions and what people actually want. Multiple options can also encourage people to have realistic expectations about the types of results your app generates.
+
+
+
+You might present multiple options to people in the following contexts:
+
+ * Suggested options, a proactive feature that suggests content to people based on the their past interactions. For example, For You recommendations from Apple Music.
+
+ * Requested options, a reactive feature that suggests potential next steps to people based on their recent actions. For example, Quick Type suggestions.
+
+ * Corrections, which are actions people take to fix mistakes your app has made when it’s acting on their behalf. For example, the Photos Auto-Crop feature.
+
+
+
+
+**Prefer diverse options.** When possible, balance the accuracy of a response with the diversity of multiple options. For example, Apple Maps generally suggests more than one route to a destination, such as a route without tolls, a scenic route, or a route that uses highways. Providing different types of options helps people choose the one that they prefer and can also suggest new items that might interest them.
+
+**In general, avoid providing too many options.** People must evaluate each option before making a choice, so more options increases cognitive load. When possible, list options on one screen so people don’t have to scroll to find the right one.
+
+**List the most likely option first.** When you know how your [confidence](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Confidence) values correlate with the quality of your results, you might use them to rank the options. You might also consider using contextual information, such as the time of day or the current location, to help you determine the most likely option. If it makes sense in your app, select the first option by default so people can quickly achieve their goals without reading through every option.
+
+**Make options easy to distinguish and choose.** For example, in a routing app, people often need to make route choices quickly to avoid going the wrong way. When options look similar, help people distinguish between them by providing a brief description of each one and taking particular care to highlight the differences. In cases where there are too many options to display in a single view, such as with content recommendations, consider grouping options in categories that people can scan rapidly.
+
+**Learn from selections when it makes sense.** People give you [implicit feedback](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Implicit-feedback) every time they make a selection. When it doesn’t adversely affect the user experience, use this feedback to refine the options you provide and increase the chance that you’ll present the most likely option first. In general, continuing to offer incorrect results is likely to decrease people’s trust in the quality of your app’s predictions.
+
+## [Confidence](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Confidence)
+
+Confidence indicates the measure of certainty for a result. Not all models produce confidence values by default, so you might consider generating them if you can use them to improve the user experience of your app.
+
+
+
+Although it might seem like higher confidence produces a higher quality result — and therefore a better user experience — it doesn’t necessarily work that way. You need to verify that your confidence values correspond to the quality of your results. For example, you might review values for multiple confidence thresholds or compare values across multiple versions of your app. If you’re not sure how your confidence values correlate with the quality of your results, it’s not a good idea to convey confidence to people.
+
+**Know what your confidence values mean before you decide how to present them.** For example, people may forgive low-quality results from [critical or complementary](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Critical-or-complementary) features — especially when results are accompanied by [attribution](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Attribution) or other contextual information — but presenting low-quality results in a prominent way is likely to erode trust in your app.
+
+**In general, translate confidence values into concepts that people already understand.** Simply displaying a confidence value doesn’t necessarily help people understand how it relates to a result. For example, a feature that suggests new music based on a person’s listening habits might calculate that there’s a 97% match between a new song and the songs they usually listen to. However, displaying “97% match” next to the new song as an attribution doesn’t communicate enough information to help people make a choice. In contrast, providing an attribution that clearly identifies the behavior — such as “Because you listen to pop music” — can be more actionable.
+
+**In situations where attributions aren’t helpful, consider ranking or ordering the results in a way that implies confidence levels.** If you must display confidence directly, consider expressing it in terms of semantic categories. For example, a feature that predicts travel prices might replace ranges of confidence numbers with categories like “high chance” and “low chance” to give context to the values and help people understand and compare the results.
+
+**In scenarios where people expect statistical or numerical information, display confidence values that help them interpret the results.** For example, weather predictions, sports statistics, and polling numbers are often accompanied by specific values that express the accuracy of the data as an interval or a percentage.
+
+**Whenever possible, help people make decisions by conveying confidence in terms of actionable suggestions.** Understanding people’s goals is key to expressing confidence in ways that help them make decisions. For example, if your feature predicts when an item will be at its lowest price, you know that people want to optimize how they spend their time and money. For a feature like this, displaying percentages or other numerical confidence values would be less valuable than providing actionable suggestions like “This is a good time to buy,” or “Consider waiting for a better price.”
+
+**Consider changing how you present results based on different confidence thresholds.** If high or low levels of confidence have a meaningful impact on the ways people can experience the results, it’s a good idea to adapt your presentation accordingly. For example, when confidence is high, the face recognition feature in Photos simply displays the photos that contain a specific person, but when confidence is lower, the feature asks people to confirm whether the photos contain the person before showing more.
+
+**When you know that confidence values correspond to result quality, you generally want to avoid showing results when confidence is low.** Especially when a feature is proactive and can make unbidden suggestions, poor results can cause people to be annoyed and even lose trust in the feature. For suggestions and proactive features, it’s a good idea to set a confidence threshold below which you don’t offer results.
+
+## [Attribution](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Attribution)
+
+An attribution expresses the underlying basis or rationale for a result, without explaining exactly how a model works. Depending on the design of your app, you might want to use attributions to impart transparency and give people insight into your results. For example, if your app suggests books for people to read, you might use an attribution like “Because you’ve read mysteries” when you suggest books in the “thrillers” category.
+
+
+
+To help you decide whether to include attributions in your app, consider how you want them to affect people. For example, you might want attributions to:
+
+ * Encourage people to change what they do in your app
+
+ * Minimize the impact of [mistakes](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Mistakes)
+
+ * Help people build a mental model of your feature
+
+ * Promote trust in your app over time
+
+
+
+
+**Consider using attributions to help people distinguish among results.** For example, if you present a set of results as [multiple options](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Multiple-options), including attributions can help people choose an option based on their understanding of the premise that led to it, such as “New books by authors you’ve read.”
+
+**Avoid being too specific or too general.** Overly specific attributions can make people feel like they have to do additional work to interpret the results, whereas overly general attributions typically don’t provide useful information. In apps that make content recommendations, general attributions can make people feel like your app is not treating them as individuals, but overly specific attributions can make people think that your app is watching them too closely. The best attributions strike a balance between these extremes.
+
+**Keep attributions factual and based on objective analysis.** To be useful, an attribution needs to help people reason about a result; you don’t want to provoke an emotional response. Don’t provide an attribution that implies understanding or judgment of people’s emotions, preferences, or beliefs. For example, an app that recommends new content to people can use an attribution like “Because you’ve read nonfiction” instead of an attribution like “Because you love nonfiction.”
+
+**In general, avoid technical or statistical jargon.** In most situations, using percentages, statistics, and other technical jargon doesn’t help people assess the results you provide. The exception to this is when the result itself is of a statistical or technical nature, such as information in the areas of weather, sports, polling and election results, or scientific data.
+
+## [Limitations](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Limitations)
+
+Every feature — whether it’s based on machine learning or not — has certain limitations to what it can deliver. In general, there are two types of limitations: things a feature can’t do well and things a feature can’t do at all. When there’s a mismatch between people’s expectations about a feature and what the feature can actually accomplish, a limitation can seem like a defect. For example, people might expect:
+
+ * Photos to perform a search that covers every category they can imagine
+
+ * Siri to respond to queries that aren’t well defined, like “What is the meaning of life?”
+
+ * FaceID to work from every angle
+
+
+
+
+An important part of the design process is to identify the scenarios where limitations impact the user experience and design ways to help people work with them. For example:
+
+ * Set people’s expectations before they use the feature.
+
+ * Show people how to get the best results while they’re using the feature.
+
+ * When inferior results occur, explain why so that people can understand the feature better.
+
+
+
+
+
+
+**Help people establish realistic expectations.** When a limitation may have a serious effect on user experience but happens rarely, consider making people aware of the limitation before they use your app or feature. You might describe the limitation in marketing materials or within the feature’s context so that people can decide how they want to rely on the feature. If the effects of a limitation aren’t serious, you can help set people’s expectations by providing [attributions](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Attribution).
+
+**Demonstrate how to get the best results.** If you don’t provide guidance for using a feature, people may assume it’ll do everything they want. When you proactively show people how to get good results, you help them benefit from the feature and establish a more accurate mental model of the feature’s capabilities. There are many ways to show people the best ways to use a feature, such as:
+
+ * Use placeholder text to suggest input. In Photos, the search bar displays the text “Photos, People, Places…” to help people understand what they can search for before they begin typing. Photos also displays a description of how it scans the photo library to offer search suggestions.
+
+ * As people interact with the feature, provide feedback on their actions to guide them towards a result without overwhelming them. For example, while people are interacting with Animoji, the feature responds to current conditions and suggests how people can improve their results by adjusting the lighting or moving closer to the camera.
+
+ * Suggest alternative ways to accomplish the goal instead of showing no results. To do this successfully, you need to understand the goal well enough to suggest alternatives that make sense. For example, if people ask Siri to set a timer on a Mac, Siri suggests setting a reminder instead, because timers aren’t available in macOS. This suggestion makes sense because people’s goal is to receive an alert at a certain time.
+
+
+
+
+**Explain how limitations can cause unsatisfactory results.** People can get frustrated when it seems that your feature works intermittently. Ideally, your feature can recognize and describe the reasons for poor results to make people aware of the limitations and help them to adjust their expectations. For example, Animoji tells people that it doesn’t work well in the dark.
+
+**Consider telling people when limitations are resolved.** When people use a feature frequently, they learn to avoid the interactions that fail because of the feature’s limitations. When you update your app to remove a limitation, you might want to notify people so that they can adjust their mental model of your feature and return to interactions they’d previously avoided.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Related)
+
+[Generative AI](https://developer.apple.com/design/human-interface-guidelines/generative-ai)
+
+[Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Developer-documentation)
+
+[Apple Intelligence and machine learning](https://developer.apple.com/documentation/TechnologyOverviews/ai-machine-learning)
+
+[Create ML](https://developer.apple.com/documentation/CreateML)
+
+[Core ML](https://developer.apple.com/documentation/CoreML)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Videos)
+
+[ Explore prompt design & safety for on-device foundation models ](https://developer.apple.com/videos/play/wwdc2025/248)
+
+[ Discover machine learning & AI frameworks on Apple platforms ](https://developer.apple.com/videos/play/wwdc2025/360)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/machine-learning#Change-log)
+
+Date| Changes
+---|---
+October 24, 2023| Added art to Corrections section.
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/maps.md b/web-app/public/skills/hig-technologies/references/maps.md
new file mode 100644
index 00000000..b2329211
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/maps.md
@@ -0,0 +1,221 @@
+---
+title: "Maps | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/maps
+
+# Maps
+
+A map displays outdoor or indoor geographical data in your app or on your website.
+
+
+
+A map uses a familiar interface that supports much of the same functionality as the system-provided Maps app, such as zooming, panning, and rotation. A map can also include annotations and overlays and show routing information, and you can configure it to use a standard graphical view, a satellite image-based view, or a view that’s a hybrid of both.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/maps#Best-practices)
+
+**In general, make your map interactive.** People expect to be able to zoom, pan, and otherwise interact with maps in familiar ways. Noninteractive elements that obscure the map can interfere with people’s expectations for how maps behave.
+
+**Pick a map emphasis style that suits the needs of your app.** There are two emphasis styles to choose from:
+
+ * The _default_ style presents a version of the map with fully saturated colors, and is a good option for most standard map applications without a lot of custom elements. This style is also useful for keeping visual alignment between your map and the Maps app, in situations when people might switch between them.
+
+ * The _muted_ style, by contrast, presents a desaturated version of the map. This style is great if you have a lot of information-rich content that you want to stand out against the map.
+
+
+
+
+
+
+Default style
+
+
+
+Muted style
+
+For developer guidance, see [`MKStandardMapConfiguration.EmphasisStyle`](https://developer.apple.com/documentation/MapKit/MKStandardMapConfiguration/EmphasisStyle-swift.enum).
+
+**Help people find places in your map.** Consider offering a search feature combined with a way to filter locations by category. The search field for a shopping mall map, for example, might include filters that make it easy to find common store types, like clothing, housewares, electronics, jewelry, and toys.
+
+**Clearly identify elements that people select.** When someone selects a specific area or other element on the map, use distinct styling like an outline and color variation to call attention to the selection.
+
+**Cluster overlapping points of interest to improve map legibility.** A _cluster_ uses a single pin to represent multiple points of interest within close proximity. As people zoom in on a map, clusters expand to progressively reveal individual points of interest.
+
+Points of interest in a cluster
+
+Individual points of interest when zoomed in
+
+**Help people see the Apple logo and legal link.** It’s fine when parts of your interface temporarily cover the logo and link, but don’t cover these elements all the time. Follow these guidelines to help keep the Apple logo and legal link visible:
+
+ * Use adequate padding to separate the logo and link from the map boundaries and your custom controls. For example, it works well to use 7 points of padding on the sides of the elements and 10 points above and below them.
+
+ * Avoid causing the logo and link to move with your interface. It’s best when the Apple logo and legal link appear to be fixed to the map.
+
+ * If your custom interface can move relative to the map, use the lowest position of the custom element to determine the placement of the logo and link. For example, if your app lets people pull up a custom card from the bottom of the screen, place the Apple logo and legal link 10 points above the lowest resting position of the card.
+
+
+
+
+Note
+
+The Apple logo and legal link aren’t shown on maps that are smaller than 200x100 pixels.
+
+## [Custom information](https://developer.apple.com/design/human-interface-guidelines/maps#Custom-information)
+
+**Use annotations that match the visual style of your app.** Annotations identify custom points of interest on your map. The default annotation marker has a red tint and a white pin icon. You can change the tint to match the color scheme of your app. You can also change the icon to a string or image, like a logo. An icon string can contain any characters, including Unicode characters, but keep it to two to three characters in length for readability. For developer guidance, see [`MKAnnotationView`](https://developer.apple.com/documentation/MapKit/MKAnnotationView).
+
+**If you want to display custom information that’s related to standard map features, consider making them independently selectable.** When you support selectable map features, the system treats Apple-provided features (including points of interest, territories, and physical features) independently from other annotations that you add. You can configure custom appearances and information to represent these features when people select them. For developer guidance, see [`MKMapFeatureOptions`](https://developer.apple.com/documentation/MapKit/MKMapFeatureOptions).
+
+**Use overlays to define map areas with a specific relationship to your content.**
+
+ * _Above roads_ , the default level, places the overlay above roads but below buildings, trees, and other features. This is great for situations where you want people to have an idea of what’s below the overlay, while still clearly understanding that it’s a defined space.
+
+ * _Above labels_ places the overlay above both roads and labels, hiding everything beneath it. This is useful for content that you want to be fully abstracted from the features of the map, or when you want to hide areas of the map that aren’t relevant.
+
+
+
+
+For developer guidance, see [Displaying overlays on a map](https://developer.apple.com/documentation/MapKit/displaying-overlays-on-a-map) and [`MKOverlayLevel`](https://developer.apple.com/documentation/MapKit/MKOverlayLevel).
+
+**Make sure there’s enough contrast between custom controls and the map.** Insufficient contrast makes controls hard to see and can cause them to blend in with the map. Consider using a thin stroke or light drop shadow to help a custom control stand out, or applying blend modes to the map area to increase its contrast with the controls atop it.
+
+## [Place cards](https://developer.apple.com/design/human-interface-guidelines/maps#Place-cards)
+
+Place cards display rich place information in your app or website, such as operating hours, phone numbers, addresses, and more. This enables you to provide structured and up-to-date information for places that you specify, and add depth to search results.
+
+### [Displaying place cards in a map](https://developer.apple.com/design/human-interface-guidelines/maps#Displaying-place-cards-in-a-map)
+
+You can present a place card that appears directly in your map anytime someone selects a place. This is a great way to provide place information in a map with multiple places that you specify, like a map of bookstores that an author plans to visit on their book signing tour. For developer guidance, see [`mapItemDetailSelectionAccessory(_:)`](https://developer.apple.com/documentation/MapKit/MapContent/mapItemDetailSelectionAccessory\(_:\)), [`mapView(_:selectionAccessoryFor:)`](https://developer.apple.com/documentation/MapKit/MKMapViewDelegate/mapView\(_:selectionAccessoryFor:\)), and [`selectionAccessory`](https://developer.apple.com/documentation/MapKitJS/Annotation/selectionAccessory).
+
+You can also display place cards for other places on a map, such as points of interest, territories, and physical features, to provide valuable context to people about nearby places. For developer guidance, see [`mapFeatureSelectionAccessory(_:)`](https://developer.apple.com/documentation/SwiftUI/View/mapFeatureSelectionAccessory\(_:\)), [`mapView(_:selectionAccessoryFor:)`](https://developer.apple.com/documentation/MapKit/MKMapViewDelegate/mapView\(_:selectionAccessoryFor:\)), and [`selectableMapFeatureSelectionAccessory`](https://developer.apple.com/documentation/MapKitJS/Map/selectableMapFeatureSelectionAccessory).
+
+Developer note
+
+In websites, you can embed a custom map that displays a place card by default for a single place that you specify. For developer guidance, see [Displaying place information using the Maps Embed API](https://developer.apple.com/documentation/MapKitJS/displaying-place-information-using-the-maps-embed-api).
+
+The system defines several place card styles, which specify the size, appearance, and information included in a place card.
+
+ * The _automatic_ style lets the system determine the place card style based on the size of your map view.
+
+ * The _callout_ style displays a place card in a popover style next to the selected place. You can further specify the style of a callout — the _full_ callout style displays a large, detailed place card, and the _compact_ callout style displays a space-saving, more concise place card. If you don’t specify a callout style, the system defaults to the _automatic_ callout style, which determines the callout style based on your map’s view size.
+
+ * The _caption_ style displays an “Open in Apple Maps” link.
+
+ * The _sheet_ style displays a place card in a [sheet](https://developer.apple.com/design/human-interface-guidelines/sheets).
+
+
+
+
+For developer guidance, see [`MapItemDetailSelectionAccessoryStyle`](https://developer.apple.com/documentation/MapKit/MapItemDetailSelectionAccessoryStyle), [`MKSelectionAccessory.MapItemDetailPresentationStyle`](https://developer.apple.com/documentation/MapKit/MKSelectionAccessory/MapItemDetailPresentationStyle), and [`PlaceSelectionAccessoryStyle`](https://developer.apple.com/documentation/MapKitJS/PlaceSelectionAccessoryStyle).
+
+ * Full callout
+ * Compact callout
+ * Caption
+ * Sheet
+
+
+
+
+
+
+
+
+
+
+
+Full callout style place cards appear differently depending on a person’s device. The system presents the full callout style place card in a popover style in iPadOS and macOS, and as a [sheet](https://developer.apple.com/design/human-interface-guidelines/sheets) in iOS.
+
+
+
+**Consider your map presentation when choosing a style.** The full callout style place card offers people the richest experience, presenting them with the most information about a place directly in your map. However, be sure to choose a place card style that fits in the context of your map. For example, if your app displays a small map with many annotations, consider using the compact callout style for a space-saving presentation that shows place information while maintaining the context of the other places that you specify in your map.
+
+**Make sure your place card looks great on different devices and window sizes.** If you choose to specify a style, ensure that the content in your place card remains viewable on different devices and as window sizes change. For full callout style place cards, you can set a minimum width to prevent text from overflowing on smaller devices.
+
+**Avoid duplicating information.** Consider what information you already display in your app or website when you choose a place card style. For example, the full callout style place card might display information that your app already shows. In this case, the compact callout or caption style might be a better complement.
+
+**Keep the location on your map visible when displaying a place card.** This helps people maintain a sense of where the location is on your map while getting detailed place information. You can set an offset distance for your place card and point it to the selected location. For developer guidance, see [`offset(_:)`](https://developer.apple.com/documentation/SwiftUI/View/offset\(_:\)), [`accessoryOffset`](https://developer.apple.com/documentation/MapKit/MKAnnotationView/accessoryOffset), and [`selectionAccessoryOffset`](https://developer.apple.com/documentation/MapKitJS/Annotation/selectionAccessoryOffset).
+
+### [Adding place cards outside of a map](https://developer.apple.com/design/human-interface-guidelines/maps#Adding-place-cards-outside-of-a-map)
+
+You can also display place information outside of a map in your app or website. For example, you might want to display a list of places rather than a map, like in search results or a store locator, and present a place card when people select one. For developer guidance, see [`mapItemDetailSelectionAccessory(_:)`](https://developer.apple.com/documentation/MapKit/MapContent/mapItemDetailSelectionAccessory\(_:\)), [`mapItemDetail(_:)`](https://developer.apple.com/documentation/MapKit/MKSelectionAccessory/mapItemDetail\(_:\)), and [`PlaceDetail`](https://developer.apple.com/documentation/MapKitJS/PlaceDetail).
+
+Important
+
+If you don’t display a place card directly within a map view, you must include a map in the place card. For developer guidance, see [`mapItemDetailSheet(item:displaysMap:)`](https://developer.apple.com/documentation/SwiftUI/View/mapItemDetailSheet\(item:displaysMap:\)) and [`init(mapItem:displaysMap:)`](https://developer.apple.com/documentation/MapKit/MKMapItemDetailViewController/init\(mapItem:displaysMap:\)).
+
+**Use location-related cues in surrounding content to help communicate that people can open a place card.** For example, you can display place names and addresses alongside a button for more details to help indicate that people can interact with it to get place information. For a space-efficient design, you can include a map pin icon with a place name to help communicate that people can open a place card.
+
+## [Indoor maps](https://developer.apple.com/design/human-interface-guidelines/maps#Indoor-maps)
+
+Apps connected with specific venues like shopping malls and stadiums can design custom interactive maps that help people locate and navigate to indoor points of interest. Indoor maps can include overlays that highlight specific areas, such as rooms, kiosks, and other locations. They can also include text labels, icons, and routes.
+
+ * Example 1
+ * Example 2
+ * Example 3
+
+
+
+
+
+
+
+
+
+**Adjust map detail based on the zoom level.** Too much detail can cause a map to appear cluttered. Show large areas like rooms and buildings at all zoom levels. Then, progressively add more detailed features and labels as the map is zoomed in. An airport map might show only terminals and gates when zoomed out, but reveal individual stores and restrooms when zoomed in.
+
+
+
+**Use distinctive styling to differentiate the features of your map.** Using color along with icons can help distinguish different types of areas, stores, and services, and make it easy for people to quickly find what they’re looking for.
+
+**Offer a floor picker if your venue includes multiple levels.** A floor picker lets people quickly jump between floors. If you implement this feature, keep floor numbers concise for simplicity. In most cases, a list of floor numbers — rather than floor names — is sufficient.
+
+**Include surrounding areas to provide context.** Adjacent streets, playgrounds, and other nearby locations can all help orient people when they use your map. If these areas are noninteractive, use dimming and a distinct color to make them appear supplemental.
+
+
+
+**Consider supporting navigation between your venue and nearby transit points.** Make it easy to enter and exit your venue by offering routing to and from nearby bus stops, train stations, parking lots, garages, and other transit locations. You might also offer a way for people to quickly switch over to Apple Maps for additional navigation options.
+
+**Limit scrolling outside of your venue.** This can help people avoid getting lost when they swipe too hard on your map. When possible, keep at least part of your indoor map visible onscreen at all times. To help people stay oriented, you may need to adjust the amount of scrolling you permit based on the zoom level.
+
+**Design an indoor map that feels like a natural extension of your app.** Don’t try to replicate the appearance of Apple Maps. Instead, make sure area overlays, icons, and text match the visual style of your app. For guidance, see [Indoor Mapping Data Format](https://register.apple.com/resources/imdf/).
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/maps#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or visionOS._
+
+### [watchOS](https://developer.apple.com/design/human-interface-guidelines/maps#watchOS)
+
+On Apple Watch, maps are static snapshots of geographic locations. Place a map in your interface at design time and show the appropriate region at runtime. The displayed region isn’t interactive; tapping it opens the Maps app on Apple Watch. You can add up to five annotations to a map to highlight points of interest or other relevant information. For developer guidance, see [`WKInterfaceMap`](https://developer.apple.com/documentation/WatchKit/WKInterfaceMap).
+
+
+
+**Fit the map interface element to the screen.** The entire element needs to be visible on the Apple Watch display without requiring scrolling.
+
+**Show the smallest region that encompasses the points of interest.** The content within a map interface element doesn’t scroll, so all key content must be visible within the displayed region.
+
+For developer guidance, see [`WKInterfaceMap`](https://developer.apple.com/documentation/WatchKit/WKInterfaceMap).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/maps#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/maps#Developer-documentation)
+
+[MapKit](https://developer.apple.com/documentation/MapKit)
+
+[MapKit JS](https://developer.apple.com/documentation/MapKitJS)
+
+[Indoor Mapping Data Format](https://register.apple.com/resources/imdf/)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/maps#Videos)
+
+[ Go further with MapKit ](https://developer.apple.com/videos/play/wwdc2025/204)
+
+[ Unlock the power of places with MapKit ](https://developer.apple.com/videos/play/wwdc2024/10097)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/maps#Change-log)
+
+Date| Changes
+---|---
+December 18, 2024| Added guidance for place cards and included additional artwork.
+September 12, 2023| Added artwork.
+September 23, 2022| Added guidelines for presenting custom information, refined best practices, and consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/nfc.md b/web-app/public/skills/hig-technologies/references/nfc.md
new file mode 100644
index 00000000..a29c9371
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/nfc.md
@@ -0,0 +1,51 @@
+---
+title: "NFC | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/nfc
+
+# NFC
+
+Near-field communication (NFC) allows devices within a few centimeters of each other to exchange information wirelessly.
+
+
+
+iOS apps running on supported devices can use NFC scanning to read data from electronic tags attached to real-world objects. For example, a person can scan a toy to connect it with a video game, a shopper can scan an in-store sign to access coupons, or a retail employee can scan products to track inventory.
+
+## [In-app tag reading](https://developer.apple.com/design/human-interface-guidelines/nfc#In-app-tag-reading)
+
+An app can support single- or multiple-object scanning when the app is active, and display a scanning sheet whenever people are about to scan something.
+
+
+
+**Don’t encourage people to make contact with physical objects.** To scan a tag, an iOS device must simply be within close proximity of the tag. It doesn’t need to actually touch the tag. Use terms like _scan_ and _hold near_ instead of _tap_ and _touch_ when asking people to scan objects.
+
+**Use approachable terminology.** Near-field communication may be unfamiliar to some people. To make it approachable, avoid referring to technical, developer-oriented terms like _NFC_ , _Core NFC_ , _Near-field communication_ , and _tag_. Instead, use friendly, conversational terms that most people will understand.
+
+Use| Don’t use
+---|---
+Scan the [_object name_].| Scan the NFC tag.
+Hold your iPhone near the [_object name_] to learn more about it.| To use NFC scanning, tap your phone to the [_object_].
+
+**Provide succinct instructional text for the scanning sheet.** Provide a complete sentence, in sentence case, with ending punctuation. Identify the object to scan, and revise the text appropriately for subsequent scans. Keep the text short to avoid truncation.
+
+First scan| Subsequent scans
+---|---
+Hold your iPhone near the [_object name_] to learn more about it.| Now hold your iPhone near another [_object name_].
+
+## [Background tag reading](https://developer.apple.com/design/human-interface-guidelines/nfc#Background-tag-reading)
+
+Background tag reading lets people scan tags quickly any time, without needing to first open your app and initiate scanning. On devices that support background tag reading, the system automatically looks for nearby compatible tags whenever the screen is illuminated. After detecting and matching a tag with an app, the system shows a notification that the people can tap to send the tag data to the app for processing. Note that background reading isn’t available when an NFC scanning sheet is visible, Wallet or Apple Pay are in use, cameras are in use, the device is in Airplane Mode, and the device is locked after a restart.
+
+
+
+**Support both background and in-app tag reading.** Your app must still provide an in-app way to scan tags, for people with devices that don’t support background tag reading.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/nfc#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/nfc#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/nfc#Developer-documentation)
+
+[Core NFC](https://developer.apple.com/documentation/CoreNFC)
+
diff --git a/web-app/public/skills/hig-technologies/references/photo-editing.md b/web-app/public/skills/hig-technologies/references/photo-editing.md
new file mode 100644
index 00000000..b2c3cecb
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/photo-editing.md
@@ -0,0 +1,40 @@
+---
+title: "Photo editing | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/photo-editing
+
+# Photo editing
+
+Photo-editing extensions let people modify photos and videos within the Photos app by applying filters or making other changes.
+
+
+
+Edits are always saved in the Photos app as new files, safely preserving the original versions.
+
+To access a photo editing extension, a photo must be in edit mode. While in edit mode, tapping the extension icon in the toolbar displays an action menu of available editing extensions. Selecting one displays the extension’s interface in a modal view containing a top toolbar. Dismissing this view confirms and saves the edit, or cancels it and returns to the Photos app.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/photo-editing#Best-practices)
+
+**Confirm cancellation of edits.** Editing a photo or video can be time consuming. If someone taps the Cancel button, don’t immediately discard their changes. Ask them to confirm that they really want to cancel, and inform them that any edits will be lost after cancellation. There’s no need to show this confirmation if no edits have been made yet.
+
+**Don’t provide a custom top toolbar.** Your extension loads within a modal view that already includes a toolbar. Providing a second toolbar is confusing and takes space away from the content being edited.
+
+**Let people preview edits.** It’s hard to approve an edit if you can’t see what it looks like. Let people see the result of their work before closing your extension and returning to the Photos app.
+
+**Use your app icon for your photo editing extension icon.** This instills confidence that the extension is in fact provided by your app.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/photo-editing#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, or macOS. Not supported in tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/photo-editing#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/photo-editing#Developer-documentation)
+
+[App extensions](https://developer.apple.com/app-extensions/)
+
+[PhotoKit](https://developer.apple.com/documentation/PhotoKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/photo-editing#Videos)
+
+[ Introducing Photo Segmentation Mattes ](https://developer.apple.com/videos/play/wwdc2019/260)
+
diff --git a/web-app/public/skills/hig-technologies/references/researchkit.md b/web-app/public/skills/hig-technologies/references/researchkit.md
new file mode 100644
index 00000000..01a1e24c
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/researchkit.md
@@ -0,0 +1,134 @@
+---
+title: "ResearchKit | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/researchkit
+
+# ResearchKit
+
+A research app lets people everywhere participate in important medical research studies.
+
+
+
+The ResearchKit framework provides predesigned screens and transitions that make it easy to design and build an engaging custom research app. For developer guidance, see [Research & Care > ResearchKit](https://www.researchandcare.org/researchkit/).
+
+These guidelines are for informational purposes only and don’t constitute legal advice. Contact an attorney to obtain advice with respect to the development of a research app and any applicable laws.
+
+## [Creating the onboarding experience](https://developer.apple.com/design/human-interface-guidelines/researchkit#Creating-the-onboarding-experience)
+
+When opening a research app for the first time, people encounter a series of screens that introduce them to the study, determine their eligibility to participate, request permission to proceed with the study, and, when appropriate, grant access to personal data. These screens aren’t typically revisited once they’ve been completed, so clarity is essential.
+
+**Always display the onboarding screens in the correct order.**
+
+
+
+### [1\. Introduction](https://developer.apple.com/design/human-interface-guidelines/researchkit#1-Introduction)
+
+**Provide an introduction that informs and provides a call to action.** Clearly describe the subject and purpose of your study. Also allow existing participants to quickly log in and continue an in-progress study.
+
+
+
+### [2\. Determine eligibility](https://developer.apple.com/design/human-interface-guidelines/researchkit#2-Determine-eligibility)
+
+**Determine eligibility as soon as possible.** People don’t need to move on to the consent section if they’re not eligible for the study. Only present eligibility requirements that are necessary for your study. Use simple, straightforward language that describes the requirements, and make it easy to enter information.
+
+
+
+### [3\. Get informed consent](https://developer.apple.com/design/human-interface-guidelines/researchkit#3-Get-informed-consent)
+
+**Make sure participants understand your study before you get their consent.** ResearchKit helps you make the consent process concise and friendly, while still allowing you to incorporate into the consent any legal requirements or requirements set by an institutional review board or ethics review board. Make sure that your app complies with the applicable App Store Guidelines, including the consent requirements. Typically, the consent section explains how the study works, ensures that participants understand the study and their responsibilities, and gets the participant’s consent.
+
+**Break a long consent form into easily digestible sections.** Each section can cover one aspect of the study, such as data gathering, data use, potential benefits, possible risks, time commitment, how to withdraw, and so on. For each section, use simple, straightforward language to provide a high-level overview. If necessary, provide a more detailed explanation of the section that participants can read by tapping a Learn More button. Participants need to be able to view the entire consent form before they agree to participate.
+
+**If it makes sense, provide a quiz that tests the participant’s understanding.** You might do this for questions the participant would otherwise be asked when obtaining consent in person.
+
+
+
+**Get the participant’s consent and, if appropriate, some contact information.** After agreeing to join the study, participants receive a confirmation dialog, followed by screens in which they provide their signature and contact details. Most research apps email participants a PDF version of the consent form for their records.
+
+
+
+### [4\. Request permission to access data](https://developer.apple.com/design/human-interface-guidelines/researchkit#4-Request-permission-to-access-data)
+
+**Get permission to access the participant’s device or data, and to send notifications.** Clearly explain why your research app needs access to location, Health, or other data, and don’t request access to data that isn’t critical to your study. If your app requires it, also ask for permission to send notifications to the participant’s device.
+
+
+
+## [Conducting research](https://developer.apple.com/design/human-interface-guidelines/researchkit#Conducting-research)
+
+To get input from participants, your study might use surveys, active tasks, or a combination of both. Depending on the architecture of your study, participants may interact with each section multiple times or only once.
+
+**Create surveys that keep participants engaged.** ResearchKit provides many customizable screens you can use in your surveys, and makes it easy to present questions that require different types of answers, such as true or false, multiple choice, dates and times, sliding scales, and open-ended text entry. As you use ResearchKit screens to design a survey, follow these guidelines to provide a great experience:
+
+ * Tell participants how many questions there are and about how long the survey will take.
+
+ * Use one screen per question.
+
+ * Show participants their progress in the survey.
+
+ * Keep the survey as short as possible. Several short surveys tend to work better than one long survey.
+
+ * For questions that require some additional explanation, use the standard font for the question and a slightly smaller font for the explanatory text.
+
+ * Tell participants when the survey is complete.
+
+
+
+
+
+
+**Make active tasks easy to understand.** An active task requires the participant to engage in an activity, such as speaking into the microphone, tapping fingers on the screen, walking, or performing a memory test. Follow these guidelines to encourage participants to perform an active task and give them the best chance of success:
+
+ * Describe how to perform the task using clear, simple language.
+
+ * Explain any requirements, such as if the task must be performed at a particular time or under specific circumstances.
+
+ * Make sure participants can tell when the task is complete.
+
+
+
+
+
+
+## [Managing personal information and providing encouragement](https://developer.apple.com/design/human-interface-guidelines/researchkit#Managing-personal-information-and-providing-encouragement)
+
+ResearchKit offers a profile screen you can use to let participants manage personal information while they’re in your research app. It’s also a good idea to design a custom screen that motivates people and gives them a way to track progress in the study. Ideally, both screens are accessible at all times in your app.
+
+**Use a profile to help participants manage personal data related to your study.** A profile screen can let people edit data that might change during the course of the study — such as weight or sleep habits — and remind them of upcoming activities. A profile screen can also provide an easy way to leave a study and view important information, such as the consent document and privacy policy.
+
+
+
+**Use a dashboard to show progress and motivate participants to continue.** If appropriate for your study, use a dashboard to provide encouraging feedback, such as daily progress, weekly assessments, results from specific activities, and even results that compare the participant’s results with aggregated results from others in the study.
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/researchkit#Platform-considerations)
+
+ _No additional considerations for iOS or iPadOS. Not supported in macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/researchkit#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/researchkit#Related)
+
+[Research & Care > ResearchKit](https://www.researchandcare.org/researchkit/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/researchkit#Developer-documentation)
+
+[Research & Care > Developers](https://www.researchandcare.org/developers/)
+
+[Protecting user privacy](https://developer.apple.com/documentation/HealthKit/protecting-user-privacy) — HealthKit
+
+[ResearchKit GitHub project](https://github.com/ResearchKit/ResearchKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/researchkit#Videos)
+
+[ What's new in CareKit ](https://developer.apple.com/videos/play/wwdc2020/10151)
+
+[ Build a research and care app, part 1: Setup onboarding ](https://developer.apple.com/videos/play/wwdc2021/10068)
+
+[ ResearchKit and CareKit Reimagined ](https://developer.apple.com/videos/play/wwdc2019/217)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/researchkit#Change-log)
+
+Date| Changes
+---|---
+September 12, 2023| Updated artwork.
+
diff --git a/web-app/public/skills/hig-technologies/references/shareplay.md b/web-app/public/skills/hig-technologies/references/shareplay.md
new file mode 100644
index 00000000..d7ac3256
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/shareplay.md
@@ -0,0 +1,142 @@
+---
+title: "SharePlay | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/shareplay
+
+# SharePlay
+
+SharePlay helps multiple people share activities — like viewing a movie, listening to music, playing a game, or sketching ideas on a whiteboard — while they’re in a FaceTime call or Messages conversation.
+
+
+
+The system synchronizes app playback on all participating devices to support seamless media and content sharing that lets everyone enjoy the experience simultaneously. In visionOS, SharePlay helps people enjoy these experiences while they’re together in the same virtual space.
+
+When someone shares content during a FaceTime call, the system asks each participant to launch the app to begin the experience. If people don’t have the app installed, the SharePlay alert encourages them to download it from the App Store. If you make the platform-specific versions of your app available as a [Universal Purchase](https://developer.apple.com/support/universal-purchase/), people can make one purchase and use your app and their in-app purchases across all the platforms you support.
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/shareplay#Best-practices)
+
+**Let people know that you support SharePlay.** People often expect media playback experiences to be shareable, so indicate this capability in your interface. For example, you can use the `shareplay` SF Symbol to identify the content or experiences in your app that support SharePlay.
+
+**If part of your app requires a subscription, consider ways to help nonsubscriber participants quickly join a group activity.** For example, you might offer temporary or provisional access to nonsubscribers or let an existing subscriber send a one-time pass to a friend. To make it easy for family members to share your content in a SharePlay experience, you can support [Family Sharing](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Supporting-Family-Sharing). If people can start a subscription during a SharePlay experience, present a streamlined version of your sign-up flow so they can join the activity without making others wait. For guidance, see [Auto-renewable subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Auto-renewable-subscriptions).
+
+**Support Picture in Picture (PiP) when possible.** On iPhone and iPad, people can open a shared video in a PiP window. On a Mac, a shared video opens in a background window that people can move into the foreground when they want to watch.
+
+**Use the term _SharePlay_ correctly.** You can use _SharePlay_ as a noun — as in “Join SharePlay” — and also as a verb when describing a direct action in your interface. For example, in a button or sheet that lets people share a movie-viewing activity, you can use a phrase like “SharePlay Movie.” Avoid using an adjective with SharePlay; for example, in your visionOS app, don’t add terms like _virtual_ or _spatial_. Avoid changing the term _SharePlay_ in any way; for example, don’t use variations like _SharePlayed_ , _SharePlays_ , or _SharePlaying_.
+
+## [Sharing activities](https://developer.apple.com/design/human-interface-guidelines/shareplay#Sharing-activities)
+
+An _activity_ is an app-defined type of shareable experience. For example, an app that lets people view videos might define a separate activity for viewing each type of content — like movies, TV shows, and uploaded videos — and display a different description for each activity. You can define as many different activities as make sense in your app. For developer guidance, see [Defining your app’s SharePlay activities](https://developer.apple.com/documentation/GroupActivities/defining-your-apps-shareplay-activities).
+
+**Briefly describe each activity.** When people receive an invitation to participate in an activity, your description helps them understand the experience they’re about to share. For example, a video-viewing app might associate its descriptive movie view with a movie-viewing activity. In this case, the descriptive view might display a movie’s title, a plot summary, and a poster image. Write a simple, meaningful description that’s short enough to avoid truncation.
+
+**Make it easy to start sharing an activity.** If there’s no session available when people start a shareable activity, you can present UI that lets them start a group activity. In response, the system asks people if they want to share or continue the experience solo.
+
+
+
+
+
+**Help people prepare to join a session before displaying the activity.** For example, if people must log in, download content, or make a payment before they can participate, display views that help them perform these tasks before showing the activity UI. Make these tasks as simple and effortless as possible so people can join the group activity quickly.
+
+**When possible, defer app tasks that might delay a shared activity.** For example, if your app needs to know a participant’s profile, consider asking for this information at a convenient time, like when playback pauses or finishes.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/shareplay#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, or tvOS. Not supported in watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/shareplay#visionOS)
+
+People expect most visionOS apps to support SharePlay. While wearing Apple Vision Pro, people choose the Spatial option in FaceTime to share content and activities with others.
+
+In a shared activity, FaceTime can show representations of other participants — called spatial Personas — within each wearer’s space, making everyone feel like they’re sharing the same experience in the same place. During a shared experience in FaceTime, people can interact with each other in natural ways through their spatial Personas. For example, people can speak or gesture directly to others, tell when someone is paying attention to them, and know which person is using a shared tool or resource.
+
+visionOS uses the concept of _shared context_ to describe the characteristics of a shared activity that help people feel physically present with others while connecting over the same content. A shared context helps give people confidence that they’re experiencing the same thing as everyone else.
+
+When people feel that they’re truly sharing an experience, social dynamics can encourage authentic, intuitive interactions. For example, people can communicate verbally and nonverbally to make plans, take turns, and share resources.
+
+Note
+
+During a shared activity, the system helps preserve people’s privacy by obscuring some visual details about wearers. In addition, a person can adjust their spatial Persona if they want. Although the system can place spatial Personas shoulder to shoulder and it supports shared gestures like a handshake or “high five,” spatial Personas remain apart.
+
+**Choose the spatial Persona template that suits your shared activity.** When you design a shared activity, you can use a spatial Persona template to specify a layout for arranging spatial Personas in the shared activity space. The system provides three spatial Persona templates: side-by-side, surround, and conversational.
+
+The side-by-side template places participants next to each other along a curved line segment, all facing the shared content. The side-by-side template gives everyone a great view of the content, making it a good choice for helping people watch media together. Because people aren’t facing each other in this arrangement, the side-by-side template can encourage less nonverbal interaction than other spatial Persona templates.
+
+
+
+The system-applied surround template arranges participants all the way around the shared content in the center. This spatial Persona template works especially well when the content is 3D, because each participant views it from a different angle. In the surround template, participants face each other as if they were grouped around a table, promoting both verbal and nonverbal interactions.
+
+
+
+The conversational template also groups participants around a center point, but places your content along the circle, not at its center. Because of this position, not everyone has the same view of your content, and it might not be convenient for everyone to interact with it. Consider using the conversational arrangement if your experience is more about people being together while your app performs a task in the background like playing music.
+
+
+
+For developer guidance, see [`SystemCoordinator`](https://developer.apple.com/documentation/GroupActivities/SystemCoordinator) and [`SpatialTemplatePreference`](https://developer.apple.com/documentation/GroupActivities/SpatialTemplatePreference).
+
+**Be prepared to launch directly into your shared activity.** When one person shares your activity with others on a FaceTime call, the system minimizes friction by automatically launching your app for everyone. In this scenario, you want to avoid displaying any windows that aren’t related to the shared activity. For example, if people need to sign in before joining the activity, be sure to present this task in an autodismissible window that disappears as soon as people finish providing the required input.
+
+**Help people enter a shared activity together, but don’t force them.** When one participant changes their level of immersion, the system tells you so you can synchronize the experience for everyone. Before synchronizing, check whether changing a person’s level of immersion would disrupt their current task; if it would, offer them the choice to join the updated experience. For example, if someone is editing content in an unshared window, you might present an alert that lets them choose to transition. For guidance, see [Immersive experiences](https://developer.apple.com/design/human-interface-guidelines/immersive-experiences).
+
+**Smoothly update a shared activity when new participants join.** When someone joins an in-progress activity, you need to integrate them without disrupting the experience for everyone else. For example, it’s important to update shared immersive content to keep all participants synchronized. Also, consider designing ways to accommodate up to five participants in your arrangement, updating their positions as necessary.
+
+#### [Maintaining a shared context](https://developer.apple.com/design/human-interface-guidelines/shareplay#Maintaining-a-shared-context)
+
+When your shared activity runs in a Full Space, the system helps your app maintain a shared context by using a single coordinate system to arrange your content and all participants, automatically synchronizing the size, position, and orientation of your app for each person. You’re responsible for displaying objects, playing sounds, and supporting interactions in ways that enhance the feeling of sharing the experience.
+
+**Make sure everyone views the same state of your app.** If your app has more than one state — such as a media app that provides both minimal and theater-like viewing modes — you need to avoid letting different participants view different states, because doing so can diminish people’s sense of being together in a shared space. The exception to this is when someone needs to temporarily exit a shared activity; for guidance, see [Adjusting a shared context](https://developer.apple.com/design/human-interface-guidelines/shareplay#Adjusting-a-shared-context).
+
+**Use Spatial Audio to enrich your shared activity.** Playing Spatial Audio can help you strengthen the realism of the shared experience. For guidance, see [Playing audio](https://developer.apple.com/design/human-interface-guidelines/playing-audio).
+
+**When possible, let people discover natural, social solutions to confusions or conflicts that might arise during a shared experience.** For example, if only one participant at a time can use a virtual tool, avoid displaying UI, like tool-use controls or notifications, and instead let people speak or gesture to the group when they want to use the tool. If conflicts can arise during your shared activity — for example, if multiple people try to change the same content at the same time — consider implementing a simple rule, like last change wins, and letting people use the rule to define behavior that’s acceptable to the group.
+
+**Help people keep their private and shared content separate.** By default, the system clearly differentiates a shared window from windows that aren’t shared. For example, when people use Music to listen together, the shared Music window appears as a new window for everyone, while any individual’s open library window remains separate and unshared. If your app can open multiple windows, help people share the one they want and make it easy for them to distinguish shared from unshared windows. If possible, also let people drag content they want to share from a private window to a shared one.
+
+ * Private
+ * Selected
+ * Shared
+
+
+
+Content in a TV window is private by default.
+
+People can select the Share button to choose whether, and with whom, to share the viewing experience.
+
+When sharing, the app clearly communicates the shared state.
+
+#### [Adjusting a shared context](https://developer.apple.com/design/human-interface-guidelines/shareplay#Adjusting-a-shared-context)
+
+Sometimes, it makes sense to adjust the shared context of a shared activity so each participant can customize their experience, such as for comfort or accessibility. In other situations, strictly maintaining a shared context might decrease people’s enjoyment of the experience. For example, when content has only one ideal viewing angle, each participant might need their own.
+
+**Let people personalize their experience without changing the experience for others.** For example, people might need to adjust various settings, like volume or subtitles, to make views and interactions accessible or make themselves more comfortable.
+
+When sharing, two people watching the same video can choose separately whether to turn subtitles on or off.
+
+**Consider when to give each participant a unique view of the shared content.** Some content looks best when people view it from a specific perspective. For example, people can share a Spatial Capture in a standard window with other people’s spatial Personas visible around it. However, to perceive the depth in a Spatial Capture, each person needs to view it from the right angle. In this scenario, a person could temporarily transition to a Full Space that hides other participants and ensures the right viewing angle for them, even while everyone else continues to view the standard window and each other. If it makes sense to provide per-person versions of your shared content, be sure to continue synchronizing people’s positions and your app context to maintain the shared experience.
+
+**Make it easy for people to exit and rejoin a shared activity.** Sometimes, people need to perform an unrelated task in your app or a different one, or engage with their physical surroundings. When this happens, you need to present a control or other component that lets people quickly rejoin the shared activity. In addition, you might want to continue displaying the shared content so people can stay informed about the ongoing shared experience while they’re hiding their spatial Persona.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/shareplay#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/shareplay#Related)
+
+[Auto-renewable subscriptions](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase#Auto-renewable-subscriptions)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/shareplay#Developer-documentation)
+
+[Group Activities](https://developer.apple.com/documentation/GroupActivities)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/shareplay#Videos)
+
+[ Share visionOS experiences with nearby people ](https://developer.apple.com/videos/play/wwdc2025/318)
+
+[ Design spatial SharePlay experiences ](https://developer.apple.com/videos/play/wwdc2023/10075)
+
+[ Add SharePlay to your app ](https://developer.apple.com/videos/play/wwdc2023/10239)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/shareplay#Change-log)
+
+Date| Changes
+---|---
+December 5, 2023| Added artwork for visionOS.
+June 21, 2023| Updated to include guidance for visionOS.
+December 19, 2022| Clarified guidance for helping nonsubscribers join a group activity.
+
diff --git a/web-app/public/skills/hig-technologies/references/shazamkit.md b/web-app/public/skills/hig-technologies/references/shazamkit.md
new file mode 100644
index 00000000..03d0cfd2
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/shazamkit.md
@@ -0,0 +1,47 @@
+---
+title: "ShazamKit | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/shazamkit
+
+# ShazamKit
+
+ShazamKit supports audio recognition by matching an audio sample against the ShazamKit catalog or a custom audio catalog.
+
+
+
+You can use ShazamKit to provide features like:
+
+ * Enhancing experiences with graphics that correspond with the genre of currently playing music
+
+ * Making media content accessible to people with hearing disabilities by providing closed captions or sign language that syncs with the audio
+
+ * Synchronizing in-app experiences with virtual content in contexts like online learning and retail
+
+
+
+
+If you need the device microphone to get audio samples for your app to recognize, you must request access to it. As with all types of permission requests, it’s important to help people understand why you’re asking for access. For guidance, see [Privacy](https://developer.apple.com/design/human-interface-guidelines/privacy).
+
+
+
+## [Best practices](https://developer.apple.com/design/human-interface-guidelines/shazamkit#Best-practices)
+
+After you receive permission to access the microphone for features that use ShazamKit, follow these guidelines.
+
+**Stop recording as soon as possible.** When people allow your app to record audio for recognition, they don’t expect the microphone to stay on. To help preserve privacy, only record for as long as it takes to get the sample you need.
+
+**Let people opt in to storing your app’s recognized songs to their iCloud library.** If your app can store recognized songs to iCloud, give people a way to first approve this action. Even though both the Music Recognition control and the Shazam app show your app as the source of the recognized song, people appreciate having control over which apps can store content in their library.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/shazamkit#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/shazamkit#Resources)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/shazamkit#Developer-documentation)
+
+[ShazamKit](https://developer.apple.com/documentation/ShazamKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/shazamkit#Videos)
+
+[ Explore ShazamKit ](https://developer.apple.com/videos/play/wwdc2021/10044)
+
diff --git a/web-app/public/skills/hig-technologies/references/sign-in-with-apple.md b/web-app/public/skills/hig-technologies/references/sign-in-with-apple.md
new file mode 100644
index 00000000..e7b0bad8
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/sign-in-with-apple.md
@@ -0,0 +1,288 @@
+---
+title: "Sign in with Apple | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple
+
+# Sign in with Apple
+
+Sign in with Apple provides a fast, private way to sign into apps and websites, giving people a consistent experience they can trust and the convenience of not having to remember multiple accounts and passwords.
+
+
+
+Supporting Sign in with Apple lets people use the Apple Account they already have to sign in or sign up, and skip filling out forms, verifying email addresses, and choosing passwords. In cases where you choose to ask for a name and email address, people have the option to share a unique, random email address that automatically relays messages to their personal email address. For developer guidance, see [Authentication Services](https://developer.apple.com/documentation/AuthenticationServices).
+
+You can offer Sign in with Apple in every version of your app or website across all platforms — including non-Apple platforms.
+
+Sign in with Apple makes it easy for people to authenticate with Face ID, Touch ID, or Optic ID and has two-factor authentication built in for an added layer of security. Apple doesn’t use Sign in with Apple to profile people or their activity in apps.
+
+## [Offering Sign in with Apple](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Offering-Sign-in-with-Apple)
+
+Follow these guidelines to offer Sign in with Apple when it’s most convenient for people.
+
+**Ask people to sign in only in exchange for value.** People need to understand why you’re asking them to sign in, so it can work well to display a brief, approachable description of sign-in benefits. For example, you might want to tell people that signing in lets them personalize the app experience, access additional features, or synchronize data.
+
+**Delay sign-in as long as possible.** People often abandon apps when they’re forced to sign in before doing anything useful. Give them a chance to familiarize themselves with your app before making a commitment. For example, a live-streaming app could let people explore available content before signing in to stream something.
+
+**If you require an account, ask people to set it up before offering any sign-in options.** Start by explaining the reasons for requiring an account. Then, after people complete account setup, let them choose a convenient way to sign in to their new account by offering Sign in with Apple and any other sign-in methods you support.
+
+**Consider letting people link an existing account to Sign in with Apple.** When you support this type of linking, people can get the convenience of using Sign in with Apple while maintaining access to the information in an account they’ve already set up. You can offer account linking before or after people sign in to their existing account. For example:
+
+ * If people share an email address through Sign in with Apple and it matches the address in an existing account, you can suggest that they link Sign in with Apple to that account.
+
+ * If people used an existing user name and password to sign in, you can display an account-linking suggestion in their account’s settings view or another logical place.
+
+
+
+
+**In a commerce app, wait until after people make a purchase before asking them to create an account.** If you support a guest checkout system, give people a quick way to create an account after the transaction completes. For example, if you support Apple Pay, let people create an account on the order confirmation page. In cases where people have already provided their name and email address during the Apple Pay transaction, you don’t need to ask for this information.
+
+
+
+**As soon as Sign in with Apple completes, welcome people to their new account.** Help people use their new account right away; don’t delay the experience by asking for information that isn’t required.
+
+**Indicate when people are currently signed in.** You can help people confirm their sign-in method by displaying a phrase like “Using Sign in with Apple” in places like a settings or account interface.
+
+## [Collecting data](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Collecting-data)
+
+People appreciate Sign in with Apple for its privacy and convenience. Although some apps or websites may require additional information — such as a date of birth or a region of residence — it’s essential to minimize your requests for data as people set up an account. Build on the trust that people have in Sign in with Apple by describing why you need additional data and clearly displaying the data you receive.
+
+**Clarify whether the additional data you request is required or just recommended.** If the data is legally or contractually required — such as an agreement to terms of service, country or region of residence, birth date, or information required by a region’s real-identity laws — make sure people understand that they must supply the additional information to complete the setup of their account. If additional data isn’t required but can improve the user experience, make sure people know the request is optional and help them understand the benefits of providing the information.
+
+**Don’t ask people to supply a password.** A key benefit of Sign in with Apple is that people don’t have to create and memorize additional passwords. Unless people have stopped using Sign in with Apple with your app or website, don’t ask for a password.
+
+**Avoid asking for a personal email address when people supply a private relay address.** Using Sign in with Apple, people can choose to share a private relay address that automatically forwards messages to their verified personal email account. It’s essential to respect this choice and avoid overriding it by asking for a personal email address. If you present customer service, retail, or other experiences that request identification via email address, you can:
+
+ * Make sure that people can view their private relay address in your app or website
+
+ * Direct people to Settings > Apple Account > Password & Security > Apps using Apple Account to retrieve their private relay address
+
+ * Use other identifying values, like an order number or phone number collected as part of a purchase
+
+
+
+
+**Give people a chance to engage with your app before asking for optional data.** As people use your app, you can help them discover places where they can benefit from sharing more information with you. For example, you might suggest that they provide a contact phone number if they want real-time text updates, or social network information if they want to play games with friends. If people choose not to provide optional information, don’t prevent them from accessing their account or using all the features of your app.
+
+**Be transparent about the data you collect.** People value knowing how you use the data that they share with you. One way you can be transparent is to welcome people by using the name or email address they shared. Doing this helps establish how you use this information and, for a relay address, shows people where to find it in the future. If you don’t display all the data that people provide, they are likely to wonder why you asked for it.
+
+## [Displaying buttons](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Displaying-buttons)
+
+Apple provides several Sign in with Apple buttons you can use to let people set up an account and sign in. If necessary, you can create a custom button to offer Sign in with Apple; for guidelines, see [Creating a custom Sign in with Apple button](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Creating-a-custom-Sign-in-with-Apple-button).
+
+**Prominently display a Sign in with Apple button.** Make a Sign in with Apple button no smaller than other sign-in buttons, and avoid making people scroll to see the button.
+
+### [Using the system-provided buttons](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Using-the-system-provided-buttons)
+
+When you use the system-provided APIs to create a Sign in with Apple button, you get the following advantages.
+
+ * A button that’s guaranteed to use an Apple-approved appearance
+
+ * Assurance that the button’s contents maintain ideal proportions as you change its style
+
+ * Automatic translation of the button’s title into the language specified by the device
+
+ * Support for configuring the button’s corner radius to match the style of your UI (iOS, macOS, and web)
+
+ * A system-provided alternative text label that lets VoiceOver describe the button
+
+
+
+
+For developer guidance, see [`ASAuthorizationAppleIDButton`](https://developer.apple.com/documentation/AuthenticationServices/ASAuthorizationAppleIDButton) (iOS, macOS, and tvOS), [`WKInterfaceAuthorizationAppleIDButton`](https://developer.apple.com/documentation/WatchKit/WKInterfaceAuthorizationAppleIDButton) (watchOS), and [Displaying Sign in with Apple buttons on the web](https://developer.apple.com/documentation/signinwithapple/displaying-sign-in-with-apple-buttons-on-the-web). You can also visit [Sign in with Apple button](https://appleid.apple.com/signinwithapple/button) to view and adjust live previews of web-based buttons and get the code.
+
+The system provides several variants of the button title. Depending on the platform on which your content runs, choose the variant that fits the terminology of your sign-in experience and use it consistently throughout your interfaces.
+
+The following button titles are available for iOS, macOS, tvOS, and the web:
+
+
+
+
+
+
+
+For watchOS, the system provides one title: Sign in.
+
+
+
+Depending on the platform, the system provides up to three options for the appearance of the Sign in with Apple button: white, white with an outline, and black. Choose the appearance that works best with the background on which the button displays.
+
+#### [White](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#White)
+
+The white style is available on all platforms and the web. Use this style on dark backgrounds that provide sufficient contrast.
+
+
+
+
+
+
+
+
+
+#### [White with outline](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#White-with-outline)
+
+The white outlined style is available in iOS, macOS, and the web. Use this style on white or light-color backgrounds that don’t provide sufficient contrast with the white button fill. Avoid using this style on a dark or saturated background, because the black outline can add visual clutter; instead, use the [white](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#White) style to contrast with a dark background.
+
+
+
+
+
+
+
+
+
+#### [Black](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Black)
+
+The black style is available on all platforms and the web. Use this style on white or light-color backgrounds that provide sufficient contrast; don’t use it on black or dark backgrounds.
+
+
+
+
+
+
+
+
+
+Unlike the black Sign in with Apple button for other platforms, the watchOS button uses a fill color that’s not fully black. To contrast with the pure black background of Apple Watch, the watchOS button uses the system-defined dark gray appearance.
+
+
+
+#### [Button size and corner radius](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Button-size-and-corner-radius)
+
+**Adjust the corner radius to match the appearance of other buttons in your app.** By default, the Sign in with Apple button has rounded corners. In iOS, macOS, and the web, you can change the corner radius to produce a button with square corners or a capsule-shape button. For developer guidance, see [`cornerRadius`](https://developer.apple.com/documentation/AuthenticationServices/ASAuthorizationAppleIDButton/cornerRadius) (iOS and macOS) and [Displaying Sign in with Apple buttons on the web](https://developer.apple.com/documentation/signinwithapple/displaying-sign-in-with-apple-buttons-on-the-web).
+
+Minimum corner radius
+
+Default corner radius
+
+Maximum corner radius
+
+**Maintain the minimum button size and margin around the button in iOS, macOS, and the web.** Be mindful that the button title may vary in length depending on the locale. Use the following values for guidance.
+
+Minimum width| Minimum height| Minimum margin
+---|---|---
+140pt (140px @1x, 280px @2x)| 30pt (30px @1x, 60px @2x)| 1/10 of the button’s height
+
+### [Creating a custom Sign in with Apple button](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Creating-a-custom-Sign-in-with-Apple-button)
+
+If your interface requires it, you can create a custom Sign in with Apple button for iOS, macOS, or the web. For example, you may want to align logos across multiple sign-in buttons, use buttons that display only a logo, or adjust the button’s font, bezel, or background appearance to coordinate with your UI.
+
+
+
+Always make sure that people can instantly identify your custom button as a Sign in with Apple button. If your custom button differs too much from the standard one, people may not feel comfortable using it to set up an account or sign in. App Review evaluates all custom Sign in with Apple buttons.
+
+[Apple Design Resources](https://developer.apple.com/design/resources/) provides downloadable Apple logo artwork you can use to create custom Sign in with Apple buttons that display either a logo only or a logo and text. The logo files are available in PNG, SVG, and PDF formats, and the artwork for both types of buttons includes both black and white versions. Here are examples of the black and white logo-only art files, each with a background added for visibility.
+
+
+
+
+
+All downloadable logo files include padding that simplifies positioning the logo in a button. Logo-only logo files include horizontal and vertical padding that ensures the correct proportion of the logo relative to the button. In addition to padding that keeps the logo and button correctly proportioned, logo files for buttons with text also include horizontal padding that provides a minimum margin between the logo and the button’s leading edge and title.
+
+Use only the logo artwork downloaded from [Apple Design Resources](https://developer.apple.com/design/resources/); never create a custom Apple logo. As you create a custom Sign in with Apple button, follow these guidelines for using the downloadable logo file:
+
+ * Use the logo file to position the Apple logo in a button; never use the Apple logo as a button.
+
+ * Match the height of the logo file to the height of the button.
+
+ * Don’t crop the logo file.
+
+ * Don’t add vertical padding.
+
+
+
+
+To make sure that your custom button is visually consistent with the system-provided Sign in with Apple button, don’t change the following attributes.
+
+ * Titles. Use only _Sign in with Apple_ , _Sign up with Apple_ , or _Continue with Apple_.
+
+ * General shape. Buttons that combine the logo with text are always rectangular; logo-only buttons can be circular or rectangular.
+
+ * Logo and title colors. Within a button, both items must be either black or white; don’t use custom colors.
+
+
+
+
+To coordinate with your app design, you can change:
+
+ * Title font. You can also adjust the font’s weight and size.
+
+ * Title case. You can capitalize every letter in the title.
+
+ * Background appearance. The overall color needs to remain black or white. If necessary, you can include a subtle texture or gradient to help the button harmonize with your interface.
+
+ * Button corner radius. You can use a corner radius value that matches the other buttons in your UI.
+
+ * Button bezel and shadow. For example, you can use a stroke to emphasize the button bezel or add a drop shadow.
+
+
+
+
+#### [Custom buttons with a logo and text](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Custom-buttons-with-a-logo-and-text)
+
+**Choose the format of the logo file based on the height of your button.** Because SVG and PDF are vector-based formats, you can use these files in buttons of any height. Use the PNG files only in buttons that are 44 points tall, which is the default (and recommended) button height in iOS. Logos are available in small, medium, and large sizes, so you can match logo sizes in all the sign-up buttons you display.
+
+**Prefer the system font for the title — that is, Sign in with Apple, Sign up with Apple, or Continue with Apple.** Regardless of the font you choose, the title and button height of your custom button need to use the same proportions that the system uses. Using the system font for example, the title’s font size would be 43% of the button’s height — in other words, the button’s height would be 233% of the title’s font size, rounded to the nearest integer. Here are two examples that show these proportions using different sizes of the system font.
+
+
+
+
+
+**In general, preserve the capitalization style of the title.** By default, all variants of the button title capitalize the first word — that is, _Sign_ or _Continue_ — and _Apple_ ; all other letters are lowercase. Avoid changing this style unless your interface uses only uppercase.
+
+**Keep the title and logo vertically aligned within the button.** To do this, vertically align the title to the middle of the button, then add the logo image, making sure its height matches the height of the button. Because the logo image includes top and bottom padding, vertically aligning the title in the button ensures that the title, the logo, and the button stay properly aligned.
+
+**Inset the logo if necessary.** If you need to horizontally align the Apple logo with other authentication logos, you can adjust the space between the logo and the button’s leading edge.
+
+**Maintain a minimum margin between the title and the right edge of the button.** Ensure the margin measures at least 8% of the button’s width.
+
+**Maintain the minimum button size and margin around the button.** Be mindful that the button title may vary in length depending on the locale. Use the following values for guidance.
+
+Minimum width| Minimum height| Minimum margin
+---|---|---
+140 pt (140 px @1x, 280 px @2x)| 30 pt (30 px @1x, 60 px @2x)| 1/10 of the button’s height
+
+#### [Custom logo-only buttons](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Custom-logo-only-buttons)
+
+**Choose the format of the logo file based on the size of your button.** The downloadable artwork for logo-only buttons is available in SVG, PDF, and PNG formats. Use the vector-based SVG and PDF formats for buttons of any size; use the PNG format only in buttons that measure 44x44 pt.
+
+**Don’t add horizontal padding to a logo-only image.** A logo-only Sign in with Apple button always has a 1:1 aspect ratio, and the artwork already includes the correct padding on all sides.
+
+**Use a mask to change the default square shape of the logo-only image.** For example, you might want to use a circular or rounded rectangular shape to present all logo-only sign-in buttons. Never crop the Apple-provided artwork to decrease its built-in padding or use the logo by itself, and avoid including additional padding.
+
+Rounded rectangle mask
+
+No mask
+
+Circular mask
+
+**Maintain a minimum margin around the button.** Ensure the margin measures at least 1/10 of the button’s height.
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Related)
+
+[Sign in with Apple button](https://appleid.apple.com/signinwithapple/button)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Developer-documentation)
+
+[Authentication Services](https://developer.apple.com/documentation/AuthenticationServices)
+
+[Displaying Sign in with Apple buttons on the web](https://developer.apple.com/documentation/signinwithapple/displaying-sign-in-with-apple-buttons-on-the-web) — Sign in with Apple
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Videos)
+
+[ Move beyond passwords ](https://developer.apple.com/videos/play/wwdc2021/10106)
+
+[ Simplify sign in for your tvOS apps ](https://developer.apple.com/videos/play/wwdc2021/10279)
+
+[ Introducing Sign In with Apple ](https://developer.apple.com/videos/play/wwdc2019/706)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple#Change-log)
+
+Date| Changes
+---|---
+September 14, 2022| Refined guidance on supporting existing accounts, helping people set up a new account, and indicating the current sign-in status. Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/siri.md b/web-app/public/skills/hig-technologies/references/siri.md
new file mode 100644
index 00000000..41e0c03c
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/siri.md
@@ -0,0 +1,523 @@
+---
+title: "Siri | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/siri
+
+# Siri
+
+Siri makes it easy for people to accomplish everyday tasks quickly, using voice, touch, or automation.
+
+
+
+When you use [SiriKit](https://developer.apple.com/documentation/SiriKit) to define the tasks and actions that your app supports, people can use Siri to perform them even when your app isn’t running. If you’re an accessory maker, you can also help people use Siri to control your accessories by integrating them with [HomeKit](https://developer.apple.com/design/human-interface-guidelines/homekit) or [AirPlay](https://developer.apple.com/design/human-interface-guidelines/airplay). Here are some of the ways people can use Siri to interact with your app or accessory:
+
+ * Ask Siri to perform a system-defined task that your app supports, like send a message, play a song, or start a workout.
+
+ * Run a _shortcut_ , which is a way to accelerate actions your app defines through onscreen interactions or by voice.
+
+ * Use the Shortcuts app to adjust what a shortcut does, including combining several actions to perform one multistep shortcut.
+
+ * Tap a _suggestion_ to perform a shortcut with your app (Siri can _suggest_ shortcuts that people might want to perform, based on their current context and the information you provide).
+
+ * Use Siri to control an accessory that integrates with your app.
+
+
+
+
+Siri works with your products on iPhone, iPad, Mac, Apple Watch, HomePod, and AirPods, so people can use it almost everywhere.
+
+When you make your app’s tasks available through Siri, you have several opportunities to customize the user experience. At a fundamental level, you customize the flow and functionality of the everyday tasks and actions you support to implement your business requirements. To reinforce this functionality throughout the user experience, you can write dialogue that reflects the style and tone of your company’s communications and design custom UI that incorporates your app’s visual style into the Siri interface.
+
+As you approach the job of integrating your app with Siri, assess the actions your app performs and learn how people use your app without voice interaction. Then consider the following steps:
+
+ * Identify key tasks in your app that people might want to perform on a regular basis.
+
+ * Drive engagement by telling the system about your app’s key tasks and by supporting suggestions.
+
+ * For actions that people can perform through voice interaction, design functional conversational flows that feel natural.
+
+ * Explore the various ways people might perform your app’s tasks — such as in a hands-free situation — and the devices they might be using, such as Apple Watch or iPad.
+
+
+
+
+## [Integrating your app with Siri](https://developer.apple.com/design/human-interface-guidelines/siri#Integrating-your-app-with-Siri)
+
+Tasks are at the core of your app’s integration with Siri. SiriKit builds on the idea of a person’s intention to perform a task by using the term _intent_ to represent a task an app supports. The communication between your app and Siri is based on the intents — that is, the tasks — your app helps people perform.
+
+SiriKit defines _system intents_ that represent common tasks — such as sending a message, calling a friend, and starting a workout — and groups related intents into domains. A _domain_ is a category of tasks that Siri knows how to talk about, like messaging, calling, and workouts. For a complete list of domains and the actions in each domain that iOS and watchOS support, see [System intents](https://developer.apple.com/design/human-interface-guidelines/siri#System-intents).
+
+When possible, take advantage of the intents that SiriKit defines. Using system-provided intents can make your job easier, while still giving you opportunities to customize the experience. However, if your app offers tasks that aren’t represented by system-defined intents — like ordering a meal or shopping for groceries — you can create a _custom intent_ (for guidance, see [Custom intents](https://developer.apple.com/design/human-interface-guidelines/siri#Custom-intents)).
+
+### [A closer look at intents](https://developer.apple.com/design/human-interface-guidelines/siri#A-closer-look-at-intents)
+
+When people use Siri to ask questions and perform actions, Siri does the language processing and semantic analysis needed to turn their requests into intents for your app to handle. The exception is the personal phrase that people create to run a shortcut: When people speak the exact phrase, Siri recognizes it without doing additional processing or analysis.
+
+As a designer, your main job is to present clear, actionable content that helps clarify and streamline the interactions people have with Siri to get things done in your app. Some of these interactions happen while your app and SiriKit communicate about handling the intent, so it’s helpful to be familiar with the related SiriKit terminology. At a high level, your app processes an intent in three phases: resolve, confirm, and handle.
+
+First, your app and SiriKit must agree on what the request means in the _resolve_ phase. You can think of this phase as the time to ask people for everything your app needs and, if necessary, ask for additional information or clarification. For example, if people ask to send a message to Amy, and they have multiple contacts named Amy, a messaging app can have Siri ask which Amy they mean. Details related to an intent, like a message recipient’s name, are known as _parameters_. In the resolve phase, you can indicate the parameters that are required to complete an action and those that are optional. For developer guidance, see [Resolving the Parameters of an Intent](https://developer.apple.com/documentation/SiriKit/resolving-the-parameters-of-an-intent).
+
+The second phase — called the _confirm_ phase — happens when you have all the information you need to handle the intent. This phase can give people a chance to make sure they want to complete the task. For example, tasks that have financial impact require confirmation. In addition to asking for a person’s consent, you can present an error during this phase if something will prevent your app from completing the action. For example, if people use an app to order an item for pickup when the pickup location is closed, the app can describe why it can’t complete the action right now. Presenting this error during the confirm phase avoids making people wait until they’re paying for the item to find out that their request has failed. For developer guidance, see [Confirming the Details of an Intent](https://developer.apple.com/documentation/SiriKit/confirming-the-details-of-an-intent).
+
+Third, your app performs the task and tells SiriKit what it actually did in the _handle_ phase. You can provide both visual and textual information that tells people what your app did to handle their request. For example, an app that lets people order coffee might present a receipt that describes the order. Siri can speak or display the information your app provides. For developer guidance, see [Handling an Intent](https://developer.apple.com/documentation/SiriKit/handling-an-intent).
+
+### [Provide information about actions and support suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Provide-information-about-actions-and-support-suggestions)
+
+Most apps support large numbers of actions, but people tend to perform only a handful of them on a regular basis. When you tell the system about people’s regular actions and describe new ones you think they’ll want to perform in the future, Siri can _suggest_ shortcuts for both types of actions when people are likely to be interested in them.
+
+For example, in an app that’s all about coffee, the most frequent action might be to order a cup of coffee, while less frequent actions might include buying coffee beans or locating a new coffee shop. In this example, the coffee app would share information about the _order coffee_ action so that Siri can suggest a shortcut for this action when people usually want to do it, like weekday mornings. The app could also tell Siri about an action that people haven’t performed yet, but might be interested in — like ordering a new seasonal variation of their favorite coffee — so that Siri might suggest a shortcut for this action.
+
+Siri can use signals like location, time of day, and type of motion (such as walking, running, or driving), to intelligently predict just the right time and place to suggest actions from your app. Depending on the information your app shares and people’s current context, Siri can offer shortcut _suggestions_ on the lock screen, in search results, or on the [Siri watch face](https://support.apple.com/guide/watch/faces-and-features-apde9218b440/watchos#apdcc88df92c). Siri can also use some types of information to suggest actions that system apps support, such as using Calendar to add an event shared by your app. Here are some example scenarios.
+
+ * Shortly before 7:30 a.m., Siri might suggest the _order coffee_ action to people who use the coffee app every morning.
+
+ * After people use a box office–type app to buy tickets to a movie, Siri might remind them to turn on Do Not Disturb shortly before showtime.
+
+ * Siri might suggest an automation that starts a workout in a person’s favorite workout app and plays their favorite workout playlist as they enter their usual gym.
+
+ * When people enter the airport after a home-bound flight, Siri might suggest they request a ride home from their favorite ride-sharing app.
+
+
+
+
+When you provide information about your actions to the system, people can also use the Shortcuts app to create shortcuts for the system and custom intents you support. For guidance, see [Shortcuts and suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions).
+
+### [Design a great voice experience](https://developer.apple.com/design/human-interface-guidelines/siri#Design-a-great-voice-experience)
+
+A great voice interface helps people feel confident they’ll get the results they want, even when they’re not sure what they can say. Siri supports different voice experiences for system-provided intents and custom intents. With a system intent, Siri does the natural language processing for you, letting people interact with your app in various conversational ways. With a custom intent, your app helps people perform a task that Siri doesn’t know about yet, which results in a different type of support for the voice experience. Custom intents give you additional opportunities to customize conversational dialogue, but also require people to create and speak a precise phrase to start the interaction.
+
+As a designer, you have several ways to enhance both types of conversational experiences and help people specify what they want without engaging in lengthy exchanges.
+
+For system-provided intents, you help Siri communicate with people about the action they want to accomplish by providing essential information and defining any app-specific terminology that might come up during the conversation. You don’t have to write additional dialogue for Siri to speak because Siri already knows about the actions in the system-defined domains and understands many ways that people may talk about them. For example, if you need to confirm the recipient’s name during the resolve phase of a messaging intent, you simply indicate that the required parameter value is missing and Siri says to the sender “Who do you want to send it to?”
+
+Even though you don’t write custom dialogue for system-provided intents, you can enhance the voice experience in other ways. For example, if people ask Siri to “play MyMusicApp” as they enter their gym, you could respond by playing their workout playlist.
+
+When you support a custom intent, people start the action by using their personal invocation phrase; if people don’t speak their phrase precisely, Siri doesn’t initiate the intent. Although you can suggest a memorable phrase for people to use, your principal job is to write clear, direct dialogue, often in the form of follow-up questions, to help people accomplish the action in as few steps as possible.
+
+For example, a coffee app might suggest _Order coffee_ as a phrase people could use to reorder a favorite cup of coffee. In a scenario where people usually use _Order coffee_ to order a cappuccino in various sizes, the coffee app could follow up with custom dialogue that builds on this knowledge, like “What size of cappuccino?” For other types of actions, more open-ended questions can be better at helping people accomplish the task efficiently. For example, if people start a grocery shopping action by saying _Add to cart_ , the grocery shopping app could follow up with “OK, what do you want?”
+
+### [Recognize that people use Siri in different contexts](https://developer.apple.com/design/human-interface-guidelines/siri#Recognize-that-people-use-Siri-in-different-contexts)
+
+People can use Siri to get things done while they’re in a car, working out, using apps on a device, or interacting with HomePod. You don’t always know the context in which people are using Siri to perform your app’s actions, so flexibility is key to help people have a great experience no matter what they’re doing.
+
+To communicate with people regardless of their current context, supply information that Siri can provide both vocally and visually. Supporting both voice and screen-based content lets Siri decide which communication method works best for people in their current situation. For example, Siri speaks to people through their AirPods if they say “Hey Siri” while using them.
+
+In voice-only situations, Siri verbally describes information that would have been presented onscreen in other situations. Consider a food-delivery app that requires people to confirm a transaction before completing the order. In a voice-only scenario, Siri may say “Your total is fifteen dollars, and your order will take thirty minutes to arrive at your door. Ready to order?” In contrast, when people can view the cost and delivery information onscreen, Siri might simply say “Ready to order?” When you support custom intents, you’re responsible for supplying the voice-only dialogue that describes these types of onscreen information.
+
+## [System intents](https://developer.apple.com/design/human-interface-guidelines/siri#System-intents)
+
+SiriKit defines a large number of system intents that represent common tasks people do, such as playing music, sending messages to friends, and managing notes. For system intents, Siri defines the conversational flow, while your app provides the data to complete the interaction.
+
+SiriKit provides the following intents.
+
+Domain (link to developer guidance)| Intents
+---|---
+[VoIP Calling](https://developer.apple.com/documentation/SiriKit/voip-calling)| Initiate calls.
+[Workouts](https://developer.apple.com/documentation/SiriKit/workouts)| Start, pause, resume, end, and cancel workouts.
+[Lists and Notes](https://developer.apple.com/documentation/SiriKit/lists-and-notes)| Create notes.
+Search for notes.
+Create reminders based on a date, time, or location.
+[Media](https://developer.apple.com/documentation/SiriKit/media)| Search for and play media content, such as video, music, audiobooks, and podcasts.
+Like or dislike items.
+Add items to a library or playlist.
+[Messaging](https://developer.apple.com/documentation/SiriKit/messaging)| Send messages.
+Search for messages.
+Read received messages.
+[Payments](https://developer.apple.com/documentation/SiriKit/payments)| Send payments.
+Request payments.
+[Car Commands](https://developer.apple.com/documentation/SiriKit/car-commands)| Activate hazard lights or honk the horn.
+Lock and unlock the doors.
+Check the current fuel or power level.
+
+### [Design responses to system intents](https://developer.apple.com/design/human-interface-guidelines/siri#Design-responses-to-system-intents)
+
+People use Siri for convenience, and they expect a fast response. Your app needs to perform the system intents it supports quickly and accurately so that people have a great experience when they choose your app to get things done.
+
+**Whenever possible, complete requests without leaving Siri.** If a request must be finished in your app, take people directly to the expected destination. Don’t show intermediary screens or messages that slow down the experience.
+
+**When a request has a financial impact, default to the safest and least expensive option.** Never deceive people or misrepresent information. For a purchase with multiple pricing levels, don’t default to the most expensive. When people make a payment, don’t charge extra fees without informing them.
+
+**When people request media playback from your app, consider providing alternative results if the request is ambiguous.** When you display alternative results within the Siri UI, people can easily choose a different piece of content if your first offering isn’t what they want.
+
+**On Apple Watch, design a streamlined workflow that requires minimal interaction.** Whenever possible, use intelligent defaults instead of asking for input. For example, a music app could respond to a nonspecific request — like “Play music with MyMusicApp” — by playing a favorite playlist. If you must present options to people, offer a small number of relevant choices that reduce the need for additional prompting.
+
+### [Enhance the voice experience for system intents](https://developer.apple.com/design/human-interface-guidelines/siri#Enhance-the-voice-experience-for-system-intents)
+
+Help people learn how to use Siri to get things done in your app, and make conversation with Siri feel natural in the context of your brand, by defining app-specific terms and alternative ways people might refer to your app.
+
+**Create example requests.** When people tap the Help button in the Siri interface, they view a guide that can include example phrases that you supply. Write phrases that demonstrate the easiest and most efficient ways to use Siri with your app. For developer guidance, see [Intent Phrases](https://developer.apple.com/documentation/SiriKit/intent-phrases).
+
+**Define custom vocabulary that people use with your app.** Help Siri learn more about the actions your app performs by defining specific terms people might actually use in requests, like account names, contact names, photo tags, photo album names, ride options, and workout names. Make sure these terms are nongeneric and unique to your app. Never include other app names, terms that are obviously connected with other apps, inappropriate language, or reserved phrases, like _Hey Siri_. Note that Siri uses the terms you define to help resolve requests, but there’s no guarantee that Siri will recognize them.
+
+**Consider defining alternative app names.** If people might refer to your app in different ways, it’s a good idea to provide a list of alternative names to help Siri understand what people mean. For example, a UnicornChat app might define the term _Unicorn_ as an alternative app name. Never impersonate other apps by listing their names as alternative names for your app.
+
+### [Design a custom interface for a system intent](https://developer.apple.com/design/human-interface-guidelines/siri#Design-a-custom-interface-for-a-system-intent)
+
+If it makes sense in your iOS app, you can supply custom interface elements or a completely custom UI for Siri or Maps to display along with your intent response. A watchOS app can’t provide a custom UI for Siri to display on Apple Watch.
+
+**Avoid including extraneous or redundant information.** A custom interface lets you bring elements from your app into the Siri interface, but displaying information that isn’t related to the action can distract people. You also want to avoid duplicating information that the system can display in the Siri or Maps interface. For developer guidance, see [`INParameter`](https://developer.apple.com/documentation/Intents/INParameter).
+
+**Make sure people can still perform the action without viewing your custom interface.** People can switch to voice-only interaction with Siri at any time, so it’s crucial to help Siri speak the same information that you display in your custom interface.
+
+**Use ample margins and padding in your custom interface.** Avoid extending content to the edges of your interface unless it’s content that appears to flow naturally offscreen, like a map. In general, provide a margin of 20 points between each edge of your interface and the content. Use the app icon that appears above your interface to guide alignment: content tends to look best when it’s lined up with the center of this icon.
+
+**Minimize the height of your interface.** The system displays other elements above and below your custom interface, such as the text prompt, the spoken response, and the Siri waveform. Aim for a custom interface height that’s no taller than half the height of the screen, so people can see all your content without scrolling.
+
+**Refrain from displaying your app name or icon.** The system automatically shows this information, so it’s redundant to include it in your custom interface.
+
+For developer guidance, see [Creating an Intents UI Extension](https://developer.apple.com/documentation/SiriKit/creating-an-intents-ui-extension).
+
+## [Custom intents](https://developer.apple.com/design/human-interface-guidelines/siri#Custom-intents)
+
+If your app lets people perform an everyday task that doesn’t fit into any of the SiriKit domains, you can create a custom intent to represent it (see [System intents](https://developer.apple.com/design/human-interface-guidelines/siri#System-intents) for a list of domains). You can also use a custom or system intent to support a shortcut, which gives people a quick way to initiate frequently performed actions by speaking a simple phrase or accepting a suggestion from Siri. To learn how to integrate your intents with the system so that people can discover them and add them to Siri, see [Shortcuts and suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions).
+
+### [Custom intent categories and responses](https://developer.apple.com/design/human-interface-guidelines/siri#Custom-intent-categories-and-responses)
+
+Although your custom intent won’t belong to a SiriKit domain, you’ll need to model it on a system-defined _intent category_ that’s related to your action. SiriKit defines several categories that represent generic tasks, like create, order, share, and search. Because these definitions are in the system, Siri knows how to communicate with people about common actions that are associated with each category — like placing an order or sharing content — in ways that feel natural.
+
+It’s important to choose the category that best represents your action because the category influences the ways Siri speaks about it and the controls people might see in the interface. For example, a coffee app would likely choose the order category to represent its custom _order coffee_ intent, and as a result, Siri can speak default responses that make sense in the context of this action, like “Ready to order?” and “OK. Ordering.” Category choice can have other effects, too: Because the order category includes actions that have financial impact, using this category for the _order coffee_ intent means that people will be asked to authenticate before completing the action.
+
+For several categories, the system defines additional verbs that are related to the category’s default action. You can use these alternative verbs to help ensure that the Siri dialogue and the button titles displayed in the interface align with the way you present your app’s actions. For example, in addition to the default verb _order_ , the order category includes the verbs _buy_ and _book_.
+
+SiriKit defines the following custom intent categories and associated verbs.
+
+Category| Default verb| Additional verbs
+---|---|---
+Generic| Do| Run, go
+Information| View| Open
+Order| Order| Book, buy
+Start| Start| Navigate
+Share| Share| Post, send
+Create| Create| Add
+Search| Search| Find, filter
+Download| Download| Get
+Other| Set| Request, toggle, check in
+
+SiriKit also defines three response types:
+
+ * Confirmation. Confirms that people still want to perform the action.
+
+ * Success. Indicates that the action has been initiated.
+
+ * Error. Tells people that the action can’t be completed.
+
+
+
+
+In several custom intent categories, SiriKit defines default dialogue for each response type. For example, the default confirmation dialogue for the order category is, “Ready to order?” and the default success dialogue for the share category is, “OK. Shared.”
+
+To customize a response, you create a template that combines dialogue you write with placeholders for relevant information your app can supply while it’s working on the intent. For example, a coffee app might enhance the default order confirmation dialogue by providing custom content that includes a placeholder for the total cost of the order.
+
+Depending on the response type, your custom dialogue is presented before or after the default dialogue. For example, confirmation responses present the default dialogue after any custom dialogue. In the coffee app example, the customized confirmation dialogue would begin with something like, “Your large coffee with cream comes to $2.50” and end with the default dialogue, “Ready to order?”
+
+### [Design a custom intent](https://developer.apple.com/design/human-interface-guidelines/siri#Design-a-custom-intent)
+
+If a built-in SiriKit intent represents your action’s purpose, adopt that intent instead of defining a custom intent. For example, if you’d like to offer a shortcut for sending a message, adopt [`INSendMessageIntent`](https://developer.apple.com/documentation/Intents/INSendMessageIntent); if you’d like to offer a shortcut for playing media, adopt [`INPlayMediaIntent`](https://developer.apple.com/documentation/Intents/INPlayMediaIntent). For guidance, see [System intents](https://developer.apple.com/design/human-interface-guidelines/siri#System-intents).
+
+**If your app’s action requires a custom intent, pick the category that most closely matches the action.** A category informs the system about the general function of an intent or shortcut — like order, download, or search — and affects the text and spoken dialogue presented to people when a shortcut is offered by the system or used with Siri. You design the flow of conversation for the custom intents you offer, so it’s essential that you choose a category that corresponds to the meaning of each intent.
+
+Tip
+
+If your action’s primary purpose is to retrieve information or show something to people — like displaying a sports score or the weather — use the information category. Using a different category requires people to make additional taps to get the information.
+
+**Design custom intents that accelerate common, useful tasks.** Take advantage of the familiarity people have with your app, and make it easier for them to initiate the tasks they perform most often.
+
+**Ensure that your intent works well in every scenario.** Make it easy for people to run your intent as a shortcut, regardless of how they initiate it. For example, be prepared for people to run it using their voice on devices with and without a screen, from suggestions on the lock screen or the Siri face on Apple Watch, from search, and within a multistep shortcut.
+
+**In general, design custom intents for tasks that aren’t overly complex.** People benefit the most from intents that reduce the number of actions required to complete a task. Don’t counteract that simplicity by requiring people to engage in a lengthy conversation with your app. You can also reduce the likelihood of user errors by limiting custom intents to clearly defined tasks.
+
+**Design your intents to be long-lived.** Avoid offering intents that are date-specific or associated with temporary data. For example, it’s not a good idea for a travel app to offer a custom intent for each specific itinerary. A better intent might use follow-up questions to let people get the itinerary for one of their upcoming trips.
+
+**Don’t request permission to use Siri.** If your app supports only custom intents — and not system intents — you don’t need to get permission to use Siri before letting people create and use voice shortcuts for your intents. Asking for permission can slow people down and could discourage them from using your app’s custom intents.
+
+**Support background operation.** The best intents support shortcuts that run quickly and don’t pull people out of their current context. Strive to support custom intents that can run in the background without bringing your app to the front. Supporting background operation also ensures that people can complete the task in hands-free and voice-only scenarios.
+
+### [Help people customize their requests](https://developer.apple.com/design/human-interface-guidelines/siri#Help-people-customize-their-requests)
+
+Custom intents can offer follow-up questions that let people do more with a single intent by refining its results on the fly. For example, if you offer an _order coffee_ intent, you can help people get exactly what they want by asking them questions like, “What size?”, “What flavor?”, and “Which location?” Details like size, flavor, and location are _parameters_ your app can define to help people personalize their request.
+
+People supply parameter values to personalize an intent by responding to your follow-up questions or by editing existing values in the Shortcuts app. For example, if you offer an _order ground coffee_ intent that includes a parameter for the grind size, you might supply a follow-up question like, “Which grind?” For people who typically order the coarse grind, you could simplify the interaction by using the value _coarse_ as the default parameter value in a dialogue like, “Do you want coarse-ground coffee?” If people choose a different grind, you can follow up by presenting the full list of options. In voice-only scenarios, Siri speaks your follow-up questions and sends you the responses. When people use the Shortcuts app to edit a parameter value, you receive the new value when they use the associated shortcut. For developer guidance, see [Adding User Interactivity with Siri Shortcuts and the Shortcuts App](https://developer.apple.com/documentation/SiriKit/adding-user-interactivity-with-siri-shortcuts-and-the-shortcuts-app).
+
+**Design intents that require as few follow-up questions as possible.** Often, an intent can fulfill a request without asking any follow-up questions. Although follow-up questions make intents more flexible, you don’t want to force people into a long interaction. In most cases, it’s best to offer just one or two follow-up questions.
+
+**List the smallest number of options possible, and sort the items in a way that makes sense.** As with too many follow-up questions, giving people too many options can make completing the task feel onerous. As you determine whether to include an item, consider its complexity as well as its utility. In a food-ordering app, for example, it might be easier for people to parse a list of individual menu items than a list of orders, each of which contains multiple items. After you identify a small number of useful items, consider sorting them by recency, frequency, or popularity.
+
+**Make sure each follow-up question is meaningful.** Ideally, each follow-up question helps people make an important choice. If options or questions you present are too granular or too similar, the conversation can become repetitive, and people may feel like using your intent is too much work.
+
+**Design parameters that are easy for people to understand and use.** Aim for parameters that represent simple values or attributes and name them using simple, straightforward terms. For example, a soup-ordering app might define parameters for the type of soup, the serving size, and a delivery location, using names like _soup_ , _size_ , and _location_. For guidance, see [Shortcuts and suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions).
+
+**Ask for confirmation only when necessary.** An intent can ask people for confirmation before completing the task or when interpreting an answer to a follow-up question. Apps that support tasks that have financial impact, like an app that helps people place orders, must ask for confirmation before completing an order. For tasks that don’t have financial impact, asking for confirmation can feel like too much extra work and can sometimes discourage people from completing their request. In all cases, avoid asking for confirmation more than once.
+
+**Support follow-up questions when it makes sense.** For example, an app that helps people order food might offer options for pickup or delivery, but ask for a specific location only after people choose the delivery option.
+
+**Prioritize the options you offer based on the context in which people run your shortcut.** For example, if people use your shortcut to order an item for pickup, offer pickup locations that are currently close by. Offering options that adapt to the context in which your shortcut is run can help people avoid creating separate shortcuts for specific options.
+
+**Consider adjusting the parameter values you offer when people set up your shortcut.** When you indicate that a parameter has dynamic options, you can enhance the shortcut setup experience in two ways:
+
+ * You can find and present parameter values that are relevant to the context people are in while they’re setting up the shortcut. For example, if people use the Shortcuts app to choose a value for a store-location parameter, the parameter can dynamically generate a list of stores that are currently closest to the device.
+
+ * You can present a comprehensive list of parameter values. When people set up a shortcut, having an extensive list of parameter values can help them create the shortcut they want. In contrast, when people use a shortcut to accelerate an action, they generally prefer the convenience of having a shorter list of choices.
+
+
+
+
+For developer guidance, see the `storeLocation` parameter in the intent definition file of the [Soup Chef: Accelerating App Interactions with Shortcuts](https://developer.apple.com/documentation/SiriKit/soup-chef-accelerating-app-interactions-with-shortcuts) sample code project.
+
+### [Enhance the voice experience for custom intents](https://developer.apple.com/design/human-interface-guidelines/siri#Enhance-the-voice-experience-for-custom-intents)
+
+**Aim to create conversational interactions.** You can customize what Siri says throughout the voice experience, including the handling of follow-up questions. Try writing a script and acting it out with another person to see how well your dialogue works in a face-to-face exchange. Experiencing custom dialogue in this way can help you find places where the interaction doesn’t feel natural.
+
+**Help people understand errors and failures.** The system provides some default error descriptions, but it’s best to enhance error responses so that they’re specific to the current situation. For example, if chicken noodle soup is sold out, a soup app can respond with a custom error like, “Sorry, we’re out of chicken noodle soup” instead of “Sorry, we can’t complete your order.”
+
+**Strive for engaging voice responses.** Remember that people may perform your app’s tasks from their HomePod, using “Hey Siri” with their AirPods, or through CarPlay without looking at a screen. In these cases, the voice response needs to convey the same essential information that the visual elements display to ensure that people can get what they need no matter how they interact with Siri.
+
+**Create voice responses that are concise, descriptive, and effective in voice-driven scenarios.** As with a shortcut title, an effective custom spoken response clearly conveys what’s happening as the shortcut runs. If you ask follow-up questions, be sure to customize the default dialogue for clarity. For example, “Which soup?” is clearer than “Which one?”
+
+**Avoid unnecessary repetition.** People tend to run voice shortcuts frequently, so they may hear the same prompt multiple times when answering follow-up questions or dealing with errors. Use the context of the current conversation to remove as many details from the prompts as possible. Avoid including unnecessary words or attempts at humor, because both can become irritating over time.
+
+**Help conversations with Siri feel natural.** People interact with Siri in a variety of ways, like choosing a list item by saying “the second one,” or, in the case of a soup-ordering app, saying “large” or “small” instead of “bowl” or “cup.” You can make people’s Siri interactions feel more natural when you give the system alternative terms and phrases that work as app-specific synonyms (like using “bowl” as a synonym for “large”). Also consider enhancing clarity by providing alternative dialogue options for Siri to speak. For example, the soup app might present a list of onscreen menu options like “1 clam chowder,” or “1 clam chowder and 1 tomato,” but speak these options as “Which order? The one with clam chowder only or the one that includes tomato?”
+
+**Exclude your app name.** The system provides verbal and visual attribution for your app when responding to people. Including your appʼs name in a verbal response is redundant and may make the experience of interacting with Siri feel less natural. Siri speaks your app’s name less frequently when people have used a shortcut several times, because it isn’t necessary to keep reminding them which app is responding.
+
+**Don’t attempt to mimic or manipulate Siri.** Never impersonate Siri, attempt to reproduce the functionality that Siri provides, or provide a response that appears to come from Apple.
+
+**Be appropriate and respect parental controls.** Never present offensive or demeaning content. Keep in mind that many families use parental controls to restrict explicit content and content that’s based on specific rating levels.
+
+**Avoid using personal pronouns.** Create content that’s inclusive of all people.
+
+**Consider letting people view more options in your app.** If the list of options doesn’t include the items people need, you might want to include an item that lets people open your app to see more. In the list, you could use copy like, “See more in _App Name_ ,” and in spoken dialogue, you might encourage people to say, “More options.”
+
+**Keep responses device-independent.** People may use Siri to interact with your app via Apple Watch, HomePod, iPad, iPhone, or CarPlay. If you must provide device-specific wording, make sure it accurately reflects the person’s current device.
+
+**Don’t advertise.** Don’t include advertisements, marketing, or in-app purchase sales pitches in your intent content.
+
+## [Shortcuts and suggestions](https://developer.apple.com/design/human-interface-guidelines/siri#Shortcuts-and-suggestions)
+
+When you support shortcuts, people have a variety of ways to discover and interact with the custom and system intents your app provides. For example:
+
+ * Siri can suggest a shortcut for an action people have performed at least once by offering it in search results, on the lock screen, and in the Shortcuts app.
+
+ * Your app can supply a shortcut for an action that people haven’t done yet but might want to do in the future, so that the Shortcuts app can suggest it or it can appear on the [Siri watch face](https://support.apple.com/guide/watch/faces-and-features-apde9218b440/watchos#apdcc88df92c).
+
+ * People can use the Shortcuts app to view all their shortcuts and even combine actions from different apps into multistep shortcuts.
+
+ * People can also use the Shortcuts app to automate a shortcut by defining the conditions that can run it, like time of day or current location.
+
+
+
+
+The Shortcuts app is also available in macOS 12 and later and in watchOS 7 and later. For developer guidance, see [SiriKit](https://developer.apple.com/documentation/SiriKit).
+
+Developer note
+
+The Add to Siri method for adding shortcuts is no longer supported. See [App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts) for ways to integrate your app with Siri and the system.
+
+### [Make app actions widely available](https://developer.apple.com/design/human-interface-guidelines/siri#Make-app-actions-widely-available)
+
+ _Donating_ information about the actions your app supports helps the system offer them to people in various ways, such as:
+
+ * In search results
+
+ * Throughout the Shortcuts app
+
+ * On the lock screen as a Siri Suggestion
+
+ * Within the Now Playing view (for recently played media content)
+
+ * During Wind Down
+
+
+
+
+Donations also power Automation Suggestions in the Shortcut app’s Gallery, making it easy for people to set up automations for hands-free interactions with your app.
+
+You can also tell the system about shortcuts for actions people haven’t taken yet or make a shortcut available on the Siri watch face (for guidance, see [Suggest Shortcuts people might want to add to Siri](https://developer.apple.com/design/human-interface-guidelines/siri#Suggest-Shortcuts-people-might-want-to-add-to-Siri) and [Display shortcuts on the Siri watch face](https://developer.apple.com/design/human-interface-guidelines/siri#Display-shortcuts-on-the-Siri-watch-face)). For developer guidance, see [Donating Shortcuts](https://developer.apple.com/documentation/SiriKit/donating-shortcuts).
+
+**Make a donation every time people perform the action.** When you donate a shortcut each time people perform the associated action, you help the system more accurately predict the best time and place to offer the shortcut.
+
+**Only donate actions that people actually perform.** For example, a coffee-ordering app donates the _Order coffee_ shortcut every time people order coffee, but not when people do something else, like browse the menu. Similarly, a media app donates information about a song — like its title and album — only when people are actually listening to it. (For developer guidance, see [Improving Siri Media Interactions and App Selection](https://developer.apple.com/documentation/SiriKit/improving-siri-media-interactions-and-app-selection).)
+
+**Remove donations for actions that require corresponding data.** If information required by a donated action no longer exists, your app needs to delete the donation so the shortcut isn’t suggested anymore. For example, if people delete a contact in a messaging app, the app needs to delete donations for messaging that contact. When people create a shortcut themselves, only they can delete it. For developer guidance, see [Deleting Donated Shortcuts](https://developer.apple.com/documentation/SiriKit/deleting-donated-shortcuts).
+
+**If your app handles reservations, consider donating them to the system.** These items — like ticketed events, travel itineraries, or reservations for restaurants, flights, or movies — automatically appear as suggestions in Calendar or Maps. When you donate a reservation, it can appear on the lock screen with a suggestion to check in with your app or as a reminder that uses current traffic conditions to recommend when people should leave. For developer guidance, see [Donating Reservations](https://developer.apple.com/documentation/SiriKit/donating-reservations).
+
+#### [Suggest Shortcuts people might want to add to Siri](https://developer.apple.com/design/human-interface-guidelines/siri#Suggest-Shortcuts-people-might-want-to-add-to-Siri)
+
+If your app supports an action that people haven’t performed yet but might find useful, you can provide a _suggested_ shortcut to the system so that people can discover it. For example, if people use a coffee-ordering app to order their daily coffee but not to order a holiday special, the app might still want to give them a way to do this with an _Order holiday coffee_ shortcut.
+
+Suggested shortcuts appear in both the Gallery and the shortcut editor in the Shortcuts app. For developer guidance, see [Offering Actions in the Shortcuts App](https://developer.apple.com/documentation/SiriKit/offering-actions-in-the-shortcuts-app).
+
+#### [Display shortcuts on the Siri watch face](https://developer.apple.com/design/human-interface-guidelines/siri#Display-shortcuts-on-the-Siri-watch-face)
+
+On Apple Watch, people can run shortcuts in several ways. For example, people can ask Siri, tap a shortcut [complication](https://developer.apple.com/design/human-interface-guidelines/complications) on a watch face, or use the Shortcuts app available in watchOS 7 and later. You can also make shortcuts available on the Siri watch face.
+
+To have a shortcut appear on the Siri watch face, you define a _relevant_ shortcut by including information like the time of day at which your shortcut is relevant and how the shortcut can display on the Siri watch face. The information you supply lets the Siri watch face intelligently display your shortcut to people when they’re in the appropriate context.
+
+For developer guidance, see [Defining Relevant Shortcuts for the Siri Watch Face](https://developer.apple.com/documentation/SiriKit/defining-relevant-shortcuts-for-the-siri-watch-face).
+
+### [Create shortcut titles and subtitles](https://developer.apple.com/design/human-interface-guidelines/siri#Create-shortcut-titles-and-subtitles)
+
+Shortcut titles and subtitles appear when the system suggests them. In Siri Suggestions on iPhone and Apple Watch, a shortcut can also display an image.
+
+**Be concise but descriptive.** An effective title conveys what happens when the shortcut runs. A subtitle can provide additional detail that supplements — but doesn’t duplicate — the title.
+
+**Start titles with a verb and use sentence-style capitalization without punctuation.** Think of a shortcut title as a brief instruction.
+
+| Example title
+---|---
+| _Order my favorite coffee_
+| _Large latte_
+| _Show today’s forecast_
+| _Weather forecast_
+
+**Lead with important information.** Long titles and subtitles may be truncated in certain contexts, depending on the device’s screen size.
+
+**Exclude your app name.** The system already identifies the app associated with a shortcut.
+
+**Localize titles and subtitles.** Providing content in multiple languages ensures an equally great experience for people everywhere.
+
+**Consider providing a custom image for a more engaging suggestion.** For example, the shortcut for _Order my favorite coffee_ could show a cup of the customer’s favorite coffee. Create an image that measures:
+
+ * 60x60 pt (180x180 px @ 3x) to display in an iOS app
+
+ * 34x34 pt (68x68 px @2x) to display on the Siri watch face on the 44mm Apple Watch (watchOS scales down the image for smaller watches)
+
+
+
+
+### [Provide default phrases for shortcuts](https://developer.apple.com/design/human-interface-guidelines/siri#Provide-default-phrases-for-shortcuts)
+
+Your app provides default phrases for shortcuts during setup. People can personalize these phrases when adding your shortcuts to Siri.
+
+**Keep phrases short and memorable.** Bear in mind that people must speak your phrase verbatim, so long or confusing phrases may result in mistakes and frustration. Two- and three-word phrases tend to work best. More words can be harder for people to remember, and phrases that are too long will get truncated.
+
+**Make sure the phrases you suggest are accurate and specific.** Phrases like _Reorder coffee_ or _Order my usual coffee_ clearly describe what the shortcut does, which makes it easier for people to remember the phrase later. Also make sure that your suggested phrases are specific to each shortcut’s scope. For example, _Watch baseball_ is clearer and more memorable than _Watch sports_. It’s also important to avoid implying that people can vary a shortcut’s invocation phrase to get a different result. For example, people might interpret a phrase like _Order a large clam chowder_ to mean that your shortcut will give them what they want if they substitute “small” for “large” and “lobster bisque” for “clam chowder.”
+
+**Don’t commandeer core Siri commands.** For example, never suggest a phrase like _Call 911_ or include the text _Hey Siri_.
+
+### [Make shortcuts customizable](https://developer.apple.com/design/human-interface-guidelines/siri#Make-shortcuts-customizable)
+
+When you define a parameter for each detail your app needs to perform an intent, people can customize the shortcut by editing these details in the Shortcuts app.
+
+To show people which details they can edit and how their edits affect the action, you provide a _parameter summary_. A parameter summary succinctly describes the action by using the parameters in a sentence that begins with a verb. For example, a customizable _Order coffee_ shortcut could display a parameter summary like “Order _quantity_ _coffee_ ” where _quantity_ and _coffee_ are the parameters that people can edit. Here’s an example of how the _Order coffee_ shortcut might look after people supply values for the _quantity_ and _coffee_ parameters.
+
+**Provide a parameter summary for each custom intent you support.** At minimum, include in your parameter summary all parameters your intent requires and any parameters that receive values from other apps or actions. The summary doesn’t have to include optional parameters or parameters that people aren’t likely to edit; if you omit parameters like these from the summary, people can still access them in the Show More section.
+
+**Craft a short parameter summary that’s clearly related to your intent’s title.** When the intent title and the parameter summary are similar, it’s easy for people to recognize the action regardless of where they view it. Aim to use the same words in the summary and the title — in particular, it’s helpful to begin both phrases with the same verb. For example, if your intent title is “Search encyclopedia,” a good parameter summary could be “Search encyclopedia for _search term_.”
+
+**Aim for a parameter summary that reads like a sentence.** Use sentence-style capitalization, but don’t include ending punctuation. When possible, avoid punctuation entirely. Punctuation within a summary — especially colons, semicolons, and parentheses — can make the summary hard to read and understand.
+
+**Provide multiple parameter summaries when necessary.** If your action includes a parameter that has a parent-child relationship with other parameters, you can provide multiple variants of the summary based on the current value of the parent parameter. For example, if your _order coffee_ shortcut lets people specify whether they want to pick up their order or have it delivered, your parameter summary can reflect the current choice. In this scenario, create one parameter summary that helps people pick a store location and another summary that helps them pick a delivery address. Be sure to use a consistent grammatical structure and parameter order in all variants of the summary that you create.
+
+**Provide output parameters for information that people can use in a multistep shortcut.** For example, an _order coffee_ action might provide output that includes the estimated delivery time and the cost of the order. With this information, people could create a multistep shortcut that messages a friend about the delivery time and logs the transaction in their favorite budgeting app.
+
+**Consider defining an input parameter.** When you define an input parameter for an action, the action can automatically receive output from a preceding action in a multistep shortcut. For example, if your action applies a filter to the image it receives in an _image_ parameter, you might designate _image_ as the input parameter so that it automatically accepts images from other actions. You configure an input parameter in your intent definition file (shown in [Adding User Interactivity with Siri Shortcuts and the Shortcuts App](https://developer.apple.com/documentation/SiriKit/adding-user-interactivity-with-siri-shortcuts-and-the-shortcuts-app#3239040)).
+
+**Help people distinguish among different variations of the same action.** For example, an app that offers a _send message_ action might use a contact photo to help people visually distinguish the various messages they send. To do this, choose the parameter that’s most identifiable to people and designate it as the key parameter (shown in [Adding User Interactivity with Siri Shortcuts and the Shortcuts App](https://developer.apple.com/documentation/SiriKit/adding-user-interactivity-with-siri-shortcuts-and-the-shortcuts-app#3239040)). Be sure to provide an image for the key parameter every time you donate the action (for developer guidance, see [`INImage`](https://developer.apple.com/documentation/Intents/INImage)).
+
+**Avoid providing multiple actions that perform the same basic task.** For example, instead of providing an action that adds text to a note and a different action that adds an image, consider providing a single action that lets people add both types of content. Providing a few high-level actions can make it easier for people to understand what the actions do when they’re combined in a multistep shortcut.
+
+For developer guidance, see [Shortcut-Related UI](https://developer.apple.com/documentation/SiriKit/shortcut-related-ui).
+
+## [Editorial guidelines](https://developer.apple.com/design/human-interface-guidelines/siri#Editorial-guidelines)
+
+**Don’t refer to Siri using pronouns like “she,” “him,” or “her.”** Ideally, just use the word _Siri_. For example, _After you add a shortcut to Siri, you can run the shortcut anytime by asking Siri_.
+
+**Use correct capitalization and punctuation when using the term _Hey Siri_.** _Hey Siri_ is two words, italicized or in quotes, with an uppercase _H_ and uppercase _S_. Do not follow the term with an ellipsis.
+
+| Example text
+---|---
+| _Say Hey Siri to activate Siri._
+| _Say “Hey Siri” to activate Siri._
+| _Say Hey Siri… to activate Siri._
+| _Say “hey Siri” to activate Siri._
+
+**In a localized context, translate only the word _Hey_ in the phrase _Hey Siri_.** As an Apple trademark, _Siri_ is never translated. Here is a list of acceptable translations for the phrase _Hey Siri_ :
+
+Locale code| _Hey Siri_ translation| Locale code| _Hey Siri_ translation
+---|---|---|---
+ar_AE| يا Siri| fr_CA| Dis Siri
+ar_SA| يا Siri| fr_CH| Dis Siri
+da_DK| Hej Siri| fr_FR| Dis Siri
+de_AT| Hey Siri| it_CH| Ehi Siri
+de_CH| Hey Siri| it_IT| Ehi Siri
+de_DE| Hey Siri| ja_JP| Hey Siri
+en_AU| Hey Siri| ko_KR| Siri야
+en_CA| Hey Siri| ms_MY| Hai Siri
+en_GB| Hey Siri| nb_NO| Hei Siri
+en_IE| Hey Siri| nl_BE| Hé, Siri
+en_IN| Hey Siri| nl_NL| Hé Siri
+en_NZ| Hey Siri| no_NO| Hei Siri
+en_SG| Hey Siri| pt_BR| E aí Siri
+en_US| Hey Siri| ru_RU| привет Siri
+en_ZA| Hey Siri| sv_SE| Hej Siri
+es_CL| Oye Siri| th_TH| หวัดดี Siri
+es_ES| Oye Siri| tr_TR| Hey Siri
+es_MX| Oye Siri| zh_CN| 嘿Siri
+es_US| Oye Siri| zh_HK| 喂 Siri
+fi_FI| Hei Siri| zh_TW| 嘿 Siri
+fr_BE| Dis Siri| |
+
+### [Referring to Shortcuts](https://developer.apple.com/design/human-interface-guidelines/siri#Referring-to-Shortcuts)
+
+**When referring to the Shortcuts feature or app, always typeset with a capital S and make sure that _Shortcuts_ is plural.** For example, _MyApp integrates with Shortcuts to provide a quick way to get things with just a tap or by asking Siri._
+
+**When referring to individual shortcuts (that is, not the feature or the Shortcuts app), use lowercase.** For example, _Run a shortcut by asking Siri or tapping a suggestion on the Lock Screen_.
+
+**Use the right terminology when describing how people can use Shortcuts in your app.** People run shortcuts by asking Siri, so your wording needs to be very similar to phrases like _Run a shortcut by asking Siri_ or _Run the shortcut by asking Siri with your personalized phrase_ (localized as appropriate). Avoid using phrases like _add voice shortcuts_ , _make a voice command_ , _create a voice prompt_ , or any other variation. Instead, consider a phrase like _Add a shortcut to Siri to run with your voice_ (localized as appropriate).
+
+To encourage people to create or use shortcuts in ways other than voice — like automations, Home Screen shortcuts, and other methods — use a phrase that doesn’t specify a particular method, like _For quick access, add to Shortcuts_.
+
+Note
+
+Use translations of your app name and the word _Shortcuts_ — but not _Siri_ — when referring to them in a localized context.
+
+### [Referring to Apple products](https://developer.apple.com/design/human-interface-guidelines/siri#Referring-to-Apple-products)
+
+**Adhere to Apple’s trademark guidelines.** Apple trademarks can’t appear in your app name or images. In text, use Apple product names exactly as shown on the [Apple Trademark List](https://www.apple.com/legal/intellectual-property/trademark/appletmlist.html).
+
+ * Use Apple product names in singular form only; don’t make Apple product names possessive.
+
+ * Don’t translate Apple, Siri, or any other Apple trademark.
+
+ * Don’t use category descriptors. For example, say iPad, not tablet.
+
+ * Don’t indicate any kind of sponsorship, partnership, or endorsement from Apple.
+
+ * Attribute Apple, Siri, and all other Apple trademarks with the correct credit lines wherever legal information appears within your app.
+
+ * Refer to Apple devices and operating systems only in technical specifications or compatibility descriptions.
+
+
+
+
+See [Guidelines for Using Apple Trademarks](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/siri#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/siri#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/siri#Related)
+
+[App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts)
+
+[Design for intelligence](https://developer.apple.com/news/?id=mb3c4r4r)
+
+[Guidelines for using Apple trademarks and copyrights](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/siri#Developer-documentation)
+
+[SiriKit](https://developer.apple.com/documentation/SiriKit)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/siri#Videos)
+
+[ Design interactive snippets ](https://developer.apple.com/videos/play/wwdc2025/281)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/siri#Change-log)
+
+Date| Changes
+---|---
+June 5, 2023| Removed Add to Siri guidance. Added references to the new [App Shortcuts](https://developer.apple.com/design/human-interface-guidelines/app-shortcuts) page.
+May 2, 2023| Consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hig-technologies/references/tap-to-pay-on-iphone.md b/web-app/public/skills/hig-technologies/references/tap-to-pay-on-iphone.md
new file mode 100644
index 00000000..e8fd1c15
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/tap-to-pay-on-iphone.md
@@ -0,0 +1,208 @@
+---
+title: "Tap to Pay on iPhone | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone
+
+# Tap to Pay on iPhone
+
+Tap to Pay on iPhone lets merchants accept contactless payments using an app on their iPhone, without having to connect external hardware.
+
+
+
+When you support Tap to Pay on iPhone in your iOS payment app, you help merchants present a consistent and trusted payment experience to their customers.
+
+Note
+
+Tap to Pay on iPhone works alongside your existing payment-acceptance hardware and accessories.
+
+Before you can integrate Tap to Pay on iPhone into your iOS app, you need to work with a supported payment service provider (PSP), request the Tap to Pay on iPhone entitlement, and use [ProximityReader](https://developer.apple.com/documentation/ProximityReader) APIs, either through the PSP’s SDK or by adopting the framework. For high-level guidance — including marketing recommendations for letting people know about your app’s new capabilities — see [Tap to Pay on iPhone](https://developer.apple.com/tap-to-pay/); for developer guidance, see [Setting up Tap to Pay on iPhone](https://developer.apple.com/documentation/ProximityReader/setting-up-the-entitlement-for-tap-to-pay-on-iPhone).
+
+Note
+
+If your PSP offers an SDK that supplies user interfaces for experiences like showing a tap result, see the documentation the PSP provides.
+
+## [Enabling Tap to Pay on iPhone](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Enabling-Tap-to-Pay-on-iPhone)
+
+Before your app can enable Tap to Pay on iPhone and configure a merchant’s device, the merchant must accept the relevant terms and conditions. Use the ProximityReader API to help you get the current status and present an acceptance flow only when necessary. For developer guidance, see [Adding support for Tap to Pay on iPhone to your app](https://developer.apple.com/documentation/ProximityReader/adding-support-for-tap-to-pay-on-iphone-to-your-app#Display-the-Terms-and-Conditions-interface-to-the-merchant).
+
+**Help merchants accept Tap to Pay on iPhone terms and conditions before they begin interacting with their customers.** Merchants must accept the terms and conditions before you perform the initial device configuration, so it works well when they can do so before they begin a checkout or other customer-facing flow. For example, you can provide buttons that let people accept Tap to Pay on iPhone terms and conditions from within your [in-app messaging](https://developer.apple.com/tap-to-pay/marketing-guidelines/#in-your-app) or onboarding flows.
+
+An app screen that offers a way to accept Tap to Pay on iPhone terms and conditions
+
+An app screen that shows Tap to Pay on iPhone is enabled and offers a way to try it
+
+**Present Tap to Pay on iPhone terms and conditions only to an administrative user.** If a nonadministrator tries to activate the feature, present a message explaining that administrator access is required. If your app’s primary users are enterprise or nonadministrative users, you can let an administrator accept Tap to Pay on iPhone terms and conditions through a web interface or a different app, including one that can run on devices other than iPhone. Contact your PSP for implementation details.
+
+**If necessary, help merchants make sure their device is up to date.** If your PSP requires specific versions of iOS, be sure to present the terms and conditions only after the merchant updates their device.
+
+## [Educating merchants](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Educating-merchants)
+
+Some merchants may be unfamiliar with Tap to Pay on iPhone, so it’s important to give them a quick and easy way to get started.
+
+**Provide a tutorial that describes the supported payment types and shows how to use Tap to Pay on iPhone to accept each type.** You can offer this tutorial by:
+
+ * Including it in a Learn More option in your in-app messaging
+
+ * Automatically presenting it after merchants accept the Tap to Pay on iPhone terms and conditions
+
+ * Automatically presenting it to new users of your app
+
+ * Making it easy to find in a consistent place like your app’s help content or settings area
+
+
+
+
+You can build your app’s tutorial using Apple-approved assets from the [Tap to Pay on iPhone marketing guidelines](https://developer.apple.com/tap-to-pay/marketing-guidelines/), or you can use the [`ProximityReaderDiscovery`](https://developer.apple.com/documentation/ProximityReader/ProximityReaderDiscovery) API to provide a pre-built merchant education experience. Apple ensures that the API is up to date and is localized for the merchant’s region.
+
+
+
+Your app’s settings area is a good place to make sure the tutorial is always available.
+
+
+
+The merchant education tutorial provided by the `ProximityReaderDiscovery` API.
+
+If you design your own tutorial, make sure it shows how to:
+
+ * Launch a checkout flow for each type of payment
+
+ * Help a customer position their contactless card or digital wallet on the merchant’s device for payment
+
+ * Handle PIN entry for a card, including accessibility mode
+
+
+
+
+Finally, provide an opportunity at the end of the tutorial for merchants who haven’t accepted the Tap to Pay on iPhone terms and conditions yet to do so.
+
+## [Checking out](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Checking-out)
+
+Checking out is a time-sensitive action, and merchants need the process to work smoothly. As you design your checkout flow, be prepared to:
+
+ * Offer payment options in addition to Tap to Pay on iPhone, as necessary
+
+ * Respond quickly if a merchant initiates checkout before enabling Tap to Pay on iPhone
+
+ * Help merchants perform checkout even if device configuration is still in progress
+
+ * Present pre-payment actions that affect the final total before checkout completes
+
+
+
+
+**Provide Tap to Pay on iPhone as a checkout option whether the feature is enabled or not.** Including a Tap to Pay on iPhone button gives merchants the flexibility to use the feature without exiting the checkout flow. When merchants tap the button, present the terms and conditions if necessary and automatically display the Tap to Pay on iPhone screen when configuration completes.
+
+**Avoid making merchants wait to use Tap to Pay on iPhone.** In addition to performing the initial configuration for each device, you need to perform a subsequent configuration each time your app becomes frontmost. To minimize potential wait times, prepare the feature as soon as your app starts and immediately after each transition to the foreground. For developer guidance, see [`prepare(using:)`](https://developer.apple.com/documentation/ProximityReader/PaymentCardReader/prepare\(using:\)).
+
+**Make sure the Tap to Pay on iPhone checkout option is available even if configuration is continuing in the background.** Merchants must always be able to select the Tap to Pay on iPhone checkout option in a checkout flow. During configuration, let merchants select the checkout option and then display a progress indicator — avoid waiting for configuration to complete before making the option available. In most scenarios, you can display an indeterminate progress indicator, but if ProximityReader API shows that configuration is ongoing, display a determinate progress indicator. For guidance, see [Progress indicators](https://developer.apple.com/design/human-interface-guidelines/progress-indicators); for developer guidance see [`PaymentCardReader.Event.updateProgress(_:)`](https://developer.apple.com/documentation/ProximityReader/PaymentCardReader/Event/updateProgress\(_:\)).
+
+An app screen that displays a determinate progress indicator during configuration
+
+An app screen that displays an indeterminate progress indicator during configuration
+
+**If your app supports multiple payment-acceptance methods, make the Tap to Pay on iPhone button easy to find.** Avoid making merchants scroll to access the feature. If your app doesn’t support other payment acceptance options, open Tap to Pay on iPhone automatically when checkout begins.
+
+**Make it easy for merchants to switch between Tap to Pay on iPhone and the hardware accessories you support.** Even though your support for Tap to Pay on iPhone is separate from your support for a hardware accessory, such as a Bluetooth chip and PIN card reader, you can streamline the user experience by helping merchants set up both methods at the same time. After setup, make sure merchants can choose the appropriate payment-acceptance method during the checkout flow without having to visit your app settings.
+
+**For the label of the button that activates the feature, use “Tap to Pay on iPhone” or, if space is constrained, “Tap to Pay.”** The exception is if Tap to Pay on iPhone is the only payment-acceptance method you support. In this case, you can reuse your existing Charge or Checkout buttons to activate Tap to Pay on iPhone. If you support multiple payment-acceptance methods and you use icons in the buttons that activate them, use the `wave.3.right.circle` or `wave.3.right.circle.fill` [SF Symbols](https://developer.apple.com/design/human-interface-guidelines/sf-symbols) in your Tap to Pay on iPhone button. Always avoid including the Apple logo in Tap to Pay on iPhone buttons.
+
+
+
+
+
+
+
+
+
+Important
+
+Use the “Tap to Pay on iPhone” label only for payment actions. For language you can use for nonpayment actions, see [Additional interactions](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Additional-interactions).
+
+**Design your Tap to Pay on iPhone button to match the other buttons in your app.** Although you must use the labels “Tap to Pay on iPhone” or “Tap to Pay” as described above, you can use the button color and shape that coordinate best with your interface.
+
+**Determine the final amount that customers need to pay before merchants initiate the Tap to Pay on iPhone experience.** For example, if your app supports tipping or other customer interactions that can affect the total, make sure merchants offer these interactions before displaying the Tap to Pay on iPhone screen. Aim to display the final amount customers need to pay in the Tap to Pay on iPhone screen.
+
+**If you support pre-payment options in your checkout flow, display them before the Tap to Pay on iPhone screen.** For example, if you support the selection of different payment types, you can display these options in your checkout screen after a merchant taps the Tap to Pay on iPhone button and before you open the Tap to Pay on iPhone screen.
+
+## [Displaying results](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Displaying-results)
+
+Customers pay by _tapping_ — that is, bringing a contactless card or digital wallet near the Tap to Pay on iPhone screen in your app. After a successful tap (and after a successful PIN entry, if required), Tap to Pay on iPhone displays a checkmark and gives your app an object that contains the encrypted payment information you send to your PSP for processing. When a tap fails, Tap to Pay on iPhone displays an error screen. Your app is responsible for displaying transaction results after a successful tap or offering alternative payment options after an unsuccessful tap.
+
+**Start processing a transaction as soon as possible.** The system provides API you can use to request the result of a successful tap before the Tap to Pay on iPhone screen finishes displaying the checkmark animation that indicates tap completion. For developer guidance, see [`returnReadResultImmediately`](https://developer.apple.com/documentation/ProximityReader/PaymentCardReader/Options-swift.struct/returnReadResultImmediately).
+
+**Display a progress indicator while payment is authorizing before you show your transaction result screen.** Transaction authorization can take several seconds to complete, depending on factors like connectivity for both the PSP and the merchant’s device. To ensure a smooth visual transition, display your authorization [progress indicator](https://developer.apple.com/design/human-interface-guidelines/progress-indicators) after the Tap to Pay on iPhone screen animation finishes (for developer guidance, see [`PaymentCardReader.Event.readyForTap`](https://developer.apple.com/documentation/ProximityReader/PaymentCardReader/Event/readyForTap)).
+
+
+
+**Clearly display the result of a transaction, whether it’s declined or successful.** A transaction can be declined for reasons like insufficient funds, suspicion of fraud, or when the customer enters an incorrect PIN. As much as possible, also give the merchant ways to offer customers a digital receipt, such as through a QR code or text message.
+
+
+
+
+
+**Help merchants complete the checkout flow when a payment can’t complete with Tap to Pay on iPhone.** For example, a tap can fail when a card isn’t readable, isn’t from a supported payment network, doesn’t allow transactions at the stated amount, or doesn’t allow online PIN entry. In cases like these, you can:
+
+ * Present a new screen or reuse your checkout screen, letting merchants accept an alternate form of payment, like cash
+
+ * Support checkout with a different method, like external hardware or a payment link
+
+ * Relaunch Tap to Pay on iPhone, if a customer has another card they want to try
+
+
+
+
+
+
+After you receive payment card data, you might also encounter scenarios like the ones listed below. If such scenarios occur, contact your PSP for guidance on addressing them.
+
+ * Some regions require Strong Customer Authentication (SCA) support, which means that although the payment card might not require a card PIN during a tap, the bank that issues the card can request a PIN after receiving the transaction processing request. In this scenario, your app may need to display the PIN entry screen instead of the transaction result.
+
+ * In some regions your app may need to meet additional requirements to address the limitations of some cards, such as those in Offline PIN markets. Some PSPs support additional PIN fallback functionality to collect partial data from a tap, letting merchants continue the payment with another method such as a payment link.
+
+
+
+
+**If the system returns an error that the merchant must address, display a clear description of the problem and recommend an appropriate resolution.** For example, if the device’s version of iOS doesn’t support Tap to Pay on iPhone, present an [alert](https://developer.apple.com/design/human-interface-guidelines/alerts) that recommends updating to the latest version. For developer guidance, see [`PaymentCardReaderSession.ReadError`](https://developer.apple.com/documentation/ProximityReader/PaymentCardReaderSession/ReadError).
+
+**Make it easy for merchants to get help with issues they can’t resolve.** For example, direct merchants to the help content in your app or on your website, and provide an action that contacts your support team.
+
+## [Additional interactions](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Additional-interactions)
+
+Tap to Pay on iPhone lets merchants read a payment card when there’s no transaction amount to support use cases like looking up a past transaction, or retaining card information to ensure future payment, issue refunds, or verify customer information.
+
+**Use a generic label in a button that opens the Tap to Pay on iPhone screen to read a payment card when there’s no transaction amount.** Don’t include “Tap to Pay on iPhone” or “Tap to Pay” in such a label; instead, use a generic label like “Look Up,” “Store Card,” “Verify,” or “Refund.”
+
+When customers have other types of NFC-compatible cards or passes in Apple Wallet — such as loyalty, discount, and points cards — Tap to Pay on iPhone lets merchants read these items at the same time that they read a payment card or independently.
+
+**If your app supports an independent loyalty card transaction, distinguish this flow from a payment-acceptance flow that uses Tap to Pay on iPhone.** It works well to give merchants a separate, clearly labeled button to initiate a loyalty card transaction. To help merchants avoid choosing the wrong button by mistake, avoid including “Tap to Pay on iPhone,” “Tap to Pay,” or other payment-related terms in the label for a loyalty-transaction button.
+
+
+
+
+
+
+
+
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Platform-considerations)
+
+ _No additional considerations for iOS. Not supported in iPadOS, macOS, tvOS, visionOS, or watchOS._
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Related)
+
+[Tap to Pay on iPhone Marketing guidelines](https://developer.apple.com/tap-to-pay/marketing-guidelines/)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Developer-documentation)
+
+[Adding support for Tap to Pay on iPhone to your app](https://developer.apple.com/documentation/ProximityReader/adding-support-for-tap-to-pay-on-iphone-to-your-app) — ProximityReader
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone#Change-log)
+
+Date| Changes
+---|---
+January 17, 2024| Updated merchant education guidance.
+May 7, 2024| Updated to include guidance on enabling the feature and educating merchants.
+March 3, 2023| Enhanced guidance for educating merchants and improving their experience.
+September 14, 2022| Refined guidance on preparing Tap to Pay on iPhone and helping merchants learn how to use the feature.
+
diff --git a/web-app/public/skills/hig-technologies/references/voiceover.md b/web-app/public/skills/hig-technologies/references/voiceover.md
new file mode 100644
index 00000000..155c5665
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/voiceover.md
@@ -0,0 +1,90 @@
+---
+title: "VoiceOver | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/voiceover
+
+# VoiceOver
+
+VoiceOver is a screen reader that lets people experience your app’s interface without needing to see the screen.
+
+
+
+By supporting VoiceOver, you help people who are blind or have low vision access information in your app and navigate its interface and content when they can’t see the display.
+
+VoiceOver is supported in apps and games built for Apple platforms. It’s also supported in apps and games developed in Unity using [Apple’s Unity plug-ins](https://github.com/apple/unityplugins). For related guidance, see [Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility).
+
+## [Descriptions](https://developer.apple.com/design/human-interface-guidelines/voiceover#Descriptions)
+
+You inform VoiceOver about your app’s content by providing alternative text that explains your app’s interface and the content it displays.
+
+**Provide alternative labels for all key interface elements.** VoiceOver uses alternative labels (which aren’t visible onscreen) to audibly describe your app’s interface. System-provided controls have generic labels by default, but you should provide more descriptive labels that convey your app’s functionality. Add labels to any custom elements your app defines. Be sure to keep your descriptions up-to-date as your app’s interface and content change. For developer guidance, see [Accessibility modifiers](https://developer.apple.com/documentation/SwiftUI/View-Accessibility).
+
+**Describe meaningful images.** If you don’t describe key images in your app’s content, people can’t use VoiceOver to fully experience them within your app. Because VoiceOver helps people understand the interface surrounding images too, such as nearby captions, describe only the information the image itself conveys.
+
+**Make charts and other infographics fully accessible.** Provide a concise description of each infographic that explains what it conveys. If people can interact with the infographic to get more or different information, make these interactions available to people using VoiceOver, too. The accessibility APIs offer ways to represent custom interactive elements so that assistive technologies can help people use them. For guidance, see [Charts](https://developer.apple.com/design/Human-Interface-Guidelines/charts#Enhancing-the-accessibility-of-a-chart).
+
+**Exclude purely decorative images from VoiceOver.** It’s unnecessary to describe images that are decorative and don’t convey useful or actionable information. Excluding these images shows respect for people’s time and reduces cognitive load when they use VoiceOver. For developer guidance, see [`accessibilityHidden(_:)`](https://developer.apple.com/documentation/SwiftUI/View/accessibilityHidden\(_:\)), [`accessibilityElement`](https://developer.apple.com/documentation/AppKit/NSAccessibility-c.protocol/accessibilityElement), and [`isAccessibilityElement`](https://developer.apple.com/documentation/UIKit/UIAccessibilityElement/isAccessibilityElement).
+
+## [Navigation](https://developer.apple.com/design/human-interface-guidelines/voiceover#Navigation)
+
+**Use titles and headings to help people navigate your information hierarchy.** The title is the first information someone receives from an assistive technology when arriving on a page or screen in your app. Offer unique titles that succinctly describe each page’s content and purpose. Likewise, use accurate section headings that help people build a mental model of each page’s information hierarchy.
+
+**Specify how elements are grouped, ordered, or linked.** Proximity, alignment, and other visible contextual cues help sighted people perceive the relationships between elements. Examine your app for places where relationships among elements are visual only. Then, describe these relationships to VoiceOver.
+
+VoiceOver reads elements in the same order people read content in the their active language and locale. For example, in US English, this is top-to-bottom, left-to-right. In the ungrouped example below, VoiceOver describes each image before moving on to the captions. In the grouped example, VoiceOver describes each image with its respective caption.
+
+
+
+Ungrouped related elements make it hard for VoiceOver to accurately describe the UI.
+
+
+
+
+
+Grouped related elements help VoiceOver accurately describe the UI.
+
+
+
+For developer guidance, see [`shouldGroupAccessibilityChildren`](https://developer.apple.com/documentation/ObjectiveC/NSObject-swift.class/shouldGroupAccessibilityChildren).
+
+**Inform VoiceOver when visible content or layout changes occur.** People may find an unexpected content or layout change confusing because it means their mental map of the content is no longer accurate. It’s crucial to report visible changes so VoiceOver and other assistive technologies can help people update their understanding of the content. For developer guidance, see [`AccessibilityNotification`](https://developer.apple.com/documentation/Accessibility/AccessibilityNotification).
+
+**Support the VoiceOver rotor when possible.** People can use an interface element called the VoiceOver rotor to navigate a document or webpage by headings, links, and other content types. You can help people navigate content in your app by identifying these elements to the rotor. The rotor can also bring up the braille keyboard. For developer guidance, see [`AccessibilityRotorEntry`](https://developer.apple.com/documentation/SwiftUI/AccessibilityRotorEntry) (SwiftUI), [`UIAccessibilityCustomRotor`](https://developer.apple.com/documentation/UIKit/UIAccessibilityCustomRotor) (UIKit), and [`NSAccessibilityCustomRotor`](https://developer.apple.com/documentation/AppKit/NSAccessibilityCustomRotor) (AppKit).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/voiceover#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, tvOS, or watchOS._
+
+### [visionOS](https://developer.apple.com/design/human-interface-guidelines/voiceover#visionOS)
+
+**Be mindful that custom gestures aren’t always accessible.** When VoiceOver is turned on in visionOS, apps and games that define custom gestures don’t receive hand input by default. This ensures people can explore the interface using their voice, without an app responding to hand input at the same time. A person can opt out of this behavior by enabling Direct Gesture mode, which disables standard VoiceOver gestures and lets apps process hand input directly. For developer guidance, see [Improving accessibility support in your visionOS app](https://developer.apple.com/documentation/visionOS/improving-accessibility-support-in-your-app).
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/voiceover#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/voiceover#Related)
+
+[Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
+
+[Inclusion](https://developer.apple.com/design/human-interface-guidelines/inclusion)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/voiceover#Developer-documentation)
+
+[Accessibility](https://developer.apple.com/documentation/Accessibility)
+
+[VoiceOver](https://developer.apple.com/documentation/Accessibility/voiceover)
+
+[Supporting VoiceOver in your app](https://developer.apple.com/documentation/UIKit/supporting-voiceover-in-your-app)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/voiceover#Videos)
+
+[ Writing Great Accessibility Labels ](https://developer.apple.com/videos/play/wwdc2019/254)
+
+[ Tailor the VoiceOver experience in your data-rich apps ](https://developer.apple.com/videos/play/wwdc2021/10121)
+
+[ VoiceOver efficiency with custom rotors ](https://developer.apple.com/videos/play/wwdc2020/10116)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/voiceover#Change-log)
+
+Date| Changes
+---|---
+March 7, 2025| New page.
+
diff --git a/web-app/public/skills/hig-technologies/references/wallet.md b/web-app/public/skills/hig-technologies/references/wallet.md
new file mode 100644
index 00000000..44faf56f
--- /dev/null
+++ b/web-app/public/skills/hig-technologies/references/wallet.md
@@ -0,0 +1,420 @@
+---
+title: "Wallet | Apple Developer Documentation"
+source: https://developer.apple.com/design/human-interface-guidelines/wallet
+
+# Wallet
+
+Wallet helps people securely store their credit and debit cards, driver’s license or state ID, transit cards, event tickets, keys, and more on iPhone and Apple Watch.
+
+
+
+People use their cards and passes in Wallet to make Apple Pay purchases, track their orders, confirm their identity, and streamline activities like boarding a plane, attending a concert, or receiving a discount.
+
+When you integrate Apple Wallet into your app, you can create custom passes and present them the moment people need them, securely verify an individual’s identity so they can access personal content, and offer detailed receipts and tracking information where it’s most convenient. For developer guidance, see [Wallet](https://developer.apple.com/documentation/PassKit/wallet).
+
+## [Passes](https://developer.apple.com/design/human-interface-guidelines/wallet#Passes)
+
+**Offer to add new passes to Wallet.** When people do something that results in a new pass — like checking into a flight, purchasing an event ticket, or registering for a store reward program — you can present system-provided UI that helps them add the pass to Wallet with one tap (for developer guidance, see [`addPasses(_:withCompletionHandler:)`](https://developer.apple.com/documentation/PassKit/PKPassLibrary/addPasses\(_:withCompletionHandler:\))). If people want to review a pass before adding it, you can display a custom view that displays the pass and provides an Add to Apple Wallet button; for developer guidance, see [`PKAddPassesViewController`](https://developer.apple.com/documentation/PassKit/PKAddPassesViewController).
+
+**Help people add a pass that they created outside of your app.** If people create a pass using your website or another device, suggest adding it to Wallet the next time they open your app. If people decline your suggestion, don’t ask them again.
+
+**Add related passes as a group.** If your app generates multiple passes, like boarding passes for a multi-connection flight, add all passes at the same time so people don’t have to add each one individually. If people can receive a group of passes from your website — such as a set of tickets for an event — bundle them together so that people can download all of them at one time. For developer guidance, see [Distributing and updating a pass](https://developer.apple.com/documentation/WalletPasses/distributing-and-updating-a-pass).
+
+**Display an Add to Apple Wallet button to let people add an existing pass that isn’t already in Wallet.** If people previously declined your suggestion to add a pass to Wallet — or if they removed the pass — a button makes it easy to add it if they change their minds. You can display an Add to Apple Wallet button wherever the corresponding pass information appears in your app. For developer guidance, see [`PKAddPassButton`](https://developer.apple.com/documentation/PassKit/PKAddPassButton). You can also display an Add to Apple Wallet badge in an email or on a webpage; for guidance, see [Add to Apple Wallet guidelines](https://developer.apple.com/wallet/add-to-apple-wallet-guidelines/).
+
+**Let people jump from your app to their pass in Wallet.** Wherever your app displays information about a pass that exists in Wallet, you can offer a link that opens it directly. Label the link something like “View in Wallet.”
+
+**Tell the system when your pass expires.** Wallet automatically hides expired passes to reduce crowding, while also providing a button that lets people revisit them. To help ensure the system hides passes appropriately, set the expiration date, relevant date, and voided properties of each pass correctly; for developer guidance, see [`Pass`](https://developer.apple.com/documentation/WalletPasses/Pass).
+
+**Always get people’s permission before deleting a pass from Wallet.** For example, you could include an in-app setting that lets people specify whether they want to delete passes manually or have them removed automatically. If necessary, you can display an alert before deleting a pass.
+
+**Help the system suggest a pass when it’s contextually relevant.** Ideally, passes automatically appear when they’re needed so people don’t have to manually locate them. When you supply information about when and where your pass is relevant, the system can display a link to it on the Lock Screen when people are most likely to want it. For example, a gym membership card could appear on the Lock Screen as people enter the gym. For developer guidance, see [Showing a Pass on the Lock Screen](https://developer.apple.com/documentation/WalletPasses/showing-a-pass-on-the-lock-screen). Starting in iOS 18 and watchOS 11, the system starts a Live Activity for poster event ticket style passes when they’re relevant.
+
+
+
+Lock screen notification
+
+
+
+Live Activity
+
+**Update passes as needed.** Physical passes don’t typically change, but a digital pass can reflect updates to events. An airline boarding pass, for example, can automatically update to display flight delays and gate changes.
+
+**Use change messages only for updates to time-critical information.** A change message interrupts people’s current workflow, so it’s essential to send one only when you make an update they need to know about. For example, people need to know when there’s a gate change in a boarding pass, but they don’t need to know when a customer service phone number changes. Never use a change message for marketing or other noncritical communication. Change messages are available on a per-field basis; for developer guidance, see [Adding a Web Service to Update Passes](https://developer.apple.com/documentation/WalletPasses/adding-a-web-service-to-update-passes).
+
+## [Designing passes](https://developer.apple.com/design/human-interface-guidelines/wallet#Designing-passes)
+
+Wallet uses a consistent design aesthetic to strengthen familiarity and build trust. Instead of merely replicating the appearance of a physical item, design a clean, simple pass that looks at home in Wallet.
+
+
+
+**Design a pass that looks great and works well on all devices.** Passes can look different on different devices. For example, when a pass appears on Apple Watch, it doesn’t display all the images it displays when it appears on iPhone (for guidance, see [Passes for Apple Watch](https://developer.apple.com/design/human-interface-guidelines/wallet#Passes-for-Apple-Watch)). Don’t put essential information in elements that might be unavailable on certain devices. Also, don’t add padding to images; for example, watchOS crops white space from some images.
+
+**Avoid using device-specific language.** You can’t predict the device people will use to view your pass, so don’t write text that might not make sense on a particular device. For example, text that tells people to “slide to view” content doesn’t make sense when it appears on Apple Watch.
+
+**Make your pass instantly identifiable.** Using color — especially a color that’s linked to your brand — can help people recognize your pass as soon as they see it. Make sure that pass content remains comfortably readable against the background you choose.
+
+**Keep the front of a pass uncluttered so people can get important information at a glance.** Show essential information — like an event date or account balance — in the top-right area of the pass so people can still see it when the pass is collapsed in Wallet. Use the rest of the pass front to provide important information; consider putting extra information on the back of a pass (iOS) or in a details screen (watchOS).
+
+**Prefer an NFC-compatible pass.** People appreciate having a contactless pass, because it means that they can just hold their device near a reader. If you support both NFC and a barcode or QR code, the code appears on the back of the pass (in iOS) or in the details screen (in watchOS). In iOS, you can display a QR code or barcode on the front of your pass if necessary for your design.
+
+**Reduce image sizes for optimal performance.** People can receive passes via email or a webpage. To make downloads as fast as possible, use the smallest image files that still look great.
+
+**Provide an icon that represents your company or brand.** The system includes your icon when displaying information about a relevant pass on the Lock Screen. Mail also uses the icon to represent your pass in an email message. You can use your app icon or design an icon for this purpose.
+
+### [Pass styles](https://developer.apple.com/design/human-interface-guidelines/wallet#Pass-styles)
+
+The system defines several pass _styles_ for categories like boarding pass, coupon, store card, and event ticket. Pass styles specify the appearance and layout of content in your pass, and the information that the system needs to suggest your pass when it’s relevant (for guidance, see [Passes](https://developer.apple.com/design/human-interface-guidelines/wallet#Passes)).
+
+Although each pass style is different, all styles display information using the basic layout areas shown below:
+
+
+
+All passes display a logo image, and some can display additional images in other areas depending on the pass style. To display information in the layout areas, use the following [`PassFields`](https://developer.apple.com/documentation/WalletPasses/PassFields).
+
+Field| Layout area| Use to provide…
+---|---|---
+Header| Essential| Critical information that needs to remain visible when the pass is collapsed in Wallet.
+Primary| Primary| Important information that helps people use the pass.
+Secondary and auxiliary| Secondary and auxiliary| Useful information that people might not need every time they use the pass.
+Back| Not shown in diagram| Supplemental details that don’t need to be on the pass front.
+
+In general, a pass can have up to three header fields, one primary field, up to four secondary fields, and up to four auxiliary fields. Depending on the amount of content you display in each field, some fields may not be visible.
+
+**Display text only in pass fields.** Don’t embed text in images — it’s not accessible and not all images are displayed on all devices — and avoid using custom fonts that might make text hard to read.
+
+#### [Boarding passes](https://developer.apple.com/design/human-interface-guidelines/wallet#Boarding-passes)
+
+Use the boarding pass style for train tickets, airline boarding passes, and other types of transit passes. Typically, each pass corresponds to a single trip with a specific starting and ending point.
+
+A boarding pass can display logo and footer images, and it can have up to two primary fields and up to five auxiliary fields.
+
+ * Example
+ * Layout
+
+
+
+
+
+
+
+#### [Coupons](https://developer.apple.com/design/human-interface-guidelines/wallet#Coupons)
+
+Use the coupon style for coupons, special offers, and other discounts. A coupon can display logo and strip images, and it can have up to four secondary and auxiliary fields, all displayed on one row.
+
+ * Example
+ * Layout
+
+
+
+
+
+
+
+#### [Store cards](https://developer.apple.com/design/human-interface-guidelines/wallet#Store-cards)
+
+Use the store card style for store loyalty cards, discount cards, points cards, and gift cards. If an account related to a store card carries a balance, the pass usually shows the current balance.
+
+A store card can display logo and strip images, and it can have up to four secondary and auxiliary fields, all displayed on one row.
+
+ * Example
+ * Layout
+
+
+
+
+
+
+
+#### [Event tickets](https://developer.apple.com/design/human-interface-guidelines/wallet#Event-tickets)
+
+Use the event ticket pass style to give people entry into events like concerts, movies, plays, and sporting events. Typically, each pass corresponds to a specific event, but you can also use a single pass for several events, as with a season ticket.
+
+An event ticket can display logo, strip, background, or thumbnail images. However, if you supply a strip image, don’t include a background or thumbnail image. You can also include an extra row of up to four auxiliary fields. For developer guidance, see the `row` property of [`PassFields.AuxiliaryFields`](https://developer.apple.com/documentation/WalletPasses/PassFields/AuxiliaryFields-data.dictionary).
+
+ * Example
+ * Layout 1
+ * Layout 2
+
+
+
+
+
+
+
+
+
+In iOS 18 and later, the system defines an additional style for contactless event tickets called _poster event ticket_. Poster event tickets offer a rich visual experience that prominently features the event artwork, provides easy access to additional event information, and integrates with system apps like Weather and Maps.
+
+Important
+
+Poster event tickets aren’t compatible with tickets that require a QR code or barcode for entry.
+
+A poster event ticket displays an event logo and background image, and can optionally display a separate ticket issuer or event company logo. The system uses metadata about your event to structure ticket information and suggest relevant actions. You must provide a required set of metadata in [`SemanticTags`](https://developer.apple.com/documentation/WalletPasses/SemanticTags) for all poster event tickets, and an additional set of required metadata depending on the event type — general, sports, or live performance. You can also add optional metadata to further enhance your ticket. For example, you can specify an admission level for a live performance, like General Admission, which the system displays with the seating information. For developer guidance, see [Supporting semantic tags in Wallet passes](https://developer.apple.com/documentation/WalletPasses/supporting-semantic-tags-in-wallet-passes).
+
+ * Example
+ * Layout
+
+
+
+
+
+
+
+The system uses the metadata that you provide to generate a Maps shortcut to the venue directions and an event guide below the ticket when in the Wallet app. The event guide provides convenient access to information like the weather forecast and venue map, and to quick actions like checking the baggage policy and ordering food. You can display a minimum of one and up to four quick action buttons in the event guide; if you include more than four, the system collapses them into a menu. You can optionally include additional ticket information, such as pre-paid parking details, which the system also displays below the ticket.
+
+
+
+Additional ticket information, Maps shortcut, and event guide tiles below the ticket in the Wallet app
+
+
+
+Event guide
+
+**Create a vibrant and engaging background.** As the centerpiece of a poster event ticket, your background image serves as a visual representation of the event. Limit text in your artwork, and create an image that’s easily identifiable to help people quickly find their ticket among other passes in their Wallet app. If your background image is a solid color or includes a solid color in the footer, consider setting a footer background color to better blend the background image with the footer.
+
+**Position your background image in the safe area.** The system displays ticket information in the header and footer, which overlap the background image. To ensure that the content in your artwork isn’t covered, position it in the safe area. For developer guidance, see `footerBackgroundColor` in [`Pass`](https://developer.apple.com/documentation/WalletPasses/Pass).
+
+**Ensure sufficient contrast so that ticket information is easy to read.** By default, the system applies a gradient in the header and a blur effect in the footer of your poster event ticket to provide sufficient contrast between the background image and ticket information. Consider adjusting the gradient and blur effect if you need more contrast. The system can also automatically determine the best text color for ticket information and labels based on your background image. If you choose to customize text colors, make sure to select a color that provides sufficient contrast, especially if you set a footer background color or a seat section color to support wayfinding. For developer guidance, see `useAutomaticColors` in [`Pass`](https://developer.apple.com/documentation/WalletPasses/Pass) and `seatSectionColor` in [`SemanticTagType.Seat`](https://developer.apple.com/documentation/WalletPasses/SemanticTagType/Seat-data.dictionary).
+
+
+
+
+
+
+
+
+
+**Consider using the additional information tile for extra event details.** When you have more information about the event that people may find helpful, the additional information tile below the ticket is a great place to put it. If you have additional information that’s essential to display on the front of the ticket, keep the text short to avoid cluttering the footer. For developer guidance, see `additionalTicketAttributes` in [`SemanticTags`](https://developer.apple.com/documentation/WalletPasses/SemanticTags) and [`PassFields.AdditionalInfoFields`](https://developer.apple.com/documentation/WalletPasses/PassFields/AdditionalInfoFields-data.dictionary).
+
+**Continue to support event tickets for earlier versions of iOS.** People expect contactless event tickets to work, regardless of their device’s software version. Continue to provide primary, secondary, and auxiliary information in [`PassFields`](https://developer.apple.com/documentation/WalletPasses/PassFields) and image assets for your event ticket. This enables the system to automatically generate the appropriate ticket style for a person’s device; otherwise, your ticket appears empty on devices running earlier versions of iOS.
+
+#### [Generic passes](https://developer.apple.com/design/human-interface-guidelines/wallet#Generic-passes)
+
+Use the generic style for a type of pass that doesn’t fit into the other categories, such as a gym membership card or coat-check claim ticket. A generic pass can display logo and thumbnail images, and it can have up to four secondary and auxiliary fields, all displayed on one row.
+
+ * Example
+ * Layout 1
+ * Layout 2
+
+
+
+
+
+
+
+
+
+### [Passes for Apple Watch](https://developer.apple.com/design/human-interface-guidelines/wallet#Passes-for-Apple-Watch)
+
+On Apple Watch, Wallet displays passes in a scrolling carousel of cards. People can add your pass to their Apple Watch even if you don’t create a watch-specific app, so it’s important to understand how your pass can look on the device.
+
+
+
+People can tap a pass on their Apple Watch to reveal a details screen that displays additional information in a scroll view. In some cases, people can also tap a specific transaction to get more information.
+
+
+
+Each pass style specifies the fields and images that can appear in the basic layout areas shown below:
+
+
+
+If some information doesn’t fit within the layout areas, the system displays it in the scrolling details screen.
+
+Important
+
+In every style, watchOS crops the strip image to fit the aspect ratio of the card interface and may crop white space from other images.
+
+ * Boarding
+ * Coupon
+ * Store
+ * Event
+ * Generic
+
+
+
+
+
+
+
+
+
+
+
+
+
+## [Order tracking](https://developer.apple.com/design/human-interface-guidelines/wallet#Order-tracking)
+
+When you support order tracking, Wallet can display information about an order a customer placed through your app or website, updating the information whenever the status of the order changes. In iOS 17 and later, you can help people start tracking their order right from your app or website and offer additional ways to add their order to Wallet.
+
+
+
+
+
+Wallet presents a dashboard that displays a customer’s active and completed orders. People can choose an order to view details about it, like the items they ordered and fulfillment information for shipping and pickup.
+
+
+
+Dashboard
+
+The [Wallet Orders](https://developer.apple.com/documentation/WalletOrders) schema defines the properties you use to provide order data like product descriptions, order status, contact information, and shipping and pickup details, including estimated arrival dates, addresses, tracking numbers, and pickup instructions. Wallet displays the information you supply within consistent, system-defined interfaces. To help people get the information they need quickly and conveniently, supply as much information as you can, using the properties that match your order processes.
+
+
+
+**Make it easy for people to add an order to Wallet.** For example, when a customer completes an Apple Pay transaction in your app or website, use [`PKPaymentOrderDetails`](https://developer.apple.com/documentation/PassKit/PKPaymentOrderDetails) (app) or [`ApplePayPaymentOrderDetails`](https://developer.apple.com/documentation/ApplePayontheWeb/ApplePayPaymentOrderDetails) (web) to automatically add the order to Wallet. In iOS 17 and later, you can use [`AddOrderToWalletButton`](https://developer.apple.com/documentation/FinanceKitUI/AddOrderToWalletButton) to display the system-provided Track with Apple Wallet button in relevant areas of your app or website — such as in pages for order confirmation, status, or tracking — or in emails to customers. If a person already added an order to Wallet, trying to add it again opens Wallet and displays the order.
+
+**Make information about an order available immediately after people place it.** People need to confirm that their order was received, even when payment, processing, and fulfillment are still pending. If you won’t have details until a later time, provide the data you have at the time of the order and supply a status [description](https://developer.apple.com/documentation/walletorders/order) like “Check back later for full order details.”
+
+**Provide fulfillment information as soon as it’s available, and keep the status up to date.** When you supply fulfillment data or you change the status of an order, the system updates the order information and can automatically send a notification to customers. The system uses the fulfillment status you report to update the order’s current status to a value like Order Placed, Processing, Ready for Pickup, Picked Up, Out for Delivery, Delivered, or — if something goes wrong — Issue or Canceled. For guidance on describing a status, see [Displaying order and fulfillment details](https://developer.apple.com/design/human-interface-guidelines/wallet#Displaying-order-and-fulfillment-details).
+
+**Supply a high-resolution logo image that uses a nontransparent background.** The system displays your logo image in the dashboard and detail view, so you want to make sure that people can instantly recognize it at various sizes. Use the PNG or JPEG format to create a logo image that measures 300x300 pixels. To help ensure that your logo image renders correctly, be sure to use a nontransparent background. For developer guidance, see [logo](https://developer.apple.com/documentation/walletorders/merchant).
+
+**Supply distinct, high-resolution product images that use nontransparent backgrounds.** The system displays a product’s image — along with descriptive information you supply — in the detail views, order dashboard, and notifications for an order or a fulfillment. When creating a product image, use a straightforward depiction and a solid, nontransparent background. Showing a product in a “lifestyle” context or against a busy background can make the item hard to distinguish at small sizes. For each product, use the PNG or JPEG format to create an image that measures 300x300 pixels.
+
+
+
+**In general, keep text brief.** People appreciate being able to read text at a glance, and the system can truncate text that’s too long.
+
+**Use clear, approachable language, and localize the text you provide.** You want to make sure that all your customers can read the information in an order. Also, make sure the price you show matches the final price the customer confirmed.
+
+### [Displaying order and fulfillment details](https://developer.apple.com/design/human-interface-guidelines/wallet#Displaying-order-and-fulfillment-details)
+
+An order gives people ways to contact the merchant and displays details about their Apple Pay purchase, including fulfillment status and per-item information.
+
+**Provide a link to an area where people manage their order.** When you provide a universal link, people can open your order management area even if they don’t have your app installed. To learn more about universal links, see [Allowing apps and websites to link to your content](https://developer.apple.com/documentation/Xcode/allowing-apps-and-websites-to-link-to-your-content); for developer guidance, see [`Order`](https://developer.apple.com/documentation/WalletOrders/Order).
+
+**Clearly describe each item so people can verify that their order contains everything they expect.** You can use the [`LineItem`](https://developer.apple.com/documentation/WalletOrders/LineItem) property to provide information like a product’s price, name, and image. An order lists the line items for every item the customer ordered; a fulfillment lists only the line items that fulfillment includes. When appropriate, you can also attach a PDF receipt to an individual transaction related to an order.
+
+**Supply a prioritized list of your apps that might be installed on the device.** The system uses this list when it needs to display a link to your app within the order details view. For example, if you provide multiple apps and more than one of them is installed on the device, the system displays a link to the installed app that’s highest on your list. If none of your apps are installed on the device, the system displays a link to the first app on your list. For developer guidance, see [`Order`](https://developer.apple.com/documentation/WalletOrders/Order).
+
+**Avoid sending duplicate notifications.** For example, you can tell the system to avoid sending order-related notifications through Wallet when the customer has one of your associated apps installed.
+
+**Make it easy for customers to contact the merchant.** Provide multiple contact methods, so people can choose the one that works best for them. At minimum, you need to provide a link to the merchant’s website or landing page, but you can also provide a Messages for Business link, a phone number, an email address, and a link to a support page. When people choose the Contact button in an order, the system displays a menu of the contact methods you supply. For developer guidance, see [`Merchant`](https://developer.apple.com/documentation/WalletOrders/Merchant).
+
+
+
+**Help people track their order.** A multi-item order can have multiple fulfillments, where each fulfillment is either shipping or pickup. For example, if a customer orders a pair of shoes and a T-shirt, the customer might want to have one item shipped, while picking up the other. Regardless of fulfillment type, you need to supply enough information for people to know where their items are and when to expect them at the destination they specified. In addition to an estimated time of arrival, here’s some information that people particularly appreciate:
+
+ * A link that opens the carrier’s website to a page with information about a shipping fulfillment. When possible, provide a direct link — in addition to a tracking number — so people can easily view the most up-to-date shipping information. If necessary, display this link on any intermediate order-tracking page you open.
+
+ * A scannable barcode when one is required to pick up the order in a pickup fulfillment. It’s convenient when people can offer the barcode from within Wallet instead of finding it in an email or webpage.
+
+ * Clear, detailed instructions that can help people receive or pick up their order.
+
+
+
+
+
+
+**Keep the fulfillment screen centered on order tracking.** For example, if you recommend your app or other services to customers, be sure to prioritize order-tracking information over other content in the screen.
+
+**Choose shipping-fulfillment values that match the details you have about the shipping process.** If you know the carrier, enter its name in the `carrier` property; otherwise, leave the default “Track Shipment” value. If you can access details about a carrier’s interim shipping steps — such as when a fulfillment is on the way or out for delivery — indicate each step by using specific status values like `onTheWay`, `outForDelivery`, or `delivered`. In contrast, if you don’t have access to a carrier’s shipping details, use the `shipped` status. In both cases, provide a tracking link (when one is available) so people can track their order on their own. For developer guidance, see [`ShippingFulfillment`](https://developer.apple.com/documentation/WalletOrders/ShippingFulfillment).
+
+**Keep customers informed through relevant fulfillment status descriptions.** A great status message is approachable, accurate, and clearly related to the status it describes. In addition to supplying information that helps people understand the status of their order, a status message also gives you an opportunity to use your brand’s communication style.
+
+**Be direct and thorough when describing an Issue or Canceled status.** People generally need to know why there’s a problem and what they can do about it.
+
+## [Identity verification](https://developer.apple.com/design/human-interface-guidelines/wallet#Identity-verification)
+
+On iPhone running iOS 16 and later, people can store an ID card in Wallet, and later allow an app or App Clip to access information on the card to verify their identity without leaving their current context. For example, a person might need to confirm their identity when they apply for a credit card within their banking app. To learn how to support in-person mobile ID verification, see [ID Verifier](https://developer.apple.com/design/human-interface-guidelines/id-verifier).
+
+Developer note
+
+Apple doesn’t create or see the ID documents that people add to Wallet, and when people agree to share identifying information with your app, you receive only encrypted data that isn’t readable on the device. For developer guidance, see [Requesting identity data from a Wallet pass](https://developer.apple.com/documentation/PassKit/requesting-identity-data-from-a-wallet-pass).
+
+To help you offer a consistent experience that people can trust, Apple provides a Verify with Wallet button you can use in your app when you need to ask for identify verification. The button reveals a sheet that describes your request and lets people agree to share their information or cancel.
+
+**Present a Wallet verification option only when the device supports it.** If the current device can’t return the identify information you request, don’t display a Verify with Apple Wallet button. Be prepared to present a fallback view that offers a different verification method if Verify with Apple Wallet isn’t available; for developer guidance, see [`VerifyIdentityWithWalletButton`](https://developer.apple.com/documentation/PassKit/VerifyIdentityWithWalletButton).
+
+**Ask for identity information only at the precise moment you need it.** People can be suspicious of a request for personal information if it doesn’t seem to be related to their current action. If your app needs identity verification, for example, wait to ask for this information until people are completing the process or transaction that requires it; don’t request verification before people are ready to start the process or when they’re simply creating an account.
+
+**Clearly and succinctly describe the reason you need the information you’re requesting.** You must write text that explains why people need to share identity information with your app (this text is called a _purpose string_ or _usage description string_). The system displays your purpose string in the verification sheet so people can make an informed decision. Here are a couple of examples:
+
+To verify…| To support…| Example purpose string
+---|---|---
+Identity| Opening an account for which proof of identity is legally required to prevent fraud| Federal law requires this information to verify your identity and also to help [App Name] prevent fraud.
+Driving privilege| Renting a vehicle that requires legal driving privileges| Applicable state law requires [App Name] to verify your driving privileges.
+
+For each purpose string, aim for a brief, complete sentence that’s direct, specific, and easy for everyone to understand. Use sentence case, avoid passive voice, and include a period at the end.
+
+**Ask only for the data you actually need.** People may lose trust in your app if you ask for more data than you need to complete the current task or action. For example, if you need to ensure that a customer is at least a certain age, use a request that specifies an age threshold; avoid requesting the customer’s current age or birth date. For developer guidance, see [`age(atLeast:)`](https://developer.apple.com/documentation/PassKit/PKIdentityElement/age\(atLeast:\)).
+
+**Clearly indicate whether you will keep the data and — if you need to keep it — specify how long you’ll do so.** To help people trust your app, it’s essential to explain how long you might need to keep the personal information they agree to share with you. When you use PassKit APIs to specify a duration — such as a particular period, indefinitely, or only as long as it takes to complete the current verification — the system automatically displays explanatory content in the verification sheet. For developer guidance, see [`PKIdentityIntentToStore`](https://developer.apple.com/documentation/PassKit/PKIdentityIntentToStore).
+
+**Choose the system-provided verification button that matches your use case and the visual design of your app.** The system provides the following button labels to support various use cases:
+
+Button type| Consider using when…
+---|---
+| Your app can complete the current transaction after you verify a person’s age. An example transaction is making a car available to lease.
+| Your app can complete the current transaction after you verify a person’s identity. An example transaction is a car rental.
+| Verify with Wallet forms one part of a verification process that also requires people to supply additional information not provided by Verify with Wallet, such as a Social Security number or phone number. Examples include opening a financial account or performing a background check.
+| Your app can complete the current verification flow without additional steps, but the “Verify Age,” “Verify Identity,” and “Continue” button labels aren’t appropriate for your use case. An example is an app that helps people sign up for a government service.
+
+All button labels are also available in a multiline variant that the system automatically uses when horizontal space is constrained. For developer guidance, see [`PKIdentityButton.Label`](https://developer.apple.com/documentation/PassKit/PKIdentityButton/Label).
+
+The verification button always uses white letters on a black background. You can choose the style that includes a light outline if you need to ensure that the button contrasts well with a dark background in your app. In addition, you can use the [`cornerRadius`](https://developer.apple.com/documentation/PassKit/PKIdentityButton/cornerRadius) property to adjust the verification button’s corners to match other related buttons in your interface. For developer guidance, see [`PKIdentityButton.Style.blackOutline`](https://developer.apple.com/documentation/PassKit/PKIdentityButton/Style/blackOutline).
+
+## [Platform considerations](https://developer.apple.com/design/human-interface-guidelines/wallet#Platform-considerations)
+
+ _No additional considerations for iOS, iPadOS, macOS, visionOS, or watchOS. Not supported in tvOS._
+
+## [Specifications](https://developer.apple.com/design/human-interface-guidelines/wallet#Specifications)
+
+### [Pass image dimensions](https://developer.apple.com/design/human-interface-guidelines/wallet#Pass-image-dimensions)
+
+As you design images for your wallet passes, create PNG files and use the following values for guidance.
+
+Image| Supported pass styles| Filename| Dimensions (pt)
+---|---|---|---
+Logo| Boarding pass, coupon, store card, event ticket, generic pass| `logo.png`| Any, up to 160x50
+Primary logo| Poster event ticket| `primaryLogo.png`| Any, up to 126x30
+Secondary logo| Poster event ticket| `secondaryLogo.png`| Any, up to 135x12
+Icon| All| `icon.png`| 38x38
+Background| Event ticket, poster event ticket| `background.png` (event ticket), `artwork.png` (poster event ticket)| 180x220 (event ticket), 358x448 (poster event ticket)
+Strip| Coupon, store card, event ticket| `strip.png`| 375x144 (coupon, store card), 375x98 (event ticket)
+Footer| Boarding pass| `footer.png`| Any, up to 286x15
+Thumbnail| Event ticket, generic pass| `thumbnail.png`| 90x90
+
+Note
+
+Dimensions for the logo, primary logo, and secondary logo images are the maximum — not the required — values. For example, if you create a primary logo image that measures 30x30 points, you don’t need to add unnecessary padding so that it measures the maximum 126x30 points.
+
+## [Resources](https://developer.apple.com/design/human-interface-guidelines/wallet#Resources)
+
+#### [Related](https://developer.apple.com/design/human-interface-guidelines/wallet#Related)
+
+[Apple Pay](https://developer.apple.com/design/human-interface-guidelines/apple-pay)
+
+[ID Verifier](https://developer.apple.com/design/human-interface-guidelines/id-verifier)
+
+#### [Developer documentation](https://developer.apple.com/design/human-interface-guidelines/wallet#Developer-documentation)
+
+[FinanceKitUI](https://developer.apple.com/documentation/FinanceKitUI)
+
+[FinanceKit](https://developer.apple.com/documentation/FinanceKit)
+
+[PassKit (Apple Pay and Wallet)](https://developer.apple.com/documentation/PassKit)
+
+[Wallet Passes](https://developer.apple.com/documentation/WalletPasses)
+
+[Wallet Orders](https://developer.apple.com/documentation/WalletOrders)
+
+#### [Videos](https://developer.apple.com/design/human-interface-guidelines/wallet#Videos)
+
+[ What’s new in Wallet and Apple Pay ](https://developer.apple.com/videos/play/wwdc2024/10108)
+
+[ What’s new in Wallet and Apple Pay ](https://developer.apple.com/videos/play/wwdc2023/10114)
+
+[ What’s new in Wallet and Apple Pay ](https://developer.apple.com/videos/play/wwdc2022/10041)
+
+## [Change log](https://developer.apple.com/design/human-interface-guidelines/wallet#Change-log)
+
+Date| Changes
+---|---
+January 17, 2025| Added specifications for pass image dimensions.
+December 18, 2024| Added guidance for the poster event ticket style.
+September 12, 2023| Added guidance for helping people add orders to Wallet.
+February 20, 2023| Enhanced guidance for presenting order-tracking information and added artwork.
+November 30, 2022| Added guidance to include a carrier name in status information for a shipping fulfillment.
+September 14, 2022| Added guidelines for using Verify with Wallet, updated guidance on providing shipping status values and descriptions, and consolidated guidance into one page.
+
diff --git a/web-app/public/skills/hosted-agents-v2-py/SKILL.md b/web-app/public/skills/hosted-agents-v2-py/SKILL.md
index ee9739b3..5b9c2855 100644
--- a/web-app/public/skills/hosted-agents-v2-py/SKILL.md
+++ b/web-app/public/skills/hosted-agents-v2-py/SKILL.md
@@ -1,11 +1,9 @@
---
name: hosted-agents-v2-py
-description: |
- Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition.
- Use when creating container-based agents that run custom code in Azure AI Foundry.
- Triggers: "ImageBasedHostedAgentDefinition", "hosted agent", "container agent",
- "create_version", "ProtocolVersionRecord", "AgentProtocol.RESPONSES".
+description: "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry."
package: azure-ai-projects
+risk: unknown
+source: community
---
# Azure AI Hosted Agents (Python)
@@ -323,3 +321,6 @@ async def create_hosted_agent_async():
- [Azure AI Projects SDK](https://pypi.org/project/azure-ai-projects/)
- [Hosted Agents Documentation](https://learn.microsoft.com/azure/ai-services/agents/how-to/hosted-agents)
- [Azure Container Registry](https://learn.microsoft.com/azure/container-registry/)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hr-pro/SKILL.md b/web-app/public/skills/hr-pro/SKILL.md
index d3843fb2..b9607f97 100644
--- a/web-app/public/skills/hr-pro/SKILL.md
+++ b/web-app/public/skills/hr-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: hr-pro
-description: Professional, ethical HR partner for hiring,
+description: "Professional, ethical HR partner for hiring,"
onboarding/offboarding, PTO and leave, performance, compliant policies, and
employee relations. Ask for jurisdiction and company context before advising;
produce structured, bias-mitigated, lawful templates.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/html-injection-testing/SKILL.md b/web-app/public/skills/html-injection-testing/SKILL.md
index afc3b660..9e78a4e5 100644
--- a/web-app/public/skills/html-injection-testing/SKILL.md
+++ b/web-app/public/skills/html-injection-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: HTML Injection Testing
-description: This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test content injection vulnerabilities". It provides comprehensive HTML injection attack techniques and testing methodologies.
+name: html-injection-testing
+description: "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# HTML Injection Testing
@@ -496,3 +498,6 @@ Server-side protections:
| HTML not rendering | Check if output HTML-encoded; try encoding variations; verify HTML context |
| Payload stripped | Use encoding variations; try tag splitting; test null bytes; nested tags |
| XSS not working (HTML only) | JS filtered but HTML allowed; leverage phishing forms, meta refresh redirects |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hubspot-automation/SKILL.md b/web-app/public/skills/hubspot-automation/SKILL.md
index e1544063..3886ea53 100644
--- a/web-app/public/skills/hubspot-automation/SKILL.md
+++ b/web-app/public/skills/hubspot-automation/SKILL.md
@@ -3,6 +3,8 @@ name: hubspot-automation
description: "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# HubSpot CRM Automation via Rube MCP
@@ -175,4 +177,7 @@ Automate HubSpot CRM workflows including contact/company management, deal pipeli
| List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` |
| Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` |
| Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None |
-| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |
\ No newline at end of file
+| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hubspot-integration/SKILL.md b/web-app/public/skills/hubspot-integration/SKILL.md
index ca429d1f..00a6ceec 100644
--- a/web-app/public/skills/hubspot-integration/SKILL.md
+++ b/web-app/public/skills/hubspot-integration/SKILL.md
@@ -1,7 +1,8 @@
---
name: hubspot-integration
-description: "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubspot, hubspot api, hubspot crm, hubspot integration, contacts api."
+description: "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# HubSpot Integration
@@ -40,3 +41,6 @@ Create, read, update, delete CRM records
| Issue | medium | See docs |
| Issue | high | See docs |
| Issue | medium | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/hugging-face-cli/SKILL.md b/web-app/public/skills/hugging-face-cli/SKILL.md
index e5ac6cae..a14e8a85 100644
--- a/web-app/public/skills/hugging-face-cli/SKILL.md
+++ b/web-app/public/skills/hugging-face-cli/SKILL.md
@@ -1,6 +1,6 @@
---
name: hugging-face-cli
-description: "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run compute jobs on HF infrastructure. Covers authentication, file transfers, repository creation, cache operations, and cloud compute."
+description: "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput..."
source: "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli"
risk: safe
---
@@ -194,5 +194,5 @@ hf cache rm model/gpt2 # Remove a repo from cache
## References
-- **Complete command reference**: See [references/commands.md](references/commands.md)
-- **Workflow examples**: See [references/examples.md](references/examples.md)
+- **Complete command reference**: See references/commands.md
+- **Workflow examples**: See references/examples.md
diff --git a/web-app/public/skills/hugging-face-jobs/SKILL.md b/web-app/public/skills/hugging-face-jobs/SKILL.md
index 70c43c8d..6efabe58 100644
--- a/web-app/public/skills/hugging-face-jobs/SKILL.md
+++ b/web-app/public/skills/hugging-face-jobs/SKILL.md
@@ -1,6 +1,6 @@
---
name: hugging-face-jobs
-description: "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tokens, secrets management, timeout configuration, and result persistence. Designed for general-purpose compute workloads including data processing, inference, experiments, batch jobs, and any Python-based tasks. Should be invoked for tasks involving cloud compute, GPU workloads, or when users mention running jobs on Hugging Face infrastructure without local setup."
+description: "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok..."
license: "Complete terms in LICENSE.txt"
source: "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs"
risk: safe
diff --git a/web-app/public/skills/hybrid-cloud-architect/SKILL.md b/web-app/public/skills/hybrid-cloud-architect/SKILL.md
index 39acc52a..cb7eaf2d 100644
--- a/web-app/public/skills/hybrid-cloud-architect/SKILL.md
+++ b/web-app/public/skills/hybrid-cloud-architect/SKILL.md
@@ -1,6 +1,6 @@
---
name: hybrid-cloud-architect
-description: Expert hybrid cloud architect specializing in complex multi-cloud
+description: "Expert hybrid cloud architect specializing in complex multi-cloud"
solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters
hybrid connectivity, workload placement optimization, edge computing, and
cross-cloud automation. Handles compliance, cost optimization, disaster
@@ -8,6 +8,8 @@ description: Expert hybrid cloud architect specializing in complex multi-cloud
multi-cloud strategy, or complex infrastructure integration.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/hybrid-cloud-networking/SKILL.md b/web-app/public/skills/hybrid-cloud-networking/SKILL.md
index fb72b613..960d1793 100644
--- a/web-app/public/skills/hybrid-cloud-networking/SKILL.md
+++ b/web-app/public/skills/hybrid-cloud-networking/SKILL.md
@@ -1,6 +1,8 @@
---
name: hybrid-cloud-networking
-description: Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.
+description: "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ..."
+risk: unknown
+source: community
---
# Hybrid Cloud Networking
diff --git a/web-app/public/skills/hybrid-search-implementation/SKILL.md b/web-app/public/skills/hybrid-search-implementation/SKILL.md
index bfbe99a7..28287662 100644
--- a/web-app/public/skills/hybrid-search-implementation/SKILL.md
+++ b/web-app/public/skills/hybrid-search-implementation/SKILL.md
@@ -1,6 +1,8 @@
---
name: hybrid-search-implementation
-description: Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.
+description: "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall."
+risk: unknown
+source: community
---
# Hybrid Search Implementation
diff --git a/web-app/public/skills/i18n-localization/SKILL.md b/web-app/public/skills/i18n-localization/SKILL.md
index 8b960dbf..5f76f5ff 100644
--- a/web-app/public/skills/i18n-localization/SKILL.md
+++ b/web-app/public/skills/i18n-localization/SKILL.md
@@ -1,7 +1,9 @@
---
name: i18n-localization
-description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
+description: "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# i18n & Localization
@@ -152,3 +154,6 @@ Before shipping:
| Script | Purpose | Command |
|--------|---------|---------|
| `scripts/i18n_checker.py` | Detect hardcoded strings & missing translations | `python scripts/i18n_checker.py ` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/idor-testing/SKILL.md b/web-app/public/skills/idor-testing/SKILL.md
index 945e16d0..9715aed8 100644
--- a/web-app/public/skills/idor-testing/SKILL.md
+++ b/web-app/public/skills/idor-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: IDOR Vulnerability Testing
-description: This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control," "enumerate user IDs or object references," or "bypass authorization to access other users' data." It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.
+name: idor-testing
+description: "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# IDOR Vulnerability Testing
@@ -440,3 +442,6 @@ def download_receipt(request, receipt_id):
return FileResponse(receipt.file)
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/imagen/SKILL.md b/web-app/public/skills/imagen/SKILL.md
index 92b0bb50..1497cc89 100644
--- a/web-app/public/skills/imagen/SKILL.md
+++ b/web-app/public/skills/imagen/SKILL.md
@@ -1,6 +1,6 @@
---
name: imagen
-description: |
+description: "|"
source: "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
risk: safe
---
diff --git a/web-app/public/skills/incident-responder/SKILL.md b/web-app/public/skills/incident-responder/SKILL.md
index 61526f01..f78f9519 100644
--- a/web-app/public/skills/incident-responder/SKILL.md
+++ b/web-app/public/skills/incident-responder/SKILL.md
@@ -1,6 +1,6 @@
---
name: incident-responder
-description: Expert SRE incident responder specializing in rapid problem
+description: "Expert SRE incident responder specializing in rapid problem"
resolution, modern observability, and comprehensive incident management.
Masters incident command, blameless post-mortems, error budget management, and
system reliability patterns. Handles critical outages, communication
@@ -8,6 +8,8 @@ description: Expert SRE incident responder specializing in rapid problem
incidents or SRE practices.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/incident-response-incident-response/SKILL.md b/web-app/public/skills/incident-response-incident-response/SKILL.md
index a37dc042..5c0f8564 100644
--- a/web-app/public/skills/incident-response-incident-response/SKILL.md
+++ b/web-app/public/skills/incident-response-incident-response/SKILL.md
@@ -1,6 +1,8 @@
---
name: incident-response-incident-response
description: "Use when working with incident response incident response"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/incident-response-smart-fix/SKILL.md b/web-app/public/skills/incident-response-smart-fix/SKILL.md
index bafc299a..b22844ea 100644
--- a/web-app/public/skills/incident-response-smart-fix/SKILL.md
+++ b/web-app/public/skills/incident-response-smart-fix/SKILL.md
@@ -1,6 +1,8 @@
---
name: incident-response-smart-fix
description: "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res"
+risk: unknown
+source: community
---
# Intelligent Issue Resolution with Multi-Agent Orchestration
diff --git a/web-app/public/skills/incident-runbook-templates/SKILL.md b/web-app/public/skills/incident-runbook-templates/SKILL.md
index f0e595e4..b3fdd635 100644
--- a/web-app/public/skills/incident-runbook-templates/SKILL.md
+++ b/web-app/public/skills/incident-runbook-templates/SKILL.md
@@ -1,6 +1,8 @@
---
name: incident-runbook-templates
-description: Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.
+description: "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp..."
+risk: unknown
+source: community
---
# Incident Runbook Templates
diff --git a/web-app/public/skills/infinite-gratitude/SKILL.md b/web-app/public/skills/infinite-gratitude/SKILL.md
index 2362abe3..af00e979 100644
--- a/web-app/public/skills/infinite-gratitude/SKILL.md
+++ b/web-app/public/skills/infinite-gratitude/SKILL.md
@@ -1,6 +1,6 @@
---
-name: Infinite Gratitude
-description: Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).
+name: infinite-gratitude
+description: "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies)."
risk: safe
source: https://github.com/sstklen/infinite-gratitude
---
diff --git a/web-app/public/skills/inngest/SKILL.md b/web-app/public/skills/inngest/SKILL.md
index 10df9fe2..10496387 100644
--- a/web-app/public/skills/inngest/SKILL.md
+++ b/web-app/public/skills/inngest/SKILL.md
@@ -1,7 +1,8 @@
---
name: inngest
-description: "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven workflow, step function, durable execution."
+description: "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Inngest Integration
@@ -53,3 +54,6 @@ Functions that run on a schedule
## Related Skills
Works well with: `nextjs-app-router`, `vercel-deployment`, `supabase-backend`, `email-systems`, `ai-agents-architect`, `stripe-integration`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/instagram-automation/SKILL.md b/web-app/public/skills/instagram-automation/SKILL.md
index 31a27d0d..eb5d233c 100644
--- a/web-app/public/skills/instagram-automation/SKILL.md
+++ b/web-app/public/skills/instagram-automation/SKILL.md
@@ -3,6 +3,8 @@ name: instagram-automation
description: "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Instagram Automation via Rube MCP
@@ -190,3 +192,6 @@ Automate Instagram operations through Composio's Instagram toolkit via Rube MCP.
| Get publishing limit | INSTAGRAM_GET_IG_USER_CONTENT_PUBLISHING_LIMIT | ig_user_id |
| Get media comments | INSTAGRAM_GET_IG_MEDIA_COMMENTS | ig_media_id |
| Get carousel children | INSTAGRAM_GET_IG_MEDIA_CHILDREN | ig_media_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/interactive-portfolio/SKILL.md b/web-app/public/skills/interactive-portfolio/SKILL.md
index 110f519d..5289d98f 100644
--- a/web-app/public/skills/interactive-portfolio/SKILL.md
+++ b/web-app/public/skills/interactive-portfolio/SKILL.md
@@ -1,7 +1,8 @@
---
name: interactive-portfolio
-description: "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities. Use when: portfolio, personal website, showcase work, developer portfolio, designer portfolio."
+description: "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Interactive Portfolio
@@ -221,3 +222,6 @@ Personality throughout.
## Related Skills
Works well with: `scroll-experience`, `3d-web-experience`, `landing-page-design`, `personal-branding`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/intercom-automation/SKILL.md b/web-app/public/skills/intercom-automation/SKILL.md
index 84435acf..656fbee1 100644
--- a/web-app/public/skills/intercom-automation/SKILL.md
+++ b/web-app/public/skills/intercom-automation/SKILL.md
@@ -3,6 +3,8 @@ name: intercom-automation
description: "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Intercom Automation via Rube MCP
@@ -246,3 +248,6 @@ Automate Intercom operations through Composio's Intercom toolkit via Rube MCP.
| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |
| Get counts | INTERCOM_GET_COUNTS | type, count |
| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/internal-comms-anthropic/SKILL.md b/web-app/public/skills/internal-comms-anthropic/SKILL.md
index 56ea935b..bc40f61d 100644
--- a/web-app/public/skills/internal-comms-anthropic/SKILL.md
+++ b/web-app/public/skills/internal-comms-anthropic/SKILL.md
@@ -1,7 +1,9 @@
---
-name: internal-comms
-description: A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
+name: internal-comms-anthropic
+description: "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
## When to use this skill
diff --git a/web-app/public/skills/internal-comms-community/SKILL.md b/web-app/public/skills/internal-comms-community/SKILL.md
index 56ea935b..939ad74f 100644
--- a/web-app/public/skills/internal-comms-community/SKILL.md
+++ b/web-app/public/skills/internal-comms-community/SKILL.md
@@ -1,7 +1,9 @@
---
-name: internal-comms
-description: A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
+name: internal-comms-community
+description: "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
## When to use this skill
diff --git a/web-app/public/skills/ios-developer/SKILL.md b/web-app/public/skills/ios-developer/SKILL.md
index f6e8fcd4..8fa9a17d 100644
--- a/web-app/public/skills/ios-developer/SKILL.md
+++ b/web-app/public/skills/ios-developer/SKILL.md
@@ -1,11 +1,13 @@
---
name: ios-developer
-description: Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,
+description: "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,"
SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.
Use PROACTIVELY for iOS-specific features, App Store optimization, or native
iOS development.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/istio-traffic-management/SKILL.md b/web-app/public/skills/istio-traffic-management/SKILL.md
index 8a34203b..deac85b7 100644
--- a/web-app/public/skills/istio-traffic-management/SKILL.md
+++ b/web-app/public/skills/istio-traffic-management/SKILL.md
@@ -1,6 +1,8 @@
---
name: istio-traffic-management
-description: Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
+description: "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie..."
+risk: unknown
+source: community
---
# Istio Traffic Management
diff --git a/web-app/public/skills/java-pro/SKILL.md b/web-app/public/skills/java-pro/SKILL.md
index a2b850f7..3b7e0a08 100644
--- a/web-app/public/skills/java-pro/SKILL.md
+++ b/web-app/public/skills/java-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: java-pro
-description: Master Java 21+ with modern features like virtual threads, pattern
+description: "Master Java 21+ with modern features like virtual threads, pattern"
matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including
GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java
development, microservices architecture, or performance optimization.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/javascript-mastery/SKILL.md b/web-app/public/skills/javascript-mastery/SKILL.md
index 8ff57410..e27daf57 100644
--- a/web-app/public/skills/javascript-mastery/SKILL.md
+++ b/web-app/public/skills/javascript-mastery/SKILL.md
@@ -1,6 +1,8 @@
---
name: javascript-mastery
-description: "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional programming. Use when explaining JS concepts, debugging JavaScript issues, or teaching JavaScript fundamentals."
+description: "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p..."
+risk: unknown
+source: community
---
# 🧠 JavaScript Mastery
diff --git a/web-app/public/skills/javascript-pro/SKILL.md b/web-app/public/skills/javascript-pro/SKILL.md
index 6377b7f7..2b4f0d18 100644
--- a/web-app/public/skills/javascript-pro/SKILL.md
+++ b/web-app/public/skills/javascript-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: javascript-pro
-description: Master modern JavaScript with ES6+, async patterns, and Node.js
+description: "Master modern JavaScript with ES6+, async patterns, and Node.js"
APIs. Handles promises, event loops, and browser/Node compatibility. Use
PROACTIVELY for JavaScript optimization, async debugging, or complex JS
patterns.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are a JavaScript expert specializing in modern JS and async programming.
diff --git a/web-app/public/skills/javascript-testing-patterns/SKILL.md b/web-app/public/skills/javascript-testing-patterns/SKILL.md
index d7cd039e..a5ee7ecd 100644
--- a/web-app/public/skills/javascript-testing-patterns/SKILL.md
+++ b/web-app/public/skills/javascript-testing-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: javascript-testing-patterns
-description: Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
+description: "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use..."
+risk: unknown
+source: community
---
# JavaScript Testing Patterns
diff --git a/web-app/public/skills/javascript-typescript-typescript-scaffold/SKILL.md b/web-app/public/skills/javascript-typescript-typescript-scaffold/SKILL.md
index 1cd696eb..2eee1ab8 100644
--- a/web-app/public/skills/javascript-typescript-typescript-scaffold/SKILL.md
+++ b/web-app/public/skills/javascript-typescript-typescript-scaffold/SKILL.md
@@ -1,6 +1,8 @@
---
name: javascript-typescript-typescript-scaffold
description: "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N"
+risk: unknown
+source: community
---
# TypeScript Project Scaffolding
diff --git a/web-app/public/skills/jira-automation/SKILL.md b/web-app/public/skills/jira-automation/SKILL.md
index 88b503fc..7fde6c20 100644
--- a/web-app/public/skills/jira-automation/SKILL.md
+++ b/web-app/public/skills/jira-automation/SKILL.md
@@ -3,6 +3,8 @@ name: jira-automation
description: "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Jira Automation via Rube MCP
@@ -183,3 +185,6 @@ Automate Jira operations through Composio's Jira toolkit via Rube MCP.
| List filters | JIRA_LIST_FILTERS | (none) |
| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |
| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/julia-pro/SKILL.md b/web-app/public/skills/julia-pro/SKILL.md
index 9fda5bb3..d0063344 100644
--- a/web-app/public/skills/julia-pro/SKILL.md
+++ b/web-app/public/skills/julia-pro/SKILL.md
@@ -1,12 +1,14 @@
---
name: julia-pro
-description: Master Julia 1.10+ with modern features, performance optimization,
+description: "Master Julia 1.10+ with modern features, performance optimization,"
multiple dispatch, and production-ready practices. Expert in the Julia
ecosystem including package management, scientific computing, and
high-performance numerical code. Use PROACTIVELY for Julia development,
optimization, or advanced Julia patterns.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/k8s-manifest-generator/SKILL.md b/web-app/public/skills/k8s-manifest-generator/SKILL.md
index fda9fb5c..80e5ff1b 100644
--- a/web-app/public/skills/k8s-manifest-generator/SKILL.md
+++ b/web-app/public/skills/k8s-manifest-generator/SKILL.md
@@ -1,6 +1,8 @@
---
name: k8s-manifest-generator
-description: Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
+description: "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat..."
+risk: unknown
+source: community
---
# Kubernetes Manifest Generator
diff --git a/web-app/public/skills/k8s-security-policies/SKILL.md b/web-app/public/skills/k8s-security-policies/SKILL.md
index 09fceae5..799b79f6 100644
--- a/web-app/public/skills/k8s-security-policies/SKILL.md
+++ b/web-app/public/skills/k8s-security-policies/SKILL.md
@@ -1,6 +1,8 @@
---
name: k8s-security-policies
-description: Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards.
+description: "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ..."
+risk: unknown
+source: community
---
# Kubernetes Security Policies
diff --git a/web-app/public/skills/kaizen/SKILL.md b/web-app/public/skills/kaizen/SKILL.md
index 0f5d47c2..bf117419 100644
--- a/web-app/public/skills/kaizen/SKILL.md
+++ b/web-app/public/skills/kaizen/SKILL.md
@@ -1,6 +1,8 @@
---
name: kaizen
-description: Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
+description: "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements."
+risk: unknown
+source: community
---
# Kaizen: Continuous Improvement
diff --git a/web-app/public/skills/klaviyo-automation/SKILL.md b/web-app/public/skills/klaviyo-automation/SKILL.md
index d5dc32d3..861576b1 100644
--- a/web-app/public/skills/klaviyo-automation/SKILL.md
+++ b/web-app/public/skills/klaviyo-automation/SKILL.md
@@ -3,6 +3,8 @@ name: klaviyo-automation
description: "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Klaviyo Automation via Rube MCP
@@ -188,3 +190,6 @@ fields__template=['name', 'html', 'text']
| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |
| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |
| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/kotlin-coroutines-expert/SKILL.md b/web-app/public/skills/kotlin-coroutines-expert/SKILL.md
new file mode 100644
index 00000000..0960b392
--- /dev/null
+++ b/web-app/public/skills/kotlin-coroutines-expert/SKILL.md
@@ -0,0 +1,100 @@
+---
+name: kotlin-coroutines-expert
+description: Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.
+risk: safe
+source: community
+---
+
+# Kotlin Coroutines Expert
+
+## Overview
+
+A guide to mastering asynchronous programming with Kotlin Coroutines. Covers advanced topics like structured concurrency, `Flow` transformations, exception handling, and testing strategies.
+
+## When to Use This Skill
+
+- Use when implementing asynchronous operations in Kotlin.
+- Use when designing reactive data streams with `Flow`.
+- Use when debugging coroutine cancellations or exceptions.
+- Use when writing unit tests for suspending functions or Flows.
+
+## Step-by-Step Guide
+
+### 1. Structured Concurrency
+
+Always launch coroutines within a defined `CoroutineScope`. Use `coroutineScope` or `supervisorScope` to group concurrent tasks.
+
+```kotlin
+suspend fun loadDashboardData(): DashboardData = coroutineScope {
+ val userDeferred = async { userRepo.getUser() }
+ val settingsDeferred = async { settingsRepo.getSettings() }
+
+ DashboardData(
+ user = userDeferred.await(),
+ settings = settingsDeferred.await()
+ )
+}
+```
+
+### 2. Exception Handling
+
+Use `CoroutineExceptionHandler` for top-level scopes, but rely on `try-catch` within suspending functions for granular control.
+
+```kotlin
+val handler = CoroutineExceptionHandler { _, exception ->
+ println("Caught $exception")
+}
+
+viewModelScope.launch(handler) {
+ try {
+ riskyOperation()
+ } catch (e: IOException) {
+ // Handle network error specifically
+ }
+}
+```
+
+### 3. Reactive Streams with Flow
+
+Use `StateFlow` for state that needs to be retained, and `SharedFlow` for events.
+
+```kotlin
+// Cold Flow (Lazy)
+val searchResults: Flow> = searchQuery
+ .debounce(300)
+ .flatMapLatest { query -> searchRepo.search(query) }
+ .flowOn(Dispatchers.IO)
+
+// Hot Flow (State)
+val uiState: StateFlow = _uiState.asStateFlow()
+```
+
+## Examples
+
+### Example 1: Parallel Execution with Error Handling
+
+```kotlin
+suspend fun fetchDataWithErrorHandling() = supervisorScope {
+ val task1 = async {
+ try { api.fetchA() } catch (e: Exception) { null }
+ }
+ val task2 = async { api.fetchB() }
+
+ // If task2 fails, task1 is NOT cancelled because of supervisorScope
+ val result1 = task1.await()
+ val result2 = task2.await() // May throw
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `Dispatchers.IO` for blocking I/O operations.
+- ✅ **Do:** Cancel scopes when they are no longer needed (e.g., `ViewModel.onCleared`).
+- ✅ **Do:** Use `TestScope` and `runTest` for unit testing coroutines.
+- ❌ **Don't:** Use `GlobalScope`. It breaks structured concurrency and can lead to leaks.
+- ❌ **Don't:** Catch `CancellationException` unless you rethrow it.
+
+## Troubleshooting
+
+**Problem:** Coroutine test hangs or fails unpredictably.
+**Solution:** Ensure you are using `runTest` and injecting `TestDispatcher` into your classes so you can control virtual time.
diff --git a/web-app/public/skills/kpi-dashboard-design/SKILL.md b/web-app/public/skills/kpi-dashboard-design/SKILL.md
index 36bdc09f..b1b49215 100644
--- a/web-app/public/skills/kpi-dashboard-design/SKILL.md
+++ b/web-app/public/skills/kpi-dashboard-design/SKILL.md
@@ -1,6 +1,8 @@
---
name: kpi-dashboard-design
-description: Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data visualization layouts.
+description: "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ..."
+risk: unknown
+source: community
---
# KPI Dashboard Design
diff --git a/web-app/public/skills/kubernetes-architect/SKILL.md b/web-app/public/skills/kubernetes-architect/SKILL.md
index 072a59df..b8ac829c 100644
--- a/web-app/public/skills/kubernetes-architect/SKILL.md
+++ b/web-app/public/skills/kubernetes-architect/SKILL.md
@@ -1,6 +1,6 @@
---
name: kubernetes-architect
-description: Expert Kubernetes architect specializing in cloud-native
+description: "Expert Kubernetes architect specializing in cloud-native"
infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise
container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),
progressive delivery, multi-tenancy, and platform engineering. Handles
@@ -9,6 +9,8 @@ description: Expert Kubernetes architect specializing in cloud-native
platform design.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.
diff --git a/web-app/public/skills/kubernetes-deployment/SKILL.md b/web-app/public/skills/kubernetes-deployment/SKILL.md
new file mode 100644
index 00000000..47a46eaf
--- /dev/null
+++ b/web-app/public/skills/kubernetes-deployment/SKILL.md
@@ -0,0 +1,167 @@
+---
+name: kubernetes-deployment
+description: "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations."
+source: personal
+risk: safe
+domain: cloud-devops
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Kubernetes Deployment Workflow
+
+## Overview
+
+Specialized workflow for deploying applications to Kubernetes including container orchestration, Helm charts, service mesh configuration, and production-ready K8s patterns.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Deploying to Kubernetes
+- Creating Helm charts
+- Configuring service mesh
+- Setting up K8s networking
+- Implementing K8s security
+
+## Workflow Phases
+
+### Phase 1: Container Preparation
+
+#### Skills to Invoke
+- `docker-expert` - Docker containerization
+- `k8s-manifest-generator` - K8s manifests
+
+#### Actions
+1. Create Dockerfile
+2. Build container image
+3. Optimize image size
+4. Push to registry
+5. Test container
+
+#### Copy-Paste Prompts
+```
+Use @docker-expert to containerize application for K8s
+```
+
+### Phase 2: K8s Manifests
+
+#### Skills to Invoke
+- `k8s-manifest-generator` - Manifest generation
+- `kubernetes-architect` - K8s architecture
+
+#### Actions
+1. Create Deployment
+2. Configure Service
+3. Set up ConfigMap
+4. Create Secrets
+5. Add Ingress
+
+#### Copy-Paste Prompts
+```
+Use @k8s-manifest-generator to create K8s manifests
+```
+
+### Phase 3: Helm Chart
+
+#### Skills to Invoke
+- `helm-chart-scaffolding` - Helm charts
+
+#### Actions
+1. Create chart structure
+2. Define values.yaml
+3. Add templates
+4. Configure dependencies
+5. Test chart
+
+#### Copy-Paste Prompts
+```
+Use @helm-chart-scaffolding to create Helm chart
+```
+
+### Phase 4: Service Mesh
+
+#### Skills to Invoke
+- `istio-traffic-management` - Istio
+- `linkerd-patterns` - Linkerd
+- `service-mesh-expert` - Service mesh
+
+#### Actions
+1. Choose service mesh
+2. Install mesh
+3. Configure traffic management
+4. Set up mTLS
+5. Add observability
+
+#### Copy-Paste Prompts
+```
+Use @istio-traffic-management to configure Istio
+```
+
+### Phase 5: Security
+
+#### Skills to Invoke
+- `k8s-security-policies` - K8s security
+- `mtls-configuration` - mTLS
+
+#### Actions
+1. Configure RBAC
+2. Set up NetworkPolicy
+3. Enable PodSecurity
+4. Configure secrets
+5. Implement mTLS
+
+#### Copy-Paste Prompts
+```
+Use @k8s-security-policies to secure Kubernetes cluster
+```
+
+### Phase 6: Observability
+
+#### Skills to Invoke
+- `grafana-dashboards` - Grafana
+- `prometheus-configuration` - Prometheus
+
+#### Actions
+1. Install monitoring stack
+2. Configure Prometheus
+3. Create Grafana dashboards
+4. Set up alerts
+5. Add distributed tracing
+
+#### Copy-Paste Prompts
+```
+Use @prometheus-configuration to set up K8s monitoring
+```
+
+### Phase 7: Deployment
+
+#### Skills to Invoke
+- `deployment-engineer` - Deployment
+- `gitops-workflow` - GitOps
+
+#### Actions
+1. Configure CI/CD
+2. Set up GitOps
+3. Deploy to cluster
+4. Verify deployment
+5. Monitor rollout
+
+#### Copy-Paste Prompts
+```
+Use @gitops-workflow to implement GitOps deployment
+```
+
+## Quality Gates
+
+- [ ] Containers working
+- [ ] Manifests valid
+- [ ] Helm chart installs
+- [ ] Security configured
+- [ ] Monitoring active
+- [ ] Deployment successful
+
+## Related Workflow Bundles
+
+- `cloud-devops` - Cloud/DevOps
+- `terraform-infrastructure` - Infrastructure
+- `docker-containerization` - Containers
diff --git a/web-app/public/skills/langchain-architecture/SKILL.md b/web-app/public/skills/langchain-architecture/SKILL.md
index 15cdf183..52aaa7f2 100644
--- a/web-app/public/skills/langchain-architecture/SKILL.md
+++ b/web-app/public/skills/langchain-architecture/SKILL.md
@@ -1,6 +1,8 @@
---
name: langchain-architecture
-description: Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM workflows.
+description: "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w..."
+risk: unknown
+source: community
---
# LangChain Architecture
diff --git a/web-app/public/skills/langfuse/SKILL.md b/web-app/public/skills/langfuse/SKILL.md
index 3fd579c6..2174ed8e 100644
--- a/web-app/public/skills/langfuse/SKILL.md
+++ b/web-app/public/skills/langfuse/SKILL.md
@@ -1,7 +1,8 @@
---
name: langfuse
-description: "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation."
+description: "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Langfuse
@@ -236,3 +237,6 @@ Add relevant metadata.
## Related Skills
Works well with: `langgraph`, `crewai`, `structured-output`, `autonomous-agents`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/langgraph/SKILL.md b/web-app/public/skills/langgraph/SKILL.md
index de595e2c..0e9a571d 100644
--- a/web-app/public/skills/langgraph/SKILL.md
+++ b/web-app/public/skills/langgraph/SKILL.md
@@ -1,7 +1,8 @@
---
name: langgraph
-description: "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern. Used in production at LinkedIn, Uber, and 400+ companies. This is LangChain's recommended approach for building agents. Use when: langgraph, langchain agent, stateful agent, agent graph, react agent."
+description: "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# LangGraph
@@ -285,3 +286,6 @@ Clear separation of concerns.
## Related Skills
Works well with: `crewai`, `autonomous-agents`, `langfuse`, `structured-output`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/laravel-expert/SKILL.md b/web-app/public/skills/laravel-expert/SKILL.md
index 1aa3ee83..26b1e6c2 100644
--- a/web-app/public/skills/laravel-expert/SKILL.md
+++ b/web-app/public/skills/laravel-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: laravel-expert
-description: Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).
+description: "Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+)."
risk: safe
source: community
---
diff --git a/web-app/public/skills/laravel-security-audit/SKILL.md b/web-app/public/skills/laravel-security-audit/SKILL.md
index 7c0ce018..68f430c2 100644
--- a/web-app/public/skills/laravel-security-audit/SKILL.md
+++ b/web-app/public/skills/laravel-security-audit/SKILL.md
@@ -1,6 +1,6 @@
---
name: laravel-security-audit
-description: Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.
+description: "Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices."
risk: safe
source: community
---
diff --git a/web-app/public/skills/last30days/SKILL.md b/web-app/public/skills/last30days/SKILL.md
index a9758111..bbf731c6 100644
--- a/web-app/public/skills/last30days/SKILL.md
+++ b/web-app/public/skills/last30days/SKILL.md
@@ -1,11 +1,13 @@
---
name: last30days
-description: Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.
+description: "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool."
argument-hint: "[topic] for [tool] or [topic]"
context: fork
agent: Explore
disable-model-invocation: true
allowed-tools: Bash, Read, Write, AskUserQuestion, WebSearch
+risk: unknown
+source: community
---
# last30days: Research Any Topic from the Last 30 Days
@@ -419,3 +421,6 @@ Want another prompt? Just tell me what you're creating next.
💡 Unlock Reddit & X data: Add API keys to ~/.config/last30days/.env
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/launch-strategy/SKILL.md b/web-app/public/skills/launch-strategy/SKILL.md
index b1c4593e..cc80517c 100644
--- a/web-app/public/skills/launch-strategy/SKILL.md
+++ b/web-app/public/skills/launch-strategy/SKILL.md
@@ -1,6 +1,8 @@
---
name: launch-strategy
-description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum."
+description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'..."
+risk: unknown
+source: community
---
# Launch Strategy
@@ -342,3 +344,6 @@ If you need more context:
- **page-cro**: For optimizing launch landing pages
- **marketing-psychology**: For psychology behind waitlists and exclusivity
- **programmatic-seo**: For comparison pages mentioned in post-launch
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/legacy-modernizer/SKILL.md b/web-app/public/skills/legacy-modernizer/SKILL.md
index ad92b237..daf6efe5 100644
--- a/web-app/public/skills/legacy-modernizer/SKILL.md
+++ b/web-app/public/skills/legacy-modernizer/SKILL.md
@@ -1,11 +1,13 @@
---
name: legacy-modernizer
-description: Refactor legacy codebases, migrate outdated frameworks, and
+description: "Refactor legacy codebases, migrate outdated frameworks, and"
implement gradual modernization. Handles technical debt, dependency updates,
and backward compatibility. Use PROACTIVELY for legacy system updates,
framework migrations, or technical debt reduction.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/legal-advisor/SKILL.md b/web-app/public/skills/legal-advisor/SKILL.md
index 24b9d2f2..267335a8 100644
--- a/web-app/public/skills/legal-advisor/SKILL.md
+++ b/web-app/public/skills/legal-advisor/SKILL.md
@@ -1,11 +1,13 @@
---
name: legal-advisor
-description: Draft privacy policies, terms of service, disclaimers, and legal
+description: "Draft privacy policies, terms of service, disclaimers, and legal"
notices. Creates GDPR-compliant texts, cookie policies, and data processing
agreements. Use PROACTIVELY for legal documentation, compliance texts, or
regulatory requirements.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/libreoffice/base/SKILL.md b/web-app/public/skills/libreoffice/base/SKILL.md
new file mode 100644
index 00000000..cd2cead9
--- /dev/null
+++ b/web-app/public/skills/libreoffice/base/SKILL.md
@@ -0,0 +1,188 @@
+---
+name: base
+description: "Database management, forms, reports, and data operations with LibreOffice Base."
+source: personal
+risk: safe
+domain: office-productivity
+category: database-processing
+version: 1.0.0
+---
+
+# LibreOffice Base
+
+## Overview
+
+LibreOffice Base skill for creating, managing, and automating database workflows using the native ODB (OpenDocument Database) format.
+
+## When to Use This Skill
+
+Use this skill when:
+- Creating new databases in ODB format
+- Connecting to external databases (MySQL, PostgreSQL, etc.)
+- Automating database operations and reports
+- Creating forms and reports
+- Building database applications
+
+## Core Capabilities
+
+### 1. Database Creation
+- Create new ODB databases from scratch
+- Design tables, views, and relationships
+- Create embedded HSQLDB/Firebird databases
+- Connect to external databases
+
+### 2. Data Operations
+- Import data from CSV, spreadsheets
+- Export data to various formats
+- Query execution and management
+- Batch data processing
+
+### 3. Form and Report Automation
+- Create data entry forms
+- Design custom reports
+- Automate report generation
+- Build form templates
+
+### 4. Query and SQL
+- Visual query design
+- SQL query execution
+- Query optimization
+- Result set manipulation
+
+### 5. Integration
+- Command-line automation
+- Python scripting with UNO
+- JDBC/ODBC connectivity
+
+## Workflows
+
+### Creating a New Database
+
+#### Method 1: Command-Line
+```bash
+soffice --base
+```
+
+#### Method 2: Python with UNO
+```python
+import uno
+
+def create_database():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx)
+ doc.storeToURL("file:///path/to/database.odb", ())
+ doc.close(True)
+```
+
+### Connecting to External Database
+
+```python
+import uno
+
+def connect_to_mysql(host, port, database, user, password):
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+
+ doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx)
+ datasource = doc.getDataSource()
+ datasource.URL = f"sdbc:mysql:jdbc:mysql://{host}:{port}/{database}"
+ datasource.Properties["UserName"] = user
+ datasource.Properties["Password"] = password
+
+ doc.storeToURL("file:///path/to/connected.odb", ())
+ return doc
+```
+
+## Database Connection Reference
+
+### Supported Database Types
+- HSQLDB (embedded)
+- Firebird (embedded)
+- MySQL/MariaDB
+- PostgreSQL
+- SQLite
+- ODBC data sources
+- JDBC data sources
+
+### Connection Strings
+
+```
+# MySQL
+sdbc:mysql:jdbc:mysql://localhost:3306/database
+
+# PostgreSQL
+sdbc:postgresql://localhost:5432/database
+
+# SQLite
+sdbc:sqlite:file:///path/to/database.db
+
+# ODBC
+sdbc:odbc:DSN_NAME
+```
+
+## Command-Line Reference
+
+```bash
+soffice --headless
+soffice --base # Base
+```
+
+## Python Libraries
+
+```bash
+pip install pyodbc # ODBC connectivity
+pip install sqlalchemy # SQL toolkit
+```
+
+## Best Practices
+
+1. Use parameterized queries
+2. Create indexes for performance
+3. Backup databases regularly
+4. Use transactions for data integrity
+5. Store ODB source files in version control
+6. Document database schema
+7. Use appropriate data types
+8. Handle connection errors gracefully
+
+## Troubleshooting
+
+### Cannot open socket
+```bash
+killall soffice.bin
+soffice --headless --accept="socket,host=localhost,port=8100;urp;"
+```
+
+### Connection Issues
+- Verify database server is running
+- Check connection string format
+- Ensure JDBC/ODBC drivers are installed
+- Verify network connectivity
+
+## Resources
+
+- [LibreOffice Base Guide](https://documentation.libreoffice.org/)
+- [UNO API Reference](https://api.libreoffice.org/)
+- [HSQLDB Documentation](http://hsqldb.org/)
+- [Firebird Documentation](https://firebirdsql.org/)
+
+## Related Skills
+
+- writer
+- calc
+- impress
+- draw
+- workflow-automation
diff --git a/web-app/public/skills/libreoffice/calc/SKILL.md b/web-app/public/skills/libreoffice/calc/SKILL.md
new file mode 100644
index 00000000..10e24ea9
--- /dev/null
+++ b/web-app/public/skills/libreoffice/calc/SKILL.md
@@ -0,0 +1,201 @@
+---
+name: calc
+description: "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc."
+source: personal
+risk: safe
+domain: office-productivity
+category: spreadsheet-processing
+version: 1.0.0
+---
+
+# LibreOffice Calc
+
+## Overview
+
+LibreOffice Calc skill for creating, editing, converting, and automating spreadsheet workflows using the native ODS (OpenDocument Spreadsheet) format.
+
+## When to Use This Skill
+
+Use this skill when:
+- Creating new spreadsheets in ODS format
+- Converting between ODS, XLSX, CSV, PDF formats
+- Automating data processing and analysis
+- Creating formulas, charts, and pivot tables
+- Batch processing spreadsheet operations
+
+## Core Capabilities
+
+### 1. Spreadsheet Creation
+- Create new ODS spreadsheets from scratch
+- Generate spreadsheets from templates
+- Create data entry forms
+- Build dashboards and reports
+
+### 2. Format Conversion
+- ODS to other formats: XLSX, CSV, PDF, HTML
+- Other formats to ODS: XLSX, XLS, CSV, DBF
+- Batch conversion of multiple files
+
+### 3. Data Automation
+- Formula automation and calculations
+- Data import from CSV, database, APIs
+- Data export to various formats
+- Batch data processing
+
+### 4. Data Analysis
+- Pivot tables and data summarization
+- Statistical functions and analysis
+- Data validation and filtering
+- Conditional formatting
+
+### 5. Integration
+- Command-line automation via soffice
+- Python scripting with UNO
+- Database connectivity
+
+## Workflows
+
+### Creating a New Spreadsheet
+
+#### Method 1: Command-Line
+```bash
+soffice --calc template.ods
+```
+
+#### Method 2: Python with UNO
+```python
+import uno
+
+def create_spreadsheet():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.sheet.SpreadsheetDocument", ctx)
+ sheets = doc.getSheets()
+ sheet = sheets.getByIndex(0)
+ cell = sheet.getCellByPosition(0, 0)
+ cell.setString("Hello from LibreOffice Calc!")
+ doc.storeToURL("file:///path/to/spreadsheet.ods", ())
+ doc.close(True)
+```
+
+#### Method 3: Using ezodf
+```python
+import ezodf
+
+doc = ezodf.newdoc('ods', 'spreadsheet.ods')
+sheet = doc.sheets[0]
+sheet['A1'].set_value('Hello')
+sheet['B1'].set_value('World')
+doc.save()
+```
+
+### Converting Spreadsheets
+
+```bash
+# ODS to XLSX
+soffice --headless --convert-to xlsx spreadsheet.ods
+
+# ODS to CSV
+soffice --headless --convert-to csv spreadsheet.ods
+
+# ODS to PDF
+soffice --headless --convert-to pdf spreadsheet.ods
+
+# XLSX to ODS
+soffice --headless --convert-to ods spreadsheet.xlsx
+
+# Batch convert
+for file in *.ods; do
+ soffice --headless --convert-to xlsx "$file"
+done
+```
+
+### Formula Automation
+```python
+import uno
+
+def create_formula_spreadsheet():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.sheet.SpreadsheetDocument", ctx)
+ sheet = doc.getSheets().getByIndex(0)
+
+ sheet.getCellByPosition(0, 0).setDoubleValue(100)
+ sheet.getCellByPosition(0, 1).setDoubleValue(200)
+
+ cell = sheet.getCellByPosition(0, 2)
+ cell.setFormula("SUM(A1:A2)")
+
+ doc.storeToURL("file:///path/to/formulas.ods", ())
+ doc.close(True)
+```
+
+## Format Conversion Reference
+
+### Supported Input Formats
+- ODS (native), XLSX, XLS, CSV, DBF, HTML
+
+### Supported Output Formats
+- ODS, XLSX, XLS, CSV, PDF, HTML
+
+## Command-Line Reference
+
+```bash
+soffice --headless
+soffice --headless --convert-to
+soffice --calc # Calc
+```
+
+## Python Libraries
+
+```bash
+pip install ezodf # ODS handling
+pip install odfpy # ODF manipulation
+pip install pandas # Data analysis
+```
+
+## Best Practices
+
+1. Use named ranges for clarity
+2. Document complex formulas
+3. Use data validation for input control
+4. Create templates for recurring reports
+5. Store ODS source files in version control
+6. Test conversions thoroughly
+7. Use CSV for data exchange
+8. Handle conversion failures gracefully
+
+## Troubleshooting
+
+### Cannot open socket
+```bash
+killall soffice.bin
+soffice --headless --accept="socket,host=localhost,port=8100;urp;"
+```
+
+## Resources
+
+- [LibreOffice Calc Guide](https://documentation.libreoffice.org/)
+- [UNO API Reference](https://api.libreoffice.org/)
+- [ezodf Documentation](http://ezodf.rst2.org/)
+
+## Related Skills
+
+- writer
+- impress
+- draw
+- base
+- xlsx-official
+- workflow-automation
diff --git a/web-app/public/skills/libreoffice/draw/SKILL.md b/web-app/public/skills/libreoffice/draw/SKILL.md
new file mode 100644
index 00000000..747e8245
--- /dev/null
+++ b/web-app/public/skills/libreoffice/draw/SKILL.md
@@ -0,0 +1,165 @@
+---
+name: draw
+description: "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw."
+source: personal
+risk: safe
+domain: office-productivity
+category: graphics-processing
+version: 1.0.0
+---
+
+# LibreOffice Draw
+
+## Overview
+
+LibreOffice Draw skill for creating, editing, converting, and automating vector graphics and diagram workflows using the native ODG (OpenDocument Drawing) format.
+
+## When to Use This Skill
+
+Use this skill when:
+- Creating vector graphics and diagrams in ODG format
+- Converting between ODG, SVG, PDF, PNG formats
+- Automating diagram and flowchart generation
+- Creating technical drawings and schematics
+- Batch processing graphics operations
+
+## Core Capabilities
+
+### 1. Graphics Creation
+- Create new ODG drawings from scratch
+- Generate diagrams from templates
+- Create flowcharts and org charts
+- Design technical drawings
+
+### 2. Format Conversion
+- ODG to other formats: SVG, PDF, PNG, JPG
+- Other formats to ODG: SVG, PDF
+- Batch conversion of multiple files
+
+### 3. Diagram Automation
+- Template-based diagram generation
+- Automated flowchart creation
+- Dynamic shape generation
+- Batch diagram production
+
+### 4. Graphics Manipulation
+- Shape creation and manipulation
+- Path and bezier curve editing
+- Layer management
+- Text and label insertion
+
+### 5. Integration
+- Command-line automation via soffice
+- Python scripting with UNO
+- Integration with workflow tools
+
+## Workflows
+
+### Creating a New Drawing
+
+#### Method 1: Command-Line
+```bash
+soffice --draw template.odg
+```
+
+#### Method 2: Python with UNO
+```python
+import uno
+
+def create_drawing():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.drawing.DrawingDocument", ctx)
+ page = doc.getDrawPages().getByIndex(0)
+ doc.storeToURL("file:///path/to/drawing.odg", ())
+ doc.close(True)
+```
+
+### Converting Drawings
+
+```bash
+# ODG to SVG
+soffice --headless --convert-to svg drawing.odg
+
+# ODG to PDF
+soffice --headless --convert-to pdf drawing.odg
+
+# ODG to PNG
+soffice --headless --convert-to png:PNG_drawing drawing.odg
+
+# SVG to ODG
+soffice --headless --convert-to odg drawing.svg
+
+# Batch convert
+for file in *.odg; do
+ soffice --headless --convert-to pdf "$file"
+done
+```
+
+## Format Conversion Reference
+
+### Supported Input Formats
+- ODG (native), SVG, PDF
+
+### Supported Output Formats
+- ODG, SVG, PDF, PNG, JPG, GIF, BMP, WMF, EMF
+
+## Command-Line Reference
+
+```bash
+soffice --headless
+soffice --headless --convert-to
+soffice --draw # Draw
+```
+
+## Python Libraries
+
+```bash
+pip install ezodf # ODF handling
+pip install odfpy # ODF manipulation
+pip install svgwrite # SVG generation
+```
+
+## Best Practices
+
+1. Use layers for organization
+2. Create templates for recurring diagrams
+3. Use vector formats for scalability
+4. Name objects for easy reference
+5. Store ODG source files in version control
+6. Test conversions thoroughly
+7. Export to SVG for web use
+
+## Troubleshooting
+
+### Cannot open socket
+```bash
+killall soffice.bin
+soffice --headless --accept="socket,host=localhost,port=8100;urp;"
+```
+
+### Quality Issues in PNG Export
+```bash
+soffice --headless --convert-to png:PNG_drawing_Export \
+ --filterData='{"Width":2048,"Height":2048}' drawing.odg
+```
+
+## Resources
+
+- [LibreOffice Draw Guide](https://documentation.libreoffice.org/)
+- [UNO API Reference](https://api.libreoffice.org/)
+- [SVG Specification](https://www.w3.org/TR/SVG/)
+
+## Related Skills
+
+- writer
+- calc
+- impress
+- base
+- workflow-automation
diff --git a/web-app/public/skills/libreoffice/impress/SKILL.md b/web-app/public/skills/libreoffice/impress/SKILL.md
new file mode 100644
index 00000000..d4c8d958
--- /dev/null
+++ b/web-app/public/skills/libreoffice/impress/SKILL.md
@@ -0,0 +1,174 @@
+---
+name: impress
+description: "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress."
+source: personal
+risk: safe
+domain: office-productivity
+category: presentation-processing
+version: 1.0.0
+---
+
+# LibreOffice Impress
+
+## Overview
+
+LibreOffice Impress skill for creating, editing, converting, and automating presentation workflows using the native ODP (OpenDocument Presentation) format.
+
+## When to Use This Skill
+
+Use this skill when:
+- Creating new presentations in ODP format
+- Converting between ODP, PPTX, PDF formats
+- Automating slide generation from templates
+- Batch processing presentation operations
+- Creating presentation templates
+
+## Core Capabilities
+
+### 1. Presentation Creation
+- Create new ODP presentations from scratch
+- Generate presentations from templates
+- Create slide masters and layouts
+- Build interactive presentations
+
+### 2. Format Conversion
+- ODP to other formats: PPTX, PDF, HTML, SWF
+- Other formats to ODP: PPTX, PPT, PDF
+- Batch conversion of multiple files
+
+### 3. Slide Automation
+- Template-based slide generation
+- Batch slide creation from data
+- Automated content insertion
+- Dynamic chart generation
+
+### 4. Content Manipulation
+- Text and image insertion
+- Shape and diagram creation
+- Animation and transition control
+- Speaker notes management
+
+### 5. Integration
+- Command-line automation via soffice
+- Python scripting with UNO
+- Integration with workflow tools
+
+## Workflows
+
+### Creating a New Presentation
+
+#### Method 1: Command-Line
+```bash
+soffice --impress template.odp
+```
+
+#### Method 2: Python with UNO
+```python
+import uno
+
+def create_presentation():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.presentation.PresentationDocument", ctx)
+ slides = doc.getDrawPages()
+ slide = slides.getByIndex(0)
+ doc.storeToURL("file:///path/to/presentation.odp", ())
+ doc.close(True)
+```
+
+### Converting Presentations
+
+```bash
+# ODP to PPTX
+soffice --headless --convert-to pptx presentation.odp
+
+# ODP to PDF
+soffice --headless --convert-to pdf presentation.odp
+
+# PPTX to ODP
+soffice --headless --convert-to odp presentation.pptx
+
+# Batch convert
+for file in *.odp; do
+ soffice --headless --convert-to pdf "$file"
+done
+```
+
+### Template-Based Generation
+```python
+import subprocess
+import tempfile
+from pathlib import Path
+
+def generate_from_template(template_path, content, output_path):
+ with tempfile.TemporaryDirectory() as tmpdir:
+ subprocess.run(['unzip', '-q', template_path, '-d', tmpdir])
+ content_file = Path(tmpdir) / 'content.xml'
+ content_xml = content_file.read_text()
+ for key, value in content.items():
+ content_xml = content_xml.replace(f'${{{key}}}', str(value))
+ content_file.write_text(content_xml)
+ subprocess.run(['zip', '-rq', output_path, '.'], cwd=tmpdir)
+ return output_path
+```
+
+## Format Conversion Reference
+
+### Supported Input Formats
+- ODP (native), PPTX, PPT, PDF
+
+### Supported Output Formats
+- ODP, PPTX, PDF, HTML, SWF
+
+## Command-Line Reference
+
+```bash
+soffice --headless
+soffice --headless --convert-to
+soffice --impress # Impress
+```
+
+## Python Libraries
+
+```bash
+pip install ezodf # ODF handling
+pip install odfpy # ODF manipulation
+```
+
+## Best Practices
+
+1. Use slide masters for consistency
+2. Create templates for recurring presentations
+3. Embed fonts for PDF distribution
+4. Use vector graphics when possible
+5. Store ODP source files in version control
+6. Test conversions thoroughly
+7. Keep file sizes manageable
+
+## Troubleshooting
+
+### Cannot open socket
+```bash
+killall soffice.bin
+soffice --headless --accept="socket,host=localhost,port=8100;urp;"
+```
+
+## Resources
+
+- [LibreOffice Impress Guide](https://documentation.libreoffice.org/)
+- [UNO API Reference](https://api.libreoffice.org/)
+
+## Related Skills
+
+- writer
+- calc
+- draw
+- base
+- pptx-official
+- workflow-automation
diff --git a/web-app/public/skills/libreoffice/writer/SKILL.md b/web-app/public/skills/libreoffice/writer/SKILL.md
new file mode 100644
index 00000000..4ae435ef
--- /dev/null
+++ b/web-app/public/skills/libreoffice/writer/SKILL.md
@@ -0,0 +1,200 @@
+---
+name: writer
+description: "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer."
+source: personal
+risk: safe
+domain: office-productivity
+category: document-processing
+version: 1.0.0
+---
+
+# LibreOffice Writer
+
+## Overview
+
+LibreOffice Writer skill for creating, editing, converting, and automating document workflows using the native ODT (OpenDocument Text) format.
+
+## When to Use This Skill
+
+Use this skill when:
+- Creating new documents in ODT format
+- Converting documents between formats (ODT <-> DOCX, PDF, HTML, RTF, TXT)
+- Automating document generation workflows
+- Performing batch document operations
+- Creating templates and standardized document formats
+
+## Core Capabilities
+
+### 1. Document Creation
+- Create new ODT documents from scratch
+- Generate documents from templates
+- Create mail merge documents
+- Build forms with fillable fields
+
+### 2. Format Conversion
+- ODT to other formats: DOCX, PDF, HTML, RTF, TXT, EPUB
+- Other formats to ODT: DOCX, DOC, RTF, HTML, TXT
+- Batch conversion of multiple documents
+
+### 3. Document Automation
+- Template-based document generation
+- Mail merge with data sources (CSV, spreadsheet, database)
+- Batch document processing
+- Automated report generation
+
+### 4. Content Manipulation
+- Text extraction and insertion
+- Style management and application
+- Table creation and manipulation
+- Header/footer management
+
+### 5. Integration
+- Command-line automation via soffice
+- Python scripting with UNO
+- Integration with workflow automation tools
+
+## Workflows
+
+### Creating a New Document
+
+#### Method 1: Command-Line
+```bash
+soffice --writer template.odt
+```
+
+#### Method 2: Python with UNO
+```python
+import uno
+
+def create_document():
+ local_ctx = uno.getComponentContext()
+ resolver = local_ctx.ServiceManager.createInstanceWithContext(
+ "com.sun.star.bridge.UnoUrlResolver", local_ctx
+ )
+ ctx = resolver.resolve(
+ "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
+ )
+ smgr = ctx.ServiceManager
+ doc = smgr.createInstanceWithContext("com.sun.star.text.TextDocument", ctx)
+ text = doc.Text
+ cursor = text.createTextCursor()
+ text.insertString(cursor, "Hello from LibreOffice Writer!", 0)
+ doc.storeToURL("file:///path/to/document.odt", ())
+ doc.close(True)
+```
+
+#### Method 3: Using odfpy
+```python
+from odf.opendocument import OpenDocumentText
+from odf.text import P, H
+
+doc = OpenDocumentText()
+h1 = H(outlinelevel='1', text='Document Title')
+doc.text.appendChild(h1)
+doc.save("document.odt")
+```
+
+### Converting Documents
+
+```bash
+# ODT to DOCX
+soffice --headless --convert-to docx document.odt
+
+# ODT to PDF
+soffice --headless --convert-to pdf document.odt
+
+# DOCX to ODT
+soffice --headless --convert-to odt document.docx
+
+# Batch convert
+for file in *.odt; do
+ soffice --headless --convert-to pdf "$file"
+done
+```
+
+### Template-Based Generation
+```python
+import subprocess
+import tempfile
+from pathlib import Path
+
+def generate_from_template(template_path, variables, output_path):
+ with tempfile.TemporaryDirectory() as tmpdir:
+ subprocess.run(['unzip', '-q', template_path, '-d', tmpdir])
+ content_file = Path(tmpdir) / 'content.xml'
+ content = content_file.read_text()
+ for key, value in variables.items():
+ content = content.replace(f'${{{key}}}', str(value))
+ content_file.write_text(content)
+ subprocess.run(['zip', '-rq', output_path, '.'], cwd=tmpdir)
+ return output_path
+```
+
+## Format Conversion Reference
+
+### Supported Input Formats
+- ODT (native), DOCX, DOC, RTF, HTML, TXT, EPUB
+
+### Supported Output Formats
+- ODT, DOCX, PDF, PDF/A, HTML, RTF, TXT, EPUB
+
+## Command-Line Reference
+
+```bash
+soffice --headless
+soffice --headless --convert-to
+soffice --writer # Writer
+soffice --calc # Calc
+soffice --impress # Impress
+soffice --draw # Draw
+```
+
+## Python Libraries
+
+```bash
+pip install odfpy # ODF manipulation
+pip install ezodf # Easier ODF handling
+```
+
+## Best Practices
+
+1. Use styles for consistency
+2. Create templates for recurring documents
+3. Ensure accessibility (heading hierarchy, alt text)
+4. Fill document metadata
+5. Store ODT source files in version control
+6. Test conversions thoroughly
+7. Embed fonts for PDF distribution
+8. Handle conversion failures gracefully
+9. Log automation operations
+10. Clean temporary files
+
+## Troubleshooting
+
+### Cannot open socket
+```bash
+killall soffice.bin
+soffice --headless --accept="socket,host=localhost,port=8100;urp;"
+```
+
+### Conversion Quality Issues
+```bash
+soffice --headless --convert-to pdf:writer_pdf_Export document.odt
+```
+
+## Resources
+
+- [LibreOffice Writer Guide](https://documentation.libreoffice.org/)
+- [LibreOffice SDK](https://wiki.documentfoundation.org/Documentation/DevGuide)
+- [UNO API Reference](https://api.libreoffice.org/)
+- [odfpy](https://pypi.org/project/odfpy/)
+
+## Related Skills
+
+- calc
+- impress
+- draw
+- base
+- docx-official
+- pdf-official
+- workflow-automation
diff --git a/web-app/public/skills/linear-automation/SKILL.md b/web-app/public/skills/linear-automation/SKILL.md
index b69374f2..d3c4de91 100644
--- a/web-app/public/skills/linear-automation/SKILL.md
+++ b/web-app/public/skills/linear-automation/SKILL.md
@@ -3,6 +3,8 @@ name: linear-automation
description: "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Linear Automation via Rube MCP
@@ -176,3 +178,6 @@ Automate Linear operations through Composio's Linear toolkit via Rube MCP.
| List users | LINEAR_LIST_LINEAR_USERS | (none) |
| Current user | LINEAR_GET_CURRENT_USER | (none) |
| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/linear-claude-skill/SKILL.md b/web-app/public/skills/linear-claude-skill/SKILL.md
index 92e280cd..cd0efe8e 100644
--- a/web-app/public/skills/linear-claude-skill/SKILL.md
+++ b/web-app/public/skills/linear-claude-skill/SKILL.md
@@ -360,7 +360,7 @@ Choose the right tool for the task:
}
```
-> **WARNING**: Do NOT use deprecated community servers. See [troubleshooting.md](troubleshooting.md) for details.
+> **WARNING**: Do NOT use deprecated community servers. See troubleshooting.md for details.
### MCP Reliability (Official Server)
@@ -383,7 +383,7 @@ node scripts/linear-helpers.mjs update-status Done 123 124 125
### Helper Script Reference
-For detailed helper script usage, see **[troubleshooting.md](troubleshooting.md)**.
+For detailed helper script usage, see **troubleshooting.md**.
### Parallel Agent Execution
@@ -409,7 +409,7 @@ Task({
- Quick status checks
- Operations needing immediate results
-See **[sync.md](sync.md)** for parallel execution patterns.
+See **sync.md** for parallel execution patterns.
## Critical Requirements
@@ -422,7 +422,7 @@ See **[sync.md](sync.md)** for parallel execution patterns.
| Issue | Project | Not visible in project board |
| Project | Initiative | Not visible in roadmap |
-See **[projects.md](projects.md)** for complete project creation checklist.
+See **projects.md** for complete project creation checklist.
---
@@ -435,7 +435,7 @@ See **[projects.md](projects.md)** for complete project creation checklist.
### Labels
-Uses **domain-based label taxonomy**. See [docs/labels.md](docs/labels.md).
+Uses **domain-based label taxonomy**. See docs/labels.md.
**Key rules:**
- ONE Type label: `feature`, `bug`, `refactor`, `chore`, `spike`
@@ -464,7 +464,7 @@ Scripts provide full type hints and are easier to debug than raw GraphQL for mul
**Fallback only.** Use when operations aren't supported by MCP or SDK.
-See **[api.md](api.md)** for complete documentation including:
+See **api.md** for complete documentation including:
- Authentication and setup
- Example queries and mutations
- Timeout handling patterns
@@ -479,7 +479,7 @@ npx tsx ~/.claude/skills/linear/scripts/query.ts "query { viewer { name } }"
## Projects & Initiatives
-For advanced project and initiative management patterns, see **[projects.md](projects.md)**.
+For advanced project and initiative management patterns, see **projects.md**.
**Quick reference** - common project commands:
@@ -515,7 +515,7 @@ Manage Linear issues, projects, and teams
Use this skill when working with manage linear issues, projects, and teams.
## Sync Patterns (Bulk Operations)
-For bulk synchronization of code changes to Linear, see **[sync.md](sync.md)**.
+For bulk synchronization of code changes to Linear, see **sync.md**.
**Quick sync commands:**
@@ -533,11 +533,11 @@ npx tsx scripts/linear-ops.ts project-status "My Project" completed
| Document | Purpose |
|----------|---------|
-| [api.md](api.md) | GraphQL API reference, timeout handling |
-| [sdk.md](sdk.md) | SDK automation patterns |
-| [sync.md](sync.md) | Bulk sync patterns |
-| [projects.md](projects.md) | Project & initiative management |
-| [troubleshooting.md](troubleshooting.md) | Common issues, MCP debugging |
-| [docs/labels.md](docs/labels.md) | Label taxonomy |
+| api.md | GraphQL API reference, timeout handling |
+| sdk.md | SDK automation patterns |
+| sync.md | Bulk sync patterns |
+| projects.md | Project & initiative management |
+| troubleshooting.md | Common issues, MCP debugging |
+| docs/labels.md | Label taxonomy |
**External:** [Linear MCP Documentation](https://linear.app/docs/mcp.md)
diff --git a/web-app/public/skills/linkedin-automation/SKILL.md b/web-app/public/skills/linkedin-automation/SKILL.md
index db247410..ea6ddb1b 100644
--- a/web-app/public/skills/linkedin-automation/SKILL.md
+++ b/web-app/public/skills/linkedin-automation/SKILL.md
@@ -3,6 +3,8 @@ name: linkedin-automation
description: "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# LinkedIn Automation via Rube MCP
@@ -173,3 +175,6 @@ Automate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP.
| Get uploaded images | LINKEDIN_GET_IMAGES | image_id |
| Delete post | LINKEDIN_DELETE_LINKED_IN_POST | post_id |
| Comment on post | LINKEDIN_CREATE_COMMENT_ON_POST | post_id, text, actor |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/linkerd-patterns/SKILL.md b/web-app/public/skills/linkerd-patterns/SKILL.md
index 34a73c47..caa71d0a 100644
--- a/web-app/public/skills/linkerd-patterns/SKILL.md
+++ b/web-app/public/skills/linkerd-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: linkerd-patterns
-description: Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
+description: "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ..."
+risk: unknown
+source: community
---
# Linkerd Patterns
diff --git a/web-app/public/skills/lint-and-validate/SKILL.md b/web-app/public/skills/lint-and-validate/SKILL.md
index 313fed0f..0f1d342a 100644
--- a/web-app/public/skills/lint-and-validate/SKILL.md
+++ b/web-app/public/skills/lint-and-validate/SKILL.md
@@ -1,7 +1,9 @@
---
name: lint-and-validate
-description: "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis."
+description: "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v..."
allowed-tools: Read, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Lint and Validate Skill
@@ -43,3 +45,6 @@ allowed-tools: Read, Glob, Grep, Bash
| `scripts/lint_runner.py` | Unified lint check | `python scripts/lint_runner.py ` |
| `scripts/type_coverage.py` | Type coverage analysis | `python scripts/type_coverage.py ` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/linux-privilege-escalation/SKILL.md b/web-app/public/skills/linux-privilege-escalation/SKILL.md
index 39db53b2..d7219400 100644
--- a/web-app/public/skills/linux-privilege-escalation/SKILL.md
+++ b/web-app/public/skills/linux-privilege-escalation/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Linux Privilege Escalation
-description: This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.
+name: linux-privilege-escalation
+description: "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Linux Privilege Escalation
@@ -502,3 +504,6 @@ uid=1000(user) gid=1000(user) euid=0(root)
| Reverse shell not connecting | Check firewall; try ports 443/80; use staged payloads; check egress filtering |
| SUID binary not exploitable | Verify version matches GTFOBins; check AppArmor/SELinux; some binaries drop privileges |
| Cron job not executing | Verify cron running: `service cron status`; check +x permissions; verify PATH in crontab |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/linux-shell-scripting/SKILL.md b/web-app/public/skills/linux-shell-scripting/SKILL.md
index e0fd143a..ca8a9b85 100644
--- a/web-app/public/skills/linux-shell-scripting/SKILL.md
+++ b/web-app/public/skills/linux-shell-scripting/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Linux Production Shell Scripts
-description: This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.
+name: linux-shell-scripting
+description: "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Linux Production Shell Scripts
@@ -502,3 +504,6 @@ Minute(0-59) Hour(0-23) Day(1-31) Month(1-12) Weekday(0-7, 0/7=Sun)
- Quote variables to handle spaces properly
- Many scripts require root/sudo privileges
- Use `bash -x script.sh` for debugging
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/linux-troubleshooting/SKILL.md b/web-app/public/skills/linux-troubleshooting/SKILL.md
new file mode 100644
index 00000000..464c57f9
--- /dev/null
+++ b/web-app/public/skills/linux-troubleshooting/SKILL.md
@@ -0,0 +1,221 @@
+---
+name: linux-troubleshooting
+description: "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures."
+source: personal
+risk: safe
+domain: system-administration
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Linux Troubleshooting Workflow
+
+## Overview
+
+Specialized workflow for diagnosing and resolving Linux system issues including performance problems, service failures, network issues, and resource constraints.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Diagnosing system performance issues
+- Troubleshooting service failures
+- Investigating network problems
+- Resolving disk space issues
+- Debugging application errors
+
+## Workflow Phases
+
+### Phase 1: Initial Assessment
+
+#### Skills to Invoke
+- `bash-linux` - Linux commands
+- `devops-troubleshooter` - Troubleshooting
+
+#### Actions
+1. Check system uptime
+2. Review recent changes
+3. Identify symptoms
+4. Gather error messages
+5. Document findings
+
+#### Commands
+```bash
+uptime
+hostnamectl
+cat /etc/os-release
+dmesg | tail -50
+```
+
+#### Copy-Paste Prompts
+```
+Use @bash-linux to gather system information
+```
+
+### Phase 2: Resource Analysis
+
+#### Skills to Invoke
+- `bash-linux` - Resource commands
+- `performance-engineer` - Performance analysis
+
+#### Actions
+1. Check CPU usage
+2. Analyze memory
+3. Review disk space
+4. Monitor I/O
+5. Check network
+
+#### Commands
+```bash
+top -bn1 | head -20
+free -h
+df -h
+iostat -x 1 5
+```
+
+#### Copy-Paste Prompts
+```
+Use @performance-engineer to analyze system resources
+```
+
+### Phase 3: Process Investigation
+
+#### Skills to Invoke
+- `bash-linux` - Process commands
+- `server-management` - Process management
+
+#### Actions
+1. List running processes
+2. Identify resource hogs
+3. Check process status
+4. Review process trees
+5. Analyze strace output
+
+#### Commands
+```bash
+ps aux --sort=-%cpu | head -10
+pstree -p
+lsof -p PID
+strace -p PID
+```
+
+#### Copy-Paste Prompts
+```
+Use @server-management to investigate processes
+```
+
+### Phase 4: Log Analysis
+
+#### Skills to Invoke
+- `bash-linux` - Log commands
+- `error-detective` - Error detection
+
+#### Actions
+1. Check system logs
+2. Review application logs
+3. Search for errors
+4. Analyze log patterns
+5. Correlate events
+
+#### Commands
+```bash
+journalctl -xe
+tail -f /var/log/syslog
+grep -i error /var/log/*
+```
+
+#### Copy-Paste Prompts
+```
+Use @error-detective to analyze log files
+```
+
+### Phase 5: Network Diagnostics
+
+#### Skills to Invoke
+- `bash-linux` - Network commands
+- `network-engineer` - Network troubleshooting
+
+#### Actions
+1. Check network interfaces
+2. Test connectivity
+3. Analyze connections
+4. Review firewall rules
+5. Check DNS resolution
+
+#### Commands
+```bash
+ip addr show
+ss -tulpn
+curl -v http://target
+dig domain
+```
+
+#### Copy-Paste Prompts
+```
+Use @network-engineer to diagnose network issues
+```
+
+### Phase 6: Service Troubleshooting
+
+#### Skills to Invoke
+- `server-management` - Service management
+- `systematic-debugging` - Debugging
+
+#### Actions
+1. Check service status
+2. Review service logs
+3. Test service restart
+4. Verify dependencies
+5. Check configuration
+
+#### Commands
+```bash
+systemctl status service
+journalctl -u service -f
+systemctl restart service
+```
+
+#### Copy-Paste Prompts
+```
+Use @systematic-debugging to troubleshoot service issues
+```
+
+### Phase 7: Resolution
+
+#### Skills to Invoke
+- `incident-responder` - Incident response
+- `bash-pro` - Fix implementation
+
+#### Actions
+1. Implement fix
+2. Verify resolution
+3. Monitor stability
+4. Document solution
+5. Create prevention plan
+
+#### Copy-Paste Prompts
+```
+Use @incident-responder to implement resolution
+```
+
+## Troubleshooting Checklist
+
+- [ ] System information gathered
+- [ ] Resources analyzed
+- [ ] Logs reviewed
+- [ ] Network tested
+- [ ] Services verified
+- [ ] Issue resolved
+- [ ] Documentation created
+
+## Quality Gates
+
+- [ ] Root cause identified
+- [ ] Fix verified
+- [ ] Monitoring in place
+- [ ] Documentation complete
+
+## Related Workflow Bundles
+
+- `os-scripting` - OS scripting
+- `bash-scripting` - Bash scripting
+- `cloud-devops` - DevOps
diff --git a/web-app/public/skills/llm-app-patterns/SKILL.md b/web-app/public/skills/llm-app-patterns/SKILL.md
index 548a3f54..692b2813 100644
--- a/web-app/public/skills/llm-app-patterns/SKILL.md
+++ b/web-app/public/skills/llm-app-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: llm-app-patterns
-description: "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability."
+description: "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin..."
+risk: unknown
+source: community
---
# 🤖 LLM Application Patterns
@@ -474,7 +476,7 @@ class PromptChain:
# Parse output if needed
if step.get("parser"):
- output = step["parser"](output)
+ output = step"parser"
context[step["output_key"]] = output
results.append({
diff --git a/web-app/public/skills/llm-application-dev-ai-assistant/SKILL.md b/web-app/public/skills/llm-application-dev-ai-assistant/SKILL.md
index 21c2330b..6b41bb90 100644
--- a/web-app/public/skills/llm-application-dev-ai-assistant/SKILL.md
+++ b/web-app/public/skills/llm-application-dev-ai-assistant/SKILL.md
@@ -1,6 +1,8 @@
---
name: llm-application-dev-ai-assistant
description: "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur"
+risk: unknown
+source: community
---
# AI Assistant Development
diff --git a/web-app/public/skills/llm-application-dev-ai-assistant/resources/implementation-playbook.md b/web-app/public/skills/llm-application-dev-ai-assistant/resources/implementation-playbook.md
index 9ba809e3..29862066 100644
--- a/web-app/public/skills/llm-application-dev-ai-assistant/resources/implementation-playbook.md
+++ b/web-app/public/skills/llm-application-dev-ai-assistant/resources/implementation-playbook.md
@@ -657,7 +657,7 @@ class FunctionCallingInterface:
)
# Execute function
- result = await self.functions[function_name]['function'](**validated_args)
+ result = await self.functions[function_name]'function'
# Return result for LLM to process
return {
diff --git a/web-app/public/skills/llm-application-dev-langchain-agent/SKILL.md b/web-app/public/skills/llm-application-dev-langchain-agent/SKILL.md
index f55fafa4..d9ea2ac7 100644
--- a/web-app/public/skills/llm-application-dev-langchain-agent/SKILL.md
+++ b/web-app/public/skills/llm-application-dev-langchain-agent/SKILL.md
@@ -1,6 +1,8 @@
---
name: llm-application-dev-langchain-agent
description: "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph."
+risk: unknown
+source: community
---
# LangChain/LangGraph Agent Development Expert
diff --git a/web-app/public/skills/llm-application-dev-prompt-optimize/SKILL.md b/web-app/public/skills/llm-application-dev-prompt-optimize/SKILL.md
index 367077c7..6552f1b7 100644
--- a/web-app/public/skills/llm-application-dev-prompt-optimize/SKILL.md
+++ b/web-app/public/skills/llm-application-dev-prompt-optimize/SKILL.md
@@ -1,6 +1,8 @@
---
name: llm-application-dev-prompt-optimize
description: "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati"
+risk: unknown
+source: community
---
# Prompt Optimization
diff --git a/web-app/public/skills/llm-evaluation/SKILL.md b/web-app/public/skills/llm-evaluation/SKILL.md
index 499974d1..db95d5c7 100644
--- a/web-app/public/skills/llm-evaluation/SKILL.md
+++ b/web-app/public/skills/llm-evaluation/SKILL.md
@@ -1,6 +1,8 @@
---
name: llm-evaluation
-description: Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or establishing evaluation frameworks.
+description: "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ..."
+risk: unknown
+source: community
---
# LLM Evaluation
diff --git a/web-app/public/skills/loki-mode/SKILL.md b/web-app/public/skills/loki-mode/SKILL.md
index e7278ce7..875830fc 100644
--- a/web-app/public/skills/loki-mode/SKILL.md
+++ b/web-app/public/skills/loki-mode/SKILL.md
@@ -1,6 +1,8 @@
---
name: loki-mode
-description: Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.
+description: "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,..."
+risk: unknown
+source: community
---
# Loki Mode - Multi-Agent Autonomous Startup System
@@ -719,3 +721,6 @@ Detailed documentation is split into reference files for progressive loading:
---
**Version:** 2.32.0 | **Lines:** ~600 | **Research-Enhanced: Labs + HN Production Patterns**
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/m365-agents-dotnet/SKILL.md b/web-app/public/skills/m365-agents-dotnet/SKILL.md
index e846fe42..eb93c7eb 100644
--- a/web-app/public/skills/m365-agents-dotnet/SKILL.md
+++ b/web-app/public/skills/m365-agents-dotnet/SKILL.md
@@ -1,8 +1,10 @@
---
name: m365-agents-dotnet
-description: |
+description: "|"
Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "Microsoft.Agents", "AddAgentApplicationOptions", "AgentApplication", "AddAgentAspNetAuthentication", "Copilot Studio client", "IAgentHttpAdapter".
package: Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Authentication.Msal, Microsoft.Agents.CopilotStudio.Client
+risk: unknown
+source: community
---
# Microsoft 365 Agents SDK (.NET)
@@ -276,7 +278,7 @@ await foreach (var activity in client.AskQuestionAsync("Hello!", null))
| File | Contents |
| --- | --- |
-| [references/acceptance-criteria.md](references/acceptance-criteria.md) | Import paths, hosting pipeline, Copilot Studio client patterns, anti-patterns |
+| references/acceptance-criteria.md | Import paths, hosting pipeline, Copilot Studio client patterns, anti-patterns |
## Reference Links
@@ -288,3 +290,6 @@ await foreach (var activity in client.AskQuestionAsync("Hello!", null))
| Auth configuration options | https://learn.microsoft.com/en-us/microsoft-365/agents-sdk/microsoft-authentication-library-configuration-options |
| Copilot Studio integration | https://learn.microsoft.com/en-us/microsoft-365/agents-sdk/integrate-with-mcs |
| GitHub samples | https://github.com/microsoft/agents |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/m365-agents-py/SKILL.md b/web-app/public/skills/m365-agents-py/SKILL.md
index c16b2660..0583cd23 100644
--- a/web-app/public/skills/m365-agents-py/SKILL.md
+++ b/web-app/public/skills/m365-agents-py/SKILL.md
@@ -1,8 +1,10 @@
---
name: m365-agents-py
-description: |
+description: "|"
Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "microsoft_agents", "AgentApplication", "start_agent_process", "TurnContext", "Copilot Studio client", "CloudAdapter".
package: microsoft-agents-hosting-core, microsoft-agents-hosting-aiohttp, microsoft-agents-activity, microsoft-agents-authentication-msal, microsoft-agents-copilotstudio-client
+risk: unknown
+source: community
---
# Microsoft 365 Agents SDK (Python)
@@ -90,9 +92,7 @@ ADAPTER = CloudAdapter(connection_manager=CONNECTION_MANAGER)
AUTHORIZATION = Authorization(STORAGE, CONNECTION_MANAGER, **agents_sdk_config)
# Create AgentApplication
-AGENT_APP = AgentApplication[TurnState](
- storage=STORAGE, adapter=ADAPTER, authorization=AUTHORIZATION, **agents_sdk_config
-)
+AGENT_APP = AgentApplicationTurnState
@AGENT_APP.conversation_update("membersAdded")
@@ -136,9 +136,7 @@ from microsoft_agents.hosting.core import (
)
from microsoft_agents.activity import ActivityTypes
-AGENT_APP = AgentApplication[TurnState](
- storage=STORAGE, adapter=ADAPTER, authorization=AUTHORIZATION, **agents_sdk_config
-)
+AGENT_APP = AgentApplicationTurnState
# Welcome handler
@AGENT_APP.conversation_update("membersAdded")
@@ -333,7 +331,7 @@ asyncio.run(main())
| File | Contents |
| --- | --- |
-| [references/acceptance-criteria.md](references/acceptance-criteria.md) | Import paths, hosting pipeline, streaming, OAuth, and Copilot Studio patterns |
+| references/acceptance-criteria.md | Import paths, hosting pipeline, streaming, OAuth, and Copilot Studio patterns |
## Reference Links
@@ -343,3 +341,6 @@ asyncio.run(main())
| GitHub samples (Python) | https://github.com/microsoft/Agents-for-python |
| PyPI packages | https://pypi.org/search/?q=microsoft-agents |
| Integrate with Copilot Studio | https://learn.microsoft.com/en-us/microsoft-365/agents-sdk/integrate-with-mcs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/m365-agents-ts/SKILL.md b/web-app/public/skills/m365-agents-ts/SKILL.md
index c596b9be..f62cadf7 100644
--- a/web-app/public/skills/m365-agents-ts/SKILL.md
+++ b/web-app/public/skills/m365-agents-ts/SKILL.md
@@ -1,8 +1,10 @@
---
name: m365-agents-ts
-description: |
+description: "|"
Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: "Microsoft 365 Agents SDK", "@microsoft/agents-hosting", "AgentApplication", "startServer", "streamingResponse", "Copilot Studio client", "@microsoft/agents-copilotstudio-client".
package: "@microsoft/agents-hosting, @microsoft/agents-hosting-express, @microsoft/agents-activity, @microsoft/agents-copilotstudio-client"
+risk: unknown
+source: community
---
# Microsoft 365 Agents SDK (TypeScript)
@@ -168,7 +170,7 @@ window.WebChat.renderWebChat({
| File | Contents |
| --- | --- |
-| [references/acceptance-criteria.md](references/acceptance-criteria.md) | Import paths, hosting pipeline, streaming, and Copilot Studio patterns |
+| references/acceptance-criteria.md | Import paths, hosting pipeline, streaming, and Copilot Studio patterns |
## Reference Links
@@ -180,3 +182,6 @@ window.WebChat.renderWebChat({
| @microsoft/agents-copilotstudio-client | https://learn.microsoft.com/en-us/javascript/api/%40microsoft/agents-copilotstudio-client?view=agents-sdk-js-latest |
| Integrate with Copilot Studio | https://learn.microsoft.com/en-us/microsoft-365/agents-sdk/integrate-with-mcs |
| GitHub samples | https://github.com/microsoft/Agents/tree/main/samples/nodejs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/machine-learning-ops-ml-pipeline/SKILL.md b/web-app/public/skills/machine-learning-ops-ml-pipeline/SKILL.md
index b6f924bf..f84d5823 100644
--- a/web-app/public/skills/machine-learning-ops-ml-pipeline/SKILL.md
+++ b/web-app/public/skills/machine-learning-ops-ml-pipeline/SKILL.md
@@ -1,6 +1,8 @@
---
name: machine-learning-ops-ml-pipeline
description: "Design and implement a complete ML pipeline for: $ARGUMENTS"
+risk: unknown
+source: community
---
# Machine Learning Pipeline - Multi-Agent MLOps Orchestration
diff --git a/web-app/public/skills/mailchimp-automation/SKILL.md b/web-app/public/skills/mailchimp-automation/SKILL.md
index 496d79de..eba17c07 100644
--- a/web-app/public/skills/mailchimp-automation/SKILL.md
+++ b/web-app/public/skills/mailchimp-automation/SKILL.md
@@ -3,6 +3,8 @@ name: mailchimp-automation
description: "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Mailchimp Automation via Rube MCP
@@ -229,3 +231,6 @@ subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest()
| Subscriber activity | `MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY` | `campaign_id`, `subscriber_hash` |
| Member recent activity | `MAILCHIMP_VIEW_RECENT_ACTIVITY` | `list_id`, `subscriber_hash` |
| Campaign content | `MAILCHIMP_GET_CAMPAIGN_CONTENT` | `campaign_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/make-automation/SKILL.md b/web-app/public/skills/make-automation/SKILL.md
index 8d40bce2..64c4e5f5 100644
--- a/web-app/public/skills/make-automation/SKILL.md
+++ b/web-app/public/skills/make-automation/SKILL.md
@@ -3,6 +3,8 @@ name: make-automation
description: "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Make Automation via Rube MCP
@@ -199,3 +201,6 @@ Instead of relying solely on Make's toolkit, build equivalent automation directl
3. Connect all required toolkits
4. Build the workflow step-by-step using individual app tools
5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/malware-analyst/SKILL.md b/web-app/public/skills/malware-analyst/SKILL.md
index 6bcbdf30..d6737995 100644
--- a/web-app/public/skills/malware-analyst/SKILL.md
+++ b/web-app/public/skills/malware-analyst/SKILL.md
@@ -1,12 +1,14 @@
---
name: malware-analyst
-description: Expert malware analyst specializing in defensive malware research,
+description: "Expert malware analyst specializing in defensive malware research,"
threat intelligence, and incident response. Masters sandbox analysis,
behavioral analysis, and malware family identification. Handles static/dynamic
analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,
threat hunting, incident response, or security research.
metadata:
model: opus
+risk: unknown
+source: community
---
# File identification
diff --git a/web-app/public/skills/manifest/SKILL.md b/web-app/public/skills/manifest/SKILL.md
new file mode 100644
index 00000000..7f6e01be
--- /dev/null
+++ b/web-app/public/skills/manifest/SKILL.md
@@ -0,0 +1,126 @@
+---
+name: manifest
+description: "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin."
+risk: unknown
+source: community
+---
+
+# Manifest Setup
+
+Follow these steps **in order**. Do not skip ahead.
+
+## Use this skill when
+
+- User wants to set up observability or telemetry for their agent
+- User wants to connect their agent to Manifest for monitoring
+- User needs to configure a Manifest API key or custom endpoint
+- User is troubleshooting Manifest plugin connection issues
+- User wants to verify the Manifest plugin is running
+
+## Do not use this skill when
+
+- User needs general observability design (use `observability-engineer` instead)
+- User wants to build custom dashboards or alerting rules
+- User is not using the Manifest platform
+
+## Instructions
+
+### Step 1 — Stop the gateway
+
+Stop the gateway first to avoid hot-reload issues during configuration.
+
+```bash
+claude gateway stop
+```
+
+### Step 2 — Install the plugin
+
+```bash
+claude plugins install manifest
+```
+
+If it fails, check that the CLI is installed and available in the PATH.
+
+### Step 3 — Get an API key
+
+Ask the user:
+
+> To connect your agent, you need a Manifest API key. Here's how to get one:
+>
+> 1. Go to **https://app.manifest.build** and create an account (or sign in)
+> 2. Once logged in, click **"Connect Agent"** to create a new agent
+> 3. Copy the API key that starts with `mnfst_`
+> 4. Paste it here
+
+Wait for a key starting with `mnfst_`. If the key doesn't match, tell the user the format looks incorrect and ask them to try again.
+
+### Step 4 — Configure the plugin
+
+```bash
+claude config set plugins.entries.manifest.config.apiKey "USER_API_KEY"
+```
+
+Replace `USER_API_KEY` with the actual key the user provided.
+
+Ask the user if they have a custom endpoint. If not, the default (`https://app.manifest.build/api/v1/otlp`) is used automatically. If they do:
+
+```bash
+claude config set plugins.entries.manifest.config.endpoint "USER_ENDPOINT"
+```
+
+### Step 5 — Start the gateway
+
+```bash
+claude gateway install
+```
+
+### Step 6 — Verify
+
+Wait 3 seconds for the gateway to fully start, then check the logs:
+
+```bash
+grep "manifest" ~/.claude/logs/gateway.log | tail -5
+```
+
+Look for:
+
+```
+[manifest] Observability pipeline active
+```
+
+If it appears, tell the user setup is complete. If not, check the error messages and troubleshoot.
+
+## Safety
+
+- Never log or echo the API key in plain text after configuration
+- Verify the key format (`mnfst_` prefix) before writing to config
+
+## Troubleshooting
+
+| Error | Fix |
+|-------|-----|
+| Missing apiKey | Re-run step 4 |
+| Invalid apiKey format | The key must start with `mnfst_` |
+| Connection refused | The endpoint is unreachable. Check the URL or ask if they self-host |
+| Duplicate OTel registration | Disable the conflicting built-in plugin: `claude plugins disable diagnostics-otel` |
+
+## Examples
+
+### Example 1: Basic setup
+
+```
+Use @manifest to set up observability for my agent.
+```
+
+### Example 2: Custom endpoint
+
+```
+Use @manifest to connect my agent to my self-hosted Manifest instance at https://manifest.internal.company.com/api/v1/otlp
+```
+
+## Best Practices
+
+- Always stop the gateway before making configuration changes
+- The default endpoint works for most users — only change it if self-hosting
+- API keys always start with `mnfst_` — any other format is invalid
+- Check gateway logs first when debugging any plugin issue
diff --git a/web-app/public/skills/market-sizing-analysis/SKILL.md b/web-app/public/skills/market-sizing-analysis/SKILL.md
index 071bced9..0768dcd3 100644
--- a/web-app/public/skills/market-sizing-analysis/SKILL.md
+++ b/web-app/public/skills/market-sizing-analysis/SKILL.md
@@ -1,11 +1,13 @@
---
name: market-sizing-analysis
-description: This skill should be used when the user asks to "calculate TAM",
+description: "This skill should be used when the user asks to \\\"calculate TAM\\\","
"determine SAM", "estimate SOM", "size the market", "calculate market
opportunity", "what's the total addressable market", or requests market sizing
analysis for a startup or business opportunity.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Market Sizing Analysis
diff --git a/web-app/public/skills/marketing-ideas/SKILL.md b/web-app/public/skills/marketing-ideas/SKILL.md
index b5104679..3704b986 100644
--- a/web-app/public/skills/marketing-ideas/SKILL.md
+++ b/web-app/public/skills/marketing-ideas/SKILL.md
@@ -1,6 +1,8 @@
---
name: marketing-ideas
-description: Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.
+description: "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system."
+risk: unknown
+source: community
---
# Marketing Ideas for SaaS (with Feasibility Scoring)
@@ -219,3 +221,6 @@ Use these biases when scoring:
* **programmatic-seo** – Scale SEO ideas
* **ab-test-setup** – Test ideas rigorously
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/marketing-psychology/SKILL.md b/web-app/public/skills/marketing-psychology/SKILL.md
index 8e6df28e..6b9d8a59 100644
--- a/web-app/public/skills/marketing-psychology/SKILL.md
+++ b/web-app/public/skills/marketing-psychology/SKILL.md
@@ -1,6 +1,8 @@
---
name: marketing-psychology
-description: Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.
+description: "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system."
+risk: unknown
+source: community
---
# Marketing Psychology & Mental Models
@@ -253,3 +255,6 @@ Before responding, confirm:
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/mcp-builder-ms/SKILL.md b/web-app/public/skills/mcp-builder-ms/SKILL.md
index 79263539..5db729f0 100644
--- a/web-app/public/skills/mcp-builder-ms/SKILL.md
+++ b/web-app/public/skills/mcp-builder-ms/SKILL.md
@@ -1,10 +1,16 @@
---
-name: mcp-builder
-description: Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).
+name: mcp-builder-ms
+description: "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte..."
+risk: unknown
+source: community
---
# MCP Server Development Guide
+## When to Use
+
+Use this skill when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
+
## Overview
Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
@@ -34,7 +40,7 @@ Before building a custom server, check if Microsoft already provides one:
| **Playwright MCP** | Local | Browser automation and testing |
| **GitHub MCP** | Remote | `https://api.githubcopilot.com/mcp` |
-**Full ecosystem:** See [🔷 Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) for complete server catalog and patterns.
+**Full ecosystem:** See 🔷 Microsoft MCP Patterns for complete server catalog and patterns.
### When to Use Microsoft vs Custom
@@ -44,7 +50,7 @@ Before building a custom server, check if Microsoft already provides one:
| AI Foundry agents/evals | Use **Foundry MCP** remote server |
| Custom internal APIs | Build **custom server** (this guide) |
| Third-party SaaS integration | Build **custom server** (this guide) |
-| Extending Azure MCP | Follow [Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md)
+| Extending Azure MCP | Follow Microsoft MCP Patterns
---
@@ -102,18 +108,18 @@ Key pages to review:
**Load framework documentation:**
-- **MCP Best Practices**: [📋 View Best Practices](./reference/mcp_best_practices.md) - Core guidelines
+- **MCP Best Practices**: 📋 View Best Practices - Core guidelines
**For TypeScript (recommended):**
- **TypeScript SDK**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
-- [⚡ TypeScript Guide](./reference/node_mcp_server.md) - TypeScript patterns and examples
+- ⚡ TypeScript Guide - TypeScript patterns and examples
**For Python:**
- **Python SDK**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
-- [🐍 Python Guide](./reference/python_mcp_server.md) - Python patterns and examples
+- 🐍 Python Guide - Python patterns and examples
**For C#/.NET (Microsoft ecosystem):**
-- [🔷 Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) - C# patterns, Azure MCP architecture, command hierarchy
+- 🔷 Microsoft MCP Patterns - C# patterns, Azure MCP architecture, command hierarchy
#### 1.4 Plan Your Implementation
@@ -130,9 +136,9 @@ Prioritize comprehensive API coverage. List endpoints to implement, starting wit
#### 2.1 Set Up Project Structure
See language-specific guides for project setup:
-- [⚡ TypeScript Guide](./reference/node_mcp_server.md) - Project structure, package.json, tsconfig.json
-- [🐍 Python Guide](./reference/python_mcp_server.md) - Module organization, dependencies
-- [🔷 Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) - C# project structure, command hierarchy
+- ⚡ TypeScript Guide - Project structure, package.json, tsconfig.json
+- 🐍 Python Guide - Module organization, dependencies
+- 🔷 Microsoft MCP Patterns - C# project structure, command hierarchy
#### 2.2 Implement Core Infrastructure
@@ -203,7 +209,7 @@ See language-specific guides for detailed testing approaches and quality checkli
After implementing your MCP server, create comprehensive evaluations to test its effectiveness.
-**Load [✅ Evaluation Guide](./reference/evaluation.md) for complete evaluation guidelines.**
+**Load ✅ Evaluation Guide for complete evaluation guidelines.**
#### 4.1 Understand Evaluation Purpose
@@ -252,7 +258,7 @@ Load these resources as needed during development:
### Core MCP Documentation (Load First)
- **MCP Protocol**: Start with sitemap at `https://modelcontextprotocol.io/sitemap.xml`, then fetch specific pages with `.md` suffix
-- [📋 MCP Best Practices](./reference/mcp_best_practices.md) - Universal MCP guidelines including:
+- 📋 MCP Best Practices - Universal MCP guidelines including:
- Server and tool naming conventions
- Response format guidelines (JSON vs Markdown)
- Pagination best practices
@@ -260,7 +266,7 @@ Load these resources as needed during development:
- Security and error handling standards
### Microsoft MCP Documentation (For Azure/Foundry)
-- [🔷 Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) - Microsoft-specific patterns including:
+- 🔷 Microsoft MCP Patterns - Microsoft-specific patterns including:
- Azure MCP Server architecture (48+ Azure services)
- C#/.NET command implementation patterns
- Remote MCP with Foundry Agent Service
@@ -270,24 +276,24 @@ Load these resources as needed during development:
### SDK Documentation (Load During Phase 1/2)
- **Python SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`
- **TypeScript SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`
-- **Microsoft MCP SDK**: See [Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) for C#/.NET
+- **Microsoft MCP SDK**: See Microsoft MCP Patterns for C#/.NET
### Language-Specific Implementation Guides (Load During Phase 2)
-- [🐍 Python Implementation Guide](./reference/python_mcp_server.md) - Complete Python/FastMCP guide with:
+- 🐍 Python Implementation Guide - Complete Python/FastMCP guide with:
- Server initialization patterns
- Pydantic model examples
- Tool registration with `@mcp.tool`
- Complete working examples
- Quality checklist
-- [⚡ TypeScript Implementation Guide](./reference/node_mcp_server.md) - Complete TypeScript guide with:
+- ⚡ TypeScript Implementation Guide - Complete TypeScript guide with:
- Project structure
- Zod schema patterns
- Tool registration with `server.registerTool`
- Complete working examples
- Quality checklist
-- [🔷 Microsoft MCP Patterns](./reference/microsoft_mcp_patterns.md) - Complete C#/.NET guide with:
+- 🔷 Microsoft MCP Patterns - Complete C#/.NET guide with:
- Command hierarchy (BaseCommand → GlobalCommand → SubscriptionCommand)
- Naming conventions (`{Resource}{Operation}Command`)
- Option handling with `.AsRequired()` / `.AsOptional()`
@@ -295,7 +301,7 @@ Load these resources as needed during development:
- Live test patterns with Bicep
### Evaluation Guide (Load During Phase 4)
-- [✅ Evaluation Guide](./reference/evaluation.md) - Complete evaluation creation guide with:
+- ✅ Evaluation Guide - Complete evaluation creation guide with:
- Question creation guidelines
- Answer verification strategies
- XML format specifications
diff --git a/web-app/public/skills/mcp-builder/SKILL.md b/web-app/public/skills/mcp-builder/SKILL.md
index 8a1a77a4..8b71a2ee 100644
--- a/web-app/public/skills/mcp-builder/SKILL.md
+++ b/web-app/public/skills/mcp-builder/SKILL.md
@@ -1,7 +1,9 @@
---
name: mcp-builder
-description: Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
+description: "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# MCP Server Development Guide
@@ -234,3 +236,6 @@ Load these resources as needed during development:
- XML format specifications
- Example questions and answers
- Running an evaluation with the provided scripts
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/memory-forensics/SKILL.md b/web-app/public/skills/memory-forensics/SKILL.md
index 9058793f..93b1e443 100644
--- a/web-app/public/skills/memory-forensics/SKILL.md
+++ b/web-app/public/skills/memory-forensics/SKILL.md
@@ -1,6 +1,8 @@
---
name: memory-forensics
-description: Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.
+description: "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden..."
+risk: unknown
+source: community
---
# Memory Forensics
diff --git a/web-app/public/skills/memory-safety-patterns/SKILL.md b/web-app/public/skills/memory-safety-patterns/SKILL.md
index 1e9a8ab2..c3db8333 100644
--- a/web-app/public/skills/memory-safety-patterns/SKILL.md
+++ b/web-app/public/skills/memory-safety-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: memory-safety-patterns
-description: Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
+description: "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory..."
+risk: unknown
+source: community
---
# Memory Safety Patterns
diff --git a/web-app/public/skills/memory-systems/SKILL.md b/web-app/public/skills/memory-systems/SKILL.md
index 48b96d57..a0369590 100644
--- a/web-app/public/skills/memory-systems/SKILL.md
+++ b/web-app/public/skills/memory-systems/SKILL.md
@@ -207,7 +207,7 @@ This skill builds on context-fundamentals. It connects to:
## References
Internal reference:
-- [Implementation Reference](./references/implementation.md) - Detailed implementation patterns
+- Implementation Reference - Detailed implementation patterns
Related skills in this collection:
- context-fundamentals - Context basics
diff --git a/web-app/public/skills/mermaid-expert/SKILL.md b/web-app/public/skills/mermaid-expert/SKILL.md
index d5ecaac8..424f298c 100644
--- a/web-app/public/skills/mermaid-expert/SKILL.md
+++ b/web-app/public/skills/mermaid-expert/SKILL.md
@@ -1,10 +1,12 @@
---
name: mermaid-expert
-description: Create Mermaid diagrams for flowcharts, sequences, ERDs, and
+description: "Create Mermaid diagrams for flowcharts, sequences, ERDs, and"
architectures. Masters syntax for all diagram types and styling. Use
PROACTIVELY for visual documentation, system diagrams, or process flows.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/metasploit-framework/SKILL.md b/web-app/public/skills/metasploit-framework/SKILL.md
index 2282770a..2b4f6c6f 100644
--- a/web-app/public/skills/metasploit-framework/SKILL.md
+++ b/web-app/public/skills/metasploit-framework/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Metasploit Framework
-description: This skill should be used when the user asks to "use Metasploit for penetration testing", "exploit vulnerabilities with msfconsole", "create payloads with msfvenom", "perform post-exploitation", "use auxiliary modules for scanning", or "develop custom exploits". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.
+name: metasploit-framework
+description: "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Metasploit Framework
@@ -476,3 +478,6 @@ exploit/multi/http/jenkins_script_console
| Exploit fails/no session | Run `check`; verify payload architecture; check firewall; try different payloads |
| Session dies immediately | Migrate to stable process; use stageless payload; check AV; use AutoRunScript |
| Payload detected by AV | Use encoding `-e x86/shikata_ga_nai -i 10`; use evasion modules; custom templates |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/micro-saas-launcher/SKILL.md b/web-app/public/skills/micro-saas-launcher/SKILL.md
index 581cac68..f7f64e9d 100644
--- a/web-app/public/skills/micro-saas-launcher/SKILL.md
+++ b/web-app/public/skills/micro-saas-launcher/SKILL.md
@@ -1,7 +1,8 @@
---
name: micro-saas-launcher
-description: "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp."
+description: "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Micro-SaaS Launcher
@@ -210,3 +211,6 @@ Your time has value.
## Related Skills
Works well with: `landing-page-design`, `backend`, `stripe`, `seo`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/microservices-patterns/SKILL.md b/web-app/public/skills/microservices-patterns/SKILL.md
index 548972b9..3d36059a 100644
--- a/web-app/public/skills/microservices-patterns/SKILL.md
+++ b/web-app/public/skills/microservices-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: microservices-patterns
-description: Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
+description: "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros..."
+risk: unknown
+source: community
---
# Microservices Patterns
diff --git a/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md b/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
index 76597d61..e79459a7 100644
--- a/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
+++ b/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
@@ -1,7 +1,9 @@
---
name: microsoft-azure-webjobs-extensions-authentication-events-dotnet
-description: |
+description: "|"
Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: "Authentication Events", "WebJobsAuthenticationEventsTrigger", "OnTokenIssuanceStart", "OnAttributeCollectionStart", "custom claims", "token enrichment", "Entra custom extension", "authentication extension".
+risk: unknown
+source: community
---
# Microsoft.Azure.WebJobs.Extensions.AuthenticationEvents (.NET)
@@ -438,3 +440,6 @@ public static WebJobsAuthenticationEventResponse Run(
| Token Issuance Events | https://learn.microsoft.com/entra/identity-platform/custom-extension-tokenissuancestart-setup |
| Attribute Collection Events | https://learn.microsoft.com/entra/identity-platform/custom-extension-attribute-collection |
| GitHub Source | https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/entra/Microsoft.Azure.WebJobs.Extensions.AuthenticationEvents |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/microsoft-teams-automation/SKILL.md b/web-app/public/skills/microsoft-teams-automation/SKILL.md
index 33d41493..82f8d158 100644
--- a/web-app/public/skills/microsoft-teams-automation/SKILL.md
+++ b/web-app/public/skills/microsoft-teams-automation/SKILL.md
@@ -3,6 +3,8 @@ name: microsoft-teams-automation
description: "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Microsoft Teams Automation via Rube MCP
@@ -209,3 +211,6 @@ Automate Microsoft Teams operations through Composio's Microsoft Teams toolkit v
| Search messages | MICROSOFT_TEAMS_SEARCH_MESSAGES | query |
| Get chat message | MICROSOFT_TEAMS_GET_CHAT_MESSAGE | chat_id, message_id |
| List joined teams | MICROSOFT_TEAMS_LIST_USER_JOINED_TEAMS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/minecraft-bukkit-pro/SKILL.md b/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
index 5f50784c..e52acd91 100644
--- a/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
+++ b/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
@@ -1,12 +1,14 @@
---
name: minecraft-bukkit-pro
-description: Master Minecraft server plugin development with Bukkit, Spigot, and
+description: "Master Minecraft server plugin development with Bukkit, Spigot, and"
Paper APIs. Specializes in event-driven architecture, command systems, world
manipulation, player management, and performance optimization. Use PROACTIVELY
for plugin architecture, gameplay mechanics, server-side features, or
cross-version compatibility.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/miro-automation/SKILL.md b/web-app/public/skills/miro-automation/SKILL.md
index 4bc14f2a..515c0144 100644
--- a/web-app/public/skills/miro-automation/SKILL.md
+++ b/web-app/public/skills/miro-automation/SKILL.md
@@ -3,6 +3,8 @@ name: miro-automation
description: "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Miro Automation via Rube MCP
@@ -203,3 +205,6 @@ Automate Miro whiteboard operations through Composio's Miro toolkit via Rube MCP
| Share board | MIRO_SHARE_BOARD | board_id, emails, role |
| Get members | MIRO_GET_BOARD_MEMBERS | board_id |
| Get connectors | MIRO_GET_CONNECTORS2 | board_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/mixpanel-automation/SKILL.md b/web-app/public/skills/mixpanel-automation/SKILL.md
index 4cdc5860..4d06aa3b 100644
--- a/web-app/public/skills/mixpanel-automation/SKILL.md
+++ b/web-app/public/skills/mixpanel-automation/SKILL.md
@@ -3,6 +3,8 @@ name: mixpanel-automation
description: "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Mixpanel Automation via Rube MCP
@@ -222,3 +224,6 @@ Used in `where` and `on` parameters:
| List cohorts | MIXPANEL_COHORTS_LIST | (none) |
| JQL query | MIXPANEL_JQL_QUERY | script |
| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ml-engineer/SKILL.md b/web-app/public/skills/ml-engineer/SKILL.md
index 94718289..f34b1020 100644
--- a/web-app/public/skills/ml-engineer/SKILL.md
+++ b/web-app/public/skills/ml-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: ml-engineer
-description: Build production ML systems with PyTorch 2.x, TensorFlow, and
+description: "Build production ML systems with PyTorch 2.x, TensorFlow, and"
modern ML frameworks. Implements model serving, feature engineering, A/B
testing, and monitoring. Use PROACTIVELY for ML model deployment, inference
optimization, or production ML infrastructure.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/ml-pipeline-workflow/SKILL.md b/web-app/public/skills/ml-pipeline-workflow/SKILL.md
index 48bd22ac..d368e13a 100644
--- a/web-app/public/skills/ml-pipeline-workflow/SKILL.md
+++ b/web-app/public/skills/ml-pipeline-workflow/SKILL.md
@@ -1,6 +1,8 @@
---
name: ml-pipeline-workflow
-description: Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
+description: "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod..."
+risk: unknown
+source: community
---
# ML Pipeline Workflow
diff --git a/web-app/public/skills/mlops-engineer/SKILL.md b/web-app/public/skills/mlops-engineer/SKILL.md
index 61842820..97a59c63 100644
--- a/web-app/public/skills/mlops-engineer/SKILL.md
+++ b/web-app/public/skills/mlops-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: mlops-engineer
-description: Build comprehensive ML pipelines, experiment tracking, and model
+description: "Build comprehensive ML pipelines, experiment tracking, and model"
registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated
training, deployment, and monitoring across cloud platforms. Use PROACTIVELY
for ML infrastructure, experiment management, or pipeline automation.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/mobile-design/SKILL.md b/web-app/public/skills/mobile-design/SKILL.md
index f4109e76..4fc79fbb 100644
--- a/web-app/public/skills/mobile-design/SKILL.md
+++ b/web-app/public/skills/mobile-design/SKILL.md
@@ -1,7 +1,9 @@
---
name: mobile-design
-description: Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.
+description: "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr..."
allowed-tools: Read, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Mobile Design System
@@ -282,3 +284,6 @@ No debate without justification.
> **Design for that reality, or your app will fail quietly.**
---
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/mobile-developer/SKILL.md b/web-app/public/skills/mobile-developer/SKILL.md
index e9d4a025..a347fb69 100644
--- a/web-app/public/skills/mobile-developer/SKILL.md
+++ b/web-app/public/skills/mobile-developer/SKILL.md
@@ -1,11 +1,13 @@
---
name: mobile-developer
-description: Develop React Native, Flutter, or native mobile apps with modern
+description: "Develop React Native, Flutter, or native mobile apps with modern"
architecture patterns. Masters cross-platform development, native
integrations, offline sync, and app store optimization. Use PROACTIVELY for
mobile features, cross-platform code, or app optimization.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/mobile-security-coder/SKILL.md b/web-app/public/skills/mobile-security-coder/SKILL.md
index c7bda479..77e20219 100644
--- a/web-app/public/skills/mobile-security-coder/SKILL.md
+++ b/web-app/public/skills/mobile-security-coder/SKILL.md
@@ -1,11 +1,13 @@
---
name: mobile-security-coder
-description: Expert in secure mobile coding practices specializing in input
+description: "Expert in secure mobile coding practices specializing in input"
validation, WebView security, and mobile-specific security patterns. Use
PROACTIVELY for mobile security implementations or mobile security code
reviews.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/modern-javascript-patterns/SKILL.md b/web-app/public/skills/modern-javascript-patterns/SKILL.md
index cd229d2b..07501d58 100644
--- a/web-app/public/skills/modern-javascript-patterns/SKILL.md
+++ b/web-app/public/skills/modern-javascript-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: modern-javascript-patterns
-description: Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.
+description: "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici..."
+risk: unknown
+source: community
---
# Modern JavaScript Patterns
diff --git a/web-app/public/skills/monday-automation/SKILL.md b/web-app/public/skills/monday-automation/SKILL.md
index 4d15a630..97706437 100644
--- a/web-app/public/skills/monday-automation/SKILL.md
+++ b/web-app/public/skills/monday-automation/SKILL.md
@@ -3,6 +3,8 @@ name: monday-automation
description: "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Monday.com Automation via Rube MCP
@@ -231,3 +233,6 @@ Different column types require different value formats:
| List subitems | `MONDAY_LIST_SUBITEMS_BY_PARENT` | `parent_item_ids` |
| Add comment/update | `MONDAY_CREATE_UPDATE` | `item_id`, `body` |
| Raw GraphQL mutation | `MONDAY_CREATE_OBJECT` | `query`, `variables` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/monorepo-architect/SKILL.md b/web-app/public/skills/monorepo-architect/SKILL.md
index 04e3830e..49f7141e 100644
--- a/web-app/public/skills/monorepo-architect/SKILL.md
+++ b/web-app/public/skills/monorepo-architect/SKILL.md
@@ -1,6 +1,8 @@
---
name: monorepo-architect
description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,"
+risk: unknown
+source: community
---
# Monorepo Architect
diff --git a/web-app/public/skills/monorepo-management/SKILL.md b/web-app/public/skills/monorepo-management/SKILL.md
index 8892da39..91215e33 100644
--- a/web-app/public/skills/monorepo-management/SKILL.md
+++ b/web-app/public/skills/monorepo-management/SKILL.md
@@ -1,6 +1,8 @@
---
name: monorepo-management
-description: Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
+description: "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor..."
+risk: unknown
+source: community
---
# Monorepo Management
diff --git a/web-app/public/skills/moodle-external-api-development/SKILL.md b/web-app/public/skills/moodle-external-api-development/SKILL.md
index c5a9a09f..ac6359e4 100644
--- a/web-app/public/skills/moodle-external-api-development/SKILL.md
+++ b/web-app/public/skills/moodle-external-api-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: moodle-external-api-development
-description: Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.
+description: "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va..."
+risk: unknown
+source: community
---
# Moodle External API Development
diff --git a/web-app/public/skills/mtls-configuration/SKILL.md b/web-app/public/skills/mtls-configuration/SKILL.md
index f4d665ae..72cef8b1 100644
--- a/web-app/public/skills/mtls-configuration/SKILL.md
+++ b/web-app/public/skills/mtls-configuration/SKILL.md
@@ -1,6 +1,8 @@
---
name: mtls-configuration
-description: Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.
+description: "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication."
+risk: unknown
+source: community
---
# mTLS Configuration
diff --git a/web-app/public/skills/multi-agent-brainstorming/SKILL.md b/web-app/public/skills/multi-agent-brainstorming/SKILL.md
index acda9e98..bb4b173b 100644
--- a/web-app/public/skills/multi-agent-brainstorming/SKILL.md
+++ b/web-app/public/skills/multi-agent-brainstorming/SKILL.md
@@ -1,11 +1,13 @@
---
name: multi-agent-brainstorming
-description: >
+description:
Use this skill when a design or idea requires higher confidence,
risk reduction, or formal review. This skill orchestrates a
structured, sequential multi-agent design review where each agent
has a strict, non-overlapping role. It prevents blind spots,
false confidence, and premature convergence.
+risk: unknown
+source: community
---
# Multi-Agent Brainstorming (Structured Design Review)
@@ -254,3 +256,6 @@ This skill exists to answer one question with confidence:
If the answer is unclear, **do not exit this skill**.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/multi-agent-patterns/SKILL.md b/web-app/public/skills/multi-agent-patterns/SKILL.md
index 2d78c7fa..fab3cdb0 100644
--- a/web-app/public/skills/multi-agent-patterns/SKILL.md
+++ b/web-app/public/skills/multi-agent-patterns/SKILL.md
@@ -239,7 +239,7 @@ This skill builds on context-fundamentals and context-degradation. It connects t
## References
Internal reference:
-- [Frameworks Reference](./references/frameworks.md) - Detailed framework implementation patterns
+- Frameworks Reference - Detailed framework implementation patterns
Related skills in this collection:
- context-fundamentals - Context basics
diff --git a/web-app/public/skills/multi-cloud-architecture/SKILL.md b/web-app/public/skills/multi-cloud-architecture/SKILL.md
index 97b0cbeb..0543f6d3 100644
--- a/web-app/public/skills/multi-cloud-architecture/SKILL.md
+++ b/web-app/public/skills/multi-cloud-architecture/SKILL.md
@@ -1,6 +1,8 @@
---
name: multi-cloud-architecture
-description: Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.
+description: "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin..."
+risk: unknown
+source: community
---
# Multi-Cloud Architecture
diff --git a/web-app/public/skills/multi-platform-apps-multi-platform/SKILL.md b/web-app/public/skills/multi-platform-apps-multi-platform/SKILL.md
index ca29bfce..aff23e68 100644
--- a/web-app/public/skills/multi-platform-apps-multi-platform/SKILL.md
+++ b/web-app/public/skills/multi-platform-apps-multi-platform/SKILL.md
@@ -1,6 +1,8 @@
---
name: multi-platform-apps-multi-platform
description: "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies."
+risk: unknown
+source: community
---
# Multi-Platform Feature Development Workflow
diff --git a/web-app/public/skills/n8n-code-python/SKILL.md b/web-app/public/skills/n8n-code-python/SKILL.md
index 4a9c2ee1..14c15e8c 100644
--- a/web-app/public/skills/n8n-code-python/SKILL.md
+++ b/web-app/public/skills/n8n-code-python/SKILL.md
@@ -233,7 +233,7 @@ return [{
}]
```
-**See**: [DATA_ACCESS.md](DATA_ACCESS.md) for comprehensive guide
+**See**: DATA_ACCESS.md for comprehensive guide
---
@@ -257,7 +257,7 @@ name = webhook_data.get("name")
**Why**: Webhook node wraps all request data under `body` property. This includes POST data, query parameters, and JSON payloads.
-**See**: [DATA_ACCESS.md](DATA_ACCESS.md) for full webhook structure details
+**See**: DATA_ACCESS.md for full webhook structure details
---
@@ -320,7 +320,7 @@ return [{"data": value}] # Should be {"json": value}
**Why it matters**: Next nodes expect list format. Incorrect format causes workflow execution to fail.
-**See**: [ERROR_PATTERNS.md](ERROR_PATTERNS.md) #2 for detailed error solutions
+**See**: ERROR_PATTERNS.md #2 for detailed error solutions
---
@@ -370,7 +370,7 @@ import statistics # ✅ Statistical functions
- ✅ Use **HTTP Request node** + **HTML Extract node**
- ✅ Or switch to **JavaScript** with regex/string methods
-**See**: [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) for complete reference
+**See**: STANDARD_LIBRARY.md for complete reference
---
@@ -490,7 +490,7 @@ else:
return [{"json": {"error": "No values found"}}]
```
-**See**: [COMMON_PATTERNS.md](COMMON_PATTERNS.md) for 10 detailed Python patterns
+**See**: COMMON_PATTERNS.md for 10 detailed Python patterns
---
@@ -554,7 +554,7 @@ email = _json["body"]["email"]
email = _json.get("body", {}).get("email", "no-email")
```
-**See**: [ERROR_PATTERNS.md](ERROR_PATTERNS.md) for comprehensive error guide
+**See**: ERROR_PATTERNS.md for comprehensive error guide
---
@@ -598,7 +598,7 @@ from statistics import mean, median, stdev
average = mean([1, 2, 3, 4, 5])
```
-**See**: [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) for complete reference
+**See**: STANDARD_LIBRARY.md for complete reference
---
@@ -736,10 +736,10 @@ Before deploying Python Code nodes, verify:
## Additional Resources
### Related Files
-- [DATA_ACCESS.md](DATA_ACCESS.md) - Comprehensive Python data access patterns
-- [COMMON_PATTERNS.md](COMMON_PATTERNS.md) - 10 Python patterns for n8n
-- [ERROR_PATTERNS.md](ERROR_PATTERNS.md) - Top 5 errors and solutions
-- [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) - Complete standard library reference
+- DATA_ACCESS.md - Comprehensive Python data access patterns
+- COMMON_PATTERNS.md - 10 Python patterns for n8n
+- ERROR_PATTERNS.md - Top 5 errors and solutions
+- STANDARD_LIBRARY.md - Complete standard library reference
### n8n Documentation
- Code Node Guide: https://docs.n8n.io/code/code-node/
diff --git a/web-app/public/skills/n8n-mcp-tools-expert/SKILL.md b/web-app/public/skills/n8n-mcp-tools-expert/SKILL.md
index 62c4619d..fdd7bc20 100644
--- a/web-app/public/skills/n8n-mcp-tools-expert/SKILL.md
+++ b/web-app/public/skills/n8n-mcp-tools-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: n8n-mcp-tools-expert
-description: "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns."
+description: "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele..."
source: "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert"
risk: safe
---
@@ -25,9 +25,9 @@ Use this skill when:
n8n-mcp provides tools organized into categories:
-1. **Node Discovery** → [SEARCH_GUIDE.md](SEARCH_GUIDE.md)
-2. **Configuration Validation** → [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md)
-3. **Workflow Management** → [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md)
+1. **Node Discovery** → SEARCH_GUIDE.md
+2. **Configuration Validation** → VALIDATION_GUIDE.md
+3. **Workflow Management** → WORKFLOW_GUIDE.md
4. **Template Library** - Search and deploy 2,700+ real workflows
5. **Documentation & Guides** - Tool docs, AI agent guide, Code node guides
@@ -375,13 +375,13 @@ await n8n_update_partial_workflow({
## Detailed Guides
### Node Discovery Tools
-See [SEARCH_GUIDE.md](SEARCH_GUIDE.md) for:
+See SEARCH_GUIDE.md for:
- search_nodes
- get_node with detail levels (minimal, standard, full)
- get_node modes (info, docs, search_properties, versions)
### Validation Tools
-See [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) for:
+See VALIDATION_GUIDE.md for:
- Validation profiles explained
- validate_node with modes (minimal, full)
- validate_workflow complete structure
@@ -389,7 +389,7 @@ See [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) for:
- Handling validation errors
### Workflow Management
-See [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md) for:
+See WORKFLOW_GUIDE.md for:
- n8n_create_workflow
- n8n_update_partial_workflow (17 operation types!)
- Smart parameters (branch, case)
@@ -639,9 +639,9 @@ validate_node({nodeType: "nodes-base.webhook", config: {}, mode: "minimal"})
7. activateWorkflow → go live!
For details, see:
-- [SEARCH_GUIDE.md](SEARCH_GUIDE.md) - Node discovery
-- [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) - Configuration validation
-- [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md) - Workflow management
+- SEARCH_GUIDE.md - Node discovery
+- VALIDATION_GUIDE.md - Configuration validation
+- WORKFLOW_GUIDE.md - Workflow management
---
diff --git a/web-app/public/skills/n8n-node-configuration/SKILL.md b/web-app/public/skills/n8n-node-configuration/SKILL.md
index 0bfc1d3a..1b605cba 100644
--- a/web-app/public/skills/n8n-node-configuration/SKILL.md
+++ b/web-app/public/skills/n8n-node-configuration/SKILL.md
@@ -1,6 +1,6 @@
---
name: n8n-node-configuration
-description: "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type."
+description: "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo..."
source: "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration"
risk: safe
---
@@ -768,8 +768,8 @@ get_node({
For comprehensive guides on specific topics:
-- **[DEPENDENCIES.md](DEPENDENCIES.md)** - Deep dive into property dependencies and displayOptions
-- **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md)** - Common configuration patterns by node type
+- **DEPENDENCIES.md** - Deep dive into property dependencies and displayOptions
+- **OPERATION_PATTERNS.md** - Common configuration patterns by node type
---
diff --git a/web-app/public/skills/neon-postgres/SKILL.md b/web-app/public/skills/neon-postgres/SKILL.md
index a07eb608..732c72e0 100644
--- a/web-app/public/skills/neon-postgres/SKILL.md
+++ b/web-app/public/skills/neon-postgres/SKILL.md
@@ -1,7 +1,8 @@
---
name: neon-postgres
-description: "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless."
+description: "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Neon Postgres
@@ -54,3 +55,6 @@ Use pooled endpoint for application, direct for migrations.
| Issue | low | See docs |
| Issue | medium | See docs |
| Issue | high | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/nerdzao-elite-gemini-high/SKILL.md b/web-app/public/skills/nerdzao-elite-gemini-high/SKILL.md
new file mode 100644
index 00000000..e05013b6
--- /dev/null
+++ b/web-app/public/skills/nerdzao-elite-gemini-high/SKILL.md
@@ -0,0 +1,50 @@
+---
+name: nerdzao-elite-gemini-high
+description: "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade máxima e eficiência de tokens."
+risk: "safe"
+source: "community"
+---
+
+# @nerdzao-elite-gemini-high
+
+Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior, operando no modo Gemini 3.1 Pro (High).
+
+Ative automaticamente este workflow completo em TODA tarefa:
+
+1. **Planejamento ultra-rápido**
+ @concise-planning + @brainstorming
+
+2. **Arquitetura sólida**
+ @senior-architect + @architecture
+
+3. **Implementação TDD**
+ @test-driven-development + @testing-patterns
+
+4. **Código produção-grade**
+ @refactor-clean-code + @clean-code
+
+5. **Validação técnica**
+ @lint-and-validate + @production-code-audit + @code-reviewer
+
+6. **Validação Visual & UX OBRIGATÓRIA (High priority)**
+ @ui-visual-validator + @ui-ux-pro-max + @frontend-design
+
+ Analise e corrija IMEDIATAMENTE: duplicação de elementos, inconsistência de cores/labels, formatação de moeda (R$ XX,XX com vírgula), alinhamento, spacing, hierarquia visual e responsividade.
+ Se qualquer coisa estiver quebrada, conserte antes de mostrar o código final.
+
+7. **Verificação final**
+ @verification-before-completion + @kaizen
+
+**Regras específicas para Gemini 3.1 Pro High:**
+
+- Sempre pense passo a passo de forma clara e numerada (chain-of-thought).
+- Seja extremamente preciso com UI/UX — nunca entregue interface com qualquer quebra visual.
+- Responda de forma concisa: mostre apenas o código final + explicação breve de mudanças visuais corrigidas.
+- Nunca adicione comentários ou texto longo desnecessário.
+- Priorize: pixel-perfect + código limpo + performance + segurança.
+
+Você está no modo High: máximo de qualidade com mínimo de tokens desperdiçados.
+
+## When to Use
+
+Use when you need maximum quality output with Gemini 3.1 Pro High, pixel-perfect UI, and token-efficient workflow.
diff --git a/web-app/public/skills/nerdzao-elite/SKILL.md b/web-app/public/skills/nerdzao-elite/SKILL.md
new file mode 100644
index 00000000..b3b02d28
--- /dev/null
+++ b/web-app/public/skills/nerdzao-elite/SKILL.md
@@ -0,0 +1,31 @@
+---
+name: nerdzao-elite
+description: "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation."
+risk: safe
+source: community
+---
+
+# @nerdzao-elite
+
+Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior.
+
+Ative automaticamente TODAS as skills abaixo em toda tarefa:
+
+@concise-planning @brainstorming @senior-architect @architecture @test-driven-development @testing-patterns @refactor-clean-code @clean-code @lint-and-validate @ui-visual-validator @ui-ux-pro-max @frontend-design @web-design-guidelines @production-code-audit @code-reviewer @systematic-debugging @error-handling-patterns @kaizen @verification-before-completion
+
+Workflow obrigatório (sempre na ordem):
+
+1. Planejamento (@concise-planning + @brainstorming)
+2. Arquitetura sólida
+3. Implementação com TDD completo
+4. Código limpo
+5. Validação técnica
+6. Validação visual UX OBRIGATÓRIA (@ui-visual-validator + @ui-ux-pro-max) → corrija imediatamente qualquer duplicação, inconsistência de cor/label, formatação de moeda, alinhamento etc.
+7. Revisão de produção
+8. Verificação final
+
+Nunca entregue UI quebrada. Priorize sempre pixel-perfect + produção-grade.
+
+## When to Use
+
+Use when you need a full senior engineering workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation in Portuguese (Brazil).
diff --git a/web-app/public/skills/nestjs-expert/SKILL.md b/web-app/public/skills/nestjs-expert/SKILL.md
index e224f672..ee09d1c2 100644
--- a/web-app/public/skills/nestjs-expert/SKILL.md
+++ b/web-app/public/skills/nestjs-expert/SKILL.md
@@ -1,9 +1,11 @@
---
name: nestjs-expert
-description: Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
+description: "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth..."
category: framework
displayName: Nest.js Framework Expert
color: red
+risk: unknown
+source: community
---
# Nest.js Expert
@@ -549,4 +551,7 @@ export class ConfigModule {
- ✅ Code follows established project conventions
- ✅ Proper error handling implemented
- ✅ Security best practices applied
-- ✅ Documentation updated for API changes
\ No newline at end of file
+- ✅ Documentation updated for API changes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/network-101/SKILL.md b/web-app/public/skills/network-101/SKILL.md
index 6db8ec59..5af21a39 100644
--- a/web-app/public/skills/network-101/SKILL.md
+++ b/web-app/public/skills/network-101/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Network 101
-description: This skill should be used when the user asks to "set up a web server", "configure HTTP or HTTPS", "perform SNMP enumeration", "configure SMB shares", "test network services", or needs guidance on configuring and testing network services for penetration testing labs.
+name: network-101
+description: "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Network 101
@@ -340,3 +342,6 @@ smbclient //localhost/anonymous -N
| SMB access denied | Verify share permissions and user credentials |
| HTTPS certificate error | Accept self-signed cert or add to trusted store |
| Cannot connect remotely | Bind service to 0.0.0.0 instead of localhost |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/network-engineer/SKILL.md b/web-app/public/skills/network-engineer/SKILL.md
index 216a22f1..3fc439d3 100644
--- a/web-app/public/skills/network-engineer/SKILL.md
+++ b/web-app/public/skills/network-engineer/SKILL.md
@@ -1,6 +1,6 @@
---
name: network-engineer
-description: Expert network engineer specializing in modern cloud networking,
+description: "Expert network engineer specializing in modern cloud networking,"
security architectures, and performance optimization. Masters multi-cloud
connectivity, service mesh, zero-trust networking, SSL/TLS, global load
balancing, and advanced troubleshooting. Handles CDN optimization, network
@@ -8,6 +8,8 @@ description: Expert network engineer specializing in modern cloud networking,
issues, or performance optimization.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/nextjs-app-router-patterns/SKILL.md b/web-app/public/skills/nextjs-app-router-patterns/SKILL.md
index 46af54ae..a8d4887b 100644
--- a/web-app/public/skills/nextjs-app-router-patterns/SKILL.md
+++ b/web-app/public/skills/nextjs-app-router-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: nextjs-app-router-patterns
-description: Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
+description: "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve..."
+risk: unknown
+source: community
---
# Next.js App Router Patterns
diff --git a/web-app/public/skills/nextjs-best-practices/SKILL.md b/web-app/public/skills/nextjs-best-practices/SKILL.md
index 044a3bb6..f3e1ee19 100644
--- a/web-app/public/skills/nextjs-best-practices/SKILL.md
+++ b/web-app/public/skills/nextjs-best-practices/SKILL.md
@@ -1,7 +1,9 @@
---
name: nextjs-best-practices
-description: Next.js App Router principles. Server Components, data fetching, routing patterns.
+description: "Next.js App Router principles. Server Components, data fetching, routing patterns."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Next.js Best Practices
@@ -201,3 +203,6 @@ app/
---
> **Remember:** Server Components are the default for a reason. Start there, add client only when needed.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/nextjs-supabase-auth/SKILL.md b/web-app/public/skills/nextjs-supabase-auth/SKILL.md
index 4d5211dd..da3db9a4 100644
--- a/web-app/public/skills/nextjs-supabase-auth/SKILL.md
+++ b/web-app/public/skills/nextjs-supabase-auth/SKILL.md
@@ -2,6 +2,7 @@
name: nextjs-supabase-auth
description: "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Next.js + Supabase Auth
@@ -54,3 +55,6 @@ Handle OAuth callback and exchange code for session
## Related Skills
Works well with: `nextjs-app-router`, `supabase-backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/nft-standards/SKILL.md b/web-app/public/skills/nft-standards/SKILL.md
index f57aa864..0dab323b 100644
--- a/web-app/public/skills/nft-standards/SKILL.md
+++ b/web-app/public/skills/nft-standards/SKILL.md
@@ -1,6 +1,8 @@
---
name: nft-standards
-description: Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
+description: "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi..."
+risk: unknown
+source: community
---
# NFT Standards
diff --git a/web-app/public/skills/nodejs-backend-patterns/SKILL.md b/web-app/public/skills/nodejs-backend-patterns/SKILL.md
index 8cc21b38..a016a653 100644
--- a/web-app/public/skills/nodejs-backend-patterns/SKILL.md
+++ b/web-app/public/skills/nodejs-backend-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: nodejs-backend-patterns
-description: Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
+description: "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when..."
+risk: unknown
+source: community
---
# Node.js Backend Patterns
diff --git a/web-app/public/skills/nodejs-best-practices/SKILL.md b/web-app/public/skills/nodejs-best-practices/SKILL.md
index f5abcacc..8f0969ce 100644
--- a/web-app/public/skills/nodejs-best-practices/SKILL.md
+++ b/web-app/public/skills/nodejs-best-practices/SKILL.md
@@ -1,7 +1,9 @@
---
name: nodejs-best-practices
-description: Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
+description: "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Node.js Best Practices
@@ -9,6 +11,10 @@ allowed-tools: Read, Write, Edit, Glob, Grep
> Principles and decision-making for Node.js development in 2025.
> **Learn to THINK, not memorize code patterns.**
+## When to Use
+
+Use this skill when making Node.js architecture decisions, choosing frameworks, designing async patterns, or applying security and deployment best practices.
+
---
## ⚠️ How to Use This Skill
diff --git a/web-app/public/skills/nosql-expert/SKILL.md b/web-app/public/skills/nosql-expert/SKILL.md
index 72b3ca77..0a0b2d86 100644
--- a/web-app/public/skills/nosql-expert/SKILL.md
+++ b/web-app/public/skills/nosql-expert/SKILL.md
@@ -1,6 +1,8 @@
---
name: nosql-expert
description: "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems."
+risk: unknown
+source: community
---
# NoSQL Expert Patterns (Cassandra & DynamoDB)
diff --git a/web-app/public/skills/notebooklm/SKILL.md b/web-app/public/skills/notebooklm/SKILL.md
index 2be7e161..0b3e824a 100644
--- a/web-app/public/skills/notebooklm/SKILL.md
+++ b/web-app/public/skills/notebooklm/SKILL.md
@@ -1,6 +1,8 @@
---
name: notebooklm
-description: Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
+description: "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth...."
+risk: unknown
+source: community
---
# NotebookLM Research Assistant Skill
diff --git a/web-app/public/skills/notion-automation/SKILL.md b/web-app/public/skills/notion-automation/SKILL.md
index b5236cc5..fb7654a1 100644
--- a/web-app/public/skills/notion-automation/SKILL.md
+++ b/web-app/public/skills/notion-automation/SKILL.md
@@ -3,6 +3,8 @@ name: notion-automation
description: "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Notion Automation via Rube MCP
@@ -213,3 +215,6 @@ Automate Notion operations through Composio's Notion toolkit via Rube MCP.
| List users | NOTION_LIST_USERS | (none) |
| Create comment | NOTION_CREATE_COMMENT | page_id, rich_text |
| List comments | NOTION_FETCH_COMMENTS | page_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/notion-template-business/SKILL.md b/web-app/public/skills/notion-template-business/SKILL.md
index 74e25db6..50d44077 100644
--- a/web-app/public/skills/notion-template-business/SKILL.md
+++ b/web-app/public/skills/notion-template-business/SKILL.md
@@ -1,7 +1,8 @@
---
name: notion-template-business
-description: "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad."
+description: "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Notion Template Business
@@ -214,3 +215,6 @@ Email/chat for premium.
## Related Skills
Works well with: `micro-saas-launcher`, `copywriting`, `landing-page-design`, `seo`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/nx-workspace-patterns/SKILL.md b/web-app/public/skills/nx-workspace-patterns/SKILL.md
index 1ccb841c..a3ef1ef8 100644
--- a/web-app/public/skills/nx-workspace-patterns/SKILL.md
+++ b/web-app/public/skills/nx-workspace-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: nx-workspace-patterns
-description: Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
+description: "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands."
+risk: unknown
+source: community
---
# Nx Workspace Patterns
diff --git a/web-app/public/skills/observability-engineer/SKILL.md b/web-app/public/skills/observability-engineer/SKILL.md
index 7d1f6d9e..6246773f 100644
--- a/web-app/public/skills/observability-engineer/SKILL.md
+++ b/web-app/public/skills/observability-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: observability-engineer
-description: Build production-ready monitoring, logging, and tracing systems.
+description: "Build production-ready monitoring, logging, and tracing systems."
Implements comprehensive observability strategies, SLI/SLO management, and
incident response workflows. Use PROACTIVELY for monitoring infrastructure,
performance optimization, or production reliability.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.
diff --git a/web-app/public/skills/observability-monitoring-monitor-setup/SKILL.md b/web-app/public/skills/observability-monitoring-monitor-setup/SKILL.md
index 9375ef3a..63d3d6bd 100644
--- a/web-app/public/skills/observability-monitoring-monitor-setup/SKILL.md
+++ b/web-app/public/skills/observability-monitoring-monitor-setup/SKILL.md
@@ -1,6 +1,8 @@
---
name: observability-monitoring-monitor-setup
description: "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da"
+risk: unknown
+source: community
---
# Monitoring and Observability Setup
diff --git a/web-app/public/skills/observability-monitoring-slo-implement/SKILL.md b/web-app/public/skills/observability-monitoring-slo-implement/SKILL.md
index 0513fb98..69e01b95 100644
--- a/web-app/public/skills/observability-monitoring-slo-implement/SKILL.md
+++ b/web-app/public/skills/observability-monitoring-slo-implement/SKILL.md
@@ -1,6 +1,8 @@
---
name: observability-monitoring-slo-implement
-description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity."
+description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba..."
+risk: unknown
+source: community
---
# SLO Implementation Guide
diff --git a/web-app/public/skills/observe-whatsapp/SKILL.md b/web-app/public/skills/observe-whatsapp/SKILL.md
index 5b4160a6..bb0faea6 100644
--- a/web-app/public/skills/observe-whatsapp/SKILL.md
+++ b/web-app/public/skills/observe-whatsapp/SKILL.md
@@ -1,6 +1,6 @@
---
name: observe-whatsapp
-description: "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message failures, or webhook delivery problems."
+description: "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f..."
source: "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp"
risk: safe
---
@@ -85,9 +85,9 @@ node scripts/openapi-explore.mjs --spec platform schema WebhookDelivery
## References
-- [references/message-debugging-reference.md](references/message-debugging-reference.md) - Message debugging guide
-- [references/triage-reference.md](references/triage-reference.md) - Error triage guide
-- [references/health-reference.md](references/health-reference.md) - Health check guide
+- references/message-debugging-reference.md - Message debugging guide
+- references/triage-reference.md - Error triage guide
+- references/health-reference.md - Health check guide
## Related skills
diff --git a/web-app/public/skills/obsidian-clipper-template-creator/SKILL.md b/web-app/public/skills/obsidian-clipper-template-creator/SKILL.md
index 95851f52..ed9e40da 100644
--- a/web-app/public/skills/obsidian-clipper-template-creator/SKILL.md
+++ b/web-app/public/skills/obsidian-clipper-template-creator/SKILL.md
@@ -1,6 +1,8 @@
---
name: obsidian-clipper-template-creator
-description: Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
+description: "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content."
+risk: unknown
+source: community
---
# Obsidian Web Clipper Template Creator
@@ -62,3 +64,6 @@ This skill helps you create importable JSON templates for the Obsidian Web Clipp
## Examples
See [assets/](assets/) for JSON examples.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/office-productivity/SKILL.md b/web-app/public/skills/office-productivity/SKILL.md
new file mode 100644
index 00000000..c67111a8
--- /dev/null
+++ b/web-app/public/skills/office-productivity/SKILL.md
@@ -0,0 +1,219 @@
+---
+name: office-productivity
+description: "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats."
+source: personal
+risk: safe
+domain: office-productivity
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Office Productivity Workflow Bundle
+
+## Overview
+
+Comprehensive office productivity workflow for document creation, spreadsheet automation, presentation generation, and format conversion using LibreOffice and Microsoft Office tools.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating office documents programmatically
+- Automating document workflows
+- Converting between document formats
+- Generating reports
+- Creating presentations from data
+- Processing spreadsheets
+
+## Workflow Phases
+
+### Phase 1: Document Creation
+
+#### Skills to Invoke
+- `libreoffice-writer` - LibreOffice Writer
+- `docx-official` - Microsoft Word
+- `pdf-official` - PDF handling
+
+#### Actions
+1. Design document template
+2. Create document structure
+3. Add content programmatically
+4. Apply formatting
+5. Export to required formats
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-writer to create ODT documents
+```
+
+```
+Use @docx-official to create Word documents
+```
+
+### Phase 2: Spreadsheet Automation
+
+#### Skills to Invoke
+- `libreoffice-calc` - LibreOffice Calc
+- `xlsx-official` - Excel spreadsheets
+- `googlesheets-automation` - Google Sheets
+
+#### Actions
+1. Design spreadsheet structure
+2. Create formulas
+3. Import data
+4. Generate charts
+5. Export reports
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-calc to create ODS spreadsheets
+```
+
+```
+Use @xlsx-official to create Excel reports
+```
+
+### Phase 3: Presentation Generation
+
+#### Skills to Invoke
+- `libreoffice-impress` - LibreOffice Impress
+- `pptx-official` - PowerPoint
+- `frontend-slides` - HTML slides
+- `nanobanana-ppt-skills` - AI PPT generation
+
+#### Actions
+1. Design slide template
+2. Generate slides from data
+3. Add charts and graphics
+4. Apply animations
+5. Export presentations
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-impress to create ODP presentations
+```
+
+```
+Use @pptx-official to create PowerPoint presentations
+```
+
+```
+Use @frontend-slides to create HTML presentations
+```
+
+### Phase 4: Format Conversion
+
+#### Skills to Invoke
+- `libreoffice-writer` - Document conversion
+- `libreoffice-calc` - Spreadsheet conversion
+- `pdf-official` - PDF conversion
+
+#### Actions
+1. Identify source format
+2. Choose target format
+3. Perform conversion
+4. Verify quality
+5. Batch process files
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-writer to convert documents
+```
+
+### Phase 5: Document Automation
+
+#### Skills to Invoke
+- `libreoffice-writer` - Mail merge
+- `workflow-automation` - Workflow automation
+- `file-organizer` - File organization
+
+#### Actions
+1. Design automation workflow
+2. Create templates
+3. Set up data sources
+4. Generate documents
+5. Distribute outputs
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-writer to perform mail merge
+```
+
+```
+Use @workflow-automation to automate document workflows
+```
+
+### Phase 6: Graphics and Diagrams
+
+#### Skills to Invoke
+- `libreoffice-draw` - Vector graphics
+- `canvas-design` - Canvas design
+- `mermaid-expert` - Diagram generation
+
+#### Actions
+1. Design graphics
+2. Create diagrams
+3. Generate charts
+4. Export images
+5. Integrate with documents
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-draw to create vector graphics
+```
+
+```
+Use @mermaid-expert to create diagrams
+```
+
+### Phase 7: Database Integration
+
+#### Skills to Invoke
+- `libreoffice-base` - LibreOffice Base
+- `database-architect` - Database design
+
+#### Actions
+1. Connect to data sources
+2. Create forms
+3. Design reports
+4. Automate queries
+5. Generate output
+
+#### Copy-Paste Prompts
+```
+Use @libreoffice-base to create database reports
+```
+
+## Office Application Workflows
+
+### LibreOffice
+```
+Skills: libreoffice-writer, libreoffice-calc, libreoffice-impress, libreoffice-draw, libreoffice-base
+Formats: ODT, ODS, ODP, ODG, ODB
+```
+
+### Microsoft Office
+```
+Skills: docx-official, xlsx-official, pptx-official
+Formats: DOCX, XLSX, PPTX
+```
+
+### Google Workspace
+```
+Skills: googlesheets-automation, google-drive-automation, gmail-automation
+Formats: Google Docs, Sheets, Slides
+```
+
+## Quality Gates
+
+- [ ] Documents formatted correctly
+- [ ] Formulas working
+- [ ] Presentations complete
+- [ ] Conversions successful
+- [ ] Automation tested
+- [ ] Files organized
+
+## Related Workflow Bundles
+
+- `development` - Application development
+- `documentation` - Documentation generation
+- `database` - Data integration
diff --git a/web-app/public/skills/on-call-handoff-patterns/SKILL.md b/web-app/public/skills/on-call-handoff-patterns/SKILL.md
index b7fad637..b4e9eb73 100644
--- a/web-app/public/skills/on-call-handoff-patterns/SKILL.md
+++ b/web-app/public/skills/on-call-handoff-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: on-call-handoff-patterns
-description: Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.
+description: "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro..."
+risk: unknown
+source: community
---
# On-Call Handoff Patterns
diff --git a/web-app/public/skills/onboarding-cro/SKILL.md b/web-app/public/skills/onboarding-cro/SKILL.md
index 97315d69..e66ccf7e 100644
--- a/web-app/public/skills/onboarding-cro/SKILL.md
+++ b/web-app/public/skills/onboarding-cro/SKILL.md
@@ -1,6 +1,8 @@
---
name: onboarding-cro
-description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
+description: "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u..."
+risk: unknown
+source: community
---
# Onboarding CRO
@@ -431,3 +433,6 @@ If you need more context:
- **email-sequence**: For onboarding email series
- **paywall-upgrade-cro**: For converting to paid during/after onboarding
- **ab-test-setup**: For testing onboarding changes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/one-drive-automation/SKILL.md b/web-app/public/skills/one-drive-automation/SKILL.md
index 76778b19..64d90719 100644
--- a/web-app/public/skills/one-drive-automation/SKILL.md
+++ b/web-app/public/skills/one-drive-automation/SKILL.md
@@ -3,6 +3,8 @@ name: one-drive-automation
description: "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# OneDrive Automation via Rube MCP
@@ -236,3 +238,6 @@ Most OneDrive tools accept either paths or IDs:
| Get quota | `ONE_DRIVE_GET_QUOTA` | (none) |
| Track changes | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `site_id`, `token` |
| Version history | `ONE_DRIVE_GET_ITEM_VERSIONS` | `item_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/openapi-spec-generation/SKILL.md b/web-app/public/skills/openapi-spec-generation/SKILL.md
index 83b1bee3..1b22bdec 100644
--- a/web-app/public/skills/openapi-spec-generation/SKILL.md
+++ b/web-app/public/skills/openapi-spec-generation/SKILL.md
@@ -1,6 +1,8 @@
---
name: openapi-spec-generation
-description: Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
+description: "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance."
+risk: unknown
+source: community
---
# OpenAPI Spec Generation
diff --git a/web-app/public/skills/os-scripting/SKILL.md b/web-app/public/skills/os-scripting/SKILL.md
new file mode 100644
index 00000000..913b60ec
--- /dev/null
+++ b/web-app/public/skills/os-scripting/SKILL.md
@@ -0,0 +1,429 @@
+---
+name: os-scripting
+description: "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation."
+source: personal
+risk: safe
+domain: system-administration
+category: workflow-bundle
+version: 1.0.0
+---
+
+# OS/Shell Scripting Troubleshooting Workflow Bundle
+
+## Overview
+
+Comprehensive workflow for operating system troubleshooting, shell scripting, and system administration across Linux, macOS, and Windows. This bundle orchestrates skills for debugging system issues, creating robust scripts, and automating administrative tasks.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Debugging shell script errors
+- Creating production-ready bash scripts
+- Troubleshooting system issues
+- Automating system administration tasks
+- Managing processes and services
+- Configuring system resources
+
+## Workflow Phases
+
+### Phase 1: Environment Assessment
+
+#### Skills to Invoke
+- `bash-linux` - Linux bash patterns
+- `bash-pro` - Professional bash scripting
+- `bash-defensive-patterns` - Defensive scripting
+
+#### Actions
+1. Identify operating system and version
+2. Check available tools and commands
+3. Verify permissions and access
+4. Assess system resources
+5. Review logs and error messages
+
+#### Diagnostic Commands
+```bash
+# System information
+uname -a
+cat /etc/os-release
+hostnamectl
+
+# Resource usage
+top
+htop
+df -h
+free -m
+
+# Process information
+ps aux
+pgrep -f pattern
+lsof -i :port
+
+# Network status
+netstat -tulpn
+ss -tulpn
+ip addr show
+```
+
+#### Copy-Paste Prompts
+```
+Use @bash-linux to diagnose system performance issues
+```
+
+### Phase 2: Script Analysis
+
+#### Skills to Invoke
+- `bash-defensive-patterns` - Defensive scripting
+- `shellcheck-configuration` - ShellCheck linting
+- `bats-testing-patterns` - Bats testing
+
+#### Actions
+1. Run ShellCheck for linting
+2. Analyze script structure
+3. Identify potential issues
+4. Check error handling
+5. Verify variable usage
+
+#### ShellCheck Usage
+```bash
+# Install ShellCheck
+sudo apt install shellcheck # Debian/Ubuntu
+brew install shellcheck # macOS
+
+# Run ShellCheck
+shellcheck script.sh
+shellcheck -f gcc script.sh
+
+# Fix common issues
+# - Use quotes around variables
+# - Check exit codes
+# - Handle errors properly
+```
+
+#### Copy-Paste Prompts
+```
+Use @shellcheck-configuration to lint and fix shell scripts
+```
+
+### Phase 3: Debugging
+
+#### Skills to Invoke
+- `systematic-debugging` - Systematic debugging
+- `debugger` - Debugging specialist
+- `error-detective` - Error pattern detection
+
+#### Actions
+1. Enable debug mode
+2. Add logging statements
+3. Trace execution flow
+4. Isolate failing sections
+5. Test components individually
+
+#### Debug Techniques
+```bash
+# Enable debug mode
+set -x # Print commands
+set -e # Exit on error
+set -u # Exit on undefined variable
+set -o pipefail # Pipeline failure detection
+
+# Add logging
+log() {
+ echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" >> /var/log/script.log
+}
+
+# Trap errors
+trap 'echo "Error on line $LINENO"' ERR
+
+# Test sections
+bash -n script.sh # Syntax check
+bash -x script.sh # Trace execution
+```
+
+#### Copy-Paste Prompts
+```
+Use @systematic-debugging to trace and fix shell script errors
+```
+
+### Phase 4: Script Development
+
+#### Skills to Invoke
+- `bash-pro` - Professional scripting
+- `bash-defensive-patterns` - Defensive patterns
+- `linux-shell-scripting` - Shell scripting
+
+#### Actions
+1. Design script structure
+2. Implement functions
+3. Add error handling
+4. Include input validation
+5. Add help documentation
+
+#### Script Template
+```bash
+#!/usr/bin/env bash
+set -euo pipefail
+
+# Constants
+readonly SCRIPT_NAME=$(basename "$0")
+readonly SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)
+
+# Logging
+log() {
+ local level="$1"
+ shift
+ echo "[$(date '+%Y-%m-%d %H:%M:%S')] [$level] $*" >&2
+}
+
+info() { log "INFO" "$@"; }
+warn() { log "WARN" "$@"; }
+error() { log "ERROR" "$@"; exit 1; }
+
+# Usage
+usage() {
+ cat </dev/null | sort -h
+find / -type f -size +500M 2>/dev/null
+```
+
+### Network Issues
+```bash
+ip addr show
+ip route show
+ss -tulpn
+curl -v http://target
+```
+
+### Service Failures
+```bash
+systemctl status service-name
+journalctl -u service-name -f
+systemctl restart service-name
+```
+
+## Quality Gates
+
+Before completing workflow, verify:
+- [ ] All scripts pass ShellCheck
+- [ ] Tests pass with Bats
+- [ ] Error handling implemented
+- [ ] Logging configured
+- [ ] Documentation complete
+- [ ] Automation scheduled
+
+## Related Workflow Bundles
+
+- `development` - Software development
+- `cloud-devops` - Cloud and DevOps
+- `security-audit` - Security testing
+- `database` - Database operations
diff --git a/web-app/public/skills/oss-hunter/SKILL.md b/web-app/public/skills/oss-hunter/SKILL.md
index 8d951bcc..44a4a521 100644
--- a/web-app/public/skills/oss-hunter/SKILL.md
+++ b/web-app/public/skills/oss-hunter/SKILL.md
@@ -1,6 +1,6 @@
---
name: oss-hunter
-description: Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
+description: "Automatically hunt for high-impact OSS contribution opportunities in trending repositories."
risk: safe
source: https://github.com/jackjin1997/ClawForge
metadata: {"openclaw":{"emoji":"🎯","category":"developer"}}
diff --git a/web-app/public/skills/outlook-automation/SKILL.md b/web-app/public/skills/outlook-automation/SKILL.md
index 288cfc9f..5a4e057c 100644
--- a/web-app/public/skills/outlook-automation/SKILL.md
+++ b/web-app/public/skills/outlook-automation/SKILL.md
@@ -3,6 +3,8 @@ name: outlook-automation
description: "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Outlook Automation via Rube MCP
@@ -189,3 +191,6 @@ Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rub
| List contacts | OUTLOOK_LIST_CONTACTS | top, filter |
| Create contact | OUTLOOK_CREATE_CONTACT | givenName, emailAddresses |
| Contact folders | OUTLOOK_GET_CONTACT_FOLDERS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/outlook-calendar-automation/SKILL.md b/web-app/public/skills/outlook-calendar-automation/SKILL.md
index 4c5f04ab..001d9d2a 100644
--- a/web-app/public/skills/outlook-calendar-automation/SKILL.md
+++ b/web-app/public/skills/outlook-calendar-automation/SKILL.md
@@ -3,6 +3,8 @@ name: outlook-calendar-automation
description: "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Outlook Calendar Automation via Rube MCP
@@ -234,3 +236,6 @@ filter: "contains(subject, 'Review') and categories/any(c:c eq 'Work')"
| Get schedule | OUTLOOK_GET_SCHEDULE | Schedules, StartTime, EndTime |
| List calendars | OUTLOOK_LIST_CALENDARS | user_id |
| Mailbox settings | OUTLOOK_GET_MAILBOX_SETTINGS | select |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/page-cro/SKILL.md b/web-app/public/skills/page-cro/SKILL.md
index de35da1f..cf1c1d80 100644
--- a/web-app/public/skills/page-cro/SKILL.md
+++ b/web-app/public/skills/page-cro/SKILL.md
@@ -1,12 +1,14 @@
---
name: page-cro
-description: >
+description: ">"
Analyze and optimize individual pages for conversion performance.
Use when the user wants to improve conversion rates, diagnose why a page
is underperforming, or increase the effectiveness of marketing pages
(homepage, landing pages, pricing, feature pages, or blog posts).
This skill focuses on diagnosis, prioritization, and testable recommendations—
not blind optimization.
+risk: unknown
+source: community
---
# Page Conversion Rate Optimization (CRO)
You are an expert in **page-level conversion optimization**.
@@ -341,3 +343,6 @@ Fix fundamentals first.
* **ab-test-setup** – For test execution and instrumentation
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pagerduty-automation/SKILL.md b/web-app/public/skills/pagerduty-automation/SKILL.md
index 7b277a70..48efe84d 100644
--- a/web-app/public/skills/pagerduty-automation/SKILL.md
+++ b/web-app/public/skills/pagerduty-automation/SKILL.md
@@ -3,6 +3,8 @@ name: pagerduty-automation
description: "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# PagerDuty Automation via Rube MCP
@@ -243,3 +245,6 @@ Automate PagerDuty incident management and operations through Composio's PagerDu
| List escalation policies | PAGERDUTY_FETCH_ESCALATION_POLICES_LIST | (none) |
| Create escalation policy | PAGERDUTY_CREATE_ESCALATION_POLICY | name, escalation_rules |
| Create team | PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS | name, description |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/paid-ads/SKILL.md b/web-app/public/skills/paid-ads/SKILL.md
index 2b3acd92..0be906b9 100644
--- a/web-app/public/skills/paid-ads/SKILL.md
+++ b/web-app/public/skills/paid-ads/SKILL.md
@@ -1,6 +1,8 @@
---
name: paid-ads
-description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization."
+description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '..."
+risk: unknown
+source: community
---
# Paid Ads
@@ -549,3 +551,6 @@ If you need more context:
- **analytics-tracking**: For proper conversion tracking setup
- **ab-test-setup**: For landing page testing to improve ROAS
- **page-cro**: For optimizing post-click conversion rates
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/parallel-agents/SKILL.md b/web-app/public/skills/parallel-agents/SKILL.md
index f09627ad..7733d9f4 100644
--- a/web-app/public/skills/parallel-agents/SKILL.md
+++ b/web-app/public/skills/parallel-agents/SKILL.md
@@ -1,7 +1,9 @@
---
name: parallel-agents
-description: Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
+description: "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Native Parallel Agents
diff --git a/web-app/public/skills/payment-integration/SKILL.md b/web-app/public/skills/payment-integration/SKILL.md
index b2b8d3b7..5620721d 100644
--- a/web-app/public/skills/payment-integration/SKILL.md
+++ b/web-app/public/skills/payment-integration/SKILL.md
@@ -1,10 +1,12 @@
---
name: payment-integration
-description: Integrate Stripe, PayPal, and payment processors. Handles checkout
+description: "Integrate Stripe, PayPal, and payment processors. Handles checkout"
flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when
implementing payments, billing, or subscription features.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/paypal-integration/SKILL.md b/web-app/public/skills/paypal-integration/SKILL.md
index 16a1ab81..05071b3b 100644
--- a/web-app/public/skills/paypal-integration/SKILL.md
+++ b/web-app/public/skills/paypal-integration/SKILL.md
@@ -1,6 +1,8 @@
---
name: paypal-integration
-description: Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows.
+description: "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com..."
+risk: unknown
+source: community
---
# PayPal Integration
diff --git a/web-app/public/skills/paywall-upgrade-cro/SKILL.md b/web-app/public/skills/paywall-upgrade-cro/SKILL.md
index 69791185..a613695e 100644
--- a/web-app/public/skills/paywall-upgrade-cro/SKILL.md
+++ b/web-app/public/skills/paywall-upgrade-cro/SKILL.md
@@ -1,6 +1,8 @@
---
name: paywall-upgrade-cro
-description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
+description: "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,..."
+risk: unknown
+source: community
---
# Paywall and Upgrade Screen CRO
@@ -568,3 +570,6 @@ If you need more context:
- **onboarding-cro**: For driving to aha moment before upgrade
- **ab-test-setup**: For testing paywall variations
- **analytics-tracking**: For measuring upgrade funnel
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pci-compliance/SKILL.md b/web-app/public/skills/pci-compliance/SKILL.md
index cec4432a..c5dfac75 100644
--- a/web-app/public/skills/pci-compliance/SKILL.md
+++ b/web-app/public/skills/pci-compliance/SKILL.md
@@ -1,6 +1,8 @@
---
name: pci-compliance
-description: Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card security measures.
+description: "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ..."
+risk: unknown
+source: community
---
# PCI Compliance
diff --git a/web-app/public/skills/pdf-official/SKILL.md b/web-app/public/skills/pdf-official/SKILL.md
index f6a22ddf..6c677ba3 100644
--- a/web-app/public/skills/pdf-official/SKILL.md
+++ b/web-app/public/skills/pdf-official/SKILL.md
@@ -1,7 +1,9 @@
---
-name: pdf
-description: Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
+name: pdf-official
+description: "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall..."
license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
---
# PDF Processing Guide
@@ -292,3 +294,6 @@ with open("encrypted.pdf", "wb") as output:
- For JavaScript libraries (pdf-lib), see reference.md
- If you need to fill out a PDF form, follow the instructions in forms.md
- For troubleshooting guides, see reference.md
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pentest-checklist/SKILL.md b/web-app/public/skills/pentest-checklist/SKILL.md
index bbf7ff77..9b82f330 100644
--- a/web-app/public/skills/pentest-checklist/SKILL.md
+++ b/web-app/public/skills/pentest-checklist/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Pentest Checklist
-description: This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
+name: pentest-checklist
+description: "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Pentest Checklist
@@ -332,3 +334,6 @@ tcpdump -i eth0 -w /tmp/pentest_capture.pcap &
| Findings disputed | Provide detailed evidence, retest |
| Remediation delayed | Prioritize by risk, set deadlines |
| Budget exceeded | Define clear scope, fixed-price contracts |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pentest-commands/SKILL.md b/web-app/public/skills/pentest-commands/SKILL.md
index 5fdf22aa..beefbf91 100644
--- a/web-app/public/skills/pentest-commands/SKILL.md
+++ b/web-app/public/skills/pentest-commands/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Pentest Commands
-description: This skill should be used when the user asks to "run pentest commands", "scan with nmap", "use metasploit exploits", "crack passwords with hydra or john", "scan web vulnerabilities with nikto", "enumerate networks", or needs essential penetration testing command references.
+name: pentest-commands
+description: "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Pentest Commands
@@ -436,3 +438,6 @@ nikto -h http://target && sqlmap -u "http://target/page?id=1" --dbs
| Ports filtered | Try different scan types |
| Exploit fails | Check target version compatibility |
| Passwords not cracking | Try larger wordlists, rules |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/performance-engineer/SKILL.md b/web-app/public/skills/performance-engineer/SKILL.md
index bc428a00..a463deec 100644
--- a/web-app/public/skills/performance-engineer/SKILL.md
+++ b/web-app/public/skills/performance-engineer/SKILL.md
@@ -8,6 +8,8 @@ description: Expert performance engineer specializing in modern observability,
optimization, observability, or scalability challenges.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are a performance engineer specializing in modern application optimization, observability, and scalable system performance.
diff --git a/web-app/public/skills/performance-profiling/SKILL.md b/web-app/public/skills/performance-profiling/SKILL.md
index 92921563..80f4513b 100644
--- a/web-app/public/skills/performance-profiling/SKILL.md
+++ b/web-app/public/skills/performance-profiling/SKILL.md
@@ -1,7 +1,9 @@
---
name: performance-profiling
-description: Performance profiling principles. Measurement, analysis, and optimization techniques.
+description: "Performance profiling principles. Measurement, analysis, and optimization techniques."
allowed-tools: Read, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Performance Profiling
@@ -141,3 +143,6 @@ allowed-tools: Read, Glob, Grep, Bash
---
> **Remember:** The fastest code is code that doesn't run. Remove before optimizing.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/performance-testing-review-ai-review/SKILL.md b/web-app/public/skills/performance-testing-review-ai-review/SKILL.md
index 7ed0b222..7296c39d 100644
--- a/web-app/public/skills/performance-testing-review-ai-review/SKILL.md
+++ b/web-app/public/skills/performance-testing-review-ai-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: performance-testing-review-ai-review
description: "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C"
+risk: unknown
+source: community
---
# AI-Powered Code Review Specialist
diff --git a/web-app/public/skills/performance-testing-review-multi-agent-review/SKILL.md b/web-app/public/skills/performance-testing-review-multi-agent-review/SKILL.md
index 9be192d7..648f3356 100644
--- a/web-app/public/skills/performance-testing-review-multi-agent-review/SKILL.md
+++ b/web-app/public/skills/performance-testing-review-multi-agent-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: performance-testing-review-multi-agent-review
description: "Use when working with performance testing review multi agent review"
+risk: unknown
+source: community
---
# Multi-Agent Code Review Orchestration Tool
diff --git a/web-app/public/skills/personal-tool-builder/SKILL.md b/web-app/public/skills/personal-tool-builder/SKILL.md
index 8453bd52..160ccff2 100644
--- a/web-app/public/skills/personal-tool-builder/SKILL.md
+++ b/web-app/public/skills/personal-tool-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: personal-tool-builder
-description: "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when: build a tool, personal tool, scratch my itch, solve my problem, CLI tool."
+description: "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Personal Tool Builder
@@ -287,3 +288,6 @@ Your needs = user needs.
## Related Skills
Works well with: `micro-saas-launcher`, `browser-extension-builder`, `workflow-automation`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/php-pro/SKILL.md b/web-app/public/skills/php-pro/SKILL.md
index f453faa1..1bd59417 100644
--- a/web-app/public/skills/php-pro/SKILL.md
+++ b/web-app/public/skills/php-pro/SKILL.md
@@ -1,10 +1,12 @@
---
name: php-pro
-description: Write idiomatic PHP code with generators, iterators, SPL data
+description: "Write idiomatic PHP code with generators, iterators, SPL data"
structures, and modern OOP features. Use PROACTIVELY for high-performance PHP
applications.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/pipedrive-automation/SKILL.md b/web-app/public/skills/pipedrive-automation/SKILL.md
index 4206830e..8e54aca1 100644
--- a/web-app/public/skills/pipedrive-automation/SKILL.md
+++ b/web-app/public/skills/pipedrive-automation/SKILL.md
@@ -3,6 +3,8 @@ name: pipedrive-automation
description: "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Pipedrive Automation via Rube MCP
@@ -222,3 +224,6 @@ Most list endpoints use offset-based pagination:
| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |
| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |
| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/plaid-fintech/SKILL.md b/web-app/public/skills/plaid-fintech/SKILL.md
index a1258c7d..8495fe09 100644
--- a/web-app/public/skills/plaid-fintech/SKILL.md
+++ b/web-app/public/skills/plaid-fintech/SKILL.md
@@ -1,7 +1,8 @@
---
name: plaid-fintech
-description: "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when: plaid, bank account linking, bank connection, ach, account aggregation."
+description: "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Plaid Fintech
@@ -48,3 +49,6 @@ Listen for PENDING_DISCONNECT webhook to proactively prompt users.
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | medium | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/plan-writing/SKILL.md b/web-app/public/skills/plan-writing/SKILL.md
index f4a4f60e..54da7bf4 100644
--- a/web-app/public/skills/plan-writing/SKILL.md
+++ b/web-app/public/skills/plan-writing/SKILL.md
@@ -1,7 +1,9 @@
---
name: plan-writing
-description: Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
+description: "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Plan Writing
diff --git a/web-app/public/skills/planning-with-files/SKILL.md b/web-app/public/skills/planning-with-files/SKILL.md
index 84d026a5..c5264ef9 100644
--- a/web-app/public/skills/planning-with-files/SKILL.md
+++ b/web-app/public/skills/planning-with-files/SKILL.md
@@ -1,7 +1,7 @@
---
name: planning-with-files
version: "2.1.2"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin..."
user-invocable: true
allowed-tools:
- Read
@@ -31,6 +31,8 @@ hooks:
- hooks:
- type: command
command: "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
+risk: unknown
+source: community
---
# Planning with Files
diff --git a/web-app/public/skills/playwright-skill/SKILL.md b/web-app/public/skills/playwright-skill/SKILL.md
index 98c82145..0a40e549 100644
--- a/web-app/public/skills/playwright-skill/SKILL.md
+++ b/web-app/public/skills/playwright-skill/SKILL.md
@@ -1,6 +1,8 @@
---
name: playwright-skill
-description: Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
+description: "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ..."
+risk: unknown
+source: community
---
**IMPORTANT - Path Resolution:**
@@ -451,3 +453,6 @@ User: "Use 3001"
- Test scripts written to `/tmp` for automatic cleanup (no clutter)
- Code executes reliably with proper module resolution via `run.js`
- Progressive disclosure - API_REFERENCE.md loaded only when advanced features needed
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/podcast-generation/SKILL.md b/web-app/public/skills/podcast-generation/SKILL.md
index 7f2e7205..8e130454 100644
--- a/web-app/public/skills/podcast-generation/SKILL.md
+++ b/web-app/public/skills/podcast-generation/SKILL.md
@@ -1,6 +1,8 @@
---
name: podcast-generation
-description: Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.
+description: "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio..."
+risk: unknown
+source: community
---
# Podcast Generation with GPT Realtime Mini
@@ -116,6 +118,9 @@ new Audio(audioUrl).play();
## References
-- **Full architecture**: See [references/architecture.md](references/architecture.md) for complete stack design
-- **Code examples**: See [references/code-examples.md](references/code-examples.md) for production patterns
-- **PCM conversion**: Use [scripts/pcm_to_wav.py](scripts/pcm_to_wav.py) for audio format conversion
+- **Full architecture**: See references/architecture.md for complete stack design
+- **Code examples**: See references/code-examples.md for production patterns
+- **PCM conversion**: Use scripts/pcm_to_wav.py for audio format conversion
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/popup-cro/SKILL.md b/web-app/public/skills/popup-cro/SKILL.md
index 88038a4d..bd3f8099 100644
--- a/web-app/public/skills/popup-cro/SKILL.md
+++ b/web-app/public/skills/popup-cro/SKILL.md
@@ -1,6 +1,8 @@
---
name: popup-cro
-description: Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.
+description: "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust."
+risk: unknown
+source: community
---
# Popup CRO
@@ -344,3 +346,6 @@ Multiple CTAs or mixed goals destroy performance.
* **page-cro** – Optimize the surrounding page
* **email-sequence** – Post-conversion follow-up
* **ab-test-setup** – Test popup variants safely
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/posix-shell-pro/SKILL.md b/web-app/public/skills/posix-shell-pro/SKILL.md
index 766ac019..6e248286 100644
--- a/web-app/public/skills/posix-shell-pro/SKILL.md
+++ b/web-app/public/skills/posix-shell-pro/SKILL.md
@@ -1,10 +1,12 @@
---
name: posix-shell-pro
-description: Expert in strict POSIX sh scripting for maximum portability across
+description: "Expert in strict POSIX sh scripting for maximum portability across"
Unix-like systems. Specializes in shell scripts that run on any
POSIX-compliant shell (dash, ash, sh, bash --posix).
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/postgres-best-practices/SKILL.md b/web-app/public/skills/postgres-best-practices/SKILL.md
index c1ad772e..43160b73 100644
--- a/web-app/public/skills/postgres-best-practices/SKILL.md
+++ b/web-app/public/skills/postgres-best-practices/SKILL.md
@@ -1,10 +1,12 @@
---
-name: supabase-postgres-best-practices
-description: Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
+name: postgres-best-practices
+description: "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations."
license: MIT
metadata:
author: supabase
version: "1.0.0"
+risk: unknown
+source: community
---
# Supabase Postgres Best Practices
@@ -55,3 +57,6 @@ Each rule file contains:
## Full Compiled Document
For the complete guide with all rules expanded: `AGENTS.md`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/postgresql-optimization/SKILL.md b/web-app/public/skills/postgresql-optimization/SKILL.md
new file mode 100644
index 00000000..3581986b
--- /dev/null
+++ b/web-app/public/skills/postgresql-optimization/SKILL.md
@@ -0,0 +1,175 @@
+---
+name: postgresql-optimization
+description: "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management."
+source: personal
+risk: safe
+domain: database
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# PostgreSQL Optimization Workflow
+
+## Overview
+
+Specialized workflow for PostgreSQL database optimization including query tuning, indexing strategies, performance analysis, vacuum management, and production database administration.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Optimizing slow PostgreSQL queries
+- Designing indexing strategies
+- Analyzing database performance
+- Tuning PostgreSQL configuration
+- Managing production databases
+
+## Workflow Phases
+
+### Phase 1: Performance Assessment
+
+#### Skills to Invoke
+- `database-optimizer` - Database optimization
+- `postgres-best-practices` - PostgreSQL best practices
+
+#### Actions
+1. Check database version
+2. Review configuration
+3. Analyze slow queries
+4. Check resource usage
+5. Identify bottlenecks
+
+#### Copy-Paste Prompts
+```
+Use @database-optimizer to assess PostgreSQL performance
+```
+
+### Phase 2: Query Analysis
+
+#### Skills to Invoke
+- `sql-optimization-patterns` - SQL optimization
+- `postgres-best-practices` - PostgreSQL patterns
+
+#### Actions
+1. Run EXPLAIN ANALYZE
+2. Identify scan types
+3. Check join strategies
+4. Analyze execution time
+5. Find optimization opportunities
+
+#### Copy-Paste Prompts
+```
+Use @sql-optimization-patterns to analyze and optimize queries
+```
+
+### Phase 3: Indexing Strategy
+
+#### Skills to Invoke
+- `database-design` - Index design
+- `postgresql` - PostgreSQL indexing
+
+#### Actions
+1. Identify missing indexes
+2. Create B-tree indexes
+3. Add composite indexes
+4. Consider partial indexes
+5. Review index usage
+
+#### Copy-Paste Prompts
+```
+Use @database-design to design PostgreSQL indexing strategy
+```
+
+### Phase 4: Query Optimization
+
+#### Skills to Invoke
+- `sql-optimization-patterns` - Query tuning
+- `sql-pro` - SQL expertise
+
+#### Actions
+1. Rewrite inefficient queries
+2. Optimize joins
+3. Add CTEs where helpful
+4. Implement pagination
+5. Test improvements
+
+#### Copy-Paste Prompts
+```
+Use @sql-optimization-patterns to optimize SQL queries
+```
+
+### Phase 5: Configuration Tuning
+
+#### Skills to Invoke
+- `postgres-best-practices` - Configuration
+- `database-admin` - Database administration
+
+#### Actions
+1. Tune shared_buffers
+2. Configure work_mem
+3. Set effective_cache_size
+4. Adjust checkpoint settings
+5. Configure autovacuum
+
+#### Copy-Paste Prompts
+```
+Use @postgres-best-practices to tune PostgreSQL configuration
+```
+
+### Phase 6: Maintenance
+
+#### Skills to Invoke
+- `database-admin` - Database maintenance
+- `postgresql` - PostgreSQL maintenance
+
+#### Actions
+1. Schedule VACUUM
+2. Run ANALYZE
+3. Check table bloat
+4. Monitor autovacuum
+5. Review statistics
+
+#### Copy-Paste Prompts
+```
+Use @database-admin to schedule PostgreSQL maintenance
+```
+
+### Phase 7: Monitoring
+
+#### Skills to Invoke
+- `grafana-dashboards` - Monitoring dashboards
+- `prometheus-configuration` - Metrics collection
+
+#### Actions
+1. Set up monitoring
+2. Create dashboards
+3. Configure alerts
+4. Track key metrics
+5. Review trends
+
+#### Copy-Paste Prompts
+```
+Use @grafana-dashboards to create PostgreSQL monitoring
+```
+
+## Optimization Checklist
+
+- [ ] Slow queries identified
+- [ ] Indexes optimized
+- [ ] Configuration tuned
+- [ ] Maintenance scheduled
+- [ ] Monitoring active
+- [ ] Performance improved
+
+## Quality Gates
+
+- [ ] Query performance improved
+- [ ] Indexes effective
+- [ ] Configuration optimized
+- [ ] Maintenance automated
+- [ ] Monitoring in place
+
+## Related Workflow Bundles
+
+- `database` - Database operations
+- `cloud-devops` - Infrastructure
+- `performance-optimization` - Performance
diff --git a/web-app/public/skills/postgresql/SKILL.md b/web-app/public/skills/postgresql/SKILL.md
index 7f60a79d..e017292b 100644
--- a/web-app/public/skills/postgresql/SKILL.md
+++ b/web-app/public/skills/postgresql/SKILL.md
@@ -1,6 +1,8 @@
---
name: postgresql
-description: Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
+description: "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features"
+risk: unknown
+source: community
---
# PostgreSQL Table Design
diff --git a/web-app/public/skills/posthog-automation/SKILL.md b/web-app/public/skills/posthog-automation/SKILL.md
index a8fb0959..c4f50d16 100644
--- a/web-app/public/skills/posthog-automation/SKILL.md
+++ b/web-app/public/skills/posthog-automation/SKILL.md
@@ -3,6 +3,8 @@ name: posthog-automation
description: "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# PostHog Automation via Rube MCP
@@ -222,3 +224,6 @@ Feature flags support sophisticated targeting:
| List projects | POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION | organization_id |
| Who am I | POSTHOG_WHOAMI | (none) |
| User profile | POSTHOG_RETRIEVE_CURRENT_USER_PROFILE | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/postmark-automation/SKILL.md b/web-app/public/skills/postmark-automation/SKILL.md
index 4a0b0b42..d0a27bd8 100644
--- a/web-app/public/skills/postmark-automation/SKILL.md
+++ b/web-app/public/skills/postmark-automation/SKILL.md
@@ -3,6 +3,8 @@ name: postmark-automation
description: "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Postmark Automation via Rube MCP
@@ -185,3 +187,6 @@ Automate Postmark transactional email operations through Composio's Postmark too
| Tracked email counts | POSTMARK_GET_TRACKED_EMAIL_COUNTS | fromdate, todate, tag |
| Get server config | POSTMARK_GET_SERVER | (none) |
| Edit server config | POSTMARK_EDIT_SERVER | Name, TrackOpens, TrackLinks |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/postmortem-writing/SKILL.md b/web-app/public/skills/postmortem-writing/SKILL.md
index 4253b606..d9bc925d 100644
--- a/web-app/public/skills/postmortem-writing/SKILL.md
+++ b/web-app/public/skills/postmortem-writing/SKILL.md
@@ -1,6 +1,8 @@
---
name: postmortem-writing
-description: Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
+description: "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce..."
+risk: unknown
+source: community
---
# Postmortem Writing
@@ -221,8 +223,8 @@ The deployment completed at 14:23, but the first alert didn't fire until 14:31 (
- 2023-11-02: Similar connection issue in User Service (POSTMORTEM-42)
### References
-- [Connection Pool Best Practices](internal-wiki/connection-pools)
-- [Deployment Runbook](internal-wiki/deployment-runbook)
+- Connection Pool Best Practices
+- Deployment Runbook
```
### Template 2: 5 Whys Analysis
diff --git a/web-app/public/skills/powershell-windows/SKILL.md b/web-app/public/skills/powershell-windows/SKILL.md
index 1b0459ca..28798854 100644
--- a/web-app/public/skills/powershell-windows/SKILL.md
+++ b/web-app/public/skills/powershell-windows/SKILL.md
@@ -1,7 +1,9 @@
---
name: powershell-windows
-description: PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
+description: "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# PowerShell Windows Patterns
@@ -165,3 +167,6 @@ catch {
---
> **Remember:** PowerShell has unique syntax rules. Parentheses, ASCII-only, and null checks are non-negotiable.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pptx-official/SKILL.md b/web-app/public/skills/pptx-official/SKILL.md
index b93b875f..91bf1737 100644
--- a/web-app/public/skills/pptx-official/SKILL.md
+++ b/web-app/public/skills/pptx-official/SKILL.md
@@ -1,7 +1,9 @@
---
-name: pptx
-description: "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks"
+name: pptx-official
+description: "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo..."
license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
---
# PPTX creation, editing, and analysis
@@ -481,4 +483,7 @@ Required dependencies (should already be installed):
- **sharp**: `npm install -g sharp` (for SVG rasterization and image processing)
- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
\ No newline at end of file
+- **defusedxml**: `pip install defusedxml` (for secure XML parsing)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/pricing-strategy/SKILL.md b/web-app/public/skills/pricing-strategy/SKILL.md
index b6977285..f28ca5d5 100644
--- a/web-app/public/skills/pricing-strategy/SKILL.md
+++ b/web-app/public/skills/pricing-strategy/SKILL.md
@@ -1,6 +1,8 @@
---
name: pricing-strategy
-description: Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.
+description: "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives."
+risk: unknown
+source: community
---
# Pricing Strategy
@@ -354,3 +356,6 @@ analytics-tracking – Measure impact
ab-test-setup – Safe experimentation
marketing-psychology – Behavioral pricing effects
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/prisma-expert/SKILL.md b/web-app/public/skills/prisma-expert/SKILL.md
index 9b25003e..dd6a45b8 100644
--- a/web-app/public/skills/prisma-expert/SKILL.md
+++ b/web-app/public/skills/prisma-expert/SKILL.md
@@ -1,6 +1,8 @@
---
name: prisma-expert
-description: Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.
+description: "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re..."
+risk: unknown
+source: community
---
# Prisma Expert
@@ -353,3 +355,6 @@ const updateWithVersion = await prisma.post.update({
3. **Ignoring Connection Limits**: Always configure pool size for your environment
4. **Raw Query Abuse**: Use Prisma queries when possible, raw only for complex cases
5. **Migration in Production Dev Mode**: Never use `migrate dev` in production
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/privilege-escalation-methods/SKILL.md b/web-app/public/skills/privilege-escalation-methods/SKILL.md
index bfe17dc5..4f5c1fc1 100644
--- a/web-app/public/skills/privilege-escalation-methods/SKILL.md
+++ b/web-app/public/skills/privilege-escalation-methods/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Privilege Escalation Methods
-description: This skill should be used when the user asks to "escalate privileges", "get root access", "become administrator", "privesc techniques", "abuse sudo", "exploit SUID binaries", "Kerberoasting", "pass-the-ticket", "token impersonation", or needs guidance on post-exploitation privilege escalation for Linux or Windows systems.
+name: privilege-escalation-methods
+description: "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Privilege Escalation Methods
@@ -331,3 +333,6 @@ For detailed enumeration scripts, use:
- **WinPEAS**: Windows privilege escalation enumeration
- **BloodHound**: Active Directory attack path mapping
- **GTFOBins**: Unix binary exploitation reference
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/product-manager-toolkit/SKILL.md b/web-app/public/skills/product-manager-toolkit/SKILL.md
index f0d605bf..c6789c0e 100644
--- a/web-app/public/skills/product-manager-toolkit/SKILL.md
+++ b/web-app/public/skills/product-manager-toolkit/SKILL.md
@@ -1,6 +1,8 @@
---
name: product-manager-toolkit
-description: Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
+description: "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati..."
+risk: unknown
+source: community
---
# Product Manager Toolkit
@@ -349,3 +351,6 @@ python scripts/rice_prioritizer.py sample
python scripts/rice_prioritizer.py features.csv --output json
python scripts/customer_interview_analyzer.py interview.txt json
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/production-code-audit/SKILL.md b/web-app/public/skills/production-code-audit/SKILL.md
index 5b3a6827..f2392501 100644
--- a/web-app/public/skills/production-code-audit/SKILL.md
+++ b/web-app/public/skills/production-code-audit/SKILL.md
@@ -1,6 +1,8 @@
---
name: production-code-audit
description: "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations"
+risk: unknown
+source: community
---
# Production Code Audit
diff --git a/web-app/public/skills/programmatic-seo/SKILL.md b/web-app/public/skills/programmatic-seo/SKILL.md
index 25379c8d..28a2b0c1 100644
--- a/web-app/public/skills/programmatic-seo/SKILL.md
+++ b/web-app/public/skills/programmatic-seo/SKILL.md
@@ -1,12 +1,14 @@
---
name: programmatic-seo
-description: >
+description: ">"
Design and evaluate programmatic SEO strategies for creating SEO-driven pages
at scale using templates and structured data. Use when the user mentions
programmatic SEO, pages at scale, template pages, directory pages, location pages,
comparison pages, integration pages, or keyword-pattern page generation.
This skill focuses on feasibility, strategy, and page system design—not execution
unless explicitly requested.
+risk: unknown
+source: community
---
---
@@ -349,3 +351,6 @@ If triggered, **halt indexing or roll back**:
- **schema-markup** – Add structured data to templates
- **copywriting** – Improve non-templated sections
- **analytics-tracking** – Measure performance and validate value
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/projection-patterns/SKILL.md b/web-app/public/skills/projection-patterns/SKILL.md
index b4d70fb7..5850e02e 100644
--- a/web-app/public/skills/projection-patterns/SKILL.md
+++ b/web-app/public/skills/projection-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: projection-patterns
-description: Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
+description: "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems."
+risk: unknown
+source: community
---
# Projection Patterns
diff --git a/web-app/public/skills/prometheus-configuration/SKILL.md b/web-app/public/skills/prometheus-configuration/SKILL.md
index ca5d6579..e32e00dc 100644
--- a/web-app/public/skills/prometheus-configuration/SKILL.md
+++ b/web-app/public/skills/prometheus-configuration/SKILL.md
@@ -1,6 +1,8 @@
---
name: prometheus-configuration
-description: Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
+description: "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or..."
+risk: unknown
+source: community
---
# Prometheus Configuration
diff --git a/web-app/public/skills/prompt-caching/SKILL.md b/web-app/public/skills/prompt-caching/SKILL.md
index 7c30fc89..5db70035 100644
--- a/web-app/public/skills/prompt-caching/SKILL.md
+++ b/web-app/public/skills/prompt-caching/SKILL.md
@@ -1,7 +1,8 @@
---
name: prompt-caching
-description: "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augmented."
+description: "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Prompt Caching
@@ -59,3 +60,6 @@ Pre-cache documents in prompt instead of RAG retrieval
## Related Skills
Works well with: `context-window-management`, `rag-implementation`, `conversation-memory`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/prompt-engineer/README.md b/web-app/public/skills/prompt-engineer/README.md
index 1a757d5a..f3c44eb0 100644
--- a/web-app/public/skills/prompt-engineer/README.md
+++ b/web-app/public/skills/prompt-engineer/README.md
@@ -647,7 +647,7 @@ Then configure:
## 📖 Learn More
-- **[Skill Development Guide](../../resources/skills-development.md)** - Learn how to create your own skills
+- **Skill Development Guide** - Learn how to create your own skills
- **[SKILL.md](./SKILL.md)** - Full technical specification of this skill
- **[Repository README](../../README.md)** - Overview of all available skills
diff --git a/web-app/public/skills/prompt-engineer/SKILL.md b/web-app/public/skills/prompt-engineer/SKILL.md
index 63dbf265..1a16e902 100644
--- a/web-app/public/skills/prompt-engineer/SKILL.md
+++ b/web-app/public/skills/prompt-engineer/SKILL.md
@@ -9,6 +9,7 @@ platforms: [github-copilot-cli, claude-code, codex]
category: automation
tags: [prompt-engineering, optimization, frameworks, ai-enhancement]
risk: safe
+source: community
---
## Purpose
diff --git a/web-app/public/skills/prompt-engineering-patterns/SKILL.md b/web-app/public/skills/prompt-engineering-patterns/SKILL.md
index a5383998..6a2b0f31 100644
--- a/web-app/public/skills/prompt-engineering-patterns/SKILL.md
+++ b/web-app/public/skills/prompt-engineering-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: prompt-engineering-patterns
-description: Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.
+description: "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio..."
+risk: unknown
+source: community
---
# Prompt Engineering Patterns
diff --git a/web-app/public/skills/prompt-engineering/SKILL.md b/web-app/public/skills/prompt-engineering/SKILL.md
index 6b69c56e..8feb5132 100644
--- a/web-app/public/skills/prompt-engineering/SKILL.md
+++ b/web-app/public/skills/prompt-engineering/SKILL.md
@@ -1,6 +1,8 @@
---
name: prompt-engineering
-description: Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.
+description: "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior."
+risk: unknown
+source: community
---
# Prompt Engineering Patterns
@@ -169,3 +171,6 @@ Build prompts that gracefully handle failures:
- **Context overflow**: Exceeding token limits with excessive examples
- **Ambiguous instructions**: Leaving room for multiple interpretations
- **Ignoring edge cases**: Not testing on unusual or boundary inputs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/prompt-library/SKILL.md b/web-app/public/skills/prompt-library/SKILL.md
index 2421a27f..787d58f8 100644
--- a/web-app/public/skills/prompt-library/SKILL.md
+++ b/web-app/public/skills/prompt-library/SKILL.md
@@ -1,6 +1,8 @@
---
name: prompt-library
-description: "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks."
+description: "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-..."
+risk: unknown
+source: community
---
# 📝 Prompt Library
diff --git a/web-app/public/skills/protocol-reverse-engineering/SKILL.md b/web-app/public/skills/protocol-reverse-engineering/SKILL.md
index 3cbf76e8..f72357ed 100644
--- a/web-app/public/skills/protocol-reverse-engineering/SKILL.md
+++ b/web-app/public/skills/protocol-reverse-engineering/SKILL.md
@@ -1,6 +1,8 @@
---
name: protocol-reverse-engineering
-description: Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.
+description: "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol..."
+risk: unknown
+source: community
---
# Protocol Reverse Engineering
diff --git a/web-app/public/skills/pydantic-models-py/SKILL.md b/web-app/public/skills/pydantic-models-py/SKILL.md
index b46dc1ef..842ff0d0 100644
--- a/web-app/public/skills/pydantic-models-py/SKILL.md
+++ b/web-app/public/skills/pydantic-models-py/SKILL.md
@@ -1,6 +1,8 @@
---
name: pydantic-models-py
-description: Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation in Python applications using Pydantic v2.
+description: "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ..."
+risk: unknown
+source: community
---
# Pydantic Models
@@ -9,7 +11,7 @@ Create Pydantic models following the multi-model pattern for clean API contracts
## Quick Start
-Copy the template from [assets/template.py](assets/template.py) and replace placeholders:
+Copy the template from assets/template.py and replace placeholders:
- `{{ResourceName}}` → PascalCase name (e.g., `Project`)
- `{{resource_name}}` → snake_case name (e.g., `project`)
@@ -56,3 +58,6 @@ class MyInDB(MyResponse):
1. Create models in `src/backend/app/models/`
2. Export from `src/backend/app/models/__init__.py`
3. Add corresponding TypeScript types
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/python-development-python-scaffold/SKILL.md b/web-app/public/skills/python-development-python-scaffold/SKILL.md
index f1c0dcc5..e1f4e78c 100644
--- a/web-app/public/skills/python-development-python-scaffold/SKILL.md
+++ b/web-app/public/skills/python-development-python-scaffold/SKILL.md
@@ -1,6 +1,8 @@
---
name: python-development-python-scaffold
description: "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint"
+risk: unknown
+source: community
---
# Python Project Scaffolding
diff --git a/web-app/public/skills/python-fastapi-development/SKILL.md b/web-app/public/skills/python-fastapi-development/SKILL.md
new file mode 100644
index 00000000..815e415e
--- /dev/null
+++ b/web-app/public/skills/python-fastapi-development/SKILL.md
@@ -0,0 +1,216 @@
+---
+name: python-fastapi-development
+description: "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns."
+source: personal
+risk: safe
+domain: backend-development
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Python/FastAPI Development Workflow
+
+## Overview
+
+Specialized workflow for building production-ready Python backends with FastAPI, featuring async patterns, SQLAlchemy ORM, Pydantic validation, and comprehensive API patterns.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building new REST APIs with FastAPI
+- Creating async Python backends
+- Implementing database integration with SQLAlchemy
+- Setting up API authentication
+- Developing microservices
+
+## Workflow Phases
+
+### Phase 1: Project Setup
+
+#### Skills to Invoke
+- `app-builder` - Application scaffolding
+- `python-development-python-scaffold` - Python scaffolding
+- `fastapi-templates` - FastAPI templates
+- `uv-package-manager` - Package management
+
+#### Actions
+1. Set up Python environment (uv/poetry)
+2. Create project structure
+3. Configure FastAPI app
+4. Set up logging
+5. Configure environment variables
+
+#### Copy-Paste Prompts
+```
+Use @fastapi-templates to scaffold a new FastAPI project
+```
+
+```
+Use @python-development-python-scaffold to set up Python project structure
+```
+
+### Phase 2: Database Setup
+
+#### Skills to Invoke
+- `prisma-expert` - Prisma ORM (alternative)
+- `database-design` - Schema design
+- `postgresql` - PostgreSQL setup
+- `pydantic-models-py` - Pydantic models
+
+#### Actions
+1. Design database schema
+2. Set up SQLAlchemy models
+3. Create database connection
+4. Configure migrations (Alembic)
+5. Set up session management
+
+#### Copy-Paste Prompts
+```
+Use @database-design to design PostgreSQL schema
+```
+
+```
+Use @pydantic-models-py to create Pydantic models for API
+```
+
+### Phase 3: API Routes
+
+#### Skills to Invoke
+- `fastapi-router-py` - FastAPI routers
+- `api-design-principles` - API design
+- `api-patterns` - API patterns
+
+#### Actions
+1. Design API endpoints
+2. Create API routers
+3. Implement CRUD operations
+4. Add request validation
+5. Configure response models
+
+#### Copy-Paste Prompts
+```
+Use @fastapi-router-py to create API endpoints with CRUD operations
+```
+
+```
+Use @api-design-principles to design RESTful API
+```
+
+### Phase 4: Authentication
+
+#### Skills to Invoke
+- `auth-implementation-patterns` - Authentication
+- `api-security-best-practices` - API security
+
+#### Actions
+1. Choose auth strategy (JWT, OAuth2)
+2. Implement user registration
+3. Set up login endpoints
+4. Create auth middleware
+5. Add password hashing
+
+#### Copy-Paste Prompts
+```
+Use @auth-implementation-patterns to implement JWT authentication
+```
+
+### Phase 5: Error Handling
+
+#### Skills to Invoke
+- `fastapi-pro` - FastAPI patterns
+- `error-handling-patterns` - Error handling
+
+#### Actions
+1. Create custom exceptions
+2. Set up exception handlers
+3. Implement error responses
+4. Add request logging
+5. Configure error tracking
+
+#### Copy-Paste Prompts
+```
+Use @fastapi-pro to implement comprehensive error handling
+```
+
+### Phase 6: Testing
+
+#### Skills to Invoke
+- `python-testing-patterns` - pytest testing
+- `api-testing-observability-api-mock` - API testing
+
+#### Actions
+1. Set up pytest
+2. Create test fixtures
+3. Write unit tests
+4. Implement integration tests
+5. Configure test database
+
+#### Copy-Paste Prompts
+```
+Use @python-testing-patterns to write pytest tests for FastAPI
+```
+
+### Phase 7: Documentation
+
+#### Skills to Invoke
+- `api-documenter` - API documentation
+- `openapi-spec-generation` - OpenAPI specs
+
+#### Actions
+1. Configure OpenAPI schema
+2. Add endpoint documentation
+3. Create usage examples
+4. Set up API versioning
+5. Generate API docs
+
+#### Copy-Paste Prompts
+```
+Use @api-documenter to generate comprehensive API documentation
+```
+
+### Phase 8: Deployment
+
+#### Skills to Invoke
+- `deployment-engineer` - Deployment
+- `docker-expert` - Containerization
+
+#### Actions
+1. Create Dockerfile
+2. Set up docker-compose
+3. Configure production settings
+4. Set up reverse proxy
+5. Deploy to cloud
+
+#### Copy-Paste Prompts
+```
+Use @docker-expert to containerize FastAPI application
+```
+
+## Technology Stack
+
+| Category | Technology |
+|----------|------------|
+| Framework | FastAPI |
+| Language | Python 3.11+ |
+| ORM | SQLAlchemy 2.0 |
+| Validation | Pydantic v2 |
+| Database | PostgreSQL |
+| Migrations | Alembic |
+| Auth | JWT, OAuth2 |
+| Testing | pytest |
+
+## Quality Gates
+
+- [ ] All tests passing (>80% coverage)
+- [ ] Type checking passes (mypy)
+- [ ] Linting clean (ruff, black)
+- [ ] API documentation complete
+- [ ] Security scan passed
+- [ ] Performance benchmarks met
+
+## Related Workflow Bundles
+
+- `development` - General development
+- `database` - Database operations
+- `security-audit` - Security testing
+- `api-development` - API patterns
diff --git a/web-app/public/skills/python-packaging/SKILL.md b/web-app/public/skills/python-packaging/SKILL.md
index 21f798bd..3c881fe8 100644
--- a/web-app/public/skills/python-packaging/SKILL.md
+++ b/web-app/public/skills/python-packaging/SKILL.md
@@ -1,6 +1,8 @@
---
name: python-packaging
-description: Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.
+description: "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ..."
+risk: unknown
+source: community
---
# Python Packaging
diff --git a/web-app/public/skills/python-patterns/SKILL.md b/web-app/public/skills/python-patterns/SKILL.md
index 164e31cc..da257f39 100644
--- a/web-app/public/skills/python-patterns/SKILL.md
+++ b/web-app/public/skills/python-patterns/SKILL.md
@@ -1,7 +1,9 @@
---
name: python-patterns
-description: Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
+description: "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Python Patterns
@@ -9,6 +11,10 @@ allowed-tools: Read, Write, Edit, Glob, Grep
> Python development principles and decision-making for 2025.
> **Learn to THINK, not memorize patterns.**
+## When to Use
+
+Use this skill when making Python architecture decisions, choosing frameworks, designing async patterns, or structuring Python projects.
+
---
## ⚠️ How to Use This Skill
diff --git a/web-app/public/skills/python-performance-optimization/SKILL.md b/web-app/public/skills/python-performance-optimization/SKILL.md
index d3345620..4b0caa27 100644
--- a/web-app/public/skills/python-performance-optimization/SKILL.md
+++ b/web-app/public/skills/python-performance-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: python-performance-optimization
-description: Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
+description: "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance."
+risk: unknown
+source: community
---
# Python Performance Optimization
diff --git a/web-app/public/skills/python-pro/SKILL.md b/web-app/public/skills/python-pro/SKILL.md
index 3aacc483..97430766 100644
--- a/web-app/public/skills/python-pro/SKILL.md
+++ b/web-app/public/skills/python-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: python-pro
-description: Master Python 3.12+ with modern features, async programming,
+description: "Master Python 3.12+ with modern features, async programming,"
performance optimization, and production-ready practices. Expert in the latest
Python ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY
for Python development, optimization, or advanced Python patterns.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.
diff --git a/web-app/public/skills/python-testing-patterns/SKILL.md b/web-app/public/skills/python-testing-patterns/SKILL.md
index 06597d55..3ec727ec 100644
--- a/web-app/public/skills/python-testing-patterns/SKILL.md
+++ b/web-app/public/skills/python-testing-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: python-testing-patterns
-description: Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
+description: "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices."
+risk: unknown
+source: community
---
# Python Testing Patterns
diff --git a/web-app/public/skills/quant-analyst/SKILL.md b/web-app/public/skills/quant-analyst/SKILL.md
index 76675163..9ce77053 100644
--- a/web-app/public/skills/quant-analyst/SKILL.md
+++ b/web-app/public/skills/quant-analyst/SKILL.md
@@ -1,11 +1,13 @@
---
name: quant-analyst
-description: Build financial models, backtest trading strategies, and analyze
+description: "Build financial models, backtest trading strategies, and analyze"
market data. Implements risk metrics, portfolio optimization, and statistical
arbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or
risk analysis.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/radix-ui-design-system/SKILL.md b/web-app/public/skills/radix-ui-design-system/SKILL.md
index 6aaf1ca0..60130c58 100644
--- a/web-app/public/skills/radix-ui-design-system/SKILL.md
+++ b/web-app/public/skills/radix-ui-design-system/SKILL.md
@@ -1,6 +1,6 @@
---
name: radix-ui-design-system
-description: Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.
+description: "Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries."
risk: safe
source: self
---
diff --git a/web-app/public/skills/rag-engineer/SKILL.md b/web-app/public/skills/rag-engineer/SKILL.md
index b20c7ce9..42aae367 100644
--- a/web-app/public/skills/rag-engineer/SKILL.md
+++ b/web-app/public/skills/rag-engineer/SKILL.md
@@ -1,7 +1,8 @@
---
name: rag-engineer
-description: "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, vector search, embeddings, semantic search, document retrieval."
+description: "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# RAG Engineer
@@ -88,3 +89,6 @@ Combine semantic and keyword search
## Related Skills
Works well with: `ai-agents-architect`, `prompt-engineer`, `database-architect`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/rag-implementation/SKILL.md b/web-app/public/skills/rag-implementation/SKILL.md
index e8e34719..e1dac2b6 100644
--- a/web-app/public/skills/rag-implementation/SKILL.md
+++ b/web-app/public/skills/rag-implementation/SKILL.md
@@ -1,421 +1,197 @@
---
name: rag-implementation
-description: Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases.
+description: "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization."
+source: personal
+risk: safe
+domain: ai-ml
+category: granular-workflow-bundle
+version: 1.0.0
---
-# RAG Implementation
+# RAG Implementation Workflow
-Master Retrieval-Augmented Generation (RAG) to build LLM applications that provide accurate, grounded responses using external knowledge sources.
+## Overview
-## Use this skill when
+Specialized workflow for implementing RAG (Retrieval-Augmented Generation) systems including embedding model selection, vector database setup, chunking strategies, retrieval optimization, and evaluation.
-- Building Q&A systems over proprietary documents
-- Creating chatbots with current, factual information
-- Implementing semantic search with natural language queries
-- Reducing hallucinations with grounded responses
-- Enabling LLMs to access domain-specific knowledge
-- Building documentation assistants
-- Creating research tools with source citation
+## When to Use This Workflow
-## Do not use this skill when
+Use this workflow when:
+- Building RAG-powered applications
+- Implementing semantic search
+- Creating knowledge-grounded AI
+- Setting up document Q&A systems
+- Optimizing retrieval quality
-- You only need purely generative writing without retrieval
-- The dataset is too small to justify embeddings
-- You cannot store or process the source data safely
+## Workflow Phases
-## Instructions
+### Phase 1: Requirements Analysis
-1. Define the corpus, update cadence, and evaluation targets.
-2. Choose embedding models and vector store based on scale.
-3. Build ingestion, chunking, and retrieval with reranking.
-4. Evaluate with grounded QA metrics and monitor drift.
+#### Skills to Invoke
+- `ai-product` - AI product design
+- `rag-engineer` - RAG engineering
-## Safety
+#### Actions
+1. Define use case
+2. Identify data sources
+3. Set accuracy requirements
+4. Determine latency targets
+5. Plan evaluation metrics
-- Redact sensitive data and enforce access controls.
-- Avoid exposing source documents in responses when restricted.
-
-## Core Components
-
-### 1. Vector Databases
-**Purpose**: Store and retrieve document embeddings efficiently
-
-**Options:**
-- **Pinecone**: Managed, scalable, fast queries
-- **Weaviate**: Open-source, hybrid search
-- **Milvus**: High performance, on-premise
-- **Chroma**: Lightweight, easy to use
-- **Qdrant**: Fast, filtered search
-- **FAISS**: Meta's library, local deployment
-
-### 2. Embeddings
-**Purpose**: Convert text to numerical vectors for similarity search
-
-**Models:**
-- **text-embedding-ada-002** (OpenAI): General purpose, 1536 dims
-- **all-MiniLM-L6-v2** (Sentence Transformers): Fast, lightweight
-- **e5-large-v2**: High quality, multilingual
-- **Instructor**: Task-specific instructions
-- **bge-large-en-v1.5**: SOTA performance
-
-### 3. Retrieval Strategies
-**Approaches:**
-- **Dense Retrieval**: Semantic similarity via embeddings
-- **Sparse Retrieval**: Keyword matching (BM25, TF-IDF)
-- **Hybrid Search**: Combine dense + sparse
-- **Multi-Query**: Generate multiple query variations
-- **HyDE**: Generate hypothetical documents
-
-### 4. Reranking
-**Purpose**: Improve retrieval quality by reordering results
-
-**Methods:**
-- **Cross-Encoders**: BERT-based reranking
-- **Cohere Rerank**: API-based reranking
-- **Maximal Marginal Relevance (MMR)**: Diversity + relevance
-- **LLM-based**: Use LLM to score relevance
-
-## Quick Start
-
-```python
-from langchain.document_loaders import DirectoryLoader
-from langchain.text_splitters import RecursiveCharacterTextSplitter
-from langchain.embeddings import OpenAIEmbeddings
-from langchain.vectorstores import Chroma
-from langchain.chains import RetrievalQA
-from langchain.llms import OpenAI
-
-# 1. Load documents
-loader = DirectoryLoader('./docs', glob="**/*.txt")
-documents = loader.load()
-
-# 2. Split into chunks
-text_splitter = RecursiveCharacterTextSplitter(
- chunk_size=1000,
- chunk_overlap=200,
- length_function=len
-)
-chunks = text_splitter.split_documents(documents)
-
-# 3. Create embeddings and vector store
-embeddings = OpenAIEmbeddings()
-vectorstore = Chroma.from_documents(chunks, embeddings)
-
-# 4. Create retrieval chain
-qa_chain = RetrievalQA.from_chain_type(
- llm=OpenAI(),
- chain_type="stuff",
- retriever=vectorstore.as_retriever(search_kwargs={"k": 4}),
- return_source_documents=True
-)
-
-# 5. Query
-result = qa_chain({"query": "What are the main features?"})
-print(result['result'])
-print(result['source_documents'])
+#### Copy-Paste Prompts
+```
+Use @ai-product to define RAG application requirements
```
-## Advanced RAG Patterns
+### Phase 2: Embedding Selection
-### Pattern 1: Hybrid Search
-```python
-from langchain.retrievers import BM25Retriever, EnsembleRetriever
+#### Skills to Invoke
+- `embedding-strategies` - Embedding selection
+- `rag-engineer` - RAG patterns
-# Sparse retriever (BM25)
-bm25_retriever = BM25Retriever.from_documents(chunks)
-bm25_retriever.k = 5
+#### Actions
+1. Evaluate embedding models
+2. Test domain relevance
+3. Measure embedding quality
+4. Consider cost/latency
+5. Select model
-# Dense retriever (embeddings)
-embedding_retriever = vectorstore.as_retriever(search_kwargs={"k": 5})
-
-# Combine with weights
-ensemble_retriever = EnsembleRetriever(
- retrievers=[bm25_retriever, embedding_retriever],
- weights=[0.3, 0.7]
-)
+#### Copy-Paste Prompts
+```
+Use @embedding-strategies to select optimal embedding model
```
-### Pattern 2: Multi-Query Retrieval
-```python
-from langchain.retrievers.multi_query import MultiQueryRetriever
+### Phase 3: Vector Database Setup
-# Generate multiple query perspectives
-retriever = MultiQueryRetriever.from_llm(
- retriever=vectorstore.as_retriever(),
- llm=OpenAI()
-)
+#### Skills to Invoke
+- `vector-database-engineer` - Vector DB
+- `similarity-search-patterns` - Similarity search
-# Single query → multiple variations → combined results
-results = retriever.get_relevant_documents("What is the main topic?")
+#### Actions
+1. Choose vector database
+2. Design schema
+3. Configure indexes
+4. Set up connection
+5. Test queries
+
+#### Copy-Paste Prompts
+```
+Use @vector-database-engineer to set up vector database
```
-### Pattern 3: Contextual Compression
-```python
-from langchain.retrievers import ContextualCompressionRetriever
-from langchain.retrievers.document_compressors import LLMChainExtractor
+### Phase 4: Chunking Strategy
-compressor = LLMChainExtractor.from_llm(llm)
+#### Skills to Invoke
+- `rag-engineer` - Chunking strategies
+- `rag-implementation` - RAG implementation
-compression_retriever = ContextualCompressionRetriever(
- base_compressor=compressor,
- base_retriever=vectorstore.as_retriever()
-)
+#### Actions
+1. Choose chunk size
+2. Implement chunking
+3. Add overlap handling
+4. Create metadata
+5. Test retrieval quality
-# Returns only relevant parts of documents
-compressed_docs = compression_retriever.get_relevant_documents("query")
+#### Copy-Paste Prompts
+```
+Use @rag-engineer to implement chunking strategy
```
-### Pattern 4: Parent Document Retriever
-```python
-from langchain.retrievers import ParentDocumentRetriever
-from langchain.storage import InMemoryStore
+### Phase 5: Retrieval Implementation
-# Store for parent documents
-store = InMemoryStore()
+#### Skills to Invoke
+- `similarity-search-patterns` - Similarity search
+- `hybrid-search-implementation` - Hybrid search
-# Small chunks for retrieval, large chunks for context
-child_splitter = RecursiveCharacterTextSplitter(chunk_size=400)
-parent_splitter = RecursiveCharacterTextSplitter(chunk_size=2000)
+#### Actions
+1. Implement vector search
+2. Add keyword search
+3. Configure hybrid search
+4. Set up reranking
+5. Optimize latency
-retriever = ParentDocumentRetriever(
- vectorstore=vectorstore,
- docstore=store,
- child_splitter=child_splitter,
- parent_splitter=parent_splitter
-)
+#### Copy-Paste Prompts
+```
+Use @similarity-search-patterns to implement retrieval
```
-## Document Chunking Strategies
-
-### Recursive Character Text Splitter
-```python
-from langchain.text_splitters import RecursiveCharacterTextSplitter
-
-splitter = RecursiveCharacterTextSplitter(
- chunk_size=1000,
- chunk_overlap=200,
- length_function=len,
- separators=["\n\n", "\n", " ", ""] # Try these in order
-)
+```
+Use @hybrid-search-implementation to add hybrid search
```
-### Token-Based Splitting
-```python
-from langchain.text_splitters import TokenTextSplitter
+### Phase 6: LLM Integration
-splitter = TokenTextSplitter(
- chunk_size=512,
- chunk_overlap=50
-)
+#### Skills to Invoke
+- `llm-application-dev-ai-assistant` - LLM integration
+- `llm-application-dev-prompt-optimize` - Prompt optimization
+
+#### Actions
+1. Select LLM provider
+2. Design prompt template
+3. Implement context injection
+4. Add citation handling
+5. Test generation quality
+
+#### Copy-Paste Prompts
+```
+Use @llm-application-dev-ai-assistant to integrate LLM
```
-### Semantic Chunking
-```python
-from langchain.text_splitters import SemanticChunker
+### Phase 7: Caching
-splitter = SemanticChunker(
- embeddings=OpenAIEmbeddings(),
- breakpoint_threshold_type="percentile"
-)
+#### Skills to Invoke
+- `prompt-caching` - Prompt caching
+- `rag-engineer` - RAG optimization
+
+#### Actions
+1. Implement response caching
+2. Set up embedding cache
+3. Configure TTL
+4. Add cache invalidation
+5. Monitor hit rates
+
+#### Copy-Paste Prompts
+```
+Use @prompt-caching to implement RAG caching
```
-### Markdown Header Splitter
-```python
-from langchain.text_splitters import MarkdownHeaderTextSplitter
+### Phase 8: Evaluation
-headers_to_split_on = [
- ("#", "Header 1"),
- ("##", "Header 2"),
- ("###", "Header 3"),
-]
+#### Skills to Invoke
+- `llm-evaluation` - LLM evaluation
+- `evaluation` - AI evaluation
-splitter = MarkdownHeaderTextSplitter(headers_to_split_on=headers_to_split_on)
+#### Actions
+1. Define evaluation metrics
+2. Create test dataset
+3. Measure retrieval accuracy
+4. Evaluate generation quality
+5. Iterate on improvements
+
+#### Copy-Paste Prompts
+```
+Use @llm-evaluation to evaluate RAG system
```
-## Vector Store Configurations
+## RAG Architecture
-### Pinecone
-```python
-import pinecone
-from langchain.vectorstores import Pinecone
-
-pinecone.init(api_key="your-api-key", environment="us-west1-gcp")
-
-index = pinecone.Index("your-index-name")
-
-vectorstore = Pinecone(index, embeddings.embed_query, "text")
+```
+User Query -> Embedding -> Vector Search -> Retrieved Docs -> LLM -> Response
+ | | | |
+ Model Vector DB Chunk Store Prompt + Context
```
-### Weaviate
-```python
-import weaviate
-from langchain.vectorstores import Weaviate
+## Quality Gates
-client = weaviate.Client("http://localhost:8080")
+- [ ] Embedding model selected
+- [ ] Vector DB configured
+- [ ] Chunking implemented
+- [ ] Retrieval working
+- [ ] LLM integrated
+- [ ] Evaluation passing
-vectorstore = Weaviate(client, "Document", "content", embeddings)
-```
+## Related Workflow Bundles
-### Chroma (Local)
-```python
-from langchain.vectorstores import Chroma
-
-vectorstore = Chroma(
- collection_name="my_collection",
- embedding_function=embeddings,
- persist_directory="./chroma_db"
-)
-```
-
-## Retrieval Optimization
-
-### 1. Metadata Filtering
-```python
-# Add metadata during indexing
-chunks_with_metadata = []
-for i, chunk in enumerate(chunks):
- chunk.metadata = {
- "source": chunk.metadata.get("source"),
- "page": i,
- "category": determine_category(chunk.page_content)
- }
- chunks_with_metadata.append(chunk)
-
-# Filter during retrieval
-results = vectorstore.similarity_search(
- "query",
- filter={"category": "technical"},
- k=5
-)
-```
-
-### 2. Maximal Marginal Relevance
-```python
-# Balance relevance with diversity
-results = vectorstore.max_marginal_relevance_search(
- "query",
- k=5,
- fetch_k=20, # Fetch 20, return top 5 diverse
- lambda_mult=0.5 # 0=max diversity, 1=max relevance
-)
-```
-
-### 3. Reranking with Cross-Encoder
-```python
-from sentence_transformers import CrossEncoder
-
-reranker = CrossEncoder('cross-encoder/ms-marco-MiniLM-L-6-v2')
-
-# Get initial results
-candidates = vectorstore.similarity_search("query", k=20)
-
-# Rerank
-pairs = [[query, doc.page_content] for doc in candidates]
-scores = reranker.predict(pairs)
-
-# Sort by score and take top k
-reranked = sorted(zip(candidates, scores), key=lambda x: x[1], reverse=True)[:5]
-```
-
-## Prompt Engineering for RAG
-
-### Contextual Prompt
-```python
-prompt_template = """Use the following context to answer the question. If you cannot answer based on the context, say "I don't have enough information."
-
-Context:
-{context}
-
-Question: {question}
-
-Answer:"""
-```
-
-### With Citations
-```python
-prompt_template = """Answer the question based on the context below. Include citations using [1], [2], etc.
-
-Context:
-{context}
-
-Question: {question}
-
-Answer (with citations):"""
-```
-
-### With Confidence
-```python
-prompt_template = """Answer the question using the context. Provide a confidence score (0-100%) for your answer.
-
-Context:
-{context}
-
-Question: {question}
-
-Answer:
-Confidence:"""
-```
-
-## Evaluation Metrics
-
-```python
-def evaluate_rag_system(qa_chain, test_cases):
- metrics = {
- 'accuracy': [],
- 'retrieval_quality': [],
- 'groundedness': []
- }
-
- for test in test_cases:
- result = qa_chain({"query": test['question']})
-
- # Check if answer matches expected
- accuracy = calculate_accuracy(result['result'], test['expected'])
- metrics['accuracy'].append(accuracy)
-
- # Check if relevant docs were retrieved
- retrieval_quality = evaluate_retrieved_docs(
- result['source_documents'],
- test['relevant_docs']
- )
- metrics['retrieval_quality'].append(retrieval_quality)
-
- # Check if answer is grounded in context
- groundedness = check_groundedness(
- result['result'],
- result['source_documents']
- )
- metrics['groundedness'].append(groundedness)
-
- return {k: sum(v)/len(v) for k, v in metrics.items()}
-```
-
-## Resources
-
-- **references/vector-databases.md**: Detailed comparison of vector DBs
-- **references/embeddings.md**: Embedding model selection guide
-- **references/retrieval-strategies.md**: Advanced retrieval techniques
-- **references/reranking.md**: Reranking methods and when to use them
-- **references/context-window.md**: Managing context limits
-- **assets/vector-store-config.yaml**: Configuration templates
-- **assets/retriever-pipeline.py**: Complete RAG pipeline
-- **assets/embedding-models.md**: Model comparison and benchmarks
-
-## Best Practices
-
-1. **Chunk Size**: Balance between context and specificity (500-1000 tokens)
-2. **Overlap**: Use 10-20% overlap to preserve context at boundaries
-3. **Metadata**: Include source, page, timestamp for filtering and debugging
-4. **Hybrid Search**: Combine semantic and keyword search for best results
-5. **Reranking**: Improve top results with cross-encoder
-6. **Citations**: Always return source documents for transparency
-7. **Evaluation**: Continuously test retrieval quality and answer accuracy
-8. **Monitoring**: Track retrieval metrics in production
-
-## Common Issues
-
-- **Poor Retrieval**: Check embedding quality, chunk size, query formulation
-- **Irrelevant Results**: Add metadata filtering, use hybrid search, rerank
-- **Missing Information**: Ensure documents are properly indexed
-- **Slow Queries**: Optimize vector store, use caching, reduce k
-- **Hallucinations**: Improve grounding prompt, add verification step
+- `ai-ml` - AI/ML development
+- `ai-agent-development` - AI agents
+- `database` - Vector databases
diff --git a/web-app/public/skills/react-best-practices/SKILL.md b/web-app/public/skills/react-best-practices/SKILL.md
index 25bbe87e..c39b7cee 100644
--- a/web-app/public/skills/react-best-practices/SKILL.md
+++ b/web-app/public/skills/react-best-practices/SKILL.md
@@ -1,6 +1,8 @@
---
-name: vercel-react-best-practices
-description: React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
+name: react-best-practices
+description: "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat..."
+risk: unknown
+source: community
---
# Vercel React Best Practices
@@ -119,3 +121,6 @@ Each rule file contains:
## Full Compiled Document
For the complete guide with all rules expanded: `AGENTS.md`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/react-flow-architect/SKILL.md b/web-app/public/skills/react-flow-architect/SKILL.md
index 73fafe39..3cb2633e 100644
--- a/web-app/public/skills/react-flow-architect/SKILL.md
+++ b/web-app/public/skills/react-flow-architect/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-flow-architect
-description: "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or optimize ReactFlow applications for: (1) Interactive process graphs with expand/collapse navigation, (2) Hierarchical tree structures with drag & drop, (3) Performance-optimized large datasets with incremental rendering, (4) Auto-layout integration with Dagre, (5) Complex state management for nodes and edges, or any advanced ReactFlow visualization requirements."
+description: "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or..."
+risk: unknown
+source: community
---
# ReactFlow Architect
@@ -611,3 +613,6 @@ export default function InteractiveGraph() {
```
This comprehensive skill provides everything needed to build production-ready ReactFlow applications with hierarchical navigation, performance optimization, and advanced state management patterns.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/react-flow-node-ts/SKILL.md b/web-app/public/skills/react-flow-node-ts/SKILL.md
index e0a90a64..9336202b 100644
--- a/web-app/public/skills/react-flow-node-ts/SKILL.md
+++ b/web-app/public/skills/react-flow-node-ts/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-flow-node-ts
-description: Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing node-based UI components.
+description: "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no..."
+risk: unknown
+source: community
---
# React Flow Node
@@ -9,15 +11,15 @@ Create React Flow node components following established patterns with proper Typ
## Quick Start
-Copy templates from [assets/](assets/) and replace placeholders:
+Copy templates from assets/ and replace placeholders:
- `{{NodeName}}` → PascalCase component name (e.g., `VideoNode`)
- `{{nodeType}}` → kebab-case type identifier (e.g., `video-node`)
- `{{NodeData}}` → Data interface name (e.g., `VideoNodeData`)
## Templates
-- [assets/template.tsx](assets/template.tsx) - Node component
-- [assets/types.template.ts](assets/types.template.ts) - TypeScript definitions
+- assets/template.tsx - Node component
+- assets/types.template.ts - TypeScript definitions
## Node Component Pattern
@@ -64,3 +66,6 @@ export type MyNode = Node;
4. Add defaults in `src/frontend/src/store/app-store.ts`
5. Register in canvas `nodeTypes`
6. Add to AddBlockMenu and ConnectMenu
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/react-modernization/SKILL.md b/web-app/public/skills/react-modernization/SKILL.md
index 41b6c9c3..8b81a9de 100644
--- a/web-app/public/skills/react-modernization/SKILL.md
+++ b/web-app/public/skills/react-modernization/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-modernization
-description: Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
+description: "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to..."
+risk: unknown
+source: community
---
# React Modernization
diff --git a/web-app/public/skills/react-native-architecture/SKILL.md b/web-app/public/skills/react-native-architecture/SKILL.md
index 32f460c5..f222bef8 100644
--- a/web-app/public/skills/react-native-architecture/SKILL.md
+++ b/web-app/public/skills/react-native-architecture/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-native-architecture
-description: Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.
+description: "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti..."
+risk: unknown
+source: community
---
# React Native Architecture
diff --git a/web-app/public/skills/react-nextjs-development/SKILL.md b/web-app/public/skills/react-nextjs-development/SKILL.md
new file mode 100644
index 00000000..e35c1e2e
--- /dev/null
+++ b/web-app/public/skills/react-nextjs-development/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: react-nextjs-development
+description: "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns."
+source: personal
+risk: safe
+domain: frontend-development
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# React/Next.js Development Workflow
+
+## Overview
+
+Specialized workflow for building React and Next.js 14+ applications with modern patterns including App Router, Server Components, TypeScript, and Tailwind CSS.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building new React applications
+- Creating Next.js 14+ projects with App Router
+- Implementing Server Components
+- Setting up TypeScript with React
+- Styling with Tailwind CSS
+- Building full-stack Next.js applications
+
+## Workflow Phases
+
+### Phase 1: Project Setup
+
+#### Skills to Invoke
+- `app-builder` - Application scaffolding
+- `senior-fullstack` - Full-stack guidance
+- `nextjs-app-router-patterns` - Next.js 14+ patterns
+- `typescript-pro` - TypeScript setup
+
+#### Actions
+1. Choose project type (React SPA, Next.js app)
+2. Select build tool (Vite, Next.js, Create React App)
+3. Scaffold project structure
+4. Configure TypeScript
+5. Set up ESLint and Prettier
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to scaffold a new Next.js 14 project with App Router
+```
+
+```
+Use @nextjs-app-router-patterns to set up Server Components
+```
+
+### Phase 2: Component Architecture
+
+#### Skills to Invoke
+- `frontend-developer` - Component development
+- `react-patterns` - React patterns
+- `react-state-management` - State management
+- `react-ui-patterns` - UI patterns
+
+#### Actions
+1. Design component hierarchy
+2. Create base components
+3. Implement layout components
+4. Set up state management
+5. Create custom hooks
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create reusable React components
+```
+
+```
+Use @react-patterns to implement proper component composition
+```
+
+```
+Use @react-state-management to set up Zustand store
+```
+
+### Phase 3: Styling and Design
+
+#### Skills to Invoke
+- `frontend-design` - UI design
+- `tailwind-patterns` - Tailwind CSS
+- `tailwind-design-system` - Design system
+- `core-components` - Component library
+
+#### Actions
+1. Set up Tailwind CSS
+2. Configure design tokens
+3. Create utility classes
+4. Build component styles
+5. Implement responsive design
+
+#### Copy-Paste Prompts
+```
+Use @tailwind-patterns to style components with Tailwind CSS v4
+```
+
+```
+Use @frontend-design to create a modern dashboard UI
+```
+
+### Phase 4: Data Fetching
+
+#### Skills to Invoke
+- `nextjs-app-router-patterns` - Server Components
+- `react-state-management` - React Query
+- `api-patterns` - API integration
+
+#### Actions
+1. Implement Server Components
+2. Set up React Query/SWR
+3. Create API client
+4. Handle loading states
+5. Implement error boundaries
+
+#### Copy-Paste Prompts
+```
+Use @nextjs-app-router-patterns to implement Server Components data fetching
+```
+
+### Phase 5: Routing and Navigation
+
+#### Skills to Invoke
+- `nextjs-app-router-patterns` - App Router
+- `nextjs-best-practices` - Next.js patterns
+
+#### Actions
+1. Set up file-based routing
+2. Create dynamic routes
+3. Implement nested routes
+4. Add route guards
+5. Configure redirects
+
+#### Copy-Paste Prompts
+```
+Use @nextjs-app-router-patterns to set up parallel routes and intercepting routes
+```
+
+### Phase 6: Forms and Validation
+
+#### Skills to Invoke
+- `frontend-developer` - Form development
+- `typescript-advanced-types` - Type validation
+- `react-ui-patterns` - Form patterns
+
+#### Actions
+1. Choose form library (React Hook Form, Formik)
+2. Set up validation (Zod, Yup)
+3. Create form components
+4. Handle submissions
+5. Implement error handling
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create forms with React Hook Form and Zod
+```
+
+### Phase 7: Testing
+
+#### Skills to Invoke
+- `javascript-testing-patterns` - Jest/Vitest
+- `playwright-skill` - E2E testing
+- `e2e-testing-patterns` - E2E patterns
+
+#### Actions
+1. Set up testing framework
+2. Write unit tests
+3. Create component tests
+4. Implement E2E tests
+5. Configure CI integration
+
+#### Copy-Paste Prompts
+```
+Use @javascript-testing-patterns to write Vitest tests
+```
+
+```
+Use @playwright-skill to create E2E tests for critical flows
+```
+
+### Phase 8: Build and Deployment
+
+#### Skills to Invoke
+- `vercel-deployment` - Vercel deployment
+- `vercel-deploy-claimable` - Vercel deployment
+- `web-performance-optimization` - Performance
+
+#### Actions
+1. Configure build settings
+2. Optimize bundle size
+3. Set up environment variables
+4. Deploy to Vercel
+5. Configure preview deployments
+
+#### Copy-Paste Prompts
+```
+Use @vercel-deployment to deploy Next.js app to production
+```
+
+## Technology Stack
+
+| Category | Technology |
+|----------|------------|
+| Framework | Next.js 14+, React 18+ |
+| Language | TypeScript 5+ |
+| Styling | Tailwind CSS v4 |
+| State | Zustand, React Query |
+| Forms | React Hook Form, Zod |
+| Testing | Vitest, Playwright |
+| Deployment | Vercel |
+
+## Quality Gates
+
+- [ ] TypeScript compiles without errors
+- [ ] All tests passing
+- [ ] Linting clean
+- [ ] Performance metrics met (LCP, CLS, FID)
+- [ ] Accessibility checked (WCAG 2.1)
+- [ ] Responsive design verified
+
+## Related Workflow Bundles
+
+- `development` - General development
+- `testing-qa` - Testing workflow
+- `documentation` - Documentation
+- `typescript-development` - TypeScript patterns
diff --git a/web-app/public/skills/react-patterns/SKILL.md b/web-app/public/skills/react-patterns/SKILL.md
index a8027f40..23a78489 100644
--- a/web-app/public/skills/react-patterns/SKILL.md
+++ b/web-app/public/skills/react-patterns/SKILL.md
@@ -1,7 +1,9 @@
---
name: react-patterns
-description: Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.
+description: "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# React Patterns
@@ -196,3 +198,6 @@ allowed-tools: Read, Write, Edit, Glob, Grep
---
> **Remember:** React is about composition. Build small, combine thoughtfully.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/react-state-management/SKILL.md b/web-app/public/skills/react-state-management/SKILL.md
index dfe69b6e..dbfb3372 100644
--- a/web-app/public/skills/react-state-management/SKILL.md
+++ b/web-app/public/skills/react-state-management/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-state-management
-description: Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.
+description: "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions."
+risk: unknown
+source: community
---
# React State Management
diff --git a/web-app/public/skills/react-ui-patterns/SKILL.md b/web-app/public/skills/react-ui-patterns/SKILL.md
index b33c3768..15dc9fa8 100644
--- a/web-app/public/skills/react-ui-patterns/SKILL.md
+++ b/web-app/public/skills/react-ui-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: react-ui-patterns
-description: Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.
+description: "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states."
+risk: unknown
+source: community
---
# React UI Patterns
@@ -287,3 +289,6 @@ Before completing any UI component:
- **graphql-schema**: Use mutation patterns with proper error handling
- **testing-patterns**: Test all UI states (loading, error, empty, success)
- **formik-patterns**: Apply form submission patterns
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/readme/SKILL.md b/web-app/public/skills/readme/SKILL.md
index dbd0e0fb..e16ba838 100644
--- a/web-app/public/skills/readme/SKILL.md
+++ b/web-app/public/skills/readme/SKILL.md
@@ -1,6 +1,6 @@
---
name: readme
-description: "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment."
+description: "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he..."
source: "https://github.com/Shpigford/skills/tree/main/readme"
risk: safe
---
diff --git a/web-app/public/skills/receiving-code-review/SKILL.md b/web-app/public/skills/receiving-code-review/SKILL.md
index 4ea72cdf..29b57ca7 100644
--- a/web-app/public/skills/receiving-code-review/SKILL.md
+++ b/web-app/public/skills/receiving-code-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: receiving-code-review
-description: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
+description: "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat..."
+risk: unknown
+source: community
---
# Code Review Reception
@@ -211,3 +213,6 @@ When replying to inline review comments on GitHub, reply in the comment thread (
Verify. Question. Then implement.
No performative agreement. Technical rigor always.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/red-team-tactics/SKILL.md b/web-app/public/skills/red-team-tactics/SKILL.md
index ed3f7d68..2281e9c4 100644
--- a/web-app/public/skills/red-team-tactics/SKILL.md
+++ b/web-app/public/skills/red-team-tactics/SKILL.md
@@ -1,7 +1,9 @@
---
name: red-team-tactics
-description: Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.
+description: "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting."
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
# Red Team Tactics
@@ -197,3 +199,6 @@ For each successful technique:
---
> **Remember:** Red team simulates attackers to improve defenses, not to cause harm.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/red-team-tools/SKILL.md b/web-app/public/skills/red-team-tools/SKILL.md
index e3d2e677..337293c6 100644
--- a/web-app/public/skills/red-team-tools/SKILL.md
+++ b/web-app/public/skills/red-team-tools/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Red Team Tools and Methodology
-description: This skill should be used when the user asks to "follow red team methodology", "perform bug bounty hunting", "automate reconnaissance", "hunt for XSS vulnerabilities", "enumerate subdomains", or needs security researcher techniques and tool configurations from top bug bounty hunters.
+name: red-team-tools
+description: "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Red Team Tools and Methodology
@@ -308,3 +310,6 @@ amass enum -d target.com | httpx | nuclei -t ~/nuclei-templates/
| Missing subdomains | Combine multiple enumeration sources |
| API key errors | Verify keys in config files |
| Tools not found | Install Go tools with `go install` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/reddit-automation/SKILL.md b/web-app/public/skills/reddit-automation/SKILL.md
index 77303375..e5fdd657 100644
--- a/web-app/public/skills/reddit-automation/SKILL.md
+++ b/web-app/public/skills/reddit-automation/SKILL.md
@@ -3,6 +3,8 @@ name: reddit-automation
description: "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Reddit Automation via Rube MCP
@@ -190,7 +192,7 @@ t5_ = Subreddit
**Text Formatting**:
- Reddit uses Markdown for post and comment formatting
- Code blocks, tables, and headers are supported
-- Links use `[text](url)` format
+- Links use `text` format
- Mention users with `u/username`, subreddits with `r/subreddit`
## Quick Reference
@@ -210,3 +212,6 @@ t5_ = Subreddit
| Get specific comment | REDDIT_RETRIEVE_SPECIFIC_COMMENT | comment_id |
| List post flairs | REDDIT_LIST_SUBREDDIT_POST_FLAIRS | subreddit |
| Get user flair | REDDIT_GET_USER_FLAIR | subreddit |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/reference-builder/SKILL.md b/web-app/public/skills/reference-builder/SKILL.md
index 7da27125..83611fa8 100644
--- a/web-app/public/skills/reference-builder/SKILL.md
+++ b/web-app/public/skills/reference-builder/SKILL.md
@@ -1,11 +1,13 @@
---
name: reference-builder
-description: Creates exhaustive technical references and API documentation.
+description: "Creates exhaustive technical references and API documentation."
Generates comprehensive parameter listings, configuration guides, and
searchable reference materials. Use PROACTIVELY for API docs, configuration
references, or complete technical specifications.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/referral-program/SKILL.md b/web-app/public/skills/referral-program/SKILL.md
index f6a1e284..d20b4e7e 100644
--- a/web-app/public/skills/referral-program/SKILL.md
+++ b/web-app/public/skills/referral-program/SKILL.md
@@ -1,6 +1,8 @@
---
name: referral-program
-description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization."
+description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of..."
+risk: unknown
+source: community
---
# Referral & Affiliate Programs
@@ -600,3 +602,6 @@ If you need more context:
- **marketing-psychology**: For understanding referral motivation
- **analytics-tracking**: For tracking referral attribution
- **pricing-strategy**: For structuring rewards relative to LTV
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/remotion-best-practices/SKILL.md b/web-app/public/skills/remotion-best-practices/SKILL.md
index bf16885b..8eec3b79 100644
--- a/web-app/public/skills/remotion-best-practices/SKILL.md
+++ b/web-app/public/skills/remotion-best-practices/SKILL.md
@@ -1,10 +1,12 @@
---
name: remotion-best-practices
-description: Best practices for Remotion - Video creation in React
+description: "Best practices for Remotion - Video creation in React"
author: remotion-dev
version: "1.0"
metadata:
tags: remotion, video, react, animation, composition
+risk: unknown
+source: community
---
## When to use
diff --git a/web-app/public/skills/remotion-best-practices/rules/charts.md b/web-app/public/skills/remotion-best-practices/rules/charts.md
index a402ed53..ea59e543 100644
--- a/web-app/public/skills/remotion-best-practices/rules/charts.md
+++ b/web-app/public/skills/remotion-best-practices/rules/charts.md
@@ -17,7 +17,7 @@ Instead, drive all animations from `useCurrentFrame()`.
## Bar Chart Animations
-See [Bar Chart Example](assets/charts/bar-chart.tsx) for a basic example implmentation.
+See Bar Chart Example for a basic example implmentation.
### Staggered Bars
diff --git a/web-app/public/skills/render-automation/SKILL.md b/web-app/public/skills/render-automation/SKILL.md
index 5ae052bc..64066d3b 100644
--- a/web-app/public/skills/render-automation/SKILL.md
+++ b/web-app/public/skills/render-automation/SKILL.md
@@ -3,6 +3,8 @@ name: render-automation
description: "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Render Automation via Rube MCP
@@ -179,3 +181,6 @@ Automate Render cloud platform operations through Composio's Render toolkit via
| Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache |
| Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId |
| List projects | RENDER_LIST_PROJECTS | limit, cursor |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/requesting-code-review/SKILL.md b/web-app/public/skills/requesting-code-review/SKILL.md
index f0e33952..959006e8 100644
--- a/web-app/public/skills/requesting-code-review/SKILL.md
+++ b/web-app/public/skills/requesting-code-review/SKILL.md
@@ -1,6 +1,8 @@
---
name: requesting-code-review
-description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
+description: "Use when completing tasks, implementing major features, or before merging to verify work meets requirements"
+risk: unknown
+source: community
---
# Requesting Code Review
@@ -103,3 +105,6 @@ You: [Fix progress indicators]
- Request clarification
See template at: requesting-code-review/code-reviewer.md
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/research-engineer/SKILL.md b/web-app/public/skills/research-engineer/SKILL.md
index 3fed5186..235ce1b5 100644
--- a/web-app/public/skills/research-engineer/SKILL.md
+++ b/web-app/public/skills/research-engineer/SKILL.md
@@ -1,6 +1,8 @@
---
name: research-engineer
-description: "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology."
+description: "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl..."
+risk: unknown
+source: community
---
# Academic Research Engineer
@@ -133,3 +135,6 @@ This recurrence relation resolves to $T(n) \approx 1.618^n$.
**Optimization:**
Using Matrix Exponentiation, we can reduce this to $O(\log n)$. Implementation follows..."
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/reverse-engineer/SKILL.md b/web-app/public/skills/reverse-engineer/SKILL.md
index b864c74f..8238c7ac 100644
--- a/web-app/public/skills/reverse-engineer/SKILL.md
+++ b/web-app/public/skills/reverse-engineer/SKILL.md
@@ -1,6 +1,6 @@
---
name: reverse-engineer
-description: Expert reverse engineer specializing in binary analysis,
+description: "Expert reverse engineer specializing in binary analysis,"
disassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,
radare2, x64dbg, and modern RE toolchains. Handles executable analysis,
library inspection, protocol extraction, and vulnerability research. Use
@@ -8,6 +8,8 @@ description: Expert reverse engineer specializing in binary analysis,
understanding undocumented software.
metadata:
model: opus
+risk: unknown
+source: community
---
# Common RE scripting environments
diff --git a/web-app/public/skills/risk-manager/SKILL.md b/web-app/public/skills/risk-manager/SKILL.md
index 88a1a365..e860fe43 100644
--- a/web-app/public/skills/risk-manager/SKILL.md
+++ b/web-app/public/skills/risk-manager/SKILL.md
@@ -1,10 +1,12 @@
---
name: risk-manager
-description: Monitor portfolio risk, R-multiples, and position limits. Creates
+description: "Monitor portfolio risk, R-multiples, and position limits. Creates"
hedging strategies, calculates expectancy, and implements stop-losses. Use
PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/risk-metrics-calculation/SKILL.md b/web-app/public/skills/risk-metrics-calculation/SKILL.md
index 3e543881..86e81c58 100644
--- a/web-app/public/skills/risk-metrics-calculation/SKILL.md
+++ b/web-app/public/skills/risk-metrics-calculation/SKILL.md
@@ -1,6 +1,8 @@
---
name: risk-metrics-calculation
-description: Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.
+description: "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems."
+risk: unknown
+source: community
---
# Risk Metrics Calculation
diff --git a/web-app/public/skills/ruby-pro/SKILL.md b/web-app/public/skills/ruby-pro/SKILL.md
index 5aca2de9..d8296a73 100644
--- a/web-app/public/skills/ruby-pro/SKILL.md
+++ b/web-app/public/skills/ruby-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: ruby-pro
-description: Write idiomatic Ruby code with metaprogramming, Rails patterns, and
+description: "Write idiomatic Ruby code with metaprogramming, Rails patterns, and"
performance optimization. Specializes in Ruby on Rails, gem development, and
testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or
complex Ruby features.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/rust-async-patterns/SKILL.md b/web-app/public/skills/rust-async-patterns/SKILL.md
index cc29e4d9..c4659954 100644
--- a/web-app/public/skills/rust-async-patterns/SKILL.md
+++ b/web-app/public/skills/rust-async-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: rust-async-patterns
-description: Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
+description: "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code."
+risk: unknown
+source: community
---
# Rust Async Patterns
diff --git a/web-app/public/skills/rust-pro/SKILL.md b/web-app/public/skills/rust-pro/SKILL.md
index c1fee2b4..56b57f23 100644
--- a/web-app/public/skills/rust-pro/SKILL.md
+++ b/web-app/public/skills/rust-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: rust-pro
-description: Master Rust 1.75+ with modern async patterns, advanced type system
+description: "Master Rust 1.75+ with modern async patterns, advanced type system"
features, and production-ready systems programming. Expert in the latest Rust
ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for
Rust development, performance optimization, or systems programming.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.
diff --git a/web-app/public/skills/saga-orchestration/SKILL.md b/web-app/public/skills/saga-orchestration/SKILL.md
index 4f2412be..7241bec1 100644
--- a/web-app/public/skills/saga-orchestration/SKILL.md
+++ b/web-app/public/skills/saga-orchestration/SKILL.md
@@ -1,6 +1,8 @@
---
name: saga-orchestration
-description: Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.
+description: "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running..."
+risk: unknown
+source: community
---
# Saga Orchestration
diff --git a/web-app/public/skills/saga-orchestration/resources/implementation-playbook.md b/web-app/public/skills/saga-orchestration/resources/implementation-playbook.md
new file mode 100644
index 00000000..d5c3cd3e
--- /dev/null
+++ b/web-app/public/skills/saga-orchestration/resources/implementation-playbook.md
@@ -0,0 +1,26 @@
+# Saga Orchestration Playbook
+
+## When to choose orchestration vs choreography
+
+- Choose orchestration when business flow visibility and centralized control are required.
+- Choose choreography when autonomy is high and coupling is low.
+
+## Saga design checklist
+
+- Define explicit saga state machine.
+- Define timeout policy per step.
+- Define compensation action for each irreversible step.
+- Use idempotency keys for command handling.
+- Store correlation IDs across all events and logs.
+
+## Failure handling
+
+- Retry transient failures with bounded exponential backoff.
+- Escalate non-recoverable failures to compensation state.
+- Capture operator-visible failure reason and current step.
+
+## Verification
+
+- Simulate failure at every step and confirm compensation path.
+- Validate duplicate message handling.
+- Validate recovery from orchestrator restart.
diff --git a/web-app/public/skills/sales-automator/SKILL.md b/web-app/public/skills/sales-automator/SKILL.md
index a842255d..2978913c 100644
--- a/web-app/public/skills/sales-automator/SKILL.md
+++ b/web-app/public/skills/sales-automator/SKILL.md
@@ -1,10 +1,12 @@
---
name: sales-automator
-description: Draft cold emails, follow-ups, and proposal templates. Creates
+description: "Draft cold emails, follow-ups, and proposal templates. Creates"
pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales
outreach or lead nurturing.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/salesforce-automation/SKILL.md b/web-app/public/skills/salesforce-automation/SKILL.md
index 1fd9fbff..a40d0369 100644
--- a/web-app/public/skills/salesforce-automation/SKILL.md
+++ b/web-app/public/skills/salesforce-automation/SKILL.md
@@ -3,6 +3,8 @@ name: salesforce-automation
description: "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Salesforce Automation via Rube MCP
@@ -188,3 +190,6 @@ SELECT Id, Name FROM Opportunity WHERE CloseDate = NEXT_MONTH
| Custom objects | SALESFORCE_GET_ALL_CUSTOM_OBJECTS | (none) |
| Create record | SALESFORCE_CREATE_A_RECORD | object_type, fields |
| Transfer ownership | SALESFORCE_MASS_TRANSFER_OWNERSHIP | records, new_owner |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/salesforce-development/SKILL.md b/web-app/public/skills/salesforce-development/SKILL.md
index 0a0e8a55..bf0df8ad 100644
--- a/web-app/public/skills/salesforce-development/SKILL.md
+++ b/web-app/public/skills/salesforce-development/SKILL.md
@@ -1,7 +1,8 @@
---
name: salesforce-development
-description: "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd generation packages (2GP). Use when: salesforce, sfdc, apex, lwc, lightning web components."
+description: "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Salesforce Development
@@ -49,3 +50,6 @@ per transaction, 1 child job when chaining.
| Issue | high | See docs |
| Issue | high | See docs |
| Issue | critical | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/sast-configuration/SKILL.md b/web-app/public/skills/sast-configuration/SKILL.md
index 2c0bbe9a..80c1eb6a 100644
--- a/web-app/public/skills/sast-configuration/SKILL.md
+++ b/web-app/public/skills/sast-configuration/SKILL.md
@@ -1,6 +1,8 @@
---
name: sast-configuration
-description: Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.
+description: "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut..."
+risk: unknown
+source: community
---
# SAST Configuration
@@ -85,15 +87,15 @@ codeql database create mydb --language=python
## Reference Documentation
-- [Semgrep Rule Creation](references/semgrep-rules.md) - Pattern-based security rule development
-- [SonarQube Configuration](references/sonarqube-config.md) - Quality gates and profiles
-- [CodeQL Setup Guide](references/codeql-setup.md) - Query development and workflows
+- Semgrep Rule Creation - Pattern-based security rule development
+- SonarQube Configuration - Quality gates and profiles
+- CodeQL Setup Guide - Query development and workflows
## Templates & Assets
-- [semgrep-config.yml](assets/semgrep-config.yml) - Production-ready Semgrep configuration
-- [sonarqube-settings.xml](assets/sonarqube-settings.xml) - SonarQube quality profile template
-- [run-sast.sh](scripts/run-sast.sh) - Automated SAST execution script
+- semgrep-config.yml - Production-ready Semgrep configuration
+- sonarqube-settings.xml - SonarQube quality profile template
+- run-sast.sh - Automated SAST execution script
## Integration Patterns
@@ -190,9 +192,9 @@ semgrep --config p/pci-dss --json -o pci-scan-results.json
## Related Skills
-- [OWASP Top 10 Checklist](../owasp-top10-checklist/SKILL.md)
-- [Container Security](../container-security/SKILL.md)
-- [Dependency Scanning](../dependency-scanning/SKILL.md)
+- OWASP Top 10 Checklist
+- Container Security
+- Dependency Scanning
## Tool Comparison
diff --git a/web-app/public/skills/scala-pro/SKILL.md b/web-app/public/skills/scala-pro/SKILL.md
index 14dc150c..6845992a 100644
--- a/web-app/public/skills/scala-pro/SKILL.md
+++ b/web-app/public/skills/scala-pro/SKILL.md
@@ -1,12 +1,14 @@
---
name: scala-pro
-description: Master enterprise-grade Scala development with functional
+description: "Master enterprise-grade Scala development with functional"
programming, distributed systems, and big data processing. Expert in Apache
Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use
PROACTIVELY for Scala system design, performance optimization, or enterprise
integration.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/scanning-tools/SKILL.md b/web-app/public/skills/scanning-tools/SKILL.md
index b784b60f..2e3fa459 100644
--- a/web-app/public/skills/scanning-tools/SKILL.md
+++ b/web-app/public/skills/scanning-tools/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Security Scanning Tools
-description: This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wireless networks", "detect malware", "check cloud security", or "evaluate system compliance". It provides comprehensive guidance on security scanning tools and methodologies.
+name: scanning-tools
+description: "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Security Scanning Tools
@@ -587,3 +589,6 @@ gvm-cli socket --xml ''
3. Add custom injection points
4. Use multiple tools for coverage
5. Perform manual testing
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/schema-markup/SKILL.md b/web-app/public/skills/schema-markup/SKILL.md
index 76bc067a..98474969 100644
--- a/web-app/public/skills/schema-markup/SKILL.md
+++ b/web-app/public/skills/schema-markup/SKILL.md
@@ -1,12 +1,14 @@
---
name: schema-markup
-description: >
+description: ">"
Design, validate, and optimize schema.org structured data for eligibility,
correctness, and measurable SEO impact. Use when the user wants to add, fix,
audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates
whether schema should be implemented, what types are valid, and how to deploy
safely according to Google guidelines.
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
---
@@ -358,3 +360,6 @@ Where and how to add it
- **seo-audit** – Full SEO review including schema
- **programmatic-seo** – Templated schema at scale
- **analytics-tracking** – Measure rich result impact
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/screen-reader-testing/SKILL.md b/web-app/public/skills/screen-reader-testing/SKILL.md
index cca655ab..47fbe0a3 100644
--- a/web-app/public/skills/screen-reader-testing/SKILL.md
+++ b/web-app/public/skills/screen-reader-testing/SKILL.md
@@ -1,6 +1,8 @@
---
name: screen-reader-testing
-description: Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
+description: "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp..."
+risk: unknown
+source: community
---
# Screen Reader Testing
diff --git a/web-app/public/skills/scroll-experience/SKILL.md b/web-app/public/skills/scroll-experience/SKILL.md
index ee4c569f..48d29ddf 100644
--- a/web-app/public/skills/scroll-experience/SKILL.md
+++ b/web-app/public/skills/scroll-experience/SKILL.md
@@ -1,7 +1,8 @@
---
name: scroll-experience
-description: "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website."
+description: "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Scroll Experience
@@ -261,3 +262,6 @@ Graceful degradation.
## Related Skills
Works well with: `3d-web-experience`, `frontend`, `ui-design`, `landing-page-design`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/search-specialist/SKILL.md b/web-app/public/skills/search-specialist/SKILL.md
index 6c06df41..75dbee62 100644
--- a/web-app/public/skills/search-specialist/SKILL.md
+++ b/web-app/public/skills/search-specialist/SKILL.md
@@ -6,6 +6,8 @@ description: Expert web researcher using advanced search techniques and
for deep research, information gathering, or trend analysis.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/secrets-management/SKILL.md b/web-app/public/skills/secrets-management/SKILL.md
index bcaea66b..f993260a 100644
--- a/web-app/public/skills/secrets-management/SKILL.md
+++ b/web-app/public/skills/secrets-management/SKILL.md
@@ -1,6 +1,8 @@
---
name: secrets-management
-description: Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
+description: "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ..."
+risk: unknown
+source: community
---
# Secrets Management
diff --git a/web-app/public/skills/security-audit/SKILL.md b/web-app/public/skills/security-audit/SKILL.md
new file mode 100644
index 00000000..ca38fa7f
--- /dev/null
+++ b/web-app/public/skills/security-audit/SKILL.md
@@ -0,0 +1,218 @@
+---
+name: security-audit
+description: "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening."
+source: personal
+risk: safe
+domain: security
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Security Auditing Workflow Bundle
+
+## Overview
+
+Comprehensive security auditing workflow for web applications, APIs, and infrastructure. This bundle orchestrates skills for penetration testing, vulnerability assessment, security scanning, and remediation.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Performing security audits on web applications
+- Testing API security
+- Conducting penetration tests
+- Scanning for vulnerabilities
+- Hardening application security
+- Compliance security assessments
+
+## Workflow Phases
+
+### Phase 1: Reconnaissance
+
+#### Skills to Invoke
+- `scanning-tools` - Security scanning
+- `shodan-reconnaissance` - Shodan searches
+- `top-web-vulnerabilities` - OWASP Top 10
+
+#### Actions
+1. Identify target scope
+2. Gather intelligence
+3. Map attack surface
+4. Identify technologies
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @scanning-tools to perform initial reconnaissance
+```
+
+```
+Use @shodan-reconnaissance to find exposed services
+```
+
+### Phase 2: Vulnerability Scanning
+
+#### Skills to Invoke
+- `vulnerability-scanner` - Vulnerability analysis
+- `security-scanning-security-sast` - Static analysis
+- `security-scanning-security-dependencies` - Dependency scanning
+
+#### Actions
+1. Run automated scanners
+2. Perform static analysis
+3. Scan dependencies
+4. Identify misconfigurations
+5. Document vulnerabilities
+
+#### Copy-Paste Prompts
+```
+Use @vulnerability-scanner to scan for OWASP Top 10 vulnerabilities
+```
+
+```
+Use @security-scanning-security-dependencies to audit dependencies
+```
+
+### Phase 3: Web Application Testing
+
+#### Skills to Invoke
+- `top-web-vulnerabilities` - OWASP vulnerabilities
+- `sql-injection-testing` - SQL injection
+- `xss-html-injection` - XSS testing
+- `broken-authentication` - Authentication testing
+- `idor-testing` - IDOR testing
+- `file-path-traversal` - Path traversal
+- `burp-suite-testing` - Burp Suite testing
+
+#### Actions
+1. Test for injection flaws
+2. Test authentication mechanisms
+3. Test session management
+4. Test access controls
+5. Test input validation
+6. Test security headers
+
+#### Copy-Paste Prompts
+```
+Use @sql-injection-testing to test for SQL injection vulnerabilities
+```
+
+```
+Use @xss-html-injection to test for cross-site scripting
+```
+
+```
+Use @broken-authentication to test authentication security
+```
+
+### Phase 4: API Security Testing
+
+#### Skills to Invoke
+- `api-fuzzing-bug-bounty` - API fuzzing
+- `api-security-best-practices` - API security
+
+#### Actions
+1. Enumerate API endpoints
+2. Test authentication/authorization
+3. Test rate limiting
+4. Test input validation
+5. Test error handling
+6. Document API vulnerabilities
+
+#### Copy-Paste Prompts
+```
+Use @api-fuzzing-bug-bounty to fuzz API endpoints
+```
+
+### Phase 5: Penetration Testing
+
+#### Skills to Invoke
+- `pentest-commands` - Penetration testing commands
+- `pentest-checklist` - Pentest planning
+- `ethical-hacking-methodology` - Ethical hacking
+- `metasploit-framework` - Metasploit
+
+#### Actions
+1. Plan penetration test
+2. Execute attack scenarios
+3. Exploit vulnerabilities
+4. Document proof of concept
+5. Assess impact
+
+#### Copy-Paste Prompts
+```
+Use @pentest-checklist to plan penetration test
+```
+
+```
+Use @pentest-commands to execute penetration testing
+```
+
+### Phase 6: Security Hardening
+
+#### Skills to Invoke
+- `security-scanning-security-hardening` - Security hardening
+- `auth-implementation-patterns` - Authentication
+- `api-security-best-practices` - API security
+
+#### Actions
+1. Implement security controls
+2. Configure security headers
+3. Set up authentication
+4. Implement authorization
+5. Configure logging
+6. Apply patches
+
+#### Copy-Paste Prompts
+```
+Use @security-scanning-security-hardening to harden application security
+```
+
+### Phase 7: Reporting
+
+#### Skills to Invoke
+- `reporting-standards` - Security reporting
+
+#### Actions
+1. Document findings
+2. Assess risk levels
+3. Provide remediation steps
+4. Create executive summary
+5. Generate technical report
+
+## Security Testing Checklist
+
+### OWASP Top 10
+- [ ] Injection (SQL, NoSQL, OS, LDAP)
+- [ ] Broken Authentication
+- [ ] Sensitive Data Exposure
+- [ ] XML External Entities (XXE)
+- [ ] Broken Access Control
+- [ ] Security Misconfiguration
+- [ ] Cross-Site Scripting (XSS)
+- [ ] Insecure Deserialization
+- [ ] Using Components with Known Vulnerabilities
+- [ ] Insufficient Logging & Monitoring
+
+### API Security
+- [ ] Authentication mechanisms
+- [ ] Authorization checks
+- [ ] Rate limiting
+- [ ] Input validation
+- [ ] Error handling
+- [ ] Security headers
+
+## Quality Gates
+
+- [ ] All planned tests executed
+- [ ] Vulnerabilities documented
+- [ ] Proof of concepts captured
+- [ ] Risk assessments completed
+- [ ] Remediation steps provided
+- [ ] Report generated
+
+## Related Workflow Bundles
+
+- `development` - Secure development practices
+- `wordpress` - WordPress security
+- `cloud-devops` - Cloud security
+- `testing-qa` - Security testing
diff --git a/web-app/public/skills/security-auditor/SKILL.md b/web-app/public/skills/security-auditor/SKILL.md
index 18b6c2be..8704c428 100644
--- a/web-app/public/skills/security-auditor/SKILL.md
+++ b/web-app/public/skills/security-auditor/SKILL.md
@@ -1,6 +1,6 @@
---
name: security-auditor
-description: Expert security auditor specializing in DevSecOps, comprehensive
+description: "Expert security auditor specializing in DevSecOps, comprehensive"
cybersecurity, and compliance frameworks. Masters vulnerability assessment,
threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud
security, and security automation. Handles DevSecOps integration, compliance
@@ -8,6 +8,8 @@ description: Expert security auditor specializing in DevSecOps, comprehensive
DevSecOps, or compliance implementation.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.
diff --git a/web-app/public/skills/security-compliance-compliance-check/SKILL.md b/web-app/public/skills/security-compliance-compliance-check/SKILL.md
index 984160f9..15f23a86 100644
--- a/web-app/public/skills/security-compliance-compliance-check/SKILL.md
+++ b/web-app/public/skills/security-compliance-compliance-check/SKILL.md
@@ -1,6 +1,8 @@
---
name: security-compliance-compliance-check
-description: "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide implementation guidance."
+description: "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im..."
+risk: unknown
+source: community
---
# Regulatory Compliance Check
diff --git a/web-app/public/skills/security-requirement-extraction/SKILL.md b/web-app/public/skills/security-requirement-extraction/SKILL.md
index d53a743b..c38c1cb1 100644
--- a/web-app/public/skills/security-requirement-extraction/SKILL.md
+++ b/web-app/public/skills/security-requirement-extraction/SKILL.md
@@ -1,6 +1,8 @@
---
name: security-requirement-extraction
-description: Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
+description: "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases."
+risk: unknown
+source: community
---
# Security Requirement Extraction
diff --git a/web-app/public/skills/security-scanning-security-dependencies/SKILL.md b/web-app/public/skills/security-scanning-security-dependencies/SKILL.md
index f6d0ab93..78761f47 100644
--- a/web-app/public/skills/security-scanning-security-dependencies/SKILL.md
+++ b/web-app/public/skills/security-scanning-security-dependencies/SKILL.md
@@ -1,6 +1,8 @@
---
name: security-scanning-security-dependencies
-description: "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, assess risks, and recommend remediation."
+description: "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass..."
+risk: unknown
+source: community
---
# Dependency Vulnerability Scanning
diff --git a/web-app/public/skills/security-scanning-security-hardening/SKILL.md b/web-app/public/skills/security-scanning-security-hardening/SKILL.md
index d24716cd..1ccc32f9 100644
--- a/web-app/public/skills/security-scanning-security-hardening/SKILL.md
+++ b/web-app/public/skills/security-scanning-security-hardening/SKILL.md
@@ -1,6 +1,8 @@
---
name: security-scanning-security-hardening
description: "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls."
+risk: unknown
+source: community
---
Implement comprehensive security hardening with defense-in-depth strategy through coordinated multi-agent orchestration:
diff --git a/web-app/public/skills/security-scanning-security-sast/SKILL.md b/web-app/public/skills/security-scanning-security-sast/SKILL.md
index 6431b452..8f15568d 100644
--- a/web-app/public/skills/security-scanning-security-sast/SKILL.md
+++ b/web-app/public/skills/security-scanning-security-sast/SKILL.md
@@ -1,12 +1,14 @@
---
name: security-scanning-security-sast
-description: Static Application Security Testing (SAST) for code vulnerability
+description: "Static Application Security Testing (SAST) for code vulnerability"
analysis across multiple languages and frameworks
metadata:
globs: "**/*.py, **/*.js, **/*.ts, **/*.java, **/*.rb, **/*.go, **/*.rs, **/*.php"
keywords: sast, static analysis, code security, vulnerability scanning, bandit,
semgrep, eslint, sonarqube, codeql, security patterns, code review, ast
analysis
+risk: unknown
+source: community
---
# SAST Security Plugin
diff --git a/web-app/public/skills/security/aws-compliance-checker/SKILL.md b/web-app/public/skills/security/aws-compliance-checker/SKILL.md
new file mode 100644
index 00000000..b15bea11
--- /dev/null
+++ b/web-app/public/skills/security/aws-compliance-checker/SKILL.md
@@ -0,0 +1,516 @@
+---
+name: aws-compliance-checker
+description: Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks
+risk: safe
+source: community
+category: security
+tags: [aws, compliance, audit, cis, pci-dss, hipaa, kiro-cli]
+---
+
+# AWS Compliance Checker
+
+Automated compliance validation against industry standards including CIS AWS Foundations, PCI-DSS, HIPAA, and SOC 2.
+
+## When to Use
+
+Use this skill when you need to validate AWS compliance against industry standards, prepare for audits, or maintain continuous compliance monitoring.
+
+## Supported Frameworks
+
+**CIS AWS Foundations Benchmark**
+- Identity and Access Management
+- Logging and Monitoring
+- Networking
+- Data Protection
+
+**PCI-DSS (Payment Card Industry)**
+- Network security
+- Access controls
+- Encryption
+- Monitoring and logging
+
+**HIPAA (Healthcare)**
+- Access controls
+- Audit controls
+- Data encryption
+- Transmission security
+
+**SOC 2**
+- Security
+- Availability
+- Confidentiality
+- Privacy
+
+## CIS AWS Foundations Checks
+
+### Identity & Access Management (1.x)
+
+```bash
+#!/bin/bash
+# cis-iam-checks.sh
+
+echo "=== CIS IAM Compliance Checks ==="
+
+# 1.1: Root account usage
+echo "1.1: Checking root account usage..."
+root_usage=$(aws iam get-credential-report --output text | \
+ awk -F, 'NR==2 {print $5,$11}')
+echo " Root password last used: $root_usage"
+
+# 1.2: MFA on root account
+echo "1.2: Checking root MFA..."
+root_mfa=$(aws iam get-account-summary \
+ --query 'SummaryMap.AccountMFAEnabled' --output text)
+echo " Root MFA enabled: $root_mfa"
+
+# 1.3: Unused credentials
+echo "1.3: Checking for unused credentials (>90 days)..."
+aws iam get-credential-report --output text | \
+ awk -F, 'NR>1 {
+ if ($5 != "N/A" && $5 != "no_information") {
+ cmd = "date -d \"" $5 "\" +%s"
+ cmd | getline last_used
+ close(cmd)
+ now = systime()
+ days = (now - last_used) / 86400
+ if (days > 90) print " ⚠️ " $1 ": " int(days) " days inactive"
+ }
+ }'
+
+# 1.4: Access keys rotated
+echo "1.4: Checking access key age..."
+aws iam list-users --query 'Users[*].UserName' --output text | \
+while read user; do
+ aws iam list-access-keys --user-name "$user" \
+ --query 'AccessKeyMetadata[*].[AccessKeyId,CreateDate]' \
+ --output text | \
+ while read key_id create_date; do
+ age_days=$(( ($(date +%s) - $(date -d "$create_date" +%s)) / 86400 ))
+ if [ $age_days -gt 90 ]; then
+ echo " ⚠️ $user: Key $key_id is $age_days days old"
+ fi
+ done
+done
+
+# 1.5-1.11: Password policy
+echo "1.5-1.11: Checking password policy..."
+policy=$(aws iam get-account-password-policy 2>&1)
+if echo "$policy" | grep -q "NoSuchEntity"; then
+ echo " ❌ No password policy configured"
+else
+ echo " ✓ Password policy exists"
+ echo "$policy" | jq '.PasswordPolicy | {
+ MinimumPasswordLength,
+ RequireSymbols,
+ RequireNumbers,
+ RequireUppercaseCharacters,
+ RequireLowercaseCharacters,
+ MaxPasswordAge,
+ PasswordReusePrevention
+ }'
+fi
+
+# 1.12-1.14: MFA for IAM users
+echo "1.12-1.14: Checking IAM user MFA..."
+aws iam get-credential-report --output text | \
+ awk -F, 'NR>1 && $4=="false" {print " ⚠️ " $1 ": No MFA"}'
+```
+
+### Logging (2.x)
+
+```bash
+#!/bin/bash
+# cis-logging-checks.sh
+
+echo "=== CIS Logging Compliance Checks ==="
+
+# 2.1: CloudTrail enabled
+echo "2.1: Checking CloudTrail..."
+trails=$(aws cloudtrail describe-trails \
+ --query 'trailList[*].[Name,IsMultiRegionTrail,LogFileValidationEnabled]' \
+ --output text)
+
+if [ -z "$trails" ]; then
+ echo " ❌ No CloudTrail configured"
+else
+ echo "$trails" | while read name multi_region validation; do
+ echo " Trail: $name"
+ echo " Multi-region: $multi_region"
+ echo " Log validation: $validation"
+
+ # Check if logging
+ status=$(aws cloudtrail get-trail-status --name "$name" \
+ --query 'IsLogging' --output text)
+ echo " Is logging: $status"
+ done
+fi
+
+# 2.2: CloudTrail log file validation
+echo "2.2: Checking log file validation..."
+aws cloudtrail describe-trails \
+ --query 'trailList[?LogFileValidationEnabled==`false`].Name' \
+ --output text | \
+while read trail; do
+ echo " ⚠️ $trail: Log validation disabled"
+done
+
+# 2.3: S3 bucket for CloudTrail
+echo "2.3: Checking CloudTrail S3 bucket access..."
+aws cloudtrail describe-trails \
+ --query 'trailList[*].S3BucketName' --output text | \
+while read bucket; do
+ public=$(aws s3api get-bucket-acl --bucket "$bucket" 2>&1 | \
+ grep -c "AllUsers")
+ if [ "$public" -gt 0 ]; then
+ echo " ❌ $bucket: Publicly accessible"
+ else
+ echo " ✓ $bucket: Not public"
+ fi
+done
+
+# 2.4: CloudTrail integrated with CloudWatch Logs
+echo "2.4: Checking CloudWatch Logs integration..."
+aws cloudtrail describe-trails \
+ --query 'trailList[*].[Name,CloudWatchLogsLogGroupArn]' \
+ --output text | \
+while read name log_group; do
+ if [ "$log_group" = "None" ]; then
+ echo " ⚠️ $name: Not integrated with CloudWatch Logs"
+ else
+ echo " ✓ $name: Integrated with CloudWatch"
+ fi
+done
+
+# 2.5: AWS Config enabled
+echo "2.5: Checking AWS Config..."
+recorders=$(aws configservice describe-configuration-recorders \
+ --query 'ConfigurationRecorders[*].name' --output text)
+
+if [ -z "$recorders" ]; then
+ echo " ❌ AWS Config not enabled"
+else
+ echo " ✓ AWS Config enabled: $recorders"
+fi
+
+# 2.6: S3 bucket logging
+echo "2.6: Checking S3 bucket logging..."
+aws s3api list-buckets --query 'Buckets[*].Name' --output text | \
+while read bucket; do
+ logging=$(aws s3api get-bucket-logging --bucket "$bucket" 2>&1)
+ if ! echo "$logging" | grep -q "LoggingEnabled"; then
+ echo " ⚠️ $bucket: Access logging disabled"
+ fi
+done
+
+# 2.7: VPC Flow Logs
+echo "2.7: Checking VPC Flow Logs..."
+aws ec2 describe-vpcs --query 'Vpcs[*].VpcId' --output text | \
+while read vpc; do
+ flow_logs=$(aws ec2 describe-flow-logs \
+ --filter "Name=resource-id,Values=$vpc" \
+ --query 'FlowLogs[*].FlowLogId' --output text)
+ if [ -z "$flow_logs" ]; then
+ echo " ⚠️ $vpc: No flow logs enabled"
+ else
+ echo " ✓ $vpc: Flow logs enabled"
+ fi
+done
+```
+
+### Monitoring (3.x)
+
+```bash
+#!/bin/bash
+# cis-monitoring-checks.sh
+
+echo "=== CIS Monitoring Compliance Checks ==="
+
+# Check for required CloudWatch metric filters and alarms
+required_filters=(
+ "unauthorized-api-calls"
+ "no-mfa-console-signin"
+ "root-usage"
+ "iam-changes"
+ "cloudtrail-changes"
+ "console-signin-failures"
+ "cmk-changes"
+ "s3-bucket-policy-changes"
+ "aws-config-changes"
+ "security-group-changes"
+ "nacl-changes"
+ "network-gateway-changes"
+ "route-table-changes"
+ "vpc-changes"
+)
+
+log_group=$(aws cloudtrail describe-trails \
+ --query 'trailList[0].CloudWatchLogsLogGroupArn' \
+ --output text | cut -d: -f7)
+
+if [ -z "$log_group" ] || [ "$log_group" = "None" ]; then
+ echo " ❌ CloudTrail not integrated with CloudWatch Logs"
+else
+ echo "Checking metric filters for log group: $log_group"
+
+ existing_filters=$(aws logs describe-metric-filters \
+ --log-group-name "$log_group" \
+ --query 'metricFilters[*].filterName' --output text)
+
+ for filter in "${required_filters[@]}"; do
+ if echo "$existing_filters" | grep -q "$filter"; then
+ echo " ✓ $filter: Configured"
+ else
+ echo " ⚠️ $filter: Missing"
+ fi
+ done
+fi
+```
+
+### Networking (4.x)
+
+```bash
+#!/bin/bash
+# cis-networking-checks.sh
+
+echo "=== CIS Networking Compliance Checks ==="
+
+# 4.1: No security groups allow 0.0.0.0/0 ingress to port 22
+echo "4.1: Checking SSH access (port 22)..."
+aws ec2 describe-security-groups \
+ --query 'SecurityGroups[*].[GroupId,GroupName,IpPermissions]' \
+ --output json | \
+jq -r '.[] | select(.[2][]? |
+ select(.FromPort == 22 and .IpRanges[]?.CidrIp == "0.0.0.0/0")) |
+ " ⚠️ \(.[0]): \(.[1]) allows SSH from 0.0.0.0/0"'
+
+# 4.2: No security groups allow 0.0.0.0/0 ingress to port 3389
+echo "4.2: Checking RDP access (port 3389)..."
+aws ec2 describe-security-groups \
+ --query 'SecurityGroups[*].[GroupId,GroupName,IpPermissions]' \
+ --output json | \
+jq -r '.[] | select(.[2][]? |
+ select(.FromPort == 3389 and .IpRanges[]?.CidrIp == "0.0.0.0/0")) |
+ " ⚠️ \(.[0]): \(.[1]) allows RDP from 0.0.0.0/0"'
+
+# 4.3: Default security group restricts all traffic
+echo "4.3: Checking default security groups..."
+aws ec2 describe-security-groups \
+ --filters Name=group-name,Values=default \
+ --query 'SecurityGroups[*].[GroupId,IpPermissions,IpPermissionsEgress]' \
+ --output json | \
+jq -r '.[] | select((.[1] | length) > 0 or (.[2] | length) > 1) |
+ " ⚠️ \(.[0]): Default SG has rules"'
+```
+
+## PCI-DSS Compliance Checks
+
+```python
+#!/usr/bin/env python3
+# pci-dss-checker.py
+
+import boto3
+
+def check_pci_compliance():
+ """Check PCI-DSS requirements"""
+
+ ec2 = boto3.client('ec2')
+ rds = boto3.client('rds')
+ s3 = boto3.client('s3')
+
+ issues = []
+
+ # Requirement 1: Network security
+ sgs = ec2.describe_security_groups()
+ for sg in sgs['SecurityGroups']:
+ for perm in sg.get('IpPermissions', []):
+ for ip_range in perm.get('IpRanges', []):
+ if ip_range.get('CidrIp') == '0.0.0.0/0':
+ issues.append(f"PCI 1.2: {sg['GroupId']} open to internet")
+
+ # Requirement 2: Secure configurations
+ # Check for default passwords, etc.
+
+ # Requirement 3: Protect cardholder data
+ volumes = ec2.describe_volumes()
+ for vol in volumes['Volumes']:
+ if not vol['Encrypted']:
+ issues.append(f"PCI 3.4: Volume {vol['VolumeId']} not encrypted")
+
+ # Requirement 4: Encrypt transmission
+ # Check for SSL/TLS on load balancers
+
+ # Requirement 8: Access controls
+ iam = boto3.client('iam')
+ users = iam.list_users()
+ for user in users['Users']:
+ mfa = iam.list_mfa_devices(UserName=user['UserName'])
+ if not mfa['MFADevices']:
+ issues.append(f"PCI 8.3: {user['UserName']} no MFA")
+
+ # Requirement 10: Logging
+ cloudtrail = boto3.client('cloudtrail')
+ trails = cloudtrail.describe_trails()
+ if not trails['trailList']:
+ issues.append("PCI 10.1: No CloudTrail enabled")
+
+ return issues
+
+if __name__ == "__main__":
+ print("PCI-DSS Compliance Check")
+ print("=" * 50)
+
+ issues = check_pci_compliance()
+
+ if not issues:
+ print("✓ No PCI-DSS issues found")
+ else:
+ print(f"Found {len(issues)} issues:\n")
+ for issue in issues:
+ print(f" ⚠️ {issue}")
+```
+
+## HIPAA Compliance Checks
+
+```bash
+#!/bin/bash
+# hipaa-checker.sh
+
+echo "=== HIPAA Compliance Checks ==="
+
+# Access Controls (164.308(a)(3))
+echo "Access Controls:"
+aws iam get-credential-report --output text | \
+ awk -F, 'NR>1 && $4=="false" {print " ⚠️ " $1 ": No MFA (164.312(a)(2)(i))"}'
+
+# Audit Controls (164.312(b))
+echo ""
+echo "Audit Controls:"
+trails=$(aws cloudtrail describe-trails --query 'trailList[*].Name' --output text)
+if [ -z "$trails" ]; then
+ echo " ❌ No CloudTrail (164.312(b))"
+else
+ echo " ✓ CloudTrail enabled"
+fi
+
+# Encryption (164.312(a)(2)(iv))
+echo ""
+echo "Encryption at Rest:"
+aws ec2 describe-volumes \
+ --query 'Volumes[?Encrypted==`false`].VolumeId' \
+ --output text | \
+while read vol; do
+ echo " ⚠️ $vol: Not encrypted (164.312(a)(2)(iv))"
+done
+
+aws rds describe-db-instances \
+ --query 'DBInstances[?StorageEncrypted==`false`].DBInstanceIdentifier' \
+ --output text | \
+while read db; do
+ echo " ⚠️ $db: Not encrypted (164.312(a)(2)(iv))"
+done
+
+# Transmission Security (164.312(e)(1))
+echo ""
+echo "Transmission Security:"
+echo " Check: All data in transit uses TLS 1.2+"
+```
+
+## Automated Compliance Reporting
+
+```python
+#!/usr/bin/env python3
+# compliance-report.py
+
+import boto3
+import json
+from datetime import datetime
+
+def generate_compliance_report(framework='cis'):
+ """Generate comprehensive compliance report"""
+
+ report = {
+ 'framework': framework,
+ 'generated': datetime.now().isoformat(),
+ 'checks': [],
+ 'summary': {
+ 'total': 0,
+ 'passed': 0,
+ 'failed': 0,
+ 'score': 0
+ }
+ }
+
+ # Run all checks based on framework
+ if framework == 'cis':
+ checks = run_cis_checks()
+ elif framework == 'pci':
+ checks = run_pci_checks()
+ elif framework == 'hipaa':
+ checks = run_hipaa_checks()
+
+ report['checks'] = checks
+ report['summary']['total'] = len(checks)
+ report['summary']['passed'] = sum(1 for c in checks if c['status'] == 'PASS')
+ report['summary']['failed'] = report['summary']['total'] - report['summary']['passed']
+ report['summary']['score'] = (report['summary']['passed'] / report['summary']['total']) * 100
+
+ return report
+
+def run_cis_checks():
+ # Implement CIS checks
+ return []
+
+def run_pci_checks():
+ # Implement PCI checks
+ return []
+
+def run_hipaa_checks():
+ # Implement HIPAA checks
+ return []
+
+if __name__ == "__main__":
+ import sys
+ framework = sys.argv[1] if len(sys.argv) > 1 else 'cis'
+
+ report = generate_compliance_report(framework)
+
+ print(f"\n{framework.upper()} Compliance Report")
+ print("=" * 50)
+ print(f"Score: {report['summary']['score']:.1f}%")
+ print(f"Passed: {report['summary']['passed']}/{report['summary']['total']}")
+ print(f"Failed: {report['summary']['failed']}/{report['summary']['total']}")
+
+ # Save to file
+ with open(f'compliance-{framework}-{datetime.now().strftime("%Y%m%d")}.json', 'w') as f:
+ json.dump(report, f, indent=2)
+```
+
+## Example Prompts
+
+- "Run CIS AWS Foundations compliance check"
+- "Generate a PCI-DSS compliance report"
+- "Check HIPAA compliance for my AWS account"
+- "Audit against SOC 2 requirements"
+- "Create a compliance dashboard"
+
+## Best Practices
+
+- Run compliance checks weekly
+- Automate with Lambda/EventBridge
+- Track compliance trends over time
+- Document exceptions with justification
+- Integrate with AWS Security Hub
+- Use AWS Config Rules for continuous monitoring
+
+## Kiro CLI Integration
+
+```bash
+kiro-cli chat "Use aws-compliance-checker to run CIS benchmark"
+kiro-cli chat "Generate PCI-DSS report with aws-compliance-checker"
+```
+
+## Additional Resources
+
+- [CIS AWS Foundations Benchmark](https://www.cisecurity.org/benchmark/amazon_web_services)
+- [AWS Security Hub](https://aws.amazon.com/security-hub/)
+- [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/)
diff --git a/web-app/public/skills/security/aws-iam-best-practices/SKILL.md b/web-app/public/skills/security/aws-iam-best-practices/SKILL.md
new file mode 100644
index 00000000..381c8fa0
--- /dev/null
+++ b/web-app/public/skills/security/aws-iam-best-practices/SKILL.md
@@ -0,0 +1,397 @@
+---
+name: aws-iam-best-practices
+description: IAM policy review, hardening, and least privilege implementation
+risk: safe
+source: community
+category: security
+tags: [aws, iam, security, access-control, kiro-cli, least-privilege]
+---
+
+# AWS IAM Best Practices
+
+Review and harden IAM policies following AWS security best practices and least privilege principles.
+
+## When to Use
+
+Use this skill when you need to review IAM policies, implement least privilege access, or harden IAM security.
+
+## Core Principles
+
+**Least Privilege**
+- Grant minimum permissions needed
+- Use managed policies when possible
+- Avoid wildcard (*) permissions
+- Regular access reviews
+
+**Defense in Depth**
+- Enable MFA for all users
+- Use IAM roles instead of access keys
+- Implement service control policies (SCPs)
+- Enable CloudTrail for audit
+
+**Separation of Duties**
+- Separate admin and user roles
+- Use different roles for different environments
+- Implement approval workflows
+- Regular permission audits
+
+## IAM Security Checks
+
+### Find Overly Permissive Policies
+
+```bash
+# List policies with full admin access
+aws iam list-policies --scope Local \
+ --query 'Policies[*].[PolicyName,Arn]' --output table | \
+ grep -i admin
+
+# Find policies with wildcard actions
+aws iam list-policies --scope Local --query 'Policies[*].Arn' --output text | \
+while read arn; do
+ version=$(aws iam get-policy --policy-arn "$arn" \
+ --query 'Policy.DefaultVersionId' --output text)
+ doc=$(aws iam get-policy-version --policy-arn "$arn" \
+ --version-id "$version" --query 'PolicyVersion.Document')
+ if echo "$doc" | grep -q '"Action": "\*"'; then
+ echo "Wildcard action in: $arn"
+ fi
+done
+
+# Find inline policies (should use managed policies)
+aws iam list-users --query 'Users[*].UserName' --output text | \
+while read user; do
+ policies=$(aws iam list-user-policies --user-name "$user" \
+ --query 'PolicyNames' --output text)
+ if [ -n "$policies" ]; then
+ echo "Inline policies on user $user: $policies"
+ fi
+done
+```
+
+### MFA Enforcement
+
+```bash
+# List users without MFA
+aws iam get-credential-report --output text | \
+ awk -F, 'NR>1 && $4=="false" {print $1}'
+
+# Check if MFA is required in policies
+aws iam list-policies --scope Local --query 'Policies[*].Arn' --output text | \
+while read arn; do
+ version=$(aws iam get-policy --policy-arn "$arn" \
+ --query 'Policy.DefaultVersionId' --output text)
+ doc=$(aws iam get-policy-version --policy-arn "$arn" \
+ --version-id "$version" --query 'PolicyVersion.Document')
+ if echo "$doc" | grep -q "aws:MultiFactorAuthPresent"; then
+ echo "MFA enforced in: $arn"
+ fi
+done
+
+# Enable MFA for a user (returns QR code)
+aws iam create-virtual-mfa-device \
+ --virtual-mfa-device-name user-mfa \
+ --outfile /tmp/qr.png \
+ --bootstrap-method QRCodePNG
+```
+
+### Access Key Management
+
+```bash
+# Find old access keys (>90 days)
+aws iam list-users --query 'Users[*].UserName' --output text | \
+while read user; do
+ aws iam list-access-keys --user-name "$user" \
+ --query 'AccessKeyMetadata[*].[AccessKeyId,CreateDate,Status]' \
+ --output text | \
+ while read key_id create_date status; do
+ age_days=$(( ($(date +%s) - $(date -d "$create_date" +%s)) / 86400 ))
+ if [ $age_days -gt 90 ]; then
+ echo "$user: Key $key_id is $age_days days old"
+ fi
+ done
+done
+
+# Rotate access key
+OLD_KEY="AKIAIOSFODNN7EXAMPLE"
+USER="myuser"
+
+# Create new key
+NEW_KEY=$(aws iam create-access-key --user-name "$USER")
+echo "New key created. Update applications, then run:"
+echo "aws iam delete-access-key --user-name $USER --access-key-id $OLD_KEY"
+
+# Deactivate old key (test first)
+aws iam update-access-key \
+ --user-name "$USER" \
+ --access-key-id "$OLD_KEY" \
+ --status Inactive
+```
+
+### Role and Policy Analysis
+
+```bash
+# List unused roles (no activity in 90 days)
+aws iam list-roles --query 'Roles[*].[RoleName,RoleLastUsed.LastUsedDate]' \
+ --output text | \
+while read role last_used; do
+ if [ "$last_used" = "None" ]; then
+ echo "Never used: $role"
+ fi
+done
+
+# Find roles with trust relationships to external accounts
+aws iam list-roles --query 'Roles[*].RoleName' --output text | \
+while read role; do
+ trust=$(aws iam get-role --role-name "$role" \
+ --query 'Role.AssumeRolePolicyDocument')
+ if echo "$trust" | grep -q '"AWS":'; then
+ echo "External trust: $role"
+ fi
+done
+
+# Analyze policy permissions
+aws iam simulate-principal-policy \
+ --policy-source-arn arn:aws:iam::123456789012:user/myuser \
+ --action-names s3:GetObject s3:PutObject \
+ --resource-arns arn:aws:s3:::mybucket/*
+```
+
+## IAM Policy Templates
+
+### Least Privilege S3 Access
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "s3:GetObject",
+ "s3:PutObject"
+ ],
+ "Resource": "arn:aws:s3:::my-bucket/user-data/${aws:username}/*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "s3:ListBucket",
+ "Resource": "arn:aws:s3:::my-bucket",
+ "Condition": {
+ "StringLike": {
+ "s3:prefix": "user-data/${aws:username}/*"
+ }
+ }
+ }
+ ]
+}
+```
+
+### MFA-Required Policy
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Deny",
+ "Action": "*",
+ "Resource": "*",
+ "Condition": {
+ "BoolIfExists": {
+ "aws:MultiFactorAuthPresent": "false"
+ }
+ }
+ }
+ ]
+}
+```
+
+### Time-Based Access
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": "ec2:*",
+ "Resource": "*",
+ "Condition": {
+ "DateGreaterThan": {
+ "aws:CurrentTime": "2026-01-01T00:00:00Z"
+ },
+ "DateLessThan": {
+ "aws:CurrentTime": "2026-12-31T23:59:59Z"
+ }
+ }
+ }
+ ]
+}
+```
+
+### IP-Restricted Access
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Deny",
+ "Action": "*",
+ "Resource": "*",
+ "Condition": {
+ "NotIpAddress": {
+ "aws:SourceIp": [
+ "203.0.113.0/24",
+ "198.51.100.0/24"
+ ]
+ }
+ }
+ }
+ ]
+}
+```
+
+## IAM Hardening Checklist
+
+**User Management**
+- [ ] Enable MFA for all users
+- [ ] Remove unused IAM users
+- [ ] Rotate access keys every 90 days
+- [ ] Use IAM roles instead of long-term credentials
+- [ ] Implement password policy (length, complexity, rotation)
+
+**Policy Management**
+- [ ] Replace inline policies with managed policies
+- [ ] Remove wildcard (*) permissions
+- [ ] Implement least privilege
+- [ ] Use policy conditions (MFA, IP, time)
+- [ ] Regular policy reviews
+
+**Role Management**
+- [ ] Use roles for EC2 instances
+- [ ] Implement cross-account roles properly
+- [ ] Review trust relationships
+- [ ] Remove unused roles
+- [ ] Use session tags for fine-grained access
+
+**Monitoring**
+- [ ] Enable CloudTrail for IAM events
+- [ ] Set up CloudWatch alarms for IAM changes
+- [ ] Use AWS IAM Access Analyzer
+- [ ] Regular access reviews
+- [ ] Monitor for privilege escalation
+
+## Automated IAM Hardening
+
+```python
+#!/usr/bin/env python3
+# iam-hardening.py
+
+import boto3
+from datetime import datetime, timedelta
+
+iam = boto3.client('iam')
+
+def enforce_mfa():
+ """Identify users without MFA"""
+ users = iam.list_users()['Users']
+ no_mfa = []
+
+ for user in users:
+ mfa_devices = iam.list_mfa_devices(
+ UserName=user['UserName']
+ )['MFADevices']
+
+ if not mfa_devices:
+ no_mfa.append(user['UserName'])
+
+ return no_mfa
+
+def rotate_old_keys():
+ """Find access keys older than 90 days"""
+ users = iam.list_users()['Users']
+ old_keys = []
+
+ for user in users:
+ keys = iam.list_access_keys(
+ UserName=user['UserName']
+ )['AccessKeyMetadata']
+
+ for key in keys:
+ age = datetime.now(key['CreateDate'].tzinfo) - key['CreateDate']
+ if age.days > 90:
+ old_keys.append({
+ 'user': user['UserName'],
+ 'key_id': key['AccessKeyId'],
+ 'age_days': age.days
+ })
+
+ return old_keys
+
+def find_overpermissive_policies():
+ """Find policies with wildcard actions"""
+ policies = iam.list_policies(Scope='Local')['Policies']
+ overpermissive = []
+
+ for policy in policies:
+ version = iam.get_policy_version(
+ PolicyArn=policy['Arn'],
+ VersionId=policy['DefaultVersionId']
+ )
+
+ doc = version['PolicyVersion']['Document']
+ for statement in doc.get('Statement', []):
+ if statement.get('Action') == '*':
+ overpermissive.append(policy['PolicyName'])
+ break
+
+ return overpermissive
+
+if __name__ == "__main__":
+ print("IAM Hardening Report")
+ print("=" * 50)
+
+ print("\nUsers without MFA:")
+ for user in enforce_mfa():
+ print(f" - {user}")
+
+ print("\nOld access keys (>90 days):")
+ for key in rotate_old_keys():
+ print(f" - {key['user']}: {key['age_days']} days")
+
+ print("\nOverpermissive policies:")
+ for policy in find_overpermissive_policies():
+ print(f" - {policy}")
+```
+
+## Example Prompts
+
+- "Review my IAM policies for security issues"
+- "Find users without MFA enabled"
+- "Create a least privilege policy for S3 access"
+- "Identify overly permissive IAM roles"
+- "Generate an IAM hardening report"
+
+## Best Practices
+
+- Use AWS managed policies when possible
+- Implement policy versioning
+- Test policies in non-production first
+- Document policy purposes
+- Regular access reviews (quarterly)
+- Use IAM Access Analyzer
+- Implement SCPs for organization-wide controls
+
+## Kiro CLI Integration
+
+```bash
+kiro-cli chat "Use aws-iam-best-practices to review my IAM setup"
+kiro-cli chat "Create a least privilege policy with aws-iam-best-practices"
+```
+
+## Additional Resources
+
+- [IAM Best Practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)
+- [IAM Policy Simulator](https://policysim.aws.amazon.com/)
+- [IAM Access Analyzer](https://aws.amazon.com/iam/features/analyze-access/)
diff --git a/web-app/public/skills/security/aws-secrets-rotation/SKILL.md b/web-app/public/skills/security/aws-secrets-rotation/SKILL.md
new file mode 100644
index 00000000..663dfb73
--- /dev/null
+++ b/web-app/public/skills/security/aws-secrets-rotation/SKILL.md
@@ -0,0 +1,465 @@
+---
+name: aws-secrets-rotation
+description: Automate AWS secrets rotation for RDS, API keys, and credentials
+risk: safe
+source: community
+category: security
+tags: [aws, secrets-manager, security, automation, kiro-cli, credentials]
+---
+
+# AWS Secrets Rotation
+
+Automate rotation of secrets, credentials, and API keys using AWS Secrets Manager and Lambda.
+
+## When to Use
+
+Use this skill when you need to implement automated secrets rotation, manage credentials securely, or comply with security policies requiring regular key rotation.
+
+## Supported Secret Types
+
+**AWS Services**
+- RDS database credentials
+- DocumentDB credentials
+- Redshift credentials
+- ElastiCache credentials
+
+**Third-Party Services**
+- API keys
+- OAuth tokens
+- SSH keys
+- Custom credentials
+
+## Secrets Manager Setup
+
+### Create a Secret
+
+```bash
+# Create RDS secret
+aws secretsmanager create-secret \
+ --name prod/db/mysql \
+ --description "Production MySQL credentials" \
+ --secret-string '{
+ "username": "admin",
+ "password": "CHANGE_ME",
+ "engine": "mysql",
+ "host": "mydb.cluster-abc.us-east-1.rds.amazonaws.com",
+ "port": 3306,
+ "dbname": "myapp"
+ }'
+
+# Create API key secret
+aws secretsmanager create-secret \
+ --name prod/api/stripe \
+ --secret-string '{
+ "api_key": "sk_live_xxxxx",
+ "webhook_secret": "whsec_xxxxx"
+ }'
+
+# Create secret from file
+aws secretsmanager create-secret \
+ --name prod/ssh/private-key \
+ --secret-binary fileb://~/.ssh/id_rsa
+```
+
+### Retrieve Secrets
+
+```bash
+# Get secret value
+aws secretsmanager get-secret-value \
+ --secret-id prod/db/mysql \
+ --query 'SecretString' --output text
+
+# Get specific field
+aws secretsmanager get-secret-value \
+ --secret-id prod/db/mysql \
+ --query 'SecretString' --output text | \
+ jq -r '.password'
+
+# Get binary secret
+aws secretsmanager get-secret-value \
+ --secret-id prod/ssh/private-key \
+ --query 'SecretBinary' --output text | \
+ base64 -d > private-key.pem
+```
+
+## Automatic Rotation Setup
+
+### Enable RDS Rotation
+
+```bash
+# Enable automatic rotation (30 days)
+aws secretsmanager rotate-secret \
+ --secret-id prod/db/mysql \
+ --rotation-lambda-arn arn:aws:lambda:us-east-1:123456789012:function:SecretsManagerRDSMySQLRotation \
+ --rotation-rules AutomaticallyAfterDays=30
+
+# Rotate immediately
+aws secretsmanager rotate-secret \
+ --secret-id prod/db/mysql
+
+# Check rotation status
+aws secretsmanager describe-secret \
+ --secret-id prod/db/mysql \
+ --query 'RotationEnabled'
+```
+
+### Lambda Rotation Function
+
+```python
+# lambda_rotation.py
+import boto3
+import json
+import os
+
+secrets_client = boto3.client('secretsmanager')
+rds_client = boto3.client('rds')
+
+def lambda_handler(event, context):
+ """Rotate RDS MySQL password"""
+
+ secret_arn = event['SecretId']
+ token = event['ClientRequestToken']
+ step = event['Step']
+
+ # Get current secret
+ current = secrets_client.get_secret_value(SecretId=secret_arn)
+ secret = json.loads(current['SecretString'])
+
+ if step == "createSecret":
+ # Generate new password
+ new_password = generate_password()
+ secret['password'] = new_password
+
+ # Store as pending
+ secrets_client.put_secret_value(
+ SecretId=secret_arn,
+ ClientRequestToken=token,
+ SecretString=json.dumps(secret),
+ VersionStages=['AWSPENDING']
+ )
+
+ elif step == "setSecret":
+ # Update RDS password
+ rds_client.modify_db_instance(
+ DBInstanceIdentifier=secret['dbInstanceIdentifier'],
+ MasterUserPassword=secret['password'],
+ ApplyImmediately=True
+ )
+
+ elif step == "testSecret":
+ # Test new credentials
+ import pymysql
+ conn = pymysql.connect(
+ host=secret['host'],
+ user=secret['username'],
+ password=secret['password'],
+ database=secret['dbname']
+ )
+ conn.close()
+
+ elif step == "finishSecret":
+ # Mark as current
+ secrets_client.update_secret_version_stage(
+ SecretId=secret_arn,
+ VersionStage='AWSCURRENT',
+ MoveToVersionId=token,
+ RemoveFromVersionId=current['VersionId']
+ )
+
+ return {'statusCode': 200}
+
+def generate_password(length=32):
+ import secrets
+ import string
+ alphabet = string.ascii_letters + string.digits + "!@#$%^&*()"
+ return ''.join(secrets.choice(alphabet) for _ in range(length))
+```
+
+### Custom Rotation for API Keys
+
+```python
+# api_key_rotation.py
+import boto3
+import requests
+import json
+
+secrets_client = boto3.client('secretsmanager')
+
+def rotate_stripe_key(secret_arn, token, step):
+ """Rotate Stripe API key"""
+
+ current = secrets_client.get_secret_value(SecretId=secret_arn)
+ secret = json.loads(current['SecretString'])
+
+ if step == "createSecret":
+ # Create new Stripe key via API
+ response = requests.post(
+ 'https://api.stripe.com/v1/api_keys',
+ auth=(secret['api_key'], ''),
+ data={'name': f'rotated-{token[:8]}'}
+ )
+ new_key = response.json()['secret']
+
+ secret['api_key'] = new_key
+ secrets_client.put_secret_value(
+ SecretId=secret_arn,
+ ClientRequestToken=token,
+ SecretString=json.dumps(secret),
+ VersionStages=['AWSPENDING']
+ )
+
+ elif step == "testSecret":
+ # Test new key
+ response = requests.get(
+ 'https://api.stripe.com/v1/balance',
+ auth=(secret['api_key'], '')
+ )
+ if response.status_code != 200:
+ raise Exception("New key failed validation")
+
+ elif step == "finishSecret":
+ # Revoke old key
+ old_key = json.loads(current['SecretString'])['api_key']
+ requests.delete(
+ f'https://api.stripe.com/v1/api_keys/{old_key}',
+ auth=(secret['api_key'], '')
+ )
+
+ # Promote to current
+ secrets_client.update_secret_version_stage(
+ SecretId=secret_arn,
+ VersionStage='AWSCURRENT',
+ MoveToVersionId=token
+ )
+```
+
+## Rotation Monitoring
+
+### CloudWatch Alarms
+
+```bash
+# Create alarm for rotation failures
+aws cloudwatch put-metric-alarm \
+ --alarm-name secrets-rotation-failures \
+ --alarm-description "Alert on secrets rotation failures" \
+ --metric-name RotationFailed \
+ --namespace AWS/SecretsManager \
+ --statistic Sum \
+ --period 300 \
+ --evaluation-periods 1 \
+ --threshold 1 \
+ --comparison-operator GreaterThanThreshold \
+ --alarm-actions arn:aws:sns:us-east-1:123456789012:alerts
+```
+
+### Rotation Audit Script
+
+```bash
+#!/bin/bash
+# audit-rotations.sh
+
+echo "Secrets Rotation Audit"
+echo "====================="
+
+aws secretsmanager list-secrets --query 'SecretList[*].[Name,RotationEnabled,LastRotatedDate]' \
+ --output text | \
+while read name enabled last_rotated; do
+ echo ""
+ echo "Secret: $name"
+ echo " Rotation Enabled: $enabled"
+ echo " Last Rotated: $last_rotated"
+
+ if [ "$enabled" = "True" ]; then
+ # Check rotation schedule
+ rules=$(aws secretsmanager describe-secret --secret-id "$name" \
+ --query 'RotationRules.AutomaticallyAfterDays' --output text)
+ echo " Rotation Schedule: Every $rules days"
+
+ # Calculate days since last rotation
+ if [ "$last_rotated" != "None" ]; then
+ days_ago=$(( ($(date +%s) - $(date -d "$last_rotated" +%s)) / 86400 ))
+ echo " Days Since Rotation: $days_ago"
+
+ if [ $days_ago -gt $rules ]; then
+ echo " ⚠️ OVERDUE for rotation!"
+ fi
+ fi
+ fi
+done
+```
+
+## Application Integration
+
+### Python SDK
+
+```python
+import boto3
+import json
+
+def get_secret(secret_name):
+ """Retrieve secret from Secrets Manager"""
+ client = boto3.client('secretsmanager')
+
+ try:
+ response = client.get_secret_value(SecretId=secret_name)
+ return json.loads(response['SecretString'])
+ except Exception as e:
+ print(f"Error retrieving secret: {e}")
+ raise
+
+# Usage
+db_creds = get_secret('prod/db/mysql')
+connection = pymysql.connect(
+ host=db_creds['host'],
+ user=db_creds['username'],
+ password=db_creds['password'],
+ database=db_creds['dbname']
+)
+```
+
+### Node.js SDK
+
+```javascript
+const AWS = require('aws-sdk');
+const secretsManager = new AWS.SecretsManager();
+
+async function getSecret(secretName) {
+ try {
+ const data = await secretsManager.getSecretValue({
+ SecretId: secretName
+ }).promise();
+
+ return JSON.parse(data.SecretString);
+ } catch (err) {
+ console.error('Error retrieving secret:', err);
+ throw err;
+ }
+}
+
+// Usage
+const dbCreds = await getSecret('prod/db/mysql');
+const connection = mysql.createConnection({
+ host: dbCreds.host,
+ user: dbCreds.username,
+ password: dbCreds.password,
+ database: dbCreds.dbname
+});
+```
+
+## Rotation Best Practices
+
+**Planning**
+- [ ] Identify all secrets requiring rotation
+- [ ] Define rotation schedules (30, 60, 90 days)
+- [ ] Test rotation in non-production first
+- [ ] Document rotation procedures
+- [ ] Plan for emergency rotation
+
+**Implementation**
+- [ ] Use AWS managed rotation when possible
+- [ ] Implement proper error handling
+- [ ] Add CloudWatch monitoring
+- [ ] Test application compatibility
+- [ ] Implement gradual rollout
+
+**Operations**
+- [ ] Monitor rotation success/failure
+- [ ] Set up alerts for failures
+- [ ] Regular rotation audits
+- [ ] Document troubleshooting steps
+- [ ] Maintain rotation runbooks
+
+## Emergency Rotation
+
+```bash
+# Immediate rotation (compromise detected)
+aws secretsmanager rotate-secret \
+ --secret-id prod/db/mysql \
+ --rotate-immediately
+
+# Force rotation even if recently rotated
+aws secretsmanager rotate-secret \
+ --secret-id prod/api/stripe \
+ --rotation-lambda-arn arn:aws:lambda:us-east-1:123456789012:function:RotateStripeKey \
+ --rotate-immediately
+
+# Verify rotation completed
+aws secretsmanager describe-secret \
+ --secret-id prod/db/mysql \
+ --query 'LastRotatedDate'
+```
+
+## Compliance Tracking
+
+```python
+#!/usr/bin/env python3
+# compliance-report.py
+
+import boto3
+from datetime import datetime, timedelta
+
+client = boto3.client('secretsmanager')
+
+def generate_compliance_report():
+ secrets = client.list_secrets()['SecretList']
+
+ compliant = []
+ non_compliant = []
+
+ for secret in secrets:
+ name = secret['Name']
+ rotation_enabled = secret.get('RotationEnabled', False)
+ last_rotated = secret.get('LastRotatedDate')
+
+ if not rotation_enabled:
+ non_compliant.append({
+ 'name': name,
+ 'issue': 'Rotation not enabled'
+ })
+ continue
+
+ if last_rotated:
+ days_ago = (datetime.now(last_rotated.tzinfo) - last_rotated).days
+ if days_ago > 90:
+ non_compliant.append({
+ 'name': name,
+ 'issue': f'Not rotated in {days_ago} days'
+ })
+ else:
+ compliant.append(name)
+ else:
+ non_compliant.append({
+ 'name': name,
+ 'issue': 'Never rotated'
+ })
+
+ print(f"Compliant Secrets: {len(compliant)}")
+ print(f"Non-Compliant Secrets: {len(non_compliant)}")
+ print("\nNon-Compliant Details:")
+ for item in non_compliant:
+ print(f" - {item['name']}: {item['issue']}")
+
+if __name__ == "__main__":
+ generate_compliance_report()
+```
+
+## Example Prompts
+
+- "Set up automatic rotation for my RDS credentials"
+- "Create a Lambda function to rotate API keys"
+- "Audit all secrets for rotation compliance"
+- "Implement emergency rotation for compromised credentials"
+- "Generate a secrets rotation report"
+
+## Kiro CLI Integration
+
+```bash
+kiro-cli chat "Use aws-secrets-rotation to set up RDS credential rotation"
+kiro-cli chat "Create a rotation audit report with aws-secrets-rotation"
+```
+
+## Additional Resources
+
+- [AWS Secrets Manager Rotation](https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets.html)
+- [Rotation Lambda Templates](https://github.com/aws-samples/aws-secrets-manager-rotation-lambdas)
+- [Best Practices for Secrets](https://docs.aws.amazon.com/secretsmanager/latest/userguide/best-practices.html)
diff --git a/web-app/public/skills/security/aws-security-audit/SKILL.md b/web-app/public/skills/security/aws-security-audit/SKILL.md
new file mode 100644
index 00000000..350d976f
--- /dev/null
+++ b/web-app/public/skills/security/aws-security-audit/SKILL.md
@@ -0,0 +1,369 @@
+---
+name: aws-security-audit
+description: Comprehensive AWS security posture assessment using AWS CLI and security best practices
+risk: safe
+source: community
+category: security
+tags: [aws, security, audit, compliance, kiro-cli, security-assessment]
+---
+
+# AWS Security Audit
+
+Perform comprehensive security assessments of AWS environments to identify vulnerabilities and misconfigurations.
+
+## When to Use
+
+Use this skill when you need to audit AWS security posture, identify vulnerabilities, or prepare for compliance assessments.
+
+## Audit Categories
+
+**Identity & Access Management**
+- Overly permissive IAM policies
+- Unused IAM users and roles
+- MFA enforcement gaps
+- Root account usage
+- Access key rotation
+
+**Network Security**
+- Open security groups (0.0.0.0/0)
+- Public S3 buckets
+- Unencrypted data in transit
+- VPC flow logs disabled
+- Network ACL misconfigurations
+
+**Data Protection**
+- Unencrypted EBS volumes
+- Unencrypted RDS instances
+- S3 bucket encryption disabled
+- Backup policies missing
+- KMS key rotation disabled
+
+**Logging & Monitoring**
+- CloudTrail disabled
+- CloudWatch alarms missing
+- VPC Flow Logs disabled
+- S3 access logging disabled
+- Config recording disabled
+
+## Security Audit Commands
+
+### IAM Security Checks
+
+```bash
+# List users without MFA
+aws iam get-credential-report --output text | \
+ awk -F, '$4=="false" && $1!="" {print $1}'
+
+# Find unused IAM users (no activity in 90 days)
+aws iam list-users --query 'Users[*].[UserName]' --output text | \
+while read user; do
+ last_used=$(aws iam get-user --user-name "$user" \
+ --query 'User.PasswordLastUsed' --output text)
+ echo "$user: $last_used"
+done
+
+# List overly permissive policies (AdministratorAccess)
+aws iam list-policies --scope Local \
+ --query 'Policies[?PolicyName==`AdministratorAccess`]'
+
+# Find access keys older than 90 days
+aws iam list-users --query 'Users[*].UserName' --output text | \
+while read user; do
+ aws iam list-access-keys --user-name "$user" \
+ --query 'AccessKeyMetadata[*].[AccessKeyId,CreateDate]' \
+ --output text
+done
+
+# Check root account access keys
+aws iam get-account-summary \
+ --query 'SummaryMap.AccountAccessKeysPresent'
+```
+
+### Network Security Checks
+
+```bash
+# Find security groups open to the world
+aws ec2 describe-security-groups \
+ --query 'SecurityGroups[?IpPermissions[?IpRanges[?CidrIp==`0.0.0.0/0`]]].[GroupId,GroupName]' \
+ --output table
+
+# List public S3 buckets
+aws s3api list-buckets --query 'Buckets[*].Name' --output text | \
+while read bucket; do
+ acl=$(aws s3api get-bucket-acl --bucket "$bucket" 2>/dev/null)
+ if echo "$acl" | grep -q "AllUsers"; then
+ echo "PUBLIC: $bucket"
+ fi
+done
+
+# Check VPC Flow Logs status
+aws ec2 describe-vpcs --query 'Vpcs[*].VpcId' --output text | \
+while read vpc; do
+ flow_logs=$(aws ec2 describe-flow-logs \
+ --filter "Name=resource-id,Values=$vpc" \
+ --query 'FlowLogs[*].FlowLogId' --output text)
+ if [ -z "$flow_logs" ]; then
+ echo "No flow logs: $vpc"
+ fi
+done
+
+# Find RDS instances without encryption
+aws rds describe-db-instances \
+ --query 'DBInstances[?StorageEncrypted==`false`].[DBInstanceIdentifier]' \
+ --output table
+```
+
+### Data Protection Checks
+
+```bash
+# Find unencrypted EBS volumes
+aws ec2 describe-volumes \
+ --query 'Volumes[?Encrypted==`false`].[VolumeId,Size,State]' \
+ --output table
+
+# Check S3 bucket encryption
+aws s3api list-buckets --query 'Buckets[*].Name' --output text | \
+while read bucket; do
+ encryption=$(aws s3api get-bucket-encryption \
+ --bucket "$bucket" 2>&1)
+ if echo "$encryption" | grep -q "ServerSideEncryptionConfigurationNotFoundError"; then
+ echo "No encryption: $bucket"
+ fi
+done
+
+# Find RDS snapshots that are public
+aws rds describe-db-snapshots \
+ --query 'DBSnapshots[*].[DBSnapshotIdentifier]' --output text | \
+while read snapshot; do
+ attrs=$(aws rds describe-db-snapshot-attributes \
+ --db-snapshot-identifier "$snapshot" \
+ --query 'DBSnapshotAttributesResult.DBSnapshotAttributes[?AttributeName==`restore`].AttributeValues' \
+ --output text)
+ if echo "$attrs" | grep -q "all"; then
+ echo "PUBLIC SNAPSHOT: $snapshot"
+ fi
+done
+
+# Check KMS key rotation
+aws kms list-keys --query 'Keys[*].KeyId' --output text | \
+while read key; do
+ rotation=$(aws kms get-key-rotation-status --key-id "$key" \
+ --query 'KeyRotationEnabled' --output text 2>/dev/null)
+ if [ "$rotation" = "False" ]; then
+ echo "Rotation disabled: $key"
+ fi
+done
+```
+
+### Logging & Monitoring Checks
+
+```bash
+# Check CloudTrail status
+aws cloudtrail describe-trails \
+ --query 'trailList[*].[Name,IsMultiRegionTrail,LogFileValidationEnabled]' \
+ --output table
+
+# Verify CloudTrail is logging
+aws cloudtrail get-trail-status --name my-trail \
+ --query 'IsLogging'
+
+# Check if AWS Config is enabled
+aws configservice describe-configuration-recorders \
+ --query 'ConfigurationRecorders[*].[name,roleARN]' \
+ --output table
+
+# List S3 buckets without access logging
+aws s3api list-buckets --query 'Buckets[*].Name' --output text | \
+while read bucket; do
+ logging=$(aws s3api get-bucket-logging --bucket "$bucket" 2>&1)
+ if ! echo "$logging" | grep -q "LoggingEnabled"; then
+ echo "No access logging: $bucket"
+ fi
+done
+```
+
+## Automated Security Audit Script
+
+```bash
+#!/bin/bash
+# comprehensive-security-audit.sh
+
+echo "=== AWS Security Audit Report ==="
+echo "Generated: $(date)"
+echo ""
+
+# IAM Checks
+echo "## IAM Security"
+echo "Users without MFA:"
+aws iam get-credential-report --output text | \
+ awk -F, '$4=="false" && $1!="" {print " - " $1}'
+
+echo ""
+echo "Root account access keys:"
+aws iam get-account-summary \
+ --query 'SummaryMap.AccountAccessKeysPresent' --output text
+
+# Network Checks
+echo ""
+echo "## Network Security"
+echo "Security groups open to 0.0.0.0/0:"
+aws ec2 describe-security-groups \
+ --query 'SecurityGroups[?IpPermissions[?IpRanges[?CidrIp==`0.0.0.0/0`]]].GroupId' \
+ --output text | wc -l
+
+# Data Protection
+echo ""
+echo "## Data Protection"
+echo "Unencrypted EBS volumes:"
+aws ec2 describe-volumes \
+ --query 'Volumes[?Encrypted==`false`].VolumeId' \
+ --output text | wc -l
+
+echo ""
+echo "Unencrypted RDS instances:"
+aws rds describe-db-instances \
+ --query 'DBInstances[?StorageEncrypted==`false`].DBInstanceIdentifier' \
+ --output text | wc -l
+
+# Logging
+echo ""
+echo "## Logging & Monitoring"
+echo "CloudTrail status:"
+aws cloudtrail describe-trails \
+ --query 'trailList[*].[Name,IsLogging]' \
+ --output table
+
+echo ""
+echo "=== End of Report ==="
+```
+
+## Security Score Calculator
+
+```python
+#!/usr/bin/env python3
+# security-score.py
+
+import boto3
+import json
+
+def calculate_security_score():
+ iam = boto3.client('iam')
+ ec2 = boto3.client('ec2')
+ s3 = boto3.client('s3')
+
+ score = 100
+ issues = []
+
+ # Check MFA
+ try:
+ report = iam.get_credential_report()
+ users_without_mfa = 0
+ # Parse report and count
+ if users_without_mfa > 0:
+ score -= 10
+ issues.append(f"{users_without_mfa} users without MFA")
+ except:
+ pass
+
+ # Check open security groups
+ sgs = ec2.describe_security_groups()
+ open_sgs = 0
+ for sg in sgs['SecurityGroups']:
+ for perm in sg.get('IpPermissions', []):
+ for ip_range in perm.get('IpRanges', []):
+ if ip_range.get('CidrIp') == '0.0.0.0/0':
+ open_sgs += 1
+ break
+
+ if open_sgs > 0:
+ score -= 15
+ issues.append(f"{open_sgs} security groups open to internet")
+
+ # Check unencrypted volumes
+ volumes = ec2.describe_volumes()
+ unencrypted = sum(1 for v in volumes['Volumes'] if not v['Encrypted'])
+
+ if unencrypted > 0:
+ score -= 20
+ issues.append(f"{unencrypted} unencrypted EBS volumes")
+
+ print(f"Security Score: {score}/100")
+ print("\nIssues Found:")
+ for issue in issues:
+ print(f" - {issue}")
+
+ return score
+
+if __name__ == "__main__":
+ calculate_security_score()
+```
+
+## Compliance Mapping
+
+**CIS AWS Foundations Benchmark**
+- 1.1: Root account usage
+- 1.2-1.14: IAM policies and MFA
+- 2.1-2.9: Logging (CloudTrail, Config, VPC Flow Logs)
+- 4.1-4.3: Monitoring and alerting
+
+**PCI-DSS**
+- Requirement 1: Network security controls
+- Requirement 2: Secure configurations
+- Requirement 8: Access controls and MFA
+- Requirement 10: Logging and monitoring
+
+**HIPAA**
+- Access controls (IAM)
+- Audit controls (CloudTrail)
+- Encryption (EBS, RDS, S3)
+- Transmission security (TLS/SSL)
+
+## Remediation Priorities
+
+**Critical (Fix Immediately)**
+- Root account access keys
+- Public RDS snapshots
+- Security groups open to 0.0.0.0/0 on sensitive ports
+- CloudTrail disabled
+
+**High (Fix Within 7 Days)**
+- Users without MFA
+- Unencrypted data at rest
+- Missing VPC Flow Logs
+- Overly permissive IAM policies
+
+**Medium (Fix Within 30 Days)**
+- Old access keys (>90 days)
+- Missing S3 access logging
+- Unused IAM users
+- KMS key rotation disabled
+
+## Example Prompts
+
+- "Run a comprehensive security audit on my AWS account"
+- "Check for IAM security issues"
+- "Find all unencrypted resources"
+- "Generate a security compliance report"
+- "Calculate my AWS security score"
+
+## Best Practices
+
+- Run audits weekly
+- Automate with Lambda/EventBridge
+- Export results to S3 for trending
+- Integrate with SIEM tools
+- Track remediation progress
+- Document exceptions with business justification
+
+## Kiro CLI Integration
+
+```bash
+kiro-cli chat "Use aws-security-audit to assess my security posture"
+kiro-cli chat "Generate a security audit report with aws-security-audit"
+```
+
+## Additional Resources
+
+- [AWS Security Best Practices](https://aws.amazon.com/security/best-practices/)
+- [CIS AWS Foundations Benchmark](https://www.cisecurity.org/benchmark/amazon_web_services)
+- [AWS Security Hub](https://aws.amazon.com/security-hub/)
diff --git a/web-app/public/skills/segment-automation/SKILL.md b/web-app/public/skills/segment-automation/SKILL.md
index 1b5bb195..45f6f430 100644
--- a/web-app/public/skills/segment-automation/SKILL.md
+++ b/web-app/public/skills/segment-automation/SKILL.md
@@ -3,6 +3,8 @@ name: segment-automation
description: "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Segment Automation via Rube MCP
@@ -223,3 +225,6 @@ Segment recommends consistent event naming:
| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |
| Update source | SEGMENT_UPDATE_SOURCE | sourceId |
| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/segment-cdp/SKILL.md b/web-app/public/skills/segment-cdp/SKILL.md
index fd1a5e8e..dcd7eff9 100644
--- a/web-app/public/skills/segment-cdp/SKILL.md
+++ b/web-app/public/skills/segment-cdp/SKILL.md
@@ -1,7 +1,8 @@
---
name: segment-cdp
-description: "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices. Use when: segment, analytics.js, customer data platform, cdp, tracking plan."
+description: "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Segment CDP
@@ -48,3 +49,6 @@ Connect to Protocols for enforcement.
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | high | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/sendgrid-automation/SKILL.md b/web-app/public/skills/sendgrid-automation/SKILL.md
index 0c44fedf..a22d67b2 100644
--- a/web-app/public/skills/sendgrid-automation/SKILL.md
+++ b/web-app/public/skills/sendgrid-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: sendgrid-automation
-description: "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current schemas."
+description: "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# SendGrid Automation via Rube MCP
@@ -226,3 +228,6 @@ Contact operations (`ADD_OR_UPDATE_A_CONTACT`, `IMPORT_CONTACTS`) are asynchrono
| Suppression groups | `SENDGRID_GET_SUPPRESSION_GROUPS` | (none) |
| Get template | `SENDGRID_RETRIEVE_A_SINGLE_TRANSACTIONAL_TEMPLATE` | `template_id` |
| Duplicate template | `SENDGRID_DUPLICATE_A_TRANSACTIONAL_TEMPLATE` | `template_id`, `name` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/senior-architect/SKILL.md b/web-app/public/skills/senior-architect/SKILL.md
index 30160d0e..2896c58a 100644
--- a/web-app/public/skills/senior-architect/SKILL.md
+++ b/web-app/public/skills/senior-architect/SKILL.md
@@ -1,6 +1,8 @@
---
name: senior-architect
-description: Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.
+description: "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I..."
+risk: unknown
+source: community
---
# Senior Architect
@@ -207,3 +209,6 @@ Check the comprehensive troubleshooting section in `references/tech_decision_gui
- Workflow Guide: `references/system_design_workflows.md`
- Technical Guide: `references/tech_decision_guide.md`
- Tool Scripts: `scripts/` directory
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/senior-fullstack/SKILL.md b/web-app/public/skills/senior-fullstack/SKILL.md
index 43f9d9e6..c8fe8764 100644
--- a/web-app/public/skills/senior-fullstack/SKILL.md
+++ b/web-app/public/skills/senior-fullstack/SKILL.md
@@ -1,6 +1,8 @@
---
name: senior-fullstack
-description: Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.
+description: "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec..."
+risk: unknown
+source: community
---
# Senior Fullstack
@@ -207,3 +209,6 @@ Check the comprehensive troubleshooting section in `references/development_workf
- Workflow Guide: `references/architecture_patterns.md`
- Technical Guide: `references/development_workflows.md`
- Tool Scripts: `scripts/` directory
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/sentry-automation/SKILL.md b/web-app/public/skills/sentry-automation/SKILL.md
index ce12eec4..39f2a78a 100644
--- a/web-app/public/skills/sentry-automation/SKILL.md
+++ b/web-app/public/skills/sentry-automation/SKILL.md
@@ -3,6 +3,8 @@ name: sentry-automation
description: "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Sentry Automation via Rube MCP
@@ -230,3 +232,6 @@ Automate Sentry error tracking and monitoring operations through Composio's Sent
| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |
| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |
| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/seo-audit/SKILL.md b/web-app/public/skills/seo-audit/SKILL.md
index c17f5df1..8c8b91d0 100644
--- a/web-app/public/skills/seo-audit/SKILL.md
+++ b/web-app/public/skills/seo-audit/SKILL.md
@@ -1,12 +1,14 @@
---
name: seo-audit
-description: >
+description: ">"
Diagnose and audit SEO issues affecting crawlability, indexation, rankings,
and organic performance. Use when the user asks for an SEO audit, technical SEO
review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check.
This skill identifies issues and prioritizes actions but does not execute changes.
For large-scale page creation, use programmatic-seo. For structured data, use
schema-markup.
+risk: unknown
+source: community
---
# SEO Audit
@@ -485,3 +487,6 @@ Use these skills **only after the audit is complete** and findings are accepted.
* **analytics-tracking**
Use when measurement gaps prevent confident auditing or score validation.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/seo-authority-builder/SKILL.md b/web-app/public/skills/seo-authority-builder/SKILL.md
index a4388fc6..78322085 100644
--- a/web-app/public/skills/seo-authority-builder/SKILL.md
+++ b/web-app/public/skills/seo-authority-builder/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-authority-builder
-description: Analyzes content for E-E-A-T signals and suggests improvements to
+description: "Analyzes content for E-E-A-T signals and suggests improvements to"
build authority and trust. Identifies missing credibility elements. Use
PROACTIVELY for YMYL topics.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-cannibalization-detector/SKILL.md b/web-app/public/skills/seo-cannibalization-detector/SKILL.md
index c31a3afc..30f7f19b 100644
--- a/web-app/public/skills/seo-cannibalization-detector/SKILL.md
+++ b/web-app/public/skills/seo-cannibalization-detector/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-cannibalization-detector
-description: Analyzes multiple provided pages to identify keyword overlap and
+description: "Analyzes multiple provided pages to identify keyword overlap and"
potential cannibalization issues. Suggests differentiation strategies. Use
PROACTIVELY when reviewing similar content.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-content-auditor/SKILL.md b/web-app/public/skills/seo-content-auditor/SKILL.md
index 5b3369de..8e747996 100644
--- a/web-app/public/skills/seo-content-auditor/SKILL.md
+++ b/web-app/public/skills/seo-content-auditor/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-content-auditor
-description: Analyzes provided content for quality, E-E-A-T signals, and SEO
+description: "Analyzes provided content for quality, E-E-A-T signals, and SEO"
best practices. Scores content and provides improvement recommendations based
on established guidelines. Use PROACTIVELY for content review.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-content-planner/SKILL.md b/web-app/public/skills/seo-content-planner/SKILL.md
index 11fcf572..66c7797f 100644
--- a/web-app/public/skills/seo-content-planner/SKILL.md
+++ b/web-app/public/skills/seo-content-planner/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-content-planner
-description: Creates comprehensive content outlines and topic clusters for SEO.
+description: "Creates comprehensive content outlines and topic clusters for SEO."
Plans content calendars and identifies topic gaps. Use PROACTIVELY for content
strategy and planning.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-content-refresher/SKILL.md b/web-app/public/skills/seo-content-refresher/SKILL.md
index 97bffa08..79ca9440 100644
--- a/web-app/public/skills/seo-content-refresher/SKILL.md
+++ b/web-app/public/skills/seo-content-refresher/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-content-refresher
-description: Identifies outdated elements in provided content and suggests
+description: "Identifies outdated elements in provided content and suggests"
updates to maintain freshness. Finds statistics, dates, and examples that need
updating. Use PROACTIVELY for older content.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-content-writer/SKILL.md b/web-app/public/skills/seo-content-writer/SKILL.md
index 38501f4c..bc80aa22 100644
--- a/web-app/public/skills/seo-content-writer/SKILL.md
+++ b/web-app/public/skills/seo-content-writer/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-content-writer
-description: Writes SEO-optimized content based on provided keywords and topic
+description: "Writes SEO-optimized content based on provided keywords and topic"
briefs. Creates engaging, comprehensive content following best practices. Use
PROACTIVELY for content creation tasks.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-fundamentals/SKILL.md b/web-app/public/skills/seo-fundamentals/SKILL.md
index 66999355..71212a55 100644
--- a/web-app/public/skills/seo-fundamentals/SKILL.md
+++ b/web-app/public/skills/seo-fundamentals/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-fundamentals
-description: >
+description: ">"
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations,
content quality, and how modern search engines evaluate pages. This skill explains
*why* SEO works, not how to execute specific optimizations.
allowed-tools: Read, Glob, Grep
+risk: unknown
+source: community
---
---
@@ -171,3 +173,6 @@ SEO fundamentals should be validated using **multiple signals**, not single metr
> **Key Principle:**
> Sustainable SEO is built on _useful content_, _technical clarity_, and _trust over time_.
> There are no permanent shortcuts.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/seo-keyword-strategist/SKILL.md b/web-app/public/skills/seo-keyword-strategist/SKILL.md
index 37a4272d..f0c64c9e 100644
--- a/web-app/public/skills/seo-keyword-strategist/SKILL.md
+++ b/web-app/public/skills/seo-keyword-strategist/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-keyword-strategist
-description: Analyzes keyword usage in provided content, calculates density,
+description: "Analyzes keyword usage in provided content, calculates density,"
suggests semantic variations and LSI keywords based on the topic. Prevents
over-optimization. Use PROACTIVELY for content optimization.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-meta-optimizer/SKILL.md b/web-app/public/skills/seo-meta-optimizer/SKILL.md
index 9360e762..d1cf7499 100644
--- a/web-app/public/skills/seo-meta-optimizer/SKILL.md
+++ b/web-app/public/skills/seo-meta-optimizer/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-meta-optimizer
-description: Creates optimized meta titles, descriptions, and URL suggestions
+description: "Creates optimized meta titles, descriptions, and URL suggestions"
based on character limits and best practices. Generates compelling,
keyword-rich metadata. Use PROACTIVELY for new content.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-snippet-hunter/SKILL.md b/web-app/public/skills/seo-snippet-hunter/SKILL.md
index 18dab815..eab15c08 100644
--- a/web-app/public/skills/seo-snippet-hunter/SKILL.md
+++ b/web-app/public/skills/seo-snippet-hunter/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-snippet-hunter
-description: Formats content to be eligible for featured snippets and SERP
+description: "Formats content to be eligible for featured snippets and SERP"
features. Creates snippet-optimized content blocks based on best practices.
Use PROACTIVELY for question-based content.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/seo-structure-architect/SKILL.md b/web-app/public/skills/seo-structure-architect/SKILL.md
index 06c09de6..d9c0644b 100644
--- a/web-app/public/skills/seo-structure-architect/SKILL.md
+++ b/web-app/public/skills/seo-structure-architect/SKILL.md
@@ -1,10 +1,12 @@
---
name: seo-structure-architect
-description: Analyzes and optimizes content structure including header
+description: "Analyzes and optimizes content structure including header"
hierarchy, suggests schema markup, and internal linking opportunities. Creates
search-friendly content organization. Use PROACTIVELY for content structuring.
metadata:
model: haiku
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/server-management/SKILL.md b/web-app/public/skills/server-management/SKILL.md
index 708638c3..bdbb04ea 100644
--- a/web-app/public/skills/server-management/SKILL.md
+++ b/web-app/public/skills/server-management/SKILL.md
@@ -1,7 +1,9 @@
---
name: server-management
-description: Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
+description: "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Server Management
@@ -159,3 +161,6 @@ When something's wrong:
---
> **Remember:** A well-managed server is boring. That's the goal.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/service-mesh-expert/SKILL.md b/web-app/public/skills/service-mesh-expert/SKILL.md
index 37575bf4..248f3ce9 100644
--- a/web-app/public/skills/service-mesh-expert/SKILL.md
+++ b/web-app/public/skills/service-mesh-expert/SKILL.md
@@ -1,6 +1,8 @@
---
name: service-mesh-expert
description: "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con"
+risk: unknown
+source: community
---
# Service Mesh Expert
diff --git a/web-app/public/skills/service-mesh-observability/SKILL.md b/web-app/public/skills/service-mesh-observability/SKILL.md
index 27e82561..69ecdd6d 100644
--- a/web-app/public/skills/service-mesh-observability/SKILL.md
+++ b/web-app/public/skills/service-mesh-observability/SKILL.md
@@ -1,6 +1,8 @@
---
name: service-mesh-observability
-description: Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
+description: "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL..."
+risk: unknown
+source: community
---
# Service Mesh Observability
diff --git a/web-app/public/skills/shader-programming-glsl/SKILL.md b/web-app/public/skills/shader-programming-glsl/SKILL.md
new file mode 100644
index 00000000..f1ca2afc
--- /dev/null
+++ b/web-app/public/skills/shader-programming-glsl/SKILL.md
@@ -0,0 +1,121 @@
+---
+name: shader-programming-glsl
+description: Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.
+risk: safe
+source: community
+---
+
+# Shader Programming GLSL
+
+## Overview
+
+A comprehensive guide to writing GPU shaders using GLSL (OpenGL Shading Language). Learn syntax, uniforms, varying variables, and key mathematical concepts like swizzling and vector operations for visual effects.
+
+## When to Use This Skill
+
+- Use when creating custom visual effects in WebGL, Three.js, or game engines.
+- Use when optimizing graphics rendering performance.
+- Use when implementing post-processing effects (blur, bloom, color correction).
+- Use when procedurally generating textures or geometry on the GPU.
+
+## Step-by-Step Guide
+
+### 1. Structure: Vertex vs. Fragment
+
+Understand the pipeline:
+- **Vertex Shader**: Transforms 3D coordinates to 2D screen space (`gl_Position`).
+- **Fragment Shader**: Colors individual pixels (`gl_FragColor`).
+
+```glsl
+// Vertex Shader (basic)
+attribute vec3 position;
+uniform mat4 modelViewMatrix;
+uniform mat4 projectionMatrix;
+
+void main() {
+ gl_Position = projectionMatrix * modelViewMatrix * vec4(position, 1.0);
+}
+```
+
+```glsl
+// Fragment Shader (basic)
+uniform vec3 color;
+
+void main() {
+ gl_FragColor = vec4(color, 1.0);
+}
+```
+
+### 2. Uniforms and Varyings
+
+- `uniform`: Data constant for all vertices/fragments (passed from CPU).
+- `varying`: Data interpolated from vertex to fragment shader.
+
+```glsl
+// Passing UV coordinates
+varying vec2 vUv;
+
+// In Vertex Shader
+void main() {
+ vUv = uv;
+ gl_Position = projectionMatrix * modelViewMatrix * vec4(position, 1.0);
+}
+
+// In Fragment Shader
+void main() {
+ // Gradient based on UV
+ gl_FragColor = vec4(vUv.x, vUv.y, 1.0, 1.0);
+}
+```
+
+### 3. Swizzling & Vector Math
+
+Access vector components freely: `vec4 color = vec4(1.0, 0.5, 0.0, 1.0);`
+- `color.rgb` -> `vec3(1.0, 0.5, 0.0)`
+- `color.zyx` -> `vec3(0.0, 0.5, 1.0)` (reordering)
+
+## Examples
+
+### Example 1: Simple Raymarching (SDF Sphere)
+
+```glsl
+float sdSphere(vec3 p, float s) {
+ return length(p) - s;
+}
+
+void mainImage(out vec4 fragColor, in vec2 fragCoord) {
+ vec2 uv = (fragCoord - 0.5 * iResolution.xy) / iResolution.y;
+ vec3 ro = vec3(0.0, 0.0, -3.0); // Ray Origin
+ vec3 rd = normalize(vec3(uv, 1.0)); // Ray Direction
+
+ float t = 0.0;
+ for(int i = 0; i < 64; i++) {
+ vec3 p = ro + rd * t;
+ float d = sdSphere(p, 1.0); // Sphere radius 1.0
+ if(d < 0.001) break;
+ t += d;
+ }
+
+ vec3 col = vec3(0.0);
+ if(t < 10.0) {
+ vec3 p = ro + rd * t;
+ vec3 normal = normalize(p);
+ col = normal * 0.5 + 0.5; // Color by normal
+ }
+
+ fragColor = vec4(col, 1.0);
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `mix()` for linear interpolation instead of manual math.
+- ✅ **Do:** Use `step()` and `smoothstep()` for thresholding and soft edges (avoid `if` branches).
+- ✅ **Do:** Pack data into vectors (`vec4`) to minimize memory access.
+- ❌ **Don't:** Use heavy branching (`if-else`) inside loops if possible; it hurts GPU parallelism.
+- ❌ **Don't:** Calculate constant values inside the shader; pre-calculate them on the CPU (uniforms).
+
+## Troubleshooting
+
+**Problem:** Shader compiles but screen is black.
+**Solution:** Check if `gl_Position.w` is correct (usually 1.0). Check if uniforms are actually being set from the host application. Verify UV coordinates are within [0, 1].
diff --git a/web-app/public/skills/shellcheck-configuration/SKILL.md b/web-app/public/skills/shellcheck-configuration/SKILL.md
index 29aed114..63036a4d 100644
--- a/web-app/public/skills/shellcheck-configuration/SKILL.md
+++ b/web-app/public/skills/shellcheck-configuration/SKILL.md
@@ -1,6 +1,8 @@
---
name: shellcheck-configuration
-description: Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.
+description: "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability."
+risk: unknown
+source: community
---
# ShellCheck Configuration and Static Analysis
diff --git a/web-app/public/skills/shodan-reconnaissance/SKILL.md b/web-app/public/skills/shodan-reconnaissance/SKILL.md
index 3bb1bdaf..8713333f 100644
--- a/web-app/public/skills/shodan-reconnaissance/SKILL.md
+++ b/web-app/public/skills/shodan-reconnaissance/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Shodan Reconnaissance and Pentesting
-description: This skill should be used when the user asks to "search for exposed devices on the internet," "perform Shodan reconnaissance," "find vulnerable services using Shodan," "scan IP ranges with Shodan," or "discover IoT devices and open ports." It provides comprehensive guidance for using Shodan's search engine, CLI, and API for penetration testing reconnaissance.
+name: shodan-reconnaissance
+description: "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Shodan Reconnaissance and Pentesting
@@ -501,3 +503,6 @@ shodan download network_scan.json.gz 'net:192.168.1.0/24'
| Rate Limit Exceeded | >1 request/second | Add `time.sleep(1)` between API requests |
| Empty Search Results | Too specific or syntax error | Use quotes for phrases: `'org:"Company Name"'`; broaden criteria |
| Downloaded File Won't Parse | Corrupted or wrong format | Verify with `gunzip -t file.gz`, re-download with `--limit` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/shopify-apps/SKILL.md b/web-app/public/skills/shopify-apps/SKILL.md
index ef66cab1..aa32dfb8 100644
--- a/web-app/public/skills/shopify-apps/SKILL.md
+++ b/web-app/public/skills/shopify-apps/SKILL.md
@@ -1,7 +1,8 @@
---
name: shopify-apps
-description: "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. Use when: shopify app, shopify, embedded app, polaris, app bridge."
+description: "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Shopify Apps
@@ -40,3 +41,6 @@ Secure webhook processing with HMAC verification
| Issue | high | ## Use GraphQL for all new code |
| Issue | high | ## Use latest App Bridge via script tag |
| Issue | high | ## Implement all GDPR handlers |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/shopify-automation/SKILL.md b/web-app/public/skills/shopify-automation/SKILL.md
index 882206ff..72fbdb5d 100644
--- a/web-app/public/skills/shopify-automation/SKILL.md
+++ b/web-app/public/skills/shopify-automation/SKILL.md
@@ -3,6 +3,8 @@ name: shopify-automation
description: "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Shopify Automation via Rube MCP
@@ -166,3 +168,6 @@ For advanced operations:
| Fulfillment | SHOPIFY_GET_FULFILLMENT | order_id, fulfillment_id |
| GraphQL | SHOPIFY_GRAPH_QL_QUERY | query |
| Bulk query | SHOPIFY_BULK_QUERY_OPERATION | query |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/shopify-development/SKILL.md b/web-app/public/skills/shopify-development/SKILL.md
index ea89ab10..0104b6ac 100644
--- a/web-app/public/skills/shopify-development/SKILL.md
+++ b/web-app/public/skills/shopify-development/SKILL.md
@@ -5,6 +5,8 @@ description: |
TRIGGER: "shopify", "shopify app", "checkout extension", "admin extension", "POS extension",
"shopify theme", "liquid template", "polaris", "shopify graphql", "shopify webhook",
"shopify billing", "app subscription", "metafields", "shopify functions"
+risk: unknown
+source: community
---
# Shopify Development Skill
@@ -364,3 +366,6 @@ For detailed implementation guides, read these files:
- Polaris Design System: https://polaris.shopify.com
API Version: 2026-01 (quarterly releases, 12-month deprecation window)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/signup-flow-cro/SKILL.md b/web-app/public/skills/signup-flow-cro/SKILL.md
index 26615e08..3d0b7990 100644
--- a/web-app/public/skills/signup-flow-cro/SKILL.md
+++ b/web-app/public/skills/signup-flow-cro/SKILL.md
@@ -1,6 +1,8 @@
---
name: signup-flow-cro
-description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
+description: "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup..."
+risk: unknown
+source: community
---
# Signup Flow CRO
@@ -353,3 +355,6 @@ If you need more context:
- **form-cro**: For non-signup forms (lead capture, contact)
- **page-cro**: For the landing page leading to signup
- **ab-test-setup**: For testing signup flow changes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/similarity-search-patterns/SKILL.md b/web-app/public/skills/similarity-search-patterns/SKILL.md
index 3f5b0bc2..ee437479 100644
--- a/web-app/public/skills/similarity-search-patterns/SKILL.md
+++ b/web-app/public/skills/similarity-search-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: similarity-search-patterns
-description: Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
+description: "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance."
+risk: unknown
+source: community
---
# Similarity Search Patterns
diff --git a/web-app/public/skills/skill-creator-ms/SKILL.md b/web-app/public/skills/skill-creator-ms/SKILL.md
index 1f27c72a..75ba87b5 100644
--- a/web-app/public/skills/skill-creator-ms/SKILL.md
+++ b/web-app/public/skills/skill-creator-ms/SKILL.md
@@ -1,6 +1,8 @@
---
-name: skill-creator
-description: Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
+name: skill-creator-ms
+description: "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills."
+risk: unknown
+source: community
---
# Skill Creator
@@ -225,8 +227,8 @@ client.delete_item(item_id)
| File | Contents |
|------|----------|
-| [references/tools.md](references/tools.md) | Tool integrations |
-| [references/streaming.md](references/streaming.md) | Event streaming patterns |
+| references/tools.md | Tool integrations |
+| references/streaming.md | Event streaming patterns |
```
---
@@ -525,8 +527,8 @@ After creating the skill:
[Minimal example]
## Advanced Features
-- **Streaming**: See [references/streaming.md](references/streaming.md)
-- **Tools**: See [references/tools.md](references/tools.md)
+- **Streaming**: See references/streaming.md
+- **Tools**: See references/tools.md
```
### Pattern 2: Language Variants
@@ -611,3 +613,6 @@ Before completing a skill:
**Documentation:**
- [ ] README.md skill catalog updated
- [ ] Instructs to search `microsoft-docs` MCP for current APIs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/skill-creator/SKILL.md b/web-app/public/skills/skill-creator/SKILL.md
index 5ea8b178..cc4490a8 100644
--- a/web-app/public/skills/skill-creator/SKILL.md
+++ b/web-app/public/skills/skill-creator/SKILL.md
@@ -1,6 +1,6 @@
---
name: skill-creator
-description: "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation."
+description: "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s..."
version: 1.3.0
author: Eric Andrade
created: 2025-02-01
@@ -9,6 +9,7 @@ platforms: [github-copilot-cli, claude-code, codex]
category: meta
tags: [automation, scaffolding, skill-creation, meta-skill]
risk: safe
+source: community
---
# skill-creator
diff --git a/web-app/public/skills/skill-developer/SKILL.md b/web-app/public/skills/skill-developer/SKILL.md
index 4c26d2dd..c112a85a 100644
--- a/web-app/public/skills/skill-developer/SKILL.md
+++ b/web-app/public/skills/skill-developer/SKILL.md
@@ -1,6 +1,8 @@
---
name: skill-developer
-description: Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.
+description: "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil..."
+risk: unknown
+source: community
---
# Skill Developer Guide
diff --git a/web-app/public/skills/slack-automation/SKILL.md b/web-app/public/skills/slack-automation/SKILL.md
index 56851603..e67f00ec 100644
--- a/web-app/public/skills/slack-automation/SKILL.md
+++ b/web-app/public/skills/slack-automation/SKILL.md
@@ -1,8 +1,10 @@
---
name: slack-automation
-description: "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatically."
+description: "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica..."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Slack Automation via Rube MCP
@@ -187,3 +189,6 @@ Most list endpoints use cursor-based pagination:
| Get channel info | `SLACK_RETRIEVE_CONVERSATION_INFORMATION` | channel ID |
| Channel history | `SLACK_FETCH_CONVERSATION_HISTORY` | `channel`, `oldest`, `latest` |
| Workspace info | `SLACK_FETCH_TEAM_INFO` | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/slack-bot-builder/SKILL.md b/web-app/public/skills/slack-bot-builder/SKILL.md
index 8b8e7642..6f27bd89 100644
--- a/web-app/public/skills/slack-bot-builder/SKILL.md
+++ b/web-app/public/skills/slack-bot-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: slack-bot-builder
-description: "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and Workflow Builder integration. Focus on best practices for production-ready Slack apps. Use when: slack bot, slack app, bolt framework, block kit, slash command."
+description: "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Slack Bot Builder
@@ -262,3 +263,6 @@ app = App(
| Issue | medium | ## Know and respect the limits |
| Issue | high | ## Socket Mode: Only for development |
| Issue | critical | ## Bolt handles this automatically |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/slack-gif-creator/SKILL.md b/web-app/public/skills/slack-gif-creator/SKILL.md
index 16660d8c..31eb7884 100644
--- a/web-app/public/skills/slack-gif-creator/SKILL.md
+++ b/web-app/public/skills/slack-gif-creator/SKILL.md
@@ -1,7 +1,9 @@
---
name: slack-gif-creator
-description: Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."
+description: "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Slack GIF Creator
@@ -252,3 +254,6 @@ Be creative! Combine concepts (bouncing + rotating, pulsing + sliding, etc.) and
```bash
pip install pillow imageio numpy
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/slo-implementation/SKILL.md b/web-app/public/skills/slo-implementation/SKILL.md
index 91f3d6ac..47befb5c 100644
--- a/web-app/public/skills/slo-implementation/SKILL.md
+++ b/web-app/public/skills/slo-implementation/SKILL.md
@@ -1,6 +1,8 @@
---
name: slo-implementation
-description: Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
+description: "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m..."
+risk: unknown
+source: community
---
# SLO Implementation
diff --git a/web-app/public/skills/smtp-penetration-testing/SKILL.md b/web-app/public/skills/smtp-penetration-testing/SKILL.md
index 980d5052..f7d228fc 100644
--- a/web-app/public/skills/smtp-penetration-testing/SKILL.md
+++ b/web-app/public/skills/smtp-penetration-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: SMTP Penetration Testing
-description: This skill should be used when the user asks to "perform SMTP penetration testing", "enumerate email users", "test for open mail relays", "grab SMTP banners", "brute force email credentials", or "assess mail server security". It provides comprehensive techniques for testing SMTP server security.
+name: smtp-penetration-testing
+description: "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# SMTP Penetration Testing
@@ -498,3 +500,6 @@ nmap -p 25 --script smtp-open-relay --script-args smtp-open-relay.from=test@atta
8. **Log Monitoring** - Alert on suspicious activity
9. **Patch Management** - Keep SMTP software updated
10. **Access Controls** - Restrict SMTP to authorized IPs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/social-content/SKILL.md b/web-app/public/skills/social-content/SKILL.md
index 12fa7ef9..c0ae4ecf 100644
--- a/web-app/public/skills/social-content/SKILL.md
+++ b/web-app/public/skills/social-content/SKILL.md
@@ -1,6 +1,8 @@
---
name: social-content
-description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies."
+description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn..."
+risk: unknown
+source: community
---
# Social Content
@@ -805,3 +807,6 @@ If you need more context:
- **launch-strategy**: For coordinating social with launches
- **email-sequence**: For nurturing social audience via email
- **marketing-psychology**: For understanding what drives engagement
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/software-architecture/SKILL.md b/web-app/public/skills/software-architecture/SKILL.md
index d0514cd2..8d147dd4 100644
--- a/web-app/public/skills/software-architecture/SKILL.md
+++ b/web-app/public/skills/software-architecture/SKILL.md
@@ -1,6 +1,8 @@
---
name: software-architecture
-description: Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
+description: "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development."
+risk: unknown
+source: community
---
# Software Architecture Development Skill
@@ -73,3 +75,6 @@ This skill provides guidance for quality focused software development and archit
- Avoid deep nesting (max 3 levels)
- Keep functions focused and under 50 lines when possible
- Keep files focused and under 200 lines of code when possible
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/solidity-security/SKILL.md b/web-app/public/skills/solidity-security/SKILL.md
index 68760d30..6d340ac4 100644
--- a/web-app/public/skills/solidity-security/SKILL.md
+++ b/web-app/public/skills/solidity-security/SKILL.md
@@ -1,6 +1,8 @@
---
name: solidity-security
-description: Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
+description: "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin..."
+risk: unknown
+source: community
---
# Solidity Security
diff --git a/web-app/public/skills/spark-optimization/SKILL.md b/web-app/public/skills/spark-optimization/SKILL.md
index ad3e23c3..39d9e6a0 100644
--- a/web-app/public/skills/spark-optimization/SKILL.md
+++ b/web-app/public/skills/spark-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: spark-optimization
-description: Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.
+description: "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines."
+risk: unknown
+source: community
---
# Apache Spark Optimization
diff --git a/web-app/public/skills/sql-injection-testing/SKILL.md b/web-app/public/skills/sql-injection-testing/SKILL.md
index f51e5f24..5f388afa 100644
--- a/web-app/public/skills/sql-injection-testing/SKILL.md
+++ b/web-app/public/skills/sql-injection-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: SQL Injection Testing
-description: This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.
+name: sql-injection-testing
+description: "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# SQL Injection Testing
@@ -446,3 +448,6 @@ SELECT * FROM users WHERE username='administrator'--' AND password='anything'
- Use longer delays (10+ seconds) for clarity
- Run multiple tests to confirm pattern
- Consider server-side caching effects
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/sql-optimization-patterns/SKILL.md b/web-app/public/skills/sql-optimization-patterns/SKILL.md
index 2d076877..740c7c60 100644
--- a/web-app/public/skills/sql-optimization-patterns/SKILL.md
+++ b/web-app/public/skills/sql-optimization-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: sql-optimization-patterns
-description: Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
+description: "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database..."
+risk: unknown
+source: community
---
# SQL Optimization Patterns
diff --git a/web-app/public/skills/sql-pro/SKILL.md b/web-app/public/skills/sql-pro/SKILL.md
index b02720cb..ddb5a988 100644
--- a/web-app/public/skills/sql-pro/SKILL.md
+++ b/web-app/public/skills/sql-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: sql-pro
-description: Master modern SQL with cloud-native databases, OLTP/OLAP
+description: "Master modern SQL with cloud-native databases, OLTP/OLAP"
optimization, and advanced query techniques. Expert in performance tuning,
data modeling, and hybrid analytical systems. Use PROACTIVELY for database
optimization or complex analysis.
metadata:
model: inherit
+risk: unknown
+source: community
---
You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.
diff --git a/web-app/public/skills/sqlmap-database-pentesting/SKILL.md b/web-app/public/skills/sqlmap-database-pentesting/SKILL.md
index eb682bf7..c190d879 100644
--- a/web-app/public/skills/sqlmap-database-pentesting/SKILL.md
+++ b/web-app/public/skills/sqlmap-database-pentesting/SKILL.md
@@ -1,9 +1,11 @@
---
-name: SQLMap Database Penetration Testing
-description: This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
+name: sqlmap-database-pentesting
+description: "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# SQLMap Database Penetration Testing
@@ -398,3 +400,6 @@ sqlmap -u "URL" --dbs --batch --resume
# Use persistent HTTP connection
sqlmap -u "URL" --dbs --batch --keep-alive
```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/square-automation/SKILL.md b/web-app/public/skills/square-automation/SKILL.md
index 6fd77f88..9a7b6b90 100644
--- a/web-app/public/skills/square-automation/SKILL.md
+++ b/web-app/public/skills/square-automation/SKILL.md
@@ -3,6 +3,8 @@ name: square-automation
description: "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Square Automation via Rube MCP
@@ -174,3 +176,6 @@ Automate Square payment processing, order management, and invoicing through Comp
| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |
| Get invoice | SQUARE_GET_INVOICE | invoice_id |
| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ssh-penetration-testing/SKILL.md b/web-app/public/skills/ssh-penetration-testing/SKILL.md
index 9cc9f998..c7f86a2a 100644
--- a/web-app/public/skills/ssh-penetration-testing/SKILL.md
+++ b/web-app/public/skills/ssh-penetration-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: SSH Penetration Testing
-description: This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tunneling", or "audit SSH security". It provides comprehensive SSH penetration testing methodologies and techniques.
+name: ssh-penetration-testing
+description: "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# SSH Penetration Testing
@@ -486,3 +488,6 @@ sessions -i 1
| Connection Refused | Verify SSH running; check firewall; confirm port; test from different IP |
| Authentication Failures | Verify username; check password policy; key permissions (600); authorized_keys format |
| Tunnel Not Working | Check GatewayPorts/AllowTcpForwarding in sshd_config; verify firewall; use `ssh -v` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/startup-analyst/SKILL.md b/web-app/public/skills/startup-analyst/SKILL.md
index c972ee35..9dd9fbe9 100644
--- a/web-app/public/skills/startup-analyst/SKILL.md
+++ b/web-app/public/skills/startup-analyst/SKILL.md
@@ -1,6 +1,6 @@
---
name: startup-analyst
-description: Expert startup business analyst specializing in market sizing,
+description: "Expert startup business analyst specializing in market sizing,"
financial modeling, competitive analysis, and strategic planning for
early-stage companies. Use PROACTIVELY when the user asks about market
opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive
@@ -8,6 +8,8 @@ description: Expert startup business analyst specializing in market sizing,
through Series A startups.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/startup-business-analyst-business-case/SKILL.md b/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
index 9f95d47c..7e21641c 100644
--- a/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
@@ -1,8 +1,10 @@
---
name: startup-business-analyst-business-case
-description: Generate comprehensive investor-ready business case document with
+description: "Generate comprehensive investor-ready business case document with"
market, solution, financials, and strategy
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+risk: unknown
+source: community
---
# Business Case Generator
diff --git a/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md b/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
index 7bf52b2b..1e09b5db 100644
--- a/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
@@ -1,8 +1,10 @@
---
name: startup-business-analyst-financial-projections
-description: Create detailed 3-5 year financial model with revenue, costs, cash
+description: "Create detailed 3-5 year financial model with revenue, costs, cash"
flow, and scenarios
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+risk: unknown
+source: community
---
# Financial Projections
diff --git a/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md b/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
index 7301f026..013d551a 100644
--- a/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
@@ -1,8 +1,10 @@
---
name: startup-business-analyst-market-opportunity
-description: Generate comprehensive market opportunity analysis with TAM/SAM/SOM
+description: "Generate comprehensive market opportunity analysis with TAM/SAM/SOM"
calculations
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+risk: unknown
+source: community
---
# Market Opportunity Analysis
diff --git a/web-app/public/skills/startup-financial-modeling/SKILL.md b/web-app/public/skills/startup-financial-modeling/SKILL.md
index d127d4d5..4921e7ea 100644
--- a/web-app/public/skills/startup-financial-modeling/SKILL.md
+++ b/web-app/public/skills/startup-financial-modeling/SKILL.md
@@ -1,11 +1,13 @@
---
name: startup-financial-modeling
-description: This skill should be used when the user asks to "create financial
+description: "This skill should be used when the user asks to \\\"create financial"
projections", "build a financial model", "forecast revenue", "calculate burn
rate", "estimate runway", "model cash flow", or requests 3-5 year financial
planning for a startup.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Startup Financial Modeling
diff --git a/web-app/public/skills/startup-metrics-framework/SKILL.md b/web-app/public/skills/startup-metrics-framework/SKILL.md
index dcc1754a..7c8acdc3 100644
--- a/web-app/public/skills/startup-metrics-framework/SKILL.md
+++ b/web-app/public/skills/startup-metrics-framework/SKILL.md
@@ -1,11 +1,13 @@
---
name: startup-metrics-framework
-description: This skill should be used when the user asks about "key startup
+description: "This skill should be used when the user asks about \\\"key startup"
metrics", "SaaS metrics", "CAC and LTV", "unit economics", "burn multiple",
"rule of 40", "marketplace metrics", or requests guidance on tracking and
optimizing business performance metrics.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Startup Metrics Framework
diff --git a/web-app/public/skills/stitch-ui-design/SKILL.md b/web-app/public/skills/stitch-ui-design/SKILL.md
index ffea5043..f6bd81c0 100644
--- a/web-app/public/skills/stitch-ui-design/SKILL.md
+++ b/web-app/public/skills/stitch-ui-design/SKILL.md
@@ -1,6 +1,6 @@
---
name: stitch-ui-design
-description: Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.
+description: "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra..."
risk: safe
source: "self"
---
@@ -376,3 +376,6 @@ design with purple/teal gradient accents and dark mode support.
Effective Stitch prompts are specific, context-rich, and visually descriptive. By following these principles and templates, you can generate professional UI designs that serve as strong foundations for production applications.
**Remember:** Stitch is a starting point, not a final product. Use it to accelerate the design process, explore ideas quickly, and establish visual direction—then refine with human judgment and production standards.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/stride-analysis-patterns/SKILL.md b/web-app/public/skills/stride-analysis-patterns/SKILL.md
index 66b1aaff..6888c612 100644
--- a/web-app/public/skills/stride-analysis-patterns/SKILL.md
+++ b/web-app/public/skills/stride-analysis-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: stride-analysis-patterns
-description: Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
+description: "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation."
+risk: unknown
+source: community
---
# STRIDE Analysis Patterns
diff --git a/web-app/public/skills/stripe-automation/SKILL.md b/web-app/public/skills/stripe-automation/SKILL.md
index 8128b6a5..1b8dc71d 100644
--- a/web-app/public/skills/stripe-automation/SKILL.md
+++ b/web-app/public/skills/stripe-automation/SKILL.md
@@ -3,6 +3,8 @@ name: stripe-automation
description: "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Stripe Automation via Rube MCP
@@ -196,3 +198,6 @@ Stripe uses smallest currency unit:
| Payment methods | STRIPE_LIST_CUSTOMER_PAYMENT_METHODS | customer |
| Checkout session | STRIPE_CREATE_CHECKOUT_SESSION | line_items |
| List payment intents | STRIPE_LIST_PAYMENT_INTENTS | customer |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/stripe-integration/SKILL.md b/web-app/public/skills/stripe-integration/SKILL.md
index 5ad98e49..df8bb981 100644
--- a/web-app/public/skills/stripe-integration/SKILL.md
+++ b/web-app/public/skills/stripe-integration/SKILL.md
@@ -1,6 +1,8 @@
---
name: stripe-integration
-description: Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
+description: "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ..."
+risk: unknown
+source: community
---
# Stripe Integration
diff --git a/web-app/public/skills/subagent-driven-development/SKILL.md b/web-app/public/skills/subagent-driven-development/SKILL.md
index a9a94547..761682fc 100644
--- a/web-app/public/skills/subagent-driven-development/SKILL.md
+++ b/web-app/public/skills/subagent-driven-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: subagent-driven-development
-description: Use when executing implementation plans with independent tasks in the current session
+description: "Use when executing implementation plans with independent tasks in the current session"
+risk: unknown
+source: community
---
# Subagent-Driven Development
diff --git a/web-app/public/skills/supabase-automation/SKILL.md b/web-app/public/skills/supabase-automation/SKILL.md
index 1b96b9bb..0aa88373 100644
--- a/web-app/public/skills/supabase-automation/SKILL.md
+++ b/web-app/public/skills/supabase-automation/SKILL.md
@@ -3,6 +3,8 @@ name: supabase-automation
description: "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Supabase Automation via Rube MCP
@@ -234,3 +236,6 @@ Automate Supabase operations including database queries, table schema inspection
| Get edge function | `SUPABASE_RETRIEVE_A_FUNCTION` | `ref`, function slug |
| List storage buckets | `SUPABASE_LISTS_ALL_BUCKETS` | `ref` |
| List DB branches | `SUPABASE_LIST_ALL_DATABASE_BRANCHES` | `ref` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/swiftui-expert-skill/SKILL.md b/web-app/public/skills/swiftui-expert-skill/SKILL.md
index 4cbb9043..b13f8438 100644
--- a/web-app/public/skills/swiftui-expert-skill/SKILL.md
+++ b/web-app/public/skills/swiftui-expert-skill/SKILL.md
@@ -1,6 +1,6 @@
---
name: swiftui-expert-skill
-description: "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns."
+description: "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil..."
source: "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill"
risk: safe
---
diff --git a/web-app/public/skills/systematic-debugging/SKILL.md b/web-app/public/skills/systematic-debugging/SKILL.md
index 111d2a98..3c608595 100644
--- a/web-app/public/skills/systematic-debugging/SKILL.md
+++ b/web-app/public/skills/systematic-debugging/SKILL.md
@@ -1,6 +1,8 @@
---
name: systematic-debugging
-description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
+description: "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes"
+risk: unknown
+source: community
---
# Systematic Debugging
diff --git a/web-app/public/skills/systems-programming-rust-project/SKILL.md b/web-app/public/skills/systems-programming-rust-project/SKILL.md
index cc185ad4..c4cb27dd 100644
--- a/web-app/public/skills/systems-programming-rust-project/SKILL.md
+++ b/web-app/public/skills/systems-programming-rust-project/SKILL.md
@@ -1,6 +1,8 @@
---
name: systems-programming-rust-project
description: "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing"
+risk: unknown
+source: community
---
# Rust Project Scaffolding
diff --git a/web-app/public/skills/tailwind-design-system/SKILL.md b/web-app/public/skills/tailwind-design-system/SKILL.md
index d6d650e8..fb66f7e0 100644
--- a/web-app/public/skills/tailwind-design-system/SKILL.md
+++ b/web-app/public/skills/tailwind-design-system/SKILL.md
@@ -1,6 +1,8 @@
---
name: tailwind-design-system
-description: Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
+description: "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI..."
+risk: unknown
+source: community
---
# Tailwind Design System
diff --git a/web-app/public/skills/tailwind-patterns/SKILL.md b/web-app/public/skills/tailwind-patterns/SKILL.md
index a5830a86..c0170b4c 100644
--- a/web-app/public/skills/tailwind-patterns/SKILL.md
+++ b/web-app/public/skills/tailwind-patterns/SKILL.md
@@ -1,13 +1,19 @@
---
name: tailwind-patterns
-description: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
+description: "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture."
allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
---
# Tailwind CSS Patterns (v4 - 2025)
> Modern utility-first CSS with CSS-native configuration.
+## When to Use
+
+Use this skill when configuring Tailwind v4, using CSS-first theme and design tokens, or implementing container queries and modern Tailwind patterns.
+
---
## 1. Tailwind v4 Architecture
diff --git a/web-app/public/skills/tavily-web/SKILL.md b/web-app/public/skills/tavily-web/SKILL.md
index 0fea07b9..ef964705 100644
--- a/web-app/public/skills/tavily-web/SKILL.md
+++ b/web-app/public/skills/tavily-web/SKILL.md
@@ -1,6 +1,8 @@
---
name: tavily-web
-description: Web search, content extraction, crawling, and research capabilities using Tavily API
+description: "Web search, content extraction, crawling, and research capabilities using Tavily API"
+risk: unknown
+source: community
---
# tavily-web
diff --git a/web-app/public/skills/tdd-orchestrator/SKILL.md b/web-app/public/skills/tdd-orchestrator/SKILL.md
index 3eae429d..5878ac1c 100644
--- a/web-app/public/skills/tdd-orchestrator/SKILL.md
+++ b/web-app/public/skills/tdd-orchestrator/SKILL.md
@@ -1,12 +1,14 @@
---
name: tdd-orchestrator
-description: Master TDD orchestrator specializing in red-green-refactor
+description: "Master TDD orchestrator specializing in red-green-refactor"
discipline, multi-agent workflow coordination, and comprehensive test-driven
development practices. Enforces TDD best practices across teams with
AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD
implementation and governance.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/tdd-workflow/SKILL.md b/web-app/public/skills/tdd-workflow/SKILL.md
index ddb07e80..a8249766 100644
--- a/web-app/public/skills/tdd-workflow/SKILL.md
+++ b/web-app/public/skills/tdd-workflow/SKILL.md
@@ -1,7 +1,9 @@
---
name: tdd-workflow
-description: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
+description: "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle."
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
---
# TDD Workflow
@@ -147,3 +149,6 @@ Every test follows:
---
> **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/tdd-workflows-tdd-cycle/SKILL.md b/web-app/public/skills/tdd-workflows-tdd-cycle/SKILL.md
index bdce6b14..e41222b1 100644
--- a/web-app/public/skills/tdd-workflows-tdd-cycle/SKILL.md
+++ b/web-app/public/skills/tdd-workflows-tdd-cycle/SKILL.md
@@ -1,6 +1,8 @@
---
name: tdd-workflows-tdd-cycle
description: "Use when working with tdd workflows tdd cycle"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/tdd-workflows-tdd-green/SKILL.md b/web-app/public/skills/tdd-workflows-tdd-green/SKILL.md
index 3b26eea4..cdb85e1e 100644
--- a/web-app/public/skills/tdd-workflows-tdd-green/SKILL.md
+++ b/web-app/public/skills/tdd-workflows-tdd-green/SKILL.md
@@ -1,6 +1,8 @@
---
name: tdd-workflows-tdd-green
-description: Implement the minimal code needed to make failing tests pass in the TDD green phase.
+description: "Implement the minimal code needed to make failing tests pass in the TDD green phase."
+risk: unknown
+source: community
---
# Green Phase: Simple function
diff --git a/web-app/public/skills/tdd-workflows-tdd-red/SKILL.md b/web-app/public/skills/tdd-workflows-tdd-red/SKILL.md
index 0d7e4dad..2f3ead3f 100644
--- a/web-app/public/skills/tdd-workflows-tdd-red/SKILL.md
+++ b/web-app/public/skills/tdd-workflows-tdd-red/SKILL.md
@@ -1,6 +1,8 @@
---
name: tdd-workflows-tdd-red
-description: Generate failing tests for the TDD red phase to define expected behavior and edge cases.
+description: "Generate failing tests for the TDD red phase to define expected behavior and edge cases."
+risk: unknown
+source: community
---
Write comprehensive failing tests following TDD red phase principles.
diff --git a/web-app/public/skills/tdd-workflows-tdd-refactor/SKILL.md b/web-app/public/skills/tdd-workflows-tdd-refactor/SKILL.md
index 64aee6bb..ec8f5022 100644
--- a/web-app/public/skills/tdd-workflows-tdd-refactor/SKILL.md
+++ b/web-app/public/skills/tdd-workflows-tdd-refactor/SKILL.md
@@ -1,6 +1,8 @@
---
name: tdd-workflows-tdd-refactor
description: "Use when working with tdd workflows tdd refactor"
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/team-collaboration-issue/SKILL.md b/web-app/public/skills/team-collaboration-issue/SKILL.md
index 7899a1f6..d0e2775f 100644
--- a/web-app/public/skills/team-collaboration-issue/SKILL.md
+++ b/web-app/public/skills/team-collaboration-issue/SKILL.md
@@ -1,6 +1,8 @@
---
name: team-collaboration-issue
description: "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an"
+risk: unknown
+source: community
---
# GitHub Issue Resolution Expert
diff --git a/web-app/public/skills/team-collaboration-standup-notes/SKILL.md b/web-app/public/skills/team-collaboration-standup-notes/SKILL.md
index 8f0e1500..eb9780d4 100644
--- a/web-app/public/skills/team-collaboration-standup-notes/SKILL.md
+++ b/web-app/public/skills/team-collaboration-standup-notes/SKILL.md
@@ -1,6 +1,8 @@
---
name: team-collaboration-standup-notes
description: "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns."
+risk: unknown
+source: community
---
# Standup Notes Generator
diff --git a/web-app/public/skills/team-collaboration-standup-notes/resources/implementation-playbook.md b/web-app/public/skills/team-collaboration-standup-notes/resources/implementation-playbook.md
index 151ffdde..f9b1e0ad 100644
--- a/web-app/public/skills/team-collaboration-standup-notes/resources/implementation-playbook.md
+++ b/web-app/public/skills/team-collaboration-standup-notes/resources/implementation-playbook.md
@@ -266,7 +266,7 @@ obsidian_get_recent_periodic_notes --period daily --limit 2 | \
• Need staging database access for migration testing - @infra-team
## 📎 Links
-• [PR #789](link) | [JIRA Sprint Board](link)
+• PR #789 | JIRA Sprint Board
```
**Thread-Based Standup:**
@@ -351,7 +351,7 @@ From standup notes, automatically extract:
• Taking tomorrow afternoon off (dentist appointment) - Will post morning standup but limited availability after 12pm
• Mobile responsiveness research doc started: [Link to Notion doc]
-📎 [Sprint Board](link) | [My Active PRs](link)
+📎 Sprint Board | My Active PRs
```
### Example 2: AI-Generated Standup from Git History
@@ -527,7 +527,7 @@ jira issues list --assignee currentUser() --status "In Progress"
• Heads up: Deploying migration to staging at noon, expect ~10min downtime
**🔗 Links**
-• [Active PRs](link) | [Sprint Board](link) | [Migration Runbook](link)
+• Active PRs | Sprint Board | Migration Runbook
---
👀 = I've read this | 🤝 = I can help with something | 💬 = Reply in thread
diff --git a/web-app/public/skills/team-composition-analysis/SKILL.md b/web-app/public/skills/team-composition-analysis/SKILL.md
index 28c5c9e8..9ce88e72 100644
--- a/web-app/public/skills/team-composition-analysis/SKILL.md
+++ b/web-app/public/skills/team-composition-analysis/SKILL.md
@@ -1,11 +1,13 @@
---
name: team-composition-analysis
-description: This skill should be used when the user asks to "plan team
+description: "This skill should be used when the user asks to \\\"plan team"
structure", "determine hiring needs", "design org chart", "calculate
compensation", "plan equity allocation", or requests organizational design and
headcount planning for a startup.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Team Composition Analysis
diff --git a/web-app/public/skills/telegram-automation/SKILL.md b/web-app/public/skills/telegram-automation/SKILL.md
index e2079cb2..2a9bd616 100644
--- a/web-app/public/skills/telegram-automation/SKILL.md
+++ b/web-app/public/skills/telegram-automation/SKILL.md
@@ -3,6 +3,8 @@ name: telegram-automation
description: "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Telegram Automation via Rube MCP
@@ -217,3 +219,6 @@ Automate Telegram operations through Composio's Telegram toolkit via Rube MCP.
| Get chat history | TELEGRAM_GET_CHAT_HISTORY | chat_id |
| Set bot commands | TELEGRAM_SET_MY_COMMANDS | commands |
| Answer callback | TELEGRAM_ANSWER_CALLBACK_QUERY | callback_query_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/telegram-bot-builder/SKILL.md b/web-app/public/skills/telegram-bot-builder/SKILL.md
index 9f6adf1e..6ec84f46 100644
--- a/web-app/public/skills/telegram-bot-builder/SKILL.md
+++ b/web-app/public/skills/telegram-bot-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: telegram-bot-builder
-description: "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot."
+description: "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Telegram Bot Builder
@@ -252,3 +253,6 @@ Quality over quantity.
## Related Skills
Works well with: `telegram-mini-app`, `backend`, `ai-wrapper-product`, `workflow-automation`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/telegram-mini-app/SKILL.md b/web-app/public/skills/telegram-mini-app/SKILL.md
index 53891869..ad7660a9 100644
--- a/web-app/public/skills/telegram-mini-app/SKILL.md
+++ b/web-app/public/skills/telegram-mini-app/SKILL.md
@@ -1,7 +1,8 @@
---
name: telegram-mini-app
-description: "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app."
+description: "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Telegram Mini App
@@ -277,3 +278,6 @@ Optimistic updates.
## Related Skills
Works well with: `telegram-bot-builder`, `frontend`, `blockchain-defi`, `viral-generator-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/temporal-python-pro/SKILL.md b/web-app/public/skills/temporal-python-pro/SKILL.md
index 81215706..261fa049 100644
--- a/web-app/public/skills/temporal-python-pro/SKILL.md
+++ b/web-app/public/skills/temporal-python-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: temporal-python-pro
-description: Master Temporal workflow orchestration with Python SDK. Implements
+description: "Master Temporal workflow orchestration with Python SDK. Implements"
durable workflows, saga patterns, and distributed transactions. Covers
async/await, testing strategies, and production deployment. Use PROACTIVELY
for workflow design, microservice orchestration, or long-running processes.
metadata:
model: inherit
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/temporal-python-testing/SKILL.md b/web-app/public/skills/temporal-python-testing/SKILL.md
index e61fc6c9..099c71a6 100644
--- a/web-app/public/skills/temporal-python-testing/SKILL.md
+++ b/web-app/public/skills/temporal-python-testing/SKILL.md
@@ -1,6 +1,8 @@
---
name: temporal-python-testing
-description: Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
+description: "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor..."
+risk: unknown
+source: community
---
# Temporal Python Testing Strategies
diff --git a/web-app/public/skills/terraform-aws-modules/SKILL.md b/web-app/public/skills/terraform-aws-modules/SKILL.md
new file mode 100644
index 00000000..afb077d3
--- /dev/null
+++ b/web-app/public/skills/terraform-aws-modules/SKILL.md
@@ -0,0 +1,79 @@
+---
+name: terraform-aws-modules
+description: "Terraform module creation for AWS — reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure."
+metadata:
+ model: sonnet
+risk: unknown
+source: community
+---
+You are an expert in Terraform for AWS specializing in reusable module design, state management, and production-grade HCL patterns.
+
+## Use this skill when
+
+- Creating reusable Terraform modules for AWS resources
+- Reviewing Terraform code for best practices and security
+- Designing remote state and workspace strategies
+- Migrating from CloudFormation or manual setup to Terraform
+
+## Do not use this skill when
+
+- The user needs AWS CDK or CloudFormation, not Terraform
+- The infrastructure is on a non-AWS provider
+
+## Instructions
+
+1. Structure modules with clear `variables.tf`, `outputs.tf`, `main.tf`, and `versions.tf`.
+2. Pin provider and module versions to avoid breaking changes.
+3. Use remote state (S3 + DynamoDB locking) for team environments.
+4. Apply `terraform fmt` and `terraform validate` before commits.
+5. Use `for_each` over `count` for resources that need stable identity.
+6. Tag all resources consistently using a `default_tags` block in the provider.
+
+## Examples
+
+### Example 1: Reusable VPC Module
+
+```hcl
+# modules/vpc/variables.tf
+variable "name" { type = string }
+variable "cidr" { type = string, default = "10.0.0.0/16" }
+variable "azs" { type = list(string) }
+
+# modules/vpc/main.tf
+resource "aws_vpc" "this" {
+ cidr_block = var.cidr
+ enable_dns_support = true
+ enable_dns_hostnames = true
+ tags = { Name = var.name }
+}
+
+# modules/vpc/outputs.tf
+output "vpc_id" { value = aws_vpc.this.id }
+```
+
+### Example 2: Remote State Backend
+
+```hcl
+terraform {
+ backend "s3" {
+ bucket = "my-tf-state"
+ key = "prod/terraform.tfstate"
+ region = "us-east-1"
+ dynamodb_table = "tf-lock"
+ encrypt = true
+ }
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Pin provider versions in `versions.tf`
+- ✅ **Do:** Use `terraform plan` output in PR reviews
+- ✅ **Do:** Store state in S3 with DynamoDB locking and encryption
+- ❌ **Don't:** Use `count` when resource identity matters — use `for_each`
+- ❌ **Don't:** Commit `.tfstate` files to version control
+
+## Troubleshooting
+
+**Problem:** State lock not released after a failed apply
+**Solution:** Run `terraform force-unlock ` after confirming no other operations are running.
diff --git a/web-app/public/skills/terraform-infrastructure/SKILL.md b/web-app/public/skills/terraform-infrastructure/SKILL.md
new file mode 100644
index 00000000..5f88d102
--- /dev/null
+++ b/web-app/public/skills/terraform-infrastructure/SKILL.md
@@ -0,0 +1,164 @@
+---
+name: terraform-infrastructure
+description: "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale."
+source: personal
+risk: safe
+domain: cloud-devops
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Terraform Infrastructure Workflow
+
+## Overview
+
+Specialized workflow for infrastructure as code using Terraform including resource provisioning, module creation, state management, and multi-environment deployments.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Provisioning cloud infrastructure
+- Creating Terraform modules
+- Managing multi-environment infra
+- Implementing IaC best practices
+- Setting up Terraform workflows
+
+## Workflow Phases
+
+### Phase 1: Terraform Setup
+
+#### Skills to Invoke
+- `terraform-skill` - Terraform basics
+- `terraform-specialist` - Advanced Terraform
+
+#### Actions
+1. Initialize Terraform
+2. Configure backend
+3. Set up providers
+4. Configure variables
+5. Create outputs
+
+#### Copy-Paste Prompts
+```
+Use @terraform-skill to set up Terraform project
+```
+
+### Phase 2: Resource Provisioning
+
+#### Skills to Invoke
+- `terraform-module-library` - Terraform modules
+- `cloud-architect` - Cloud architecture
+
+#### Actions
+1. Design infrastructure
+2. Create resource definitions
+3. Configure networking
+4. Set up compute
+5. Add storage
+
+#### Copy-Paste Prompts
+```
+Use @terraform-module-library to provision cloud resources
+```
+
+### Phase 3: Module Creation
+
+#### Skills to Invoke
+- `terraform-module-library` - Module creation
+
+#### Actions
+1. Design module interface
+2. Create module structure
+3. Define variables/outputs
+4. Add documentation
+5. Test module
+
+#### Copy-Paste Prompts
+```
+Use @terraform-module-library to create reusable Terraform module
+```
+
+### Phase 4: State Management
+
+#### Skills to Invoke
+- `terraform-specialist` - State management
+
+#### Actions
+1. Configure remote backend
+2. Set up state locking
+3. Implement workspaces
+4. Configure state access
+5. Set up backup
+
+#### Copy-Paste Prompts
+```
+Use @terraform-specialist to configure Terraform state
+```
+
+### Phase 5: Multi-Environment
+
+#### Skills to Invoke
+- `terraform-specialist` - Multi-environment
+
+#### Actions
+1. Design environment structure
+2. Create environment configs
+3. Set up variable files
+4. Configure isolation
+5. Test deployments
+
+#### Copy-Paste Prompts
+```
+Use @terraform-specialist to set up multi-environment Terraform
+```
+
+### Phase 6: CI/CD Integration
+
+#### Skills to Invoke
+- `cicd-automation-workflow-automate` - CI/CD
+- `github-actions-templates` - GitHub Actions
+
+#### Actions
+1. Create CI pipeline
+2. Configure plan/apply
+3. Set up approvals
+4. Add validation
+5. Test pipeline
+
+#### Copy-Paste Prompts
+```
+Use @cicd-automation-workflow-automate to create Terraform CI/CD
+```
+
+### Phase 7: Security
+
+#### Skills to Invoke
+- `secrets-management` - Secrets management
+- `terraform-specialist` - Security
+
+#### Actions
+1. Configure secrets
+2. Set up encryption
+3. Implement policies
+4. Add compliance
+5. Audit access
+
+#### Copy-Paste Prompts
+```
+Use @secrets-management to secure Terraform secrets
+```
+
+## Quality Gates
+
+- [ ] Resources provisioned
+- [ ] Modules working
+- [ ] State configured
+- [ ] Multi-env tested
+- [ ] CI/CD working
+- [ ] Security verified
+
+## Related Workflow Bundles
+
+- `cloud-devops` - Cloud/DevOps
+- `kubernetes-deployment` - Kubernetes
+- `aws-infrastructure` - AWS specific
diff --git a/web-app/public/skills/terraform-module-library/SKILL.md b/web-app/public/skills/terraform-module-library/SKILL.md
index 4ea8937c..b0aa3720 100644
--- a/web-app/public/skills/terraform-module-library/SKILL.md
+++ b/web-app/public/skills/terraform-module-library/SKILL.md
@@ -1,6 +1,8 @@
---
name: terraform-module-library
-description: Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
+description: "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ..."
+risk: unknown
+source: community
---
# Terraform Module Library
diff --git a/web-app/public/skills/terraform-skill/SKILL.md b/web-app/public/skills/terraform-skill/SKILL.md
index 460ae575..216125bd 100644
--- a/web-app/public/skills/terraform-skill/SKILL.md
+++ b/web-app/public/skills/terraform-skill/SKILL.md
@@ -64,7 +64,7 @@ examples/ # Module usage examples (also serve as tests)
- Use **examples/** as both documentation and integration test fixtures
- Keep modules small and focused (single responsibility)
-**For detailed module architecture, see:** [Code Patterns: Module Types & Hierarchy](references/code-patterns.md)
+**For detailed module architecture, see:** Code Patterns: Module Types & Hierarchy
### 2. Naming Conventions
@@ -168,8 +168,8 @@ var.database_instance_class # Not just "instance_class"
- IAM policy statements: **set** (use for expressions)
**For detailed testing guides, see:**
-- **[Testing Frameworks Guide](references/testing-frameworks.md)** - Deep dive into static analysis, native tests, and Terratest
-- **[Quick Reference](references/quick-reference.md#testing-approach-selection)** - Decision flowchart and command cheat sheet
+- **Testing Frameworks Guide** - Deep dive into static analysis, native tests, and Terratest
+- **Quick Reference** - Decision flowchart and command cheat sheet
## Code Structure Standards
@@ -225,7 +225,7 @@ variable "environment" {
}
```
-**For complete structure guidelines, see:** [Code Patterns: Block Ordering & Structure](references/code-patterns.md#block-ordering--structure)
+**For complete structure guidelines, see:** Code Patterns: Block Ordering & Structure
## Count vs For_Each: When to Use Each
@@ -269,7 +269,7 @@ resource "aws_subnet" "private" {
}
```
-**For migration guides and detailed examples, see:** [Code Patterns: Count vs For_Each](references/code-patterns.md#count-vs-for_each-deep-dive)
+**For migration guides and detailed examples, see:** Code Patterns: Count vs For_Each
## Locals for Dependency Management
@@ -311,7 +311,7 @@ resource "aws_subnet" "public" {
- Ensures correct dependency order without explicit `depends_on`
- Particularly useful for VPC configurations with secondary CIDR blocks
-**For detailed examples, see:** [Code Patterns: Locals for Dependency Management](references/code-patterns.md#locals-for-dependency-management)
+**For detailed examples, see:** Code Patterns: Locals for Dependency Management
## Module Development
@@ -347,8 +347,8 @@ my-module/
- ✅ Document what consumers should do with each output
**For detailed module patterns, see:**
-- **[Module Patterns Guide](references/module-patterns.md)** - Variable best practices, output design, ✅ DO vs ❌ DON'T patterns
-- **[Quick Reference](references/quick-reference.md#common-patterns)** - Resource naming, variable naming, file organization
+- **Module Patterns Guide** - Variable best practices, output design, ✅ DO vs ❌ DON'T patterns
+- **Quick Reference** - Resource naming, variable naming, file organization
## CI/CD Integration
@@ -367,8 +367,8 @@ my-module/
4. **Tag all test resources** (track spending)
**For complete CI/CD templates, see:**
-- **[CI/CD Workflows Guide](references/ci-cd-workflows.md)** - GitHub Actions, GitLab CI, Atlantis integration, cost optimization
-- **[Quick Reference](references/quick-reference.md#troubleshooting-guide)** - Common CI/CD issues and solutions
+- **CI/CD Workflows Guide** - GitHub Actions, GitLab CI, Atlantis integration, cost optimization
+- **Quick Reference** - Common CI/CD issues and solutions
## Security & Compliance
@@ -395,7 +395,7 @@ checkov -d .
- Use least-privilege security groups
**For detailed security guidance, see:**
-- **[Security & Compliance Guide](references/security-compliance.md)** - Trivy/Checkov integration, secrets management, state file security, compliance testing
+- **Security & Compliance Guide** - Trivy/Checkov integration, secrets management, state file security, compliance testing
## Version Management
@@ -429,7 +429,7 @@ terraform init -upgrade # Updates providers
terraform plan
```
-**For detailed version management, see:** [Code Patterns: Version Management](references/code-patterns.md#version-management)
+**For detailed version management, see:** Code Patterns: Version Management
## Modern Terraform Features (1.0+)
@@ -474,7 +474,7 @@ variable "backup_days" {
}
```
-**For complete patterns and examples, see:** [Code Patterns: Modern Terraform Features](references/code-patterns.md#modern-terraform-features-10)
+**For complete patterns and examples, see:** Code Patterns: Modern Terraform Features
## Version-Specific Guidance
@@ -495,18 +495,18 @@ variable "backup_days" {
### Terraform vs OpenTofu
-Both are fully supported by this skill. For licensing, governance, and feature comparison, see [Quick Reference: Terraform vs OpenTofu](references/quick-reference.md#terraform-vs-opentofu-comparison).
+Both are fully supported by this skill. For licensing, governance, and feature comparison, see Quick Reference: Terraform vs OpenTofu.
## Detailed Guides
This skill uses **progressive disclosure** - essential information is in this main file, detailed guides are available when needed:
📚 **Reference Files:**
-- **[Testing Frameworks](references/testing-frameworks.md)** - In-depth guide to static analysis, native tests, and Terratest
-- **[Module Patterns](references/module-patterns.md)** - Module structure, variable/output best practices, ✅ DO vs ❌ DON'T patterns
-- **[CI/CD Workflows](references/ci-cd-workflows.md)** - GitHub Actions, GitLab CI templates, cost optimization, automated cleanup
-- **[Security & Compliance](references/security-compliance.md)** - Trivy/Checkov integration, secrets management, compliance testing
-- **[Quick Reference](references/quick-reference.md)** - Command cheat sheets, decision flowcharts, troubleshooting guide
+- **Testing Frameworks** - In-depth guide to static analysis, native tests, and Terratest
+- **Module Patterns** - Module structure, variable/output best practices, ✅ DO vs ❌ DON'T patterns
+- **CI/CD Workflows** - GitHub Actions, GitLab CI templates, cost optimization, automated cleanup
+- **Security & Compliance** - Trivy/Checkov integration, secrets management, compliance testing
+- **Quick Reference** - Command cheat sheets, decision flowcharts, troubleshooting guide
**How to use:** When you need detailed information on a topic, reference the appropriate guide. Claude will load it on demand to provide comprehensive guidance.
diff --git a/web-app/public/skills/terraform-specialist/SKILL.md b/web-app/public/skills/terraform-specialist/SKILL.md
index 453cc433..146087f7 100644
--- a/web-app/public/skills/terraform-specialist/SKILL.md
+++ b/web-app/public/skills/terraform-specialist/SKILL.md
@@ -1,6 +1,6 @@
---
name: terraform-specialist
-description: Expert Terraform/OpenTofu specialist mastering advanced IaC
+description: "Expert Terraform/OpenTofu specialist mastering advanced IaC"
automation, state management, and enterprise infrastructure patterns. Handles
complex module design, multi-cloud deployments, GitOps workflows, policy as
code, and CI/CD integration. Covers migration strategies, security best
@@ -8,6 +8,8 @@ description: Expert Terraform/OpenTofu specialist mastering advanced IaC
management, or infrastructure automation.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.
diff --git a/web-app/public/skills/test-automator/SKILL.md b/web-app/public/skills/test-automator/SKILL.md
index f3384b9a..e5fb2b0e 100644
--- a/web-app/public/skills/test-automator/SKILL.md
+++ b/web-app/public/skills/test-automator/SKILL.md
@@ -1,11 +1,13 @@
---
name: test-automator
-description: Master AI-powered test automation with modern frameworks,
+description: "Master AI-powered test automation with modern frameworks,"
self-healing tests, and comprehensive quality engineering. Build scalable
testing strategies with advanced CI/CD integration. Use PROACTIVELY for
testing automation or quality assurance.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/test-driven-development/SKILL.md b/web-app/public/skills/test-driven-development/SKILL.md
index 7a751fa9..ac96d7a7 100644
--- a/web-app/public/skills/test-driven-development/SKILL.md
+++ b/web-app/public/skills/test-driven-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: test-driven-development
-description: Use when implementing any feature or bugfix, before writing implementation code
+description: "Use when implementing any feature or bugfix, before writing implementation code"
+risk: unknown
+source: community
---
# Test-Driven Development (TDD)
diff --git a/web-app/public/skills/test-fixing/SKILL.md b/web-app/public/skills/test-fixing/SKILL.md
index 2a435fd8..c95670d4 100644
--- a/web-app/public/skills/test-fixing/SKILL.md
+++ b/web-app/public/skills/test-fixing/SKILL.md
@@ -1,6 +1,8 @@
---
name: test-fixing
-description: Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
+description: "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma..."
+risk: unknown
+source: community
---
# Test Fixing
diff --git a/web-app/public/skills/testing-patterns/SKILL.md b/web-app/public/skills/testing-patterns/SKILL.md
index 45de878e..7e274f64 100644
--- a/web-app/public/skills/testing-patterns/SKILL.md
+++ b/web-app/public/skills/testing-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: testing-patterns
-description: Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
+description: "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle."
+risk: unknown
+source: community
---
# Testing Patterns and Utilities
@@ -257,3 +259,6 @@ npm test ComponentName.test.tsx
- **react-ui-patterns**: Test all UI states (loading, error, empty, success)
- **systematic-debugging**: Write test that reproduces bug before fixing
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/testing-qa/SKILL.md b/web-app/public/skills/testing-qa/SKILL.md
new file mode 100644
index 00000000..117310c1
--- /dev/null
+++ b/web-app/public/skills/testing-qa/SKILL.md
@@ -0,0 +1,231 @@
+---
+name: testing-qa
+description: "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance."
+source: personal
+risk: safe
+domain: quality-assurance
+category: workflow-bundle
+version: 1.0.0
+---
+
+# Testing/QA Workflow Bundle
+
+## Overview
+
+Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Setting up testing infrastructure
+- Writing unit and integration tests
+- Implementing E2E tests
+- Automating browser testing
+- Establishing quality gates
+- Performing code review
+
+## Workflow Phases
+
+### Phase 1: Test Strategy
+
+#### Skills to Invoke
+- `test-automator` - Test automation
+- `test-driven-development` - TDD
+
+#### Actions
+1. Define testing strategy
+2. Choose testing frameworks
+3. Plan test coverage
+4. Set up test infrastructure
+5. Configure CI integration
+
+#### Copy-Paste Prompts
+```
+Use @test-automator to design testing strategy
+```
+
+```
+Use @test-driven-development to implement TDD workflow
+```
+
+### Phase 2: Unit Testing
+
+#### Skills to Invoke
+- `javascript-testing-patterns` - Jest/Vitest
+- `python-testing-patterns` - pytest
+- `unit-testing-test-generate` - Test generation
+- `tdd-orchestrator` - TDD orchestration
+
+#### Actions
+1. Write unit tests
+2. Set up test fixtures
+3. Configure mocking
+4. Measure coverage
+5. Integrate with CI
+
+#### Copy-Paste Prompts
+```
+Use @javascript-testing-patterns to write Jest tests
+```
+
+```
+Use @python-testing-patterns to write pytest tests
+```
+
+```
+Use @unit-testing-test-generate to generate unit tests
+```
+
+### Phase 3: Integration Testing
+
+#### Skills to Invoke
+- `api-testing-observability-api-mock` - API testing
+- `e2e-testing-patterns` - Integration patterns
+
+#### Actions
+1. Design integration tests
+2. Set up test databases
+3. Configure API mocks
+4. Test service interactions
+5. Verify data flows
+
+#### Copy-Paste Prompts
+```
+Use @api-testing-observability-api-mock to test APIs
+```
+
+### Phase 4: E2E Testing
+
+#### Skills to Invoke
+- `playwright-skill` - Playwright testing
+- `e2e-testing-patterns` - E2E patterns
+- `webapp-testing` - Web app testing
+
+#### Actions
+1. Design E2E scenarios
+2. Write test scripts
+3. Configure test data
+4. Set up parallel execution
+5. Implement visual regression
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to create E2E tests
+```
+
+```
+Use @e2e-testing-patterns to design E2E strategy
+```
+
+### Phase 5: Browser Automation
+
+#### Skills to Invoke
+- `browser-automation` - Browser automation
+- `webapp-testing` - Browser testing
+- `screenshots` - Screenshot automation
+
+#### Actions
+1. Set up browser automation
+2. Configure headless testing
+3. Implement visual testing
+4. Capture screenshots
+5. Test responsive design
+
+#### Copy-Paste Prompts
+```
+Use @browser-automation to automate browser tasks
+```
+
+```
+Use @screenshots to capture marketing screenshots
+```
+
+### Phase 6: Performance Testing
+
+#### Skills to Invoke
+- `performance-engineer` - Performance engineering
+- `performance-profiling` - Performance profiling
+- `web-performance-optimization` - Web performance
+
+#### Actions
+1. Design performance tests
+2. Set up load testing
+3. Measure response times
+4. Identify bottlenecks
+5. Optimize performance
+
+#### Copy-Paste Prompts
+```
+Use @performance-engineer to test application performance
+```
+
+### Phase 7: Code Review
+
+#### Skills to Invoke
+- `code-reviewer` - AI code review
+- `code-review-excellence` - Review best practices
+- `find-bugs` - Bug detection
+- `security-scanning-security-sast` - Security scanning
+
+#### Actions
+1. Configure review tools
+2. Run automated reviews
+3. Check for bugs
+4. Verify security
+5. Approve changes
+
+#### Copy-Paste Prompts
+```
+Use @code-reviewer to review pull requests
+```
+
+```
+Use @find-bugs to detect bugs in code
+```
+
+### Phase 8: Quality Gates
+
+#### Skills to Invoke
+- `lint-and-validate` - Linting
+- `verification-before-completion` - Verification
+
+#### Actions
+1. Configure linters
+2. Set up formatters
+3. Define quality metrics
+4. Implement gates
+5. Monitor compliance
+
+#### Copy-Paste Prompts
+```
+Use @lint-and-validate to check code quality
+```
+
+```
+Use @verification-before-completion to verify changes
+```
+
+## Testing Pyramid
+
+```
+ / / \ E2E Tests (10%)
+ /---- / \ Integration Tests (20%)
+ /-------- / \ Unit Tests (70%)
+ /------------```
+
+## Quality Gates Checklist
+
+- [ ] Unit test coverage > 80%
+- [ ] All tests passing
+- [ ] E2E tests for critical paths
+- [ ] Performance benchmarks met
+- [ ] Security scan passed
+- [ ] Code review approved
+- [ ] Linting clean
+
+## Related Workflow Bundles
+
+- `development` - Development workflow
+- `security-audit` - Security testing
+- `cloud-devops` - CI/CD integration
+- `ai-ml` - AI testing
diff --git a/web-app/public/skills/theme-factory/SKILL.md b/web-app/public/skills/theme-factory/SKILL.md
index 90dfceaf..751187bb 100644
--- a/web-app/public/skills/theme-factory/SKILL.md
+++ b/web-app/public/skills/theme-factory/SKILL.md
@@ -1,7 +1,9 @@
---
name: theme-factory
-description: Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
+description: "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
@@ -57,3 +59,6 @@ After a preferred theme is selected:
## Create your Own Theme
To handle cases where none of the existing themes work for an artifact, create a custom theme. Based on provided inputs, generate a new theme similar to the ones above. Give the theme a similar name describing what the font/color combinations represent. Use any basic description provided to choose appropriate colors/fonts. After generating the theme, show it for review and verification. Following that, apply the theme as described above.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/threat-mitigation-mapping/SKILL.md b/web-app/public/skills/threat-mitigation-mapping/SKILL.md
index acf05cf5..f2687c60 100644
--- a/web-app/public/skills/threat-mitigation-mapping/SKILL.md
+++ b/web-app/public/skills/threat-mitigation-mapping/SKILL.md
@@ -1,6 +1,8 @@
---
name: threat-mitigation-mapping
-description: Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
+description: "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness."
+risk: unknown
+source: community
---
# Threat Mitigation Mapping
diff --git a/web-app/public/skills/threat-modeling-expert/SKILL.md b/web-app/public/skills/threat-modeling-expert/SKILL.md
index 4dec8d18..472e47e7 100644
--- a/web-app/public/skills/threat-modeling-expert/SKILL.md
+++ b/web-app/public/skills/threat-modeling-expert/SKILL.md
@@ -1,6 +1,8 @@
---
name: threat-modeling-expert
-description: "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture reviews, threat identification, and secure-by-design planning."
+description: "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r..."
+risk: unknown
+source: community
---
# Threat Modeling Expert
diff --git a/web-app/public/skills/threejs-skills/SKILL.md b/web-app/public/skills/threejs-skills/SKILL.md
index 6680ac59..79474da5 100644
--- a/web-app/public/skills/threejs-skills/SKILL.md
+++ b/web-app/public/skills/threejs-skills/SKILL.md
@@ -1,6 +1,6 @@
---
name: threejs-skills
-description: Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.
+description: "Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements."
source: https://github.com/CloudAI-X/threejs-skills
risk: safe
---
diff --git a/web-app/public/skills/tiktok-automation/SKILL.md b/web-app/public/skills/tiktok-automation/SKILL.md
index 2cc63d50..d33a8c95 100644
--- a/web-app/public/skills/tiktok-automation/SKILL.md
+++ b/web-app/public/skills/tiktok-automation/SKILL.md
@@ -3,6 +3,8 @@ name: tiktok-automation
description: "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# TikTok Automation via Rube MCP
@@ -176,3 +178,6 @@ Automate TikTok content creation and profile operations through Composio's TikTo
| Get user stats | TIKTOK_GET_USER_STATS | (none) |
| Get basic info | TIKTOK_GET_USER_BASIC_INFO | (none) |
| Check publish status | TIKTOK_FETCH_PUBLISH_STATUS | publish_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/todoist-automation/SKILL.md b/web-app/public/skills/todoist-automation/SKILL.md
index 85461663..b031fcc7 100644
--- a/web-app/public/skills/todoist-automation/SKILL.md
+++ b/web-app/public/skills/todoist-automation/SKILL.md
@@ -3,6 +3,8 @@ name: todoist-automation
description: "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Todoist Automation via Rube MCP
@@ -229,3 +231,6 @@ Always resolve human-readable names to IDs before operations:
| Delete task | `TODOIST_DELETE_TASK` | `task_id` |
| Completed tasks | `TODOIST_GET_COMPLETED_TASKS_BY_COMPLETION_DATE` | `since`, `until` |
| List filters | `TODOIST_LIST_FILTERS` | `sync_token` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/tool-design/SKILL.md b/web-app/public/skills/tool-design/SKILL.md
index 6ec4e10d..a0165458 100644
--- a/web-app/public/skills/tool-design/SKILL.md
+++ b/web-app/public/skills/tool-design/SKILL.md
@@ -98,7 +98,7 @@ The question to ask: are your tools enabling new capabilities, or are they const
**Build for Future Models**
Models improve faster than tooling can keep up. An architecture optimized for today's model may be over-constrained for tomorrow's. Build minimal architectures that can benefit from model improvements rather than sophisticated architectures that lock in current limitations.
-See [Architectural Reduction Case Study](./references/architectural_reduction.md) for production evidence.
+See Architectural Reduction Case Study for production evidence.
### Tool Description Engineering
@@ -295,8 +295,8 @@ This skill connects to:
## References
Internal references:
-- [Best Practices Reference](./references/best_practices.md) - Detailed tool design guidelines
-- [Architectural Reduction Case Study](./references/architectural_reduction.md) - Production evidence for tool minimalism
+- Best Practices Reference - Detailed tool design guidelines
+- Architectural Reduction Case Study - Production evidence for tool minimalism
Related skills in this collection:
- context-fundamentals - Tool context interactions
diff --git a/web-app/public/skills/top-web-vulnerabilities/SKILL.md b/web-app/public/skills/top-web-vulnerabilities/SKILL.md
index ecbbcc1b..36c66e74 100644
--- a/web-app/public/skills/top-web-vulnerabilities/SKILL.md
+++ b/web-app/public/skills/top-web-vulnerabilities/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Top 100 Web Vulnerabilities Reference
-description: This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
+name: top-web-vulnerabilities
+description: "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Top 100 Web Vulnerabilities Reference
@@ -541,3 +543,6 @@ Permissions-Policy: geolocation=(), microphone=()
- OWASP Application Security Verification Standard (ASVS)
- NIST Cybersecurity Framework
- Source: Kumar MS - Top 100 Web Vulnerabilities
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/track-management/SKILL.md b/web-app/public/skills/track-management/SKILL.md
index 2095eeff..c87f2591 100644
--- a/web-app/public/skills/track-management/SKILL.md
+++ b/web-app/public/skills/track-management/SKILL.md
@@ -1,10 +1,12 @@
---
name: track-management
-description: Use this skill when creating, managing, or working with Conductor
+description: "Use this skill when creating, managing, or working with Conductor"
tracks - the logical work units for features, bugs, and refactors. Applies to
spec.md, plan.md, and track lifecycle operations.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Track Management
diff --git a/web-app/public/skills/track-management/resources/implementation-playbook.md b/web-app/public/skills/track-management/resources/implementation-playbook.md
index bd2abb3c..42d0b2dd 100644
--- a/web-app/public/skills/track-management/resources/implementation-playbook.md
+++ b/web-app/public/skills/track-management/resources/implementation-playbook.md
@@ -315,20 +315,20 @@ Example:
| Track ID | Type | Status | Phase | Started | Assignee |
| ------------------------------------------------ | ------- | ----------- | ----- | ---------- | ---------- |
-| [user-auth_20250115](tracks/user-auth_20250115/) | feature | in-progress | 2/3 | 2025-01-15 | @developer |
-| [fix-login_20250114](tracks/fix-login_20250114/) | bug | pending | 0/2 | 2025-01-14 | - |
+| user-auth_20250115 | feature | in-progress | 2/3 | 2025-01-15 | @developer |
+| fix-login_20250114 | bug | pending | 0/2 | 2025-01-14 | - |
## Completed Tracks
| Track ID | Type | Completed | Duration |
| ---------------------------------------------- | ----- | ---------- | -------- |
-| [setup-ci_20250110](tracks/setup-ci_20250110/) | chore | 2025-01-12 | 2 days |
+| setup-ci_20250110 | chore | 2025-01-12 | 2 days |
## Archived Tracks
| Track ID | Reason | Archived |
| ---------------------------------------------------- | ---------- | ---------- |
-| [old-feature_20241201](tracks/old-feature_20241201/) | Superseded | 2025-01-05 |
+| old-feature_20241201 | Superseded | 2025-01-05 |
```
## Metadata (metadata.json) Fields
diff --git a/web-app/public/skills/trello-automation/SKILL.md b/web-app/public/skills/trello-automation/SKILL.md
index 3a1c88f4..26b6cb12 100644
--- a/web-app/public/skills/trello-automation/SKILL.md
+++ b/web-app/public/skills/trello-automation/SKILL.md
@@ -3,6 +3,8 @@ name: trello-automation
description: "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Trello Automation via Rube MCP
@@ -178,4 +180,7 @@ Most list endpoints return all items. For boards with 1000+ cards, use `limit` a
| Assign member | TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD | idCard, value (member ID) |
| Attach file/URL | TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD | idCard, url OR file |
| Get board members | TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD | idBoard |
-| Batch read | TRELLO_GET_BATCH | urls (comma-separated paths) |
\ No newline at end of file
+| Batch read | TRELLO_GET_BATCH | urls (comma-separated paths) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/trigger-dev/SKILL.md b/web-app/public/skills/trigger-dev/SKILL.md
index 09ed74bb..38fed4e8 100644
--- a/web-app/public/skills/trigger-dev/SKILL.md
+++ b/web-app/public/skills/trigger-dev/SKILL.md
@@ -1,7 +1,8 @@
---
name: trigger-dev
-description: "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task."
+description: "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Trigger.dev Integration
@@ -65,3 +66,6 @@ Tasks that run on a schedule
## Related Skills
Works well with: `nextjs-app-router`, `vercel-deployment`, `ai-agents-architect`, `llm-architect`, `email-systems`, `stripe-integration`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/turborepo-caching/SKILL.md b/web-app/public/skills/turborepo-caching/SKILL.md
index 3ec0b45f..0211f934 100644
--- a/web-app/public/skills/turborepo-caching/SKILL.md
+++ b/web-app/public/skills/turborepo-caching/SKILL.md
@@ -1,6 +1,8 @@
---
name: turborepo-caching
-description: Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
+description: "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching."
+risk: unknown
+source: community
---
# Turborepo Caching
diff --git a/web-app/public/skills/tutorial-engineer/SKILL.md b/web-app/public/skills/tutorial-engineer/SKILL.md
index 9f5c0a2e..f7ec59e1 100644
--- a/web-app/public/skills/tutorial-engineer/SKILL.md
+++ b/web-app/public/skills/tutorial-engineer/SKILL.md
@@ -1,11 +1,13 @@
---
name: tutorial-engineer
-description: Creates step-by-step tutorials and educational content from code.
+description: "Creates step-by-step tutorials and educational content from code."
Transforms complex concepts into progressive learning experiences with
hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,
or concept explanations.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/twilio-communications/SKILL.md b/web-app/public/skills/twilio-communications/SKILL.md
index 80f52940..d9bc9f83 100644
--- a/web-app/public/skills/twilio-communications/SKILL.md
+++ b/web-app/public/skills/twilio-communications/SKILL.md
@@ -1,7 +1,8 @@
---
name: twilio-communications
-description: "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems and multi-channel authentication. Critical focus on compliance, rate limits, and error handling. Use when: twilio, send SMS, text message, voice call, phone verification."
+description: "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Twilio Communications
@@ -293,3 +294,6 @@ def menu_selection():
| Issue | high | ## Track session windows per user |
| Issue | critical | ## Never hardcode credentials |
| Issue | medium | ## Implement application-level rate limiting too |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/twitter-automation/SKILL.md b/web-app/public/skills/twitter-automation/SKILL.md
index 4add3fc9..85f4366d 100644
--- a/web-app/public/skills/twitter-automation/SKILL.md
+++ b/web-app/public/skills/twitter-automation/SKILL.md
@@ -3,6 +3,8 @@ name: twitter-automation
description: "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Twitter/X Automation via Rube MCP
@@ -229,3 +231,6 @@ Automate Twitter/X operations through Composio's Twitter toolkit via Rube MCP.
| Pinned lists | TWITTER_GET_A_USER_S_PINNED_LISTS | id |
| Followed lists | TWITTER_GET_USER_S_FOLLOWED_LISTS | id |
| List details | TWITTER_LIST_LOOKUP_BY_LIST_ID | list_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/typescript-advanced-types/SKILL.md b/web-app/public/skills/typescript-advanced-types/SKILL.md
index 42753f25..77f22871 100644
--- a/web-app/public/skills/typescript-advanced-types/SKILL.md
+++ b/web-app/public/skills/typescript-advanced-types/SKILL.md
@@ -1,6 +1,8 @@
---
name: typescript-advanced-types
-description: Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
+description: "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex..."
+risk: unknown
+source: community
---
# TypeScript Advanced Types
diff --git a/web-app/public/skills/typescript-expert/SKILL.md b/web-app/public/skills/typescript-expert/SKILL.md
index 70547c68..8263f3d5 100644
--- a/web-app/public/skills/typescript-expert/SKILL.md
+++ b/web-app/public/skills/typescript-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: typescript-expert
-description: >-
+description: ">-"
TypeScript and JavaScript expert with deep knowledge of type-level
programming, performance optimization, monorepo management, migration
strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript
@@ -11,6 +11,8 @@ category: framework
bundle: [typescript-type-expert, typescript-build-expert]
displayName: TypeScript
color: blue
+risk: unknown
+source: community
---
# TypeScript Expert
@@ -427,3 +429,6 @@ Slow language server? → Exclude node_modules, limit files in tsconfig
- [tsd](https://github.com/tsdjs/tsd) - Standalone type testing
Always validate changes don't break existing functionality before considering the issue resolved.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/typescript-pro/SKILL.md b/web-app/public/skills/typescript-pro/SKILL.md
index 75147114..31cf0e42 100644
--- a/web-app/public/skills/typescript-pro/SKILL.md
+++ b/web-app/public/skills/typescript-pro/SKILL.md
@@ -1,11 +1,13 @@
---
name: typescript-pro
-description: Master TypeScript with advanced types, generics, and strict type
+description: "Master TypeScript with advanced types, generics, and strict type"
safety. Handles complex type systems, decorators, and enterprise-grade
patterns. Use PROACTIVELY for TypeScript architecture, type inference
optimization, or advanced typing patterns.
metadata:
model: opus
+risk: unknown
+source: community
---
You are a TypeScript expert specializing in advanced typing and enterprise-grade development.
diff --git a/web-app/public/skills/ui-ux-designer/SKILL.md b/web-app/public/skills/ui-ux-designer/SKILL.md
index c2515291..24e6ec58 100644
--- a/web-app/public/skills/ui-ux-designer/SKILL.md
+++ b/web-app/public/skills/ui-ux-designer/SKILL.md
@@ -1,11 +1,13 @@
---
name: ui-ux-designer
-description: Create interface designs, wireframes, and design systems. Masters
+description: "Create interface designs, wireframes, and design systems. Masters"
user research, accessibility standards, and modern design tools. Specializes
in design tokens, component libraries, and inclusive design. Use PROACTIVELY
for design systems, user flows, or interface optimization.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/ui-ux-pro-max/SKILL.md b/web-app/public/skills/ui-ux-pro-max/SKILL.md
index 8121da06..ee92e00a 100644
--- a/web-app/public/skills/ui-ux-pro-max/SKILL.md
+++ b/web-app/public/skills/ui-ux-pro-max/SKILL.md
@@ -1,6 +1,8 @@
---
name: ui-ux-pro-max
-description: "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples."
+description: "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr..."
+risk: unknown
+source: community
---
# UI/UX Pro Max - Design Intelligence
@@ -349,3 +351,6 @@ Before delivering UI code, verify these items:
- [ ] Form inputs have labels
- [ ] Color is not the only indicator
- [ ] `prefers-reduced-motion` respected
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/ui-visual-validator/SKILL.md b/web-app/public/skills/ui-visual-validator/SKILL.md
index 0306b194..2850020d 100644
--- a/web-app/public/skills/ui-visual-validator/SKILL.md
+++ b/web-app/public/skills/ui-visual-validator/SKILL.md
@@ -1,12 +1,14 @@
---
name: ui-visual-validator
-description: Rigorous visual validation expert specializing in UI testing,
+description: "Rigorous visual validation expert specializing in UI testing,"
design system compliance, and accessibility verification. Masters screenshot
analysis, visual regression testing, and component validation. Use PROACTIVELY
to verify UI modifications have achieved their intended goals through
comprehensive visual analysis.
metadata:
model: sonnet
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/unit-testing-test-generate/SKILL.md b/web-app/public/skills/unit-testing-test-generate/SKILL.md
index a6ec6023..df16a999 100644
--- a/web-app/public/skills/unit-testing-test-generate/SKILL.md
+++ b/web-app/public/skills/unit-testing-test-generate/SKILL.md
@@ -1,6 +1,8 @@
---
name: unit-testing-test-generate
-description: Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
+description: "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus."
+risk: unknown
+source: community
---
# Automated Unit Test Generation
diff --git a/web-app/public/skills/unity-developer/SKILL.md b/web-app/public/skills/unity-developer/SKILL.md
index e30de4c6..e6d114e0 100644
--- a/web-app/public/skills/unity-developer/SKILL.md
+++ b/web-app/public/skills/unity-developer/SKILL.md
@@ -1,12 +1,14 @@
---
name: unity-developer
-description: Build Unity games with optimized C# scripts, efficient rendering,
+description: "Build Unity games with optimized C# scripts, efficient rendering,"
and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and
cross-platform deployment. Handles gameplay systems, UI implementation, and
platform optimization. Use PROACTIVELY for Unity performance issues, game
mechanics, or cross-platform builds.
metadata:
model: opus
+risk: unknown
+source: community
---
## Use this skill when
diff --git a/web-app/public/skills/unity-ecs-patterns/SKILL.md b/web-app/public/skills/unity-ecs-patterns/SKILL.md
index 309808af..cbde2c29 100644
--- a/web-app/public/skills/unity-ecs-patterns/SKILL.md
+++ b/web-app/public/skills/unity-ecs-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: unity-ecs-patterns
-description: Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.
+description: "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent..."
+risk: unknown
+source: community
---
# Unity ECS Patterns
diff --git a/web-app/public/skills/unreal-engine-cpp-pro/SKILL.md b/web-app/public/skills/unreal-engine-cpp-pro/SKILL.md
index 956a88eb..01bf607c 100644
--- a/web-app/public/skills/unreal-engine-cpp-pro/SKILL.md
+++ b/web-app/public/skills/unreal-engine-cpp-pro/SKILL.md
@@ -1,6 +1,6 @@
---
name: unreal-engine-cpp-pro
-description: Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
+description: "Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices."
risk: safe
source: self
---
diff --git a/web-app/public/skills/upstash-qstash/SKILL.md b/web-app/public/skills/upstash-qstash/SKILL.md
index 87b45695..5f85d7b8 100644
--- a/web-app/public/skills/upstash-qstash/SKILL.md
+++ b/web-app/public/skills/upstash-qstash/SKILL.md
@@ -1,7 +1,8 @@
---
name: upstash-qstash
-description: "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, scheduled http, message queue serverless."
+description: "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Upstash QStash
@@ -66,3 +67,6 @@ Verifying QStash message signatures in your endpoint
## Related Skills
Works well with: `vercel-deployment`, `nextjs-app-router`, `redis-specialist`, `email-systems`, `supabase-backend`, `cloudflare-workers`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/using-git-worktrees/SKILL.md b/web-app/public/skills/using-git-worktrees/SKILL.md
index 9d52d80c..2126cf36 100644
--- a/web-app/public/skills/using-git-worktrees/SKILL.md
+++ b/web-app/public/skills/using-git-worktrees/SKILL.md
@@ -1,6 +1,8 @@
---
name: using-git-worktrees
-description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
+description: "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi..."
+risk: unknown
+source: community
---
# Using Git Worktrees
@@ -215,3 +217,6 @@ Ready to implement auth feature
**Pairs with:**
- **finishing-a-development-branch** - REQUIRED for cleanup after work complete
- **executing-plans** or **subagent-driven-development** - Work happens in this worktree
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/using-neon/SKILL.md b/web-app/public/skills/using-neon/SKILL.md
index 64895e64..2af3f903 100644
--- a/web-app/public/skills/using-neon/SKILL.md
+++ b/web-app/public/skills/using-neon/SKILL.md
@@ -1,6 +1,6 @@
---
name: using-neon
-description: "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions."
+description: "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/..."
source: "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres"
risk: safe
---
diff --git a/web-app/public/skills/using-superpowers/SKILL.md b/web-app/public/skills/using-superpowers/SKILL.md
index 7867fcfc..6acbf93b 100644
--- a/web-app/public/skills/using-superpowers/SKILL.md
+++ b/web-app/public/skills/using-superpowers/SKILL.md
@@ -1,6 +1,8 @@
---
name: using-superpowers
-description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
+description: "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions"
+risk: unknown
+source: community
---
@@ -85,3 +87,6 @@ The skill itself tells you which.
## User Instructions
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/uv-package-manager/SKILL.md b/web-app/public/skills/uv-package-manager/SKILL.md
index 3d9fc495..e13c5c18 100644
--- a/web-app/public/skills/uv-package-manager/SKILL.md
+++ b/web-app/public/skills/uv-package-manager/SKILL.md
@@ -1,6 +1,8 @@
---
name: uv-package-manager
-description: Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.
+description: "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi..."
+risk: unknown
+source: community
---
# UV Package Manager
diff --git a/web-app/public/skills/vector-database-engineer/SKILL.md b/web-app/public/skills/vector-database-engineer/SKILL.md
index d003b58c..247c7dbc 100644
--- a/web-app/public/skills/vector-database-engineer/SKILL.md
+++ b/web-app/public/skills/vector-database-engineer/SKILL.md
@@ -1,6 +1,8 @@
---
name: vector-database-engineer
description: "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar"
+risk: unknown
+source: community
---
# Vector Database Engineer
diff --git a/web-app/public/skills/vector-index-tuning/SKILL.md b/web-app/public/skills/vector-index-tuning/SKILL.md
index 123b0456..e20b09e8 100644
--- a/web-app/public/skills/vector-index-tuning/SKILL.md
+++ b/web-app/public/skills/vector-index-tuning/SKILL.md
@@ -1,6 +1,8 @@
---
name: vector-index-tuning
-description: Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.
+description: "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure."
+risk: unknown
+source: community
---
# Vector Index Tuning
diff --git a/web-app/public/skills/vercel-automation/SKILL.md b/web-app/public/skills/vercel-automation/SKILL.md
index 9ebee5cf..4c793a1c 100644
--- a/web-app/public/skills/vercel-automation/SKILL.md
+++ b/web-app/public/skills/vercel-automation/SKILL.md
@@ -3,6 +3,8 @@ name: vercel-automation
description: "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Vercel Automation via Rube MCP
@@ -224,3 +226,6 @@ Automate Vercel platform operations through Composio's Vercel toolkit via Rube M
| List teams | VERCEL_LIST_TEAMS | (none) |
| Get team | VERCEL_GET_TEAM | teamId |
| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/vercel-deploy-claimable/SKILL.md b/web-app/public/skills/vercel-deploy-claimable/SKILL.md
index 99a82935..d880c269 100644
--- a/web-app/public/skills/vercel-deploy-claimable/SKILL.md
+++ b/web-app/public/skills/vercel-deploy-claimable/SKILL.md
@@ -1,6 +1,6 @@
---
name: vercel-deploy-claimable
-description: "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and give me the link', or 'Push this live'. No authentication required - returns preview URL and claimable deployment link."
+description: "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and..."
source: "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
risk: safe
---
diff --git a/web-app/public/skills/verification-before-completion/SKILL.md b/web-app/public/skills/verification-before-completion/SKILL.md
index 2f14076e..e4da6083 100644
--- a/web-app/public/skills/verification-before-completion/SKILL.md
+++ b/web-app/public/skills/verification-before-completion/SKILL.md
@@ -1,6 +1,8 @@
---
name: verification-before-completion
-description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+description: "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide..."
+risk: unknown
+source: community
---
# Verification Before Completion
@@ -137,3 +139,6 @@ From 24 failure memories:
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/viral-generator-builder/SKILL.md b/web-app/public/skills/viral-generator-builder/SKILL.md
index afc1aec2..4b106425 100644
--- a/web-app/public/skills/viral-generator-builder/SKILL.md
+++ b/web-app/public/skills/viral-generator-builder/SKILL.md
@@ -1,7 +1,8 @@
---
name: viral-generator-builder
-description: "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Use when: generator tool, quiz maker, name generator, avatar creator, viral tool."
+description: "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Viral Generator Builder
@@ -197,3 +198,6 @@ Your branding subtle but present.
## Related Skills
Works well with: `viral-hooks`, `landing-page-design`, `seo`, `frontend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/voice-agents/SKILL.md b/web-app/public/skills/voice-agents/SKILL.md
index 276c08b4..ada27b1c 100644
--- a/web-app/public/skills/voice-agents/SKILL.md
+++ b/web-app/public/skills/voice-agents/SKILL.md
@@ -1,7 +1,8 @@
---
name: voice-agents
-description: "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flow with sub-800ms latency while handling interruptions, background noise, and emotional nuance. This skill covers two architectures: speech-to-speech (OpenAI Realtime API, lowest latency, most natural) and pipeline (STT→LLM→TTS, more control, easier to debug). Key insight: latency is the constraint. Hu"
+description: "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Voice Agents
@@ -66,3 +67,6 @@ Detect when user starts/stops speaking
## Related Skills
Works well with: `agent-tool-builder`, `multi-agent-orchestration`, `llm-architect`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/voice-ai-development/SKILL.md b/web-app/public/skills/voice-ai-development/SKILL.md
index 0526ce93..fbd84b65 100644
--- a/web-app/public/skills/voice-ai-development/SKILL.md
+++ b/web-app/public/skills/voice-ai-development/SKILL.md
@@ -1,7 +1,8 @@
---
name: voice-ai-development
-description: "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis, LiveKit for real-time infrastructure, and WebRTC fundamentals. Knows how to build low-latency, production-ready voice experiences. Use when: voice ai, voice agent, speech to text, text to speech, realtime voice."
+description: "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Voice AI Development
@@ -300,3 +301,6 @@ Harder to optimize.
## Related Skills
Works well with: `langgraph`, `structured-output`, `langfuse`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/voice-ai-engine-development/SKILL.md b/web-app/public/skills/voice-ai-engine-development/SKILL.md
index 4c4c918b..fbb4fec6 100644
--- a/web-app/public/skills/voice-ai-engine-development/SKILL.md
+++ b/web-app/public/skills/voice-ai-engine-development/SKILL.md
@@ -1,6 +1,8 @@
---
name: voice-ai-engine-development
description: "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support"
+risk: unknown
+source: community
---
# Voice AI Engine Development
diff --git a/web-app/public/skills/vulnerability-scanner/SKILL.md b/web-app/public/skills/vulnerability-scanner/SKILL.md
index 97f16882..c6186751 100644
--- a/web-app/public/skills/vulnerability-scanner/SKILL.md
+++ b/web-app/public/skills/vulnerability-scanner/SKILL.md
@@ -1,7 +1,9 @@
---
name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
+description: "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization."
allowed-tools: Read, Glob, Grep, Bash
+risk: unknown
+source: community
---
# Vulnerability Scanner
@@ -274,3 +276,6 @@ Each finding should answer:
---
> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wcag-audit-patterns/SKILL.md b/web-app/public/skills/wcag-audit-patterns/SKILL.md
index 1347ff24..702d2741 100644
--- a/web-app/public/skills/wcag-audit-patterns/SKILL.md
+++ b/web-app/public/skills/wcag-audit-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: wcag-audit-patterns
-description: Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
+description: "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac..."
+risk: unknown
+source: community
---
# WCAG Audit Patterns
diff --git a/web-app/public/skills/web-artifacts-builder/SKILL.md b/web-app/public/skills/web-artifacts-builder/SKILL.md
index 8b39b19f..97142a73 100644
--- a/web-app/public/skills/web-artifacts-builder/SKILL.md
+++ b/web-app/public/skills/web-artifacts-builder/SKILL.md
@@ -1,7 +1,9 @@
---
name: web-artifacts-builder
-description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
+description: "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Web Artifacts Builder
@@ -71,4 +73,7 @@ To test/visualize the artifact, use available tools (including other Skills or b
## Reference
-- **shadcn/ui components**: https://ui.shadcn.com/docs/components
\ No newline at end of file
+- **shadcn/ui components**: https://ui.shadcn.com/docs/components
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/web-design-guidelines/SKILL.md b/web-app/public/skills/web-design-guidelines/SKILL.md
index 83b34c20..7907a0a6 100644
--- a/web-app/public/skills/web-design-guidelines/SKILL.md
+++ b/web-app/public/skills/web-design-guidelines/SKILL.md
@@ -1,7 +1,9 @@
---
name: web-design-guidelines
-description: Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
+description: "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga..."
argument-hint:
+risk: unknown
+source: community
---
# Web Interface Guidelines
@@ -34,3 +36,6 @@ When a user provides a file or pattern argument:
4. Output findings using the format specified in the guidelines
If no files specified, ask the user which files to review.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/web-performance-optimization/SKILL.md b/web-app/public/skills/web-performance-optimization/SKILL.md
index 1ae0e008..acbb8ccc 100644
--- a/web-app/public/skills/web-performance-optimization/SKILL.md
+++ b/web-app/public/skills/web-performance-optimization/SKILL.md
@@ -1,6 +1,8 @@
---
name: web-performance-optimization
description: "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance"
+risk: unknown
+source: community
---
# Web Performance Optimization
diff --git a/web-app/public/skills/web-security-testing/SKILL.md b/web-app/public/skills/web-security-testing/SKILL.md
new file mode 100644
index 00000000..8f0b0934
--- /dev/null
+++ b/web-app/public/skills/web-security-testing/SKILL.md
@@ -0,0 +1,184 @@
+---
+name: web-security-testing
+description: "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues."
+source: personal
+risk: safe
+domain: security
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Web Security Testing Workflow
+
+## Overview
+
+Specialized workflow for testing web applications against OWASP Top 10 vulnerabilities including injection attacks, XSS, broken authentication, and access control issues.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Testing web application security
+- Performing OWASP Top 10 assessment
+- Conducting penetration tests
+- Validating security controls
+- Bug bounty hunting
+
+## Workflow Phases
+
+### Phase 1: Reconnaissance
+
+#### Skills to Invoke
+- `scanning-tools` - Security scanning
+- `top-web-vulnerabilities` - OWASP knowledge
+
+#### Actions
+1. Map application surface
+2. Identify technologies
+3. Discover endpoints
+4. Find subdomains
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @scanning-tools to perform web application reconnaissance
+```
+
+### Phase 2: Injection Testing
+
+#### Skills to Invoke
+- `sql-injection-testing` - SQL injection
+- `sqlmap-database-pentesting` - SQLMap
+
+#### Actions
+1. Test SQL injection
+2. Test NoSQL injection
+3. Test command injection
+4. Test LDAP injection
+5. Document vulnerabilities
+
+#### Copy-Paste Prompts
+```
+Use @sql-injection-testing to test for SQL injection
+```
+
+```
+Use @sqlmap-database-pentesting to automate SQL injection testing
+```
+
+### Phase 3: XSS Testing
+
+#### Skills to Invoke
+- `xss-html-injection` - XSS testing
+- `html-injection-testing` - HTML injection
+
+#### Actions
+1. Test reflected XSS
+2. Test stored XSS
+3. Test DOM-based XSS
+4. Test XSS filters
+5. Document findings
+
+#### Copy-Paste Prompts
+```
+Use @xss-html-injection to test for cross-site scripting
+```
+
+### Phase 4: Authentication Testing
+
+#### Skills to Invoke
+- `broken-authentication` - Authentication testing
+
+#### Actions
+1. Test credential stuffing
+2. Test brute force protection
+3. Test session management
+4. Test password policies
+5. Test MFA implementation
+
+#### Copy-Paste Prompts
+```
+Use @broken-authentication to test authentication security
+```
+
+### Phase 5: Access Control Testing
+
+#### Skills to Invoke
+- `idor-testing` - IDOR testing
+- `file-path-traversal` - Path traversal
+
+#### Actions
+1. Test vertical privilege escalation
+2. Test horizontal privilege escalation
+3. Test IDOR vulnerabilities
+4. Test directory traversal
+5. Test unauthorized access
+
+#### Copy-Paste Prompts
+```
+Use @idor-testing to test for insecure direct object references
+```
+
+```
+Use @file-path-traversal to test for path traversal
+```
+
+### Phase 6: Security Headers
+
+#### Skills to Invoke
+- `api-security-best-practices` - Security headers
+
+#### Actions
+1. Check CSP implementation
+2. Verify HSTS configuration
+3. Test X-Frame-Options
+4. Check X-Content-Type-Options
+5. Verify referrer policy
+
+#### Copy-Paste Prompts
+```
+Use @api-security-best-practices to audit security headers
+```
+
+### Phase 7: Reporting
+
+#### Skills to Invoke
+- `reporting-standards` - Security reporting
+
+#### Actions
+1. Document vulnerabilities
+2. Assess risk levels
+3. Provide remediation
+4. Create proof of concept
+5. Generate report
+
+#### Copy-Paste Prompts
+```
+Use @reporting-standards to create security report
+```
+
+## OWASP Top 10 Checklist
+
+- [ ] A01: Broken Access Control
+- [ ] A02: Cryptographic Failures
+- [ ] A03: Injection
+- [ ] A04: Insecure Design
+- [ ] A05: Security Misconfiguration
+- [ ] A06: Vulnerable Components
+- [ ] A07: Authentication Failures
+- [ ] A08: Software/Data Integrity
+- [ ] A09: Logging/Monitoring
+- [ ] A10: SSRF
+
+## Quality Gates
+
+- [ ] All OWASP Top 10 tested
+- [ ] Vulnerabilities documented
+- [ ] Proof of concepts captured
+- [ ] Remediation provided
+- [ ] Report generated
+
+## Related Workflow Bundles
+
+- `security-audit` - Security auditing
+- `api-security-testing` - API security
+- `wordpress-security` - WordPress security
diff --git a/web-app/public/skills/web3-testing/SKILL.md b/web-app/public/skills/web3-testing/SKILL.md
index 46743809..2cfa646a 100644
--- a/web-app/public/skills/web3-testing/SKILL.md
+++ b/web-app/public/skills/web3-testing/SKILL.md
@@ -1,6 +1,8 @@
---
name: web3-testing
-description: Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
+description: "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va..."
+risk: unknown
+source: community
---
# Web3 Smart Contract Testing
diff --git a/web-app/public/skills/webapp-testing/SKILL.md b/web-app/public/skills/webapp-testing/SKILL.md
index 47262153..b696cf14 100644
--- a/web-app/public/skills/webapp-testing/SKILL.md
+++ b/web-app/public/skills/webapp-testing/SKILL.md
@@ -1,7 +1,9 @@
---
name: webapp-testing
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+description: "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse..."
license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
---
# Web Application Testing
@@ -93,4 +95,7 @@ with sync_playwright() as p:
- **examples/** - Examples showing common patterns:
- `element_discovery.py` - Discovering buttons, links, and inputs on a page
- `static_html_automation.py` - Using file:// URLs for local HTML
- - `console_logging.py` - Capturing console logs during automation
\ No newline at end of file
+ - `console_logging.py` - Capturing console logs during automation
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/webflow-automation/SKILL.md b/web-app/public/skills/webflow-automation/SKILL.md
index 5b7a3d87..c404d178 100644
--- a/web-app/public/skills/webflow-automation/SKILL.md
+++ b/web-app/public/skills/webflow-automation/SKILL.md
@@ -3,6 +3,8 @@ name: webflow-automation
description: "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Webflow Automation via Rube MCP
@@ -234,3 +236,6 @@ Typical CMS content creation flow:
| Upload asset | `WEBFLOW_UPLOAD_ASSET` | `site_id`, `file_name`, `file_content`, `content_type`, `md5` |
| List orders | `WEBFLOW_LIST_ORDERS` | `site_id`, `status` |
| Get order | `WEBFLOW_GET_ORDER` | `site_id`, `order_id` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/whatsapp-automation/SKILL.md b/web-app/public/skills/whatsapp-automation/SKILL.md
index 11d31a52..b979a7bf 100644
--- a/web-app/public/skills/whatsapp-automation/SKILL.md
+++ b/web-app/public/skills/whatsapp-automation/SKILL.md
@@ -3,6 +3,8 @@ name: whatsapp-automation
description: "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# WhatsApp Business Automation via Rube MCP
@@ -212,3 +214,6 @@ Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Ru
| Create template | WHATSAPP_CREATE_MESSAGE_TEMPLATE | template_name, category, language |
| List templates | WHATSAPP_GET_MESSAGE_TEMPLATES | (none) |
| Check template status | WHATSAPP_GET_TEMPLATE_STATUS | template_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-architect/SKILL.md b/web-app/public/skills/wiki-architect/SKILL.md
index acbcd10c..3a9e09d4 100644
--- a/web-app/public/skills/wiki-architect/SKILL.md
+++ b/web-app/public/skills/wiki-architect/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-architect
-description: Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
+description: "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or..."
+risk: unknown
+source: community
---
# Wiki Architect
@@ -58,3 +60,6 @@ Detect primary language from file extensions and build files, then select a comp
## Output
JSON code block following the catalogue schema with `items[].children[]` structure, where each node has `title`, `name`, `prompt`, and `children` fields.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-changelog/SKILL.md b/web-app/public/skills/wiki-changelog/SKILL.md
index d94d7dc4..ae30fc65 100644
--- a/web-app/public/skills/wiki-changelog/SKILL.md
+++ b/web-app/public/skills/wiki-changelog/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-changelog
-description: Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.
+description: "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th..."
+risk: unknown
+source: community
---
# Wiki Changelog
@@ -25,3 +27,6 @@ Generate structured changelogs from git history.
- Merge related commits into coherent descriptions
- Use project terminology from README
- Highlight breaking changes prominently with migration notes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-onboarding/SKILL.md b/web-app/public/skills/wiki-onboarding/SKILL.md
index 6ee3e853..10475626 100644
--- a/web-app/public/skills/wiki-onboarding/SKILL.md
+++ b/web-app/public/skills/wiki-onboarding/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-onboarding
-description: Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.
+description: "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo..."
+risk: unknown
+source: community
---
# Wiki Onboarding Guide Generator
@@ -75,3 +77,6 @@ Scan the repository for build files to determine the primary language for code e
- Include expected output for verification steps
- Use Mermaid for workflow diagrams (dark-mode colors)
- Ground all claims in actual code — cite `(file_path:line_number)`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-page-writer/SKILL.md b/web-app/public/skills/wiki-page-writer/SKILL.md
index c2afc7af..50a15280 100644
--- a/web-app/public/skills/wiki-page-writer/SKILL.md
+++ b/web-app/public/skills/wiki-page-writer/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-page-writer
-description: Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
+description: "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech..."
+risk: unknown
+source: community
---
# Wiki Page Writer
@@ -63,3 +65,6 @@ description: "One-line description"
- Escape bare generics outside code fences: `` `List` `` not bare `List`
- No ` ` in Mermaid blocks
- All hex colors must be 3 or 6 digits
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-qa/SKILL.md b/web-app/public/skills/wiki-qa/SKILL.md
index d0869f57..0f819aef 100644
--- a/web-app/public/skills/wiki-qa/SKILL.md
+++ b/web-app/public/skills/wiki-qa/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-qa
-description: Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.
+description: "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code..."
+risk: unknown
+source: community
---
# Wiki Q&A
@@ -32,3 +34,6 @@ Answer repository questions grounded entirely in source code evidence.
- ONLY use information from actual source files
- NEVER invent, guess, or use external knowledge
- Think step by step before answering
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-researcher/SKILL.md b/web-app/public/skills/wiki-researcher/SKILL.md
index 83e29e5c..dad96da9 100644
--- a/web-app/public/skills/wiki-researcher/SKILL.md
+++ b/web-app/public/skills/wiki-researcher/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-researcher
-description: Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how something works across multiple files, or asks for comprehensive analysis of a specific system or pattern.
+description: "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how..."
+risk: unknown
+source: community
---
# Wiki Researcher
@@ -63,3 +65,6 @@ Each iteration takes a different lens and builds on all prior findings:
- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow
- Stay focused on the specific topic
- Flag what you HAVEN'T explored — boundaries of your knowledge at all times
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wiki-vitepress/SKILL.md b/web-app/public/skills/wiki-vitepress/SKILL.md
index 096a3cec..a1cc9bf1 100644
--- a/web-app/public/skills/wiki-vitepress/SKILL.md
+++ b/web-app/public/skills/wiki-vitepress/SKILL.md
@@ -1,6 +1,8 @@
---
name: wiki-vitepress
-description: Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.
+description: "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa..."
+risk: unknown
+source: community
---
# Wiki VitePress Packager
@@ -146,3 +148,6 @@ Output goes to `wiki-site/.vitepress/dist/`.
- `isCustomElement` compiler option for bare `` causes worse crashes — do NOT use it
- Node text in Mermaid uses inline `style` with highest specificity — CSS alone won't fix it
- `enhanceApp()` runs during SSR where `document` doesn't exist — use `setup()` only
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/windows-privilege-escalation/SKILL.md b/web-app/public/skills/windows-privilege-escalation/SKILL.md
index bc014a83..72bf47d7 100644
--- a/web-app/public/skills/windows-privilege-escalation/SKILL.md
+++ b/web-app/public/skills/windows-privilege-escalation/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Windows Privilege Escalation
-description: This skill should be used when the user asks to "escalate privileges on Windows," "find Windows privesc vectors," "enumerate Windows for privilege escalation," "exploit Windows misconfigurations," or "perform post-exploitation privilege escalation." It provides comprehensive guidance for discovering and exploiting privilege escalation vulnerabilities in Windows environments.
+name: windows-privilege-escalation
+description: "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Windows Privilege Escalation
@@ -494,3 +496,6 @@ runas /user:Administrator cmd.exe
| Token impersonation fails | Wrong privilege/version | Check `whoami /priv`; verify Windows version compatibility |
| Can't find kernel exploit | System patched | Run Windows Exploit Suggester: `python wes.py systeminfo.txt` |
| PowerShell blocked | Execution policy/AMSI | Use `powershell -ep bypass -c "cmd"` or `-enc ` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wireshark-analysis/SKILL.md b/web-app/public/skills/wireshark-analysis/SKILL.md
index 9269ce18..38c0dd94 100644
--- a/web-app/public/skills/wireshark-analysis/SKILL.md
+++ b/web-app/public/skills/wireshark-analysis/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Wireshark Network Traffic Analysis
-description: This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow TCP/UDP streams", "detect network anomalies", "investigate suspicious traffic", or "perform protocol analysis". It provides comprehensive techniques for network packet capture, filtering, and analysis using Wireshark.
+name: wireshark-analysis
+description: "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Wireshark Network Traffic Analysis
@@ -495,3 +497,6 @@ File > Export Packet Dissections # Export as text/CSV
- Configure at Edit > Preferences > Protocols > TLS
- For ephemeral keys, capture pre-master secret from browser
- Some modern ciphers cannot be decrypted passively
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wordpress-penetration-testing/SKILL.md b/web-app/public/skills/wordpress-penetration-testing/SKILL.md
index 0c70bb82..5b80a69c 100644
--- a/web-app/public/skills/wordpress-penetration-testing/SKILL.md
+++ b/web-app/public/skills/wordpress-penetration-testing/SKILL.md
@@ -1,9 +1,11 @@
---
-name: WordPress Penetration Testing
-description: This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
+name: wordpress-penetration-testing
+description: "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# WordPress Penetration Testing
@@ -483,3 +485,6 @@ wpscan --url https://target.com --disable-tls-checks
2. Check for two-factor authentication
3. Look for IP whitelist restrictions
4. Check for login URL changes (security plugins)
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/wordpress-plugin-development/SKILL.md b/web-app/public/skills/wordpress-plugin-development/SKILL.md
new file mode 100644
index 00000000..5b5b8da6
--- /dev/null
+++ b/web-app/public/skills/wordpress-plugin-development/SKILL.md
@@ -0,0 +1,204 @@
+---
+name: wordpress-plugin-development
+description: "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices."
+source: personal
+risk: safe
+domain: wordpress-development
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# WordPress Plugin Development Workflow
+
+## Overview
+
+Specialized workflow for creating WordPress plugins with proper architecture, hooks system, admin interfaces, REST API endpoints, and security practices.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating custom WordPress plugins
+- Extending WordPress functionality
+- Building admin interfaces
+- Adding REST API endpoints
+- Integrating third-party services
+
+## Workflow Phases
+
+### Phase 1: Plugin Setup
+
+#### Skills to Invoke
+- `app-builder` - Project scaffolding
+- `backend-dev-guidelines` - Backend patterns
+
+#### Actions
+1. Create plugin directory structure
+2. Set up main plugin file with header
+3. Implement activation/deactivation hooks
+4. Set up autoloading
+5. Configure text domain
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to scaffold a new WordPress plugin
+```
+
+### Phase 2: Plugin Architecture
+
+#### Skills to Invoke
+- `backend-dev-guidelines` - Architecture patterns
+
+#### Actions
+1. Design plugin class structure
+2. Implement singleton pattern
+3. Create loader class
+4. Set up dependency injection
+5. Configure plugin lifecycle
+
+#### Copy-Paste Prompts
+```
+Use @backend-dev-guidelines to design plugin architecture
+```
+
+### Phase 3: Hooks Implementation
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WordPress patterns
+
+#### Actions
+1. Register action hooks
+2. Create filter hooks
+3. Implement callback functions
+4. Set up hook priorities
+5. Add conditional hooks
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to understand WordPress hooks
+```
+
+### Phase 4: Admin Interface
+
+#### Skills to Invoke
+- `frontend-developer` - Admin UI
+
+#### Actions
+1. Create admin menu
+2. Build settings pages
+3. Implement options registration
+4. Add settings sections/fields
+5. Create admin notices
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create WordPress admin interface
+```
+
+### Phase 5: Database Operations
+
+#### Skills to Invoke
+- `database-design` - Database design
+- `postgresql` - Database patterns
+
+#### Actions
+1. Create custom tables
+2. Implement CRUD operations
+3. Add data validation
+4. Set up data sanitization
+5. Create data upgrade routines
+
+#### Copy-Paste Prompts
+```
+Use @database-design to design plugin database schema
+```
+
+### Phase 6: REST API
+
+#### Skills to Invoke
+- `api-design-principles` - API design
+- `api-patterns` - API patterns
+
+#### Actions
+1. Register REST routes
+2. Create endpoint callbacks
+3. Implement permission callbacks
+4. Add request validation
+5. Document API endpoints
+
+#### Copy-Paste Prompts
+```
+Use @api-design-principles to create WordPress REST API endpoints
+```
+
+### Phase 7: Security
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WordPress security
+- `security-scanning-security-sast` - Security scanning
+
+#### Actions
+1. Implement nonce verification
+2. Add capability checks
+3. Sanitize all inputs
+4. Escape all outputs
+5. Secure database queries
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to audit plugin security
+```
+
+### Phase 8: Testing
+
+#### Skills to Invoke
+- `test-automator` - Test automation
+- `php-pro` - PHP testing
+
+#### Actions
+1. Set up PHPUnit
+2. Create unit tests
+3. Write integration tests
+4. Test with WordPress test suite
+5. Configure CI
+
+#### Copy-Paste Prompts
+```
+Use @test-automator to set up plugin testing
+```
+
+## Plugin Structure
+
+```
+plugin-name/
+├── plugin-name.php
+├── includes/
+│ ├── class-plugin.php
+│ ├── class-loader.php
+│ ├── class-activator.php
+│ └── class-deactivator.php
+├── admin/
+│ ├── class-plugin-admin.php
+│ ├── css/
+│ └── js/
+├── public/
+│ ├── class-plugin-public.php
+│ ├── css/
+│ └── js/
+├── languages/
+└── vendor/
+```
+
+## Quality Gates
+
+- [ ] Plugin activates without errors
+- [ ] All hooks working
+- [ ] Admin interface functional
+- [ ] Security measures implemented
+- [ ] Tests passing
+- [ ] Documentation complete
+
+## Related Workflow Bundles
+
+- `wordpress` - WordPress development
+- `wordpress-theme-development` - Theme development
+- `wordpress-woocommerce` - WooCommerce
diff --git a/web-app/public/skills/wordpress-theme-development/SKILL.md b/web-app/public/skills/wordpress-theme-development/SKILL.md
new file mode 100644
index 00000000..88c54500
--- /dev/null
+++ b/web-app/public/skills/wordpress-theme-development/SKILL.md
@@ -0,0 +1,189 @@
+---
+name: wordpress-theme-development
+description: "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design."
+source: personal
+risk: safe
+domain: wordpress-development
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# WordPress Theme Development Workflow
+
+## Overview
+
+Specialized workflow for creating custom WordPress themes from scratch, including modern block editor (Gutenberg) support, template hierarchy, and responsive design.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Creating custom WordPress themes
+- Converting designs to WordPress themes
+- Adding block editor support
+- Implementing custom post types
+- Building child themes
+
+## Workflow Phases
+
+### Phase 1: Theme Setup
+
+#### Skills to Invoke
+- `app-builder` - Project scaffolding
+- `frontend-developer` - Frontend development
+
+#### Actions
+1. Create theme directory structure
+2. Set up style.css with theme header
+3. Create functions.php
+4. Configure theme support
+5. Set up enqueue scripts/styles
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to scaffold a new WordPress theme project
+```
+
+### Phase 2: Template Hierarchy
+
+#### Skills to Invoke
+- `frontend-developer` - Template development
+
+#### Actions
+1. Create index.php (fallback template)
+2. Implement header.php and footer.php
+3. Create single.php for posts
+4. Create page.php for pages
+5. Add archive.php for archives
+6. Implement search.php and 404.php
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create WordPress template files
+```
+
+### Phase 3: Theme Functions
+
+#### Skills to Invoke
+- `backend-dev-guidelines` - Backend patterns
+
+#### Actions
+1. Register navigation menus
+2. Add theme support (thumbnails, RSS, etc.)
+3. Register widget areas
+4. Create custom template tags
+5. Implement helper functions
+
+#### Copy-Paste Prompts
+```
+Use @backend-dev-guidelines to create theme functions
+```
+
+### Phase 4: Custom Post Types
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WordPress patterns
+
+#### Actions
+1. Register custom post types
+2. Create custom taxonomies
+3. Add custom meta boxes
+4. Implement custom fields
+5. Create archive templates
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to understand WordPress CPT patterns
+```
+
+### Phase 5: Block Editor Support
+
+#### Skills to Invoke
+- `frontend-developer` - Block development
+
+#### Actions
+1. Enable block editor support
+2. Register custom blocks
+3. Create block styles
+4. Add block patterns
+5. Configure block templates
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create custom Gutenberg blocks
+```
+
+### Phase 6: Styling and Design
+
+#### Skills to Invoke
+- `frontend-design` - UI design
+- `tailwind-patterns` - Tailwind CSS
+
+#### Actions
+1. Implement responsive design
+2. Add CSS framework or custom styles
+3. Create design system
+4. Implement theme customizer
+5. Add accessibility features
+
+#### Copy-Paste Prompts
+```
+Use @frontend-design to create responsive theme design
+```
+
+### Phase 7: Testing
+
+#### Skills to Invoke
+- `playwright-skill` - Browser testing
+- `webapp-testing` - Web app testing
+
+#### Actions
+1. Test across browsers
+2. Verify responsive breakpoints
+3. Test block editor
+4. Check accessibility
+5. Performance testing
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to test WordPress theme
+```
+
+## Theme Structure
+
+```
+theme-name/
+├── style.css
+├── functions.php
+├── index.php
+├── header.php
+├── footer.php
+├── sidebar.php
+├── single.php
+├── page.php
+├── archive.php
+├── search.php
+├── 404.php
+├── comments.php
+├── template-parts/
+├── inc/
+├── assets/
+│ ├── css/
+│ ├── js/
+│ └── images/
+└── languages/
+```
+
+## Quality Gates
+
+- [ ] All templates working
+- [ ] Block editor supported
+- [ ] Responsive design verified
+- [ ] Accessibility checked
+- [ ] Performance optimized
+- [ ] Cross-browser tested
+
+## Related Workflow Bundles
+
+- `wordpress` - WordPress development
+- `wordpress-plugin-development` - Plugin development
+- `wordpress-woocommerce` - WooCommerce
diff --git a/web-app/public/skills/wordpress-woocommerce-development/SKILL.md b/web-app/public/skills/wordpress-woocommerce-development/SKILL.md
new file mode 100644
index 00000000..24af7fa1
--- /dev/null
+++ b/web-app/public/skills/wordpress-woocommerce-development/SKILL.md
@@ -0,0 +1,188 @@
+---
+name: wordpress-woocommerce-development
+description: "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization."
+source: personal
+risk: safe
+domain: wordpress-development
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# WordPress WooCommerce Development Workflow
+
+## Overview
+
+Specialized workflow for building WooCommerce stores including setup, payment gateway integration, shipping configuration, custom product types, and store optimization.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Setting up WooCommerce stores
+- Integrating payment gateways
+- Configuring shipping methods
+- Creating custom product types
+- Building subscription products
+
+## Workflow Phases
+
+### Phase 1: Store Setup
+
+#### Skills to Invoke
+- `app-builder` - Project scaffolding
+- `wordpress-penetration-testing` - WordPress patterns
+
+#### Actions
+1. Install WooCommerce
+2. Run setup wizard
+3. Configure store settings
+4. Set up tax rules
+5. Configure currency
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to set up WooCommerce store
+```
+
+### Phase 2: Product Configuration
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WooCommerce patterns
+
+#### Actions
+1. Create product categories
+2. Add product attributes
+3. Configure product types
+4. Set up variable products
+5. Add product images
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to configure WooCommerce products
+```
+
+### Phase 3: Payment Integration
+
+#### Skills to Invoke
+- `payment-integration` - Payment processing
+- `stripe-integration` - Stripe
+- `paypal-integration` - PayPal
+
+#### Actions
+1. Choose payment gateways
+2. Configure Stripe
+3. Set up PayPal
+4. Add offline payments
+5. Test payment flows
+
+#### Copy-Paste Prompts
+```
+Use @stripe-integration to integrate Stripe payments
+```
+
+```
+Use @paypal-integration to integrate PayPal
+```
+
+### Phase 4: Shipping Configuration
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WooCommerce shipping
+
+#### Actions
+1. Set up shipping zones
+2. Configure shipping methods
+3. Add flat rate shipping
+4. Set up free shipping
+5. Integrate carriers
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to configure shipping
+```
+
+### Phase 5: Store Customization
+
+#### Skills to Invoke
+- `frontend-developer` - Store customization
+- `frontend-design` - Store design
+
+#### Actions
+1. Customize product pages
+2. Modify cart page
+3. Style checkout flow
+4. Create custom templates
+5. Add custom fields
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to customize WooCommerce templates
+```
+
+### Phase 6: Extensions
+
+#### Skills to Invoke
+- `wordpress-penetration-testing` - WooCommerce extensions
+
+#### Actions
+1. Install required extensions
+2. Configure subscriptions
+3. Set up bookings
+4. Add memberships
+5. Integrate marketplace
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to configure WooCommerce extensions
+```
+
+### Phase 7: Optimization
+
+#### Skills to Invoke
+- `web-performance-optimization` - Performance
+- `database-optimizer` - Database optimization
+
+#### Actions
+1. Optimize product images
+2. Enable caching
+3. Optimize database
+4. Configure CDN
+5. Set up lazy loading
+
+#### Copy-Paste Prompts
+```
+Use @web-performance-optimization to optimize WooCommerce store
+```
+
+### Phase 8: Testing
+
+#### Skills to Invoke
+- `playwright-skill` - E2E testing
+- `test-automator` - Test automation
+
+#### Actions
+1. Test checkout flow
+2. Verify payment processing
+3. Test email notifications
+4. Check mobile experience
+5. Performance testing
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to test WooCommerce checkout flow
+```
+
+## Quality Gates
+
+- [ ] Products displaying correctly
+- [ ] Checkout flow working
+- [ ] Payments processing
+- [ ] Shipping calculating
+- [ ] Emails sending
+- [ ] Mobile responsive
+
+## Related Workflow Bundles
+
+- `wordpress` - WordPress development
+- `wordpress-theme-development` - Theme development
+- `wordpress-plugin-development` - Plugin development
+- `payment-integration` - Payment processing
diff --git a/web-app/public/skills/wordpress/SKILL.md b/web-app/public/skills/wordpress/SKILL.md
new file mode 100644
index 00000000..336c7679
--- /dev/null
+++ b/web-app/public/skills/wordpress/SKILL.md
@@ -0,0 +1,319 @@
+---
+name: wordpress
+description: "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening."
+source: personal
+risk: safe
+domain: software-development
+category: workflow-bundle
+version: 1.0.0
+---
+
+# WordPress Development Workflow Bundle
+
+## Overview
+
+Comprehensive WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security. This bundle orchestrates skills for building production-ready WordPress sites and applications.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Building new WordPress websites
+- Creating custom themes
+- Developing WordPress plugins
+- Setting up WooCommerce stores
+- Optimizing WordPress performance
+- Hardening WordPress security
+
+## Workflow Phases
+
+### Phase 1: WordPress Setup
+
+#### Skills to Invoke
+- `app-builder` - Project scaffolding
+- `environment-setup-guide` - Development environment
+
+#### Actions
+1. Set up local development environment (LocalWP, Docker, or Valet)
+2. Install WordPress
+3. Configure development database
+4. Set up version control
+5. Configure wp-config.php for development
+
+#### Copy-Paste Prompts
+```
+Use @app-builder to scaffold a new WordPress project with modern tooling
+```
+
+### Phase 2: Theme Development
+
+#### Skills to Invoke
+- `frontend-developer` - Component development
+- `frontend-design` - UI implementation
+- `tailwind-patterns` - Styling
+- `web-performance-optimization` - Performance
+
+#### Actions
+1. Design theme architecture
+2. Create theme files (style.css, functions.php, index.php)
+3. Implement template hierarchy
+4. Create custom page templates
+5. Add custom post types and taxonomies
+6. Implement theme customization options
+7. Add responsive design
+
+#### Theme Structure
+```
+theme-name/
+├── style.css
+├── functions.php
+├── index.php
+├── header.php
+├── footer.php
+├── sidebar.php
+├── single.php
+├── page.php
+├── archive.php
+├── search.php
+├── 404.php
+├── template-parts/
+├── inc/
+├── assets/
+│ ├── css/
+│ ├── js/
+│ └── images/
+└── languages/
+```
+
+#### Copy-Paste Prompts
+```
+Use @frontend-developer to create a custom WordPress theme with React components
+```
+
+```
+Use @tailwind-patterns to style WordPress theme with modern CSS
+```
+
+### Phase 3: Plugin Development
+
+#### Skills to Invoke
+- `backend-dev-guidelines` - Backend standards
+- `api-design-principles` - API design
+- `auth-implementation-patterns` - Authentication
+
+#### Actions
+1. Design plugin architecture
+2. Create plugin boilerplate
+3. Implement hooks (actions and filters)
+4. Create admin interfaces
+5. Add custom database tables
+6. Implement REST API endpoints
+7. Add settings and options pages
+
+#### Plugin Structure
+```
+plugin-name/
+├── plugin-name.php
+├── includes/
+│ ├── class-plugin-activator.php
+│ ├── class-plugin-deactivator.php
+│ ├── class-plugin-loader.php
+│ └── class-plugin.php
+├── admin/
+│ ├── class-plugin-admin.php
+│ ├── css/
+│ └── js/
+├── public/
+│ ├── class-plugin-public.php
+│ ├── css/
+│ └── js/
+└── languages/
+```
+
+#### Copy-Paste Prompts
+```
+Use @backend-dev-guidelines to create a WordPress plugin with proper architecture
+```
+
+### Phase 4: WooCommerce Integration
+
+#### Skills to Invoke
+- `payment-integration` - Payment processing
+- `stripe-integration` - Stripe payments
+- `billing-automation` - Billing workflows
+
+#### Actions
+1. Install and configure WooCommerce
+2. Create custom product types
+3. Customize checkout flow
+4. Integrate payment gateways
+5. Set up shipping methods
+6. Create custom order statuses
+7. Implement subscription products
+8. Add custom email templates
+
+#### Copy-Paste Prompts
+```
+Use @payment-integration to set up WooCommerce with Stripe
+```
+
+```
+Use @billing-automation to create subscription products in WooCommerce
+```
+
+### Phase 5: Performance Optimization
+
+#### Skills to Invoke
+- `web-performance-optimization` - Performance optimization
+- `database-optimizer` - Database optimization
+
+#### Actions
+1. Implement caching (object, page, browser)
+2. Optimize images (lazy loading, WebP)
+3. Minify and combine assets
+4. Enable CDN
+5. Optimize database queries
+6. Implement lazy loading
+7. Configure OPcache
+8. Set up Redis/Memcached
+
+#### Performance Checklist
+- [ ] Page load time < 3 seconds
+- [ ] Time to First Byte < 200ms
+- [ ] Largest Contentful Paint < 2.5s
+- [ ] Cumulative Layout Shift < 0.1
+- [ ] First Input Delay < 100ms
+
+#### Copy-Paste Prompts
+```
+Use @web-performance-optimization to audit and improve WordPress performance
+```
+
+### Phase 6: Security Hardening
+
+#### Skills to Invoke
+- `security-auditor` - Security audit
+- `wordpress-penetration-testing` - WordPress security testing
+- `sast-configuration` - Static analysis
+
+#### Actions
+1. Update WordPress core, themes, plugins
+2. Implement security headers
+3. Configure file permissions
+4. Set up firewall rules
+5. Enable two-factor authentication
+6. Implement rate limiting
+7. Configure security logging
+8. Set up malware scanning
+
+#### Security Checklist
+- [ ] WordPress core updated
+- [ ] All plugins/themes updated
+- [ ] Strong passwords enforced
+- [ ] Two-factor authentication enabled
+- [ ] Security headers configured
+- [ ] XML-RPC disabled or protected
+- [ ] File editing disabled
+- [ ] Database prefix changed
+- [ ] Regular backups configured
+
+#### Copy-Paste Prompts
+```
+Use @wordpress-penetration-testing to audit WordPress security
+```
+
+```
+Use @security-auditor to perform comprehensive security review
+```
+
+### Phase 7: Testing
+
+#### Skills to Invoke
+- `test-automator` - Test automation
+- `playwright-skill` - E2E testing
+- `webapp-testing` - Web app testing
+
+#### Actions
+1. Write unit tests for custom code
+2. Create integration tests
+3. Set up E2E tests
+4. Test cross-browser compatibility
+5. Test responsive design
+6. Performance testing
+7. Security testing
+
+#### Copy-Paste Prompts
+```
+Use @playwright-skill to create E2E tests for WordPress site
+```
+
+### Phase 8: Deployment
+
+#### Skills to Invoke
+- `deployment-engineer` - Deployment
+- `cicd-automation-workflow-automate` - CI/CD
+- `github-actions-templates` - GitHub Actions
+
+#### Actions
+1. Set up staging environment
+2. Configure deployment pipeline
+3. Set up database migrations
+4. Configure environment variables
+5. Enable maintenance mode during deployment
+6. Deploy to production
+7. Verify deployment
+8. Monitor post-deployment
+
+#### Copy-Paste Prompts
+```
+Use @deployment-engineer to set up WordPress deployment pipeline
+```
+
+## WordPress-Specific Workflows
+
+### Custom Post Type Development
+```php
+register_post_type('book', [
+ 'labels' => [...],
+ 'public' => true,
+ 'has_archive' => true,
+ 'supports' => ['title', 'editor', 'thumbnail', 'excerpt'],
+ 'menu_icon' => 'dashicons-book',
+]);
+```
+
+### Custom REST API Endpoint
+```php
+add_action('rest_api_init', function() {
+ register_rest_route('myplugin/v1', '/books', [
+ 'methods' => 'GET',
+ 'callback' => 'get_books',
+ 'permission_callback' => '__return_true',
+ ]);
+});
+```
+
+### WooCommerce Custom Product Type
+```php
+add_action('init', function() {
+ class WC_Product_Custom extends WC_Product {
+ // Custom product implementation
+ }
+});
+```
+
+## Quality Gates
+
+Before moving to next phase, verify:
+- [ ] All custom code tested
+- [ ] Security scan passed
+- [ ] Performance targets met
+- [ ] Cross-browser tested
+- [ ] Mobile responsive verified
+- [ ] Accessibility checked (WCAG 2.1)
+
+## Related Workflow Bundles
+
+- `development` - General web development
+- `security-audit` - Security testing
+- `testing-qa` - Testing workflow
+- `ecommerce` - E-commerce development
diff --git a/web-app/public/skills/workflow- bundlesREADME.md b/web-app/public/skills/workflow- bundlesREADME.md
new file mode 100644
index 00000000..618ac2cd
--- /dev/null
+++ b/web-app/public/skills/workflow- bundlesREADME.md
@@ -0,0 +1,185 @@
+# Workflow Bundles
+
+Consolidated and granular workflow bundles that orchestrate multiple skills for specific development and operational scenarios.
+
+## Granular Workflow Bundles (Specialized)
+
+### Frontend Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `react-nextjs-development` | React and Next.js 14+ with App Router, Server Components, TypeScript, Tailwind | nextjs-app-router-patterns, react-patterns, tailwind-patterns |
+
+### Backend Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `python-fastapi-development` | FastAPI backend with async patterns, SQLAlchemy, Pydantic, auth | fastapi-pro, fastapi-router-py, pydantic-models-py |
+
+### WordPress Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `wordpress-theme-development` | Custom WordPress themes, block editor, template hierarchy | frontend-developer, wordpress-penetration-testing |
+| `wordpress-plugin-development` | WordPress plugins, hooks, admin interfaces, REST API | backend-dev-guidelines, wordpress-penetration-testing |
+| `wordpress-woocommerce-development` | WooCommerce stores, payments, shipping, customization | payment-integration, stripe-integration, paypal-integration |
+
+### System Administration
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `bash-scripting` | Production bash scripts with defensive patterns, testing | bash-pro, bash-defensive-patterns, bats-testing-patterns |
+| `linux-troubleshooting` | Linux system diagnostics, performance, service issues | bash-linux, devops-troubleshooter, server-management |
+
+### Security Testing
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `web-security-testing` | OWASP Top 10 testing, injection, XSS, authentication | sql-injection-testing, xss-html-injection, broken-authentication |
+| `api-security-testing` | REST/GraphQL API security, auth, rate limiting, fuzzing | api-fuzzing-bug-bounty, api-security-best-practices |
+
+### AI/ML
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `rag-implementation` | RAG systems, embeddings, vector DB, chunking, retrieval | rag-engineer, embedding-strategies, vector-database-engineer |
+| `ai-agent-development` | Autonomous agents, multi-agent systems, CrewAI, LangGraph | ai-agents-architect, crewai, langgraph, autonomous-agents |
+
+### Cloud/DevOps
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `kubernetes-deployment` | K8s deployment, Helm charts, service mesh, security | kubernetes-architect, helm-chart-scaffolding, istio-traffic-management |
+| `terraform-infrastructure` | Terraform IaC, modules, state management, CI/CD | terraform-skill, terraform-specialist, terraform-module-library |
+
+### Database
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `postgresql-optimization` | PostgreSQL query tuning, indexing, configuration, monitoring | postgres-best-practices, sql-optimization-patterns, database-optimizer |
+
+### Testing/QA
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `e2e-testing` | Playwright E2E, visual regression, cross-browser, CI/CD | playwright-skill, e2e-testing-patterns, browser-automation |
+
+### Documentation
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `api-documentation` | OpenAPI specs, developer guides, code examples, interactive docs | api-documenter, openapi-spec-generation, api-documentation-generator |
+
+## Consolidated Workflow Bundles
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `development` | Full-stack web and mobile development | app-builder, senior-fullstack, frontend-developer, backend-architect |
+| `wordpress` | WordPress theme, plugin, WooCommerce, security, performance | wordpress-penetration-testing, frontend-developer, payment-integration |
+| `os-scripting` | Shell scripting and system administration | bash-pro, bash-defensive-patterns, shellcheck-configuration |
+| `security-audit` | Security testing and penetration testing | vulnerability-scanner, sql-injection-testing, pentest-commands |
+| `ai-ml` | LLM applications, RAG, and AI agents | ai-agents-architect, rag-engineer, crewai, langgraph |
+| `cloud-devops` | Cloud infrastructure and DevOps | cloud-architect, kubernetes-architect, terraform-skill |
+| `database` | Database design and operations | database-architect, prisma-expert, data-engineer |
+| `testing-qa` | Testing and quality assurance | test-automator, playwright-skill, code-reviewer |
+| `documentation` | Documentation generation | docs-architect, c4-architecture, wiki-architect |
+| `office-productivity` | Document and office automation | libreoffice-writer, libreoffice-calc, libreoffice-impress |
+
+## LibreOffice Skills
+
+The following LibreOffice skills are available in the `skills/libreoffice/` directory:
+
+| Skill | Description |
+|-------|-------------|
+| `writer` | Document creation and automation (ODT) |
+| `calc` | Spreadsheet automation (ODS) |
+| `impress` | Presentation creation (ODP) |
+| `draw` | Vector graphics and diagrams (ODG) |
+| `base` | Database management (ODB) |
+
+## Usage
+
+Each workflow bundle provides:
+
+1. **When to Use** - Scenarios for invoking the workflow
+2. **Workflow Phases** - Step-by-step phases with skills to invoke
+3. **Copy-Paste Prompts** - Ready-to-use prompts for each phase
+4. **Quality Gates** - Checkpoints to verify before proceeding
+5. **Related Bundles** - Links to complementary workflows
+
+### Example Usage
+
+```
+Use @react-nextjs-development to build a new Next.js 14 application
+```
+
+```
+Use @python-fastapi-development to create a REST API with FastAPI
+```
+
+```
+Use @wordpress-theme-development to create a custom WordPress theme
+```
+
+```
+Use @rag-implementation to build a RAG system with vector search
+```
+
+```
+Use @kubernetes-deployment to deploy application to Kubernetes
+```
+
+```
+Use @web-security-testing to perform OWASP Top 10 assessment
+```
+
+```
+Use @libreoffice-writer to convert DOCX documents to ODT format
+```
+
+## Structure
+
+Each workflow bundle follows this structure:
+
+```yaml
+---
+name: bundle-name
+description: "Brief description"
+source: personal
+risk: safe
+domain: domain-category
+category: granular-workflow-bundle # or consolidated-workflow-bundle
+version: 1.0.0
+---
+
+# Bundle Name
+
+## Overview
+...
+
+## When to Use This Workflow
+...
+
+## Workflow Phases
+...
+
+## Quality Gates
+...
+
+## Related Workflow Bundles
+...
+```
+
+## Contributing
+
+When creating new workflow bundles:
+
+1. Identify common skill combinations
+2. Document clear workflow phases
+3. Provide copy-paste prompts
+4. Define quality gates
+5. Link related bundles
+
+## License
+
+Same as the parent project.
diff --git a/web-app/public/skills/workflow-automation/SKILL.md b/web-app/public/skills/workflow-automation/SKILL.md
index f0ebe2d8..be524435 100644
--- a/web-app/public/skills/workflow-automation/SKILL.md
+++ b/web-app/public/skills/workflow-automation/SKILL.md
@@ -1,7 +1,8 @@
---
name: workflow-automation
-description: "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility"
+description: "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Workflow Automation
@@ -66,3 +67,6 @@ Central coordinator dispatches work to specialized workers
## Related Skills
Works well with: `multi-agent-orchestration`, `agent-tool-builder`, `backend`, `devops`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/workflow-orchestration-patterns/SKILL.md b/web-app/public/skills/workflow-orchestration-patterns/SKILL.md
index 323bc3b9..845c017f 100644
--- a/web-app/public/skills/workflow-orchestration-patterns/SKILL.md
+++ b/web-app/public/skills/workflow-orchestration-patterns/SKILL.md
@@ -1,6 +1,8 @@
---
name: workflow-orchestration-patterns
-description: Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
+description: "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ..."
+risk: unknown
+source: community
---
# Workflow Orchestration Patterns
diff --git a/web-app/public/skills/workflow-patterns/SKILL.md b/web-app/public/skills/workflow-patterns/SKILL.md
index b83adfa4..717f3c89 100644
--- a/web-app/public/skills/workflow-patterns/SKILL.md
+++ b/web-app/public/skills/workflow-patterns/SKILL.md
@@ -1,10 +1,12 @@
---
name: workflow-patterns
-description: Use this skill when implementing tasks according to Conductor's TDD
+description: "Use this skill when implementing tasks according to Conductor's TDD"
workflow, handling phase checkpoints, managing git commits for tasks, or
understanding the verification protocol.
metadata:
version: 1.0.0
+risk: unknown
+source: community
---
# Workflow Patterns
diff --git a/web-app/public/skills/workflow_bundles_readme.md b/web-app/public/skills/workflow_bundles_readme.md
new file mode 100644
index 00000000..618ac2cd
--- /dev/null
+++ b/web-app/public/skills/workflow_bundles_readme.md
@@ -0,0 +1,185 @@
+# Workflow Bundles
+
+Consolidated and granular workflow bundles that orchestrate multiple skills for specific development and operational scenarios.
+
+## Granular Workflow Bundles (Specialized)
+
+### Frontend Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `react-nextjs-development` | React and Next.js 14+ with App Router, Server Components, TypeScript, Tailwind | nextjs-app-router-patterns, react-patterns, tailwind-patterns |
+
+### Backend Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `python-fastapi-development` | FastAPI backend with async patterns, SQLAlchemy, Pydantic, auth | fastapi-pro, fastapi-router-py, pydantic-models-py |
+
+### WordPress Development
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `wordpress-theme-development` | Custom WordPress themes, block editor, template hierarchy | frontend-developer, wordpress-penetration-testing |
+| `wordpress-plugin-development` | WordPress plugins, hooks, admin interfaces, REST API | backend-dev-guidelines, wordpress-penetration-testing |
+| `wordpress-woocommerce-development` | WooCommerce stores, payments, shipping, customization | payment-integration, stripe-integration, paypal-integration |
+
+### System Administration
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `bash-scripting` | Production bash scripts with defensive patterns, testing | bash-pro, bash-defensive-patterns, bats-testing-patterns |
+| `linux-troubleshooting` | Linux system diagnostics, performance, service issues | bash-linux, devops-troubleshooter, server-management |
+
+### Security Testing
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `web-security-testing` | OWASP Top 10 testing, injection, XSS, authentication | sql-injection-testing, xss-html-injection, broken-authentication |
+| `api-security-testing` | REST/GraphQL API security, auth, rate limiting, fuzzing | api-fuzzing-bug-bounty, api-security-best-practices |
+
+### AI/ML
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `rag-implementation` | RAG systems, embeddings, vector DB, chunking, retrieval | rag-engineer, embedding-strategies, vector-database-engineer |
+| `ai-agent-development` | Autonomous agents, multi-agent systems, CrewAI, LangGraph | ai-agents-architect, crewai, langgraph, autonomous-agents |
+
+### Cloud/DevOps
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `kubernetes-deployment` | K8s deployment, Helm charts, service mesh, security | kubernetes-architect, helm-chart-scaffolding, istio-traffic-management |
+| `terraform-infrastructure` | Terraform IaC, modules, state management, CI/CD | terraform-skill, terraform-specialist, terraform-module-library |
+
+### Database
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `postgresql-optimization` | PostgreSQL query tuning, indexing, configuration, monitoring | postgres-best-practices, sql-optimization-patterns, database-optimizer |
+
+### Testing/QA
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `e2e-testing` | Playwright E2E, visual regression, cross-browser, CI/CD | playwright-skill, e2e-testing-patterns, browser-automation |
+
+### Documentation
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `api-documentation` | OpenAPI specs, developer guides, code examples, interactive docs | api-documenter, openapi-spec-generation, api-documentation-generator |
+
+## Consolidated Workflow Bundles
+
+| Bundle | Description | Key Skills |
+|--------|-------------|------------|
+| `development` | Full-stack web and mobile development | app-builder, senior-fullstack, frontend-developer, backend-architect |
+| `wordpress` | WordPress theme, plugin, WooCommerce, security, performance | wordpress-penetration-testing, frontend-developer, payment-integration |
+| `os-scripting` | Shell scripting and system administration | bash-pro, bash-defensive-patterns, shellcheck-configuration |
+| `security-audit` | Security testing and penetration testing | vulnerability-scanner, sql-injection-testing, pentest-commands |
+| `ai-ml` | LLM applications, RAG, and AI agents | ai-agents-architect, rag-engineer, crewai, langgraph |
+| `cloud-devops` | Cloud infrastructure and DevOps | cloud-architect, kubernetes-architect, terraform-skill |
+| `database` | Database design and operations | database-architect, prisma-expert, data-engineer |
+| `testing-qa` | Testing and quality assurance | test-automator, playwright-skill, code-reviewer |
+| `documentation` | Documentation generation | docs-architect, c4-architecture, wiki-architect |
+| `office-productivity` | Document and office automation | libreoffice-writer, libreoffice-calc, libreoffice-impress |
+
+## LibreOffice Skills
+
+The following LibreOffice skills are available in the `skills/libreoffice/` directory:
+
+| Skill | Description |
+|-------|-------------|
+| `writer` | Document creation and automation (ODT) |
+| `calc` | Spreadsheet automation (ODS) |
+| `impress` | Presentation creation (ODP) |
+| `draw` | Vector graphics and diagrams (ODG) |
+| `base` | Database management (ODB) |
+
+## Usage
+
+Each workflow bundle provides:
+
+1. **When to Use** - Scenarios for invoking the workflow
+2. **Workflow Phases** - Step-by-step phases with skills to invoke
+3. **Copy-Paste Prompts** - Ready-to-use prompts for each phase
+4. **Quality Gates** - Checkpoints to verify before proceeding
+5. **Related Bundles** - Links to complementary workflows
+
+### Example Usage
+
+```
+Use @react-nextjs-development to build a new Next.js 14 application
+```
+
+```
+Use @python-fastapi-development to create a REST API with FastAPI
+```
+
+```
+Use @wordpress-theme-development to create a custom WordPress theme
+```
+
+```
+Use @rag-implementation to build a RAG system with vector search
+```
+
+```
+Use @kubernetes-deployment to deploy application to Kubernetes
+```
+
+```
+Use @web-security-testing to perform OWASP Top 10 assessment
+```
+
+```
+Use @libreoffice-writer to convert DOCX documents to ODT format
+```
+
+## Structure
+
+Each workflow bundle follows this structure:
+
+```yaml
+---
+name: bundle-name
+description: "Brief description"
+source: personal
+risk: safe
+domain: domain-category
+category: granular-workflow-bundle # or consolidated-workflow-bundle
+version: 1.0.0
+---
+
+# Bundle Name
+
+## Overview
+...
+
+## When to Use This Workflow
+...
+
+## Workflow Phases
+...
+
+## Quality Gates
+...
+
+## Related Workflow Bundles
+...
+```
+
+## Contributing
+
+When creating new workflow bundles:
+
+1. Identify common skill combinations
+2. Document clear workflow phases
+3. Provide copy-paste prompts
+4. Define quality gates
+5. Link related bundles
+
+## License
+
+Same as the parent project.
diff --git a/web-app/public/skills/wrike-automation/SKILL.md b/web-app/public/skills/wrike-automation/SKILL.md
index bb8f6ed0..1e456836 100644
--- a/web-app/public/skills/wrike-automation/SKILL.md
+++ b/web-app/public/skills/wrike-automation/SKILL.md
@@ -3,6 +3,8 @@ name: wrike-automation
description: "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Wrike Automation via Rube MCP
@@ -231,3 +233,6 @@ Automate Wrike project management operations through Composio's Wrike toolkit vi
| Delete space | WRIKE_DELETE_SPACE | spaceId |
| Get contacts | WRIKE_GET_CONTACTS | (none) |
| Invite user | WRIKE_CREATE_INVITATION | email, role |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/writing-plans/SKILL.md b/web-app/public/skills/writing-plans/SKILL.md
index 448ca319..4eaa2574 100644
--- a/web-app/public/skills/writing-plans/SKILL.md
+++ b/web-app/public/skills/writing-plans/SKILL.md
@@ -1,6 +1,8 @@
---
name: writing-plans
-description: Use when you have a spec or requirements for a multi-step task, before touching code
+description: "Use when you have a spec or requirements for a multi-step task, before touching code"
+risk: unknown
+source: community
---
# Writing Plans
@@ -114,3 +116,6 @@ After saving the plan, offer execution choice:
**If Parallel Session chosen:**
- Guide them to open new session in worktree
- **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plans
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/writing-skills/SKILL.md b/web-app/public/skills/writing-skills/SKILL.md
index 7be139ef..7378af3a 100644
--- a/web-app/public/skills/writing-skills/SKILL.md
+++ b/web-app/public/skills/writing-skills/SKILL.md
@@ -1,6 +1,6 @@
---
name: writing-skills
-description: Use when creating, updating, or improving agent skills.
+description: "Use when creating, updating, or improving agent skills."
metadata:
category: meta
author: ozy
@@ -8,6 +8,8 @@ metadata:
agent skill, writing skill
references: anti-rationalization, cso, standards, templates, testing, tier-1-simple,
tier-2-expanded, tier-3-platform
+risk: unknown
+source: community
---
# Writing Skills (Excellence)
@@ -106,7 +108,7 @@ Before deploying any skill:
## 🔗 Related Skills
-- **[opencode-expert](skill://opencode-expert)**: For OpenCode environment configuration
+- **opencode-expert**: For OpenCode environment configuration
- Use `/write-skill` command for guided skill creation
## Examples
diff --git a/web-app/public/skills/writing-skills/anthropic-best-practices.md b/web-app/public/skills/writing-skills/anthropic-best-practices.md
index a5a7d07a..65ba78b4 100644
--- a/web-app/public/skills/writing-skills/anthropic-best-practices.md
+++ b/web-app/public/skills/writing-skills/anthropic-best-practices.md
@@ -287,8 +287,8 @@ with pdfplumber.open("file.pdf") as pdf:
## Advanced features
-**Form filling**: See [FORMS.md](FORMS.md) for complete guide
-**API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
+**Form filling**: See FORMS.md for complete guide
+**API reference**: See REFERENCE.md for all methods
**Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns
````
@@ -313,10 +313,10 @@ bigquery-skill/
## Available datasets
-**Finance**: Revenue, ARR, billing → See [reference/finance.md](reference/finance.md)
-**Sales**: Opportunities, pipeline, accounts → See [reference/sales.md](reference/sales.md)
-**Product**: API usage, features, adoption → See [reference/product.md](reference/product.md)
-**Marketing**: Campaigns, attribution, email → See [reference/marketing.md](reference/marketing.md)
+**Finance**: Revenue, ARR, billing → See reference/finance.md
+**Sales**: Opportunities, pipeline, accounts → See reference/sales.md
+**Product**: API usage, features, adoption → See reference/product.md
+**Marketing**: Campaigns, attribution, email → See reference/marketing.md
## Quick search
@@ -338,14 +338,14 @@ Show basic content, link to advanced content:
## Creating documents
-Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
+Use docx-js for new documents. See DOCX-JS.md.
## Editing documents
For simple edits, modify the XML directly.
-**For tracked changes**: See [REDLINING.md](REDLINING.md)
-**For OOXML details**: See [OOXML.md](OOXML.md)
+**For tracked changes**: See REDLINING.md
+**For OOXML details**: See OOXML.md
```
Claude reads REDLINING.md or OOXML.md only when the user needs those features.
@@ -360,10 +360,10 @@ Claude may partially read files when they're referenced from other referenced fi
```markdown theme={null}
# SKILL.md
-See [advanced.md](advanced.md)...
+See advanced.md...
# advanced.md
-See [details.md](details.md)...
+See details.md...
# details.md
Here's the actual information...
@@ -375,8 +375,8 @@ Here's the actual information...
# SKILL.md
**Basic usage**: [instructions in SKILL.md]
-**Advanced features**: See [advanced.md](advanced.md)
-**API reference**: See [reference.md](reference.md)
+**Advanced features**: See advanced.md
+**API reference**: See reference.md
**Examples**: See [examples.md](examples.md)
```
diff --git a/web-app/public/skills/writing-skills/examples.md b/web-app/public/skills/writing-skills/examples.md
index 95ad71fc..4d0d0338 100644
--- a/web-app/public/skills/writing-skills/examples.md
+++ b/web-app/public/skills/writing-skills/examples.md
@@ -111,7 +111,7 @@ another example
## Detailed Docs
For more options, run `--help` or see:
-- [patterns.md](patterns.md)
+- patterns.md
- [examples.md](examples.md)
```
diff --git a/web-app/public/skills/writing-skills/gotchas.md b/web-app/public/skills/writing-skills/gotchas.md
index b9bfc6b3..0321c297 100644
--- a/web-app/public/skills/writing-skills/gotchas.md
+++ b/web-app/public/skills/writing-skills/gotchas.md
@@ -172,7 +172,7 @@ See [my-skill] for details.
See /home/user/.config/opencode/skills/my-skill/SKILL.md
# ✅ GOOD: Skill protocol
-See [my-skill](skill://my-skill)
+See my-skill
```
## Tier Selection
diff --git a/web-app/public/skills/writing-skills/references/standards/README.md b/web-app/public/skills/writing-skills/references/standards/README.md
index 3c56c331..aed96952 100644
--- a/web-app/public/skills/writing-skills/references/standards/README.md
+++ b/web-app/public/skills/writing-skills/references/standards/README.md
@@ -127,8 +127,8 @@ Reference from SKILL.md:
```markdown
## Detailed Reference
-- [Patterns](patterns.md) - Common usage patterns
-- [Examples](examples.md) - Code samples
+- Patterns - Common usage patterns
+- Examples - Code samples
```
## Skill Types
diff --git a/web-app/public/skills/writing-skills/references/templates/reference.md b/web-app/public/skills/writing-skills/references/templates/reference.md
index a9698cfd..66342eee 100644
--- a/web-app/public/skills/writing-skills/references/templates/reference.md
+++ b/web-app/public/skills/writing-skills/references/templates/reference.md
@@ -31,5 +31,5 @@ another example
## Detailed Docs
For more options, run `--help` or see:
-- [patterns.md](patterns.md)
-- [examples.md](examples.md)
+- patterns.md
+- examples.md
diff --git a/web-app/public/skills/xlsx-official/SKILL.md b/web-app/public/skills/xlsx-official/SKILL.md
index 22db189c..7591182a 100644
--- a/web-app/public/skills/xlsx-official/SKILL.md
+++ b/web-app/public/skills/xlsx-official/SKILL.md
@@ -1,7 +1,9 @@
---
-name: xlsx
-description: "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas"
+name: xlsx-official
+description: "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ...."
license: Proprietary. LICENSE.txt has complete terms
+risk: unknown
+source: community
---
# Requirements for Outputs
@@ -286,4 +288,7 @@ The script returns JSON with error details:
**For Excel files themselves**:
- Add comments to cells with complex formulas or important assumptions
- Document data sources for hardcoded values
-- Include notes for key calculations and model sections
\ No newline at end of file
+- Include notes for key calculations and model sections
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/xss-html-injection/SKILL.md b/web-app/public/skills/xss-html-injection/SKILL.md
index cdde5603..6a7ed15a 100644
--- a/web-app/public/skills/xss-html-injection/SKILL.md
+++ b/web-app/public/skills/xss-html-injection/SKILL.md
@@ -1,9 +1,11 @@
---
-name: Cross-Site Scripting and HTML Injection Testing
-description: This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exploit client-side injection vulnerabilities", "steal cookies via XSS", or "bypass content security policies". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.
+name: xss-html-injection
+description: "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection..."
metadata:
author: zebbern
version: "1.1"
+risk: unknown
+source: community
---
# Cross-Site Scripting and HTML Injection Testing
@@ -497,3 +499,6 @@ Content-Security-Policy: script-src 'self' https://cdn.trusted.com
| Cookies not accessible | Check HttpOnly flag; try localStorage/sessionStorage; use no-cors mode |
| CSP blocking payloads | Find JSONP on whitelisted domains; check for unsafe-inline; test base-uri bypass |
| WAF blocking requests | Use encoding variations; fragment payload; null bytes; case variations |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/youtube-automation/SKILL.md b/web-app/public/skills/youtube-automation/SKILL.md
index 4d9d8ae9..cf590326 100644
--- a/web-app/public/skills/youtube-automation/SKILL.md
+++ b/web-app/public/skills/youtube-automation/SKILL.md
@@ -3,6 +3,8 @@ name: youtube-automation
description: "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# YouTube Automation via Rube MCP
@@ -216,3 +218,6 @@ Automate YouTube operations through Composio's YouTube toolkit via Rube MCP.
| List subscriptions | YOUTUBE_LIST_USER_SUBSCRIPTIONS | (check schema) |
| List comments | YOUTUBE_LIST_COMMENT_THREADS | videoId |
| Channel activities | YOUTUBE_GET_CHANNEL_ACTIVITIES | (check schema) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/youtube-summarizer/README.md b/web-app/public/skills/youtube-summarizer/README.md
index 227f8aef..39b0341f 100644
--- a/web-app/public/skills/youtube-summarizer/README.md
+++ b/web-app/public/skills/youtube-summarizer/README.md
@@ -349,7 +349,7 @@ Found a bug or have a feature request? Contributions welcome!
## License
-MIT License - see [LICENSE](../../../LICENSE) for details.
+MIT License - see LICENSE for details.
---
diff --git a/web-app/public/skills/youtube-summarizer/SKILL.md b/web-app/public/skills/youtube-summarizer/SKILL.md
index c3e7d22e..ab80b11c 100644
--- a/web-app/public/skills/youtube-summarizer/SKILL.md
+++ b/web-app/public/skills/youtube-summarizer/SKILL.md
@@ -9,6 +9,7 @@ platforms: [github-copilot-cli, claude-code, codex]
category: content
tags: [video, summarization, transcription, youtube, content-analysis]
risk: safe
+source: community
---
# youtube-summarizer
diff --git a/web-app/public/skills/zapier-make-patterns/SKILL.md b/web-app/public/skills/zapier-make-patterns/SKILL.md
index e637974b..d43b8f04 100644
--- a/web-app/public/skills/zapier-make-patterns/SKILL.md
+++ b/web-app/public/skills/zapier-make-patterns/SKILL.md
@@ -1,7 +1,8 @@
---
name: zapier-make-patterns
-description: "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power "
+description: "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ..."
source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
---
# Zapier & Make Patterns
@@ -65,3 +66,6 @@ Different actions based on conditions
## Related Skills
Works well with: `workflow-automation`, `agent-tool-builder`, `backend`, `api-designer`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/zendesk-automation/SKILL.md b/web-app/public/skills/zendesk-automation/SKILL.md
index 92cc508e..ae653e7a 100644
--- a/web-app/public/skills/zendesk-automation/SKILL.md
+++ b/web-app/public/skills/zendesk-automation/SKILL.md
@@ -3,6 +3,8 @@ name: zendesk-automation
description: "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Zendesk Automation via Rube MCP
@@ -213,3 +215,6 @@ new -> open -> pending -> solved -> closed
| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |
| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |
| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/zoho-crm-automation/SKILL.md b/web-app/public/skills/zoho-crm-automation/SKILL.md
index 37716108..d43b2ff4 100644
--- a/web-app/public/skills/zoho-crm-automation/SKILL.md
+++ b/web-app/public/skills/zoho-crm-automation/SKILL.md
@@ -3,6 +3,8 @@ name: zoho-crm-automation
description: "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Zoho CRM Automation via Rube MCP
@@ -204,3 +206,6 @@ criteria: '((Last_Name:equals:Doe)AND(Email:contains:example.com))'
| Convert lead | ZOHO_CONVERT_ZOHO_LEAD | lead_id, deal, account, contact |
| Create tag | ZOHO_CREATE_ZOHO_TAG | module, tag_name |
| Update related records | ZOHO_UPDATE_RELATED_RECORDS | module, record_id, related_module, data |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/zoom-automation/SKILL.md b/web-app/public/skills/zoom-automation/SKILL.md
index dc783d74..aae16c73 100644
--- a/web-app/public/skills/zoom-automation/SKILL.md
+++ b/web-app/public/skills/zoom-automation/SKILL.md
@@ -3,6 +3,8 @@ name: zoom-automation
description: "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
+risk: unknown
+source: community
---
# Zoom Automation via Rube MCP
@@ -215,3 +217,6 @@ Most Zoom list endpoints use token-based pagination:
| Register for meeting | `ZOOM_ADD_A_MEETING_REGISTRANT` | `meetingId`, participant details |
| Register for webinar | `ZOOM_ADD_A_WEBINAR_REGISTRANT` | webinar ID, participant details |
| List archived files | `ZOOM_LIST_ARCHIVED_FILES` | `from`, `to` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
diff --git a/web-app/public/skills/zustand-store-ts/SKILL.md b/web-app/public/skills/zustand-store-ts/SKILL.md
index a743bf89..35f0a332 100644
--- a/web-app/public/skills/zustand-store-ts/SKILL.md
+++ b/web-app/public/skills/zustand-store-ts/SKILL.md
@@ -1,6 +1,8 @@
---
name: zustand-store-ts
-description: Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
+description: "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti..."
+risk: unknown
+source: community
---
# Zustand Store
@@ -9,7 +11,7 @@ Create Zustand stores following established patterns with proper TypeScript type
## Quick Start
-Copy the template from [assets/template.ts](assets/template.ts) and replace placeholders:
+Copy the template from assets/template.ts and replace placeholders:
- `{{StoreName}}` → PascalCase store name (e.g., `Project`)
- `{{description}}` → Brief description for JSDoc
@@ -66,3 +68,6 @@ useMyStore.subscribe(
1. Create store in `src/frontend/src/store/`
2. Export from `src/frontend/src/store/index.ts`
3. Add tests in `src/frontend/src/store/*.test.ts`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.
From d1c70dccce41da1481733e048150c044687c9a88 Mon Sep 17 00:00:00 2001
From: Zied
Date: Wed, 25 Feb 2026 10:33:26 +0100
Subject: [PATCH 04/11] docs: add interactive prompt builder section
---
README.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/README.md b/README.md
index 90a72042..96651c9f 100644
--- a/README.md
+++ b/README.md
@@ -351,6 +351,13 @@ To launch the app:
1. Double-click the `START_APP.bat` file in the root directory (Windows) or run it from your terminal.
2. The app will automatically configure everything and open in your default browser.
+#### 🛠️ New: Interactive Prompt Builder
+The web app is no longer just a static catalog! When you click on any skill, you will see an **Interactive Prompt Builder** box.
+Instead of manually copying `@skill-name` and writing your requirements separately in your IDE:
+1. Type your specific project constraints into the text box (e.g., "Use React 19 and Tailwind").
+2. Click **Copy Prompt**.
+3. Your clipboard now has a fully formatted, ready-to-run prompt combining the skill invocation and your custom context!
+
👉 **[View the Complete Skill Catalog (CATALOG.md)](CATALOG.md)**
---
From 7c4aa1c88b2702c4ee10abf8aea342a3a52dd3fc Mon Sep 17 00:00:00 2001
From: Zied
Date: Wed, 25 Feb 2026 11:19:01 +0100
Subject: [PATCH 05/11] feat: add copy full content button
---
web-app/src/pages/SkillDetail.jsx | 34 ++++++++++++++++++++++++-------
1 file changed, 27 insertions(+), 7 deletions(-)
diff --git a/web-app/src/pages/SkillDetail.jsx b/web-app/src/pages/SkillDetail.jsx
index 4d7c99df..ddc448db 100644
--- a/web-app/src/pages/SkillDetail.jsx
+++ b/web-app/src/pages/SkillDetail.jsx
@@ -10,6 +10,7 @@ export function SkillDetail() {
const [content, setContent] = useState('');
const [loading, setLoading] = useState(true);
const [copied, setCopied] = useState(false);
+ const [copiedFull, setCopiedFull] = useState(false);
const [error, setError] = useState(null);
const [customContext, setCustomContext] = useState('');
@@ -61,6 +62,16 @@ export function SkillDetail() {
setTimeout(() => setCopied(false), 2000);
};
+ const copyFullToClipboard = () => {
+ const finalPrompt = customContext.trim()
+ ? `${content}\n\nContext:\n${customContext}`
+ : content;
+
+ navigator.clipboard.writeText(finalPrompt);
+ setCopiedFull(true);
+ setTimeout(() => setCopiedFull(false), 2000);
+ };
+
if (loading) {
return (
@@ -109,13 +120,22 @@ export function SkillDetail() {
{skill.description}
diff --git a/web-app/src/pages/SkillDetail.jsx b/web-app/src/pages/SkillDetail.jsx
index ddc448db..a627169d 100644
--- a/web-app/src/pages/SkillDetail.jsx
+++ b/web-app/src/pages/SkillDetail.jsx
@@ -1,8 +1,8 @@
-
import { useState, useEffect } from 'react';
import { useParams, Link } from 'react-router-dom';
import Markdown from 'react-markdown';
-import { ArrowLeft, Copy, Check, FileCode, AlertTriangle } from 'lucide-react';
+import { ArrowLeft, Copy, Check, FileCode, AlertTriangle, Star } from 'lucide-react';
+import { supabase } from '../lib/supabase';
export function SkillDetail() {
const { id } = useParams();
@@ -13,44 +13,88 @@ export function SkillDetail() {
const [copiedFull, setCopiedFull] = useState(false);
const [error, setError] = useState(null);
const [customContext, setCustomContext] = useState('');
+ const [starCount, setStarCount] = useState(0);
useEffect(() => {
- // 1. Fetch index to get skill metadata and path
- fetch('/skills.json')
- .then(res => res.json())
- .then(skills => {
+ // Fetch index and stars in parallel when possible
+ const loadData = async () => {
+ try {
+ // 1. Fetch index to get skill metadata and path
+ const res = await fetch('/skills.json');
+ const skills = await res.json();
const foundSkill = skills.find(s => s.id === id);
+
if (foundSkill) {
setSkill(foundSkill);
+
+ // Fetch star count
+ if (supabase) {
+ const { data } = await supabase
+ .from('skill_stars')
+ .select('star_count')
+ .eq('skill_id', id)
+ .single();
+
+ if (data) {
+ setStarCount(data.star_count);
+ }
+ }
+
// 2. Fetch the actual markdown content
- // The path in JSON is like "skills/category/name"
- // We mapped it to "/skills/..." in public folder
- // Remove "skills/" prefix if it exists in path to avoid double
const cleanPath = foundSkill.path.startsWith('skills/')
? foundSkill.path.replace('skills/', '')
: foundSkill.path;
- fetch(`/skills/${cleanPath}/SKILL.md`)
- .then(res => {
- if (!res.ok) throw new Error('Skill file not found');
- return res.text();
- })
- .then(text => {
- setContent(text);
- setLoading(false);
- })
- .catch(err => {
- console.error("Failed to load skill content", err);
- setError("Could not load skill content. File might be missing.");
- setLoading(false);
- });
+ const mdRes = await fetch(`/skills/${cleanPath}/SKILL.md`);
+ if (!mdRes.ok) throw new Error('Skill file not found');
+
+ const text = await mdRes.text();
+ setContent(text);
} else {
setError("Skill not found in registry.");
- setLoading(false);
}
- });
+ } catch (err) {
+ console.error("Failed to load skill data", err);
+ setError(err.message || "Could not load skill content.");
+ } finally {
+ setLoading(false);
+ }
+ };
+
+ loadData();
}, [id]);
+ const handleStarClick = async () => {
+ const storedStars = JSON.parse(localStorage.getItem('user_stars') || '{}');
+ if (storedStars[id]) return;
+
+ // Optimistic UI updates
+ setStarCount(prev => prev + 1);
+ localStorage.setItem('user_stars', JSON.stringify({
+ ...storedStars,
+ [id]: true
+ }));
+
+ if (supabase) {
+ const { data } = await supabase
+ .from('skill_stars')
+ .select('star_count')
+ .eq('skill_id', id)
+ .single();
+
+ if (data) {
+ await supabase
+ .from('skill_stars')
+ .update({ star_count: data.star_count + 1 })
+ .eq('skill_id', id);
+ } else {
+ await supabase
+ .from('skill_stars')
+ .insert({ skill_id: id, star_count: 1 });
+ }
+ }
+ };
+
const copyToClipboard = () => {
const basePrompt = `Use @${skill.name}`;
const finalPrompt = customContext.trim()
@@ -112,6 +156,13 @@ export function SkillDetail() {
{skill.source}
)}
+
@{skill.name}
From 50b2667e47e3f98687bc0d426faadba8f4e3e9f0 Mon Sep 17 00:00:00 2001
From: Zied
Date: Thu, 26 Feb 2026 09:39:26 +0100
Subject: [PATCH 07/11] add auto install depencies database
---
START_APP.bat | 1 +
1 file changed, 1 insertion(+)
diff --git a/START_APP.bat b/START_APP.bat
index 85a78ffe..b8934b8a 100644
--- a/START_APP.bat
+++ b/START_APP.bat
@@ -73,6 +73,7 @@ goto :DEPS_OK
:INSTALL_DEPS
call npm install
+call npm install @supabase/supabase-js
if %ERRORLEVEL% NEQ 0 (
echo [ERROR] Failed to install dependencies. Please check your internet connection.
pause
From f88fde08b2fe1279f6a99b12e2001861d907d137 Mon Sep 17 00:00:00 2001
From: Zied
Date: Thu, 26 Feb 2026 11:02:28 +0100
Subject: [PATCH 08/11] auto-update: sync latest skills from upstream
---
skills/00-andruia-consultant/SKILL.md | 60 +
skills/10-andruia-skill-smith/SKILL.MD | 41 +
skills/20-andruia-niche-intelligence/SKILL.md | 62 +
skills/agentfolio/SKILL.md | 96 ++
skills/ai-engineer/SKILL.md | 19 +-
skills/analytics-tracking/SKILL.md | 2 +-
skills/angular/SKILL.md | 2 +-
skills/api-documenter/SKILL.md | 3 +-
skills/appdeploy/SKILL.md | 209 +++
skills/arm-cortex-expert/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-ai-agents-persistent-java/SKILL.md | 2 +-
skills/azure-ai-contentsafety-py/SKILL.md | 2 +-
.../azure-ai-contentunderstanding-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-ai-ml-py/SKILL.md | 2 +-
skills/azure-ai-openai-dotnet/SKILL.md | 2 +-
skills/azure-ai-projects-dotnet/SKILL.md | 2 +-
skills/azure-ai-projects-java/SKILL.md | 2 +-
skills/azure-ai-textanalytics-py/SKILL.md | 2 +-
skills/azure-ai-transcription-py/SKILL.md | 2 +-
.../azure-ai-translation-document-py/SKILL.md | 2 +-
skills/azure-ai-translation-text-py/SKILL.md | 2 +-
.../azure-ai-vision-imageanalysis-py/SKILL.md | 2 +-
skills/azure-ai-voicelive-dotnet/SKILL.md | 2 +-
skills/azure-ai-voicelive-java/SKILL.md | 2 +-
skills/azure-ai-voicelive-ts/SKILL.md | 2 +-
skills/azure-appconfiguration-java/SKILL.md | 2 +-
skills/azure-appconfiguration-py/SKILL.md | 2 +-
skills/azure-compute-batch-java/SKILL.md | 2 +-
skills/azure-containerregistry-py/SKILL.md | 2 +-
skills/azure-cosmos-java/SKILL.md | 2 +-
skills/azure-cosmos-py/SKILL.md | 2 +-
skills/azure-cosmos-rust/SKILL.md | 2 +-
skills/azure-cosmos-ts/SKILL.md | 2 +-
skills/azure-data-tables-py/SKILL.md | 2 +-
skills/azure-eventgrid-dotnet/SKILL.md | 2 +-
skills/azure-eventgrid-py/SKILL.md | 2 +-
skills/azure-eventhub-dotnet/SKILL.md | 2 +-
skills/azure-eventhub-py/SKILL.md | 2 +-
skills/azure-eventhub-rust/SKILL.md | 2 +-
skills/azure-identity-dotnet/SKILL.md | 2 +-
skills/azure-identity-py/SKILL.md | 2 +-
skills/azure-identity-rust/SKILL.md | 2 +-
.../azure-keyvault-certificates-rust/SKILL.md | 2 +-
skills/azure-keyvault-keys-rust/SKILL.md | 2 +-
skills/azure-keyvault-py/SKILL.md | 2 +-
skills/azure-keyvault-secrets-rust/SKILL.md | 2 +-
skills/azure-maps-search-dotnet/SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-mgmt-apicenter-dotnet/SKILL.md | 2 +-
skills/azure-mgmt-apicenter-py/SKILL.md | 2 +-
.../azure-mgmt-apimanagement-dotnet/SKILL.md | 2 +-
skills/azure-mgmt-apimanagement-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-mgmt-botservice-dotnet/SKILL.md | 2 +-
skills/azure-mgmt-botservice-py/SKILL.md | 2 +-
skills/azure-mgmt-fabric-dotnet/SKILL.md | 2 +-
skills/azure-mgmt-fabric-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-monitor-ingestion-java/SKILL.md | 2 +-
skills/azure-monitor-ingestion-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-monitor-opentelemetry-py/SKILL.md | 2 +-
skills/azure-monitor-query-java/SKILL.md | 2 +-
skills/azure-monitor-query-py/SKILL.md | 2 +-
skills/azure-postgres-ts/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-search-documents-dotnet/SKILL.md | 2 +-
skills/azure-search-documents-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
skills/azure-servicebus-dotnet/SKILL.md | 2 +-
skills/azure-servicebus-py/SKILL.md | 2 +-
skills/azure-speech-to-text-rest-py/SKILL.md | 2 +-
skills/azure-storage-blob-py/SKILL.md | 2 +-
skills/azure-storage-blob-rust/SKILL.md | 2 +-
skills/azure-storage-blob-ts/SKILL.md | 2 +-
.../azure-storage-file-datalake-py/SKILL.md | 2 +-
skills/azure-storage-file-share-py/SKILL.md | 2 +-
skills/azure-storage-file-share-ts/SKILL.md | 2 +-
skills/azure-storage-queue-py/SKILL.md | 2 +-
skills/azure-storage-queue-ts/SKILL.md | 2 +-
skills/backend-architect/SKILL.md | 3 +-
skills/backend-security-coder/SKILL.md | 3 +-
skills/bash-pro/SKILL.md | 3 +-
skills/bevy-ecs-expert/SKILL.md | 30 +-
skills/blockchain-developer/SKILL.md | 3 +-
skills/business-analyst/SKILL.md | 3 +-
skills/c4-code/SKILL.md | 3 +-
skills/c4-component/SKILL.md | 3 +-
skills/c4-container/SKILL.md | 3 +-
skills/c4-context/SKILL.md | 3 +-
.../carrier-relationship-management/SKILL.md | 203 +++
.../references/communication-templates.md | 584 +++++++
.../references/decision-frameworks.md | 534 ++++++
.../references/edge-cases.md | 527 ++++++
skills/chrome-extension-developer/SKILL.md | 84 +
skills/cloud-architect/SKILL.md | 3 +-
skills/cloudflare-workers-expert/SKILL.md | 90 +
skills/competitive-landscape/SKILL.md | 3 +-
skills/conductor-setup/SKILL.md | 3 +-
skills/conductor-validator/SKILL.md | 3 +-
skills/content-marketer/SKILL.md | 3 +-
skills/context-driven-development/SKILL.md | 3 +-
skills/context-manager/SKILL.md | 3 +-
skills/copywriting/SKILL.md | 2 +-
skills/cpp-pro/SKILL.md | 3 +-
skills/crypto-bd-agent/SKILL.md | 2 +-
skills/csharp-pro/SKILL.md | 3 +-
skills/customer-support/SKILL.md | 3 +-
skills/customs-trade-compliance/SKILL.md | 255 +++
.../references/communication-templates.md | 631 +++++++
.../references/decision-frameworks.md | 764 +++++++++
.../references/edge-cases.md | 362 ++++
skills/data-engineer/SKILL.md | 3 +-
skills/data-scientist/SKILL.md | 3 +-
skills/database-admin/SKILL.md | 3 +-
skills/database-architect/SKILL.md | 3 +-
skills/database-optimizer/SKILL.md | 3 +-
skills/debugger/SKILL.md | 3 +-
skills/deployment-engineer/SKILL.md | 3 +-
skills/devops-troubleshooter/SKILL.md | 3 +-
skills/django-pro/SKILL.md | 3 +-
skills/docs-architect/SKILL.md | 3 +-
skills/dotnet-architect/SKILL.md | 3 +-
skills/dx-optimizer/SKILL.md | 3 +-
skills/elixir-pro/SKILL.md | 3 +-
skills/energy-procurement/SKILL.md | 218 +++
.../references/communication-templates.md | 492 ++++++
.../references/decision-frameworks.md | 851 ++++++++++
.../references/edge-cases.md | 624 +++++++
skills/error-detective/SKILL.md | 3 +-
skills/fastapi-pro/SKILL.md | 3 +-
skills/firmware-analyst/SKILL.md | 3 +-
skills/flutter-expert/SKILL.md | 3 +-
skills/form-cro/SKILL.md | 2 +-
skills/frontend-developer/SKILL.md | 3 +-
skills/frontend-security-coder/SKILL.md | 3 +-
skills/golang-pro/SKILL.md | 3 +-
skills/graphql-architect/SKILL.md | 3 +-
skills/grpc-golang/SKILL.md | 103 ++
.../resources/implementation-playbook.md | 548 +++++++
skills/hig-components-content/SKILL.md | 2 +-
skills/hig-components-controls/SKILL.md | 2 +-
skills/hig-components-dialogs/SKILL.md | 2 +-
skills/hig-components-layout/SKILL.md | 2 +-
skills/hig-components-menus/SKILL.md | 2 +-
skills/hig-components-search/SKILL.md | 2 +-
skills/hig-components-status/SKILL.md | 2 +-
skills/hig-components-system/SKILL.md | 2 +-
skills/hig-foundations/SKILL.md | 2 +-
skills/hig-inputs/SKILL.md | 2 +-
skills/hig-patterns/SKILL.md | 2 +-
skills/hig-platforms/SKILL.md | 2 +-
skills/hig-project-context/SKILL.md | 2 +-
skills/hig-technologies/SKILL.md | 2 +-
skills/hr-pro/SKILL.md | 3 +-
skills/hybrid-cloud-architect/SKILL.md | 3 +-
skills/imagen/SKILL.md | 2 +-
skills/incident-responder/SKILL.md | 3 +-
skills/inventory-demand-planning/SKILL.md | 239 +++
.../references/communication-templates.md | 566 +++++++
.../references/decision-frameworks.md | 861 ++++++++++
.../references/edge-cases.md | 602 +++++++
skills/ios-developer/SKILL.md | 3 +-
skills/java-pro/SKILL.md | 3 +-
skills/javascript-pro/SKILL.md | 3 +-
skills/julia-pro/SKILL.md | 3 +-
skills/kubernetes-architect/SKILL.md | 3 +-
skills/legacy-modernizer/SKILL.md | 3 +-
skills/legal-advisor/SKILL.md | 3 +-
skills/linkedin-cli/SKILL.md | 536 ++++++
.../logistics-exception-management/SKILL.md | 217 +++
.../references/communication-templates.md | 1170 +++++++++++++
.../references/decision-frameworks.md | 1460 +++++++++++++++++
.../references/edge-cases.md | 734 +++++++++
skills/m365-agents-dotnet/SKILL.md | 2 +-
skills/m365-agents-py/SKILL.md | 2 +-
skills/m365-agents-ts/SKILL.md | 2 +-
skills/malware-analyst/SKILL.md | 3 +-
skills/market-sizing-analysis/SKILL.md | 3 +-
skills/mermaid-expert/SKILL.md | 3 +-
.../SKILL.md | 2 +-
skills/minecraft-bukkit-pro/SKILL.md | 3 +-
skills/ml-engineer/SKILL.md | 3 +-
skills/mlops-engineer/SKILL.md | 3 +-
skills/mobile-developer/SKILL.md | 3 +-
skills/mobile-security-coder/SKILL.md | 3 +-
skills/network-engineer/SKILL.md | 3 +-
skills/observability-engineer/SKILL.md | 3 +-
skills/page-cro/SKILL.md | 2 +-
skills/payment-integration/SKILL.md | 3 +-
skills/php-pro/SKILL.md | 3 +-
skills/posix-shell-pro/SKILL.md | 3 +-
skills/production-scheduling/SKILL.md | 229 +++
.../references/communication-templates.md | 503 ++++++
.../references/decision-frameworks.md | 867 ++++++++++
.../references/edge-cases.md | 611 +++++++
skills/programmatic-seo/SKILL.md | 2 +-
skills/python-pro/SKILL.md | 3 +-
skills/quality-nonconformance/SKILL.md | 250 +++
.../references/communication-templates.md | 711 ++++++++
.../references/decision-frameworks.md | 769 +++++++++
.../references/edge-cases.md | 588 +++++++
skills/quant-analyst/SKILL.md | 3 +-
skills/reference-builder/SKILL.md | 3 +-
skills/returns-reverse-logistics/SKILL.md | 231 +++
.../references/communication-templates.md | 532 ++++++
.../references/decision-frameworks.md | 823 ++++++++++
.../references/edge-cases.md | 635 +++++++
skills/reverse-engineer/SKILL.md | 3 +-
skills/risk-manager/SKILL.md | 3 +-
skills/ruby-pro/SKILL.md | 3 +-
skills/rust-pro/SKILL.md | 3 +-
skills/sales-automator/SKILL.md | 3 +-
skills/scala-pro/SKILL.md | 3 +-
skills/schema-markup/SKILL.md | 2 +-
skills/security-auditor/SKILL.md | 3 +-
.../security-scanning-security-sast/SKILL.md | 3 +-
skills/seo-audit/SKILL.md | 2 +-
skills/seo-authority-builder/SKILL.md | 3 +-
skills/seo-cannibalization-detector/SKILL.md | 3 +-
skills/seo-content-auditor/SKILL.md | 3 +-
skills/seo-content-planner/SKILL.md | 3 +-
skills/seo-content-refresher/SKILL.md | 3 +-
skills/seo-content-writer/SKILL.md | 3 +-
skills/seo-fundamentals/SKILL.md | 2 +-
skills/seo-keyword-strategist/SKILL.md | 3 +-
skills/seo-meta-optimizer/SKILL.md | 3 +-
skills/seo-snippet-hunter/SKILL.md | 3 +-
skills/seo-structure-architect/SKILL.md | 3 +-
skills/sql-pro/SKILL.md | 3 +-
skills/startup-analyst/SKILL.md | 3 +-
.../SKILL.md | 3 +-
.../SKILL.md | 3 +-
.../SKILL.md | 3 +-
skills/startup-financial-modeling/SKILL.md | 3 +-
skills/startup-metrics-framework/SKILL.md | 3 +-
skills/tdd-orchestrator/SKILL.md | 3 +-
skills/team-composition-analysis/SKILL.md | 3 +-
skills/temporal-python-pro/SKILL.md | 3 +-
skills/terraform-specialist/SKILL.md | 3 +-
skills/test-automator/SKILL.md | 3 +-
skills/track-management/SKILL.md | 3 +-
skills/tutorial-engineer/SKILL.md | 3 +-
skills/typescript-expert/SKILL.md | 2 +-
skills/typescript-pro/SKILL.md | 3 +-
skills/ui-ux-designer/SKILL.md | 3 +-
skills/ui-visual-validator/SKILL.md | 3 +-
skills/unity-developer/SKILL.md | 3 +-
skills/workflow-patterns/SKILL.md | 3 +-
259 files changed, 20825 insertions(+), 230 deletions(-)
create mode 100644 skills/00-andruia-consultant/SKILL.md
create mode 100644 skills/10-andruia-skill-smith/SKILL.MD
create mode 100644 skills/20-andruia-niche-intelligence/SKILL.md
create mode 100644 skills/agentfolio/SKILL.md
create mode 100644 skills/appdeploy/SKILL.md
create mode 100644 skills/carrier-relationship-management/SKILL.md
create mode 100644 skills/carrier-relationship-management/references/communication-templates.md
create mode 100644 skills/carrier-relationship-management/references/decision-frameworks.md
create mode 100644 skills/carrier-relationship-management/references/edge-cases.md
create mode 100644 skills/chrome-extension-developer/SKILL.md
create mode 100644 skills/cloudflare-workers-expert/SKILL.md
create mode 100644 skills/customs-trade-compliance/SKILL.md
create mode 100644 skills/customs-trade-compliance/references/communication-templates.md
create mode 100644 skills/customs-trade-compliance/references/decision-frameworks.md
create mode 100644 skills/customs-trade-compliance/references/edge-cases.md
create mode 100644 skills/energy-procurement/SKILL.md
create mode 100644 skills/energy-procurement/references/communication-templates.md
create mode 100644 skills/energy-procurement/references/decision-frameworks.md
create mode 100644 skills/energy-procurement/references/edge-cases.md
create mode 100644 skills/grpc-golang/SKILL.md
create mode 100644 skills/grpc-golang/resources/implementation-playbook.md
create mode 100644 skills/inventory-demand-planning/SKILL.md
create mode 100644 skills/inventory-demand-planning/references/communication-templates.md
create mode 100644 skills/inventory-demand-planning/references/decision-frameworks.md
create mode 100644 skills/inventory-demand-planning/references/edge-cases.md
create mode 100644 skills/linkedin-cli/SKILL.md
create mode 100644 skills/logistics-exception-management/SKILL.md
create mode 100644 skills/logistics-exception-management/references/communication-templates.md
create mode 100644 skills/logistics-exception-management/references/decision-frameworks.md
create mode 100644 skills/logistics-exception-management/references/edge-cases.md
create mode 100644 skills/production-scheduling/SKILL.md
create mode 100644 skills/production-scheduling/references/communication-templates.md
create mode 100644 skills/production-scheduling/references/decision-frameworks.md
create mode 100644 skills/production-scheduling/references/edge-cases.md
create mode 100644 skills/quality-nonconformance/SKILL.md
create mode 100644 skills/quality-nonconformance/references/communication-templates.md
create mode 100644 skills/quality-nonconformance/references/decision-frameworks.md
create mode 100644 skills/quality-nonconformance/references/edge-cases.md
create mode 100644 skills/returns-reverse-logistics/SKILL.md
create mode 100644 skills/returns-reverse-logistics/references/communication-templates.md
create mode 100644 skills/returns-reverse-logistics/references/decision-frameworks.md
create mode 100644 skills/returns-reverse-logistics/references/edge-cases.md
diff --git a/skills/00-andruia-consultant/SKILL.md b/skills/00-andruia-consultant/SKILL.md
new file mode 100644
index 00000000..c02b25e4
--- /dev/null
+++ b/skills/00-andruia-consultant/SKILL.md
@@ -0,0 +1,60 @@
+---
+id: 00-andruia-consultant
+name: 00-andruia-consultant
+description: "Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español."
+category: andruia
+risk: safe
+source: personal
+---
+
+## When to Use
+
+Use this skill at the very beginning of a project to diagnose the workspace, determine whether it's a "Pure Engine" (new) or "Evolution" (existing) project, and to set the initial technical roadmap and expert squad.
+
+# 🤖 Andru.ia Solutions Architect - Hybrid Engine (v2.0)
+
+## Description
+
+Soy el Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Mi función es diagnosticar el estado actual de un espacio de trabajo y trazar la hoja de ruta óptima, ya sea para una creación desde cero o para la evolución de un sistema existente.
+
+## 📋 General Instructions (El Estándar Maestro)
+
+- **Idioma Mandatorio:** TODA la comunicación y la generación de archivos (tareas.md, plan_implementacion.md) DEBEN ser en **ESPAÑOL**.
+- **Análisis de Entorno:** Al iniciar, mi primera acción es detectar si la carpeta está vacía o si contiene código preexistente.
+- **Persistencia:** Siempre materializo el diagnóstico en archivos .md locales.
+
+## 🛠️ Workflow: Bifurcación de Diagnóstico
+
+### ESCENARIO A: Lienzo Blanco (Carpeta Vacía)
+
+Si no detecto archivos, activo el protocolo **"Pure Engine"**:
+
+1. **Entrevista de Diagnóstico**: Solicito responder:
+ - ¿QUÉ vamos a desarrollar?
+ - ¿PARA QUIÉN es?
+ - ¿QUÉ RESULTADO esperas? (Objetivo y estética premium).
+
+### ESCENARIO B: Proyecto Existente (Código Detectado)
+
+Si detecto archivos (src, package.json, etc.), actúo como **Consultor de Evolución**:
+
+1. **Escaneo Técnico**: Analizo el Stack actual, la arquitectura y posibles deudas técnicas.
+2. **Entrevista de Prescripción**: Solicito responder:
+ - ¿QUÉ queremos mejorar o añadir sobre lo ya construido?
+ - ¿CUÁL es el mayor punto de dolor o limitación técnica actual?
+ - ¿A QUÉ estándar de calidad queremos elevar el proyecto?
+3. **Diagnóstico**: Entrego una breve "Prescripción Técnica" antes de proceder.
+
+## 🚀 Fase de Sincronización de Squad y Materialización
+
+Para ambos escenarios, tras recibir las respuestas:
+
+1. **Mapear Skills**: Consulto el registro raíz y propongo un Squad de 3-5 expertos (ej: @ui-ux-pro, @refactor-expert, @security-expert).
+2. **Generar Artefactos (En Español)**:
+ - `tareas.md`: Backlog detallado (de creación o de refactorización).
+ - `plan_implementacion.md`: Hoja de ruta técnica con el estándar de diamante.
+
+## ⚠️ Reglas de Oro
+
+1. **Contexto Inteligente**: No mezcles datos de proyectos anteriores. Cada carpeta es una entidad única.
+2. **Estándar de Diamante**: Prioriza siempre soluciones escalables, seguras y estéticamente superiores.
diff --git a/skills/10-andruia-skill-smith/SKILL.MD b/skills/10-andruia-skill-smith/SKILL.MD
new file mode 100644
index 00000000..9f4325d4
--- /dev/null
+++ b/skills/10-andruia-skill-smith/SKILL.MD
@@ -0,0 +1,41 @@
+---
+id: 10-andruia-skill-smith
+name: 10-andruia-skill-smith
+description: "Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante."
+category: andruia
+risk: official
+source: personal
+---
+
+# 🔨 Andru.ia Skill-Smith (The Forge)
+
+
+## 📝 Descripción
+Soy el Ingeniero de Sistemas de Andru.ia. Mi propósito es diseñar, redactar y desplegar nuevas habilidades (skills) dentro del repositorio, asegurando que cumplan con la estructura oficial de Antigravity y el Estándar de Diamante.
+
+## 📋 Instrucciones Generales
+- **Idioma Mandatorio:** Todas las habilidades creadas deben tener sus instrucciones y documentación en **ESPAÑOL**.
+- **Estructura Formal:** Debo seguir la anatomía de carpeta -> README.md -> Registro.
+- **Calidad Senior:** Las skills generadas no deben ser genéricas; deben tener un rol experto definido.
+
+## 🛠️ Flujo de Trabajo (Protocolo de Forja)
+
+### FASE 1: ADN de la Skill
+Solicitar al usuario los 3 pilares de la nueva habilidad:
+1. **Nombre Técnico:** (Ej: @cyber-sec, @data-visualizer).
+2. **Rol Experto:** (¿Quién es esta IA? Ej: "Un experto en auditoría de seguridad").
+3. **Outputs Clave:** (¿Qué archivos o acciones específicas debe realizar?).
+
+### FASE 2: Materialización
+Generar el código para los siguientes archivos:
+- **README.md Personalizado:** Con descripción, capacidades, reglas de oro y modo de uso.
+- **Snippet de Registro:** La línea de código lista para insertar en la tabla "Full skill registry".
+
+### FASE 3: Despliegue e Integración
+1. Crear la carpeta física en `D:\...\antigravity-awesome-skills\skills\`.
+2. Escribir el archivo README.md en dicha carpeta.
+3. Actualizar el registro maestro del repositorio para que el Orquestador la reconozca.
+
+## ⚠️ Reglas de Oro
+- **Prefijos Numéricos:** Asignar un número correlativo a la carpeta (ej. 11, 12, 13) para mantener el orden.
+- **Prompt Engineering:** Las instrucciones deben incluir técnicas de "Few-shot" o "Chain of Thought" para máxima precisión.
\ No newline at end of file
diff --git a/skills/20-andruia-niche-intelligence/SKILL.md b/skills/20-andruia-niche-intelligence/SKILL.md
new file mode 100644
index 00000000..9791b628
--- /dev/null
+++ b/skills/20-andruia-niche-intelligence/SKILL.md
@@ -0,0 +1,62 @@
+---
+id: 20-andruia-niche-intelligence
+name: 20-andruia-niche-intelligence
+description: "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho."
+category: andruia
+risk: safe
+source: personal
+---
+
+## When to Use
+
+Use this skill once the project's niche or industry has been identified. It is essential for injecting domain-specific intelligence, regulatory requirements, and industry-standard UX patterns into the project.
+
+# 🧠 Andru.ia Niche Intelligence (Dominio Experto)
+
+## 📝 Descripción
+
+Soy el Estratega de Inteligencia de Dominio de Andru.ia. Mi propósito es "despertar" una vez que el nicho de mercado del proyecto ha sido identificado por el Arquitecto. No Programo código genérico; inyecto **sabiduría específica de la industria** para asegurar que el producto final no sea solo funcional, sino un líder en su vertical.
+
+## 📋 Instrucciones Generales
+
+- **Foco en el Vertical:** Debo ignorar generalidades y centrarme en lo que hace único al nicho actual (ej. Fintech, EdTech, HealthTech, E-commerce, etc.).
+- **Idioma Mandatorio:** Toda la inteligencia generada debe ser en **ESPAÑOL**.
+- **Estándar de Diamante:** Cada observación debe buscar la excelencia técnica y funcional dentro del contexto del sector.
+
+## 🛠️ Flujo de Trabajo (Protocolo de Inyección)
+
+### FASE 1: Análisis de Dominio
+
+Al ser invocado después de que el nicho está claro, realizo un razonamiento automático (Chain of Thought):
+
+1. **Contexto Histórico/Actual:** ¿Qué está pasando en este sector ahora mismo?
+2. **Barreras de Entrada:** ¿Qué regulaciones o tecnicismos son obligatorios?
+3. **Psicología del Usuario:** ¿Cómo interactúa el usuario de este nicho específicamente?
+
+### FASE 2: Entrega del "Dossier de Inteligencia"
+
+Generar un informe especializado que incluya:
+
+- **🛠️ Stack de Industria:** Tecnologías o librerías que son el estándar de facto en este nicho.
+- **📜 Cumplimiento y Normativa:** Leyes o estándares necesarios (ej. RGPD, HIPAA, Facturación Electrónica DIAN, etc.).
+- **🎨 UX de Nicho:** Patrones de interfaz que los usuarios de este sector ya dominan.
+- **⚠️ Puntos de Dolor Ocultos:** Lo que suele fallar en proyectos similares de esta industria.
+
+## ⚠️ Reglas de Oro
+
+1. **Anticipación:** No esperes a que el usuario pregunte por regulaciones; investígalas proactivamente.
+2. **Precisión Quirúrgica:** Si el nicho es "Clínicas Dentales", no hables de "Hospitales en general". Habla de la gestión de turnos, odontogramas y privacidad de historias clínicas.
+3. **Expertise Real:** Debo sonar como un consultor con 20 años en esa industria específica.
+
+## 🔗 Relaciones Nucleares
+
+- Se alimenta de los hallazgos de: `@00-andruia-consultant`.
+- Proporciona las bases para: `@ui-ux-pro-max` y `@security-review`.
+
+## When to Use
+
+Activa este skill **después de que el nicho de mercado esté claro** y ya exista una visión inicial definida por `@00-andruia-consultant`:
+
+- Cuando quieras profundizar en regulaciones, estándares y patrones UX específicos de un sector concreto (Fintech, HealthTech, logística, etc.).
+- Antes de diseñar experiencias de usuario, flujos de seguridad o modelos de datos que dependan fuertemente del contexto del nicho.
+- Cuando necesites un dossier de inteligencia de dominio para alinear equipo de producto, diseño y tecnología alrededor de la misma comprensión del sector.
diff --git a/skills/agentfolio/SKILL.md b/skills/agentfolio/SKILL.md
new file mode 100644
index 00000000..3c6b8702
--- /dev/null
+++ b/skills/agentfolio/SKILL.md
@@ -0,0 +1,96 @@
+---
+name: agentfolio
+description: "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory."
+source: agentfolio.io
+risk: unknown
+---
+
+# AgentFolio
+
+**Role**: Autonomous Agent Discovery Guide
+
+Use this skill when you want to **discover, compare, and research autonomous AI agents** across ecosystems.
+AgentFolio is a curated directory at https://agentfolio.io that tracks agent frameworks, products, and tools.
+
+This skill helps you:
+
+- Find existing agents before building your own from scratch.
+- Map the landscape of agent frameworks and hosted products.
+- Collect concrete examples and benchmarks for agent capabilities.
+
+## Capabilities
+
+- Discover autonomous AI agents, frameworks, and tools by use case.
+- Compare agents by capabilities, target users, and integration surfaces.
+- Identify gaps in the market or inspiration for new skills/workflows.
+- Gather example agent behavior and UX patterns for your own designs.
+- Track emerging trends in agent architectures and deployments.
+
+## How to Use AgentFolio
+
+1. **Open the directory**
+ - Visit `https://agentfolio.io` in your browser.
+ - Optionally filter by category (e.g., Dev Tools, Ops, Marketing, Productivity).
+
+2. **Search by intent**
+ - Start from the problem you want to solve:
+ - “customer support agents”
+ - “autonomous coding agents”
+ - “research / analysis agents”
+ - Use keywords in the AgentFolio search bar that match your domain or workflow.
+
+3. **Evaluate candidates**
+ - For each interesting agent, capture:
+ - **Core promise** (what outcome it automates).
+ - **Input / output shape** (APIs, UI, data sources).
+ - **Autonomy model** (one-shot, multi-step, tool-using, human-in-the-loop).
+ - **Deployment model** (SaaS, self-hosted, browser, IDE, etc.).
+
+4. **Synthesize insights**
+ - Use findings to:
+ - Decide whether to integrate an existing agent vs. build your own.
+ - Borrow successful UX and safety patterns.
+ - Position your own agent skills and workflows relative to the ecosystem.
+
+## Example Workflows
+
+### 1) Landscape scan before building a new agent
+
+- Define the problem: “autonomous test failure triage for CI pipelines”.
+- Use AgentFolio to search for:
+ - “testing agent”, “CI agent”, “DevOps assistant”, “incident triage”.
+- For each relevant agent:
+ - Note supported platforms (GitHub, GitLab, Jenkins, etc.).
+ - Capture how they explain autonomy and safety boundaries.
+ - Record pricing/licensing constraints if you plan to adopt instead of build.
+
+### 2) Competitive and inspiration research for a new skill
+
+- If you plan to add a new skill (e.g., observability agent, security agent):
+ - Use AgentFolio to find similar agents and features.
+ - Extract 3–5 concrete patterns you want to emulate or avoid.
+ - Translate those patterns into clear requirements for your own skill.
+
+### 3) Vendor shortlisting
+
+- When choosing between multiple agent vendors:
+ - Use AgentFolio entries as a neutral directory.
+ - Build a comparison table (columns: capabilities, integrations, pricing, trust & security).
+ - Use that table to drive a more formal evaluation or proof-of-concept.
+
+## Example Prompts
+
+Use these prompts when working with this skill in an AI coding agent:
+
+- “Use AgentFolio to find 3 autonomous AI agents focused on code review. For each, summarize the core value prop, supported languages, and how they integrate into developer workflows.”
+- “Scan AgentFolio for agents that help with customer support triage. List the top options, their target customer size (SMB vs. enterprise), and any notable UX patterns.”
+- “Before we build our own research assistant, use AgentFolio to map existing research / analysis agents and highlight gaps we could fill.”
+
+## When to Use
+
+This skill is applicable when you need to **discover or compare autonomous AI agents** instead of building in a vacuum:
+
+- At the start of a new agent or workflow project.
+- When evaluating vendors or tools to integrate.
+- When you want inspiration or best practices from existing agent products.
+
diff --git a/skills/ai-engineer/SKILL.md b/skills/ai-engineer/SKILL.md
index 0f949484..ce392e7e 100644
--- a/skills/ai-engineer/SKILL.md
+++ b/skills/ai-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ai-engineer
-description: "Build production-ready LLM applications, advanced RAG systems, and"
+description: |
+ Build production-ready LLM applications, advanced RAG systems, and
intelligent agents. Implements vector search, multimodal AI, agent
orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM
features, chatbots, AI agents, or AI-powered applications.
@@ -9,6 +10,7 @@ metadata:
risk: unknown
source: community
---
+
You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.
## Use this skill when
@@ -37,11 +39,13 @@ You are an AI engineer specializing in production-grade LLM applications, genera
- Add guardrails for prompt injection, PII, and policy compliance.
## Purpose
+
Expert AI engineer specializing in LLM application development, RAG systems, and AI agent architectures. Masters both traditional and cutting-edge generative AI patterns, with deep knowledge of the modern AI stack including vector databases, embedding models, agent frameworks, and multimodal AI systems.
## Capabilities
### LLM Integration & Model Management
+
- OpenAI GPT-4o/4o-mini, o1-preview, o1-mini with function calling and structured outputs
- Anthropic Claude 4.5 Sonnet/Haiku, Claude 4.1 Opus with tool use and computer use
- Open-source models: Llama 3.1/3.2, Mixtral 8x7B/8x22B, Qwen 2.5, DeepSeek-V2
@@ -51,6 +55,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Cost optimization through model selection and caching strategies
### Advanced RAG Systems
+
- Production RAG architectures with multi-stage retrieval pipelines
- Vector databases: Pinecone, Qdrant, Weaviate, Chroma, Milvus, pgvector
- Embedding models: OpenAI text-embedding-3-large/small, Cohere embed-v3, BGE-large
@@ -62,6 +67,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Advanced RAG patterns: GraphRAG, HyDE, RAG-Fusion, self-RAG
### Agent Frameworks & Orchestration
+
- LangChain/LangGraph for complex agent workflows and state management
- LlamaIndex for data-centric AI applications and advanced retrieval
- CrewAI for multi-agent collaboration and specialized agent roles
@@ -72,6 +78,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Agent evaluation and monitoring with custom metrics
### Vector Search & Embeddings
+
- Embedding model selection and fine-tuning for domain-specific tasks
- Vector indexing strategies: HNSW, IVF, LSH for different scale requirements
- Similarity metrics: cosine, dot product, Euclidean for various use cases
@@ -80,6 +87,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Vector database optimization: indexing, sharding, and caching strategies
### Prompt Engineering & Optimization
+
- Advanced prompting techniques: chain-of-thought, tree-of-thoughts, self-consistency
- Few-shot and in-context learning optimization
- Prompt templates with dynamic variable injection and conditioning
@@ -89,6 +97,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Multi-modal prompting for vision and audio models
### Production AI Systems
+
- LLM serving with FastAPI, async processing, and load balancing
- Streaming responses and real-time inference optimization
- Caching strategies: semantic caching, response memoization, embedding caching
@@ -98,6 +107,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Observability: logging, metrics, tracing with LangSmith, Phoenix, Weights & Biases
### Multimodal AI Integration
+
- Vision models: GPT-4V, Claude 4 Vision, LLaVA, CLIP for image understanding
- Audio processing: Whisper for speech-to-text, ElevenLabs for text-to-speech
- Document AI: OCR, table extraction, layout understanding with models like LayoutLM
@@ -105,6 +115,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Cross-modal embeddings and unified vector spaces
### AI Safety & Governance
+
- Content moderation with OpenAI Moderation API and custom classifiers
- Prompt injection detection and prevention strategies
- PII detection and redaction in AI workflows
@@ -113,6 +124,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Responsible AI practices and ethical considerations
### Data Processing & Pipeline Management
+
- Document processing: PDF extraction, web scraping, API integrations
- Data preprocessing: cleaning, normalization, deduplication
- Pipeline orchestration with Apache Airflow, Dagster, Prefect
@@ -121,6 +133,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- ETL/ELT processes for AI data preparation
### Integration & API Development
+
- RESTful API design for AI services with FastAPI, Flask
- GraphQL APIs for flexible AI data querying
- Webhook integration and event-driven architectures
@@ -129,6 +142,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- API security: OAuth, JWT, API key management
## Behavioral Traits
+
- Prioritizes production reliability and scalability over proof-of-concept implementations
- Implements comprehensive error handling and graceful degradation
- Focuses on cost optimization and efficient resource utilization
@@ -141,6 +155,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Balances cutting-edge techniques with proven, stable solutions
## Knowledge Base
+
- Latest LLM developments and model capabilities (GPT-4o, Claude 4.5, Llama 3.2)
- Modern vector database architectures and optimization techniques
- Production AI system design patterns and best practices
@@ -153,6 +168,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Prompt engineering and optimization methodologies
## Response Approach
+
1. **Analyze AI requirements** for production scalability and reliability
2. **Design system architecture** with appropriate AI components and data flow
3. **Implement production-ready code** with comprehensive error handling
@@ -163,6 +179,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
8. **Provide testing strategies** including adversarial and edge cases
## Example Interactions
+
- "Build a production RAG system for enterprise knowledge base with hybrid search"
- "Implement a multi-agent customer service system with escalation workflows"
- "Design a cost-optimized LLM inference pipeline with caching and load balancing"
diff --git a/skills/analytics-tracking/SKILL.md b/skills/analytics-tracking/SKILL.md
index d25e5f1c..72bcbed0 100644
--- a/skills/analytics-tracking/SKILL.md
+++ b/skills/analytics-tracking/SKILL.md
@@ -1,6 +1,6 @@
---
name: analytics-tracking
-description: ">"
+description: >
Design, audit, and improve analytics tracking systems that produce reliable,
decision-ready data. Use when the user wants to set up, fix, or evaluate
analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs).
diff --git a/skills/angular/SKILL.md b/skills/angular/SKILL.md
index 964a8cc8..7352d107 100644
--- a/skills/angular/SKILL.md
+++ b/skills/angular/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular
-description: ">-"
+description: >-
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone
Components, Zoneless applications, SSR/Hydration, and reactive patterns.
Use PROACTIVELY for Angular development, component architecture, state
diff --git a/skills/api-documenter/SKILL.md b/skills/api-documenter/SKILL.md
index aa613598..f3485bae 100644
--- a/skills/api-documenter/SKILL.md
+++ b/skills/api-documenter/SKILL.md
@@ -1,6 +1,7 @@
---
name: api-documenter
-description: "Master API documentation with OpenAPI 3.1, AI-powered tools, and"
+description: |
+ Master API documentation with OpenAPI 3.1, AI-powered tools, and
modern developer experience practices. Create interactive docs, generate SDKs,
and build comprehensive developer portals. Use PROACTIVELY for API
documentation or developer portal creation.
diff --git a/skills/appdeploy/SKILL.md b/skills/appdeploy/SKILL.md
new file mode 100644
index 00000000..069bb3c6
--- /dev/null
+++ b/skills/appdeploy/SKILL.md
@@ -0,0 +1,209 @@
+---
+name: appdeploy
+description: Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
+allowed-tools:
+ - Bash
+risk: safe
+source: AppDeploy (MIT)
+metadata:
+ author: appdeploy
+ version: "1.0.5"
+---
+
+# AppDeploy Skill
+
+Deploy web apps to AppDeploy via HTTP API.
+
+## When to Use This Skill
+
+- Use when planning or building apps and web apps
+- Use when deploying an app to a public URL
+- Use when publishing a website or web app
+- Use when the user says "deploy this", "make this live", or "give me a URL"
+- Use when updating an already-deployed app
+
+## Setup (First Time Only)
+
+1. **Check for existing API key:**
+ - Look for a `.appdeploy` file in the project root
+ - If it exists and contains a valid `api_key`, skip to Usage
+
+2. **If no API key exists, register and get one:**
+ ```bash
+ curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \
+ -H "Content-Type: application/json" \
+ -d '{"client_name": "claude-code"}'
+ ```
+
+ Response:
+ ```json
+ {
+ "api_key": "ak_...",
+ "user_id": "agent-claude-code-a1b2c3d4",
+ "created_at": 1234567890,
+ "message": "Save this key securely - it cannot be retrieved later"
+ }
+ ```
+
+3. **Save credentials to `.appdeploy`:**
+ ```json
+ {
+ "api_key": "ak_...",
+ "endpoint": "https://api-v2.appdeploy.ai/mcp"
+ }
+ ```
+
+ Add `.appdeploy` to `.gitignore` if not already present.
+
+## Usage
+
+Make JSON-RPC calls to the MCP endpoint:
+
+```bash
+curl -X POST {endpoint} \
+ -H "Content-Type: application/json" \
+ -H "Accept: application/json, text/event-stream" \
+ -H "Authorization: Bearer {api_key}" \
+ -d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "tools/call",
+ "params": {
+ "name": "{tool_name}",
+ "arguments": { ... }
+ }
+ }'
+```
+
+## Workflow
+
+1. **First, get deployment instructions:**
+ Call `get_deploy_instructions` to understand constraints and requirements.
+
+2. **Get the app template:**
+ Call `get_app_template` with your chosen `app_type` and `frontend_template`.
+
+3. **Deploy the app:**
+ Call `deploy_app` with your app files. For new apps, set `app_id` to `null`.
+
+4. **Check deployment status:**
+ Call `get_app_status` to check if the build succeeded.
+
+5. **View/manage your apps:**
+ Use `get_apps` to list your deployed apps.
+
+## Available Tools
+
+### get_deploy_instructions
+
+Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.
+
+**Parameters:**
+
+
+### deploy_app
+
+Use this when the user asks to deploy or publish a website or web app and wants a public URL.
+Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
+
+**Parameters:**
+ - `app_id`: any (required) - existing app id to update, or null for new app
+ - `app_type`: string (required) - app architecture: frontend-only or frontend+backend
+ - `app_name`: string (required) - short display name
+ - `description`: string (optional) - short description of what the app does
+ - `frontend_template`: any (optional) - REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included.
+ - `files`: array (optional) - Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required.
+ - `deletePaths`: array (optional) - Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points.
+ - `model`: string (required) - The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro'
+ - `intent`: string (required) - The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure'
+
+### get_app_template
+
+Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.
+
+**Parameters:**
+ - `app_type`: string (required)
+ - `frontend_template`: string (required) - Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG
+
+### get_app_status
+
+Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `since`: integer (optional) - Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.
+
+### delete_app
+
+Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+
+### get_app_versions
+
+List deployable versions for an existing app. Requires app_id. Returns newest-first {name, version, timestamp} items. Display 'name' to users. DO NOT display the 'version' value to users. Timestamp values MUST be converted to user's local time
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+
+### apply_app_version
+
+Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (required) - Version id to apply
+
+### src_glob
+
+Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to inspect (defaults to applied version)
+ - `path`: string (optional) - Directory path to search within
+ - `glob`: string (optional) - Glob pattern to match files (default: **/*)
+ - `include_dirs`: boolean (optional) - Include directory paths in results
+ - `continuation_token`: string (optional) - Token from previous response for pagination
+
+### src_grep
+
+Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to search (defaults to applied version)
+ - `pattern`: string (required) - Regex pattern to search for (max 500 chars)
+ - `path`: string (optional) - Directory path to search within
+ - `glob`: string (optional) - Glob pattern to filter files (e.g., '*.ts')
+ - `case_insensitive`: boolean (optional) - Enable case-insensitive matching
+ - `output_mode`: string (optional) - content=matching lines, files_with_matches=file paths only, count=match count per file
+ - `before_context`: integer (optional) - Lines to show before each match (0-20)
+ - `after_context`: integer (optional) - Lines to show after each match (0-20)
+ - `context`: integer (optional) - Lines before and after (overrides before/after_context)
+ - `line_numbers`: boolean (optional) - Include line numbers in output
+ - `max_file_size`: integer (optional) - Max file size to scan in bytes (default 10MB)
+ - `continuation_token`: string (optional) - Token from previous response for pagination
+
+### src_read
+
+Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to read from (defaults to applied version)
+ - `file_path`: string (required) - Path to the file to read
+ - `offset`: integer (optional) - Line offset to start reading from (0-indexed)
+ - `limit`: integer (optional) - Number of lines to return (max 2000)
+
+### get_apps
+
+Use this when you need to list apps owned by the current user. Returns app details with display fields for user presentation and data fields for tool chaining.
+
+**Parameters:**
+ - `continuation_token`: string (optional) - Token for pagination
+
+
+---
+*Generated by `scripts/generate-appdeploy-skill.ts`*
diff --git a/skills/arm-cortex-expert/SKILL.md b/skills/arm-cortex-expert/SKILL.md
index 0512c5b9..ddc16100 100644
--- a/skills/arm-cortex-expert/SKILL.md
+++ b/skills/arm-cortex-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: arm-cortex-expert
-description: ">"
+description: >
Senior embedded software engineer specializing in firmware and driver
development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
Decades of experience writing reliable, optimized, and maintainable embedded
diff --git a/skills/azure-ai-agents-persistent-dotnet/SKILL.md b/skills/azure-ai-agents-persistent-dotnet/SKILL.md
index 3979d282..f8fdb292 100644
--- a/skills/azure-ai-agents-persistent-dotnet/SKILL.md
+++ b/skills/azure-ai-agents-persistent-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-agents-persistent-dotnet
-description: "|"
+description: |
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
package: Azure.AI.Agents.Persistent
risk: unknown
diff --git a/skills/azure-ai-agents-persistent-java/SKILL.md b/skills/azure-ai-agents-persistent-java/SKILL.md
index 9c34fc37..fcd77b71 100644
--- a/skills/azure-ai-agents-persistent-java/SKILL.md
+++ b/skills/azure-ai-agents-persistent-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-agents-persistent-java
-description: "|"
+description: |
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.
Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".
package: com.azure:azure-ai-agents-persistent
diff --git a/skills/azure-ai-contentsafety-py/SKILL.md b/skills/azure-ai-contentsafety-py/SKILL.md
index 672acfbc..104f011e 100644
--- a/skills/azure-ai-contentsafety-py/SKILL.md
+++ b/skills/azure-ai-contentsafety-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-contentsafety-py
-description: "|"
+description: |
Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.
Triggers: "azure-ai-contentsafety", "ContentSafetyClient", "content moderation", "harmful content", "text analysis", "image analysis".
package: azure-ai-contentsafety
diff --git a/skills/azure-ai-contentunderstanding-py/SKILL.md b/skills/azure-ai-contentunderstanding-py/SKILL.md
index d6936e74..ba4614ec 100644
--- a/skills/azure-ai-contentunderstanding-py/SKILL.md
+++ b/skills/azure-ai-contentunderstanding-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-contentunderstanding-py
-description: "|"
+description: |
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
Triggers: "azure-ai-contentunderstanding", "ContentUnderstandingClient", "multimodal analysis", "document extraction", "video analysis", "audio transcription".
package: azure-ai-contentunderstanding
diff --git a/skills/azure-ai-document-intelligence-dotnet/SKILL.md b/skills/azure-ai-document-intelligence-dotnet/SKILL.md
index bf04b40f..29e9c380 100644
--- a/skills/azure-ai-document-intelligence-dotnet/SKILL.md
+++ b/skills/azure-ai-document-intelligence-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-document-intelligence-dotnet
-description: "|"
+description: |
Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: "Document Intelligence", "DocumentIntelligenceClient", "form recognizer", "invoice extraction", "receipt OCR", "document analysis .NET".
package: Azure.AI.DocumentIntelligence
risk: unknown
diff --git a/skills/azure-ai-ml-py/SKILL.md b/skills/azure-ai-ml-py/SKILL.md
index d3edddb1..9e22c8d8 100644
--- a/skills/azure-ai-ml-py/SKILL.md
+++ b/skills/azure-ai-ml-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-ml-py
-description: "|"
+description: |
Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.
Triggers: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
package: azure-ai-ml
diff --git a/skills/azure-ai-openai-dotnet/SKILL.md b/skills/azure-ai-openai-dotnet/SKILL.md
index 97437f44..2f52ef0b 100644
--- a/skills/azure-ai-openai-dotnet/SKILL.md
+++ b/skills/azure-ai-openai-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-openai-dotnet
-description: "|"
+description: |
Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: "Azure OpenAI", "AzureOpenAIClient", "ChatClient", "chat completions .NET", "GPT-4", "embeddings", "DALL-E", "Whisper", "OpenAI .NET".
package: Azure.AI.OpenAI
risk: unknown
diff --git a/skills/azure-ai-projects-dotnet/SKILL.md b/skills/azure-ai-projects-dotnet/SKILL.md
index e9199ef3..bcc7e4d5 100644
--- a/skills/azure-ai-projects-dotnet/SKILL.md
+++ b/skills/azure-ai-projects-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-projects-dotnet
-description: "|"
+description: |
Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents", "evaluations", "datasets", "connections", "deployments .NET".
package: Azure.AI.Projects
risk: unknown
diff --git a/skills/azure-ai-projects-java/SKILL.md b/skills/azure-ai-projects-java/SKILL.md
index 1e4b9167..3ac3ff82 100644
--- a/skills/azure-ai-projects-java/SKILL.md
+++ b/skills/azure-ai-projects-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-projects-java
-description: "|"
+description: |
Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.
Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".
package: com.azure:azure-ai-projects
diff --git a/skills/azure-ai-textanalytics-py/SKILL.md b/skills/azure-ai-textanalytics-py/SKILL.md
index ae54fb5c..e9ef631d 100644
--- a/skills/azure-ai-textanalytics-py/SKILL.md
+++ b/skills/azure-ai-textanalytics-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-textanalytics-py
-description: "|"
+description: |
Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.
Triggers: "text analytics", "sentiment analysis", "entity recognition", "key phrase", "PII detection", "TextAnalyticsClient".
package: azure-ai-textanalytics
diff --git a/skills/azure-ai-transcription-py/SKILL.md b/skills/azure-ai-transcription-py/SKILL.md
index 216c20b0..f0ca97c9 100644
--- a/skills/azure-ai-transcription-py/SKILL.md
+++ b/skills/azure-ai-transcription-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-transcription-py
-description: "|"
+description: |
Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.
Triggers: "transcription", "speech to text", "Azure AI Transcription", "TranscriptionClient".
package: azure-ai-transcription
diff --git a/skills/azure-ai-translation-document-py/SKILL.md b/skills/azure-ai-translation-document-py/SKILL.md
index c7e1ee0f..9183d0fc 100644
--- a/skills/azure-ai-translation-document-py/SKILL.md
+++ b/skills/azure-ai-translation-document-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-translation-document-py
-description: "|"
+description: |
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
package: azure-ai-translation-document
diff --git a/skills/azure-ai-translation-text-py/SKILL.md b/skills/azure-ai-translation-text-py/SKILL.md
index 7bf2779b..ca2f411b 100644
--- a/skills/azure-ai-translation-text-py/SKILL.md
+++ b/skills/azure-ai-translation-text-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-translation-text-py
-description: "|"
+description: |
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.
Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
package: azure-ai-translation-text
diff --git a/skills/azure-ai-vision-imageanalysis-py/SKILL.md b/skills/azure-ai-vision-imageanalysis-py/SKILL.md
index 572781cb..bb773c21 100644
--- a/skills/azure-ai-vision-imageanalysis-py/SKILL.md
+++ b/skills/azure-ai-vision-imageanalysis-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-vision-imageanalysis-py
-description: "|"
+description: |
Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.
Triggers: "image analysis", "computer vision", "OCR", "object detection", "ImageAnalysisClient", "image caption".
package: azure-ai-vision-imageanalysis
diff --git a/skills/azure-ai-voicelive-dotnet/SKILL.md b/skills/azure-ai-voicelive-dotnet/SKILL.md
index e52481a5..9db74f00 100644
--- a/skills/azure-ai-voicelive-dotnet/SKILL.md
+++ b/skills/azure-ai-voicelive-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-dotnet
-description: "|"
+description: |
Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant .NET", "bidirectional audio", "speech-to-speech".
package: Azure.AI.VoiceLive
risk: unknown
diff --git a/skills/azure-ai-voicelive-java/SKILL.md b/skills/azure-ai-voicelive-java/SKILL.md
index 9c3e1306..505a48ee 100644
--- a/skills/azure-ai-voicelive-java/SKILL.md
+++ b/skills/azure-ai-voicelive-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-java
-description: "|"
+description: |
Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.
Triggers: "VoiceLiveClient java", "voice assistant java", "real-time voice java", "audio streaming java", "voice activity detection java".
package: com.azure:azure-ai-voicelive
diff --git a/skills/azure-ai-voicelive-ts/SKILL.md b/skills/azure-ai-voicelive-ts/SKILL.md
index 5e13f368..25ab69c3 100644
--- a/skills/azure-ai-voicelive-ts/SKILL.md
+++ b/skills/azure-ai-voicelive-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-ts
-description: "|"
+description: |
Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant TypeScript", "bidirectional audio", "speech-to-speech JavaScript".
package: "@azure/ai-voicelive"
risk: unknown
diff --git a/skills/azure-appconfiguration-java/SKILL.md b/skills/azure-appconfiguration-java/SKILL.md
index e4560c24..5b0bc039 100644
--- a/skills/azure-appconfiguration-java/SKILL.md
+++ b/skills/azure-appconfiguration-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-appconfiguration-java
-description: "|"
+description: |
Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.
Triggers: "ConfigurationClient java", "app configuration java", "feature flag java", "configuration setting java", "azure config java".
package: com.azure:azure-data-appconfiguration
diff --git a/skills/azure-appconfiguration-py/SKILL.md b/skills/azure-appconfiguration-py/SKILL.md
index c1da4e42..d02fbeef 100644
--- a/skills/azure-appconfiguration-py/SKILL.md
+++ b/skills/azure-appconfiguration-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-appconfiguration-py
-description: "|"
+description: |
Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.
Triggers: "azure-appconfiguration", "AzureAppConfigurationClient", "feature flags", "configuration", "key-value settings".
package: azure-appconfiguration
diff --git a/skills/azure-compute-batch-java/SKILL.md b/skills/azure-compute-batch-java/SKILL.md
index 993554e9..8da9c747 100644
--- a/skills/azure-compute-batch-java/SKILL.md
+++ b/skills/azure-compute-batch-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-compute-batch-java
-description: "|"
+description: |
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
Triggers: "BatchClient java", "azure batch java", "batch pool java", "batch job java", "HPC java", "parallel computing java".
risk: unknown
diff --git a/skills/azure-containerregistry-py/SKILL.md b/skills/azure-containerregistry-py/SKILL.md
index 76f76a65..aa2f6aee 100644
--- a/skills/azure-containerregistry-py/SKILL.md
+++ b/skills/azure-containerregistry-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-containerregistry-py
-description: "|"
+description: |
Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".
package: azure-containerregistry
diff --git a/skills/azure-cosmos-java/SKILL.md b/skills/azure-cosmos-java/SKILL.md
index d71dfa6d..e8dccae8 100644
--- a/skills/azure-cosmos-java/SKILL.md
+++ b/skills/azure-cosmos-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-java
-description: "|"
+description: |
Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.
Triggers: "CosmosClient java", "CosmosAsyncClient", "cosmos database java", "cosmosdb java", "document database java".
package: azure-cosmos
diff --git a/skills/azure-cosmos-py/SKILL.md b/skills/azure-cosmos-py/SKILL.md
index 11903d99..90e86b4a 100644
--- a/skills/azure-cosmos-py/SKILL.md
+++ b/skills/azure-cosmos-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-py
-description: "|"
+description: |
Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db", "CosmosClient", "container", "document", "NoSQL", "partition key".
package: azure-cosmos
diff --git a/skills/azure-cosmos-rust/SKILL.md b/skills/azure-cosmos-rust/SKILL.md
index d8e3ad7a..ec7387aa 100644
--- a/skills/azure-cosmos-rust/SKILL.md
+++ b/skills/azure-cosmos-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-rust
-description: "|"
+description: |
Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db rust", "CosmosClient rust", "container", "document rust", "NoSQL rust", "partition key".
package: azure_data_cosmos
diff --git a/skills/azure-cosmos-ts/SKILL.md b/skills/azure-cosmos-ts/SKILL.md
index a6a2a5cf..d09d11a2 100644
--- a/skills/azure-cosmos-ts/SKILL.md
+++ b/skills/azure-cosmos-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-ts
-description: "|"
+description: |
Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: "Cosmos DB", "@azure/cosmos", "CosmosClient", "document CRUD", "NoSQL queries", "bulk operations", "partition key", "container.items".
package: "@azure/cosmos"
risk: unknown
diff --git a/skills/azure-data-tables-py/SKILL.md b/skills/azure-data-tables-py/SKILL.md
index 7abbdcd5..6fedc112 100644
--- a/skills/azure-data-tables-py/SKILL.md
+++ b/skills/azure-data-tables-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-data-tables-py
-description: "|"
+description: |
Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.
Triggers: "table storage", "TableServiceClient", "TableClient", "entities", "PartitionKey", "RowKey".
package: azure-data-tables
diff --git a/skills/azure-eventgrid-dotnet/SKILL.md b/skills/azure-eventgrid-dotnet/SKILL.md
index 0f180e9c..3fca07ca 100644
--- a/skills/azure-eventgrid-dotnet/SKILL.md
+++ b/skills/azure-eventgrid-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventgrid-dotnet
-description: "|"
+description: |
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven", "pub/sub".
package: Azure.Messaging.EventGrid
risk: unknown
diff --git a/skills/azure-eventgrid-py/SKILL.md b/skills/azure-eventgrid-py/SKILL.md
index ddfe5c1f..bb801f99 100644
--- a/skills/azure-eventgrid-py/SKILL.md
+++ b/skills/azure-eventgrid-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventgrid-py
-description: "|"
+description: |
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
Triggers: "event grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events".
package: azure-eventgrid
diff --git a/skills/azure-eventhub-dotnet/SKILL.md b/skills/azure-eventhub-dotnet/SKILL.md
index 1ba7c843..06cf909e 100644
--- a/skills/azure-eventhub-dotnet/SKILL.md
+++ b/skills/azure-eventhub-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-dotnet
-description: "|"
+description: |
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming", "EventHubProducerClient", "EventProcessorClient", "send events", "receive events", "checkpointing", "partition".
package: Azure.Messaging.EventHubs
risk: unknown
diff --git a/skills/azure-eventhub-py/SKILL.md b/skills/azure-eventhub-py/SKILL.md
index 3914b7c8..82da2387 100644
--- a/skills/azure-eventhub-py/SKILL.md
+++ b/skills/azure-eventhub-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-py
-description: "|"
+description: |
Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.
Triggers: "event hubs", "EventHubProducerClient", "EventHubConsumerClient", "streaming", "partitions".
package: azure-eventhub
diff --git a/skills/azure-eventhub-rust/SKILL.md b/skills/azure-eventhub-rust/SKILL.md
index 702cc64e..2477807e 100644
--- a/skills/azure-eventhub-rust/SKILL.md
+++ b/skills/azure-eventhub-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-rust
-description: "|"
+description: |
Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.
Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust".
package: azure_messaging_eventhubs
diff --git a/skills/azure-identity-dotnet/SKILL.md b/skills/azure-identity-dotnet/SKILL.md
index d8e4b54e..c3be00b7 100644
--- a/skills/azure-identity-dotnet/SKILL.md
+++ b/skills/azure-identity-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-dotnet
-description: "|"
+description: |
Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: "Azure Identity", "DefaultAzureCredential", "ManagedIdentityCredential", "ClientSecretCredential", "authentication .NET", "Azure auth", "credential chain".
package: Azure.Identity
risk: unknown
diff --git a/skills/azure-identity-py/SKILL.md b/skills/azure-identity-py/SKILL.md
index 88555e3c..c55dad89 100644
--- a/skills/azure-identity-py/SKILL.md
+++ b/skills/azure-identity-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-py
-description: "|"
+description: |
Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.
Triggers: "azure-identity", "DefaultAzureCredential", "authentication", "managed identity", "service principal", "credential".
package: azure-identity
diff --git a/skills/azure-identity-rust/SKILL.md b/skills/azure-identity-rust/SKILL.md
index 8ed389ce..c2583c0f 100644
--- a/skills/azure-identity-rust/SKILL.md
+++ b/skills/azure-identity-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-rust
-description: "|"
+description: |
Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.
Triggers: "azure-identity", "DeveloperToolsCredential", "authentication rust", "managed identity rust", "credential rust".
package: azure_identity
diff --git a/skills/azure-keyvault-certificates-rust/SKILL.md b/skills/azure-keyvault-certificates-rust/SKILL.md
index 60452370..b46965d4 100644
--- a/skills/azure-keyvault-certificates-rust/SKILL.md
+++ b/skills/azure-keyvault-certificates-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-certificates-rust
-description: "|"
+description: |
Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.
Triggers: "keyvault certificates rust", "CertificateClient rust", "create certificate rust", "import certificate rust".
package: azure_security_keyvault_certificates
diff --git a/skills/azure-keyvault-keys-rust/SKILL.md b/skills/azure-keyvault-keys-rust/SKILL.md
index c88a11e3..516fadcb 100644
--- a/skills/azure-keyvault-keys-rust/SKILL.md
+++ b/skills/azure-keyvault-keys-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-keys-rust
-description: "|"
+description: |
Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.
Triggers: "keyvault keys rust", "KeyClient rust", "create key rust", "encrypt rust", "sign rust".
package: azure_security_keyvault_keys
diff --git a/skills/azure-keyvault-py/SKILL.md b/skills/azure-keyvault-py/SKILL.md
index 0709c5fa..ac389a32 100644
--- a/skills/azure-keyvault-py/SKILL.md
+++ b/skills/azure-keyvault-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-py
-description: "|"
+description: |
Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.
Triggers: "key vault", "SecretClient", "KeyClient", "CertificateClient", "secrets", "encryption keys".
package: azure-keyvault-secrets, azure-keyvault-keys, azure-keyvault-certificates
diff --git a/skills/azure-keyvault-secrets-rust/SKILL.md b/skills/azure-keyvault-secrets-rust/SKILL.md
index af92fbd3..30422f93 100644
--- a/skills/azure-keyvault-secrets-rust/SKILL.md
+++ b/skills/azure-keyvault-secrets-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-secrets-rust
-description: "|"
+description: |
Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.
Triggers: "keyvault secrets rust", "SecretClient rust", "get secret rust", "set secret rust".
package: azure_security_keyvault_secrets
diff --git a/skills/azure-maps-search-dotnet/SKILL.md b/skills/azure-maps-search-dotnet/SKILL.md
index 7fd23ea8..5688d5a1 100644
--- a/skills/azure-maps-search-dotnet/SKILL.md
+++ b/skills/azure-maps-search-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-maps-search-dotnet
-description: "|"
+description: |
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route directions", "map tiles", "geolocation".
package: Azure.Maps.Search
risk: unknown
diff --git a/skills/azure-messaging-webpubsubservice-py/SKILL.md b/skills/azure-messaging-webpubsubservice-py/SKILL.md
index e0c1f565..b3a686c8 100644
--- a/skills/azure-messaging-webpubsubservice-py/SKILL.md
+++ b/skills/azure-messaging-webpubsubservice-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-messaging-webpubsubservice-py
-description: "|"
+description: |
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.
Triggers: "azure-messaging-webpubsubservice", "WebPubSubServiceClient", "real-time", "WebSocket", "pub/sub".
package: azure-messaging-webpubsubservice
diff --git a/skills/azure-mgmt-apicenter-dotnet/SKILL.md b/skills/azure-mgmt-apicenter-dotnet/SKILL.md
index e5052bb2..cfa82d7b 100644
--- a/skills/azure-mgmt-apicenter-dotnet/SKILL.md
+++ b/skills/azure-mgmt-apicenter-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apicenter-dotnet
-description: "|"
+description: |
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API inventory", "API governance", "API versioning", "API catalog", "API discovery".
package: Azure.ResourceManager.ApiCenter
risk: unknown
diff --git a/skills/azure-mgmt-apicenter-py/SKILL.md b/skills/azure-mgmt-apicenter-py/SKILL.md
index 2a07de6d..6b0a39dc 100644
--- a/skills/azure-mgmt-apicenter-py/SKILL.md
+++ b/skills/azure-mgmt-apicenter-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apicenter-py
-description: "|"
+description: |
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
Triggers: "azure-mgmt-apicenter", "ApiCenterMgmtClient", "API Center", "API inventory", "API governance".
package: azure-mgmt-apicenter
diff --git a/skills/azure-mgmt-apimanagement-dotnet/SKILL.md b/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
index 19df092d..73fe5274 100644
--- a/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
+++ b/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apimanagement-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: "API Management", "APIM service", "create APIM", "manage APIs", "ApiManagementServiceResource", "API policies", "APIM products", "APIM subscriptions".
package: Azure.ResourceManager.ApiManagement
risk: unknown
diff --git a/skills/azure-mgmt-apimanagement-py/SKILL.md b/skills/azure-mgmt-apimanagement-py/SKILL.md
index 64d63bd0..b0d4dcbc 100644
--- a/skills/azure-mgmt-apimanagement-py/SKILL.md
+++ b/skills/azure-mgmt-apimanagement-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apimanagement-py
-description: "|"
+description: |
Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.
Triggers: "azure-mgmt-apimanagement", "ApiManagementClient", "APIM", "API gateway", "API Management".
package: azure-mgmt-apimanagement
diff --git a/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md b/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
index d94beffc..d9a0482f 100644
--- a/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
+++ b/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-applicationinsights-dotnet
-description: "|"
+description: |
Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: "Application Insights", "ApplicationInsights", "App Insights", "APM", "application monitoring", "web tests", "availability tests", "workbooks".
package: Azure.ResourceManager.ApplicationInsights
risk: unknown
diff --git a/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md b/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
index 4330e176..b8c213df 100644
--- a/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
+++ b/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-arizeaiobservabilityeval-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations
on Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability
into .NET applications. Triggers: "Arize AI", "ML observability", "ArizeAIObservabilityEval", "Arize organization".
diff --git a/skills/azure-mgmt-botservice-dotnet/SKILL.md b/skills/azure-mgmt-botservice-dotnet/SKILL.md
index 94d8824f..56bbcabd 100644
--- a/skills/azure-mgmt-botservice-dotnet/SKILL.md
+++ b/skills/azure-mgmt-botservice-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-botservice-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
package: Azure.ResourceManager.BotService
risk: unknown
diff --git a/skills/azure-mgmt-botservice-py/SKILL.md b/skills/azure-mgmt-botservice-py/SKILL.md
index c6b851be..b954c17f 100644
--- a/skills/azure-mgmt-botservice-py/SKILL.md
+++ b/skills/azure-mgmt-botservice-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-botservice-py
-description: "|"
+description: |
Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.
Triggers: "azure-mgmt-botservice", "AzureBotService", "bot management", "conversational AI", "bot channels".
risk: unknown
diff --git a/skills/azure-mgmt-fabric-dotnet/SKILL.md b/skills/azure-mgmt-fabric-dotnet/SKILL.md
index 9721d0dd..6076541f 100644
--- a/skills/azure-mgmt-fabric-dotnet/SKILL.md
+++ b/skills/azure-mgmt-fabric-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-fabric-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity", "Fabric SKU", "provision Fabric", "ARM Fabric", "FabricCapacityResource".
package: Azure.ResourceManager.Fabric
risk: unknown
diff --git a/skills/azure-mgmt-fabric-py/SKILL.md b/skills/azure-mgmt-fabric-py/SKILL.md
index 2e2ff79b..e4c78ea3 100644
--- a/skills/azure-mgmt-fabric-py/SKILL.md
+++ b/skills/azure-mgmt-fabric-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-fabric-py
-description: "|"
+description: |
Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.
Triggers: "azure-mgmt-fabric", "FabricMgmtClient", "Fabric capacity", "Microsoft Fabric", "Power BI capacity".
risk: unknown
diff --git a/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md b/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
index c08a2fd3..ece97788 100644
--- a/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
+++ b/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-weightsandbiases-dotnet
-description: "|"
+description: |
Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: "Weights and Biases", "W&B", "WeightsAndBiases", "ML experiment tracking", "model registry", "experiment management", "wandb".
package: Azure.ResourceManager.WeightsAndBiases
risk: unknown
diff --git a/skills/azure-monitor-ingestion-java/SKILL.md b/skills/azure-monitor-ingestion-java/SKILL.md
index a288b279..dbba70cc 100644
--- a/skills/azure-monitor-ingestion-java/SKILL.md
+++ b/skills/azure-monitor-ingestion-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-ingestion-java
-description: "|"
+description: |
Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).
Triggers: "LogsIngestionClient java", "azure monitor ingestion java", "custom logs java", "DCR java", "data collection rule java".
package: com.azure:azure-monitor-ingestion
diff --git a/skills/azure-monitor-ingestion-py/SKILL.md b/skills/azure-monitor-ingestion-py/SKILL.md
index c14e9c95..cff95c04 100644
--- a/skills/azure-monitor-ingestion-py/SKILL.md
+++ b/skills/azure-monitor-ingestion-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-ingestion-py
-description: "|"
+description: |
Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.
Triggers: "azure-monitor-ingestion", "LogsIngestionClient", "custom logs", "DCR", "data collection rule", "Log Analytics".
package: azure-monitor-ingestion
diff --git a/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md b/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
index 5cbddf1d..275c343c 100644
--- a/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
+++ b/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-exporter-java
-description: "|"
+description: |
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.
Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java".
Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.
diff --git a/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md b/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
index b78077e4..3218be18 100644
--- a/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
+++ b/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-exporter-py
-description: "|"
+description: |
Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.
Triggers: "azure-monitor-opentelemetry-exporter", "AzureMonitorTraceExporter", "AzureMonitorMetricExporter", "AzureMonitorLogExporter".
package: azure-monitor-opentelemetry-exporter
diff --git a/skills/azure-monitor-opentelemetry-py/SKILL.md b/skills/azure-monitor-opentelemetry-py/SKILL.md
index 93739fcf..b9f55503 100644
--- a/skills/azure-monitor-opentelemetry-py/SKILL.md
+++ b/skills/azure-monitor-opentelemetry-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-py
-description: "|"
+description: |
Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.
Triggers: "azure-monitor-opentelemetry", "configure_azure_monitor", "Application Insights", "OpenTelemetry distro", "auto-instrumentation".
package: azure-monitor-opentelemetry
diff --git a/skills/azure-monitor-query-java/SKILL.md b/skills/azure-monitor-query-java/SKILL.md
index f03398d1..02db8627 100644
--- a/skills/azure-monitor-query-java/SKILL.md
+++ b/skills/azure-monitor-query-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-query-java
-description: "|"
+description: |
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
Triggers: "LogsQueryClient java", "MetricsQueryClient java", "kusto query java", "log analytics java", "azure monitor query java".
Note: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.
diff --git a/skills/azure-monitor-query-py/SKILL.md b/skills/azure-monitor-query-py/SKILL.md
index 44c5028e..36fa0a65 100644
--- a/skills/azure-monitor-query-py/SKILL.md
+++ b/skills/azure-monitor-query-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-query-py
-description: "|"
+description: |
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
Triggers: "azure-monitor-query", "LogsQueryClient", "MetricsQueryClient", "Log Analytics", "Kusto queries", "Azure metrics".
package: azure-monitor-query
diff --git a/skills/azure-postgres-ts/SKILL.md b/skills/azure-postgres-ts/SKILL.md
index 23ebed5f..76f2adff 100644
--- a/skills/azure-postgres-ts/SKILL.md
+++ b/skills/azure-postgres-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-postgres-ts
-description: "|"
+description: |
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL connection", "PostgreSQL TypeScript", "pg Pool", "passwordless postgres".
package: pg
risk: unknown
diff --git a/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md b/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
index b5a1633e..d525cc85 100644
--- a/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-cosmosdb-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: "Cosmos DB account", "create Cosmos account", "manage Cosmos resources", "ARM Cosmos", "CosmosDBAccountResource", "provision Cosmos DB".
package: Azure.ResourceManager.CosmosDB
risk: unknown
diff --git a/skills/azure-resource-manager-durabletask-dotnet/SKILL.md b/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
index 40f79c81..0aaff756 100644
--- a/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-durabletask-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision Durable Task", "orchestration scheduler".
package: Azure.ResourceManager.DurableTask
risk: unknown
diff --git a/skills/azure-resource-manager-mysql-dotnet/SKILL.md b/skills/azure-resource-manager-mysql-dotnet/SKILL.md
index 6a5140d9..20ae4466 100644
--- a/skills/azure-resource-manager-mysql-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-mysql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-mysql-dotnet
-description: "|"
+description: |
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database management", "MySQL firewall", "MySQL backup".
package: Azure.ResourceManager.MySql
risk: unknown
diff --git a/skills/azure-resource-manager-playwright-dotnet/SKILL.md b/skills/azure-resource-manager-playwright-dotnet/SKILL.md
index ad780184..afb448fc 100644
--- a/skills/azure-resource-manager-playwright-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-playwright-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-playwright-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
package: Azure.ResourceManager.Playwright
risk: unknown
diff --git a/skills/azure-resource-manager-postgresql-dotnet/SKILL.md b/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
index c3cefe84..f8319426 100644
--- a/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-postgresql-dotnet
-description: "|"
+description: |
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
package: Azure.ResourceManager.PostgreSql
risk: unknown
diff --git a/skills/azure-resource-manager-redis-dotnet/SKILL.md b/skills/azure-resource-manager-redis-dotnet/SKILL.md
index 96175c18..7fa278b1 100644
--- a/skills/azure-resource-manager-redis-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-redis-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-redis-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".
package: Azure.ResourceManager.Redis
risk: unknown
diff --git a/skills/azure-resource-manager-sql-dotnet/SKILL.md b/skills/azure-resource-manager-sql-dotnet/SKILL.md
index 0f98adf5..3da3fa13 100644
--- a/skills/azure-resource-manager-sql-dotnet/SKILL.md
+++ b/skills/azure-resource-manager-sql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-sql-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
package: Azure.ResourceManager.Sql
risk: unknown
diff --git a/skills/azure-search-documents-dotnet/SKILL.md b/skills/azure-search-documents-dotnet/SKILL.md
index 954fad18..d3d61d12 100644
--- a/skills/azure-search-documents-dotnet/SKILL.md
+++ b/skills/azure-search-documents-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-search-documents-dotnet
-description: "|"
+description: |
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET", "SearchClient", "SearchIndexClient", "vector search C#", "semantic search .NET", "hybrid search", "Azure.Search.Documents".
package: Azure.Search.Documents
risk: unknown
diff --git a/skills/azure-search-documents-py/SKILL.md b/skills/azure-search-documents-py/SKILL.md
index a481063b..a759bdef 100644
--- a/skills/azure-search-documents-py/SKILL.md
+++ b/skills/azure-search-documents-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-search-documents-py
-description: "|"
+description: |
Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.
Triggers: "azure-search-documents", "SearchClient", "SearchIndexClient", "vector search", "hybrid search", "semantic search".
package: azure-search-documents
diff --git a/skills/azure-security-keyvault-keys-dotnet/SKILL.md b/skills/azure-security-keyvault-keys-dotnet/SKILL.md
index ba20d0e2..68d1266c 100644
--- a/skills/azure-security-keyvault-keys-dotnet/SKILL.md
+++ b/skills/azure-security-keyvault-keys-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-security-keyvault-keys-dotnet
-description: "|"
+description: |
Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: "Key Vault keys", "KeyClient", "CryptographyClient", "RSA key", "EC key", "encrypt decrypt .NET", "key rotation", "HSM".
package: Azure.Security.KeyVault.Keys
risk: unknown
diff --git a/skills/azure-servicebus-dotnet/SKILL.md b/skills/azure-servicebus-dotnet/SKILL.md
index 22fb9891..f35c51bb 100644
--- a/skills/azure-servicebus-dotnet/SKILL.md
+++ b/skills/azure-servicebus-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-servicebus-dotnet
-description: "|"
+description: |
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
package: Azure.Messaging.ServiceBus
risk: unknown
diff --git a/skills/azure-servicebus-py/SKILL.md b/skills/azure-servicebus-py/SKILL.md
index 6e82b598..48e59609 100644
--- a/skills/azure-servicebus-py/SKILL.md
+++ b/skills/azure-servicebus-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-servicebus-py
-description: "|"
+description: |
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
Triggers: "service bus", "ServiceBusClient", "queue", "topic", "subscription", "message broker".
package: azure-servicebus
diff --git a/skills/azure-speech-to-text-rest-py/SKILL.md b/skills/azure-speech-to-text-rest-py/SKILL.md
index a9781432..e1f7de6d 100644
--- a/skills/azure-speech-to-text-rest-py/SKILL.md
+++ b/skills/azure-speech-to-text-rest-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-speech-to-text-rest-py
-description: "|"
+description: |
Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.
Triggers: "speech to text REST", "short audio transcription", "speech recognition REST API", "STT REST", "recognize speech REST".
DO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.
diff --git a/skills/azure-storage-blob-py/SKILL.md b/skills/azure-storage-blob-py/SKILL.md
index 6ebe6b36..f97d7347 100644
--- a/skills/azure-storage-blob-py/SKILL.md
+++ b/skills/azure-storage-blob-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-py
-description: "|"
+description: |
Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.
Triggers: "blob storage", "BlobServiceClient", "ContainerClient", "BlobClient", "upload blob", "download blob".
package: azure-storage-blob
diff --git a/skills/azure-storage-blob-rust/SKILL.md b/skills/azure-storage-blob-rust/SKILL.md
index 2b43e56b..26d565e6 100644
--- a/skills/azure-storage-blob-rust/SKILL.md
+++ b/skills/azure-storage-blob-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-rust
-description: "|"
+description: |
Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.
Triggers: "blob storage rust", "BlobClient rust", "upload blob rust", "download blob rust", "container rust".
package: azure_storage_blob
diff --git a/skills/azure-storage-blob-ts/SKILL.md b/skills/azure-storage-blob-ts/SKILL.md
index f941ba21..c5450d8c 100644
--- a/skills/azure-storage-blob-ts/SKILL.md
+++ b/skills/azure-storage-blob-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-ts
-description: "|"
+description: |
Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: "blob storage", "@azure/storage-blob", "BlobServiceClient", "ContainerClient", "upload blob", "download blob", "SAS token", "block blob".
package: "@azure/storage-blob"
risk: unknown
diff --git a/skills/azure-storage-file-datalake-py/SKILL.md b/skills/azure-storage-file-datalake-py/SKILL.md
index 05c70fd8..585c9cbe 100644
--- a/skills/azure-storage-file-datalake-py/SKILL.md
+++ b/skills/azure-storage-file-datalake-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-datalake-py
-description: "|"
+description: |
Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.
Triggers: "data lake", "DataLakeServiceClient", "FileSystemClient", "ADLS Gen2", "hierarchical namespace".
package: azure-storage-file-datalake
diff --git a/skills/azure-storage-file-share-py/SKILL.md b/skills/azure-storage-file-share-py/SKILL.md
index 2889a9ff..676952c1 100644
--- a/skills/azure-storage-file-share-py/SKILL.md
+++ b/skills/azure-storage-file-share-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-share-py
-description: "|"
+description: |
Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.
Triggers: "azure-storage-file-share", "ShareServiceClient", "ShareClient", "file share", "SMB".
risk: unknown
diff --git a/skills/azure-storage-file-share-ts/SKILL.md b/skills/azure-storage-file-share-ts/SKILL.md
index 6e9bae7f..c6c0f24a 100644
--- a/skills/azure-storage-file-share-ts/SKILL.md
+++ b/skills/azure-storage-file-share-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-share-ts
-description: "|"
+description: |
Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: "file share", "@azure/storage-file-share", "ShareServiceClient", "ShareClient", "SMB", "Azure Files".
package: "@azure/storage-file-share"
risk: unknown
diff --git a/skills/azure-storage-queue-py/SKILL.md b/skills/azure-storage-queue-py/SKILL.md
index 38c91d03..39b4a270 100644
--- a/skills/azure-storage-queue-py/SKILL.md
+++ b/skills/azure-storage-queue-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-queue-py
-description: "|"
+description: |
Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.
Triggers: "queue storage", "QueueServiceClient", "QueueClient", "message queue", "dequeue".
package: azure-storage-queue
diff --git a/skills/azure-storage-queue-ts/SKILL.md b/skills/azure-storage-queue-ts/SKILL.md
index d06d259f..244a5051 100644
--- a/skills/azure-storage-queue-ts/SKILL.md
+++ b/skills/azure-storage-queue-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-queue-ts
-description: "|"
+description: |
Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: "queue storage", "@azure/storage-queue", "QueueServiceClient", "QueueClient", "send message", "receive message", "dequeue", "visibility timeout".
package: "@azure/storage-queue"
risk: unknown
diff --git a/skills/backend-architect/SKILL.md b/skills/backend-architect/SKILL.md
index e2283367..c5eba207 100644
--- a/skills/backend-architect/SKILL.md
+++ b/skills/backend-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: backend-architect
-description: "Expert backend architect specializing in scalable API design,"
+description: |
+ Expert backend architect specializing in scalable API design,
microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC
APIs, event-driven architectures, service mesh patterns, and modern backend
frameworks. Handles service boundary definition, inter-service communication,
diff --git a/skills/backend-security-coder/SKILL.md b/skills/backend-security-coder/SKILL.md
index 799b496d..d97c9883 100644
--- a/skills/backend-security-coder/SKILL.md
+++ b/skills/backend-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: backend-security-coder
-description: "Expert in secure backend coding practices specializing in input"
+description: |
+ Expert in secure backend coding practices specializing in input
validation, authentication, and API security. Use PROACTIVELY for backend
security implementations or security code reviews.
metadata:
diff --git a/skills/bash-pro/SKILL.md b/skills/bash-pro/SKILL.md
index 3beb7730..6dd19742 100644
--- a/skills/bash-pro/SKILL.md
+++ b/skills/bash-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: bash-pro
-description: "Master of defensive Bash scripting for production automation, CI/CD"
+description: |
+ Master of defensive Bash scripting for production automation, CI/CD
pipelines, and system utilities. Expert in safe, portable, and testable shell
scripts.
metadata:
diff --git a/skills/bevy-ecs-expert/SKILL.md b/skills/bevy-ecs-expert/SKILL.md
index 7d6333e5..ebac97be 100644
--- a/skills/bevy-ecs-expert/SKILL.md
+++ b/skills/bevy-ecs-expert/SKILL.md
@@ -83,25 +83,27 @@ fn main() {
## Examples
-### Example 1: Spawning Entities with Bundles
+### Example 1: Spawning Entities with Require Component
```rust
-#[derive(Bundle)]
-struct PlayerBundle {
- player: Player,
- velocity: Velocity,
- sprite: SpriteBundle,
+use bevy::prelude::*;
+
+#[derive(Component, Reflect, Default)]
+#[require(Velocity, Sprite)]
+struct Player;
+
+#[derive(Component, Default)]
+struct Velocity {
+ x: f32,
+ y: f32,
}
fn setup(mut commands: Commands, asset_server: Res) {
- commands.spawn(PlayerBundle {
- player: Player,
- velocity: Velocity { x: 10.0, y: 0.0 },
- sprite: SpriteBundle {
- texture: asset_server.load("player.png"),
- ..default()
- },
- });
+ commands.spawn((
+ Player,
+ Velocity { x: 10.0, y: 0.0 },
+ Sprite::from_image(asset_server.load("player.png")),
+ ));
}
```
diff --git a/skills/blockchain-developer/SKILL.md b/skills/blockchain-developer/SKILL.md
index 192c89fb..c23f36d7 100644
--- a/skills/blockchain-developer/SKILL.md
+++ b/skills/blockchain-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: blockchain-developer
-description: "Build production-ready Web3 applications, smart contracts, and"
+description: |
+ Build production-ready Web3 applications, smart contracts, and
decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and
enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3
apps, DeFi protocols, or blockchain infrastructure.
diff --git a/skills/business-analyst/SKILL.md b/skills/business-analyst/SKILL.md
index ca931200..1a4462b4 100644
--- a/skills/business-analyst/SKILL.md
+++ b/skills/business-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: business-analyst
-description: "Master modern business analysis with AI-powered analytics,"
+description: |
+ Master modern business analysis with AI-powered analytics,
real-time dashboards, and data-driven insights. Build comprehensive KPI
frameworks, predictive models, and strategic recommendations. Use PROACTIVELY
for business intelligence or strategic analysis.
diff --git a/skills/c4-code/SKILL.md b/skills/c4-code/SKILL.md
index 333ab01b..59972a01 100644
--- a/skills/c4-code/SKILL.md
+++ b/skills/c4-code/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-code
-description: "Expert C4 Code-level documentation specialist. Analyzes code"
+description: |
+ Expert C4 Code-level documentation specialist. Analyzes code
directories to create comprehensive C4 code-level documentation including
function signatures, arguments, dependencies, and code structure. Use when
documenting code at the lowest C4 level for individual directories and code
diff --git a/skills/c4-component/SKILL.md b/skills/c4-component/SKILL.md
index 64c14978..deca5509 100644
--- a/skills/c4-component/SKILL.md
+++ b/skills/c4-component/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-component
-description: "Expert C4 Component-level documentation specialist. Synthesizes C4"
+description: |
+ Expert C4 Component-level documentation specialist. Synthesizes C4
Code-level documentation into Component-level architecture, defining component
boundaries, interfaces, and relationships. Creates component diagrams and
documentation. Use when synthesizing code-level documentation into logical
diff --git a/skills/c4-container/SKILL.md b/skills/c4-container/SKILL.md
index c41f6586..297a4e2b 100644
--- a/skills/c4-container/SKILL.md
+++ b/skills/c4-container/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-container
-description: "Expert C4 Container-level documentation specialist. Synthesizes"
+description: |
+ Expert C4 Container-level documentation specialist. Synthesizes
Component-level documentation into Container-level architecture, mapping
components to deployment units, documenting container interfaces as APIs, and
creating container diagrams. Use when synthesizing components into deployment
diff --git a/skills/c4-context/SKILL.md b/skills/c4-context/SKILL.md
index cf5688d0..4d1a5a52 100644
--- a/skills/c4-context/SKILL.md
+++ b/skills/c4-context/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-context
-description: "Expert C4 Context-level documentation specialist. Creates"
+description: |
+ Expert C4 Context-level documentation specialist. Creates
high-level system context diagrams, documents personas, user journeys, system
features, and external dependencies. Synthesizes container and component
documentation with system documentation to create comprehensive context-level
diff --git a/skills/carrier-relationship-management/SKILL.md b/skills/carrier-relationship-management/SKILL.md
new file mode 100644
index 00000000..cff92397
--- /dev/null
+++ b/skills/carrier-relationship-management/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: carrier-relationship-management
+description: >
+ Codified expertise for managing carrier portfolios, negotiating freight rates,
+ tracking carrier performance, allocating freight, and maintaining strategic
+ carrier relationships. Informed by transportation managers with 15+ years
+ experience. Includes scorecarding frameworks, RFP processes, market intelligence,
+ and compliance vetting. Use when managing carriers, negotiating rates, evaluating
+ carrier performance, or building freight strategies.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🤝"
+---
+
+## When to Use
+
+Use this skill when building and managing a carrier network, conducting freight RFPs, negotiating linehaul and accessorial rates, tracking carrier KPIs via scorecards, or ensuring regulatory compliance of transportation partners.
+
+# Carrier Relationship Management
+
+## Role and Context
+
+You are a senior transportation manager with 15+ years managing carrier portfolios ranging from 40 to 200+ active carriers across truckload, LTL, intermodal, and brokerage. You own the full lifecycle: sourcing new carriers, negotiating rates, running RFPs, building routing guides, tracking performance via scorecards, managing contract renewals, and making allocation decisions. You sit between procurement (who owns total logistics spend), operations (who tenders daily freight), finance (who pays invoices), and senior leadership (who sets cost and service targets). Your systems include TMS (transportation management), rate management platforms, carrier onboarding portals, DAT/Greenscreens for market intelligence, and FMCSA SAFER for compliance. You balance cost reduction pressure against service quality, capacity security, and carrier relationship health — because when the market tightens, your carriers' willingness to cover your freight depends on how you treated them when capacity was loose.
+
+## Core Knowledge
+
+### Rate Negotiation Fundamentals
+
+Every freight rate has components that must be negotiated independently — bundling them obscures where you're overpaying:
+
+- **Base linehaul rate:** The per-mile or flat rate for dock-to-dock transportation. For truckload, benchmark against DAT or Greenscreens lane rates. For LTL, this is the discount off the carrier's published tariff (typically 70-85% discount for mid-volume shippers). Always negotiate on a lane-by-lane basis — a carrier competitive on Chicago–Dallas may be 15% over market on Atlanta–LA.
+- **Fuel surcharge (FSC):** Percentage or per-mile adder tied to the DOE national average diesel price. Negotiate the FSC table, not just the current rate. Key details: the base price trigger (what diesel price equals 0% FSC), the increment (e.g., $0.01/mile per $0.05 diesel increase), and the index lag (weekly vs. monthly adjustment). A carrier quoting a low linehaul with an aggressive FSC table can be more expensive than a higher linehaul with a standard DOE-indexed FSC.
+- **Accessorial charges:** Detention ($50-$100/hr after 2 hours free time is standard), liftgate ($75-$150), residential delivery ($75-$125), inside delivery ($100+), limited access ($50-$100), appointment scheduling ($0-$50). Negotiate free time for detention aggressively — driver detention is the #1 source of carrier invoice disputes. For LTL, watch for reweigh/reclass fees ($25-$75 per occurrence) and cubic capacity surcharges.
+- **Minimum charges:** Every carrier has a minimum per-shipment charge. For truckload, it's typically a minimum mileage (e.g., $800 for loads under 200 miles). For LTL, it's the minimum charge per shipment ($75-$150) regardless of weight or class. Negotiate minimums on short-haul lanes separately.
+- **Contract vs. spot rates:** Contract rates (awarded through RFP or negotiation, valid 6-12 months) provide cost predictability and capacity commitment. Spot rates (negotiated per load on the open market) are 10-30% higher in tight markets, 5-20% lower in soft markets. A healthy portfolio uses 75-85% contract freight and 15-25% spot. More than 30% spot means your routing guide is failing.
+
+### Carrier Scorecarding
+
+Measure what matters. A scorecard that tracks 20 metrics gets ignored; one that tracks 5 gets acted on:
+
+- **On-time delivery (OTD):** Percentage of shipments delivered within the agreed window. Target: ≥95%. Red flag: <90%. Measure pickup and delivery separately — a carrier with 98% on-time pickup and 88% on-time delivery has a linehaul or terminal problem, not a capacity problem.
+- **Tender acceptance rate:** Percentage of electronically tendered loads accepted by the carrier. Target: ≥90% for primary carriers. Red flag: <80%. A carrier that rejects 25% of tenders is consuming your operations team's time re-tendering and forcing spot market exposure. Tender acceptance below 75% on a contract lane means the rate is below market — renegotiate or reallocate.
+- **Claims ratio:** Dollar value of claims filed divided by total freight spend with the carrier. Target: <0.5% of spend. Red flag: >1.0%. Track claims frequency separately from claims severity — a carrier with one $50K claim is different from one with fifty $1K claims. The latter indicates a systemic handling problem.
+- **Invoice accuracy:** Percentage of invoices matching the contracted rate without manual correction. Target: ≥97%. Red flag: <93%. Chronic overbilling (even small amounts) signals either intentional rate testing or broken billing systems. Either way, it costs you audit labor. Carriers with <90% invoice accuracy should be on corrective action.
+- **Tender-to-pickup time:** Hours between electronic tender acceptance and actual pickup. Target: within 2 hours of requested pickup for FTL. Carriers that accept tenders but consistently pick up late are "soft rejecting" — they accept to hold the load while shopping for better freight.
+
+### Portfolio Strategy
+
+Your carrier portfolio is an investment portfolio — diversification manages risk, concentration drives leverage:
+
+- **Asset carriers vs. brokers:** Asset carriers own trucks. They provide capacity certainty, consistent service, and direct accountability — but they're less flexible on pricing and may not cover all your lanes. Brokers source capacity from thousands of small carriers. They offer pricing flexibility and lane coverage, but introduce counterparty risk (double-brokering, carrier quality variance, payment chain complexity). Target mix: 60-70% asset, 20-30% broker, 5-15% niche/specialty.
+- **Routing guide structure:** Build a 3-deep routing guide for every lane with >2 loads/week. Primary carrier gets first tender (target: 80%+ acceptance). Secondary gets the fallback (target: 70%+ acceptance on overflow). Tertiary is your price ceiling — often a broker whose rate represents the "do not exceed" for spot procurement. For lanes with <2 loads/week, use a 2-deep guide or a regional broker with broad coverage.
+- **Lane density and carrier concentration:** Award enough volume per carrier per lane to matter to them. A carrier running 2 loads/week on your lane will prioritize you over a shipper giving them 2 loads/month. But don't give one carrier more than 40% of any single lane — a carrier exit or service failure on a concentrated lane is catastrophic. For your top 20 lanes by volume, maintain at least 3 active carriers.
+- **Small carrier value:** Carriers with 10-50 trucks often provide better service, more flexible pricing, and stronger relationships than mega-carriers. They answer the phone. Their owner-operators care about your freight. The tradeoff: less technology integration, thinner insurance, and capacity limits during peak. Use small carriers for consistent, mid-volume lanes where relationship quality matters more than surge capacity.
+
+### RFP Process
+
+A well-run freight RFP takes 8-12 weeks and touches every active and prospective carrier:
+
+- **Pre-RFP:** Analyze 12 months of shipment data. Identify lanes by volume, spend, and current service levels. Flag underperforming lanes and lanes where current rates exceed market benchmarks (DAT, Greenscreens, Chainalytics). Set targets: cost reduction percentage, service level minimums, carrier diversity goals.
+- **RFP design:** Include lane-level detail (origin/destination zip, volume range, required equipment, any special handling), current transit time expectations, accessorial requirements, payment terms, insurance minimums, and your evaluation criteria with weightings. Make carriers bid lane-by-lane — portfolio bids ("we'll give you 5% off everything") hide cross-subsidization.
+- **Bid evaluation:** Don't award on price alone. Weight cost at 40-50%, service history at 25-30%, capacity commitment at 15-20%, and operational fit at 10-15%. A carrier 3% above the lowest bid but with 97% OTD and 95% tender acceptance is cheaper than the lowest bidder with 85% OTD and 70% tender acceptance — the service failures cost more than the rate difference.
+- **Award and implementation:** Award in waves — primary carriers first, then secondary. Give carriers 2-3 weeks to operationalize new lanes before you start tendering. Run a 30-day parallel period where old and new routing guides overlap. Cut over cleanly.
+
+### Market Intelligence
+
+Rate cycles are predictable in direction, unpredictable in magnitude:
+
+- **DAT and Greenscreens:** DAT RateView provides lane-level spot and contract rate benchmarks based on broker-reported transactions. Greenscreens provides carrier-specific pricing intelligence and predictive analytics. Use both — DAT for market direction, Greenscreens for carrier-specific negotiation leverage. Neither is perfectly accurate, but both are better than negotiating blind.
+- **Freight market cycles:** The truckload market oscillates between shipper-favorable (excess capacity, falling rates, high tender acceptance) and carrier-favorable (tight capacity, rising rates, tender rejections). Cycles last 18-36 months peak-to-peak. Key indicators: DAT load-to-truck ratio (>6:1 signals tight market), OTRI (Outbound Tender Rejection Index — >10% signals carrier leverage shifting), Class 8 truck orders (leading indicator of capacity addition 6-12 months out).
+- **Seasonal patterns:** Produce season (April-July) tightens reefer capacity in the Southeast and West. Peak retail season (October-January) tightens dry van capacity nationally. The last week of each month and quarter sees volume spikes as shippers meet revenue targets. Budget RFP timing to avoid awarding contracts at the peak or trough of a cycle — award during the transition for more realistic rates.
+
+### FMCSA Compliance Vetting
+
+Every carrier in your portfolio must pass compliance screening before their first load and on a recurring quarterly basis:
+
+- **Operating authority:** Verify active MC (Motor Carrier) or FF (Freight Forwarder) authority via FMCSA SAFER. An "authorized" status that hasn't been updated in 12+ months may indicate a carrier that's technically authorized but operationally inactive. Check the "authorized for" field — a carrier authorized for "property" cannot legally carry household goods.
+- **Insurance minimums:** $750K minimum for general freight (per FMCSA §387.9), $1M for hazmat, $5M for household goods. Require $1M minimum from all carriers regardless of commodity — the FMCSA minimum of $750K doesn't cover a serious accident. Verify insurance through the FMCSA Insurance tab, not just the certificate the carrier provides — certificates can be forged or outdated.
+- **Safety rating:** FMCSA assigns Satisfactory, Conditional, or Unsatisfactory ratings based on compliance reviews. Never use a carrier with an Unsatisfactory rating. Conditional carriers require case-by-case evaluation — understand what the conditions are. Carriers with no rating ("unrated") make up the majority — use their CSA (Compliance, Safety, Accountability) scores instead. Focus on Unsafe Driving, Hours-of-Service, and Vehicle Maintenance BASICs. A carrier in the top 25% percentile (worst) on Unsafe Driving is a liability risk.
+- **Broker bond verification:** If using brokers, verify their $75K surety bond or trust fund is active. A broker whose bond has been revoked or reduced is likely in financial distress. Check the FMCSA Bond/Trust tab. Also verify the broker has contingent cargo insurance — this protects you if the broker's underlying carrier causes a loss and the carrier's insurance is insufficient.
+
+## Decision Frameworks
+
+### Carrier Selection for New Lanes
+
+When adding a new lane to your network, evaluate candidates on this decision tree:
+
+1. **Do existing portfolio carriers cover this lane?** If yes, negotiate with incumbents first — adding a new carrier for one lane introduces onboarding cost ($500-$1,500) and relationship management overhead. Offer existing carriers the new lane as incremental volume in exchange for a rate concession on an existing lane.
+2. **If no incumbent covers the lane:** Source 3-5 candidates. For lanes >500 miles, prioritize asset carriers with domicile within 100 miles of the origin. For lanes <300 miles, consider regional carriers and dedicated fleets. For infrequent lanes (<1 load/week), a broker with strong regional coverage may be the most practical option.
+3. **Evaluate:** Run FMCSA compliance check. Request 12-month service history on the specific lane from each candidate (not just their network average). Check DAT lane rates for market benchmark. Compare total cost (linehaul + FSC + expected accessorials), not just linehaul.
+4. **Trial period:** Award 30-day trial at contracted rates. Set clear KPIs: OTD ≥93%, tender acceptance ≥85%, invoice accuracy ≥95%. Review at 30 days — do not lock in a 12-month commitment without operational validation.
+
+### When to Consolidate vs. Diversify
+
+- **Consolidate (reduce carrier count) when:** You have more than 3 carriers on a lane with <5 loads/week (each carrier gets too little volume to care). Your carrier management resources are stretched. You need deeper pricing from a strategic partner (volume concentration = leverage). The market is loose and carriers are competing for your freight.
+- **Diversify (add carriers) when:** A single carrier handles >40% of a critical lane. Tender rejections are rising above 15% on a lane. You're entering peak season and need surge capacity. A carrier shows financial distress indicators (late payments to drivers reported on Carrier411, FMCSA insurance lapses, sudden driver turnover visible via CDL postings).
+
+### Spot vs. Contract Decisions
+
+- **Stay on contract when:** The spread between contract and spot is <10%. You have consistent, predictable volume. Capacity is tightening (spot rates are rising). The lane is customer-critical with tight delivery windows.
+- **Go to spot when:** Spot rates are >15% below your contract rate (market is soft). The lane is irregular (<1 load/week). You need one-time surge capacity beyond your routing guide. Your contract carrier is consistently rejecting tenders on this lane (they're effectively pricing you into spot anyway).
+- **Renegotiate contract when:** The spread between your contract rate and DAT benchmark exceeds 15% for 60+ consecutive days. A carrier's tender acceptance drops below 75% for 30 days. You've had a significant volume change (up or down) that changes the lane economics.
+
+### Carrier Exit Criteria
+
+Remove a carrier from your active routing guide when any of these thresholds are met, after documented corrective action has failed:
+
+- OTD below 85% for 60 consecutive days
+- Tender acceptance below 70% for 30 consecutive days with no communication
+- Claims ratio exceeds 2% of spend for 90 days
+- FMCSA authority revoked, insurance lapsed, or safety rating downgraded to Unsatisfactory
+- Invoice accuracy below 88% for 90 days after corrective notice
+- Discovery of double-brokering your freight
+- Evidence of financial distress: bond revocation, driver complaints on CarrierOK or Carrier411, unexplained service collapse
+
+## Key Edge Cases
+
+These are situations where standard playbook decisions lead to poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Capacity squeeze during a hurricane:** Your top carrier evacuates drivers from the Gulf Coast. Spot rates triple. The temptation is to pay any rate to move freight. The expert move: activate pre-positioned regional carriers, reroute through unaffected corridors, and negotiate multi-load commitments with spot carriers to lock a rate ceiling.
+
+2. **Double-brokering discovery:** You're told the truck that arrived isn't from the carrier on your BOL. The insurance chain may be broken and your freight is at higher risk. Do not accept the load if it hasn't departed. If in transit, document everything and demand a written explanation within 24 hours.
+
+3. **Rate renegotiation after 40% volume loss:** Your company lost a major customer and your freight volume dropped. Your carriers' contract rates were predicated on volume commitments you can no longer meet. Proactive renegotiation preserves relationships; letting carriers discover the shortfall at invoice time destroys trust.
+
+4. **Carrier financial distress indicators:** The warning signs appear months before a carrier fails: delayed driver settlements, FMCSA insurance filings changing underwriters frequently, bond amount dropping, Carrier411 complaints spiking. Reduce exposure incrementally — don't wait for the failure.
+
+5. **Mega-carrier acquisition of your niche partner:** Your best regional carrier just got acquired by a national fleet. Expect service disruption during integration, rate renegotiation attempts, and potential loss of your dedicated account manager. Secure alternative capacity before the transition completes.
+
+6. **Fuel surcharge manipulation:** A carrier proposes an artificially low base rate with an aggressive FSC schedule that inflates the total cost above market. Always model total cost across a range of diesel prices ($3.50, $4.00, $4.50/gal) to expose this tactic.
+
+7. **Detention and accessorial disputes at scale:** When detention charges represent >5% of a carrier's total billing, the root cause is usually shipper facility operations, not carrier overcharging. Address the operational issue before disputing the charges — or lose the carrier.
+
+## Communication Patterns
+
+### Rate Negotiation Tone
+
+Rate negotiations are long-term relationship conversations, not one-time transactions. Calibrate tone:
+
+- **Opening position:** Lead with data, not demands. "DAT shows this lane averaging $2.15/mile over the last 90 days. Our current contract is $2.45. We'd like to discuss alignment." Never say "your rate is too high" — say "the market has shifted and we want to make sure we're in a competitive position together."
+- **Counter-offers:** Acknowledge the carrier's perspective. "We understand driver pay increases are real. Let's find a number that keeps this lane attractive for your drivers while keeping us competitive." Meet in the middle on base rate, negotiate harder on accessorials and FSC table.
+- **Annual reviews:** Frame as partnership check-ins, not cost-cutting exercises. Share your volume forecast, growth plans, and lane changes. Ask what you can do operationally to help the carrier (faster dock times, consistent scheduling, drop-trailer programs). Carriers give better rates to shippers who make their drivers' lives easier.
+
+### Performance Reviews
+
+- **Positive reviews:** Be specific. "Your 97% OTD on the Chicago–Dallas lane saved us approximately $45K in expedite costs this quarter. We're increasing your allocation from 60% to 75% on that lane." Carriers invest in relationships that reward performance.
+- **Corrective reviews:** Lead with data, not accusations. Present the scorecard. Identify the specific metrics below threshold. Ask for a corrective action plan with a 30/60/90-day timeline. Set a clear consequence: "If OTD on this lane doesn't reach 92% by the 60-day mark, we'll need to shift 50% of volume to an alternate carrier."
+
+For full communication templates, see [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------------------------- | ------------------------------------------------ | --------------- |
+| Carrier tender acceptance drops below 70% for 2 consecutive weeks | Notify procurement, schedule carrier call | Within 48 hours |
+| Spot spend exceeds 30% of lane budget for any lane | Review routing guide, initiate carrier sourcing | Within 1 week |
+| Carrier FMCSA authority or insurance lapses | Immediately suspend tendering, notify operations | Within 1 hour |
+| Single carrier controls >50% of a critical lane | Initiate secondary carrier qualification | Within 2 weeks |
+| Claims ratio exceeds 1.5% for any carrier for 60+ days | Schedule formal performance review | Within 1 week |
+| Rate variance >20% from DAT benchmark on 5+ lanes | Initiate contract renegotiation or mini-bid | Within 2 weeks |
+| Carrier reports driver shortage or service disruption | Activate backup carriers, increase monitoring | Within 4 hours |
+| Double-brokering confirmed on any load | Immediate carrier suspension, compliance review | Within 2 hours |
+
+### Escalation Chain
+
+Analyst → Transportation Manager (48 hours) → Director of Transportation (1 week) → VP Supply Chain (persistent issue or >$100K exposure)
+
+## Performance Indicators
+
+Track weekly, review monthly with carrier management team, share quarterly with carriers:
+
+| Metric | Target | Red Flag |
+| ------------------------------------------------ | -------------- | ------------------------ |
+| Contract rate vs. DAT benchmark | Within ±8% | >15% premium or discount |
+| Routing guide compliance (% of freight on guide) | ≥85% | <70% |
+| Primary tender acceptance | ≥90% | <80% |
+| Weighted average OTD across portfolio | ≥95% | <90% |
+| Carrier portfolio claims ratio | <0.5% of spend | >1.0% |
+| Average carrier invoice accuracy | ≥97% | <93% |
+| Spot freight percentage | <20% | >30% |
+| RFP cycle time (launch to implementation) | ≤12 weeks | >16 weeks |
+
+## Additional Resources
+
+- For detailed decision frameworks on rate negotiation, portfolio optimization, and RFP execution, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you are **designing or tuning your carrier portfolio, routing guides, and freight procurement strategy**:
+
+- Running freight RFPs, renegotiating contract and fuel tables, or balancing spot vs. contract exposure.
+- Building carrier scorecards, exit criteria, and escalation protocols to manage performance and risk.
+- Deciding how to allocate lanes across asset carriers, brokers, and regional specialists to protect service while controlling logistics spend.
diff --git a/skills/carrier-relationship-management/references/communication-templates.md b/skills/carrier-relationship-management/references/communication-templates.md
new file mode 100644
index 00000000..053b981a
--- /dev/null
+++ b/skills/carrier-relationship-management/references/communication-templates.md
@@ -0,0 +1,584 @@
+# Communication Templates — Carrier Relationship Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing carrier communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by communication type and business context. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RFP Invitation Letter](#1-rfp-invitation-letter)
+2. [Rate Negotiation Opening](#2-rate-negotiation-opening)
+3. [Rate Counter-Offer](#3-rate-counter-offer)
+4. [Carrier Performance Review — Positive](#4-carrier-performance-review--positive)
+5. [Carrier Performance Review — Corrective](#5-carrier-performance-review--corrective)
+6. [Carrier Onboarding Welcome](#6-carrier-onboarding-welcome)
+7. [Carrier Warning Letter](#7-carrier-warning-letter)
+8. [Carrier Exit Notification](#8-carrier-exit-notification)
+9. [Market Rate Discussion](#9-market-rate-discussion)
+10. [Partnership Proposal](#10-partnership-proposal)
+11. [Detention Dispute Communication](#11-detention-dispute-communication)
+12. [Accessorial Challenge](#12-accessorial-challenge)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{carrier_name}}` | Carrier legal or DBA name | `Ridgeline Transport, Inc.` |
+| `{{carrier_contact}}` | Carrier contact name | `Mike Patterson` |
+| `{{carrier_contact_title}}` | Carrier contact title | `VP of Sales` |
+| `{{carrier_mc}}` | Carrier MC number | `MC-498132` |
+| `{{our_company}}` | Our company name | `Consolidated Manufacturing LLC` |
+| `{{our_contact_name}}` | Our representative name | `Sarah Chen` |
+| `{{our_contact_title}}` | Our representative title | `Director of Transportation` |
+| `{{our_contact_email}}` | Our representative email | `schen@company.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(312) 555-0189` |
+| `{{lane_origin}}` | Lane origin city/state | `Chicago, IL` |
+| `{{lane_destination}}` | Lane destination city/state | `Dallas, TX` |
+| `{{current_rate}}` | Current contract rate per mile | `$2.45/mile` |
+| `{{proposed_rate}}` | Proposed new rate | `$2.28/mile` |
+| `{{market_rate}}` | DAT/benchmark market rate | `$2.18/mile` |
+| `{{volume_loads_week}}` | Weekly load volume | `8 loads/week` |
+| `{{annual_spend}}` | Annual freight spend with carrier | `$2.4M` |
+| `{{contract_start}}` | Contract effective date | `2026-04-01` |
+| `{{contract_end}}` | Contract expiration date | `2027-03-31` |
+| `{{rfp_deadline}}` | RFP response deadline | `2026-03-15` |
+| `{{otd_percentage}}` | Carrier's on-time delivery rate | `96.2%` |
+| `{{tender_acceptance}}` | Carrier's tender acceptance rate | `91.4%` |
+| `{{claims_ratio}}` | Carrier's claims ratio | `0.3%` |
+| `{{invoice_accuracy}}` | Carrier's invoice accuracy rate | `97.8%` |
+| `{{review_period}}` | Performance review time period | `Q3 2025 (Jul-Sep)` |
+| `{{detention_amount}}` | Disputed detention charge amount | `$4,275` |
+| `{{accessorial_type}}` | Specific accessorial charge type | `liftgate delivery` |
+
+---
+
+## 1. RFP Invitation Letter
+
+**Channel:** Email
+**Audience:** Carrier sales / pricing leadership
+**Tone:** Professional, opportunity-oriented. You're inviting them to compete for business, not demanding concessions.
+
+---
+
+**Subject:** `Invitation to Bid — {{our_company}} Freight RFP — {{contract_start}} Award`
+
+{{carrier_contact}},
+
+{{our_company}} is conducting our annual freight RFP process and we're inviting {{carrier_name}} to participate as a bidding carrier. Based on our analysis of market capabilities and your operational profile, we believe there may be strong alignment between your network and our shipping requirements.
+
+**RFP Overview:**
+- **Scope:** {{lane_count}} lanes across TL, LTL, and intermodal modes
+- **Total annual freight spend:** Approximately {{total_annual_spend}}
+- **Contract period:** {{contract_start}} through {{contract_end}}
+- **Bid deadline:** {{rfp_deadline}} at 5:00 PM CT
+
+**What We're Looking For:**
+We evaluate bids on a weighted scorecard: rate competitiveness (40%), service history and reliability (25%), capacity commitment (20%), and operational fit including technology integration (15%). We value carriers who bring consistent service and a commitment to partnership over the lowest possible rate.
+
+**Enclosed with this letter:**
+1. Lane-level bid package with volume ranges, equipment requirements, and transit expectations
+2. Accessorial schedule with standard rates and negotiable items
+3. Insurance and compliance requirements
+4. Service-level expectations (OTD, tender acceptance, claims thresholds)
+5. Contract terms summary
+
+**Next Steps:**
+Please confirm your intent to bid by {{rfp_confirm_date}}. A Q&A webinar for all participating carriers is scheduled for {{qa_date}} at {{qa_time}} CT. All questions must be submitted in writing through the RFP portal; responses will be shared with all bidders.
+
+We look forward to your participation.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 2. Rate Negotiation Opening
+
+**Channel:** Email followed by phone call
+**Audience:** Carrier account manager or VP of Sales
+**Tone:** Data-driven, collaborative. Lead with market data, not demands. Frame as aligning rates with market reality, not squeezing the carrier.
+
+---
+
+**Subject:** `Rate Review Discussion — {{lane_origin}} to {{lane_destination}} | {{our_company}}`
+
+{{carrier_contact}},
+
+I'd like to schedule a call to discuss rate alignment on our {{lane_origin}} to {{lane_destination}} lane. As part of our quarterly rate benchmarking process, we've identified an opportunity to ensure our pricing on this lane reflects current market conditions.
+
+**Our Current Situation:**
+- **Current contract rate:** {{current_rate}} (effective since {{contract_start}})
+- **DAT 90-day contract average for this lane:** {{market_rate}}
+- **Your current volume on this lane:** {{volume_loads_week}}
+- **Your performance:** {{otd_percentage}} OTD, {{tender_acceptance}} tender acceptance
+
+We recognize that {{carrier_name}} has delivered strong service on this lane, and our goal is to find a rate that keeps this lane attractive for both of us. We're not looking to drive rates to a level that compromises your service or driver compensation — we are looking for alignment with where the market has moved.
+
+Could you check availability for a 30-minute call this week? I'd like to walk through the data together and explore options.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Rate Counter-Offer
+
+**Channel:** Email
+**Audience:** Carrier account manager or pricing team
+**Tone:** Firm but respectful. Acknowledge the carrier's position while advancing yours. Always justify with data.
+
+---
+
+**Subject:** `Re: Rate Proposal — {{lane_origin}} to {{lane_destination}}`
+
+{{carrier_contact}},
+
+Thank you for the rate proposal on our {{lane_origin}} to {{lane_destination}} lane. I appreciate the detail and the time your team invested.
+
+After reviewing your proposal against our market data and total cost model, I'd like to share our counter-position:
+
+**Your Proposal:** {{carrier_proposed_rate}}
+**Our Counter:** {{our_counter_rate}}
+
+**Rationale:**
+- DAT 90-day contract average for this lane is {{market_rate}}, which puts your proposal {{percentage_above_market}}% above the current market benchmark.
+- We modeled total cost including your proposed fuel surcharge schedule at diesel prices of $3.25, $3.85, and $4.50/gal. At current diesel ({{current_diesel}}), your total cost per mile is {{total_cost_per_mile}}, which is {{total_cost_vs_market}}% above our benchmark total cost.
+- Our counter rate of {{our_counter_rate}} reflects the market benchmark plus a {{premium_percentage}}% premium for your service quality — which we genuinely value. Your {{otd_percentage}} OTD is among the best in our portfolio.
+
+**What We're Offering in Return:**
+- Volume commitment: {{volume_commitment}} loads/week guaranteed (vs. your current {{current_volume}} loads/week)
+- Payment terms: Net {{payment_days}} (vs. our standard Net 30)
+- Drop-trailer program at our {{facility_name}} facility (eliminating an average of {{detention_hours}} hours detention per load)
+
+I believe we can find alignment here. Would a call on {{proposed_call_date}} work to discuss?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 4. Carrier Performance Review — Positive
+
+**Channel:** Email + formal quarterly business review meeting
+**Audience:** Carrier account manager, VP of Sales, and operations leadership
+**Tone:** Celebratory and specific. Name the metrics, quantify the impact, and reward with tangible actions (more volume, longer contract, public recognition). Generic praise is worse than no praise.
+
+---
+
+**Subject:** `Q{{quarter}} Performance Review — {{carrier_name}} | Outstanding Results`
+
+{{carrier_contact}},
+
+I want to formally recognize {{carrier_name}}'s performance during {{review_period}}. Your team has been exceptional across every metric we track, and we want to make sure you know it — and that we're backing up that recognition with action.
+
+**Performance Summary — {{review_period}}:**
+
+| Metric | Target | Your Performance | Portfolio Average |
+|--------|--------|-----------------|-------------------|
+| On-Time Delivery | ≥95% | {{otd_percentage}} | {{portfolio_avg_otd}} |
+| Tender Acceptance | ≥90% | {{tender_acceptance}} | {{portfolio_avg_tender}} |
+| Claims Ratio | <0.5% | {{claims_ratio}} | {{portfolio_avg_claims}} |
+| Invoice Accuracy | ≥97% | {{invoice_accuracy}} | {{portfolio_avg_invoice}} |
+
+**Specific Highlights:**
+- Your team's performance on the {{highlight_lane}} lane was particularly strong — {{highlight_detail}}.
+- Driver {{driver_name}} received compliments from our {{facility_name}} receiving team for consistent professionalism and efficient dock operations.
+- Your operations team's proactive communication during {{event}} prevented what could have been a significant service disruption.
+
+**What This Means for Our Partnership:**
+Based on this performance, we're making the following allocation changes effective {{effective_date}}:
+- **{{lane_1}}:** Increasing your allocation from {{old_allocation_1}}% to {{new_allocation_1}}%
+- **{{lane_2}}:** Adding you as primary carrier (new lane award — {{volume_2}} loads/week)
+- **Contract extension:** We'd like to discuss extending our agreement through {{extended_end_date}} at current terms
+
+Thank you for making our operation better. We value this partnership and look forward to continuing to grow together.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Carrier Performance Review — Corrective
+
+**Channel:** Email followed by in-person or video meeting
+**Audience:** Carrier account manager and operations leadership
+**Tone:** Professional, direct, data-driven. Not punitive — corrective. Present the data, state the impact, set clear expectations with a timeline, and define the consequence. Avoid emotional language.
+
+---
+
+**Subject:** `Performance Review — {{carrier_name}} | Corrective Action Required`
+
+{{carrier_contact}},
+
+I'm reaching out regarding {{carrier_name}}'s performance during {{review_period}} on lanes serviced for {{our_company}}. Several metrics have fallen below our minimum standards, and I want to address this directly so we can work together on a resolution.
+
+**Performance Summary — {{review_period}}:**
+
+| Metric | Our Standard | Your Performance | Gap |
+|--------|-------------|-----------------|-----|
+| On-Time Delivery | ≥95% | {{otd_percentage}} | {{otd_gap}} below standard |
+| Tender Acceptance | ≥90% | {{tender_acceptance}} | {{tender_gap}} below standard |
+| Claims Ratio | <0.5% | {{claims_ratio}} | {{claims_gap}} above standard |
+| Invoice Accuracy | ≥97% | {{invoice_accuracy}} | {{invoice_gap}} below standard |
+
+**Business Impact:**
+- Tender rejections on the {{problem_lane}} lane forced {{spot_loads}} loads to the spot market at an average premium of {{spot_premium}}%, costing us approximately ${{incremental_cost}} in incremental freight spend.
+- Late deliveries resulted in {{penalty_count}} customer penalty events totaling ${{penalty_total}}.
+
+**What We Need:**
+We value our relationship with {{carrier_name}} and want to find a path forward. We're requesting a Corrective Action Plan that addresses the following within the timelines indicated:
+
+| Metric | Target | 30-Day Checkpoint | 60-Day Checkpoint |
+|--------|--------|-------------------|-------------------|
+| OTD | ≥{{otd_target}}% | ≥{{otd_30day}}% | ≥{{otd_60day}}% |
+| Tender Acceptance | ≥{{tender_target}}% | ≥{{tender_30day}}% | ≥{{tender_60day}}% |
+
+Please send your CAP document by {{cap_due_date}} outlining the root causes you've identified and the specific operational changes you're implementing.
+
+**If Targets Are Not Met:**
+If the 60-day checkpoint targets are not achieved, we will need to reduce your allocation on affected lanes by 50% and reassign volume to alternate carriers. This is not our preferred outcome — we'd much rather see improvement and continue building this partnership.
+
+I'd like to schedule a call for {{proposed_call_date}} to discuss your initial assessment. Please let me know your availability.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 6. Carrier Onboarding Welcome
+
+**Channel:** Email
+**Audience:** Carrier's assigned account manager and operations contact
+**Tone:** Welcoming, organized, and clear about expectations. First impressions set the relationship trajectory.
+
+---
+
+**Subject:** `Welcome to {{our_company}}'s Carrier Network — Onboarding Information`
+
+{{carrier_contact}},
+
+Welcome to {{our_company}}'s carrier network. We're pleased to have {{carrier_name}} as a transportation partner and look forward to a productive relationship.
+
+This email contains everything you need to get started. Please review carefully and let me know if you have questions.
+
+**Your Awarded Lanes:**
+
+| Lane | Volume | Equipment | Transit Requirement |
+|------|--------|-----------|-------------------|
+| {{lane_1_origin}} → {{lane_1_dest}} | {{lane_1_volume}}/week | {{lane_1_equip}} | {{lane_1_transit}} |
+| {{lane_2_origin}} → {{lane_2_dest}} | {{lane_2_volume}}/week | {{lane_2_equip}} | {{lane_2_transit}} |
+
+**Onboarding Checklist (please complete by {{onboarding_deadline}}):**
+
+- [ ] Return signed Carrier Transportation Agreement (attached)
+- [ ] Provide current Certificate of Insurance meeting our minimums ($1M auto liability, $100K cargo)
+- [ ] Complete W-9 form (attached)
+- [ ] Provide EDI/API contact for system integration setup (if applicable)
+- [ ] Confirm operational contact for daily dispatching (name, phone, email)
+- [ ] Confirm after-hours emergency contact (name, phone)
+
+**What to Expect:**
+- **First 30 days:** We'll run trial loads on your awarded lanes. Our minimum standards during trial: ≥93% OTD, ≥85% tender acceptance, ≥95% invoice accuracy.
+- **Day 30 review:** We'll review trial performance together. If targets are met, you'll move to full allocation. If not, we'll discuss what adjustments are needed.
+- **Ongoing:** Quarterly performance reviews, annual rate review aligned with our RFP cycle.
+
+**Our Facilities — Key Operational Notes:**
+
+| Facility | Dock Hours | Appointment Required? | Avg Load/Unload Time | Detention Policy |
+|----------|-----------|----------------------|---------------------|-----------------|
+| {{facility_1}} | {{hours_1}} | {{appt_1}} | {{avg_time_1}} | {{detention_1}} |
+| {{facility_2}} | {{hours_2}} | {{appt_2}} | {{avg_time_2}} | {{detention_2}} |
+
+**Your Primary Contacts at {{our_company}}:**
+- **Relationship management:** {{our_contact_name}}, {{our_contact_title}} ({{our_contact_email}}, {{our_contact_phone}})
+- **Daily operations / tendering:** {{ops_contact_name}}, {{ops_contact_title}} ({{ops_contact_email}}, {{ops_contact_phone}})
+- **Accounts payable / invoicing:** {{ap_contact_name}} ({{ap_contact_email}})
+
+Welcome aboard. We believe in rewarding performance — carriers who deliver consistent, high-quality service earn more volume, longer contracts, and priority consideration for new lanes.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+
+---
+
+## 7. Carrier Warning Letter
+
+**Channel:** Formal email with read receipt requested; copy to carrier's VP of Sales
+**Audience:** Carrier account manager + carrier senior leadership
+**Tone:** Formal and serious. This is a documentation event as much as a communication — it creates the paper trail for a potential exit decision. Factual, not emotional. Cite specific contract provisions.
+
+---
+
+**Subject:** `FORMAL NOTICE: Performance Deficiency — {{carrier_name}} / {{our_company}} Account`
+
+{{carrier_contact}},
+
+This letter serves as formal notice that {{carrier_name}}'s performance on {{our_company}}'s account has fallen below contractual standards for a sustained period, and continued non-compliance will result in volume reduction and potential removal from our routing guide.
+
+**Deficiency Summary:**
+Per Section {{contract_section}} of our Transportation Agreement dated {{agreement_date}}, the following minimum standards apply:
+
+| Metric | Contractual Minimum | {{carrier_name}}'s Performance ({{deficiency_period}}) |
+|--------|--------------------|----------------------------------------------------|
+| {{metric_1}} | {{standard_1}} | {{actual_1}} |
+| {{metric_2}} | {{standard_2}} | {{actual_2}} |
+
+**Prior Communication:**
+- {{prior_comm_date_1}}: {{prior_comm_description_1}}
+- {{prior_comm_date_2}}: {{prior_comm_description_2}}
+- {{cap_date}}: Corrective Action Plan submitted, targeting improvement by {{cap_target_date}}
+- As of {{current_date}}, targets have not been met.
+
+**Consequences:**
+Effective {{consequence_date}}, we will reduce {{carrier_name}}'s allocation on the following lanes by {{reduction_percentage}}%:
+{{affected_lanes_list}}
+
+If performance does not reach contractual minimums by {{final_deadline}}, {{carrier_name}} will be removed from our active routing guide on all affected lanes.
+
+**Path to Resolution:**
+We would prefer to resolve this cooperatively. If {{carrier_name}} can provide an updated remediation plan addressing the specific root causes and committing to measurable improvement targets, we are willing to extend the review period by 30 days.
+
+Please respond in writing by {{response_deadline}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+CC: {{carrier_vp_name}}, {{carrier_vp_title}}, {{carrier_name}}
+CC: {{our_director_name}}, {{our_director_title}}, {{our_company}}
+
+---
+
+## 8. Carrier Exit Notification
+
+**Channel:** Formal email followed by phone call
+**Audience:** Carrier account manager and carrier senior leadership
+**Tone:** Respectful and final. This is a business decision, not a punishment. Leave the door open for future consideration. Avoid burning bridges — the carrier community is smaller than you think.
+
+---
+
+**Subject:** `Notice of Routing Guide Removal — {{carrier_name}} / {{our_company}}`
+
+{{carrier_contact}},
+
+After careful consideration and review of {{carrier_name}}'s performance over the past {{review_months}} months, we have made the decision to remove {{carrier_name}} from {{our_company}}'s active routing guide effective {{exit_date}}.
+
+**Reason for Decision:**
+{{exit_reason_summary}}
+
+**Transition Plan:**
+- **{{exit_date}} through {{transition_end_date}}:** We will reduce tender volume by approximately {{reduction_percent}}% per week during this transition period to allow both organizations to adjust.
+- **Open invoices:** All outstanding invoices will be processed per standard payment terms. Please ensure all invoices are submitted by {{invoice_deadline}}.
+- **Open claims:** Any pending claims will continue through their normal resolution process. This decision does not affect the adjudication of open claims.
+
+**What This Means Going Forward:**
+This is not necessarily a permanent decision. We review our carrier portfolio annually during our RFP process. If {{carrier_name}} addresses the issues noted above and would like to re-engage, we welcome your participation in future RFP cycles.
+
+I'm available to discuss this decision directly if you'd like to connect. I respect the work your team has done for our account and want to ensure this transition is handled professionally.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 9. Market Rate Discussion
+
+**Channel:** Email or phone, depending on relationship depth
+**Audience:** Carrier account manager
+**Tone:** Collegial and transparent. This is a market discussion, not a negotiation — you're sharing data and inviting dialogue. Use when market conditions have shifted and you want to proactively discuss alignment before it becomes a formal renegotiation.
+
+---
+
+**Subject:** `Market Check-In — {{lane_origin}} to {{lane_destination}} Corridor`
+
+{{carrier_contact}},
+
+I wanted to reach out proactively about what we're seeing in the {{lane_origin}} to {{lane_destination}} market. As you know, we track lane-level benchmarks quarterly, and the latest data suggests some movement worth discussing.
+
+**What We're Seeing:**
+- DAT contract average for this lane has moved from {{old_benchmark}} to {{new_benchmark}} over the last {{timeframe}} — a {{percentage_change}} {{direction}} shift.
+- Our spot procurement on overflow loads in this corridor has averaged {{spot_average}} over the last 30 days.
+- Load-to-truck ratios in the {{region}} region are currently {{ltt_ratio}}, compared to {{ltt_previous}} last quarter.
+
+**Our Perspective:**
+We're not sending this as a formal rate request — it's a market conversation. We want to understand how you're seeing the same data and whether there's an opportunity to align proactively rather than waiting for contract renewal.
+
+If the market has moved in a way that affects our lane economics, I'd rather discuss it now and find a mutually workable solution than have it surface as a surprise during our annual review.
+
+Would you have 20 minutes this week to discuss?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 10. Partnership Proposal
+
+**Channel:** Formal letter or meeting presentation
+**Audience:** Carrier CEO, President, or SVP of Sales
+**Tone:** Strategic and forward-looking. This is a business partnership proposal, not a procurement transaction. Emphasize mutual benefit, growth potential, and commitment.
+
+---
+
+**Subject:** `Strategic Partnership Proposal — {{our_company}} and {{carrier_name}}`
+
+{{carrier_contact}},
+
+I'd like to propose elevating the relationship between {{our_company}} and {{carrier_name}} from a standard carrier-shipper arrangement to a strategic partnership. Our analysis suggests significant mutual benefit in a deeper, more integrated collaboration.
+
+**Why {{carrier_name}}:**
+Over the past {{relationship_years}} years, {{carrier_name}} has consistently performed in the top tier of our carrier portfolio. Specifically:
+- {{otd_percentage}} OTD (vs. portfolio average of {{portfolio_avg}}%)
+- {{tender_acceptance}} tender acceptance (vs. {{portfolio_avg_tender}}% average)
+- Exceptional communication and problem-resolution responsiveness
+
+**What We're Proposing:**
+1. **Volume commitment:** Increase {{carrier_name}}'s share of our total freight from {{current_share}}% to {{proposed_share}}%, representing approximately {{proposed_spend}} in annual freight spend.
+2. **Multi-year agreement:** 24-month contract with pre-agreed annual escalators tied to {{escalator_index}}, replacing the annual RFP cycle for your lanes.
+3. **Operational integration:** Implement real-time tracking integration (API), shared KPI dashboard, and quarterly executive business reviews.
+4. **Growth collaboration:** As {{our_company}} expands into {{growth_markets}}, {{carrier_name}} would be our first-call carrier for new lanes in your network.
+
+**What We'd Need in Return:**
+1. Rate alignment: Competitive pricing reflecting the volume commitment and multi-year certainty (we're targeting rates within {{target_range}}% of DAT contract benchmark).
+2. Service guarantee: {{otd_target}}% OTD and {{tender_target}}% tender acceptance with quarterly review.
+3. Dedicated account management: A named contact who knows our operations, our customers, and our seasonal patterns.
+4. Capacity priority: During peak season or disruption events, {{our_company}} freight receives priority dispatch from your operations team.
+
+I'd welcome the opportunity to discuss this in a meeting with your leadership team. Would {{proposed_meeting_date}} work for an in-person session at {{proposed_location}}?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 11. Detention Dispute Communication
+
+**Channel:** Email with supporting documentation attached
+**Audience:** Carrier billing / accounts receivable team, cc carrier account manager
+**Tone:** Factual and cooperative. Detention disputes get adversarial quickly — lead with data and a willingness to pay what's legitimate while disputing what's not.
+
+---
+
+**Subject:** `Detention Invoice Dispute — PRO# {{pro_number}} / {{dispute_date}}`
+
+{{carrier_contact}},
+
+We've reviewed the detention invoice for PRO# {{pro_number}} ({{lane_origin}} to {{lane_destination}}, delivered {{delivery_date}}) and have identified discrepancies between the invoiced detention and our facility records.
+
+**Your Invoice:**
+- Driver arrival: {{carrier_arrival_time}}
+- Departure: {{carrier_departure_time}}
+- Total detention billed: {{billed_detention_hours}} hours at ${{detention_rate}}/hr = {{detention_amount}}
+
+**Our Records:**
+- Driver check-in at guard shack: {{our_checkin_time}}
+- Dock door assigned: {{dock_assign_time}}
+- Loading/unloading complete (BOL signed): {{bol_sign_time}}
+- Free time: {{free_time_hours}} hours per contract Section {{contract_section}}
+
+**Discrepancy Analysis:**
+- The driver arrived {{early_minutes}} minutes before the scheduled appointment of {{appointment_time}}. Per our contract, detention begins at the later of appointment time or arrival time — not early arrival time.
+- Our records show actual dock dwell time (from check-in to BOL signature) of {{actual_dwell}} hours, of which {{free_time_hours}} hours is free time. Billable detention per our records: {{adjusted_detention}} hours.
+
+**Our Proposed Resolution:**
+We'll pay {{adjusted_amount}} ({{adjusted_detention}} hours × ${{detention_rate}}/hr) against this invoice. If you believe our records are inaccurate, please provide driver GPS or ELD data showing dock arrival and departure times, and we'll reconcile.
+
+We want to get this right for both of us. If detention on this lane is a recurring issue, I'd welcome a discussion about adjusting appointment scheduling or implementing a drop-trailer program to address the root cause.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 12. Accessorial Challenge
+
+**Channel:** Email
+**Audience:** Carrier billing / pricing team, cc carrier account manager
+**Tone:** Measured and evidence-based. Accessorial disputes are high-volume, low-dollar events that can poison a relationship if handled aggressively. Focus on accuracy, not accusation.
+
+---
+
+**Subject:** `Accessorial Charge Review — {{accessorial_type}} | PRO# {{pro_number}}`
+
+{{carrier_contact}},
+
+We're reviewing an accessorial charge on PRO# {{pro_number}} ({{lane_origin}} to {{lane_destination}}, {{delivery_date}}) and need clarification before processing payment.
+
+**Charge in Question:**
+- Accessorial type: {{accessorial_type}}
+- Amount: ${{accessorial_amount}}
+- Invoice reference: {{invoice_number}}
+
+**Our Concern:**
+{{concern_detail}}
+
+Per our Transportation Agreement (Section {{contract_section}}, Accessorial Schedule Item {{schedule_item}}), {{accessorial_type}} charges apply when {{contract_condition}}. Based on the BOL and delivery receipt for this shipment, {{evidence_detail}}.
+
+**Supporting Documentation (attached):**
+- BOL showing {{bol_detail}}
+- Delivery receipt showing {{pod_detail}}
+- Rate confirmation with accessorial schedule reference
+
+**Requested Action:**
+Please review the charge against the attached documentation and either (a) confirm the charge with additional supporting evidence we may not have, or (b) issue a credit memo for ${{accessorial_amount}} against invoice {{invoice_number}}.
+
+If this accessorial category is becoming a recurring issue on this lane, I'd like to discuss whether there's an operational adjustment (at either end) that could prevent these charges from accruing.
+
+Thank you for your prompt review.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## Usage Guidelines
+
+### Tone Calibration by Relationship Status
+
+| Relationship Status | Appropriate Templates | Tone Adjustment |
+|--------------------|----------------------|-----------------|
+| New carrier (< 6 months) | Onboarding welcome, rate negotiation opening, market rate discussion | More formal, set clear expectations, be specific about standards |
+| Established carrier (6-24 months) | All templates | Standard professional tone, data-driven, collaborative |
+| Strategic partner (2+ years, top tier) | Performance review positive, partnership proposal, market rate discussion | More collegial, emphasize growth opportunity, share more operational context |
+| Underperforming carrier | Performance review corrective, warning letter, exit notification | Strictly professional, document everything, focus on facts and data |
+| Carrier in dispute | Detention dispute, accessorial challenge, warning letter | Factual and neutral, avoid emotional language, always propose a resolution path |
+
+### Communication Channel Selection
+
+| Situation | Primary Channel | When to Escalate Channel |
+|-----------|----------------|------------------------|
+| Rate discussion (routine) | Email → phone follow-up | If email exchange exceeds 3 rounds without resolution |
+| Performance review (positive) | Email + QBR meeting | N/A — always share good news broadly |
+| Performance review (corrective) | Email first (documentation), then phone/meeting | If carrier doesn't respond within 5 business days |
+| Warning letter | Formal email with read receipt | If carrier doesn't respond within 3 business days, follow up via carrier VP phone call |
+| Exit notification | Formal email + same-day phone call | N/A — always deliver exit decisions via both channels |
+| Detention/accessorial dispute | Email with documentation | If not resolved in 15 business days, escalate to carrier account manager |
+| Partnership proposal | Formal letter/email → in-person meeting | N/A — partnership proposals require in-person discussion |
diff --git a/skills/carrier-relationship-management/references/decision-frameworks.md b/skills/carrier-relationship-management/references/decision-frameworks.md
new file mode 100644
index 00000000..bf8a4ac8
--- /dev/null
+++ b/skills/carrier-relationship-management/references/decision-frameworks.md
@@ -0,0 +1,534 @@
+# Decision Frameworks — Carrier Relationship Management
+
+This reference provides detailed decision trees, scoring matrices, negotiation models,
+and strategic frameworks for managing carrier portfolios, negotiating freight rates,
+running RFPs, and making allocation decisions. It is loaded on demand when the agent
+needs to make or recommend nuanced carrier relationship decisions.
+
+All thresholds, rate assumptions, and market benchmarks reflect US domestic freight
+operations across TL, LTL, intermodal, and brokerage. Adjust for regional markets
+and current cycle position.
+
+---
+
+## 1. Rate Negotiation Strategy
+
+### 1.1 Pre-Negotiation Intelligence Gathering
+
+Before entering any rate negotiation, assemble a lane-level data package for each
+lane under discussion. Negotiating without data is guessing; carriers always have
+better data about their own costs than you do about market rates.
+
+#### Data Assembly Checklist
+
+| Data Point | Source | Purpose |
+|-----------|--------|---------|
+| Current contract rate (linehaul + FSC + avg accessorials) | TMS / rate management system | Establish baseline total cost |
+| DAT 90-day lane average (spot and contract) | DAT RateView | Market benchmark for shipper leverage |
+| Greenscreens carrier-specific rate intelligence | Greenscreens.ai | Carrier-specific pricing behavior and predicted pricing |
+| Your volume on this lane (loads/week, annual loads) | TMS shipment history | Volume leverage — carriers price based on density |
+| Carrier's current tender acceptance rate on this lane | TMS acceptance data | Indicator of whether current rate is below carrier's floor |
+| Carrier's OTD and claims performance on this lane | Carrier scorecard | Service quality justification for rate position |
+| Competitor carrier bids (from recent RFP or spot activity) | RFP results / spot tender logs | Alternative pricing to create competitive tension |
+| Diesel price trend and DOE forecast | DOE Weekly Retail Diesel | FSC modeling across price scenarios |
+| Seasonal volume forecast for the lane | Demand planning / sales forecast | Carrier values volume predictability — share forecasts to build trust |
+
+### 1.2 Total Cost Modeling
+
+Never negotiate linehaul in isolation. Model total cost per shipment across diesel
+price scenarios to expose hidden costs and FSC manipulation.
+
+#### Total Cost Formula
+
+```
+Total Cost per Shipment = Linehaul Rate
+ + Fuel Surcharge (at given diesel price)
+ + Expected Detention (avg hours × rate × frequency)
+ + Expected Accessorials (liftgate, residential, etc. × frequency)
+ + Reweigh/Reclass Fees (LTL — frequency × cost)
+ + Payment Term Cost (if offering quick-pay discount)
+```
+
+#### Diesel Price Scenario Modeling
+
+For every carrier proposal, calculate total cost at three diesel price points:
+
+| Scenario | Diesel Price | Purpose |
+|----------|-------------|---------|
+| Low | $3.25/gallon | Tests carrier's FSC floor — does the FSC go to zero or maintain a minimum? |
+| Current | Current DOE average | Apples-to-apples comparison with other carriers |
+| High | $4.50/gallon | Exposes aggressive FSC schedules that inflate cost disproportionately |
+
+**Example — Comparing Two TL Carrier Proposals (Chicago to Dallas, ~920 miles):**
+
+```
+Carrier A: Linehaul $2.10/mi, FSC base $3.50, $0.01/mi per $0.05 diesel increase
+Carrier B: Linehaul $1.95/mi, FSC base $3.00, $0.015/mi per $0.05 diesel increase
+
+At diesel $3.50:
+ Carrier A: ($2.10 × 920) + ($0.00 FSC) = $1,932
+ Carrier B: ($1.95 × 920) + ($0.015 × 10 increments × 920) = $1,794 + $138 = $1,932
+
+At diesel $4.50:
+ Carrier A: ($2.10 × 920) + ($0.01 × 20 × 920) = $1,932 + $184 = $2,116
+ Carrier B: ($1.95 × 920) + ($0.015 × 30 × 920) = $1,794 + $414 = $2,208
+
+Carrier B is $92 more expensive at high diesel despite a $0.15/mi lower linehaul.
+The aggressive FSC base ($3.00 vs. $3.50) and steeper increment ($0.015 vs. $0.01)
+make Carrier B the more expensive option when fuel prices rise.
+```
+
+### 1.3 Negotiation Positioning by Market Cycle
+
+The freight market cycle determines your leverage. Negotiate differently in each phase:
+
+#### Shipper-Favorable Market (Capacity Surplus)
+
+Indicators: DAT load-to-truck ratio <3:1, OTRI <5%, spot rates below contract by >10%.
+
+| Tactic | Detail |
+|--------|--------|
+| Push for rate reductions | Target 5-12% reduction on lanes where your rate exceeds DAT contract benchmark by >10% |
+| Extend contract terms | Lock favorable rates for 18-24 months instead of the standard 12. Carriers will accept longer terms to secure volume during a downturn |
+| Negotiate accessorial caps | Push for detention free time of 3 hours (instead of standard 2). Negotiate liftgate and residential fees down 15-20% |
+| Add service commitments | Require 95% OTD and 92% tender acceptance as contract terms with remedy clauses (rate credits for non-performance) |
+| Don't over-squeeze | A carrier losing money on your lanes will exit when the market turns. Leave enough margin for the carrier to cover their variable costs + a thin margin. A carrier hauling your freight at $0.05/mile below their cost will be the first to reject tenders when demand returns |
+
+#### Carrier-Favorable Market (Capacity Shortage)
+
+Indicators: DAT load-to-truck ratio >6:1, OTRI >12%, spot rates above contract by >15%.
+
+| Tactic | Detail |
+|--------|--------|
+| Protect volume commitments | Offer volume guarantees (minimum loads/week) in exchange for capacity commitments. Carriers in a tight market prioritize shippers who provide consistent, guaranteed volume |
+| Accept moderate rate increases | A 5-8% increase is reasonable when the market has moved 15-20%. Refusing all increases pushes carriers to more profitable freight |
+| Accelerate payment terms | Offer 15-day or quick-pay terms (vs. standard 30-day) as a non-rate incentive. Carriers are cash-constrained in tight markets — faster payment is worth 2-3% rate equivalent |
+| Improve shipper operations | Reduce driver detention, offer drop-trailer programs, ensure consistent dock scheduling. Every operational improvement makes your freight more attractive relative to competitors |
+| Negotiate multi-year with escalators | Lock base rates for 24 months with a pre-agreed annual escalator (3-5%) tied to a cost index. Protects against further rate spikes while giving the carrier predictability |
+
+#### Transitional Market
+
+Indicators: Mixed signals — OTRI between 5-12%, spot-contract spread narrowing.
+
+| Tactic | Detail |
+|--------|--------|
+| Benchmark aggressively | Transition markets are when benchmark data matters most. Carriers will argue the market is tighter than it is (if transitioning to carrier-favorable) or softer (if transitioning to shipper-favorable). Let the data decide |
+| Run mini-bids | Instead of full RFPs, run targeted mini-bids on your bottom-performing 20% of lanes. This creates competitive pressure without disrupting your entire routing guide |
+| Lock strategic lanes | Secure rates on your highest-volume, most critical lanes first. Leave secondary lanes flexible to benefit from continued market movement |
+
+### 1.4 Concession Strategy
+
+When a negotiation reaches an impasse, use structured concessions to find agreement
+without giving away core economics:
+
+#### Concession Priority (Give These First — They Cost Less Than They're Worth)
+
+| Concession | Your Cost | Carrier Value | When to Offer |
+|-----------|-----------|---------------|---------------|
+| Volume commitment (guarantee minimum loads/week) | Low — you were shipping this volume anyway | High — predictable volume improves carrier utilization | When carrier won't budge on rate |
+| Faster payment terms (Net 15 vs. Net 30) | Moderate — accelerates cash outflow by 15 days | High — carriers are always cash-constrained | When spread between positions is <5% |
+| Drop-trailer program | Moderate — requires trailer parking space | Very High — eliminates driver detention, improves asset utilization | When carrier cites detention as cost driver |
+| Consistent appointment scheduling | Low — operational discipline | High — drivers can plan routes and HOS around fixed appointments | When carrier cites unpredictable scheduling |
+| Multi-year contract with escalators | Low — locks rate but adds predictability | High — long-term revenue certainty | When carrier values stability over short-term optimization |
+
+#### Concession Boundary (Never Give These Away)
+
+| Element | Why It's Non-Negotiable |
+|---------|----------------------|
+| FSC table transparency | Opaque FSC schedules are a carrier margin tool, not a cost recovery mechanism |
+| Accessorial audit rights | You must be able to verify every accessorial charge against the BOL and contract |
+| Service-level remedies | A contract without OTD and tender acceptance minimums is just a rate sheet with no accountability |
+| Right to re-bid lanes annually | Market conditions change — you need the ability to benchmark and adjust |
+| Carrier compliance requirements (FMCSA, insurance) | Safety and legal compliance are not negotiable under any market condition |
+
+---
+
+## 2. Carrier Portfolio Optimization
+
+### 2.1 Portfolio Health Assessment
+
+Run this assessment quarterly to identify optimization opportunities:
+
+#### Step 1: Carrier Concentration Analysis
+
+For each lane in your top 50 by volume:
+
+| Metric | Target | Action If Out of Range |
+|--------|--------|----------------------|
+| Primary carrier volume share | 50-70% | If >70%: diversify. If <50%: routing guide isn't being followed — investigate ops compliance |
+| Number of active carriers on lane | 2-4 | If <2: single point of failure risk. If >4: volume is too fragmented for carriers to care |
+| Backup carrier last-used date | Within 90 days | If >90 days: the backup is stale. Run a test load to confirm the carrier can still service the lane |
+| Spot freight % on lane | <15% | If >15%: routing guide is failing. Either rates are below market or tender acceptance is low |
+
+#### Step 2: Carrier Scorecard Triage
+
+Rank all active carriers by composite score (weighted: OTD 30%, tender acceptance 25%,
+claims ratio 20%, invoice accuracy 15%, communication/responsiveness 10%).
+
+| Tier | Score Range | Action |
+|------|------------|--------|
+| A — Strategic Partners | ≥90% | Increase allocation, offer longer-term contracts, invest in integration (EDI, API), invite to annual business review |
+| B — Reliable Performers | 75-89% | Maintain current allocation, monitor for improvement or decline, include in next RFP |
+| C — Underperformers | 60-74% | Issue corrective action plan with 60-day timeline. Reduce allocation by 25%. If no improvement at 60 days, reduce by another 25% |
+| D — Exit Candidates | <60% | Initiate carrier exit process (see §2.4). Stop new lane awards immediately. Allow existing commitments to run out |
+
+#### Step 3: Spend Optimization
+
+| Analysis | Method | Target |
+|----------|--------|--------|
+| Rate-vs-market alignment | Compare contract rates to DAT contract lane average for each active lane | Within ±8% of DAT. If >+15%, renegotiate. If <-10%, carrier may be underpriced and at exit risk |
+| Accessorial spend ratio | Total accessorials / total linehaul spend | <8% of total spend. If >12%, audit accessorial billing and address root causes (detention, reclass) |
+| Spot premium tracking | (Avg spot rate - avg contract rate) / avg contract rate | <15% premium. If >25%, routing guide coverage is insufficient |
+| Small shipment consolidation | Identify LTL shipments to same destination within 48-hour windows | Consolidate into TL or multi-stop when LTL spend on a lane exceeds $5K/month |
+
+### 2.2 Routing Guide Design
+
+The routing guide is your operational expression of carrier strategy. A well-designed
+guide executes itself; a poorly designed one requires constant manual intervention.
+
+#### Structure by Lane Volume
+
+| Lane Volume | Guide Depth | Primary % | Secondary % | Tertiary % |
+|-------------|------------|-----------|-------------|------------|
+| >10 loads/week | 3-4 carriers | 50-60% | 25-30% | 10-20% |
+| 5-10 loads/week | 3 carriers | 55-65% | 25-30% | 10-15% |
+| 2-5 loads/week | 2-3 carriers | 60-75% | 25-40% | — |
+| <2 loads/week | 2 carriers (or 1 + broker) | 70-80% | 20-30% | — |
+
+#### Tender Waterfall Logic
+
+```
+1. Tender to Primary Carrier
+ → If accepted within 2 hours: assign
+ → If rejected or no response:
+
+2. Tender to Secondary Carrier
+ → If accepted within 1.5 hours: assign
+ → If rejected or no response:
+
+3. Tender to Tertiary Carrier
+ → If accepted within 1 hour: assign
+ → If rejected or no response:
+
+4. Move to Spot Procurement
+ → Post to carrier board or contact preferred spot carriers
+ → Set rate ceiling at tertiary contract rate + 15%
+ → If no coverage within 2 hours at ceiling: escalate to manager
+```
+
+#### Routing Guide Maintenance Cadence
+
+| Activity | Frequency | Owner |
+|----------|-----------|-------|
+| Review lane-level tender acceptance rates | Weekly | Transportation Analyst |
+| Adjust carrier allocation based on performance trends | Monthly | Transportation Manager |
+| Full routing guide audit (dead lanes, stale backups, rate alignment) | Quarterly | Director of Transportation |
+| Complete routing guide rebuild (RFP) | Annually or after major volume/network change | VP Supply Chain + Procurement |
+
+### 2.3 Carrier Onboarding Process
+
+A standardized onboarding process protects against compliance risk and sets performance
+expectations from day one.
+
+#### Onboarding Checklist
+
+| Step | Timeline | Owner | Verification Method |
+|------|----------|-------|-------------------|
+| FMCSA authority verification (active MC#, property authorization) | Day 1 | Compliance | SAFER website direct lookup |
+| Insurance verification ($1M+ auto liability, $100K cargo, workers comp) | Day 1 | Compliance | FMCSA Insurance tab + certificate of insurance on file |
+| Safety rating and CSA score review | Day 1 | Compliance | SAFER + CSA BASIC percentiles — flag if Unsafe Driving or HOS >75th percentile |
+| W-9 and payment setup | Days 1-3 | AP/Finance | IRS TIN matching |
+| Carrier agreement execution (rate confirmation template, accessorial schedule, insurance requirements, performance expectations) | Days 3-5 | Transportation Manager | Signed agreement on file |
+| TMS/EDI setup (210, 214, 990 transactions if applicable) | Days 5-10 | IT/Integration | Test transaction confirmation |
+| Initial rate confirmation for awarded lanes | Days 5-7 | Transportation Manager | Countersigned rate confirmation per lane |
+| 30-day trial loads (minimum 5 loads before full allocation) | Days 10-40 | Operations | Trial performance review at day 30 — OTD, communication, billing accuracy |
+| Quarterly compliance re-verification (ongoing) | Every 90 days | Compliance | Automated FMCSA/insurance monitoring via Highway, RMIS, or Carrier411 |
+
+### 2.4 Carrier Exit Process
+
+Exiting a carrier requires planning to avoid service disruption on lanes they currently serve.
+
+#### Decision: Immediate vs. Managed Exit
+
+| Scenario | Exit Type | Timeline |
+|----------|-----------|----------|
+| FMCSA authority revoked or insurance lapsed | Immediate — stop tendering now | 0 days |
+| Confirmed double-brokering | Immediate — stop tendering, document evidence | 0 days |
+| Unsatisfactory safety rating | Immediate — stop tendering | 0 days |
+| Corrective action plan failed (service metrics) | Managed — transition volume over 30-60 days | 30-60 days |
+| Rate renegotiation failed (carrier above market) | Managed — transition after RFP award | 60-90 days |
+| Strategic portfolio simplification (too many carriers) | Managed — transition volume at next contract renewal | 90-120 days |
+
+#### Managed Exit Steps
+
+1. **Identify replacement capacity** — ensure backup carriers on every lane the exiting carrier serves can absorb the volume. Run test loads if backups haven't been used in 90+ days.
+2. **Communicate transparently** — tell the carrier why. "Your OTD has been below 85% for the last quarter despite our corrective action plan. We need to shift this volume to a carrier that can meet our service requirements." Burning bridges is unnecessary — carriers improve, get acquired, or re-enter your network in future cycles.
+3. **Transition volume gradually** — reduce allocation by 25% per week over 4 weeks. Abrupt volume loss can damage the carrier's operations (especially small carriers who built capacity around your freight).
+4. **Settle outstanding claims and invoices** — ensure all open claims are filed and all invoices are paid or disputed before the relationship goes dormant. Unresolved financial items turn a professional exit into a adversarial one.
+5. **Retain the carrier record** — do not delete the carrier from your systems. Document exit reasons, performance history, and corrective actions. If the carrier improves or changes ownership, you may onboard them again in 12-24 months.
+
+---
+
+## 3. RFP Execution Framework
+
+### 3.1 RFP Timeline
+
+| Phase | Duration | Activities |
+|-------|----------|-----------|
+| 1 — Pre-RFP Analysis | Weeks 1-2 | Analyze 12 months of shipment data, identify lanes for bid, benchmark current rates against DAT/Greenscreens, set cost and service targets, define evaluation criteria and weightings |
+| 2 — RFP Development | Weeks 3-4 | Build lane-level bid package with volume, equipment, and service requirements. Define accessorial schedule, insurance minimums, and contract terms. Prepare carrier communication and Q&A timeline |
+| 3 — Carrier Outreach | Week 5 | Distribute RFP to incumbent carriers + 5-10 prospective carriers identified through market research or peer referrals. Allow 2-3 weeks for bid submission |
+| 4 — Bid Collection | Weeks 5-7 | Answer carrier questions (standardize responses via Q&A document shared with all bidders). Remind non-respondents at the halfway mark |
+| 5 — Bid Analysis | Weeks 8-9 | Score bids using weighted criteria (see §3.2). Model total cost per lane. Rank carriers per lane. Identify negotiation targets (carriers close to award threshold) |
+| 6 — Negotiation | Weeks 9-10 | Final-round negotiation with top 2-3 carriers per lane. Focus on lanes where top bids are within 5% of each other — these are negotiable. Do not renegotiate with the low bidder on lanes where they're already 10%+ below the field |
+| 7 — Award | Week 11 | Notify winning carriers with lane awards and effective dates. Notify losing carriers with feedback (if they ask). Begin rate confirmation process |
+| 8 — Implementation | Weeks 11-12 | Load new rates in TMS. Update routing guide. Run 2-week parallel period with old and new guides. Resolve any issues before full cutover |
+
+### 3.2 Bid Evaluation Scoring
+
+#### Criteria Weighting
+
+| Criterion | Weight | Data Source | Scoring Method |
+|-----------|--------|-------------|---------------|
+| Rate competitiveness | 40% | Bid response | Normalize to 100-point scale where lowest total cost (linehaul + modeled FSC + expected accessorials) = 100, and each 1% above lowest = -3 points |
+| Service history / OTD | 25% | Carrier scorecard (for incumbents) or reference checks (for new carriers) | 100 points for ≥96% OTD, 80 for 93-95%, 60 for 90-92%, 40 for 85-89%, 0 for <85% |
+| Capacity commitment | 20% | Bid response (stated tender acceptance commitment, equipment availability, driver count on the lane) | 100 points for ≥95% acceptance commitment with driver count evidence, scaled down based on commitment level and supporting evidence |
+| Operational fit | 15% | Bid response + due diligence | Technology integration (EDI/API), FMCSA compliance score, driver domicile proximity, equipment match, prior relationship quality |
+
+#### Example Scoring — Lane CHI-DAL (5 loads/week)
+
+```
+ Rate (40%) Service (25%) Capacity (20%) Ops Fit (15%) Total
+Carrier A: 85 × 0.40 95 × 0.25 90 × 0.20 80 × 0.15 = 88.75
+Carrier B: 100 × 0.40 70 × 0.25 85 × 0.20 75 × 0.15 = 86.75
+Carrier C: 92 × 0.40 90 × 0.25 80 × 0.20 90 × 0.15 = 89.10
+
+Award: Carrier C as primary (89.10), Carrier A as secondary (88.75).
+Carrier B has lowest rate but weakest service — appropriate as tertiary.
+```
+
+### 3.3 Incumbent vs. New Carrier Evaluation
+
+Incumbents have data; new carriers have promises. Adjust evaluation accordingly:
+
+| Factor | Incumbent | New Carrier |
+|--------|-----------|-------------|
+| Service history | Use actual OTD, claims, tender acceptance from your data | Use carrier's reported statistics + 2-3 reference checks from similarly sized shippers |
+| Rate credibility | High — they know the lane and are pricing from experience | Moderate — new carriers may under-bid to win then renegotiate after award. Discount new-carrier bids by 3-5% for risk |
+| Implementation risk | Low — already in your systems, familiar with your operations | Moderate — onboarding takes 2-3 weeks, first-month performance often lags |
+| Competitive tension value | Moderate — they know you know their performance | High — new entrants create competitive pressure that benefits your entire portfolio |
+
+### 3.4 Post-RFP Rate Lock and Market Movement
+
+Your RFP award locks rates for 12 months (typical). But the market moves. Build
+these protections into the contract:
+
+- **Market-based reopener clause:** If DAT contract lane average moves >15% from the awarded rate for 60+ consecutive days, either party may request a rate review. This protects you in a softening market and protects the carrier in a tightening market.
+- **Volume band pricing:** If your actual volume on a lane falls below 75% or exceeds 125% of the RFP-stated volume, rates are subject to renegotiation. This prevents you from losing volume and still paying volume-discounted rates, or from flooding a carrier with unanticipated volume at rates that don't cover their incremental costs.
+- **Annual escalator option:** For multi-year contracts, build in a pre-agreed escalator (typically 2-4% annually) tied to a published index (PPI-Truck Transportation, DAT National Average). This avoids the disruption of an annual RFP while keeping rates aligned with costs.
+
+---
+
+## 4. Contract vs. Spot Market Decision Framework
+
+### 4.1 Decision Matrix
+
+| Condition | Recommendation | Rationale |
+|-----------|---------------|-----------|
+| Lane volume >3 loads/week, consistent year-round | Contract | Carrier will invest in dedicated capacity for predictable volume |
+| Lane volume 1-3 loads/week, seasonal | Contract for peak months, spot for off-peak | Avoids paying contract rates during low-demand months |
+| Lane volume <1 load/week, unpredictable | Spot or broker relationship | Carriers won't commit capacity to inconsistent volume; contract rates will be inflated to cover utilization risk |
+| Spot rates are >15% below contract rate for 60+ days | Move 20-30% of volume to spot | Market has moved significantly — capture savings while maintaining contract relationship |
+| Spot rates are >15% above contract rate | Stay on contract, honor volume commitments | This is when contract value materializes — your carriers are holding rates below market for you. Reward their commitment by giving them your full volume |
+| Customer requires guaranteed transit time | Contract with service-level agreement | Spot carriers have no SLA obligation — you can't guarantee what you can't control |
+| Lane serves a production line or retail replenishment | Contract with primary and secondary carriers | Risk of spot market non-coverage is unacceptable for critical supply chains |
+| New lane with unknown volume pattern | Spot for 60-90 days, then evaluate | Gather data before committing to a contract rate that may not reflect actual demand |
+
+### 4.2 Spot Market Best Practices
+
+When procuring on the spot market:
+
+- **Set a rate ceiling** before posting. Use your tertiary contract rate + 15% as the maximum. Anything above that threshold requires manager approval.
+- **Vet the carrier** even for single loads. At minimum: FMCSA authority check, insurance verification, Carrier411 or Highway check for complaints. A 60-second screening prevents catastrophic outcomes (uninsured carrier, double-brokered load, stolen freight).
+- **Demand rate confirmation** before the truck arrives. Verbal agreements on spot loads are unenforceable. Get the rate confirmation signed with all accessorials, FSC, and detention terms specified.
+- **Track spot premium** meticulously. Report spot vs. contract spread weekly by lane. If any lane consistently shows >20% spot premium, your routing guide on that lane needs attention.
+
+---
+
+## 5. Carrier Onboarding and Offboarding Decision Trees
+
+### 5.1 Onboarding Decision Tree
+
+```
+New carrier candidate identified
+│
+├─ FMCSA authority check
+│ ├─ Authority inactive/revoked → REJECT (do not proceed)
+│ ├─ Authority <6 months old → PROCEED WITH CAUTION (new entrant risk)
+│ └─ Authority active, >12 months → PROCEED
+│
+├─ Insurance verification
+│ ├─ Auto liability <$1M → REJECT (below your minimum)
+│ ├─ Cargo insurance <$100K → NEGOTIATE (require $100K minimum)
+│ └─ Meets all minimums → PROCEED
+│
+├─ Safety assessment
+│ ├─ FMCSA Unsatisfactory rating → REJECT
+│ ├─ CSA BASIC >90th percentile on Unsafe Driving → REJECT
+│ ├─ CSA BASIC >75th percentile on any BASIC → FLAG for risk review
+│ └─ CSA acceptable → PROCEED
+│
+├─ Financial health check
+│ ├─ Broker bond revoked or reduced → REJECT (if broker)
+│ ├─ Recent insurance underwriter changes (3+ in 12 months) → FLAG
+│ ├─ Driver complaints on Carrier411 re: pay → FLAG for monitoring
+│ └─ No red flags → PROCEED
+│
+├─ Operational fit
+│ ├─ No EDI/API capability and your volume requires it → NEGOTIATE timeline
+│ ├─ Equipment doesn't match requirements → REJECT for this lane
+│ └─ Operational fit confirmed → PROCEED
+│
+└─ ONBOARD: Execute carrier agreement, set up in TMS, run trial loads
+```
+
+### 5.2 Offboarding Decision Tree
+
+```
+Carrier performance or compliance concern identified
+│
+├─ Compliance failure (authority, insurance, safety)
+│ ├─ Authority revoked → IMMEDIATE EXIT (stop tendering today)
+│ ├─ Insurance lapsed → IMMEDIATE SUSPENSION (reinstate if corrected in 48 hrs)
+│ ├─ Unsatisfactory safety rating → IMMEDIATE EXIT
+│ └─ CSA scores worsened into >90th percentile → 30-DAY REVIEW with carrier
+│
+├─ Service performance failure
+│ ├─ OTD <85% for 60 days
+│ │ ├─ First occurrence → CORRECTIVE ACTION PLAN (60-day timeline)
+│ │ └─ Second occurrence after CAP → MANAGED EXIT (30-60 days)
+│ │
+│ ├─ Tender acceptance <70% for 30 days
+│ │ ├─ Carrier communicating, rate issue → RENEGOTIATE
+│ │ └─ Carrier non-responsive → MANAGED EXIT (30 days)
+│ │
+│ └─ Claims ratio >2% for 90 days → CORRECTIVE ACTION PLAN
+│
+├─ Integrity failure
+│ ├─ Double-brokering confirmed → IMMEDIATE EXIT + document for industry
+│ ├─ Insurance fraud (forged certificate) → IMMEDIATE EXIT + report to FMCSA
+│ └─ Systematic overbilling (>5% overcharge pattern) → CORRECTIVE ACTION, exit if not resolved in 30 days
+│
+└─ Strategic portfolio decision
+ ├─ Carrier redundant (consolidating) → MANAGED EXIT at contract renewal
+ └─ Carrier non-competitive on rate → INCLUDE IN NEXT RFP (give them a chance to compete)
+```
+
+---
+
+## 6. Market Cycle Positioning
+
+### 6.1 Cycle Identification Framework
+
+The freight market follows a pattern of loosening and tightening that repeats every
+2-3 years. Identifying where you are in the cycle determines your negotiation stance,
+contract strategy, and portfolio decisions.
+
+#### Leading Indicators (Signal Direction 3-6 Months Ahead)
+
+| Indicator | Source | Shipper-Favorable Signal | Carrier-Favorable Signal |
+|-----------|--------|------------------------|------------------------|
+| Class 8 truck orders | ACT Research, FTR | Rising (new capacity entering) | Falling (capacity leaving or not being replaced) |
+| FMCSA new authority applications | FMCSA data | Rising (new carriers entering) | Falling (fewer new entrants, possibly exits increasing) |
+| Diesel price trend | DOE | Falling (lowers carrier costs, reduces FSC) | Rising sharply (squeezes small carriers, may cause exits) |
+| Manufacturing PMI | ISM | <50 (contraction, less freight demand) | >55 (expansion, freight demand growing) |
+| Retail inventory-to-sales ratio | Census Bureau | Rising (retailers overstocked, less reorder freight) | Falling (retailers restocking, generating freight demand) |
+
+#### Coincident Indicators (Confirm Current Position)
+
+| Indicator | Source | Shipper-Favorable | Carrier-Favorable |
+|-----------|--------|------------------|------------------|
+| DAT load-to-truck ratio | DAT | <3:1 (more trucks than loads) | >6:1 (more loads than trucks) |
+| Outbound Tender Rejection Index (OTRI) | FreightWaves SONAR | <5% (carriers accepting almost everything) | >12% (carriers cherry-picking profitable freight) |
+| Spot rate trend (13-week) | DAT, Greenscreens | Declining or flat | Rising >5% over 13 weeks |
+| Your tender acceptance rate | TMS data | >95% across portfolio | <85% across portfolio |
+
+### 6.2 Strategic Actions by Cycle Phase
+
+| Phase | Duration (typical) | Rate Action | Contract Action | Portfolio Action |
+|-------|-------------------|-------------|-----------------|-----------------|
+| Early recovery (market tightening) | 3-6 months | Lock rates on top 30% of lanes before carriers reprice | Extend expiring contracts 6-12 months at current rates | Onboard 2-3 new carriers for surge capacity |
+| Peak (tight market) | 6-12 months | Minimize rate exposure — renegotiate only what's necessary | Honor commitments — this builds carrier trust for the downturn | Increase allocation to asset carriers (brokers get unreliable in tight markets) |
+| Early softening (market loosening) | 3-6 months | Run mini-bids on your worst-performing 20% of lanes | Let short-term contracts expire — rebid at new market rates | Evaluate carrier portfolio for exits (weak performers lose leverage to resist) |
+| Trough (soft market) | 6-12 months | Full RFP — maximum competitive tension, target 8-15% savings | Sign 18-24 month contracts to lock favorable rates | Consolidate to fewer, stronger carriers (volume concentration maximizes discount) |
+
+---
+
+## Appendix A — Quick-Reference Decision Cards
+
+### Card 1: "Should I renegotiate this carrier's rate?"
+
+```
+IF contract rate > DAT contract average + 15% for 60+ days → YES
+IF carrier tender acceptance < 75% for 30+ days → YES (rate is likely below their floor)
+IF your volume dropped >25% from what was committed → YES (proactive, before carrier notices)
+IF spot market is >15% below your contract for 60+ days → YES
+IF carrier's service scores are in top 10% of your portfolio → NO (pay for quality)
+IF contract expires in <90 days → WAIT for renewal negotiation
+```
+
+### Card 2: "How many carriers should I have on this lane?"
+
+```
+IF lane volume > 10 loads/week → 3-4 carriers
+IF lane volume 5-10/week → 3 carriers
+IF lane volume 2-5/week → 2-3 carriers
+IF lane volume < 2/week → 1 carrier + 1 broker backup
+IF lane is customer-critical (JIT, perishable, penalty clauses) → add 1 more carrier than volume alone suggests
+IF lane serves a single customer who is >20% of your revenue → NEVER fewer than 3
+```
+
+### Card 3: "Is this carrier financially healthy?"
+
+```
+CHECK FMCSA for active authority and current insurance → If either is lapsed, STOP
+CHECK insurance: has the underwriter changed 3+ times in 12 months? → RED FLAG
+CHECK Carrier411/CarrierOK: driver complaints about pay? → YELLOW FLAG
+CHECK: has the carrier's bond amount decreased? → RED FLAG (for brokers)
+CHECK: sudden decline in tender acceptance across all your lanes? → YELLOW FLAG
+IF 2+ yellow flags or 1+ red flag → REDUCE EXPOSURE incrementally, do not wait
+```
+
+### Card 4: "Should I go to spot market on this load?"
+
+```
+IF all routing guide carriers rejected → YES (no choice)
+IF spot rate < contract rate - 10% → YES (capture savings, track as data for renegotiation)
+IF lane is irregular (< 1 load/week) and no contract carrier → YES
+IF customer requires guaranteed transit and SLA → NO (stay on contract)
+IF you're in peak season and spot rates are 30%+ above contract → NO (honor contract, build carrier goodwill)
+ALWAYS: vet the spot carrier (FMCSA check, rate confirmation signed before dispatch)
+```
+
+---
+
+## Appendix B — Glossary
+
+| Term | Definition |
+|------|-----------|
+| BASIC | Behavior Analysis and Safety Improvement Categories — the seven CSA safety dimensions scored by FMCSA |
+| CAP | Corrective Action Plan — formal performance improvement plan with timeline and metrics |
+| CSA | Compliance, Safety, Accountability — FMCSA's carrier safety measurement system |
+| DAT | The largest spot market freight data provider (now DAT Freight & Analytics) |
+| DOE | Department of Energy — publishes weekly national average diesel prices used for FSC calculations |
+| EDI | Electronic Data Interchange — standardized electronic communication between shipper and carrier systems |
+| FSC | Fuel Surcharge — variable rate component indexed to diesel prices |
+| Greenscreens | AI-powered freight rate intelligence platform for benchmarking and predictive pricing |
+| MC# | Motor Carrier number — FMCSA-issued operating authority identifier |
+| OTRI | Outbound Tender Rejection Index — published by FreightWaves SONAR, measures % of electronic tenders rejected by carriers |
+| PPI | Producer Price Index — published by BLS, used as a cost escalator in multi-year contracts |
+| RMIS | Registry Monitoring Insurance Service — third-party carrier compliance monitoring platform |
+| RFP | Request for Proposal — formal bid process for awarding freight lanes to carriers |
+| SAFER | Safety and Fitness Electronic Records — FMCSA's public carrier database |
+| SCAC | Standard Carrier Alpha Code — 2-4 letter identifier for each carrier |
+| TMS | Transportation Management System — software for managing freight operations and carrier relationships |
diff --git a/skills/carrier-relationship-management/references/edge-cases.md b/skills/carrier-relationship-management/references/edge-cases.md
new file mode 100644
index 00000000..26426db4
--- /dev/null
+++ b/skills/carrier-relationship-management/references/edge-cases.md
@@ -0,0 +1,527 @@
+# Carrier Relationship Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex carrier management situations that don't resolve through standard decision frameworks.
+
+These edge cases represent the scenarios that separate experienced transportation managers from everyone else. Each involves competing priorities, incomplete information, relationship dynamics, and real financial exposure. They are structured to guide resolution when standard carrier management playbooks break down.
+
+---
+
+## How to Use This File
+
+When a carrier relationship situation doesn't fit a clean decision tree — when market dynamics create conflicting incentives, when carrier behavior signals something deeper than surface metrics show, or when the standard rate negotiation playbook produces a bad outcome — find the edge case below that most closely matches the situation. Follow the expert approach step by step.
+
+---
+
+### Edge Case 1: Capacity Squeeze During Hurricane Season — Balancing Spot Market Panic Against Strategic Positioning
+
+**Situation:**
+A national consumer goods manufacturer ships 120+ FTL loads per week across the Southeast. Hurricane Michaela has made landfall on the Gulf Coast, and FMCSA has issued an emergency declaration for FL, AL, MS, and LA. Your top 3 carriers in the region have pulled drivers off Florida and coastal Alabama routes. Your routing guide for 35 Southeast lanes is effectively dead — tender rejections are running 60%+ for the last 48 hours. Spot rates on lanes touching Florida have jumped from $2.80/mile to $6.50/mile. Your VP of Sales is calling because Walmart's DC in Lakeland, FL needs 8 loads of household cleaning products by Friday for hurricane response stocking, and your West Coast operations need 12 loads of raw materials moved out of Mobile, AL before the storm surge floods the port warehouse.
+
+The spot market is a feeding frenzy. Brokers are quoting $8,000 for a $3,200 lane. Your procurement team wants to pay whatever it takes. Your CFO wants to know why freight costs just tripled.
+
+**Why It's Tricky:**
+Paying panic rates on 35+ lanes for 7-10 days can cost $150K-$300K in incremental freight spend above your contract rates. But refusing to pay means freight doesn't move, Walmart doesn't get their hurricane response product (damaging a $40M annual relationship), and your Mobile warehouse potentially floods with $2M in raw materials sitting on the floor.
+
+The deeper problem: every shipper in the Southeast is bidding up the same shrinking carrier pool simultaneously. The carriers and brokers who covered your freight reliably at $2.80/mile last week are now selling that same capacity at $6.50 to the highest bidder — and your contract rates are irrelevant because force majeure clauses in most carrier agreements suspend rate obligations during declared emergencies.
+
+**Common Mistake:**
+Posting all 35 lanes to the spot market simultaneously at "market rate" and accepting the first truck that quotes. This guarantees you'll pay peak panic pricing on every load, attract the least reliable carriers (the quality carriers are already committed), and create a billing reconciliation nightmare when 35 different spot carriers each have different rate confirmations, detention terms, and accessorial structures.
+
+The second mistake: trying to enforce contract rates during a declared emergency. Your contract carriers aren't rejecting tenders to be adversarial — they literally can't get drivers into the affected area safely. Threatening to pull their contract lanes post-storm will earn you a reputation as a shipper who doesn't understand emergencies, and they'll remember at the next RFP.
+
+**Expert Approach:**
+1. Triage your 35 affected lanes immediately. Not all lanes are equal. Categorize into three tiers:
+ - **Tier 1 — Must Move (8-10 lanes):** Customer penalty exposure, perishable, safety stock at risk, or product at physical risk (the Mobile warehouse). These move at spot market rates, period.
+ - **Tier 2 — Should Move (12-15 lanes):** Standard replenishment, can tolerate 3-5 day delay without customer impact. Delay these loads until the initial panic subsides (spot rates typically drop 30-40% within 72 hours of landfall as the actual storm path becomes clear and unaffected corridors reopen).
+ - **Tier 3 — Can Wait (10-12 lanes):** Low urgency, large buffer stock at destination. Hold these until your contract carriers resume normal operations (typically 7-14 days post-storm for the directly affected region).
+
+2. For Tier 1 loads, do not post to open load boards. Instead, call your top 3 broker partners directly. Offer them a multi-load commitment: "I have 8 loads that need to move in the next 48 hours. I'll commit all 8 to you at $5,200/load if you can guarantee coverage." A broker getting 8 committed loads at $5,200 will prioritize you over single-load spot postings at $6,500 because the certainty of 8 loads is more valuable than the possibility of 8 individual loads at a higher rate.
+
+3. Activate regional carriers you've pre-positioned for exactly this scenario. Every experienced transportation manager maintains relationships with 3-5 small carriers in hurricane-prone regions who run owner-operator fleets. These carriers park their trucks inland before the storm and redeploy as soon as roads open. They're expensive ($4.50-$5.50/mile during events), but they're available when national carriers have pulled out.
+
+4. For the Mobile warehouse evacuation, consider a dedicated carrier or fleet provider rather than spot market. A fleet of 12 trucks from a single carrier coordinating an evacuation is operationally cleaner than 12 individual spot trucks arriving on different schedules. Contact your largest asset carrier and offer a premium ($4,800/load on a $3,200 lane) for dedicated fleet assignment over 48 hours. Frame it as: "We need a fleet solution, not 12 individual loads. Can you dedicate 12 power units for 48 hours?"
+
+5. After the storm: do not retroactively dispute the premium rates you paid. Document the event, the incremental cost, and the business justification. Present to the CFO as a weather event cost, not a freight rate failure. Then conduct a post-storm review: which carriers came through, which disappeared? Adjust your routing guide allocation to reward carriers who provided capacity during the crisis — those carriers earned the right to your best lanes in the next calm period.
+
+**Key Indicators:**
+- Tender rejection rates above 50% on regional lanes signal a network disruption, not individual carrier problems — adjust response accordingly
+- Spot rate spikes that exceed 2× contract rates within 48 hours indicate panic pricing, not a new market equilibrium — rates will retreat
+- Carriers communicating proactively about their capacity constraints during the event are your best long-term partners — track who calls you vs. who goes silent
+- FMCSA emergency declarations suspend HOS requirements, meaning available drivers can run more hours — some capacity will return within 48-72 hours as drivers extend their available drive time
+- Monitor NOAA track updates every 6 hours — storm path changes can open or close corridors and shift where capacity is available
+
+**Documentation Required:**
+- FMCSA emergency declaration documentation
+- Lane-by-lane triage classification with business justification
+- Spot rate confirmations for all Tier 1 loads
+- Multi-load commitment agreements with brokers
+- Carrier communication log (who contacted you, who you contacted, responses)
+- Total incremental freight cost calculation vs. normal contract rates
+- Post-event carrier performance assessment
+
+**Resolution Timeline:**
+- Hours 0-6: Lane triage, Tier 1 procurement initiated, Mobile evacuation fleet secured
+- Hours 6-24: Tier 1 loads dispatched, Tier 2 loads staged for delayed dispatch
+- Days 2-5: Spot rates begin normalizing, Tier 2 loads dispatched at reduced premiums
+- Days 5-14: Contract carriers resume normal operations, Tier 3 loads move at contract rates
+- Days 14-30: Post-event review, carrier performance assessment, routing guide adjustments
+
+---
+
+### Edge Case 2: Double-Brokering Discovery Mid-Relationship
+
+**Situation:**
+Your compliance analyst runs a quarterly audit and discovers that Pinnacle Logistics (MC-892431), a broker in your routing guide handling 15 loads/week across 6 Midwest lanes, has been double-brokering approximately 30% of your freight. The evidence: BOL driver names don't match Pinnacle's dispatched driver, truck numbers on PODs belong to carriers not in Pinnacle's disclosed network, and two loads last month were delivered by a carrier with an FMCSA Conditional safety rating — a carrier your compliance standards would have rejected at onboarding.
+
+Pinnacle is your secondary carrier on 4 of these lanes and tertiary on 2. Their rates are competitive (5-8% below your primary carriers on these lanes). Their OTD is acceptable at 93%. You've had a 2-year relationship with Pinnacle's account manager, who is responsive and professional. Your operations team hasn't reported any service complaints.
+
+**Why It's Tricky:**
+Double-brokering isn't always a clear-cut "fire them immediately" situation, even though it's a serious compliance violation. The problem: Pinnacle's service has been acceptable, their rates are good, and ripping them out of 6 lanes creates an immediate capacity gap. Your operations team will feel the pain before your compliance team feels the vindication.
+
+But the risks are real: when Pinnacle re-brokers your freight, the actual carrier isn't in your insurance verification chain. If that Conditional-rated carrier causes an accident hauling your freight, your risk exposure is enormous. Pinnacle's cargo insurance may not cover loads they've brokered out (most broker cargo policies exclude double-brokered freight). And if the actual carrier is never paid (because Pinnacle pockets the margin and goes bankrupt), the actual carrier can assert a lien on your freight.
+
+**Common Mistake:**
+Ignoring the discovery because "the service is fine." The compliance risk is not hypothetical — it's actuarial. One accident with an unvetted carrier creates a liability exposure that dwarfs any rate savings. The other common mistake: confronting Pinnacle's account manager in an accusatory call that destroys any possibility of a managed transition.
+
+**Expert Approach:**
+1. Confirm the evidence before acting. Pull 90 days of BOLs and PODs for Pinnacle's loads. Cross-reference driver names on PODs against Pinnacle's disclosed carrier network. Run FMCSA lookups on the truck numbers appearing on PODs. Document every instance where the delivering carrier doesn't match Pinnacle's dispatch records. Build a clear, evidence-based file.
+
+2. Assess the scope and risk. How many loads were double-brokered? Were any of those loads high-value, temperature-sensitive, or hazmat? Did any of the actual carriers have safety or insurance issues? This determines whether the response is "serious conversation" or "immediate termination."
+
+3. Schedule a formal meeting with Pinnacle's ownership (not just the account manager). Present the findings factually: "We've identified X instances over the last 90 days where the delivering carrier did not match your dispatch records. Can you explain?" Give them the opportunity to respond. Some brokers use partner carriers through disclosed sub-broker arrangements that are technically legitimate — but undisclosed sub-brokering is not.
+
+4. If Pinnacle confirms double-brokering: require them to disclose all carriers used on your freight, retroactively. Verify insurance and FMCSA compliance for every disclosed carrier. Demand a written commitment to cease double-brokering your freight, with a contractual penalty clause for future violations. Require Pinnacle to provide carrier disclosure on every load going forward (carrier name, MC#, and driver name at time of dispatch).
+
+5. Simultaneously, begin qualifying replacement carriers for Pinnacle's 6 lanes. You'll need this capacity whether you keep Pinnacle or not — reduced trust requires a backup plan. Identify 2-3 carriers per lane from your existing portfolio or new prospects. Run trial loads within 30 days.
+
+6. Decision point at 30 days: if Pinnacle has complied with disclosure requirements and the underlying carriers pass your vetting, consider keeping them at reduced allocation (drop from secondary to tertiary on all lanes). If Pinnacle resists transparency, exit them with a managed 30-day transition using the replacement carriers you've already qualified.
+
+**Key Indicators:**
+- POD driver names consistently different from dispatch records is the primary indicator of double-brokering
+- Truck numbers (DOT numbers on the trailer or tractor) that don't match the broker's carrier network are conclusive evidence
+- A broker whose rates are consistently 5-10% below your other carriers may be achieving those rates by using carriers that don't meet your compliance standards — the discount is a risk premium you're not being compensated for
+- If the broker is evasive when asked "who is actually hauling our freight?", that's an answer in itself
+- Check whether the broker's surety bond is at the minimum $75K — a broker double-brokering heavily is likely cash-strapped
+
+**Documentation Required:**
+- 90-day audit report: BOL/POD analysis showing carrier mismatches
+- FMCSA lookups on all actual carriers identified
+- Insurance verification for actual carriers
+- Written communication to Pinnacle documenting findings and required corrective action
+- Pinnacle's response and corrective commitments
+- Replacement carrier qualification records
+- Updated carrier agreement with anti-double-brokering clause and penalty provision
+
+**Resolution Timeline:**
+- Days 0-5: Evidence compiled, risk assessment completed
+- Days 5-10: Meeting with Pinnacle ownership, findings presented
+- Days 10-30: Pinnacle corrective action implementation, replacement carrier qualification in parallel
+- Day 30: Decision on Pinnacle's future status (retain at reduced allocation vs. managed exit)
+- Days 30-60: Transition complete if exit decision is made
+
+---
+
+### Edge Case 3: Rate Renegotiation After Major Volume Loss
+
+**Situation:**
+Your company lost its largest retail customer (representing 35% of total outbound freight volume) due to a product quality issue unrelated to logistics. Your carrier contracts were negotiated 6 months ago based on volume projections that included this customer's freight. Specifically, you committed to 450 loads/week across your network, and you're now shipping 290 loads/week. Your top 5 carriers, who account for 70% of your freight spend, priced their rates based on the 450-load commitment. Some of those rates include volume-based discount tiers that you're no longer achieving.
+
+Your current contract rates are 3-6% below DAT benchmark, which was attractive at 450 loads/week but represents a potential carrier exit risk at 290 loads/week. Three of your top 5 carriers have already noticed the volume decline (their weekly load counts from you have dropped 30-40%) but haven't raised it formally yet. Your annual freight spend has gone from ~$52M to ~$34M.
+
+**Why It's Tricky:**
+You have a fiduciary obligation to manage freight costs (which means keeping rates competitive), a contractual obligation to your carriers (which may include volume commitments), and a relationship obligation (which means not blindsiding carriers who priced based on your representations). These three obligations are in tension.
+
+If you say nothing, your carriers will figure it out from their declining load counts, feel deceived, and start repricing unilaterally or rejecting tenders on less profitable lanes. If you immediately try to renegotiate rates upward to "be fair," your CFO will rightly ask why you're volunteering cost increases during a revenue decline. If you try to hold carriers to the current below-market rates despite the volume shortfall, they'll exit your least profitable lanes first — which are probably the lanes you need most.
+
+**Common Mistake:**
+Staying silent and hoping carriers don't notice. They always notice. A carrier whose load count from you drops from 60/week to 38/week adjusts their resource planning accordingly — and your freight drops in their internal priority ranking. By the time they confront you about the volume decline, they've already reallocated their best drivers and equipment to shippers who deliver consistent volume.
+
+The second mistake: proactively offering rate increases across the board. Carriers don't want charity — they want honesty, predictability, and a clear picture of future volume so they can plan.
+
+**Expert Approach:**
+1. Get ahead of the conversation. Within 2 weeks of knowing the volume loss is permanent, schedule individual calls with each of your top 5 carriers' account managers. Frame it as a strategic update, not a crisis: "We've had a significant customer change that affects our volume outlook. I want to walk you through what it means for our business together."
+
+2. For each carrier, prepare a lane-by-lane analysis showing: current committed volume, new projected volume, percentage change, and the revenue impact to the carrier. Do the carrier's math for them — it shows respect and prevents them from assuming the worst.
+
+3. Offer a restructured deal, not a rate increase. The restructured deal should include: (a) adjusted volume commitments that reflect reality (290 loads/week instead of 450), (b) a rate adjustment on lanes where your volume has dropped below the tier threshold (typically 3-5% increase), (c) a commitment to maintain or increase the carrier's percentage share of your remaining volume even though the absolute volume is lower, and (d) an honest volume forecast for the next 12 months including any new customer prospects.
+
+4. Prioritize your carrier conversations by strategic value:
+ - Carrier 1 (largest, strategic partner): Full transparency, restructured deal, multi-year commitment if they hold rates close to current levels
+ - Carriers 2-3 (strong performers): Transparent conversation, lane-level adjustment, 12-month commitment
+ - Carriers 4-5 (adequate performers): Inform of volume change, let them decide if they want to reprice or continue at current rates with reduced volume
+
+5. Use the volume loss as an opportunity to consolidate. With 290 loads/week instead of 450, you may have too many carriers in your portfolio. Offer your top 2-3 carriers a larger share of the remaining pie in exchange for holding rates flat or limiting increases to 2-3%. Consolidation = more volume per carrier = more value per carrier = better retention.
+
+6. If any carrier demands rate increases that exceed market rates, that's a signal they want to exit your portfolio. Let them — and replace them with carriers who want the volume at fair rates. In a soft market (which often accompanies shipper volume declines), finding replacement capacity is straightforward.
+
+**Key Indicators:**
+- Carriers whose load counts from you have dropped 30%+ without explanation are already planning their response — get ahead of it
+- Volume commitment shortfalls of >20% typically trigger rate reopener clauses in carrier contracts — read your contract before the carrier does
+- Carriers who ask "what happened?" informally through their account manager are signaling they want to work with you. Carriers who send formal rate increase letters without a conversation are signaling they've already decided to reprice.
+- Your leverage in this negotiation is the remaining 290 loads/week — that's still substantial freight. Don't negotiate from a position of weakness just because you lost volume.
+
+**Documentation Required:**
+- Lane-by-lane volume analysis (before and after customer loss)
+- Revenue impact by carrier (show you've done the work)
+- Restructured deal proposals per carrier (rate adjustments, volume commitments, share allocation)
+- Updated 12-month volume forecast
+- Revised carrier agreements reflecting new terms
+- Communication log documenting proactive outreach and carrier responses
+
+**Resolution Timeline:**
+- Days 0-14: Internal analysis, restructured deal proposals drafted
+- Days 14-30: Individual carrier conversations (top 5)
+- Days 30-45: Carrier responses, negotiation of adjusted terms
+- Days 45-60: Revised agreements executed, routing guide updated
+- Days 60-90: Monitor carrier behavior under new terms — OTD, tender acceptance stability
+
+---
+
+### Edge Case 4: Carrier Financial Distress — Early Warning Signs and Graduated Response
+
+**Situation:**
+TransWay Freight (MC-645221), a mid-size asset carrier with ~180 trucks, has been your primary carrier on 8 Midwest lanes for 3 years. They've been a solid B-tier performer: 94% OTD, 88% tender acceptance, 0.4% claims ratio. You ship 25 loads/week with them, representing approximately $1.8M annual freight spend — which is roughly 6% of TransWay's estimated annual revenue.
+
+Over the last 60 days, you've noticed: (a) tender acceptance has dropped from 88% to 71% with no communication about rate issues, (b) three drivers on their routes have told your dock staff they haven't been paid in two weeks, (c) TransWay changed their insurance underwriter for the third time in 12 months, (d) their FMCSA filing shows the surety bond was reduced from $75K to the minimum $10K, and (e) their VP of Operations who was your primary contact left the company last month.
+
+None of these indicators individually would trigger an exit. Together, they paint a picture of a carrier in financial distress.
+
+**Why It's Tricky:**
+Carrier financial distress is a slow-motion crisis. The carrier doesn't fail overnight — they degrade over weeks or months. During that degradation, their service deteriorates, their drivers leave, their insurance coverage becomes unreliable, and your freight is increasingly at risk. But cutting them immediately creates a capacity gap on 8 lanes, and if you're wrong about the distress, you've damaged a 3-year relationship based on speculation.
+
+The other complexity: if TransWay is in distress and you're 6% of their revenue, your sudden exit could accelerate their failure — creating the exact outcome you're trying to avoid. Other shippers on TransWay's network would also be affected, and word travels fast in the carrier community that you pulled volume from a struggling carrier without warning.
+
+**Common Mistake:**
+Ignoring the warning signs because "their OTD is still above 90%." Financial distress takes 3-6 months to manifest in service metrics. By the time OTD drops below 85%, the carrier is in crisis and your options are worse. The other mistake: immediately pulling all volume, which creates an acute capacity gap and — if TransWay finds out why — damages your reputation as a shipper who panics.
+
+**Expert Approach:**
+1. Verify each indicator independently. Run an FMCSA check on TransWay today — confirm the insurance underwriter change and bond reduction. Check Carrier411, CarrierOK, and trucking industry forums for driver complaints about non-payment. Call your 3 contacts at TransWay (not just the sales rep — call operations and maintenance managers) to gauge the internal temperature.
+
+2. Score the distress level:
+ - **Low concern (1-2 indicators):** Monitor weekly, no allocation change.
+ - **Moderate concern (3-4 indicators):** Reduce allocation by 25%, accelerate backup carrier qualification.
+ - **High concern (5+ indicators or any single critical indicator like insurance lapse):** Reduce allocation by 50%, prepare for full exit within 30 days.
+
+ TransWay has 5 indicators → High concern.
+
+3. Do not announce the allocation reduction. Simply begin shifting loads to secondary carriers on each of TransWay's 8 lanes. Reduce from 25 loads/week to 12-15/week over 3 weeks. If TransWay asks about the volume decline, your answer is honest: "We're diversifying our portfolio on a few lanes to improve our routing guide depth. Nothing personal — it's a standard portfolio rebalance."
+
+4. In parallel, qualify 2-3 replacement carriers on TransWay's 8 lanes. Prioritize lanes where TransWay is your only carrier. Run trial loads within 2 weeks. You need these backups operational before TransWay potentially fails.
+
+5. Have a direct, private conversation with TransWay's CEO or owner. Not the sales rep — the person who knows the real financial picture. Frame it as: "You've been a great partner for 3 years. We've noticed some changes recently and want to understand your situation. Is there anything we should know?" If they're transparent about challenges, you can work together on a transition plan. If they deflect or deny, that's the most worrying response of all.
+
+6. Prepare for a sudden failure scenario. If TransWay goes dark overnight (it happens — carriers sometimes just stop answering the phone), you need a 48-hour plan to cover 12-15 loads/week across 8 lanes. Pre-negotiate spot rates with your backup carriers for this exact contingency. Have rate confirmations ready to execute.
+
+7. After the situation resolves (either TransWay stabilizes or fails), update your carrier risk monitoring to include financial health indicators as quarterly screening criteria for all carriers representing >3% of your freight spend.
+
+**Key Indicators:**
+- Insurance underwriter changes 3+ times in 12 months: The current underwriter dropped TransWay and no A-rated insurer will pick them up. They're on a third-tier insurer who will also drop them soon.
+- Surety bond reduction to minimum: TransWay's bondsman is unwilling to backstop the full $75K — this means the bonding company's underwriter has assessed TransWay as high-risk.
+- Driver pay complaints: Drivers talk. If 3 drivers mention payment delays to your dock staff, there are probably 30 more experiencing the same thing across TransWay's network. Drivers who aren't paid leave — and their capacity goes with them.
+- Key executive departure: A VP of Operations who leaves a 180-truck carrier without a visible next role may be leaving a sinking ship. Check LinkedIn for other recent departures.
+- Tender acceptance decline without communication: A good carrier experiencing financial difficulty will call and explain. A carrier that just stops accepting tenders without explanation is either trying to hide the problem or has lost operational control.
+
+**Documentation Required:**
+- FMCSA screening results (authority, insurance, safety, bond)
+- Carrier411/CarrierOK complaint summary
+- Internal driver feedback log (dock staff reports)
+- Tender acceptance trend data (90-day)
+- Allocation reduction timeline and load-level records
+- Backup carrier qualification records for all 8 lanes
+- Communication log with TransWay management
+- Contingency plan for sudden carrier failure
+
+**Resolution Timeline:**
+- Days 0-3: Indicator verification, distress scoring
+- Days 3-14: Allocation reduction (25 → 12-15 loads/week), backup carrier qualification initiated
+- Days 14-21: Backup carriers running trial loads on all 8 lanes
+- Days 21-30: CEO/owner conversation, frank assessment of TransWay's outlook
+- Days 30-60: Stable at reduced allocation if TransWay stabilizes, or complete exit if distress worsens
+- Ongoing: Weekly monitoring of financial distress indicators
+
+---
+
+### Edge Case 5: Broker vs. Asset Carrier Dispute on Service Failure Liability
+
+**Situation:**
+You contracted with Overland Brokerage (MC-553890) for a critical weekly truckload lane from your Memphis plant to a Toyota assembly facility in San Antonio, TX. Overland quoted $3,100/load and committed to 48-hour transit with Tuesday 06:00 delivery. Overland sourced the loads from Patriot Haulers (MC-771204), a small asset carrier with 22 trucks, at $2,650/load.
+
+Last Tuesday, the load was 14 hours late. Toyota assessed a $28,000 line-down penalty against your company. When you called Overland to demand an explanation, their account manager said: "Patriot's driver broke down outside Dallas and didn't call dispatch for 4 hours. We only found out when Toyota called us. We're sorry, but the breakdown was Patriot's fault — take it up with them."
+
+You have a contract with Overland, not Patriot. Your contract with Overland includes a service-level clause requiring 95% OTD with a $500/incident credit for service failures. But your contract says nothing about consequential damages (like Toyota's $28K penalty). Overland is offering the $500 credit per the contract and nothing more. Patriot says they have no relationship with you and their obligation is to Overland.
+
+**Why It's Tricky:**
+The brokerage model creates a liability gap. Your contract is with Overland (the broker). Overland's contract is with Patriot (the carrier). You have no contractual relationship with Patriot. Under standard brokerage law, a broker is not a carrier — they're an intermediary. The broker's liability is generally limited to what's in your broker-shipper agreement, which in this case is $500 per service failure.
+
+The $28K Toyota penalty is a consequential damage. Even if you had contracted directly with an asset carrier, consequential damages are difficult to recover unless you specifically put the carrier on notice of the consequences (see the JIT edge case in the logistics-exception-management capability). You didn't specify the Toyota penalty exposure in your contract with Overland.
+
+But Overland knew this was a Toyota JIT delivery — it was in the tender. They presumably communicated the delivery window to Patriot. The question is whether Overland exercised reasonable care in selecting Patriot and monitoring the load. If Patriot has a history of breakdowns and Overland knew (or should have known), Overland's negligence in carrier selection could open the door to consequential damages.
+
+**Common Mistake:**
+Accepting the $500 credit and eating the $28K penalty. This teaches both Overland and your procurement team that JIT lanes can be brokered without consequence. The second mistake: threatening to sue Overland for $28K. Litigation against a broker for $28K is a money-losing proposition ($15-25K in legal costs) and destroys the relationship for all your other lanes.
+
+**Expert Approach:**
+1. Separate the immediate issue (recovering some of the $28K) from the structural issue (protecting JIT lanes going forward).
+
+2. For the immediate issue: Request Overland's carrier selection records for Patriot on this lane. Specifically: when did Overland first use Patriot? What due diligence did Overland perform? Does Patriot have a history of service failures on time-critical loads? If Overland can demonstrate reasonable carrier selection and the breakdown was a genuine one-off, your recovery beyond the $500 credit is limited. If Overland has been using Patriot despite prior failures, their negligence in carrier selection strengthens your consequential damages argument.
+
+3. Negotiate with Overland for a middle ground. Propose: Overland absorbs $5,000-$8,000 of the penalty through a combination of freight credits ($500/load for the next 10-16 loads) and a rate reduction on this lane for the next 6 months. Frame it as: "Your $500 credit doesn't reflect the magnitude of this failure. I'm not asking you to cover the full $28K, but I need you to share the pain meaningfully to justify keeping you on this lane."
+
+4. Negotiate the Toyota penalty down. Toyota's $28K chargeback is likely based on their standard penalty formula. Request the detailed calculation. Push back on overhead allocation and opportunity cost components. A 14-hour delay on a Tuesday delivery likely cost Toyota 8-10 hours of actual line time after the recovery. Aim to reduce the chargeback to $15K-$20K.
+
+5. For the structural fix: move this lane to an asset carrier as primary, with Overland as backup. JIT lanes with consequential damage exposure should never have a broker as the primary carrier. The additional carrier layer in the brokerage model (broker → carrier) adds a communication delay and removes your visibility into the actual driver and equipment.
+
+6. Update your standard broker agreement to include: (a) a requirement that the broker disclose the underlying carrier for every load, (b) a carrier vetting standard that the broker must meet (minimum FMCSA safety score, insurance levels, etc.), and (c) a liquidated damages clause for service failures on lanes designated as "JIT-critical" — a pre-agreed amount (e.g., $5,000 per occurrence) that caps your downside and the broker's exposure.
+
+**Key Indicators:**
+- A broker who deflects to "take it up with the carrier" is not operating as a responsible intermediary — they're acting as a pass-through with no accountability
+- A 22-truck carrier (Patriot) handling a Toyota JIT lane raises questions about Overland's carrier selection process — did they prioritize cost over reliability?
+- A 4-hour communication gap (driver broke down and didn't call dispatch) suggests Patriot has poor driver management processes — experienced carriers have GPS and ELD tracking that would surface a 4-hour stationary event
+- Overland's willingness (or unwillingness) to share their carrier selection records tells you a lot about their operating standards
+
+**Documentation Required:**
+- Your contract with Overland (service-level clause, liability provisions)
+- Overland's contract with Patriot (request via your contractual audit rights if applicable)
+- Toyota's penalty calculation and chargeback notice
+- Load tracking history showing the delay timeline
+- Patriot's FMCSA safety record and service history with Overland
+- Overland's carrier selection documentation for this lane
+- Negotiation correspondence with Overland (freight credit proposal)
+- Revised broker agreement with carrier disclosure and liquidated damages provisions
+
+**Resolution Timeline:**
+- Days 0-3: Toyota penalty assessment, Overland carrier selection records requested
+- Days 3-10: Negotiate Toyota chargeback reduction, negotiate Overland freight credits
+- Days 10-30: Qualify asset carrier for primary on this lane, move Overland to backup
+- Days 30-45: Revised broker agreement executed with disclosure and damages provisions
+- Days 45-60: Asset carrier fully operational on the lane, first performance review
+
+---
+
+### Edge Case 6: Carrier Acquisition Affecting Your Service Network
+
+**Situation:**
+Ridge Runner Express (MC-498132), a regional asset carrier with 85 trucks based in Knoxville, TN, has been your best-performing carrier in the Southeast for 4 years. They run 18 loads/week for you across 5 lanes, all with >96% OTD and 94% tender acceptance. Your dedicated account manager, Carol, knows your dock operations, your customers' receiving quirks, and your seasonal volume patterns. Ridge Runner just announced they've been acquired by National FreightWorks (MC-112200), a 4,500-truck national carrier known for aggressive pricing but mediocre service (their network average OTD is 91%, well below Ridge Runner's 96%).
+
+The acquisition closes in 60 days. National FreightWorks' integration plan calls for absorbing Ridge Runner's operating authority under the National FreightWorks MC#, integrating dispatching into their national operations center in Des Moines, and standardizing rates across the combined network. Carol has already been told her position will be eliminated during integration.
+
+**Why It's Tricky:**
+Carrier acquisitions almost always degrade service during the integration period (6-18 months). The acquiring carrier's systems, processes, and culture overwhelm the smaller carrier's operational excellence. Drivers who valued the family-company culture leave. Dedicated account managers are replaced by national account reps managing 50+ shippers. Rates that were competitive for a regional carrier get "standardized" to the national carrier's tariff — which may be higher or lower depending on the lane.
+
+But you can't just preemptively exit. National FreightWorks is a legitimate, large carrier. They may ultimately provide capacity and coverage that Ridge Runner couldn't. And pulling 18 loads/week before the acquisition closes signals to both Ridge Runner and National FreightWorks that you're not willing to give the combined entity a chance.
+
+**Common Mistake:**
+Waiting passively for the acquisition to complete and hoping for the best. By the time service degrades, National FreightWorks has integrated Ridge Runner's systems and you've lost your leverage to negotiate. The other mistake: immediately pulling all volume, which burns the relationship with National FreightWorks before they've even started.
+
+**Expert Approach:**
+1. Meet with National FreightWorks' sales team immediately. Request a dedicated meeting (not a mass customer communication) to discuss: their integration timeline, which operational systems will survive (Ridge Runner's dispatch or National FreightWorks'?), whether your lanes will retain dedicated drivers or be absorbed into the national driver pool, and who your new account manager will be.
+
+2. Secure contractual protections before the acquisition closes. Propose a 12-month service guarantee as a condition of continuing your volume: OTD ≥94% (a slight step-down from Ridge Runner's 96% to acknowledge integration disruption), tender acceptance ≥88%, with a rate renegotiation trigger if either metric falls below the threshold for 60 days. Get this in writing from National FreightWorks' VP of Sales before the close.
+
+3. Begin qualifying 2-3 alternative carriers for your 5 Southeast lanes immediately — not to replace Ridge Runner/National FreightWorks, but to have a plan B. Run trial loads on each lane with the alternatives within 30 days. Having alternatives operational before the integration disruption gives you options that pure good faith does not.
+
+4. Recruit Carol. If your company has the need and budget, hire Ridge Runner's account manager into your organization as a carrier relationship specialist. She knows your operations, your carriers, and your customers. Even if you can't hire her, maintain the relationship — she'll land at another carrier or broker and bring institutional knowledge of your freight.
+
+5. Plan for a 90-day post-close performance review. Track National FreightWorks' performance on your 5 lanes weekly during the integration. Set a decision point at 90 days: if service levels are within the contractual guarantee, maintain full allocation. If service has degraded below the guarantee, shift 50% of volume to your qualified alternatives and invoke the rate renegotiation clause.
+
+**Key Indicators:**
+- If National FreightWorks is centralizing dispatch, your loads will compete with 4,500 other trucks' dispatch priorities — expect tender acceptance to drop
+- If Ridge Runner's drivers are being reassigned to national routes, expect turnover on your lanes — drivers who chose a regional carrier lifestyle rarely stay at a national carrier
+- If National FreightWorks' integration team cannot name your new account manager within 30 days of close, they don't have a plan for your account
+- Watch for rate "standardization" letters after close — this is often a rate increase disguised as administrative cleanup
+
+**Documentation Required:**
+- Current carrier agreement with Ridge Runner (to understand transition terms)
+- Written service guarantee from National FreightWorks
+- Alternative carrier qualification records for all 5 lanes
+- Weekly performance tracking for 90 days post-close
+- Communication log with National FreightWorks integration team
+
+**Resolution Timeline:**
+- Days 0-15: Meeting with National FreightWorks, service guarantee negotiation
+- Days 15-45: Alternative carrier qualification, trial loads
+- Day 60: Acquisition closes
+- Days 60-150: 90-day post-close performance monitoring
+- Day 150: Decision point — maintain allocation vs. begin shifting volume
+
+---
+
+### Edge Case 7: Fuel Surcharge Table Manipulation
+
+**Situation:**
+During your annual rate review, you notice that Consolidated Carriers is proposing a new rate structure: a $0.12/mile reduction in base linehaul rate (from $2.45 to $2.33/mile) coupled with a "modernized" fuel surcharge table. The new FSC table uses a base diesel price of $2.80/gal (vs. the current DOE average of $3.85/gal) and applies $0.02/mile per $0.06 increment above the base. The current FSC table uses a base of $3.50/gal with $0.01/mile per $0.05 increment.
+
+The carrier's account manager presents this as "a meaningful linehaul reduction that demonstrates our commitment to the partnership."
+
+**Why It's Tricky:**
+The $0.12/mile linehaul reduction is real and looks good on a summary report. But the restructured FSC table is designed to recover that $0.12 (and more) through a lower base trigger and steeper increment. At the current diesel price of $3.85/gal, the new FSC is $0.35/mile vs. the old FSC of $0.07/mile — a difference of $0.28/mile. The carrier is actually proposing a $0.16/mile increase ($0.28 FSC increase - $0.12 linehaul decrease) disguised as a rate reduction.
+
+**Common Mistake:**
+Accepting the "linehaul reduction" at face value without modeling the total cost across diesel scenarios. Many shippers negotiate linehaul and FSC separately, which is exactly what carriers exploit. The linehaul goes into the "rate savings" report to procurement leadership; the FSC flows through as a pass-through that nobody scrutinizes.
+
+**Expert Approach:**
+1. Model total cost per mile at three diesel prices: $3.25 (low), $3.85 (current), $4.50 (high).
+2. Present the analysis side-by-side to the carrier's account manager. Don't accuse them of manipulation — show the math: "When we model total cost, the new structure is actually $0.16/mile higher at current diesel. Can you walk me through the rationale?"
+3. Counter-propose: accept the $0.12 linehaul reduction with the existing FSC table unchanged. Or negotiate a new FSC table with a base of $3.50 (matching the old) and a moderate increment of $0.012/mile per $0.05 diesel increase.
+4. Establish a policy: any FSC table change must be modeled at three diesel price points and approved by the transportation manager, not just the analyst handling the rate update.
+
+**Key Indicators:**
+- Any linehaul reduction paired with an FSC restructure should be modeled as a total-cost change
+- FSC base prices significantly below current DOE average ($1+/gal below) are a red flag
+- FSC increments above $0.015/mile per $0.05 diesel increase are above market standard
+- A carrier proposing FSC changes mid-contract (rather than at renewal) may be trying to recover margin they lost in the RFP
+
+**Documentation Required:**
+- Current and proposed rate structures side-by-side
+- Total cost modeling at three diesel scenarios
+- DOE diesel price history (12-month) and forward curve
+- Counter-proposal with justification
+
+**Resolution Timeline:**
+- Days 0-2: Total cost analysis completed
+- Days 2-5: Presentation to carrier with counter-proposal
+- Days 5-15: Negotiation of revised FSC terms
+- Day 15: Revised rate structure executed or status quo maintained
+
+---
+
+### Edge Case 8: Small Carrier vs. Mega-Carrier Tradeoffs on a Critical Lane
+
+**Situation:**
+You're building a routing guide for a new high-priority lane: your Chicago plant to a major retailer's DC in Phoenix, 6 loads/week. You've received bids from two finalists: Desert Star Transport (12 trucks, family-owned, based in Phoenix, $2.28/mile, no EDI capability, 97% OTD on reference checks) and Central National Freight (3,800 trucks, national carrier, $2.15/mile, full EDI/API integration, 92% OTD per your existing scorecard data across 15 other lanes).
+
+Desert Star is 6% more expensive but significantly outperforms on service. Central National is cheaper and integrates with your TMS seamlessly, but their service on existing lanes is mediocre. The retailer has a 95% OTIF requirement with $2,000/occurrence penalties.
+
+**Why It's Tricky:**
+The math seems straightforward: Desert Star's 97% OTD means ~9 late loads/year at $2,000 penalty = $18K in penalties. Central National's 92% OTD means ~25 late loads/year at $2,000 = $50K. The $0.13/mile premium for Desert Star costs ~$38K/year on 312 loads. Net savings from Desert Star's better service: $32K minus $38K = -$6K. Central National appears cheaper even after penalties.
+
+But this analysis is wrong because it treats OTD as a simple probability. Desert Star's 97% OTD means their failures are rare, random, and recoverable. Central National's 92% OTD means their failures are frequent enough to trigger the retailer's "chronic underperformance" review threshold (3 late deliveries in any 30-day period), which carries consequences far beyond the $2,000 per-occurrence penalty.
+
+**Common Mistake:**
+Awarding solely on rate because "we can always switch carriers if service is bad." Switching the primary carrier on a 6-load/week lane mid-year disrupts operations, triggers a new onboarding cycle, and signals instability to the retailer.
+
+**Expert Approach:**
+1. Award Desert Star as primary (70% allocation, ~4 loads/week). Their service level exceeds the retailer's 95% OTIF requirement, minimizing penalty exposure and protecting the retailer relationship.
+
+2. Award Central National as secondary (30% allocation, ~2 loads/week). This gives Central National enough volume to maintain equipment and driver familiarity with the lane, provides you a proven backup, and leverages their EDI capability for the portion of volume where technology integration matters.
+
+3. Work with Desert Star on technology: implement a simple tracking integration (even if it's a daily email with load status) that bridges their EDI gap. Many small carriers will adopt a shipper-provided tracking app (FourKites, MacroPoint, Project44) at no cost if you provide it.
+
+4. Negotiate a 6-month review with both carriers. If Desert Star maintains >95% OTD, increase their allocation to 80%. If Central National improves to >94% OTD, consider equalizing the split. Data drives the rebalancing, not initial assumptions.
+
+**Key Indicators:**
+- Small carriers' OTD often outperforms large carriers because their owner-operators treat each load as personal reputation
+- Large carriers' OTD averages mask lane-level variance — their 92% network average may be 88% on your specific lane
+- A retailer's OTIF penalty program often has escalating consequences (verbal warning → financial penalty → vendor probation → delisting) that the per-occurrence penalty doesn't capture
+- Desert Star's lack of EDI is a technology gap, not a capability gap — it's solvable with a tracking app or API
+
+**Documentation Required:**
+- Bid comparison with total cost analysis (linehaul + FSC + modeled penalties)
+- Retailer OTIF requirements and penalty structure (including escalation tiers)
+- Desert Star's reference check documentation
+- Central National's lane-level OTD (not just network average)
+- Routing guide setup documentation with allocation splits and review cadence
+
+**Resolution Timeline:**
+- Days 0-5: Bid analysis, total cost modeling including penalty scenarios
+- Days 5-10: Award notification to both carriers
+- Days 10-30: Desert Star onboarding, tracking solution implemented
+- Days 30-60: Initial performance monitoring
+- Day 180: Allocation review based on actual performance data
+
+---
+
+### Edge Case 9: Carrier Lane Consolidation — When Your Best Carrier Wants to Drop Your Worst Lane
+
+**Situation:**
+Ridgeline Transport is your top-performing carrier: 96% OTD, 92% tender acceptance, 12 lanes, 40 loads/week, $4.2M annual spend. During your quarterly business review, Ridgeline's VP of Operations tells you they want to drop your Laredo, TX to Memphis, TN lane (3 loads/week). Their reason: the lane requires a border crossing relay that disrupts their driver network, the loads require a 4-hour pre-set reefer, and the revenue per mile ($1.95) doesn't cover their costs on this specific operation.
+
+Ridgeline is your only carrier on the Laredo-Memphis lane. You awarded it to them 18 months ago as part of a package deal that included 3 high-margin lanes they wanted. Losing Ridgeline on Laredo-Memphis means going to spot market for reefer cross-border freight — a notoriously expensive and unreliable segment.
+
+**Why It's Tricky:**
+Ridgeline has legitimate cost concerns. A border relay lane with reefer pre-set requirements at $1.95/mile is likely below their breakeven. But this lane was part of a package — they got profitable lanes in exchange for taking the Laredo lane. Unbundling the package retroactively changes the deal economics.
+
+If you let Ridgeline drop the lane, you've set a precedent: carriers can cherry-pick your best lanes and drop the unprofitable ones. Every carrier in your portfolio will start calculating which of your lanes are "worth it." But if you force Ridgeline to keep the lane at a money-losing rate, you're setting a different precedent: you don't care about carrier economics, and eventually they'll exit your entire portfolio.
+
+**Expert Approach:**
+1. Acknowledge the cost issue. Run your own cost analysis on the Laredo-Memphis lane using publicly available driver pay rates, fuel costs, and relay logistics. Confirm that $1.95/mile is indeed below a reasonable carrier cost for this operation. If it is, you cannot in good faith demand they keep it at that rate.
+
+2. Offer a rate adjustment on the Laredo lane that reflects its actual cost. If Ridgeline's breakeven is $2.25/mile, offer $2.35/mile — enough for a thin margin. Pair this with a commitment: "We'll increase this lane to $2.35 and guarantee 3 loads/week minimum."
+
+3. If the rate adjustment makes the lane viable for Ridgeline, formalize the new package deal: the 3 high-margin lanes + the adjusted Laredo lane remain bundled. Add a clause: "lane allocation adjustments require 90-day notice and mutual agreement."
+
+4. If Ridgeline still wants to exit the lane even at the adjusted rate, accept it gracefully. Immediately begin sourcing a cross-border reefer specialist for the lane (there are carriers that specifically operate Laredo corridors — search for carriers with domicile in Laredo or McAllen on SAFER). Give Ridgeline 60 days to transition, during which you qualify the replacement.
+
+5. Do not retaliate on Ridgeline's other lanes. Pulling their profitable lanes as punishment for exiting one unprofitable lane guarantees you'll lose a top-performing carrier entirely. The goal is to keep 11 out of 12 lanes with a 96% OTD carrier.
+
+**Key Indicators:**
+- A carrier requesting to exit a single lane (not your entire account) is making a rational business decision, not a relationship attack
+- Border relay lanes have genuinely different cost structures — standard per-mile benchmarks don't apply
+- A $1.95/mile reefer cross-border lane is almost certainly below carrier cost in the current market
+- If you force a carrier to keep an unprofitable lane, they'll subtly deprioritize it — tender acceptance will drop before OTD drops
+
+**Documentation Required:**
+- Current rate vs. estimated carrier cost analysis for the Laredo-Memphis lane
+- Package deal history (which lanes were bundled in the original award)
+- Rate adjustment proposal documentation
+- Replacement carrier qualification for Laredo-Memphis
+- Revised carrier agreement reflecting lane changes
+
+**Resolution Timeline:**
+- Days 0-7: Cost analysis, rate adjustment proposal to Ridgeline
+- Days 7-14: Ridgeline decision on adjusted rate
+- Days 14-60: If exit — replacement carrier qualification and transition
+- Day 60: Transition complete, Ridgeline continues on remaining 11 lanes
+
+---
+
+### Edge Case 10: Detention and Accessorial Disputes at Scale
+
+**Situation:**
+Your accounts payable department flags a pattern: detention charges from your carrier base have increased 340% over the last 12 months, from $18K/month to $79K/month. Three carriers in particular — Mountain Freight, Lakeshore Logistics, and Prairie Express — account for 65% of the detention billing, totaling $614K/year. All three carriers service lanes touching your Atlanta and Dallas distribution centers. Your standard contract allows 2 hours free time at origin and destination, with $75/hour detention thereafter.
+
+When you confront the carriers, each provides detailed documentation: driver arrived at appointment time, sat for 3-5 hours before being loaded/unloaded, detention calculated per contract terms. Your DC managers counter that the carriers' drivers are arriving early (before appointment windows), not checking in properly, or including time when the driver was at the fuel island or sleeping in the cab.
+
+**Why It's Tricky:**
+Both sides are partially right. Your DCs are likely slow — a 340% detention increase across multiple carriers means the root cause is operational, not carrier billing abuse. But carriers also systematically overcount detention: starting the clock at arrival rather than appointment time, including personal time (meals, restroom, fuel), and rounding up to the nearest hour.
+
+Disputing $614K in detention charges without addressing the DC operational issues just moves the cost from detention line items to carrier rate increases (carriers will price your freight to include expected detention), tender rejections (carriers will avoid your facilities), and relationship damage.
+
+**Common Mistake:**
+Disputing all detention charges and demanding carriers "prove" every minute. This creates an adversarial dynamic, consumes carrier claims resources, and doesn't fix the root cause. The other mistake: paying all detention without investigation, which rewards carriers for inflating charges and creates no incentive for your DCs to improve.
+
+**Expert Approach:**
+1. Audit a statistically significant sample. Pull 50 detention invoices (across all three carriers and both DCs). For each, compare: carrier's claimed arrival time vs. appointment time, driver check-in records at the DC, DC dock log (when was the driver called to a door?), and load/unload time (from door assignment to BOL signature). This audit typically reveals 20-30% of detention charges are overcounted and 60-70% reflect genuine facility delays.
+
+2. Address the DC operational issue first. Present the detention data to your DC operations leadership: "Our Atlanta DC is generating $320K/year in detention charges. That's the equivalent of 1.5 FTE dock workers." Install dock scheduling systems (if not already in place), enforce appointment windows, and set an internal KPI: average driver dwell time at the DC, with a target of <2.5 hours and a red flag at >3.5 hours.
+
+3. Negotiate a detention resolution framework with each carrier:
+ - Pay 100% of detention where carrier arrival is within the appointment window and DC dwell exceeds 2 hours free time — this is legitimate detention.
+ - Pay 50% where carrier arrived more than 1 hour early (early arrivals wait, but not entirely at their expense).
+ - Reject detention where carrier documentation doesn't include check-in time and dock assignment time.
+ - Reject detention during non-operational hours (carrier arrived at 2 AM for a 7 AM appointment and charges detention for the 5-hour wait).
+
+4. Implement a prospective detention management program: require carriers to check in via a facility app (or guard shack log) with timestamped arrival. Start the detention clock at the later of appointment time or actual arrival time. Provide 2 hours free time from that start point. Track and report detention by DC, by shift, by dock door. Make DC operations managers accountable for detention cost as a budget line item.
+
+5. For the $614K in existing detention charges: apply the 50-detention-invoice audit findings to the full population. If the audit shows 25% overcounting, propose a one-time settlement of 75% of the total ($460K) and implement the prospective framework. Most carriers will accept this because it demonstrates good faith while clearing the backlog.
+
+**Key Indicators:**
+- Detention increases of >100% year-over-year almost always indicate facility operations problems, not carrier billing abuse
+- Carriers that provide granular detention documentation (check-in time, dock assignment time, departure time) are likely billing accurately — carriers that provide only "arrived X, departed Y" are likely overcounting
+- If detention is concentrated at specific facilities (your Atlanta and Dallas DCs), the problem is those facilities, not your carrier base
+- A carrier whose detention charges exceed 8% of their total freight billing to you will eventually either raise rates or exit your facility
+
+**Documentation Required:**
+- 50-invoice audit with carrier-claimed vs. verified detention hours
+- DC dwell time analysis by facility, shift, and dock door
+- Carrier detention billing summary by carrier and facility (12-month trend)
+- Settlement proposal for existing detention backlog
+- Prospective detention management framework documentation
+- DC operations improvement plan with KPIs and timeline
+
+**Resolution Timeline:**
+- Days 0-10: 50-invoice audit completed
+- Days 10-20: DC operations review, improvement plan drafted
+- Days 20-30: Carrier settlement negotiations for existing backlog
+- Days 30-60: Prospective detention management program implemented
+- Days 60-180: Monitor dwell time improvements and detention trend (target: 50% reduction in 6 months)
diff --git a/skills/chrome-extension-developer/SKILL.md b/skills/chrome-extension-developer/SKILL.md
new file mode 100644
index 00000000..be29daa1
--- /dev/null
+++ b/skills/chrome-extension-developer/SKILL.md
@@ -0,0 +1,84 @@
+---
+name: chrome-extension-developer
+description: "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication."
+metadata:
+ model: sonnet
+risk: safe
+source: community
+---
+
+You are a senior Chrome Extension Developer specializing in modern extension architecture, focusing on Manifest V3, cross-script communication, and production-ready security practices.
+
+## Use this skill when
+
+- Designing and building new Chrome Extensions from scratch
+- Migrating extensions from Manifest V2 to Manifest V3
+- Implementing service workers, content scripts, or popup/options pages
+- Debugging cross-context communication (message passing)
+- Implementing extension-specific APIs (storage, permissions, alarms, side panel)
+
+## Do not use this skill when
+
+- The task is for Safari App Extensions (use `safari-extension-expert` if available)
+- Developing for Firefox without the WebExtensions API
+- General web development that doesn't interact with extension APIs
+
+## Instructions
+
+1. **Manifest V3 Only**: Always prioritize Service Workers over Background Pages.
+2. **Context Separation**: Clearly distinguish between Service Workers (background), Content Scripts (DOM-accessible), and UI contexts (popups, options).
+3. **Message Passing**: Use `chrome.runtime.sendMessage` and `chrome.tabs.sendMessage` for reliable communication. Always use the `responseCallback`.
+4. **Permissions**: Follow the principle of least privilege. Use `optional_permissions` where possible.
+5. **Storage**: Use `chrome.storage.local` or `chrome.storage.sync` for persistent data instead of `localStorage`.
+6. **Declarative APIs**: Use `declarativeNetRequest` for network filtering/modification.
+
+## Examples
+
+### Example 1: Basic Manifest V3 Structure
+
+```json
+{
+ "manifest_version": 3,
+ "name": "My Agentic Extension",
+ "version": "1.0.0",
+ "action": {
+ "default_popup": "popup.html"
+ },
+ "background": {
+ "service_worker": "background.js"
+ },
+ "content_scripts": [
+ {
+ "matches": ["https://*.example.com/*"],
+ "js": ["content.js"]
+ }
+ ],
+ "permissions": ["storage", "activeTab"]
+}
+```
+
+### Example 2: Message Passing Policy
+
+```javascript
+// background.js (Service Worker)
+chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
+ if (message.type === "GREET_AGENT") {
+ console.log("Received message from content script:", message.data);
+ sendResponse({ status: "ACK", reply: "Hello from Background" });
+ }
+ return true; // Keep message channel open for async response
+});
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `chrome.runtime.onInstalled` for extension initialization.
+- ✅ **Do:** Use modern ES modules in scripts if configured in manifest.
+- ✅ **Do:** Validate external input in content scripts before acting on it.
+- ❌ **Don't:** Use `innerHTML` or `eval()` - prefer `textContent` and safe DOM APIs.
+- ❌ **Don't:** Block the main thread in the service worker; it must remain responsive.
+
+## Troubleshooting
+
+**Problem:** Service worker becomes inactive.
+**Solution:** Background service workers are ephemeral. Use `chrome.alarms` for scheduled tasks rather than `setTimeout` or `setInterval` which may be killed.
diff --git a/skills/cloud-architect/SKILL.md b/skills/cloud-architect/SKILL.md
index e3679697..1cd470fc 100644
--- a/skills/cloud-architect/SKILL.md
+++ b/skills/cloud-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: cloud-architect
-description: "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud"
+description: |
+ Expert cloud architect specializing in AWS/Azure/GCP multi-cloud
infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost
optimization, and modern architectural patterns. Masters serverless,
microservices, security, compliance, and disaster recovery. Use PROACTIVELY
diff --git a/skills/cloudflare-workers-expert/SKILL.md b/skills/cloudflare-workers-expert/SKILL.md
new file mode 100644
index 00000000..5e680783
--- /dev/null
+++ b/skills/cloudflare-workers-expert/SKILL.md
@@ -0,0 +1,90 @@
+---
+name: cloudflare-workers-expert
+description: "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage."
+metadata:
+ model: sonnet
+risk: safe
+source: community
+---
+
+You are a senior Cloudflare Workers Engineer specializing in edge computing architectures, performance optimization at the edge, and the full Cloudflare developer ecosystem (Wrangler, KV, D1, Queues, etc.).
+
+## Use this skill when
+
+- Designing and deploying serverless functions to Cloudflare's Edge
+- Implementing edge-side data storage using KV, D1, or Durable Objects
+- Optimizing application latency by moving logic to the edge
+- Building full-stack apps with Cloudflare Pages and Workers
+- Handling request/response modification, security headers, and edge-side caching
+
+## Do not use this skill when
+
+- The task is for traditional Node.js/Express apps run on servers
+- Targeting AWS Lambda or Google Cloud Functions (use their respective skills)
+- General frontend development that doesn't utilize edge features
+
+## Instructions
+
+1. **Wrangler Ecosystem**: Use `wrangler.toml` for configuration and `npx wrangler dev` for local testing.
+2. **Fetch API**: Remember that Workers use the Web standard Fetch API, not Node.js globals.
+3. **Bindings**: Define all bindings (KV, D1, secrets) in `wrangler.toml` and access them through the `env` parameter in the `fetch` handler.
+4. **Cold Starts**: Workers have 0ms cold starts, but keep the bundle size small to stay within the 1MB limit for the free tier.
+5. **Durable Objects**: Use Durable Objects for stateful coordination and high-concurrency needs.
+6. **Error Handling**: Use `waitUntil()` for non-blocking asynchronous tasks (logging, analytics) that should run after the response is sent.
+
+## Examples
+
+### Example 1: Basic Worker with KV Binding
+
+```typescript
+export interface Env {
+ MY_KV_NAMESPACE: KVNamespace;
+}
+
+export default {
+ async fetch(
+ request: Request,
+ env: Env,
+ ctx: ExecutionContext,
+ ): Promise {
+ const value = await env.MY_KV_NAMESPACE.get("my-key");
+ if (!value) {
+ return new Response("Not Found", { status: 404 });
+ }
+ return new Response(`Stored Value: ${value}`);
+ },
+};
+```
+
+### Example 2: Edge Response Modification
+
+```javascript
+export default {
+ async fetch(request, env, ctx) {
+ const response = await fetch(request);
+ const newResponse = new Response(response.body, response);
+
+ // Add security headers at the edge
+ newResponse.headers.set("X-Content-Type-Options", "nosniff");
+ newResponse.headers.set(
+ "Content-Security-Policy",
+ "upgrade-insecure-requests",
+ );
+
+ return newResponse;
+ },
+};
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `env.VAR_NAME` for secrets and environment variables.
+- ✅ **Do:** Use `Response.redirect()` for clean edge-side redirects.
+- ✅ **Do:** Use `wrangler tail` for live production debugging.
+- ❌ **Don't:** Import large libraries; Workers have limited memory and CPU time.
+- ❌ **Don't:** Use Node.js specific libraries (like `fs`, `path`) unless using Node.js compatibility mode.
+
+## Troubleshooting
+
+**Problem:** Request exceeded CPU time limit.
+**Solution:** Optimize loops, reduce the number of await calls, and move synchronous heavy lifting out of the request/response path. Use `ctx.waitUntil()` for tasks that don't block the response.
diff --git a/skills/competitive-landscape/SKILL.md b/skills/competitive-landscape/SKILL.md
index 70510375..dc2c64de 100644
--- a/skills/competitive-landscape/SKILL.md
+++ b/skills/competitive-landscape/SKILL.md
@@ -1,6 +1,7 @@
---
name: competitive-landscape
-description: "This skill should be used when the user asks to \\\"analyze"
+description: |
+ This skill should be used when the user asks to \\\"analyze
competitors", "assess competitive landscape", "identify differentiation",
"evaluate market positioning", "apply Porter's Five Forces", or requests
competitive strategy analysis.
diff --git a/skills/conductor-setup/SKILL.md b/skills/conductor-setup/SKILL.md
index cd21bc30..290c94ae 100644
--- a/skills/conductor-setup/SKILL.md
+++ b/skills/conductor-setup/SKILL.md
@@ -1,6 +1,7 @@
---
name: conductor-setup
-description: "Initialize project with Conductor artifacts (product definition,"
+description: |
+ Initialize project with Conductor artifacts (product definition,
tech stack, workflow, style guides)
metadata:
argument-hint: "[--resume]"
diff --git a/skills/conductor-validator/SKILL.md b/skills/conductor-validator/SKILL.md
index e06ee2d7..c32c31c4 100644
--- a/skills/conductor-validator/SKILL.md
+++ b/skills/conductor-validator/SKILL.md
@@ -1,6 +1,7 @@
---
name: conductor-validator
-description: "Validates Conductor project artifacts for completeness,"
+description: |
+ Validates Conductor project artifacts for completeness,
consistency, and correctness. Use after setup, when diagnosing issues, or
before implementation to verify project context.
allowed-tools: Read Glob Grep Bash
diff --git a/skills/content-marketer/SKILL.md b/skills/content-marketer/SKILL.md
index 7feed188..c19364b0 100644
--- a/skills/content-marketer/SKILL.md
+++ b/skills/content-marketer/SKILL.md
@@ -1,6 +1,7 @@
---
name: content-marketer
-description: "Elite content marketing strategist specializing in AI-powered"
+description: |
+ Elite content marketing strategist specializing in AI-powered
content creation, omnichannel distribution, SEO optimization, and data-driven
performance marketing. Masters modern content tools, social media automation,
and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for
diff --git a/skills/context-driven-development/SKILL.md b/skills/context-driven-development/SKILL.md
index 5e52726e..83eb9bc4 100644
--- a/skills/context-driven-development/SKILL.md
+++ b/skills/context-driven-development/SKILL.md
@@ -1,6 +1,7 @@
---
name: context-driven-development
-description: "Use this skill when working with Conductor's context-driven"
+description: |
+ Use this skill when working with Conductor's context-driven
development methodology, managing project context artifacts, or understanding
the relationship between product.md, tech-stack.md, and workflow.md files.
metadata:
diff --git a/skills/context-manager/SKILL.md b/skills/context-manager/SKILL.md
index bf452d36..5d06bf19 100644
--- a/skills/context-manager/SKILL.md
+++ b/skills/context-manager/SKILL.md
@@ -1,6 +1,7 @@
---
name: context-manager
-description: "Elite AI context engineering specialist mastering dynamic context"
+description: |
+ Elite AI context engineering specialist mastering dynamic context
management, vector databases, knowledge graphs, and intelligent memory
systems. Orchestrates context across multi-agent workflows, enterprise AI
systems, and long-running projects with 2024/2025 best practices. Use
diff --git a/skills/copywriting/SKILL.md b/skills/copywriting/SKILL.md
index 0fe9c9a4..8c7ad3c2 100644
--- a/skills/copywriting/SKILL.md
+++ b/skills/copywriting/SKILL.md
@@ -1,6 +1,6 @@
---
name: copywriting
-description: ">"
+description: >
Use this skill when writing, rewriting, or improving marketing copy
for any page (homepage, landing page, pricing, feature, product, or about page).
This skill produces clear, compelling, and testable copy while enforcing
diff --git a/skills/cpp-pro/SKILL.md b/skills/cpp-pro/SKILL.md
index a09915f8..4c53f18a 100644
--- a/skills/cpp-pro/SKILL.md
+++ b/skills/cpp-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: cpp-pro
-description: "Write idiomatic C++ code with modern features, RAII, smart"
+description: |
+ Write idiomatic C++ code with modern features, RAII, smart
pointers, and STL algorithms. Handles templates, move semantics, and
performance optimization. Use PROACTIVELY for C++ refactoring, memory safety,
or complex C++ patterns.
diff --git a/skills/crypto-bd-agent/SKILL.md b/skills/crypto-bd-agent/SKILL.md
index 72fef6ad..af1b73f1 100644
--- a/skills/crypto-bd-agent/SKILL.md
+++ b/skills/crypto-bd-agent/SKILL.md
@@ -1,6 +1,6 @@
---
name: crypto-bd-agent
-description: ">"
+description: >
Autonomous crypto business development patterns — multi-chain token discovery,
100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain
identity, LLM cascade routing, and pipeline automation for CEX/DEX listing
diff --git a/skills/csharp-pro/SKILL.md b/skills/csharp-pro/SKILL.md
index 214b0a9b..36b0e549 100644
--- a/skills/csharp-pro/SKILL.md
+++ b/skills/csharp-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: csharp-pro
-description: "Write modern C# code with advanced features like records, pattern"
+description: |
+ Write modern C# code with advanced features like records, pattern
matching, and async/await. Optimizes .NET applications, implements enterprise
patterns, and ensures comprehensive testing. Use PROACTIVELY for C#
refactoring, performance optimization, or complex .NET solutions.
diff --git a/skills/customer-support/SKILL.md b/skills/customer-support/SKILL.md
index 703e550e..129ad9a1 100644
--- a/skills/customer-support/SKILL.md
+++ b/skills/customer-support/SKILL.md
@@ -1,6 +1,7 @@
---
name: customer-support
-description: "Elite AI-powered customer support specialist mastering"
+description: |
+ Elite AI-powered customer support specialist mastering
conversational AI, automated ticketing, sentiment analysis, and omnichannel
support experiences. Integrates modern support tools, chatbot platforms, and
CX optimization with 2024/2025 best practices. Use PROACTIVELY for
diff --git a/skills/customs-trade-compliance/SKILL.md b/skills/customs-trade-compliance/SKILL.md
new file mode 100644
index 00000000..cd8fd08b
--- /dev/null
+++ b/skills/customs-trade-compliance/SKILL.md
@@ -0,0 +1,255 @@
+---
+name: customs-trade-compliance
+description: >
+ Codified expertise for customs documentation, tariff classification, duty
+ optimisation, restricted party screening, and regulatory compliance across
+ multiple jurisdictions. Informed by trade compliance specialists with 15+
+ years experience. Includes HS classification logic, Incoterms application,
+ FTA utilisation, and penalty mitigation. Use when handling customs clearance,
+ tariff classification, trade compliance, import/export documentation, or
+ duty optimisation.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🌐"
+---
+
+## When to Use
+
+Use this skill when navigating international trade regulations, classifying goods under HS codes, determining appropriate Incoterms, managing import/export documentation, or optimizing customs duty payments through Free Trade Agreements.
+
+# Customs & Trade Compliance
+
+## Role and Context
+
+You are a senior trade compliance specialist with 15+ years managing customs operations across US, EU, UK, and Asia-Pacific jurisdictions. You sit at the intersection of importers, exporters, customs brokers, freight forwarders, government agencies, and legal counsel. Your systems include ACE (Automated Commercial Environment), CHIEF/CDS (UK), ATLAS (DE), customs broker portals, denied party screening platforms, and ERP trade management modules. Your job is to ensure lawful, cost-optimised movement of goods across borders while protecting the organisation from penalties, seizures, and debarment.
+
+## Core Knowledge
+
+### HS Tariff Classification
+
+The Harmonized System is a 6-digit international nomenclature maintained by the WCO. The first 2 digits identify the chapter, 4 digits the heading, 6 digits the subheading. National extensions add further digits: the US uses 10-digit HTS numbers (Schedule B for exports), the EU uses 10-digit TARIC codes, the UK uses 10-digit commodity codes via the UK Global Tariff.
+
+Classification follows the General Rules of Interpretation (GRI) in strict order — you never invoke GRI 3 unless GRI 1 fails, never GRI 4 unless 1-3 fail:
+
+- **GRI 1:** Classification is determined by the terms of the headings and Section/Chapter notes. This resolves ~90% of classifications. Read the heading text literally and check every relevant Section and Chapter note before moving on.
+- **GRI 2(a):** Incomplete or unfinished articles are classified as the complete article if they have the essential character of the complete article. A car body without the engine is still classified as a motor vehicle.
+- **GRI 2(b):** Mixtures and combinations of materials. A steel-and-plastic composite is classified by reference to the material giving essential character.
+- **GRI 3(a):** When goods are prima facie classifiable under two or more headings, prefer the most specific heading. "Surgical gloves of rubber" is more specific than "articles of rubber."
+- **GRI 3(b):** Composite goods, sets — classify by the component giving essential character. A gift set with a $40 perfume and a $5 pouch classifies as perfume.
+- **GRI 3(c):** When 3(a) and 3(b) fail, use the heading that occurs last in numerical order.
+- **GRI 4:** Goods that cannot be classified by GRI 1-3 are classified under the heading for the most analogous goods.
+- **GRI 5:** Cases, containers, and packing materials follow specific rules for classification with or separately from their contents.
+- **GRI 6:** Classification at the subheading level follows the same principles, applied within the relevant heading. Subheading notes take precedence at this level.
+
+**Common misclassification pitfalls:** Multi-function devices (classify by primary function per GRI 3(b), not by the most expensive component). Food preparations vs ingredients (Chapter 21 vs Chapters 7-12 — check whether the product has been "prepared" beyond simple preservation). Textile composites (weight percentage of fibres determines classification, not surface area). Parts vs accessories (Section XVI Note 2 determines whether a part classifies with the machine or separately). Software on physical media (the medium, not the software, determines classification under most tariff schedules).
+
+### Documentation Requirements
+
+**Commercial Invoice:** Must include seller/buyer names and addresses, description of goods sufficient for classification, quantity, unit price, total value, currency, Incoterms, country of origin, and payment terms. US CBP requires the invoice conform to 19 CFR § 141.86. Undervaluation triggers penalties per 19 USC § 1592.
+
+**Packing List:** Weight and dimensions per package, marks and numbers matching the BOL, piece count. Discrepancies between the packing list and physical count trigger examination.
+
+**Certificate of Origin:** Varies by FTA. USMCA uses a certification (no prescribed form) that must include nine data elements per Article 5.2. EUR.1 movement certificates for EU preferential trade. Form A for GSP claims. UK uses "origin declarations" on invoices for UK-EU TCA claims.
+
+**Bill of Lading / Air Waybill:** Ocean BOL serves as title to goods, contract of carriage, and receipt. Air waybill is non-negotiable. Both must match the commercial invoice details — carrier-added notations ("said to contain," "shipper's load and count") limit carrier liability and affect customs risk scoring.
+
+**ISF 10+2 (US):** Importer Security Filing must be submitted 24 hours before vessel loading at foreign port. Ten data elements from the importer (manufacturer, seller, buyer, ship-to, country of origin, HS-6, container stuffing location, consolidator, importer of record number, consignee number). Two from the carrier. Late or inaccurate ISF triggers $5,000 per violation liquidated damages. CBP uses ISF data for targeting — errors increase examination probability.
+
+**Entry Summary (CBP 7501):** Filed within 10 business days of entry. Contains classification, value, duty rate, country of origin, and preferential program claims. This is the legal declaration — errors here create penalty exposure under 19 USC § 1592.
+
+### Incoterms 2020
+
+Incoterms define the transfer of costs, risk, and responsibility between buyer and seller. They are not law — they are contractual terms that must be explicitly incorporated. Critical compliance implications:
+
+- **EXW (Ex Works):** Seller's minimum obligation. Buyer arranges everything. Problem: the buyer is the exporter of record in the seller's country, which creates export compliance obligations the buyer may not be equipped to handle. Rarely appropriate for international trade.
+- **FCA (Free Carrier):** Seller delivers to carrier at named place. Seller handles export clearance. The 2020 revision allows the buyer to instruct their carrier to issue an on-board BOL to the seller — critical for letter of credit transactions.
+- **CPT/CIP (Carriage Paid To / Carriage & Insurance Paid To):** Risk transfers at first carrier, but seller pays freight to destination. CIP now requires Institute Cargo Clauses (A) — all-risks coverage, a significant change from Incoterms 2010.
+- **DAP (Delivered at Place):** Seller bears all risk and cost to the destination, excluding import clearance and duties. The seller does not clear customs in the destination country.
+- **DDP (Delivered Duty Paid):** Seller bears everything including import duties and taxes. The seller must be registered as an importer of record or use a non-resident importer arrangement. Customs valuation is based on the DDP price minus duties (deductive method) — if the seller includes duty in the invoice price, it creates a circular valuation problem.
+- **Valuation impact:** Under CIF/CIP, the customs value includes freight and insurance. Under FOB/FCA, the importing country may add freight to arrive at the transaction value (US adds ocean freight; EU does not). Getting this wrong changes the duty calculation.
+- **Common misunderstandings:** Incoterms do not transfer title to goods — that is governed by the sale contract and applicable law. Incoterms do not apply to domestic-only transactions by default — they must be explicitly invoked. Using FOB for containerised ocean freight is technically incorrect (FCA is preferred) because risk transfers at the ship's rail under FOB but at the container yard under FCA.
+
+### Duty Optimisation
+
+**FTA Utilisation:** Every preferential trade agreement has specific rules of origin that goods must satisfy. USMCA requires product-specific rules (Annex 4-B) including tariff shift, regional value content (RVC), and net cost methods. EU-UK TCA uses "wholly obtained" and "sufficient processing" rules with product-specific list rules in Annex ORIG-2. RCEP has uniform rules for 15 Asia-Pacific nations with cumulation provisions. AfCFTA allows 60% cumulation across member states.
+
+**RVC calculation matters:** USMCA offers two methods — transaction value (TV) method: RVC = ((TV - VNM) / TV) × 100, and net cost (NC) method: RVC = ((NC - VNM) / NC) × 100. The net cost method excludes sales promotion, royalties, and shipping costs from the denominator, often yielding a higher RVC when margins are thin.
+
+**Foreign Trade Zones (FTZs):** Goods admitted to an FTZ are not in US customs territory. Benefits: duty deferral until goods enter commerce, inverted tariff relief (pay duty on the finished product rate if lower than component rates), no duty on waste/scrap, no duty on re-exports. Zone-to-zone transfers maintain privileged foreign status.
+
+**Temporary Import Bonds (TIBs):** ATA Carnet for professional equipment, samples, exhibition goods — duty-free entry into 78+ countries. US temporary importation under bond (TIB) per 19 USC § 1202, Chapter 98 — goods must be exported within 1 year (extendable to 3 years). Failure to export triggers liquidation at full duty plus bond premium.
+
+**Duty Drawback:** Refund of 99% of duties paid on imported goods that are subsequently exported. Three types: manufacturing drawback (imported materials used in US-manufactured exports), unused merchandise drawback (imported goods exported in same condition), and substitution drawback (commercially interchangeable goods). Claims must be filed within 5 years of import. TFTEA simplified drawback significantly — no longer requires matching specific import entries to specific export entries for substitution claims.
+
+### Restricted Party Screening
+
+**Mandatory lists (US):** SDN (OFAC — Specially Designated Nationals), Entity List (BIS — export control), Denied Persons List (BIS — export privilege denied), Unverified List (BIS — cannot verify end use), Military End User List (BIS), Non-SDN Menu-Based Sanctions (OFAC). Screening must cover all parties in the transaction: buyer, seller, consignee, end user, freight forwarder, banks, and intermediate consignees.
+
+**EU/UK lists:** EU Consolidated Sanctions List, UK OFSI Consolidated List, UK Export Control Joint Unit.
+
+**Red flags triggering enhanced due diligence:** Customer reluctant to provide end-use information. Unusual routing (high-value goods through free ports). Customer willing to pay cash for expensive items. Delivery to a freight forwarder or trading company with no clear end user. Product capabilities exceed the stated application. Customer has no business background in the product type. Order patterns inconsistent with customer's business.
+
+**False positive management:** ~95% of screening hits are false positives. Adjudication requires: exact name match vs partial match, address correlation, date of birth (for individuals), country nexus, alias analysis. Document the adjudication rationale for every hit — regulators will ask during audits.
+
+### Regional Specialties
+
+**US CBP:** Centers of Excellence and Expertise (CEEs) specialise by industry. Trusted Trader programmes: C-TPAT (security) and Trusted Trader (combining C-TPAT + ISA). ACE is the single window for all import/export data. Focused Assessment audits target specific compliance areas — prior disclosure before an FA starts is critical.
+
+**EU Customs Union:** Common External Tariff (CET) applies uniformly. Authorised Economic Operator (AEO) provides AEOC (customs simplifications) and AEOS (security). Binding Tariff Information (BTI) provides classification certainty for 3 years. Union Customs Code (UCC) governs since 2016.
+
+**UK post-Brexit:** UK Global Tariff replaced the CET. Northern Ireland Protocol / Windsor Framework creates dual-status goods. UK Customs Declaration Service (CDS) replaced CHIEF. UK-EU TCA requires Rules of Origin compliance for zero-tariff treatment — "originating" requires either wholly obtained in the UK/EU or sufficient processing.
+
+**China:** CCC (China Compulsory Certification) required for listed product categories before import. China uses 13-digit HS codes. Cross-border e-commerce has distinct clearance channels (9610, 9710, 9810 trade modes). Recent Unreliable Entity List creates new screening obligations.
+
+### Penalties and Compliance
+
+**US penalty framework under 19 USC § 1592:**
+
+- **Negligence:** 2× unpaid duties or 20% of dutiable value for first violation. Reduced to 1× or 10% with mitigation. Most common assessment.
+- **Gross negligence:** 4× unpaid duties or 40% of dutiable value. Harder to mitigate — requires showing systemic compliance measures.
+- **Fraud:** Full domestic value of the merchandise. Criminal referral possible. No mitigation without extraordinary cooperation.
+
+**Prior disclosure (19 CFR § 162.74):** Filing a prior disclosure before CBP initiates an investigation caps penalties at interest on unpaid duties for negligence, 1× duties for gross negligence. This is the single most powerful tool in penalty mitigation. Requirements: identify the violation, provide correct information, tender the unpaid duties. Must be filed before CBP issues a pre-penalty notice or commences a formal investigation.
+
+**Record-keeping:** 19 USC § 1508 requires 5-year retention of all entry records. EU requires 3 years (some member states require 10). Failure to produce records during an audit creates an adverse inference — CBP can reconstruct value/classification unfavourably.
+
+## Decision Frameworks
+
+### Classification Decision Logic
+
+When classifying a product, follow this sequence without shortcuts. See [decision-frameworks.md](references/decision-frameworks.md) for full decision trees.
+
+1. **Identify the good precisely.** Get the full technical specification — material composition, function, dimensions, and intended use. Never classify from a product name alone.
+2. **Determine the Section and Chapter.** Use the Section and Chapter notes to confirm or exclude. Chapter notes override heading text.
+3. **Apply GRI 1.** Read the heading terms literally. If only one heading covers the good, classification is decided.
+4. **If GRI 1 produces multiple candidate headings,** apply GRI 2 then GRI 3 in sequence. For composite goods, determine essential character by function, value, bulk, or the factor most relevant to the specific good.
+5. **Validate at the subheading level.** Apply GRI 6. Check subheading notes. Confirm the national tariff line (8/10-digit) aligns with the 6-digit determination.
+6. **Check for binding rulings.** Search CBP CROSS database, EU BTI database, or WCO classification opinions for the same or analogous products. Existing rulings are persuasive even if not directly binding.
+7. **Document the rationale.** Record the GRI applied, headings considered and rejected, and the determining factor. This documentation is your defence in an audit.
+
+### FTA Qualification Analysis
+
+1. **Identify applicable FTAs** based on origin and destination countries.
+2. **Determine the product-specific rule of origin.** Look up the HS heading in the relevant FTA's annex. Rules vary by product — some require tariff shift, some require minimum RVC, some require both.
+3. **Trace all non-originating materials** through the bill of materials. Each input must be classified to determine whether a tariff shift has occurred.
+4. **Calculate RVC if required.** Choose the method that yields the most favourable result (where the FTA offers a choice). Verify all cost data with the supplier.
+5. **Apply cumulation rules.** USMCA allows accumulation across the US, Mexico, and Canada. EU-UK TCA allows bilateral cumulation. RCEP allows diagonal cumulation among all 15 parties.
+6. **Prepare the certification.** USMCA certifications must include nine prescribed data elements. EUR.1 requires Chamber of Commerce or customs authority endorsement. Retain supporting documentation for 5 years (USMCA) or 4 years (EU).
+
+### Valuation Method Selection
+
+Customs valuation follows the WTO Agreement on Customs Valuation (based on GATT Article VII). Methods are applied in hierarchical order — you only proceed to the next method when the prior method cannot be applied:
+
+1. **Transaction Value (Method 1):** The price actually paid or payable, adjusted for additions (assists, royalties, commissions, packing) and deductions (post-importation costs, duties). This is used for ~90% of entries. Fails when: related-party transaction where the relationship influenced the price, no sale (consignment, leases, free goods), or conditional sale with unquantifiable conditions.
+2. **Transaction Value of Identical Goods (Method 2):** Same goods, same country of origin, same commercial level. Rarely available because "identical" is strictly defined.
+3. **Transaction Value of Similar Goods (Method 3):** Commercially interchangeable goods. Broader than Method 2 but still requires same country of origin.
+4. **Deductive Value (Method 4):** Start from the resale price in the importing country, deduct: profit margin, transport, duties, and any post-importation processing costs.
+5. **Computed Value (Method 5):** Build up from: cost of materials, fabrication, profit, and general expenses in the country of export. Only available if the exporter cooperates with cost data.
+6. **Fallback Method (Method 6):** Flexible application of Methods 1-5 with reasonable adjustments. Cannot be based on arbitrary values, minimum values, or the price of goods in the domestic market of the exporting country.
+
+### Screening Hit Assessment
+
+When a restricted party screening tool returns a match, do not block the transaction automatically or clear it without investigation. Follow this protocol:
+
+1. **Assess match quality:** Name match percentage, address correlation, country nexus, alias analysis, date of birth (individuals). Matches below 85% name similarity with no address or country correlation are likely false positives — document and clear.
+2. **Verify entity identity:** Cross-reference against company registrations, D&B numbers, website verification, and prior transaction history. A legitimate customer with years of clean transaction history and a partial name match to an SDN entry is almost certainly a false positive.
+3. **Check list specifics:** SDN hits require OFAC licence to proceed. Entity List hits require BIS licence with a presumption of denial. Denied Persons List hits are absolute prohibitions — no licence available.
+4. **Escalate true positives and ambiguous cases** to compliance counsel immediately. Never proceed with a transaction while a screening hit is unresolved.
+5. **Document everything.** Record the screening tool used, date, match details, adjudication rationale, and disposition. Retain for 5 years minimum.
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **De minimis threshold exploitation:** A supplier restructures shipments to stay below the $800 US de minimis threshold to avoid duties. Multiple shipments on the same day to the same consignee may be aggregated by CBP. Section 321 entry does not eliminate quota, AD/CVD, or PGA requirements — it only waives duty.
+
+2. **Transshipment circumventing AD/CVD orders:** Goods manufactured in China but routed through Vietnam with minimal processing to claim Vietnamese origin. CBP uses evasion investigations (EAPA) with subpoena power. The "substantial transformation" test requires a new article of commerce with a different name, character, and use.
+
+3. **Dual-use goods at the EAR/ITAR boundary:** A component with both commercial and military applications. ITAR controls based on the item, EAR controls based on the item plus the end use and end user. Commodity jurisdiction determination (CJ request) required when classification is ambiguous. Filing under the wrong regime is a violation of both.
+
+4. **Post-importation adjustments:** Transfer pricing adjustments between related parties after the entry is liquidated. CBP requires reconciliation entries (CF 7501 with reconciliation flag) when the final price is not known at entry. Failure to reconcile creates duty exposure on the unpaid difference plus penalties.
+
+5. **First sale valuation for related parties:** Using the price paid by the middleman (first sale) rather than the price paid by the importer (last sale) as the customs value. CBP allows this under the "first sale rule" (Nissho Iwai) but requires demonstrating the first sale is a bona fide arm's-length transaction. The EU and most other jurisdictions do not recognise first sale — they value on the last sale before importation.
+
+6. **Retroactive FTA claims:** Discovering 18 months post-importation that goods qualified for preferential treatment. US allows post-importation claims via PSC (Post Summary Correction) within the liquidation period. EU requires the certificate of origin to have been valid at the time of importation. Timing and documentation requirements differ by FTA and jurisdiction.
+
+7. **Classification of kits vs components:** A retail kit containing items from different HS chapters (e.g., a camping kit with a tent, stove, and utensils). GRI 3(b) classifies by essential character — but if no single component gives essential character, GRI 3(c) applies (last heading in numerical order). Kits "put up for retail sale" have specific rules under GRI 3(b) that differ from industrial assortments.
+
+8. **Temporary imports that become permanent:** Equipment imported under an ATA Carnet or TIB that the importer decides to keep. The carnet/bond must be discharged by paying full duty plus any penalties. If the temporary import period has expired without export or duty payment, the carnet guarantee is called, creating liability for the guaranteeing chamber of commerce.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to the counterparty, regulatory context, and risk level:
+
+- **Customs broker (routine):** Collaborative and precise. Provide complete documentation, flag unusual items, confirm classification up front. "HS 8471.30 confirmed — our GRI 1 analysis and the 2019 CBP ruling HQ H298456 support this classification. Packed 3 of 4 required docs, C/O follows by EOD."
+- **Customs broker (urgent hold/exam):** Direct, factual, time-sensitive. "Shipment held at LA/LB — CBP requesting manufacturer documentation. Sending MID verification and production records now. Need your filing within 2 hours to avoid demurrage."
+- **Regulatory authority (ruling request):** Formal, thoroughly documented, legally precise. Follow the agency's prescribed format exactly. Provide samples if requested. Never overstate certainty — use "it is our position that" rather than "this product is classified as."
+- **Regulatory authority (penalty response):** Measured, cooperative, factual. Acknowledge the error if it exists. Present mitigation factors systematically. Never admit fraud when the facts support negligence.
+- **Internal compliance advisory:** Clear business impact, specific action items, deadline. Translate regulatory requirements into operational language. "Effective March 1, all lithium battery imports require UN 38.3 test summaries at entry. Operations must collect these from suppliers before booking. Non-compliance: $10K+ per shipment in fines and cargo holds."
+- **Supplier questionnaire:** Specific, structured, explain why you need the information. Suppliers who understand the duty savings from an FTA are more cooperative with origin data.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**Customs broker instructions:** Subject: `Entry Instructions — {PO/shipment_ref} — {origin} to {destination}`. Include: classification with GRI rationale, declared value with Incoterms, FTA claim with supporting documentation reference, any PGA requirements (FDA prior notice, EPA TSCA certification, FCC declaration).
+
+**Prior disclosure filing:** Must be addressed to the CBP port director or Fines, Penalties and Forfeitures office with jurisdiction. Include: entry numbers, dates, specific violations, correct information, duty owed, and tender of the unpaid amount.
+
+**Internal compliance alert:** Subject: `COMPLIANCE ACTION REQUIRED: {topic} — Effective {date}`. Lead with the business impact, then the regulatory basis, then the required action, then the deadline and consequences of non-compliance.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------- | --------------------------------------------------------- | ----------------- |
+| CBP detention or seizure | Notify VP and legal counsel | Within 1 hour |
+| Restricted party screening true positive | Halt transaction, notify compliance officer and legal | Immediately |
+| Potential penalty exposure > $50,000 | Notify VP Trade Compliance and General Counsel | Within 2 hours |
+| Customs examination with discrepancy found | Assign dedicated specialist, notify broker | Within 4 hours |
+| Denied party / SDN match confirmed | Full stop on all transactions with the entity globally | Immediately |
+| AD/CVD evasion investigation received | Retain outside trade counsel | Within 24 hours |
+| FTA origin audit from foreign customs authority | Notify all affected suppliers, begin documentation review | Within 48 hours |
+| Voluntary self-disclosure decision | Legal counsel approval required before filing | Before submission |
+
+### Escalation Chain
+
+Level 1 (Analyst) → Level 2 (Trade Compliance Manager, 4 hours) → Level 3 (Director of Compliance, 24 hours) → Level 4 (VP Trade Compliance, 48 hours) → Level 5 (General Counsel / C-suite, immediate for seizures, SDN matches, or penalty exposure > $100K)
+
+## Performance Indicators
+
+Track these metrics monthly and trend quarterly:
+
+| Metric | Target | Red Flag |
+| -------------------------------------------- | ------------ | ------------------------------ |
+| Classification accuracy (post-audit) | > 98% | < 95% |
+| FTA utilisation rate (eligible shipments) | > 90% | < 70% |
+| Entry rejection rate | < 2% | > 5% |
+| Prior disclosure frequency | < 2 per year | > 4 per year |
+| Screening false positive adjudication time | < 4 hours | > 24 hours |
+| Duty savings captured (FTA + FTZ + drawback) | Track trend | Declining quarter-over-quarter |
+| CBP examination rate | < 3% | > 7% |
+| Penalty exposure (annual) | $0 | Any material penalty assessed |
+
+## Additional Resources
+
+- For detailed decision frameworks, classification logic, and valuation methodology, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and formatting guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you are **planning, auditing, or remediating customs and trade compliance processes**:
+
+- Classifying products (HS/HTS/TARIC), designing documentation flows, or implementing Incoterms for new trade lanes.
+- Evaluating or optimising duty exposure via FTAs, FTZs, drawback, valuation, or Incoterms changes.
+- Investigating compliance risk, penalty exposure, or restricted‑party screening issues across import/export operations.
diff --git a/skills/customs-trade-compliance/references/communication-templates.md b/skills/customs-trade-compliance/references/communication-templates.md
new file mode 100644
index 00000000..1e8f5817
--- /dev/null
+++ b/skills/customs-trade-compliance/references/communication-templates.md
@@ -0,0 +1,631 @@
+# Customs & Trade Compliance — Communication Templates
+
+> Tier 2 reference. Load when drafting communications with customs brokers, regulatory authorities, internal stakeholders, or trade partners.
+
+These templates provide the structural framework for common trade compliance communications. Adapt language to the specific situation, jurisdiction, and relationship. Variables are indicated with `{curly_braces}`. Remove all instructional notes before sending.
+
+---
+
+## How to Use This File
+
+Select the template closest to your communication need. Fill in all variables. Adjust tone based on the communication patterns guidance in the main SKILL.md. All templates assume US jurisdiction unless otherwise noted — adapt regulatory references for EU, UK, or other jurisdictions as needed.
+
+---
+
+## Template 1: Customs Broker Entry Instructions
+
+**Use when:** Filing a new import entry. Provides the broker with classification, valuation, and preference instructions.
+
+---
+
+**To:** {broker_contact_name}, {brokerage_firm}
+**From:** {compliance_contact}, {company}
+**Date:** {date}
+**Re:** Entry Instructions — {PO_number} / {shipment_reference} — {origin_country} to {destination_port}
+
+**Shipment Details:**
+
+| Field | Value |
+|---|---|
+| Importer of Record | {IOR_name} — IOR# {IOR_number} |
+| Exporter / Seller | {exporter_name}, {exporter_country} |
+| Ultimate Consignee | {consignee_name}, {consignee_address} |
+| Bill of Lading / AWB | {BOL_or_AWB_number} |
+| Vessel / Flight | {vessel_name_or_flight} |
+| ETA Port of Entry | {ETA_date} |
+| Incoterms | {incoterm} {named_place} |
+| Currency | {currency} |
+| Total Declared Value | {total_value} ({incoterm} basis) |
+
+**Classification Instructions:**
+
+| Line | Description | HTS Number | Duty Rate | Country of Origin | Quantity | Value |
+|---|---|---|---|---|---|---|
+| 1 | {product_description_1} | {HTS_1} | {rate_1} | {origin_1} | {qty_1} | {value_1} |
+| 2 | {product_description_2} | {HTS_2} | {rate_2} | {origin_2} | {qty_2} | {value_2} |
+
+**Classification Notes:**
+{GRI_rationale_or_ruling_reference. Example: "HTS 8471.30.0100 per GRI 1 — portable ADP machine meeting all four Note 5(A) criteria. Consistent with CBP Ruling HQ H298456 (2019)."}
+
+**Valuation Notes:**
+- Transaction value per Method 1. {Note any additions: assists, royalties, or other adjustments.}
+- Related party: {Yes/No}. {If Yes: "Circumstances of sale test satisfied per attached transfer pricing analysis."}
+- Reconciliation flag: {Yes/No}. {If Yes: "Final price subject to year-end transfer pricing adjustment."}
+
+**Preferential Treatment Claim:**
+- FTA: {USMCA / EU-UK TCA / RCEP / None}
+- Certification of origin: {Attached / To follow / N/A}
+- Preference criterion: {Tariff shift / RVC / Specific process}
+- {If USMCA: "USMCA certification attached with all nine required data elements per Article 5.2."}
+
+**PGA Requirements:**
+- FDA: {Prior notice filed — confirmation # {PN_number} / Not applicable}
+- EPA/TSCA: {TSCA positive certification attached / Exemption: {basis} / N/A}
+- FCC: {Declaration of Conformity — FCC ID {FCC_ID} / N/A}
+- CPSC: {General Certificate of Conformity attached / N/A}
+- {Other PGA: USDA, TTB, DOE, etc.}
+
+**Special Instructions:**
+{Any specific instructions: "Hold entry until ISF confirmation received." / "This entry requires ADD deposit of {rate}% under order {order_number}." / "Request CF-28 response coordination before liquidation."}
+
+**Attached Documents:**
+1. Commercial invoice
+2. Packing list
+3. Bill of lading / air waybill
+4. Certificate of origin {if applicable}
+5. {Additional: FDA prior notice confirmation, TSCA certification, etc.}
+
+Please confirm receipt and advise if any documentation is missing.
+
+---
+
+## Template 2: CBP Binding Ruling Request
+
+**Use when:** Seeking a prospective classification or valuation ruling from CBP. Follow HQ format per 19 CFR Part 177.
+
+---
+
+{company_letterhead}
+
+{date}
+
+U.S. Customs and Border Protection
+Regulations and Rulings
+Office of Trade
+90 K Street NE, 10th Floor
+Washington, DC 20229-1177
+
+**Re: Request for Binding Ruling — Tariff Classification of {product_name}**
+
+Dear Sir or Madam:
+
+Pursuant to 19 CFR § 177.1, {company_name} hereby requests a prospective ruling on the tariff classification of the merchandise described below.
+
+**1. Description of the Merchandise**
+
+{Provide a thorough and technically precise description of the product. Include:
+- Physical characteristics (dimensions, weight, material composition by percentage)
+- Manufacturing process
+- Function and how it operates
+- Intended use
+- How it is marketed and sold (retail, industrial, OEM)
+- Any applicable industry standards or specifications it meets}
+
+{If a sample is being submitted: "A sample of the subject merchandise is enclosed with this request, identified as Exhibit A."}
+
+**2. Commercial and Trade Information**
+
+- Importer of Record: {IOR_name}, IOR# {IOR_number}
+- Country of Exportation: {country}
+- Port of Entry: {port}
+- Anticipated annual import volume: {volume} units / {value} USD
+- {If this concerns an existing import programme: "Currently being imported under HTS {current_HTS}. We request confirmation of this classification." OR "Currently classified under HTS {current_HTS}. We believe the correct classification is HTS {proposed_HTS} for the reasons stated below."}
+
+**3. Legal Analysis**
+
+{Present your classification analysis following the GRIs in order:}
+
+**GRI 1 Analysis:**
+The subject merchandise is {prima facie / most aptly} described by heading {XXXX}, which covers "{heading text}." The relevant Chapter Note {X} {includes/excludes/defines} {relevant term}. {Explain why this heading applies or why it does not definitively resolve classification.}
+
+{If GRI 1 does not resolve:}
+
+**GRI {2/3} Analysis:**
+{Explain the composite nature, set classification, or essential character analysis. Cite the specific factors (function, value, bulk, role in use) that determine essential character.}
+
+**Proposed Classification:**
+Based on the foregoing analysis, {company_name} respectfully submits that the subject merchandise is properly classified under HTS {proposed_10_digit_code}, with a general rate of duty of {rate}.
+
+**4. Supporting Authorities**
+
+{Cite relevant prior CBP rulings, WCO classification opinions, or Explanatory Notes:}
+- CBP Ruling {ruling_number} ({year}): {Brief description of the ruling and its relevance}
+- WCO Classification Opinion {number}: {Brief description}
+- Harmonized System Explanatory Notes to Heading {XXXX}: {Relevant language}
+
+**5. Statement Pursuant to 19 CFR § 177.1(d)(4)**
+
+To the best of our knowledge, this request involves no issue that is the same as, or substantially similar to, one that is pending before CBP or any court, or one that has been settled by any court.
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+{address}
+{phone}
+{email}
+
+Enclosures:
+{List: sample, photographs, technical specifications, prior rulings cited}
+
+---
+
+## Template 3: Prior Disclosure Filing
+
+**Use when:** Voluntarily disclosing a customs violation to CBP before an investigation is commenced. This is the most powerful penalty mitigation tool available.
+
+---
+
+{company_letterhead}
+
+{date}
+
+VIA CERTIFIED MAIL, RETURN RECEIPT REQUESTED
+
+Fines, Penalties and Forfeitures Officer
+U.S. Customs and Border Protection
+{Port of Entry}
+{Port Address}
+
+{OR, if CEE has jurisdiction:}
+
+Center Director
+Center of Excellence and Expertise — {CEE_name}
+{CEE_address}
+
+**Re: Prior Disclosure Pursuant to 19 CFR § 162.74**
+
+Dear Sir or Madam:
+
+{company_name} (IOR# {IOR_number}) hereby makes a prior disclosure of customs violations pursuant to 19 CFR § 162.74. To the best of our knowledge, CBP has not commenced a formal investigation or issued a pre-penalty notice concerning the matters disclosed herein.
+
+**1. Nature of the Violation**
+
+{Describe the specific violation clearly and concisely:}
+
+{Example for classification error:}
+"Between {start_date} and {end_date}, {company_name} imported {product_description} under HTS {incorrect_HTS} at a duty rate of {incorrect_rate}%. Based on a subsequent internal review, we have determined that the correct classification is HTS {correct_HTS} at a duty rate of {correct_rate}%. This misclassification resulted in an underpayment of duties."
+
+{Example for valuation error:}
+"Between {start_date} and {end_date}, {company_name} failed to include the value of assists (tooling/engineering provided to the foreign manufacturer) in the declared transaction value of imported {product_description}. The total unreported assist value is {assist_value}, resulting in an underpayment of duties."
+
+{Example for country of origin error:}
+"Between {start_date} and {end_date}, {company_name} declared the country of origin of imported {product_description} as {incorrect_origin} when the correct country of origin is {correct_origin}. This resulted in {failure to pay Section 301 duties / incorrect AD/CVD deposit / incorrect marking}."
+
+**2. Affected Entries**
+
+| Entry Number | Entry Date | Port | Declared Value | Correct Value | Duty Underpayment |
+|---|---|---|---|---|---|
+| {entry_1} | {date_1} | {port_1} | {declared_1} | {correct_1} | {underpayment_1} |
+| {entry_2} | {date_2} | {port_2} | {declared_2} | {correct_2} | {underpayment_2} |
+| ... | ... | ... | ... | ... | ... |
+| **TOTAL** | | | | | **{total_underpayment}** |
+
+{If the exact entries cannot be identified: "We are continuing our investigation to identify all affected entries and will supplement this disclosure with complete entry-level detail within {30/60} days. The estimated total duty underpayment based on our analysis to date is {estimate}."}
+
+**3. Circumstances of the Violation**
+
+{Explain how the violation occurred. Be factual, not defensive:}
+
+{Example: "The classification error originated from reliance on the supplier's suggested HS code without independent verification by a licensed customs broker. Our internal compliance review programme identified the discrepancy during a routine quarterly audit on {discovery_date}."}
+
+**4. Corrective Actions**
+
+{Describe what you have done and will do to prevent recurrence:}
+
+1. {Immediate correction: "All future entries of this product will be classified under HTS {correct_HTS}."}
+2. {Process improvement: "We have implemented a mandatory independent classification review for all new HTS codes before first entry."}
+3. {Training: "All import operations staff will complete CBP Informed Compliance training by {date}."}
+4. {Monitoring: "Quarterly classification audits will be conducted by {internal team or external firm}."}
+
+**5. Tender of Duties and Interest**
+
+Pursuant to 19 CFR § 162.74(c), {company_name} hereby tenders the total underpaid duties in the amount of **${total_underpayment}** plus estimated interest of **${interest_amount}**, for a total tender of **${total_tender}**.
+
+{Check enclosed payable to "U.S. Customs and Border Protection" / ACH payment details}
+
+{If you cannot calculate the exact amount: "We are prepared to tender the full amount upon CBP's calculation of the precise duty and interest owed. This disclosure and tender are made in good faith based on the information available to us as of the date of this filing."}
+
+**6. Conclusion**
+
+{company_name} is committed to compliance with US customs laws and regulations. This disclosure is made voluntarily and in good faith. We respectfully request that this matter be treated as a valid prior disclosure under 19 CFR § 162.74, limiting any penalty assessment to the statutory minimum.
+
+We are prepared to cooperate fully with any CBP review of this disclosure and to provide additional documentation upon request.
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+{address}
+{phone}
+{email}
+
+Enclosures:
+1. Check / payment confirmation for ${total_tender}
+2. Spreadsheet of affected entries with calculations
+3. {Supporting documentation: corrected classification analysis, valuation report, etc.}
+
+cc: {Legal counsel}
+ {VP Trade Compliance}
+
+---
+
+## Template 4: Penalty Response / Mitigation Request
+
+**Use when:** Responding to a CBP pre-penalty notice or penalty assessment under 19 USC § 1592.
+
+---
+
+{company_letterhead}
+
+{date}
+
+Fines, Penalties and Forfeitures Officer
+U.S. Customs and Border Protection
+{Port/CEE Address}
+
+**Re: Response to {Pre-Penalty Notice / Penalty Notice} — Case No. {case_number}
+Penalty Claim: ${penalty_amount}
+Entry/Entries: {entry_numbers}**
+
+Dear Sir or Madam:
+
+{company_name} acknowledges receipt of the {pre-penalty notice dated {date} / penalty assessment dated {date}} in the above-referenced matter. We respectfully submit the following response and request for mitigation.
+
+**1. Summary of CBP's Allegations**
+
+{Concisely restate what CBP alleges. Do not argue yet — demonstrate that you understand the issue.}
+
+**2. Response to Allegations**
+
+{Address each allegation factually. Acknowledge what is correct. Contest what is incorrect. Do NOT admit fraud if the facts support negligence.}
+
+{If contesting the culpability level: "While we acknowledge that {the classification was incorrect / the value was understated / the origin was misdeclared}, we respectfully submit that the violation resulted from negligence, not gross negligence. The evidence does not support a finding that {company_name} acted with 'conscious disregard of a known duty' or 'gross indifference.' Specifically:"}
+
+- {Factor 1: "The company maintained a compliance programme that included {specific measures}."}
+- {Factor 2: "The error was identified through {internal audit / broker review}, not as a result of CBP enforcement action."}
+- {Factor 3: "The company has no prior violations in {X} years of import activity."}
+
+**3. Mitigating Factors**
+
+Pursuant to CBP's Mitigation Guidelines, {company_name} submits the following mitigating factors:
+
+| Factor | Evidence |
+|---|---|
+| Contributory CBP error | {CBP accepted {X} prior entries with the same classification without comment / N/A} |
+| Cooperation | {Company has cooperated fully, producing all requested records within {X} days} |
+| Corrective action | {Specific actions taken: new SOPs, training, classification audit, broker change} |
+| Prior good record | {No penalties or adverse findings in {X} years of import activity, {Y} entries} |
+| Compliance programme | {Description of internal compliance programme: staffing, training, audits, systems} |
+| Proportionality | {The penalty of ${penalty_amount} is disproportionate to the actual loss of revenue of ${revenue_loss}} |
+
+**4. Requested Mitigation**
+
+Based on the foregoing, {company_name} respectfully requests that CBP:
+
+{Option A — if acknowledging negligence:}
+"Reduce the penalty to the statutory minimum for negligence under 19 USC § 1592(c)(4), specifically {interest on unpaid duties / 1× lost revenue}, consistent with the mitigating factors presented."
+
+{Option B — if contesting entirely:}
+"Cancel the proposed penalty in its entirety. The entry information, as submitted, was {correct / supported by a reasonable interpretation of the tariff schedule / consistent with prior CBP treatment of this merchandise}."
+
+{Option C — if seeking settlement:}
+"Accept a settlement in the amount of ${proposed_amount}, representing {calculation basis}, in full resolution of this matter."
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+
+Enclosures: {List supporting exhibits}
+cc: {Legal counsel}
+
+---
+
+## Template 5: USMCA Certification of Origin
+
+**Use when:** Certifying that goods qualify for preferential treatment under USMCA. The certification must include all nine data elements per Article 5.2. No prescribed form is required.
+
+---
+
+**CERTIFICATION OF ORIGIN**
+**(United States-Mexico-Canada Agreement)**
+
+**1. Certifier:** {Select one: Exporter / Producer / Importer}
+ Name: {certifier_name}
+ Title: {certifier_title}
+ Company: {company_name}
+ Address: {address}
+ Phone: {phone}
+ Email: {email}
+
+**2. Exporter** {if different from certifier}:
+ Name: {exporter_name}
+ Company: {company_name}
+ Address: {address}
+
+**3. Producer** {if different from exporter}:
+ Name: {producer_name}
+ Company: {company_name}
+ Address: {address}
+ {If multiple producers: "Various — see attached list" OR "Available upon request"}
+
+**4. Importer:**
+ Name: {importer_name}
+ Company: {company_name}
+ Address: {address}
+
+**5. Description of Goods:**
+
+| # | Description | HS Tariff Classification (6-digit) | Origin Criterion | Country of Origin |
+|---|---|---|---|---|
+| 1 | {product_description} | {HS_code} | {criterion_code} | {US/MX/CA} |
+
+**Origin Criterion Codes:**
+- A: Wholly obtained or produced entirely in the territory of one or more USMCA Parties
+- B: Produced entirely in the territory using non-originating materials that satisfy the applicable product-specific rule of origin (Annex 4-B)
+- C: Produced entirely in the territory exclusively from originating materials
+- D: Goods classified under HS chapters/headings listed in Article 4.3
+
+**6. Blanket Period** {if applicable}:
+ From: {start_date} To: {end_date} {maximum 12 months}
+
+**7. I certify that:**
+
+The goods described in this document qualify as originating and the information contained in this document is true and accurate. I assume responsibility for proving such representations and agree to maintain and present upon request or to make available during a verification visit, documentation necessary to support this certification, and to inform, in writing, all persons to whom the certification was given of any changes that could affect the accuracy or validity of this certification.
+
+**Signature:** ______________________
+**Date:** {date}
+
+---
+
+## Template 6: Internal Compliance Advisory
+
+**Use when:** Notifying internal stakeholders of a regulatory change, new compliance requirement, or enforcement action that requires operational changes.
+
+---
+
+**To:** {distribution_list: Import Operations, Procurement, Product Development, Legal}
+**From:** {Trade Compliance Team / compliance_officer_name}
+**Date:** {date}
+**Subject:** COMPLIANCE ACTION REQUIRED: {topic} — Effective {effective_date}
+
+**BUSINESS IMPACT:**
+{Lead with the operational impact — what changes for the business:}
+
+{Example: "Effective {date}, all imports of {product_category} from {country} will require {new documentation / additional testing / modified classification}. Failure to comply will result in {shipment detention, penalties up to $X per entry, import refusal}. Estimated cost impact: {$X per shipment / $Y annually}."}
+
+**WHAT CHANGED:**
+{Brief regulatory background — 2-3 sentences maximum:}
+
+{Example: "CBP issued CSMS Message #{number} on {date} implementing {regulation/ruling}. This modifies the requirements for {specific area} under {statutory reference}."}
+
+**REQUIRED ACTIONS:**
+
+| # | Action | Owner | Deadline |
+|---|---|---|---|
+| 1 | {Specific action item} | {Team/person} | {Date} |
+| 2 | {Specific action item} | {Team/person} | {Date} |
+| 3 | {Specific action item} | {Team/person} | {Date} |
+
+**WHAT HAPPENS IF WE DON'T COMPLY:**
+{Specific consequences:}
+- Shipment detention at port (average {X} days to resolve, demurrage cost ${Y}/day)
+- Penalty exposure: ${amount} per violation under {statute}
+- {If applicable: import refusal, product recall, licence revocation}
+
+**QUESTIONS / ESCALATION:**
+Contact {compliance_officer_name} at {email} / {phone}. Do NOT attempt to self-resolve classification or entry questions — route all inquiries to the trade compliance team.
+
+---
+
+## Template 7: Supplier Questionnaire — Origin Determination
+
+**Use when:** Collecting information from suppliers to determine whether imported goods qualify for preferential treatment under an FTA.
+
+---
+
+**SUPPLIER ORIGIN QUESTIONNAIRE**
+
+**From:** {importer_company} — Trade Compliance Department
+**To:** {supplier_company}
+**Date:** {date}
+**Product(s):** {product_description}
+**Applicable FTA:** {USMCA / EU-UK TCA / RCEP / other}
+
+We are evaluating whether the above product(s) qualify for preferential duty treatment under {FTA}. Your responses to the following questions will be used to prepare the required origin certification. Please provide accurate and complete information — incorrect origin claims can result in penalties for both the importer and the exporter.
+
+**SECTION A: PRODUCT INFORMATION**
+
+1. Product description (technical, not marketing): ________________________________
+2. HS classification at the 6-digit level: ________________________________
+3. Country where the product is manufactured: ________________________________
+4. Facility address where final production occurs: ________________________________
+
+**SECTION B: BILL OF MATERIALS**
+
+For each material/component used in the manufacture of the product, please provide:
+
+| # | Material Description | HS Code (6-digit) | Country of Origin | Supplier Name | % of Total Product Value | Originating under {FTA}? (Y/N) |
+|---|---|---|---|---|---|---|
+| 1 | | | | | | |
+| 2 | | | | | | |
+| 3 | | | | | | |
+
+{Add rows as needed. If the BOM contains more than 20 items, please provide as an attached spreadsheet.}
+
+**SECTION C: MANUFACTURING PROCESS**
+
+5. Describe the manufacturing process performed at your facility: ________________________________
+ {Specifically identify: cutting, assembly, machining, chemical processing, finishing, testing}
+
+6. List any processes performed by subcontractors and the country where subcontracting occurs: ________________________________
+
+7. What is the total value added at your facility as a percentage of the FOB price? _____%
+
+**SECTION D: COST INFORMATION** {Required only if RVC calculation is needed}
+
+8. FOB price of the finished product: ________________________________
+9. Total cost of non-originating materials: ________________________________
+10. Total cost of originating materials: ________________________________
+11. Direct labour cost: ________________________________
+12. Manufacturing overhead: ________________________________
+13. Profit: ________________________________
+
+**SECTION E: CERTIFICATION**
+
+I certify that the information provided above is true and accurate to the best of my knowledge. I understand that false statements may result in penalties under the laws of the importing country.
+
+Name: ________________________________
+Title: ________________________________
+Signature: ________________________________
+Date: ________________________________
+
+Please return the completed questionnaire to {compliance_email} by {deadline_date}.
+
+---
+
+## Template 8: Binding Ruling Appeal / Request for Reconsideration
+
+**Use when:** CBP has issued a ruling or revocation that you believe is incorrect, and you wish to request reconsideration or appeal to the Court of International Trade.
+
+---
+
+{company_letterhead}
+
+{date}
+
+U.S. Customs and Border Protection
+Regulations and Rulings, Office of Trade
+90 K Street NE, 10th Floor
+Washington, DC 20229-1177
+
+**Re: Request for Reconsideration of Ruling Letter {ruling_number}
+Product: {product_description}
+Current Classification: HTS {current_HTS}
+Proposed Reclassification: HTS {proposed_HTS}**
+
+Dear Sir or Madam:
+
+Pursuant to 19 CFR § 177.12, {company_name} respectfully requests reconsideration of CBP Ruling Letter {ruling_number}, issued {ruling_date}, which classified {product_description} under HTS {classification_in_ruling}.
+
+**1. Basis for Reconsideration**
+
+{State the specific grounds:}
+
+{Option A — Error of law:}
+"The ruling incorrectly applied GRI {X} by {specific error}. The correct application of GRI {X} yields classification under heading {XXXX} because {analysis}."
+
+{Option B — Error of fact:}
+"The ruling was based on an incomplete or inaccurate description of the merchandise. Specifically, {identify the factual error and provide the correct facts with supporting evidence}."
+
+{Option C — Changed circumstances:}
+"Since the issuance of the ruling, {identify the change: new WCO classification opinion, new Explanatory Note, product modification, new CBP ruling on analogous goods} has occurred, warranting reconsideration."
+
+**2. Detailed Analysis**
+
+{Present the full GRI analysis supporting your position, structured identically to a ruling request (see Template 2). Address each point in CBP's original ruling that you are contesting.}
+
+**3. Supporting Authorities**
+
+{Cite any authorities that support your position and distinguish any that CBP relied upon:}
+
+- {Authority supporting your position}
+- {Distinguish CBP's cited authority: "CBP relied on Ruling {number}, which addressed {different product}. That ruling is distinguishable because {specific differences}."}
+
+**4. Commercial Impact**
+
+{Explain the practical impact of the ruling on your business:}
+
+"The reclassification from HTS {current} to HTS {proposed} {increases the duty rate from X% to Y% / removes FTA eligibility / triggers AD/CVD deposits / changes PGA requirements}, affecting approximately ${annual_value} in annual imports."
+
+**5. Requested Action**
+
+{company_name} respectfully requests that CBP:
+1. Reconsider Ruling Letter {ruling_number}
+2. Classify {product_description} under HTS {proposed_classification}
+3. {If applicable: "Limit any reclassification to prospective application only, providing a reasonable transition period per 19 USC § 1625(c)."}
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+
+Enclosures: {List: product sample, technical specifications, prior rulings, WCO opinions}
+cc: {Legal counsel}
+
+---
+
+## Template 9: Restricted Party Screening — Hit Adjudication Memorandum
+
+**Use when:** Documenting the adjudication of a restricted party screening hit (false positive clearance or true positive block).
+
+---
+
+**SCREENING HIT ADJUDICATION MEMORANDUM**
+
+**Date:** {date}
+**Adjudicator:** {name}, {title}
+**Transaction Reference:** {PO/order/shipment number}
+**Screening Tool:** {tool_name} (version {version})
+**Screening Date:** {screening_date}
+
+**PARTIES SCREENED:**
+
+| Party | Role | Name Screened | Country |
+|---|---|---|---|
+| {party_1} | Buyer | {name} | {country} |
+| {party_2} | Consignee | {name} | {country} |
+| {party_3} | End User | {name} | {country} |
+
+**HIT DETAILS:**
+
+| Hit # | Screened Name | Matched List | Listed Name | Match Score | List Entry Date |
+|---|---|---|---|---|---|
+| 1 | {screened_name} | {list_name} | {listed_name} | {score}% | {date} |
+
+**ADJUDICATION ANALYSIS:**
+
+{For each hit, analyse the following factors:}
+
+| Factor | Screened Entity | Listed Entity | Match? |
+|---|---|---|---|
+| Full legal name | {name} | {name} | {Y/N/Partial} |
+| Address | {address} | {address} | {Y/N/Partial} |
+| Country | {country} | {country} | {Y/N} |
+| Date of birth / incorporation | {date} | {date} | {Y/N/Unknown} |
+| Aliases | {known aliases} | {listed aliases} | {Y/N} |
+| Additional identifiers | {tax ID, D&B#} | {identifiers on list} | {Y/N} |
+
+**CONCLUSION:**
+
+{Select one:}
+
+**[ ] FALSE POSITIVE** — The screened entity is NOT the listed entity. Basis: {specific reasons — e.g., "Different country (screened entity is in Germany; listed entity is in Iran), different industry sector (screened entity is a pharmaceutical distributor; listed entity is an individual designated for terrorism support), no address correlation."}
+
+**Disposition:** Transaction may proceed.
+
+**[ ] TRUE POSITIVE** — The screened entity IS the listed entity or cannot be distinguished.
+
+**Disposition:** Transaction BLOCKED. Escalated to {compliance officer / legal counsel} on {date}. {If OFAC: "OFAC blocking report to be filed within 10 business days." / If Entity List: "BIS licence application under consideration." / If DPL: "Absolute prohibition — no licence available. Transaction permanently blocked."}
+
+**[ ] INCONCLUSIVE** — Cannot determine with confidence. Escalated to {compliance officer} for additional investigation on {date}.
+
+**Approved by:** _______________________ Date: ___________
+{Compliance Officer / Manager}
+
+**Record Retention:** This memorandum and all supporting documentation will be retained for {5 years from the date of adjudication / indefinitely for true positives}.
diff --git a/skills/customs-trade-compliance/references/decision-frameworks.md b/skills/customs-trade-compliance/references/decision-frameworks.md
new file mode 100644
index 00000000..ac9ed87a
--- /dev/null
+++ b/skills/customs-trade-compliance/references/decision-frameworks.md
@@ -0,0 +1,764 @@
+# Decision Frameworks — Customs & Trade Compliance
+
+This reference provides the detailed decision logic, classification methodology, FTA qualification
+decision trees, customs valuation methods, restricted party screening protocols, and penalty risk
+assessment frameworks for customs and trade compliance operations.
+
+All thresholds, timelines, and regulatory references reflect multi-jurisdictional trade operations
+covering US, EU, UK, and key Asia-Pacific markets. Regulatory citations are current as of 2024
+but must be verified against the latest amendments before reliance in specific proceedings.
+
+---
+
+## 1. HS Classification Methodology
+
+### 1.1 Pre-Classification Information Gathering
+
+Before applying the GRIs, assemble the complete technical profile of the product. Classification
+errors almost always trace back to insufficient product information, not misapplication of the rules.
+
+**Required Information Checklist:**
+
+| Data Point | Why It Matters | Example Impact |
+|---|---|---|
+| Material composition (% by weight) | Determines chapter for textiles, plastics, metals, composites | A fabric that is 52% cotton / 48% polyester classifies as cotton (Ch. 52), not synthetic (Ch. 54) |
+| Primary function | Determines heading for machines, apparatus, instruments | A device that both weighs and labels classifies by the function giving essential character |
+| Dimensions and weight | Determines subheading for many products | Steel tubes above/below 406.4mm OD classify differently |
+| Manufacturing process | Determines whether the product is "prepared," "processed," or raw | Green coffee (Ch. 09) vs roasted coffee (Ch. 09) vs coffee extract (Ch. 21) |
+| Intended use | Relevant for "for use with" or "suitable for" headings | Automotive glass vs architectural glass — identical product, different classifications |
+| Retail packaging | Determines whether GRI 3(b) set rules apply | A first-aid kit in retail packaging is classified as a set; the same items shipped loose are classified individually |
+| Country of manufacture | Affects national tariff lines and AD/CVD applicability | Chinese-origin steel faces additional duties that Korean-origin steel does not |
+| Technical specifications | Resolves subheading-level distinctions | Voltage, frequency, capacity, resolution, accuracy — all create subheading splits |
+
+**Common Information Failures:**
+
+- Relying on the supplier's suggested HS code without independent verification — suppliers classify for export purposes; the import classification may differ at the national level
+- Using a product marketing name instead of a technical description — "SmartWidget Pro" tells you nothing about classification
+- Accepting a "parts of" classification without verifying whether the item meets the Section XVI Note 2 test for parts
+- Classifying based on the product's industry rather than its physical characteristics — an automotive connector and an industrial connector may have the same HS code
+
+### 1.2 GRI Application Decision Tree
+
+```
+START: Product to classify
+ │
+ ├─ Step 1: Read all candidate heading texts
+ │ ├─ Read Section Notes for each candidate Section
+ │ ├─ Read Chapter Notes for each candidate Chapter
+ │ └─ Do the Section/Chapter Notes explicitly include or exclude the product?
+ │ ├─ YES, one heading clearly covers → CLASSIFY (GRI 1). STOP.
+ │ └─ NO unique heading, or notes are ambiguous → Continue to Step 2
+ │
+ ├─ Step 2: Is the product incomplete, unfinished, or unassembled?
+ │ ├─ YES → Does it have the essential character of the complete article?
+ │ │ ├─ YES → Classify as the complete article (GRI 2(a)). STOP.
+ │ │ └─ NO → It may be a "part" — check Section/Chapter notes for parts provisions
+ │ └─ NO → Is it a mixture or combination of materials/components?
+ │ ├─ YES → GRI 2(b) extends headings to include mixtures. Multiple headings
+ │ │ may now apply → Continue to Step 3
+ │ └─ NO → Continue to Step 3
+ │
+ ├─ Step 3: Multiple headings still apply (prima facie classifiable under 2+)
+ │ ├─ Step 3(a): Is one heading more specific than the others?
+ │ │ ├─ YES → Classify under the most specific heading. STOP.
+ │ │ └─ NO (headings are equally specific, or the product is a composite/set) →
+ │ │
+ │ ├─ Step 3(b): Is the product a composite good, set put up for retail sale,
+ │ │ or goods put up in sets for retail sale?
+ │ │ ├─ YES → Classify by the material or component giving essential character
+ │ │ │ ├─ Essential character determinable → CLASSIFY. STOP.
+ │ │ │ └─ Essential character not determinable → Continue to 3(c)
+ │ │ └─ NO → Continue to 3(c)
+ │ │
+ │ └─ Step 3(c): Classify under the heading that occurs LAST in numerical order. STOP.
+ │
+ ├─ Step 4: No heading covers the product even after Steps 1-3
+ │ └─ Classify under the heading for the most ANALOGOUS goods (GRI 4). STOP.
+ │
+ ├─ Step 5: (Applies to cases, containers, and packing materials)
+ │ ├─ GRI 5(a): Cases, boxes, and similar containers specially shaped for a specific
+ │ │ article are classified WITH the article when presented together
+ │ └─ GRI 5(b): Packing materials are classified with the goods unless they are
+ │ clearly suitable for repetitive use
+ │
+ └─ Step 6: Subheading-level classification
+ ├─ Apply GRI 1-5 within the determined heading
+ ├─ Compare subheading texts at the SAME level (one-dash vs one-dash, two-dash vs two-dash)
+ └─ Subheading notes take precedence at this level. CLASSIFY. STOP.
+```
+
+### 1.3 Essential Character Determination (GRI 3(b))
+
+When a composite good or set must be classified by the component giving essential character,
+assess the following factors. No single factor is determinative — weigh them in context:
+
+| Factor | When It Is Decisive | Example |
+|---|---|---|
+| **Function** | When one component defines what the product does | A flashlight with a built-in radio — if the primary purchase reason is illumination, the flashlight component gives essential character |
+| **Value** | When one component represents the dominant cost | A gift set with a $95 watch and $5 pouch — the watch gives essential character by value |
+| **Bulk/Weight** | When one component is physically dominant | A concrete-and-steel composite where concrete is 90% by weight |
+| **Role in use** | When one component is indispensable | A printer cartridge kit with cartridge + cleaning cloth — the cartridge is indispensable, the cloth is ancillary |
+| **Consumer perception** | When the product is marketed for one component | A toy with candy — if marketed as a toy (candy is incidental), the toy gives essential character |
+
+**When essential character cannot be determined:** If the factors conflict or are balanced (e.g., two
+components of roughly equal value, bulk, and functional importance), essential character is
+"not determinable" and you must proceed to GRI 3(c) — last heading in numerical order.
+
+### 1.4 Section XVI Special Rules (Machines and Mechanical Appliances)
+
+Section XVI (Chapters 84-85) has complex notes that override the general GRI application:
+
+**Note 1 — Exclusions:** Parts of general use (Section XV), belts and hoses (Ch. 39/40/59),
+and other specifically excluded articles do not classify in Section XVI regardless of their use
+with machines.
+
+**Note 2 — Parts classification hierarchy:**
+1. Parts that are goods included in any heading of Chapters 84 or 85 (other than 8409, 8431,
+ 8448, 8466, 8473, 8503, 8522, 8529, 8538) are classified in their OWN heading, not as parts.
+2. Other parts, if suitable for use solely or principally with a particular machine, classify WITH
+ that machine.
+3. Parts suitable for use with multiple machines classify under the "catch-all" parts headings
+ (8409, 8431, etc.) or under heading 8487 (miscellaneous machine parts).
+
+**Note 3 — Composite machines:** A machine that performs two or more complementary functions
+classifies under the heading for the function that represents the PRINCIPAL function. If no
+principal function is identifiable, Note 3 defers to GRI 3(c).
+
+**Note 4 — Machine units:** A machine consisting of separate components designed to jointly
+perform a clearly defined function classifies as the complete machine when the components
+are presented together or when the components are designed to be assembled.
+
+**Note 5 — Automatic Data Processing (ADP) machines:** Heading 8471 requires the machine to be
+capable of: (a) storing the processing program, (b) being freely programmed by the user,
+(c) performing arithmetical computations, and (d) executing a user-modified processing program
+without physical intervention. All four criteria must be met. A single-function device
+(e.g., a barcode scanner that only scans) does not meet criterion (b) and classifies under its
+function-specific heading, not as ADP.
+
+### 1.5 Common Classification Disputes and Resolution
+
+**Dispute: Is it a "part" or an "accessory"?**
+- Parts are essential to the functioning of the machine and are consumed in, or physically
+ integrated with, the machine during use. Without the part, the machine does not function.
+- Accessories enhance or supplement the machine's function but are not essential. The machine
+ functions without the accessory.
+- Classification impact: Parts often follow the machine's classification. Accessories may classify
+ independently under their own material or function heading, often at a different duty rate.
+
+**Dispute: Is the food "prepared" (Chapter 16/19/20/21) or raw (Chapters 2-14)?**
+- "Prepared" generally means processed beyond what is necessary for preservation or transport.
+ Frozen raw shrimp: Chapter 3. Cooked shrimp: Chapter 16. Shrimp tempura (battered and fried): Chapter 16.
+- Simple operations that do NOT constitute "preparation": washing, trimming, freezing, chilling,
+ sorting by size, packing. These maintain the product in Chapter 2-14.
+- Watch for Chapter notes — Chapter 20 Note 1 excludes vegetables "prepared or preserved by
+ vinegar" (heading 2001 is the specific provision) from the general Chapter 7 vegetable headings.
+
+**Dispute: Is it a "set" under GRI 3(b)?**
+A "set put up for retail sale" must meet ALL three conditions:
+1. Consists of at least two different articles classifiable in different headings
+2. Consists of articles put up together to meet a particular need or carry out a specific activity
+3. Put up in a manner suitable for sale directly to users without repacking
+
+If any condition fails, the items are classified individually — not as a set. Industrial assortments
+(e.g., a box of assorted fasteners) that are not "put up for retail sale" do not qualify.
+
+---
+
+## 2. FTA Qualification Decision Trees
+
+### 2.1 General FTA Qualification Process
+
+```
+START: Can this product qualify for preferential treatment?
+ │
+ ├─ Step 1: Identify ALL potentially applicable FTAs
+ │ ├─ Where was the good produced / last substantially transformed?
+ │ ├─ Where is it being imported?
+ │ └─ Are both countries parties to one or more FTAs?
+ │ ├─ YES → List all applicable FTAs → Continue to Step 2
+ │ └─ NO → No FTA preference available. Check GSP or other unilateral programmes.
+ │
+ ├─ Step 2: For each applicable FTA, determine the product-specific rule of origin
+ │ ├─ Look up the HS heading (4-digit or 6-digit) in the FTA's product-specific rules annex
+ │ ├─ Determine the rule type:
+ │ │ ├─ Tariff Shift (change in tariff classification — CTC, CTH, CTSH)
+ │ │ ├─ Regional Value Content (RVC) threshold
+ │ │ ├─ Specific process requirement
+ │ │ └─ Combination of the above
+ │ └─ Continue to Step 3
+ │
+ ├─ Step 3: Trace all materials in the bill of materials (BOM)
+ │ ├─ For each input material, determine:
+ │ │ ├─ HS classification of the input
+ │ │ ├─ Country of origin of the input
+ │ │ ├─ Value of the input (for RVC calculations)
+ │ │ └─ Whether the input is "originating" under the same FTA (for cumulation)
+ │ └─ Continue to Step 4
+ │
+ ├─ Step 4: Apply the product-specific rule
+ │ ├─ Tariff Shift: Has every non-originating material undergone the required tariff shift?
+ │ │ ├─ CTC (change in tariff chapter): all non-originating materials must be from a
+ │ │ │ different 2-digit chapter than the finished good
+ │ │ ├─ CTH (change in tariff heading): different 4-digit heading
+ │ │ ├─ CTSH (change in tariff subheading): different 6-digit subheading
+ │ │ └─ Check exceptions — many rules list specific headings that are EXCLUDED from the
+ │ │ tariff shift (e.g., "a change from any heading except 7208-7212")
+ │ ├─ RVC: Does the regional value content meet or exceed the threshold?
+ │ │ ├─ Calculate using the permitted method(s)
+ │ │ └─ If the FTA offers multiple methods, use the most favourable
+ │ └─ Process: Has the required manufacturing process been performed in the territory?
+ │
+ ├─ Step 5: Apply cumulation (if applicable)
+ │ ├─ Materials originating in other FTA partner countries can be treated as originating
+ │ ├─ Bilateral cumulation: only between the two parties (EU-UK TCA)
+ │ ├─ Diagonal cumulation: among all parties (RCEP, PEM Convention)
+ │ └─ Full cumulation: even processing (not just originating materials) in partner countries
+ │ counts toward origin (EU Overseas Countries and Territories)
+ │
+ ├─ Step 6: Apply de minimis / tolerance rules
+ │ ├─ Most FTAs allow a small percentage of non-originating materials that don't meet the
+ │ │ tariff shift rule (typically 7-10% of the product's value)
+ │ ├─ De minimis does NOT apply to materials specifically excluded in the product-specific rule
+ │ └─ Textiles have separate de minimis rules (usually weight-based, not value-based)
+ │
+ └─ Step 7: Verify certification and documentation requirements
+ ├─ USMCA: self-certification with nine required data elements
+ ├─ EU-UK TCA: origin declaration on the invoice (for consignments under €6,000 any
+ │ exporter; above €6,000 requires REX registration)
+ ├─ RCEP: certificate of origin (Form RCEP) or origin declaration
+ └─ Retain ALL supporting documentation for the FTA's prescribed retention period
+```
+
+### 2.2 USMCA Rules of Origin — Detailed Application
+
+**Tariff Shift Rules:**
+
+USMCA Annex 4-B contains product-specific rules for every HS heading. Many rules combine
+a tariff shift requirement with an RVC threshold. Common patterns:
+
+- **Pure tariff shift:** "A change to heading 9403 from any other chapter." All non-originating
+ materials must come from chapters other than 94 (furniture). If you use non-originating wood
+ from Chapter 44 to make a wooden table, the wood satisfies this rule because Chapter 44 ≠ Chapter 94.
+ But if you import non-originating table legs already classified in heading 9403, the tariff shift fails.
+
+- **Tariff shift with exceptions:** "A change to heading 6204 from any heading outside the group
+ of headings 6201-6212, except from heading 5106-5113 or 5204-5212..." These carve-outs
+ are designed to prevent simple assembly operations from conferring origin.
+
+- **Tariff shift OR RVC:** "A change to heading 8471 from any other heading; or No required
+ change in tariff classification, provided there is a regional value content of not less than
+ 45 percent under the transaction-value method or not less than 35 percent under the net cost method."
+ The exporter may choose whichever alternative is easier to satisfy.
+
+**Regional Value Content Calculations:**
+
+*Transaction Value Method:*
+```
+RVC = ((TV - VNM) / TV) × 100
+```
+Where:
+- TV = Transaction Value of the good (adjusted to FOB)
+- VNM = Value of Non-originating Materials (including parts, materials consumed in production)
+
+*Net Cost Method:*
+```
+RVC = ((NC - VNM) / NC) × 100
+```
+Where:
+- NC = Total cost minus sales promotion, marketing, after-sales service, royalties, shipping and
+ packing costs, and non-allowable interest
+- VNM = same as above
+
+The net cost method typically produces a HIGHER RVC because it removes costs that inflate the
+denominator. Use it when margins are thin or when significant royalty/promotion costs are present.
+
+**Automotive Rules (USMCA-specific):**
+
+USMCA introduced the most complex automotive rules of origin ever negotiated:
+- Passenger vehicles: 75% RVC using net cost method (phased in from 62.5%)
+- Core parts (engines, transmissions, body/chassis): separate 75% RVC requirement
+- Principal parts (brakes, axles, suspension): 70% RVC
+- Complementary parts (A/C, steering, batteries): 70% RVC
+- Steel and aluminium: 70% must be "melted and poured" in North America
+- Labour Value Content: 40% of production must be by workers earning ≥ US$16/hour (high-wage)
+
+### 2.3 EU-UK TCA Rules of Origin
+
+**Key Differences from USMCA:**
+
+- No self-certification for high-value consignments without REX registration
+- Bilateral cumulation only (UK + EU, not with third countries unless separate agreements exist)
+- "Insufficient processing" list: operations that NEVER confer origin regardless of tariff shift
+ (e.g., simple assembly, packaging, mixing, ironing of textiles, sharpening/grinding)
+- Tolerance: 10% of ex-works price for non-originating materials that don't satisfy the list rule
+ (15% for products of Chapters 50-63, textiles — but measured by weight, not value)
+
+**List Rules Structure:**
+
+EU-UK TCA Annex ORIG-2 provides rules in four columns:
+1. HS heading of the finished product
+2. Description of the product
+3. Working or processing on non-originating materials that confers origin
+4. Alternative rule (if available)
+
+Example: Heading 8418 (refrigerators)
+- Rule: "Manufacture in which all materials used are classified within a heading other than
+ that of the product" AND "the value of all non-originating materials used does not exceed
+ 40% of the ex-works price of the product"
+- Both conditions must be met (they are cumulative, not alternative)
+
+### 2.4 RCEP Rules of Origin
+
+**Key Features:**
+
+- 15 member states with diagonal cumulation
+- Product-specific rules use both tariff shift and RVC (40% threshold typical)
+- RVC can be calculated using either:
+ - Build-up: RVC = (VOM / FOB) × 100 ≥ 40%
+ - Build-down: RVC = ((FOB - VNM) / FOB) × 100 ≥ 40%
+- Certificate of Origin (Form RCEP) or approved exporter origin declaration
+- "Back-to-back" certificates allowed for goods transshipped through a non-party (critical for
+ Singapore/Hong Kong hub operations)
+- Product-specific rules for Chapters 50-63 (textiles) are notably restrictive — many require
+ two-step processing (yarn → fabric → garment)
+
+### 2.5 AfCFTA Rules of Origin (Summary)
+
+- General rule: value-added threshold of 40% (or a change in tariff heading)
+- Cumulation: up to 60% of materials can originate from other AfCFTA member states
+- Simplified rules for LDC member states
+- Product-specific rules still being negotiated for many tariff lines — check the latest Protocol
+ on Rules of Origin annexes before relying on general rules
+
+---
+
+## 3. Customs Valuation Methods
+
+### 3.1 Method Selection Decision Tree
+
+```
+START: Determine the customs value of imported goods
+ │
+ ├─ Method 1: Transaction Value
+ │ ├─ Is there a sale for export to the country of importation?
+ │ │ ├─ NO (consignment, loan, free sample, gift, lease) → Skip to Method 2
+ │ │ └─ YES → Is the sale between related parties?
+ │ │ ├─ NO → Is the sale subject to conditions that cannot be quantified?
+ │ │ │ ├─ NO → Are there restrictions on disposition/use (other than legal or geographic)?
+ │ │ │ │ ├─ NO → Transaction Value = Price paid or payable + additions - deductions
+ │ │ │ │ │ ├─ Additions (19 CFR § 152.103 / UCC Art. 71):
+ │ │ │ │ │ │ ├─ Commissions (except buying commissions)
+ │ │ │ │ │ │ ├─ Assists (tools, dies, moulds, engineering provided free/at reduced cost)
+ │ │ │ │ │ │ ├─ Royalties and licence fees related to the imported goods, payable as
+ │ │ │ │ │ │ │ a condition of sale
+ │ │ │ │ │ │ ├─ Packing costs
+ │ │ │ │ │ │ ├─ Proceeds of subsequent resale accruing to the seller
+ │ │ │ │ │ │ └─ US: cost of transport TO the US port (ocean/air freight, insurance)
+ │ │ │ │ │ │ EU: transport and insurance to the EU border are INCLUDED
+ │ │ │ │ │ │ (CIF basis for EU, FOB+ for US)
+ │ │ │ │ │ └─ Deductions (not included in transaction value):
+ │ │ │ │ │ ├─ Post-importation transport costs (inland freight)
+ │ │ │ │ │ ├─ Import duties and taxes
+ │ │ │ │ │ ├─ Construction/installation costs after importation
+ │ │ │ │ │ └─ Buying commissions (if clearly identified)
+ │ │ │ │ └─ CLASSIFY VALUE. STOP.
+ │ │ │ └─ YES → Skip to Method 2
+ │ │ └─ YES (related parties) →
+ │ │ ├─ Did the relationship influence the price?
+ │ │ │ ├─ NO (demonstrate with "circumstances of sale" test or test values) →
+ │ │ │ │ Transaction Value is acceptable. Apply additions/deductions above.
+ │ │ │ └─ YES or cannot demonstrate → Skip to Method 2
+ │ │ └─ OR: Does the transaction value approximate a "test value"?
+ │ │ (transaction value of identical/similar goods to unrelated buyers,
+ │ │ deductive value, or computed value for identical/similar goods)
+ │ │ ├─ YES → Transaction Value acceptable. STOP.
+ │ │ └─ NO → Skip to Method 2
+ │
+ ├─ Method 2: Transaction Value of Identical Goods
+ │ ├─ Are there importations of IDENTICAL goods?
+ │ │ (same in all respects: physical characteristics, quality, reputation, country of origin)
+ │ ├─ Sold for export at the same commercial level and in substantially the same quantity?
+ │ │ (Adjustments permitted for quantity differences and transport costs)
+ │ ├─ Sold at or about the same time as the goods being valued?
+ │ │ ├─ YES to all → Use the transaction value of those identical goods. STOP.
+ │ │ └─ NO to any → Skip to Method 3
+ │
+ ├─ Method 3: Transaction Value of Similar Goods
+ │ ├─ Same criteria as Method 2, but for goods that are "similar" —
+ │ │ closely resembling in characteristics, components, materials,
+ │ │ and capable of performing the same functions and being commercially interchangeable
+ │ │ ├─ Available → Use. STOP.
+ │ │ └─ Not available → Skip to Method 4 (or Method 5 at importer's request in the US)
+ │
+ ├─ Method 4: Deductive Value
+ │ ├─ Start with the unit price at which the greatest aggregate quantity is sold
+ │ │ in the country of importation (within 90 days of import date)
+ │ ├─ DEDUCT:
+ │ │ ├─ Commissions or profit and general expenses normally earned on sales in the
+ │ │ │ importing country for goods of the same class or kind
+ │ │ ├─ Transport and insurance costs within the importing country
+ │ │ ├─ Customs duties and other national taxes payable on importation
+ │ │ └─ If the goods are further processed after importation ("super deductive"):
+ │ │ deduct the value added by the processing
+ │ └─ Result = Deductive Value. STOP.
+ │
+ ├─ Method 5: Computed Value
+ │ ├─ BUILD UP from:
+ │ │ ├─ Cost or value of materials and fabrication/processing in the producing country
+ │ │ ├─ Amount for profit and general expenses equal to that usually reflected in sales
+ │ │ │ of goods of the same class or kind from the country of exportation
+ │ │ └─ Cost of transport and insurance to the importing country (CIF for EU, FOB+ for US)
+ │ ├─ This method is only available if the foreign producer is willing to share cost data
+ │ │ and submit to verification by the importing country's customs authority
+ │ └─ Result = Computed Value. STOP.
+ │
+ └─ Method 6: Fallback ("Reasonable Means")
+ ├─ Flexible application of Methods 1-5 with reasonable adjustments
+ ├─ Prohibitions — the value CANNOT be based on:
+ │ ├─ Selling price of goods produced in the importing country
+ │ ├─ A system providing for use of the higher of two alternative values
+ │ ├─ The price of goods in the domestic market of the country of exportation
+ │ ├─ Minimum customs values
+ │ ├─ Arbitrary or fictitious values
+ │ └─ Cost of production other than computed values for identical/similar goods
+ └─ Result = Fallback Value. STOP.
+```
+
+### 3.2 Related-Party Valuation — Circumstances of Sale Test
+
+When the buyer and seller are related (per 19 USC § 1401a(g) or UCC Art. 127), customs
+authorities will scrutinise the transaction value. To demonstrate that the relationship did not
+influence the price:
+
+**Evidence that supports acceptance:**
+
+1. The price was settled in a manner consistent with normal pricing practices in the industry
+2. The price was settled in a manner consistent with how the seller prices to unrelated buyers
+3. The price is adequate to ensure recovery of all costs plus a profit equivalent to the
+ firm's overall profit over a representative period in sales of goods of the same class or kind
+4. Transfer pricing documentation showing the price was set at arm's length under OECD guidelines
+
+**Test values (alternative to circumstances of sale):**
+
+The transaction value is acceptable if it closely approximates one of:
+- Transaction value on identical or similar goods sold to unrelated buyers in the importing country
+- Deductive value for identical or similar goods
+- Computed value for identical or similar goods
+
+"Closely approximates" means within a reasonable range — CBP and EU customs have discretion here,
+but differences under 5% are generally accepted, 5-10% require explanation, and over 10% will
+likely trigger rejection of the transaction value.
+
+### 3.3 Assists Valuation
+
+Assists are one of the most frequently overlooked additions to transaction value. An assist is
+anything the buyer provides to the seller free of charge or at reduced cost for use in producing
+the imported goods:
+
+**Types of assists:**
+
+| Assist Type | Valuation Method | Apportionment |
+|---|---|---|
+| Materials consumed in production (raw materials, components) | Cost of acquisition or production | Full value added to first shipment, or prorated across all units produced |
+| Tools, dies, moulds, and similar items | Cost of acquisition or production; if previously used, current value only | Prorated across the number of units produced using the tool/die/mould |
+| Engineering, development, artwork, design, plans, and sketches | Cost if undertaken in the importing country; value if undertaken elsewhere | Prorated across anticipated total production, or first shipment |
+| Materials consumed in production provided by related parties | Price paid between related parties if arm's length; otherwise cost of production | Same as unrelated-party assists |
+
+**Critical assist trap:** A US company sends CAD drawings to a Chinese manufacturer at no charge.
+The value of producing those drawings (engineering time, software licences) must be added to the
+customs value of every import from that manufacturer that uses those drawings. Failure to declare
+assists is one of the top findings in CBP Focused Assessments and triggers penalty exposure.
+
+### 3.4 Royalties and Licence Fees
+
+Royalties are dutiable additions to transaction value when they are:
+1. Related to the imported goods (not to post-importation activity), AND
+2. Paid as a condition of the sale (the buyer cannot buy the goods without paying the royalty)
+
+**Dutiable examples:**
+- Royalty paid to the seller (or a related party) for the right to manufacture using a patented
+ process — the royalty directly relates to production of the imported goods
+- Trademark licence fee paid to the parent company where the manufacturer will only produce
+ goods bearing the trademark for the licensed importer
+- Technology licence fee where the foreign producer can only access the technology through the
+ buyer's licence
+
+**Non-dutiable examples:**
+- Royalty for the right to distribute or resell in the importing country (post-importation activity)
+- Royalty paid to an unrelated third party where the seller has no knowledge of or interest in
+ the royalty arrangement and the royalty is not a condition of the sale
+
+**The "condition of sale" analysis is fact-intensive.** Look at:
+- Would the seller sell the goods to the buyer without the royalty being paid?
+- Does the seller have any involvement in, or control over, the royalty arrangement?
+- Can the buyer source the goods elsewhere if the royalty is not paid?
+
+---
+
+## 4. Restricted Party Screening Protocol
+
+### 4.1 Screening Workflow
+
+```
+START: New transaction (sale, purchase, or service)
+ │
+ ├─ Step 1: Identify ALL parties to the transaction
+ │ ├─ Buyer / importer of record
+ │ ├─ Seller / exporter
+ │ ├─ Ultimate consignee / end user
+ │ ├─ Intermediate consignees
+ │ ├─ Freight forwarders and customs brokers
+ │ ├─ Banks (in letter of credit transactions)
+ │ ├─ Ship-to addresses (if different from buyer/consignee)
+ │ └─ Any agents, representatives, or beneficial owners
+ │
+ ├─ Step 2: Screen ALL identified parties against ALL applicable lists
+ │ ├─ US Lists (if US nexus exists — US-origin goods, US persons, US financial system):
+ │ │ ├─ OFAC SDN List (Specially Designated Nationals and Blocked Persons)
+ │ │ ├─ OFAC Sectoral Sanctions Identifications (SSI) List
+ │ │ ├─ OFAC Non-SDN Menu-Based Sanctions List (NS-MBS)
+ │ │ ├─ BIS Entity List (Supplement No. 4 to Part 744)
+ │ │ ├─ BIS Denied Persons List
+ │ │ ├─ BIS Unverified List
+ │ │ ├─ BIS Military End User (MEU) List
+ │ │ ├─ DDTC Debarred Parties (AECA Section 38)
+ │ │ └─ Non-Proliferation Sanctions lists
+ │ ├─ EU Lists (if EU nexus exists):
+ │ │ ├─ EU Consolidated Financial Sanctions List
+ │ │ └─ EU Dual-Use Regulation Annex I controlled end-users
+ │ ├─ UK Lists (if UK nexus exists):
+ │ │ ├─ UK OFSI Consolidated List
+ │ │ └─ UK Export Control Joint Unit
+ │ ├─ Other Jurisdictions: Australia DFAT, Canada SEMA, Japan METI, etc.
+ │ └─ Internal denied/watch lists (prior compliance issues, flagged entities)
+ │
+ ├─ Step 3: Evaluate screening results
+ │ ├─ NO HITS → Document the screening (date, tool, parties screened, result).
+ │ │ Proceed with the transaction. STOP.
+ │ ├─ HITS RETURNED → Continue to Step 4
+ │
+ ├─ Step 4: Adjudicate each hit
+ │ ├─ For each hit, assess:
+ │ │ ├─ Name match quality (exact, near-exact, partial, phonetic)
+ │ │ ├─ Address correlation (same country? same city? same street?)
+ │ │ ├─ Date of birth / incorporation date (for individuals / entities)
+ │ │ ├─ Alias match (is the match against a known alias?)
+ │ │ ├─ Additional identifiers (passport #, tax ID, DUNS, vessel IMO#)
+ │ │ └─ Prior transaction history (known good customer for 10 years?)
+ │ ├─ FALSE POSITIVE (high confidence) → Document adjudication rationale.
+ │ │ Record: who adjudicated, date, factors considered, conclusion.
+ │ │ Proceed with transaction. STOP.
+ │ ├─ POSSIBLE MATCH (ambiguous) → Continue to Step 5
+ │ └─ TRUE POSITIVE (confirmed) → Continue to Step 6
+ │
+ ├─ Step 5: Escalate ambiguous matches
+ │ ├─ Request additional identifying information from the customer/counterparty
+ │ ├─ Engage compliance counsel
+ │ ├─ Do NOT proceed with the transaction until resolved
+ │ ├─ Document the hold and all steps taken
+ │ └─ If cannot be resolved → Treat as TRUE POSITIVE (Step 6)
+ │
+ └─ Step 6: True positive — full stop
+ ├─ BLOCK the transaction immediately
+ ├─ SDN/OFAC match:
+ │ ├─ Block and report to OFAC within 10 business days
+ │ ├─ Do not release goods, do not process payment, do not communicate
+ │ │ the reason to the blocked party
+ │ └─ Determine if an OFAC licence is available and warranted
+ ├─ Entity List match:
+ │ ├─ Determine licence requirement (most are "presumption of denial")
+ │ ├─ If a licence exception is available, document the basis
+ │ └─ If no exception, apply for a BIS licence (expect 60-90 day processing)
+ ├─ Denied Persons List match:
+ │ ├─ ABSOLUTE prohibition — no licence available
+ │ └─ No exports, re-exports, or in-country transfers to denied persons
+ ├─ Notify compliance officer and legal counsel
+ ├─ Document EVERYTHING — the hit, the adjudication, the decision, the block
+ └─ Retain records indefinitely for DPL; 5 years minimum for others
+```
+
+### 4.2 Red Flag Indicators — Enhanced Due Diligence Triggers
+
+When any of the following red flags are present, standard screening is insufficient. Conduct
+enhanced due diligence before proceeding:
+
+| Red Flag | What It Suggests | Required Action |
+|---|---|---|
+| Customer declines to state end use | Diversion risk | Require end-use certificate or decline the transaction |
+| Unusual routing (e.g., electronics shipped Lagos→Dubai→Baku) | Sanctions evasion / diversion to embargoed destination | Map the full supply chain; verify the final destination |
+| Customer willing to pay cash for high-value capital goods | Money laundering or sanctions circumvention | Enhanced KYC; verify source of funds |
+| Delivery to P.O. Box, residential address, or free trade zone | Concealment of true end user | Require physical street address and site visit if >$50K |
+| Product capability exceeds stated end use | Military/WMD diversion | Verify end-use statement matches the product specification |
+| Customer has no Internet presence or verifiable business history | Shell company or front for sanctioned entity | Company registration check, D&B report, beneficial ownership analysis |
+| Order for spare parts inconsistent with installed base | Stockpiling for embargoed destination | Request installed-base details; verify service history |
+| Customer requests removal of product labelling or markings | Circumvention of end-use controls or trademark fraud | Decline the request and escalate to compliance |
+| Customer or forwarding agent was previously flagged | Repeat compliance risk | Senior compliance review before any transaction |
+| Payment from a third party or country not involved in the transaction | Sanctions evasion through financial intermediaries | Verify the commercial rationale for the payment structure |
+
+---
+
+## 5. Penalty Risk Assessment
+
+### 5.1 US Penalty Framework — Detailed Analysis
+
+**19 USC § 1592 — Penalties for Fraud, Gross Negligence, and Negligence:**
+
+| Element | Fraud | Gross Negligence | Negligence |
+|---|---|---|---|
+| **Mental state** | Intentional and knowing violation with intent to defraud | Conscious disregard of a known duty or gross indifference | Failure to exercise reasonable care |
+| **Maximum penalty** | Domestic value of the merchandise | 4× lost revenue, or 40% of dutiable value | 2× lost revenue, or 20% of dutiable value |
+| **Criminal referral** | Yes — up to $10K fine and 2 years per count (18 USC § 542) | Rare | No |
+| **Proof burden** | CBP must prove fraud by clear and convincing evidence | CBP must prove by preponderance of the evidence | CBP must prove by preponderance; importer must show reasonable care |
+| **Mitigation potential** | Limited — requires extraordinary cooperation | Moderate — compliance programme, disclosure, cooperation | Significant — first offence, corrective actions, small scale |
+| **Prior disclosure effect** | Caps penalty at 1× lost revenue (if accepted) | Caps penalty at 1× lost revenue | Caps penalty at interest on the unpaid duties |
+| **Statute of limitations** | 5 years from date of violation | 5 years | 5 years |
+
+**Penalty Mitigation Factors (per CBP's Mitigation Guidelines):**
+
+1. **Contributory CBP error:** Did CBP accept prior entries with the same error without comment?
+2. **Cooperation:** Full cooperation with the investigation, including production of records and
+ internal investigation findings
+3. **Immediate corrective action:** Did the importer fix the problem as soon as it was discovered?
+4. **Prior good record:** Clean compliance history for 5+ years
+5. **Inability to pay:** Financial hardship (documented) can reduce monetary penalties
+6. **Scale of violation:** Isolated incident vs systemic pattern
+7. **Compliance programme:** Existence and effectiveness of an internal compliance programme
+
+### 5.2 Prior Disclosure Decision Framework
+
+```
+START: You have discovered a potential customs violation
+ │
+ ├─ Step 1: Assess — Has CBP already commenced an investigation?
+ │ ├─ YES (you've received a CF-28 Request for Information, CF-29 Notice of Action,
+ │ │ pre-penalty notice, or Focused Assessment notification) →
+ │ │ Prior disclosure is still available UNTIL a formal investigation has commenced.
+ │ │ A CF-28/29 alone does not constitute commencement. A pre-penalty notice does.
+ │ │ ├─ Pre-penalty notice or formal investigation commenced → Prior disclosure
+ │ │ │ is NOT available. Respond to the notice with legal counsel. STOP.
+ │ │ └─ Only CF-28/29 → Prior disclosure is still available. Continue.
+ │ └─ NO → Prior disclosure is available. Continue to Step 2.
+ │
+ ├─ Step 2: Determine the nature and scope of the violation
+ │ ├─ Classification error → How many entries are affected? Calculate total duty differential.
+ │ ├─ Valuation error → Quantify the underdeclared value and the corresponding duty impact.
+ │ ├─ Origin misstatement → Identify all affected entries and the correct origin.
+ │ ├─ FTA over-claim → Calculate the duty that should have been paid without the preference.
+ │ ├─ Record-keeping failure → Identify what records are missing and for which entries.
+ │ └─ Other → Define the specific violation and quantify the duty impact.
+ │
+ ├─ Step 3: Evaluate prior disclosure vs. alternative strategies
+ │ ├─ Prior disclosure IS advisable when:
+ │ │ ├─ The violation is clear-cut and the duty shortfall is quantifiable
+ │ │ ├─ You are confident CBP has not yet begun investigating this issue
+ │ │ ├─ The penalty exposure is material (prior disclosure caps it at interest/1×)
+ │ │ └─ The violation involves negligence or gross negligence (not fraud)
+ │ ├─ Prior disclosure may NOT be advisable when:
+ │ │ ├─ The classification or valuation position is defensible and you are prepared to litigate
+ │ │ ├─ The amount at issue is de minimis (the administrative cost of disclosure exceeds benefit)
+ │ │ ├─ The violation is uncertain — you may be disclosing something that isn't actually wrong
+ │ │ └─ The disclosure would reveal other issues CBP is unaware of (consult counsel first)
+ │ └─ ALWAYS consult legal counsel before filing. Prior disclosure is an admission of violation.
+ │
+ ├─ Step 4: Prepare the prior disclosure
+ │ ├─ Required elements (19 CFR § 162.74):
+ │ │ ├─ Identify the entry numbers and dates of all affected entries
+ │ │ ├─ Describe the specific violation (what was wrong)
+ │ │ ├─ Provide the correct information (what should have been declared)
+ │ │ ├─ Identify the circumstances that led to the violation (how it happened)
+ │ │ ├─ Calculate the duty owed with interest
+ │ │ └─ Tender the full amount of unpaid duties (or explain why you cannot calculate exactly
+ │ │ and provide a good-faith estimate with a commitment to pay the final amount)
+ │ ├─ File with the FP&F office at the port of entry (or the CEE with jurisdiction)
+ │ └─ Retain a copy with proof of delivery
+ │
+ └─ Step 5: Post-filing
+ ├─ CBP will review the disclosure and may request additional information
+ ├─ If accepted, you will receive a penalty notice limited to interest (negligence) or
+ │ 1× lost revenue (gross negligence)
+ ├─ If rejected (disclosure was incomplete, or investigation had already commenced),
+ │ full penalty exposure returns
+ └─ Implement corrective measures to prevent recurrence — CBP will look at this if
+ another violation occurs
+```
+
+### 5.3 Export Control Penalty Framework
+
+**BIS (EAR) Penalties:**
+- Civil: Up to $330,198 per violation OR twice the value of the transaction, whichever is greater
+ (adjusted annually for inflation)
+- Criminal: Up to $1,000,000 per violation and 20 years imprisonment
+- Denial of export privileges: automatic bar from all exports/re-exports from the US
+
+**DDTC (ITAR) Penalties:**
+- Civil: Up to $1,301,256 per violation (adjusted annually)
+- Criminal: Up to $1,000,000 per violation and 20 years imprisonment
+- Debarment from all ITAR-controlled exports
+
+**OFAC Penalties:**
+- Vary by sanctions programme, but civil penalties can exceed $330,000 per violation for
+ IEEPA-based sanctions
+- Criminal: up to $1,000,000 and 20 years imprisonment under IEEPA
+- Strict liability for OFAC violations — no intent required for civil penalties
+
+---
+
+## 6. Post-Entry Audit Preparation
+
+### 6.1 CBP Focused Assessment Preparation Checklist
+
+When a CBP Focused Assessment is announced, the following preparation is critical:
+
+**Documentation to assemble:**
+- [ ] Internal compliance manual / SOP documentation
+- [ ] Organisational chart showing compliance function reporting lines
+- [ ] Training records for all personnel involved in import operations
+- [ ] Customs broker power of attorney and instructions
+- [ ] Classification decisions with supporting rationale (for sample entries)
+- [ ] Valuation documentation including assist calculations and related-party analysis
+- [ ] FTA qualification files with supplier certifications
+- [ ] Restricted party screening logs with adjudication records
+- [ ] Reconciliation entries (if applicable)
+- [ ] Prior disclosures filed (if any)
+- [ ] Internal audit reports for the past 3 years
+- [ ] Record retention policy and evidence of compliance
+
+**Pre-assessment self-audit:**
+1. Pull 50 representative entries spanning the audit period
+2. Re-classify the top 20 by value — does the classification still hold?
+3. Re-value 10 entries including related-party transactions — are assists captured?
+4. Verify FTA claims on 10 entries — is the origin documentation complete?
+5. Re-screen all parties from 10 entries — any new hits since original screening?
+6. Identify and disclose any errors found BEFORE the FA team arrives (prior disclosure still available)
+
+---
+
+## 7. Incoterms Decision Matrix
+
+### 7.1 Selecting the Appropriate Incoterm
+
+| Consideration | Recommended Incoterm | Rationale |
+|---|---|---|
+| Buyer wants maximum control over logistics | FCA | Buyer chooses carrier, route, and insurance. Seller handles export formalities. |
+| Seller has better freight rates (economy of scale) | CIF / CIP | Seller leverages volume contracts. Buyer bears risk from first carrier. |
+| Buyer cannot act as exporter in seller's country | FCA, CPT, CIP, DAP, DDP | Avoid EXW — it makes the buyer the exporter of record in the origin country. |
+| Buyer lacks import capability in destination | DDP | Seller handles everything including import clearance. Seller must register as IOR. |
+| Letter of credit requires on-board BOL | FCA (with 2020 A6/B6 option) | The 2020 revision allows buyer to instruct carrier to issue on-board BOL to seller. |
+| High-risk transit (theft, damage, piracy corridor) | CIF / CIP | Seller is responsible for insurance. CIP requires all-risks coverage (ICC A). |
+| Containerised ocean freight | FCA, CPT, CIP | FOB is technically incorrect for containers — risk transfers at container yard, not ship's rail. |
+| Domestic delivery (same country) | FCA, DAP | Incoterms are not required for domestic; if used, FCA or DAP are appropriate. |
+
+### 7.2 Incoterms and Customs Valuation Impact
+
+The Incoterm affects the customs value because different terms include or exclude freight and
+insurance in the invoice price:
+
+| Incoterm | US Customs Value Adjustment | EU Customs Value Adjustment |
+|---|---|---|
+| EXW | ADD: inland freight to port + international freight + insurance to US port | ADD: inland freight to port + international freight + insurance to EU border |
+| FCA | ADD: international freight + insurance from named place to US port | ADD: international freight + insurance from named place to EU border |
+| FOB | ADD: ocean freight + insurance to US port (already includes inland to port) | ADD: ocean freight + insurance to EU border |
+| CFR/CPT | ADD: insurance (freight already included) | ADD: insurance (freight already included) |
+| CIF/CIP | No adjustment (freight and insurance included) | No adjustment (freight and insurance included) |
+| DAP | DEDUCT: inland freight from port/airport to final destination in US (if identifiable) | DEDUCT: inland freight from EU border to destination |
+| DDP | DEDUCT: inland freight + import duties (duty is never part of customs value) | DEDUCT: inland freight from EU border + import duties |
diff --git a/skills/customs-trade-compliance/references/edge-cases.md b/skills/customs-trade-compliance/references/edge-cases.md
new file mode 100644
index 00000000..69b90747
--- /dev/null
+++ b/skills/customs-trade-compliance/references/edge-cases.md
@@ -0,0 +1,362 @@
+# Customs & Trade Compliance — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous trade compliance situations that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced trade compliance professionals from everyone else. Each one involves competing regulatory frameworks, ambiguous fact patterns, multi-jurisdictional complexity, and real financial exposure. They are structured to guide resolution when standard procedures break down.
+
+---
+
+## How to Use This File
+
+When a trade compliance question doesn't fit a clean category — when classification is genuinely ambiguous, when origin is disputed, when multiple regulatory regimes apply simultaneously, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; these are the cases that end up before administrative law judges, in penalty proceedings, or in criminal referrals.
+
+---
+
+### Edge Case 1: De Minimis Threshold Exploitation — Section 321 Abuse
+
+**Situation:**
+A mid-size e-commerce retailer imports consumer electronics from Shenzhen. Their freight forwarder suggests restructuring ocean freight consolidations into individual direct-to-consumer parcels, each valued under $800, to clear under Section 321 de minimis and avoid the 25% Section 301 duty on List 3 goods. The retailer currently imports approximately 15,000 units per month at a declared value of $45 per unit (total duty exposure: approximately $168,750/month at 25%). The forwarder's proposal would route parcels through a fulfilment centre in China that ships individual packages via ePacket/USPS to US consumers.
+
+**Why It's Tricky:**
+The de minimis threshold is per importation, per person, per day. On its face, individual shipments valued at $45 each qualify. But CBP has increasingly targeted structured de minimis programmes, and the Consolidated Appropriations Act of 2016 gave CBP expanded enforcement authority. Several factors complicate this:
+
+- If the retailer is the importer of record for all packages (not the individual consumers), CBP can aggregate all packages arriving on the same day as a single importation
+- Section 321 does NOT exempt goods subject to AD/CVD orders, quotas, or certain PGA requirements (FDA, CPSC, EPA) — only the duty is waived
+- If the electronics require FCC certification, each unit still needs to comply regardless of de minimis status
+- CBP's e-commerce enforcement strategy specifically targets "daigou" and structured de minimis programmes
+
+**Common Mistake:**
+Assuming that Section 321 is a simple value threshold. Many importers and their forwarders treat it as a binary: under $800, no duty. But the aggregation rules, PGA requirements, and enforcement posture make structured programmes a significant compliance risk. CBP has issued penalty cases exceeding $1M against importers who structured shipments to exploit de minimis.
+
+The second mistake: ignoring state sales tax and marketplace facilitator obligations. Even if federal duty is avoided, the retailer may have nexus obligations in destination states that offset some of the savings.
+
+**Expert Approach:**
+1. Assess whether the individual consumers are genuinely the importers of record. If the retailer controls the logistics, owns the inventory in transit, and bears the risk of loss, the retailer is the IOR — not the consumer. This makes aggregation almost certain.
+2. Review the specific HS codes for AD/CVD applicability. Electronics are generally not subject to AD/CVD, but certain components (e.g., crystalline silicon PV cells, certain steel enclosures) may be covered.
+3. Check PGA requirements. Consumer electronics almost certainly require FCC Declaration of Conformity. Lithium batteries require DOT/PHMSA compliance. Children's products require CPSC testing. None of these are waived by Section 321.
+4. Calculate the true savings vs risk. The duty savings of $168,750/month must be weighed against: (a) per-unit shipping cost increase (ocean FCL at $0.35/unit vs ePacket at $3-5/unit), (b) compliance risk (penalty exposure under 19 USC § 1592 for structured evasion), (c) transit time increase (30-45 days ocean + inland vs 14-21 days ePacket but no inventory buffer), (d) customer experience impact (inconsistent delivery times, returns complexity).
+5. If the economics still favour de minimis after honest analysis, structure it properly: each consumer must be the IOR, the retailer should use a compliant Section 321 filing programme (not just undervalue or misdeclare), and all PGA requirements must be satisfied per shipment.
+6. Document the business rationale and legal analysis thoroughly. If CBP challenges the programme, the difference between "structured evasion" (penalty) and "legitimate programme" (defensible) is documentation of good-faith compliance effort.
+
+**Key Indicators:**
+- CBP's COAC subcommittee on Section 321 has recommended enhanced data requirements — anticipate changes
+- Multiple packages to the same address on the same day from the same shipper will be flagged
+- The STOP Act of 2018 requires electronic advance data for all international mail shipments — the "under the radar" strategy no longer works
+
+---
+
+### Edge Case 2: Transshipment Circumventing AD/CVD Duties — EAPA Investigation
+
+**Situation:**
+A US furniture importer purchases wooden bedroom furniture "manufactured in Vietnam" from a Vietnamese trading company. The unit price is $180 FOB Ho Chi Minh City, which is 40% below comparable Vietnamese production costs. Coincidentally, Chinese-origin wooden bedroom furniture is subject to AD/CVD duties totalling 216.01% (combined AD duty of 198.08% + CVD of 17.93%) under A-570-890. CBP initiates an EAPA (Enforce and Protect Act) investigation based on an allegation from a domestic manufacturer.
+
+**Why It's Tricky:**
+The EAPA process gives CBP subpoena authority and the ability to impose interim measures (cash deposits at the AD/CVD rate) within 90 days. The importer must prove that the goods are genuinely of Vietnamese origin — which requires demonstrating "substantial transformation" in Vietnam. The test is whether the processing in Vietnam results in "a new and different article of commerce with a new name, character, and use."
+
+Vietnamese furniture factories that merely assemble Chinese-manufactured components (pre-cut panels, pre-finished parts) into finished furniture are almost certainly NOT performing substantial transformation. But factories that take raw lumber (even Chinese-origin lumber), mill it, join it, finish it, and assemble it in Vietnam likely ARE performing substantial transformation, because the raw lumber has been transformed into a finished article with a different name, character, and use.
+
+The grey area is where the Vietnamese factory receives semi-finished components (rough-cut panels, unfinished drawer boxes) and performs significant but not complete processing (sanding, finishing, assembly, quality control, packaging). This is where most disputes land.
+
+**Common Mistake:**
+Relying on the certificate of origin from the Vietnamese chamber of commerce as proof of origin. Certificates of origin attest to the country of EXPORTATION, not the country of substantial transformation. CBP will look through the certificate to the actual manufacturing process.
+
+The second mistake: waiting for CBP to ask questions before investigating your own supply chain. If CBP is conducting an EAPA investigation against your supplier, the best position is to have already audited the supply chain and be able to present a documented analysis.
+
+**Expert Approach:**
+1. Immediately retain trade counsel experienced in AD/CVD and EAPA proceedings. The timelines are short and the penalties are severe (retroactive application of AD/CVD rates to all entries, plus potential fraud referral).
+2. Request from the Vietnamese supplier: (a) complete bill of materials showing the origin of all inputs, (b) production flow chart from raw material receipt to finished goods shipment, (c) cost of production analysis showing the value added in Vietnam, (d) photographs and video of the production process, (e) list of Chinese-origin inputs by HS code and value.
+3. Apply the substantial transformation test. Map each Chinese-origin input through the Vietnamese production process. Determine: does the finished furniture have a different name (yes — "lumber" → "bedroom set"), different character (depends on the degree of processing), and different use (raw lumber has construction and industrial uses; finished furniture has a consumer use)? All three must change.
+4. Calculate the value added in Vietnam as a percentage of the FOB price. While there's no statutory minimum, CBP generally views less than 30% value addition with suspicion. If the Vietnamese factory's value addition (labour, overhead, materials consumed, profit) is less than 30% of the export price, the substantial transformation argument is weak.
+5. If the supply chain analysis reveals that the goods are effectively Chinese-origin with minimal Vietnamese processing, consider: (a) voluntary disclosure to CBP (prior disclosure of AD/CVD evasion caps penalties), (b) restructuring the supply chain to use a Vietnamese factory with genuine manufacturing capability, (c) sourcing from a non-subject country with genuine production.
+6. If the supply chain analysis supports genuine Vietnamese origin, compile the documentation package and be prepared to present it to CBP within the EAPA timeline. Proactive submission of evidence carries significant weight with CBP investigators.
+
+**Key Indicators:**
+- Unit price significantly below production cost in the alleged country of origin is a primary trigger for EAPA complaints
+- Vietnam, Malaysia, Thailand, and Indonesia are the top countries for transshipment allegations on Chinese AD/CVD goods
+- CBP may conduct on-site verification at the Vietnamese factory — prepare the factory for a CBP visit
+- CBP's Allegations Management and Tracking System (AMATS) allows domestic producers to file electronically — expect more allegations
+
+---
+
+### Edge Case 3: Dual-Use Goods — EAR/ITAR Jurisdictional Boundary
+
+**Situation:**
+A US manufacturer produces high-precision CNC milling machines with 5-axis simultaneous contouring capability and positioning accuracy of ±2 microns. The machines are sold commercially to automotive and aerospace manufacturers worldwide. A new customer in India requests a quote for 3 machines to be used in "precision component manufacturing." The machines have a commercial ECCN of 2B001.b.2 under the EAR (controlled for NP, NS, AT reasons). However, the machines could also be used in the production of missile components, and some configurations have historically been considered for ITAR control under USML Category IV (Launch Vehicles, Guided Missiles, Ballistic Missiles, Rockets, Torpedoes, Bombs, and Mines) — specifically, production equipment "specially designed" for USML items.
+
+**Why It's Tricky:**
+This sits at the exact boundary between the EAR (administered by BIS, Department of Commerce) and the ITAR (administered by DDTC, Department of State). The Export Control Reform (ECR) initiative moved many items from the USML to the CCL, but the "specially designed" definition (§ 772.1 of the EAR) creates a complex exclusion/inclusion analysis. If the machine is classified under the ITAR, an export licence is almost certainly required for India and the end-use controls are far more restrictive. If it's under the EAR, a licence may or may not be required depending on the end user and end use.
+
+The critical determination is whether the machine is "specially designed" for USML articles. Under the ECR definition, an item is NOT "specially designed" if it meets any of the six "release" criteria in paragraph (b) of the definition — most importantly, (b)(3): the item "has a function other than" producing USML items and is "not a dedicated tool, jig, fixture, mould, or die." A general-purpose CNC mill that can make many types of precision components likely qualifies for the (b)(3) release. But if the specific configuration being sold is optimised for producing specific missile components, the release may not apply.
+
+**Common Mistake:**
+Self-classifying the item under the EAR without formally resolving the jurisdictional question. If the item is ITAR-controlled and exported under an EAR classification, the exporter has committed violations of BOTH regimes — an unauthorised ITAR export AND a false EAR filing. The correct procedure when jurisdiction is unclear is to submit a Commodity Jurisdiction (CJ) request to DDTC.
+
+The second mistake: assuming that because the machine is sold commercially to many industries, it's automatically EAR-jurisdiction. Commercial availability is relevant but not dispositive. A commercially available item that is "specially designed" for USML applications is ITAR-controlled regardless of its commercial sales history.
+
+**Expert Approach:**
+1. Conduct the "specially designed" analysis under the ECR definition for the SPECIFIC configuration being sold to the Indian customer. Document: (a) what are ALL the functions this machine configuration can perform? (b) is this configuration a "dedicated" production tool for any USML article, or a general-purpose machine? (c) does it meet any of the (b)(1) through (b)(6) release criteria?
+2. If the analysis is clear (the machine is a general-purpose commercial product that meets the (b)(3) release), document the analysis and proceed with EAR classification. Confirm the ECCN (2B001.b.2) and determine the licence requirement for India. For NP-controlled items to India, a licence is likely required unless a licence exception applies. Check BIS's India entity list entries.
+3. If the analysis is ambiguous (the configuration could be considered "specially designed"), file a CJ request with DDTC. Include: the item's technical specifications, its commercial applications, its potential USML applications, and your "specially designed" analysis. DDTC has 45 days to respond (often takes longer).
+4. While the CJ is pending, do NOT ship the machines. Treat the item as ITAR-controlled until DDTC makes a determination.
+5. Regardless of jurisdiction, conduct end-user due diligence on the Indian customer. The machines' accuracy (±2 microns) places them at or near the MTCR (Missile Technology Control Regime) Annex thresholds. Verify: (a) the customer's identity and business operations, (b) the stated end use is consistent with the customer's business, (c) the customer is not on any restricted party list, (d) there are no red flags suggesting missile programme diversion.
+6. If the machines are EAR-jurisdiction and a licence is required, include the Indian customer's end-use statement and the complete technical specifications in the BIS licence application. Processing time is typically 30-60 days.
+7. If the machines are ITAR-jurisdiction, apply for a DSP-5 export licence from DDTC. Processing time is typically 60-90 days, and India is subject to additional review for missile-related items.
+
+**Key Indicators:**
+- 5-axis simultaneous contouring capability at ±2 microns places this firmly in the controlled range under both regimes
+- India is a missile technology-sensitive destination — enhanced scrutiny is expected
+- The phrase "precision component manufacturing" in the customer's end-use statement is too vague — require specificity
+- If the customer refuses to specify the components being manufactured, this is a red flag under § 744.6 (General Prohibition Six)
+
+---
+
+### Edge Case 4: Post-Importation Transfer Pricing Adjustments
+
+**Situation:**
+A multinational pharmaceutical company imports active pharmaceutical ingredients (APIs) from its German parent company. The transfer price is set annually by the parent's tax department using the Comparable Profits Method (CPM) under OECD Transfer Pricing Guidelines. The US subsidiary imports approximately $200M in APIs annually. At fiscal year-end, the tax department determines that the US subsidiary's operating margin exceeded the arm's-length range and issues a downward transfer pricing adjustment of $18M (effectively reducing the price paid for the APIs retroactively). The US subsidiary's trade compliance team discovers that all entries during the fiscal year were declared at the higher, pre-adjustment value.
+
+**Why It's Tricky:**
+Customs valuation and transfer pricing serve opposite purposes. Tax authorities want the transfer price to be high in low-tax jurisdictions and low in high-tax jurisdictions (to minimize global tax). Customs authorities want the declared value to be as high as possible (to maximize duties collected). A downward transfer pricing adjustment reduces the customs value — which means the importer overpaid duties and is entitled to a refund. An upward adjustment increases the customs value — which means the importer underpaid duties and owes additional payments plus potential penalties.
+
+CBP's position (articulated in multiple rulings) is that transfer pricing adjustments must be reflected in the customs value when they relate to the imported merchandise. But the mechanism for doing so — reconciliation entries — has specific procedural requirements that many importers miss.
+
+**Common Mistake:**
+Ignoring the customs implications entirely because "transfer pricing is a tax issue." The trade compliance team often doesn't learn about year-end adjustments until months after they occur, by which time entries may have liquidated and the window for correction has closed.
+
+The second mistake: filing a PSC (Post Summary Correction) to reduce the declared value without proper documentation. CBP will challenge a downward correction on related-party entries unless the importer can demonstrate that the adjusted price satisfies the transaction value test under Method 1.
+
+**Expert Approach:**
+1. Flag reconciliation at the time of importation. When the final price is not known at entry (as with transfer pricing that is subject to year-end adjustment), file entries with the reconciliation flag set. This preserves the right to adjust the declared value after liquidation under the reconciliation programme (19 CFR Part 181 Subpart D for USMCA, or Part 182 for general reconciliation).
+2. When the transfer pricing adjustment is finalised, determine the direction and magnitude:
+ - Downward adjustment ($18M in this case): the importer overpaid duties. File reconciliation entries reducing the declared value and request a refund of excess duties paid. CBP will scrutinise the related-party circumstances of sale.
+ - Upward adjustment: the importer underpaid duties. File reconciliation entries increasing the declared value and tender the additional duties owed. This is effectively a prior disclosure of underpayment.
+3. To support the adjusted value, prepare a "circumstances of sale" analysis demonstrating that the related-party relationship did not influence the price. This requires showing that the transfer pricing methodology produces a price consistent with arm's-length pricing. The CPM analysis from the tax department is helpful but not sufficient — CBP wants to see that the price approximates a "test value" (transaction value of identical/similar goods to unrelated buyers).
+4. If reconciliation was NOT flagged at entry, file PSCs for entries within the liquidation period (typically 314 days from date of entry). For entries that have already liquidated, file a protest under 19 USC § 1514 within 180 days of liquidation. For entries beyond the protest period, the opportunity is lost.
+5. Establish a standing protocol between the trade compliance and tax departments. Require that: (a) trade compliance is notified of all transfer pricing adjustments before they are finalised, (b) reconciliation is flagged on all related-party entries where the price may be adjusted, (c) the tax department's transfer pricing study is shared with trade compliance for customs valuation analysis.
+6. For the $18M downward adjustment: at a 6.5% duty rate (common for APIs), the duty refund would be approximately $1.17M. The administrative cost of filing reconciliation is approximately $5,000-$15,000 (broker fees + internal time). The ROI is overwhelming — do not leave the refund on the table.
+
+**Key Indicators:**
+- Related-party import volume > $50M annually almost guarantees that transfer pricing adjustments will occur
+- CBP's Centers of Excellence and Expertise (Pharmaceutical CEE in New York) actively audits related-party valuations
+- Reconciliation programme participation requires advance approval from CBP — apply before entry, not after
+- The OECD's Two-Pillar Solution may change transfer pricing dynamics significantly — monitor developments
+
+---
+
+### Edge Case 5: First Sale Valuation — Multi-Tier Supply Chain
+
+**Situation:**
+A US apparel retailer sources private-label clothing through a Hong Kong buying agent. The supply chain is: Chinese factory sells to Hong Kong middleman at $8.00/unit (first sale), Hong Kong middleman sells to the US retailer at $12.50/unit (last sale). The goods ship directly from China to the US — they never physically pass through Hong Kong. The applicable duty rate is 19.7%. The retailer wants to declare the $8.00 first sale price as the customs value instead of the $12.50 last sale price, saving $0.89 per unit in duty (($12.50 - $8.00) × 19.7% = $0.89). At 2 million units annually, this is $1.78M in annual duty savings.
+
+**Why It's Tricky:**
+The "first sale rule" derives from the US Court of International Trade's decision in Nissho Iwai American Corp. v. United States (1982). CBP allows the use of the first sale as the transaction value when: (1) the first sale is a bona fide sale for export to the US, (2) the sale is at arm's length, and (3) the price of the first sale is the appropriate measure of the value of the goods when they enter the US.
+
+The challenge is proving all three elements, especially when the middleman adds no physical processing — the goods ship directly from factory to US. CBP scrutinises these arrangements because the middleman's margin (here, $4.50/unit or 56% markup) is significant and may include services that should be additions to the customs value rather than excludable middleman profit.
+
+**Common Mistake:**
+Claiming first sale without maintaining contemporaneous documentation of the factory-to-middleman sale. CBP requires that the first sale be documented with its own commercial invoice, payment records, and shipping instructions that demonstrate it is a genuine sale separate from the middleman-to-importer sale.
+
+The second mistake: failing to account for assists. If the US retailer provides design specifications, tech packs, or quality standards directly to the Chinese factory (bypassing the middleman), these are assists that must be added to the first sale price. Many first sale programmes collapse during audit because the assists were not valued.
+
+**Expert Approach:**
+1. Verify the first sale is a genuine arm's-length transaction. Required documentation:
+ - Separate commercial invoice from the Chinese factory to the Hong Kong middleman
+ - Evidence of payment from the middleman to the factory (bank records)
+ - The factory invoice must pre-date or be contemporaneous with the middleman's invoice to the US retailer
+ - Shipping instructions showing the goods were shipped FOR the middleman (not just invoiced through the middleman)
+2. Analyse the middleman's role. Legitimate first sale structures involve a middleman who: bears title risk, carries inventory risk (even briefly), can independently choose suppliers, negotiates prices independently with both the factory and the buyer, and provides genuine services (sourcing, quality control, logistics coordination). A middleman who is merely invoicing without bearing commercial risk is not a genuine seller — it's a conduit.
+3. Identify all assists flowing from the US retailer to the factory. Every tech pack, design file, sample, lab testing result, or quality inspection provided by the retailer is an assist. Compute the total value and add it to the first sale price. If assists exceed $2.50/unit, the effective first sale price rises to $10.50 and the savings diminish significantly.
+4. Calculate the actual duty savings after all adjustments:
+ - Last sale value: $12.50 → Duty: $2.4625
+ - First sale value (with assists): $8.00 + $1.80 assists = $9.80 → Duty: $1.9306
+ - Net savings per unit: $0.5319 × 2M units = $1,063,800/year
+ - Programme administration cost: approximately $50,000/year (broker fees, documentation, monitoring)
+ - Net benefit: approximately $1,013,800/year
+5. Prepare a first sale ruling request to CBP if the programme exceeds $500K in annual duty savings. A binding ruling provides certainty and significantly reduces audit risk. Include all documentation from steps 1-4.
+6. Monitor the programme quarterly. If the middleman's margin changes significantly, or if the retailer begins providing additional assists, the first sale analysis must be updated.
+
+**Key Indicators:**
+- First sale is ONLY available in the US, Israel, and Australia — the EU, UK, Canada, and most other jurisdictions value on the last sale before importation
+- CBP has revoked first sale treatment in multiple audits where documentation was insufficient
+- If the middleman is related to the factory, first sale treatment is extremely difficult to defend
+- The middleman's markup should reflect genuine commercial services — a 56% markup requires explanation of what services justify that margin
+
+---
+
+### Edge Case 6: Retroactive FTA Claims — Missed Preferential Treatment
+
+**Situation:**
+An internal audit reveals that a US electronics manufacturer has been importing circuit board assemblies from Mexico at the MFN rate of 3.4% for the past 3 years without claiming USMCA preferential treatment. The assemblies qualify for duty-free treatment under USMCA because they undergo a tariff shift from heading 8534 (printed circuits) to heading 8538 (parts for switching apparatus) in Mexico — all non-originating materials (capacitors from Japan, resistors from Korea) change at the heading level. The company imports approximately $15M annually; the overpaid duty totals approximately $1.53M over 3 years.
+
+**Why It's Tricky:**
+USMCA allows retroactive preferential claims, but the mechanism and timeline vary depending on how the entries were filed and whether they have liquidated:
+
+- Entries within the liquidation period (typically 314 days from entry): file a PSC (Post Summary Correction) claiming USMCA preference and attaching the certification of origin
+- Entries that have liquidated but are within the 180-day protest window: file a protest under 19 USC § 1514
+- Entries that have liquidated AND the protest period has expired: file a petition for reliquidation under 19 USC § 1520(d), which allows up to 1 year from the date of liquidation
+
+After these windows close, the duties are permanently overpaid.
+
+**Common Mistake:**
+Assuming all 3 years of entries can be recovered. In practice, the oldest entries have almost certainly passed all available windows. The recoverable amount depends on when exactly each entry liquidated, which varies by port and processing time.
+
+The second mistake: filing a USMCA certification of origin retroactively without verifying that the goods actually qualified at the time of importation. If the bill of materials changed during the 3-year period (e.g., a supplier switched from a Japanese capacitor to a Chinese capacitor), the tariff shift analysis must be performed for each period with different inputs.
+
+**Expert Approach:**
+1. Pull every entry for the 3-year period. For each entry, determine: (a) entry date, (b) liquidation date (check ACE or request from broker), (c) whether liquidation has occurred, (d) whether the protest period has expired.
+2. Categorise entries into three buckets:
+ - Recoverable via PSC (unliquidated): file immediately, no reason to wait
+ - Recoverable via protest (liquidated < 180 days ago): file protests immediately — the clock is ticking
+ - Recoverable via 1520(d) petition (liquidated 180 days - 1 year ago): file petitions
+ - Non-recoverable (liquidated > 1 year ago): document the loss and move on
+3. For each recoverable entry, prepare or obtain the USMCA certification of origin. Under USMCA, the certification can be prepared by the exporter, producer, or importer — the importer can self-certify based on their knowledge of the production process and bill of materials. The certification must include all nine data elements required by Article 5.2.
+4. Verify qualification for each entry period. Obtain the bill of materials from the Mexican producer for each shipment period. Confirm that ALL non-originating materials changed at the heading level. If any material's HS classification is in the same heading as the finished good (8538), that material must be originating or subject to a de minimis exception.
+5. File all claims simultaneously (or in quick succession) to avoid the perception of cherry-picking. Include a cover letter explaining that the claims result from a compliance audit and that the company is implementing corrective measures to claim USMCA preference on future entries.
+6. Implement a go-forward process: (a) add USMCA qualification review to the new-product sourcing workflow, (b) require the customs broker to flag all Mexico-origin entries for preference screening, (c) conduct annual reviews of HS code changes that may affect qualification.
+
+**Key Indicators:**
+- $1.53M in recoverable duties makes this a high-priority recovery project — assign dedicated resources
+- USMCA certifications do not need to be on a specific form — they can be on the commercial invoice, a separate document, or even in electronic format
+- If the Mexican supplier's bill of materials has changed over 3 years, you may need multiple certifications covering different periods
+- CBP may audit retroactive claims — maintain complete documentation of the qualification analysis
+
+---
+
+### Edge Case 7: Temporary Imports That Become Permanent — ATA Carnet Breach
+
+**Situation:**
+A European medical device company brings 6 demonstration units of a surgical laser system (value: €120,000 each, €720,000 total) to the US under an ATA Carnet for a 2-week medical conference and hands-on training programme. During the event, a major US hospital chain expresses interest in purchasing 3 of the 6 units immediately. The sales team, seeing an opportunity, negotiates a sale on the spot and instructs the logistics team to deliver 3 units to the hospital instead of re-exporting them. The carnet expires in 60 days.
+
+**Why It's Tricky:**
+ATA Carnets provide temporary duty-free and tax-free admission on the strict condition that the goods will be re-exported. Selling goods admitted under a carnet is a fundamental breach — the goods were imported duty-free and are now entering US commerce without paying duty. The violations compound:
+
+1. The carnet guarantee (issued by the US Council for International Business, backed by the ICC World Chambers Federation) will be called for the 3 units not re-exported — the European chamber of commerce that issued the carnet is liable
+2. The importing company owes duty, applicable taxes (federal + state), and likely penalties for failure to make entry under the correct customs procedure
+3. The sale may violate the terms of the FDA clearance/approval — if the devices were imported for "demonstration only," they may not have the required FDA status for commercial distribution
+4. Any applicable section 301, AD/CVD, or other special duties apply in addition to the regular duty rate
+
+**Common Mistake:**
+Thinking that simply "paying the duty" fixes the problem. The carnet system is a multilateral guarantee arrangement involving the exporting country's chamber, the importing country's customs authority, and the international guarantee chain. A breach triggers administrative proceedings in both countries and may result in the company being barred from future carnet use.
+
+The second mistake: ignoring the FDA regulatory implications. Surgical lasers are typically Class II or III medical devices requiring 510(k) clearance or PMA. Demonstration units imported under a carnet may not have been cleared for commercial distribution — they were admitted for the specific purpose stated on the carnet (exhibition/demonstration). Selling them for clinical use may be an FDA violation independent of the customs violation.
+
+**Expert Approach:**
+1. Do not deliver the 3 units to the hospital. Halt the sale immediately. The cost of unwinding the customs violation and FDA issues far exceeds the revenue from 3 units.
+2. Re-export all 6 units as planned under the carnet. Have the carnet properly endorsed by CBP on departure.
+3. For the 3 units the hospital wants to purchase, arrange a separate commercial importation: (a) file a formal entry (CBP 7501) with proper classification, valuation, and duty payment, (b) ensure FDA compliance — either import under the existing 510(k)/PMA clearance for the device, or file a new entry with the appropriate FDA affirmation of compliance, (c) use the correct Incoterms for the commercial transaction (likely DDP if the European company is handling everything).
+4. If units have already been delivered to the hospital (the logistics team acted on the sales team's instructions before compliance could intervene): (a) contact a customs broker immediately to file a consumption entry retroactively — this is a "late filing" violation but far better than a "no filing" violation, (b) pay all applicable duties with interest, (c) notify the carnet-issuing chamber that 3 units will not be re-exported and that a formal entry is being filed, (d) file a prior disclosure if the late filing triggers a penalty assessment, (e) conduct a separate FDA analysis — if the devices are not cleared for commercial distribution in the US, they may need to be recalled from the hospital pending clearance.
+5. Implement sales team training: carnet goods CANNOT be sold during the temporary import period. Any sale requires a new import transaction. This is non-negotiable and must be part of sales operations SOP for international demonstrations.
+
+**Key Indicators:**
+- The US duty rate for surgical laser systems (HS 9018.90) is typically 0% — but this doesn't eliminate the filing requirement, MPF, or FDA compliance
+- ATA Carnet claims can take 18-24 months to resolve through the ICC guarantee chain
+- Repeated carnet breaches can result in the issuing chamber refusing to issue future carnets
+- FDA enforcement of "demonstration only" imports has increased — especially for high-risk devices
+
+---
+
+### Edge Case 8: Classification of Kits vs Components — GRI 3(b) Application
+
+**Situation:**
+A US retailer imports a "Home Barista Coffee Kit" from Italy. The kit contains: an espresso machine (HS 8419.81, duty 3.4%), a burr coffee grinder (HS 8509.40, duty 4.2%), a milk frothing pitcher (HS 7323.93, duty 3.4%), a tamper (HS 8210.00, duty 0.4¢ each + 6.4%), two espresso cups with saucers (HS 6912.00, duty 9.8%), and a 250g bag of espresso beans (HS 0901.21, duty free). All items are packaged together in a branded retail box.
+
+**Why It's Tricky:**
+The items span 6 different HS chapters with duty rates ranging from 0% to 9.8%. If classified as a set under GRI 3(b), the entire kit takes a single classification determined by the component giving essential character. If classified individually, each item is entered separately at its own rate.
+
+The importer wants the kit classified as a set under the espresso machine heading (8419.81) at 3.4% duty — arguing the espresso machine gives essential character because it is the highest-value component and the primary reason consumers purchase the kit. CBP may argue the items should be classified individually because: (a) the items are independently functional and sold separately in the market, (b) the "kit" is merely a marketing assortment, not a "set put up for retail sale" meeting GRI 3(b)'s requirements.
+
+**Common Mistake:**
+Assuming that packaging items together automatically creates a "set" for customs purposes. GRI 3(b) has three specific requirements that ALL must be met: (1) at least two different articles classifiable in different headings, (2) articles put together to meet a particular need or carry out a specific activity, and (3) put up in a manner suitable for sale directly to users without repacking.
+
+The second mistake: ignoring the possibility that CBP may argue GRI 3(b) doesn't apply because the espresso machine alone meets the "particular need" (making espresso), and the other items are merely accessories packed with it for marketing purposes.
+
+**Expert Approach:**
+1. Analyse each GRI 3(b) requirement:
+ - Condition 1 (different headings): Satisfied — items span 6 different headings.
+ - Condition 2 (particular need or specific activity): Arguable. "Home espresso preparation" is a specific activity, and all items contribute to that activity. The cups, frothing pitcher, and tamper are directly used in espresso service. The grinder prepares the beans. The beans are the consumable. This condition is likely met.
+ - Condition 3 (put up for retail sale): Satisfied if the packaging is retail-ready (branded box, UPC code, retail pricing). If the items are loose in a plain brown carton, this condition fails.
+2. Determine essential character. The espresso machine is the highest-value component (likely 60-70% of the kit's total value) and is the functional core of the kit — without it, the other items serve no coordinated purpose. Strong argument for the espresso machine as essential character.
+3. Consider the duty impact. If classified as a set at 3.4% (espresso machine rate), the weighted average duty is lower than if the items are classified individually (where the ceramic cups at 9.8% pull the average up). Quantify the difference to determine whether the classification dispute is worth pursuing.
+4. Search the CBP CROSS database for prior rulings on similar kits. CBP has ruled on numerous "sets" — coffee sets, beauty kits, tool kits, art supply sets. Prior rulings provide strong guidance even if not directly on point.
+5. If the duty differential is significant, consider requesting a binding ruling from CBP. Include photographs of the retail packaging, the itemised bill of materials with individual values, and a detailed GRI 3(b) analysis.
+6. Alternative strategy: if set classification is denied, consider whether "duty engineering" — sourcing the high-duty components (ceramic cups) from an FTA partner country — would reduce overall duty more effectively than the set argument.
+
+**Key Indicators:**
+- CBP tends to deny set treatment when the components are independently marketable commodity items
+- CBP is more likely to grant set treatment when the components are specially designed to work together and are not sold separately
+- The bag of coffee beans creates a perishability issue — it may need separate entry with FDA prior notice regardless of set classification
+- Italian-origin goods qualify for zero duty under certain headings if the EU-US tariff negotiations (currently suspended) resume
+
+---
+
+### Edge Case 9: Mis-Declared Country of Origin — Marking Violations
+
+**Situation:**
+A US importer of consumer electronics discovers that their Chinese supplier has been shipping Bluetooth speakers labelled "Designed in California, Assembled in Malaysia" when in fact the speakers are 100% manufactured in China. The Malaysian facility only repackages the products into retail boxes. Over the past 18 months, the importer has entered approximately $4.2M in speakers at the MFN rate applicable to Malaysian-origin goods, avoiding the 25% Section 301 tariff on Chinese-origin goods.
+
+**Why It's Tricky:**
+This is a marking violation (19 USC § 1304) and a false country of origin declaration — both carry separate and compounding penalties. The marking violation alone can result in 10% additional duty plus seizure. The false origin declaration triggers 19 USC § 1592 penalties (negligence, gross negligence, or fraud depending on what the importer knew). And the Section 301 duty avoidance is independently actionable as an AD/CVD evasion matter under EAPA if CBP initiates proceedings.
+
+The importer's exposure calculation:
+- Section 301 duties avoided: $4.2M × 25% = $1,050,000
+- Marking penalty: 10% of $4.2M = $420,000
+- 19 USC § 1592 penalty: up to $4.2M (domestic value) for fraud; $1,680,000 for gross negligence; $840,000 for negligence
+- Total worst-case exposure: $6.3M+ plus seizure of in-transit goods
+
+**Common Mistake:**
+Blaming the supplier and hoping CBP doesn't notice. CBP holds the importer of record responsible for the accuracy of all entry information, including country of origin. "My supplier told me it was Malaysian" is not a defence — it is evidence of negligent reliance on a supplier without verification.
+
+The second mistake: continuing to import while investigating. Every additional entry filed with the wrong origin adds to the penalty exposure.
+
+**Expert Approach:**
+1. IMMEDIATELY halt all imports from this supplier pending investigation.
+2. Engage trade counsel. The exposure level ($1M+ in avoided duties, potential fraud allegation) requires legal representation.
+3. Conduct a rapid investigation: (a) obtain production records from the Malaysian facility — what exactly happens there? If it's only repackaging, that is NOT substantial transformation, (b) obtain production records from the Chinese factory — does the product leave China as a finished, functional speaker? If yes, origin is China regardless of where it's repackaged, (c) review all communications with the supplier about origin — did the importer know or should have known the true origin?
+4. Evaluate the prior disclosure option. If CBP has not commenced an investigation:
+ - Prior disclosure caps the penalty at interest on unpaid duties for negligence ($1,050,000 in duties + interest ≈ $1,100,000 total exposure)
+ - Without prior disclosure, the penalty could exceed $3M
+ - File prior disclosure BEFORE CBP issues any CF-28, CF-29, or pre-penalty notice
+5. In the prior disclosure: (a) identify all affected entries, (b) provide the correct country of origin (China), (c) calculate the Section 301 duty owed, (d) tender the full amount of underpaid duties + interest, (e) explain what happened (supplier misrepresentation, inadequate supply chain verification), (f) describe corrective actions (terminated the supplier, implemented origin verification procedures).
+6. For future imports, implement origin verification SOPs: (a) conduct factory audits before onboarding new suppliers, (b) require production records and material sourcing documentation, (c) verify country of origin marking on all inbound shipments at first receipt, (d) incorporate origin verification into the supplier qualification process.
+
+**Key Indicators:**
+- "Designed in California" is not a country of origin — it's a marketing claim. Origin is where the article was manufactured or substantially transformed.
+- "Assembled in Malaysia" is misleading if the assembly is merely packaging — assembly must confer a new name, character, and use
+- Section 301 tariffs have been in place since 2018 — there is extensive CBP enforcement attention on Chinese-origin goods routed through third countries
+- CBP's trade data analytics can identify price and volume anomalies that suggest origin misstatement
+
+---
+
+### Edge Case 10: Dual-Reporting Obligations — UFLPA and Forced Labour Compliance
+
+**Situation:**
+A US apparel brand imports cotton garments from Bangladesh. The Bangladeshi factory sources cotton yarn from multiple spinners, including one in Pakistan that is known to use Xinjiang, China-origin cotton. The Uyghur Forced Labor Prevention Act (UFLPA) creates a rebuttable presumption that any goods mined, produced, or manufactured wholly or in part in the Xinjiang Uyghur Autonomous Region (XUAR) are produced with forced labour and are prohibited from entry into the US under 19 USC § 1307. CBP detains a shipment of 12,000 units (FOB value $180,000) at the port of Los Angeles pending UFLPA review.
+
+**Why It's Tricky:**
+The UFLPA's rebuttable presumption means the burden is on the IMPORTER to prove — by clear and convincing evidence — that forced labour was NOT used at ANY point in the supply chain. For cotton garments, this requires tracing the supply chain from the garment factory → yarn spinner → cotton gin → cotton farm. If any link in that chain touches Xinjiang, the goods are presumed prohibited.
+
+The evidentiary standard is extremely high. CBP has rejected many detention responses because the importer could not provide sufficient supply chain tracing. Required evidence includes: purchase orders between each entity in the supply chain, production records linking specific cotton bales to specific yarn lots to specific fabric rolls to specific garments, third-party audit reports of labour conditions at each facility, and isotopic testing (where available) confirming the geographic origin of the cotton fibre.
+
+**Common Mistake:**
+Providing a generic "supplier certification" that the factory does not use forced labour. CBP has explicitly stated that self-certifications and supplier affidavits alone are insufficient to overcome the rebuttable presumption. The importer needs documentary evidence tracing the specific inputs in the detained shipment through the entire supply chain.
+
+The second mistake: admitting that Xinjiang cotton might be in the supply chain while arguing it was a small percentage. There is no de minimis exception under UFLPA. Any amount of Xinjiang-origin input renders the goods inadmissible.
+
+**Expert Approach:**
+1. Respond to the detention notice within CBP's prescribed timeline (typically 30 days from the date of the detention notice). Request an extension if needed — CBP routinely grants 30-day extensions for complex supply chains.
+2. Engage the Bangladeshi factory to trace the cotton supply chain:
+ - Identify ALL cotton yarn suppliers and the origins of their cotton
+ - For each yarn supplier, obtain: (a) purchase records for raw cotton, (b) cotton gin certificates showing the origin of cotton bales, (c) lot/batch traceability linking specific cotton purchases to specific yarn production runs, (d) independent audit reports on labour conditions
+3. If the Pakistani spinner used Xinjiang cotton in ANY yarn supplied to the Bangladeshi factory during the production period: the shipment CANNOT be admitted under UFLPA, period. Options:
+ - Re-export the goods to a non-US destination
+ - Abandon/destroy the goods (customs will supervise destruction)
+ - Appeal CBP's determination to the CBP Commissioner within 30 days of the final decision
+4. If the supply chain can be definitively traced to NON-Xinjiang cotton: compile the evidence package. Include: (a) purchase orders and invoices at each tier of the supply chain, (b) production/lot records linking inputs to outputs, (c) independent third-party audit reports (Social Responsibility Alliance, WRAP, Better Cotton Initiative), (d) isotopic testing results if available (Oritain, Applied DNA Sciences), (e) shipping records showing the physical movement of cotton from origin to factory.
+5. File the response with CBP's Forced Labor Division. Organise the evidence to demonstrate clear traceability from finished garment → yarn → cotton → non-XUAR origin.
+6. For future shipments, implement a UFLPA compliance programme: (a) map the entire cotton supply chain to the farm level, (b) eliminate all Xinjiang-connected suppliers, (c) require suppliers to provide chain of custody documentation with each shipment, (d) conduct regular audits using independent third parties, (e) consider switching to cotton sourced from regions with robust traceability programmes (US, Australian, or Brazilian cotton with Better Cotton Initiative certification).
+
+**Key Indicators:**
+- CBP's UFLPA enforcement has detained thousands of shipments — cotton, polysilicon/solar panels, and tomatoes are the primary targets
+- Isotopic testing can distinguish Xinjiang cotton from cotton grown in other regions — CBP is increasingly requesting or conducting these tests
+- The UFLPA Entity List includes specific entities in Xinjiang — screen all suppliers against this list
+- Even if the detained shipment is released, expect heightened scrutiny on ALL future shipments from the same supplier and origin
diff --git a/skills/data-engineer/SKILL.md b/skills/data-engineer/SKILL.md
index 5811df64..e70febdd 100644
--- a/skills/data-engineer/SKILL.md
+++ b/skills/data-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: data-engineer
-description: "Build scalable data pipelines, modern data warehouses, and"
+description: |
+ Build scalable data pipelines, modern data warehouses, and
real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and
cloud-native data platforms. Use PROACTIVELY for data pipeline design,
analytics infrastructure, or modern data stack implementation.
diff --git a/skills/data-scientist/SKILL.md b/skills/data-scientist/SKILL.md
index 5a64a5f2..1557281d 100644
--- a/skills/data-scientist/SKILL.md
+++ b/skills/data-scientist/SKILL.md
@@ -1,6 +1,7 @@
---
name: data-scientist
-description: "Expert data scientist for advanced analytics, machine learning, and"
+description: |
+ Expert data scientist for advanced analytics, machine learning, and
statistical modeling. Handles complex data analysis, predictive modeling, and
business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,
statistical analysis, and data-driven insights.
diff --git a/skills/database-admin/SKILL.md b/skills/database-admin/SKILL.md
index aad6b46b..32b0891e 100644
--- a/skills/database-admin/SKILL.md
+++ b/skills/database-admin/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-admin
-description: "Expert database administrator specializing in modern cloud"
+description: |
+ Expert database administrator specializing in modern cloud
databases, automation, and reliability engineering. Masters AWS/Azure/GCP
database services, Infrastructure as Code, high availability, disaster
recovery, performance optimization, and compliance. Handles multi-cloud
diff --git a/skills/database-architect/SKILL.md b/skills/database-architect/SKILL.md
index 09cbd574..16ed3352 100644
--- a/skills/database-architect/SKILL.md
+++ b/skills/database-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-architect
-description: "Expert database architect specializing in data layer design from"
+description: |
+ Expert database architect specializing in data layer design from
scratch, technology selection, schema modeling, and scalable database
architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization
strategies, migration planning, and performance-first design. Handles both
diff --git a/skills/database-optimizer/SKILL.md b/skills/database-optimizer/SKILL.md
index b8f16262..1bbba8bb 100644
--- a/skills/database-optimizer/SKILL.md
+++ b/skills/database-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-optimizer
-description: "Expert database optimizer specializing in modern performance"
+description: |
+ Expert database optimizer specializing in modern performance
tuning, query optimization, and scalable architectures. Masters advanced
indexing, N+1 resolution, multi-tier caching, partitioning strategies, and
cloud database optimization. Handles complex query analysis, migration
diff --git a/skills/debugger/SKILL.md b/skills/debugger/SKILL.md
index 303c9145..1eb2dfc2 100644
--- a/skills/debugger/SKILL.md
+++ b/skills/debugger/SKILL.md
@@ -1,6 +1,7 @@
---
name: debugger
-description: "Debugging specialist for errors, test failures, and unexpected"
+description: |
+ Debugging specialist for errors, test failures, and unexpected
behavior. Use proactively when encountering any issues.
metadata:
model: sonnet
diff --git a/skills/deployment-engineer/SKILL.md b/skills/deployment-engineer/SKILL.md
index 78ec5db7..af21bd2c 100644
--- a/skills/deployment-engineer/SKILL.md
+++ b/skills/deployment-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: deployment-engineer
-description: "Expert deployment engineer specializing in modern CI/CD pipelines,"
+description: |
+ Expert deployment engineer specializing in modern CI/CD pipelines,
GitOps workflows, and advanced deployment automation. Masters GitHub Actions,
ArgoCD/Flux, progressive delivery, container security, and platform
engineering. Handles zero-downtime deployments, security scanning, and
diff --git a/skills/devops-troubleshooter/SKILL.md b/skills/devops-troubleshooter/SKILL.md
index 94a3fbfc..c2140fe4 100644
--- a/skills/devops-troubleshooter/SKILL.md
+++ b/skills/devops-troubleshooter/SKILL.md
@@ -1,6 +1,7 @@
---
name: devops-troubleshooter
-description: "Expert DevOps troubleshooter specializing in rapid incident"
+description: |
+ Expert DevOps troubleshooter specializing in rapid incident
response, advanced debugging, and modern observability. Masters log analysis,
distributed tracing, Kubernetes debugging, performance optimization, and root
cause analysis. Handles production outages, system reliability, and preventive
diff --git a/skills/django-pro/SKILL.md b/skills/django-pro/SKILL.md
index 06737455..95265460 100644
--- a/skills/django-pro/SKILL.md
+++ b/skills/django-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: django-pro
-description: "Master Django 5.x with async views, DRF, Celery, and Django"
+description: |
+ Master Django 5.x with async views, DRF, Celery, and Django
Channels. Build scalable web applications with proper architecture, testing,
and deployment. Use PROACTIVELY for Django development, ORM optimization, or
complex Django patterns.
diff --git a/skills/docs-architect/SKILL.md b/skills/docs-architect/SKILL.md
index 4f7a0fa1..7c4930da 100644
--- a/skills/docs-architect/SKILL.md
+++ b/skills/docs-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: docs-architect
-description: "Creates comprehensive technical documentation from existing"
+description: |
+ Creates comprehensive technical documentation from existing
codebases. Analyzes architecture, design patterns, and implementation details
to produce long-form technical manuals and ebooks. Use PROACTIVELY for system
documentation, architecture guides, or technical deep-dives.
diff --git a/skills/dotnet-architect/SKILL.md b/skills/dotnet-architect/SKILL.md
index 4c1b4a9d..d5970b28 100644
--- a/skills/dotnet-architect/SKILL.md
+++ b/skills/dotnet-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: dotnet-architect
-description: "Expert .NET backend architect specializing in C#, ASP.NET Core,"
+description: |
+ Expert .NET backend architect specializing in C#, ASP.NET Core,
Entity Framework, Dapper, and enterprise application patterns. Masters
async/await, dependency injection, caching strategies, and performance
optimization. Use PROACTIVELY for .NET API development, code review, or
diff --git a/skills/dx-optimizer/SKILL.md b/skills/dx-optimizer/SKILL.md
index b42d5745..d85bbaa0 100644
--- a/skills/dx-optimizer/SKILL.md
+++ b/skills/dx-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: dx-optimizer
-description: "Developer Experience specialist. Improves tooling, setup, and"
+description: |
+ Developer Experience specialist. Improves tooling, setup, and
workflows. Use PROACTIVELY when setting up new projects, after team feedback,
or when development friction is noticed.
metadata:
diff --git a/skills/elixir-pro/SKILL.md b/skills/elixir-pro/SKILL.md
index ab0d10ef..eb7dbdf0 100644
--- a/skills/elixir-pro/SKILL.md
+++ b/skills/elixir-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: elixir-pro
-description: "Write idiomatic Elixir code with OTP patterns, supervision trees,"
+description: |
+ Write idiomatic Elixir code with OTP patterns, supervision trees,
and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed
systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM
optimizations.
diff --git a/skills/energy-procurement/SKILL.md b/skills/energy-procurement/SKILL.md
new file mode 100644
index 00000000..ba209b5f
--- /dev/null
+++ b/skills/energy-procurement/SKILL.md
@@ -0,0 +1,218 @@
+---
+name: energy-procurement
+description: >
+ Codified expertise for electricity and gas procurement, tariff optimisation,
+ demand charge management, renewable PPA evaluation, and multi-facility energy
+ cost management. Informed by energy procurement managers with 15+ years
+ experience at large commercial and industrial consumers. Includes market
+ structure analysis, hedging strategies, load profiling, and sustainability
+ reporting frameworks. Use when procuring energy, optimising tariffs, managing
+ demand charges, evaluating PPAs, or developing energy strategies.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "⚡"
+---
+
+## When to Use
+
+Use this skill when managing energy procurement tasks, such as optimizing electricity or gas tariffs, evaluating Power Purchase Agreements (PPAs), or developing long-term energy cost management strategies for commercial or industrial facilities.
+
+# Energy Procurement
+
+## Role and Context
+
+You are a senior energy procurement manager at a large commercial and industrial (C&I) consumer with multiple facilities across regulated and deregulated electricity markets. You manage an annual energy spend of $15M–$80M across 10–50+ sites — manufacturing plants, distribution centers, corporate offices, and cold storage. You own the full procurement lifecycle: tariff analysis, supplier RFPs, contract negotiation, demand charge management, renewable energy sourcing, budget forecasting, and sustainability reporting. You sit between operations (who control load), finance (who own the budget), sustainability (who set emissions targets), and executive leadership (who approve long-term commitments like PPAs). Your systems include utility bill management platforms (Urjanet, EnergyCAP), interval data analytics (meter-level 15-minute kWh/kW), energy market data providers (ICE, CME, Platts), and procurement platforms (energy brokers, aggregators, direct ISO market access). You balance cost reduction against budget certainty, sustainability targets, and operational flexibility — because a procurement strategy that saves 8% but exposes the company to a $2M budget variance in a polar vortex year is not a good strategy.
+
+## Core Knowledge
+
+### Pricing Structures and Utility Bill Anatomy
+
+Every commercial electricity bill has components that must be understood independently — bundling them into a single "rate" obscures where real optimization opportunities exist:
+
+- **Energy charges:** The per-kWh cost for electricity consumed. Can be flat rate (same price all hours), time-of-use/TOU (different prices for on-peak, mid-peak, off-peak), or real-time pricing/RTP (hourly prices indexed to wholesale market). For large C&I customers, energy charges typically represent 40–55% of the total bill. In deregulated markets, this is the component you can competitively procure.
+- **Demand charges:** Billed on peak kW drawn during a billing period, measured in 15-minute intervals. The utility takes the highest single 15-minute average kW reading in the month and multiplies by the demand rate ($8–$25/kW depending on utility and rate class). Demand charges represent 20–40% of the bill for manufacturing facilities with variable loads. One bad 15-minute interval — a compressor startup coinciding with HVAC peak — can add $5,000–$15,000 to a monthly bill.
+- **Capacity charges:** In markets with capacity obligations (PJM, ISO-NE, NYISO), your share of the grid's capacity cost is allocated based on your peak load contribution (PLC) during the prior year's system peak hours (typically 1–5 hours in summer). PLC is measured at your meter during the system coincident peak. Reducing load during those few critical hours can cut capacity charges by 15–30% the following year. This is the single highest-ROI demand response opportunity for most C&I customers.
+- **Transmission and distribution (T&D):** Regulated charges for moving power from generation to your meter. Transmission is typically based on your contribution to the regional transmission peak (similar to capacity). Distribution includes customer charges, demand-based delivery charges, and volumetric delivery charges. These are generally non-bypassable — even with on-site generation, you pay distribution charges for being connected to the grid.
+- **Riders and surcharges:** Renewable energy standards compliance, nuclear decommissioning, utility transition charges, and regulatory mandated programs. These change through rate cases. A utility rate case filing can add $0.005–$0.015/kWh to your delivered cost — track open proceedings at your state PUC.
+
+### Procurement Strategies
+
+The core decision in deregulated markets is how much price risk to retain versus transfer to suppliers:
+
+- **Fixed-price (full requirements):** Supplier provides all electricity at a locked $/kWh for the contract term (12–36 months). Provides budget certainty. You pay a risk premium — typically 5–12% above the forward curve at contract signing — because the supplier is absorbing price, volume, and basis risk. Best for organizations where budget predictability outweighs cost minimization.
+- **Index/variable pricing:** You pay the real-time or day-ahead wholesale price plus a supplier adder ($0.002–$0.006/kWh). Lowest long-run average cost, but full exposure to price spikes. In ERCOT during Winter Storm Uri (Feb 2021), wholesale prices hit $9,000/MWh — an index customer on a 5 MW peak load faced a single-week energy bill exceeding $1.5M. Index pricing requires active risk management and a corporate culture that tolerates budget variance.
+- **Block-and-index (hybrid):** You purchase fixed-price blocks to cover your baseload (60–80% of expected consumption) and let the remaining variable load float at index. This balances cost optimization with partial budget certainty. The blocks should match your base load shape — if your facility runs 3 MW baseload 24/7 with a 2 MW variable load during production hours, buy 3 MW blocks around-the-clock and 2 MW blocks on-peak only.
+- **Layered procurement:** Instead of locking in your full load at one point in time (which concentrates market timing risk), buy in tranches over 12–24 months. For example, for a 2027 contract year: buy 25% in Q1 2025, 25% in Q3 2025, 25% in Q1 2026, and the remaining 25% in Q3 2026. Dollar-cost averaging for energy. This is the single most effective risk management technique available to most C&I buyers — it eliminates the "did we lock at the top?" problem.
+- **RFP process in deregulated markets:** Issue RFPs to 5–8 qualified retail energy providers (REPs). Include 36 months of interval data, your load factor, site addresses, utility account numbers, current contract expiration dates, and any sustainability requirements (RECs, carbon-free targets). Evaluate on total cost, supplier credit quality (check S&P/Moody's — a supplier bankruptcy mid-contract forces you into utility default service at tariff rates), contract flexibility (change-of-use provisions, early termination), and value-added services (demand response management, sustainability reporting, market intelligence).
+
+### Demand Charge Management
+
+Demand charges are the most controllable cost component for facilities with operational flexibility:
+
+- **Peak identification:** Download 15-minute interval data from your utility or meter data management system. Identify the top 10 peak intervals per month. In most facilities, 6–8 of the top 10 peaks share a common root cause — simultaneous startup of multiple large loads (chillers, compressors, production lines) during morning ramp-up between 6:00–9:00 AM.
+- **Load shifting:** Move discretionary loads (batch processes, charging, thermal storage, water heating) to off-peak periods. A 500 kW load shifted from on-peak to off-peak saves $5,000–$12,500/month in demand charges alone, plus energy cost differential.
+- **Peak shaving with batteries:** Behind-the-meter battery storage can cap peak demand by discharging during the highest-demand 15-minute intervals. A 500 kW / 2 MWh battery system costs $800K–$1.2M installed. At $15/kW demand charge, shaving 500 kW saves $7,500/month ($90K/year). Simple payback: 9–13 years — but stack demand charge savings with TOU energy arbitrage, capacity tag reduction, and demand response program payments, and payback drops to 5–7 years.
+- **Demand response (DR) programs:** Utility and ISO-operated programs pay customers to curtail load during grid stress events. PJM's Economic DR program pays the LMP for curtailed load during high-price hours. ERCOT's Emergency Response Service (ERS) pays a standby fee plus an energy payment during events. DR revenue for a 1 MW curtailment capability: $15K–$80K/year depending on market, program, and number of dispatch events.
+- **Ratchet clauses:** Many tariffs include a demand ratchet — your billed demand cannot fall below 60–80% of the highest peak demand recorded in the prior 11 months. A single accidental peak of 6 MW when your normal peak is 4 MW locks you into billing demand of at least 3.6–4.8 MW for a year. Always check your tariff for ratchet provisions before any facility modification that could spike peak load.
+
+### Renewable Energy Procurement
+
+- **Physical PPA:** You contract directly with a renewable generator (solar/wind farm) to purchase output at a fixed $/MWh price for 10–25 years. The generator is typically located in the same ISO where your load is, and power flows through the grid to your meter. You receive both the energy and the associated RECs. Physical PPAs require you to manage basis risk (the price difference between the generator's node and your load zone), curtailment risk (when the ISO curtails the generator), and shape risk (solar produces when the sun shines, not when you consume).
+- **Virtual (financial) PPA (VPPA):** A contract-for-differences. You agree on a fixed strike price (e.g., $35/MWh). The generator sells power into the wholesale market at the settlement point price. If the market price is $45/MWh, the generator pays you $10/MWh. If the market price is $25/MWh, you pay the generator $10/MWh. You receive RECs to claim renewable attributes. VPPAs do not change your physical power supply — you continue buying from your retail supplier. VPPAs are financial instruments and may require CFO/treasury approval, ISDA agreements, and mark-to-market accounting treatment.
+- **RECs (Renewable Energy Certificates):** 1 REC = 1 MWh of renewable generation attributes. Unbundled RECs (purchased separately from physical power) are the cheapest way to claim renewable energy use — $1–$5/MWh for national wind RECs, $5–$15/MWh for solar RECs, $20–$60/MWh for specific regional markets (New England, PJM). However, unbundled RECs face increasing scrutiny under GHG Protocol Scope 2 guidance: they satisfy market-based accounting but do not demonstrate "additionality" (causing new renewable generation to be built).
+- **On-site generation:** Rooftop or ground-mount solar, combined heat and power (CHP). On-site solar PPA pricing: $0.04–$0.08/kWh depending on location, system size, and ITC eligibility. On-site generation reduces T&D exposure and can lower capacity tags. But behind-the-meter generation introduces net metering risk (utility compensation rate changes), interconnection costs, and site lease complications. Evaluate on-site vs. off-site based on total economic value, not just energy cost.
+
+### Load Profiling
+
+Understanding your facility's load shape is the foundation of every procurement and optimization decision:
+
+- **Base vs. variable load:** Base load runs 24/7 — process refrigeration, server rooms, continuous manufacturing, lighting in occupied areas. Variable load correlates with production schedules, occupancy, and weather (HVAC). A facility with a 0.85 load factor (base load is 85% of peak) benefits from around-the-clock block purchases. A facility with a 0.45 load factor (large swings between occupied and unoccupied) benefits from shaped products that match the on-peak/off-peak pattern.
+- **Load factor:** Average demand divided by peak demand. Load factor = (Total kWh) / (Peak kW × Hours in period). A high load factor (>0.75) means relatively flat, predictable consumption — easier to procure and lower demand charges per kWh. A low load factor (<0.50) means spiky consumption with a high peak-to-average ratio — demand charges dominate your bill and peak shaving has the highest ROI.
+- **Contribution by system:** In manufacturing, typical load breakdown: HVAC 25–35%, production motors/drives 30–45%, compressed air 10–15%, lighting 5–10%, process heating 5–15%. The system contributing most to peak demand is not always the one consuming the most energy — compressed air systems often have the worst peak-to-average ratio due to unloaded running and cycling compressors.
+
+### Market Structures
+
+- **Regulated markets:** A single utility provides generation, transmission, and distribution. Rates are set by the state Public Utility Commission (PUC) through periodic rate cases. You cannot choose your electricity supplier. Optimization is limited to tariff selection (switching between available rate schedules), demand charge management, and on-site generation. Approximately 35% of US commercial electricity load is in fully regulated markets.
+- **Deregulated markets:** Generation is competitive. You can buy electricity from qualified retail energy providers (REPs), directly from the wholesale market (if you have the infrastructure and credit), or through brokers/aggregators. ISOs/RTOs operate the wholesale market: PJM (Mid-Atlantic and Midwest, largest US market), ERCOT (Texas, uniquely isolated grid), CAISO (California), NYISO (New York), ISO-NE (New England), MISO (Central US), SPP (Plains states). Each ISO has different market rules, capacity structures, and pricing mechanisms.
+- **Locational Marginal Pricing (LMP):** Wholesale electricity prices vary by location (node) within an ISO, reflecting generation costs, transmission losses, and congestion. LMP = Energy Component + Congestion Component + Loss Component. A facility at a congested node pays more than one at an uncongested node. Congestion can add $5–$30/MWh to your delivered cost in constrained zones. When evaluating a VPPA, the basis risk between the generator's node and your load zone is driven by congestion patterns.
+
+### Sustainability Reporting
+
+- **Scope 2 emissions — two methods:** The GHG Protocol requires dual reporting. Location-based: uses average grid emission factor for your region (eGRID in the US). Market-based: reflects your procurement choices — if you buy RECs or have a PPA, your market-based emissions decrease. Most companies targeting RE100 or SBTi approval focus on market-based Scope 2.
+- **RE100:** A global initiative where companies commit to 100% renewable electricity. Requires annual reporting of progress. Acceptable instruments: physical PPAs, VPPAs with RECs, utility green tariff programs, unbundled RECs (though RE100 is tightening additionality requirements), and on-site generation.
+- **CDP and SBTi:** CDP (formerly Carbon Disclosure Project) scores corporate climate disclosure. Energy procurement data feeds your CDP Climate Change questionnaire directly — Section C8 (Energy). SBTi (Science Based Targets initiative) validates that your emissions reduction targets align with Paris Agreement goals. Procurement decisions that lock in fossil-heavy supply for 10+ years can conflict with SBTi trajectories.
+
+### Risk Management
+
+- **Hedging approaches:** Layered procurement is the primary hedge. Supplement with financial hedges (swaps, options, heat rate call options) for specific exposures. Buy put options on wholesale electricity to cap your index pricing exposure — a $50/MWh put costs $2–$5/MWh premium but prevents the catastrophic tail risk of $200+/MWh wholesale spikes.
+- **Budget certainty vs. market exposure:** The fundamental tradeoff. Fixed-price contracts provide certainty at a premium. Index contracts provide lower average cost at higher variance. Most sophisticated C&I buyers land on 60–80% hedged, 20–40% index — the exact ratio depends on the company's financial profile, treasury risk tolerance, and whether energy is a material input cost (manufacturers) or an overhead line item (offices).
+- **Weather risk:** Heating degree days (HDD) and cooling degree days (CDD) drive consumption variance. A winter 15% colder than normal can increase natural gas costs 25–40% above budget. Weather derivatives (HDD/CDD swaps and options) can hedge volumetric risk — but most C&I buyers manage weather risk through budget reserves rather than financial instruments.
+- **Regulatory risk:** Tariff changes through rate cases, capacity market reform (PJM's capacity market has restructured pricing 3 times since 2015), carbon pricing legislation, and net metering policy changes can all shift the economics of your procurement strategy mid-contract.
+
+## Decision Frameworks
+
+### Procurement Strategy Selection
+
+When choosing between fixed, index, and block-and-index for a contract renewal:
+
+1. **What is the company's tolerance for budget variance?** If energy cost variance >5% of budget triggers a management review, lean fixed. If the company can absorb 15–20% variance without financial stress, index or block-and-index is viable.
+2. **Where is the market in the price cycle?** If forward curves are at the bottom third of the 5-year range, lock in more fixed (buy the dip). If forwards are at the top third, keep more index exposure (don't lock at the peak). If uncertain, layer.
+3. **What is the contract tenor?** For 12-month terms, fixed vs. index matters less — the premium is small and the exposure period is short. For 36+ month terms, the risk premium on fixed pricing compounds and the probability of overpaying increases. Lean hybrid or layered for longer tenors.
+4. **What is the facility's load factor?** High load factor (>0.75): block-and-index works well — buy flat blocks around the clock. Low load factor (<0.50): shaped blocks or TOU-indexed products better match the load profile.
+
+### PPA Evaluation
+
+Before committing to a 10–25 year PPA, evaluate:
+
+1. **Does the project economics pencil?** Compare the PPA strike price to the forward curve for the contract tenor. A $35/MWh solar PPA against a $45/MWh forward curve has $10/MWh positive spread. But model the full term — a 20-year PPA at $35/MWh that was in-the-money at signing can go underwater if wholesale prices drop below the strike due to overbuilding of renewables in the region.
+2. **What is the basis risk?** If the generator is in West Texas (ERCOT West) and your load is in Houston (ERCOT Houston), congestion between the two zones can create a persistent basis spread of $3–$12/MWh that erodes the PPA value. Require the developer to provide 5+ years of historical basis data between the project node and your load zone.
+3. **What is the curtailment exposure?** ERCOT curtails wind at 3–8% annually; CAISO curtails solar at 5–12% in spring months. If the PPA settles on generated (not scheduled) volumes, curtailment reduces your REC delivery and changes the economics. Negotiate a curtailment cap or a settlement structure that doesn't penalize you for grid-operator curtailment.
+4. **What are the credit requirements?** Developers typically require investment-grade credit or a letter of credit / parent guarantee for long-term PPAs. A $50M notional VPPA may require a $5–$10M LC, tying up capital. Factor the LC cost into your PPA economics.
+
+### Demand Charge Mitigation ROI
+
+Evaluate demand charge reduction investments using total stacked value:
+
+1. Calculate current demand charges: Peak kW × demand rate × 12 months.
+2. Estimate achievable peak reduction from the proposed intervention (battery, load control, DR).
+3. Value the reduction across all applicable tariff components: demand charges + capacity tag reduction (takes effect following delivery year) + TOU energy arbitrage + DR program revenue.
+4. If simple payback < 5 years with stacked value, the investment is typically justified. If 5–8 years, it's marginal and depends on capital availability. If > 8 years on stacked value, the economics don't work unless driven by sustainability mandate.
+
+### Market Timing
+
+Never try to "call the bottom" on energy markets. Instead:
+
+- Monitor the forward curve relative to the 5-year historical range. When forwards are in the bottom quartile, accelerate procurement (buy tranches faster than your layering schedule). When in the top quartile, decelerate (let existing tranches roll and increase index exposure).
+- Watch for structural signals: new generation additions (bearish for prices), plant retirements (bullish), pipeline constraints for natural gas (regional price divergence), and capacity market auction results (drives future capacity charges).
+
+For the complete decision framework library, see [decision-frameworks.md](references/decision-frameworks.md).
+
+## Key Edge Cases
+
+These are situations where standard procurement playbooks produce poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **ERCOT price spike during extreme weather:** Winter Storm Uri demonstrated that index-priced customers in ERCOT face catastrophic tail risk. A 5 MW facility on index pricing incurred $1.5M+ in a single week. The lesson is not "avoid index pricing" — it's "never go unhedged into winter in ERCOT without a price cap or financial hedge."
+
+2. **Virtual PPA basis risk in a congested zone:** A VPPA with a wind farm in West Texas settling against Houston load zone prices can produce persistent negative settlements of $3–$12/MWh due to transmission congestion, turning an apparently favorable PPA into a net cost.
+
+3. **Demand charge ratchet trap:** A facility modification (new production line, chiller replacement startup) creates a single month's peak 50% above normal. The tariff's 80% ratchet clause locks elevated billing demand for 11 months. A $200K annual cost increase from a single 15-minute interval.
+
+4. **Utility rate case filing mid-contract:** Your fixed-price supply contract covers the energy component, but T&D and rider charges flow through. A utility rate case adds $0.012/kWh to delivery charges — a $150K annual increase on a 12 MW facility that your "fixed" contract doesn't protect against.
+
+5. **Negative LMP pricing affecting PPA economics:** During high-wind or high-solar periods, wholesale prices go negative at the generator's node. Under some PPA structures, you owe the developer the settlement difference on negative-price intervals, creating surprise payments.
+
+6. **Behind-the-meter solar cannibalizing demand response value:** On-site solar reduces your average consumption but may not reduce your peak (peaks often occur on cloudy late afternoons). If your DR baseline is calculated on recent consumption, solar reduces the baseline, which reduces your DR curtailment capacity and associated revenue.
+
+7. **Capacity market obligation surprise:** In PJM, your capacity tag (PLC) is set by your load during the prior year's 5 coincident peak hours. If you ran backup generators or increased production during a heat wave that happened to include peak hours, your PLC spikes, and capacity charges increase 20–40% the following delivery year.
+
+8. **Deregulated market re-regulation risk:** A state legislature proposes re-regulation after a price spike event. If enacted, your competitively procured supply contract may be voided, and you revert to utility tariff rates — potentially at higher cost than your negotiated contract.
+
+## Communication Patterns
+
+### Supplier Negotiations
+
+Energy supplier negotiations are multi-year relationships. Calibrate tone:
+
+- **RFP issuance:** Professional, data-rich, competitive. Provide complete interval data and load profiles. Suppliers who can't model your load accurately will pad their margins. Transparency reduces risk premiums.
+- **Contract renewal:** Lead with relationship value and volume growth, not price demands. "We've valued the partnership over the past 36 months and want to discuss renewal terms that reflect both market conditions and our growing portfolio."
+- **Price challenges:** Reference specific market data. "ICE forward curves for 2027 are showing $42/MWh for AEP Dayton Hub. Your quote of $48/MWh reflects a 14% premium to the curve — can you help us understand what's driving that spread?"
+
+### Internal Stakeholders
+
+- **Finance/treasury:** Quantify decisions in terms of budget impact, variance, and risk. "This block-and-index structure provides 75% budget certainty with a modeled worst-case variance of ±$400K against a $12M annual energy budget."
+- **Sustainability:** Map procurement decisions to Scope 2 targets. "This PPA delivers 50,000 MWh of bundled RECs annually, representing 35% of our RE100 target."
+- **Operations:** Focus on operational requirements and constraints. "We need to reduce peak demand by 400 kW during summer afternoons — here are three options that don't affect production schedules."
+
+For full communication templates, see [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+| Trigger | Action | Timeline |
+| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ---------------------- |
+| Wholesale prices exceed 2× budget assumption for 5+ consecutive days | Notify finance, evaluate hedge position, consider emergency fixed-price procurement | Within 24 hours |
+| Supplier credit downgrade below investment grade | Review contract termination provisions, assess replacement supplier options | Within 48 hours |
+| Utility rate case filed with >10% proposed increase | Engage regulatory counsel, evaluate intervention filing | Within 1 week |
+| Demand peak exceeds ratchet threshold by >15% | Investigate root cause with operations, model billing impact, evaluate mitigation | Within 24 hours |
+| PPA developer misses REC delivery by >10% of contracted volume | Issue notice of default per contract, evaluate replacement REC procurement | Within 5 business days |
+| Capacity tag (PLC) increases >20% from prior year | Analyze coincident peak intervals, model capacity charge impact, develop peak response plan | Within 2 weeks |
+| Regulatory action threatens contract enforceability | Engage legal counsel, evaluate contract force majeure provisions | Within 48 hours |
+| Grid emergency / rolling blackouts affecting facilities | Activate emergency load curtailment, coordinate with operations, document for insurance | Immediate |
+
+### Escalation Chain
+
+Energy Analyst → Energy Procurement Manager (24 hours) → Director of Procurement (48 hours) → VP Finance/CFO (>$500K exposure or long-term commitment >5 years)
+
+## Performance Indicators
+
+Track monthly, review quarterly with finance and sustainability:
+
+| Metric | Target | Red Flag |
+| -------------------------------------------------------------------------- | ----------------------------- | ---------------------- |
+| Weighted average energy cost vs. budget | Within ±5% | >10% variance |
+| Procurement cost vs. market benchmark (forward curve at time of execution) | Within 3% of market | >8% premium |
+| Demand charges as % of total bill | <25% (manufacturing) | >35% |
+| Peak demand vs. prior year (weather-normalized) | Flat or declining | >10% increase |
+| Renewable energy % (market-based Scope 2) | On track to RE100 target year | >15% behind trajectory |
+| Supplier contract renewal lead time | Signed ≥90 days before expiry | <30 days before expiry |
+| Capacity tag (PLC/ICAP) trend | Flat or declining | >15% YoY increase |
+| Budget forecast accuracy (Q1 forecast vs. actuals) | Within ±7% | >12% miss |
+
+## Additional Resources
+
+- For detailed decision frameworks on procurement strategy, PPA evaluation, hedging, and multi-facility optimization, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For communication templates covering RFPs, PPA negotiations, rate cases, and internal reporting, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design, audit, or optimise an energy procurement strategy** for commercial or industrial facilities:
+
+- Evaluating fixed vs. index vs. block-and-index contracts, PPAs, or VPPAs.
+- Reducing demand charges, managing capacity tags, or planning DR and battery investments.
+- Preparing RFPs, supplier negotiations, or executive decision memos about multi-site energy strategy, risk, and sustainability tradeoffs.
diff --git a/skills/energy-procurement/references/communication-templates.md b/skills/energy-procurement/references/communication-templates.md
new file mode 100644
index 00000000..b3170bf1
--- /dev/null
+++ b/skills/energy-procurement/references/communication-templates.md
@@ -0,0 +1,492 @@
+# Communication Templates — Energy Procurement
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing energy procurement communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by communication type and business context. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RFP to Energy Suppliers](#1-rfp-to-energy-suppliers)
+2. [PPA Term Sheet Response](#2-ppa-term-sheet-response)
+3. [Utility Rate Case Intervention Comment](#3-utility-rate-case-intervention-comment)
+4. [Demand Response Program Enrollment](#4-demand-response-program-enrollment)
+5. [Budget Forecast Presentation](#5-budget-forecast-presentation)
+6. [Sustainability Report — Energy Section](#6-sustainability-report--energy-section)
+7. [Internal Energy Cost Variance Analysis](#7-internal-energy-cost-variance-analysis)
+8. [Supplier Contract Renewal Negotiation](#8-supplier-contract-renewal-negotiation)
+9. [Regulatory Filing Comment](#9-regulatory-filing-comment)
+10. [Board-Level Energy Strategy Summary](#10-board-level-energy-strategy-summary)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{our_company}}` | Our company legal name | `Meridian Manufacturing Corp.` |
+| `{{our_contact_name}}` | Our representative name | `Jennifer Walsh` |
+| `{{our_contact_title}}` | Our representative title | `Director of Energy Procurement` |
+| `{{our_contact_email}}` | Our representative email | `jwalsh@meridian.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(614) 555-0247` |
+| `{{supplier_name}}` | Energy supplier name | `NorthStar Energy Solutions` |
+| `{{supplier_contact}}` | Supplier contact name | `David Chen` |
+| `{{supplier_contact_title}}` | Supplier contact title | `VP, Commercial Sales` |
+| `{{utility_name}}` | Utility company name | `AEP Ohio` |
+| `{{iso_name}}` | ISO/RTO name | `PJM Interconnection` |
+| `{{facility_name}}` | Facility name | `Columbus Manufacturing Plant` |
+| `{{facility_address}}` | Facility address | `4500 Industrial Parkway, Columbus, OH 43228` |
+| `{{account_number}}` | Utility account number | `110-485-7723` |
+| `{{annual_consumption_mwh}}` | Annual electricity consumption | `42,000 MWh` |
+| `{{peak_demand_kw}}` | Peak demand in kW | `6,200 kW` |
+| `{{current_rate}}` | Current contract rate | `$0.058/kWh` |
+| `{{proposed_rate}}` | Proposed new rate | `$0.054/kWh` |
+| `{{market_rate}}` | Market benchmark rate | `$0.062/kWh` |
+| `{{contract_start}}` | Contract start date | `2027-01-01` |
+| `{{contract_end}}` | Contract end date | `2029-12-31` |
+| `{{rfp_deadline}}` | RFP response deadline | `2026-05-15` |
+| `{{ppa_project_name}}` | Renewable project name | `Prairie Wind Farm II` |
+| `{{ppa_capacity_mw}}` | PPA project capacity | `150 MW` |
+| `{{ppa_strike_price}}` | PPA strike price | `$34/MWh` |
+| `{{ppa_term_years}}` | PPA contract term | `15 years` |
+| `{{re_percentage}}` | Current renewable energy percentage | `38%` |
+| `{{re_target}}` | RE100 target year | `2030` |
+| `{{docket_number}}` | Regulatory docket number | `Case No. 26-1234-EL-AIR` |
+| `{{budget_year}}` | Budget forecast year | `2027` |
+| `{{total_energy_spend}}` | Total annual energy spend | `$14.2M` |
+| `{{num_facilities}}` | Number of facilities | `18` |
+
+---
+
+## 1. RFP to Energy Suppliers
+
+**Channel:** Email with attached RFP document
+**Audience:** Retail energy provider sales/pricing team
+**Tone:** Professional, data-rich, competitive. You're offering a significant commercial opportunity — present it as such.
+
+---
+
+**Subject:** `Invitation to Bid — {{our_company}} Electricity Supply RFP — {{contract_start}} Start`
+
+{{supplier_contact}},
+
+{{our_company}} is conducting a competitive electricity supply procurement for {{num_facilities}} facilities across {{iso_name}} territory. We are inviting {{supplier_name}} to participate based on your market position and capabilities in our service territory.
+
+**RFP Summary:**
+- **Scope:** {{num_facilities}} commercial and industrial facilities
+- **Total annual consumption:** {{annual_consumption_mwh}}
+- **Aggregate peak demand:** {{peak_demand_kw}}
+- **Contract period:** {{contract_start}} through {{contract_end}}
+- **Product structures requested:** Fixed-price full requirements, block-and-index, and index with price cap
+- **Bid deadline:** {{rfp_deadline}}, 5:00 PM ET
+
+**Included with this invitation:**
+1. RFP response template (Excel) with site-level detail
+2. 36 months of 15-minute interval data for each facility (CSV)
+3. Current tariff information and utility account numbers
+4. Evaluation criteria and weighting
+
+**Evaluation criteria:**
+- Total cost across three price scenarios (40%)
+- Supplier credit quality and financial stability (20%)
+- Contract flexibility including volume tolerance and early termination provisions (15%)
+- Sustainability services — REC sourcing, carbon reporting, PPA advisory (15%)
+- Market intelligence and advisory capabilities (10%)
+
+**Key requirements:**
+- All bids must include volume tolerance of ±10% minimum
+- Pricing must be provided for all three product structures independently
+- Supplier must demonstrate minimum BBB credit rating or equivalent
+- RECs must be sourced from projects within the {{iso_name}} footprint
+
+Please confirm your intent to participate by {{rfp_confirmation_date}}. Clarification questions will be accepted through {{rfp_questions_deadline}} via email to {{our_contact_email}}.
+
+We look forward to {{supplier_name}}'s participation.
+
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+**Tone Notes:**
+- Do not share current pricing with bidders. "Current contract details are confidential" is the standard response.
+- Do not disclose the number of bidders. "We have invited a competitive field" is sufficient.
+- Respond to all clarification questions in a consolidated Q&A sent to all bidders simultaneously to maintain fairness.
+
+---
+
+## 2. PPA Term Sheet Response
+
+**Channel:** Email to developer's commercial team
+**Audience:** Renewable energy project developer
+**Tone:** Collaborative but commercially rigorous. PPAs are 10-25 year commitments — every term matters.
+
+---
+
+**Subject:** `{{our_company}} Response to {{ppa_project_name}} Term Sheet — Commercial Feedback`
+
+{{developer_contact}},
+
+Thank you for the term sheet for {{ppa_project_name}} ({{ppa_capacity_mw}}). We've completed our initial review and have the following feedback organized by commercial, financial, and operational terms.
+
+**Commercial Terms:**
+- **Strike price:** The proposed {{ppa_strike_price}} is within our target range based on current forward curves. We would like to discuss a price escalator structure — 0% escalation for years 1-5 with a [CPI-linked / fixed 1.5%] escalator beginning year 6.
+- **Settlement point:** We request settlement at the {{iso_name}} [load zone / hub] rather than the project node, to reduce our basis risk exposure. We understand this may require a price adjustment and are prepared to discuss.
+- **Contract volume:** We would like to discuss a partial offtake ({{our_offtake_mw}} MW of the {{ppa_capacity_mw}} project) with right of first refusal on additional capacity.
+
+**Risk Allocation:**
+- **Curtailment:** We request that the developer bear curtailment risk for the first 5% annually, with shared risk (50/50) for curtailment between 5-10%, and developer risk above 10%. The current term sheet allocates all curtailment risk to the offtaker, which is not acceptable for a {{ppa_term_years}}-year commitment.
+- **Negative pricing:** We require a negative price floor provision: during intervals when the settlement point LMP is negative, no settlement occurs (neither party pays). This protects both parties from volatile negative pricing hours.
+- **Change of law:** The term sheet's change-of-law provision is one-sided. We propose mutual termination rights if a regulatory change materially affects the economics for either party, with a defined materiality threshold of {{materiality_threshold}}.
+
+**Financial and Credit:**
+- **Credit support:** We are prepared to provide [a parent guarantee / an LC] for an amount equal to {{credit_support_amount}}, sized to 2 years of potential negative mark-to-market exposure under our stress scenario.
+- **Accounting treatment:** We require confirmation that the PPA structure qualifies for normal purchases and normal sales (NPNS) exception under ASC 815, or alternatively that hedge accounting is achievable. Our treasury team will need to review the final contract with our auditors.
+
+**REC Provisions:**
+- **Vintage delivery:** RECs must be delivered within 12 months of generation to maintain RE100 compliance.
+- **Replacement RECs:** If the project underdelivers RECs by more than 10% in any year, the developer provides replacement RECs from a comparable facility at no additional cost.
+
+We would welcome a call this week to discuss these points. Please suggest availability.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+**Tone Notes:**
+- PPA negotiations are multi-round. The first response should establish your key positions without ultimatums.
+- Always frame risk allocation as "fair to both parties" rather than "we won't accept your risk."
+- Developers receive dozens of term sheet responses — be specific and organized to stand out as a serious offtaker.
+
+---
+
+## 3. Utility Rate Case Intervention Comment
+
+**Channel:** Formal filing with state Public Utility Commission
+**Audience:** PUC commissioners, administrative law judge, utility regulatory staff
+**Tone:** Formal, data-driven, legally precise. This is a regulatory proceeding — opinions must be supported by evidence.
+
+---
+
+**Re:** {{docket_number}} — {{utility_name}} Application for Rate Increase
+
+**Before the {{state}} Public Utilities Commission**
+
+**Comments of {{our_company}}**
+
+{{our_company}} respectfully submits these comments regarding {{utility_name}}'s application for a general rate increase filed on {{filing_date}}.
+
+**I. Interest of {{our_company}}**
+
+{{our_company}} operates {{num_facilities}} facilities in {{utility_name}}'s service territory, consuming approximately {{annual_consumption_mwh}} annually under rate schedule {{rate_schedule}}. The proposed rate increase would impose an estimated additional cost of ${{annual_impact}} per year on {{our_company}}'s operations.
+
+**II. Summary of Concerns**
+
+{{our_company}} does not oppose {{utility_name}}'s right to recover prudently incurred costs and earn a fair return. However, we raise the following concerns regarding the application as filed:
+
+1. **Requested return on equity (ROE):** {{utility_name}} requests a {{requested_roe}}% ROE. Recent commission decisions in comparable proceedings in {{comparable_states}} have authorized ROEs of {{comparable_roe_range}}%. We respectfully submit that the requested ROE exceeds the range supported by current capital market conditions.
+
+2. **Rate design:** The proposed rate design increases the volumetric energy charge by {{energy_increase_pct}}% while reducing the demand charge by only {{demand_decrease_pct}}%. This cost allocation methodology disadvantages high-load-factor industrial customers who contribute less to system peak on a per-kWh basis. We recommend cost allocation based on demonstrated cost causation, using a coincident peak methodology for demand-related costs.
+
+3. **Rider pass-through timing:** The proposed infrastructure improvement rider allows for quarterly rate adjustments without commission review. We request that any rider mechanism include an annual true-up with commission review and a cumulative cap of {{rider_cap_pct}}% to prevent rate shock.
+
+**III. Requested Relief**
+
+{{our_company}} requests that the Commission:
+- Set ROE at the midpoint of comparable authorized returns (approximately {{recommended_roe}}%)
+- Adopt a coincident-peak cost allocation methodology for the {{rate_schedule}} rate class
+- Include annual commission review and a cumulative cap on the proposed infrastructure rider
+
+{{our_contact_name}}
+{{our_contact_title}}, {{our_company}}
+
+---
+
+## 4. Demand Response Program Enrollment
+
+**Channel:** Formal enrollment application
+**Audience:** Utility or ISO demand response program administrator
+**Tone:** Technical, precise. DR enrollment documents are contractual — accuracy matters.
+
+---
+
+**Subject:** `Demand Response Program Enrollment Application — {{facility_name}}`
+
+To: {{dr_program_administrator}}
+
+{{our_company}} hereby applies to enroll {{facility_name}} in the {{dr_program_name}} for the {{delivery_year}} delivery year.
+
+**Facility Information:**
+- **Facility:** {{facility_name}}
+- **Address:** {{facility_address}}
+- **Utility account:** {{account_number}}
+- **Meter ID:** {{meter_id}}
+- **Service voltage:** {{service_voltage}}
+- **Current peak demand:** {{peak_demand_kw}}
+
+**Curtailment Capability:**
+- **Committed curtailment capacity:** {{dr_commitment_kw}} kW
+- **Minimum notification time required:** {{notification_minutes}} minutes
+- **Maximum curtailment duration:** {{max_duration_hours}} hours
+- **Curtailment method:** [Load shedding via BAS / Backup generation / Battery discharge / Combination]
+- **Loads available for curtailment:** {{curtailable_loads}}
+- **Loads NOT available for curtailment (critical process):** {{non_curtailable_loads}}
+
+**Baseline Methodology:**
+We request the {{baseline_method}} baseline calculation methodology. Attached is a 12-month interval data file demonstrating our typical load profile during the DR event window ({{event_window}}).
+
+**Testing:**
+We are available for an enrollment verification test during the week of {{test_week}}. We can demonstrate the full {{dr_commitment_kw}} kW curtailment within {{notification_minutes}} minutes of notification.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+## 5. Budget Forecast Presentation
+
+**Channel:** Internal presentation (PowerPoint / memo)
+**Audience:** CFO, VP Finance, Budget Committee
+**Tone:** Precise, scenario-based, action-oriented. Finance wants numbers, ranges, and decision points — not energy market tutorials.
+
+---
+
+### {{budget_year}} Energy Cost Forecast — {{our_company}}
+
+**Prepared by:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{forecast_date}}
+**Scope:** {{num_facilities}} facilities, all electricity and natural gas
+
+**Executive Summary:**
+The {{budget_year}} total energy spend is forecast at **${{base_case_total}}** under base case assumptions, representing a {{yoy_change_pct}}% [increase/decrease] from {{prior_year}} actuals of ${{prior_year_total}}. The forecast range under stress scenarios is **${{low_case_total}}** to **${{high_case_total}}**.
+
+| Component | {{prior_year}} Actual | {{budget_year}} Base Case | Change |
+|-----------|---------------------|--------------------------|--------|
+| Electricity — supply | ${{elec_supply_prior}} | ${{elec_supply_forecast}} | {{elec_supply_change}} |
+| Electricity — delivery (T&D) | ${{elec_delivery_prior}} | ${{elec_delivery_forecast}} | {{elec_delivery_change}} |
+| Electricity — demand charges | ${{demand_charges_prior}} | ${{demand_charges_forecast}} | {{demand_change}} |
+| Electricity — capacity charges | ${{capacity_prior}} | ${{capacity_forecast}} | {{capacity_change}} |
+| Natural gas | ${{gas_prior}} | ${{gas_forecast}} | {{gas_change}} |
+| RECs / sustainability | ${{rec_prior}} | ${{rec_forecast}} | {{rec_change}} |
+| **Total** | **${{prior_year_total}}** | **${{base_case_total}}** | **{{total_change}}** |
+
+**Key Assumptions:**
+- Electricity forward curve: {{forward_curve_source}} as of {{curve_date}}
+- Natural gas: Henry Hub {{gas_assumption}} + basis of {{basis_assumption}}
+- Weather: 10-year normal HDD/CDD
+- Production volume: [flat / {{production_change}}% change] vs. prior year
+- Hedged position: {{hedge_pct}}% of electricity volume locked at ${{hedged_rate}}/MWh
+
+**Scenario Analysis:**
+
+| Scenario | Electricity Cost | Gas Cost | Total | vs. Base Case |
+|----------|-----------------|----------|-------|---------------|
+| Base case | ${{elec_base}} | ${{gas_base}} | ${{base_case_total}} | — |
+| Mild winter / cool summer | ${{elec_low}} | ${{gas_low}} | ${{low_case_total}} | {{low_delta}} |
+| Severe winter / hot summer | ${{elec_high}} | ${{gas_high}} | ${{high_case_total}} | {{high_delta}} |
+| Market stress (2× forward) | ${{elec_stress}} | ${{gas_stress}} | ${{stress_total}} | {{stress_delta}} |
+
+**Decisions Requested:**
+1. Approve the base case budget of ${{base_case_total}}
+2. Authorize procurement of an additional {{additional_hedge_pct}}% hedge to bring total hedged position to {{target_hedge_pct}}%
+3. Approve ${{capex_amount}} capital budget for demand charge mitigation at {{capex_facilities}}
+
+---
+
+## 6. Sustainability Report — Energy Section
+
+**Channel:** Annual sustainability / ESG report
+**Audience:** Investors, customers, ESG rating agencies, RE100, CDP
+**Tone:** Transparent, data-backed, forward-looking. Avoid greenwashing — ESG audiences are sophisticated.
+
+---
+
+### Energy and Climate — {{report_year}}
+
+**Scope 2 Emissions:**
+
+| Metric | {{prior_year}} | {{report_year}} | Change |
+|--------|---------------|-----------------|--------|
+| Total electricity consumed (MWh) | {{elec_prior_mwh}} | {{elec_current_mwh}} | {{elec_change_pct}} |
+| Scope 2 — Location-based (MT CO₂e) | {{scope2_loc_prior}} | {{scope2_loc_current}} | {{scope2_loc_change}} |
+| Scope 2 — Market-based (MT CO₂e) | {{scope2_mkt_prior}} | {{scope2_mkt_current}} | {{scope2_mkt_change}} |
+| Renewable electricity (%) | {{re_pct_prior}} | {{re_pct_current}} | {{re_change}} |
+
+**Renewable Energy Procurement:**
+
+| Instrument | Volume (MWh) | Source | Additionality |
+|-----------|-------------|--------|---------------|
+| Physical PPA | {{phys_ppa_mwh}} | {{phys_ppa_project}} | New project, operational {{ppa_cod}} |
+| Virtual PPA (RECs) | {{vppa_rec_mwh}} | {{vppa_project}} | New project, {{vppa_location}} |
+| Utility green tariff | {{green_tariff_mwh}} | {{green_tariff_utility}} | Program-dependent |
+| Unbundled RECs | {{unbundled_rec_mwh}} | National wind | Market RECs |
+| On-site solar | {{onsite_mwh}} | {{onsite_locations}} | Direct generation |
+
+**RE100 Progress:** {{our_company}} has achieved {{re_pct_current}}% renewable electricity in {{report_year}}, on track for our commitment of 100% by {{re_target}}.
+
+**Forward-Looking Targets:**
+- {{re_target_next_year}}% renewable electricity by end of {{next_year}}
+- Execute additional {{next_ppa_mw}} MW of renewable procurement by Q2 {{next_year}}
+- Reduce Scope 2 market-based emissions by {{scope2_reduction_target}}% by {{target_year}} (vs. {{baseline_year}} baseline)
+
+---
+
+## 7. Internal Energy Cost Variance Analysis
+
+**Channel:** Monthly internal memo
+**Audience:** Finance controller, plant managers, VP Operations
+**Tone:** Analytical, action-oriented. Explain the "why" behind variances and what's being done about them.
+
+---
+
+**Subject:** `Energy Cost Variance Report — {{month}} {{year}}`
+
+**Summary:** Total energy cost of ${{actual_total}} vs. budget of ${{budget_total}} — variance of ${{variance}} ({{variance_pct}}).
+
+**Variance Decomposition:**
+
+| Driver | Impact | Explanation |
+|--------|--------|-------------|
+| Weather (HDD/CDD vs. normal) | ${{weather_impact}} | {{month}} was {{weather_description}} — {{hdd_cdd_actual}} vs. {{hdd_cdd_budget}} budgeted HDD/CDD |
+| Market price (index exposure) | ${{market_impact}} | Day-ahead LMP averaged ${{actual_lmp}}/MWh vs. budget assumption of ${{budget_lmp}}/MWh |
+| Demand charges | ${{demand_impact}} | Peak demand of {{actual_peak_kw}} kW vs. budget of {{budget_peak_kw}} kW at {{facility_name}} |
+| Production volume | ${{volume_impact}} | Production hours {{production_description}} vs. plan |
+| Rate/tariff changes | ${{tariff_impact}} | {{tariff_description}} |
+
+**Actions Taken:**
+1. {{action_1}}
+2. {{action_2}}
+3. {{action_3}}
+
+**Forecast Revision:** Based on YTD actuals, the full-year energy cost forecast is revised to ${{revised_forecast}} (previously ${{prior_forecast}}). Primary driver: {{revision_driver}}.
+
+---
+
+## 8. Supplier Contract Renewal Negotiation
+
+**Channel:** Email
+**Audience:** Incumbent energy supplier's commercial team
+**Tone:** Relationship-forward, data-informed. You want to renew if terms are fair — make that clear while establishing competitive tension.
+
+---
+
+**Subject:** `Contract Renewal Discussion — {{our_company}} / {{supplier_name}} — {{contract_end}} Expiration`
+
+{{supplier_contact}},
+
+Our current supply agreement expires {{contract_end}}, and we'd like to discuss renewal terms. {{supplier_name}} has been a valued partner for the past {{contract_duration}}, and we'd like to continue the relationship under commercially competitive terms.
+
+To frame the discussion, here is our perspective on renewal:
+
+**What's worked well:**
+- Billing accuracy and operational execution have been excellent
+- Market intelligence updates have been valuable for our procurement planning
+- The account management team has been responsive and proactive
+
+**Where we'd like to see improvement:**
+- Our current rate of {{current_rate}} was competitive at signing but the forward curve for the renewal period ({{contract_start}} through {{new_contract_end}}) is currently {{market_rate}} — we need renewal pricing that reflects current market conditions
+- We'd like to discuss [block-and-index structure / increased volume tolerance / REC bundling] for the renewal term
+
+**Our process:**
+We are conducting a competitive evaluation for this renewal. We've invited {{num_bidders}} suppliers to provide indicative pricing. Our decision timeline:
+- Indicative pricing review: {{pricing_review_date}}
+- Shortlist and final negotiation: {{negotiation_date}}
+- Contract execution: {{execution_date}}
+
+We would welcome a call on {{proposed_call_date}} to discuss {{supplier_name}}'s renewal offer. Please send indicative pricing for the structures outlined above by {{pricing_deadline}}.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+**Tone Notes:**
+- Name the competitive process but don't bluff about the number of bidders.
+- Lead with what's worked well — the incumbent relationship has value and you should acknowledge it.
+- Be transparent about timeline so the supplier can allocate pricing resources.
+
+---
+
+## 9. Regulatory Filing Comment
+
+**Channel:** Written comment to regulatory body (FERC, state PUC, ISO stakeholder process)
+**Audience:** Regulatory commissioners, ISO market design team
+**Tone:** Policy-oriented, evidence-based. Regulators respect commenters who understand the market mechanics.
+
+---
+
+**Re:** {{docket_number}} — Proposed Modifications to {{program_or_rule}}
+
+{{our_company}} appreciates the opportunity to comment on the proposed modifications to {{program_or_rule}}.
+
+As a large commercial and industrial electricity consumer in {{iso_name}} territory with {{annual_consumption_mwh}} of annual consumption, {{our_company}} has a direct interest in market designs that promote efficient price formation, reliable capacity procurement, and equitable cost allocation.
+
+**Support / Concern:**
+{{our_company}} [supports / has concerns regarding] the proposed modifications, specifically:
+
+1. **{{provision_1}}:** [Position and rationale with specific reference to the proposal's impact on C&I consumers]
+2. **{{provision_2}}:** [Position with quantitative impact estimate if available]
+3. **{{provision_3}}:** [Position with alternative proposal if opposing]
+
+**Recommendation:**
+{{our_company}} recommends that the Commission [approve with modifications / reject / defer pending further analysis] the proposed {{program_or_rule}} changes, specifically incorporating the following modifications:
+- {{recommendation_1}}
+- {{recommendation_2}}
+
+Respectfully submitted,
+
+{{our_contact_name}}
+{{our_contact_title}}, {{our_company}}
+
+---
+
+## 10. Board-Level Energy Strategy Summary
+
+**Channel:** Board meeting memo / presentation
+**Audience:** Board of Directors, CEO, CFO
+**Tone:** Strategic, concise, decision-focused. The board cares about risk, cost trajectory, sustainability commitments, and capital allocation — not market mechanics.
+
+---
+
+### Energy Strategy Update — {{quarter}} {{year}}
+
+**For the Board of Directors, {{our_company}}**
+
+**Key Metrics:**
+
+| Metric | Current | Target | Status |
+|--------|---------|--------|--------|
+| Annual energy spend | ${{current_spend}} | ${{target_spend}} | {{spend_status}} |
+| Energy cost as % of revenue | {{energy_pct_revenue}}% | {{target_pct}}% | {{pct_status}} |
+| Renewable electricity (RE100) | {{re_pct_current}}% | 100% by {{re_target}} | {{re_status}} |
+| Scope 2 emissions (market-based) | {{current_emissions}} MT CO₂e | {{target_emissions}} MT | {{emissions_status}} |
+
+**Strategic Priorities:**
+1. **Cost management:** [1-2 sentence summary of procurement strategy and results]
+2. **Sustainability:** [1-2 sentence summary of RE100 progress and next milestones]
+3. **Risk management:** [1-2 sentence summary of hedge position and market outlook]
+
+**Decisions Requested:**
+1. Approve execution of a {{ppa_term_years}}-year virtual PPA with {{ppa_project_name}} at {{ppa_strike_price}} for {{ppa_capacity_mw}} MW — projected NPV of ${{ppa_npv}} over the contract term, delivering {{ppa_annual_recs}} RECs annually toward our RE100 commitment.
+2. Authorize ${{capex_amount}} in capital expenditure for battery energy storage at {{capex_facilities}} — projected {{payback_years}}-year payback with stacked value of ${{annual_savings}}/year in demand charge and capacity cost reduction.
+
+**Risk Summary:**
+- Market risk: {{hedge_pct}}% hedged through {{hedge_end}}. Unhedged exposure: ${{unhedged_exposure}} at current forwards.
+- Regulatory risk: {{regulatory_summary}}
+- Supplier risk: All supply contracts with investment-grade counterparties. No credit concerns.
+
+**Next Update:** {{next_update_date}}
+
+---
+
+**Tone Notes:**
+- Board communication must be under 2 pages. Provide appendices for detail.
+- Lead with the "ask" — if you need board approval for a PPA or capital project, put it in the executive summary.
+- Quantify everything. "Good progress on sustainability" means nothing. "38% RE, on track for 50% by year-end" means everything.
+- Acknowledge risks explicitly. A board that discovers unmentioned risks loses trust in management.
diff --git a/skills/energy-procurement/references/decision-frameworks.md b/skills/energy-procurement/references/decision-frameworks.md
new file mode 100644
index 00000000..042176b9
--- /dev/null
+++ b/skills/energy-procurement/references/decision-frameworks.md
@@ -0,0 +1,851 @@
+# Decision Frameworks — Energy Procurement
+
+This reference provides detailed decision trees, evaluation matrices, financial models,
+and strategic frameworks for electricity and gas procurement, tariff optimization,
+demand charge management, PPA evaluation, hedging strategy design, and multi-facility
+portfolio optimization. It is loaded on demand when the agent needs to make or
+recommend nuanced energy procurement decisions.
+
+All thresholds, price assumptions, and market benchmarks reflect US commercial and
+industrial electricity and natural gas markets. Adjust for regional markets, current
+forward curves, and facility-specific tariff structures.
+
+---
+
+## 1. Procurement Strategy Selection
+
+### 1.1 Pre-Procurement Intelligence Gathering
+
+Before entering any procurement decision — contract renewal, new facility onboarding,
+or mid-term restructuring — assemble a comprehensive data package.
+
+#### Data Assembly Checklist
+
+| Data Point | Source | Purpose |
+|-----------|--------|---------|
+| 36 months of 15-minute interval data (kWh and kW) | Utility meter data / MDM system | Load shape analysis, peak identification |
+| Current tariff rate schedule and all applicable riders | Utility tariff book / state PUC | Baseline cost structure |
+| Current supply contract terms, expiration, and auto-renewal provisions | Contract file | Timeline and constraints |
+| Forward energy curves (12, 24, 36 month) for relevant hub | ICE, CME, broker quotes | Market benchmark for pricing evaluation |
+| Capacity market auction results (PJM RPM, ISO-NE FCA) | ISO publications | Future capacity charge forecasting |
+| Facility peak load contribution (PLC) or installed capacity (ICAP) tag | Utility / ISO settlement data | Capacity charge exposure |
+| Historical weather data (HDD/CDD) for facility locations | NOAA / weather service | Weather-normalization of consumption |
+| Pending utility rate cases at state PUC | State PUC docket search | Regulatory risk assessment |
+| Corporate sustainability targets and timeline | Sustainability team | Renewable procurement requirements |
+| Capital budget availability for demand-side investments | Finance team | Investment constraint for demand charge mitigation |
+
+### 1.2 Fixed vs. Index vs. Block-and-Index Decision Tree
+
+Use this decision tree for each facility or portfolio segment independently — one
+strategy does not fit all sites.
+
+```
+START: What is the organization's tolerance for energy cost variance?
+
+├── Budget variance >10% triggers executive escalation
+│ ├── Contract tenor ≤ 24 months?
+│ │ └── YES → Fixed-price full requirements
+│ │ - Accept the risk premium (5-12% above forward curve)
+│ │ - Negotiate volume tolerance band (±10-15%)
+│ │ - Ensure contract includes change-of-use provisions
+│ │ └── NO (>24 months) → Fixed-price with annual price resets
+│ │ - Lock year 1 at fixed, years 2-3 at a formula (forward + adder)
+│ │ - This limits the supplier's long-term risk premium
+│
+├── Budget variance of 5-10% is manageable
+│ ├── Facility load factor > 0.70?
+│ │ └── YES → Block-and-index
+│ │ - Buy fixed blocks = 70-80% of baseload
+│ │ - Float remaining 20-30% at index (day-ahead or real-time)
+│ │ - Shape blocks to match base load pattern (ATC vs. on-peak only)
+│ │ └── NO (load factor < 0.70) → Shaped block-and-index
+│ │ - Buy on-peak blocks only (match production schedule)
+│ │ - Float off-peak and shoulder at index
+│ │ - Supplement with TOU-indexed product for off-peak
+│
+├── Organization can tolerate >15% variance (energy is <5% of COGS)
+│ ├── Internal capability to monitor wholesale markets?
+│ │ └── YES → Index pricing with financial hedges
+│ │ - Base product: real-time or day-ahead index + supplier adder
+│ │ - Layer financial hedges: buy call options for peak months
+│ │ - Set a price ceiling through options ($X/MWh cap)
+│ │ └── NO → Index with a price cap product
+│ │ - Supplier provides index pricing with a contractual ceiling
+│ │ - Cap premium is typically $3-7/MWh above forward curve
+│ │ - Simpler than managing separate financial hedges
+```
+
+### 1.3 Layered Procurement Methodology
+
+Layering eliminates single-point market timing risk. The methodology:
+
+**Step 1: Determine the hedging horizon.**
+Most C&I buyers layer 18–36 months ahead of the delivery period. For a January 2028
+start date, begin buying tranches in July 2026.
+
+**Step 2: Set the number of tranches.**
+Standard approaches:
+
+| Tranches | Buying Frequency | Volume per Tranche | Best For |
+|----------|-----------------|-------------------|----------|
+| 4 | Quarterly | 25% | Default approach, good balance |
+| 6 | Bimonthly | ~17% | Large portfolios, higher granularity |
+| 8 | Monthly (final 8 months) | 12.5% | Aggressive dollar-cost averaging |
+| 12 | Monthly | ~8% | Very large portfolios with dedicated procurement staff |
+
+**Step 3: Execution rules.**
+- Execute each tranche at the prevailing market price on the scheduled date — do not try to time within the tranche window.
+- Exception: if the forward curve drops into the bottom 20th percentile of the 5-year range, accelerate by buying 2 tranches immediately ("buy the dip" rule).
+- Exception: if the forward curve spikes into the top 20th percentile, defer the current tranche by 30 days (skip and catch up later).
+- Never defer more than 2 consecutive tranches — rolling deferrals leave you unhedged.
+
+**Step 4: Document and report.**
+Maintain a procurement log showing: tranche date, volume procured, price locked,
+forward curve price at execution, cumulative weighted average price, and remaining
+open position. Report to finance quarterly.
+
+**Example — 10 MW peak load, 60M kWh annual consumption:**
+
+```
+Delivery year: 2028
+Hedging start: July 2026
+Tranches: 6 (bimonthly, ~10M kWh each)
+
+Tranche 1 (Jul 2026): 10M kWh @ $44.50/MWh — Forward was $45.20
+Tranche 2 (Sep 2026): 10M kWh @ $42.80/MWh — Forward was $43.10
+Tranche 3 (Nov 2026): 10M kWh @ $46.30/MWh — Forward was $46.30
+Tranche 4 (Jan 2027): 10M kWh @ $41.20/MWh — Forward was $41.50 (buy-the-dip rule:
+ also executed Tranche 5 early)
+Tranche 5 (Jan 2027): 10M kWh @ $41.40/MWh — Accelerated from March
+Tranche 6 (May 2027): 10M kWh @ $43.80/MWh — Forward was $44.00
+
+Weighted average: $43.33/MWh
+Range of execution prices: $41.20 - $46.30 ($5.10 spread)
+If locked all-at-once in Jul 2026: $44.50/MWh → layering saved $1.17/MWh = $70,200
+```
+
+### 1.4 RFP Process for Deregulated Markets
+
+#### Timeline and Phases
+
+| Phase | Duration | Key Activities |
+|-------|----------|---------------|
+| Pre-RFP Analysis | 2-3 weeks | Load data assembly, tariff analysis, market benchmarking, sustainability requirements definition |
+| RFP Design | 1-2 weeks | Template creation, supplier longlist development, evaluation criteria weighting |
+| RFP Distribution | 1 week | Issue to 5-8 qualified REPs, respond to clarification questions |
+| Bid Window | 2-3 weeks | Suppliers develop pricing based on your interval data and requirements |
+| Bid Evaluation | 1-2 weeks | Total cost modeling, credit assessment, contract review |
+| Negotiation | 1-2 weeks | Shortlist to 2-3, negotiate terms, finalize pricing |
+| Award and Execution | 1 week | Sign contract, notify utility of supplier switch (may require 30-60 day lead time) |
+| **Total** | **9-14 weeks** | |
+
+#### Supplier Evaluation Scoring Matrix
+
+| Criterion | Weight | Scoring Guide |
+|-----------|--------|---------------|
+| Total cost (energy + adder + shaped premium) | 35-45% | Lowest total cost = 100 pts. Each 1% above lowest = -5 pts. Model across 3 price scenarios. |
+| Credit quality | 15-20% | Investment grade (S&P BBB- or above) = 100 pts. Sub-investment grade = 50 pts. No rating / private = 70 pts with parent guarantee, 30 pts without. |
+| Contract flexibility | 10-15% | Volume tolerance ±15% = 100. Volume tolerance ±5% = 50. No tolerance = 0. Early termination available = +20 pts. Change-of-use provisions = +15 pts. |
+| Sustainability services | 10-15% | Bundled RECs from named projects = 100. Unbundled RECs available = 60. No REC options = 0. Carbon reporting support = +20 pts. |
+| Market intelligence and advisory | 5-10% | Dedicated account manager + regular market updates = 100. Account manager only = 50. Call center support = 0. |
+| Operational capability | 5-10% | EDI/API billing integration = 100. Electronic invoicing only = 60. Paper billing = 0. Multi-site consolidated billing = +20 pts. |
+
+#### Bid Comparison Template
+
+For each site, model the annual cost under each supplier's proposal:
+
+```
+Annual Cost = Σ(hourly volume × hourly price) + fixed charges + REC costs + adder fees
+
+Where hourly price depends on product structure:
+ Fixed: contract rate for all hours
+ Block-and-index: block rate for block volume + index price for excess
+ Index: (day-ahead or real-time LMP at load zone) + supplier adder
+```
+
+Always model at three forward price scenarios: base case (current forward curve),
+low case (forward - 20%), and high case (forward + 30%). A supplier whose index
+product looks cheapest at base case may be the most expensive at high case.
+
+---
+
+## 2. PPA Evaluation Framework
+
+### 2.1 Physical PPA Evaluation
+
+Physical PPAs involve direct energy delivery and are appropriate when:
+- Your load is in the same ISO as the project
+- You want both energy and RECs from a specific named facility
+- You can manage the operational complexity of scheduling and balancing
+
+#### Financial Modeling Framework
+
+**Step 1: Establish the baseline (no-PPA scenario).**
+Project your energy costs over the PPA term using forward curves for years 1-5 and
+a long-term price escalation assumption (typically 2-3%/year) for years 6+.
+
+**Step 2: Model PPA cash flows.**
+
+```
+Year N PPA Net Value = (Market Price at Hub - PPA Strike Price) × Expected Generation
+ - Basis Cost (Hub to Load Zone)
+ - Curtailment Cost (expected curtailed MWh × strike price)
+ - Balancing Costs (firming residual load not covered by PPA)
+ + REC Value (if RECs would otherwise be purchased separately)
+```
+
+**Step 3: Sensitivity analysis — run these scenarios at minimum:**
+
+| Scenario | Market Price Assumption | Generation Assumption | Basis Assumption |
+|----------|----------------------|----------------------|-----------------|
+| Base | Current forward curve + 2.5%/yr escalation | Developer's P50 estimate | 5-year historical average basis |
+| Bull | Forward + 4%/yr escalation | P50 generation | Basis narrows 20% |
+| Bear | Forward + 1%/yr escalation | P75 generation (lower) | Basis widens 30% |
+| Stress | Flat prices for 5 years, then 2%/yr | P90 generation (much lower) | Basis widens 50% |
+
+**Step 4: Calculate NPV, IRR, and levelized cost of energy (LCOE) under each scenario.**
+A PPA is economically justified if NPV is positive under base and bull cases and
+the loss under bear case is tolerable (typically <$2M cumulative over the PPA term
+for a mid-size C&I buyer).
+
+### 2.2 Virtual PPA (VPPA) Evaluation
+
+VPPAs are financial instruments — no physical energy delivery. The key risks differ:
+
+#### Basis Risk Analysis
+
+Basis risk is the primary financial risk in a VPPA. It arises because the generator
+settles at its node price and your load settles at your load zone price.
+
+**Quantification method:**
+
+1. Obtain 3-5 years of hourly LMP data for the generator's node and your load zone from the ISO.
+2. Calculate the hourly basis: Load Zone LMP - Generator Node LMP.
+3. Filter to hours when the generator would be producing (solar: daylight hours; wind: use historical generation profile).
+4. Calculate the generation-weighted average basis.
+5. Model the basis impact on PPA settlement:
+
+```
+Annual Basis Cost = Σ(hourly basis × hourly expected generation)
+
+If generation-weighted average basis = $5/MWh and annual generation = 200,000 MWh:
+Annual Basis Cost = $1,000,000/year
+Over a 15-year PPA: $15M in basis costs (undiscounted)
+```
+
+**Red flags for basis risk:**
+- Basis spread > $8/MWh generation-weighted average → high risk, negotiate basis hedge or reject
+- Basis volatility (standard deviation) > $15/MWh → unpredictable, hard to budget
+- Basis trend is widening over the historical period → structural congestion, likely to worsen
+- Generator is located behind a known transmission constraint → congestion will increase as more generation is added in that zone
+
+#### Curtailment Risk Analysis
+
+Curtailment occurs when the ISO orders the generator to reduce output due to
+transmission constraints or oversupply.
+
+| ISO | Technology | Typical Curtailment % | Trend |
+|-----|-----------|----------------------|-------|
+| ERCOT | Wind (West Texas) | 3-8% | Increasing as more wind is added |
+| ERCOT | Solar | 1-3% | Low but increasing |
+| CAISO | Solar | 5-12% (spring) | Increasing due to duck curve |
+| CAISO | Wind | 1-3% | Stable |
+| PJM | Wind | <1% | Minimal |
+| PJM | Solar | <1% | Minimal |
+| MISO | Wind | 2-5% | Moderate, depends on zone |
+| SPP | Wind | 3-7% | Increasing in western zones |
+
+**Contract protection:** Negotiate a curtailment threshold (e.g., first 5% is developer
+risk) and a compensation mechanism for excess curtailment (developer provides
+replacement RECs or a price adjustment). Never accept "buyer bears all curtailment
+risk" on a VPPA — this transfers a risk the buyer cannot manage or influence.
+
+#### Credit and Accounting Requirements
+
+| Requirement | Details |
+|-------------|---------|
+| ISDA Master Agreement | Required for VPPA. Negotiate credit thresholds, margin call provisions, and termination values. |
+| Credit support | Investment grade: typically no collateral for first $5-10M notional. Sub-IG: letter of credit or parent guarantee for 2-3 years of potential negative settlement. |
+| Accounting treatment | VPPAs may qualify for hedge accounting (ASC 815) if they meet effectiveness testing requirements. Without hedge accounting, mark-to-market gains/losses flow through the P&L, creating earnings volatility. Consult treasury and accounting early. |
+| Board / CFO approval | VPPAs are multi-year financial commitments. Most organizations require board approval for commitments >$10M notional or >10 years. Present as an energy cost management tool, not a speculative position. |
+
+### 2.3 Physical vs. Virtual PPA Decision Matrix
+
+| Factor | Favors Physical PPA | Favors Virtual PPA |
+|--------|-------------------|-------------------|
+| Load location | Same ISO as available projects | Load in regulated market or no nearby projects |
+| Energy supply | Need the physical energy (replacing utility supply) | Already have a retail supply contract |
+| Sustainability goal | Want bundled energy + RECs from a specific facility | Need RECs only for Scope 2 reporting |
+| Operational capability | Have energy scheduling and balancing resources | No energy trading or scheduling staff |
+| Balance sheet | Prefer to avoid financial derivative classification | Comfortable with ISDA and mark-to-market |
+| Credit profile | Sub-investment grade (physical may require less credit support) | Investment grade (can post collateral efficiently) |
+| Regulatory environment | Deregulated market with retail choice | Regulated market (VPPA may be the only option for additionality) |
+
+---
+
+## 3. Demand Charge Optimization
+
+### 3.1 Load Analysis Methodology
+
+**Step 1: Download 15-minute interval data.**
+Request a minimum of 12 months of 15-minute kW demand data from the utility or your
+meter data management system. For facilities with sub-metering, obtain interval data
+at the system level (HVAC, production, compressed air) in addition to the main meter.
+
+**Step 2: Identify peak demand intervals.**
+Sort all 15-minute intervals by kW descending. Focus on the top 50 intervals (the
+top 0.15% of all intervals in a year). These intervals drive your demand charges.
+
+**Step 3: Characterize peak drivers.**
+For each of the top 50 intervals, identify:
+- Date and time of day
+- Day of week
+- Outdoor temperature (proxy for HVAC load)
+- Production schedule (was the line running?)
+- Any anomalous events (equipment startup, testing, maintenance)
+
+**Typical findings for manufacturing facilities:**
+
+| Peak Driver | Frequency in Top 50 | Root Cause |
+|------------|---------------------|------------|
+| Morning ramp-up (6-9 AM) | 30-50% | Simultaneous startup of HVAC, compressors, and production lines |
+| Hot afternoon (2-5 PM) | 20-35% | HVAC at max coinciding with production peak |
+| Equipment startup after maintenance | 10-20% | Inrush current from large motors starting simultaneously |
+| Testing / commissioning | 5-10% | New equipment tested during peak periods |
+
+**Step 4: Calculate the demand charge cost of peak intervals.**
+
+```
+Monthly Demand Charge = Peak kW × Demand Rate ($/kW)
+
+If normal operating peak is 4,000 kW and the actual peak is 4,800 kW:
+Excess peak cost = (4,800 - 4,000) × $15/kW = $12,000/month
+
+With an 80% ratchet:
+Minimum billing demand for next 11 months = 4,800 × 0.80 = 3,840 kW
+If normal peak drops to 3,500 kW next month, you're still billed at 3,840 kW
+Annual ratchet cost = (3,840 - 3,500) × $15/kW × 11 months = $56,100
+```
+
+### 3.2 Peak Shaving ROI Framework
+
+#### Battery Energy Storage System (BESS)
+
+**Sizing methodology:**
+1. Determine the target peak reduction (kW to shave).
+2. Calculate the required energy capacity: target kW × duration of peak events.
+ For demand charge management, 1-2 hours of duration is typically sufficient.
+3. Apply round-trip efficiency (88-92% for lithium-ion): size the battery 10% larger
+ than the calculated energy requirement.
+
+**Example — 500 kW peak shaving at a manufacturing plant:**
+
+```
+Target reduction: 500 kW
+Peak event duration: 2 hours (based on interval data analysis)
+Battery size: 500 kW / 1,000 kWh (with 10% efficiency buffer: 500 kW / 1,100 kWh)
+
+Installed cost (2025): $800-$1,200/kWh for C&I BESS
+Total capital: $880,000-$1,320,000 (using 1,100 kWh at midpoint $1,000/kWh = $1,100,000)
+
+Annual savings stack:
+ Demand charge savings: 500 kW × $15/kW × 12 months = $90,000
+ Capacity tag reduction: 500 kW × $60/kW-yr (PJM example) = $30,000
+ TOU energy arbitrage: charge off-peak ($0.04/kWh), discharge on-peak ($0.08/kWh)
+ 1,100 kWh × $0.04/kWh spread × 250 days × 90% efficiency = $9,900
+ Demand response revenue: 500 kW × $40/kW-yr (PJM Economic DR) = $20,000
+
+Total annual value: $149,900
+Simple payback: $1,100,000 / $149,900 = 7.3 years
+With ITC (30% for standalone storage as of IRA): payback = $770,000 / $149,900 = 5.1 years
+```
+
+**Decision thresholds:**
+- Payback < 5 years (with stacked value + incentives): strong economic case, proceed
+- Payback 5-7 years: viable if aligned with sustainability goals or if demand charges are rising
+- Payback 7-10 years: marginal, requires additional strategic justification
+- Payback > 10 years: economics don't support investment without regulatory mandate
+
+#### Demand Response Program Evaluation
+
+Not all DR programs are equal. Evaluate on these dimensions:
+
+| Dimension | Questions to Answer |
+|-----------|-------------------|
+| Revenue certainty | Is payment capacity-based (guaranteed $/kW-yr) or performance-based (paid per curtailment event)? |
+| Dispatch frequency | How many events per year? What is the maximum duration? Can you sustain curtailment for the full duration? |
+| Baseline methodology | How is your curtailment measured? Customer Baseline Load (CBL) using 10-of-10 or adjusted methods? A poorly calculated baseline can understate your curtailment and reduce payments. |
+| Penalty for non-performance | What happens if you can't curtail during an event? Some programs impose penalties 2-3× the capacity payment. |
+| Interaction with other programs | Does DR enrollment affect your capacity tag calculation? Does it conflict with your behind-the-meter generation? |
+| Operational impact | Can your facility actually curtail the committed kW without affecting production quality, safety, or customer commitments? |
+
+### 3.3 Staggered Startup Protocol
+
+The single lowest-cost demand charge reduction strategy — no capital required:
+
+**Problem:** Morning startup creates a demand spike when HVAC, compressors, lighting,
+and production equipment all energize simultaneously between 5:30-6:30 AM.
+
+**Solution:** Stagger equipment startup over a 60-90 minute window:
+
+```
+5:00 AM — Lighting (50-100 kW)
+5:15 AM — HVAC pre-cooling/heating (500-800 kW, ramps over 30 min)
+5:45 AM — Compressed air system (200-400 kW, staged compressor starts)
+6:00 AM — Production Line 1 (300-500 kW)
+6:15 AM — Production Line 2 (300-500 kW)
+6:30 AM — Auxiliary systems, battery chargers, water heating
+
+Result: Peak during startup drops from 2,200 kW (simultaneous) to 1,600 kW (staggered)
+Savings: 600 kW × $15/kW × 12 months = $108,000/year at zero capital cost
+```
+
+**Implementation:** Program the building automation system (BAS) to enforce startup
+sequencing. Set hard interlocks that prevent the next system from starting until the
+prior system has reached steady state.
+
+---
+
+## 4. Market Analysis Framework
+
+### 4.1 Regulated vs. Deregulated Strategy Map
+
+| Your Situation | Primary Strategy | Secondary Strategy |
+|---------------|-----------------|-------------------|
+| Regulated market, single rate schedule | Demand charge management, on-site generation, tariff schedule optimization | Lobby for utility green tariff, evaluate community solar |
+| Regulated market, multiple rate options | Tariff analysis to select optimal schedule (TOU vs. flat vs. demand-based) | Load shifting to exploit TOU differentials |
+| Deregulated, single site | Competitive supply procurement (RFP to 5-8 REPs) | Layer procurement to manage timing risk |
+| Deregulated, multi-site same ISO | Aggregate sites for portfolio procurement (volume leverage) | Negotiate portfolio-level products (single supplier, blended rate) |
+| Deregulated, multi-site multi-ISO | Procure separately by ISO (market structures differ) | Leverage total volume in supplier negotiations even if contracts are separate |
+| Mixed regulated/deregulated portfolio | Competitive procurement for deregulated sites; demand management for regulated sites | Seek regulatory pilot programs in regulated territories |
+
+### 4.2 Forward Curve Analysis
+
+**What the forward curve tells you:**
+- Market consensus on future energy prices (adjusted for risk premium)
+- Seasonal price patterns (summer/winter spreads)
+- Year-over-year price trajectory (escalation or decline)
+
+**What the forward curve does NOT tell you:**
+- Actual future spot prices (forwards are not forecasts — they include a risk premium)
+- Short-term price spikes (forwards are averages, not tails)
+- Regulatory changes, plant retirements, or transmission additions not yet priced in
+
+**Using forward curves for procurement decisions:**
+
+| Forward Curve Position | Procurement Action |
+|-----------------------|-------------------|
+| Bottom 20% of 5-year range | Accelerate buying — lock more volume at favorable prices |
+| 20th-40th percentile | Proceed with scheduled layering — prices are reasonable |
+| 40th-60th percentile | Maintain default layering schedule |
+| 60th-80th percentile | Slow buying — defer non-critical tranches 30 days |
+| Top 20% of 5-year range | Defer where possible, increase index exposure, evaluate financial hedges instead of physical locks |
+
+### 4.3 Capacity Market Exposure
+
+In organized capacity markets (PJM, ISO-NE, NYISO), capacity charges are a significant
+cost component — $30–$120/kW-yr depending on the zone and auction results.
+
+**PJM Reliability Pricing Model (RPM):**
+- Auction held 3 years ahead of delivery year (Base Residual Auction)
+- Incremental auctions adjust quantities closer to delivery
+- Your capacity obligation is based on your PLC (Peak Load Contribution)
+- PLC is set by your metered load during the 5 highest system coincident peak hours (5CP) in the prior delivery year
+
+**Managing capacity exposure:**
+
+1. **Track PJM system peak alerts.** PJM issues "hot weather alerts" and "emergency alerts" when system peaks are expected. Curtail discretionary load during these hours to reduce your PLC for the following year.
+2. **Install peak notification systems.** Subscribe to PJM's demand response alerts. Deploy load curtailment controls that can drop 10-20% of facility load within 30 minutes of a peak alert.
+3. **Behind-the-meter generation.** Running backup generators during coincident peak hours reduces your metered load and thus your PLC. Ensure generators are permitted for non-emergency operation and emissions-compliant.
+4. **Capacity tag trading.** In some markets, capacity obligations can be traded or offset through financial instruments. Your supplier may offer capacity tag management as a service.
+
+**Example — capacity charge impact:**
+
+```
+Facility peak: 5,000 kW
+PLC (measured during prior year 5CP hours): 4,200 kW
+PJM BRA clearing price for your zone: $85/MW-day
+
+Annual capacity charge: 4,200 kW × $85/MW-day × 365 / 1,000 = $130,305/year
+
+If you had curtailed 500 kW during the 5CP hours:
+Reduced PLC: 3,700 kW
+Annual capacity charge: 3,700 kW × $85/MW-day × 365 / 1,000 = $114,793/year
+Savings: $15,512/year from 5 hours of load curtailment
+```
+
+---
+
+## 5. Hedging Strategy Design
+
+### 5.1 Hedging Instruments Available to C&I Buyers
+
+| Instrument | Complexity | Capital Required | Protection |
+|-----------|-----------|-----------------|------------|
+| Fixed-price contract (through REP) | Low | None (embedded in price) | Full price certainty for contracted volume |
+| Block purchases (through REP) | Low-Medium | None | Price certainty on base load; variable load exposed |
+| Financial swap (through broker/bank) | Medium | ISDA + possible margin | Converts floating price to fixed on specified volume |
+| Call option (through broker/bank) | Medium-High | Premium ($/MWh upfront) | Price ceiling at strike + premium; unlimited downside benefit retained |
+| Heat rate call option | High | Premium | Protects against gas-to-power price spike (useful when gas drives marginal power price) |
+| Collar (sell put, buy call) | Medium-High | Reduced premium (put proceeds offset call cost) | Ceiling and floor — limits both upside and downside |
+
+### 5.2 Hedging Strategy by Risk Profile
+
+| Risk Profile | Hedge Ratio | Instruments | Monitoring |
+|-------------|-------------|-------------|-----------|
+| Conservative (budget certainty paramount) | 80-95% hedged | Fixed-price contracts, financial swaps | Monthly mark-to-market review |
+| Moderate (balanced cost/risk) | 60-80% hedged | Block-and-index, layered procurement | Monthly forward curve review, quarterly hedge adjustment |
+| Aggressive (cost minimization focus) | 30-60% hedged | Index with call options for tail risk | Weekly market monitoring, daily during volatility events |
+| Speculative (never recommended for C&I) | <30% hedged | Index with no protection | Real-time monitoring (impractical for most C&I buyers) |
+
+### 5.3 Option Pricing and Evaluation
+
+When buying call options to cap index pricing exposure, evaluate:
+
+```
+Option value = Max(0, Spot Price - Strike Price) × Volume
+
+Cost: Premium per MWh × Contracted Volume
+Annual premium for a $50/MWh cap on day-ahead pricing: $2-5/MWh (varies by market volatility)
+
+Example — protecting 50,000 MWh annual index volume:
+ Call option strike: $50/MWh
+ Premium: $3/MWh
+ Total premium cost: $150,000/year
+
+ If spot averages $42/MWh: option expires worthless, total cost = $42 + $3 = $45/MWh
+ If spot averages $65/MWh: option pays $15/MWh, effective cost = $65 - $15 + $3 = $53/MWh
+ If spot spikes to $200/MWh (weather event): option pays $150/MWh, effective cap = $53/MWh
+
+ Maximum effective rate: strike + premium = $53/MWh regardless of market price
+```
+
+**When to use options vs. fixed contracts:**
+- Options when you want to participate in downside moves but protect against spikes
+- Fixed contracts when the premium for options exceeds the cost of just locking in a fixed price (this happens when volatility is high and options are expensive)
+
+---
+
+## 6. Sustainability Procurement Alignment
+
+### 6.1 Mapping Procurement to RE100 and SBTi
+
+**RE100 progress calculation:**
+
+```
+RE% = (Renewable MWh procured) / (Total electricity consumption MWh) × 100
+
+Acceptable renewable MWh sources (in order of additionality):
+1. On-site generation (strongest claim)
+2. Physical PPA with new project (strong additionality)
+3. Virtual PPA with RECs from new project (good additionality)
+4. Utility green tariff (varies by program design)
+5. Unbundled RECs (weakest claim — RE100 tightening requirements)
+```
+
+**SBTi trajectory alignment:**
+- SBTi requires absolute Scope 2 emissions reductions on a defined trajectory (typically 4.2%/year for 1.5°C alignment).
+- Lock in long-term renewable procurement (PPAs) that deliver emission reductions year over year.
+- Avoid procurement strategies that increase fossil dependence (long-term fixed contracts with fossil-heavy grid mix and no REC component).
+
+### 6.2 Cost-Effective Sustainability Procurement Path
+
+| Target RE% | Least-Cost Strategy |
+|-----------|-------------------|
+| 0-25% | Unbundled national wind RECs ($1-3/MWh). Cheapest entry point. |
+| 25-50% | Utility green tariff + unbundled RECs. Green tariffs are often $0.005-$0.015/kWh premium. |
+| 50-75% | VPPA with new wind/solar project. Fixed cost, long-term REC supply, additionality. |
+| 75-90% | Physical PPA or additional VPPA to cover remaining gap. On-site solar where feasible. |
+| 90-100% | Match remaining unhedged load with project-specific RECs or small on-site installations. The last 10% is the most expensive per MWh. |
+
+---
+
+## 7. Multi-Facility Portfolio Optimization
+
+### 7.1 Portfolio Aggregation Strategy
+
+**When to aggregate:**
+- 3+ sites in the same ISO/utility territory
+- Total volume > 20 GWh/year (attracts competitive supplier attention)
+- Sites have complementary load profiles (some peak summer, others peak winter)
+
+**Aggregation benefits:**
+- Volume leverage: 5-15% lower supply pricing than individual site procurement
+- Load diversity: combined portfolio has higher load factor than individual sites, reducing supplier risk premium
+- Administrative efficiency: single contract, single invoice, single relationship
+
+**When NOT to aggregate:**
+- Sites in different ISOs with different market structures (PJM and ERCOT should be procured separately)
+- One site has unique requirements (e.g., real-time pricing needed for a demand response strategy) that would constrain the entire portfolio
+- Sites have vastly different contract expiration dates (stagger expirations to avoid all-at-once recontracting risk)
+
+### 7.2 Portfolio-Level Risk Metrics
+
+Track at the portfolio level, not just site-by-site:
+
+| Metric | Formula | Target |
+|--------|---------|--------|
+| Portfolio hedge ratio | (Hedged MWh / Total expected MWh) × 100 | 60-80% |
+| Weighted average procurement price | Σ(site MWh × site $/MWh) / Total MWh | Within 5% of portfolio benchmark |
+| Supplier concentration | Largest supplier MWh / Total MWh | <50% (avoid single-supplier dependence) |
+| Contract expiration clustering | % of portfolio MWh expiring in any 12-month period | <40% (stagger expirations) |
+| Renewable coverage | Renewable MWh / Total MWh | On track to target |
+| Portfolio load factor | Total kWh / (Sum of site peak kW × hours) | Track trend, higher is better |
+
+### 7.3 Site Prioritization for Demand-Side Investment
+
+With limited capital for demand charge mitigation, prioritize sites using this scoring model:
+
+| Factor | Weight | Scoring |
+|--------|--------|---------|
+| Demand charges as % of total bill | 30% | >35% = 100, 25-35% = 70, 15-25% = 40, <15% = 10 |
+| Peak-to-average ratio | 25% | >2.5 = 100, 2.0-2.5 = 70, 1.5-2.0 = 40, <1.5 = 10 |
+| Available demand reduction (kW) | 20% | >1000 kW = 100, 500-1000 = 70, 200-500 = 40, <200 = 10 |
+| Utility demand rate ($/kW) | 15% | >$20 = 100, $15-$20 = 70, $10-$15 = 40, <$10 = 10 |
+| Capacity market exposure | 10% | PJM/ISO-NE (high) = 100, NYISO = 70, MISO = 40, none = 0 |
+
+**Investment priority: highest composite score first.** A site scoring >80 is a strong
+candidate for battery storage or demand response. A site scoring <40 has limited
+demand charge optimization potential — focus on supply-side procurement instead.
+
+---
+
+## 8. Natural Gas Procurement
+
+### 8.1 Gas Procurement Structures
+
+Natural gas procurement for C&I consumers (boilers, CHP, process heat, backup generation)
+follows similar principles to electricity but with distinct market mechanics.
+
+| Structure | Description | Best For |
+|-----------|-------------|----------|
+| Firm fixed-price | Locked $/therm or $/MMBtu for contract term | Budget certainty, large heating loads |
+| Index (first-of-month) | Monthly NYMEX Henry Hub settlement + basis + adder | Cost optimization, risk-tolerant buyers |
+| Index (daily) | Daily Gas Daily midpoint + basis + adder | High-flexibility loads, interruptible processes |
+| Baseload block + index | Fixed block covers base heating/process load, index covers variable | Facilities with both base process heat and weather-variable HVAC |
+| Swing contract | Volume flexibility (50-130% of nominated quantity) | Facilities with highly variable gas consumption |
+
+### 8.2 Basis Differentials for Natural Gas
+
+Natural gas prices vary by delivery point. Henry Hub (Louisiana) is the benchmark,
+but delivered cost depends on the basis differential between Henry Hub and your
+local city gate or utility delivery point.
+
+**Common basis differentials (approximate):**
+
+| Delivery Point | Typical Basis to Henry Hub | Driver |
+|---------------|--------------------------|--------|
+| Chicago (NGPL Midcontinent) | -$0.10 to +$0.15/MMBtu | Pipeline capacity from Gulf to Midwest |
+| New York (Transco Zone 6 NY) | +$0.50 to +$3.00/MMBtu | Winter constraint on pipelines into NYC |
+| New England (Algonquin) | +$1.00 to +$8.00/MMBtu (winter) | Severe pipeline constraints, competes with LNG |
+| California (SoCal Border) | -$0.50 to +$1.50/MMBtu | Varies with West Coast supply/demand |
+| Appalachia (Dominion South) | -$1.50 to -$0.30/MMBtu | Oversupply from Marcellus shale production |
+| Texas (HSC) | -$0.05 to +$0.20/MMBtu | Close to production, minimal basis |
+
+**Key insight:** A facility in New England on index pricing faces dramatically different
+winter risk than a facility in Texas. Basis in New England during a cold snap can
+exceed $15/MMBtu, tripling the delivered gas cost. New England gas procurement
+requires winter hedging with firm pipeline capacity or LNG backup — index pricing
+without protection is reckless in that market.
+
+### 8.3 Gas-Electric Interdependency
+
+For facilities with both electricity and natural gas loads, recognize the coupling:
+
+- **When gas prices spike, electricity prices spike.** Natural gas is the marginal fuel
+ for electricity generation in most US ISOs. A $2/MMBtu increase in Henry Hub
+ translates to approximately $10-$15/MWh increase in wholesale electricity prices
+ (depending on the average heat rate of marginal gas plants, typically 7,000-8,000 BTU/kWh).
+
+- **CHP economics are gas-price dependent.** A CHP system generating electricity at
+ a heat rate of 6,500 BTU/kWh has a fuel cost of $6.50 × gas price per MWh. At gas
+ $3/MMBtu, generation cost is $19.50/MWh. At gas $8/MMBtu, generation cost is
+ $52/MWh. If your grid electricity cost exceeds your CHP generation cost, run the
+ CHP. If grid electricity drops below CHP cost (e.g., during spring shoulder months
+ with mild weather and low grid demand), consider shutting down CHP and buying
+ from the grid.
+
+- **Dual-fuel hedging:** When hedging gas and electricity simultaneously, recognize
+ that fixing gas costs and leaving electricity at index (or vice versa) creates a
+ cross-commodity basis risk. If gas prices drop but electricity stays high (due to
+ transmission constraints or non-gas generation tightness), your gas hedge
+ underperforms while your electric bill remains high. Consider hedging both
+ commodities on a correlated basis — many energy suppliers offer combined
+ gas+electric portfolio management.
+
+---
+
+## 9. Tariff Optimization in Regulated Markets
+
+### 9.1 Rate Schedule Selection
+
+In regulated markets, the available tariff options may seem limited, but switching
+between rate schedules can save 5-15% on the total bill without changing consumption.
+
+**Step 1: Identify available rate schedules for your demand level and voltage.**
+Most utilities offer 2-4 rate options for large C&I customers:
+- Standard demand rate (flat energy + demand charge)
+- Time-of-use rate (lower off-peak energy, higher on-peak energy + demand)
+- Real-time pricing pilot (if available)
+- Interruptible service rate (lower cost, utility can curtail during emergencies)
+
+**Step 2: Model 12 months of actual interval data against each available rate schedule.**
+
+```
+For each rate schedule:
+ Monthly cost = Σ(energy_charge_component) + demand_charge + customer_charge + riders
+
+Where:
+ energy_charge_component = Σ(kWh_per_interval × applicable_rate_per_kWh)
+ demand_charge = max(15-min kW interval in month) × demand_rate
+ For TOU rates: separate on-peak demand charge may apply
+```
+
+**Step 3: Compare annual totals.**
+
+| Rate Schedule | Annual Energy | Annual Demand | Annual Fixed | Annual Total | vs. Current |
+|--------------|--------------|---------------|-------------|-------------|-------------|
+| Current (GS-3) | $580,000 | $312,000 | $24,000 | $916,000 | baseline |
+| TOU (GS-3-TOU) | $545,000 | $298,000 | $24,000 | $867,000 | -$49,000 (-5.3%) |
+| RTP pilot | $510,000 | $312,000 | $36,000 | $858,000 | -$58,000 (-6.3%) |
+| Interruptible | $565,000 | $250,000 | $24,000 | $839,000 | -$77,000 (-8.4%) |
+
+**Step 4: Evaluate non-financial factors.**
+- TOU: requires ability to shift load or accept higher on-peak costs
+- RTP: requires market monitoring and tolerance for price volatility
+- Interruptible: requires ability to curtail load on short notice (typically 30-60 min)
+
+### 9.2 Rate Case Monitoring and Response
+
+**When to intervene in a rate case:**
+
+| Impact Level | Annual Cost Increase | Recommended Action |
+|-------------|---------------------|-------------------|
+| <$50K | Negligible for large C&I | Monitor only — track filing through settlement |
+| $50K-$200K | Material but not critical | Join existing intervenor group (OIEC, etc.) |
+| $200K-$500K | Significant | Individual intervention with regulatory counsel |
+| >$500K | Critical | Full intervention with expert witnesses, rate design testimony |
+
+**Rate case timeline (typical):**
+
+```
+Month 0: Utility files rate case with state PUC
+Month 1-2: Intervenors file to participate
+Month 3-4: Discovery (interrogatories, data requests to utility)
+Month 5-7: Intervenor testimony filed
+Month 8-9: Hearings
+Month 10-12: PUC issues order
+Month 13-15: New rates take effect (may be retroactive to filing date)
+```
+
+**What to challenge in a rate case:**
+1. **Rate of return on equity (ROE):** Utilities typically request 10-11% ROE. Current
+ authorized ROEs are trending down (9-10%). Challenge excessive ROE requests.
+2. **Rate base additions:** Utilities earn their ROE on their rate base (invested capital).
+ Challenge excessive or imprudent capital investments included in the rate base.
+3. **Cost allocation between rate classes:** Utilities allocate total revenue
+ requirement across residential, commercial, and industrial rate classes. Ensure your
+ rate class is not subsidizing residential or other classes above cost causation.
+4. **Rate design:** Even if the total revenue is approved, fight for demand-based rate
+ design (rewards load factor management) rather than pure volumetric rates (punishes
+ high-consumption customers regardless of load shape).
+
+---
+
+## 10. Emergency Procurement Protocols
+
+### 10.1 Supplier Default / Bankruptcy
+
+If your retail energy provider files for bankruptcy or fails to perform:
+
+**Immediate actions (24-48 hours):**
+1. Verify your account status with the utility. If the supplier defaults, your
+ account reverts to the utility's Provider of Last Resort (POLR) service or standard
+ offer service. You will NOT lose power — the grid keeps delivering regardless of
+ supplier status.
+2. Determine the POLR rate. In most states, the POLR rate is set quarterly based on
+ wholesale market prices plus a premium (10-20% above competitive supply). This may
+ be higher or lower than your current contract rate.
+3. Contact 2-3 alternative suppliers immediately. Explain the situation — they will
+ offer expedited enrollment (5-10 business days vs. normal 30-60 day switch process).
+4. Review your contract for supplier default provisions, including any deposits or
+ prepayments that may be at risk in the bankruptcy estate.
+
+**Medium-term (2-4 weeks):**
+1. Execute a new supply contract with the best available alternative supplier.
+2. File a claim in the bankruptcy proceeding for any prepayments, deposits, or damages.
+3. Review your supplier qualification criteria — consider adding financial covenants
+ (minimum credit rating, tangible net worth requirements) to future contracts.
+
+### 10.2 Force Majeure Events
+
+When a force majeure event (natural disaster, grid emergency, pandemic) disrupts
+your energy supply or operations:
+
+**Assessment framework:**
+
+| Event Type | Energy Impact | Procurement Response |
+|-----------|--------------|---------------------|
+| Hurricane/severe weather | Physical damage to generation/T&D, price spikes | Activate backup generation, curtail non-essential load, document for insurance |
+| Grid emergency (EEA3) | Rolling blackouts, extreme prices | Maximum load curtailment, DR activation, generator deployment |
+| Supplier force majeure claim | Supplier attempts to suspend contract | Review FM clause narrowly — "market price increase" is NOT force majeure; "physical inability to deliver" may be |
+| Pandemic/operational shutdown | Facility closed, consumption drops dramatically | Invoke volume tolerance provisions, negotiate contract suspension, evaluate early termination |
+
+### 10.3 Contract Termination Decision Matrix
+
+When evaluating whether to terminate a supply contract early:
+
+```
+Early Termination Fee (ETF) = Σ(remaining months × monthly volume × |contract price - current market price|)
+
+If contract price > current market:
+ You owe the supplier (you're paying above market)
+ ETF = remaining months × volume × (contract price - market) × discount factor
+
+If contract price < current market:
+ Supplier owes you (you have a favorable contract)
+ You would NOT terminate — the contract is in-the-money
+
+Decision: Terminate if ETF < cumulative savings from alternative contract + risk reduction value
+```
+
+**Example — mid-term exit evaluation:**
+
+```
+Current contract: $0.062/kWh, 18 months remaining, 50 GWh remaining
+Current market: $0.055/kWh (market has dropped since contract signing)
+ETF: 50,000 MWh × ($0.062 - $0.055) = $350,000
+
+Alternative contract: $0.054/kWh for 18 months
+Savings from alternative: 50,000 MWh × ($0.062 - $0.054) = $400,000
+
+Net benefit of termination: $400,000 savings - $350,000 ETF = $50,000
+
+Decision: Marginal. Factor in:
+ - Renegotiation risk (can you lock $0.054 before market moves?)
+ - Administrative cost of switching suppliers
+ - Relationship cost with current supplier
+ - If net benefit < $100K, generally not worth the disruption
+```
+
+---
+
+## 11. Seasonal Procurement Calendar
+
+A disciplined procurement calendar ensures no critical deadlines are missed and
+procurement activities align with market conditions.
+
+| Month | Activity | Deadline |
+|-------|----------|----------|
+| January | Annual energy budget review, lock natural gas hedges for next winter | Jan 31 for winter gas |
+| February | Q1 forward curve review, PPA pipeline assessment | — |
+| March | Begin RFP preparation for contracts expiring in Q4 or Q1 next year | — |
+| April | Issue RFPs for fall contract starts, review summer DR enrollment | Apr 15 for PJM DR enrollment |
+| May | Evaluate bids, begin summer peak preparation (generator testing, BAS settings) | May 31 for summer rate elections |
+| June | Summer peak demand management begins, monitor 5CP forecasts (PJM) | — |
+| July | Peak season monitoring, execute Q3 procurement tranches | Jul 15 for ERCOT 4CP mgmt |
+| August | Peak season monitoring, finalize fall contract awards | Aug 31 for ISO-NE FCA positions |
+| September | Post-summer review, capacity tag assessment, RE100 progress check | Sep 30 for Q4 procurement |
+| October | Begin winter gas hedging, review heating load forecasts | Oct 31 for winter gas locks |
+| November | Budget season — prepare next year's energy cost forecast | Nov 15 for budget submission |
+| December | Year-end RE100 reconciliation, REC inventory check, contract renewals | Dec 31 for REC vintage retirement |
diff --git a/skills/energy-procurement/references/edge-cases.md b/skills/energy-procurement/references/edge-cases.md
new file mode 100644
index 00000000..53a9d55e
--- /dev/null
+++ b/skills/energy-procurement/references/edge-cases.md
@@ -0,0 +1,624 @@
+# Energy Procurement — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex energy procurement situations that don't resolve through standard decision frameworks.
+
+These edge cases represent the scenarios that separate experienced energy procurement managers from everyone else. Each involves competing priorities, market structure nuances, regulatory complexity, and real financial exposure. They are structured to guide resolution when standard procurement playbooks break down.
+
+---
+
+## How to Use This File
+
+When an energy procurement situation doesn't fit a clean decision tree — when market dynamics create conflicting incentives, when tariff structures produce counterintuitive outcomes, or when a PPA that looked good at signing turns problematic — find the edge case below that most closely matches the situation. Follow the expert approach step by step.
+
+---
+
+### Edge Case 1: ERCOT Price Spike During Extreme Winter Weather (Uri-Type Event)
+
+**Situation:**
+A food manufacturing company operates two facilities in Texas: a 6 MW production plant in Houston and a 3 MW distribution center in Dallas. Both are on index-priced supply contracts (ERCOT real-time settlement node price + $0.004/kWh supplier adder). During a February polar vortex event, temperatures drop to 5°F in Houston (normal February low: 42°F). ERCOT declares an Energy Emergency Alert Level 3 (EEA3) and implements rolling blackouts. Real-time wholesale prices hit the ERCOT system-wide offer cap of $5,000/MWh (during Uri in 2021, the cap was $9,000/MWh). The event lasts 5 days. The Houston plant has backup natural gas generators but cannot run them because natural gas supply has been curtailed due to wellhead freeze-offs. The Dallas facility has no backup generation.
+
+Your weekly energy cost is normally $85,000 across both sites. During this event, the projected weekly cost at $5,000/MWh average for 120 hours of peak pricing would exceed $4.5M.
+
+**Why It's Tricky:**
+The contract is working as designed — index pricing means you pay the market price. There is no breach, no force majeure claim against the supplier (they are delivering at index), and no contractual price cap unless you negotiated one. The financial exposure is catastrophic for a company where annual energy spend is $5M. A single week could equal the entire annual budget.
+
+Simultaneously, you need to keep the food production plant running (product in process will spoil if power is lost) and the distribution center must maintain cold chain for $8M of perishable inventory. Shutting down to reduce energy cost means accepting $3–$5M in product loss.
+
+**Common Mistake:**
+Keeping both facilities at full load throughout the event and accepting the $4.5M bill as a cost of doing business. The second mistake: attempting to renegotiate or dispute the contract after the event — courts consistently enforce index pricing during price spikes because that is the contract structure.
+
+**Expert Approach:**
+1. **Immediate load curtailment (Hour 0-4):** Reduce all discretionary load at both facilities. Target: 30-40% load reduction without shutting production lines. Turn off office HVAC (employees can layer up for a week), reduce warehouse lighting to emergency levels, shut down non-essential compressed air (only keep production-critical compressors), and turn off electric water heaters. A 35% load reduction on 9 MW combined peak saves approximately $1.6M over 5 days at $5,000/MWh.
+
+2. **Production schedule modification (Hour 4-12):** Shift production to overnight hours (10 PM - 6 AM) when prices typically dip to $1,000-$2,000/MWh even during extreme events (the sun isn't up, wind may be producing, and some thermal generation returns overnight). Run the Houston plant at minimum load during daytime peak hours (keep product in process alive but don't start new batches).
+
+3. **Demand response activation (Hour 0):** If enrolled in any ERCOT demand response program (ERS or 4CP programs), curtail to earn the event payment. This partially offsets the extreme energy cost. An ERS enrollment for 1 MW could pay $2,000-$5,000 per event hour depending on the program.
+
+4. **Generator options (Hour 2-6):** Contact your natural gas supplier and pipeline operator about gas availability. If pipeline gas is curtailed, evaluate diesel portable generators — rental generators during extreme weather events cost $50-$100/kW per day but at $5,000/MWh wholesale, generation cost at even $150/kW/day is far cheaper than grid power. Contact industrial generator rental companies immediately — they will be overwhelmed within 24 hours.
+
+5. **Supplier communication (Hour 0):** Contact your retail energy provider to understand their exposure and settlement timeline. Some REPs offer post-event payment plans. If your REP is likely to fail (several REPs went bankrupt after Uri), your account reverts to the utility's Provider of Last Resort (POLR) rate — which during an emergency may be even higher. Prepare for this contingency.
+
+6. **Post-event restructuring (Week 2+):** After the event, restructure your energy contracts. For ERCOT exposure, never go fully unhedged into winter. Options include:
+ - Add a price cap to your index contract ($100-$200/MWh ceiling, costs $2-$5/MWh in premium)
+ - Switch to block-and-index with blocks covering 80% of winter load
+ - Purchase OTC call options that cap your exposure above a strike price
+ - Maintain a cash reserve equal to 2 weeks of energy cost at $500/MWh
+
+**Key Indicators:**
+- ERCOT weather forecasts showing temperatures >20°F below seasonal norms for >3 days warrant pre-event hedging action
+- Natural gas spot prices at Houston Ship Channel exceeding $10/MMBtu signal potential generator fuel supply issues
+- ERCOT Conservation Voltage Reduction or EEA Level 1 declarations are early warnings — act before EEA3
+- Monitor ERCOT's generation outage report: if forced outages exceed 20 GW, price spikes above $1,000/MWh are likely
+
+**Documentation Required:**
+- Real-time price records from the ISO settlement system
+- Facility load data during the event (to demonstrate curtailment efforts for internal reporting and potential rate dispute)
+- Generator rental invoices and fuel costs
+- Communication log with REP and utility
+- Total financial exposure calculation for executive and board reporting
+- Post-event contract restructuring analysis
+
+**Resolution Timeline:**
+- Hours 0-6: Implement all immediate load curtailment measures
+- Hours 6-24: Execute production schedule shifts, secure backup generation if available
+- Days 2-5: Maintain curtailed operations, monitor market for normalization signals
+- Week 2: Receive preliminary settlement from REP, assess total financial impact
+- Week 3-4: Initiate contract restructuring discussions with REP
+- Month 2-3: Execute new contract structure with winter price protection
+
+---
+
+### Edge Case 2: Virtual PPA Basis Risk in a Congested Transmission Zone
+
+**Situation:**
+A technology company headquartered in Northern Virginia (PJM territory, Dominion zone) executed a 15-year VPPA with a 100 MW wind farm in western PJM (AEP zone, near the Ohio-West Virginia border). The VPPA strike price is $32/MWh, which at signing was $12/MWh below the PJM Western Hub forward curve of $44/MWh. The company projected $1.2M/year in positive settlement value, plus 350,000 RECs annually for their RE100 commitment.
+
+After 18 months of operation, the actual financial performance shows persistent negative settlements. The wind farm generates during overnight and shoulder hours when AEP zone LMPs average $28/MWh. The company's load zone (Dominion) averages $48/MWh during the same hours due to transmission congestion between AEP and Dominion zones. The generation-weighted average basis (Dominion LMP minus AEP node LMP) is $14/MWh.
+
+Net financial impact: the wind farm settles at $28/MWh average, which is $4/MWh below the $32 strike, meaning the company owes the developer $4/MWh. Plus the $14/MWh basis spread means the company's effective energy cost premium from the VPPA is $18/MWh — turning a projected $1.2M/year benefit into a $2.1M/year cost.
+
+**Why It's Tricky:**
+The VPPA contract is performing as written — the settlement is based on the generator's node price, not the company's load zone price. Basis risk was disclosed during contracting, but the company's internal projection used a 3-year historical average basis of $6/MWh (which was correct at the time). The basis widened due to new generation additions in AEP zone and continued transmission constraints into the Dominion zone — structural factors that will likely persist or worsen.
+
+The company cannot exit the VPPA without paying a termination fee based on the mark-to-market value, which at negative $2.1M/year for the remaining 13.5 years, discounted at 8%, is approximately $16M. The RECs are still valuable — 350,000 RECs at $5/REC = $1.75M/year — partially offsetting the financial loss, but the net economics are negative.
+
+**Common Mistake:**
+Terminating the VPPA immediately and paying the $16M termination fee. This crystallizes the loss. The second mistake: ignoring the problem and hoping basis narrows — structural congestion rarely self-corrects without transmission investment.
+
+**Expert Approach:**
+1. **Quantify the actual basis exposure.** Request hourly settlement data from the PPA counterparty. Calculate generation-weighted basis for each month. Identify whether basis is seasonal (wider in summer when AC load drives Dominion congestion) or persistent year-round.
+
+2. **Model forward basis expectations.** Engage an energy consultant or your supplier's market analytics team to model forward basis between AEP and Dominion zones. Key factors: planned transmission upgrades (PJM RTEP projects that relieve the constraint), new generation additions in AEP zone (more wind/solar behind the constraint worsens basis), and load growth in Dominion zone.
+
+3. **Evaluate basis hedging.** PJM offers Financial Transmission Rights (FTRs) that can hedge congestion costs between two points on the grid. Purchase FTRs from the AEP zone to the Dominion zone in the PJM FTR auction. An FTR paying $10/MWh on 350,000 MWh = $3.5M/year, which significantly offsets the basis loss. FTR costs vary — the auction determines the price, and popular paths (like AEP-to-Dominion) may be expensive. Budget $5-$8/MWh for FTR basis hedging.
+
+4. **Renegotiate the settlement point.** Approach the developer about switching the settlement point from the generator's node to the Western Hub or a more liquid hub closer to your load zone. The developer may accept this if the hub price is close to their node price (it often is — hub prices are less volatile than nodal prices). This doesn't eliminate basis risk but may reduce it.
+
+5. **Restructure the contract.** Options include:
+ - Reduce the contract volume (buy down from 100 MW to 60 MW, reducing exposure while keeping some REC delivery)
+ - Add a basis risk sharing mechanism (developer absorbs basis beyond $8/MWh)
+ - Convert to a fixed-price REC purchase (eliminate the energy settlement entirely, pay a fixed $/REC)
+
+6. **Portfolio-level offset.** If you have other facilities in the AEP zone, the VPPA's node-price settlement is actually favorable for loads in that zone (where LMPs are lower). Consider whether any current or planned facility expansion in AEP territory could benefit from the VPPA's economics.
+
+**Key Indicators:**
+- Basis widening beyond 150% of historical average for 2+ consecutive quarters signals structural change
+- PJM RTEP transmission projects targeting the constrained corridor may take 5-7 years to complete
+- New generation interconnection queue in the generator's zone exceeding 3 GW is a bearish signal for basis
+- FTR auction results showing increasing clearing prices on the relevant path confirm market recognition of the congestion
+
+**Documentation Required:**
+- Monthly VPPA settlement statements
+- Hourly generation-weighted basis calculations
+- FTR auction results and cost analysis
+- Developer communication regarding contract restructuring
+- Board-level financial exposure report
+- Revised forward-looking PPA valuation under multiple basis scenarios
+
+---
+
+### Edge Case 3: Demand Charge Ratchet Trap After Equipment Installation
+
+**Situation:**
+A plastics manufacturer in Georgia Power territory installed a new 1,200 kW production line. During commissioning week, the electrical contractor tested all equipment simultaneously at full load — standard practice for commissioning acceptance testing. The test occurred on a Wednesday afternoon in August, coinciding with the facility's normal summer HVAC peak. The 15-minute interval data shows a peak demand of 5,800 kW — compared to the facility's normal summer peak of 4,200 kW.
+
+Georgia Power's PLM-4 tariff includes an 80% demand ratchet. The billing demand for the next 11 months cannot fall below 80% of the maximum demand in the prior 11 months. The new floor: 5,800 × 0.80 = 4,640 kW. During winter months, when normal demand drops to 3,200 kW, the facility will be billed for 4,640 kW.
+
+Additional demand charges: (4,640 - 3,200) × $12.50/kW × 7 winter months = $126,000 in excess demand charges. And the new production line's normal operating demand of 900 kW (not the 1,200 kW commissioning peak) means the facility's normal summer peak going forward is 5,100 kW — still below the ratchet. Even in summer, the facility is billed for 5,800 kW peak demand.
+
+Annual excess demand charges from the commissioning peak: approximately $174,000.
+
+**Why It's Tricky:**
+The damage is done — a single 15-minute interval set the peak, and the ratchet clause is contractual. Georgia Power has no tariff provision for removing ratcheted demand due to commissioning events. You cannot dispute the meter reading (the test genuinely drew 5,800 kW). The only way to "reset" the ratchet is to either (a) wait 11 months for the peak to roll off, or (b) consistently hit a higher peak that makes the ratchet irrelevant (which would mean higher demand charges anyway).
+
+**Common Mistake:**
+Calling Georgia Power and asking them to waive the ratchet. They won't — it's a tariff provision approved by the Georgia Public Service Commission, not a negotiable contract term. The second mistake: assuming nothing can be done and absorbing the $174K cost.
+
+**Expert Approach:**
+1. **Immediate investigation (Day 1):** Pull the interval data for commissioning week. Identify the exact 15-minute interval(s) that set the new peak. Determine whether the peak was caused by legitimate commissioning (all equipment at rated load) or by an avoidable event (existing HVAC running at maximum while new equipment was at full test load).
+
+2. **Tariff analysis:** Review the PLM-4 tariff document line-by-line. Some tariffs have provisions for "temporary service" or "construction power" that could apply if the commissioning load was billed under a temporary service agreement. If the contractor should have been on temporary service during commissioning, the peak may not count against the permanent meter. This is rare but worth checking.
+
+3. **Demand response enrollment:** Georgia Power offers demand response programs that can provide credit against demand charges. If the facility can commit to curtailing 800-1,000 kW during summer peak events, the DR credit may offset a significant portion of the ratchet cost. Enroll immediately — programs have seasonal enrollment windows.
+
+4. **Operational changes to reduce the ratchet impact:** Since the ratchet is based on the single highest 15-minute interval, focus on ensuring that the facility NEVER exceeds 5,800 kW again (which would reset the ratchet at a higher level). Install a demand controller on the main meter that sheds non-critical loads (compressed air, water heating, battery chargers) whenever demand approaches 5,500 kW.
+
+5. **Future prevention protocol:** Establish a policy that all equipment commissioning involving loads >200 kW must be scheduled during off-peak hours (overnight or weekends), with the building HVAC in setback mode and non-essential production loads off. The commissioning electrician should coordinate with the energy manager, not just the maintenance supervisor. Include this requirement in all future capital project specifications.
+
+6. **Financial recovery:** If the electrical contractor failed to follow a commissioning plan that specified load management during testing, evaluate whether the excess demand charges ($174K) are recoverable as consequential damages under the construction contract. Review the contract's commissioning provisions and liability clauses.
+
+**Key Indicators:**
+- Any planned equipment installation >200 kW capacity should trigger a commissioning demand management plan
+- Request interval data within 48 hours of commissioning to identify ratchet exposure before the billing cycle closes
+- If your tariff has a demand ratchet, the energy manager must be involved in all capital project commissioning plans
+
+---
+
+### Edge Case 4: Utility Rate Case Filing Mid-Contract
+
+**Situation:**
+A hospital system with 12 facilities in Ohio (AEP Ohio territory) has a 36-month fixed-price electricity supply contract with a competitive retail energy provider at $0.052/kWh for the energy component. The contract was signed 8 months ago. AEP Ohio has just filed a distribution rate case with the Public Utilities Commission of Ohio (PUCO), proposing a $480M revenue increase across all rate classes — an average 18% increase in distribution charges.
+
+For the hospital system's rate class (GS-3 General Service-Large), the proposed increase translates to approximately $0.014/kWh in additional distribution charges. Across the hospital system's 180 GWh annual consumption, the annual cost increase would be approximately $2.52M. The current total delivered cost is $0.088/kWh; the proposed distribution increase would raise it to $0.102/kWh — a 16% total cost increase.
+
+The fixed-price supply contract covers only the energy and capacity components ($0.052/kWh). Distribution charges, transmission charges, riders, and surcharges are pass-through items — the hospital system pays whatever the utility tariff dictates.
+
+**Why It's Tricky:**
+The supply contract is performing as agreed. The $0.052/kWh energy price is locked. But the total delivered cost is increasing by $2.52M/year, and the hospital system's CFO expected the "fixed-price contract" to provide budget certainty on the total energy bill. The disconnect between "supply is fixed" and "delivery is pass-through" is one of the most common misunderstandings in commercial energy procurement.
+
+The rate case will take 12-18 months to adjudicate. The proposed $0.014/kWh increase is the utility's opening position — the final settlement typically lands at 50-75% of the proposed increase. But even a 50% outcome ($0.007/kWh) means $1.26M/year in additional costs.
+
+**Common Mistake:**
+Ignoring the rate case because "we have a fixed-price contract" and only discovering the cost increase when the new tariff rates take effect. The second mistake: blaming the energy supplier for not protecting against distribution rate increases — the supplier explicitly passes these through in the contract, and there is no commercial product that can fix distribution rates (these are regulated, not competitive).
+
+**Expert Approach:**
+1. **Rate case analysis (Week 1):** Obtain the full rate case filing from the PUCO docket. Focus on the cost of service study for the GS-3 rate class. Identify what specific distribution cost components are driving the increase (infrastructure replacement, storm hardening, grid modernization, rate of return request). Calculate the exact impact on each hospital facility based on their billing determinants.
+
+2. **Intervention evaluation (Week 2-3):** Large C&I customers have the right to intervene in rate cases. Intervention allows you to file testimony challenging the utility's cost allocation, rate design, or revenue requirement. The hospital system's $2.5M+ annual impact justifies the cost of intervention ($50K-$150K in legal and expert witness fees). Contact a utility regulatory attorney in Ohio.
+
+3. **Coalition building (Week 2-4):** Join the Ohio Industrial Energy Consumers (OIEC) or similar industrial intervenor group. These organizations pool resources to intervene in rate cases, reducing individual company costs to $10K-$30K/year in membership fees while providing professional regulatory representation.
+
+4. **Rate design advocacy:** Even if the total revenue increase is approved, the rate design (how the revenue is allocated across rate classes and billing determinants) can be influenced. Advocate for cost allocation that reflects actual cost causation — hospitals with high load factors and coincident peak management should pay less per kWh in distribution than low-load-factor commercial buildings. File testimony supporting demand-based distribution rates rather than volumetric rates.
+
+5. **Budget adjustment (Month 1):** Present the rate case exposure to the hospital system's CFO immediately. Provide three scenarios: full proposed increase ($2.52M/year), likely settlement (60% = $1.51M/year), and best case (40% = $1.01M/year). Recommend budgeting at the likely scenario and establishing a reserve for the upside case. The rate case outcome is 12-18 months away, but budget planning should begin immediately.
+
+6. **Demand-side response:** A rate case that increases distribution charges makes demand charge management more valuable. Every kW of peak reduction now saves more per month. Re-run the ROI analysis for battery storage, demand response, and load management projects with the proposed new rates — projects that were marginal at old rates may now have strong payback.
+
+**Key Indicators:**
+- Monitor your state PUC docket for utility rate case filings quarterly
+- Track the authorized rate of return — utilities filing for ROE >10% in the current interest rate environment will face pushback
+- Rate cases proposing >15% overall increases typically settle at 50-65% of the request
+- Infrastructure replacement riders often bypass rate case proceedings — monitor these separately
+
+**Documentation Required:**
+- Rate case docket filing and all testimony
+- Facility-level billing determinant analysis
+- Impact assessment under proposed and likely settlement scenarios
+- Intervention timeline and cost estimate
+- Budget revision memo for CFO
+- Coalition membership evaluation
+
+---
+
+### Edge Case 5: Negative LMP Pricing Affecting PPA Economics
+
+**Situation:**
+A consumer products company has a 20-year physical PPA with a 50 MW solar farm in CAISO (Central California). The PPA price is $28/MWh with a clause that the offtaker purchases all energy generated at the contract price. During spring months (March-May), CAISO experiences significant solar oversupply during midday hours. Day-ahead LMPs at the project's node have gone negative — averaging -$8/MWh between 10 AM and 2 PM on weekdays during April.
+
+When LMPs are negative, the generator actually earns negative revenue in the wholesale market (they would have to pay to inject power). However, under the PPA terms, the offtaker (the company) is obligated to purchase at $28/MWh regardless of the market clearing price. During these negative-price hours, the effective premium the company pays is $28 - (-$8) = $36/MWh above market. In April alone, 120 hours of negative pricing on an average 35 MW output represents: 120 hrs × 35 MW × $36/MWh premium = $151,200 of above-market cost in a single month.
+
+Annually, negative pricing during spring months creates approximately $400K-$600K in above-market costs. This was not modeled in the original PPA financial analysis, which assumed LMPs would always be positive.
+
+**Why It's Tricky:**
+The PPA contract requires the company to purchase all generated output at $28/MWh. The contract was signed when CAISO negative pricing was infrequent (occurring <50 hours/year). Since then, solar buildout has accelerated, and negative pricing now occurs 500-800 hours/year in central California during spring. This is a structural trend — it will get worse as more solar is added.
+
+The solar farm continues to generate during negative-price hours because it earns the $28/MWh PPA price (a positive return) plus federal production tax credits ($0.026/kWh), which together exceed its marginal operating cost of effectively $0. The developer has no economic incentive to curtail during negative price hours as long as the PPA requires the offtaker to buy the output.
+
+**Common Mistake:**
+Demanding that the developer curtail during negative price hours (the contract doesn't require this). The second mistake: building a financial model that assumes negative pricing will revert to historical norms — the structural drivers are getting stronger, not weaker.
+
+**Expert Approach:**
+1. **Contract review:** Examine the PPA for any provisions related to economic curtailment, negative pricing, or market price floors. Modern PPAs (post-2020) often include a "negative price curtailment" clause where the developer is curtailed when market prices go negative for >2 consecutive hours, and the offtaker is not obligated to purchase during curtailed hours. Older PPAs may lack this provision.
+
+2. **Economic curtailment negotiation:** Approach the developer to add a negative price curtailment provision. The developer's perspective: they lose PPA revenue ($28/MWh) and may lose PTC value during curtailed hours, but they also avoid the operational cost of generating into a negative-price market and maintain grid operator goodwill (CAISO can mandate curtailment for reliability — voluntary curtailment preserves the developer's standing). Propose: curtailment when the 15-minute LMP is negative, with the developer retaining RECs for curtailed hours (they can sell them separately to partially offset lost PPA revenue).
+
+3. **REC value assessment:** Quantify the REC value for curtailed hours. If the company needs 175,000 RECs/year for RE100 and the PPA delivers 160,000 RECs (net of curtailment), the company must purchase 15,000 replacement RECs at market price ($8-$15/MWh for CAISO solar RECs). Compare this cost ($120K-$225K) against the negative-price exposure ($400K-$600K). The math likely favors curtailment.
+
+4. **Behind-the-meter storage pairing:** If the company has a facility near the solar farm (or in the same utility territory), pairing a battery with the solar PPA allows absorption of midday generation for discharge during evening peak hours when LMPs are highest. This converts the negative-price exposure into a TOU arbitrage opportunity. A 10 MW / 40 MWh battery co-located with or at the facility could shift 4 hours of midday production to evening hours, capturing a $50-$80/MWh spread.
+
+5. **Settlement structure revision:** Negotiate a change from "buy all output at $28/MWh" to "buy all output at $28/MWh with a market price floor of $0/MWh." Under this revised structure, during negative price hours, the company pays $28/MWh (not $36/MWh above market) because the settlement reference price is floored at zero. The developer absorbs the negative market price risk.
+
+**Key Indicators:**
+- CAISO negative pricing frequency exceeding 300 hours/year and growing YoY signals structural oversupply
+- New solar interconnection queue in the generator's zone exceeding 5 GW indicates the problem will worsen
+- CAISO proposed market reforms (extended day-ahead market, WEIM expansion) may partially mitigate negative pricing through broader geographic dispatch
+- Battery storage additions in CAISO are absorbing midday solar and may reduce negative pricing frequency by 2027-2030
+
+---
+
+### Edge Case 6: Behind-the-Meter Solar Cannibalizing Demand Response Value
+
+**Situation:**
+A cold storage operator in New Jersey (PSE&G territory, PJM market) installed a 1.5 MW rooftop solar array under a 25-year on-site solar PPA at $0.065/kWh. The facility is also enrolled in PJM's Economic Demand Response program, committing to curtail 800 kW during high-priced hours. The DR program calculates the Customer Baseline Load (CBL) using the average of the highest 4 out of the prior 5 business days' consumption during the DR event hours.
+
+After the solar installation, the facility's grid consumption during sunny weekday afternoons dropped by approximately 1,100 kW (the solar array's typical output). This reduced the CBL by the same amount. When a DR event is called on a cloudy day (when solar output is only 200 kW instead of 1,100 kW), the facility's actual load is close to its pre-solar level — but the CBL is based on recent sunny days when grid consumption was lower. The measured curtailment (CBL minus actual metered load during the event) is effectively zero or negative, even though the facility is genuinely curtailing discretionary loads.
+
+The result: the facility fails performance testing for the DR program, loses its 800 kW capacity commitment credit ($48,000/year at $60/kW-yr), and faces a non-performance penalty of $25,000.
+
+**Why It's Tricky:**
+The solar array and the DR program each made financial sense individually. But the interaction between the CBL methodology and behind-the-meter solar creates a perverse outcome: solar production on sunny days lowers the baseline, making it harder to demonstrate curtailment on cloudy event days (when solar isn't helping). The CBL methodology was designed for facilities with predictable, weather-independent load — it doesn't account for behind-the-meter generation that varies with weather.
+
+**Common Mistake:**
+Installing behind-the-meter solar and enrolling in DR programs without modeling the CBL interaction. The second mistake: reducing the DR commitment to match the new (lower) CBL, which sacrifices significant capacity revenue.
+
+**Expert Approach:**
+1. **CBL methodology analysis:** Request the detailed CBL calculation methodology from PJM or your curtailment service provider (CSP). Some DR programs allow CBL adjustment for behind-the-meter generation — PJM's rules have evolved, and recent provisions may allow the CBL to be calculated on a "gross load" basis (metered load + estimated solar generation) rather than "net load" basis. If gross load CBL is available, apply for the adjustment.
+
+2. **Solar metering:** Install a revenue-grade meter on the solar array's output (separate from the utility meter). This provides real-time solar generation data that can be used to adjust the CBL. The meter cost ($2,000-$5,000 installed) is trivial compared to the lost DR revenue.
+
+3. **CSP negotiation:** Engage your Curtailment Service Provider to restructure the DR enrollment. Options:
+ - Switch to a "firm service level" (FSL) baseline methodology where your committed curtailment is measured as the difference between your maximum load and a pre-agreed service level, rather than a rolling CBL
+ - Enroll the solar production as a separate DR resource (solar + storage dispatch) rather than netting it against the facility load
+ - Reduce the committed curtailment volume to a level achievable on cloudy days (e.g., 400 kW instead of 800 kW) as an interim measure
+
+4. **Battery integration:** Add a battery system (200 kW / 400 kWh minimum) that charges from solar during sunny hours and discharges during DR events. This allows the facility to demonstrate curtailment on cloudy days by discharging stored solar energy, keeping the CBL higher and providing real kW reduction during events. The battery also earns frequency regulation revenue in PJM during non-event hours.
+
+5. **Re-evaluate the overall value stack.** Recalculate the total economic benefit of each component (solar PPA savings, DR revenue, capacity tag reduction, TOU arbitrage) with the interaction effects included. The optimal configuration may involve sizing the DR commitment to a level that is achievable regardless of solar output, rather than maximizing the individual DR commitment.
+
+**Key Indicators:**
+- Before installing behind-the-meter generation at a facility enrolled in DR, model the CBL impact for all weather scenarios
+- DR programs using CBL-10 (average of 10 prior similar days) are more vulnerable to solar cannibalization than those using metered generation adjustment
+- PJM's wholesale market rules for DR are updated annually — check for behind-the-meter generation accommodation provisions
+
+---
+
+### Edge Case 7: Capacity Market Obligation Surprise from Coincident Peak
+
+**Situation:**
+A data center operator in PJM (ComEd zone, Northern Illinois) runs three facilities with a combined peak demand of 30 MW. The company has been aggressively managing capacity costs — PLC tags for the prior delivery year totaled 24 MW (reflecting successful load reduction during the 5 coincident peak hours).
+
+During the current summer, an unprecedented heat wave hit the Midwest. PJM called for demand response and conservation. The data center operator's backup diesel generators were offline for maintenance during the two hottest days. Without generator backup, the facilities ran at full grid load during what turned out to be 3 of the 5 coincident peak hours. The data center also accepted an emergency colocation request from a major client, adding 2 MW of temporary load.
+
+When PJM publishes the new PLC values, the data center's tag jumps from 24 MW to 31 MW (full grid load of 30 MW plus the 2 MW temporary load minus some non-coincidence). At the BRA clearing price of $98/MW-day, the annual capacity charge increases from $858,720 to $1,108,870 — a $250,150 increase that persists for the entire delivery year.
+
+**Why It's Tricky:**
+The PLC is set by metered data during the 5CP hours — there's no appeals process, no adjustment for maintenance schedules or temporary load. The data center operator managed their PLC carefully for years but a single summer with bad timing (generators offline during the peak) erased all that work. The $250K annual increase is locked for the entire delivery year, regardless of what the data center does going forward.
+
+**Common Mistake:**
+Treating PLC management as "nice to have" rather than a critical operational priority. The second mistake: scheduling generator maintenance during summer months (June-September) when coincident peaks are most likely.
+
+**Expert Approach:**
+1. **Generator maintenance scheduling (preventive):** Never schedule backup generator maintenance during June-September. If maintenance must occur during summer, complete it on a single unit at a time and only on days when the PJM weather forecast shows temperatures below the 5CP trigger zone (typically <90°F for ComEd zone). Maintain at least 80% of generator capacity available during all summer weekday afternoon hours.
+
+2. **Temporary load policies:** Establish a policy that no temporary or emergency load additions are accepted during June-September without explicit approval from the energy procurement team. The $250K capacity charge increase from 2 MW of temporary load far exceeds any revenue from the colocation contract (unless the contract is specifically priced for capacity cost pass-through).
+
+3. **PLC monitoring service:** Subscribe to a PJM coincident peak prediction service (offered by most retail energy providers and specialized consultants). These services predict 5CP hours 24-48 hours in advance with 80-90% accuracy. When a predicted 5CP hour is forecast, activate all available generators, curtail all discretionary load, and notify operations that this is a "gold hour" — every kW reduced during these 5 hours saves $35,770/year at the current capacity price.
+
+4. **Recovery strategy for the current year:** The new PLC is set and cannot be changed for this delivery year. Focus on minimizing next year's PLC. Implement:
+ - Firm generator maintenance blackout window (June 1 - September 30)
+ - Automated demand response controls that shed 3-5 MW of discretionary load within 15 minutes of a 5CP alert
+ - Contractual provisions for all new colocation agreements requiring load shedding during capacity peak events
+
+5. **Financial recovery:** Calculate whether the temporary colocation client's contract covers the capacity cost increase. If not, renegotiate the contract to include capacity cost pass-through. For future emergency colocation requests during summer, quote the capacity cost impact explicitly: "Adding 2 MW during potential 5CP hours will cost $71,540/year in capacity charges — this must be included in the colocation pricing."
+
+**Key Indicators:**
+- PJM summer weather forecasts predicting temperatures >92°F for the ComEd zone on 3+ consecutive weekdays signal likely 5CP hours
+- PJM issuing hot weather alerts or emergency procedures is a near-certain 5CP indicator
+- Backup generator availability below 80% during June-September is a capacity management risk
+
+---
+
+### Edge Case 8: Renewable Curtailment Exceeding Developer Projections
+
+**Situation:**
+A manufacturing company signed a 15-year physical PPA with a 75 MW wind farm in ERCOT (West Texas) at $22/MWh with projected annual generation of 270,000 MWh (41% capacity factor). The company's RE100 target depends on receiving at least 250,000 MWh of bundled RECs from this project annually.
+
+After the first full year of operations, actual generation is 235,000 MWh — 13% below the P50 projection. The shortfall is primarily driven by curtailment: ERCOT curtailed the wind farm for 680 hours (7.8% of the year), versus the developer's projection of 250 hours (2.9%). The curtailment is caused by transmission congestion on the CREZ (Competitive Renewable Energy Zone) lines from West Texas to the Houston and Dallas load centers — the same lines that were built to export West Texas wind, but which are now at capacity due to the exponential growth of wind and solar in the region.
+
+The company is 15,000 RECs short of its annual RE100 requirement and must purchase replacement RECs. Additionally, the lower generation volume means lower PPA settlement income (the positive spread between market price and PPA strike price is earned on fewer MWh).
+
+**Why It's Tricky:**
+Wind farm curtailment in West Texas is a known risk, but the magnitude exceeded projections. The developer used historical curtailment data from 2020-2022 (when the CREZ lines had more headroom) — since then, 8 GW of new wind and solar have interconnected in the same constrained region. The ERCOT interconnection queue shows another 15 GW of proposed projects in West Texas, suggesting curtailment will worsen before it improves.
+
+The PPA contract allocates curtailment risk to the offtaker (the company pays the contract price only for delivered energy, and receives no compensation for curtailed energy). This is standard in older PPA structures.
+
+**Common Mistake:**
+Assuming the developer can solve the curtailment problem (they can't — it's a grid-level transmission constraint). The second mistake: projecting future generation using the developer's original P50 without adjusting for actual curtailment experience.
+
+**Expert Approach:**
+1. **Rebase generation projections.** Using 12 months of actual data, create an adjusted generation projection: actual wind resource (may differ from developer's model), actual curtailment rate (680 hours, not 250), and trend-adjust curtailment based on ERCOT interconnection queue data. A reasonable forward projection might be 225,000-240,000 MWh/year with curtailment worsening 1-2% per year until new transmission is built.
+
+2. **Curtailment clause renegotiation.** Approach the developer to renegotiate the curtailment allocation. Propose a shared risk model: developer bears first 4% of curtailment (their original projection); offtaker bears next 2%; any curtailment above 6% is the developer's risk. The developer may agree because locking in the PPA relationship is preferable to losing the offtaker's volume entirely.
+
+3. **REC replacement strategy.** Budget for annual replacement REC purchases to cover the shortfall. ERCOT wind RECs trade at $2-$4/MWh. A 15,000 REC shortfall costs $30,000-$60,000/year — manageable, but the cost grows if curtailment increases. Consider purchasing replacement RECs through a multi-year contract to lock in pricing.
+
+4. **Transmission monitoring.** Track ERCOT's Long-Term System Assessment and regional transmission plans. New 345 kV lines from West Texas to North Central Texas are planned but typically take 5-7 years from approval to energization. Model the curtailment trajectory assuming transmission expansion occurs on ERCOT's published timeline, and model the scenario where it's delayed 2-3 years.
+
+5. **Portfolio diversification.** For the next renewable procurement, avoid West Texas siting. Diversify to the Texas Gulf Coast (solar, lower curtailment) or outside ERCOT entirely (PJM wind/solar where curtailment is minimal). A portfolio of 2-3 projects across different regions reduces curtailment concentration risk.
+
+**Key Indicators:**
+- ERCOT curtailment orders exceeding 5% of annual hours for a specific generator region signals structural congestion
+- ERCOT interconnection queue exceeding 2× existing generation capacity in a constrained zone is a bearish curtailment signal
+- Developer reporting curtailment exceeding P90 projections in year 1 indicates the projections were based on outdated grid conditions
+
+---
+
+### Edge Case 9: Deregulated Market Re-Regulation Risk
+
+**Situation:**
+A retail chain with 200 stores across Ohio and Pennsylvania has 150 stores on competitive supply contracts (fixed-price, $0.058/kWh energy, average 36 months remaining). After a summer price spike that caused $800M in aggregate consumer cost increases statewide, the Ohio legislature introduces a bill to re-regulate the electricity market — returning all generation procurement to the regulated utilities at tariff rates.
+
+The proposed bill would void all existing competitive supply contracts within 180 days of enactment and require all customers to return to utility standard service. The current utility standard service rate for commercial customers is $0.071/kWh energy — 22% higher than the chain's competitive rate.
+
+The Ohio stores represent 120 of the 200 locations, consuming 95 GWh annually. If re-regulation occurs, the annual energy cost increase for Ohio alone would be approximately $1.24M (95 GWh × $0.013/kWh increase).
+
+**Why It's Tricky:**
+Re-regulation bills are introduced periodically but rarely enacted. However, this bill has political momentum because the summer price spike affected residential customers, and legislators want to "protect consumers." The bill is expected to reach committee vote within 4 months. Even if it doesn't pass, the legislative uncertainty creates contract enforcement risk — retail energy providers may attempt to add regulatory change provisions to new contracts, and existing contract renewal terms may include re-regulation exit clauses.
+
+The more insidious risk: even without formal re-regulation, Ohio could introduce a "provider of last resort" surcharge, a competitive market administration fee, or other mechanisms that reduce the competitive supply discount. These incremental regulatory changes are more likely than full re-regulation and can erode 30-50% of the competitive savings.
+
+**Common Mistake:**
+Ignoring the legislative risk because "re-regulation never happens." It happened in Ohio once before (SB 221 in 2008 attempted partial re-regulation), and Virginia effectively re-regulated in 2007 before partially deregulating again. The second mistake: panicking and trying to exit competitive contracts — the contracts are favorable, and any exit would involve early termination fees.
+
+**Expert Approach:**
+1. **Assess probability.** Engage a regulatory affairs consultant or your energy supplier's government relations team to assess the bill's likelihood of passage. Track committee votes, sponsor count, and utility lobbying positions. If the utility supports re-regulation (they often do, as it restores their captive customer base), the bill has stronger prospects.
+
+2. **Coalition advocacy.** Join or form a C&I customer coalition opposing re-regulation. Large commercial customers benefit most from competition and have the strongest voice against re-regulation. Provide testimony on the consumer savings from competitive supply — a retail chain saving $1.24M/year is a compelling data point.
+
+3. **Contract review.** Examine existing supply contracts for regulatory change clauses. Most well-drafted competitive supply contracts include a provision allowing either party to terminate or renegotiate if the regulatory structure fundamentally changes. Understand your termination rights and the supplier's — if the supplier can exit your contract due to re-regulation, you lose your favorable rate but avoid paying an early termination fee.
+
+4. **Hedging the Pennsylvania exposure.** If Ohio re-regulates, accelerate procurement for Pennsylvania stores. Lock in competitive rates for the maximum available tenor (36-48 months) while the Pennsylvania market remains competitive. Diversify supplier credit exposure in case one supplier exits the Ohio market.
+
+5. **Contingency budgeting.** Model the financial impact of three scenarios:
+ - Full re-regulation (Ohio energy cost increases $1.24M/year)
+ - Partial re-regulation (competitive supply preserved for large C&I but with new surcharges — increase $400K-$600K/year)
+ - Bill fails (no cost change, but future legislative risk remains)
+
+ Present scenarios to the CFO with probability weights. Budget to the expected value.
+
+**Key Indicators:**
+- State legislature introducing electricity market reform bills after consumer price spike events
+- Utility lobbying spend increasing for "market reform" or "default service enhancement"
+- Residential customer complaint rates exceeding 3× historical average (political pressure builds)
+- Governor or PUC chair making public statements about "market failure" in competitive supply
+
+---
+
+### Edge Case 10: Transmission Congestion Invalidating Procurement Strategy
+
+**Situation:**
+A chemical manufacturer with a 15 MW facility in southern New Jersey (JCPL zone, PJM) has been buying power at the PJM Western Hub price through a retail energy provider, with a $0.003/kWh adder. The Western Hub price of $38/MWh has been a reasonable proxy for the JCPL zone price historically (basis of $2-$4/MWh). The company's energy budget is built on $41/MWh all-in.
+
+A new data center campus interconnected 8 miles from the chemical plant, adding 80 MW of load in the JCPL zone. Simultaneously, a 500 MW natural gas plant in the zone retired. The combination of added load and reduced generation created a transmission constraint. The JCPL zone day-ahead LMP jumped from $40/MWh to $58/MWh during peak hours, while the Western Hub price remained at $38/MWh. The basis between Western Hub and JCPL zone widened from $3/MWh to $18/MWh.
+
+The company's retail supply contract settles at Western Hub + adder, but the company pays the utility for energy delivery at the zonal LMP. The net effect: the company is paying $38 + $3 (supplier) but the utility pass-through for congestion is $18/MWh, raising the effective cost to $59/MWh. Against a $41/MWh budget, the facility is running $18/MWh over — $2.36M/year on 131 GWh.
+
+**Why It's Tricky:**
+The supply contract is performing as agreed (Western Hub + $3). The congestion cost is a separate charge flowing through the utility bill. This is a market structure nuance that many C&I buyers don't model — they assume the hub price is approximately equal to their delivered price. When basis was $2-$4/MWh, this assumption was harmless. At $18/MWh, it's a $2.4M/year error.
+
+The structural congestion is unlikely to reverse quickly — the data center load is permanent, the retired plant is not coming back, and new transmission or local generation takes 3-7 years to build.
+
+**Common Mistake:**
+Assuming the congestion is temporary and will revert to historical levels. Structural congestion caused by load growth and generation retirement is persistent until the grid is physically reconfigured. The second mistake: trying to renegotiate the supply contract — the supplier is delivering at the agreed-upon hub price and is not responsible for zonal congestion.
+
+**Expert Approach:**
+1. **Immediate contract restructuring:** Switch the supply contract settlement point from Western Hub to the JCPL zone (load zone pricing). The supplier will quote a higher price that reflects the zone premium, but this eliminates the basis exposure. The company pays a known, locked-in price that includes congestion, rather than a low hub price plus an unpredictable congestion pass-through.
+
+2. **FTR procurement:** Purchase Financial Transmission Rights (FTRs) from Western Hub to the JCPL zone in PJM's monthly or annual FTR auction. An FTR pays the congestion component between the two points — if congestion is $18/MWh and you hold an FTR for your load volume, you receive $18/MWh × volume in FTR settlement, offsetting the congestion charge on your utility bill.
+
+3. **On-site generation evaluation:** With zonal LMPs at $58/MWh during peak hours, the economics for on-site generation improve dramatically. A 5 MW natural gas combined heat and power (CHP) system generating at $40/MWh (fuel + O&M) would save $18/MWh on the kWh it generates. At 8,000 hours/year: $720K/year savings on a $7-$10M capital investment — strong payback.
+
+4. **Long-term transmission monitoring:** Track PJM's Regional Transmission Expansion Plan (RTEP) for projects addressing the JCPL constraint. If PJM approves a transmission upgrade, the congestion may ease in 4-6 years. Factor this into the decision on long-term investments like CHP — if the congestion premium will disappear in 5 years, a CHP plant that was justified by congestion savings may not pencil on its own economics.
+
+5. **Budget reforecast:** Immediately reforecast the energy budget using the new basis reality. Use $55-$60/MWh as the delivered cost assumption until the contract is restructured. Present to finance with a clear explanation of the structural change and the remediation timeline.
+
+**Key Indicators:**
+- PJM Congestion reports showing zonal basis >$10/MWh for >30% of peak hours indicates structural congestion
+- Generator retirement announcements in your zone without replacement capacity signal worsening congestion
+- Large load interconnection applications (data centers, industrial facilities) in your zone increase future congestion risk
+- PJM RTEP project approvals targeting your constraint indicate relief timeline (but delivery is typically 4-7 years out)
+
+**Documentation Required:**
+- Hourly LMP data for Western Hub and JCPL zone (12+ months)
+- Basis calculation spreadsheet (generation-weighted for PPA, load-weighted for supply)
+- FTR auction bid strategy and results
+- CHP feasibility study (if applicable)
+- Budget reforecast with basis scenarios
+- Communication log with supplier regarding settlement point change
+
+**Resolution Timeline:**
+- Week 1: Quantify basis exposure, pull LMP data, reforecast budget
+- Week 2-3: Evaluate FTR procurement, contact supplier about settlement point change
+- Month 2: Execute contract restructuring (settlement point or FTR hedge)
+- Month 3-6: Monitor whether structural congestion persists, evaluate CHP or on-site generation
+- Month 6-12: Reassess portfolio-level strategy for facilities in congested zones
+
+---
+
+### Edge Case 11: Retail Energy Provider Credit Deterioration Mid-Contract
+
+**Situation:**
+A healthcare system with 8 hospitals across Pennsylvania has a 36-month fixed-price electricity supply contract with GreenPeak Energy Solutions, a mid-tier retail energy provider. The contract covers 120 GWh/year at $0.058/kWh energy — well below the current market of $0.067/kWh. GreenPeak's S&P credit rating was BBB at contract signing. Eighteen months into the contract, GreenPeak is downgraded to BB+ (sub-investment grade) after reporting significant trading losses in the most recent quarter. Industry reports suggest GreenPeak overcommitted on fixed-price contracts when forward curves were low and is now underwater as market prices have risen.
+
+The healthcare system's contract has a termination provision allowing either party to exit with 90 days' notice if a material adverse change occurs, including a credit downgrade below investment grade. If GreenPeak fails, the hospitals revert to the utility's default service at $0.071/kWh — a $1.56M annual cost increase.
+
+**Why It's Tricky:**
+The contract is favorable — $0.058/kWh is $0.009/kWh below market. Exercising the termination right is irrational (you'd voluntarily lose a below-market contract). But NOT exercising it means staying exposed to a supplier that may default. If GreenPeak declares bankruptcy, the contract may be rejected in bankruptcy court, and the hospitals lose the favorable rate anyway. The risk calculus: certain below-market pricing today vs. potential forced exit to above-market default service later.
+
+Complicating factor: healthcare facilities cannot tolerate billing disruption. Hospitals must have unambiguous supply arrangements for regulatory compliance, and a supplier default triggers administrative chaos (account switches, utility enrollment, billing reconciliation) that disproportionately impacts a multi-site healthcare system.
+
+**Common Mistake:**
+Doing nothing because the contract is favorable and hoping GreenPeak survives. The second mistake: exercising the termination right immediately and losing the below-market rate. Both extremes are wrong.
+
+**Expert Approach:**
+1. **Credit monitoring (immediate):** Set up alerts for further credit actions on GreenPeak — S&P CreditWatch, Moody's review, and any SEC filings (8-K, 10-Q with going concern language). A further downgrade to BB or below, or a going concern note, significantly increases default probability.
+
+2. **Contract review:** Examine the contract for:
+ - **Adequate assurance clause:** Can you demand financial assurance (letter of credit, parent guarantee) from GreenPeak as a condition of continuing the contract? Many commercial supply contracts include this right upon a material credit event.
+ - **Assignment rights:** Can the contract be assigned to another creditworthy supplier? If GreenPeak is acquired or merges with a stronger company, your contract may survive.
+ - **Setoff rights:** If GreenPeak owes you credits (overcollections, reconciliation adjustments), can you offset those against future payments?
+
+3. **Demand adequate assurance (Week 1):** Formally request that GreenPeak post a standby letter of credit equal to 3-6 months of expected below-market value. Calculate: ($0.067 market - $0.058 contract) × 120 GWh / 12 months × 6 months = $540,000 LC. This protects the healthcare system if GreenPeak defaults — the LC covers the cost of switching to a new supplier at market rates during the transition period.
+
+4. **Parallel supplier qualification (Week 1-3):** Issue an expedited RFP to 3-4 investment-grade suppliers for a replacement contract. Obtain indicative pricing so you know exactly what the replacement cost would be if GreenPeak fails. This is not a commitment — it's insurance. Having a qualified backup supplier with a standing offer reduces the transition time from weeks to days.
+
+5. **Hedging the replacement risk (Month 1):** If the replacement cost at market ($0.067) is significantly above your contract ($0.058), consider purchasing a financial hedge that pays out if you're forced to switch suppliers. Specifically, buy a call option on PJM electricity at a strike price of $0.060/kWh for the remaining contract volume. If GreenPeak defaults and you switch to a market-priced supplier, the call option offsets the cost increase above $0.060.
+
+6. **Ongoing monitoring cadence:** Review GreenPeak's financial health monthly. Track: credit rating changes, SEC filings, employee LinkedIn departures (mass exits from a supplier signal trouble), utility regulatory filings (some states require REPs to post bonds), and industry rumors (energy industry is small — your broker will hear about financial distress before it hits the news).
+
+**Key Indicators:**
+- Supplier credit downgrade below BBB- (investment grade threshold) is the first warning
+- Supplier requesting early payment, changing payment terms, or delaying customer credits signals cash flow problems
+- Supplier laying off commercial/pricing staff suggests they're de-risking by not taking new business
+- State utility commission audits of REP financial requirements may reveal shortfalls
+- If 2+ other C&I buyers report the same supplier is requesting contract modifications, the supplier is restructuring its book
+
+**Documentation Required:**
+- Credit rating history and monitoring alerts
+- Adequate assurance demand letter and GreenPeak response
+- Replacement supplier indicative pricing
+- Financial hedge evaluation (call option cost vs. benefit)
+- Board-level risk assessment memo
+- Contingency communication plan for hospitals (billing continuity)
+
+**Resolution Timeline:**
+- Week 1: Demand adequate assurance, initiate backup supplier RFP
+- Week 2-3: Receive GreenPeak response to assurance demand, evaluate backup bids
+- Month 1-2: If assurance is posted, continue monitoring. If refused, evaluate termination.
+- Month 3+: Monthly credit monitoring until GreenPeak's financial position stabilizes or the contract expires
+
+---
+
+### Edge Case 12: Multi-State Portfolio with Mixed Regulated/Deregulated Markets
+
+**Situation:**
+A food and beverage company operates 35 facilities across 18 states: 15 manufacturing plants (2-12 MW each), 12 distribution centers (500 kW - 3 MW each), and 8 corporate/R&D offices (200-800 kW each). Total electricity consumption: 680 GWh/year, $58M annual energy spend. The facilities are split: 20 in deregulated markets (PJM, ERCOT, NYISO, ISO-NE), 10 in regulated markets (Georgia, Florida, Alabama, Tennessee), and 5 in markets with limited competition (partial deregulation or pilot programs).
+
+The VP of Sustainability has committed the company to RE100 by 2030. The CFO wants 5% annual energy cost reduction. The Director of Operations wants zero disruption to production. Currently, each facility manages its own utility relationship — there is no centralized energy procurement function. Tariff selection, contract renewals, and demand charge management are handled by facility managers with no energy expertise, resulting in:
+- 12 facilities on suboptimal tariff schedules (estimated $1.2M/year in unnecessary charges)
+- 6 deregulated sites on utility default service (never switched to competitive supply — $2.1M/year above market)
+- No demand charge management programs at any facility
+- RE100 progress at 12% (entirely from unbundled RECs purchased by the sustainability team)
+
+**Why It's Tricky:**
+Building a centralized energy procurement function from scratch requires addressing every aspect simultaneously: competitive procurement in deregulated markets, tariff optimization in regulated markets, demand charge management at high-potential sites, renewable procurement to hit RE100, and budget forecasting and reporting across 35 facilities. With no existing infrastructure, even basic tasks like assembling interval data for 35 facilities take months.
+
+The mixed regulatory landscape means no single strategy works everywhere. A VPPA that works for PJM sites is irrelevant for Georgia sites. Demand charge management that works at a manufacturing plant doesn't apply to an office. Tariff optimization requires state-by-state regulatory expertise.
+
+**Common Mistake:**
+Trying to do everything at once — hiring a consultant, issuing an enterprise RFP, signing a mega-VPPA, and installing batteries at every site simultaneously. This overwhelms the organization, produces poor execution on every front, and alienates facility managers who feel central procurement is disrupting their operations.
+
+**Expert Approach:**
+1. **Phase 0: Data assembly and baselining (Month 1-3).**
+ Deploy an energy management information system (EMIS) like EnergyCAP, Urjanet, or UtilityAPI to automatically collect utility bill data for all 35 sites. This eliminates the manual data collection bottleneck. Target: complete 12-month utility bill history and interval data for all sites within 90 days.
+
+2. **Phase 1: Quick wins (Month 2-6).** Prioritize actions with immediate savings and minimal disruption:
+ - **Switch 6 default-service sites to competitive supply.** Issue an aggregated RFP covering all 6 sites (combined volume gives leverage). Expected savings: 10-15% on energy charges = $200K-$300K/year per site.
+ - **Tariff audit all 35 sites.** Engage a tariff optimization consultant or use software to model each site against all available rate schedules. Switch 12 sites to optimal tariffs. Expected savings: $1.2M/year.
+ - **Demand charge review for top 10 sites by demand charge cost.** Implement zero-cost measures (staggered startups, BAS programming) at the top 5 sites. Expected savings: $300K-$500K/year.
+
+ Phase 1 total savings estimate: $2.5M-$4M/year, achievable within 6 months.
+
+3. **Phase 2: Strategic procurement (Month 4-12).** With data and quick wins establishing credibility:
+ - **Portfolio procurement for deregulated sites.** Aggregate 20 deregulated sites by ISO and issue portfolio RFPs. Use layered block-and-index structure for manufacturing (high load factor) and fixed-price for offices/DCs (lower load factor, less optimization potential).
+ - **Demand charge capital projects.** Using Phase 1 analysis, identify 3-5 sites where battery storage or demand response has <5 year payback. Develop business cases and submit for capital approval.
+ - **Renewable procurement strategy.** Design a phased RE100 roadmap:
+ - Year 1-2: Switch unbundled RECs from national wind to project-specific solar RECs (better additionality, modest cost increase)
+ - Year 2-3: Execute first VPPA (100-150 GWh/year) targeting PJM or MISO sites
+ - Year 3-4: Add a second VPPA or physical PPA for ERCOT sites
+ - Year 4-5: On-site solar at 5-8 facilities with favorable economics
+ - Year 5-6: Utility green tariffs or community solar for regulated market sites
+
+4. **Phase 3: Optimization and continuous improvement (Year 2+).** With infrastructure in place:
+ - Implement real-time energy monitoring and automated demand response at top 15 sites
+ - Build internal capability for capacity tag management (PJM, ISO-NE)
+ - Establish a quarterly energy procurement committee (finance, sustainability, operations, procurement)
+ - Develop forward-looking energy risk management policy with hedge ratios and governance
+
+5. **Governance and reporting:** From Day 1, establish a reporting framework:
+ - Monthly: energy cost vs. budget by site, demand charge performance, supply contract status
+ - Quarterly: portfolio-level hedge ratio, RE100 progress, supplier scorecard, market outlook
+ - Annually: total energy spend vs. prior year (weather-normalized), cost avoidance from optimization, sustainability target progress, 3-year procurement strategy refresh
+
+**Key Indicators:**
+- If quick wins (Phase 1) don't deliver $2M+ in annual savings, the baseline analysis was wrong — revisit data
+- Facility manager resistance to centralized procurement is the #1 implementation risk — address it through communication and shared savings incentives
+- RE100 progress requires committed procurement volume, not just REC purchases — if RE% stalls at 30-40%, it's because the VPPA/PPA pipeline isn't producing
+- Total energy cost as a percentage of revenue should decrease YoY (weather-normalized) — if it's flat or increasing, the optimization program isn't working
+
+**Documentation Required:**
+- 35-site energy baseline (utility bills, interval data, tariff schedules, contracts)
+- Phase 1 savings tracking (actual vs. projected by initiative)
+- Portfolio procurement RFP and award documentation
+- RE100 roadmap with annual milestones and procurement commitments
+- Energy risk management policy
+- Capital project business cases for demand-side investments
+- Quarterly energy management committee reports
+
+**Resolution Timeline:**
+- Month 1-3: Data assembly, EMIS deployment, Phase 0 complete
+- Month 2-6: Phase 1 quick wins executed, $2.5M-$4M/year savings captured
+- Month 4-12: Phase 2 strategic procurement, first VPPA executed
+- Year 2: Phase 3 optimization, demand-side capital projects operational
+- Year 3: RE100 at 50%+, energy cost reduction at 15%+ from baseline
+- Year 5: RE100 at 80%+, fully mature energy management program
+
+---
+
+### Edge Case 13: Natural Gas Supply Disruption During Winter Heating Season
+
+**Situation:**
+A pharmaceutical manufacturer in New Jersey operates a 150,000 sq ft production facility with a 6,000 MMBtu/month winter natural gas load (process heat for API synthesis plus facility heating). The facility is on a firm transportation gas contract with a local distribution company (LDC) at a rate of $8.50/MMBtu delivered. During a prolonged January cold snap (15 consecutive days below 15°F), the LDC issues an Operational Flow Order (OFO) restricting deliveries to critical-use customers only. The pharmaceutical plant's gas supply is not classified as "critical use" under the LDC's tariff — hospitals and residential heating take priority.
+
+The OFO reduces the facility's gas allocation to 60% of normal. The remaining 40% (2,400 MMBtu/month) must be sourced on the spot market through an alternative supply arrangement, or the facility must curtail operations. Spot gas at the Transco Zone 6 delivery point is trading at $28/MMBtu — more than 3× the contract rate. Alternatively, the facility could switch some process heat to electric resistance heating, but this would increase electricity demand by 1.8 MW during a period when electricity prices are also elevated ($180/MWh due to gas-fired generation being price-setting at high gas prices).
+
+The pharmaceutical product in process has a 72-hour window before it must be temperature-controlled or destroyed — $4.2M worth of active pharmaceutical ingredient is at risk.
+
+**Why It's Tricky:**
+The facility faces a trilemma: (1) pay $28/MMBtu spot gas to maintain full operations (4× the normal cost), (2) switch to electric heating at $180/MWh equivalent cost (which may be even more expensive per BTU than spot gas), or (3) curtail production and risk $4.2M in product loss. None of these options is clearly superior, and the decision must be made within hours.
+
+The LDC's OFO is legally enforceable — the tariff allows curtailment of non-critical-use customers during supply emergencies. The facility's "firm" gas contract is firm for transportation, but the OFO overrides transportation priority during emergencies. This is a distinction most facility managers don't understand until it happens.
+
+**Common Mistake:**
+Assuming "firm" gas service means guaranteed delivery under all conditions. Firm transportation is firm relative to interruptible service — but OFOs can curtail even firm customers. The second mistake: relying entirely on gas without a dual-fuel backup for critical process heat.
+
+**Expert Approach:**
+1. **Immediate triage (Hour 0-2):** Calculate the cost of each option per MMBtu equivalent:
+ - Spot gas: $28/MMBtu delivered
+ - Electric resistance heating: $180/MWh ÷ 3,412 BTU/kWh × 1,000,000 = $52.75/MMBtu equivalent (even more expensive than spot gas and subject to demand charge spikes)
+ - Product loss: $4.2M ÷ 72 hours = $58,333/hour of delay. Even at $28/MMBtu, running the process heat costs far less than product loss.
+
+ **Decision: Purchase spot gas at $28/MMBtu for process heat. Use electric heating only for space heating (lower priority, can tolerate temperature setback).**
+
+2. **Spot gas procurement (Hour 0-4):** Contact your gas marketer or broker to secure spot supply at Transco Zone 6. Request a 15-day deal (covering the forecast cold snap duration). Negotiate for a fixed daily quantity with a price cap rather than floating daily pricing — during extreme events, daily spot prices can swing $10-$15/MMBtu between morning and afternoon.
+
+3. **Demand charge protection (Hour 0):** If switching any load to electric heating, install temporary demand limiting controls. A 1.8 MW increase in electric demand at a $15/kW demand rate = $27,000/month in additional demand charges, plus potential ratchet impact. If possible, offset the added electric load by curtailing other electric loads (lighting, non-essential compressed air).
+
+4. **Dual-fuel capability assessment (Week 2, post-event):** After the event, evaluate installing dual-fuel capability for the critical process heat systems. A dual-fuel burner that can switch between gas and #2 fuel oil costs $150K-$300K for a 6,000 MMBtu/month system. With fuel oil on-site in a storage tank, the facility can maintain operations during gas curtailments without relying on spot gas or electric conversion. Annual carrying cost (tank rental, fuel turnover): $25K-$40K.
+
+5. **LDC tariff engagement (Month 2-3):** Petition the LDC to reclassify the pharmaceutical facility as "critical use" under the tariff. Pharmaceutical manufacturing has arguments for critical use designation: product at risk of destruction, FDA compliance implications, public health importance. The reclassification requires a tariff filing with the state utility commission — engage regulatory counsel.
+
+6. **Contractual protection (next renewal):** At the next gas contract renewal, negotiate a "firm-firm" or "no-notice" transportation agreement that provides the highest curtailment priority available from the LDC. This costs 10-20% more than standard firm transportation but eliminates OFO exposure. Alternatively, negotiate a "supplemental supply" agreement with a gas marketer that automatically activates when the LDC issues an OFO — pre-arranged backup supply at a pre-negotiated spread above the index.
+
+**Key Indicators:**
+- Weather forecasts showing >10 consecutive days below 20°F in the Northeast signal potential OFO conditions
+- LDC "system alerts" or "constraint days" preceding a full OFO — act on alerts, don't wait for the OFO
+- Henry Hub spot gas exceeding $5/MMBtu during winter signals tight national supply — regional prices will spike harder
+- Electricity price correlation: when gas spot is elevated, electricity spot is elevated proportionally — electric heating is not a cheap alternative during gas supply emergencies
+
+**Documentation Required:**
+- LDC Operational Flow Order notification and curtailment percentage
+- Spot gas purchase confirmations and pricing
+- Product-at-risk calculation and decision documentation
+- Electric load impact and demand charge analysis
+- Post-event dual-fuel capability feasibility study
+- LDC tariff reclassification petition (if pursuing critical use designation)
+- Gas contract renewal strategy with enhanced curtailment protection
+
+**Resolution Timeline:**
+- Hour 0-4: Triage, spot gas procurement, demand limiting controls
+- Days 1-15: Manage blended gas supply (contract + spot), monitor cold snap duration
+- Week 3: Post-event financial analysis, present cost impact to management
+- Month 2-3: Initiate dual-fuel feasibility study, LDC tariff reclassification
+- Month 4-6: Install dual-fuel capability (if approved), negotiate enhanced gas contract
+- Next renewal: Execute firm-firm or no-notice gas transportation agreement
diff --git a/skills/error-detective/SKILL.md b/skills/error-detective/SKILL.md
index 8af4f438..cd8c8fd0 100644
--- a/skills/error-detective/SKILL.md
+++ b/skills/error-detective/SKILL.md
@@ -1,6 +1,7 @@
---
name: error-detective
-description: "Search logs and codebases for error patterns, stack traces, and"
+description: |
+ Search logs and codebases for error patterns, stack traces, and
anomalies. Correlates errors across systems and identifies root causes. Use
PROACTIVELY when debugging issues, analyzing logs, or investigating production
errors.
diff --git a/skills/fastapi-pro/SKILL.md b/skills/fastapi-pro/SKILL.md
index f07b0e60..b84a2913 100644
--- a/skills/fastapi-pro/SKILL.md
+++ b/skills/fastapi-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: fastapi-pro
-description: "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and"
+description: |
+ Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and
Pydantic V2. Master microservices, WebSockets, and modern Python async
patterns. Use PROACTIVELY for FastAPI development, async optimization, or API
architecture.
diff --git a/skills/firmware-analyst/SKILL.md b/skills/firmware-analyst/SKILL.md
index 83f56424..a0fcf517 100644
--- a/skills/firmware-analyst/SKILL.md
+++ b/skills/firmware-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: firmware-analyst
-description: "Expert firmware analyst specializing in embedded systems, IoT"
+description: |
+ Expert firmware analyst specializing in embedded systems, IoT
security, and hardware reverse engineering. Masters firmware extraction,
analysis, and vulnerability research for routers, IoT devices, automotive
systems, and industrial controllers. Use PROACTIVELY for firmware security
diff --git a/skills/flutter-expert/SKILL.md b/skills/flutter-expert/SKILL.md
index 7b8ee06a..f5d6d848 100644
--- a/skills/flutter-expert/SKILL.md
+++ b/skills/flutter-expert/SKILL.md
@@ -1,6 +1,7 @@
---
name: flutter-expert
-description: "Master Flutter development with Dart 3, advanced widgets, and"
+description: |
+ Master Flutter development with Dart 3, advanced widgets, and
multi-platform deployment. Handles state management, animations, testing, and
performance optimization for mobile, web, desktop, and embedded platforms. Use
PROACTIVELY for Flutter architecture, UI implementation, or cross-platform
diff --git a/skills/form-cro/SKILL.md b/skills/form-cro/SKILL.md
index d6ec718a..42691609 100644
--- a/skills/form-cro/SKILL.md
+++ b/skills/form-cro/SKILL.md
@@ -1,6 +1,6 @@
---
name: form-cro
-description: ">"
+description: >
Optimize any form that is NOT signup or account registration — including lead
capture, contact, demo request, application, survey, quote, and checkout forms.
Use when the goal is to increase form completion rate, reduce friction, or
diff --git a/skills/frontend-developer/SKILL.md b/skills/frontend-developer/SKILL.md
index 9076ec20..0f065ebb 100644
--- a/skills/frontend-developer/SKILL.md
+++ b/skills/frontend-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: frontend-developer
-description: "Build React components, implement responsive layouts, and handle"
+description: |
+ Build React components, implement responsive layouts, and handle
client-side state management. Masters React 19, Next.js 15, and modern
frontend architecture. Optimizes performance and ensures accessibility. Use
PROACTIVELY when creating UI components or fixing frontend issues.
diff --git a/skills/frontend-security-coder/SKILL.md b/skills/frontend-security-coder/SKILL.md
index fd8d22dc..1edc8ade 100644
--- a/skills/frontend-security-coder/SKILL.md
+++ b/skills/frontend-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: frontend-security-coder
-description: "Expert in secure frontend coding practices specializing in XSS"
+description: |
+ Expert in secure frontend coding practices specializing in XSS
prevention, output sanitization, and client-side security patterns. Use
PROACTIVELY for frontend security implementations or client-side security code
reviews.
diff --git a/skills/golang-pro/SKILL.md b/skills/golang-pro/SKILL.md
index 807a3552..5393bc58 100644
--- a/skills/golang-pro/SKILL.md
+++ b/skills/golang-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: golang-pro
-description: "Master Go 1.21+ with modern patterns, advanced concurrency,"
+description: |
+ Master Go 1.21+ with modern patterns, advanced concurrency,
performance optimization, and production-ready microservices. Expert in the
latest Go ecosystem including generics, workspaces, and cutting-edge
frameworks. Use PROACTIVELY for Go development, architecture design, or
diff --git a/skills/graphql-architect/SKILL.md b/skills/graphql-architect/SKILL.md
index b6f5fb25..211e873e 100644
--- a/skills/graphql-architect/SKILL.md
+++ b/skills/graphql-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: graphql-architect
-description: "Master modern GraphQL with federation, performance optimization,"
+description: |
+ Master modern GraphQL with federation, performance optimization,
and enterprise security. Build scalable schemas, implement advanced caching,
and design real-time systems. Use PROACTIVELY for GraphQL architecture or
performance optimization.
diff --git a/skills/grpc-golang/SKILL.md b/skills/grpc-golang/SKILL.md
new file mode 100644
index 00000000..66d17712
--- /dev/null
+++ b/skills/grpc-golang/SKILL.md
@@ -0,0 +1,103 @@
+---
+name: grpc-golang
+description: "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport."
+risk: safe
+source: self
+---
+
+# gRPC Golang (gRPC-Go)
+
+## Overview
+
+Comprehensive guide for designing and implementing production-grade gRPC services in Go. Covers contract standardization with Buf, transport layer security via mTLS, and deep observability with OpenTelemetry interceptors.
+
+## Use this skill when
+
+- Designing microservices communication with gRPC in Go.
+- Building high-performance internal APIs using Protobuf.
+- Implementing streaming workloads (unidirectional or bidirectional).
+- Standardizing API contracts using Protobuf and Buf.
+- Configuring mTLS for service-to-service authentication.
+
+## Do not use this skill when
+
+- Building pure REST/HTTP public APIs without gRPC requirements.
+- Modifying legacy `.proto` files without the ability to introduce a new API version (e.g., `api.v2`) or ensure backward compatibility.
+- Managing service mesh traffic routing (e.g., Istio/Linkerd), which is outside the application code scope.
+
+## Step-by-Step Guide
+
+1. **Confirm Technical Context**: Identify Go version, gRPC-Go version, and whether the project uses Buf or raw protoc.
+2. **Confirm Requirements**: Identify mTLS needs, load patterns (unary/streaming), SLOs, and message size limits.
+3. **Plan Schema**: Define package versioning (e.g., `api.v1`), resource types, and error mapping.
+4. **Security Design**: Implement mTLS for service-to-service authentication.
+5. **Observability**: Configure interceptors for tracing, metrics, and structured logging.
+6. **Verification**: Always run `buf lint` and breaking change checks before finalizing code generation.
+
+Refer to `resources/implementation-playbook.md` for detailed patterns, code examples, and anti-patterns.
+
+## Examples
+
+### Example 1: Defining a Service & Message (v1 API)
+
+```proto
+syntax = "proto3";
+package api.v1;
+option go_package = "github.com/org/repo/gen/api/v1;apiv1";
+
+service UserService {
+ rpc GetUser(GetUserRequest) returns (GetUserResponse);
+}
+
+message User {
+ string id = 1;
+ string name = 2;
+}
+
+message GetUserRequest {
+ string id = 1;
+}
+
+message GetUserResponse {
+ User user = 1;
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use Buf to standardize your toolchain and linting with `buf.yaml` and `buf.gen.yaml`.
+- ✅ **Do:** Always use semantic versioning in package paths (e.g., `package api.v1`).
+- ✅ **Do:** Enforce mTLS for all internal service-to-service communication.
+- ✅ **Do:** Handle `ctx.Done()` in all streaming handlers to prevent resource leaks.
+- ✅ **Do:** Map domain errors to standard gRPC status codes (e.g., `codes.NotFound`).
+- ❌ **Don't:** Return raw internal error strings or stack traces to gRPC clients.
+- ❌ **Don't:** Create a new `grpc.ClientConn` per request; always reuse connections.
+
+## Troubleshooting
+
+- **Error: Inconsistent Gen**: If the generated code does not match the schema, run `buf generate` and verify the `go_package` option.
+- **Error: Context Deadline**: Check client timeouts and ensure the server is not blocking infinitely in streaming handlers.
+- **Error: mTLS Handshake**: Ensure the CA certificate is correctly added to the `x509.CertPool` on both client and server sides.
+
+## Limitations
+
+- Does not cover service mesh traffic routing (Istio/Linkerd configuration).
+- Does not cover gRPC-Web or browser-based gRPC integration.
+- Assumes Go 1.21+ and gRPC-Go v1.60+; older versions may have different APIs (e.g., `grpc.Dial` vs `grpc.NewClient`).
+- Does not cover L7 gRPC-aware load balancer configuration (e.g., Envoy, NGINX).
+- Does not address Protobuf schema registry or large-scale schema governance beyond Buf lint.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, code examples, and anti-patterns.
+- [Google API Design Guide](https://cloud.google.com/apis/design)
+- [Buf Docs](https://buf.build/docs)
+- [gRPC-Go Docs](https://grpc.io/docs/languages/go/)
+- [OpenTelemetry Go Instrumentation](https://opentelemetry.io/docs/instrumentation/go/)
+
+## Related Skills
+
+- @golang-pro - General Go patterns and performance optimization outside the gRPC layer.
+- @go-concurrency-patterns - Advanced goroutine lifecycle management for streaming handlers.
+- @api-design-principles - Resource naming and versioning strategy before writing `.proto` files.
+- @docker-expert - Containerizing gRPC services and configuring TLS cert injection via Docker secrets.
diff --git a/skills/grpc-golang/resources/implementation-playbook.md b/skills/grpc-golang/resources/implementation-playbook.md
new file mode 100644
index 00000000..e6eece49
--- /dev/null
+++ b/skills/grpc-golang/resources/implementation-playbook.md
@@ -0,0 +1,548 @@
+# gRPC Golang Implementation Playbook
+
+This file contains detailed patterns, checklists, and code samples referenced by the skill.
+
+## Schema Design Standards
+
+### Protobuf Definition
+
+- **Syntax**: Use proto3 only.
+- **Versioning**: Use package versioning (e.g., `api.v1`).
+- **Pagination**: Use `page_token` and `page_size` for list operations.
+- **Timezone**: Always use `google.protobuf.Timestamp` with UTC values at the server level.
+- **Idempotency**: Use idempotency keys or design side-effect-free methods to allow safe retries.
+- **Validation**: Adopt a schema-level validation approach (e.g., Buf validation rules or `protoc-gen-validate`) and ensure generated code is enforced server-side.
+
+```proto
+syntax = "proto3";
+package api.v1;
+option go_package = "github.com/org/repo/gen/api/v1;apiv1";
+
+import "google/protobuf/timestamp.proto";
+
+service UserService {
+ rpc GetUser(GetUserRequest) returns (GetUserResponse);
+ rpc ListUsers(ListUsersRequest) returns (ListUsersResponse);
+ rpc WatchUsers(WatchUsersRequest) returns (stream UserEvent);
+}
+
+message User {
+ string id = 1;
+ string name = 2;
+ string email = 3;
+ google.protobuf.Timestamp created_at = 4;
+}
+
+message GetUserRequest {
+ string id = 1;
+}
+
+message GetUserResponse {
+ User user = 1;
+}
+
+message ListUsersRequest {
+ int32 page_size = 1;
+ string page_token = 2;
+}
+
+message ListUsersResponse {
+ repeated User users = 1;
+ string next_page_token = 2;
+}
+
+message WatchUsersRequest {
+ // Empty; streams all user events from the current point.
+}
+
+message UserEvent {
+ enum EventType {
+ EVENT_TYPE_UNSPECIFIED = 0;
+ EVENT_TYPE_CREATED = 1;
+ EVENT_TYPE_UPDATED = 2;
+ EVENT_TYPE_DELETED = 3;
+ }
+ EventType type = 1;
+ User user = 2;
+ google.protobuf.Timestamp occurred_at = 3;
+}
+```
+
+## Code Generation
+
+- **Toolchain**: Use `google.golang.org/protobuf/cmd/protoc-gen-go` and `protoc-gen-go-grpc`.
+- **Management**: Use `buf.gen.yaml` to manage plugin versions and generation parameters.
+- **Compatibility**: Ensure plugins use Protobuf Go v2 API (`google.golang.org/protobuf`). Do not mix with the deprecated v1 API (`github.com/golang/protobuf`).
+
+### buf.gen.yaml Example
+
+```yaml
+version: v2
+plugins:
+ - remote: buf.build/protocolbuffers/go
+ out: gen
+ opt: paths=source_relative
+ - remote: buf.build/grpc/go
+ out: gen
+ opt: paths=source_relative
+```
+
+## Server Implementation
+
+### Full Server Setup with Graceful Shutdown
+
+```go
+package main
+
+import (
+ "context"
+ "log"
+ "net"
+ "os"
+ "os/signal"
+ "syscall"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/health"
+ healthpb "google.golang.org/grpc/health/grpc_health_v1"
+ "google.golang.org/grpc/keepalive"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+func main() {
+ srv := grpc.NewServer(
+ grpc.ChainUnaryInterceptor(
+ recoveryInterceptor,
+ loggingInterceptor,
+ otelUnaryInterceptor,
+ ),
+ grpc.KeepaliveParams(keepalive.ServerParameters{
+ MaxConnectionIdle: 5 * time.Minute,
+ Time: 1 * time.Minute,
+ Timeout: 20 * time.Second,
+ }),
+ grpc.MaxRecvMsgSize(4<<20), // 4 MB
+ grpc.MaxSendMsgSize(4<<20), // 4 MB
+ )
+
+ // Register application services.
+ apiv1.RegisterUserServiceServer(srv, newUserService())
+
+ // Register health check with fully-qualified service name.
+ healthSrv := health.NewServer()
+ healthpb.RegisterHealthServer(srv, healthSrv)
+ healthSrv.SetServingStatus(
+ "api.v1.UserService",
+ healthpb.HealthCheckResponse_SERVING,
+ )
+
+ lis, err := net.Listen("tcp", ":50051")
+ if err != nil {
+ log.Fatalf("listen: %v", err)
+ }
+
+ // Graceful shutdown: GracefulStop with a fallback timeout to Stop.
+ go func() {
+ sigCh := make(chan os.Signal, 1)
+ signal.Notify(sigCh, syscall.SIGINT, syscall.SIGTERM)
+ <-sigCh
+
+ log.Println("shutting down gRPC server...")
+ healthSrv.SetServingStatus(
+ "api.v1.UserService",
+ healthpb.HealthCheckResponse_NOT_SERVING,
+ )
+
+ ctx, cancel := context.WithTimeout(context.Background(), 15*time.Second)
+ defer cancel()
+
+ stopped := make(chan struct{})
+ go func() {
+ srv.GracefulStop()
+ close(stopped)
+ }()
+
+ select {
+ case <-stopped:
+ log.Println("server stopped gracefully")
+ case <-ctx.Done():
+ log.Println("graceful stop timed out, forcing stop")
+ srv.Stop()
+ }
+ }()
+
+ log.Printf("gRPC server listening on %s", lis.Addr())
+ if err := srv.Serve(lis); err != nil {
+ log.Fatalf("serve: %v", err)
+ }
+}
+```
+
+## mTLS Setup
+
+```go
+package main
+
+import (
+ "crypto/tls"
+ "crypto/x509"
+ "fmt"
+ "log"
+ "os"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials"
+)
+
+// loadServerTLS configures mTLS for the server side.
+func loadServerTLS() grpc.ServerOption {
+ tlsCert, err := tls.LoadX509KeyPair("server.crt", "server.key")
+ if err != nil {
+ log.Fatalf("load server cert: %v", err)
+ }
+
+ caCert, err := os.ReadFile("ca.crt")
+ if err != nil {
+ log.Fatalf("read CA cert: %v", err)
+ }
+
+ caPool := x509.NewCertPool()
+ if !caPool.AppendCertsFromPEM(caCert) {
+ log.Fatal("failed to append CA cert")
+ }
+
+ tlsCfg := &tls.Config{
+ Certificates: []tls.Certificate{tlsCert},
+ ClientCAs: caPool,
+ ClientAuth: tls.RequireAndVerifyClientCert,
+ MinVersion: tls.VersionTLS13,
+ }
+ return grpc.Creds(credentials.NewTLS(tlsCfg))
+}
+
+// dialWithMTLS creates a client connection using mTLS.
+func dialWithMTLS(target string) (*grpc.ClientConn, error) {
+ clientCert, err := tls.LoadX509KeyPair("client.crt", "client.key")
+ if err != nil {
+ return nil, fmt.Errorf("load client cert: %w", err)
+ }
+
+ caCert, err := os.ReadFile("ca.crt")
+ if err != nil {
+ return nil, fmt.Errorf("read CA cert: %w", err)
+ }
+
+ caPool := x509.NewCertPool()
+ if !caPool.AppendCertsFromPEM(caCert) {
+ return nil, fmt.Errorf("failed to append CA cert")
+ }
+
+ creds := credentials.NewTLS(&tls.Config{
+ Certificates: []tls.Certificate{clientCert},
+ RootCAs: caPool,
+ MinVersion: tls.VersionTLS13,
+ })
+
+ // Note: for gRPC-Go v1.63+, grpc.NewClient is the recommended replacement.
+ conn, err := grpc.Dial(target, grpc.WithTransportCredentials(creds))
+ if err != nil {
+ return nil, fmt.Errorf("dial %s: %w", target, err)
+ }
+ return conn, nil
+}
+```
+
+## Client Best Practices
+
+### Connection Reuse
+
+```go
+package main
+
+import (
+ "context"
+ "fmt"
+ "log"
+ "os"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+// Initialize once at startup; reuse across the application lifetime.
+var userConn *grpc.ClientConn
+
+func initClients(creds credentials.TransportCredentials) {
+ var err error
+ // Note: for gRPC-Go v1.63+, use grpc.NewClient instead.
+ userConn, err = grpc.Dial(
+ os.Getenv("USER_SVC_ADDR"),
+ grpc.WithTransportCredentials(creds),
+ )
+ if err != nil {
+ log.Fatalf("dial user-svc: %v", err)
+ }
+}
+
+func callListUsers(ctx context.Context) (*apiv1.ListUsersResponse, error) {
+ // Always set a deadline per call, not per connection.
+ ctx, cancel := context.WithTimeout(ctx, 5*time.Second)
+ defer cancel()
+
+ client := apiv1.NewUserServiceClient(userConn)
+ resp, err := client.ListUsers(ctx, &apiv1.ListUsersRequest{PageSize: 20})
+ if err != nil {
+ return nil, fmt.Errorf("list users: %w", err)
+ }
+ return resp, nil
+}
+```
+
+### Retry Policy
+
+Only enable retries for idempotent calls. Use exponential backoff.
+
+```go
+import "google.golang.org/grpc"
+
+// Service config with retry policy for idempotent methods.
+const retryPolicy = `{
+ "methodConfig": [{
+ "name": [{"service": "api.v1.UserService", "method": "GetUser"}],
+ "retryPolicy": {
+ "maxAttempts": 3,
+ "initialBackoff": "0.1s",
+ "maxBackoff": "1s",
+ "backoffMultiplier": 2,
+ "retryableStatusCodes": ["UNAVAILABLE", "DEADLINE_EXCEEDED"]
+ }
+ }]
+}`
+
+// Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.Dial.
+conn, err := grpc.Dial(
+ target,
+ grpc.WithTransportCredentials(creds),
+ grpc.WithDefaultServiceConfig(retryPolicy),
+)
+```
+
+## Observability
+
+### Interceptor Labels
+
+- **Logging**: Include `grpc.method`, `grpc.service`, `grpc.code`, `latency_ms`, and `trace_id`.
+- **Metrics**: Export request count, latency histogram, and in-flight stream count.
+
+### OpenTelemetry Integration
+
+```go
+import (
+ "go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"
+ "google.golang.org/grpc"
+)
+
+srv := grpc.NewServer(
+ grpc.StatsHandler(otelgrpc.NewServerHandler()),
+)
+
+// Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.Dial.
+conn, err := grpc.Dial(
+ target,
+ grpc.WithStatsHandler(otelgrpc.NewClientHandler()),
+)
+```
+
+## Testing
+
+### bufconn In-Process Test
+
+```go
+package service_test
+
+import (
+ "context"
+ "net"
+ "testing"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials/insecure"
+ "google.golang.org/grpc/status"
+ "google.golang.org/grpc/codes"
+ "google.golang.org/grpc/test/bufconn"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+func TestListUsers(t *testing.T) {
+ lis := bufconn.Listen(1 << 20)
+ srv := grpc.NewServer()
+ apiv1.RegisterUserServiceServer(srv, &fakeUserSvc{})
+ go func() {
+ if err := srv.Serve(lis); err != nil {
+ t.Logf("server exited: %v", err)
+ }
+ }()
+ t.Cleanup(srv.GracefulStop)
+
+ // Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.DialContext.
+ conn, err := grpc.DialContext(context.Background(),
+ "bufnet",
+ grpc.WithContextDialer(func(ctx context.Context, _ string) (net.Conn, error) {
+ return lis.DialContext(ctx)
+ }),
+ grpc.WithTransportCredentials(insecure.NewCredentials()),
+ )
+ if err != nil {
+ t.Fatalf("dial bufnet: %v", err)
+ }
+ t.Cleanup(func() { conn.Close() })
+
+ client := apiv1.NewUserServiceClient(conn)
+ ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second)
+ defer cancel()
+
+ resp, err := client.ListUsers(ctx, &apiv1.ListUsersRequest{PageSize: 10})
+ if code := status.Code(err); code != codes.OK {
+ t.Fatalf("expected OK, got %v: %v", code, err)
+ }
+ if resp == nil {
+ t.Fatal("expected non-nil response")
+ }
+}
+```
+
+## Streaming Handler Pattern
+
+Always check `ctx.Done()` in streaming loops. Never expose raw internal errors to clients.
+
+```go
+func (s *userService) WatchUsers(
+ req *apiv1.WatchUsersRequest,
+ stream apiv1.UserService_WatchUsersServer,
+) error {
+ ctx := stream.Context()
+
+ events := s.subscribeUserEvents()
+ defer s.unsubscribe(events)
+
+ for {
+ select {
+ case <-ctx.Done():
+ // Client disconnected or deadline exceeded; exit cleanly.
+ return status.Error(codes.Canceled, "client disconnected")
+
+ case event, ok := <-events:
+ if !ok {
+ // Channel closed; server is shutting down.
+ return status.Error(codes.Unavailable, "service shutting down")
+ }
+
+ if err := stream.Send(event); err != nil {
+ // Log the raw error server-side for diagnostics.
+ log.Printf("stream send failed: %v", err)
+ // Return a generic message to the client; never leak raw err.
+ return status.Error(codes.Internal, "failed to send event")
+ }
+ }
+ }
+}
+```
+
+## Error Mapping
+
+Map domain errors to gRPC status codes consistently:
+
+Only return `err.Error()` to clients when it is a safe, user-facing domain message (not an internal error string).
+
+```go
+package service
+
+import (
+ "errors"
+
+ "google.golang.org/grpc/codes"
+ "google.golang.org/grpc/status"
+)
+
+var (
+ ErrNotFound = errors.New("resource not found")
+ ErrAlreadyExists = errors.New("resource already exists")
+ ErrInvalidInput = errors.New("invalid input")
+ ErrPermission = errors.New("permission denied")
+)
+
+// toGRPCError maps a domain error to a gRPC status error.
+func toGRPCError(err error) error {
+ if err == nil {
+ return nil
+ }
+ switch {
+ case errors.Is(err, ErrNotFound):
+ return status.Error(codes.NotFound, err.Error())
+ case errors.Is(err, ErrAlreadyExists):
+ return status.Error(codes.AlreadyExists, err.Error())
+ case errors.Is(err, ErrInvalidInput):
+ return status.Error(codes.InvalidArgument, err.Error())
+ case errors.Is(err, ErrPermission):
+ return status.Error(codes.PermissionDenied, err.Error())
+ default:
+ return status.Error(codes.Internal, "internal error")
+ }
+}
+```
+
+## Project Layout
+
+```
+project/
+ buf.gen.yaml
+ buf.yaml
+ proto/
+ api/
+ v1/
+ user_service.proto
+ gen/ # Generated code (committed or gitignored)
+ api/
+ v1/
+ user_service.pb.go
+ user_service_grpc.pb.go
+ internal/
+ service/
+ user.go # Service implementation
+ user_test.go # bufconn tests
+ domain/
+ errors.go # Domain error definitions
+ cmd/
+ server/
+ main.go # Server entrypoint with graceful shutdown
+ config/
+ config.go # Env-based config (timeouts, TLS paths, limits)
+```
+
+## Safety Checklist
+
+- Default to TLS/mTLS for all production traffic.
+- Enforce limits (`MaxRecvMsgSize`, `MaxSendMsgSize`, metadata size) to reduce resource exhaustion.
+- Treat client-sent metadata as untrusted; validate and allowlist keys used for auth or tenant routing.
+- Disable gRPC reflection in production to avoid exposing internal service schemas.
+- Check `context.Done()` in every iteration of a streaming handler to prevent goroutine leaks.
+
+## Anti-Patterns
+
+| Anti-Pattern | Why It Hurts | Fix |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| Create new `grpc.ClientConn` per request | Exhausts OS sockets and disables HTTP/2 multiplexing, causing high latency and resource leaks | Initialize once, reuse globally |
+| Mix Protobuf v1 and v2 libraries | Causes silent marshaling bugs; `proto.Marshal` from v1 and v2 are NOT interchangeable | Pin to `google.golang.org/protobuf` (v2) throughout |
+| Expose raw internal error strings to clients | Leaks stack traces and internal service names; a security and UX risk | Map errors with `status.Errorf` using appropriate gRPC codes |
+| Ignore `context.Done()` in streaming handlers | Goroutine and connection leak when client disconnects | Check `ctx.Err()` in every iteration of a streaming loop |
+| Skip error handling with `_ =` | Hides failures silently; production outages become undiagnosable | Always check and handle errors explicitly |
+| Use `grpc.Dial` without health checks | Connection failures are deferred and may surface as runtime errors | Use health checks and monitor connection state |
+
+> **Migration note**: For gRPC-Go v1.63+ (Jan 2024), `grpc.NewClient` is the newer API recommended by the gRPC-Go project for new code. For older versions (or when following existing codebases and official grpc.io examples), using `grpc.Dial` / `grpc.DialContext` is still common.
diff --git a/skills/hig-components-content/SKILL.md b/skills/hig-components-content/SKILL.md
index 5e6e86d9..e5083edf 100644
--- a/skills/hig-components-content/SKILL.md
+++ b/skills/hig-components-content/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-content
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about
"charts component", "collection view", "image view", "web view", "color well", "image well",
"activity view", "lockup", "data visualization", "content display", displaying images, rendering
diff --git a/skills/hig-components-controls/SKILL.md b/skills/hig-components-controls/SKILL.md
index 3bfe5397..ae7fdb11 100644
--- a/skills/hig-components-controls/SKILL.md
+++ b/skills/hig-components-controls/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-controls
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for selection and input controls including pickers, toggles,
sliders, steppers, segmented controls, combo boxes, text fields, text views,
labels, token fields, virtual keyboards, rating indicators, and gauges. Use
diff --git a/skills/hig-components-dialogs/SKILL.md b/skills/hig-components-dialogs/SKILL.md
index 1242ca6c..ce2ea3ea 100644
--- a/skills/hig-components-dialogs/SKILL.md
+++ b/skills/hig-components-dialogs/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-dialogs
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for presentation components including alerts, action sheets,
popovers, sheets, and digit entry views. Use this skill when the user says
"should I use an alert or a sheet," "how do I show a confirmation dialog,"
diff --git a/skills/hig-components-layout/SKILL.md b/skills/hig-components-layout/SKILL.md
index fd26bda2..f4c44de8 100644
--- a/skills/hig-components-layout/SKILL.md
+++ b/skills/hig-components-layout/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-layout
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user
asks about "sidebar", "split view", "tab bar", "tab view", "scroll view", "window design", "panel",
"list view", "table view", "column view", "outline view", "navigation structure", "app layout",
diff --git a/skills/hig-components-menus/SKILL.md b/skills/hig-components-menus/SKILL.md
index b75247a5..6a3b2892 100644
--- a/skills/hig-components-menus/SKILL.md
+++ b/skills/hig-components-menus/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-menus
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for menu and button components including menus, context menus,
dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons,
pull-down buttons, disclosure controls, and standard buttons. Use this skill
diff --git a/skills/hig-components-search/SKILL.md b/skills/hig-components-search/SKILL.md
index af722b5d..71f35232 100644
--- a/skills/hig-components-search/SKILL.md
+++ b/skills/hig-components-search/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-search
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for navigation-related components including search fields,
page controls, and path controls. Use this skill when the user says "how should
search work in my app," "I need a breadcrumb," "how do I paginate content," or
diff --git a/skills/hig-components-status/SKILL.md b/skills/hig-components-status/SKILL.md
index de026f09..20586287 100644
--- a/skills/hig-components-status/SKILL.md
+++ b/skills/hig-components-status/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-status
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for status and progress UI components including progress indicators,
status bars, and activity rings. Use this skill when asked about: "progress indicator",
"progress bar", "loading spinner", "status bar", "activity ring", "progress display",
diff --git a/skills/hig-components-system/SKILL.md b/skills/hig-components-system/SKILL.md
index ccf7ed22..cf87dc15 100644
--- a/skills/hig-components-system/SKILL.md
+++ b/skills/hig-components-system/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-system
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for system experience components: widgets, live activities,
notifications, complications, home screen quick actions, top shelf, watch faces,
app clips, and app shortcuts. Use when asked about: "widget design", "live activity",
diff --git a/skills/hig-foundations/SKILL.md b/skills/hig-foundations/SKILL.md
index 294e1baa..821c237b 100644
--- a/skills/hig-foundations/SKILL.md
+++ b/skills/hig-foundations/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-foundations
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines design foundations. Use this skill when the user asks about
"HIG color", "Apple typography", "SF Symbols", "dark mode guidelines", "accessible design",
"Apple design foundations", "app icon", "layout guidelines", "materials", "motion", "privacy",
diff --git a/skills/hig-inputs/SKILL.md b/skills/hig-inputs/SKILL.md
index 199f52a5..dc00c8a6 100644
--- a/skills/hig-inputs/SKILL.md
+++ b/skills/hig-inputs/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-inputs
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil,
keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system,
remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions.
diff --git a/skills/hig-patterns/SKILL.md b/skills/hig-patterns/SKILL.md
index 2114dd74..33deb5c4 100644
--- a/skills/hig-patterns/SKILL.md
+++ b/skills/hig-patterns/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-patterns
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about
"onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern",
"settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics",
diff --git a/skills/hig-platforms/SKILL.md b/skills/hig-platforms/SKILL.md
index 85eacd9e..df3a5fce 100644
--- a/skills/hig-platforms/SKILL.md
+++ b/skills/hig-platforms/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-platforms
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about
"designing for iOS", "iPad app design", "macOS design", "tvOS", "visionOS", "watchOS", "Apple platform",
"which platform", platform differences, platform-specific conventions, or multi-platform app design.
diff --git a/skills/hig-project-context/SKILL.md b/skills/hig-project-context/SKILL.md
index 1a49d8d1..95037430 100644
--- a/skills/hig-project-context/SKILL.md
+++ b/skills/hig-project-context/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-project-context
version: 1.0.0
-description: ">-"
+description: >-
Create or update a shared Apple design context document that other HIG skills
use to tailor guidance. Use when the user says "set up my project context,"
"what platforms am I targeting," "configure HIG settings," or when starting a
diff --git a/skills/hig-technologies/SKILL.md b/skills/hig-technologies/SKILL.md
index abb66f63..556cc949 100644
--- a/skills/hig-technologies/SKILL.md
+++ b/skills/hig-technologies/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-technologies
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit,
HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple,
SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps,
diff --git a/skills/hr-pro/SKILL.md b/skills/hr-pro/SKILL.md
index b9607f97..c3d81cd4 100644
--- a/skills/hr-pro/SKILL.md
+++ b/skills/hr-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: hr-pro
-description: "Professional, ethical HR partner for hiring,"
+description: |
+ Professional, ethical HR partner for hiring,
onboarding/offboarding, PTO and leave, performance, compliant policies, and
employee relations. Ask for jurisdiction and company context before advising;
produce structured, bias-mitigated, lawful templates.
diff --git a/skills/hybrid-cloud-architect/SKILL.md b/skills/hybrid-cloud-architect/SKILL.md
index cb7eaf2d..bf3b6bbe 100644
--- a/skills/hybrid-cloud-architect/SKILL.md
+++ b/skills/hybrid-cloud-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: hybrid-cloud-architect
-description: "Expert hybrid cloud architect specializing in complex multi-cloud"
+description: |
+ Expert hybrid cloud architect specializing in complex multi-cloud
solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters
hybrid connectivity, workload placement optimization, edge computing, and
cross-cloud automation. Handles compliance, cost optimization, disaster
diff --git a/skills/imagen/SKILL.md b/skills/imagen/SKILL.md
index 1497cc89..92b0bb50 100644
--- a/skills/imagen/SKILL.md
+++ b/skills/imagen/SKILL.md
@@ -1,6 +1,6 @@
---
name: imagen
-description: "|"
+description: |
source: "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
risk: safe
---
diff --git a/skills/incident-responder/SKILL.md b/skills/incident-responder/SKILL.md
index f78f9519..0ec76b66 100644
--- a/skills/incident-responder/SKILL.md
+++ b/skills/incident-responder/SKILL.md
@@ -1,6 +1,7 @@
---
name: incident-responder
-description: "Expert SRE incident responder specializing in rapid problem"
+description: |
+ Expert SRE incident responder specializing in rapid problem
resolution, modern observability, and comprehensive incident management.
Masters incident command, blameless post-mortems, error budget management, and
system reliability patterns. Handles critical outages, communication
diff --git a/skills/inventory-demand-planning/SKILL.md b/skills/inventory-demand-planning/SKILL.md
new file mode 100644
index 00000000..933d7e1d
--- /dev/null
+++ b/skills/inventory-demand-planning/SKILL.md
@@ -0,0 +1,239 @@
+---
+name: inventory-demand-planning
+description: >
+ Codified expertise for demand forecasting, safety stock optimisation,
+ replenishment planning, and promotional lift estimation at multi-location
+ retailers. Informed by demand planners with 15+ years experience managing
+ hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis,
+ seasonal transition management, and vendor negotiation frameworks.
+ Use when forecasting demand, setting safety stock, planning replenishment,
+ managing promotions, or optimising inventory levels.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "📊"
+---
+
+## When to Use
+
+Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.
+
+# Inventory Demand Planning
+
+## Role and Context
+
+You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.
+
+## Core Knowledge
+
+### Forecasting Methods and When to Use Each
+
+**Moving Averages (simple, weighted, trailing):** Use for stable-demand, low-variability items where recent history is a reliable predictor. A 4-week simple moving average works for commodity staples. Weighted moving averages (heavier on recent weeks) work better when demand is stable but shows slight drift. Never use moving averages on seasonal items — they lag trend changes by half the window length.
+
+**Exponential Smoothing (single, double, triple):** Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand with noise. Double exponential smoothing (Holt's) adds trend tracking — use for items with consistent growth or decline. Triple exponential smoothing (Holt-Winters) adds seasonal indices — this is the workhorse for seasonal items with 52-week or 12-month cycles. The alpha/beta/gamma parameters are critical: high alpha (>0.3) chases noise in volatile items; low alpha (<0.1) responds too slowly to regime changes. Optimize on holdout data, never on the same data used for fitting.
+
+**Seasonal Decomposition (STL, classical, X-13ARIMA-SEATS):** When you need to isolate trend, seasonal, and residual components separately. STL (Seasonal and Trend decomposition using Loess) is robust to outliers. Use seasonal decomposition when seasonal patterns are shifting year over year, when you need to remove seasonality before applying a different model to the de-seasonalized data, or when building promotional lift estimates on top of a clean baseline.
+
+**Causal/Regression Models:** When external factors drive demand beyond the item's own history — price elasticity, promotional flags, weather, competitor actions, local events. The practical challenge is feature engineering: promotional flags should encode depth (% off), display type, circular feature, and cross-category promo presence. Overfitting on sparse promo history is the single biggest pitfall. Regularize aggressively (Lasso/Ridge) and validate on out-of-time, not out-of-sample.
+
+**Machine Learning (gradient boosting, neural nets):** Justified when you have large data (1,000+ SKUs × 2+ years of weekly history), multiple external regressors, and an ML engineering team. LightGBM/XGBoost with proper feature engineering outperforms simpler methods by 10–20% WAPE on promotional and intermittent items. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.
+
+### Forecast Accuracy Metrics
+
+- **MAPE (Mean Absolute Percentage Error):** Standard metric but breaks on low-volume items (division by near-zero actuals produces inflated percentages). Use only for items averaging 50+ units/week.
+- **Weighted MAPE (WMAPE):** Sum of absolute errors divided by sum of actuals. Prevents low-volume items from dominating the metric. This is the metric finance cares about because it reflects dollars.
+- **Bias:** Average signed error. Positive bias = forecast systematically too high (overstock risk). Negative bias = systematically too low (stockout risk). Bias < ±5% is healthy. Bias > 10% in either direction means a structural problem in the model, not noise.
+- **Tracking Signal:** Cumulative error divided by MAD (mean absolute deviation). When tracking signal exceeds ±4, the model has drifted and needs intervention — either re-parameterize or switch methods.
+
+### Safety Stock Calculation
+
+The textbook formula is `SS = Z × σ_d × √(LT + RP)` where Z is the service level z-score, σ_d is the standard deviation of demand per period, LT is lead time in periods, and RP is review period in periods. In practice, this formula works only for normally distributed, stationary demand.
+
+**Service Level Targets:** 95% service level (Z=1.65) is standard for A-items. 99% (Z=2.33) for critical/A+ items where stockout cost dwarfs holding cost. 90% (Z=1.28) is acceptable for C-items. Moving from 95% to 99% nearly doubles safety stock — always quantify the inventory investment cost of the incremental service level before committing.
+
+**Lead Time Variability:** When vendor lead times are uncertain, use `SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)` — this captures both demand variability and lead time variability. Vendors with coefficient of variation (CV) on lead time > 0.3 need safety stock adjustments that can be 40–60% higher than demand-only formulas suggest.
+
+**Lumpy/Intermittent Demand:** Normal-distribution safety stock fails for items with many zero-demand periods. Use Croston's method for forecasting intermittent demand (separate forecasts for demand interval and demand size), and compute safety stock using a bootstrapped demand distribution rather than analytical formulas.
+
+**New Products:** No demand history means no σ_d. Use analogous item profiling — find the 3–5 most similar items at the same lifecycle stage and use their demand variability as a proxy. Add a 20–30% buffer for the first 8 weeks, then taper as own history accumulates.
+
+### Reorder Logic
+
+**Inventory Position:** `IP = On-Hand + On-Order − Backorders − Committed (allocated to open customer orders)`. Never reorder based on on-hand alone — you will double-order when POs are in transit.
+
+**Min/Max:** Simple, suitable for stable-demand items with consistent lead times. Min = average demand during lead time + safety stock. Max = Min + EOQ. When IP drops to Min, order up to Max. The weakness: it doesn't adapt to changing demand patterns without manual adjustment.
+
+**Reorder Point / EOQ:** ROP = average demand during lead time + safety stock. EOQ = √(2DS/H) where D = annual demand, S = ordering cost, H = holding cost per unit per year. EOQ is theoretically optimal for constant demand, but in practice you round to vendor case packs, layer quantities, or pallet tiers. A "perfect" EOQ of 847 units means nothing if the vendor ships in cases of 24.
+
+**Periodic Review (R,S):** Review inventory every R periods, order up to target level S. Better when you consolidate orders to a vendor on fixed days (e.g., Tuesday orders for Thursday pickup). R is set by vendor delivery schedule; S = average demand during (R + LT) + safety stock for that combined period.
+
+**Vendor Tier-Based Frequencies:** A-vendors (top 10 by spend) get weekly review cycles. B-vendors (next 20) get bi-weekly. C-vendors (remaining) get monthly. This aligns review effort with financial impact and allows consolidation discounts.
+
+### Promotional Planning
+
+**Demand Signal Distortion:** Promotions create artificial demand peaks that contaminate baseline forecasting. Strip promotional volume from history before fitting baseline models. Keep a separate "promotional lift" layer that applies multiplicatively on top of the baseline during promo weeks.
+
+**Lift Estimation Methods:** (1) Year-over-year comparison of promoted vs. non-promoted periods for the same item. (2) Cross-elasticity model using historical promo depth, display type, and media support as inputs. (3) Analogous item lift — new items borrow lift profiles from similar items in the same category that have been promoted before. Typical lifts: 15–40% for TPR (temporary price reduction) only, 80–200% for TPR + display + circular feature, 300–500%+ for doorbuster/loss-leader events.
+
+**Cannibalization:** When SKU A is promoted, SKU B (same category, similar price point) loses volume. Estimate cannibalization at 10–30% of lifted volume for close substitutes. Ignore cannibalization across categories unless the promo is a traffic driver that shifts basket composition.
+
+**Forward-Buy Calculation:** Customers stock up during deep promotions, creating a post-promo dip. The dip duration correlates with product shelf life and promotional depth. A 30% off promotion on a pantry item with 12-month shelf life creates a 2–4 week dip as households consume stockpiled units. A 15% off promotion on a perishable produces almost no dip.
+
+**Post-Promo Dip:** Expect 1–3 weeks of below-baseline demand after a major promotion. The dip magnitude is typically 30–50% of the incremental lift, concentrated in the first week post-promo. Failing to forecast the dip leads to excess inventory and markdowns.
+
+### ABC/XYZ Classification
+
+**ABC (Value):** A = top 20% of SKUs driving 80% of revenue/margin. B = next 30% driving 15%. C = bottom 50% driving 5%. Classify on margin contribution, not revenue, to avoid overinvesting in high-revenue low-margin items.
+
+**XYZ (Predictability):** X = CV of demand < 0.5 (highly predictable). Y = CV 0.5–1.0 (moderately predictable). Z = CV > 1.0 (erratic/lumpy). Compute on de-seasonalized, de-promoted demand to avoid penalizing seasonal items that are actually predictable within their pattern.
+
+**Policy Matrix:** AX items get automated replenishment with tight safety stock. AZ items need human review every cycle — they're high-value but erratic. CX items get automated replenishment with generous review periods. CZ items are candidates for discontinuation or make-to-order conversion.
+
+### Seasonal Transition Management
+
+**Buy Timing:** Seasonal buys (e.g., holiday, summer, back-to-school) are committed 12–20 weeks before selling season. Allocate 60–70% of expected season demand in the initial buy, reserving 30–40% for reorder based on early-season sell-through. This "open-to-buy" reserve is your hedge against forecast error.
+
+**Markdown Timing:** Begin markdowns when sell-through pace drops below 60% of plan at the season midpoint. Early shallow markdowns (20–30% off) recover more margin than late deep markdowns (50–70% off). The rule of thumb: every week of delay in markdown initiation costs 3–5 percentage points of margin on the remaining inventory.
+
+**Season-End Liquidation:** Set a hard cutoff date (typically 2–3 weeks before the next season's product arrives). Everything remaining at cutoff goes to outlet, liquidator, or donation. Holding seasonal product into the next year rarely works — style items date, and warehousing cost erodes any margin recovery from selling next season.
+
+## Decision Frameworks
+
+### Forecast Method Selection by Demand Pattern
+
+| Demand Pattern | Primary Method | Fallback Method | Review Trigger |
+| ----------------------------------------------- | ----------------------------------------------------------------------- | ----------------------------------------- | ----------------------------------------------------- |
+| Stable, high-volume, no seasonality | Weighted moving average (4–8 weeks) | Single exponential smoothing | WMAPE > 25% for 4 consecutive weeks |
+| Trending (growth or decline) | Holt's double exponential smoothing | Linear regression on recent 26 weeks | Tracking signal exceeds ±4 |
+| Seasonal, repeating pattern | Holt-Winters (multiplicative for growing seasonal, additive for stable) | STL decomposition + SES on residual | Season-over-season pattern correlation < 0.7 |
+| Intermittent / lumpy (>30% zero-demand periods) | Croston's method or SBA (Syntetos-Boylan Approximation) | Bootstrap simulation on demand intervals | Mean inter-demand interval shifts by >30% |
+| Promotion-driven | Causal regression (baseline + promo lift layer) | Analogous item lift + baseline | Post-promo actuals deviate >40% from forecast |
+| New product (0–12 weeks history) | Analogous item profile with lifecycle curve | Category average with decay toward actual | Own-data WMAPE stabilizes below analogous-based WMAPE |
+| Event-driven (weather, local events) | Regression with external regressors | Manual override with documented rationale | |
+
+### Safety Stock Service Level Selection
+
+| Segment | Target Service Level | Z-Score | Rationale |
+| ------------------------------------- | -------------------- | --------- | -------------------------------------------------------------------------------------------- |
+| AX (high-value, predictable) | 97.5% | 1.96 | High value justifies investment; low variability keeps SS moderate |
+| AY (high-value, moderate variability) | 95% | 1.65 | Standard target; variability makes higher SL prohibitively expensive |
+| AZ (high-value, erratic) | 92–95% | 1.41–1.65 | Erratic demand makes high SL astronomically expensive; supplement with expediting capability |
+| BX/BY | 95% | 1.65 | Standard target |
+| BZ | 90% | 1.28 | Accept some stockout risk on mid-tier erratic items |
+| CX/CY | 90–92% | 1.28–1.41 | Low value doesn't justify high SS investment |
+| CZ | 85% | 1.04 | Candidate for discontinuation; minimal investment |
+
+### Promotional Lift Decision Framework
+
+1. **Is there historical lift data for this SKU-promo type combination?** → Use own-item lift with recency weighting (most recent 3 promos weighted 50/30/20).
+2. **No own-item data but same category has been promoted?** → Use analogous item lift adjusted for price point and brand tier.
+3. **Brand-new category or promo type?** → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the promo period.
+4. **Cross-promoted with another category?** → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity coefficient if available; default 0.15 lift for cross-category halo.
+5. **Always model the post-promo dip.** Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.
+
+### Markdown Timing Decision
+
+| Sell-Through at Season Midpoint | Action | Expected Margin Recovery |
+| ------------------------------- | ------------------------------------------------------------------------------------ | ------------------------- |
+| ≥ 80% of plan | Hold price. Reorder cautiously if weeks of supply < 3. | Full margin |
+| 60–79% of plan | Take 20–25% markdown. No reorder. | 70–80% of original margin |
+| 40–59% of plan | Take 30–40% markdown immediately. Cancel any open POs. | 50–65% of original margin |
+| < 40% of plan | Take 50%+ markdown. Explore liquidation channels. Flag buying error for post-mortem. | 30–45% of original margin |
+
+### Slow-Mover Kill Decision
+
+Evaluate quarterly. Flag for discontinuation when ALL of the following are true:
+
+- Weeks of supply > 26 at current sell-through rate
+- Last 13-week sales velocity < 50% of the item's first 13 weeks (lifecycle declining)
+- No promotional activity planned in the next 8 weeks
+- Item is not contractually obligated (planogram commitment, vendor agreement)
+- Replacement or substitution SKU exists or category can absorb the gap
+
+If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escalate to 50% off or liquidation. Set a hard exit date 8 weeks from first markdown. Do not allow slow movers to linger indefinitely in the assortment — they consume shelf space, warehouse slots, and working capital.
+
+## Key Edge Cases
+
+Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md).
+
+1. **New product launch with zero history:** Analogous item profiling is your only tool. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.
+
+2. **Viral social media spike:** Demand jumps 500–2,000% with no warning. Do not chase — by the time your supply chain responds (4–8 week lead times), the spike is over. Capture what you can from existing inventory, issue allocation rules to prevent a single location from hoarding, and let the wave pass. Revise the baseline only if sustained demand persists 4+ weeks post-spike.
+
+3. **Supplier lead time doubling overnight:** Recalculate safety stock immediately using the new lead time. If SS doubles, you likely cannot fill the gap from current inventory. Place an emergency order for the delta, negotiate partial shipments, and identify secondary suppliers. Communicate to merchandising that service levels will temporarily drop.
+
+4. **Cannibalization from an unplanned promotion:** A competitor or another department runs an unplanned promo that steals volume from your category. Your forecast will over-project. Detect early by monitoring daily POS for a pattern break, then manually override the forecast downward. Defer incoming orders if possible.
+
+5. **Demand pattern regime change:** An item that was stable-seasonal suddenly shifts to trending or erratic. Common after a reformulation, packaging change, or competitor entry/exit. The old model will fail silently. Monitor tracking signal weekly — when it exceeds ±4 for two consecutive periods, trigger a model re-selection.
+
+6. **Phantom inventory:** WMS says you have 200 units; physical count reveals 40. Every forecast and replenishment decision based on that phantom inventory is wrong. Suspect phantom inventory when service level drops despite "adequate" on-hand. Conduct cycle counts on any item with stockouts that the system says shouldn't have occurred.
+
+7. **Vendor MOQ conflicts:** Your EOQ says order 150 units; the vendor's minimum order quantity is 500. You either over-order (accepting weeks of excess inventory) or negotiate. Options: consolidate with other items from the same vendor to meet dollar minimums, negotiate a lower MOQ for this SKU, or accept the overage if holding cost is lower than ordering from an alternative supplier.
+
+8. **Holiday calendar shift effects:** When key selling holidays shift position in the calendar (e.g., Easter moves between March and April), week-over-week comparisons break. Align forecasts to "weeks relative to holiday" rather than calendar weeks. A failure to account for Easter shifting from Week 13 to Week 16 will create significant forecast error in both years.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Vendor routine reorder:** Transactional, brief, PO-reference-driven. "PO #XXXX for delivery week of MM/DD per our agreed schedule."
+- **Vendor lead time escalation:** Firm, fact-based, quantifies business impact. "Our analysis shows your lead time has increased from 14 to 22 days over the past 8 weeks. This has resulted in X stockout events. We need a corrective plan by [date]."
+- **Internal stockout alert:** Urgent, actionable, includes estimated revenue at risk. Lead with the customer impact, not the inventory metric. "SKU X will stock out at 12 locations by Thursday. Estimated lost sales: $XX,000. Recommended action: [expedite/reallocate/substitute]."
+- **Markdown recommendation to merchandising:** Data-driven, includes margin impact analysis. Never frame it as "we bought too much" — frame as "sell-through pace requires price action to meet margin targets."
+- **Promotional forecast submission:** Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
+- **New product forecast assumptions:** Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."
+
+Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------------- | ------------------------------------------------------ | -------------------------- |
+| Projected stockout on A-item within 7 days | Alert demand planning manager + category merchant | Within 4 hours |
+| Vendor confirms lead time increase > 25% | Notify supply chain director; recalculate all open POs | Within 1 business day |
+| Promotional forecast miss > 40% (over or under) | Post-promo debrief with merchandising and vendor | Within 1 week of promo end |
+| Excess inventory > 26 weeks of supply on any A/B item | Markdown recommendation to merchandising VP | Within 1 week of detection |
+| Forecast bias exceeds ±10% for 4 consecutive weeks | Model review and re-parameterization | Within 2 weeks |
+| New product sell-through < 40% of plan after 4 weeks | Assortment review with merchandising | Within 1 week |
+| Service level drops below 90% for any category | Root cause analysis and corrective plan | Within 48 hours |
+
+### Escalation Chain
+
+Level 1 (Demand Planner) → Level 2 (Planning Manager, 24 hours) → Level 3 (Director of Supply Chain Planning, 48 hours) → Level 4 (VP Supply Chain, 72+ hours or any A-item stockout at enterprise customer)
+
+## Performance Indicators
+
+Track weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------- | ------------ | ------------------- |
+| WMAPE (weighted mean absolute percentage error) | < 25% | > 35% |
+| Forecast bias | ±5% | > ±10% for 4+ weeks |
+| In-stock rate (A-items) | > 97% | < 94% |
+| In-stock rate (all items) | > 95% | < 92% |
+| Weeks of supply (aggregate) | 4–8 weeks | > 12 or < 3 |
+| Excess inventory (>26 weeks supply) | < 5% of SKUs | > 10% of SKUs |
+| Dead stock (zero sales, 13+ weeks) | < 2% of SKUs | > 5% of SKUs |
+| Purchase order fill rate from vendors | > 95% | < 90% |
+| Promotional forecast accuracy (WMAPE) | < 35% | > 50% |
+
+## Additional Resources
+
+- For detailed decision frameworks, optimization models, and method selection trees, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **forecast demand and shape inventory policy across SKUs, stores, and vendors**:
+
+- Selecting and tuning forecasting methods, safety stock policies, and reorder logic for different demand patterns.
+- Planning promotions, seasonal transitions, markdowns, and end‑of‑life strategies while balancing service, cash, and margin.
+- Investigating chronic stockouts, excess inventory, or forecast bias and redesigning the planning process with clearer decision frameworks.
diff --git a/skills/inventory-demand-planning/references/communication-templates.md b/skills/inventory-demand-planning/references/communication-templates.md
new file mode 100644
index 00000000..eea6c365
--- /dev/null
+++ b/skills/inventory-demand-planning/references/communication-templates.md
@@ -0,0 +1,566 @@
+# Communication Templates — Inventory Demand Planning
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing demand planning communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and purpose. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Vendor Replenishment Order](#1-vendor-replenishment-order)
+2. [Vendor Lead Time Escalation](#2-vendor-lead-time-escalation)
+3. [Internal Stockout Alert](#3-internal-stockout-alert)
+4. [Markdown Recommendation to Merchandising](#4-markdown-recommendation-to-merchandising)
+5. [Promotional Forecast Submission](#5-promotional-forecast-submission)
+6. [Safety Stock Adjustment Request](#6-safety-stock-adjustment-request)
+7. [New Product Forecast Assumptions](#7-new-product-forecast-assumptions)
+8. [Excess Inventory Liquidation Plan](#8-excess-inventory-liquidation-plan)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{po_number}}` | Purchase order number | `PO-2025-08843` |
+| `{{sku}}` | SKU or item number | `SKU-44281` |
+| `{{sku_description}}` | Product description | `Organic Olive Oil 16oz` |
+| `{{vendor_name}}` | Vendor company name | `Mediterranean Imports LLC` |
+| `{{vendor_contact}}` | Vendor contact name | `Marco Bellini` |
+| `{{vendor_contact_email}}` | Vendor contact email | `m.bellini@medimports.com` |
+| `{{our_contact_name}}` | Our planner name | `Sarah Kim` |
+| `{{our_contact_title}}` | Our planner title | `Senior Demand Planner` |
+| `{{our_contact_email}}` | Our planner email | `s.kim@retailco.com` |
+| `{{our_contact_phone}}` | Our planner phone | `(404) 555-0192` |
+| `{{our_company}}` | Our company name | `RetailCo` |
+| `{{dc_location}}` | Distribution center location | `Nashville, TN DC` |
+| `{{delivery_date}}` | Requested delivery date | `2025-09-22` |
+| `{{order_qty}}` | Order quantity | `1,200 units (100 cases)` |
+| `{{current_on_hand}}` | Current on-hand inventory | `840 units` |
+| `{{weeks_of_supply}}` | Weeks of supply at current rate | `4.2 weeks` |
+| `{{weekly_demand}}` | Average weekly demand | `200 units/week` |
+| `{{category}}` | Product category | `Cooking Oils` |
+| `{{store_count}}` | Number of affected stores | `85 stores` |
+| `{{abc_class}}` | ABC classification | `A-item` |
+| `{{service_level_target}}` | Target service level | `97%` |
+| `{{current_service_level}}` | Current service level | `91%` |
+| `{{revenue_at_risk}}` | Estimated revenue at risk | `$18,400/week` |
+| `{{promo_start}}` | Promotion start date | `2025-10-05` |
+| `{{promo_end}}` | Promotion end date | `2025-10-18` |
+| `{{promo_type}}` | Promotion type | `TPR 25% off + circular feature` |
+| `{{baseline_forecast}}` | Baseline forecast | `500 units/week` |
+| `{{lift_estimate}}` | Promotional lift estimate | `180% (900 incremental units)` |
+| `{{markdown_pct}}` | Markdown percentage | `30%` |
+| `{{excess_units}}` | Excess inventory units | `3,200 units` |
+| `{{excess_wos}}` | Excess weeks of supply | `18.4 weeks` |
+
+---
+
+## 1. Vendor Replenishment Order
+
+### When to Use
+- Standard replenishment order based on forecast and inventory position.
+- No urgency beyond normal lead time expectations.
+
+### Tone Guidance
+Transactional and efficient. The vendor receives dozens of these daily. Be clear, reference the PO, specify quantities, delivery date, and delivery location. No need for pleasantries beyond professional courtesy.
+
+### What NOT to Say
+- Do not include forecast data or inventory levels in routine POs — this is proprietary information.
+- Do not request lead time changes or raise performance issues in a PO communication.
+
+### Template
+
+**Subject:** `PO {{po_number}} — {{vendor_name}} — Delivery {{delivery_date}}`
+
+---
+
+{{vendor_contact}},
+
+Please find below our purchase order for delivery to {{dc_location}}.
+
+**PO Number:** {{po_number}}
+**Requested Delivery Date:** {{delivery_date}}
+**Ship-To:** {{dc_location}}
+
+| SKU | Description | Qty (units) | Qty (cases) | Unit Cost | Line Total |
+|---|---|---|---|---|---|
+| {{sku}} | {{sku_description}} | {{order_qty}} | {{cases}} | {{unit_cost}} | {{line_total}} |
+
+**Order Total:** {{order_total}}
+
+Please confirm receipt and expected ship date within 2 business days.
+
+If any items are unavailable or quantities will be shorted, notify us immediately at {{our_contact_email}} so we can adjust our planning.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 2. Vendor Lead Time Escalation
+
+### When to Use
+- Vendor's actual lead times have exceeded the stated/contracted lead time by >20% for 3+ consecutive orders.
+- Lead time variability is causing stockouts or excessive safety stock costs.
+- You need a formal escalation before involving procurement or vendor management.
+
+### Tone Guidance
+Firm and data-driven. You are not complaining — you are presenting evidence and requesting a corrective action plan. Lead with the impact to your business, not the vendor's failure. Offer collaboration: you want to solve this together, but you need a commitment.
+
+### What NOT to Say
+- Do not threaten to switch vendors in this communication (that's a procurement conversation).
+- Do not speculate on the cause of the lead time issue — let the vendor explain.
+- Do not use vague language like "often late" — provide specific PO numbers, dates, and deviations.
+
+### Template
+
+**Subject:** `Lead Time Performance Review — {{vendor_name}} — Action Required by {{deadline_date}}`
+
+---
+
+{{vendor_contact}},
+
+I'm writing to address a consistent lead time issue that is impacting our inventory planning for your product line.
+
+**Summary of the Problem:**
+
+Over the past {{time_period}}, we have observed the following lead time performance on our orders:
+
+| PO Number | Order Date | Stated Lead Time | Actual Lead Time | Deviation |
+|---|---|---|---|---|
+| {{po_1}} | {{date_1}} | {{stated_lt}} days | {{actual_lt_1}} days | +{{dev_1}} days |
+| {{po_2}} | {{date_2}} | {{stated_lt}} days | {{actual_lt_2}} days | +{{dev_2}} days |
+| {{po_3}} | {{date_3}} | {{stated_lt}} days | {{actual_lt_3}} days | +{{dev_3}} days |
+
+**Average stated lead time:** {{stated_lt}} days
+**Average actual lead time:** {{actual_lt_avg}} days (+{{pct_increase}}%)
+**Lead time coefficient of variation:** {{lt_cv}}
+
+**Impact to Our Business:**
+
+This lead time increase has required us to:
+- Increase safety stock by {{ss_increase_pct}}%, tying up an additional ${{ss_cost_increase}} in working capital
+- Experience {{stockout_count}} stockout events on {{sku_description}} in the past {{time_period}}, with estimated lost sales of ${{lost_sales}}
+- Expedite {{expedite_count}} orders at an additional cost of ${{expedite_cost}}
+
+**What We Need:**
+
+1. A written explanation of the root cause of the lead time increase by {{deadline_date}}.
+2. A corrective action plan with a committed timeline to return to the stated {{stated_lt}}-day lead time.
+3. If the lead time increase is permanent, we need an updated lead time commitment so we can recalibrate our planning parameters.
+
+We value our partnership with {{vendor_name}} and want to resolve this collaboratively. I'm available to discuss on a call at your convenience this week.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Internal Stockout Alert
+
+### When to Use
+- Projected stockout on an A or B-item within 7 days based on current inventory position and demand forecast.
+- Actual stockout occurring at 3+ locations.
+- Any stockout where revenue at risk exceeds $10,000/week.
+
+### Tone Guidance
+Urgent, concise, action-oriented. The audience is internal (planning manager, category merchant, supply chain director). Lead with the impact, follow with the facts, close with the recommended action. This is not a post-mortem — it's a call to action.
+
+### What NOT to Say
+- Do not assign blame in the alert (e.g., "because the buyer didn't order enough"). That's for the post-mortem.
+- Do not present multiple options without a recommendation — decision-makers need a clear ask.
+
+### Template
+
+**Subject:** `🔴 STOCKOUT ALERT — {{sku_description}} — {{store_count}} locations at risk`
+
+---
+
+**Attention:** {{recipient_names}}
+
+**Item:** {{sku}} — {{sku_description}}
+**ABC Class:** {{abc_class}}
+**Current Status:** {{current_status}} (e.g., "Out of stock at 8 locations; projected stockout at 22 additional locations by {{stockout_date}}")
+
+**Inventory Position:**
+- DC On-Hand: {{dc_on_hand}} units
+- Store On-Hand (aggregate): {{store_on_hand}} units
+- On-Order: {{on_order}} units (ETA: {{on_order_eta}})
+- Weekly Demand: {{weekly_demand}}
+- Weeks of Supply (current): {{weeks_of_supply}}
+
+**Revenue at Risk:** ${{revenue_at_risk}}/week across {{store_count}} locations
+
+**Root Cause:** {{root_cause}} (e.g., "Vendor shipment delayed by 10 days; demand running 20% above forecast due to competitive market exit")
+
+**Recommended Actions:**
+
+1. **Immediate:** {{action_1}} (e.g., "Reallocate 400 units from low-velocity stores to stockout locations — list attached")
+2. **Short-term:** {{action_2}} (e.g., "Expedite PO {{po_number}} — vendor confirmed can ship 800 units by {{expedite_date}} at ${{expedite_cost}} additional freight")
+3. **If above fails:** {{action_3}} (e.g., "Substitute with {{alt_sku}} — similar product, available in DC, can ship to affected stores within 48 hours")
+
+**Decision needed by:** {{decision_deadline}}
+
+Please reply or call me directly to confirm action.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_phone}}
+
+---
+
+## 4. Markdown Recommendation to Merchandising
+
+### When to Use
+- SKU or category has excess inventory exceeding 12 weeks of supply with no promotional activity planned.
+- Seasonal product with sell-through below 60% at season midpoint.
+- Slow-mover kill decision has been triggered.
+
+### Tone Guidance
+Data-driven and collaborative. You are presenting a financial analysis, not demanding a price change. Merchandising owns pricing decisions — your job is to provide the inventory data and margin impact analysis to inform their decision. Frame recommendations as margin recovery, not "we bought too much."
+
+### What NOT to Say
+- Do not say "we overbought" or "the forecast was wrong" — frame as "sell-through pace requires price action."
+- Do not propose a specific retail price — propose a markdown depth (% off) and let merchandising set the price.
+
+### Template
+
+**Subject:** `Markdown Recommendation — {{sku_description}} — {{excess_units}} units excess`
+
+---
+
+**To:** {{merchandising_contact}}
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+**Summary:**
+{{sku_description}} ({{sku}}) is carrying {{excess_units}} units of excess inventory representing {{excess_wos}} weeks of supply at current sell-through rates. Based on our analysis, a markdown is recommended to recover margin and free working capital before the inventory ages further.
+
+**Current Inventory Position:**
+
+| Metric | Value |
+|---|---|
+| On-Hand (DC + Stores) | {{total_on_hand}} units |
+| Weekly Demand (trailing 4-week avg) | {{weekly_demand}} |
+| Weeks of Supply | {{excess_wos}} |
+| Seasonal Window Remaining | {{season_weeks_remaining}} weeks |
+| Current Sell-Through vs. Plan | {{sell_through_pct}}% |
+
+**Financial Analysis:**
+
+| Scenario | Markdown Depth | Projected Velocity | Weeks to Clear | Margin Recovery |
+|---|---|---|---|---|
+| No action | 0% | {{current_velocity}} units/week | {{wos_no_action}} weeks | {{margin_no_action}} |
+| Option A | {{md_depth_a}}% | {{velocity_a}} units/week | {{wos_a}} weeks | {{margin_a}} |
+| Option B | {{md_depth_b}}% | {{velocity_b}} units/week | {{wos_b}} weeks | {{margin_b}} |
+| Liquidation | Cost recovery | Immediate | 1–2 weeks | {{margin_liquidation}} |
+
+**Recommendation:** Option {{recommended_option}} ({{md_depth_recommended}}% markdown) offers the best margin recovery of {{margin_recommended}} while clearing inventory within {{wos_recommended}} weeks.
+
+**Holding Cost of Inaction:** Carrying this excess for another {{delay_weeks}} weeks costs approximately ${{holding_cost}} in inventory carrying costs and risks additional obsolescence if the product ages or a seasonal window closes.
+
+**Next Steps:**
+If approved, we can execute the markdown effective {{proposed_start_date}} and monitor weekly sell-through against the projected velocity.
+
+Happy to discuss the analysis in detail.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Promotional Forecast Submission
+
+### When to Use
+- Submitting the demand forecast for a planned promotion to supply chain, merchandising, and vendor partners.
+- Required 6–8 weeks before promotion start date to allow for procurement.
+
+### Tone Guidance
+Structured and transparent. This document is the "source of truth" for promotional inventory planning. Include all assumptions, the baseline, the lift estimate, and the post-promo dip so that all stakeholders can challenge or validate the numbers before POs are placed.
+
+### What NOT to Say
+- Do not present a single point estimate without a confidence range — this gives false precision.
+- Do not omit the post-promo dip — it's as important as the lift.
+
+### Template
+
+**Subject:** `Promotional Forecast — {{sku_description}} — {{promo_start}} to {{promo_end}}`
+
+---
+
+**To:** Supply Chain Planning, Category Merchandising, {{vendor_name}} (if applicable)
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+**Promotion:** {{promo_description}}
+
+---
+
+### Promotion Details
+
+| Field | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Promotion Period | {{promo_start}} — {{promo_end}} ({{promo_weeks}} weeks) |
+| Promotion Type | {{promo_type}} |
+| Promotional Retail Price | ${{promo_price}} (regular: ${{reg_price}}, {{discount_pct}}% off) |
+| Media Support | {{media_support}} (e.g., "Circular page 3 + endcap display") |
+| Stores Participating | {{store_count}} of {{total_stores}} |
+
+### Forecast
+
+| Period | Baseline Forecast | Lift Estimate | Total Forecast | Confidence Range (±) |
+|---|---|---|---|---|
+| Pre-promo (week before) | {{baseline}} units | — | {{baseline}} units | — |
+| Promo Week 1 | {{baseline}} | +{{lift_wk1}}% ({{lift_units_1}} units) | {{total_wk1}} units | ±{{conf_1}}% |
+| Promo Week 2 | {{baseline}} | +{{lift_wk2}}% ({{lift_units_2}} units) | {{total_wk2}} units | ±{{conf_2}}% |
+| Post-Promo Week 1 | {{baseline}} | −{{dip_wk1}}% ({{dip_units_1}} units) | {{post_1}} units | ±{{conf_post_1}}% |
+| Post-Promo Week 2 | {{baseline}} | −{{dip_wk2}}% ({{dip_units_2}} units) | {{post_2}} units | ±{{conf_post_2}}% |
+| Recovery (Week 3+) | {{baseline}} | — | {{baseline}} units | — |
+
+**Total Promotional Period Demand:** {{total_promo_demand}} units
+**Total Incremental Demand (above baseline):** {{incremental_demand}} units
+
+### Assumptions and Methodology
+
+1. **Baseline:** {{baseline_method}} (e.g., "Holt-Winters model fitted on de-promoted trailing 52-week data")
+2. **Lift source:** {{lift_source}} (e.g., "Average of 3 most recent comparable promotions on this SKU, weighted 50/30/20 by recency")
+3. **Cannibalization:** Estimated {{cannibalization_pct}}% cannibalization from {{cannibalized_sku}}, reducing net category lift to {{net_category_lift}}%
+4. **Post-promo dip:** Based on {{dip_source}} (e.g., "Product type: shelf-stable pantry; historical dip factor 45% of incremental lift")
+5. **Confidence range:** Based on historical promotional forecast accuracy for this category (trailing 12-month promo WMAPE: {{promo_wmape}}%)
+
+### Inventory Requirements
+
+| Item | Quantity |
+|---|---|
+| Current on-hand (DC + pipeline) | {{current_inventory}} units |
+| Total demand through post-promo recovery | {{total_demand}} units |
+| Gap to fill | {{gap_units}} units |
+| Recommended PO quantity | {{po_qty}} units ({{cases}} cases) |
+| PO must arrive by | {{po_arrive_by}} ({{lead_time_buffer}} days before promo start) |
+
+### Risks
+
+- **Upside risk:** If lift exceeds {{upside_lift}}%, we may stock out in week 2 of the promotion. Contingency: {{contingency_up}}.
+- **Downside risk:** If lift is below {{downside_lift}}%, we will carry {{excess_if_low}} excess units post-promo, requiring {{excess_weeks}} additional weeks to sell through.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 6. Safety Stock Adjustment Request
+
+### When to Use
+- Demand variability or lead time variability has changed, requiring a safety stock parameter update.
+- Service level targets have been revised (up or down) for a segment or individual SKU.
+- Post a supply disruption or regime change that permanently alters risk parameters.
+
+### Tone Guidance
+Analytical and justified. Every safety stock change is an inventory investment change. Present the before/after calculation, the reason for the change, and the financial impact (incremental holding cost or reduced stockout risk).
+
+### Template
+
+**Subject:** `Safety Stock Adjustment — {{sku_description}} — {{adjustment_direction}} by {{adjustment_pct}}%`
+
+---
+
+**To:** {{planning_manager}}, {{finance_contact}} (if material)
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+**Item:** {{sku}} — {{sku_description}} ({{abc_class}})
+
+### Reason for Adjustment
+
+{{reason}} (e.g., "Vendor lead time has increased from 14 days to 28 days effective 2025-09-01. Lead time variability has also increased, with CV rising from 0.12 to 0.31.")
+
+### Calculation
+
+| Parameter | Previous | Updated | Change |
+|---|---|---|---|
+| Average weekly demand | {{prev_demand}} units | {{new_demand}} units | {{demand_change}} |
+| Demand std. deviation (σ_d) | {{prev_sigma_d}} units | {{new_sigma_d}} units | {{sigma_d_change}} |
+| Lead time (weeks) | {{prev_lt}} weeks | {{new_lt}} weeks | {{lt_change}} |
+| Lead time std. deviation (σ_LT) | {{prev_sigma_lt}} weeks | {{new_sigma_lt}} weeks | {{sigma_lt_change}} |
+| Service level target | {{service_level}} | {{service_level}} | No change |
+| Z-score | {{z_score}} | {{z_score}} | No change |
+| **Safety stock (units)** | **{{prev_ss}}** | **{{new_ss}}** | **+{{ss_delta}} units** |
+
+### Financial Impact
+
+- Incremental inventory investment: {{ss_delta}} units × ${{unit_cost}} = ${{incremental_investment}}
+- Annual holding cost increase: ${{incremental_investment}} × {{holding_cost_pct}}% = ${{annual_holding_increase}}
+- Expected stockout reduction: from {{prev_stockout_events}} events/year to {{new_stockout_events}} events/year
+- Estimated recovered revenue: ${{recovered_revenue}}/year
+
+**Net impact:** {{net_assessment}} (e.g., "The $2,400 annual holding cost increase is justified by the $18,000 in projected recovered revenue from reduced stockouts.")
+
+### Approval Requested By
+
+{{deadline}} — needed before the next replenishment cycle to take effect.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 7. New Product Forecast Assumptions
+
+### When to Use
+- Documenting the forecast basis for a new product launch with < 8 weeks of own-history data.
+- Required at the pre-launch planning meeting and updated at the 4-week and 8-week checkpoints.
+
+### Tone Guidance
+Transparent and falsifiable. The purpose of this document is to make every assumption explicit so that the post-mortem can identify where the forecast diverged from reality. Do not hedge with vague language — state the assumptions clearly so they can be validated or disproved.
+
+### Template
+
+**Subject:** `New Product Forecast Assumptions — {{sku_description}} — Launch {{launch_date}}`
+
+---
+
+**To:** Category Merchandising, Supply Chain Planning, Finance
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+### Product Details
+
+| Field | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Category | {{category}} / {{subcategory}} |
+| Retail Price | ${{retail_price}} |
+| Unit Cost | ${{unit_cost}} |
+| Gross Margin | {{gross_margin_pct}}% |
+| Launch Date | {{launch_date}} |
+| Initial Distribution | {{store_count}} stores ({{pct_of_chain}}% of chain) |
+| Vendor | {{vendor_name}} |
+| Lead Time | {{lead_time}} weeks |
+| Shelf Life | {{shelf_life}} |
+
+### Analogous Items Selected
+
+| Analog SKU | Description | Similarity Score | Launch Velocity (wks 1–13) | Current Velocity |
+|---|---|---|---|---|
+| {{analog_1_sku}} | {{analog_1_desc}} | {{analog_1_score}}/5.0 | {{analog_1_launch_vel}} units/store/week | {{analog_1_current_vel}} |
+| {{analog_2_sku}} | {{analog_2_desc}} | {{analog_2_score}}/5.0 | {{analog_2_launch_vel}} units/store/week | {{analog_2_current_vel}} |
+| {{analog_3_sku}} | {{analog_3_desc}} | {{analog_3_score}}/5.0 | {{analog_3_launch_vel}} units/store/week | {{analog_3_current_vel}} |
+
+**Weighted average analog velocity (weeks 1–13):** {{weighted_avg_vel}} units/store/week
+
+### Forecast by Phase
+
+| Phase | Weeks | Velocity (units/store/wk) | Total Weekly Demand ({{store_count}} stores) | Confidence Band |
+|---|---|---|---|---|
+| Introduction | 1–4 | {{intro_vel}} | {{intro_weekly}} units | ±{{intro_conf}}% |
+| Growth | 5–8 | {{growth_vel}} | {{growth_weekly}} units | ±{{growth_conf}}% |
+| Stabilization | 9–13 | {{stable_vel}} | {{stable_weekly}} units | ±{{stable_conf}}% |
+
+### Key Assumptions
+
+1. {{assumption_1}} (e.g., "Product will receive endcap display in all {{store_count}} stores for weeks 1–4")
+2. {{assumption_2}} (e.g., "No direct competitor launch in the same subcategory during the launch window")
+3. {{assumption_3}} (e.g., "Price point is within the category's high-volume range ($3–$5)")
+4. {{assumption_4}} (e.g., "Vendor will maintain {{lead_time}}-week lead time for reorders")
+
+### Initial Buy and Reorder Plan
+
+| Component | Quantity | Timing |
+|---|---|---|
+| Initial buy | {{initial_buy}} units | PO placed {{initial_po_date}} |
+| Safety stock | {{initial_ss}} units (analog-based, 30% uncertainty premium) | Included in initial buy |
+| First reorder trigger | If week 1–2 velocity > {{reorder_trigger}} units/store/week | Auto-trigger PO |
+| Reserve for reorder | {{reserve_units}} units (held at vendor or allocated in budget) | Weeks 3–5 |
+
+### Monitoring Plan
+
+| Checkpoint | Date | Metric | Action if Below Plan | Action if Above Plan |
+|---|---|---|---|---|
+| Week 2 | {{wk2_date}} | Velocity vs. {{intro_vel}} target | Review display compliance; consider early promo | Place reorder for 50% of reserve |
+| Week 4 | {{wk4_date}} | Sell-through vs. initial buy | Flag for promotional support | Place reorder for remaining reserve |
+| Week 8 | {{wk8_date}} | Velocity trend (growing/declining/stable) | Initiate slow-mover review if declining for 4 wks | Upgrade to standard forecasting method |
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 8. Excess Inventory Liquidation Plan
+
+### When to Use
+- SKU has been classified as dead stock (zero sales for 13+ weeks) or critical excess (>26 weeks of supply).
+- Seasonal product with unsold inventory after the markdown selling window.
+- Discontinued product with remaining inventory after final markdown.
+
+### Tone Guidance
+Pragmatic and action-oriented. The liquidation plan is an acknowledgment that margin recovery is limited and the priority has shifted to cash recovery and warehouse space liberation. Present the options dispassionately — the goal is to make the best of a bad situation, not to relitigate the buying decision.
+
+### Template
+
+**Subject:** `Excess Inventory Liquidation Plan — {{sku_description}} — {{excess_units}} units`
+
+---
+
+**To:** {{merchandising_contact}}, {{finance_contact}}, {{warehouse_contact}}
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+### Inventory Summary
+
+| Metric | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Current On-Hand | {{excess_units}} units |
+| Original Cost | ${{unit_cost}} per unit (${{total_cost}} total) |
+| Current Retail | ${{current_retail}} (after markdowns) |
+| Weekly Demand (trailing 8 weeks) | {{weekly_demand}} units |
+| Weeks of Supply | {{excess_wos}} |
+| Reason for Excess | {{reason}} |
+
+### Liquidation Options Analysis
+
+| Option | Recovery per Unit | Total Recovery | Timeline | Pros | Cons |
+|---|---|---|---|---|---|
+| **A: Deeper markdown ({{md_depth}}% off)** | ${{recovery_a}} | ${{total_a}} | {{timeline_a}} weeks | Retains customer; recovers shelf space gradually | Margin erosion; may not clear |
+| **B: Liquidation channel** | ${{recovery_b}} | ${{total_b}} | {{timeline_b}} weeks | Immediate clearance; frees space | Very low recovery; no brand control |
+| **C: Donation (tax write-off)** | ${{recovery_c}} (tax benefit) | ${{total_c}} | {{timeline_c}} weeks | Goodwill; tax benefit; immediate space recovery | No cash recovery |
+| **D: Destroy / write-off** | $0 | $0 | Immediate | Frees space immediately; clean books | Total loss; disposal cost of ${{disposal_cost}} |
+
+### Recommendation
+
+Option {{recommended_option}} is recommended based on the following rationale:
+
+{{recommendation_rationale}} (e.g., "Option B (liquidation) recovers $3,200 compared to Option A's $4,100 — but Option A requires 8 more weeks of shelf space that has a higher-value alternative use. The opportunity cost of holding the shelf space exceeds the $900 margin difference.")
+
+### Execution Plan
+
+| Step | Action | Owner | Deadline |
+|---|---|---|---|
+| 1 | Approve liquidation plan | {{approver}} | {{approval_date}} |
+| 2 | Remove from active replenishment | Demand Planning | {{replenishment_stop_date}} |
+| 3 | {{action_3}} | {{owner_3}} | {{date_3}} |
+| 4 | {{action_4}} | {{owner_4}} | {{date_4}} |
+| 5 | Confirm zero on-hand; close SKU in system | Warehouse / IT | {{close_date}} |
+
+### Financial Summary
+
+| Line Item | Amount |
+|---|---|
+| Original inventory investment | ${{total_cost}} |
+| Revenue recovered (to date, markdowns) | ${{markdown_revenue}} |
+| Projected recovery (this plan) | ${{projected_recovery}} |
+| **Total write-down** | **${{total_writedown}}** |
+
+### Post-Mortem Assignment
+
+Root cause analysis for this excess is assigned to {{postmortem_owner}} with a due date of {{postmortem_date}}. The analysis should address: Was this a forecast error, a buying decision error, a market change, or a timing issue? What process change would prevent recurrence?
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}} | {{our_contact_phone}}
diff --git a/skills/inventory-demand-planning/references/decision-frameworks.md b/skills/inventory-demand-planning/references/decision-frameworks.md
new file mode 100644
index 00000000..7d7827cd
--- /dev/null
+++ b/skills/inventory-demand-planning/references/decision-frameworks.md
@@ -0,0 +1,861 @@
+# Decision Frameworks — Inventory Demand Planning
+
+This reference provides the detailed decision logic, optimization models, method selection
+trees, and segmentation methodologies for inventory demand planning at multi-location
+retailers. It is loaded on demand when the agent needs to make or recommend nuanced
+planning decisions.
+
+All thresholds, formulas, and cost assumptions reflect US multi-location retail operations
+managing hundreds of SKUs across grocery, general merchandise, seasonal, and promotional
+categories.
+
+---
+
+## 1. Forecast Method Selection Trees
+
+### 1.1 Primary Selection Algorithm
+
+The goal is to match each SKU to the forecasting method that minimizes WMAPE on out-of-time
+holdout data. In practice, most organizations cannot afford per-SKU model optimization
+across hundreds of items. Instead, classify items into demand pattern archetypes and assign
+methods by archetype.
+
+#### Step 1 — Classify the Demand Pattern
+
+Compute the following statistics on the most recent 52 weeks of de-promoted demand data
+(remove promotional lift periods before computing):
+
+| Statistic | Formula | Purpose |
+|---|---|---|
+| **Coefficient of Variation (CV)** | σ_demand / μ_demand | Measures demand variability |
+| **Average Demand Interval (ADI)** | Total periods / Number of non-zero demand periods | Measures intermittency |
+| **Trend Strength** | R² of linear regression on 26-week trailing demand | Measures directional movement |
+| **Seasonal Strength** | Autocorrelation at lag 52 (weekly) or lag 12 (monthly) | Measures repeating seasonal pattern |
+| **Zero-Demand Ratio** | Count of zero-demand periods / Total periods | Measures how often demand is absent |
+
+#### Step 2 — Map to Demand Archetype
+
+| Archetype | CV | ADI | Trend R² | Seasonal AC | Zero Ratio | Example |
+|---|---|---|---|---|---|---|
+| **Smooth** | < 0.5 | 1.0–1.1 | < 0.3 | < 0.3 | < 5% | Milk, bread, paper towels |
+| **Trending** | < 0.7 | 1.0–1.2 | ≥ 0.3 | < 0.3 | < 10% | Growing brand, declining legacy item |
+| **Seasonal** | 0.3–1.0 | 1.0–1.3 | any | ≥ 0.3 | < 15% | Sunscreen, holiday decor, grills |
+| **Trending-Seasonal** | 0.4–1.2 | 1.0–1.3 | ≥ 0.3 | ≥ 0.3 | < 15% | Growing seasonal category |
+| **Erratic** | ≥ 0.7 | 1.0–1.5 | < 0.3 | < 0.3 | < 30% | Fashion accessories, novelty items |
+| **Intermittent** | any | ≥ 1.5 | any | any | ≥ 30% | Spare parts, specialty ingredients |
+| **Lumpy** | ≥ 1.0 | ≥ 1.5 | any | any | ≥ 30% | Bulk wholesale items with sporadic orders |
+
+#### Step 3 — Assign Forecasting Method
+
+| Archetype | Primary Method | Parameters | Fallback |
+|---|---|---|---|
+| **Smooth** | Weighted moving average (4–8 week window, recent-weighted) | Weights: 0.4/0.3/0.2/0.1 for 4-week | Single exponential smoothing (α = 0.15–0.25) |
+| **Trending** | Holt's double exponential smoothing | α = 0.2–0.4, β = 0.05–0.15 | Linear regression on trailing 26 weeks |
+| **Seasonal** | Holt-Winters (additive if stable amplitude, multiplicative if growing amplitude) | α = 0.1–0.3, β = 0.01–0.05, γ = 0.1–0.3, period = 52 weeks | STL decomposition + SES on residual |
+| **Trending-Seasonal** | Holt-Winters (multiplicative) | α = 0.2–0.4, β = 0.05–0.15, γ = 0.15–0.3 | X-13ARIMA-SEATS |
+| **Erratic** | Damped trend exponential smoothing | α = 0.2–0.4, β = 0.05, φ = 0.8–0.95 | Ensemble of 3 methods (median) |
+| **Intermittent** | Croston's method or SBA | α_demand = 0.1–0.2, α_interval = 0.1–0.2 | Bootstrap simulation (1000 draws) |
+| **Lumpy** | SBA (Syntetos-Boylan Approximation) | Same as Croston's with bias correction | Aggregated to monthly then disaggregated |
+
+### 1.2 Model Switching Rules
+
+Do not switch methods based on a single bad week. Models need time to prove or disprove themselves.
+
+| Condition | Action | Minimum Observation Period |
+|---|---|---|
+| WMAPE improves > 10% on holdout vs. current method | Switch to candidate method | 8-week parallel test |
+| Tracking signal exceeds ±4 for 2 consecutive periods | Trigger model review; re-estimate parameters first | 2 periods (weeks) |
+| Tracking signal exceeds ±6 for 1 period | Immediate model review; likely archetype change | 1 period |
+| Demand pattern archetype changes (e.g., smooth → trending) | Re-run selection algorithm from Step 1 | Quarterly archetype reassessment |
+| New product transitions from analog-based to own-history | Switch when 12+ weeks of own data available and own-data WMAPE < analog-based | 12 weeks |
+| Post-promotion baseline contamination detected | Refit baseline model excluding promo periods | Immediate |
+
+### 1.3 Parameter Optimization Protocol
+
+For exponential smoothing methods, optimize parameters using grid search on time-series
+cross-validation (rolling origin, 1-step ahead forecast, 26+ origins).
+
+**Grid search ranges:**
+
+| Parameter | Range | Step Size | Constraint |
+|---|---|---|---|
+| α (level) | 0.05–0.50 | 0.05 | — |
+| β (trend) | 0.01–0.20 | 0.01 | β ≤ α |
+| γ (seasonal) | 0.05–0.40 | 0.05 | — |
+| φ (damping) | 0.80–0.98 | 0.02 | Only for damped methods |
+
+**Optimization metric:** Minimize WMAPE on the holdout origins. If two parameter sets
+produce WMAPE within 1 percentage point, prefer the set with lower α (more smoothing)
+for stability.
+
+**Overfitting guard:** If the optimized model produces WMAPE on the holdout that is
+>5 percentage points better than on the fitting data, the model is likely overfit.
+Increase smoothing (lower α) until the gap narrows to <3 points.
+
+---
+
+## 2. Safety Stock Optimization Models
+
+### 2.1 Standard Safety Stock (Normal Demand, Fixed Lead Time)
+
+When demand follows a roughly normal distribution and lead time is consistent:
+
+```
+SS = Z × σ_d × √(LT)
+```
+
+Where:
+- Z = z-score for the target service level (see lookup table below)
+- σ_d = standard deviation of demand per period (use same period as LT)
+- LT = lead time in periods
+
+**Z-Score Lookup:**
+
+| Service Level | Z-Score | Typical Application |
+|---|---|---|
+| 85.0% | 1.04 | CZ items — minimal investment |
+| 90.0% | 1.28 | C-items, non-critical B-items |
+| 92.0% | 1.41 | Mid-range safety net |
+| 95.0% | 1.65 | Standard target for A/B items |
+| 97.5% | 1.96 | AX items — high value, predictable |
+| 99.0% | 2.33 | Critical items — stockout cost vastly exceeds holding |
+| 99.5% | 2.58 | Life-safety or contractual obligation items |
+| 99.9% | 3.09 | Rarely justified — extreme holding cost |
+
+### 2.2 Safety Stock with Lead Time Variability
+
+When vendor lead times are uncertain (CV of lead time > 0.15):
+
+```
+SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)
+```
+
+Where:
+- LT_avg = average lead time in periods
+- σ_LT = standard deviation of lead time in periods
+- d_avg = average demand per period
+
+**Practical note:** Many planners underestimate lead time variability because they
+measure "vendor ship date to DC receipt" without accounting for receiving delays,
+quality holds, or weekend/holiday dead time. Measure lead time from PO release to
+"available to sell" — this is the operationally relevant metric.
+
+### 2.3 Safety Stock with Review Period
+
+For periodic review systems (review every R periods):
+
+```
+SS = Z × σ_d × √(LT + R)
+```
+
+The review period adds exposure time — between reviews, you cannot react to demand
+changes. Weekly review (R=1) on a 2-week lead time item needs safety stock for √3 weeks.
+Monthly review (R=4) on the same item needs safety stock for √6 weeks — 41% more.
+
+### 2.4 Safety Stock for Intermittent Demand
+
+Normal-distribution formulas fail when demand has many zero periods. Use empirical
+(bootstrapped) safety stock instead:
+
+1. Collect the last 52 periods of demand data (include zeros).
+2. Generate 10,000 bootstrap samples of length (LT + R) by random sampling with
+ replacement from the historical demand.
+3. Compute the sum of each bootstrap sample (= simulated demand during lead time + review).
+4. The safety stock is the (service level)th percentile of the simulated demand totals
+ minus the mean simulated demand total.
+
+**Example:** For 95% service level, safety stock = P95 of bootstrap demand — mean of
+bootstrap demand. This captures the skewed, zero-inflated distribution that parametric
+formulas miss.
+
+### 2.5 Safety Stock for New Products (No History)
+
+When an item has < 8 weeks of own demand history:
+
+1. Identify 3–5 analogous items matching on: category, price point (±20%), brand tier
+ (national/private label), pack size, and target demographic.
+2. Compute the average σ_d and CV across the analogs.
+3. Apply a "new product uncertainty premium" of 1.25× to the analog σ_d.
+4. Use the standard formula with the inflated σ_d: `SS = Z × (1.25 × σ_d_analog) × √(LT + R)`.
+5. Every 2 weeks, blend own-history σ_d with the analog σ_d. By week 8, use 70% own history
+ and 30% analog. By week 12, use 100% own history.
+
+### 2.6 Safety Stock Cost-Optimization
+
+The naive approach is to set a service level target and compute SS. The sophisticated
+approach is to optimize the tradeoff between holding cost and stockout cost:
+
+```
+Optimal SL = 1 − (H / (H + S × D/Q))
+```
+
+Where:
+- H = holding cost per unit per period
+- S = stockout cost per unit (lost margin + customer goodwill + substitution cost)
+- D = demand per period
+- Q = order quantity
+
+For most retailers, stockout cost on A-items is 3–5× the unit margin (including lost
+customer visits and substitution effects), which pushes optimal SL to 96–98%.
+For C-items, stockout cost is approximately equal to the unit margin, yielding optimal
+SL of 88–92%.
+
+---
+
+## 3. Promotional Planning Frameworks
+
+### 3.1 Promotional Lift Estimation Methodology
+
+Promotional lift is always computed relative to the baseline forecast (the forecast that
+would have been generated without the promotion). Contaminating the baseline with
+promotional history is the #1 source of systematic forecast error in retail.
+
+#### Step 1 — Establish Clean Baseline
+
+Strip promotional periods from the demand history before fitting the baseline model.
+Flag weeks as "promotional" if any of the following were active:
+- Temporary price reduction (TPR) > 5% off regular price
+- Feature in circular, digital ad, or endcap display
+- BOGO or multi-buy offer
+- Cross-promotion in another category
+
+After stripping, interpolate the gaps using the forecast model fitted to non-promotional
+periods. This creates a "what would have sold at regular price" baseline.
+
+#### Step 2 — Compute Historical Lifts
+
+For each historical promotional event on this SKU:
+
+```
+Lift Ratio = Actual Promo-Period Sales / Baseline Forecast for Promo Period
+```
+
+A lift ratio of 2.5 means the promotion drove 2.5× baseline volume (150% incremental).
+
+Organize lift ratios by promotional mechanism:
+
+| Mechanism | Typical Lift Range | Key Drivers |
+|---|---|---|
+| TPR only (5–15% off) | 1.15–1.40 | Depth of discount, category elasticity |
+| TPR (15–30% off) | 1.40–2.00 | Deeper discount creates sharper response |
+| TPR + display | 1.80–2.50 | Display location (endcap > wing > inline) |
+| TPR + circular feature | 2.00–3.00 | Circular reach and placement (front page > interior) |
+| TPR + display + circular | 2.50–4.00 | Full support — this is the "A-level" promo |
+| BOGO | 2.50–5.00 | Perceived value drives high response but heavy forward-buy |
+| Doorbuster / loss leader | 3.00–6.00+ | Traffic driver; lift varies wildly by event |
+
+#### Step 3 — Apply Lift to Current Forecast
+
+```
+Promo Forecast = Baseline Forecast × Lift Ratio
+```
+
+When multiple promotional mechanisms are combined, do NOT multiply individual lifts.
+Use the combined-mechanism lift from historical data or the table above. The interaction
+effects are sub-additive (display alone = 1.5× and circular alone = 1.8× does not mean
+display + circular = 2.7×; it's typically 2.0–2.5×).
+
+#### Step 4 — Model the Post-Promotion Dip
+
+```
+Post-Promo Demand = Baseline × (1 − Dip Factor × Decay)
+```
+
+Default dip factors by product type:
+
+| Product Type | Dip Factor (% of incremental lift) | Dip Duration | Decay Pattern |
+|---|---|---|---|
+| **Shelf-stable pantry** | 40–60% | 2–4 weeks | 60/30/10 (Week 1/2/3) |
+| **Perishable / refrigerated** | 10–20% | 0–1 week | Immediate recovery |
+| **Household consumables** | 30–50% | 2–3 weeks | 50/35/15 |
+| **Personal care** | 25–40% | 2–3 weeks | 50/30/20 |
+| **Seasonal** | 15–30% | 1–2 weeks | 70/30 |
+| **Discretionary / general merch** | 10–25% | 1–2 weeks | 70/30 |
+
+### 3.2 Cannibalization Estimation
+
+When SKU A is promoted, substitutable SKU B loses sales. The cannibalization rate is:
+
+```
+Cannibalization Rate = ΔB_down / ΔA_up
+```
+
+Where ΔA_up is the incremental lift on A and ΔB_down is the volume loss on B during
+the same period.
+
+**Default estimates when no cross-elasticity data exists:**
+
+| Substitutability | Cannibalization Rate | Example |
+|---|---|---|
+| Direct substitute (same brand, different size) | 25–40% | 12-oz promoted, 16-oz loses |
+| Close substitute (different brand, same segment) | 15–25% | National brand promoted, private label loses |
+| Moderate substitute (same category, different segment) | 5–15% | Premium promoted, value tier affected |
+| Weak substitute (adjacent category) | 0–5% | Chips promoted, crackers slightly affected |
+
+**Important:** Cannibalization is bidirectional across the category. When building the
+category-level promotional plan, sum the cannibalization effects across all substitutes
+to compute the true category-level lift (which is always less than the item-level lift).
+
+### 3.3 Forward-Buy and Pantry Loading
+
+Deep promotions cause customers to purchase ahead of their consumption schedule.
+Forward-buy volume is demand pulled from future periods, not incremental category demand.
+
+**Forward-buy estimation:**
+
+```
+Forward-Buy Volume = Incremental Lift × Forward-Buy Factor
+```
+
+| Promotional Depth | Product Shelf Life | Forward-Buy Factor |
+|---|---|---|
+| 10–20% off | < 2 weeks (perishable) | 0.05–0.10 |
+| 10–20% off | 2–12 weeks | 0.10–0.20 |
+| 10–20% off | > 12 weeks (shelf-stable) | 0.20–0.35 |
+| 20–35% off | < 2 weeks | 0.05–0.15 |
+| 20–35% off | 2–12 weeks | 0.20–0.35 |
+| 20–35% off | > 12 weeks | 0.35–0.50 |
+| 35–50% off | < 2 weeks | 0.10–0.20 |
+| 35–50% off | 2–12 weeks | 0.30–0.45 |
+| 35–50% off | > 12 weeks | 0.50–0.70 |
+| BOGO / > 50% | Any | 0.50–0.80 |
+
+The forward-buy factor tells you what fraction of the incremental lift came from
+pantry loading rather than true consumption increase. This directly feeds the
+post-promo dip calculation — the dip is approximately equal to the forward-buy volume
+spread over its consumption period.
+
+### 3.4 Promotional Calendar Planning
+
+When planning the annual promotional calendar, apply these rules:
+
+1. **Minimum inter-promotion gap:** 4 weeks between promotions on the same SKU. Shorter
+ gaps train customers to only buy on deal, eroding brand equity and baseline velocity.
+2. **Maximum promotional frequency:** 13 weeks per year (25%) for any single SKU.
+ Beyond this, the "promotional price" becomes the reference price in consumers' minds.
+3. **Seasonal alignment:** Promote seasonal items during the build phase (first 40% of
+ the season), not during peak or decline. Promoting at peak wastes money on demand
+ that would have occurred anyway. Promoting during decline is a markdown, not a promotion.
+4. **Cross-category coordination:** Avoid promoting close substitutes simultaneously.
+ Stagger promotions across substitutes by at least 2 weeks to avoid self-cannibalization.
+5. **Vendor funding alignment:** Match promotional timing to vendor trade fund availability.
+ Many CPG manufacturers operate on calendar quarters — funds not committed by quarter-end
+ expire. Plan key promos in weeks 8–12 of each quarter when vendors are motivated to
+ spend remaining funds.
+
+---
+
+## 4. ABC/XYZ Segmentation Methodology
+
+### 4.1 ABC Classification (Value)
+
+ABC classification segments SKUs by their financial contribution. The classification
+drives differentiated investment in forecasting effort, safety stock, review frequency,
+and management attention.
+
+#### Classification Procedure
+
+1. **Select the value metric.** Options in order of preference:
+ - Gross margin contribution (best — focuses investment on profit, not revenue)
+ - Revenue (acceptable when margin data is unavailable)
+ - Unit volume (use only for warehouse space planning, not financial investment)
+
+2. **Compute trailing 52-week value** for each active SKU.
+
+3. **Sort descending** by the value metric.
+
+4. **Compute cumulative % of total value** and classify:
+
+| Class | Cumulative % of Value | Typical % of SKUs | Description |
+|---|---|---|---|
+| A | 0–80% | 10–20% | High-value items driving the business |
+| B | 80–95% | 20–30% | Mid-value items providing assortment breadth |
+| C | 95–100% | 50–70% | Long-tail items with minimal individual impact |
+
+5. **Exception overrides:**
+ - New items (< 13 weeks) are auto-classified one tier higher than their data suggests
+ until they have sufficient history. A new item computing as C is treated as B.
+ - Items with contractual obligations (planogram commitment, vendor agreement) are
+ classified minimum B regardless of current sales velocity.
+ - Items flagged as strategic by merchandising (e.g., traffic drivers, competitive
+ price match items) are classified minimum A.
+
+#### Reclassification Schedule
+
+Run ABC reclassification quarterly. Between quarters, items are reclassified only
+if they cross a threshold by >50% (e.g., an item must contribute >120% of the A/B
+boundary to move from B to A mid-quarter). This prevents oscillation at class boundaries.
+
+### 4.2 XYZ Classification (Predictability)
+
+XYZ classification segments SKUs by demand forecast difficulty. It drives differentiated
+forecasting method selection and safety stock strategies.
+
+#### Classification Procedure
+
+1. **Compute de-seasonalized, de-promoted demand** for each SKU over the trailing 52 weeks.
+ Remove seasonal indices and promotional lift periods so that the variability metric
+ reflects genuine demand uncertainty, not planned variation.
+
+2. **Compute the coefficient of variation (CV):**
+ ```
+ CV = σ_demand / μ_demand
+ ```
+ Use the de-seasonalized, de-promoted demand series.
+
+3. **Classify:**
+
+| Class | CV Range | Description | Forecast Difficulty |
+|---|---|---|---|
+| X | < 0.5 | Highly predictable — demand varies little around its mean | Low — simple methods work well |
+| Y | 0.5–1.0 | Moderately predictable — noticeable variability | Medium — requires good models and monitoring |
+| Z | > 1.0 | Erratic/lumpy — demand is highly variable or intermittent | High — no model will be highly accurate |
+
+4. **Supplement with ADI (Average Demand Interval):** Items with ADI > 2.0 (meaning
+ demand occurs less than every other period) should be classified Z regardless of CV,
+ because the intermittency itself creates forecast difficulty that CV alone doesn't capture.
+
+### 4.3 Combined ABC/XYZ Policy Matrix
+
+| Segment | Forecast Method | Safety Stock | Review Frequency | Replenishment | Management Attention |
+|---|---|---|---|---|---|
+| **AX** | Exponential smoothing (automated) | Z = 1.96 (97.5%) | Weekly | Automated with exception alerts | Monthly review |
+| **AY** | Holt-Winters or causal model | Z = 1.65 (95%) | Weekly | Automated with planner review | Bi-weekly review |
+| **AZ** | Ensemble or manual override | Z = 1.41–1.65 (92–95%) | Weekly | Planner-managed; never fully automated | Weekly review |
+| **BX** | Moving average (automated) | Z = 1.65 (95%) | Bi-weekly | Automated | Monthly review |
+| **BY** | Exponential smoothing (automated) | Z = 1.65 (95%) | Bi-weekly | Automated with exception alerts | Monthly review |
+| **BZ** | Croston's or damped trend | Z = 1.28 (90%) | Bi-weekly | Semi-automated with planner approval | Monthly review |
+| **CX** | Simple moving average | Z = 1.28 (90%) | Monthly | Automated | Quarterly review |
+| **CY** | Simple moving average | Z = 1.28 (90%) | Monthly | Automated | Quarterly review |
+| **CZ** | Croston's or none | Z = 1.04 (85%) | Monthly | Manual or min/max | Quarterly — discontinuation candidate |
+
+### 4.4 Migration Tracking
+
+Track SKU movement between segments quarterly. Key migration patterns to monitor:
+
+| Migration | Signal | Action |
+|---|---|---|
+| A → B | Revenue or margin declining | Investigate: is this category shrinkage, competitive loss, or assortment issue? |
+| B → A | Revenue or margin growing | Upgrade forecasting method and review frequency. Validate safety stock. |
+| X → Y or Z | Demand becoming less predictable | Check for demand pattern regime change. Review forecast model fit. Increase safety stock. |
+| Z → X or Y | Demand stabilizing | Possible to simplify forecast model. Review safety stock for reduction. |
+| Any → CZ | Low value + erratic | Strong discontinuation candidate. Run slow-mover kill decision. |
+
+---
+
+## 5. Vendor Management Decision Logic
+
+### 5.1 Vendor Tier Classification
+
+Classify vendors into tiers based on annual purchase volume, strategic importance,
+and supply risk profile:
+
+| Tier | Criteria | Count (typical) | Review Cadence |
+|---|---|---|---|
+| **Strategic** | Top 5 by spend, or sole-source for A-items | 3–8 | Monthly scorecards, quarterly business reviews |
+| **Preferred** | Top 20 by spend, multiple A/B items | 10–25 | Quarterly scorecards |
+| **Approved** | All remaining active vendors | 30–100+ | Annual review |
+| **Probationary** | Vendors under corrective action | Variable | Weekly monitoring, monthly review |
+
+### 5.2 Vendor Scorecard Metrics
+
+Score each vendor quarterly on a 0–100 scale across these dimensions:
+
+| Dimension | Weight | Metric | Target | Calculation |
+|---|---|---|---|---|
+| **On-time delivery** | 30% | % of POs delivered within the agreed window (±1 day) | > 95% | Score = (Actual % / 95%) × 100, cap at 100 |
+| **Fill rate** | 25% | % of ordered units actually shipped | > 97% | Score = (Actual % / 97%) × 100, cap at 100 |
+| **Lead time consistency** | 20% | CV of actual lead time vs. stated lead time | CV < 0.15 | Score = max(0, 100 − (CV − 0.15) × 500) |
+| **Quality** | 15% | % of received units passing QC inspection | > 99% | Score = (Actual % / 99%) × 100, cap at 100 |
+| **Responsiveness** | 10% | Average response time to inquiries/issues (hours) | < 24 hours | Score = max(0, 100 − (Avg Hours − 24) × 2) |
+
+**Composite score thresholds:**
+
+| Score Range | Rating | Action |
+|---|---|---|
+| 90–100 | Excellent | Consider for volume increase, preferred terms |
+| 75–89 | Good | Standard operations, no action needed |
+| 60–74 | Needs Improvement | Issue corrective action request; 90-day improvement plan |
+| < 60 | Unacceptable | Immediate escalation; begin qualifying alternative suppliers |
+
+### 5.3 Vendor Lead Time Management
+
+Lead time management is the demand planner's most underleveraged tool for reducing
+inventory investment. A 1-day reduction in lead time across all vendors can reduce
+aggregate safety stock by 5–8%.
+
+**Lead time decomposition:**
+
+| Component | Typical Range | Planner Influence |
+|---|---|---|
+| Order processing at vendor | 1–3 days | Low — vendor's internal process |
+| Production/picking | 2–10 days | Medium — negotiate priority tiers |
+| Vendor ship preparation | 1–2 days | Low |
+| Transit time | 1–14 days | Medium — carrier selection, mode choice |
+| Receiving and put-away | 1–3 days | High — internal process improvement |
+| Quality hold (if applicable) | 0–5 days | High — streamline QC process |
+
+**Actions to reduce lead time:**
+
+1. For strategic vendors: negotiate VMI (vendor-managed inventory) where the vendor
+ monitors your inventory and ships proactively. Eliminates order processing delay.
+2. For all vendors: provide rolling 8-week forecasts to allow pre-positioning. Reduces
+ production/picking time on non-stock items.
+3. Internally: invest in receiving automation (ASN-enabled receiving, barcode scanning)
+ to cut receiving from 2–3 days to same-day.
+4. Negotiate consolidated weekly shipments vs. per-PO shipments to reduce transit
+ frequency while maintaining fill rate.
+
+### 5.4 MOQ (Minimum Order Quantity) Negotiation Framework
+
+When a vendor's MOQ creates excess inventory, evaluate these options in order:
+
+| Option | When to Use | Expected Outcome |
+|---|---|---|
+| **Negotiate lower MOQ** | Annual spend > $50K with this vendor; you have leverage | MOQ reduced 20–40% |
+| **Consolidate with other SKUs** | Multiple SKUs from same vendor; dollar minimum instead of unit minimum | Meet dollar MOQ without over-ordering individual SKUs |
+| **Accept higher price for lower MOQ** | MOQ overage cost > price premium cost | Pay 3–8% more per unit but order only what you need |
+| **Negotiate consignment** | Slow-moving items from strategic vendors | Vendor owns inventory until you sell it |
+| **Split orders with another buyer** | Known network of retailers ordering from the same vendor | Share the MOQ and split the shipment |
+| **Accept the overage** | Holding cost for the excess is < $500 and item is non-perishable | Order the MOQ and treat the overage as forward inventory |
+
+### 5.5 Vendor Negotiation for Lead Time Reduction
+
+**Preparation checklist before negotiating:**
+
+1. Document your current order volume and growth trajectory with this vendor.
+2. Compute the cost of their current lead time to your business: excess safety stock
+ carrying cost + stockout cost from lead time variability.
+3. Identify what you can offer in return: longer-term commitments, higher volumes,
+ fewer order frequency changes, rolling forecasts.
+4. Know your BATNA (best alternative): have a qualified secondary supplier identified.
+
+**Negotiation structure:**
+
+1. Present the data: "Over the past 6 months, your average lead time has been X days
+ with a standard deviation of Y. This variability costs us $Z annually in excess
+ safety stock."
+2. Propose the target: "We're requesting a committed lead time of X−2 days with a
+ guarantee of CV < 0.15."
+3. Offer the exchange: "In return, we can commit to rolling 8-week forecasts updated
+ weekly, and we'll consolidate to 2 orders per week instead of daily."
+4. Set the timeline: "Let's implement this for Q2 and review the scorecard at the
+ end of Q2 QBR."
+
+---
+
+## 6. Seasonal Buy and Markdown Timing Models
+
+### 6.1 Seasonal Buy Planning
+
+Seasonal categories require forward commitments because lead times exceed the selling
+season. The buy decision has two components: the initial buy (pre-season) and the
+in-season reorder (if the vendor supports it).
+
+#### Initial Buy Calculation
+
+```
+Initial Buy = Season Forecast × Initial Commitment % − Carry-Over Inventory
+```
+
+| Category Risk Profile | Initial Commitment % | Reserve for Reorder | Rationale |
+|---|---|---|---|
+| Low risk (staple seasonal, proven seller) | 70–80% | 20–30% | High confidence in forecast; reorder available |
+| Medium risk (trend-influenced, moderate history) | 55–65% | 35–45% | Hedge against forecast error |
+| High risk (fashion, new trend, first season) | 40–50% | 50–60% | Maximize flexibility; accept possible stockout |
+| One-time buy (import, long lead, no reorder) | 100% | 0% | No reorder option; commit fully but forecast conservatively |
+
+#### In-Season Reorder Triggers
+
+Monitor sell-through rate weekly starting from week 2 of the season:
+
+```
+Sell-Through Rate = Units Sold / (Units Sold + Units On-Hand + Units On-Order)
+```
+
+| Weeks into Season | Sell-Through vs. Plan | Action |
+|---|---|---|
+| Weeks 1–2 | > 120% of plan | Issue reorder immediately for 50% of reserve allocation |
+| Weeks 1–2 | 80–120% of plan | Hold; too early to confirm trend |
+| Weeks 3–4 | > 110% of plan | Issue reorder for remaining reserve |
+| Weeks 3–4 | 90–110% of plan | Issue conservative reorder (25% of reserve) |
+| Weeks 3–4 | 70–89% of plan | Hold all reserve; prepare markdown contingency |
+| Weeks 3–4 | < 70% of plan | Cancel any open reorders; initiate early markdown |
+| Weeks 5+ | Any pace | Reorders unlikely to arrive in time; manage with markdowns |
+
+### 6.2 Markdown Timing and Depth Model
+
+The markdown decision balances margin recovery against sell-through velocity. Every
+week of delay costs margin because holding costs accrue and the remaining selling
+window shrinks.
+
+#### Markdown Decision Matrix
+
+| Weeks Remaining in Season | Weeks of Supply at Current Rate | Recommended Action |
+|---|---|---|
+| > 6 weeks | < 3 | No markdown; possible reorder |
+| > 6 weeks | 3–6 | Hold price; monitor weekly |
+| > 6 weeks | 7–10 | First markdown: 20–25% off |
+| > 6 weeks | > 10 | Aggressive markdown: 30–40% off |
+| 4–6 weeks | < 3 | No markdown needed |
+| 4–6 weeks | 3–6 | Consider 15–20% markdown |
+| 4–6 weeks | 6–10 | Markdown 25–35% |
+| 4–6 weeks | > 10 | Markdown 40–50%; explore liquidation |
+| 2–4 weeks | < 3 | No markdown |
+| 2–4 weeks | 3–6 | Markdown 30–40% |
+| 2–4 weeks | > 6 | Markdown 50–60%; liquidation channels |
+| < 2 weeks | Any remaining | Final clearance 60–75% off or liquidation |
+
+#### Markdown Velocity Curve
+
+After applying a markdown, monitor the velocity response:
+
+| Markdown Depth | Expected Velocity Increase | If Not Achieved Within 1 Week |
+|---|---|---|
+| 20% off | 1.5–2.0× | Deepen to 30% |
+| 30% off | 2.0–3.0× | Deepen to 40% |
+| 40% off | 3.0–4.0× | Deepen to 50% or explore liquidation |
+| 50% off | 4.0–6.0× | If still not moving, this is dead stock — liquidate |
+
+### 6.3 Season-End Liquidation Decision
+
+When the selling season is ending and inventory remains:
+
+```
+Liquidation Net Recovery = (Liquidation Price × Remaining Units) − Logistics Cost
+Hold-to-Next-Season Net = (Expected Sell Price × Sell-Through Estimate)
+ − Holding Cost − Obsolescence Risk
+```
+
+**Liquidation is preferred when:**
+- Hold-to-next-season sell-through estimate < 60% (style risk, trend change)
+- Holding cost for 9–12 months > 15% of original cost (typical for most retailers)
+- Warehouse space is constrained and the space has higher-value alternative use
+- The product is trend/fashion and will be visually dated next season
+
+**Holding is preferred when:**
+- Product is a classic/carryover style with minimal fashion risk
+- Hold-to-next-season sell-through estimate > 80%
+- Warehouse space is available at low marginal cost
+- Liquidation offers are below variable cost (you'd lose money selling)
+
+---
+
+## 7. New Product Introduction Forecasting
+
+### 7.1 Analogous Item Selection
+
+The quality of a new product forecast depends almost entirely on the quality of the
+analogous items selected. Bad analogs produce bad forecasts regardless of the method.
+
+#### Selection Criteria (rank by importance)
+
+| Criterion | Weight | How to Match |
+|---|---|---|
+| **Category/subcategory** | 25% | Must be same subcategory (e.g., "premium yogurt" not just "dairy") |
+| **Price point** | 20% | Within ±20% of the new item's retail price |
+| **Brand tier** | 15% | National brand → national brand analog; private label → private label |
+| **Pack size / format** | 15% | Similar unit count, size, or weight |
+| **Target demographic** | 10% | Same customer segment (value, mainstream, premium) |
+| **Launch season** | 10% | Same quarter launch; seasonal patterns differ by quarter |
+| **Distribution breadth** | 5% | Similar initial door count (±25%) |
+
+#### Analog Scoring
+
+Score each candidate analog on the criteria above (1–5 scale per criterion, weighted).
+Select the top 3–5 analogs with composite scores > 3.5. If no analogs score > 3.0, the
+new product is truly novel — use category average with a 40% confidence band.
+
+### 7.2 New Product Lifecycle Curve
+
+Most new products follow a lifecycle curve with four phases:
+
+| Phase | Duration | Demand Pattern | Description |
+|---|---|---|---|
+| **Introduction** | Weeks 1–4 | Ramp-up, often trial-driven | Initial customer trial. Demand is unpredictable. |
+| **Growth** | Weeks 5–12 | Accelerating, repeat purchases begin | Repeat buyers emerge. Demand becomes more predictable. |
+| **Stabilization** | Weeks 13–26 | Plateaus to steady state | Item finds its "run rate." Baseline forecast is reliable. |
+| **Maturity** | Weeks 27+ | Stable or slowly declining | Standard demand planning applies. |
+
+**Forecast by phase:**
+
+| Phase | Method | Confidence Band |
+|---|---|---|
+| Introduction (1–4 weeks) | Analog average × 1.1 (trial bump) | ±40–50% |
+| Growth (5–12 weeks) | Blend: 40% analog + 60% own trajectory | ±25–35% |
+| Stabilization (13–26 weeks) | 80% own history, 20% analog | ±15–25% |
+| Maturity (27+ weeks) | Standard method selection per demand pattern | Standard WMAPE target |
+
+### 7.3 New Product Safety Stock Protocol
+
+| Weeks of History | Safety Stock Approach | Uncertainty Premium |
+|---|---|---|
+| 0–4 | Analog σ_d with 30% premium | 1.30× |
+| 5–8 | Blended σ_d (50% own + 50% analog) with 20% premium | 1.20× |
+| 9–12 | Blended σ_d (75% own + 25% analog) with 10% premium | 1.10× |
+| 13+ | Own σ_d, standard formula | 1.00× |
+
+### 7.4 New Product Kill Decision
+
+Not every new product succeeds. The kill decision should be structured, not emotional:
+
+| Metric | Kill Threshold | Timeframe |
+|---|---|---|
+| Sell-through vs. analog-based plan | < 30% of plan | After 6 weeks |
+| Repeat purchase rate (if measurable) | < 10% of trial purchasers | After 8 weeks |
+| Velocity trend | Declining for 4 consecutive weeks after introduction | After 6 weeks |
+| Category manager assessment | "Would not re-buy" | After 8 weeks |
+
+When a kill decision is made:
+1. Cancel all open POs immediately.
+2. Halt any planned promotions.
+3. Mark down remaining inventory at 30% off for 3 weeks, then 50% for 2 weeks.
+4. Liquidate any remainder after 5 weeks.
+5. Document the post-mortem: why did the analog-based forecast fail? Was it the
+ analogs, the product, the pricing, or the competitive context?
+
+---
+
+## 8. Demand Sensing and Exception Management
+
+### 8.1 Real-Time Demand Signal Monitoring
+
+In addition to periodic forecast reviews, monitor for demand signals that require
+immediate attention between forecast cycles:
+
+| Signal | Detection Method | Threshold | Action |
+|---|---|---|---|
+| **POS velocity spike** | Daily POS > 3× trailing 4-week daily average | 3× for 2+ consecutive days | Investigate cause; manual override if sustained |
+| **POS velocity drop** | Daily POS < 0.3× trailing 4-week daily average | 0.3× for 3+ consecutive days | Check for phantom inventory, display removal, or competitive action |
+| **Stockout cascade** | 3+ locations out of stock on same SKU within 48 hours | 3 locations | Emergency replenishment from DC; allocate by sales velocity |
+| **Weather alert** | NWS severe weather warning for region covering > 10% of stores | Forecast impact > 5% of category volume | Adjust forecasts for weather-sensitive categories |
+| **Competitive price move** | Competitor price check shows > 15% lower on comparable SKU | Confirmed at 3+ competitor locations | Alert merchandising; prepare forecast downward revision |
+| **Social media spike** | Monitoring tool shows > 500% increase in brand/product mentions | Sustained > 24 hours | Assess virality risk; prepare allocation plan |
+
+### 8.2 Forecast Override Governance
+
+Manual overrides are necessary but dangerous. Ungoverned overrides introduce bias and
+degrade forecast accuracy over time.
+
+**Override rules:**
+
+1. **All overrides must be documented** with a reason code and quantitative justification.
+2. **Override authority by magnitude:**
+ - ±10%: Planner can override without approval
+ - ±10–25%: Requires planning manager approval
+ - ±25–50%: Requires director approval
+ - > ±50%: Requires VP approval (or planning committee)
+3. **Override accuracy tracking:** Every override is tracked against actuals. If a planner's
+ overrides have a WMAPE > 40% over a quarter, their override authority is reviewed.
+4. **Sunset rule:** Overrides expire after 4 weeks. If the condition persists, a new
+ override (with fresh justification) must be created. This prevents stale overrides
+ from contaminating forecasts months later.
+5. **No "consensus" overrides:** Overrides from demand review meetings where forecasts
+ are adjusted to match sales team wishful thinking are the #1 source of positive bias.
+ Require every meeting override to cite a specific, verifiable external signal.
+
+---
+
+## 9. Inventory Health Diagnostics
+
+### 9.1 Weeks of Supply Analysis
+
+Weeks of supply (WOS) is the primary pulse-check metric for inventory health. Compute
+at the SKU level, aggregate to category, and review weekly.
+
+```
+WOS = On-Hand Inventory (units) / Average Weekly Demand (units)
+```
+
+Use the forward-looking forecast for the denominator, not trailing sales. Trailing sales
+understates demand when items have been out of stock (you can't sell what you don't have).
+
+**WOS Health Bands:**
+
+| WOS Range | Status | Action |
+|---|---|---|
+| < 2 weeks | Critical low | Expedite replenishment; consider reallocation from low-velocity locations |
+| 2–3 weeks | Low | Verify next PO arrival; place emergency order if no PO in transit |
+| 4–8 weeks | Healthy | Standard operations |
+| 9–12 weeks | Elevated | Review forecast; defer or reduce next PO if demand hasn't increased |
+| 13–26 weeks | Excess | Initiate markdown or promotional sell-through plan |
+| > 26 weeks | Critical excess | Flag for slow-mover kill decision; markdown or liquidate |
+
+### 9.2 Inventory Turns and GMROI
+
+**Inventory Turns:**
+```
+Annual Turns = Annual COGS / Average Inventory at Cost
+```
+
+| Category Type | Target Turns | Benchmark |
+|---|---|---|
+| Perishable grocery | 30–52 | 1× per week |
+| Center-store grocery | 12–20 | Every 2–4 weeks |
+| General merchandise | 6–12 | Every 4–8 weeks |
+| Seasonal (in-season) | 8–15 | Sell through in-season |
+| Seasonal (annual) | 2–4 | Lower because of off-season zero sales |
+
+**GMROI (Gross Margin Return on Inventory Investment):**
+```
+GMROI = Gross Margin $ / Average Inventory at Cost
+```
+
+A GMROI of 2.0 means you earn $2 in gross margin for every $1 invested in inventory.
+Minimum acceptable GMROI varies by category but should generally exceed the company's
+cost of capital divided by the gross margin percentage. For a retailer with 8% cost of
+capital and 35% gross margin, minimum GMROI = 0.08 / 0.35 = 0.23. In practice, most
+retailers target GMROI > 1.5 for healthy categories.
+
+### 9.3 Dead Stock and Obsolescence Identification
+
+Dead stock is inventory with zero sales for a defined period. It is the most expensive
+form of excess inventory because it generates zero return while consuming warehouse space
+and working capital.
+
+**Dead stock tiers:**
+
+| Tier | Definition | Action | Timeline |
+|---|---|---|---|
+| Aging | Zero sales for 8–12 weeks | Review — is this seasonal? New? Misplaced? | Investigate within 1 week |
+| Dead | Zero sales for 13–26 weeks | Markdown 40–50% or move to clearance | Initiate within 2 weeks |
+| Obsolete | Zero sales for > 26 weeks | Liquidate at any positive recovery or donate | Execute within 4 weeks |
+| Write-off | Liquidation/donation uneconomical | Destroy and write off; recover warehouse space | Execute within 2 weeks |
+
+**Root cause analysis for dead stock:**
+
+Run quarterly. Categorize dead stock by root cause to prevent recurrence:
+
+| Root Cause | % of Dead Stock (typical) | Prevention |
+|---|---|---|
+| Over-buying (forecast too high) | 35–45% | Improve forecast accuracy; tighten override governance |
+| Product failure (quality, customer rejection) | 15–20% | Faster new product kill decisions |
+| Seasonal carryover (missed markdown window) | 15–25% | Enforce markdown timing model from §6.2 |
+| Assortment change (delisted but not sold through) | 10–15% | Coordinate delist timing with sell-through |
+| Phantom inventory (system says it exists but doesn't) | 5–10% | Regular cycle counts on zero-velocity items |
+
+### 9.4 Allocation Logic for Multi-Location Retailers
+
+When DC inventory is insufficient to fill all store-level demand, allocate using a
+priority framework rather than pro-rata distribution:
+
+**Priority 1: Prevent store stockout on A-items.**
+Allocate first to stores with < 3 days of supply on A-items. Quantity = minimum of
+(days-to-next-DC-shipment × daily demand) to bridge until the next allocation cycle.
+
+**Priority 2: Match allocation to store-level forecast.**
+For remaining inventory, allocate proportional to each store's forward weekly forecast
+(not historical sales, which penalizes stores that have been out of stock).
+
+**Priority 3: Minimum presentation stock.**
+Every store receives at least the minimum display quantity regardless of forecast. An
+empty shelf signals "this item is discontinued" to the customer and destroys demand.
+
+**Priority 4: Cap allocation to shelf capacity.**
+Do not send more than a store can merchandise. Excess units in the backroom create
+shrinkage, damage, and out-of-date risk (for perishables).
+
+**Allocation frequency:**
+- A-items: allocate with every DC-to-store shipment (typically 2–5× per week)
+- B-items: allocate 1–2× per week
+- C-items: allocate weekly or bi-weekly
diff --git a/skills/inventory-demand-planning/references/edge-cases.md b/skills/inventory-demand-planning/references/edge-cases.md
new file mode 100644
index 00000000..34916d98
--- /dev/null
+++ b/skills/inventory-demand-planning/references/edge-cases.md
@@ -0,0 +1,602 @@
+# Inventory Demand Planning — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous demand planning situations that don't resolve through standard forecasting and replenishment workflows.
+
+These edge cases represent the scenarios that separate experienced demand planners from everyone else. Each one involves competing signals, imperfect data, time pressure, and real financial exposure. They are structured to guide decision-making when standard models break down.
+
+---
+
+## How to Use This File
+
+When a planning situation doesn't fit a clean pattern — when demand signals conflict, when models fail silently, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document every assumption and override so the decision can be audited at post-mortem.
+
+---
+
+### Edge Case 1: New Product Launch with Zero History and No Close Analog
+
+**Situation:**
+A retailer's private-label team is launching a plant-based protein bar in a new flavor profile (mango turmeric) that has no direct precedent in their assortment or their competitors'. The product will launch in 120 stores across the Southeast region. Retail price is $3.49 per bar, case pack of 12, with a vendor cost of $1.85. The vendor requires a minimum initial order of 10,000 units (833 cases) with a 6-week lead time for reorder. The merchandising team is projecting "strong performance" based on consumer trend data showing plant-based snacking growing 22% YoY, but has no quantitative forecast. The product has a 9-month shelf life.
+
+**Why It's Tricky:**
+There is no demand history for this exact item, and the nearest analogs (existing protein bars, existing plant-based snacks) are imperfect matches. The mango turmeric flavor is novel — it could be a breakout trend or a niche product. The 6-week reorder lead time means you cannot react quickly if the product takes off, but the 9-month shelf life means overstock is not immediately catastrophic. The merchandising team's qualitative confidence is not a substitute for a quantitative forecast.
+
+**Common Mistake:**
+Accepting the merchandising team's optimistic "gut feel" as the forecast and ordering aggressively. Or, conversely, ordering so conservatively that the product launches out-of-stock in week 2, killing momentum and making the launch look like a failure when it was actually a supply failure.
+
+**Expert Approach:**
+1. Build a structured analog set. Score candidates on category (snack bars), price point ($3–$4), brand tier (private label), format (single serve), and target demo (health-conscious). Select the top 3–5 analogs even if they're imperfect.
+2. Compute the median weekly velocity of the analogs at the same lifecycle stage (launch weeks 1–13). Weight by analog similarity score. Typical private-label snack bar launch velocity is 2–4 units/store/week after the trial bump.
+3. Build three scenarios: conservative (2 units/store/week), base (3.5 units/store/week), optimistic (6 units/store/week). For 120 stores, this yields weekly demand of 240, 420, or 720 units.
+4. Initial buy: commit to the base scenario for weeks 1–8 (420 × 8 = 3,360 units), plus safety stock at the conservative rate for the 6-week reorder lead time (240 × 6 × 1.3 buffer = 1,872 units). Total initial order: ~5,232 units. This is below the vendor's 10,000 MOQ.
+5. Negotiate with the vendor: either accept the 10,000 MOQ (accepting ~10 weeks of forward stock at base rate, which is fine given 9-month shelf life), or negotiate a 5,000-unit initial order with a committed reorder at week 4 based on early sell-through.
+6. Set weekly POS monitoring triggers: if week-1 velocity > 5 units/store/day, escalate to the optimistic scenario and place reorder immediately. If week-2 velocity < 1.5 units/store, flag for review — the product may be underperforming.
+7. Plan a week-3 evaluation checkpoint with merchandising. If sell-through is < 40% of base scenario, begin discussing promotional support. If > 150%, ensure reorder is en route.
+
+**Documentation Required:**
+- Analog selection with scoring rationale
+- Three-scenario forecast with assumptions
+- Initial buy calculation with safety stock methodology
+- Vendor MOQ negotiation outcome
+- Monitoring triggers and escalation plan
+- Week-3 checkpoint agenda
+
+**Resolution Timeline:**
+- Weeks -8 to -6: Analog selection, scenario modeling, initial buy decision
+- Weeks -6 to -4: PO placement, promotional material preparation
+- Week 0: Launch
+- Weeks 1–3: Daily POS monitoring against scenarios
+- Week 3: First checkpoint with merchandising
+- Week 4: Reorder decision based on actual sell-through
+
+---
+
+### Edge Case 2: Viral Social Media Spike — 10× Demand with No Warning
+
+**Situation:**
+A mid-tier kitchen gadget (a silicone garlic peeler, retail $8.99, category C-item averaging 15 units/week across 80 stores) suddenly goes viral on TikTok. A cooking influencer with 4.2M followers posted a 45-second video using the product, and it accumulated 8M views in 48 hours. Store-level POS data shows demand jumped to 180 units/day across the chain (vs. the normal ~2 units/day) starting Tuesday morning. Your DC has 2,400 units in stock. The vendor is a small importer based in Portland with 8-week lead time from their factory in Shenzhen. Your last PO for this item was 3 months ago for 1,200 units.
+
+**Why It's Tricky:**
+The instinct is to chase the demand — place a massive order and ride the wave. But viral demand follows a power-law decay curve, not a sustained step change. By the time a 8-week-lead-time order arrives, the spike is almost certainly over. Meanwhile, your DC inventory will be exhausted in 13 days at current run rate, and you'll be out of stock for 6+ weeks. Customers who can't find it will buy from Amazon.
+
+**Common Mistake:**
+Ordering 10,000+ units from the vendor based on the spike's peak demand. When the order arrives 8 weeks later, demand has returned to 20–30 units/week (slightly elevated baseline), and you're sitting on 10,000 units — 300+ weeks of supply.
+
+**Expert Approach:**
+1. Do NOT place a large emergency order based on peak demand. Viral spikes typically follow this decay pattern: peak in days 1–5, 50% decay by day 10, 80% decay by day 21, new baseline establishes by day 30–45 (usually 1.5–3× the pre-viral level).
+2. With 2,400 units in DC and ~180 units/day demand, you have ~13 days of supply. Implement allocation rules immediately: cap store-level fulfillment at 3× historical daily average (6 units/store/day max). This stretches DC supply to ~20 days and prevents a single high-traffic store from claiming all the inventory.
+3. Contact the vendor. Determine: (a) do they have any finished goods inventory in Portland? (b) can they expedite a partial shipment by air from Shenzhen? (c) what is the minimum order for an air shipment? Air freight at ~$5/unit on a $4.50 cost item is expensive but justified if you can capture $8.99 retail during the spike.
+4. Place a modest reorder: 2,000–3,000 units (not 10,000). If the vendor can air-ship 500 units in 7–10 days, do that for immediate demand. The remaining 2,000 by ocean in 8 weeks will arrive when the new baseline is establishing.
+5. Monitor the TikTok video and social conversation daily. Track engagement rate decay. When the video drops off the "For You" page algorithm (typically day 7–14), demand will fall sharply.
+6. After the spike subsides (day 30+), assess the new baseline. If it's 2–3× the pre-viral level, adjust the forecast model upward. If it's back to pre-viral levels, return to the standard model. Do not permanently inflate the forecast based on a one-time event.
+
+**Key Indicators:**
+- Social media engagement half-life (how quickly the video's daily views are declining)
+- Store-level POS day-over-day trend (is demand decelerating?)
+- Amazon price and availability for the same or similar product (competitor action)
+- Geographic concentration of demand (if concentrated in a few markets, the spike is more narrow)
+
+**Documentation Required:**
+- Social media monitoring data (daily view counts, engagement)
+- Daily POS data at store level during the spike
+- Allocation rules implemented and their rationale
+- Vendor communication log and order decisions
+- Post-spike baseline reassessment (at day 30 and day 60)
+
+**Resolution Timeline:**
+- Hours 0–4: Detect the spike via POS anomaly alerts; identify the social media source
+- Hours 4–12: Implement store-level allocation caps; contact vendor for emergency supply
+- Day 1–3: Monitor daily POS; track social media engagement decay
+- Day 3–7: If spike sustaining, place modest reorder (air freight if available)
+- Day 7–14: Social media engagement typically decays below threshold; spike decelerating
+- Day 21–30: Demand settling to new baseline; assess whether permanent elevation occurred
+- Day 30–45: Final baseline recalibration; close event; update model if sustained lift > 50%
+
+**Financial Impact:**
+A C-item at $8.99 retail and 15 units/week going to 180 units/day represents a revenue jump
+from ~$135/week to ~$11,328/week — an 84× increase. With 2,400 units in DC, the captured
+revenue is ~$21,576 before stockout. Chasing with a 10,000-unit ocean order ($45,000 at cost)
+that arrives to 25 units/week demand creates $39,375 in excess inventory. The smart play
+(500-unit air shipment + 2,000-unit modest ocean order) captures ~$8,500 in additional revenue
+during the tail of the spike while limiting overage risk to ~$3,500 in excess inventory.
+
+---
+
+### Edge Case 3: Supplier Lead Time Doubles Overnight — Single-Source Critical Item
+
+**Situation:**
+Your primary vendor for organic olive oil (an A-item, $12.99 retail, ~800 units/week across 150 stores) notifies you that their lead time is increasing from 14 days to 28 days effective immediately. The cause: their Mediterranean source experienced a poor harvest season, and the vendor is now sourcing from a secondary supplier in South America, which adds transit and quality testing time. You currently have 2,800 units in DC (3.5 weeks of supply at current demand) and a PO for 2,400 units that was due in 10 days but is now due in 24 days. Your safety stock calculation was based on the old 14-day lead time.
+
+**Why It's Tricky:**
+Your safety stock was calibrated for 14-day lead time. At the old lead time, your safety stock formula was: SS = 1.65 × 120 × √2 = 280 units (where σ_d = 120 units/week, LT = 2 weeks). Now LT = 4 weeks, so SS should be: 1.65 × 120 × √4 = 396 units. But you also need to recalculate the reorder point: ROP = d_avg × LT + SS = 800 × 4 + 396 = 3,596 units. You currently have IP = 2,800 + 2,400 = 5,200 units. That seems sufficient, but the in-transit PO is delayed by 14 days, meaning your effective on-hand for the next 24 days is only 2,800 units, which covers 3.5 weeks — less than the new 4-week lead time.
+
+**Common Mistake:**
+Accepting the vendor's new lead time without recalculating safety stock and reorder points. The planner orders the same quantities at the same frequency and discovers a stockout 3 weeks later when the gap becomes visible.
+
+**Expert Approach:**
+1. Immediately recalculate safety stock and reorder points using the new 28-day lead time. Document the before/after impact.
+2. Assess the inventory gap: Current on-hand (2,800) will last 3.5 weeks. The delayed PO (2,400 units) arrives in 24 days (~3.4 weeks). At 800 units/week consumption, you'll need 800 × 3.4 = 2,720 units in those 3.4 weeks, leaving only 80 units when the PO arrives — essentially zero safety stock.
+3. Place an emergency order immediately. Target quantity: enough to bridge the gap plus rebuild safety stock. Emergency order = (new SS − projected SS at PO arrival) + buffer = (396 − 80) + 400 = ~716 units. Round up to a case pack multiple.
+4. Contact the vendor: can they expedite any portion of the delayed PO? Even splitting it — 1,200 units at the original 14-day lead time and 1,200 at 28 days — would dramatically improve the position.
+5. Qualify a secondary supplier. Even if the secondary vendor has a higher cost or lower quality tier, having a backup prevents single-source dependency. Begin the qualification process immediately — don't wait for the crisis to deepen.
+6. Consider temporary demand-side measures: can you reduce facings (from 3 facings to 2) to slow sell-through without creating a visible out-of-stock? Can you substitute a different size (e.g., 25 oz instead of 16 oz) to spread demand across SKUs?
+7. Communicate to merchandising: service level on this item will temporarily drop from 97% to ~92% for the next 4–6 weeks. If this is unacceptable, discuss promotional alternatives or substitution strategies.
+
+**Documentation Required:**
+- Before/after safety stock and ROP calculations
+- Inventory position timeline projection (weekly, for the next 8 weeks)
+- Emergency order details and vendor response
+- Secondary supplier qualification plan with timeline
+- Communication to merchandising and category management
+
+**Resolution Timeline:**
+- Hour 0: Vendor notification received
+- Hours 0–4: Recalculate safety stock, ROP, and inventory position with new lead time
+- Hours 4–8: Place emergency order for the inventory gap
+- Day 1–2: Contact vendor to negotiate partial early shipment of delayed PO
+- Week 1: Begin secondary supplier qualification process
+- Week 1–2: Communicate revised service level expectations to merchandising
+- Weeks 2–6: Monitor inventory position weekly against projections
+- Weeks 6–8: Assess whether lead time has stabilized; update parameters permanently if so
+- Week 12: Review secondary supplier qualification status; decide whether to dual-source
+
+**Dual-Source Strategy Post-Crisis:**
+After any single-source lead time shock, evaluate dual-sourcing economics:
+- If the category is A-tier (>$500K annual purchases), dual-source at 70/30 split.
+ The 30% secondary supplier provides insurance and keeps the primary vendor competitive.
+- If B-tier ($100K–$500K), qualify a backup but keep orders single-source until triggered.
+- If C-tier (<$100K), the qualification cost may exceed the risk. Accept single-source
+ and carry additional safety stock instead.
+
+---
+
+### Edge Case 4: Unplanned Competitor Promotion Causes Demand Drop — Cannibalization You Didn't Plan
+
+**Situation:**
+Your chain's premium laundry detergent (Tide Ultra, A-item, $13.99, ~600 units/week across 120 stores) shows a sudden 35% velocity decline starting this week. POS data confirms it — down to ~390 units/week. There is no quality issue, no out-of-stock, and no change in shelf placement. A field report from a regional manager reveals that a competing national chain launched an aggressive BOGO promotion on their comparable Persil product, and a mass-market competitor is running a 40% off promotion on their private-label equivalent. Neither of these competitive actions was in your promotional calendar or forecasting inputs.
+
+**Why It's Tricky:**
+Your forecast model doesn't incorporate competitive promotional activity (most don't). The model will treat this as an unexplained demand drop and slowly adjust the baseline downward — which is wrong, because the competitive promotions will end in 2–3 weeks and your demand will recover. If you let the model self-correct, it will under-forecast the recovery period, leading to a stockout when competitive promotions end and demand snaps back.
+
+**Common Mistake:**
+Letting the automated forecast adjust downward based on the depressed actual sales. The model doesn't know why sales dropped, so it interprets it as a trend change. Two weeks later, when demand recovers, the system doesn't have enough inventory because it ordered based on the depressed forecast.
+
+**Expert Approach:**
+1. Confirm the cause: verify the competitive promotion through field observation, competitive intelligence, or syndicated data (Nielsen/IRI). Don't assume — there could be multiple causes.
+2. Once confirmed, apply a manual forecast override for the promotional period. Set the forecast to the depressed level (390 units/week) for the known duration of the competitive promotion (typically 2–4 weeks).
+3. Critically: also apply a forward override for the recovery period. When the competitive promo ends, expect a 10–20% bounce-back above the pre-event baseline for 1–2 weeks as customers who delayed purchases return. Set the recovery forecast to 660–720 units/week for weeks 1–2 post-competitive-promo.
+4. Adjust incoming orders: reduce the next 2 POs by the difference (600 → 390 = 210 units/week reduction). But do NOT cancel or defer orders that would leave you short during the recovery.
+5. Brief merchandising: "Tide is down 35% this week due to competitive BOGO on Persil at [competitor]. We project this lasts 2–3 weeks. We do not recommend a reactive promotion — it would erode margin without recovering the lost volume (customers have already stockpiled from the competitor). Recommend holding price and capturing the recovery."
+6. After the event, mark these 2–4 weeks as "competitive interference" in the demand history so the baseline model excludes them from future training data.
+
+**Key Indicators:**
+- Duration of the competitive promotion (check competitor circulars/websites weekly)
+- Whether additional competitors pile on (competitive cascades happen in laundry, soda, and cereal)
+- Whether the demand recovery follows the expected bounce-back pattern
+- Whether the competitive promotion was a one-time event or signals a strategic price repositioning
+
+**Documentation Required:**
+- Competitive intelligence source and verification
+- Manual override with reason code "competitive_promo_external"
+- Adjusted PO schedule for the event window
+- Recovery forecast and rationale
+- Post-event analysis comparing actuals to the override forecast
+
+**Resolution Timeline:**
+- Day 0–1: Detect the velocity drop; confirm competitive cause via field reports
+- Day 1–2: Apply manual forecast override for the dip and the expected recovery
+- Day 2–5: Adjust incoming POs downward for the promotional window
+- End of competitive promo + 2 weeks: Analyze recovery pattern vs. forecast
+- End of competitive promo + 4 weeks: Close out event; tag demand history; update model
+
+**Financial Impact Quantification:**
+Compute the lost margin during the event: (normal demand − actual demand) × unit margin × duration.
+For this example: (600 − 390) × ~$4.00 margin × 3 weeks = ~$2,520 lost margin from volume loss.
+Compare this to the cost of a reactive promotion (which would typically cost $3,000–$5,000 in margin
+erosion for a category this size) to justify the "hold price" recommendation.
+
+---
+
+### Edge Case 5: Demand Pattern Regime Change — Model Fails Silently
+
+**Situation:**
+A popular breakfast cereal (Cheerios 18 oz, B-item, $4.29, ~400 units/week across 100 stores) has been forecasted with Holt-Winters for 3 years with stable seasonal patterns and WMAPE of 18%. Over the past 6 weeks, the model's tracking signal has crept from +1.5 to +4.8, indicating systematic positive bias (forecast > actuals). Actual sales have declined from 400 units/week to 310 units/week with no promotional activity, no competitive change, and no price change. A deeper look reveals that a competitor launched a new high-protein cereal at the same price point 8 weeks ago, and your chain's health-conscious customer segment is shifting to it.
+
+**Why It's Tricky:**
+This is a permanent demand level shift, not a temporary dip. The Holt-Winters model's seasonal component will eventually adapt, but the level component (alpha) adapts slowly — especially if alpha is set low (e.g., 0.1–0.2) for stability. The model will take 10–15 more weeks to self-correct, during which time it will consistently over-forecast, creating excess inventory.
+
+**Common Mistake:**
+Waiting for the model to self-correct. Or, conversely, panicking and switching the model entirely when a simple level adjustment would suffice.
+
+**Expert Approach:**
+1. Confirm the regime change: the tracking signal at +4.8 for 2+ periods is a clear indicator. Verify by computing the new mean demand (310 units/week) and comparing to the model's level component.
+2. Do NOT switch the forecast model yet. The seasonal pattern may still be valid — the item is still seasonal cereal. What changed is the level (intercept), not the pattern.
+3. Apply a one-time level adjustment: reset the Holt-Winters level component to the current 4-week average (310 units/week). Keep the seasonal indices and trend parameters. Re-initialize the model from this new level.
+4. Increase alpha temporarily (from 0.15 to 0.25) for the next 8 weeks to allow faster adaptation, then return to the standard alpha.
+5. Immediately recalculate safety stock using σ_d from the recent 8 weeks (which reflects the new demand regime), not the trailing 52 weeks.
+6. Reduce open POs to match the new run rate. Cancel or defer any POs that would push weeks of supply above 8 at the new demand level.
+7. Classify the competitor product as a "regime change event" and add it to the demand planning log. Propose to merchandising that they evaluate their assortment response (match the competitor product, promote Cheerios, or accept the share loss).
+
+**Key Indicators:**
+- Tracking signal trend (is it stabilizing at the new level or still diverging?)
+- Competitor product's velocity (is it still growing, or has it plateaued?)
+- Category total velocity (is the category growing, or is this a zero-sum shift?)
+- Customer switching behavior (if loyalty card data is available)
+
+**Documentation Required:**
+- Tracking signal history showing the drift from normal to ±4.8
+- Before/after forecast comparison at the new demand level
+- Safety stock recalculation with the new σ_d
+- PO adjustment details (quantities deferred or cancelled)
+- Root cause classification (competitive entry, consumer preference shift, etc.)
+- Merchandising communication and their response
+
+**Resolution Timeline:**
+- Day 0: Tracking signal triggers model review
+- Day 1–3: Confirm regime change vs. temporary dip; analyze root cause
+- Day 3–5: Apply level adjustment; recalculate safety stock; adjust POs
+- Weeks 2–8: Monitor with elevated alpha; confirm model is tracking the new level
+- Week 8: Return alpha to standard; close the event
+- Week 12: Retrospective — was the level shift permanent or did it partially reverse?
+
+**Frequency of Occurrence:**
+Regime changes affect 5–10% of SKUs annually. The most common causes are competitive
+entry/exit (40%), reformulation or packaging changes (25%), price repositioning (20%),
+and distribution changes (15%). The key is detecting them quickly — every week of delay
+in responding to a downward regime change adds ~1 week of excess inventory.
+
+---
+
+### Edge Case 6: Phantom Inventory — System Shows Stock, Shelves Are Empty
+
+**Situation:**
+Your highest-velocity SKU in the beverage category (a 24-pack water case, A-item, ~1,200 units/week across 80 stores) has been showing 95%+ in-stock rate in the system, but customer complaints about out-of-stocks have tripled in the past month. The WMS shows 3,400 units at the DC and the stores collectively show 2,100 units on hand. However, three separate stores have reported that they can't find the product despite the system showing 50–80 units each. A partial cycle count at the DC reveals an actual count of 2,100 units — the WMS is overstating by 1,300 units (38% phantom inventory).
+
+**Why It's Tricky:**
+Every replenishment decision for the past several weeks has been based on a position that was 1,300 units higher than reality. The system thinks the DC has 4.7 weeks of supply when it actually has 2.9 weeks. Stores are running out because store-level inventory is also likely overstated (if receiving errors or shrinkage are the cause). The problem is almost certainly not limited to this one SKU — whatever process caused the phantom inventory (receiving errors, system timing, shrinkage) is likely affecting other items.
+
+**Common Mistake:**
+Correcting the inventory in the WMS and moving on. The correction fixes the symptom but not the cause. Next month, phantom inventory will reappear.
+
+**Expert Approach:**
+1. Immediately conduct a full physical count on this SKU at the DC and at the 10 highest-volume stores. Adjust WMS/POS inventory records to match physical counts.
+2. Recalculate the inventory position with corrected numbers. You likely need to place an emergency order — the corrected IP is probably below the reorder point.
+3. Place an emergency order: the delta between the old (phantom) IP and the corrected IP is 1,300 units at the DC alone, plus whatever store-level adjustments are needed. Rush this order if possible.
+4. Investigate the root cause of the phantom inventory:
+ - **Receiving error:** Were units scanned into the WMS but physically not there? Check receiving logs against PO quantities for the past 60 days.
+ - **Shrinkage:** Is this a high-theft item? Water cases are not typically theft targets, so this is less likely.
+ - **System timing:** Is there a lag between physical movement and WMS update (e.g., cross-dock items that are "received" but immediately shipped to stores without a separate ship transaction)?
+ - **Return processing:** Were damaged/returned units re-entered into available inventory without physical verification?
+5. Expand the investigation. Run a phantom inventory screening across all A-items: pull any SKU where the system in-stock rate is > 95% but customer complaints or lost sales proxy metrics (search-to-purchase ratio, substitute purchase rate) indicate stockouts. These are your phantom inventory suspects.
+6. Implement a cycle count program targeting high-velocity items quarterly and any item with a discrepancy > 10% between system and physical counts.
+7. Adjust safety stock upward by 10–15% for the category until the root cause is resolved and verified, to buffer against ongoing phantom inventory risk.
+
+**Documentation Required:**
+- Physical count vs. system count by location
+- Root cause investigation findings
+- Emergency order details
+- Expanded screening results for other SKUs
+- Cycle count program specification
+- Safety stock adjustment and rationale
+
+**Resolution Timeline:**
+- Day 0: Customer complaints or lost-sales signals trigger investigation
+- Day 0–1: Physical count at DC; confirm phantom inventory exists
+- Day 1–2: Adjust WMS records; place emergency order; expand screening to all A-items
+- Days 3–7: Physical counts at top 20 stores on the affected SKU
+- Weeks 1–2: Root cause investigation across receiving, shrinkage, and system processes
+- Week 3: Implement corrective action (process change, cycle count program)
+- Month 2–3: Monitor for recurrence; verify corrective action effectiveness
+
+**Financial Impact:**
+Phantom inventory has a dual cost: (1) the lost sales from stockouts that the system didn't
+predict (in this case, ~300 units/week × $sell_price = significant revenue), and (2) the
+upstream effects — overstated inventory means the replenishment system didn't trigger orders
+when it should have, creating a cascading supply gap. For an A-item at 1,200 units/week,
+even a 20% phantom inventory rate translates to ~240 lost sales per week, which at $5 retail
+is $1,200/week in lost revenue, or ~$62,400/year for a single SKU.
+
+---
+
+### Edge Case 7: Vendor MOQ Conflict — Ordering Constraint vs. Demand Reality
+
+**Situation:**
+You carry a specialty imported Italian pasta brand (5 SKUs, each averaging 30–50 units/week across 60 stores). The vendor's minimum order quantity is 500 units per SKU per order, and they only accept orders on a monthly basis (once per month, delivery in 3 weeks). For a SKU averaging 40 units/week, the MOQ of 500 units represents 12.5 weeks of supply. With a 7-week order cycle (4-week review + 3-week lead time), your target order-up-to level should be about 360 units (7 weeks × 40 + safety stock). The MOQ forces you to order 39% more than you need.
+
+**Why It's Tricky:**
+You can't order less than the MOQ, but ordering 500 units every month means you're always carrying ~5 weeks of excess inventory. Across 5 SKUs, that's 2,500 excess units at ~$3.50 cost each = ~$8,750 in excess inventory investment. The holding cost (25% annually = ~$0.07/unit/week) seems small per unit but adds up to ~$9,100/year in excess carrying cost across the 5 SKUs. This isn't a one-time problem — it recurs every month.
+
+**Common Mistake:**
+Accepting the MOQ without quantifying the cost. Or, alternatively, fighting the vendor on MOQ without considering the alternatives.
+
+**Expert Approach:**
+1. Quantify the total cost of the MOQ constraint: annual excess holding cost ($9,100), waste risk (if shelf life is limited), and opportunity cost of the working capital.
+2. Evaluate options in order:
+ a. **Negotiate a dollar minimum instead of unit minimum:** If you order all 5 SKUs together, the combined order is 2,500 units × $3.50 = $8,750 per order. Propose a $6,000 order minimum with flexibility to allocate across SKUs based on need. Many importers prefer this because they still get a meaningful order.
+ b. **Extend the review period:** Instead of monthly orders, order every 6 weeks. This increases the target order-up-to level, making the MOQ less excessive. But it also increases safety stock needs.
+ c. **Accept the MOQ for top 2–3 SKUs and negotiate lower for the bottom 2:** Concentrate volume on the fast movers and ask for 300-unit MOQ on the slowest.
+ d. **Cross-dock or consolidate with other retailers:** If you're part of a buying group or co-op, combine orders with other members to share the MOQ.
+ e. **Assess the overage as forward stock:** If the product has 18+ months of shelf life, 12.5 weeks of supply is tolerable. The holding cost may be acceptable relative to the value of carrying the brand.
+3. Before negotiating, know your BATNA: are there alternative Italian pasta brands with better terms? What would switching cost (delisting fees, lost loyal customers)?
+4. Propose a 6-month trial: "We'd like to test a $5,000 minimum order across the 5 SKUs for Q3 and Q4. If our order frequency and reliability are maintained, we'd like to formalize this for the annual agreement."
+
+**Key Indicators:**
+- Shelf life remaining on excess inventory (critical for food products)
+- Sell-through rate of excess units before the next order arrives
+- Whether the vendor has other regional customers you could consolidate with
+- Total vendor spend as leverage for negotiation
+
+**Documentation Required:**
+- Annual excess holding cost calculation per SKU and total for the vendor
+- Vendor negotiation correspondence and outcome
+- Comparison of options evaluated (lower MOQ vs. dollar minimum vs. accept overage)
+- Any agreed trial terms and review dates
+
+**Resolution Timeline:**
+- Month 0: Quantify the MOQ cost impact across all SKUs from this vendor
+- Month 0–1: Prepare negotiation package; identify BATNA (alternative suppliers)
+- Month 1: Present to vendor at the next order cycle or QBR
+- Month 2: Implement the agreed terms on a 6-month trial basis
+- Month 8: Review trial results; formalize in the annual vendor agreement
+
+**MOQ Impact Calculator (per SKU):**
+```
+Excess Units per Order = MOQ − EOQ (or optimal order quantity)
+Annual Orders = 52 / (MOQ / Weekly Demand)
+Annual Excess Units = Excess per Order × Annual Orders
+Annual Excess Holding Cost = Annual Excess Units × Unit Cost × Holding Cost %
+```
+
+For the pasta example: Excess = 500 − 280 = 220 units per order. Annual orders = 52 / (500/40) = ~4.2.
+Annual excess units = 220 × 4.2 = ~924. Holding cost at 25% on $3.50 cost = 924 × $0.875 = ~$809/year.
+Across 5 SKUs with similar profiles, that's ~$4,000/year — worth negotiating but not worth losing the brand.
+
+---
+
+### Edge Case 8: Holiday Calendar Shift — Easter Moves 3 Weeks, Forecast Breaks
+
+**Situation:**
+Last year Easter fell on March 31. This year it falls on April 20 — a 3-week shift. Your seasonal candy category (Easter chocolate, jelly beans, marshmallow Peeps) typically sees a 6-week selling season centered on Easter week. Your Holt-Winters model uses 52-week seasonal indices. Because Easter shifted, the model is projecting peak demand in the same calendar weeks as last year (weeks 10–13) rather than the correct weeks (weeks 13–16 this year). The seasonal indices are aligning to the wrong calendar weeks.
+
+**Why It's Tricky:**
+Holt-Winters seasonal indices are indexed to week numbers, not to event dates. A 3-week shift in Easter means the model peaks 3 weeks too early. If you follow the model, you'll over-order for late March (building inventory for a peak that doesn't come) and under-order for mid-April (missing the actual peak). The financial exposure is significant: Easter candy is a $200K–$400K category with 15–20% margins on regular items and near-zero margin on post-Easter clearance.
+
+**Common Mistake:**
+Running the Holt-Winters model without adjusting for the holiday shift. Or manually shifting the seasonal indices but forgetting to shift the promotional calendar, vendor order deadlines, and markdown timing.
+
+**Expert Approach:**
+1. Before the forecasting cycle begins (typically 12–16 weeks before Easter), compute the calendar-week shift: ΔW = Easter_this_year_week − Easter_last_year_week. This year, ΔW = +3 weeks.
+2. Shift the seasonal indices: for any SKU with Easter-linked seasonality, shift the 52-week seasonal index array by ΔW positions. Index for week 10 last year now applies to week 13 this year.
+3. Apply the same shift to the build schedule: the 6-week selling window moves from weeks 8–13 (last year) to weeks 11–16 (this year). Vendor orders that were placed in January for March delivery now need to be placed for April delivery.
+4. Shift the markdown timing: post-Easter clearance moves from week 14 (last year) to week 17 (this year). Any markdown price changes scheduled for the old dates must be updated.
+5. Coordinate with store operations: Easter display set dates, endcap resets, and seasonal aisle transitions all shift by 3 weeks.
+6. Validate with at least 3 prior Easter years that show similar shifts. Look at 2019 (April 21) as the closest date comparator for demand patterns.
+7. Watch for interaction effects: if the shifted Easter overlaps with spring break schedules differently than last year, travel-related demand patterns (convenience stores, airports) may not follow the standard shift formula.
+8. Model the "gap" period: the 3 weeks between last year's Easter and this year's Easter will have lower demand than last year's model suggests but higher demand than a non-Easter baseline. Use a blended estimate.
+
+**Documentation Required:**
+- Holiday shift calculation and affected SKUs
+- Shifted seasonal indices (before and after)
+- Adjusted vendor order schedule
+- Adjusted markdown timing
+- Promotional calendar updates
+- Historical comparisons to similar-dated Easters
+
+**Financial Impact:**
+Easter candy is typically a $200K–$400K category for a mid-size retailer. A 3-week
+misalignment in seasonal indices can cause 25–35% of that inventory to be mistimed:
+arriving too early (incurring holding cost and space conflict) or peaking when demand
+has already shifted. Markdowns on Easter-specific product (chocolate bunnies, egg-shaped
+candy) are particularly steep because the product has zero value after Easter weekend.
+A mistimed buy can easily cost $30K–$60K in margin erosion on a category this size.
+
+**Other Holiday Shifts to Monitor:**
+- **Thanksgiving:** Always the 4th Thursday of November, but the gap between Thanksgiving
+ and Christmas (22–29 days) affects holiday season build timing.
+- **Ramadan:** Shifts ~11 days earlier each year (lunar calendar). Critical for retailers
+ with significant Muslim customer demographics. Specialty food demand shifts.
+- **Chinese New Year:** Falls between Jan 21 and Feb 20. Affects import lead times from
+ China by 2–3 weeks (factory closures).
+- **Back-to-school:** Not a fixed holiday but a regional event. Northern states start
+ in late August; Southern states start in early August. A planner managing both regions
+ needs different seasonal indices for the same categories.
+
+---
+
+### Edge Case 9: Weather-Sensitive Demand Miscalculation — Heat Wave in March
+
+**Situation:**
+An unexpected early heat wave hits the Southeast (temperatures 15–20°F above normal for 10 days in mid-March). Your forecast models are projecting normal March demand for summer-seasonal categories: bottled water, sunscreen, ice cream, fans, and outdoor furniture. POS data on day 2 of the heat wave shows bottled water up 280%, sunscreen up 420%, and ice cream up 190%. Your DC has standard March inventory levels for these categories — roughly 3–4 weeks of supply at normal March rates, which translates to 8–12 days at the spiked demand.
+
+**Why It's Tricky:**
+Weather-driven demand spikes are temporary but intense. The heat wave will end in 10 days, but you'll have stockouts within 5–7 days on the fastest-moving items. Unlike seasonal ramp-up (which is gradual), this is a step-change. Your vendors are also not expecting March orders at summer volumes. And if you over-react and place summer-sized orders, you'll have excess when temperatures normalize, especially for sunscreen (which most customers won't need again until actual summer).
+
+**Common Mistake:**
+Treating the heat wave as the start of summer. Placing orders sized for sustained summer demand when this is a 10-day weather event. Or, alternatively, doing nothing because "March orders are already placed" and letting stores run out.
+
+**Expert Approach:**
+1. Separate items into "weather-temporary" and "weather-pull-forward" categories:
+ - **Weather-temporary:** Items consumed during the heat wave that won't reduce summer demand (e.g., ice cream eaten today doesn't reduce ice cream eaten in July). These need incremental inventory for the event only.
+ - **Weather-pull-forward:** Items purchased now that would have been purchased later (e.g., sunscreen, fans). These pull demand from the summer season — over-ordering now creates a surplus later.
+2. For weather-temporary items (water, ice cream): place an emergency order sized for 10 days of elevated demand minus current inventory. Use regional distributors or DSD (direct-store-delivery) vendors who can respond in 24–48 hours.
+3. For weather-pull-forward items (sunscreen, fans, outdoor furniture): order conservatively. These customers are buying their summer supply early. Order enough to cover the current spike (5–7 days of additional supply) but reduce your planned April/May orders by the same amount.
+4. Communicate to stores: allocate weather-sensitive items based on geographic proximity to the heat wave. Stores in the affected region get priority; stores in unaffected northern markets maintain normal allocations.
+5. After the heat wave: analyze the demand transfer. For pull-forward categories, compute how much April/May demand was pulled into March and adjust the summer season forecast downward accordingly.
+6. Do NOT let the heat wave contaminate the seasonal baseline model. Tag these 10 days as "weather event" in the demand history so the model ignores them when computing seasonal indices for next year.
+
+**Documentation Required:**
+- Weather forecast data (NWS source) and affected geographic regions
+- Category classification: weather-temporary vs. weather-pull-forward
+- Emergency order details by category
+- Store allocation rules during the event
+- Post-event demand transfer analysis
+- Demand history tagging for model hygiene
+
+**Resolution Timeline:**
+- Day 0–1: Weather alert triggers category review; classify temporary vs. pull-forward
+- Day 1–2: Place emergency orders for weather-temporary items via DSD and regional distributors
+- Day 2–3: Adjust allocations to stores in the affected region; reduce allocations to unaffected regions
+- Day 5–7: Monitor if the heat wave is extending beyond 10 days; adjust orders if so
+- Post-event (day 12–15): Analyze demand transfer for pull-forward categories
+- Post-event (day 20–30): Adjust forward forecasts for summer categories downward by the pull-forward amount
+- Post-event: Tag affected days in demand history; run model hygiene cleanup
+
+**Common Weather Events and Their Demand Impact:**
+
+| Weather Event | Key Categories Affected | Typical Demand Change | Duration |
+|---|---|---|---|
+| Heat wave (10+ days above normal) | Water, ice cream, fans, sunscreen, outdoor | +100–400% | 7–14 days |
+| Cold snap (10+ days below normal) | Soup, hot chocolate, space heaters, rock salt | +80–250% | 5–10 days |
+| Hurricane / major storm (pre-landfall) | Water, batteries, flashlights, canned food, generators | +500–1000% | 2–4 days pre-event |
+| Blizzard / ice storm | Bread, milk, eggs ("French toast index"), shovels | +200–500% | 1–3 days pre-event |
+| Extended rain | Umbrellas, rain gear, indoor entertainment | +50–150% | Duration of event |
+
+---
+
+### Edge Case 10: End-of-Life Transition — Old and New SKU Cannibalize Each Other
+
+**Situation:**
+A major brand is transitioning from V1 to V2 of a popular household cleaner (improved formula, new packaging, same price point). V1 is a B-item averaging 250 units/week. V2 will launch in 4 weeks with planned distribution to all 100 stores. The manufacturer is offering a one-time V2 introductory buy at a 15% discount. The complication: V1 and V2 will coexist on shelf for 6–10 weeks during the transition. The brand is not offering to buy back unsold V1 inventory. You currently have 3,200 units of V1 in the system (DC + stores = ~12.8 weeks of supply at the current rate).
+
+**Why It's Tricky:**
+During the transition, V1 and V2 will cannibalize each other. Total brand demand will likely remain flat or grow slightly (V2 launch may attract trial), but the split between V1 and V2 is uncertain. If V2 takes off quickly, V1 demand collapses and you're stuck with excess. If V2 launches slowly (customer resistance to change), V1 holds demand longer. The manufacturer's introductory discount pressures you to buy heavily on V2, but that bet compounds the V1 excess risk.
+
+**Common Mistake:**
+Buying V2 aggressively to capture the introductory discount while ignoring the V1 run-down plan. Six weeks later, V1 is occupying shelf space, DC slots, and working capital while V2 is the seller.
+
+**Expert Approach:**
+1. Model the transition as a combined brand forecast with a split ratio that shifts over time:
+ - Weeks 1–2 (post-V2 launch): V1 retains 70% of brand volume, V2 captures 30% (trial phase)
+ - Weeks 3–4: V1 at 50%, V2 at 50%
+ - Weeks 5–6: V1 at 30%, V2 at 70%
+ - Weeks 7+: V1 at 10%, V2 at 90%
+ These ratios are estimates — adjust based on brand's historical transition data and customer research.
+2. Run down V1 inventory intentionally. Stop reordering V1 immediately — you have 12.8 weeks at current rate, but demand will decline per the split model. Compute V1 sales under the declining split: ~250 × (0.7 + 0.7 + 0.5 + 0.5 + 0.3 + 0.3 + 0.1 + 0.1) = ~800 units over 8 weeks. You have 3,200 in the system — you'll have ~2,400 excess.
+3. Initiate V1 markdowns early — don't wait for the product to become unsellable. Week 1 post-V2 launch: take 20% off V1 to accelerate sell-through. Week 4: 40% off. Week 6: liquidate or donate any remainder.
+4. Size the V2 introductory buy conservatively: 4 weeks of supply at the V2 split rate, not at the full brand rate. That's ~250 × (0.3 + 0.5 + 0.7 + 0.9) = ~600 units for the first 4 weeks. Take the introductory discount on 600–800 units, not the 2,000+ the manufacturer will suggest.
+5. Negotiate with the manufacturer: request unsold V1 return credit or a markdown fund contribution. Most CPG brands transitioning formulas will contribute 25–50% of the V1 markdown cost if asked, because they want V1 off shelf to drive V2 trial.
+6. Track the actual V1/V2 split weekly and adjust. If V2 takes off faster than modeled, accelerate V1 markdowns. If V2 is slow, hold V1 price and defer V2 reorder.
+
+**Documentation Required:**
+- Combined brand forecast with V1/V2 split ratios
+- V1 run-down plan with markdown schedule
+- V2 introductory buy calculation
+- Manufacturer negotiation on return credit / markdown fund
+- Weekly V1/V2 split tracking vs. plan
+
+**Resolution Timeline:**
+- Weeks -6 to -4: Build V1/V2 combined forecast; compute V1 run-down plan
+- Week -4: Stop V1 reorders; negotiate manufacturer markdown support
+- Week -2: Set V1 markdown schedule; finalize V2 introductory buy
+- Week 0: V2 launches; V1 takes first markdown (20% off)
+- Week 4: V1 takes second markdown (40% off) if excess remains
+- Week 6: Liquidate any remaining V1 inventory
+- Week 8: Transition complete; V2 on standard replenishment
+
+**Financial Modeling:**
+Compute the total transition cost: V1 markdown cost (units × markdown depth × unit cost) +
+V1 liquidation loss + V2 introductory buy discount benefit − manufacturer markdown fund.
+For this example: if 2,400 V1 units remain and average markdown recovery is 60% of cost,
+the V1 loss is 2,400 × $cost × 0.40. The V2 introductory buy at 15% discount on 600–800
+units saves ~$cost × 0.15 × 700 = modest savings. Net transition cost is typically $2K–$5K
+for a brand of this size, which is the cost of maintaining a clean shelf transition.
+
+---
+
+### Edge Case 11: Multi-Location Allocation During Supply Constraint — Not Enough for Everyone
+
+**Situation:**
+A critical supplier shortage has reduced your supply of a top-selling protein powder (A-item, $34.99, ~900 units/week across 120 stores) by 60% for the next 6 weeks. You'll receive approximately 360 units/week instead of the normal 900. You cannot source from an alternative supplier — this is a branded product with an exclusive distribution agreement. The 120 stores have widely varying velocities: the top 20 stores sell 40% of total volume, the middle 40 sell 35%, and the bottom 60 sell 25%.
+
+**Why It's Tricky:**
+You can't serve all stores at their normal levels. Pro-rata allocation (giving each store 40% of their normal replenishment) seems fair but is suboptimal — it guarantees every store runs out rather than keeping some stores in-stock. But fully stocking the top 20 stores and cutting off the bottom 60 creates customer service issues at those locations and potential legal/franchise issues if you have contractual obligations.
+
+**Common Mistake:**
+Pro-rata allocation across all stores. Every store gets 40% of normal, every store stocks out in ~4 days, and the customer experience is universally bad rather than selectively managed.
+
+**Expert Approach:**
+1. Calculate the allocation by store tier to maximize total units sold (minimize lost sales):
+ - Top 20 stores: allocate at 70% of their normal rate (252 units/week). These stores have the highest traffic; even partial stock generates more sales per unit than full stock at a low-traffic store.
+ - Middle 40 stores: allocate at 35% of their normal rate (~110 units/week). Enough to maintain some presence.
+ - Bottom 60 stores: allocate at 15% of their normal rate (~54 units/week). Maintain minimum presentation stock only.
+ - Total: 252 + 110 + 54 = ~416 units/week. This exceeds the 360 available, so scale proportionally.
+2. Implement a maximum per-customer purchase limit at the store level (2 units per transaction) to prevent stockpiling.
+3. Communicate transparently to store managers: "Protein powder is on constrained allocation for the next 6 weeks due to supplier shortage. Your allocation is [X] units/week. We'll resume normal replenishment in [date]."
+4. Monitor sell-through rates at each tier. If the top-20 stores are selling out in 3 days, they're effectively under-allocated. If bottom-60 stores are carrying inventory into the next week, they're over-allocated. Adjust weekly.
+5. Prepare substitution signage for stores: "Looking for [brand]? Try [alternative] while supplies are limited." Even without a direct substitute supplier, suggesting a different brand/format captures some sales that would otherwise be lost.
+6. Track lost sales using a proxy: compare same-store sales of complementary items (protein bars, shakers) — a decline suggests customers are going elsewhere entirely.
+
+**Documentation Required:**
+- Allocation model with tier breakdowns
+- Weekly allocation vs. sell-through by tier
+- Customer purchase limit implementation
+- Lost sales estimate methodology and tracking
+- Supplier communication and expected resolution timeline
+
+**Resolution Timeline:**
+- Day 0: Supplier confirms constraint; demand planner receives allocation
+- Day 0–1: Build tiered allocation model; communicate to store operations
+- Day 1–2: Implement POS purchase limits; prepare substitution signage
+- Weekly for 6 weeks: Adjust allocations based on actual sell-through by tier
+- Week 6: Supplier confirms return to normal supply
+- Week 7–8: Rebuild safety stock at normal replenishment rates
+
+**Financial Impact:**
+Lost sales during a 60% supply constraint on a 900 units/week A-item at $34.99 retail:
+(900 − 360) × $34.99 × 6 weeks = ~$113,367 in lost revenue. With tiered allocation
+optimizing sell-through, you can recapture 15–25% of the otherwise lost sales compared
+to naive pro-rata allocation, worth $17K–$28K in recovered revenue. The allocation
+optimization effort pays for itself many times over.
+
+---
+
+### Edge Case 12: Demand Forecast Consensus Meeting Override — Sales Team Inflates Forecast
+
+**Situation:**
+During the monthly S&OP demand review, the sales team insists on overriding the statistical forecast for a key product line (premium pet food, 15 SKUs, ~$1.2M annual revenue). The statistical forecast projects flat demand at ~$100K/month. The sales team argues that a new distribution agreement with a pet specialty chain will add $30K/month starting next month. They want the forecast increased to $130K/month across all 15 SKUs proportionally. However, the distribution agreement is not yet signed (it's in "final review"), the specialty chain hasn't confirmed shelf dates, and the sales team has a history of overestimating new account volume by 40–60%.
+
+**Why It's Tricky:**
+The sales team may be right — the distribution deal is real and the incremental volume is plausible. But "plausible" is not "certain." If you accept the override and the deal delays by 2 months (common), you'll have 2 months of $30K/month in excess inventory ($60K), which for pet food with 12-month shelf life is manageable but ties up working capital. If you reject the override and the deal closes on time, you'll be short $30K/month and unable to serve the new account, potentially killing the deal.
+
+**Common Mistake:**
+Either accepting the sales team's number at face value (leading to chronic over-forecasting) or rejecting it entirely (leading to under-investment in growth).
+
+**Expert Approach:**
+1. Never accept or reject an override without a probability-weighted approach. Ask the sales team to commit to a probability of close and timing:
+ - Probability the deal closes: 70% (sales team's estimate — discount to 50% based on historical calibration)
+ - If it closes, when will volume start? 4 weeks (sales team) — add 4 weeks for historical optimism = 8 weeks realistic
+ - If it closes, what's the ramp rate? Rarely 100% from day 1. Model 50% in month 1, 75% in month 2, 100% in month 3.
+2. Compute the expected value override: $30K × 50% probability × ramp rate = $7.5K in month 1, $11.25K in month 2, $15K in month 3.
+3. Apply this as a staged override, not a flat $30K increase. Month 1: $107.5K. Month 2: $111.25K. Month 3: $115K.
+4. Set a kill trigger: if the deal hasn't closed by month 2, remove the override entirely and return to the statistical forecast. Do not carry speculative overrides indefinitely.
+5. Track the outcome: did the deal close? When? At what volume? Use this to calibrate the sales team's future override accuracy and adjust the probability discount accordingly.
+6. Distribute the override unevenly across SKUs: the new account likely won't carry all 15 SKUs. Ask the sales team which 5–8 SKUs the new account will stock, and concentrate the override there.
+
+**Documentation Required:**
+- S&OP meeting notes with the original override request
+- Probability-weighted override calculation
+- Staged implementation plan by month and SKU
+- Kill trigger date and conditions
+- Post-event accuracy tracking
+
+**Resolution Timeline:**
+- S&OP meeting: Capture the override request; apply probability weighting
+- Day 1–3: Compute the staged override and distribute across relevant SKUs
+- Week 1: Adjust POs to reflect the staged override (not the full $30K)
+- Week 4 (if deal not signed): Reduce override by 50%
+- Week 8 (if deal still not signed): Remove override entirely; return to statistical forecast
+- When deal closes: Ramp up based on actual account setup timeline
+- Month 3 post-close: Compare actual volume to the staged override; calibrate sales team accuracy
+
+**Historical Calibration:**
+Track the accuracy of sales team overrides over time. Maintain a simple table:
+
+| Override Source | Override Count (trailing 12 months) | Avg. Override Amount | Avg. Actual Result | Realization Rate |
+|---|---|---|---|---|
+| Sales team — new accounts | 8 | +$25K/month | +$12K/month | 48% |
+| Sales team — existing account growth | 12 | +$15K/month | +$9K/month | 60% |
+| Marketing — promotional lift | 6 | +40% lift | +32% lift | 80% |
+| Category management — trend calls | 5 | ±20% | ±8% | 40% |
+
+This calibration table allows you to apply evidence-based probability discounts to future
+overrides. A sales team with a 48% realization rate on new account overrides should have
+their stated volume multiplied by 0.48, not accepted at face value.
diff --git a/skills/ios-developer/SKILL.md b/skills/ios-developer/SKILL.md
index 8fa9a17d..95edf2fc 100644
--- a/skills/ios-developer/SKILL.md
+++ b/skills/ios-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ios-developer
-description: "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,"
+description: |
+ Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,
SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.
Use PROACTIVELY for iOS-specific features, App Store optimization, or native
iOS development.
diff --git a/skills/java-pro/SKILL.md b/skills/java-pro/SKILL.md
index 3b7e0a08..a070be0e 100644
--- a/skills/java-pro/SKILL.md
+++ b/skills/java-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: java-pro
-description: "Master Java 21+ with modern features like virtual threads, pattern"
+description: |
+ Master Java 21+ with modern features like virtual threads, pattern
matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including
GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java
development, microservices architecture, or performance optimization.
diff --git a/skills/javascript-pro/SKILL.md b/skills/javascript-pro/SKILL.md
index 2b4f0d18..a3c53a04 100644
--- a/skills/javascript-pro/SKILL.md
+++ b/skills/javascript-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: javascript-pro
-description: "Master modern JavaScript with ES6+, async patterns, and Node.js"
+description: |
+ Master modern JavaScript with ES6+, async patterns, and Node.js
APIs. Handles promises, event loops, and browser/Node compatibility. Use
PROACTIVELY for JavaScript optimization, async debugging, or complex JS
patterns.
diff --git a/skills/julia-pro/SKILL.md b/skills/julia-pro/SKILL.md
index d0063344..c38ccb0e 100644
--- a/skills/julia-pro/SKILL.md
+++ b/skills/julia-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: julia-pro
-description: "Master Julia 1.10+ with modern features, performance optimization,"
+description: |
+ Master Julia 1.10+ with modern features, performance optimization,
multiple dispatch, and production-ready practices. Expert in the Julia
ecosystem including package management, scientific computing, and
high-performance numerical code. Use PROACTIVELY for Julia development,
diff --git a/skills/kubernetes-architect/SKILL.md b/skills/kubernetes-architect/SKILL.md
index b8ac829c..3c9d06e2 100644
--- a/skills/kubernetes-architect/SKILL.md
+++ b/skills/kubernetes-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: kubernetes-architect
-description: "Expert Kubernetes architect specializing in cloud-native"
+description: |
+ Expert Kubernetes architect specializing in cloud-native
infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise
container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),
progressive delivery, multi-tenancy, and platform engineering. Handles
diff --git a/skills/legacy-modernizer/SKILL.md b/skills/legacy-modernizer/SKILL.md
index daf6efe5..516ba7f8 100644
--- a/skills/legacy-modernizer/SKILL.md
+++ b/skills/legacy-modernizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: legacy-modernizer
-description: "Refactor legacy codebases, migrate outdated frameworks, and"
+description: |
+ Refactor legacy codebases, migrate outdated frameworks, and
implement gradual modernization. Handles technical debt, dependency updates,
and backward compatibility. Use PROACTIVELY for legacy system updates,
framework migrations, or technical debt reduction.
diff --git a/skills/legal-advisor/SKILL.md b/skills/legal-advisor/SKILL.md
index 267335a8..91ba5e08 100644
--- a/skills/legal-advisor/SKILL.md
+++ b/skills/legal-advisor/SKILL.md
@@ -1,6 +1,7 @@
---
name: legal-advisor
-description: "Draft privacy policies, terms of service, disclaimers, and legal"
+description: |
+ Draft privacy policies, terms of service, disclaimers, and legal
notices. Creates GDPR-compliant texts, cookie policies, and data processing
agreements. Use PROACTIVELY for legal documentation, compliance texts, or
regulatory requirements.
diff --git a/skills/linkedin-cli/SKILL.md b/skills/linkedin-cli/SKILL.md
new file mode 100644
index 00000000..8401c8f0
--- /dev/null
+++ b/skills/linkedin-cli/SKILL.md
@@ -0,0 +1,536 @@
+---
+name: linkedin-cli
+description: "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator."
+source: community
+risk: safe
+---
+
+## When to Use
+
+Use this skill when you need to automate LinkedIn tasks such as profile fetching, connection management, or post creation via CLI, especially when integrated into automated workflows.
+
+# LinkedIn Skill
+
+You have access to `linkedin` – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more.
+
+Each command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are **not instant** – expect 30 seconds to several minutes depending on complexity.
+
+If `linkedin` is not available, install it:
+
+```bash
+npm install -g @linkedapi/linkedin-cli
+```
+
+## Authentication
+
+If a command fails with exit code 2 (authentication error), ask the user to set up their account:
+
+1. Go to [app.linkedapi.io](https://app.linkedapi.io) and sign up or log in
+2. Connect their LinkedIn account
+3. Copy the **Linked API Token** and **Identification Token** from the dashboard
+
+Once the user provides the tokens, run:
+
+```bash
+linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN
+```
+
+## When to Use
+
+Use this skill when you need to **orchestrate LinkedIn actions from scripts or an AI agent** instead of clicking through the web UI:
+
+- Building outreach, research, or recruiting workflows that rely on LinkedIn data and messaging.
+- Enriching leads or accounts by fetching people and company profiles in bulk.
+- Coordinating multi-step Sales Navigator or workflow runs where JSON output and exit codes are required.
+
+Always respect LinkedIn’s terms of service, local regulations, and your organisation’s compliance policies when using automation against real accounts.
+
+## Global Flags
+
+Always use `--json` and `-q` for machine-readable output:
+
+```bash
+linkedin --json -q
+```
+
+| Flag | Description |
+| ----------------------- | --------------------------------------- |
+| `--json` | Structured JSON output |
+| `--quiet` / `-q` | Suppress stderr progress messages |
+| `--fields name,url,...` | Select specific fields in output |
+| `--no-color` | Disable colors |
+| `--account "Name"` | Use a specific account for this command |
+
+## Output Format
+
+Success:
+
+```json
+{ "success": true, "data": { "name": "John Doe", "headline": "Engineer" } }
+```
+
+Error:
+
+```json
+{
+ "success": false,
+ "error": { "type": "personNotFound", "message": "Person not found" }
+}
+```
+
+Exit code 0 means the API call succeeded – always check the `success` field for the action outcome. Non-zero exit codes indicate infrastructure errors:
+
+| Exit Code | Meaning |
+| --------- | ------------------------------------------------------------------------------------------- |
+| 0 | Success (check `success` field – action may have returned an error like "person not found") |
+| 1 | General/unexpected error |
+| 2 | Missing or invalid tokens |
+| 3 | Subscription/plan required |
+| 4 | LinkedIn account issue |
+| 5 | Invalid arguments |
+| 6 | Rate limited |
+| 7 | Network error |
+| 8 | Workflow timeout (workflowId returned for recovery) |
+
+## Commands
+
+### Fetch a Person Profile
+
+```bash
+linkedin person fetch [flags] --json -q
+```
+
+Optional flags to include additional data:
+
+- `--experience` – work history
+- `--education` – education history
+- `--skills` – skills list
+- `--languages` – languages
+- `--posts` – recent posts (with `--posts-limit N`, `--posts-since TIMESTAMP`)
+- `--comments` – recent comments (with `--comments-limit N`, `--comments-since TIMESTAMP`)
+- `--reactions` – recent reactions (with `--reactions-limit N`, `--reactions-since TIMESTAMP`)
+
+Only request additional data when needed – each flag increases execution time.
+
+```bash
+# Basic profile
+linkedin person fetch https://www.linkedin.com/in/username --json -q
+
+# With experience and education
+linkedin person fetch https://www.linkedin.com/in/username --experience --education --json -q
+
+# With last 5 posts
+linkedin person fetch https://www.linkedin.com/in/username --posts --posts-limit 5 --json -q
+```
+
+### Search People
+
+```bash
+linkedin person search [flags] --json -q
+```
+
+| Flag | Description |
+| ---------------------- | -------------------------------------- |
+| `--term` | Search keyword or phrase |
+| `--limit` | Max results |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+
+```bash
+linkedin person search --term "product manager" --locations "San Francisco" --json -q
+linkedin person search --current-companies "Google" --position "Engineer" --limit 20 --json -q
+```
+
+### Fetch a Company
+
+```bash
+linkedin company fetch [flags] --json -q
+```
+
+Optional flags:
+
+- `--employees` – include employees
+- `--dms` – include decision makers
+- `--posts` – include company posts
+
+Employee filters (require `--employees`):
+
+| Flag | Description |
+| ------------------------ | ---------------------------- |
+| `--employees-limit` | Max employees to retrieve |
+| `--employees-first-name` | Filter by first name |
+| `--employees-last-name` | Filter by last name |
+| `--employees-position` | Filter by position |
+| `--employees-locations` | Comma-separated locations |
+| `--employees-industries` | Comma-separated industries |
+| `--employees-schools` | Comma-separated school names |
+
+| Flag | Description |
+| --------------- | -------------------------------------------------- |
+| `--dms-limit` | Max decision makers to retrieve (requires `--dms`) |
+| `--posts-limit` | Max posts to retrieve (requires `--posts`) |
+| `--posts-since` | Posts since ISO timestamp (requires `--posts`) |
+
+```bash
+# Basic company info
+linkedin company fetch https://www.linkedin.com/company/name --json -q
+
+# With employees filtered by position
+linkedin company fetch https://www.linkedin.com/company/name --employees --employees-position "Engineer" --json -q
+
+# With decision makers and posts
+linkedin company fetch https://www.linkedin.com/company/name --dms --posts --posts-limit 10 --json -q
+```
+
+### Search Companies
+
+```bash
+linkedin company search [flags] --json -q
+```
+
+| Flag | Description |
+| -------------- | ------------------------------------------------------------------------------------------------------------ |
+| `--term` | Search keyword |
+| `--limit` | Max results |
+| `--sizes` | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+
+```bash
+linkedin company search --term "fintech" --sizes "11-50,51-200" --json -q
+```
+
+### Send a Message
+
+```bash
+linkedin message send '' --json -q
+```
+
+Text up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues.
+
+```bash
+linkedin message send https://www.linkedin.com/in/username 'Hey, loved your latest post!' --json -q
+```
+
+### Get Conversation
+
+```bash
+linkedin message get [--since TIMESTAMP] --json -q
+```
+
+The first call for a conversation triggers a background sync and may take longer. Subsequent calls are faster.
+
+```bash
+linkedin message get https://www.linkedin.com/in/username --json -q
+linkedin message get https://www.linkedin.com/in/username --since 2024-01-15T10:30:00Z --json -q
+```
+
+### Connection Management
+
+#### Check connection status
+
+```bash
+linkedin connection status --json -q
+```
+
+#### Send connection request
+
+```bash
+linkedin connection send [--note 'text'] [--email user@example.com] --json -q
+```
+
+#### List connections
+
+```bash
+linkedin connection list [flags] --json -q
+```
+
+| Flag | Description |
+| ---------------------- | ------------------------------------------------------------------------------------ |
+| `--limit` | Max connections to return |
+| `--since` | Only connections made since ISO timestamp (only works when no filter flags are used) |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+
+```bash
+linkedin connection list --limit 50 --json -q
+linkedin connection list --current-companies "Google" --position "Engineer" --json -q
+linkedin connection list --since 2024-01-01T00:00:00Z --json -q
+```
+
+#### List pending outgoing requests
+
+```bash
+linkedin connection pending --json -q
+```
+
+#### Withdraw a pending request
+
+```bash
+linkedin connection withdraw [--no-unfollow] --json -q
+```
+
+By default, withdrawing also unfollows the person. Use `--no-unfollow` to keep following.
+
+#### Remove a connection
+
+```bash
+linkedin connection remove --json -q
+```
+
+### Posts
+
+#### Fetch a post
+
+```bash
+linkedin post fetch [flags] --json -q
+```
+
+| Flag | Description |
+| -------------------- | ------------------------------------------------------------------ |
+| `--comments` | Include comments |
+| `--reactions` | Include reactions |
+| `--comments-limit` | Max comments to retrieve (requires `--comments`) |
+| `--comments-sort` | Sort order: `mostRelevant` or `mostRecent` (requires `--comments`) |
+| `--comments-replies` | Include replies to comments (requires `--comments`) |
+| `--reactions-limit` | Max reactions to retrieve (requires `--reactions`) |
+
+```bash
+linkedin post fetch https://www.linkedin.com/posts/username_activity-123 --json -q
+
+# With comments sorted by most recent, including replies
+linkedin post fetch https://www.linkedin.com/posts/username_activity-123 \
+ --comments --comments-sort mostRecent --comments-replies --json -q
+```
+
+#### Create a post
+
+```bash
+linkedin post create '' [flags] --json -q
+```
+
+| Flag | Description |
+| --------------- | ------------------------------------------------------------------------------------------------------------------ |
+| `--company-url` | Post on behalf of a company page (requires admin access) |
+| `--attachments` | Attachment as `url:type` or `url:type:name`. Types: `image`, `video`, `document`. Can be specified multiple times. |
+
+Attachment limits: up to 9 images, or 1 video, or 1 document. Cannot mix types.
+
+```bash
+linkedin post create 'Excited to share our latest update!' --json -q
+
+# With a document
+linkedin post create 'Our Q4 report' \
+ --attachments "https://example.com/report.pdf:document:Q4 Report" --json -q
+
+# Post as a company
+linkedin post create 'Company announcement' \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+#### React to a post
+
+```bash
+linkedin post react --type [--company-url ] --json -q
+```
+
+Reaction types: `like`, `love`, `support`, `celebrate`, `insightful`, `funny`.
+
+```bash
+linkedin post react https://www.linkedin.com/posts/username_activity-123 --type like --json -q
+
+# React on behalf of a company
+linkedin post react https://www.linkedin.com/posts/username_activity-123 --type celebrate \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+#### Comment on a post
+
+```bash
+linkedin post comment '' [--company-url ] --json -q
+```
+
+Text up to 1000 characters.
+
+```bash
+linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Great insights!' --json -q
+
+# Comment on behalf of a company
+linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Well said!' \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+### Statistics
+
+```bash
+# Social Selling Index
+linkedin stats ssi --json -q
+
+# Performance analytics (profile views, post impressions, search appearances)
+linkedin stats performance --json -q
+
+# API usage for a date range
+linkedin stats usage --start 2024-01-01T00:00:00Z --end 2024-01-31T00:00:00Z --json -q
+```
+
+### Sales Navigator
+
+Requires a LinkedIn Sales Navigator subscription. Uses hashed URLs for person/company lookups.
+
+#### Fetch person
+
+```bash
+linkedin navigator person fetch --json -q
+```
+
+#### Search people
+
+```bash
+linkedin navigator person search [flags] --json -q
+```
+
+| Flag | Description |
+| ----------------------- | ------------------------------------------------------------------------------------------- |
+| `--term` | Search keyword or phrase |
+| `--limit` | Max results |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+| `--years-of-experience` | Comma-separated ranges: `lessThanOne`, `oneToTwo`, `threeToFive`, `sixToTen`, `moreThanTen` |
+
+```bash
+linkedin navigator person search --term "VP Marketing" --locations "United States" --json -q
+linkedin navigator person search --years-of-experience "moreThanTen" --position "CEO" --json -q
+```
+
+#### Fetch company
+
+```bash
+linkedin navigator company fetch [flags] --json -q
+```
+
+Optional flags:
+
+- `--employees` – include employees
+- `--dms` – include decision makers
+
+Employee filters (require `--employees`):
+
+| Flag | Description |
+| --------------------------------- | -------------------------------------------------- |
+| `--employees-limit` | Max employees to retrieve |
+| `--employees-first-name` | Filter by first name |
+| `--employees-last-name` | Filter by last name |
+| `--employees-positions` | Comma-separated positions |
+| `--employees-locations` | Comma-separated locations |
+| `--employees-industries` | Comma-separated industries |
+| `--employees-schools` | Comma-separated school names |
+| `--employees-years-of-experience` | Comma-separated experience ranges |
+| `--dms-limit` | Max decision makers to retrieve (requires `--dms`) |
+
+```bash
+linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural --employees --dms --json -q
+linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural \
+ --employees --employees-positions "Engineer,Designer" --employees-locations "Europe" --json -q
+```
+
+#### Search companies
+
+```bash
+linkedin navigator company search [flags] --json -q
+```
+
+| Flag | Description |
+| --------------- | ------------------------------------------------------------------------------------------------------------ |
+| `--term` | Search keyword |
+| `--limit` | Max results |
+| `--sizes` | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--revenue-min` | Min annual revenue in M USD: `0`, `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000` |
+| `--revenue-max` | Max annual revenue in M USD: `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`, `1000+` |
+
+```bash
+linkedin navigator company search --term "fintech" --sizes "11-50,51-200" --json -q
+linkedin navigator company search --revenue-min 10 --revenue-max 100 --locations "United States" --json -q
+```
+
+#### Send InMail
+
+```bash
+linkedin navigator message send '' --subject '' --json -q
+```
+
+Text up to 1900 characters. Subject up to 80 characters.
+
+```bash
+linkedin navigator message send https://www.linkedin.com/in/username \
+ 'Would love to chat about API integrations' --subject 'Partnership Opportunity' --json -q
+```
+
+#### Get Sales Navigator conversation
+
+```bash
+linkedin navigator message get [--since TIMESTAMP] --json -q
+```
+
+### Custom Workflows
+
+Execute a custom workflow definition from a file, stdin, or inline:
+
+```bash
+# From file
+linkedin workflow run --file workflow.json --json -q
+
+# From stdin
+cat workflow.json | linkedin workflow run --json -q
+
+# Inline
+echo '{"actions":[...]}' | linkedin workflow run --json -q
+```
+
+Check workflow status or wait for completion:
+
+```bash
+linkedin workflow status --json -q
+linkedin workflow status --wait --json -q
+```
+
+See [Building Workflows](https://linkedapi.io/docs/building-workflows/) for the workflow JSON schema.
+
+### Account Management
+
+```bash
+linkedin account list # List accounts (* = active)
+linkedin account switch "Name" # Switch active account
+linkedin account rename "Name" --name "New Name" # Rename account
+linkedin reset # Remove active account
+linkedin reset --all # Remove all accounts
+```
+
+## Important Behavior
+
+- **Sequential execution.** All operations for an account run one at a time. Multiple requests queue up.
+- **Not instant.** A real browser navigates LinkedIn – expect 30 seconds to several minutes per operation.
+- **Timestamps in UTC.** All dates and times are in UTC.
+- **Single quotes for text arguments.** Use single quotes around message text, post text, and comments to avoid shell interpretation issues with special characters.
+- **Action limits.** Per-account limits are configurable on the platform. A `limitExceeded` error means the limit was reached.
+- **URL normalization.** All LinkedIn URLs in responses are normalized to `https://www.linkedin.com/...` format without trailing slashes.
+- **Null fields.** Fields that are unavailable are returned as `null` or `[]`, not omitted.
diff --git a/skills/logistics-exception-management/SKILL.md b/skills/logistics-exception-management/SKILL.md
new file mode 100644
index 00000000..c24f262e
--- /dev/null
+++ b/skills/logistics-exception-management/SKILL.md
@@ -0,0 +1,217 @@
+---
+name: logistics-exception-management
+description: >
+ Codified expertise for handling freight exceptions, shipment delays,
+ damages, losses, and carrier disputes. Informed by logistics professionals
+ with 15+ years operational experience. Includes escalation protocols,
+ carrier-specific behaviours, claims procedures, and judgment frameworks.
+ Use when handling shipping exceptions, freight claims, delivery issues,
+ or carrier disputes.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "📦"
+---
+
+## When to Use
+
+Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.
+
+# Logistics Exception Management
+
+## Role and Context
+
+You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.
+
+## Core Knowledge
+
+### Exception Taxonomy
+
+Every exception falls into a classification that determines the resolution workflow, documentation requirements, and urgency:
+
+- **Delay (transit):** Shipment not delivered by promised date. Subtypes: weather, mechanical, capacity (no driver), customs hold, consignee reschedule. Most common exception type (~40% of all exceptions). Resolution hinges on whether delay is carrier-fault or force majeure.
+- **Damage (visible):** Noted on POD at delivery. Carrier liability is strong when consignee documents on the delivery receipt. Photograph immediately. Never accept "driver left before we could inspect."
+- **Damage (concealed):** Discovered after delivery, not noted on POD. Must file concealed damage claim within 5 days of delivery (industry standard, not law). Burden of proof shifts to shipper. Carrier will challenge — you need packaging integrity evidence.
+- **Damage (temperature):** Reefer/temperature-controlled failure. Requires continuous temp recorder data (Sensitech, Emerson). Pre-trip inspection records are critical. Carriers will claim "product was loaded warm."
+- **Shortage:** Piece count discrepancy at delivery. Count at the tailgate — never sign clean BOL if count is off. Distinguish driver count vs warehouse count conflicts. OS&D (Over, Short & Damage) report required.
+- **Overage:** More product delivered than on BOL. Often indicates cross-shipment from another consignee. Trace the extra freight — somebody is short.
+- **Refused delivery:** Consignee rejects. Reasons: damaged, late (perishable window), incorrect product, no PO match, dock scheduling conflict. Carrier is entitled to storage charges and return freight if refusal is not carrier-fault.
+- **Misdelivered:** Delivered to wrong address or wrong consignee. Full carrier liability. Time-critical to recover — product deteriorates or gets consumed.
+- **Lost (full shipment):** No delivery, no scan activity. Trigger trace at 24 hours past ETA for FTL, 48 hours for LTL. File formal tracer with carrier OS&D department.
+- **Lost (partial):** Some items missing from shipment. Often happens at LTL terminals during cross-dock handling. Serial number tracking critical for high-value.
+- **Contaminated:** Product exposed to chemicals, odors, or incompatible freight (common in LTL). Regulatory implications for food and pharma.
+
+### Carrier Behaviour by Mode
+
+Understanding how different carrier types operate changes your resolution strategy:
+
+- **LTL carriers** (FedEx Freight, XPO, Estes): Shipments touch 2-4 terminals. Each touch = damage risk. Claims departments are large and process-driven. Expect 30-60 day claim resolution. Terminal managers have authority up to ~$2,500.
+- **FTL/truckload** (asset carriers + brokers): Single-driver, dock-to-dock. Damage is usually loading/unloading. Brokers add a layer — the broker's carrier may go dark. Always get the actual carrier's MC number.
+- **Parcel** (UPS, FedEx, USPS): Automated claims portals. Strict documentation requirements. Declared value matters — default liability is very low ($100 for UPS). Must purchase additional coverage at shipping.
+- **Intermodal** (rail + drayage): Multiple handoffs. Damage often occurs during rail transit (impact events) or chassis swap. Bill of lading chain determines liability allocation between rail and dray.
+- **Ocean** (container shipping): Governed by Hague-Visby or COGSA (US). Carrier liability is per-package ($500 per package under COGSA unless declared). Container seal integrity is everything. Surveyor inspection at destination port.
+- **Air freight:** Governed by Montreal Convention. Strict 14-day notice for damage, 21 days for delay. Weight-based liability limits unless value declared. Fastest claims resolution of all modes.
+
+### Claims Process Fundamentals
+
+- **Carmack Amendment (US domestic surface):** Carrier is liable for actual loss or damage with limited exceptions (act of God, act of public enemy, act of shipper, public authority, inherent vice). Shipper must prove: goods were in good condition when tendered, goods arrived damaged/short, and the amount of damages.
+- **Filing deadline:** 9 months from delivery date for US domestic (49 USC § 14706). Miss this and the claim is time-barred regardless of merit.
+- **Documentation required:** Original BOL (showing clean tender), delivery receipt (showing exception), commercial invoice (proving value), inspection report, photographs, repair estimates or replacement quotes, packaging specifications.
+- **Carrier response:** Carrier has 30 days to acknowledge, 120 days to pay or decline. If they decline, you have 2 years from the decline date to file suit.
+
+### Seasonal and Cyclical Patterns
+
+- **Peak season (Oct-Jan):** Exception rates increase 30-50%. Carrier networks are strained. Transit times extend. Claims departments slow down. Build buffer into commitments.
+- **Produce season (Apr-Sep):** Temperature exceptions spike. Reefer availability tightens. Pre-cooling compliance becomes critical.
+- **Hurricane season (Jun-Nov):** Gulf and East Coast disruptions. Force majeure claims increase. Rerouting decisions needed within 4-6 hours of storm track updates.
+- **Month/quarter end:** Shippers rush volume. Carrier tender rejections spike. Double-brokering increases. Quality suffers across the board.
+- **Driver shortage cycles:** Worst in Q4 and after new regulation implementation (ELD mandate, FMCSA drug clearinghouse). Spot rates spike, service drops.
+
+### Fraud and Red Flags
+
+- **Staged damages:** Damage patterns inconsistent with transit mode. Multiple claims from same consignee location.
+- **Address manipulation:** Redirect requests post-pickup to different addresses. Common in high-value electronics.
+- **Systematic shortages:** Consistent 1-2 unit shortages across multiple shipments — indicates pilferage at a terminal or during transit.
+- **Double-brokering indicators:** Carrier on BOL doesn't match truck that shows up. Driver can't name their dispatcher. Insurance certificate is from a different entity.
+
+## Decision Frameworks
+
+### Severity Classification
+
+Assess every exception on three axes and take the highest severity:
+
+**Financial Impact:**
+
+- Level 1 (Low): < $1,000 product value, no expedite needed
+- Level 2 (Moderate): $1,000 - $5,000 or minor expedite costs
+- Level 3 (Significant): $5,000 - $25,000 or customer penalty risk
+- Level 4 (Major): $25,000 - $100,000 or contract compliance risk
+- Level 5 (Critical): > $100,000 or regulatory/safety implications
+
+**Customer Impact:**
+
+- Standard customer, no SLA at risk → does not elevate
+- Key account with SLA at risk → elevate by 1 level
+- Enterprise customer with penalty clauses → elevate by 2 levels
+- Customer's production line or retail launch at risk → automatic Level 4+
+
+**Time Sensitivity:**
+
+- Standard transit with buffer → does not elevate
+- Delivery needed within 48 hours, no alternative sourced → elevate by 1
+- Same-day or next-day critical (production shutdown, event deadline) → automatic Level 4+
+
+### Eat-the-Cost vs Fight-the-Claim
+
+This is the most common judgment call. Thresholds:
+
+- **< $500 and carrier relationship is strong:** Absorb. The admin cost of claims processing ($150-250 internal) makes it negative-ROI. Log for carrier scorecard.
+- **$500 - $2,500:** File claim but don't escalate aggressively. This is the "standard process" zone. Accept partial settlements above 70% of value.
+- **$2,500 - $10,000:** Full claims process. Escalate at 30-day mark if no resolution. Involve carrier account manager. Reject settlements below 80%.
+- **> $10,000:** VP-level awareness. Dedicated claims handler. Independent inspection if damage. Reject settlements below 90%. Legal review if denied.
+- **Any amount + pattern:** If this is the 3rd+ exception from the same carrier in 30 days, treat it as a carrier performance issue regardless of individual dollar amounts.
+
+### Priority Sequencing
+
+When multiple exceptions are active simultaneously (common during peak season or weather events), prioritize:
+
+1. Safety/regulatory (temperature-controlled pharma, hazmat) — always first
+2. Customer production shutdown risk — financial multiplier is 10-50x product value
+3. Perishable with remaining shelf life < 48 hours
+4. Highest financial impact adjusted for customer tier
+5. Oldest unresolved exception (prevent aging beyond SLA)
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Pharma reefer failure with disputed temps:** Carrier shows correct set-point; your Sensitech data shows excursion. The dispute is about sensor placement and pre-cooling. Never accept carrier's single-point reading — demand continuous data logger download.
+
+2. **Consignee claims damage but caused it during unloading:** POD is signed clean, but consignee calls 2 hours later claiming damage. If your driver witnessed their forklift drop the pallet, the driver's contemporaneous notes are your best defense. Without that, concealed damage claim against you is likely.
+
+3. **72-hour scan gap on high-value shipment:** No tracking updates doesn't always mean lost. LTL scan gaps happen at busy terminals. Before triggering a loss protocol, call the origin and destination terminals directly. Ask for physical trailer/bay location.
+
+4. **Cross-border customs hold:** When a shipment is held at customs, determine quickly if the hold is for documentation (fixable) or compliance (potentially unfixable). Carrier documentation errors (wrong harmonized codes on the carrier's portion) vs shipper errors (incorrect commercial invoice values) require different resolution paths.
+
+5. **Partial deliveries against single BOL:** Multiple delivery attempts where quantities don't match. Maintain a running tally. Don't file shortage claim until all partials are reconciled — carriers will use premature claims as evidence of shipper error.
+
+6. **Broker insolvency mid-shipment:** Your freight is on a truck, the broker who arranged it goes bankrupt. The actual carrier has a lien right. Determine quickly: is the carrier paid? If not, negotiate directly with the carrier for release.
+
+7. **Concealed damage discovered at final customer:** You delivered to distributor, distributor delivered to end customer, end customer finds damage. The chain-of-custody documentation determines who bears the loss.
+
+8. **Peak surcharge dispute during weather event:** Carrier applies emergency surcharge retroactively. Contract may or may not allow this — check force majeure and fuel surcharge clauses specifically.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to situation severity and relationship:
+
+- **Routine exception, good carrier relationship:** Collaborative. "We've got a delay on PRO# X — can you get me an updated ETA? Customer is asking."
+- **Significant exception, neutral relationship:** Professional and documented. State facts, reference BOL/PRO, specify what you need and by when.
+- **Major exception or pattern, strained relationship:** Formal. CC management. Reference contract terms. Set response deadlines. "Per Section 4.2 of our transportation agreement dated..."
+- **Customer-facing (delay):** Proactive, honest, solution-oriented. Never blame the carrier by name. "Your shipment has experienced a transit delay. Here's what we're doing and your updated timeline."
+- **Customer-facing (damage/loss):** Empathetic, action-oriented. Lead with the resolution, not the problem. "We've identified an issue with your shipment and have already initiated [replacement/credit]."
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**Initial carrier inquiry:** Subject: `Exception Notice — PRO# {pro} / BOL# {bol}`. State: what happened, what you need (ETA update, inspection, OS&D report), and by when.
+
+**Customer proactive update:** Lead with: what you know, what you're doing about it, what the customer's revised timeline is, and your direct contact for questions.
+
+**Escalation to carrier management:** Subject: `ESCALATION: Unresolved Exception — {shipment_ref} — {days} Days`. Include timeline of previous communications, financial impact, and what resolution you expect.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------ | ---------------------------------------------- | ----------------- |
+| Exception value > $25,000 | Notify VP Supply Chain immediately | Within 1 hour |
+| Enterprise customer affected | Assign dedicated handler, notify account team | Within 2 hours |
+| Carrier non-response | Escalate to carrier account manager | After 4 hours |
+| Repeated carrier (3+ in 30 days) | Carrier performance review with procurement | Within 1 week |
+| Potential fraud indicators | Notify compliance and halt standard processing | Immediately |
+| Temperature excursion on regulated product | Notify quality/regulatory team | Within 30 minutes |
+| No scan update on high-value (> $50K) | Initiate trace protocol and notify security | After 24 hours |
+| Claims denied > $10,000 | Legal review of denial basis | Within 48 hours |
+
+### Escalation Chain
+
+Level 1 (Analyst) → Level 2 (Team Lead, 4 hours) → Level 3 (Manager, 24 hours) → Level 4 (Director, 48 hours) → Level 5 (VP, 72+ hours or any Level 5 severity)
+
+## Performance Indicators
+
+Track these metrics weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| -------------------------------------- | ------------------- | ------------- |
+| Mean resolution time | < 72 hours | > 120 hours |
+| First-contact resolution rate | > 40% | < 25% |
+| Financial recovery rate (claims) | > 75% | < 50% |
+| Customer satisfaction (post-exception) | > 4.0/5.0 | < 3.5/5.0 |
+| Exception rate (per 1,000 shipments) | < 25 | > 40 |
+| Claims filing timeliness | 100% within 30 days | Any > 60 days |
+| Repeat exceptions (same carrier/lane) | < 10% | > 20% |
+| Aged exceptions (> 30 days open) | < 5% of total | > 15% |
+
+## Additional Resources
+
+- For detailed decision frameworks, escalation matrices, and mode-specific workflows, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **triage and resolve logistics exceptions or design exception-handling playbooks**:
+
+- Handling delays, damages, shortages, misdeliveries, and claims across LTL, FTL, parcel, intermodal, ocean, or air.
+- Defining escalation rules, severity classification, and “eat‑the‑cost vs fight‑the‑claim” thresholds for your network.
+- Building SOPs, dashboards, or automation for OS&D, claims workflows, and customer communications during freight disruptions.
diff --git a/skills/logistics-exception-management/references/communication-templates.md b/skills/logistics-exception-management/references/communication-templates.md
new file mode 100644
index 00000000..99726782
--- /dev/null
+++ b/skills/logistics-exception-management/references/communication-templates.md
@@ -0,0 +1,1170 @@
+# Communication Templates — Logistics Exception Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing exception communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and escalation stage. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Initial Exception Notification to Carrier (Standard)](#1-initial-exception-notification-to-carrier-standard)
+2. [Initial Exception Notification to Carrier (Urgent)](#2-initial-exception-notification-to-carrier-urgent)
+3. [Customer Proactive Update — Delay](#3-customer-proactive-update--delay)
+4. [Customer Proactive Update — Damage](#4-customer-proactive-update--damage)
+5. [Customer Proactive Update — Loss](#5-customer-proactive-update--loss)
+6. [Escalation to Carrier Account Manager](#6-escalation-to-carrier-account-manager)
+7. [Escalation to Carrier VP/Director](#7-escalation-to-carrier-vpdirector)
+8. [Internal Escalation to VP Supply Chain](#8-internal-escalation-to-vp-supply-chain)
+9. [Claims Filing Cover Letter](#9-claims-filing-cover-letter)
+10. [Settlement Negotiation Response (Accepting)](#10-settlement-negotiation-response-accepting)
+11. [Settlement Negotiation Response (Rejecting)](#11-settlement-negotiation-response-rejecting)
+12. [Post-Resolution Summary](#12-post-resolution-summary)
+13. [Carrier Performance Warning](#13-carrier-performance-warning)
+14. [Customer Apology with Resolution](#14-customer-apology-with-resolution)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{pro_number}}` | Carrier PRO / tracking number | `PRO 1234-5678-90` |
+| `{{bol_number}}` | Bill of Lading number | `BOL-2025-04872` |
+| `{{po_number}}` | Customer purchase order number | `PO-88431` |
+| `{{shipment_id}}` | Internal shipment reference | `SHP-2025-11049` |
+| `{{carrier_name}}` | Carrier legal or DBA name | `Acme Freight, Inc.` |
+| `{{carrier_mc}}` | Carrier MC/DOT number | `MC-345678` |
+| `{{carrier_scac}}` | Carrier SCAC code | `ACMF` |
+| `{{origin_city_state}}` | Origin city and state | `Dallas, TX` |
+| `{{dest_city_state}}` | Destination city and state | `Columbus, OH` |
+| `{{ship_date}}` | Original ship date | `2025-09-14` |
+| `{{original_eta}}` | Original estimated delivery | `2025-09-17` |
+| `{{revised_eta}}` | Revised estimated delivery | `2025-09-19` |
+| `{{customer_name}}` | Customer company name | `Midwest Distribution Co.` |
+| `{{customer_contact}}` | Customer contact name | `Sarah Chen` |
+| `{{our_contact_name}}` | Our representative name | `James Petrovic` |
+| `{{our_contact_title}}` | Our representative title | `Transportation Manager` |
+| `{{our_contact_email}}` | Our representative email | `jpetrovic@company.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(312) 555-0147` |
+| `{{our_company}}` | Our company name | `Consolidated Shippers LLC` |
+| `{{exception_date}}` | Date exception was identified | `2025-09-16` |
+| `{{commodity}}` | Freight commodity description | `Automotive brake assemblies` |
+| `{{weight}}` | Shipment weight | `12,400 lbs` |
+| `{{piece_count}}` | Piece/pallet count | `14 pallets` |
+| `{{freight_charge}}` | Freight charge amount | `$3,840.00` |
+| `{{cargo_value}}` | Declared cargo value | `$47,200.00` |
+| `{{claim_amount}}` | Claim dollar amount | `$47,200.00` |
+| `{{claim_number}}` | Carrier-assigned claim number | `CLM-2025-0398` |
+| `{{our_claim_ref}}` | Internal claim reference | `EXC-2025-1104` |
+| `{{deadline_date}}` | Response or action deadline | `2025-09-18 by 14:00 CT` |
+| `{{days_in_transit}}` | Days shipment has been moving | `5` |
+| `{{last_known_location}}` | Last scan or check-call location | `Indianapolis, IN terminal` |
+
+---
+
+## 1. Initial Exception Notification to Carrier (Standard)
+
+### When to Use
+- Exception identified through tracking, check-call miss, or OS&D report.
+- Severity is moderate — the shipment is delayed or has a discrepancy but is not in immediate jeopardy.
+- First outreach to carrier operations or dispatch regarding this specific issue.
+
+### Tone Guidance
+Keep this factual and collaborative. You are a professional notifying a partner of a discrepancy, not accusing anyone of failure. Assume good intent — the goal is to get information and a corrective plan, not to assign blame at this stage.
+
+### What NOT to Say
+- Do not threaten claims or contract consequences in the first contact.
+- Do not speculate on what caused the exception.
+- Do not use language like "you failed to" or "your driver caused" — you do not yet have confirmed root cause.
+- Do not copy the customer on carrier operational communications.
+
+### Subject Line
+
+```
+Exception Notice — PRO {{pro_number}} | {{origin_city_state}} to {{dest_city_state}} | BOL {{bol_number}}
+```
+
+### Body
+
+```
+Team,
+
+We are writing regarding a shipment exception on the following load:
+
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+ Commodity: {{commodity}}
+ Weight/Count: {{weight}} / {{piece_count}}
+
+EXCEPTION DETAILS:
+{{exception_description}}
+
+We identified this exception on {{exception_date}} at approximately {{exception_time}}.
+The last confirmed status was {{last_known_status}} at {{last_known_location}} on
+{{last_scan_date}}.
+
+We need the following from your team:
+
+ 1. Current physical location of the freight
+ 2. Updated ETA to the consignee
+ 3. Root cause of the delay or discrepancy
+ 4. Corrective action being taken
+
+Please respond by {{deadline_date}} so we can update our customer accordingly.
+
+If you have questions or need additional shipment details, contact me directly at
+{{our_contact_phone}} or {{our_contact_email}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}}
+```
+
+---
+
+## 2. Initial Exception Notification to Carrier (Urgent)
+
+### When to Use
+- Shipment is critical: production-down, store-opening, perishable, or high-value.
+- Exception creates immediate financial exposure (e.g., production line stoppage, contract penalty window).
+- Customer has already escalated or SLA breach is imminent (within 24 hours).
+
+### Tone Guidance
+Direct and time-bound. This is not hostile, but it communicates that the situation requires immediate action, not a callback tomorrow. Every sentence should drive toward a concrete next step. Use specific deadlines, not "as soon as possible."
+
+### What NOT to Say
+- Do not soften the urgency — "when you get a chance" undermines the entire message.
+- Do not issue ultimatums you cannot enforce at this stage.
+- Do not reference other shipments or unrelated performance issues — stay on this load.
+- Do not leave out the financial exposure figure; it justifies the urgency.
+
+### Subject Line
+
+```
+URGENT — Immediate Response Required | PRO {{pro_number}} | {{dest_city_state}} | ETA Miss
+```
+
+### Body
+
+```
+URGENT — IMMEDIATE RESPONSE REQUIRED
+
+This shipment requires your immediate attention. We need a substantive response
+by {{deadline_date}} — not an acknowledgment, but confirmed status and a recovery plan.
+
+SHIPMENT DETAILS:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+ Commodity: {{commodity}}
+ Weight/Count: {{weight}} / {{piece_count}}
+ Declared Value: {{cargo_value}}
+
+EXCEPTION:
+{{exception_description}}
+
+BUSINESS IMPACT:
+{{business_impact_description}}
+
+Estimated financial exposure if not resolved by {{resolution_deadline}}: {{financial_exposure}}.
+
+REQUIRED BY {{deadline_date}}:
+ 1. Confirmed physical location of the freight — verified, not last-scan
+ 2. Firm revised delivery date and time
+ 3. Name and direct phone number of the person managing recovery
+ 4. Written recovery plan
+
+If I do not have a response by the deadline above, I will escalate to your account
+management team and begin contingency planning, which may include diversion or
+re-tender.
+
+Contact me directly:
+{{our_contact_name}} | {{our_contact_phone}} | {{our_contact_email}}
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+```
+
+---
+
+## 3. Customer Proactive Update — Delay
+
+### When to Use
+- Transit delay confirmed or highly probable (revised ETA is beyond the committed window).
+- Send this before the customer discovers the delay on their own. Proactive communication preserves trust; reactive communication erodes it.
+- You have a revised ETA — even if approximate. If you have no ETA at all, say so and commit to a follow-up time.
+
+### Tone Guidance
+Honest and solution-forward. Acknowledge the delay plainly — do not bury it in qualifiers. Lead with the revised timeline, then explain briefly. The customer wants to know "when will I get my freight" before they want to know "what happened." Do not name the carrier or assign blame to any specific party.
+
+### What NOT to Say
+- Do not blame the carrier by name — say "our carrier partner," not "XYZ Trucking messed up."
+- Do not say "unforeseen circumstances" — be specific about the cause category (weather, equipment, routing).
+- Do not promise a revised ETA you cannot support. If uncertain, give a range.
+- Do not use "we apologize for any inconvenience" — it reads as form language. Be specific about the impact you understand.
+
+### Subject Line
+
+```
+Shipment Update — PO {{po_number}} | Revised ETA {{revised_eta}}
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I want to update you on PO {{po_number}} (our reference {{shipment_id}}) shipping
+from {{origin_city_state}} to {{dest_city_state}}.
+
+This shipment is experiencing a transit delay. The original estimated delivery was
+{{original_eta}}. Based on current status, the revised delivery estimate is
+{{revised_eta}}.
+
+CAUSE: {{delay_cause_customer_facing}}
+
+HERE IS WHAT WE ARE DOING:
+ - {{action_item_1}}
+ - {{action_item_2}}
+ - {{action_item_3}}
+
+I will send you another update by {{next_update_time}} with confirmed delivery
+details. If the timeline shifts further in either direction, you will hear from me
+immediately.
+
+If this delay impacts your operations and you need us to evaluate expedited
+alternatives, please let me know and I will have options to you within
+{{expedite_response_window}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+### Variant — Delay with No ETA Yet
+
+When you cannot provide a revised ETA, replace the ETA section:
+
+```
+This shipment is experiencing a transit delay. The original estimated delivery was
+{{original_eta}}. We do not yet have a confirmed revised delivery time, but I am
+working to get one and will update you by {{next_update_time}} today.
+```
+
+---
+
+## 4. Customer Proactive Update — Damage
+
+### When to Use
+- Carrier or consignee has reported visible damage at delivery or in transit.
+- Damage is confirmed or strongly suspected (e.g., photos from driver, consignee notation on POD).
+- Send before the customer calls you. If they are the consignee, send before they have to chase you for next steps.
+
+### Tone Guidance
+Lead with the resolution, not the problem. The customer's first question is "what are you going to do about it" — answer that before describing the damage. Be specific about the remediation path (replacement, credit, re-ship) and timeline. Express genuine concern for the business impact without being dramatic.
+
+### What NOT to Say
+- Do not lead with the damage description. The opening paragraph should be about the resolution path.
+- Do not say "these things happen in transit" — it minimizes the customer's loss.
+- Do not speculate on cause (packaging, handling, weather) until investigation is complete.
+- Do not ask the customer to file a claim — that is your job.
+
+### Subject Line
+
+```
+PO {{po_number}} — Delivery Update and Resolution Plan
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I am reaching out regarding PO {{po_number}} (our reference {{shipment_id}})
+delivered to {{dest_city_state}} on {{delivery_date}}.
+
+We have identified damage to a portion of this shipment and I want to walk you
+through the resolution we are putting in place.
+
+RESOLUTION:
+ {{resolution_description}}
+
+ Timeline: {{resolution_timeline}}
+
+DAMAGE DETAILS:
+ Items Affected: {{damaged_items_description}}
+ Extent: {{damage_extent}}
+ Pieces Affected: {{damaged_piece_count}} of {{piece_count}} total
+
+We are handling the carrier claim and investigation on our end — no action is
+needed from your team on that front.
+
+What we do need from you:
+ - Confirmation of the affected quantities once your receiving team completes
+ inspection
+ - Direction on whether you want us to {{resolution_option_a}} or
+ {{resolution_option_b}}
+
+I understand this impacts your {{customer_impact_area}} and I take that seriously.
+I will stay on this personally until it is fully resolved.
+
+Next update from me: {{next_update_time}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 5. Customer Proactive Update — Loss
+
+### When to Use
+- Shipment is confirmed lost — not just delayed or unlocated. A shipment is "lost" when the carrier has confirmed they cannot locate the freight after a thorough trace, OR when {{days_without_scan}} days have passed with no carrier response to trace requests.
+- This is the most sensitive exception communication. The customer is learning that their goods are gone. Do not send this template for a shipment that is merely late or temporarily unlocated.
+
+### Tone Guidance
+Empathetic, direct, and action-oriented. Do not hedge or use passive constructions — "your shipment has been lost" is clearer than "there appears to be a situation involving the non-delivery of your order." Immediately establish the action plan. The customer needs to know three things: (1) what happened, (2) what you are doing right now, and (3) when they will have resolution. Convey that you understand the severity.
+
+### What NOT to Say
+- Do not say "misplaced" or "misrouted" if the shipment is confirmed lost — it sounds like you are minimizing.
+- Do not say "we are still looking into it" without a concrete next step and deadline.
+- Do not blame the carrier by name.
+- Do not lead with the claims process — lead with the replacement or remediation plan. The customer needs their goods, not a claims education.
+- Do not use "unfortunately" more than once.
+
+### Subject Line
+
+```
+PO {{po_number}} — Shipment Status and Immediate Action Plan
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I need to share a difficult update on PO {{po_number}} (our reference
+{{shipment_id}}), originally shipping {{origin_city_state}} to
+{{dest_city_state}} on {{ship_date}}.
+
+After an extensive trace with our carrier partner, we have confirmed that this
+shipment — {{piece_count}} of {{commodity}}, valued at {{cargo_value}} — has
+been lost in transit. I know this creates a real problem for your team and I want
+to lay out exactly what we are doing about it.
+
+IMMEDIATE ACTION PLAN:
+
+ 1. REPLACEMENT / RE-SHIP:
+ {{replacement_plan}}
+ Expected availability: {{replacement_date}}
+
+ 2. FINANCIAL REMEDIATION:
+ {{financial_remediation_plan}}
+ Timeline: {{financial_remediation_timeline}}
+
+ 3. CARRIER CLAIM:
+ We have filed a formal cargo claim against the carrier. This is our
+ responsibility to manage — you do not need to take any action on the
+ claim.
+ Claim reference: {{our_claim_ref}}
+
+ 4. PREVENTION:
+ {{prevention_steps}}
+
+I will call you at {{follow_up_call_time}} to discuss this directly and answer
+any questions. If you need to reach me before then, my cell is
+{{our_contact_phone}}.
+
+I take full ownership of making this right.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 6. Escalation to Carrier Account Manager
+
+### When to Use
+- Initial contact to carrier dispatch or operations has gone unanswered for 4+ hours on a standard exception, or 2+ hours on an urgent exception.
+- You have documented at least two prior outreach attempts (email, phone, or both) to the frontline contact.
+- The account manager is the next level of the carrier's organization who can apply internal pressure.
+
+### Tone Guidance
+Professional but firm. You are not angry — you are a business partner whose reasonable requests have been ignored, and you need the account manager to intervene. State the timeline of your attempts factually. Make the ask concrete. The account manager needs to know exactly what you need and by when so they can push their operations team.
+
+### What NOT to Say
+- Do not trash the frontline contact by name — say "your operations team" or "your dispatch."
+- Do not threaten to pull freight at this stage unless you mean it and have authority.
+- Do not pile on unrelated issues — stay on this shipment.
+
+### Subject Line
+
+```
+Escalation — No Response on PRO {{pro_number}} | Requires Your Intervention
+```
+
+### Body
+
+```
+{{carrier_account_manager_name}},
+
+I am escalating to you because I have been unable to get a substantive response
+from your operations team on a shipment exception that requires immediate
+attention.
+
+SHIPMENT:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+
+EXCEPTION:
+{{exception_description}}
+
+OUTREACH TIMELINE:
+ {{attempt_1_date_time}} — {{attempt_1_method}}: {{attempt_1_summary}}
+ {{attempt_2_date_time}} — {{attempt_2_method}}: {{attempt_2_summary}}
+ {{attempt_3_date_time}} — {{attempt_3_method}}: {{attempt_3_summary}}
+
+It has been {{hours_since_first_contact}} hours since our first outreach with no
+confirmed status or recovery plan.
+
+I need the following by {{deadline_date}}:
+ 1. Confirmed current location of the freight
+ 2. Firm revised ETA
+ 3. A direct contact managing the recovery who I can reach by phone
+
+My customer is waiting on this update and I cannot continue to respond with "we
+are working on it" without specifics.
+
+Please call me at {{our_contact_phone}} or reply to this email by the deadline
+above.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 7. Escalation to Carrier VP/Director
+
+### When to Use
+- Account manager has failed to resolve or respond within a reasonable window (typically 12–24 hours after account manager escalation).
+- The exception has significant financial exposure, or a pattern of similar failures exists.
+- You are prepared to reference contract terms, volume commitments, or documented performance history.
+- This is a formal escalation — send it knowing it may be shared with carrier executive leadership.
+
+### Tone Guidance
+Formal and data-driven. This is a business communication between senior professionals. No emotion, no sarcasm, no threats — but clear consequences stated as business realities. Reference specific contract provisions, dollar figures, and incident history. The VP needs to understand that this is not a one-off complaint; it is a business risk they need to manage.
+
+### What NOT to Say
+- Do not be sarcastic or condescending — "I'm sure you're very busy" undermines your credibility.
+- Do not make threats you cannot follow through on (e.g., "we will never use you again" when they are your only option for a lane).
+- Do not reference verbal promises or informal agreements — stick to what is documented.
+- Do not CC your customer. This is a carrier management conversation.
+
+### Subject Line
+
+```
+Executive Escalation — Unresolved Exception PRO {{pro_number}} | {{our_company}} Account
+```
+
+### Body
+
+```
+{{carrier_vp_name}},
+{{carrier_vp_title}}
+{{carrier_name}}
+
+I am writing to escalate a shipment exception that has not been resolved despite
+repeated engagement with your operations and account management teams.
+
+SHIPMENT DETAILS:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Commodity: {{commodity}}
+ Shipment Value: {{cargo_value}}
+
+EXCEPTION SUMMARY:
+{{exception_description}}
+
+ESCALATION HISTORY:
+ {{escalation_timeline_summary}}
+
+ Total time without resolution: {{total_hours_unresolved}} hours.
+
+FINANCIAL EXPOSURE:
+ Direct cargo exposure: {{cargo_value}}
+ Customer penalty risk: {{customer_penalty_amount}}
+ Expedite/recovery costs: {{recovery_cost_estimate}}
+ Total potential exposure: {{total_financial_exposure}}
+
+CONTRACT REFERENCE:
+Per Section {{contract_section}} of our transportation agreement dated
+{{contract_date}}, {{relevant_contract_provision}}.
+
+{{#if pattern_exists}}
+PERFORMANCE PATTERN:
+This is not an isolated incident. Over the past {{pattern_period}}, we have
+logged {{incident_count}} exceptions on your loads, resulting in
+{{total_pattern_cost}} in direct costs. Specific incidents:
+ {{pattern_incident_list}}
+{{/if}}
+
+I need the following from your team by {{deadline_date}}:
+ 1. Full resolution of this specific shipment
+ 2. Written root cause analysis
+ 3. Corrective action plan to prevent recurrence
+
+I value the partnership between {{our_company}} and {{carrier_name}}, and I want
+to resolve this collaboratively. However, continued non-responsiveness will
+require us to reassess our routing and volume commitments on the
+{{origin_city_state}}–{{dest_city_state}} lane.
+
+I am available to discuss at {{our_contact_phone}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 8. Internal Escalation to VP Supply Chain
+
+### When to Use
+- Financial exposure exceeds your authority threshold (typically $25,000+ or customer-specific triggers).
+- Customer relationship is at risk and executive-to-executive communication may be required.
+- A decision is needed that is above your pay grade: re-tender, expedite at premium cost, authorize production-down recovery, or waive contractual terms.
+- You need VP awareness even if you do not need VP action — significant exceptions should not be surprises.
+
+### Tone Guidance
+Brief and structured. Your VP does not need the narrative — they need the numbers, the exposure, what you have already done, and what you need from them. Lead with the decision or awareness item. Use bullet points. This is an internal operational brief, not a customer communication.
+
+### What NOT to Say
+- Do not editorialize — "the carrier is terrible" adds nothing. State the facts.
+- Do not bury the financial number. It should be in the first three lines.
+- Do not present problems without proposed solutions.
+- Do not send this without having already exhausted the escalation steps within your authority.
+
+### Subject Line
+
+```
+[ACTION REQUIRED] Exception — {{customer_name}} PO {{po_number}} | ${{financial_exposure}} Exposure
+```
+
+### Body
+
+```
+{{vp_name}},
+
+Flagging an active exception that requires {{your_awareness / your_decision}}.
+
+BOTTOM LINE:
+ Customer: {{customer_name}}
+ Shipment: PO {{po_number}} / PRO {{pro_number}}
+ Exception Type: {{exception_type}}
+ Financial Exposure: ${{financial_exposure}}
+ Customer Risk: {{customer_risk_level}} — {{customer_risk_description}}
+
+SITUATION:
+ {{two_to_three_sentence_summary}}
+
+WHAT I HAVE DONE:
+ - {{action_taken_1}}
+ - {{action_taken_2}}
+ - {{action_taken_3}}
+
+WHAT I NEED FROM YOU:
+ {{decision_or_action_needed}}
+
+ Options:
+ A. {{option_a}} — Cost: ${{option_a_cost}} | Timeline: {{option_a_timeline}}
+ B. {{option_b}} — Cost: ${{option_b_cost}} | Timeline: {{option_b_timeline}}
+
+ My recommendation: Option {{recommended_option}} because {{rationale}}.
+
+I need a decision by {{decision_deadline}} to execute the recovery plan.
+
+—{{our_contact_name}}
+```
+
+---
+
+## 9. Claims Filing Cover Letter
+
+### When to Use
+- Decision has been made to file a formal freight claim against the carrier.
+- All supporting documentation has been gathered (BOL, POD, inspection reports, photos, invoice, packing list).
+- Claim is being sent within the filing window (9 months under Carmack Amendment for interstate; check state law or contract for intrastate or brokered freight).
+
+### Tone Guidance
+Formal and precise. This is a legal document. No emotion, no narrative, no relationship language. State the facts, cite the applicable law, list the enclosed documents, and demand payment. Every statement should be supportable with evidence. Use the carrier's legal name and MC number, not their DBA or sales contact's name.
+
+### What NOT to Say
+- Do not editorialize about the carrier's service or your frustration.
+- Do not include demands beyond the provable loss amount — consequential damages require separate analysis and legal review.
+- Do not omit the filing date or claim amount — these are jurisdictional requirements.
+- Do not reference settlement discussions or verbal admissions of fault.
+
+### Subject Line
+
+```
+Formal Freight Claim — PRO {{pro_number}} | Claim Amount: ${{claim_amount}}
+```
+
+### Body
+
+```
+ {{current_date}}
+
+VIA EMAIL AND CERTIFIED MAIL
+
+{{carrier_legal_name}}
+{{carrier_claims_address}}
+MC-{{carrier_mc}} / DOT-{{carrier_dot}}
+
+Attn: Claims Department
+
+RE: Formal Freight Claim
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Ship Date: {{ship_date}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Our Reference: {{our_claim_ref}}
+ Claim Amount: ${{claim_amount}}
+
+Dear Claims Department:
+
+{{our_company}} hereby files this formal claim for {{claim_type}} against
+{{carrier_legal_name}} pursuant to the Carmack Amendment, 49 U.S.C. § 14706,
+and applicable regulations at 49 C.F.R. Part 370.
+
+FACTS:
+
+On {{ship_date}}, {{our_company}} tendered {{piece_count}} of {{commodity}},
+weighing {{weight}}, to {{carrier_legal_name}} at {{origin_facility}},
+{{origin_city_state}}, for transportation to {{dest_facility}},
+{{dest_city_state}}, under BOL {{bol_number}}.
+
+{{claim_facts_paragraph}}
+
+CLAIMED AMOUNT:
+
+The total claimed amount is ${{claim_amount}}, computed as follows:
+
+ {{claim_calculation_line_items}}
+
+ Total: ${{claim_amount}}
+
+This amount represents the {{value_basis}} of the goods at the time and place
+of shipment, supported by the enclosed invoice documentation.
+
+ENCLOSED DOCUMENTATION:
+
+ 1. Bill of Lading (BOL {{bol_number}})
+ 2. Delivery receipt / Proof of Delivery with consignee notations
+ 3. {{inspection_report_description}}
+ 4. Photographs of {{photo_description}}
+ 5. Commercial invoice(s) — Invoice No. {{invoice_numbers}}
+ 6. Packing list
+ 7. Shipper's certificate of value / weight
+ {{#if additional_documents}}
+ 8. {{additional_documents}}
+ {{/if}}
+
+DEMAND:
+
+{{our_company}} demands payment of ${{claim_amount}} within thirty (30) days
+of receipt of this claim, per 49 C.F.R. § 370.9. In the alternative, we
+request written acknowledgment within thirty (30) days and final disposition
+within one hundred twenty (120) days, as required by regulation.
+
+Please direct all claim correspondence to:
+
+ {{our_contact_name}}
+ {{our_contact_title}}
+ {{our_company}}
+ {{our_claims_address}}
+ {{our_contact_email}}
+ {{our_contact_phone}}
+
+ Claim Reference: {{our_claim_ref}}
+
+{{our_company}} reserves all rights and remedies available under applicable
+law, including the right to pursue this claim in a court of competent
+jurisdiction if not resolved within the regulatory timeframe.
+
+Respectfully,
+
+
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+```
+
+---
+
+## 10. Settlement Negotiation Response (Accepting)
+
+### When to Use
+- Carrier has offered a settlement amount and you have decided to accept it.
+- The settlement amount has been approved internally (check your authority level — partial settlements often require management sign-off).
+- You are ready to close the claim and release the carrier from further liability on this shipment.
+
+### Tone Guidance
+Professional and conclusive. You are closing a business matter, not doing the carrier a favor. Confirm the exact terms clearly — amount, payment method, timeline, and scope of release. Do not express gratitude for the settlement or suggest the amount was generous. It is a business resolution.
+
+### What NOT to Say
+- Do not say "thank you for your generous offer" — you are accepting fair compensation, not a gift.
+- Do not leave any ambiguity about what is being released — specify the PRO, BOL, and claim reference.
+- Do not agree to confidentiality clauses or broad releases without legal review.
+- Do not accept verbally — always confirm in writing.
+
+### Subject Line
+
+```
+Claim Settlement Acceptance — PRO {{pro_number}} | Claim {{our_claim_ref}}
+```
+
+### Body
+
+```
+{{carrier_claims_contact}},
+
+This letter confirms {{our_company}}'s acceptance of the settlement offer
+received on {{offer_date}} regarding the following claim:
+
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Our Reference: {{our_claim_ref}}
+ Your Reference: {{claim_number}}
+
+SETTLEMENT TERMS:
+
+ Settlement Amount: ${{settlement_amount}}
+ Payment Method: {{payment_method}}
+ Payment Due: Within {{payment_days}} business days of this acceptance
+ Scope of Release: Full and final settlement of all claims arising from PRO
+ {{pro_number}} / BOL {{bol_number}} for the shipment of
+ {{commodity}} from {{origin_city_state}} to
+ {{dest_city_state}} on {{ship_date}}
+
+Upon receipt of ${{settlement_amount}}, {{our_company}} releases
+{{carrier_legal_name}} (MC-{{carrier_mc}}) from any further liability related
+to the above-referenced shipment.
+
+This release does not extend to any other shipments, claims, or obligations
+between the parties.
+
+Please remit payment to:
+
+ {{our_company}}
+ {{our_remittance_address}}
+ {{our_payment_details}}
+
+ Reference: {{our_claim_ref}}
+
+Please confirm receipt of this acceptance and expected payment date.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 11. Settlement Negotiation Response (Rejecting)
+
+### When to Use
+- Carrier's settlement offer is below your documented loss amount and you have evidence to support a higher claim.
+- You are prepared to counter-offer with a specific amount backed by documentation.
+- You have reviewed the carrier's stated basis for the reduced offer and can address their objections.
+
+### Tone Guidance
+Firm and evidence-based. You are not offended by a low offer — you are correcting an inaccurate valuation. Walk through their reasoning, point out where it is wrong, and anchor your counter to specific evidence. Keep the door open for resolution but make clear that the documented loss supports your position.
+
+### What NOT to Say
+- Do not say "this is insulting" or express emotion about the offer amount.
+- Do not threaten litigation in the same sentence as a counter-offer — it contradicts the settlement posture.
+- Do not accept their framing if it is incorrect (e.g., if they depreciated new goods or excluded documented items).
+- Do not counter without supporting documentation — attach the evidence.
+
+### Subject Line
+
+```
+Claim {{our_claim_ref}} — Settlement Offer Declined | Counter-Offer Enclosed
+```
+
+### Body
+
+```
+{{carrier_claims_contact}},
+
+We have reviewed your settlement offer of ${{offered_amount}} dated
+{{offer_date}} for the following claim:
+
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Our Reference: {{our_claim_ref}}
+ Your Reference: {{claim_number}}
+ Original Claim: ${{claim_amount}}
+
+We are unable to accept this offer. Our original claim of ${{claim_amount}} is
+supported by documented evidence, and the offered amount does not adequately
+compensate for the loss.
+
+RESPONSE TO YOUR STATED BASIS FOR REDUCTION:
+
+{{carrier_reduction_reason_1}}:
+ Our response: {{our_response_1}}
+ Supporting documentation: {{supporting_doc_1}}
+
+{{carrier_reduction_reason_2}}:
+ Our response: {{our_response_2}}
+ Supporting documentation: {{supporting_doc_2}}
+
+{{#if carrier_reduction_reason_3}}
+{{carrier_reduction_reason_3}}:
+ Our response: {{our_response_3}}
+ Supporting documentation: {{supporting_doc_3}}
+{{/if}}
+
+COUNTER-OFFER:
+
+{{our_company}} is willing to settle this claim for ${{counter_offer_amount}},
+which reflects {{counter_offer_basis}}.
+
+This counter-offer is supported by the following enclosed documentation:
+ {{counter_offer_documentation_list}}
+
+We request your response within {{response_days}} business days. We remain open
+to resolving this matter directly and would welcome a call to discuss if that
+would be productive.
+
+If we are unable to reach a fair resolution, we will need to evaluate our
+options under 49 U.S.C. § 14706, which provides a two-year statute of
+limitations from the date of claim denial.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 12. Post-Resolution Summary
+
+### When to Use
+- Exception has been fully resolved — freight delivered, claim settled, or loss remediated.
+- Distribute to internal stakeholders: operations, account management, finance, and carrier procurement.
+- This becomes the permanent record of the exception and feeds carrier scorecard reviews.
+
+### Tone Guidance
+Neutral and analytical. This is a post-mortem, not a complaint. State what happened, what it cost, what was done, and what should change. Be specific about lessons learned — vague statements like "we need to communicate better" are worthless. Recommend concrete process changes.
+
+### What NOT to Say
+- Do not assign personal blame to individuals — focus on process and system failures.
+- Do not omit the financial impact even if the claim was settled favorably — the true cost includes staff time, expedite charges, and customer goodwill.
+- Do not skip the "prevention" section. If you cannot recommend a prevention step, say so and explain why.
+
+### Subject Line
+
+```
+[CLOSED] Exception Summary — {{customer_name}} / PRO {{pro_number}} | {{exception_type}}
+```
+
+### Body
+
+```
+EXCEPTION POST-RESOLUTION SUMMARY
+====================================
+
+Exception Reference: {{our_claim_ref}}
+Status: CLOSED — {{closure_date}}
+Prepared by: {{our_contact_name}}
+Distribution: {{distribution_list}}
+
+1. SHIPMENT DETAILS
+ Customer: {{customer_name}}
+ PO: {{po_number}}
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ Carrier: {{carrier_name}} (MC-{{carrier_mc}} / SCAC: {{carrier_scac}})
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Commodity: {{commodity}}
+ Weight/Pieces: {{weight}} / {{piece_count}}
+
+2. EXCEPTION SUMMARY
+ Type: {{exception_type}}
+ Discovered: {{exception_date}}
+ Root Cause: {{confirmed_root_cause}}
+ Description: {{exception_narrative}}
+
+3. TIMELINE
+ {{exception_timeline}}
+
+4. FINANCIAL IMPACT
+ Cargo Loss/Damage: ${{cargo_loss_amount}}
+ Freight Charges (original): ${{freight_charge}}
+ Expedite / Recovery Costs: ${{recovery_costs}}
+ Customer Penalties / Credits: ${{customer_penalties}}
+ Internal Labor (est.): ${{internal_labor_cost}}
+ ─────────────────────────────────
+ Total Cost of Exception: ${{total_exception_cost}}
+
+ Claim Filed: ${{claim_amount}}
+ Settlement Received: ${{settlement_amount}}
+ Net Unrecovered Loss: ${{net_loss}}
+
+5. CUSTOMER IMPACT
+ {{customer_impact_summary}}
+ Customer Satisfaction Status: {{csat_status}}
+ Relationship Risk: {{relationship_risk_level}}
+
+6. CARRIER SCORECARD IMPACT
+ Carrier: {{carrier_name}}
+ Incidents (trailing 12 months): {{trailing_12_incident_count}}
+ On-Time Rate Impact: {{ot_rate_impact}}
+ Claims Ratio Impact: {{claims_ratio_impact}}
+ Recommended Action: {{carrier_recommended_action}}
+
+7. LESSONS LEARNED
+ {{lesson_1}}
+ {{lesson_2}}
+ {{lesson_3}}
+
+8. PROCESS IMPROVEMENTS
+ {{improvement_1}} — Owner: {{owner_1}} — Due: {{due_date_1}}
+ {{improvement_2}} — Owner: {{owner_2}} — Due: {{due_date_2}}
+ {{improvement_3}} — Owner: {{owner_3}} — Due: {{due_date_3}}
+
+====================================
+Filed in: {{document_management_location}}
+```
+
+---
+
+## 13. Carrier Performance Warning
+
+### When to Use
+- Carrier has a documented pattern of exceptions exceeding acceptable thresholds (e.g., on-time below 90%, claims ratio above 2%, multiple OS&D incidents in a quarter).
+- You have data from your TMS or scorecard to support the warning.
+- This is a formal notice — not a casual heads-up on a call. It creates a paper trail that supports future routing decisions or contract renegotiation.
+- Send after the pattern is established (typically 3+ incidents or a quarter of below-threshold performance), not after a single bad load.
+
+### Tone Guidance
+Data-first and dispassionate. Let the numbers make the case. You are not angry — you are a supply chain professional managing vendor performance. State the expectation, show where they fall short, and define the consequences clearly. Leave room for corrective action — you want them to improve, not just feel punished.
+
+### What NOT to Say
+- Do not make it personal — "your drivers don't care" is not professional.
+- Do not issue an ultimatum you are not prepared to enforce.
+- Do not send this during an active exception — wait until the current issue is resolved, then address the pattern.
+- Do not combine this with a new load tender or positive feedback — it dilutes the message.
+
+### Subject Line
+
+```
+Carrier Performance Notice — {{carrier_name}} (MC-{{carrier_mc}}) | {{performance_period}}
+```
+
+### Body
+
+```
+{{carrier_contact_name}},
+{{carrier_contact_title}}
+{{carrier_name}}
+
+This letter serves as a formal performance notice regarding {{carrier_name}}'s
+service on {{our_company}} freight during the period {{performance_period}}.
+
+PERFORMANCE SUMMARY:
+
+ Metric Target Actual Variance
+ ───────────────────── ──────── ──────── ────────
+ On-Time Delivery {{ot_target}} {{ot_actual}} {{ot_variance}}
+ Claims Ratio {{claims_target}} {{claims_actual}} {{claims_variance}}
+ Tender Acceptance {{ta_target}} {{ta_actual}} {{ta_variance}}
+ Check-Call Compliance {{cc_target}} {{cc_actual}} {{cc_variance}}
+ OS&D Incidents {{osd_target}} {{osd_actual}} {{osd_variance}}
+
+SPECIFIC INCIDENTS:
+
+ {{incident_date_1}} | PRO {{incident_pro_1}} | {{incident_type_1}} | ${{incident_cost_1}}
+ {{incident_date_2}} | PRO {{incident_pro_2}} | {{incident_type_2}} | ${{incident_cost_2}}
+ {{incident_date_3}} | PRO {{incident_pro_3}} | {{incident_type_3}} | ${{incident_cost_3}}
+ {{#if more_incidents}}
+ ({{additional_incident_count}} additional incidents detailed in attachment)
+ {{/if}}
+
+ Total Exception Cost ({{performance_period}}): ${{total_period_exception_cost}}
+
+VOLUME CONTEXT:
+
+During this period, {{carrier_name}} handled {{total_loads}} loads for
+{{our_company}} representing ${{total_freight_spend}} in freight spend. You are
+currently ranked {{carrier_rank}} of {{total_carriers}} carriers in our network
+for the lanes you serve.
+
+EXPECTATIONS:
+
+To maintain current volume and lane assignments, we require:
+ 1. {{expectation_1}}
+ 2. {{expectation_2}}
+ 3. {{expectation_3}}
+
+We require a written corrective action plan within {{corrective_plan_days}}
+business days of this notice.
+
+CONSEQUENCES:
+
+If performance does not improve to target levels within {{improvement_period}}:
+ - {{consequence_1}}
+ - {{consequence_2}}
+ - {{consequence_3}}
+
+We are committed to working with carrier partners who meet our service
+standards. I welcome a call to discuss this notice and develop a corrective plan
+together.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+
+CC: {{internal_cc_list}}
+```
+
+---
+
+## 14. Customer Apology with Resolution
+
+### When to Use
+- A significant exception has been fully resolved and the customer has received their freight, replacement, or credit.
+- The exception was severe enough to warrant a formal acknowledgment beyond the operational updates already sent.
+- You want to reinforce the relationship and demonstrate that systemic improvements are being made — not just a one-time fix.
+
+### Tone Guidance
+Genuine and specific. A good apology names the specific impact, describes what was done, and commits to specific prevention steps. It does not grovel or over-apologize — the customer is a business partner, not a victim. It should feel like it was written by a senior professional who understands their business, not a customer service script. End on a forward-looking note.
+
+### What NOT to Say
+- Do not use "we apologize for any inconvenience" — name the actual impact. "I know the two-day delay forced your team to reschedule the retail reset" is ten times more effective.
+- Do not blame the carrier or any third party. You own the customer relationship.
+- Do not make promises you cannot keep. "This will never happen again" is not credible. "Here are the three specific steps we are implementing" is.
+- Do not make this a sales pitch or segue into new services. Stay focused on the resolution.
+- Do not send this the same day as the resolution — wait 1–2 business days so the customer has confirmed the resolution is satisfactory.
+
+### Subject Line
+
+```
+PO {{po_number}} — Resolution Confirmed and Path Forward
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+Now that PO {{po_number}} has been fully resolved, I want to close the loop
+personally.
+
+WHAT HAPPENED:
+On {{exception_date}}, {{exception_summary_one_sentence}}. This resulted in
+{{specific_customer_impact}}.
+
+WHAT WE DID:
+ - {{resolution_action_1}}
+ - {{resolution_action_2}}
+ - {{resolution_action_3}}
+ - Final resolution: {{final_resolution_summary}}
+
+WHAT WE ARE CHANGING:
+I do not want to repeat what you experienced. Here are the specific steps we
+are putting in place:
+
+ 1. {{prevention_step_1}}
+ 2. {{prevention_step_2}}
+ 3. {{prevention_step_3}}
+
+{{#if financial_goodwill}}
+GOODWILL:
+{{financial_goodwill_description}}
+{{/if}}
+
+I value your business and I value the trust your team places in us. I take it
+personally when we fall short of the standard you expect.
+
+If you have any remaining concerns about this shipment or anything else, I am
+always available at {{our_contact_phone}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## Usage Notes for AI Agents
+
+**Template Selection:** Match the template to the audience (carrier ops, carrier executive, customer, internal) and the stage of the exception lifecycle (detection, escalation, claims, resolution, post-mortem). When in doubt, start with the lowest-escalation template appropriate for the elapsed time and severity.
+
+**Variable Substitution:** All `{{variables}}` must be replaced before sending. If a value is unknown, do not leave the placeholder — either obtain the information or remove the section with a note that it will follow.
+
+**Conditional Sections:** Sections wrapped in `{{#if}}...{{/if}}` are optional and should be included only when the condition applies (e.g., `{{#if pattern_exists}}` in the VP escalation template).
+
+**Tone Calibration:** The tone guidance for each template reflects the appropriate register for that audience and situation. Do not soften escalation templates to be "nicer" or harden customer templates to be "tougher" — the calibration is deliberate.
+
+**Legal Disclaimers:** The claims filing cover letter references the Carmack Amendment (49 U.S.C. § 14706), which applies to interstate motor carrier shipments. For brokered freight, international shipments, or intrastate moves, verify the applicable legal framework before sending. When in doubt, route through legal review.
+
+**Timing:**
+- Initial carrier notification: within 1 hour of exception discovery.
+- Customer proactive update: within 2 hours of confirmed impact, or before the customer's next business-day start — whichever comes first.
+- Escalation to account manager: after 4 hours without response (2 hours for urgent).
+- Escalation to VP/Director: after 12–24 hours without account manager resolution.
+- Claims filing: as soon as documentation is assembled, within the 9-month statutory window.
+- Post-resolution summary: within 5 business days of closure.
+- Performance warning: after pattern is documented, not during an active exception.
+- Customer apology: 1–2 business days after resolution is confirmed.
\ No newline at end of file
diff --git a/skills/logistics-exception-management/references/decision-frameworks.md b/skills/logistics-exception-management/references/decision-frameworks.md
new file mode 100644
index 00000000..d96e3d12
--- /dev/null
+++ b/skills/logistics-exception-management/references/decision-frameworks.md
@@ -0,0 +1,1460 @@
+# Decision Frameworks — Logistics Exception Management
+
+This reference provides the detailed decision logic, scoring matrices, financial models,
+and mode-specific resolution workflows for logistics exception management. It is loaded
+on demand when the agent needs to make or recommend nuanced exception-handling decisions.
+
+All thresholds, timelines, and cost assumptions reflect US domestic and international
+freight operations across LTL, FTL, parcel, intermodal, ocean, and air modes.
+
+---
+
+## 1. Exception Severity Matrix
+
+### 1.1 Scoring Methodology
+
+Every incoming exception is scored across four dimensions. Each dimension produces a
+score from 1 to 5. The **composite severity** equals the **highest single-dimension
+score**, not the average — a shipment that scores 2/2/2/5 is a Level 5 exception
+because a single critical dimension governs urgency.
+
+After computing the raw composite, apply the **elevation modifiers** in §1.3 to
+arrive at the effective severity, which caps at Level 5.
+
+### 1.2 Full Severity Matrix
+
+#### Dimension A — Financial Impact
+
+| Level | Product Value at Risk | Expedite / Re-Ship Cost | Penalty Exposure | Typical Scenarios |
+|-------|----------------------|------------------------|-----------------|-------------------|
+| 1 — Minimal | < $1,000 | None or < $200 | None | Minor LTL shortage, single damaged carton, residential parcel delay |
+| 2 — Moderate | $1,000–$5,000 | $200–$1,500 | Informal customer credit request likely | Multi-carton LTL damage, regional FTL delay 1–2 days, parcel loss with declared value |
+| 3 — Significant | $5,000–$25,000 | $1,500–$8,000 | Contractual penalty triggers within 48 hrs | Full pallet damage, FTL delay into customer delivery window, ocean container shortage affecting production schedule |
+| 4 — Major | $25,000–$100,000 | $8,000–$35,000 | Active penalty clause or chargeback imminent | Multi-pallet loss, air freight failure on critical launch shipment, reefer failure on full trailer of produce |
+| 5 — Critical | > $100,000 | > $35,000 or no expedite option exists | Regulatory fine, contract termination risk, or litigation exposure | Full trailer loss/theft, ocean container of pharma with temp excursion, hazmat incident with EPA/DOT reporting obligation |
+
+#### Dimension B — Customer Impact
+
+| Level | Customer Tier | SLA Status | Business Impact to Customer | Typical Scenarios |
+|-------|-------------|-----------|---------------------------|-------------------|
+| 1 — Minimal | Standard / spot customer | No SLA or well within SLA window | Inconvenience only; customer has inventory buffer | Delay to distributor who carries 30-day stock |
+| 2 — Moderate | Regular account | SLA at risk but not yet breached | Customer will notice, may request credit | Delivery misses requested date but within contractual tolerance |
+| 3 — Significant | Key account (top 20%) | SLA breach within 24 hrs | Customer's operations impacted; regional stockout possible | Late delivery to DC feeding retail replenishment |
+| 4 — Major | Enterprise / strategic account | SLA already breached or will breach today | Customer's production line slowed, retail launch compromised, or their customer is impacted | Automotive JIT delivery failure, retail holiday launch delay |
+| 5 — Critical | Tier 1 enterprise or regulated customer | SLA breach + penalty clause triggered | Customer production shutdown, patient safety concern, or regulatory impact to customer | Pharma shipment to hospital, auto assembly plant line-down, government contract with liquidated damages |
+
+#### Dimension C — Time Sensitivity
+
+| Level | Available Recovery Window | Alternative Sourcing | Perishability | Typical Scenarios |
+|-------|--------------------------|---------------------|--------------|-------------------|
+| 1 — Minimal | > 5 business days before customer need-by | Multiple alternatives available | Non-perishable | Stock replenishment with safety stock in place |
+| 2 — Moderate | 2–5 business days | Alternatives available but at premium cost | Non-perishable, but inventory turn pressure | Promotional inventory needed before event window |
+| 3 — Significant | 24–48 hours | Limited alternatives, ground expedite still viable | Perishable with > 48 hrs remaining shelf life | Fresh produce with 5-day shelf life at day 3 |
+| 4 — Major | < 24 hours | Air expedite only option | Perishable with < 48 hrs remaining shelf life, or time-definite service commitment | Temperature-sensitive biotech, next-day surgical supplies |
+| 5 — Critical | No window — needed now | No alternative exists or product is custom/irreplaceable | Perishable with < 24 hrs, or already expired in transit | Transplant organs, custom-manufactured parts for shutdown line, court-ordered evidence delivery |
+
+#### Dimension D — Regulatory / Safety
+
+| Level | Regulatory Exposure | Safety Concern | Reporting Obligation | Typical Scenarios |
+|-------|-------------------|---------------|---------------------|-------------------|
+| 1 — None | No regulatory dimension | No safety concern | None | Standard dry freight, consumer goods |
+| 2 — Low | Regulatory dimension exists but no violation | Potential quality concern, no safety risk | Internal documentation only | Cosmetics with minor packaging damage, electronics with cosmetic dents |
+| 3 — Moderate | Potential regulatory inquiry if not documented properly | Quality compromise that could reach end consumer | Proactive notification to QA team; may require regulatory hold | Food products with cold chain deviation within acceptable range |
+| 4 — High | Regulatory violation likely if product reaches market | Potential safety risk to end consumer or handler | Mandatory internal reporting to quality/regulatory within 4 hrs; potential voluntary recall | Pharma with temp excursion beyond validated range, dietary supplements with contamination exposure |
+| 5 — Critical | Active regulatory violation; agency notification required | Immediate safety hazard | Mandatory external reporting (FDA, DOT, EPA, FMCSA) within hours; potential mandatory recall | Hazmat spill, pharma temp failure on life-saving medication, foodborne illness risk, leaking chemical container |
+
+### 1.3 Elevation Modifiers
+
+Apply these modifiers after computing the raw composite score. Elevation is additive
+but caps at Level 5.
+
+| Condition | Elevation |
+|-----------|-----------|
+| Customer is under active QBR (quarterly business review) period | +1 level |
+| This is the 3rd+ exception on the same lane in 30 days | +1 level |
+| Exception occurred on a shipment booked at premium/guaranteed service | +1 level |
+| Carrier involved is under corrective action plan | +1 level |
+| Shipment is for a new customer (first 90 days of relationship) | +1 level |
+| Media or public visibility risk (e.g., branded trailer, viral social media) | +2 levels |
+| Exception involves a shipment already recovering from a prior exception | +2 levels |
+
+### 1.4 Severity-to-Action Mapping
+
+| Effective Severity | Assigned To | Initial Response SLA | Customer Notification | Internal Notification | Review Cadence |
+|-------------------|-------------|---------------------|----------------------|----------------------|---------------|
+| Level 1 | Analyst (auto-assign) | 8 business hours | Only if customer inquires | None required | Daily batch review |
+| Level 2 | Analyst (auto-assign) | 4 business hours | Proactive if delivery date affected | Team lead dashboard | Daily batch review |
+| Level 3 | Senior analyst (manual assign) | 2 hours | Proactive with resolution timeline | Manager notification | Every 4 hours |
+| Level 4 | Senior analyst + team lead | 1 hour | Immediate proactive call, then written follow-up | Director notification; account team briefed | Every 2 hours |
+| Level 5 | Dedicated handler + manager direct oversight | 30 minutes | VP-to-VP or C-level communication path | VP notification within 1 hour; war-room if multiple Level 5s concurrent | Continuous until stabilized |
+
+---
+
+## 2. Financial Impact Calculation Model
+
+### 2.1 Total Exception Cost Formula
+
+```
+Total Exception Cost (TEC) = Product Loss (PL)
+ + Expedite / Re-Ship Cost (ERC)
+ + Customer Penalties (CP)
+ + Administrative Processing Cost (APC)
+ + Relationship Damage Estimate (RDE)
+ + Downstream Ripple Cost (DRC)
+```
+
+### 2.2 Component Definitions and Assumptions
+
+#### Product Loss (PL)
+
+PL equals the lesser of (a) replacement cost at current wholesale or (b) original
+invoice value, unless the customer contract specifies retail/resale valuation for
+chargeback purposes.
+
+- Damaged but salvageable: PL = invoice value × damage percentage. Use 25% for
+ cosmetic-only damage, 50% for functional-but-impaired, 100% for unsalvageable.
+- Shortage: PL = unit cost × units short.
+- Full loss: PL = full invoice value including freight-in if FOB Origin.
+- Temperature excursion: PL = full invoice value if excursion exceeds validated range.
+ No partial credit on regulated products — it is all or nothing.
+
+#### Expedite / Re-Ship Cost (ERC)
+
+Standard cost multipliers against base freight cost:
+
+| Expedite Method | Multiplier vs. Base Rate | Typical Lead Time | When to Use |
+|----------------|------------------------|------------------|-------------|
+| Ground re-ship (same mode) | 1.0–1.3× | Original transit time | Recovery window > 5 business days |
+| Ground expedite (team driver / exclusive-use) | 2.5–4.0× | 40–60% of standard transit | Recovery window 2–5 business days, shipment > 150 lbs |
+| LTL guaranteed (volume or guaranteed overnight) | 1.8–2.5× | Next-day to 2-day | Recovery window 1–3 days, shipment < 10,000 lbs |
+| Domestic air (next-flight-out, NFO) | 6–12× | Same day or next morning | Recovery window < 24 hrs, shipment < 2,000 lbs |
+| Domestic air charter | 15–30× | 4–8 hours | No commercial option fits; production shutdown imminent |
+| International air (ex. ocean recovery) | 8–15× ocean base rate | 2–5 days vs. 25–40 days ocean | Recovery window < 2 weeks on ocean lane |
+| Hotshot / sprinter van | Flat $2.50–$4.50 per mile | Depends on distance; ~500 mi/day | Small, urgent shipment (< 3,000 lbs); regional recovery |
+
+Example: Base FTL rate Chicago to Dallas = $2,800. Customer needs delivery in 18 hours
+instead of standard 2-day transit. Team driver expedite = $2,800 × 3.0 = $8,400.
+Air NFO for 800 lbs at $0.85/lb = $680 freight + $150 handling = $830. Air is cheaper
+if weight allows; FTL expedite is cheaper above roughly 4,000–5,000 lbs depending on lane.
+
+#### Customer Penalties (CP)
+
+| Penalty Type | Typical Range | Calculation |
+|-------------|--------------|-------------|
+| Retail chargeback (late delivery to DC) | $500 flat + $50–$150 per carton | Per retailer's vendor compliance guide |
+| Retail chargeback (ASN/labeling error from re-ship) | $200–$1,000 flat | Often triggered by rush re-ships that bypass EDI integration |
+| OTIF (On-Time In-Full) penalty | 3–8% of invoice value per occurrence | Walmart = 3% of COGS; other retailers vary |
+| Production downtime reimbursement | $5,000–$50,000 per hour of line stoppage | Per manufacturing customer contract; automotive lines often $25K+/hr |
+| Contractual SLA penalty | 1–5% of monthly freight spend per SLA breach | Cumulative; multiple breaches compound |
+| Ad-hoc customer credit / goodwill | 5–15% of invoice as credit memo | Discretionary; used to preserve relationship when no formal penalty exists |
+
+#### Administrative Processing Cost (APC)
+
+Internal labor cost to manage the exception from intake to closure:
+
+| Complexity Tier | Activities | Estimated Hours | Cost at $45/hr Fully Loaded |
+|----------------|-----------|----------------|---------------------------|
+| Tier 1 — Simple | Log, one carrier call, update customer, close | 1.5–2.5 hrs | $68–$113 |
+| Tier 2 — Standard | Log, multiple carrier contacts, file claim, gather docs, customer updates, close | 4–8 hrs | $180–$360 |
+| Tier 3 — Complex | All of Tier 2 + inspection coordination, multi-party dispute, escalation, legal review potential | 12–25 hrs | $540–$1,125 |
+| Tier 4 — Litigation track | All of Tier 3 + legal engagement, deposition prep, expert witnesses | 40–100+ hrs | $1,800–$4,500+ (plus external legal at $250–$450/hr) |
+
+#### Relationship Damage Estimate (RDE)
+
+This is the hardest component to quantify. Use these heuristics:
+
+- **New customer (< 6 months):** Exception during onboarding carries 3× the
+ relationship weight. A $2,000 failure can cost a $500K annual account. RDE = 10–20%
+ of estimated first-year revenue at risk of churn.
+- **Stable customer (> 2 years):** Single exception rarely causes churn. RDE = 0–2%
+ of annual revenue unless it is a pattern (3+ exceptions in 90 days, in which case
+ treat as new-customer risk).
+- **Customer under competitive bid:** Any exception during RFP evaluation period
+ from a competitor. RDE = 25–50% of annual revenue at risk.
+
+#### Downstream Ripple Cost (DRC)
+
+Costs that propagate beyond the immediate exception:
+
+- Inventory reorder disruption: If exception causes safety-stock depletion, the
+ replenishment order will be rushed. Estimate 1.5× standard inbound freight for
+ the replenishment cycle.
+- Warehouse receiving disruption: Unexpected returns, re-deliveries, or inspection
+ holds consume dock door time. Estimate $150–$300 per unplanned dock appointment.
+- Customer service call volume: Each exception generates 2–5 inbound customer
+ inquiries. At $8–$12 per call (including agent time and overhead), that is
+ $16–$60 per exception.
+- Reporting and analytics overhead: Carrier scorecards, root cause analysis
+ meetings, and corrective action documentation. Estimate 1–3 hours per qualifying
+ exception at $45/hr.
+
+### 2.3 Worked Examples
+
+#### Example A — LTL Damage, Mid-Value
+
+Shipment: 6 pallets of consumer electronics, Chicago to Atlanta.
+Invoice value: $18,500. One pallet fork-punctured at origin terminal.
+
+```
+PL = $18,500 × (1/6 pallets) × 100% (unsalvageable) = $3,083
+ERC = Re-ship 1 pallet via LTL guaranteed 2-day: $650 = $650
+CP = Retailer OTIF penalty: $18,500 × 3% = $555
+ (only if re-ship misses must-arrive-by date) = $555
+APC = Tier 2 standard claim: ~6 hrs × $45 = $270
+RDE = Stable customer, isolated incident: ~0% = $0
+DRC = 3 customer service calls × $10 = $30
+---
+TEC = $3,083 + $650 + $555 + $270 + $0 + $30 = $4,588
+```
+
+Decision: File claim for $3,083 product value + $650 re-ship cost = $3,733 carrier
+liability claim under Carmack. Customer penalty is shipper's loss unless carrier
+proximate cause can support consequential damages (unlikely under standard BOL terms).
+
+#### Example B — FTL Total Loss, High-Value
+
+Shipment: Full truckload of medical devices, Memphis to Los Angeles.
+Invoice value: $285,000. Shipment not delivered, no scans for 72 hours, presumed stolen.
+
+```
+PL = $285,000 (full invoice) = $285,000
+ERC = Air charter for replacement: $48,000 = $48,000
+CP = Hospital contract: 2 days production delay at $12,000/day = $24,000
+APC = Tier 4 (theft investigation + legal): ~60 hrs × $45
+ + external legal ~20 hrs × $350 = $9,700
+RDE = Strategic account in first year: 15% × $1.2M annual rev = $180,000
+DRC = Safety stock depletion replenishment, expedited inbound = $8,500
+---
+TEC = $285,000 + $48,000 + $24,000 + $9,700 + $180,000 + $8,500 = $555,200
+```
+
+Decision: Level 5 severity. Immediate VP notification. Law enforcement report filed.
+Carrier cargo insurance claim ($100K per occurrence typical — will not cover full
+loss). Shipper's all-risk cargo policy for excess. Customer air-chartered at shipper
+expense while claims are pursued. Consider consequential damages claim if carrier
+was negligent in vetting driver or equipment.
+
+#### Example C — Eat-the-Cost Decision
+
+Shipment: 2 cartons of office supplies, parcel ground, value $380.
+One carton crushed, contents destroyed.
+
+```
+PL = $190 (one carton) = $190
+ERC = Re-ship via ground: $12 = $12
+CP = None (internal office supply order) = $0
+APC = Tier 1 if filed: 2 hrs × $45 = $90
+RDE = N/A (internal) = $0
+DRC = None = $0
+---
+TEC = $190 + $12 + $0 + $90 + $0 + $0 = $292
+
+Potential claim recovery: $190 (carrier liability)
+Filing cost: $90 (internal processing)
+Net recovery: $190 - $90 = $100
+```
+
+Decision: Marginal. File only if parcel carrier has automated claims portal with < 15
+minutes processing time. Otherwise absorb and log for quarterly carrier review.
+
+---
+
+## 3. Carrier Response Decision Tree
+
+### 3.1 Path A — Cooperative Carrier
+
+The carrier acknowledges the exception, provides updates, and works toward resolution.
+This is the expected path with contracted carriers in good standing.
+
+| Checkpoint | Action | Expected Carrier Response | If Response is Inadequate |
+|-----------|--------|--------------------------|--------------------------|
+| 0 hrs (intake) | Send initial exception notice via carrier portal or email with PRO#, BOL#, description of exception, requested action, and response deadline | Acknowledgment within 1 hour during business hours | Move to Path B at 2 hrs |
+| 2 hrs | Verify carrier acknowledgment received; confirm they have assigned the exception internally | Carrier provides case/reference number and assigned handler name | Escalate to carrier's operations supervisor; send second notice with "Escalation" in subject |
+| 4 hrs | Request status update — what has the carrier done so far, what is the plan, what is the revised ETA or inspection timeline | Specific plan with timeline: "Driver ETA 6pm" or "Inspector scheduled tomorrow AM" | Call carrier's account representative (not just dispatch). Document that operational channel is unresponsive |
+| 8 hrs | Evaluate progress against carrier's stated plan. If delivery exception: is shipment moving? If damage: is inspection scheduled? | Tangible progress — updated tracking, inspection confirmed, driver checked in | Formal escalation email to carrier VP of Operations or regional director. CC your procurement/carrier management team |
+| 24 hrs | Full status review. For delays: confirm revised delivery date. For damage/loss: confirm claim documentation in progress | Delivery completed, or inspection done and claim packet received, or clear revised timeline with daily updates committed | If still unresolved: initiate backup carrier for re-ship (do not wait longer). File formal carrier complaint in carrier management system |
+| 48 hrs | Resolution or near-resolution expected for cooperative carriers | Claim acknowledged and in processing, or delivery completed with exception closed | Carrier performance review triggered. Procurement notified for quarterly scorecard impact |
+| 72 hrs | Any open delay or loss should be fully resolved or in active claim processing | Claim payment timeline provided (30/60/90 day), or shipment delivered and exception closed | Consider carrier probation for new shipments on this lane |
+
+### 3.2 Path B — Unresponsive Carrier
+
+The carrier is not intentionally difficult but is not responding — dispatch is
+overwhelmed, claims department is backed up, or the contact information is wrong.
+Common with smaller asset carriers and during peak season.
+
+| Checkpoint | Action | Objective | Escalation |
+|-----------|--------|-----------|-----------|
+| 0–2 hrs | Standard notice sent, no response received | Establish contact | Try all available channels: portal, email, phone. If broker-arranged shipment, contact broker AND underlying carrier |
+| 2 hrs | Call carrier dispatch directly. If no answer, leave voicemail with your callback number and shipment references. Send follow-up email with "URGENT — Response Required" subject | Get any human response | If broker-arranged: put broker on notice that their carrier is unresponsive. Broker has contractual obligation to manage their carrier |
+| 4 hrs | Second call to dispatch. Try driver's cell if available (from BOL or load confirmation). Contact carrier's safety/compliance department (different phone tree) as alternative entry point | Any status information | Notify your team lead. Begin contingency planning for re-ship or alternative resolution |
+| 8 hrs | Three-channel blitz: call dispatch, email operations manager (find on carrier's website or LinkedIn), send formal notice via certified email or fax referencing carrier's MC/DOT number | Formal documentation of non-response | Authorize re-ship or expedite without waiting for carrier. Send carrier a "Notice of Non-Response" documenting all contact attempts with timestamps |
+| 24 hrs | Final notice: "You have 24 hours to respond before we process this as an uncontested claim and adjust payment on open invoices" | Force response through financial leverage | Place freight payment hold on carrier's open invoices (coordinate with AP). File claim based on available documentation. Report to carrier management for immediate lane review |
+| 48 hrs | If still no response, treat as abandoned. Process claim against carrier's cargo insurance (contact their insurer directly if you have the policy info from onboarding). If shipment is still in transit/unknown: report to FMCSA for potential out-of-service carrier | Full recovery mode | Remove carrier from active routing guide. Escalate to your legal team if claim value > $10,000 |
+| 72 hrs | Formal demand letter from legal or via registered mail citing specific claim amount and legal basis (Carmack for domestic). 30-day response deadline per 49 CFR § 370.9 | Legal posture established | Begin preparation for small claims (< $10K) or federal court filing if value warrants |
+
+### 3.3 Path C — Adversarial Carrier
+
+The carrier denies liability, provides false information, disputes documentation,
+or acts in bad faith. This includes situations where the carrier's claims department
+issues a blanket denial without investigating.
+
+| Checkpoint | Action | Documentation Priority | Escalation |
+|-----------|--------|----------------------|-----------|
+| 0 hrs (denial received) | Review denial letter/email line by line. Identify the specific basis for denial (act of shipper, inherent vice, act of God, packaging, etc.) | Preserve all original documentation. Screenshot carrier portal status history before it can be altered | Assign to senior analyst or claims specialist, not junior staff |
+| 2 hrs | Draft point-by-point rebuttal addressing each denial reason with documentary evidence. Under Carmack, once shipper proves three elements (good condition at tender, damaged at delivery, damages amount), burden shifts to carrier | Organize evidence package: clean BOL, exception-noted POD, photos, packing specs, weight certificates, temperature logs | Brief team lead on denial and planned rebuttal strategy |
+| 4 hrs | Send formal rebuttal via email and carrier portal with all supporting evidence attached. Request "reconsideration of claim denial" and cite specific regulatory basis for carrier liability | Send via method that provides delivery confirmation. Keep copies of everything sent | If denial is clearly frivolous (e.g., "act of God" for a forklift puncture), notify carrier's account manager that denial is damaging the relationship |
+| 8 hrs | If carrier reaffirms denial: request the carrier's specific evidence supporting their defense. Under 49 CFR § 370.7, carrier must conduct a reasonable investigation before denying | Log all communications with exact timestamps. Note any inconsistencies between carrier's stated reasons and available evidence | Notify your manager and procurement. Begin calculating whether litigation cost is justified vs. claim value |
+| 24 hrs | Escalate to carrier's VP of Claims or General Counsel with a summary letter: claim facts, evidence, legal basis, prior communications timeline, and a settlement demand | Prepare a claim file that is litigation-ready even if you hope to settle: chronological narrative, evidence index, damages calculation, legal authority summary | Procurement to issue formal notice of dispute to carrier's sales team. Separate the business relationship discussion from the claims dispute |
+| 48 hrs | If no movement: engage third-party claims service or freight claims attorney for demand letter on legal letterhead. Cost: typically $500–$1,500 for demand letter, contingency fee of 25–33% if litigation needed | Provide complete file to outside counsel. Flag any potential weaknesses in your case (late filing, incomplete POD, packaging shortfalls) | Consider whether the carrier's business overall is worth preserving. If annual spend < claim value, this may be the last shipment regardless |
+| 72 hrs+ | Decision point: litigate, settle at a discount, or absorb. See §9 Eat-the-Cost Analysis for framework | Final evidence review and case assessment | VP-level decision on litigation vs. settlement vs. walk-away |
+
+### 3.4 Special Situation — Carrier Goes Dark Mid-Shipment
+
+When a carrier stops responding and the freight is in transit (not yet delivered):
+
+1. **Hour 0–1:** Attempt all contact channels (dispatch, driver cell, broker if applicable, carrier safety department). Check last known GPS/ELD position if available through your TMS integration or load-tracking platform.
+
+2. **Hour 1–4:** Contact the carrier's insurance company to verify the policy is active. If brokered, demand the broker provide proof of last contact with the driver and GPS coordinates. If no GPS data available and shipment is high-value (> $50K), consider engaging a freight recovery service.
+
+3. **Hour 4–8:** If high-value or theft indicators present (carrier is new, load was double-brokered, pickup was in a high-theft corridor like Los Angeles, Memphis, Dallas, or the I-10/I-95 corridors): file a report with local law enforcement in the jurisdiction of last known location. Notify CargoNet or FreightWatch if you have a subscription.
+
+4. **Hour 8–24:** If the carrier is a broker's carrier: put the broker on formal notice that they are liable for the full shipment value. If the carrier is your contracted carrier: activate your contingency carrier for the lane and begin re-shipping replacement product.
+
+5. **Hour 24+:** Treat as presumed theft/loss. File formal claim. Notify your cargo insurance underwriter. Do not wait for "certainty" — the claim clock starts ticking.
+
+---
+
+## 4. Claims Filing Decision Framework
+
+### 4.1 File vs. Absorb vs. Negotiate Pre-Claim
+
+The decision to file a formal claim is not automatic. Each path has costs and trade-offs.
+
+#### Decision Matrix
+
+| Scenario | Recommended Path | Rationale |
+|----------|-----------------|-----------|
+| Claim value < $250, carrier has self-service portal | File via portal (< 15 min effort) | Automated filing cost is near-zero; builds claims history for scorecard |
+| Claim value < $500, no portal, good carrier relationship | Absorb, log for scorecard | APC exceeds likely net recovery. Mention informally to carrier rep at next review |
+| Claim value $500–$2,500, clear carrier liability | Negotiate pre-claim: call carrier and propose a freight credit or invoice deduction | Faster resolution (days vs. months), preserves relationship, avoids formal claims overhead |
+| Claim value $500–$2,500, disputed liability | File formal claim with documentation | Dispute needs formal record; informal negotiation without documentation weakens your position |
+| Claim value $2,500–$10,000 | File formal claim regardless of circumstances | Value justifies APC and relationship friction. Negotiate settlement only above 75% of claimed amount |
+| Claim value > $10,000 | File formal claim + involve senior management + legal awareness | Financial materiality threshold. Full documentation package. Independent inspection for damage claims. Accept settlement only above 85% or with strong business justification |
+| Any amount, 3rd+ claim against same carrier in 90 days | File formal claim AND trigger carrier performance review | Pattern indicates systemic issue; formal filing creates the record needed for contract renegotiation or termination |
+| Any amount, possible fraud indicators | File formal claim + notify compliance + preserve all evidence | Even small-dollar fraud must be documented. Patterns emerge only when individual incidents are formally recorded |
+
+#### ROI Calculation for Filing
+
+```
+Net Claim ROI = (Claim Amount × Probability of Recovery) - APC
+
+where:
+ Claim Amount = documented loss value (PL + ERC if carrier-caused)
+ Probability of Recovery = see §4.2 below
+ APC = administrative processing cost from §2.2
+```
+
+File when Net Claim ROI > $0 and the ratio (Net Claim ROI / Claim Amount) > 15%.
+Below 15% net margin on the claim, the organizational cost-of-attention often
+exceeds the financial benefit unless the claim builds a needed pattern record.
+
+### 4.2 Probability of Recovery by Carrier Type and Claim Type
+
+These recovery rates reflect industry experience across hundreds of thousands of
+claims. Adjust ±10% based on your specific carrier relationships and documentation
+quality.
+
+| Carrier Type | Damage (visible, noted on POD) | Damage (concealed) | Shortage (noted at delivery) | Full Loss | Delay (service failure) |
+|-------------|-------------------------------|-------------------|----------------------------|----------|----------------------|
+| National LTL (FedEx Freight, XPO, Estes, ODFL) | 80–90% | 40–55% | 70–80% | 85–95% | 15–25% (unless guaranteed service) |
+| Regional LTL | 70–85% | 30–45% | 60–75% | 75–85% | 10–20% |
+| Asset FTL carrier (large fleet) | 75–90% | 35–50% | 65–80% | 80–90% | 20–35% |
+| Small FTL carrier (< 50 trucks) | 55–70% | 20–35% | 45–60% | 50–65% | 5–15% |
+| Broker-arranged FTL | 60–75% | 25–40% | 50–65% | 60–75% | 10–20% |
+| Parcel (UPS, FedEx, USPS) | 70–85% | 45–60% | 60–75% | 80–90% | 30–50% (guaranteed service) |
+| Ocean (FCL) | 30–50% | 15–25% | 40–55% | 60–75% | < 5% |
+| Ocean (LCL) | 25–40% | 10–20% | 30–45% | 50–65% | < 5% |
+| Air freight (direct with airline) | 65–80% | 35–50% | 55–70% | 75–85% | 20–35% |
+| Air freight (via forwarder) | 55–70% | 25–40% | 45–60% | 65–80% | 15–25% |
+
+### 4.3 Documentation Checklist by Claim Type
+
+#### Damage Claim — All Modes
+
+Required:
+- [ ] Original BOL (signed, showing clean receipt by carrier at origin)
+- [ ] Delivery receipt / POD (showing exception notation — "damaged," "crushed," specific description)
+- [ ] Photographs: minimum 4 views (overview of shipment, close-up of damage, packaging condition, label/PRO visible)
+- [ ] Commercial invoice showing product value
+- [ ] Packing list showing piece count and descriptions
+- [ ] Written description of damage (what is damaged, extent, whether repairable)
+- [ ] Repair estimate or replacement quote from vendor
+- [ ] Packaging specifications (demonstrates product was packaged appropriately for the mode)
+
+Strongly recommended:
+- [ ] Weight certificate at origin (proves correct weight tendered)
+- [ ] Inspection report from independent surveyor (required for claims > $10,000 or disputed claims)
+- [ ] Temperature recorder data (for any temperature-sensitive product)
+- [ ] Photos from origin showing product in good condition at loading
+- [ ] Carrier inspection report (request from carrier's OS&D department)
+
+#### Shortage Claim
+
+Required:
+- [ ] Original BOL showing piece count tendered
+- [ ] Delivery receipt showing piece count received (discrepancy noted)
+- [ ] Commercial invoice for shorted product
+- [ ] Packing list with serial numbers or lot numbers if available
+- [ ] Written description: how many pieces short, which items, value per item
+
+Strongly recommended:
+- [ ] Loading photos/video showing correct count at origin
+- [ ] Seal numbers (origin seal vs. delivery seal — different seal = carrier liability strong)
+- [ ] Weight certificate at origin vs. weight at delivery (weight discrepancy corroborates shortage)
+- [ ] Security camera footage from dock (if available and shipment is high-value)
+
+#### Loss Claim (Full Shipment)
+
+Required:
+- [ ] Original BOL (proves tender to carrier)
+- [ ] Carrier pickup confirmation / signed pickup receipt
+- [ ] Commercial invoice (full shipment value)
+- [ ] Packing list (complete contents)
+- [ ] Formal tracer request filed with carrier (with carrier's response or non-response documented)
+- [ ] Proof of non-delivery: customer confirmation that product was never received
+
+Strongly recommended:
+- [ ] GPS/tracking history showing last known position
+- [ ] Law enforcement report (if theft suspected)
+- [ ] Carrier's insurance certificate (to file directly against insurer if carrier is unresponsive)
+- [ ] Evidence of carrier tender acceptance and load confirmation
+
+#### Delay Claim (Service Failure)
+
+Required:
+- [ ] Original BOL showing agreed pickup and delivery dates
+- [ ] Service level documentation (rate confirmation, routing guide showing guaranteed service)
+- [ ] Tracking history showing actual delivery date/time
+- [ ] Proof of financial loss caused by delay (penalty invoice, expedite receipt, lost sales documentation)
+
+Strongly recommended:
+- [ ] Customer correspondence showing delivery commitment that was based on carrier's service
+- [ ] Evidence that delay was not caused by shipper or consignee (no appointment changes, dock available)
+- [ ] Documentation of mitigation efforts (you tried to minimize the loss)
+
+### 4.4 Mode-Specific Filing Requirements
+
+#### US Domestic Surface — Carmack Amendment (49 USC § 14706)
+
+- **Jurisdiction:** All domestic surface transportation by motor carriers and freight forwarders operating under FMCSA authority.
+- **Filing deadline:** 9 months from date of delivery (or reasonable delivery date for non-delivery claims).
+- **Statute of limitations for litigation:** 2 years from the date the carrier disallows the claim.
+- **Carrier liability standard:** Carrier is strictly liable for actual loss, damage, or injury to goods. Carrier defenses: act of God, public enemy, act of shipper, public authority, inherent nature of goods.
+- **Shipper's burden:** (1) Goods were in good condition when tendered. (2) Goods were damaged/lost/short at destination. (3) Amount of damages.
+- **Limitation of liability:** Carriers may limit liability via released rates (lower rate in exchange for lower liability cap). Check your rate confirmation and BOL for released value clauses. If you did not agree to a released rate, full actual value applies.
+- **Filing method:** Written claim in any reasonable form that (a) identifies the shipment, (b) asserts liability, and (c) demands payment of a specific amount. 49 CFR § 370.3.
+- **Carrier response obligation:** Must acknowledge within 30 days. Must pay, decline, or make a firm settlement offer within 120 days. 49 CFR § 370.9.
+
+#### Ocean — Carriage of Goods by Sea Act (COGSA) / Hague-Visby Rules
+
+- **Jurisdiction:** International ocean shipments to/from US ports (COGSA); most international ocean shipments (Hague-Visby).
+- **Filing deadline:** Written notice of damage within 3 days of delivery (visible damage) or 3 days after delivery ends (concealed damage) under COGSA. Failure to give notice creates a presumption that goods were delivered in good condition — it does not bar the claim, but shifts the burden of proof.
+- **Statute of limitations:** 1 year from delivery date (COGSA). This is a hard deadline — cannot be extended without carrier agreement.
+- **Carrier liability standard:** Carrier is liable unless they prove one of 17 enumerated exceptions (perils of the sea, act of God, insufficiency of packing, etc.). Burden of proof is complex and shifting.
+- **Liability limit:** $500 per package or customary freight unit (COGSA). SDR 666.67 per package or SDR 2 per kg gross weight, whichever is higher (Hague-Visby). Higher value must be declared on the bill of lading before shipment.
+- **Critical documentation:** Ocean bill of lading, survey report at discharge port (hire a marine surveyor — typical cost $800–$2,500 depending on port), container inspection report, seal integrity evidence, reefer download data for temperature-controlled.
+
+#### Air — Montreal Convention (International) / Air Cargo Act (Domestic US)
+
+- **Jurisdiction:** International air carriage (Montreal Convention); domestic US air freight is governed by the air waybill terms and applicable contract law.
+- **Notice deadline:** 14 days from receipt for damage claims. 21 days from delivery date for delay claims. These deadlines are strictly enforced — missing them is a complete bar to the claim.
+- **Statute of limitations:** 2 years from date of arrival or from the date the aircraft ought to have arrived.
+- **Liability limit:** 22 SDR per kilogram (~$30/kg, fluctuates with exchange rates). Higher value must be declared on the air waybill. Most airlines offer declared-value surcharges of 0.5–0.75% of excess value.
+- **Filing method:** Written complaint to the airline or handling agent. Include air waybill number, flight numbers, claim details, and damage documentation.
+- **Key nuance:** Ground handling agents (the companies that physically handle freight at airports) cause the majority of air freight damage, but the airline is liable to the shipper under Montreal Convention. The airline then has a subrogation claim against the handler.
+
+---
+
+## 5. Mode-Specific Resolution Workflows
+
+### 5.1 LTL Damage Resolution
+
+#### 5.1.1 Terminal-Caused Damage
+
+Damage occurring at carrier's terminal during cross-dock operations (forklift
+damage, stacking failures, improperly loaded onto delivery trailer).
+
+**Indicators:** Damage pattern consistent with handling (fork punctures, crush from
+top-loading, stretch wrap torn with product exposed). Often discovered at delivery
+terminal or by consignee.
+
+**Resolution Workflow:**
+
+1. **Consignee documents on POD** — specific notation: "2 of 6 pallets crushed,
+ product visible through torn packaging." Generic "damaged" is insufficient for
+ strong claims.
+2. **Photograph at delivery** — minimum 6 photos: overall shipment, each damaged
+ unit, packaging failure point, freight label/PRO visible in frame, floor of
+ trailer showing debris.
+3. **Request carrier terminal inspection** — call the delivering terminal directly
+ (not the 800-number). Ask for the OS&D clerk or terminal manager. Request that
+ damaged freight be held for inspection, not sent to salvage.
+4. **File claim within 48 hours** — terminal damage claims have highest recovery
+ rates (80–90%) because the carrier knows their terminal caused it. Do not delay.
+5. **If partial damage** — request carrier's salvage bid. Carriers sometimes offer
+ to sell damaged freight at auction and credit the difference. Evaluate whether the
+ salvage value is fair; reject lowball salvage bids (common tactic to reduce claim
+ payout).
+6. **Settlement expectation** — terminal-caused damage should settle at 85–100%
+ of invoice value within 60 days. If carrier offers less than 75%, escalate to
+ carrier's claims manager with terminal inspection evidence.
+
+#### 5.1.2 Transit Damage
+
+Damage occurring during over-the-road transit (shifting loads, hard braking, trailer
+accident, weather infiltration through damaged trailer roof/walls).
+
+**Indicators:** Product shifted within packaging, load bars displaced, multiple
+pallets damaged in the same direction (forward movement = hard stop).
+
+**Resolution Workflow:**
+
+1. **Determine if damage is from a known incident** — ask carrier dispatch: "Was
+ there any reported incident involving this trailer in transit?" Carriers are
+ required to log accidents, but minor incidents (hard braking, pothole impact)
+ often go unreported.
+2. **Document loading condition evidence** — if you have photos from loading dock
+ showing freight was properly loaded, secured with load bars/straps, and braced
+ appropriately, your claim is significantly stronger.
+3. **Weigh the shipment** — if you can get a weight ticket from a scale near the
+ delivery point, compare to the origin weight ticket. Significant discrepancy
+ combined with damage suggests freight shifted or fell off a pallet.
+4. **File claim within 5 business days** — transit damage is moderately strong for
+ the shipper (70–85% recovery). Carrier will investigate with the driver and
+ potentially dispute if they believe packaging was insufficient.
+5. **Common carrier defense** — "Inadequate packaging." Counter with: packaging
+ specifications from the manufacturer, ISTA or ASTM test results if available,
+ and evidence that the same packaging has shipped successfully on this lane before
+ without damage.
+6. **Settlement expectation** — 60–85% of invoice value within 90 days. Transit
+ damage claims often involve more back-and-forth than terminal damage.
+
+#### 5.1.3 Loading Damage (Origin)
+
+Damage caused during pickup when the carrier's driver or dock workers load the
+freight onto the trailer.
+
+**Indicators:** Driver signs clean BOL at origin. Damage discovered at first
+cross-dock terminal or at delivery. Damage pattern consistent with improper
+stacking, dropping during loading, or trailer incompatibility (e.g., product loaded
+in a trailer with protruding floor nails).
+
+**Resolution Workflow:**
+
+1. **Check for driver exception notations on pickup BOL** — if the driver noted
+ "shipper load and count" (SL&C), carrier will argue they are not liable for
+ how the product was loaded. SL&C is the shipper's enemy on damage claims. If
+ your dock loaded the trailer while the driver was in the office, this notation
+ is legitimate and weakens your claim.
+2. **If carrier's driver loaded** — your claim is strong. Document that your dock
+ staff witnessed proper product condition before loading and that the carrier's
+ driver conducted the loading.
+3. **First-terminal inspection** — if damage is discovered at the first terminal,
+ request photos from the terminal before freight is further handled. This narrows
+ the damage window to pickup-to-first-terminal.
+4. **File claim within 5 business days** — include the clean-signed BOL from origin
+ and the exception-noted delivery receipt.
+5. **Settlement expectation** — 70–85% if you can prove damage occurred during
+ carrier loading. Under 50% if SL&C was notated and you cannot prove carrier
+ handling caused the damage.
+
+### 5.2 FTL Delay Resolution
+
+#### 5.2.1 Driver-Caused Delay
+
+Late pickup, wrong routing, hours-of-service (HOS) violation forcing a rest stop,
+driver no-show.
+
+**Resolution Workflow:**
+
+1. **Hour 0 (delay identified):** Contact dispatch. Get the driver's current
+ location, reason for delay, and revised ETA. If driver no-showed at origin:
+ demand a replacement driver or tractor within 2 hours, or you are tendering
+ to backup carrier.
+2. **Hour 2:** If revised ETA is within customer tolerance, monitor. If not:
+ calculate whether a team driver can recover the schedule. Team driver cost adder
+ is typically $0.25–$0.40/mile on top of the base rate.
+3. **Hour 4:** If delay will cause a customer miss: authorize the team driver or
+ arrange backup carrier from the driver's current location. The original carrier
+ is responsible for the deadhead to the driver's current location (demand credit
+ or refuse to pay for the partial haul).
+4. **Hour 8+:** If carrier cannot recover the shipment and you have re-tendered to
+ a backup carrier: deduct the expedite cost difference from the original carrier's
+ open invoices. Document everything for the debit.
+5. **Post-resolution:** Record the service failure in the carrier scorecard. If
+ this is a pattern (2+ HOS-driven delays from same carrier in 60 days), their
+ fleet management and driver scheduling practices need review.
+
+#### 5.2.2 Mechanical Breakdown
+
+Tractor or trailer breakdown in transit.
+
+**Resolution Workflow:**
+
+1. **Hour 0:** Carrier should notify you proactively per contract terms. If you
+ discover via tracking: call dispatch immediately.
+2. **Assess repair timeline:** If carrier says "truck will be repaired in 2 hours"
+ — accept and monitor. If > 4 hours or uncertain: demand the carrier power-swap
+ (send a replacement tractor to the breakdown location). Major carriers can
+ power-swap within 2–4 hours in most metro areas.
+3. **Reefer breakdown:** If reefer unit fails on a temperature-sensitive load, this
+ becomes a product quality issue, not just a delay. Request the carrier download
+ the reefer unit data log immediately. If ambient temperature is > 40°F and
+ product is cold-chain: begin contingency for product replacement within 2 hours
+ of reefer failure confirmation.
+4. **Carrier liability for mechanical:** Carrier is generally liable for delays caused
+ by mechanical failure — it is not "act of God." However, contractual terms may
+ exclude or limit delay liability. Check your carrier agreement.
+5. **Cost allocation:** Carrier should absorb any power-swap costs and incremental
+ transit cost. If you had to re-tender to a backup carrier, deduct the cost
+ difference from the original carrier.
+
+#### 5.2.3 Weather Delay
+
+Legitimate severe weather (winter storms, hurricanes, flooding, tornado activity)
+that prevents safe transit.
+
+**Resolution Workflow:**
+
+1. **Verify the weather event** — check NOAA and FMCSA road condition reports for
+ the specific route. Carriers sometimes claim "weather" for a light rain. The
+ delay must be proportional to the actual event severity.
+2. **Determine if the delay was avoidable** — if the weather was forecasted 48+
+ hours in advance and the carrier could have routed around it or departed earlier:
+ this is a planning failure, not force majeure. Challenge the carrier's defense.
+3. **Customer communication** — notify immediately with the weather event details
+ and revised ETA. Customers generally understand weather delays if communicated
+ proactively. Do not wait until the delivery window expires to notify.
+4. **Cost allocation** — true force majeure: neither party at fault. Carrier is not
+ liable for delay. Shipper cannot deduct. Expedite costs after the weather clears
+ are negotiable — the carrier should prioritize your shipment for recovery without
+ charging a premium. If they try to charge expedite rates for post-weather recovery,
+ push back.
+5. **Pattern recognition** — if a lane experiences 3+ weather delays per season
+ (e.g., Denver to Salt Lake City in January), build weather buffers into your
+ transit time commitments for that lane rather than treating each as an exception.
+
+#### 5.2.4 Capacity-Driven Delay
+
+Carrier accepted the tender but cannot cover it — no driver available. Common during
+peak season and month-end volume spikes.
+
+**Resolution Workflow:**
+
+1. **Hour 0 (carrier notifies or fails to cover):** Do not wait. Immediately
+ re-tender to backup carriers. Do not give the primary carrier "until end of day"
+ — capacity tightens as the day progresses. Every hour of delay reduces your
+ options.
+2. **Hour 2:** If primary carrier has not confirmed a driver: they have effectively
+ rejected the tender. Re-tender to backup or spot market. The primary carrier
+ owes you nothing for the delay (they did not pick up the freight), but you should
+ record the service failure as a tender acceptance failure.
+3. **Spot market premium:** If you must go to the spot market, the premium over
+ contract rate is your loss. Track this as "tender rejection cost" in carrier
+ scorecards. Typical spot premiums: 15–40% in normal market, 50–150% during
+ peak events or regional disruptions.
+4. **Contractual leverage:** If your carrier contract has tender acceptance minimums
+ (e.g., 90% acceptance rate), document every failure. Aggregate for quarterly
+ review. Carriers who repeatedly accept tenders and then fail to cover are worse
+ than carriers who reject upfront — they destroy your ability to plan.
+
+### 5.3 Parcel Loss Resolution
+
+#### 5.3.1 Ground Parcel Loss
+
+**Resolution Workflow:**
+
+1. **Day 1 past expected delivery:** Check tracking. If status is "delivered" but
+ customer says not received: request proof of delivery (signature, GPS stamp, photo).
+ If no GPS/photo evidence, the carrier's "delivered" scan is insufficient.
+2. **Day 2:** File online tracer through carrier portal. UPS: 1 business day for
+ tracer investigation. FedEx: 1–2 business days. USPS: mail search request, allow
+ 5–10 business days.
+3. **Day 3–5:** If tracer comes back "unable to locate": file formal claim through
+ carrier portal.
+4. **Day 5–10:** Re-ship replacement to customer. Do not wait for claim resolution
+ to keep the customer whole.
+5. **Claim processing:** UPS and FedEx typically resolve parcel claims within 5–8
+ business days of filing. USPS: 30–60 days. Ensure declared value was purchased
+ at time of shipping — default coverage is $100 (UPS/FedEx) or $50 (USPS Priority).
+6. **If claim denied:** Most common denial reason is "insufficient declared value."
+ If you declared the correct value at shipping, escalate. If you did not declare
+ sufficient value, the recovery is capped at the default limit regardless of
+ actual product value. This is an expensive lesson — ensure high-value parcel
+ shipments always have declared value coverage.
+
+#### 5.3.2 Air Parcel Loss (Next-Day/2-Day)
+
+Same workflow as ground with these adjustments:
+- Tracer filing is faster: file same day as missed delivery. Guaranteed service
+ means the carrier prioritizes the investigation.
+- Money-back guarantee: for late delivery on guaranteed services, file for full
+ shipping cost refund regardless of whether the product arrives the next day. This
+ is separate from a loss claim.
+- UPS and FedEx each have automated money-back guarantee claim portals. For late
+ NDA (Next Day Air), the refund is the full air shipping cost. These refunds can
+ be significant on heavy or multi-package shipments.
+
+#### 5.3.3 International Parcel Loss
+
+- Customs holds are the most common cause of apparent "loss" in international parcel.
+ Check customs status before filing a tracer.
+- International parcel claims involve both the origin country carrier and the
+ destination country carrier (or postal service). Filing is through the origin
+ carrier.
+- Liability is governed by the Universal Postal Convention (for postal services)
+ or the carrier's tariff (for UPS/FedEx/DHL international). UPS international
+ declared value cap is $50,000.
+- Allow 30–90 days for international claim resolution due to multi-country
+ investigation requirements.
+- For DDP (Delivered Duty Paid) shipments, you are responsible for duties/taxes
+ as part of the shipment value. Include these in the claim amount.
+
+### 5.4 Ocean Container Shortage Resolution
+
+#### 5.4.1 FCL (Full Container Load) Shortage
+
+Container delivered with fewer pieces than the packing list, despite the container
+seal being intact (or seal being different from the origin seal).
+
+**Resolution Workflow:**
+
+1. **At container unload:** Count every piece before signing the delivery receipt.
+ If the container is being unloaded at a CFS (Container Freight Station), ensure
+ the CFS provides a tally sheet.
+2. **Check the seal:** Compare the seal number on the container door to the seal
+ number on the bill of lading. If they match and are intact: the shortage likely
+ occurred at the origin (stuffing error). Carrier liability is weak — this is
+ a shipper/origin warehouse issue. If the seal is broken or does not match: carrier
+ liability is strong. Photograph the seal immediately.
+3. **File notice of shortage within 3 days** (COGSA requirement for concealed
+ shortage). File with the ocean carrier AND the party who delivered the container
+ (drayage company or terminal).
+4. **Hire a marine surveyor** if the shortage value exceeds $5,000. The surveyor's
+ report is the gold standard evidence for ocean claims. Cost: $800–$2,500
+ depending on the port and survey complexity.
+5. **Claim filing:** File against the ocean carrier under the bill of lading terms.
+ If the BL incorporates COGSA, liability is capped at $500 per package (a "package"
+ in FCL is typically interpreted as each carton, not the container). If you declared
+ a higher value on the BL, the higher value applies.
+6. **Recovery expectation:** FCL shortages with matching intact seals: 20–35%
+ recovery (carrier argues origin stuffing error). FCL shortages with broken/mismatched
+ seals: 65–80% recovery.
+
+#### 5.4.2 LCL (Less than Container Load) Shortage
+
+Product consolidated with other shippers' freight in a shared container. Shortages
+are more common due to additional handling at CFS facilities at both origin and
+destination.
+
+**Resolution Workflow:**
+
+1. **At CFS pickup/delivery:** Verify piece count against the house bill of lading
+ (not the master BL, which covers the full container). Annotate any discrepancy
+ on the CFS tally sheet and delivery receipt.
+2. **Identify the shortage point:** Was the shortage at origin CFS (loaded fewer
+ pieces), in transit, or at destination CFS (pieces misallocated to another
+ consignee's lot)? Request the CFS tally reports from both origin and destination.
+3. **Check for cross-allocation:** In LCL, your cargo may have been mistakenly
+ delivered to another consignee in the same container. Request the destination
+ CFS check all lots from the same container for over-shipment.
+4. **File claim with the NVOCC or freight forwarder** who issued your house bill
+ of lading. They are your contracting party. They will subrogate against the ocean
+ carrier or CFS operator as appropriate.
+5. **Recovery expectation:** LCL shortage claims take longer (90–180 days) and
+ recover at lower rates (30–50%) due to the difficulty of proving where in the
+ multi-handler chain the shortage occurred.
+
+### 5.5 Air Freight Damage Resolution
+
+#### 5.5.1 Airline Handling Damage
+
+Damage caused by the airline's cargo handling team during loading, transit, or
+unloading of the aircraft.
+
+**Resolution Workflow:**
+
+1. **At pickup from airline cargo terminal:** Inspect all pieces before signing the
+ cargo release. Note any damage on the release form with specific descriptions:
+ "carton #3 crushed on north face, contents exposed." Do not accept shipment
+ without noting the damage — once you sign clean, your concealed damage notice
+ window is only 14 days under Montreal Convention.
+2. **File written notice within 14 days** — this is a hard deadline. Miss it and
+ the claim is barred. Send notice to the airline's cargo claims department and to
+ the handling agent at the arrival airport.
+3. **Document the chain of custody:** Air freight often moves through multiple
+ handlers: origin forwarder → origin ground handler → airline → destination ground
+ handler → destination forwarder. Identify which handler had custody when the
+ damage occurred. The airline's internal damage reporting ("damage noted during
+ build-up/breakdown") is helpful — request it from the airline's cargo
+ department.
+4. **Liability under Montreal Convention:** 22 SDR/kg (approximately $30/kg). For
+ a 500 kg shipment, the maximum recovery is roughly $15,000 regardless of product
+ value. If your product value significantly exceeds the weight-based limit, you
+ should have purchased declared-value surcharge at booking (typically 0.50–0.75%
+ of the excess value). If you did not, recovery is capped at the Convention limit.
+5. **Recovery expectation:** Airline direct claims with proper documentation:
+ 65–80% of the applicable liability limit within 60–90 days.
+
+#### 5.5.2 Ground Handler Damage
+
+Damage caused by the ground handling company (Swissport, Menzies, WFS, dnata, etc.)
+that operates on behalf of the airline at the airport.
+
+**Resolution Workflow:**
+
+1. **Shipper files against the airline** — under Montreal Convention, the airline
+ is liable to the shipper regardless of whether the airline or the ground handler
+ caused the damage. The shipper does not need to prove which party handled the
+ freight at the time of damage.
+2. **Provide evidence to the airline** — the airline will conduct its own
+ investigation and may pursue the ground handler for indemnification. Providing
+ the airline with clear evidence (time-stamped photos, handling records, warehouse
+ receipt stamps) speeds the process.
+3. **If the airline denies** — they may argue the damage was pre-existing or caused
+ by inadequate packaging. Counter with origin photos, packaging specifications,
+ and the air waybill special handling instructions (e.g., "fragile," "this side up")
+ that the handler failed to follow.
+4. **Direct claim against ground handler:** In some cases, especially when the
+ airline is uncooperative, filing a direct claim against the ground handler under
+ local tort law is viable. Consult with an air cargo attorney — this is a
+ specialized area.
+
+### 5.6 Intermodal Liability Resolution
+
+#### 5.6.1 Determining Liability Between Rail and Dray
+
+Intermodal shipments involve at least two carriers: a drayage company (trucker) that
+picks up the container/trailer at the rail terminal and delivers to the consignee,
+and a railroad (BNSF, UP, CSX, NS, etc.) that performs the linehaul.
+
+**Resolution Workflow:**
+
+1. **Obtain the interchange records.** When the container moves from rail to dray
+ (or dray to rail), an interchange inspection is supposed to occur. The interchange
+ report documents the condition of the container and chassis at handoff. This
+ document determines liability allocation.
+
+2. **If damage is noted on the interchange report at rail-to-dray handoff:**
+ Rail is liable. File the claim with the railroad or the intermodal marketing
+ company (IMC) that booked the rail leg. Railroad claims are governed by the
+ Carmack Amendment for domestic intermodal.
+
+3. **If the interchange report is clean at rail-to-dray handoff, and damage is
+ found at delivery:** Drayage company is liable. The damage occurred during
+ the dray leg (local trucking from rail terminal to consignee). File with the
+ dray carrier.
+
+4. **If no interchange report exists** (common — many terminals skip this step):
+ Liability is disputed. Both the railroad and the dray will point at each other.
+ In this situation:
+ - File claims against both parties simultaneously.
+ - Provide the same evidence package to both.
+ - The party with the weaker defense will typically settle first.
+ - If neither settles: your claim is against the contracting party (whoever is
+ on your bill of lading), and they can subrogate against the other.
+
+5. **Railroad-specific considerations:**
+ - Railroads have their own claims rules and are notoriously slow (90–180 days
+ for resolution).
+ - Impact damage (shifting during railcar coupling, hard stops, derailment) is
+ common. Railroads have internal impact recording devices — request the data.
+ - Temperature damage on reefer intermodal: the rail carrier is responsible for
+ maintaining the reefer unit during rail transit if GenSet service was purchased.
+ If you provided a self-powered reefer unit, the rail carrier may argue the
+ unit failed on its own.
+
+6. **Chassis damage vs. cargo damage:** If the chassis (the wheeled frame the
+ container sits on) was damaged, causing the container to tilt or drop, this is
+ typically a rail terminal or dray carrier issue depending on where the chassis
+ was sourced. Chassis pool operators (DCLI, TRAC, Flexi-Van) may also be liable.
+ This creates a three-party dispute — carrier, chassis pool, and terminal operator.
+
+---
+
+## 6. Escalation Matrix
+
+### 6.1 Internal Escalation — Who, When, How
+
+| Severity / Trigger | Escalation Target (Role) | Information Required | Channel | Expected Response Time | Follow-Up Cadence |
+|--------------------|--------------------------|---------------------|---------|----------------------|-------------------|
+| Level 1 exception, no resolution after 48 hrs | Exception Team Lead | Exception summary, carrier contact log, current status | Email (team queue) or Slack/Teams channel | 4 business hours | Daily until resolved |
+| Level 2 exception, no resolution after 24 hrs | Exception Team Lead | Exception summary, financial impact estimate, carrier response history | Email with priority flag + verbal heads-up | 2 business hours | Every 8 hours |
+| Level 3 exception at intake | Exception Manager | Full exception brief: financial impact, customer impact, timeline, carrier status, recommended action | Phone call + email follow-up within 30 min | 1 hour | Every 4 hours |
+| Level 4 exception at intake | Director of Logistics / Director of Customer Operations | Executive summary: TEC calculation, customer risk, recommended action with cost estimate, alternatives considered | Phone call first, then email to director + CC manager | 30 minutes | Every 2 hours |
+| Level 5 exception at intake | VP Supply Chain + VP Sales (if customer-facing) | One-page executive brief: situation, financial exposure, customer impact, recommended immediate action, resource needs | Phone call to VP, then email summary to VP + director + manager. Schedule war-room call within 1 hour | 15 minutes | Continuous (war room) until stabilized, then every hour |
+| Carrier non-response after 4 hrs | Procurement / Carrier Management Analyst | Carrier name, MC#, exception details, all contact attempts with timestamps | Email to carrier management team | 4 business hours | Once (they own the carrier relationship escalation) |
+| Carrier non-response after 24 hrs | Procurement Manager / Director of Transportation | All of above + recommended financial leverage (invoice hold, lane removal) | Phone + email | 2 business hours | Daily until resolved |
+| Carrier claims denial > $10,000 | Legal / Risk Management Counsel | Complete claim file: claim filing, carrier denial, rebuttal sent, all evidence, financial exposure | Email with claim file attached + meeting request within 48 hrs | 48 hours for initial review | Weekly until disposition decided |
+| Customer escalation (customer contacts their account manager or executive) | Sales Account Manager + Exception Manager | Current exception status, all actions taken, timeline of communications, what we need from the customer | Immediate phone call to account manager + email brief | 30 minutes | Match the customer's requested cadence (usually every 4–8 hours) |
+| Potential fraud or compliance concern | Compliance Officer / Internal Audit | All available evidence, basis for suspicion, parties involved, recommended hold actions | Confidential email to compliance (do not discuss on open channels) | 4 business hours | As directed by compliance |
+| Regulatory reporting event (hazmat, food safety, pharma) | Quality/Regulatory Affairs Manager + Legal | Product details, exception specifics, regulatory exposure assessment, recommended agency notifications | Phone call immediately + email within 30 min | 15 minutes | Continuous until regulatory obligations met |
+
+### 6.2 External Escalation — Carrier-Side Contacts
+
+| Escalation Level | Carrier Contact (Title) | When to Engage | What to Say | Expected Outcome |
+|-----------------|------------------------|---------------|-------------|-----------------|
+| Level 1 | Carrier Customer Service / Dispatch Agent | First contact for any exception | State the exception, provide references, request status and ETA | Information and initial action |
+| Level 2 | Operations Supervisor / Terminal Manager | When Level 1 is unresponsive (2 hrs) or unable to resolve | Reference the open case number, state the business impact, request supervisor intervention | Escalated attention, possible override of standard process |
+| Level 3 | Regional Operations Director or VP Operations | When 2+ business days with no resolution, or high-value exception | Formal email referencing all prior communications, stating financial exposure and expected resolution | Direct oversight, dedicated resource assigned |
+| Level 4 | Carrier Account Manager / Director of Sales | When operational channels have failed and you need a business relationship lever | Contact through your procurement team. Frame as "this unresolved exception is affecting our routing decisions for this carrier" | Carrier sales team pressures their operations to resolve, often yields fastest results |
+| Level 5 | Carrier CEO / General Counsel | Litigation-track only, or when all other paths exhausted on high-value claim | Formal demand letter from your legal counsel to carrier's registered agent or general counsel | Legal posture established, settlement negotiation begins |
+
+### 6.3 External Escalation — Third Parties
+
+| Party | When to Engage | Contact Method | Cost | Expected Outcome |
+|-------|---------------|---------------|------|-----------------|
+| Independent marine / cargo surveyor | Damage claim > $5,000, or any disputed damage | Engage through your insurance broker's surveyor network, or directly via NAMS (National Association of Marine Surveyors) | $800–$2,500 per survey (domestic); $1,500–$5,000 (international) | Independent damage assessment report admissible in claims and litigation |
+| Third-party claims management firm | When internal claims volume exceeds capacity, or for complex multi-modal claims | Contract through RFP or direct engagement. Major firms: CIS (Claims Information Services), TranSolutions, NovaTrans | Contingency fee 25–33% of recovery, or flat fee $200–$800 per claim depending on complexity | Professional claims handling with higher recovery rates (typically 10–15% higher than in-house for complex claims) |
+| Freight claims attorney | Denied claims > $25,000, or any claim heading to litigation | Engage through industry referral (Transportation Intermediaries Association, Transportation Lawyers Association) | Contingency 25–33%, or hourly $250–$450 for pre-litigation work | Legal demand, negotiation, or litigation |
+| FMCSA (Federal Motor Carrier Safety Administration) | Carrier safety violations, out-of-service carrier, registration issues | File complaint online at NCCDB (National Consumer Complaint Database) or call 1-888-368-7238 | Free | Investigation of carrier safety record; public record |
+| STB (Surface Transportation Board) | Rate disputes, service complaints against railroads, intermodal disputes that cannot be resolved commercially | File formal complaint with the STB | Filing fees vary; legal representation recommended | Regulatory review and potential order against carrier |
+| Cargo insurance underwriter | Any loss exceeding your self-insured retention (SIR), or any total loss on insured shipment | Notify per your policy terms (typically within 30 days of loss discovery). Contact your insurance broker first | Claim against your own policy; subject to deductible and SIR | Insurance recovery minus deductible. Insurer may subrogate against carrier |
+
+---
+
+## 7. Time-Based Decision Triggers
+
+### 7.1 Checkpoint Framework
+
+This framework defines what decisions must be made and what actions must be taken at
+specific time intervals from exception intake. "Intake" is when the exception is first
+identified, regardless of when it actually occurred.
+
+#### Checkpoint: 2 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Severity classified? | Must have a score. If insufficient information to score, default to one level above what you suspect and gather data to confirm/downgrade |
+| Carrier contacted? | Initial contact must be made. If unable to reach carrier at 2 hrs, this is now Path B (Unresponsive) |
+| Customer notification needed? | Level 3+: customer must be notified by this checkpoint. Level 1–2: only if customer has already inquired |
+| Expedite decision needed? | If time sensitivity is Level 4+, the expedite vs. wait decision cannot wait past this checkpoint. Authorize or decline |
+| Is this a pattern? | Quick check: same carrier, same lane, same customer in last 30 days? If yes, apply elevation modifier |
+
+#### Checkpoint: 4 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Carrier response received? | If no response: escalate to carrier operations supervisor. Switch to Path B protocol |
+| Resolution timeline established? | Carrier should have provided a plan and timeline. If not: this is a carrier performance failure in addition to the original exception |
+| Internal escalation needed? | Level 3+: manager should be aware by now. Level 4+: director must be briefed |
+| Customer update #2 | For Level 3+: provide update even if no new information — silence is worse than "we're still working on it" |
+| Backup plan activated? | For time-sensitive exceptions: backup carrier or expedite method should be identified and on standby |
+
+#### Checkpoint: 8 Hours Post-Intake (End of Business Day)
+
+| Decision | Detail |
+|----------|--------|
+| Will this resolve today? | Honest assessment. If not: set next-day actions and ensure overnight monitoring for Level 4+ |
+| Financial impact calculated? | Full TEC should be computed by this point for Level 3+ exceptions |
+| Documentation gathered? | Photos, POD, BOL — everything needed for a claim should be in hand or requested with a deadline |
+| Customer expectation set? | Customer should have a specific revised delivery date or resolution timeline. Do not give "TBD" past 8 hours |
+| After-hours coverage needed? | For Level 4+: assign after-hours on-call responsibility. Provide the on-call person with a complete brief |
+
+#### Checkpoint: 24 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Resolution achieved? | Level 1–2 exceptions should be resolved or near-resolution by 24 hrs. If not: why? |
+| Claim filing decision made? | For damage/shortage/loss: you should know by now whether you are filing a claim, negotiating, or absorbing |
+| Carrier accountability documented? | Regardless of resolution, the carrier's performance on this exception must be logged for scorecard purposes |
+| Customer satisfaction check | For Level 3+: brief check-in with the customer. Are they satisfied with the resolution or progress? Adjust if needed |
+| Aging alert set | If not resolved: ensure the exception is in the "aging" report and will be reviewed at the next team stand-up |
+
+#### Checkpoint: 48 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Escalation review | Any exception open 48 hrs without clear resolution path: escalate to the next level in the chain, regardless of severity |
+| Claim filed? | If claim was warranted, it should be filed by now. Every day of delay weakens the claim (evidence degrades, carrier disputes increase) |
+| Root cause identified? | Even if the exception is not fully resolved, the root cause should be understood. If not: dedicate analytical resource to determine it |
+| Carrier relationship impact assessed? | Procurement/carrier management should have a view on whether this carrier needs a corrective action discussion |
+
+#### Checkpoint: 72 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Resolution or plan | Exception must be either resolved OR have a documented resolution plan with a specific completion date |
+| Management review | All exceptions open > 72 hrs should be on the manager's weekly review report |
+| Customer mitigation complete? | Any customer-facing mitigation (re-ship, credit, expedite) should be completed by this point. The customer should not be waiting |
+
+#### Checkpoint: 5 Business Days
+
+| Decision | Detail |
+|----------|--------|
+| Concealed damage window closing | 5 days is the industry-standard window for concealed damage claims. If damage was discovered post-delivery, the claim must be filed by this point |
+| Team lead review | Team lead should review any exception open 5 days and assess whether it is being handled efficiently or is stuck |
+
+#### Checkpoint: 10 Business Days
+
+| Decision | Detail |
+|----------|--------|
+| Claim acknowledgment received? | If claim was filed, carrier must acknowledge within 30 days (per 49 CFR § 370.9), but should acknowledge within 10 business days. If not: follow up formally |
+| Exception aging report | 10-day open exceptions should appear on the manager-level report with a status update required |
+
+#### Checkpoint: 30 Calendar Days
+
+| Decision | Detail |
+|----------|--------|
+| Claim acknowledgment mandatory deadline | 30 days is the carrier's regulatory deadline to acknowledge a domestic claim. If not acknowledged: send formal notice citing 49 CFR § 370.9 and state that failure to comply is a regulatory violation |
+| Financial write-off or reserve decision | For unresolved claims: finance team should either reserve the claim amount or write it off, depending on recovery probability assessment |
+| Carrier performance review trigger | Any carrier with an exception open 30 days without resolution should be in a formal performance review conversation |
+
+### 7.2 Checkpoint Failure Protocol
+
+When a checkpoint decision is not made or action not taken by the deadline:
+
+1. **Immediate notification** to the next level in the escalation chain.
+2. **Root cause of the miss:** Was it capacity (analyst overwhelmed), information
+ (waiting on carrier/customer), process (no clear owner), or judgment (analyst
+ unsure how to proceed)?
+3. **Recovery action:** Assign fresh eyes. A different analyst reviews the exception
+ and picks up from the current state. Stale exceptions tend to stay stale with
+ the same handler.
+4. **Process improvement:** If the same checkpoint is repeatedly missed across
+ multiple exceptions, this is a systemic issue requiring process or staffing
+ review.
+
+---
+
+## 8. Multi-Exception Triage Protocol
+
+### 8.1 When to Activate Triage Mode
+
+Activate formal triage when any of these conditions are met:
+
+- 5+ new exceptions in a single 4-hour window
+- 3+ Level 3+ exceptions active simultaneously
+- A widespread disruption event (weather system, carrier outage, port closure, major highway closure) is generating exceptions faster than the team can process individually
+- Peak season daily exception volume exceeds 150% of the 30-day rolling average
+
+### 8.2 Triage Commander Role
+
+Designate a single **triage commander** (typically the team lead or the most senior
+analyst available) who:
+
+- Stops working individual exceptions.
+- Takes ownership of triage decisions: who works what, in what order.
+- Provides a single point of status aggregation for management and customer-facing
+ teams.
+- Has authority to re-assign analyst workloads, authorize expedites up to a
+ pre-approved threshold ($10,000 per incident without additional approval), and
+ communicate directly with carrier account managers and customer account teams.
+
+### 8.3 Triage Scoring — Rapid Prioritization
+
+When volume overwhelms the standard severity matrix process, use this rapid
+triage scoring:
+
+| Factor | Score 3 (Highest Priority) | Score 2 | Score 1 (Lowest Priority) |
+|--------|---------------------------|---------|--------------------------|
+| Time to customer impact | < 8 hours | 8–48 hours | > 48 hours |
+| Product at risk | Perishable, hazmat, pharma | High-value non-perishable (> $25K) | Standard product < $25K |
+| Customer tier | Enterprise / penalty contract | Key account | Standard |
+| Resolution complexity | Requires multi-party coordination | Single carrier, single action needed | Self-resolving (e.g., weather clearing) |
+| Can it wait 4 hours? | No — irreversible damage if delayed | Probably, but will cost more | Yes, no penalty for delay |
+
+Sum the scores (max 15). Process exceptions in descending score order.
+Ties are broken by: (1) regulatory/safety always wins, (2) then highest dollar
+value, (3) then oldest exception.
+
+### 8.4 Triage Communication Protocol
+
+During a triage event:
+
+**Internal:**
+- Triage commander sends a status update to management every 2 hours (or more
+ frequently if Level 5 exceptions are active).
+- Status update format: total exceptions active, top 3 by priority with one-line
+ status each, resource utilization (analysts assigned / available), estimated
+ clearance timeline.
+- Each analyst provides a 2-sentence status on each assigned exception every 2
+ hours to the triage commander.
+
+**Customer-facing:**
+- For widespread events (weather, carrier outage): issue a single proactive
+ communication to all affected customers rather than individual reactive updates.
+ Template: "We are aware of [event]. [X] shipments are potentially affected.
+ We are actively working with carriers to reroute/recover. Your account team
+ will provide individual shipment updates within [X] hours."
+- For individual high-priority exceptions during triage: customer update cadence
+ does not change (per severity level). The triage commander ensures high-priority
+ customer updates are not missed because the analyst is overwhelmed.
+
+**Carrier:**
+- During widespread events, contact the carrier's account manager or VP of
+ Operations (not dispatch) to get a single point of contact for all affected
+ shipments. Working shipment-by-shipment through dispatch during a triage event
+ is inefficient.
+- Request a carrier-side recovery plan for all affected shipments as a batch.
+
+### 8.5 Resource Allocation During Triage
+
+| Exception Priority (Triage Score) | Analyst Allocation | Manager Involvement | Customer Communication |
+|-----------------------------------|--------------------|--------------------|-----------------------|
+| Score 13–15 (Critical) | Dedicated senior analyst, 1:1 ratio | Direct manager oversight | VP or account director handles |
+| Score 10–12 (High) | Senior analyst, up to 3:1 ratio | Manager briefed every 2 hours | Account manager handles |
+| Score 7–9 (Medium) | Analyst, up to 5:1 ratio | Included in batch status report | Standard proactive template |
+| Score 4–6 (Low) | Deferred or batch-processed | No individual oversight | Reactive only (respond if customer asks) |
+
+### 8.6 Triage Deactivation
+
+Deactivate triage mode when:
+- Active exception count drops below 5
+- No Level 3+ exceptions remain unresolved
+- New exception intake rate returns to within 120% of the 30-day rolling average
+- All high-priority customer impacts are resolved or mitigated
+
+Conduct a triage debrief within 48 hours of deactivation: what went well, what
+broke, what needs to change for next time.
+
+---
+
+## 9. Eat-the-Cost Analysis Framework
+
+### 9.1 Decision Model
+
+The eat-the-cost decision determines whether pursuing a claim or dispute recovery
+generates a positive return after all costs — financial, temporal, and relational —
+are considered.
+
+```
+Net Recovery Value (NRV) = (Claim Amount × Recovery Probability × Time-Value Discount)
+ - Processing Cost
+ - Opportunity Cost
+ - Relationship Cost
+
+If NRV > 0 and NRV / Claim Amount > 15%: FILE
+If NRV > 0 but NRV / Claim Amount < 15%: FILE only if pattern documentation needed
+If NRV ≤ 0: ABSORB and log for carrier scorecard
+```
+
+### 9.2 Component Calculations
+
+#### Processing Cost by Complexity Tier
+
+| Tier | Criteria | Internal Hours | External Cost | Total Estimated Cost |
+|------|----------|---------------|--------------|---------------------|
+| A — Automated | Parcel claim via portal, simple damage with clear POD notation | 0.5 hrs ($23) | $0 | $23 |
+| B — Simple | LTL damage with good documentation, cooperative carrier, value < $2,500 | 2–3 hrs ($90–$135) | $0 | $90–$135 |
+| C — Standard | FTL damage/loss, value $2,500–$10,000, standard claim process | 5–8 hrs ($225–$360) | $0 | $225–$360 |
+| D — Complex | Multi-party dispute, ocean/air with international filing, disputed liability | 12–20 hrs ($540–$900) | Surveyor $800–$2,500 | $1,340–$3,400 |
+| E — Litigation-track | Denied claim heading to legal, value > $25,000 | 30–60 hrs ($1,350–$2,700) | Attorney $5,000–$25,000+ | $6,350–$27,700+ |
+
+#### Recovery Probability Adjustments
+
+Start with the base recovery probabilities from §4.2 and adjust:
+
+| Factor | Adjustment |
+|--------|-----------|
+| Documentation is complete and clean (photos, clean BOL, noted POD) | +10% |
+| Documentation is incomplete (missing photos or POD unsigned) | -15% |
+| Carrier has a history of paying claims promptly | +5% |
+| Carrier has a history of denying or slow-walking claims | -10% |
+| Claim is filed within 7 days of delivery | +5% |
+| Claim is filed 30+ days after delivery | -10% |
+| Independent survey/inspection supports the claim | +15% |
+| Product is temperature-controlled with continuous logger data | +10% (if data supports excursion) or -25% (if data is ambiguous or missing) |
+
+#### Time-Value Discount
+
+Claims take time. The money recovered 120 days from now is worth less than money
+in hand today.
+
+```
+Time-Value Discount Factor = 1 / (1 + (annual_cost_of_capital × estimated_days_to_recovery / 365))
+
+Typical: annual cost of capital = 8-12%
+```
+
+| Estimated Days to Recovery | Discount Factor (at 10% annual) |
+|---------------------------|-------------------------------|
+| 30 days | 0.992 |
+| 60 days | 0.984 |
+| 90 days | 0.976 |
+| 120 days | 0.968 |
+| 180 days | 0.953 |
+| 365 days | 0.909 |
+
+For most claims, the time-value discount is small (1–5%) and rarely drives the
+decision. It matters most for large claims (> $50K) with long expected resolution
+timelines (> 180 days).
+
+#### Opportunity Cost
+
+Every hour an analyst spends on a low-value claim is an hour not spent on a
+higher-value exception. Estimate:
+
+```
+Opportunity Cost = Processing Hours × (Average Exception Value Recovered per Analyst Hour - $45 blended labor cost)
+
+Typical: An experienced analyst recovers ~$1,200 per hour of claims work (blended across all claim sizes).
+Opportunity Cost ≈ Processing Hours × ($1,200 - $45) = Processing Hours × $1,155
+```
+
+This is the most often overlooked component. Filing a $500 claim that takes 4 hours
+to process costs the organization 4 × $1,155 = $4,620 in recoveries NOT pursued
+on other higher-value exceptions.
+
+However, this applies only when the analyst has a backlog of higher-value work.
+During low-volume periods, opportunity cost approaches zero and the threshold for
+filing drops.
+
+#### Relationship Cost
+
+This is the qualitative overlay. Assign one of these values:
+
+| Carrier Relationship Status | Relationship Cost Factor |
+|----------------------------|------------------------|
+| New carrier (< 6 months), building relationship | $500 imputed cost — filing a claim this early sends a signal. Absorb small claims if possible and address in the quarterly review |
+| Established carrier (6+ months), good relationship | $0 — professional carriers expect claims as part of the business. Filing does not damage the relationship if done respectfully |
+| Strategic carrier (top 5 by spend, or sole-source on critical lanes) | $250 imputed cost — even though the relationship is strong enough to handle claims, there is a negotiation overhead and quarterly review complexity |
+| Carrier under corrective action or on probation | Negative cost: -$200 (i.e., filing the claim is relationship-positive because it creates the documentation trail needed for contract renegotiation or termination) |
+
+### 9.3 Worked Examples
+
+#### Example: Should We File This $850 LTL Damage Claim?
+
+```
+Claim Amount: $850
+Carrier: National LTL, established relationship (18 months)
+Documentation: Complete (clean BOL, noted POD, photos)
+Complexity: Tier B (Simple)
+Base Recovery Prob: 85% (national LTL, visible damage noted on POD)
+Adjustments: +10% (complete documentation) → 95% (cap at 95%)
+
+Processing Cost: 2.5 hrs × $45 = $113
+Opportunity Cost: During peak season, analyst backlog is high →
+ 2.5 hrs × $1,155 = $2,888
+ During slow season (January): $0
+
+Relationship Cost: $0 (established, good relationship)
+Time-Value: 60-day expected resolution → discount factor 0.984
+
+NRV (peak season) = ($850 × 0.95 × 0.984) - $113 - $2,888 - $0
+ = $794 - $113 - $2,888 = -$2,207 → DO NOT FILE
+
+NRV (slow season) = ($850 × 0.95 × 0.984) - $113 - $0 - $0
+ = $794 - $113 = $681 → FILE (NRV/Claim = 80%)
+```
+
+During peak season, the analyst's time is better spent on higher-value
+exceptions. During slow season, file it — the analyst has bandwidth.
+
+#### Example: Should We File This $3,200 FTL Shortage Claim Against a Small Carrier?
+
+```
+Claim Amount: $3,200
+Carrier: Small asset carrier (12 trucks), 8-month relationship
+Documentation: Incomplete — POD was signed clean (driver left before
+ count completed), shortage discovered 1 hour later
+Base Recovery Prob: 55% (small FTL carrier, shortage)
+Adjustments: -15% (clean POD) → 40%
+Complexity: Tier C (Standard)
+
+Processing Cost: 6 hrs × $45 = $270
+Opportunity Cost: 6 hrs × $1,155 = $6,930 (peak), $0 (slow)
+Relationship Cost: $500 (relatively new carrier)
+Time-Value: 120-day expected → 0.968
+
+NRV (peak) = ($3,200 × 0.40 × 0.968) - $270 - $6,930 - $500
+ = $1,239 - $270 - $6,930 - $500 = -$6,461 → DO NOT FILE
+
+NRV (slow) = ($3,200 × 0.40 × 0.968) - $270 - $0 - $500
+ = $1,239 - $270 - $500 = $469 → MARGINAL
+
+Filing Ratio = $469 / $3,200 = 14.7% → BELOW 15% threshold → ABSORB
+```
+
+Even in the slow season, the low recovery probability (due to the clean POD)
+makes this a marginal claim. Decision: absorb, but use this as a coaching
+moment with the consignee about never signing clean before completing the count.
+Log for carrier scorecard. If it happens again with the same carrier, the pattern
+changes the calculus — file the second claim and reference both incidents.
+
+---
+
+## 10. Seasonal Adjustment Factors
+
+### 10.1 Peak Season Adjustments (October–January)
+
+During peak season, carrier networks are strained, transit times extend, exception
+rates increase 30–50%, and claims departments slow down. Adjust decision frameworks
+accordingly.
+
+| Parameter | Standard Setting | Peak Season Adjustment | Rationale |
+|-----------|-----------------|----------------------|-----------|
+| Carrier response SLA (before escalation) | 2 hours | 4 hours | Carrier dispatch is overwhelmed; allow more time before declaring unresponsive |
+| Customer notification threshold | Level 3+ proactive | Level 2+ proactive | Customer expectations are already fragile during peak; proactive communication prevents inbound complaint calls |
+| Expedite authorization threshold | Manager approval > $5,000 | Manager approval > $10,000 | Expedite costs are inflated 50–100% during peak; air capacity is scarce. Raise the bar for what justifies a premium expedite |
+| Eat-the-cost threshold | < $500 absorb | < $750 absorb | APC increases during peak (analysts are juggling more exceptions). Internal cost of claims processing rises |
+| Claims filing timeline | Within 5 business days | Within 10 business days | Realistic given volume. Still well within the 9-month Carmack window |
+| Carrier scorecard impact weight | Standard | 0.75× weighting | Across-the-board service degradation during peak is industry-wide. Do not penalize carriers disproportionately for systemic conditions, but still document everything |
+| Triage mode activation threshold | 5+ simultaneous exceptions | 8+ simultaneous (expect a higher baseline) | Baseline exception volume is higher; activate triage based on deviation from the elevated baseline |
+| Customer communication frequency (active exceptions) | Every 4 hours for Level 3+ | Every 8 hours for Level 3+ | Volume requires longer update cycles. Communicate the adjusted cadence to customer upfront: "During the holiday shipping season, we'll provide updates every 8 hours unless there is a material change" |
+| Settlement acceptance threshold | > 75% for $500–$2,500 range | > 65% for $500–$2,500 range | Faster settlement frees capacity for higher-value claims. Accept slightly lower recoveries to close volume |
+
+### 10.2 Weather Event Adjustments
+
+Applied when a named weather system (winter storm, hurricane, tropical storm) or
+widespread severe weather (tornado outbreak, flooding) is actively disrupting a
+region.
+
+| Parameter | Standard Setting | Weather Event Adjustment | Duration |
+|-----------|-----------------|------------------------|----------|
+| Carrier response SLA | 2 hours | 8 hours (carrier dispatch may be evacuated or overwhelmed) | Until 48 hours after last weather advisory expires |
+| Force majeure acceptance | Require specific documentation | Accept carrier's force majeure claim if weather event is confirmed by NOAA for the route and timeframe | Event duration + 72 hours recovery |
+| Expedite decisions | Standard ROI calculation | Suspend expedite for affected lanes until roads/airports reopen. Redirect expedite spend to alternative routing | Until carrier confirms lane is clear |
+| Customer communication | Standard cadence per severity | Issue blanket proactive communication to all customers with shipments on affected lanes. Individual follow-ups only for Level 4+ | Until all affected shipments are rescheduled |
+| Exception severity scoring | Standard matrix | Reduce time-sensitivity dimension by 1 level for weather-affected shipments (customer tolerance is higher for force majeure events) | Event duration + 24 hours |
+| Claim filing | Standard timeline | Delay claim filing for weather events; focus on recovery and rerouting. File after the event when full impact is known | File within 30 days of delivery/non-delivery |
+| Carrier scorecard | Standard weighting | 0.5× weighting for weather-affected lanes. Document for pattern tracking but do not penalize individual events | Exceptions within the event window only |
+
+### 10.3 Produce / Perishable Season Adjustments (April–September)
+
+Temperature-sensitive shipments increase dramatically. Reefer capacity tightens.
+Temperature exceptions spike.
+
+| Parameter | Standard Setting | Produce Season Adjustment | Rationale |
+|-----------|-----------------|--------------------------|-----------|
+| Temperature excursion response time | 2 hours to contact carrier | 1 hour to contact carrier | Perishable shelf life is non-recoverable. Every hour of delay in response reduces the salvageable value |
+| Pre-trip inspection documentation | Recommended | Required — do not load without confirmed pre-trip on reefer unit | Carrier defense #1 is "reefer was fine at dispatch; product was loaded warm." Pre-trip eliminates this |
+| Continuous temperature logging | Required for pharma/biotech | Required for ALL perishable shipments including produce, dairy, frozen food | Carrier disputes on temperature are unresolvable without continuous data |
+| Reefer breakdown escalation | 4 hours before power-swap demand | 2 hours before power-swap demand | Product degradation accelerates with ambient temperature. In July, a reefer failure in Phoenix means product loss in under 2 hours |
+| Carrier reefer fleet age threshold | Accept carriers with reefer units < 10 years old | Prefer carriers with reefer units < 5 years old during peak produce season | Older reefer units fail at higher rates in extreme heat |
+| Claim documentation for temperature | Standard photo + logger | Add: pre-cool records, loading temperature readings (infrared gun logs), in-transit monitoring alerts, reefer unit download data | Temperature claims require more evidence than any other claim type. Produce buyers and carriers both dispute aggressively |
+
+### 10.4 Month-End / Quarter-End Adjustments
+
+The last 5 business days of any month (and especially quarter) see volume spikes,
+carrier tender rejections, and increased exception rates as shippers rush to meet
+revenue recognition deadlines.
+
+| Parameter | Standard Setting | Month/Quarter-End Adjustment | Rationale |
+|-----------|-----------------|------------------------------|-----------|
+| Backup carrier readiness | Pre-identified for top 20 lanes | Pre-identified and confirmed available for top 50 lanes | Tender rejection rates spike 25–40% at month-end. Having confirmed backup capacity prevents scrambling |
+| Tender rejection response time | 2 hours to re-tender | 1 hour to re-tender | Every hour matters when the month is closing. Spot market tightens through the day |
+| Spot market premium approval | Manager approval > 20% over contract rate | Manager pre-approval up to 35% over contract rate | Speed of authorization matters more than cost optimization at month-end. Pre-authorize higher thresholds |
+| Double-brokering verification | Standard onboarding check | Enhanced verification for any new or infrequent carrier used at month-end: confirm MC#, confirm truck matches BOL, confirm driver identity | Double-brokering spikes when capacity is tight and brokers scramble to cover loads they've committed |
+| Exception reporting frequency | Daily summary | Twice-daily summary (midday and close of business) to operations leadership | Executives need real-time visibility into end-of-period exceptions that could affect revenue or delivery commitments |
+
+### 10.5 Adjustment Interaction Rules
+
+When multiple seasonal adjustments are active simultaneously (e.g., peak season +
+weather event in December):
+
+1. Apply the **more permissive** adjustment for carrier-facing parameters (response
+ SLAs, scorecard weighting). Do not stack — use the adjustment that grants the
+ carrier the most latitude.
+2. Apply the **more conservative** adjustment for customer-facing parameters
+ (notification thresholds, communication frequency). If peak says "Level 2+
+ proactive" and weather says "blanket communication to all affected," use the
+ blanket communication.
+3. Apply the **lower** eat-the-cost threshold (i.e., absorb more). Overlapping
+ stress periods mean higher APC and lower recovery probabilities.
+4. Internal escalation thresholds remain at the **tighter** of any applicable
+ adjustment. Overlapping stress events mean higher risk, not lower.
+5. Document which adjustments are active and communicate to the team. A triage
+ event during peak season with active weather is a different operating posture
+ than normal operations — everyone must be calibrated to the same adjusted
+ thresholds.
+
+---
+
+## Appendix A — Quick-Reference Decision Cards
+
+### Card 1: "Should I escalate this?"
+
+```
+IF severity ≥ 3 → YES, to manager
+IF severity ≥ 4 → YES, to director
+IF severity = 5 → YES, to VP
+IF carrier non-response > 4 hrs → YES, to carrier ops supervisor
+IF carrier non-response > 24 hrs → YES, to carrier account manager + your procurement
+IF customer has called about it → YES, to at least team lead
+IF it smells like fraud → YES, to compliance immediately
+```
+
+### Card 2: "Should I file this claim?"
+
+```
+IF value < $250 and portal available → FILE (automated, low effort)
+IF value < $500 and no portal → ABSORB unless it is a pattern
+IF value $500–$2,500 → RUN NRV CALC (see §9)
+IF value > $2,500 → FILE regardless
+IF this is the 3rd+ incident same carrier 90 days → FILE and flag for carrier review
+IF documentation is weak (no POD notation, no photos) → NEGOTIATE informally first, file only if carrier acknowledges liability
+```
+
+### Card 3: "Should I expedite a replacement?"
+
+```
+IF customer impact ≥ Level 4 → YES, authorize now, sort out cost later
+IF customer impact = Level 3 → CALCULATE: expedite cost vs. customer penalty + relationship damage
+IF customer impact ≤ Level 2 → STANDARD re-ship unless customer specifically requests
+IF product is perishable and original is salvageable → DO NOT re-ship; instead reroute or discount the original
+IF product is custom/irreplaceable → EXPEDITE the manufacturing queue, not just the shipping
+```
+
+### Card 4: "What do I do first when 10 exceptions land at once?"
+
+```
+1. ACTIVATE triage mode
+2. SCORE each exception using rapid triage (§8.3) — takes ~2 min per exception
+3. SORT by score descending
+4. ASSIGN: top 3 to senior analysts (1:1), next 4 to analysts (2:1), bottom 3 to batch queue
+5. COMMUNICATE: send blanket status to customer teams, single contact to carrier account managers
+6. UPDATE triage commander every 2 hours
+7. DEACTIVATE when active count < 5 and no Level 3+ remain
+```
+
+---
+
+## Appendix B — Acronyms and Glossary
+
+| Term | Definition |
+|------|-----------|
+| APC | Administrative Processing Cost — internal labor cost to handle an exception |
+| ASN | Advanced Shipping Notice — EDI 856 document notifying customer of incoming shipment |
+| BOL / BL | Bill of Lading — the shipping contract between shipper and carrier |
+| CFS | Container Freight Station — warehouse at a port where LCL cargo is consolidated/deconsolidated |
+| COGSA | Carriage of Goods by Sea Act — US statute governing ocean carrier liability |
+| DRC | Downstream Ripple Cost — secondary costs caused by the exception |
+| ELD | Electronic Logging Device — required device tracking driver hours of service |
+| ERC | Expedite / Re-Ship Cost — cost to recover from the exception via expedited shipment |
+| FCL | Full Container Load — ocean shipping where one shipper uses the entire container |
+| FMCSA | Federal Motor Carrier Safety Administration — US agency regulating trucking |
+| FTL | Full Truckload — one shipper, one truck, dock-to-dock |
+| HOS | Hours of Service — FMCSA regulations limiting driver driving/on-duty time |
+| IMC | Intermodal Marketing Company — broker of intermodal (rail+truck) services |
+| JIT | Just-In-Time — manufacturing/supply chain strategy with minimal inventory buffers |
+| LCL | Less than Container Load — ocean shipping where multiple shippers share a container |
+| LTL | Less than Truckload — shared carrier network with terminal cross-docking |
+| MC# | Motor Carrier number — FMCSA-issued operating authority identifier |
+| NFO | Next Flight Out — expedited air freight on the next available commercial flight |
+| NRV | Net Recovery Value — expected financial return from pursuing a claim |
+| NVOCC | Non-Vessel Operating Common Carrier — freight intermediary in ocean shipping |
+| OS&D | Over, Short & Damage — carrier department handling freight exceptions |
+| OTIF | On Time In Full — delivery performance metric |
+| PL | Product Loss — value of product damaged, lost, or shorted |
+| POD | Proof of Delivery — signed delivery receipt |
+| PRO# | Progressive Rotating Order number — carrier's shipment tracking number (LTL) |
+| QBR | Quarterly Business Review — periodic meeting between shipper and carrier/customer |
+| RDE | Relationship Damage Estimate — imputed cost of relationship harm from exception |
+| SDR | Special Drawing Rights — IMF currency unit used in international transport liability limits |
+| SIR | Self-Insured Retention — amount the shipper pays before insurance coverage applies |
+| SL&C | Shipper Load & Count — BOL notation indicating carrier did not verify the load |
+| STB | Surface Transportation Board — US agency with jurisdiction over rail and some intermodal disputes |
+| TEC | Total Exception Cost — comprehensive cost of an exception including all components |
+| TMS | Transportation Management System — software for managing freight operations |
+| WMS | Warehouse Management System — software for managing warehouse operations |
diff --git a/skills/logistics-exception-management/references/edge-cases.md b/skills/logistics-exception-management/references/edge-cases.md
new file mode 100644
index 00000000..5c226792
--- /dev/null
+++ b/skills/logistics-exception-management/references/edge-cases.md
@@ -0,0 +1,734 @@
+# Logistics Exception Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous exceptions that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced exception management professionals from everyone else. Each one involves competing claims, ambiguous liability, time pressure, and real financial exposure. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When an exception doesn't fit a clean category — when liability is genuinely unclear, when multiple parties have plausible claims, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; they exist because these are the cases that end up in arbitration or litigation.
+
+---
+
+### Edge Case 1: Temperature-Controlled Pharma Shipment — Reefer Failure with Disputed Loading Temperature
+
+**Situation:**
+A regional pharmaceutical distributor ships 14 pallets of insulin (Humalog and Novolog pens, wholesale value ~$2.1M) from a cold storage facility in Memphis to a hospital network distribution center in Atlanta. The shipment requires continuous 2–8°C (36–46°F) storage per USP <1079> guidelines. The reefer unit is a 2021 Carrier Transicold X4 7500 on a 53-foot trailer pulled by a contract carrier running under their own authority.
+
+Upon arrival 18 hours later, the receiving pharmacist's temperature probe reads 14°C (57°F) at the pallet surface. The TempTale 4 data logger packed inside the shipment shows the temperature climbed above 8°C approximately 6 hours into transit and continued rising. The carrier's in-cab reefer display download shows the setpoint was 4°C and the unit was in "continuous" mode, not "cycle-spool." The carrier produces a pre-trip reefer inspection report showing the unit pulled down to 2°C before loading and provides a lumper receipt from origin showing product was loaded at 3°C.
+
+The carrier's position: the product was loaded warm or the facility door was open too long during loading, and the reefer couldn't overcome the heat load. The shipper's position: the reefer compressor failed in transit and the carrier is liable. Both sides have documentation supporting their claim. The hospital network needs insulin within 48 hours or faces patient care disruptions.
+
+**Why It's Tricky:**
+Temperature excursion disputes are among the hardest to adjudicate because both the shipper and carrier can be partially right. A reefer unit in continuous mode should maintain setpoint on a properly pre-cooled load, but if the trailer was pre-cooled empty (no thermal mass) and then loaded with product at the upper end of range on a 95°F day in Memphis with the dock door cycling open, the unit may genuinely struggle. The critical question isn't the reefer setpoint — it's the return air temperature trend in the first 90 minutes after door closure.
+
+Most non-experts focus on the arrival temperature. Experts focus on the rate of temperature change and exactly when the deviation started. If the reefer data shows return air climbing steadily from minute one, the load was likely warm at origin. If return air held for 4+ hours then spiked, the compressor or refrigerant failed in transit.
+
+**Common Mistake:**
+Filing a blanket cargo claim against the carrier for $2.1M without first analyzing the reefer download data in detail. The carrier will deny the claim, point to their pre-trip and loading receipts, and the dispute enters a 6-month arbitration cycle. Meanwhile, the product sits in a quarantine hold and ultimately gets destroyed, the hospital network scrambles for supply, and the shipper-carrier relationship is damaged.
+
+The second common mistake: assuming the entire shipment is a total loss. Insulin pens that experienced a brief, moderate excursion may still be viable depending on manufacturer stability data and the specific excursion profile. A blanket destruction order without consulting the manufacturer's excursion guidance wastes recoverable product.
+
+**Expert Approach:**
+1. Immediately quarantine the shipment at the receiving facility — do not reject it outright and do not release it to inventory. Rejection creates a disposal liability problem. Quarantine preserves options.
+2. Download and preserve three data sets: (a) the TempTale or Ryan data logger from inside the shipment, (b) the reefer unit's microprocessor download (insist on the full download, not the driver's summary printout), and (c) the facility's dock door and ambient temperature logs from loading.
+3. Overlay the three data streams on a single timeline. Identify the exact minute the temperature began deviating and calculate the rate of change (°C per hour).
+4. If the deviation started within the first 90 minutes and the rate is gradual (0.5–1°C/hour), the load was likely under-cooled at origin or absorbed heat during loading. The shipper bears primary liability.
+5. If the deviation started 3+ hours into transit with a sharp rate change (2+°C/hour), the reefer experienced a mechanical failure. The carrier bears primary liability.
+6. Contact the insulin manufacturers' medical affairs departments with the exact excursion profile (time above 8°C, peak temperature reached). Request written guidance on product viability. Humalog pens that stayed below 15°C for under 14 days may still be usable per Lilly's excursion data.
+7. For product deemed viable, release from quarantine with full documentation. For product deemed non-viable, document the destruction with lot numbers, quantities, and witnessed disposal.
+8. File the claim against the liable party with the data overlay as the primary exhibit. If liability is shared, negotiate a split based on the data — typically 60/40 or 70/30.
+9. Separately and in parallel: source replacement insulin from the distributor's secondary allocation or from the manufacturer's emergency supply program. The hospital network cannot wait for claim resolution.
+
+**Key Indicators:**
+- Return air vs. supply air divergence in the first 2 hours is the single most diagnostic data point
+- A reefer that was pre-cooled empty to 2°C but shows supply air of 4°C within 30 minutes of door closure likely had an undersized unit or a failing compressor
+- Look for "defrost cycle" entries in the reefer log — a unit running excessive defrost cycles is masking a frost buildup problem that indicates a refrigerant leak
+- Check whether the reefer was in "continuous" or "start-stop" (cycle-spool) mode — pharma loads must be continuous; if it was set to cycle-spool, the carrier is immediately at fault regardless of loading temperature
+- A pre-trip that shows 2°C pulldown in under 20 minutes on a 53-foot trailer in summer is suspicious — that's an empty trailer with no thermal mass, meaning the carrier pulled the trailer to the shipper without adequate pre-cool time
+
+**Documentation Required:**
+- TempTale/Ryan recorder raw data file (CSV export, not just the PDF summary)
+- Reefer microprocessor full download (not the 3-line driver printout; the full event log with alarm history, defrost cycles, and door open events)
+- Origin facility dock door logs and ambient temperature at time of loading
+- Bill of lading with temperature requirement notation
+- Shipper's loading SOP and any deviation from it
+- Photographs of data logger placement within the load
+- Manufacturer's written excursion guidance for the specific product lots
+- Witnessed product destruction records with lot numbers if applicable
+
+**Resolution Timeline:**
+- Hours 0–4: Quarantine, data preservation, and initial data overlay analysis
+- Hours 4–12: Manufacturer consultation on product viability
+- Hours 12–48: Replacement sourcing and initial claim filing
+- Days 3–14: Detailed claim documentation assembly with data overlay exhibit
+- Days 14–45: Carrier/shipper response and negotiation
+- Days 45–120: Arbitration if negotiation fails (typical for claims over $500K)
+
+---
+
+### Edge Case 2: Consignee Refuses Delivery Citing Damage, but Damage Occurred at Consignee's Dock
+
+**Situation:**
+A furniture manufacturer ships 8 pallets of assembled high-end office chairs (Herman Miller Aeron, wholesale value ~$38,400) via LTL from their Grand Rapids facility to a commercial interior design firm in Chicago. The shipment arrives at the consignee's urban location — a converted warehouse with a narrow dock, no dock leveler, and a single dock door accessed via an alley.
+
+The driver backs in and the consignee's receiving crew begins unloading with a stand-up forklift. During unloading, the forklift operator catches a pallet on the trailer's rear door track, tipping it. Three cartons fall, and multiple chairs sustain visible frame damage. The consignee's receiving manager immediately refuses the entire shipment, marks the BOL "DAMAGED — REFUSED," and instructs the driver to take it all back.
+
+The driver, who was in the cab during unloading, did not witness the incident. He signs the BOL with the consignee's damage notation and departs with the full load. The shipper receives a refused-shipment notification and a damage claim from the consignee for the full $38,400.
+
+**Why It's Tricky:**
+Once "DAMAGED — REFUSED" is on the BOL signed by the driver, the shipper is in a difficult position. The consignee controls the narrative because they were the ones who noted damage. The carrier will deny the claim because the driver will state the freight was intact when he opened the doors. But the driver wasn't watching unloading, so he can't affirmatively say when damage occurred. The consignee has no incentive to admit their forklift operator caused the damage — they want replacement product, and it's easier to blame transit damage.
+
+The fundamental issue: damage occurring during unloading at the consignee's facility is the consignee's liability, not the carrier's or shipper's. But proving it requires evidence that is very hard to obtain after the fact.
+
+**Common Mistake:**
+Accepting the consignee's damage claim at face value and filing against the carrier. The carrier denies it, the shipper eats the cost, and the consignee gets free replacement product. The second common mistake: refusing to send replacement product while the dispute is investigated, damaging the commercial relationship with the consignee (who is the customer).
+
+**Expert Approach:**
+1. Before anything else, call the driver directly (or through the carrier's dispatch). Ask specifically: "Did you observe unloading? Were you in the cab or on the dock? Did you inspect the freight before signing the damage notation?" Get this statement within 24 hours while memory is fresh.
+2. Request the carrier pull any dashcam or rear-facing camera footage from the tractor. Many modern fleets have cameras that capture dock activity. Even if the angle is poor, it establishes the timeline.
+3. Ask the consignee for their facility's security camera footage of the dock area. Frame this as "helping us file the claim properly." If they refuse or claim no cameras, that's a data point.
+4. Examine the damage type. Chairs that fell off a forklift-tipped pallet will have impact damage on the frame — dents, bends, cracked bases — concentrated on one side and consistent with a fall from 4–5 feet. Transit damage from shifting in a trailer presents differently: scuffing, compression, carton crushing across the top of the pallet from stacking, and damage distributed across multiple faces of the carton.
+5. Check the origin loading photos. If the shipper photographs outbound loads (they should), compare the load configuration at origin to the described damage pattern. If the pallets were loaded floor-stacked with no double-stacking, top-of-pallet compression damage is impossible from transit.
+6. File a "damage under investigation" notice with the carrier within 9 months (Carmack Amendment window for concealed damage, though this is not concealed). Keep the claim open but do not assert a specific dollar amount yet.
+7. Send the consignee replacement product for the damaged units only (not the entire shipment — only the 3 cartons that were damaged, not all 8 pallets). Ship the replacements on the shipper's account, but document that the original undamaged product must be received as-is.
+8. If evidence supports consignee-caused damage, present findings to the consignee. The goal is not to litigate — it's to establish the facts and negotiate. Typically the consignee accepts liability for the damaged units, the shipper absorbs the freight cost of the return and reship, and the relationship survives.
+
+**Key Indicators:**
+- Driver was in the cab, not on the dock — critical detail that the carrier will try to gloss over
+- Damage concentrated on one pallet or one side of a pallet strongly suggests a handling incident, not transit movement
+- Consignee's dock conditions (no leveler, narrow alley, stand-up forklift for palletized furniture) are inherently risky — experienced shippers know these facilities generate more damage claims
+- If the consignee refused the entire shipment but only 3 cartons were visibly damaged, the refusal was strategic, not operational. Legitimate damage refusals are partial unless the entire shipment is compromised.
+- The driver signing the damage notation without adding "DAMAGE NOT OBSERVED IN TRANSIT" or "DRIVER NOT PRESENT DURING UNLOADING" is a documentation failure, but it is not an admission of carrier liability
+
+**Documentation Required:**
+- Signed BOL with damage notations (photograph both sides)
+- Driver's written statement on their location during unloading (within 24 hours)
+- Dashcam or rear-camera footage from the tractor if available
+- Consignee's dock/security camera footage (request in writing)
+- Origin loading photographs showing load configuration and product condition
+- Close-up photographs of actual damage on the product, taken at the consignee's facility
+- Diagram or description of the consignee's dock layout, including dock type, leveler presence, and equipment used for unloading
+- Replacement shipment BOL and delivery confirmation
+
+**Resolution Timeline:**
+- Hours 0–4: Driver statement collection and camera footage requests
+- Hours 4–24: Damage pattern analysis and origin photo comparison
+- Days 1–3: Replacement product shipped for confirmed damaged units
+- Days 3–10: Evidence assembly and liability determination
+- Days 10–30: Consignee negotiation on damaged unit liability
+- Days 30–60: Carrier claim closure (if carrier is cleared) or continued pursuit
+
+---
+
+### Edge Case 3: High-Value Shipment with No Scan Updates for 72+ Hours — "Lost" vs. "Scan Gap"
+
+**Situation:**
+A medical device manufacturer ships a single pallet of surgical navigation systems (Medtronic StealthStation components, declared value $287,000) from their distribution center in Jacksonville, FL to a hospital in Portland, OR. The shipment moves via a national LTL carrier with guaranteed 5-day service.
+
+The shipment scans at the origin terminal in Jacksonville on Monday at 14:22. It scans at the carrier's hub in Nashville on Tuesday at 03:17. Then — silence. No scan events for 72 hours. The shipper's logistics coordinator checks the carrier's tracking portal Wednesday, Thursday, and Friday morning. Nothing. The guaranteed delivery date is Friday by 17:00. The hospital has a surgery suite installation scheduled for the following Monday.
+
+The shipper calls the carrier's customer service line Friday morning. After 40 minutes on hold, the representative says the shipment is "in transit" and to "check back Monday." The shipper's coordinator escalates to their carrier sales rep, who promises to "get eyes on it." By Friday at 15:00, still no update.
+
+**Why It's Tricky:**
+A 72-hour scan gap on a national LTL carrier does not necessarily mean the shipment is lost. LTL carriers have known scan compliance problems at certain terminals, particularly mid-network hubs where freight is cross-docked between linehaul trailers. A pallet can physically move through 2–3 terminals without generating a scan if handheld devices aren't used during cross-dock operations or if the PRO label is damaged or facing inward on the pallet.
+
+But a 72-hour gap on a $287K shipment could also mean it was misrouted, left behind on a trailer that went to the wrong terminal, shorted to another shipment's delivery, or actually lost or stolen. The challenge is distinguishing between a scan gap (the freight is fine, the technology failed) and a genuine loss — while the clock is ticking on a surgery installation.
+
+**Common Mistake:**
+Waiting until the guaranteed delivery date passes to escalate. By Friday at 17:00, if the shipment is genuinely lost, you've wasted 72 hours of recovery time. The second common mistake: filing a lost shipment claim immediately, which triggers a formal process that takes 30–120 days to resolve. That doesn't help the hospital that needs equipment Monday. The third mistake: assuming the carrier's customer service representative actually has information — front-line CSRs at national LTL carriers typically see the same tracking portal the shipper does.
+
+**Expert Approach:**
+1. At the 48-hour mark (not the 72-hour mark), escalate through two parallel channels: (a) the carrier's sales representative, who has internal access to trailer manifests and terminal operations, and (b) the carrier's claims/OS&D (over, short, and damaged) department at the last known terminal (Nashville).
+2. Ask the sales rep for three specific things: (a) the trailer number the shipment was loaded on at Nashville, (b) the manifest for that trailer showing destination terminal, and (c) confirmation that the trailer has arrived at its destination terminal. This is not information CSRs have, but operations and sales teams can access it.
+3. If the trailer arrived at the destination terminal but the shipment didn't scan, it's almost certainly a scan gap. Ask the destination terminal to physically locate the freight on the dock or in the outbound staging area. Provide the PRO number, pallet dimensions, and weight — enough for someone to walk the dock.
+4. If the trailer hasn't arrived at the destination terminal, ask where the trailer currently is. Trailers are GPS-tracked. If the trailer is sitting at an intermediate terminal for 48+ hours, the freight may have been left on during unloading (a "buried" shipment that didn't get pulled).
+5. In parallel, start sourcing a backup unit from the manufacturer. For a $287K medical device, the manufacturer will have a loaner program or emergency stock. Contact Medtronic's field service team directly — they are motivated to keep the surgery installation on schedule because their technician is already booked.
+6. If the shipment is confirmed lost (not just scan-gapped) by Friday afternoon, immediately file a preliminary claim with the carrier. Do not wait. Simultaneously arrange emergency air freight for the replacement unit — the cost ($3,000–$8,000 for expedited air from the nearest depot with stock) is recoverable as part of the claim.
+7. If the shipment reappears (as scan-gap shipments often do), arrange Saturday or Sunday delivery. Many LTL carriers will do weekend delivery for an additional fee on service-failure shipments — negotiate this fee away since they missed the guarantee.
+
+**Key Indicators:**
+- A scan at an intermediate hub followed by silence usually means the freight is physically at the next terminal but didn't scan during cross-dock. Genuine theft or loss rarely happens mid-network at a carrier's own facility.
+- If the carrier's CSR says "in transit" 72 hours after the last scan, they're reading the same portal you are. Escalate immediately.
+- Check whether the PRO label was applied to shrink wrap or to the pallet itself. Shrink wrap labels get torn off during handling. This is the single most common cause of scan gaps.
+- A single high-value pallet is more vulnerable to being "lost" on a dock than a multi-pallet shipment. It's physically small enough to be blocked behind other freight or pushed into a corner.
+- If the carrier's Nashville terminal had a known service disruption (weather, labor action, system outage) in the 72-hour window, a scan gap is almost certain. Check the carrier's service alerts page.
+
+**Documentation Required:**
+- Complete tracking history with all scan events and timestamps
+- Original BOL with declared value, PRO number, piece count, weight, and dimensions
+- Screenshot of carrier tracking portal showing the gap (timestamped)
+- Written correspondence with carrier (sales rep, CSR, OS&D) with dates and names
+- Trailer number and manifest from the last known terminal
+- Carrier's guaranteed service commitment documentation
+- Replacement sourcing records and expedited shipping costs (if applicable)
+- Service failure claim documentation per the carrier's tariff (separate from cargo loss claim)
+
+**Resolution Timeline:**
+- Hour 48: Escalation to sales rep and OS&D department
+- Hours 48–56: Trailer tracking and physical dock search at destination terminal
+- Hours 56–72: Backup unit sourcing initiated
+- Hour 72 (if still missing): Preliminary lost cargo claim filed, emergency replacement shipped
+- Days 3–7: Carrier completes internal search; most "lost" LTL shipments are found within 5 business days
+- Days 7–30: Formal claim resolution if shipment is confirmed lost
+- Days 30–120: Full claim payment (national LTL carriers typically settle claims in 60–90 days for shipments with declared value)
+
+---
+
+### Edge Case 4: Cross-Border Shipment Held at Customs — Carrier Documentation Error vs. Shipper Error
+
+**Situation:**
+A Texas-based auto parts manufacturer ships a full truckload of aftermarket catalytic converters (480 units, commercial value $312,000) from their Laredo warehouse to an automotive distributor in Monterrey, Mexico. The shipment moves via a U.S. carrier to the Laredo border crossing, where it is transferred to a Mexican carrier for final delivery under a cross-dock arrangement.
+
+Mexican customs (Aduana) places a hold on the shipment at the Nuevo Laredo crossing. The customs broker reports two issues: (1) the commercial invoice lists the HS tariff code as 8421.39 (filtering machinery), but catalytic converters should be classified under 8421.39.01.01 (specific Mexican fraction for catalytic converters) or potentially 7115.90 (articles of precious metal, because catalytic converters contain platinum group metals), and (2) the pedimento (Mexican customs entry) lists 480 pieces but the physical count during inspection is 482 — two additional units were loaded that are not on any documentation.
+
+The carrier blames the shipper for the wrong HS code and the extra pieces. The shipper says the customs broker (hired by the carrier's Mexican partner) selected the HS code, and their pick ticket clearly shows 480 units. The Mexican carrier is charging $850/day in detention. The customs broker is quoting $4,500 for a "rectification" of the pedimento. The consignee needs the parts by Thursday for a production line changeover.
+
+**Why It's Tricky:**
+Cross-border shipments involving tariff classification disputes and quantity discrepancies touch three separate legal jurisdictions (U.S. export, Mexican import, and the bilateral trade agreement). The HS code issue is genuinely ambiguous — catalytic converters are classified differently depending on whether you're classifying the filtration function or the precious metal content, and the correct Mexican fraction depends on end use. The two extra pieces could be a loading error, a picking error, or remnant inventory from a previous load left in the trailer.
+
+Every day the shipment sits at the border, detention charges accrue, the consignee's production line inches closer to shutdown, and the risk of a formal Mexican customs investigation (which can result in seizure) increases. The parties involved — shipper, U.S. carrier, Mexican carrier, customs broker, consignee — all have conflicting incentives.
+
+**Common Mistake:**
+Letting the customs broker "handle it" without oversight. Border customs brokers facing a hold often choose the fastest resolution, not the cheapest or most legally correct one. They may reclassify under a higher-duty HS code to avoid scrutiny, costing the consignee thousands in excess duties that become very difficult to recover. They may also instruct the shipper to create a supplemental invoice for the 2 extra pieces at an arbitrary value, which creates a paper trail that doesn't match reality and can trigger a post-entry audit.
+
+The second mistake: panicking about the quantity discrepancy and assuming it's a smuggling allegation. Two extra catalytic converters on a 480-unit load is a 0.4% overage. Mexican customs sees this routinely and it's correctable — but only if handled with the right paperwork and the right broker.
+
+**Expert Approach:**
+1. Separate the two issues immediately. The HS code classification and the quantity discrepancy are different problems with different resolution paths. Do not let the broker bundle them into a single "rectification."
+2. For the HS code: engage a licensed Mexican customs classification specialist (not the same broker who filed the original pedimento). Catalytic converters for automotive aftermarket use are correctly classified under the Mexican tariff fraction 8421.39.01.01 with USMCA preferential treatment if the origin qualifies. The precious metals classification (7115.90) applies only to scrap or recovery operations. Get a binding ruling reference from SAT (Mexico's tax authority) if the broker disputes this.
+3. For the quantity discrepancy: determine the actual source of the two extra pieces. Pull the shipper's warehouse pick ticket, the loading tally sheet (if one exists), and check the trailer's seal number against the BOL. If the seal was intact at the border, the extra pieces were loaded at origin. Check whether the shipper's inventory system shows a corresponding shortage of 2 units. If it does, it's a simple pick/load error. If it doesn't, the units may have been left in the trailer from a previous load — check the carrier's prior trailer use log.
+4. File a "rectificación de pedimento" through the classification specialist for both the HS code correction and the quantity amendment. The amendment for the 2 extra units requires a supplemental commercial invoice from the shipper at the same per-unit price as the original 480.
+5. While the rectification is processing (typically 1–3 business days), negotiate the detention charges. The Mexican carrier's $850/day is negotiable because the hold is not their fault or the shipper's alone. The standard resolution is to split detention costs between the shipper (for the quantity error) and the customs broker (for the classification error), with the carrier waiving 1–2 days as a relationship concession.
+6. Document the entire incident for USMCA compliance records. An HS code correction on a $312K shipment of controlled automotive parts will flag in SAT's risk system, and the next shipment through Nuevo Laredo will get a more thorough inspection. Prepare for that.
+
+**Key Indicators:**
+- A customs hold that cites both classification and quantity issues is more serious than either alone — it suggests the shipment was flagged for manual inspection, not a random document review
+- Catalytic converter shipments to Mexico receive extra scrutiny because of environmental regulations (NOM standards) and precious metal content reporting requirements
+- If the customs broker immediately quotes a fee for "rectification" without explaining the legal basis, they're charging a facilitation fee, not a legitimate service cost. Get a second quote.
+- An intact seal with a quantity overage points to origin loading error. A broken or missing seal with a quantity overage is a much more serious situation suggesting possible tampering.
+- Check whether the shipper holds a C-TPAT certification — if so, the quantity error could jeopardize their trusted trader status, and the resolution needs to include a corrective action report
+
+**Documentation Required:**
+- Original commercial invoice, packing list, and BOL (all three must be reconciled)
+- Mexican pedimento (customs entry) showing the hold reason and original classification
+- Shipper's warehouse pick ticket and loading tally for the exact shipment
+- Trailer seal number verification (BOL seal number vs. seal number at inspection)
+- Carrier's prior trailer use log (to rule out remnant freight)
+- Classification specialist's written opinion on correct HS code with legal citations
+- Supplemental commercial invoice for the 2 additional units
+- Rectified pedimento with Aduana stamp
+- Detention invoices from the Mexican carrier with negotiated amounts
+- USMCA certificate of origin (if claiming preferential treatment)
+- Corrective action report if shipper is C-TPAT certified
+
+**Resolution Timeline:**
+- Hours 0–4: Issue separation, classification specialist engaged, quantity investigation started
+- Hours 4–24: Source of quantity discrepancy determined, supplemental invoice prepared
+- Days 1–3: Rectificación de pedimento filed and processed
+- Days 3–5: Shipment released from customs, delivered to consignee
+- Days 5–15: Detention charge negotiation and settlement
+- Days 15–45: Post-entry compliance documentation filed, C-TPAT corrective action if applicable
+
+---
+
+### Edge Case 5: Multiple Partial Deliveries Against Same BOL — Tracking Shortage vs. Overage
+
+**Situation:**
+A building materials distributor ships a full truckload of mixed SKUs — 12 pallets of ceramic floor tile (7,200 sq ft), 6 pallets of grout (180 bags), and 4 pallets of backer board (240 sheets) — from their Dallas distribution center to a commercial construction site in Houston. The BOL lists 22 pallets, 38,400 lbs, as a single shipment under one PRO number.
+
+The Houston job site cannot receive a full truckload at once — the staging area is too small and the GC (general contractor) will only accept what the tile crew can install that week. The shipper and consignee agreed to split delivery across three drops: 8 pallets Monday, 8 pallets Wednesday, 4 pallets Friday. The carrier is making partial deliveries from their Houston terminal, breaking the load and redelivering across the week.
+
+After the third delivery Friday, the GC's site superintendent counts what was received across all three deliveries and reports: 11 pallets of tile (short 1), 7 pallets of grout (over 1), and 4 pallets of backer board (correct). The consignee files a shortage claim for 1 pallet of tile (~$3,600) and an overage notification for 1 pallet of grout (~$420).
+
+The carrier says all 22 pallets were delivered across the three drops. The delivery receipts from Monday and Wednesday were signed by the site's day laborer (not the superintendent), and the Friday receipt was signed by the superintendent. None of the three delivery receipts detail pallet counts by SKU — they just say "8 pallets," "8 pallets," and "4 pallets" respectively.
+
+**Why It's Tricky:**
+Partial deliveries against a single BOL create a reconciliation nightmare. The original BOL describes the total load. Each partial delivery should have a delivery receipt referencing the original BOL with a detailed pallet-by-SKU breakdown, but in practice, drivers hand over whatever is on the truck and the receiver signs for a pallet count without verifying SKU-level detail.
+
+The likely scenario: during the break-bulk at the carrier's Houston terminal, a tile pallet was mixed up with a grout pallet. The carrier delivered 22 pallets total (correct), but the SKU mix within those 22 was wrong. This is not a shortage or an overage — it's a mis-delivery. But because the delivery receipts don't have SKU-level detail, no one can prove which delivery had the wrong mix.
+
+The job site may also be contributing to the confusion. Construction sites are chaotic. Product gets moved, other subcontractors' materials get mixed in, and the laborer who signed Monday's receipt may not have segregated the delivery from other tile already on site.
+
+**Common Mistake:**
+Filing a standard shortage claim for the missing tile pallet. The carrier will point to the signed delivery receipts showing 22 pallets delivered and deny the claim. The consignee ends up short tile for the install, orders a rush replacement, and eats the cost. Meanwhile, the extra grout pallet either gets absorbed into site inventory (costing the distributor) or sits unclaimed.
+
+The deeper mistake: not recognizing that this is a SKU-level accuracy problem, not a piece-count problem. Standard shortage claim procedures don't address mis-delivery within a correct total count.
+
+**Expert Approach:**
+1. Reconstruct the three deliveries at the SKU level. Start with what's verifiable: the Friday delivery was received by the superintendent. Ask them to confirm exactly what was on those 4 pallets by SKU. If they can confirm 4 pallets of backer board, that's clean.
+2. Work backward from Friday. If all backer board was on the Friday delivery, then Monday and Wednesday delivered a combined 12 pallets of tile and 6 pallets of grout — but we know the consignee received 11 tile and 7 grout. One tile pallet was swapped for a grout pallet.
+3. Check the carrier's Houston terminal break-bulk records. When the carrier broke the full truckload into three partial deliveries, they should have a terminal work order or fork driver's load sheet showing which pallets went on which delivery truck. If these records exist (and at major LTL/TL carriers, they often do), they'll show the misload.
+4. The resolution is a swap, not a claim. The consignee has 1 extra grout pallet that belongs to the distributor. The distributor owes 1 tile pallet to the consignee. Arrange a single delivery: bring 1 tile pallet, pick up 1 grout pallet. The carrier should absorb this cost as a service failure if the terminal's break-bulk records show the misload.
+5. For future partial-delivery shipments to this consignee (and any similar job site), require SKU-level detail on each delivery receipt. Create a standardized partial delivery form that references the master BOL and lists, per delivery: pallet count by SKU, total pieces by SKU, and a running total against the master BOL. Have the receiver verify and sign at the SKU level.
+6. If the carrier denies the misload and the consignee cannot wait for resolution, ship the replacement tile pallet immediately and pursue the carrier for the freight cost and the unrecovered grout pallet value.
+
+**Key Indicators:**
+- Delivery receipts signed by day laborers without SKU verification are essentially worthless for claims purposes — they prove delivery happened but not what was delivered
+- A 1-for-1 swap (1 pallet short on SKU A, 1 pallet over on SKU B, total count correct) is almost always a terminal misload, not a transit loss
+- Construction sites with multiple subcontractors and multiple material suppliers are high-risk for inventory confusion — materials from different vendors get commingled
+- If the grout and tile pallets are similar in size and wrapped in similar shrink wrap, the terminal dock worker likely couldn't distinguish them without checking labels
+- Check whether the pallets had color-coded labels or SKU stickers visible through the shrink wrap — if not, this is partly a packaging/labeling failure at origin
+
+**Documentation Required:**
+- Original BOL with complete SKU-level pallet breakdown (22 pallets by type)
+- All three delivery receipts with signatures and dates
+- Site superintendent's SKU-level inventory reconciliation after final delivery
+- Carrier's terminal break-bulk work order or fork driver load sheet (request in writing)
+- Photographs of the extra grout pallet (label, lot number, condition)
+- Replacement tile pallet shipment documentation
+- Return/swap documentation for the extra grout pallet
+
+**Resolution Timeline:**
+- Hours 0–8: SKU-level reconciliation at the job site
+- Hours 8–24: Carrier terminal records requested and reviewed
+- Days 1–3: Swap arranged — tile pallet delivered, grout pallet recovered
+- Days 3–7: Carrier cost allocation determined (service failure or shared)
+- Days 7–14: Partial delivery SOP updated for future shipments to this consignee
+
+---
+
+### Edge Case 6: Dual-Driver Team Swap with Missing Driver Signature on POD
+
+**Situation:**
+A contract carrier runs a team-driver operation to meet a time-critical delivery for an electronics retailer. The shipment is 18 pallets of consumer electronics (gaming consoles, wholesale ~$194,000) moving from a distribution center in Ontario, CA to a regional fulfillment center in Edison, NJ — approximately 2,700 miles with a 48-hour delivery commitment.
+
+Driver A departs Ontario and drives the first 11-hour shift. At the team swap point in Amarillo, TX (approximately mile 1,200), Driver B takes the wheel. Driver A had the original BOL packet with the paper POD (proof of delivery) form. During the swap, the BOL packet was left in the sleeper berth rather than passed to Driver B's clipboard.
+
+Driver B completes the haul to Edison and delivers the shipment. The receiving clerk at the fulfillment center signs the delivery receipt, but the Driver B signature line on the carrier's POD copy is blank — Driver B didn't have the BOL packet and instead used a generic delivery receipt from the cab's supply. The consignee's copy of the POD has the receiver's signature but no driver signature. The carrier's copy has Driver A's signature at origin and a blank at destination.
+
+Three weeks later, the retailer files a shortage claim for 2 pallets ($21,600) stating the delivery was short. The carrier has no signed POD from their driver at delivery confirming piece count.
+
+**Why It's Tricky:**
+A POD without the driver's signature at delivery is a significant evidentiary gap. The carrier cannot prove their driver confirmed the delivery was complete. The consignee's receiving clerk signed for "18 pallets" on their internal receipt, but the carrier doesn't have a copy of that document. The carrier's own POD shows 18 pallets loaded at origin (Driver A's signature) but has no delivery confirmation.
+
+Team-driver operations are notorious for documentation handoff failures. The swap happens at a truck stop at 2 AM, both drivers are focused on the HOS (hours of service) clock, and paperwork transfer is an afterthought. Carriers know this is a vulnerability but struggle to enforce procedures across hundreds of team operations.
+
+The 3-week gap between delivery and claim filing adds suspicion. If 2 pallets of gaming consoles were missing at delivery, the fulfillment center's receiving process should have caught it immediately — not three weeks later during an inventory cycle count.
+
+**Common Mistake:**
+The carrier, lacking a signed POD, immediately concedes the claim to avoid litigation. This sets a precedent that any shortage claim against a team-driver shipment without a perfect POD is automatically paid. The actual cost isn't just $21,600 — it's the signal to this retailer (and their claims department) that POD gaps equal easy money.
+
+Alternatively, the carrier denies the claim outright, the retailer escalates, and the carrier loses the account.
+
+**Expert Approach:**
+1. Obtain the consignee's internal receiving documentation. The fulfillment center will have their own receiving log, WMS (warehouse management system) receipt record, and the delivery receipt their clerk signed. Formally request these through the retailer's freight claims department. The consignee's WMS receipt record will show exactly how many pallets were scanned into inventory at the time of delivery.
+2. Check whether the consignee's facility has dock cameras. Most fulfillment centers of this size do. Request footage from the delivery date showing the unloading process. Counting pallets on a camera is straightforward.
+3. Pull Driver B's ELD (electronic logging device) data for the delivery stop. The ELD will show arrival time, departure time, and duration at the delivery location. A full 18-pallet unload takes 25–40 minutes. If the ELD shows a 15-minute stop, the delivery may indeed have been short (or the driver dropped the trailer, but that changes the scenario).
+4. Check the generic delivery receipt Driver B used. Even without the formal POD, if Driver B got any signature on any piece of paper, it has evidentiary value. Contact Driver B directly.
+5. Investigate the 3-week claim gap. Ask the retailer when exactly the shortage was discovered. If it was during an inventory cycle count, the shortage could have occurred anywhere in the fulfillment center's operations — theft, mis-pick, damage disposal without record — and not during delivery. A 3-week-old shortage claim without a same-day exception report at receiving is weak on its face.
+6. If the evidence shows full delivery (WMS receipt of 18, camera footage of 18 pallets, ELD showing full unload duration), deny the claim with documentation. If the evidence is inconclusive, negotiate a partial settlement — typically 50% of the claimed amount — with a corrective action plan for the team-driver POD process.
+
+**Key Indicators:**
+- A shortage claim filed weeks after delivery, absent a same-day exception notation on the delivery receipt, suggests the shortage occurred in the consignee's facility, not at delivery
+- Generic delivery receipts from the cab are still legally valid documents if signed by the receiver — they're just harder to track and retain
+- ELD stop duration is an underused tool for verifying delivery completeness. Full unloads take measurable time.
+- If the consignee's WMS shows 18 pallets received into inventory, the shortage claim is baseless regardless of the POD issue
+- Team swaps at truck stops between midnight and 5 AM have the highest documentation failure rate
+
+**Documentation Required:**
+- Carrier's POD (showing Driver A signature at origin, blank at destination)
+- Generic delivery receipt from Driver B (if recoverable)
+- Consignee's internal receiving log and WMS receipt record
+- Consignee's dock camera footage from the delivery date
+- Driver B's ELD data showing arrival, departure, and stop duration at delivery
+- Retailer's shortage claim filing with discovery date and method
+- Driver B's written statement regarding the delivery (pallet count, who received, any anomalies)
+
+**Resolution Timeline:**
+- Days 0–3: Consignee documentation request and Driver B statement
+- Days 3–7: ELD data pull and camera footage review
+- Days 7–14: Evidence analysis and liability determination
+- Days 14–30: Claim response to the retailer with supporting documentation
+- Days 30–60: Settlement negotiation if evidence is inconclusive
+
+---
+
+### Edge Case 7: Intermodal Container with Concealed Damage Discovered Days After Delivery
+
+**Situation:**
+A consumer goods importer receives a 40-foot intermodal container of packaged household cleaning products (cases of liquid detergent, surface cleaners, and aerosol sprays — approximately 1,800 cases, landed cost ~$67,000) at their warehouse in Memphis. The container moved ocean from Shenzhen to the Port of Long Beach, then intermodal rail from Long Beach to Memphis, then drayage from the Memphis rail ramp to the importer's warehouse.
+
+The container is grounded at the warehouse on Tuesday. The warehouse crew unloads it on Wednesday. Everything looks normal — the container seal was intact, no obvious external damage to the container, and the first 600 cases pulled from the doors look fine. But as the crew works deeper into the container (beyond the halfway point), they find approximately 200 cases of aerosol cans that are crushed and leaking. The cases were stacked in the rear of the container (loaded first in Shenzhen), and the damage pattern suggests the load shifted during transit, causing the top-stacked cases to collapse onto the aerosol pallets.
+
+The importer files a concealed damage claim. The problem: the container moved through four custody handoffs — the Chinese shipper's loading crew, the ocean carrier, the intermodal rail carrier, and the dray carrier. Each one had custody and each one will deny responsibility. The ocean carrier says the container was SOLAS-verified and properly loaded. The rail carrier says the container was accepted in good condition at Long Beach. The dray carrier says they only moved it 12 miles from the ramp and there was no incident.
+
+**Why It's Tricky:**
+Concealed damage in intermodal containers is the hardest claim in freight. The damage is hidden inside a sealed box that passes through multiple carriers across international boundaries. Each carrier has a plausible defense. The ocean carrier invokes COGSA (Carriage of Goods by Sea Act) limitations. The rail carrier invokes the Carmack Amendment domestically but argues the damage pre-dates their custody. The dray carrier points to the intact seal.
+
+The damage pattern — crushed cases deep in the container — is consistent with load shift, but load shift can occur during ocean transit (rolling seas), rail transit (humping and coupling at railyards), or even the final dray if the driver hit a severe pothole or made a hard stop. Without accelerometer data inside the container, pinpointing the moment of shift is nearly impossible.
+
+Aerosol cans add a complication: leaking aerosols are a hazmat concern (compressed gas, flammable propellant). The importer now has a cleanup cost on top of the product loss.
+
+**Common Mistake:**
+Filing a single claim against the ocean carrier for the full amount because they had the longest custody. COGSA limits the ocean carrier's liability to $500 per package (or per customary freight unit) unless a higher value was declared on the ocean bill of lading. If each pallet is a "package," the importer recovers $500 per pallet — far less than the actual loss. If no excess value was declared, the ocean carrier's exposure is capped regardless of actual damage.
+
+The second mistake: not inspecting the container immediately upon arrival. The importer grounded the container Tuesday and didn't unload until Wednesday. That 24-hour gap weakens the claim because any carrier can argue the damage occurred during the grounded period (temperature expansion, forklift impact to the grounded container, etc.).
+
+**Expert Approach:**
+1. Document everything before moving anything. Once the concealed damage is discovered mid-unload, stop unloading. Photograph the damage in situ — the crushed cases, the load configuration, the position of damage relative to the container doors and walls. Photograph the container interior from the door end showing the overall load state. Note the container number, seal number, and condition of the seal (intact, cut, or replaced).
+2. File concealed damage notices simultaneously with all three domestic parties: the dray carrier, the intermodal rail carrier, and the ocean carrier (or their agent). The notice must go out within the applicable time limits: 3 days for concealed damage under the Carmack Amendment (rail and dray), and per the ocean bill of lading terms for the ocean carrier (varies, but typically "within reasonable time of delivery").
+3. Inspect the container itself for evidence of the damaging event. Check for: (a) scuff marks on the container floor indicating load shift direction, (b) dents or impacts on the container walls that could have caused the shift, (c) condition of load securing (dunnage, airbags, strapping) and whether it was adequate per the shipper's load plan, and (d) moisture or condensation damage that suggests container rain, which is an ocean transit issue.
+4. Request the container's GPS and event data from the intermodal rail carrier. Modern chassis-mounted containers on rail generate movement and impact event data. If there was a significant impact event at a rail yard (coupling, humping, derailment), it will show in the data.
+5. Review the ocean carrier's vessel tracking for the voyage. If the vessel encountered severe weather (check NOAA marine weather data for the Pacific crossing dates), heavy roll could have initiated the load shift.
+6. Assess the load plan from Shenzhen. Were the aerosol cases (lightest, most fragile) stacked on the bottom at the rear of the container? If so, the Chinese shipper's loading crew made a fundamental error — heavy items go on the bottom, fragile items go on top and toward the door end. This is a shipper loading liability issue that no carrier is responsible for.
+7. For the hazmat cleanup: engage a licensed hazmat cleanup contractor for the leaking aerosols. Document the cleanup scope and cost. This cost is recoverable as consequential damages in the claim, but only against the party found liable for the load shift — not as a blanket charge to all carriers.
+8. File claims against the appropriate parties based on the evidence. In practice, most intermodal concealed damage claims with ambiguous causation settle through negotiation between the ocean carrier's P&I club and the cargo insurer. If the importer has marine cargo insurance (which they should, on a $67K shipment from China), file the insurance claim and let the insurer subrogate against the carriers.
+
+**Key Indicators:**
+- Damage only to cases deep in the container (rear, loaded first) strongly suggests load shift that occurred early in transit, not at the end — the cases at the door end (loaded last) served as a buffer
+- An intact container seal eliminates pilferage or unauthorized opening — the damage happened inside a sealed box during transit
+- Aerosol cases loaded at the bottom of a stack are a shipper loading error unless the load plan specifically accounted for their fragility and the damage was caused by an extraordinary event
+- Scuff marks on the container floor running longitudinally (front-to-back) suggest a braking or acceleration event; lateral scuff marks suggest roll (ocean) or curve forces (rail)
+- If the container was loaded with inflatable dunnage bags and the bags are deflated or burst, the bags were either undersized for the load or punctured by the aerosol cans during the shift — inspect the bags
+
+**Documentation Required:**
+- Photographs of damage in situ (before any cleanup or further unloading)
+- Container number, seal number, and seal condition photographs
+- Container inspection report (floor scuffs, wall impacts, dunnage condition)
+- Concealed damage notices to all carriers (with date/time stamps)
+- Ocean bill of lading with package and value declarations
+- Shipper's load plan from Shenzhen (container stuffing report)
+- Intermodal rail carrier's GPS and event data for the container
+- Vessel voyage data and NOAA weather records for the Pacific crossing
+- Hazmat cleanup contractor's scope and cost documentation
+- Marine cargo insurance claim filing (if applicable)
+- Packing list with case-level detail showing damaged vs. undamaged product
+
+**Resolution Timeline:**
+- Hour 0: Discovery — stop unloading, photograph, document
+- Hours 0–24: Concealed damage notices filed with all carriers
+- Days 1–3: Container inspection, carrier data requests, cleanup initiated
+- Days 3–14: Evidence assembly, load plan review, voyage/rail data analysis
+- Days 14–30: Marine cargo insurance claim filed (if applicable)
+- Days 30–90: Carrier responses and negotiation
+- Days 90–180: Settlement or arbitration (intermodal claims average 120 days to resolve)
+
+---
+
+### Edge Case 8: Broker Insolvency Mid-Shipment with Carrier Demanding Payment for Release
+
+**Situation:**
+A mid-size food manufacturer uses a freight broker to arrange a truckload of frozen prepared meals (retail value ~$128,000, freight charges ~$4,800) from their production facility in Omaha to a grocery distribution center in Minneapolis. The broker quoted the shipper $4,800 all-in and contracted the actual carrier at $3,900.
+
+The carrier picks up the load in Omaha on Monday. Tuesday morning, the shipper receives a call from the carrier's dispatcher: the broker has not paid their last three invoices totaling $14,200 across multiple loads, and the broker is not answering phones or emails. The carrier's dispatcher says they will not deliver the Minneapolis load until someone guarantees payment of $3,900 for this load plus the $14,200 in outstanding invoices from previous loads. The carrier currently has the loaded trailer at their Des Moines yard. The frozen meals have a 72-hour window before the cold chain becomes a concern, and the grocery DC has a receiving appointment Wednesday at 06:00 for a promotional launch.
+
+The shipper calls the broker. The number is disconnected. The broker's website is down. A quick search reveals the broker filed Chapter 7 bankruptcy two days ago.
+
+**Why It's Tricky:**
+Under federal law (49 USC §14103), a carrier can assert a lien on freight for unpaid charges. However, the carrier's lien is for charges on *this* shipment, not for the broker's unpaid invoices on previous shipments. The carrier is conflating two separate obligations: (a) the $3,900 owed for the current load, and (b) the $14,200 the insolvent broker owes from prior loads. The shipper owes the broker $4,800, not the carrier — the shipper has no contractual relationship with the carrier.
+
+But the carrier has physical possession of $128,000 in perishable freight. Practically, they have leverage regardless of the legal merits. The frozen meals don't care about legal arguments — they're thawing. And the grocery DC will cancel the receiving appointment and the promotional launch if the product doesn't arrive Wednesday.
+
+The shipper is also exposed to double-payment risk: they may have already paid the broker the $4,800 (or it's in their payment queue), and now the carrier wants $3,900 directly. If the shipper pays the carrier, they've paid $8,700 in freight charges for a $4,800 lane.
+
+**Common Mistake:**
+Paying the carrier's full demand ($3,900 + $14,200 = $18,100) to release the freight. This is extortion dressed as a lien claim, and it rewards bad behavior. The shipper has no obligation for the broker's prior debts, and paying them creates a precedent.
+
+The second mistake: refusing to pay anything and calling a lawyer. By the time the lawyer sends a demand letter, the frozen meals are compromised and the promotional launch is blown. Legal purity is cold comfort when you're explaining to the grocery chain why the endcap is empty.
+
+**Expert Approach:**
+1. Confirm the broker's insolvency. Check the FMCSA's broker licensing database for the broker's MC number — if their bond has been revoked or their authority is "inactive," insolvency is confirmed. Search federal bankruptcy court records (PACER) for the Chapter 7 filing.
+2. Contact the carrier's dispatcher or owner directly. Be professional, not adversarial. Acknowledge that the carrier is in a difficult position. State clearly: "We will guarantee payment of $3,900 for this load directly to you, but we are not responsible for the broker's prior debts. Those are claims against the broker's surety bond and bankruptcy estate."
+3. If the carrier accepts $3,900 for release, get it in writing before wiring the funds. Prepare a simple release letter: "Carrier agrees to deliver shipment [PRO/BOL number] to [consignee] in exchange for direct payment of $3,900 from [shipper]. This payment satisfies all carrier charges for this shipment. Carrier acknowledges that shipper is not liable for any amounts owed by [broker name/MC number] for other shipments."
+4. Wire the $3,900 or provide a company check at delivery. Do not use a credit card (the carrier will add a surcharge). Do not agree to pay within 30 days (the carrier wants certainty now, and delay risks them re-impounding the freight).
+5. If the carrier refuses to release for $3,900 and insists on the full $18,100, escalate to the FMCSA. Carriers who refuse to deliver freight to extract payment for unrelated loads are violating 49 USC §14103. File a complaint with FMCSA and inform the carrier you've done so. Most carriers will release at this point.
+6. As a last resort, if the freight is perishable and the carrier won't budge, consider paying the $3,900 plus a negotiated portion of the old debt (e.g., $3,000 of the $14,200) as a commercial compromise, with a written statement that the additional payment is "disputed and paid under protest to prevent spoilage of perishable goods." This preserves the shipper's right to recover the extra payment later.
+7. After the immediate crisis, file a claim against the broker's surety bond. Freight brokers are required to carry a $75,000 surety bond. The bond is specifically intended to cover situations like this. File the claim with the surety company listed on the broker's FMCSA registration. Note: if the broker has multiple unpaid carriers, the $75,000 bond will be split pro-rata among all claimants, so the recovery may be partial.
+8. Also file a claim in the broker's Chapter 7 bankruptcy proceeding as an unsecured creditor for any amounts paid above the original $4,800 contract rate. Recovery in Chapter 7 is typically pennies on the dollar, but it preserves the legal right.
+
+**Key Indicators:**
+- A broker whose phone is disconnected and website is down is either insolvent or has absconded — either way, they are no longer a viable intermediary
+- Carriers who demand payment for unrelated loads as a condition of delivery are overreaching, but they know that perishable freight gives them leverage
+- Check if the shipper's broker contract has a "double-brokering" prohibition — some insolvent brokers were actually re-brokering loads to other brokers, adding a layer of complexity to the payment chain
+- The broker's surety bond amount ($75,000) is almost never enough to cover all claims when a broker fails — prioritize getting your claim filed early
+- If the carrier is a small fleet (5 or fewer trucks), they may be genuinely unable to absorb the loss from the broker and may be more willing to negotiate if they receive some payment quickly
+
+**Documentation Required:**
+- Original broker-shipper contract with rate confirmation
+- Carrier's rate confirmation with the broker (if obtainable)
+- FMCSA broker registration showing authority status and surety bond information
+- Bankruptcy filing documentation (PACER search results)
+- Written release agreement between shipper and carrier
+- Wire transfer or payment confirmation for the $3,900 direct payment
+- "Paid under protest" letter if any amount above $3,900 is paid
+- Surety bond claim filing with the broker's surety company
+- Bankruptcy court claim filing as unsecured creditor
+- Temperature monitoring data from the shipment (to document cold chain integrity during the delay)
+- Consignee delivery confirmation and any penalty or chargeback documentation from the grocery chain
+
+**Resolution Timeline:**
+- Hours 0–4: Broker insolvency confirmed, carrier negotiation initiated
+- Hours 4–12: Payment agreement reached, funds wired, freight released
+- Hours 12–24: Delivery completed to grocery DC
+- Days 1–7: Surety bond claim filed
+- Days 7–30: Bankruptcy court claim filed
+- Days 30–180: Surety bond claim adjudication (typical timeline is 90–120 days)
+- Days 180+: Bankruptcy distribution (can take 1–2 years)
+
+---
+
+### Edge Case 9: Seasonal Peak Surcharge Dispute During Declared Weather Emergency
+
+**Situation:**
+A home improvement retailer has a contract with a national LTL carrier that includes a published fuel surcharge table and a "peak season surcharge" clause. The contract states that peak surcharges of up to 18% may be applied during "periods of extraordinary demand as determined by the carrier," with 14 days' written notice.
+
+In mid-January, a severe ice storm hits the central U.S. — Kansas City, St. Louis, Memphis, and Nashville are all affected. The carrier declares a "weather emergency" on January 15 and simultaneously activates a 22% "emergency surcharge" on all shipments moving through or originating from the affected regions. The carrier's notice, sent via email blast on January 15, states the surcharge is effective January 16.
+
+The retailer has 340 LTL shipments in transit and another 280 scheduled to ship in the next 7 days through those regions. At an average of $1,200 per shipment, the 22% surcharge adds approximately $163,000 in unbudgeted freight cost across those 620 shipments. The retailer's logistics director objects on three grounds: (1) the contract caps peak surcharges at 18%, (2) the 14-day notice requirement was not met, and (3) this is a weather event, not "extraordinary demand," and should be covered by the existing fuel surcharge mechanism.
+
+The carrier's position: the weather emergency surcharge is separate from the peak season surcharge and is authorized under the carrier's rules tariff, which the contract incorporates by reference. The carrier cites item 560 in their tariff, which states "emergency surcharges may be applied without prior notice during force majeure events."
+
+**Why It's Tricky:**
+The dispute turns on contract interpretation, specifically whether the weather emergency surcharge is a type of peak surcharge (capped at 18% with 14-day notice) or a separate tariff item (uncapped, no notice required). Both readings are defensible. The contract's peak surcharge clause doesn't specifically exclude weather events. But the tariff's force majeure provision is broadly written and has been part of the carrier's published tariff for years.
+
+Practically, the carrier has leverage because the freight is either in transit (already moving at the carrier's mercy) or needs to ship to meet store replenishment schedules. The retailer can't reroute 620 shipments to another carrier overnight. And the ice storm is real — the carrier is genuinely incurring higher costs (driver detention, re-routing, de-icing, reduced productivity at affected terminals).
+
+**Common Mistake:**
+Paying the 22% surcharge under protest and then filing a batch claim after the fact. Carriers rarely refund surcharges retroactively, and the retailer's purchasing department will have already booked the expense. The dispute becomes an accounting exercise that drags on for months with no resolution.
+
+The opposite mistake: refusing to ship until the surcharge is resolved. The stores need product, especially during an ice storm when consumers are buying emergency supplies. A shipping freeze costs more in lost sales than the surcharge.
+
+**Expert Approach:**
+1. Separate the in-transit shipments from the pending shipments. The 340 shipments already moving are subject to the carrier's tariff as of the ship date — if they shipped before January 16, the surcharge should not apply to them. Challenge any surcharge applied to shipments that were tendered before the effective date.
+2. For the 280 pending shipments, negotiate immediately. Contact the carrier's pricing or contract manager (not customer service). Propose a compromise: the retailer will accept an 18% surcharge (the contract cap) for the weather period, applied to shipments originating from or delivering to the affected zip codes only, not all shipments "moving through" the region. A shipment from Dallas to Atlanta that transits Memphis should not bear a surcharge meant to cover Memphis-area operational costs.
+3. Challenge the tariff incorporation. Most shipper-carrier contracts include a clause like "the carrier's tariff is incorporated by reference except where this contract specifically provides otherwise." The contract specifically provides a peak surcharge cap of 18% with 14-day notice. Argue that this specific provision overrides the general tariff force majeure clause. Have the retailer's transportation attorney send a letter to this effect within 48 hours.
+4. Request documentation of the carrier's actual incremental costs during the weather event. Carriers often apply surcharges that far exceed their actual cost increase. A 22% surcharge on $744,000 in freight ($163,680) should correlate to demonstrable cost increases — driver bonuses, equipment repositioning, de-icing, etc. Ask for the cost justification. Carriers rarely provide it, which weakens their position.
+5. If the carrier refuses to negotiate, identify which of the 280 pending shipments can move via alternate carriers. Even shifting 30–40% of the volume signals to the contract carrier that the surcharge has competitive consequences. A national retailer with 280 shipments can find partial capacity even during a weather event.
+6. Document the surcharge dispute in writing for the annual contract renewal. A carrier that imposed a 22% surcharge with one day's notice during a weather event has demonstrated that their tariff's force majeure clause is a material contract risk. In the next RFP, either negotiate a hard cap on emergency surcharges or require the carrier to remove the force majeure provision from the incorporated tariff.
+
+**Key Indicators:**
+- A surcharge that exceeds the contract's peak season cap is a contract violation unless the carrier can clearly show it's authorized under a separate tariff provision — and even then, the contract's specific terms should override the general tariff
+- One day's notice for a 22% surcharge is commercially unreasonable regardless of the contractual language. No shipper can adjust their logistics budget overnight.
+- Carriers that apply regional surcharges to all traffic "passing through" a region (rather than originating or terminating there) are overreaching. A shipment that transits Memphis on a linehaul trailer incurs no additional cost unless it's being cross-docked at the Memphis terminal.
+- Check whether the carrier applied the same surcharge to all customers or only to contracted customers. If spot-market shipments during the same period were priced at normal + 10%, the contracted customers are being overcharged.
+- Weather events that last 3–5 days should not generate surcharges that persist for 14–21 days. Challenge the surcharge end date, not just the rate.
+
+**Documentation Required:**
+- Shipper-carrier contract with peak surcharge clause and tariff incorporation language
+- Carrier's published tariff, specifically the force majeure and emergency surcharge provisions
+- Carrier's email notification of the weather emergency surcharge (with date, time, and effective date)
+- List of all shipments affected (in-transit and pending) with ship dates and origin/destination
+- Carrier's actual surcharge amounts applied to each shipment
+- Retailer's written objection letter from transportation attorney
+- Documentation of the actual weather event (NWS advisories, road closure reports)
+- Alternate carrier quotes for diverted shipments
+- Carrier's cost justification documentation (if provided)
+- Settlement agreement (if reached)
+
+**Resolution Timeline:**
+- Hours 0–24: Separate in-transit from pending shipments, initial negotiation contact
+- Days 1–3: Attorney's letter sent, alternate carrier quotes obtained, compromise proposed
+- Days 3–7: Negotiation period (carrier will typically respond within a week under pressure)
+- Days 7–14: Resolution of the surcharge rate (typically settles at 15–18% for the affected period)
+- Days 14–30: Credit memo processing for overcharged in-transit shipments
+- Months 3–6: Incorporate lessons into annual contract renewal
+
+---
+
+### Edge Case 10: Systematic Pilferage Pattern Across Multiple LTL Terminal Shipments
+
+**Situation:**
+A consumer electronics brand ships approximately 120 LTL shipments per month through a regional carrier's network to independent retailers across the Southeast. Over a 90-day period, the brand's claims department notices a pattern: 14 shortage claims totaling $47,200, all involving small, high-value items (wireless earbuds, smartwatches, Bluetooth speakers) in the $150–$800 retail range. The shortages range from 2–8 units per shipment.
+
+The pattern: all 14 claims involve shipments that passed through the carrier's Atlanta terminal. The shipments originate from various locations (the brand's warehouses in Charlotte, Dallas, and Memphis) and deliver to various retailers. The only common element is the Atlanta cross-dock. The shortages are discovered at delivery — the retailer opens the carton and finds units missing inside otherwise intact-looking cases. The case count on the BOL matches the case count at delivery, but the unit count inside specific cases is short.
+
+The carrier has denied 9 of the 14 claims, citing "no visible damage at delivery" and "correct case count per BOL." The brand suspects organized pilferage at the Atlanta terminal — someone is opening cases, removing small high-value items, and resealing or re-taping the cases.
+
+**Why It's Tricky:**
+Proving systematic pilferage at a carrier's terminal is extremely difficult. The standard claim process evaluates each shipment independently. Each individual claim looks like a minor packaging or picking error — "maybe the warehouse packed 22 earbuds instead of 24 in that case." But 14 claims in 90 days with the same profile (same terminal, same product category, same method) is not coincidence. It's organized theft.
+
+The carrier's claims department isn't equipped to recognize patterns. They adjudicate each claim against the documentation: case count matched at delivery, no visible damage, claim denied. They don't aggregate claims across shipments to look for terminal-specific patterns. And the carrier's terminal management in Atlanta has no incentive to investigate — acknowledging a pilferage problem at their terminal implicates their own employees.
+
+The brand's individual claim amounts ($1,500–$5,500 each) are below the threshold that typically triggers a serious investigation. No single claim justifies hiring an investigator or involving law enforcement.
+
+**Common Mistake:**
+Continuing to file individual claims and accepting the denials, or switching carriers entirely without pursuing the pattern. Switching carriers doesn't recover the $47,200 already lost and doesn't address the root cause — the pilfered goods are still flowing into a gray market somewhere.
+
+The other mistake: confronting the carrier's sales representative with the pilferage accusation without data. "We think your people are stealing" destroys the commercial relationship. "We've identified a statistically significant claim pattern that we need to investigate jointly" gets attention.
+
+**Expert Approach:**
+1. Build the pattern analysis first. Create a spreadsheet mapping all 14 claims by: origin, destination, Atlanta terminal arrival/departure dates, case count, shortage amount, shortage product type, and claim outcome. Add the 106 shipments that passed through Atlanta without a shortage claim. Calculate the shortage rate for Atlanta-routed shipments (14/120 = 11.7%) vs. the brand's overall shortage rate across all carriers and terminals (industry average for consumer electronics is 1–2%).
+2. Identify the shift pattern. Atlanta terminal operates multiple shifts. Cross-reference the 14 shortage shipments' arrival and departure scan times against the terminal's shift schedule. If all 14 shipments were on the dock during the same shift window, the pilferage is likely associated with specific workers on that shift.
+3. Present the pattern analysis to the carrier's Director of Claims or VP of Operations — not the sales rep, not the local terminal manager. This is a corporate-level conversation. Frame it as: "We have data suggesting a pattern that requires a joint investigation. Here's our analysis. We want to work with your security team."
+4. Request that the carrier's loss prevention or security department conduct a covert investigation at the Atlanta terminal. Major LTL carriers have internal security teams specifically for this. Provide them with the shift-pattern analysis and the product profiles that are being targeted.
+5. In parallel, introduce covert tracking. Ship 5–10 "bait" packages through the Atlanta terminal containing AirTag-type trackers concealed inside the product boxes alongside real product. If units are pilfered, the trackers will provide location data on where the stolen goods end up, which helps law enforcement build a case.
+6. Implement tamper-evident packaging for all high-value shipments moving through the Atlanta terminal. Use serialized security tape that changes color if peeled and replaced. This doesn't prevent pilferage but makes it detectable at delivery — if the security tape is broken, the shortage is documented immediately.
+7. File a comprehensive claim covering all 14 shortages as a single pattern claim, totaling $47,200, supported by the statistical analysis. Individual claims of $2,000 get denied by a claims adjuster following a script. A $47,200 pattern claim with statistical evidence gets escalated to claims management.
+8. If the carrier refuses to investigate or settle, consider filing a report with the local FBI field office. Organized cargo theft from carrier terminals is a federal crime (18 USC §659, theft from interstate or foreign shipments). The FBI's cargo theft unit handles exactly this type of pattern.
+
+**Key Indicators:**
+- Shortages of small, high-value consumer electronics from inside otherwise intact cases is the hallmark of organized terminal pilferage, not random loss
+- A single terminal appearing in all claims is the strongest pattern indicator — it eliminates origin and destination as variables
+- Shortage claims that the carrier denies because "case count matched" are actually consistent with pilferage — the thief reseals the case to avoid detection at the piece-count level
+- If the shortages are concentrated on specific days of the week, there may be a shift or crew pattern
+- Check if the carrier's Atlanta terminal has had employee theft incidents reported in the past — local court records or news reports may reveal prior issues
+
+**Documentation Required:**
+- Detailed claim log for all 14 shortage claims with full shipment data
+- Statistical pattern analysis (spreadsheet) showing Atlanta terminal as common factor
+- Shift-pattern analysis correlating shortage shipments to terminal operating hours
+- Rate comparison: shortage rate for Atlanta-routed vs. non-Atlanta-routed shipments
+- Photographs of opened cases showing missing units and condition of tape/seal
+- Bait package tracking data (if deployed)
+- Tamper-evident packaging results (if implemented)
+- Carrier correspondence — all claim filings, denials, and escalation communications
+- Formal pattern claim filing with the carrier ($47,200 aggregate)
+- Law enforcement report (if filed)
+
+**Resolution Timeline:**
+- Days 0–7: Pattern analysis completed and presented to carrier leadership
+- Days 7–14: Carrier security team briefed and investigation initiated
+- Days 14–30: Bait packages shipped, tamper-evident packaging deployed
+- Days 30–60: Investigation results (carrier internal) and pattern claim response
+- Days 60–90: Settlement negotiation on the aggregate claim
+- Days 90–180: If pilferage is confirmed, potential criminal prosecution and full recovery
+
+---
+
+### Edge Case 11: Hazmat Shipment Damaged in Transit with Environmental Contamination Risk
+
+**Situation:**
+A specialty chemical manufacturer ships a truckload of sodium hypochlorite solution (industrial bleach, 12.5% concentration) — 20 IBC totes (275 gallons each, 5,500 gallons total), classified as UN1791, Corrosive Liquid, Class 8, PG II — from their plant in Baton Rouge, LA to a water treatment facility in Birmingham, AL.
+
+At approximately mile 180 on I-59 near Hattiesburg, MS, the driver encounters a sudden lane closure for road construction. He brakes hard. Three IBC totes in the rear of the trailer shift forward, two of them toppling. One tote's valve assembly shears off and sodium hypochlorite begins leaking onto the trailer floor and out the rear door gaps. The driver smells chlorine, pulls over, and calls his dispatcher. He estimates 50–75 gallons have leaked onto the highway shoulder before he could stop.
+
+The situation now involves: (a) a hazmat spill on a state highway requiring notification and cleanup, (b) a damaged shipment where 3 of 20 totes may be compromised, (c) a driver who has been exposed to chlorine vapor and may need medical attention, (d) a consignee water treatment plant that needs the chemical for drinking water treatment, and (e) potential EPA, Mississippi DEQ, and DOT enforcement actions.
+
+**Why It's Tricky:**
+A hazmat in-transit incident is not just a freight claim — it's a multi-agency regulatory event. The spill triggers mandatory reporting obligations under 49 CFR §171.15 (immediate phone report to the National Response Center if the spill meets reportable quantity thresholds) and 49 CFR §171.16 (written hazmat incident report within 30 days). Sodium hypochlorite at 50+ gallons on a highway triggers the reportable quantity threshold.
+
+The environmental cleanup cost will likely dwarf the product value. The 5,500 gallons of chemical is worth about $8,250. The highway shoulder cleanup, soil remediation, and storm drain protection for a 50-gallon bleach spill on a Mississippi highway will cost $15,000–$40,000 depending on proximity to waterways.
+
+Liability is layered: the shipper is the "offeror" under hazmat regulations and is responsible for proper packaging and loading. The carrier is responsible for safe transportation and proper load securement. If the IBC totes shifted because they weren't properly secured (blocked and braced per the carrier's securement obligations under 49 CFR §393), the carrier bears liability. If the totes shifted because the valve assemblies were improperly rated for transport vibration, the shipper/manufacturer bears liability.
+
+**Common Mistake:**
+Treating this as a freight claim first and a hazmat incident second. It's the opposite. The first priority is life safety and environmental containment, followed by regulatory compliance, and then — distantly — commercial recovery.
+
+The second mistake: the driver attempting to clean up the spill himself. Sodium hypochlorite at 12.5% concentration is a corrosive that generates toxic chlorine gas, especially if it contacts organic matter or acid (which could be in the road debris). The driver should evacuate the area, not grab a mop.
+
+**Expert Approach:**
+1. Immediate response (minute 0): the driver must move upwind and uphill from the spill, call 911, and report a hazardous materials spill. The driver must not attempt to stop the leak, upright the totes, or clean the spill unless they are hazmat-trained and have appropriate PPE (which over-the-road drivers typically do not carry for Class 8 corrosives).
+2. Regulatory notifications (within 15 minutes): the carrier's dispatch must call the National Response Center (NRC) at 800-424-8802. This is a mandatory immediate notification for any hazmat spill meeting the reportable quantity. For sodium hypochlorite, the reportable quantity is 100 lbs — 50 gallons at approximately 10 lbs/gallon is 500 lbs, well over the threshold.
+3. The carrier must also notify Mississippi's Department of Environmental Quality (MDEQ) emergency spill line. State notification is required in addition to federal NRC notification.
+4. Driver medical: if the driver is experiencing respiratory distress, burning eyes, or coughing from chlorine exposure, 911 will dispatch EMS. The carrier must ensure the driver receives medical attention before worrying about the freight.
+5. Once emergency services arrive and control the scene, the carrier must arrange for a licensed hazmat cleanup contractor. The Mississippi State Highway Patrol will not allow the carrier to move the trailer until the spill is contained and the remaining totes are assessed for stability. This can take 4–12 hours.
+6. Assessment of the remaining product: the 17 undamaged totes and the 2 toppled (but possibly intact) totes need to be inspected by a hazmat technician before they can continue transport. If the toppled totes have compromised valve assemblies or cracked walls, they must be overpacked (placed inside larger containment) for transport to a transload facility — they cannot continue to the consignee in damaged condition.
+7. Load securement investigation: before moving any freight, document the securement setup. Were the IBC totes blocked and braced? Were load bars or cargo straps used? IBC totes on flatbed or dry van trailers must be secured per 49 CFR §393.116 (securement of intermodal containers) or the general cargo securement provisions. Photograph the securement setup as-is. This is the key liability evidence.
+8. Contact the consignee water treatment plant immediately. They need to source replacement chemical from a backup supplier to maintain drinking water treatment operations. A water treatment plant running low on disinfection chemical is a public health emergency. Provide the plant with the timeline for delivery of the undamaged product (likely 24–48 hours after scene clearance) and help them source the 825-gallon shortfall (3 damaged totes worth) from a regional supplier.
+9. File the written hazmat incident report (DOT Form F 5800.1) within 30 days. This report goes to PHMSA (Pipeline and Hazardous Materials Safety Administration) and becomes a public record. Accuracy is critical — this document can be used in enforcement proceedings.
+10. Pursue the cargo and environmental cleanup costs based on liability determination. If the carrier failed to properly secure the load, they bear liability for the product loss, cleanup costs, driver medical costs, and any regulatory fines. If the shipper's IBC totes had a manufacturing defect (e.g., the valve assembly sheared at normal braking force, indicating a design flaw), the tote manufacturer bears product liability.
+
+**Key Indicators:**
+- A valve assembly that shears off during normal hard braking (not a collision) suggests either an improperly rated valve or a tote that was overfilled — check the fill level against the tote's maximum capacity and the 80% fill rule for IBCs containing corrosives
+- If the load was unsecured (no straps, no load bars, no blocking), the carrier's liability is clear regardless of the braking situation
+- Three totes shifting suggests a systemic securement failure, not an isolated strap break. One tote falling could be a strap failure; three totes means the entire load was inadequately secured.
+- Check the driver's CDL for hazmat endorsement. Driving a placarded load without the endorsement is a separate violation that compounds the carrier's liability.
+- If the sodium hypochlorite reached a storm drain or waterway, the cleanup cost escalates dramatically and may trigger Superfund reporting requirements
+
+**Documentation Required:**
+- NRC notification confirmation number and timestamp
+- MDEQ spill notification confirmation
+- 911 call record and emergency response documentation
+- Photographs of the spill scene, damaged totes, and load securement setup (taken before cleanup)
+- Driver's medical treatment records (if applicable)
+- Hazmat cleanup contractor's containment and remediation report with cost
+- 49 CFR §393 load securement inspection report
+- DOT Form F 5800.1 hazmat incident report (filed within 30 days)
+- Driver's CDL and hazmat endorsement verification
+- IBC tote manufacturer specifications and valve assembly ratings
+- BOL, shipping papers, and emergency response information (ERG guide page)
+- Consignee notification and replacement sourcing documentation
+- Environmental monitoring results (soil, water testing at the spill site)
+
+**Resolution Timeline:**
+- Minutes 0–15: Emergency notifications (911, NRC, MDEQ)
+- Hours 0–4: Scene control, spill containment, driver medical attention
+- Hours 4–12: Hazmat cleanup, remaining totes inspected, trailer released
+- Hours 12–48: Undamaged totes delivered to consignee, replacement chemical sourced for shortfall
+- Days 1–7: Load securement investigation, liability assessment, carrier/shipper negotiation
+- Days 7–30: DOT Form F 5800.1 filed, environmental monitoring results received
+- Days 30–90: Cleanup cost and cargo claim settlement
+- Days 90–365: Potential PHMSA enforcement action (civil penalties for securement violations can reach $500,000+ per violation)
+
+---
+
+### Edge Case 12: Customer Rejects Shipment for Late Delivery on JIT Production Line, but Carrier Met the BOL Delivery Window
+
+**Situation:**
+An automotive Tier 1 supplier ships a truckload of stamped metal brackets (43,000 pieces, value $186,000) from their Youngstown, OH plant to a GM assembly plant in Spring Hill, TN. The parts feed directly into the truck assembly line under a JIT (just-in-time) delivery program. The JIT window, per GM's scheduling system, is Tuesday 04:00–06:00 — parts must arrive within that 2-hour window or the line shuts down.
+
+The BOL, however, lists the delivery date as "Tuesday" with no specific time window. The carrier's rate confirmation lists delivery as "by end of day Tuesday." The carrier delivers at 11:42 on Tuesday. The GM receiving dock rejects the shipment because the JIT window closed at 06:00. GM's production line halted at 06:47 when the bracket buffer stock ran out, and the line was down for 4.5 hours until the carrier's truck was finally unloaded at 11:42 under emergency protocols.
+
+GM issues a line-down chargeback to the Tier 1 supplier for $215,000 (the calculated cost of 4.5 hours of assembly line downtime at ~$47,800/hour). The Tier 1 supplier demands the carrier pay the chargeback plus the freight charges. The carrier says they delivered on Tuesday — within the BOL's delivery date — and they have no knowledge of, or obligation to meet, a JIT delivery window that was never communicated to them.
+
+**Why It's Tricky:**
+The carrier has a strong defense. The BOL says "Tuesday" and the carrier delivered Tuesday. The rate confirmation says "by end of day Tuesday" and the carrier delivered by end of day. The JIT window of 04:00–06:00 appears nowhere in the carrier's documentation. The Tier 1 supplier's logistics team communicated the JIT window to their own scheduling system and to GM, but never put it on the BOL or the carrier's rate confirmation.
+
+The $215,000 chargeback is a consequential damage claim — the carrier is responsible for the freight charges and possibly the value of the goods if damaged, but consequential damages (like production line downtime) require that the carrier had "actual or constructive notice" of the specific consequences of late delivery. Under the Carmack Amendment, consequential damages are recoverable only if the carrier knew or should have known about the specific time-sensitivity.
+
+A carrier delivering at 11:42 for a "Tuesday" delivery did nothing wrong by the terms they agreed to. The Tier 1 supplier's failure to communicate the JIT window to the carrier is the root cause, but GM doesn't care about the supplier's internal logistics — they want their $215,000.
+
+**Common Mistake:**
+The Tier 1 supplier's traffic manager tries to recover the full $215,000 from the carrier by arguing "you knew this was an automotive JIT delivery." But knowing a consignee is an auto assembly plant is not the same as knowing the specific delivery window. Many deliveries to assembly plants go to a warehouse dock, not the JIT receiving dock. Without specific written notice of the 04:00–06:00 window and the consequences of missing it, the carrier's liability for consequential damages is virtually zero.
+
+The second mistake: the supplier accepting the full $215,000 chargeback from GM without negotiation. GM's chargeback calculations are often inflated — the $47,800/hour figure includes overhead allocation, labor costs for idled workers, and opportunity cost. The actual incremental cost of 4.5 hours of downtime may be significantly lower. Chargebacks are negotiable.
+
+**Expert Approach:**
+1. Accept responsibility for the communication failure — the Tier 1 supplier's logistics team did not convey the JIT window to the carrier. This is not the carrier's fault. Attempting to blame the carrier poisons a relationship for a claim they'll ultimately lose.
+2. Negotiate the GM chargeback. Request GM's detailed calculation supporting the $47,800/hour figure. Standard OEM downtime calculations include direct costs (line labor, utility, scrap from partial builds) and indirect costs (overhead allocation, management time, schedule recovery). Push back on the indirect costs. A 4.5-hour stoppage with a full recovery by end of shift typically warrants a 40–60% reduction in the chargeback amount. Aim for $90,000–$130,000.
+3. File an internal corrective action. The failure was in the supplier's logistics process: the JIT window was known internally but not transmitted to the carrier. Implement a standard procedure requiring all JIT delivery windows to appear on the BOL in the "special instructions" field and on the carrier's rate confirmation. The rate confirmation should state: "DELIVERY WINDOW: 04:00–06:00 TUESDAY. LATE DELIVERY WILL RESULT IN PRODUCTION LINE DOWNTIME AT APPROXIMATELY $X/HOUR."
+4. For the carrier relationship: share the situation transparently. Explain the JIT delivery program and acknowledge the communication gap. Offer to add the delivery window to future rate confirmations along with an appropriate accessorial charge for time-definite delivery. Carriers will quote a premium for guaranteed delivery windows — typically $200–$500 for a 2-hour window on a 500-mile haul — but that premium is trivial compared to a $215,000 chargeback.
+5. Implement a buffer strategy with GM. The underlying vulnerability is a single truckload feeding a production line with minimal buffer stock. Work with GM's materials planning team to increase the bracket buffer from 47 minutes (which is what the 06:47 line-down time implies) to 4 hours. This costs additional warehouse space and carrying cost at the assembly plant, but it converts a missed 2-hour delivery window from a $215,000 disaster to a minor scheduling inconvenience.
+6. Consider a carrier-of-last-resort arrangement for this lane. Identify a dedicated carrier or small fleet within 2 hours of Spring Hill that can run an emergency load if the primary carrier is delayed. Pre-stage one truckload of brackets at a cross-dock near Spring Hill as rolling safety stock. The carrying cost of $186,000 in brackets sitting at a cross-dock ($400–$600/month in storage) is insurance against $215,000 chargebacks.
+
+**Key Indicators:**
+- A BOL without a specific delivery time window provides the carrier zero legal exposure for consequential damages from late delivery — the entire consequential damages claim depends on documented, communicated time-sensitivity
+- GM and other major OEMs chargeback calculations are formulaic and include significant overhead allocation — they are always negotiable, though the negotiation requires understanding the OEM's cost model
+- A 47-minute buffer stock at an assembly plant is dangerously thin for a JIT delivery program — anything less than 2 hours of buffer for a 500+ mile lane is an organizational risk management failure
+- If the carrier has a history of on-time delivery for this lane (check their scorecard), this is an anomaly, not a pattern — that context helps in both the carrier conversation and the GM chargeback negotiation
+- Check whether the carrier experienced any en-route delays (weather, traffic, mechanical) that explain the 11:42 arrival. A documented en-route delay is a mitigating factor even though the carrier isn't technically liable.
+
+**Documentation Required:**
+- BOL showing delivery date without time window
+- Carrier rate confirmation showing "by end of day Tuesday"
+- GM's JIT scheduling system printout showing the 04:00–06:00 delivery window
+- GM's line-down notification and production stoppage report
+- GM's chargeback notice with detailed cost calculation
+- Carrier's delivery receipt showing 11:42 arrival and unloading
+- Carrier's ELD data showing en-route trip timeline
+- Internal corrective action report documenting the communication gap
+- Updated BOL and rate confirmation templates with JIT delivery window fields
+- Negotiated chargeback settlement agreement with GM
+- Carrier on-time performance scorecard for the lane (prior 12 months)
+
+**Resolution Timeline:**
+- Hours 0–4: Immediate crisis management — emergency unloading at GM, line restarted
+- Days 1–3: Root cause analysis, carrier conversation, GM chargeback received
+- Days 3–14: GM chargeback negotiation, internal corrective action drafted
+- Days 14–30: Corrective action implemented (BOL/rate confirmation process updates)
+- Days 30–45: GM chargeback settlement
+- Days 30–60: Buffer strategy and carrier-of-last-resort arrangement implemented
+- Ongoing: Monthly review of JIT delivery performance for all assembly plant lanes
+
+---
+
+## Cross-Cutting Lessons
+
+The edge cases above share several themes that experienced exception managers internalize:
+
+1. **Documentation at the moment of discovery is irreplaceable.** Photos, data downloads, witness statements, and physical evidence degrade or disappear within hours. The first responder's instinct should be to document, not to fix.
+
+2. **Separate the immediate crisis from the claim.** Getting the customer their product, containing the spill, or keeping the production line running is always the first priority. The claim can be filed for months afterward; the commercial or safety crisis cannot wait.
+
+3. **Liability is rarely 100% on one party.** Most complex exceptions involve shared fault — a shipper who didn't communicate, a carrier who didn't secure, a broker who didn't pay, a consignee who didn't inspect. Expert resolution is about finding the right allocation, not proving absolute fault.
+
+4. **Escalate through data, not emotion.** "Your driver broke our product" gets denied. "We have a pattern of 14 shortage claims correlating to your Atlanta terminal's second shift" gets investigated.
+
+5. **The carrier's front-line customer service sees the same portal you do.** For any exception involving real money or real urgency, go directly to the carrier's operations team, sales representative, or claims director. The 800-number is for routine inquiries, not for $200K exposures.
+
+6. **Contracts and tariffs are the battlefield.** Every surcharge dispute, every consequential damages claim, and every liability allocation ultimately comes down to what was written, what was communicated, and what was incorporated by reference. Read the tariff. Read the contract. Know what your counterparty actually agreed to.
+
+7. **Time is the most expensive variable.** Every day a perishable shipment sits at a carrier's yard, every hour an assembly line is down, every week a customs hold persists — these accrue costs that dwarf the underlying product value. Speed of resolution is not just a service metric; it's a financial imperative.
diff --git a/skills/m365-agents-dotnet/SKILL.md b/skills/m365-agents-dotnet/SKILL.md
index eb93c7eb..01b1885f 100644
--- a/skills/m365-agents-dotnet/SKILL.md
+++ b/skills/m365-agents-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-dotnet
-description: "|"
+description: |
Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "Microsoft.Agents", "AddAgentApplicationOptions", "AgentApplication", "AddAgentAspNetAuthentication", "Copilot Studio client", "IAgentHttpAdapter".
package: Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Authentication.Msal, Microsoft.Agents.CopilotStudio.Client
risk: unknown
diff --git a/skills/m365-agents-py/SKILL.md b/skills/m365-agents-py/SKILL.md
index 0583cd23..3ec3bbdf 100644
--- a/skills/m365-agents-py/SKILL.md
+++ b/skills/m365-agents-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-py
-description: "|"
+description: |
Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "microsoft_agents", "AgentApplication", "start_agent_process", "TurnContext", "Copilot Studio client", "CloudAdapter".
package: microsoft-agents-hosting-core, microsoft-agents-hosting-aiohttp, microsoft-agents-activity, microsoft-agents-authentication-msal, microsoft-agents-copilotstudio-client
risk: unknown
diff --git a/skills/m365-agents-ts/SKILL.md b/skills/m365-agents-ts/SKILL.md
index f62cadf7..b6ec66fe 100644
--- a/skills/m365-agents-ts/SKILL.md
+++ b/skills/m365-agents-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-ts
-description: "|"
+description: |
Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: "Microsoft 365 Agents SDK", "@microsoft/agents-hosting", "AgentApplication", "startServer", "streamingResponse", "Copilot Studio client", "@microsoft/agents-copilotstudio-client".
package: "@microsoft/agents-hosting, @microsoft/agents-hosting-express, @microsoft/agents-activity, @microsoft/agents-copilotstudio-client"
risk: unknown
diff --git a/skills/malware-analyst/SKILL.md b/skills/malware-analyst/SKILL.md
index d6737995..4b447911 100644
--- a/skills/malware-analyst/SKILL.md
+++ b/skills/malware-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: malware-analyst
-description: "Expert malware analyst specializing in defensive malware research,"
+description: |
+ Expert malware analyst specializing in defensive malware research,
threat intelligence, and incident response. Masters sandbox analysis,
behavioral analysis, and malware family identification. Handles static/dynamic
analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,
diff --git a/skills/market-sizing-analysis/SKILL.md b/skills/market-sizing-analysis/SKILL.md
index 0768dcd3..3ddc7dd0 100644
--- a/skills/market-sizing-analysis/SKILL.md
+++ b/skills/market-sizing-analysis/SKILL.md
@@ -1,6 +1,7 @@
---
name: market-sizing-analysis
-description: "This skill should be used when the user asks to \\\"calculate TAM\\\","
+description: |
+ This skill should be used when the user asks to \\\"calculate TAM\\\",
"determine SAM", "estimate SOM", "size the market", "calculate market
opportunity", "what's the total addressable market", or requests market sizing
analysis for a startup or business opportunity.
diff --git a/skills/mermaid-expert/SKILL.md b/skills/mermaid-expert/SKILL.md
index 424f298c..6e328913 100644
--- a/skills/mermaid-expert/SKILL.md
+++ b/skills/mermaid-expert/SKILL.md
@@ -1,6 +1,7 @@
---
name: mermaid-expert
-description: "Create Mermaid diagrams for flowcharts, sequences, ERDs, and"
+description: |
+ Create Mermaid diagrams for flowcharts, sequences, ERDs, and
architectures. Masters syntax for all diagram types and styling. Use
PROACTIVELY for visual documentation, system diagrams, or process flows.
metadata:
diff --git a/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md b/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
index e79459a7..d49dcee2 100644
--- a/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
+++ b/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: microsoft-azure-webjobs-extensions-authentication-events-dotnet
-description: "|"
+description: |
Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: "Authentication Events", "WebJobsAuthenticationEventsTrigger", "OnTokenIssuanceStart", "OnAttributeCollectionStart", "custom claims", "token enrichment", "Entra custom extension", "authentication extension".
risk: unknown
source: community
diff --git a/skills/minecraft-bukkit-pro/SKILL.md b/skills/minecraft-bukkit-pro/SKILL.md
index e52acd91..f89b7668 100644
--- a/skills/minecraft-bukkit-pro/SKILL.md
+++ b/skills/minecraft-bukkit-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: minecraft-bukkit-pro
-description: "Master Minecraft server plugin development with Bukkit, Spigot, and"
+description: |
+ Master Minecraft server plugin development with Bukkit, Spigot, and
Paper APIs. Specializes in event-driven architecture, command systems, world
manipulation, player management, and performance optimization. Use PROACTIVELY
for plugin architecture, gameplay mechanics, server-side features, or
diff --git a/skills/ml-engineer/SKILL.md b/skills/ml-engineer/SKILL.md
index f34b1020..4a816dc6 100644
--- a/skills/ml-engineer/SKILL.md
+++ b/skills/ml-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ml-engineer
-description: "Build production ML systems with PyTorch 2.x, TensorFlow, and"
+description: |
+ Build production ML systems with PyTorch 2.x, TensorFlow, and
modern ML frameworks. Implements model serving, feature engineering, A/B
testing, and monitoring. Use PROACTIVELY for ML model deployment, inference
optimization, or production ML infrastructure.
diff --git a/skills/mlops-engineer/SKILL.md b/skills/mlops-engineer/SKILL.md
index 97a59c63..511743e8 100644
--- a/skills/mlops-engineer/SKILL.md
+++ b/skills/mlops-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: mlops-engineer
-description: "Build comprehensive ML pipelines, experiment tracking, and model"
+description: |
+ Build comprehensive ML pipelines, experiment tracking, and model
registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated
training, deployment, and monitoring across cloud platforms. Use PROACTIVELY
for ML infrastructure, experiment management, or pipeline automation.
diff --git a/skills/mobile-developer/SKILL.md b/skills/mobile-developer/SKILL.md
index a347fb69..7c9de867 100644
--- a/skills/mobile-developer/SKILL.md
+++ b/skills/mobile-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: mobile-developer
-description: "Develop React Native, Flutter, or native mobile apps with modern"
+description: |
+ Develop React Native, Flutter, or native mobile apps with modern
architecture patterns. Masters cross-platform development, native
integrations, offline sync, and app store optimization. Use PROACTIVELY for
mobile features, cross-platform code, or app optimization.
diff --git a/skills/mobile-security-coder/SKILL.md b/skills/mobile-security-coder/SKILL.md
index 77e20219..d6756980 100644
--- a/skills/mobile-security-coder/SKILL.md
+++ b/skills/mobile-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: mobile-security-coder
-description: "Expert in secure mobile coding practices specializing in input"
+description: |
+ Expert in secure mobile coding practices specializing in input
validation, WebView security, and mobile-specific security patterns. Use
PROACTIVELY for mobile security implementations or mobile security code
reviews.
diff --git a/skills/network-engineer/SKILL.md b/skills/network-engineer/SKILL.md
index 3fc439d3..26cf7f66 100644
--- a/skills/network-engineer/SKILL.md
+++ b/skills/network-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: network-engineer
-description: "Expert network engineer specializing in modern cloud networking,"
+description: |
+ Expert network engineer specializing in modern cloud networking,
security architectures, and performance optimization. Masters multi-cloud
connectivity, service mesh, zero-trust networking, SSL/TLS, global load
balancing, and advanced troubleshooting. Handles CDN optimization, network
diff --git a/skills/observability-engineer/SKILL.md b/skills/observability-engineer/SKILL.md
index 6246773f..ac320312 100644
--- a/skills/observability-engineer/SKILL.md
+++ b/skills/observability-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: observability-engineer
-description: "Build production-ready monitoring, logging, and tracing systems."
+description: |
+ Build production-ready monitoring, logging, and tracing systems.
Implements comprehensive observability strategies, SLI/SLO management, and
incident response workflows. Use PROACTIVELY for monitoring infrastructure,
performance optimization, or production reliability.
diff --git a/skills/page-cro/SKILL.md b/skills/page-cro/SKILL.md
index cf1c1d80..bdb40688 100644
--- a/skills/page-cro/SKILL.md
+++ b/skills/page-cro/SKILL.md
@@ -1,6 +1,6 @@
---
name: page-cro
-description: ">"
+description: >
Analyze and optimize individual pages for conversion performance.
Use when the user wants to improve conversion rates, diagnose why a page
is underperforming, or increase the effectiveness of marketing pages
diff --git a/skills/payment-integration/SKILL.md b/skills/payment-integration/SKILL.md
index 5620721d..378ae43d 100644
--- a/skills/payment-integration/SKILL.md
+++ b/skills/payment-integration/SKILL.md
@@ -1,6 +1,7 @@
---
name: payment-integration
-description: "Integrate Stripe, PayPal, and payment processors. Handles checkout"
+description: |
+ Integrate Stripe, PayPal, and payment processors. Handles checkout
flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when
implementing payments, billing, or subscription features.
metadata:
diff --git a/skills/php-pro/SKILL.md b/skills/php-pro/SKILL.md
index 1bd59417..99fa90e7 100644
--- a/skills/php-pro/SKILL.md
+++ b/skills/php-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: php-pro
-description: "Write idiomatic PHP code with generators, iterators, SPL data"
+description: |
+ Write idiomatic PHP code with generators, iterators, SPL data
structures, and modern OOP features. Use PROACTIVELY for high-performance PHP
applications.
metadata:
diff --git a/skills/posix-shell-pro/SKILL.md b/skills/posix-shell-pro/SKILL.md
index 6e248286..b6c7824a 100644
--- a/skills/posix-shell-pro/SKILL.md
+++ b/skills/posix-shell-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: posix-shell-pro
-description: "Expert in strict POSIX sh scripting for maximum portability across"
+description: |
+ Expert in strict POSIX sh scripting for maximum portability across
Unix-like systems. Specializes in shell scripts that run on any
POSIX-compliant shell (dash, ash, sh, bash --posix).
metadata:
diff --git a/skills/production-scheduling/SKILL.md b/skills/production-scheduling/SKILL.md
new file mode 100644
index 00000000..02cd702d
--- /dev/null
+++ b/skills/production-scheduling/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: production-scheduling
+description: >
+ Codified expertise for production scheduling, job sequencing, line balancing,
+ changeover optimisation, and bottleneck resolution in discrete and batch
+ manufacturing. Informed by production schedulers with 15+ years experience.
+ Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response
+ frameworks, and ERP/MES interaction patterns. Use when scheduling production,
+ resolving bottlenecks, optimising changeovers, responding to disruptions,
+ or balancing manufacturing lines.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🏭"
+---
+
+## When to Use
+
+Use this skill when planning manufacturing operations, sequencing jobs to minimize changeover times, balancing production lines, resolving factory bottlenecks, or responding to unexpected equipment downtime and supply disruptions.
+
+# Production Scheduling
+
+## Role and Context
+
+You are a senior production scheduler at a discrete and batch manufacturing facility operating 3–8 production lines with 50–300 direct-labour headcount per shift. You manage job sequencing, line balancing, changeover optimization, and disruption response across work centres that include machining, assembly, finishing, and packaging. Your systems include an ERP (SAP PP, Oracle Manufacturing, or Epicor), a finite-capacity scheduling tool (Preactor, PlanetTogether, or Opcenter APS), an MES for shop floor execution and real-time reporting, and a CMMS for maintenance coordination. You sit between production management (which owns output targets and headcount), planning (which releases work orders from MRP), quality (which gates product release), and maintenance (which owns equipment availability). Your job is to translate a set of work orders with due dates, routings, and BOMs into a minute-by-minute execution sequence that maximises throughput at the constraint while meeting customer delivery commitments, labour rules, and quality requirements.
+
+## Core Knowledge
+
+### Scheduling Fundamentals
+
+**Forward vs. backward scheduling:** Forward scheduling starts from material availability date and schedules operations sequentially to find the earliest completion date. Backward scheduling starts from the customer due date and works backward to find the latest permissible start date. In practice, use backward scheduling as the default to preserve flexibility and minimise WIP, then switch to forward scheduling when the backward pass reveals that the latest start date is already in the past — that work order is already late-starting and needs to be expedited from today forward.
+
+**Finite vs. infinite capacity:** MRP runs infinite-capacity planning — it assumes every work centre has unlimited capacity and flags overloads for the scheduler to resolve manually. Finite-capacity scheduling (FCS) respects actual resource availability: machine count, shift patterns, maintenance windows, and tooling constraints. Never trust an MRP-generated schedule as executable without running it through finite-capacity logic. MRP tells you _what_ needs to be made; FCS tells you _when_ it can actually be made.
+
+**Drum-Buffer-Rope (DBR) and Theory of Constraints:** The drum is the constraint resource — the work centre with the least excess capacity relative to demand. The buffer is a time buffer (not inventory buffer) protecting the constraint from upstream starvation. The rope is the release mechanism that limits new work into the system to the constraint's processing rate. Identify the constraint by comparing load hours to available hours per work centre; the one with the highest utilisation ratio (>85%) is your drum. Subordinate every other scheduling decision to keeping the drum fed and running. A minute lost at the constraint is a minute lost for the entire plant; a minute lost at a non-constraint costs nothing if buffer time absorbs it.
+
+**JIT sequencing:** In mixed-model assembly environments, level the production sequence to minimise variation in component consumption rates. Use heijunka logic: if you produce models A, B, and C in a 3:2:1 ratio per shift, the ideal sequence is A-B-A-C-A-B, not AAA-BB-C. Levelled sequencing smooths upstream demand, reduces component safety stock, and prevents the "end-of-shift crunch" where the hardest jobs get pushed to the last hour.
+
+**Where MRP breaks down:** MRP assumes fixed lead times, infinite capacity, and perfect BOM accuracy. It fails when (a) lead times are queue-dependent and compress under light load or expand under heavy load, (b) multiple work orders compete for the same constrained resource, (c) setup times are sequence-dependent, or (d) yield losses create variable output from fixed input. Schedulers must compensate for all four.
+
+### Changeover Optimisation
+
+**SMED methodology (Single-Minute Exchange of Die):** Shigeo Shingo's framework divides setup activities into external (can be done while the machine is still running the previous job) and internal (must be done with the machine stopped). Phase 1: document the current setup and classify every element as internal or external. Phase 2: convert internal elements to external wherever possible (pre-staging tools, pre-heating moulds, pre-mixing materials). Phase 3: streamline remaining internal elements (quick-release clamps, standardised die heights, colour-coded connections). Phase 4: eliminate adjustments through poka-yoke and first-piece verification jigs. Typical results: 40–60% setup time reduction from Phase 1–2 alone.
+
+**Colour/size sequencing:** In painting, coating, printing, and textile operations, sequence jobs from light to dark, small to large, or simple to complex to minimise cleaning between runs. A light-to-dark paint sequence might need only a 5-minute flush; dark-to-light requires a 30-minute full-purge. Capture these sequence-dependent setup times in a setup matrix and feed it to the scheduling algorithm.
+
+**Campaign vs. mixed-model scheduling:** Campaign scheduling groups all jobs of the same product family into a single run, minimising total changeovers but increasing WIP and lead times. Mixed-model scheduling interleaves products to reduce lead times and WIP but incurs more changeovers. The right balance depends on the changeover-cost-to-carrying-cost ratio. When changeovers are long and expensive (>60 minutes, >$500 in scrap and lost output), lean toward campaigns. When changeovers are fast (<15 minutes) or when customer order profiles demand short lead times, lean toward mixed-model.
+
+**Changeover cost vs. inventory carrying cost vs. delivery tradeoff:** Every scheduling decision involves this three-way tension. Longer campaigns reduce changeover cost but increase cycle stock and risk missing due dates for non-campaign products. Shorter campaigns improve delivery responsiveness but increase changeover frequency. The economic crossover point is where marginal changeover cost equals marginal carrying cost per unit of additional cycle stock. Compute it; don't guess.
+
+### Bottleneck Management
+
+**Identifying the true constraint vs. where WIP piles up:** WIP accumulation in front of a work centre does not necessarily mean that work centre is the constraint. WIP can pile up because the upstream work centre is batch-dumping, because a shared resource (crane, forklift, inspector) creates an artificial queue, or because a scheduling rule creates starvation downstream. The true constraint is the resource with the highest ratio of required hours to available hours. Verify by checking: if you added one hour of capacity at this work centre, would plant output increase? If yes, it is the constraint.
+
+**Buffer management:** In DBR, the time buffer is typically 50% of the production lead time for the constraint operation. Monitor buffer penetration: green zone (buffer consumed < 33%) means the constraint is well-protected; yellow zone (33–67%) triggers expediting of late-arriving upstream work; red zone (>67%) triggers immediate management attention and possible overtime at upstream operations. Buffer penetration trends over weeks reveal chronic problems: persistent yellow means upstream reliability is degrading.
+
+**Subordination principle:** Non-constraint resources should be scheduled to serve the constraint, not to maximise their own utilisation. Running a non-constraint at 100% utilisation when the constraint operates at 85% creates excess WIP with no throughput gain. Deliberately schedule idle time at non-constraints to match the constraint's consumption rate.
+
+**Detecting shifting bottlenecks:** The constraint can move between work centres as product mix changes, as equipment degrades, or as staffing shifts. A work centre that is the bottleneck on day shift (running high-setup products) may not be the bottleneck on night shift (running long-run products). Monitor utilisation ratios weekly by product mix. When the constraint shifts, the entire scheduling logic must shift with it — the new drum dictates the tempo.
+
+### Disruption Response
+
+**Machine breakdowns:** Immediate actions: (1) assess repair time estimate with maintenance, (2) determine if the broken machine is the constraint, (3) if constraint, calculate throughput loss per hour and activate the contingency plan — overtime on alternate equipment, subcontracting, or re-sequencing to prioritise highest-margin jobs. If not the constraint, assess buffer penetration — if buffer is green, do nothing to the schedule; if yellow or red, expedite upstream work to alternate routings.
+
+**Material shortages:** Check substitute materials, alternate BOMs, and partial-build options. If a component is short, can you build sub-assemblies to the point of the missing component and complete later (kitting strategy)? Escalate to purchasing for expedited delivery. Re-sequence the schedule to pull forward jobs that do not require the short material, keeping the constraint running.
+
+**Quality holds:** When a batch is placed on quality hold, it is invisible to the schedule — it cannot ship and it cannot be consumed downstream. Immediately re-run the schedule excluding held inventory. If the held batch was feeding a customer commitment, assess alternative sources: safety stock, in-process inventory from another work order, or expedited production of a replacement batch.
+
+**Absenteeism:** With certified operator requirements, one absent operator can disable an entire line. Maintain a cross-training matrix showing which operators are certified on which equipment. When absenteeism occurs, first check whether the missing operator runs the constraint — if so, reassign the best-qualified backup. If the missing operator runs a non-constraint, assess whether buffer time absorbs the delay before pulling a backup from another area.
+
+**Re-sequencing framework:** When disruption hits, apply this priority logic: (1) protect constraint uptime above all else, (2) protect customer commitments in order of customer tier and penalty exposure, (3) minimise total changeover cost of the new sequence, (4) level labour load across remaining available operators. Re-sequence, communicate the new schedule within 30 minutes, and lock it for at least 4 hours before allowing further changes.
+
+### Labour Management
+
+**Shift patterns:** Common patterns include 3×8 (three 8-hour shifts, 24/5 or 24/7), 2×12 (two 12-hour shifts, often with rotating days), and 4×10 (four 10-hour days for day-shift-only operations). Each pattern has different implications for overtime rules, handover quality, and fatigue-related error rates. 12-hour shifts reduce handovers but increase error rates in hours 10–12. Factor this into scheduling: do not put critical first-piece inspections or complex changeovers in the last 2 hours of a 12-hour shift.
+
+**Skill matrices:** Maintain a matrix of operator × work centre × certification level (trainee, qualified, expert). Scheduling feasibility depends on this matrix — a work order routed to a CNC lathe is infeasible if no qualified operator is on shift. The scheduling tool should carry labour as a constraint alongside machines.
+
+**Cross-training ROI:** Each additional operator certified on the constraint work centre reduces the probability of constraint starvation due to absenteeism. Quantify: if the constraint generates $5,000/hour in throughput and average absenteeism is 8%, having only 2 qualified operators vs. 4 qualified operators changes the expected throughput loss by $200K+/year.
+
+**Union rules and overtime:** Many manufacturing environments have contractual constraints on overtime assignment (by seniority), mandatory rest periods between shifts (typically 8–10 hours), and restrictions on temporary reassignment across departments. These are hard constraints that the scheduling algorithm must respect. Violating a union rule can trigger a grievance that costs far more than the production it was meant to save.
+
+### OEE — Overall Equipment Effectiveness
+
+**Calculation:** OEE = Availability × Performance × Quality. Availability = (Planned Production Time − Downtime) / Planned Production Time. Performance = (Ideal Cycle Time × Total Pieces) / Operating Time. Quality = Good Pieces / Total Pieces. World-class OEE is 85%+; typical discrete manufacturing runs 55–65%.
+
+**Planned vs. unplanned downtime:** Planned downtime (scheduled maintenance, changeovers, breaks) is excluded from the Availability denominator in some OEE standards and included in others. Use TEEP (Total Effective Equipment Performance) when you need to compare across plants or justify capital expansion — TEEP includes all calendar time.
+
+**Availability losses:** Breakdowns and unplanned stops. Address with preventive maintenance, predictive maintenance (vibration analysis, thermal imaging), and TPM operator-level daily checks. Target: unplanned downtime < 5% of scheduled time.
+
+**Performance losses:** Speed losses and micro-stops. A machine rated at 100 parts/hour running at 85 parts/hour has a 15% performance loss. Common causes: material feed inconsistencies, worn tooling, sensor false-triggers, and operator hesitation. Track actual cycle time vs. standard cycle time per job.
+
+**Quality losses:** Scrap and rework. First-pass yield below 95% on a constraint operation directly reduces effective capacity. Prioritise quality improvement at the constraint — a 2% yield improvement at the constraint delivers the same throughput gain as a 2% capacity expansion.
+
+### ERP/MES Interaction Patterns
+
+**SAP PP / Oracle Manufacturing production planning flow:** Demand enters as sales orders or forecast consumption, drives MPS (Master Production Schedule), which explodes through MRP into planned orders by work centre with material requirements. The scheduler converts planned orders into production orders, sequences them, and releases to the shop floor via MES. Feedback flows from MES (operation confirmations, scrap reporting, labour booking) back to ERP to update order status and inventory.
+
+**Work order management:** A work order carries the routing (sequence of operations with work centres, setup times, and run times), the BOM (components required), and the due date. The scheduler's job is to assign each operation to a specific time slot on a specific resource, respecting resource capacity, material availability, and dependency constraints (operation 20 cannot start until operation 10 is complete).
+
+**Shop floor reporting and plan-vs-reality gap:** MES captures actual start/end times, actual quantities produced, scrap counts, and downtime reasons. The gap between the schedule and MES actuals is the "plan adherence" metric. Healthy plan adherence is > 90% of jobs starting within ±1 hour of scheduled start. Persistent gaps indicate that either the scheduling parameters (setup times, run rates, yield factors) are wrong or that the shop floor is not following the sequence.
+
+**Closing the loop:** Every shift, compare scheduled vs. actual at the operation level. Update the schedule with actuals, re-sequence the remaining horizon, and publish the updated schedule. This "rolling re-plan" cadence keeps the schedule realistic rather than aspirational. The worst failure mode is a schedule that diverges from reality and becomes ignored by the shop floor — once operators stop trusting the schedule, it ceases to function.
+
+## Decision Frameworks
+
+### Job Priority Sequencing
+
+When multiple jobs compete for the same resource, apply this decision tree:
+
+1. **Is any job past-due or will miss its due date without immediate processing?** → Schedule past-due jobs first, ordered by customer penalty exposure (contractual penalties > reputational damage > internal KPI impact).
+2. **Are any jobs feeding the constraint and the constraint buffer is in yellow or red zone?** → Schedule constraint-feeding jobs next to prevent constraint starvation.
+3. **Among remaining jobs, apply the dispatching rule appropriate to the product mix:**
+ - High-variety, short-run: use **Earliest Due Date (EDD)** to minimise maximum lateness.
+ - Long-run, few products: use **Shortest Processing Time (SPT)** to minimise average flow time and WIP.
+ - Mixed, with sequence-dependent setups: use **setup-aware EDD** — EDD with a setup-time lookahead that swaps adjacent jobs when a swap saves >30 minutes of setup without causing a due date miss.
+4. **Tie-breaker:** Higher customer tier wins. If same tier, higher margin job wins.
+
+### Changeover Sequence Optimisation
+
+1. **Build the setup matrix:** For each pair of products (A→B, B→A, A→C, etc.), record the changeover time in minutes and the changeover cost (labour + scrap + lost output).
+2. **Identify mandatory sequence constraints:** Some transitions are prohibited (allergen cross-contamination in food, hazardous material sequencing in chemical). These are hard constraints, not optimisable.
+3. **Apply nearest-neighbour heuristic as baseline:** From the current product, select the next product with the smallest changeover time. This gives a feasible starting sequence.
+4. **Improve with 2-opt swaps:** Swap pairs of adjacent jobs; keep the swap if total changeover time decreases without violating due dates.
+5. **Validate against due dates:** Run the optimised sequence through the schedule. If any job misses its due date, insert it earlier even if it increases total changeover time. Due date compliance trumps changeover optimisation.
+
+### Disruption Re-Sequencing
+
+When a disruption invalidates the current schedule:
+
+1. **Assess impact window:** How many hours/shifts is the disrupted resource unavailable? Is it the constraint?
+2. **Freeze committed work:** Jobs already in process or within 2 hours of start should not be moved unless physically impossible.
+3. **Re-sequence remaining jobs:** Apply the job priority framework above to all unfrozen jobs, using updated resource availability.
+4. **Communicate within 30 minutes:** Publish the revised schedule to all affected work centres, supervisors, and material handlers.
+5. **Set a stability lock:** No further schedule changes for at least 4 hours (or until next shift start) unless a new disruption occurs. Constant re-sequencing creates more chaos than the original disruption.
+
+### Bottleneck Identification
+
+1. **Pull utilisation reports** for all work centres over the trailing 2 weeks (by shift, not averaged).
+2. **Rank by utilisation ratio** (load hours / available hours). The top work centre is the suspected constraint.
+3. **Verify causally:** Would adding one hour of capacity at this work centre increase total plant output? If the work centre downstream of it is always starved when this one is down, the answer is yes.
+4. **Check for shifting patterns:** If the top-ranked work centre changes between shifts or between weeks, you have a shifting bottleneck driven by product mix. In this case, schedule the constraint _for each shift_ based on that shift's product mix, not on a weekly average.
+5. **Distinguish from artificial constraints:** A work centre that appears overloaded because upstream batch-dumps WIP into it is not a true constraint — it is a victim of poor upstream scheduling. Fix the upstream release rate before adding capacity to the victim.
+
+## Key Edge Cases
+
+Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md).
+
+1. **Shifting bottleneck mid-shift:** Product mix change moves the constraint from machining to assembly during the shift. The schedule that was optimal at 6:00 AM is wrong by 10:00 AM. Requires real-time utilisation monitoring and intra-shift re-sequencing authority.
+
+2. **Certified operator absent for regulated process:** An FDA-regulated coating operation requires a specific operator certification. The only certified night-shift operator calls in sick. The line cannot legally run. Activate the cross-training matrix, call in a certified day-shift operator on overtime if permitted, or shut down the regulated operation and re-route non-regulated work.
+
+3. **Competing rush orders from tier-1 customers:** Two top-tier automotive OEM customers both demand expedited delivery. Satisfying one delays the other. Requires commercial decision input — which customer relationship carries higher penalty exposure or strategic value? The scheduler identifies the tradeoff; management decides.
+
+4. **MRP phantom demand from BOM error:** A BOM listing error causes MRP to generate planned orders for a component that is not actually consumed. The scheduler sees a work order with no real demand behind it. Detect by cross-referencing MRP-generated demand against actual sales orders and forecast consumption. Flag and hold — do not schedule phantom demand.
+
+5. **Quality hold on WIP affecting downstream:** A paint defect is discovered on 200 partially complete assemblies. These were scheduled to feed the final assembly constraint tomorrow. The constraint will starve unless replacement WIP is expedited from an earlier stage or alternate routing is used.
+
+6. **Equipment breakdown at the constraint:** The single most damaging disruption. Every minute of constraint downtime equals lost throughput for the entire plant. Trigger immediate maintenance response, activate alternate routing if available, and notify customers whose orders are at risk.
+
+7. **Supplier delivers wrong material mid-run:** A batch of steel arrives with the wrong alloy specification. Jobs already kitted with this material cannot proceed. Quarantine the material, re-sequence to pull forward jobs using a different alloy, and escalate to purchasing for emergency replacement.
+
+8. **Customer order change after production started:** The customer modifies quantity or specification after work is in process. Assess sunk cost of work already completed, rework feasibility, and impact on other jobs sharing the same resource. A partial-completion hold may be cheaper than scrapping and restarting.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Daily schedule publication:** Clear, structured, no ambiguity. Job sequence, start times, line assignments, operator assignments. Use table format. The shop floor does not read paragraphs.
+- **Schedule change notification:** Urgent header, reason for change, specific jobs affected, new sequence and timing. "Effective immediately" or "effective at [time]."
+- **Disruption escalation:** Lead with impact magnitude (hours of constraint time lost, number of customer orders at risk), then cause, then proposed response, then decision needed from management.
+- **Overtime request:** Quantify the business case — cost of overtime vs. cost of missed deliveries. Include union rule compliance. "Requesting 4 hours voluntary OT for CNC operators (3 personnel) on Saturday AM. Cost: $1,200. At-risk revenue without OT: $45,000."
+- **Customer delivery impact notice:** Never surprise the customer. As soon as a delay is likely, notify with the new estimated date, root cause (without blaming internal teams), and recovery plan. "Due to an equipment issue, order #12345 will ship [new date] vs. the original [old date]. We are running overtime to minimise the delay."
+- **Maintenance coordination:** Specific window requested, business justification for the timing, impact if maintenance is deferred. "Requesting PM window on Line 3, Tuesday 06:00–10:00. This avoids the Thursday changeover peak. Deferring past Friday risks an unplanned breakdown — vibration readings are trending into the caution zone."
+
+Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------- |
+| Constraint work centre down > 30 minutes unplanned | Alert production manager + maintenance manager | Immediate |
+| Plan adherence drops below 80% for a shift | Root cause analysis with shift supervisor | Within 4 hours |
+| Customer order projected to miss committed ship date | Notify sales and customer service with revised ETA | Within 2 hours of detection |
+| Overtime requirement exceeds weekly budget by > 20% | Escalate to plant manager with cost-benefit analysis | Within 1 business day |
+| OEE at constraint drops below 65% for 3 consecutive shifts | Trigger focused improvement event (maintenance + engineering + scheduling) | Within 1 week |
+| Quality yield at constraint drops below 93% | Joint review with quality engineering | Within 24 hours |
+| MRP-generated load exceeds finite capacity by > 15% for the upcoming week | Capacity meeting with planning and production management | 2 days before the overloaded week |
+
+### Escalation Chain
+
+Level 1 (Production Scheduler) → Level 2 (Production Manager / Shift Superintendent, 30 min for constraint issues, 4 hours for non-constraint) → Level 3 (Plant Manager, 2 hours for customer-impacting issues) → Level 4 (VP Operations, same day for multi-customer impact or safety-related schedule changes)
+
+## Performance Indicators
+
+Track per shift and trend weekly:
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------------- | ------------------ | -------------- |
+| Schedule adherence (jobs started within ±1 hour) | > 90% | < 80% |
+| On-time delivery (to customer commit date) | > 95% | < 90% |
+| OEE at constraint | > 75% | < 65% |
+| Changeover time vs. standard | < 110% of standard | > 130% |
+| WIP days (total WIP value / daily COGS) | < 5 days | > 8 days |
+| Constraint utilisation (actual producing / available) | > 85% | < 75% |
+| First-pass yield at constraint | > 97% | < 93% |
+| Unplanned downtime (% of scheduled time) | < 5% | > 10% |
+| Labour utilisation (direct hours / available hours) | 80–90% | < 70% or > 95% |
+
+## Additional Resources
+
+- For detailed decision frameworks, scheduling algorithms, and optimisation methodologies, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design or adjust production schedules and constraint‑focused execution plans**:
+
+- Sequencing jobs, balancing lines, and optimising changeovers in discrete or batch manufacturing.
+- Responding to disruptions (machine breakdowns, shortages, quality holds, absenteeism) while protecting the bottleneck and customer commitments.
+- Building scheduling rules, KPIs, and communication patterns between planning, production, maintenance, and quality teams.
diff --git a/skills/production-scheduling/references/communication-templates.md b/skills/production-scheduling/references/communication-templates.md
new file mode 100644
index 00000000..827f6877
--- /dev/null
+++ b/skills/production-scheduling/references/communication-templates.md
@@ -0,0 +1,503 @@
+# Communication Templates — Production Scheduling
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing production scheduling communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and purpose. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Production Schedule Publication](#1-production-schedule-publication)
+2. [Schedule Change Notification](#2-schedule-change-notification)
+3. [Disruption Alert](#3-disruption-alert)
+4. [Overtime Request](#4-overtime-request)
+5. [Customer Delivery Impact Notice](#5-customer-delivery-impact-notice)
+6. [Maintenance Coordination Request](#6-maintenance-coordination-request)
+7. [Quality Hold Notification](#7-quality-hold-notification)
+8. [Capacity Constraint Escalation](#8-capacity-constraint-escalation)
+9. [New Product Trial Run Request](#9-new-product-trial-run-request)
+10. [Cross-Functional Priority Alignment](#10-cross-functional-priority-alignment)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{date}}` | Date of communication | `2025-09-15` |
+| `{{shift}}` | Shift identifier | `Day Shift (06:00–14:00)` |
+| `{{line_id}}` | Production line identifier | `Line 3 — CNC Machining Cell` |
+| `{{work_order}}` | Work order number | `WO-2025-04823` |
+| `{{product}}` | Product name/number | `Valve Body Assembly VB-220` |
+| `{{customer}}` | Customer name | `Apex Automotive GmbH` |
+| `{{customer_po}}` | Customer purchase order | `APX-PO-88412` |
+| `{{qty}}` | Quantity | `500 units` |
+| `{{due_date}}` | Customer due date | `2025-09-22` |
+| `{{revised_date}}` | Revised delivery date | `2025-09-25` |
+| `{{scheduler_name}}` | Scheduler name | `Dave Morrison` |
+| `{{scheduler_title}}` | Scheduler title | `Senior Production Scheduler` |
+| `{{scheduler_email}}` | Scheduler email | `d.morrison@mfgco.com` |
+| `{{scheduler_phone}}` | Scheduler phone | `(513) 555-0147` |
+| `{{plant}}` | Plant name/location | `Cincinnati Plant — Building 2` |
+| `{{constraint_wc}}` | Constraint work centre | `CNC Horizontal Boring — WC 420` |
+| `{{oee_value}}` | OEE percentage | `72%` |
+| `{{downtime_hrs}}` | Downtime hours | `4.5 hours` |
+| `{{changeover_time}}` | Changeover duration | `45 minutes` |
+| `{{operator_name}}` | Operator name | `J. Rodriguez` |
+| `{{supervisor_name}}` | Shift supervisor | `Karen Phillips` |
+| `{{maintenance_lead}}` | Maintenance lead | `Tom Becker` |
+| `{{quality_lead}}` | Quality lead | `Dr. Sarah Chen` |
+
+---
+
+## 1. Production Schedule Publication
+
+**Audience:** Shift supervisors, operators, material handlers, quality inspectors
+**Frequency:** Published at shift start; updated only if disruption requires re-sequencing
+**Format:** Table-driven, no paragraphs. Shop floor reads tables, not prose.
+**Delivery:** Printed and posted at each work centre + emailed to supervisors + displayed on MES screens
+
+---
+
+**Subject:** Production Schedule — {{plant}} — {{shift}} — {{date}}
+
+**Schedule published by:** {{scheduler_name}} at {{date}} {{time}}
+
+**Priority Legend:** 🔴 Past-due or critical | 🟡 At risk (CR < 1.0) | 🟢 On schedule
+
+| Seq | Work Order | Product | Qty | Start Time | End Time | Work Centre | Operator | Priority | Notes |
+|---|---|---|---|---|---|---|---|---|---|
+| 1 | {{work_order}} | {{product}} | {{qty}} | 06:00 | 08:30 | {{line_id}} | {{operator_name}} | 🔴 | Rush — customer line-down |
+| 2 | WO-2025-04824 | Housing H-340 | 200 | 08:45 | 11:15 | {{line_id}} | {{operator_name}} | 🟢 | Std changeover at 08:30 |
+| 3 | WO-2025-04826 | Bracket BR-110 | 350 | 11:30 | 14:00 | {{line_id}} | {{operator_name}} | 🟡 | Material confirm by 10:00 |
+
+**Changeover Summary:**
+- 08:30–08:45: Changeover WO-04823 → WO-04824 (tooling pre-staged at machine)
+- 11:15–11:30: Changeover WO-04824 → WO-04826 (fixture change, 15 min)
+
+**Material Status:**
+- WO-04823: All material staged ✅
+- WO-04824: All material staged ✅
+- WO-04826: Bracket raw material pending — confirm with stores by 10:00 ⚠️
+
+**Labour Notes:**
+- {{operator_name}} certified on all three jobs
+- Relief operator for 10:00 break: M. Thompson
+
+**Constraint Status:** {{constraint_wc}} — current OEE {{oee_value}}. Buffer status: GREEN.
+
+**Do not deviate from this sequence without scheduler approval.**
+
+---
+
+**Tone guidance:** Directive, not conversational. The schedule is an instruction, not a suggestion. Use clear times, no approximations. Flag risks with symbols that are visible at a glance. Include material and labour status because the most common schedule disruption is "I didn't have the material" or "nobody told me I was on this job."
+
+---
+
+## 2. Schedule Change Notification
+
+**Audience:** Shift supervisors, affected operators, material handlers
+**Trigger:** Any change to the published schedule during the frozen zone
+**Delivery:** In-person verbal confirmation + written (posted + emailed)
+
+---
+
+**Subject:** ⚠️ SCHEDULE CHANGE — {{line_id}} — Effective {{effective_time}}
+
+**Change issued by:** {{scheduler_name}} at {{date}} {{time}}
+**Approved by:** {{supervisor_name}} (Production Manager approval required for frozen-zone changes)
+
+**Reason for change:** {{change_reason}}
+
+**What changed:**
+
+| | Before | After |
+|---|---|---|
+| Job sequence at {{line_id}} | WO-04824 → WO-04826 | WO-04826 → WO-04824 |
+| WO-04826 start time | 11:30 | 08:45 |
+| WO-04824 start time | 08:45 | 11:30 |
+| Changeover | Tooling → Fixture (15 min) | Fixture → Tooling (20 min) |
+
+**Why:** {{detailed_reason}} — e.g., "WO-04826 material (bracket raw stock) arrived early. WO-04826 due date is 1 day earlier than WO-04824. Swapping sequence saves 5 minutes of changeover time and improves on-time delivery for both orders."
+
+**Impact on other work centres:** None — downstream operations unaffected.
+
+**Action required:**
+- Material handler: Re-stage WO-04826 material at {{line_id}} by 08:30.
+- Operator: Confirm fixture change procedure for WO-04826 with setup technician.
+
+**No further changes to this shift's schedule unless a new disruption occurs.**
+
+---
+
+**Tone guidance:** Authoritative but explanatory. The "why" is important because frequent unexplained changes erode shop floor trust in the schedule. Always include who approved the change (accountability). End with a stability commitment — "no further changes" — to prevent the shop floor from anticipating constant flux.
+
+---
+
+## 3. Disruption Alert
+
+**Audience:** Production manager, maintenance manager, shift supervisors, planning
+**Trigger:** Any unplanned event affecting the constraint or customer deliveries
+**Delivery:** Immediate — phone/radio for constraint events, email for non-constraint
+
+---
+
+**Subject:** 🔴 DISRUPTION ALERT — {{disruption_type}} at {{line_id}} — {{date}} {{time}}
+
+**Reported by:** {{scheduler_name}}
+**Severity:** {{severity}} (Critical / Major / Minor)
+
+**What happened:**
+{{disruption_description}}
+Example: "Hydraulic pump failure on CNC Horizontal Boring Mill (WC 420) at 09:15. Machine stopped mid-cycle on WO-04823 (defence contract valve body, $38,000 piece in machine). Maintenance assessment: pump replacement required, 6–8 hour repair estimated."
+
+**Impact:**
+- **Constraint affected:** Yes / No
+- **Estimated downtime:** {{downtime_hrs}}
+- **Throughput loss:** {{throughput_loss}} (e.g., "$4,800 — 6 hours × $800/hr constraint throughput")
+- **Customer orders at risk:** {{at_risk_orders}} (e.g., "3 orders totalling $220,000, due dates within 2 weeks")
+- **Current buffer status:** {{buffer_status}} (e.g., "Buffer was GREEN, will reach RED in 4 hours if not resolved")
+
+**Immediate actions taken:**
+1. Machine isolated. Maintenance on-site.
+2. Replacement pump ordered from OEM distributor — ETA {{pump_eta}}.
+3. In-machine part assessed: datum offsets preserved, part likely salvageable on restart.
+4. Queued jobs reviewed for alternate routing — 3 of 14 can run on vertical CNC.
+
+**Decision needed from management:**
+- Authorise Saturday overtime (8 hours, estimated cost ${{overtime_cost}}) to recover lost capacity? Y/N
+- Approve subcontracting for {{subcontract_jobs}} to external shop (cost ${{subcontract_cost}})? Y/N
+- Customer notification: approve revised delivery dates for {{at_risk_customers}}? Y/N
+
+**Next update:** {{next_update_time}} or when repair status changes.
+
+---
+
+**Tone guidance:** Lead with impact, not description. The production manager needs to know "how bad is this?" before "what exactly happened." Quantify everything in hours and dollars. Present decisions as explicit Y/N choices — do not leave it ambiguous. Set a next-update cadence so management isn't chasing you for information.
+
+---
+
+## 4. Overtime Request
+
+**Audience:** Production manager (approval), HR/payroll (processing), affected operators
+**Trigger:** Capacity shortfall that can be recovered with additional hours
+**Delivery:** Email with formal cost justification; verbal pre-approval for urgency
+
+---
+
+**Subject:** Overtime Request — {{line_id}} — {{date_range}}
+
+**Requested by:** {{scheduler_name}}
+**Date of request:** {{date}}
+
+**Business justification:**
+{{business_case}}
+Example: "Constraint work centre (CNC Boring, WC 420) lost 20 hours due to unplanned hydraulic failure on 9/15. Recovery requires Saturday overtime shift to process queued customer orders and prevent 3 delivery misses totalling $220,000 in at-risk revenue."
+
+**Overtime details:**
+
+| Item | Detail |
+|---|---|
+| Work centre | {{constraint_wc}} |
+| Date(s) | {{overtime_dates}} (e.g., Saturday 9/20, 06:00–14:00) |
+| Duration | {{overtime_hours}} hours |
+| Personnel required | {{personnel_count}} (e.g., 2 CNC operators + 1 setup tech) |
+| Personnel names | {{personnel_names}} (voluntary — confirmed availability) |
+| Estimated cost | ${{overtime_cost}} ({{hours}} hrs × ${{rate}}/hr × {{multiplier}} OT premium) |
+| Union compliance | ✅ Voluntary. Offered by seniority per CBA Article 14.3. 8-hour rest observed. |
+
+**Revenue at risk without overtime:** ${{revenue_at_risk}}
+**Cost-to-benefit ratio:** {{ratio}} (e.g., "$1,200 OT cost to protect $220,000 revenue = 183:1 ROI")
+
+**Orders recovered with overtime:**
+
+| Work Order | Customer | Due Date | Status Without OT | Status With OT |
+|---|---|---|---|---|
+| WO-04825 | {{customer}} | {{due_date}} | 2 days late | On time |
+| WO-04827 | Nexus Defense | 9/26 | 1 day late | On time |
+| WO-04829 | Summit Aero | 9/28 | On time (barely) | Comfortable margin |
+
+**Approval requested by:** {{approval_deadline}} (e.g., "Thursday 5:00 PM to allow operator notification per CBA 48-hour notice requirement")
+
+---
+
+**Tone guidance:** Treat overtime requests as business cases, not pleas. Quantify both the cost and the benefit. Include union compliance confirmation proactively — the production manager should not have to ask. Provide the approval deadline because overtime notification requirements are contractual, not flexible.
+
+---
+
+## 5. Customer Delivery Impact Notice
+
+**Audience:** Sales/account manager (internal), then customer
+**Trigger:** Any order projected to miss its committed delivery date
+**Delivery:** Internal first (email + phone to account manager), then customer (via account manager or directly)
+
+---
+
+**Internal Version (to Sales/Account Manager):**
+
+**Subject:** Delivery Impact — {{customer}} — Order {{customer_po}} — Revised ETA {{revised_date}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Summary:**
+Order {{customer_po}} for {{customer}} ({{qty}} of {{product}}, original commit date {{due_date}}) will ship {{delay_days}} days late. Revised delivery date: {{revised_date}}.
+
+**Root cause:** {{root_cause_internal}}
+Example: "Unplanned constraint downtime on 9/15 (hydraulic failure, 20 hours lost) consumed the schedule buffer. Recovery overtime approved but insufficient to fully close the gap for all affected orders."
+
+**Recovery actions in progress:**
+- Saturday overtime shift authorised (recovers 8 hours)
+- 3 lower-priority jobs subcontracted to reduce constraint queue (recovers 6 hours)
+- Remaining gap: 6 hours, which pushes {{customer_po}} delivery from {{due_date}} to {{revised_date}}
+
+**Contractual exposure:** {{penalty_info}}
+Example: "Customer A framework agreement includes $25,000/day late delivery penalty. 3-day delay = $75,000 exposure. Recommend proactive notification and negotiation."
+
+**Recommended customer message:** See external version below. Please review and send by {{notification_deadline}}, or let me know if you'd like to adjust the messaging.
+
+---
+
+**External Version (to Customer):**
+
+**Subject:** Delivery Update — Order {{customer_po}}
+
+Dear {{customer_contact}},
+
+I am writing to update you on the delivery timeline for your order {{customer_po}} ({{qty}} of {{product}}).
+
+Due to {{root_cause_external}} (e.g., "an equipment issue at our machining facility"), we are revising the delivery date from {{due_date}} to {{revised_date}}.
+
+We have taken the following actions to minimise the delay:
+- Authorised additional production shifts dedicated to your order
+- Re-prioritised your order to the front of the production queue
+- Assigned our senior machining team to ensure quality and speed
+
+We understand the impact this may have on your operations and sincerely regret the inconvenience. If the revised date presents difficulties, please let us know and we will explore every option to accelerate further.
+
+{{scheduler_name}} is available at {{scheduler_phone}} for any questions about the production status.
+
+Regards,
+{{account_manager_name}}
+{{account_manager_title}}
+{{our_company}}
+
+---
+
+**Tone guidance — internal:** Factual, quantified, includes penalty exposure. The account manager needs the full picture to make the right call on messaging.
+
+**Tone guidance — external:** Proactive (before the customer discovers the delay), accountable (acknowledge the impact), action-oriented (show what you're doing), no blame (do not name internal equipment or personnel). Never use "we apologise for any inconvenience" — that phrase signals insincerity. Instead, acknowledge the specific impact on their operations.
+
+---
+
+## 6. Maintenance Coordination Request
+
+**Audience:** Maintenance manager/planner
+**Trigger:** Scheduling a preventive maintenance window, or requesting priority on corrective maintenance
+**Delivery:** Email + calendar invite for planned; phone/radio + email for urgent
+
+---
+
+**Subject:** Maintenance Window Request — {{line_id}} — {{requested_date_range}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Request type:** Preventive Maintenance / Corrective Maintenance / Calibration
+
+**Equipment:** {{equipment_id}} (e.g., "600-ton Stamping Press #2, Asset Tag SP-602")
+**Work centre:** {{constraint_wc}}
+
+**Requested window:** {{pm_start}} to {{pm_end}} (e.g., "Saturday 9/20, 06:00–16:00, 10 hours")
+
+**Business justification for this timing:**
+{{timing_justification}}
+Example: "Saturday window avoids impacting the Week 39 production plan, which is loaded at 94% Mon–Fri. Vibration readings on SP-602 are trending into the caution zone (0.28 in/s, threshold is 0.30). Deferring beyond Saturday increases the risk of an unplanned breakdown during the peak Monday–Wednesday production window."
+
+**Impact if deferred:**
+- Probability of unplanned failure in next 2 weeks: {{failure_probability}} (e.g., "estimated 35% based on vibration trend and historical MTBF data")
+- Cost of unplanned failure: {{failure_cost}} (e.g., "$16,000 lost throughput + $5,000 emergency repair + potential die damage")
+- Production orders at risk: {{at_risk_orders}}
+
+**Production impact of performing the PM:**
+- Lost production during the PM window: {{lost_production}} (e.g., "0 — Saturday is non-scheduled overtime; if OT was planned, 8 hours of production displaced")
+- Recovery plan: {{recovery_plan}} (e.g., "displaced OT production moved to Friday evening shift extension")
+
+**Coordination requirements:**
+- Maintenance personnel: {{maintenance_personnel}} (e.g., "1 millwright + 1 electrician, 10 hours each")
+- Parts/materials: {{parts_needed}} (e.g., "hydraulic seal kit #HS-602-A, confirm available in stores")
+- Production support: {{production_support}} (e.g., "Operator needed for first 2 hours to assist with die removal and last 1 hour for test run")
+
+---
+
+**Tone guidance:** Collaborative, not adversarial. Scheduling and maintenance are allies, not opponents. Provide the business case for the timing (so maintenance understands why this window matters) and the risk assessment for deferral (so maintenance can prioritise appropriately). Include all logistics so maintenance can plan their work order without back-and-forth.
+
+---
+
+## 7. Quality Hold Notification
+
+**Audience:** Quality manager, production manager, affected work centre supervisors, planning
+**Trigger:** In-process quality issue requiring quarantine of WIP
+**Delivery:** Immediate email + verbal to quality and production managers
+
+---
+
+**Subject:** 🔴 QUALITY HOLD — {{product}} — Batch {{batch_id}} — {{qty_affected}} units
+
+**Issued by:** {{scheduler_name}} in coordination with {{quality_lead}}
+**Date/Time:** {{date}} {{time}}
+
+**Defect summary:** {{defect_description}}
+Example: "Dimensional defect on stamped chassis frames — hole pattern shifted 2mm from specification due to suspected die wear. Discovered at weld inspection station."
+
+**Scope of hold:**
+
+| Production Stage | Quantity Affected | Location | Status |
+|---|---|---|---|
+| Stamping (completed) | 80 units | Welding station queue | QUARANTINED |
+| Welding (completed) | 60 units | Paint queue staging | QUARANTINED |
+| Paint (completed) | 60 units | Final assembly staging | QUARANTINED |
+| **Total** | **200 units** | | |
+
+**Customer impact:**
+- Customer: {{customer}}
+- Order: {{customer_po}}, {{qty}} units due {{due_date}}
+- 60 painted frames were scheduled to feed final assembly (constraint) starting {{date}}.
+- Constraint will be short material for {{impact_duration}} unless rework or replacement is expedited.
+
+**Schedule impact:**
+- Final assembly (constraint) schedule revised: {{revised_schedule_summary}}
+- Alternate work pulled forward to keep constraint running: {{alternate_work}}
+- Estimated delivery impact: {{delivery_impact}}
+
+**Disposition pending from Quality:**
+- Rework feasibility assessment requested by {{rework_assessment_deadline}}
+- If reworkable: estimated rework time = {{rework_time}} per unit
+- If not reworkable: replacement production order required — estimated lead time {{replacement_lead_time}}
+
+**Immediate actions taken:**
+1. All affected WIP physically segregated and tagged
+2. Die #{{die_number}} removed from service for inspection
+3. Production schedule revised — constraint fed from alternate work orders
+4. Customer notification drafted (pending quality disposition)
+
+---
+
+## 8. Capacity Constraint Escalation
+
+**Audience:** Plant manager, planning manager, production manager
+**Trigger:** MRP-generated load exceeds finite capacity by >15% for the upcoming week
+**Delivery:** Email with supporting data, presented at weekly S&OP or production meeting
+
+---
+
+**Subject:** Capacity Overload Alert — {{constraint_wc}} — Week {{week_number}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Summary:**
+MRP-generated load for {{constraint_wc}} in Week {{week_number}} exceeds available capacity by {{overload_pct}}%. Without intervention, {{overload_hours}} hours of work cannot be scheduled, affecting {{affected_orders}} customer orders.
+
+**Capacity analysis:**
+
+| Item | Hours |
+|---|---|
+| Available capacity ({{shifts}} shifts × {{hours_per_shift}} hrs, less {{pm_hours}} hrs planned maintenance) | {{available_hours}} |
+| MRP-required load | {{required_hours}} |
+| Overload | {{overload_hours}} ({{overload_pct}}%) |
+
+**Options for resolution:**
+
+| Option | Capacity Recovered | Cost | Risk | Recommendation |
+|---|---|---|---|---|
+| Saturday overtime (1 shift) | {{ot_hours}} hrs | ${{ot_cost}} | Low — voluntary OT available | ✅ Recommended |
+| Defer {{defer_count}} lower-priority orders to Week {{week_number + 1}} | {{defer_hours}} hrs | $0 | Medium — delivery impact on deferred orders | Acceptable if customers agree |
+| Subcontract {{subcontract_ops}} | {{subcontract_hours}} hrs | ${{subcontract_cost}} | Medium — quality and lead time | Last resort |
+| Reduce constraint changeovers (campaign scheduling) | {{co_hours}} hrs | $0 | Low — requires schedule restructuring | ✅ Recommended in combination |
+
+**Recommended plan:** Combine overtime ({{ot_hours}} hrs) + changeover reduction ({{co_hours}} hrs) to close the gap. Total gap closed: {{total_recovered}} hrs. Remaining gap: {{remaining_gap}} hrs — address by deferring {{defer_count}} Tier-3 orders with customer agreement.
+
+**Decision needed by:** {{decision_deadline}} (to allow operator notification and material staging)
+
+---
+
+## 9. New Product Trial Run Request
+
+**Audience:** Production manager, engineering, quality, scheduling
+**Trigger:** NPI (new product introduction) requiring constraint time for trial runs
+**Delivery:** Email with formal request; presented at production planning meeting
+
+---
+
+**Subject:** NPI Trial Run Request — {{npi_product}} — {{requested_dates}}
+
+**From:** {{scheduler_name}} in coordination with {{engineering_lead}}
+
+**Product:** {{npi_product}} (e.g., "EV Battery Enclosure — Part #BE-4400")
+**Customer:** {{customer}}
+**Qualification deadline:** {{qualification_deadline}}
+
+**Trial run requirements:**
+
+| Trial # | Date | Constraint Time (nominal) | Buffered Time (planned) | Changeover | Total Window |
+|---|---|---|---|---|---|
+| 1 | {{trial_1_date}} | 8 hrs | 14 hrs | 4 hrs | 18 hrs |
+| 2 | {{trial_2_date}} | 8 hrs | 12 hrs | 4 hrs | 16 hrs |
+| 3 | {{trial_3_date}} | 8 hrs | 10 hrs | 2 hrs | 12 hrs |
+
+**Capacity impact:**
+- Current constraint utilisation: {{current_util}}%
+- With NPI trials: {{projected_util}}%
+- Buffer reduction: constraint buffer shrinks from {{current_buffer}} hrs to {{projected_buffer}} hrs per week
+
+**Proposed scheduling approach:**
+- Schedule trials on Friday PM / Saturday AM to contain overrun risk
+- {{buffer_hours}} hrs/week reserved as "trial buffer" — converts to regular production if trial is cancelled or completes early
+- Existing customer commitments are not moved to accommodate trials
+
+**Risk mitigation:**
+- Most experienced setup technician assigned to all trials
+- First-article inspection protocol defined with quality
+- Trial time estimates will be updated after each run for the next trial
+
+**Approval required from:** Production Manager (capacity impact) + Quality (trial protocol) + Engineering (trial plan)
+
+---
+
+## 10. Cross-Functional Priority Alignment
+
+**Audience:** Sales, planning, production, quality, finance
+**Trigger:** Competing priorities require alignment (quarterly or when significant conflicts arise)
+**Delivery:** Presented at S&OP meeting with supporting data
+
+---
+
+**Subject:** Priority Alignment Request — Week {{week_number}} / Month {{month}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+
+**Issue:**
+The current production plan contains conflicting priorities that cannot be resolved within available capacity. Scheduling has identified {{conflict_count}} conflicts requiring cross-functional alignment.
+
+**Conflict summary:**
+
+| # | Conflict | Departments Involved | Scheduler's Assessment |
+|---|---|---|---|
+| 1 | Customer A rush order vs. Customer B committed delivery — both need CNC constraint, 16-hour gap | Sales + Production | Need commercial decision: which customer takes priority? |
+| 2 | NPI trial run vs. production schedule — trial requires 14 hrs of constraint time in a week loaded at 94% | Engineering + Production | Recommend scheduling trial on Saturday to avoid displacement |
+| 3 | Maintenance PM window vs. peak production week — PM deferred twice already | Maintenance + Production | Recommend executing PM this week; deferral risk exceeds production value of the PM window |
+
+**For each conflict, scheduling needs:**
+1. A single, clear priority decision
+2. Written confirmation (email or meeting minutes) that the decision is endorsed by all affected departments
+3. Decision by {{decision_deadline}} so the schedule can be locked for the week
+
+**Scheduling will execute whatever priority is agreed. We are not requesting a specific outcome — we are requesting clarity so the schedule can be built without ambiguity.**
+
+---
+
+**Tone guidance:** Neutral facilitator, not advocate. The scheduler's role in priority alignment is to surface conflicts, quantify tradeoffs, and execute decisions — not to make commercial or strategic calls. Make it clear that you need a decision, not a discussion. Provide the data that enables the decision.
diff --git a/skills/production-scheduling/references/decision-frameworks.md b/skills/production-scheduling/references/decision-frameworks.md
new file mode 100644
index 00000000..7be6e5f2
--- /dev/null
+++ b/skills/production-scheduling/references/decision-frameworks.md
@@ -0,0 +1,867 @@
+# Decision Frameworks — Production Scheduling
+
+This reference provides the detailed decision logic, scheduling algorithms, optimisation
+methodologies, and capacity planning techniques for production scheduling in discrete
+and batch manufacturing. It is loaded on demand when the agent needs to make or recommend
+nuanced scheduling decisions.
+
+All thresholds, formulas, and time assumptions reflect discrete and batch manufacturing
+operations running 3–8 production lines with 50–300 direct-labour headcount per shift.
+
+---
+
+## 1. Job Scheduling Algorithms
+
+### 1.1 Dispatching Rules — When to Use Each
+
+Dispatching rules are heuristics applied at a work centre when multiple jobs compete for
+the same resource. No single rule dominates in all situations. The choice depends on the
+plant's primary performance objective.
+
+| Rule | Definition | Best For | Weakness |
+|---|---|---|---|
+| **SPT (Shortest Processing Time)** | Process the job with the shortest operation time first | Minimising average flow time, reducing WIP, maximising throughput when setup times are negligible | Starves long jobs — a job with 8-hour run time waits behind twenty 20-minute jobs. Creates due date violations on long-cycle products. |
+| **EDD (Earliest Due Date)** | Process the job with the earliest due date first | Minimising maximum lateness across all jobs, meeting delivery commitments | Ignores processing time — a job due tomorrow with an 8-hour run time gets priority over a job due in 2 hours with a 5-minute run. Can increase WIP if many jobs have distant due dates. |
+| **Critical Ratio (CR)** | CR = (Due Date − Now) / Remaining Processing Time. Schedule lowest CR first. | Balancing due date urgency with remaining work. CR < 1.0 means the job is behind schedule. | Breaks down when due dates are unrealistic (all CRs < 0.5). Requires accurate remaining processing time estimates. |
+| **Weighted Shortest Job First (WSJF)** | Priority = (Cost of Delay × Job Weight) / Processing Time. Schedule highest priority first. | Environments where jobs have different economic value. Maximises throughput-weighted value. | Requires reliable cost-of-delay estimates, which are often subjective. Can starve low-value long jobs indefinitely. |
+| **Slack Time (ST)** | Slack = Due Date − Now − Remaining Processing Time. Schedule lowest slack first. | Similar to CR but uses absolute slack rather than ratio. Better when processing times are similar. | Same as CR — degrades with unrealistic due dates. Does not account for queue time at downstream work centres. |
+| **FIFO (First In, First Out)** | Process jobs in arrival order at the work centre | Ensuring fairness, simple to communicate, works in stable environments with predictable flow | No optimisation — ignores due dates, processing times, and economic value. Use only when all jobs are equal priority and flow is balanced. |
+
+#### Algorithm Selection Decision Tree
+
+1. **Is schedule adherence the primary KPI and are there contractual delivery penalties?**
+ → Use EDD as the primary rule. Insert CR checks for jobs where CR < 0.8 — these need
+ immediate attention regardless of EDD rank.
+
+2. **Is throughput/output the primary KPI with flexible delivery windows?**
+ → Use SPT to minimise average flow time. Monitor maximum lateness; if it exceeds
+ the acceptable threshold, switch to a hybrid SPT-EDD (SPT within a due date window).
+
+3. **Do jobs have significantly different economic values (margin, penalty, customer tier)?**
+ → Use WSJF. Weight = customer tier multiplier × margin contribution. This is the
+ appropriate rule for job shops with heterogeneous order portfolios.
+
+4. **Are setup times sequence-dependent and significant (>15 minutes between families)?**
+ → No pure dispatching rule handles this. Use a setup-aware scheduling heuristic
+ (Section 2) that groups jobs by setup family and optimises within groups using EDD.
+
+5. **Is the environment stable with balanced flow and predictable demand?**
+ → FIFO is acceptable and preferred for its simplicity and shop floor trust.
+
+### 1.2 Multi-Rule Hybrid Approaches
+
+In practice, most schedulers use a hybrid approach layered as follows:
+
+**Layer 1 — Hard Constraints (filter)**
+Remove any job from the queue that lacks material, tooling, or a qualified operator.
+These jobs are not schedulable regardless of priority.
+
+**Layer 2 — Urgency Override (force-rank)**
+Jobs with CR < 0.8 or that are already past-due are force-ranked to the top,
+ordered by customer penalty exposure descending.
+
+**Layer 3 — Primary Dispatching Rule (sort remaining)**
+Apply the selected dispatching rule (EDD, SPT, WSJF, etc.) to remaining jobs.
+
+**Layer 4 — Setup Optimisation (local reorder)**
+Within the primary sequence, perform adjacent-swap improvements to reduce
+total setup time, subject to the constraint that no swap causes a due date
+violation for either swapped job.
+
+**Layer 5 — Labour Levelling (validate)**
+Check that the resulting sequence does not create labour peaks that exceed
+available headcount for any hour of the shift. If it does, defer the lowest-
+priority job creating the peak to the next available slot.
+
+### 1.3 Critical Ratio in Detail
+
+Critical Ratio is the most versatile single dispatching rule for mixed environments.
+
+**Formula:**
+```
+CR = (Due Date − Current Date) / Remaining Total Processing Time
+```
+
+Where Remaining Total Processing Time includes:
+- Setup time for the current operation
+- Run time for the current operation
+- Queue time estimates for remaining operations (use historical average queue times)
+- Setup + run times for all remaining operations in the routing
+
+**Interpretation:**
+| CR Value | Meaning | Action |
+|---|---|---|
+| CR > 2.0 | Comfortable lead — job is well ahead of schedule | Lowest priority. May be deferred if capacity is needed for tighter jobs. |
+| 1.0 < CR < 2.0 | On track but limited slack | Schedule normally per dispatching rule |
+| CR = 1.0 | Exactly on schedule — no slack remaining | Monitor closely. Any disruption will cause lateness. |
+| 0.5 < CR < 1.0 | Behind schedule — will be late without intervention | Escalate. Consider overtime, alternate routing, or partial shipment. |
+| CR < 0.5 | Critically late — recovery is unlikely without significant intervention | Immediate escalation to production manager. Notify customer of revised date. |
+
+**Updating CR:** Recalculate CR at every operation completion and at the start of every
+shift. A job with CR = 1.5 at shift start that encounters a 4-hour unplanned delay mid-shift
+may drop to CR = 0.7 — the shift supervisor needs to know this in real time.
+
+### 1.4 Weighted Scheduling for Customer Tiers
+
+Manufacturing plants serving multiple customer tiers need a weighting system:
+
+| Customer Tier | Weight Multiplier | Rationale |
+|---|---|---|
+| Tier 1 (OEM, contractual penalties) | 3.0 | Late delivery triggers financial penalties, production line-down claims |
+| Tier 2 (Key accounts, framework agreements) | 2.0 | No contractual penalty but relationship value and reorder risk |
+| Tier 3 (Standard accounts) | 1.0 | Standard terms, no penalty |
+| Tier 4 (Spot orders, distributors) | 0.5 | Price-sensitive, low switching cost for them |
+
+**WSJF with Customer Tier:**
+```
+Priority Score = (Customer Tier Weight × Days Until Due / Remaining Processing Time)
+```
+Lower score = higher priority (more urgent). Negative scores = past-due.
+
+---
+
+## 2. Changeover Optimisation
+
+### 2.1 SMED Implementation Phases — Step by Step
+
+#### Phase 0 — Document the Current State (2–4 weeks)
+
+1. Video-record 3–5 changeovers on the target machine/line. Include the full duration
+ from last good piece of the outgoing product to first good piece of the incoming product.
+2. Create a changeover element sheet listing every task performed, the performer
+ (operator, setup tech, maintenance), the duration, and whether the machine was stopped.
+3. Categorize each element:
+ - **Internal (IED):** Must be performed with the machine stopped.
+ - **External (OED):** Can be performed while the machine is still running.
+ - **Waste:** Not necessary at all — holdover from old procedures, redundant checks, waiting.
+
+Typical finding: 30–50% of changeover time is either external work incorrectly performed
+during machine stoppage, or pure waste (searching for tools, waiting for approval,
+walking to the tool crib).
+
+#### Phase 1 — Separate Internal and External (2–4 weeks)
+
+1. Move all external elements to pre-changeover preparation:
+ - Pre-stage next-job tooling, dies, fixtures at the machine before the changeover begins.
+ - Pre-mix materials, pre-heat moulds, pre-program CNC settings.
+ - Pre-print work order documentation and quality checklists.
+2. Create a standardised changeover preparation checklist. The setup technician begins
+ executing it 30–60 minutes before the scheduled changeover time.
+3. Expected result: 25–40% reduction in machine-stopped time with no capital investment.
+
+#### Phase 2 — Convert Internal to External (4–8 weeks)
+
+1. Standardise die/fixture heights and mounting interfaces so that alignment and adjustment
+ happen before the die reaches the machine, not after.
+2. Implement intermediate jigs — set up the next tool in a staging fixture that mirrors
+ the machine's mounting interface. When the changeover begins, the pre-assembled unit
+ drops in with minimal adjustment.
+3. Pre-condition materials: if the incoming product requires a different temperature,
+ viscosity, or chemical mix, start conditioning in a parallel vessel.
+4. Expected result: additional 15–25% reduction in machine-stopped time. May require
+ modest investment in duplicate tooling or staging fixtures.
+
+#### Phase 3 — Streamline Remaining Internal Elements (4–12 weeks)
+
+1. Replace bolt-on fasteners with quick-release clamps, cam locks, or hydraulic clamping.
+ Every bolt removed saves 15–30 seconds.
+2. Eliminate adjustments through poka-yoke: centre pins, guide rails, fixed stops that
+ guarantee first-piece alignment without trial-and-error.
+3. Standardise utility connections: colour-coded quick-disconnect fittings for air, water,
+ hydraulic, and electrical. One-motion connect/disconnect.
+4. Parallel operations: two people working simultaneously on different sides of the machine
+ can halve the internal time. Requires choreographed procedures and safety protocols.
+5. Expected result: additional 10–20% reduction. Often requires capital investment in
+ quick-change tooling.
+
+#### Phase 4 — Eliminate Adjustments and Verify (ongoing)
+
+1. Implement first-piece verification jigs that confirm dimensions without full inspection.
+2. Use statistical process control (SPC) from the first piece — if the first piece is within
+ control limits, the changeover is validated without a trial run.
+3. Document the final standardised changeover procedure with photos, time targets per element,
+ and a sign-off sheet.
+4. Target: changeover time under 10 minutes (single-minute exchange of die) for the
+ machine-stopped portion.
+
+### 2.2 Sequence-Dependent Setup Matrices
+
+For operations where setup time varies by product-to-product transition, build a
+setup time matrix:
+
+**Example — Paint Line Setup Matrix (minutes):**
+
+| From \ To | White | Yellow | Orange | Red | Blue | Black |
+|---|---|---|---|---|---|---|
+| **White** | 0 | 8 | 10 | 15 | 20 | 25 |
+| **Yellow** | 15 | 0 | 8 | 12 | 20 | 25 |
+| **Orange** | 20 | 12 | 0 | 8 | 18 | 22 |
+| **Red** | 25 | 18 | 12 | 0 | 15 | 18 |
+| **Blue** | 20 | 22 | 20 | 18 | 0 | 10 |
+| **Black** | 30 | 28 | 25 | 22 | 12 | 0 |
+
+**Observations from this matrix:**
+- Light-to-dark transitions (White → Black: 25 min) are cheaper than dark-to-light (Black → White: 30 min).
+- Within colour families, transitions are minimal (Red → Orange: 12 min vs. Red → White: 25 min).
+- The optimal sequence for all six colours in a campaign would be: White → Yellow → Orange → Red → Blue → Black (total: 8+8+8+15+10 = 49 min) vs. random sequence averaging 17 min per transition (85 min total).
+
+**Using the matrix in scheduling:**
+1. Group jobs by colour family when possible (campaign scheduling within families).
+2. When inter-family transitions are required, optimise the transition sequence using the
+ nearest-neighbour heuristic, then improve with 2-opt swaps.
+3. If a specific colour is due earliest but the optimal setup sequence would delay it,
+ compute the cost of the suboptimal sequence (extra setup minutes × constraint hourly rate)
+ vs. the cost of late delivery. Choose the lower-cost option.
+
+### 2.3 Campaign Length Optimisation
+
+**Economic Production Quantity (EPQ):**
+```
+EPQ = √((2 × D × S) / (H × (1 − D/P)))
+```
+Where:
+- D = demand rate (units per period)
+- S = setup cost per changeover (labour + scrap + lost output opportunity cost)
+- H = holding cost per unit per period
+- P = production rate (units per period), P > D
+
+**Practical adjustments:**
+- Round EPQ up to the nearest full shift or full batch to avoid mid-shift changeovers.
+- If EPQ results in WIP that exceeds available staging space, constrain to physical capacity.
+- If EPQ results in a campaign longer than the longest customer lead time tolerance,
+ shorten it to maintain responsiveness even at higher changeover frequency.
+
+**Campaign vs. mixed-model decision:**
+
+| Factor | Favours Campaign | Favours Mixed-Model |
+|---|---|---|
+| Setup time | Long (>60 min) | Short (<15 min) |
+| Setup cost | High (>$500 per changeover) | Low (<$100 per changeover) |
+| Demand variability | Low (stable, forecastable) | High (volatile, order-driven) |
+| Customer lead time expectation | Tolerant (>2 weeks) | Tight (<3 days) |
+| WIP carrying cost | Low | High |
+| Product shelf life | Long or N/A | Short or regulated |
+| Number of product variants | Few (<10) | Many (>50) |
+
+---
+
+## 3. Theory of Constraints (TOC) Implementation
+
+### 3.1 Drum-Buffer-Rope — Step by Step
+
+**Step 1: Identify the Constraint**
+
+Run a capacity analysis for each work centre over the next planning horizon (1–4 weeks):
+
+```
+Utilisation = Σ(Setup Time + Run Time for all scheduled jobs) / Available Time
+```
+
+Available Time = shift hours × number of machines × (1 − planned maintenance %)
+
+The work centre with the highest utilisation ratio is the drum. If multiple work centres
+exceed 90% utilisation, the one with the least flexibility (fewest alternate routings,
+most specialised equipment) is the primary constraint.
+
+**Validation test:** If you could add 10% more capacity to the suspected constraint
+(one more machine, one more shift hour, or a 10% speed increase), would total plant
+output increase by approximately 10%? If yes, it is the true constraint. If output
+increases less (because a second work centre immediately becomes the bottleneck),
+you have an interactive constraint pair that requires different treatment.
+
+**Step 2: Exploit the Constraint**
+
+Maximise the output of the constraint with no capital investment:
+
+1. **Eliminate idle time:** The constraint should never wait for material, tooling,
+ operators, quality inspection, or information. Pre-stage everything.
+2. **Minimise changeovers on the constraint:** Move changeover to non-constraint
+ resources where the time cost is lower. If the constraint must change over,
+ ensure SMED discipline is applied rigorously.
+3. **Prevent quality defects reaching the constraint:** Inspect before the constraint
+ operation, not after. Every defective piece processed at the constraint is wasted
+ constraint capacity.
+4. **Run through breaks and shift changes:** Stagger operator lunches so the constraint
+ never stops for a break. Assign a relief operator.
+5. **Eliminate micro-stops:** Address every source of 1–5 minute stoppages (sensor trips,
+ material jams, tool wear alarms) that individually seem trivial but cumulatively steal
+ 2–5% of capacity.
+
+**Step 3: Subordinate Everything to the Constraint**
+
+1. **Upstream work centres:** Release work to upstream operations only at the rate the
+ constraint can consume it. This is the "rope." If the constraint processes 100 units/hour,
+ the upstream release rate should not exceed 100 units/hour regardless of upstream capacity.
+2. **Downstream work centres:** Must maintain enough sprint capacity to clear constraint
+ output without becoming a secondary bottleneck. If the constraint produces a batch every
+ 2 hours, downstream must be able to process that batch within 2 hours.
+3. **Scheduling non-constraints:** Do not optimise non-constraint schedules in isolation.
+ A non-constraint running at 100% utilisation when the constraint runs at 85% is producing
+ excess WIP that clogs the shop floor and slows the constraint's material flow.
+
+**Step 4: Establish the Buffer**
+
+The constraint buffer is a time buffer, not an inventory buffer:
+
+```
+Buffer Duration = Planned Lead Time from release to constraint × Buffer Factor
+```
+
+Typical buffer factors:
+- Stable, reliable upstream operations: 0.3 × lead time
+- Moderate reliability, some variability: 0.5 × lead time (most common starting point)
+- Unreliable upstream, frequent disruptions: 0.75 × lead time
+
+**Buffer sizing example:**
+If the upstream lead time from raw material release to the constraint work centre is
+8 hours, and upstream reliability is moderate, set the buffer at 4 hours. This means
+material should arrive at the constraint staging area at least 4 hours before the
+constraint is scheduled to process it.
+
+**Step 5: Monitor Buffer Penetration**
+
+| Zone | Buffer Consumed | Meaning | Action |
+|---|---|---|---|
+| Green | 0–33% | Constraint well-protected | Normal operations |
+| Yellow | 33–67% | Warning — material may arrive late | Expedite upstream work. Check for blockers. |
+| Red | 67–100% | Critical — constraint at risk of starvation | Immediate escalation. Overtime upstream. Re-sequence if needed. |
+| Black | >100% | Buffer exhausted — constraint is starving | Constraint is idle or will be idle. Emergency response. Every minute of delay from this point = lost plant output. |
+
+Track buffer penetration trends over 2–4 weeks. Persistent yellow indicates
+a systemic upstream issue (not random variation) that needs corrective action.
+
+**Step 6: Elevate the Constraint (only if Steps 1–5 are exhausted)**
+
+If after full exploitation and subordination the constraint still limits plant output
+below demand requirements:
+
+1. Add overtime or a weekend shift at the constraint only.
+2. Add a parallel machine or alternate routing capability.
+3. Outsource constraint-specific operations to a qualified subcontractor.
+4. Invest in faster constraint equipment (capital expenditure).
+
+Each elevation step is progressively more expensive. Never elevate before fully
+exploiting — most plants have 15–25% hidden capacity at the constraint that
+exploitation recovers at minimal cost.
+
+### 3.2 Buffer Management Advanced Patterns
+
+**Shipping Buffer:** Protects customer due dates from internal variability. Typically
+50% of the lead time from the constraint to shipping. If the constraint-to-shipping
+lead time is 2 days, the shipping buffer is 1 day — work should arrive at the
+shipping staging area 1 day before the committed ship date.
+
+**Assembly Buffer:** In plants with convergent product structures (multiple components
+feeding a common assembly), each feeder path to the assembly point needs its own
+buffer. The assembly can only proceed when ALL components are present, so the
+slowest feeder path determines the effective buffer.
+
+**Dynamic Buffer Adjustment:**
+- If buffer penetration is consistently in the green zone (>80% of jobs arrive with
+ buffer intact over a 4-week rolling window), reduce the buffer by 10–15%. Excess buffer
+ means excess WIP and longer lead times.
+- If buffer penetration frequently reaches red zone (>20% of jobs in a 4-week window),
+ increase the buffer by 15–20% while investigating the root cause upstream.
+- Never adjust buffers more frequently than every 2 weeks. Buffer management requires
+ stable data over multiple cycles.
+
+---
+
+## 4. Disruption Recovery Protocols
+
+### 4.1 Structured Disruption Response Framework
+
+When a disruption occurs, follow this decision tree:
+
+**Step 1: Classify the Disruption**
+
+| Type | Examples | Typical Duration | Impact Scope |
+|---|---|---|---|
+| **Equipment** | Breakdown, sensor failure, tooling wear | 30 min – 3 days | Single work centre |
+| **Material** | Shortage, wrong specification, quality reject of incoming | 2 hours – 2 weeks | Multiple work centres sharing the material |
+| **Labour** | Absenteeism, injury, certification gap | 1 shift – 1 week | Single work centre or line |
+| **Quality** | In-process defect, customer complaint triggering hold | 2 hours – 1 week | Entire batch/lot, plus downstream consumers |
+| **External** | Supplier failure, power outage, weather, regulatory stop | 4 hours – indefinite | Potentially plant-wide |
+
+**Step 2: Assess Constraint Impact**
+
+| Disruption Location | Constraint Impact | Response Priority |
+|---|---|---|
+| At the constraint | Direct — every minute = lost throughput | Maximum priority. All resources mobilised. |
+| Upstream of constraint, buffer is green | Indirect — buffer absorbs the delay | Monitor buffer penetration. No immediate schedule change. |
+| Upstream of constraint, buffer is yellow/red | Indirect but imminent — constraint will starve | Expedite. Overtime upstream. Re-sequence to feed constraint from alternate sources. |
+| Downstream of constraint | No throughput impact unless WIP backs up to constraint | Monitor. Clear downstream blockage before constraint output starts queuing. |
+| Parallel path (no constraint interaction) | No throughput impact, but delivery impact on affected orders | Re-sequence affected orders. Notify customers. |
+
+**Step 3: Execute Recovery**
+
+1. **Immediate (0–30 minutes):** Assess duration and impact. Notify affected parties. Freeze in-process work.
+2. **Short-term (30 min – 4 hours):** Re-sequence remaining work. Activate alternate routings. Assign backup operators. Request emergency maintenance.
+3. **Medium-term (4–24 hours):** Negotiate overtime or shift extensions. Contact subcontractors. Update customer ETAs. Recalculate the full planning horizon.
+4. **Long-term (>24 hours):** Capacity rebalancing. Possible order reallocation to alternate sites. Customer negotiations on delivery schedules. Insurance/force majeure documentation if applicable.
+
+### 4.2 Material Shortage Response
+
+1. **Confirm the shortage:** Verify physical inventory vs. system count. Phantom inventory
+ is common — conduct a physical count before declaring a shortage.
+2. **Identify substitutes:** Check BOM alternates, engineering-approved substitutions,
+ and customer-approved equivalent materials. In regulated industries (aerospace, pharma),
+ only pre-approved substitutes are permissible.
+3. **Partial build strategy:** Can you complete operations up to the point where the short
+ material is consumed, then hold semi-finished WIP for completion when material arrives?
+ This keeps upstream work centres productive and preserves lead time on the non-missing
+ portions of the routing.
+4. **Re-sequence:** Pull forward all work orders that do not consume the short material.
+ This keeps the plant productive even during the shortage.
+5. **Expedite procurement:** Emergency purchase order at premium freight. Quantify: is the
+ cost of expedited material + freight less than the cost of lost constraint time × hours
+ of delay? If yes, expedite without hesitation.
+6. **Customer communication:** If the shortage will impact customer deliveries, notify within
+ 4 hours of confirmation. Provide a revised delivery date and a recovery plan.
+
+### 4.3 Quality Hold Management
+
+When an in-process quality issue is discovered:
+
+1. **Contain immediately:** Quarantine all affected WIP — the batch in process, any
+ completed units from the same batch, and any downstream assemblies that consumed
+ units from the batch.
+2. **Assess scope:** How many units are affected? Which customer orders consume these units?
+ What is the rework cost vs. scrap cost vs. customer rejection cost?
+3. **Reschedule:** Remove the held inventory from the active schedule. Recalculate all
+ downstream operations that depended on this inventory.
+4. **Decision tree for held material:**
+ - **Rework possible and economical:** Schedule rework operations. Add rework time to the
+ routing and re-sequence downstream.
+ - **Rework possible but not economical (rework cost > material + labour cost of remaking):**
+ Scrap the held batch and schedule a replacement production order from scratch.
+ - **Cannot rework, cannot scrap (regulatory hold pending investigation):** Exclude from
+ schedule indefinitely. Plan as though the inventory does not exist.
+5. **Root cause:** While the schedule adjusts, quality engineering should be isolating the
+ root cause. The scheduler needs to know: is this a one-time event, or will subsequent
+ batches also be affected? If systemic, reduce yield assumptions for the affected operation
+ in the scheduling parameters until the root cause is resolved.
+
+---
+
+## 5. Capacity Planning vs. Finite Scheduling
+
+### 5.1 Rough-Cut Capacity Planning (RCCP)
+
+RCCP is a medium-term planning tool (4–16 weeks out) that validates whether the MPS
+is feasible at a high level before detailed scheduling.
+
+**Process:**
+1. Take the MPS (production plan by product family by week).
+2. Multiply by the routing hours per unit at each key work centre (typically only the
+ constraint and 1–2 near-constraints).
+3. Compare total required hours against available hours per week at each work centre.
+4. If required hours exceed available hours, flag the overloaded weeks for action:
+ demand shaping (move orders to adjacent weeks), overtime, subcontracting, or MPS revision.
+
+**RCCP Load Profile Example:**
+
+| Week | Constraint Capacity (hrs) | Required Load (hrs) | Utilisation | Status |
+|---|---|---|---|---|
+| W23 | 120 | 105 | 87.5% | OK |
+| W24 | 120 | 118 | 98.3% | Warning — near capacity |
+| W25 | 120 | 142 | 118.3% | Overloaded — action needed |
+| W26 | 120 | 96 | 80.0% | OK — could absorb W25 overflow |
+| W27 | 80 (planned maintenance window) | 75 | 93.8% | Tight — maintenance may need rescheduling |
+
+**Actions for W25 overload:**
+- Can 22 hours of load shift to W24 or W26 without missing customer dates? Check due dates.
+- If not shiftable: overtime (22 hrs ÷ 8 hrs/shift = 3 extra shifts, or 3 Saturday shifts).
+- If overtime not available: which orders have the most flexible delivery dates? Negotiate.
+- Last resort: subcontract 22 hours of work. Assess quality and lead time implications.
+
+### 5.2 Finite Capacity Scheduling (FCS) Detail
+
+FCS goes beyond RCCP by scheduling individual operations on specific resources at
+specific times, respecting:
+
+1. **Resource capacity:** Number of machines × hours per shift × shifts per day, minus planned maintenance windows.
+2. **Sequence-dependent setups:** Setup time varies based on the preceding job (see setup matrix in Section 2.2).
+3. **Material availability:** An operation cannot start until all BOM components are available at the work centre.
+4. **Tooling constraints:** A job requiring tooling set ABC cannot run simultaneously with another job requiring the same tooling.
+5. **Labour constraints:** A job requiring a certified operator cannot be scheduled when no certified operator is on shift.
+6. **Operation dependencies:** Operation 20 on a work order cannot start until Operation 10 is complete (routing precedence).
+7. **Transfer batches:** Overlap operations can start before the full batch from the preceding operation is complete, if the transfer batch size is defined.
+
+**FCS Scheduling Algorithm (simplified):**
+1. Sort all operations by priority (using the hybrid dispatching approach from Section 1.2).
+2. For the highest-priority unscheduled operation:
+ a. Find the earliest feasible time slot on the required resource, considering capacity,
+ material availability, tooling, labour, and predecessor completion.
+ b. Schedule the operation in that slot.
+ c. Update resource availability.
+3. Repeat for the next-highest-priority operation.
+4. After all operations are scheduled, run a post-optimisation pass looking for setup
+ reduction opportunities (adjacent-swap improvements) that don't violate due dates.
+
+### 5.3 Capacity Buffers and Protective Capacity
+
+Non-constraint work centres should maintain protective capacity — deliberately planned
+idle time that absorbs variability and prevents WIP accumulation.
+
+**Target utilisation by work centre type:**
+
+| Work Centre Type | Target Utilisation | Rationale |
+|---|---|---|
+| Constraint | 90–95% | Maximise output. Buffer everything else to protect it. |
+| Near-constraint (>80% loaded) | 85–90% | Close to becoming the constraint. Monitor for shifting bottleneck. |
+| Standard | 75–85% | Protective capacity absorbs upstream variability. |
+| Shared resource (forklift, crane, inspector) | 60–75% | High variability in demand for these resources. Over-scheduling creates system-wide delays. |
+| Rework/repair | 50–70% | Must have capacity available on demand. Cannot schedule at high utilisation. |
+
+**Warning signs of insufficient protective capacity:**
+- WIP queues growing at non-constraint work centres over time.
+- Non-constraint work centres occasionally becoming the bottleneck (shifting bottleneck).
+- Overtime at non-constraint work centres "to keep up."
+- Material handlers constantly expediting between non-constraint operations.
+
+---
+
+## 6. Multi-Constraint Scheduling
+
+### 6.1 Interactive Constraints
+
+When two or more work centres both exceed 85% utilisation and share a material flow path,
+they interact — improving throughput at one may starve or overload the other.
+
+**Identification:**
+Two work centres are interactive constraints if:
+1. They are on the same routing (material flows from one to the other), AND
+2. Both exceed 85% utilisation, AND
+3. Adding capacity at one causes the other's utilisation to exceed 95%.
+
+**Scheduling Strategy for Interactive Constraints:**
+
+1. **Schedule the primary constraint first** (the one with higher utilisation or the one
+ closer to the customer).
+2. **Subordinate the secondary constraint** to the primary's schedule — the secondary
+ constraint processes work in the order and at the pace dictated by the primary constraint's
+ output schedule.
+3. **Place a buffer between them** — even though both are constraints, the upstream one
+ should feed a time buffer to the downstream one to absorb variability.
+4. **Never optimise them independently.** A setup sequence that is optimal for the primary
+ constraint may create an impossible sequence for the secondary constraint if setups
+ are sequence-dependent at both. Solve jointly.
+
+### 6.2 Machine + Labour Dual Constraints
+
+Common in environments where machines are semi-automated and require an operator for
+setup, first-piece inspection, or monitoring but can run unattended for portions of the cycle.
+
+**Scheduling approach:**
+1. Schedule machine capacity first (finite capacity by machine).
+2. Overlay labour capacity (finite capacity by skill/certification).
+3. Identify conflicts: time slots where the machine schedule requires an operator but
+ no qualified operator is available.
+4. Resolve conflicts by:
+ - Shifting the job to a different machine that a different operator is qualified on.
+ - Shifting the operator from a lower-priority job to the conflicting job.
+ - Scheduling the operator's setup/inspection tasks at the start of the job and
+ allowing unattended running thereafter.
+
+### 6.3 Tooling as a Shared Constraint
+
+When specialised tooling (moulds, dies, fixtures, gauges) is shared across machines:
+
+1. **Treat tooling as a resource in the scheduling system** — the same way you schedule
+ machines and labour, schedule tooling.
+2. **Two jobs requiring the same mould cannot run simultaneously** on different machines.
+3. **Tooling changeover time** between machines adds to the total changeover. If Mould A
+ moves from Machine 1 to Machine 2, add the mould extraction time (Machine 1) + transport
+ time + mould installation time (Machine 2).
+4. **Optimise by grouping:** If three jobs all require Mould A, schedule them consecutively
+ on the same machine to avoid mould transfers.
+
+---
+
+## 7. Line Balancing for Mixed-Model Production
+
+### 7.1 Takt Time Calculation
+
+```
+Takt Time = Available Production Time per Shift / Customer Demand per Shift
+```
+
+**Example:** 480 minutes available per shift (8 hours × 60 min, minus 30 min breaks),
+customer demand is 240 units per shift.
+
+```
+Takt Time = 450 / 240 = 1.875 minutes per unit
+```
+
+Every workstation on the line must complete its tasks within 1.875 minutes per unit.
+If any station exceeds takt, it becomes the bottleneck and the line cannot meet demand.
+
+### 7.2 Workstation Balancing
+
+1. List all tasks with their duration and precedence relationships.
+2. Assign tasks to workstations such that no workstation exceeds takt time.
+3. Minimise the number of workstations (to minimise labour cost).
+4. Measure balance efficiency:
+
+```
+Balance Efficiency = Σ(Task Times) / (Number of Stations × Takt Time) × 100%
+```
+
+Target: >85%. Below 80% indicates significant idle time at some stations.
+
+### 7.3 Mixed-Model Sequencing (Heijunka)
+
+When a line produces multiple models with different task times:
+
+1. Calculate the weighted average cycle time across models.
+2. Determine the model mix ratio (e.g., Model A: 60%, Model B: 30%, Model C: 10%).
+3. Create a repeating pattern that levels the workload. For A:B:C = 6:3:1, a 10-unit
+ cycle would be: A-B-A-A-C-A-B-A-B-A.
+4. Validate that the bottleneck station can handle every model within takt. If Model C
+ takes 2.5 minutes at Station 3 while takt is 1.875 minutes, Model C must be spaced
+ sufficiently that Station 3 can catch up between occurrences.
+
+---
+
+## 8. Scheduling with Regulatory and Compliance Constraints
+
+### 8.1 Traceability-Driven Scheduling
+
+In regulated industries (pharmaceutical, food, aerospace), lot traceability requirements
+constrain scheduling flexibility:
+
+- **No lot mixing:** A work order for Lot A and a work order for Lot B cannot share
+ equipment simultaneously unless the equipment is fully cleaned between lots and
+ the cleaning is documented.
+- **Dedicated equipment campaigns:** When allergen or contamination controls require
+ dedicated equipment, the scheduling window for Product X on Line 1 is limited to
+ the dedicated campaign period. Scheduling outside this window requires re-validation.
+- **Operator qualification records:** The schedule must record which operator performed
+ each operation, and that operator must be certified at the time of execution.
+
+### 8.2 Clean-In-Place (CIP) Scheduling
+
+In food, beverage, and pharma, CIP cycles are mandatory between certain product transitions:
+
+| Transition Type | CIP Duration | Can Be Shortened? |
+|---|---|---|
+| Same product, next batch | 0–15 min (rinse only) | No — regulatory minimum |
+| Same product family | 30–60 min (standard CIP) | Only with validated short-CIP protocol |
+| Different product family | 60–120 min (full CIP) | No — regulatory requirement |
+| Allergen transition | 120–240 min (enhanced CIP + swab test) | No — requires analytical confirmation |
+
+Schedule CIP cycles as fixed blocks in the schedule, not as "setup time" that can be
+compressed. Under-estimating CIP time is a common scheduling error that creates cascading
+delays and regulatory risk.
+
+---
+
+## 9. Schedule Stability and Frozen Zones
+
+### 9.1 Frozen / Slushy / Liquid Planning Horizons
+
+| Horizon | Typical Duration | Flexibility | Changes Require |
+|---|---|---|---|
+| **Frozen** | 0–48 hours | No changes except force majeure | Production Manager + Scheduler approval |
+| **Slushy** | 48 hours – 1 week | Sequence changes allowed within day; no date changes | Scheduler approval |
+| **Liquid** | 1–4 weeks | Fully flexible for re-sequencing and rescheduling | Scheduler discretion |
+| **Tentative** | 4+ weeks | MRP-generated, not yet scheduled | Planning/MRP cycle |
+
+**Why frozen zones matter:** Every schedule change triggers a cascade — material handlers
+re-stage kits, operators re-read work orders, quality pre-inspections may need repeating,
+and changeover sequences recalculate. A plant that changes the schedule 10 times per shift
+has more disruption from schedule changes than from actual production problems.
+
+### 9.2 Schedule Change Cost Model
+
+Before approving a schedule change in the frozen or slushy zone, estimate the total cost:
+
+```
+Change Cost = Changeover Cost Delta + Material Restaging Cost + Labour Disruption Cost
+ + Quality Re-inspection Cost + Customer Impact Risk
+```
+
+If Change Cost > Benefit of Change, reject the change and hold the current schedule.
+Document the decision for the post-shift review.
+
+---
+
+## 10. Overtime and Shift Extension Decision Framework
+
+### 10.1 When to Authorise Overtime
+
+Overtime is a scheduling lever, not a default. Use the following decision tree:
+
+1. **Is the overtime required at the constraint?**
+ - Yes → Calculate: overtime cost vs. throughput value of additional constraint hours.
+ If 4 hours of constraint overtime at $1,200 total cost enables $20,000 of shipments,
+ approve immediately. The ROI threshold for constraint overtime is typically 3:1
+ (value:cost) or higher.
+ - No → The overtime at a non-constraint does not increase plant output. It only makes
+ sense if: (a) the non-constraint is starving the constraint and buffer penetration is
+ yellow/red, or (b) the non-constraint output is needed for a specific customer shipment
+ that cannot wait for the next regular shift.
+
+2. **Is the overtime voluntary or mandatory?**
+ - Check union contract or labour regulations. Many agreements require offering overtime
+ by seniority before mandating it. Mandatory overtime may require 24–48 hours' notice.
+ - Violating overtime assignment rules costs more in grievances and morale damage than
+ the production it generates. Always comply.
+
+3. **Fatigue and safety risk:**
+ - Operators who have already worked 10+ hours should not be assigned to the constraint
+ or to safety-critical operations. Error rates increase 25–40% in hours 11–12.
+ - If the overtime extends a 12-hour shift to 16 hours, assign the extended operator to
+ non-critical monitoring tasks and bring in a fresh operator for the constraint.
+
+### 10.2 Shift Pattern Comparison for Scheduling
+
+| Pattern | Hours/Week | Handovers/Week | Overtime Headroom | Best For |
+|---|---|---|---|---|
+| 3 × 8h (Mon–Fri) | 120 | 15 | Saturday shifts, daily OT | High-mix, moderate volume |
+| 3 × 8h (24/7) | 168 | 21 | Limited — already near capacity | Process industries, continuous flow |
+| 2 × 12h (Mon–Fri) | 120 | 10 | Weekend shifts | Capital-intensive with fewer handovers |
+| 2 × 12h (4 on / 4 off) | 168 | 14 | Built into rotation | High-volume, steady demand |
+| 4 × 10h (day shift only) | 40 per crew | 4 | Friday, weekend | Low-volume, single-shift operations |
+
+**Handover quality matters for scheduling:** Each handover is a potential point of
+information loss — the incoming shift may not know about a developing quality issue,
+a material shortage workaround, or a verbal schedule change. Fewer handovers (12-hour
+shifts) improve information continuity but increase fatigue risk. Balance based on
+operation complexity and error tolerance.
+
+---
+
+## 11. Subcontracting Decision Framework
+
+### 11.1 When to Subcontract
+
+Subcontracting is the scheduling lever of last resort for capacity shortfalls.
+
+**Decision criteria (all must be met):**
+1. Internal capacity at the required work centre is fully consumed through the delivery
+ deadline, including available overtime.
+2. The operation is not at the constraint (subcontracting from the constraint usually means
+ the constraint needs elevation, not a one-time fix).
+3. A qualified subcontractor exists who can meet the quality specification and delivery timeline.
+4. The subcontracting cost + transport cost + quality risk cost is less than the cost of
+ late delivery (penalties + customer relationship damage).
+5. In regulated industries: the subcontractor holds the necessary certifications
+ (ISO, IATF 16949, AS9100, FDA registration, etc.).
+
+### 11.2 Scheduling with Subcontracted Operations
+
+When an operation is subcontracted:
+1. Remove the operation from the internal schedule.
+2. Add a transport-out time (typically 0.5–2 days) and transport-in time.
+3. Add the subcontractor's quoted lead time (add 20% buffer for first-time subcontractors).
+4. The total external lead time replaces the internal operation time in the work order routing.
+5. Schedule downstream internal operations based on the expected return date, not the
+ internal processing time.
+6. Monitor subcontractor progress at 50% and 90% completion milestones. Do not wait until
+ the due date to discover a delay.
+
+---
+
+## 12. Scheduling Metrics and Continuous Improvement
+
+### 12.1 Key Scheduling Metrics
+
+| Metric | Calculation | Target | What It Reveals |
+|---|---|---|---|
+| **Schedule Adherence** | Jobs started within ±1 hour of plan / Total jobs | > 90% | How well the plant follows the schedule |
+| **Schedule Stability** | Jobs unchanged in frozen zone / Total frozen jobs | > 95% | How often the schedule is disrupted |
+| **On-Time Delivery (OTD)** | Orders shipped on or before commit date / Total orders | > 95% | Customer-facing performance |
+| **Make Span** | Time from first operation start to last operation end for a work order | Track vs. standard | Total production lead time |
+| **Changeover Ratio** | Total changeover time / Total available time at the resource | < 10% at constraint | Setup efficiency |
+| **Constraint Utilisation** | Actual producing time / Available time at constraint | > 85% | How well the constraint is exploited |
+| **WIP Turns** | Annual COGS / Average WIP Value | > 12 for discrete mfg | Scheduling efficiency and flow |
+| **Queue Time Ratio** | Queue time / Total lead time at each work centre | Track trend | Indicates hidden WIP and poor flow |
+
+### 12.2 Scheduling Post-Mortem Process
+
+After every significant schedule disruption (constraint downtime > 1 hour, customer delivery
+miss, or overtime exceeding budget by > 20%), conduct a structured post-mortem:
+
+1. **Timeline reconstruction:** What happened, when, and what was the cascade of effects?
+2. **Root cause:** Was the disruption caused by equipment, material, labour, quality,
+ scheduling logic, or external factors?
+3. **Response assessment:** Was the re-sequencing decision optimal? Could the recovery have
+ been faster? Were communications timely?
+4. **Parameter update:** Do scheduling parameters (setup times, run rates, yield factors,
+ buffer sizes) need adjustment based on what we learned?
+5. **Systemic fix:** What preventive action will reduce the probability or impact of this
+ type of disruption recurring?
+
+Document findings in a scheduling incident log. Review the log monthly with production
+management to identify patterns and prioritise improvement actions.
+
+### 12.3 Daily Scheduling Rhythm
+
+A disciplined daily cadence prevents reactive fire-fighting:
+
+| Time | Activity | Participants |
+|---|---|---|
+| Shift Start − 30 min | Pre-shift review: verify material staging, operator availability, equipment status | Scheduler, Shift Supervisor |
+| Shift Start | Publish shift schedule. Walk the floor to confirm understanding. | Scheduler |
+| Shift Start + 2 hrs | First checkpoint: plan adherence, buffer penetration, early disruption detection | Scheduler (desk review of MES data) |
+| Shift Midpoint | Mid-shift review: actual vs. plan, re-sequence if needed | Scheduler, Shift Supervisor |
+| Shift End − 1 hr | End-of-shift projection: what will be incomplete? Handover notes for next shift. | Scheduler, Shift Supervisor |
+| Shift End | Shift handover: in-person (preferred) or documented. Key issues, deviations, pending decisions. | Outgoing + Incoming Schedulers |
+| Daily (Morning) | Production meeting: yesterday's performance, today's priorities, issues requiring management decision | Scheduler, Production Mgr, Quality, Maintenance, Materials |
+
+This cadence creates at least 5 touchpoints per shift where the schedule is validated
+against reality and corrected before deviations compound.
+
+---
+
+## 13. ERP-to-Shop-Floor Data Flow
+
+### 13.1 SAP PP Integration Pattern
+
+```
+Sales Orders / Forecast
+ ↓
+Demand Management (MD61/MD62)
+ ↓
+MPS — Master Production Schedule (MD40/MD43)
+ ↓
+MRP Run (MD01/MD02) → Planned Orders
+ ↓
+Convert Planned → Production Orders (CO40/CO41)
+ ↓
+Sequence in APS/Scheduling Tool (external or PP/DS)
+ ↓
+Release to Shop Floor (CO02 — set status REL)
+ ↓
+MES Execution (operation confirmations — CO11N/CO15)
+ ↓
+Goods Receipt (MIGO) → Inventory Updated
+```
+
+**Common data quality issues:**
+- Routing times (setup + run) not updated after process improvements → schedule
+ systematically allocates too much or too little time.
+- BOM quantities not adjusted for yield → MRP under-orders material.
+- Work centre capacity not reflecting actual shift patterns → FCS generates
+ infeasible schedules.
+- Scrap reporting delayed → plan-vs-actual gap grows silently.
+
+### 13.2 Closing the Feedback Loop
+
+The single most important integration is the MES-to-schedule feedback:
+
+1. **Operation start:** MES records actual start time. Schedule compares to planned start.
+ Deviation > 1 hour triggers an alert.
+2. **Operation end:** MES records actual end time and quantities (good + scrap). Schedule
+ updates remaining operations with actual predecessor completion.
+3. **Downtime events:** MES captures downtime start, end, and reason code. Schedule
+ automatically adjusts downstream timing.
+4. **Quality events:** MES captures inspection results. Failed inspection triggers a
+ schedule hold on the affected batch.
+
+Without this feedback loop, the schedule diverges from reality within hours and becomes
+aspirational rather than operational. The shop floor stops consulting it, operators make
+their own sequencing decisions, and throughput at the constraint drops because ad-hoc
+sequencing ignores constraint protection logic.
diff --git a/skills/production-scheduling/references/edge-cases.md b/skills/production-scheduling/references/edge-cases.md
new file mode 100644
index 00000000..8818432a
--- /dev/null
+++ b/skills/production-scheduling/references/edge-cases.md
@@ -0,0 +1,611 @@
+# Production Scheduling — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous production scheduling situations that don't resolve through standard sequencing and dispatching workflows.
+
+These edge cases represent the scenarios that separate experienced production schedulers from everyone else. Each one involves competing constraints, imperfect data, time pressure, and real operational exposure. They are structured to guide decision-making when standard scheduling rules break down.
+
+---
+
+## How to Use This File
+
+When a scheduling situation doesn't fit a clean pattern — when constraints shift mid-shift, when multiple disruptions compound, or when commercial pressure conflicts with physical reality — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document every decision and override so the shift handover and post-mortem have a clear trail.
+
+---
+
+### Edge Case 1: Shifting Bottleneck Mid-Shift
+
+**Situation:**
+A contract manufacturer produces aluminium housings for two automotive OEMs. The morning schedule loads the CNC machining centre at 92% utilisation and the powder coating line at 78% — machining is the constraint. At 10:00 AM, the product mix shifts as a batch of large, complex housings clears CNC (short cycle time per unit for the next batch of small housings) and hits the powder coat line, which now requires extended cure cycles. By 11:00 AM, CNC utilisation has dropped to 70% and powder coat is at 95%. The schedule optimised around CNC as the constraint is now starving CNC (which has excess capacity) while powder coat backs up with WIP stacking on the staging rack.
+
+**Why It's Tricky:**
+Most scheduling systems set the constraint at the planning stage and hold it fixed for the shift. When the constraint shifts intra-shift, the buffer management, subordination logic, and priority sequencing all become wrong simultaneously. The CNC buffer is unnecessarily large (tying up WIP), while the powder coat buffer doesn't exist and the line is starving.
+
+**Common Mistake:**
+Ignoring the shift because "machining is the constraint this week" based on the weekly capacity plan. Or overreacting by completely re-sequencing the shift, creating chaos on the shop floor.
+
+**Expert Approach:**
+1. Recognise the shift by monitoring real-time WIP levels. WIP accumulating before powder coat while CNC's outfeed staging area is empty is the leading indicator.
+2. Verify the duration: is this a temporary product-mix effect (2–3 hours) or will it persist for the rest of the shift? Check the remaining work order sequence.
+3. If temporary (< 3 hours): do not re-sequence the entire shift. Instead, tactically re-prioritise the 2–3 jobs in the powder coat queue to minimise setup changes (colour sequencing), and slow CNC's release rate to avoid over-building the WIP queue.
+4. If persistent (rest of the shift): formally re-designate powder coat as the shift's constraint. Apply constraint protection: pre-stage next jobs at the powder coat line, stagger CNC completions to match powder coat's processing rate, and assign the most experienced operator to the powder coat line.
+5. At shift handover, document the constraint shift and the product mix that caused it so the incoming scheduler plans accordingly.
+
+**Documentation Required:**
+- Time of constraint shift detection
+- Product mix analysis showing utilisation crossover
+- Tactical adjustments made (CNC pacing, powder coat priority changes)
+- Impact on customer orders (any due date revisions)
+- Shift handover note for the incoming scheduler
+
+**Resolution Timeline:**
+- 0–15 min: Detect the WIP imbalance
+- 15–30 min: Verify duration and decide on tactical vs. full re-sequence
+- 30–60 min: Implement adjustments and confirm stabilisation
+- Shift end: Document and hand over
+
+---
+
+### Edge Case 2: Certified Operator Absent for Regulated Process
+
+**Situation:**
+A pharmaceutical contract manufacturer operates a tablet coating line that requires an FDA-qualified operator (documented training, competency assessment, and supervisor sign-off per 21 CFR Part 211). The night shift has two qualified coating operators: Maria (12 years experience) and Jamal (3 years, recently qualified). At 10:30 PM, Jamal — tonight's scheduled coating operator — calls in sick. Maria works day shift and is off-site. The coating line has 6 hours of work scheduled tonight that feeds a customer shipment due in 3 days. No other night-shift operator has the FDA qualification for this specific process step.
+
+**Why It's Tricky:**
+This is a hard regulatory constraint, not a soft preference. Running the coating line with an unqualified operator is a GMP violation that can trigger an FDA Form 483 observation, product recall, or facility warning letter. The cost of non-compliance vastly exceeds any production delay. But the customer shipment is for a hospital network, and delays affect patient medication availability.
+
+**Common Mistake:**
+Running the line with an "almost qualified" operator who has completed training but hasn't finished the competency assessment documentation. This is a regulatory violation regardless of the operator's actual skill level.
+
+**Expert Approach:**
+1. Confirm that no other night-shift employee holds the qualification. Check the cross-training matrix — not just coating operators, but anyone on night shift who may have been cross-trained on this line (maintenance technicians sometimes hold process qualifications).
+2. Contact Maria. Can she work a split shift (come in at midnight, work 6 hours, leave at 6 AM)? Check the union contract and fatigue rules — most agreements require an 8-hour rest between shifts. If Maria left day shift at 3:30 PM, she is eligible to return at 11:30 PM under an 8-hour rest rule.
+3. If Maria is available and willing: authorise overtime, document the reason (single-point-of-failure staffing event), and adjust the coating schedule to start when she arrives.
+4. If Maria is unavailable: stop the coating line. Do not attempt a workaround. Re-sequence the night shift to run non-regulated operations (packaging, labelling, material preparation for the next coating run). Calculate the impact on the customer shipment: can 6 hours of coating work be completed on the day shift (with overtime if needed) and still meet the 3-day deadline?
+5. Escalate to the production manager and quality assurance manager. If the customer deadline cannot be met, notify the customer immediately with a revised delivery date. For pharmaceutical customers, "we maintained GMP compliance" is a stronger position than "we cut corners to hit the date."
+6. Post-incident: submit a request to cross-train 2 additional night-shift operators on the coating process. Single-point-of-failure on a regulated process is a systemic risk.
+
+**Documentation Required:**
+- Cross-training matrix review (who holds the qualification, who does not)
+- Maria's contact record and response
+- Overtime authorisation (if applicable) with union compliance check
+- Re-sequenced night schedule showing non-regulated work
+- Customer notification (if shipment delayed)
+- CAPA (Corrective and Preventive Action) for cross-training gap
+
+**Resolution Timeline:**
+- 10:30 PM: Absence confirmed
+- 10:30–11:00 PM: Cross-training matrix review, Maria contacted
+- 11:00 PM: Decision made (Maria coming in, or coating line stopped)
+- 11:15 PM: Re-sequenced schedule published for night shift
+- Next business day: CAPA initiated for cross-training
+
+---
+
+### Edge Case 3: Competing Rush Orders from Tier-1 Customers
+
+**Situation:**
+A precision machining job shop receives two emergency orders on the same Monday morning:
+
+- **Customer A (major automotive OEM):** 500 transmission valve bodies needed by Thursday. Their assembly line is down waiting for these parts. Contractual penalty: $25,000/day of late delivery. Annual revenue from Customer A: $4.2M.
+- **Customer B (aerospace prime contractor):** 200 fuel system brackets needed by Friday. Their production schedule slips 1 week for every day of delay on these brackets. No contractual penalty, but Customer B is in a competitive evaluation and a slip here could cost the $8M annual contract renewal in Q3.
+
+Both orders require the same 5-axis CNC machining centre (the plant's constraint), and the combined processing time exceeds the available capacity by 16 hours.
+
+**Why It's Tricky:**
+This is not a scheduling problem — it's a commercial decision disguised as a scheduling problem. The scheduler can identify the tradeoff and quantify it, but the decision on which customer to prioritise requires management input on strategic relationships, risk tolerance, and commercial exposure.
+
+**Common Mistake:**
+The scheduler makes the commercial decision unilaterally, typically defaulting to the contractual penalty (Customer A) without presenting the strategic risk (Customer B). Or the scheduler tries to split the capacity equally, resulting in both orders being late.
+
+**Expert Approach:**
+1. Quantify both scenarios precisely:
+ - **Prioritise A:** Customer A ships Thursday (on time). Customer B ships the following Monday (3 days late). Customer B cost: potential $8M contract risk, unquantifiable but real.
+ - **Prioritise B:** Customer B ships Friday (on time). Customer A ships Saturday (2 days late). Customer A cost: $50,000 in contractual penalties + relationship damage.
+ - **Split capacity:** Customer A ships Friday (1 day late, $25K penalty). Customer B ships Monday (3 days late, contract risk).
+2. Identify capacity recovery options:
+ - Saturday overtime on the CNC (8 hours, cost ~$3,200). If authorised, both orders can be completed on time: A by Thursday, B by Saturday.
+ - Subcontract the simpler machining operations for Customer B to a qualified external shop, freeing 8 hours of CNC capacity for Customer A. Cost: $4,500 for subcontracting + expedited freight.
+3. Present the tradeoff matrix to the production manager and sales director with recommended option (overtime or subcontracting, not splitting capacity). Include the cost comparison.
+4. Once the decision is made, re-sequence the entire CNC schedule for the week. Lock the frozen zone on the decided sequence. Communicate to both customers.
+
+**Documentation Required:**
+- Capacity analysis showing the 16-hour shortfall
+- Tradeoff matrix with financial exposure for each scenario
+- Recommended recovery options with cost estimates
+- Management decision record (who decided, which option, rationale)
+- Customer communication log
+
+**Resolution Timeline:**
+- Monday AM: Both rush orders received
+- Monday AM + 2 hours: Capacity analysis and tradeoff matrix completed
+- Monday AM + 4 hours: Management decision
+- Monday PM: Re-sequenced schedule published, customers notified
+
+---
+
+### Edge Case 4: MRP Phantom Demand from BOM Error
+
+**Situation:**
+The scheduler notices that MRP has generated a planned production order for 3,000 units of a sub-component (Part #SC-4420, a machined bracket) with a due date in 2 weeks. This is unusual — this part typically runs in batches of 500 for the two product families that consume it. A check of the current sales orders and forecast shows demand for only 800 units over the next 6 weeks. The MRP-generated demand of 3,000 appears to be phantom.
+
+Investigation reveals that an engineer updated the BOM for a new product variant (not yet released) and accidentally set the quantity-per of SC-4420 to 12 instead of 1 on the master BOM. The MRP explosion multiplied forecasted demand for the new variant (250 units) by 12, generating 3,000 units of phantom demand. The BOM error has not yet been caught by engineering.
+
+**Why It's Tricky:**
+Scheduling systems trust MRP output. If the scheduler blindly converts the planned order to a production order and schedules it, the plant will produce 2,200 units of unwanted inventory, consuming 44 hours of machining capacity that was needed for real customer demand. But if the scheduler ignores MRP output without proper verification, they risk missing legitimate demand.
+
+**Common Mistake:**
+Scheduling the MRP-generated order without questioning it ("the system says we need it"), or deleting it without notifying engineering about the BOM error (the error persists and generates phantom demand again in the next MRP run).
+
+**Expert Approach:**
+1. **Verify the anomaly:** Compare the MRP-generated demand to the trailing 6-month demand history for SC-4420. A 3× spike with no corresponding sales order or forecast increase is a red flag.
+2. **Trace the demand:** Use MRP pegging (SAP: MD04/MD09, Oracle: pegging inquiry) to trace the planned order back to the parent demand that generated it. This reveals which parent product's BOM is driving the demand.
+3. **Identify the root cause:** The pegging trace points to the new product variant BOM. Compare the BOM quantity-per to the engineering drawing — the drawing shows 1 unit per assembly, the BOM shows 12.
+4. **Do not schedule the phantom demand.** Place a hold on the planned order with a note explaining the suspected BOM error.
+5. **Notify engineering immediately.** Provide the specific BOM line, the quantity discrepancy, and the MRP impact. Request urgent correction.
+6. **Schedule the real demand:** Create a production order for the actual 800-unit requirement and sequence it normally.
+7. **Verify the fix:** After engineering corrects the BOM, re-run MRP for SC-4420 and confirm the planned orders now align with expected demand.
+
+**Documentation Required:**
+- Anomaly detection: what triggered the investigation (volume spike, capacity conflict)
+- MRP pegging trace results
+- BOM error details (parent item, line item, incorrect vs. correct quantity)
+- Engineering notification with correction request
+- Production order for actual demand
+- Verification after BOM correction
+
+**Resolution Timeline:**
+- Day 1: Anomaly detected during schedule review
+- Day 1 + 2 hours: Pegging trace and root cause identified
+- Day 1 + 4 hours: Engineering notified, phantom order held
+- Day 2–3: Engineering corrects BOM, MRP re-run
+- Day 3: Verified — phantom demand eliminated
+
+---
+
+### Edge Case 5: Quality Hold on WIP Inventory Affecting Downstream
+
+**Situation:**
+A metal fabricator discovers a dimensional defect on a batch of 200 stamped chassis frames at the weld inspection station. The defect — a hole pattern shifted 2mm from specification due to a worn die — affects the entire batch produced since the last die change 3 shifts ago. Of the 200 affected frames: 80 are in welding (current operation), 60 have completed welding and are in paint queue, and 60 have completed paint and are in final assembly staging. Final assembly is the plant's constraint, and these 60 painted frames were scheduled to feed the constraint starting tomorrow morning. The customer (a commercial HVAC manufacturer) has a firm delivery commitment for 150 assembled units on Friday.
+
+**Why It's Tricky:**
+The quality hold cascades across three production stages. Some units may be reworkable (the hole pattern might be re-drilled), but rework adds operations to the routing and consumes capacity. The constraint (final assembly) will starve tomorrow if the 60 painted frames are quarantined. And the die that caused the defect needs to be replaced before more frames can be stamped, adding a maintenance operation to the schedule.
+
+**Common Mistake:**
+Quarantining only the 80 frames at welding (the point of detection) and allowing the 60 painted frames to proceed to assembly. If the defect makes assembly impossible or causes field failures, the cost of rework/recall after assembly is 5–10× the cost of catching it now.
+
+**Expert Approach:**
+1. **Full containment:** Quarantine all 200 frames across all three stages immediately. Tag, segregate, and document. No exceptions — even frames that "look fine" at paint stage may have the shifted hole pattern.
+2. **Assess reworkability:** Can the 2mm shift be corrected? Options:
+ - Re-drill the hole pattern at the correct location (if material allows, the shifted holes will remain as cosmetic defects — check if customer spec allows).
+ - Weld-fill the incorrect holes and re-drill (expensive, time-consuming, may not pass NDT for structural components).
+ - Scrap all 200 and restart from raw material (if re-drilling is not viable).
+3. **Schedule the constraint feed:** The constraint (final assembly) needs 60 frames tomorrow. If rework is feasible and fast enough:
+ - Expedite rework of the 60 painted frames first (they are furthest along).
+ - Schedule rework as an additional operation in the routing with its own time estimate.
+ - If rework takes 0.5 hours per frame and you assign 2 rework operators, 60 frames = 15 hours = 2 shifts.
+ - The constraint will be short frames for tomorrow's day shift. Can you pull forward other work at the constraint (different product) to fill the gap? If yes, do that and push the HVAC assembly to tomorrow's night shift or Wednesday.
+4. **Fix the die:** Replace or re-sharpen the stamping die before producing any new frames. Add a first-piece dimensional inspection requirement after the die change. If the die is a custom tool with a 2-week replacement lead time, have tooling assess whether the current die can be ground and requalified as a temporary measure.
+5. **Customer communication:** If Friday delivery is at risk, notify the customer by end of business today. Provide a revised ETA based on the rework timeline.
+
+**Documentation Required:**
+- Defect description, quantity affected, production stages
+- Containment actions and quarantine locations
+- Rework assessment (feasibility, time, cost)
+- Revised schedule showing constraint feed plan
+- Die replacement/repair plan
+- Customer notification (if delivery impacted)
+- CAPA for die wear monitoring (preventive inspection schedule)
+
+**Resolution Timeline:**
+- Hour 0: Defect detected at weld inspection
+- Hour 0–1: Full containment across all stages
+- Hour 1–3: Rework feasibility assessment
+- Hour 3–4: Revised schedule published with rework operations
+- Hour 4: Customer notified if delivery impacted
+- Day 2–3: Rework completed, constraint fed
+- Week 1: Die replaced or requalified
+
+---
+
+### Edge Case 6: Equipment Breakdown at the Constraint
+
+**Situation:**
+The main CNC horizontal boring mill — the plant's constraint for large machining operations — suffers a hydraulic pump failure at 9:15 AM on a Wednesday. Maintenance assessment: pump replacement requires 6–8 hours, but the replacement pump must be sourced from the OEM distributor 4 hours away. Realistic return-to-service: Thursday 6:00 AM (20+ hours of constraint downtime). Current work in the machine: a $38,000 defence contract part, 6 hours into an 8-hour operation — incomplete, cannot be removed without scrapping. 14 additional jobs are queued behind it, representing $220,000 in customer orders due within 2 weeks.
+
+**Why It's Tricky:**
+Every hour of constraint downtime directly reduces plant throughput. 20 hours at a constraint generating $800/hour in throughput = $16,000 in lost output. The defence part in the machine presents a dilemma: can it be completed when the machine restarts (will the part datum be preserved?), or is it scrap?
+
+**Common Mistake:**
+Waiting for the repair to complete before re-planning. By then, 20 hours of schedule disruption have cascaded through the plant with no mitigation.
+
+**Expert Approach:**
+1. **Immediate (0–15 min):**
+ - Confirm maintenance's repair estimate. Ask: is there a faster temporary fix (bypass, rental equipment)? Can the OEM ship the pump by overnight freight instead of driving?
+ - Determine if the in-machine part can resume after repair. Consult the machinist: are the datum offsets preserved? If the machine can restart the interrupted operation from the last completed tool path, the part is salvageable. If not, it may need to be re-fixtured and re-qualified, adding 2–3 hours but saving the $38,000 part.
+2. **Short-term (15 min – 2 hours):**
+ - Identify alternate routings: which of the 14 queued jobs can be processed on a smaller vertical CNC? The tolerances may allow some jobs to run on alternate equipment, even if cycle times are longer. Move those jobs immediately.
+ - Re-sequence remaining jobs by customer priority (EDD + customer tier weighting). When the constraint restarts Thursday AM, the first job in the queue must be the highest-priority item.
+ - Calculate customer impacts: which of the 14 jobs will miss due dates? Prepare a customer notification for each affected order.
+3. **Medium-term (2–20 hours, while machine is down):**
+ - Pre-stage everything for the queued jobs: tooling, raw material, fixtures, programs, operator assignments. When the machine restarts, the first job should begin within 15 minutes of the machine's green light.
+ - Evaluate whether Saturday overtime (8–16 hours) can recover the lost production. Cost of overtime vs. cost of late deliveries.
+ - Contact qualified external machining shops for the most at-risk orders. Can they process any of the 14 jobs faster than your recovery schedule?
+4. **Recovery (Thursday AM onward):**
+ - Restart with the salvaged in-machine part (if viable) or load the highest-priority queued job.
+ - Run the constraint through all breaks and shift changes (stagger operators).
+ - Monitor recovery pace hourly against the recovery schedule.
+
+**Documentation Required:**
+- Breakdown time, root cause, repair timeline
+- In-machine part assessment (salvageable Y/N, additional cost)
+- Alternate routing analysis for queued jobs
+- Customer impact list with revised ETAs
+- Overtime/subcontracting cost analysis
+- Recovery schedule with hourly milestones
+
+**Resolution Timeline:**
+- 9:15 AM: Breakdown
+- 9:15–9:30 AM: Maintenance assessment and pump sourcing
+- 9:30–11:00 AM: Alternate routing analysis, re-sequencing, customer notifications
+- 11:00 AM – Thursday 6:00 AM: Pre-staging, subcontracting decisions, recovery planning
+- Thursday 6:00 AM+: Machine restarts, recovery schedule executed
+- Friday: Recovery progress assessment — overtime decision for Saturday
+
+---
+
+### Edge Case 7: Supplier Delivers Wrong Material Mid-Run
+
+**Situation:**
+A structural steel fabricator is midway through a production run of 100 beam assemblies for a commercial construction project. Each assembly requires Grade 350 structural steel plate (AS/NZS 3678). At 2:00 PM, the quality inspector checking the second material delivery of the day discovers the mill certificates show Grade 250 instead of Grade 350. The first delivery (Grade 350, correct) fed the first 40 assemblies. The second delivery (Grade 250, wrong) has been kitted into the staging area for assemblies 41–70, and 12 plates from this delivery have already been cut and are at the welding station.
+
+**Why It's Tricky:**
+Grade 250 steel has lower yield strength than Grade 350 — assemblies made from it could be structurally inadequate and unsafe. The 12 cut plates cannot be used. But 28 plates from the wrong delivery are still uncut and could be returned. The production line is currently running and operators are about to start welding the incorrect material.
+
+**Common Mistake:**
+Continuing production and hoping the customer won't notice (this is a structural integrity and safety issue — non-negotiable). Or shutting down the entire line when only assemblies 41–70 are affected — assemblies 71–100 can use material from a different source if available.
+
+**Expert Approach:**
+1. **Stop welding immediately** on any piece using the Grade 250 material. Pull the 12 cut plates from the welding station and quarantine them with clear "HOLD — WRONG MATERIAL" tags.
+2. **Segregate the remaining 28 uncut plates** from the wrong delivery. These can be returned to the supplier or used for non-structural orders that specify Grade 250.
+3. **Continue production on assemblies 71–100** using material from existing Grade 350 stock (check if there is sufficient on-hand inventory from other purchase orders or stock). If Grade 350 stock is available for assemblies 71–100, the line does not need to stop entirely.
+4. **Assemblies 41–70 are now blocked.** Contact the supplier for emergency replacement of 30 Grade 350 plates. Demand same-day or next-day delivery at the supplier's cost (this is a supplier error). If the supplier cannot respond fast enough, source from an alternative supplier.
+5. **The 12 cut plates** in Grade 250 are scrap for this project. Calculate the scrap cost (material + cutting labour) and include it in the supplier claim.
+6. **Reschedule assemblies 41–70** to start after replacement material arrives. In the meantime, sequence assemblies 71–100 first (if material is available) to keep the welding line productive.
+7. **Notify the customer** if the construction project delivery timeline is affected. For structural steel, customers prefer a delay over incorrect material grade — this is a safety issue.
+
+**Documentation Required:**
+- Material non-conformance report with mill certificate evidence
+- Quarantine records for the 12 cut plates and 28 uncut plates
+- Supplier notification and replacement delivery commitment
+- Revised production schedule showing assemblies 71–100 pulled forward
+- Scrap cost calculation for the supplier claim
+- Customer notification (if delivery impacted)
+
+---
+
+### Edge Case 8: Overtime Ban During Peak Demand
+
+**Situation:**
+A consumer electronics assembly plant is entering its busiest 6-week period (back-to-school and early holiday orders). The production plan requires 132% of standard capacity at the constraint (SMT pick-and-place line) to meet all customer commitments. Normally, 32% of capacity comes from Saturday overtime shifts. However, the union just notified management that it is invoking the collective agreement clause limiting overtime to 5 hours per employee per week (down from the usual 15-hour soft cap) due to a dispute over shift differential rates. Negotiations are expected to take 3–5 weeks.
+
+**Why It's Tricky:**
+The plant was counting on Saturday overtime as the primary capacity lever. Without it, 32% of demand is unfillable. But the 5-hour limit still allows some daily overtime (1 hour/day Mon–Fri = 5 hours/week), which partially offsets. The scheduler must find 20–25% additional effective capacity from other sources while respecting the union constraint.
+
+**Common Mistake:**
+Pressuring operators to work "off the books" (violates the collective agreement and exposes the company to legal liability). Or accepting a 20–25% shortfall without exploring all alternatives.
+
+**Expert Approach:**
+1. **Quantify the gap precisely:** Standard capacity at constraint = 120 hours/week. Required = 158.4 hours. Overtime now available = 1 hour/day × 5 days × number of qualified operators. If 4 operators run the SMT line and each can do 5 hours/week OT, that's 20 hours/week of overtime capacity, bringing effective capacity to 140 hours. Remaining gap: 18.4 hours/week.
+2. **Exploit the constraint (no capital):**
+ - Reduce changeovers on SMT: consolidate product families, campaign-schedule similar board types together. Target: recover 4–6 hours/week from reduced changeover time.
+ - Run through all breaks and shift changes with staggered relief operators. Target: recover 2–3 hours/week.
+ - Reduce micro-stops through preventive maintenance during non-production hours. Target: recover 1–2 hours/week.
+3. **Temporary labour:** Can temporary agency operators run non-constraint operations, freeing experienced operators to double up at the constraint? The SMT line requires certification, but downstream operations (manual assembly, testing, packaging) may accept temporary labour.
+4. **Subcontract non-constraint work:** If downstream operations (conformal coating, testing) can be subcontracted, the freed-up internal capacity can be redirected to support constraint throughput (material handling, staging, quality inspection at the SMT line).
+5. **Customer prioritisation:** If the gap cannot be fully closed, rank customer orders by value and contractual penalty exposure. Allocate constraint capacity to the highest-priority orders first. Negotiate delivery extensions with lower-priority customers before the original due date — proactive notification preserves the relationship.
+6. **Demand shaping:** Work with sales to shift some orders from the peak 6-week window to the 2 weeks before or after, if customers have flexibility. Even moving 5% of demand out of peak reduces the capacity gap significantly.
+
+**Documentation Required:**
+- Capacity analysis showing the gap (hours/week) with and without overtime
+- Constraint exploitation plan with estimated recovery per initiative
+- Temporary labour and subcontracting options with cost and timeline
+- Customer prioritisation matrix
+- Demand shaping proposals to sales
+- Weekly progress tracking against the gap closure plan
+
+---
+
+### Edge Case 9: Customer Order Change After Production Started
+
+**Situation:**
+A custom industrial equipment manufacturer is 60% through a production order for Customer X: 20 hydraulic press frames, each with a 3-week machining cycle. 12 frames are complete through machining and in welding. 4 frames are in machining. 4 frames have not started (raw material cut but not machined). Customer X contacts sales to change the specification: they now need 15 frames at the original spec and 5 frames at a modified spec (different mounting hole pattern, additional reinforcement welds). The modified spec requires re-programming the CNC, a different welding fixture, and a revised quality inspection plan. Delivery date is unchanged.
+
+**Why It's Tricky:**
+The 12 completed frames and 4 in-process frames are at the original spec. If the change applies to any of these, the rework cost is substantial (re-machining mounting holes, adding welds to finished frames). The 4 unstarted frames can be built to the new spec without rework. But the customer wants 5 modified frames, and only 4 are unstarted.
+
+**Common Mistake:**
+Accepting the change without quantifying the rework cost and schedule impact, or rejecting the change outright without exploring options.
+
+**Expert Approach:**
+1. **Analyse the change impact by production stage:**
+ - 4 unstarted frames: can be built to modified spec with no rework. CNC reprogramming takes 4 hours. Welding fixture modification takes 6 hours.
+ - 4 frames in machining: modification requires adding the new mounting holes, which can be done as an additional machining operation before the frames leave CNC. Added time: 2 hours per frame = 8 hours.
+ - 12 completed frames at welding: modification would require returning frames to CNC (re-fixturing, new hole pattern), then additional welding operations. Cost: $1,200 per frame rework + 4 hours per frame on the CNC constraint. This is expensive and uses 48 hours of constraint capacity.
+2. **Propose the least-cost solution:**
+ - Build 4 unstarted frames to modified spec.
+ - Modify 1 of the 4 in-machining frames (the one least progressed) to modified spec. This gives Customer X their 5 modified frames.
+ - Complete the remaining 15 frames at original spec as planned.
+ - Total added cost: CNC reprogramming (4 hrs) + welding fixture modification (6 hrs) + additional machining on the modified in-process frame (2 hrs) = 12 hours added to the schedule.
+3. **Price the change:** Calculate the total cost (labour, material, fixture modification, schedule disruption) and issue a change order cost estimate to Customer X before executing. The customer should approve the cost delta.
+4. **Schedule the change:** Insert the CNC reprogramming and fixture modification into the schedule. The 4 unstarted frames are re-routed to the modified spec routing. The 1 in-process frame gets an additional operation added to its routing.
+5. **Assess delivery impact:** 12 hours added to the critical path. Can this be absorbed within the original delivery date? If not, negotiate a 2-day extension or authorize overtime to recover the 12 hours.
+
+**Documentation Required:**
+- Engineering change analysis showing impact per production stage
+- Rework cost estimate per frame (by stage)
+- Recommended solution with minimum cost/disruption
+- Change order cost estimate for customer approval
+- Revised schedule showing added operations
+- Delivery impact assessment
+
+---
+
+### Edge Case 10: New Product Introduction Competing with Existing Orders
+
+**Situation:**
+A precision stamping company has been awarded a new contract for an automotive EV battery enclosure (a high-profile new product introduction, or NPI). The NPI requires 3 trial production runs over the next 6 weeks to qualify the tooling, validate the process, and produce samples for customer approval. Each trial run requires 8 hours on the 400-ton stamping press (the plant's constraint) plus 4 hours of changeover and die tryout between runs. The constraint is already running at 88% utilisation with existing customer orders. The NPI trial runs need 36 hours of constraint time over 6 weeks (6 hours/week average), which would push constraint utilisation to 93% — within capacity but with almost no buffer.
+
+**Why It's Tricky:**
+NPI trial runs are unpredictable: the first run may reveal tooling issues requiring extended die adjustment (adding 4–8 hours), scrap rates on trial runs are typically 10–30% (vs. 2–3% for production runs), and engineering may need to stop the trial for measurements, adjustments, and design iterations. A trial run scheduled for 8 hours may actually consume 12–16 hours when interruptions are factored in.
+
+**Common Mistake:**
+Scheduling NPI trials into standard production slots and expecting them to run on time. When the trial overruns, it displaces existing customer orders and creates cascading delays.
+
+**Expert Approach:**
+1. **Do not schedule NPI trials at scheduled utilisation.** The 8-hour nominal trial time should be planned as a 14-hour window (8 hours production + 4 hours changeover + 2 hours contingency for tooling issues). This is realistic, not pessimistic, for first and second trials.
+2. **Schedule trial runs at the end of the week** (Friday PM or Saturday) when any overrun pushes into the weekend rather than into Monday's committed production schedule. If the trial finishes early, the slot converts to weekend overtime production (recovering any capacity borrowed from the week).
+3. **Reserve a "trial buffer" in the weekly schedule:** Block 14 hours per week as tentatively reserved for NPI. If the trial proceeds on schedule, this time is used as planned. If the trial is cancelled or postponed (common for NPIs), the buffer converts to regular production or maintenance.
+4. **Protect existing customer commitments:** No existing order should have its due date moved to accommodate the NPI trial. If constraint capacity cannot accommodate both, escalate to management: the NPI trial schedule may need to extend beyond 6 weeks, or the plant may need Saturday overtime to create the capacity.
+5. **Assign the most experienced setup technician and stamping operator** to the NPI trials. Trial-run productivity is heavily dependent on operator skill in adjusting die settings and recognising incipient defects. A junior operator on a trial run will consume 30–50% more time.
+6. **After each trial run, update the time estimate** for the next trial. If Trial 1 took 14 hours and produced 15% scrap, plan Trial 2 at 12 hours (process should be improving) but keep the full 14-hour buffer until proven otherwise.
+
+**Documentation Required:**
+- NPI trial schedule with buffered time estimates
+- Constraint capacity analysis showing impact on existing orders
+- Contingency plan if trial overruns
+- Customer communication plan if existing orders are at risk
+- Trial results and time actuals for updating subsequent trial estimates
+- Post-trial tooling qualification report
+
+---
+
+### Edge Case 11: Simultaneous Material Shortage and Equipment Degradation
+
+**Situation:**
+A food processing plant producing canned soups faces two simultaneous problems: (1) the primary tomato paste supplier is 4 days late on a delivery that was supposed to arrive Monday, affecting all tomato-based soup production scheduled for this week, and (2) the retort (sterilisation vessel) — the plant's constraint — has developed a slow steam leak that reduces its effective cycle time by 12% (each batch takes 45 minutes instead of 40 minutes). Maintenance can fix the leak during a planned maintenance window on Saturday, but running the retort at reduced capacity all week compounds the supplier delay.
+
+**Expert Approach:**
+1. Re-sequence the week to run non-tomato soup products (chicken, vegetable, cream-based) first while waiting for the tomato paste delivery. This keeps the retort running even at reduced capacity.
+2. Calculate the effective capacity loss: 12% longer cycles = ~12% throughput reduction at the constraint. Over a 120-hour production week, this is 14.4 hours of lost capacity, equivalent to roughly 18 batches (at 48 min/batch effective).
+3. When the tomato paste arrives (projected Thursday), re-sequence tomato soups with the most urgent due dates first.
+4. Evaluate whether Saturday maintenance can be pulled forward to Wednesday night (sacrificing one night shift of production but restoring full capacity for Thursday–Friday).
+5. Calculate the net capacity impact of early maintenance vs. running degraded all week: early fix loses 8 hours of production but recovers 12% efficiency for remaining 40+ hours = net gain of ~4.8 hours.
+6. Customer priority: rank all orders by delivery date and penalty risk. Allocate retort capacity accordingly.
+
+---
+
+### Edge Case 12: ERP System Upgrade During Production Week
+
+**Situation:**
+IT has scheduled an ERP system upgrade (SAP ECC to S/4HANA migration cutover) for the upcoming weekend, with the system offline from Friday 6:00 PM to Monday 6:00 AM. The plant runs 24/7 production. During the outage, operators cannot confirm operations, material transactions cannot be posted, and work order status cannot be updated. The scheduling tool (which reads from SAP) will not receive real-time data.
+
+**Expert Approach:**
+1. Print all work orders, routings, BOMs, and the production schedule for Friday PM through Monday AM. Distribute physical copies to every shift supervisor and work centre.
+2. Pre-issue all materials needed for weekend production. Complete all goods issues in SAP before 6:00 PM Friday. Operators should not need to perform material transactions during the outage.
+3. Implement manual shop floor tracking: paper travellers accompanying each batch, operator log sheets recording start/end times, quantities, and scrap.
+4. Freeze the schedule for the weekend — no re-sequencing unless a genuine disruption (breakdown, quality hold) occurs. Without system support, ad-hoc schedule changes are extremely error-prone.
+5. Monday AM: enter all weekend transactions into the new system. This "catch-up" data entry will take 2–4 hours. Assign a dedicated team. Verify inventory balances match physical counts before releasing the Monday schedule.
+6. Have IT on standby for Monday morning to resolve any data migration issues that affect production records.
+
+**Documentation Required:**
+- Pre-printed schedule and work order packets
+- Material pre-issue verification checklist
+- Manual tracking forms and instructions
+- Monday catch-up data entry plan
+- IT escalation contacts for Monday morning
+
+**Resolution Timeline:**
+- Friday − 1 week: Print all production documentation, verify completeness
+- Friday − 2 days: Pre-issue all weekend materials in SAP
+- Friday 6:00 PM: System goes offline. Switch to manual tracking.
+- Saturday–Sunday: Manual operations with paper travellers
+- Monday 6:00 AM: System restored. Begin catch-up data entry.
+- Monday 10:00 AM: Inventory verification and schedule release for Monday production
+
+---
+
+### Edge Case 13: Batch Traceability Contamination — Product Recall Scenario
+
+**Situation:**
+A medical device manufacturer receives a supplier notification that a lot of surgical-grade stainless steel (Heat #A7742) may contain elevated levels of nickel beyond the ASTM F138 specification. The supplier is still testing, but has issued a precautionary advisory. The plant's records show Heat #A7742 was received 3 weeks ago and has been consumed across 14 production work orders for 3 different product families (hip implant stems, bone screws, and spinal rods). Some finished goods from these work orders have already shipped to 4 hospital systems.
+
+**Why It's Tricky:**
+Full traceability is mandatory under FDA 21 CFR Part 820 for medical devices. The scheduler must immediately identify every work order, every operation, every batch that consumed material from Heat #A7742. Some of this material may be in WIP across multiple production stages. A false-positive (the material is actually fine) means the quarantine was unnecessary but the disruption was real. A false-negative (failing to quarantine all affected units) could result in a Class I recall.
+
+**Common Mistake:**
+Quarantining only the known remaining raw material from Heat #A7742 and missing the WIP and finished goods. Or waiting for the supplier's final test results before acting (which could take 5–7 business days).
+
+**Expert Approach:**
+1. **Immediate lot trace (Hour 0–2):** Run a forward lot trace from Heat #A7742 through every production stage. In the ERP, trace the material receipt to every goods issue, then to every work order that consumed it, then to every finished goods batch, then to every shipment.
+2. **Quarantine all affected WIP (Hour 0–4):** Every work-in-process piece traceable to Heat #A7742 must be physically segregated and tagged with "QUALITY HOLD — SUPPLIER ADVISORY" status. Update work order status in the ERP to "blocked."
+3. **Identify shipped finished goods:** For units already shipped, prepare a device history record (DHR) extract for the quality team. They will assess whether a customer notification or field action is required.
+4. **Re-schedule all affected work orders:** These are now blocked. Remove them from the active schedule. Calculate the impact on customer deliveries. The 14 work orders represent significant production volume — their removal creates a capacity surplus at some work centres and a delivery shortfall.
+5. **Fill the capacity gap:** Pull forward work orders for unaffected product families. Keep the constraint running on unaffected work. The quarantine should not idle the constraint if other schedulable work exists.
+6. **Monitor the supplier investigation:** Request daily updates. If the material passes testing (false alarm), the quarantined WIP can be released and re-inserted into the schedule. If the material fails, transition from quarantine to scrap/rework disposition.
+7. **Schedule replacement production:** If the quarantined material is confirmed non-conforming, replacement raw material must be ordered and new work orders created. Calculate the lead time for replacement material + production to meet customer delivery obligations.
+
+**Documentation Required:**
+- Full forward lot trace from Heat #A7742
+- Quarantine records for all WIP and finished goods
+- Shipped goods report for quality team
+- Revised schedule excluding quarantined work orders
+- Replacement material purchase order
+- Customer notification drafts (for quality team review)
+- Daily supplier investigation status updates
+
+**Resolution Timeline:**
+- Hour 0: Supplier advisory received
+- Hour 0–2: Lot trace completed, scope of exposure quantified
+- Hour 2–4: All affected WIP quarantined, schedule revised
+- Hour 4–8: Customer delivery impact assessed, replacement material ordered
+- Day 2–7: Awaiting supplier test results, running unaffected production
+- Day 7+: Disposition decision (release or scrap), recovery schedule published
+
+---
+
+### Edge Case 14: Power Curtailment Order During Peak Production
+
+**Situation:**
+During a summer heat wave, the regional utility issues a mandatory curtailment order requiring the plant to reduce electrical consumption by 30% during peak hours (1:00 PM – 7:00 PM) for the next 5 business days. The plant's major electrical loads are: arc welding stations (35% of load), CNC machining (25%), HVAC/lighting (20%), and electric furnaces (20%). The constraint work centre is a CNC machining cell. Shutting down any production equipment during peak hours will reduce output. Non-compliance with the curtailment order carries fines of $50,000/day.
+
+**Expert Approach:**
+1. **Load analysis:** Identify which equipment can be shut down during peak hours with the least production impact. HVAC cannot be fully shut down (heat stress safety risk for operators), but setpoint can be raised by 3–4°F to reduce load by ~30% of HVAC consumption.
+2. **Shift heavy loads to off-peak:** Move arc welding operations to the early morning (5:00 AM – 1:00 PM) and evening (7:00 PM – 1:00 AM) shifts. Welding is labour-intensive but electrically heavy — shifting it avoids most of the curtailment window.
+3. **Protect the constraint:** CNC machining is the constraint. Calculate whether CNC can run during the curtailment window if welding and furnaces are offline. If CNC alone is within the 70% power allowance, keep CNC running and idle the other major loads.
+4. **Electric furnace scheduling:** Pre-heat and pre-melt in the morning. Hold molten metal in insulated vessels during the curtailment window (thermal mass carries 4–6 hours). Resume furnace operations at 7:00 PM.
+5. **Reschedule the week:** Create two sub-schedules:
+ - Off-peak (5:00 AM – 1:00 PM and 7:00 PM – 5:00 AM): Full production, all work centres operational.
+ - Peak curtailment (1:00 PM – 7:00 PM): Constraint (CNC) running, welding and furnaces offline, non-electrical operations (manual assembly, inspection, packaging, material prep) active.
+6. **Labour adjustment:** Operators who normally work day shift welding are reassigned to manual operations during curtailment hours, then brought back to welding on an adjusted schedule. Check overtime implications — some operators may need split shifts.
+7. **Customer impact:** Calculate the throughput reduction from 5 days of restricted production. If the constraint runs during curtailment but non-constraints do not, the throughput impact may be small (constraint is the bottleneck). Quantify and notify affected customers if any delivery dates slip.
+
+**Documentation Required:**
+- Load analysis by equipment and time window
+- Curtailment compliance plan (submitted to utility if required)
+- Revised daily schedules for the 5-day curtailment period
+- Labour reassignment plan
+- Customer delivery impact assessment
+- Cost analysis: compliance plan cost vs. $50K/day non-compliance fine
+
+---
+
+### Edge Case 15: Concurrent Preventive Maintenance and Rush Order
+
+**Situation:**
+A stamping plant's quarterly preventive maintenance (PM) on the 600-ton press (the constraint) is scheduled for this Saturday, requiring a full 10-hour shutdown for die inspection, hydraulic system service, and electrical control calibration. On Thursday afternoon, the plant receives a rush order from its largest customer: 5,000 brackets due Wednesday of next week. The 600-ton press is the only machine that can stamp these brackets. The job requires 18 hours of press time. Without the Saturday PM, the bracket run can start Friday evening and finish Sunday afternoon, meeting the Wednesday deadline easily. With the PM, the bracket run cannot start until Sunday afternoon and will finish Tuesday, cutting it dangerously close to the Wednesday ship deadline.
+
+**Why It's Tricky:**
+Skipping or deferring PM on the constraint is a high-risk gamble. The PM schedule exists because the 600-ton press has a history of hydraulic seal failures when PM intervals stretch beyond the quarterly cycle. A hydraulic failure during the bracket run would be catastrophic — potentially damaging the die (a $45,000 asset), scrapping in-process work, and causing multiple days of unplanned downtime.
+
+**Expert Approach:**
+1. **Do not skip the PM.** The expected cost of a hydraulic failure (die damage + scrap + 3–5 days unplanned downtime + customer penalties) far exceeds the cost of any workaround.
+2. **Can the PM be compressed?** Consult maintenance: can the 10-hour PM be reduced to 6 hours by parallelising activities (two maintenance crews working simultaneously on hydraulics and electrical)? If so, the press is available Saturday evening instead of Sunday morning, giving an extra 8+ hours for the bracket run.
+3. **Can the PM be moved earlier?** If PM starts Friday night instead of Saturday morning, the press is available by Saturday morning. Friday night PM means cancelling Friday night production — calculate the lost production (probably 1 shift of lower-priority work) vs. the benefit of earlier bracket availability.
+4. **Can the bracket run be accelerated?** Check if the die can be modified for a 2-out configuration (stamping 2 brackets per stroke instead of 1). If tooling supports this and first-piece quality validates, the 18-hour job drops to 10 hours. This is a production engineering question, not just a scheduling question.
+5. **Recommended plan:** Move PM to Friday 10:00 PM – Saturday 8:00 AM (compressed to 10 hours or less). Start bracket run Saturday 8:00 AM. At 18 hours, the run finishes Sunday 2:00 AM. Ship Monday for Wednesday delivery — comfortable margin.
+6. **Backup plan:** If PM cannot be compressed or moved earlier, start the bracket run Sunday afternoon, run through Sunday night and Monday day shift (18 hours completion by Monday evening), and ship Tuesday for Wednesday delivery. This is tight but feasible. Add an overtime shift Monday evening as insurance.
+
+**Documentation Required:**
+- PM schedule analysis showing compression/shift options
+- Bracket run time calculation and earliest-start-time scenarios
+- Risk assessment of PM deferral (not recommended, but documented to explain the decision)
+- Customer delivery confirmation with the chosen plan
+- Maintenance crew availability for compressed PM schedule
+
+**Resolution Timeline:**
+- Thursday PM: Rush order received
+- Thursday PM + 2 hours: PM compression/shift analysis completed
+- Thursday end-of-day: Decision made, revised schedule published
+- Friday night or Saturday AM: PM begins
+- Saturday AM or PM: Bracket run begins
+- Sunday or Monday: Bracket run complete
+- Monday–Tuesday: Ship for Wednesday delivery
+
+---
+
+### Edge Case 16: Multi-Site Load Balancing Under Capacity Crunch
+
+**Situation:**
+A packaging company operates two plants 90 miles apart. Plant A specialises in rigid plastic containers (thermoforming + printing) and Plant B specialises in flexible pouches (form-fill-seal). Both plants have secondary capability in the other's specialty, but at 30–40% lower throughput rates. Plant A's thermoforming constraint is at 97% utilisation for the next 3 weeks. Plant B's form-fill-seal line is at 72%. A key customer (national retailer) has just increased their Q4 order for rigid containers by 25%, pushing Plant A's projected utilisation to 122%.
+
+**Why It's Tricky:**
+Moving rigid container production to Plant B is technically possible but operationally complex: different tooling must be transferred, operator cross-training is limited, Plant B's rigid container quality history is weaker, and the customer has approved Plant A as the manufacturing site (switching sites may require customer re-qualification, especially for food-contact packaging).
+
+**Common Mistake:**
+Accepting all incremental volume at Plant A and planning to "make it work" with overtime. At 122% utilisation, even maximum overtime only reaches ~108%, creating an inevitable 14% shortfall. Or refusing the incremental order without exploring Plant B as an option.
+
+**Expert Approach:**
+1. **Quantify the overflow precisely:** Plant A needs 22% more capacity = 26.4 hours/week over 3 weeks = 79.2 total overflow hours.
+2. **Assess Plant A's maximum realistic capacity:** Standard (120 hrs/week) + Saturday OT (16 hrs) + reduced changeovers (estimated 4 hrs recovery through better sequencing) = 140 hrs/week max. At 122% requirement = 146.4 hrs needed. Plant A can deliver 140 hrs, shortfall = 6.4 hrs/week = 19.2 hours over 3 weeks.
+3. **Assess Plant B's absorption capacity:** Plant B's rigid container capability runs at 70% of Plant A's throughput. 19.2 hours of Plant A work = 27.4 hours at Plant B's rate. Plant B has 33.6 hours of available capacity (120 × 28% headroom) — it can absorb the overflow.
+4. **Customer qualification:** Contact the customer's quality team to determine whether a temporary site switch requires re-qualification. For food-contact packaging, the answer is usually yes for a new site, but may be waived if both plants hold the same certifications (SQF, BRC, FDA registration) and use identical raw materials.
+5. **Tooling transfer plan:** Which moulds and print plates need to move to Plant B? What is the transfer time (transport + setup + qualification runs at Plant B)? Plan for 2–3 days of transfer activity before Plant B can begin producing.
+6. **Quality safeguard:** Assign Plant A's quality supervisor to Plant B for the first 2 days of the overflow production run. First-article inspection with full dimensional check before releasing production quantities.
+7. **Logistics:** Coordinate shipping from Plant B to the customer's DC. If the customer expects a single point of shipment, Plant B's output may need to be consolidated at Plant A before shipping.
+
+**Documentation Required:**
+- Capacity analysis for both plants over the 3-week horizon
+- Overflow volume calculation and Plant B absorption plan
+- Customer qualification requirement assessment
+- Tooling transfer schedule
+- Quality plan for Plant B overflow production
+- Logistics coordination plan
+- Cost comparison: overtime at Plant A vs. transfer + production at Plant B
+
+---
+
+### Edge Case 17: Seasonal Product Transition with Shared Tooling
+
+**Situation:**
+A consumer goods manufacturer produces both summer products (portable fans, outdoor lighting) and winter products (space heaters, humidifiers) on shared injection moulding and assembly lines. The seasonal transition begins in August: summer products wind down while winter products ramp up. Both product families share 6 of the plant's 10 injection moulding machines, requiring complete mould changes (4–6 hours per machine). The transition must happen while simultaneously filling the last summer orders (end-of-season clearance orders from retailers, due by August 31) and beginning the winter build-up (first winter shipments due September 15).
+
+**Why It's Tricky:**
+During the transition period, the plant needs to produce both summer and winter products on the same machines. Every mould change consumes 4–6 hours of production capacity. If you transition all 6 machines at once, you lose 24–36 hours of capacity in a single week — during the highest-demand period. If you transition one machine at a time, you maintain more capacity but stretch the transition over 3+ weeks, during which the schedule is constantly in flux with different machines running different product families.
+
+**Expert Approach:**
+1. **Phase the transition by machine and demand priority:**
+ - Weeks 1–2 (Aug 1–14): Keep all 6 machines on summer products. Fill all remaining summer orders.
+ - Week 3 (Aug 15–21): Transition 2 machines to winter moulds. These begin producing the highest-priority winter products.
+ - Week 4 (Aug 22–28): Transition 2 more machines. Now 4 winter, 2 summer.
+ - Week 5 (Aug 29 – Sep 4): Transition final 2 machines. All 6 on winter products.
+2. **Priority sequencing during transition:**
+ - Summer machines in Weeks 3–4 focus exclusively on committed retailer orders with firm due dates. No speculative production.
+ - Winter machines in Weeks 3–4 focus on long-lead-time components that downstream assembly needs by September 15.
+3. **Mould change scheduling:** Schedule all mould changes for Friday PM or Saturday AM, when the changeover downtime has the least impact on committed production (assuming the plant runs Mon–Fri with Saturday overtime available).
+4. **Buffer management:** Build 1 week of safety stock on critical summer components before Week 3 begins. This buffers downstream assembly from any transition-related disruptions on the moulding machines.
+5. **Labour coordination:** Mould changes require skilled tooling technicians. Ensure technician availability matches the changeover schedule — do not schedule 4 mould changes on the same day with only 2 technicians.
+
+**Documentation Required:**
+- Phased transition schedule showing machine-by-product assignment per week
+- Summer order backlog with due dates and machine requirements
+- Winter build-up schedule with component lead times
+- Mould change schedule with technician assignments
+- Safety stock build plan for transition buffer
+- Post-transition capacity verification (all winter moulds qualified and running at standard rates)
+
+**Resolution Timeline:**
+- Aug 1: Transition plan published to all departments
+- Aug 1–14: Summer production, safety stock build
+- Aug 15: First 2 machines transition — winter production begins
+- Aug 22: Second pair transitions
+- Aug 29: Final pair transitions — full winter production
+- Sep 5: Post-transition review — all machines at standard winter rates
+- Sep 15: First winter shipments
+
+---
+
+## Summary: Edge Case Pattern Recognition
+
+Experienced production schedulers recognise recurring patterns across these edge cases:
+
+| Pattern | Key Indicator | First Response |
+|---|---|---|
+| **Constraint shift** | WIP moving from one queue to another unexpectedly | Re-identify the constraint. Don't re-sequence unless shift persists. |
+| **Single-point-of-failure** | One operator, one machine, one supplier | Cross-train, qualify alternates, dual-source before the failure occurs. |
+| **Commercial vs. physical conflict** | Multiple customers need the same scarce resource | Quantify the tradeoff. Present options. Let management decide. |
+| **Data integrity failure** | MRP generating implausible demand, phantom inventory | Verify at the source. Trace the data. Fix the root before acting on bad data. |
+| **Cascading quality issue** | Defect detected late, affecting multiple production stages | Full containment first, rework assessment second, schedule recovery third. |
+| **External constraint imposed** | Utility curtailment, regulatory stop, weather | Protect the constraint. Shift flexible operations around the restriction. |
+| **Transition complexity** | Product mix changing, seasonal changeover, NPI | Phase the transition. Buffer between old and new. Don't try to flip everything at once. |
+
+The common thread: **never sacrifice the constraint's output for a non-constraint problem.** Every decision should be evaluated through the lens of: "Does this protect or harm throughput at the constraint?" If a disruption does not affect the constraint (directly or through buffer penetration), it is lower priority regardless of how visible or noisy it is on the shop floor.
diff --git a/skills/programmatic-seo/SKILL.md b/skills/programmatic-seo/SKILL.md
index 28a2b0c1..dd0cf288 100644
--- a/skills/programmatic-seo/SKILL.md
+++ b/skills/programmatic-seo/SKILL.md
@@ -1,6 +1,6 @@
---
name: programmatic-seo
-description: ">"
+description: >
Design and evaluate programmatic SEO strategies for creating SEO-driven pages
at scale using templates and structured data. Use when the user mentions
programmatic SEO, pages at scale, template pages, directory pages, location pages,
diff --git a/skills/python-pro/SKILL.md b/skills/python-pro/SKILL.md
index 97430766..d4c64386 100644
--- a/skills/python-pro/SKILL.md
+++ b/skills/python-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: python-pro
-description: "Master Python 3.12+ with modern features, async programming,"
+description: |
+ Master Python 3.12+ with modern features, async programming,
performance optimization, and production-ready practices. Expert in the latest
Python ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY
for Python development, optimization, or advanced Python patterns.
diff --git a/skills/quality-nonconformance/SKILL.md b/skills/quality-nonconformance/SKILL.md
new file mode 100644
index 00000000..e0a2f8ef
--- /dev/null
+++ b/skills/quality-nonconformance/SKILL.md
@@ -0,0 +1,250 @@
+---
+name: quality-nonconformance
+description: >
+ Codified expertise for quality control, non-conformance investigation, root
+ cause analysis, corrective action, and supplier quality management in
+ regulated manufacturing. Informed by quality engineers with 15+ years
+ experience across FDA, IATF 16949, and AS9100 environments. Includes NCR
+ lifecycle management, CAPA systems, SPC interpretation, and audit methodology.
+ Use when investigating non-conformances, performing root cause analysis,
+ managing CAPAs, interpreting SPC data, or handling supplier quality issues.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🔍"
+---
+
+## When to Use
+
+Use this skill when investigating product defects or process deviations, performing root cause analysis (RCA), managing Corrective and Preventive Actions (CAPA), interpreting Statistical Process Control (SPC) data, or auditing supplier quality.
+
+# Quality & Non-Conformance Management
+
+## Role and Context
+
+You are a senior quality engineer with 15+ years in regulated manufacturing environments — FDA 21 CFR 820 (medical devices), IATF 16949 (automotive), AS9100 (aerospace), and ISO 13485 (medical devices). You manage the full non-conformance lifecycle from incoming inspection through final disposition. Your systems include QMS (eQMS platforms like MasterControl, ETQ, Veeva), SPC software (Minitab, InfinityQS), ERP (SAP QM, Oracle Quality), CMM and metrology equipment, and supplier portals. You sit at the intersection of manufacturing, engineering, procurement, regulatory, and customer quality. Your judgment calls directly affect product safety, regulatory standing, production throughput, and supplier relationships.
+
+## Core Knowledge
+
+### NCR Lifecycle
+
+Every non-conformance follows a controlled lifecycle. Skipping steps creates audit findings and regulatory risk:
+
+- **Identification:** Anyone can initiate. Record: who found it, where (incoming, in-process, final, field), what standard/spec was violated, quantity affected, lot/batch traceability. Tag or quarantine nonconforming material immediately — no exceptions. Physical segregation with red-tag or hold-tag in a designated MRB area. Electronic hold in ERP to prevent inadvertent shipment.
+- **Documentation:** NCR number assigned per your QMS numbering scheme. Link to part number, revision, PO/work order, specification clause violated, measurement data (actuals vs. tolerances), photographs, and inspector ID. For FDA-regulated products, records must satisfy 21 CFR 820.90; for automotive, IATF 16949 §8.7.
+- **Investigation:** Determine scope — is this an isolated piece or a systemic lot issue? Check upstream and downstream: other lots from the same supplier shipment, other units from the same production run, WIP and finished goods inventory from the same period. Containment actions must happen before root cause analysis begins.
+- **Disposition via MRB (Material Review Board):** The MRB typically includes quality, engineering, and manufacturing representatives. For aerospace (AS9100), the customer may need to participate. Disposition options:
+ - **Use-as-is:** Part does not meet drawing but is functionally acceptable. Requires engineering justification (concession/deviation). In aerospace, requires customer approval per AS9100 §8.7.1. In automotive, customer notification is typically required. Document the rationale — "because we need the parts" is not a justification.
+ - **Rework:** Bring the part into conformance using an approved rework procedure. The rework instruction must be documented, and the reworked part must be re-inspected to the original specification. Track rework costs.
+ - **Repair:** Part will not fully meet the original specification but will be made functional. Requires engineering disposition and often customer concession. Different from rework — repair accepts a permanent deviation.
+ - **Return to Vendor (RTV):** Issue a Supplier Corrective Action Request (SCAR) or CAR. Debit memo or replacement PO. Track supplier response within agreed timelines. Update supplier scorecard.
+ - **Scrap:** Document scrap with quantity, cost, lot traceability, and authorized scrap approval (often requires management sign-off above a dollar threshold). For serialized or safety-critical parts, witness destruction.
+
+### Root Cause Analysis
+
+Stopping at symptoms is the most common failure mode in quality investigations:
+
+- **5 Whys:** Simple, effective for straightforward process failures. Limitation: assumes a single linear causal chain. Fails on complex, multi-factor problems. Each "why" must be verified with data, not opinion — "Why did the dimension drift?" → "Because the tool wore" is only valid if you measured tool wear.
+- **Ishikawa (Fishbone) Diagram:** Use the 6M framework (Man, Machine, Material, Method, Measurement, Mother Nature/Environment). Forces consideration of all potential cause categories. Most useful as a brainstorming framework to prevent premature convergence on a single cause. Not a root cause tool by itself — it generates hypotheses that need verification.
+- **Fault Tree Analysis (FTA):** Top-down, deductive. Start with the failure event and decompose into contributing causes using AND/OR logic gates. Quantitative when failure rate data is available. Required or expected in aerospace (AS9100) and medical device (ISO 14971 risk analysis) contexts. Most rigorous method but resource-intensive.
+- **8D Methodology:** Team-based, structured problem-solving. D0: Symptom recognition and emergency response. D1: Team formation. D2: Problem definition (IS/IS-NOT). D3: Interim containment. D4: Root cause identification (use fishbone + 5 Whys within 8D). D5: Corrective action selection. D6: Implementation. D7: Prevention of recurrence. D8: Team recognition. Automotive OEMs (GM, Ford, Stellantis) expect 8D reports for significant supplier quality issues.
+- **Red flags that you stopped at symptoms:** Your "root cause" contains the word "error" (human error is never a root cause — why did the system allow the error?), your corrective action is "retrain the operator" (training alone is the weakest corrective action), or your root cause matches the problem statement reworded.
+
+### CAPA System
+
+CAPA is the regulatory backbone. FDA cites CAPA deficiencies more than any other subsystem:
+
+- **Initiation:** Not every NCR requires a CAPA. Triggers: repeat non-conformances (same failure mode 3+ times), customer complaints, audit findings, field failures, trend analysis (SPC signals), regulatory observations. Over-initiating CAPAs dilutes resources and creates closure backlogs. Under-initiating creates audit findings.
+- **Corrective Action vs. Preventive Action:** Corrective addresses an existing non-conformance and prevents its recurrence. Preventive addresses a potential non-conformance that hasn't occurred yet — typically identified through trend analysis, risk assessment, or near-miss events. FDA expects both; don't conflate them.
+- **Writing Effective CAPAs:** The action must be specific, measurable, and address the verified root cause. Bad: "Improve inspection procedures." Good: "Add torque verification step at Station 12 with calibrated torque wrench (±2%), documented on traveler checklist WI-4401 Rev C, effective by 2025-04-15." Every CAPA must have an owner, a target date, and defined evidence of completion.
+- **Verification vs. Validation of Effectiveness:** Verification confirms the action was implemented as planned (did we install the poka-yoke fixture?). Validation confirms the action actually prevented recurrence (did the defect rate drop to zero over 90 days of production data?). FDA expects both. Closing a CAPA at verification without validation is a common audit finding.
+- **Closure Criteria:** Objective evidence that the corrective action was implemented AND effective. Minimum effectiveness monitoring period: 90 days for process changes, 3 production lots for material changes, or the next audit cycle for system changes. Document the effectiveness data — charts, rejection rates, audit results.
+- **Regulatory Expectations:** FDA 21 CFR 820.198 (complaint handling) and 820.90 (nonconforming product) feed into 820.100 (CAPA). IATF 16949 §10.2.3-10.2.6. AS9100 §10.2. ISO 13485 §8.5.2-8.5.3. Each standard has specific documentation and timing expectations.
+
+### Statistical Process Control (SPC)
+
+SPC separates signal from noise. Misinterpreting charts causes more problems than not charting at all:
+
+- **Chart Selection:** X-bar/R for continuous data with subgroups (n=2-10). X-bar/S for subgroups n>10. Individual/Moving Range (I-MR) for continuous data with subgroup n=1 (batch processes, destructive testing). p-chart for proportion defective (variable sample size). np-chart for count of defectives (fixed sample size). c-chart for count of defects per unit (fixed opportunity area). u-chart for defects per unit (variable opportunity area).
+- **Capability Indices:** Cp measures process spread vs. specification width (potential capability). Cpk adjusts for centering (actual capability). Pp/Ppk use overall variation (long-term) vs. Cp/Cpk which use within-subgroup variation (short-term). A process with Cp=2.0 but Cpk=0.8 is capable but not centered — fix the mean, not the variation. Automotive (IATF 16949) typically requires Cpk ≥ 1.33 for established processes, Ppk ≥ 1.67 for new processes.
+- **Western Electric Rules (signals beyond control limits):** Rule 1: One point beyond 3σ. Rule 2: Nine consecutive points on one side of the center line. Rule 3: Six consecutive points steadily increasing or decreasing. Rule 4: Fourteen consecutive points alternating up and down. Rule 1 demands immediate action. Rules 2-4 indicate systematic causes requiring investigation before the process goes out of spec.
+- **The Over-Adjustment Problem:** Reacting to common cause variation by tweaking the process increases variation — this is tampering. If the chart shows a stable process within control limits but individual points "look high," do not adjust. Only adjust for special cause signals confirmed by the Western Electric rules.
+- **Common vs. Special Cause:** Common cause variation is inherent to the process — reducing it requires fundamental process changes (better equipment, different material, environmental controls). Special cause variation is assignable to a specific event — a worn tool, a new raw material lot, an untrained operator on second shift. SPC's primary function is detecting special causes quickly.
+
+### Incoming Inspection
+
+- **AQL Sampling Plans (ANSI/ASQ Z1.4 / ISO 2859-1):** Determine inspection level (I, II, III — Level II is standard), lot size, AQL value, and sample size code letter. Tightened inspection: switch after 2 of 5 consecutive lots rejected. Normal: default. Reduced: switch after 10 consecutive lots accepted AND production stable. Critical defects: AQL = 0 with appropriate sample size. Major defects: typically AQL 1.0-2.5. Minor defects: typically AQL 2.5-6.5.
+- **LTPD (Lot Tolerance Percent Defective):** The defect level the plan is designed to reject. AQL protects the producer (low risk of rejecting good lots). LTPD protects the consumer (low risk of accepting bad lots). Understanding both sides is critical for communicating inspection risk to management.
+- **Skip-Lot Qualification:** After a supplier demonstrates consistent quality (typically 10+ consecutive lots accepted at normal inspection), reduce frequency to inspecting every 2nd, 3rd, or 5th lot. Revert immediately upon any rejection. Requires formal qualification criteria and documented decision.
+- **Certificate of Conformance (CoC) Reliance:** When to trust supplier CoCs vs. performing incoming inspection: new supplier = always inspect; qualified supplier with history = CoC + reduced verification; critical/safety dimensions = always inspect regardless of history. CoC reliance requires a documented agreement and periodic audit verification (audit the supplier's final inspection process, not just the paperwork).
+
+### Supplier Quality Management
+
+- **Audit Methodology:** Process audits assess how work is done (observe, interview, sample). System audits assess QMS compliance (document review, record sampling). Product audits verify specific product characteristics. Use a risk-based audit schedule — high-risk suppliers annually, medium biennially, low every 3 years plus cause-based. Announce audits for system assessments; unannounced audits for process verification when performance concerns exist.
+- **Supplier Scorecards:** Measure PPM (parts per million defective), on-time delivery, SCAR response time, SCAR effectiveness (recurrence rate), and lot acceptance rate. Weight the metrics by business impact. Share scorecards quarterly. Scores drive inspection level adjustments, business allocation, and ASL status.
+- **Corrective Action Requests (CARs/SCARs):** Issue for each significant non-conformance or repeated minor non-conformances. Expect 8D or equivalent root cause analysis. Set response deadline (typically 10 business days for initial response, 30 days for full corrective action plan). Follow up on effectiveness verification.
+- **Approved Supplier List (ASL):** Entry requires qualification (first article, capability study, system audit). Maintenance requires ongoing performance meeting scorecard thresholds. Removal is a significant business decision requiring procurement, engineering, and quality agreement plus a transition plan. Provisional status (approved with conditions) is useful for suppliers under improvement plans.
+- **Develop vs. Switch Decisions:** Supplier development (investment in training, process improvement, tooling) makes sense when: the supplier has unique capability, switching costs are high, the relationship is otherwise strong, and the quality gaps are addressable. Switching makes sense when: the supplier is unwilling to invest, the quality trend is deteriorating despite CARs, or alternative qualified sources exist with lower total cost of quality.
+
+### Regulatory Frameworks
+
+- **FDA 21 CFR 820 (QSR):** Covers medical device quality systems. Key sections: 820.90 (nonconforming product), 820.100 (CAPA), 820.198 (complaint handling), 820.250 (statistical techniques). FDA auditors specifically look at CAPA system effectiveness, complaint trending, and whether root cause analysis is rigorous.
+- **IATF 16949 (Automotive):** Adds customer-specific requirements on top of ISO 9001. Control plans, PPAP (Production Part Approval Process), MSA (Measurement Systems Analysis), 8D reporting, special characteristics management. Customer notification required for process changes and non-conformance disposition.
+- **AS9100 (Aerospace):** Adds requirements for product safety, counterfeit part prevention, configuration management, first article inspection (FAI per AS9102), and key characteristic management. Customer approval required for use-as-is dispositions. OASIS database for supplier management.
+- **ISO 13485 (Medical Devices):** Harmonized with FDA QSR but with European regulatory alignment. Emphasis on risk management (ISO 14971), traceability, and design controls. Clinical investigation requirements feed into non-conformance management.
+- **Control Plans:** Define inspection characteristics, methods, frequencies, sample sizes, reaction plans, and responsible parties for each process step. Required by IATF 16949 and good practice universally. Must be a living document updated when processes change.
+
+### Cost of Quality
+
+Build the business case for quality investment using Juran's COQ model:
+
+- **Prevention costs:** Training, process validation, design reviews, supplier qualification, SPC implementation, poka-yoke fixtures. Typically 5-10% of total COQ. Every dollar invested here returns $10-$100 in failure cost avoidance.
+- **Appraisal costs:** Incoming inspection, in-process inspection, final inspection, testing, calibration, audit costs. Typically 20-25% of total COQ.
+- **Internal failure costs:** Scrap, rework, re-inspection, MRB processing, production delays due to non-conformances, root cause investigation labor. Typically 25-40% of total COQ.
+- **External failure costs:** Customer returns, warranty claims, field service, recalls, regulatory actions, liability exposure, reputation damage. Typically 25-40% of total COQ but most volatile and highest per-incident cost.
+
+## Decision Frameworks
+
+### NCR Disposition Decision Logic
+
+Evaluate in this sequence — the first path that applies governs the disposition:
+
+1. **Safety/regulatory critical:** If the non-conformance affects a safety-critical characteristic or regulatory requirement → do not use-as-is. Rework if possible to full conformance, otherwise scrap. No exceptions without formal engineering risk assessment and, where required, regulatory notification.
+2. **Customer-specific requirements:** If the customer specification is tighter than the design spec and the part meets design but not customer requirements → contact customer for concession before disposing. Automotive and aerospace customers have explicit concession processes.
+3. **Functional impact:** Engineering evaluates whether the non-conformance affects form, fit, or function. If no functional impact and within material review authority → use-as-is with documented engineering justification. If functional impact exists → rework or scrap.
+4. **Reworkability:** If the part can be brought into full conformance through an approved rework process → rework. Verify rework cost vs. replacement cost. If rework cost exceeds 60% of replacement cost, scrap is usually more economical.
+5. **Supplier accountability:** If the non-conformance is supplier-caused → RTV with SCAR. Exception: if production cannot wait for replacement parts, use-as-is or rework may be needed with cost recovery from the supplier.
+
+### RCA Method Selection
+
+- **Single-event, simple causal chain:** 5 Whys. Budget: 1-2 hours.
+- **Single-event, multiple potential cause categories:** Ishikawa + 5 Whys on the most likely branches. Budget: 4-8 hours.
+- **Recurring issue, process-related:** 8D with full team. Budget: 20-40 hours across D0-D8.
+- **Safety-critical or high-severity event:** Fault Tree Analysis with quantitative risk assessment. Budget: 40-80 hours. Required for aerospace product safety events and medical device post-market analysis.
+- **Customer-mandated format:** Use whatever the customer requires (most automotive OEMs mandate 8D).
+
+### CAPA Effectiveness Verification
+
+Before closing any CAPA, verify:
+
+1. **Implementation evidence:** Documented proof the action was completed (updated work instruction with revision, installed fixture with validation, modified inspection plan with effective date).
+2. **Monitoring period data:** Minimum 90 days of production data, 3 consecutive production lots, or one full audit cycle — whichever provides the most meaningful evidence.
+3. **Recurrence check:** Zero recurrences of the specific failure mode during the monitoring period. If recurrence occurs, the CAPA is not effective — reopen and re-investigate. Do not close and open a new CAPA for the same issue.
+4. **Leading indicator review:** Beyond the specific failure, have related metrics improved? (e.g., overall PPM for that process, customer complaint rate for that product family).
+
+### Inspection Level Adjustment
+
+| Condition | Action |
+| ---------------------------------------------- | ----------------------------------------------- |
+| New supplier, first 5 lots | Tightened inspection (Level III or 100%) |
+| 10+ consecutive lots accepted at normal | Qualify for reduced or skip-lot |
+| 1 lot rejected under reduced inspection | Revert to normal immediately |
+| 2 of 5 consecutive lots rejected under normal | Switch to tightened |
+| 5 consecutive lots accepted under tightened | Revert to normal |
+| 10 consecutive lots rejected under tightened | Suspend supplier; escalate to procurement |
+| Customer complaint traced to incoming material | Revert to tightened regardless of current level |
+
+### Supplier Corrective Action Escalation
+
+| Stage | Trigger | Action | Timeline |
+| --------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| Level 1: SCAR issued | Single significant NC or 3+ minor NCs in 90 days | Formal SCAR requiring 8D response | 10 days for response, 30 for implementation |
+| Level 2: Supplier on watch | SCAR not responded to in time, or corrective action not effective | Increased inspection, supplier on probation, procurement notified | 60 days to demonstrate improvement |
+| Level 3: Controlled shipping | Continued quality failures during watch period | Supplier must submit inspection data with each shipment; or third-party sort at supplier's expense | 90 days to demonstrate sustained improvement |
+| Level 4: New source qualification | No improvement under controlled shipping | Initiate alternate supplier qualification; reduce business allocation | Qualification timeline (3-12 months depending on industry) |
+| Level 5: ASL removal | Failure to improve or unwillingness to invest | Formal removal from Approved Supplier List; transition all parts | Complete transition before final PO |
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Customer-reported field failure with no internal detection:** Your inspection and testing passed this lot, but customer field data shows failures. The instinct is to question the customer's data — resist it. Check whether your inspection plan covers the actual failure mode. Often, field failures expose gaps in test coverage rather than test execution errors.
+
+2. **Supplier audit reveals falsified Certificates of Conformance:** The supplier has been submitting CoCs with fabricated test data. Quarantine all material from that supplier immediately, including WIP and finished goods. This is a regulatory reportable event in aerospace (counterfeit prevention per AS9100) and potentially in medical devices. The scale of the containment drives the response, not the individual NCR.
+
+3. **SPC shows process in-control but customer complaints are rising:** The chart is stable within control limits, but the customer's assembly process is sensitive to variation within your spec. Your process is "capable" by the numbers but not capable enough. This requires customer collaboration to understand the true functional requirement, not just a spec review.
+
+4. **Non-conformance discovered on already-shipped product:** Containment must extend to the customer's incoming stock, WIP, and potentially their customers. The speed of notification depends on safety risk — safety-critical issues require immediate customer notification, others can follow the standard process with urgency.
+
+5. **CAPA that addresses a symptom, not the root cause:** The defect recurs after CAPA closure. Before reopening, verify the original root cause analysis — if the root cause was "operator error" and the corrective action was "retrain," neither the root cause nor the action was adequate. Start the RCA over with the assumption the first investigation was insufficient.
+
+6. **Multiple root causes for a single non-conformance:** A single defect results from the interaction of machine wear, material lot variation, and a measurement system limitation. The 5 Whys forces a single chain — use Ishikawa or FTA to capture the interaction. Corrective actions must address all contributing causes; fixing only one may reduce frequency but won't eliminate the failure mode.
+
+7. **Intermittent defect that cannot be reproduced on demand:** Cannot reproduce ≠ does not exist. Increase sample size and monitoring frequency. Check for environmental correlations (shift, ambient temperature, humidity, vibration from adjacent equipment). Component of Variation studies (Gauge R&R with nested factors) can reveal intermittent measurement system contributions.
+
+8. **Non-conformance discovered during a regulatory audit:** Do not attempt to minimize or explain away. Acknowledge the finding, document it in the audit response, and treat it as you would any NCR — with a formal investigation, root cause analysis, and CAPA. Auditors specifically test whether your system catches what they find; demonstrating a robust response is more valuable than pretending it's an anomaly.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to situation severity and audience:
+
+- **Routine NCR, internal team:** Direct and factual. "NCR-2025-0412: Incoming lot 4471 of part 7832-A has OD measurements at 12.52mm against a 12.45±0.05mm specification. 18 of 50 sample pieces out of spec. Material quarantined in MRB cage, Bay 3."
+- **Significant NCR, management reporting:** Summarize impact first — production impact, customer risk, financial exposure — then the details. Managers need to know what it means before they need to know what happened.
+- **Supplier notification (SCAR):** Professional, specific, and documented. State the nonconformance, the specification violated, the impact, and the expected response format and timeline. Never accusatory; the data speaks.
+- **Customer notification (non-conformance on shipped product):** Lead with what you know, what you've done (containment), what the customer needs to do, and the timeline for full resolution. Transparency builds trust; delay destroys it.
+- **Regulatory response (audit finding):** Factual, accountable, and structured per the regulatory expectation (e.g., FDA Form 483 response format). Acknowledge the observation, describe the investigation, state the corrective action, provide evidence of implementation and effectiveness.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**NCR Notification (internal):** Subject: `NCR-{number}: {part_number} — {defect_summary}`. State: what was found, specification violated, quantity affected, current containment status, and initial assessment of scope.
+
+**SCAR to Supplier:** Subject: `SCAR-{number}: Non-Conformance on PO# {po_number} — Response Required by {date}`. Include: part number, lot, specification, measurement data, quantity affected, impact statement, expected response format.
+
+**Customer Quality Notification:** Lead with: containment actions taken, product traceability (lot/serial numbers), recommended customer actions, timeline for corrective action, and direct contact for quality engineering.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ---------------------------------------------- | ------------------------------------------------------------- | --------------- |
+| Safety-critical non-conformance | Notify VP Quality and Regulatory immediately | Within 1 hour |
+| Field failure or customer complaint | Assign dedicated investigator, notify account team | Within 4 hours |
+| Repeat NCR (same failure mode, 3+ occurrences) | Mandatory CAPA initiation, management review | Within 24 hours |
+| Supplier falsified documentation | Quarantine all supplier material, notify regulatory and legal | Immediately |
+| Non-conformance on shipped product | Initiate customer notification protocol, containment | Within 4 hours |
+| Audit finding (external) | Management review, response plan development | Within 48 hours |
+| CAPA overdue > 30 days past target | Escalate to Quality Director for resource allocation | Within 1 week |
+| NCR backlog exceeds 50 open items | Process review, resource allocation, management briefing | Within 1 week |
+
+### Escalation Chain
+
+Level 1 (Quality Engineer) → Level 2 (Quality Supervisor, 4 hours) → Level 3 (Quality Manager, 24 hours) → Level 4 (Quality Director, 48 hours) → Level 5 (VP Quality, 72+ hours or any safety-critical event)
+
+## Performance Indicators
+
+Track these metrics weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| --------------------------------------- | ------------------ | ------------------ |
+| NCR closure time (median) | < 15 business days | > 30 business days |
+| CAPA on-time closure rate | > 90% | < 75% |
+| CAPA effectiveness rate (no recurrence) | > 85% | < 70% |
+| Supplier PPM (incoming) | < 500 PPM | > 2,000 PPM |
+| Cost of quality (% of revenue) | < 3% | > 5% |
+| Internal defect rate (in-process) | < 1,000 PPM | > 5,000 PPM |
+| Customer complaint rate (per 1M units) | < 50 | > 200 |
+| Aged NCRs (> 30 days open) | < 10% of total | > 25% |
+
+## Additional Resources
+
+- For detailed decision frameworks, MRB processes, and SPC decision logic, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **run or improve non‑conformance and CAPA processes in regulated manufacturing**:
+
+- Investigating NCRs, selecting root‑cause methods, and defining MRB dispositions and CAPA actions.
+- Designing or auditing CAPA systems, SPC programmes, incoming inspection plans, and supplier quality governance.
+- Preparing for, or responding to, customer and regulatory audits (FDA, IATF, AS9100, ISO 13485) that focus on non‑conformance handling and CAPA effectiveness.
diff --git a/skills/quality-nonconformance/references/communication-templates.md b/skills/quality-nonconformance/references/communication-templates.md
new file mode 100644
index 00000000..b733f4ab
--- /dev/null
+++ b/skills/quality-nonconformance/references/communication-templates.md
@@ -0,0 +1,711 @@
+# Communication Templates — Quality & Non-Conformance Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing quality communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and situation. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [NCR Notification (Internal)](#1-ncr-notification-internal)
+2. [MRB Disposition Record](#2-mrb-disposition-record)
+3. [Corrective Action Request (CAR) to Supplier](#3-corrective-action-request-car-to-supplier)
+4. [CAPA Initiation Record](#4-capa-initiation-record)
+5. [CAPA Effectiveness Review](#5-capa-effectiveness-review)
+6. [Audit Finding Response](#6-audit-finding-response)
+7. [Customer Quality Notification](#7-customer-quality-notification)
+8. [Supplier Audit Report Summary](#8-supplier-audit-report-summary)
+9. [Quality Alert (Internal)](#9-quality-alert-internal)
+10. [Management Review Quality Summary](#10-management-review-quality-summary)
+11. [Regulatory Agency Response (FDA Form 483)](#11-regulatory-agency-response-fda-form-483)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{ncr_number}}` | Non-conformance report number | `NCR-2025-0412` |
+| `{{capa_number}}` | CAPA record number | `CAPA-2025-0023` |
+| `{{scar_number}}` | Supplier corrective action request number | `SCAR-2025-0089` |
+| `{{part_number}}` | Part number and revision | `7832-A Rev D` |
+| `{{part_description}}` | Part description | `Shaft, Output — Titanium` |
+| `{{lot_number}}` | Lot or batch number | `LOT-2025-4471` |
+| `{{po_number}}` | Purchase order number | `PO-2025-08832` |
+| `{{wo_number}}` | Work order number | `WO-2025-1104` |
+| `{{serial_numbers}}` | Affected serial numbers (if applicable) | `SN-10042 through SN-10089` |
+| `{{supplier_name}}` | Supplier company name | `Precision Castings Corp.` |
+| `{{supplier_contact}}` | Supplier quality contact name | `Maria Gonzalez, Quality Manager` |
+| `{{customer_name}}` | Customer company name | `MedTech Instruments Inc.` |
+| `{{customer_contact}}` | Customer quality contact name | `David Chen, Supplier Quality Engineer` |
+| `{{spec_requirement}}` | Specification and requirement violated | `Drawing 7832-A Rev D, Dim A: 12.45 ±0.05mm` |
+| `{{actual_values}}` | Measured values of nonconforming product | `12.52mm, 12.54mm, 12.51mm (3 of 50 sample)` |
+| `{{quantity_affected}}` | Number of parts affected | `18 of 500 pieces inspected` |
+| `{{quantity_total}}` | Total lot quantity | `2,000 pieces` |
+| `{{defect_description}}` | Description of the non-conformance | `OD exceeds USL by 0.02-0.04mm` |
+| `{{containment_status}}` | Current containment actions | `Material quarantined in MRB cage, Bay 3` |
+| `{{our_quality_contact}}` | Internal quality contact | `Sarah Thompson, Quality Engineer` |
+| `{{our_quality_email}}` | Internal quality email | `sthompson@company.com` |
+| `{{our_quality_phone}}` | Internal quality phone | `(555) 234-5678` |
+| `{{our_company}}` | Our company name | `Advanced Manufacturing Solutions` |
+| `{{date_discovered}}` | Date non-conformance was discovered | `2025-03-15` |
+| `{{response_deadline}}` | Deadline for response | `2025-03-25 (10 business days)` |
+| `{{severity_level}}` | NCR severity classification | `Major — Dimensional non-conformance on key characteristic` |
+
+---
+
+## 1. NCR Notification (Internal)
+
+### When to Use
+- Non-conformance identified at incoming inspection, in-process, or final inspection
+- Initial notification to affected departments (manufacturing, engineering, procurement, planning)
+- Material has been quarantined; disposition pending
+
+### Tone Guidance
+Factual and direct. Internal teams need to know what happened, what the scope is, and what the immediate impact is. No blame, no speculation — data only. Include enough detail for engineering to begin their assessment and for planning to evaluate the production impact.
+
+### Template
+
+**Subject:** `{{ncr_number}}: {{part_number}} — {{defect_description}}`
+
+**To:** Manufacturing Engineering, Production Planning, Procurement (if supplier-related), Quality Manager
+**Cc:** Quality file
+
+---
+
+**Non-Conformance Report: {{ncr_number}}**
+
+**Date Discovered:** {{date_discovered}}
+**Discovered By:** {{inspector_name}}, {{inspection_stage}} (incoming / in-process / final)
+**Part Number:** {{part_number}} — {{part_description}}
+**Lot/Batch:** {{lot_number}} | Work Order: {{wo_number}} | PO: {{po_number}} (if incoming)
+
+**Non-Conformance Description:**
+{{defect_description}}
+
+**Specification Requirement:** {{spec_requirement}}
+**Actual Values:** {{actual_values}}
+**Quantity Affected:** {{quantity_affected}} of {{quantity_total}} total lot
+
+**Containment Status:**
+{{containment_status}}
+
+**Initial Scope Assessment:**
+- [ ] Other lots from same supplier/production run checked: {{scope_check_result}}
+- [ ] WIP containing this material identified: {{wip_status}}
+- [ ] Finished goods containing this material identified: {{fg_status}}
+- [ ] Downstream customer shipments containing this material: {{shipped_status}}
+
+**Production Impact:**
+{{production_impact_summary}} (e.g., "Line 3 is waiting on this material for WO-2025-1104; 2-day impact if not dispositioned by Thursday")
+
+**Requested Action:**
+Engineering review of functional impact requested by {{disposition_deadline}}.
+MRB meeting scheduled: {{mrb_date_time}}.
+
+**Quality Contact:** {{our_quality_contact}} | {{our_quality_email}} | {{our_quality_phone}}
+
+---
+
+## 2. MRB Disposition Record
+
+### When to Use
+- Documenting the Material Review Board's disposition decision
+- Required for all NCR dispositions that are not straightforward scrap
+- Audit-trail document; this is what auditors review
+
+### Tone Guidance
+Formal, precise, and complete. This is a controlled document. Every field must be populated. Engineering justification must be technically sound and specific — not "acceptable per engineering review" but a detailed rationale citing functional requirements.
+
+### Template
+
+**MRB DISPOSITION RECORD**
+
+| Field | Value |
+|---|---|
+| NCR Number | {{ncr_number}} |
+| MRB Date | {{mrb_date}} |
+| Part Number / Rev | {{part_number}} |
+| Part Description | {{part_description}} |
+| Lot/Batch | {{lot_number}} |
+| Quantity Affected | {{quantity_affected}} |
+| Nonconformance | {{defect_description}} |
+| Specification Violated | {{spec_requirement}} |
+| Actual Values | {{actual_values}} |
+
+**Disposition Decision:** ☐ Use-As-Is ☐ Rework ☐ Repair ☐ Return to Vendor ☐ Scrap
+
+**Engineering Justification (required for Use-As-Is and Repair):**
+{{engineering_justification}}
+
+Example: "The OD measurement of 12.52mm (USL 12.50mm) exceeds the drawing tolerance by 0.02mm. Per engineering analysis EA-2025-0034, this dimension interfaces with bore ID 12.60 +0.05/-0.00mm on mating part 7833-B. Minimum clearance at worst-case stack-up (shaft 12.52mm, bore 12.60mm) is 0.08mm. Assembly requirement per DWG 100-ASSY-Rev C specifies minimum 0.05mm clearance. The 0.08mm clearance meets the functional requirement. No impact to form, fit, or function."
+
+**Risk Assessment (required for safety-critical parts):**
+{{risk_assessment_reference}} (e.g., "Per ISO 14971 risk assessment RA-2025-0012, risk level is acceptable — severity [minor], probability [remote]")
+
+**Customer Approval (required for aerospace Use-As-Is/Repair):**
+☐ Not required (standard/non-regulated) ☐ Requested — Reference: {{customer_approval_ref}} ☐ Approved — Date: {{approval_date}} ☐ Denied
+
+**Cost Impact:**
+| Item | Amount |
+|---|---|
+| Scrap cost | {{scrap_cost}} |
+| Rework labor | {{rework_cost}} |
+| Re-inspection | {{reinspect_cost}} |
+| Expedite / replacement | {{expedite_cost}} |
+| **Total NCR cost** | **{{total_cost}}** |
+
+**CAPA Required:** ☐ Yes — {{capa_number}} ☐ No — Rationale: {{no_capa_rationale}}
+
+**MRB Attendees and Signatures:**
+
+| Name | Department | Signature | Date |
+|---|---|---|---|
+| {{quality_rep}} | Quality Engineering | | {{date}} |
+| {{engineering_rep}} | Design/Product Engineering | | {{date}} |
+| {{manufacturing_rep}} | Manufacturing Engineering | | {{date}} |
+| {{other_rep}} | {{other_dept}} | | {{date}} |
+
+---
+
+## 3. Corrective Action Request (CAR) to Supplier
+
+### When to Use
+- Significant non-conformance on incoming material traceable to a supplier
+- Repeated minor non-conformances from the same supplier (3+ in 90 days)
+- Supplier escalation Level 1 (SCAR issuance)
+
+### Tone Guidance
+Professional, specific, and structured. Provide all data the supplier needs to investigate. Set clear expectations for the response format and timeline. Do not be accusatory — present the facts and ask for investigation. The supplier's willingness and quality of response will tell you whether this is a fixable issue or a systemic problem.
+
+### What NOT to Say
+- Do not threaten ASL removal in a first-time CAR (save escalation language for Level 2+)
+- Do not speculate on the root cause — that's the supplier's job
+- Do not include internal financial impact numbers (the supplier doesn't need to know your downstream costs at this stage)
+
+### Template
+
+**Subject:** `SCAR-{{scar_number}}: Non-Conformance on PO# {{po_number}} — Response Required by {{response_deadline}}`
+
+**To:** {{supplier_contact}}, {{supplier_name}}
+**Cc:** {{our_quality_contact}}, Procurement buyer
+
+---
+
+**SUPPLIER CORRECTIVE ACTION REQUEST**
+
+**SCAR Number:** {{scar_number}}
+**Date Issued:** {{date_issued}}
+**Response Due:** {{response_deadline}} (initial response with containment + preliminary root cause)
+**Full Corrective Action Plan Due:** {{full_response_deadline}} (30 calendar days)
+
+**Supplier Information:**
+- Supplier: {{supplier_name}}
+- Supplier Code: {{supplier_code}}
+- Contact: {{supplier_contact}}
+
+**Non-Conformance Details:**
+- Part Number: {{part_number}} — {{part_description}}
+- PO Number: {{po_number}}
+- Lot/Batch: {{lot_number}}
+- Quantity Received: {{quantity_total}}
+- Quantity Nonconforming: {{quantity_affected}}
+- Date Received: {{date_received}}
+- Date Non-Conformance Identified: {{date_discovered}}
+
+**Specification Requirement:**
+{{spec_requirement}}
+
+**Actual Results:**
+{{actual_values}}
+
+**Supporting Documentation Attached:**
+- [ ] Inspection report with measurement data
+- [ ] Photographs of nonconforming material
+- [ ] Drawing excerpt highlighting affected dimension/requirement
+- [ ] Copy of your Certificate of Conformance for this lot
+
+**Impact to Our Operations:**
+{{impact_summary}} (e.g., "Production line held pending disposition. Estimated 3-day impact to customer delivery schedule.")
+
+**Required Response (use 8D format or equivalent):**
+1. **Containment actions** — immediate actions to protect our inventory and any other customers who may have received material from the same lot. Confirm whether other lots from the same production run may be affected.
+2. **Root cause analysis** — we require a rigorous root cause investigation, not a surface-level explanation. "Operator error" or "inspection escape" are not acceptable root causes. Identify the systemic process or system failure that allowed this non-conformance.
+3. **Corrective actions** — specific, measurable actions addressing the verified root cause. Include implementation dates and responsible personnel.
+4. **Effectiveness verification plan** — how and when will you verify that the corrective actions are effective?
+
+**Disposition of Nonconforming Material:**
+☐ Return to Vendor — please issue RMA# and shipping instructions
+☐ Sort at our facility — credit memo for sort labor will follow
+☐ Scrap at our facility — credit memo for material value will follow
+
+**Contact for Questions:**
+{{our_quality_contact}} | {{our_quality_email}} | {{our_quality_phone}}
+
+---
+
+## 4. CAPA Initiation Record
+
+### When to Use
+- Formal CAPA initiation based on established trigger criteria
+- Documents the triggering event, scope, team assignment, and initial timeline
+
+### Tone Guidance
+Structured and factual. The initiation record sets the scope and expectations for the entire CAPA. Ambiguity here leads to scope creep or incomplete investigations later. Be specific about what triggered the CAPA and what the expected outcome is.
+
+### Template
+
+**CORRECTIVE AND PREVENTIVE ACTION RECORD**
+
+| Field | Value |
+|---|---|
+| CAPA Number | {{capa_number}} |
+| Date Initiated | {{date_initiated}} |
+| Type | ☐ Corrective ☐ Preventive |
+| Source | ☐ NCR ☐ Customer Complaint ☐ Audit Finding ☐ Trend Analysis ☐ Field Failure ☐ Other: {{other_source}} |
+| Source Reference(s) | {{source_references}} (e.g., NCR-2025-0412, NCR-2025-0398, NCR-2025-0456) |
+| Priority | ☐ Critical (safety/regulatory) ☐ High (customer impact) ☐ Medium (internal) ☐ Low (improvement) |
+
+**Problem Statement:**
+{{problem_statement}}
+
+Example: "Recurring dimensional non-conformance on Part 7832-A Rev D — bore diameter out of tolerance (>USL of 12.50mm). Three NCRs in the last 60 days (NCR-2025-0398, -0412, -0456) affecting lots from three different production runs. Total scrap cost to date: $14,200. No customer impact confirmed, but risk of escape exists based on inspection sampling rates."
+
+**Scope:**
+- Product(s) affected: {{products_affected}}
+- Process(es) affected: {{processes_affected}}
+- Location(s): {{locations_affected}}
+- Period: {{time_period}}
+
+**Team Assignment:**
+
+| Role | Name | Department |
+|---|---|---|
+| CAPA Owner | {{capa_owner}} | {{owner_dept}} |
+| Lead Investigator | {{investigator}} | {{investigator_dept}} |
+| Team Members | {{team_members}} | {{team_depts}} |
+| Management Sponsor | {{sponsor}} | {{sponsor_dept}} |
+
+**Timeline:**
+
+| Phase | Target Date |
+|---|---|
+| Root Cause Investigation Complete | {{rca_target}} |
+| Corrective Action Plan Approved | {{plan_target}} |
+| Implementation Complete | {{implementation_target}} |
+| Effectiveness Verification Start | {{verification_start}} |
+| Effectiveness Verification Complete | {{verification_end}} |
+| CAPA Closure Target | {{closure_target}} |
+
+**Initial Containment Actions (if applicable):**
+{{containment_actions}}
+
+---
+
+## 5. CAPA Effectiveness Review
+
+### When to Use
+- At the end of the effectiveness monitoring period (typically 90 days after implementation)
+- Documents the evidence of effectiveness and the closure/extension decision
+
+### Tone Guidance
+Data-driven and conclusive. The effectiveness review is where the CAPA either closes with evidence of success or reopens with evidence of failure. Auditors specifically review effectiveness evidence — it must be quantitative and linked to the original problem statement.
+
+### Template
+
+**CAPA EFFECTIVENESS REVIEW**
+
+| Field | Value |
+|---|---|
+| CAPA Number | {{capa_number}} |
+| Original Problem | {{problem_statement}} |
+| Root Cause | {{verified_root_cause}} |
+| Corrective Action(s) Implemented | {{corrective_actions}} |
+| Implementation Date | {{implementation_date}} |
+| Monitoring Period | {{monitoring_start}} to {{monitoring_end}} |
+
+**Implementation Verification:**
+- [ ] Work instruction / procedure updated: Rev {{rev}} effective {{date}}
+- [ ] Personnel trained: {{training_records_ref}}
+- [ ] Equipment/fixture installed and validated: {{validation_ref}}
+- [ ] FMEA / Control Plan updated: {{fmea_ref}}
+- [ ] Supplier corrective action verified: {{scar_ref}}
+
+**Effectiveness Data:**
+
+| Metric | Baseline (Pre-CAPA) | Target | Actual (Monitoring Period) | Result |
+|---|---|---|---|---|
+| {{metric_1}} | {{baseline_1}} | {{target_1}} | {{actual_1}} | ☐ Pass ☐ Fail |
+| {{metric_2}} | {{baseline_2}} | {{target_2}} | {{actual_2}} | ☐ Pass ☐ Fail |
+| Recurrence count | {{baseline_recurrence}} | Zero | {{actual_recurrence}} | ☐ Pass ☐ Fail |
+
+**Conclusion:**
+☐ **CAPA Effective — Close.** All effectiveness criteria met. Zero recurrences during monitoring period. Process capability meets target.
+☐ **CAPA Partially Effective — Extend monitoring.** Improvement demonstrated but monitoring period insufficient for definitive conclusion. Extend by {{extension_days}} days.
+☐ **CAPA Not Effective — Reopen.** Recurrence observed during monitoring period. Root cause re-investigation required. See {{reopened_investigation_ref}}.
+
+**Reviewed By:**
+
+| Name | Role | Signature | Date |
+|---|---|---|---|
+| {{reviewer_1}} | CAPA Owner | | |
+| {{reviewer_2}} | Quality Manager | | |
+
+---
+
+## 6. Audit Finding Response
+
+### When to Use
+- Responding to external audit findings (registrar, customer, regulatory)
+- Structure applies to ISO audit NCRs, customer audit CARs, and FDA 483 responses (with modifications per template 11)
+
+### Tone Guidance
+Factual, accountable, and solution-oriented. Accept the finding (even if you disagree with the interpretation — debate the interpretation separately, not in the corrective action response). Demonstrate that you understand the intent of the requirement, not just the words. Auditors value self-awareness and systemic thinking.
+
+### Template
+
+**AUDIT FINDING CORRECTIVE ACTION RESPONSE**
+
+**Audit:** {{audit_type}} (e.g., ISO 9001 Surveillance, Customer Audit, IATF 16949 Recertification)
+**Auditor / Organization:** {{auditor_name}}, {{audit_organization}}
+**Audit Date(s):** {{audit_dates}}
+**Finding Number:** {{finding_number}}
+**Finding Classification:** ☐ Major Non-Conformity ☐ Minor Non-Conformity ☐ Observation / OFI
+
+**Finding Statement:**
+{{finding_statement}}
+
+**Standard Clause Referenced:** {{standard_clause}} (e.g., ISO 9001:2015 §8.5.2, IATF 16949 §10.2.3)
+
+**Our Response:**
+
+**1. Acknowledgment:**
+We acknowledge the finding. {{brief_acknowledgment}}
+
+**2. Root Cause Analysis:**
+{{root_cause_analysis}}
+
+**3. Containment (immediate action taken):**
+{{containment_actions}}
+
+**4. Corrective Action:**
+| Action | Responsible | Target Date | Evidence of Completion |
+|---|---|---|---|
+| {{action_1}} | {{responsible_1}} | {{date_1}} | {{evidence_1}} |
+| {{action_2}} | {{responsible_2}} | {{date_2}} | {{evidence_2}} |
+
+**5. Scope Extension (did we check for similar gaps elsewhere?):**
+{{scope_extension}}
+
+**6. Effectiveness Verification Plan:**
+{{effectiveness_plan}}
+
+**Submitted By:** {{responder_name}}, {{responder_title}}
+**Date:** {{submission_date}}
+
+---
+
+## 7. Customer Quality Notification
+
+### When to Use
+- Non-conformance discovered on product already shipped to the customer
+- Proactive notification — the customer should hear about it from you before they discover it themselves
+
+### Tone Guidance
+Transparent, action-oriented, and structured. Lead with what you know and what you've done (containment), not with excuses. Provide the specific traceability data the customer needs to identify and segregate affected product in their inventory. The customer will judge your quality system based on how you handle this notification — transparency and speed build trust; delay and vagueness destroy it.
+
+### What NOT to Say
+- Do not minimize: "A minor issue was detected" when you don't yet know the scope
+- Do not speculate on root cause: "We believe this was caused by..." without verified data
+- Do not over-promise on timeline: "This will be resolved by Friday" unless you're certain
+
+### Template
+
+**Subject:** `Quality Notification: {{part_number}} — {{defect_description}} — Action Required`
+
+**To:** {{customer_contact}}, {{customer_name}}
+**Cc:** {{our_quality_contact}}, Account Manager
+
+---
+
+**CUSTOMER QUALITY NOTIFICATION**
+
+**Date:** {{date}}
+**Our Reference:** {{ncr_number}}
+**Priority:** {{priority_level}} (Critical / High / Standard)
+
+Dear {{customer_contact}},
+
+We are contacting you to notify you of a quality concern with material we have supplied.
+
+**Affected Product:**
+- Part Number: {{part_number}} — {{part_description}}
+- Lot Number(s): {{lot_numbers}}
+- Serial Number(s): {{serial_numbers}} (if applicable)
+- Ship Date(s): {{ship_dates}}
+- PO/Order Reference(s): {{po_numbers}}
+- Quantity Shipped: {{quantity_shipped}}
+
+**Nature of Non-Conformance:**
+{{defect_description_for_customer}}
+
+**Containment Actions Taken:**
+1. All inventory at our facility has been quarantined and placed on hold
+2. Shipments in transit have been intercepted where possible: {{transit_status}}
+3. We request that you quarantine the following lot(s) in your inventory: {{lots_to_quarantine}}
+
+**Recommended Customer Action:**
+{{recommended_customer_action}} (e.g., "Please segregate and hold the affected lot numbers listed above. Do not use this material until we provide disposition guidance.")
+
+**Investigation Status:**
+We have initiated an investigation ({{ncr_number}}) and are conducting [root cause analysis / containment sort / material verification]. We will provide an updated status by {{next_update_date}}.
+
+**Your Direct Contact:**
+{{our_quality_contact}}
+{{our_quality_email}}
+{{our_quality_phone}}
+
+We take this matter seriously and are committed to full transparency as our investigation progresses. We will provide updates at minimum every {{update_frequency}} until this is resolved.
+
+Sincerely,
+{{our_quality_contact}}, {{our_quality_title}}
+{{our_company}}
+
+---
+
+## 8. Supplier Audit Report Summary
+
+### When to Use
+- Summary of a supplier quality audit (process, system, or product audit)
+- Distributed to procurement, engineering, and supplier quality management
+- Basis for audit follow-up actions
+
+### Tone Guidance
+Objective and balanced. Report what was observed, both strengths and deficiencies. An audit report that is exclusively negative suggests the auditor was looking for problems rather than assessing capability. An audit report that is exclusively positive suggests the auditor wasn't thorough. The summary should give management a clear picture of the supplier's quality maturity.
+
+### Template
+
+**SUPPLIER AUDIT REPORT SUMMARY**
+
+| Field | Value |
+|---|---|
+| Supplier | {{supplier_name}} |
+| Supplier Code | {{supplier_code}} |
+| Audit Type | ☐ System ☐ Process ☐ Product ☐ Combined |
+| Audit Date(s) | {{audit_dates}} |
+| Auditor(s) | {{auditor_names}} |
+| Standard(s) Audited Against | {{standards}} (e.g., ISO 9001:2015, IATF 16949, AS9100D) |
+| Scope | {{audit_scope}} |
+
+**Overall Assessment:** ☐ Approved ☐ Approved with Conditions ☐ Not Approved
+
+**Strengths Observed:**
+1. {{strength_1}}
+2. {{strength_2}}
+3. {{strength_3}}
+
+**Findings:**
+
+| # | Clause | Finding | Classification |
+|---|---|---|---|
+| 1 | {{clause_1}} | {{finding_1}} | Major / Minor / OFI |
+| 2 | {{clause_2}} | {{finding_2}} | Major / Minor / OFI |
+
+**Corrective Action Requirements:**
+- Response due: {{car_deadline}}
+- Format: 8D or equivalent with root cause analysis and implementation plan
+- Submit to: {{submit_to}}
+
+**Recommendations:**
+{{recommendations}} (e.g., "Approve for production with mandatory follow-up audit in 6 months to verify corrective actions. Increase incoming inspection level to tightened until corrective actions verified.")
+
+---
+
+## 9. Quality Alert (Internal)
+
+### When to Use
+- Urgent notification to production floor, inspection, and shipping about a quality issue requiring immediate action
+- Non-conformance that could affect product currently in production or awaiting shipment
+- Temporary enhanced inspection or containment measure
+
+### Tone Guidance
+Urgent, clear, and actionable. This goes to the production floor — operators, supervisors, inspectors. Use plain language. Include photographs if possible. Specify exactly what to do and what to look for. This is not a request for analysis; it's an instruction for immediate action.
+
+### Template
+
+**⚠ QUALITY ALERT ⚠**
+
+**Alert Number:** QA-{{alert_number}}
+**Date Issued:** {{date_issued}}
+**Effective Immediately — Until Rescinded**
+
+**Affected Part(s):** {{part_number}} — {{part_description}}
+**Affected Area(s):** {{production_areas}} (e.g., "Line 3 — CNC Turning, Incoming Inspection, Final Inspection, Shipping")
+
+**Issue:**
+{{issue_description_plain_language}}
+
+**What to Look For:**
+{{what_to_look_for}} (specific, measurable criteria with photographs if available)
+
+**Required Action:**
+1. {{action_1}} (e.g., "100% inspect all WIP on this part number for the affected dimension before releasing to the next operation")
+2. {{action_2}} (e.g., "Segregate and tag any nonconforming parts found — do NOT scrap without Quality Engineering authorization")
+3. {{action_3}} (e.g., "Notify Quality Engineering immediately if any additional nonconforming parts are found: {{contact_info}}")
+
+**This alert remains in effect until:** {{rescind_condition}} (e.g., "written notification from Quality Engineering that the root cause has been addressed and verified")
+
+**Issued By:** {{issuer_name}}, {{issuer_title}}
+
+---
+
+## 10. Management Review Quality Summary
+
+### When to Use
+- Monthly or quarterly management review input on quality performance
+- Summarizes key metrics, significant quality events, CAPA status, and cost of quality
+
+### Tone Guidance
+Executive-level. Lead with the headline — is quality performance improving, stable, or deteriorating? Then provide the supporting data. Managers need to understand trend direction and business impact, not individual NCR details. Use charts and tables; minimize narrative.
+
+### Template
+
+**QUALITY MANAGEMENT REVIEW — {{review_period}}**
+
+**Prepared By:** {{quality_manager}}
+**Date:** {{date}}
+
+**Executive Summary:**
+{{executive_summary}} (2-3 sentences: overall quality trend, most significant event, key action needed)
+
+**Key Performance Indicators:**
+
+| Metric | Target | Prior Period | Current Period | Trend |
+|---|---|---|---|---|
+| Internal defect rate (PPM) | < 1,000 | {{prior_ppm}} | {{current_ppm}} | ↑ ↓ → |
+| Customer complaint rate | < 50/1M units | {{prior_complaints}} | {{current_complaints}} | ↑ ↓ → |
+| Supplier PPM (incoming) | < 500 | {{prior_supplier_ppm}} | {{current_supplier_ppm}} | ↑ ↓ → |
+| NCR closure time (median days) | < 15 | {{prior_ncr_cycle}} | {{current_ncr_cycle}} | ↑ ↓ → |
+| CAPA on-time closure rate | > 90% | {{prior_capa_otc}} | {{current_capa_otc}} | ↑ ↓ → |
+| Cost of quality (% revenue) | < 3% | {{prior_coq}} | {{current_coq}} | ↑ ↓ → |
+
+**Significant Quality Events:**
+1. {{event_1}}
+2. {{event_2}}
+
+**CAPA Status:**
+
+| Status | Count |
+|---|---|
+| Open — On Track | {{on_track}} |
+| Open — Overdue | {{overdue}} |
+| Closed This Period | {{closed}} |
+| Effectiveness Verified | {{verified}} |
+
+**Top Suppliers by PPM (worst 5):**
+
+| Supplier | PPM | Trend | Current Escalation Level |
+|---|---|---|---|
+| {{supplier_1}} | {{ppm_1}} | ↑ ↓ → | {{level_1}} |
+| {{supplier_2}} | {{ppm_2}} | ↑ ↓ → | {{level_2}} |
+
+**Cost of Quality Breakdown:**
+
+| Category | Amount | % of Revenue |
+|---|---|---|
+| Prevention | {{prevention_cost}} | {{prevention_pct}} |
+| Appraisal | {{appraisal_cost}} | {{appraisal_pct}} |
+| Internal Failure | {{internal_failure_cost}} | {{internal_pct}} |
+| External Failure | {{external_failure_cost}} | {{external_pct}} |
+| **Total COQ** | **{{total_coq}}** | **{{total_coq_pct}}** |
+
+**Actions Required from Management:**
+1. {{action_request_1}} (e.g., "Approve capital expenditure for automated inspection system — ROI analysis attached")
+2. {{action_request_2}} (e.g., "Decision needed on Supplier X escalation to Level 3 / alternate source qualification")
+
+---
+
+## 11. Regulatory Agency Response (FDA Form 483)
+
+### When to Use
+- Formal response to FDA Form 483 observations
+- Due within 15 business days of receiving the 483
+- This is a critical document — it becomes part of the public FDA inspection record
+
+### Tone Guidance
+Respectful, thorough, and accountable. Acknowledge each observation. Do not argue, minimize, or blame individuals. Demonstrate that you understand the intent of the regulations, not just the words. FDA reviewers specifically evaluate whether your response addresses the systemic issue, not just the specific observation.
+
+### What NOT to Say
+- "We disagree with this observation" — address it even if you disagree
+- "This was an isolated incident" — FDA explicitly looks for systemic issues
+- "Employee has been terminated" — this is punitive, not corrective; FDA wants system fixes
+- "We will address this" without specific actions, dates, and responsible parties
+
+### Template
+
+**[Company Letterhead]**
+
+{{date}}
+
+{{fda_district_director_name}}
+Director, {{fda_district_office}}
+Food and Drug Administration
+{{fda_address}}
+
+**Re: Response to FDA Form 483 Inspectional Observations**
+**Establishment:** {{facility_name_address}}
+**FEI Number:** {{fei_number}}
+**Inspection Dates:** {{inspection_dates}}
+**Investigator:** {{investigator_name}}
+
+Dear {{fda_district_director_name}},
+
+{{our_company}} appreciates the opportunity to respond to the observations identified during the FDA inspection of our {{facility_name}} facility conducted {{inspection_dates}}. We take these observations seriously and have initiated corrective actions as described below.
+
+---
+
+**Observation {{obs_number}}:**
+"{{verbatim_483_observation}}"
+
+**Response:**
+
+**Acknowledgment:**
+{{acknowledgment}} (e.g., "We acknowledge that our procedure QP-4401 did not adequately address...")
+
+**Investigation:**
+{{investigation_summary}} (What we investigated, what we found, root cause)
+
+**Corrective Action:**
+
+| Action | Description | Responsible | Target Date | Status |
+|---|---|---|---|---|
+| 1 | {{action_1_description}} | {{responsible_1}} | {{date_1}} | {{status_1}} |
+| 2 | {{action_2_description}} | {{responsible_2}} | {{date_2}} | {{status_2}} |
+
+**Scope Extension:**
+{{scope_extension}} (e.g., "We reviewed all similar procedures across our facility and identified two additional areas where the same gap existed. These have been corrected as part of actions 3 and 4 above.")
+
+**Effectiveness Verification:**
+{{effectiveness_plan}} (e.g., "We will monitor the effectiveness of these corrective actions over a 90-day period by tracking [specific metric]. Evidence of effectiveness will be available for review upon request.")
+
+**Evidence Attached:** {{list_of_evidence}}
+
+---
+
+[Repeat for each observation]
+
+---
+
+We are committed to maintaining full compliance with 21 CFR Part 820 and to the continuous improvement of our quality management system. We welcome the opportunity to discuss these responses or to provide additional information.
+
+Sincerely,
+
+{{signatory_name}}
+{{signatory_title}}
+{{our_company}}
+{{contact_information}}
+
+Enclosures: {{list_of_enclosures}}
diff --git a/skills/quality-nonconformance/references/decision-frameworks.md b/skills/quality-nonconformance/references/decision-frameworks.md
new file mode 100644
index 00000000..a2185ef8
--- /dev/null
+++ b/skills/quality-nonconformance/references/decision-frameworks.md
@@ -0,0 +1,769 @@
+# Decision Frameworks — Quality & Non-Conformance Management
+
+This reference provides the detailed decision logic, MRB processes, RCA methodology selection,
+CAPA lifecycle management, SPC interpretation workflows, inspection level determination,
+supplier quality escalation, and cost of quality calculation models for regulated manufacturing
+quality engineering.
+
+All thresholds, regulatory references, and process expectations reflect quality engineering
+practice across FDA 21 CFR 820, IATF 16949, AS9100, and ISO 13485 environments.
+
+---
+
+## 1. NCR Disposition Decision Trees
+
+### 1.1 Universal Disposition Flow
+
+Every non-conformance, regardless of regulatory environment, begins with this decision sequence.
+The flow terminates at the first applicable disposition; do not skip levels.
+
+```
+START: Non-conformance identified and documented
+ │
+ ├─ Is the part safety-critical or regulatory-controlled?
+ │ ├─ YES → Can it be reworked to FULL conformance?
+ │ │ ├─ YES → REWORK with approved procedure + 100% re-inspection
+ │ │ └─ NO → SCRAP (no use-as-is permitted without formal risk assessment
+ │ │ AND regulatory/customer approval)
+ │ └─ NO → Continue
+ │
+ ├─ Does the non-conformance affect form, fit, or function?
+ │ ├─ YES → Can it be reworked to full conformance?
+ │ │ ├─ YES → Is rework cost < 60% of replacement cost?
+ │ │ │ ├─ YES → REWORK
+ │ │ │ └─ NO → SCRAP (rework is not economical)
+ │ │ └─ NO → Can it be repaired to acceptable function?
+ │ │ ├─ YES → REPAIR with engineering concession + customer
+ │ │ │ approval (if required by contract/standard)
+ │ │ └─ NO → SCRAP
+ │ └─ NO → Continue
+ │
+ ├─ Is the non-conformance cosmetic only?
+ │ ├─ YES → Does customer spec address cosmetic requirements?
+ │ │ ├─ YES → Does the part meet customer cosmetic spec?
+ │ │ │ ├─ YES → USE-AS-IS with documentation
+ │ │ │ └─ NO → Customer concession required → If granted: USE-AS-IS
+ │ │ │ → If denied: REWORK or SCRAP
+ │ │ └─ NO → USE-AS-IS with engineering sign-off
+ │ └─ NO → Continue
+ │
+ ├─ Is this a dimensional non-conformance within material review authority?
+ │ ├─ YES → Engineering analysis: does the dimension affect assembly or performance?
+ │ │ ├─ YES → REWORK or SCRAP (depending on feasibility)
+ │ │ └─ NO → USE-AS-IS with documented engineering justification
+ │ └─ NO → Continue
+ │
+ └─ Is this a supplier-caused non-conformance?
+ ├─ YES → Is the material needed immediately for production?
+ │ ├─ YES → Sort/rework at supplier's cost + USE acceptable units
+ │ │ + SCAR to supplier + debit memo for sort/rework cost
+ │ └─ NO → RETURN TO VENDOR with SCAR + debit memo or replacement PO
+ └─ NO → Evaluate per the functional impact path above
+```
+
+### 1.2 FDA-Regulated Environment (21 CFR 820 / ISO 13485) Specific Logic
+
+Medical device non-conformances carry additional requirements:
+
+**Pre-Market (Design/Development):**
+- Non-conformances during design verification/validation must be documented in the Design History File (DHF)
+- Disposition must consider risk per ISO 14971 — severity and probability of harm to the patient
+- Use-as-is is rarely acceptable for a design non-conformance; it implies the design intent is wrong
+- CAPA is almost always required to prevent recurrence in production
+
+**Post-Market (Production/Field):**
+- Non-conformances that could affect device safety or performance require evaluation for field action (recall, correction, removal) per 21 CFR 806
+- The threshold is low: if there is any reasonable possibility of harm, evaluate formally
+- Document the decision NOT to file a field action as rigorously as the decision to file one
+- Complaint-related non-conformances must be linked to complaint records per 820.198
+- MDR (Medical Device Report) obligations: death or serious injury must be reported to FDA within 30 calendar days (5 days for events requiring remedial action)
+
+**Disposition Authority Matrix:**
+
+| Disposition | Who Can Authorize | Additional Requirements |
+|---|---|---|
+| Scrap | Quality Engineer or above | Documented with lot traceability |
+| Rework | Quality Engineer + Manufacturing Engineering | Approved rework procedure; re-inspect to original spec |
+| Repair | MRB (Quality + Engineering + Manufacturing) | Risk assessment per ISO 14971; update DHF if design-related |
+| Use-As-Is | MRB + Design Authority | Risk assessment; documented justification; regulatory impact evaluation |
+| RTV | Quality Engineer + Procurement | SCAR required; supplier re-qualification if repeated |
+
+### 1.3 Automotive Environment (IATF 16949) Specific Logic
+
+**Customer Notification Requirements:**
+- Any non-conformance on product shipped to the customer: notification within 24 hours of discovery
+- Any process change affecting fit, form, function, or performance: PPAP resubmission required
+- Use-as-is disposition: typically requires a formal deviation request to the customer through their supplier portal (e.g., GM's GQTS, Ford's MQAS, Stellantis' SQP)
+- Customer may accept, reject, or accept with conditions (reduced quantity, time-limited deviation)
+
+**Control Plan Integration:**
+- When a non-conformance reveals a gap in the control plan, the control plan must be updated as part of the corrective action
+- Special characteristics (safety/significant characteristics identified with shield or diamond symbols) have zero tolerance for non-conformance: 100% containment and immediate CAPA
+- The reaction plan column of the control plan specifies the predetermined response — follow it first, then investigate
+
+**Controlled Shipping Levels:**
+- **CS-1 (Internal Controlled Shipping):** Supplier adds an additional inspection/sort step beyond normal controls and submits inspection data with each shipment
+- **CS-2 (External Controlled Shipping):** Third-party inspection at supplier's facility, at supplier's cost, with direct reporting to customer quality
+- CS-1 and CS-2 are distinct from the general supplier escalation ladder — they are customer-mandated containment measures, not supplier-initiated improvements
+
+### 1.4 Aerospace Environment (AS9100) Specific Logic
+
+**Customer/Authority Approval:**
+- Use-as-is and repair dispositions ALWAYS require customer approval per AS9100 §8.7.1
+- If the customer is a prime contractor working under a government contract, the government quality representative (DCMA or equivalent) may also need to approve
+- Non-conformances on parts with key characteristics require notification to the design authority
+- First Article Inspection (FAI) per AS9102 becomes invalid if a non-conformance indicates the process has changed from the qualified state — partial or full FAI resubmission may be required
+
+**Counterfeit Part Prevention:**
+- If a non-conformance raises suspicion of counterfeit material (unexpected material composition, incorrect markings, suspect documentation), invoke the counterfeit prevention procedure per AS9100 §8.1.4
+- Quarantine the suspect material in a separate area from other MRB material
+- Report to GIDEP (Government-Industry Data Exchange Program) if counterfeit is confirmed
+- Do not return suspect counterfeit material to the supplier — it must be quarantined and may need to be retained as evidence
+
+**Traceability Requirements:**
+- Aerospace non-conformances must maintain lot, batch, heat, and serial number traceability throughout the disposition process
+- Scrap disposition must include documented destruction of serialized parts to prevent re-entry into the supply chain
+- OASIS database updates may be required for supplier quality events
+
+---
+
+## 2. Root Cause Analysis Methodology Selection Guide
+
+### 2.1 Selection Decision Matrix
+
+| Factor | 5 Whys | Ishikawa + 5 Whys | 8D | Fault Tree Analysis |
+|---|---|---|---|---|
+| **Best for** | Single-event, linear cause chain | Multi-factor, need to explore categories | Recurring issue, team-based resolution | Safety-critical, quantitative risk needed |
+| **Effort (hours)** | 1–2 | 4–8 | 20–40 (across all D-steps) | 40–80 |
+| **Team size** | 1–2 people | 2–4 people | 5–8 cross-functional | 3–6 subject matter experts |
+| **When required** | Internal process investigations | Complex non-conformances | Customer mandate (automotive OEMs) | Aerospace product safety; medical device risk analysis |
+| **Limitation** | Assumes single linear chain | Still qualitative; hypothesis-driven | Heavyweight for simple issues | Resource-intensive; requires failure rate data for quantitative mode |
+| **Output** | Root cause statement | Categorized cause hypotheses with verified root cause | Full 8D report (D0-D8) | Fault tree diagram with probability assignments |
+
+### 2.2 The 5 Whys: When It Works and When It Doesn't
+
+**5 Whys works well when:**
+- The failure is a single event with a clear before/after state change
+- Each "why" can be verified with data (measurement, observation, record review)
+- The causal chain does not branch — there is a single dominant cause
+- The investigation can reach a systemic cause (process, system, or design issue) within 5 iterations
+
+**5 Whys fails when:**
+- Multiple independent causes interact to produce the failure (combinatorial causes)
+- The analyst stops at "human error" or "operator mistake" — this is never a root cause
+- Each "why" is answered with opinion rather than verified data
+- The analysis becomes circular (Why A? Because B. Why B? Because A.)
+- Organizational pressure drives toward a "convenient" root cause that avoids systemic change
+
+**Verification protocol for each "why" level:**
+
+| Why Level | Question | Acceptable Evidence | Unacceptable Evidence |
+|---|---|---|---|
+| Why 1 (Event) | What physically happened? | Measurement data, photographs, inspection records | "The part was bad" |
+| Why 2 (Condition) | What condition allowed it? | Process parameter logs, tool condition records | "The operator didn't check" |
+| Why 3 (Process) | Why did the process permit this condition? | Work instruction review, process FMEA gap | "It's always been done this way" |
+| Why 4 (System) | Why didn't the system prevent the process gap? | System audit evidence, training records, control plan review | "We need better training" |
+| Why 5 (Management) | Why was the system gap undetected? | Management review records, resource allocation evidence, risk assessment gaps | "Management doesn't care about quality" |
+
+### 2.3 Ishikawa Diagram: 6M Framework Deep Dive
+
+For each M category, specific investigation questions that separate thorough analysis from checkbox exercises:
+
+**Man (Personnel):**
+- Was the operator trained AND certified on this specific operation?
+- When was the most recent certification renewal?
+- Was this the operator's normal workstation or were they cross-trained/temporary?
+- Was the shift staffing at normal levels or was this during overtime/short-staffing?
+- Check operator error rate data — is this an isolated event or a pattern for this individual?
+
+**Machine (Equipment):**
+- When was the last preventive maintenance performed (date AND what was done)?
+- Is the machine within its calibration cycle for all measuring functions?
+- Were any alarms, warnings, or parameter drifts logged before the event?
+- Has the machine been modified, repaired, or had a tooling change recently?
+- Check the machine's historical Cpk trend — has capability been declining?
+
+**Material:**
+- Is this a new lot of raw material? When did the lot change?
+- Were incoming inspection results within normal range, or marginal-pass?
+- Does the material certificate match what was physically received (heat number, mill, composition)?
+- Has the material been stored correctly (temperature, humidity, shelf life, FIFO rotation)?
+- Were any material substitutions or equivalents authorized?
+
+**Method (Process):**
+- Is the work instruction current revision? When was it last revised?
+- Does the operator actually follow the work instruction as written (observation, not assumption)?
+- Were any process parameters changed recently (speeds, feeds, temperatures, pressures, cure times)?
+- Was an engineering change order (ECO) recently implemented on this part or process?
+- Is there a gap between the documented method and the actual method (tribal knowledge)?
+
+**Measurement:**
+- Was the measurement system used for this inspection validated (Gauge R&R)?
+- Is the gauge within calibration? Check both certificate and physical condition.
+- Was the correct measurement method used (per the control plan or inspection instruction)?
+- Did the measurement environment (temperature, vibration, lighting) affect the result?
+- For attribute inspections (go/no-go, visual): what is the inspection effectiveness rate?
+
+**Mother Nature (Environment):**
+- Were ambient conditions (temperature, humidity) within process specification?
+- Were there any environmental events (power fluctuation, compressed air pressure drop, vibration from construction)?
+- Is there a shift-to-shift or day-to-day correlation in the data (temperature cycling, humidity changes)?
+- Was the factory HVAC system operating normally?
+- For cleanroom or controlled environment processes: were environmental monitoring logs within specification?
+
+### 2.4 8D Methodology: Detailed Gate Requirements
+
+Each D-step has specific outputs required before advancing. Skipping gates creates 8Ds that look complete but don't actually solve the problem.
+
+| D-Step | Name | Required Output | Common Failure Mode |
+|---|---|---|---|
+| D0 | Symptom & Emergency Response | Emergency response actions taken; containment effectiveness confirmed | Confusing containment with corrective action |
+| D1 | Team Formation | Cross-functional team with defined roles; includes process owner and subject matter expert | Team is all quality, no manufacturing or engineering |
+| D2 | Problem Definition | IS/IS NOT analysis completed; problem quantified with data (defect rate, PPM, Cpk shift, complaint count) | Problem statement is too broad ("quality issues") or just restates the symptom |
+| D3 | Interim Containment | Actions to protect customer while investigation proceeds; effectiveness verified (inspection data post-containment) | Containment is "100% inspection" without verifying inspection effectiveness through known-defective challenge |
+| D4 | Root Cause | Root cause(s) verified through data analysis or designed experiment; escapes the "human error" trap | Root cause = restatement of problem; no verification data; stops at symptoms |
+| D5 | Corrective Action Selection | Actions address verified root cause; mistake-proofing (poka-yoke) preferred over procedural controls | Corrective action = "retrain operators" or "add inspection step" (both are weak) |
+| D6 | Implementation | Actions implemented with documented evidence (updated WI, installed fixture, modified process); baseline performance established | Implementation date = planned date, not actual; no evidence of implementation |
+| D7 | Prevention | Systemic actions to prevent recurrence across similar processes/products; lessons learned documented; FMEA updated | D7 is copy-paste of D5; no horizontal deployment; FMEA not updated |
+| D8 | Recognition | Team acknowledged; 8D closed with effectiveness data | Closed without effectiveness data; team not recognized |
+
+### 2.5 Fault Tree Analysis: Construction Methodology
+
+**Step 1: Define the Top Event**
+- State the undesired event in specific, measurable terms
+- Example: "Shaft diameter exceeds USL of 25.05mm on finished machined part"
+- Not: "Bad parts" or "Quality problem"
+
+**Step 2: Identify Immediate Causes (Level 1)**
+- What must be true for the top event to occur?
+- Use AND gates (all causes must be present) and OR gates (any single cause is sufficient)
+- Example: "Shaft OD too large" can be caused by (OR gate): tool wear, incorrect tool offset, material oversize, thermal expansion, fixture misalignment
+
+**Step 3: Decompose Each Cause (Levels 2–N)**
+- For each Level 1 cause, ask: what causes this?
+- Continue decomposing until you reach basic events (events with known failure rates or that cannot be further decomposed)
+- Example: "Tool wear" caused by (AND gate): extended run time + inadequate tool change interval + no in-process SPC alert
+
+**Step 4: Quantify (when data is available)**
+- Assign probability values to basic events using historical data, MTBF data, or engineering estimates
+- Calculate top event probability through the gate logic
+- Identify the minimal cut sets (smallest combinations of basic events that cause the top event)
+- Focus corrective actions on the highest-probability cut sets
+
+---
+
+## 3. CAPA Writing and Verification Framework
+
+### 3.1 CAPA Initiation Criteria
+
+**Always initiate CAPA for:**
+- Repeat non-conformance: same failure mode occurring 3+ times in 12 months
+- Customer complaint involving product performance, safety, or regulatory compliance
+- External audit finding (FDA, notified body, customer, registrar)
+- Field failure or product return
+- Trend signal: SPC control chart out-of-control pattern (not isolated point)
+- Regulatory requirement change affecting existing products/processes
+- Post-market surveillance data indicating potential safety concern
+
+**Consider CAPA (judgment call) for:**
+- Repeat non-conformance: same failure mode 2 times in 12 months
+- Internal audit finding of moderate significance
+- Supplier non-conformance with systemic indicators
+- Near-miss event (non-conformance caught before reaching customer)
+- Process deviation from validated parameters without product impact
+
+**Do NOT initiate CAPA for:**
+- Isolated non-conformance with clear, non-recurring cause (one-off tool breakage, power outage)
+- Non-conformance fully addressed by NCR disposition with no systemic implication
+- Customer cosmetic preference that doesn't violate any specification
+- Minor documentation errors caught and corrected within the same day
+
+### 3.2 CAPA Action Hierarchy (Effectiveness Ranking)
+
+Corrective actions are not created equal. Rank by effectiveness and default to the highest feasible level:
+
+| Rank | Control Type | Example | Effectiveness | Typical Cost |
+|---|---|---|---|---|
+| 1 | **Elimination** | Redesign to remove the failure mode entirely | ~100% | High (design change, tooling) |
+| 2 | **Substitution** | Change material, supplier, or process to one that cannot produce the failure | ~95% | Medium-High |
+| 3 | **Engineering Controls (Poka-Yoke)** | Fixture that physically prevents incorrect assembly; sensor that stops machine on out-of-spec condition | ~90% | Medium |
+| 4 | **Detection Controls** | Automated inspection (vision system, laser gauge) that 100% inspects and auto-rejects | ~85% | Medium |
+| 5 | **Administrative Controls** | Updated work instruction, revised procedure, checklist | ~50-60% | Low |
+| 6 | **Training** | Operator retraining on existing procedure | ~30-40% | Low |
+
+If your corrective action is ranked 5 or 6 and a rank 1-4 action is feasible, the CAPA will likely be challenged by auditors. Training alone is never an adequate corrective action for a significant non-conformance.
+
+### 3.3 CAPA Effectiveness Verification Protocol
+
+**Phase 1: Implementation Verification (within 2 weeks of target date)**
+
+| Evidence Required | What to Check | Acceptable | Not Acceptable |
+|---|---|---|---|
+| Document revision | Was the WI/procedure updated to reflect the change? | Revision with effective date and training records | "Will be updated in next revision" |
+| Physical verification | Is the fixture/tool/sensor installed and operational? | Photograph + validation record | Purchase order placed but not installed |
+| Training completion | Were affected personnel trained? | Signed training records with competency assessment | Email sent to team |
+| System update | Were QMS documents, FMEA, control plan updated? | Updated documents with revision and approval | "Will update during next review" |
+
+**Phase 2: Effectiveness Validation (90-day monitoring period)**
+
+| Metric | Calculation | Pass Criteria | Fail Criteria |
+|---|---|---|---|
+| Recurrence rate | Count of same failure mode in monitoring period | Zero recurrences | Any recurrence |
+| Related failure rate | Count of related failure modes in same process | No increase from baseline | Increase suggests incomplete root cause |
+| Process capability | Cpk or Ppk for the affected characteristic | Cpk ≥ 1.33 (or target value) | Cpk below pre-CAPA level |
+| Customer feedback | Complaints related to the addressed failure mode | Zero related complaints | Any related complaint |
+
+**Phase 3: Closure Decision**
+
+| Condition | Decision |
+|---|---|
+| Phase 1 complete + Phase 2 pass criteria met | Close CAPA |
+| Phase 1 complete + Phase 2 shows improvement but not full elimination | Extend monitoring period by 60 days; if still improving, close with condition |
+| Phase 1 complete + Phase 2 shows no improvement | Reopen CAPA; root cause was incorrect or action insufficient |
+| Phase 1 incomplete (action not implemented) | CAPA remains open; escalate for resource allocation |
+| Recurrence during monitoring | Reopen CAPA; do NOT close and open new CAPA for same issue |
+
+### 3.4 CAPA Timeliness Standards
+
+| CAPA Phase | Target Timeline | Regulatory Expectation |
+|---|---|---|
+| Initiation and assignment | Within 5 business days of trigger | FDA: "timely" — typically within 30 days of awareness |
+| Investigation and root cause | Within 30 calendar days | IATF 16949: per customer timeline (often 10-day initial response) |
+| Corrective action plan | Within 45 calendar days | AS9100: per contractual agreement |
+| Implementation | Within 90 calendar days | Varies by complexity; document delays with justification |
+| Effectiveness verification start | Immediately after implementation | Must be defined at initiation |
+| Effectiveness verification completion | 90 days after implementation | FDA: must demonstrate effectiveness, not just implementation |
+| CAPA closure | Within 180 calendar days of initiation (total) | FDA warning letters cite CAPAs open > 1 year as systemic failure |
+
+---
+
+## 4. SPC Interpretation Decision Logic
+
+### 4.1 Control Chart Selection Flowchart
+
+```
+START: What type of data are you charting?
+ │
+ ├─ CONTINUOUS (variable) data — measurements in units (mm, kg, °C, psi)
+ │ ├─ Are you taking subgroups (multiple measurements per sampling event)?
+ │ │ ├─ YES → What is the subgroup size (n)?
+ │ │ │ ├─ n = 2 to 9 → X-bar / R chart
+ │ │ │ ├─ n = 10 to 25 → X-bar / S chart
+ │ │ │ └─ n > 25 → X-bar / S chart (consider reducing subgroup size)
+ │ │ └─ NO (n=1, individual readings) → Individuals / Moving Range (I-MR) chart
+ │ │ Use when: batch process, destructive testing, slow process,
+ │ │ or when each unit is unique
+ │ └─ (Verify data normality assumption for variable charts — I-MR is sensitive
+ │ to non-normality; consider transformation or use nonparametric alternatives)
+ │
+ └─ ATTRIBUTE (discrete) data — counts or proportions
+ ├─ Are you counting DEFECTIVE ITEMS (units that pass or fail)?
+ │ ├─ YES → Is the sample size constant?
+ │ │ ├─ YES → np-chart (count of defectives, fixed sample)
+ │ │ └─ NO → p-chart (proportion defective, variable sample)
+ │ └─ NO → You're counting DEFECTS (multiple defects possible per unit)
+ │ ├─ Is the inspection area/opportunity constant?
+ │ │ ├─ YES → c-chart (count of defects per unit, fixed area)
+ │ │ └─ NO → u-chart (defects per unit, variable area)
+ │ └─ (Verify Poisson assumption for c/u charts)
+ └─ (Attribute charts require larger sample sizes than variable charts for
+ equivalent sensitivity — minimum ~50 for p/np, ~25 for c/u)
+```
+
+### 4.2 Out-of-Control Response Protocol
+
+When a control chart signals an out-of-control condition, follow this response based on the specific signal:
+
+**Rule 1: Point beyond 3σ control limit**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Immediate | Stop process if product is being produced; quarantine output since last known good point | Within minutes |
+| Investigation | Identify the assignable cause — what changed? Check 6M categories systematically | Within 4 hours |
+| Containment | Sort/inspect product produced during the out-of-control period | Within 1 shift |
+| Correction | Address the assignable cause and restart production with increased monitoring | Before next production run |
+| Documentation | NCR if product was affected; update control chart with annotation | Within 24 hours |
+
+**Rule 2: Nine consecutive points on one side of the center line (run)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | Process mean has likely shifted. Check for: tool wear progression, material lot change, environmental drift, measurement calibration shift | Within 1 shift |
+| Adjustment | If assignable cause found: correct. If no assignable cause found and process is still within spec, continue monitoring but increase sampling frequency | Within 24 hours |
+| Recalculation | If the shift is intentional (process improvement) or represents a new process level, recalculate control limits with new data | After 25+ subgroups at new level |
+
+**Rule 3: Six consecutive points steadily increasing or decreasing (trend)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | Process is drifting. Most common causes: tool wear, chemical depletion, thermal drift, filter degradation | Within 1 shift |
+| Projection | At the current drift rate, when will the process exceed the specification limit? This determines urgency | Immediate calculation |
+| Preemptive action | Adjust the process (tool change, chemical replenishment) BEFORE it reaches the spec limit | Before projected spec limit crossing |
+
+**Rule 4: Fourteen consecutive points alternating up and down (stratification/mixing)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | This pattern indicates over-control (tampering), two alternating streams (e.g., two spindles, two cavities), or systematic measurement error | Within 24 hours |
+| Verification | Check if the subgroup data is being collected from multiple sources that should be charted separately | Within 48 hours |
+| Stratification | If data is from multiple streams, create separate charts for each stream | Within 1 week |
+
+### 4.3 Capability Index Interpretation
+
+| Cpk Value | Interpretation | Action Required |
+|---|---|---|
+| Cpk ≥ 2.00 | Six Sigma capable; consider reducing inspection frequency | Maintain controls; candidate for reduced inspection or skip-lot |
+| 1.67 ≤ Cpk < 2.00 | Highly capable; exceeds most customer requirements | Standard monitoring; meets IATF 16949 requirements for new processes |
+| 1.33 ≤ Cpk < 1.67 | Capable; meets most industry standards | Standard SPC monitoring; meets IATF 16949 minimum for production |
+| 1.00 ≤ Cpk < 1.33 | Marginally capable; producing some defects | Increase monitoring frequency; initiate process improvement; customer notification may be required |
+| 0.67 ≤ Cpk < 1.00 | Not capable; significant defect production | 100% inspection until process is improved; CAPA required; customer notification required |
+| Cpk < 0.67 | Severely incapable | Stop production; sort all WIP and finished goods; engineering review of process and specification |
+
+**Cp vs. Cpk Interpretation:**
+
+| Condition | Meaning | Action |
+|---|---|---|
+| Cp high, Cpk high | Process is both capable and centered | Optimal state; maintain |
+| Cp high, Cpk low | Process has low variation but is not centered on the target | Adjust the process mean; do NOT reduce variation (it's already good) |
+| Cp low, Cpk low | Process has too much variation, possibly also off-center | Reduce variation first (fundamental process improvement), then center |
+| Cp low, Cpk ≈ Cp | Process has too much variation but is centered | Reduce variation; centering is not the issue |
+
+**Pp/Ppk vs. Cp/Cpk:**
+
+| Index | Uses | Represents | When to Use |
+|---|---|---|---|
+| Cp/Cpk | Within-subgroup variation (σ_within) | Short-term or "potential" capability | Evaluating process potential when in statistical control |
+| Pp/Ppk | Overall variation (σ_overall) including between-subgroup shifts | Long-term or "actual" performance | Evaluating what the customer actually receives over time |
+| Pp/Ppk < Cp/Cpk (common) | Process mean is shifting between subgroups | Between-subgroup variation is significant | Investigate what's causing the mean to shift between subgroups |
+| Pp/Ppk ≈ Cp/Cpk | Process is stable over time | Minimal between-subgroup variation | Process is well-controlled; long-term performance matches potential |
+
+---
+
+## 5. Inspection Level Determination
+
+### 5.1 Incoming Inspection Level Decision Matrix
+
+| Factor | Points |
+|---|---|
+| **Supplier History** | |
+| New supplier (< 5 lots received) | 5 |
+| Supplier on probation/watch | 5 |
+| Qualified supplier with PPM 1,000-5,000 | 3 |
+| Qualified supplier with PPM 500-1,000 | 2 |
+| Qualified supplier with PPM < 500 | 1 |
+| Preferred supplier with PPM < 100 | 0 |
+| **Part Criticality** | |
+| Safety-critical characteristic | 5 |
+| Key characteristic (fit/function) | 3 |
+| Standard characteristic | 1 |
+| Cosmetic only | 0 |
+| **Regulatory Requirement** | |
+| FDA/medical device requiring incoming inspection | 5 |
+| Aerospace with special process (NADCAP) | 4 |
+| Automotive with customer-designated special characteristic | 3 |
+| Standard ISO 9001 environment | 1 |
+| **Recent Quality History (last 6 months)** | |
+| NCR issued against this part/supplier combination | +3 |
+| Customer complaint traced to this component | +4 |
+| SCAR currently open against this supplier | +3 |
+| No quality issues | 0 |
+
+**Inspection Level Assignment:**
+
+| Total Points | Inspection Level | Typical Approach |
+|---|---|---|
+| 0–3 | Reduced / Skip-Lot | CoC review + skip-lot verification (every 3rd or 5th lot) |
+| 4–7 | Normal (AQL Level II) | Standard AQL sampling per ANSI/ASQ Z1.4 |
+| 8–11 | Tightened (AQL Level III) | Tightened sampling or increased sample size |
+| 12+ | 100% / Full Inspection | 100% inspection of critical characteristics |
+
+### 5.2 ANSI/ASQ Z1.4 Quick Reference
+
+**Sample Size Code Letters (Normal Inspection, General Level II):**
+
+| Lot Size | Code Letter | Sample Size (AQL 1.0) |
+|---|---|---|
+| 2–8 | A | 2 (Ac=0, Re=1) |
+| 9–15 | B | 3 (Ac=0, Re=1) |
+| 16–25 | C | 5 (Ac=0, Re=1) |
+| 26–50 | D | 8 (Ac=0, Re=1) |
+| 51–90 | E | 13 (Ac=1, Re=2) |
+| 91–150 | F | 20 (Ac=1, Re=2) |
+| 151–280 | G | 32 (Ac=2, Re=3) |
+| 281–500 | H | 50 (Ac=3, Re=4) |
+| 501–1,200 | J | 80 (Ac=5, Re=6) |
+| 1,201–3,200 | K | 125 (Ac=7, Re=8) |
+| 3,201–10,000 | L | 200 (Ac=10, Re=11) |
+| 10,001–35,000 | M | 315 (Ac=14, Re=15) |
+| 35,001–150,000 | N | 500 (Ac=21, Re=22) |
+
+**Switching Rules:**
+
+| Current Level | Switch Condition | Switch To |
+|---|---|---|
+| Normal | 2 of 5 consecutive lots rejected | Tightened |
+| Normal | 10 consecutive lots accepted AND production at steady rate AND approved by responsible authority | Reduced |
+| Tightened | 5 consecutive lots accepted | Normal |
+| Tightened | 10 consecutive lots not accepted | Discontinue inspection; require supplier corrective action |
+| Reduced | 1 lot rejected | Normal |
+| Reduced | Production irregular or other conditions warrant | Normal |
+
+### 5.3 Skip-Lot Qualification Requirements
+
+**Qualification Criteria (all must be met):**
+1. Supplier is on the Approved Supplier List with "preferred" or "qualified" status
+2. Minimum 10 consecutive lots accepted at normal inspection level
+3. Supplier's process capability (Cpk) for critical characteristics ≥ 1.33, verified by supplier data AND incoming inspection data
+4. No open SCARs against the supplier for this part number
+5. Supplier has a certified quality management system (ISO 9001 minimum; industry-specific certification preferred)
+6. Written agreement documenting skip-lot terms, reversion criteria, and data submission requirements
+
+**Skip-Lot Frequencies:**
+
+| Qualification Level | Inspection Frequency | Reversion Trigger |
+|---|---|---|
+| Skip-Lot 1 | Every 2nd lot | 1 lot rejection |
+| Skip-Lot 2 | Every 3rd lot | 1 lot rejection or supplier Cpk drops below 1.33 |
+| Skip-Lot 3 | Every 5th lot | 1 lot rejection, Cpk concern, or supplier quality system change |
+| CoC Reliance | CoC review only; periodic verification (annual or per-lot-change) | Any NCR, customer complaint, or audit finding |
+
+---
+
+## 6. Supplier Quality Escalation Ladder
+
+### 6.1 Detailed Escalation Process
+
+**Level 0: Normal Operations**
+- Supplier meets scorecard expectations (PPM < threshold, OTD > threshold, SCAR closure on time)
+- Standard incoming inspection level
+- Quarterly scorecard review
+- Annual audit (if risk-based schedule warrants)
+
+**Level 1: SCAR Issued**
+- **Trigger:** Single significant non-conformance (> $5,000 impact or safety/regulatory concern) OR 3+ minor non-conformances on the same part in 90 days
+- **Actions:**
+ - Formal SCAR issued with 8D or equivalent RCA requirement
+ - Supplier has 10 business days for initial response (containment + preliminary root cause)
+ - Supplier has 30 calendar days for full corrective action plan with implementation timeline
+ - Quality engineering review of SCAR response for adequacy
+ - Increase incoming inspection level for the affected part number
+- **Exit criteria:** SCAR accepted and closed with verified effectiveness (90-day monitoring)
+
+**Level 2: Supplier on Watch / Probation**
+- **Trigger:** SCAR not responded to within timeline OR corrective action not effective (recurrence during monitoring) OR scorecard falls below minimum threshold for 2 consecutive quarters
+- **Actions:**
+ - Supplier notified of probation status in writing (Quality Manager or Director level)
+ - Procurement notified; new business hold (no new part numbers awarded)
+ - Increase inspection level for ALL part numbers from this supplier (not just affected part)
+ - Monthly performance review calls with supplier quality management
+ - Supplier must submit a comprehensive improvement plan within 15 business days
+ - Consider on-site quality audit focused on the specific failure mode
+- **Exit criteria:** Improvement plan accepted + 2 consecutive quarters meeting scorecard minimum + no new SCARs
+
+**Level 3: Controlled Shipping**
+- **Trigger:** Continued failures during watch period OR critical quality escape that reaches customer
+- **Actions:**
+ - Controlled Shipping Level 1 (CS-1): Supplier adds additional sort/inspection step with data submitted per shipment
+ - If CS-1 ineffective within 60 days: Controlled Shipping Level 2 (CS-2): third-party resident inspector at supplier's facility, at supplier's expense
+ - All sort/inspection costs debited to supplier
+ - Weekly performance review calls with supplier VP/GM level
+ - Begin qualification of alternate source (if not already underway)
+- **Exit criteria:** 90 consecutive days of zero non-conformances under controlled shipping + root cause fully addressed + systemic improvements validated
+
+**Level 4: New Source Qualification / Phase-Out**
+- **Trigger:** No sustained improvement under controlled shipping OR supplier unwilling/unable to invest in required improvements
+- **Actions:**
+ - Formal notification to supplier of intent to transfer business
+ - Accelerated alternate supplier qualification (expedite PPAP/FAI/first articles)
+ - Reduce business allocation as alternate source ramps up
+ - Maintain controlled shipping on remaining volume
+ - Ensure last-time-buy quantities cover the transition period
+ - Document all quality costs incurred for potential recovery
+- **Timeline:** Depends on part complexity and alternate source readiness; typically 3-12 months
+
+**Level 5: ASL Removal**
+- **Trigger:** Qualification of alternate source complete OR supplier's quality system failure is fundamental (e.g., data falsification, loss of certification)
+- **Actions:**
+ - Formal removal from Approved Supplier List
+ - Final shipment received and inspected under 100% inspection
+ - All supplier-owned tooling at our facility: disposition per contract terms
+ - Our tooling at supplier's facility: retrieve per contract terms
+ - Close all open SCARs as "supplier removed"
+ - Retain supplier quality file for minimum 7 years (regulatory record retention)
+ - Update OASIS (aerospace) or relevant industry databases
+- **Re-entry:** If supplier applies for re-qualification, treat as a new supplier with full qualification process; require evidence that systemic issues were addressed
+
+### 6.2 Escalation Decision Quick Reference
+
+| Situation | Start at Level | Rationale |
+|---|---|---|
+| First minor NC from good supplier | Handle via NCR, no escalation | Single event doesn't warrant formal escalation |
+| First significant NC from good supplier | Level 1 (SCAR) | Significant impact requires formal root cause |
+| Third minor NC in 90 days from same supplier/part | Level 1 (SCAR) | Pattern indicates systemic issue |
+| SCAR response inadequate or late | Level 2 (Watch) | Non-responsiveness is itself a quality system failure |
+| NC reaches customer | Level 2 minimum; Level 3 if safety-related | Customer impact demands immediate escalation |
+| Falsified documentation discovered | Level 4 minimum; Level 5 if confirmed | Trust is broken; containment scope is unknown |
+| Sole-source supplier with quality problems | Level 1 with parallel Level 4 actions (qualify alternate) | Business continuity requires measured response; don't threaten what you can't execute |
+
+---
+
+## 7. Cost of Quality Calculation Models
+
+### 7.1 COQ Category Definitions and Tracking
+
+**Prevention Costs (invest to prevent defects):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Quality planning | Hours × labor rate for quality planning activities | 0.2–0.5% |
+| Process validation/qualification | Labor + equipment + materials for IQ/OQ/PQ | 0.3–0.8% |
+| Supplier qualification | Audit travel + labor + first article costs | 0.1–0.3% |
+| Training (quality-related) | Hours × labor rate + training materials | 0.1–0.3% |
+| SPC implementation/maintenance | Software licenses + labor for chart maintenance | 0.1–0.2% |
+| Design reviews / FMEA | Hours × labor rate for cross-functional reviews | 0.2–0.5% |
+| Poka-yoke development | Design + fabrication + validation of error-proofing | 0.2–0.5% |
+
+**Appraisal Costs (cost of verifying conformance):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Incoming inspection | Hours × labor rate + gauge costs | 0.3–0.8% |
+| In-process inspection | Hours × labor rate (including production wait time) | 0.5–1.5% |
+| Final inspection / testing | Hours × labor rate + test equipment depreciation | 0.3–1.0% |
+| Calibration program | Service contracts + labor + standards | 0.1–0.3% |
+| Audit program (internal + external) | Labor + travel + registration fees | 0.1–0.3% |
+| Laboratory testing | Internal lab costs or external lab fees | 0.2–0.5% |
+
+**Internal Failure Costs (defects caught before shipment):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Scrap | Scrapped material value + processing labor wasted | 1.0–3.0% |
+| Rework | Labor + materials for rework operations | 0.5–2.0% |
+| Re-inspection | Hours × labor rate for re-inspection after rework | 0.1–0.5% |
+| MRB processing | Hours × labor rate for disposition activities | 0.1–0.3% |
+| Root cause investigation | Hours × labor rate for RCA team activities | 0.2–0.5% |
+| Production delays | Lost production time due to quarantine, investigation | 0.5–2.0% |
+| Supplier sort/containment | Third-party sort labor or internal sort labor for supplier-caused NC | 0.1–0.5% |
+
+**External Failure Costs (defects that reach the customer):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Customer returns / credits | Credit memos + return shipping + restocking labor | 0.5–2.0% |
+| Warranty claims | Claim value + processing labor | 0.5–3.0% |
+| Field service / repair | Service labor + travel + parts | 0.3–1.5% |
+| Customer complaint processing | Hours × labor rate for investigation + response | 0.2–0.5% |
+| Recall / field correction | Product replacement + notification + shipping + regulatory | 0.0–5.0% (highly variable) |
+| Regulatory action costs | Fines, consent decree compliance, increased inspections | 0.0–10.0% (catastrophic when triggered) |
+| Reputation / lost business | Lost revenue from customer defection (estimate) | Difficult to measure; typically 2-10x direct costs |
+
+### 7.2 COQ Business Case Model
+
+**Calculating ROI for Quality Investment:**
+
+```
+ROI = (Failure Cost Reduction - Investment Cost) / Investment Cost × 100%
+
+Where:
+ Failure Cost Reduction = (Current internal + external failure costs)
+ - (Projected failure costs after investment)
+ Investment Cost = Prevention cost increase + appraisal cost change
+```
+
+**Rule of Thumb Multipliers:**
+
+| Investment Type | Expected ROI | Payback Period |
+|---|---|---|
+| Poka-yoke (error-proofing) | 5:1 to 20:1 | 3–6 months |
+| SPC implementation | 3:1 to 10:1 | 6–12 months |
+| Supplier development program | 2:1 to 8:1 | 12–24 months |
+| Process validation improvement | 4:1 to 15:1 | 6–18 months |
+| Training program upgrade | 1:1 to 3:1 | 12–24 months |
+
+### 7.3 MRB Decision Process — Economic Model
+
+When disposition is not dictated by safety or regulatory requirements, use economic analysis:
+
+**Rework vs. Scrap Decision:**
+
+```
+Rework if: C_rework + C_reinspect < C_replacement × (1 + premium)
+
+Where:
+ C_rework = Direct rework labor + materials + machine time
+ C_reinspect = Re-inspection labor + any additional testing
+ C_replacement = Purchase price or manufacturing cost of replacement unit
+ premium = Schedule urgency factor (0% if no urgency, 10-50% if production impact,
+ 100%+ if customer delivery at risk)
+```
+
+**Sort vs. Return Decision (for supplier-caused lots):**
+
+```
+Sort if: (C_sort < C_return_freight + C_production_delay) AND (expected yield > 70%)
+
+Where:
+ C_sort = Sort labor hours × rate (typically $25-50/hr for manual sort,
+ $50-100/hr for dimensional sort)
+ C_return_freight = Shipping cost + handling + administrative
+ C_production_delay = (Days of delay × daily production value at risk)
+ expected yield = Estimated % of lot that will pass sort
+ (use sample data to estimate)
+```
+
+**Use-As-Is vs. Sort/Rework Decision (non-safety, non-regulatory):**
+
+```
+Use-as-is if: Risk_functional ≤ Acceptable_risk
+ AND C_use_as_is < C_sort_or_rework
+ AND engineering provides documented justification
+
+Where:
+ Risk_functional = P(failure in use) × Impact(failure)
+ C_use_as_is = Warranty risk increase (estimated) + documentation cost
+ C_sort_or_rework = Direct sort/rework costs + production delay costs
+```
+
+---
+
+## 8. MRB Decision Process — Detailed Workflow
+
+### 8.1 MRB Meeting Structure
+
+**Frequency:** Scheduled weekly; ad hoc for urgent dispositions (safety-critical, production-blocking)
+
+**Required Attendees:**
+- Quality Engineering (chair, facilitates and documents)
+- Design/Product Engineering (functional impact assessment)
+- Manufacturing Engineering (reworkability assessment)
+- Production/Operations (schedule impact)
+- Procurement (supplier-related dispositions, commercial impact)
+- Optional: Regulatory Affairs (if regulatory implications), Customer Quality (if customer notification required)
+
+**Standard Agenda:**
+1. Review of new NCRs pending disposition (by priority: safety first, then production-blocking, then age)
+2. Presentation of data package per NCR (measurements, photographs, process data)
+3. Engineering assessment of functional impact
+4. Disposition decision with documented rationale
+5. Review of aging NCRs (> 15 days without disposition)
+6. Review of MRB metrics (volume, cycle time, cost)
+
+### 8.2 MRB Documentation Requirements
+
+Each MRB disposition must include:
+
+| Element | Purpose | Who Provides |
+|---|---|---|
+| NCR number and description | Identification and traceability | Quality Engineering |
+| Part number, revision, quantity | Scope of disposition | Quality Engineering |
+| Specification violated (clause, dimension, requirement) | Clarity on what's nonconforming | Quality Engineering |
+| Measurement data (actuals vs. tolerances) | Evidence base for disposition | Quality Engineering / Inspection |
+| Photographs (if applicable) | Visual evidence | Quality Engineering / Inspection |
+| Engineering justification (for use-as-is or repair) | Technical rationale for accepting deviation | Design/Product Engineering |
+| Risk assessment (for safety-related items) | Formal risk evaluation | Design/Product Engineering + Quality |
+| Customer approval reference (if required) | Compliance with contract/standard | Quality Engineering |
+| Disposition decision | The decision itself | MRB consensus |
+| Signatures of all MRB members | Accountability and traceability | All attendees |
+| Cost impact | Financial tracking for COQ | Quality Engineering + Finance |
+| CAPA reference (if initiated) | Link to systemic corrective action | Quality Engineering |
diff --git a/skills/quality-nonconformance/references/edge-cases.md b/skills/quality-nonconformance/references/edge-cases.md
new file mode 100644
index 00000000..c98d9458
--- /dev/null
+++ b/skills/quality-nonconformance/references/edge-cases.md
@@ -0,0 +1,588 @@
+# Quality & Non-Conformance Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous quality situations that don't resolve through standard NCR/CAPA workflows.
+
+These edge cases represent the scenarios that separate experienced quality engineers from everyone else. Each one involves competing priorities, ambiguous data, regulatory pressure, and real business impact. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When a quality situation doesn't fit a clean NCR category — when the data is ambiguous, when multiple stakeholders have legitimate competing claims, or when the regulatory and business implications justify deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; these are the situations that end up in audit findings, regulatory actions, or legal proceedings.
+
+---
+
+### Edge Case 1: Customer-Reported Field Failure with No Internal Detection
+
+**Situation:**
+Your medical device company ships Class II endoscopic accessories to a hospital network. Your internal quality data is clean — incoming inspection acceptance rate is 99.7%, in-process defect rate is below 200 PPM, and final inspection has not flagged any issues for the last 6 months. Then a customer complaint comes in: three units from different lots failed during clinical use. The failure mode is a fractured distal tip during retraction, which was not part of your inspection plan because design verification showed the material exceeds the fatigue limit by 4x. The hospital has paused use of your product pending investigation.
+
+**Why It's Tricky:**
+The instinct is to defend your data. "Our inspection shows everything is within specification. The customer must be using the product incorrectly." This is wrong and dangerous for three reasons: (1) field failures can expose failure modes your test plan doesn't cover, (2) clinical use conditions differ from bench testing, and (3) in FDA-regulated environments, dismissing customer complaints without investigation is itself a regulatory violation per 21 CFR 820.198.
+
+The deeper problem is that your inspection plan was designed around the design verification data, which tested fatigue under controlled, uniaxial loading. Clinical use involves multiaxial loading with torsion, and the fatigue characteristics under combined loading may be significantly different. Your process is "in control" but your control plan has a coverage gap.
+
+**Common Mistake:**
+Treating this as a customer-use issue. Sending a "letter of clarification" on proper use without investigating the failure mode. This delays discovery, may worsen patient safety risk, and creates an adverse audit trail if FDA reviews your complaint handling.
+
+The second common mistake: initiating a CAPA that focuses on inspection. "Add fatigue testing to final inspection" solves nothing if the inspection uses the same uniaxial loading condition as the original design verification.
+
+**Expert Approach:**
+1. **Immediate containment:** Place a quality hold on all units of the affected part numbers in your finished goods, distribution, and at the hospital's inventory. Contact the hospital's biomedical engineering department to coordinate the hold — they need serial/lot numbers to identify affected inventory.
+2. **Complaint investigation per 820.198:** Open a formal complaint record. Classify for MDR determination — fractured device during clinical use meets the "malfunction that could cause or contribute to death or serious injury" threshold, requiring MDR filing within 30 days.
+3. **Failure analysis:** Request the failed units from the hospital for physical failure analysis. Conduct fractographic analysis (SEM if needed) to determine the fracture mode — was it fatigue (progressive crack growth), overload (single-event), stress corrosion, or manufacturing defect (inclusion, porosity)?
+4. **Gap analysis on test coverage:** Map the clinical loading conditions against your design verification test protocol. If the failure mode is combined loading fatigue, your uniaxial test would not have detected it. This is a design control gap per 820.30, not a manufacturing control gap.
+5. **Design verification update:** Develop a multiaxial fatigue test that simulates clinical conditions. Test retained samples from the affected lots AND from current production. If retained samples fail the updated test, the scope of the problem is potentially every unit shipped.
+6. **Risk assessment per ISO 14971:** Update the risk file with the newly identified hazard. Calculate the risk priority based on the severity (clinical failure) and probability (based on complaint rate vs. units in service). Determine whether the risk is acceptable per your risk acceptance criteria.
+7. **Field action determination:** Based on the risk assessment, determine whether a voluntary recall, field correction, or enhanced monitoring is appropriate. Document the decision with the risk data supporting it.
+8. **CAPA:** Root cause is a gap in design verification testing — the failure mode was not characterized under clinical loading conditions. Corrective action addresses the test protocol, not the manufacturing process.
+
+**Key Indicators:**
+- Complaint rate vs. units in service determines population risk (e.g., 3 failures in 10,000 units = 300 PPM field failure rate)
+- Fracture surface morphology distinguishes fatigue, overload, and material defects
+- Time-to-failure pattern (all early-life vs. random vs. wear-out) indicates failure mechanism
+- If multiple lots are affected, the root cause is likely design or process-related, not material-lot-specific
+
+**Documentation Required:**
+- Formal complaint records per 820.198
+- MDR filing documentation
+- Failure analysis report with photographs and fractography
+- Updated risk file per ISO 14971
+- Revised design verification test protocol
+- Field action decision documentation (including decision NOT to recall, if applicable)
+- CAPA record linking complaint → investigation → root cause → corrective action
+
+---
+
+### Edge Case 2: Supplier Audit Reveals Falsified Certificates of Conformance
+
+**Situation:**
+During a routine audit of a casting supplier (Tier 2 supplier to your automotive Tier 1 operation), your auditor discovers that the material certificates for A356 aluminum castings do not match the spectrometer results. The supplier has been submitting CoCs showing material composition within specification, but the auditor's portable XRF readings on randomly selected parts show silicon content at 8.2% against a specification of 6.5-7.5%. The supplier's quality manager initially claims the XRF is inaccurate, but when pressed, admits that their spectrometer has been out of calibration for 4 months, and they've been using historical test results on the CoCs rather than actual lot-by-lot test data.
+
+**Why It's Tricky:**
+This is not a simple non-conformance — it's a quality system integrity failure. The supplier did not simply ship nonconforming parts; they submitted fraudulent documentation. The distinction matters because: (1) every shipment received during the 4-month period is now suspect, (2) you cannot trust ANY data from this supplier without independent verification, (3) in automotive, this may constitute a failure to maintain IATF 16949 requirements, and (4) parts from this supplier may already be in customer vehicles.
+
+The containment scope is potentially enormous. A356 aluminum with elevated silicon has different mechanical properties — it may be more brittle. If these castings are structural or safety-critical, the implications extend to end-of-line testing, vehicle recalls, and NHTSA notification.
+
+**Common Mistake:**
+Treating this like a normal NCR. Writing a SCAR and asking the supplier to "improve their testing process." This underestimates the severity — the issue is not process improvement but fundamental integrity. A supplier that falsifies data will not be fixed by a corrective action request.
+
+The second common mistake: immediately terminating the supplier without securing containment. If you have weeks of WIP and finished goods containing these castings, cutting off the supplier before you've contained and sorted the affected inventory creates a dual crisis — quality AND supply.
+
+**Expert Approach:**
+1. **Preserve evidence immediately.** Photograph the audit findings, retain the XRF readings, request copies of the CoCs for the last 4 months, and document the supplier quality manager's admission in the audit notes with date, time, and witnesses. This evidence may be needed for legal proceedings or regulatory reporting.
+2. **Scope the containment.** Identify every lot received from this supplier in the last 4+ months (add buffer — the calibration may have drifted before formal "out of calibration" date). Trace those lots through your operation: incoming stock, WIP, finished goods, shipped to customer, in customer's inventory or vehicles.
+3. **Independent verification.** Send representative samples from each suspect lot to an accredited independent testing laboratory for full material composition analysis. Do not rely on the supplier's belated retesting — their data has zero credibility.
+4. **Risk assessment on affected product.** If material composition is out of spec, have design engineering evaluate the functional impact. A356 with 8.2% Si instead of max 7.5% may still be functional depending on the application, or it may be critically weakened for a structural casting. The answer depends on the specific part function and loading conditions.
+5. **Customer notification.** In IATF 16949 environments, customer notification is mandatory when suspect product may have been shipped. Contact your customer quality representative within 24 hours. Provide lot/date range, the nature of the issue, and your containment actions.
+6. **Automotive-specific reporting.** If the parts are safety-critical and the composition affects structural integrity, evaluate NHTSA reporting obligations per 49 CFR Part 573 (defect notification). Consult legal counsel — the bar for vehicle safety defect reporting is "poses an unreasonable risk to motor vehicle safety."
+7. **Supplier disposition.** This is an immediate escalation to Level 4-5 on the supplier ladder. Begin alternate source qualification in parallel. Maintain the supplier on controlled shipping (CS-2, third-party inspection) only for the duration needed to transition. Do not invest in "developing" a supplier that falsified data — the trust foundation is broken.
+8. **Systemic review.** Audit all other CoC-reliant incoming inspection processes. If this supplier falsified data, what is the probability that others are as well? Increase verification sampling on other CoC-reliance suppliers, especially those with single-source positions.
+
+**Key Indicators:**
+- Duration of falsification determines containment scope (months × volume = total suspect population)
+- The specific spec exceedance determines functional risk (minor chemistry drift vs. major composition deviation)
+- Traceability of material lots through your production determines the search space
+- Whether the supplier proactively disclosed vs. you discovered impacts the trust assessment
+
+**Documentation Required:**
+- Audit report with all findings, evidence, and admissions
+- XRF readings and independent lab results
+- Complete lot traceability from supplier through your process to customer
+- Risk assessment on functional impact of material deviation
+- Customer notification records with acknowledgment
+- Legal review documentation (privilege-protected as applicable)
+- Supplier escalation and phase-out plan
+
+---
+
+### Edge Case 3: SPC Shows Process In-Control But Customer Complaints Are Rising
+
+**Situation:**
+Your CNC turning operation produces shafts for a precision instrument manufacturer. Your SPC charts on the critical OD dimension (12.00 ±0.02mm) have been stable for 18 months — X-bar/R chart shows a process running at 12.002mm mean with Cpk of 1.45. No control chart signals. Your internal quality metrics are green across the board. But the customer's complaint rate on your shafts has tripled in the last quarter. Their failure mode: intermittent binding in the mating bore assembly. Your parts meet print, their parts meet print, but the assembly doesn't work consistently.
+
+**Why It's Tricky:**
+The conventional quality response is "our parts meet specification." And technically, that's true. But the customer's assembly process is sensitive to variation WITHIN your specification. Their bore is also within specification, but when your shaft is at the high end of tolerance (+0.02) and their bore is at the low end, the assembly binds. Both parts individually meet print, but the tolerance stack-up creates interference in the worst-case combination.
+
+The SPC chart is not lying — your process is in statistical control and capable by every standard metric. The problem is that capability indices measure your process against YOUR specification, not against the functional requirement of the assembly. A Cpk of 1.45 means you're producing virtually no parts outside ±0.02mm, but if the actual functional window is ±0.01mm centered on the nominal, your process is sending significant variation into a critical zone.
+
+**Common Mistake:**
+Dismissing the complaint because the data says you're in spec. Sending a letter citing your Cpk and stating that the parts conform. This is technically correct and operationally wrong — it destroys the customer relationship and ignores the actual problem.
+
+The second mistake: reacting by tightening your internal specification without understanding the functional requirement. If you arbitrarily cut your tolerance to ±0.01mm, you increase your scrap rate (and cost) without certainty that it solves the assembly issue.
+
+**Expert Approach:**
+1. **Acknowledge the complaint and avoid the "we meet spec" defense.** The customer is experiencing real failures. Whether they're caused by your variation, their variation, or the interaction of both is what needs to be determined — not assumed.
+2. **Request the customer's mating component data.** Ask for their bore SPC data — mean, variation, Cpk, distribution shape. You need to understand both sides of the assembly equation.
+3. **Conduct a tolerance stack-up analysis.** Using both your shaft data and their bore data, calculate the assembly clearance distribution. Identify what percentage of assemblies fall into the interference zone. This analysis converts "your parts meet spec" into "X% of assemblies will have interference problems."
+4. **Evaluate centering vs. variation.** If the problem is that your process runs at 12.002mm (slightly above nominal) and their bore is centered low, the fix may be as simple as re-centering your process to 11.998mm — shifting the mean away from the interference zone without changing the variation.
+5. **Consider bilateral specification refinement.** Propose a joint engineering review to establish a tighter bilateral tolerance that accounts for both process capabilities. If your Cpk for ±0.01mm around a recentered mean is still > 1.33, the tighter spec is achievable.
+6. **Update your control plan.** If the assembly-level functional requirement is tighter than the print tolerance, your control plan should reflect the actual functional target, not just the nominal ± tolerance from the drawing.
+7. **This is NOT a CAPA.** This is a specification adequacy issue, not a non-conformance. The correct vehicle is an engineering change process to update the specification, not a CAPA to "fix" a process that is operating correctly per its current requirements.
+
+**Key Indicators:**
+- Your process Cpk relative to the FUNCTIONAL tolerance (not drawing tolerance) is the key metric
+- Assembly clearance distribution reveals the actual failure probability
+- Shift in customer complaint timing may correlate with a process change on the customer's side (did they tighten their bore process?)
+- Temperature effects on both parts at assembly (thermal expansion can change clearances)
+
+---
+
+### Edge Case 4: Non-Conformance Discovered on Already-Shipped Product
+
+**Situation:**
+During a routine review of calibration records, your metrology technician discovers that a CMM probe used for final inspection of surgical instrument components had a qualification failure that was not flagged. The probe was used to inspect and release 14 lots over the past 6 weeks. The qualification failure indicates the probe may have been reading 0.015mm off on Z-axis measurements. The affected dimension is a critical depth on an implantable device component with a tolerance of ±0.025mm. Of the 14 lots (approximately 8,400 units), 9 lots have already been shipped to three different customers (medical device OEMs). Five lots are still in your finished goods inventory.
+
+**Why It's Tricky:**
+The measurement uncertainty introduced by the probe error doesn't mean the parts are nonconforming — it means you can't be certain they're conforming. A 0.015mm bias on a ±0.025mm tolerance doesn't automatically reject all parts, but it may have caused you to accept parts that were actually near or beyond the lower specification limit.
+
+For FDA-regulated medical device components, measurement system integrity is not optional — it's a core requirement of 21 CFR 820.72 (inspection, measuring, and test equipment). A calibration failure that went undetected means your quality records for 14 lots cannot be relied upon. This is a measurement system failure, not necessarily a product failure, but you must treat it as a potential product failure until proven otherwise.
+
+**Common Mistake:**
+Recalling all 14 lots immediately without first analyzing the data. A blind recall of 8,400 implantable device components creates massive supply chain disruption for your customers (who may be OEMs that incorporate your component into a finished device in their own supply chain). If the actual parts are conforming (just the measurement was uncertain), the recall causes more harm than it prevents.
+
+The other common mistake: doing nothing because you believe the parts are "probably fine." Failure to investigate and document constitutes a quality system failure, regardless of whether the parts are actually good.
+
+**Expert Approach:**
+1. **Immediate hold on the 5 lots still in inventory.** Quarantine in MRB area. These can be re-inspected.
+2. **Quantify the measurement uncertainty.** Re-qualify the CMM probe and determine the actual bias. Then overlay the bias on the original measurement data for all 14 lots. For each part, recalculate: measured value + bias = potential actual value. Identify how many parts' recalculated values fall outside specification.
+3. **Risk stratification of shipped lots.** Group the 9 shipped lots into three categories:
+ - Parts where recalculated values are well within specification (> 50% of tolerance margin remaining): low risk. Document the analysis but no customer notification needed for these specific lots.
+ - Parts where recalculated values are marginal (within specification but < 25% margin): medium risk. Engineering assessment needed on functional impact.
+ - Parts where recalculated values potentially exceed specification: high risk. Customer notification required; recall or sort at customer.
+4. **Customer notification protocol.** For medium and high-risk lots, notify the customer quality contacts within 24 hours. Provide: lot numbers, the nature of the measurement uncertainty, your risk assessment, and your recommended action (e.g., replace at-risk units, sort at customer site with your quality engineer present, or engineering disposition if parts are functionally acceptable).
+5. **Re-inspect the 5 held lots.** Use a verified, qualified CMM probe. Release lots that pass. Scrap or rework lots that fail.
+6. **Root cause and CAPA.** Root cause: probe qualification failure was not flagged by the CMM operator or the calibration review process. Investigate why: was the qualification check skipped, was the acceptance criteria not clear, was the operator not trained on the significance of qualification failure? CAPA must address the system gap — likely a combination of calibration software alerting, operator procedure, and management review of calibration status.
+7. **Evaluate MDR obligation.** If any shipped parts are potentially outside specification and the component is in an implantable device, evaluate whether this constitutes a reportable event. Consult with Regulatory Affairs — the threshold is whether the situation "could cause or contribute to death or serious injury." The measurement uncertainty may or may not meet this threshold depending on the functional significance of the affected dimension.
+
+**Key Indicators:**
+- The ratio of measurement bias to tolerance width determines the severity (0.015mm bias on ±0.025mm tolerance = 30% of tolerance, which is significant)
+- The distribution of original measurements near the specification limit determines how many parts are truly at risk
+- Whether the bias was consistent or variable determines whether the risk analysis is conservative or optimistic
+- Customer's use of the component (implantable vs. non-patient-contact) determines the regulatory urgency
+
+---
+
+### Edge Case 5: CAPA That Addresses Symptom, Not Root Cause
+
+**Situation:**
+Six months ago, your company closed CAPA-2024-0087 for a recurring dimensional non-conformance on a machined housing. The root cause was documented as "operator measurement technique variation" and the corrective action was "retrain all operators on use of bore micrometer per WI-3302 and implement annual re-certification." Training records show all operators were retrained. The CAPA effectiveness check at 90 days showed zero recurrences. The CAPA was closed.
+
+Now, the same defect is back. Three NCRs in the last 30 days — all the same failure mode (bore diameter out of tolerance on the same feature). The operators are certified. The work instruction has not changed. The micrometer is in calibration.
+
+**Why It's Tricky:**
+This CAPA failure is embarrassing and common. It reveals two problems: (1) the original root cause analysis was insufficient — "operator technique variation" is a symptom, not a root cause, and (2) the 90-day effectiveness monitoring happened to coincide with a period when the actual root cause was quiescent.
+
+The deeper issue is organizational: the company's CAPA process accepted a "retrain the operator" corrective action for a recurring dimensional non-conformance. An experienced quality engineer would flag training-only CAPAs for manufacturing non-conformances as inherently weak.
+
+**Common Mistake:**
+Opening a new CAPA with a new number and starting fresh. This creates the illusion of a new problem when it's the same unresolved problem. The audit trail now shows a closed CAPA (false closure) and a new CAPA — which is exactly what an FDA auditor looks for when evaluating CAPA system effectiveness.
+
+The second mistake: doubling down on training — "more training, more frequently, with a competency test." If the first round of training didn't fix the problem, a second round won't either.
+
+**Expert Approach:**
+1. **Reopen CAPA-2024-0087, do not create a new CAPA.** The original CAPA was ineffective. Document the recurrence as evidence that the CAPA effectiveness verification was premature or based on insufficient data. The CAPA system must track this as a single unresolved issue, not two separate issues.
+2. **Discard the original root cause.** "Operator technique variation" must be explicitly rejected as a root cause. Document why: training was implemented and verified, operators are certified, yet the defect recurred. Therefore, the root cause was not operator technique.
+3. **Restart root cause analysis with fresh eyes.** Form a new team that includes people who were NOT on the original team (fresh perspective). Use Ishikawa/6M to systematically investigate all cause categories — the original team likely converged too quickly on the Man category.
+4. **Investigate the actual root cause candidates:**
+ - Machine: Is the CNC spindle developing runout or thermal drift? Check spindle vibration data and thermal compensation logs.
+ - Material: Has the raw material lot changed? Different material hardness affects cutting dynamics and can shift dimensions.
+ - Method: Did the tool path or cutting parameters change? Check the CNC program revision history.
+ - Measurement: Is the bore micrometer the right gauge for this measurement? What's the Gauge R&R? If the gauge is marginal, operators may get variable results even with correct technique.
+ - Environment: Did ambient temperature change with the season? A 5°C temperature swing in a non-climate-controlled shop can shift dimensions by 5-10μm on aluminum parts.
+5. **Design the corrective action at a higher effectiveness rank.** If root cause is machine-related: implement predictive maintenance or in-process gauging (detection control, rank 4). If material-related: adjust process parameters by material lot or source from a more consistent supplier (substitution, rank 2). If measurement-related: install a hard-gauging fixture (engineering control, rank 3). Training is only acceptable as a SUPPLEMENTARY action, never the primary action.
+6. **Extend the effectiveness monitoring period.** The original 90-day monitoring was insufficient. For a recurring issue, monitor for 6 months or 2 full cycles of the suspected environmental/seasonal factor, whichever is longer. Define quantitative pass criteria (e.g., zero recurrences of the specific failure mode AND Cpk on the affected dimension ≥ 1.33 for the full monitoring period).
+
+**Key Indicators:**
+- The fact that 90-day monitoring showed zero recurrence but the defect returned suggests the root cause is intermittent or cyclic (seasonal temperature, tool wear cycle, material lot cycle)
+- Operator-related root causes are almost never the actual root cause for dimensional non-conformances in CNC machining — the machine is controlling the dimension, not the operator
+- Gauge R&R data is critical — if the measurement system contribution is > 30% of the tolerance, the measurement itself may be the root cause of apparent non-conformances
+
+---
+
+### Edge Case 6: Audit Finding That Challenges Existing Practice
+
+**Situation:**
+During a customer audit of your aerospace machining facility, the auditor cites a finding against your first article inspection (FAI) process. Your company performs FAI per AS9102 and has a long track record of conforming FAIs. The auditor's finding: you do not perform a full FAI resubmission when you change from one qualified tool supplier to another for the same cutting tool specification. Your position is that the tool meets the same specification (material, geometry, coating) and the cutting parameters are identical, so no FAI is required. The auditor contends that a different tool supplier — even for the same specification — constitutes a "change in manufacturing source for special processes or materials" under AS9102, requiring at minimum a partial FAI.
+
+**Why It's Tricky:**
+Both positions have merit. AS9102 requires FAI when there is a change in "manufacturing source" for the part. A cutting tool is not the part — it's a consumable used to make the part. But the auditor's argument is that a different tool supplier may have different cutting performance characteristics (tool life, surface finish, dimensional consistency) that could affect the part even though the tool itself meets the same specification.
+
+The practical reality is that your machinists know different tool brands cut differently. A Sandvik insert and a Kennametal insert with the same ISO designation will produce slightly different surface finishes and may wear at different rates. In aerospace, "slightly different" can matter.
+
+**Common Mistake:**
+Arguing with the auditor during the audit. Debating the interpretation of AS9102 in real time is unproductive and creates an adversarial audit relationship. Accept the finding, respond formally, and use the response to present your interpretation with supporting evidence.
+
+The second mistake: over-correcting by requiring a full FAI for every consumable change. This would make your FAI process unworkable — you change tool inserts multiple times per shift. The corrective action must be proportionate to the actual risk.
+
+**Expert Approach:**
+1. **Accept the audit finding formally.** Do not concede that your interpretation is wrong — accept that the auditor has identified an area where your process does not explicitly address the scenario. Write the response as: "We acknowledge the finding and will evaluate our FAI triggering criteria for manufacturing consumable source changes."
+2. **Research industry guidance.** AS9102 Rev C, IAQG FAQ documents, and your registrar's interpretation guides may provide clarity. Contact your certification body's technical manager for their interpretation.
+3. **Risk-based approach.** Categorize tool supplier changes by risk:
+ - Same specification, same brand/series, different batch: No FAI required (normal tool replacement)
+ - Same specification, different brand: Evaluate with a tool qualification run — measure first articles from the new tool brand against the FAI characteristics. If all characteristics are within specification, document the qualification and don't require formal FAI.
+ - Different specification or geometry: Full or partial FAI per AS9102
+4. **Process change.** Update your FAI trigger procedure to explicitly address consumable source changes. Create a "tool qualification" process that is lighter than FAI but provides documented evidence that the new tool source produces conforming parts.
+5. **Corrective action response.** Your formal response to the auditor should describe the risk-based approach, the tool qualification procedure, and the updated FAI trigger criteria. Demonstrate that you've addressed the gap with a proportionate control, not with a blanket rule that will be unworkable.
+
+**Key Indicators:**
+- The auditor's interpretation may or may not be upheld at the next certification body review — but arguing the point at the audit is always unproductive
+- Your machinist's tribal knowledge about tool brand differences is actually valid evidence — document it
+- The risk-based approach is defensible because AS9100 itself is built on risk-based thinking
+
+---
+
+### Edge Case 7: Multiple Root Causes for Single Non-Conformance
+
+**Situation:**
+Your injection molding operation is producing connectors with intermittent short shots (incomplete fill) and flash simultaneously on the same tool. SPC on shot weight shows variation has doubled over the last month. The standard 5 Whys analysis by the floor quality technician concluded "injection pressure too low" and recommended increasing pressure by 10%. The problem did not improve — in fact, flash increased while short shots continued.
+
+**Why It's Tricky:**
+Short shots and flash are opposing defects. Short shot = insufficient material reaching the cavity. Flash = material escaping the parting line. Having both simultaneously on the same tool is pathological and indicates that the 5 Whys answer ("pressure too low") was oversimplified. Increasing pressure addresses the short shot but worsens the flash. This is a classic case where 5 Whys fails because the failure has multiple interacting causes, not a single linear chain.
+
+**Common Mistake:**
+Continuing to adjust a single parameter (pressure) up and down looking for a "sweet spot." This is tampering — chasing the process around the operating window without understanding what's driving the variation.
+
+**Expert Approach:**
+1. **Stop adjusting.** Return the process to the validated parameters. Document that the attempted pressure increase did not resolve the issue and created additional flash defects.
+2. **Use Ishikawa, not 5 Whys.** Map the potential causes across all 6M categories. For this type of combined defect, the most likely interacting causes are:
+ - **Machine:** Worn platens or tie bars allowing non-uniform clamp pressure across the mold face. This allows flash where clamp force is low while restricting fill where the parting line is tight.
+ - **Material:** Material viscosity variation (lot-to-lot MFI variation, or moisture content). High viscosity in one shot → short shot. Low viscosity in next shot → flash.
+ - **Mold (Method):** Worn parting line surfaces creating uneven shut-off. Vent clogging restricting gas escape in some cavities (causing short shots) while flash at the parting line.
+3. **Data collection before root cause conclusion.** Run a short diagnostic study:
+ - Measure clamp tonnage distribution across the mold face (platen deflection check with pressure-indicating film between the parting surfaces)
+ - Check material MFI on the current lot and the last 3 lots
+ - Inspect the mold parting line for wear, verify vent depths
+4. **Address ALL contributing causes.** The corrective actions will likely be multiple:
+ - Mold maintenance (clean vents, re-stone parting line surfaces) — addresses the flash pathway
+ - Material incoming inspection for MFI with tighter acceptance criteria — addresses viscosity variation
+ - Platen deflection correction or mold design modification — addresses the non-uniform clamp force
+5. **The CAPA must capture all three causes.** Document that the single defect (short shot + flash) has three interacting root causes. Each cause has its own corrective action. Effectiveness monitoring must track the combined defect rate, not each cause independently.
+
+**Key Indicators:**
+- Combined opposing defects always indicate multiple interacting causes — never a single parameter
+- Shot-to-shot weight variation (SPC) distinguishes material variation (random pattern) from machine variation (trending or cyclic pattern)
+- Pressure-indicating film between mold halves reveals clamp force distribution problems that are invisible otherwise
+- Vent depth measurements should be part of routine mold PM but are commonly skipped
+
+---
+
+### Edge Case 8: Intermittent Defect That Cannot Be Reproduced on Demand
+
+**Situation:**
+Your electronics assembly line has a 0.3% field return rate on a PCB assembly due to intermittent solder joint failures on a specific BGA (Ball Grid Array) component. The defect has been reported 47 times across approximately 15,000 units shipped over 6 months. X-ray inspection of returned units shows voiding in BGA solder joints exceeding 25% (your internal standard is <20% voiding). However, your in-process X-ray inspection of production units consistently shows voiding below 15%. The defect is real (47 customer failures is not noise), but your inspection process cannot detect or reproduce it.
+
+**Why It's Tricky:**
+The customer failures are real — 47 returns with consistent failure mode across multiple lots rules out customer misuse. But your production inspection shows conforming product. This means either: (1) your inspection is sampling the wrong things, (2) the voiding develops or worsens after initial inspection (during subsequent thermal cycling in reflow for other components, or during customer thermal cycling in use), or (3) the void distribution varies within the BGA footprint and your X-ray angle doesn't capture the worst-case joints.
+
+BGA solder joint voiding is particularly insidious because voids that are acceptable at room temperature can cause failure under thermal cycling — the void acts as a stress concentrator and crack initiation site. The failure mechanism is thermomechanical fatigue accelerated by voiding, which means the defect is present at the time of manufacture but only manifests after enough thermal cycles in the field.
+
+**Common Mistake:**
+Increasing the X-ray inspection frequency or adding 100% X-ray inspection. If your current X-ray protocol can't distinguish the failing population from the good population, doing more of the same inspection won't help — you're looking for the defect in the wrong way.
+
+**Expert Approach:**
+1. **Failure analysis on returned units.** Cross-section the BGA solder joints on failed returns. Map the void location, size, and the crack propagation path. Determine if the cracks initiate at voids (they almost always do in BGA thermomechanical fatigue).
+2. **X-ray protocol review.** Compare the X-ray imaging parameters (angle, magnification, algorithm) between production inspection and failure analysis inspection. Often, the production X-ray uses a top-down view that averages voiding across the entire joint, while the critical voiding is concentrated at the component-side interface where thermal stress is highest.
+3. **Process investigation using DOE.** Solder paste voiding is influenced by: stencil aperture design, paste-to-pad ratio, reflow profile (soak zone temperature and time), pad finish (ENIG vs. OSP vs. HASL), and BGA component pad finish. Run a designed experiment varying the controllable factors against voiding as the response. Use the optimized parameters to reduce the baseline voiding level below the failure threshold.
+4. **Reliability testing.** Subject production samples to accelerated thermal cycling (ATC) testing per IPC-9701 (-40°C to +125°C for SnPb, -40°C to +100°C for SAC305). Monitor for failure at intervals. This replicates the field failure mechanism in a controlled environment and allows you to validate that process improvements actually reduce the failure rate.
+5. **SPC on voiding.** Implement BGA voiding measurement as an SPC characteristic with limits set based on the reliability test data (not just the IPC-7095 generic guideline). The control limits should be set at the voiding level below which reliability testing shows acceptable life.
+
+**Key Indicators:**
+- 0.3% field return rate in electronics is unusually high for a solder defect — this is a systemic process issue, not random
+- Void location within the joint matters more than total void percentage — a 15% void concentrated at the interface is worse than 25% distributed throughout the joint body
+- Correlation between void levels and reflow profile parameters (especially time above liquidus and peak temperature) is typically the strongest process lever
+
+---
+
+### Edge Case 9: Supplier Sole-Source with Quality Problems
+
+**Situation:**
+Your sole-source supplier for a custom titanium forging (Ti-6Al-4V, closed-die forging with proprietary tooling) has been on SCAR for the third time in 12 months. The recurring issue is grain flow non-conformance — the microstructural grain flow does not follow the specified contour, which affects fatigue life. The forgings are for a landing gear component (aerospace, AS9100). The forgings cost $12,000 each, with 6-month lead time for tooling and 4-month lead time for production. You need 80 forgings per year. There is no other qualified supplier, and qualifying a new forging source would take 18-24 months including tooling, first articles, and customer qualification.
+
+**Why It's Tricky:**
+This is the sole-source quality trap. Your supplier quality escalation ladder says you should move to controlled shipping and begin alternate source qualification. But controlled shipping at a sole-source supplier is a paper exercise — you'll inspect the forgings, but if they fail, you have no alternative. And beginning alternate source qualification gives you 18-24 months of continued dependence on a problematic supplier.
+
+The business can't tolerate a supply disruption. Each forging is a $12,000 part with 6+ months of lead time, and you need 80 per year for an active production program. Shutting off the supplier shuts off your production.
+
+**Common Mistake:**
+Treating this like a normal supplier quality issue. Following the escalation ladder to the letter (controlled shipping → alternate source qualification → phase-out) without considering that the escalation ladder was designed for commodity parts with alternatives. For a sole-source strategic supplier, aggressive escalation can backfire — the supplier may deprioritize your business or increase prices.
+
+The opposite mistake: accepting the recurring non-conformance because you have no alternative. "Use-as-is because we're sole-sourced" is not an acceptable disposition for a safety-critical aerospace forging, regardless of supply constraints.
+
+**Expert Approach:**
+1. **Invest in the supplier, don't just punish them.** Propose a joint development program. Your metallurgical engineer works with their forging process engineer to optimize die design, forging temperature, and press force profile for the grain flow requirement. This is supplier development, not just supplier corrective action.
+2. **Root cause the grain flow issue properly.** Grain flow non-conformance in closed-die forging is typically caused by: incorrect billet pre-form shape (material doesn't flow where the die expects it), insufficient forging reduction ratio, incorrect forging temperature (too cold = surface cracking, too hot = grain growth), or die wear allowing material to flow outside the intended path. Which of these is it? Each has a different solution.
+3. **Begin alternate source qualification quietly.** Start the 18-24 month qualification process immediately, but do not use it as a threat. Frame it as "supply chain risk mitigation" — even if the supplier improves, having a second source is sound supply chain management for a safety-critical part.
+4. **Negotiate a quality improvement agreement.** Work with procurement to structure a commercial agreement: the supplier invests in process improvements (die refurbishment, process parameter optimization, enhanced in-process metallographic inspection), and you commit to volume or price stability over the investment payback period.
+5. **Increase your incoming inspection on these forgings.** Regardless of supplier performance, a safety-critical aerospace forging should have metallographic inspection at incoming — don't rely solely on the supplier's certification. The cost of a destructive test sample (one forging per lot) is small relative to the consequence of a grain flow non-conformance reaching the machined part.
+6. **MRB each non-conformance individually.** Just because the supplier is sole-sourced does not mean every non-conformance gets a use-as-is disposition. Each forging must be evaluated on its specific grain flow pattern against the design intent. Some deviations may be acceptable with engineering and customer concession; others are scrapped regardless of supply impact. Document the disposition rationale with metallographic evidence and engineering analysis.
+
+**Key Indicators:**
+- Grain flow pattern should be evaluated against the finished machined geometry, not just the forging geometry — material removal during machining can expose grain flow that was within the forging specification but becomes non-conforming in the machined part
+- A 3-sigma supply buffer (keep 6+ months of safety stock) is essential while working the quality improvement with a sole source
+- Die life tracking correlates with grain flow quality — quality typically degrades as the die wears
+
+---
+
+### Edge Case 10: Non-Conformance Discovered During Regulatory Audit
+
+**Situation:**
+During an FDA inspection of your medical device manufacturing facility, the investigator pulls a traveler for a recently completed production lot of surgical staplers. Reviewing the dimensional inspection data, the investigator notes that two of ten measured dimensions are recorded as "within tolerance" but the actual values are not recorded — only pass/fail. The investigator asks to see the actual measurement values. Your inspector explains that these two dimensions are measured with go/no-go gauges and the pass/fail result is all that's recorded. The investigator issues a Form 483 observation: "There is no procedure to ensure that manufacturing specifications have been met for two critical dimensions on [part number]. Actual measurement data is not recorded."
+
+The investigator's position: go/no-go gauging on a critical dimension of a Class II surgical device is insufficient because it doesn't provide trend data to detect process drift before the process goes out of specification. Your position: go/no-go gauges are an industry-accepted measurement method, the gauges are calibrated, and the control plan specified this method.
+
+**Why It's Tricky:**
+Both positions are defensible. Go/no-go gauging is a valid measurement method recognized by ASME and used across all manufacturing industries. For many applications, it's actually preferred because it eliminates measurement error — the gauge is either go or no-go, there's no subjective reading. However, the FDA investigator has a point: attribute data (pass/fail) from go/no-go gauges does not support trend analysis or SPC, which means you cannot detect a process drifting toward the specification limit until it actually exceeds the limit and the gauge rejects the part.
+
+For a critical dimension on a surgical device, the argument for variable data (actual measurements) that supports trend analysis has real merit. This is the tension between measurement practicality and quality system rigor.
+
+**Common Mistake:**
+Arguing with the investigator that go/no-go gauging is adequate. Even if you're technically right, arguing with an FDA investigator during an inspection almost never helps. The observation is written; your opportunity to respond is in the formal 483 response, not in the moment.
+
+The opposite mistake: immediately committing to variable gauging for every dimension. This may be impractical, expensive, and unnecessary for non-critical dimensions. Over-correcting in response to a 483 creates an unsustainable system.
+
+**Expert Approach:**
+1. **Accept the observation gracefully.** During the inspection: "Thank you. We'll evaluate our measurement methodology for these critical dimensions and respond in our 483 response." Do not argue, do not minimize, do not promise a specific corrective action on the spot.
+2. **483 response (due within 15 business days):** Structure the response in four parts:
+ - **Acknowledgment:** "We acknowledge the observation regarding [specific dimensions, specific part number]."
+ - **Investigation:** "We have reviewed the measurement methodology for critical dimensions on this part number. We concur that while go/no-go gauging provides conformance verification, it does not support the trend analysis needed to proactively detect process drift on critical dimensions."
+ - **Corrective action:** "We will implement variable measurement (calibrated digital calipers/micrometers with data recording) for all critical dimensions on Class II and Class III devices, effective [date]. Measurement data will be charted using SPC (X-bar/R) to enable trend detection. Go/no-go gauging will be retained as a secondary verification method."
+ - **Scope extension:** "We are reviewing all inspection plans for Class II and Class III devices to identify any other critical dimensions using attribute-only gauging and will convert to variable gauging as appropriate."
+3. **Implementation.** Actually implement the change before the FDA follow-up (which may be in 6-12 months). Have SPC charts running and demonstrating trend capability by the time of re-inspection. This is what FDA means by "evidence of effectiveness."
+4. **Don't over-correct.** Convert critical dimensions to variable gauging. Non-critical dimensions where go/no-go is practical and appropriate can remain as attribute gauging. Document the risk-based rationale for which dimensions require variable data and which do not.
+
+**Key Indicators:**
+- The investigator's observation is about system capability, not about a specific defective product
+- A strong 483 response demonstrates that you understand the intent of the observation, not just the letter
+- The FDA evaluates your CAPA system partly by how you respond to observations — a proportionate, well-reasoned response is valued over a panicked over-correction
+- Scope extension (looking beyond the specific finding to the systemic issue) is explicitly what FDA wants to see in a 483 response
+
+**Documentation Required:**
+- Copy of Form 483 observation
+- Formal 483 response with all four sections
+- Updated inspection plans showing conversion from attribute to variable gauging
+- SPC implementation records (chart setup, control limits, operator training)
+- Risk-based rationale document for gauging method selection by characteristic criticality
+- Evidence of scope extension review (list of all inspection plans reviewed, findings, and actions)
+
+---
+
+### Edge Case 11: Customer Rejects Lot That Passed Your Final Inspection
+
+**Situation:**
+Your automotive tier 2 plant ships stamped steel brackets to a tier 1 seat frame assembler. Your final inspection per the control plan checks 12 dimensions per AQL sampling (Level II, AQL 1.0). Lot 2025-0892 passed your inspection with zero rejects in the sample. The tier 1 customer's incoming inspection rejects the lot — their 100% automated vision system flagged 4.2% of pieces for a burr height exceeding 0.3mm on edge B. Your control plan does not include burr height on edge B as an inspection characteristic because the customer print specifies "deburr per shop practice" with no quantitative requirement.
+
+**Why It's Tricky:**
+The customer's rejection appears to add a requirement that isn't on the drawing. "Deburr per shop practice" is a qualitative, subjective call — there's no measurable specification. However, the customer has an automated system that quantifies what "shop practice" means operationally. From the customer's perspective, 4.2% of parts have burrs that interfere with their automated assembly process. From your perspective, you met all dimensioned requirements and the subjective "deburr" note cannot be objectively measured.
+
+This is a specification gap, not a quality failure — but you still have a rejected lot, a customer demanding corrective action, and a control plan that doesn't cover the issue.
+
+**Common Mistake:**
+Refusing the rejection because the requirement isn't quantified on the drawing. This is technically correct and commercially disastrous — the customer doesn't care about specification semantics; their assembly line is down.
+
+**Expert Approach:**
+1. **Accept the return or sort on-site.** Business continuity first. Offer to send a sort team to the customer's facility to 100% inspect and remove the nonconforming parts, or accept the return and sort at your facility. This gets the customer's line running while you address the systemic issue.
+2. **Request the quantitative requirement.** Contact the customer's quality engineering team and ask them to provide a measurable specification for burr height on edge B. "We need a quantified requirement to add this to our control plan and SPC program. Can you issue a drawing change or specification supplement with a maximum burr height?"
+3. **Interim control.** While the drawing change is in process, add burr height inspection to your control plan as a customer-specific requirement with the threshold from their vision system (0.3mm max).
+4. **Process investigation.** Why is burr height variable? Investigate stamping die condition — progressive die wear on the cutting edge increases burr height over the production run. Establish a die maintenance interval based on burr height progression, not just parts count.
+5. **PPAP update.** Once the customer issues a formal specification for burr height, submit a PPAP update (at minimum a control plan revision and MSA for the new characteristic).
+
+**Key Indicators:**
+- Burr height typically increases with die wear — plot burr height vs. parts since last die sharpen to establish the maintenance interval
+- "Deburr per shop practice" without quantification is a common specification deficiency — the corrective action is a drawing change, not a process change
+- The customer's 4.2% reject rate suggests your process is close to the threshold — a small process improvement (die maintenance interval) may reduce the rate below detection
+
+---
+
+### Edge Case 12: Cross-Contamination in Multi-Product Manufacturing
+
+**Situation:**
+Your pharmaceutical contract manufacturer runs tablet compression on Line 3 for both Product A (a controlled substance, Schedule III) and Product B (an over-the-counter supplement). Changeover between products follows your validated cleaning procedure (cleaning validation study CV-2023-011). During a routine post-cleaning swab analysis before starting Product B, the QC lab reports trace levels of Product A's active ingredient at 0.8 ppm — your validated cleaning limit is 1.0 ppm based on MACO (Maximum Allowable Carryover) calculation. The result is within specification, so the line is released for production.
+
+Two weeks later, the FDA requests your cleaning validation data during an inspection. The investigator points out that your MACO calculation used the maximum daily dose of Product B (the "contaminated" product) as 10 grams, but the actual maximum daily dose on the current label is 15 grams (the label was updated 6 months ago, but the MACO calculation was not revised). Recalculating with the correct maximum daily dose, the cleaning limit should be 0.67 ppm — and the 0.8 ppm result now exceeds the corrected limit.
+
+**Why It's Tricky:**
+The cleaning validation was "validated" but the underlying calculation is now incorrect. This means: (1) every batch of Product B produced since the label change may have been exposed to unacceptable levels of Product A (a controlled substance, adding regulatory severity), (2) your cleaning validation program has a gap — it doesn't trigger recalculation when the inputs change, and (3) the FDA investigator has identified a systemic quality system failure, not just an isolated event.
+
+**Common Mistake:**
+Arguing that 0.8 ppm is toxicologically insignificant. The FDA doesn't operate on "it's probably fine" — they operate on validated limits derived from documented calculations. If the calculation is wrong, the limit is wrong, and the validation is invalid.
+
+**Expert Approach:**
+1. **Acknowledge the finding.** Do not debate the arithmetic with the FDA investigator. The calculation error is factual.
+2. **Immediate containment.** Place a hold on all in-process and unreleased Product B lots manufactured since the label change. Review the cleaning verification results for every changeover in that period. For lots where the cleaning result exceeded the corrected 0.67 ppm limit, conduct a risk assessment on the actual patient exposure.
+3. **Toxicological risk assessment.** Engage your toxicologist or a qualified consultant to assess the actual risk. At 0.8 ppm of Product A in Product B with a maximum daily dose of 15g, the maximum daily exposure to Product A is 12 µg. Is this below the ADI (Acceptable Daily Intake) for Product A's active ingredient? If yes, document this as a secondary justification — but it doesn't fix the process gap.
+4. **Recalculate and revalidate.** Update the MACO calculation with the correct inputs. If the new limit (0.67 ppm) requires a different cleaning procedure, validate the new procedure. If the existing cleaning procedure can meet the new limit (review all historical data), document the cleaning verification with the new limit.
+5. **Systemic corrective action.** The root cause is not the arithmetic error — it's the absence of a change control linkage between product labeling changes and cleaning validation inputs. The CAPA must establish a formal review trigger: any change to maximum daily dose, therapeutic dose, or product formulation triggers a review of all affected MACO calculations.
+6. **Batch disposition.** For lots where Product B was produced with cleaning results between 0.67 and 1.0 ppm: if the toxicological assessment shows the exposure is within ADI, the lots may be dispositioned as acceptable with documentation. If exposure exceeds ADI, the lots must be rejected.
+
+**Key Indicators:**
+- The MACO calculation inputs (maximum daily dose, minimum daily dose of contaminating product, safety factor) must be traceable to current product documentation
+- A cleaning validation that hasn't been reviewed after a product change is not validated — it's out of date
+- Controlled substance cross-contamination adds DEA regulatory obligations on top of FDA obligations
+- The systemic fix (change control linkage) is more important than the specific calculation correction
+
+---
+
+### Edge Case 13: Supplier Ships Correct Part but Wrong Material Certification
+
+**Situation:**
+Your aerospace receiving inspection accepts a lot of 200 titanium fasteners (Ti-6Al-4V per AMS 4928) from a qualified supplier. The CoC shows the correct material specification. Your incoming dimensional inspection on a sample of 13 pieces passes. The parts are released into production. During assembly, one of your technicians notices the fasteners seem to machine differently during a modification step — they're cutting "easier" than expected for Ti-6Al-4V. You pull a part and send it for material verification via handheld XRF. The result shows the parts are commercially pure (CP) titanium (Grade 2), not Ti-6Al-4V. The CoC is for the correct material, but the actual parts are wrong.
+
+**Why It's Tricky:**
+CP titanium Grade 2 and Ti-6Al-4V are both titanium, and visually indistinguishable. The CoC was correct for the material the supplier intended to ship, but a lot mix-up at the supplier's warehouse resulted in the wrong material being shipped. Your incoming inspection checked dimensions (which happen to be identical between the two materials) but did not perform material verification testing.
+
+In aerospace, this is a potential counterfeit/suspect part situation per AS9100 §8.1.4, even if it was an innocent mix-up. CP Grade 2 has significantly lower yield and tensile strength than Ti-6Al-4V (345 MPa vs. 880 MPa yield) — a safety-critical difference on a structural fastener.
+
+**Common Mistake:**
+Assuming the parts can be sorted by XRF and the wrong material returned. While that's eventually the disposition, the immediate priority is containment: how many of the 200 fasteners have already been installed in assemblies? Those assemblies may need to be torn down and the fasteners replaced.
+
+**Expert Approach:**
+1. **Immediate quarantine of all remaining fasteners.** Mark as suspect; do not use for any purpose until material verification is complete.
+2. **Containment — trace forward.** How many of the 200 fasteners have been consumed in production? Which assemblies? Are any of those assemblies already shipped to the customer? Each installed CP titanium fastener in a structure designed for Ti-6Al-4V is a potential structural failure in service.
+3. **100% material verification on remaining stock.** XRF every remaining fastener. Separate confirmed Ti-6Al-4V (if any) from confirmed CP Grade 2.
+4. **Engineering assessment on installed fasteners.** For each assembly containing suspect fasteners, engineering must evaluate: (a) the specific loading condition on each fastener location, (b) whether CP Grade 2 meets the structural requirement at that location (it may for lightly loaded positions), and (c) whether the assembly can be reworked (remove and replace the fastener) without damaging the structure.
+5. **Customer notification.** For shipped assemblies, notify the customer immediately with traceability data. The customer must evaluate their own installation context and downstream assemblies.
+6. **Supplier investigation.** This is a material traceability failure at the supplier. Issue a SCAR demanding: (a) root cause of the lot mix-up, (b) containment of other orders that may have been affected by the same mix-up, (c) implementation of positive material identification (PMI) as a pre-shipment verification step. This is a Level 2 or Level 3 escalation depending on whether the supplier has had material-related non-conformances before.
+7. **GIDEP reporting.** If the investigation suggests the material substitution was anything other than an innocent warehouse mix-up, report to GIDEP per AS9100 counterfeit prevention requirements.
+8. **Incoming inspection update.** Add PMI (XRF or OES) to the incoming inspection plan for all structural material lots, regardless of supplier qualification level. CoC reliance without material verification is a known vulnerability for material mix-ups.
+
+**Key Indicators:**
+- The machinability difference noticed by the technician is a real and reliable indicator — CP titanium machines significantly differently from Ti-6Al-4V (lower cutting forces, different chip formation)
+- XRF can distinguish Grade 2 from Ti-6Al-4V quickly by the absence of aluminum and vanadium peaks
+- The safety risk depends entirely on the application — a CP Grade 2 fastener in a lightly loaded panel is probably fine; the same fastener in a primary structure fitting is a safety-of-flight concern
+- Lot traceability from the supplier's heat/melt lot number through their inventory system to your PO is the critical investigation path
+
+---
+
+### Edge Case 14: CAPA System Backlog Creating Systemic Risk
+
+**Situation:**
+Your quality management system currently has 147 open CAPAs. Of these, 62 are past their target closure date, with 23 overdue by more than 6 months. The quality team of 4 engineers is overwhelmed. Management's response has been to hire a temporary contractor to "clear the backlog." Your registrar audit is in 8 weeks, and the auditor will evaluate CAPA system effectiveness. FDA conducted an inspection 18 months ago and noted a 483 observation about CAPA timeliness; you committed to improvement in your response.
+
+**Why It's Tricky:**
+The backlog itself is a symptom, and the proposed solution (hire a contractor to "close" CAPAs) is likely to create a bigger problem than it solves. A contractor who doesn't understand your processes, products, and quality history will either (a) close CAPAs with superficial effectiveness evidence, or (b) take months to ramp up and not clear the backlog in time.
+
+The deeper issue: 147 open CAPAs in a 4-person quality team means the system is initiating too many CAPAs, not that the team is closing too few. If every NCR and every minor audit finding generates a CAPA, the system is undifferentiated — everything is treated the same, so nothing gets adequate attention.
+
+**Common Mistake:**
+Mass-closing CAPAs to reduce the count. Closing CAPAs without verified effectiveness is worse than having them open — it's a systemic falsification of the quality record. An auditor who sees 60 CAPAs closed in the last 2 weeks before an audit will investigate the closure quality, and finding superficial closures is a major finding.
+
+**Expert Approach:**
+1. **Triage the 147 open CAPAs.** Categorize each into one of four buckets:
+ - **Active and valid:** Root cause is systemic, corrective action is in progress or effective. These stay open and get prioritized.
+ - **Should not have been CAPAs:** Isolated non-conformances that were over-escalated to CAPA. These should be downgraded to NCR dispositions with documented rationale for why CAPA was not required. This is not "closing for convenience" — it's applying correct CAPA initiation criteria retroactively.
+ - **Duplicate or overlapping:** Multiple CAPAs addressing the same root cause from different trigger events. Consolidate into a single CAPA with all triggers linked.
+ - **Stale and no longer applicable:** Process or product has changed since the CAPA was initiated, making the original issue moot. Close with documented rationale that the original condition no longer exists.
+2. **Right-size the CAPA pipeline.** After triage, the active CAPA count should drop to 40-60 (manageable for a 4-person team at ~10-15 CAPAs per engineer). Prioritize by risk: safety and regulatory CAPAs first, customer-facing CAPAs second, internal improvement CAPAs third.
+3. **Fix the initiation criteria.** Update the CAPA initiation procedure with clear, documented criteria for what warrants a CAPA vs. what is handled at the NCR level. Train the quality team on the updated criteria. This is the actual corrective action for the backlog — preventing future over-initiation.
+4. **Demonstrate systemic improvement at audit.** Present the triage analysis, the updated initiation criteria, the prioritization methodology, and the current CAPA metrics (average closure time, effectiveness rate for closed CAPAs). An auditor who sees a thoughtful, risk-based approach to CAPA management will view this far more favorably than a frantic mass-closure.
+5. **Address the FDA commitment.** Your 483 response committed to improvement in CAPA timeliness. The triage and process change demonstrate systemic improvement, which is what FDA expects. Simply clearing the backlog without fixing the systemic cause would be repeating the same failure.
+
+**Key Indicators:**
+- CAPA count per engineer is the capacity metric — more than 15 active CAPAs per engineer indicates either over-initiation or under-resourcing
+- The ratio of CAPAs initiated to CAPAs closed per month shows whether the pipeline is growing or shrinking
+- Effectiveness rate (CAPAs closed with verified effectiveness, no recurrence) is more important than closure rate
+- Auditors assess CAPA system maturity, not CAPA count — a mature system has few, well-managed CAPAs
+
+**Documentation Required:**
+- CAPA triage register with categorization and rationale for each CAPA
+- Updated CAPA initiation procedure (before and after revision)
+- Management review presentation showing backlog analysis and improvement plan
+- Metrics dashboard showing CAPA pipeline health (open count, aging, closure rate, effectiveness rate)
+- Training records for quality team on updated initiation criteria
+- Communication to management on the root cause of the backlog (over-initiation, not under-performance)
+
+---
+
+### Edge Case 15: Process Validation Deviation During FDA-Regulated Production
+
+**Situation:**
+Your medical device manufacturing facility completed process validation (IQ/OQ/PQ) for an ultrasonic welding process 18 months ago. The validated parameters include a weld force of 800N ±50N, amplitude of 40µm, and weld time of 0.6 seconds. During routine production monitoring, the quality engineer notices that the weld force has been running at 760N for the last 3 production lots — technically within the validated range (750-850N), but at the very bottom. The process has not been formally changed. Upon investigation, the force transducer was recalibrated 4 weeks ago, and the calibration adjustment shifted the reading by approximately 40N. The actual physical weld force has likely been consistent — it's the measurement that shifted.
+
+But there's a catch: the process validation was performed with the old calibration. If the transducer was reading 40N high during validation, the actual weld force during PQ was 760-810N, not the documented 800-850N. This means the validation data may not represent what was actually validated.
+
+**Why It's Tricky:**
+This is not a simple calibration adjustment — it's a retroactive question about the validity of the process validation itself. If the force transducer was reading high during validation, the documented validated range (750-850N indicated) actually corresponded to 710-810N actual force. The question becomes: was the process validated at the range you thought it was validated at?
+
+For FDA 21 CFR 820.75, process validation must demonstrate that the process produces results consistently meeting predetermined specifications. If the validation data was collected with a biased instrument, the validation conclusion may be unsound.
+
+**Common Mistake:**
+Ignoring the implication because "the process hasn't changed." The process may not have changed, but your understanding of what was validated has changed. This matters for FDA because the validation must be scientifically sound, and a 40N measurement bias on an 800N nominal process (5% bias) is not trivial.
+
+The second mistake: invalidating the process and halting production for a full revalidation. This may be an overreaction if the product quality data (test results, field performance) supports that the process has been producing conforming product throughout.
+
+**Expert Approach:**
+1. **Quantify the calibration shift.** Review the calibration records — what was the as-found reading vs. the as-left reading during the last calibration? If the as-found was 40N high and the as-left is now correct, the shift is documented.
+2. **Retrospective data analysis.** Collect all product quality data (weld pull-test results, leak test results, or whatever the product-level test is that verifies weld integrity) from the entire period between calibrations. If the product quality data shows consistent, conforming results throughout, this is strong evidence that the process, regardless of the measurement bias, was producing acceptable product.
+3. **Impact assessment on validation.** Recalculate the process capability from the PQ study using the corrected force values (subtract the 40N bias from all documented force readings). If the corrected data still demonstrates capability (Cpk ≥ 1.33) within the specification range, the validation conclusion remains sound even with the adjusted values.
+4. **Protocol for validated range.** If the corrected data shifts the validated range, determine whether the current operating point (760N indicated = 760N actual with corrected calibration) falls within the corrected validated range. If yes, no action needed beyond documentation. If no, a bridging validation study may be required to extend the validated range.
+5. **Calibration program improvement.** The root cause is that the calibration program did not evaluate the impact of calibration adjustments on process validation status. The CAPA should establish a change control trigger: any calibration adjustment exceeding a defined threshold (e.g., > 2% of nominal) triggers a review of the impact on process validation.
+6. **Documentation.** File this as a deviation to the process validation protocol. Document the impact assessment, the retrospective data analysis, the conclusion on validation status, and the corrective action. This creates the audit trail that demonstrates you identified, evaluated, and resolved the issue — which is what FDA expects.
+
+**Key Indicators:**
+- The ratio of calibration shift to process tolerance determines severity (40N shift on a ±50N tolerance = 80% of tolerance, which is significant)
+- Product-level test data is the ultimate evidence of process acceptability — it measures the output, not the input
+- Calibration as-found/as-left data should always be evaluated for process validation impact, not just instrument accuracy
+
+**Documentation Required:**
+- Calibration certificate showing as-found and as-left values
+- Retrospective product quality data analysis with statistical summary
+- Impact assessment on process validation (corrected PQ data analysis)
+- Deviation report to process validation protocol
+- Updated calibration program procedure requiring validation impact assessment
+
+---
+
+## Quick Reference: Edge Case Pattern Recognition
+
+The edge cases above share common patterns. When you encounter a quality situation that feels complex, check which pattern(s) apply:
+
+### Pattern A: Specification Gap
+**Signature:** Parts meet the documented specification but fail in application.
+**Edge cases:** 3 (SPC in-control but complaints rising), 6 (audit finding challenging practice), 11 (customer rejects lot that passed inspection)
+**Key question:** Is the specification adequate for the functional requirement?
+**Default action:** Collaborate with the customer/user to quantify the real requirement.
+
+### Pattern B: Measurement System Integrity
+**Signature:** The quality data says everything is fine, but reality disagrees.
+**Edge cases:** 1 (field failure with no internal detection), 4 (shipped product with calibration issue), 8 (intermittent defect can't reproduce), 10 (go/no-go vs. variable gauging), 15 (calibration shift affects validation)
+**Key question:** Is the measurement system capable of detecting the actual failure mode?
+**Default action:** Evaluate measurement system against the failure mode, not just the specification.
+
+### Pattern C: Trust Breakdown
+**Signature:** Data or documentation cannot be relied upon.
+**Edge cases:** 2 (falsified CoCs), 13 (wrong material with correct cert)
+**Key question:** What is the full scope of potentially affected product?
+**Default action:** Independent verification; do not rely on the compromised data source.
+
+### Pattern D: Systemic Process Failure
+**Signature:** The corrective action treats a symptom; the problem recurs.
+**Edge cases:** 5 (CAPA addresses symptom not root cause), 7 (multiple root causes), 14 (CAPA backlog)
+**Key question:** Is the root cause analysis rigorous enough?
+**Default action:** Restart RCA with fresh team and more rigorous methodology.
+
+### Pattern E: Competing Priorities
+**Signature:** Quality requirements conflict with supply or business constraints.
+**Edge cases:** 9 (sole-source with quality problems), 12 (cross-contamination with supply implications)
+**Key question:** What is the minimum acceptable quality action that maintains regulatory compliance?
+**Default action:** Risk-based approach with parallel paths (fix the problem AND develop alternatives).
+
+### Cross-Referencing Edge Cases with Decision Frameworks
+
+| Edge Case | Primary Decision Framework | Secondary Framework |
+|---|---|---|
+| 1. Field failure no internal detection | CAPA initiation criteria | FDA reporting obligations |
+| 2. Falsified CoCs | Supplier escalation ladder (Level 4-5) | NCR disposition (containment scope) |
+| 3. SPC in-control, complaints rising | Cp/Cpk interpretation | Specification adequacy review |
+| 4. NC on shipped product | NCR disposition (containment) | Customer notification protocol |
+| 5. CAPA addresses symptom | RCA method selection (upgrade methodology) | CAPA effectiveness verification |
+| 6. Audit finding challenges practice | Audit response protocol | Risk-based process change |
+| 7. Multiple root causes | RCA method selection (Ishikawa/FTA) | CAPA action hierarchy |
+| 8. Intermittent defect | Measurement system evaluation | SPC chart selection |
+| 9. Sole-source quality problems | Supplier develop vs. switch | MRB economic model |
+| 10. NC during regulatory audit | Regulatory response protocol | CAPA timeliness standards |
+| 11. Customer rejects despite passing | Specification gap analysis | Control plan update |
+| 12. Cross-contamination | Cleaning validation | FDA field action determination |
+| 13. Wrong material, correct cert | Counterfeit prevention (AS9100) | Incoming inspection update |
+| 14. CAPA backlog | CAPA initiation criteria triage | Management review |
+| 15. Validation deviation | Process validation impact assessment | Calibration program improvement |
diff --git a/skills/quant-analyst/SKILL.md b/skills/quant-analyst/SKILL.md
index 9ce77053..c84d4b6f 100644
--- a/skills/quant-analyst/SKILL.md
+++ b/skills/quant-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: quant-analyst
-description: "Build financial models, backtest trading strategies, and analyze"
+description: |
+ Build financial models, backtest trading strategies, and analyze
market data. Implements risk metrics, portfolio optimization, and statistical
arbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or
risk analysis.
diff --git a/skills/reference-builder/SKILL.md b/skills/reference-builder/SKILL.md
index 83611fa8..d66d4b65 100644
--- a/skills/reference-builder/SKILL.md
+++ b/skills/reference-builder/SKILL.md
@@ -1,6 +1,7 @@
---
name: reference-builder
-description: "Creates exhaustive technical references and API documentation."
+description: |
+ Creates exhaustive technical references and API documentation.
Generates comprehensive parameter listings, configuration guides, and
searchable reference materials. Use PROACTIVELY for API docs, configuration
references, or complete technical specifications.
diff --git a/skills/returns-reverse-logistics/SKILL.md b/skills/returns-reverse-logistics/SKILL.md
new file mode 100644
index 00000000..fde9d64d
--- /dev/null
+++ b/skills/returns-reverse-logistics/SKILL.md
@@ -0,0 +1,231 @@
+---
+name: returns-reverse-logistics
+description: >
+ Codified expertise for returns authorisation, receipt and inspection,
+ disposition decisions, refund processing, fraud detection, and warranty
+ claims management. Informed by returns operations managers with 15+ years
+ experience. Includes grading frameworks, disposition economics, fraud
+ pattern recognition, and vendor recovery processes. Use when handling
+ product returns, reverse logistics, refund decisions, return fraud
+ detection, or warranty claims.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🔄"
+---
+
+## When to Use
+
+Use this skill when managing the product return lifecycle, including authorization, physical inspection, making disposition decisions (e.g., restock vs. liquidator), detecting return fraud, or processing warranty claims.
+
+# Returns & Reverse Logistics
+
+## Role and Context
+
+You are a senior returns operations manager with 15+ years handling the full returns lifecycle across retail, e-commerce, and omnichannel environments. Your responsibilities span return merchandise authorisation (RMA), receiving and inspection, condition grading, disposition routing, refund and credit processing, fraud detection, vendor recovery (RTV), and warranty claims management. Your systems include OMS (order management), WMS (warehouse management), RMS (returns management), CRM, fraud detection platforms, and vendor portals. You balance customer satisfaction against margin protection, processing speed against inspection accuracy, and fraud prevention against false-positive customer friction.
+
+## Core Knowledge
+
+### Returns Policy Logic
+
+Every return starts with policy evaluation. The policy engine must account for overlapping and sometimes conflicting rules:
+
+- **Standard return window:** Typically 30 days from delivery for most general merchandise. Electronics often 15 days. Perishables non-returnable. Furniture/mattresses 30-90 days with specific condition requirements. Extended holiday windows (purchases Nov 1 – Dec 31 returnable through Jan 31) create a surge that peaks mid-January.
+- **Condition requirements:** Most policies require original packaging, all accessories, and no signs of use beyond reasonable inspection. "Reasonable inspection" is where disputes live — a customer who removed laptop screen protector film has technically altered the product but this is normal unboxing behaviour.
+- **Receipt and proof of purchase:** POS transaction lookup by credit card, loyalty number, or phone number has largely replaced paper receipts. Gift receipts entitle the bearer to exchange or store credit at the purchase price, never cash refund. No-receipt returns are capped (typically $50-75 per transaction, 3 per rolling 12 months) and refunded at lowest recent selling price.
+- **Restocking fees:** Applied to opened electronics (15%), special-order items (20-25%), and large/bulky items requiring return shipping coordination. Waived for defective products or fulfilment errors. The decision to waive for customer goodwill requires margin awareness — waiving a $45 restocking fee on a $300 item with 28% margin costs more than it appears.
+- **Cross-channel returns:** Buy-online-return-in-store (BORIS) is expected by customers and operationally complex. Online prices may differ from store prices. The refund should match the original purchase price, not the current store shelf price. Inventory system must accept the unit back into store inventory or flag for return-to-DC.
+- **International returns:** Duty drawback eligibility requires proof of re-export within the statutory window (typically 3-5 years depending on country). Return shipping costs often exceed product value for low-cost items — offer "returnless refund" when shipping exceeds 40% of product value. Customs declarations for returned goods differ from original export documentation.
+- **Exceptions:** Price-match returns (customer found it cheaper), buyer's remorse beyond window with compelling circumstances, defective products outside warranty, and loyalty tier overrides (top-tier customers get extended windows and waived fees) all require judgment frameworks rather than rigid rules.
+
+### Inspection and Grading
+
+Returned products require consistent grading that drives disposition decisions. Speed and accuracy are in tension — a 30-second visual inspection moves volume but misses cosmetic defects; a 5-minute functional test catches everything but creates bottleneck at scale:
+
+- **Grade A (Like New):** Original packaging intact, all accessories present, no signs of use, passes functional test. Restockable as new or "open box" with full margin recovery (85-100% of original retail). Target inspection time: 45-90 seconds.
+- **Grade B (Good):** Minor cosmetic wear, original packaging may be damaged or missing outer sleeve, all accessories present, fully functional. Restockable as "open box" or "renewed" at 60-80% of retail. May need repackaging ($2-5 per unit). Target inspection time: 90-180 seconds.
+- **Grade C (Fair):** Visible wear, scratches, or minor damage. Missing accessories that cost <10% of unit value. Functional but cosmetically impaired. Sells through secondary channels (outlet, marketplace, liquidation) at 30-50% of retail. Refurbishment possible if cost < 20% of recovered value.
+- **Grade D (Salvage/Parts):** Non-functional, heavily damaged, or missing critical components. Salvageable for parts or materials recovery at 5-15% of retail. If parts recovery isn't viable, route to recycling or destruction.
+
+Grading standards vary by category. Consumer electronics require functional testing (power on, screen check, connectivity) adding 2-4 minutes per unit. Apparel inspection focuses on stains, odour, stretched fabric, and missing tags — experienced inspectors use the "arm's length sniff test" and UV light for stain detection. Cosmetics and personal care items are almost never restockable once opened due to health regulations.
+
+### Disposition Decision Trees
+
+Disposition is where returns either recover value or destroy margin. The routing decision is economics-driven:
+
+- **Restock as new:** Only Grade A with complete packaging. Product must pass any required functional/safety testing. Relabelling or resealing may trigger regulatory issues (FTC "used as new" enforcement). Best for high-margin items where the restocking cost ($3-8 per unit) is trivial relative to recovered value.
+- **Repackage and sell as "open box":** Grade A with damaged packaging or Grade B items. Repackaging cost ($5-15 depending on complexity) must be justified by the margin difference between open-box and next-lower channel. Electronics and small appliances are the sweet spot.
+- **Refurbish:** Economically viable when refurbishment cost < 40% of the refurbished selling price, and a refurbished sales channel exists (certified refurbished program, manufacturer's outlet). Common for premium electronics, power tools, and small appliances. Requires dedicated refurb station, spare parts inventory, and re-testing capacity.
+- **Liquidate:** Grade C and some Grade B items where repackaging/refurb isn't justified. Liquidation channels include pallet auctions (B-Stock, DirectLiquidation, Bulq), wholesale liquidators (per-pound pricing for apparel, per-unit for electronics), and regional liquidators. Recovery rates: 5-20% of retail. Critical insight: mixing categories in a pallet destroys value — electronics/apparel/home goods pallets sell at the lowest-category rate.
+- **Donate:** Tax-deductible at fair market value (FMV). More valuable than liquidation when FMV > liquidation recovery AND the company has sufficient tax liability to utilise the deduction. Brand protection: restrict donations of branded products that could end up in discount channels undermining brand positioning.
+- **Destroy:** Required for recalled products, counterfeit items found in the return stream, products with regulatory disposal requirements (batteries, electronics with WEEE compliance, hazmat), and branded goods where any secondary market presence is unacceptable. Certificate of destruction required for compliance and tax documentation.
+
+### Fraud Detection
+
+Return fraud costs US retailers $24B+ annually. The challenge is detection without creating friction for legitimate customers:
+
+- **Wardrobing (wear and return):** Customer buys apparel or accessories, wears them for an event, returns them. Indicators: returns clustered around holidays/events, deodorant residue, makeup on collars, creased/stretched fabric inconsistent with "tried on." Countermeasure: black-light inspection for cosmetic traces, RFID security tags that customers aren't instructed to remove (if the tag is missing, the item was worn).
+- **Receipt fraud:** Using found, stolen, or fabricated receipts to return shoplifted merchandise for cash. Declining as digital receipt lookup replaces paper, but still occurs. Countermeasure: require ID for all cash refunds, match return to original payment method, limit no-receipt returns per ID.
+- **Swap fraud (return switching):** Returning a counterfeit, cheaper, or broken item in the packaging of a purchased item. Common in electronics (returning a used phone in a new phone box) and cosmetics (refilling a container with a cheaper product). Countermeasure: serial number verification at return, weight check against expected product weight, detailed inspection of high-value items before processing refund.
+- **Serial returners:** Customers with return rates > 30% of purchases or > $5,000 in annual returns. Not all are fraudulent — some are genuinely indecisive or bracket-shopping (buying multiple sizes to try). Segment by: return reason consistency, product condition at return, net lifetime value after returns. A customer with $50K in purchases and $18K in returns (36% rate) but $32K net revenue is worth more than a customer with $15K in purchases and zero returns.
+- **Bracketing:** Intentionally ordering multiple sizes/colours with the plan to return most. Legitimate shopping behaviour that becomes costly at scale. Address through fit technology (size recommendation tools, AR try-on), generous exchange policies (free exchange, restocking fee on return), and education rather than punishment.
+- **Price arbitrage:** Purchasing during promotions/discounts, then returning at a different location or time for full-price credit. Policy must tie refund to actual purchase price regardless of current selling price. Cross-channel returns are the primary vector.
+- **Organised retail crime (ORC):** Coordinated theft-and-return operations across multiple stores/identities. Indicators: high-value returns from multiple IDs at the same address, returns of commonly shoplifted categories (electronics, cosmetics, health), geographic clustering. Report to LP (loss prevention) team — this is beyond standard returns operations.
+
+### Vendor Recovery
+
+Not all returns are the customer's fault. Defective products, fulfilment errors, and quality issues have a cost recovery path back to the vendor:
+
+- **Return-to-vendor (RTV):** Defective products returned within the vendor's warranty or defect claim window. Process: accumulate defective units (minimum RTV shipment thresholds vary by vendor, typically $200-500), obtain RTV authorisation number, ship to vendor's designated return facility, track credit issuance. Common failure: letting RTV-eligible product sit in the returns warehouse past the vendor's claim window (often 90 days from receipt).
+- **Defect claims:** When defect rate exceeds the vendor agreement threshold (typically 2-5%), file a formal defect claim for the excess. Requires defect documentation (photos, inspection notes, customer complaint data aggregated by SKU). Vendors will challenge — your data quality determines your recovery.
+- **Vendor chargebacks:** For vendor-caused issues (wrong item shipped from vendor DC, mislabelled products, packaging failures) charge back the full cost including return shipping and processing labour. Requires a vendor compliance program with published standards and penalty schedules.
+- **Credit vs replacement vs write-off:** If the vendor is solvent and responsive, pursue credit. If the vendor is overseas with difficult collections, negotiate replacement product. If the claim is small (< $200) and the vendor is a critical supplier, consider writing it off and noting it in the next contract negotiation.
+
+### Warranty Management
+
+Warranty claims are distinct from returns and follow a different workflow:
+
+- **Warranty vs return:** A return is a customer exercising their right to reverse a purchase (typically within 30 days, any reason). A warranty claim is a customer reporting a product defect within the warranty coverage period (90 days to lifetime). Different systems, different policies, different financial treatment.
+- **Manufacturer vs retailer obligation:** The retailer is typically responsible for the return window. The manufacturer is responsible for the warranty period. Grey area: the "lemon" product that keeps failing within warranty — the customer wants a refund, the manufacturer offers repair, and the retailer is caught in the middle.
+- **Extended warranties/protection plans:** Sold at point of sale with 30-60% margins. Claims against extended warranties are handled by the warranty provider (often a third party). Retailer's role is facilitating the claim, not processing it. Common complaint: customers don't distinguish between retailer return policy, manufacturer warranty, and extended warranty coverage.
+
+## Decision Frameworks
+
+### Disposition Routing by Category and Condition
+
+| Category | Grade A | Grade B | Grade C | Grade D |
+| -------------------- | -------------------- | ---------------------- | ----------------------------------- | ---------------------------- |
+| Consumer Electronics | Restock (test first) | Open box / Renewed | Refurb if ROI > 40%, else liquidate | Parts harvest or e-waste |
+| Apparel | Restock if tags on | Repackage / outlet | Liquidate by weight | Textile recycling |
+| Home & Furniture | Restock | Open box with discount | Liquidate (local, avoid shipping) | Donate or destroy |
+| Health & Beauty | Restock if sealed | Destroy (regulation) | Destroy | Destroy |
+| Books & Media | Restock | Restock (discount) | Liquidate | Recycle |
+| Sporting Goods | Restock | Open box | Refurb if cost < 25% value | Parts or donate |
+| Toys & Games | Restock if sealed | Open box | Liquidate | Donate (if safety-compliant) |
+
+### Fraud Scoring Model
+
+Score each return 0-100. Flag for review at 65+, hold refund at 80+:
+
+| Signal | Points | Notes |
+| ---------------------------------------------------- | ------ | ---------------------------------------- |
+| Return rate > 30% (rolling 12 mo) | +15 | Adjusted for category norms |
+| Item returned within 48 hours of delivery | +5 | Could be legitimate bracket shopping |
+| High-value electronics, serial number mismatch | +40 | Near-certain swap fraud |
+| Return reason changed between initiation and receipt | +10 | Inconsistency flag |
+| Multiple returns same week | +10 | Cumulative with rate signal |
+| Return from address different than shipping address | +10 | Gift returns excluded |
+| Product weight differs > 5% from expected | +25 | Swap or missing components |
+| Customer account < 30 days old | +10 | New account risk |
+| No-receipt return | +15 | Higher risk of receipt fraud |
+| Item in category with high shrink rate | +5 | Electronics, cosmetics, designer apparel |
+
+### Vendor Recovery ROI
+
+Pursue vendor recovery when: `(Expected credit × probability of collection) > (Labour cost + shipping cost + relationship cost)`. Rules of thumb:
+
+- Claims > $500: Always pursue. The math works even at 50% collection probability.
+- Claims $200-500: Pursue if the vendor has a functional RTV programme and you can batch shipments.
+- Claims < $200: Batch until threshold is met, or offset against next PO. Do not ship individual units.
+- Overseas vendors: Increase minimum threshold to $1,000. Add 30% to expected processing time.
+
+### Return Policy Exception Logic
+
+When a return falls outside standard policy, evaluate in this order:
+
+1. **Is the product defective?** If yes, accept regardless of window or condition. Defective products are the company's problem, not the customer's.
+2. **Is this a high-value customer?** (Top 10% by LTV) If yes, accept with standard refund. The retention math almost always favours the exception.
+3. **Is the request reasonable to a neutral observer?** A customer returning a winter coat in March that they bought in November (4 months, outside 30-day window) is understandable. A customer returning a swimsuit in December that they bought in June is less so.
+4. **What is the disposition outcome?** If the product is restockable (Grade A), the cost of the exception is minimal — grant it. If it's Grade C or worse, the exception costs real margin.
+5. **Does granting create a precedent risk?** One-time exceptions for documented circumstances rarely create precedent. Publicised exceptions (social media complaints) always do.
+
+## Key Edge Cases
+
+These are situations where standard workflows fail. Brief summaries — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **High-value electronics with firmware wiped:** Customer returns a laptop claiming defect, but the unit has been factory-reset and shows 6 months of battery cycle count. The device was used extensively and is now being returned as "defective" — grading must look beyond the clean software state.
+
+2. **Hazmat return with improper packaging:** Customer returns a product containing lithium batteries or chemicals without the required DOT packaging. Accepting creates regulatory liability; refusing creates a customer service problem. The product cannot go back through standard parcel return shipping.
+
+3. **Cross-border return with duty implications:** An international customer returns a product that was exported with duty paid. The duty drawback claim requires specific documentation that the customer doesn't have. The return shipping cost may exceed the product value.
+
+4. **Influencer bulk return post-content-creation:** A social media influencer purchases 20+ items, creates content, returns all but one. Technically within policy, but the brand value was extracted. Restocking challenges compound because unboxing videos show the exact items.
+
+5. **Warranty claim on product modified by customer:** Customer replaced a component in a product (e.g., upgraded RAM in a laptop), then claims a warranty defect in an unrelated component (e.g., screen failure). The modification may or may not void the warranty for the claimed defect.
+
+6. **Serial returner who is also a high-value customer:** Customer with $80K annual spend and a 42% return rate. Banning them from returns loses a profitable customer; accepting the behaviour encourages continuation. Requires nuanced segmentation beyond simple return rate.
+
+7. **Return of a recalled product:** Customer returns a product that is subject to an active safety recall. The standard return process is wrong — recalled products follow the recall programme, not the returns programme. Mixing them creates liability and reporting errors.
+
+8. **Gift receipt return where current price exceeds purchase price:** The gift recipient brings a gift receipt. The item is now selling for $30 more than the gift-giver paid. Policy says refund at purchase price, but the customer sees the shelf price and expects that amount.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Standard refund confirmation:** Warm, efficient. Lead with the resolution amount and timeline, not the process.
+- **Denial of return:** Empathetic but clear. Explain the specific policy, offer alternatives (exchange, store credit, warranty claim), provide escalation path. Never leave the customer with no options.
+- **Fraud investigation hold:** Neutral, factual. "We need additional time to process your return" — never say "fraud" or "investigation" to the customer. Provide a timeline. Internal communications are where you document the fraud indicators.
+- **Restocking fee explanation:** Transparent. Explain what the fee covers (inspection, repackaging, value loss) and confirm the net refund amount before processing so there are no surprises.
+- **Vendor RTV claim:** Professional, evidence-based. Include defect data, photos, return volumes by SKU, and reference the vendor agreement section that covers defect claims.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**RMA approval:** Subject: `Return Approved — Order #{order_id}`. Provide: RMA number, return shipping instructions, expected refund timeline, condition requirements.
+
+**Refund confirmation:** Lead with the number: "Your refund of ${amount} has been processed to your [payment method]. Please allow [X] business days."
+
+**Fraud hold notice:** "Your return is being reviewed by our processing team. We expect to have an update within [X] business days. We appreciate your patience."
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------------------------------ | ---------------------------------------------------------------- | ----------------- |
+| Return value > $5,000 (single item) | Supervisor approval required before refund | Before processing |
+| Fraud score ≥ 80 | Hold refund, route to fraud review team | Immediately |
+| Customer has filed chargeback simultaneously | Halt return processing, coordinate with payments team | Within 1 hour |
+| Product identified as recalled | Route to recall coordinator, do not process as standard return | Immediately |
+| Vendor defect rate exceeds 5% for SKU | Notify merchandise and vendor management | Within 24 hours |
+| Third policy exception request from same customer in 12 months | Manager review before granting | Before processing |
+| Suspected counterfeit in return stream | Pull from processing, photograph, notify LP and brand protection | Immediately |
+| Return involves regulated product (pharma, hazmat, medical device) | Route to compliance team | Immediately |
+
+### Escalation Chain
+
+Level 1 (Returns Associate) → Level 2 (Team Lead, 2 hours) → Level 3 (Returns Manager, 8 hours) → Level 4 (Director of Operations, 24 hours) → Level 5 (VP, 48+ hours or any single-item return > $25K)
+
+## Performance Indicators
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------------- | ---------- | ---------- |
+| Return processing time (receipt to refund) | < 48 hours | > 96 hours |
+| Inspection accuracy (grade agreement on audit) | > 95% | < 88% |
+| Restock rate (% of returns restocked as new/open box) | > 45% | < 30% |
+| Fraud detection rate (confirmed fraud caught) | > 80% | < 60% |
+| False positive rate (legitimate returns flagged) | < 3% | > 8% |
+| Vendor recovery rate ($ recovered / $ eligible) | > 70% | < 45% |
+| Customer satisfaction (post-return CSAT) | > 4.2/5.0 | < 3.5/5.0 |
+| Cost per return processed | < $8.00 | > $15.00 |
+
+## Additional Resources
+
+- For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design, improve, or troubleshoot returns and reverse logistics operations**:
+
+- Defining or revising returns policies, grading standards, and disposition routes across channels.
+- Investigating high return rates, fraud patterns, or margin leakage in refunds and write‑offs.
+- Building SOPs, scorecards, or automation flows for RMAs, inspections, RTV, and warranty workflows in retail or e‑commerce environments.
diff --git a/skills/returns-reverse-logistics/references/communication-templates.md b/skills/returns-reverse-logistics/references/communication-templates.md
new file mode 100644
index 00000000..d769c3bf
--- /dev/null
+++ b/skills/returns-reverse-logistics/references/communication-templates.md
@@ -0,0 +1,532 @@
+# Communication Templates — Returns & Reverse Logistics
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing returns-related communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and stage. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RMA Approval Notification](#1-rma-approval-notification)
+2. [RMA Denial Notification](#2-rma-denial-notification)
+3. [Fraud Investigation Hold Notice](#3-fraud-investigation-hold-notice)
+4. [Vendor RTV Claim Submission](#4-vendor-rtv-claim-submission)
+5. [Customer Refund Confirmation](#5-customer-refund-confirmation)
+6. [Restocking Fee Explanation](#6-restocking-fee-explanation)
+7. [Warranty Claim Filing to Manufacturer](#7-warranty-claim-filing-to-manufacturer)
+8. [Disposition Report (Internal)](#8-disposition-report-internal)
+9. [Return Policy Exception Approval](#9-return-policy-exception-approval)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{customer_name}}` | Customer's full name | `Sarah Chen` |
+| `{{customer_email}}` | Customer's email | `schen@email.com` |
+| `{{order_number}}` | Original order number | `ORD-2025-88431` |
+| `{{rma_number}}` | Return merchandise authorisation number | `RMA-2025-04872` |
+| `{{product_name}}` | Product name/description | `Sony WH-1000XM5 Wireless Headphones` |
+| `{{product_sku}}` | Product SKU | `SNY-WH1000XM5-BLK` |
+| `{{serial_number}}` | Product serial number | `SN-8834201` |
+| `{{purchase_date}}` | Original purchase date | `2025-09-14` |
+| `{{purchase_price}}` | Original purchase price | `$349.99` |
+| `{{refund_amount}}` | Refund amount to be issued | `$349.99` |
+| `{{restocking_fee}}` | Restocking fee amount | `$52.50` |
+| `{{payment_method}}` | Original payment method (masked) | `Visa ending in 4821` |
+| `{{return_reason}}` | Customer-stated return reason | `Product not as described` |
+| `{{return_window_end}}` | Last day for standard return | `2025-10-14` |
+| `{{rma_expiry}}` | RMA label/authorisation expiry date | `2025-10-28` |
+| `{{our_company}}` | Our company name | `Apex Commerce Inc.` |
+| `{{our_contact_name}}` | Returns team contact name | `Maria Gonzalez` |
+| `{{our_contact_title}}` | Contact's title | `Returns Operations Supervisor` |
+| `{{our_contact_email}}` | Contact email | `returns@apexcommerce.com` |
+| `{{our_contact_phone}}` | Contact phone | `(800) 555-0199` |
+| `{{vendor_name}}` | Vendor / manufacturer name | `Bose Corporation` |
+| `{{vendor_contact}}` | Vendor returns contact | `James Park, RTV Coordinator` |
+| `{{vendor_account}}` | Vendor account number | `APEX-VND-00342` |
+| `{{defect_description}}` | Description of the defect | `Left ear cup intermittent audio dropout` |
+| `{{inspection_grade}}` | Assigned condition grade | `Grade B` |
+| `{{disposition_route}}` | Disposition decision | `Open box resale` |
+| `{{business_days}}` | Processing time in business days | `5-7` |
+| `{{carrier_name}}` | Return shipping carrier | `UPS Ground` |
+| `{{tracking_number}}` | Return shipment tracking | `1Z999AA10123456784` |
+| `{{warranty_end_date}}` | Warranty expiration date | `2027-09-14` |
+| `{{claim_number}}` | Warranty or vendor claim reference | `WC-2025-11294` |
+
+---
+
+## 1. RMA Approval Notification
+
+### When to Use
+- Customer has initiated a return request and it has been approved under standard policy or an authorised exception.
+- Send immediately upon RMA approval to minimise the time the customer holds the product.
+
+### Tone Guidance
+Warm and efficient. The customer made a decision to return — make it easy. Lead with the actionable information (RMA number, shipping instructions), not the policy.
+
+### What NOT to Say
+- Do not ask "are you sure?" or attempt to dissuade the return at this stage.
+- Do not include language that implies the customer did something wrong.
+- Do not bury the shipping instructions below marketing content.
+
+### Template
+
+**Subject:** Your Return Has Been Approved — RMA# {{rma_number}}
+
+---
+
+Hi {{customer_name}},
+
+Your return for **{{product_name}}** (Order {{order_number}}) has been approved.
+
+**Your RMA Number:** {{rma_number}}
+
+**How to Return Your Item:**
+
+1. Pack the product in its original packaging with all accessories included.
+2. Print the prepaid return label attached to this email.
+3. Attach the label to the outside of the package.
+4. Drop off the package at any {{carrier_name}} location.
+
+**Important Details:**
+- Please ship your return by **{{rma_expiry}}** — the RMA expires after this date.
+- Once we receive and inspect your return, your refund of **{{refund_amount}}** will be processed to your {{payment_method}} within {{business_days}} business days.
+
+If you have any questions, reply to this email or call us at {{our_contact_phone}}.
+
+Best regards,
+{{our_company}} Returns Team
+
+---
+
+## 2. RMA Denial Notification
+
+### When to Use
+- The return request does not meet policy requirements (outside window, excluded category, condition not met).
+- Always provide specific reasons and alternative options.
+
+### Tone Guidance
+Empathetic but clear. The customer will be disappointed. Acknowledge their situation, explain the specific reason (not generic "per our policy"), and always offer at least one alternative path forward.
+
+### What NOT to Say
+- Do not use "unfortunately" more than once.
+- Do not cite policy section numbers or legalistic language.
+- Do not close the door completely — always provide an alternative or escalation path.
+- Never say "there's nothing we can do."
+
+### Template
+
+**Subject:** Regarding Your Return Request — Order {{order_number}}
+
+---
+
+Hi {{customer_name}},
+
+Thank you for contacting us about returning your **{{product_name}}** (Order {{order_number}}, purchased {{purchase_date}}).
+
+After reviewing your request, we're unable to process a standard return because **{{denial_reason}}**.
+
+**We understand this is frustrating, and we want to help. Here are your options:**
+
+{{#if warranty_eligible}}
+- **Warranty claim:** Your product is still covered under the manufacturer's warranty through {{warranty_end_date}}. We can help you file a warranty claim for repair or replacement. Just reply to this email and we'll get that started.
+{{/if}}
+
+{{#if exchange_eligible}}
+- **Exchange:** While we can't offer a refund, we can arrange an exchange for the same product or a similar item. A {{restocking_fee_pct}}% restocking fee would apply.
+{{/if}}
+
+- **Store credit:** We may be able to offer store credit on a case-by-case basis. If you'd like us to review this option, please reply with any additional details about your situation.
+
+- **Speak with a supervisor:** If you feel your situation warrants an exception, we're happy to have a supervisor review your case. Call us at {{our_contact_phone}} and ask for a returns supervisor.
+
+We value your business and want to find a solution that works for you.
+
+Sincerely,
+{{our_contact_name}}
+{{our_company}} Returns Team
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Fraud Investigation Hold Notice
+
+### When to Use
+- A return has been flagged by the fraud scoring system (score ≥ 65) and requires review before the refund is processed.
+- The customer must be informed of the delay without revealing the fraud investigation.
+
+### Tone Guidance
+Neutral and professional. This is a "processing delay" notification. NEVER use the words "fraud," "suspicious," "investigation," or "flagged." The customer may be entirely legitimate — the hold is precautionary.
+
+### What NOT to Say
+- Never say "your return has been flagged."
+- Never reference fraud, theft, or abuse.
+- Never imply the customer has done something wrong.
+- Do not give an indefinite timeline — always commit to a specific review window.
+
+### Template
+
+**Subject:** Your Return is Being Processed — Order {{order_number}}
+
+---
+
+Hi {{customer_name}},
+
+Thank you for your return of **{{product_name}}** (RMA# {{rma_number}}).
+
+We've received your returned item and it is currently undergoing our quality review process. This review ensures we accurately assess the product's condition and process your refund correctly.
+
+**We expect to complete this review within {{review_days}} business days.**
+
+You don't need to do anything at this time. We'll send you a confirmation email once your refund has been processed.
+
+If you have questions in the meantime, you can reach us at {{our_contact_phone}} or reply to this email.
+
+Thank you for your patience,
+{{our_company}} Returns Team
+
+---
+
+### Internal Companion Note (Not Sent to Customer)
+
+**Fraud Review — RMA# {{rma_number}}**
+
+| Field | Detail |
+|---|---|
+| Customer | {{customer_name}} ({{customer_email}}) |
+| Fraud Score | {{fraud_score}} |
+| Primary Signals | {{fraud_signals}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Return Value | {{purchase_price}} |
+| Customer LTV | {{customer_ltv}} |
+| Action Required | {{review_action}} |
+| Review Deadline | {{review_deadline}} |
+| Assigned To | {{reviewer_name}} |
+
+**Review Instructions:** Complete inspection with photo documentation. Verify serial number against order record. Check product weight against expected weight. Compare physical product against product listing. Document findings in the fraud case management system. Recommend: process refund / partial refund / deny with escalation.
+
+---
+
+## 4. Vendor RTV Claim Submission
+
+### When to Use
+- Submitting a return-to-vendor claim for defective products, vendor-caused quality issues, or vendor compliance violations.
+- Attach all supporting documentation (photos, inspection reports, customer complaint data).
+
+### Tone Guidance
+Professional and evidence-based. Vendors respond to data, not complaints. Lead with the facts: SKU, quantity, defect description, return rate data. Reference the vendor agreement section that covers defect claims.
+
+### Template
+
+**Subject:** RTV Claim — {{vendor_account}} — {{claim_number}}
+
+---
+
+{{vendor_contact}},
+
+Please find below our return-to-vendor claim for defective merchandise received under account {{vendor_account}}.
+
+**Claim Reference:** {{claim_number}}
+**Date Submitted:** {{claim_date}}
+**RTV Authorisation #:** {{rtv_auth_number}} (if applicable)
+
+**Claim Details:**
+
+| SKU | Product Name | Qty Defective | Defect Description | Unit Cost | Extended |
+|---|---|---|---|---|---|
+| {{sku_1}} | {{product_1}} | {{qty_1}} | {{defect_1}} | {{cost_1}} | {{ext_1}} |
+| {{sku_2}} | {{product_2}} | {{qty_2}} | {{defect_2}} | {{cost_2}} | {{ext_2}} |
+
+**Total Claim Amount:** {{total_claim_amount}}
+
+**Supporting Documentation (attached):**
+- Defect photographs ({{photo_count}} images)
+- Inspection reports for each SKU
+- Customer return data by SKU (return rate, complaint summary)
+- Original purchase order(s): {{po_numbers}}
+
+**Defect Rate Analysis:**
+- SKU {{sku_1}}: {{defect_rate_1}}% return rate ({{period}}), versus category baseline of {{baseline_rate}}%
+- Excess returns above baseline: {{excess_units}} units
+
+Per Section {{agreement_section}} of our Vendor Agreement dated {{agreement_date}}, defective merchandise exceeding the {{defect_threshold}}% defect rate threshold is eligible for full credit including inbound freight and return processing costs.
+
+**Requested Resolution:** Full merchandise credit of {{total_claim_amount}} plus return processing costs of {{processing_costs}} and inbound freight of {{freight_costs}}, for a total claim of {{grand_total}}.
+
+Please confirm receipt and provide expected credit timeline. Per our agreement, vendor credits are due within {{credit_days}} days of claim submission.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Customer Refund Confirmation
+
+### When to Use
+- Refund has been processed. This is the final communication for a standard return.
+- Send immediately when the refund is initiated (not when it clears the customer's bank).
+
+### Tone Guidance
+Warm and concise. Lead with the refund amount and timeline. The customer wants to know: how much and when.
+
+### Template
+
+**Subject:** Your Refund Has Been Processed — {{refund_amount}}
+
+---
+
+Hi {{customer_name}},
+
+Your refund for **{{product_name}}** (Order {{order_number}}) has been processed.
+
+**Refund Details:**
+- **Amount:** {{refund_amount}}
+- **Refunded to:** {{payment_method}}
+- **Expected arrival:** {{refund_timeline}}
+
+{{#if restocking_fee_applied}}
+A restocking fee of {{restocking_fee}} was applied per our return policy for opened {{product_category}} items. Your original purchase price was {{purchase_price}}.
+{{/if}}
+
+{{#if store_credit}}
+Your store credit of {{store_credit_amount}} has been added to your account and is available immediately.
+{{/if}}
+
+Thank you for shopping with us. If there's anything else we can help with, we're here.
+
+Best,
+{{our_company}} Customer Care
+
+---
+
+## 6. Restocking Fee Explanation
+
+### When to Use
+- When a restocking fee is applied and the customer questions it (either proactively at the time of return or in response to a complaint).
+
+### Tone Guidance
+Transparent and factual. Explain what the fee covers. Do not be apologetic about the policy, but do be clear about the specific dollar amounts.
+
+### Template
+
+**Subject:** Re: Your Return — Restocking Fee Details
+
+---
+
+Hi {{customer_name}},
+
+I understand you have a question about the restocking fee on your return of **{{product_name}}**.
+
+Here's a breakdown:
+
+| Item | Amount |
+|---|---|
+| Original purchase price | {{purchase_price}} |
+| Restocking fee ({{restocking_fee_pct}}%) | -{{restocking_fee}} |
+| **Your refund** | **{{refund_amount}}** |
+
+**Why a restocking fee is applied:**
+
+Our return policy includes a {{restocking_fee_pct}}% restocking fee for opened {{product_category}} products. This fee covers the cost of inspecting, testing, and repackaging the product so it can be offered to the next customer at a reduced "open box" price. Once an item has been opened and used, it can no longer be sold as new, and the restocking fee helps offset this value difference.
+
+**Please note:** Restocking fees are waived for defective products and fulfilment errors. If you believe your product was defective, please let us know and we'll review — if a defect is confirmed, we'll refund the restocking fee.
+
+If you'd like to discuss further, please call us at {{our_contact_phone}} or reply to this email.
+
+Regards,
+{{our_contact_name}}
+{{our_company}} Returns Team
+
+---
+
+## 7. Warranty Claim Filing to Manufacturer
+
+### When to Use
+- Filing a warranty claim with the manufacturer on behalf of the customer or for retailer-held defective inventory.
+
+### Tone Guidance
+Formal and thorough. Manufacturers process warranty claims based on documentation quality. Include everything upfront to avoid back-and-forth.
+
+### Template
+
+**Subject:** Warranty Claim — {{claim_number}} — {{product_name}}
+
+---
+
+To: {{manufacturer_warranty_dept}}
+
+**Warranty Claim Submission**
+
+| Field | Detail |
+|---|---|
+| Claim Reference | {{claim_number}} |
+| Retailer Account | {{retailer_account_number}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Serial Number | {{serial_number}} |
+| Purchase Date | {{purchase_date}} |
+| Warranty Expiration | {{warranty_end_date}} |
+| Defect Description | {{defect_description}} |
+| Date Defect Reported | {{defect_report_date}} |
+
+**Customer Information:**
+- Name: {{customer_name}}
+- Original Order: {{order_number}}
+- Customer has been provided interim resolution: {{interim_resolution}}
+
+**Defect Documentation:**
+- Photographs of defect: attached ({{photo_count}} images)
+- Functional test results: {{test_results}}
+- Customer description of defect: "{{customer_defect_statement}}"
+
+**Product Condition:**
+- Physical condition: {{physical_condition}}
+- Modifications: {{modifications_noted}}
+- Accessories present: {{accessories_status}}
+
+**Requested Resolution:** {{requested_resolution}} (repair / replacement / credit)
+
+Please confirm receipt and provide claim processing timeline. The customer is awaiting resolution.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 8. Disposition Report (Internal)
+
+### When to Use
+- Weekly or monthly summary of returns disposition outcomes for management review.
+- Used to track recovery rates, identify disposition efficiency opportunities, and monitor fraud trends.
+
+### Tone Guidance
+Data-first, concise. Management reads these for trends and exceptions, not prose.
+
+### Template
+
+**Subject:** Returns Disposition Report — {{report_period}}
+
+---
+
+## Summary
+
+| Metric | This Period | Prior Period | Trend |
+|---|---|---|---|
+| Total returns received | {{total_returns}} | {{prior_total}} | {{trend_total}} |
+| Total return value | {{total_value}} | {{prior_value}} | {{trend_value}} |
+| Average return value | {{avg_value}} | {{prior_avg}} | {{trend_avg}} |
+| Restock rate (Grade A) | {{restock_pct}}% | {{prior_restock}}% | {{trend_restock}} |
+| Open box / renewed rate (Grade B) | {{open_box_pct}}% | {{prior_open_box}}% | {{trend_ob}} |
+| Liquidation rate (Grade C) | {{liquidation_pct}}% | {{prior_liq}}% | {{trend_liq}} |
+| Destroy / recycle rate (Grade D) | {{destroy_pct}}% | {{prior_destroy}}% | {{trend_destroy}} |
+| Net recovery rate | {{recovery_pct}}% | {{prior_recovery}}% | {{trend_recovery}} |
+| Fraud flags triggered | {{fraud_flags}} | {{prior_fraud}} | {{trend_fraud}} |
+| Confirmed fraud cases | {{confirmed_fraud}} | {{prior_confirmed}} | {{trend_confirmed}} |
+| Vendor RTV claims filed | {{rtv_count}} ({{rtv_value}}) | {{prior_rtv}} | {{trend_rtv}} |
+
+## Top Return Reasons
+
+| Reason | Count | % of Total | Avg Value |
+|---|---|---|---|
+| {{reason_1}} | {{count_1}} | {{pct_1}}% | {{avg_1}} |
+| {{reason_2}} | {{count_2}} | {{pct_2}}% | {{avg_2}} |
+| {{reason_3}} | {{count_3}} | {{pct_3}}% | {{avg_3}} |
+| {{reason_4}} | {{count_4}} | {{pct_4}}% | {{avg_4}} |
+| {{reason_5}} | {{count_5}} | {{pct_5}}% | {{avg_5}} |
+
+## Top SKUs by Return Volume
+
+| SKU | Product | Returns | Return Rate | Primary Reason | Action |
+|---|---|---|---|---|---|
+| {{sku_1}} | {{prod_1}} | {{ret_1}} | {{rate_1}}% | {{reason_sku_1}} | {{action_1}} |
+| {{sku_2}} | {{prod_2}} | {{ret_2}} | {{rate_2}}% | {{reason_sku_2}} | {{action_2}} |
+| {{sku_3}} | {{prod_3}} | {{ret_3}} | {{rate_3}}% | {{reason_sku_3}} | {{action_3}} |
+
+## Exceptions and Escalations
+
+- {{exception_summary_1}}
+- {{exception_summary_2}}
+- {{exception_summary_3}}
+
+## Recommendations
+
+- {{recommendation_1}}
+- {{recommendation_2}}
+- {{recommendation_3}}
+
+---
+
+Prepared by: {{our_contact_name}}, {{our_contact_title}}
+Distribution: {{distribution_list}}
+
+---
+
+## 9. Return Policy Exception Approval
+
+### When to Use
+- When an exception to standard return policy has been approved (outside window, missing receipt, condition outside standard acceptance criteria).
+- Documents the exception for audit trail and communicates the decision to the customer.
+
+### Tone Guidance
+Customer-facing version: warm, conveys that you went above and beyond. Internal version: factual, documents the business justification.
+
+### Customer-Facing Template
+
+**Subject:** Good News — Your Return Has Been Approved
+
+---
+
+Hi {{customer_name}},
+
+We've reviewed your return request for **{{product_name}}** (Order {{order_number}}) and we're happy to let you know that we've approved it as a one-time exception.
+
+**Here's what you need to know:**
+
+- **Refund amount:** {{refund_amount}} as {{refund_type}}
+- **How to return:** {{return_instructions}}
+- **RMA Number:** {{rma_number}} (valid through {{rma_expiry}})
+
+{{#if conditions}}
+**Please note:** {{exception_conditions}}
+{{/if}}
+
+We appreciate your loyalty and hope this helps. If you need anything else, we're here.
+
+Best,
+{{our_contact_name}}
+{{our_company}} Customer Care
+
+---
+
+### Internal Approval Record
+
+**Policy Exception Approval**
+
+| Field | Detail |
+|---|---|
+| RMA | {{rma_number}} |
+| Customer | {{customer_name}} ({{customer_email}}) |
+| Order | {{order_number}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Purchase Price | {{purchase_price}} |
+| Refund Amount | {{refund_amount}} |
+| Refund Type | {{refund_type}} |
+| Standard Policy Violation | {{policy_violation}} |
+| Exception Score | {{exception_score}} (per Exception Matrix) |
+| Customer LTV | {{customer_ltv}} |
+| Customer Return Rate | {{customer_return_rate}}% |
+| Business Justification | {{business_justification}} |
+| Approved By | {{approver_name}} ({{approver_title}}) |
+| Approval Date | {{approval_date}} |
+| Precedent Risk | {{precedent_risk}} |
+| Notes | {{approval_notes}} |
diff --git a/skills/returns-reverse-logistics/references/decision-frameworks.md b/skills/returns-reverse-logistics/references/decision-frameworks.md
new file mode 100644
index 00000000..6b84367f
--- /dev/null
+++ b/skills/returns-reverse-logistics/references/decision-frameworks.md
@@ -0,0 +1,823 @@
+# Decision Frameworks — Returns & Reverse Logistics
+
+This reference provides the detailed decision logic, scoring matrices, financial models,
+grading standards, and disposition workflows for returns and reverse logistics operations.
+It is loaded on demand when the agent needs to make or recommend nuanced return-handling
+decisions.
+
+All thresholds, timelines, and cost assumptions reflect US retail and e-commerce operations
+with applicability to omnichannel, pure-play e-commerce, and brick-and-mortar environments.
+
+---
+
+## 1. Disposition Decision Trees by Product Category
+
+### 1.1 Decision Methodology
+
+Every returned item follows a decision tree that routes to the highest-value disposition
+channel. The routing decision is made after grading (see §5) and considers:
+
+1. **Recovered value** at each disposition tier (restock, open box, refurbish, liquidate, donate, destroy)
+2. **Processing cost** for each tier (inspection, repackaging, refurbishment, shipping)
+3. **Time-to-recovery** — cash tied up in returns inventory has a carrying cost
+4. **Regulatory constraints** — some dispositions are prohibited for certain categories
+5. **Brand protection** — premium brands may restrict secondary-market sales
+
+The **net recovery** for any disposition = `(Sale price at channel) - (Processing cost) - (Shipping cost) - (Channel fees)`.
+
+Always route to the disposition with the highest net recovery, subject to regulatory and
+brand constraints.
+
+### 1.2 Consumer Electronics
+
+Consumer electronics are the highest-value and most complex returns category. Serial numbers,
+firmware states, activation locks, and functional testing requirements add cost and time.
+
+```
+RECEIVE → Verify serial number matches RMA
+ ├── Mismatch → Flag for fraud review (swap fraud), HALT processing
+ └── Match → Visual inspection
+ ├── Grade A (no cosmetic defects, all accessories, original packaging)
+ │ └── Functional test (power on, screen, connectivity, battery health)
+ │ ├── Pass → Check activation lock / factory reset status
+ │ │ ├── Locked → Contact customer for unlock, hold 48 hrs
+ │ │ │ ├── Unlocked within 48 hrs → Restock as new
+ │ │ │ └── Not unlocked → Grade B (open box with disclaimer)
+ │ │ └── Clean → Restock as new (full margin recovery)
+ │ └── Fail → Route to refurbishment assessment
+ │ ├── Refurb cost < 40% of refurb selling price → Refurbish
+ │ ├── Refurb cost 40-60% → Liquidate as "for parts / not working"
+ │ └── Refurb cost > 60% → Parts harvest or e-waste recycling
+ ├── Grade B (minor cosmetic wear, accessories complete, packaging damaged)
+ │ └── Functional test
+ │ ├── Pass → Repackage as "open box" or "renewed" (60-80% of retail)
+ │ └── Fail → Refurbishment assessment (same tree as above)
+ ├── Grade C (visible wear, scratches, missing non-essential accessories)
+ │ └── Functional test
+ │ ├── Pass → Sell through secondary channel at 30-50% of retail
+ │ └── Fail → Parts harvest if unit value > $100, else e-waste
+ └── Grade D (heavily damaged, non-functional, missing critical components)
+ └── Parts harvest if any component value > $15, else e-waste recycling
+```
+
+**Category-specific thresholds:**
+- Smartphones: Always verify IMEI against stolen device databases (GSMA) before restocking
+- Laptops: Battery health must be > 80% for Grade A restock; 60-80% triggers Grade B
+- Tablets: Check for MDM (mobile device management) profiles — enterprise tablets may have
+ remote-lock capability that surfaces post-sale
+- Headphones: Hygiene concern — all ear tips/pads replaced before resale ($2-8 per unit)
+- Smart home devices: Factory reset verified; linked account removal confirmed. A smart lock
+ that is still linked to a previous owner's account is unsellable and potentially a safety issue
+
+**Typical processing costs:**
+| Action | Cost per Unit | Time per Unit |
+|--------|--------------|---------------|
+| Visual inspection | $1.50-2.50 | 45-90 seconds |
+| Functional test (basic) | $3.00-5.00 | 2-4 minutes |
+| Functional test (full diagnostic) | $8.00-15.00 | 10-20 minutes |
+| Repackaging | $5.00-12.00 | 3-8 minutes |
+| Refurbishment (minor: screen clean, reset) | $15.00-30.00 | 15-30 minutes |
+| Refurbishment (moderate: component replacement) | $30.00-80.00 | 30-90 minutes |
+| Data wipe (NIST 800-88 compliant) | $5.00-10.00 | 5-15 minutes |
+
+### 1.3 Apparel and Footwear
+
+Apparel returns are high-volume, low-unit-value, and condition-sensitive. Odour, stains,
+and stretched fabric are the primary defects. Speed is critical because fashion depreciates
+rapidly — a trend item loses 10-20% of sellable value per month.
+
+```
+RECEIVE → Scan RMA / order lookup
+ └── Visual inspection (30-60 seconds)
+ ├── Tags attached, no signs of wear
+ │ ├── Original packaging intact → Restock as new
+ │ └── Packaging damaged/missing → Repackage, restock as new (tag is key, not box)
+ ├── Tags removed but no signs of wear
+ │ └── UV light + odour check
+ │ ├── Clean → Restock as "like new" or outlet (80-90% of retail)
+ │ └── Traces detected → Grade C, route to launder/clean assessment
+ │ ├── Cleaning cost < $5 and item value > $30 → Clean and restock as outlet
+ │ └── Cleaning not viable or cost > value threshold → Liquidate by weight
+ ├── Visible wear, stains, or damage
+ │ ├── Premium brand (retail > $100) → Assess repair viability
+ │ │ ├── Repair cost < 20% of outlet price → Repair and sell through outlet
+ │ │ └── Repair not viable → Liquidate (never destroy premium apparel; brand resale exists)
+ │ └── Standard brand → Liquidate by weight ($0.50-2.00/lb) or textile recycling
+ └── Heavily damaged, soiled, or biohazard
+ └── Textile recycling or destroy (biohazard requires specific disposal)
+```
+
+**Apparel-specific considerations:**
+- Seasonal timing is everything: a winter coat returned in February can restock for next season,
+ but the carrying cost of 8 months of storage may exceed liquidation recovery. Decision point:
+ if storage cost > (expected recovery next season × probability of sale) - liquidation value now,
+ liquidate immediately.
+- Footwear: Check sole wear. A shoe worn on carpet for 5 minutes is different from one worn
+ on pavement. Sole scuffing = Grade C minimum. Check for orthotics left inside.
+- Swimwear and intimate apparel: Once hygienic liner is removed, non-returnable per health code
+ in most jurisdictions. If returned, destroy — do not restock or liquidate.
+- Designer/luxury: Authenticate before accepting. Counterfeits in the return stream are
+ increasing. Compare serial numbers, stitching quality, hardware weight against known
+ genuine samples.
+
+### 1.4 Home, Furniture, and Large Goods
+
+Returns of bulky items are expensive — return shipping alone can be $50-200+. The disposition
+decision often happens before the item physically returns.
+
+```
+CUSTOMER INITIATES RETURN →
+ ├── Item value < return shipping cost × 2.5
+ │ └── Offer returnless refund (customer keeps item, full refund)
+ │ Cost justification: returnless refund costs $X (product value).
+ │ Processing the return costs $X (product) + $Y (shipping) + $Z (processing).
+ │ If Y + Z > 40% of X, returnless is cheaper.
+ ├── Item value > threshold AND item is in original packaging
+ │ └── Schedule carrier pickup → Receive → Inspect
+ │ ├── Grade A → Restock (furniture typically restock at 85-95% due to assembly/box condition)
+ │ ├── Grade B → Sell as "open box" in-store (avoid re-shipping; sell from nearest location)
+ │ ├── Grade C → Donate locally (shipping destroyed items is negative ROI)
+ │ └── Grade D → Local disposal (donation or recycling based on materials)
+ └── Item is assembled
+ └── Generally non-returnable once assembled (policy). Exceptions:
+ ├── Defective → Offer replacement parts first, full return if unfixable
+ ├── Missing parts on arrival → Ship missing parts (cheaper than full return)
+ └── Customer insists → Accept but apply 25% restocking fee to cover disassembly/repackaging
+```
+
+### 1.5 Health, Beauty, and Personal Care
+
+Regulatory constraints dominate this category. Once opened, most health and beauty products cannot
+be legally resold due to FDA and state health department regulations.
+
+```
+RECEIVE → Seal integrity check
+ ├── Sealed / unopened
+ │ ├── Expiration date > 6 months out → Restock as new
+ │ ├── Expiration 3-6 months → Restock with markdown or outlet
+ │ └── Expiration < 3 months → Donate (tax benefit > markdown recovery)
+ ├── Opened but appears unused (seal broken, product visually intact)
+ │ └── DESTROY. Cannot verify non-contamination. No restocking of opened health/beauty.
+ │ Exception: Hard goods (hair dryers, electric razors) → treat as electronics tree
+ └── Used
+ └── DESTROY. Biohazard disposal if applicable (used cosmetics applicators, skincare).
+```
+
+**Special cases:**
+- Prescription items: Cannot accept return under any circumstances (most states). Direct
+ customer to pharmacy or manufacturer disposal programme.
+- Supplements/vitamins: Same as cosmetics — once opened, destroy. Sealed returns restock
+ only with lot number verification.
+- Sunscreen: Regulated as OTC drug by FDA. Opened sunscreen is destroyed. Expired sunscreen
+ (even sealed) is destroyed — never sell expired OTC.
+
+### 1.6 Books, Media, and Software
+
+High restock rate, low processing cost. The primary fraud vector is digital content extraction
+(reading/ripping then returning).
+
+```
+RECEIVE → Condition check
+ ├── New condition (no creasing, bending, markings)
+ │ └── Restock as new. Media: verify disc is present and matches case.
+ ├── Minor wear (slight cover bend, shelf wear)
+ │ └── Restock at minor discount or sell through marketplace as "very good"
+ ├── Moderate wear (highlighting, writing, water damage)
+ │ └── Liquidate through bulk book buyers ($0.10-0.50 per book) or donate
+ └── Software / digital media
+ ├── If activation key is unredeemed → Restock
+ ├── If key is redeemed → Cannot resell. Write off. Pursue refund from publisher if within terms.
+ └── Physical media with digital code (game + download) → Sell disc only at reduced price
+```
+
+---
+
+## 2. Fraud Detection Scoring Model
+
+### 2.1 Scoring Architecture
+
+The fraud scoring model assigns points based on observable signals at the time of return
+initiation (pre-receipt signals) and at the time of physical inspection (post-receipt
+signals). The two scores are summed for a composite score.
+
+**Thresholds:**
+| Composite Score | Action |
+|----------------|--------|
+| 0-30 | Process normally. No additional review. |
+| 31-50 | Flag for passive monitoring. Process refund but add customer to watch list for 90 days. |
+| 51-64 | Enhanced inspection. Hold refund until physical inspection is complete and matches RMA description. |
+| 65-79 | Supervisor review. Hold refund. Detailed inspection with photo documentation. Supervisor approves or escalates. |
+| 80-100 | Fraud review team. Refund on hold. Customer contacted for "verification" (never say "fraud"). LP notified. |
+
+### 2.2 Pre-Receipt Signals (scored at return initiation)
+
+| Signal | Points | Logic |
+|--------|--------|-------|
+| Customer return rate > 30% (rolling 12 months, ≥ 5 orders) | +15 | High return rate alone isn't fraud, but it is a risk multiplier. Exclude exchanges from rate calculation. |
+| Return rate > 50% | +25 | Replaces the +15 above. At this rate, the customer is almost certainly bracket-shopping or abusing policy. |
+| Return initiated < 48 hours after delivery confirmation | +5 | Could be legitimate (wrong item, didn't match description) or bracket shopping. Mild signal. |
+| Return reason is "defective" but product category has < 2% defect rate | +10 | "Defective" is used to avoid restocking fees. True defect claims on low-defect products are suspicious. |
+| Return reason changed between online initiation and customer service contact | +10 | Inconsistency suggests the customer is constructing a narrative. |
+| Customer account age < 30 days | +10 | New accounts used for return fraud or testing fraud viability. |
+| Multiple returns in same week (3+) | +10 | Cumulative with return rate signal. Suggests bracket shopping or wardrobing batch. |
+| Return from an address different than the original shipping address | +10 | Excludes gift returns (flagged as gift at order). Otherwise indicates potential organised activity. |
+| Item is in a high-shrink category (electronics, designer, cosmetics) | +5 | These categories have higher fraud incidence. Mild base signal. |
+| No-receipt or no-order-match return | +15 | Receipt fraud is the primary risk vector. Match to payment method or loyalty ID. |
+| Order was placed with a promotion/coupon > 30% off | +5 | Price-arbitrage returns are more common on heavily discounted purchases. |
+| Customer has previously been flagged for fraud review (any outcome) | +15 | Prior flags, even if resolved as legitimate, indicate a pattern worth monitoring. |
+
+### 2.3 Post-Receipt Signals (scored during physical inspection)
+
+| Signal | Points | Logic |
+|--------|--------|-------|
+| Serial number mismatch (does not match the unit sold to this customer) | +40 | Near-certain swap fraud. Verify against order record before escalating — packing errors at fulfilment can cause legitimate mismatches. |
+| Product weight differs > 5% from expected for SKU | +25 | Indicates missing components, swap with lighter/cheaper item, or empty packaging. Weigh before opening. |
+| IMEI/MEID on returned device doesn't match sold device | +40 | Definitive swap fraud for mobile devices. Cross-reference IMEI from order with IMEI on returned device. |
+| Product shows wear inconsistent with stated return reason | +15 | "Changed my mind" return on a laptop with 200 battery cycles suggests extended use. |
+| Tags removed on apparel/footwear with "didn't fit" reason | +10 | Tags removed is consistent with wearing, not just trying on. |
+| Cosmetic traces on apparel (makeup, deodorant, perfume) | +15 | Wardrobing indicator. UV light reveals traces invisible to naked eye. |
+| Packaging has been repacked (tape over tape, non-original inner packaging) | +10 | Could indicate swap (customer repacked a different item) or simply customer repackaging for return. Context-dependent. |
+| Security/RFID tag removed | +20 | Tags that are not customer-removable (hidden tags, sewn-in RFID) should still be present. Removal suggests the item was worn/used in a retail environment. |
+| Product firmware/software shows usage history inconsistent with claim | +15 | Laptop claiming "unopened" but with 6 months of OS updates installed. |
+| Multiple units of same SKU returned (3+) in single return | +10 | Could be legitimate (sizing across colours) or reseller return. Check original order for bulk discount. |
+
+### 2.4 Score Adjustments and Overrides
+
+| Condition | Adjustment |
+|-----------|-----------|
+| Customer lifetime value > $10,000 and net LTV positive | -15 points (floor at 0) |
+| Customer is a verified loyalty programme member (2+ years) | -10 points |
+| Return is an exchange (not refund) | -10 points |
+| Return reason is verified fulfilment error (wrong item shipped) | Set score to 0, process immediately |
+| Return was pre-approved by customer service with case notes | -10 points |
+| Customer has filed a chargeback simultaneously with this return | +20 points (escalate regardless of score) |
+
+### 2.5 False Positive Management
+
+False positives destroy customer relationships. Every customer flagged by the fraud scoring
+system who turns out to be legitimate represents a risk of customer attrition. Manage through:
+
+1. **Never communicate "fraud" to the customer.** Use neutral language: "additional processing
+ time," "verification of your return," "quality review."
+2. **Time-box the review.** Flagged returns must be resolved within 5 business days. If the
+ review cannot conclusively determine fraud within 5 days, process the refund. The cost
+ of a false positive held for 3 weeks exceeds the cost of most fraudulent returns.
+3. **Track false positive rate monthly.** Target: < 3% of total returns flagged are
+ confirmed false positives. If rate exceeds 5%, recalibrate the scoring model.
+4. **Feedback loop:** Every fraud review outcome (confirmed fraud, confirmed legitimate,
+ inconclusive) feeds back into the scoring model calibration. Signals that generate
+ high false-positive rates have their point values reduced.
+
+---
+
+## 3. Vendor Recovery Framework
+
+### 3.1 Return-to-Vendor (RTV) Process
+
+RTV is the primary mechanism for recovering costs on defective products. The process:
+
+```
+Identify RTV-eligible unit (defective, vendor-caused quality issue, mispick at vendor DC)
+ │
+ ├── Check vendor agreement for RTV terms
+ │ ├── RTV window: Typically 90 days from retailer receipt of return (not customer purchase date)
+ │ ├── Minimum shipment value: Usually $200-500 per RTV shipment
+ │ ├── Documentation requirements: Varies by vendor (photos, defect codes, customer complaint data)
+ │ └── RTV authorisation: Some vendors require pre-approval; others accept "open RTV" under agreement
+ │
+ ├── Accumulate RTV-eligible units by vendor
+ │ ├── Stage in designated RTV area (separate from general returns inventory)
+ │ ├── Track aging — units approaching 90-day window need priority shipment
+ │ └── Batch by vendor to meet minimum shipment thresholds
+ │
+ ├── Obtain RTV authorisation (if required)
+ │ ├── Submit RTV request with: SKU, quantity, defect description, photos, customer return rate data
+ │ └── Vendor has 5-10 business days to approve/deny (per most vendor agreements)
+ │
+ ├── Ship to vendor return facility
+ │ ├── Use vendor-provided shipping label (if applicable — vendor pays)
+ │ ├── If retailer pays shipping: deduct from credit claim or use lowest-cost carrier
+ │ └── Track shipment and confirm delivery at vendor facility
+ │
+ └── Track credit issuance
+ ├── Vendor credit should appear within 30-45 days of vendor receipt
+ ├── If no credit at 30 days: first follow-up (email to vendor returns dept)
+ ├── If no credit at 45 days: escalate to vendor account manager
+ ├── If no credit at 60 days: debit memo against next PO (per vendor agreement terms)
+ └── If vendor disputes: provide defect documentation as evidence. Escalate to vendor management.
+```
+
+### 3.2 Defect Rate Monitoring and Claims
+
+Beyond individual RTV, monitor defect rates at the SKU level to identify systemic quality
+issues that trigger formal defect claims:
+
+| Defect Rate (per SKU, rolling 90 days) | Action |
+|----------------------------------------|--------|
+| < 2% | Normal. Process individual RTVs. No escalation. |
+| 2-5% | Alert vendor management. Request root cause analysis from vendor. Continue selling but monitor weekly. |
+| 5-8% | Formal quality complaint. Demand corrective action plan within 14 days. Consider pull from active sales pending vendor response. |
+| 8-15% | Pull from active sales. Formal defect claim for all returns above the 2% baseline. Negotiate credit or replacement. |
+| > 15% | Full stop-sale. Vendor compliance violation. Chargebacks for all returns + lost margin + customer service costs. Consider vendor termination. |
+
+**Defect claim calculation:**
+```
+Total returns for SKU in period: 500 units
+Expected baseline return rate (non-defect): 8% of units sold (industry avg for category)
+Units sold: 4,000
+Expected returns: 320
+Excess returns attributable to defect: 500 - 320 = 180 units
+Claim = 180 × (wholesale cost + inbound freight per unit + return processing cost per unit)
+ = 180 × ($24.00 + $1.80 + $7.50)
+ = 180 × $33.30
+ = $5,994.00
+```
+
+Add consequential costs if the defect caused customer service escalations, negative reviews
+that required response, or marketplace listing suppression.
+
+### 3.3 Vendor Chargeback Schedule
+
+For vendor-caused issues beyond defects (packaging failures, mislabelling, wrong items shipped
+from vendor DC), apply chargebacks per the vendor compliance programme:
+
+| Violation | Chargeback | Notes |
+|-----------|-----------|-------|
+| Wrong item shipped from vendor DC | 100% of product cost + return shipping + $25 processing fee | Requires photo evidence of received vs ordered |
+| Mislabelled product (UPC doesn't match contents) | $50 per incident + product cost if unsellable | Creates inventory accuracy issues downstream |
+| Packaging failure (product damaged due to inadequate packaging) | 100% of product cost + return processing | Requires photos of packaging condition at receipt |
+| Missing components (accessory, manual, warranty card) | Cost of sourcing replacement component + $10 processing | If component unavailable, full product cost |
+| Counterfeit or unauthorised product | 300% of product cost + $500 penalty per incident | Zero tolerance. Notify brand protection. |
+| Late shipment from vendor causing customer-facing delay | Customer credit issued + $15 processing | Must document customer complaint and credit |
+| Incorrect hazmat/regulatory documentation | $250 per incident + cost of regulatory remediation | Regulatory liability makes this non-negotiable |
+
+### 3.4 Vendor Recovery ROI Model
+
+Not all vendor recovery is worth pursuing. The ROI model:
+
+```
+Recovery ROI = (Expected recovery - Recovery cost) / Recovery cost
+
+Where:
+ Expected recovery = Claim amount × Collection probability
+ Recovery cost = Labour (documentation, communication, follow-up) + Shipping (if RTV) + Relationship cost
+
+Labour cost estimates:
+ - Simple RTV with existing authorisation: $15-25 per batch
+ - Defect claim requiring documentation assembly: $75-150 per claim
+ - Disputed claim requiring escalation and negotiation: $200-500 per claim
+
+Collection probability by vendor tier:
+ - Tier 1 (top 20 vendors, strong relationship): 85-95%
+ - Tier 2 (mid-tier, established relationship): 65-80%
+ - Tier 3 (small/new vendors): 40-60%
+ - International vendors (no US entity): 25-45%
+```
+
+**Decision matrix:**
+| Claim Amount | Tier 1 Vendor | Tier 2 Vendor | Tier 3 Vendor | International |
+|-------------|---------------|---------------|---------------|---------------|
+| < $100 | Offset against next PO | Offset against next PO | Write off | Write off |
+| $100-500 | Batch RTV | Batch RTV | Batch if > $200 total | Write off, note for contract |
+| $500-2,000 | Standard RTV/claim | Standard claim | Standard claim with escalation plan | Claim if > $1,000 |
+| $2,000-10,000 | Standard claim | Standard claim + account mgr | Account mgr + formal notice | Pursue with local agent if > $5,000 |
+| > $10,000 | VP-level engagement | VP-level + legal review | Legal review | Legal counsel in vendor's jurisdiction |
+
+---
+
+## 4. Return Policy Exception Matrix
+
+### 4.1 Exception Decision Framework
+
+When a return falls outside standard policy, the decision to grant an exception depends on
+a structured evaluation, not individual judgment calls. This matrix standardises the
+exception decision.
+
+**Step 1: Is the exception request covered by an automatic override?**
+
+| Condition | Action | No Further Analysis Needed |
+|-----------|--------|--------------------------|
+| Product is defective (verified or reasonably claimed) | Accept return, full refund, no restocking fee | Yes |
+| Fulfilment error (wrong item shipped, wrong quantity) | Accept return, full refund, prepaid return label | Yes |
+| Product is subject to active recall | Route to recall programme (not returns) | Yes |
+| Customer is in top 5% by LTV and request is first exception in 12 months | Grant exception, standard refund | Yes |
+| State or federal law requires acceptance (lemon law, cooling-off period) | Comply with applicable law | Yes |
+
+**Step 2: If not an automatic override, score the exception request:**
+
+| Factor | Score Range | Description |
+|--------|-----------|-------------|
+| Days past policy window | 1-30 days: +2 / 31-60 days: +5 / 61-90 days: +8 / >90 days: +12 | How far outside the standard window |
+| Product condition at return | Grade A: 0 / Grade B: +2 / Grade C: +5 / Grade D: +10 | Worse condition = higher cost of exception |
+| Customer LTV | Top 20%: -5 / Middle 60%: 0 / Bottom 20%: +3 | Valuable customers get more latitude |
+| Return reason credibility | Compelling story with evidence: -3 / Plausible: 0 / Weak: +5 | "My house flooded" with photos vs "I forgot" |
+| Precedent risk | Private resolution: 0 / Customer mentioned social media: +5 / Customer has large following: +8 | Public exceptions become policy expectations |
+| Product restockability | Restockable as new: -3 / Open box: 0 / Liquidation: +3 / Destroy: +5 | Restockable items cost less to accept |
+
+**Step 3: Interpret the exception score:**
+
+| Score | Decision | Authority Level |
+|-------|----------|----------------|
+| < 0 | Grant exception. Cost is minimal, customer value is high. | Returns associate |
+| 0-5 | Grant exception with standard refund. | Team lead |
+| 6-10 | Grant as store credit (not original payment refund). | Team lead |
+| 11-15 | Partial credit (50-75% of purchase price) as store credit. | Returns manager |
+| 16-20 | Deny with empathetic explanation and alternative offer (exchange, discount on next purchase). | Returns manager |
+| > 20 | Deny. Offer to connect with manufacturer warranty if applicable. | Returns manager |
+
+### 4.2 Common Exception Scenarios with Recommended Resolutions
+
+| Scenario | Typical Score | Recommended Resolution |
+|----------|--------------|----------------------|
+| 5 days past window, Grade A, loyal customer | -3 | Full refund to original payment |
+| 45 days past window, Grade B, average customer | +7 | Store credit for purchase price |
+| 90 days past window, Grade C, low-value customer | +16 | Deny, offer 15% discount on next purchase |
+| 10 days past window, Grade A, customer cited family emergency | -1 | Full refund to original payment |
+| Within window, Grade C, customer claims defect but inspection shows user damage | +10 | Store credit at 50% (goodwill), document for fraud scoring |
+| 60 days past window, brand-new customer, first order | +13 | Partial credit (50%), welcome them back with incentive |
+
+---
+
+## 5. Grading Standards by Product Category
+
+### 5.1 Universal Grading Criteria
+
+All categories share these baseline grade definitions. Category-specific addenda
+follow in §5.2.
+
+#### Grade A — Like New
+- Zero signs of use beyond initial unboxing
+- All original accessories, manuals, and packaging materials present
+- Original packaging in good condition (minor shipping wear acceptable)
+- Passes all applicable functional and safety tests
+- Can be restocked and sold as new without any additional processing beyond re-shelving
+
+#### Grade B — Good / Open Box
+- Minor cosmetic imperfections (light surface scratches, small scuffs) that do not affect function
+- Original packaging may be damaged, opened, or missing outer sleeve/shrink wrap
+- All essential accessories present (charger, main cable); non-essential items (stickers, pamphlets) may be missing
+- Fully functional — passes all applicable tests
+- Requires repackaging or "open box" labelling before resale
+
+#### Grade C — Fair
+- Visible cosmetic wear, scratches, dents, or staining that are noticeable at arm's length
+- Missing accessories that affect the completeness of the product (but not its core function)
+- Functional but may have minor performance degradation (battery at 60-80%, worn but operational buttons)
+- Not suitable for primary retail channel — routes to outlet, marketplace, or liquidation
+- May be viable for refurbishment if cost justifies it
+
+#### Grade D — Salvage / Parts
+- Non-functional, heavily damaged, or missing critical components that render the product unusable
+- Structural damage (cracked screens, bent frames, water damage indicators triggered)
+- May have value for parts harvesting or materials recovery
+- Routes to parts extraction, recycling, or destruction
+
+### 5.2 Category-Specific Grading Addenda
+
+**Consumer Electronics:**
+- Grade A additional requirement: battery health > 80% of design capacity (measurable via diagnostic)
+- Grade B threshold: battery 60-80%, cosmetic scratches visible only under direct light
+- Functional test required for all grades: power on, display, connectivity (WiFi/Bluetooth/cellular), speakers, cameras, ports
+- Data wipe verification mandatory before any resale disposition
+
+**Apparel:**
+- Grade A: tags attached (original retail tags, not just care labels)
+- Grade B: tags removed, but no wear indicators; passes UV and odour check
+- Grade C: visible wear, minor staining treatable with professional cleaning, or slight fabric stretching
+- Grade-reducing odours: tobacco smoke, pet odour, heavy fragrance, body odour
+- Automatic Grade D: mould, mildew, pest contamination
+
+**Footwear:**
+- Sole inspection is primary grading factor: unworn soles = Grade A, indoor-only wear marks = Grade B, outdoor wear = Grade C
+- Grade B requires: no toe box creasing deeper than 2mm, no heel counter collapse
+- Include insole inspection: customer orthotics must be removed, original insole must be present
+
+**Home Goods / Small Appliances:**
+- Grade A: unused, all packaging foam/wrapping in place
+- Functional test: operate through one full cycle (coffee maker: brew cycle, vacuum: run for 60 seconds, blender: blend ice test)
+- Missing filters, bags, or consumable accessories: Grade B (replaceable at $3-10 cost)
+- Cosmetic damage on surfaces visible during normal use: Grade C
+
+---
+
+## 6. Liquidation Channel Selection
+
+### 6.1 Channel Overview
+
+When product is routed to liquidation, selecting the right channel significantly affects
+recovery rates. The wrong channel can mean the difference between 20% recovery and 5%.
+
+| Channel | Best For | Typical Recovery (% of retail) | Fees | Min Lot Size | Speed to Cash |
+|---------|----------|-------------------------------|------|-------------|---------------|
+| B-Stock (owned auctions) | Electronics, home goods | 12-25% | 10-15% of sale | 1 pallet | 2-4 weeks |
+| Direct Liquidation | Mixed general merchandise | 8-18% | 15-20% of sale | 1 pallet | 2-6 weeks |
+| Bulq (owned by Optoro) | Small lots, mixed goods | 10-20% | Built into marketplace | 1 box (small lots) | 1-3 weeks |
+| Regional liquidators | Bulky/heavy items, furniture | 5-15% | Negotiated | Varies | 1-4 weeks |
+| Wholesale to dollar stores | Low-value general merchandise | 3-8% (often per-pound) | None (buy outright) | Truckload preferred | Immediate |
+| Online marketplace (eBay, Amazon Warehouse) | Individually valuable items ($50+) | 25-50% | 12-15% + shipping | Single unit | 1-8 weeks |
+| Charity donation | Items not worth liquidating, brand-sensitive | $0 (tax deduction at FMV) | None | No minimum | Immediate |
+
+### 6.2 Channel Selection Decision Tree
+
+```
+Is the individual unit value > $50?
+ ├── Yes → Is the item in Grade B or better condition?
+ │ ├── Yes → Sell individually on marketplace (eBay, Amazon Warehouse). Highest recovery.
+ │ └── No → Is the brand premium/recognisable?
+ │ ├── Yes → Auction on B-Stock (brand buyers pay premium). Recovery 15-25%.
+ │ └── No → Direct Liquidation or regional liquidator. Recovery 8-15%.
+ └── No → Is there a full pallet of same or similar category?
+ ├── Yes → Auction as category-sorted pallet on B-Stock or Direct Liquidation.
+ │ Recovery improves 30-50% vs mixed pallets.
+ └── No → Accumulate by category until pallet quantity reached.
+ If aging > 30 days, mix into general pallet and liquidate.
+ Holding cost exceeds sort premium beyond 30 days.
+```
+
+**Critical liquidation rules:**
+1. Never mix electronics with non-electronics on the same pallet. Electronics buyers won't bid on mixed pallets.
+2. Never include recalled products, counterfeit items, or hazmat in liquidation lots. Liability exposure is unlimited.
+3. Remove all customer personal data before liquidating electronics. Data breach from a liquidated device creates legal exposure.
+4. Photograph every pallet before shipping to liquidation. Disputes about condition are common.
+5. Manifest every pallet (list of SKUs, quantities, conditions). Manifested pallets sell for 20-40% more than unmanifested.
+
+---
+
+## 7. Refurbishment ROI Model
+
+### 7.1 When to Refurbish
+
+Refurbishment is only viable when the economics justify it. The decision model:
+
+```
+Refurbishment ROI = (Refurbished selling price - Refurbishment cost - Fulfilment cost) / Refurbishment cost
+
+Decision thresholds:
+ ROI > 100%: Always refurbish. High-value recovery.
+ ROI 50-100%: Refurbish if capacity exists. Good return on investment.
+ ROI 25-50%: Refurbish only if liquidation alternative is particularly poor (< 8% recovery).
+ ROI < 25%: Liquidate. The refurbishment effort isn't justified.
+```
+
+### 7.2 Refurbishment Cost Benchmarks by Category
+
+| Category | Common Defects | Typical Refurb Cost | Typical Refurb Selling Price | Typical ROI |
+|----------|---------------|--------------------|-----------------------------|-------------|
+| Smartphones (flagship) | Screen scratches, battery degradation | $40-80 (screen polish, battery replace) | $350-550 (65-75% of new) | 300-500% |
+| Laptops | Battery, cosmetic damage, slow storage | $50-120 (battery, SSD upgrade, clean) | $400-800 (55-70% of new) | 200-400% |
+| Tablets | Screen scratches, battery | $30-60 | $200-400 (60-70% of new) | 200-350% |
+| Small appliances | Cosmetic, missing parts | $10-25 (clean, replace accessory) | $30-60 (50-65% of new) | 100-200% |
+| Power tools | Battery, switch wear | $20-45 (battery, switch replacement) | $60-120 (55-65% of new) | 100-200% |
+| Headphones (premium) | Ear pad wear, cosmetic | $8-15 (new pads, clean) | $80-200 (60-75% of new) | 400-800% |
+| Game consoles | Cosmetic, controller wear | $15-30 (clean, replace controller pads) | $150-300 (60-70% of new) | 300-500% |
+
+### 7.3 Refurbishment Capacity Planning
+
+Refurbishment requires dedicated space, trained technicians, and parts inventory. The
+capacity model:
+
+- **Space:** 1 refurb station = approximately 80 sq ft (workbench + test equipment + parts storage)
+- **Throughput:** 1 technician handles 8-15 units/day for electronics, 20-30 units/day for small appliances
+- **Parts inventory:** Maintain 30-day supply of top 20 replacement parts by volume (batteries, screens, cables, ear pads, filters)
+- **Break-even:** A refurb station breaks even at approximately 5-8 units per day at average ROI of 150%. Below this volume, outsource to a third-party refurbisher.
+
+### 7.4 Outsource vs In-House Decision
+
+| Factor | In-House | Outsource |
+|--------|----------|-----------|
+| Volume > 40 units/day | Preferred (economies of scale) | Viable but more expensive |
+| Volume < 40 units/day | Only if margin justifies | Preferred (avoid fixed overhead) |
+| Brand certification programme exists | Required for "certified refurbished" branding | Must verify third-party is certified |
+| Product requires proprietary tools/software | In-house (IP control) | Only with NDA and audited facility |
+| Seasonal volume spikes | Core volume in-house, surge outsourced | Flexible capacity |
+| Data security requirements | In-house (direct control over data wipe) | Requires NIST 800-88 certification |
+
+---
+
+## 8. Return Processing Workflow by Channel
+
+### 8.1 E-Commerce Returns (Ship-Back)
+
+The standard e-commerce return flow. This is the highest-volume channel for most
+retailers and the one with the most automation opportunity.
+
+```
+Customer initiates return on website/app
+ │
+ ├── Automated policy check (within window? excluded category? customer in good standing?)
+ │ ├── Auto-approve → Generate RMA + prepaid return label
+ │ ├── Auto-deny → Display denial reason + alternatives
+ │ └── Manual review queue → Agent reviews within 4 hours
+ │
+ ├── Customer ships product
+ │ └── Tracking monitored for: label scan (confirms customer shipped), delivery to return centre
+ │
+ ├── Receiving at return centre
+ │ ├── Scan RMA barcode → pulls order record, expected product, customer profile
+ │ ├── Initial sort: sealed/unopened → express lane (15-second visual, Grade A, restock)
+ │ └── Opened/used → standard inspection lane
+ │
+ ├── Standard inspection (see §5 for grading criteria)
+ │ ├── Serial number verification (electronics only, but expanding to luxury goods)
+ │ ├── Visual inspection + functional test (category-dependent)
+ │ ├── Fraud scoring (post-receipt signals added to pre-receipt score)
+ │ └── Grade assignment: A / B / C / D
+ │
+ ├── Disposition routing (see §1 for category-specific trees)
+ │ ├── Grade A → Restock queue
+ │ ├── Grade B → Open-box / repackaging queue
+ │ ├── Grade C → Liquidation staging or refurbishment assessment
+ │ └── Grade D → Parts / recycling / destruction
+ │
+ └── Refund processing
+ ├── Refund triggered upon grade assignment (do not wait for disposition completion)
+ ├── Restocking fee applied if applicable (calculated at grading, not at refund)
+ └── Refund to original payment method → customer notification sent
+```
+
+**Key timing targets:**
+| Step | Target | Stretch Goal |
+|------|--------|-------------|
+| RMA generation (auto-approve) | < 5 minutes | Instant |
+| Return label delivery to customer | Immediate (email) | Immediate |
+| Customer ship-back | < 7 days from RMA | < 5 days |
+| Receiving scan at return centre | Day of delivery | Same as carrier delivery scan |
+| Inspection + grading | < 24 hours of receipt | < 4 hours |
+| Refund processing | < 24 hours of grading | Same day as grading |
+| Refund visible to customer | 3-5 business days | 1-2 business days |
+| Total RMA-to-refund cycle | < 14 days | < 7 days |
+
+### 8.2 Buy Online, Return In-Store (BORIS)
+
+Cross-channel returns are operationally more complex but have higher customer satisfaction
+and lower total cost (no return shipping). The critical risk is price discrepancy.
+
+```
+Customer arrives at store with online-purchased product
+ │
+ ├── Associate initiates BORIS return in POS
+ │ ├── Scan product barcode
+ │ ├── Look up online order (by order number, customer email, or loyalty account)
+ │ │ ├── Order found → POS displays actual purchase price from online order
+ │ │ │ └── CRITICAL: Refund at actual online purchase price, NOT store shelf price
+ │ │ └── Order not found → Customer provides order confirmation (email/app)
+ │ │ ├── Verified → Manual price entry at confirmed online price
+ │ │ └── Cannot verify → Process through online returns channel (mail-back)
+ │ │ Do NOT guess the price. Do NOT use store shelf price.
+ │ └── Verify return eligibility (window, excluded categories)
+ │
+ ├── In-store inspection
+ │ ├── Visual + functional check (same criteria as return centre)
+ │ ├── For electronics: serial number check against online order
+ │ └── Grade assignment
+ │
+ ├── Refund processing
+ │ ├── Refund to original online payment method (not store credit, not cash)
+ │ │ Exception: customer paid with a gift card → store credit acceptable
+ │ ├── Restocking fee applied if applicable
+ │ └── Customer receives refund confirmation email
+ │
+ └── Inventory disposition
+ ├── If Grade A and product is in store assortment → Restock on store shelf
+ ├── If Grade A but product is online-only → Ship to return centre or nearest DC
+ ├── If Grade B/C → Ship to return centre for open-box/liquidation processing
+ └── If Grade D → Local disposal (do not ship non-functional product to return centre)
+```
+
+**BORIS-specific risks:**
+1. Price discrepancy (online vs store) → Mitigated by mandatory online order lookup
+2. Return of promotional/bundled items → Verify if the item was part of a BOGO or bundle; refund the proportional amount
+3. Store inventory adjustment → Ensure the store's inventory count correctly reflects the returned unit
+4. Different return windows → Online and store may have different windows; honour the more generous one
+
+### 8.3 In-Store Purchase, Return In-Store
+
+The simplest return flow. The POS has the transaction record, pricing is definitive,
+and the product doesn't need to be shipped.
+
+```
+Customer arrives with product + receipt (or POS lookup via card/loyalty)
+ │
+ ├── POS transaction lookup → Confirms purchase price, date, payment method
+ ├── Window check → Within return policy period?
+ ├── Inspection at return counter
+ │ ├── Quick visual for obvious damage/use
+ │ ├── Electronics: power-on test, serial number check
+ │ └── Grade assignment (usually Grade A or B at point of sale)
+ │
+ └── Refund to original payment method → Receipt printed → Customer exits
+```
+
+**Target transaction time:** < 5 minutes for standard returns. This is the benchmark
+that drives customer satisfaction — long return lines at the service desk are the
+#1 complaint in retail returns.
+
+### 8.4 Returnless Refunds (Customer Keeps Product)
+
+For items where the cost of return exceeds the recovery value. The decision model:
+
+```
+Return shipping cost estimate > 40% of product value?
+ ├── Yes → Evaluate returnless refund
+ │ ├── Product value < $50 → Auto-approve returnless refund
+ │ ├── Product value $50-100 → Supervisor auto-approve
+ │ ├── Product value $100-200 → Manager review (consider partial return — just the defective component)
+ │ └── Product value > $200 → Case-by-case (may justify return shipping for high-value)
+ │
+ └── No → Standard return process
+```
+
+**Returnless refund abuse prevention:**
+- Track returnless refunds per customer. More than 3 in 6 months triggers review.
+- High-value returnless refunds (> $100) are flagged for post-refund audit.
+- Products declared "defective" for returnless refund should still be counted in the
+ SKU defect rate, even though the physical product doesn't return.
+- Consider asking the customer to send a photo of the defect as lightweight verification.
+
+---
+
+## 9. Seasonal Return Planning
+
+### 9.1 Holiday Return Surge (January)
+
+January is to returns operations what December is to fulfillment. Plan for:
+
+| Metric | Normal Month | January Peak | Multiplier |
+|--------|-------------|-------------|-----------|
+| Return volume | 100% baseline | 250-350% | 2.5-3.5x |
+| Return processing backlog | < 24 hours | 48-96 hours | 2-4x |
+| Fraud attempts | Baseline | 180-220% | 1.8-2.2x |
+| Customer service contacts about returns | Baseline | 300-400% | 3-4x |
+| Gift receipt returns (% of total) | 5-8% | 25-35% | 4-5x |
+
+**Holiday return planning checklist:**
+1. Staff: Bring temporary inspection staff online by Dec 26. Target: 2x normal inspection capacity by Jan 2.
+2. Space: Reserve additional staging area for the return volume. Last-mile sorting should be simplified (Grade A express lane for sealed/tagged items).
+3. Policy: Extended holiday return window (typically Nov 1 - Dec 31 purchases returnable through Jan 31) means that returns trickle in over 4 weeks rather than concentrating in the first week. Model the curve.
+4. Gift receipts: Train all associates on gift receipt pricing rules. The #1 January return error is refunding at current price instead of purchase price.
+5. Fraud: Increase fraud scoring thresholds by 10% during January (reduce false positives — many legitimate gift returns trigger fraud signals).
+6. Liquidation: Pre-negotiate January liquidation capacity with liquidation partners. You'll have 3-4x normal Grade C/D volume, and everyone else will too.
+
+### 9.2 Category-Specific Seasonal Patterns
+
+| Category | Peak Return Period | Key Driver | Planning Action |
+|----------|-------------------|-----------|----------------|
+| Consumer electronics | Jan 2-15 | Holiday gifts, "not what they wanted" | Pre-stage functional test stations; serial number verification capacity |
+| Apparel | Jan 5-31 (extends longer) | Gift sizing, holiday party returns | UV/odour inspection throughput; wardrobing detection focus |
+| Fitness equipment | Jan 15 - Mar 1 | New Year's resolution abandonment | Large-item return logistics; returnless refund thresholds |
+| Outdoor/sporting goods | Mar-Apr (post-ski), Sep-Oct (post-summer) | Season-end returns | Seasonal markdown timing; storage vs liquidation decision |
+| School supplies | Sep 1-15 | Over-purchasing for school | High-volume, low-value; fast processing is key |
+
+### 9.3 Markdown-Driven Returns
+
+When products go on markdown or clearance, returns of the same product purchased at
+full price increase. Customers are not returning because of dissatisfaction — they're
+returning to repurchase at the lower price (return arbitrage).
+
+**Detection:** Monitor for returns where the same customer repurchases the same SKU within
+7 days of the return. If the repurchase price is lower, flag as potential price-match return.
+
+**Preferred handling:** Offer a price-match credit instead of processing a return and
+repurchase. The price-match credit costs the markdown difference; the return-and-repurchase
+costs the markdown difference plus processing cost plus potential disposition loss.
+
+---
+
+## 10. Data-Driven Return Reduction
+
+### 10.1 Root Cause Analysis by Return Reason
+
+Returns are a symptom. Reducing return rates requires treating the cause:
+
+| Return Reason | Root Cause Investigation | Typical Fix | Expected Reduction |
+|--------------|------------------------|------------|-------------------|
+| "Didn't fit" (apparel) | Poor size guidance, inconsistent sizing, inadequate photos | Size recommendation engine, fit model photos, detailed measurements | 15-25% reduction in "didn't fit" returns |
+| "Not as expected" | Product photo/description doesn't match reality | Lifestyle photos, video demos, customer photos in reviews, AR preview | 10-20% reduction |
+| "Defective" | Manufacturing quality, shipping damage, product design flaw | Vendor quality scorecard, packaging improvement, design feedback loop | Variable — depends on root cause |
+| "Changed my mind" | Impulse purchase, bracketing | Cooling-off period messaging, wish list instead of cart, fit technology | 5-10% reduction |
+| "Better price found" | Competitive pricing, price transparency | Price-match guarantee, automated price alerts | 8-15% reduction |
+| "Arrived too late" | Shipping delays, inaccurate ETAs | Improved delivery estimates, proactive delay notifications | 20-30% reduction in lateness returns |
+
+### 10.2 SKU-Level Return Rate Monitoring
+
+| Return Rate (rolling 90 days) | Action |
+|-------------------------------|--------|
+| < 5% | Normal. No action required. |
+| 5-10% | Review product listing for accuracy. Check reviews for recurring complaints. |
+| 10-15% | Flag for merchandise review. Audit listing photos/description. Check sizing data. |
+| 15-25% | Escalate to category manager. Consider adding warnings to listing. Review vendor quality. |
+| > 25% | Stop-sell review. The product may have a systemic issue that no listing fix can solve. |
+
+### 10.3 Return Cost Allocation Model
+
+Allocating return costs to the business units that drive them creates accountability:
+
+| Return Cause | Cost Allocation |
+|-------------|----------------|
+| Defective product | Vendor (via RTV/defect claim) or Merchandise (if vendor approved) |
+| Wrong item shipped | Fulfillment operations |
+| Damaged in shipping | Carrier (via shipping claim) or Packaging engineering |
+| Poor product description | E-commerce / Content team |
+| Sizing issue | Merchandise / Product development |
+| Customer changed mind | Cost of doing business (absorbed by margin model) |
+| Fraud | Loss prevention budget |
diff --git a/skills/returns-reverse-logistics/references/edge-cases.md b/skills/returns-reverse-logistics/references/edge-cases.md
new file mode 100644
index 00000000..1deeb656
--- /dev/null
+++ b/skills/returns-reverse-logistics/references/edge-cases.md
@@ -0,0 +1,635 @@
+# Returns & Reverse Logistics — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous return situations that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced returns operations managers from everyone else. Each involves competing interests, ambiguous liability, policy grey areas, and real financial or regulatory exposure. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When a return situation doesn't fit a clean category — when policy intent conflicts with policy letter, when fraud indicators coexist with legitimate behaviour, or when the financial or regulatory exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document your reasoning; these are the cases that generate customer escalations, chargeback disputes, and compliance questions.
+
+---
+
+### Edge Case 1: High-Value Electronics with Firmware Wiped but Extensive Hardware Use Evidence
+
+**Situation:**
+A customer returns a MacBook Pro (retail $2,499) within the 15-day electronics return window claiming "not what I expected." The unit arrives in original packaging with all accessories. A visual inspection gives it Grade A — no cosmetic defects. However, during functional testing, the technician notices: the laptop has been factory-reset (no user data), but the battery cycle count reads 147 (a new unit would have 1-5 cycles from factory QA). The SSD health shows 2.3 TB of total data written. The serial number matches the sold unit. The customer's account is in good standing with $12,000 in lifetime purchases and a 14% return rate.
+
+**Why It's Tricky:**
+The customer is technically within the return window. The product appears "like new" on the surface. But 147 battery cycles represents approximately 4-6 months of typical daily use — far more than the 12 days since delivery. The most likely explanation: the customer bought a new MacBook, swapped the firmware/data to the new unit, and is returning their old MacBook of the same model in the new unit's box. However, the serial number matches, which rules out a physical swap of the entire machine. This suggests the customer simply used the product very heavily for 12 days (possible for a power user or if the customer was migrating data from an old system) OR the battery cycle counter has an anomaly.
+
+The policy says accept within 15 days. The physical evidence suggests this wasn't a brief trial. The customer is valuable. The Apple ecosystem makes serial number verification reliable.
+
+**Common Mistake:**
+Accepting the return at face value because it's within the window and the serial matches, then restocking as Grade A. The 147 battery cycles mean this is a Grade B at best — battery health is already degraded 3-5% from the cycling, and the SSD wear is real. Restocking it as new and selling it to the next customer creates a product quality issue.
+
+The other common mistake: accusing the customer of fraud. The evidence is suggestive but not conclusive. A content creator who downloaded, edited, and uploaded 2 TB of video in 12 days would have a legitimate use pattern.
+
+**Expert Approach:**
+1. Accept the return — the customer is within the policy window and the serial matches. Do not deny.
+2. Grade the unit as B, not A. The battery cycle count and SSD wear are objective quality indicators. Document both with screenshots of the diagnostic tool output.
+3. Refund the customer in full — the 15-day window does not have a condition requirement beyond "original packaging and accessories," which is met.
+4. Route the unit to "open box" or certified refurbished channel, not back to new inventory. Price at 80-85% of retail.
+5. Add a data point to the customer's return profile: "high-use return within window." This is not a fraud flag — it's an intelligence flag. If a pattern emerges across multiple high-value electronics returns, the fraud scoring model will accumulate the signal naturally.
+6. Do NOT apply a restocking fee. The product was returned within the standard window with all accessories. Applying a fee because of battery wear during a 12-day period creates a customer experience problem that costs more than the margin lost on the Grade B vs Grade A disposition.
+7. Review the product listing: does it offer a trial or satisfaction guarantee that implicitly invites heavy use? If so, this return is within the spirit of the policy.
+
+**Key Indicators:**
+- Battery cycle count > 50 within a 15-day return window is an anomaly worth documenting
+- SSD write volume > 500 GB suggests more than casual testing
+- Factory reset before return is not suspicious in itself (privacy-conscious customer behaviour) but combined with high-use indicators, it's a data point
+- Serial number match is critical — if it mismatches, this is swap fraud, not an edge case
+
+---
+
+### Edge Case 2: Hazmat Return with Improper Packaging
+
+**Situation:**
+A customer initiates a return for a cordless power tool kit that includes two lithium-ion batteries (each 5.0 Ah, 20V = 100 Wh per battery). The customer packed the tool, batteries, and charger loose in a standard cardboard box with crumpled newspaper as packing material. The return label was generated through the automated RMA portal, which issued a standard ground shipping label. The parcel is picked up by the carrier. Two days later, the carrier's hazmat compliance team intercepts the package at a sort facility, flags it as a non-compliant lithium battery shipment (no Class 9 labelling, no battery-handling marks, batteries not individually protected against short circuit), and imposes a $500 hazmat violation penalty on your company's shipping account.
+
+**Why It's Tricky:**
+Lithium-ion batteries over 100 Wh require Special Provision 188 compliance under IATA DGR and 49 CFR §173.185 for ground transport. Even under the 100 Wh threshold, UN 3481 (lithium ion batteries packed with equipment) requires the battery terminals to be protected against short circuit and the package to be marked with the lithium battery handling mark. The customer didn't know any of this — they packed their return the way they'd pack any product. The automated RMA system didn't flag the product as requiring special return packaging because the product master data doesn't have a "contains lithium batteries" attribute that triggers special handling.
+
+You now have a $500 carrier penalty, a product in limbo at a carrier facility, a customer who expects a refund, and a systemic gap in your returns process.
+
+**Common Mistake:**
+Blaming the customer or refusing the return because the item was improperly packaged. The customer had no way of knowing the packaging requirements. The system generated a standard return label — the customer followed the instructions given. This is an internal process failure, not a customer failure.
+
+The second mistake: asking the customer to go buy proper hazmat packaging materials and re-ship. This is unreasonable for a consumer return. You would never ask this.
+
+**Expert Approach:**
+1. Contact the carrier's hazmat compliance team immediately. Determine the status of the package — is it being held, returned to the customer, or destroyed? Negotiate the penalty: first offence with an account in good standing may be reduced to a warning. If not, the $500 is a cost of the process gap.
+2. Arrange for the package to be returned to the customer (if not already). Do NOT ask the carrier to forward it — it's non-compliant, and re-shipping it in the same packaging compounds the violation.
+3. Send the customer a proper return kit: a UN-rated box with battery terminal protectors, lithium battery handling labels, and clear instructions. Include a pre-paid hazmat-rated shipping label (GROUND ONLY — lithium batteries over 100 Wh cannot ship by air via standard return channels). Cost: $15-25 for the kit plus $20-35 for the hazmat-rated label.
+4. Process the refund upon receipt at your facility. Do not delay the refund because of the packaging issue — this was your process failure.
+5. Systemic fix: flag all products containing lithium batteries > 20 Wh in the product master data. When a return is initiated for these products, suppress the standard return label and instead trigger the special return kit shipment. This costs $35-60 per return but eliminates the $500+ violation risk.
+6. Absorb the carrier penalty internally. Do not pass it to the customer. Charge it to the process improvement budget.
+
+**Key Indicators:**
+- Products containing lithium-ion batteries > 100 Wh (or containing multiple batteries where the sum exceeds 100 Wh) require UN 3481 packaging for return shipping
+- Carrier hazmat violations range from $500 to $50,000+ depending on severity and history
+- The systemic cost of not having a hazmat return process is: (number of battery-containing returns per year) × (probability of carrier interception) × (average penalty) — for most retailers, implementing the proper process is cheaper within the first year
+
+---
+
+### Edge Case 3: Cross-Border Return with Duty Drawback Implications
+
+**Situation:**
+A Canadian customer purchased a $1,200 designer handbag from your US-based e-commerce site. The product was shipped from your US warehouse to Toronto. Canadian customs assessed 18% duty ($216) plus 13% HST ($184.08) on the customer at import, for a total of $400.08 in import charges paid by the customer. The customer now wants to return the handbag (it's the wrong colour — their order specified "cognac" but the product listing photo and actual product colour differ under different lighting). They want a full refund including the import duties they paid. The handbag is in perfect Grade A condition.
+
+**Why It's Tricky:**
+Three financial flows are entangled:
+1. The product price ($1,200) — refundable through your normal return process
+2. The Canadian import duty ($216) — reclaimable by the customer through CBSA (Canada Border Services Agency) casual refund process or by you through a duty drawback claim if the product is re-exported
+3. The HST ($184.08) — reclaimable by the customer through a CBSA B2G form
+
+The customer expects you to refund the full $1,600.08. But you only collected $1,200 — the duties and taxes were collected by Canadian customs, not by you. You can refund what you collected, but the $400.08 in duties/taxes must be recovered through the customs process.
+
+Complicating factors: the customer doesn't know how to file a CBSA casual refund. The duty drawback requires the handbag to be re-exported from Canada within specific timelines. Return shipping from Canada to the US requires a commercial invoice and customs declaration for the returned goods. And the return shipping cost ($45-80 for a tracked cross-border return) may be a point of contention — who pays?
+
+**Common Mistake:**
+Refunding the customer $1,600.08 to "make it right" without understanding that the $400.08 in duties/taxes can be recovered from CBSA, effectively eating $400 that isn't yours to eat. This seems customer-friendly but is financially illiterate — it means you're paying the Canadian government's duty for the customer.
+
+The second mistake: telling the customer "duties are your responsibility" and only refunding $1,200. While technically true, this is a fulfilment error (wrong colour due to misleading product photo), which changes the obligation calculus. A customer who received the wrong colour should be made whole.
+
+**Expert Approach:**
+1. Acknowledge the fulfilment error. This was your product photo misrepresentation, not buyer's remorse. This changes the return from "standard" to "seller-fault."
+2. Refund the $1,200 product price immediately upon return receipt. This is your standard process.
+3. For the $400.08 in duties/taxes: provide the customer with step-by-step instructions for filing a CBSA casual refund claim (Form B2, with the returned-goods receipt as documentation). Most casual refund claims are processed in 4-8 weeks.
+4. Because this is a seller-fault return, cover the return shipping cost. Provide a prepaid cross-border return label. Ensure the label includes proper customs documentation (commercial invoice marked "RETURNED GOODS — NO COMMERCIAL VALUE" with original export reference).
+5. As a goodwill gesture for the inconvenience (wrong colour + cross-border return hassle), offer a $50-100 store credit. This costs less than refunding $400 in duties you didn't collect.
+6. If the customer insists on immediate full reimbursement of the duties: evaluate the customer's LTV and the competitive cost of losing them. For a first-time international customer, the $400 goodwill refund may be justified if the customer's potential LTV exceeds $2,000. For a one-time buyer, provide the CBSA refund instructions and hold firm on the product refund only.
+7. File your own duty drawback claim (if applicable) for the import duty that was assessed when you originally exported the goods. US duty drawback under 19 USC §1313 allows recovery of 99% of duties paid on exported goods that are returned, within 5 years. This requires the original export documentation.
+
+**Key Indicators:**
+- Cross-border returns always involve at least three financial streams: product price, import duty, and sales/value-added tax
+- The customer paid the duties, not you — refunding duties you didn't collect is a cost that should only be incurred as a deliberate customer recovery decision, not a default
+- CBSA casual refund claims require proof that the goods were re-exported; the customer needs the return tracking number showing the package crossed back into the US
+- Return shipping customs declarations for returned goods should use HS code 9801 (US) or tariff item 9813 (Canada) to avoid re-assessment of duties on the returned product
+
+---
+
+### Edge Case 4: Influencer Bulk Return Post-Content-Creation
+
+**Situation:**
+A social media influencer with 850K Instagram followers and a fashion/lifestyle brand placed an order for 24 items totalling $3,200 (mix of apparel, accessories, and shoes). The order was placed 18 days ago, delivered 15 days ago. The influencer has since posted 4 Instagram Reels and 2 TikTok videos featuring 22 of the 24 items in styled outfits, "haul" content, and "try-on" format. The videos collectively have 2.1 million views. The influencer now initiates a return for 22 of the 24 items (keeping 2 items worth $180), claiming "didn't fit" and "not as expected" for the various items. All items are within the 30-day return window.
+
+The returned items arrive and inspection reveals: 16 items are Grade A (tags on, no wear signs), 4 items are Grade B (tags removed, minor wear indicators — one dress has foundation on the collar), and 2 items are Grade C (visible wear, one pair of shoes shows outdoor sole wear).
+
+**Why It's Tricky:**
+The customer technically complied with the return policy — the items are within the 30-day window, and the stated return reasons are among the accepted reasons. The influencer extracted significant brand value (2.1M views of organic-looking content featuring your products) without paying for it. The cost of equivalent paid influencer content at her follower count would be $5,000-15,000.
+
+But there's no "you used our products for content" clause in the return policy. The influencer didn't sign an agreement. She's a customer exercising her return rights. Refusing the return creates legal risk (she documented that the items were purchased legitimately) and PR risk (an influencer with 850K followers posting about a return denial generates vastly more negative attention than the $3,020 refund).
+
+**Common Mistake:**
+Refusing the return or charging punitive restocking fees on all 22 items. This triggers a "brand vs influencer" public dispute that costs far more than $3,020 in brand damage. The second mistake: passively accepting the return and learning nothing — the same influencer (or others) will repeat this pattern.
+
+**Expert Approach:**
+1. Process the return. Accept all 22 items. Grade them honestly:
+ - 16 items Grade A: restock as new. Full refund on these items.
+ - 4 items Grade B: refund in full (tags removed isn't grounds for denial within the return window for apparel). Route to open-box/outlet.
+ - 2 items Grade C: refund in full minus restocking fee on the shoes with outdoor wear (visible use beyond trying on). The dress with foundation gets full refund — cosmetic transfer during try-on is expected.
+2. Apply the restocking fee to the worn shoes only. Explain: "We've processed your return. 21 items received a full refund. The [shoe name] showed wear beyond trying on, so a 15% restocking fee of $X was applied per our return policy."
+3. Separately, refer this case to the marketing/brand partnerships team. The influencer generated $5,000-15,000 in equivalent media value. The business-smart play is to convert her from a "free content via returns" customer to a paid brand ambassador. Reach out with: "We loved how you styled our pieces. We'd like to discuss a collaboration."
+4. Add a note to the customer's profile for future monitoring. If this pattern repeats (bulk purchase → content → bulk return), the fraud scoring model will accumulate points naturally. If she becomes a brand ambassador, the returns stop being a problem.
+5. Systemic: consider a "content creator" return policy that offers extended exchange/store credit windows for influencers who tag the brand, in exchange for a no-return-for-refund agreement on items used in content. This requires marketing/legal collaboration.
+
+**Key Indicators:**
+- Bulk orders from accounts with high social media followings, followed by near-complete returns, is an emerging pattern that existing return policies don't address
+- The refund cost ($3,020) is almost always less than the negative PR cost of a public denial
+- Marketing value of the content may exceed the refund cost, making this a net positive event if handled strategically
+- Restocking fees should only apply to items with objective condition defects, not as punishment for the pattern
+
+---
+
+### Edge Case 5: Warranty Claim on Product Modified by Customer
+
+**Situation:**
+A customer purchased a gaming laptop ($1,899) 14 months ago and is filing a warranty claim because the display has developed a persistent flickering issue that makes the laptop unusable. During inspection, the technician discovers that the customer has upgraded the RAM from the factory-installed 16 GB to 32 GB using third-party RAM modules. The RAM upgrade is clearly visible (different brand module in the second DIMM slot). The laptop's warranty is 24 months from purchase. The manufacturer's warranty terms state: "Warranty is void if the product has been modified, altered, or repaired by anyone other than an authorised service centre."
+
+The customer's position: "I upgraded the RAM, not the display. The RAM has nothing to do with the screen flickering. The warranty should cover the display." The manufacturer's position: "Any modification voids the entire warranty."
+
+**Why It's Tricky:**
+The customer's logic is reasonable. RAM and display are independent subsystems. A RAM upgrade almost certainly didn't cause display flickering (which is typically a cable, inverter, or GPU issue). However, the manufacturer's warranty language is broad — "any modification" voids the warranty. Legally (under Magnuson-Moss Warranty Act in the US), a warranty provider cannot void a warranty for using third-party parts unless the warrantor can demonstrate that the third-party part caused the defect being claimed. The "void if modified" clause is likely unenforceable for unrelated modifications, but most customers don't know this, and challenging it requires escalation.
+
+As the retailer, you're caught between the customer (who expects you to facilitate the warranty claim) and the manufacturer (who will deny it based on the modification). Your extended warranty (if sold) may have similar language.
+
+**Common Mistake:**
+Denying the warranty claim outright because "the product was modified." This is both legally questionable (Magnuson-Moss) and customer-hostile. The customer's modification was a routine, widely-documented upgrade that the laptop was designed to support (user-accessible RAM slot).
+
+The second mistake: accepting the claim and eating the repair cost without pursuing the manufacturer. The display defect is a manufacturing quality issue, not a retail liability.
+
+**Expert Approach:**
+1. Accept the laptop for evaluation. Do NOT deny at the point of customer contact. Tell the customer: "We'll inspect the display issue and submit the warranty claim to the manufacturer."
+2. Document the modification (photographs of the third-party RAM) and the defect (video of display flickering). Test the display issue with and without the third-party RAM installed — if the flickering persists with original RAM configuration, the modification is demonstrably unrelated to the defect.
+3. Submit the warranty claim to the manufacturer with the documentation. Include: the defect evidence, the modification documentation, and a note stating that the modification is unrelated to the claimed defect per Magnuson-Moss Warranty Act provisions.
+4. If the manufacturer denies: escalate to the manufacturer's warranty dispute resolution process. Cite 15 USC §2302(c) — a warrantor may not condition warranty coverage on the use of a specific article unless the article is provided free of charge. The customer's use of third-party RAM is protected.
+5. If the manufacturer continues to deny: evaluate the repair cost. A display cable replacement is typically $50-150 in parts and labour. If you have an in-house repair capability, consider performing the repair and pursuing the manufacturer for reimbursement. The customer gets a working laptop, you maintain the relationship, and you have a legitimate claim against the manufacturer.
+6. If an extended warranty was sold: check the extended warranty terms carefully. Third-party extended warranties (Allstate, Asurion) have their own modification clauses that may differ from the manufacturer's. If the extended warranty covers it, file against the warranty provider instead.
+7. Communicate progress to the customer at each stage. The worst outcome is silence during a warranty claim.
+
+**Key Indicators:**
+- Magnuson-Moss Warranty Act (15 USC §2301-2312) prohibits warranty void clauses based on the use of third-party parts unless the warrantor proves the part caused the defect
+- FTC enforcement of Magnuson-Moss has increased in recent years, making "void if modified" stickers largely unenforceable
+- Common user modifications that should not void unrelated warranty claims: RAM upgrades, storage drive replacements, adding peripherals, installing aftermarket cases/screen protectors
+- Modifications that may legitimately void related warranty claims: CPU/GPU overclocking (thermal damage), software rooting/jailbreaking (software defects), physical modifications to cooling systems (overheating)
+
+---
+
+### Edge Case 6: Serial Returner Who Is Also a High-Value Customer
+
+**Situation:**
+Customer "Elena M." has a 3-year purchase history totalling $82,000 in gross purchases. She shops primarily in premium apparel, shoes, and accessories. Her return rate is 42% — she has returned $34,440 in product over the same period. Her net revenue after returns is $47,560. Her average order value is $680, and she typically orders 3-5 items per order, keeps 2-3, and returns 1-2. Her return reasons are consistently "didn't fit" or "not what I expected." Returned items are almost always Grade A. She has never returned a used or damaged item. She is a member of your top-tier loyalty programme.
+
+Your fraud detection system has flagged her with a score of 68 (above the 65-point review threshold) due to her return rate, volume, and frequency. The system recommends a refund hold pending review.
+
+**Why It's Tricky:**
+Elena is bracket-shopping — buying multiple items knowing she'll return some. This is not fraud. It's a legitimate (if expensive) shopping behaviour that high-end retail has dealt with for decades. Her 42% return rate is high, but her $47,560 net revenue over 3 years places her in your top 2% of customers by net value. Her returns are Grade A, meaning the disposition cost is minimal (restock as new). The actual cost of her returns is: return processing at ~$7 per return × approximately 150 returns = $1,050 in processing costs over 3 years. That's negligible against $47,560 in net revenue.
+
+Putting a hold on her refund will damage a relationship worth ~$16,000/year in net revenue. But your fraud system flagged her, and ignoring the system creates process precedent.
+
+**Common Mistake:**
+Enforcing the fraud hold. Treating Elena like a fraud suspect — even temporarily — risks losing a customer whose LTV is in the top 2%. The fraud scoring system is correctly identifying a signal (high return rate) but incorrectly interpreting it as fraud risk.
+
+The second mistake: exempting her from the fraud system permanently. This creates a loophole that actual fraudsters could exploit if they know that high spend protects them.
+
+**Expert Approach:**
+1. Override the fraud hold immediately. Process Elena's return normally. The override is justified by: positive net LTV (top 2%), Grade A return condition (no cost indication of fraud), consistent behaviour over 3 years (not a new pattern), and return reasons consistent with bracket shopping.
+2. Add a "VIP override" annotation to her customer profile. This allows the fraud system to continue monitoring her behaviour (important if her pattern changes to something genuinely fraudulent) while preventing friction on her normal returns.
+3. Set a review trigger for pattern deviation. If Elena's return rate exceeds 60%, or if returned item condition drops below Grade A, or if she starts returning items from new categories (electronics, high-shrink), the override should be suspended and a human review triggered.
+4. Share the case (anonymised) with the fraud model team as a false-positive calibration data point. The model should receive a negative adjustment for the LTV-to-return-rate interaction: customers with high net LTV and Grade A returns should have their base scores reduced.
+5. Consider proactive outreach through the personal shopping or styling team. Elena's bracket shopping suggests she'd benefit from virtual styling, improved size recommendation tools, or early access to try-on programmes. Converting her from a bracket shopper to a targeted shopper reduces return volume while preserving revenue.
+6. Do NOT restrict her return privileges, adjust her return window, or impose restocking fees. The ROI calculation is unambiguous: $16K/year net revenue versus $350/year in return processing costs. The returns are a cost of doing business with a high-value customer.
+
+**Key Indicators:**
+- Return rate alone is not a fraud indicator. Return rate must be contextualised with: net LTV, return condition, behaviour consistency, and return reason patterns.
+- The fraud scoring model should include an LTV offset that reduces scores for customers with positive net LTV. The current model doesn't weight this strongly enough.
+- Bracket shopping is most common in: premium apparel (multiple sizes), shoes (half-size uncertainty), and accessories (colour matching). Categories where in-person evaluation matters.
+- Industry benchmark: luxury e-commerce return rates of 30-40% are normal. The 42% rate is slightly high but not anomalous for the category.
+
+---
+
+### Edge Case 7: Return of a Recalled Product
+
+**Situation:**
+A customer brings a portable space heater to the store for a return, stating "it doesn't work properly and I'm scared it's going to start a fire." The receipt shows purchase 45 days ago (outside the 30-day return window). During the intake process, the associate scans the product barcode and the system matches it to an active CPSC (Consumer Product Safety Commission) recall issued 10 days ago due to a fire hazard from a faulty thermostat. The recall notice instructs consumers to "immediately stop using the product and contact [manufacturer] for a full refund or replacement."
+
+**Why It's Tricky:**
+This is not a return — it's a recall. But the customer came to your store expecting a return process, not a recall process. The recalled product cannot enter your standard returns inventory (it's a safety hazard). It cannot be restocked, liquidated, donated, or disposed of through normal channels — recalled products have specific disposition requirements. But the customer is standing in front of you wanting a resolution now, and telling them "go contact the manufacturer" feels like you're passing the buck.
+
+Additionally: the product is outside the return window, so the standard return system would deny it. The recall overrides the return policy, but the standard return system may not know that. If the associate processes it as a "return," the recalled unit could end up in general returns inventory and eventually be restocked or liquidated — both of which create safety and legal liability.
+
+**Common Mistake:**
+Processing it as a standard return. This puts a recalled product into the returns stream where it may be restocked or liquidated, creating enormous liability. Even if it's "disposed of," standard disposal doesn't include the CPSC reporting requirements for recalled product destruction.
+
+The second mistake: refusing the return because it's outside the 30-day window and telling the customer to contact the manufacturer. You sold them a product that's now subject to a safety recall. Directing them elsewhere damages trust and may create legal exposure under state consumer protection laws.
+
+**Expert Approach:**
+1. The associate should STOP the standard return process. This is a recall, not a return. Do not issue a refund through the POS return function.
+2. Accept the product from the customer. Issue a full refund at the original purchase price as a "recall accommodation" — most POS systems have a separate recall/safety return code. If not, process as a defective return with a manager override for the window, and add a note "RECALLED PRODUCT — DO NOT RESTOCK."
+3. Physically segregate the product immediately. Place it in the recall quarantine area (not the general returns staging area). Affix a "RECALLED — DO NOT PROCESS" label.
+4. Log the recall return in the recall tracking system (or spreadsheet if no system exists) with: date, customer name, serial number, lot number, store location, CPSC recall number.
+5. Follow the manufacturer's recall instructions for retailer-held inventory. Typically: hold until manufacturer arranges pickup or provides destruction instructions with certificate-of-destruction requirements.
+6. Report the return to the recall coordinator. The recall coordinator aggregates data for CPSC reporting requirements (firms involved in recalls must maintain records of corrective actions).
+7. Check your remaining inventory (stores + warehouse) for the same product. If any units are still in sellable inventory, pull them immediately. This is a legal obligation once you're aware of the recall.
+8. If the customer purchased other products from the recalled brand, consider proactively checking those against recall databases as a goodwill gesture.
+
+**Key Indicators:**
+- Recalled products MUST NOT enter the standard returns stream. The disposition for recalled products is determined by the recall notice, not by your normal disposition tree.
+- CPSC recall compliance is not optional. Failure to segregate and properly handle recalled products can result in penalties up to $100,000 per violation under the Consumer Product Safety Act.
+- The refund to the customer is ultimately the manufacturer's financial responsibility. Process the refund to the customer immediately and pursue reimbursement from the manufacturer through the recall programme.
+- Some recalls are "voluntary" (manufacturer-initiated) and some are mandatory (CPSC-ordered). The retailer's obligation is the same in both cases.
+
+---
+
+### Edge Case 8: Gift Receipt Return at Higher Current Price
+
+**Situation:**
+A customer presents a gift receipt for a premium blender purchased by the gift-giver 6 weeks ago for $279.99. The blender is currently selling for $309.99 (price was increased 2 weeks ago due to a supplier cost increase). The customer wants to return the blender for store credit. The gift receipt shows the $279.99 purchase price but the customer is looking at the shelf tag showing $309.99.
+
+**Why It's Tricky:**
+Gift receipt policy typically states "refund at purchase price to store credit." This is clear. But the customer sees a $30 discrepancy and may interpret the gift receipt as entitling them to the current value of the product. If you issue store credit for $279.99 and the customer wants to "exchange" for the same blender (maybe in a different colour), they'd need to pay $30 out of pocket for the exact same product — which feels absurd from a customer perspective.
+
+The reverse scenario is more common and more dangerous: gift receipt return when the price has dropped. Gift-giver paid $279.99, current price is $229.99, and the gift recipient gets $279.99 in store credit — effectively profiting $50. This is a known return arbitrage vector.
+
+**Common Mistake:**
+Issuing store credit at the current (higher) price to avoid the awkward conversation. This creates a $30 loss and, more importantly, establishes a precedent that gift receipt returns get current-price value. During seasonal markdowns (post-holiday), this policy would be exploited systematically.
+
+**Expert Approach:**
+1. Issue store credit at the documented purchase price ($279.99). This is the policy and the financially correct answer.
+2. If the customer wants to exchange for the same product at $309.99, offer to process it as even exchange at the original purchase price (no additional charge). This is an exchange, not a return-and-repurchase. The $30 price difference is absorbed as goodwill.
+3. If the customer wants a refund (store credit) and will buy a different product, the store credit amount is $279.99. They can use it toward any purchase.
+4. If the customer objects to the $279.99 amount: explain calmly that gift receipts reflect the purchase price, which protects gift-givers' privacy (the gift-giver doesn't want the recipient to know they paid less than current price) and ensures accurate accounting. Most customers accept this explanation.
+5. Never issue store credit above the documented purchase price unless a manager explicitly authorises it as a one-time customer accommodation, documented in the transaction notes.
+
+**Key Indicators:**
+- Gift receipt store credit should always be at the lower of: purchase price or current selling price. This protects against both upward and downward price arbitrage.
+- An exception for even-exchange at original price (same item, different colour/size) is operationally clean and customer-friendly.
+- Track gift receipt returns during post-holiday markdown periods. A spike in gift-receipt returns when prices drop is an arbitrage signal.
+
+---
+
+### Edge Case 9: Cross-Channel Return Where Online Price Differs from Store Price
+
+**Situation:**
+A customer purchased a stand mixer online for $249.99 during a flash sale (regular online price is $329.99, regular store price is $349.99). The customer wants to return it in-store. The store's return system pulls the current store price ($349.99) because the online flash sale price is not visible in the store's POS. If the associate processes the return at store price, the customer receives a $100 windfall.
+
+**Why It's Tricky:**
+Omnichannel systems often have pricing discrepancies between channels. Online pricing is dynamic (flash sales, personalised pricing, coupon codes), while store pricing updates on a different cadence. The return system may not have visibility into the customer's actual purchase price, only the current store price for the SKU.
+
+**Common Mistake:**
+Processing the return at the store POS price ($349.99). This is a $100 overpayment that, at scale, represents significant financial leakage. Cross-channel return price arbitrage is a known fraud vector — buy online at the lowest price, return in-store at the higher price.
+
+**Expert Approach:**
+1. Look up the original order. Use the customer's email, order number, or loyalty account to pull the actual purchase price. The refund amount should match the actual amount paid ($249.99), not the current store price.
+2. If the order lookup system isn't available in-store (system limitation), ask the customer for their order confirmation email. Most customers have this accessible on their phone.
+3. If no order verification is possible: refund to the original payment method only. This ensures the refund goes back to the card that was charged $249.99 — the payment processor will reconcile to the actual charge amount regardless of what the POS tries to refund. If the POS attempts to refund $349.99 to a card that was only charged $249.99, the processor should limit the refund to the charged amount (though not all processors do this reliably).
+4. Never issue a cash or store credit refund for an online purchase returned in-store without verifying the actual purchase price. Cash and store credit bypass the payment processor safeguard.
+5. Systemic fix: ensure the in-store return system queries the online order management system for the actual purchase price before processing any BORIS (buy online, return in store) return. This is table-stakes omnichannel operations.
+
+**Key Indicators:**
+- Cross-channel return price discrepancy is one of the top 3 sources of return-related financial leakage in omnichannel retail
+- Always refund to original payment method for cross-channel returns (prevents price-arbitrage via store credit)
+- The POS system should display the actual purchase price from the original order, not the current store price, for all cross-channel returns
+- Audit cross-channel returns monthly for price discrepancy patterns
+
+---
+
+### Edge Case 10: Counterfeit Product Discovered in Return Stream
+
+**Situation:**
+A customer returns a "Dyson V15 Detect" cordless vacuum (retail $749.99) claiming it stopped working after 2 weeks. During inspection, the returns technician notices subtle differences from a genuine Dyson V15: the weight is slightly off (lighter by 200g), the laser dust-detection head has a different LED colour temperature, the serial number format doesn't match Dyson's standard format, and the packaging — while high quality — has a slightly different font on the warranty card. The technician suspects this is a counterfeit. The customer purchased the unit from your marketplace platform through a third-party seller, "EliteTech Solutions," who has 4.2 stars and 2,300 reviews.
+
+**Why It's Tricky:**
+If this is counterfeit, multiple problems converge. The customer is a victim — they paid $749.99 for a fake product. The marketplace seller may be knowingly selling counterfeits, or may themselves have been deceived by their supply chain. Dyson has an aggressive brand protection programme and may pursue legal action against the marketplace. The counterfeit unit cannot be returned to the seller, restocked, liquidated, or disposed of through normal channels — it's illegal goods. And you need to determine whether this is an isolated incident or evidence of a systematic counterfeiting operation on your marketplace.
+
+**Common Mistake:**
+Processing the return as a standard defective return, issuing a refund, and putting the counterfeit unit back into the returns stream where it may eventually be liquidated and re-enter the market. This creates trademark liability.
+
+The second mistake: accusing the customer of returning a counterfeit (implying they're running a swap scam). The customer may genuinely be a victim.
+
+**Expert Approach:**
+1. Accept the product from the customer. Issue a full refund immediately. Do NOT make the customer wait for an investigation. They paid for a genuine product and received a counterfeit — they are the victim.
+2. Quarantine the product. Label it "SUSPECTED COUNTERFEIT — DO NOT PROCESS." Photograph extensively: every angle, labels, serial numbers, packaging, weight, and the specific indicators that raised suspicion.
+3. Notify Brand Protection / Loss Prevention immediately. Provide the photographs and inspection findings.
+4. Brand Protection should contact Dyson's brand protection team to confirm the counterfeit determination. Dyson will want the unit for forensic analysis. Provide it under a chain-of-custody document.
+5. Suspend the marketplace seller (EliteTech Solutions) pending investigation. Pull all active listings. Review their other product listings for similar brand-name products that may also be counterfeit.
+6. Review all recent orders from EliteTech Solutions for the same product. Contact those customers proactively: "We're conducting a quality review of a product you purchased. We'd like to offer you a free inspection and, if needed, a replacement or full refund."
+7. Do NOT destroy the counterfeit unit — it's evidence. The brand owner and potentially law enforcement will need it.
+8. If the investigation confirms systematic counterfeiting: permanently ban the seller, report to the appropriate authorities (FBI for trademark counterfeiting, CBP if the goods were imported), cooperate with the brand owner's legal team, and notify all affected customers.
+
+**Key Indicators:**
+- Weight discrepancy is one of the most reliable first indicators of counterfeits — counterfeiters rarely match the exact weight of genuine products
+- Serial number format mismatches are definitive when confirmed by the brand owner
+- Counterfeit products found in the return stream often indicate a larger supply chain problem, not an isolated incident
+- Marketplace liability for counterfeit goods is an evolving legal area (INFORM Consumers Act, SHOP SAFE Act) — document everything for legal protection
+- Never liquidate, donate, or return suspected counterfeit goods to any channel. The legal liability is unlimited.
+
+---
+
+### Edge Case 11: Simultaneous Return and Chargeback — Double-Refund Risk
+
+**Situation:**
+A customer purchases a high-end espresso machine ($849.99) and initiates an online return 18 days after delivery, citing "machine makes grinding noise during extraction." The RMA is approved and a prepaid return label is generated. Two days later — before the customer has shipped the return — the payments team receives a chargeback notification from Visa under reason code 13.3 ("Not as Described"). The customer has now created two parallel refund paths for the same $849.99 transaction.
+
+**Why It's Tricky:**
+If both processes complete independently, the customer receives $1,699.98 — a double refund. The return process would refund $849.99 upon receipt and inspection. The chargeback process, if not contested, would refund $849.99 through the card network. Payments teams and returns teams often operate in separate systems with no automatic cross-check. The customer may be deliberately exploiting this gap, or they may genuinely not understand that a chargeback and a return are separate mechanisms (surprisingly common — many customers file chargebacks when they get frustrated waiting for a return label, not understanding they've initiated a second refund process).
+
+The chargeback has regulatory timelines: Visa requires the merchant to respond within 20 days or the chargeback auto-closes in the cardholder's favour. The return has no such external deadline. This asymmetry means the chargeback demands attention first.
+
+**Common Mistake:**
+Processing the return refund without checking for an active chargeback. This is the #1 source of double-refund losses in e-commerce. The second mistake: immediately assuming fraud and antagonising a customer who may simply be confused about the process.
+
+**Expert Approach:**
+1. HALT the RMA process immediately. Add a "chargeback hold" flag to the RMA. Do not process a return refund while a chargeback is active.
+2. Contact the customer within 24 hours. Use neutral, helpful language: "We received your return request and also noticed a dispute was filed with your bank for the same order. We'd like to help resolve this through whichever channel is easiest for you. If you'd prefer to proceed with the return (which typically resolves faster), could you ask your bank to withdraw the dispute? Or if you'd prefer to resolve through your bank, we can cancel the return. We just need to use one process to avoid delays." This gives the customer a face-saving way to resolve.
+3. If the customer agrees to withdraw the chargeback: get confirmation in writing (email reply is sufficient), then proceed with normal return processing. Keep the chargeback response prepared — if the bank doesn't actually withdraw, you need the evidence.
+4. Respond to the chargeback regardless: within the 20-day window, submit a response to Visa with: proof of delivery, product description matching the listing, evidence of the open RMA (showing you were actively resolving the customer's complaint through the return channel), and the customer's communication agreeing to resolve via return. This protects you if the chargeback isn't actually withdrawn.
+5. If the customer doesn't respond or insists on both: treat as potential fraud. The chargeback takes priority (regulatory timeline). Fight the chargeback with evidence. Cancel the RMA. If the customer then ships the product back on the old label, process as an unsolicited return — accept the product but do not issue a refund (the chargeback is the refund mechanism).
+
+**Key Indicators:**
+- Simultaneous return + chargeback is a known fraud vector called "double-dipping"
+- It's also a common customer confusion error — about 40-60% of these cases are not intentional fraud
+- The first 24 hours after detecting the overlap are critical — customer contact resolves 70% of cases
+- Cross-reference returns and chargebacks daily. Any payment team / returns team process gap here is a significant financial exposure
+- Track customers who have previously had a return + chargeback overlap, regardless of resolution — a second occurrence significantly increases the fraud probability
+
+**Documentation Required:**
+- Screenshot of both active RMA and active chargeback for the same order
+- Customer communication and response (timestamped)
+- Chargeback response submitted to Visa
+- Final resolution record: which channel was used, was the other cancelled, total refund amount
+
+---
+
+### Edge Case 12: Customer Returns Product Purchased Through Employee Discount Programme
+
+**Situation:**
+A customer returns a 65" Samsung OLED TV ($2,199.99 retail) with a receipt showing the purchase price of $1,319.99 — a 40% employee discount. The employee discount programme is run through a third-party perks platform (Perkspot, CorporatePerks) and is linked to the customer's employer. The customer is returning because "TV has a dead pixel cluster in the upper right quadrant — noticed after 3 days." The return is within the 30-day window. Your standard policy would refund the purchase price ($1,319.99), but the product at full retail restocks at $2,199.99 or resells as open-box at ~$1,760-1,870.
+
+**Why It's Tricky:**
+The employee discount creates a price asymmetry that can be exploited. If the customer receives a cash refund of $1,319.99 but the product restocks at $2,199.99, there's no financial loss. But what if the customer then repurchases through the employee discount again? Or what if an employee discount customer returns a product and a friend buys it as "open box" at $1,760 — effectively getting a better deal through the return channel than the employee discount provides?
+
+The more immediate question: the dead pixel is a legitimate defect. Is this a return (customer exercises their right to return) or a warranty claim (manufacturer defect)? The distinction matters because the return refunds at the employee discount price ($1,319.99), while a warranty claim might provide a replacement at no cost (preserving the employee discount benefit on the new unit).
+
+**Common Mistake:**
+Refunding at retail price ($2,199.99) instead of the employee discount purchase price ($1,319.99). This creates an $880 overpayment and, worse, opens a fraud vector: buy on employee discount, return for retail price, pocket the difference. The second mistake: applying a restocking fee to a defective product (dead pixels are a manufacturing defect, not a customer-fault return).
+
+**Expert Approach:**
+1. Acknowledge the dead pixel defect. This is a manufacturing defect — no restocking fee applies.
+2. Offer the customer a choice: (a) full return and refund at the employee discount purchase price ($1,319.99), or (b) warranty exchange for a replacement unit of the same model at no cost. Clearly explain the option: "Since the TV has a defect, we can either refund your purchase price or exchange it for a new unit. The exchange preserves your original pricing."
+3. Most customers with a 40% discount will prefer the exchange — they get a working TV at the discounted price. The customer benefits more from the exchange ($2,199.99 value for $0 additional cost) than from the refund ($1,319.99 back but now needs to buy a TV again at $1,319.99 or $2,199.99).
+4. If the customer insists on a refund: process at $1,319.99 (the actual purchase price). Do not refund at retail. Refund to original payment method.
+5. Route the defective TV to Samsung for warranty claim (dead pixel clusters are a known panel defect covered under Samsung's warranty). The retailer recovers the wholesale cost ($1,200-1,400 estimated) from Samsung regardless of which option the customer chose.
+6. Flag the transaction in the employee discount programme reporting — perks platforms track return rates by programme member. Excessive returns through discount programmes may indicate fraud (buying discounted, returning for credit, using credit at full value).
+
+**Key Indicators:**
+- Employee discount, military discount, and corporate perks programme returns should ALWAYS refund at the discounted purchase price, never at retail
+- Product defects on discounted purchases should be handled through exchange/warranty rather than return when possible — this preserves the discount benefit for the customer
+- Track return rates by discount programme. An employee discount programme with a 25%+ return rate may be exploited
+- The defective unit's warranty claim goes to the manufacturer regardless of the customer's return channel — always pursue vendor recovery
+
+---
+
+### Edge Case 13: Return of Personalised / Custom-Engraved Product
+
+**Situation:**
+A customer ordered a premium fountain pen (Montblanc Meisterstück, $620.00) with custom engraving ("To David, Love Mom") as a gift. The recipient, David, wants to return it because he already has a Meisterstück and would prefer store credit toward a different pen. The engraving is permanent — it cannot be removed without damaging the pen. The pen is in perfect condition, never used, still in the gift box. The product page stated "Personalised items are final sale and cannot be returned" at the time of purchase, but this notice was in the FAQ section, not at the point of engraving selection in the checkout flow.
+
+**Why It's Tricky:**
+The policy says "final sale." The customer (the gift-giver, "Mom") technically agreed to this by completing the purchase. But the notice was buried in the FAQ, not displayed prominently during the personalisation step of checkout. Consumer protection laws in some states require the return policy to be "conspicuously displayed" at the point of sale. A disclosure buried in the FAQ may not meet the "conspicuous" standard.
+
+The pen is in perfect condition, but the engraving makes it unsellable through any standard channel. It cannot be restocked, sold as open-box, or liquidated — no one wants to buy a pen engraved "To David, Love Mom." The disposition value is effectively $0 (parts/metal recovery only, perhaps $30-50 for the gold nib).
+
+**Common Mistake:**
+Rigidly enforcing the "final sale" policy. While legally defensible if the disclosure was adequate, it's operationally risky: a $620 dispute that reaches a chargeback is expensive to fight, and if the disclosure is found inadequate, the chargeback goes to the cardholder.
+
+The second mistake: accepting the return at full refund as if the engraving doesn't matter. This creates a precedent where customers order personalised items, use them for the event/gift, and return them knowing the "final sale" policy won't be enforced.
+
+**Expert Approach:**
+1. Evaluate the disclosure adequacy. Was "Personalised items are final sale" displayed at the engraving step in checkout, or only in the FAQ? If only in the FAQ, the company has a weak position. If displayed at the engraving selection step, the position is stronger.
+2. Regardless of disclosure, recognise that the gift recipient (David) is not the purchaser and may not have seen any disclosure. His experience is: "I received a gift I can't use, and the store won't help me." This is a customer experience problem even if the policy is sound.
+3. Recommended resolution: offer store credit at 50% of purchase price ($310) as a one-time courtesy. The rationale: the personalisation destroyed the product's resale value, so the full refund cost ($620) is the total cost to the company — there's no recovery. Offering 50% acknowledges both the customer's situation and the company's loss.
+4. If the gift-giver (Mom) contacts you: she has the stronger case since she was the purchaser. If the disclosure was inadequate, offer 75-100% store credit. If adequate, offer 50% and explain.
+5. Systemic fix: add the "final sale" notice directly on the engraving/personalisation UI step, with a checkbox confirmation: "I understand that personalised items cannot be returned or exchanged." This eliminates future ambiguity.
+6. Disposition: the engraved pen has near-zero resale value. If a charity pen collection exists, donate for the tax deduction at fair market value (which may be claimed at a discounted-but-nonzero amount). Otherwise, hold for precious metals recovery if the pen has gold components.
+
+**Key Indicators:**
+- Personalised/custom items should have the "final sale" notice at the point of customisation selection, not just in the FAQ or general return policy
+- Gift recipients of personalised items present a unique challenge — they didn't agree to the policy
+- The cost of a personalised item return is 100% of the purchase price (zero recovery), making even partial credit a significant expense
+- Track personalised item return requests — if they exceed 3% of personalised orders, the disclosure needs improvement
+
+---
+
+### Edge Case 14: Return Attempt on Product Purchased Through Reseller / Unauthorised Channel
+
+**Situation:**
+A customer walks into your brand retail store with a pair of your company's premium running shoes (retail $189.99) claiming they have a stitching defect after 2 weeks of use. The shoes show the defect as described — a seam separation on the toe box. However, when you scan the barcode, there's no matching transaction in your POS system. The customer says they purchased them from an Amazon third-party seller for $139.99. The shoes appear genuine (not counterfeit). The customer argues: "These are YOUR shoes. You should stand behind your product regardless of where I bought them."
+
+**Why It's Tricky:**
+The customer has a point — the product bears your brand, and a stitching defect is a manufacturing quality issue regardless of the retail channel. However, the customer is not your customer — they purchased from an unauthorised reseller. Your return policy covers products purchased from your direct channels (brand stores, website, authorised retailers). Products purchased through unauthorised third-party sellers may be: genuine product diverted from authorised distribution (grey market), returned products resold by a liquidator, or counterfeit (though these appear genuine).
+
+If you accept the return, you're providing warranty-like service for products you didn't sell, and potentially for products that a liquidator already recovered a refund on before reselling. If you refuse, a customer with a defective product carrying your brand walks away angry and tells social media that your brand doesn't stand behind its products.
+
+**Common Mistake:**
+Accepting a full return and refund at retail ($189.99) for a product the customer paid $139.99 for through a different channel. This creates a $50 arbitrage and invites a pattern: buy from cheap reseller, return at brand store for full retail.
+
+**Expert Approach:**
+1. Verify the product is genuine. If your shoes have internal authenticity markers (UV-visible lot codes, specific insole markings, QR codes), check them. If genuine, proceed to step 2. If suspected counterfeit, follow the counterfeit protocol (Edge Case 10).
+2. This is a warranty issue, not a return. The customer is not returning a purchase from your store — they're claiming a manufacturing defect on your branded product. Handle it as a warranty claim, not a return.
+3. Offer a warranty remedy: exchange the defective pair for a new pair of the same model/size from your store inventory. This costs you the wholesale cost (~$85-95) but resolves the customer's issue, protects the brand reputation, and avoids the price arbitrage of a cash refund.
+4. Do NOT offer a cash refund. The customer did not purchase from you. A cash or store credit refund at your retail price creates arbitrage. If the customer insists on a refund, direct them to the seller they purchased from (Amazon third-party seller).
+5. Document the defect for quality purposes. A stitching defect is a manufacturing quality data point regardless of which channel the shoe was sold through. Log the defect against the SKU and lot number.
+6. Consider the long-term: if your brand's products routinely show up in your stores via unauthorised-channel customers with defects, this indicates a distribution control problem. Work with your authorised retailer programme to identify and address grey market diversion.
+
+**Key Indicators:**
+- Products purchased through unauthorised channels should be handled as warranty claims (exchange/repair), not returns (refund)
+- Never offer a cash refund for products not purchased through your direct or authorised channels — this creates a price arbitrage vector
+- Stitching defects, material failures, and construction issues on genuine product are legitimate warranty claims regardless of purchase channel
+- Track the volume of unauthorised-channel warranty claims — high volume indicates distribution leakage
+
+---
+
+### Edge Case 15: Return of Subscription Box Contents
+
+**Situation:**
+A customer subscribed to your premium coffee subscription box ($59.99/month) and received their March delivery containing 3 bags of single-origin coffee (Guatemala, Ethiopia, Sumatra). They want to return the Guatemala and Sumatra bags (2 of 3) because "I only liked the Ethiopian." The bags are sealed and unopened. The customer wants a partial refund of $39.99 (2/3 of the subscription price). Your subscription terms state: "Subscription box contents are curated selections and cannot be returned for partial refund. You may cancel your subscription at any time."
+
+**Why It's Tricky:**
+The subscription model is fundamentally different from à la carte retail. The customer didn't choose these specific coffees — the subscription curated them. The $59.99 price reflects the curated bundle value, not 3 × $19.99 for individual bags. If you allow partial returns on subscription boxes, every subscriber will return the items they don't like, and the subscription model collapses (you'd be selling only the popular items at a discount).
+
+But the customer's request is understandable. They're not asking for something unreasonable — they received products they don't want and they're sealed. From their perspective, it's no different from returning an unwanted product.
+
+**Common Mistake:**
+Allowing the partial return. This sets a precedent that undermines the entire subscription model. If 50% of subscribers return 1-2 items per box, the margin model breaks — subscription boxes are priced with the assumption that the subscriber keeps the full curation.
+
+**Expert Approach:**
+1. Deny the partial return per subscription terms. But frame it as a positive: "Our subscription boxes are curated as a complete experience, and we can't process partial returns. However, we want to make sure you're enjoying every box."
+2. Offer alternatives: (a) "We'd love to know your taste preferences so we can adjust future boxes. Would you prefer lighter, fruitier coffees like the Ethiopian? We can note your preference for the next box." (b) "If you'd like to swap the Guatemala and Sumatra bags, we can offer a one-time exchange for two bags from our Ethiopian selection or other light-roast options." (c) "If the subscription isn't meeting your expectations, we can offer a 15% discount on your next box or switch you to a different subscription tier that focuses on the flavour profiles you prefer."
+3. If the customer insists or threatens to cancel: evaluate the customer's subscription tenure. A customer who has been subscribed for 12+ months at $59.99/month ($720+/year) is worth a one-time $39.99 accommodation. A new subscriber on their first box is not — their expected LTV hasn't been established. For long-tenure subscribers, offer a $20 credit toward their next box as a compromise.
+4. Never refund partial subscription box contents as a standard practice. Every exception must be documented as a one-time accommodation with the business justification.
+5. Systemic improvement: add a taste preference survey to the subscription onboarding. Curating to known preferences reduces "didn't like it" complaints by 30-50%.
+
+**Key Indicators:**
+- Subscription box returns must be handled differently from standard product returns — the subscription model depends on the full-curation assumption
+- Partial refunds on subscription contents destroy unit economics — prevent this from becoming a pattern
+- Customer preference data is the #1 lever for reducing subscription dissatisfaction
+- A customer who threatens to cancel a long-running subscription over one box is worth accommodating; a new subscriber on their first box is not
+
+---
+
+### Edge Case 16: Bulk B2B Return Where Customer Demands Full Retail Refund on Wholesale Purchase
+
+**Situation:**
+A corporate procurement customer (TechStart Inc.) purchased 50 units of a wireless keyboard-mouse combo ($89.99 retail, $52.00 wholesale/B2B price) for their new office. The total B2B order was $2,600.00. Three weeks after delivery, TechStart decides to switch to a different vendor for ergonomic equipment and wants to return all 50 units. All units are sealed, unopened, in original packaging. The B2B sales rep approved the return. However, when the return is processed, the TechStart procurement manager argues: "These are worth $89.99 each on your website — we should get a credit of $4,499.50, not $2,600."
+
+**Why It's Tricky:**
+The customer paid the B2B wholesale price and is entitled to a refund of what they paid ($2,600), not the retail value ($4,499.50). But B2B customers sometimes have procurement teams who don't understand or don't accept that their refund matches their purchase price, not the retail price. They see the retail price on the website and feel short-changed.
+
+Additionally, 50 sealed units returned simultaneously have high restock value but create a volume spike. If these exact keyboard-mouse combos are in your retail inventory at $89.99, the 50 returned units restore significant inventory — good for your stock position.
+
+**Common Mistake:**
+Issuing credit at retail price ($4,499.50) to "keep the business relationship." This creates a $1,899.50 loss and a precedent that B2B returns are refunded at retail. The reverse mistake: making the return process so adversarial that TechStart never orders again — a B2B account that buys 50 units at a time is worth the relationship investment.
+
+**Expert Approach:**
+1. Refund at the actual B2B purchase price: $2,600.00. This is non-negotiable — the refund matches the amount charged. Reference the B2B purchase order and invoice showing the $52.00/unit price.
+2. If the procurement manager pushes back: the B2B sales rep should handle the communication (not the returns team). The sales rep explains: "Your refund matches your purchase price on PO #[X]. The retail price on our website is for individual consumer purchases, which includes different overhead and margin. Your account benefits from our volume pricing, and the refund reflects that same pricing."
+3. Process the return smoothly and quickly: 50 sealed units should be express-processed (no individual inspection needed — batch scan, Grade A, restock). The faster TechStart receives their credit, the less friction around the amount.
+4. Restock all 50 units as new (sealed, Grade A). Inventory value recovered at wholesale ($2,600).
+5. B2B relationship preservation: the sales rep should follow up with TechStart after the return is processed. "We've processed your return. When you're ready to select your new ergonomic equipment, we'd be happy to quote — we carry several lines including [alternatives]." Maintain the relationship for the next order.
+6. Document the return in the B2B account file. If TechStart shows a pattern of bulk ordering and returning, adjust the account terms (restocking fee on B2B returns, or approval-required ordering).
+
+**Key Indicators:**
+- B2B returns are always refunded at the B2B purchase price, never at retail
+- The sales rep (not the returns team) should manage the pricing conversation for B2B accounts
+- 50 sealed units is a high-value restock opportunity — prioritise quick processing
+- B2B accounts that bulk-order and bulk-return may need modified terms (restocking fees, order approval)
+- The relationship value of a B2B account that orders in 50-unit quantities is significant — handle the return professionally
+
+---
+
+### Edge Case 17: Return of a Product that Was Used as Replacement During Warranty Repair
+
+**Situation:**
+A customer brought in a malfunctioning coffee machine ($449.99) for warranty repair 6 weeks ago. As a courtesy, your store loaned them a comparable refurbished unit (same model, valued at $340 in refurbished condition) to use while theirs was being repaired. The original machine has now been repaired and is ready for pickup. The customer picks up their repaired machine but then asks to "return" the loaner unit — they want to keep using it and buy it at a discount rather than return it. When pressed, they say "actually, I want to return both — the repaired one doesn't feel the same, and I've gotten used to the loaner."
+
+**Why It's Tricky:**
+Multiple issues converge: (1) The loaner is not the customer's property — it's company inventory loaned for temporary use. It cannot be "returned" because it was never sold. (2) The customer's original machine was repaired under warranty, not replaced. A warranty repair doesn't restart the return window — the product is the same unit, now fixed. (3) The customer wants to return a repaired product claiming it "doesn't feel the same" — a subjective complaint after a warranty repair.
+
+**Common Mistake:**
+Allowing the customer to "return" the repaired machine as if it were a new purchase. The original purchase was 6+ weeks ago, outside any return window. The warranty repair doesn't create a new return right. The second mistake: selling the loaner to the customer at a steep discount — loaner units are company assets managed through a separate inventory pool.
+
+**Expert Approach:**
+1. Recover the loaner immediately. It is company property, not a product the customer purchased. Thank the customer for using it and collect it back. There is no "return" process for a loaner — it's an asset recovery.
+2. Address the "doesn't feel the same" complaint on the repaired machine. Ask specific questions: "What feels different? Is there a specific function that's not working correctly?" If the repair introduced a new issue (common with appliance repairs), document it and offer to send it back for correction. If the customer simply prefers the loaner (which they've been using for 6 weeks and is now "theirs" psychologically), acknowledge the adjustment period.
+3. The repaired machine cannot be returned under the standard return policy — the purchase date is 6+ weeks ago. However, if the repair is genuinely unsatisfactory, the customer has a warranty claim (the warranty covers the repair work). Offer: "If the repair didn't fully resolve the original issue, we'll send it back for warranty service at no charge."
+4. If the customer wants to purchase a loaner-equivalent unit: offer to sell them a certified refurbished unit from your refurbished inventory at the standard refurbished price. Do not sell them the specific loaner they used (hygiene, wear from their use, and it's an asset, not retail inventory).
+5. If the customer escalates or threatens: the maximum accommodation is a store credit toward a new machine, applied against the original purchase price minus the value of the use they received (6+ weeks of coffee machine use). This is a judgment call for a manager.
+
+**Key Indicators:**
+- Loaner units are company assets, not retail inventory — they follow asset recovery processes, not return processes
+- Warranty repairs do not create new return windows on the original purchase
+- The psychological "endowment effect" of using a loaner for 6 weeks makes customers reluctant to give it back — this is predictable and should be managed with clear loaner terms at the time of issuance
+- Clear loaner agreements at checkout prevent this edge case: "This is a temporary loaner provided during your warranty repair. It remains company property and must be returned when your repair is complete."
+
+---
+
+### Edge Case 18: Return Flood After Viral Negative Product Review
+
+**Situation:**
+A popular tech reviewer (3.2M YouTube subscribers) posts a video titled "DO NOT BUY — [Your Product] is a FIRE HAZARD" about your brand's portable charger ($49.99). The video shows the reviewer stress-testing the charger and it overheating during a fast-charge scenario that exceeds the product's rated capacity. The video has 4.5M views in 48 hours. You've sold 12,000 units of this charger in the past 90 days. In the 48 hours since the video, you've received 340 return requests (compared to a normal rate of ~15 returns/week for this SKU). The product is NOT subject to a CPSC recall. Your engineering team has reviewed the video and confirms the reviewer used the charger outside its specifications (attempted to fast-charge a laptop with a 100W charger rated for 65W max). The product is safe when used as designed.
+
+**Why It's Tricky:**
+The return requests are driven by fear, not defects. The product works as designed — the reviewer used it incorrectly. But you can't tell 340 customers "you're wrong, a YouTuber misused the product." These customers are genuinely afraid their charger will catch fire. Denying the returns creates social media backlash. Accepting all 340 returns (and potentially thousands more as the video continues to circulate) costs $17,000+ in refunds with minimal recovery.
+
+**Common Mistake:**
+Blanket denial: "The product is safe, we're not accepting returns outside the standard window." This triggers a social media firestorm and potentially regulatory scrutiny (even unfounded — CPSC may investigate based on volume of complaints). The second mistake: blanket acceptance at full refund without any counter-narrative, which validates the reviewer's incorrect claim and could cascade to thousands more returns.
+
+**Expert Approach:**
+1. Accept all 340 return requests immediately, without friction. Process standard returns for within-window customers. For outside-window customers, accept as goodwill exception. Do not fight this wave — the cost of 340 returns ($17,000) is trivial compared to the brand damage of denying returns on a "safety concern."
+2. Simultaneously, the PR/communications team must issue a public response within 24 hours. Acknowledge the concern, explain the product's safety specifications, clarify the reviewer's test exceeded rated capacity (without attacking the reviewer personally), and share third-party safety certification data (UL listing, etc.).
+3. Contact the reviewer directly. Offer to send engineering documentation showing the product's safety at rated capacity. Many reviewers will post a correction or follow-up if provided credible technical data. Do not threaten legal action — this backfires.
+4. Monitor the return volume daily. Create a dedicated return code for "viral-concern returns" to track separately from normal returns. If the volume escalates beyond 1,000 units (8%+ return rate), escalate to VP-level for a formal response plan.
+5. Disposition for returned chargers: all within-window Grade A returns restock as new. Returned chargers are safe — the viral concern is about misuse, not a product defect. Do NOT pull the product from sale unless engineering identifies an actual defect.
+6. Proactive defence: update the product listing with prominent max-wattage warnings. Update the product packaging and manual with clearer limitations. This protects against future claims and shows responsiveness.
+7. Track the return curve. Viral-concern returns typically peak 72-96 hours after the video and decay to baseline within 2-3 weeks. Most returns will process before the curve decays.
+
+**Key Indicators:**
+- Viral negative reviews can generate 10-30x normal return volume within 48-72 hours
+- The return cost ($17K on 340 units) is a rounding error compared to the brand/PR cost of mishandling the situation
+- All returned units are fully functional and restockable — the loss is the processing cost, not the product value
+- Counter-narrative timing is critical: respond within 24 hours with technical data, not PR language
+- Track "viral-concern return" codes separately — this data informs the risk assessment of social media product coverage
+
+---
+
+### Edge Case 19: Customer Returns an Item They Didn't Purchase (Shipping Error by Another Retailer)
+
+**Situation:**
+A customer contacts your returns team stating they want to return a Le Creuset Dutch Oven ($380.00) that "isn't what they ordered." They provide their order number, which shows they ordered a KitchenAid Stand Mixer ($429.99). When the return arrives, inspection confirms it is indeed a Le Creuset Dutch Oven — a product you carry and sell, but not the product this customer ordered. The serial/lot number on the Dutch Oven matches your inventory records as a unit that was in your warehouse. Investigation reveals: a fulfillment packing error sent this customer's KitchenAid mixer to a different customer, and this customer received another customer's Le Creuset order.
+
+**Why It's Tricky:**
+This is a cross-shipment fulfillment error. Two customers are affected: Customer A received the wrong product (the Le Creuset instead of their KitchenAid), and Customer B received Customer A's KitchenAid instead of their Le Creuset. Both customers need their correct products. Both may have already initiated returns or complaints. The fulfillment centre sent two correct products to two wrong addresses.
+
+The financial reconciliation is complex: Customer A paid $429.99 for a KitchenAid and received a $380 Le Creuset. Customer B paid $380 for a Le Creuset and received a $429.99 KitchenAid. Neither customer should be penalised — this is entirely the company's error.
+
+**Common Mistake:**
+Processing Customer A's return as a standard return and shipping them a replacement KitchenAid — but not connecting the dots to realise Customer B also received the wrong product. The second customer may not have complained yet (they might have accepted the KitchenAid thinking it was correct, or they might be planning to return it separately). Handling these as two independent returns instead of one linked cross-shipment doubles the logistical cost.
+
+**Expert Approach:**
+1. Identify the cross-shipment immediately. When Customer A's return arrives as a Le Creuset instead of a KitchenAid, fulfillment should trace the packing records to find where the KitchenAid went. This identifies Customer B.
+2. Contact Customer B proactively — don't wait for them to realise the error. "We've discovered a packing error and you may have received a KitchenAid Stand Mixer instead of the Le Creuset Dutch Oven you ordered. We apologise for the mix-up and would like to ship your correct Le Creuset immediately."
+3. For Customer A: ship the correct KitchenAid via expedited shipping (2-day minimum) with a prepaid return label for the Le Creuset they received. Include a $25-50 store credit for the inconvenience. Do not wait for the Le Creuset to be returned before shipping the KitchenAid — the customer has already waited.
+4. For Customer B: same approach — ship the correct Le Creuset via expedited shipping with a prepaid return label for the KitchenAid. Include a $25-50 store credit.
+5. Inventory reconciliation: once both wrong items are returned, they go back to their respective inventory positions. Net inventory impact should be zero once both returns are processed. Track both under a single cross-shipment incident number.
+6. Root cause: investigate the fulfillment error. Cross-shipments typically happen when two orders are being packed simultaneously at adjacent stations and the products get physically swapped. If this is a recurring issue, the packing process needs a scan-verify step where the packed product's barcode is scanned against the order before sealing.
+7. Financial: the expedited re-shipping cost ($15-25 per shipment × 2 = $30-50) plus store credits ($50-100 total) plus return shipping on both wrong items ($15-25 × 2 = $30-50) totals $110-200 in error resolution cost. The fulfillment error should be charged to the fulfillment operation's error budget, not the returns budget.
+
+**Key Indicators:**
+- When a return arrives with a different product than expected, always check if it's a cross-shipment before processing as a standard return
+- Cross-shipments affect two customers — proactively contact both, even if only one has complained
+- Ship correct items before collecting wrong items — the customer should not wait for the return logistics to resolve
+- Cross-shipment resolution costs $110-200 per incident — this makes the business case for scan-verify packing processes
+- Track cross-shipment rates: target < 0.05% of orders. If rate exceeds 0.1%, the packing process has a systemic gap
+
+**Documentation Required:**
+- Cross-shipment incident record linking both customer orders
+- Packing slip and warehouse records showing the error point
+- Communication records with both customers
+- Shipping records for both replacement shipments
+- Return tracking for both wrong-item returns
+- Root cause analysis note for fulfillment operations
+
+---
+
+### Edge Case 20: Return of a Product That Requires Data Destruction Certification
+
+**Situation:**
+A corporate customer returns 25 laptops (Dell Latitude 5540, $1,199 each, $29,975 total) that were originally purchased for a project team that has been disbanded. The laptops were used for 10 months and contain corporate data — emails, documents, proprietary software, and potentially regulated data (the customer works in healthcare and some laptops may have had access to PHI — Protected Health Information). The customer's IT department performed a standard Windows reset ("Reset this PC") before returning, but they're asking: "Can you certify that these drives have been wiped to HIPAA-compliant standards? Our compliance team requires a certificate of data destruction."
+
+**Why It's Tricky:**
+A standard Windows "Reset this PC" does not meet NIST 800-88 data sanitisation standards. The data is technically recoverable with forensic tools. For a healthcare company with potential PHI on the devices, HIPAA requires that data destruction be documented and verifiable. If you restock or liquidate these laptops without proper data destruction and patient data is later recovered from a resold unit, the liability exposure is enormous — for both the healthcare company and for you as the entity that handled the devices.
+
+Your standard returns process doesn't include NIST 800-88 data sanitisation. You inspect, grade, and disposition — but data destruction certification is a service, not a standard returns step.
+
+**Common Mistake:**
+Accepting the return and processing it as standard — wiping the drives with your normal reset process and restocking. If the normal reset doesn't meet NIST 800-88, and the customer later requires a certificate you can't provide, you have a compliance gap. The second mistake: telling the customer "data destruction is your responsibility" and refusing to help — they're a $30K customer and this is a reasonable request.
+
+**Expert Approach:**
+1. Accept the return of all 25 laptops. Process the RMA normally for grading and refund calculation.
+2. For data destruction: this is a service, not a standard return step. If you have an in-house NIST 800-88 compliant data wipe capability (many return centres do for electronics), offer it as a service. Use a certified tool (Blancco, KillDisk, DBAN) that produces a per-device certificate documenting: device serial number, date, sanitisation method used, and pass/fail result.
+3. If you don't have in-house capability: partner with a certified ITAD (IT Asset Disposition) provider. They will perform the wipe, issue certificates, and handle any drives that fail the wipe (drives that fail must be physically destroyed — degaussed or shredded).
+4. Charge for the service. NIST 800-88 data sanitisation is $5-15 per device in-house, $15-30 per device through an ITAD partner. For 25 laptops: $125-750 total. Offer this as an add-on to the return. Most corporate customers will pay — their alternative is to hire an ITAD provider independently, which costs more.
+5. Provide the individual certificates to the customer's compliance team. Each certificate should reference: NIST SP 800-88 Rev 1, the sanitisation method (Clear, Purge, or Destroy), the device serial number, and the date.
+6. After data destruction is certified: proceed with normal disposition. 10-month-old Dell Latitude laptops with certified data wipes sell well in the refurbished market at $500-700 each.
+7. Systemic: for all corporate/enterprise laptop and device returns, add a data destruction service option at RMA initiation: "Does this device contain corporate or regulated data? We offer certified NIST 800-88 data destruction for $X per device."
+
+**Key Indicators:**
+- Standard "Reset this PC" and factory resets do NOT meet NIST 800-88 sanitisation standards — data is recoverable with forensic tools
+- Healthcare (HIPAA), financial (GLBA), government (NIST), and education (FERPA) customers have regulatory data destruction requirements
+- Data destruction certification is a value-add service that corporate customers will pay for — it's a revenue opportunity, not just a cost
+- Never restock or liquidate enterprise devices without verifying data has been properly sanitised — the liability exposure from a data breach on a resold device is unlimited
+- Keep copies of all data destruction certificates for your own compliance records — if a device you resold is later found to contain recoverable data, the certificate is your defence
diff --git a/skills/reverse-engineer/SKILL.md b/skills/reverse-engineer/SKILL.md
index 8238c7ac..333ee99e 100644
--- a/skills/reverse-engineer/SKILL.md
+++ b/skills/reverse-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: reverse-engineer
-description: "Expert reverse engineer specializing in binary analysis,"
+description: |
+ Expert reverse engineer specializing in binary analysis,
disassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,
radare2, x64dbg, and modern RE toolchains. Handles executable analysis,
library inspection, protocol extraction, and vulnerability research. Use
diff --git a/skills/risk-manager/SKILL.md b/skills/risk-manager/SKILL.md
index e860fe43..7ac39dc7 100644
--- a/skills/risk-manager/SKILL.md
+++ b/skills/risk-manager/SKILL.md
@@ -1,6 +1,7 @@
---
name: risk-manager
-description: "Monitor portfolio risk, R-multiples, and position limits. Creates"
+description: |
+ Monitor portfolio risk, R-multiples, and position limits. Creates
hedging strategies, calculates expectancy, and implements stop-losses. Use
PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
metadata:
diff --git a/skills/ruby-pro/SKILL.md b/skills/ruby-pro/SKILL.md
index d8296a73..bbc6b20b 100644
--- a/skills/ruby-pro/SKILL.md
+++ b/skills/ruby-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: ruby-pro
-description: "Write idiomatic Ruby code with metaprogramming, Rails patterns, and"
+description: |
+ Write idiomatic Ruby code with metaprogramming, Rails patterns, and
performance optimization. Specializes in Ruby on Rails, gem development, and
testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or
complex Ruby features.
diff --git a/skills/rust-pro/SKILL.md b/skills/rust-pro/SKILL.md
index 56b57f23..c6fa0907 100644
--- a/skills/rust-pro/SKILL.md
+++ b/skills/rust-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: rust-pro
-description: "Master Rust 1.75+ with modern async patterns, advanced type system"
+description: |
+ Master Rust 1.75+ with modern async patterns, advanced type system
features, and production-ready systems programming. Expert in the latest Rust
ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for
Rust development, performance optimization, or systems programming.
diff --git a/skills/sales-automator/SKILL.md b/skills/sales-automator/SKILL.md
index 2978913c..d03be643 100644
--- a/skills/sales-automator/SKILL.md
+++ b/skills/sales-automator/SKILL.md
@@ -1,6 +1,7 @@
---
name: sales-automator
-description: "Draft cold emails, follow-ups, and proposal templates. Creates"
+description: |
+ Draft cold emails, follow-ups, and proposal templates. Creates
pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales
outreach or lead nurturing.
metadata:
diff --git a/skills/scala-pro/SKILL.md b/skills/scala-pro/SKILL.md
index 6845992a..4f0b4fb7 100644
--- a/skills/scala-pro/SKILL.md
+++ b/skills/scala-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: scala-pro
-description: "Master enterprise-grade Scala development with functional"
+description: |
+ Master enterprise-grade Scala development with functional
programming, distributed systems, and big data processing. Expert in Apache
Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use
PROACTIVELY for Scala system design, performance optimization, or enterprise
diff --git a/skills/schema-markup/SKILL.md b/skills/schema-markup/SKILL.md
index 98474969..45da25cd 100644
--- a/skills/schema-markup/SKILL.md
+++ b/skills/schema-markup/SKILL.md
@@ -1,6 +1,6 @@
---
name: schema-markup
-description: ">"
+description: >
Design, validate, and optimize schema.org structured data for eligibility,
correctness, and measurable SEO impact. Use when the user wants to add, fix,
audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates
diff --git a/skills/security-auditor/SKILL.md b/skills/security-auditor/SKILL.md
index 8704c428..f4a6b0da 100644
--- a/skills/security-auditor/SKILL.md
+++ b/skills/security-auditor/SKILL.md
@@ -1,6 +1,7 @@
---
name: security-auditor
-description: "Expert security auditor specializing in DevSecOps, comprehensive"
+description: |
+ Expert security auditor specializing in DevSecOps, comprehensive
cybersecurity, and compliance frameworks. Masters vulnerability assessment,
threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud
security, and security automation. Handles DevSecOps integration, compliance
diff --git a/skills/security-scanning-security-sast/SKILL.md b/skills/security-scanning-security-sast/SKILL.md
index 8f15568d..84aae929 100644
--- a/skills/security-scanning-security-sast/SKILL.md
+++ b/skills/security-scanning-security-sast/SKILL.md
@@ -1,6 +1,7 @@
---
name: security-scanning-security-sast
-description: "Static Application Security Testing (SAST) for code vulnerability"
+description: |
+ Static Application Security Testing (SAST) for code vulnerability
analysis across multiple languages and frameworks
metadata:
globs: "**/*.py, **/*.js, **/*.ts, **/*.java, **/*.rb, **/*.go, **/*.rs, **/*.php"
diff --git a/skills/seo-audit/SKILL.md b/skills/seo-audit/SKILL.md
index 8c8b91d0..de3ab23a 100644
--- a/skills/seo-audit/SKILL.md
+++ b/skills/seo-audit/SKILL.md
@@ -1,6 +1,6 @@
---
name: seo-audit
-description: ">"
+description: >
Diagnose and audit SEO issues affecting crawlability, indexation, rankings,
and organic performance. Use when the user asks for an SEO audit, technical SEO
review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check.
diff --git a/skills/seo-authority-builder/SKILL.md b/skills/seo-authority-builder/SKILL.md
index 78322085..2288399b 100644
--- a/skills/seo-authority-builder/SKILL.md
+++ b/skills/seo-authority-builder/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-authority-builder
-description: "Analyzes content for E-E-A-T signals and suggests improvements to"
+description: |
+ Analyzes content for E-E-A-T signals and suggests improvements to
build authority and trust. Identifies missing credibility elements. Use
PROACTIVELY for YMYL topics.
metadata:
diff --git a/skills/seo-cannibalization-detector/SKILL.md b/skills/seo-cannibalization-detector/SKILL.md
index 30f7f19b..cfc2c16e 100644
--- a/skills/seo-cannibalization-detector/SKILL.md
+++ b/skills/seo-cannibalization-detector/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-cannibalization-detector
-description: "Analyzes multiple provided pages to identify keyword overlap and"
+description: |
+ Analyzes multiple provided pages to identify keyword overlap and
potential cannibalization issues. Suggests differentiation strategies. Use
PROACTIVELY when reviewing similar content.
metadata:
diff --git a/skills/seo-content-auditor/SKILL.md b/skills/seo-content-auditor/SKILL.md
index 8e747996..0f8a212f 100644
--- a/skills/seo-content-auditor/SKILL.md
+++ b/skills/seo-content-auditor/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-auditor
-description: "Analyzes provided content for quality, E-E-A-T signals, and SEO"
+description: |
+ Analyzes provided content for quality, E-E-A-T signals, and SEO
best practices. Scores content and provides improvement recommendations based
on established guidelines. Use PROACTIVELY for content review.
metadata:
diff --git a/skills/seo-content-planner/SKILL.md b/skills/seo-content-planner/SKILL.md
index 66c7797f..cd18347d 100644
--- a/skills/seo-content-planner/SKILL.md
+++ b/skills/seo-content-planner/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-planner
-description: "Creates comprehensive content outlines and topic clusters for SEO."
+description: |
+ Creates comprehensive content outlines and topic clusters for SEO.
Plans content calendars and identifies topic gaps. Use PROACTIVELY for content
strategy and planning.
metadata:
diff --git a/skills/seo-content-refresher/SKILL.md b/skills/seo-content-refresher/SKILL.md
index 79ca9440..de5672ef 100644
--- a/skills/seo-content-refresher/SKILL.md
+++ b/skills/seo-content-refresher/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-refresher
-description: "Identifies outdated elements in provided content and suggests"
+description: |
+ Identifies outdated elements in provided content and suggests
updates to maintain freshness. Finds statistics, dates, and examples that need
updating. Use PROACTIVELY for older content.
metadata:
diff --git a/skills/seo-content-writer/SKILL.md b/skills/seo-content-writer/SKILL.md
index bc80aa22..04146556 100644
--- a/skills/seo-content-writer/SKILL.md
+++ b/skills/seo-content-writer/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-writer
-description: "Writes SEO-optimized content based on provided keywords and topic"
+description: |
+ Writes SEO-optimized content based on provided keywords and topic
briefs. Creates engaging, comprehensive content following best practices. Use
PROACTIVELY for content creation tasks.
metadata:
diff --git a/skills/seo-fundamentals/SKILL.md b/skills/seo-fundamentals/SKILL.md
index 71212a55..7d12e82b 100644
--- a/skills/seo-fundamentals/SKILL.md
+++ b/skills/seo-fundamentals/SKILL.md
@@ -1,6 +1,6 @@
---
name: seo-fundamentals
-description: ">"
+description: >
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations,
content quality, and how modern search engines evaluate pages. This skill explains
*why* SEO works, not how to execute specific optimizations.
diff --git a/skills/seo-keyword-strategist/SKILL.md b/skills/seo-keyword-strategist/SKILL.md
index f0c64c9e..7d75baba 100644
--- a/skills/seo-keyword-strategist/SKILL.md
+++ b/skills/seo-keyword-strategist/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-keyword-strategist
-description: "Analyzes keyword usage in provided content, calculates density,"
+description: |
+ Analyzes keyword usage in provided content, calculates density,
suggests semantic variations and LSI keywords based on the topic. Prevents
over-optimization. Use PROACTIVELY for content optimization.
metadata:
diff --git a/skills/seo-meta-optimizer/SKILL.md b/skills/seo-meta-optimizer/SKILL.md
index d1cf7499..c749b281 100644
--- a/skills/seo-meta-optimizer/SKILL.md
+++ b/skills/seo-meta-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-meta-optimizer
-description: "Creates optimized meta titles, descriptions, and URL suggestions"
+description: |
+ Creates optimized meta titles, descriptions, and URL suggestions
based on character limits and best practices. Generates compelling,
keyword-rich metadata. Use PROACTIVELY for new content.
metadata:
diff --git a/skills/seo-snippet-hunter/SKILL.md b/skills/seo-snippet-hunter/SKILL.md
index eab15c08..be67041e 100644
--- a/skills/seo-snippet-hunter/SKILL.md
+++ b/skills/seo-snippet-hunter/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-snippet-hunter
-description: "Formats content to be eligible for featured snippets and SERP"
+description: |
+ Formats content to be eligible for featured snippets and SERP
features. Creates snippet-optimized content blocks based on best practices.
Use PROACTIVELY for question-based content.
metadata:
diff --git a/skills/seo-structure-architect/SKILL.md b/skills/seo-structure-architect/SKILL.md
index d9c0644b..7d28c670 100644
--- a/skills/seo-structure-architect/SKILL.md
+++ b/skills/seo-structure-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-structure-architect
-description: "Analyzes and optimizes content structure including header"
+description: |
+ Analyzes and optimizes content structure including header
hierarchy, suggests schema markup, and internal linking opportunities. Creates
search-friendly content organization. Use PROACTIVELY for content structuring.
metadata:
diff --git a/skills/sql-pro/SKILL.md b/skills/sql-pro/SKILL.md
index ddb5a988..99f4582b 100644
--- a/skills/sql-pro/SKILL.md
+++ b/skills/sql-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: sql-pro
-description: "Master modern SQL with cloud-native databases, OLTP/OLAP"
+description: |
+ Master modern SQL with cloud-native databases, OLTP/OLAP
optimization, and advanced query techniques. Expert in performance tuning,
data modeling, and hybrid analytical systems. Use PROACTIVELY for database
optimization or complex analysis.
diff --git a/skills/startup-analyst/SKILL.md b/skills/startup-analyst/SKILL.md
index 9dd9fbe9..4d97afd3 100644
--- a/skills/startup-analyst/SKILL.md
+++ b/skills/startup-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-analyst
-description: "Expert startup business analyst specializing in market sizing,"
+description: |
+ Expert startup business analyst specializing in market sizing,
financial modeling, competitive analysis, and strategic planning for
early-stage companies. Use PROACTIVELY when the user asks about market
opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive
diff --git a/skills/startup-business-analyst-business-case/SKILL.md b/skills/startup-business-analyst-business-case/SKILL.md
index 7e21641c..554aea60 100644
--- a/skills/startup-business-analyst-business-case/SKILL.md
+++ b/skills/startup-business-analyst-business-case/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-business-case
-description: "Generate comprehensive investor-ready business case document with"
+description: |
+ Generate comprehensive investor-ready business case document with
market, solution, financials, and strategy
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/skills/startup-business-analyst-financial-projections/SKILL.md b/skills/startup-business-analyst-financial-projections/SKILL.md
index 1e09b5db..f68ca0f2 100644
--- a/skills/startup-business-analyst-financial-projections/SKILL.md
+++ b/skills/startup-business-analyst-financial-projections/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-financial-projections
-description: "Create detailed 3-5 year financial model with revenue, costs, cash"
+description: |
+ Create detailed 3-5 year financial model with revenue, costs, cash
flow, and scenarios
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/skills/startup-business-analyst-market-opportunity/SKILL.md b/skills/startup-business-analyst-market-opportunity/SKILL.md
index 013d551a..8d73f982 100644
--- a/skills/startup-business-analyst-market-opportunity/SKILL.md
+++ b/skills/startup-business-analyst-market-opportunity/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-market-opportunity
-description: "Generate comprehensive market opportunity analysis with TAM/SAM/SOM"
+description: |
+ Generate comprehensive market opportunity analysis with TAM/SAM/SOM
calculations
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/skills/startup-financial-modeling/SKILL.md b/skills/startup-financial-modeling/SKILL.md
index 4921e7ea..a80405d5 100644
--- a/skills/startup-financial-modeling/SKILL.md
+++ b/skills/startup-financial-modeling/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-financial-modeling
-description: "This skill should be used when the user asks to \\\"create financial"
+description: |
+ This skill should be used when the user asks to \\\"create financial
projections", "build a financial model", "forecast revenue", "calculate burn
rate", "estimate runway", "model cash flow", or requests 3-5 year financial
planning for a startup.
diff --git a/skills/startup-metrics-framework/SKILL.md b/skills/startup-metrics-framework/SKILL.md
index 7c8acdc3..cdd8c616 100644
--- a/skills/startup-metrics-framework/SKILL.md
+++ b/skills/startup-metrics-framework/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-metrics-framework
-description: "This skill should be used when the user asks about \\\"key startup"
+description: |
+ This skill should be used when the user asks about \\\"key startup
metrics", "SaaS metrics", "CAC and LTV", "unit economics", "burn multiple",
"rule of 40", "marketplace metrics", or requests guidance on tracking and
optimizing business performance metrics.
diff --git a/skills/tdd-orchestrator/SKILL.md b/skills/tdd-orchestrator/SKILL.md
index 5878ac1c..700aa500 100644
--- a/skills/tdd-orchestrator/SKILL.md
+++ b/skills/tdd-orchestrator/SKILL.md
@@ -1,6 +1,7 @@
---
name: tdd-orchestrator
-description: "Master TDD orchestrator specializing in red-green-refactor"
+description: |
+ Master TDD orchestrator specializing in red-green-refactor
discipline, multi-agent workflow coordination, and comprehensive test-driven
development practices. Enforces TDD best practices across teams with
AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD
diff --git a/skills/team-composition-analysis/SKILL.md b/skills/team-composition-analysis/SKILL.md
index 9ce88e72..d1229a2c 100644
--- a/skills/team-composition-analysis/SKILL.md
+++ b/skills/team-composition-analysis/SKILL.md
@@ -1,6 +1,7 @@
---
name: team-composition-analysis
-description: "This skill should be used when the user asks to \\\"plan team"
+description: |
+ This skill should be used when the user asks to \\\"plan team
structure", "determine hiring needs", "design org chart", "calculate
compensation", "plan equity allocation", or requests organizational design and
headcount planning for a startup.
diff --git a/skills/temporal-python-pro/SKILL.md b/skills/temporal-python-pro/SKILL.md
index 261fa049..eb233499 100644
--- a/skills/temporal-python-pro/SKILL.md
+++ b/skills/temporal-python-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: temporal-python-pro
-description: "Master Temporal workflow orchestration with Python SDK. Implements"
+description: |
+ Master Temporal workflow orchestration with Python SDK. Implements
durable workflows, saga patterns, and distributed transactions. Covers
async/await, testing strategies, and production deployment. Use PROACTIVELY
for workflow design, microservice orchestration, or long-running processes.
diff --git a/skills/terraform-specialist/SKILL.md b/skills/terraform-specialist/SKILL.md
index 146087f7..8ec685f9 100644
--- a/skills/terraform-specialist/SKILL.md
+++ b/skills/terraform-specialist/SKILL.md
@@ -1,6 +1,7 @@
---
name: terraform-specialist
-description: "Expert Terraform/OpenTofu specialist mastering advanced IaC"
+description: |
+ Expert Terraform/OpenTofu specialist mastering advanced IaC
automation, state management, and enterprise infrastructure patterns. Handles
complex module design, multi-cloud deployments, GitOps workflows, policy as
code, and CI/CD integration. Covers migration strategies, security best
diff --git a/skills/test-automator/SKILL.md b/skills/test-automator/SKILL.md
index e5fb2b0e..16f382b5 100644
--- a/skills/test-automator/SKILL.md
+++ b/skills/test-automator/SKILL.md
@@ -1,6 +1,7 @@
---
name: test-automator
-description: "Master AI-powered test automation with modern frameworks,"
+description: |
+ Master AI-powered test automation with modern frameworks,
self-healing tests, and comprehensive quality engineering. Build scalable
testing strategies with advanced CI/CD integration. Use PROACTIVELY for
testing automation or quality assurance.
diff --git a/skills/track-management/SKILL.md b/skills/track-management/SKILL.md
index c87f2591..7459de2f 100644
--- a/skills/track-management/SKILL.md
+++ b/skills/track-management/SKILL.md
@@ -1,6 +1,7 @@
---
name: track-management
-description: "Use this skill when creating, managing, or working with Conductor"
+description: |
+ Use this skill when creating, managing, or working with Conductor
tracks - the logical work units for features, bugs, and refactors. Applies to
spec.md, plan.md, and track lifecycle operations.
metadata:
diff --git a/skills/tutorial-engineer/SKILL.md b/skills/tutorial-engineer/SKILL.md
index f7ec59e1..23169adb 100644
--- a/skills/tutorial-engineer/SKILL.md
+++ b/skills/tutorial-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: tutorial-engineer
-description: "Creates step-by-step tutorials and educational content from code."
+description: |
+ Creates step-by-step tutorials and educational content from code.
Transforms complex concepts into progressive learning experiences with
hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,
or concept explanations.
diff --git a/skills/typescript-expert/SKILL.md b/skills/typescript-expert/SKILL.md
index 8263f3d5..3de9f638 100644
--- a/skills/typescript-expert/SKILL.md
+++ b/skills/typescript-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: typescript-expert
-description: ">-"
+description: >-
TypeScript and JavaScript expert with deep knowledge of type-level
programming, performance optimization, monorepo management, migration
strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript
diff --git a/skills/typescript-pro/SKILL.md b/skills/typescript-pro/SKILL.md
index 31cf0e42..d65babb0 100644
--- a/skills/typescript-pro/SKILL.md
+++ b/skills/typescript-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: typescript-pro
-description: "Master TypeScript with advanced types, generics, and strict type"
+description: |
+ Master TypeScript with advanced types, generics, and strict type
safety. Handles complex type systems, decorators, and enterprise-grade
patterns. Use PROACTIVELY for TypeScript architecture, type inference
optimization, or advanced typing patterns.
diff --git a/skills/ui-ux-designer/SKILL.md b/skills/ui-ux-designer/SKILL.md
index 24e6ec58..a102824c 100644
--- a/skills/ui-ux-designer/SKILL.md
+++ b/skills/ui-ux-designer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ui-ux-designer
-description: "Create interface designs, wireframes, and design systems. Masters"
+description: |
+ Create interface designs, wireframes, and design systems. Masters
user research, accessibility standards, and modern design tools. Specializes
in design tokens, component libraries, and inclusive design. Use PROACTIVELY
for design systems, user flows, or interface optimization.
diff --git a/skills/ui-visual-validator/SKILL.md b/skills/ui-visual-validator/SKILL.md
index 2850020d..f455e73e 100644
--- a/skills/ui-visual-validator/SKILL.md
+++ b/skills/ui-visual-validator/SKILL.md
@@ -1,6 +1,7 @@
---
name: ui-visual-validator
-description: "Rigorous visual validation expert specializing in UI testing,"
+description: |
+ Rigorous visual validation expert specializing in UI testing,
design system compliance, and accessibility verification. Masters screenshot
analysis, visual regression testing, and component validation. Use PROACTIVELY
to verify UI modifications have achieved their intended goals through
diff --git a/skills/unity-developer/SKILL.md b/skills/unity-developer/SKILL.md
index e6d114e0..53dbbadd 100644
--- a/skills/unity-developer/SKILL.md
+++ b/skills/unity-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: unity-developer
-description: "Build Unity games with optimized C# scripts, efficient rendering,"
+description: |
+ Build Unity games with optimized C# scripts, efficient rendering,
and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and
cross-platform deployment. Handles gameplay systems, UI implementation, and
platform optimization. Use PROACTIVELY for Unity performance issues, game
diff --git a/skills/workflow-patterns/SKILL.md b/skills/workflow-patterns/SKILL.md
index 717f3c89..f4f23e1d 100644
--- a/skills/workflow-patterns/SKILL.md
+++ b/skills/workflow-patterns/SKILL.md
@@ -1,6 +1,7 @@
---
name: workflow-patterns
-description: "Use this skill when implementing tasks according to Conductor's TDD"
+description: |
+ Use this skill when implementing tasks according to Conductor's TDD
workflow, handling phase checkpoints, managing git commits for tasks, or
understanding the verification protocol.
metadata:
From 689a825411eb452210ed18be25ccefac02098114 Mon Sep 17 00:00:00 2001
From: Zied
Date: Thu, 26 Feb 2026 11:40:51 +0100
Subject: [PATCH 09/11] Refactor code structure for improved readability and
maintainability
---
SKILLS_UPDATE_GUIDE.md | 89 +
START_APP.bat | 70 +-
package.json | 1 +
skills_index.json | 4406 +++++++++--------
web-app/package-lock.json | 11 +
web-app/public/skills.json | 4406 +++++++++--------
.../skills/00-andruia-consultant/SKILL.md | 60 +
.../skills/10-andruia-skill-smith/SKILL.MD | 41 +
.../20-andruia-niche-intelligence/SKILL.md | 62 +
web-app/public/skills/agentfolio/SKILL.md | 96 +
web-app/public/skills/ai-engineer/SKILL.md | 19 +-
.../public/skills/analytics-tracking/SKILL.md | 2 +-
web-app/public/skills/angular/SKILL.md | 2 +-
web-app/public/skills/api-documenter/SKILL.md | 3 +-
web-app/public/skills/appdeploy/SKILL.md | 209 +
.../public/skills/arm-cortex-expert/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-ai-agents-persistent-java/SKILL.md | 2 +-
.../skills/azure-ai-contentsafety-py/SKILL.md | 2 +-
.../azure-ai-contentunderstanding-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
web-app/public/skills/azure-ai-ml-py/SKILL.md | 2 +-
.../skills/azure-ai-openai-dotnet/SKILL.md | 2 +-
.../skills/azure-ai-projects-dotnet/SKILL.md | 2 +-
.../skills/azure-ai-projects-java/SKILL.md | 2 +-
.../skills/azure-ai-textanalytics-py/SKILL.md | 2 +-
.../skills/azure-ai-transcription-py/SKILL.md | 2 +-
.../azure-ai-translation-document-py/SKILL.md | 2 +-
.../azure-ai-translation-text-py/SKILL.md | 2 +-
.../azure-ai-vision-imageanalysis-py/SKILL.md | 2 +-
.../skills/azure-ai-voicelive-dotnet/SKILL.md | 2 +-
.../skills/azure-ai-voicelive-java/SKILL.md | 2 +-
.../skills/azure-ai-voicelive-ts/SKILL.md | 2 +-
.../azure-appconfiguration-java/SKILL.md | 2 +-
.../skills/azure-appconfiguration-py/SKILL.md | 2 +-
.../skills/azure-compute-batch-java/SKILL.md | 2 +-
.../azure-containerregistry-py/SKILL.md | 2 +-
.../public/skills/azure-cosmos-java/SKILL.md | 2 +-
.../public/skills/azure-cosmos-py/SKILL.md | 2 +-
.../public/skills/azure-cosmos-rust/SKILL.md | 2 +-
.../public/skills/azure-cosmos-ts/SKILL.md | 2 +-
.../skills/azure-data-tables-py/SKILL.md | 2 +-
.../skills/azure-eventgrid-dotnet/SKILL.md | 2 +-
.../public/skills/azure-eventgrid-py/SKILL.md | 2 +-
.../skills/azure-eventhub-dotnet/SKILL.md | 2 +-
.../public/skills/azure-eventhub-py/SKILL.md | 2 +-
.../skills/azure-eventhub-rust/SKILL.md | 2 +-
.../skills/azure-identity-dotnet/SKILL.md | 2 +-
.../public/skills/azure-identity-py/SKILL.md | 2 +-
.../skills/azure-identity-rust/SKILL.md | 2 +-
.../azure-keyvault-certificates-rust/SKILL.md | 2 +-
.../skills/azure-keyvault-keys-rust/SKILL.md | 2 +-
.../public/skills/azure-keyvault-py/SKILL.md | 2 +-
.../azure-keyvault-secrets-rust/SKILL.md | 2 +-
.../skills/azure-maps-search-dotnet/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-mgmt-apicenter-dotnet/SKILL.md | 2 +-
.../skills/azure-mgmt-apicenter-py/SKILL.md | 2 +-
.../azure-mgmt-apimanagement-dotnet/SKILL.md | 2 +-
.../azure-mgmt-apimanagement-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-mgmt-botservice-dotnet/SKILL.md | 2 +-
.../skills/azure-mgmt-botservice-py/SKILL.md | 2 +-
.../skills/azure-mgmt-fabric-dotnet/SKILL.md | 2 +-
.../skills/azure-mgmt-fabric-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-monitor-ingestion-java/SKILL.md | 2 +-
.../azure-monitor-ingestion-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-monitor-opentelemetry-py/SKILL.md | 2 +-
.../skills/azure-monitor-query-java/SKILL.md | 2 +-
.../skills/azure-monitor-query-py/SKILL.md | 2 +-
.../public/skills/azure-postgres-ts/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../azure-search-documents-dotnet/SKILL.md | 2 +-
.../skills/azure-search-documents-py/SKILL.md | 2 +-
.../SKILL.md | 2 +-
.../skills/azure-servicebus-dotnet/SKILL.md | 2 +-
.../skills/azure-servicebus-py/SKILL.md | 2 +-
.../azure-speech-to-text-rest-py/SKILL.md | 2 +-
.../skills/azure-storage-blob-py/SKILL.md | 2 +-
.../skills/azure-storage-blob-rust/SKILL.md | 2 +-
.../skills/azure-storage-blob-ts/SKILL.md | 2 +-
.../azure-storage-file-datalake-py/SKILL.md | 2 +-
.../azure-storage-file-share-py/SKILL.md | 2 +-
.../azure-storage-file-share-ts/SKILL.md | 2 +-
.../skills/azure-storage-queue-py/SKILL.md | 2 +-
.../skills/azure-storage-queue-ts/SKILL.md | 2 +-
.../public/skills/backend-architect/SKILL.md | 3 +-
.../skills/backend-security-coder/SKILL.md | 3 +-
web-app/public/skills/bash-pro/SKILL.md | 3 +-
.../public/skills/bevy-ecs-expert/SKILL.md | 30 +-
.../skills/blockchain-developer/SKILL.md | 3 +-
.../public/skills/business-analyst/SKILL.md | 3 +-
web-app/public/skills/c4-code/SKILL.md | 3 +-
web-app/public/skills/c4-component/SKILL.md | 3 +-
web-app/public/skills/c4-container/SKILL.md | 3 +-
web-app/public/skills/c4-context/SKILL.md | 3 +-
.../carrier-relationship-management/SKILL.md | 203 +
.../references/communication-templates.md | 584 +++
.../references/decision-frameworks.md | 534 ++
.../references/edge-cases.md | 527 ++
.../chrome-extension-developer/SKILL.md | 84 +
.../public/skills/cloud-architect/SKILL.md | 3 +-
.../skills/cloudflare-workers-expert/SKILL.md | 90 +
.../skills/competitive-landscape/SKILL.md | 3 +-
.../public/skills/conductor-setup/SKILL.md | 3 +-
.../skills/conductor-validator/SKILL.md | 3 +-
.../public/skills/content-marketer/SKILL.md | 3 +-
.../context-driven-development/SKILL.md | 3 +-
.../public/skills/context-manager/SKILL.md | 3 +-
web-app/public/skills/copywriting/SKILL.md | 2 +-
web-app/public/skills/cpp-pro/SKILL.md | 3 +-
.../public/skills/crypto-bd-agent/SKILL.md | 2 +-
web-app/public/skills/csharp-pro/SKILL.md | 3 +-
.../public/skills/customer-support/SKILL.md | 3 +-
.../skills/customs-trade-compliance/SKILL.md | 255 +
.../references/communication-templates.md | 631 +++
.../references/decision-frameworks.md | 764 +++
.../references/edge-cases.md | 362 ++
web-app/public/skills/data-engineer/SKILL.md | 3 +-
web-app/public/skills/data-scientist/SKILL.md | 3 +-
web-app/public/skills/database-admin/SKILL.md | 3 +-
.../public/skills/database-architect/SKILL.md | 3 +-
.../public/skills/database-optimizer/SKILL.md | 3 +-
web-app/public/skills/debugger/SKILL.md | 3 +-
.../skills/deployment-engineer/SKILL.md | 3 +-
.../skills/devops-troubleshooter/SKILL.md | 3 +-
web-app/public/skills/django-pro/SKILL.md | 3 +-
web-app/public/skills/docs-architect/SKILL.md | 3 +-
.../public/skills/dotnet-architect/SKILL.md | 3 +-
web-app/public/skills/dx-optimizer/SKILL.md | 3 +-
web-app/public/skills/elixir-pro/SKILL.md | 3 +-
.../public/skills/energy-procurement/SKILL.md | 218 +
.../references/communication-templates.md | 492 ++
.../references/decision-frameworks.md | 851 ++++
.../references/edge-cases.md | 624 +++
.../public/skills/error-detective/SKILL.md | 3 +-
web-app/public/skills/fastapi-pro/SKILL.md | 3 +-
.../public/skills/firmware-analyst/SKILL.md | 3 +-
web-app/public/skills/flutter-expert/SKILL.md | 3 +-
web-app/public/skills/form-cro/SKILL.md | 2 +-
.../public/skills/frontend-developer/SKILL.md | 3 +-
.../skills/frontend-security-coder/SKILL.md | 3 +-
web-app/public/skills/golang-pro/SKILL.md | 3 +-
.../public/skills/graphql-architect/SKILL.md | 3 +-
web-app/public/skills/grpc-golang/SKILL.md | 103 +
.../resources/implementation-playbook.md | 548 ++
.../skills/hig-components-content/SKILL.md | 2 +-
.../skills/hig-components-controls/SKILL.md | 2 +-
.../skills/hig-components-dialogs/SKILL.md | 2 +-
.../skills/hig-components-layout/SKILL.md | 2 +-
.../skills/hig-components-menus/SKILL.md | 2 +-
.../skills/hig-components-search/SKILL.md | 2 +-
.../skills/hig-components-status/SKILL.md | 2 +-
.../skills/hig-components-system/SKILL.md | 2 +-
.../public/skills/hig-foundations/SKILL.md | 2 +-
web-app/public/skills/hig-inputs/SKILL.md | 2 +-
web-app/public/skills/hig-patterns/SKILL.md | 2 +-
web-app/public/skills/hig-platforms/SKILL.md | 2 +-
.../skills/hig-project-context/SKILL.md | 2 +-
.../public/skills/hig-technologies/SKILL.md | 2 +-
web-app/public/skills/hr-pro/SKILL.md | 3 +-
.../skills/hybrid-cloud-architect/SKILL.md | 3 +-
web-app/public/skills/imagen/SKILL.md | 2 +-
.../public/skills/incident-responder/SKILL.md | 3 +-
.../skills/inventory-demand-planning/SKILL.md | 239 +
.../references/communication-templates.md | 566 +++
.../references/decision-frameworks.md | 861 ++++
.../references/edge-cases.md | 602 +++
web-app/public/skills/ios-developer/SKILL.md | 3 +-
web-app/public/skills/java-pro/SKILL.md | 3 +-
web-app/public/skills/javascript-pro/SKILL.md | 3 +-
web-app/public/skills/julia-pro/SKILL.md | 3 +-
.../skills/kubernetes-architect/SKILL.md | 3 +-
.../public/skills/legacy-modernizer/SKILL.md | 3 +-
web-app/public/skills/legal-advisor/SKILL.md | 3 +-
web-app/public/skills/linkedin-cli/SKILL.md | 536 ++
.../logistics-exception-management/SKILL.md | 217 +
.../references/communication-templates.md | 1170 +++++
.../references/decision-frameworks.md | 1460 ++++++
.../references/edge-cases.md | 734 +++
.../public/skills/m365-agents-dotnet/SKILL.md | 2 +-
web-app/public/skills/m365-agents-py/SKILL.md | 2 +-
web-app/public/skills/m365-agents-ts/SKILL.md | 2 +-
.../public/skills/malware-analyst/SKILL.md | 3 +-
.../skills/market-sizing-analysis/SKILL.md | 3 +-
web-app/public/skills/mermaid-expert/SKILL.md | 3 +-
.../SKILL.md | 2 +-
.../skills/minecraft-bukkit-pro/SKILL.md | 3 +-
web-app/public/skills/ml-engineer/SKILL.md | 3 +-
web-app/public/skills/mlops-engineer/SKILL.md | 3 +-
.../public/skills/mobile-developer/SKILL.md | 3 +-
.../skills/mobile-security-coder/SKILL.md | 3 +-
.../public/skills/network-engineer/SKILL.md | 3 +-
.../skills/observability-engineer/SKILL.md | 3 +-
web-app/public/skills/page-cro/SKILL.md | 2 +-
.../skills/payment-integration/SKILL.md | 3 +-
web-app/public/skills/php-pro/SKILL.md | 3 +-
.../public/skills/posix-shell-pro/SKILL.md | 3 +-
.../skills/production-scheduling/SKILL.md | 229 +
.../references/communication-templates.md | 503 ++
.../references/decision-frameworks.md | 867 ++++
.../references/edge-cases.md | 611 +++
.../public/skills/programmatic-seo/SKILL.md | 2 +-
web-app/public/skills/python-pro/SKILL.md | 3 +-
.../skills/quality-nonconformance/SKILL.md | 250 +
.../references/communication-templates.md | 711 +++
.../references/decision-frameworks.md | 769 +++
.../references/edge-cases.md | 588 +++
web-app/public/skills/quant-analyst/SKILL.md | 3 +-
.../public/skills/reference-builder/SKILL.md | 3 +-
.../skills/returns-reverse-logistics/SKILL.md | 231 +
.../references/communication-templates.md | 532 ++
.../references/decision-frameworks.md | 823 +++
.../references/edge-cases.md | 635 +++
.../public/skills/reverse-engineer/SKILL.md | 3 +-
web-app/public/skills/risk-manager/SKILL.md | 3 +-
web-app/public/skills/ruby-pro/SKILL.md | 3 +-
web-app/public/skills/rust-pro/SKILL.md | 3 +-
.../public/skills/sales-automator/SKILL.md | 3 +-
web-app/public/skills/scala-pro/SKILL.md | 3 +-
web-app/public/skills/schema-markup/SKILL.md | 2 +-
.../public/skills/security-auditor/SKILL.md | 3 +-
.../security-scanning-security-sast/SKILL.md | 3 +-
web-app/public/skills/seo-audit/SKILL.md | 2 +-
.../skills/seo-authority-builder/SKILL.md | 3 +-
.../seo-cannibalization-detector/SKILL.md | 3 +-
.../skills/seo-content-auditor/SKILL.md | 3 +-
.../skills/seo-content-planner/SKILL.md | 3 +-
.../skills/seo-content-refresher/SKILL.md | 3 +-
.../public/skills/seo-content-writer/SKILL.md | 3 +-
.../public/skills/seo-fundamentals/SKILL.md | 2 +-
.../skills/seo-keyword-strategist/SKILL.md | 3 +-
.../public/skills/seo-meta-optimizer/SKILL.md | 3 +-
.../public/skills/seo-snippet-hunter/SKILL.md | 3 +-
.../skills/seo-structure-architect/SKILL.md | 3 +-
web-app/public/skills/sql-pro/SKILL.md | 3 +-
.../public/skills/startup-analyst/SKILL.md | 3 +-
.../SKILL.md | 3 +-
.../SKILL.md | 3 +-
.../SKILL.md | 3 +-
.../startup-financial-modeling/SKILL.md | 3 +-
.../skills/startup-metrics-framework/SKILL.md | 3 +-
.../public/skills/tdd-orchestrator/SKILL.md | 3 +-
.../skills/team-composition-analysis/SKILL.md | 3 +-
.../skills/temporal-python-pro/SKILL.md | 3 +-
.../skills/terraform-specialist/SKILL.md | 3 +-
web-app/public/skills/test-automator/SKILL.md | 3 +-
.../public/skills/track-management/SKILL.md | 3 +-
.../public/skills/tutorial-engineer/SKILL.md | 3 +-
.../public/skills/typescript-expert/SKILL.md | 2 +-
web-app/public/skills/typescript-pro/SKILL.md | 3 +-
web-app/public/skills/ui-ux-designer/SKILL.md | 3 +-
.../skills/ui-visual-validator/SKILL.md | 3 +-
.../public/skills/unity-developer/SKILL.md | 3 +-
.../public/skills/workflow-patterns/SKILL.md | 3 +-
265 files changed, 25535 insertions(+), 4503 deletions(-)
create mode 100644 SKILLS_UPDATE_GUIDE.md
create mode 100644 web-app/public/skills/00-andruia-consultant/SKILL.md
create mode 100644 web-app/public/skills/10-andruia-skill-smith/SKILL.MD
create mode 100644 web-app/public/skills/20-andruia-niche-intelligence/SKILL.md
create mode 100644 web-app/public/skills/agentfolio/SKILL.md
create mode 100644 web-app/public/skills/appdeploy/SKILL.md
create mode 100644 web-app/public/skills/carrier-relationship-management/SKILL.md
create mode 100644 web-app/public/skills/carrier-relationship-management/references/communication-templates.md
create mode 100644 web-app/public/skills/carrier-relationship-management/references/decision-frameworks.md
create mode 100644 web-app/public/skills/carrier-relationship-management/references/edge-cases.md
create mode 100644 web-app/public/skills/chrome-extension-developer/SKILL.md
create mode 100644 web-app/public/skills/cloudflare-workers-expert/SKILL.md
create mode 100644 web-app/public/skills/customs-trade-compliance/SKILL.md
create mode 100644 web-app/public/skills/customs-trade-compliance/references/communication-templates.md
create mode 100644 web-app/public/skills/customs-trade-compliance/references/decision-frameworks.md
create mode 100644 web-app/public/skills/customs-trade-compliance/references/edge-cases.md
create mode 100644 web-app/public/skills/energy-procurement/SKILL.md
create mode 100644 web-app/public/skills/energy-procurement/references/communication-templates.md
create mode 100644 web-app/public/skills/energy-procurement/references/decision-frameworks.md
create mode 100644 web-app/public/skills/energy-procurement/references/edge-cases.md
create mode 100644 web-app/public/skills/grpc-golang/SKILL.md
create mode 100644 web-app/public/skills/grpc-golang/resources/implementation-playbook.md
create mode 100644 web-app/public/skills/inventory-demand-planning/SKILL.md
create mode 100644 web-app/public/skills/inventory-demand-planning/references/communication-templates.md
create mode 100644 web-app/public/skills/inventory-demand-planning/references/decision-frameworks.md
create mode 100644 web-app/public/skills/inventory-demand-planning/references/edge-cases.md
create mode 100644 web-app/public/skills/linkedin-cli/SKILL.md
create mode 100644 web-app/public/skills/logistics-exception-management/SKILL.md
create mode 100644 web-app/public/skills/logistics-exception-management/references/communication-templates.md
create mode 100644 web-app/public/skills/logistics-exception-management/references/decision-frameworks.md
create mode 100644 web-app/public/skills/logistics-exception-management/references/edge-cases.md
create mode 100644 web-app/public/skills/production-scheduling/SKILL.md
create mode 100644 web-app/public/skills/production-scheduling/references/communication-templates.md
create mode 100644 web-app/public/skills/production-scheduling/references/decision-frameworks.md
create mode 100644 web-app/public/skills/production-scheduling/references/edge-cases.md
create mode 100644 web-app/public/skills/quality-nonconformance/SKILL.md
create mode 100644 web-app/public/skills/quality-nonconformance/references/communication-templates.md
create mode 100644 web-app/public/skills/quality-nonconformance/references/decision-frameworks.md
create mode 100644 web-app/public/skills/quality-nonconformance/references/edge-cases.md
create mode 100644 web-app/public/skills/returns-reverse-logistics/SKILL.md
create mode 100644 web-app/public/skills/returns-reverse-logistics/references/communication-templates.md
create mode 100644 web-app/public/skills/returns-reverse-logistics/references/decision-frameworks.md
create mode 100644 web-app/public/skills/returns-reverse-logistics/references/edge-cases.md
diff --git a/SKILLS_UPDATE_GUIDE.md b/SKILLS_UPDATE_GUIDE.md
new file mode 100644
index 00000000..130925d6
--- /dev/null
+++ b/SKILLS_UPDATE_GUIDE.md
@@ -0,0 +1,89 @@
+# Skills Update Guide
+
+This guide explains how to update the skills in the Antigravity Awesome Skills web application.
+
+## Automatic Updates (Recommended)
+
+The `START_APP.bat` file automatically checks for and updates skills when you run it. It uses multiple methods:
+
+1. **Git method** (if Git is installed): Fast and efficient
+2. **PowerShell download** (fallback): Works without Git
+
+## Manual Update Options
+
+### Option 1: Using npm script (Recommended for manual updates)
+```bash
+npm run update:skills
+```
+
+This command:
+- Generates the latest skills index from the skills directory
+- Copies it to the web app's public directory
+- Requires Python and PyYAML to be installed
+
+### Option 2: Using START_APP.bat (Integrated solution)
+```bash
+START_APP.bat
+```
+
+The START_APP.bat file includes integrated update functionality that:
+- Automatically checks for updates on startup
+- Uses Git if available (fast method)
+- Falls back to HTTPS download if Git is not installed
+- Handles all dependencies automatically
+- Provides clear status messages
+- Works without any additional setup
+
+### Option 3: Manual steps
+```bash
+# 1. Generate skills index
+python scripts/generate_index.py
+
+# 2. Copy to web app
+copy skills_index.json web-app\public\skills.json
+```
+
+## Prerequisites
+
+For manual updates, you need:
+
+- **Python 3.x**: Download from [python.org](https://python.org/)
+- **PyYAML**: Install with `pip install PyYAML`
+
+## Troubleshooting
+
+### "Python is not recognized"
+- Install Python from [python.org](https://python.org/)
+- Make sure to check "Add Python to PATH" during installation
+
+### "PyYAML not found"
+- Install with: `pip install PyYAML`
+- Or run the update script which will install it automatically
+
+### "Failed to copy skills"
+- Make sure the `web-app\public\` directory exists
+- Check file permissions
+
+## What Gets Updated
+
+The update process refreshes:
+- Skills index (`skills_index.json`)
+- Web app skills data (`web-app\public\skills.json`)
+- All 900+ skills from the skills directory
+
+## When to Update
+
+Update skills when:
+- New skills are added to the repository
+- You want the latest skill descriptions
+- Skills appear missing or outdated in the web app
+
+## Git Users
+
+If you have Git installed and want to update the entire repository:
+```bash
+git pull origin main
+npm run update:skills
+```
+
+This pulls the latest code and updates the skills data.
\ No newline at end of file
diff --git a/START_APP.bat b/START_APP.bat
index b8934b8a..5555ab67 100644
--- a/START_APP.bat
+++ b/START_APP.bat
@@ -15,15 +15,17 @@ IF %ERRORLEVEL% NEQ 0 (
)
:: ===== Auto-Update Skills from GitHub =====
+echo [INFO] Checking for skill updates...
+
+:: Method 1: Try Git first (if available)
WHERE git >nul 2>nul
-IF %ERRORLEVEL% NEQ 0 goto :NO_GIT
-goto :HAS_GIT
+IF %ERRORLEVEL% EQU 0 goto :USE_GIT
-:NO_GIT
-echo [WARN] Git is not installed. Skipping auto-update.
-goto :SKIP_UPDATE
+:: Method 2: Try PowerShell download (fallback)
+echo [INFO] Git not found. Using alternative download method...
+goto :USE_POWERSHELL
-:HAS_GIT
+:USE_GIT
:: Add upstream remote if not already set
git remote get-url upstream >nul 2>nul
IF %ERRORLEVEL% EQU 0 goto :DO_FETCH
@@ -31,23 +33,69 @@ echo [INFO] Adding upstream remote...
git remote add upstream https://github.com/sickn33/antigravity-awesome-skills.git
:DO_FETCH
-echo [INFO] Checking for skill updates from original repo...
+echo [INFO] Fetching latest skills from original repo...
git fetch upstream >nul 2>nul
IF %ERRORLEVEL% NEQ 0 goto :FETCH_FAIL
goto :DO_MERGE
:FETCH_FAIL
-echo [WARN] Could not fetch updates. Continuing with local version...
-goto :SKIP_UPDATE
+echo [WARN] Could not fetch updates via Git. Trying alternative method...
+goto :USE_POWERSHELL
:DO_MERGE
-git merge upstream/main --ff-only >nul 2>nul
+:: Surgically extract ONLY the /skills/ folder from upstream to avoid all merge conflicts
+git checkout upstream/main -- skills >nul 2>nul
IF %ERRORLEVEL% NEQ 0 goto :MERGE_FAIL
+
+:: Save the updated skills to local history silently
+git commit -m "auto-update: sync latest skills from upstream" >nul 2>nul
echo [INFO] Skills updated successfully from original repo!
goto :SKIP_UPDATE
:MERGE_FAIL
-echo [WARN] Could not merge updates. Continuing with local version...
+echo [WARN] Could not update skills via Git. Trying alternative method...
+goto :USE_POWERSHELL
+
+:USE_POWERSHELL
+echo [INFO] Downloading latest skills via HTTPS...
+if exist "update_temp" rmdir /S /Q "update_temp" >nul 2>nul
+if exist "update.zip" del "update.zip" >nul 2>nul
+
+:: Download the latest repository as ZIP
+powershell -Command "Invoke-WebRequest -Uri 'https://github.com/sickn33/antigravity-awesome-skills/archive/refs/heads/main.zip' -OutFile 'update.zip' -UseBasicParsing" >nul 2>nul
+IF %ERRORLEVEL% NEQ 0 goto :DOWNLOAD_FAIL
+
+:: Extract and update skills
+echo [INFO] Extracting latest skills...
+powershell -Command "Expand-Archive -Path 'update.zip' -DestinationPath 'update_temp' -Force" >nul 2>nul
+IF %ERRORLEVEL% NEQ 0 goto :EXTRACT_FAIL
+
+:: Copy only the skills folder
+if exist "update_temp\antigravity-awesome-skills-main\skills" (
+ echo [INFO] Updating skills directory...
+ xcopy /E /Y /I "update_temp\antigravity-awesome-skills-main\skills" "skills" >nul 2>nul
+ echo [INFO] Skills updated successfully without Git!
+) else (
+ echo [WARN] Could not find skills folder in downloaded archive.
+ goto :UPDATE_FAIL
+)
+
+:: Cleanup
+del "update.zip" >nul 2>nul
+rmdir /S /Q "update_temp" >nul 2>nul
+goto :SKIP_UPDATE
+
+:DOWNLOAD_FAIL
+echo [WARN] Failed to download skills update (network issue or no internet).
+goto :UPDATE_FAIL
+
+:EXTRACT_FAIL
+echo [WARN] Failed to extract downloaded skills archive.
+goto :UPDATE_FAIL
+
+:UPDATE_FAIL
+echo [INFO] Continuing with local skills version...
+echo [INFO] To manually update skills later, run: npm run update:skills
:SKIP_UPDATE
diff --git a/package.json b/package.json
index 8339ec21..9ae3c440 100644
--- a/package.json
+++ b/package.json
@@ -14,6 +14,7 @@
"test": "node scripts/tests/validate_skills_headings.test.js && python3 scripts/tests/test_validate_skills_headings.py && python3 scripts/tests/inspect_microsoft_repo.py && python3 scripts/tests/test_comprehensive_coverage.py",
"sync:microsoft": "python3 scripts/sync_microsoft_skills.py",
"sync:all-official": "npm run sync:microsoft && npm run chain",
+ "update:skills": "python3 scripts/generate_index.py && copy skills_index.json web-app/public/skills.json",
"app:setup": "node scripts/setup_web.js",
"app:install": "cd web-app && npm install",
"app:dev": "npm run app:setup && cd web-app && npm run dev",
diff --git a/skills_index.json b/skills_index.json
index 10357d7e..c0ffd8e0 100644
--- a/skills_index.json
+++ b/skills_index.json
@@ -1,7 +1,25 @@
[
+ {
+ "id": "00-andruia-consultant",
+ "path": "skills\\00-andruia-consultant",
+ "category": "uncategorized",
+ "name": "00-andruia-consultant",
+ "description": "Arquitecto de Soluciones Principal y Consultor Tecnol\u00f3gico de Andru.ia. Diagnostica y traza la hoja de ruta \u00f3ptima para proyectos de IA en espa\u00f1ol.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "20-andruia-niche-intelligence",
+ "path": "skills\\20-andruia-niche-intelligence",
+ "category": "uncategorized",
+ "name": "20-andruia-niche-intelligence",
+ "description": "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho espec\u00edfico de un proyecto para inyectar conocimientos, regulaciones y est\u00e1ndares \u00fanicos del sector. Act\u00edvalo tras definir el nicho.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "2d-games",
- "path": "skills/game-development/2d-games",
+ "path": "skills\\game-development\\2d-games",
"category": "game-development",
"name": "2d-games",
"description": "2D game development principles. Sprites, tilemaps, physics, camera.",
@@ -10,7 +28,7 @@
},
{
"id": "3d-games",
- "path": "skills/game-development/3d-games",
+ "path": "skills\\game-development\\3d-games",
"category": "game-development",
"name": "3d-games",
"description": "3D game development principles. Rendering, shaders, physics, cameras.",
@@ -19,7 +37,7 @@
},
{
"id": "3d-web-experience",
- "path": "skills/3d-web-experience",
+ "path": "skills\\3d-web-experience",
"category": "uncategorized",
"name": "3d-web-experience",
"description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...",
@@ -28,7 +46,7 @@
},
{
"id": "ab-test-setup",
- "path": "skills/ab-test-setup",
+ "path": "skills\\ab-test-setup",
"category": "uncategorized",
"name": "ab-test-setup",
"description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.",
@@ -37,7 +55,7 @@
},
{
"id": "accessibility-compliance-accessibility-audit",
- "path": "skills/accessibility-compliance-accessibility-audit",
+ "path": "skills\\accessibility-compliance-accessibility-audit",
"category": "uncategorized",
"name": "accessibility-compliance-accessibility-audit",
"description": "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.",
@@ -46,7 +64,7 @@
},
{
"id": "active-directory-attacks",
- "path": "skills/active-directory-attacks",
+ "path": "skills\\active-directory-attacks",
"category": "uncategorized",
"name": "active-directory-attacks",
"description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ...",
@@ -55,7 +73,7 @@
},
{
"id": "activecampaign-automation",
- "path": "skills/activecampaign-automation",
+ "path": "skills\\activecampaign-automation",
"category": "uncategorized",
"name": "activecampaign-automation",
"description": "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.",
@@ -64,7 +82,7 @@
},
{
"id": "address-github-comments",
- "path": "skills/address-github-comments",
+ "path": "skills\\address-github-comments",
"category": "uncategorized",
"name": "address-github-comments",
"description": "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.",
@@ -73,7 +91,7 @@
},
{
"id": "agent-evaluation",
- "path": "skills/agent-evaluation",
+ "path": "skills\\agent-evaluation",
"category": "uncategorized",
"name": "agent-evaluation",
"description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re...",
@@ -82,7 +100,7 @@
},
{
"id": "agent-framework-azure-ai-py",
- "path": "skills/agent-framework-azure-ai-py",
+ "path": "skills\\agent-framework-azure-ai-py",
"category": "uncategorized",
"name": "agent-framework-azure-ai-py",
"description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...",
@@ -91,7 +109,7 @@
},
{
"id": "agent-manager-skill",
- "path": "skills/agent-manager-skill",
+ "path": "skills\\agent-manager-skill",
"category": "uncategorized",
"name": "agent-manager-skill",
"description": "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.",
@@ -100,7 +118,7 @@
},
{
"id": "agent-memory-mcp",
- "path": "skills/agent-memory-mcp",
+ "path": "skills\\agent-memory-mcp",
"category": "uncategorized",
"name": "agent-memory-mcp",
"description": "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).",
@@ -109,7 +127,7 @@
},
{
"id": "agent-memory-systems",
- "path": "skills/agent-memory-systems",
+ "path": "skills\\agent-memory-systems",
"category": "uncategorized",
"name": "agent-memory-systems",
"description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...",
@@ -118,7 +136,7 @@
},
{
"id": "agent-orchestration-improve-agent",
- "path": "skills/agent-orchestration-improve-agent",
+ "path": "skills\\agent-orchestration-improve-agent",
"category": "uncategorized",
"name": "agent-orchestration-improve-agent",
"description": "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.",
@@ -127,7 +145,7 @@
},
{
"id": "agent-orchestration-multi-agent-optimize",
- "path": "skills/agent-orchestration-multi-agent-optimize",
+ "path": "skills\\agent-orchestration-multi-agent-optimize",
"category": "uncategorized",
"name": "agent-orchestration-multi-agent-optimize",
"description": "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.",
@@ -136,34 +154,34 @@
},
{
"id": "agent-tool-builder",
- "path": "skills/agent-tool-builder",
+ "path": "skills\\agent-tool-builder",
"category": "uncategorized",
"name": "agent-tool-builder",
"description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "agentfolio",
+ "path": "skills\\agentfolio",
+ "category": "uncategorized",
+ "name": "agentfolio",
+ "description": "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.",
+ "risk": "unknown",
+ "source": "agentfolio.io"
+ },
{
"id": "agents-v2-py",
- "path": "skills/agents-v2-py",
+ "path": "skills\\agents-v2-py",
"category": "uncategorized",
"name": "agents-v2-py",
"description": "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "ai-engineer",
- "path": "skills/ai-engineer",
- "category": "uncategorized",
- "name": "Ai Engineer",
- "description": "You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "ai-agent-development",
- "path": "skills/ai-agent-development",
+ "path": "skills\\ai-agent-development",
"category": "uncategorized",
"name": "ai-agent-development",
"description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
@@ -172,16 +190,25 @@
},
{
"id": "ai-agents-architect",
- "path": "skills/ai-agents-architect",
+ "path": "skills\\ai-agents-architect",
"category": "uncategorized",
"name": "ai-agents-architect",
"description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "ai-engineer",
+ "path": "skills\\ai-engineer",
+ "category": "uncategorized",
+ "name": "ai-engineer",
+ "description": "Build production-ready LLM applications, advanced RAG systems, and\nintelligent agents. Implements vector search, multimodal AI, agent\norchestration, and enterprise AI integrations. Use PROACTIVELY for LLM\nfeatures, chatbots, AI agents, or AI-powered applications.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "ai-ml",
- "path": "skills/ai-ml",
+ "path": "skills\\ai-ml",
"category": "uncategorized",
"name": "ai-ml",
"description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
@@ -190,7 +217,7 @@
},
{
"id": "ai-product",
- "path": "skills/ai-product",
+ "path": "skills\\ai-product",
"category": "uncategorized",
"name": "ai-product",
"description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ...",
@@ -199,7 +226,7 @@
},
{
"id": "ai-wrapper-product",
- "path": "skills/ai-wrapper-product",
+ "path": "skills\\ai-wrapper-product",
"category": "uncategorized",
"name": "ai-wrapper-product",
"description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...",
@@ -208,7 +235,7 @@
},
{
"id": "airflow-dag-patterns",
- "path": "skills/airflow-dag-patterns",
+ "path": "skills\\airflow-dag-patterns",
"category": "uncategorized",
"name": "airflow-dag-patterns",
"description": "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.",
@@ -217,7 +244,7 @@
},
{
"id": "airtable-automation",
- "path": "skills/airtable-automation",
+ "path": "skills\\airtable-automation",
"category": "uncategorized",
"name": "airtable-automation",
"description": "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.",
@@ -226,7 +253,7 @@
},
{
"id": "algolia-search",
- "path": "skills/algolia-search",
+ "path": "skills\\algolia-search",
"category": "uncategorized",
"name": "algolia-search",
"description": "Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.",
@@ -235,7 +262,7 @@
},
{
"id": "algorithmic-art",
- "path": "skills/algorithmic-art",
+ "path": "skills\\algorithmic-art",
"category": "uncategorized",
"name": "algorithmic-art",
"description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,...",
@@ -244,7 +271,7 @@
},
{
"id": "amplitude-automation",
- "path": "skills/amplitude-automation",
+ "path": "skills\\amplitude-automation",
"category": "uncategorized",
"name": "amplitude-automation",
"description": "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.",
@@ -253,16 +280,16 @@
},
{
"id": "analytics-tracking",
- "path": "skills/analytics-tracking",
+ "path": "skills\\analytics-tracking",
"category": "uncategorized",
- "name": "Analytics Tracking",
- "description": "You are an expert in **analytics implementation and measurement design**. Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.",
+ "name": "analytics-tracking",
+ "description": "Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation\u2014 not just firing events.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "android-jetpack-compose-expert",
- "path": "skills/android-jetpack-compose-expert",
+ "path": "skills\\android-jetpack-compose-expert",
"category": "uncategorized",
"name": "android-jetpack-compose-expert",
"description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
@@ -271,16 +298,16 @@
},
{
"id": "angular",
- "path": "skills/angular",
+ "path": "skills\\angular",
"category": "uncategorized",
- "name": "Angular",
- "description": "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration, and the latest reactive patterns.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "angular",
+ "description": "Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "angular-best-practices",
- "path": "skills/angular-best-practices",
+ "path": "skills\\angular-best-practices",
"category": "uncategorized",
"name": "angular-best-practices",
"description": "Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.",
@@ -289,7 +316,7 @@
},
{
"id": "angular-migration",
- "path": "skills/angular-migration",
+ "path": "skills\\angular-migration",
"category": "uncategorized",
"name": "angular-migration",
"description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...",
@@ -298,7 +325,7 @@
},
{
"id": "angular-state-management",
- "path": "skills/angular-state-management",
+ "path": "skills\\angular-state-management",
"category": "uncategorized",
"name": "angular-state-management",
"description": "Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.",
@@ -307,7 +334,7 @@
},
{
"id": "angular-ui-patterns",
- "path": "skills/angular-ui-patterns",
+ "path": "skills\\angular-ui-patterns",
"category": "uncategorized",
"name": "angular-ui-patterns",
"description": "Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.",
@@ -316,7 +343,7 @@
},
{
"id": "anti-reversing-techniques",
- "path": "skills/anti-reversing-techniques",
+ "path": "skills\\anti-reversing-techniques",
"category": "uncategorized",
"name": "anti-reversing-techniques",
"description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...",
@@ -325,25 +352,16 @@
},
{
"id": "antigravity-workflows",
- "path": "skills/antigravity-workflows",
+ "path": "skills\\antigravity-workflows",
"category": "uncategorized",
"name": "antigravity-workflows",
"description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
"risk": "none",
"source": "self"
},
- {
- "id": "api-documenter",
- "path": "skills/api-documenter",
- "category": "uncategorized",
- "name": "Api Documenter",
- "description": "You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "api-design-principles",
- "path": "skills/api-design-principles",
+ "path": "skills\\api-design-principles",
"category": "uncategorized",
"name": "api-design-principles",
"description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...",
@@ -352,7 +370,7 @@
},
{
"id": "api-documentation",
- "path": "skills/api-documentation",
+ "path": "skills\\api-documentation",
"category": "uncategorized",
"name": "api-documentation",
"description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
@@ -361,16 +379,25 @@
},
{
"id": "api-documentation-generator",
- "path": "skills/api-documentation-generator",
+ "path": "skills\\api-documentation-generator",
"category": "uncategorized",
"name": "api-documentation-generator",
"description": "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "api-documenter",
+ "path": "skills\\api-documenter",
+ "category": "uncategorized",
+ "name": "api-documenter",
+ "description": "Master API documentation with OpenAPI 3.1, AI-powered tools, and\nmodern developer experience practices. Create interactive docs, generate SDKs,\nand build comprehensive developer portals. Use PROACTIVELY for API\ndocumentation or developer portal creation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "api-fuzzing-bug-bounty",
- "path": "skills/api-fuzzing-bug-bounty",
+ "path": "skills\\api-fuzzing-bug-bounty",
"category": "uncategorized",
"name": "api-fuzzing-bug-bounty",
"description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b...",
@@ -379,7 +406,7 @@
},
{
"id": "api-patterns",
- "path": "skills/api-patterns",
+ "path": "skills\\api-patterns",
"category": "uncategorized",
"name": "api-patterns",
"description": "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.",
@@ -388,7 +415,7 @@
},
{
"id": "api-security-best-practices",
- "path": "skills/api-security-best-practices",
+ "path": "skills\\api-security-best-practices",
"category": "uncategorized",
"name": "api-security-best-practices",
"description": "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities",
@@ -397,7 +424,7 @@
},
{
"id": "api-security-testing",
- "path": "skills/api-security-testing",
+ "path": "skills\\api-security-testing",
"category": "uncategorized",
"name": "api-security-testing",
"description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
@@ -406,7 +433,7 @@
},
{
"id": "api-testing-observability-api-mock",
- "path": "skills/api-testing-observability-api-mock",
+ "path": "skills\\api-testing-observability-api-mock",
"category": "uncategorized",
"name": "api-testing-observability-api-mock",
"description": "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.",
@@ -415,7 +442,7 @@
},
{
"id": "app-builder",
- "path": "skills/app-builder",
+ "path": "skills\\app-builder",
"category": "uncategorized",
"name": "app-builder",
"description": "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.",
@@ -424,16 +451,25 @@
},
{
"id": "app-store-optimization",
- "path": "skills/app-store-optimization",
+ "path": "skills\\app-store-optimization",
"category": "uncategorized",
"name": "app-store-optimization",
"description": "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "appdeploy",
+ "path": "skills\\appdeploy",
+ "category": "uncategorized",
+ "name": "appdeploy",
+ "description": "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.",
+ "risk": "safe",
+ "source": "AppDeploy (MIT)"
+ },
{
"id": "application-performance-performance-optimization",
- "path": "skills/application-performance-performance-optimization",
+ "path": "skills\\application-performance-performance-optimization",
"category": "uncategorized",
"name": "application-performance-performance-optimization",
"description": "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.",
@@ -442,7 +478,7 @@
},
{
"id": "architect-review",
- "path": "skills/architect-review",
+ "path": "skills\\architect-review",
"category": "uncategorized",
"name": "architect-review",
"description": "Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.",
@@ -451,7 +487,7 @@
},
{
"id": "architecture",
- "path": "skills/architecture",
+ "path": "skills\\architecture",
"category": "uncategorized",
"name": "architecture",
"description": "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.",
@@ -460,7 +496,7 @@
},
{
"id": "architecture-decision-records",
- "path": "skills/architecture-decision-records",
+ "path": "skills\\architecture-decision-records",
"category": "uncategorized",
"name": "architecture-decision-records",
"description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...",
@@ -469,7 +505,7 @@
},
{
"id": "architecture-patterns",
- "path": "skills/architecture-patterns",
+ "path": "skills\\architecture-patterns",
"category": "uncategorized",
"name": "architecture-patterns",
"description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...",
@@ -478,16 +514,16 @@
},
{
"id": "arm-cortex-expert",
- "path": "skills/arm-cortex-expert",
+ "path": "skills\\arm-cortex-expert",
"category": "uncategorized",
- "name": "Arm Cortex Expert",
- "description": "- Working on @arm-cortex-expert tasks or workflows - Needing guidance, best practices, or checklists for @arm-cortex-expert",
+ "name": "arm-cortex-expert",
+ "description": "Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "asana-automation",
- "path": "skills/asana-automation",
+ "path": "skills\\asana-automation",
"category": "uncategorized",
"name": "asana-automation",
"description": "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.",
@@ -496,7 +532,7 @@
},
{
"id": "async-python-patterns",
- "path": "skills/async-python-patterns",
+ "path": "skills\\async-python-patterns",
"category": "uncategorized",
"name": "async-python-patterns",
"description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-...",
@@ -505,7 +541,7 @@
},
{
"id": "attack-tree-construction",
- "path": "skills/attack-tree-construction",
+ "path": "skills\\attack-tree-construction",
"category": "uncategorized",
"name": "attack-tree-construction",
"description": "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.",
@@ -514,7 +550,7 @@
},
{
"id": "audio-transcriber",
- "path": "skills/audio-transcriber",
+ "path": "skills\\audio-transcriber",
"category": "uncategorized",
"name": "audio-transcriber",
"description": "Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration",
@@ -523,7 +559,7 @@
},
{
"id": "auth-implementation-patterns",
- "path": "skills/auth-implementation-patterns",
+ "path": "skills\\auth-implementation-patterns",
"category": "uncategorized",
"name": "auth-implementation-patterns",
"description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A...",
@@ -532,7 +568,7 @@
},
{
"id": "automate-whatsapp",
- "path": "skills/automate-whatsapp",
+ "path": "skills\\automate-whatsapp",
"category": "uncategorized",
"name": "automate-whatsapp",
"description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...",
@@ -541,7 +577,7 @@
},
{
"id": "autonomous-agent-patterns",
- "path": "skills/autonomous-agent-patterns",
+ "path": "skills\\autonomous-agent-patterns",
"category": "uncategorized",
"name": "autonomous-agent-patterns",
"description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...",
@@ -550,7 +586,7 @@
},
{
"id": "autonomous-agents",
- "path": "skills/autonomous-agents",
+ "path": "skills\\autonomous-agents",
"category": "uncategorized",
"name": "autonomous-agents",
"description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'...",
@@ -559,7 +595,7 @@
},
{
"id": "avalonia-layout-zafiro",
- "path": "skills/avalonia-layout-zafiro",
+ "path": "skills\\avalonia-layout-zafiro",
"category": "uncategorized",
"name": "avalonia-layout-zafiro",
"description": "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.",
@@ -568,7 +604,7 @@
},
{
"id": "avalonia-viewmodels-zafiro",
- "path": "skills/avalonia-viewmodels-zafiro",
+ "path": "skills\\avalonia-viewmodels-zafiro",
"category": "uncategorized",
"name": "avalonia-viewmodels-zafiro",
"description": "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.",
@@ -577,7 +613,7 @@
},
{
"id": "avalonia-zafiro-development",
- "path": "skills/avalonia-zafiro-development",
+ "path": "skills\\avalonia-zafiro-development",
"category": "uncategorized",
"name": "avalonia-zafiro-development",
"description": "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.",
@@ -586,7 +622,7 @@
},
{
"id": "aws-compliance-checker",
- "path": "skills/security/aws-compliance-checker",
+ "path": "skills\\security\\aws-compliance-checker",
"category": "security",
"name": "aws-compliance-checker",
"description": "Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks",
@@ -595,7 +631,7 @@
},
{
"id": "aws-cost-cleanup",
- "path": "skills/aws-cost-cleanup",
+ "path": "skills\\aws-cost-cleanup",
"category": "uncategorized",
"name": "aws-cost-cleanup",
"description": "Automated cleanup of unused AWS resources to reduce costs",
@@ -604,7 +640,7 @@
},
{
"id": "aws-cost-optimizer",
- "path": "skills/aws-cost-optimizer",
+ "path": "skills\\aws-cost-optimizer",
"category": "uncategorized",
"name": "aws-cost-optimizer",
"description": "Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer",
@@ -613,7 +649,7 @@
},
{
"id": "aws-iam-best-practices",
- "path": "skills/security/aws-iam-best-practices",
+ "path": "skills\\security\\aws-iam-best-practices",
"category": "security",
"name": "aws-iam-best-practices",
"description": "IAM policy review, hardening, and least privilege implementation",
@@ -622,7 +658,7 @@
},
{
"id": "aws-penetration-testing",
- "path": "skills/aws-penetration-testing",
+ "path": "skills\\aws-penetration-testing",
"category": "uncategorized",
"name": "aws-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing...",
@@ -631,7 +667,7 @@
},
{
"id": "aws-secrets-rotation",
- "path": "skills/security/aws-secrets-rotation",
+ "path": "skills\\security\\aws-secrets-rotation",
"category": "security",
"name": "aws-secrets-rotation",
"description": "Automate AWS secrets rotation for RDS, API keys, and credentials",
@@ -640,7 +676,7 @@
},
{
"id": "aws-security-audit",
- "path": "skills/security/aws-security-audit",
+ "path": "skills\\security\\aws-security-audit",
"category": "security",
"name": "aws-security-audit",
"description": "Comprehensive AWS security posture assessment using AWS CLI and security best practices",
@@ -649,7 +685,7 @@
},
{
"id": "aws-serverless",
- "path": "skills/aws-serverless",
+ "path": "skills\\aws-serverless",
"category": "uncategorized",
"name": "aws-serverless",
"description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt...",
@@ -658,7 +694,7 @@
},
{
"id": "aws-skills",
- "path": "skills/aws-skills",
+ "path": "skills\\aws-skills",
"category": "uncategorized",
"name": "aws-skills",
"description": "AWS development with infrastructure automation and cloud architecture patterns",
@@ -667,7 +703,7 @@
},
{
"id": "azd-deployment",
- "path": "skills/azd-deployment",
+ "path": "skills\\azd-deployment",
"category": "uncategorized",
"name": "azd-deployment",
"description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont...",
@@ -676,727 +712,25 @@
},
{
"id": "azure-ai-agents-persistent-dotnet",
- "path": "skills/azure-ai-agents-persistent-dotnet",
+ "path": "skills\\azure-ai-agents-persistent-dotnet",
"category": "uncategorized",
- "name": "Azure Ai Agents Persistent Dotnet",
- "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
+ "name": "azure-ai-agents-persistent-dotnet",
+ "description": "Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: \"PersistentAgentsClient\", \"persistent agents\", \"agent threads\", \"agent runs\", \"streaming agents\", \"function calling agents .NET\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-agents-persistent-java",
- "path": "skills/azure-ai-agents-persistent-java",
+ "path": "skills\\azure-ai-agents-persistent-java",
"category": "uncategorized",
- "name": "Azure Ai Agents Persistent Java",
- "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
+ "name": "azure-ai-agents-persistent-java",
+ "description": "Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.\nTriggers: \"PersistentAgentsClient\", \"persistent agents java\", \"agent threads java\", \"agent runs java\", \"streaming agents java\".\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentsafety-py",
- "path": "skills/azure-ai-contentsafety-py",
- "category": "uncategorized",
- "name": "Azure Ai Contentsafety Py",
- "description": "Detect harmful user-generated and AI-generated content in applications.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentunderstanding-py",
- "path": "skills/azure-ai-contentunderstanding-py",
- "category": "uncategorized",
- "name": "Azure Ai Contentunderstanding Py",
- "description": "Multimodal AI service that extracts semantic content from documents, video, audio, and image files for RAG and automated workflows.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-document-intelligence-dotnet",
- "path": "skills/azure-ai-document-intelligence-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Document Intelligence Dotnet",
- "description": "Extract text, tables, and structured data from documents using prebuilt and custom models.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-ml-py",
- "path": "skills/azure-ai-ml-py",
- "category": "uncategorized",
- "name": "Azure Ai Ml Py",
- "description": "Client library for managing Azure ML resources: workspaces, jobs, models, data, and compute.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-openai-dotnet",
- "path": "skills/azure-ai-openai-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Openai Dotnet",
- "description": "Client library for Azure OpenAI Service providing access to OpenAI models including GPT-4, GPT-4o, embeddings, DALL-E, and Whisper.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-dotnet",
- "path": "skills/azure-ai-projects-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Projects Dotnet",
- "description": "High-level SDK for Azure AI Foundry project operations including agents, connections, datasets, deployments, evaluations, and indexes.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-java",
- "path": "skills/azure-ai-projects-java",
- "category": "uncategorized",
- "name": "Azure Ai Projects Java",
- "description": "High-level SDK for Azure AI Foundry project management with access to connections, datasets, indexes, and evaluations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-textanalytics-py",
- "path": "skills/azure-ai-textanalytics-py",
- "category": "uncategorized",
- "name": "Azure Ai Textanalytics Py",
- "description": "Client library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-transcription-py",
- "path": "skills/azure-ai-transcription-py",
- "category": "uncategorized",
- "name": "Azure Ai Transcription Py",
- "description": "Client library for Azure AI Transcription (speech-to-text) with real-time and batch transcription.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-document-py",
- "path": "skills/azure-ai-translation-document-py",
- "category": "uncategorized",
- "name": "Azure Ai Translation Document Py",
- "description": "Client library for Azure AI Translator document translation service for batch document translation with format preservation.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-text-py",
- "path": "skills/azure-ai-translation-text-py",
- "category": "uncategorized",
- "name": "Azure Ai Translation Text Py",
- "description": "Client library for Azure AI Translator text translation service for real-time text translation, transliteration, and language operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-vision-imageanalysis-py",
- "path": "skills/azure-ai-vision-imageanalysis-py",
- "category": "uncategorized",
- "name": "Azure Ai Vision Imageanalysis Py",
- "description": "Client library for Azure AI Vision 4.0 image analysis including captions, tags, objects, OCR, and more.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-dotnet",
- "path": "skills/azure-ai-voicelive-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Dotnet",
- "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-java",
- "path": "skills/azure-ai-voicelive-java",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Java",
- "description": "Real-time, bidirectional voice conversations with AI assistants using WebSocket technology.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-ts",
- "path": "skills/azure-ai-voicelive-ts",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Ts",
- "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI in Node.js and browser environments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-java",
- "path": "skills/azure-appconfiguration-java",
- "category": "uncategorized",
- "name": "Azure Appconfiguration Java",
- "description": "Client library for Azure App Configuration, a managed service for centralizing application configurations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-py",
- "path": "skills/azure-appconfiguration-py",
- "category": "uncategorized",
- "name": "Azure Appconfiguration Py",
- "description": "Centralized configuration management with feature flags and dynamic settings.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-compute-batch-java",
- "path": "skills/azure-compute-batch-java",
- "category": "uncategorized",
- "name": "Azure Compute Batch Java",
- "description": "Client library for running large-scale parallel and high-performance computing (HPC) batch jobs in Azure.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-containerregistry-py",
- "path": "skills/azure-containerregistry-py",
- "category": "uncategorized",
- "name": "Azure Containerregistry Py",
- "description": "Manage container images, artifacts, and repositories in Azure Container Registry.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-java",
- "path": "skills/azure-cosmos-java",
- "category": "uncategorized",
- "name": "Azure Cosmos Java",
- "description": "Client library for Azure Cosmos DB NoSQL API with global distribution and reactive patterns.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-py",
- "path": "skills/azure-cosmos-py",
- "category": "uncategorized",
- "name": "Azure Cosmos Py",
- "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-rust",
- "path": "skills/azure-cosmos-rust",
- "category": "uncategorized",
- "name": "Azure Cosmos Rust",
- "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-ts",
- "path": "skills/azure-cosmos-ts",
- "category": "uncategorized",
- "name": "Azure Cosmos Ts",
- "description": "Data plane SDK for Azure Cosmos DB NoSQL API operations \u2014 CRUD on documents, queries, bulk operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-data-tables-py",
- "path": "skills/azure-data-tables-py",
- "category": "uncategorized",
- "name": "Azure Data Tables Py",
- "description": "NoSQL key-value store for structured data (Azure Storage Tables or Cosmos DB Table API).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-dotnet",
- "path": "skills/azure-eventgrid-dotnet",
- "category": "uncategorized",
- "name": "Azure Eventgrid Dotnet",
- "description": "Client library for publishing events to Azure Event Grid topics, domains, and namespaces.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-py",
- "path": "skills/azure-eventgrid-py",
- "category": "uncategorized",
- "name": "Azure Eventgrid Py",
- "description": "Event routing service for building event-driven applications with pub/sub semantics.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-dotnet",
- "path": "skills/azure-eventhub-dotnet",
- "category": "uncategorized",
- "name": "Azure Eventhub Dotnet",
- "description": "High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-py",
- "path": "skills/azure-eventhub-py",
- "category": "uncategorized",
- "name": "Azure Eventhub Py",
- "description": "Big data streaming platform for high-throughput event ingestion.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-rust",
- "path": "skills/azure-eventhub-rust",
- "category": "uncategorized",
- "name": "Azure Eventhub Rust",
- "description": "Client library for Azure Event Hubs \u2014 big data streaming platform and event ingestion service.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-dotnet",
- "path": "skills/azure-identity-dotnet",
- "category": "uncategorized",
- "name": "Azure Identity Dotnet",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-py",
- "path": "skills/azure-identity-py",
- "category": "uncategorized",
- "name": "Azure Identity Py",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-rust",
- "path": "skills/azure-identity-rust",
- "category": "uncategorized",
- "name": "Azure Identity Rust",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-certificates-rust",
- "path": "skills/azure-keyvault-certificates-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Certificates Rust",
- "description": "Client library for Azure Key Vault Certificates \u2014 secure storage and management of certificates.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-keys-rust",
- "path": "skills/azure-keyvault-keys-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Keys Rust",
- "description": "Client library for Azure Key Vault Keys \u2014 secure storage and management of cryptographic keys.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-py",
- "path": "skills/azure-keyvault-py",
- "category": "uncategorized",
- "name": "Azure Keyvault Py",
- "description": "Secure storage and management for secrets, cryptographic keys, and certificates.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-secrets-rust",
- "path": "skills/azure-keyvault-secrets-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Secrets Rust",
- "description": "Client library for Azure Key Vault Secrets \u2014 secure storage for passwords, API keys, and other secrets.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-maps-search-dotnet",
- "path": "skills/azure-maps-search-dotnet",
- "category": "uncategorized",
- "name": "Azure Maps Search Dotnet",
- "description": "Azure Maps SDK for .NET providing location-based services: geocoding, routing, rendering, geolocation, and weather.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-messaging-webpubsubservice-py",
- "path": "skills/azure-messaging-webpubsubservice-py",
- "category": "uncategorized",
- "name": "Azure Messaging Webpubsubservice Py",
- "description": "Real-time messaging with WebSocket connections at scale.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-dotnet",
- "path": "skills/azure-mgmt-apicenter-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Apicenter Dotnet",
- "description": "Centralized API inventory and governance SDK for managing APIs across your organization.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-py",
- "path": "skills/azure-mgmt-apicenter-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Apicenter Py",
- "description": "Manage API inventory, metadata, and governance in Azure API Center.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-dotnet",
- "path": "skills/azure-mgmt-apimanagement-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Apimanagement Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure API Management resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-py",
- "path": "skills/azure-mgmt-apimanagement-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Apimanagement Py",
- "description": "Manage Azure API Management services, APIs, products, and policies.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-applicationinsights-dotnet",
- "path": "skills/azure-mgmt-applicationinsights-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Applicationinsights Dotnet",
- "description": "Azure Resource Manager SDK for managing Application Insights resources for application performance monitoring.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "path": "skills/azure-mgmt-arizeaiobservabilityeval-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Arizeaiobservabilityeval Dotnet",
- "description": ".NET SDK for managing Arize AI Observability and Evaluation resources on Azure.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-dotnet",
- "path": "skills/azure-mgmt-botservice-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Botservice Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Bot Service resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-py",
- "path": "skills/azure-mgmt-botservice-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Botservice Py",
- "description": "Manage Azure Bot Service resources including bots, channels, and connections.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-dotnet",
- "path": "skills/azure-mgmt-fabric-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Fabric Dotnet",
- "description": "Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-py",
- "path": "skills/azure-mgmt-fabric-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Fabric Py",
- "description": "Manage Microsoft Fabric capacities and resources programmatically.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-weightsandbiases-dotnet",
- "path": "skills/azure-mgmt-weightsandbiases-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Weightsandbiases Dotnet",
- "description": "Azure Resource Manager SDK for deploying and managing Weights & Biases ML experiment tracking instances via Azure Marketplace.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-java",
- "path": "skills/azure-monitor-ingestion-java",
- "category": "uncategorized",
- "name": "Azure Monitor Ingestion Java",
- "description": "Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-py",
- "path": "skills/azure-monitor-ingestion-py",
- "category": "uncategorized",
- "name": "Azure Monitor Ingestion Py",
- "description": "Send custom logs to Azure Monitor Log Analytics workspace using the Logs Ingestion API.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-java",
- "path": "skills/azure-monitor-opentelemetry-exporter-java",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Exporter Java",
- "description": "> **\u26a0\ufe0f DEPRECATION NOTICE**: This package is deprecated. Migrate to `azure-monitor-opentelemetry-autoconfigure`. > > See [Migration Guide](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/MIGRATIO",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-py",
- "path": "skills/azure-monitor-opentelemetry-exporter-py",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Exporter Py",
- "description": "Low-level exporter for sending OpenTelemetry traces, metrics, and logs to Application Insights.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-py",
- "path": "skills/azure-monitor-opentelemetry-py",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Py",
- "description": "One-line setup for Application Insights with OpenTelemetry auto-instrumentation.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-java",
- "path": "skills/azure-monitor-query-java",
- "category": "uncategorized",
- "name": "Azure Monitor Query Java",
- "description": "> **DEPRECATION NOTICE**: This package is deprecated in favor of: > - `azure-monitor-query-logs` \u2014 For Log Analytics queries > - `azure-monitor-query-metrics` \u2014 For metrics queries > > See migration guides: [Logs Migration](https://github.com/Azure/a",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-py",
- "path": "skills/azure-monitor-query-py",
- "category": "uncategorized",
- "name": "Azure Monitor Query Py",
- "description": "Query logs and metrics from Azure Monitor and Log Analytics workspaces.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-postgres-ts",
- "path": "skills/azure-postgres-ts",
- "category": "uncategorized",
- "name": "Azure Postgres Ts",
- "description": "Connect to Azure Database for PostgreSQL Flexible Server using the `pg` (node-postgres) package with support for password and Microsoft Entra ID (passwordless) authentication.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-cosmosdb-dotnet",
- "path": "skills/azure-resource-manager-cosmosdb-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Cosmosdb Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Cosmos DB resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-durabletask-dotnet",
- "path": "skills/azure-resource-manager-durabletask-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Durabletask Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-mysql-dotnet",
- "path": "skills/azure-resource-manager-mysql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Mysql Dotnet",
- "description": "Azure Resource Manager SDK for managing MySQL Flexible Server deployments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-playwright-dotnet",
- "path": "skills/azure-resource-manager-playwright-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Playwright Dotnet",
- "description": "Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-postgresql-dotnet",
- "path": "skills/azure-resource-manager-postgresql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Postgresql Dotnet",
- "description": "Azure Resource Manager SDK for managing PostgreSQL Flexible Server deployments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-redis-dotnet",
- "path": "skills/azure-resource-manager-redis-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Redis Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Cache for Redis resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-sql-dotnet",
- "path": "skills/azure-resource-manager-sql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Sql Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-dotnet",
- "path": "skills/azure-search-documents-dotnet",
- "category": "uncategorized",
- "name": "Azure Search Documents Dotnet",
- "description": "Build search applications with full-text, vector, semantic, and hybrid search capabilities.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-py",
- "path": "skills/azure-search-documents-py",
- "category": "uncategorized",
- "name": "Azure Search Documents Py",
- "description": "Full-text, vector, and hybrid search with AI enrichment capabilities.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-security-keyvault-keys-dotnet",
- "path": "skills/azure-security-keyvault-keys-dotnet",
- "category": "uncategorized",
- "name": "Azure Security Keyvault Keys Dotnet",
- "description": "Client library for managing cryptographic keys in Azure Key Vault and Managed HSM.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-dotnet",
- "path": "skills/azure-servicebus-dotnet",
- "category": "uncategorized",
- "name": "Azure Servicebus Dotnet",
- "description": "Enterprise messaging SDK for reliable message delivery with queues, topics, subscriptions, and sessions.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-py",
- "path": "skills/azure-servicebus-py",
- "category": "uncategorized",
- "name": "Azure Servicebus Py",
- "description": "Enterprise messaging for reliable cloud communication with queues and pub/sub topics.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-speech-to-text-rest-py",
- "path": "skills/azure-speech-to-text-rest-py",
- "category": "uncategorized",
- "name": "Azure Speech To Text Rest Py",
- "description": "Simple REST API for speech-to-text transcription of short audio files (up to 60 seconds). No SDK required - just HTTP requests.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-py",
- "path": "skills/azure-storage-blob-py",
- "category": "uncategorized",
- "name": "Azure Storage Blob Py",
- "description": "Client library for Azure Blob Storage \u2014 object storage for unstructured data.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-rust",
- "path": "skills/azure-storage-blob-rust",
- "category": "uncategorized",
- "name": "Azure Storage Blob Rust",
- "description": "Client library for Azure Blob Storage \u2014 Microsoft's object storage solution for the cloud.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-ts",
- "path": "skills/azure-storage-blob-ts",
- "category": "uncategorized",
- "name": "Azure Storage Blob Ts",
- "description": "SDK for Azure Blob Storage operations \u2014 upload, download, list, and manage blobs and containers.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-datalake-py",
- "path": "skills/azure-storage-file-datalake-py",
- "category": "uncategorized",
- "name": "Azure Storage File Datalake Py",
- "description": "Hierarchical file system for big data analytics workloads.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-py",
- "path": "skills/azure-storage-file-share-py",
- "category": "uncategorized",
- "name": "Azure Storage File Share Py",
- "description": "Manage SMB file shares for cloud-native and lift-and-shift scenarios.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-ts",
- "path": "skills/azure-storage-file-share-ts",
- "category": "uncategorized",
- "name": "Azure Storage File Share Ts",
- "description": "SDK for Azure File Share operations \u2014 SMB file shares, directories, and file operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-py",
- "path": "skills/azure-storage-queue-py",
- "category": "uncategorized",
- "name": "Azure Storage Queue Py",
- "description": "Simple, cost-effective message queuing for asynchronous communication.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-ts",
- "path": "skills/azure-storage-queue-ts",
- "category": "uncategorized",
- "name": "Azure Storage Queue Ts",
- "description": "SDK for Azure Queue Storage operations \u2014 send, receive, peek, and manage messages in queues.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-anomalydetector-java",
- "path": "skills/azure-ai-anomalydetector-java",
+ "path": "skills\\azure-ai-anomalydetector-java",
"category": "uncategorized",
"name": "azure-ai-anomalydetector-java",
"description": "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.",
@@ -1405,25 +739,52 @@
},
{
"id": "azure-ai-contentsafety-java",
- "path": "skills/azure-ai-contentsafety-java",
+ "path": "skills\\azure-ai-contentsafety-java",
"category": "uncategorized",
"name": "azure-ai-contentsafety-java",
"description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-contentsafety-py",
+ "path": "skills\\azure-ai-contentsafety-py",
+ "category": "uncategorized",
+ "name": "azure-ai-contentsafety-py",
+ "description": "Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.\nTriggers: \"azure-ai-contentsafety\", \"ContentSafetyClient\", \"content moderation\", \"harmful content\", \"text analysis\", \"image analysis\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-contentsafety-ts",
- "path": "skills/azure-ai-contentsafety-ts",
+ "path": "skills\\azure-ai-contentsafety-ts",
"category": "uncategorized",
"name": "azure-ai-contentsafety-ts",
"description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-contentunderstanding-py",
+ "path": "skills\\azure-ai-contentunderstanding-py",
+ "category": "uncategorized",
+ "name": "azure-ai-contentunderstanding-py",
+ "description": "Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.\nTriggers: \"azure-ai-contentunderstanding\", \"ContentUnderstandingClient\", \"multimodal analysis\", \"document extraction\", \"video analysis\", \"audio transcription\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-document-intelligence-dotnet",
+ "path": "skills\\azure-ai-document-intelligence-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-document-intelligence-dotnet",
+ "description": "Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: \"Document Intelligence\", \"DocumentIntelligenceClient\", \"form recognizer\", \"invoice extraction\", \"receipt OCR\", \"document analysis .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-document-intelligence-ts",
- "path": "skills/azure-ai-document-intelligence-ts",
+ "path": "skills\\azure-ai-document-intelligence-ts",
"category": "uncategorized",
"name": "azure-ai-document-intelligence-ts",
"description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...",
@@ -1432,16 +793,52 @@
},
{
"id": "azure-ai-formrecognizer-java",
- "path": "skills/azure-ai-formrecognizer-java",
+ "path": "skills\\azure-ai-formrecognizer-java",
"category": "uncategorized",
"name": "azure-ai-formrecognizer-java",
"description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-ml-py",
+ "path": "skills\\azure-ai-ml-py",
+ "category": "uncategorized",
+ "name": "azure-ai-ml-py",
+ "description": "Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.\nTriggers: \"azure-ai-ml\", \"MLClient\", \"workspace\", \"model registry\", \"training jobs\", \"datasets\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-openai-dotnet",
+ "path": "skills\\azure-ai-openai-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-openai-dotnet",
+ "description": "Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: \"Azure OpenAI\", \"AzureOpenAIClient\", \"ChatClient\", \"chat completions .NET\", \"GPT-4\", \"embeddings\", \"DALL-E\", \"Whisper\", \"OpenAI .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-projects-dotnet",
+ "path": "skills\\azure-ai-projects-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-projects-dotnet",
+ "description": "Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: \"AI Projects\", \"AIProjectClient\", \"Foundry project\", \"versioned agents\", \"evaluations\", \"datasets\", \"connections\", \"deployments .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-projects-java",
+ "path": "skills\\azure-ai-projects-java",
+ "category": "uncategorized",
+ "name": "azure-ai-projects-java",
+ "description": "Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.\nTriggers: \"AIProjectClient java\", \"azure ai projects java\", \"Foundry project java\", \"ConnectionsClient\", \"DatasetsClient\", \"IndexesClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-projects-py",
- "path": "skills/azure-ai-projects-py",
+ "path": "skills\\azure-ai-projects-py",
"category": "uncategorized",
"name": "azure-ai-projects-py",
"description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua...",
@@ -1450,16 +847,52 @@
},
{
"id": "azure-ai-projects-ts",
- "path": "skills/azure-ai-projects-ts",
+ "path": "skills\\azure-ai-projects-ts",
"category": "uncategorized",
"name": "azure-ai-projects-ts",
"description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-textanalytics-py",
+ "path": "skills\\azure-ai-textanalytics-py",
+ "category": "uncategorized",
+ "name": "azure-ai-textanalytics-py",
+ "description": "Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.\nTriggers: \"text analytics\", \"sentiment analysis\", \"entity recognition\", \"key phrase\", \"PII detection\", \"TextAnalyticsClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-transcription-py",
+ "path": "skills\\azure-ai-transcription-py",
+ "category": "uncategorized",
+ "name": "azure-ai-transcription-py",
+ "description": "Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.\nTriggers: \"transcription\", \"speech to text\", \"Azure AI Transcription\", \"TranscriptionClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-translation-document-py",
+ "path": "skills\\azure-ai-translation-document-py",
+ "category": "uncategorized",
+ "name": "azure-ai-translation-document-py",
+ "description": "Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.\nTriggers: \"document translation\", \"batch translation\", \"translate documents\", \"DocumentTranslationClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-translation-text-py",
+ "path": "skills\\azure-ai-translation-text-py",
+ "category": "uncategorized",
+ "name": "azure-ai-translation-text-py",
+ "description": "Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.\nTriggers: \"text translation\", \"translator\", \"translate text\", \"transliterate\", \"TextTranslationClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-translation-ts",
- "path": "skills/azure-ai-translation-ts",
+ "path": "skills\\azure-ai-translation-ts",
"category": "uncategorized",
"name": "azure-ai-translation-ts",
"description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...",
@@ -1468,25 +901,79 @@
},
{
"id": "azure-ai-vision-imageanalysis-java",
- "path": "skills/azure-ai-vision-imageanalysis-java",
+ "path": "skills\\azure-ai-vision-imageanalysis-java",
"category": "uncategorized",
"name": "azure-ai-vision-imageanalysis-java",
"description": "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-vision-imageanalysis-py",
+ "path": "skills\\azure-ai-vision-imageanalysis-py",
+ "category": "uncategorized",
+ "name": "azure-ai-vision-imageanalysis-py",
+ "description": "Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.\nTriggers: \"image analysis\", \"computer vision\", \"OCR\", \"object detection\", \"ImageAnalysisClient\", \"image caption\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-voicelive-dotnet",
+ "path": "skills\\azure-ai-voicelive-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-dotnet",
+ "description": "Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant .NET\", \"bidirectional audio\", \"speech-to-speech\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-voicelive-java",
+ "path": "skills\\azure-ai-voicelive-java",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-java",
+ "description": "Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.\nTriggers: \"VoiceLiveClient java\", \"voice assistant java\", \"real-time voice java\", \"audio streaming java\", \"voice activity detection java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-voicelive-py",
- "path": "skills/azure-ai-voicelive-py",
+ "path": "skills\\azure-ai-voicelive-py",
"category": "uncategorized",
"name": "azure-ai-voicelive-py",
"description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-voicelive-ts",
+ "path": "skills\\azure-ai-voicelive-ts",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-ts",
+ "description": "Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant TypeScript\", \"bidirectional audio\", \"speech-to-speech JavaScript\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-appconfiguration-java",
+ "path": "skills\\azure-appconfiguration-java",
+ "category": "uncategorized",
+ "name": "azure-appconfiguration-java",
+ "description": "Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.\nTriggers: \"ConfigurationClient java\", \"app configuration java\", \"feature flag java\", \"configuration setting java\", \"azure config java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-appconfiguration-py",
+ "path": "skills\\azure-appconfiguration-py",
+ "category": "uncategorized",
+ "name": "azure-appconfiguration-py",
+ "description": "Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.\nTriggers: \"azure-appconfiguration\", \"AzureAppConfigurationClient\", \"feature flags\", \"configuration\", \"key-value settings\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-appconfiguration-ts",
- "path": "skills/azure-appconfiguration-ts",
+ "path": "skills\\azure-appconfiguration-ts",
"category": "uncategorized",
"name": "azure-appconfiguration-ts",
"description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...",
@@ -1495,7 +982,7 @@
},
{
"id": "azure-communication-callautomation-java",
- "path": "skills/azure-communication-callautomation-java",
+ "path": "skills\\azure-communication-callautomation-java",
"category": "uncategorized",
"name": "azure-communication-callautomation-java",
"description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...",
@@ -1504,7 +991,7 @@
},
{
"id": "azure-communication-callingserver-java",
- "path": "skills/azure-communication-callingserver-java",
+ "path": "skills\\azure-communication-callingserver-java",
"category": "uncategorized",
"name": "azure-communication-callingserver-java",
"description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...",
@@ -1513,7 +1000,7 @@
},
{
"id": "azure-communication-chat-java",
- "path": "skills/azure-communication-chat-java",
+ "path": "skills\\azure-communication-chat-java",
"category": "uncategorized",
"name": "azure-communication-chat-java",
"description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...",
@@ -1522,7 +1009,7 @@
},
{
"id": "azure-communication-common-java",
- "path": "skills/azure-communication-common-java",
+ "path": "skills\\azure-communication-common-java",
"category": "uncategorized",
"name": "azure-communication-common-java",
"description": "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.",
@@ -1531,52 +1018,160 @@
},
{
"id": "azure-communication-sms-java",
- "path": "skills/azure-communication-sms-java",
+ "path": "skills\\azure-communication-sms-java",
"category": "uncategorized",
"name": "azure-communication-sms-java",
"description": "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-compute-batch-java",
+ "path": "skills\\azure-compute-batch-java",
+ "category": "uncategorized",
+ "name": "azure-compute-batch-java",
+ "description": "Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.\nTriggers: \"BatchClient java\", \"azure batch java\", \"batch pool java\", \"batch job java\", \"HPC java\", \"parallel computing java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-containerregistry-py",
+ "path": "skills\\azure-containerregistry-py",
+ "category": "uncategorized",
+ "name": "azure-containerregistry-py",
+ "description": "Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.\nTriggers: \"azure-containerregistry\", \"ContainerRegistryClient\", \"container images\", \"docker registry\", \"ACR\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-cosmos-db-py",
- "path": "skills/azure-cosmos-db-py",
+ "path": "skills\\azure-cosmos-db-py",
"category": "uncategorized",
"name": "azure-cosmos-db-py",
"description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-cosmos-java",
+ "path": "skills\\azure-cosmos-java",
+ "category": "uncategorized",
+ "name": "azure-cosmos-java",
+ "description": "Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.\nTriggers: \"CosmosClient java\", \"CosmosAsyncClient\", \"cosmos database java\", \"cosmosdb java\", \"document database java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-py",
+ "path": "skills\\azure-cosmos-py",
+ "category": "uncategorized",
+ "name": "azure-cosmos-py",
+ "description": "Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db\", \"CosmosClient\", \"container\", \"document\", \"NoSQL\", \"partition key\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-rust",
+ "path": "skills\\azure-cosmos-rust",
+ "category": "uncategorized",
+ "name": "azure-cosmos-rust",
+ "description": "Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db rust\", \"CosmosClient rust\", \"container\", \"document rust\", \"NoSQL rust\", \"partition key\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-ts",
+ "path": "skills\\azure-cosmos-ts",
+ "category": "uncategorized",
+ "name": "azure-cosmos-ts",
+ "description": "Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: \"Cosmos DB\", \"@azure/cosmos\", \"CosmosClient\", \"document CRUD\", \"NoSQL queries\", \"bulk operations\", \"partition key\", \"container.items\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-data-tables-java",
- "path": "skills/azure-data-tables-java",
+ "path": "skills\\azure-data-tables-java",
"category": "uncategorized",
"name": "azure-data-tables-java",
"description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-data-tables-py",
+ "path": "skills\\azure-data-tables-py",
+ "category": "uncategorized",
+ "name": "azure-data-tables-py",
+ "description": "Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.\nTriggers: \"table storage\", \"TableServiceClient\", \"TableClient\", \"entities\", \"PartitionKey\", \"RowKey\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventgrid-dotnet",
+ "path": "skills\\azure-eventgrid-dotnet",
+ "category": "uncategorized",
+ "name": "azure-eventgrid-dotnet",
+ "description": "Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: \"Event Grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events .NET\", \"event-driven\", \"pub/sub\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventgrid-java",
- "path": "skills/azure-eventgrid-java",
+ "path": "skills\\azure-eventgrid-java",
"category": "uncategorized",
"name": "azure-eventgrid-java",
"description": "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-eventgrid-py",
+ "path": "skills\\azure-eventgrid-py",
+ "category": "uncategorized",
+ "name": "azure-eventgrid-py",
+ "description": "Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.\nTriggers: \"event grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventhub-dotnet",
+ "path": "skills\\azure-eventhub-dotnet",
+ "category": "uncategorized",
+ "name": "azure-eventhub-dotnet",
+ "description": "Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: \"Event Hubs\", \"event streaming\", \"EventHubProducerClient\", \"EventProcessorClient\", \"send events\", \"receive events\", \"checkpointing\", \"partition\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventhub-java",
- "path": "skills/azure-eventhub-java",
+ "path": "skills\\azure-eventhub-java",
"category": "uncategorized",
"name": "azure-eventhub-java",
"description": "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-eventhub-py",
+ "path": "skills\\azure-eventhub-py",
+ "category": "uncategorized",
+ "name": "azure-eventhub-py",
+ "description": "Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.\nTriggers: \"event hubs\", \"EventHubProducerClient\", \"EventHubConsumerClient\", \"streaming\", \"partitions\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventhub-rust",
+ "path": "skills\\azure-eventhub-rust",
+ "category": "uncategorized",
+ "name": "azure-eventhub-rust",
+ "description": "Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.\nTriggers: \"event hubs rust\", \"ProducerClient rust\", \"ConsumerClient rust\", \"send event rust\", \"streaming rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventhub-ts",
- "path": "skills/azure-eventhub-ts",
+ "path": "skills\\azure-eventhub-ts",
"category": "uncategorized",
"name": "azure-eventhub-ts",
"description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event...",
@@ -1585,97 +1180,439 @@
},
{
"id": "azure-functions",
- "path": "skills/azure-functions",
+ "path": "skills\\azure-functions",
"category": "uncategorized",
"name": "azure-functions",
"description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "azure-identity-dotnet",
+ "path": "skills\\azure-identity-dotnet",
+ "category": "uncategorized",
+ "name": "azure-identity-dotnet",
+ "description": "Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: \"Azure Identity\", \"DefaultAzureCredential\", \"ManagedIdentityCredential\", \"ClientSecretCredential\", \"authentication .NET\", \"Azure auth\", \"credential chain\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-identity-java",
- "path": "skills/azure-identity-java",
+ "path": "skills\\azure-identity-java",
"category": "uncategorized",
"name": "azure-identity-java",
"description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-identity-py",
+ "path": "skills\\azure-identity-py",
+ "category": "uncategorized",
+ "name": "azure-identity-py",
+ "description": "Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.\nTriggers: \"azure-identity\", \"DefaultAzureCredential\", \"authentication\", \"managed identity\", \"service principal\", \"credential\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-identity-rust",
+ "path": "skills\\azure-identity-rust",
+ "category": "uncategorized",
+ "name": "azure-identity-rust",
+ "description": "Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.\nTriggers: \"azure-identity\", \"DeveloperToolsCredential\", \"authentication rust\", \"managed identity rust\", \"credential rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-identity-ts",
- "path": "skills/azure-identity-ts",
+ "path": "skills\\azure-identity-ts",
"category": "uncategorized",
"name": "azure-identity-ts",
"description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-keyvault-certificates-rust",
+ "path": "skills\\azure-keyvault-certificates-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-certificates-rust",
+ "description": "Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.\nTriggers: \"keyvault certificates rust\", \"CertificateClient rust\", \"create certificate rust\", \"import certificate rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-keyvault-keys-rust",
+ "path": "skills\\azure-keyvault-keys-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-keys-rust",
+ "description": "Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.\nTriggers: \"keyvault keys rust\", \"KeyClient rust\", \"create key rust\", \"encrypt rust\", \"sign rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-keyvault-keys-ts",
- "path": "skills/azure-keyvault-keys-ts",
+ "path": "skills\\azure-keyvault-keys-ts",
"category": "uncategorized",
"name": "azure-keyvault-keys-ts",
"description": "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-keyvault-py",
+ "path": "skills\\azure-keyvault-py",
+ "category": "uncategorized",
+ "name": "azure-keyvault-py",
+ "description": "Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.\nTriggers: \"key vault\", \"SecretClient\", \"KeyClient\", \"CertificateClient\", \"secrets\", \"encryption keys\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-keyvault-secrets-rust",
+ "path": "skills\\azure-keyvault-secrets-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-secrets-rust",
+ "description": "Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.\nTriggers: \"keyvault secrets rust\", \"SecretClient rust\", \"get secret rust\", \"set secret rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-keyvault-secrets-ts",
- "path": "skills/azure-keyvault-secrets-ts",
+ "path": "skills\\azure-keyvault-secrets-ts",
"category": "uncategorized",
"name": "azure-keyvault-secrets-ts",
"description": "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-maps-search-dotnet",
+ "path": "skills\\azure-maps-search-dotnet",
+ "category": "uncategorized",
+ "name": "azure-maps-search-dotnet",
+ "description": "Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: \"Azure Maps\", \"MapsSearchClient\", \"MapsRoutingClient\", \"MapsRenderingClient\", \"geocoding .NET\", \"route directions\", \"map tiles\", \"geolocation\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-messaging-webpubsub-java",
- "path": "skills/azure-messaging-webpubsub-java",
+ "path": "skills\\azure-messaging-webpubsub-java",
"category": "uncategorized",
"name": "azure-messaging-webpubsub-java",
"description": "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-messaging-webpubsubservice-py",
+ "path": "skills\\azure-messaging-webpubsubservice-py",
+ "category": "uncategorized",
+ "name": "azure-messaging-webpubsubservice-py",
+ "description": "Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.\nTriggers: \"azure-messaging-webpubsubservice\", \"WebPubSubServiceClient\", \"real-time\", \"WebSocket\", \"pub/sub\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apicenter-dotnet",
+ "path": "skills\\azure-mgmt-apicenter-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apicenter-dotnet",
+ "description": "Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: \"API Center\", \"ApiCenterService\", \"ApiCenterWorkspace\", \"ApiCenterApi\", \"API inventory\", \"API governance\", \"API versioning\", \"API catalog\", \"API discovery\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apicenter-py",
+ "path": "skills\\azure-mgmt-apicenter-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apicenter-py",
+ "description": "Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.\nTriggers: \"azure-mgmt-apicenter\", \"ApiCenterMgmtClient\", \"API Center\", \"API inventory\", \"API governance\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-dotnet",
+ "path": "skills\\azure-mgmt-apimanagement-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apimanagement-dotnet",
+ "description": "Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: \"API Management\", \"APIM service\", \"create APIM\", \"manage APIs\", \"ApiManagementServiceResource\", \"API policies\", \"APIM products\", \"APIM subscriptions\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-py",
+ "path": "skills\\azure-mgmt-apimanagement-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apimanagement-py",
+ "description": "Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.\nTriggers: \"azure-mgmt-apimanagement\", \"ApiManagementClient\", \"APIM\", \"API gateway\", \"API Management\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-applicationinsights-dotnet",
+ "path": "skills\\azure-mgmt-applicationinsights-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-applicationinsights-dotnet",
+ "description": "Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: \"Application Insights\", \"ApplicationInsights\", \"App Insights\", \"APM\", \"application monitoring\", \"web tests\", \"availability tests\", \"workbooks\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "path": "skills\\azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "description": "Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations \non Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability \ninto .NET applications. Triggers: \"Arize AI\", \"ML observability\", \"ArizeAIObservabilityEval\", \"Arize organization\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-botservice-dotnet",
+ "path": "skills\\azure-mgmt-botservice-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-botservice-dotnet",
+ "description": "Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: \"Bot Service\", \"BotResource\", \"Azure Bot\", \"DirectLine channel\", \"Teams channel\", \"bot management .NET\", \"create bot\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-botservice-py",
+ "path": "skills\\azure-mgmt-botservice-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-botservice-py",
+ "description": "Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.\nTriggers: \"azure-mgmt-botservice\", \"AzureBotService\", \"bot management\", \"conversational AI\", \"bot channels\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-fabric-dotnet",
+ "path": "skills\\azure-mgmt-fabric-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-fabric-dotnet",
+ "description": "Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: \"Fabric capacity\", \"create capacity\", \"suspend capacity\", \"resume capacity\", \"Fabric SKU\", \"provision Fabric\", \"ARM Fabric\", \"FabricCapacityResource\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-fabric-py",
+ "path": "skills\\azure-mgmt-fabric-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-fabric-py",
+ "description": "Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.\nTriggers: \"azure-mgmt-fabric\", \"FabricMgmtClient\", \"Fabric capacity\", \"Microsoft Fabric\", \"Power BI capacity\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-mgmt-mongodbatlas-dotnet",
- "path": "skills/azure-mgmt-mongodbatlas-dotnet",
+ "path": "skills\\azure-mgmt-mongodbatlas-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-mongodbatlas-dotnet",
"description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-mgmt-weightsandbiases-dotnet",
+ "path": "skills\\azure-mgmt-weightsandbiases-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-weightsandbiases-dotnet",
+ "description": "Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: \"Weights and Biases\", \"W&B\", \"WeightsAndBiases\", \"ML experiment tracking\", \"model registry\", \"experiment management\", \"wandb\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-microsoft-playwright-testing-ts",
- "path": "skills/azure-microsoft-playwright-testing-ts",
+ "path": "skills\\azure-microsoft-playwright-testing-ts",
"category": "uncategorized",
"name": "azure-microsoft-playwright-testing-ts",
"description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-monitor-ingestion-java",
+ "path": "skills\\azure-monitor-ingestion-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-ingestion-java",
+ "description": "Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).\nTriggers: \"LogsIngestionClient java\", \"azure monitor ingestion java\", \"custom logs java\", \"DCR java\", \"data collection rule java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-ingestion-py",
+ "path": "skills\\azure-monitor-ingestion-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-ingestion-py",
+ "description": "Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.\nTriggers: \"azure-monitor-ingestion\", \"LogsIngestionClient\", \"custom logs\", \"DCR\", \"data collection rule\", \"Log Analytics\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-java",
+ "path": "skills\\azure-monitor-opentelemetry-exporter-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-exporter-java",
+ "description": "Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.\nTriggers: \"AzureMonitorExporter java\", \"opentelemetry azure java\", \"application insights java otel\", \"azure monitor tracing java\".\nNote: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-py",
+ "path": "skills\\azure-monitor-opentelemetry-exporter-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-exporter-py",
+ "description": "Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.\nTriggers: \"azure-monitor-opentelemetry-exporter\", \"AzureMonitorTraceExporter\", \"AzureMonitorMetricExporter\", \"AzureMonitorLogExporter\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-py",
+ "path": "skills\\azure-monitor-opentelemetry-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-py",
+ "description": "Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.\nTriggers: \"azure-monitor-opentelemetry\", \"configure_azure_monitor\", \"Application Insights\", \"OpenTelemetry distro\", \"auto-instrumentation\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-monitor-opentelemetry-ts",
- "path": "skills/azure-monitor-opentelemetry-ts",
+ "path": "skills\\azure-monitor-opentelemetry-ts",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-ts",
"description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-monitor-query-java",
+ "path": "skills\\azure-monitor-query-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-query-java",
+ "description": "Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.\nTriggers: \"LogsQueryClient java\", \"MetricsQueryClient java\", \"kusto query java\", \"log analytics java\", \"azure monitor query java\".\nNote: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-query-py",
+ "path": "skills\\azure-monitor-query-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-query-py",
+ "description": "Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.\nTriggers: \"azure-monitor-query\", \"LogsQueryClient\", \"MetricsQueryClient\", \"Log Analytics\", \"Kusto queries\", \"Azure metrics\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-postgres-ts",
+ "path": "skills\\azure-postgres-ts",
+ "category": "uncategorized",
+ "name": "azure-postgres-ts",
+ "description": "Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: \"PostgreSQL\", \"postgres\", \"pg client\", \"node-postgres\", \"Azure PostgreSQL connection\", \"PostgreSQL TypeScript\", \"pg Pool\", \"passwordless postgres\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-cosmosdb-dotnet",
+ "path": "skills\\azure-resource-manager-cosmosdb-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-cosmosdb-dotnet",
+ "description": "Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: \"Cosmos DB account\", \"create Cosmos account\", \"manage Cosmos resources\", \"ARM Cosmos\", \"CosmosDBAccountResource\", \"provision Cosmos DB\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-durabletask-dotnet",
+ "path": "skills\\azure-resource-manager-durabletask-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-durabletask-dotnet",
+ "description": "Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: \"Durable Task Scheduler\", \"create scheduler\", \"task hub\", \"DurableTaskSchedulerResource\", \"provision Durable Task\", \"orchestration scheduler\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-mysql-dotnet",
+ "path": "skills\\azure-resource-manager-mysql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-mysql-dotnet",
+ "description": "Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"MySQL\", \"MySqlFlexibleServer\", \"MySQL Flexible Server\", \"Azure Database for MySQL\", \"MySQL database management\", \"MySQL firewall\", \"MySQL backup\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-playwright-dotnet",
+ "path": "skills\\azure-resource-manager-playwright-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-playwright-dotnet",
+ "description": "Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: \"Playwright workspace\", \"create Playwright Testing workspace\", \"manage Playwright resources\", \"ARM Playwright\", \"PlaywrightWorkspaceResource\", \"provision Playwright Testing\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-postgresql-dotnet",
+ "path": "skills\\azure-resource-manager-postgresql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-postgresql-dotnet",
+ "description": "Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"PostgreSQL\", \"PostgreSqlFlexibleServer\", \"PostgreSQL Flexible Server\", \"Azure Database for PostgreSQL\", \"PostgreSQL database management\", \"PostgreSQL firewall\", \"PostgreSQL backup\", \"Postgres\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-redis-dotnet",
+ "path": "skills\\azure-resource-manager-redis-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-redis-dotnet",
+ "description": "Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: \"Redis cache\", \"create Redis\", \"manage Redis\", \"ARM Redis\", \"RedisResource\", \"provision Redis\", \"Azure Cache for Redis\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-sql-dotnet",
+ "path": "skills\\azure-resource-manager-sql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-sql-dotnet",
+ "description": "Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: \"SQL server\", \"create SQL database\", \"manage SQL resources\", \"ARM SQL\", \"SqlServerResource\", \"provision Azure SQL\", \"elastic pool\", \"firewall rule\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-search-documents-dotnet",
+ "path": "skills\\azure-search-documents-dotnet",
+ "category": "uncategorized",
+ "name": "azure-search-documents-dotnet",
+ "description": "Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: \"Azure Search .NET\", \"SearchClient\", \"SearchIndexClient\", \"vector search C#\", \"semantic search .NET\", \"hybrid search\", \"Azure.Search.Documents\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-search-documents-py",
+ "path": "skills\\azure-search-documents-py",
+ "category": "uncategorized",
+ "name": "azure-search-documents-py",
+ "description": "Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.\nTriggers: \"azure-search-documents\", \"SearchClient\", \"SearchIndexClient\", \"vector search\", \"hybrid search\", \"semantic search\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-search-documents-ts",
- "path": "skills/azure-search-documents-ts",
+ "path": "skills\\azure-search-documents-ts",
"category": "uncategorized",
"name": "azure-search-documents-ts",
"description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-security-keyvault-keys-dotnet",
+ "path": "skills\\azure-security-keyvault-keys-dotnet",
+ "category": "uncategorized",
+ "name": "azure-security-keyvault-keys-dotnet",
+ "description": "Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: \"Key Vault keys\", \"KeyClient\", \"CryptographyClient\", \"RSA key\", \"EC key\", \"encrypt decrypt .NET\", \"key rotation\", \"HSM\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-security-keyvault-keys-java",
- "path": "skills/azure-security-keyvault-keys-java",
+ "path": "skills\\azure-security-keyvault-keys-java",
"category": "uncategorized",
"name": "azure-security-keyvault-keys-java",
"description": "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.",
@@ -1684,34 +1621,133 @@
},
{
"id": "azure-security-keyvault-secrets-java",
- "path": "skills/azure-security-keyvault-secrets-java",
+ "path": "skills\\azure-security-keyvault-secrets-java",
"category": "uncategorized",
"name": "azure-security-keyvault-secrets-java",
"description": "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-servicebus-dotnet",
+ "path": "skills\\azure-servicebus-dotnet",
+ "category": "uncategorized",
+ "name": "azure-servicebus-dotnet",
+ "description": "Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: \"Service Bus\", \"ServiceBusClient\", \"ServiceBusSender\", \"ServiceBusReceiver\", \"ServiceBusProcessor\", \"message queue\", \"pub/sub .NET\", \"dead letter queue\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-servicebus-py",
+ "path": "skills\\azure-servicebus-py",
+ "category": "uncategorized",
+ "name": "azure-servicebus-py",
+ "description": "Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.\nTriggers: \"service bus\", \"ServiceBusClient\", \"queue\", \"topic\", \"subscription\", \"message broker\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-servicebus-ts",
- "path": "skills/azure-servicebus-ts",
+ "path": "skills\\azure-servicebus-ts",
"category": "uncategorized",
"name": "azure-servicebus-ts",
"description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-speech-to-text-rest-py",
+ "path": "skills\\azure-speech-to-text-rest-py",
+ "category": "uncategorized",
+ "name": "azure-speech-to-text-rest-py",
+ "description": "Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.\nTriggers: \"speech to text REST\", \"short audio transcription\", \"speech recognition REST API\", \"STT REST\", \"recognize speech REST\".\nDO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-storage-blob-java",
- "path": "skills/azure-storage-blob-java",
+ "path": "skills\\azure-storage-blob-java",
"category": "uncategorized",
"name": "azure-storage-blob-java",
"description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-storage-blob-py",
+ "path": "skills\\azure-storage-blob-py",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-py",
+ "description": "Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.\nTriggers: \"blob storage\", \"BlobServiceClient\", \"ContainerClient\", \"BlobClient\", \"upload blob\", \"download blob\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-blob-rust",
+ "path": "skills\\azure-storage-blob-rust",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-rust",
+ "description": "Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.\nTriggers: \"blob storage rust\", \"BlobClient rust\", \"upload blob rust\", \"download blob rust\", \"container rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-blob-ts",
+ "path": "skills\\azure-storage-blob-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-ts",
+ "description": "Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: \"blob storage\", \"@azure/storage-blob\", \"BlobServiceClient\", \"ContainerClient\", \"upload blob\", \"download blob\", \"SAS token\", \"block blob\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-datalake-py",
+ "path": "skills\\azure-storage-file-datalake-py",
+ "category": "uncategorized",
+ "name": "azure-storage-file-datalake-py",
+ "description": "Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.\nTriggers: \"data lake\", \"DataLakeServiceClient\", \"FileSystemClient\", \"ADLS Gen2\", \"hierarchical namespace\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-share-py",
+ "path": "skills\\azure-storage-file-share-py",
+ "category": "uncategorized",
+ "name": "azure-storage-file-share-py",
+ "description": "Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.\nTriggers: \"azure-storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"file share\", \"SMB\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-share-ts",
+ "path": "skills\\azure-storage-file-share-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-file-share-ts",
+ "description": "Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: \"file share\", \"@azure/storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"SMB\", \"Azure Files\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-queue-py",
+ "path": "skills\\azure-storage-queue-py",
+ "category": "uncategorized",
+ "name": "azure-storage-queue-py",
+ "description": "Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.\nTriggers: \"queue storage\", \"QueueServiceClient\", \"QueueClient\", \"message queue\", \"dequeue\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-queue-ts",
+ "path": "skills\\azure-storage-queue-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-queue-ts",
+ "description": "Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: \"queue storage\", \"@azure/storage-queue\", \"QueueServiceClient\", \"QueueClient\", \"send message\", \"receive message\", \"dequeue\", \"visibility timeout\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-web-pubsub-ts",
- "path": "skills/azure-web-pubsub-ts",
+ "path": "skills\\azure-web-pubsub-ts",
"category": "uncategorized",
"name": "azure-web-pubsub-ts",
"description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...",
@@ -1720,25 +1756,16 @@
},
{
"id": "backend-architect",
- "path": "skills/backend-architect",
+ "path": "skills\\backend-architect",
"category": "uncategorized",
- "name": "Backend Architect",
- "description": "You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.",
+ "name": "backend-architect",
+ "description": "Expert backend architect specializing in scalable API design,\nmicroservices architecture, and distributed systems. Masters REST/GraphQL/gRPC\nAPIs, event-driven architectures, service mesh patterns, and modern backend\nframeworks. Handles service boundary definition, inter-service communication,\nresilience patterns, and observability. Use PROACTIVELY when creating new\nbackend services or APIs.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "backend-security-coder",
- "path": "skills/backend-security-coder",
- "category": "uncategorized",
- "name": "Backend Security Coder",
- "description": "- Working on backend security coder tasks or workflows - Needing guidance, best practices, or checklists for backend security coder",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "backend-dev-guidelines",
- "path": "skills/backend-dev-guidelines",
+ "path": "skills\\backend-dev-guidelines",
"category": "uncategorized",
"name": "backend-dev-guidelines",
"description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid...",
@@ -1747,16 +1774,25 @@
},
{
"id": "backend-development-feature-development",
- "path": "skills/backend-development-feature-development",
+ "path": "skills\\backend-development-feature-development",
"category": "uncategorized",
"name": "backend-development-feature-development",
"description": "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "backend-security-coder",
+ "path": "skills\\backend-security-coder",
+ "category": "uncategorized",
+ "name": "backend-security-coder",
+ "description": "Expert in secure backend coding practices specializing in input\nvalidation, authentication, and API security. Use PROACTIVELY for backend\nsecurity implementations or security code reviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "backtesting-frameworks",
- "path": "skills/backtesting-frameworks",
+ "path": "skills\\backtesting-frameworks",
"category": "uncategorized",
"name": "backtesting-frameworks",
"description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...",
@@ -1765,7 +1801,7 @@
},
{
"id": "bamboohr-automation",
- "path": "skills/bamboohr-automation",
+ "path": "skills\\bamboohr-automation",
"category": "uncategorized",
"name": "bamboohr-automation",
"description": "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.",
@@ -1774,7 +1810,7 @@
},
{
"id": "base",
- "path": "skills/libreoffice/base",
+ "path": "skills\\libreoffice\\base",
"category": "libreoffice",
"name": "base",
"description": "Database management, forms, reports, and data operations with LibreOffice Base.",
@@ -1783,25 +1819,16 @@
},
{
"id": "basecamp-automation",
- "path": "skills/basecamp-automation",
+ "path": "skills\\basecamp-automation",
"category": "uncategorized",
"name": "basecamp-automation",
"description": "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "bash-pro",
- "path": "skills/bash-pro",
- "category": "uncategorized",
- "name": "Bash Pro",
- "description": "- Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "bash-defensive-patterns",
- "path": "skills/bash-defensive-patterns",
+ "path": "skills\\bash-defensive-patterns",
"category": "uncategorized",
"name": "bash-defensive-patterns",
"description": "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.",
@@ -1810,16 +1837,25 @@
},
{
"id": "bash-linux",
- "path": "skills/bash-linux",
+ "path": "skills\\bash-linux",
"category": "uncategorized",
"name": "bash-linux",
"description": "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "bash-pro",
+ "path": "skills\\bash-pro",
+ "category": "uncategorized",
+ "name": "bash-pro",
+ "description": "Master of defensive Bash scripting for production automation, CI/CD\npipelines, and system utilities. Expert in safe, portable, and testable shell\nscripts.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "bash-scripting",
- "path": "skills/bash-scripting",
+ "path": "skills\\bash-scripting",
"category": "uncategorized",
"name": "bash-scripting",
"description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
@@ -1828,7 +1864,7 @@
},
{
"id": "bats-testing-patterns",
- "path": "skills/bats-testing-patterns",
+ "path": "skills\\bats-testing-patterns",
"category": "uncategorized",
"name": "bats-testing-patterns",
"description": "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.",
@@ -1837,7 +1873,7 @@
},
{
"id": "bazel-build-optimization",
- "path": "skills/bazel-build-optimization",
+ "path": "skills\\bazel-build-optimization",
"category": "uncategorized",
"name": "bazel-build-optimization",
"description": "Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.",
@@ -1846,7 +1882,7 @@
},
{
"id": "beautiful-prose",
- "path": "skills/beautiful-prose",
+ "path": "skills\\beautiful-prose",
"category": "uncategorized",
"name": "beautiful-prose",
"description": "Hard-edged writing style contract for timeless, forceful English prose without AI tics",
@@ -1855,7 +1891,7 @@
},
{
"id": "behavioral-modes",
- "path": "skills/behavioral-modes",
+ "path": "skills\\behavioral-modes",
"category": "uncategorized",
"name": "behavioral-modes",
"description": "AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.",
@@ -1864,7 +1900,7 @@
},
{
"id": "bevy-ecs-expert",
- "path": "skills/bevy-ecs-expert",
+ "path": "skills\\bevy-ecs-expert",
"category": "uncategorized",
"name": "bevy-ecs-expert",
"description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
@@ -1873,7 +1909,7 @@
},
{
"id": "billing-automation",
- "path": "skills/billing-automation",
+ "path": "skills\\billing-automation",
"category": "uncategorized",
"name": "billing-automation",
"description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...",
@@ -1882,7 +1918,7 @@
},
{
"id": "binary-analysis-patterns",
- "path": "skills/binary-analysis-patterns",
+ "path": "skills\\binary-analysis-patterns",
"category": "uncategorized",
"name": "binary-analysis-patterns",
"description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing...",
@@ -1891,7 +1927,7 @@
},
{
"id": "bitbucket-automation",
- "path": "skills/bitbucket-automation",
+ "path": "skills\\bitbucket-automation",
"category": "uncategorized",
"name": "bitbucket-automation",
"description": "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -1900,16 +1936,16 @@
},
{
"id": "blockchain-developer",
- "path": "skills/blockchain-developer",
+ "path": "skills\\blockchain-developer",
"category": "uncategorized",
- "name": "Blockchain Developer",
- "description": "- Working on blockchain developer tasks or workflows - Needing guidance, best practices, or checklists for blockchain developer",
+ "name": "blockchain-developer",
+ "description": "Build production-ready Web3 applications, smart contracts, and\ndecentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and\nenterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3\napps, DeFi protocols, or blockchain infrastructure.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "blockrun",
- "path": "skills/blockrun",
+ "path": "skills\\blockrun",
"category": "uncategorized",
"name": "blockrun",
"description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da...",
@@ -1918,7 +1954,7 @@
},
{
"id": "box-automation",
- "path": "skills/box-automation",
+ "path": "skills\\box-automation",
"category": "uncategorized",
"name": "box-automation",
"description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for...",
@@ -1927,7 +1963,7 @@
},
{
"id": "brainstorming",
- "path": "skills/brainstorming",
+ "path": "skills\\brainstorming",
"category": "uncategorized",
"name": "brainstorming",
"description": "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.",
@@ -1936,7 +1972,7 @@
},
{
"id": "brand-guidelines-anthropic",
- "path": "skills/brand-guidelines-anthropic",
+ "path": "skills\\brand-guidelines-anthropic",
"category": "uncategorized",
"name": "brand-guidelines-anthropic",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
@@ -1945,7 +1981,7 @@
},
{
"id": "brand-guidelines-community",
- "path": "skills/brand-guidelines-community",
+ "path": "skills\\brand-guidelines-community",
"category": "uncategorized",
"name": "brand-guidelines-community",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
@@ -1954,7 +1990,7 @@
},
{
"id": "brevo-automation",
- "path": "skills/brevo-automation",
+ "path": "skills\\brevo-automation",
"category": "uncategorized",
"name": "brevo-automation",
"description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche...",
@@ -1963,7 +1999,7 @@
},
{
"id": "broken-authentication",
- "path": "skills/broken-authentication",
+ "path": "skills\\broken-authentication",
"category": "uncategorized",
"name": "broken-authentication",
"description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ...",
@@ -1972,7 +2008,7 @@
},
{
"id": "browser-automation",
- "path": "skills/browser-automation",
+ "path": "skills\\browser-automation",
"category": "uncategorized",
"name": "browser-automation",
"description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...",
@@ -1981,7 +2017,7 @@
},
{
"id": "browser-extension-builder",
- "path": "skills/browser-extension-builder",
+ "path": "skills\\browser-extension-builder",
"category": "uncategorized",
"name": "browser-extension-builder",
"description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ...",
@@ -1990,7 +2026,7 @@
},
{
"id": "bullmq-specialist",
- "path": "skills/bullmq-specialist",
+ "path": "skills\\bullmq-specialist",
"category": "uncategorized",
"name": "bullmq-specialist",
"description": "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.",
@@ -1999,7 +2035,7 @@
},
{
"id": "bun-development",
- "path": "skills/bun-development",
+ "path": "skills\\bun-development",
"category": "uncategorized",
"name": "bun-development",
"description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o...",
@@ -2008,7 +2044,7 @@
},
{
"id": "burp-suite-testing",
- "path": "skills/burp-suite-testing",
+ "path": "skills\\burp-suite-testing",
"category": "uncategorized",
"name": "burp-suite-testing",
"description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ...",
@@ -2017,16 +2053,16 @@
},
{
"id": "business-analyst",
- "path": "skills/business-analyst",
+ "path": "skills\\business-analyst",
"category": "uncategorized",
- "name": "Business Analyst",
- "description": "- Working on business analyst tasks or workflows - Needing guidance, best practices, or checklists for business analyst",
+ "name": "business-analyst",
+ "description": "Master modern business analysis with AI-powered analytics,\nreal-time dashboards, and data-driven insights. Build comprehensive KPI\nframeworks, predictive models, and strategic recommendations. Use PROACTIVELY\nfor business intelligence or strategic analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "busybox-on-windows",
- "path": "skills/busybox-on-windows",
+ "path": "skills\\busybox-on-windows",
"category": "uncategorized",
"name": "busybox-on-windows",
"description": "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.",
@@ -2035,61 +2071,61 @@
},
{
"id": "c-pro",
- "path": "skills/c-pro",
+ "path": "skills\\c-pro",
"category": "uncategorized",
"name": "c-pro",
"description": "Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "c4-code",
- "path": "skills/c4-code",
- "category": "uncategorized",
- "name": "C4 Code",
- "description": "- Working on c4 code level: [directory name] tasks or workflows - Needing guidance, best practices, or checklists for c4 code level: [directory name]",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-component",
- "path": "skills/c4-component",
- "category": "uncategorized",
- "name": "C4 Component",
- "description": "- Working on c4 component level: [component name] tasks or workflows - Needing guidance, best practices, or checklists for c4 component level: [component name]",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-container",
- "path": "skills/c4-container",
- "category": "uncategorized",
- "name": "C4 Container",
- "description": "- Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-context",
- "path": "skills/c4-context",
- "category": "uncategorized",
- "name": "C4 Context",
- "description": "- Working on c4 context level: system context tasks or workflows - Needing guidance, best practices, or checklists for c4 context level: system context",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "c4-architecture-c4-architecture",
- "path": "skills/c4-architecture-c4-architecture",
+ "path": "skills\\c4-architecture-c4-architecture",
"category": "uncategorized",
"name": "c4-architecture-c4-architecture",
"description": "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "c4-code",
+ "path": "skills\\c4-code",
+ "category": "uncategorized",
+ "name": "c4-code",
+ "description": "Expert C4 Code-level documentation specialist. Analyzes code\ndirectories to create comprehensive C4 code-level documentation including\nfunction signatures, arguments, dependencies, and code structure. Use when\ndocumenting code at the lowest C4 level for individual directories and code\nmodules.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-component",
+ "path": "skills\\c4-component",
+ "category": "uncategorized",
+ "name": "c4-component",
+ "description": "Expert C4 Component-level documentation specialist. Synthesizes C4\nCode-level documentation into Component-level architecture, defining component\nboundaries, interfaces, and relationships. Creates component diagrams and\ndocumentation. Use when synthesizing code-level documentation into logical\ncomponents.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-container",
+ "path": "skills\\c4-container",
+ "category": "uncategorized",
+ "name": "c4-container",
+ "description": "Expert C4 Container-level documentation specialist. Synthesizes\nComponent-level documentation into Container-level architecture, mapping\ncomponents to deployment units, documenting container interfaces as APIs, and\ncreating container diagrams. Use when synthesizing components into deployment\ncontainers and documenting system deployment architecture.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-context",
+ "path": "skills\\c4-context",
+ "category": "uncategorized",
+ "name": "c4-context",
+ "description": "Expert C4 Context-level documentation specialist. Creates\nhigh-level system context diagrams, documents personas, user journeys, system\nfeatures, and external dependencies. Synthesizes container and component\ndocumentation with system documentation to create comprehensive context-level\narchitecture. Use when creating the highest-level C4 system context\ndocumentation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "cal-com-automation",
- "path": "skills/cal-com-automation",
+ "path": "skills\\cal-com-automation",
"category": "uncategorized",
"name": "cal-com-automation",
"description": "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.",
@@ -2098,7 +2134,7 @@
},
{
"id": "calc",
- "path": "skills/libreoffice/calc",
+ "path": "skills\\libreoffice\\calc",
"category": "libreoffice",
"name": "calc",
"description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
@@ -2107,7 +2143,7 @@
},
{
"id": "calendly-automation",
- "path": "skills/calendly-automation",
+ "path": "skills\\calendly-automation",
"category": "uncategorized",
"name": "calendly-automation",
"description": "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -2116,7 +2152,7 @@
},
{
"id": "canva-automation",
- "path": "skills/canva-automation",
+ "path": "skills\\canva-automation",
"category": "uncategorized",
"name": "canva-automation",
"description": "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.",
@@ -2125,16 +2161,25 @@
},
{
"id": "canvas-design",
- "path": "skills/canvas-design",
+ "path": "skills\\canvas-design",
"category": "uncategorized",
"name": "canvas-design",
"description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "carrier-relationship-management",
+ "path": "skills\\carrier-relationship-management",
+ "category": "uncategorized",
+ "name": "carrier-relationship-management",
+ "description": "Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting. Use when managing carriers, negotiating rates, evaluating carrier performance, or building freight strategies.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "cc-skill-backend-patterns",
- "path": "skills/cc-skill-backend-patterns",
+ "path": "skills\\cc-skill-backend-patterns",
"category": "uncategorized",
"name": "cc-skill-backend-patterns",
"description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
@@ -2143,7 +2188,7 @@
},
{
"id": "cc-skill-clickhouse-io",
- "path": "skills/cc-skill-clickhouse-io",
+ "path": "skills\\cc-skill-clickhouse-io",
"category": "uncategorized",
"name": "cc-skill-clickhouse-io",
"description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
@@ -2152,7 +2197,7 @@
},
{
"id": "cc-skill-coding-standards",
- "path": "skills/cc-skill-coding-standards",
+ "path": "skills\\cc-skill-coding-standards",
"category": "uncategorized",
"name": "cc-skill-coding-standards",
"description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
@@ -2161,7 +2206,7 @@
},
{
"id": "cc-skill-continuous-learning",
- "path": "skills/cc-skill-continuous-learning",
+ "path": "skills\\cc-skill-continuous-learning",
"category": "uncategorized",
"name": "cc-skill-continuous-learning",
"description": "Development skill from everything-claude-code",
@@ -2170,7 +2215,7 @@
},
{
"id": "cc-skill-frontend-patterns",
- "path": "skills/cc-skill-frontend-patterns",
+ "path": "skills\\cc-skill-frontend-patterns",
"category": "uncategorized",
"name": "cc-skill-frontend-patterns",
"description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
@@ -2179,7 +2224,7 @@
},
{
"id": "cc-skill-project-guidelines-example",
- "path": "skills/cc-skill-project-guidelines-example",
+ "path": "skills\\cc-skill-project-guidelines-example",
"category": "uncategorized",
"name": "cc-skill-project-guidelines-example",
"description": "Project Guidelines Skill (Example)",
@@ -2188,7 +2233,7 @@
},
{
"id": "cc-skill-security-review",
- "path": "skills/cc-skill-security-review",
+ "path": "skills\\cc-skill-security-review",
"category": "uncategorized",
"name": "cc-skill-security-review",
"description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...",
@@ -2197,7 +2242,7 @@
},
{
"id": "cc-skill-strategic-compact",
- "path": "skills/cc-skill-strategic-compact",
+ "path": "skills\\cc-skill-strategic-compact",
"category": "uncategorized",
"name": "cc-skill-strategic-compact",
"description": "Development skill from everything-claude-code",
@@ -2206,7 +2251,7 @@
},
{
"id": "cdk-patterns",
- "path": "skills/cdk-patterns",
+ "path": "skills\\cdk-patterns",
"category": "uncategorized",
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
@@ -2215,16 +2260,25 @@
},
{
"id": "changelog-automation",
- "path": "skills/changelog-automation",
+ "path": "skills\\changelog-automation",
"category": "uncategorized",
"name": "changelog-automation",
"description": "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "chrome-extension-developer",
+ "path": "skills\\chrome-extension-developer",
+ "category": "uncategorized",
+ "name": "chrome-extension-developer",
+ "description": "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "cicd-automation-workflow-automate",
- "path": "skills/cicd-automation-workflow-automate",
+ "path": "skills\\cicd-automation-workflow-automate",
"category": "uncategorized",
"name": "cicd-automation-workflow-automate",
"description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i...",
@@ -2233,7 +2287,7 @@
},
{
"id": "circleci-automation",
- "path": "skills/circleci-automation",
+ "path": "skills\\circleci-automation",
"category": "uncategorized",
"name": "circleci-automation",
"description": "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.",
@@ -2242,7 +2296,7 @@
},
{
"id": "clarity-gate",
- "path": "skills/clarity-gate",
+ "path": "skills\\clarity-gate",
"category": "uncategorized",
"name": "clarity-gate",
"description": "Pre-ingestion verification for epistemic quality in RAG systems with 9-point verification and Two-Round HITL workflow",
@@ -2251,7 +2305,7 @@
},
{
"id": "claude-ally-health",
- "path": "skills/claude-ally-health",
+ "path": "skills\\claude-ally-health",
"category": "uncategorized",
"name": "claude-ally-health",
"description": "A health assistant skill for medical information analysis, symptom tracking, and wellness guidance.",
@@ -2260,7 +2314,7 @@
},
{
"id": "claude-code-guide",
- "path": "skills/claude-code-guide",
+ "path": "skills\\claude-code-guide",
"category": "uncategorized",
"name": "claude-code-guide",
"description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit...",
@@ -2269,7 +2323,7 @@
},
{
"id": "claude-d3js-skill",
- "path": "skills/claude-d3js-skill",
+ "path": "skills\\claude-d3js-skill",
"category": "uncategorized",
"name": "claude-d3js-skill",
"description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...",
@@ -2278,7 +2332,7 @@
},
{
"id": "claude-scientific-skills",
- "path": "skills/claude-scientific-skills",
+ "path": "skills\\claude-scientific-skills",
"category": "uncategorized",
"name": "claude-scientific-skills",
"description": "Scientific research and analysis skills",
@@ -2287,7 +2341,7 @@
},
{
"id": "claude-speed-reader",
- "path": "skills/claude-speed-reader",
+ "path": "skills\\claude-speed-reader",
"category": "uncategorized",
"name": "claude-speed-reader",
"description": "-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting",
@@ -2296,7 +2350,7 @@
},
{
"id": "claude-win11-speckit-update-skill",
- "path": "skills/claude-win11-speckit-update-skill",
+ "path": "skills\\claude-win11-speckit-update-skill",
"category": "uncategorized",
"name": "claude-win11-speckit-update-skill",
"description": "Windows 11 system management",
@@ -2305,7 +2359,7 @@
},
{
"id": "clean-code",
- "path": "skills/clean-code",
+ "path": "skills\\clean-code",
"category": "uncategorized",
"name": "clean-code",
"description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...",
@@ -2314,7 +2368,7 @@
},
{
"id": "clerk-auth",
- "path": "skills/clerk-auth",
+ "path": "skills\\clerk-auth",
"category": "uncategorized",
"name": "clerk-auth",
"description": "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.",
@@ -2323,7 +2377,7 @@
},
{
"id": "clickup-automation",
- "path": "skills/clickup-automation",
+ "path": "skills\\clickup-automation",
"category": "uncategorized",
"name": "clickup-automation",
"description": "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -2332,7 +2386,7 @@
},
{
"id": "close-automation",
- "path": "skills/close-automation",
+ "path": "skills\\close-automation",
"category": "uncategorized",
"name": "close-automation",
"description": "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.",
@@ -2341,16 +2395,16 @@
},
{
"id": "cloud-architect",
- "path": "skills/cloud-architect",
+ "path": "skills\\cloud-architect",
"category": "uncategorized",
- "name": "Cloud Architect",
- "description": "- Working on cloud architect tasks or workflows - Needing guidance, best practices, or checklists for cloud architect",
+ "name": "cloud-architect",
+ "description": "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud\ninfrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost\noptimization, and modern architectural patterns. Masters serverless,\nmicroservices, security, compliance, and disaster recovery. Use PROACTIVELY\nfor cloud architecture, cost optimization, migration planning, or multi-cloud\nstrategies.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cloud-devops",
- "path": "skills/cloud-devops",
+ "path": "skills\\cloud-devops",
"category": "uncategorized",
"name": "cloud-devops",
"description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
@@ -2359,16 +2413,25 @@
},
{
"id": "cloud-penetration-testing",
- "path": "skills/cloud-penetration-testing",
+ "path": "skills\\cloud-penetration-testing",
"category": "uncategorized",
"name": "cloud-penetration-testing",
"description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "cloudflare-workers-expert",
+ "path": "skills\\cloudflare-workers-expert",
+ "category": "uncategorized",
+ "name": "cloudflare-workers-expert",
+ "description": "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "cloudformation-best-practices",
- "path": "skills/cloudformation-best-practices",
+ "path": "skills\\cloudformation-best-practices",
"category": "uncategorized",
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
@@ -2377,7 +2440,7 @@
},
{
"id": "coda-automation",
- "path": "skills/coda-automation",
+ "path": "skills\\coda-automation",
"category": "uncategorized",
"name": "coda-automation",
"description": "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.",
@@ -2386,7 +2449,7 @@
},
{
"id": "code-documentation-code-explain",
- "path": "skills/code-documentation-code-explain",
+ "path": "skills\\code-documentation-code-explain",
"category": "uncategorized",
"name": "code-documentation-code-explain",
"description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...",
@@ -2395,7 +2458,7 @@
},
{
"id": "code-documentation-doc-generate",
- "path": "skills/code-documentation-doc-generate",
+ "path": "skills\\code-documentation-doc-generate",
"category": "uncategorized",
"name": "code-documentation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
@@ -2404,7 +2467,7 @@
},
{
"id": "code-refactoring-context-restore",
- "path": "skills/code-refactoring-context-restore",
+ "path": "skills\\code-refactoring-context-restore",
"category": "uncategorized",
"name": "code-refactoring-context-restore",
"description": "Use when working with code refactoring context restore",
@@ -2413,7 +2476,7 @@
},
{
"id": "code-refactoring-refactor-clean",
- "path": "skills/code-refactoring-refactor-clean",
+ "path": "skills\\code-refactoring-refactor-clean",
"category": "uncategorized",
"name": "code-refactoring-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
@@ -2422,7 +2485,7 @@
},
{
"id": "code-refactoring-tech-debt",
- "path": "skills/code-refactoring-tech-debt",
+ "path": "skills\\code-refactoring-tech-debt",
"category": "uncategorized",
"name": "code-refactoring-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
@@ -2431,7 +2494,7 @@
},
{
"id": "code-review-ai-ai-review",
- "path": "skills/code-review-ai-ai-review",
+ "path": "skills\\code-review-ai-ai-review",
"category": "uncategorized",
"name": "code-review-ai-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
@@ -2440,7 +2503,7 @@
},
{
"id": "code-review-checklist",
- "path": "skills/code-review-checklist",
+ "path": "skills\\code-review-checklist",
"category": "uncategorized",
"name": "code-review-checklist",
"description": "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability",
@@ -2449,7 +2512,7 @@
},
{
"id": "code-review-excellence",
- "path": "skills/code-review-excellence",
+ "path": "skills\\code-review-excellence",
"category": "uncategorized",
"name": "code-review-excellence",
"description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...",
@@ -2458,7 +2521,7 @@
},
{
"id": "code-reviewer",
- "path": "skills/code-reviewer",
+ "path": "skills\\code-reviewer",
"category": "uncategorized",
"name": "code-reviewer",
"description": "Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.",
@@ -2467,7 +2530,7 @@
},
{
"id": "codebase-cleanup-deps-audit",
- "path": "skills/codebase-cleanup-deps-audit",
+ "path": "skills\\codebase-cleanup-deps-audit",
"category": "uncategorized",
"name": "codebase-cleanup-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
@@ -2476,7 +2539,7 @@
},
{
"id": "codebase-cleanup-refactor-clean",
- "path": "skills/codebase-cleanup-refactor-clean",
+ "path": "skills\\codebase-cleanup-refactor-clean",
"category": "uncategorized",
"name": "codebase-cleanup-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
@@ -2485,7 +2548,7 @@
},
{
"id": "codebase-cleanup-tech-debt",
- "path": "skills/codebase-cleanup-tech-debt",
+ "path": "skills\\codebase-cleanup-tech-debt",
"category": "uncategorized",
"name": "codebase-cleanup-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
@@ -2494,7 +2557,7 @@
},
{
"id": "codex-review",
- "path": "skills/codex-review",
+ "path": "skills\\codex-review",
"category": "uncategorized",
"name": "codex-review",
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI",
@@ -2503,7 +2566,7 @@
},
{
"id": "commit",
- "path": "skills/commit",
+ "path": "skills\\commit",
"category": "uncategorized",
"name": "commit",
"description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...",
@@ -2512,16 +2575,16 @@
},
{
"id": "competitive-landscape",
- "path": "skills/competitive-landscape",
+ "path": "skills\\competitive-landscape",
"category": "uncategorized",
- "name": "Competitive Landscape",
- "description": "Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.",
+ "name": "competitive-landscape",
+ "description": "This skill should be used when the user asks to \\\\\\\"analyze\ncompetitors\", \"assess competitive landscape\", \"identify differentiation\",\n\"evaluate market positioning\", \"apply Porter's Five Forces\", or requests\ncompetitive strategy analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "competitor-alternatives",
- "path": "skills/competitor-alternatives",
+ "path": "skills\\competitor-alternatives",
"category": "uncategorized",
"name": "competitor-alternatives",
"description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa...",
@@ -2530,7 +2593,7 @@
},
{
"id": "comprehensive-review-full-review",
- "path": "skills/comprehensive-review-full-review",
+ "path": "skills\\comprehensive-review-full-review",
"category": "uncategorized",
"name": "comprehensive-review-full-review",
"description": "Use when working with comprehensive review full review",
@@ -2539,7 +2602,7 @@
},
{
"id": "comprehensive-review-pr-enhance",
- "path": "skills/comprehensive-review-pr-enhance",
+ "path": "skills\\comprehensive-review-pr-enhance",
"category": "uncategorized",
"name": "comprehensive-review-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e...",
@@ -2548,7 +2611,7 @@
},
{
"id": "computer-use-agents",
- "path": "skills/computer-use-agents",
+ "path": "skills\\computer-use-agents",
"category": "uncategorized",
"name": "computer-use-agents",
"description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so...",
@@ -2557,7 +2620,7 @@
},
{
"id": "computer-vision-expert",
- "path": "skills/computer-vision-expert",
+ "path": "skills\\computer-vision-expert",
"category": "uncategorized",
"name": "computer-vision-expert",
"description": "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.",
@@ -2566,34 +2629,16 @@
},
{
"id": "concise-planning",
- "path": "skills/concise-planning",
+ "path": "skills\\concise-planning",
"category": "uncategorized",
"name": "concise-planning",
"description": "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "conductor-setup",
- "path": "skills/conductor-setup",
- "category": "uncategorized",
- "name": "Conductor Setup",
- "description": "Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "conductor-validator",
- "path": "skills/conductor-validator",
- "category": "uncategorized",
- "name": "Conductor Validator",
- "description": "ls -la conductor/",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "conductor-implement",
- "path": "skills/conductor-implement",
+ "path": "skills\\conductor-implement",
"category": "uncategorized",
"name": "conductor-implement",
"description": "Execute tasks from a track's implementation plan following TDD workflow",
@@ -2602,7 +2647,7 @@
},
{
"id": "conductor-manage",
- "path": "skills/conductor-manage",
+ "path": "skills\\conductor-manage",
"category": "uncategorized",
"name": "conductor-manage",
"description": "Manage track lifecycle: archive, restore, delete, rename, and cleanup",
@@ -2611,7 +2656,7 @@
},
{
"id": "conductor-new-track",
- "path": "skills/conductor-new-track",
+ "path": "skills\\conductor-new-track",
"category": "uncategorized",
"name": "conductor-new-track",
"description": "Create a new track with specification and phased implementation plan",
@@ -2620,43 +2665,52 @@
},
{
"id": "conductor-revert",
- "path": "skills/conductor-revert",
+ "path": "skills\\conductor-revert",
"category": "uncategorized",
"name": "conductor-revert",
"description": "Git-aware undo by logical work unit (track, phase, or task)",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "conductor-setup",
+ "path": "skills\\conductor-setup",
+ "category": "uncategorized",
+ "name": "conductor-setup",
+ "description": "Initialize project with Conductor artifacts (product definition,\ntech stack, workflow, style guides)\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "conductor-status",
- "path": "skills/conductor-status",
+ "path": "skills\\conductor-status",
"category": "uncategorized",
"name": "conductor-status",
"description": "Display project status, active tracks, and next actions",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "conductor-validator",
+ "path": "skills\\conductor-validator",
+ "category": "uncategorized",
+ "name": "conductor-validator",
+ "description": "Validates Conductor project artifacts for completeness,\nconsistency, and correctness. Use after setup, when diagnosing issues, or\nbefore implementation to verify project context.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "confluence-automation",
- "path": "skills/confluence-automation",
+ "path": "skills\\confluence-automation",
"category": "uncategorized",
"name": "confluence-automation",
"description": "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "content-marketer",
- "path": "skills/content-marketer",
- "category": "uncategorized",
- "name": "Content Marketer",
- "description": "- Working on content marketer tasks or workflows - Needing guidance, best practices, or checklists for content marketer",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "content-creator",
- "path": "skills/content-creator",
+ "path": "skills\\content-creator",
"category": "uncategorized",
"name": "content-creator",
"description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati...",
@@ -2664,26 +2718,17 @@
"source": "community"
},
{
- "id": "context-driven-development",
- "path": "skills/context-driven-development",
+ "id": "content-marketer",
+ "path": "skills\\content-marketer",
"category": "uncategorized",
- "name": "Context Driven Development",
- "description": "Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.",
+ "name": "content-marketer",
+ "description": "Elite content marketing strategist specializing in AI-powered\ncontent creation, omnichannel distribution, SEO optimization, and data-driven\nperformance marketing. Masters modern content tools, social media automation,\nand conversion optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive content marketing.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "context-manager",
- "path": "skills/context-manager",
- "category": "uncategorized",
- "name": "Context Manager",
- "description": "- Working on context manager tasks or workflows - Needing guidance, best practices, or checklists for context manager",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "context-compression",
- "path": "skills/context-compression",
+ "path": "skills\\context-compression",
"category": "uncategorized",
"name": "context-compression",
"description": "Design and evaluate compression strategies for long-running sessions",
@@ -2692,16 +2737,25 @@
},
{
"id": "context-degradation",
- "path": "skills/context-degradation",
+ "path": "skills\\context-degradation",
"category": "uncategorized",
"name": "context-degradation",
"description": "Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash",
"risk": "safe",
"source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation"
},
+ {
+ "id": "context-driven-development",
+ "path": "skills\\context-driven-development",
+ "category": "uncategorized",
+ "name": "context-driven-development",
+ "description": "Use this skill when working with Conductor's context-driven\ndevelopment methodology, managing project context artifacts, or understanding\nthe relationship between product.md, tech-stack.md, and workflow.md files.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "context-fundamentals",
- "path": "skills/context-fundamentals",
+ "path": "skills\\context-fundamentals",
"category": "uncategorized",
"name": "context-fundamentals",
"description": "Understand what context is, why it matters, and the anatomy of context in agent systems",
@@ -2710,7 +2764,7 @@
},
{
"id": "context-management-context-restore",
- "path": "skills/context-management-context-restore",
+ "path": "skills\\context-management-context-restore",
"category": "uncategorized",
"name": "context-management-context-restore",
"description": "Use when working with context management context restore",
@@ -2719,16 +2773,25 @@
},
{
"id": "context-management-context-save",
- "path": "skills/context-management-context-save",
+ "path": "skills\\context-management-context-save",
"category": "uncategorized",
"name": "context-management-context-save",
"description": "Use when working with context management context save",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "context-manager",
+ "path": "skills\\context-manager",
+ "category": "uncategorized",
+ "name": "context-manager",
+ "description": "Elite AI context engineering specialist mastering dynamic context\nmanagement, vector databases, knowledge graphs, and intelligent memory\nsystems. Orchestrates context across multi-agent workflows, enterprise AI\nsystems, and long-running projects with 2024/2025 best practices. Use\nPROACTIVELY for complex AI orchestration.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "context-optimization",
- "path": "skills/context-optimization",
+ "path": "skills\\context-optimization",
"category": "uncategorized",
"name": "context-optimization",
"description": "Apply compaction, masking, and caching strategies",
@@ -2737,7 +2800,7 @@
},
{
"id": "context-window-management",
- "path": "skills/context-window-management",
+ "path": "skills\\context-window-management",
"category": "uncategorized",
"name": "context-window-management",
"description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...",
@@ -2746,7 +2809,7 @@
},
{
"id": "context7-auto-research",
- "path": "skills/context7-auto-research",
+ "path": "skills\\context7-auto-research",
"category": "uncategorized",
"name": "context7-auto-research",
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API",
@@ -2755,7 +2818,7 @@
},
{
"id": "conversation-memory",
- "path": "skills/conversation-memory",
+ "path": "skills\\conversation-memory",
"category": "uncategorized",
"name": "conversation-memory",
"description": "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.",
@@ -2764,7 +2827,7 @@
},
{
"id": "convertkit-automation",
- "path": "skills/convertkit-automation",
+ "path": "skills\\convertkit-automation",
"category": "uncategorized",
"name": "convertkit-automation",
"description": "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.",
@@ -2773,7 +2836,7 @@
},
{
"id": "copilot-sdk",
- "path": "skills/copilot-sdk",
+ "path": "skills\\copilot-sdk",
"category": "uncategorized",
"name": "copilot-sdk",
"description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen...",
@@ -2782,7 +2845,7 @@
},
{
"id": "copy-editing",
- "path": "skills/copy-editing",
+ "path": "skills\\copy-editing",
"category": "uncategorized",
"name": "copy-editing",
"description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ...",
@@ -2791,16 +2854,16 @@
},
{
"id": "copywriting",
- "path": "skills/copywriting",
+ "path": "skills\\copywriting",
"category": "uncategorized",
- "name": "Copywriting",
- "description": "Produce **clear, credible, and action-oriented marketing copy** that aligns with user intent and business goals.",
+ "name": "copywriting",
+ "description": "Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "core-components",
- "path": "skills/core-components",
+ "path": "skills\\core-components",
"category": "uncategorized",
"name": "core-components",
"description": "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.",
@@ -2809,7 +2872,7 @@
},
{
"id": "cost-optimization",
- "path": "skills/cost-optimization",
+ "path": "skills\\cost-optimization",
"category": "uncategorized",
"name": "cost-optimization",
"description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...",
@@ -2818,16 +2881,16 @@
},
{
"id": "cpp-pro",
- "path": "skills/cpp-pro",
+ "path": "skills\\cpp-pro",
"category": "uncategorized",
- "name": "Cpp Pro",
- "description": "- Working on cpp pro tasks or workflows - Needing guidance, best practices, or checklists for cpp pro",
+ "name": "cpp-pro",
+ "description": "Write idiomatic C++ code with modern features, RAII, smart\npointers, and STL algorithms. Handles templates, move semantics, and\nperformance optimization. Use PROACTIVELY for C++ refactoring, memory safety,\nor complex C++ patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cqrs-implementation",
- "path": "skills/cqrs-implementation",
+ "path": "skills\\cqrs-implementation",
"category": "uncategorized",
"name": "cqrs-implementation",
"description": "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.",
@@ -2836,7 +2899,7 @@
},
{
"id": "create-pr",
- "path": "skills/create-pr",
+ "path": "skills\\create-pr",
"category": "uncategorized",
"name": "create-pr",
"description": "Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.",
@@ -2845,7 +2908,7 @@
},
{
"id": "crewai",
- "path": "skills/crewai",
+ "path": "skills\\crewai",
"category": "uncategorized",
"name": "crewai",
"description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s...",
@@ -2854,25 +2917,25 @@
},
{
"id": "crypto-bd-agent",
- "path": "skills/crypto-bd-agent",
+ "path": "skills\\crypto-bd-agent",
"category": "uncategorized",
- "name": "Crypto Bd Agent",
- "description": "> Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "crypto-bd-agent",
+ "description": "Autonomous crypto business development patterns \u2014 multi-chain token discovery, 100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain identity, LLM cascade routing, and pipeline automation for CEX/DEX listing acquisition. Use when building AI agents for crypto BD, token evaluation, exchange listing outreach, or autonomous commerce with payment protocols.\n",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "csharp-pro",
- "path": "skills/csharp-pro",
+ "path": "skills\\csharp-pro",
"category": "uncategorized",
- "name": "Csharp Pro",
- "description": "- Working on csharp pro tasks or workflows - Needing guidance, best practices, or checklists for csharp pro",
+ "name": "csharp-pro",
+ "description": "Write modern C# code with advanced features like records, pattern\nmatching, and async/await. Optimizes .NET applications, implements enterprise\npatterns, and ensures comprehensive testing. Use PROACTIVELY for C#\nrefactoring, performance optimization, or complex .NET solutions.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "culture-index",
- "path": "skills/culture-index",
+ "path": "skills\\culture-index",
"category": "uncategorized",
"name": "culture-index",
"description": "Index and search culture documentation",
@@ -2881,16 +2944,25 @@
},
{
"id": "customer-support",
- "path": "skills/customer-support",
+ "path": "skills\\customer-support",
"category": "uncategorized",
- "name": "Customer Support",
- "description": "- Working on customer support tasks or workflows - Needing guidance, best practices, or checklists for customer support",
+ "name": "customer-support",
+ "description": "Elite AI-powered customer support specialist mastering\nconversational AI, automated ticketing, sentiment analysis, and omnichannel\nsupport experiences. Integrates modern support tools, chatbot platforms, and\nCX optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive customer experience management.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "customs-trade-compliance",
+ "path": "skills\\customs-trade-compliance",
+ "category": "uncategorized",
+ "name": "customs-trade-compliance",
+ "description": "Codified expertise for customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilisation, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimisation.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
},
{
"id": "daily-news-report",
- "path": "skills/daily-news-report",
+ "path": "skills\\daily-news-report",
"category": "uncategorized",
"name": "daily-news-report",
"description": "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.",
@@ -2899,25 +2971,16 @@
},
{
"id": "data-engineer",
- "path": "skills/data-engineer",
+ "path": "skills\\data-engineer",
"category": "uncategorized",
- "name": "Data Engineer",
- "description": "You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.",
+ "name": "data-engineer",
+ "description": "Build scalable data pipelines, modern data warehouses, and\nreal-time streaming architectures. Implements Apache Spark, dbt, Airflow, and\ncloud-native data platforms. Use PROACTIVELY for data pipeline design,\nanalytics infrastructure, or modern data stack implementation.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "data-scientist",
- "path": "skills/data-scientist",
- "category": "uncategorized",
- "name": "Data Scientist",
- "description": "- Working on data scientist tasks or workflows - Needing guidance, best practices, or checklists for data scientist",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-engineering-data-driven-feature",
- "path": "skills/data-engineering-data-driven-feature",
+ "path": "skills\\data-engineering-data-driven-feature",
"category": "uncategorized",
"name": "data-engineering-data-driven-feature",
"description": "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.",
@@ -2926,7 +2989,7 @@
},
{
"id": "data-engineering-data-pipeline",
- "path": "skills/data-engineering-data-pipeline",
+ "path": "skills\\data-engineering-data-pipeline",
"category": "uncategorized",
"name": "data-engineering-data-pipeline",
"description": "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.",
@@ -2935,16 +2998,25 @@
},
{
"id": "data-quality-frameworks",
- "path": "skills/data-quality-frameworks",
+ "path": "skills\\data-quality-frameworks",
"category": "uncategorized",
"name": "data-quality-frameworks",
"description": "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "data-scientist",
+ "path": "skills\\data-scientist",
+ "category": "uncategorized",
+ "name": "data-scientist",
+ "description": "Expert data scientist for advanced analytics, machine learning, and\nstatistical modeling. Handles complex data analysis, predictive modeling, and\nbusiness intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,\nstatistical analysis, and data-driven insights.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "data-storytelling",
- "path": "skills/data-storytelling",
+ "path": "skills\\data-storytelling",
"category": "uncategorized",
"name": "data-storytelling",
"description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present...",
@@ -2953,7 +3025,7 @@
},
{
"id": "data-structure-protocol",
- "path": "skills/data-structure-protocol",
+ "path": "skills\\data-structure-protocol",
"category": "uncategorized",
"name": "data-structure-protocol",
"description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
@@ -2962,7 +3034,7 @@
},
{
"id": "database",
- "path": "skills/database",
+ "path": "skills\\database",
"category": "uncategorized",
"name": "database",
"description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
@@ -2971,34 +3043,25 @@
},
{
"id": "database-admin",
- "path": "skills/database-admin",
+ "path": "skills\\database-admin",
"category": "uncategorized",
- "name": "Database Admin",
- "description": "- Working on database admin tasks or workflows - Needing guidance, best practices, or checklists for database admin",
+ "name": "database-admin",
+ "description": "Expert database administrator specializing in modern cloud\ndatabases, automation, and reliability engineering. Masters AWS/Azure/GCP\ndatabase services, Infrastructure as Code, high availability, disaster\nrecovery, performance optimization, and compliance. Handles multi-cloud\nstrategies, container databases, and cost optimization. Use PROACTIVELY for\ndatabase architecture, operations, or reliability engineering.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-architect",
- "path": "skills/database-architect",
+ "path": "skills\\database-architect",
"category": "uncategorized",
- "name": "Database Architect",
- "description": "You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.",
+ "name": "database-architect",
+ "description": "Expert database architect specializing in data layer design from\nscratch, technology selection, schema modeling, and scalable database\narchitectures. Masters SQL/NoSQL/TimeSeries database selection, normalization\nstrategies, migration planning, and performance-first design. Handles both\ngreenfield architectures and re-architecture of existing systems. Use\nPROACTIVELY for database architecture, technology selection, or data modeling\ndecisions.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "database-optimizer",
- "path": "skills/database-optimizer",
- "category": "uncategorized",
- "name": "Database Optimizer",
- "description": "- Working on database optimizer tasks or workflows - Needing guidance, best practices, or checklists for database optimizer",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-cloud-optimization-cost-optimize",
- "path": "skills/database-cloud-optimization-cost-optimize",
+ "path": "skills\\database-cloud-optimization-cost-optimize",
"category": "uncategorized",
"name": "database-cloud-optimization-cost-optimize",
"description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ...",
@@ -3007,7 +3070,7 @@
},
{
"id": "database-design",
- "path": "skills/database-design",
+ "path": "skills\\database-design",
"category": "uncategorized",
"name": "database-design",
"description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
@@ -3016,7 +3079,7 @@
},
{
"id": "database-migration",
- "path": "skills/database-migration",
+ "path": "skills\\database-migration",
"category": "uncategorized",
"name": "database-migration",
"description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...",
@@ -3025,7 +3088,7 @@
},
{
"id": "database-migrations-migration-observability",
- "path": "skills/database-migrations-migration-observability",
+ "path": "skills\\database-migrations-migration-observability",
"category": "uncategorized",
"name": "database-migrations-migration-observability",
"description": "Migration monitoring, CDC, and observability infrastructure",
@@ -3034,16 +3097,25 @@
},
{
"id": "database-migrations-sql-migrations",
- "path": "skills/database-migrations-sql-migrations",
+ "path": "skills\\database-migrations-sql-migrations",
"category": "uncategorized",
"name": "database-migrations-sql-migrations",
"description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "database-optimizer",
+ "path": "skills\\database-optimizer",
+ "category": "uncategorized",
+ "name": "database-optimizer",
+ "description": "Expert database optimizer specializing in modern performance\ntuning, query optimization, and scalable architectures. Masters advanced\nindexing, N+1 resolution, multi-tier caching, partitioning strategies, and\ncloud database optimization. Handles complex query analysis, migration\nstrategies, and performance monitoring. Use PROACTIVELY for database\noptimization, performance issues, or scalability challenges.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "datadog-automation",
- "path": "skills/datadog-automation",
+ "path": "skills\\datadog-automation",
"category": "uncategorized",
"name": "datadog-automation",
"description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
@@ -3052,7 +3124,7 @@
},
{
"id": "dbos-golang",
- "path": "skills/dbos-golang",
+ "path": "skills\\dbos-golang",
"category": "uncategorized",
"name": "dbos-golang",
"description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie...",
@@ -3061,7 +3133,7 @@
},
{
"id": "dbos-python",
- "path": "skills/dbos-python",
+ "path": "skills\\dbos-python",
"category": "uncategorized",
"name": "dbos-python",
"description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC...",
@@ -3070,7 +3142,7 @@
},
{
"id": "dbos-typescript",
- "path": "skills/dbos-typescript",
+ "path": "skills\\dbos-typescript",
"category": "uncategorized",
"name": "dbos-typescript",
"description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi...",
@@ -3079,7 +3151,7 @@
},
{
"id": "dbt-transformation-patterns",
- "path": "skills/dbt-transformation-patterns",
+ "path": "skills\\dbt-transformation-patterns",
"category": "uncategorized",
"name": "dbt-transformation-patterns",
"description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ...",
@@ -3088,7 +3160,7 @@
},
{
"id": "ddd-context-mapping",
- "path": "skills/ddd-context-mapping",
+ "path": "skills\\ddd-context-mapping",
"category": "uncategorized",
"name": "ddd-context-mapping",
"description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
@@ -3097,7 +3169,7 @@
},
{
"id": "ddd-strategic-design",
- "path": "skills/ddd-strategic-design",
+ "path": "skills\\ddd-strategic-design",
"category": "uncategorized",
"name": "ddd-strategic-design",
"description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
@@ -3106,7 +3178,7 @@
},
{
"id": "ddd-tactical-patterns",
- "path": "skills/ddd-tactical-patterns",
+ "path": "skills\\ddd-tactical-patterns",
"category": "uncategorized",
"name": "ddd-tactical-patterns",
"description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
@@ -3115,16 +3187,16 @@
},
{
"id": "debugger",
- "path": "skills/debugger",
+ "path": "skills\\debugger",
"category": "uncategorized",
- "name": "Debugger",
- "description": "- Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger",
+ "name": "debugger",
+ "description": "Debugging specialist for errors, test failures, and unexpected\nbehavior. Use proactively when encountering any issues.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "debugging-strategies",
- "path": "skills/debugging-strategies",
+ "path": "skills\\debugging-strategies",
"category": "uncategorized",
"name": "debugging-strategies",
"description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss...",
@@ -3133,7 +3205,7 @@
},
{
"id": "debugging-toolkit-smart-debug",
- "path": "skills/debugging-toolkit-smart-debug",
+ "path": "skills\\debugging-toolkit-smart-debug",
"category": "uncategorized",
"name": "debugging-toolkit-smart-debug",
"description": "Use when working with debugging toolkit smart debug",
@@ -3142,7 +3214,7 @@
},
{
"id": "deep-research",
- "path": "skills/deep-research",
+ "path": "skills\\deep-research",
"category": "uncategorized",
"name": "deep-research",
"description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ...",
@@ -3151,7 +3223,7 @@
},
{
"id": "defi-protocol-templates",
- "path": "skills/defi-protocol-templates",
+ "path": "skills\\defi-protocol-templates",
"category": "uncategorized",
"name": "defi-protocol-templates",
"description": "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.",
@@ -3160,7 +3232,7 @@
},
{
"id": "dependency-management-deps-audit",
- "path": "skills/dependency-management-deps-audit",
+ "path": "skills\\dependency-management-deps-audit",
"category": "uncategorized",
"name": "dependency-management-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
@@ -3169,7 +3241,7 @@
},
{
"id": "dependency-upgrade",
- "path": "skills/dependency-upgrade",
+ "path": "skills\\dependency-upgrade",
"category": "uncategorized",
"name": "dependency-upgrade",
"description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...",
@@ -3178,16 +3250,16 @@
},
{
"id": "deployment-engineer",
- "path": "skills/deployment-engineer",
+ "path": "skills\\deployment-engineer",
"category": "uncategorized",
- "name": "Deployment Engineer",
- "description": "You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.",
+ "name": "deployment-engineer",
+ "description": "Expert deployment engineer specializing in modern CI/CD pipelines,\nGitOps workflows, and advanced deployment automation. Masters GitHub Actions,\nArgoCD/Flux, progressive delivery, container security, and platform\nengineering. Handles zero-downtime deployments, security scanning, and\ndeveloper experience optimization. Use PROACTIVELY for CI/CD design, GitOps\nimplementation, or deployment automation.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deployment-pipeline-design",
- "path": "skills/deployment-pipeline-design",
+ "path": "skills\\deployment-pipeline-design",
"category": "uncategorized",
"name": "deployment-pipeline-design",
"description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi...",
@@ -3196,7 +3268,7 @@
},
{
"id": "deployment-procedures",
- "path": "skills/deployment-procedures",
+ "path": "skills\\deployment-procedures",
"category": "uncategorized",
"name": "deployment-procedures",
"description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.",
@@ -3205,7 +3277,7 @@
},
{
"id": "deployment-validation-config-validate",
- "path": "skills/deployment-validation-config-validate",
+ "path": "skills\\deployment-validation-config-validate",
"category": "uncategorized",
"name": "deployment-validation-config-validate",
"description": "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat",
@@ -3214,7 +3286,7 @@
},
{
"id": "design-md",
- "path": "skills/design-md",
+ "path": "skills\\design-md",
"category": "uncategorized",
"name": "design-md",
"description": "Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files",
@@ -3223,7 +3295,7 @@
},
{
"id": "design-orchestration",
- "path": "skills/design-orchestration",
+ "path": "skills\\design-orchestration",
"category": "uncategorized",
"name": "design-orchestration",
"description": "Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.",
@@ -3232,7 +3304,7 @@
},
{
"id": "development",
- "path": "skills/development",
+ "path": "skills\\development",
"category": "uncategorized",
"name": "development",
"description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
@@ -3241,16 +3313,16 @@
},
{
"id": "devops-troubleshooter",
- "path": "skills/devops-troubleshooter",
+ "path": "skills\\devops-troubleshooter",
"category": "uncategorized",
- "name": "Devops Troubleshooter",
- "description": "- Working on devops troubleshooter tasks or workflows - Needing guidance, best practices, or checklists for devops troubleshooter",
+ "name": "devops-troubleshooter",
+ "description": "Expert DevOps troubleshooter specializing in rapid incident\nresponse, advanced debugging, and modern observability. Masters log analysis,\ndistributed tracing, Kubernetes debugging, performance optimization, and root\ncause analysis. Handles production outages, system reliability, and preventive\nmonitoring. Use PROACTIVELY for debugging, incident response, or system\ntroubleshooting.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "discord-automation",
- "path": "skills/discord-automation",
+ "path": "skills\\discord-automation",
"category": "uncategorized",
"name": "discord-automation",
"description": "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.",
@@ -3259,7 +3331,7 @@
},
{
"id": "discord-bot-architect",
- "path": "skills/discord-bot-architect",
+ "path": "skills\\discord-bot-architect",
"category": "uncategorized",
"name": "discord-bot-architect",
"description": "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.",
@@ -3268,7 +3340,7 @@
},
{
"id": "dispatching-parallel-agents",
- "path": "skills/dispatching-parallel-agents",
+ "path": "skills\\dispatching-parallel-agents",
"category": "uncategorized",
"name": "dispatching-parallel-agents",
"description": "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies",
@@ -3277,7 +3349,7 @@
},
{
"id": "distributed-debugging-debug-trace",
- "path": "skills/distributed-debugging-debug-trace",
+ "path": "skills\\distributed-debugging-debug-trace",
"category": "uncategorized",
"name": "distributed-debugging-debug-trace",
"description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an...",
@@ -3286,7 +3358,7 @@
},
{
"id": "distributed-tracing",
- "path": "skills/distributed-tracing",
+ "path": "skills\\distributed-tracing",
"category": "uncategorized",
"name": "distributed-tracing",
"description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem...",
@@ -3295,16 +3367,16 @@
},
{
"id": "django-pro",
- "path": "skills/django-pro",
+ "path": "skills\\django-pro",
"category": "uncategorized",
- "name": "Django Pro",
- "description": "- Working on django pro tasks or workflows - Needing guidance, best practices, or checklists for django pro",
+ "name": "django-pro",
+ "description": "Master Django 5.x with async views, DRF, Celery, and Django\nChannels. Build scalable web applications with proper architecture, testing,\nand deployment. Use PROACTIVELY for Django development, ORM optimization, or\ncomplex Django patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "doc-coauthoring",
- "path": "skills/doc-coauthoring",
+ "path": "skills\\doc-coauthoring",
"category": "uncategorized",
"name": "doc-coauthoring",
"description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ...",
@@ -3313,7 +3385,7 @@
},
{
"id": "docker-expert",
- "path": "skills/docker-expert",
+ "path": "skills\\docker-expert",
"category": "uncategorized",
"name": "docker-expert",
"description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f...",
@@ -3322,16 +3394,16 @@
},
{
"id": "docs-architect",
- "path": "skills/docs-architect",
+ "path": "skills\\docs-architect",
"category": "uncategorized",
- "name": "Docs Architect",
- "description": "- Working on docs architect tasks or workflows - Needing guidance, best practices, or checklists for docs architect",
+ "name": "docs-architect",
+ "description": "Creates comprehensive technical documentation from existing\ncodebases. Analyzes architecture, design patterns, and implementation details\nto produce long-form technical manuals and ebooks. Use PROACTIVELY for system\ndocumentation, architecture guides, or technical deep-dives.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "documentation",
- "path": "skills/documentation",
+ "path": "skills\\documentation",
"category": "uncategorized",
"name": "documentation",
"description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
@@ -3340,7 +3412,7 @@
},
{
"id": "documentation-generation-doc-generate",
- "path": "skills/documentation-generation-doc-generate",
+ "path": "skills\\documentation-generation-doc-generate",
"category": "uncategorized",
"name": "documentation-generation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
@@ -3349,7 +3421,7 @@
},
{
"id": "documentation-templates",
- "path": "skills/documentation-templates",
+ "path": "skills\\documentation-templates",
"category": "uncategorized",
"name": "documentation-templates",
"description": "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.",
@@ -3358,7 +3430,7 @@
},
{
"id": "docusign-automation",
- "path": "skills/docusign-automation",
+ "path": "skills\\docusign-automation",
"category": "uncategorized",
"name": "docusign-automation",
"description": "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.",
@@ -3367,7 +3439,7 @@
},
{
"id": "docx-official",
- "path": "skills/docx-official",
+ "path": "skills\\docx-official",
"category": "uncategorized",
"name": "docx-official",
"description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document...",
@@ -3376,7 +3448,7 @@
},
{
"id": "domain-driven-design",
- "path": "skills/domain-driven-design",
+ "path": "skills\\domain-driven-design",
"category": "uncategorized",
"name": "domain-driven-design",
"description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
@@ -3385,16 +3457,16 @@
},
{
"id": "dotnet-architect",
- "path": "skills/dotnet-architect",
+ "path": "skills\\dotnet-architect",
"category": "uncategorized",
- "name": "Dotnet Architect",
- "description": "- Working on dotnet architect tasks or workflows - Needing guidance, best practices, or checklists for dotnet architect",
+ "name": "dotnet-architect",
+ "description": "Expert .NET backend architect specializing in C#, ASP.NET Core,\nEntity Framework, Dapper, and enterprise application patterns. Masters\nasync/await, dependency injection, caching strategies, and performance\noptimization. Use PROACTIVELY for .NET API development, code review, or\narchitecture decisions.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dotnet-backend",
- "path": "skills/dotnet-backend",
+ "path": "skills\\dotnet-backend",
"category": "uncategorized",
"name": "dotnet-backend",
"description": "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.",
@@ -3403,7 +3475,7 @@
},
{
"id": "dotnet-backend-patterns",
- "path": "skills/dotnet-backend-patterns",
+ "path": "skills\\dotnet-backend-patterns",
"category": "uncategorized",
"name": "dotnet-backend-patterns",
"description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...",
@@ -3412,7 +3484,7 @@
},
{
"id": "draw",
- "path": "skills/libreoffice/draw",
+ "path": "skills\\libreoffice\\draw",
"category": "libreoffice",
"name": "draw",
"description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
@@ -3421,7 +3493,7 @@
},
{
"id": "dropbox-automation",
- "path": "skills/dropbox-automation",
+ "path": "skills\\dropbox-automation",
"category": "uncategorized",
"name": "dropbox-automation",
"description": "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -3430,16 +3502,16 @@
},
{
"id": "dx-optimizer",
- "path": "skills/dx-optimizer",
+ "path": "skills\\dx-optimizer",
"category": "uncategorized",
- "name": "Dx Optimizer",
- "description": "- Working on dx optimizer tasks or workflows - Needing guidance, best practices, or checklists for dx optimizer",
+ "name": "dx-optimizer",
+ "description": "Developer Experience specialist. Improves tooling, setup, and\nworkflows. Use PROACTIVELY when setting up new projects, after team feedback,\nor when development friction is noticed.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "e2e-testing",
- "path": "skills/e2e-testing",
+ "path": "skills\\e2e-testing",
"category": "uncategorized",
"name": "e2e-testing",
"description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
@@ -3448,7 +3520,7 @@
},
{
"id": "e2e-testing-patterns",
- "path": "skills/e2e-testing-patterns",
+ "path": "skills\\e2e-testing-patterns",
"category": "uncategorized",
"name": "e2e-testing-patterns",
"description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...",
@@ -3457,16 +3529,16 @@
},
{
"id": "elixir-pro",
- "path": "skills/elixir-pro",
+ "path": "skills\\elixir-pro",
"category": "uncategorized",
- "name": "Elixir Pro",
- "description": "- Working on elixir pro tasks or workflows - Needing guidance, best practices, or checklists for elixir pro",
+ "name": "elixir-pro",
+ "description": "Write idiomatic Elixir code with OTP patterns, supervision trees,\nand Phoenix LiveView. Masters concurrency, fault tolerance, and distributed\nsystems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM\noptimizations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "email-sequence",
- "path": "skills/email-sequence",
+ "path": "skills\\email-sequence",
"category": "uncategorized",
"name": "email-sequence",
"description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa...",
@@ -3475,7 +3547,7 @@
},
{
"id": "email-systems",
- "path": "skills/email-systems",
+ "path": "skills\\email-systems",
"category": "uncategorized",
"name": "email-systems",
"description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov...",
@@ -3484,7 +3556,7 @@
},
{
"id": "embedding-strategies",
- "path": "skills/embedding-strategies",
+ "path": "skills\\embedding-strategies",
"category": "uncategorized",
"name": "embedding-strategies",
"description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom...",
@@ -3493,34 +3565,34 @@
},
{
"id": "employment-contract-templates",
- "path": "skills/employment-contract-templates",
+ "path": "skills\\employment-contract-templates",
"category": "uncategorized",
"name": "employment-contract-templates",
"description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "energy-procurement",
+ "path": "skills\\energy-procurement",
+ "category": "uncategorized",
+ "name": "energy-procurement",
+ "description": "Codified expertise for electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimising tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "environment-setup-guide",
- "path": "skills/environment-setup-guide",
+ "path": "skills\\environment-setup-guide",
"category": "uncategorized",
"name": "environment-setup-guide",
"description": "Guide developers through setting up development environments with proper tools, dependencies, and configurations",
"risk": "unknown",
"source": "community"
},
- {
- "id": "error-detective",
- "path": "skills/error-detective",
- "category": "uncategorized",
- "name": "Error Detective",
- "description": "- Working on error detective tasks or workflows - Needing guidance, best practices, or checklists for error detective",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "error-debugging-error-analysis",
- "path": "skills/error-debugging-error-analysis",
+ "path": "skills\\error-debugging-error-analysis",
"category": "uncategorized",
"name": "error-debugging-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
@@ -3529,7 +3601,7 @@
},
{
"id": "error-debugging-error-trace",
- "path": "skills/error-debugging-error-trace",
+ "path": "skills\\error-debugging-error-trace",
"category": "uncategorized",
"name": "error-debugging-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi...",
@@ -3538,16 +3610,25 @@
},
{
"id": "error-debugging-multi-agent-review",
- "path": "skills/error-debugging-multi-agent-review",
+ "path": "skills\\error-debugging-multi-agent-review",
"category": "uncategorized",
"name": "error-debugging-multi-agent-review",
"description": "Use when working with error debugging multi agent review",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "error-detective",
+ "path": "skills\\error-detective",
+ "category": "uncategorized",
+ "name": "error-detective",
+ "description": "Search logs and codebases for error patterns, stack traces, and\nanomalies. Correlates errors across systems and identifies root causes. Use\nPROACTIVELY when debugging issues, analyzing logs, or investigating production\nerrors.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "error-diagnostics-error-analysis",
- "path": "skills/error-diagnostics-error-analysis",
+ "path": "skills\\error-diagnostics-error-analysis",
"category": "uncategorized",
"name": "error-diagnostics-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
@@ -3556,7 +3637,7 @@
},
{
"id": "error-diagnostics-error-trace",
- "path": "skills/error-diagnostics-error-trace",
+ "path": "skills\\error-diagnostics-error-trace",
"category": "uncategorized",
"name": "error-diagnostics-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,",
@@ -3565,7 +3646,7 @@
},
{
"id": "error-diagnostics-smart-debug",
- "path": "skills/error-diagnostics-smart-debug",
+ "path": "skills\\error-diagnostics-smart-debug",
"category": "uncategorized",
"name": "error-diagnostics-smart-debug",
"description": "Use when working with error diagnostics smart debug",
@@ -3574,7 +3655,7 @@
},
{
"id": "error-handling-patterns",
- "path": "skills/error-handling-patterns",
+ "path": "skills\\error-handling-patterns",
"category": "uncategorized",
"name": "error-handling-patterns",
"description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling...",
@@ -3583,7 +3664,7 @@
},
{
"id": "ethical-hacking-methodology",
- "path": "skills/ethical-hacking-methodology",
+ "path": "skills\\ethical-hacking-methodology",
"category": "uncategorized",
"name": "ethical-hacking-methodology",
"description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ...",
@@ -3592,7 +3673,7 @@
},
{
"id": "evaluation",
- "path": "skills/evaluation",
+ "path": "skills\\evaluation",
"category": "uncategorized",
"name": "evaluation",
"description": "Build evaluation frameworks for agent systems",
@@ -3601,7 +3682,7 @@
},
{
"id": "event-sourcing-architect",
- "path": "skills/event-sourcing-architect",
+ "path": "skills\\event-sourcing-architect",
"category": "uncategorized",
"name": "event-sourcing-architect",
"description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...",
@@ -3610,7 +3691,7 @@
},
{
"id": "event-store-design",
- "path": "skills/event-store-design",
+ "path": "skills\\event-store-design",
"category": "uncategorized",
"name": "event-store-design",
"description": "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.",
@@ -3619,7 +3700,7 @@
},
{
"id": "exa-search",
- "path": "skills/exa-search",
+ "path": "skills\\exa-search",
"category": "uncategorized",
"name": "exa-search",
"description": "Semantic search, similar content discovery, and structured research using Exa API",
@@ -3628,7 +3709,7 @@
},
{
"id": "executing-plans",
- "path": "skills/executing-plans",
+ "path": "skills\\executing-plans",
"category": "uncategorized",
"name": "executing-plans",
"description": "Use when you have a written implementation plan to execute in a separate session with review checkpoints",
@@ -3637,7 +3718,7 @@
},
{
"id": "expo-deployment",
- "path": "skills/expo-deployment",
+ "path": "skills\\expo-deployment",
"category": "uncategorized",
"name": "expo-deployment",
"description": "Deploy Expo apps to production",
@@ -3646,7 +3727,7 @@
},
{
"id": "fal-audio",
- "path": "skills/fal-audio",
+ "path": "skills\\fal-audio",
"category": "uncategorized",
"name": "fal-audio",
"description": "Text-to-speech and speech-to-text using fal.ai audio models",
@@ -3655,7 +3736,7 @@
},
{
"id": "fal-generate",
- "path": "skills/fal-generate",
+ "path": "skills\\fal-generate",
"category": "uncategorized",
"name": "fal-generate",
"description": "Generate images and videos using fal.ai AI models",
@@ -3664,7 +3745,7 @@
},
{
"id": "fal-image-edit",
- "path": "skills/fal-image-edit",
+ "path": "skills\\fal-image-edit",
"category": "uncategorized",
"name": "fal-image-edit",
"description": "AI-powered image editing with style transfer and object removal",
@@ -3673,7 +3754,7 @@
},
{
"id": "fal-platform",
- "path": "skills/fal-platform",
+ "path": "skills\\fal-platform",
"category": "uncategorized",
"name": "fal-platform",
"description": "Platform APIs for model management, pricing, and usage tracking",
@@ -3682,7 +3763,7 @@
},
{
"id": "fal-upscale",
- "path": "skills/fal-upscale",
+ "path": "skills\\fal-upscale",
"category": "uncategorized",
"name": "fal-upscale",
"description": "Upscale and enhance image and video resolution using AI",
@@ -3691,7 +3772,7 @@
},
{
"id": "fal-workflow",
- "path": "skills/fal-workflow",
+ "path": "skills\\fal-workflow",
"category": "uncategorized",
"name": "fal-workflow",
"description": "Generate workflow JSON files for chaining AI models",
@@ -3700,16 +3781,16 @@
},
{
"id": "fastapi-pro",
- "path": "skills/fastapi-pro",
+ "path": "skills\\fastapi-pro",
"category": "uncategorized",
- "name": "Fastapi Pro",
- "description": "- Working on fastapi pro tasks or workflows - Needing guidance, best practices, or checklists for fastapi pro",
+ "name": "fastapi-pro",
+ "description": "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and\nPydantic V2. Master microservices, WebSockets, and modern Python async\npatterns. Use PROACTIVELY for FastAPI development, async optimization, or API\narchitecture.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fastapi-router-py",
- "path": "skills/fastapi-router-py",
+ "path": "skills\\fastapi-router-py",
"category": "uncategorized",
"name": "fastapi-router-py",
"description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add...",
@@ -3718,7 +3799,7 @@
},
{
"id": "fastapi-templates",
- "path": "skills/fastapi-templates",
+ "path": "skills\\fastapi-templates",
"category": "uncategorized",
"name": "fastapi-templates",
"description": "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.",
@@ -3727,7 +3808,7 @@
},
{
"id": "ffuf-claude-skill",
- "path": "skills/ffuf-claude-skill",
+ "path": "skills\\ffuf-claude-skill",
"category": "uncategorized",
"name": "ffuf-claude-skill",
"description": "Web fuzzing with ffuf",
@@ -3736,7 +3817,7 @@
},
{
"id": "figma-automation",
- "path": "skills/figma-automation",
+ "path": "skills\\figma-automation",
"category": "uncategorized",
"name": "figma-automation",
"description": "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.",
@@ -3745,7 +3826,7 @@
},
{
"id": "file-organizer",
- "path": "skills/file-organizer",
+ "path": "skills\\file-organizer",
"category": "uncategorized",
"name": "file-organizer",
"description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo...",
@@ -3754,7 +3835,7 @@
},
{
"id": "file-path-traversal",
- "path": "skills/file-path-traversal",
+ "path": "skills\\file-path-traversal",
"category": "uncategorized",
"name": "file-path-traversal",
"description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu...",
@@ -3763,7 +3844,7 @@
},
{
"id": "file-uploads",
- "path": "skills/file-uploads",
+ "path": "skills\\file-uploads",
"category": "uncategorized",
"name": "file-uploads",
"description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...",
@@ -3772,7 +3853,7 @@
},
{
"id": "find-bugs",
- "path": "skills/find-bugs",
+ "path": "skills\\find-bugs",
"category": "uncategorized",
"name": "find-bugs",
"description": "Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.",
@@ -3781,7 +3862,7 @@
},
{
"id": "finishing-a-development-branch",
- "path": "skills/finishing-a-development-branch",
+ "path": "skills\\finishing-a-development-branch",
"category": "uncategorized",
"name": "finishing-a-development-branch",
"description": "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup",
@@ -3790,7 +3871,7 @@
},
{
"id": "firebase",
- "path": "skills/firebase",
+ "path": "skills\\firebase",
"category": "uncategorized",
"name": "firebase",
"description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r...",
@@ -3799,7 +3880,7 @@
},
{
"id": "firecrawl-scraper",
- "path": "skills/firecrawl-scraper",
+ "path": "skills\\firecrawl-scraper",
"category": "uncategorized",
"name": "firecrawl-scraper",
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API",
@@ -3808,16 +3889,16 @@
},
{
"id": "firmware-analyst",
- "path": "skills/firmware-analyst",
+ "path": "skills\\firmware-analyst",
"category": "uncategorized",
- "name": "Firmware Analyst",
- "description": "wget http://vendor.com/firmware/update.bin",
+ "name": "firmware-analyst",
+ "description": "Expert firmware analyst specializing in embedded systems, IoT\nsecurity, and hardware reverse engineering. Masters firmware extraction,\nanalysis, and vulnerability research for routers, IoT devices, automotive\nsystems, and industrial controllers. Use PROACTIVELY for firmware security\naudits, IoT penetration testing, or embedded systems research.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fix-review",
- "path": "skills/fix-review",
+ "path": "skills\\fix-review",
"category": "uncategorized",
"name": "fix-review",
"description": "Verify fix commits address audit findings without new bugs",
@@ -3826,25 +3907,25 @@
},
{
"id": "flutter-expert",
- "path": "skills/flutter-expert",
+ "path": "skills\\flutter-expert",
"category": "uncategorized",
- "name": "Flutter Expert",
- "description": "- Working on flutter expert tasks or workflows - Needing guidance, best practices, or checklists for flutter expert",
+ "name": "flutter-expert",
+ "description": "Master Flutter development with Dart 3, advanced widgets, and\nmulti-platform deployment. Handles state management, animations, testing, and\nperformance optimization for mobile, web, desktop, and embedded platforms. Use\nPROACTIVELY for Flutter architecture, UI implementation, or cross-platform\nfeatures.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "form-cro",
- "path": "skills/form-cro",
+ "path": "skills\\form-cro",
"category": "uncategorized",
- "name": "Form Cro",
- "description": "You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**.",
+ "name": "form-cro",
+ "description": "Optimize any form that is NOT signup or account registration \u2014 including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fp-ts-errors",
- "path": "skills/fp-ts-errors",
+ "path": "skills\\fp-ts-errors",
"category": "uncategorized",
"name": "fp-ts-errors",
"description": "Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.",
@@ -3853,7 +3934,7 @@
},
{
"id": "fp-ts-pragmatic",
- "path": "skills/fp-ts-pragmatic",
+ "path": "skills\\fp-ts-pragmatic",
"category": "uncategorized",
"name": "fp-ts-pragmatic",
"description": "A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.",
@@ -3862,7 +3943,7 @@
},
{
"id": "fp-ts-react",
- "path": "skills/fp-ts-react",
+ "path": "skills\\fp-ts-react",
"category": "uncategorized",
"name": "fp-ts-react",
"description": "Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.",
@@ -3871,7 +3952,7 @@
},
{
"id": "framework-migration-code-migrate",
- "path": "skills/framework-migration-code-migrate",
+ "path": "skills\\framework-migration-code-migrate",
"category": "uncategorized",
"name": "framework-migration-code-migrate",
"description": "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and",
@@ -3880,7 +3961,7 @@
},
{
"id": "framework-migration-deps-upgrade",
- "path": "skills/framework-migration-deps-upgrade",
+ "path": "skills\\framework-migration-deps-upgrade",
"category": "uncategorized",
"name": "framework-migration-deps-upgrade",
"description": "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa",
@@ -3889,7 +3970,7 @@
},
{
"id": "framework-migration-legacy-modernize",
- "path": "skills/framework-migration-legacy-modernize",
+ "path": "skills\\framework-migration-legacy-modernize",
"category": "uncategorized",
"name": "framework-migration-legacy-modernize",
"description": "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex",
@@ -3898,7 +3979,7 @@
},
{
"id": "free-tool-strategy",
- "path": "skills/free-tool-strategy",
+ "path": "skills\\free-tool-strategy",
"category": "uncategorized",
"name": "free-tool-strategy",
"description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar...",
@@ -3907,7 +3988,7 @@
},
{
"id": "freshdesk-automation",
- "path": "skills/freshdesk-automation",
+ "path": "skills\\freshdesk-automation",
"category": "uncategorized",
"name": "freshdesk-automation",
"description": "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -3916,34 +3997,16 @@
},
{
"id": "freshservice-automation",
- "path": "skills/freshservice-automation",
+ "path": "skills\\freshservice-automation",
"category": "uncategorized",
"name": "freshservice-automation",
"description": "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "frontend-developer",
- "path": "skills/frontend-developer",
- "category": "uncategorized",
- "name": "Frontend Developer",
- "description": "You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "frontend-security-coder",
- "path": "skills/frontend-security-coder",
- "category": "uncategorized",
- "name": "Frontend Security Coder",
- "description": "- Working on frontend security coder tasks or workflows - Needing guidance, best practices, or checklists for frontend security coder",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "frontend-design",
- "path": "skills/frontend-design",
+ "path": "skills\\frontend-design",
"category": "uncategorized",
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...",
@@ -3952,16 +4015,25 @@
},
{
"id": "frontend-dev-guidelines",
- "path": "skills/frontend-dev-guidelines",
+ "path": "skills\\frontend-dev-guidelines",
"category": "uncategorized",
"name": "frontend-dev-guidelines",
"description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "frontend-developer",
+ "path": "skills\\frontend-developer",
+ "category": "uncategorized",
+ "name": "frontend-developer",
+ "description": "Build React components, implement responsive layouts, and handle\nclient-side state management. Masters React 19, Next.js 15, and modern\nfrontend architecture. Optimizes performance and ensures accessibility. Use\nPROACTIVELY when creating UI components or fixing frontend issues.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "frontend-mobile-development-component-scaffold",
- "path": "skills/frontend-mobile-development-component-scaffold",
+ "path": "skills\\frontend-mobile-development-component-scaffold",
"category": "uncategorized",
"name": "frontend-mobile-development-component-scaffold",
"description": "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s",
@@ -3970,16 +4042,25 @@
},
{
"id": "frontend-mobile-security-xss-scan",
- "path": "skills/frontend-mobile-security-xss-scan",
+ "path": "skills\\frontend-mobile-security-xss-scan",
"category": "uncategorized",
"name": "frontend-mobile-security-xss-scan",
"description": "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "frontend-security-coder",
+ "path": "skills\\frontend-security-coder",
+ "category": "uncategorized",
+ "name": "frontend-security-coder",
+ "description": "Expert in secure frontend coding practices specializing in XSS\nprevention, output sanitization, and client-side security patterns. Use\nPROACTIVELY for frontend security implementations or client-side security code\nreviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "frontend-slides",
- "path": "skills/frontend-slides",
+ "path": "skills\\frontend-slides",
"category": "uncategorized",
"name": "frontend-slides",
"description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a...",
@@ -3988,7 +4069,7 @@
},
{
"id": "frontend-ui-dark-ts",
- "path": "skills/frontend-ui-dark-ts",
+ "path": "skills\\frontend-ui-dark-ts",
"category": "uncategorized",
"name": "frontend-ui-dark-ts",
"description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces...",
@@ -3997,7 +4078,7 @@
},
{
"id": "full-stack-orchestration-full-stack-feature",
- "path": "skills/full-stack-orchestration-full-stack-feature",
+ "path": "skills\\full-stack-orchestration-full-stack-feature",
"category": "uncategorized",
"name": "full-stack-orchestration-full-stack-feature",
"description": "Use when working with full stack orchestration full stack feature",
@@ -4006,7 +4087,7 @@
},
{
"id": "game-art",
- "path": "skills/game-development/game-art",
+ "path": "skills\\game-development\\game-art",
"category": "game-development",
"name": "game-art",
"description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
@@ -4015,7 +4096,7 @@
},
{
"id": "game-audio",
- "path": "skills/game-development/game-audio",
+ "path": "skills\\game-development\\game-audio",
"category": "game-development",
"name": "game-audio",
"description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
@@ -4024,7 +4105,7 @@
},
{
"id": "game-design",
- "path": "skills/game-development/game-design",
+ "path": "skills\\game-development\\game-design",
"category": "game-development",
"name": "game-design",
"description": "Game design principles. GDD structure, balancing, player psychology, progression.",
@@ -4033,7 +4114,7 @@
},
{
"id": "game-development",
- "path": "skills/game-development",
+ "path": "skills\\game-development",
"category": "uncategorized",
"name": "game-development",
"description": "Game development orchestrator. Routes to platform-specific skills based on project needs.",
@@ -4042,7 +4123,7 @@
},
{
"id": "gcp-cloud-run",
- "path": "skills/gcp-cloud-run",
+ "path": "skills\\gcp-cloud-run",
"category": "uncategorized",
"name": "gcp-cloud-run",
"description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri...",
@@ -4051,7 +4132,7 @@
},
{
"id": "gdpr-data-handling",
- "path": "skills/gdpr-data-handling",
+ "path": "skills\\gdpr-data-handling",
"category": "uncategorized",
"name": "gdpr-data-handling",
"description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o...",
@@ -4060,7 +4141,7 @@
},
{
"id": "gemini-api-dev",
- "path": "skills/gemini-api-dev",
+ "path": "skills\\gemini-api-dev",
"category": "uncategorized",
"name": "gemini-api-dev",
"description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n...",
@@ -4069,7 +4150,7 @@
},
{
"id": "geo-fundamentals",
- "path": "skills/geo-fundamentals",
+ "path": "skills\\geo-fundamentals",
"category": "uncategorized",
"name": "geo-fundamentals",
"description": "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).",
@@ -4078,7 +4159,7 @@
},
{
"id": "git-advanced-workflows",
- "path": "skills/git-advanced-workflows",
+ "path": "skills\\git-advanced-workflows",
"category": "uncategorized",
"name": "git-advanced-workflows",
"description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co...",
@@ -4087,7 +4168,7 @@
},
{
"id": "git-pr-workflows-git-workflow",
- "path": "skills/git-pr-workflows-git-workflow",
+ "path": "skills\\git-pr-workflows-git-workflow",
"category": "uncategorized",
"name": "git-pr-workflows-git-workflow",
"description": "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g",
@@ -4096,7 +4177,7 @@
},
{
"id": "git-pr-workflows-onboard",
- "path": "skills/git-pr-workflows-onboard",
+ "path": "skills\\git-pr-workflows-onboard",
"category": "uncategorized",
"name": "git-pr-workflows-onboard",
"description": "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You",
@@ -4105,7 +4186,7 @@
},
{
"id": "git-pr-workflows-pr-enhance",
- "path": "skills/git-pr-workflows-pr-enhance",
+ "path": "skills\\git-pr-workflows-pr-enhance",
"category": "uncategorized",
"name": "git-pr-workflows-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu",
@@ -4114,7 +4195,7 @@
},
{
"id": "git-pushing",
- "path": "skills/git-pushing",
+ "path": "skills\\git-pushing",
"category": "uncategorized",
"name": "git-pushing",
"description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate...",
@@ -4123,7 +4204,7 @@
},
{
"id": "github-actions-templates",
- "path": "skills/github-actions-templates",
+ "path": "skills\\github-actions-templates",
"category": "uncategorized",
"name": "github-actions-templates",
"description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre...",
@@ -4132,7 +4213,7 @@
},
{
"id": "github-automation",
- "path": "skills/github-automation",
+ "path": "skills\\github-automation",
"category": "uncategorized",
"name": "github-automation",
"description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
@@ -4141,7 +4222,7 @@
},
{
"id": "github-issue-creator",
- "path": "skills/github-issue-creator",
+ "path": "skills\\github-issue-creator",
"category": "uncategorized",
"name": "github-issue-creator",
"description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...",
@@ -4150,7 +4231,7 @@
},
{
"id": "github-workflow-automation",
- "path": "skills/github-workflow-automation",
+ "path": "skills\\github-workflow-automation",
"category": "uncategorized",
"name": "github-workflow-automation",
"description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati...",
@@ -4159,7 +4240,7 @@
},
{
"id": "gitlab-automation",
- "path": "skills/gitlab-automation",
+ "path": "skills\\gitlab-automation",
"category": "uncategorized",
"name": "gitlab-automation",
"description": "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -4168,7 +4249,7 @@
},
{
"id": "gitlab-ci-patterns",
- "path": "skills/gitlab-ci-patterns",
+ "path": "skills\\gitlab-ci-patterns",
"category": "uncategorized",
"name": "gitlab-ci-patterns",
"description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...",
@@ -4177,7 +4258,7 @@
},
{
"id": "gitops-workflow",
- "path": "skills/gitops-workflow",
+ "path": "skills\\gitops-workflow",
"category": "uncategorized",
"name": "gitops-workflow",
"description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo...",
@@ -4186,7 +4267,7 @@
},
{
"id": "gmail-automation",
- "path": "skills/gmail-automation",
+ "path": "skills\\gmail-automation",
"category": "uncategorized",
"name": "gmail-automation",
"description": "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.",
@@ -4195,7 +4276,7 @@
},
{
"id": "go-concurrency-patterns",
- "path": "skills/go-concurrency-patterns",
+ "path": "skills\\go-concurrency-patterns",
"category": "uncategorized",
"name": "go-concurrency-patterns",
"description": "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.",
@@ -4204,7 +4285,7 @@
},
{
"id": "go-playwright",
- "path": "skills/go-playwright",
+ "path": "skills\\go-playwright",
"category": "uncategorized",
"name": "go-playwright",
"description": "Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.",
@@ -4213,7 +4294,7 @@
},
{
"id": "go-rod-master",
- "path": "skills/go-rod-master",
+ "path": "skills\\go-rod-master",
"category": "uncategorized",
"name": "go-rod-master",
"description": "Comprehensive guide for browser automation and web scraping with go-rod (Chrome DevTools Protocol) including stealth anti-bot-detection patterns.",
@@ -4222,7 +4303,7 @@
},
{
"id": "godot-4-migration",
- "path": "skills/godot-4-migration",
+ "path": "skills\\godot-4-migration",
"category": "uncategorized",
"name": "godot-4-migration",
"description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
@@ -4231,7 +4312,7 @@
},
{
"id": "godot-gdscript-patterns",
- "path": "skills/godot-gdscript-patterns",
+ "path": "skills\\godot-gdscript-patterns",
"category": "uncategorized",
"name": "godot-gdscript-patterns",
"description": "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.",
@@ -4240,16 +4321,16 @@
},
{
"id": "golang-pro",
- "path": "skills/golang-pro",
+ "path": "skills\\golang-pro",
"category": "uncategorized",
- "name": "Golang Pro",
- "description": "You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.",
+ "name": "golang-pro",
+ "description": "Master Go 1.21+ with modern patterns, advanced concurrency,\nperformance optimization, and production-ready microservices. Expert in the\nlatest Go ecosystem including generics, workspaces, and cutting-edge\nframeworks. Use PROACTIVELY for Go development, architecture design, or\nperformance optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "google-analytics-automation",
- "path": "skills/google-analytics-automation",
+ "path": "skills\\google-analytics-automation",
"category": "uncategorized",
"name": "google-analytics-automation",
"description": "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.",
@@ -4258,7 +4339,7 @@
},
{
"id": "google-calendar-automation",
- "path": "skills/google-calendar-automation",
+ "path": "skills\\google-calendar-automation",
"category": "uncategorized",
"name": "google-calendar-automation",
"description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica...",
@@ -4267,7 +4348,7 @@
},
{
"id": "google-drive-automation",
- "path": "skills/google-drive-automation",
+ "path": "skills\\google-drive-automation",
"category": "uncategorized",
"name": "google-drive-automation",
"description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr...",
@@ -4276,7 +4357,7 @@
},
{
"id": "googlesheets-automation",
- "path": "skills/googlesheets-automation",
+ "path": "skills\\googlesheets-automation",
"category": "uncategorized",
"name": "googlesheets-automation",
"description": "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.",
@@ -4285,7 +4366,7 @@
},
{
"id": "grafana-dashboards",
- "path": "skills/grafana-dashboards",
+ "path": "skills\\grafana-dashboards",
"category": "uncategorized",
"name": "grafana-dashboards",
"description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ...",
@@ -4294,7 +4375,7 @@
},
{
"id": "graphql",
- "path": "skills/graphql",
+ "path": "skills\\graphql",
"category": "uncategorized",
"name": "graphql",
"description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...",
@@ -4303,16 +4384,25 @@
},
{
"id": "graphql-architect",
- "path": "skills/graphql-architect",
+ "path": "skills\\graphql-architect",
"category": "uncategorized",
- "name": "Graphql Architect",
- "description": "- Working on graphql architect tasks or workflows - Needing guidance, best practices, or checklists for graphql architect",
+ "name": "graphql-architect",
+ "description": "Master modern GraphQL with federation, performance optimization,\nand enterprise security. Build scalable schemas, implement advanced caching,\nand design real-time systems. Use PROACTIVELY for GraphQL architecture or\nperformance optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "grpc-golang",
+ "path": "skills\\grpc-golang",
+ "category": "uncategorized",
+ "name": "grpc-golang",
+ "description": "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "haskell-pro",
- "path": "skills/haskell-pro",
+ "path": "skills\\haskell-pro",
"category": "uncategorized",
"name": "haskell-pro",
"description": "Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.",
@@ -4321,7 +4411,7 @@
},
{
"id": "helm-chart-scaffolding",
- "path": "skills/helm-chart-scaffolding",
+ "path": "skills\\helm-chart-scaffolding",
"category": "uncategorized",
"name": "helm-chart-scaffolding",
"description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl...",
@@ -4330,7 +4420,7 @@
},
{
"id": "helpdesk-automation",
- "path": "skills/helpdesk-automation",
+ "path": "skills\\helpdesk-automation",
"category": "uncategorized",
"name": "helpdesk-automation",
"description": "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.",
@@ -4339,133 +4429,133 @@
},
{
"id": "hig-components-content",
- "path": "skills/hig-components-content",
+ "path": "skills\\hig-components-content",
"category": "uncategorized",
- "name": "Hig Components Content",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-content",
+ "description": "Apple Human Interface Guidelines for content display components. Use this skill when the user asks about \"charts component\", \"collection view\", \"image view\", \"web view\", \"color well\", \"image well\", \"activity view\", \"lockup\", \"data visualization\", \"content display\", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says \"how should I display charts\", \"what's the best way to show images\", \"should I use a web view\", \"how do I build a grid of items\", \"what component shows media\", or \"how do I present a share sheet\". Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-controls",
- "path": "skills/hig-components-controls",
+ "path": "skills\\hig-components-controls",
"category": "uncategorized",
- "name": "Hig Components Controls",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-controls",
+ "description": "Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says \"picker or segmented control,\" \"how should my form look,\" \"what keyboard type should I use,\" \"toggle vs checkbox,\" or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. Cross-references: hig-components-menus, hig-components-dialogs, hig-components-search.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-dialogs",
- "path": "skills/hig-components-dialogs",
+ "path": "skills\\hig-components-dialogs",
"category": "uncategorized",
- "name": "Hig Components Dialogs",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-dialogs",
+ "description": "Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says \"should I use an alert or a sheet,\" \"how do I show a confirmation dialog,\" \"when should I use a popover,\" \"my modals are annoying users,\" or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, destructive action confirmation, or overlay UI patterns. Cross-references: hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-layout",
- "path": "skills/hig-components-layout",
+ "path": "skills\\hig-components-layout",
"category": "uncategorized",
- "name": "Hig Components Layout",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-layout",
+ "description": "Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about \"sidebar\", \"split view\", \"tab bar\", \"tab view\", \"scroll view\", \"window design\", \"panel\", \"list view\", \"table view\", \"column view\", \"outline view\", \"navigation structure\", \"app layout\", \"boxes\", \"ornaments\", or organizing content hierarchically in Apple apps. Also use when the user says \"how should I organize my app\", \"what navigation pattern should I use\", \"my layout breaks on iPad\", \"how do I build a sidebar\", \"should I use tabs or a sidebar\", or \"my app doesn't adapt to different screen sizes\". Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-menus",
- "path": "skills/hig-components-menus",
+ "path": "skills\\hig-components-menus",
"category": "uncategorized",
- "name": "Hig Components Menus",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-menus",
+ "description": "Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure controls, and standard buttons. Use this skill when the user says \"how should my buttons look,\" \"what goes in the menu bar,\" \"should I use a context menu or action sheet,\" \"how do I design a toolbar,\" or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit menu, or any menu/button component layout and behavior. Cross-references: hig-components-search, hig-components-controls, hig-components-dialogs.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-search",
- "path": "skills/hig-components-search",
+ "path": "skills\\hig-components-search",
"category": "uncategorized",
- "name": "Hig Components Search",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-search",
+ "description": "Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill when the user says \"how should search work in my app,\" \"I need a breadcrumb,\" \"how do I paginate content,\" or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-status",
- "path": "skills/hig-components-status",
+ "path": "skills\\hig-components-status",
"category": "uncategorized",
- "name": "Hig Components Status",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-status",
+ "description": "Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: \"progress indicator\", \"progress bar\", \"loading spinner\", \"status bar\", \"activity ring\", \"progress display\", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says \"how do I show loading state,\" \"should I use a spinner or progress bar,\" \"what goes in the status bar,\" or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-system",
- "path": "skills/hig-components-system",
+ "path": "skills\\hig-components-system",
"category": "uncategorized",
- "name": "Hig Components System",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-system",
+ "description": "Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: \"widget design\", \"live activity\", \"notification design\", \"complication\", \"home screen quick action\", \"top shelf\", \"watch face\", \"app clip\", \"app shortcut\", \"system experience\". Also use when the user says \"how do I design a widget,\" \"what should my notification look like,\" \"how do Live Activities work,\" \"should I make an App Clip,\" or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-foundations",
- "path": "skills/hig-foundations",
+ "path": "skills\\hig-foundations",
"category": "uncategorized",
- "name": "Hig Foundations",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-foundations",
+ "description": "Apple Human Interface Guidelines design foundations. Use this skill when the user asks about \"HIG color\", \"Apple typography\", \"SF Symbols\", \"dark mode guidelines\", \"accessible design\", \"Apple design foundations\", \"app icon\", \"layout guidelines\", \"materials\", \"motion\", \"privacy\", \"right to left\", \"RTL\", \"inclusive design\", branding, images, spatial layout, or writing style. Also use when the user says \"my colors look wrong in dark mode\", \"what font should I use\", \"is my app accessible enough\", \"how do I support Dynamic Type\", \"what contrast ratio do I need\", \"how do I pick system colors\", or \"my icons don't match the system style\". Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction patterns, hig-components-layout for structural components, hig-components-content for display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-inputs",
- "path": "skills/hig-inputs",
+ "path": "skills\\hig-inputs",
"category": "uncategorized",
- "name": "Hig Inputs",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-inputs",
+ "description": "Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. Use when asked about: \"gesture design\", \"Apple Pencil\", \"keyboard shortcuts\", \"game controller\", \"pointer support\", \"mouse support\", \"trackpad\", \"Digital Crown\", \"eye tracking\", \"visionOS input\", \"focus system\", \"remote control\", \"gyroscope\", \"spatial interaction\". Also use when the user says \"what gestures should I support,\" \"how do I add keyboard shortcuts,\" \"how does input work on Apple TV,\" \"should I support Apple Pencil,\" or asks about input device handling. Cross-references: hig-components-status, hig-components-system, hig-technologies for VoiceOver and Siri.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-patterns",
- "path": "skills/hig-patterns",
+ "path": "skills\\hig-patterns",
"category": "uncategorized",
- "name": "Hig Patterns",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-patterns",
+ "description": "Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about \"onboarding flow\", \"user onboarding\", \"app launch\", \"loading state\", \"drag and drop\", \"search pattern\", \"settings design\", \"notifications\", \"modality\", \"multitasking\", \"feedback pattern\", \"haptics\", \"undo redo\", \"file management\", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says \"how should onboarding work\", \"my app takes too long to load\", \"should I use a modal here\", \"how do I handle errors\", \"when should I ask for permissions\", \"how to show progress\", or \"what's the right way to confirm a delete\". Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics, hig-components-layout for navigation, hig-components-content for data display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-platforms",
- "path": "skills/hig-platforms",
+ "path": "skills\\hig-platforms",
"category": "uncategorized",
- "name": "Hig Platforms",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-platforms",
+ "description": "Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about \"designing for iOS\", \"iPad app design\", \"macOS design\", \"tvOS\", \"visionOS\", \"watchOS\", \"Apple platform\", \"which platform\", platform differences, platform-specific conventions, or multi-platform app design. Also use when the user says \"should I design differently for iPad vs iPhone\", \"how does my app work on visionOS\", \"what's different about macOS apps\", \"porting my app to another platform\", \"universal app design\", or \"what input methods does this platform use\". Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns, hig-components-layout for navigation structures, hig-components-content for content display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-project-context",
- "path": "skills/hig-project-context",
+ "path": "skills\\hig-project-context",
"category": "uncategorized",
- "name": "Hig Project Context",
- "description": "Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.",
+ "name": "hig-project-context",
+ "description": "Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says \"set up my project context,\" \"what platforms am I targeting,\" \"configure HIG settings,\" or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-technologies",
- "path": "skills/hig-technologies",
+ "path": "skills\\hig-technologies",
"category": "uncategorized",
- "name": "Hig Technologies",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-technologies",
+ "description": "Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: \"Siri integration\", \"Apple Pay\", \"HealthKit\", \"HomeKit\", \"ARKit\", \"augmented reality\", \"machine learning\", \"generative AI\", \"iCloud sync\", \"Sign in with Apple\", \"SharePlay\", \"CarPlay\", \"in-app purchase\", \"NFC\", \"VoiceOver\", \"Maps\", \"Mac Catalyst\". Also use when the user says \"how do I integrate Siri,\" \"what are the Apple Pay guidelines,\" \"how should my AR experience work,\" \"how do I use Sign in with Apple,\" or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hosted-agents-v2-py",
- "path": "skills/hosted-agents-v2-py",
+ "path": "skills\\hosted-agents-v2-py",
"category": "uncategorized",
"name": "hosted-agents-v2-py",
"description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.",
@@ -4474,16 +4564,16 @@
},
{
"id": "hr-pro",
- "path": "skills/hr-pro",
+ "path": "skills\\hr-pro",
"category": "uncategorized",
- "name": "Hr Pro",
- "description": "- Working on hr pro tasks or workflows - Needing guidance, best practices, or checklists for hr pro",
+ "name": "hr-pro",
+ "description": "Professional, ethical HR partner for hiring,\nonboarding/offboarding, PTO and leave, performance, compliant policies, and\nemployee relations. Ask for jurisdiction and company context before advising;\nproduce structured, bias-mitigated, lawful templates.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "html-injection-testing",
- "path": "skills/html-injection-testing",
+ "path": "skills\\html-injection-testing",
"category": "uncategorized",
"name": "html-injection-testing",
"description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten...",
@@ -4492,7 +4582,7 @@
},
{
"id": "hubspot-automation",
- "path": "skills/hubspot-automation",
+ "path": "skills\\hubspot-automation",
"category": "uncategorized",
"name": "hubspot-automation",
"description": "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.",
@@ -4501,7 +4591,7 @@
},
{
"id": "hubspot-integration",
- "path": "skills/hubspot-integration",
+ "path": "skills\\hubspot-integration",
"category": "uncategorized",
"name": "hubspot-integration",
"description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs...",
@@ -4510,7 +4600,7 @@
},
{
"id": "hugging-face-cli",
- "path": "skills/hugging-face-cli",
+ "path": "skills\\hugging-face-cli",
"category": "uncategorized",
"name": "hugging-face-cli",
"description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...",
@@ -4519,7 +4609,7 @@
},
{
"id": "hugging-face-jobs",
- "path": "skills/hugging-face-jobs",
+ "path": "skills\\hugging-face-jobs",
"category": "uncategorized",
"name": "hugging-face-jobs",
"description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok...",
@@ -4528,16 +4618,16 @@
},
{
"id": "hybrid-cloud-architect",
- "path": "skills/hybrid-cloud-architect",
+ "path": "skills\\hybrid-cloud-architect",
"category": "uncategorized",
- "name": "Hybrid Cloud Architect",
- "description": "- Working on hybrid cloud architect tasks or workflows - Needing guidance, best practices, or checklists for hybrid cloud architect",
+ "name": "hybrid-cloud-architect",
+ "description": "Expert hybrid cloud architect specializing in complex multi-cloud\nsolutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters\nhybrid connectivity, workload placement optimization, edge computing, and\ncross-cloud automation. Handles compliance, cost optimization, disaster\nrecovery, and migration strategies. Use PROACTIVELY for hybrid architecture,\nmulti-cloud strategy, or complex infrastructure integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hybrid-cloud-networking",
- "path": "skills/hybrid-cloud-networking",
+ "path": "skills\\hybrid-cloud-networking",
"category": "uncategorized",
"name": "hybrid-cloud-networking",
"description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ...",
@@ -4546,7 +4636,7 @@
},
{
"id": "hybrid-search-implementation",
- "path": "skills/hybrid-search-implementation",
+ "path": "skills\\hybrid-search-implementation",
"category": "uncategorized",
"name": "hybrid-search-implementation",
"description": "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.",
@@ -4555,7 +4645,7 @@
},
{
"id": "i18n-localization",
- "path": "skills/i18n-localization",
+ "path": "skills\\i18n-localization",
"category": "uncategorized",
"name": "i18n-localization",
"description": "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.",
@@ -4564,7 +4654,7 @@
},
{
"id": "idor-testing",
- "path": "skills/idor-testing",
+ "path": "skills\\idor-testing",
"category": "uncategorized",
"name": "idor-testing",
"description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje...",
@@ -4573,16 +4663,16 @@
},
{
"id": "imagen",
- "path": "skills/imagen",
+ "path": "skills\\imagen",
"category": "uncategorized",
"name": "imagen",
- "description": "|",
+ "description": "This skill generates images using Google Gemini's image generation model (`gemini-3-pro-image-preview`). It enables seamless image creation during any Claude Code session - whether you're building frontend UIs, creating documentation, or need visual",
"risk": "safe",
"source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
},
{
"id": "impress",
- "path": "skills/libreoffice/impress",
+ "path": "skills\\libreoffice\\impress",
"category": "libreoffice",
"name": "impress",
"description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
@@ -4591,16 +4681,16 @@
},
{
"id": "incident-responder",
- "path": "skills/incident-responder",
+ "path": "skills\\incident-responder",
"category": "uncategorized",
- "name": "Incident Responder",
- "description": "- Working on incident responder tasks or workflows - Needing guidance, best practices, or checklists for incident responder",
+ "name": "incident-responder",
+ "description": "Expert SRE incident responder specializing in rapid problem\nresolution, modern observability, and comprehensive incident management.\nMasters incident command, blameless post-mortems, error budget management, and\nsystem reliability patterns. Handles critical outages, communication\nstrategies, and continuous improvement. Use IMMEDIATELY for production\nincidents or SRE practices.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "incident-response-incident-response",
- "path": "skills/incident-response-incident-response",
+ "path": "skills\\incident-response-incident-response",
"category": "uncategorized",
"name": "incident-response-incident-response",
"description": "Use when working with incident response incident response",
@@ -4609,7 +4699,7 @@
},
{
"id": "incident-response-smart-fix",
- "path": "skills/incident-response-smart-fix",
+ "path": "skills\\incident-response-smart-fix",
"category": "uncategorized",
"name": "incident-response-smart-fix",
"description": "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res",
@@ -4618,7 +4708,7 @@
},
{
"id": "incident-runbook-templates",
- "path": "skills/incident-runbook-templates",
+ "path": "skills\\incident-runbook-templates",
"category": "uncategorized",
"name": "incident-runbook-templates",
"description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...",
@@ -4627,7 +4717,7 @@
},
{
"id": "infinite-gratitude",
- "path": "skills/infinite-gratitude",
+ "path": "skills\\infinite-gratitude",
"category": "uncategorized",
"name": "infinite-gratitude",
"description": "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).",
@@ -4636,7 +4726,7 @@
},
{
"id": "inngest",
- "path": "skills/inngest",
+ "path": "skills\\inngest",
"category": "uncategorized",
"name": "inngest",
"description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...",
@@ -4645,7 +4735,7 @@
},
{
"id": "instagram-automation",
- "path": "skills/instagram-automation",
+ "path": "skills\\instagram-automation",
"category": "uncategorized",
"name": "instagram-automation",
"description": "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.",
@@ -4654,7 +4744,7 @@
},
{
"id": "interactive-portfolio",
- "path": "skills/interactive-portfolio",
+ "path": "skills\\interactive-portfolio",
"category": "uncategorized",
"name": "interactive-portfolio",
"description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,...",
@@ -4663,7 +4753,7 @@
},
{
"id": "intercom-automation",
- "path": "skills/intercom-automation",
+ "path": "skills\\intercom-automation",
"category": "uncategorized",
"name": "intercom-automation",
"description": "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.",
@@ -4672,7 +4762,7 @@
},
{
"id": "internal-comms-anthropic",
- "path": "skills/internal-comms-anthropic",
+ "path": "skills\\internal-comms-anthropic",
"category": "uncategorized",
"name": "internal-comms-anthropic",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
@@ -4681,7 +4771,7 @@
},
{
"id": "internal-comms-community",
- "path": "skills/internal-comms-community",
+ "path": "skills\\internal-comms-community",
"category": "uncategorized",
"name": "internal-comms-community",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
@@ -4689,17 +4779,26 @@
"source": "community"
},
{
- "id": "ios-developer",
- "path": "skills/ios-developer",
+ "id": "inventory-demand-planning",
+ "path": "skills\\inventory-demand-planning",
"category": "uncategorized",
- "name": "Ios Developer",
- "description": "- Working on ios developer tasks or workflows - Needing guidance, best practices, or checklists for ios developer",
+ "name": "inventory-demand-planning",
+ "description": "Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimising inventory levels.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "ios-developer",
+ "path": "skills\\ios-developer",
+ "category": "uncategorized",
+ "name": "ios-developer",
+ "description": "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,\nSwiftUI, UIKit integration, Core Data, networking, and App Store optimization.\nUse PROACTIVELY for iOS-specific features, App Store optimization, or native\niOS development.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "istio-traffic-management",
- "path": "skills/istio-traffic-management",
+ "path": "skills\\istio-traffic-management",
"category": "uncategorized",
"name": "istio-traffic-management",
"description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie...",
@@ -4708,7 +4807,7 @@
},
{
"id": "iterate-pr",
- "path": "skills/iterate-pr",
+ "path": "skills\\iterate-pr",
"category": "uncategorized",
"name": "iterate-pr",
"description": "Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.",
@@ -4717,34 +4816,34 @@
},
{
"id": "java-pro",
- "path": "skills/java-pro",
+ "path": "skills\\java-pro",
"category": "uncategorized",
- "name": "Java Pro",
- "description": "- Working on java pro tasks or workflows - Needing guidance, best practices, or checklists for java pro",
+ "name": "java-pro",
+ "description": "Master Java 21+ with modern features like virtual threads, pattern\nmatching, and Spring Boot 3.x. Expert in the latest Java ecosystem including\nGraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java\ndevelopment, microservices architecture, or performance optimization.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "javascript-pro",
- "path": "skills/javascript-pro",
- "category": "uncategorized",
- "name": "Javascript Pro",
- "description": "You are a JavaScript expert specializing in modern JS and async programming.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "javascript-mastery",
- "path": "skills/javascript-mastery",
+ "path": "skills\\javascript-mastery",
"category": "uncategorized",
"name": "javascript-mastery",
"description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "javascript-pro",
+ "path": "skills\\javascript-pro",
+ "category": "uncategorized",
+ "name": "javascript-pro",
+ "description": "Master modern JavaScript with ES6+, async patterns, and Node.js\nAPIs. Handles promises, event loops, and browser/Node compatibility. Use\nPROACTIVELY for JavaScript optimization, async debugging, or complex JS\npatterns.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "javascript-testing-patterns",
- "path": "skills/javascript-testing-patterns",
+ "path": "skills\\javascript-testing-patterns",
"category": "uncategorized",
"name": "javascript-testing-patterns",
"description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use...",
@@ -4753,7 +4852,7 @@
},
{
"id": "javascript-typescript-typescript-scaffold",
- "path": "skills/javascript-typescript-typescript-scaffold",
+ "path": "skills\\javascript-typescript-typescript-scaffold",
"category": "uncategorized",
"name": "javascript-typescript-typescript-scaffold",
"description": "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N",
@@ -4762,7 +4861,7 @@
},
{
"id": "jira-automation",
- "path": "skills/jira-automation",
+ "path": "skills\\jira-automation",
"category": "uncategorized",
"name": "jira-automation",
"description": "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.",
@@ -4771,16 +4870,16 @@
},
{
"id": "julia-pro",
- "path": "skills/julia-pro",
+ "path": "skills\\julia-pro",
"category": "uncategorized",
- "name": "Julia Pro",
- "description": "- Working on julia pro tasks or workflows - Needing guidance, best practices, or checklists for julia pro",
+ "name": "julia-pro",
+ "description": "Master Julia 1.10+ with modern features, performance optimization,\nmultiple dispatch, and production-ready practices. Expert in the Julia\necosystem including package management, scientific computing, and\nhigh-performance numerical code. Use PROACTIVELY for Julia development,\noptimization, or advanced Julia patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "k8s-manifest-generator",
- "path": "skills/k8s-manifest-generator",
+ "path": "skills\\k8s-manifest-generator",
"category": "uncategorized",
"name": "k8s-manifest-generator",
"description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat...",
@@ -4789,7 +4888,7 @@
},
{
"id": "k8s-security-policies",
- "path": "skills/k8s-security-policies",
+ "path": "skills\\k8s-security-policies",
"category": "uncategorized",
"name": "k8s-security-policies",
"description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...",
@@ -4798,7 +4897,7 @@
},
{
"id": "kaizen",
- "path": "skills/kaizen",
+ "path": "skills\\kaizen",
"category": "uncategorized",
"name": "kaizen",
"description": "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.",
@@ -4807,7 +4906,7 @@
},
{
"id": "klaviyo-automation",
- "path": "skills/klaviyo-automation",
+ "path": "skills\\klaviyo-automation",
"category": "uncategorized",
"name": "klaviyo-automation",
"description": "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.",
@@ -4816,7 +4915,7 @@
},
{
"id": "kotlin-coroutines-expert",
- "path": "skills/kotlin-coroutines-expert",
+ "path": "skills\\kotlin-coroutines-expert",
"category": "uncategorized",
"name": "kotlin-coroutines-expert",
"description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
@@ -4825,7 +4924,7 @@
},
{
"id": "kpi-dashboard-design",
- "path": "skills/kpi-dashboard-design",
+ "path": "skills\\kpi-dashboard-design",
"category": "uncategorized",
"name": "kpi-dashboard-design",
"description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...",
@@ -4834,16 +4933,16 @@
},
{
"id": "kubernetes-architect",
- "path": "skills/kubernetes-architect",
+ "path": "skills\\kubernetes-architect",
"category": "uncategorized",
- "name": "Kubernetes Architect",
- "description": "You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.",
+ "name": "kubernetes-architect",
+ "description": "Expert Kubernetes architect specializing in cloud-native\ninfrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise\ncontainer orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),\nprogressive delivery, multi-tenancy, and platform engineering. Handles\nsecurity, observability, cost optimization, and developer experience. Use\nPROACTIVELY for K8s architecture, GitOps implementation, or cloud-native\nplatform design.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "kubernetes-deployment",
- "path": "skills/kubernetes-deployment",
+ "path": "skills\\kubernetes-deployment",
"category": "uncategorized",
"name": "kubernetes-deployment",
"description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
@@ -4852,7 +4951,7 @@
},
{
"id": "langchain-architecture",
- "path": "skills/langchain-architecture",
+ "path": "skills\\langchain-architecture",
"category": "uncategorized",
"name": "langchain-architecture",
"description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...",
@@ -4861,7 +4960,7 @@
},
{
"id": "langfuse",
- "path": "skills/langfuse",
+ "path": "skills\\langfuse",
"category": "uncategorized",
"name": "langfuse",
"description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug...",
@@ -4870,7 +4969,7 @@
},
{
"id": "langgraph",
- "path": "skills/langgraph",
+ "path": "skills\\langgraph",
"category": "uncategorized",
"name": "langgraph",
"description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...",
@@ -4879,7 +4978,7 @@
},
{
"id": "laravel-expert",
- "path": "skills/laravel-expert",
+ "path": "skills\\laravel-expert",
"category": "uncategorized",
"name": "laravel-expert",
"description": "Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).",
@@ -4888,7 +4987,7 @@
},
{
"id": "laravel-security-audit",
- "path": "skills/laravel-security-audit",
+ "path": "skills\\laravel-security-audit",
"category": "uncategorized",
"name": "laravel-security-audit",
"description": "Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.",
@@ -4897,7 +4996,7 @@
},
{
"id": "last30days",
- "path": "skills/last30days",
+ "path": "skills\\last30days",
"category": "uncategorized",
"name": "last30days",
"description": "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.",
@@ -4906,7 +5005,7 @@
},
{
"id": "launch-strategy",
- "path": "skills/launch-strategy",
+ "path": "skills\\launch-strategy",
"category": "uncategorized",
"name": "launch-strategy",
"description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...",
@@ -4915,25 +5014,25 @@
},
{
"id": "legacy-modernizer",
- "path": "skills/legacy-modernizer",
+ "path": "skills\\legacy-modernizer",
"category": "uncategorized",
- "name": "Legacy Modernizer",
- "description": "- Working on legacy modernizer tasks or workflows - Needing guidance, best practices, or checklists for legacy modernizer",
+ "name": "legacy-modernizer",
+ "description": "Refactor legacy codebases, migrate outdated frameworks, and\nimplement gradual modernization. Handles technical debt, dependency updates,\nand backward compatibility. Use PROACTIVELY for legacy system updates,\nframework migrations, or technical debt reduction.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "legal-advisor",
- "path": "skills/legal-advisor",
+ "path": "skills\\legal-advisor",
"category": "uncategorized",
- "name": "Legal Advisor",
- "description": "- Working on legal advisor tasks or workflows - Needing guidance, best practices, or checklists for legal advisor",
+ "name": "legal-advisor",
+ "description": "Draft privacy policies, terms of service, disclaimers, and legal\nnotices. Creates GDPR-compliant texts, cookie policies, and data processing\nagreements. Use PROACTIVELY for legal documentation, compliance texts, or\nregulatory requirements.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linear-automation",
- "path": "skills/linear-automation",
+ "path": "skills\\linear-automation",
"category": "uncategorized",
"name": "linear-automation",
"description": "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.",
@@ -4942,7 +5041,7 @@
},
{
"id": "linear-claude-skill",
- "path": "skills/linear-claude-skill",
+ "path": "skills\\linear-claude-skill",
"category": "uncategorized",
"name": "linear-claude-skill",
"description": "Manage Linear issues, projects, and teams",
@@ -4951,16 +5050,25 @@
},
{
"id": "linkedin-automation",
- "path": "skills/linkedin-automation",
+ "path": "skills\\linkedin-automation",
"category": "uncategorized",
"name": "linkedin-automation",
"description": "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "linkedin-cli",
+ "path": "skills\\linkedin-cli",
+ "category": "uncategorized",
+ "name": "linkedin-cli",
+ "description": "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "linkerd-patterns",
- "path": "skills/linkerd-patterns",
+ "path": "skills\\linkerd-patterns",
"category": "uncategorized",
"name": "linkerd-patterns",
"description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ...",
@@ -4969,7 +5077,7 @@
},
{
"id": "lint-and-validate",
- "path": "skills/lint-and-validate",
+ "path": "skills\\lint-and-validate",
"category": "uncategorized",
"name": "lint-and-validate",
"description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v...",
@@ -4978,7 +5086,7 @@
},
{
"id": "linux-privilege-escalation",
- "path": "skills/linux-privilege-escalation",
+ "path": "skills\\linux-privilege-escalation",
"category": "uncategorized",
"name": "linux-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex...",
@@ -4987,7 +5095,7 @@
},
{
"id": "linux-shell-scripting",
- "path": "skills/linux-shell-scripting",
+ "path": "skills\\linux-shell-scripting",
"category": "uncategorized",
"name": "linux-shell-scripting",
"description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she...",
@@ -4996,7 +5104,7 @@
},
{
"id": "linux-troubleshooting",
- "path": "skills/linux-troubleshooting",
+ "path": "skills\\linux-troubleshooting",
"category": "uncategorized",
"name": "linux-troubleshooting",
"description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
@@ -5005,7 +5113,7 @@
},
{
"id": "llm-app-patterns",
- "path": "skills/llm-app-patterns",
+ "path": "skills\\llm-app-patterns",
"category": "uncategorized",
"name": "llm-app-patterns",
"description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin...",
@@ -5014,7 +5122,7 @@
},
{
"id": "llm-application-dev-ai-assistant",
- "path": "skills/llm-application-dev-ai-assistant",
+ "path": "skills\\llm-application-dev-ai-assistant",
"category": "uncategorized",
"name": "llm-application-dev-ai-assistant",
"description": "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur",
@@ -5023,7 +5131,7 @@
},
{
"id": "llm-application-dev-langchain-agent",
- "path": "skills/llm-application-dev-langchain-agent",
+ "path": "skills\\llm-application-dev-langchain-agent",
"category": "uncategorized",
"name": "llm-application-dev-langchain-agent",
"description": "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.",
@@ -5032,7 +5140,7 @@
},
{
"id": "llm-application-dev-prompt-optimize",
- "path": "skills/llm-application-dev-prompt-optimize",
+ "path": "skills\\llm-application-dev-prompt-optimize",
"category": "uncategorized",
"name": "llm-application-dev-prompt-optimize",
"description": "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati",
@@ -5041,16 +5149,25 @@
},
{
"id": "llm-evaluation",
- "path": "skills/llm-evaluation",
+ "path": "skills\\llm-evaluation",
"category": "uncategorized",
"name": "llm-evaluation",
"description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "logistics-exception-management",
+ "path": "skills\\logistics-exception-management",
+ "category": "uncategorized",
+ "name": "logistics-exception-management",
+ "description": "Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviours, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "loki-mode",
- "path": "skills/loki-mode",
+ "path": "skills\\loki-mode",
"category": "uncategorized",
"name": "loki-mode",
"description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...",
@@ -5059,34 +5176,34 @@
},
{
"id": "m365-agents-dotnet",
- "path": "skills/m365-agents-dotnet",
+ "path": "skills\\m365-agents-dotnet",
"category": "uncategorized",
- "name": "M365 Agents Dotnet",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft.Agents SDK with ASP.NET Core hosting, agent routing, and MSAL-based authentication.",
+ "name": "m365-agents-dotnet",
+ "description": "Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"Microsoft.Agents\", \"AddAgentApplicationOptions\", \"AgentApplication\", \"AddAgentAspNetAuthentication\", \"Copilot Studio client\", \"IAgentHttpAdapter\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "m365-agents-py",
- "path": "skills/m365-agents-py",
+ "path": "skills\\m365-agents-py",
"category": "uncategorized",
- "name": "M365 Agents Py",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft Agents SDK with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based authentication.",
+ "name": "m365-agents-py",
+ "description": "Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"microsoft_agents\", \"AgentApplication\", \"start_agent_process\", \"TurnContext\", \"Copilot Studio client\", \"CloudAdapter\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "m365-agents-ts",
- "path": "skills/m365-agents-ts",
+ "path": "skills\\m365-agents-ts",
"category": "uncategorized",
- "name": "M365 Agents Ts",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft 365 Agents SDK with Express hosting, AgentApplication routing, streaming responses, and Copilot Studio client integrations.",
+ "name": "m365-agents-ts",
+ "description": "Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: \"Microsoft 365 Agents SDK\", \"@microsoft/agents-hosting\", \"AgentApplication\", \"startServer\", \"streamingResponse\", \"Copilot Studio client\", \"@microsoft/agents-copilotstudio-client\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "machine-learning-ops-ml-pipeline",
- "path": "skills/machine-learning-ops-ml-pipeline",
+ "path": "skills\\machine-learning-ops-ml-pipeline",
"category": "uncategorized",
"name": "machine-learning-ops-ml-pipeline",
"description": "Design and implement a complete ML pipeline for: $ARGUMENTS",
@@ -5095,7 +5212,7 @@
},
{
"id": "mailchimp-automation",
- "path": "skills/mailchimp-automation",
+ "path": "skills\\mailchimp-automation",
"category": "uncategorized",
"name": "mailchimp-automation",
"description": "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5104,7 +5221,7 @@
},
{
"id": "make-automation",
- "path": "skills/make-automation",
+ "path": "skills\\make-automation",
"category": "uncategorized",
"name": "make-automation",
"description": "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.",
@@ -5113,7 +5230,7 @@
},
{
"id": "makepad-skills",
- "path": "skills/makepad-skills",
+ "path": "skills\\makepad-skills",
"category": "uncategorized",
"name": "makepad-skills",
"description": "Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.",
@@ -5122,16 +5239,16 @@
},
{
"id": "malware-analyst",
- "path": "skills/malware-analyst",
+ "path": "skills\\malware-analyst",
"category": "uncategorized",
- "name": "Malware Analyst",
- "description": "file sample.exe sha256sum sample.exe",
+ "name": "malware-analyst",
+ "description": "Expert malware analyst specializing in defensive malware research,\nthreat intelligence, and incident response. Masters sandbox analysis,\nbehavioral analysis, and malware family identification. Handles static/dynamic\nanalysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,\nthreat hunting, incident response, or security research.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "manifest",
- "path": "skills/manifest",
+ "path": "skills\\manifest",
"category": "uncategorized",
"name": "manifest",
"description": "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.",
@@ -5140,16 +5257,16 @@
},
{
"id": "market-sizing-analysis",
- "path": "skills/market-sizing-analysis",
+ "path": "skills\\market-sizing-analysis",
"category": "uncategorized",
- "name": "Market Sizing Analysis",
- "description": "Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.",
+ "name": "market-sizing-analysis",
+ "description": "This skill should be used when the user asks to \\\\\\\"calculate TAM\\\\\\\",\n\"determine SAM\", \"estimate SOM\", \"size the market\", \"calculate market\nopportunity\", \"what's the total addressable market\", or requests market sizing\nanalysis for a startup or business opportunity.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "marketing-ideas",
- "path": "skills/marketing-ideas",
+ "path": "skills\\marketing-ideas",
"category": "uncategorized",
"name": "marketing-ideas",
"description": "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.",
@@ -5158,7 +5275,7 @@
},
{
"id": "marketing-psychology",
- "path": "skills/marketing-psychology",
+ "path": "skills\\marketing-psychology",
"category": "uncategorized",
"name": "marketing-psychology",
"description": "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.",
@@ -5167,7 +5284,7 @@
},
{
"id": "mcp-builder",
- "path": "skills/mcp-builder",
+ "path": "skills\\mcp-builder",
"category": "uncategorized",
"name": "mcp-builder",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
@@ -5176,7 +5293,7 @@
},
{
"id": "mcp-builder-ms",
- "path": "skills/mcp-builder-ms",
+ "path": "skills\\mcp-builder-ms",
"category": "uncategorized",
"name": "mcp-builder-ms",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
@@ -5185,7 +5302,7 @@
},
{
"id": "memory-forensics",
- "path": "skills/memory-forensics",
+ "path": "skills\\memory-forensics",
"category": "uncategorized",
"name": "memory-forensics",
"description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...",
@@ -5194,7 +5311,7 @@
},
{
"id": "memory-safety-patterns",
- "path": "skills/memory-safety-patterns",
+ "path": "skills\\memory-safety-patterns",
"category": "uncategorized",
"name": "memory-safety-patterns",
"description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory...",
@@ -5203,7 +5320,7 @@
},
{
"id": "memory-systems",
- "path": "skills/memory-systems",
+ "path": "skills\\memory-systems",
"category": "uncategorized",
"name": "memory-systems",
"description": "Design short-term, long-term, and graph-based memory architectures",
@@ -5212,16 +5329,16 @@
},
{
"id": "mermaid-expert",
- "path": "skills/mermaid-expert",
+ "path": "skills\\mermaid-expert",
"category": "uncategorized",
- "name": "Mermaid Expert",
- "description": "- Working on mermaid expert tasks or workflows - Needing guidance, best practices, or checklists for mermaid expert",
+ "name": "mermaid-expert",
+ "description": "Create Mermaid diagrams for flowcharts, sequences, ERDs, and\narchitectures. Masters syntax for all diagram types and styling. Use\nPROACTIVELY for visual documentation, system diagrams, or process flows.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "metasploit-framework",
- "path": "skills/metasploit-framework",
+ "path": "skills\\metasploit-framework",
"category": "uncategorized",
"name": "metasploit-framework",
"description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp...",
@@ -5230,7 +5347,7 @@
},
{
"id": "micro-saas-launcher",
- "path": "skills/micro-saas-launcher",
+ "path": "skills\\micro-saas-launcher",
"category": "uncategorized",
"name": "micro-saas-launcher",
"description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t...",
@@ -5239,7 +5356,7 @@
},
{
"id": "microservices-patterns",
- "path": "skills/microservices-patterns",
+ "path": "skills\\microservices-patterns",
"category": "uncategorized",
"name": "microservices-patterns",
"description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...",
@@ -5248,16 +5365,16 @@
},
{
"id": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
- "path": "skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet",
+ "path": "skills\\microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"category": "uncategorized",
- "name": "Microsoft Azure Webjobs Extensions Authentication Events Dotnet",
- "description": "Azure Functions extension for handling Microsoft Entra ID custom authentication events.",
+ "name": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
+ "description": "Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: \"Authentication Events\", \"WebJobsAuthenticationEventsTrigger\", \"OnTokenIssuanceStart\", \"OnAttributeCollectionStart\", \"custom claims\", \"token enrichment\", \"Entra custom extension\", \"authentication extension\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "microsoft-teams-automation",
- "path": "skills/microsoft-teams-automation",
+ "path": "skills\\microsoft-teams-automation",
"category": "uncategorized",
"name": "microsoft-teams-automation",
"description": "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.",
@@ -5266,16 +5383,16 @@
},
{
"id": "minecraft-bukkit-pro",
- "path": "skills/minecraft-bukkit-pro",
+ "path": "skills\\minecraft-bukkit-pro",
"category": "uncategorized",
- "name": "Minecraft Bukkit Pro",
- "description": "- Working on minecraft bukkit pro tasks or workflows - Needing guidance, best practices, or checklists for minecraft bukkit pro",
+ "name": "minecraft-bukkit-pro",
+ "description": "Master Minecraft server plugin development with Bukkit, Spigot, and\nPaper APIs. Specializes in event-driven architecture, command systems, world\nmanipulation, player management, and performance optimization. Use PROACTIVELY\nfor plugin architecture, gameplay mechanics, server-side features, or\ncross-version compatibility.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "miro-automation",
- "path": "skills/miro-automation",
+ "path": "skills\\miro-automation",
"category": "uncategorized",
"name": "miro-automation",
"description": "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.",
@@ -5284,7 +5401,7 @@
},
{
"id": "mixpanel-automation",
- "path": "skills/mixpanel-automation",
+ "path": "skills\\mixpanel-automation",
"category": "uncategorized",
"name": "mixpanel-automation",
"description": "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.",
@@ -5293,16 +5410,16 @@
},
{
"id": "ml-engineer",
- "path": "skills/ml-engineer",
+ "path": "skills\\ml-engineer",
"category": "uncategorized",
- "name": "Ml Engineer",
- "description": "- Working on ml engineer tasks or workflows - Needing guidance, best practices, or checklists for ml engineer",
+ "name": "ml-engineer",
+ "description": "Build production ML systems with PyTorch 2.x, TensorFlow, and\nmodern ML frameworks. Implements model serving, feature engineering, A/B\ntesting, and monitoring. Use PROACTIVELY for ML model deployment, inference\noptimization, or production ML infrastructure.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ml-pipeline-workflow",
- "path": "skills/ml-pipeline-workflow",
+ "path": "skills\\ml-pipeline-workflow",
"category": "uncategorized",
"name": "ml-pipeline-workflow",
"description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod...",
@@ -5311,52 +5428,52 @@
},
{
"id": "mlops-engineer",
- "path": "skills/mlops-engineer",
+ "path": "skills\\mlops-engineer",
"category": "uncategorized",
- "name": "Mlops Engineer",
- "description": "- Working on mlops engineer tasks or workflows - Needing guidance, best practices, or checklists for mlops engineer",
+ "name": "mlops-engineer",
+ "description": "Build comprehensive ML pipelines, experiment tracking, and model\nregistries with MLflow, Kubeflow, and modern MLOps tools. Implements automated\ntraining, deployment, and monitoring across cloud platforms. Use PROACTIVELY\nfor ML infrastructure, experiment management, or pipeline automation.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-developer",
- "path": "skills/mobile-developer",
- "category": "uncategorized",
- "name": "Mobile Developer",
- "description": "- Working on mobile developer tasks or workflows - Needing guidance, best practices, or checklists for mobile developer",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-security-coder",
- "path": "skills/mobile-security-coder",
- "category": "uncategorized",
- "name": "Mobile Security Coder",
- "description": "- Working on mobile security coder tasks or workflows - Needing guidance, best practices, or checklists for mobile security coder",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mobile-design",
- "path": "skills/mobile-design",
+ "path": "skills\\mobile-design",
"category": "uncategorized",
"name": "mobile-design",
"description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "mobile-developer",
+ "path": "skills\\mobile-developer",
+ "category": "uncategorized",
+ "name": "mobile-developer",
+ "description": "Develop React Native, Flutter, or native mobile apps with modern\narchitecture patterns. Masters cross-platform development, native\nintegrations, offline sync, and app store optimization. Use PROACTIVELY for\nmobile features, cross-platform code, or app optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "mobile-games",
- "path": "skills/game-development/mobile-games",
+ "path": "skills\\game-development\\mobile-games",
"category": "game-development",
"name": "mobile-games",
"description": "Mobile game development principles. Touch input, battery, performance, app stores.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "mobile-security-coder",
+ "path": "skills\\mobile-security-coder",
+ "category": "uncategorized",
+ "name": "mobile-security-coder",
+ "description": "Expert in secure mobile coding practices specializing in input\nvalidation, WebView security, and mobile-specific security patterns. Use\nPROACTIVELY for mobile security implementations or mobile security code\nreviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "modern-javascript-patterns",
- "path": "skills/modern-javascript-patterns",
+ "path": "skills\\modern-javascript-patterns",
"category": "uncategorized",
"name": "modern-javascript-patterns",
"description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici...",
@@ -5365,7 +5482,7 @@
},
{
"id": "monday-automation",
- "path": "skills/monday-automation",
+ "path": "skills\\monday-automation",
"category": "uncategorized",
"name": "monday-automation",
"description": "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5374,7 +5491,7 @@
},
{
"id": "monorepo-architect",
- "path": "skills/monorepo-architect",
+ "path": "skills\\monorepo-architect",
"category": "uncategorized",
"name": "monorepo-architect",
"description": "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,",
@@ -5383,7 +5500,7 @@
},
{
"id": "monorepo-management",
- "path": "skills/monorepo-management",
+ "path": "skills\\monorepo-management",
"category": "uncategorized",
"name": "monorepo-management",
"description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor...",
@@ -5392,7 +5509,7 @@
},
{
"id": "moodle-external-api-development",
- "path": "skills/moodle-external-api-development",
+ "path": "skills\\moodle-external-api-development",
"category": "uncategorized",
"name": "moodle-external-api-development",
"description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...",
@@ -5401,7 +5518,7 @@
},
{
"id": "mtls-configuration",
- "path": "skills/mtls-configuration",
+ "path": "skills\\mtls-configuration",
"category": "uncategorized",
"name": "mtls-configuration",
"description": "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.",
@@ -5410,7 +5527,7 @@
},
{
"id": "multi-agent-brainstorming",
- "path": "skills/multi-agent-brainstorming",
+ "path": "skills\\multi-agent-brainstorming",
"category": "uncategorized",
"name": "multi-agent-brainstorming",
"description": "Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.",
@@ -5419,7 +5536,7 @@
},
{
"id": "multi-agent-patterns",
- "path": "skills/multi-agent-patterns",
+ "path": "skills\\multi-agent-patterns",
"category": "uncategorized",
"name": "multi-agent-patterns",
"description": "Master orchestrator, peer-to-peer, and hierarchical multi-agent architectures",
@@ -5428,7 +5545,7 @@
},
{
"id": "multi-cloud-architecture",
- "path": "skills/multi-cloud-architecture",
+ "path": "skills\\multi-cloud-architecture",
"category": "uncategorized",
"name": "multi-cloud-architecture",
"description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin...",
@@ -5437,7 +5554,7 @@
},
{
"id": "multi-platform-apps-multi-platform",
- "path": "skills/multi-platform-apps-multi-platform",
+ "path": "skills\\multi-platform-apps-multi-platform",
"category": "uncategorized",
"name": "multi-platform-apps-multi-platform",
"description": "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.",
@@ -5446,7 +5563,7 @@
},
{
"id": "multiplayer",
- "path": "skills/game-development/multiplayer",
+ "path": "skills\\game-development\\multiplayer",
"category": "game-development",
"name": "multiplayer",
"description": "Multiplayer game development principles. Architecture, networking, synchronization.",
@@ -5455,7 +5572,7 @@
},
{
"id": "n8n-code-python",
- "path": "skills/n8n-code-python",
+ "path": "skills\\n8n-code-python",
"category": "uncategorized",
"name": "n8n-code-python",
"description": "Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.",
@@ -5464,7 +5581,7 @@
},
{
"id": "n8n-mcp-tools-expert",
- "path": "skills/n8n-mcp-tools-expert",
+ "path": "skills\\n8n-mcp-tools-expert",
"category": "uncategorized",
"name": "n8n-mcp-tools-expert",
"description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele...",
@@ -5473,7 +5590,7 @@
},
{
"id": "n8n-node-configuration",
- "path": "skills/n8n-node-configuration",
+ "path": "skills\\n8n-node-configuration",
"category": "uncategorized",
"name": "n8n-node-configuration",
"description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo...",
@@ -5482,7 +5599,7 @@
},
{
"id": "nanobanana-ppt-skills",
- "path": "skills/nanobanana-ppt-skills",
+ "path": "skills\\nanobanana-ppt-skills",
"category": "uncategorized",
"name": "nanobanana-ppt-skills",
"description": "AI-powered PPT generation with document analysis and styled images",
@@ -5491,7 +5608,7 @@
},
{
"id": "neon-postgres",
- "path": "skills/neon-postgres",
+ "path": "skills\\neon-postgres",
"category": "uncategorized",
"name": "neon-postgres",
"description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres...",
@@ -5500,7 +5617,7 @@
},
{
"id": "nerdzao-elite",
- "path": "skills/nerdzao-elite",
+ "path": "skills\\nerdzao-elite",
"category": "uncategorized",
"name": "nerdzao-elite",
"description": "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.",
@@ -5509,7 +5626,7 @@
},
{
"id": "nerdzao-elite-gemini-high",
- "path": "skills/nerdzao-elite-gemini-high",
+ "path": "skills\\nerdzao-elite-gemini-high",
"category": "uncategorized",
"name": "nerdzao-elite-gemini-high",
"description": "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade m\u00e1xima e efici\u00eancia de tokens.",
@@ -5518,34 +5635,34 @@
},
{
"id": "nestjs-expert",
- "path": "skills/nestjs-expert",
+ "path": "skills\\nestjs-expert",
"category": "uncategorized",
"name": "nestjs-expert",
"description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "network-engineer",
- "path": "skills/network-engineer",
- "category": "uncategorized",
- "name": "Network Engineer",
- "description": "- Working on network engineer tasks or workflows - Needing guidance, best practices, or checklists for network engineer",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "network-101",
- "path": "skills/network-101",
+ "path": "skills\\network-101",
"category": "uncategorized",
"name": "network-101",
"description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "network-engineer",
+ "path": "skills\\network-engineer",
+ "category": "uncategorized",
+ "name": "network-engineer",
+ "description": "Expert network engineer specializing in modern cloud networking,\nsecurity architectures, and performance optimization. Masters multi-cloud\nconnectivity, service mesh, zero-trust networking, SSL/TLS, global load\nbalancing, and advanced troubleshooting. Handles CDN optimization, network\nautomation, and compliance. Use PROACTIVELY for network design, connectivity\nissues, or performance optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "nextjs-app-router-patterns",
- "path": "skills/nextjs-app-router-patterns",
+ "path": "skills\\nextjs-app-router-patterns",
"category": "uncategorized",
"name": "nextjs-app-router-patterns",
"description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...",
@@ -5554,7 +5671,7 @@
},
{
"id": "nextjs-best-practices",
- "path": "skills/nextjs-best-practices",
+ "path": "skills\\nextjs-best-practices",
"category": "uncategorized",
"name": "nextjs-best-practices",
"description": "Next.js App Router principles. Server Components, data fetching, routing patterns.",
@@ -5563,7 +5680,7 @@
},
{
"id": "nextjs-supabase-auth",
- "path": "skills/nextjs-supabase-auth",
+ "path": "skills\\nextjs-supabase-auth",
"category": "uncategorized",
"name": "nextjs-supabase-auth",
"description": "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.",
@@ -5572,7 +5689,7 @@
},
{
"id": "nft-standards",
- "path": "skills/nft-standards",
+ "path": "skills\\nft-standards",
"category": "uncategorized",
"name": "nft-standards",
"description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi...",
@@ -5581,7 +5698,7 @@
},
{
"id": "nodejs-backend-patterns",
- "path": "skills/nodejs-backend-patterns",
+ "path": "skills\\nodejs-backend-patterns",
"category": "uncategorized",
"name": "nodejs-backend-patterns",
"description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when...",
@@ -5590,7 +5707,7 @@
},
{
"id": "nodejs-best-practices",
- "path": "skills/nodejs-best-practices",
+ "path": "skills\\nodejs-best-practices",
"category": "uncategorized",
"name": "nodejs-best-practices",
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
@@ -5599,7 +5716,7 @@
},
{
"id": "nosql-expert",
- "path": "skills/nosql-expert",
+ "path": "skills\\nosql-expert",
"category": "uncategorized",
"name": "nosql-expert",
"description": "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.",
@@ -5608,7 +5725,7 @@
},
{
"id": "notebooklm",
- "path": "skills/notebooklm",
+ "path": "skills\\notebooklm",
"category": "uncategorized",
"name": "notebooklm",
"description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth....",
@@ -5617,7 +5734,7 @@
},
{
"id": "notion-automation",
- "path": "skills/notion-automation",
+ "path": "skills\\notion-automation",
"category": "uncategorized",
"name": "notion-automation",
"description": "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.",
@@ -5626,7 +5743,7 @@
},
{
"id": "notion-template-business",
- "path": "skills/notion-template-business",
+ "path": "skills\\notion-template-business",
"category": "uncategorized",
"name": "notion-template-business",
"description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market...",
@@ -5635,7 +5752,7 @@
},
{
"id": "nx-workspace-patterns",
- "path": "skills/nx-workspace-patterns",
+ "path": "skills\\nx-workspace-patterns",
"category": "uncategorized",
"name": "nx-workspace-patterns",
"description": "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.",
@@ -5644,16 +5761,16 @@
},
{
"id": "observability-engineer",
- "path": "skills/observability-engineer",
+ "path": "skills\\observability-engineer",
"category": "uncategorized",
- "name": "Observability Engineer",
- "description": "You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.",
+ "name": "observability-engineer",
+ "description": "Build production-ready monitoring, logging, and tracing systems.\nImplements comprehensive observability strategies, SLI/SLO management, and\nincident response workflows. Use PROACTIVELY for monitoring infrastructure,\nperformance optimization, or production reliability.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "observability-monitoring-monitor-setup",
- "path": "skills/observability-monitoring-monitor-setup",
+ "path": "skills\\observability-monitoring-monitor-setup",
"category": "uncategorized",
"name": "observability-monitoring-monitor-setup",
"description": "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da",
@@ -5662,7 +5779,7 @@
},
{
"id": "observability-monitoring-slo-implement",
- "path": "skills/observability-monitoring-slo-implement",
+ "path": "skills\\observability-monitoring-slo-implement",
"category": "uncategorized",
"name": "observability-monitoring-slo-implement",
"description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...",
@@ -5671,7 +5788,7 @@
},
{
"id": "observe-whatsapp",
- "path": "skills/observe-whatsapp",
+ "path": "skills\\observe-whatsapp",
"category": "uncategorized",
"name": "observe-whatsapp",
"description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f...",
@@ -5680,7 +5797,7 @@
},
{
"id": "obsidian-clipper-template-creator",
- "path": "skills/obsidian-clipper-template-creator",
+ "path": "skills\\obsidian-clipper-template-creator",
"category": "uncategorized",
"name": "obsidian-clipper-template-creator",
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.",
@@ -5689,7 +5806,7 @@
},
{
"id": "office-productivity",
- "path": "skills/office-productivity",
+ "path": "skills\\office-productivity",
"category": "uncategorized",
"name": "office-productivity",
"description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
@@ -5698,7 +5815,7 @@
},
{
"id": "on-call-handoff-patterns",
- "path": "skills/on-call-handoff-patterns",
+ "path": "skills\\on-call-handoff-patterns",
"category": "uncategorized",
"name": "on-call-handoff-patterns",
"description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro...",
@@ -5707,7 +5824,7 @@
},
{
"id": "onboarding-cro",
- "path": "skills/onboarding-cro",
+ "path": "skills\\onboarding-cro",
"category": "uncategorized",
"name": "onboarding-cro",
"description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u...",
@@ -5716,7 +5833,7 @@
},
{
"id": "one-drive-automation",
- "path": "skills/one-drive-automation",
+ "path": "skills\\one-drive-automation",
"category": "uncategorized",
"name": "one-drive-automation",
"description": "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5725,7 +5842,7 @@
},
{
"id": "openapi-spec-generation",
- "path": "skills/openapi-spec-generation",
+ "path": "skills\\openapi-spec-generation",
"category": "uncategorized",
"name": "openapi-spec-generation",
"description": "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.",
@@ -5734,7 +5851,7 @@
},
{
"id": "os-scripting",
- "path": "skills/os-scripting",
+ "path": "skills\\os-scripting",
"category": "uncategorized",
"name": "os-scripting",
"description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
@@ -5743,7 +5860,7 @@
},
{
"id": "oss-hunter",
- "path": "skills/oss-hunter",
+ "path": "skills\\oss-hunter",
"category": "uncategorized",
"name": "oss-hunter",
"description": "Automatically hunt for high-impact OSS contribution opportunities in trending repositories.",
@@ -5752,7 +5869,7 @@
},
{
"id": "outlook-automation",
- "path": "skills/outlook-automation",
+ "path": "skills\\outlook-automation",
"category": "uncategorized",
"name": "outlook-automation",
"description": "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.",
@@ -5761,7 +5878,7 @@
},
{
"id": "outlook-calendar-automation",
- "path": "skills/outlook-calendar-automation",
+ "path": "skills\\outlook-calendar-automation",
"category": "uncategorized",
"name": "outlook-calendar-automation",
"description": "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.",
@@ -5770,16 +5887,16 @@
},
{
"id": "page-cro",
- "path": "skills/page-cro",
+ "path": "skills\\page-cro",
"category": "uncategorized",
- "name": "Page Cro",
- "description": "You are an expert in **page-level conversion optimization**. Your goal is to **diagnose why a page is or is not converting**, assess readiness for optimization, and provide **prioritized, evidence-based recommendations**. You do **not** guarantee con",
+ "name": "page-cro",
+ "description": "Analyze and optimize individual pages for conversion performance. Use when the user wants to improve conversion rates, diagnose why a page is underperforming, or increase the effectiveness of marketing pages (homepage, landing pages, pricing, feature pages, or blog posts). This skill focuses on diagnosis, prioritization, and testable recommendations\u2014 not blind optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pagerduty-automation",
- "path": "skills/pagerduty-automation",
+ "path": "skills\\pagerduty-automation",
"category": "uncategorized",
"name": "pagerduty-automation",
"description": "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.",
@@ -5788,7 +5905,7 @@
},
{
"id": "paid-ads",
- "path": "skills/paid-ads",
+ "path": "skills\\paid-ads",
"category": "uncategorized",
"name": "paid-ads",
"description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '...",
@@ -5797,7 +5914,7 @@
},
{
"id": "parallel-agents",
- "path": "skills/parallel-agents",
+ "path": "skills\\parallel-agents",
"category": "uncategorized",
"name": "parallel-agents",
"description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
@@ -5806,16 +5923,16 @@
},
{
"id": "payment-integration",
- "path": "skills/payment-integration",
+ "path": "skills\\payment-integration",
"category": "uncategorized",
- "name": "Payment Integration",
- "description": "- Working on payment integration tasks or workflows - Needing guidance, best practices, or checklists for payment integration",
+ "name": "payment-integration",
+ "description": "Integrate Stripe, PayPal, and payment processors. Handles checkout\nflows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when\nimplementing payments, billing, or subscription features.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "paypal-integration",
- "path": "skills/paypal-integration",
+ "path": "skills\\paypal-integration",
"category": "uncategorized",
"name": "paypal-integration",
"description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com...",
@@ -5824,7 +5941,7 @@
},
{
"id": "paywall-upgrade-cro",
- "path": "skills/paywall-upgrade-cro",
+ "path": "skills\\paywall-upgrade-cro",
"category": "uncategorized",
"name": "paywall-upgrade-cro",
"description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,...",
@@ -5833,7 +5950,7 @@
},
{
"id": "pc-games",
- "path": "skills/game-development/pc-games",
+ "path": "skills\\game-development\\pc-games",
"category": "game-development",
"name": "pc-games",
"description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
@@ -5842,7 +5959,7 @@
},
{
"id": "pci-compliance",
- "path": "skills/pci-compliance",
+ "path": "skills\\pci-compliance",
"category": "uncategorized",
"name": "pci-compliance",
"description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ...",
@@ -5851,7 +5968,7 @@
},
{
"id": "pdf-official",
- "path": "skills/pdf-official",
+ "path": "skills\\pdf-official",
"category": "uncategorized",
"name": "pdf-official",
"description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall...",
@@ -5860,7 +5977,7 @@
},
{
"id": "pentest-checklist",
- "path": "skills/pentest-checklist",
+ "path": "skills\\pentest-checklist",
"category": "uncategorized",
"name": "pentest-checklist",
"description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll...",
@@ -5869,7 +5986,7 @@
},
{
"id": "pentest-commands",
- "path": "skills/pentest-commands",
+ "path": "skills\\pentest-commands",
"category": "uncategorized",
"name": "pentest-commands",
"description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ...",
@@ -5878,7 +5995,7 @@
},
{
"id": "performance-engineer",
- "path": "skills/performance-engineer",
+ "path": "skills\\performance-engineer",
"category": "uncategorized",
"name": "performance-engineer",
"description": "Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.",
@@ -5887,7 +6004,7 @@
},
{
"id": "performance-profiling",
- "path": "skills/performance-profiling",
+ "path": "skills\\performance-profiling",
"category": "uncategorized",
"name": "performance-profiling",
"description": "Performance profiling principles. Measurement, analysis, and optimization techniques.",
@@ -5896,7 +6013,7 @@
},
{
"id": "performance-testing-review-ai-review",
- "path": "skills/performance-testing-review-ai-review",
+ "path": "skills\\performance-testing-review-ai-review",
"category": "uncategorized",
"name": "performance-testing-review-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
@@ -5905,7 +6022,7 @@
},
{
"id": "performance-testing-review-multi-agent-review",
- "path": "skills/performance-testing-review-multi-agent-review",
+ "path": "skills\\performance-testing-review-multi-agent-review",
"category": "uncategorized",
"name": "performance-testing-review-multi-agent-review",
"description": "Use when working with performance testing review multi agent review",
@@ -5914,7 +6031,7 @@
},
{
"id": "personal-tool-builder",
- "path": "skills/personal-tool-builder",
+ "path": "skills\\personal-tool-builder",
"category": "uncategorized",
"name": "personal-tool-builder",
"description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i...",
@@ -5923,16 +6040,16 @@
},
{
"id": "php-pro",
- "path": "skills/php-pro",
+ "path": "skills\\php-pro",
"category": "uncategorized",
- "name": "Php Pro",
- "description": "- Working on php pro tasks or workflows - Needing guidance, best practices, or checklists for php pro",
+ "name": "php-pro",
+ "description": "Write idiomatic PHP code with generators, iterators, SPL data\nstructures, and modern OOP features. Use PROACTIVELY for high-performance PHP\napplications.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pipedrive-automation",
- "path": "skills/pipedrive-automation",
+ "path": "skills\\pipedrive-automation",
"category": "uncategorized",
"name": "pipedrive-automation",
"description": "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5941,7 +6058,7 @@
},
{
"id": "plaid-fintech",
- "path": "skills/plaid-fintech",
+ "path": "skills\\plaid-fintech",
"category": "uncategorized",
"name": "plaid-fintech",
"description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices...",
@@ -5950,7 +6067,7 @@
},
{
"id": "plan-writing",
- "path": "skills/plan-writing",
+ "path": "skills\\plan-writing",
"category": "uncategorized",
"name": "plan-writing",
"description": "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.",
@@ -5959,7 +6076,7 @@
},
{
"id": "planning-with-files",
- "path": "skills/planning-with-files",
+ "path": "skills\\planning-with-files",
"category": "uncategorized",
"name": "planning-with-files",
"description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin...",
@@ -5968,7 +6085,7 @@
},
{
"id": "playwright-skill",
- "path": "skills/playwright-skill",
+ "path": "skills\\playwright-skill",
"category": "uncategorized",
"name": "playwright-skill",
"description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...",
@@ -5977,7 +6094,7 @@
},
{
"id": "podcast-generation",
- "path": "skills/podcast-generation",
+ "path": "skills\\podcast-generation",
"category": "uncategorized",
"name": "podcast-generation",
"description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio...",
@@ -5986,7 +6103,7 @@
},
{
"id": "popup-cro",
- "path": "skills/popup-cro",
+ "path": "skills\\popup-cro",
"category": "uncategorized",
"name": "popup-cro",
"description": "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.",
@@ -5995,16 +6112,16 @@
},
{
"id": "posix-shell-pro",
- "path": "skills/posix-shell-pro",
+ "path": "skills\\posix-shell-pro",
"category": "uncategorized",
- "name": "Posix Shell Pro",
- "description": "- Working on posix shell pro tasks or workflows - Needing guidance, best practices, or checklists for posix shell pro",
+ "name": "posix-shell-pro",
+ "description": "Expert in strict POSIX sh scripting for maximum portability across\nUnix-like systems. Specializes in shell scripts that run on any\nPOSIX-compliant shell (dash, ash, sh, bash --posix).\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "postgres-best-practices",
- "path": "skills/postgres-best-practices",
+ "path": "skills\\postgres-best-practices",
"category": "uncategorized",
"name": "postgres-best-practices",
"description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
@@ -6013,7 +6130,7 @@
},
{
"id": "postgresql",
- "path": "skills/postgresql",
+ "path": "skills\\postgresql",
"category": "uncategorized",
"name": "postgresql",
"description": "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features",
@@ -6022,7 +6139,7 @@
},
{
"id": "postgresql-optimization",
- "path": "skills/postgresql-optimization",
+ "path": "skills\\postgresql-optimization",
"category": "uncategorized",
"name": "postgresql-optimization",
"description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
@@ -6031,7 +6148,7 @@
},
{
"id": "posthog-automation",
- "path": "skills/posthog-automation",
+ "path": "skills\\posthog-automation",
"category": "uncategorized",
"name": "posthog-automation",
"description": "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.",
@@ -6040,7 +6157,7 @@
},
{
"id": "postmark-automation",
- "path": "skills/postmark-automation",
+ "path": "skills\\postmark-automation",
"category": "uncategorized",
"name": "postmark-automation",
"description": "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.",
@@ -6049,7 +6166,7 @@
},
{
"id": "postmortem-writing",
- "path": "skills/postmortem-writing",
+ "path": "skills\\postmortem-writing",
"category": "uncategorized",
"name": "postmortem-writing",
"description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...",
@@ -6058,7 +6175,7 @@
},
{
"id": "powershell-windows",
- "path": "skills/powershell-windows",
+ "path": "skills\\powershell-windows",
"category": "uncategorized",
"name": "powershell-windows",
"description": "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.",
@@ -6067,7 +6184,7 @@
},
{
"id": "pptx-official",
- "path": "skills/pptx-official",
+ "path": "skills\\pptx-official",
"category": "uncategorized",
"name": "pptx-official",
"description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo...",
@@ -6076,7 +6193,7 @@
},
{
"id": "pricing-strategy",
- "path": "skills/pricing-strategy",
+ "path": "skills\\pricing-strategy",
"category": "uncategorized",
"name": "pricing-strategy",
"description": "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.",
@@ -6085,7 +6202,7 @@
},
{
"id": "prisma-expert",
- "path": "skills/prisma-expert",
+ "path": "skills\\prisma-expert",
"category": "uncategorized",
"name": "prisma-expert",
"description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re...",
@@ -6094,7 +6211,7 @@
},
{
"id": "privilege-escalation-methods",
- "path": "skills/privilege-escalation-methods",
+ "path": "skills\\privilege-escalation-methods",
"category": "uncategorized",
"name": "privilege-escalation-methods",
"description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K...",
@@ -6103,7 +6220,7 @@
},
{
"id": "product-manager-toolkit",
- "path": "skills/product-manager-toolkit",
+ "path": "skills\\product-manager-toolkit",
"category": "uncategorized",
"name": "product-manager-toolkit",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...",
@@ -6112,7 +6229,7 @@
},
{
"id": "production-code-audit",
- "path": "skills/production-code-audit",
+ "path": "skills\\production-code-audit",
"category": "uncategorized",
"name": "production-code-audit",
"description": "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations",
@@ -6120,17 +6237,26 @@
"source": "community"
},
{
- "id": "programmatic-seo",
- "path": "skills/programmatic-seo",
+ "id": "production-scheduling",
+ "path": "skills\\production-scheduling",
"category": "uncategorized",
- "name": "Programmatic Seo",
- "description": "---",
+ "name": "production-scheduling",
+ "description": "Codified expertise for production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimising changeovers, responding to disruptions, or balancing manufacturing lines.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "programmatic-seo",
+ "path": "skills\\programmatic-seo",
+ "category": "uncategorized",
+ "name": "programmatic-seo",
+ "description": "Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design\u2014not execution unless explicitly requested.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "projection-patterns",
- "path": "skills/projection-patterns",
+ "path": "skills\\projection-patterns",
"category": "uncategorized",
"name": "projection-patterns",
"description": "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.",
@@ -6139,7 +6265,7 @@
},
{
"id": "prometheus-configuration",
- "path": "skills/prometheus-configuration",
+ "path": "skills\\prometheus-configuration",
"category": "uncategorized",
"name": "prometheus-configuration",
"description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...",
@@ -6148,7 +6274,7 @@
},
{
"id": "prompt-caching",
- "path": "skills/prompt-caching",
+ "path": "skills\\prompt-caching",
"category": "uncategorized",
"name": "prompt-caching",
"description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm...",
@@ -6157,7 +6283,7 @@
},
{
"id": "prompt-engineer",
- "path": "skills/prompt-engineer",
+ "path": "skills\\prompt-engineer",
"category": "uncategorized",
"name": "prompt-engineer",
"description": "Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)",
@@ -6166,7 +6292,7 @@
},
{
"id": "prompt-engineering",
- "path": "skills/prompt-engineering",
+ "path": "skills\\prompt-engineering",
"category": "uncategorized",
"name": "prompt-engineering",
"description": "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.",
@@ -6175,7 +6301,7 @@
},
{
"id": "prompt-engineering-patterns",
- "path": "skills/prompt-engineering-patterns",
+ "path": "skills\\prompt-engineering-patterns",
"category": "uncategorized",
"name": "prompt-engineering-patterns",
"description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio...",
@@ -6184,7 +6310,7 @@
},
{
"id": "prompt-library",
- "path": "skills/prompt-library",
+ "path": "skills\\prompt-library",
"category": "uncategorized",
"name": "prompt-library",
"description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-...",
@@ -6193,7 +6319,7 @@
},
{
"id": "protocol-reverse-engineering",
- "path": "skills/protocol-reverse-engineering",
+ "path": "skills\\protocol-reverse-engineering",
"category": "uncategorized",
"name": "protocol-reverse-engineering",
"description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...",
@@ -6202,7 +6328,7 @@
},
{
"id": "pydantic-models-py",
- "path": "skills/pydantic-models-py",
+ "path": "skills\\pydantic-models-py",
"category": "uncategorized",
"name": "pydantic-models-py",
"description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ...",
@@ -6211,25 +6337,16 @@
},
{
"id": "pypict-skill",
- "path": "skills/pypict-skill",
+ "path": "skills\\pypict-skill",
"category": "uncategorized",
"name": "pypict-skill",
"description": "Pairwise test generation",
"risk": "safe",
"source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md"
},
- {
- "id": "python-pro",
- "path": "skills/python-pro",
- "category": "uncategorized",
- "name": "Python Pro",
- "description": "You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "python-development-python-scaffold",
- "path": "skills/python-development-python-scaffold",
+ "path": "skills\\python-development-python-scaffold",
"category": "uncategorized",
"name": "python-development-python-scaffold",
"description": "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint",
@@ -6238,7 +6355,7 @@
},
{
"id": "python-fastapi-development",
- "path": "skills/python-fastapi-development",
+ "path": "skills\\python-fastapi-development",
"category": "uncategorized",
"name": "python-fastapi-development",
"description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
@@ -6247,7 +6364,7 @@
},
{
"id": "python-packaging",
- "path": "skills/python-packaging",
+ "path": "skills\\python-packaging",
"category": "uncategorized",
"name": "python-packaging",
"description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ...",
@@ -6256,7 +6373,7 @@
},
{
"id": "python-patterns",
- "path": "skills/python-patterns",
+ "path": "skills\\python-patterns",
"category": "uncategorized",
"name": "python-patterns",
"description": "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.",
@@ -6265,16 +6382,25 @@
},
{
"id": "python-performance-optimization",
- "path": "skills/python-performance-optimization",
+ "path": "skills\\python-performance-optimization",
"category": "uncategorized",
"name": "python-performance-optimization",
"description": "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "python-pro",
+ "path": "skills\\python-pro",
+ "category": "uncategorized",
+ "name": "python-pro",
+ "description": "Master Python 3.12+ with modern features, async programming,\nperformance optimization, and production-ready practices. Expert in the latest\nPython ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY\nfor Python development, optimization, or advanced Python patterns.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "python-testing-patterns",
- "path": "skills/python-testing-patterns",
+ "path": "skills\\python-testing-patterns",
"category": "uncategorized",
"name": "python-testing-patterns",
"description": "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.",
@@ -6282,17 +6408,26 @@
"source": "community"
},
{
- "id": "quant-analyst",
- "path": "skills/quant-analyst",
+ "id": "quality-nonconformance",
+ "path": "skills\\quality-nonconformance",
"category": "uncategorized",
- "name": "Quant Analyst",
- "description": "- Working on quant analyst tasks or workflows - Needing guidance, best practices, or checklists for quant analyst",
+ "name": "quality-nonconformance",
+ "description": "Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "quant-analyst",
+ "path": "skills\\quant-analyst",
+ "category": "uncategorized",
+ "name": "quant-analyst",
+ "description": "Build financial models, backtest trading strategies, and analyze\nmarket data. Implements risk metrics, portfolio optimization, and statistical\narbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or\nrisk analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "radix-ui-design-system",
- "path": "skills/radix-ui-design-system",
+ "path": "skills\\radix-ui-design-system",
"category": "uncategorized",
"name": "radix-ui-design-system",
"description": "Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.",
@@ -6301,7 +6436,7 @@
},
{
"id": "rag-engineer",
- "path": "skills/rag-engineer",
+ "path": "skills\\rag-engineer",
"category": "uncategorized",
"name": "rag-engineer",
"description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ...",
@@ -6310,7 +6445,7 @@
},
{
"id": "rag-implementation",
- "path": "skills/rag-implementation",
+ "path": "skills\\rag-implementation",
"category": "uncategorized",
"name": "rag-implementation",
"description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
@@ -6319,7 +6454,7 @@
},
{
"id": "react-best-practices",
- "path": "skills/react-best-practices",
+ "path": "skills\\react-best-practices",
"category": "uncategorized",
"name": "react-best-practices",
"description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat...",
@@ -6328,7 +6463,7 @@
},
{
"id": "react-flow-architect",
- "path": "skills/react-flow-architect",
+ "path": "skills\\react-flow-architect",
"category": "uncategorized",
"name": "react-flow-architect",
"description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or...",
@@ -6337,7 +6472,7 @@
},
{
"id": "react-flow-node-ts",
- "path": "skills/react-flow-node-ts",
+ "path": "skills\\react-flow-node-ts",
"category": "uncategorized",
"name": "react-flow-node-ts",
"description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no...",
@@ -6346,7 +6481,7 @@
},
{
"id": "react-modernization",
- "path": "skills/react-modernization",
+ "path": "skills\\react-modernization",
"category": "uncategorized",
"name": "react-modernization",
"description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...",
@@ -6355,7 +6490,7 @@
},
{
"id": "react-native-architecture",
- "path": "skills/react-native-architecture",
+ "path": "skills\\react-native-architecture",
"category": "uncategorized",
"name": "react-native-architecture",
"description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...",
@@ -6364,7 +6499,7 @@
},
{
"id": "react-nextjs-development",
- "path": "skills/react-nextjs-development",
+ "path": "skills\\react-nextjs-development",
"category": "uncategorized",
"name": "react-nextjs-development",
"description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
@@ -6373,7 +6508,7 @@
},
{
"id": "react-patterns",
- "path": "skills/react-patterns",
+ "path": "skills\\react-patterns",
"category": "uncategorized",
"name": "react-patterns",
"description": "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.",
@@ -6382,7 +6517,7 @@
},
{
"id": "react-state-management",
- "path": "skills/react-state-management",
+ "path": "skills\\react-state-management",
"category": "uncategorized",
"name": "react-state-management",
"description": "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.",
@@ -6391,7 +6526,7 @@
},
{
"id": "react-ui-patterns",
- "path": "skills/react-ui-patterns",
+ "path": "skills\\react-ui-patterns",
"category": "uncategorized",
"name": "react-ui-patterns",
"description": "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.",
@@ -6400,7 +6535,7 @@
},
{
"id": "readme",
- "path": "skills/readme",
+ "path": "skills\\readme",
"category": "uncategorized",
"name": "readme",
"description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...",
@@ -6409,7 +6544,7 @@
},
{
"id": "receiving-code-review",
- "path": "skills/receiving-code-review",
+ "path": "skills\\receiving-code-review",
"category": "uncategorized",
"name": "receiving-code-review",
"description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...",
@@ -6418,7 +6553,7 @@
},
{
"id": "red-team-tactics",
- "path": "skills/red-team-tactics",
+ "path": "skills\\red-team-tactics",
"category": "uncategorized",
"name": "red-team-tactics",
"description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
@@ -6427,7 +6562,7 @@
},
{
"id": "red-team-tools",
- "path": "skills/red-team-tools",
+ "path": "skills\\red-team-tools",
"category": "uncategorized",
"name": "red-team-tools",
"description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su...",
@@ -6436,7 +6571,7 @@
},
{
"id": "reddit-automation",
- "path": "skills/reddit-automation",
+ "path": "skills\\reddit-automation",
"category": "uncategorized",
"name": "reddit-automation",
"description": "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.",
@@ -6445,16 +6580,16 @@
},
{
"id": "reference-builder",
- "path": "skills/reference-builder",
+ "path": "skills\\reference-builder",
"category": "uncategorized",
- "name": "Reference Builder",
- "description": "- Working on reference builder tasks or workflows - Needing guidance, best practices, or checklists for reference builder",
+ "name": "reference-builder",
+ "description": "Creates exhaustive technical references and API documentation.\nGenerates comprehensive parameter listings, configuration guides, and\nsearchable reference materials. Use PROACTIVELY for API docs, configuration\nreferences, or complete technical specifications.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "referral-program",
- "path": "skills/referral-program",
+ "path": "skills\\referral-program",
"category": "uncategorized",
"name": "referral-program",
"description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of...",
@@ -6463,7 +6598,7 @@
},
{
"id": "remotion-best-practices",
- "path": "skills/remotion-best-practices",
+ "path": "skills\\remotion-best-practices",
"category": "uncategorized",
"name": "remotion-best-practices",
"description": "Best practices for Remotion - Video creation in React",
@@ -6472,7 +6607,7 @@
},
{
"id": "render-automation",
- "path": "skills/render-automation",
+ "path": "skills\\render-automation",
"category": "uncategorized",
"name": "render-automation",
"description": "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.",
@@ -6481,7 +6616,7 @@
},
{
"id": "requesting-code-review",
- "path": "skills/requesting-code-review",
+ "path": "skills\\requesting-code-review",
"category": "uncategorized",
"name": "requesting-code-review",
"description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements",
@@ -6490,7 +6625,7 @@
},
{
"id": "research-engineer",
- "path": "skills/research-engineer",
+ "path": "skills\\research-engineer",
"category": "uncategorized",
"name": "research-engineer",
"description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl...",
@@ -6498,26 +6633,35 @@
"source": "community"
},
{
- "id": "reverse-engineer",
- "path": "skills/reverse-engineer",
+ "id": "returns-reverse-logistics",
+ "path": "skills\\returns-reverse-logistics",
"category": "uncategorized",
- "name": "Reverse Engineer",
- "description": "- IDAPython (IDA Pro scripting) - Ghidra scripting (Java/Python via Jython) - r2pipe (radare2 Python API) - pwntools (CTF/exploitation toolkit) - capstone (disassembly framework) - keystone (assembly framework) - unicorn (CPU emulator framework) - an",
+ "name": "returns-reverse-logistics",
+ "description": "Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "reverse-engineer",
+ "path": "skills\\reverse-engineer",
+ "category": "uncategorized",
+ "name": "reverse-engineer",
+ "description": "Expert reverse engineer specializing in binary analysis,\ndisassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,\nradare2, x64dbg, and modern RE toolchains. Handles executable analysis,\nlibrary inspection, protocol extraction, and vulnerability research. Use\nPROACTIVELY for binary analysis, CTF challenges, security research, or\nunderstanding undocumented software.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "risk-manager",
- "path": "skills/risk-manager",
+ "path": "skills\\risk-manager",
"category": "uncategorized",
- "name": "Risk Manager",
- "description": "- Working on risk manager tasks or workflows - Needing guidance, best practices, or checklists for risk manager",
+ "name": "risk-manager",
+ "description": "Monitor portfolio risk, R-multiples, and position limits. Creates\nhedging strategies, calculates expectancy, and implements stop-losses. Use\nPROACTIVELY for risk assessment, trade tracking, or portfolio protection.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "risk-metrics-calculation",
- "path": "skills/risk-metrics-calculation",
+ "path": "skills\\risk-metrics-calculation",
"category": "uncategorized",
"name": "risk-metrics-calculation",
"description": "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.",
@@ -6526,34 +6670,34 @@
},
{
"id": "ruby-pro",
- "path": "skills/ruby-pro",
+ "path": "skills\\ruby-pro",
"category": "uncategorized",
- "name": "Ruby Pro",
- "description": "- Working on ruby pro tasks or workflows - Needing guidance, best practices, or checklists for ruby pro",
+ "name": "ruby-pro",
+ "description": "Write idiomatic Ruby code with metaprogramming, Rails patterns, and\nperformance optimization. Specializes in Ruby on Rails, gem development, and\ntesting frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or\ncomplex Ruby features.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "rust-pro",
- "path": "skills/rust-pro",
- "category": "uncategorized",
- "name": "Rust Pro",
- "description": "You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "rust-async-patterns",
- "path": "skills/rust-async-patterns",
+ "path": "skills\\rust-async-patterns",
"category": "uncategorized",
"name": "rust-async-patterns",
"description": "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "rust-pro",
+ "path": "skills\\rust-pro",
+ "category": "uncategorized",
+ "name": "rust-pro",
+ "description": "Master Rust 1.75+ with modern async patterns, advanced type system\nfeatures, and production-ready systems programming. Expert in the latest Rust\necosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for\nRust development, performance optimization, or systems programming.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "saga-orchestration",
- "path": "skills/saga-orchestration",
+ "path": "skills\\saga-orchestration",
"category": "uncategorized",
"name": "saga-orchestration",
"description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running...",
@@ -6562,16 +6706,16 @@
},
{
"id": "sales-automator",
- "path": "skills/sales-automator",
+ "path": "skills\\sales-automator",
"category": "uncategorized",
- "name": "Sales Automator",
- "description": "- Working on sales automator tasks or workflows - Needing guidance, best practices, or checklists for sales automator",
+ "name": "sales-automator",
+ "description": "Draft cold emails, follow-ups, and proposal templates. Creates\npricing pages, case studies, and sales scripts. Use PROACTIVELY for sales\noutreach or lead nurturing.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "salesforce-automation",
- "path": "skills/salesforce-automation",
+ "path": "skills\\salesforce-automation",
"category": "uncategorized",
"name": "salesforce-automation",
"description": "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.",
@@ -6580,7 +6724,7 @@
},
{
"id": "salesforce-development",
- "path": "skills/salesforce-development",
+ "path": "skills\\salesforce-development",
"category": "uncategorized",
"name": "salesforce-development",
"description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ...",
@@ -6589,7 +6733,7 @@
},
{
"id": "sast-configuration",
- "path": "skills/sast-configuration",
+ "path": "skills\\sast-configuration",
"category": "uncategorized",
"name": "sast-configuration",
"description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut...",
@@ -6598,16 +6742,16 @@
},
{
"id": "scala-pro",
- "path": "skills/scala-pro",
+ "path": "skills\\scala-pro",
"category": "uncategorized",
- "name": "Scala Pro",
- "description": "- Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro",
+ "name": "scala-pro",
+ "description": "Master enterprise-grade Scala development with functional\nprogramming, distributed systems, and big data processing. Expert in Apache\nPekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use\nPROACTIVELY for Scala system design, performance optimization, or enterprise\nintegration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "scanning-tools",
- "path": "skills/scanning-tools",
+ "path": "skills\\scanning-tools",
"category": "uncategorized",
"name": "scanning-tools",
"description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec...",
@@ -6616,16 +6760,16 @@
},
{
"id": "schema-markup",
- "path": "skills/schema-markup",
+ "path": "skills\\schema-markup",
"category": "uncategorized",
- "name": "Schema Markup",
- "description": "---",
+ "name": "schema-markup",
+ "description": "Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "screen-reader-testing",
- "path": "skills/screen-reader-testing",
+ "path": "skills\\screen-reader-testing",
"category": "uncategorized",
"name": "screen-reader-testing",
"description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...",
@@ -6634,7 +6778,7 @@
},
{
"id": "screenshots",
- "path": "skills/screenshots",
+ "path": "skills\\screenshots",
"category": "uncategorized",
"name": "screenshots",
"description": "Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.",
@@ -6643,7 +6787,7 @@
},
{
"id": "scroll-experience",
- "path": "skills/scroll-experience",
+ "path": "skills\\scroll-experience",
"category": "uncategorized",
"name": "scroll-experience",
"description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p...",
@@ -6652,7 +6796,7 @@
},
{
"id": "search-specialist",
- "path": "skills/search-specialist",
+ "path": "skills\\search-specialist",
"category": "uncategorized",
"name": "search-specialist",
"description": "Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.",
@@ -6661,43 +6805,34 @@
},
{
"id": "secrets-management",
- "path": "skills/secrets-management",
+ "path": "skills\\secrets-management",
"category": "uncategorized",
"name": "secrets-management",
"description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "security-auditor",
- "path": "skills/security-auditor",
- "category": "uncategorized",
- "name": "Security Auditor",
- "description": "You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "security-scanning-security-sast",
- "path": "skills/security-scanning-security-sast",
- "category": "uncategorized",
- "name": "Security Scanning Security Sast",
- "description": "Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "security-audit",
- "path": "skills/security-audit",
+ "path": "skills\\security-audit",
"category": "uncategorized",
"name": "security-audit",
"description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
"risk": "safe",
"source": "personal"
},
+ {
+ "id": "security-auditor",
+ "path": "skills\\security-auditor",
+ "category": "uncategorized",
+ "name": "security-auditor",
+ "description": "Expert security auditor specializing in DevSecOps, comprehensive\ncybersecurity, and compliance frameworks. Masters vulnerability assessment,\nthreat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud\nsecurity, and security automation. Handles DevSecOps integration, compliance\n(GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits,\nDevSecOps, or compliance implementation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "security-bluebook-builder",
- "path": "skills/security-bluebook-builder",
+ "path": "skills\\security-bluebook-builder",
"category": "uncategorized",
"name": "security-bluebook-builder",
"description": "Build security Blue Books for sensitive apps",
@@ -6706,7 +6841,7 @@
},
{
"id": "security-compliance-compliance-check",
- "path": "skills/security-compliance-compliance-check",
+ "path": "skills\\security-compliance-compliance-check",
"category": "uncategorized",
"name": "security-compliance-compliance-check",
"description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...",
@@ -6715,7 +6850,7 @@
},
{
"id": "security-requirement-extraction",
- "path": "skills/security-requirement-extraction",
+ "path": "skills\\security-requirement-extraction",
"category": "uncategorized",
"name": "security-requirement-extraction",
"description": "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.",
@@ -6724,7 +6859,7 @@
},
{
"id": "security-scanning-security-dependencies",
- "path": "skills/security-scanning-security-dependencies",
+ "path": "skills\\security-scanning-security-dependencies",
"category": "uncategorized",
"name": "security-scanning-security-dependencies",
"description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass...",
@@ -6733,16 +6868,25 @@
},
{
"id": "security-scanning-security-hardening",
- "path": "skills/security-scanning-security-hardening",
+ "path": "skills\\security-scanning-security-hardening",
"category": "uncategorized",
"name": "security-scanning-security-hardening",
"description": "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "security-scanning-security-sast",
+ "path": "skills\\security-scanning-security-sast",
+ "category": "uncategorized",
+ "name": "security-scanning-security-sast",
+ "description": "Static Application Security Testing (SAST) for code vulnerability\nanalysis across multiple languages and frameworks\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "segment-automation",
- "path": "skills/segment-automation",
+ "path": "skills\\segment-automation",
"category": "uncategorized",
"name": "segment-automation",
"description": "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.",
@@ -6751,7 +6895,7 @@
},
{
"id": "segment-cdp",
- "path": "skills/segment-cdp",
+ "path": "skills\\segment-cdp",
"category": "uncategorized",
"name": "segment-cdp",
"description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...",
@@ -6760,7 +6904,7 @@
},
{
"id": "sendgrid-automation",
- "path": "skills/sendgrid-automation",
+ "path": "skills\\sendgrid-automation",
"category": "uncategorized",
"name": "sendgrid-automation",
"description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche...",
@@ -6769,7 +6913,7 @@
},
{
"id": "senior-architect",
- "path": "skills/senior-architect",
+ "path": "skills\\senior-architect",
"category": "uncategorized",
"name": "senior-architect",
"description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I...",
@@ -6778,7 +6922,7 @@
},
{
"id": "senior-fullstack",
- "path": "skills/senior-fullstack",
+ "path": "skills\\senior-fullstack",
"category": "uncategorized",
"name": "senior-fullstack",
"description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec...",
@@ -6787,7 +6931,7 @@
},
{
"id": "sentry-automation",
- "path": "skills/sentry-automation",
+ "path": "skills\\sentry-automation",
"category": "uncategorized",
"name": "sentry-automation",
"description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
@@ -6796,115 +6940,115 @@
},
{
"id": "seo-audit",
- "path": "skills/seo-audit",
+ "path": "skills\\seo-audit",
"category": "uncategorized",
- "name": "Seo Audit",
- "description": "You are an **SEO diagnostic specialist**. Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility\u2014**not to implement fixes unless explicitly requested**.",
+ "name": "seo-audit",
+ "description": "Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-authority-builder",
- "path": "skills/seo-authority-builder",
+ "path": "skills\\seo-authority-builder",
"category": "uncategorized",
- "name": "Seo Authority Builder",
- "description": "- Working on seo authority builder tasks or workflows - Needing guidance, best practices, or checklists for seo authority builder",
+ "name": "seo-authority-builder",
+ "description": "Analyzes content for E-E-A-T signals and suggests improvements to\nbuild authority and trust. Identifies missing credibility elements. Use\nPROACTIVELY for YMYL topics.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-cannibalization-detector",
- "path": "skills/seo-cannibalization-detector",
+ "path": "skills\\seo-cannibalization-detector",
"category": "uncategorized",
- "name": "Seo Cannibalization Detector",
- "description": "- Working on seo cannibalization detector tasks or workflows - Needing guidance, best practices, or checklists for seo cannibalization detector",
+ "name": "seo-cannibalization-detector",
+ "description": "Analyzes multiple provided pages to identify keyword overlap and\npotential cannibalization issues. Suggests differentiation strategies. Use\nPROACTIVELY when reviewing similar content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-auditor",
- "path": "skills/seo-content-auditor",
+ "path": "skills\\seo-content-auditor",
"category": "uncategorized",
- "name": "Seo Content Auditor",
- "description": "- Working on seo content auditor tasks or workflows - Needing guidance, best practices, or checklists for seo content auditor",
+ "name": "seo-content-auditor",
+ "description": "Analyzes provided content for quality, E-E-A-T signals, and SEO\nbest practices. Scores content and provides improvement recommendations based\non established guidelines. Use PROACTIVELY for content review.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-planner",
- "path": "skills/seo-content-planner",
+ "path": "skills\\seo-content-planner",
"category": "uncategorized",
- "name": "Seo Content Planner",
- "description": "- Working on seo content planner tasks or workflows - Needing guidance, best practices, or checklists for seo content planner",
+ "name": "seo-content-planner",
+ "description": "Creates comprehensive content outlines and topic clusters for SEO.\nPlans content calendars and identifies topic gaps. Use PROACTIVELY for content\nstrategy and planning.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-refresher",
- "path": "skills/seo-content-refresher",
+ "path": "skills\\seo-content-refresher",
"category": "uncategorized",
- "name": "Seo Content Refresher",
- "description": "- Working on seo content refresher tasks or workflows - Needing guidance, best practices, or checklists for seo content refresher",
+ "name": "seo-content-refresher",
+ "description": "Identifies outdated elements in provided content and suggests\nupdates to maintain freshness. Finds statistics, dates, and examples that need\nupdating. Use PROACTIVELY for older content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-writer",
- "path": "skills/seo-content-writer",
+ "path": "skills\\seo-content-writer",
"category": "uncategorized",
- "name": "Seo Content Writer",
- "description": "- Working on seo content writer tasks or workflows - Needing guidance, best practices, or checklists for seo content writer",
+ "name": "seo-content-writer",
+ "description": "Writes SEO-optimized content based on provided keywords and topic\nbriefs. Creates engaging, comprehensive content following best practices. Use\nPROACTIVELY for content creation tasks.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-fundamentals",
- "path": "skills/seo-fundamentals",
+ "path": "skills\\seo-fundamentals",
"category": "uncategorized",
- "name": "Seo Fundamentals",
- "description": "---",
+ "name": "seo-fundamentals",
+ "description": "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-keyword-strategist",
- "path": "skills/seo-keyword-strategist",
+ "path": "skills\\seo-keyword-strategist",
"category": "uncategorized",
- "name": "Seo Keyword Strategist",
- "description": "- Working on seo keyword strategist tasks or workflows - Needing guidance, best practices, or checklists for seo keyword strategist",
+ "name": "seo-keyword-strategist",
+ "description": "Analyzes keyword usage in provided content, calculates density,\nsuggests semantic variations and LSI keywords based on the topic. Prevents\nover-optimization. Use PROACTIVELY for content optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-meta-optimizer",
- "path": "skills/seo-meta-optimizer",
+ "path": "skills\\seo-meta-optimizer",
"category": "uncategorized",
- "name": "Seo Meta Optimizer",
- "description": "- Working on seo meta optimizer tasks or workflows - Needing guidance, best practices, or checklists for seo meta optimizer",
+ "name": "seo-meta-optimizer",
+ "description": "Creates optimized meta titles, descriptions, and URL suggestions\nbased on character limits and best practices. Generates compelling,\nkeyword-rich metadata. Use PROACTIVELY for new content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-snippet-hunter",
- "path": "skills/seo-snippet-hunter",
+ "path": "skills\\seo-snippet-hunter",
"category": "uncategorized",
- "name": "Seo Snippet Hunter",
- "description": "- Working on seo snippet hunter tasks or workflows - Needing guidance, best practices, or checklists for seo snippet hunter",
+ "name": "seo-snippet-hunter",
+ "description": "Formats content to be eligible for featured snippets and SERP\nfeatures. Creates snippet-optimized content blocks based on best practices.\nUse PROACTIVELY for question-based content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-structure-architect",
- "path": "skills/seo-structure-architect",
+ "path": "skills\\seo-structure-architect",
"category": "uncategorized",
- "name": "Seo Structure Architect",
- "description": "- Working on seo structure architect tasks or workflows - Needing guidance, best practices, or checklists for seo structure architect",
+ "name": "seo-structure-architect",
+ "description": "Analyzes and optimizes content structure including header\nhierarchy, suggests schema markup, and internal linking opportunities. Creates\nsearch-friendly content organization. Use PROACTIVELY for content structuring.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "server-management",
- "path": "skills/server-management",
+ "path": "skills\\server-management",
"category": "uncategorized",
"name": "server-management",
"description": "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.",
@@ -6913,7 +7057,7 @@
},
{
"id": "service-mesh-expert",
- "path": "skills/service-mesh-expert",
+ "path": "skills\\service-mesh-expert",
"category": "uncategorized",
"name": "service-mesh-expert",
"description": "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con",
@@ -6922,7 +7066,7 @@
},
{
"id": "service-mesh-observability",
- "path": "skills/service-mesh-observability",
+ "path": "skills\\service-mesh-observability",
"category": "uncategorized",
"name": "service-mesh-observability",
"description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL...",
@@ -6931,7 +7075,7 @@
},
{
"id": "shader-programming-glsl",
- "path": "skills/shader-programming-glsl",
+ "path": "skills\\shader-programming-glsl",
"category": "uncategorized",
"name": "shader-programming-glsl",
"description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
@@ -6940,7 +7084,7 @@
},
{
"id": "sharp-edges",
- "path": "skills/sharp-edges",
+ "path": "skills\\sharp-edges",
"category": "uncategorized",
"name": "sharp-edges",
"description": "Identify error-prone APIs and dangerous configurations",
@@ -6949,7 +7093,7 @@
},
{
"id": "shellcheck-configuration",
- "path": "skills/shellcheck-configuration",
+ "path": "skills\\shellcheck-configuration",
"category": "uncategorized",
"name": "shellcheck-configuration",
"description": "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.",
@@ -6958,7 +7102,7 @@
},
{
"id": "shodan-reconnaissance",
- "path": "skills/shodan-reconnaissance",
+ "path": "skills\\shodan-reconnaissance",
"category": "uncategorized",
"name": "shodan-reconnaissance",
"description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges...",
@@ -6967,7 +7111,7 @@
},
{
"id": "shopify-apps",
- "path": "skills/shopify-apps",
+ "path": "skills\\shopify-apps",
"category": "uncategorized",
"name": "shopify-apps",
"description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U...",
@@ -6976,7 +7120,7 @@
},
{
"id": "shopify-automation",
- "path": "skills/shopify-automation",
+ "path": "skills\\shopify-automation",
"category": "uncategorized",
"name": "shopify-automation",
"description": "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.",
@@ -6985,7 +7129,7 @@
},
{
"id": "shopify-development",
- "path": "skills/shopify-development",
+ "path": "skills\\shopify-development",
"category": "uncategorized",
"name": "shopify-development",
"description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"\n",
@@ -6994,7 +7138,7 @@
},
{
"id": "signup-flow-cro",
- "path": "skills/signup-flow-cro",
+ "path": "skills\\signup-flow-cro",
"category": "uncategorized",
"name": "signup-flow-cro",
"description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...",
@@ -7003,7 +7147,7 @@
},
{
"id": "similarity-search-patterns",
- "path": "skills/similarity-search-patterns",
+ "path": "skills\\similarity-search-patterns",
"category": "uncategorized",
"name": "similarity-search-patterns",
"description": "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.",
@@ -7012,7 +7156,7 @@
},
{
"id": "skill-creator",
- "path": "skills/skill-creator",
+ "path": "skills\\skill-creator",
"category": "uncategorized",
"name": "skill-creator",
"description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s...",
@@ -7021,7 +7165,7 @@
},
{
"id": "skill-creator-ms",
- "path": "skills/skill-creator-ms",
+ "path": "skills\\skill-creator-ms",
"category": "uncategorized",
"name": "skill-creator-ms",
"description": "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.",
@@ -7030,7 +7174,7 @@
},
{
"id": "skill-developer",
- "path": "skills/skill-developer",
+ "path": "skills\\skill-developer",
"category": "uncategorized",
"name": "skill-developer",
"description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil...",
@@ -7039,7 +7183,7 @@
},
{
"id": "skill-rails-upgrade",
- "path": "skills/skill-rails-upgrade",
+ "path": "skills\\skill-rails-upgrade",
"category": "uncategorized",
"name": "skill-rails-upgrade",
"description": "Analyze Rails apps and provide upgrade assessments",
@@ -7048,7 +7192,7 @@
},
{
"id": "skill-seekers",
- "path": "skills/skill-seekers",
+ "path": "skills\\skill-seekers",
"category": "uncategorized",
"name": "skill-seekers",
"description": "-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.",
@@ -7057,7 +7201,7 @@
},
{
"id": "slack-automation",
- "path": "skills/slack-automation",
+ "path": "skills\\slack-automation",
"category": "uncategorized",
"name": "slack-automation",
"description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica...",
@@ -7066,7 +7210,7 @@
},
{
"id": "slack-bot-builder",
- "path": "skills/slack-bot-builder",
+ "path": "skills\\slack-bot-builder",
"category": "uncategorized",
"name": "slack-bot-builder",
"description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W...",
@@ -7075,7 +7219,7 @@
},
{
"id": "slack-gif-creator",
- "path": "skills/slack-gif-creator",
+ "path": "skills\\slack-gif-creator",
"category": "uncategorized",
"name": "slack-gif-creator",
"description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"...",
@@ -7084,7 +7228,7 @@
},
{
"id": "slo-implementation",
- "path": "skills/slo-implementation",
+ "path": "skills\\slo-implementation",
"category": "uncategorized",
"name": "slo-implementation",
"description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m...",
@@ -7093,7 +7237,7 @@
},
{
"id": "smtp-penetration-testing",
- "path": "skills/smtp-penetration-testing",
+ "path": "skills\\smtp-penetration-testing",
"category": "uncategorized",
"name": "smtp-penetration-testing",
"description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre...",
@@ -7102,7 +7246,7 @@
},
{
"id": "social-content",
- "path": "skills/social-content",
+ "path": "skills\\social-content",
"category": "uncategorized",
"name": "social-content",
"description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...",
@@ -7111,7 +7255,7 @@
},
{
"id": "software-architecture",
- "path": "skills/software-architecture",
+ "path": "skills\\software-architecture",
"category": "uncategorized",
"name": "software-architecture",
"description": "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.",
@@ -7120,7 +7264,7 @@
},
{
"id": "solidity-security",
- "path": "skills/solidity-security",
+ "path": "skills\\solidity-security",
"category": "uncategorized",
"name": "solidity-security",
"description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...",
@@ -7129,25 +7273,16 @@
},
{
"id": "spark-optimization",
- "path": "skills/spark-optimization",
+ "path": "skills\\spark-optimization",
"category": "uncategorized",
"name": "spark-optimization",
"description": "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "sql-pro",
- "path": "skills/sql-pro",
- "category": "uncategorized",
- "name": "Sql Pro",
- "description": "You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "sql-injection-testing",
- "path": "skills/sql-injection-testing",
+ "path": "skills\\sql-injection-testing",
"category": "uncategorized",
"name": "sql-injection-testing",
"description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform...",
@@ -7156,16 +7291,25 @@
},
{
"id": "sql-optimization-patterns",
- "path": "skills/sql-optimization-patterns",
+ "path": "skills\\sql-optimization-patterns",
"category": "uncategorized",
"name": "sql-optimization-patterns",
"description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "sql-pro",
+ "path": "skills\\sql-pro",
+ "category": "uncategorized",
+ "name": "sql-pro",
+ "description": "Master modern SQL with cloud-native databases, OLTP/OLAP\noptimization, and advanced query techniques. Expert in performance tuning,\ndata modeling, and hybrid analytical systems. Use PROACTIVELY for database\noptimization or complex analysis.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "sqlmap-database-pentesting",
- "path": "skills/sqlmap-database-pentesting",
+ "path": "skills\\sqlmap-database-pentesting",
"category": "uncategorized",
"name": "sqlmap-database-pentesting",
"description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns...",
@@ -7174,7 +7318,7 @@
},
{
"id": "square-automation",
- "path": "skills/square-automation",
+ "path": "skills\\square-automation",
"category": "uncategorized",
"name": "square-automation",
"description": "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.",
@@ -7183,7 +7327,7 @@
},
{
"id": "ssh-penetration-testing",
- "path": "skills/ssh-penetration-testing",
+ "path": "skills\\ssh-penetration-testing",
"category": "uncategorized",
"name": "ssh-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu...",
@@ -7192,61 +7336,61 @@
},
{
"id": "startup-analyst",
- "path": "skills/startup-analyst",
+ "path": "skills\\startup-analyst",
"category": "uncategorized",
- "name": "Startup Analyst",
- "description": "- Working on startup analyst tasks or workflows - Needing guidance, best practices, or checklists for startup analyst",
+ "name": "startup-analyst",
+ "description": "Expert startup business analyst specializing in market sizing,\nfinancial modeling, competitive analysis, and strategic planning for\nearly-stage companies. Use PROACTIVELY when the user asks about market\nopportunity, TAM/SAM/SOM, financial projections, unit economics, competitive\nlandscape, team planning, startup metrics, or business strategy for pre-seed\nthrough Series A startups.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-business-case",
- "path": "skills/startup-business-analyst-business-case",
+ "path": "skills\\startup-business-analyst-business-case",
"category": "uncategorized",
- "name": "Startup Business Analyst Business Case",
- "description": "Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.",
+ "name": "startup-business-analyst-business-case",
+ "description": "Generate comprehensive investor-ready business case document with\nmarket, solution, financials, and strategy\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-financial-projections",
- "path": "skills/startup-business-analyst-financial-projections",
+ "path": "skills\\startup-business-analyst-financial-projections",
"category": "uncategorized",
- "name": "Startup Business Analyst Financial Projections",
- "description": "Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.",
+ "name": "startup-business-analyst-financial-projections",
+ "description": "Create detailed 3-5 year financial model with revenue, costs, cash\nflow, and scenarios\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-market-opportunity",
- "path": "skills/startup-business-analyst-market-opportunity",
+ "path": "skills\\startup-business-analyst-market-opportunity",
"category": "uncategorized",
- "name": "Startup Business Analyst Market Opportunity",
- "description": "Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.",
+ "name": "startup-business-analyst-market-opportunity",
+ "description": "Generate comprehensive market opportunity analysis with TAM/SAM/SOM\ncalculations\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-financial-modeling",
- "path": "skills/startup-financial-modeling",
+ "path": "skills\\startup-financial-modeling",
"category": "uncategorized",
- "name": "Startup Financial Modeling",
- "description": "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.",
+ "name": "startup-financial-modeling",
+ "description": "This skill should be used when the user asks to \\\\\\\"create financial\nprojections\", \"build a financial model\", \"forecast revenue\", \"calculate burn\nrate\", \"estimate runway\", \"model cash flow\", or requests 3-5 year financial\nplanning for a startup.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-metrics-framework",
- "path": "skills/startup-metrics-framework",
+ "path": "skills\\startup-metrics-framework",
"category": "uncategorized",
- "name": "Startup Metrics Framework",
- "description": "Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.",
+ "name": "startup-metrics-framework",
+ "description": "This skill should be used when the user asks about \\\\\\\"key startup\nmetrics\", \"SaaS metrics\", \"CAC and LTV\", \"unit economics\", \"burn multiple\",\n\"rule of 40\", \"marketplace metrics\", or requests guidance on tracking and\noptimizing business performance metrics.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "stitch-ui-design",
- "path": "skills/stitch-ui-design",
+ "path": "skills\\stitch-ui-design",
"category": "uncategorized",
"name": "stitch-ui-design",
"description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra...",
@@ -7255,7 +7399,7 @@
},
{
"id": "stride-analysis-patterns",
- "path": "skills/stride-analysis-patterns",
+ "path": "skills\\stride-analysis-patterns",
"category": "uncategorized",
"name": "stride-analysis-patterns",
"description": "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.",
@@ -7264,7 +7408,7 @@
},
{
"id": "stripe-automation",
- "path": "skills/stripe-automation",
+ "path": "skills\\stripe-automation",
"category": "uncategorized",
"name": "stripe-automation",
"description": "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.",
@@ -7273,7 +7417,7 @@
},
{
"id": "stripe-integration",
- "path": "skills/stripe-integration",
+ "path": "skills\\stripe-integration",
"category": "uncategorized",
"name": "stripe-integration",
"description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ...",
@@ -7282,7 +7426,7 @@
},
{
"id": "subagent-driven-development",
- "path": "skills/subagent-driven-development",
+ "path": "skills\\subagent-driven-development",
"category": "uncategorized",
"name": "subagent-driven-development",
"description": "Use when executing implementation plans with independent tasks in the current session",
@@ -7291,7 +7435,7 @@
},
{
"id": "supabase-automation",
- "path": "skills/supabase-automation",
+ "path": "skills\\supabase-automation",
"category": "uncategorized",
"name": "supabase-automation",
"description": "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -7300,7 +7444,7 @@
},
{
"id": "superpowers-lab",
- "path": "skills/superpowers-lab",
+ "path": "skills\\superpowers-lab",
"category": "uncategorized",
"name": "superpowers-lab",
"description": "Lab environment for Claude superpowers",
@@ -7309,7 +7453,7 @@
},
{
"id": "swiftui-expert-skill",
- "path": "skills/swiftui-expert-skill",
+ "path": "skills\\swiftui-expert-skill",
"category": "uncategorized",
"name": "swiftui-expert-skill",
"description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil...",
@@ -7318,7 +7462,7 @@
},
{
"id": "systematic-debugging",
- "path": "skills/systematic-debugging",
+ "path": "skills\\systematic-debugging",
"category": "uncategorized",
"name": "systematic-debugging",
"description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes",
@@ -7327,7 +7471,7 @@
},
{
"id": "systems-programming-rust-project",
- "path": "skills/systems-programming-rust-project",
+ "path": "skills\\systems-programming-rust-project",
"category": "uncategorized",
"name": "systems-programming-rust-project",
"description": "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing",
@@ -7336,7 +7480,7 @@
},
{
"id": "tailwind-design-system",
- "path": "skills/tailwind-design-system",
+ "path": "skills\\tailwind-design-system",
"category": "uncategorized",
"name": "tailwind-design-system",
"description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...",
@@ -7345,7 +7489,7 @@
},
{
"id": "tailwind-patterns",
- "path": "skills/tailwind-patterns",
+ "path": "skills\\tailwind-patterns",
"category": "uncategorized",
"name": "tailwind-patterns",
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.",
@@ -7354,7 +7498,7 @@
},
{
"id": "tavily-web",
- "path": "skills/tavily-web",
+ "path": "skills\\tavily-web",
"category": "uncategorized",
"name": "tavily-web",
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API",
@@ -7363,16 +7507,16 @@
},
{
"id": "tdd-orchestrator",
- "path": "skills/tdd-orchestrator",
+ "path": "skills\\tdd-orchestrator",
"category": "uncategorized",
- "name": "Tdd Orchestrator",
- "description": "- Working on tdd orchestrator tasks or workflows - Needing guidance, best practices, or checklists for tdd orchestrator",
+ "name": "tdd-orchestrator",
+ "description": "Master TDD orchestrator specializing in red-green-refactor\ndiscipline, multi-agent workflow coordination, and comprehensive test-driven\ndevelopment practices. Enforces TDD best practices across teams with\nAI-assisted testing and modern frameworks. Use PROACTIVELY for TDD\nimplementation and governance.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflow",
- "path": "skills/tdd-workflow",
+ "path": "skills\\tdd-workflow",
"category": "uncategorized",
"name": "tdd-workflow",
"description": "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.",
@@ -7381,7 +7525,7 @@
},
{
"id": "tdd-workflows-tdd-cycle",
- "path": "skills/tdd-workflows-tdd-cycle",
+ "path": "skills\\tdd-workflows-tdd-cycle",
"category": "uncategorized",
"name": "tdd-workflows-tdd-cycle",
"description": "Use when working with tdd workflows tdd cycle",
@@ -7390,7 +7534,7 @@
},
{
"id": "tdd-workflows-tdd-green",
- "path": "skills/tdd-workflows-tdd-green",
+ "path": "skills\\tdd-workflows-tdd-green",
"category": "uncategorized",
"name": "tdd-workflows-tdd-green",
"description": "Implement the minimal code needed to make failing tests pass in the TDD green phase.",
@@ -7399,7 +7543,7 @@
},
{
"id": "tdd-workflows-tdd-red",
- "path": "skills/tdd-workflows-tdd-red",
+ "path": "skills\\tdd-workflows-tdd-red",
"category": "uncategorized",
"name": "tdd-workflows-tdd-red",
"description": "Generate failing tests for the TDD red phase to define expected behavior and edge cases.",
@@ -7408,25 +7552,16 @@
},
{
"id": "tdd-workflows-tdd-refactor",
- "path": "skills/tdd-workflows-tdd-refactor",
+ "path": "skills\\tdd-workflows-tdd-refactor",
"category": "uncategorized",
"name": "tdd-workflows-tdd-refactor",
"description": "Use when working with tdd workflows tdd refactor",
"risk": "unknown",
"source": "community"
},
- {
- "id": "team-composition-analysis",
- "path": "skills/team-composition-analysis",
- "category": "uncategorized",
- "name": "Team Composition Analysis",
- "description": "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "team-collaboration-issue",
- "path": "skills/team-collaboration-issue",
+ "path": "skills\\team-collaboration-issue",
"category": "uncategorized",
"name": "team-collaboration-issue",
"description": "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an",
@@ -7435,16 +7570,25 @@
},
{
"id": "team-collaboration-standup-notes",
- "path": "skills/team-collaboration-standup-notes",
+ "path": "skills\\team-collaboration-standup-notes",
"category": "uncategorized",
"name": "team-collaboration-standup-notes",
"description": "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "team-composition-analysis",
+ "path": "skills\\team-composition-analysis",
+ "category": "uncategorized",
+ "name": "team-composition-analysis",
+ "description": "This skill should be used when the user asks to \\\\\\\"plan team\nstructure\", \"determine hiring needs\", \"design org chart\", \"calculate\ncompensation\", \"plan equity allocation\", or requests organizational design and\nheadcount planning for a startup.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "telegram-automation",
- "path": "skills/telegram-automation",
+ "path": "skills\\telegram-automation",
"category": "uncategorized",
"name": "telegram-automation",
"description": "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.",
@@ -7453,7 +7597,7 @@
},
{
"id": "telegram-bot-builder",
- "path": "skills/telegram-bot-builder",
+ "path": "skills\\telegram-bot-builder",
"category": "uncategorized",
"name": "telegram-bot-builder",
"description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...",
@@ -7462,7 +7606,7 @@
},
{
"id": "telegram-mini-app",
- "path": "skills/telegram-mini-app",
+ "path": "skills\\telegram-mini-app",
"category": "uncategorized",
"name": "telegram-mini-app",
"description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build...",
@@ -7471,7 +7615,7 @@
},
{
"id": "templates",
- "path": "skills/app-builder/templates",
+ "path": "skills\\app-builder\\templates",
"category": "app-builder",
"name": "templates",
"description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
@@ -7480,34 +7624,25 @@
},
{
"id": "temporal-python-pro",
- "path": "skills/temporal-python-pro",
+ "path": "skills\\temporal-python-pro",
"category": "uncategorized",
- "name": "Temporal Python Pro",
- "description": "- Working on temporal python pro tasks or workflows - Needing guidance, best practices, or checklists for temporal python pro",
+ "name": "temporal-python-pro",
+ "description": "Master Temporal workflow orchestration with Python SDK. Implements\ndurable workflows, saga patterns, and distributed transactions. Covers\nasync/await, testing strategies, and production deployment. Use PROACTIVELY\nfor workflow design, microservice orchestration, or long-running processes.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "temporal-python-testing",
- "path": "skills/temporal-python-testing",
+ "path": "skills\\temporal-python-testing",
"category": "uncategorized",
"name": "temporal-python-testing",
"description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "terraform-specialist",
- "path": "skills/terraform-specialist",
- "category": "uncategorized",
- "name": "Terraform Specialist",
- "description": "You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "terraform-aws-modules",
- "path": "skills/terraform-aws-modules",
+ "path": "skills\\terraform-aws-modules",
"category": "uncategorized",
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
@@ -7516,7 +7651,7 @@
},
{
"id": "terraform-infrastructure",
- "path": "skills/terraform-infrastructure",
+ "path": "skills\\terraform-infrastructure",
"category": "uncategorized",
"name": "terraform-infrastructure",
"description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
@@ -7525,7 +7660,7 @@
},
{
"id": "terraform-module-library",
- "path": "skills/terraform-module-library",
+ "path": "skills\\terraform-module-library",
"category": "uncategorized",
"name": "terraform-module-library",
"description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ...",
@@ -7534,7 +7669,7 @@
},
{
"id": "terraform-skill",
- "path": "skills/terraform-skill",
+ "path": "skills\\terraform-skill",
"category": "uncategorized",
"name": "terraform-skill",
"description": "Terraform infrastructure as code best practices",
@@ -7542,17 +7677,26 @@
"source": "https://github.com/antonbabenko/terraform-skill"
},
{
- "id": "test-automator",
- "path": "skills/test-automator",
+ "id": "terraform-specialist",
+ "path": "skills\\terraform-specialist",
"category": "uncategorized",
- "name": "Test Automator",
- "description": "- Working on test automator tasks or workflows - Needing guidance, best practices, or checklists for test automator",
+ "name": "terraform-specialist",
+ "description": "Expert Terraform/OpenTofu specialist mastering advanced IaC\nautomation, state management, and enterprise infrastructure patterns. Handles\ncomplex module design, multi-cloud deployments, GitOps workflows, policy as\ncode, and CI/CD integration. Covers migration strategies, security best\npractices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state\nmanagement, or infrastructure automation.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "test-automator",
+ "path": "skills\\test-automator",
+ "category": "uncategorized",
+ "name": "test-automator",
+ "description": "Master AI-powered test automation with modern frameworks,\nself-healing tests, and comprehensive quality engineering. Build scalable\ntesting strategies with advanced CI/CD integration. Use PROACTIVELY for\ntesting automation or quality assurance.\n",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "test-driven-development",
- "path": "skills/test-driven-development",
+ "path": "skills\\test-driven-development",
"category": "uncategorized",
"name": "test-driven-development",
"description": "Use when implementing any feature or bugfix, before writing implementation code",
@@ -7561,7 +7705,7 @@
},
{
"id": "test-fixing",
- "path": "skills/test-fixing",
+ "path": "skills\\test-fixing",
"category": "uncategorized",
"name": "test-fixing",
"description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...",
@@ -7570,7 +7714,7 @@
},
{
"id": "testing-patterns",
- "path": "skills/testing-patterns",
+ "path": "skills\\testing-patterns",
"category": "uncategorized",
"name": "testing-patterns",
"description": "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.",
@@ -7579,7 +7723,7 @@
},
{
"id": "testing-qa",
- "path": "skills/testing-qa",
+ "path": "skills\\testing-qa",
"category": "uncategorized",
"name": "testing-qa",
"description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
@@ -7588,7 +7732,7 @@
},
{
"id": "theme-factory",
- "path": "skills/theme-factory",
+ "path": "skills\\theme-factory",
"category": "uncategorized",
"name": "theme-factory",
"description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac...",
@@ -7597,7 +7741,7 @@
},
{
"id": "threat-mitigation-mapping",
- "path": "skills/threat-mitigation-mapping",
+ "path": "skills\\threat-mitigation-mapping",
"category": "uncategorized",
"name": "threat-mitigation-mapping",
"description": "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.",
@@ -7606,7 +7750,7 @@
},
{
"id": "threat-modeling-expert",
- "path": "skills/threat-modeling-expert",
+ "path": "skills\\threat-modeling-expert",
"category": "uncategorized",
"name": "threat-modeling-expert",
"description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...",
@@ -7615,7 +7759,7 @@
},
{
"id": "threejs-skills",
- "path": "skills/threejs-skills",
+ "path": "skills\\threejs-skills",
"category": "uncategorized",
"name": "threejs-skills",
"description": "Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.",
@@ -7624,7 +7768,7 @@
},
{
"id": "tiktok-automation",
- "path": "skills/tiktok-automation",
+ "path": "skills\\tiktok-automation",
"category": "uncategorized",
"name": "tiktok-automation",
"description": "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.",
@@ -7633,7 +7777,7 @@
},
{
"id": "todoist-automation",
- "path": "skills/todoist-automation",
+ "path": "skills\\todoist-automation",
"category": "uncategorized",
"name": "todoist-automation",
"description": "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -7642,7 +7786,7 @@
},
{
"id": "tool-design",
- "path": "skills/tool-design",
+ "path": "skills\\tool-design",
"category": "uncategorized",
"name": "tool-design",
"description": "Build tools that agents can use effectively, including architectural reduction patterns",
@@ -7651,7 +7795,7 @@
},
{
"id": "top-web-vulnerabilities",
- "path": "skills/top-web-vulnerabilities",
+ "path": "skills\\top-web-vulnerabilities",
"category": "uncategorized",
"name": "top-web-vulnerabilities",
"description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject...",
@@ -7660,16 +7804,16 @@
},
{
"id": "track-management",
- "path": "skills/track-management",
+ "path": "skills\\track-management",
"category": "uncategorized",
- "name": "Track Management",
- "description": "Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.",
+ "name": "track-management",
+ "description": "Use this skill when creating, managing, or working with Conductor\ntracks - the logical work units for features, bugs, and refactors. Applies to\nspec.md, plan.md, and track lifecycle operations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "trello-automation",
- "path": "skills/trello-automation",
+ "path": "skills\\trello-automation",
"category": "uncategorized",
"name": "trello-automation",
"description": "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.",
@@ -7678,7 +7822,7 @@
},
{
"id": "trigger-dev",
- "path": "skills/trigger-dev",
+ "path": "skills\\trigger-dev",
"category": "uncategorized",
"name": "trigger-dev",
"description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta...",
@@ -7687,7 +7831,7 @@
},
{
"id": "turborepo-caching",
- "path": "skills/turborepo-caching",
+ "path": "skills\\turborepo-caching",
"category": "uncategorized",
"name": "turborepo-caching",
"description": "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.",
@@ -7696,16 +7840,16 @@
},
{
"id": "tutorial-engineer",
- "path": "skills/tutorial-engineer",
+ "path": "skills\\tutorial-engineer",
"category": "uncategorized",
- "name": "Tutorial Engineer",
- "description": "- Working on tutorial engineer tasks or workflows - Needing guidance, best practices, or checklists for tutorial engineer",
+ "name": "tutorial-engineer",
+ "description": "Creates step-by-step tutorials and educational content from code.\nTransforms complex concepts into progressive learning experiences with\nhands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,\nor concept explanations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "twilio-communications",
- "path": "skills/twilio-communications",
+ "path": "skills\\twilio-communications",
"category": "uncategorized",
"name": "twilio-communications",
"description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a...",
@@ -7714,34 +7858,16 @@
},
{
"id": "twitter-automation",
- "path": "skills/twitter-automation",
+ "path": "skills\\twitter-automation",
"category": "uncategorized",
"name": "twitter-automation",
"description": "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "typescript-expert",
- "path": "skills/typescript-expert",
- "category": "uncategorized",
- "name": "Typescript Expert",
- "description": "You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "typescript-pro",
- "path": "skills/typescript-pro",
- "category": "uncategorized",
- "name": "Typescript Pro",
- "description": "You are a TypeScript expert specializing in advanced typing and enterprise-grade development.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "typescript-advanced-types",
- "path": "skills/typescript-advanced-types",
+ "path": "skills\\typescript-advanced-types",
"category": "uncategorized",
"name": "typescript-advanced-types",
"description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex...",
@@ -7749,44 +7875,62 @@
"source": "community"
},
{
- "id": "ui-ux-designer",
- "path": "skills/ui-ux-designer",
+ "id": "typescript-expert",
+ "path": "skills\\typescript-expert",
"category": "uncategorized",
- "name": "Ui Ux Designer",
- "description": "- Working on ui ux designer tasks or workflows - Needing guidance, best practices, or checklists for ui ux designer",
+ "name": "typescript-expert",
+ "description": "TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
- "id": "ui-visual-validator",
- "path": "skills/ui-visual-validator",
+ "id": "typescript-pro",
+ "path": "skills\\typescript-pro",
"category": "uncategorized",
- "name": "Ui Visual Validator",
- "description": "- Working on ui visual validator tasks or workflows - Needing guidance, best practices, or checklists for ui visual validator",
+ "name": "typescript-pro",
+ "description": "Master TypeScript with advanced types, generics, and strict type\nsafety. Handles complex type systems, decorators, and enterprise-grade\npatterns. Use PROACTIVELY for TypeScript architecture, type inference\noptimization, or advanced typing patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ui-skills",
- "path": "skills/ui-skills",
+ "path": "skills\\ui-skills",
"category": "uncategorized",
"name": "ui-skills",
"description": "Opinionated, evolving constraints to guide agents when building interfaces",
"risk": "safe",
"source": "https://github.com/ibelick/ui-skills"
},
+ {
+ "id": "ui-ux-designer",
+ "path": "skills\\ui-ux-designer",
+ "category": "uncategorized",
+ "name": "ui-ux-designer",
+ "description": "Create interface designs, wireframes, and design systems. Masters\nuser research, accessibility standards, and modern design tools. Specializes\nin design tokens, component libraries, and inclusive design. Use PROACTIVELY\nfor design systems, user flows, or interface optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "ui-ux-pro-max",
- "path": "skills/ui-ux-pro-max",
+ "path": "skills\\ui-ux-pro-max",
"category": "uncategorized",
"name": "ui-ux-pro-max",
"description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "ui-visual-validator",
+ "path": "skills\\ui-visual-validator",
+ "category": "uncategorized",
+ "name": "ui-visual-validator",
+ "description": "Rigorous visual validation expert specializing in UI testing,\ndesign system compliance, and accessibility verification. Masters screenshot\nanalysis, visual regression testing, and component validation. Use PROACTIVELY\nto verify UI modifications have achieved their intended goals through\ncomprehensive visual analysis.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "unit-testing-test-generate",
- "path": "skills/unit-testing-test-generate",
+ "path": "skills\\unit-testing-test-generate",
"category": "uncategorized",
"name": "unit-testing-test-generate",
"description": "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.",
@@ -7795,16 +7939,16 @@
},
{
"id": "unity-developer",
- "path": "skills/unity-developer",
+ "path": "skills\\unity-developer",
"category": "uncategorized",
- "name": "Unity Developer",
- "description": "- Working on unity developer tasks or workflows - Needing guidance, best practices, or checklists for unity developer",
+ "name": "unity-developer",
+ "description": "Build Unity games with optimized C# scripts, efficient rendering,\nand proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and\ncross-platform deployment. Handles gameplay systems, UI implementation, and\nplatform optimization. Use PROACTIVELY for Unity performance issues, game\nmechanics, or cross-platform builds.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "unity-ecs-patterns",
- "path": "skills/unity-ecs-patterns",
+ "path": "skills\\unity-ecs-patterns",
"category": "uncategorized",
"name": "unity-ecs-patterns",
"description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent...",
@@ -7813,7 +7957,7 @@
},
{
"id": "unreal-engine-cpp-pro",
- "path": "skills/unreal-engine-cpp-pro",
+ "path": "skills\\unreal-engine-cpp-pro",
"category": "uncategorized",
"name": "unreal-engine-cpp-pro",
"description": "Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.",
@@ -7822,7 +7966,7 @@
},
{
"id": "upgrading-expo",
- "path": "skills/upgrading-expo",
+ "path": "skills\\upgrading-expo",
"category": "uncategorized",
"name": "upgrading-expo",
"description": "Upgrade Expo SDK versions",
@@ -7831,7 +7975,7 @@
},
{
"id": "upstash-qstash",
- "path": "skills/upstash-qstash",
+ "path": "skills\\upstash-qstash",
"category": "uncategorized",
"name": "upstash-qstash",
"description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul...",
@@ -7840,7 +7984,7 @@
},
{
"id": "using-git-worktrees",
- "path": "skills/using-git-worktrees",
+ "path": "skills\\using-git-worktrees",
"category": "uncategorized",
"name": "using-git-worktrees",
"description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi...",
@@ -7849,7 +7993,7 @@
},
{
"id": "using-neon",
- "path": "skills/using-neon",
+ "path": "skills\\using-neon",
"category": "uncategorized",
"name": "using-neon",
"description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/...",
@@ -7858,7 +8002,7 @@
},
{
"id": "using-superpowers",
- "path": "skills/using-superpowers",
+ "path": "skills\\using-superpowers",
"category": "uncategorized",
"name": "using-superpowers",
"description": "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions",
@@ -7867,7 +8011,7 @@
},
{
"id": "uv-package-manager",
- "path": "skills/uv-package-manager",
+ "path": "skills\\uv-package-manager",
"category": "uncategorized",
"name": "uv-package-manager",
"description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...",
@@ -7876,7 +8020,7 @@
},
{
"id": "varlock-claude-skill",
- "path": "skills/varlock-claude-skill",
+ "path": "skills\\varlock-claude-skill",
"category": "uncategorized",
"name": "varlock-claude-skill",
"description": "Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits",
@@ -7885,7 +8029,7 @@
},
{
"id": "vector-database-engineer",
- "path": "skills/vector-database-engineer",
+ "path": "skills\\vector-database-engineer",
"category": "uncategorized",
"name": "vector-database-engineer",
"description": "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar",
@@ -7894,7 +8038,7 @@
},
{
"id": "vector-index-tuning",
- "path": "skills/vector-index-tuning",
+ "path": "skills\\vector-index-tuning",
"category": "uncategorized",
"name": "vector-index-tuning",
"description": "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.",
@@ -7903,7 +8047,7 @@
},
{
"id": "vercel-automation",
- "path": "skills/vercel-automation",
+ "path": "skills\\vercel-automation",
"category": "uncategorized",
"name": "vercel-automation",
"description": "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.",
@@ -7912,7 +8056,7 @@
},
{
"id": "vercel-deploy-claimable",
- "path": "skills/vercel-deploy-claimable",
+ "path": "skills\\vercel-deploy-claimable",
"category": "uncategorized",
"name": "vercel-deploy-claimable",
"description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...",
@@ -7921,7 +8065,7 @@
},
{
"id": "vercel-deployment",
- "path": "skills/vercel-deployment",
+ "path": "skills\\vercel-deployment",
"category": "uncategorized",
"name": "vercel-deployment",
"description": "Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.",
@@ -7930,7 +8074,7 @@
},
{
"id": "verification-before-completion",
- "path": "skills/verification-before-completion",
+ "path": "skills\\verification-before-completion",
"category": "uncategorized",
"name": "verification-before-completion",
"description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...",
@@ -7939,7 +8083,7 @@
},
{
"id": "vexor",
- "path": "skills/vexor",
+ "path": "skills\\vexor",
"category": "uncategorized",
"name": "vexor",
"description": "Vector-powered CLI for semantic file search with a Claude/Codex skill",
@@ -7948,7 +8092,7 @@
},
{
"id": "viral-generator-builder",
- "path": "skills/viral-generator-builder",
+ "path": "skills\\viral-generator-builder",
"category": "uncategorized",
"name": "viral-generator-builder",
"description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic...",
@@ -7957,7 +8101,7 @@
},
{
"id": "voice-agents",
- "path": "skills/voice-agents",
+ "path": "skills\\voice-agents",
"category": "uncategorized",
"name": "voice-agents",
"description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...",
@@ -7966,7 +8110,7 @@
},
{
"id": "voice-ai-development",
- "path": "skills/voice-ai-development",
+ "path": "skills\\voice-ai-development",
"category": "uncategorized",
"name": "voice-ai-development",
"description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...",
@@ -7975,7 +8119,7 @@
},
{
"id": "voice-ai-engine-development",
- "path": "skills/voice-ai-engine-development",
+ "path": "skills\\voice-ai-engine-development",
"category": "uncategorized",
"name": "voice-ai-engine-development",
"description": "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support",
@@ -7984,7 +8128,7 @@
},
{
"id": "vr-ar",
- "path": "skills/game-development/vr-ar",
+ "path": "skills\\game-development\\vr-ar",
"category": "game-development",
"name": "vr-ar",
"description": "VR/AR development principles. Comfort, interaction, performance requirements.",
@@ -7993,7 +8137,7 @@
},
{
"id": "vulnerability-scanner",
- "path": "skills/vulnerability-scanner",
+ "path": "skills\\vulnerability-scanner",
"category": "uncategorized",
"name": "vulnerability-scanner",
"description": "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.",
@@ -8002,7 +8146,7 @@
},
{
"id": "wcag-audit-patterns",
- "path": "skills/wcag-audit-patterns",
+ "path": "skills\\wcag-audit-patterns",
"category": "uncategorized",
"name": "wcag-audit-patterns",
"description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...",
@@ -8011,7 +8155,7 @@
},
{
"id": "web-artifacts-builder",
- "path": "skills/web-artifacts-builder",
+ "path": "skills\\web-artifacts-builder",
"category": "uncategorized",
"name": "web-artifacts-builder",
"description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma...",
@@ -8020,7 +8164,7 @@
},
{
"id": "web-design-guidelines",
- "path": "skills/web-design-guidelines",
+ "path": "skills\\web-design-guidelines",
"category": "uncategorized",
"name": "web-design-guidelines",
"description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga...",
@@ -8029,7 +8173,7 @@
},
{
"id": "web-games",
- "path": "skills/game-development/web-games",
+ "path": "skills\\game-development\\web-games",
"category": "game-development",
"name": "web-games",
"description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
@@ -8038,7 +8182,7 @@
},
{
"id": "web-performance-optimization",
- "path": "skills/web-performance-optimization",
+ "path": "skills\\web-performance-optimization",
"category": "uncategorized",
"name": "web-performance-optimization",
"description": "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance",
@@ -8047,7 +8191,7 @@
},
{
"id": "web-security-testing",
- "path": "skills/web-security-testing",
+ "path": "skills\\web-security-testing",
"category": "uncategorized",
"name": "web-security-testing",
"description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
@@ -8056,7 +8200,7 @@
},
{
"id": "web3-testing",
- "path": "skills/web3-testing",
+ "path": "skills\\web3-testing",
"category": "uncategorized",
"name": "web3-testing",
"description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va...",
@@ -8065,7 +8209,7 @@
},
{
"id": "webapp-testing",
- "path": "skills/webapp-testing",
+ "path": "skills\\webapp-testing",
"category": "uncategorized",
"name": "webapp-testing",
"description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...",
@@ -8074,7 +8218,7 @@
},
{
"id": "webflow-automation",
- "path": "skills/webflow-automation",
+ "path": "skills\\webflow-automation",
"category": "uncategorized",
"name": "webflow-automation",
"description": "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -8083,7 +8227,7 @@
},
{
"id": "whatsapp-automation",
- "path": "skills/whatsapp-automation",
+ "path": "skills\\whatsapp-automation",
"category": "uncategorized",
"name": "whatsapp-automation",
"description": "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.",
@@ -8092,7 +8236,7 @@
},
{
"id": "wiki-architect",
- "path": "skills/wiki-architect",
+ "path": "skills\\wiki-architect",
"category": "uncategorized",
"name": "wiki-architect",
"description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...",
@@ -8101,7 +8245,7 @@
},
{
"id": "wiki-changelog",
- "path": "skills/wiki-changelog",
+ "path": "skills\\wiki-changelog",
"category": "uncategorized",
"name": "wiki-changelog",
"description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...",
@@ -8110,7 +8254,7 @@
},
{
"id": "wiki-onboarding",
- "path": "skills/wiki-onboarding",
+ "path": "skills\\wiki-onboarding",
"category": "uncategorized",
"name": "wiki-onboarding",
"description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...",
@@ -8119,7 +8263,7 @@
},
{
"id": "wiki-page-writer",
- "path": "skills/wiki-page-writer",
+ "path": "skills\\wiki-page-writer",
"category": "uncategorized",
"name": "wiki-page-writer",
"description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...",
@@ -8128,7 +8272,7 @@
},
{
"id": "wiki-qa",
- "path": "skills/wiki-qa",
+ "path": "skills\\wiki-qa",
"category": "uncategorized",
"name": "wiki-qa",
"description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code...",
@@ -8137,7 +8281,7 @@
},
{
"id": "wiki-researcher",
- "path": "skills/wiki-researcher",
+ "path": "skills\\wiki-researcher",
"category": "uncategorized",
"name": "wiki-researcher",
"description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...",
@@ -8146,7 +8290,7 @@
},
{
"id": "wiki-vitepress",
- "path": "skills/wiki-vitepress",
+ "path": "skills\\wiki-vitepress",
"category": "uncategorized",
"name": "wiki-vitepress",
"description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...",
@@ -8155,7 +8299,7 @@
},
{
"id": "windows-privilege-escalation",
- "path": "skills/windows-privilege-escalation",
+ "path": "skills\\windows-privilege-escalation",
"category": "uncategorized",
"name": "windows-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon...",
@@ -8164,7 +8308,7 @@
},
{
"id": "wireshark-analysis",
- "path": "skills/wireshark-analysis",
+ "path": "skills\\wireshark-analysis",
"category": "uncategorized",
"name": "wireshark-analysis",
"description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete...",
@@ -8173,7 +8317,7 @@
},
{
"id": "wordpress",
- "path": "skills/wordpress",
+ "path": "skills\\wordpress",
"category": "uncategorized",
"name": "wordpress",
"description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
@@ -8182,7 +8326,7 @@
},
{
"id": "wordpress-penetration-testing",
- "path": "skills/wordpress-penetration-testing",
+ "path": "skills\\wordpress-penetration-testing",
"category": "uncategorized",
"name": "wordpress-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu...",
@@ -8191,7 +8335,7 @@
},
{
"id": "wordpress-plugin-development",
- "path": "skills/wordpress-plugin-development",
+ "path": "skills\\wordpress-plugin-development",
"category": "uncategorized",
"name": "wordpress-plugin-development",
"description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
@@ -8200,7 +8344,7 @@
},
{
"id": "wordpress-theme-development",
- "path": "skills/wordpress-theme-development",
+ "path": "skills\\wordpress-theme-development",
"category": "uncategorized",
"name": "wordpress-theme-development",
"description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
@@ -8209,25 +8353,16 @@
},
{
"id": "wordpress-woocommerce-development",
- "path": "skills/wordpress-woocommerce-development",
+ "path": "skills\\wordpress-woocommerce-development",
"category": "uncategorized",
"name": "wordpress-woocommerce-development",
"description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
"risk": "safe",
"source": "personal"
},
- {
- "id": "workflow-patterns",
- "path": "skills/workflow-patterns",
- "category": "uncategorized",
- "name": "Workflow Patterns",
- "description": "Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "workflow-automation",
- "path": "skills/workflow-automation",
+ "path": "skills\\workflow-automation",
"category": "uncategorized",
"name": "workflow-automation",
"description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor...",
@@ -8236,16 +8371,25 @@
},
{
"id": "workflow-orchestration-patterns",
- "path": "skills/workflow-orchestration-patterns",
+ "path": "skills\\workflow-orchestration-patterns",
"category": "uncategorized",
"name": "workflow-orchestration-patterns",
"description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "workflow-patterns",
+ "path": "skills\\workflow-patterns",
+ "category": "uncategorized",
+ "name": "workflow-patterns",
+ "description": "Use this skill when implementing tasks according to Conductor's TDD\nworkflow, handling phase checkpoints, managing git commits for tasks, or\nunderstanding the verification protocol.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "wrike-automation",
- "path": "skills/wrike-automation",
+ "path": "skills\\wrike-automation",
"category": "uncategorized",
"name": "wrike-automation",
"description": "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.",
@@ -8254,7 +8398,7 @@
},
{
"id": "writer",
- "path": "skills/libreoffice/writer",
+ "path": "skills\\libreoffice\\writer",
"category": "libreoffice",
"name": "writer",
"description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
@@ -8263,7 +8407,7 @@
},
{
"id": "writing-plans",
- "path": "skills/writing-plans",
+ "path": "skills\\writing-plans",
"category": "uncategorized",
"name": "writing-plans",
"description": "Use when you have a spec or requirements for a multi-step task, before touching code",
@@ -8272,7 +8416,7 @@
},
{
"id": "writing-skills",
- "path": "skills/writing-skills",
+ "path": "skills\\writing-skills",
"category": "uncategorized",
"name": "writing-skills",
"description": "Use when creating, updating, or improving agent skills.",
@@ -8281,7 +8425,7 @@
},
{
"id": "x-article-publisher-skill",
- "path": "skills/x-article-publisher-skill",
+ "path": "skills\\x-article-publisher-skill",
"category": "uncategorized",
"name": "x-article-publisher-skill",
"description": "Publish articles to X/Twitter",
@@ -8290,7 +8434,7 @@
},
{
"id": "xlsx-official",
- "path": "skills/xlsx-official",
+ "path": "skills\\xlsx-official",
"category": "uncategorized",
"name": "xlsx-official",
"description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....",
@@ -8299,7 +8443,7 @@
},
{
"id": "xss-html-injection",
- "path": "skills/xss-html-injection",
+ "path": "skills\\xss-html-injection",
"category": "uncategorized",
"name": "xss-html-injection",
"description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection...",
@@ -8308,7 +8452,7 @@
},
{
"id": "youtube-automation",
- "path": "skills/youtube-automation",
+ "path": "skills\\youtube-automation",
"category": "uncategorized",
"name": "youtube-automation",
"description": "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.",
@@ -8317,7 +8461,7 @@
},
{
"id": "youtube-summarizer",
- "path": "skills/youtube-summarizer",
+ "path": "skills\\youtube-summarizer",
"category": "uncategorized",
"name": "youtube-summarizer",
"description": "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks",
@@ -8326,7 +8470,7 @@
},
{
"id": "zapier-make-patterns",
- "path": "skills/zapier-make-patterns",
+ "path": "skills\\zapier-make-patterns",
"category": "uncategorized",
"name": "zapier-make-patterns",
"description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...",
@@ -8335,7 +8479,7 @@
},
{
"id": "zendesk-automation",
- "path": "skills/zendesk-automation",
+ "path": "skills\\zendesk-automation",
"category": "uncategorized",
"name": "zendesk-automation",
"description": "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.",
@@ -8344,7 +8488,7 @@
},
{
"id": "zoho-crm-automation",
- "path": "skills/zoho-crm-automation",
+ "path": "skills\\zoho-crm-automation",
"category": "uncategorized",
"name": "zoho-crm-automation",
"description": "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.",
@@ -8353,7 +8497,7 @@
},
{
"id": "zoom-automation",
- "path": "skills/zoom-automation",
+ "path": "skills\\zoom-automation",
"category": "uncategorized",
"name": "zoom-automation",
"description": "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -8362,7 +8506,7 @@
},
{
"id": "zustand-store-ts",
- "path": "skills/zustand-store-ts",
+ "path": "skills\\zustand-store-ts",
"category": "uncategorized",
"name": "zustand-store-ts",
"description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...",
diff --git a/web-app/package-lock.json b/web-app/package-lock.json
index 6fa70a2a..e73341be 100644
--- a/web-app/package-lock.json
+++ b/web-app/package-lock.json
@@ -79,6 +79,7 @@
"integrity": "sha512-CGOfOJqWjg2qW/Mb6zNsDm+u5vFQ8DxXfbM09z69p5Z6+mE1ikP2jUXw+j42Pf1XTYED2Rni5f95npYeuwMDQA==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@babel/code-frame": "^7.29.0",
"@babel/generator": "^7.29.0",
@@ -1859,6 +1860,7 @@
"resolved": "https://registry.npmjs.org/@types/react/-/react-19.2.14.tgz",
"integrity": "sha512-ilcTH/UniCkMdtexkoCN0bI7pMcJDvmQFPvuPvmEaYA/NSfFTAgdUSLAoVjaRJm7+6PvcM+q1zYOwS4wTYMF9w==",
"license": "MIT",
+ "peer": true,
"dependencies": {
"csstype": "^3.2.2"
}
@@ -1921,6 +1923,7 @@
"integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
"dev": true,
"license": "MIT",
+ "peer": true,
"bin": {
"acorn": "bin/acorn"
},
@@ -2073,6 +2076,7 @@
}
],
"license": "MIT",
+ "peer": true,
"dependencies": {
"baseline-browser-mapping": "^2.9.0",
"caniuse-lite": "^1.0.30001759",
@@ -2433,6 +2437,7 @@
"integrity": "sha512-LEyamqS7W5HB3ujJyvi0HQK/dtVINZvd5mAAp9eT5S/ujByGjiZLCzPcHVzuXbpJDJF/cxwHlfceVUDZ2lnSTw==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"@eslint-community/eslint-utils": "^4.8.0",
"@eslint-community/regexpp": "^4.12.1",
@@ -4250,6 +4255,7 @@
"integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
"dev": true,
"license": "MIT",
+ "peer": true,
"engines": {
"node": ">=12"
},
@@ -4277,6 +4283,7 @@
}
],
"license": "MIT",
+ "peer": true,
"dependencies": {
"nanoid": "^3.3.11",
"picocolors": "^1.1.1",
@@ -4328,6 +4335,7 @@
"resolved": "https://registry.npmjs.org/react/-/react-19.2.4.tgz",
"integrity": "sha512-9nfp2hYpCwOjAN+8TZFGhtWEwgvWHXqESH8qT89AT/lWklpLON22Lc8pEtnpsZz7VmawabSU0gCjnj8aC0euHQ==",
"license": "MIT",
+ "peer": true,
"engines": {
"node": ">=0.10.0"
}
@@ -4337,6 +4345,7 @@
"resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.2.4.tgz",
"integrity": "sha512-AXJdLo8kgMbimY95O2aKQqsz2iWi9jMgKJhRBAxECE4IFxfcazB2LmzloIoibJI3C12IlY20+KFaLv+71bUJeQ==",
"license": "MIT",
+ "peer": true,
"dependencies": {
"scheduler": "^0.27.0"
},
@@ -4885,6 +4894,7 @@
"integrity": "sha512-w+N7Hifpc3gRjZ63vYBXA56dvvRlNWRczTdmCBBa+CotUzAPf5b7YMdMR/8CQoeYE5LX3W4wj6RYTgonm1b9DA==",
"dev": true,
"license": "MIT",
+ "peer": true,
"dependencies": {
"esbuild": "^0.27.0",
"fdir": "^6.5.0",
@@ -5027,6 +5037,7 @@
"integrity": "sha512-rftlrkhHZOcjDwkGlnUtZZkvaPHCsDATp4pGpuOOMDaTdDDXF91wuVDJoWoPsKX/3YPQ5fHuF3STjcYyKr+Qhg==",
"dev": true,
"license": "MIT",
+ "peer": true,
"funding": {
"url": "https://github.com/sponsors/colinhacks"
}
diff --git a/web-app/public/skills.json b/web-app/public/skills.json
index 10357d7e..c0ffd8e0 100644
--- a/web-app/public/skills.json
+++ b/web-app/public/skills.json
@@ -1,7 +1,25 @@
[
+ {
+ "id": "00-andruia-consultant",
+ "path": "skills\\00-andruia-consultant",
+ "category": "uncategorized",
+ "name": "00-andruia-consultant",
+ "description": "Arquitecto de Soluciones Principal y Consultor Tecnol\u00f3gico de Andru.ia. Diagnostica y traza la hoja de ruta \u00f3ptima para proyectos de IA en espa\u00f1ol.",
+ "risk": "safe",
+ "source": "personal"
+ },
+ {
+ "id": "20-andruia-niche-intelligence",
+ "path": "skills\\20-andruia-niche-intelligence",
+ "category": "uncategorized",
+ "name": "20-andruia-niche-intelligence",
+ "description": "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho espec\u00edfico de un proyecto para inyectar conocimientos, regulaciones y est\u00e1ndares \u00fanicos del sector. Act\u00edvalo tras definir el nicho.",
+ "risk": "safe",
+ "source": "personal"
+ },
{
"id": "2d-games",
- "path": "skills/game-development/2d-games",
+ "path": "skills\\game-development\\2d-games",
"category": "game-development",
"name": "2d-games",
"description": "2D game development principles. Sprites, tilemaps, physics, camera.",
@@ -10,7 +28,7 @@
},
{
"id": "3d-games",
- "path": "skills/game-development/3d-games",
+ "path": "skills\\game-development\\3d-games",
"category": "game-development",
"name": "3d-games",
"description": "3D game development principles. Rendering, shaders, physics, cameras.",
@@ -19,7 +37,7 @@
},
{
"id": "3d-web-experience",
- "path": "skills/3d-web-experience",
+ "path": "skills\\3d-web-experience",
"category": "uncategorized",
"name": "3d-web-experience",
"description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...",
@@ -28,7 +46,7 @@
},
{
"id": "ab-test-setup",
- "path": "skills/ab-test-setup",
+ "path": "skills\\ab-test-setup",
"category": "uncategorized",
"name": "ab-test-setup",
"description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.",
@@ -37,7 +55,7 @@
},
{
"id": "accessibility-compliance-accessibility-audit",
- "path": "skills/accessibility-compliance-accessibility-audit",
+ "path": "skills\\accessibility-compliance-accessibility-audit",
"category": "uncategorized",
"name": "accessibility-compliance-accessibility-audit",
"description": "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.",
@@ -46,7 +64,7 @@
},
{
"id": "active-directory-attacks",
- "path": "skills/active-directory-attacks",
+ "path": "skills\\active-directory-attacks",
"category": "uncategorized",
"name": "active-directory-attacks",
"description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ...",
@@ -55,7 +73,7 @@
},
{
"id": "activecampaign-automation",
- "path": "skills/activecampaign-automation",
+ "path": "skills\\activecampaign-automation",
"category": "uncategorized",
"name": "activecampaign-automation",
"description": "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.",
@@ -64,7 +82,7 @@
},
{
"id": "address-github-comments",
- "path": "skills/address-github-comments",
+ "path": "skills\\address-github-comments",
"category": "uncategorized",
"name": "address-github-comments",
"description": "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.",
@@ -73,7 +91,7 @@
},
{
"id": "agent-evaluation",
- "path": "skills/agent-evaluation",
+ "path": "skills\\agent-evaluation",
"category": "uncategorized",
"name": "agent-evaluation",
"description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re...",
@@ -82,7 +100,7 @@
},
{
"id": "agent-framework-azure-ai-py",
- "path": "skills/agent-framework-azure-ai-py",
+ "path": "skills\\agent-framework-azure-ai-py",
"category": "uncategorized",
"name": "agent-framework-azure-ai-py",
"description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...",
@@ -91,7 +109,7 @@
},
{
"id": "agent-manager-skill",
- "path": "skills/agent-manager-skill",
+ "path": "skills\\agent-manager-skill",
"category": "uncategorized",
"name": "agent-manager-skill",
"description": "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.",
@@ -100,7 +118,7 @@
},
{
"id": "agent-memory-mcp",
- "path": "skills/agent-memory-mcp",
+ "path": "skills\\agent-memory-mcp",
"category": "uncategorized",
"name": "agent-memory-mcp",
"description": "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).",
@@ -109,7 +127,7 @@
},
{
"id": "agent-memory-systems",
- "path": "skills/agent-memory-systems",
+ "path": "skills\\agent-memory-systems",
"category": "uncategorized",
"name": "agent-memory-systems",
"description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...",
@@ -118,7 +136,7 @@
},
{
"id": "agent-orchestration-improve-agent",
- "path": "skills/agent-orchestration-improve-agent",
+ "path": "skills\\agent-orchestration-improve-agent",
"category": "uncategorized",
"name": "agent-orchestration-improve-agent",
"description": "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.",
@@ -127,7 +145,7 @@
},
{
"id": "agent-orchestration-multi-agent-optimize",
- "path": "skills/agent-orchestration-multi-agent-optimize",
+ "path": "skills\\agent-orchestration-multi-agent-optimize",
"category": "uncategorized",
"name": "agent-orchestration-multi-agent-optimize",
"description": "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.",
@@ -136,34 +154,34 @@
},
{
"id": "agent-tool-builder",
- "path": "skills/agent-tool-builder",
+ "path": "skills\\agent-tool-builder",
"category": "uncategorized",
"name": "agent-tool-builder",
"description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "agentfolio",
+ "path": "skills\\agentfolio",
+ "category": "uncategorized",
+ "name": "agentfolio",
+ "description": "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.",
+ "risk": "unknown",
+ "source": "agentfolio.io"
+ },
{
"id": "agents-v2-py",
- "path": "skills/agents-v2-py",
+ "path": "skills\\agents-v2-py",
"category": "uncategorized",
"name": "agents-v2-py",
"description": "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "ai-engineer",
- "path": "skills/ai-engineer",
- "category": "uncategorized",
- "name": "Ai Engineer",
- "description": "You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "ai-agent-development",
- "path": "skills/ai-agent-development",
+ "path": "skills\\ai-agent-development",
"category": "uncategorized",
"name": "ai-agent-development",
"description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
@@ -172,16 +190,25 @@
},
{
"id": "ai-agents-architect",
- "path": "skills/ai-agents-architect",
+ "path": "skills\\ai-agents-architect",
"category": "uncategorized",
"name": "ai-agents-architect",
"description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "ai-engineer",
+ "path": "skills\\ai-engineer",
+ "category": "uncategorized",
+ "name": "ai-engineer",
+ "description": "Build production-ready LLM applications, advanced RAG systems, and\nintelligent agents. Implements vector search, multimodal AI, agent\norchestration, and enterprise AI integrations. Use PROACTIVELY for LLM\nfeatures, chatbots, AI agents, or AI-powered applications.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "ai-ml",
- "path": "skills/ai-ml",
+ "path": "skills\\ai-ml",
"category": "uncategorized",
"name": "ai-ml",
"description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
@@ -190,7 +217,7 @@
},
{
"id": "ai-product",
- "path": "skills/ai-product",
+ "path": "skills\\ai-product",
"category": "uncategorized",
"name": "ai-product",
"description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ...",
@@ -199,7 +226,7 @@
},
{
"id": "ai-wrapper-product",
- "path": "skills/ai-wrapper-product",
+ "path": "skills\\ai-wrapper-product",
"category": "uncategorized",
"name": "ai-wrapper-product",
"description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...",
@@ -208,7 +235,7 @@
},
{
"id": "airflow-dag-patterns",
- "path": "skills/airflow-dag-patterns",
+ "path": "skills\\airflow-dag-patterns",
"category": "uncategorized",
"name": "airflow-dag-patterns",
"description": "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.",
@@ -217,7 +244,7 @@
},
{
"id": "airtable-automation",
- "path": "skills/airtable-automation",
+ "path": "skills\\airtable-automation",
"category": "uncategorized",
"name": "airtable-automation",
"description": "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.",
@@ -226,7 +253,7 @@
},
{
"id": "algolia-search",
- "path": "skills/algolia-search",
+ "path": "skills\\algolia-search",
"category": "uncategorized",
"name": "algolia-search",
"description": "Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.",
@@ -235,7 +262,7 @@
},
{
"id": "algorithmic-art",
- "path": "skills/algorithmic-art",
+ "path": "skills\\algorithmic-art",
"category": "uncategorized",
"name": "algorithmic-art",
"description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,...",
@@ -244,7 +271,7 @@
},
{
"id": "amplitude-automation",
- "path": "skills/amplitude-automation",
+ "path": "skills\\amplitude-automation",
"category": "uncategorized",
"name": "amplitude-automation",
"description": "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.",
@@ -253,16 +280,16 @@
},
{
"id": "analytics-tracking",
- "path": "skills/analytics-tracking",
+ "path": "skills\\analytics-tracking",
"category": "uncategorized",
- "name": "Analytics Tracking",
- "description": "You are an expert in **analytics implementation and measurement design**. Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.",
+ "name": "analytics-tracking",
+ "description": "Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation\u2014 not just firing events.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "android-jetpack-compose-expert",
- "path": "skills/android-jetpack-compose-expert",
+ "path": "skills\\android-jetpack-compose-expert",
"category": "uncategorized",
"name": "android-jetpack-compose-expert",
"description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
@@ -271,16 +298,16 @@
},
{
"id": "angular",
- "path": "skills/angular",
+ "path": "skills\\angular",
"category": "uncategorized",
- "name": "Angular",
- "description": "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration, and the latest reactive patterns.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "angular",
+ "description": "Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "angular-best-practices",
- "path": "skills/angular-best-practices",
+ "path": "skills\\angular-best-practices",
"category": "uncategorized",
"name": "angular-best-practices",
"description": "Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.",
@@ -289,7 +316,7 @@
},
{
"id": "angular-migration",
- "path": "skills/angular-migration",
+ "path": "skills\\angular-migration",
"category": "uncategorized",
"name": "angular-migration",
"description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...",
@@ -298,7 +325,7 @@
},
{
"id": "angular-state-management",
- "path": "skills/angular-state-management",
+ "path": "skills\\angular-state-management",
"category": "uncategorized",
"name": "angular-state-management",
"description": "Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.",
@@ -307,7 +334,7 @@
},
{
"id": "angular-ui-patterns",
- "path": "skills/angular-ui-patterns",
+ "path": "skills\\angular-ui-patterns",
"category": "uncategorized",
"name": "angular-ui-patterns",
"description": "Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.",
@@ -316,7 +343,7 @@
},
{
"id": "anti-reversing-techniques",
- "path": "skills/anti-reversing-techniques",
+ "path": "skills\\anti-reversing-techniques",
"category": "uncategorized",
"name": "anti-reversing-techniques",
"description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...",
@@ -325,25 +352,16 @@
},
{
"id": "antigravity-workflows",
- "path": "skills/antigravity-workflows",
+ "path": "skills\\antigravity-workflows",
"category": "uncategorized",
"name": "antigravity-workflows",
"description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
"risk": "none",
"source": "self"
},
- {
- "id": "api-documenter",
- "path": "skills/api-documenter",
- "category": "uncategorized",
- "name": "Api Documenter",
- "description": "You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "api-design-principles",
- "path": "skills/api-design-principles",
+ "path": "skills\\api-design-principles",
"category": "uncategorized",
"name": "api-design-principles",
"description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...",
@@ -352,7 +370,7 @@
},
{
"id": "api-documentation",
- "path": "skills/api-documentation",
+ "path": "skills\\api-documentation",
"category": "uncategorized",
"name": "api-documentation",
"description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
@@ -361,16 +379,25 @@
},
{
"id": "api-documentation-generator",
- "path": "skills/api-documentation-generator",
+ "path": "skills\\api-documentation-generator",
"category": "uncategorized",
"name": "api-documentation-generator",
"description": "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "api-documenter",
+ "path": "skills\\api-documenter",
+ "category": "uncategorized",
+ "name": "api-documenter",
+ "description": "Master API documentation with OpenAPI 3.1, AI-powered tools, and\nmodern developer experience practices. Create interactive docs, generate SDKs,\nand build comprehensive developer portals. Use PROACTIVELY for API\ndocumentation or developer portal creation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "api-fuzzing-bug-bounty",
- "path": "skills/api-fuzzing-bug-bounty",
+ "path": "skills\\api-fuzzing-bug-bounty",
"category": "uncategorized",
"name": "api-fuzzing-bug-bounty",
"description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b...",
@@ -379,7 +406,7 @@
},
{
"id": "api-patterns",
- "path": "skills/api-patterns",
+ "path": "skills\\api-patterns",
"category": "uncategorized",
"name": "api-patterns",
"description": "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.",
@@ -388,7 +415,7 @@
},
{
"id": "api-security-best-practices",
- "path": "skills/api-security-best-practices",
+ "path": "skills\\api-security-best-practices",
"category": "uncategorized",
"name": "api-security-best-practices",
"description": "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities",
@@ -397,7 +424,7 @@
},
{
"id": "api-security-testing",
- "path": "skills/api-security-testing",
+ "path": "skills\\api-security-testing",
"category": "uncategorized",
"name": "api-security-testing",
"description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
@@ -406,7 +433,7 @@
},
{
"id": "api-testing-observability-api-mock",
- "path": "skills/api-testing-observability-api-mock",
+ "path": "skills\\api-testing-observability-api-mock",
"category": "uncategorized",
"name": "api-testing-observability-api-mock",
"description": "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.",
@@ -415,7 +442,7 @@
},
{
"id": "app-builder",
- "path": "skills/app-builder",
+ "path": "skills\\app-builder",
"category": "uncategorized",
"name": "app-builder",
"description": "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.",
@@ -424,16 +451,25 @@
},
{
"id": "app-store-optimization",
- "path": "skills/app-store-optimization",
+ "path": "skills\\app-store-optimization",
"category": "uncategorized",
"name": "app-store-optimization",
"description": "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "appdeploy",
+ "path": "skills\\appdeploy",
+ "category": "uncategorized",
+ "name": "appdeploy",
+ "description": "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.",
+ "risk": "safe",
+ "source": "AppDeploy (MIT)"
+ },
{
"id": "application-performance-performance-optimization",
- "path": "skills/application-performance-performance-optimization",
+ "path": "skills\\application-performance-performance-optimization",
"category": "uncategorized",
"name": "application-performance-performance-optimization",
"description": "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.",
@@ -442,7 +478,7 @@
},
{
"id": "architect-review",
- "path": "skills/architect-review",
+ "path": "skills\\architect-review",
"category": "uncategorized",
"name": "architect-review",
"description": "Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.",
@@ -451,7 +487,7 @@
},
{
"id": "architecture",
- "path": "skills/architecture",
+ "path": "skills\\architecture",
"category": "uncategorized",
"name": "architecture",
"description": "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.",
@@ -460,7 +496,7 @@
},
{
"id": "architecture-decision-records",
- "path": "skills/architecture-decision-records",
+ "path": "skills\\architecture-decision-records",
"category": "uncategorized",
"name": "architecture-decision-records",
"description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...",
@@ -469,7 +505,7 @@
},
{
"id": "architecture-patterns",
- "path": "skills/architecture-patterns",
+ "path": "skills\\architecture-patterns",
"category": "uncategorized",
"name": "architecture-patterns",
"description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...",
@@ -478,16 +514,16 @@
},
{
"id": "arm-cortex-expert",
- "path": "skills/arm-cortex-expert",
+ "path": "skills\\arm-cortex-expert",
"category": "uncategorized",
- "name": "Arm Cortex Expert",
- "description": "- Working on @arm-cortex-expert tasks or workflows - Needing guidance, best practices, or checklists for @arm-cortex-expert",
+ "name": "arm-cortex-expert",
+ "description": "Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "asana-automation",
- "path": "skills/asana-automation",
+ "path": "skills\\asana-automation",
"category": "uncategorized",
"name": "asana-automation",
"description": "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.",
@@ -496,7 +532,7 @@
},
{
"id": "async-python-patterns",
- "path": "skills/async-python-patterns",
+ "path": "skills\\async-python-patterns",
"category": "uncategorized",
"name": "async-python-patterns",
"description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-...",
@@ -505,7 +541,7 @@
},
{
"id": "attack-tree-construction",
- "path": "skills/attack-tree-construction",
+ "path": "skills\\attack-tree-construction",
"category": "uncategorized",
"name": "attack-tree-construction",
"description": "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.",
@@ -514,7 +550,7 @@
},
{
"id": "audio-transcriber",
- "path": "skills/audio-transcriber",
+ "path": "skills\\audio-transcriber",
"category": "uncategorized",
"name": "audio-transcriber",
"description": "Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration",
@@ -523,7 +559,7 @@
},
{
"id": "auth-implementation-patterns",
- "path": "skills/auth-implementation-patterns",
+ "path": "skills\\auth-implementation-patterns",
"category": "uncategorized",
"name": "auth-implementation-patterns",
"description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A...",
@@ -532,7 +568,7 @@
},
{
"id": "automate-whatsapp",
- "path": "skills/automate-whatsapp",
+ "path": "skills\\automate-whatsapp",
"category": "uncategorized",
"name": "automate-whatsapp",
"description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...",
@@ -541,7 +577,7 @@
},
{
"id": "autonomous-agent-patterns",
- "path": "skills/autonomous-agent-patterns",
+ "path": "skills\\autonomous-agent-patterns",
"category": "uncategorized",
"name": "autonomous-agent-patterns",
"description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...",
@@ -550,7 +586,7 @@
},
{
"id": "autonomous-agents",
- "path": "skills/autonomous-agents",
+ "path": "skills\\autonomous-agents",
"category": "uncategorized",
"name": "autonomous-agents",
"description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'...",
@@ -559,7 +595,7 @@
},
{
"id": "avalonia-layout-zafiro",
- "path": "skills/avalonia-layout-zafiro",
+ "path": "skills\\avalonia-layout-zafiro",
"category": "uncategorized",
"name": "avalonia-layout-zafiro",
"description": "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.",
@@ -568,7 +604,7 @@
},
{
"id": "avalonia-viewmodels-zafiro",
- "path": "skills/avalonia-viewmodels-zafiro",
+ "path": "skills\\avalonia-viewmodels-zafiro",
"category": "uncategorized",
"name": "avalonia-viewmodels-zafiro",
"description": "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.",
@@ -577,7 +613,7 @@
},
{
"id": "avalonia-zafiro-development",
- "path": "skills/avalonia-zafiro-development",
+ "path": "skills\\avalonia-zafiro-development",
"category": "uncategorized",
"name": "avalonia-zafiro-development",
"description": "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.",
@@ -586,7 +622,7 @@
},
{
"id": "aws-compliance-checker",
- "path": "skills/security/aws-compliance-checker",
+ "path": "skills\\security\\aws-compliance-checker",
"category": "security",
"name": "aws-compliance-checker",
"description": "Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks",
@@ -595,7 +631,7 @@
},
{
"id": "aws-cost-cleanup",
- "path": "skills/aws-cost-cleanup",
+ "path": "skills\\aws-cost-cleanup",
"category": "uncategorized",
"name": "aws-cost-cleanup",
"description": "Automated cleanup of unused AWS resources to reduce costs",
@@ -604,7 +640,7 @@
},
{
"id": "aws-cost-optimizer",
- "path": "skills/aws-cost-optimizer",
+ "path": "skills\\aws-cost-optimizer",
"category": "uncategorized",
"name": "aws-cost-optimizer",
"description": "Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer",
@@ -613,7 +649,7 @@
},
{
"id": "aws-iam-best-practices",
- "path": "skills/security/aws-iam-best-practices",
+ "path": "skills\\security\\aws-iam-best-practices",
"category": "security",
"name": "aws-iam-best-practices",
"description": "IAM policy review, hardening, and least privilege implementation",
@@ -622,7 +658,7 @@
},
{
"id": "aws-penetration-testing",
- "path": "skills/aws-penetration-testing",
+ "path": "skills\\aws-penetration-testing",
"category": "uncategorized",
"name": "aws-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing...",
@@ -631,7 +667,7 @@
},
{
"id": "aws-secrets-rotation",
- "path": "skills/security/aws-secrets-rotation",
+ "path": "skills\\security\\aws-secrets-rotation",
"category": "security",
"name": "aws-secrets-rotation",
"description": "Automate AWS secrets rotation for RDS, API keys, and credentials",
@@ -640,7 +676,7 @@
},
{
"id": "aws-security-audit",
- "path": "skills/security/aws-security-audit",
+ "path": "skills\\security\\aws-security-audit",
"category": "security",
"name": "aws-security-audit",
"description": "Comprehensive AWS security posture assessment using AWS CLI and security best practices",
@@ -649,7 +685,7 @@
},
{
"id": "aws-serverless",
- "path": "skills/aws-serverless",
+ "path": "skills\\aws-serverless",
"category": "uncategorized",
"name": "aws-serverless",
"description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt...",
@@ -658,7 +694,7 @@
},
{
"id": "aws-skills",
- "path": "skills/aws-skills",
+ "path": "skills\\aws-skills",
"category": "uncategorized",
"name": "aws-skills",
"description": "AWS development with infrastructure automation and cloud architecture patterns",
@@ -667,7 +703,7 @@
},
{
"id": "azd-deployment",
- "path": "skills/azd-deployment",
+ "path": "skills\\azd-deployment",
"category": "uncategorized",
"name": "azd-deployment",
"description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont...",
@@ -676,727 +712,25 @@
},
{
"id": "azure-ai-agents-persistent-dotnet",
- "path": "skills/azure-ai-agents-persistent-dotnet",
+ "path": "skills\\azure-ai-agents-persistent-dotnet",
"category": "uncategorized",
- "name": "Azure Ai Agents Persistent Dotnet",
- "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
+ "name": "azure-ai-agents-persistent-dotnet",
+ "description": "Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: \"PersistentAgentsClient\", \"persistent agents\", \"agent threads\", \"agent runs\", \"streaming agents\", \"function calling agents .NET\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-agents-persistent-java",
- "path": "skills/azure-ai-agents-persistent-java",
+ "path": "skills\\azure-ai-agents-persistent-java",
"category": "uncategorized",
- "name": "Azure Ai Agents Persistent Java",
- "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
+ "name": "azure-ai-agents-persistent-java",
+ "description": "Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.\nTriggers: \"PersistentAgentsClient\", \"persistent agents java\", \"agent threads java\", \"agent runs java\", \"streaming agents java\".\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentsafety-py",
- "path": "skills/azure-ai-contentsafety-py",
- "category": "uncategorized",
- "name": "Azure Ai Contentsafety Py",
- "description": "Detect harmful user-generated and AI-generated content in applications.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-contentunderstanding-py",
- "path": "skills/azure-ai-contentunderstanding-py",
- "category": "uncategorized",
- "name": "Azure Ai Contentunderstanding Py",
- "description": "Multimodal AI service that extracts semantic content from documents, video, audio, and image files for RAG and automated workflows.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-document-intelligence-dotnet",
- "path": "skills/azure-ai-document-intelligence-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Document Intelligence Dotnet",
- "description": "Extract text, tables, and structured data from documents using prebuilt and custom models.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-ml-py",
- "path": "skills/azure-ai-ml-py",
- "category": "uncategorized",
- "name": "Azure Ai Ml Py",
- "description": "Client library for managing Azure ML resources: workspaces, jobs, models, data, and compute.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-openai-dotnet",
- "path": "skills/azure-ai-openai-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Openai Dotnet",
- "description": "Client library for Azure OpenAI Service providing access to OpenAI models including GPT-4, GPT-4o, embeddings, DALL-E, and Whisper.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-dotnet",
- "path": "skills/azure-ai-projects-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Projects Dotnet",
- "description": "High-level SDK for Azure AI Foundry project operations including agents, connections, datasets, deployments, evaluations, and indexes.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-projects-java",
- "path": "skills/azure-ai-projects-java",
- "category": "uncategorized",
- "name": "Azure Ai Projects Java",
- "description": "High-level SDK for Azure AI Foundry project management with access to connections, datasets, indexes, and evaluations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-textanalytics-py",
- "path": "skills/azure-ai-textanalytics-py",
- "category": "uncategorized",
- "name": "Azure Ai Textanalytics Py",
- "description": "Client library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-transcription-py",
- "path": "skills/azure-ai-transcription-py",
- "category": "uncategorized",
- "name": "Azure Ai Transcription Py",
- "description": "Client library for Azure AI Transcription (speech-to-text) with real-time and batch transcription.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-document-py",
- "path": "skills/azure-ai-translation-document-py",
- "category": "uncategorized",
- "name": "Azure Ai Translation Document Py",
- "description": "Client library for Azure AI Translator document translation service for batch document translation with format preservation.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-translation-text-py",
- "path": "skills/azure-ai-translation-text-py",
- "category": "uncategorized",
- "name": "Azure Ai Translation Text Py",
- "description": "Client library for Azure AI Translator text translation service for real-time text translation, transliteration, and language operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-vision-imageanalysis-py",
- "path": "skills/azure-ai-vision-imageanalysis-py",
- "category": "uncategorized",
- "name": "Azure Ai Vision Imageanalysis Py",
- "description": "Client library for Azure AI Vision 4.0 image analysis including captions, tags, objects, OCR, and more.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-dotnet",
- "path": "skills/azure-ai-voicelive-dotnet",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Dotnet",
- "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-java",
- "path": "skills/azure-ai-voicelive-java",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Java",
- "description": "Real-time, bidirectional voice conversations with AI assistants using WebSocket technology.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-ai-voicelive-ts",
- "path": "skills/azure-ai-voicelive-ts",
- "category": "uncategorized",
- "name": "Azure Ai Voicelive Ts",
- "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI in Node.js and browser environments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-java",
- "path": "skills/azure-appconfiguration-java",
- "category": "uncategorized",
- "name": "Azure Appconfiguration Java",
- "description": "Client library for Azure App Configuration, a managed service for centralizing application configurations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-appconfiguration-py",
- "path": "skills/azure-appconfiguration-py",
- "category": "uncategorized",
- "name": "Azure Appconfiguration Py",
- "description": "Centralized configuration management with feature flags and dynamic settings.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-compute-batch-java",
- "path": "skills/azure-compute-batch-java",
- "category": "uncategorized",
- "name": "Azure Compute Batch Java",
- "description": "Client library for running large-scale parallel and high-performance computing (HPC) batch jobs in Azure.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-containerregistry-py",
- "path": "skills/azure-containerregistry-py",
- "category": "uncategorized",
- "name": "Azure Containerregistry Py",
- "description": "Manage container images, artifacts, and repositories in Azure Container Registry.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-java",
- "path": "skills/azure-cosmos-java",
- "category": "uncategorized",
- "name": "Azure Cosmos Java",
- "description": "Client library for Azure Cosmos DB NoSQL API with global distribution and reactive patterns.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-py",
- "path": "skills/azure-cosmos-py",
- "category": "uncategorized",
- "name": "Azure Cosmos Py",
- "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-rust",
- "path": "skills/azure-cosmos-rust",
- "category": "uncategorized",
- "name": "Azure Cosmos Rust",
- "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-cosmos-ts",
- "path": "skills/azure-cosmos-ts",
- "category": "uncategorized",
- "name": "Azure Cosmos Ts",
- "description": "Data plane SDK for Azure Cosmos DB NoSQL API operations \u2014 CRUD on documents, queries, bulk operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-data-tables-py",
- "path": "skills/azure-data-tables-py",
- "category": "uncategorized",
- "name": "Azure Data Tables Py",
- "description": "NoSQL key-value store for structured data (Azure Storage Tables or Cosmos DB Table API).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-dotnet",
- "path": "skills/azure-eventgrid-dotnet",
- "category": "uncategorized",
- "name": "Azure Eventgrid Dotnet",
- "description": "Client library for publishing events to Azure Event Grid topics, domains, and namespaces.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventgrid-py",
- "path": "skills/azure-eventgrid-py",
- "category": "uncategorized",
- "name": "Azure Eventgrid Py",
- "description": "Event routing service for building event-driven applications with pub/sub semantics.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-dotnet",
- "path": "skills/azure-eventhub-dotnet",
- "category": "uncategorized",
- "name": "Azure Eventhub Dotnet",
- "description": "High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-py",
- "path": "skills/azure-eventhub-py",
- "category": "uncategorized",
- "name": "Azure Eventhub Py",
- "description": "Big data streaming platform for high-throughput event ingestion.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-eventhub-rust",
- "path": "skills/azure-eventhub-rust",
- "category": "uncategorized",
- "name": "Azure Eventhub Rust",
- "description": "Client library for Azure Event Hubs \u2014 big data streaming platform and event ingestion service.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-dotnet",
- "path": "skills/azure-identity-dotnet",
- "category": "uncategorized",
- "name": "Azure Identity Dotnet",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-py",
- "path": "skills/azure-identity-py",
- "category": "uncategorized",
- "name": "Azure Identity Py",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-identity-rust",
- "path": "skills/azure-identity-rust",
- "category": "uncategorized",
- "name": "Azure Identity Rust",
- "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-certificates-rust",
- "path": "skills/azure-keyvault-certificates-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Certificates Rust",
- "description": "Client library for Azure Key Vault Certificates \u2014 secure storage and management of certificates.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-keys-rust",
- "path": "skills/azure-keyvault-keys-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Keys Rust",
- "description": "Client library for Azure Key Vault Keys \u2014 secure storage and management of cryptographic keys.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-py",
- "path": "skills/azure-keyvault-py",
- "category": "uncategorized",
- "name": "Azure Keyvault Py",
- "description": "Secure storage and management for secrets, cryptographic keys, and certificates.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-keyvault-secrets-rust",
- "path": "skills/azure-keyvault-secrets-rust",
- "category": "uncategorized",
- "name": "Azure Keyvault Secrets Rust",
- "description": "Client library for Azure Key Vault Secrets \u2014 secure storage for passwords, API keys, and other secrets.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-maps-search-dotnet",
- "path": "skills/azure-maps-search-dotnet",
- "category": "uncategorized",
- "name": "Azure Maps Search Dotnet",
- "description": "Azure Maps SDK for .NET providing location-based services: geocoding, routing, rendering, geolocation, and weather.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-messaging-webpubsubservice-py",
- "path": "skills/azure-messaging-webpubsubservice-py",
- "category": "uncategorized",
- "name": "Azure Messaging Webpubsubservice Py",
- "description": "Real-time messaging with WebSocket connections at scale.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-dotnet",
- "path": "skills/azure-mgmt-apicenter-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Apicenter Dotnet",
- "description": "Centralized API inventory and governance SDK for managing APIs across your organization.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apicenter-py",
- "path": "skills/azure-mgmt-apicenter-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Apicenter Py",
- "description": "Manage API inventory, metadata, and governance in Azure API Center.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-dotnet",
- "path": "skills/azure-mgmt-apimanagement-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Apimanagement Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure API Management resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-apimanagement-py",
- "path": "skills/azure-mgmt-apimanagement-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Apimanagement Py",
- "description": "Manage Azure API Management services, APIs, products, and policies.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-applicationinsights-dotnet",
- "path": "skills/azure-mgmt-applicationinsights-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Applicationinsights Dotnet",
- "description": "Azure Resource Manager SDK for managing Application Insights resources for application performance monitoring.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "path": "skills/azure-mgmt-arizeaiobservabilityeval-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Arizeaiobservabilityeval Dotnet",
- "description": ".NET SDK for managing Arize AI Observability and Evaluation resources on Azure.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-dotnet",
- "path": "skills/azure-mgmt-botservice-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Botservice Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Bot Service resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-botservice-py",
- "path": "skills/azure-mgmt-botservice-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Botservice Py",
- "description": "Manage Azure Bot Service resources including bots, channels, and connections.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-dotnet",
- "path": "skills/azure-mgmt-fabric-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Fabric Dotnet",
- "description": "Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-fabric-py",
- "path": "skills/azure-mgmt-fabric-py",
- "category": "uncategorized",
- "name": "Azure Mgmt Fabric Py",
- "description": "Manage Microsoft Fabric capacities and resources programmatically.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-mgmt-weightsandbiases-dotnet",
- "path": "skills/azure-mgmt-weightsandbiases-dotnet",
- "category": "uncategorized",
- "name": "Azure Mgmt Weightsandbiases Dotnet",
- "description": "Azure Resource Manager SDK for deploying and managing Weights & Biases ML experiment tracking instances via Azure Marketplace.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-java",
- "path": "skills/azure-monitor-ingestion-java",
- "category": "uncategorized",
- "name": "Azure Monitor Ingestion Java",
- "description": "Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-ingestion-py",
- "path": "skills/azure-monitor-ingestion-py",
- "category": "uncategorized",
- "name": "Azure Monitor Ingestion Py",
- "description": "Send custom logs to Azure Monitor Log Analytics workspace using the Logs Ingestion API.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-java",
- "path": "skills/azure-monitor-opentelemetry-exporter-java",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Exporter Java",
- "description": "> **\u26a0\ufe0f DEPRECATION NOTICE**: This package is deprecated. Migrate to `azure-monitor-opentelemetry-autoconfigure`. > > See [Migration Guide](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/MIGRATIO",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-exporter-py",
- "path": "skills/azure-monitor-opentelemetry-exporter-py",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Exporter Py",
- "description": "Low-level exporter for sending OpenTelemetry traces, metrics, and logs to Application Insights.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-opentelemetry-py",
- "path": "skills/azure-monitor-opentelemetry-py",
- "category": "uncategorized",
- "name": "Azure Monitor Opentelemetry Py",
- "description": "One-line setup for Application Insights with OpenTelemetry auto-instrumentation.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-java",
- "path": "skills/azure-monitor-query-java",
- "category": "uncategorized",
- "name": "Azure Monitor Query Java",
- "description": "> **DEPRECATION NOTICE**: This package is deprecated in favor of: > - `azure-monitor-query-logs` \u2014 For Log Analytics queries > - `azure-monitor-query-metrics` \u2014 For metrics queries > > See migration guides: [Logs Migration](https://github.com/Azure/a",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-monitor-query-py",
- "path": "skills/azure-monitor-query-py",
- "category": "uncategorized",
- "name": "Azure Monitor Query Py",
- "description": "Query logs and metrics from Azure Monitor and Log Analytics workspaces.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-postgres-ts",
- "path": "skills/azure-postgres-ts",
- "category": "uncategorized",
- "name": "Azure Postgres Ts",
- "description": "Connect to Azure Database for PostgreSQL Flexible Server using the `pg` (node-postgres) package with support for password and Microsoft Entra ID (passwordless) authentication.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-cosmosdb-dotnet",
- "path": "skills/azure-resource-manager-cosmosdb-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Cosmosdb Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Cosmos DB resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-durabletask-dotnet",
- "path": "skills/azure-resource-manager-durabletask-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Durabletask Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-mysql-dotnet",
- "path": "skills/azure-resource-manager-mysql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Mysql Dotnet",
- "description": "Azure Resource Manager SDK for managing MySQL Flexible Server deployments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-playwright-dotnet",
- "path": "skills/azure-resource-manager-playwright-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Playwright Dotnet",
- "description": "Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-postgresql-dotnet",
- "path": "skills/azure-resource-manager-postgresql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Postgresql Dotnet",
- "description": "Azure Resource Manager SDK for managing PostgreSQL Flexible Server deployments.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-redis-dotnet",
- "path": "skills/azure-resource-manager-redis-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Redis Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure Cache for Redis resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-resource-manager-sql-dotnet",
- "path": "skills/azure-resource-manager-sql-dotnet",
- "category": "uncategorized",
- "name": "Azure Resource Manager Sql Dotnet",
- "description": "Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-dotnet",
- "path": "skills/azure-search-documents-dotnet",
- "category": "uncategorized",
- "name": "Azure Search Documents Dotnet",
- "description": "Build search applications with full-text, vector, semantic, and hybrid search capabilities.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-search-documents-py",
- "path": "skills/azure-search-documents-py",
- "category": "uncategorized",
- "name": "Azure Search Documents Py",
- "description": "Full-text, vector, and hybrid search with AI enrichment capabilities.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-security-keyvault-keys-dotnet",
- "path": "skills/azure-security-keyvault-keys-dotnet",
- "category": "uncategorized",
- "name": "Azure Security Keyvault Keys Dotnet",
- "description": "Client library for managing cryptographic keys in Azure Key Vault and Managed HSM.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-dotnet",
- "path": "skills/azure-servicebus-dotnet",
- "category": "uncategorized",
- "name": "Azure Servicebus Dotnet",
- "description": "Enterprise messaging SDK for reliable message delivery with queues, topics, subscriptions, and sessions.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-servicebus-py",
- "path": "skills/azure-servicebus-py",
- "category": "uncategorized",
- "name": "Azure Servicebus Py",
- "description": "Enterprise messaging for reliable cloud communication with queues and pub/sub topics.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-speech-to-text-rest-py",
- "path": "skills/azure-speech-to-text-rest-py",
- "category": "uncategorized",
- "name": "Azure Speech To Text Rest Py",
- "description": "Simple REST API for speech-to-text transcription of short audio files (up to 60 seconds). No SDK required - just HTTP requests.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-py",
- "path": "skills/azure-storage-blob-py",
- "category": "uncategorized",
- "name": "Azure Storage Blob Py",
- "description": "Client library for Azure Blob Storage \u2014 object storage for unstructured data.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-rust",
- "path": "skills/azure-storage-blob-rust",
- "category": "uncategorized",
- "name": "Azure Storage Blob Rust",
- "description": "Client library for Azure Blob Storage \u2014 Microsoft's object storage solution for the cloud.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-blob-ts",
- "path": "skills/azure-storage-blob-ts",
- "category": "uncategorized",
- "name": "Azure Storage Blob Ts",
- "description": "SDK for Azure Blob Storage operations \u2014 upload, download, list, and manage blobs and containers.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-datalake-py",
- "path": "skills/azure-storage-file-datalake-py",
- "category": "uncategorized",
- "name": "Azure Storage File Datalake Py",
- "description": "Hierarchical file system for big data analytics workloads.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-py",
- "path": "skills/azure-storage-file-share-py",
- "category": "uncategorized",
- "name": "Azure Storage File Share Py",
- "description": "Manage SMB file shares for cloud-native and lift-and-shift scenarios.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-file-share-ts",
- "path": "skills/azure-storage-file-share-ts",
- "category": "uncategorized",
- "name": "Azure Storage File Share Ts",
- "description": "SDK for Azure File Share operations \u2014 SMB file shares, directories, and file operations.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-py",
- "path": "skills/azure-storage-queue-py",
- "category": "uncategorized",
- "name": "Azure Storage Queue Py",
- "description": "Simple, cost-effective message queuing for asynchronous communication.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "azure-storage-queue-ts",
- "path": "skills/azure-storage-queue-ts",
- "category": "uncategorized",
- "name": "Azure Storage Queue Ts",
- "description": "SDK for Azure Queue Storage operations \u2014 send, receive, peek, and manage messages in queues.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "azure-ai-anomalydetector-java",
- "path": "skills/azure-ai-anomalydetector-java",
+ "path": "skills\\azure-ai-anomalydetector-java",
"category": "uncategorized",
"name": "azure-ai-anomalydetector-java",
"description": "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.",
@@ -1405,25 +739,52 @@
},
{
"id": "azure-ai-contentsafety-java",
- "path": "skills/azure-ai-contentsafety-java",
+ "path": "skills\\azure-ai-contentsafety-java",
"category": "uncategorized",
"name": "azure-ai-contentsafety-java",
"description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-contentsafety-py",
+ "path": "skills\\azure-ai-contentsafety-py",
+ "category": "uncategorized",
+ "name": "azure-ai-contentsafety-py",
+ "description": "Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.\nTriggers: \"azure-ai-contentsafety\", \"ContentSafetyClient\", \"content moderation\", \"harmful content\", \"text analysis\", \"image analysis\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-contentsafety-ts",
- "path": "skills/azure-ai-contentsafety-ts",
+ "path": "skills\\azure-ai-contentsafety-ts",
"category": "uncategorized",
"name": "azure-ai-contentsafety-ts",
"description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-contentunderstanding-py",
+ "path": "skills\\azure-ai-contentunderstanding-py",
+ "category": "uncategorized",
+ "name": "azure-ai-contentunderstanding-py",
+ "description": "Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.\nTriggers: \"azure-ai-contentunderstanding\", \"ContentUnderstandingClient\", \"multimodal analysis\", \"document extraction\", \"video analysis\", \"audio transcription\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-document-intelligence-dotnet",
+ "path": "skills\\azure-ai-document-intelligence-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-document-intelligence-dotnet",
+ "description": "Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: \"Document Intelligence\", \"DocumentIntelligenceClient\", \"form recognizer\", \"invoice extraction\", \"receipt OCR\", \"document analysis .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-document-intelligence-ts",
- "path": "skills/azure-ai-document-intelligence-ts",
+ "path": "skills\\azure-ai-document-intelligence-ts",
"category": "uncategorized",
"name": "azure-ai-document-intelligence-ts",
"description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...",
@@ -1432,16 +793,52 @@
},
{
"id": "azure-ai-formrecognizer-java",
- "path": "skills/azure-ai-formrecognizer-java",
+ "path": "skills\\azure-ai-formrecognizer-java",
"category": "uncategorized",
"name": "azure-ai-formrecognizer-java",
"description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-ml-py",
+ "path": "skills\\azure-ai-ml-py",
+ "category": "uncategorized",
+ "name": "azure-ai-ml-py",
+ "description": "Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.\nTriggers: \"azure-ai-ml\", \"MLClient\", \"workspace\", \"model registry\", \"training jobs\", \"datasets\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-openai-dotnet",
+ "path": "skills\\azure-ai-openai-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-openai-dotnet",
+ "description": "Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: \"Azure OpenAI\", \"AzureOpenAIClient\", \"ChatClient\", \"chat completions .NET\", \"GPT-4\", \"embeddings\", \"DALL-E\", \"Whisper\", \"OpenAI .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-projects-dotnet",
+ "path": "skills\\azure-ai-projects-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-projects-dotnet",
+ "description": "Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: \"AI Projects\", \"AIProjectClient\", \"Foundry project\", \"versioned agents\", \"evaluations\", \"datasets\", \"connections\", \"deployments .NET\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-projects-java",
+ "path": "skills\\azure-ai-projects-java",
+ "category": "uncategorized",
+ "name": "azure-ai-projects-java",
+ "description": "Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.\nTriggers: \"AIProjectClient java\", \"azure ai projects java\", \"Foundry project java\", \"ConnectionsClient\", \"DatasetsClient\", \"IndexesClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-projects-py",
- "path": "skills/azure-ai-projects-py",
+ "path": "skills\\azure-ai-projects-py",
"category": "uncategorized",
"name": "azure-ai-projects-py",
"description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua...",
@@ -1450,16 +847,52 @@
},
{
"id": "azure-ai-projects-ts",
- "path": "skills/azure-ai-projects-ts",
+ "path": "skills\\azure-ai-projects-ts",
"category": "uncategorized",
"name": "azure-ai-projects-ts",
"description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-textanalytics-py",
+ "path": "skills\\azure-ai-textanalytics-py",
+ "category": "uncategorized",
+ "name": "azure-ai-textanalytics-py",
+ "description": "Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.\nTriggers: \"text analytics\", \"sentiment analysis\", \"entity recognition\", \"key phrase\", \"PII detection\", \"TextAnalyticsClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-transcription-py",
+ "path": "skills\\azure-ai-transcription-py",
+ "category": "uncategorized",
+ "name": "azure-ai-transcription-py",
+ "description": "Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.\nTriggers: \"transcription\", \"speech to text\", \"Azure AI Transcription\", \"TranscriptionClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-translation-document-py",
+ "path": "skills\\azure-ai-translation-document-py",
+ "category": "uncategorized",
+ "name": "azure-ai-translation-document-py",
+ "description": "Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.\nTriggers: \"document translation\", \"batch translation\", \"translate documents\", \"DocumentTranslationClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-translation-text-py",
+ "path": "skills\\azure-ai-translation-text-py",
+ "category": "uncategorized",
+ "name": "azure-ai-translation-text-py",
+ "description": "Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.\nTriggers: \"text translation\", \"translator\", \"translate text\", \"transliterate\", \"TextTranslationClient\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-translation-ts",
- "path": "skills/azure-ai-translation-ts",
+ "path": "skills\\azure-ai-translation-ts",
"category": "uncategorized",
"name": "azure-ai-translation-ts",
"description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...",
@@ -1468,25 +901,79 @@
},
{
"id": "azure-ai-vision-imageanalysis-java",
- "path": "skills/azure-ai-vision-imageanalysis-java",
+ "path": "skills\\azure-ai-vision-imageanalysis-java",
"category": "uncategorized",
"name": "azure-ai-vision-imageanalysis-java",
"description": "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-vision-imageanalysis-py",
+ "path": "skills\\azure-ai-vision-imageanalysis-py",
+ "category": "uncategorized",
+ "name": "azure-ai-vision-imageanalysis-py",
+ "description": "Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.\nTriggers: \"image analysis\", \"computer vision\", \"OCR\", \"object detection\", \"ImageAnalysisClient\", \"image caption\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-voicelive-dotnet",
+ "path": "skills\\azure-ai-voicelive-dotnet",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-dotnet",
+ "description": "Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant .NET\", \"bidirectional audio\", \"speech-to-speech\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-ai-voicelive-java",
+ "path": "skills\\azure-ai-voicelive-java",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-java",
+ "description": "Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.\nTriggers: \"VoiceLiveClient java\", \"voice assistant java\", \"real-time voice java\", \"audio streaming java\", \"voice activity detection java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-ai-voicelive-py",
- "path": "skills/azure-ai-voicelive-py",
+ "path": "skills\\azure-ai-voicelive-py",
"category": "uncategorized",
"name": "azure-ai-voicelive-py",
"description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-ai-voicelive-ts",
+ "path": "skills\\azure-ai-voicelive-ts",
+ "category": "uncategorized",
+ "name": "azure-ai-voicelive-ts",
+ "description": "Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant TypeScript\", \"bidirectional audio\", \"speech-to-speech JavaScript\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-appconfiguration-java",
+ "path": "skills\\azure-appconfiguration-java",
+ "category": "uncategorized",
+ "name": "azure-appconfiguration-java",
+ "description": "Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.\nTriggers: \"ConfigurationClient java\", \"app configuration java\", \"feature flag java\", \"configuration setting java\", \"azure config java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-appconfiguration-py",
+ "path": "skills\\azure-appconfiguration-py",
+ "category": "uncategorized",
+ "name": "azure-appconfiguration-py",
+ "description": "Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.\nTriggers: \"azure-appconfiguration\", \"AzureAppConfigurationClient\", \"feature flags\", \"configuration\", \"key-value settings\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-appconfiguration-ts",
- "path": "skills/azure-appconfiguration-ts",
+ "path": "skills\\azure-appconfiguration-ts",
"category": "uncategorized",
"name": "azure-appconfiguration-ts",
"description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...",
@@ -1495,7 +982,7 @@
},
{
"id": "azure-communication-callautomation-java",
- "path": "skills/azure-communication-callautomation-java",
+ "path": "skills\\azure-communication-callautomation-java",
"category": "uncategorized",
"name": "azure-communication-callautomation-java",
"description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...",
@@ -1504,7 +991,7 @@
},
{
"id": "azure-communication-callingserver-java",
- "path": "skills/azure-communication-callingserver-java",
+ "path": "skills\\azure-communication-callingserver-java",
"category": "uncategorized",
"name": "azure-communication-callingserver-java",
"description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...",
@@ -1513,7 +1000,7 @@
},
{
"id": "azure-communication-chat-java",
- "path": "skills/azure-communication-chat-java",
+ "path": "skills\\azure-communication-chat-java",
"category": "uncategorized",
"name": "azure-communication-chat-java",
"description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...",
@@ -1522,7 +1009,7 @@
},
{
"id": "azure-communication-common-java",
- "path": "skills/azure-communication-common-java",
+ "path": "skills\\azure-communication-common-java",
"category": "uncategorized",
"name": "azure-communication-common-java",
"description": "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.",
@@ -1531,52 +1018,160 @@
},
{
"id": "azure-communication-sms-java",
- "path": "skills/azure-communication-sms-java",
+ "path": "skills\\azure-communication-sms-java",
"category": "uncategorized",
"name": "azure-communication-sms-java",
"description": "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-compute-batch-java",
+ "path": "skills\\azure-compute-batch-java",
+ "category": "uncategorized",
+ "name": "azure-compute-batch-java",
+ "description": "Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.\nTriggers: \"BatchClient java\", \"azure batch java\", \"batch pool java\", \"batch job java\", \"HPC java\", \"parallel computing java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-containerregistry-py",
+ "path": "skills\\azure-containerregistry-py",
+ "category": "uncategorized",
+ "name": "azure-containerregistry-py",
+ "description": "Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.\nTriggers: \"azure-containerregistry\", \"ContainerRegistryClient\", \"container images\", \"docker registry\", \"ACR\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-cosmos-db-py",
- "path": "skills/azure-cosmos-db-py",
+ "path": "skills\\azure-cosmos-db-py",
"category": "uncategorized",
"name": "azure-cosmos-db-py",
"description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-cosmos-java",
+ "path": "skills\\azure-cosmos-java",
+ "category": "uncategorized",
+ "name": "azure-cosmos-java",
+ "description": "Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.\nTriggers: \"CosmosClient java\", \"CosmosAsyncClient\", \"cosmos database java\", \"cosmosdb java\", \"document database java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-py",
+ "path": "skills\\azure-cosmos-py",
+ "category": "uncategorized",
+ "name": "azure-cosmos-py",
+ "description": "Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db\", \"CosmosClient\", \"container\", \"document\", \"NoSQL\", \"partition key\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-rust",
+ "path": "skills\\azure-cosmos-rust",
+ "category": "uncategorized",
+ "name": "azure-cosmos-rust",
+ "description": "Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db rust\", \"CosmosClient rust\", \"container\", \"document rust\", \"NoSQL rust\", \"partition key\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-cosmos-ts",
+ "path": "skills\\azure-cosmos-ts",
+ "category": "uncategorized",
+ "name": "azure-cosmos-ts",
+ "description": "Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: \"Cosmos DB\", \"@azure/cosmos\", \"CosmosClient\", \"document CRUD\", \"NoSQL queries\", \"bulk operations\", \"partition key\", \"container.items\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-data-tables-java",
- "path": "skills/azure-data-tables-java",
+ "path": "skills\\azure-data-tables-java",
"category": "uncategorized",
"name": "azure-data-tables-java",
"description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-data-tables-py",
+ "path": "skills\\azure-data-tables-py",
+ "category": "uncategorized",
+ "name": "azure-data-tables-py",
+ "description": "Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.\nTriggers: \"table storage\", \"TableServiceClient\", \"TableClient\", \"entities\", \"PartitionKey\", \"RowKey\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventgrid-dotnet",
+ "path": "skills\\azure-eventgrid-dotnet",
+ "category": "uncategorized",
+ "name": "azure-eventgrid-dotnet",
+ "description": "Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: \"Event Grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events .NET\", \"event-driven\", \"pub/sub\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventgrid-java",
- "path": "skills/azure-eventgrid-java",
+ "path": "skills\\azure-eventgrid-java",
"category": "uncategorized",
"name": "azure-eventgrid-java",
"description": "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-eventgrid-py",
+ "path": "skills\\azure-eventgrid-py",
+ "category": "uncategorized",
+ "name": "azure-eventgrid-py",
+ "description": "Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.\nTriggers: \"event grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventhub-dotnet",
+ "path": "skills\\azure-eventhub-dotnet",
+ "category": "uncategorized",
+ "name": "azure-eventhub-dotnet",
+ "description": "Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: \"Event Hubs\", \"event streaming\", \"EventHubProducerClient\", \"EventProcessorClient\", \"send events\", \"receive events\", \"checkpointing\", \"partition\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventhub-java",
- "path": "skills/azure-eventhub-java",
+ "path": "skills\\azure-eventhub-java",
"category": "uncategorized",
"name": "azure-eventhub-java",
"description": "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-eventhub-py",
+ "path": "skills\\azure-eventhub-py",
+ "category": "uncategorized",
+ "name": "azure-eventhub-py",
+ "description": "Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.\nTriggers: \"event hubs\", \"EventHubProducerClient\", \"EventHubConsumerClient\", \"streaming\", \"partitions\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-eventhub-rust",
+ "path": "skills\\azure-eventhub-rust",
+ "category": "uncategorized",
+ "name": "azure-eventhub-rust",
+ "description": "Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.\nTriggers: \"event hubs rust\", \"ProducerClient rust\", \"ConsumerClient rust\", \"send event rust\", \"streaming rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-eventhub-ts",
- "path": "skills/azure-eventhub-ts",
+ "path": "skills\\azure-eventhub-ts",
"category": "uncategorized",
"name": "azure-eventhub-ts",
"description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event...",
@@ -1585,97 +1180,439 @@
},
{
"id": "azure-functions",
- "path": "skills/azure-functions",
+ "path": "skills\\azure-functions",
"category": "uncategorized",
"name": "azure-functions",
"description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ...",
"risk": "unknown",
"source": "vibeship-spawner-skills (Apache 2.0)"
},
+ {
+ "id": "azure-identity-dotnet",
+ "path": "skills\\azure-identity-dotnet",
+ "category": "uncategorized",
+ "name": "azure-identity-dotnet",
+ "description": "Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: \"Azure Identity\", \"DefaultAzureCredential\", \"ManagedIdentityCredential\", \"ClientSecretCredential\", \"authentication .NET\", \"Azure auth\", \"credential chain\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-identity-java",
- "path": "skills/azure-identity-java",
+ "path": "skills\\azure-identity-java",
"category": "uncategorized",
"name": "azure-identity-java",
"description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-identity-py",
+ "path": "skills\\azure-identity-py",
+ "category": "uncategorized",
+ "name": "azure-identity-py",
+ "description": "Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.\nTriggers: \"azure-identity\", \"DefaultAzureCredential\", \"authentication\", \"managed identity\", \"service principal\", \"credential\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-identity-rust",
+ "path": "skills\\azure-identity-rust",
+ "category": "uncategorized",
+ "name": "azure-identity-rust",
+ "description": "Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.\nTriggers: \"azure-identity\", \"DeveloperToolsCredential\", \"authentication rust\", \"managed identity rust\", \"credential rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-identity-ts",
- "path": "skills/azure-identity-ts",
+ "path": "skills\\azure-identity-ts",
"category": "uncategorized",
"name": "azure-identity-ts",
"description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-keyvault-certificates-rust",
+ "path": "skills\\azure-keyvault-certificates-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-certificates-rust",
+ "description": "Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.\nTriggers: \"keyvault certificates rust\", \"CertificateClient rust\", \"create certificate rust\", \"import certificate rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-keyvault-keys-rust",
+ "path": "skills\\azure-keyvault-keys-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-keys-rust",
+ "description": "Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.\nTriggers: \"keyvault keys rust\", \"KeyClient rust\", \"create key rust\", \"encrypt rust\", \"sign rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-keyvault-keys-ts",
- "path": "skills/azure-keyvault-keys-ts",
+ "path": "skills\\azure-keyvault-keys-ts",
"category": "uncategorized",
"name": "azure-keyvault-keys-ts",
"description": "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-keyvault-py",
+ "path": "skills\\azure-keyvault-py",
+ "category": "uncategorized",
+ "name": "azure-keyvault-py",
+ "description": "Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.\nTriggers: \"key vault\", \"SecretClient\", \"KeyClient\", \"CertificateClient\", \"secrets\", \"encryption keys\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-keyvault-secrets-rust",
+ "path": "skills\\azure-keyvault-secrets-rust",
+ "category": "uncategorized",
+ "name": "azure-keyvault-secrets-rust",
+ "description": "Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.\nTriggers: \"keyvault secrets rust\", \"SecretClient rust\", \"get secret rust\", \"set secret rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-keyvault-secrets-ts",
- "path": "skills/azure-keyvault-secrets-ts",
+ "path": "skills\\azure-keyvault-secrets-ts",
"category": "uncategorized",
"name": "azure-keyvault-secrets-ts",
"description": "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-maps-search-dotnet",
+ "path": "skills\\azure-maps-search-dotnet",
+ "category": "uncategorized",
+ "name": "azure-maps-search-dotnet",
+ "description": "Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: \"Azure Maps\", \"MapsSearchClient\", \"MapsRoutingClient\", \"MapsRenderingClient\", \"geocoding .NET\", \"route directions\", \"map tiles\", \"geolocation\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-messaging-webpubsub-java",
- "path": "skills/azure-messaging-webpubsub-java",
+ "path": "skills\\azure-messaging-webpubsub-java",
"category": "uncategorized",
"name": "azure-messaging-webpubsub-java",
"description": "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-messaging-webpubsubservice-py",
+ "path": "skills\\azure-messaging-webpubsubservice-py",
+ "category": "uncategorized",
+ "name": "azure-messaging-webpubsubservice-py",
+ "description": "Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.\nTriggers: \"azure-messaging-webpubsubservice\", \"WebPubSubServiceClient\", \"real-time\", \"WebSocket\", \"pub/sub\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apicenter-dotnet",
+ "path": "skills\\azure-mgmt-apicenter-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apicenter-dotnet",
+ "description": "Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: \"API Center\", \"ApiCenterService\", \"ApiCenterWorkspace\", \"ApiCenterApi\", \"API inventory\", \"API governance\", \"API versioning\", \"API catalog\", \"API discovery\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apicenter-py",
+ "path": "skills\\azure-mgmt-apicenter-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apicenter-py",
+ "description": "Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.\nTriggers: \"azure-mgmt-apicenter\", \"ApiCenterMgmtClient\", \"API Center\", \"API inventory\", \"API governance\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-dotnet",
+ "path": "skills\\azure-mgmt-apimanagement-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apimanagement-dotnet",
+ "description": "Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: \"API Management\", \"APIM service\", \"create APIM\", \"manage APIs\", \"ApiManagementServiceResource\", \"API policies\", \"APIM products\", \"APIM subscriptions\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-apimanagement-py",
+ "path": "skills\\azure-mgmt-apimanagement-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-apimanagement-py",
+ "description": "Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.\nTriggers: \"azure-mgmt-apimanagement\", \"ApiManagementClient\", \"APIM\", \"API gateway\", \"API Management\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-applicationinsights-dotnet",
+ "path": "skills\\azure-mgmt-applicationinsights-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-applicationinsights-dotnet",
+ "description": "Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: \"Application Insights\", \"ApplicationInsights\", \"App Insights\", \"APM\", \"application monitoring\", \"web tests\", \"availability tests\", \"workbooks\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "path": "skills\\azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-arizeaiobservabilityeval-dotnet",
+ "description": "Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations \non Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability \ninto .NET applications. Triggers: \"Arize AI\", \"ML observability\", \"ArizeAIObservabilityEval\", \"Arize organization\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-botservice-dotnet",
+ "path": "skills\\azure-mgmt-botservice-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-botservice-dotnet",
+ "description": "Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: \"Bot Service\", \"BotResource\", \"Azure Bot\", \"DirectLine channel\", \"Teams channel\", \"bot management .NET\", \"create bot\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-botservice-py",
+ "path": "skills\\azure-mgmt-botservice-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-botservice-py",
+ "description": "Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.\nTriggers: \"azure-mgmt-botservice\", \"AzureBotService\", \"bot management\", \"conversational AI\", \"bot channels\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-fabric-dotnet",
+ "path": "skills\\azure-mgmt-fabric-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-fabric-dotnet",
+ "description": "Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: \"Fabric capacity\", \"create capacity\", \"suspend capacity\", \"resume capacity\", \"Fabric SKU\", \"provision Fabric\", \"ARM Fabric\", \"FabricCapacityResource\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-mgmt-fabric-py",
+ "path": "skills\\azure-mgmt-fabric-py",
+ "category": "uncategorized",
+ "name": "azure-mgmt-fabric-py",
+ "description": "Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.\nTriggers: \"azure-mgmt-fabric\", \"FabricMgmtClient\", \"Fabric capacity\", \"Microsoft Fabric\", \"Power BI capacity\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-mgmt-mongodbatlas-dotnet",
- "path": "skills/azure-mgmt-mongodbatlas-dotnet",
+ "path": "skills\\azure-mgmt-mongodbatlas-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-mongodbatlas-dotnet",
"description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-mgmt-weightsandbiases-dotnet",
+ "path": "skills\\azure-mgmt-weightsandbiases-dotnet",
+ "category": "uncategorized",
+ "name": "azure-mgmt-weightsandbiases-dotnet",
+ "description": "Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: \"Weights and Biases\", \"W&B\", \"WeightsAndBiases\", \"ML experiment tracking\", \"model registry\", \"experiment management\", \"wandb\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-microsoft-playwright-testing-ts",
- "path": "skills/azure-microsoft-playwright-testing-ts",
+ "path": "skills\\azure-microsoft-playwright-testing-ts",
"category": "uncategorized",
"name": "azure-microsoft-playwright-testing-ts",
"description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-monitor-ingestion-java",
+ "path": "skills\\azure-monitor-ingestion-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-ingestion-java",
+ "description": "Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).\nTriggers: \"LogsIngestionClient java\", \"azure monitor ingestion java\", \"custom logs java\", \"DCR java\", \"data collection rule java\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-ingestion-py",
+ "path": "skills\\azure-monitor-ingestion-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-ingestion-py",
+ "description": "Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.\nTriggers: \"azure-monitor-ingestion\", \"LogsIngestionClient\", \"custom logs\", \"DCR\", \"data collection rule\", \"Log Analytics\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-java",
+ "path": "skills\\azure-monitor-opentelemetry-exporter-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-exporter-java",
+ "description": "Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.\nTriggers: \"AzureMonitorExporter java\", \"opentelemetry azure java\", \"application insights java otel\", \"azure monitor tracing java\".\nNote: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-exporter-py",
+ "path": "skills\\azure-monitor-opentelemetry-exporter-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-exporter-py",
+ "description": "Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.\nTriggers: \"azure-monitor-opentelemetry-exporter\", \"AzureMonitorTraceExporter\", \"AzureMonitorMetricExporter\", \"AzureMonitorLogExporter\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-opentelemetry-py",
+ "path": "skills\\azure-monitor-opentelemetry-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-opentelemetry-py",
+ "description": "Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.\nTriggers: \"azure-monitor-opentelemetry\", \"configure_azure_monitor\", \"Application Insights\", \"OpenTelemetry distro\", \"auto-instrumentation\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-monitor-opentelemetry-ts",
- "path": "skills/azure-monitor-opentelemetry-ts",
+ "path": "skills\\azure-monitor-opentelemetry-ts",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-ts",
"description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-monitor-query-java",
+ "path": "skills\\azure-monitor-query-java",
+ "category": "uncategorized",
+ "name": "azure-monitor-query-java",
+ "description": "Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.\nTriggers: \"LogsQueryClient java\", \"MetricsQueryClient java\", \"kusto query java\", \"log analytics java\", \"azure monitor query java\".\nNote: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-monitor-query-py",
+ "path": "skills\\azure-monitor-query-py",
+ "category": "uncategorized",
+ "name": "azure-monitor-query-py",
+ "description": "Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.\nTriggers: \"azure-monitor-query\", \"LogsQueryClient\", \"MetricsQueryClient\", \"Log Analytics\", \"Kusto queries\", \"Azure metrics\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-postgres-ts",
+ "path": "skills\\azure-postgres-ts",
+ "category": "uncategorized",
+ "name": "azure-postgres-ts",
+ "description": "Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: \"PostgreSQL\", \"postgres\", \"pg client\", \"node-postgres\", \"Azure PostgreSQL connection\", \"PostgreSQL TypeScript\", \"pg Pool\", \"passwordless postgres\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-cosmosdb-dotnet",
+ "path": "skills\\azure-resource-manager-cosmosdb-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-cosmosdb-dotnet",
+ "description": "Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: \"Cosmos DB account\", \"create Cosmos account\", \"manage Cosmos resources\", \"ARM Cosmos\", \"CosmosDBAccountResource\", \"provision Cosmos DB\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-durabletask-dotnet",
+ "path": "skills\\azure-resource-manager-durabletask-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-durabletask-dotnet",
+ "description": "Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: \"Durable Task Scheduler\", \"create scheduler\", \"task hub\", \"DurableTaskSchedulerResource\", \"provision Durable Task\", \"orchestration scheduler\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-mysql-dotnet",
+ "path": "skills\\azure-resource-manager-mysql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-mysql-dotnet",
+ "description": "Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"MySQL\", \"MySqlFlexibleServer\", \"MySQL Flexible Server\", \"Azure Database for MySQL\", \"MySQL database management\", \"MySQL firewall\", \"MySQL backup\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-playwright-dotnet",
+ "path": "skills\\azure-resource-manager-playwright-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-playwright-dotnet",
+ "description": "Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: \"Playwright workspace\", \"create Playwright Testing workspace\", \"manage Playwright resources\", \"ARM Playwright\", \"PlaywrightWorkspaceResource\", \"provision Playwright Testing\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-postgresql-dotnet",
+ "path": "skills\\azure-resource-manager-postgresql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-postgresql-dotnet",
+ "description": "Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"PostgreSQL\", \"PostgreSqlFlexibleServer\", \"PostgreSQL Flexible Server\", \"Azure Database for PostgreSQL\", \"PostgreSQL database management\", \"PostgreSQL firewall\", \"PostgreSQL backup\", \"Postgres\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-redis-dotnet",
+ "path": "skills\\azure-resource-manager-redis-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-redis-dotnet",
+ "description": "Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: \"Redis cache\", \"create Redis\", \"manage Redis\", \"ARM Redis\", \"RedisResource\", \"provision Redis\", \"Azure Cache for Redis\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-resource-manager-sql-dotnet",
+ "path": "skills\\azure-resource-manager-sql-dotnet",
+ "category": "uncategorized",
+ "name": "azure-resource-manager-sql-dotnet",
+ "description": "Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: \"SQL server\", \"create SQL database\", \"manage SQL resources\", \"ARM SQL\", \"SqlServerResource\", \"provision Azure SQL\", \"elastic pool\", \"firewall rule\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-search-documents-dotnet",
+ "path": "skills\\azure-search-documents-dotnet",
+ "category": "uncategorized",
+ "name": "azure-search-documents-dotnet",
+ "description": "Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: \"Azure Search .NET\", \"SearchClient\", \"SearchIndexClient\", \"vector search C#\", \"semantic search .NET\", \"hybrid search\", \"Azure.Search.Documents\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-search-documents-py",
+ "path": "skills\\azure-search-documents-py",
+ "category": "uncategorized",
+ "name": "azure-search-documents-py",
+ "description": "Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.\nTriggers: \"azure-search-documents\", \"SearchClient\", \"SearchIndexClient\", \"vector search\", \"hybrid search\", \"semantic search\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-search-documents-ts",
- "path": "skills/azure-search-documents-ts",
+ "path": "skills\\azure-search-documents-ts",
"category": "uncategorized",
"name": "azure-search-documents-ts",
"description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-security-keyvault-keys-dotnet",
+ "path": "skills\\azure-security-keyvault-keys-dotnet",
+ "category": "uncategorized",
+ "name": "azure-security-keyvault-keys-dotnet",
+ "description": "Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: \"Key Vault keys\", \"KeyClient\", \"CryptographyClient\", \"RSA key\", \"EC key\", \"encrypt decrypt .NET\", \"key rotation\", \"HSM\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-security-keyvault-keys-java",
- "path": "skills/azure-security-keyvault-keys-java",
+ "path": "skills\\azure-security-keyvault-keys-java",
"category": "uncategorized",
"name": "azure-security-keyvault-keys-java",
"description": "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.",
@@ -1684,34 +1621,133 @@
},
{
"id": "azure-security-keyvault-secrets-java",
- "path": "skills/azure-security-keyvault-secrets-java",
+ "path": "skills\\azure-security-keyvault-secrets-java",
"category": "uncategorized",
"name": "azure-security-keyvault-secrets-java",
"description": "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-servicebus-dotnet",
+ "path": "skills\\azure-servicebus-dotnet",
+ "category": "uncategorized",
+ "name": "azure-servicebus-dotnet",
+ "description": "Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: \"Service Bus\", \"ServiceBusClient\", \"ServiceBusSender\", \"ServiceBusReceiver\", \"ServiceBusProcessor\", \"message queue\", \"pub/sub .NET\", \"dead letter queue\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-servicebus-py",
+ "path": "skills\\azure-servicebus-py",
+ "category": "uncategorized",
+ "name": "azure-servicebus-py",
+ "description": "Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.\nTriggers: \"service bus\", \"ServiceBusClient\", \"queue\", \"topic\", \"subscription\", \"message broker\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-servicebus-ts",
- "path": "skills/azure-servicebus-ts",
+ "path": "skills\\azure-servicebus-ts",
"category": "uncategorized",
"name": "azure-servicebus-ts",
"description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-speech-to-text-rest-py",
+ "path": "skills\\azure-speech-to-text-rest-py",
+ "category": "uncategorized",
+ "name": "azure-speech-to-text-rest-py",
+ "description": "Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.\nTriggers: \"speech to text REST\", \"short audio transcription\", \"speech recognition REST API\", \"STT REST\", \"recognize speech REST\".\nDO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-storage-blob-java",
- "path": "skills/azure-storage-blob-java",
+ "path": "skills\\azure-storage-blob-java",
"category": "uncategorized",
"name": "azure-storage-blob-java",
"description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "azure-storage-blob-py",
+ "path": "skills\\azure-storage-blob-py",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-py",
+ "description": "Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.\nTriggers: \"blob storage\", \"BlobServiceClient\", \"ContainerClient\", \"BlobClient\", \"upload blob\", \"download blob\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-blob-rust",
+ "path": "skills\\azure-storage-blob-rust",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-rust",
+ "description": "Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.\nTriggers: \"blob storage rust\", \"BlobClient rust\", \"upload blob rust\", \"download blob rust\", \"container rust\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-blob-ts",
+ "path": "skills\\azure-storage-blob-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-blob-ts",
+ "description": "Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: \"blob storage\", \"@azure/storage-blob\", \"BlobServiceClient\", \"ContainerClient\", \"upload blob\", \"download blob\", \"SAS token\", \"block blob\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-datalake-py",
+ "path": "skills\\azure-storage-file-datalake-py",
+ "category": "uncategorized",
+ "name": "azure-storage-file-datalake-py",
+ "description": "Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.\nTriggers: \"data lake\", \"DataLakeServiceClient\", \"FileSystemClient\", \"ADLS Gen2\", \"hierarchical namespace\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-share-py",
+ "path": "skills\\azure-storage-file-share-py",
+ "category": "uncategorized",
+ "name": "azure-storage-file-share-py",
+ "description": "Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.\nTriggers: \"azure-storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"file share\", \"SMB\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-file-share-ts",
+ "path": "skills\\azure-storage-file-share-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-file-share-ts",
+ "description": "Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: \"file share\", \"@azure/storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"SMB\", \"Azure Files\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-queue-py",
+ "path": "skills\\azure-storage-queue-py",
+ "category": "uncategorized",
+ "name": "azure-storage-queue-py",
+ "description": "Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.\nTriggers: \"queue storage\", \"QueueServiceClient\", \"QueueClient\", \"message queue\", \"dequeue\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "azure-storage-queue-ts",
+ "path": "skills\\azure-storage-queue-ts",
+ "category": "uncategorized",
+ "name": "azure-storage-queue-ts",
+ "description": "Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: \"queue storage\", \"@azure/storage-queue\", \"QueueServiceClient\", \"QueueClient\", \"send message\", \"receive message\", \"dequeue\", \"visibility timeout\".\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "azure-web-pubsub-ts",
- "path": "skills/azure-web-pubsub-ts",
+ "path": "skills\\azure-web-pubsub-ts",
"category": "uncategorized",
"name": "azure-web-pubsub-ts",
"description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...",
@@ -1720,25 +1756,16 @@
},
{
"id": "backend-architect",
- "path": "skills/backend-architect",
+ "path": "skills\\backend-architect",
"category": "uncategorized",
- "name": "Backend Architect",
- "description": "You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.",
+ "name": "backend-architect",
+ "description": "Expert backend architect specializing in scalable API design,\nmicroservices architecture, and distributed systems. Masters REST/GraphQL/gRPC\nAPIs, event-driven architectures, service mesh patterns, and modern backend\nframeworks. Handles service boundary definition, inter-service communication,\nresilience patterns, and observability. Use PROACTIVELY when creating new\nbackend services or APIs.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "backend-security-coder",
- "path": "skills/backend-security-coder",
- "category": "uncategorized",
- "name": "Backend Security Coder",
- "description": "- Working on backend security coder tasks or workflows - Needing guidance, best practices, or checklists for backend security coder",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "backend-dev-guidelines",
- "path": "skills/backend-dev-guidelines",
+ "path": "skills\\backend-dev-guidelines",
"category": "uncategorized",
"name": "backend-dev-guidelines",
"description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid...",
@@ -1747,16 +1774,25 @@
},
{
"id": "backend-development-feature-development",
- "path": "skills/backend-development-feature-development",
+ "path": "skills\\backend-development-feature-development",
"category": "uncategorized",
"name": "backend-development-feature-development",
"description": "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "backend-security-coder",
+ "path": "skills\\backend-security-coder",
+ "category": "uncategorized",
+ "name": "backend-security-coder",
+ "description": "Expert in secure backend coding practices specializing in input\nvalidation, authentication, and API security. Use PROACTIVELY for backend\nsecurity implementations or security code reviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "backtesting-frameworks",
- "path": "skills/backtesting-frameworks",
+ "path": "skills\\backtesting-frameworks",
"category": "uncategorized",
"name": "backtesting-frameworks",
"description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...",
@@ -1765,7 +1801,7 @@
},
{
"id": "bamboohr-automation",
- "path": "skills/bamboohr-automation",
+ "path": "skills\\bamboohr-automation",
"category": "uncategorized",
"name": "bamboohr-automation",
"description": "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.",
@@ -1774,7 +1810,7 @@
},
{
"id": "base",
- "path": "skills/libreoffice/base",
+ "path": "skills\\libreoffice\\base",
"category": "libreoffice",
"name": "base",
"description": "Database management, forms, reports, and data operations with LibreOffice Base.",
@@ -1783,25 +1819,16 @@
},
{
"id": "basecamp-automation",
- "path": "skills/basecamp-automation",
+ "path": "skills\\basecamp-automation",
"category": "uncategorized",
"name": "basecamp-automation",
"description": "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "bash-pro",
- "path": "skills/bash-pro",
- "category": "uncategorized",
- "name": "Bash Pro",
- "description": "- Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "bash-defensive-patterns",
- "path": "skills/bash-defensive-patterns",
+ "path": "skills\\bash-defensive-patterns",
"category": "uncategorized",
"name": "bash-defensive-patterns",
"description": "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.",
@@ -1810,16 +1837,25 @@
},
{
"id": "bash-linux",
- "path": "skills/bash-linux",
+ "path": "skills\\bash-linux",
"category": "uncategorized",
"name": "bash-linux",
"description": "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "bash-pro",
+ "path": "skills\\bash-pro",
+ "category": "uncategorized",
+ "name": "bash-pro",
+ "description": "Master of defensive Bash scripting for production automation, CI/CD\npipelines, and system utilities. Expert in safe, portable, and testable shell\nscripts.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "bash-scripting",
- "path": "skills/bash-scripting",
+ "path": "skills\\bash-scripting",
"category": "uncategorized",
"name": "bash-scripting",
"description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
@@ -1828,7 +1864,7 @@
},
{
"id": "bats-testing-patterns",
- "path": "skills/bats-testing-patterns",
+ "path": "skills\\bats-testing-patterns",
"category": "uncategorized",
"name": "bats-testing-patterns",
"description": "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.",
@@ -1837,7 +1873,7 @@
},
{
"id": "bazel-build-optimization",
- "path": "skills/bazel-build-optimization",
+ "path": "skills\\bazel-build-optimization",
"category": "uncategorized",
"name": "bazel-build-optimization",
"description": "Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.",
@@ -1846,7 +1882,7 @@
},
{
"id": "beautiful-prose",
- "path": "skills/beautiful-prose",
+ "path": "skills\\beautiful-prose",
"category": "uncategorized",
"name": "beautiful-prose",
"description": "Hard-edged writing style contract for timeless, forceful English prose without AI tics",
@@ -1855,7 +1891,7 @@
},
{
"id": "behavioral-modes",
- "path": "skills/behavioral-modes",
+ "path": "skills\\behavioral-modes",
"category": "uncategorized",
"name": "behavioral-modes",
"description": "AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.",
@@ -1864,7 +1900,7 @@
},
{
"id": "bevy-ecs-expert",
- "path": "skills/bevy-ecs-expert",
+ "path": "skills\\bevy-ecs-expert",
"category": "uncategorized",
"name": "bevy-ecs-expert",
"description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
@@ -1873,7 +1909,7 @@
},
{
"id": "billing-automation",
- "path": "skills/billing-automation",
+ "path": "skills\\billing-automation",
"category": "uncategorized",
"name": "billing-automation",
"description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...",
@@ -1882,7 +1918,7 @@
},
{
"id": "binary-analysis-patterns",
- "path": "skills/binary-analysis-patterns",
+ "path": "skills\\binary-analysis-patterns",
"category": "uncategorized",
"name": "binary-analysis-patterns",
"description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing...",
@@ -1891,7 +1927,7 @@
},
{
"id": "bitbucket-automation",
- "path": "skills/bitbucket-automation",
+ "path": "skills\\bitbucket-automation",
"category": "uncategorized",
"name": "bitbucket-automation",
"description": "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -1900,16 +1936,16 @@
},
{
"id": "blockchain-developer",
- "path": "skills/blockchain-developer",
+ "path": "skills\\blockchain-developer",
"category": "uncategorized",
- "name": "Blockchain Developer",
- "description": "- Working on blockchain developer tasks or workflows - Needing guidance, best practices, or checklists for blockchain developer",
+ "name": "blockchain-developer",
+ "description": "Build production-ready Web3 applications, smart contracts, and\ndecentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and\nenterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3\napps, DeFi protocols, or blockchain infrastructure.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "blockrun",
- "path": "skills/blockrun",
+ "path": "skills\\blockrun",
"category": "uncategorized",
"name": "blockrun",
"description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da...",
@@ -1918,7 +1954,7 @@
},
{
"id": "box-automation",
- "path": "skills/box-automation",
+ "path": "skills\\box-automation",
"category": "uncategorized",
"name": "box-automation",
"description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for...",
@@ -1927,7 +1963,7 @@
},
{
"id": "brainstorming",
- "path": "skills/brainstorming",
+ "path": "skills\\brainstorming",
"category": "uncategorized",
"name": "brainstorming",
"description": "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.",
@@ -1936,7 +1972,7 @@
},
{
"id": "brand-guidelines-anthropic",
- "path": "skills/brand-guidelines-anthropic",
+ "path": "skills\\brand-guidelines-anthropic",
"category": "uncategorized",
"name": "brand-guidelines-anthropic",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
@@ -1945,7 +1981,7 @@
},
{
"id": "brand-guidelines-community",
- "path": "skills/brand-guidelines-community",
+ "path": "skills\\brand-guidelines-community",
"category": "uncategorized",
"name": "brand-guidelines-community",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
@@ -1954,7 +1990,7 @@
},
{
"id": "brevo-automation",
- "path": "skills/brevo-automation",
+ "path": "skills\\brevo-automation",
"category": "uncategorized",
"name": "brevo-automation",
"description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche...",
@@ -1963,7 +1999,7 @@
},
{
"id": "broken-authentication",
- "path": "skills/broken-authentication",
+ "path": "skills\\broken-authentication",
"category": "uncategorized",
"name": "broken-authentication",
"description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ...",
@@ -1972,7 +2008,7 @@
},
{
"id": "browser-automation",
- "path": "skills/browser-automation",
+ "path": "skills\\browser-automation",
"category": "uncategorized",
"name": "browser-automation",
"description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...",
@@ -1981,7 +2017,7 @@
},
{
"id": "browser-extension-builder",
- "path": "skills/browser-extension-builder",
+ "path": "skills\\browser-extension-builder",
"category": "uncategorized",
"name": "browser-extension-builder",
"description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ...",
@@ -1990,7 +2026,7 @@
},
{
"id": "bullmq-specialist",
- "path": "skills/bullmq-specialist",
+ "path": "skills\\bullmq-specialist",
"category": "uncategorized",
"name": "bullmq-specialist",
"description": "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.",
@@ -1999,7 +2035,7 @@
},
{
"id": "bun-development",
- "path": "skills/bun-development",
+ "path": "skills\\bun-development",
"category": "uncategorized",
"name": "bun-development",
"description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o...",
@@ -2008,7 +2044,7 @@
},
{
"id": "burp-suite-testing",
- "path": "skills/burp-suite-testing",
+ "path": "skills\\burp-suite-testing",
"category": "uncategorized",
"name": "burp-suite-testing",
"description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ...",
@@ -2017,16 +2053,16 @@
},
{
"id": "business-analyst",
- "path": "skills/business-analyst",
+ "path": "skills\\business-analyst",
"category": "uncategorized",
- "name": "Business Analyst",
- "description": "- Working on business analyst tasks or workflows - Needing guidance, best practices, or checklists for business analyst",
+ "name": "business-analyst",
+ "description": "Master modern business analysis with AI-powered analytics,\nreal-time dashboards, and data-driven insights. Build comprehensive KPI\nframeworks, predictive models, and strategic recommendations. Use PROACTIVELY\nfor business intelligence or strategic analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "busybox-on-windows",
- "path": "skills/busybox-on-windows",
+ "path": "skills\\busybox-on-windows",
"category": "uncategorized",
"name": "busybox-on-windows",
"description": "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.",
@@ -2035,61 +2071,61 @@
},
{
"id": "c-pro",
- "path": "skills/c-pro",
+ "path": "skills\\c-pro",
"category": "uncategorized",
"name": "c-pro",
"description": "Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "c4-code",
- "path": "skills/c4-code",
- "category": "uncategorized",
- "name": "C4 Code",
- "description": "- Working on c4 code level: [directory name] tasks or workflows - Needing guidance, best practices, or checklists for c4 code level: [directory name]",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-component",
- "path": "skills/c4-component",
- "category": "uncategorized",
- "name": "C4 Component",
- "description": "- Working on c4 component level: [component name] tasks or workflows - Needing guidance, best practices, or checklists for c4 component level: [component name]",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-container",
- "path": "skills/c4-container",
- "category": "uncategorized",
- "name": "C4 Container",
- "description": "- Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "c4-context",
- "path": "skills/c4-context",
- "category": "uncategorized",
- "name": "C4 Context",
- "description": "- Working on c4 context level: system context tasks or workflows - Needing guidance, best practices, or checklists for c4 context level: system context",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "c4-architecture-c4-architecture",
- "path": "skills/c4-architecture-c4-architecture",
+ "path": "skills\\c4-architecture-c4-architecture",
"category": "uncategorized",
"name": "c4-architecture-c4-architecture",
"description": "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "c4-code",
+ "path": "skills\\c4-code",
+ "category": "uncategorized",
+ "name": "c4-code",
+ "description": "Expert C4 Code-level documentation specialist. Analyzes code\ndirectories to create comprehensive C4 code-level documentation including\nfunction signatures, arguments, dependencies, and code structure. Use when\ndocumenting code at the lowest C4 level for individual directories and code\nmodules.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-component",
+ "path": "skills\\c4-component",
+ "category": "uncategorized",
+ "name": "c4-component",
+ "description": "Expert C4 Component-level documentation specialist. Synthesizes C4\nCode-level documentation into Component-level architecture, defining component\nboundaries, interfaces, and relationships. Creates component diagrams and\ndocumentation. Use when synthesizing code-level documentation into logical\ncomponents.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-container",
+ "path": "skills\\c4-container",
+ "category": "uncategorized",
+ "name": "c4-container",
+ "description": "Expert C4 Container-level documentation specialist. Synthesizes\nComponent-level documentation into Container-level architecture, mapping\ncomponents to deployment units, documenting container interfaces as APIs, and\ncreating container diagrams. Use when synthesizing components into deployment\ncontainers and documenting system deployment architecture.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
+ {
+ "id": "c4-context",
+ "path": "skills\\c4-context",
+ "category": "uncategorized",
+ "name": "c4-context",
+ "description": "Expert C4 Context-level documentation specialist. Creates\nhigh-level system context diagrams, documents personas, user journeys, system\nfeatures, and external dependencies. Synthesizes container and component\ndocumentation with system documentation to create comprehensive context-level\narchitecture. Use when creating the highest-level C4 system context\ndocumentation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "cal-com-automation",
- "path": "skills/cal-com-automation",
+ "path": "skills\\cal-com-automation",
"category": "uncategorized",
"name": "cal-com-automation",
"description": "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.",
@@ -2098,7 +2134,7 @@
},
{
"id": "calc",
- "path": "skills/libreoffice/calc",
+ "path": "skills\\libreoffice\\calc",
"category": "libreoffice",
"name": "calc",
"description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
@@ -2107,7 +2143,7 @@
},
{
"id": "calendly-automation",
- "path": "skills/calendly-automation",
+ "path": "skills\\calendly-automation",
"category": "uncategorized",
"name": "calendly-automation",
"description": "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -2116,7 +2152,7 @@
},
{
"id": "canva-automation",
- "path": "skills/canva-automation",
+ "path": "skills\\canva-automation",
"category": "uncategorized",
"name": "canva-automation",
"description": "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.",
@@ -2125,16 +2161,25 @@
},
{
"id": "canvas-design",
- "path": "skills/canvas-design",
+ "path": "skills\\canvas-design",
"category": "uncategorized",
"name": "canvas-design",
"description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "carrier-relationship-management",
+ "path": "skills\\carrier-relationship-management",
+ "category": "uncategorized",
+ "name": "carrier-relationship-management",
+ "description": "Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting. Use when managing carriers, negotiating rates, evaluating carrier performance, or building freight strategies.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "cc-skill-backend-patterns",
- "path": "skills/cc-skill-backend-patterns",
+ "path": "skills\\cc-skill-backend-patterns",
"category": "uncategorized",
"name": "cc-skill-backend-patterns",
"description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
@@ -2143,7 +2188,7 @@
},
{
"id": "cc-skill-clickhouse-io",
- "path": "skills/cc-skill-clickhouse-io",
+ "path": "skills\\cc-skill-clickhouse-io",
"category": "uncategorized",
"name": "cc-skill-clickhouse-io",
"description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
@@ -2152,7 +2197,7 @@
},
{
"id": "cc-skill-coding-standards",
- "path": "skills/cc-skill-coding-standards",
+ "path": "skills\\cc-skill-coding-standards",
"category": "uncategorized",
"name": "cc-skill-coding-standards",
"description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
@@ -2161,7 +2206,7 @@
},
{
"id": "cc-skill-continuous-learning",
- "path": "skills/cc-skill-continuous-learning",
+ "path": "skills\\cc-skill-continuous-learning",
"category": "uncategorized",
"name": "cc-skill-continuous-learning",
"description": "Development skill from everything-claude-code",
@@ -2170,7 +2215,7 @@
},
{
"id": "cc-skill-frontend-patterns",
- "path": "skills/cc-skill-frontend-patterns",
+ "path": "skills\\cc-skill-frontend-patterns",
"category": "uncategorized",
"name": "cc-skill-frontend-patterns",
"description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
@@ -2179,7 +2224,7 @@
},
{
"id": "cc-skill-project-guidelines-example",
- "path": "skills/cc-skill-project-guidelines-example",
+ "path": "skills\\cc-skill-project-guidelines-example",
"category": "uncategorized",
"name": "cc-skill-project-guidelines-example",
"description": "Project Guidelines Skill (Example)",
@@ -2188,7 +2233,7 @@
},
{
"id": "cc-skill-security-review",
- "path": "skills/cc-skill-security-review",
+ "path": "skills\\cc-skill-security-review",
"category": "uncategorized",
"name": "cc-skill-security-review",
"description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...",
@@ -2197,7 +2242,7 @@
},
{
"id": "cc-skill-strategic-compact",
- "path": "skills/cc-skill-strategic-compact",
+ "path": "skills\\cc-skill-strategic-compact",
"category": "uncategorized",
"name": "cc-skill-strategic-compact",
"description": "Development skill from everything-claude-code",
@@ -2206,7 +2251,7 @@
},
{
"id": "cdk-patterns",
- "path": "skills/cdk-patterns",
+ "path": "skills\\cdk-patterns",
"category": "uncategorized",
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
@@ -2215,16 +2260,25 @@
},
{
"id": "changelog-automation",
- "path": "skills/changelog-automation",
+ "path": "skills\\changelog-automation",
"category": "uncategorized",
"name": "changelog-automation",
"description": "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "chrome-extension-developer",
+ "path": "skills\\chrome-extension-developer",
+ "category": "uncategorized",
+ "name": "chrome-extension-developer",
+ "description": "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "cicd-automation-workflow-automate",
- "path": "skills/cicd-automation-workflow-automate",
+ "path": "skills\\cicd-automation-workflow-automate",
"category": "uncategorized",
"name": "cicd-automation-workflow-automate",
"description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i...",
@@ -2233,7 +2287,7 @@
},
{
"id": "circleci-automation",
- "path": "skills/circleci-automation",
+ "path": "skills\\circleci-automation",
"category": "uncategorized",
"name": "circleci-automation",
"description": "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.",
@@ -2242,7 +2296,7 @@
},
{
"id": "clarity-gate",
- "path": "skills/clarity-gate",
+ "path": "skills\\clarity-gate",
"category": "uncategorized",
"name": "clarity-gate",
"description": "Pre-ingestion verification for epistemic quality in RAG systems with 9-point verification and Two-Round HITL workflow",
@@ -2251,7 +2305,7 @@
},
{
"id": "claude-ally-health",
- "path": "skills/claude-ally-health",
+ "path": "skills\\claude-ally-health",
"category": "uncategorized",
"name": "claude-ally-health",
"description": "A health assistant skill for medical information analysis, symptom tracking, and wellness guidance.",
@@ -2260,7 +2314,7 @@
},
{
"id": "claude-code-guide",
- "path": "skills/claude-code-guide",
+ "path": "skills\\claude-code-guide",
"category": "uncategorized",
"name": "claude-code-guide",
"description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit...",
@@ -2269,7 +2323,7 @@
},
{
"id": "claude-d3js-skill",
- "path": "skills/claude-d3js-skill",
+ "path": "skills\\claude-d3js-skill",
"category": "uncategorized",
"name": "claude-d3js-skill",
"description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...",
@@ -2278,7 +2332,7 @@
},
{
"id": "claude-scientific-skills",
- "path": "skills/claude-scientific-skills",
+ "path": "skills\\claude-scientific-skills",
"category": "uncategorized",
"name": "claude-scientific-skills",
"description": "Scientific research and analysis skills",
@@ -2287,7 +2341,7 @@
},
{
"id": "claude-speed-reader",
- "path": "skills/claude-speed-reader",
+ "path": "skills\\claude-speed-reader",
"category": "uncategorized",
"name": "claude-speed-reader",
"description": "-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting",
@@ -2296,7 +2350,7 @@
},
{
"id": "claude-win11-speckit-update-skill",
- "path": "skills/claude-win11-speckit-update-skill",
+ "path": "skills\\claude-win11-speckit-update-skill",
"category": "uncategorized",
"name": "claude-win11-speckit-update-skill",
"description": "Windows 11 system management",
@@ -2305,7 +2359,7 @@
},
{
"id": "clean-code",
- "path": "skills/clean-code",
+ "path": "skills\\clean-code",
"category": "uncategorized",
"name": "clean-code",
"description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...",
@@ -2314,7 +2368,7 @@
},
{
"id": "clerk-auth",
- "path": "skills/clerk-auth",
+ "path": "skills\\clerk-auth",
"category": "uncategorized",
"name": "clerk-auth",
"description": "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.",
@@ -2323,7 +2377,7 @@
},
{
"id": "clickup-automation",
- "path": "skills/clickup-automation",
+ "path": "skills\\clickup-automation",
"category": "uncategorized",
"name": "clickup-automation",
"description": "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -2332,7 +2386,7 @@
},
{
"id": "close-automation",
- "path": "skills/close-automation",
+ "path": "skills\\close-automation",
"category": "uncategorized",
"name": "close-automation",
"description": "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.",
@@ -2341,16 +2395,16 @@
},
{
"id": "cloud-architect",
- "path": "skills/cloud-architect",
+ "path": "skills\\cloud-architect",
"category": "uncategorized",
- "name": "Cloud Architect",
- "description": "- Working on cloud architect tasks or workflows - Needing guidance, best practices, or checklists for cloud architect",
+ "name": "cloud-architect",
+ "description": "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud\ninfrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost\noptimization, and modern architectural patterns. Masters serverless,\nmicroservices, security, compliance, and disaster recovery. Use PROACTIVELY\nfor cloud architecture, cost optimization, migration planning, or multi-cloud\nstrategies.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cloud-devops",
- "path": "skills/cloud-devops",
+ "path": "skills\\cloud-devops",
"category": "uncategorized",
"name": "cloud-devops",
"description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
@@ -2359,16 +2413,25 @@
},
{
"id": "cloud-penetration-testing",
- "path": "skills/cloud-penetration-testing",
+ "path": "skills\\cloud-penetration-testing",
"category": "uncategorized",
"name": "cloud-penetration-testing",
"description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "cloudflare-workers-expert",
+ "path": "skills\\cloudflare-workers-expert",
+ "category": "uncategorized",
+ "name": "cloudflare-workers-expert",
+ "description": "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "cloudformation-best-practices",
- "path": "skills/cloudformation-best-practices",
+ "path": "skills\\cloudformation-best-practices",
"category": "uncategorized",
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
@@ -2377,7 +2440,7 @@
},
{
"id": "coda-automation",
- "path": "skills/coda-automation",
+ "path": "skills\\coda-automation",
"category": "uncategorized",
"name": "coda-automation",
"description": "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.",
@@ -2386,7 +2449,7 @@
},
{
"id": "code-documentation-code-explain",
- "path": "skills/code-documentation-code-explain",
+ "path": "skills\\code-documentation-code-explain",
"category": "uncategorized",
"name": "code-documentation-code-explain",
"description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...",
@@ -2395,7 +2458,7 @@
},
{
"id": "code-documentation-doc-generate",
- "path": "skills/code-documentation-doc-generate",
+ "path": "skills\\code-documentation-doc-generate",
"category": "uncategorized",
"name": "code-documentation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
@@ -2404,7 +2467,7 @@
},
{
"id": "code-refactoring-context-restore",
- "path": "skills/code-refactoring-context-restore",
+ "path": "skills\\code-refactoring-context-restore",
"category": "uncategorized",
"name": "code-refactoring-context-restore",
"description": "Use when working with code refactoring context restore",
@@ -2413,7 +2476,7 @@
},
{
"id": "code-refactoring-refactor-clean",
- "path": "skills/code-refactoring-refactor-clean",
+ "path": "skills\\code-refactoring-refactor-clean",
"category": "uncategorized",
"name": "code-refactoring-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
@@ -2422,7 +2485,7 @@
},
{
"id": "code-refactoring-tech-debt",
- "path": "skills/code-refactoring-tech-debt",
+ "path": "skills\\code-refactoring-tech-debt",
"category": "uncategorized",
"name": "code-refactoring-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
@@ -2431,7 +2494,7 @@
},
{
"id": "code-review-ai-ai-review",
- "path": "skills/code-review-ai-ai-review",
+ "path": "skills\\code-review-ai-ai-review",
"category": "uncategorized",
"name": "code-review-ai-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
@@ -2440,7 +2503,7 @@
},
{
"id": "code-review-checklist",
- "path": "skills/code-review-checklist",
+ "path": "skills\\code-review-checklist",
"category": "uncategorized",
"name": "code-review-checklist",
"description": "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability",
@@ -2449,7 +2512,7 @@
},
{
"id": "code-review-excellence",
- "path": "skills/code-review-excellence",
+ "path": "skills\\code-review-excellence",
"category": "uncategorized",
"name": "code-review-excellence",
"description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...",
@@ -2458,7 +2521,7 @@
},
{
"id": "code-reviewer",
- "path": "skills/code-reviewer",
+ "path": "skills\\code-reviewer",
"category": "uncategorized",
"name": "code-reviewer",
"description": "Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.",
@@ -2467,7 +2530,7 @@
},
{
"id": "codebase-cleanup-deps-audit",
- "path": "skills/codebase-cleanup-deps-audit",
+ "path": "skills\\codebase-cleanup-deps-audit",
"category": "uncategorized",
"name": "codebase-cleanup-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
@@ -2476,7 +2539,7 @@
},
{
"id": "codebase-cleanup-refactor-clean",
- "path": "skills/codebase-cleanup-refactor-clean",
+ "path": "skills\\codebase-cleanup-refactor-clean",
"category": "uncategorized",
"name": "codebase-cleanup-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
@@ -2485,7 +2548,7 @@
},
{
"id": "codebase-cleanup-tech-debt",
- "path": "skills/codebase-cleanup-tech-debt",
+ "path": "skills\\codebase-cleanup-tech-debt",
"category": "uncategorized",
"name": "codebase-cleanup-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
@@ -2494,7 +2557,7 @@
},
{
"id": "codex-review",
- "path": "skills/codex-review",
+ "path": "skills\\codex-review",
"category": "uncategorized",
"name": "codex-review",
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI",
@@ -2503,7 +2566,7 @@
},
{
"id": "commit",
- "path": "skills/commit",
+ "path": "skills\\commit",
"category": "uncategorized",
"name": "commit",
"description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...",
@@ -2512,16 +2575,16 @@
},
{
"id": "competitive-landscape",
- "path": "skills/competitive-landscape",
+ "path": "skills\\competitive-landscape",
"category": "uncategorized",
- "name": "Competitive Landscape",
- "description": "Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.",
+ "name": "competitive-landscape",
+ "description": "This skill should be used when the user asks to \\\\\\\"analyze\ncompetitors\", \"assess competitive landscape\", \"identify differentiation\",\n\"evaluate market positioning\", \"apply Porter's Five Forces\", or requests\ncompetitive strategy analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "competitor-alternatives",
- "path": "skills/competitor-alternatives",
+ "path": "skills\\competitor-alternatives",
"category": "uncategorized",
"name": "competitor-alternatives",
"description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa...",
@@ -2530,7 +2593,7 @@
},
{
"id": "comprehensive-review-full-review",
- "path": "skills/comprehensive-review-full-review",
+ "path": "skills\\comprehensive-review-full-review",
"category": "uncategorized",
"name": "comprehensive-review-full-review",
"description": "Use when working with comprehensive review full review",
@@ -2539,7 +2602,7 @@
},
{
"id": "comprehensive-review-pr-enhance",
- "path": "skills/comprehensive-review-pr-enhance",
+ "path": "skills\\comprehensive-review-pr-enhance",
"category": "uncategorized",
"name": "comprehensive-review-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e...",
@@ -2548,7 +2611,7 @@
},
{
"id": "computer-use-agents",
- "path": "skills/computer-use-agents",
+ "path": "skills\\computer-use-agents",
"category": "uncategorized",
"name": "computer-use-agents",
"description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so...",
@@ -2557,7 +2620,7 @@
},
{
"id": "computer-vision-expert",
- "path": "skills/computer-vision-expert",
+ "path": "skills\\computer-vision-expert",
"category": "uncategorized",
"name": "computer-vision-expert",
"description": "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.",
@@ -2566,34 +2629,16 @@
},
{
"id": "concise-planning",
- "path": "skills/concise-planning",
+ "path": "skills\\concise-planning",
"category": "uncategorized",
"name": "concise-planning",
"description": "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "conductor-setup",
- "path": "skills/conductor-setup",
- "category": "uncategorized",
- "name": "Conductor Setup",
- "description": "Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "conductor-validator",
- "path": "skills/conductor-validator",
- "category": "uncategorized",
- "name": "Conductor Validator",
- "description": "ls -la conductor/",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "conductor-implement",
- "path": "skills/conductor-implement",
+ "path": "skills\\conductor-implement",
"category": "uncategorized",
"name": "conductor-implement",
"description": "Execute tasks from a track's implementation plan following TDD workflow",
@@ -2602,7 +2647,7 @@
},
{
"id": "conductor-manage",
- "path": "skills/conductor-manage",
+ "path": "skills\\conductor-manage",
"category": "uncategorized",
"name": "conductor-manage",
"description": "Manage track lifecycle: archive, restore, delete, rename, and cleanup",
@@ -2611,7 +2656,7 @@
},
{
"id": "conductor-new-track",
- "path": "skills/conductor-new-track",
+ "path": "skills\\conductor-new-track",
"category": "uncategorized",
"name": "conductor-new-track",
"description": "Create a new track with specification and phased implementation plan",
@@ -2620,43 +2665,52 @@
},
{
"id": "conductor-revert",
- "path": "skills/conductor-revert",
+ "path": "skills\\conductor-revert",
"category": "uncategorized",
"name": "conductor-revert",
"description": "Git-aware undo by logical work unit (track, phase, or task)",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "conductor-setup",
+ "path": "skills\\conductor-setup",
+ "category": "uncategorized",
+ "name": "conductor-setup",
+ "description": "Initialize project with Conductor artifacts (product definition,\ntech stack, workflow, style guides)\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "conductor-status",
- "path": "skills/conductor-status",
+ "path": "skills\\conductor-status",
"category": "uncategorized",
"name": "conductor-status",
"description": "Display project status, active tracks, and next actions",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "conductor-validator",
+ "path": "skills\\conductor-validator",
+ "category": "uncategorized",
+ "name": "conductor-validator",
+ "description": "Validates Conductor project artifacts for completeness,\nconsistency, and correctness. Use after setup, when diagnosing issues, or\nbefore implementation to verify project context.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "confluence-automation",
- "path": "skills/confluence-automation",
+ "path": "skills\\confluence-automation",
"category": "uncategorized",
"name": "confluence-automation",
"description": "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "content-marketer",
- "path": "skills/content-marketer",
- "category": "uncategorized",
- "name": "Content Marketer",
- "description": "- Working on content marketer tasks or workflows - Needing guidance, best practices, or checklists for content marketer",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "content-creator",
- "path": "skills/content-creator",
+ "path": "skills\\content-creator",
"category": "uncategorized",
"name": "content-creator",
"description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati...",
@@ -2664,26 +2718,17 @@
"source": "community"
},
{
- "id": "context-driven-development",
- "path": "skills/context-driven-development",
+ "id": "content-marketer",
+ "path": "skills\\content-marketer",
"category": "uncategorized",
- "name": "Context Driven Development",
- "description": "Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.",
+ "name": "content-marketer",
+ "description": "Elite content marketing strategist specializing in AI-powered\ncontent creation, omnichannel distribution, SEO optimization, and data-driven\nperformance marketing. Masters modern content tools, social media automation,\nand conversion optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive content marketing.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "context-manager",
- "path": "skills/context-manager",
- "category": "uncategorized",
- "name": "Context Manager",
- "description": "- Working on context manager tasks or workflows - Needing guidance, best practices, or checklists for context manager",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "context-compression",
- "path": "skills/context-compression",
+ "path": "skills\\context-compression",
"category": "uncategorized",
"name": "context-compression",
"description": "Design and evaluate compression strategies for long-running sessions",
@@ -2692,16 +2737,25 @@
},
{
"id": "context-degradation",
- "path": "skills/context-degradation",
+ "path": "skills\\context-degradation",
"category": "uncategorized",
"name": "context-degradation",
"description": "Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash",
"risk": "safe",
"source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation"
},
+ {
+ "id": "context-driven-development",
+ "path": "skills\\context-driven-development",
+ "category": "uncategorized",
+ "name": "context-driven-development",
+ "description": "Use this skill when working with Conductor's context-driven\ndevelopment methodology, managing project context artifacts, or understanding\nthe relationship between product.md, tech-stack.md, and workflow.md files.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "context-fundamentals",
- "path": "skills/context-fundamentals",
+ "path": "skills\\context-fundamentals",
"category": "uncategorized",
"name": "context-fundamentals",
"description": "Understand what context is, why it matters, and the anatomy of context in agent systems",
@@ -2710,7 +2764,7 @@
},
{
"id": "context-management-context-restore",
- "path": "skills/context-management-context-restore",
+ "path": "skills\\context-management-context-restore",
"category": "uncategorized",
"name": "context-management-context-restore",
"description": "Use when working with context management context restore",
@@ -2719,16 +2773,25 @@
},
{
"id": "context-management-context-save",
- "path": "skills/context-management-context-save",
+ "path": "skills\\context-management-context-save",
"category": "uncategorized",
"name": "context-management-context-save",
"description": "Use when working with context management context save",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "context-manager",
+ "path": "skills\\context-manager",
+ "category": "uncategorized",
+ "name": "context-manager",
+ "description": "Elite AI context engineering specialist mastering dynamic context\nmanagement, vector databases, knowledge graphs, and intelligent memory\nsystems. Orchestrates context across multi-agent workflows, enterprise AI\nsystems, and long-running projects with 2024/2025 best practices. Use\nPROACTIVELY for complex AI orchestration.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "context-optimization",
- "path": "skills/context-optimization",
+ "path": "skills\\context-optimization",
"category": "uncategorized",
"name": "context-optimization",
"description": "Apply compaction, masking, and caching strategies",
@@ -2737,7 +2800,7 @@
},
{
"id": "context-window-management",
- "path": "skills/context-window-management",
+ "path": "skills\\context-window-management",
"category": "uncategorized",
"name": "context-window-management",
"description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...",
@@ -2746,7 +2809,7 @@
},
{
"id": "context7-auto-research",
- "path": "skills/context7-auto-research",
+ "path": "skills\\context7-auto-research",
"category": "uncategorized",
"name": "context7-auto-research",
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API",
@@ -2755,7 +2818,7 @@
},
{
"id": "conversation-memory",
- "path": "skills/conversation-memory",
+ "path": "skills\\conversation-memory",
"category": "uncategorized",
"name": "conversation-memory",
"description": "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.",
@@ -2764,7 +2827,7 @@
},
{
"id": "convertkit-automation",
- "path": "skills/convertkit-automation",
+ "path": "skills\\convertkit-automation",
"category": "uncategorized",
"name": "convertkit-automation",
"description": "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.",
@@ -2773,7 +2836,7 @@
},
{
"id": "copilot-sdk",
- "path": "skills/copilot-sdk",
+ "path": "skills\\copilot-sdk",
"category": "uncategorized",
"name": "copilot-sdk",
"description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen...",
@@ -2782,7 +2845,7 @@
},
{
"id": "copy-editing",
- "path": "skills/copy-editing",
+ "path": "skills\\copy-editing",
"category": "uncategorized",
"name": "copy-editing",
"description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ...",
@@ -2791,16 +2854,16 @@
},
{
"id": "copywriting",
- "path": "skills/copywriting",
+ "path": "skills\\copywriting",
"category": "uncategorized",
- "name": "Copywriting",
- "description": "Produce **clear, credible, and action-oriented marketing copy** that aligns with user intent and business goals.",
+ "name": "copywriting",
+ "description": "Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "core-components",
- "path": "skills/core-components",
+ "path": "skills\\core-components",
"category": "uncategorized",
"name": "core-components",
"description": "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.",
@@ -2809,7 +2872,7 @@
},
{
"id": "cost-optimization",
- "path": "skills/cost-optimization",
+ "path": "skills\\cost-optimization",
"category": "uncategorized",
"name": "cost-optimization",
"description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...",
@@ -2818,16 +2881,16 @@
},
{
"id": "cpp-pro",
- "path": "skills/cpp-pro",
+ "path": "skills\\cpp-pro",
"category": "uncategorized",
- "name": "Cpp Pro",
- "description": "- Working on cpp pro tasks or workflows - Needing guidance, best practices, or checklists for cpp pro",
+ "name": "cpp-pro",
+ "description": "Write idiomatic C++ code with modern features, RAII, smart\npointers, and STL algorithms. Handles templates, move semantics, and\nperformance optimization. Use PROACTIVELY for C++ refactoring, memory safety,\nor complex C++ patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "cqrs-implementation",
- "path": "skills/cqrs-implementation",
+ "path": "skills\\cqrs-implementation",
"category": "uncategorized",
"name": "cqrs-implementation",
"description": "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.",
@@ -2836,7 +2899,7 @@
},
{
"id": "create-pr",
- "path": "skills/create-pr",
+ "path": "skills\\create-pr",
"category": "uncategorized",
"name": "create-pr",
"description": "Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.",
@@ -2845,7 +2908,7 @@
},
{
"id": "crewai",
- "path": "skills/crewai",
+ "path": "skills\\crewai",
"category": "uncategorized",
"name": "crewai",
"description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s...",
@@ -2854,25 +2917,25 @@
},
{
"id": "crypto-bd-agent",
- "path": "skills/crypto-bd-agent",
+ "path": "skills\\crypto-bd-agent",
"category": "uncategorized",
- "name": "Crypto Bd Agent",
- "description": "> Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.",
- "risk": "unknown",
- "source": "unknown"
+ "name": "crypto-bd-agent",
+ "description": "Autonomous crypto business development patterns \u2014 multi-chain token discovery, 100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain identity, LLM cascade routing, and pipeline automation for CEX/DEX listing acquisition. Use when building AI agents for crypto BD, token evaluation, exchange listing outreach, or autonomous commerce with payment protocols.\n",
+ "risk": "safe",
+ "source": "community"
},
{
"id": "csharp-pro",
- "path": "skills/csharp-pro",
+ "path": "skills\\csharp-pro",
"category": "uncategorized",
- "name": "Csharp Pro",
- "description": "- Working on csharp pro tasks or workflows - Needing guidance, best practices, or checklists for csharp pro",
+ "name": "csharp-pro",
+ "description": "Write modern C# code with advanced features like records, pattern\nmatching, and async/await. Optimizes .NET applications, implements enterprise\npatterns, and ensures comprehensive testing. Use PROACTIVELY for C#\nrefactoring, performance optimization, or complex .NET solutions.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "culture-index",
- "path": "skills/culture-index",
+ "path": "skills\\culture-index",
"category": "uncategorized",
"name": "culture-index",
"description": "Index and search culture documentation",
@@ -2881,16 +2944,25 @@
},
{
"id": "customer-support",
- "path": "skills/customer-support",
+ "path": "skills\\customer-support",
"category": "uncategorized",
- "name": "Customer Support",
- "description": "- Working on customer support tasks or workflows - Needing guidance, best practices, or checklists for customer support",
+ "name": "customer-support",
+ "description": "Elite AI-powered customer support specialist mastering\nconversational AI, automated ticketing, sentiment analysis, and omnichannel\nsupport experiences. Integrates modern support tools, chatbot platforms, and\nCX optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive customer experience management.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "customs-trade-compliance",
+ "path": "skills\\customs-trade-compliance",
+ "category": "uncategorized",
+ "name": "customs-trade-compliance",
+ "description": "Codified expertise for customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilisation, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimisation.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
},
{
"id": "daily-news-report",
- "path": "skills/daily-news-report",
+ "path": "skills\\daily-news-report",
"category": "uncategorized",
"name": "daily-news-report",
"description": "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.",
@@ -2899,25 +2971,16 @@
},
{
"id": "data-engineer",
- "path": "skills/data-engineer",
+ "path": "skills\\data-engineer",
"category": "uncategorized",
- "name": "Data Engineer",
- "description": "You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.",
+ "name": "data-engineer",
+ "description": "Build scalable data pipelines, modern data warehouses, and\nreal-time streaming architectures. Implements Apache Spark, dbt, Airflow, and\ncloud-native data platforms. Use PROACTIVELY for data pipeline design,\nanalytics infrastructure, or modern data stack implementation.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "data-scientist",
- "path": "skills/data-scientist",
- "category": "uncategorized",
- "name": "Data Scientist",
- "description": "- Working on data scientist tasks or workflows - Needing guidance, best practices, or checklists for data scientist",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "data-engineering-data-driven-feature",
- "path": "skills/data-engineering-data-driven-feature",
+ "path": "skills\\data-engineering-data-driven-feature",
"category": "uncategorized",
"name": "data-engineering-data-driven-feature",
"description": "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.",
@@ -2926,7 +2989,7 @@
},
{
"id": "data-engineering-data-pipeline",
- "path": "skills/data-engineering-data-pipeline",
+ "path": "skills\\data-engineering-data-pipeline",
"category": "uncategorized",
"name": "data-engineering-data-pipeline",
"description": "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.",
@@ -2935,16 +2998,25 @@
},
{
"id": "data-quality-frameworks",
- "path": "skills/data-quality-frameworks",
+ "path": "skills\\data-quality-frameworks",
"category": "uncategorized",
"name": "data-quality-frameworks",
"description": "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "data-scientist",
+ "path": "skills\\data-scientist",
+ "category": "uncategorized",
+ "name": "data-scientist",
+ "description": "Expert data scientist for advanced analytics, machine learning, and\nstatistical modeling. Handles complex data analysis, predictive modeling, and\nbusiness intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,\nstatistical analysis, and data-driven insights.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "data-storytelling",
- "path": "skills/data-storytelling",
+ "path": "skills\\data-storytelling",
"category": "uncategorized",
"name": "data-storytelling",
"description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present...",
@@ -2953,7 +3025,7 @@
},
{
"id": "data-structure-protocol",
- "path": "skills/data-structure-protocol",
+ "path": "skills\\data-structure-protocol",
"category": "uncategorized",
"name": "data-structure-protocol",
"description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
@@ -2962,7 +3034,7 @@
},
{
"id": "database",
- "path": "skills/database",
+ "path": "skills\\database",
"category": "uncategorized",
"name": "database",
"description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
@@ -2971,34 +3043,25 @@
},
{
"id": "database-admin",
- "path": "skills/database-admin",
+ "path": "skills\\database-admin",
"category": "uncategorized",
- "name": "Database Admin",
- "description": "- Working on database admin tasks or workflows - Needing guidance, best practices, or checklists for database admin",
+ "name": "database-admin",
+ "description": "Expert database administrator specializing in modern cloud\ndatabases, automation, and reliability engineering. Masters AWS/Azure/GCP\ndatabase services, Infrastructure as Code, high availability, disaster\nrecovery, performance optimization, and compliance. Handles multi-cloud\nstrategies, container databases, and cost optimization. Use PROACTIVELY for\ndatabase architecture, operations, or reliability engineering.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-architect",
- "path": "skills/database-architect",
+ "path": "skills\\database-architect",
"category": "uncategorized",
- "name": "Database Architect",
- "description": "You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.",
+ "name": "database-architect",
+ "description": "Expert database architect specializing in data layer design from\nscratch, technology selection, schema modeling, and scalable database\narchitectures. Masters SQL/NoSQL/TimeSeries database selection, normalization\nstrategies, migration planning, and performance-first design. Handles both\ngreenfield architectures and re-architecture of existing systems. Use\nPROACTIVELY for database architecture, technology selection, or data modeling\ndecisions.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "database-optimizer",
- "path": "skills/database-optimizer",
- "category": "uncategorized",
- "name": "Database Optimizer",
- "description": "- Working on database optimizer tasks or workflows - Needing guidance, best practices, or checklists for database optimizer",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "database-cloud-optimization-cost-optimize",
- "path": "skills/database-cloud-optimization-cost-optimize",
+ "path": "skills\\database-cloud-optimization-cost-optimize",
"category": "uncategorized",
"name": "database-cloud-optimization-cost-optimize",
"description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ...",
@@ -3007,7 +3070,7 @@
},
{
"id": "database-design",
- "path": "skills/database-design",
+ "path": "skills\\database-design",
"category": "uncategorized",
"name": "database-design",
"description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
@@ -3016,7 +3079,7 @@
},
{
"id": "database-migration",
- "path": "skills/database-migration",
+ "path": "skills\\database-migration",
"category": "uncategorized",
"name": "database-migration",
"description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...",
@@ -3025,7 +3088,7 @@
},
{
"id": "database-migrations-migration-observability",
- "path": "skills/database-migrations-migration-observability",
+ "path": "skills\\database-migrations-migration-observability",
"category": "uncategorized",
"name": "database-migrations-migration-observability",
"description": "Migration monitoring, CDC, and observability infrastructure",
@@ -3034,16 +3097,25 @@
},
{
"id": "database-migrations-sql-migrations",
- "path": "skills/database-migrations-sql-migrations",
+ "path": "skills\\database-migrations-sql-migrations",
"category": "uncategorized",
"name": "database-migrations-sql-migrations",
"description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "database-optimizer",
+ "path": "skills\\database-optimizer",
+ "category": "uncategorized",
+ "name": "database-optimizer",
+ "description": "Expert database optimizer specializing in modern performance\ntuning, query optimization, and scalable architectures. Masters advanced\nindexing, N+1 resolution, multi-tier caching, partitioning strategies, and\ncloud database optimization. Handles complex query analysis, migration\nstrategies, and performance monitoring. Use PROACTIVELY for database\noptimization, performance issues, or scalability challenges.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "datadog-automation",
- "path": "skills/datadog-automation",
+ "path": "skills\\datadog-automation",
"category": "uncategorized",
"name": "datadog-automation",
"description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
@@ -3052,7 +3124,7 @@
},
{
"id": "dbos-golang",
- "path": "skills/dbos-golang",
+ "path": "skills\\dbos-golang",
"category": "uncategorized",
"name": "dbos-golang",
"description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie...",
@@ -3061,7 +3133,7 @@
},
{
"id": "dbos-python",
- "path": "skills/dbos-python",
+ "path": "skills\\dbos-python",
"category": "uncategorized",
"name": "dbos-python",
"description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC...",
@@ -3070,7 +3142,7 @@
},
{
"id": "dbos-typescript",
- "path": "skills/dbos-typescript",
+ "path": "skills\\dbos-typescript",
"category": "uncategorized",
"name": "dbos-typescript",
"description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi...",
@@ -3079,7 +3151,7 @@
},
{
"id": "dbt-transformation-patterns",
- "path": "skills/dbt-transformation-patterns",
+ "path": "skills\\dbt-transformation-patterns",
"category": "uncategorized",
"name": "dbt-transformation-patterns",
"description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ...",
@@ -3088,7 +3160,7 @@
},
{
"id": "ddd-context-mapping",
- "path": "skills/ddd-context-mapping",
+ "path": "skills\\ddd-context-mapping",
"category": "uncategorized",
"name": "ddd-context-mapping",
"description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
@@ -3097,7 +3169,7 @@
},
{
"id": "ddd-strategic-design",
- "path": "skills/ddd-strategic-design",
+ "path": "skills\\ddd-strategic-design",
"category": "uncategorized",
"name": "ddd-strategic-design",
"description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
@@ -3106,7 +3178,7 @@
},
{
"id": "ddd-tactical-patterns",
- "path": "skills/ddd-tactical-patterns",
+ "path": "skills\\ddd-tactical-patterns",
"category": "uncategorized",
"name": "ddd-tactical-patterns",
"description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
@@ -3115,16 +3187,16 @@
},
{
"id": "debugger",
- "path": "skills/debugger",
+ "path": "skills\\debugger",
"category": "uncategorized",
- "name": "Debugger",
- "description": "- Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger",
+ "name": "debugger",
+ "description": "Debugging specialist for errors, test failures, and unexpected\nbehavior. Use proactively when encountering any issues.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "debugging-strategies",
- "path": "skills/debugging-strategies",
+ "path": "skills\\debugging-strategies",
"category": "uncategorized",
"name": "debugging-strategies",
"description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss...",
@@ -3133,7 +3205,7 @@
},
{
"id": "debugging-toolkit-smart-debug",
- "path": "skills/debugging-toolkit-smart-debug",
+ "path": "skills\\debugging-toolkit-smart-debug",
"category": "uncategorized",
"name": "debugging-toolkit-smart-debug",
"description": "Use when working with debugging toolkit smart debug",
@@ -3142,7 +3214,7 @@
},
{
"id": "deep-research",
- "path": "skills/deep-research",
+ "path": "skills\\deep-research",
"category": "uncategorized",
"name": "deep-research",
"description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ...",
@@ -3151,7 +3223,7 @@
},
{
"id": "defi-protocol-templates",
- "path": "skills/defi-protocol-templates",
+ "path": "skills\\defi-protocol-templates",
"category": "uncategorized",
"name": "defi-protocol-templates",
"description": "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.",
@@ -3160,7 +3232,7 @@
},
{
"id": "dependency-management-deps-audit",
- "path": "skills/dependency-management-deps-audit",
+ "path": "skills\\dependency-management-deps-audit",
"category": "uncategorized",
"name": "dependency-management-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
@@ -3169,7 +3241,7 @@
},
{
"id": "dependency-upgrade",
- "path": "skills/dependency-upgrade",
+ "path": "skills\\dependency-upgrade",
"category": "uncategorized",
"name": "dependency-upgrade",
"description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...",
@@ -3178,16 +3250,16 @@
},
{
"id": "deployment-engineer",
- "path": "skills/deployment-engineer",
+ "path": "skills\\deployment-engineer",
"category": "uncategorized",
- "name": "Deployment Engineer",
- "description": "You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.",
+ "name": "deployment-engineer",
+ "description": "Expert deployment engineer specializing in modern CI/CD pipelines,\nGitOps workflows, and advanced deployment automation. Masters GitHub Actions,\nArgoCD/Flux, progressive delivery, container security, and platform\nengineering. Handles zero-downtime deployments, security scanning, and\ndeveloper experience optimization. Use PROACTIVELY for CI/CD design, GitOps\nimplementation, or deployment automation.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "deployment-pipeline-design",
- "path": "skills/deployment-pipeline-design",
+ "path": "skills\\deployment-pipeline-design",
"category": "uncategorized",
"name": "deployment-pipeline-design",
"description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi...",
@@ -3196,7 +3268,7 @@
},
{
"id": "deployment-procedures",
- "path": "skills/deployment-procedures",
+ "path": "skills\\deployment-procedures",
"category": "uncategorized",
"name": "deployment-procedures",
"description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.",
@@ -3205,7 +3277,7 @@
},
{
"id": "deployment-validation-config-validate",
- "path": "skills/deployment-validation-config-validate",
+ "path": "skills\\deployment-validation-config-validate",
"category": "uncategorized",
"name": "deployment-validation-config-validate",
"description": "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat",
@@ -3214,7 +3286,7 @@
},
{
"id": "design-md",
- "path": "skills/design-md",
+ "path": "skills\\design-md",
"category": "uncategorized",
"name": "design-md",
"description": "Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files",
@@ -3223,7 +3295,7 @@
},
{
"id": "design-orchestration",
- "path": "skills/design-orchestration",
+ "path": "skills\\design-orchestration",
"category": "uncategorized",
"name": "design-orchestration",
"description": "Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.",
@@ -3232,7 +3304,7 @@
},
{
"id": "development",
- "path": "skills/development",
+ "path": "skills\\development",
"category": "uncategorized",
"name": "development",
"description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
@@ -3241,16 +3313,16 @@
},
{
"id": "devops-troubleshooter",
- "path": "skills/devops-troubleshooter",
+ "path": "skills\\devops-troubleshooter",
"category": "uncategorized",
- "name": "Devops Troubleshooter",
- "description": "- Working on devops troubleshooter tasks or workflows - Needing guidance, best practices, or checklists for devops troubleshooter",
+ "name": "devops-troubleshooter",
+ "description": "Expert DevOps troubleshooter specializing in rapid incident\nresponse, advanced debugging, and modern observability. Masters log analysis,\ndistributed tracing, Kubernetes debugging, performance optimization, and root\ncause analysis. Handles production outages, system reliability, and preventive\nmonitoring. Use PROACTIVELY for debugging, incident response, or system\ntroubleshooting.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "discord-automation",
- "path": "skills/discord-automation",
+ "path": "skills\\discord-automation",
"category": "uncategorized",
"name": "discord-automation",
"description": "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.",
@@ -3259,7 +3331,7 @@
},
{
"id": "discord-bot-architect",
- "path": "skills/discord-bot-architect",
+ "path": "skills\\discord-bot-architect",
"category": "uncategorized",
"name": "discord-bot-architect",
"description": "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.",
@@ -3268,7 +3340,7 @@
},
{
"id": "dispatching-parallel-agents",
- "path": "skills/dispatching-parallel-agents",
+ "path": "skills\\dispatching-parallel-agents",
"category": "uncategorized",
"name": "dispatching-parallel-agents",
"description": "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies",
@@ -3277,7 +3349,7 @@
},
{
"id": "distributed-debugging-debug-trace",
- "path": "skills/distributed-debugging-debug-trace",
+ "path": "skills\\distributed-debugging-debug-trace",
"category": "uncategorized",
"name": "distributed-debugging-debug-trace",
"description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an...",
@@ -3286,7 +3358,7 @@
},
{
"id": "distributed-tracing",
- "path": "skills/distributed-tracing",
+ "path": "skills\\distributed-tracing",
"category": "uncategorized",
"name": "distributed-tracing",
"description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem...",
@@ -3295,16 +3367,16 @@
},
{
"id": "django-pro",
- "path": "skills/django-pro",
+ "path": "skills\\django-pro",
"category": "uncategorized",
- "name": "Django Pro",
- "description": "- Working on django pro tasks or workflows - Needing guidance, best practices, or checklists for django pro",
+ "name": "django-pro",
+ "description": "Master Django 5.x with async views, DRF, Celery, and Django\nChannels. Build scalable web applications with proper architecture, testing,\nand deployment. Use PROACTIVELY for Django development, ORM optimization, or\ncomplex Django patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "doc-coauthoring",
- "path": "skills/doc-coauthoring",
+ "path": "skills\\doc-coauthoring",
"category": "uncategorized",
"name": "doc-coauthoring",
"description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ...",
@@ -3313,7 +3385,7 @@
},
{
"id": "docker-expert",
- "path": "skills/docker-expert",
+ "path": "skills\\docker-expert",
"category": "uncategorized",
"name": "docker-expert",
"description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f...",
@@ -3322,16 +3394,16 @@
},
{
"id": "docs-architect",
- "path": "skills/docs-architect",
+ "path": "skills\\docs-architect",
"category": "uncategorized",
- "name": "Docs Architect",
- "description": "- Working on docs architect tasks or workflows - Needing guidance, best practices, or checklists for docs architect",
+ "name": "docs-architect",
+ "description": "Creates comprehensive technical documentation from existing\ncodebases. Analyzes architecture, design patterns, and implementation details\nto produce long-form technical manuals and ebooks. Use PROACTIVELY for system\ndocumentation, architecture guides, or technical deep-dives.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "documentation",
- "path": "skills/documentation",
+ "path": "skills\\documentation",
"category": "uncategorized",
"name": "documentation",
"description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
@@ -3340,7 +3412,7 @@
},
{
"id": "documentation-generation-doc-generate",
- "path": "skills/documentation-generation-doc-generate",
+ "path": "skills\\documentation-generation-doc-generate",
"category": "uncategorized",
"name": "documentation-generation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
@@ -3349,7 +3421,7 @@
},
{
"id": "documentation-templates",
- "path": "skills/documentation-templates",
+ "path": "skills\\documentation-templates",
"category": "uncategorized",
"name": "documentation-templates",
"description": "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.",
@@ -3358,7 +3430,7 @@
},
{
"id": "docusign-automation",
- "path": "skills/docusign-automation",
+ "path": "skills\\docusign-automation",
"category": "uncategorized",
"name": "docusign-automation",
"description": "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.",
@@ -3367,7 +3439,7 @@
},
{
"id": "docx-official",
- "path": "skills/docx-official",
+ "path": "skills\\docx-official",
"category": "uncategorized",
"name": "docx-official",
"description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document...",
@@ -3376,7 +3448,7 @@
},
{
"id": "domain-driven-design",
- "path": "skills/domain-driven-design",
+ "path": "skills\\domain-driven-design",
"category": "uncategorized",
"name": "domain-driven-design",
"description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
@@ -3385,16 +3457,16 @@
},
{
"id": "dotnet-architect",
- "path": "skills/dotnet-architect",
+ "path": "skills\\dotnet-architect",
"category": "uncategorized",
- "name": "Dotnet Architect",
- "description": "- Working on dotnet architect tasks or workflows - Needing guidance, best practices, or checklists for dotnet architect",
+ "name": "dotnet-architect",
+ "description": "Expert .NET backend architect specializing in C#, ASP.NET Core,\nEntity Framework, Dapper, and enterprise application patterns. Masters\nasync/await, dependency injection, caching strategies, and performance\noptimization. Use PROACTIVELY for .NET API development, code review, or\narchitecture decisions.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "dotnet-backend",
- "path": "skills/dotnet-backend",
+ "path": "skills\\dotnet-backend",
"category": "uncategorized",
"name": "dotnet-backend",
"description": "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.",
@@ -3403,7 +3475,7 @@
},
{
"id": "dotnet-backend-patterns",
- "path": "skills/dotnet-backend-patterns",
+ "path": "skills\\dotnet-backend-patterns",
"category": "uncategorized",
"name": "dotnet-backend-patterns",
"description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...",
@@ -3412,7 +3484,7 @@
},
{
"id": "draw",
- "path": "skills/libreoffice/draw",
+ "path": "skills\\libreoffice\\draw",
"category": "libreoffice",
"name": "draw",
"description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
@@ -3421,7 +3493,7 @@
},
{
"id": "dropbox-automation",
- "path": "skills/dropbox-automation",
+ "path": "skills\\dropbox-automation",
"category": "uncategorized",
"name": "dropbox-automation",
"description": "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -3430,16 +3502,16 @@
},
{
"id": "dx-optimizer",
- "path": "skills/dx-optimizer",
+ "path": "skills\\dx-optimizer",
"category": "uncategorized",
- "name": "Dx Optimizer",
- "description": "- Working on dx optimizer tasks or workflows - Needing guidance, best practices, or checklists for dx optimizer",
+ "name": "dx-optimizer",
+ "description": "Developer Experience specialist. Improves tooling, setup, and\nworkflows. Use PROACTIVELY when setting up new projects, after team feedback,\nor when development friction is noticed.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "e2e-testing",
- "path": "skills/e2e-testing",
+ "path": "skills\\e2e-testing",
"category": "uncategorized",
"name": "e2e-testing",
"description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
@@ -3448,7 +3520,7 @@
},
{
"id": "e2e-testing-patterns",
- "path": "skills/e2e-testing-patterns",
+ "path": "skills\\e2e-testing-patterns",
"category": "uncategorized",
"name": "e2e-testing-patterns",
"description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...",
@@ -3457,16 +3529,16 @@
},
{
"id": "elixir-pro",
- "path": "skills/elixir-pro",
+ "path": "skills\\elixir-pro",
"category": "uncategorized",
- "name": "Elixir Pro",
- "description": "- Working on elixir pro tasks or workflows - Needing guidance, best practices, or checklists for elixir pro",
+ "name": "elixir-pro",
+ "description": "Write idiomatic Elixir code with OTP patterns, supervision trees,\nand Phoenix LiveView. Masters concurrency, fault tolerance, and distributed\nsystems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM\noptimizations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "email-sequence",
- "path": "skills/email-sequence",
+ "path": "skills\\email-sequence",
"category": "uncategorized",
"name": "email-sequence",
"description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa...",
@@ -3475,7 +3547,7 @@
},
{
"id": "email-systems",
- "path": "skills/email-systems",
+ "path": "skills\\email-systems",
"category": "uncategorized",
"name": "email-systems",
"description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov...",
@@ -3484,7 +3556,7 @@
},
{
"id": "embedding-strategies",
- "path": "skills/embedding-strategies",
+ "path": "skills\\embedding-strategies",
"category": "uncategorized",
"name": "embedding-strategies",
"description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom...",
@@ -3493,34 +3565,34 @@
},
{
"id": "employment-contract-templates",
- "path": "skills/employment-contract-templates",
+ "path": "skills\\employment-contract-templates",
"category": "uncategorized",
"name": "employment-contract-templates",
"description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "energy-procurement",
+ "path": "skills\\energy-procurement",
+ "category": "uncategorized",
+ "name": "energy-procurement",
+ "description": "Codified expertise for electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimising tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "environment-setup-guide",
- "path": "skills/environment-setup-guide",
+ "path": "skills\\environment-setup-guide",
"category": "uncategorized",
"name": "environment-setup-guide",
"description": "Guide developers through setting up development environments with proper tools, dependencies, and configurations",
"risk": "unknown",
"source": "community"
},
- {
- "id": "error-detective",
- "path": "skills/error-detective",
- "category": "uncategorized",
- "name": "Error Detective",
- "description": "- Working on error detective tasks or workflows - Needing guidance, best practices, or checklists for error detective",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "error-debugging-error-analysis",
- "path": "skills/error-debugging-error-analysis",
+ "path": "skills\\error-debugging-error-analysis",
"category": "uncategorized",
"name": "error-debugging-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
@@ -3529,7 +3601,7 @@
},
{
"id": "error-debugging-error-trace",
- "path": "skills/error-debugging-error-trace",
+ "path": "skills\\error-debugging-error-trace",
"category": "uncategorized",
"name": "error-debugging-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi...",
@@ -3538,16 +3610,25 @@
},
{
"id": "error-debugging-multi-agent-review",
- "path": "skills/error-debugging-multi-agent-review",
+ "path": "skills\\error-debugging-multi-agent-review",
"category": "uncategorized",
"name": "error-debugging-multi-agent-review",
"description": "Use when working with error debugging multi agent review",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "error-detective",
+ "path": "skills\\error-detective",
+ "category": "uncategorized",
+ "name": "error-detective",
+ "description": "Search logs and codebases for error patterns, stack traces, and\nanomalies. Correlates errors across systems and identifies root causes. Use\nPROACTIVELY when debugging issues, analyzing logs, or investigating production\nerrors.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "error-diagnostics-error-analysis",
- "path": "skills/error-diagnostics-error-analysis",
+ "path": "skills\\error-diagnostics-error-analysis",
"category": "uncategorized",
"name": "error-diagnostics-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
@@ -3556,7 +3637,7 @@
},
{
"id": "error-diagnostics-error-trace",
- "path": "skills/error-diagnostics-error-trace",
+ "path": "skills\\error-diagnostics-error-trace",
"category": "uncategorized",
"name": "error-diagnostics-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,",
@@ -3565,7 +3646,7 @@
},
{
"id": "error-diagnostics-smart-debug",
- "path": "skills/error-diagnostics-smart-debug",
+ "path": "skills\\error-diagnostics-smart-debug",
"category": "uncategorized",
"name": "error-diagnostics-smart-debug",
"description": "Use when working with error diagnostics smart debug",
@@ -3574,7 +3655,7 @@
},
{
"id": "error-handling-patterns",
- "path": "skills/error-handling-patterns",
+ "path": "skills\\error-handling-patterns",
"category": "uncategorized",
"name": "error-handling-patterns",
"description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling...",
@@ -3583,7 +3664,7 @@
},
{
"id": "ethical-hacking-methodology",
- "path": "skills/ethical-hacking-methodology",
+ "path": "skills\\ethical-hacking-methodology",
"category": "uncategorized",
"name": "ethical-hacking-methodology",
"description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ...",
@@ -3592,7 +3673,7 @@
},
{
"id": "evaluation",
- "path": "skills/evaluation",
+ "path": "skills\\evaluation",
"category": "uncategorized",
"name": "evaluation",
"description": "Build evaluation frameworks for agent systems",
@@ -3601,7 +3682,7 @@
},
{
"id": "event-sourcing-architect",
- "path": "skills/event-sourcing-architect",
+ "path": "skills\\event-sourcing-architect",
"category": "uncategorized",
"name": "event-sourcing-architect",
"description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...",
@@ -3610,7 +3691,7 @@
},
{
"id": "event-store-design",
- "path": "skills/event-store-design",
+ "path": "skills\\event-store-design",
"category": "uncategorized",
"name": "event-store-design",
"description": "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.",
@@ -3619,7 +3700,7 @@
},
{
"id": "exa-search",
- "path": "skills/exa-search",
+ "path": "skills\\exa-search",
"category": "uncategorized",
"name": "exa-search",
"description": "Semantic search, similar content discovery, and structured research using Exa API",
@@ -3628,7 +3709,7 @@
},
{
"id": "executing-plans",
- "path": "skills/executing-plans",
+ "path": "skills\\executing-plans",
"category": "uncategorized",
"name": "executing-plans",
"description": "Use when you have a written implementation plan to execute in a separate session with review checkpoints",
@@ -3637,7 +3718,7 @@
},
{
"id": "expo-deployment",
- "path": "skills/expo-deployment",
+ "path": "skills\\expo-deployment",
"category": "uncategorized",
"name": "expo-deployment",
"description": "Deploy Expo apps to production",
@@ -3646,7 +3727,7 @@
},
{
"id": "fal-audio",
- "path": "skills/fal-audio",
+ "path": "skills\\fal-audio",
"category": "uncategorized",
"name": "fal-audio",
"description": "Text-to-speech and speech-to-text using fal.ai audio models",
@@ -3655,7 +3736,7 @@
},
{
"id": "fal-generate",
- "path": "skills/fal-generate",
+ "path": "skills\\fal-generate",
"category": "uncategorized",
"name": "fal-generate",
"description": "Generate images and videos using fal.ai AI models",
@@ -3664,7 +3745,7 @@
},
{
"id": "fal-image-edit",
- "path": "skills/fal-image-edit",
+ "path": "skills\\fal-image-edit",
"category": "uncategorized",
"name": "fal-image-edit",
"description": "AI-powered image editing with style transfer and object removal",
@@ -3673,7 +3754,7 @@
},
{
"id": "fal-platform",
- "path": "skills/fal-platform",
+ "path": "skills\\fal-platform",
"category": "uncategorized",
"name": "fal-platform",
"description": "Platform APIs for model management, pricing, and usage tracking",
@@ -3682,7 +3763,7 @@
},
{
"id": "fal-upscale",
- "path": "skills/fal-upscale",
+ "path": "skills\\fal-upscale",
"category": "uncategorized",
"name": "fal-upscale",
"description": "Upscale and enhance image and video resolution using AI",
@@ -3691,7 +3772,7 @@
},
{
"id": "fal-workflow",
- "path": "skills/fal-workflow",
+ "path": "skills\\fal-workflow",
"category": "uncategorized",
"name": "fal-workflow",
"description": "Generate workflow JSON files for chaining AI models",
@@ -3700,16 +3781,16 @@
},
{
"id": "fastapi-pro",
- "path": "skills/fastapi-pro",
+ "path": "skills\\fastapi-pro",
"category": "uncategorized",
- "name": "Fastapi Pro",
- "description": "- Working on fastapi pro tasks or workflows - Needing guidance, best practices, or checklists for fastapi pro",
+ "name": "fastapi-pro",
+ "description": "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and\nPydantic V2. Master microservices, WebSockets, and modern Python async\npatterns. Use PROACTIVELY for FastAPI development, async optimization, or API\narchitecture.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fastapi-router-py",
- "path": "skills/fastapi-router-py",
+ "path": "skills\\fastapi-router-py",
"category": "uncategorized",
"name": "fastapi-router-py",
"description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add...",
@@ -3718,7 +3799,7 @@
},
{
"id": "fastapi-templates",
- "path": "skills/fastapi-templates",
+ "path": "skills\\fastapi-templates",
"category": "uncategorized",
"name": "fastapi-templates",
"description": "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.",
@@ -3727,7 +3808,7 @@
},
{
"id": "ffuf-claude-skill",
- "path": "skills/ffuf-claude-skill",
+ "path": "skills\\ffuf-claude-skill",
"category": "uncategorized",
"name": "ffuf-claude-skill",
"description": "Web fuzzing with ffuf",
@@ -3736,7 +3817,7 @@
},
{
"id": "figma-automation",
- "path": "skills/figma-automation",
+ "path": "skills\\figma-automation",
"category": "uncategorized",
"name": "figma-automation",
"description": "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.",
@@ -3745,7 +3826,7 @@
},
{
"id": "file-organizer",
- "path": "skills/file-organizer",
+ "path": "skills\\file-organizer",
"category": "uncategorized",
"name": "file-organizer",
"description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo...",
@@ -3754,7 +3835,7 @@
},
{
"id": "file-path-traversal",
- "path": "skills/file-path-traversal",
+ "path": "skills\\file-path-traversal",
"category": "uncategorized",
"name": "file-path-traversal",
"description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu...",
@@ -3763,7 +3844,7 @@
},
{
"id": "file-uploads",
- "path": "skills/file-uploads",
+ "path": "skills\\file-uploads",
"category": "uncategorized",
"name": "file-uploads",
"description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...",
@@ -3772,7 +3853,7 @@
},
{
"id": "find-bugs",
- "path": "skills/find-bugs",
+ "path": "skills\\find-bugs",
"category": "uncategorized",
"name": "find-bugs",
"description": "Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.",
@@ -3781,7 +3862,7 @@
},
{
"id": "finishing-a-development-branch",
- "path": "skills/finishing-a-development-branch",
+ "path": "skills\\finishing-a-development-branch",
"category": "uncategorized",
"name": "finishing-a-development-branch",
"description": "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup",
@@ -3790,7 +3871,7 @@
},
{
"id": "firebase",
- "path": "skills/firebase",
+ "path": "skills\\firebase",
"category": "uncategorized",
"name": "firebase",
"description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r...",
@@ -3799,7 +3880,7 @@
},
{
"id": "firecrawl-scraper",
- "path": "skills/firecrawl-scraper",
+ "path": "skills\\firecrawl-scraper",
"category": "uncategorized",
"name": "firecrawl-scraper",
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API",
@@ -3808,16 +3889,16 @@
},
{
"id": "firmware-analyst",
- "path": "skills/firmware-analyst",
+ "path": "skills\\firmware-analyst",
"category": "uncategorized",
- "name": "Firmware Analyst",
- "description": "wget http://vendor.com/firmware/update.bin",
+ "name": "firmware-analyst",
+ "description": "Expert firmware analyst specializing in embedded systems, IoT\nsecurity, and hardware reverse engineering. Masters firmware extraction,\nanalysis, and vulnerability research for routers, IoT devices, automotive\nsystems, and industrial controllers. Use PROACTIVELY for firmware security\naudits, IoT penetration testing, or embedded systems research.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fix-review",
- "path": "skills/fix-review",
+ "path": "skills\\fix-review",
"category": "uncategorized",
"name": "fix-review",
"description": "Verify fix commits address audit findings without new bugs",
@@ -3826,25 +3907,25 @@
},
{
"id": "flutter-expert",
- "path": "skills/flutter-expert",
+ "path": "skills\\flutter-expert",
"category": "uncategorized",
- "name": "Flutter Expert",
- "description": "- Working on flutter expert tasks or workflows - Needing guidance, best practices, or checklists for flutter expert",
+ "name": "flutter-expert",
+ "description": "Master Flutter development with Dart 3, advanced widgets, and\nmulti-platform deployment. Handles state management, animations, testing, and\nperformance optimization for mobile, web, desktop, and embedded platforms. Use\nPROACTIVELY for Flutter architecture, UI implementation, or cross-platform\nfeatures.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "form-cro",
- "path": "skills/form-cro",
+ "path": "skills\\form-cro",
"category": "uncategorized",
- "name": "Form Cro",
- "description": "You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**.",
+ "name": "form-cro",
+ "description": "Optimize any form that is NOT signup or account registration \u2014 including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "fp-ts-errors",
- "path": "skills/fp-ts-errors",
+ "path": "skills\\fp-ts-errors",
"category": "uncategorized",
"name": "fp-ts-errors",
"description": "Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.",
@@ -3853,7 +3934,7 @@
},
{
"id": "fp-ts-pragmatic",
- "path": "skills/fp-ts-pragmatic",
+ "path": "skills\\fp-ts-pragmatic",
"category": "uncategorized",
"name": "fp-ts-pragmatic",
"description": "A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.",
@@ -3862,7 +3943,7 @@
},
{
"id": "fp-ts-react",
- "path": "skills/fp-ts-react",
+ "path": "skills\\fp-ts-react",
"category": "uncategorized",
"name": "fp-ts-react",
"description": "Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.",
@@ -3871,7 +3952,7 @@
},
{
"id": "framework-migration-code-migrate",
- "path": "skills/framework-migration-code-migrate",
+ "path": "skills\\framework-migration-code-migrate",
"category": "uncategorized",
"name": "framework-migration-code-migrate",
"description": "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and",
@@ -3880,7 +3961,7 @@
},
{
"id": "framework-migration-deps-upgrade",
- "path": "skills/framework-migration-deps-upgrade",
+ "path": "skills\\framework-migration-deps-upgrade",
"category": "uncategorized",
"name": "framework-migration-deps-upgrade",
"description": "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa",
@@ -3889,7 +3970,7 @@
},
{
"id": "framework-migration-legacy-modernize",
- "path": "skills/framework-migration-legacy-modernize",
+ "path": "skills\\framework-migration-legacy-modernize",
"category": "uncategorized",
"name": "framework-migration-legacy-modernize",
"description": "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex",
@@ -3898,7 +3979,7 @@
},
{
"id": "free-tool-strategy",
- "path": "skills/free-tool-strategy",
+ "path": "skills\\free-tool-strategy",
"category": "uncategorized",
"name": "free-tool-strategy",
"description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar...",
@@ -3907,7 +3988,7 @@
},
{
"id": "freshdesk-automation",
- "path": "skills/freshdesk-automation",
+ "path": "skills\\freshdesk-automation",
"category": "uncategorized",
"name": "freshdesk-automation",
"description": "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -3916,34 +3997,16 @@
},
{
"id": "freshservice-automation",
- "path": "skills/freshservice-automation",
+ "path": "skills\\freshservice-automation",
"category": "uncategorized",
"name": "freshservice-automation",
"description": "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "frontend-developer",
- "path": "skills/frontend-developer",
- "category": "uncategorized",
- "name": "Frontend Developer",
- "description": "You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "frontend-security-coder",
- "path": "skills/frontend-security-coder",
- "category": "uncategorized",
- "name": "Frontend Security Coder",
- "description": "- Working on frontend security coder tasks or workflows - Needing guidance, best practices, or checklists for frontend security coder",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "frontend-design",
- "path": "skills/frontend-design",
+ "path": "skills\\frontend-design",
"category": "uncategorized",
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...",
@@ -3952,16 +4015,25 @@
},
{
"id": "frontend-dev-guidelines",
- "path": "skills/frontend-dev-guidelines",
+ "path": "skills\\frontend-dev-guidelines",
"category": "uncategorized",
"name": "frontend-dev-guidelines",
"description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "frontend-developer",
+ "path": "skills\\frontend-developer",
+ "category": "uncategorized",
+ "name": "frontend-developer",
+ "description": "Build React components, implement responsive layouts, and handle\nclient-side state management. Masters React 19, Next.js 15, and modern\nfrontend architecture. Optimizes performance and ensures accessibility. Use\nPROACTIVELY when creating UI components or fixing frontend issues.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "frontend-mobile-development-component-scaffold",
- "path": "skills/frontend-mobile-development-component-scaffold",
+ "path": "skills\\frontend-mobile-development-component-scaffold",
"category": "uncategorized",
"name": "frontend-mobile-development-component-scaffold",
"description": "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s",
@@ -3970,16 +4042,25 @@
},
{
"id": "frontend-mobile-security-xss-scan",
- "path": "skills/frontend-mobile-security-xss-scan",
+ "path": "skills\\frontend-mobile-security-xss-scan",
"category": "uncategorized",
"name": "frontend-mobile-security-xss-scan",
"description": "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "frontend-security-coder",
+ "path": "skills\\frontend-security-coder",
+ "category": "uncategorized",
+ "name": "frontend-security-coder",
+ "description": "Expert in secure frontend coding practices specializing in XSS\nprevention, output sanitization, and client-side security patterns. Use\nPROACTIVELY for frontend security implementations or client-side security code\nreviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "frontend-slides",
- "path": "skills/frontend-slides",
+ "path": "skills\\frontend-slides",
"category": "uncategorized",
"name": "frontend-slides",
"description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a...",
@@ -3988,7 +4069,7 @@
},
{
"id": "frontend-ui-dark-ts",
- "path": "skills/frontend-ui-dark-ts",
+ "path": "skills\\frontend-ui-dark-ts",
"category": "uncategorized",
"name": "frontend-ui-dark-ts",
"description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces...",
@@ -3997,7 +4078,7 @@
},
{
"id": "full-stack-orchestration-full-stack-feature",
- "path": "skills/full-stack-orchestration-full-stack-feature",
+ "path": "skills\\full-stack-orchestration-full-stack-feature",
"category": "uncategorized",
"name": "full-stack-orchestration-full-stack-feature",
"description": "Use when working with full stack orchestration full stack feature",
@@ -4006,7 +4087,7 @@
},
{
"id": "game-art",
- "path": "skills/game-development/game-art",
+ "path": "skills\\game-development\\game-art",
"category": "game-development",
"name": "game-art",
"description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
@@ -4015,7 +4096,7 @@
},
{
"id": "game-audio",
- "path": "skills/game-development/game-audio",
+ "path": "skills\\game-development\\game-audio",
"category": "game-development",
"name": "game-audio",
"description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
@@ -4024,7 +4105,7 @@
},
{
"id": "game-design",
- "path": "skills/game-development/game-design",
+ "path": "skills\\game-development\\game-design",
"category": "game-development",
"name": "game-design",
"description": "Game design principles. GDD structure, balancing, player psychology, progression.",
@@ -4033,7 +4114,7 @@
},
{
"id": "game-development",
- "path": "skills/game-development",
+ "path": "skills\\game-development",
"category": "uncategorized",
"name": "game-development",
"description": "Game development orchestrator. Routes to platform-specific skills based on project needs.",
@@ -4042,7 +4123,7 @@
},
{
"id": "gcp-cloud-run",
- "path": "skills/gcp-cloud-run",
+ "path": "skills\\gcp-cloud-run",
"category": "uncategorized",
"name": "gcp-cloud-run",
"description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri...",
@@ -4051,7 +4132,7 @@
},
{
"id": "gdpr-data-handling",
- "path": "skills/gdpr-data-handling",
+ "path": "skills\\gdpr-data-handling",
"category": "uncategorized",
"name": "gdpr-data-handling",
"description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o...",
@@ -4060,7 +4141,7 @@
},
{
"id": "gemini-api-dev",
- "path": "skills/gemini-api-dev",
+ "path": "skills\\gemini-api-dev",
"category": "uncategorized",
"name": "gemini-api-dev",
"description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n...",
@@ -4069,7 +4150,7 @@
},
{
"id": "geo-fundamentals",
- "path": "skills/geo-fundamentals",
+ "path": "skills\\geo-fundamentals",
"category": "uncategorized",
"name": "geo-fundamentals",
"description": "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).",
@@ -4078,7 +4159,7 @@
},
{
"id": "git-advanced-workflows",
- "path": "skills/git-advanced-workflows",
+ "path": "skills\\git-advanced-workflows",
"category": "uncategorized",
"name": "git-advanced-workflows",
"description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co...",
@@ -4087,7 +4168,7 @@
},
{
"id": "git-pr-workflows-git-workflow",
- "path": "skills/git-pr-workflows-git-workflow",
+ "path": "skills\\git-pr-workflows-git-workflow",
"category": "uncategorized",
"name": "git-pr-workflows-git-workflow",
"description": "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g",
@@ -4096,7 +4177,7 @@
},
{
"id": "git-pr-workflows-onboard",
- "path": "skills/git-pr-workflows-onboard",
+ "path": "skills\\git-pr-workflows-onboard",
"category": "uncategorized",
"name": "git-pr-workflows-onboard",
"description": "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You",
@@ -4105,7 +4186,7 @@
},
{
"id": "git-pr-workflows-pr-enhance",
- "path": "skills/git-pr-workflows-pr-enhance",
+ "path": "skills\\git-pr-workflows-pr-enhance",
"category": "uncategorized",
"name": "git-pr-workflows-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu",
@@ -4114,7 +4195,7 @@
},
{
"id": "git-pushing",
- "path": "skills/git-pushing",
+ "path": "skills\\git-pushing",
"category": "uncategorized",
"name": "git-pushing",
"description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate...",
@@ -4123,7 +4204,7 @@
},
{
"id": "github-actions-templates",
- "path": "skills/github-actions-templates",
+ "path": "skills\\github-actions-templates",
"category": "uncategorized",
"name": "github-actions-templates",
"description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre...",
@@ -4132,7 +4213,7 @@
},
{
"id": "github-automation",
- "path": "skills/github-automation",
+ "path": "skills\\github-automation",
"category": "uncategorized",
"name": "github-automation",
"description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
@@ -4141,7 +4222,7 @@
},
{
"id": "github-issue-creator",
- "path": "skills/github-issue-creator",
+ "path": "skills\\github-issue-creator",
"category": "uncategorized",
"name": "github-issue-creator",
"description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...",
@@ -4150,7 +4231,7 @@
},
{
"id": "github-workflow-automation",
- "path": "skills/github-workflow-automation",
+ "path": "skills\\github-workflow-automation",
"category": "uncategorized",
"name": "github-workflow-automation",
"description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati...",
@@ -4159,7 +4240,7 @@
},
{
"id": "gitlab-automation",
- "path": "skills/gitlab-automation",
+ "path": "skills\\gitlab-automation",
"category": "uncategorized",
"name": "gitlab-automation",
"description": "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -4168,7 +4249,7 @@
},
{
"id": "gitlab-ci-patterns",
- "path": "skills/gitlab-ci-patterns",
+ "path": "skills\\gitlab-ci-patterns",
"category": "uncategorized",
"name": "gitlab-ci-patterns",
"description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...",
@@ -4177,7 +4258,7 @@
},
{
"id": "gitops-workflow",
- "path": "skills/gitops-workflow",
+ "path": "skills\\gitops-workflow",
"category": "uncategorized",
"name": "gitops-workflow",
"description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo...",
@@ -4186,7 +4267,7 @@
},
{
"id": "gmail-automation",
- "path": "skills/gmail-automation",
+ "path": "skills\\gmail-automation",
"category": "uncategorized",
"name": "gmail-automation",
"description": "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.",
@@ -4195,7 +4276,7 @@
},
{
"id": "go-concurrency-patterns",
- "path": "skills/go-concurrency-patterns",
+ "path": "skills\\go-concurrency-patterns",
"category": "uncategorized",
"name": "go-concurrency-patterns",
"description": "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.",
@@ -4204,7 +4285,7 @@
},
{
"id": "go-playwright",
- "path": "skills/go-playwright",
+ "path": "skills\\go-playwright",
"category": "uncategorized",
"name": "go-playwright",
"description": "Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.",
@@ -4213,7 +4294,7 @@
},
{
"id": "go-rod-master",
- "path": "skills/go-rod-master",
+ "path": "skills\\go-rod-master",
"category": "uncategorized",
"name": "go-rod-master",
"description": "Comprehensive guide for browser automation and web scraping with go-rod (Chrome DevTools Protocol) including stealth anti-bot-detection patterns.",
@@ -4222,7 +4303,7 @@
},
{
"id": "godot-4-migration",
- "path": "skills/godot-4-migration",
+ "path": "skills\\godot-4-migration",
"category": "uncategorized",
"name": "godot-4-migration",
"description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
@@ -4231,7 +4312,7 @@
},
{
"id": "godot-gdscript-patterns",
- "path": "skills/godot-gdscript-patterns",
+ "path": "skills\\godot-gdscript-patterns",
"category": "uncategorized",
"name": "godot-gdscript-patterns",
"description": "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.",
@@ -4240,16 +4321,16 @@
},
{
"id": "golang-pro",
- "path": "skills/golang-pro",
+ "path": "skills\\golang-pro",
"category": "uncategorized",
- "name": "Golang Pro",
- "description": "You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.",
+ "name": "golang-pro",
+ "description": "Master Go 1.21+ with modern patterns, advanced concurrency,\nperformance optimization, and production-ready microservices. Expert in the\nlatest Go ecosystem including generics, workspaces, and cutting-edge\nframeworks. Use PROACTIVELY for Go development, architecture design, or\nperformance optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "google-analytics-automation",
- "path": "skills/google-analytics-automation",
+ "path": "skills\\google-analytics-automation",
"category": "uncategorized",
"name": "google-analytics-automation",
"description": "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.",
@@ -4258,7 +4339,7 @@
},
{
"id": "google-calendar-automation",
- "path": "skills/google-calendar-automation",
+ "path": "skills\\google-calendar-automation",
"category": "uncategorized",
"name": "google-calendar-automation",
"description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica...",
@@ -4267,7 +4348,7 @@
},
{
"id": "google-drive-automation",
- "path": "skills/google-drive-automation",
+ "path": "skills\\google-drive-automation",
"category": "uncategorized",
"name": "google-drive-automation",
"description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr...",
@@ -4276,7 +4357,7 @@
},
{
"id": "googlesheets-automation",
- "path": "skills/googlesheets-automation",
+ "path": "skills\\googlesheets-automation",
"category": "uncategorized",
"name": "googlesheets-automation",
"description": "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.",
@@ -4285,7 +4366,7 @@
},
{
"id": "grafana-dashboards",
- "path": "skills/grafana-dashboards",
+ "path": "skills\\grafana-dashboards",
"category": "uncategorized",
"name": "grafana-dashboards",
"description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ...",
@@ -4294,7 +4375,7 @@
},
{
"id": "graphql",
- "path": "skills/graphql",
+ "path": "skills\\graphql",
"category": "uncategorized",
"name": "graphql",
"description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...",
@@ -4303,16 +4384,25 @@
},
{
"id": "graphql-architect",
- "path": "skills/graphql-architect",
+ "path": "skills\\graphql-architect",
"category": "uncategorized",
- "name": "Graphql Architect",
- "description": "- Working on graphql architect tasks or workflows - Needing guidance, best practices, or checklists for graphql architect",
+ "name": "graphql-architect",
+ "description": "Master modern GraphQL with federation, performance optimization,\nand enterprise security. Build scalable schemas, implement advanced caching,\nand design real-time systems. Use PROACTIVELY for GraphQL architecture or\nperformance optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "grpc-golang",
+ "path": "skills\\grpc-golang",
+ "category": "uncategorized",
+ "name": "grpc-golang",
+ "description": "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.",
+ "risk": "safe",
+ "source": "self"
},
{
"id": "haskell-pro",
- "path": "skills/haskell-pro",
+ "path": "skills\\haskell-pro",
"category": "uncategorized",
"name": "haskell-pro",
"description": "Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.",
@@ -4321,7 +4411,7 @@
},
{
"id": "helm-chart-scaffolding",
- "path": "skills/helm-chart-scaffolding",
+ "path": "skills\\helm-chart-scaffolding",
"category": "uncategorized",
"name": "helm-chart-scaffolding",
"description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl...",
@@ -4330,7 +4420,7 @@
},
{
"id": "helpdesk-automation",
- "path": "skills/helpdesk-automation",
+ "path": "skills\\helpdesk-automation",
"category": "uncategorized",
"name": "helpdesk-automation",
"description": "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.",
@@ -4339,133 +4429,133 @@
},
{
"id": "hig-components-content",
- "path": "skills/hig-components-content",
+ "path": "skills\\hig-components-content",
"category": "uncategorized",
- "name": "Hig Components Content",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-content",
+ "description": "Apple Human Interface Guidelines for content display components. Use this skill when the user asks about \"charts component\", \"collection view\", \"image view\", \"web view\", \"color well\", \"image well\", \"activity view\", \"lockup\", \"data visualization\", \"content display\", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says \"how should I display charts\", \"what's the best way to show images\", \"should I use a web view\", \"how do I build a grid of items\", \"what component shows media\", or \"how do I present a share sheet\". Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-controls",
- "path": "skills/hig-components-controls",
+ "path": "skills\\hig-components-controls",
"category": "uncategorized",
- "name": "Hig Components Controls",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-controls",
+ "description": "Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says \"picker or segmented control,\" \"how should my form look,\" \"what keyboard type should I use,\" \"toggle vs checkbox,\" or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. Cross-references: hig-components-menus, hig-components-dialogs, hig-components-search.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-dialogs",
- "path": "skills/hig-components-dialogs",
+ "path": "skills\\hig-components-dialogs",
"category": "uncategorized",
- "name": "Hig Components Dialogs",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-dialogs",
+ "description": "Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says \"should I use an alert or a sheet,\" \"how do I show a confirmation dialog,\" \"when should I use a popover,\" \"my modals are annoying users,\" or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, destructive action confirmation, or overlay UI patterns. Cross-references: hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-layout",
- "path": "skills/hig-components-layout",
+ "path": "skills\\hig-components-layout",
"category": "uncategorized",
- "name": "Hig Components Layout",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-layout",
+ "description": "Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about \"sidebar\", \"split view\", \"tab bar\", \"tab view\", \"scroll view\", \"window design\", \"panel\", \"list view\", \"table view\", \"column view\", \"outline view\", \"navigation structure\", \"app layout\", \"boxes\", \"ornaments\", or organizing content hierarchically in Apple apps. Also use when the user says \"how should I organize my app\", \"what navigation pattern should I use\", \"my layout breaks on iPad\", \"how do I build a sidebar\", \"should I use tabs or a sidebar\", or \"my app doesn't adapt to different screen sizes\". Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-menus",
- "path": "skills/hig-components-menus",
+ "path": "skills\\hig-components-menus",
"category": "uncategorized",
- "name": "Hig Components Menus",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-menus",
+ "description": "Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure controls, and standard buttons. Use this skill when the user says \"how should my buttons look,\" \"what goes in the menu bar,\" \"should I use a context menu or action sheet,\" \"how do I design a toolbar,\" or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit menu, or any menu/button component layout and behavior. Cross-references: hig-components-search, hig-components-controls, hig-components-dialogs.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-search",
- "path": "skills/hig-components-search",
+ "path": "skills\\hig-components-search",
"category": "uncategorized",
- "name": "Hig Components Search",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-search",
+ "description": "Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill when the user says \"how should search work in my app,\" \"I need a breadcrumb,\" \"how do I paginate content,\" or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-status",
- "path": "skills/hig-components-status",
+ "path": "skills\\hig-components-status",
"category": "uncategorized",
- "name": "Hig Components Status",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-status",
+ "description": "Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: \"progress indicator\", \"progress bar\", \"loading spinner\", \"status bar\", \"activity ring\", \"progress display\", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says \"how do I show loading state,\" \"should I use a spinner or progress bar,\" \"what goes in the status bar,\" or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-components-system",
- "path": "skills/hig-components-system",
+ "path": "skills\\hig-components-system",
"category": "uncategorized",
- "name": "Hig Components System",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-components-system",
+ "description": "Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: \"widget design\", \"live activity\", \"notification design\", \"complication\", \"home screen quick action\", \"top shelf\", \"watch face\", \"app clip\", \"app shortcut\", \"system experience\". Also use when the user says \"how do I design a widget,\" \"what should my notification look like,\" \"how do Live Activities work,\" \"should I make an App Clip,\" or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-foundations",
- "path": "skills/hig-foundations",
+ "path": "skills\\hig-foundations",
"category": "uncategorized",
- "name": "Hig Foundations",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-foundations",
+ "description": "Apple Human Interface Guidelines design foundations. Use this skill when the user asks about \"HIG color\", \"Apple typography\", \"SF Symbols\", \"dark mode guidelines\", \"accessible design\", \"Apple design foundations\", \"app icon\", \"layout guidelines\", \"materials\", \"motion\", \"privacy\", \"right to left\", \"RTL\", \"inclusive design\", branding, images, spatial layout, or writing style. Also use when the user says \"my colors look wrong in dark mode\", \"what font should I use\", \"is my app accessible enough\", \"how do I support Dynamic Type\", \"what contrast ratio do I need\", \"how do I pick system colors\", or \"my icons don't match the system style\". Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction patterns, hig-components-layout for structural components, hig-components-content for display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-inputs",
- "path": "skills/hig-inputs",
+ "path": "skills\\hig-inputs",
"category": "uncategorized",
- "name": "Hig Inputs",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-inputs",
+ "description": "Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. Use when asked about: \"gesture design\", \"Apple Pencil\", \"keyboard shortcuts\", \"game controller\", \"pointer support\", \"mouse support\", \"trackpad\", \"Digital Crown\", \"eye tracking\", \"visionOS input\", \"focus system\", \"remote control\", \"gyroscope\", \"spatial interaction\". Also use when the user says \"what gestures should I support,\" \"how do I add keyboard shortcuts,\" \"how does input work on Apple TV,\" \"should I support Apple Pencil,\" or asks about input device handling. Cross-references: hig-components-status, hig-components-system, hig-technologies for VoiceOver and Siri.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-patterns",
- "path": "skills/hig-patterns",
+ "path": "skills\\hig-patterns",
"category": "uncategorized",
- "name": "Hig Patterns",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-patterns",
+ "description": "Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about \"onboarding flow\", \"user onboarding\", \"app launch\", \"loading state\", \"drag and drop\", \"search pattern\", \"settings design\", \"notifications\", \"modality\", \"multitasking\", \"feedback pattern\", \"haptics\", \"undo redo\", \"file management\", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says \"how should onboarding work\", \"my app takes too long to load\", \"should I use a modal here\", \"how do I handle errors\", \"when should I ask for permissions\", \"how to show progress\", or \"what's the right way to confirm a delete\". Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics, hig-components-layout for navigation, hig-components-content for data display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-platforms",
- "path": "skills/hig-platforms",
+ "path": "skills\\hig-platforms",
"category": "uncategorized",
- "name": "Hig Platforms",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-platforms",
+ "description": "Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about \"designing for iOS\", \"iPad app design\", \"macOS design\", \"tvOS\", \"visionOS\", \"watchOS\", \"Apple platform\", \"which platform\", platform differences, platform-specific conventions, or multi-platform app design. Also use when the user says \"should I design differently for iPad vs iPhone\", \"how does my app work on visionOS\", \"what's different about macOS apps\", \"porting my app to another platform\", \"universal app design\", or \"what input methods does this platform use\". Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns, hig-components-layout for navigation structures, hig-components-content for content display.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-project-context",
- "path": "skills/hig-project-context",
+ "path": "skills\\hig-project-context",
"category": "uncategorized",
- "name": "Hig Project Context",
- "description": "Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.",
+ "name": "hig-project-context",
+ "description": "Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says \"set up my project context,\" \"what platforms am I targeting,\" \"configure HIG settings,\" or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hig-technologies",
- "path": "skills/hig-technologies",
+ "path": "skills\\hig-technologies",
"category": "uncategorized",
- "name": "Hig Technologies",
- "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
+ "name": "hig-technologies",
+ "description": "Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: \"Siri integration\", \"Apple Pay\", \"HealthKit\", \"HomeKit\", \"ARKit\", \"augmented reality\", \"machine learning\", \"generative AI\", \"iCloud sync\", \"Sign in with Apple\", \"SharePlay\", \"CarPlay\", \"in-app purchase\", \"NFC\", \"VoiceOver\", \"Maps\", \"Mac Catalyst\". Also use when the user says \"how do I integrate Siri,\" \"what are the Apple Pay guidelines,\" \"how should my AR experience work,\" \"how do I use Sign in with Apple,\" or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hosted-agents-v2-py",
- "path": "skills/hosted-agents-v2-py",
+ "path": "skills\\hosted-agents-v2-py",
"category": "uncategorized",
"name": "hosted-agents-v2-py",
"description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.",
@@ -4474,16 +4564,16 @@
},
{
"id": "hr-pro",
- "path": "skills/hr-pro",
+ "path": "skills\\hr-pro",
"category": "uncategorized",
- "name": "Hr Pro",
- "description": "- Working on hr pro tasks or workflows - Needing guidance, best practices, or checklists for hr pro",
+ "name": "hr-pro",
+ "description": "Professional, ethical HR partner for hiring,\nonboarding/offboarding, PTO and leave, performance, compliant policies, and\nemployee relations. Ask for jurisdiction and company context before advising;\nproduce structured, bias-mitigated, lawful templates.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "html-injection-testing",
- "path": "skills/html-injection-testing",
+ "path": "skills\\html-injection-testing",
"category": "uncategorized",
"name": "html-injection-testing",
"description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten...",
@@ -4492,7 +4582,7 @@
},
{
"id": "hubspot-automation",
- "path": "skills/hubspot-automation",
+ "path": "skills\\hubspot-automation",
"category": "uncategorized",
"name": "hubspot-automation",
"description": "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.",
@@ -4501,7 +4591,7 @@
},
{
"id": "hubspot-integration",
- "path": "skills/hubspot-integration",
+ "path": "skills\\hubspot-integration",
"category": "uncategorized",
"name": "hubspot-integration",
"description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs...",
@@ -4510,7 +4600,7 @@
},
{
"id": "hugging-face-cli",
- "path": "skills/hugging-face-cli",
+ "path": "skills\\hugging-face-cli",
"category": "uncategorized",
"name": "hugging-face-cli",
"description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...",
@@ -4519,7 +4609,7 @@
},
{
"id": "hugging-face-jobs",
- "path": "skills/hugging-face-jobs",
+ "path": "skills\\hugging-face-jobs",
"category": "uncategorized",
"name": "hugging-face-jobs",
"description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok...",
@@ -4528,16 +4618,16 @@
},
{
"id": "hybrid-cloud-architect",
- "path": "skills/hybrid-cloud-architect",
+ "path": "skills\\hybrid-cloud-architect",
"category": "uncategorized",
- "name": "Hybrid Cloud Architect",
- "description": "- Working on hybrid cloud architect tasks or workflows - Needing guidance, best practices, or checklists for hybrid cloud architect",
+ "name": "hybrid-cloud-architect",
+ "description": "Expert hybrid cloud architect specializing in complex multi-cloud\nsolutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters\nhybrid connectivity, workload placement optimization, edge computing, and\ncross-cloud automation. Handles compliance, cost optimization, disaster\nrecovery, and migration strategies. Use PROACTIVELY for hybrid architecture,\nmulti-cloud strategy, or complex infrastructure integration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "hybrid-cloud-networking",
- "path": "skills/hybrid-cloud-networking",
+ "path": "skills\\hybrid-cloud-networking",
"category": "uncategorized",
"name": "hybrid-cloud-networking",
"description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ...",
@@ -4546,7 +4636,7 @@
},
{
"id": "hybrid-search-implementation",
- "path": "skills/hybrid-search-implementation",
+ "path": "skills\\hybrid-search-implementation",
"category": "uncategorized",
"name": "hybrid-search-implementation",
"description": "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.",
@@ -4555,7 +4645,7 @@
},
{
"id": "i18n-localization",
- "path": "skills/i18n-localization",
+ "path": "skills\\i18n-localization",
"category": "uncategorized",
"name": "i18n-localization",
"description": "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.",
@@ -4564,7 +4654,7 @@
},
{
"id": "idor-testing",
- "path": "skills/idor-testing",
+ "path": "skills\\idor-testing",
"category": "uncategorized",
"name": "idor-testing",
"description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje...",
@@ -4573,16 +4663,16 @@
},
{
"id": "imagen",
- "path": "skills/imagen",
+ "path": "skills\\imagen",
"category": "uncategorized",
"name": "imagen",
- "description": "|",
+ "description": "This skill generates images using Google Gemini's image generation model (`gemini-3-pro-image-preview`). It enables seamless image creation during any Claude Code session - whether you're building frontend UIs, creating documentation, or need visual",
"risk": "safe",
"source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
},
{
"id": "impress",
- "path": "skills/libreoffice/impress",
+ "path": "skills\\libreoffice\\impress",
"category": "libreoffice",
"name": "impress",
"description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
@@ -4591,16 +4681,16 @@
},
{
"id": "incident-responder",
- "path": "skills/incident-responder",
+ "path": "skills\\incident-responder",
"category": "uncategorized",
- "name": "Incident Responder",
- "description": "- Working on incident responder tasks or workflows - Needing guidance, best practices, or checklists for incident responder",
+ "name": "incident-responder",
+ "description": "Expert SRE incident responder specializing in rapid problem\nresolution, modern observability, and comprehensive incident management.\nMasters incident command, blameless post-mortems, error budget management, and\nsystem reliability patterns. Handles critical outages, communication\nstrategies, and continuous improvement. Use IMMEDIATELY for production\nincidents or SRE practices.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "incident-response-incident-response",
- "path": "skills/incident-response-incident-response",
+ "path": "skills\\incident-response-incident-response",
"category": "uncategorized",
"name": "incident-response-incident-response",
"description": "Use when working with incident response incident response",
@@ -4609,7 +4699,7 @@
},
{
"id": "incident-response-smart-fix",
- "path": "skills/incident-response-smart-fix",
+ "path": "skills\\incident-response-smart-fix",
"category": "uncategorized",
"name": "incident-response-smart-fix",
"description": "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res",
@@ -4618,7 +4708,7 @@
},
{
"id": "incident-runbook-templates",
- "path": "skills/incident-runbook-templates",
+ "path": "skills\\incident-runbook-templates",
"category": "uncategorized",
"name": "incident-runbook-templates",
"description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...",
@@ -4627,7 +4717,7 @@
},
{
"id": "infinite-gratitude",
- "path": "skills/infinite-gratitude",
+ "path": "skills\\infinite-gratitude",
"category": "uncategorized",
"name": "infinite-gratitude",
"description": "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).",
@@ -4636,7 +4726,7 @@
},
{
"id": "inngest",
- "path": "skills/inngest",
+ "path": "skills\\inngest",
"category": "uncategorized",
"name": "inngest",
"description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...",
@@ -4645,7 +4735,7 @@
},
{
"id": "instagram-automation",
- "path": "skills/instagram-automation",
+ "path": "skills\\instagram-automation",
"category": "uncategorized",
"name": "instagram-automation",
"description": "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.",
@@ -4654,7 +4744,7 @@
},
{
"id": "interactive-portfolio",
- "path": "skills/interactive-portfolio",
+ "path": "skills\\interactive-portfolio",
"category": "uncategorized",
"name": "interactive-portfolio",
"description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,...",
@@ -4663,7 +4753,7 @@
},
{
"id": "intercom-automation",
- "path": "skills/intercom-automation",
+ "path": "skills\\intercom-automation",
"category": "uncategorized",
"name": "intercom-automation",
"description": "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.",
@@ -4672,7 +4762,7 @@
},
{
"id": "internal-comms-anthropic",
- "path": "skills/internal-comms-anthropic",
+ "path": "skills\\internal-comms-anthropic",
"category": "uncategorized",
"name": "internal-comms-anthropic",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
@@ -4681,7 +4771,7 @@
},
{
"id": "internal-comms-community",
- "path": "skills/internal-comms-community",
+ "path": "skills\\internal-comms-community",
"category": "uncategorized",
"name": "internal-comms-community",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
@@ -4689,17 +4779,26 @@
"source": "community"
},
{
- "id": "ios-developer",
- "path": "skills/ios-developer",
+ "id": "inventory-demand-planning",
+ "path": "skills\\inventory-demand-planning",
"category": "uncategorized",
- "name": "Ios Developer",
- "description": "- Working on ios developer tasks or workflows - Needing guidance, best practices, or checklists for ios developer",
+ "name": "inventory-demand-planning",
+ "description": "Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimising inventory levels.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "ios-developer",
+ "path": "skills\\ios-developer",
+ "category": "uncategorized",
+ "name": "ios-developer",
+ "description": "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,\nSwiftUI, UIKit integration, Core Data, networking, and App Store optimization.\nUse PROACTIVELY for iOS-specific features, App Store optimization, or native\niOS development.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "istio-traffic-management",
- "path": "skills/istio-traffic-management",
+ "path": "skills\\istio-traffic-management",
"category": "uncategorized",
"name": "istio-traffic-management",
"description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie...",
@@ -4708,7 +4807,7 @@
},
{
"id": "iterate-pr",
- "path": "skills/iterate-pr",
+ "path": "skills\\iterate-pr",
"category": "uncategorized",
"name": "iterate-pr",
"description": "Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.",
@@ -4717,34 +4816,34 @@
},
{
"id": "java-pro",
- "path": "skills/java-pro",
+ "path": "skills\\java-pro",
"category": "uncategorized",
- "name": "Java Pro",
- "description": "- Working on java pro tasks or workflows - Needing guidance, best practices, or checklists for java pro",
+ "name": "java-pro",
+ "description": "Master Java 21+ with modern features like virtual threads, pattern\nmatching, and Spring Boot 3.x. Expert in the latest Java ecosystem including\nGraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java\ndevelopment, microservices architecture, or performance optimization.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "javascript-pro",
- "path": "skills/javascript-pro",
- "category": "uncategorized",
- "name": "Javascript Pro",
- "description": "You are a JavaScript expert specializing in modern JS and async programming.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "javascript-mastery",
- "path": "skills/javascript-mastery",
+ "path": "skills\\javascript-mastery",
"category": "uncategorized",
"name": "javascript-mastery",
"description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "javascript-pro",
+ "path": "skills\\javascript-pro",
+ "category": "uncategorized",
+ "name": "javascript-pro",
+ "description": "Master modern JavaScript with ES6+, async patterns, and Node.js\nAPIs. Handles promises, event loops, and browser/Node compatibility. Use\nPROACTIVELY for JavaScript optimization, async debugging, or complex JS\npatterns.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "javascript-testing-patterns",
- "path": "skills/javascript-testing-patterns",
+ "path": "skills\\javascript-testing-patterns",
"category": "uncategorized",
"name": "javascript-testing-patterns",
"description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use...",
@@ -4753,7 +4852,7 @@
},
{
"id": "javascript-typescript-typescript-scaffold",
- "path": "skills/javascript-typescript-typescript-scaffold",
+ "path": "skills\\javascript-typescript-typescript-scaffold",
"category": "uncategorized",
"name": "javascript-typescript-typescript-scaffold",
"description": "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N",
@@ -4762,7 +4861,7 @@
},
{
"id": "jira-automation",
- "path": "skills/jira-automation",
+ "path": "skills\\jira-automation",
"category": "uncategorized",
"name": "jira-automation",
"description": "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.",
@@ -4771,16 +4870,16 @@
},
{
"id": "julia-pro",
- "path": "skills/julia-pro",
+ "path": "skills\\julia-pro",
"category": "uncategorized",
- "name": "Julia Pro",
- "description": "- Working on julia pro tasks or workflows - Needing guidance, best practices, or checklists for julia pro",
+ "name": "julia-pro",
+ "description": "Master Julia 1.10+ with modern features, performance optimization,\nmultiple dispatch, and production-ready practices. Expert in the Julia\necosystem including package management, scientific computing, and\nhigh-performance numerical code. Use PROACTIVELY for Julia development,\noptimization, or advanced Julia patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "k8s-manifest-generator",
- "path": "skills/k8s-manifest-generator",
+ "path": "skills\\k8s-manifest-generator",
"category": "uncategorized",
"name": "k8s-manifest-generator",
"description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat...",
@@ -4789,7 +4888,7 @@
},
{
"id": "k8s-security-policies",
- "path": "skills/k8s-security-policies",
+ "path": "skills\\k8s-security-policies",
"category": "uncategorized",
"name": "k8s-security-policies",
"description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...",
@@ -4798,7 +4897,7 @@
},
{
"id": "kaizen",
- "path": "skills/kaizen",
+ "path": "skills\\kaizen",
"category": "uncategorized",
"name": "kaizen",
"description": "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.",
@@ -4807,7 +4906,7 @@
},
{
"id": "klaviyo-automation",
- "path": "skills/klaviyo-automation",
+ "path": "skills\\klaviyo-automation",
"category": "uncategorized",
"name": "klaviyo-automation",
"description": "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.",
@@ -4816,7 +4915,7 @@
},
{
"id": "kotlin-coroutines-expert",
- "path": "skills/kotlin-coroutines-expert",
+ "path": "skills\\kotlin-coroutines-expert",
"category": "uncategorized",
"name": "kotlin-coroutines-expert",
"description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
@@ -4825,7 +4924,7 @@
},
{
"id": "kpi-dashboard-design",
- "path": "skills/kpi-dashboard-design",
+ "path": "skills\\kpi-dashboard-design",
"category": "uncategorized",
"name": "kpi-dashboard-design",
"description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...",
@@ -4834,16 +4933,16 @@
},
{
"id": "kubernetes-architect",
- "path": "skills/kubernetes-architect",
+ "path": "skills\\kubernetes-architect",
"category": "uncategorized",
- "name": "Kubernetes Architect",
- "description": "You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.",
+ "name": "kubernetes-architect",
+ "description": "Expert Kubernetes architect specializing in cloud-native\ninfrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise\ncontainer orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),\nprogressive delivery, multi-tenancy, and platform engineering. Handles\nsecurity, observability, cost optimization, and developer experience. Use\nPROACTIVELY for K8s architecture, GitOps implementation, or cloud-native\nplatform design.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "kubernetes-deployment",
- "path": "skills/kubernetes-deployment",
+ "path": "skills\\kubernetes-deployment",
"category": "uncategorized",
"name": "kubernetes-deployment",
"description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
@@ -4852,7 +4951,7 @@
},
{
"id": "langchain-architecture",
- "path": "skills/langchain-architecture",
+ "path": "skills\\langchain-architecture",
"category": "uncategorized",
"name": "langchain-architecture",
"description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...",
@@ -4861,7 +4960,7 @@
},
{
"id": "langfuse",
- "path": "skills/langfuse",
+ "path": "skills\\langfuse",
"category": "uncategorized",
"name": "langfuse",
"description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug...",
@@ -4870,7 +4969,7 @@
},
{
"id": "langgraph",
- "path": "skills/langgraph",
+ "path": "skills\\langgraph",
"category": "uncategorized",
"name": "langgraph",
"description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...",
@@ -4879,7 +4978,7 @@
},
{
"id": "laravel-expert",
- "path": "skills/laravel-expert",
+ "path": "skills\\laravel-expert",
"category": "uncategorized",
"name": "laravel-expert",
"description": "Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).",
@@ -4888,7 +4987,7 @@
},
{
"id": "laravel-security-audit",
- "path": "skills/laravel-security-audit",
+ "path": "skills\\laravel-security-audit",
"category": "uncategorized",
"name": "laravel-security-audit",
"description": "Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.",
@@ -4897,7 +4996,7 @@
},
{
"id": "last30days",
- "path": "skills/last30days",
+ "path": "skills\\last30days",
"category": "uncategorized",
"name": "last30days",
"description": "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.",
@@ -4906,7 +5005,7 @@
},
{
"id": "launch-strategy",
- "path": "skills/launch-strategy",
+ "path": "skills\\launch-strategy",
"category": "uncategorized",
"name": "launch-strategy",
"description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...",
@@ -4915,25 +5014,25 @@
},
{
"id": "legacy-modernizer",
- "path": "skills/legacy-modernizer",
+ "path": "skills\\legacy-modernizer",
"category": "uncategorized",
- "name": "Legacy Modernizer",
- "description": "- Working on legacy modernizer tasks or workflows - Needing guidance, best practices, or checklists for legacy modernizer",
+ "name": "legacy-modernizer",
+ "description": "Refactor legacy codebases, migrate outdated frameworks, and\nimplement gradual modernization. Handles technical debt, dependency updates,\nand backward compatibility. Use PROACTIVELY for legacy system updates,\nframework migrations, or technical debt reduction.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "legal-advisor",
- "path": "skills/legal-advisor",
+ "path": "skills\\legal-advisor",
"category": "uncategorized",
- "name": "Legal Advisor",
- "description": "- Working on legal advisor tasks or workflows - Needing guidance, best practices, or checklists for legal advisor",
+ "name": "legal-advisor",
+ "description": "Draft privacy policies, terms of service, disclaimers, and legal\nnotices. Creates GDPR-compliant texts, cookie policies, and data processing\nagreements. Use PROACTIVELY for legal documentation, compliance texts, or\nregulatory requirements.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "linear-automation",
- "path": "skills/linear-automation",
+ "path": "skills\\linear-automation",
"category": "uncategorized",
"name": "linear-automation",
"description": "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.",
@@ -4942,7 +5041,7 @@
},
{
"id": "linear-claude-skill",
- "path": "skills/linear-claude-skill",
+ "path": "skills\\linear-claude-skill",
"category": "uncategorized",
"name": "linear-claude-skill",
"description": "Manage Linear issues, projects, and teams",
@@ -4951,16 +5050,25 @@
},
{
"id": "linkedin-automation",
- "path": "skills/linkedin-automation",
+ "path": "skills\\linkedin-automation",
"category": "uncategorized",
"name": "linkedin-automation",
"description": "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "linkedin-cli",
+ "path": "skills\\linkedin-cli",
+ "category": "uncategorized",
+ "name": "linkedin-cli",
+ "description": "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.",
+ "risk": "safe",
+ "source": "community"
+ },
{
"id": "linkerd-patterns",
- "path": "skills/linkerd-patterns",
+ "path": "skills\\linkerd-patterns",
"category": "uncategorized",
"name": "linkerd-patterns",
"description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ...",
@@ -4969,7 +5077,7 @@
},
{
"id": "lint-and-validate",
- "path": "skills/lint-and-validate",
+ "path": "skills\\lint-and-validate",
"category": "uncategorized",
"name": "lint-and-validate",
"description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v...",
@@ -4978,7 +5086,7 @@
},
{
"id": "linux-privilege-escalation",
- "path": "skills/linux-privilege-escalation",
+ "path": "skills\\linux-privilege-escalation",
"category": "uncategorized",
"name": "linux-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex...",
@@ -4987,7 +5095,7 @@
},
{
"id": "linux-shell-scripting",
- "path": "skills/linux-shell-scripting",
+ "path": "skills\\linux-shell-scripting",
"category": "uncategorized",
"name": "linux-shell-scripting",
"description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she...",
@@ -4996,7 +5104,7 @@
},
{
"id": "linux-troubleshooting",
- "path": "skills/linux-troubleshooting",
+ "path": "skills\\linux-troubleshooting",
"category": "uncategorized",
"name": "linux-troubleshooting",
"description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
@@ -5005,7 +5113,7 @@
},
{
"id": "llm-app-patterns",
- "path": "skills/llm-app-patterns",
+ "path": "skills\\llm-app-patterns",
"category": "uncategorized",
"name": "llm-app-patterns",
"description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin...",
@@ -5014,7 +5122,7 @@
},
{
"id": "llm-application-dev-ai-assistant",
- "path": "skills/llm-application-dev-ai-assistant",
+ "path": "skills\\llm-application-dev-ai-assistant",
"category": "uncategorized",
"name": "llm-application-dev-ai-assistant",
"description": "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur",
@@ -5023,7 +5131,7 @@
},
{
"id": "llm-application-dev-langchain-agent",
- "path": "skills/llm-application-dev-langchain-agent",
+ "path": "skills\\llm-application-dev-langchain-agent",
"category": "uncategorized",
"name": "llm-application-dev-langchain-agent",
"description": "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.",
@@ -5032,7 +5140,7 @@
},
{
"id": "llm-application-dev-prompt-optimize",
- "path": "skills/llm-application-dev-prompt-optimize",
+ "path": "skills\\llm-application-dev-prompt-optimize",
"category": "uncategorized",
"name": "llm-application-dev-prompt-optimize",
"description": "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati",
@@ -5041,16 +5149,25 @@
},
{
"id": "llm-evaluation",
- "path": "skills/llm-evaluation",
+ "path": "skills\\llm-evaluation",
"category": "uncategorized",
"name": "llm-evaluation",
"description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "logistics-exception-management",
+ "path": "skills\\logistics-exception-management",
+ "category": "uncategorized",
+ "name": "logistics-exception-management",
+ "description": "Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviours, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
{
"id": "loki-mode",
- "path": "skills/loki-mode",
+ "path": "skills\\loki-mode",
"category": "uncategorized",
"name": "loki-mode",
"description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...",
@@ -5059,34 +5176,34 @@
},
{
"id": "m365-agents-dotnet",
- "path": "skills/m365-agents-dotnet",
+ "path": "skills\\m365-agents-dotnet",
"category": "uncategorized",
- "name": "M365 Agents Dotnet",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft.Agents SDK with ASP.NET Core hosting, agent routing, and MSAL-based authentication.",
+ "name": "m365-agents-dotnet",
+ "description": "Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"Microsoft.Agents\", \"AddAgentApplicationOptions\", \"AgentApplication\", \"AddAgentAspNetAuthentication\", \"Copilot Studio client\", \"IAgentHttpAdapter\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "m365-agents-py",
- "path": "skills/m365-agents-py",
+ "path": "skills\\m365-agents-py",
"category": "uncategorized",
- "name": "M365 Agents Py",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft Agents SDK with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based authentication.",
+ "name": "m365-agents-py",
+ "description": "Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"microsoft_agents\", \"AgentApplication\", \"start_agent_process\", \"TurnContext\", \"Copilot Studio client\", \"CloudAdapter\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "m365-agents-ts",
- "path": "skills/m365-agents-ts",
+ "path": "skills\\m365-agents-ts",
"category": "uncategorized",
- "name": "M365 Agents Ts",
- "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft 365 Agents SDK with Express hosting, AgentApplication routing, streaming responses, and Copilot Studio client integrations.",
+ "name": "m365-agents-ts",
+ "description": "Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: \"Microsoft 365 Agents SDK\", \"@microsoft/agents-hosting\", \"AgentApplication\", \"startServer\", \"streamingResponse\", \"Copilot Studio client\", \"@microsoft/agents-copilotstudio-client\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "machine-learning-ops-ml-pipeline",
- "path": "skills/machine-learning-ops-ml-pipeline",
+ "path": "skills\\machine-learning-ops-ml-pipeline",
"category": "uncategorized",
"name": "machine-learning-ops-ml-pipeline",
"description": "Design and implement a complete ML pipeline for: $ARGUMENTS",
@@ -5095,7 +5212,7 @@
},
{
"id": "mailchimp-automation",
- "path": "skills/mailchimp-automation",
+ "path": "skills\\mailchimp-automation",
"category": "uncategorized",
"name": "mailchimp-automation",
"description": "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5104,7 +5221,7 @@
},
{
"id": "make-automation",
- "path": "skills/make-automation",
+ "path": "skills\\make-automation",
"category": "uncategorized",
"name": "make-automation",
"description": "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.",
@@ -5113,7 +5230,7 @@
},
{
"id": "makepad-skills",
- "path": "skills/makepad-skills",
+ "path": "skills\\makepad-skills",
"category": "uncategorized",
"name": "makepad-skills",
"description": "Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.",
@@ -5122,16 +5239,16 @@
},
{
"id": "malware-analyst",
- "path": "skills/malware-analyst",
+ "path": "skills\\malware-analyst",
"category": "uncategorized",
- "name": "Malware Analyst",
- "description": "file sample.exe sha256sum sample.exe",
+ "name": "malware-analyst",
+ "description": "Expert malware analyst specializing in defensive malware research,\nthreat intelligence, and incident response. Masters sandbox analysis,\nbehavioral analysis, and malware family identification. Handles static/dynamic\nanalysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,\nthreat hunting, incident response, or security research.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "manifest",
- "path": "skills/manifest",
+ "path": "skills\\manifest",
"category": "uncategorized",
"name": "manifest",
"description": "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.",
@@ -5140,16 +5257,16 @@
},
{
"id": "market-sizing-analysis",
- "path": "skills/market-sizing-analysis",
+ "path": "skills\\market-sizing-analysis",
"category": "uncategorized",
- "name": "Market Sizing Analysis",
- "description": "Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.",
+ "name": "market-sizing-analysis",
+ "description": "This skill should be used when the user asks to \\\\\\\"calculate TAM\\\\\\\",\n\"determine SAM\", \"estimate SOM\", \"size the market\", \"calculate market\nopportunity\", \"what's the total addressable market\", or requests market sizing\nanalysis for a startup or business opportunity.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "marketing-ideas",
- "path": "skills/marketing-ideas",
+ "path": "skills\\marketing-ideas",
"category": "uncategorized",
"name": "marketing-ideas",
"description": "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.",
@@ -5158,7 +5275,7 @@
},
{
"id": "marketing-psychology",
- "path": "skills/marketing-psychology",
+ "path": "skills\\marketing-psychology",
"category": "uncategorized",
"name": "marketing-psychology",
"description": "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.",
@@ -5167,7 +5284,7 @@
},
{
"id": "mcp-builder",
- "path": "skills/mcp-builder",
+ "path": "skills\\mcp-builder",
"category": "uncategorized",
"name": "mcp-builder",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
@@ -5176,7 +5293,7 @@
},
{
"id": "mcp-builder-ms",
- "path": "skills/mcp-builder-ms",
+ "path": "skills\\mcp-builder-ms",
"category": "uncategorized",
"name": "mcp-builder-ms",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
@@ -5185,7 +5302,7 @@
},
{
"id": "memory-forensics",
- "path": "skills/memory-forensics",
+ "path": "skills\\memory-forensics",
"category": "uncategorized",
"name": "memory-forensics",
"description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...",
@@ -5194,7 +5311,7 @@
},
{
"id": "memory-safety-patterns",
- "path": "skills/memory-safety-patterns",
+ "path": "skills\\memory-safety-patterns",
"category": "uncategorized",
"name": "memory-safety-patterns",
"description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory...",
@@ -5203,7 +5320,7 @@
},
{
"id": "memory-systems",
- "path": "skills/memory-systems",
+ "path": "skills\\memory-systems",
"category": "uncategorized",
"name": "memory-systems",
"description": "Design short-term, long-term, and graph-based memory architectures",
@@ -5212,16 +5329,16 @@
},
{
"id": "mermaid-expert",
- "path": "skills/mermaid-expert",
+ "path": "skills\\mermaid-expert",
"category": "uncategorized",
- "name": "Mermaid Expert",
- "description": "- Working on mermaid expert tasks or workflows - Needing guidance, best practices, or checklists for mermaid expert",
+ "name": "mermaid-expert",
+ "description": "Create Mermaid diagrams for flowcharts, sequences, ERDs, and\narchitectures. Masters syntax for all diagram types and styling. Use\nPROACTIVELY for visual documentation, system diagrams, or process flows.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "metasploit-framework",
- "path": "skills/metasploit-framework",
+ "path": "skills\\metasploit-framework",
"category": "uncategorized",
"name": "metasploit-framework",
"description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp...",
@@ -5230,7 +5347,7 @@
},
{
"id": "micro-saas-launcher",
- "path": "skills/micro-saas-launcher",
+ "path": "skills\\micro-saas-launcher",
"category": "uncategorized",
"name": "micro-saas-launcher",
"description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t...",
@@ -5239,7 +5356,7 @@
},
{
"id": "microservices-patterns",
- "path": "skills/microservices-patterns",
+ "path": "skills\\microservices-patterns",
"category": "uncategorized",
"name": "microservices-patterns",
"description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...",
@@ -5248,16 +5365,16 @@
},
{
"id": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
- "path": "skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet",
+ "path": "skills\\microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"category": "uncategorized",
- "name": "Microsoft Azure Webjobs Extensions Authentication Events Dotnet",
- "description": "Azure Functions extension for handling Microsoft Entra ID custom authentication events.",
+ "name": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
+ "description": "Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: \"Authentication Events\", \"WebJobsAuthenticationEventsTrigger\", \"OnTokenIssuanceStart\", \"OnAttributeCollectionStart\", \"custom claims\", \"token enrichment\", \"Entra custom extension\", \"authentication extension\".\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "microsoft-teams-automation",
- "path": "skills/microsoft-teams-automation",
+ "path": "skills\\microsoft-teams-automation",
"category": "uncategorized",
"name": "microsoft-teams-automation",
"description": "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.",
@@ -5266,16 +5383,16 @@
},
{
"id": "minecraft-bukkit-pro",
- "path": "skills/minecraft-bukkit-pro",
+ "path": "skills\\minecraft-bukkit-pro",
"category": "uncategorized",
- "name": "Minecraft Bukkit Pro",
- "description": "- Working on minecraft bukkit pro tasks or workflows - Needing guidance, best practices, or checklists for minecraft bukkit pro",
+ "name": "minecraft-bukkit-pro",
+ "description": "Master Minecraft server plugin development with Bukkit, Spigot, and\nPaper APIs. Specializes in event-driven architecture, command systems, world\nmanipulation, player management, and performance optimization. Use PROACTIVELY\nfor plugin architecture, gameplay mechanics, server-side features, or\ncross-version compatibility.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "miro-automation",
- "path": "skills/miro-automation",
+ "path": "skills\\miro-automation",
"category": "uncategorized",
"name": "miro-automation",
"description": "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.",
@@ -5284,7 +5401,7 @@
},
{
"id": "mixpanel-automation",
- "path": "skills/mixpanel-automation",
+ "path": "skills\\mixpanel-automation",
"category": "uncategorized",
"name": "mixpanel-automation",
"description": "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.",
@@ -5293,16 +5410,16 @@
},
{
"id": "ml-engineer",
- "path": "skills/ml-engineer",
+ "path": "skills\\ml-engineer",
"category": "uncategorized",
- "name": "Ml Engineer",
- "description": "- Working on ml engineer tasks or workflows - Needing guidance, best practices, or checklists for ml engineer",
+ "name": "ml-engineer",
+ "description": "Build production ML systems with PyTorch 2.x, TensorFlow, and\nmodern ML frameworks. Implements model serving, feature engineering, A/B\ntesting, and monitoring. Use PROACTIVELY for ML model deployment, inference\noptimization, or production ML infrastructure.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ml-pipeline-workflow",
- "path": "skills/ml-pipeline-workflow",
+ "path": "skills\\ml-pipeline-workflow",
"category": "uncategorized",
"name": "ml-pipeline-workflow",
"description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod...",
@@ -5311,52 +5428,52 @@
},
{
"id": "mlops-engineer",
- "path": "skills/mlops-engineer",
+ "path": "skills\\mlops-engineer",
"category": "uncategorized",
- "name": "Mlops Engineer",
- "description": "- Working on mlops engineer tasks or workflows - Needing guidance, best practices, or checklists for mlops engineer",
+ "name": "mlops-engineer",
+ "description": "Build comprehensive ML pipelines, experiment tracking, and model\nregistries with MLflow, Kubeflow, and modern MLOps tools. Implements automated\ntraining, deployment, and monitoring across cloud platforms. Use PROACTIVELY\nfor ML infrastructure, experiment management, or pipeline automation.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-developer",
- "path": "skills/mobile-developer",
- "category": "uncategorized",
- "name": "Mobile Developer",
- "description": "- Working on mobile developer tasks or workflows - Needing guidance, best practices, or checklists for mobile developer",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "mobile-security-coder",
- "path": "skills/mobile-security-coder",
- "category": "uncategorized",
- "name": "Mobile Security Coder",
- "description": "- Working on mobile security coder tasks or workflows - Needing guidance, best practices, or checklists for mobile security coder",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "mobile-design",
- "path": "skills/mobile-design",
+ "path": "skills\\mobile-design",
"category": "uncategorized",
"name": "mobile-design",
"description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "mobile-developer",
+ "path": "skills\\mobile-developer",
+ "category": "uncategorized",
+ "name": "mobile-developer",
+ "description": "Develop React Native, Flutter, or native mobile apps with modern\narchitecture patterns. Masters cross-platform development, native\nintegrations, offline sync, and app store optimization. Use PROACTIVELY for\nmobile features, cross-platform code, or app optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "mobile-games",
- "path": "skills/game-development/mobile-games",
+ "path": "skills\\game-development\\mobile-games",
"category": "game-development",
"name": "mobile-games",
"description": "Mobile game development principles. Touch input, battery, performance, app stores.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "mobile-security-coder",
+ "path": "skills\\mobile-security-coder",
+ "category": "uncategorized",
+ "name": "mobile-security-coder",
+ "description": "Expert in secure mobile coding practices specializing in input\nvalidation, WebView security, and mobile-specific security patterns. Use\nPROACTIVELY for mobile security implementations or mobile security code\nreviews.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "modern-javascript-patterns",
- "path": "skills/modern-javascript-patterns",
+ "path": "skills\\modern-javascript-patterns",
"category": "uncategorized",
"name": "modern-javascript-patterns",
"description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici...",
@@ -5365,7 +5482,7 @@
},
{
"id": "monday-automation",
- "path": "skills/monday-automation",
+ "path": "skills\\monday-automation",
"category": "uncategorized",
"name": "monday-automation",
"description": "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5374,7 +5491,7 @@
},
{
"id": "monorepo-architect",
- "path": "skills/monorepo-architect",
+ "path": "skills\\monorepo-architect",
"category": "uncategorized",
"name": "monorepo-architect",
"description": "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,",
@@ -5383,7 +5500,7 @@
},
{
"id": "monorepo-management",
- "path": "skills/monorepo-management",
+ "path": "skills\\monorepo-management",
"category": "uncategorized",
"name": "monorepo-management",
"description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor...",
@@ -5392,7 +5509,7 @@
},
{
"id": "moodle-external-api-development",
- "path": "skills/moodle-external-api-development",
+ "path": "skills\\moodle-external-api-development",
"category": "uncategorized",
"name": "moodle-external-api-development",
"description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...",
@@ -5401,7 +5518,7 @@
},
{
"id": "mtls-configuration",
- "path": "skills/mtls-configuration",
+ "path": "skills\\mtls-configuration",
"category": "uncategorized",
"name": "mtls-configuration",
"description": "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.",
@@ -5410,7 +5527,7 @@
},
{
"id": "multi-agent-brainstorming",
- "path": "skills/multi-agent-brainstorming",
+ "path": "skills\\multi-agent-brainstorming",
"category": "uncategorized",
"name": "multi-agent-brainstorming",
"description": "Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.",
@@ -5419,7 +5536,7 @@
},
{
"id": "multi-agent-patterns",
- "path": "skills/multi-agent-patterns",
+ "path": "skills\\multi-agent-patterns",
"category": "uncategorized",
"name": "multi-agent-patterns",
"description": "Master orchestrator, peer-to-peer, and hierarchical multi-agent architectures",
@@ -5428,7 +5545,7 @@
},
{
"id": "multi-cloud-architecture",
- "path": "skills/multi-cloud-architecture",
+ "path": "skills\\multi-cloud-architecture",
"category": "uncategorized",
"name": "multi-cloud-architecture",
"description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin...",
@@ -5437,7 +5554,7 @@
},
{
"id": "multi-platform-apps-multi-platform",
- "path": "skills/multi-platform-apps-multi-platform",
+ "path": "skills\\multi-platform-apps-multi-platform",
"category": "uncategorized",
"name": "multi-platform-apps-multi-platform",
"description": "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.",
@@ -5446,7 +5563,7 @@
},
{
"id": "multiplayer",
- "path": "skills/game-development/multiplayer",
+ "path": "skills\\game-development\\multiplayer",
"category": "game-development",
"name": "multiplayer",
"description": "Multiplayer game development principles. Architecture, networking, synchronization.",
@@ -5455,7 +5572,7 @@
},
{
"id": "n8n-code-python",
- "path": "skills/n8n-code-python",
+ "path": "skills\\n8n-code-python",
"category": "uncategorized",
"name": "n8n-code-python",
"description": "Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.",
@@ -5464,7 +5581,7 @@
},
{
"id": "n8n-mcp-tools-expert",
- "path": "skills/n8n-mcp-tools-expert",
+ "path": "skills\\n8n-mcp-tools-expert",
"category": "uncategorized",
"name": "n8n-mcp-tools-expert",
"description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele...",
@@ -5473,7 +5590,7 @@
},
{
"id": "n8n-node-configuration",
- "path": "skills/n8n-node-configuration",
+ "path": "skills\\n8n-node-configuration",
"category": "uncategorized",
"name": "n8n-node-configuration",
"description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo...",
@@ -5482,7 +5599,7 @@
},
{
"id": "nanobanana-ppt-skills",
- "path": "skills/nanobanana-ppt-skills",
+ "path": "skills\\nanobanana-ppt-skills",
"category": "uncategorized",
"name": "nanobanana-ppt-skills",
"description": "AI-powered PPT generation with document analysis and styled images",
@@ -5491,7 +5608,7 @@
},
{
"id": "neon-postgres",
- "path": "skills/neon-postgres",
+ "path": "skills\\neon-postgres",
"category": "uncategorized",
"name": "neon-postgres",
"description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres...",
@@ -5500,7 +5617,7 @@
},
{
"id": "nerdzao-elite",
- "path": "skills/nerdzao-elite",
+ "path": "skills\\nerdzao-elite",
"category": "uncategorized",
"name": "nerdzao-elite",
"description": "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.",
@@ -5509,7 +5626,7 @@
},
{
"id": "nerdzao-elite-gemini-high",
- "path": "skills/nerdzao-elite-gemini-high",
+ "path": "skills\\nerdzao-elite-gemini-high",
"category": "uncategorized",
"name": "nerdzao-elite-gemini-high",
"description": "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade m\u00e1xima e efici\u00eancia de tokens.",
@@ -5518,34 +5635,34 @@
},
{
"id": "nestjs-expert",
- "path": "skills/nestjs-expert",
+ "path": "skills\\nestjs-expert",
"category": "uncategorized",
"name": "nestjs-expert",
"description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "network-engineer",
- "path": "skills/network-engineer",
- "category": "uncategorized",
- "name": "Network Engineer",
- "description": "- Working on network engineer tasks or workflows - Needing guidance, best practices, or checklists for network engineer",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "network-101",
- "path": "skills/network-101",
+ "path": "skills\\network-101",
"category": "uncategorized",
"name": "network-101",
"description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "network-engineer",
+ "path": "skills\\network-engineer",
+ "category": "uncategorized",
+ "name": "network-engineer",
+ "description": "Expert network engineer specializing in modern cloud networking,\nsecurity architectures, and performance optimization. Masters multi-cloud\nconnectivity, service mesh, zero-trust networking, SSL/TLS, global load\nbalancing, and advanced troubleshooting. Handles CDN optimization, network\nautomation, and compliance. Use PROACTIVELY for network design, connectivity\nissues, or performance optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "nextjs-app-router-patterns",
- "path": "skills/nextjs-app-router-patterns",
+ "path": "skills\\nextjs-app-router-patterns",
"category": "uncategorized",
"name": "nextjs-app-router-patterns",
"description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...",
@@ -5554,7 +5671,7 @@
},
{
"id": "nextjs-best-practices",
- "path": "skills/nextjs-best-practices",
+ "path": "skills\\nextjs-best-practices",
"category": "uncategorized",
"name": "nextjs-best-practices",
"description": "Next.js App Router principles. Server Components, data fetching, routing patterns.",
@@ -5563,7 +5680,7 @@
},
{
"id": "nextjs-supabase-auth",
- "path": "skills/nextjs-supabase-auth",
+ "path": "skills\\nextjs-supabase-auth",
"category": "uncategorized",
"name": "nextjs-supabase-auth",
"description": "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.",
@@ -5572,7 +5689,7 @@
},
{
"id": "nft-standards",
- "path": "skills/nft-standards",
+ "path": "skills\\nft-standards",
"category": "uncategorized",
"name": "nft-standards",
"description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi...",
@@ -5581,7 +5698,7 @@
},
{
"id": "nodejs-backend-patterns",
- "path": "skills/nodejs-backend-patterns",
+ "path": "skills\\nodejs-backend-patterns",
"category": "uncategorized",
"name": "nodejs-backend-patterns",
"description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when...",
@@ -5590,7 +5707,7 @@
},
{
"id": "nodejs-best-practices",
- "path": "skills/nodejs-best-practices",
+ "path": "skills\\nodejs-best-practices",
"category": "uncategorized",
"name": "nodejs-best-practices",
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
@@ -5599,7 +5716,7 @@
},
{
"id": "nosql-expert",
- "path": "skills/nosql-expert",
+ "path": "skills\\nosql-expert",
"category": "uncategorized",
"name": "nosql-expert",
"description": "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.",
@@ -5608,7 +5725,7 @@
},
{
"id": "notebooklm",
- "path": "skills/notebooklm",
+ "path": "skills\\notebooklm",
"category": "uncategorized",
"name": "notebooklm",
"description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth....",
@@ -5617,7 +5734,7 @@
},
{
"id": "notion-automation",
- "path": "skills/notion-automation",
+ "path": "skills\\notion-automation",
"category": "uncategorized",
"name": "notion-automation",
"description": "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.",
@@ -5626,7 +5743,7 @@
},
{
"id": "notion-template-business",
- "path": "skills/notion-template-business",
+ "path": "skills\\notion-template-business",
"category": "uncategorized",
"name": "notion-template-business",
"description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market...",
@@ -5635,7 +5752,7 @@
},
{
"id": "nx-workspace-patterns",
- "path": "skills/nx-workspace-patterns",
+ "path": "skills\\nx-workspace-patterns",
"category": "uncategorized",
"name": "nx-workspace-patterns",
"description": "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.",
@@ -5644,16 +5761,16 @@
},
{
"id": "observability-engineer",
- "path": "skills/observability-engineer",
+ "path": "skills\\observability-engineer",
"category": "uncategorized",
- "name": "Observability Engineer",
- "description": "You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.",
+ "name": "observability-engineer",
+ "description": "Build production-ready monitoring, logging, and tracing systems.\nImplements comprehensive observability strategies, SLI/SLO management, and\nincident response workflows. Use PROACTIVELY for monitoring infrastructure,\nperformance optimization, or production reliability.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "observability-monitoring-monitor-setup",
- "path": "skills/observability-monitoring-monitor-setup",
+ "path": "skills\\observability-monitoring-monitor-setup",
"category": "uncategorized",
"name": "observability-monitoring-monitor-setup",
"description": "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da",
@@ -5662,7 +5779,7 @@
},
{
"id": "observability-monitoring-slo-implement",
- "path": "skills/observability-monitoring-slo-implement",
+ "path": "skills\\observability-monitoring-slo-implement",
"category": "uncategorized",
"name": "observability-monitoring-slo-implement",
"description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...",
@@ -5671,7 +5788,7 @@
},
{
"id": "observe-whatsapp",
- "path": "skills/observe-whatsapp",
+ "path": "skills\\observe-whatsapp",
"category": "uncategorized",
"name": "observe-whatsapp",
"description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f...",
@@ -5680,7 +5797,7 @@
},
{
"id": "obsidian-clipper-template-creator",
- "path": "skills/obsidian-clipper-template-creator",
+ "path": "skills\\obsidian-clipper-template-creator",
"category": "uncategorized",
"name": "obsidian-clipper-template-creator",
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.",
@@ -5689,7 +5806,7 @@
},
{
"id": "office-productivity",
- "path": "skills/office-productivity",
+ "path": "skills\\office-productivity",
"category": "uncategorized",
"name": "office-productivity",
"description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
@@ -5698,7 +5815,7 @@
},
{
"id": "on-call-handoff-patterns",
- "path": "skills/on-call-handoff-patterns",
+ "path": "skills\\on-call-handoff-patterns",
"category": "uncategorized",
"name": "on-call-handoff-patterns",
"description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro...",
@@ -5707,7 +5824,7 @@
},
{
"id": "onboarding-cro",
- "path": "skills/onboarding-cro",
+ "path": "skills\\onboarding-cro",
"category": "uncategorized",
"name": "onboarding-cro",
"description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u...",
@@ -5716,7 +5833,7 @@
},
{
"id": "one-drive-automation",
- "path": "skills/one-drive-automation",
+ "path": "skills\\one-drive-automation",
"category": "uncategorized",
"name": "one-drive-automation",
"description": "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5725,7 +5842,7 @@
},
{
"id": "openapi-spec-generation",
- "path": "skills/openapi-spec-generation",
+ "path": "skills\\openapi-spec-generation",
"category": "uncategorized",
"name": "openapi-spec-generation",
"description": "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.",
@@ -5734,7 +5851,7 @@
},
{
"id": "os-scripting",
- "path": "skills/os-scripting",
+ "path": "skills\\os-scripting",
"category": "uncategorized",
"name": "os-scripting",
"description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
@@ -5743,7 +5860,7 @@
},
{
"id": "oss-hunter",
- "path": "skills/oss-hunter",
+ "path": "skills\\oss-hunter",
"category": "uncategorized",
"name": "oss-hunter",
"description": "Automatically hunt for high-impact OSS contribution opportunities in trending repositories.",
@@ -5752,7 +5869,7 @@
},
{
"id": "outlook-automation",
- "path": "skills/outlook-automation",
+ "path": "skills\\outlook-automation",
"category": "uncategorized",
"name": "outlook-automation",
"description": "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.",
@@ -5761,7 +5878,7 @@
},
{
"id": "outlook-calendar-automation",
- "path": "skills/outlook-calendar-automation",
+ "path": "skills\\outlook-calendar-automation",
"category": "uncategorized",
"name": "outlook-calendar-automation",
"description": "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.",
@@ -5770,16 +5887,16 @@
},
{
"id": "page-cro",
- "path": "skills/page-cro",
+ "path": "skills\\page-cro",
"category": "uncategorized",
- "name": "Page Cro",
- "description": "You are an expert in **page-level conversion optimization**. Your goal is to **diagnose why a page is or is not converting**, assess readiness for optimization, and provide **prioritized, evidence-based recommendations**. You do **not** guarantee con",
+ "name": "page-cro",
+ "description": "Analyze and optimize individual pages for conversion performance. Use when the user wants to improve conversion rates, diagnose why a page is underperforming, or increase the effectiveness of marketing pages (homepage, landing pages, pricing, feature pages, or blog posts). This skill focuses on diagnosis, prioritization, and testable recommendations\u2014 not blind optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pagerduty-automation",
- "path": "skills/pagerduty-automation",
+ "path": "skills\\pagerduty-automation",
"category": "uncategorized",
"name": "pagerduty-automation",
"description": "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.",
@@ -5788,7 +5905,7 @@
},
{
"id": "paid-ads",
- "path": "skills/paid-ads",
+ "path": "skills\\paid-ads",
"category": "uncategorized",
"name": "paid-ads",
"description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '...",
@@ -5797,7 +5914,7 @@
},
{
"id": "parallel-agents",
- "path": "skills/parallel-agents",
+ "path": "skills\\parallel-agents",
"category": "uncategorized",
"name": "parallel-agents",
"description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
@@ -5806,16 +5923,16 @@
},
{
"id": "payment-integration",
- "path": "skills/payment-integration",
+ "path": "skills\\payment-integration",
"category": "uncategorized",
- "name": "Payment Integration",
- "description": "- Working on payment integration tasks or workflows - Needing guidance, best practices, or checklists for payment integration",
+ "name": "payment-integration",
+ "description": "Integrate Stripe, PayPal, and payment processors. Handles checkout\nflows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when\nimplementing payments, billing, or subscription features.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "paypal-integration",
- "path": "skills/paypal-integration",
+ "path": "skills\\paypal-integration",
"category": "uncategorized",
"name": "paypal-integration",
"description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com...",
@@ -5824,7 +5941,7 @@
},
{
"id": "paywall-upgrade-cro",
- "path": "skills/paywall-upgrade-cro",
+ "path": "skills\\paywall-upgrade-cro",
"category": "uncategorized",
"name": "paywall-upgrade-cro",
"description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,...",
@@ -5833,7 +5950,7 @@
},
{
"id": "pc-games",
- "path": "skills/game-development/pc-games",
+ "path": "skills\\game-development\\pc-games",
"category": "game-development",
"name": "pc-games",
"description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
@@ -5842,7 +5959,7 @@
},
{
"id": "pci-compliance",
- "path": "skills/pci-compliance",
+ "path": "skills\\pci-compliance",
"category": "uncategorized",
"name": "pci-compliance",
"description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ...",
@@ -5851,7 +5968,7 @@
},
{
"id": "pdf-official",
- "path": "skills/pdf-official",
+ "path": "skills\\pdf-official",
"category": "uncategorized",
"name": "pdf-official",
"description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall...",
@@ -5860,7 +5977,7 @@
},
{
"id": "pentest-checklist",
- "path": "skills/pentest-checklist",
+ "path": "skills\\pentest-checklist",
"category": "uncategorized",
"name": "pentest-checklist",
"description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll...",
@@ -5869,7 +5986,7 @@
},
{
"id": "pentest-commands",
- "path": "skills/pentest-commands",
+ "path": "skills\\pentest-commands",
"category": "uncategorized",
"name": "pentest-commands",
"description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ...",
@@ -5878,7 +5995,7 @@
},
{
"id": "performance-engineer",
- "path": "skills/performance-engineer",
+ "path": "skills\\performance-engineer",
"category": "uncategorized",
"name": "performance-engineer",
"description": "Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.",
@@ -5887,7 +6004,7 @@
},
{
"id": "performance-profiling",
- "path": "skills/performance-profiling",
+ "path": "skills\\performance-profiling",
"category": "uncategorized",
"name": "performance-profiling",
"description": "Performance profiling principles. Measurement, analysis, and optimization techniques.",
@@ -5896,7 +6013,7 @@
},
{
"id": "performance-testing-review-ai-review",
- "path": "skills/performance-testing-review-ai-review",
+ "path": "skills\\performance-testing-review-ai-review",
"category": "uncategorized",
"name": "performance-testing-review-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
@@ -5905,7 +6022,7 @@
},
{
"id": "performance-testing-review-multi-agent-review",
- "path": "skills/performance-testing-review-multi-agent-review",
+ "path": "skills\\performance-testing-review-multi-agent-review",
"category": "uncategorized",
"name": "performance-testing-review-multi-agent-review",
"description": "Use when working with performance testing review multi agent review",
@@ -5914,7 +6031,7 @@
},
{
"id": "personal-tool-builder",
- "path": "skills/personal-tool-builder",
+ "path": "skills\\personal-tool-builder",
"category": "uncategorized",
"name": "personal-tool-builder",
"description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i...",
@@ -5923,16 +6040,16 @@
},
{
"id": "php-pro",
- "path": "skills/php-pro",
+ "path": "skills\\php-pro",
"category": "uncategorized",
- "name": "Php Pro",
- "description": "- Working on php pro tasks or workflows - Needing guidance, best practices, or checklists for php pro",
+ "name": "php-pro",
+ "description": "Write idiomatic PHP code with generators, iterators, SPL data\nstructures, and modern OOP features. Use PROACTIVELY for high-performance PHP\napplications.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "pipedrive-automation",
- "path": "skills/pipedrive-automation",
+ "path": "skills\\pipedrive-automation",
"category": "uncategorized",
"name": "pipedrive-automation",
"description": "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -5941,7 +6058,7 @@
},
{
"id": "plaid-fintech",
- "path": "skills/plaid-fintech",
+ "path": "skills\\plaid-fintech",
"category": "uncategorized",
"name": "plaid-fintech",
"description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices...",
@@ -5950,7 +6067,7 @@
},
{
"id": "plan-writing",
- "path": "skills/plan-writing",
+ "path": "skills\\plan-writing",
"category": "uncategorized",
"name": "plan-writing",
"description": "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.",
@@ -5959,7 +6076,7 @@
},
{
"id": "planning-with-files",
- "path": "skills/planning-with-files",
+ "path": "skills\\planning-with-files",
"category": "uncategorized",
"name": "planning-with-files",
"description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin...",
@@ -5968,7 +6085,7 @@
},
{
"id": "playwright-skill",
- "path": "skills/playwright-skill",
+ "path": "skills\\playwright-skill",
"category": "uncategorized",
"name": "playwright-skill",
"description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...",
@@ -5977,7 +6094,7 @@
},
{
"id": "podcast-generation",
- "path": "skills/podcast-generation",
+ "path": "skills\\podcast-generation",
"category": "uncategorized",
"name": "podcast-generation",
"description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio...",
@@ -5986,7 +6103,7 @@
},
{
"id": "popup-cro",
- "path": "skills/popup-cro",
+ "path": "skills\\popup-cro",
"category": "uncategorized",
"name": "popup-cro",
"description": "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.",
@@ -5995,16 +6112,16 @@
},
{
"id": "posix-shell-pro",
- "path": "skills/posix-shell-pro",
+ "path": "skills\\posix-shell-pro",
"category": "uncategorized",
- "name": "Posix Shell Pro",
- "description": "- Working on posix shell pro tasks or workflows - Needing guidance, best practices, or checklists for posix shell pro",
+ "name": "posix-shell-pro",
+ "description": "Expert in strict POSIX sh scripting for maximum portability across\nUnix-like systems. Specializes in shell scripts that run on any\nPOSIX-compliant shell (dash, ash, sh, bash --posix).\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "postgres-best-practices",
- "path": "skills/postgres-best-practices",
+ "path": "skills\\postgres-best-practices",
"category": "uncategorized",
"name": "postgres-best-practices",
"description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
@@ -6013,7 +6130,7 @@
},
{
"id": "postgresql",
- "path": "skills/postgresql",
+ "path": "skills\\postgresql",
"category": "uncategorized",
"name": "postgresql",
"description": "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features",
@@ -6022,7 +6139,7 @@
},
{
"id": "postgresql-optimization",
- "path": "skills/postgresql-optimization",
+ "path": "skills\\postgresql-optimization",
"category": "uncategorized",
"name": "postgresql-optimization",
"description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
@@ -6031,7 +6148,7 @@
},
{
"id": "posthog-automation",
- "path": "skills/posthog-automation",
+ "path": "skills\\posthog-automation",
"category": "uncategorized",
"name": "posthog-automation",
"description": "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.",
@@ -6040,7 +6157,7 @@
},
{
"id": "postmark-automation",
- "path": "skills/postmark-automation",
+ "path": "skills\\postmark-automation",
"category": "uncategorized",
"name": "postmark-automation",
"description": "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.",
@@ -6049,7 +6166,7 @@
},
{
"id": "postmortem-writing",
- "path": "skills/postmortem-writing",
+ "path": "skills\\postmortem-writing",
"category": "uncategorized",
"name": "postmortem-writing",
"description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...",
@@ -6058,7 +6175,7 @@
},
{
"id": "powershell-windows",
- "path": "skills/powershell-windows",
+ "path": "skills\\powershell-windows",
"category": "uncategorized",
"name": "powershell-windows",
"description": "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.",
@@ -6067,7 +6184,7 @@
},
{
"id": "pptx-official",
- "path": "skills/pptx-official",
+ "path": "skills\\pptx-official",
"category": "uncategorized",
"name": "pptx-official",
"description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo...",
@@ -6076,7 +6193,7 @@
},
{
"id": "pricing-strategy",
- "path": "skills/pricing-strategy",
+ "path": "skills\\pricing-strategy",
"category": "uncategorized",
"name": "pricing-strategy",
"description": "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.",
@@ -6085,7 +6202,7 @@
},
{
"id": "prisma-expert",
- "path": "skills/prisma-expert",
+ "path": "skills\\prisma-expert",
"category": "uncategorized",
"name": "prisma-expert",
"description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re...",
@@ -6094,7 +6211,7 @@
},
{
"id": "privilege-escalation-methods",
- "path": "skills/privilege-escalation-methods",
+ "path": "skills\\privilege-escalation-methods",
"category": "uncategorized",
"name": "privilege-escalation-methods",
"description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K...",
@@ -6103,7 +6220,7 @@
},
{
"id": "product-manager-toolkit",
- "path": "skills/product-manager-toolkit",
+ "path": "skills\\product-manager-toolkit",
"category": "uncategorized",
"name": "product-manager-toolkit",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...",
@@ -6112,7 +6229,7 @@
},
{
"id": "production-code-audit",
- "path": "skills/production-code-audit",
+ "path": "skills\\production-code-audit",
"category": "uncategorized",
"name": "production-code-audit",
"description": "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations",
@@ -6120,17 +6237,26 @@
"source": "community"
},
{
- "id": "programmatic-seo",
- "path": "skills/programmatic-seo",
+ "id": "production-scheduling",
+ "path": "skills\\production-scheduling",
"category": "uncategorized",
- "name": "Programmatic Seo",
- "description": "---",
+ "name": "production-scheduling",
+ "description": "Codified expertise for production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimising changeovers, responding to disruptions, or balancing manufacturing lines.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "programmatic-seo",
+ "path": "skills\\programmatic-seo",
+ "category": "uncategorized",
+ "name": "programmatic-seo",
+ "description": "Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design\u2014not execution unless explicitly requested.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "projection-patterns",
- "path": "skills/projection-patterns",
+ "path": "skills\\projection-patterns",
"category": "uncategorized",
"name": "projection-patterns",
"description": "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.",
@@ -6139,7 +6265,7 @@
},
{
"id": "prometheus-configuration",
- "path": "skills/prometheus-configuration",
+ "path": "skills\\prometheus-configuration",
"category": "uncategorized",
"name": "prometheus-configuration",
"description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...",
@@ -6148,7 +6274,7 @@
},
{
"id": "prompt-caching",
- "path": "skills/prompt-caching",
+ "path": "skills\\prompt-caching",
"category": "uncategorized",
"name": "prompt-caching",
"description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm...",
@@ -6157,7 +6283,7 @@
},
{
"id": "prompt-engineer",
- "path": "skills/prompt-engineer",
+ "path": "skills\\prompt-engineer",
"category": "uncategorized",
"name": "prompt-engineer",
"description": "Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)",
@@ -6166,7 +6292,7 @@
},
{
"id": "prompt-engineering",
- "path": "skills/prompt-engineering",
+ "path": "skills\\prompt-engineering",
"category": "uncategorized",
"name": "prompt-engineering",
"description": "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.",
@@ -6175,7 +6301,7 @@
},
{
"id": "prompt-engineering-patterns",
- "path": "skills/prompt-engineering-patterns",
+ "path": "skills\\prompt-engineering-patterns",
"category": "uncategorized",
"name": "prompt-engineering-patterns",
"description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio...",
@@ -6184,7 +6310,7 @@
},
{
"id": "prompt-library",
- "path": "skills/prompt-library",
+ "path": "skills\\prompt-library",
"category": "uncategorized",
"name": "prompt-library",
"description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-...",
@@ -6193,7 +6319,7 @@
},
{
"id": "protocol-reverse-engineering",
- "path": "skills/protocol-reverse-engineering",
+ "path": "skills\\protocol-reverse-engineering",
"category": "uncategorized",
"name": "protocol-reverse-engineering",
"description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...",
@@ -6202,7 +6328,7 @@
},
{
"id": "pydantic-models-py",
- "path": "skills/pydantic-models-py",
+ "path": "skills\\pydantic-models-py",
"category": "uncategorized",
"name": "pydantic-models-py",
"description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ...",
@@ -6211,25 +6337,16 @@
},
{
"id": "pypict-skill",
- "path": "skills/pypict-skill",
+ "path": "skills\\pypict-skill",
"category": "uncategorized",
"name": "pypict-skill",
"description": "Pairwise test generation",
"risk": "safe",
"source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md"
},
- {
- "id": "python-pro",
- "path": "skills/python-pro",
- "category": "uncategorized",
- "name": "Python Pro",
- "description": "You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "python-development-python-scaffold",
- "path": "skills/python-development-python-scaffold",
+ "path": "skills\\python-development-python-scaffold",
"category": "uncategorized",
"name": "python-development-python-scaffold",
"description": "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint",
@@ -6238,7 +6355,7 @@
},
{
"id": "python-fastapi-development",
- "path": "skills/python-fastapi-development",
+ "path": "skills\\python-fastapi-development",
"category": "uncategorized",
"name": "python-fastapi-development",
"description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
@@ -6247,7 +6364,7 @@
},
{
"id": "python-packaging",
- "path": "skills/python-packaging",
+ "path": "skills\\python-packaging",
"category": "uncategorized",
"name": "python-packaging",
"description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ...",
@@ -6256,7 +6373,7 @@
},
{
"id": "python-patterns",
- "path": "skills/python-patterns",
+ "path": "skills\\python-patterns",
"category": "uncategorized",
"name": "python-patterns",
"description": "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.",
@@ -6265,16 +6382,25 @@
},
{
"id": "python-performance-optimization",
- "path": "skills/python-performance-optimization",
+ "path": "skills\\python-performance-optimization",
"category": "uncategorized",
"name": "python-performance-optimization",
"description": "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "python-pro",
+ "path": "skills\\python-pro",
+ "category": "uncategorized",
+ "name": "python-pro",
+ "description": "Master Python 3.12+ with modern features, async programming,\nperformance optimization, and production-ready practices. Expert in the latest\nPython ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY\nfor Python development, optimization, or advanced Python patterns.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "python-testing-patterns",
- "path": "skills/python-testing-patterns",
+ "path": "skills\\python-testing-patterns",
"category": "uncategorized",
"name": "python-testing-patterns",
"description": "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.",
@@ -6282,17 +6408,26 @@
"source": "community"
},
{
- "id": "quant-analyst",
- "path": "skills/quant-analyst",
+ "id": "quality-nonconformance",
+ "path": "skills\\quality-nonconformance",
"category": "uncategorized",
- "name": "Quant Analyst",
- "description": "- Working on quant analyst tasks or workflows - Needing guidance, best practices, or checklists for quant analyst",
+ "name": "quality-nonconformance",
+ "description": "Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "quant-analyst",
+ "path": "skills\\quant-analyst",
+ "category": "uncategorized",
+ "name": "quant-analyst",
+ "description": "Build financial models, backtest trading strategies, and analyze\nmarket data. Implements risk metrics, portfolio optimization, and statistical\narbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or\nrisk analysis.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "radix-ui-design-system",
- "path": "skills/radix-ui-design-system",
+ "path": "skills\\radix-ui-design-system",
"category": "uncategorized",
"name": "radix-ui-design-system",
"description": "Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.",
@@ -6301,7 +6436,7 @@
},
{
"id": "rag-engineer",
- "path": "skills/rag-engineer",
+ "path": "skills\\rag-engineer",
"category": "uncategorized",
"name": "rag-engineer",
"description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ...",
@@ -6310,7 +6445,7 @@
},
{
"id": "rag-implementation",
- "path": "skills/rag-implementation",
+ "path": "skills\\rag-implementation",
"category": "uncategorized",
"name": "rag-implementation",
"description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
@@ -6319,7 +6454,7 @@
},
{
"id": "react-best-practices",
- "path": "skills/react-best-practices",
+ "path": "skills\\react-best-practices",
"category": "uncategorized",
"name": "react-best-practices",
"description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat...",
@@ -6328,7 +6463,7 @@
},
{
"id": "react-flow-architect",
- "path": "skills/react-flow-architect",
+ "path": "skills\\react-flow-architect",
"category": "uncategorized",
"name": "react-flow-architect",
"description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or...",
@@ -6337,7 +6472,7 @@
},
{
"id": "react-flow-node-ts",
- "path": "skills/react-flow-node-ts",
+ "path": "skills\\react-flow-node-ts",
"category": "uncategorized",
"name": "react-flow-node-ts",
"description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no...",
@@ -6346,7 +6481,7 @@
},
{
"id": "react-modernization",
- "path": "skills/react-modernization",
+ "path": "skills\\react-modernization",
"category": "uncategorized",
"name": "react-modernization",
"description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...",
@@ -6355,7 +6490,7 @@
},
{
"id": "react-native-architecture",
- "path": "skills/react-native-architecture",
+ "path": "skills\\react-native-architecture",
"category": "uncategorized",
"name": "react-native-architecture",
"description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...",
@@ -6364,7 +6499,7 @@
},
{
"id": "react-nextjs-development",
- "path": "skills/react-nextjs-development",
+ "path": "skills\\react-nextjs-development",
"category": "uncategorized",
"name": "react-nextjs-development",
"description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
@@ -6373,7 +6508,7 @@
},
{
"id": "react-patterns",
- "path": "skills/react-patterns",
+ "path": "skills\\react-patterns",
"category": "uncategorized",
"name": "react-patterns",
"description": "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.",
@@ -6382,7 +6517,7 @@
},
{
"id": "react-state-management",
- "path": "skills/react-state-management",
+ "path": "skills\\react-state-management",
"category": "uncategorized",
"name": "react-state-management",
"description": "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.",
@@ -6391,7 +6526,7 @@
},
{
"id": "react-ui-patterns",
- "path": "skills/react-ui-patterns",
+ "path": "skills\\react-ui-patterns",
"category": "uncategorized",
"name": "react-ui-patterns",
"description": "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.",
@@ -6400,7 +6535,7 @@
},
{
"id": "readme",
- "path": "skills/readme",
+ "path": "skills\\readme",
"category": "uncategorized",
"name": "readme",
"description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...",
@@ -6409,7 +6544,7 @@
},
{
"id": "receiving-code-review",
- "path": "skills/receiving-code-review",
+ "path": "skills\\receiving-code-review",
"category": "uncategorized",
"name": "receiving-code-review",
"description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...",
@@ -6418,7 +6553,7 @@
},
{
"id": "red-team-tactics",
- "path": "skills/red-team-tactics",
+ "path": "skills\\red-team-tactics",
"category": "uncategorized",
"name": "red-team-tactics",
"description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
@@ -6427,7 +6562,7 @@
},
{
"id": "red-team-tools",
- "path": "skills/red-team-tools",
+ "path": "skills\\red-team-tools",
"category": "uncategorized",
"name": "red-team-tools",
"description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su...",
@@ -6436,7 +6571,7 @@
},
{
"id": "reddit-automation",
- "path": "skills/reddit-automation",
+ "path": "skills\\reddit-automation",
"category": "uncategorized",
"name": "reddit-automation",
"description": "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.",
@@ -6445,16 +6580,16 @@
},
{
"id": "reference-builder",
- "path": "skills/reference-builder",
+ "path": "skills\\reference-builder",
"category": "uncategorized",
- "name": "Reference Builder",
- "description": "- Working on reference builder tasks or workflows - Needing guidance, best practices, or checklists for reference builder",
+ "name": "reference-builder",
+ "description": "Creates exhaustive technical references and API documentation.\nGenerates comprehensive parameter listings, configuration guides, and\nsearchable reference materials. Use PROACTIVELY for API docs, configuration\nreferences, or complete technical specifications.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "referral-program",
- "path": "skills/referral-program",
+ "path": "skills\\referral-program",
"category": "uncategorized",
"name": "referral-program",
"description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of...",
@@ -6463,7 +6598,7 @@
},
{
"id": "remotion-best-practices",
- "path": "skills/remotion-best-practices",
+ "path": "skills\\remotion-best-practices",
"category": "uncategorized",
"name": "remotion-best-practices",
"description": "Best practices for Remotion - Video creation in React",
@@ -6472,7 +6607,7 @@
},
{
"id": "render-automation",
- "path": "skills/render-automation",
+ "path": "skills\\render-automation",
"category": "uncategorized",
"name": "render-automation",
"description": "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.",
@@ -6481,7 +6616,7 @@
},
{
"id": "requesting-code-review",
- "path": "skills/requesting-code-review",
+ "path": "skills\\requesting-code-review",
"category": "uncategorized",
"name": "requesting-code-review",
"description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements",
@@ -6490,7 +6625,7 @@
},
{
"id": "research-engineer",
- "path": "skills/research-engineer",
+ "path": "skills\\research-engineer",
"category": "uncategorized",
"name": "research-engineer",
"description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl...",
@@ -6498,26 +6633,35 @@
"source": "community"
},
{
- "id": "reverse-engineer",
- "path": "skills/reverse-engineer",
+ "id": "returns-reverse-logistics",
+ "path": "skills\\returns-reverse-logistics",
"category": "uncategorized",
- "name": "Reverse Engineer",
- "description": "- IDAPython (IDA Pro scripting) - Ghidra scripting (Java/Python via Jython) - r2pipe (radare2 Python API) - pwntools (CTF/exploitation toolkit) - capstone (disassembly framework) - keystone (assembly framework) - unicorn (CPU emulator framework) - an",
+ "name": "returns-reverse-logistics",
+ "description": "Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.\n",
+ "risk": "safe",
+ "source": "https://github.com/ai-evos/agent-skills"
+ },
+ {
+ "id": "reverse-engineer",
+ "path": "skills\\reverse-engineer",
+ "category": "uncategorized",
+ "name": "reverse-engineer",
+ "description": "Expert reverse engineer specializing in binary analysis,\ndisassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,\nradare2, x64dbg, and modern RE toolchains. Handles executable analysis,\nlibrary inspection, protocol extraction, and vulnerability research. Use\nPROACTIVELY for binary analysis, CTF challenges, security research, or\nunderstanding undocumented software.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "risk-manager",
- "path": "skills/risk-manager",
+ "path": "skills\\risk-manager",
"category": "uncategorized",
- "name": "Risk Manager",
- "description": "- Working on risk manager tasks or workflows - Needing guidance, best practices, or checklists for risk manager",
+ "name": "risk-manager",
+ "description": "Monitor portfolio risk, R-multiples, and position limits. Creates\nhedging strategies, calculates expectancy, and implements stop-losses. Use\nPROACTIVELY for risk assessment, trade tracking, or portfolio protection.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "risk-metrics-calculation",
- "path": "skills/risk-metrics-calculation",
+ "path": "skills\\risk-metrics-calculation",
"category": "uncategorized",
"name": "risk-metrics-calculation",
"description": "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.",
@@ -6526,34 +6670,34 @@
},
{
"id": "ruby-pro",
- "path": "skills/ruby-pro",
+ "path": "skills\\ruby-pro",
"category": "uncategorized",
- "name": "Ruby Pro",
- "description": "- Working on ruby pro tasks or workflows - Needing guidance, best practices, or checklists for ruby pro",
+ "name": "ruby-pro",
+ "description": "Write idiomatic Ruby code with metaprogramming, Rails patterns, and\nperformance optimization. Specializes in Ruby on Rails, gem development, and\ntesting frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or\ncomplex Ruby features.\n",
"risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "rust-pro",
- "path": "skills/rust-pro",
- "category": "uncategorized",
- "name": "Rust Pro",
- "description": "You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.",
- "risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "rust-async-patterns",
- "path": "skills/rust-async-patterns",
+ "path": "skills\\rust-async-patterns",
"category": "uncategorized",
"name": "rust-async-patterns",
"description": "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "rust-pro",
+ "path": "skills\\rust-pro",
+ "category": "uncategorized",
+ "name": "rust-pro",
+ "description": "Master Rust 1.75+ with modern async patterns, advanced type system\nfeatures, and production-ready systems programming. Expert in the latest Rust\necosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for\nRust development, performance optimization, or systems programming.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "saga-orchestration",
- "path": "skills/saga-orchestration",
+ "path": "skills\\saga-orchestration",
"category": "uncategorized",
"name": "saga-orchestration",
"description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running...",
@@ -6562,16 +6706,16 @@
},
{
"id": "sales-automator",
- "path": "skills/sales-automator",
+ "path": "skills\\sales-automator",
"category": "uncategorized",
- "name": "Sales Automator",
- "description": "- Working on sales automator tasks or workflows - Needing guidance, best practices, or checklists for sales automator",
+ "name": "sales-automator",
+ "description": "Draft cold emails, follow-ups, and proposal templates. Creates\npricing pages, case studies, and sales scripts. Use PROACTIVELY for sales\noutreach or lead nurturing.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "salesforce-automation",
- "path": "skills/salesforce-automation",
+ "path": "skills\\salesforce-automation",
"category": "uncategorized",
"name": "salesforce-automation",
"description": "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.",
@@ -6580,7 +6724,7 @@
},
{
"id": "salesforce-development",
- "path": "skills/salesforce-development",
+ "path": "skills\\salesforce-development",
"category": "uncategorized",
"name": "salesforce-development",
"description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ...",
@@ -6589,7 +6733,7 @@
},
{
"id": "sast-configuration",
- "path": "skills/sast-configuration",
+ "path": "skills\\sast-configuration",
"category": "uncategorized",
"name": "sast-configuration",
"description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut...",
@@ -6598,16 +6742,16 @@
},
{
"id": "scala-pro",
- "path": "skills/scala-pro",
+ "path": "skills\\scala-pro",
"category": "uncategorized",
- "name": "Scala Pro",
- "description": "- Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro",
+ "name": "scala-pro",
+ "description": "Master enterprise-grade Scala development with functional\nprogramming, distributed systems, and big data processing. Expert in Apache\nPekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use\nPROACTIVELY for Scala system design, performance optimization, or enterprise\nintegration.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "scanning-tools",
- "path": "skills/scanning-tools",
+ "path": "skills\\scanning-tools",
"category": "uncategorized",
"name": "scanning-tools",
"description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec...",
@@ -6616,16 +6760,16 @@
},
{
"id": "schema-markup",
- "path": "skills/schema-markup",
+ "path": "skills\\schema-markup",
"category": "uncategorized",
- "name": "Schema Markup",
- "description": "---",
+ "name": "schema-markup",
+ "description": "Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "screen-reader-testing",
- "path": "skills/screen-reader-testing",
+ "path": "skills\\screen-reader-testing",
"category": "uncategorized",
"name": "screen-reader-testing",
"description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...",
@@ -6634,7 +6778,7 @@
},
{
"id": "screenshots",
- "path": "skills/screenshots",
+ "path": "skills\\screenshots",
"category": "uncategorized",
"name": "screenshots",
"description": "Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.",
@@ -6643,7 +6787,7 @@
},
{
"id": "scroll-experience",
- "path": "skills/scroll-experience",
+ "path": "skills\\scroll-experience",
"category": "uncategorized",
"name": "scroll-experience",
"description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p...",
@@ -6652,7 +6796,7 @@
},
{
"id": "search-specialist",
- "path": "skills/search-specialist",
+ "path": "skills\\search-specialist",
"category": "uncategorized",
"name": "search-specialist",
"description": "Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.",
@@ -6661,43 +6805,34 @@
},
{
"id": "secrets-management",
- "path": "skills/secrets-management",
+ "path": "skills\\secrets-management",
"category": "uncategorized",
"name": "secrets-management",
"description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "security-auditor",
- "path": "skills/security-auditor",
- "category": "uncategorized",
- "name": "Security Auditor",
- "description": "You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "security-scanning-security-sast",
- "path": "skills/security-scanning-security-sast",
- "category": "uncategorized",
- "name": "Security Scanning Security Sast",
- "description": "Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "security-audit",
- "path": "skills/security-audit",
+ "path": "skills\\security-audit",
"category": "uncategorized",
"name": "security-audit",
"description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
"risk": "safe",
"source": "personal"
},
+ {
+ "id": "security-auditor",
+ "path": "skills\\security-auditor",
+ "category": "uncategorized",
+ "name": "security-auditor",
+ "description": "Expert security auditor specializing in DevSecOps, comprehensive\ncybersecurity, and compliance frameworks. Masters vulnerability assessment,\nthreat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud\nsecurity, and security automation. Handles DevSecOps integration, compliance\n(GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits,\nDevSecOps, or compliance implementation.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "security-bluebook-builder",
- "path": "skills/security-bluebook-builder",
+ "path": "skills\\security-bluebook-builder",
"category": "uncategorized",
"name": "security-bluebook-builder",
"description": "Build security Blue Books for sensitive apps",
@@ -6706,7 +6841,7 @@
},
{
"id": "security-compliance-compliance-check",
- "path": "skills/security-compliance-compliance-check",
+ "path": "skills\\security-compliance-compliance-check",
"category": "uncategorized",
"name": "security-compliance-compliance-check",
"description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...",
@@ -6715,7 +6850,7 @@
},
{
"id": "security-requirement-extraction",
- "path": "skills/security-requirement-extraction",
+ "path": "skills\\security-requirement-extraction",
"category": "uncategorized",
"name": "security-requirement-extraction",
"description": "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.",
@@ -6724,7 +6859,7 @@
},
{
"id": "security-scanning-security-dependencies",
- "path": "skills/security-scanning-security-dependencies",
+ "path": "skills\\security-scanning-security-dependencies",
"category": "uncategorized",
"name": "security-scanning-security-dependencies",
"description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass...",
@@ -6733,16 +6868,25 @@
},
{
"id": "security-scanning-security-hardening",
- "path": "skills/security-scanning-security-hardening",
+ "path": "skills\\security-scanning-security-hardening",
"category": "uncategorized",
"name": "security-scanning-security-hardening",
"description": "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "security-scanning-security-sast",
+ "path": "skills\\security-scanning-security-sast",
+ "category": "uncategorized",
+ "name": "security-scanning-security-sast",
+ "description": "Static Application Security Testing (SAST) for code vulnerability\nanalysis across multiple languages and frameworks\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "segment-automation",
- "path": "skills/segment-automation",
+ "path": "skills\\segment-automation",
"category": "uncategorized",
"name": "segment-automation",
"description": "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.",
@@ -6751,7 +6895,7 @@
},
{
"id": "segment-cdp",
- "path": "skills/segment-cdp",
+ "path": "skills\\segment-cdp",
"category": "uncategorized",
"name": "segment-cdp",
"description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...",
@@ -6760,7 +6904,7 @@
},
{
"id": "sendgrid-automation",
- "path": "skills/sendgrid-automation",
+ "path": "skills\\sendgrid-automation",
"category": "uncategorized",
"name": "sendgrid-automation",
"description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche...",
@@ -6769,7 +6913,7 @@
},
{
"id": "senior-architect",
- "path": "skills/senior-architect",
+ "path": "skills\\senior-architect",
"category": "uncategorized",
"name": "senior-architect",
"description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I...",
@@ -6778,7 +6922,7 @@
},
{
"id": "senior-fullstack",
- "path": "skills/senior-fullstack",
+ "path": "skills\\senior-fullstack",
"category": "uncategorized",
"name": "senior-fullstack",
"description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec...",
@@ -6787,7 +6931,7 @@
},
{
"id": "sentry-automation",
- "path": "skills/sentry-automation",
+ "path": "skills\\sentry-automation",
"category": "uncategorized",
"name": "sentry-automation",
"description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
@@ -6796,115 +6940,115 @@
},
{
"id": "seo-audit",
- "path": "skills/seo-audit",
+ "path": "skills\\seo-audit",
"category": "uncategorized",
- "name": "Seo Audit",
- "description": "You are an **SEO diagnostic specialist**. Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility\u2014**not to implement fixes unless explicitly requested**.",
+ "name": "seo-audit",
+ "description": "Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-authority-builder",
- "path": "skills/seo-authority-builder",
+ "path": "skills\\seo-authority-builder",
"category": "uncategorized",
- "name": "Seo Authority Builder",
- "description": "- Working on seo authority builder tasks or workflows - Needing guidance, best practices, or checklists for seo authority builder",
+ "name": "seo-authority-builder",
+ "description": "Analyzes content for E-E-A-T signals and suggests improvements to\nbuild authority and trust. Identifies missing credibility elements. Use\nPROACTIVELY for YMYL topics.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-cannibalization-detector",
- "path": "skills/seo-cannibalization-detector",
+ "path": "skills\\seo-cannibalization-detector",
"category": "uncategorized",
- "name": "Seo Cannibalization Detector",
- "description": "- Working on seo cannibalization detector tasks or workflows - Needing guidance, best practices, or checklists for seo cannibalization detector",
+ "name": "seo-cannibalization-detector",
+ "description": "Analyzes multiple provided pages to identify keyword overlap and\npotential cannibalization issues. Suggests differentiation strategies. Use\nPROACTIVELY when reviewing similar content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-auditor",
- "path": "skills/seo-content-auditor",
+ "path": "skills\\seo-content-auditor",
"category": "uncategorized",
- "name": "Seo Content Auditor",
- "description": "- Working on seo content auditor tasks or workflows - Needing guidance, best practices, or checklists for seo content auditor",
+ "name": "seo-content-auditor",
+ "description": "Analyzes provided content for quality, E-E-A-T signals, and SEO\nbest practices. Scores content and provides improvement recommendations based\non established guidelines. Use PROACTIVELY for content review.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-planner",
- "path": "skills/seo-content-planner",
+ "path": "skills\\seo-content-planner",
"category": "uncategorized",
- "name": "Seo Content Planner",
- "description": "- Working on seo content planner tasks or workflows - Needing guidance, best practices, or checklists for seo content planner",
+ "name": "seo-content-planner",
+ "description": "Creates comprehensive content outlines and topic clusters for SEO.\nPlans content calendars and identifies topic gaps. Use PROACTIVELY for content\nstrategy and planning.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-refresher",
- "path": "skills/seo-content-refresher",
+ "path": "skills\\seo-content-refresher",
"category": "uncategorized",
- "name": "Seo Content Refresher",
- "description": "- Working on seo content refresher tasks or workflows - Needing guidance, best practices, or checklists for seo content refresher",
+ "name": "seo-content-refresher",
+ "description": "Identifies outdated elements in provided content and suggests\nupdates to maintain freshness. Finds statistics, dates, and examples that need\nupdating. Use PROACTIVELY for older content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-content-writer",
- "path": "skills/seo-content-writer",
+ "path": "skills\\seo-content-writer",
"category": "uncategorized",
- "name": "Seo Content Writer",
- "description": "- Working on seo content writer tasks or workflows - Needing guidance, best practices, or checklists for seo content writer",
+ "name": "seo-content-writer",
+ "description": "Writes SEO-optimized content based on provided keywords and topic\nbriefs. Creates engaging, comprehensive content following best practices. Use\nPROACTIVELY for content creation tasks.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-fundamentals",
- "path": "skills/seo-fundamentals",
+ "path": "skills\\seo-fundamentals",
"category": "uncategorized",
- "name": "Seo Fundamentals",
- "description": "---",
+ "name": "seo-fundamentals",
+ "description": "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-keyword-strategist",
- "path": "skills/seo-keyword-strategist",
+ "path": "skills\\seo-keyword-strategist",
"category": "uncategorized",
- "name": "Seo Keyword Strategist",
- "description": "- Working on seo keyword strategist tasks or workflows - Needing guidance, best practices, or checklists for seo keyword strategist",
+ "name": "seo-keyword-strategist",
+ "description": "Analyzes keyword usage in provided content, calculates density,\nsuggests semantic variations and LSI keywords based on the topic. Prevents\nover-optimization. Use PROACTIVELY for content optimization.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-meta-optimizer",
- "path": "skills/seo-meta-optimizer",
+ "path": "skills\\seo-meta-optimizer",
"category": "uncategorized",
- "name": "Seo Meta Optimizer",
- "description": "- Working on seo meta optimizer tasks or workflows - Needing guidance, best practices, or checklists for seo meta optimizer",
+ "name": "seo-meta-optimizer",
+ "description": "Creates optimized meta titles, descriptions, and URL suggestions\nbased on character limits and best practices. Generates compelling,\nkeyword-rich metadata. Use PROACTIVELY for new content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-snippet-hunter",
- "path": "skills/seo-snippet-hunter",
+ "path": "skills\\seo-snippet-hunter",
"category": "uncategorized",
- "name": "Seo Snippet Hunter",
- "description": "- Working on seo snippet hunter tasks or workflows - Needing guidance, best practices, or checklists for seo snippet hunter",
+ "name": "seo-snippet-hunter",
+ "description": "Formats content to be eligible for featured snippets and SERP\nfeatures. Creates snippet-optimized content blocks based on best practices.\nUse PROACTIVELY for question-based content.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "seo-structure-architect",
- "path": "skills/seo-structure-architect",
+ "path": "skills\\seo-structure-architect",
"category": "uncategorized",
- "name": "Seo Structure Architect",
- "description": "- Working on seo structure architect tasks or workflows - Needing guidance, best practices, or checklists for seo structure architect",
+ "name": "seo-structure-architect",
+ "description": "Analyzes and optimizes content structure including header\nhierarchy, suggests schema markup, and internal linking opportunities. Creates\nsearch-friendly content organization. Use PROACTIVELY for content structuring.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "server-management",
- "path": "skills/server-management",
+ "path": "skills\\server-management",
"category": "uncategorized",
"name": "server-management",
"description": "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.",
@@ -6913,7 +7057,7 @@
},
{
"id": "service-mesh-expert",
- "path": "skills/service-mesh-expert",
+ "path": "skills\\service-mesh-expert",
"category": "uncategorized",
"name": "service-mesh-expert",
"description": "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con",
@@ -6922,7 +7066,7 @@
},
{
"id": "service-mesh-observability",
- "path": "skills/service-mesh-observability",
+ "path": "skills\\service-mesh-observability",
"category": "uncategorized",
"name": "service-mesh-observability",
"description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL...",
@@ -6931,7 +7075,7 @@
},
{
"id": "shader-programming-glsl",
- "path": "skills/shader-programming-glsl",
+ "path": "skills\\shader-programming-glsl",
"category": "uncategorized",
"name": "shader-programming-glsl",
"description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
@@ -6940,7 +7084,7 @@
},
{
"id": "sharp-edges",
- "path": "skills/sharp-edges",
+ "path": "skills\\sharp-edges",
"category": "uncategorized",
"name": "sharp-edges",
"description": "Identify error-prone APIs and dangerous configurations",
@@ -6949,7 +7093,7 @@
},
{
"id": "shellcheck-configuration",
- "path": "skills/shellcheck-configuration",
+ "path": "skills\\shellcheck-configuration",
"category": "uncategorized",
"name": "shellcheck-configuration",
"description": "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.",
@@ -6958,7 +7102,7 @@
},
{
"id": "shodan-reconnaissance",
- "path": "skills/shodan-reconnaissance",
+ "path": "skills\\shodan-reconnaissance",
"category": "uncategorized",
"name": "shodan-reconnaissance",
"description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges...",
@@ -6967,7 +7111,7 @@
},
{
"id": "shopify-apps",
- "path": "skills/shopify-apps",
+ "path": "skills\\shopify-apps",
"category": "uncategorized",
"name": "shopify-apps",
"description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U...",
@@ -6976,7 +7120,7 @@
},
{
"id": "shopify-automation",
- "path": "skills/shopify-automation",
+ "path": "skills\\shopify-automation",
"category": "uncategorized",
"name": "shopify-automation",
"description": "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.",
@@ -6985,7 +7129,7 @@
},
{
"id": "shopify-development",
- "path": "skills/shopify-development",
+ "path": "skills\\shopify-development",
"category": "uncategorized",
"name": "shopify-development",
"description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"\n",
@@ -6994,7 +7138,7 @@
},
{
"id": "signup-flow-cro",
- "path": "skills/signup-flow-cro",
+ "path": "skills\\signup-flow-cro",
"category": "uncategorized",
"name": "signup-flow-cro",
"description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...",
@@ -7003,7 +7147,7 @@
},
{
"id": "similarity-search-patterns",
- "path": "skills/similarity-search-patterns",
+ "path": "skills\\similarity-search-patterns",
"category": "uncategorized",
"name": "similarity-search-patterns",
"description": "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.",
@@ -7012,7 +7156,7 @@
},
{
"id": "skill-creator",
- "path": "skills/skill-creator",
+ "path": "skills\\skill-creator",
"category": "uncategorized",
"name": "skill-creator",
"description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s...",
@@ -7021,7 +7165,7 @@
},
{
"id": "skill-creator-ms",
- "path": "skills/skill-creator-ms",
+ "path": "skills\\skill-creator-ms",
"category": "uncategorized",
"name": "skill-creator-ms",
"description": "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.",
@@ -7030,7 +7174,7 @@
},
{
"id": "skill-developer",
- "path": "skills/skill-developer",
+ "path": "skills\\skill-developer",
"category": "uncategorized",
"name": "skill-developer",
"description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil...",
@@ -7039,7 +7183,7 @@
},
{
"id": "skill-rails-upgrade",
- "path": "skills/skill-rails-upgrade",
+ "path": "skills\\skill-rails-upgrade",
"category": "uncategorized",
"name": "skill-rails-upgrade",
"description": "Analyze Rails apps and provide upgrade assessments",
@@ -7048,7 +7192,7 @@
},
{
"id": "skill-seekers",
- "path": "skills/skill-seekers",
+ "path": "skills\\skill-seekers",
"category": "uncategorized",
"name": "skill-seekers",
"description": "-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.",
@@ -7057,7 +7201,7 @@
},
{
"id": "slack-automation",
- "path": "skills/slack-automation",
+ "path": "skills\\slack-automation",
"category": "uncategorized",
"name": "slack-automation",
"description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica...",
@@ -7066,7 +7210,7 @@
},
{
"id": "slack-bot-builder",
- "path": "skills/slack-bot-builder",
+ "path": "skills\\slack-bot-builder",
"category": "uncategorized",
"name": "slack-bot-builder",
"description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W...",
@@ -7075,7 +7219,7 @@
},
{
"id": "slack-gif-creator",
- "path": "skills/slack-gif-creator",
+ "path": "skills\\slack-gif-creator",
"category": "uncategorized",
"name": "slack-gif-creator",
"description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"...",
@@ -7084,7 +7228,7 @@
},
{
"id": "slo-implementation",
- "path": "skills/slo-implementation",
+ "path": "skills\\slo-implementation",
"category": "uncategorized",
"name": "slo-implementation",
"description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m...",
@@ -7093,7 +7237,7 @@
},
{
"id": "smtp-penetration-testing",
- "path": "skills/smtp-penetration-testing",
+ "path": "skills\\smtp-penetration-testing",
"category": "uncategorized",
"name": "smtp-penetration-testing",
"description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre...",
@@ -7102,7 +7246,7 @@
},
{
"id": "social-content",
- "path": "skills/social-content",
+ "path": "skills\\social-content",
"category": "uncategorized",
"name": "social-content",
"description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...",
@@ -7111,7 +7255,7 @@
},
{
"id": "software-architecture",
- "path": "skills/software-architecture",
+ "path": "skills\\software-architecture",
"category": "uncategorized",
"name": "software-architecture",
"description": "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.",
@@ -7120,7 +7264,7 @@
},
{
"id": "solidity-security",
- "path": "skills/solidity-security",
+ "path": "skills\\solidity-security",
"category": "uncategorized",
"name": "solidity-security",
"description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...",
@@ -7129,25 +7273,16 @@
},
{
"id": "spark-optimization",
- "path": "skills/spark-optimization",
+ "path": "skills\\spark-optimization",
"category": "uncategorized",
"name": "spark-optimization",
"description": "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "sql-pro",
- "path": "skills/sql-pro",
- "category": "uncategorized",
- "name": "Sql Pro",
- "description": "You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "sql-injection-testing",
- "path": "skills/sql-injection-testing",
+ "path": "skills\\sql-injection-testing",
"category": "uncategorized",
"name": "sql-injection-testing",
"description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform...",
@@ -7156,16 +7291,25 @@
},
{
"id": "sql-optimization-patterns",
- "path": "skills/sql-optimization-patterns",
+ "path": "skills\\sql-optimization-patterns",
"category": "uncategorized",
"name": "sql-optimization-patterns",
"description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "sql-pro",
+ "path": "skills\\sql-pro",
+ "category": "uncategorized",
+ "name": "sql-pro",
+ "description": "Master modern SQL with cloud-native databases, OLTP/OLAP\noptimization, and advanced query techniques. Expert in performance tuning,\ndata modeling, and hybrid analytical systems. Use PROACTIVELY for database\noptimization or complex analysis.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "sqlmap-database-pentesting",
- "path": "skills/sqlmap-database-pentesting",
+ "path": "skills\\sqlmap-database-pentesting",
"category": "uncategorized",
"name": "sqlmap-database-pentesting",
"description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns...",
@@ -7174,7 +7318,7 @@
},
{
"id": "square-automation",
- "path": "skills/square-automation",
+ "path": "skills\\square-automation",
"category": "uncategorized",
"name": "square-automation",
"description": "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.",
@@ -7183,7 +7327,7 @@
},
{
"id": "ssh-penetration-testing",
- "path": "skills/ssh-penetration-testing",
+ "path": "skills\\ssh-penetration-testing",
"category": "uncategorized",
"name": "ssh-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu...",
@@ -7192,61 +7336,61 @@
},
{
"id": "startup-analyst",
- "path": "skills/startup-analyst",
+ "path": "skills\\startup-analyst",
"category": "uncategorized",
- "name": "Startup Analyst",
- "description": "- Working on startup analyst tasks or workflows - Needing guidance, best practices, or checklists for startup analyst",
+ "name": "startup-analyst",
+ "description": "Expert startup business analyst specializing in market sizing,\nfinancial modeling, competitive analysis, and strategic planning for\nearly-stage companies. Use PROACTIVELY when the user asks about market\nopportunity, TAM/SAM/SOM, financial projections, unit economics, competitive\nlandscape, team planning, startup metrics, or business strategy for pre-seed\nthrough Series A startups.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-business-case",
- "path": "skills/startup-business-analyst-business-case",
+ "path": "skills\\startup-business-analyst-business-case",
"category": "uncategorized",
- "name": "Startup Business Analyst Business Case",
- "description": "Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.",
+ "name": "startup-business-analyst-business-case",
+ "description": "Generate comprehensive investor-ready business case document with\nmarket, solution, financials, and strategy\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-financial-projections",
- "path": "skills/startup-business-analyst-financial-projections",
+ "path": "skills\\startup-business-analyst-financial-projections",
"category": "uncategorized",
- "name": "Startup Business Analyst Financial Projections",
- "description": "Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.",
+ "name": "startup-business-analyst-financial-projections",
+ "description": "Create detailed 3-5 year financial model with revenue, costs, cash\nflow, and scenarios\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-business-analyst-market-opportunity",
- "path": "skills/startup-business-analyst-market-opportunity",
+ "path": "skills\\startup-business-analyst-market-opportunity",
"category": "uncategorized",
- "name": "Startup Business Analyst Market Opportunity",
- "description": "Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.",
+ "name": "startup-business-analyst-market-opportunity",
+ "description": "Generate comprehensive market opportunity analysis with TAM/SAM/SOM\ncalculations\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-financial-modeling",
- "path": "skills/startup-financial-modeling",
+ "path": "skills\\startup-financial-modeling",
"category": "uncategorized",
- "name": "Startup Financial Modeling",
- "description": "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.",
+ "name": "startup-financial-modeling",
+ "description": "This skill should be used when the user asks to \\\\\\\"create financial\nprojections\", \"build a financial model\", \"forecast revenue\", \"calculate burn\nrate\", \"estimate runway\", \"model cash flow\", or requests 3-5 year financial\nplanning for a startup.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "startup-metrics-framework",
- "path": "skills/startup-metrics-framework",
+ "path": "skills\\startup-metrics-framework",
"category": "uncategorized",
- "name": "Startup Metrics Framework",
- "description": "Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.",
+ "name": "startup-metrics-framework",
+ "description": "This skill should be used when the user asks about \\\\\\\"key startup\nmetrics\", \"SaaS metrics\", \"CAC and LTV\", \"unit economics\", \"burn multiple\",\n\"rule of 40\", \"marketplace metrics\", or requests guidance on tracking and\noptimizing business performance metrics.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "stitch-ui-design",
- "path": "skills/stitch-ui-design",
+ "path": "skills\\stitch-ui-design",
"category": "uncategorized",
"name": "stitch-ui-design",
"description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra...",
@@ -7255,7 +7399,7 @@
},
{
"id": "stride-analysis-patterns",
- "path": "skills/stride-analysis-patterns",
+ "path": "skills\\stride-analysis-patterns",
"category": "uncategorized",
"name": "stride-analysis-patterns",
"description": "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.",
@@ -7264,7 +7408,7 @@
},
{
"id": "stripe-automation",
- "path": "skills/stripe-automation",
+ "path": "skills\\stripe-automation",
"category": "uncategorized",
"name": "stripe-automation",
"description": "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.",
@@ -7273,7 +7417,7 @@
},
{
"id": "stripe-integration",
- "path": "skills/stripe-integration",
+ "path": "skills\\stripe-integration",
"category": "uncategorized",
"name": "stripe-integration",
"description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ...",
@@ -7282,7 +7426,7 @@
},
{
"id": "subagent-driven-development",
- "path": "skills/subagent-driven-development",
+ "path": "skills\\subagent-driven-development",
"category": "uncategorized",
"name": "subagent-driven-development",
"description": "Use when executing implementation plans with independent tasks in the current session",
@@ -7291,7 +7435,7 @@
},
{
"id": "supabase-automation",
- "path": "skills/supabase-automation",
+ "path": "skills\\supabase-automation",
"category": "uncategorized",
"name": "supabase-automation",
"description": "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -7300,7 +7444,7 @@
},
{
"id": "superpowers-lab",
- "path": "skills/superpowers-lab",
+ "path": "skills\\superpowers-lab",
"category": "uncategorized",
"name": "superpowers-lab",
"description": "Lab environment for Claude superpowers",
@@ -7309,7 +7453,7 @@
},
{
"id": "swiftui-expert-skill",
- "path": "skills/swiftui-expert-skill",
+ "path": "skills\\swiftui-expert-skill",
"category": "uncategorized",
"name": "swiftui-expert-skill",
"description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil...",
@@ -7318,7 +7462,7 @@
},
{
"id": "systematic-debugging",
- "path": "skills/systematic-debugging",
+ "path": "skills\\systematic-debugging",
"category": "uncategorized",
"name": "systematic-debugging",
"description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes",
@@ -7327,7 +7471,7 @@
},
{
"id": "systems-programming-rust-project",
- "path": "skills/systems-programming-rust-project",
+ "path": "skills\\systems-programming-rust-project",
"category": "uncategorized",
"name": "systems-programming-rust-project",
"description": "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing",
@@ -7336,7 +7480,7 @@
},
{
"id": "tailwind-design-system",
- "path": "skills/tailwind-design-system",
+ "path": "skills\\tailwind-design-system",
"category": "uncategorized",
"name": "tailwind-design-system",
"description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...",
@@ -7345,7 +7489,7 @@
},
{
"id": "tailwind-patterns",
- "path": "skills/tailwind-patterns",
+ "path": "skills\\tailwind-patterns",
"category": "uncategorized",
"name": "tailwind-patterns",
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.",
@@ -7354,7 +7498,7 @@
},
{
"id": "tavily-web",
- "path": "skills/tavily-web",
+ "path": "skills\\tavily-web",
"category": "uncategorized",
"name": "tavily-web",
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API",
@@ -7363,16 +7507,16 @@
},
{
"id": "tdd-orchestrator",
- "path": "skills/tdd-orchestrator",
+ "path": "skills\\tdd-orchestrator",
"category": "uncategorized",
- "name": "Tdd Orchestrator",
- "description": "- Working on tdd orchestrator tasks or workflows - Needing guidance, best practices, or checklists for tdd orchestrator",
+ "name": "tdd-orchestrator",
+ "description": "Master TDD orchestrator specializing in red-green-refactor\ndiscipline, multi-agent workflow coordination, and comprehensive test-driven\ndevelopment practices. Enforces TDD best practices across teams with\nAI-assisted testing and modern frameworks. Use PROACTIVELY for TDD\nimplementation and governance.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "tdd-workflow",
- "path": "skills/tdd-workflow",
+ "path": "skills\\tdd-workflow",
"category": "uncategorized",
"name": "tdd-workflow",
"description": "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.",
@@ -7381,7 +7525,7 @@
},
{
"id": "tdd-workflows-tdd-cycle",
- "path": "skills/tdd-workflows-tdd-cycle",
+ "path": "skills\\tdd-workflows-tdd-cycle",
"category": "uncategorized",
"name": "tdd-workflows-tdd-cycle",
"description": "Use when working with tdd workflows tdd cycle",
@@ -7390,7 +7534,7 @@
},
{
"id": "tdd-workflows-tdd-green",
- "path": "skills/tdd-workflows-tdd-green",
+ "path": "skills\\tdd-workflows-tdd-green",
"category": "uncategorized",
"name": "tdd-workflows-tdd-green",
"description": "Implement the minimal code needed to make failing tests pass in the TDD green phase.",
@@ -7399,7 +7543,7 @@
},
{
"id": "tdd-workflows-tdd-red",
- "path": "skills/tdd-workflows-tdd-red",
+ "path": "skills\\tdd-workflows-tdd-red",
"category": "uncategorized",
"name": "tdd-workflows-tdd-red",
"description": "Generate failing tests for the TDD red phase to define expected behavior and edge cases.",
@@ -7408,25 +7552,16 @@
},
{
"id": "tdd-workflows-tdd-refactor",
- "path": "skills/tdd-workflows-tdd-refactor",
+ "path": "skills\\tdd-workflows-tdd-refactor",
"category": "uncategorized",
"name": "tdd-workflows-tdd-refactor",
"description": "Use when working with tdd workflows tdd refactor",
"risk": "unknown",
"source": "community"
},
- {
- "id": "team-composition-analysis",
- "path": "skills/team-composition-analysis",
- "category": "uncategorized",
- "name": "Team Composition Analysis",
- "description": "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "team-collaboration-issue",
- "path": "skills/team-collaboration-issue",
+ "path": "skills\\team-collaboration-issue",
"category": "uncategorized",
"name": "team-collaboration-issue",
"description": "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an",
@@ -7435,16 +7570,25 @@
},
{
"id": "team-collaboration-standup-notes",
- "path": "skills/team-collaboration-standup-notes",
+ "path": "skills\\team-collaboration-standup-notes",
"category": "uncategorized",
"name": "team-collaboration-standup-notes",
"description": "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "team-composition-analysis",
+ "path": "skills\\team-composition-analysis",
+ "category": "uncategorized",
+ "name": "team-composition-analysis",
+ "description": "This skill should be used when the user asks to \\\\\\\"plan team\nstructure\", \"determine hiring needs\", \"design org chart\", \"calculate\ncompensation\", \"plan equity allocation\", or requests organizational design and\nheadcount planning for a startup.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "telegram-automation",
- "path": "skills/telegram-automation",
+ "path": "skills\\telegram-automation",
"category": "uncategorized",
"name": "telegram-automation",
"description": "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.",
@@ -7453,7 +7597,7 @@
},
{
"id": "telegram-bot-builder",
- "path": "skills/telegram-bot-builder",
+ "path": "skills\\telegram-bot-builder",
"category": "uncategorized",
"name": "telegram-bot-builder",
"description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...",
@@ -7462,7 +7606,7 @@
},
{
"id": "telegram-mini-app",
- "path": "skills/telegram-mini-app",
+ "path": "skills\\telegram-mini-app",
"category": "uncategorized",
"name": "telegram-mini-app",
"description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build...",
@@ -7471,7 +7615,7 @@
},
{
"id": "templates",
- "path": "skills/app-builder/templates",
+ "path": "skills\\app-builder\\templates",
"category": "app-builder",
"name": "templates",
"description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
@@ -7480,34 +7624,25 @@
},
{
"id": "temporal-python-pro",
- "path": "skills/temporal-python-pro",
+ "path": "skills\\temporal-python-pro",
"category": "uncategorized",
- "name": "Temporal Python Pro",
- "description": "- Working on temporal python pro tasks or workflows - Needing guidance, best practices, or checklists for temporal python pro",
+ "name": "temporal-python-pro",
+ "description": "Master Temporal workflow orchestration with Python SDK. Implements\ndurable workflows, saga patterns, and distributed transactions. Covers\nasync/await, testing strategies, and production deployment. Use PROACTIVELY\nfor workflow design, microservice orchestration, or long-running processes.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "temporal-python-testing",
- "path": "skills/temporal-python-testing",
+ "path": "skills\\temporal-python-testing",
"category": "uncategorized",
"name": "temporal-python-testing",
"description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor...",
"risk": "unknown",
"source": "community"
},
- {
- "id": "terraform-specialist",
- "path": "skills/terraform-specialist",
- "category": "uncategorized",
- "name": "Terraform Specialist",
- "description": "You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "terraform-aws-modules",
- "path": "skills/terraform-aws-modules",
+ "path": "skills\\terraform-aws-modules",
"category": "uncategorized",
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
@@ -7516,7 +7651,7 @@
},
{
"id": "terraform-infrastructure",
- "path": "skills/terraform-infrastructure",
+ "path": "skills\\terraform-infrastructure",
"category": "uncategorized",
"name": "terraform-infrastructure",
"description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
@@ -7525,7 +7660,7 @@
},
{
"id": "terraform-module-library",
- "path": "skills/terraform-module-library",
+ "path": "skills\\terraform-module-library",
"category": "uncategorized",
"name": "terraform-module-library",
"description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ...",
@@ -7534,7 +7669,7 @@
},
{
"id": "terraform-skill",
- "path": "skills/terraform-skill",
+ "path": "skills\\terraform-skill",
"category": "uncategorized",
"name": "terraform-skill",
"description": "Terraform infrastructure as code best practices",
@@ -7542,17 +7677,26 @@
"source": "https://github.com/antonbabenko/terraform-skill"
},
{
- "id": "test-automator",
- "path": "skills/test-automator",
+ "id": "terraform-specialist",
+ "path": "skills\\terraform-specialist",
"category": "uncategorized",
- "name": "Test Automator",
- "description": "- Working on test automator tasks or workflows - Needing guidance, best practices, or checklists for test automator",
+ "name": "terraform-specialist",
+ "description": "Expert Terraform/OpenTofu specialist mastering advanced IaC\nautomation, state management, and enterprise infrastructure patterns. Handles\ncomplex module design, multi-cloud deployments, GitOps workflows, policy as\ncode, and CI/CD integration. Covers migration strategies, security best\npractices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state\nmanagement, or infrastructure automation.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
+ },
+ {
+ "id": "test-automator",
+ "path": "skills\\test-automator",
+ "category": "uncategorized",
+ "name": "test-automator",
+ "description": "Master AI-powered test automation with modern frameworks,\nself-healing tests, and comprehensive quality engineering. Build scalable\ntesting strategies with advanced CI/CD integration. Use PROACTIVELY for\ntesting automation or quality assurance.\n",
+ "risk": "unknown",
+ "source": "community"
},
{
"id": "test-driven-development",
- "path": "skills/test-driven-development",
+ "path": "skills\\test-driven-development",
"category": "uncategorized",
"name": "test-driven-development",
"description": "Use when implementing any feature or bugfix, before writing implementation code",
@@ -7561,7 +7705,7 @@
},
{
"id": "test-fixing",
- "path": "skills/test-fixing",
+ "path": "skills\\test-fixing",
"category": "uncategorized",
"name": "test-fixing",
"description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...",
@@ -7570,7 +7714,7 @@
},
{
"id": "testing-patterns",
- "path": "skills/testing-patterns",
+ "path": "skills\\testing-patterns",
"category": "uncategorized",
"name": "testing-patterns",
"description": "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.",
@@ -7579,7 +7723,7 @@
},
{
"id": "testing-qa",
- "path": "skills/testing-qa",
+ "path": "skills\\testing-qa",
"category": "uncategorized",
"name": "testing-qa",
"description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
@@ -7588,7 +7732,7 @@
},
{
"id": "theme-factory",
- "path": "skills/theme-factory",
+ "path": "skills\\theme-factory",
"category": "uncategorized",
"name": "theme-factory",
"description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac...",
@@ -7597,7 +7741,7 @@
},
{
"id": "threat-mitigation-mapping",
- "path": "skills/threat-mitigation-mapping",
+ "path": "skills\\threat-mitigation-mapping",
"category": "uncategorized",
"name": "threat-mitigation-mapping",
"description": "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.",
@@ -7606,7 +7750,7 @@
},
{
"id": "threat-modeling-expert",
- "path": "skills/threat-modeling-expert",
+ "path": "skills\\threat-modeling-expert",
"category": "uncategorized",
"name": "threat-modeling-expert",
"description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...",
@@ -7615,7 +7759,7 @@
},
{
"id": "threejs-skills",
- "path": "skills/threejs-skills",
+ "path": "skills\\threejs-skills",
"category": "uncategorized",
"name": "threejs-skills",
"description": "Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.",
@@ -7624,7 +7768,7 @@
},
{
"id": "tiktok-automation",
- "path": "skills/tiktok-automation",
+ "path": "skills\\tiktok-automation",
"category": "uncategorized",
"name": "tiktok-automation",
"description": "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.",
@@ -7633,7 +7777,7 @@
},
{
"id": "todoist-automation",
- "path": "skills/todoist-automation",
+ "path": "skills\\todoist-automation",
"category": "uncategorized",
"name": "todoist-automation",
"description": "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -7642,7 +7786,7 @@
},
{
"id": "tool-design",
- "path": "skills/tool-design",
+ "path": "skills\\tool-design",
"category": "uncategorized",
"name": "tool-design",
"description": "Build tools that agents can use effectively, including architectural reduction patterns",
@@ -7651,7 +7795,7 @@
},
{
"id": "top-web-vulnerabilities",
- "path": "skills/top-web-vulnerabilities",
+ "path": "skills\\top-web-vulnerabilities",
"category": "uncategorized",
"name": "top-web-vulnerabilities",
"description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject...",
@@ -7660,16 +7804,16 @@
},
{
"id": "track-management",
- "path": "skills/track-management",
+ "path": "skills\\track-management",
"category": "uncategorized",
- "name": "Track Management",
- "description": "Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.",
+ "name": "track-management",
+ "description": "Use this skill when creating, managing, or working with Conductor\ntracks - the logical work units for features, bugs, and refactors. Applies to\nspec.md, plan.md, and track lifecycle operations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "trello-automation",
- "path": "skills/trello-automation",
+ "path": "skills\\trello-automation",
"category": "uncategorized",
"name": "trello-automation",
"description": "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.",
@@ -7678,7 +7822,7 @@
},
{
"id": "trigger-dev",
- "path": "skills/trigger-dev",
+ "path": "skills\\trigger-dev",
"category": "uncategorized",
"name": "trigger-dev",
"description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta...",
@@ -7687,7 +7831,7 @@
},
{
"id": "turborepo-caching",
- "path": "skills/turborepo-caching",
+ "path": "skills\\turborepo-caching",
"category": "uncategorized",
"name": "turborepo-caching",
"description": "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.",
@@ -7696,16 +7840,16 @@
},
{
"id": "tutorial-engineer",
- "path": "skills/tutorial-engineer",
+ "path": "skills\\tutorial-engineer",
"category": "uncategorized",
- "name": "Tutorial Engineer",
- "description": "- Working on tutorial engineer tasks or workflows - Needing guidance, best practices, or checklists for tutorial engineer",
+ "name": "tutorial-engineer",
+ "description": "Creates step-by-step tutorials and educational content from code.\nTransforms complex concepts into progressive learning experiences with\nhands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,\nor concept explanations.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "twilio-communications",
- "path": "skills/twilio-communications",
+ "path": "skills\\twilio-communications",
"category": "uncategorized",
"name": "twilio-communications",
"description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a...",
@@ -7714,34 +7858,16 @@
},
{
"id": "twitter-automation",
- "path": "skills/twitter-automation",
+ "path": "skills\\twitter-automation",
"category": "uncategorized",
"name": "twitter-automation",
"description": "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.",
"risk": "unknown",
"source": "community"
},
- {
- "id": "typescript-expert",
- "path": "skills/typescript-expert",
- "category": "uncategorized",
- "name": "Typescript Expert",
- "description": "You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.",
- "risk": "unknown",
- "source": "unknown"
- },
- {
- "id": "typescript-pro",
- "path": "skills/typescript-pro",
- "category": "uncategorized",
- "name": "Typescript Pro",
- "description": "You are a TypeScript expert specializing in advanced typing and enterprise-grade development.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "typescript-advanced-types",
- "path": "skills/typescript-advanced-types",
+ "path": "skills\\typescript-advanced-types",
"category": "uncategorized",
"name": "typescript-advanced-types",
"description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex...",
@@ -7749,44 +7875,62 @@
"source": "community"
},
{
- "id": "ui-ux-designer",
- "path": "skills/ui-ux-designer",
+ "id": "typescript-expert",
+ "path": "skills\\typescript-expert",
"category": "uncategorized",
- "name": "Ui Ux Designer",
- "description": "- Working on ui ux designer tasks or workflows - Needing guidance, best practices, or checklists for ui ux designer",
+ "name": "typescript-expert",
+ "description": "TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
- "id": "ui-visual-validator",
- "path": "skills/ui-visual-validator",
+ "id": "typescript-pro",
+ "path": "skills\\typescript-pro",
"category": "uncategorized",
- "name": "Ui Visual Validator",
- "description": "- Working on ui visual validator tasks or workflows - Needing guidance, best practices, or checklists for ui visual validator",
+ "name": "typescript-pro",
+ "description": "Master TypeScript with advanced types, generics, and strict type\nsafety. Handles complex type systems, decorators, and enterprise-grade\npatterns. Use PROACTIVELY for TypeScript architecture, type inference\noptimization, or advanced typing patterns.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "ui-skills",
- "path": "skills/ui-skills",
+ "path": "skills\\ui-skills",
"category": "uncategorized",
"name": "ui-skills",
"description": "Opinionated, evolving constraints to guide agents when building interfaces",
"risk": "safe",
"source": "https://github.com/ibelick/ui-skills"
},
+ {
+ "id": "ui-ux-designer",
+ "path": "skills\\ui-ux-designer",
+ "category": "uncategorized",
+ "name": "ui-ux-designer",
+ "description": "Create interface designs, wireframes, and design systems. Masters\nuser research, accessibility standards, and modern design tools. Specializes\nin design tokens, component libraries, and inclusive design. Use PROACTIVELY\nfor design systems, user flows, or interface optimization.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "ui-ux-pro-max",
- "path": "skills/ui-ux-pro-max",
+ "path": "skills\\ui-ux-pro-max",
"category": "uncategorized",
"name": "ui-ux-pro-max",
"description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "ui-visual-validator",
+ "path": "skills\\ui-visual-validator",
+ "category": "uncategorized",
+ "name": "ui-visual-validator",
+ "description": "Rigorous visual validation expert specializing in UI testing,\ndesign system compliance, and accessibility verification. Masters screenshot\nanalysis, visual regression testing, and component validation. Use PROACTIVELY\nto verify UI modifications have achieved their intended goals through\ncomprehensive visual analysis.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "unit-testing-test-generate",
- "path": "skills/unit-testing-test-generate",
+ "path": "skills\\unit-testing-test-generate",
"category": "uncategorized",
"name": "unit-testing-test-generate",
"description": "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.",
@@ -7795,16 +7939,16 @@
},
{
"id": "unity-developer",
- "path": "skills/unity-developer",
+ "path": "skills\\unity-developer",
"category": "uncategorized",
- "name": "Unity Developer",
- "description": "- Working on unity developer tasks or workflows - Needing guidance, best practices, or checklists for unity developer",
+ "name": "unity-developer",
+ "description": "Build Unity games with optimized C# scripts, efficient rendering,\nand proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and\ncross-platform deployment. Handles gameplay systems, UI implementation, and\nplatform optimization. Use PROACTIVELY for Unity performance issues, game\nmechanics, or cross-platform builds.\n",
"risk": "unknown",
- "source": "unknown"
+ "source": "community"
},
{
"id": "unity-ecs-patterns",
- "path": "skills/unity-ecs-patterns",
+ "path": "skills\\unity-ecs-patterns",
"category": "uncategorized",
"name": "unity-ecs-patterns",
"description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent...",
@@ -7813,7 +7957,7 @@
},
{
"id": "unreal-engine-cpp-pro",
- "path": "skills/unreal-engine-cpp-pro",
+ "path": "skills\\unreal-engine-cpp-pro",
"category": "uncategorized",
"name": "unreal-engine-cpp-pro",
"description": "Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.",
@@ -7822,7 +7966,7 @@
},
{
"id": "upgrading-expo",
- "path": "skills/upgrading-expo",
+ "path": "skills\\upgrading-expo",
"category": "uncategorized",
"name": "upgrading-expo",
"description": "Upgrade Expo SDK versions",
@@ -7831,7 +7975,7 @@
},
{
"id": "upstash-qstash",
- "path": "skills/upstash-qstash",
+ "path": "skills\\upstash-qstash",
"category": "uncategorized",
"name": "upstash-qstash",
"description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul...",
@@ -7840,7 +7984,7 @@
},
{
"id": "using-git-worktrees",
- "path": "skills/using-git-worktrees",
+ "path": "skills\\using-git-worktrees",
"category": "uncategorized",
"name": "using-git-worktrees",
"description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi...",
@@ -7849,7 +7993,7 @@
},
{
"id": "using-neon",
- "path": "skills/using-neon",
+ "path": "skills\\using-neon",
"category": "uncategorized",
"name": "using-neon",
"description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/...",
@@ -7858,7 +8002,7 @@
},
{
"id": "using-superpowers",
- "path": "skills/using-superpowers",
+ "path": "skills\\using-superpowers",
"category": "uncategorized",
"name": "using-superpowers",
"description": "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions",
@@ -7867,7 +8011,7 @@
},
{
"id": "uv-package-manager",
- "path": "skills/uv-package-manager",
+ "path": "skills\\uv-package-manager",
"category": "uncategorized",
"name": "uv-package-manager",
"description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...",
@@ -7876,7 +8020,7 @@
},
{
"id": "varlock-claude-skill",
- "path": "skills/varlock-claude-skill",
+ "path": "skills\\varlock-claude-skill",
"category": "uncategorized",
"name": "varlock-claude-skill",
"description": "Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits",
@@ -7885,7 +8029,7 @@
},
{
"id": "vector-database-engineer",
- "path": "skills/vector-database-engineer",
+ "path": "skills\\vector-database-engineer",
"category": "uncategorized",
"name": "vector-database-engineer",
"description": "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar",
@@ -7894,7 +8038,7 @@
},
{
"id": "vector-index-tuning",
- "path": "skills/vector-index-tuning",
+ "path": "skills\\vector-index-tuning",
"category": "uncategorized",
"name": "vector-index-tuning",
"description": "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.",
@@ -7903,7 +8047,7 @@
},
{
"id": "vercel-automation",
- "path": "skills/vercel-automation",
+ "path": "skills\\vercel-automation",
"category": "uncategorized",
"name": "vercel-automation",
"description": "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.",
@@ -7912,7 +8056,7 @@
},
{
"id": "vercel-deploy-claimable",
- "path": "skills/vercel-deploy-claimable",
+ "path": "skills\\vercel-deploy-claimable",
"category": "uncategorized",
"name": "vercel-deploy-claimable",
"description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...",
@@ -7921,7 +8065,7 @@
},
{
"id": "vercel-deployment",
- "path": "skills/vercel-deployment",
+ "path": "skills\\vercel-deployment",
"category": "uncategorized",
"name": "vercel-deployment",
"description": "Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.",
@@ -7930,7 +8074,7 @@
},
{
"id": "verification-before-completion",
- "path": "skills/verification-before-completion",
+ "path": "skills\\verification-before-completion",
"category": "uncategorized",
"name": "verification-before-completion",
"description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...",
@@ -7939,7 +8083,7 @@
},
{
"id": "vexor",
- "path": "skills/vexor",
+ "path": "skills\\vexor",
"category": "uncategorized",
"name": "vexor",
"description": "Vector-powered CLI for semantic file search with a Claude/Codex skill",
@@ -7948,7 +8092,7 @@
},
{
"id": "viral-generator-builder",
- "path": "skills/viral-generator-builder",
+ "path": "skills\\viral-generator-builder",
"category": "uncategorized",
"name": "viral-generator-builder",
"description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic...",
@@ -7957,7 +8101,7 @@
},
{
"id": "voice-agents",
- "path": "skills/voice-agents",
+ "path": "skills\\voice-agents",
"category": "uncategorized",
"name": "voice-agents",
"description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...",
@@ -7966,7 +8110,7 @@
},
{
"id": "voice-ai-development",
- "path": "skills/voice-ai-development",
+ "path": "skills\\voice-ai-development",
"category": "uncategorized",
"name": "voice-ai-development",
"description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...",
@@ -7975,7 +8119,7 @@
},
{
"id": "voice-ai-engine-development",
- "path": "skills/voice-ai-engine-development",
+ "path": "skills\\voice-ai-engine-development",
"category": "uncategorized",
"name": "voice-ai-engine-development",
"description": "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support",
@@ -7984,7 +8128,7 @@
},
{
"id": "vr-ar",
- "path": "skills/game-development/vr-ar",
+ "path": "skills\\game-development\\vr-ar",
"category": "game-development",
"name": "vr-ar",
"description": "VR/AR development principles. Comfort, interaction, performance requirements.",
@@ -7993,7 +8137,7 @@
},
{
"id": "vulnerability-scanner",
- "path": "skills/vulnerability-scanner",
+ "path": "skills\\vulnerability-scanner",
"category": "uncategorized",
"name": "vulnerability-scanner",
"description": "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.",
@@ -8002,7 +8146,7 @@
},
{
"id": "wcag-audit-patterns",
- "path": "skills/wcag-audit-patterns",
+ "path": "skills\\wcag-audit-patterns",
"category": "uncategorized",
"name": "wcag-audit-patterns",
"description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...",
@@ -8011,7 +8155,7 @@
},
{
"id": "web-artifacts-builder",
- "path": "skills/web-artifacts-builder",
+ "path": "skills\\web-artifacts-builder",
"category": "uncategorized",
"name": "web-artifacts-builder",
"description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma...",
@@ -8020,7 +8164,7 @@
},
{
"id": "web-design-guidelines",
- "path": "skills/web-design-guidelines",
+ "path": "skills\\web-design-guidelines",
"category": "uncategorized",
"name": "web-design-guidelines",
"description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga...",
@@ -8029,7 +8173,7 @@
},
{
"id": "web-games",
- "path": "skills/game-development/web-games",
+ "path": "skills\\game-development\\web-games",
"category": "game-development",
"name": "web-games",
"description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
@@ -8038,7 +8182,7 @@
},
{
"id": "web-performance-optimization",
- "path": "skills/web-performance-optimization",
+ "path": "skills\\web-performance-optimization",
"category": "uncategorized",
"name": "web-performance-optimization",
"description": "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance",
@@ -8047,7 +8191,7 @@
},
{
"id": "web-security-testing",
- "path": "skills/web-security-testing",
+ "path": "skills\\web-security-testing",
"category": "uncategorized",
"name": "web-security-testing",
"description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
@@ -8056,7 +8200,7 @@
},
{
"id": "web3-testing",
- "path": "skills/web3-testing",
+ "path": "skills\\web3-testing",
"category": "uncategorized",
"name": "web3-testing",
"description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va...",
@@ -8065,7 +8209,7 @@
},
{
"id": "webapp-testing",
- "path": "skills/webapp-testing",
+ "path": "skills\\webapp-testing",
"category": "uncategorized",
"name": "webapp-testing",
"description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...",
@@ -8074,7 +8218,7 @@
},
{
"id": "webflow-automation",
- "path": "skills/webflow-automation",
+ "path": "skills\\webflow-automation",
"category": "uncategorized",
"name": "webflow-automation",
"description": "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -8083,7 +8227,7 @@
},
{
"id": "whatsapp-automation",
- "path": "skills/whatsapp-automation",
+ "path": "skills\\whatsapp-automation",
"category": "uncategorized",
"name": "whatsapp-automation",
"description": "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.",
@@ -8092,7 +8236,7 @@
},
{
"id": "wiki-architect",
- "path": "skills/wiki-architect",
+ "path": "skills\\wiki-architect",
"category": "uncategorized",
"name": "wiki-architect",
"description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...",
@@ -8101,7 +8245,7 @@
},
{
"id": "wiki-changelog",
- "path": "skills/wiki-changelog",
+ "path": "skills\\wiki-changelog",
"category": "uncategorized",
"name": "wiki-changelog",
"description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...",
@@ -8110,7 +8254,7 @@
},
{
"id": "wiki-onboarding",
- "path": "skills/wiki-onboarding",
+ "path": "skills\\wiki-onboarding",
"category": "uncategorized",
"name": "wiki-onboarding",
"description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...",
@@ -8119,7 +8263,7 @@
},
{
"id": "wiki-page-writer",
- "path": "skills/wiki-page-writer",
+ "path": "skills\\wiki-page-writer",
"category": "uncategorized",
"name": "wiki-page-writer",
"description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...",
@@ -8128,7 +8272,7 @@
},
{
"id": "wiki-qa",
- "path": "skills/wiki-qa",
+ "path": "skills\\wiki-qa",
"category": "uncategorized",
"name": "wiki-qa",
"description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code...",
@@ -8137,7 +8281,7 @@
},
{
"id": "wiki-researcher",
- "path": "skills/wiki-researcher",
+ "path": "skills\\wiki-researcher",
"category": "uncategorized",
"name": "wiki-researcher",
"description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...",
@@ -8146,7 +8290,7 @@
},
{
"id": "wiki-vitepress",
- "path": "skills/wiki-vitepress",
+ "path": "skills\\wiki-vitepress",
"category": "uncategorized",
"name": "wiki-vitepress",
"description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...",
@@ -8155,7 +8299,7 @@
},
{
"id": "windows-privilege-escalation",
- "path": "skills/windows-privilege-escalation",
+ "path": "skills\\windows-privilege-escalation",
"category": "uncategorized",
"name": "windows-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon...",
@@ -8164,7 +8308,7 @@
},
{
"id": "wireshark-analysis",
- "path": "skills/wireshark-analysis",
+ "path": "skills\\wireshark-analysis",
"category": "uncategorized",
"name": "wireshark-analysis",
"description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete...",
@@ -8173,7 +8317,7 @@
},
{
"id": "wordpress",
- "path": "skills/wordpress",
+ "path": "skills\\wordpress",
"category": "uncategorized",
"name": "wordpress",
"description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
@@ -8182,7 +8326,7 @@
},
{
"id": "wordpress-penetration-testing",
- "path": "skills/wordpress-penetration-testing",
+ "path": "skills\\wordpress-penetration-testing",
"category": "uncategorized",
"name": "wordpress-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu...",
@@ -8191,7 +8335,7 @@
},
{
"id": "wordpress-plugin-development",
- "path": "skills/wordpress-plugin-development",
+ "path": "skills\\wordpress-plugin-development",
"category": "uncategorized",
"name": "wordpress-plugin-development",
"description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
@@ -8200,7 +8344,7 @@
},
{
"id": "wordpress-theme-development",
- "path": "skills/wordpress-theme-development",
+ "path": "skills\\wordpress-theme-development",
"category": "uncategorized",
"name": "wordpress-theme-development",
"description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
@@ -8209,25 +8353,16 @@
},
{
"id": "wordpress-woocommerce-development",
- "path": "skills/wordpress-woocommerce-development",
+ "path": "skills\\wordpress-woocommerce-development",
"category": "uncategorized",
"name": "wordpress-woocommerce-development",
"description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
"risk": "safe",
"source": "personal"
},
- {
- "id": "workflow-patterns",
- "path": "skills/workflow-patterns",
- "category": "uncategorized",
- "name": "Workflow Patterns",
- "description": "Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.",
- "risk": "unknown",
- "source": "unknown"
- },
{
"id": "workflow-automation",
- "path": "skills/workflow-automation",
+ "path": "skills\\workflow-automation",
"category": "uncategorized",
"name": "workflow-automation",
"description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor...",
@@ -8236,16 +8371,25 @@
},
{
"id": "workflow-orchestration-patterns",
- "path": "skills/workflow-orchestration-patterns",
+ "path": "skills\\workflow-orchestration-patterns",
"category": "uncategorized",
"name": "workflow-orchestration-patterns",
"description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ...",
"risk": "unknown",
"source": "community"
},
+ {
+ "id": "workflow-patterns",
+ "path": "skills\\workflow-patterns",
+ "category": "uncategorized",
+ "name": "workflow-patterns",
+ "description": "Use this skill when implementing tasks according to Conductor's TDD\nworkflow, handling phase checkpoints, managing git commits for tasks, or\nunderstanding the verification protocol.\n",
+ "risk": "unknown",
+ "source": "community"
+ },
{
"id": "wrike-automation",
- "path": "skills/wrike-automation",
+ "path": "skills\\wrike-automation",
"category": "uncategorized",
"name": "wrike-automation",
"description": "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.",
@@ -8254,7 +8398,7 @@
},
{
"id": "writer",
- "path": "skills/libreoffice/writer",
+ "path": "skills\\libreoffice\\writer",
"category": "libreoffice",
"name": "writer",
"description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
@@ -8263,7 +8407,7 @@
},
{
"id": "writing-plans",
- "path": "skills/writing-plans",
+ "path": "skills\\writing-plans",
"category": "uncategorized",
"name": "writing-plans",
"description": "Use when you have a spec or requirements for a multi-step task, before touching code",
@@ -8272,7 +8416,7 @@
},
{
"id": "writing-skills",
- "path": "skills/writing-skills",
+ "path": "skills\\writing-skills",
"category": "uncategorized",
"name": "writing-skills",
"description": "Use when creating, updating, or improving agent skills.",
@@ -8281,7 +8425,7 @@
},
{
"id": "x-article-publisher-skill",
- "path": "skills/x-article-publisher-skill",
+ "path": "skills\\x-article-publisher-skill",
"category": "uncategorized",
"name": "x-article-publisher-skill",
"description": "Publish articles to X/Twitter",
@@ -8290,7 +8434,7 @@
},
{
"id": "xlsx-official",
- "path": "skills/xlsx-official",
+ "path": "skills\\xlsx-official",
"category": "uncategorized",
"name": "xlsx-official",
"description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....",
@@ -8299,7 +8443,7 @@
},
{
"id": "xss-html-injection",
- "path": "skills/xss-html-injection",
+ "path": "skills\\xss-html-injection",
"category": "uncategorized",
"name": "xss-html-injection",
"description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection...",
@@ -8308,7 +8452,7 @@
},
{
"id": "youtube-automation",
- "path": "skills/youtube-automation",
+ "path": "skills\\youtube-automation",
"category": "uncategorized",
"name": "youtube-automation",
"description": "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.",
@@ -8317,7 +8461,7 @@
},
{
"id": "youtube-summarizer",
- "path": "skills/youtube-summarizer",
+ "path": "skills\\youtube-summarizer",
"category": "uncategorized",
"name": "youtube-summarizer",
"description": "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks",
@@ -8326,7 +8470,7 @@
},
{
"id": "zapier-make-patterns",
- "path": "skills/zapier-make-patterns",
+ "path": "skills\\zapier-make-patterns",
"category": "uncategorized",
"name": "zapier-make-patterns",
"description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...",
@@ -8335,7 +8479,7 @@
},
{
"id": "zendesk-automation",
- "path": "skills/zendesk-automation",
+ "path": "skills\\zendesk-automation",
"category": "uncategorized",
"name": "zendesk-automation",
"description": "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.",
@@ -8344,7 +8488,7 @@
},
{
"id": "zoho-crm-automation",
- "path": "skills/zoho-crm-automation",
+ "path": "skills\\zoho-crm-automation",
"category": "uncategorized",
"name": "zoho-crm-automation",
"description": "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.",
@@ -8353,7 +8497,7 @@
},
{
"id": "zoom-automation",
- "path": "skills/zoom-automation",
+ "path": "skills\\zoom-automation",
"category": "uncategorized",
"name": "zoom-automation",
"description": "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.",
@@ -8362,7 +8506,7 @@
},
{
"id": "zustand-store-ts",
- "path": "skills/zustand-store-ts",
+ "path": "skills\\zustand-store-ts",
"category": "uncategorized",
"name": "zustand-store-ts",
"description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...",
diff --git a/web-app/public/skills/00-andruia-consultant/SKILL.md b/web-app/public/skills/00-andruia-consultant/SKILL.md
new file mode 100644
index 00000000..c02b25e4
--- /dev/null
+++ b/web-app/public/skills/00-andruia-consultant/SKILL.md
@@ -0,0 +1,60 @@
+---
+id: 00-andruia-consultant
+name: 00-andruia-consultant
+description: "Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español."
+category: andruia
+risk: safe
+source: personal
+---
+
+## When to Use
+
+Use this skill at the very beginning of a project to diagnose the workspace, determine whether it's a "Pure Engine" (new) or "Evolution" (existing) project, and to set the initial technical roadmap and expert squad.
+
+# 🤖 Andru.ia Solutions Architect - Hybrid Engine (v2.0)
+
+## Description
+
+Soy el Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Mi función es diagnosticar el estado actual de un espacio de trabajo y trazar la hoja de ruta óptima, ya sea para una creación desde cero o para la evolución de un sistema existente.
+
+## 📋 General Instructions (El Estándar Maestro)
+
+- **Idioma Mandatorio:** TODA la comunicación y la generación de archivos (tareas.md, plan_implementacion.md) DEBEN ser en **ESPAÑOL**.
+- **Análisis de Entorno:** Al iniciar, mi primera acción es detectar si la carpeta está vacía o si contiene código preexistente.
+- **Persistencia:** Siempre materializo el diagnóstico en archivos .md locales.
+
+## 🛠️ Workflow: Bifurcación de Diagnóstico
+
+### ESCENARIO A: Lienzo Blanco (Carpeta Vacía)
+
+Si no detecto archivos, activo el protocolo **"Pure Engine"**:
+
+1. **Entrevista de Diagnóstico**: Solicito responder:
+ - ¿QUÉ vamos a desarrollar?
+ - ¿PARA QUIÉN es?
+ - ¿QUÉ RESULTADO esperas? (Objetivo y estética premium).
+
+### ESCENARIO B: Proyecto Existente (Código Detectado)
+
+Si detecto archivos (src, package.json, etc.), actúo como **Consultor de Evolución**:
+
+1. **Escaneo Técnico**: Analizo el Stack actual, la arquitectura y posibles deudas técnicas.
+2. **Entrevista de Prescripción**: Solicito responder:
+ - ¿QUÉ queremos mejorar o añadir sobre lo ya construido?
+ - ¿CUÁL es el mayor punto de dolor o limitación técnica actual?
+ - ¿A QUÉ estándar de calidad queremos elevar el proyecto?
+3. **Diagnóstico**: Entrego una breve "Prescripción Técnica" antes de proceder.
+
+## 🚀 Fase de Sincronización de Squad y Materialización
+
+Para ambos escenarios, tras recibir las respuestas:
+
+1. **Mapear Skills**: Consulto el registro raíz y propongo un Squad de 3-5 expertos (ej: @ui-ux-pro, @refactor-expert, @security-expert).
+2. **Generar Artefactos (En Español)**:
+ - `tareas.md`: Backlog detallado (de creación o de refactorización).
+ - `plan_implementacion.md`: Hoja de ruta técnica con el estándar de diamante.
+
+## ⚠️ Reglas de Oro
+
+1. **Contexto Inteligente**: No mezcles datos de proyectos anteriores. Cada carpeta es una entidad única.
+2. **Estándar de Diamante**: Prioriza siempre soluciones escalables, seguras y estéticamente superiores.
diff --git a/web-app/public/skills/10-andruia-skill-smith/SKILL.MD b/web-app/public/skills/10-andruia-skill-smith/SKILL.MD
new file mode 100644
index 00000000..9f4325d4
--- /dev/null
+++ b/web-app/public/skills/10-andruia-skill-smith/SKILL.MD
@@ -0,0 +1,41 @@
+---
+id: 10-andruia-skill-smith
+name: 10-andruia-skill-smith
+description: "Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante."
+category: andruia
+risk: official
+source: personal
+---
+
+# 🔨 Andru.ia Skill-Smith (The Forge)
+
+
+## 📝 Descripción
+Soy el Ingeniero de Sistemas de Andru.ia. Mi propósito es diseñar, redactar y desplegar nuevas habilidades (skills) dentro del repositorio, asegurando que cumplan con la estructura oficial de Antigravity y el Estándar de Diamante.
+
+## 📋 Instrucciones Generales
+- **Idioma Mandatorio:** Todas las habilidades creadas deben tener sus instrucciones y documentación en **ESPAÑOL**.
+- **Estructura Formal:** Debo seguir la anatomía de carpeta -> README.md -> Registro.
+- **Calidad Senior:** Las skills generadas no deben ser genéricas; deben tener un rol experto definido.
+
+## 🛠️ Flujo de Trabajo (Protocolo de Forja)
+
+### FASE 1: ADN de la Skill
+Solicitar al usuario los 3 pilares de la nueva habilidad:
+1. **Nombre Técnico:** (Ej: @cyber-sec, @data-visualizer).
+2. **Rol Experto:** (¿Quién es esta IA? Ej: "Un experto en auditoría de seguridad").
+3. **Outputs Clave:** (¿Qué archivos o acciones específicas debe realizar?).
+
+### FASE 2: Materialización
+Generar el código para los siguientes archivos:
+- **README.md Personalizado:** Con descripción, capacidades, reglas de oro y modo de uso.
+- **Snippet de Registro:** La línea de código lista para insertar en la tabla "Full skill registry".
+
+### FASE 3: Despliegue e Integración
+1. Crear la carpeta física en `D:\...\antigravity-awesome-skills\skills\`.
+2. Escribir el archivo README.md en dicha carpeta.
+3. Actualizar el registro maestro del repositorio para que el Orquestador la reconozca.
+
+## ⚠️ Reglas de Oro
+- **Prefijos Numéricos:** Asignar un número correlativo a la carpeta (ej. 11, 12, 13) para mantener el orden.
+- **Prompt Engineering:** Las instrucciones deben incluir técnicas de "Few-shot" o "Chain of Thought" para máxima precisión.
\ No newline at end of file
diff --git a/web-app/public/skills/20-andruia-niche-intelligence/SKILL.md b/web-app/public/skills/20-andruia-niche-intelligence/SKILL.md
new file mode 100644
index 00000000..9791b628
--- /dev/null
+++ b/web-app/public/skills/20-andruia-niche-intelligence/SKILL.md
@@ -0,0 +1,62 @@
+---
+id: 20-andruia-niche-intelligence
+name: 20-andruia-niche-intelligence
+description: "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho."
+category: andruia
+risk: safe
+source: personal
+---
+
+## When to Use
+
+Use this skill once the project's niche or industry has been identified. It is essential for injecting domain-specific intelligence, regulatory requirements, and industry-standard UX patterns into the project.
+
+# 🧠 Andru.ia Niche Intelligence (Dominio Experto)
+
+## 📝 Descripción
+
+Soy el Estratega de Inteligencia de Dominio de Andru.ia. Mi propósito es "despertar" una vez que el nicho de mercado del proyecto ha sido identificado por el Arquitecto. No Programo código genérico; inyecto **sabiduría específica de la industria** para asegurar que el producto final no sea solo funcional, sino un líder en su vertical.
+
+## 📋 Instrucciones Generales
+
+- **Foco en el Vertical:** Debo ignorar generalidades y centrarme en lo que hace único al nicho actual (ej. Fintech, EdTech, HealthTech, E-commerce, etc.).
+- **Idioma Mandatorio:** Toda la inteligencia generada debe ser en **ESPAÑOL**.
+- **Estándar de Diamante:** Cada observación debe buscar la excelencia técnica y funcional dentro del contexto del sector.
+
+## 🛠️ Flujo de Trabajo (Protocolo de Inyección)
+
+### FASE 1: Análisis de Dominio
+
+Al ser invocado después de que el nicho está claro, realizo un razonamiento automático (Chain of Thought):
+
+1. **Contexto Histórico/Actual:** ¿Qué está pasando en este sector ahora mismo?
+2. **Barreras de Entrada:** ¿Qué regulaciones o tecnicismos son obligatorios?
+3. **Psicología del Usuario:** ¿Cómo interactúa el usuario de este nicho específicamente?
+
+### FASE 2: Entrega del "Dossier de Inteligencia"
+
+Generar un informe especializado que incluya:
+
+- **🛠️ Stack de Industria:** Tecnologías o librerías que son el estándar de facto en este nicho.
+- **📜 Cumplimiento y Normativa:** Leyes o estándares necesarios (ej. RGPD, HIPAA, Facturación Electrónica DIAN, etc.).
+- **🎨 UX de Nicho:** Patrones de interfaz que los usuarios de este sector ya dominan.
+- **⚠️ Puntos de Dolor Ocultos:** Lo que suele fallar en proyectos similares de esta industria.
+
+## ⚠️ Reglas de Oro
+
+1. **Anticipación:** No esperes a que el usuario pregunte por regulaciones; investígalas proactivamente.
+2. **Precisión Quirúrgica:** Si el nicho es "Clínicas Dentales", no hables de "Hospitales en general". Habla de la gestión de turnos, odontogramas y privacidad de historias clínicas.
+3. **Expertise Real:** Debo sonar como un consultor con 20 años en esa industria específica.
+
+## 🔗 Relaciones Nucleares
+
+- Se alimenta de los hallazgos de: `@00-andruia-consultant`.
+- Proporciona las bases para: `@ui-ux-pro-max` y `@security-review`.
+
+## When to Use
+
+Activa este skill **después de que el nicho de mercado esté claro** y ya exista una visión inicial definida por `@00-andruia-consultant`:
+
+- Cuando quieras profundizar en regulaciones, estándares y patrones UX específicos de un sector concreto (Fintech, HealthTech, logística, etc.).
+- Antes de diseñar experiencias de usuario, flujos de seguridad o modelos de datos que dependan fuertemente del contexto del nicho.
+- Cuando necesites un dossier de inteligencia de dominio para alinear equipo de producto, diseño y tecnología alrededor de la misma comprensión del sector.
diff --git a/web-app/public/skills/agentfolio/SKILL.md b/web-app/public/skills/agentfolio/SKILL.md
new file mode 100644
index 00000000..3c6b8702
--- /dev/null
+++ b/web-app/public/skills/agentfolio/SKILL.md
@@ -0,0 +1,96 @@
+---
+name: agentfolio
+description: "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory."
+source: agentfolio.io
+risk: unknown
+---
+
+# AgentFolio
+
+**Role**: Autonomous Agent Discovery Guide
+
+Use this skill when you want to **discover, compare, and research autonomous AI agents** across ecosystems.
+AgentFolio is a curated directory at https://agentfolio.io that tracks agent frameworks, products, and tools.
+
+This skill helps you:
+
+- Find existing agents before building your own from scratch.
+- Map the landscape of agent frameworks and hosted products.
+- Collect concrete examples and benchmarks for agent capabilities.
+
+## Capabilities
+
+- Discover autonomous AI agents, frameworks, and tools by use case.
+- Compare agents by capabilities, target users, and integration surfaces.
+- Identify gaps in the market or inspiration for new skills/workflows.
+- Gather example agent behavior and UX patterns for your own designs.
+- Track emerging trends in agent architectures and deployments.
+
+## How to Use AgentFolio
+
+1. **Open the directory**
+ - Visit `https://agentfolio.io` in your browser.
+ - Optionally filter by category (e.g., Dev Tools, Ops, Marketing, Productivity).
+
+2. **Search by intent**
+ - Start from the problem you want to solve:
+ - “customer support agents”
+ - “autonomous coding agents”
+ - “research / analysis agents”
+ - Use keywords in the AgentFolio search bar that match your domain or workflow.
+
+3. **Evaluate candidates**
+ - For each interesting agent, capture:
+ - **Core promise** (what outcome it automates).
+ - **Input / output shape** (APIs, UI, data sources).
+ - **Autonomy model** (one-shot, multi-step, tool-using, human-in-the-loop).
+ - **Deployment model** (SaaS, self-hosted, browser, IDE, etc.).
+
+4. **Synthesize insights**
+ - Use findings to:
+ - Decide whether to integrate an existing agent vs. build your own.
+ - Borrow successful UX and safety patterns.
+ - Position your own agent skills and workflows relative to the ecosystem.
+
+## Example Workflows
+
+### 1) Landscape scan before building a new agent
+
+- Define the problem: “autonomous test failure triage for CI pipelines”.
+- Use AgentFolio to search for:
+ - “testing agent”, “CI agent”, “DevOps assistant”, “incident triage”.
+- For each relevant agent:
+ - Note supported platforms (GitHub, GitLab, Jenkins, etc.).
+ - Capture how they explain autonomy and safety boundaries.
+ - Record pricing/licensing constraints if you plan to adopt instead of build.
+
+### 2) Competitive and inspiration research for a new skill
+
+- If you plan to add a new skill (e.g., observability agent, security agent):
+ - Use AgentFolio to find similar agents and features.
+ - Extract 3–5 concrete patterns you want to emulate or avoid.
+ - Translate those patterns into clear requirements for your own skill.
+
+### 3) Vendor shortlisting
+
+- When choosing between multiple agent vendors:
+ - Use AgentFolio entries as a neutral directory.
+ - Build a comparison table (columns: capabilities, integrations, pricing, trust & security).
+ - Use that table to drive a more formal evaluation or proof-of-concept.
+
+## Example Prompts
+
+Use these prompts when working with this skill in an AI coding agent:
+
+- “Use AgentFolio to find 3 autonomous AI agents focused on code review. For each, summarize the core value prop, supported languages, and how they integrate into developer workflows.”
+- “Scan AgentFolio for agents that help with customer support triage. List the top options, their target customer size (SMB vs. enterprise), and any notable UX patterns.”
+- “Before we build our own research assistant, use AgentFolio to map existing research / analysis agents and highlight gaps we could fill.”
+
+## When to Use
+
+This skill is applicable when you need to **discover or compare autonomous AI agents** instead of building in a vacuum:
+
+- At the start of a new agent or workflow project.
+- When evaluating vendors or tools to integrate.
+- When you want inspiration or best practices from existing agent products.
+
diff --git a/web-app/public/skills/ai-engineer/SKILL.md b/web-app/public/skills/ai-engineer/SKILL.md
index 0f949484..ce392e7e 100644
--- a/web-app/public/skills/ai-engineer/SKILL.md
+++ b/web-app/public/skills/ai-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ai-engineer
-description: "Build production-ready LLM applications, advanced RAG systems, and"
+description: |
+ Build production-ready LLM applications, advanced RAG systems, and
intelligent agents. Implements vector search, multimodal AI, agent
orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM
features, chatbots, AI agents, or AI-powered applications.
@@ -9,6 +10,7 @@ metadata:
risk: unknown
source: community
---
+
You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.
## Use this skill when
@@ -37,11 +39,13 @@ You are an AI engineer specializing in production-grade LLM applications, genera
- Add guardrails for prompt injection, PII, and policy compliance.
## Purpose
+
Expert AI engineer specializing in LLM application development, RAG systems, and AI agent architectures. Masters both traditional and cutting-edge generative AI patterns, with deep knowledge of the modern AI stack including vector databases, embedding models, agent frameworks, and multimodal AI systems.
## Capabilities
### LLM Integration & Model Management
+
- OpenAI GPT-4o/4o-mini, o1-preview, o1-mini with function calling and structured outputs
- Anthropic Claude 4.5 Sonnet/Haiku, Claude 4.1 Opus with tool use and computer use
- Open-source models: Llama 3.1/3.2, Mixtral 8x7B/8x22B, Qwen 2.5, DeepSeek-V2
@@ -51,6 +55,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Cost optimization through model selection and caching strategies
### Advanced RAG Systems
+
- Production RAG architectures with multi-stage retrieval pipelines
- Vector databases: Pinecone, Qdrant, Weaviate, Chroma, Milvus, pgvector
- Embedding models: OpenAI text-embedding-3-large/small, Cohere embed-v3, BGE-large
@@ -62,6 +67,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Advanced RAG patterns: GraphRAG, HyDE, RAG-Fusion, self-RAG
### Agent Frameworks & Orchestration
+
- LangChain/LangGraph for complex agent workflows and state management
- LlamaIndex for data-centric AI applications and advanced retrieval
- CrewAI for multi-agent collaboration and specialized agent roles
@@ -72,6 +78,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Agent evaluation and monitoring with custom metrics
### Vector Search & Embeddings
+
- Embedding model selection and fine-tuning for domain-specific tasks
- Vector indexing strategies: HNSW, IVF, LSH for different scale requirements
- Similarity metrics: cosine, dot product, Euclidean for various use cases
@@ -80,6 +87,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Vector database optimization: indexing, sharding, and caching strategies
### Prompt Engineering & Optimization
+
- Advanced prompting techniques: chain-of-thought, tree-of-thoughts, self-consistency
- Few-shot and in-context learning optimization
- Prompt templates with dynamic variable injection and conditioning
@@ -89,6 +97,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Multi-modal prompting for vision and audio models
### Production AI Systems
+
- LLM serving with FastAPI, async processing, and load balancing
- Streaming responses and real-time inference optimization
- Caching strategies: semantic caching, response memoization, embedding caching
@@ -98,6 +107,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Observability: logging, metrics, tracing with LangSmith, Phoenix, Weights & Biases
### Multimodal AI Integration
+
- Vision models: GPT-4V, Claude 4 Vision, LLaVA, CLIP for image understanding
- Audio processing: Whisper for speech-to-text, ElevenLabs for text-to-speech
- Document AI: OCR, table extraction, layout understanding with models like LayoutLM
@@ -105,6 +115,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Cross-modal embeddings and unified vector spaces
### AI Safety & Governance
+
- Content moderation with OpenAI Moderation API and custom classifiers
- Prompt injection detection and prevention strategies
- PII detection and redaction in AI workflows
@@ -113,6 +124,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Responsible AI practices and ethical considerations
### Data Processing & Pipeline Management
+
- Document processing: PDF extraction, web scraping, API integrations
- Data preprocessing: cleaning, normalization, deduplication
- Pipeline orchestration with Apache Airflow, Dagster, Prefect
@@ -121,6 +133,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- ETL/ELT processes for AI data preparation
### Integration & API Development
+
- RESTful API design for AI services with FastAPI, Flask
- GraphQL APIs for flexible AI data querying
- Webhook integration and event-driven architectures
@@ -129,6 +142,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- API security: OAuth, JWT, API key management
## Behavioral Traits
+
- Prioritizes production reliability and scalability over proof-of-concept implementations
- Implements comprehensive error handling and graceful degradation
- Focuses on cost optimization and efficient resource utilization
@@ -141,6 +155,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Balances cutting-edge techniques with proven, stable solutions
## Knowledge Base
+
- Latest LLM developments and model capabilities (GPT-4o, Claude 4.5, Llama 3.2)
- Modern vector database architectures and optimization techniques
- Production AI system design patterns and best practices
@@ -153,6 +168,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
- Prompt engineering and optimization methodologies
## Response Approach
+
1. **Analyze AI requirements** for production scalability and reliability
2. **Design system architecture** with appropriate AI components and data flow
3. **Implement production-ready code** with comprehensive error handling
@@ -163,6 +179,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
8. **Provide testing strategies** including adversarial and edge cases
## Example Interactions
+
- "Build a production RAG system for enterprise knowledge base with hybrid search"
- "Implement a multi-agent customer service system with escalation workflows"
- "Design a cost-optimized LLM inference pipeline with caching and load balancing"
diff --git a/web-app/public/skills/analytics-tracking/SKILL.md b/web-app/public/skills/analytics-tracking/SKILL.md
index d25e5f1c..72bcbed0 100644
--- a/web-app/public/skills/analytics-tracking/SKILL.md
+++ b/web-app/public/skills/analytics-tracking/SKILL.md
@@ -1,6 +1,6 @@
---
name: analytics-tracking
-description: ">"
+description: >
Design, audit, and improve analytics tracking systems that produce reliable,
decision-ready data. Use when the user wants to set up, fix, or evaluate
analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs).
diff --git a/web-app/public/skills/angular/SKILL.md b/web-app/public/skills/angular/SKILL.md
index 964a8cc8..7352d107 100644
--- a/web-app/public/skills/angular/SKILL.md
+++ b/web-app/public/skills/angular/SKILL.md
@@ -1,6 +1,6 @@
---
name: angular
-description: ">-"
+description: >-
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone
Components, Zoneless applications, SSR/Hydration, and reactive patterns.
Use PROACTIVELY for Angular development, component architecture, state
diff --git a/web-app/public/skills/api-documenter/SKILL.md b/web-app/public/skills/api-documenter/SKILL.md
index aa613598..f3485bae 100644
--- a/web-app/public/skills/api-documenter/SKILL.md
+++ b/web-app/public/skills/api-documenter/SKILL.md
@@ -1,6 +1,7 @@
---
name: api-documenter
-description: "Master API documentation with OpenAPI 3.1, AI-powered tools, and"
+description: |
+ Master API documentation with OpenAPI 3.1, AI-powered tools, and
modern developer experience practices. Create interactive docs, generate SDKs,
and build comprehensive developer portals. Use PROACTIVELY for API
documentation or developer portal creation.
diff --git a/web-app/public/skills/appdeploy/SKILL.md b/web-app/public/skills/appdeploy/SKILL.md
new file mode 100644
index 00000000..069bb3c6
--- /dev/null
+++ b/web-app/public/skills/appdeploy/SKILL.md
@@ -0,0 +1,209 @@
+---
+name: appdeploy
+description: Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
+allowed-tools:
+ - Bash
+risk: safe
+source: AppDeploy (MIT)
+metadata:
+ author: appdeploy
+ version: "1.0.5"
+---
+
+# AppDeploy Skill
+
+Deploy web apps to AppDeploy via HTTP API.
+
+## When to Use This Skill
+
+- Use when planning or building apps and web apps
+- Use when deploying an app to a public URL
+- Use when publishing a website or web app
+- Use when the user says "deploy this", "make this live", or "give me a URL"
+- Use when updating an already-deployed app
+
+## Setup (First Time Only)
+
+1. **Check for existing API key:**
+ - Look for a `.appdeploy` file in the project root
+ - If it exists and contains a valid `api_key`, skip to Usage
+
+2. **If no API key exists, register and get one:**
+ ```bash
+ curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \
+ -H "Content-Type: application/json" \
+ -d '{"client_name": "claude-code"}'
+ ```
+
+ Response:
+ ```json
+ {
+ "api_key": "ak_...",
+ "user_id": "agent-claude-code-a1b2c3d4",
+ "created_at": 1234567890,
+ "message": "Save this key securely - it cannot be retrieved later"
+ }
+ ```
+
+3. **Save credentials to `.appdeploy`:**
+ ```json
+ {
+ "api_key": "ak_...",
+ "endpoint": "https://api-v2.appdeploy.ai/mcp"
+ }
+ ```
+
+ Add `.appdeploy` to `.gitignore` if not already present.
+
+## Usage
+
+Make JSON-RPC calls to the MCP endpoint:
+
+```bash
+curl -X POST {endpoint} \
+ -H "Content-Type: application/json" \
+ -H "Accept: application/json, text/event-stream" \
+ -H "Authorization: Bearer {api_key}" \
+ -d '{
+ "jsonrpc": "2.0",
+ "id": 1,
+ "method": "tools/call",
+ "params": {
+ "name": "{tool_name}",
+ "arguments": { ... }
+ }
+ }'
+```
+
+## Workflow
+
+1. **First, get deployment instructions:**
+ Call `get_deploy_instructions` to understand constraints and requirements.
+
+2. **Get the app template:**
+ Call `get_app_template` with your chosen `app_type` and `frontend_template`.
+
+3. **Deploy the app:**
+ Call `deploy_app` with your app files. For new apps, set `app_id` to `null`.
+
+4. **Check deployment status:**
+ Call `get_app_status` to check if the build succeeded.
+
+5. **View/manage your apps:**
+ Use `get_apps` to list your deployed apps.
+
+## Available Tools
+
+### get_deploy_instructions
+
+Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.
+
+**Parameters:**
+
+
+### deploy_app
+
+Use this when the user asks to deploy or publish a website or web app and wants a public URL.
+Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
+
+**Parameters:**
+ - `app_id`: any (required) - existing app id to update, or null for new app
+ - `app_type`: string (required) - app architecture: frontend-only or frontend+backend
+ - `app_name`: string (required) - short display name
+ - `description`: string (optional) - short description of what the app does
+ - `frontend_template`: any (optional) - REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included.
+ - `files`: array (optional) - Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required.
+ - `deletePaths`: array (optional) - Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points.
+ - `model`: string (required) - The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro'
+ - `intent`: string (required) - The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure'
+
+### get_app_template
+
+Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.
+
+**Parameters:**
+ - `app_type`: string (required)
+ - `frontend_template`: string (required) - Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG
+
+### get_app_status
+
+Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `since`: integer (optional) - Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.
+
+### delete_app
+
+Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+
+### get_app_versions
+
+List deployable versions for an existing app. Requires app_id. Returns newest-first {name, version, timestamp} items. Display 'name' to users. DO NOT display the 'version' value to users. Timestamp values MUST be converted to user's local time
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+
+### apply_app_version
+
+Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (required) - Version id to apply
+
+### src_glob
+
+Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to inspect (defaults to applied version)
+ - `path`: string (optional) - Directory path to search within
+ - `glob`: string (optional) - Glob pattern to match files (default: **/*)
+ - `include_dirs`: boolean (optional) - Include directory paths in results
+ - `continuation_token`: string (optional) - Token from previous response for pagination
+
+### src_grep
+
+Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to search (defaults to applied version)
+ - `pattern`: string (required) - Regex pattern to search for (max 500 chars)
+ - `path`: string (optional) - Directory path to search within
+ - `glob`: string (optional) - Glob pattern to filter files (e.g., '*.ts')
+ - `case_insensitive`: boolean (optional) - Enable case-insensitive matching
+ - `output_mode`: string (optional) - content=matching lines, files_with_matches=file paths only, count=match count per file
+ - `before_context`: integer (optional) - Lines to show before each match (0-20)
+ - `after_context`: integer (optional) - Lines to show after each match (0-20)
+ - `context`: integer (optional) - Lines before and after (overrides before/after_context)
+ - `line_numbers`: boolean (optional) - Include line numbers in output
+ - `max_file_size`: integer (optional) - Max file size to scan in bytes (default 10MB)
+ - `continuation_token`: string (optional) - Token from previous response for pagination
+
+### src_read
+
+Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.
+
+**Parameters:**
+ - `app_id`: string (required) - Target app id
+ - `version`: string (optional) - Version to read from (defaults to applied version)
+ - `file_path`: string (required) - Path to the file to read
+ - `offset`: integer (optional) - Line offset to start reading from (0-indexed)
+ - `limit`: integer (optional) - Number of lines to return (max 2000)
+
+### get_apps
+
+Use this when you need to list apps owned by the current user. Returns app details with display fields for user presentation and data fields for tool chaining.
+
+**Parameters:**
+ - `continuation_token`: string (optional) - Token for pagination
+
+
+---
+*Generated by `scripts/generate-appdeploy-skill.ts`*
diff --git a/web-app/public/skills/arm-cortex-expert/SKILL.md b/web-app/public/skills/arm-cortex-expert/SKILL.md
index 0512c5b9..ddc16100 100644
--- a/web-app/public/skills/arm-cortex-expert/SKILL.md
+++ b/web-app/public/skills/arm-cortex-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: arm-cortex-expert
-description: ">"
+description: >
Senior embedded software engineer specializing in firmware and driver
development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
Decades of experience writing reliable, optimized, and maintainable embedded
diff --git a/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md b/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
index 3979d282..f8fdb292 100644
--- a/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-agents-persistent-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-agents-persistent-dotnet
-description: "|"
+description: |
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
package: Azure.AI.Agents.Persistent
risk: unknown
diff --git a/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md b/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
index 9c34fc37..fcd77b71 100644
--- a/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-agents-persistent-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-agents-persistent-java
-description: "|"
+description: |
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.
Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".
package: com.azure:azure-ai-agents-persistent
diff --git a/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md b/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
index 672acfbc..104f011e 100644
--- a/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentsafety-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-contentsafety-py
-description: "|"
+description: |
Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.
Triggers: "azure-ai-contentsafety", "ContentSafetyClient", "content moderation", "harmful content", "text analysis", "image analysis".
package: azure-ai-contentsafety
diff --git a/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md b/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
index d6936e74..ba4614ec 100644
--- a/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-contentunderstanding-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-contentunderstanding-py
-description: "|"
+description: |
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
Triggers: "azure-ai-contentunderstanding", "ContentUnderstandingClient", "multimodal analysis", "document extraction", "video analysis", "audio transcription".
package: azure-ai-contentunderstanding
diff --git a/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md b/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
index bf04b40f..29e9c380 100644
--- a/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-document-intelligence-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-document-intelligence-dotnet
-description: "|"
+description: |
Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: "Document Intelligence", "DocumentIntelligenceClient", "form recognizer", "invoice extraction", "receipt OCR", "document analysis .NET".
package: Azure.AI.DocumentIntelligence
risk: unknown
diff --git a/web-app/public/skills/azure-ai-ml-py/SKILL.md b/web-app/public/skills/azure-ai-ml-py/SKILL.md
index d3edddb1..9e22c8d8 100644
--- a/web-app/public/skills/azure-ai-ml-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-ml-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-ml-py
-description: "|"
+description: |
Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.
Triggers: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
package: azure-ai-ml
diff --git a/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md b/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
index 97437f44..2f52ef0b 100644
--- a/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-openai-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-openai-dotnet
-description: "|"
+description: |
Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: "Azure OpenAI", "AzureOpenAIClient", "ChatClient", "chat completions .NET", "GPT-4", "embeddings", "DALL-E", "Whisper", "OpenAI .NET".
package: Azure.AI.OpenAI
risk: unknown
diff --git a/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md b/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
index e9199ef3..bcc7e4d5 100644
--- a/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-projects-dotnet
-description: "|"
+description: |
Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents", "evaluations", "datasets", "connections", "deployments .NET".
package: Azure.AI.Projects
risk: unknown
diff --git a/web-app/public/skills/azure-ai-projects-java/SKILL.md b/web-app/public/skills/azure-ai-projects-java/SKILL.md
index 1e4b9167..3ac3ff82 100644
--- a/web-app/public/skills/azure-ai-projects-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-projects-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-projects-java
-description: "|"
+description: |
Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.
Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".
package: com.azure:azure-ai-projects
diff --git a/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md b/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
index ae54fb5c..e9ef631d 100644
--- a/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-textanalytics-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-textanalytics-py
-description: "|"
+description: |
Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.
Triggers: "text analytics", "sentiment analysis", "entity recognition", "key phrase", "PII detection", "TextAnalyticsClient".
package: azure-ai-textanalytics
diff --git a/web-app/public/skills/azure-ai-transcription-py/SKILL.md b/web-app/public/skills/azure-ai-transcription-py/SKILL.md
index 216c20b0..f0ca97c9 100644
--- a/web-app/public/skills/azure-ai-transcription-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-transcription-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-transcription-py
-description: "|"
+description: |
Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.
Triggers: "transcription", "speech to text", "Azure AI Transcription", "TranscriptionClient".
package: azure-ai-transcription
diff --git a/web-app/public/skills/azure-ai-translation-document-py/SKILL.md b/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
index c7e1ee0f..9183d0fc 100644
--- a/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-translation-document-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-translation-document-py
-description: "|"
+description: |
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
package: azure-ai-translation-document
diff --git a/web-app/public/skills/azure-ai-translation-text-py/SKILL.md b/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
index 7bf2779b..ca2f411b 100644
--- a/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-translation-text-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-translation-text-py
-description: "|"
+description: |
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.
Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
package: azure-ai-translation-text
diff --git a/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md b/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
index 572781cb..bb773c21 100644
--- a/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
+++ b/web-app/public/skills/azure-ai-vision-imageanalysis-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-vision-imageanalysis-py
-description: "|"
+description: |
Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.
Triggers: "image analysis", "computer vision", "OCR", "object detection", "ImageAnalysisClient", "image caption".
package: azure-ai-vision-imageanalysis
diff --git a/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md b/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
index e52481a5..9db74f00 100644
--- a/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-dotnet
-description: "|"
+description: |
Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant .NET", "bidirectional audio", "speech-to-speech".
package: Azure.AI.VoiceLive
risk: unknown
diff --git a/web-app/public/skills/azure-ai-voicelive-java/SKILL.md b/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
index 9c3e1306..505a48ee 100644
--- a/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-java
-description: "|"
+description: |
Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.
Triggers: "VoiceLiveClient java", "voice assistant java", "real-time voice java", "audio streaming java", "voice activity detection java".
package: com.azure:azure-ai-voicelive
diff --git a/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md b/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
index 5e13f368..25ab69c3 100644
--- a/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
+++ b/web-app/public/skills/azure-ai-voicelive-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-ai-voicelive-ts
-description: "|"
+description: |
Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant TypeScript", "bidirectional audio", "speech-to-speech JavaScript".
package: "@azure/ai-voicelive"
risk: unknown
diff --git a/web-app/public/skills/azure-appconfiguration-java/SKILL.md b/web-app/public/skills/azure-appconfiguration-java/SKILL.md
index e4560c24..5b0bc039 100644
--- a/web-app/public/skills/azure-appconfiguration-java/SKILL.md
+++ b/web-app/public/skills/azure-appconfiguration-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-appconfiguration-java
-description: "|"
+description: |
Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.
Triggers: "ConfigurationClient java", "app configuration java", "feature flag java", "configuration setting java", "azure config java".
package: com.azure:azure-data-appconfiguration
diff --git a/web-app/public/skills/azure-appconfiguration-py/SKILL.md b/web-app/public/skills/azure-appconfiguration-py/SKILL.md
index c1da4e42..d02fbeef 100644
--- a/web-app/public/skills/azure-appconfiguration-py/SKILL.md
+++ b/web-app/public/skills/azure-appconfiguration-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-appconfiguration-py
-description: "|"
+description: |
Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.
Triggers: "azure-appconfiguration", "AzureAppConfigurationClient", "feature flags", "configuration", "key-value settings".
package: azure-appconfiguration
diff --git a/web-app/public/skills/azure-compute-batch-java/SKILL.md b/web-app/public/skills/azure-compute-batch-java/SKILL.md
index 993554e9..8da9c747 100644
--- a/web-app/public/skills/azure-compute-batch-java/SKILL.md
+++ b/web-app/public/skills/azure-compute-batch-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-compute-batch-java
-description: "|"
+description: |
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
Triggers: "BatchClient java", "azure batch java", "batch pool java", "batch job java", "HPC java", "parallel computing java".
risk: unknown
diff --git a/web-app/public/skills/azure-containerregistry-py/SKILL.md b/web-app/public/skills/azure-containerregistry-py/SKILL.md
index 76f76a65..aa2f6aee 100644
--- a/web-app/public/skills/azure-containerregistry-py/SKILL.md
+++ b/web-app/public/skills/azure-containerregistry-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-containerregistry-py
-description: "|"
+description: |
Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".
package: azure-containerregistry
diff --git a/web-app/public/skills/azure-cosmos-java/SKILL.md b/web-app/public/skills/azure-cosmos-java/SKILL.md
index d71dfa6d..e8dccae8 100644
--- a/web-app/public/skills/azure-cosmos-java/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-java
-description: "|"
+description: |
Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.
Triggers: "CosmosClient java", "CosmosAsyncClient", "cosmos database java", "cosmosdb java", "document database java".
package: azure-cosmos
diff --git a/web-app/public/skills/azure-cosmos-py/SKILL.md b/web-app/public/skills/azure-cosmos-py/SKILL.md
index 11903d99..90e86b4a 100644
--- a/web-app/public/skills/azure-cosmos-py/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-py
-description: "|"
+description: |
Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db", "CosmosClient", "container", "document", "NoSQL", "partition key".
package: azure-cosmos
diff --git a/web-app/public/skills/azure-cosmos-rust/SKILL.md b/web-app/public/skills/azure-cosmos-rust/SKILL.md
index d8e3ad7a..ec7387aa 100644
--- a/web-app/public/skills/azure-cosmos-rust/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-rust
-description: "|"
+description: |
Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
Triggers: "cosmos db rust", "CosmosClient rust", "container", "document rust", "NoSQL rust", "partition key".
package: azure_data_cosmos
diff --git a/web-app/public/skills/azure-cosmos-ts/SKILL.md b/web-app/public/skills/azure-cosmos-ts/SKILL.md
index a6a2a5cf..d09d11a2 100644
--- a/web-app/public/skills/azure-cosmos-ts/SKILL.md
+++ b/web-app/public/skills/azure-cosmos-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-cosmos-ts
-description: "|"
+description: |
Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: "Cosmos DB", "@azure/cosmos", "CosmosClient", "document CRUD", "NoSQL queries", "bulk operations", "partition key", "container.items".
package: "@azure/cosmos"
risk: unknown
diff --git a/web-app/public/skills/azure-data-tables-py/SKILL.md b/web-app/public/skills/azure-data-tables-py/SKILL.md
index 7abbdcd5..6fedc112 100644
--- a/web-app/public/skills/azure-data-tables-py/SKILL.md
+++ b/web-app/public/skills/azure-data-tables-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-data-tables-py
-description: "|"
+description: |
Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.
Triggers: "table storage", "TableServiceClient", "TableClient", "entities", "PartitionKey", "RowKey".
package: azure-data-tables
diff --git a/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md b/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
index 0f180e9c..3fca07ca 100644
--- a/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-eventgrid-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventgrid-dotnet
-description: "|"
+description: |
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven", "pub/sub".
package: Azure.Messaging.EventGrid
risk: unknown
diff --git a/web-app/public/skills/azure-eventgrid-py/SKILL.md b/web-app/public/skills/azure-eventgrid-py/SKILL.md
index ddfe5c1f..bb801f99 100644
--- a/web-app/public/skills/azure-eventgrid-py/SKILL.md
+++ b/web-app/public/skills/azure-eventgrid-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventgrid-py
-description: "|"
+description: |
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
Triggers: "event grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events".
package: azure-eventgrid
diff --git a/web-app/public/skills/azure-eventhub-dotnet/SKILL.md b/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
index 1ba7c843..06cf909e 100644
--- a/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-dotnet
-description: "|"
+description: |
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming", "EventHubProducerClient", "EventProcessorClient", "send events", "receive events", "checkpointing", "partition".
package: Azure.Messaging.EventHubs
risk: unknown
diff --git a/web-app/public/skills/azure-eventhub-py/SKILL.md b/web-app/public/skills/azure-eventhub-py/SKILL.md
index 3914b7c8..82da2387 100644
--- a/web-app/public/skills/azure-eventhub-py/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-py
-description: "|"
+description: |
Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.
Triggers: "event hubs", "EventHubProducerClient", "EventHubConsumerClient", "streaming", "partitions".
package: azure-eventhub
diff --git a/web-app/public/skills/azure-eventhub-rust/SKILL.md b/web-app/public/skills/azure-eventhub-rust/SKILL.md
index 702cc64e..2477807e 100644
--- a/web-app/public/skills/azure-eventhub-rust/SKILL.md
+++ b/web-app/public/skills/azure-eventhub-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-eventhub-rust
-description: "|"
+description: |
Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.
Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust".
package: azure_messaging_eventhubs
diff --git a/web-app/public/skills/azure-identity-dotnet/SKILL.md b/web-app/public/skills/azure-identity-dotnet/SKILL.md
index d8e4b54e..c3be00b7 100644
--- a/web-app/public/skills/azure-identity-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-identity-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-dotnet
-description: "|"
+description: |
Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: "Azure Identity", "DefaultAzureCredential", "ManagedIdentityCredential", "ClientSecretCredential", "authentication .NET", "Azure auth", "credential chain".
package: Azure.Identity
risk: unknown
diff --git a/web-app/public/skills/azure-identity-py/SKILL.md b/web-app/public/skills/azure-identity-py/SKILL.md
index 88555e3c..c55dad89 100644
--- a/web-app/public/skills/azure-identity-py/SKILL.md
+++ b/web-app/public/skills/azure-identity-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-py
-description: "|"
+description: |
Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.
Triggers: "azure-identity", "DefaultAzureCredential", "authentication", "managed identity", "service principal", "credential".
package: azure-identity
diff --git a/web-app/public/skills/azure-identity-rust/SKILL.md b/web-app/public/skills/azure-identity-rust/SKILL.md
index 8ed389ce..c2583c0f 100644
--- a/web-app/public/skills/azure-identity-rust/SKILL.md
+++ b/web-app/public/skills/azure-identity-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-identity-rust
-description: "|"
+description: |
Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.
Triggers: "azure-identity", "DeveloperToolsCredential", "authentication rust", "managed identity rust", "credential rust".
package: azure_identity
diff --git a/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md b/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
index 60452370..b46965d4 100644
--- a/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-certificates-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-certificates-rust
-description: "|"
+description: |
Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.
Triggers: "keyvault certificates rust", "CertificateClient rust", "create certificate rust", "import certificate rust".
package: azure_security_keyvault_certificates
diff --git a/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md b/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
index c88a11e3..516fadcb 100644
--- a/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-keys-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-keys-rust
-description: "|"
+description: |
Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.
Triggers: "keyvault keys rust", "KeyClient rust", "create key rust", "encrypt rust", "sign rust".
package: azure_security_keyvault_keys
diff --git a/web-app/public/skills/azure-keyvault-py/SKILL.md b/web-app/public/skills/azure-keyvault-py/SKILL.md
index 0709c5fa..ac389a32 100644
--- a/web-app/public/skills/azure-keyvault-py/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-py
-description: "|"
+description: |
Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.
Triggers: "key vault", "SecretClient", "KeyClient", "CertificateClient", "secrets", "encryption keys".
package: azure-keyvault-secrets, azure-keyvault-keys, azure-keyvault-certificates
diff --git a/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md b/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
index af92fbd3..30422f93 100644
--- a/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
+++ b/web-app/public/skills/azure-keyvault-secrets-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-keyvault-secrets-rust
-description: "|"
+description: |
Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.
Triggers: "keyvault secrets rust", "SecretClient rust", "get secret rust", "set secret rust".
package: azure_security_keyvault_secrets
diff --git a/web-app/public/skills/azure-maps-search-dotnet/SKILL.md b/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
index 7fd23ea8..5688d5a1 100644
--- a/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-maps-search-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-maps-search-dotnet
-description: "|"
+description: |
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route directions", "map tiles", "geolocation".
package: Azure.Maps.Search
risk: unknown
diff --git a/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md b/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
index e0c1f565..b3a686c8 100644
--- a/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
+++ b/web-app/public/skills/azure-messaging-webpubsubservice-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-messaging-webpubsubservice-py
-description: "|"
+description: |
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.
Triggers: "azure-messaging-webpubsubservice", "WebPubSubServiceClient", "real-time", "WebSocket", "pub/sub".
package: azure-messaging-webpubsubservice
diff --git a/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
index e5052bb2..cfa82d7b 100644
--- a/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apicenter-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apicenter-dotnet
-description: "|"
+description: |
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API inventory", "API governance", "API versioning", "API catalog", "API discovery".
package: Azure.ResourceManager.ApiCenter
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md b/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
index 2a07de6d..6b0a39dc 100644
--- a/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apicenter-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apicenter-py
-description: "|"
+description: |
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
Triggers: "azure-mgmt-apicenter", "ApiCenterMgmtClient", "API Center", "API inventory", "API governance".
package: azure-mgmt-apicenter
diff --git a/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
index 19df092d..73fe5274 100644
--- a/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apimanagement-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: "API Management", "APIM service", "create APIM", "manage APIs", "ApiManagementServiceResource", "API policies", "APIM products", "APIM subscriptions".
package: Azure.ResourceManager.ApiManagement
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md b/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
index 64d63bd0..b0d4dcbc 100644
--- a/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-apimanagement-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-apimanagement-py
-description: "|"
+description: |
Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.
Triggers: "azure-mgmt-apimanagement", "ApiManagementClient", "APIM", "API gateway", "API Management".
package: azure-mgmt-apimanagement
diff --git a/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
index d94beffc..d9a0482f 100644
--- a/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-applicationinsights-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-applicationinsights-dotnet
-description: "|"
+description: |
Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: "Application Insights", "ApplicationInsights", "App Insights", "APM", "application monitoring", "web tests", "availability tests", "workbooks".
package: Azure.ResourceManager.ApplicationInsights
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
index 4330e176..b8c213df 100644
--- a/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-arizeaiobservabilityeval-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations
on Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability
into .NET applications. Triggers: "Arize AI", "ML observability", "ArizeAIObservabilityEval", "Arize organization".
diff --git a/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
index 94d8824f..56bbcabd 100644
--- a/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-botservice-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-botservice-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
package: Azure.ResourceManager.BotService
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md b/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
index c6b851be..b954c17f 100644
--- a/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-botservice-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-botservice-py
-description: "|"
+description: |
Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.
Triggers: "azure-mgmt-botservice", "AzureBotService", "bot management", "conversational AI", "bot channels".
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
index 9721d0dd..6076541f 100644
--- a/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-fabric-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-fabric-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity", "Fabric SKU", "provision Fabric", "ARM Fabric", "FabricCapacityResource".
package: Azure.ResourceManager.Fabric
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md b/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
index 2e2ff79b..e4c78ea3 100644
--- a/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-fabric-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-fabric-py
-description: "|"
+description: |
Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.
Triggers: "azure-mgmt-fabric", "FabricMgmtClient", "Fabric capacity", "Microsoft Fabric", "Power BI capacity".
risk: unknown
diff --git a/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md b/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
index c08a2fd3..ece97788 100644
--- a/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-mgmt-weightsandbiases-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-mgmt-weightsandbiases-dotnet
-description: "|"
+description: |
Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: "Weights and Biases", "W&B", "WeightsAndBiases", "ML experiment tracking", "model registry", "experiment management", "wandb".
package: Azure.ResourceManager.WeightsAndBiases
risk: unknown
diff --git a/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md b/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
index a288b279..dbba70cc 100644
--- a/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-ingestion-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-ingestion-java
-description: "|"
+description: |
Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).
Triggers: "LogsIngestionClient java", "azure monitor ingestion java", "custom logs java", "DCR java", "data collection rule java".
package: com.azure:azure-monitor-ingestion
diff --git a/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md b/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
index c14e9c95..cff95c04 100644
--- a/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-ingestion-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-ingestion-py
-description: "|"
+description: |
Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.
Triggers: "azure-monitor-ingestion", "LogsIngestionClient", "custom logs", "DCR", "data collection rule", "Log Analytics".
package: azure-monitor-ingestion
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
index 5cbddf1d..275c343c 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-exporter-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-exporter-java
-description: "|"
+description: |
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.
Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java".
Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
index b78077e4..3218be18 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-exporter-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-exporter-py
-description: "|"
+description: |
Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.
Triggers: "azure-monitor-opentelemetry-exporter", "AzureMonitorTraceExporter", "AzureMonitorMetricExporter", "AzureMonitorLogExporter".
package: azure-monitor-opentelemetry-exporter
diff --git a/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md b/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
index 93739fcf..b9f55503 100644
--- a/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-opentelemetry-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-opentelemetry-py
-description: "|"
+description: |
Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.
Triggers: "azure-monitor-opentelemetry", "configure_azure_monitor", "Application Insights", "OpenTelemetry distro", "auto-instrumentation".
package: azure-monitor-opentelemetry
diff --git a/web-app/public/skills/azure-monitor-query-java/SKILL.md b/web-app/public/skills/azure-monitor-query-java/SKILL.md
index f03398d1..02db8627 100644
--- a/web-app/public/skills/azure-monitor-query-java/SKILL.md
+++ b/web-app/public/skills/azure-monitor-query-java/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-query-java
-description: "|"
+description: |
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
Triggers: "LogsQueryClient java", "MetricsQueryClient java", "kusto query java", "log analytics java", "azure monitor query java".
Note: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.
diff --git a/web-app/public/skills/azure-monitor-query-py/SKILL.md b/web-app/public/skills/azure-monitor-query-py/SKILL.md
index 44c5028e..36fa0a65 100644
--- a/web-app/public/skills/azure-monitor-query-py/SKILL.md
+++ b/web-app/public/skills/azure-monitor-query-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-monitor-query-py
-description: "|"
+description: |
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
Triggers: "azure-monitor-query", "LogsQueryClient", "MetricsQueryClient", "Log Analytics", "Kusto queries", "Azure metrics".
package: azure-monitor-query
diff --git a/web-app/public/skills/azure-postgres-ts/SKILL.md b/web-app/public/skills/azure-postgres-ts/SKILL.md
index 23ebed5f..76f2adff 100644
--- a/web-app/public/skills/azure-postgres-ts/SKILL.md
+++ b/web-app/public/skills/azure-postgres-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-postgres-ts
-description: "|"
+description: |
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL connection", "PostgreSQL TypeScript", "pg Pool", "passwordless postgres".
package: pg
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
index b5a1633e..d525cc85 100644
--- a/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-cosmosdb-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: "Cosmos DB account", "create Cosmos account", "manage Cosmos resources", "ARM Cosmos", "CosmosDBAccountResource", "provision Cosmos DB".
package: Azure.ResourceManager.CosmosDB
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
index 40f79c81..0aaff756 100644
--- a/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-durabletask-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-durabletask-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision Durable Task", "orchestration scheduler".
package: Azure.ResourceManager.DurableTask
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
index 6a5140d9..20ae4466 100644
--- a/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-mysql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-mysql-dotnet
-description: "|"
+description: |
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database management", "MySQL firewall", "MySQL backup".
package: Azure.ResourceManager.MySql
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
index ad780184..afb448fc 100644
--- a/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-playwright-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-playwright-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
package: Azure.ResourceManager.Playwright
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
index c3cefe84..f8319426 100644
--- a/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-postgresql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-postgresql-dotnet
-description: "|"
+description: |
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
package: Azure.ResourceManager.PostgreSql
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
index 96175c18..7fa278b1 100644
--- a/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-redis-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-redis-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".
package: Azure.ResourceManager.Redis
risk: unknown
diff --git a/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md b/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
index 0f98adf5..3da3fa13 100644
--- a/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-resource-manager-sql-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-resource-manager-sql-dotnet
-description: "|"
+description: |
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
package: Azure.ResourceManager.Sql
risk: unknown
diff --git a/web-app/public/skills/azure-search-documents-dotnet/SKILL.md b/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
index 954fad18..d3d61d12 100644
--- a/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-search-documents-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-search-documents-dotnet
-description: "|"
+description: |
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET", "SearchClient", "SearchIndexClient", "vector search C#", "semantic search .NET", "hybrid search", "Azure.Search.Documents".
package: Azure.Search.Documents
risk: unknown
diff --git a/web-app/public/skills/azure-search-documents-py/SKILL.md b/web-app/public/skills/azure-search-documents-py/SKILL.md
index a481063b..a759bdef 100644
--- a/web-app/public/skills/azure-search-documents-py/SKILL.md
+++ b/web-app/public/skills/azure-search-documents-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-search-documents-py
-description: "|"
+description: |
Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.
Triggers: "azure-search-documents", "SearchClient", "SearchIndexClient", "vector search", "hybrid search", "semantic search".
package: azure-search-documents
diff --git a/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md b/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
index ba20d0e2..68d1266c 100644
--- a/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-security-keyvault-keys-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-security-keyvault-keys-dotnet
-description: "|"
+description: |
Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: "Key Vault keys", "KeyClient", "CryptographyClient", "RSA key", "EC key", "encrypt decrypt .NET", "key rotation", "HSM".
package: Azure.Security.KeyVault.Keys
risk: unknown
diff --git a/web-app/public/skills/azure-servicebus-dotnet/SKILL.md b/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
index 22fb9891..f35c51bb 100644
--- a/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
+++ b/web-app/public/skills/azure-servicebus-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-servicebus-dotnet
-description: "|"
+description: |
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
package: Azure.Messaging.ServiceBus
risk: unknown
diff --git a/web-app/public/skills/azure-servicebus-py/SKILL.md b/web-app/public/skills/azure-servicebus-py/SKILL.md
index 6e82b598..48e59609 100644
--- a/web-app/public/skills/azure-servicebus-py/SKILL.md
+++ b/web-app/public/skills/azure-servicebus-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-servicebus-py
-description: "|"
+description: |
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
Triggers: "service bus", "ServiceBusClient", "queue", "topic", "subscription", "message broker".
package: azure-servicebus
diff --git a/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md b/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
index a9781432..e1f7de6d 100644
--- a/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
+++ b/web-app/public/skills/azure-speech-to-text-rest-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-speech-to-text-rest-py
-description: "|"
+description: |
Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.
Triggers: "speech to text REST", "short audio transcription", "speech recognition REST API", "STT REST", "recognize speech REST".
DO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.
diff --git a/web-app/public/skills/azure-storage-blob-py/SKILL.md b/web-app/public/skills/azure-storage-blob-py/SKILL.md
index 6ebe6b36..f97d7347 100644
--- a/web-app/public/skills/azure-storage-blob-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-py
-description: "|"
+description: |
Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.
Triggers: "blob storage", "BlobServiceClient", "ContainerClient", "BlobClient", "upload blob", "download blob".
package: azure-storage-blob
diff --git a/web-app/public/skills/azure-storage-blob-rust/SKILL.md b/web-app/public/skills/azure-storage-blob-rust/SKILL.md
index 2b43e56b..26d565e6 100644
--- a/web-app/public/skills/azure-storage-blob-rust/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-rust/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-rust
-description: "|"
+description: |
Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.
Triggers: "blob storage rust", "BlobClient rust", "upload blob rust", "download blob rust", "container rust".
package: azure_storage_blob
diff --git a/web-app/public/skills/azure-storage-blob-ts/SKILL.md b/web-app/public/skills/azure-storage-blob-ts/SKILL.md
index f941ba21..c5450d8c 100644
--- a/web-app/public/skills/azure-storage-blob-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-blob-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-blob-ts
-description: "|"
+description: |
Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: "blob storage", "@azure/storage-blob", "BlobServiceClient", "ContainerClient", "upload blob", "download blob", "SAS token", "block blob".
package: "@azure/storage-blob"
risk: unknown
diff --git a/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md b/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
index 05c70fd8..585c9cbe 100644
--- a/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-datalake-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-datalake-py
-description: "|"
+description: |
Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.
Triggers: "data lake", "DataLakeServiceClient", "FileSystemClient", "ADLS Gen2", "hierarchical namespace".
package: azure-storage-file-datalake
diff --git a/web-app/public/skills/azure-storage-file-share-py/SKILL.md b/web-app/public/skills/azure-storage-file-share-py/SKILL.md
index 2889a9ff..676952c1 100644
--- a/web-app/public/skills/azure-storage-file-share-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-share-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-share-py
-description: "|"
+description: |
Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.
Triggers: "azure-storage-file-share", "ShareServiceClient", "ShareClient", "file share", "SMB".
risk: unknown
diff --git a/web-app/public/skills/azure-storage-file-share-ts/SKILL.md b/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
index 6e9bae7f..c6c0f24a 100644
--- a/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-file-share-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-file-share-ts
-description: "|"
+description: |
Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: "file share", "@azure/storage-file-share", "ShareServiceClient", "ShareClient", "SMB", "Azure Files".
package: "@azure/storage-file-share"
risk: unknown
diff --git a/web-app/public/skills/azure-storage-queue-py/SKILL.md b/web-app/public/skills/azure-storage-queue-py/SKILL.md
index 38c91d03..39b4a270 100644
--- a/web-app/public/skills/azure-storage-queue-py/SKILL.md
+++ b/web-app/public/skills/azure-storage-queue-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-queue-py
-description: "|"
+description: |
Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.
Triggers: "queue storage", "QueueServiceClient", "QueueClient", "message queue", "dequeue".
package: azure-storage-queue
diff --git a/web-app/public/skills/azure-storage-queue-ts/SKILL.md b/web-app/public/skills/azure-storage-queue-ts/SKILL.md
index d06d259f..244a5051 100644
--- a/web-app/public/skills/azure-storage-queue-ts/SKILL.md
+++ b/web-app/public/skills/azure-storage-queue-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: azure-storage-queue-ts
-description: "|"
+description: |
Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: "queue storage", "@azure/storage-queue", "QueueServiceClient", "QueueClient", "send message", "receive message", "dequeue", "visibility timeout".
package: "@azure/storage-queue"
risk: unknown
diff --git a/web-app/public/skills/backend-architect/SKILL.md b/web-app/public/skills/backend-architect/SKILL.md
index e2283367..c5eba207 100644
--- a/web-app/public/skills/backend-architect/SKILL.md
+++ b/web-app/public/skills/backend-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: backend-architect
-description: "Expert backend architect specializing in scalable API design,"
+description: |
+ Expert backend architect specializing in scalable API design,
microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC
APIs, event-driven architectures, service mesh patterns, and modern backend
frameworks. Handles service boundary definition, inter-service communication,
diff --git a/web-app/public/skills/backend-security-coder/SKILL.md b/web-app/public/skills/backend-security-coder/SKILL.md
index 799b496d..d97c9883 100644
--- a/web-app/public/skills/backend-security-coder/SKILL.md
+++ b/web-app/public/skills/backend-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: backend-security-coder
-description: "Expert in secure backend coding practices specializing in input"
+description: |
+ Expert in secure backend coding practices specializing in input
validation, authentication, and API security. Use PROACTIVELY for backend
security implementations or security code reviews.
metadata:
diff --git a/web-app/public/skills/bash-pro/SKILL.md b/web-app/public/skills/bash-pro/SKILL.md
index 3beb7730..6dd19742 100644
--- a/web-app/public/skills/bash-pro/SKILL.md
+++ b/web-app/public/skills/bash-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: bash-pro
-description: "Master of defensive Bash scripting for production automation, CI/CD"
+description: |
+ Master of defensive Bash scripting for production automation, CI/CD
pipelines, and system utilities. Expert in safe, portable, and testable shell
scripts.
metadata:
diff --git a/web-app/public/skills/bevy-ecs-expert/SKILL.md b/web-app/public/skills/bevy-ecs-expert/SKILL.md
index 7d6333e5..ebac97be 100644
--- a/web-app/public/skills/bevy-ecs-expert/SKILL.md
+++ b/web-app/public/skills/bevy-ecs-expert/SKILL.md
@@ -83,25 +83,27 @@ fn main() {
## Examples
-### Example 1: Spawning Entities with Bundles
+### Example 1: Spawning Entities with Require Component
```rust
-#[derive(Bundle)]
-struct PlayerBundle {
- player: Player,
- velocity: Velocity,
- sprite: SpriteBundle,
+use bevy::prelude::*;
+
+#[derive(Component, Reflect, Default)]
+#[require(Velocity, Sprite)]
+struct Player;
+
+#[derive(Component, Default)]
+struct Velocity {
+ x: f32,
+ y: f32,
}
fn setup(mut commands: Commands, asset_server: Res) {
- commands.spawn(PlayerBundle {
- player: Player,
- velocity: Velocity { x: 10.0, y: 0.0 },
- sprite: SpriteBundle {
- texture: asset_server.load("player.png"),
- ..default()
- },
- });
+ commands.spawn((
+ Player,
+ Velocity { x: 10.0, y: 0.0 },
+ Sprite::from_image(asset_server.load("player.png")),
+ ));
}
```
diff --git a/web-app/public/skills/blockchain-developer/SKILL.md b/web-app/public/skills/blockchain-developer/SKILL.md
index 192c89fb..c23f36d7 100644
--- a/web-app/public/skills/blockchain-developer/SKILL.md
+++ b/web-app/public/skills/blockchain-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: blockchain-developer
-description: "Build production-ready Web3 applications, smart contracts, and"
+description: |
+ Build production-ready Web3 applications, smart contracts, and
decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and
enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3
apps, DeFi protocols, or blockchain infrastructure.
diff --git a/web-app/public/skills/business-analyst/SKILL.md b/web-app/public/skills/business-analyst/SKILL.md
index ca931200..1a4462b4 100644
--- a/web-app/public/skills/business-analyst/SKILL.md
+++ b/web-app/public/skills/business-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: business-analyst
-description: "Master modern business analysis with AI-powered analytics,"
+description: |
+ Master modern business analysis with AI-powered analytics,
real-time dashboards, and data-driven insights. Build comprehensive KPI
frameworks, predictive models, and strategic recommendations. Use PROACTIVELY
for business intelligence or strategic analysis.
diff --git a/web-app/public/skills/c4-code/SKILL.md b/web-app/public/skills/c4-code/SKILL.md
index 333ab01b..59972a01 100644
--- a/web-app/public/skills/c4-code/SKILL.md
+++ b/web-app/public/skills/c4-code/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-code
-description: "Expert C4 Code-level documentation specialist. Analyzes code"
+description: |
+ Expert C4 Code-level documentation specialist. Analyzes code
directories to create comprehensive C4 code-level documentation including
function signatures, arguments, dependencies, and code structure. Use when
documenting code at the lowest C4 level for individual directories and code
diff --git a/web-app/public/skills/c4-component/SKILL.md b/web-app/public/skills/c4-component/SKILL.md
index 64c14978..deca5509 100644
--- a/web-app/public/skills/c4-component/SKILL.md
+++ b/web-app/public/skills/c4-component/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-component
-description: "Expert C4 Component-level documentation specialist. Synthesizes C4"
+description: |
+ Expert C4 Component-level documentation specialist. Synthesizes C4
Code-level documentation into Component-level architecture, defining component
boundaries, interfaces, and relationships. Creates component diagrams and
documentation. Use when synthesizing code-level documentation into logical
diff --git a/web-app/public/skills/c4-container/SKILL.md b/web-app/public/skills/c4-container/SKILL.md
index c41f6586..297a4e2b 100644
--- a/web-app/public/skills/c4-container/SKILL.md
+++ b/web-app/public/skills/c4-container/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-container
-description: "Expert C4 Container-level documentation specialist. Synthesizes"
+description: |
+ Expert C4 Container-level documentation specialist. Synthesizes
Component-level documentation into Container-level architecture, mapping
components to deployment units, documenting container interfaces as APIs, and
creating container diagrams. Use when synthesizing components into deployment
diff --git a/web-app/public/skills/c4-context/SKILL.md b/web-app/public/skills/c4-context/SKILL.md
index cf5688d0..4d1a5a52 100644
--- a/web-app/public/skills/c4-context/SKILL.md
+++ b/web-app/public/skills/c4-context/SKILL.md
@@ -1,6 +1,7 @@
---
name: c4-context
-description: "Expert C4 Context-level documentation specialist. Creates"
+description: |
+ Expert C4 Context-level documentation specialist. Creates
high-level system context diagrams, documents personas, user journeys, system
features, and external dependencies. Synthesizes container and component
documentation with system documentation to create comprehensive context-level
diff --git a/web-app/public/skills/carrier-relationship-management/SKILL.md b/web-app/public/skills/carrier-relationship-management/SKILL.md
new file mode 100644
index 00000000..cff92397
--- /dev/null
+++ b/web-app/public/skills/carrier-relationship-management/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: carrier-relationship-management
+description: >
+ Codified expertise for managing carrier portfolios, negotiating freight rates,
+ tracking carrier performance, allocating freight, and maintaining strategic
+ carrier relationships. Informed by transportation managers with 15+ years
+ experience. Includes scorecarding frameworks, RFP processes, market intelligence,
+ and compliance vetting. Use when managing carriers, negotiating rates, evaluating
+ carrier performance, or building freight strategies.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🤝"
+---
+
+## When to Use
+
+Use this skill when building and managing a carrier network, conducting freight RFPs, negotiating linehaul and accessorial rates, tracking carrier KPIs via scorecards, or ensuring regulatory compliance of transportation partners.
+
+# Carrier Relationship Management
+
+## Role and Context
+
+You are a senior transportation manager with 15+ years managing carrier portfolios ranging from 40 to 200+ active carriers across truckload, LTL, intermodal, and brokerage. You own the full lifecycle: sourcing new carriers, negotiating rates, running RFPs, building routing guides, tracking performance via scorecards, managing contract renewals, and making allocation decisions. You sit between procurement (who owns total logistics spend), operations (who tenders daily freight), finance (who pays invoices), and senior leadership (who sets cost and service targets). Your systems include TMS (transportation management), rate management platforms, carrier onboarding portals, DAT/Greenscreens for market intelligence, and FMCSA SAFER for compliance. You balance cost reduction pressure against service quality, capacity security, and carrier relationship health — because when the market tightens, your carriers' willingness to cover your freight depends on how you treated them when capacity was loose.
+
+## Core Knowledge
+
+### Rate Negotiation Fundamentals
+
+Every freight rate has components that must be negotiated independently — bundling them obscures where you're overpaying:
+
+- **Base linehaul rate:** The per-mile or flat rate for dock-to-dock transportation. For truckload, benchmark against DAT or Greenscreens lane rates. For LTL, this is the discount off the carrier's published tariff (typically 70-85% discount for mid-volume shippers). Always negotiate on a lane-by-lane basis — a carrier competitive on Chicago–Dallas may be 15% over market on Atlanta–LA.
+- **Fuel surcharge (FSC):** Percentage or per-mile adder tied to the DOE national average diesel price. Negotiate the FSC table, not just the current rate. Key details: the base price trigger (what diesel price equals 0% FSC), the increment (e.g., $0.01/mile per $0.05 diesel increase), and the index lag (weekly vs. monthly adjustment). A carrier quoting a low linehaul with an aggressive FSC table can be more expensive than a higher linehaul with a standard DOE-indexed FSC.
+- **Accessorial charges:** Detention ($50-$100/hr after 2 hours free time is standard), liftgate ($75-$150), residential delivery ($75-$125), inside delivery ($100+), limited access ($50-$100), appointment scheduling ($0-$50). Negotiate free time for detention aggressively — driver detention is the #1 source of carrier invoice disputes. For LTL, watch for reweigh/reclass fees ($25-$75 per occurrence) and cubic capacity surcharges.
+- **Minimum charges:** Every carrier has a minimum per-shipment charge. For truckload, it's typically a minimum mileage (e.g., $800 for loads under 200 miles). For LTL, it's the minimum charge per shipment ($75-$150) regardless of weight or class. Negotiate minimums on short-haul lanes separately.
+- **Contract vs. spot rates:** Contract rates (awarded through RFP or negotiation, valid 6-12 months) provide cost predictability and capacity commitment. Spot rates (negotiated per load on the open market) are 10-30% higher in tight markets, 5-20% lower in soft markets. A healthy portfolio uses 75-85% contract freight and 15-25% spot. More than 30% spot means your routing guide is failing.
+
+### Carrier Scorecarding
+
+Measure what matters. A scorecard that tracks 20 metrics gets ignored; one that tracks 5 gets acted on:
+
+- **On-time delivery (OTD):** Percentage of shipments delivered within the agreed window. Target: ≥95%. Red flag: <90%. Measure pickup and delivery separately — a carrier with 98% on-time pickup and 88% on-time delivery has a linehaul or terminal problem, not a capacity problem.
+- **Tender acceptance rate:** Percentage of electronically tendered loads accepted by the carrier. Target: ≥90% for primary carriers. Red flag: <80%. A carrier that rejects 25% of tenders is consuming your operations team's time re-tendering and forcing spot market exposure. Tender acceptance below 75% on a contract lane means the rate is below market — renegotiate or reallocate.
+- **Claims ratio:** Dollar value of claims filed divided by total freight spend with the carrier. Target: <0.5% of spend. Red flag: >1.0%. Track claims frequency separately from claims severity — a carrier with one $50K claim is different from one with fifty $1K claims. The latter indicates a systemic handling problem.
+- **Invoice accuracy:** Percentage of invoices matching the contracted rate without manual correction. Target: ≥97%. Red flag: <93%. Chronic overbilling (even small amounts) signals either intentional rate testing or broken billing systems. Either way, it costs you audit labor. Carriers with <90% invoice accuracy should be on corrective action.
+- **Tender-to-pickup time:** Hours between electronic tender acceptance and actual pickup. Target: within 2 hours of requested pickup for FTL. Carriers that accept tenders but consistently pick up late are "soft rejecting" — they accept to hold the load while shopping for better freight.
+
+### Portfolio Strategy
+
+Your carrier portfolio is an investment portfolio — diversification manages risk, concentration drives leverage:
+
+- **Asset carriers vs. brokers:** Asset carriers own trucks. They provide capacity certainty, consistent service, and direct accountability — but they're less flexible on pricing and may not cover all your lanes. Brokers source capacity from thousands of small carriers. They offer pricing flexibility and lane coverage, but introduce counterparty risk (double-brokering, carrier quality variance, payment chain complexity). Target mix: 60-70% asset, 20-30% broker, 5-15% niche/specialty.
+- **Routing guide structure:** Build a 3-deep routing guide for every lane with >2 loads/week. Primary carrier gets first tender (target: 80%+ acceptance). Secondary gets the fallback (target: 70%+ acceptance on overflow). Tertiary is your price ceiling — often a broker whose rate represents the "do not exceed" for spot procurement. For lanes with <2 loads/week, use a 2-deep guide or a regional broker with broad coverage.
+- **Lane density and carrier concentration:** Award enough volume per carrier per lane to matter to them. A carrier running 2 loads/week on your lane will prioritize you over a shipper giving them 2 loads/month. But don't give one carrier more than 40% of any single lane — a carrier exit or service failure on a concentrated lane is catastrophic. For your top 20 lanes by volume, maintain at least 3 active carriers.
+- **Small carrier value:** Carriers with 10-50 trucks often provide better service, more flexible pricing, and stronger relationships than mega-carriers. They answer the phone. Their owner-operators care about your freight. The tradeoff: less technology integration, thinner insurance, and capacity limits during peak. Use small carriers for consistent, mid-volume lanes where relationship quality matters more than surge capacity.
+
+### RFP Process
+
+A well-run freight RFP takes 8-12 weeks and touches every active and prospective carrier:
+
+- **Pre-RFP:** Analyze 12 months of shipment data. Identify lanes by volume, spend, and current service levels. Flag underperforming lanes and lanes where current rates exceed market benchmarks (DAT, Greenscreens, Chainalytics). Set targets: cost reduction percentage, service level minimums, carrier diversity goals.
+- **RFP design:** Include lane-level detail (origin/destination zip, volume range, required equipment, any special handling), current transit time expectations, accessorial requirements, payment terms, insurance minimums, and your evaluation criteria with weightings. Make carriers bid lane-by-lane — portfolio bids ("we'll give you 5% off everything") hide cross-subsidization.
+- **Bid evaluation:** Don't award on price alone. Weight cost at 40-50%, service history at 25-30%, capacity commitment at 15-20%, and operational fit at 10-15%. A carrier 3% above the lowest bid but with 97% OTD and 95% tender acceptance is cheaper than the lowest bidder with 85% OTD and 70% tender acceptance — the service failures cost more than the rate difference.
+- **Award and implementation:** Award in waves — primary carriers first, then secondary. Give carriers 2-3 weeks to operationalize new lanes before you start tendering. Run a 30-day parallel period where old and new routing guides overlap. Cut over cleanly.
+
+### Market Intelligence
+
+Rate cycles are predictable in direction, unpredictable in magnitude:
+
+- **DAT and Greenscreens:** DAT RateView provides lane-level spot and contract rate benchmarks based on broker-reported transactions. Greenscreens provides carrier-specific pricing intelligence and predictive analytics. Use both — DAT for market direction, Greenscreens for carrier-specific negotiation leverage. Neither is perfectly accurate, but both are better than negotiating blind.
+- **Freight market cycles:** The truckload market oscillates between shipper-favorable (excess capacity, falling rates, high tender acceptance) and carrier-favorable (tight capacity, rising rates, tender rejections). Cycles last 18-36 months peak-to-peak. Key indicators: DAT load-to-truck ratio (>6:1 signals tight market), OTRI (Outbound Tender Rejection Index — >10% signals carrier leverage shifting), Class 8 truck orders (leading indicator of capacity addition 6-12 months out).
+- **Seasonal patterns:** Produce season (April-July) tightens reefer capacity in the Southeast and West. Peak retail season (October-January) tightens dry van capacity nationally. The last week of each month and quarter sees volume spikes as shippers meet revenue targets. Budget RFP timing to avoid awarding contracts at the peak or trough of a cycle — award during the transition for more realistic rates.
+
+### FMCSA Compliance Vetting
+
+Every carrier in your portfolio must pass compliance screening before their first load and on a recurring quarterly basis:
+
+- **Operating authority:** Verify active MC (Motor Carrier) or FF (Freight Forwarder) authority via FMCSA SAFER. An "authorized" status that hasn't been updated in 12+ months may indicate a carrier that's technically authorized but operationally inactive. Check the "authorized for" field — a carrier authorized for "property" cannot legally carry household goods.
+- **Insurance minimums:** $750K minimum for general freight (per FMCSA §387.9), $1M for hazmat, $5M for household goods. Require $1M minimum from all carriers regardless of commodity — the FMCSA minimum of $750K doesn't cover a serious accident. Verify insurance through the FMCSA Insurance tab, not just the certificate the carrier provides — certificates can be forged or outdated.
+- **Safety rating:** FMCSA assigns Satisfactory, Conditional, or Unsatisfactory ratings based on compliance reviews. Never use a carrier with an Unsatisfactory rating. Conditional carriers require case-by-case evaluation — understand what the conditions are. Carriers with no rating ("unrated") make up the majority — use their CSA (Compliance, Safety, Accountability) scores instead. Focus on Unsafe Driving, Hours-of-Service, and Vehicle Maintenance BASICs. A carrier in the top 25% percentile (worst) on Unsafe Driving is a liability risk.
+- **Broker bond verification:** If using brokers, verify their $75K surety bond or trust fund is active. A broker whose bond has been revoked or reduced is likely in financial distress. Check the FMCSA Bond/Trust tab. Also verify the broker has contingent cargo insurance — this protects you if the broker's underlying carrier causes a loss and the carrier's insurance is insufficient.
+
+## Decision Frameworks
+
+### Carrier Selection for New Lanes
+
+When adding a new lane to your network, evaluate candidates on this decision tree:
+
+1. **Do existing portfolio carriers cover this lane?** If yes, negotiate with incumbents first — adding a new carrier for one lane introduces onboarding cost ($500-$1,500) and relationship management overhead. Offer existing carriers the new lane as incremental volume in exchange for a rate concession on an existing lane.
+2. **If no incumbent covers the lane:** Source 3-5 candidates. For lanes >500 miles, prioritize asset carriers with domicile within 100 miles of the origin. For lanes <300 miles, consider regional carriers and dedicated fleets. For infrequent lanes (<1 load/week), a broker with strong regional coverage may be the most practical option.
+3. **Evaluate:** Run FMCSA compliance check. Request 12-month service history on the specific lane from each candidate (not just their network average). Check DAT lane rates for market benchmark. Compare total cost (linehaul + FSC + expected accessorials), not just linehaul.
+4. **Trial period:** Award 30-day trial at contracted rates. Set clear KPIs: OTD ≥93%, tender acceptance ≥85%, invoice accuracy ≥95%. Review at 30 days — do not lock in a 12-month commitment without operational validation.
+
+### When to Consolidate vs. Diversify
+
+- **Consolidate (reduce carrier count) when:** You have more than 3 carriers on a lane with <5 loads/week (each carrier gets too little volume to care). Your carrier management resources are stretched. You need deeper pricing from a strategic partner (volume concentration = leverage). The market is loose and carriers are competing for your freight.
+- **Diversify (add carriers) when:** A single carrier handles >40% of a critical lane. Tender rejections are rising above 15% on a lane. You're entering peak season and need surge capacity. A carrier shows financial distress indicators (late payments to drivers reported on Carrier411, FMCSA insurance lapses, sudden driver turnover visible via CDL postings).
+
+### Spot vs. Contract Decisions
+
+- **Stay on contract when:** The spread between contract and spot is <10%. You have consistent, predictable volume. Capacity is tightening (spot rates are rising). The lane is customer-critical with tight delivery windows.
+- **Go to spot when:** Spot rates are >15% below your contract rate (market is soft). The lane is irregular (<1 load/week). You need one-time surge capacity beyond your routing guide. Your contract carrier is consistently rejecting tenders on this lane (they're effectively pricing you into spot anyway).
+- **Renegotiate contract when:** The spread between your contract rate and DAT benchmark exceeds 15% for 60+ consecutive days. A carrier's tender acceptance drops below 75% for 30 days. You've had a significant volume change (up or down) that changes the lane economics.
+
+### Carrier Exit Criteria
+
+Remove a carrier from your active routing guide when any of these thresholds are met, after documented corrective action has failed:
+
+- OTD below 85% for 60 consecutive days
+- Tender acceptance below 70% for 30 consecutive days with no communication
+- Claims ratio exceeds 2% of spend for 90 days
+- FMCSA authority revoked, insurance lapsed, or safety rating downgraded to Unsatisfactory
+- Invoice accuracy below 88% for 90 days after corrective notice
+- Discovery of double-brokering your freight
+- Evidence of financial distress: bond revocation, driver complaints on CarrierOK or Carrier411, unexplained service collapse
+
+## Key Edge Cases
+
+These are situations where standard playbook decisions lead to poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Capacity squeeze during a hurricane:** Your top carrier evacuates drivers from the Gulf Coast. Spot rates triple. The temptation is to pay any rate to move freight. The expert move: activate pre-positioned regional carriers, reroute through unaffected corridors, and negotiate multi-load commitments with spot carriers to lock a rate ceiling.
+
+2. **Double-brokering discovery:** You're told the truck that arrived isn't from the carrier on your BOL. The insurance chain may be broken and your freight is at higher risk. Do not accept the load if it hasn't departed. If in transit, document everything and demand a written explanation within 24 hours.
+
+3. **Rate renegotiation after 40% volume loss:** Your company lost a major customer and your freight volume dropped. Your carriers' contract rates were predicated on volume commitments you can no longer meet. Proactive renegotiation preserves relationships; letting carriers discover the shortfall at invoice time destroys trust.
+
+4. **Carrier financial distress indicators:** The warning signs appear months before a carrier fails: delayed driver settlements, FMCSA insurance filings changing underwriters frequently, bond amount dropping, Carrier411 complaints spiking. Reduce exposure incrementally — don't wait for the failure.
+
+5. **Mega-carrier acquisition of your niche partner:** Your best regional carrier just got acquired by a national fleet. Expect service disruption during integration, rate renegotiation attempts, and potential loss of your dedicated account manager. Secure alternative capacity before the transition completes.
+
+6. **Fuel surcharge manipulation:** A carrier proposes an artificially low base rate with an aggressive FSC schedule that inflates the total cost above market. Always model total cost across a range of diesel prices ($3.50, $4.00, $4.50/gal) to expose this tactic.
+
+7. **Detention and accessorial disputes at scale:** When detention charges represent >5% of a carrier's total billing, the root cause is usually shipper facility operations, not carrier overcharging. Address the operational issue before disputing the charges — or lose the carrier.
+
+## Communication Patterns
+
+### Rate Negotiation Tone
+
+Rate negotiations are long-term relationship conversations, not one-time transactions. Calibrate tone:
+
+- **Opening position:** Lead with data, not demands. "DAT shows this lane averaging $2.15/mile over the last 90 days. Our current contract is $2.45. We'd like to discuss alignment." Never say "your rate is too high" — say "the market has shifted and we want to make sure we're in a competitive position together."
+- **Counter-offers:** Acknowledge the carrier's perspective. "We understand driver pay increases are real. Let's find a number that keeps this lane attractive for your drivers while keeping us competitive." Meet in the middle on base rate, negotiate harder on accessorials and FSC table.
+- **Annual reviews:** Frame as partnership check-ins, not cost-cutting exercises. Share your volume forecast, growth plans, and lane changes. Ask what you can do operationally to help the carrier (faster dock times, consistent scheduling, drop-trailer programs). Carriers give better rates to shippers who make their drivers' lives easier.
+
+### Performance Reviews
+
+- **Positive reviews:** Be specific. "Your 97% OTD on the Chicago–Dallas lane saved us approximately $45K in expedite costs this quarter. We're increasing your allocation from 60% to 75% on that lane." Carriers invest in relationships that reward performance.
+- **Corrective reviews:** Lead with data, not accusations. Present the scorecard. Identify the specific metrics below threshold. Ask for a corrective action plan with a 30/60/90-day timeline. Set a clear consequence: "If OTD on this lane doesn't reach 92% by the 60-day mark, we'll need to shift 50% of volume to an alternate carrier."
+
+For full communication templates, see [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------------------------- | ------------------------------------------------ | --------------- |
+| Carrier tender acceptance drops below 70% for 2 consecutive weeks | Notify procurement, schedule carrier call | Within 48 hours |
+| Spot spend exceeds 30% of lane budget for any lane | Review routing guide, initiate carrier sourcing | Within 1 week |
+| Carrier FMCSA authority or insurance lapses | Immediately suspend tendering, notify operations | Within 1 hour |
+| Single carrier controls >50% of a critical lane | Initiate secondary carrier qualification | Within 2 weeks |
+| Claims ratio exceeds 1.5% for any carrier for 60+ days | Schedule formal performance review | Within 1 week |
+| Rate variance >20% from DAT benchmark on 5+ lanes | Initiate contract renegotiation or mini-bid | Within 2 weeks |
+| Carrier reports driver shortage or service disruption | Activate backup carriers, increase monitoring | Within 4 hours |
+| Double-brokering confirmed on any load | Immediate carrier suspension, compliance review | Within 2 hours |
+
+### Escalation Chain
+
+Analyst → Transportation Manager (48 hours) → Director of Transportation (1 week) → VP Supply Chain (persistent issue or >$100K exposure)
+
+## Performance Indicators
+
+Track weekly, review monthly with carrier management team, share quarterly with carriers:
+
+| Metric | Target | Red Flag |
+| ------------------------------------------------ | -------------- | ------------------------ |
+| Contract rate vs. DAT benchmark | Within ±8% | >15% premium or discount |
+| Routing guide compliance (% of freight on guide) | ≥85% | <70% |
+| Primary tender acceptance | ≥90% | <80% |
+| Weighted average OTD across portfolio | ≥95% | <90% |
+| Carrier portfolio claims ratio | <0.5% of spend | >1.0% |
+| Average carrier invoice accuracy | ≥97% | <93% |
+| Spot freight percentage | <20% | >30% |
+| RFP cycle time (launch to implementation) | ≤12 weeks | >16 weeks |
+
+## Additional Resources
+
+- For detailed decision frameworks on rate negotiation, portfolio optimization, and RFP execution, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you are **designing or tuning your carrier portfolio, routing guides, and freight procurement strategy**:
+
+- Running freight RFPs, renegotiating contract and fuel tables, or balancing spot vs. contract exposure.
+- Building carrier scorecards, exit criteria, and escalation protocols to manage performance and risk.
+- Deciding how to allocate lanes across asset carriers, brokers, and regional specialists to protect service while controlling logistics spend.
diff --git a/web-app/public/skills/carrier-relationship-management/references/communication-templates.md b/web-app/public/skills/carrier-relationship-management/references/communication-templates.md
new file mode 100644
index 00000000..053b981a
--- /dev/null
+++ b/web-app/public/skills/carrier-relationship-management/references/communication-templates.md
@@ -0,0 +1,584 @@
+# Communication Templates — Carrier Relationship Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing carrier communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by communication type and business context. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RFP Invitation Letter](#1-rfp-invitation-letter)
+2. [Rate Negotiation Opening](#2-rate-negotiation-opening)
+3. [Rate Counter-Offer](#3-rate-counter-offer)
+4. [Carrier Performance Review — Positive](#4-carrier-performance-review--positive)
+5. [Carrier Performance Review — Corrective](#5-carrier-performance-review--corrective)
+6. [Carrier Onboarding Welcome](#6-carrier-onboarding-welcome)
+7. [Carrier Warning Letter](#7-carrier-warning-letter)
+8. [Carrier Exit Notification](#8-carrier-exit-notification)
+9. [Market Rate Discussion](#9-market-rate-discussion)
+10. [Partnership Proposal](#10-partnership-proposal)
+11. [Detention Dispute Communication](#11-detention-dispute-communication)
+12. [Accessorial Challenge](#12-accessorial-challenge)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{carrier_name}}` | Carrier legal or DBA name | `Ridgeline Transport, Inc.` |
+| `{{carrier_contact}}` | Carrier contact name | `Mike Patterson` |
+| `{{carrier_contact_title}}` | Carrier contact title | `VP of Sales` |
+| `{{carrier_mc}}` | Carrier MC number | `MC-498132` |
+| `{{our_company}}` | Our company name | `Consolidated Manufacturing LLC` |
+| `{{our_contact_name}}` | Our representative name | `Sarah Chen` |
+| `{{our_contact_title}}` | Our representative title | `Director of Transportation` |
+| `{{our_contact_email}}` | Our representative email | `schen@company.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(312) 555-0189` |
+| `{{lane_origin}}` | Lane origin city/state | `Chicago, IL` |
+| `{{lane_destination}}` | Lane destination city/state | `Dallas, TX` |
+| `{{current_rate}}` | Current contract rate per mile | `$2.45/mile` |
+| `{{proposed_rate}}` | Proposed new rate | `$2.28/mile` |
+| `{{market_rate}}` | DAT/benchmark market rate | `$2.18/mile` |
+| `{{volume_loads_week}}` | Weekly load volume | `8 loads/week` |
+| `{{annual_spend}}` | Annual freight spend with carrier | `$2.4M` |
+| `{{contract_start}}` | Contract effective date | `2026-04-01` |
+| `{{contract_end}}` | Contract expiration date | `2027-03-31` |
+| `{{rfp_deadline}}` | RFP response deadline | `2026-03-15` |
+| `{{otd_percentage}}` | Carrier's on-time delivery rate | `96.2%` |
+| `{{tender_acceptance}}` | Carrier's tender acceptance rate | `91.4%` |
+| `{{claims_ratio}}` | Carrier's claims ratio | `0.3%` |
+| `{{invoice_accuracy}}` | Carrier's invoice accuracy rate | `97.8%` |
+| `{{review_period}}` | Performance review time period | `Q3 2025 (Jul-Sep)` |
+| `{{detention_amount}}` | Disputed detention charge amount | `$4,275` |
+| `{{accessorial_type}}` | Specific accessorial charge type | `liftgate delivery` |
+
+---
+
+## 1. RFP Invitation Letter
+
+**Channel:** Email
+**Audience:** Carrier sales / pricing leadership
+**Tone:** Professional, opportunity-oriented. You're inviting them to compete for business, not demanding concessions.
+
+---
+
+**Subject:** `Invitation to Bid — {{our_company}} Freight RFP — {{contract_start}} Award`
+
+{{carrier_contact}},
+
+{{our_company}} is conducting our annual freight RFP process and we're inviting {{carrier_name}} to participate as a bidding carrier. Based on our analysis of market capabilities and your operational profile, we believe there may be strong alignment between your network and our shipping requirements.
+
+**RFP Overview:**
+- **Scope:** {{lane_count}} lanes across TL, LTL, and intermodal modes
+- **Total annual freight spend:** Approximately {{total_annual_spend}}
+- **Contract period:** {{contract_start}} through {{contract_end}}
+- **Bid deadline:** {{rfp_deadline}} at 5:00 PM CT
+
+**What We're Looking For:**
+We evaluate bids on a weighted scorecard: rate competitiveness (40%), service history and reliability (25%), capacity commitment (20%), and operational fit including technology integration (15%). We value carriers who bring consistent service and a commitment to partnership over the lowest possible rate.
+
+**Enclosed with this letter:**
+1. Lane-level bid package with volume ranges, equipment requirements, and transit expectations
+2. Accessorial schedule with standard rates and negotiable items
+3. Insurance and compliance requirements
+4. Service-level expectations (OTD, tender acceptance, claims thresholds)
+5. Contract terms summary
+
+**Next Steps:**
+Please confirm your intent to bid by {{rfp_confirm_date}}. A Q&A webinar for all participating carriers is scheduled for {{qa_date}} at {{qa_time}} CT. All questions must be submitted in writing through the RFP portal; responses will be shared with all bidders.
+
+We look forward to your participation.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 2. Rate Negotiation Opening
+
+**Channel:** Email followed by phone call
+**Audience:** Carrier account manager or VP of Sales
+**Tone:** Data-driven, collaborative. Lead with market data, not demands. Frame as aligning rates with market reality, not squeezing the carrier.
+
+---
+
+**Subject:** `Rate Review Discussion — {{lane_origin}} to {{lane_destination}} | {{our_company}}`
+
+{{carrier_contact}},
+
+I'd like to schedule a call to discuss rate alignment on our {{lane_origin}} to {{lane_destination}} lane. As part of our quarterly rate benchmarking process, we've identified an opportunity to ensure our pricing on this lane reflects current market conditions.
+
+**Our Current Situation:**
+- **Current contract rate:** {{current_rate}} (effective since {{contract_start}})
+- **DAT 90-day contract average for this lane:** {{market_rate}}
+- **Your current volume on this lane:** {{volume_loads_week}}
+- **Your performance:** {{otd_percentage}} OTD, {{tender_acceptance}} tender acceptance
+
+We recognize that {{carrier_name}} has delivered strong service on this lane, and our goal is to find a rate that keeps this lane attractive for both of us. We're not looking to drive rates to a level that compromises your service or driver compensation — we are looking for alignment with where the market has moved.
+
+Could you check availability for a 30-minute call this week? I'd like to walk through the data together and explore options.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Rate Counter-Offer
+
+**Channel:** Email
+**Audience:** Carrier account manager or pricing team
+**Tone:** Firm but respectful. Acknowledge the carrier's position while advancing yours. Always justify with data.
+
+---
+
+**Subject:** `Re: Rate Proposal — {{lane_origin}} to {{lane_destination}}`
+
+{{carrier_contact}},
+
+Thank you for the rate proposal on our {{lane_origin}} to {{lane_destination}} lane. I appreciate the detail and the time your team invested.
+
+After reviewing your proposal against our market data and total cost model, I'd like to share our counter-position:
+
+**Your Proposal:** {{carrier_proposed_rate}}
+**Our Counter:** {{our_counter_rate}}
+
+**Rationale:**
+- DAT 90-day contract average for this lane is {{market_rate}}, which puts your proposal {{percentage_above_market}}% above the current market benchmark.
+- We modeled total cost including your proposed fuel surcharge schedule at diesel prices of $3.25, $3.85, and $4.50/gal. At current diesel ({{current_diesel}}), your total cost per mile is {{total_cost_per_mile}}, which is {{total_cost_vs_market}}% above our benchmark total cost.
+- Our counter rate of {{our_counter_rate}} reflects the market benchmark plus a {{premium_percentage}}% premium for your service quality — which we genuinely value. Your {{otd_percentage}} OTD is among the best in our portfolio.
+
+**What We're Offering in Return:**
+- Volume commitment: {{volume_commitment}} loads/week guaranteed (vs. your current {{current_volume}} loads/week)
+- Payment terms: Net {{payment_days}} (vs. our standard Net 30)
+- Drop-trailer program at our {{facility_name}} facility (eliminating an average of {{detention_hours}} hours detention per load)
+
+I believe we can find alignment here. Would a call on {{proposed_call_date}} work to discuss?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 4. Carrier Performance Review — Positive
+
+**Channel:** Email + formal quarterly business review meeting
+**Audience:** Carrier account manager, VP of Sales, and operations leadership
+**Tone:** Celebratory and specific. Name the metrics, quantify the impact, and reward with tangible actions (more volume, longer contract, public recognition). Generic praise is worse than no praise.
+
+---
+
+**Subject:** `Q{{quarter}} Performance Review — {{carrier_name}} | Outstanding Results`
+
+{{carrier_contact}},
+
+I want to formally recognize {{carrier_name}}'s performance during {{review_period}}. Your team has been exceptional across every metric we track, and we want to make sure you know it — and that we're backing up that recognition with action.
+
+**Performance Summary — {{review_period}}:**
+
+| Metric | Target | Your Performance | Portfolio Average |
+|--------|--------|-----------------|-------------------|
+| On-Time Delivery | ≥95% | {{otd_percentage}} | {{portfolio_avg_otd}} |
+| Tender Acceptance | ≥90% | {{tender_acceptance}} | {{portfolio_avg_tender}} |
+| Claims Ratio | <0.5% | {{claims_ratio}} | {{portfolio_avg_claims}} |
+| Invoice Accuracy | ≥97% | {{invoice_accuracy}} | {{portfolio_avg_invoice}} |
+
+**Specific Highlights:**
+- Your team's performance on the {{highlight_lane}} lane was particularly strong — {{highlight_detail}}.
+- Driver {{driver_name}} received compliments from our {{facility_name}} receiving team for consistent professionalism and efficient dock operations.
+- Your operations team's proactive communication during {{event}} prevented what could have been a significant service disruption.
+
+**What This Means for Our Partnership:**
+Based on this performance, we're making the following allocation changes effective {{effective_date}}:
+- **{{lane_1}}:** Increasing your allocation from {{old_allocation_1}}% to {{new_allocation_1}}%
+- **{{lane_2}}:** Adding you as primary carrier (new lane award — {{volume_2}} loads/week)
+- **Contract extension:** We'd like to discuss extending our agreement through {{extended_end_date}} at current terms
+
+Thank you for making our operation better. We value this partnership and look forward to continuing to grow together.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Carrier Performance Review — Corrective
+
+**Channel:** Email followed by in-person or video meeting
+**Audience:** Carrier account manager and operations leadership
+**Tone:** Professional, direct, data-driven. Not punitive — corrective. Present the data, state the impact, set clear expectations with a timeline, and define the consequence. Avoid emotional language.
+
+---
+
+**Subject:** `Performance Review — {{carrier_name}} | Corrective Action Required`
+
+{{carrier_contact}},
+
+I'm reaching out regarding {{carrier_name}}'s performance during {{review_period}} on lanes serviced for {{our_company}}. Several metrics have fallen below our minimum standards, and I want to address this directly so we can work together on a resolution.
+
+**Performance Summary — {{review_period}}:**
+
+| Metric | Our Standard | Your Performance | Gap |
+|--------|-------------|-----------------|-----|
+| On-Time Delivery | ≥95% | {{otd_percentage}} | {{otd_gap}} below standard |
+| Tender Acceptance | ≥90% | {{tender_acceptance}} | {{tender_gap}} below standard |
+| Claims Ratio | <0.5% | {{claims_ratio}} | {{claims_gap}} above standard |
+| Invoice Accuracy | ≥97% | {{invoice_accuracy}} | {{invoice_gap}} below standard |
+
+**Business Impact:**
+- Tender rejections on the {{problem_lane}} lane forced {{spot_loads}} loads to the spot market at an average premium of {{spot_premium}}%, costing us approximately ${{incremental_cost}} in incremental freight spend.
+- Late deliveries resulted in {{penalty_count}} customer penalty events totaling ${{penalty_total}}.
+
+**What We Need:**
+We value our relationship with {{carrier_name}} and want to find a path forward. We're requesting a Corrective Action Plan that addresses the following within the timelines indicated:
+
+| Metric | Target | 30-Day Checkpoint | 60-Day Checkpoint |
+|--------|--------|-------------------|-------------------|
+| OTD | ≥{{otd_target}}% | ≥{{otd_30day}}% | ≥{{otd_60day}}% |
+| Tender Acceptance | ≥{{tender_target}}% | ≥{{tender_30day}}% | ≥{{tender_60day}}% |
+
+Please send your CAP document by {{cap_due_date}} outlining the root causes you've identified and the specific operational changes you're implementing.
+
+**If Targets Are Not Met:**
+If the 60-day checkpoint targets are not achieved, we will need to reduce your allocation on affected lanes by 50% and reassign volume to alternate carriers. This is not our preferred outcome — we'd much rather see improvement and continue building this partnership.
+
+I'd like to schedule a call for {{proposed_call_date}} to discuss your initial assessment. Please let me know your availability.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 6. Carrier Onboarding Welcome
+
+**Channel:** Email
+**Audience:** Carrier's assigned account manager and operations contact
+**Tone:** Welcoming, organized, and clear about expectations. First impressions set the relationship trajectory.
+
+---
+
+**Subject:** `Welcome to {{our_company}}'s Carrier Network — Onboarding Information`
+
+{{carrier_contact}},
+
+Welcome to {{our_company}}'s carrier network. We're pleased to have {{carrier_name}} as a transportation partner and look forward to a productive relationship.
+
+This email contains everything you need to get started. Please review carefully and let me know if you have questions.
+
+**Your Awarded Lanes:**
+
+| Lane | Volume | Equipment | Transit Requirement |
+|------|--------|-----------|-------------------|
+| {{lane_1_origin}} → {{lane_1_dest}} | {{lane_1_volume}}/week | {{lane_1_equip}} | {{lane_1_transit}} |
+| {{lane_2_origin}} → {{lane_2_dest}} | {{lane_2_volume}}/week | {{lane_2_equip}} | {{lane_2_transit}} |
+
+**Onboarding Checklist (please complete by {{onboarding_deadline}}):**
+
+- [ ] Return signed Carrier Transportation Agreement (attached)
+- [ ] Provide current Certificate of Insurance meeting our minimums ($1M auto liability, $100K cargo)
+- [ ] Complete W-9 form (attached)
+- [ ] Provide EDI/API contact for system integration setup (if applicable)
+- [ ] Confirm operational contact for daily dispatching (name, phone, email)
+- [ ] Confirm after-hours emergency contact (name, phone)
+
+**What to Expect:**
+- **First 30 days:** We'll run trial loads on your awarded lanes. Our minimum standards during trial: ≥93% OTD, ≥85% tender acceptance, ≥95% invoice accuracy.
+- **Day 30 review:** We'll review trial performance together. If targets are met, you'll move to full allocation. If not, we'll discuss what adjustments are needed.
+- **Ongoing:** Quarterly performance reviews, annual rate review aligned with our RFP cycle.
+
+**Our Facilities — Key Operational Notes:**
+
+| Facility | Dock Hours | Appointment Required? | Avg Load/Unload Time | Detention Policy |
+|----------|-----------|----------------------|---------------------|-----------------|
+| {{facility_1}} | {{hours_1}} | {{appt_1}} | {{avg_time_1}} | {{detention_1}} |
+| {{facility_2}} | {{hours_2}} | {{appt_2}} | {{avg_time_2}} | {{detention_2}} |
+
+**Your Primary Contacts at {{our_company}}:**
+- **Relationship management:** {{our_contact_name}}, {{our_contact_title}} ({{our_contact_email}}, {{our_contact_phone}})
+- **Daily operations / tendering:** {{ops_contact_name}}, {{ops_contact_title}} ({{ops_contact_email}}, {{ops_contact_phone}})
+- **Accounts payable / invoicing:** {{ap_contact_name}} ({{ap_contact_email}})
+
+Welcome aboard. We believe in rewarding performance — carriers who deliver consistent, high-quality service earn more volume, longer contracts, and priority consideration for new lanes.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+
+---
+
+## 7. Carrier Warning Letter
+
+**Channel:** Formal email with read receipt requested; copy to carrier's VP of Sales
+**Audience:** Carrier account manager + carrier senior leadership
+**Tone:** Formal and serious. This is a documentation event as much as a communication — it creates the paper trail for a potential exit decision. Factual, not emotional. Cite specific contract provisions.
+
+---
+
+**Subject:** `FORMAL NOTICE: Performance Deficiency — {{carrier_name}} / {{our_company}} Account`
+
+{{carrier_contact}},
+
+This letter serves as formal notice that {{carrier_name}}'s performance on {{our_company}}'s account has fallen below contractual standards for a sustained period, and continued non-compliance will result in volume reduction and potential removal from our routing guide.
+
+**Deficiency Summary:**
+Per Section {{contract_section}} of our Transportation Agreement dated {{agreement_date}}, the following minimum standards apply:
+
+| Metric | Contractual Minimum | {{carrier_name}}'s Performance ({{deficiency_period}}) |
+|--------|--------------------|----------------------------------------------------|
+| {{metric_1}} | {{standard_1}} | {{actual_1}} |
+| {{metric_2}} | {{standard_2}} | {{actual_2}} |
+
+**Prior Communication:**
+- {{prior_comm_date_1}}: {{prior_comm_description_1}}
+- {{prior_comm_date_2}}: {{prior_comm_description_2}}
+- {{cap_date}}: Corrective Action Plan submitted, targeting improvement by {{cap_target_date}}
+- As of {{current_date}}, targets have not been met.
+
+**Consequences:**
+Effective {{consequence_date}}, we will reduce {{carrier_name}}'s allocation on the following lanes by {{reduction_percentage}}%:
+{{affected_lanes_list}}
+
+If performance does not reach contractual minimums by {{final_deadline}}, {{carrier_name}} will be removed from our active routing guide on all affected lanes.
+
+**Path to Resolution:**
+We would prefer to resolve this cooperatively. If {{carrier_name}} can provide an updated remediation plan addressing the specific root causes and committing to measurable improvement targets, we are willing to extend the review period by 30 days.
+
+Please respond in writing by {{response_deadline}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+CC: {{carrier_vp_name}}, {{carrier_vp_title}}, {{carrier_name}}
+CC: {{our_director_name}}, {{our_director_title}}, {{our_company}}
+
+---
+
+## 8. Carrier Exit Notification
+
+**Channel:** Formal email followed by phone call
+**Audience:** Carrier account manager and carrier senior leadership
+**Tone:** Respectful and final. This is a business decision, not a punishment. Leave the door open for future consideration. Avoid burning bridges — the carrier community is smaller than you think.
+
+---
+
+**Subject:** `Notice of Routing Guide Removal — {{carrier_name}} / {{our_company}}`
+
+{{carrier_contact}},
+
+After careful consideration and review of {{carrier_name}}'s performance over the past {{review_months}} months, we have made the decision to remove {{carrier_name}} from {{our_company}}'s active routing guide effective {{exit_date}}.
+
+**Reason for Decision:**
+{{exit_reason_summary}}
+
+**Transition Plan:**
+- **{{exit_date}} through {{transition_end_date}}:** We will reduce tender volume by approximately {{reduction_percent}}% per week during this transition period to allow both organizations to adjust.
+- **Open invoices:** All outstanding invoices will be processed per standard payment terms. Please ensure all invoices are submitted by {{invoice_deadline}}.
+- **Open claims:** Any pending claims will continue through their normal resolution process. This decision does not affect the adjudication of open claims.
+
+**What This Means Going Forward:**
+This is not necessarily a permanent decision. We review our carrier portfolio annually during our RFP process. If {{carrier_name}} addresses the issues noted above and would like to re-engage, we welcome your participation in future RFP cycles.
+
+I'm available to discuss this decision directly if you'd like to connect. I respect the work your team has done for our account and want to ensure this transition is handled professionally.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 9. Market Rate Discussion
+
+**Channel:** Email or phone, depending on relationship depth
+**Audience:** Carrier account manager
+**Tone:** Collegial and transparent. This is a market discussion, not a negotiation — you're sharing data and inviting dialogue. Use when market conditions have shifted and you want to proactively discuss alignment before it becomes a formal renegotiation.
+
+---
+
+**Subject:** `Market Check-In — {{lane_origin}} to {{lane_destination}} Corridor`
+
+{{carrier_contact}},
+
+I wanted to reach out proactively about what we're seeing in the {{lane_origin}} to {{lane_destination}} market. As you know, we track lane-level benchmarks quarterly, and the latest data suggests some movement worth discussing.
+
+**What We're Seeing:**
+- DAT contract average for this lane has moved from {{old_benchmark}} to {{new_benchmark}} over the last {{timeframe}} — a {{percentage_change}} {{direction}} shift.
+- Our spot procurement on overflow loads in this corridor has averaged {{spot_average}} over the last 30 days.
+- Load-to-truck ratios in the {{region}} region are currently {{ltt_ratio}}, compared to {{ltt_previous}} last quarter.
+
+**Our Perspective:**
+We're not sending this as a formal rate request — it's a market conversation. We want to understand how you're seeing the same data and whether there's an opportunity to align proactively rather than waiting for contract renewal.
+
+If the market has moved in a way that affects our lane economics, I'd rather discuss it now and find a mutually workable solution than have it surface as a surprise during our annual review.
+
+Would you have 20 minutes this week to discuss?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 10. Partnership Proposal
+
+**Channel:** Formal letter or meeting presentation
+**Audience:** Carrier CEO, President, or SVP of Sales
+**Tone:** Strategic and forward-looking. This is a business partnership proposal, not a procurement transaction. Emphasize mutual benefit, growth potential, and commitment.
+
+---
+
+**Subject:** `Strategic Partnership Proposal — {{our_company}} and {{carrier_name}}`
+
+{{carrier_contact}},
+
+I'd like to propose elevating the relationship between {{our_company}} and {{carrier_name}} from a standard carrier-shipper arrangement to a strategic partnership. Our analysis suggests significant mutual benefit in a deeper, more integrated collaboration.
+
+**Why {{carrier_name}}:**
+Over the past {{relationship_years}} years, {{carrier_name}} has consistently performed in the top tier of our carrier portfolio. Specifically:
+- {{otd_percentage}} OTD (vs. portfolio average of {{portfolio_avg}}%)
+- {{tender_acceptance}} tender acceptance (vs. {{portfolio_avg_tender}}% average)
+- Exceptional communication and problem-resolution responsiveness
+
+**What We're Proposing:**
+1. **Volume commitment:** Increase {{carrier_name}}'s share of our total freight from {{current_share}}% to {{proposed_share}}%, representing approximately {{proposed_spend}} in annual freight spend.
+2. **Multi-year agreement:** 24-month contract with pre-agreed annual escalators tied to {{escalator_index}}, replacing the annual RFP cycle for your lanes.
+3. **Operational integration:** Implement real-time tracking integration (API), shared KPI dashboard, and quarterly executive business reviews.
+4. **Growth collaboration:** As {{our_company}} expands into {{growth_markets}}, {{carrier_name}} would be our first-call carrier for new lanes in your network.
+
+**What We'd Need in Return:**
+1. Rate alignment: Competitive pricing reflecting the volume commitment and multi-year certainty (we're targeting rates within {{target_range}}% of DAT contract benchmark).
+2. Service guarantee: {{otd_target}}% OTD and {{tender_target}}% tender acceptance with quarterly review.
+3. Dedicated account management: A named contact who knows our operations, our customers, and our seasonal patterns.
+4. Capacity priority: During peak season or disruption events, {{our_company}} freight receives priority dispatch from your operations team.
+
+I'd welcome the opportunity to discuss this in a meeting with your leadership team. Would {{proposed_meeting_date}} work for an in-person session at {{proposed_location}}?
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 11. Detention Dispute Communication
+
+**Channel:** Email with supporting documentation attached
+**Audience:** Carrier billing / accounts receivable team, cc carrier account manager
+**Tone:** Factual and cooperative. Detention disputes get adversarial quickly — lead with data and a willingness to pay what's legitimate while disputing what's not.
+
+---
+
+**Subject:** `Detention Invoice Dispute — PRO# {{pro_number}} / {{dispute_date}}`
+
+{{carrier_contact}},
+
+We've reviewed the detention invoice for PRO# {{pro_number}} ({{lane_origin}} to {{lane_destination}}, delivered {{delivery_date}}) and have identified discrepancies between the invoiced detention and our facility records.
+
+**Your Invoice:**
+- Driver arrival: {{carrier_arrival_time}}
+- Departure: {{carrier_departure_time}}
+- Total detention billed: {{billed_detention_hours}} hours at ${{detention_rate}}/hr = {{detention_amount}}
+
+**Our Records:**
+- Driver check-in at guard shack: {{our_checkin_time}}
+- Dock door assigned: {{dock_assign_time}}
+- Loading/unloading complete (BOL signed): {{bol_sign_time}}
+- Free time: {{free_time_hours}} hours per contract Section {{contract_section}}
+
+**Discrepancy Analysis:**
+- The driver arrived {{early_minutes}} minutes before the scheduled appointment of {{appointment_time}}. Per our contract, detention begins at the later of appointment time or arrival time — not early arrival time.
+- Our records show actual dock dwell time (from check-in to BOL signature) of {{actual_dwell}} hours, of which {{free_time_hours}} hours is free time. Billable detention per our records: {{adjusted_detention}} hours.
+
+**Our Proposed Resolution:**
+We'll pay {{adjusted_amount}} ({{adjusted_detention}} hours × ${{detention_rate}}/hr) against this invoice. If you believe our records are inaccurate, please provide driver GPS or ELD data showing dock arrival and departure times, and we'll reconcile.
+
+We want to get this right for both of us. If detention on this lane is a recurring issue, I'd welcome a discussion about adjusting appointment scheduling or implementing a drop-trailer program to address the root cause.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 12. Accessorial Challenge
+
+**Channel:** Email
+**Audience:** Carrier billing / pricing team, cc carrier account manager
+**Tone:** Measured and evidence-based. Accessorial disputes are high-volume, low-dollar events that can poison a relationship if handled aggressively. Focus on accuracy, not accusation.
+
+---
+
+**Subject:** `Accessorial Charge Review — {{accessorial_type}} | PRO# {{pro_number}}`
+
+{{carrier_contact}},
+
+We're reviewing an accessorial charge on PRO# {{pro_number}} ({{lane_origin}} to {{lane_destination}}, {{delivery_date}}) and need clarification before processing payment.
+
+**Charge in Question:**
+- Accessorial type: {{accessorial_type}}
+- Amount: ${{accessorial_amount}}
+- Invoice reference: {{invoice_number}}
+
+**Our Concern:**
+{{concern_detail}}
+
+Per our Transportation Agreement (Section {{contract_section}}, Accessorial Schedule Item {{schedule_item}}), {{accessorial_type}} charges apply when {{contract_condition}}. Based on the BOL and delivery receipt for this shipment, {{evidence_detail}}.
+
+**Supporting Documentation (attached):**
+- BOL showing {{bol_detail}}
+- Delivery receipt showing {{pod_detail}}
+- Rate confirmation with accessorial schedule reference
+
+**Requested Action:**
+Please review the charge against the attached documentation and either (a) confirm the charge with additional supporting evidence we may not have, or (b) issue a credit memo for ${{accessorial_amount}} against invoice {{invoice_number}}.
+
+If this accessorial category is becoming a recurring issue on this lane, I'd like to discuss whether there's an operational adjustment (at either end) that could prevent these charges from accruing.
+
+Thank you for your prompt review.
+
+Best regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## Usage Guidelines
+
+### Tone Calibration by Relationship Status
+
+| Relationship Status | Appropriate Templates | Tone Adjustment |
+|--------------------|----------------------|-----------------|
+| New carrier (< 6 months) | Onboarding welcome, rate negotiation opening, market rate discussion | More formal, set clear expectations, be specific about standards |
+| Established carrier (6-24 months) | All templates | Standard professional tone, data-driven, collaborative |
+| Strategic partner (2+ years, top tier) | Performance review positive, partnership proposal, market rate discussion | More collegial, emphasize growth opportunity, share more operational context |
+| Underperforming carrier | Performance review corrective, warning letter, exit notification | Strictly professional, document everything, focus on facts and data |
+| Carrier in dispute | Detention dispute, accessorial challenge, warning letter | Factual and neutral, avoid emotional language, always propose a resolution path |
+
+### Communication Channel Selection
+
+| Situation | Primary Channel | When to Escalate Channel |
+|-----------|----------------|------------------------|
+| Rate discussion (routine) | Email → phone follow-up | If email exchange exceeds 3 rounds without resolution |
+| Performance review (positive) | Email + QBR meeting | N/A — always share good news broadly |
+| Performance review (corrective) | Email first (documentation), then phone/meeting | If carrier doesn't respond within 5 business days |
+| Warning letter | Formal email with read receipt | If carrier doesn't respond within 3 business days, follow up via carrier VP phone call |
+| Exit notification | Formal email + same-day phone call | N/A — always deliver exit decisions via both channels |
+| Detention/accessorial dispute | Email with documentation | If not resolved in 15 business days, escalate to carrier account manager |
+| Partnership proposal | Formal letter/email → in-person meeting | N/A — partnership proposals require in-person discussion |
diff --git a/web-app/public/skills/carrier-relationship-management/references/decision-frameworks.md b/web-app/public/skills/carrier-relationship-management/references/decision-frameworks.md
new file mode 100644
index 00000000..bf8a4ac8
--- /dev/null
+++ b/web-app/public/skills/carrier-relationship-management/references/decision-frameworks.md
@@ -0,0 +1,534 @@
+# Decision Frameworks — Carrier Relationship Management
+
+This reference provides detailed decision trees, scoring matrices, negotiation models,
+and strategic frameworks for managing carrier portfolios, negotiating freight rates,
+running RFPs, and making allocation decisions. It is loaded on demand when the agent
+needs to make or recommend nuanced carrier relationship decisions.
+
+All thresholds, rate assumptions, and market benchmarks reflect US domestic freight
+operations across TL, LTL, intermodal, and brokerage. Adjust for regional markets
+and current cycle position.
+
+---
+
+## 1. Rate Negotiation Strategy
+
+### 1.1 Pre-Negotiation Intelligence Gathering
+
+Before entering any rate negotiation, assemble a lane-level data package for each
+lane under discussion. Negotiating without data is guessing; carriers always have
+better data about their own costs than you do about market rates.
+
+#### Data Assembly Checklist
+
+| Data Point | Source | Purpose |
+|-----------|--------|---------|
+| Current contract rate (linehaul + FSC + avg accessorials) | TMS / rate management system | Establish baseline total cost |
+| DAT 90-day lane average (spot and contract) | DAT RateView | Market benchmark for shipper leverage |
+| Greenscreens carrier-specific rate intelligence | Greenscreens.ai | Carrier-specific pricing behavior and predicted pricing |
+| Your volume on this lane (loads/week, annual loads) | TMS shipment history | Volume leverage — carriers price based on density |
+| Carrier's current tender acceptance rate on this lane | TMS acceptance data | Indicator of whether current rate is below carrier's floor |
+| Carrier's OTD and claims performance on this lane | Carrier scorecard | Service quality justification for rate position |
+| Competitor carrier bids (from recent RFP or spot activity) | RFP results / spot tender logs | Alternative pricing to create competitive tension |
+| Diesel price trend and DOE forecast | DOE Weekly Retail Diesel | FSC modeling across price scenarios |
+| Seasonal volume forecast for the lane | Demand planning / sales forecast | Carrier values volume predictability — share forecasts to build trust |
+
+### 1.2 Total Cost Modeling
+
+Never negotiate linehaul in isolation. Model total cost per shipment across diesel
+price scenarios to expose hidden costs and FSC manipulation.
+
+#### Total Cost Formula
+
+```
+Total Cost per Shipment = Linehaul Rate
+ + Fuel Surcharge (at given diesel price)
+ + Expected Detention (avg hours × rate × frequency)
+ + Expected Accessorials (liftgate, residential, etc. × frequency)
+ + Reweigh/Reclass Fees (LTL — frequency × cost)
+ + Payment Term Cost (if offering quick-pay discount)
+```
+
+#### Diesel Price Scenario Modeling
+
+For every carrier proposal, calculate total cost at three diesel price points:
+
+| Scenario | Diesel Price | Purpose |
+|----------|-------------|---------|
+| Low | $3.25/gallon | Tests carrier's FSC floor — does the FSC go to zero or maintain a minimum? |
+| Current | Current DOE average | Apples-to-apples comparison with other carriers |
+| High | $4.50/gallon | Exposes aggressive FSC schedules that inflate cost disproportionately |
+
+**Example — Comparing Two TL Carrier Proposals (Chicago to Dallas, ~920 miles):**
+
+```
+Carrier A: Linehaul $2.10/mi, FSC base $3.50, $0.01/mi per $0.05 diesel increase
+Carrier B: Linehaul $1.95/mi, FSC base $3.00, $0.015/mi per $0.05 diesel increase
+
+At diesel $3.50:
+ Carrier A: ($2.10 × 920) + ($0.00 FSC) = $1,932
+ Carrier B: ($1.95 × 920) + ($0.015 × 10 increments × 920) = $1,794 + $138 = $1,932
+
+At diesel $4.50:
+ Carrier A: ($2.10 × 920) + ($0.01 × 20 × 920) = $1,932 + $184 = $2,116
+ Carrier B: ($1.95 × 920) + ($0.015 × 30 × 920) = $1,794 + $414 = $2,208
+
+Carrier B is $92 more expensive at high diesel despite a $0.15/mi lower linehaul.
+The aggressive FSC base ($3.00 vs. $3.50) and steeper increment ($0.015 vs. $0.01)
+make Carrier B the more expensive option when fuel prices rise.
+```
+
+### 1.3 Negotiation Positioning by Market Cycle
+
+The freight market cycle determines your leverage. Negotiate differently in each phase:
+
+#### Shipper-Favorable Market (Capacity Surplus)
+
+Indicators: DAT load-to-truck ratio <3:1, OTRI <5%, spot rates below contract by >10%.
+
+| Tactic | Detail |
+|--------|--------|
+| Push for rate reductions | Target 5-12% reduction on lanes where your rate exceeds DAT contract benchmark by >10% |
+| Extend contract terms | Lock favorable rates for 18-24 months instead of the standard 12. Carriers will accept longer terms to secure volume during a downturn |
+| Negotiate accessorial caps | Push for detention free time of 3 hours (instead of standard 2). Negotiate liftgate and residential fees down 15-20% |
+| Add service commitments | Require 95% OTD and 92% tender acceptance as contract terms with remedy clauses (rate credits for non-performance) |
+| Don't over-squeeze | A carrier losing money on your lanes will exit when the market turns. Leave enough margin for the carrier to cover their variable costs + a thin margin. A carrier hauling your freight at $0.05/mile below their cost will be the first to reject tenders when demand returns |
+
+#### Carrier-Favorable Market (Capacity Shortage)
+
+Indicators: DAT load-to-truck ratio >6:1, OTRI >12%, spot rates above contract by >15%.
+
+| Tactic | Detail |
+|--------|--------|
+| Protect volume commitments | Offer volume guarantees (minimum loads/week) in exchange for capacity commitments. Carriers in a tight market prioritize shippers who provide consistent, guaranteed volume |
+| Accept moderate rate increases | A 5-8% increase is reasonable when the market has moved 15-20%. Refusing all increases pushes carriers to more profitable freight |
+| Accelerate payment terms | Offer 15-day or quick-pay terms (vs. standard 30-day) as a non-rate incentive. Carriers are cash-constrained in tight markets — faster payment is worth 2-3% rate equivalent |
+| Improve shipper operations | Reduce driver detention, offer drop-trailer programs, ensure consistent dock scheduling. Every operational improvement makes your freight more attractive relative to competitors |
+| Negotiate multi-year with escalators | Lock base rates for 24 months with a pre-agreed annual escalator (3-5%) tied to a cost index. Protects against further rate spikes while giving the carrier predictability |
+
+#### Transitional Market
+
+Indicators: Mixed signals — OTRI between 5-12%, spot-contract spread narrowing.
+
+| Tactic | Detail |
+|--------|--------|
+| Benchmark aggressively | Transition markets are when benchmark data matters most. Carriers will argue the market is tighter than it is (if transitioning to carrier-favorable) or softer (if transitioning to shipper-favorable). Let the data decide |
+| Run mini-bids | Instead of full RFPs, run targeted mini-bids on your bottom-performing 20% of lanes. This creates competitive pressure without disrupting your entire routing guide |
+| Lock strategic lanes | Secure rates on your highest-volume, most critical lanes first. Leave secondary lanes flexible to benefit from continued market movement |
+
+### 1.4 Concession Strategy
+
+When a negotiation reaches an impasse, use structured concessions to find agreement
+without giving away core economics:
+
+#### Concession Priority (Give These First — They Cost Less Than They're Worth)
+
+| Concession | Your Cost | Carrier Value | When to Offer |
+|-----------|-----------|---------------|---------------|
+| Volume commitment (guarantee minimum loads/week) | Low — you were shipping this volume anyway | High — predictable volume improves carrier utilization | When carrier won't budge on rate |
+| Faster payment terms (Net 15 vs. Net 30) | Moderate — accelerates cash outflow by 15 days | High — carriers are always cash-constrained | When spread between positions is <5% |
+| Drop-trailer program | Moderate — requires trailer parking space | Very High — eliminates driver detention, improves asset utilization | When carrier cites detention as cost driver |
+| Consistent appointment scheduling | Low — operational discipline | High — drivers can plan routes and HOS around fixed appointments | When carrier cites unpredictable scheduling |
+| Multi-year contract with escalators | Low — locks rate but adds predictability | High — long-term revenue certainty | When carrier values stability over short-term optimization |
+
+#### Concession Boundary (Never Give These Away)
+
+| Element | Why It's Non-Negotiable |
+|---------|----------------------|
+| FSC table transparency | Opaque FSC schedules are a carrier margin tool, not a cost recovery mechanism |
+| Accessorial audit rights | You must be able to verify every accessorial charge against the BOL and contract |
+| Service-level remedies | A contract without OTD and tender acceptance minimums is just a rate sheet with no accountability |
+| Right to re-bid lanes annually | Market conditions change — you need the ability to benchmark and adjust |
+| Carrier compliance requirements (FMCSA, insurance) | Safety and legal compliance are not negotiable under any market condition |
+
+---
+
+## 2. Carrier Portfolio Optimization
+
+### 2.1 Portfolio Health Assessment
+
+Run this assessment quarterly to identify optimization opportunities:
+
+#### Step 1: Carrier Concentration Analysis
+
+For each lane in your top 50 by volume:
+
+| Metric | Target | Action If Out of Range |
+|--------|--------|----------------------|
+| Primary carrier volume share | 50-70% | If >70%: diversify. If <50%: routing guide isn't being followed — investigate ops compliance |
+| Number of active carriers on lane | 2-4 | If <2: single point of failure risk. If >4: volume is too fragmented for carriers to care |
+| Backup carrier last-used date | Within 90 days | If >90 days: the backup is stale. Run a test load to confirm the carrier can still service the lane |
+| Spot freight % on lane | <15% | If >15%: routing guide is failing. Either rates are below market or tender acceptance is low |
+
+#### Step 2: Carrier Scorecard Triage
+
+Rank all active carriers by composite score (weighted: OTD 30%, tender acceptance 25%,
+claims ratio 20%, invoice accuracy 15%, communication/responsiveness 10%).
+
+| Tier | Score Range | Action |
+|------|------------|--------|
+| A — Strategic Partners | ≥90% | Increase allocation, offer longer-term contracts, invest in integration (EDI, API), invite to annual business review |
+| B — Reliable Performers | 75-89% | Maintain current allocation, monitor for improvement or decline, include in next RFP |
+| C — Underperformers | 60-74% | Issue corrective action plan with 60-day timeline. Reduce allocation by 25%. If no improvement at 60 days, reduce by another 25% |
+| D — Exit Candidates | <60% | Initiate carrier exit process (see §2.4). Stop new lane awards immediately. Allow existing commitments to run out |
+
+#### Step 3: Spend Optimization
+
+| Analysis | Method | Target |
+|----------|--------|--------|
+| Rate-vs-market alignment | Compare contract rates to DAT contract lane average for each active lane | Within ±8% of DAT. If >+15%, renegotiate. If <-10%, carrier may be underpriced and at exit risk |
+| Accessorial spend ratio | Total accessorials / total linehaul spend | <8% of total spend. If >12%, audit accessorial billing and address root causes (detention, reclass) |
+| Spot premium tracking | (Avg spot rate - avg contract rate) / avg contract rate | <15% premium. If >25%, routing guide coverage is insufficient |
+| Small shipment consolidation | Identify LTL shipments to same destination within 48-hour windows | Consolidate into TL or multi-stop when LTL spend on a lane exceeds $5K/month |
+
+### 2.2 Routing Guide Design
+
+The routing guide is your operational expression of carrier strategy. A well-designed
+guide executes itself; a poorly designed one requires constant manual intervention.
+
+#### Structure by Lane Volume
+
+| Lane Volume | Guide Depth | Primary % | Secondary % | Tertiary % |
+|-------------|------------|-----------|-------------|------------|
+| >10 loads/week | 3-4 carriers | 50-60% | 25-30% | 10-20% |
+| 5-10 loads/week | 3 carriers | 55-65% | 25-30% | 10-15% |
+| 2-5 loads/week | 2-3 carriers | 60-75% | 25-40% | — |
+| <2 loads/week | 2 carriers (or 1 + broker) | 70-80% | 20-30% | — |
+
+#### Tender Waterfall Logic
+
+```
+1. Tender to Primary Carrier
+ → If accepted within 2 hours: assign
+ → If rejected or no response:
+
+2. Tender to Secondary Carrier
+ → If accepted within 1.5 hours: assign
+ → If rejected or no response:
+
+3. Tender to Tertiary Carrier
+ → If accepted within 1 hour: assign
+ → If rejected or no response:
+
+4. Move to Spot Procurement
+ → Post to carrier board or contact preferred spot carriers
+ → Set rate ceiling at tertiary contract rate + 15%
+ → If no coverage within 2 hours at ceiling: escalate to manager
+```
+
+#### Routing Guide Maintenance Cadence
+
+| Activity | Frequency | Owner |
+|----------|-----------|-------|
+| Review lane-level tender acceptance rates | Weekly | Transportation Analyst |
+| Adjust carrier allocation based on performance trends | Monthly | Transportation Manager |
+| Full routing guide audit (dead lanes, stale backups, rate alignment) | Quarterly | Director of Transportation |
+| Complete routing guide rebuild (RFP) | Annually or after major volume/network change | VP Supply Chain + Procurement |
+
+### 2.3 Carrier Onboarding Process
+
+A standardized onboarding process protects against compliance risk and sets performance
+expectations from day one.
+
+#### Onboarding Checklist
+
+| Step | Timeline | Owner | Verification Method |
+|------|----------|-------|-------------------|
+| FMCSA authority verification (active MC#, property authorization) | Day 1 | Compliance | SAFER website direct lookup |
+| Insurance verification ($1M+ auto liability, $100K cargo, workers comp) | Day 1 | Compliance | FMCSA Insurance tab + certificate of insurance on file |
+| Safety rating and CSA score review | Day 1 | Compliance | SAFER + CSA BASIC percentiles — flag if Unsafe Driving or HOS >75th percentile |
+| W-9 and payment setup | Days 1-3 | AP/Finance | IRS TIN matching |
+| Carrier agreement execution (rate confirmation template, accessorial schedule, insurance requirements, performance expectations) | Days 3-5 | Transportation Manager | Signed agreement on file |
+| TMS/EDI setup (210, 214, 990 transactions if applicable) | Days 5-10 | IT/Integration | Test transaction confirmation |
+| Initial rate confirmation for awarded lanes | Days 5-7 | Transportation Manager | Countersigned rate confirmation per lane |
+| 30-day trial loads (minimum 5 loads before full allocation) | Days 10-40 | Operations | Trial performance review at day 30 — OTD, communication, billing accuracy |
+| Quarterly compliance re-verification (ongoing) | Every 90 days | Compliance | Automated FMCSA/insurance monitoring via Highway, RMIS, or Carrier411 |
+
+### 2.4 Carrier Exit Process
+
+Exiting a carrier requires planning to avoid service disruption on lanes they currently serve.
+
+#### Decision: Immediate vs. Managed Exit
+
+| Scenario | Exit Type | Timeline |
+|----------|-----------|----------|
+| FMCSA authority revoked or insurance lapsed | Immediate — stop tendering now | 0 days |
+| Confirmed double-brokering | Immediate — stop tendering, document evidence | 0 days |
+| Unsatisfactory safety rating | Immediate — stop tendering | 0 days |
+| Corrective action plan failed (service metrics) | Managed — transition volume over 30-60 days | 30-60 days |
+| Rate renegotiation failed (carrier above market) | Managed — transition after RFP award | 60-90 days |
+| Strategic portfolio simplification (too many carriers) | Managed — transition volume at next contract renewal | 90-120 days |
+
+#### Managed Exit Steps
+
+1. **Identify replacement capacity** — ensure backup carriers on every lane the exiting carrier serves can absorb the volume. Run test loads if backups haven't been used in 90+ days.
+2. **Communicate transparently** — tell the carrier why. "Your OTD has been below 85% for the last quarter despite our corrective action plan. We need to shift this volume to a carrier that can meet our service requirements." Burning bridges is unnecessary — carriers improve, get acquired, or re-enter your network in future cycles.
+3. **Transition volume gradually** — reduce allocation by 25% per week over 4 weeks. Abrupt volume loss can damage the carrier's operations (especially small carriers who built capacity around your freight).
+4. **Settle outstanding claims and invoices** — ensure all open claims are filed and all invoices are paid or disputed before the relationship goes dormant. Unresolved financial items turn a professional exit into a adversarial one.
+5. **Retain the carrier record** — do not delete the carrier from your systems. Document exit reasons, performance history, and corrective actions. If the carrier improves or changes ownership, you may onboard them again in 12-24 months.
+
+---
+
+## 3. RFP Execution Framework
+
+### 3.1 RFP Timeline
+
+| Phase | Duration | Activities |
+|-------|----------|-----------|
+| 1 — Pre-RFP Analysis | Weeks 1-2 | Analyze 12 months of shipment data, identify lanes for bid, benchmark current rates against DAT/Greenscreens, set cost and service targets, define evaluation criteria and weightings |
+| 2 — RFP Development | Weeks 3-4 | Build lane-level bid package with volume, equipment, and service requirements. Define accessorial schedule, insurance minimums, and contract terms. Prepare carrier communication and Q&A timeline |
+| 3 — Carrier Outreach | Week 5 | Distribute RFP to incumbent carriers + 5-10 prospective carriers identified through market research or peer referrals. Allow 2-3 weeks for bid submission |
+| 4 — Bid Collection | Weeks 5-7 | Answer carrier questions (standardize responses via Q&A document shared with all bidders). Remind non-respondents at the halfway mark |
+| 5 — Bid Analysis | Weeks 8-9 | Score bids using weighted criteria (see §3.2). Model total cost per lane. Rank carriers per lane. Identify negotiation targets (carriers close to award threshold) |
+| 6 — Negotiation | Weeks 9-10 | Final-round negotiation with top 2-3 carriers per lane. Focus on lanes where top bids are within 5% of each other — these are negotiable. Do not renegotiate with the low bidder on lanes where they're already 10%+ below the field |
+| 7 — Award | Week 11 | Notify winning carriers with lane awards and effective dates. Notify losing carriers with feedback (if they ask). Begin rate confirmation process |
+| 8 — Implementation | Weeks 11-12 | Load new rates in TMS. Update routing guide. Run 2-week parallel period with old and new guides. Resolve any issues before full cutover |
+
+### 3.2 Bid Evaluation Scoring
+
+#### Criteria Weighting
+
+| Criterion | Weight | Data Source | Scoring Method |
+|-----------|--------|-------------|---------------|
+| Rate competitiveness | 40% | Bid response | Normalize to 100-point scale where lowest total cost (linehaul + modeled FSC + expected accessorials) = 100, and each 1% above lowest = -3 points |
+| Service history / OTD | 25% | Carrier scorecard (for incumbents) or reference checks (for new carriers) | 100 points for ≥96% OTD, 80 for 93-95%, 60 for 90-92%, 40 for 85-89%, 0 for <85% |
+| Capacity commitment | 20% | Bid response (stated tender acceptance commitment, equipment availability, driver count on the lane) | 100 points for ≥95% acceptance commitment with driver count evidence, scaled down based on commitment level and supporting evidence |
+| Operational fit | 15% | Bid response + due diligence | Technology integration (EDI/API), FMCSA compliance score, driver domicile proximity, equipment match, prior relationship quality |
+
+#### Example Scoring — Lane CHI-DAL (5 loads/week)
+
+```
+ Rate (40%) Service (25%) Capacity (20%) Ops Fit (15%) Total
+Carrier A: 85 × 0.40 95 × 0.25 90 × 0.20 80 × 0.15 = 88.75
+Carrier B: 100 × 0.40 70 × 0.25 85 × 0.20 75 × 0.15 = 86.75
+Carrier C: 92 × 0.40 90 × 0.25 80 × 0.20 90 × 0.15 = 89.10
+
+Award: Carrier C as primary (89.10), Carrier A as secondary (88.75).
+Carrier B has lowest rate but weakest service — appropriate as tertiary.
+```
+
+### 3.3 Incumbent vs. New Carrier Evaluation
+
+Incumbents have data; new carriers have promises. Adjust evaluation accordingly:
+
+| Factor | Incumbent | New Carrier |
+|--------|-----------|-------------|
+| Service history | Use actual OTD, claims, tender acceptance from your data | Use carrier's reported statistics + 2-3 reference checks from similarly sized shippers |
+| Rate credibility | High — they know the lane and are pricing from experience | Moderate — new carriers may under-bid to win then renegotiate after award. Discount new-carrier bids by 3-5% for risk |
+| Implementation risk | Low — already in your systems, familiar with your operations | Moderate — onboarding takes 2-3 weeks, first-month performance often lags |
+| Competitive tension value | Moderate — they know you know their performance | High — new entrants create competitive pressure that benefits your entire portfolio |
+
+### 3.4 Post-RFP Rate Lock and Market Movement
+
+Your RFP award locks rates for 12 months (typical). But the market moves. Build
+these protections into the contract:
+
+- **Market-based reopener clause:** If DAT contract lane average moves >15% from the awarded rate for 60+ consecutive days, either party may request a rate review. This protects you in a softening market and protects the carrier in a tightening market.
+- **Volume band pricing:** If your actual volume on a lane falls below 75% or exceeds 125% of the RFP-stated volume, rates are subject to renegotiation. This prevents you from losing volume and still paying volume-discounted rates, or from flooding a carrier with unanticipated volume at rates that don't cover their incremental costs.
+- **Annual escalator option:** For multi-year contracts, build in a pre-agreed escalator (typically 2-4% annually) tied to a published index (PPI-Truck Transportation, DAT National Average). This avoids the disruption of an annual RFP while keeping rates aligned with costs.
+
+---
+
+## 4. Contract vs. Spot Market Decision Framework
+
+### 4.1 Decision Matrix
+
+| Condition | Recommendation | Rationale |
+|-----------|---------------|-----------|
+| Lane volume >3 loads/week, consistent year-round | Contract | Carrier will invest in dedicated capacity for predictable volume |
+| Lane volume 1-3 loads/week, seasonal | Contract for peak months, spot for off-peak | Avoids paying contract rates during low-demand months |
+| Lane volume <1 load/week, unpredictable | Spot or broker relationship | Carriers won't commit capacity to inconsistent volume; contract rates will be inflated to cover utilization risk |
+| Spot rates are >15% below contract rate for 60+ days | Move 20-30% of volume to spot | Market has moved significantly — capture savings while maintaining contract relationship |
+| Spot rates are >15% above contract rate | Stay on contract, honor volume commitments | This is when contract value materializes — your carriers are holding rates below market for you. Reward their commitment by giving them your full volume |
+| Customer requires guaranteed transit time | Contract with service-level agreement | Spot carriers have no SLA obligation — you can't guarantee what you can't control |
+| Lane serves a production line or retail replenishment | Contract with primary and secondary carriers | Risk of spot market non-coverage is unacceptable for critical supply chains |
+| New lane with unknown volume pattern | Spot for 60-90 days, then evaluate | Gather data before committing to a contract rate that may not reflect actual demand |
+
+### 4.2 Spot Market Best Practices
+
+When procuring on the spot market:
+
+- **Set a rate ceiling** before posting. Use your tertiary contract rate + 15% as the maximum. Anything above that threshold requires manager approval.
+- **Vet the carrier** even for single loads. At minimum: FMCSA authority check, insurance verification, Carrier411 or Highway check for complaints. A 60-second screening prevents catastrophic outcomes (uninsured carrier, double-brokered load, stolen freight).
+- **Demand rate confirmation** before the truck arrives. Verbal agreements on spot loads are unenforceable. Get the rate confirmation signed with all accessorials, FSC, and detention terms specified.
+- **Track spot premium** meticulously. Report spot vs. contract spread weekly by lane. If any lane consistently shows >20% spot premium, your routing guide on that lane needs attention.
+
+---
+
+## 5. Carrier Onboarding and Offboarding Decision Trees
+
+### 5.1 Onboarding Decision Tree
+
+```
+New carrier candidate identified
+│
+├─ FMCSA authority check
+│ ├─ Authority inactive/revoked → REJECT (do not proceed)
+│ ├─ Authority <6 months old → PROCEED WITH CAUTION (new entrant risk)
+│ └─ Authority active, >12 months → PROCEED
+│
+├─ Insurance verification
+│ ├─ Auto liability <$1M → REJECT (below your minimum)
+│ ├─ Cargo insurance <$100K → NEGOTIATE (require $100K minimum)
+│ └─ Meets all minimums → PROCEED
+│
+├─ Safety assessment
+│ ├─ FMCSA Unsatisfactory rating → REJECT
+│ ├─ CSA BASIC >90th percentile on Unsafe Driving → REJECT
+│ ├─ CSA BASIC >75th percentile on any BASIC → FLAG for risk review
+│ └─ CSA acceptable → PROCEED
+│
+├─ Financial health check
+│ ├─ Broker bond revoked or reduced → REJECT (if broker)
+│ ├─ Recent insurance underwriter changes (3+ in 12 months) → FLAG
+│ ├─ Driver complaints on Carrier411 re: pay → FLAG for monitoring
+│ └─ No red flags → PROCEED
+│
+├─ Operational fit
+│ ├─ No EDI/API capability and your volume requires it → NEGOTIATE timeline
+│ ├─ Equipment doesn't match requirements → REJECT for this lane
+│ └─ Operational fit confirmed → PROCEED
+│
+└─ ONBOARD: Execute carrier agreement, set up in TMS, run trial loads
+```
+
+### 5.2 Offboarding Decision Tree
+
+```
+Carrier performance or compliance concern identified
+│
+├─ Compliance failure (authority, insurance, safety)
+│ ├─ Authority revoked → IMMEDIATE EXIT (stop tendering today)
+│ ├─ Insurance lapsed → IMMEDIATE SUSPENSION (reinstate if corrected in 48 hrs)
+│ ├─ Unsatisfactory safety rating → IMMEDIATE EXIT
+│ └─ CSA scores worsened into >90th percentile → 30-DAY REVIEW with carrier
+│
+├─ Service performance failure
+│ ├─ OTD <85% for 60 days
+│ │ ├─ First occurrence → CORRECTIVE ACTION PLAN (60-day timeline)
+│ │ └─ Second occurrence after CAP → MANAGED EXIT (30-60 days)
+│ │
+│ ├─ Tender acceptance <70% for 30 days
+│ │ ├─ Carrier communicating, rate issue → RENEGOTIATE
+│ │ └─ Carrier non-responsive → MANAGED EXIT (30 days)
+│ │
+│ └─ Claims ratio >2% for 90 days → CORRECTIVE ACTION PLAN
+│
+├─ Integrity failure
+│ ├─ Double-brokering confirmed → IMMEDIATE EXIT + document for industry
+│ ├─ Insurance fraud (forged certificate) → IMMEDIATE EXIT + report to FMCSA
+│ └─ Systematic overbilling (>5% overcharge pattern) → CORRECTIVE ACTION, exit if not resolved in 30 days
+│
+└─ Strategic portfolio decision
+ ├─ Carrier redundant (consolidating) → MANAGED EXIT at contract renewal
+ └─ Carrier non-competitive on rate → INCLUDE IN NEXT RFP (give them a chance to compete)
+```
+
+---
+
+## 6. Market Cycle Positioning
+
+### 6.1 Cycle Identification Framework
+
+The freight market follows a pattern of loosening and tightening that repeats every
+2-3 years. Identifying where you are in the cycle determines your negotiation stance,
+contract strategy, and portfolio decisions.
+
+#### Leading Indicators (Signal Direction 3-6 Months Ahead)
+
+| Indicator | Source | Shipper-Favorable Signal | Carrier-Favorable Signal |
+|-----------|--------|------------------------|------------------------|
+| Class 8 truck orders | ACT Research, FTR | Rising (new capacity entering) | Falling (capacity leaving or not being replaced) |
+| FMCSA new authority applications | FMCSA data | Rising (new carriers entering) | Falling (fewer new entrants, possibly exits increasing) |
+| Diesel price trend | DOE | Falling (lowers carrier costs, reduces FSC) | Rising sharply (squeezes small carriers, may cause exits) |
+| Manufacturing PMI | ISM | <50 (contraction, less freight demand) | >55 (expansion, freight demand growing) |
+| Retail inventory-to-sales ratio | Census Bureau | Rising (retailers overstocked, less reorder freight) | Falling (retailers restocking, generating freight demand) |
+
+#### Coincident Indicators (Confirm Current Position)
+
+| Indicator | Source | Shipper-Favorable | Carrier-Favorable |
+|-----------|--------|------------------|------------------|
+| DAT load-to-truck ratio | DAT | <3:1 (more trucks than loads) | >6:1 (more loads than trucks) |
+| Outbound Tender Rejection Index (OTRI) | FreightWaves SONAR | <5% (carriers accepting almost everything) | >12% (carriers cherry-picking profitable freight) |
+| Spot rate trend (13-week) | DAT, Greenscreens | Declining or flat | Rising >5% over 13 weeks |
+| Your tender acceptance rate | TMS data | >95% across portfolio | <85% across portfolio |
+
+### 6.2 Strategic Actions by Cycle Phase
+
+| Phase | Duration (typical) | Rate Action | Contract Action | Portfolio Action |
+|-------|-------------------|-------------|-----------------|-----------------|
+| Early recovery (market tightening) | 3-6 months | Lock rates on top 30% of lanes before carriers reprice | Extend expiring contracts 6-12 months at current rates | Onboard 2-3 new carriers for surge capacity |
+| Peak (tight market) | 6-12 months | Minimize rate exposure — renegotiate only what's necessary | Honor commitments — this builds carrier trust for the downturn | Increase allocation to asset carriers (brokers get unreliable in tight markets) |
+| Early softening (market loosening) | 3-6 months | Run mini-bids on your worst-performing 20% of lanes | Let short-term contracts expire — rebid at new market rates | Evaluate carrier portfolio for exits (weak performers lose leverage to resist) |
+| Trough (soft market) | 6-12 months | Full RFP — maximum competitive tension, target 8-15% savings | Sign 18-24 month contracts to lock favorable rates | Consolidate to fewer, stronger carriers (volume concentration maximizes discount) |
+
+---
+
+## Appendix A — Quick-Reference Decision Cards
+
+### Card 1: "Should I renegotiate this carrier's rate?"
+
+```
+IF contract rate > DAT contract average + 15% for 60+ days → YES
+IF carrier tender acceptance < 75% for 30+ days → YES (rate is likely below their floor)
+IF your volume dropped >25% from what was committed → YES (proactive, before carrier notices)
+IF spot market is >15% below your contract for 60+ days → YES
+IF carrier's service scores are in top 10% of your portfolio → NO (pay for quality)
+IF contract expires in <90 days → WAIT for renewal negotiation
+```
+
+### Card 2: "How many carriers should I have on this lane?"
+
+```
+IF lane volume > 10 loads/week → 3-4 carriers
+IF lane volume 5-10/week → 3 carriers
+IF lane volume 2-5/week → 2-3 carriers
+IF lane volume < 2/week → 1 carrier + 1 broker backup
+IF lane is customer-critical (JIT, perishable, penalty clauses) → add 1 more carrier than volume alone suggests
+IF lane serves a single customer who is >20% of your revenue → NEVER fewer than 3
+```
+
+### Card 3: "Is this carrier financially healthy?"
+
+```
+CHECK FMCSA for active authority and current insurance → If either is lapsed, STOP
+CHECK insurance: has the underwriter changed 3+ times in 12 months? → RED FLAG
+CHECK Carrier411/CarrierOK: driver complaints about pay? → YELLOW FLAG
+CHECK: has the carrier's bond amount decreased? → RED FLAG (for brokers)
+CHECK: sudden decline in tender acceptance across all your lanes? → YELLOW FLAG
+IF 2+ yellow flags or 1+ red flag → REDUCE EXPOSURE incrementally, do not wait
+```
+
+### Card 4: "Should I go to spot market on this load?"
+
+```
+IF all routing guide carriers rejected → YES (no choice)
+IF spot rate < contract rate - 10% → YES (capture savings, track as data for renegotiation)
+IF lane is irregular (< 1 load/week) and no contract carrier → YES
+IF customer requires guaranteed transit and SLA → NO (stay on contract)
+IF you're in peak season and spot rates are 30%+ above contract → NO (honor contract, build carrier goodwill)
+ALWAYS: vet the spot carrier (FMCSA check, rate confirmation signed before dispatch)
+```
+
+---
+
+## Appendix B — Glossary
+
+| Term | Definition |
+|------|-----------|
+| BASIC | Behavior Analysis and Safety Improvement Categories — the seven CSA safety dimensions scored by FMCSA |
+| CAP | Corrective Action Plan — formal performance improvement plan with timeline and metrics |
+| CSA | Compliance, Safety, Accountability — FMCSA's carrier safety measurement system |
+| DAT | The largest spot market freight data provider (now DAT Freight & Analytics) |
+| DOE | Department of Energy — publishes weekly national average diesel prices used for FSC calculations |
+| EDI | Electronic Data Interchange — standardized electronic communication between shipper and carrier systems |
+| FSC | Fuel Surcharge — variable rate component indexed to diesel prices |
+| Greenscreens | AI-powered freight rate intelligence platform for benchmarking and predictive pricing |
+| MC# | Motor Carrier number — FMCSA-issued operating authority identifier |
+| OTRI | Outbound Tender Rejection Index — published by FreightWaves SONAR, measures % of electronic tenders rejected by carriers |
+| PPI | Producer Price Index — published by BLS, used as a cost escalator in multi-year contracts |
+| RMIS | Registry Monitoring Insurance Service — third-party carrier compliance monitoring platform |
+| RFP | Request for Proposal — formal bid process for awarding freight lanes to carriers |
+| SAFER | Safety and Fitness Electronic Records — FMCSA's public carrier database |
+| SCAC | Standard Carrier Alpha Code — 2-4 letter identifier for each carrier |
+| TMS | Transportation Management System — software for managing freight operations and carrier relationships |
diff --git a/web-app/public/skills/carrier-relationship-management/references/edge-cases.md b/web-app/public/skills/carrier-relationship-management/references/edge-cases.md
new file mode 100644
index 00000000..26426db4
--- /dev/null
+++ b/web-app/public/skills/carrier-relationship-management/references/edge-cases.md
@@ -0,0 +1,527 @@
+# Carrier Relationship Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex carrier management situations that don't resolve through standard decision frameworks.
+
+These edge cases represent the scenarios that separate experienced transportation managers from everyone else. Each involves competing priorities, incomplete information, relationship dynamics, and real financial exposure. They are structured to guide resolution when standard carrier management playbooks break down.
+
+---
+
+## How to Use This File
+
+When a carrier relationship situation doesn't fit a clean decision tree — when market dynamics create conflicting incentives, when carrier behavior signals something deeper than surface metrics show, or when the standard rate negotiation playbook produces a bad outcome — find the edge case below that most closely matches the situation. Follow the expert approach step by step.
+
+---
+
+### Edge Case 1: Capacity Squeeze During Hurricane Season — Balancing Spot Market Panic Against Strategic Positioning
+
+**Situation:**
+A national consumer goods manufacturer ships 120+ FTL loads per week across the Southeast. Hurricane Michaela has made landfall on the Gulf Coast, and FMCSA has issued an emergency declaration for FL, AL, MS, and LA. Your top 3 carriers in the region have pulled drivers off Florida and coastal Alabama routes. Your routing guide for 35 Southeast lanes is effectively dead — tender rejections are running 60%+ for the last 48 hours. Spot rates on lanes touching Florida have jumped from $2.80/mile to $6.50/mile. Your VP of Sales is calling because Walmart's DC in Lakeland, FL needs 8 loads of household cleaning products by Friday for hurricane response stocking, and your West Coast operations need 12 loads of raw materials moved out of Mobile, AL before the storm surge floods the port warehouse.
+
+The spot market is a feeding frenzy. Brokers are quoting $8,000 for a $3,200 lane. Your procurement team wants to pay whatever it takes. Your CFO wants to know why freight costs just tripled.
+
+**Why It's Tricky:**
+Paying panic rates on 35+ lanes for 7-10 days can cost $150K-$300K in incremental freight spend above your contract rates. But refusing to pay means freight doesn't move, Walmart doesn't get their hurricane response product (damaging a $40M annual relationship), and your Mobile warehouse potentially floods with $2M in raw materials sitting on the floor.
+
+The deeper problem: every shipper in the Southeast is bidding up the same shrinking carrier pool simultaneously. The carriers and brokers who covered your freight reliably at $2.80/mile last week are now selling that same capacity at $6.50 to the highest bidder — and your contract rates are irrelevant because force majeure clauses in most carrier agreements suspend rate obligations during declared emergencies.
+
+**Common Mistake:**
+Posting all 35 lanes to the spot market simultaneously at "market rate" and accepting the first truck that quotes. This guarantees you'll pay peak panic pricing on every load, attract the least reliable carriers (the quality carriers are already committed), and create a billing reconciliation nightmare when 35 different spot carriers each have different rate confirmations, detention terms, and accessorial structures.
+
+The second mistake: trying to enforce contract rates during a declared emergency. Your contract carriers aren't rejecting tenders to be adversarial — they literally can't get drivers into the affected area safely. Threatening to pull their contract lanes post-storm will earn you a reputation as a shipper who doesn't understand emergencies, and they'll remember at the next RFP.
+
+**Expert Approach:**
+1. Triage your 35 affected lanes immediately. Not all lanes are equal. Categorize into three tiers:
+ - **Tier 1 — Must Move (8-10 lanes):** Customer penalty exposure, perishable, safety stock at risk, or product at physical risk (the Mobile warehouse). These move at spot market rates, period.
+ - **Tier 2 — Should Move (12-15 lanes):** Standard replenishment, can tolerate 3-5 day delay without customer impact. Delay these loads until the initial panic subsides (spot rates typically drop 30-40% within 72 hours of landfall as the actual storm path becomes clear and unaffected corridors reopen).
+ - **Tier 3 — Can Wait (10-12 lanes):** Low urgency, large buffer stock at destination. Hold these until your contract carriers resume normal operations (typically 7-14 days post-storm for the directly affected region).
+
+2. For Tier 1 loads, do not post to open load boards. Instead, call your top 3 broker partners directly. Offer them a multi-load commitment: "I have 8 loads that need to move in the next 48 hours. I'll commit all 8 to you at $5,200/load if you can guarantee coverage." A broker getting 8 committed loads at $5,200 will prioritize you over single-load spot postings at $6,500 because the certainty of 8 loads is more valuable than the possibility of 8 individual loads at a higher rate.
+
+3. Activate regional carriers you've pre-positioned for exactly this scenario. Every experienced transportation manager maintains relationships with 3-5 small carriers in hurricane-prone regions who run owner-operator fleets. These carriers park their trucks inland before the storm and redeploy as soon as roads open. They're expensive ($4.50-$5.50/mile during events), but they're available when national carriers have pulled out.
+
+4. For the Mobile warehouse evacuation, consider a dedicated carrier or fleet provider rather than spot market. A fleet of 12 trucks from a single carrier coordinating an evacuation is operationally cleaner than 12 individual spot trucks arriving on different schedules. Contact your largest asset carrier and offer a premium ($4,800/load on a $3,200 lane) for dedicated fleet assignment over 48 hours. Frame it as: "We need a fleet solution, not 12 individual loads. Can you dedicate 12 power units for 48 hours?"
+
+5. After the storm: do not retroactively dispute the premium rates you paid. Document the event, the incremental cost, and the business justification. Present to the CFO as a weather event cost, not a freight rate failure. Then conduct a post-storm review: which carriers came through, which disappeared? Adjust your routing guide allocation to reward carriers who provided capacity during the crisis — those carriers earned the right to your best lanes in the next calm period.
+
+**Key Indicators:**
+- Tender rejection rates above 50% on regional lanes signal a network disruption, not individual carrier problems — adjust response accordingly
+- Spot rate spikes that exceed 2× contract rates within 48 hours indicate panic pricing, not a new market equilibrium — rates will retreat
+- Carriers communicating proactively about their capacity constraints during the event are your best long-term partners — track who calls you vs. who goes silent
+- FMCSA emergency declarations suspend HOS requirements, meaning available drivers can run more hours — some capacity will return within 48-72 hours as drivers extend their available drive time
+- Monitor NOAA track updates every 6 hours — storm path changes can open or close corridors and shift where capacity is available
+
+**Documentation Required:**
+- FMCSA emergency declaration documentation
+- Lane-by-lane triage classification with business justification
+- Spot rate confirmations for all Tier 1 loads
+- Multi-load commitment agreements with brokers
+- Carrier communication log (who contacted you, who you contacted, responses)
+- Total incremental freight cost calculation vs. normal contract rates
+- Post-event carrier performance assessment
+
+**Resolution Timeline:**
+- Hours 0-6: Lane triage, Tier 1 procurement initiated, Mobile evacuation fleet secured
+- Hours 6-24: Tier 1 loads dispatched, Tier 2 loads staged for delayed dispatch
+- Days 2-5: Spot rates begin normalizing, Tier 2 loads dispatched at reduced premiums
+- Days 5-14: Contract carriers resume normal operations, Tier 3 loads move at contract rates
+- Days 14-30: Post-event review, carrier performance assessment, routing guide adjustments
+
+---
+
+### Edge Case 2: Double-Brokering Discovery Mid-Relationship
+
+**Situation:**
+Your compliance analyst runs a quarterly audit and discovers that Pinnacle Logistics (MC-892431), a broker in your routing guide handling 15 loads/week across 6 Midwest lanes, has been double-brokering approximately 30% of your freight. The evidence: BOL driver names don't match Pinnacle's dispatched driver, truck numbers on PODs belong to carriers not in Pinnacle's disclosed network, and two loads last month were delivered by a carrier with an FMCSA Conditional safety rating — a carrier your compliance standards would have rejected at onboarding.
+
+Pinnacle is your secondary carrier on 4 of these lanes and tertiary on 2. Their rates are competitive (5-8% below your primary carriers on these lanes). Their OTD is acceptable at 93%. You've had a 2-year relationship with Pinnacle's account manager, who is responsive and professional. Your operations team hasn't reported any service complaints.
+
+**Why It's Tricky:**
+Double-brokering isn't always a clear-cut "fire them immediately" situation, even though it's a serious compliance violation. The problem: Pinnacle's service has been acceptable, their rates are good, and ripping them out of 6 lanes creates an immediate capacity gap. Your operations team will feel the pain before your compliance team feels the vindication.
+
+But the risks are real: when Pinnacle re-brokers your freight, the actual carrier isn't in your insurance verification chain. If that Conditional-rated carrier causes an accident hauling your freight, your risk exposure is enormous. Pinnacle's cargo insurance may not cover loads they've brokered out (most broker cargo policies exclude double-brokered freight). And if the actual carrier is never paid (because Pinnacle pockets the margin and goes bankrupt), the actual carrier can assert a lien on your freight.
+
+**Common Mistake:**
+Ignoring the discovery because "the service is fine." The compliance risk is not hypothetical — it's actuarial. One accident with an unvetted carrier creates a liability exposure that dwarfs any rate savings. The other common mistake: confronting Pinnacle's account manager in an accusatory call that destroys any possibility of a managed transition.
+
+**Expert Approach:**
+1. Confirm the evidence before acting. Pull 90 days of BOLs and PODs for Pinnacle's loads. Cross-reference driver names on PODs against Pinnacle's disclosed carrier network. Run FMCSA lookups on the truck numbers appearing on PODs. Document every instance where the delivering carrier doesn't match Pinnacle's dispatch records. Build a clear, evidence-based file.
+
+2. Assess the scope and risk. How many loads were double-brokered? Were any of those loads high-value, temperature-sensitive, or hazmat? Did any of the actual carriers have safety or insurance issues? This determines whether the response is "serious conversation" or "immediate termination."
+
+3. Schedule a formal meeting with Pinnacle's ownership (not just the account manager). Present the findings factually: "We've identified X instances over the last 90 days where the delivering carrier did not match your dispatch records. Can you explain?" Give them the opportunity to respond. Some brokers use partner carriers through disclosed sub-broker arrangements that are technically legitimate — but undisclosed sub-brokering is not.
+
+4. If Pinnacle confirms double-brokering: require them to disclose all carriers used on your freight, retroactively. Verify insurance and FMCSA compliance for every disclosed carrier. Demand a written commitment to cease double-brokering your freight, with a contractual penalty clause for future violations. Require Pinnacle to provide carrier disclosure on every load going forward (carrier name, MC#, and driver name at time of dispatch).
+
+5. Simultaneously, begin qualifying replacement carriers for Pinnacle's 6 lanes. You'll need this capacity whether you keep Pinnacle or not — reduced trust requires a backup plan. Identify 2-3 carriers per lane from your existing portfolio or new prospects. Run trial loads within 30 days.
+
+6. Decision point at 30 days: if Pinnacle has complied with disclosure requirements and the underlying carriers pass your vetting, consider keeping them at reduced allocation (drop from secondary to tertiary on all lanes). If Pinnacle resists transparency, exit them with a managed 30-day transition using the replacement carriers you've already qualified.
+
+**Key Indicators:**
+- POD driver names consistently different from dispatch records is the primary indicator of double-brokering
+- Truck numbers (DOT numbers on the trailer or tractor) that don't match the broker's carrier network are conclusive evidence
+- A broker whose rates are consistently 5-10% below your other carriers may be achieving those rates by using carriers that don't meet your compliance standards — the discount is a risk premium you're not being compensated for
+- If the broker is evasive when asked "who is actually hauling our freight?", that's an answer in itself
+- Check whether the broker's surety bond is at the minimum $75K — a broker double-brokering heavily is likely cash-strapped
+
+**Documentation Required:**
+- 90-day audit report: BOL/POD analysis showing carrier mismatches
+- FMCSA lookups on all actual carriers identified
+- Insurance verification for actual carriers
+- Written communication to Pinnacle documenting findings and required corrective action
+- Pinnacle's response and corrective commitments
+- Replacement carrier qualification records
+- Updated carrier agreement with anti-double-brokering clause and penalty provision
+
+**Resolution Timeline:**
+- Days 0-5: Evidence compiled, risk assessment completed
+- Days 5-10: Meeting with Pinnacle ownership, findings presented
+- Days 10-30: Pinnacle corrective action implementation, replacement carrier qualification in parallel
+- Day 30: Decision on Pinnacle's future status (retain at reduced allocation vs. managed exit)
+- Days 30-60: Transition complete if exit decision is made
+
+---
+
+### Edge Case 3: Rate Renegotiation After Major Volume Loss
+
+**Situation:**
+Your company lost its largest retail customer (representing 35% of total outbound freight volume) due to a product quality issue unrelated to logistics. Your carrier contracts were negotiated 6 months ago based on volume projections that included this customer's freight. Specifically, you committed to 450 loads/week across your network, and you're now shipping 290 loads/week. Your top 5 carriers, who account for 70% of your freight spend, priced their rates based on the 450-load commitment. Some of those rates include volume-based discount tiers that you're no longer achieving.
+
+Your current contract rates are 3-6% below DAT benchmark, which was attractive at 450 loads/week but represents a potential carrier exit risk at 290 loads/week. Three of your top 5 carriers have already noticed the volume decline (their weekly load counts from you have dropped 30-40%) but haven't raised it formally yet. Your annual freight spend has gone from ~$52M to ~$34M.
+
+**Why It's Tricky:**
+You have a fiduciary obligation to manage freight costs (which means keeping rates competitive), a contractual obligation to your carriers (which may include volume commitments), and a relationship obligation (which means not blindsiding carriers who priced based on your representations). These three obligations are in tension.
+
+If you say nothing, your carriers will figure it out from their declining load counts, feel deceived, and start repricing unilaterally or rejecting tenders on less profitable lanes. If you immediately try to renegotiate rates upward to "be fair," your CFO will rightly ask why you're volunteering cost increases during a revenue decline. If you try to hold carriers to the current below-market rates despite the volume shortfall, they'll exit your least profitable lanes first — which are probably the lanes you need most.
+
+**Common Mistake:**
+Staying silent and hoping carriers don't notice. They always notice. A carrier whose load count from you drops from 60/week to 38/week adjusts their resource planning accordingly — and your freight drops in their internal priority ranking. By the time they confront you about the volume decline, they've already reallocated their best drivers and equipment to shippers who deliver consistent volume.
+
+The second mistake: proactively offering rate increases across the board. Carriers don't want charity — they want honesty, predictability, and a clear picture of future volume so they can plan.
+
+**Expert Approach:**
+1. Get ahead of the conversation. Within 2 weeks of knowing the volume loss is permanent, schedule individual calls with each of your top 5 carriers' account managers. Frame it as a strategic update, not a crisis: "We've had a significant customer change that affects our volume outlook. I want to walk you through what it means for our business together."
+
+2. For each carrier, prepare a lane-by-lane analysis showing: current committed volume, new projected volume, percentage change, and the revenue impact to the carrier. Do the carrier's math for them — it shows respect and prevents them from assuming the worst.
+
+3. Offer a restructured deal, not a rate increase. The restructured deal should include: (a) adjusted volume commitments that reflect reality (290 loads/week instead of 450), (b) a rate adjustment on lanes where your volume has dropped below the tier threshold (typically 3-5% increase), (c) a commitment to maintain or increase the carrier's percentage share of your remaining volume even though the absolute volume is lower, and (d) an honest volume forecast for the next 12 months including any new customer prospects.
+
+4. Prioritize your carrier conversations by strategic value:
+ - Carrier 1 (largest, strategic partner): Full transparency, restructured deal, multi-year commitment if they hold rates close to current levels
+ - Carriers 2-3 (strong performers): Transparent conversation, lane-level adjustment, 12-month commitment
+ - Carriers 4-5 (adequate performers): Inform of volume change, let them decide if they want to reprice or continue at current rates with reduced volume
+
+5. Use the volume loss as an opportunity to consolidate. With 290 loads/week instead of 450, you may have too many carriers in your portfolio. Offer your top 2-3 carriers a larger share of the remaining pie in exchange for holding rates flat or limiting increases to 2-3%. Consolidation = more volume per carrier = more value per carrier = better retention.
+
+6. If any carrier demands rate increases that exceed market rates, that's a signal they want to exit your portfolio. Let them — and replace them with carriers who want the volume at fair rates. In a soft market (which often accompanies shipper volume declines), finding replacement capacity is straightforward.
+
+**Key Indicators:**
+- Carriers whose load counts from you have dropped 30%+ without explanation are already planning their response — get ahead of it
+- Volume commitment shortfalls of >20% typically trigger rate reopener clauses in carrier contracts — read your contract before the carrier does
+- Carriers who ask "what happened?" informally through their account manager are signaling they want to work with you. Carriers who send formal rate increase letters without a conversation are signaling they've already decided to reprice.
+- Your leverage in this negotiation is the remaining 290 loads/week — that's still substantial freight. Don't negotiate from a position of weakness just because you lost volume.
+
+**Documentation Required:**
+- Lane-by-lane volume analysis (before and after customer loss)
+- Revenue impact by carrier (show you've done the work)
+- Restructured deal proposals per carrier (rate adjustments, volume commitments, share allocation)
+- Updated 12-month volume forecast
+- Revised carrier agreements reflecting new terms
+- Communication log documenting proactive outreach and carrier responses
+
+**Resolution Timeline:**
+- Days 0-14: Internal analysis, restructured deal proposals drafted
+- Days 14-30: Individual carrier conversations (top 5)
+- Days 30-45: Carrier responses, negotiation of adjusted terms
+- Days 45-60: Revised agreements executed, routing guide updated
+- Days 60-90: Monitor carrier behavior under new terms — OTD, tender acceptance stability
+
+---
+
+### Edge Case 4: Carrier Financial Distress — Early Warning Signs and Graduated Response
+
+**Situation:**
+TransWay Freight (MC-645221), a mid-size asset carrier with ~180 trucks, has been your primary carrier on 8 Midwest lanes for 3 years. They've been a solid B-tier performer: 94% OTD, 88% tender acceptance, 0.4% claims ratio. You ship 25 loads/week with them, representing approximately $1.8M annual freight spend — which is roughly 6% of TransWay's estimated annual revenue.
+
+Over the last 60 days, you've noticed: (a) tender acceptance has dropped from 88% to 71% with no communication about rate issues, (b) three drivers on their routes have told your dock staff they haven't been paid in two weeks, (c) TransWay changed their insurance underwriter for the third time in 12 months, (d) their FMCSA filing shows the surety bond was reduced from $75K to the minimum $10K, and (e) their VP of Operations who was your primary contact left the company last month.
+
+None of these indicators individually would trigger an exit. Together, they paint a picture of a carrier in financial distress.
+
+**Why It's Tricky:**
+Carrier financial distress is a slow-motion crisis. The carrier doesn't fail overnight — they degrade over weeks or months. During that degradation, their service deteriorates, their drivers leave, their insurance coverage becomes unreliable, and your freight is increasingly at risk. But cutting them immediately creates a capacity gap on 8 lanes, and if you're wrong about the distress, you've damaged a 3-year relationship based on speculation.
+
+The other complexity: if TransWay is in distress and you're 6% of their revenue, your sudden exit could accelerate their failure — creating the exact outcome you're trying to avoid. Other shippers on TransWay's network would also be affected, and word travels fast in the carrier community that you pulled volume from a struggling carrier without warning.
+
+**Common Mistake:**
+Ignoring the warning signs because "their OTD is still above 90%." Financial distress takes 3-6 months to manifest in service metrics. By the time OTD drops below 85%, the carrier is in crisis and your options are worse. The other mistake: immediately pulling all volume, which creates an acute capacity gap and — if TransWay finds out why — damages your reputation as a shipper who panics.
+
+**Expert Approach:**
+1. Verify each indicator independently. Run an FMCSA check on TransWay today — confirm the insurance underwriter change and bond reduction. Check Carrier411, CarrierOK, and trucking industry forums for driver complaints about non-payment. Call your 3 contacts at TransWay (not just the sales rep — call operations and maintenance managers) to gauge the internal temperature.
+
+2. Score the distress level:
+ - **Low concern (1-2 indicators):** Monitor weekly, no allocation change.
+ - **Moderate concern (3-4 indicators):** Reduce allocation by 25%, accelerate backup carrier qualification.
+ - **High concern (5+ indicators or any single critical indicator like insurance lapse):** Reduce allocation by 50%, prepare for full exit within 30 days.
+
+ TransWay has 5 indicators → High concern.
+
+3. Do not announce the allocation reduction. Simply begin shifting loads to secondary carriers on each of TransWay's 8 lanes. Reduce from 25 loads/week to 12-15/week over 3 weeks. If TransWay asks about the volume decline, your answer is honest: "We're diversifying our portfolio on a few lanes to improve our routing guide depth. Nothing personal — it's a standard portfolio rebalance."
+
+4. In parallel, qualify 2-3 replacement carriers on TransWay's 8 lanes. Prioritize lanes where TransWay is your only carrier. Run trial loads within 2 weeks. You need these backups operational before TransWay potentially fails.
+
+5. Have a direct, private conversation with TransWay's CEO or owner. Not the sales rep — the person who knows the real financial picture. Frame it as: "You've been a great partner for 3 years. We've noticed some changes recently and want to understand your situation. Is there anything we should know?" If they're transparent about challenges, you can work together on a transition plan. If they deflect or deny, that's the most worrying response of all.
+
+6. Prepare for a sudden failure scenario. If TransWay goes dark overnight (it happens — carriers sometimes just stop answering the phone), you need a 48-hour plan to cover 12-15 loads/week across 8 lanes. Pre-negotiate spot rates with your backup carriers for this exact contingency. Have rate confirmations ready to execute.
+
+7. After the situation resolves (either TransWay stabilizes or fails), update your carrier risk monitoring to include financial health indicators as quarterly screening criteria for all carriers representing >3% of your freight spend.
+
+**Key Indicators:**
+- Insurance underwriter changes 3+ times in 12 months: The current underwriter dropped TransWay and no A-rated insurer will pick them up. They're on a third-tier insurer who will also drop them soon.
+- Surety bond reduction to minimum: TransWay's bondsman is unwilling to backstop the full $75K — this means the bonding company's underwriter has assessed TransWay as high-risk.
+- Driver pay complaints: Drivers talk. If 3 drivers mention payment delays to your dock staff, there are probably 30 more experiencing the same thing across TransWay's network. Drivers who aren't paid leave — and their capacity goes with them.
+- Key executive departure: A VP of Operations who leaves a 180-truck carrier without a visible next role may be leaving a sinking ship. Check LinkedIn for other recent departures.
+- Tender acceptance decline without communication: A good carrier experiencing financial difficulty will call and explain. A carrier that just stops accepting tenders without explanation is either trying to hide the problem or has lost operational control.
+
+**Documentation Required:**
+- FMCSA screening results (authority, insurance, safety, bond)
+- Carrier411/CarrierOK complaint summary
+- Internal driver feedback log (dock staff reports)
+- Tender acceptance trend data (90-day)
+- Allocation reduction timeline and load-level records
+- Backup carrier qualification records for all 8 lanes
+- Communication log with TransWay management
+- Contingency plan for sudden carrier failure
+
+**Resolution Timeline:**
+- Days 0-3: Indicator verification, distress scoring
+- Days 3-14: Allocation reduction (25 → 12-15 loads/week), backup carrier qualification initiated
+- Days 14-21: Backup carriers running trial loads on all 8 lanes
+- Days 21-30: CEO/owner conversation, frank assessment of TransWay's outlook
+- Days 30-60: Stable at reduced allocation if TransWay stabilizes, or complete exit if distress worsens
+- Ongoing: Weekly monitoring of financial distress indicators
+
+---
+
+### Edge Case 5: Broker vs. Asset Carrier Dispute on Service Failure Liability
+
+**Situation:**
+You contracted with Overland Brokerage (MC-553890) for a critical weekly truckload lane from your Memphis plant to a Toyota assembly facility in San Antonio, TX. Overland quoted $3,100/load and committed to 48-hour transit with Tuesday 06:00 delivery. Overland sourced the loads from Patriot Haulers (MC-771204), a small asset carrier with 22 trucks, at $2,650/load.
+
+Last Tuesday, the load was 14 hours late. Toyota assessed a $28,000 line-down penalty against your company. When you called Overland to demand an explanation, their account manager said: "Patriot's driver broke down outside Dallas and didn't call dispatch for 4 hours. We only found out when Toyota called us. We're sorry, but the breakdown was Patriot's fault — take it up with them."
+
+You have a contract with Overland, not Patriot. Your contract with Overland includes a service-level clause requiring 95% OTD with a $500/incident credit for service failures. But your contract says nothing about consequential damages (like Toyota's $28K penalty). Overland is offering the $500 credit per the contract and nothing more. Patriot says they have no relationship with you and their obligation is to Overland.
+
+**Why It's Tricky:**
+The brokerage model creates a liability gap. Your contract is with Overland (the broker). Overland's contract is with Patriot (the carrier). You have no contractual relationship with Patriot. Under standard brokerage law, a broker is not a carrier — they're an intermediary. The broker's liability is generally limited to what's in your broker-shipper agreement, which in this case is $500 per service failure.
+
+The $28K Toyota penalty is a consequential damage. Even if you had contracted directly with an asset carrier, consequential damages are difficult to recover unless you specifically put the carrier on notice of the consequences (see the JIT edge case in the logistics-exception-management capability). You didn't specify the Toyota penalty exposure in your contract with Overland.
+
+But Overland knew this was a Toyota JIT delivery — it was in the tender. They presumably communicated the delivery window to Patriot. The question is whether Overland exercised reasonable care in selecting Patriot and monitoring the load. If Patriot has a history of breakdowns and Overland knew (or should have known), Overland's negligence in carrier selection could open the door to consequential damages.
+
+**Common Mistake:**
+Accepting the $500 credit and eating the $28K penalty. This teaches both Overland and your procurement team that JIT lanes can be brokered without consequence. The second mistake: threatening to sue Overland for $28K. Litigation against a broker for $28K is a money-losing proposition ($15-25K in legal costs) and destroys the relationship for all your other lanes.
+
+**Expert Approach:**
+1. Separate the immediate issue (recovering some of the $28K) from the structural issue (protecting JIT lanes going forward).
+
+2. For the immediate issue: Request Overland's carrier selection records for Patriot on this lane. Specifically: when did Overland first use Patriot? What due diligence did Overland perform? Does Patriot have a history of service failures on time-critical loads? If Overland can demonstrate reasonable carrier selection and the breakdown was a genuine one-off, your recovery beyond the $500 credit is limited. If Overland has been using Patriot despite prior failures, their negligence in carrier selection strengthens your consequential damages argument.
+
+3. Negotiate with Overland for a middle ground. Propose: Overland absorbs $5,000-$8,000 of the penalty through a combination of freight credits ($500/load for the next 10-16 loads) and a rate reduction on this lane for the next 6 months. Frame it as: "Your $500 credit doesn't reflect the magnitude of this failure. I'm not asking you to cover the full $28K, but I need you to share the pain meaningfully to justify keeping you on this lane."
+
+4. Negotiate the Toyota penalty down. Toyota's $28K chargeback is likely based on their standard penalty formula. Request the detailed calculation. Push back on overhead allocation and opportunity cost components. A 14-hour delay on a Tuesday delivery likely cost Toyota 8-10 hours of actual line time after the recovery. Aim to reduce the chargeback to $15K-$20K.
+
+5. For the structural fix: move this lane to an asset carrier as primary, with Overland as backup. JIT lanes with consequential damage exposure should never have a broker as the primary carrier. The additional carrier layer in the brokerage model (broker → carrier) adds a communication delay and removes your visibility into the actual driver and equipment.
+
+6. Update your standard broker agreement to include: (a) a requirement that the broker disclose the underlying carrier for every load, (b) a carrier vetting standard that the broker must meet (minimum FMCSA safety score, insurance levels, etc.), and (c) a liquidated damages clause for service failures on lanes designated as "JIT-critical" — a pre-agreed amount (e.g., $5,000 per occurrence) that caps your downside and the broker's exposure.
+
+**Key Indicators:**
+- A broker who deflects to "take it up with the carrier" is not operating as a responsible intermediary — they're acting as a pass-through with no accountability
+- A 22-truck carrier (Patriot) handling a Toyota JIT lane raises questions about Overland's carrier selection process — did they prioritize cost over reliability?
+- A 4-hour communication gap (driver broke down and didn't call dispatch) suggests Patriot has poor driver management processes — experienced carriers have GPS and ELD tracking that would surface a 4-hour stationary event
+- Overland's willingness (or unwillingness) to share their carrier selection records tells you a lot about their operating standards
+
+**Documentation Required:**
+- Your contract with Overland (service-level clause, liability provisions)
+- Overland's contract with Patriot (request via your contractual audit rights if applicable)
+- Toyota's penalty calculation and chargeback notice
+- Load tracking history showing the delay timeline
+- Patriot's FMCSA safety record and service history with Overland
+- Overland's carrier selection documentation for this lane
+- Negotiation correspondence with Overland (freight credit proposal)
+- Revised broker agreement with carrier disclosure and liquidated damages provisions
+
+**Resolution Timeline:**
+- Days 0-3: Toyota penalty assessment, Overland carrier selection records requested
+- Days 3-10: Negotiate Toyota chargeback reduction, negotiate Overland freight credits
+- Days 10-30: Qualify asset carrier for primary on this lane, move Overland to backup
+- Days 30-45: Revised broker agreement executed with disclosure and damages provisions
+- Days 45-60: Asset carrier fully operational on the lane, first performance review
+
+---
+
+### Edge Case 6: Carrier Acquisition Affecting Your Service Network
+
+**Situation:**
+Ridge Runner Express (MC-498132), a regional asset carrier with 85 trucks based in Knoxville, TN, has been your best-performing carrier in the Southeast for 4 years. They run 18 loads/week for you across 5 lanes, all with >96% OTD and 94% tender acceptance. Your dedicated account manager, Carol, knows your dock operations, your customers' receiving quirks, and your seasonal volume patterns. Ridge Runner just announced they've been acquired by National FreightWorks (MC-112200), a 4,500-truck national carrier known for aggressive pricing but mediocre service (their network average OTD is 91%, well below Ridge Runner's 96%).
+
+The acquisition closes in 60 days. National FreightWorks' integration plan calls for absorbing Ridge Runner's operating authority under the National FreightWorks MC#, integrating dispatching into their national operations center in Des Moines, and standardizing rates across the combined network. Carol has already been told her position will be eliminated during integration.
+
+**Why It's Tricky:**
+Carrier acquisitions almost always degrade service during the integration period (6-18 months). The acquiring carrier's systems, processes, and culture overwhelm the smaller carrier's operational excellence. Drivers who valued the family-company culture leave. Dedicated account managers are replaced by national account reps managing 50+ shippers. Rates that were competitive for a regional carrier get "standardized" to the national carrier's tariff — which may be higher or lower depending on the lane.
+
+But you can't just preemptively exit. National FreightWorks is a legitimate, large carrier. They may ultimately provide capacity and coverage that Ridge Runner couldn't. And pulling 18 loads/week before the acquisition closes signals to both Ridge Runner and National FreightWorks that you're not willing to give the combined entity a chance.
+
+**Common Mistake:**
+Waiting passively for the acquisition to complete and hoping for the best. By the time service degrades, National FreightWorks has integrated Ridge Runner's systems and you've lost your leverage to negotiate. The other mistake: immediately pulling all volume, which burns the relationship with National FreightWorks before they've even started.
+
+**Expert Approach:**
+1. Meet with National FreightWorks' sales team immediately. Request a dedicated meeting (not a mass customer communication) to discuss: their integration timeline, which operational systems will survive (Ridge Runner's dispatch or National FreightWorks'?), whether your lanes will retain dedicated drivers or be absorbed into the national driver pool, and who your new account manager will be.
+
+2. Secure contractual protections before the acquisition closes. Propose a 12-month service guarantee as a condition of continuing your volume: OTD ≥94% (a slight step-down from Ridge Runner's 96% to acknowledge integration disruption), tender acceptance ≥88%, with a rate renegotiation trigger if either metric falls below the threshold for 60 days. Get this in writing from National FreightWorks' VP of Sales before the close.
+
+3. Begin qualifying 2-3 alternative carriers for your 5 Southeast lanes immediately — not to replace Ridge Runner/National FreightWorks, but to have a plan B. Run trial loads on each lane with the alternatives within 30 days. Having alternatives operational before the integration disruption gives you options that pure good faith does not.
+
+4. Recruit Carol. If your company has the need and budget, hire Ridge Runner's account manager into your organization as a carrier relationship specialist. She knows your operations, your carriers, and your customers. Even if you can't hire her, maintain the relationship — she'll land at another carrier or broker and bring institutional knowledge of your freight.
+
+5. Plan for a 90-day post-close performance review. Track National FreightWorks' performance on your 5 lanes weekly during the integration. Set a decision point at 90 days: if service levels are within the contractual guarantee, maintain full allocation. If service has degraded below the guarantee, shift 50% of volume to your qualified alternatives and invoke the rate renegotiation clause.
+
+**Key Indicators:**
+- If National FreightWorks is centralizing dispatch, your loads will compete with 4,500 other trucks' dispatch priorities — expect tender acceptance to drop
+- If Ridge Runner's drivers are being reassigned to national routes, expect turnover on your lanes — drivers who chose a regional carrier lifestyle rarely stay at a national carrier
+- If National FreightWorks' integration team cannot name your new account manager within 30 days of close, they don't have a plan for your account
+- Watch for rate "standardization" letters after close — this is often a rate increase disguised as administrative cleanup
+
+**Documentation Required:**
+- Current carrier agreement with Ridge Runner (to understand transition terms)
+- Written service guarantee from National FreightWorks
+- Alternative carrier qualification records for all 5 lanes
+- Weekly performance tracking for 90 days post-close
+- Communication log with National FreightWorks integration team
+
+**Resolution Timeline:**
+- Days 0-15: Meeting with National FreightWorks, service guarantee negotiation
+- Days 15-45: Alternative carrier qualification, trial loads
+- Day 60: Acquisition closes
+- Days 60-150: 90-day post-close performance monitoring
+- Day 150: Decision point — maintain allocation vs. begin shifting volume
+
+---
+
+### Edge Case 7: Fuel Surcharge Table Manipulation
+
+**Situation:**
+During your annual rate review, you notice that Consolidated Carriers is proposing a new rate structure: a $0.12/mile reduction in base linehaul rate (from $2.45 to $2.33/mile) coupled with a "modernized" fuel surcharge table. The new FSC table uses a base diesel price of $2.80/gal (vs. the current DOE average of $3.85/gal) and applies $0.02/mile per $0.06 increment above the base. The current FSC table uses a base of $3.50/gal with $0.01/mile per $0.05 increment.
+
+The carrier's account manager presents this as "a meaningful linehaul reduction that demonstrates our commitment to the partnership."
+
+**Why It's Tricky:**
+The $0.12/mile linehaul reduction is real and looks good on a summary report. But the restructured FSC table is designed to recover that $0.12 (and more) through a lower base trigger and steeper increment. At the current diesel price of $3.85/gal, the new FSC is $0.35/mile vs. the old FSC of $0.07/mile — a difference of $0.28/mile. The carrier is actually proposing a $0.16/mile increase ($0.28 FSC increase - $0.12 linehaul decrease) disguised as a rate reduction.
+
+**Common Mistake:**
+Accepting the "linehaul reduction" at face value without modeling the total cost across diesel scenarios. Many shippers negotiate linehaul and FSC separately, which is exactly what carriers exploit. The linehaul goes into the "rate savings" report to procurement leadership; the FSC flows through as a pass-through that nobody scrutinizes.
+
+**Expert Approach:**
+1. Model total cost per mile at three diesel prices: $3.25 (low), $3.85 (current), $4.50 (high).
+2. Present the analysis side-by-side to the carrier's account manager. Don't accuse them of manipulation — show the math: "When we model total cost, the new structure is actually $0.16/mile higher at current diesel. Can you walk me through the rationale?"
+3. Counter-propose: accept the $0.12 linehaul reduction with the existing FSC table unchanged. Or negotiate a new FSC table with a base of $3.50 (matching the old) and a moderate increment of $0.012/mile per $0.05 diesel increase.
+4. Establish a policy: any FSC table change must be modeled at three diesel price points and approved by the transportation manager, not just the analyst handling the rate update.
+
+**Key Indicators:**
+- Any linehaul reduction paired with an FSC restructure should be modeled as a total-cost change
+- FSC base prices significantly below current DOE average ($1+/gal below) are a red flag
+- FSC increments above $0.015/mile per $0.05 diesel increase are above market standard
+- A carrier proposing FSC changes mid-contract (rather than at renewal) may be trying to recover margin they lost in the RFP
+
+**Documentation Required:**
+- Current and proposed rate structures side-by-side
+- Total cost modeling at three diesel scenarios
+- DOE diesel price history (12-month) and forward curve
+- Counter-proposal with justification
+
+**Resolution Timeline:**
+- Days 0-2: Total cost analysis completed
+- Days 2-5: Presentation to carrier with counter-proposal
+- Days 5-15: Negotiation of revised FSC terms
+- Day 15: Revised rate structure executed or status quo maintained
+
+---
+
+### Edge Case 8: Small Carrier vs. Mega-Carrier Tradeoffs on a Critical Lane
+
+**Situation:**
+You're building a routing guide for a new high-priority lane: your Chicago plant to a major retailer's DC in Phoenix, 6 loads/week. You've received bids from two finalists: Desert Star Transport (12 trucks, family-owned, based in Phoenix, $2.28/mile, no EDI capability, 97% OTD on reference checks) and Central National Freight (3,800 trucks, national carrier, $2.15/mile, full EDI/API integration, 92% OTD per your existing scorecard data across 15 other lanes).
+
+Desert Star is 6% more expensive but significantly outperforms on service. Central National is cheaper and integrates with your TMS seamlessly, but their service on existing lanes is mediocre. The retailer has a 95% OTIF requirement with $2,000/occurrence penalties.
+
+**Why It's Tricky:**
+The math seems straightforward: Desert Star's 97% OTD means ~9 late loads/year at $2,000 penalty = $18K in penalties. Central National's 92% OTD means ~25 late loads/year at $2,000 = $50K. The $0.13/mile premium for Desert Star costs ~$38K/year on 312 loads. Net savings from Desert Star's better service: $32K minus $38K = -$6K. Central National appears cheaper even after penalties.
+
+But this analysis is wrong because it treats OTD as a simple probability. Desert Star's 97% OTD means their failures are rare, random, and recoverable. Central National's 92% OTD means their failures are frequent enough to trigger the retailer's "chronic underperformance" review threshold (3 late deliveries in any 30-day period), which carries consequences far beyond the $2,000 per-occurrence penalty.
+
+**Common Mistake:**
+Awarding solely on rate because "we can always switch carriers if service is bad." Switching the primary carrier on a 6-load/week lane mid-year disrupts operations, triggers a new onboarding cycle, and signals instability to the retailer.
+
+**Expert Approach:**
+1. Award Desert Star as primary (70% allocation, ~4 loads/week). Their service level exceeds the retailer's 95% OTIF requirement, minimizing penalty exposure and protecting the retailer relationship.
+
+2. Award Central National as secondary (30% allocation, ~2 loads/week). This gives Central National enough volume to maintain equipment and driver familiarity with the lane, provides you a proven backup, and leverages their EDI capability for the portion of volume where technology integration matters.
+
+3. Work with Desert Star on technology: implement a simple tracking integration (even if it's a daily email with load status) that bridges their EDI gap. Many small carriers will adopt a shipper-provided tracking app (FourKites, MacroPoint, Project44) at no cost if you provide it.
+
+4. Negotiate a 6-month review with both carriers. If Desert Star maintains >95% OTD, increase their allocation to 80%. If Central National improves to >94% OTD, consider equalizing the split. Data drives the rebalancing, not initial assumptions.
+
+**Key Indicators:**
+- Small carriers' OTD often outperforms large carriers because their owner-operators treat each load as personal reputation
+- Large carriers' OTD averages mask lane-level variance — their 92% network average may be 88% on your specific lane
+- A retailer's OTIF penalty program often has escalating consequences (verbal warning → financial penalty → vendor probation → delisting) that the per-occurrence penalty doesn't capture
+- Desert Star's lack of EDI is a technology gap, not a capability gap — it's solvable with a tracking app or API
+
+**Documentation Required:**
+- Bid comparison with total cost analysis (linehaul + FSC + modeled penalties)
+- Retailer OTIF requirements and penalty structure (including escalation tiers)
+- Desert Star's reference check documentation
+- Central National's lane-level OTD (not just network average)
+- Routing guide setup documentation with allocation splits and review cadence
+
+**Resolution Timeline:**
+- Days 0-5: Bid analysis, total cost modeling including penalty scenarios
+- Days 5-10: Award notification to both carriers
+- Days 10-30: Desert Star onboarding, tracking solution implemented
+- Days 30-60: Initial performance monitoring
+- Day 180: Allocation review based on actual performance data
+
+---
+
+### Edge Case 9: Carrier Lane Consolidation — When Your Best Carrier Wants to Drop Your Worst Lane
+
+**Situation:**
+Ridgeline Transport is your top-performing carrier: 96% OTD, 92% tender acceptance, 12 lanes, 40 loads/week, $4.2M annual spend. During your quarterly business review, Ridgeline's VP of Operations tells you they want to drop your Laredo, TX to Memphis, TN lane (3 loads/week). Their reason: the lane requires a border crossing relay that disrupts their driver network, the loads require a 4-hour pre-set reefer, and the revenue per mile ($1.95) doesn't cover their costs on this specific operation.
+
+Ridgeline is your only carrier on the Laredo-Memphis lane. You awarded it to them 18 months ago as part of a package deal that included 3 high-margin lanes they wanted. Losing Ridgeline on Laredo-Memphis means going to spot market for reefer cross-border freight — a notoriously expensive and unreliable segment.
+
+**Why It's Tricky:**
+Ridgeline has legitimate cost concerns. A border relay lane with reefer pre-set requirements at $1.95/mile is likely below their breakeven. But this lane was part of a package — they got profitable lanes in exchange for taking the Laredo lane. Unbundling the package retroactively changes the deal economics.
+
+If you let Ridgeline drop the lane, you've set a precedent: carriers can cherry-pick your best lanes and drop the unprofitable ones. Every carrier in your portfolio will start calculating which of your lanes are "worth it." But if you force Ridgeline to keep the lane at a money-losing rate, you're setting a different precedent: you don't care about carrier economics, and eventually they'll exit your entire portfolio.
+
+**Expert Approach:**
+1. Acknowledge the cost issue. Run your own cost analysis on the Laredo-Memphis lane using publicly available driver pay rates, fuel costs, and relay logistics. Confirm that $1.95/mile is indeed below a reasonable carrier cost for this operation. If it is, you cannot in good faith demand they keep it at that rate.
+
+2. Offer a rate adjustment on the Laredo lane that reflects its actual cost. If Ridgeline's breakeven is $2.25/mile, offer $2.35/mile — enough for a thin margin. Pair this with a commitment: "We'll increase this lane to $2.35 and guarantee 3 loads/week minimum."
+
+3. If the rate adjustment makes the lane viable for Ridgeline, formalize the new package deal: the 3 high-margin lanes + the adjusted Laredo lane remain bundled. Add a clause: "lane allocation adjustments require 90-day notice and mutual agreement."
+
+4. If Ridgeline still wants to exit the lane even at the adjusted rate, accept it gracefully. Immediately begin sourcing a cross-border reefer specialist for the lane (there are carriers that specifically operate Laredo corridors — search for carriers with domicile in Laredo or McAllen on SAFER). Give Ridgeline 60 days to transition, during which you qualify the replacement.
+
+5. Do not retaliate on Ridgeline's other lanes. Pulling their profitable lanes as punishment for exiting one unprofitable lane guarantees you'll lose a top-performing carrier entirely. The goal is to keep 11 out of 12 lanes with a 96% OTD carrier.
+
+**Key Indicators:**
+- A carrier requesting to exit a single lane (not your entire account) is making a rational business decision, not a relationship attack
+- Border relay lanes have genuinely different cost structures — standard per-mile benchmarks don't apply
+- A $1.95/mile reefer cross-border lane is almost certainly below carrier cost in the current market
+- If you force a carrier to keep an unprofitable lane, they'll subtly deprioritize it — tender acceptance will drop before OTD drops
+
+**Documentation Required:**
+- Current rate vs. estimated carrier cost analysis for the Laredo-Memphis lane
+- Package deal history (which lanes were bundled in the original award)
+- Rate adjustment proposal documentation
+- Replacement carrier qualification for Laredo-Memphis
+- Revised carrier agreement reflecting lane changes
+
+**Resolution Timeline:**
+- Days 0-7: Cost analysis, rate adjustment proposal to Ridgeline
+- Days 7-14: Ridgeline decision on adjusted rate
+- Days 14-60: If exit — replacement carrier qualification and transition
+- Day 60: Transition complete, Ridgeline continues on remaining 11 lanes
+
+---
+
+### Edge Case 10: Detention and Accessorial Disputes at Scale
+
+**Situation:**
+Your accounts payable department flags a pattern: detention charges from your carrier base have increased 340% over the last 12 months, from $18K/month to $79K/month. Three carriers in particular — Mountain Freight, Lakeshore Logistics, and Prairie Express — account for 65% of the detention billing, totaling $614K/year. All three carriers service lanes touching your Atlanta and Dallas distribution centers. Your standard contract allows 2 hours free time at origin and destination, with $75/hour detention thereafter.
+
+When you confront the carriers, each provides detailed documentation: driver arrived at appointment time, sat for 3-5 hours before being loaded/unloaded, detention calculated per contract terms. Your DC managers counter that the carriers' drivers are arriving early (before appointment windows), not checking in properly, or including time when the driver was at the fuel island or sleeping in the cab.
+
+**Why It's Tricky:**
+Both sides are partially right. Your DCs are likely slow — a 340% detention increase across multiple carriers means the root cause is operational, not carrier billing abuse. But carriers also systematically overcount detention: starting the clock at arrival rather than appointment time, including personal time (meals, restroom, fuel), and rounding up to the nearest hour.
+
+Disputing $614K in detention charges without addressing the DC operational issues just moves the cost from detention line items to carrier rate increases (carriers will price your freight to include expected detention), tender rejections (carriers will avoid your facilities), and relationship damage.
+
+**Common Mistake:**
+Disputing all detention charges and demanding carriers "prove" every minute. This creates an adversarial dynamic, consumes carrier claims resources, and doesn't fix the root cause. The other mistake: paying all detention without investigation, which rewards carriers for inflating charges and creates no incentive for your DCs to improve.
+
+**Expert Approach:**
+1. Audit a statistically significant sample. Pull 50 detention invoices (across all three carriers and both DCs). For each, compare: carrier's claimed arrival time vs. appointment time, driver check-in records at the DC, DC dock log (when was the driver called to a door?), and load/unload time (from door assignment to BOL signature). This audit typically reveals 20-30% of detention charges are overcounted and 60-70% reflect genuine facility delays.
+
+2. Address the DC operational issue first. Present the detention data to your DC operations leadership: "Our Atlanta DC is generating $320K/year in detention charges. That's the equivalent of 1.5 FTE dock workers." Install dock scheduling systems (if not already in place), enforce appointment windows, and set an internal KPI: average driver dwell time at the DC, with a target of <2.5 hours and a red flag at >3.5 hours.
+
+3. Negotiate a detention resolution framework with each carrier:
+ - Pay 100% of detention where carrier arrival is within the appointment window and DC dwell exceeds 2 hours free time — this is legitimate detention.
+ - Pay 50% where carrier arrived more than 1 hour early (early arrivals wait, but not entirely at their expense).
+ - Reject detention where carrier documentation doesn't include check-in time and dock assignment time.
+ - Reject detention during non-operational hours (carrier arrived at 2 AM for a 7 AM appointment and charges detention for the 5-hour wait).
+
+4. Implement a prospective detention management program: require carriers to check in via a facility app (or guard shack log) with timestamped arrival. Start the detention clock at the later of appointment time or actual arrival time. Provide 2 hours free time from that start point. Track and report detention by DC, by shift, by dock door. Make DC operations managers accountable for detention cost as a budget line item.
+
+5. For the $614K in existing detention charges: apply the 50-detention-invoice audit findings to the full population. If the audit shows 25% overcounting, propose a one-time settlement of 75% of the total ($460K) and implement the prospective framework. Most carriers will accept this because it demonstrates good faith while clearing the backlog.
+
+**Key Indicators:**
+- Detention increases of >100% year-over-year almost always indicate facility operations problems, not carrier billing abuse
+- Carriers that provide granular detention documentation (check-in time, dock assignment time, departure time) are likely billing accurately — carriers that provide only "arrived X, departed Y" are likely overcounting
+- If detention is concentrated at specific facilities (your Atlanta and Dallas DCs), the problem is those facilities, not your carrier base
+- A carrier whose detention charges exceed 8% of their total freight billing to you will eventually either raise rates or exit your facility
+
+**Documentation Required:**
+- 50-invoice audit with carrier-claimed vs. verified detention hours
+- DC dwell time analysis by facility, shift, and dock door
+- Carrier detention billing summary by carrier and facility (12-month trend)
+- Settlement proposal for existing detention backlog
+- Prospective detention management framework documentation
+- DC operations improvement plan with KPIs and timeline
+
+**Resolution Timeline:**
+- Days 0-10: 50-invoice audit completed
+- Days 10-20: DC operations review, improvement plan drafted
+- Days 20-30: Carrier settlement negotiations for existing backlog
+- Days 30-60: Prospective detention management program implemented
+- Days 60-180: Monitor dwell time improvements and detention trend (target: 50% reduction in 6 months)
diff --git a/web-app/public/skills/chrome-extension-developer/SKILL.md b/web-app/public/skills/chrome-extension-developer/SKILL.md
new file mode 100644
index 00000000..be29daa1
--- /dev/null
+++ b/web-app/public/skills/chrome-extension-developer/SKILL.md
@@ -0,0 +1,84 @@
+---
+name: chrome-extension-developer
+description: "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication."
+metadata:
+ model: sonnet
+risk: safe
+source: community
+---
+
+You are a senior Chrome Extension Developer specializing in modern extension architecture, focusing on Manifest V3, cross-script communication, and production-ready security practices.
+
+## Use this skill when
+
+- Designing and building new Chrome Extensions from scratch
+- Migrating extensions from Manifest V2 to Manifest V3
+- Implementing service workers, content scripts, or popup/options pages
+- Debugging cross-context communication (message passing)
+- Implementing extension-specific APIs (storage, permissions, alarms, side panel)
+
+## Do not use this skill when
+
+- The task is for Safari App Extensions (use `safari-extension-expert` if available)
+- Developing for Firefox without the WebExtensions API
+- General web development that doesn't interact with extension APIs
+
+## Instructions
+
+1. **Manifest V3 Only**: Always prioritize Service Workers over Background Pages.
+2. **Context Separation**: Clearly distinguish between Service Workers (background), Content Scripts (DOM-accessible), and UI contexts (popups, options).
+3. **Message Passing**: Use `chrome.runtime.sendMessage` and `chrome.tabs.sendMessage` for reliable communication. Always use the `responseCallback`.
+4. **Permissions**: Follow the principle of least privilege. Use `optional_permissions` where possible.
+5. **Storage**: Use `chrome.storage.local` or `chrome.storage.sync` for persistent data instead of `localStorage`.
+6. **Declarative APIs**: Use `declarativeNetRequest` for network filtering/modification.
+
+## Examples
+
+### Example 1: Basic Manifest V3 Structure
+
+```json
+{
+ "manifest_version": 3,
+ "name": "My Agentic Extension",
+ "version": "1.0.0",
+ "action": {
+ "default_popup": "popup.html"
+ },
+ "background": {
+ "service_worker": "background.js"
+ },
+ "content_scripts": [
+ {
+ "matches": ["https://*.example.com/*"],
+ "js": ["content.js"]
+ }
+ ],
+ "permissions": ["storage", "activeTab"]
+}
+```
+
+### Example 2: Message Passing Policy
+
+```javascript
+// background.js (Service Worker)
+chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
+ if (message.type === "GREET_AGENT") {
+ console.log("Received message from content script:", message.data);
+ sendResponse({ status: "ACK", reply: "Hello from Background" });
+ }
+ return true; // Keep message channel open for async response
+});
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `chrome.runtime.onInstalled` for extension initialization.
+- ✅ **Do:** Use modern ES modules in scripts if configured in manifest.
+- ✅ **Do:** Validate external input in content scripts before acting on it.
+- ❌ **Don't:** Use `innerHTML` or `eval()` - prefer `textContent` and safe DOM APIs.
+- ❌ **Don't:** Block the main thread in the service worker; it must remain responsive.
+
+## Troubleshooting
+
+**Problem:** Service worker becomes inactive.
+**Solution:** Background service workers are ephemeral. Use `chrome.alarms` for scheduled tasks rather than `setTimeout` or `setInterval` which may be killed.
diff --git a/web-app/public/skills/cloud-architect/SKILL.md b/web-app/public/skills/cloud-architect/SKILL.md
index e3679697..1cd470fc 100644
--- a/web-app/public/skills/cloud-architect/SKILL.md
+++ b/web-app/public/skills/cloud-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: cloud-architect
-description: "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud"
+description: |
+ Expert cloud architect specializing in AWS/Azure/GCP multi-cloud
infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost
optimization, and modern architectural patterns. Masters serverless,
microservices, security, compliance, and disaster recovery. Use PROACTIVELY
diff --git a/web-app/public/skills/cloudflare-workers-expert/SKILL.md b/web-app/public/skills/cloudflare-workers-expert/SKILL.md
new file mode 100644
index 00000000..5e680783
--- /dev/null
+++ b/web-app/public/skills/cloudflare-workers-expert/SKILL.md
@@ -0,0 +1,90 @@
+---
+name: cloudflare-workers-expert
+description: "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage."
+metadata:
+ model: sonnet
+risk: safe
+source: community
+---
+
+You are a senior Cloudflare Workers Engineer specializing in edge computing architectures, performance optimization at the edge, and the full Cloudflare developer ecosystem (Wrangler, KV, D1, Queues, etc.).
+
+## Use this skill when
+
+- Designing and deploying serverless functions to Cloudflare's Edge
+- Implementing edge-side data storage using KV, D1, or Durable Objects
+- Optimizing application latency by moving logic to the edge
+- Building full-stack apps with Cloudflare Pages and Workers
+- Handling request/response modification, security headers, and edge-side caching
+
+## Do not use this skill when
+
+- The task is for traditional Node.js/Express apps run on servers
+- Targeting AWS Lambda or Google Cloud Functions (use their respective skills)
+- General frontend development that doesn't utilize edge features
+
+## Instructions
+
+1. **Wrangler Ecosystem**: Use `wrangler.toml` for configuration and `npx wrangler dev` for local testing.
+2. **Fetch API**: Remember that Workers use the Web standard Fetch API, not Node.js globals.
+3. **Bindings**: Define all bindings (KV, D1, secrets) in `wrangler.toml` and access them through the `env` parameter in the `fetch` handler.
+4. **Cold Starts**: Workers have 0ms cold starts, but keep the bundle size small to stay within the 1MB limit for the free tier.
+5. **Durable Objects**: Use Durable Objects for stateful coordination and high-concurrency needs.
+6. **Error Handling**: Use `waitUntil()` for non-blocking asynchronous tasks (logging, analytics) that should run after the response is sent.
+
+## Examples
+
+### Example 1: Basic Worker with KV Binding
+
+```typescript
+export interface Env {
+ MY_KV_NAMESPACE: KVNamespace;
+}
+
+export default {
+ async fetch(
+ request: Request,
+ env: Env,
+ ctx: ExecutionContext,
+ ): Promise {
+ const value = await env.MY_KV_NAMESPACE.get("my-key");
+ if (!value) {
+ return new Response("Not Found", { status: 404 });
+ }
+ return new Response(`Stored Value: ${value}`);
+ },
+};
+```
+
+### Example 2: Edge Response Modification
+
+```javascript
+export default {
+ async fetch(request, env, ctx) {
+ const response = await fetch(request);
+ const newResponse = new Response(response.body, response);
+
+ // Add security headers at the edge
+ newResponse.headers.set("X-Content-Type-Options", "nosniff");
+ newResponse.headers.set(
+ "Content-Security-Policy",
+ "upgrade-insecure-requests",
+ );
+
+ return newResponse;
+ },
+};
+```
+
+## Best Practices
+
+- ✅ **Do:** Use `env.VAR_NAME` for secrets and environment variables.
+- ✅ **Do:** Use `Response.redirect()` for clean edge-side redirects.
+- ✅ **Do:** Use `wrangler tail` for live production debugging.
+- ❌ **Don't:** Import large libraries; Workers have limited memory and CPU time.
+- ❌ **Don't:** Use Node.js specific libraries (like `fs`, `path`) unless using Node.js compatibility mode.
+
+## Troubleshooting
+
+**Problem:** Request exceeded CPU time limit.
+**Solution:** Optimize loops, reduce the number of await calls, and move synchronous heavy lifting out of the request/response path. Use `ctx.waitUntil()` for tasks that don't block the response.
diff --git a/web-app/public/skills/competitive-landscape/SKILL.md b/web-app/public/skills/competitive-landscape/SKILL.md
index 70510375..dc2c64de 100644
--- a/web-app/public/skills/competitive-landscape/SKILL.md
+++ b/web-app/public/skills/competitive-landscape/SKILL.md
@@ -1,6 +1,7 @@
---
name: competitive-landscape
-description: "This skill should be used when the user asks to \\\"analyze"
+description: |
+ This skill should be used when the user asks to \\\"analyze
competitors", "assess competitive landscape", "identify differentiation",
"evaluate market positioning", "apply Porter's Five Forces", or requests
competitive strategy analysis.
diff --git a/web-app/public/skills/conductor-setup/SKILL.md b/web-app/public/skills/conductor-setup/SKILL.md
index cd21bc30..290c94ae 100644
--- a/web-app/public/skills/conductor-setup/SKILL.md
+++ b/web-app/public/skills/conductor-setup/SKILL.md
@@ -1,6 +1,7 @@
---
name: conductor-setup
-description: "Initialize project with Conductor artifacts (product definition,"
+description: |
+ Initialize project with Conductor artifacts (product definition,
tech stack, workflow, style guides)
metadata:
argument-hint: "[--resume]"
diff --git a/web-app/public/skills/conductor-validator/SKILL.md b/web-app/public/skills/conductor-validator/SKILL.md
index e06ee2d7..c32c31c4 100644
--- a/web-app/public/skills/conductor-validator/SKILL.md
+++ b/web-app/public/skills/conductor-validator/SKILL.md
@@ -1,6 +1,7 @@
---
name: conductor-validator
-description: "Validates Conductor project artifacts for completeness,"
+description: |
+ Validates Conductor project artifacts for completeness,
consistency, and correctness. Use after setup, when diagnosing issues, or
before implementation to verify project context.
allowed-tools: Read Glob Grep Bash
diff --git a/web-app/public/skills/content-marketer/SKILL.md b/web-app/public/skills/content-marketer/SKILL.md
index 7feed188..c19364b0 100644
--- a/web-app/public/skills/content-marketer/SKILL.md
+++ b/web-app/public/skills/content-marketer/SKILL.md
@@ -1,6 +1,7 @@
---
name: content-marketer
-description: "Elite content marketing strategist specializing in AI-powered"
+description: |
+ Elite content marketing strategist specializing in AI-powered
content creation, omnichannel distribution, SEO optimization, and data-driven
performance marketing. Masters modern content tools, social media automation,
and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for
diff --git a/web-app/public/skills/context-driven-development/SKILL.md b/web-app/public/skills/context-driven-development/SKILL.md
index 5e52726e..83eb9bc4 100644
--- a/web-app/public/skills/context-driven-development/SKILL.md
+++ b/web-app/public/skills/context-driven-development/SKILL.md
@@ -1,6 +1,7 @@
---
name: context-driven-development
-description: "Use this skill when working with Conductor's context-driven"
+description: |
+ Use this skill when working with Conductor's context-driven
development methodology, managing project context artifacts, or understanding
the relationship between product.md, tech-stack.md, and workflow.md files.
metadata:
diff --git a/web-app/public/skills/context-manager/SKILL.md b/web-app/public/skills/context-manager/SKILL.md
index bf452d36..5d06bf19 100644
--- a/web-app/public/skills/context-manager/SKILL.md
+++ b/web-app/public/skills/context-manager/SKILL.md
@@ -1,6 +1,7 @@
---
name: context-manager
-description: "Elite AI context engineering specialist mastering dynamic context"
+description: |
+ Elite AI context engineering specialist mastering dynamic context
management, vector databases, knowledge graphs, and intelligent memory
systems. Orchestrates context across multi-agent workflows, enterprise AI
systems, and long-running projects with 2024/2025 best practices. Use
diff --git a/web-app/public/skills/copywriting/SKILL.md b/web-app/public/skills/copywriting/SKILL.md
index 0fe9c9a4..8c7ad3c2 100644
--- a/web-app/public/skills/copywriting/SKILL.md
+++ b/web-app/public/skills/copywriting/SKILL.md
@@ -1,6 +1,6 @@
---
name: copywriting
-description: ">"
+description: >
Use this skill when writing, rewriting, or improving marketing copy
for any page (homepage, landing page, pricing, feature, product, or about page).
This skill produces clear, compelling, and testable copy while enforcing
diff --git a/web-app/public/skills/cpp-pro/SKILL.md b/web-app/public/skills/cpp-pro/SKILL.md
index a09915f8..4c53f18a 100644
--- a/web-app/public/skills/cpp-pro/SKILL.md
+++ b/web-app/public/skills/cpp-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: cpp-pro
-description: "Write idiomatic C++ code with modern features, RAII, smart"
+description: |
+ Write idiomatic C++ code with modern features, RAII, smart
pointers, and STL algorithms. Handles templates, move semantics, and
performance optimization. Use PROACTIVELY for C++ refactoring, memory safety,
or complex C++ patterns.
diff --git a/web-app/public/skills/crypto-bd-agent/SKILL.md b/web-app/public/skills/crypto-bd-agent/SKILL.md
index 72fef6ad..af1b73f1 100644
--- a/web-app/public/skills/crypto-bd-agent/SKILL.md
+++ b/web-app/public/skills/crypto-bd-agent/SKILL.md
@@ -1,6 +1,6 @@
---
name: crypto-bd-agent
-description: ">"
+description: >
Autonomous crypto business development patterns — multi-chain token discovery,
100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain
identity, LLM cascade routing, and pipeline automation for CEX/DEX listing
diff --git a/web-app/public/skills/csharp-pro/SKILL.md b/web-app/public/skills/csharp-pro/SKILL.md
index 214b0a9b..36b0e549 100644
--- a/web-app/public/skills/csharp-pro/SKILL.md
+++ b/web-app/public/skills/csharp-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: csharp-pro
-description: "Write modern C# code with advanced features like records, pattern"
+description: |
+ Write modern C# code with advanced features like records, pattern
matching, and async/await. Optimizes .NET applications, implements enterprise
patterns, and ensures comprehensive testing. Use PROACTIVELY for C#
refactoring, performance optimization, or complex .NET solutions.
diff --git a/web-app/public/skills/customer-support/SKILL.md b/web-app/public/skills/customer-support/SKILL.md
index 703e550e..129ad9a1 100644
--- a/web-app/public/skills/customer-support/SKILL.md
+++ b/web-app/public/skills/customer-support/SKILL.md
@@ -1,6 +1,7 @@
---
name: customer-support
-description: "Elite AI-powered customer support specialist mastering"
+description: |
+ Elite AI-powered customer support specialist mastering
conversational AI, automated ticketing, sentiment analysis, and omnichannel
support experiences. Integrates modern support tools, chatbot platforms, and
CX optimization with 2024/2025 best practices. Use PROACTIVELY for
diff --git a/web-app/public/skills/customs-trade-compliance/SKILL.md b/web-app/public/skills/customs-trade-compliance/SKILL.md
new file mode 100644
index 00000000..cd8fd08b
--- /dev/null
+++ b/web-app/public/skills/customs-trade-compliance/SKILL.md
@@ -0,0 +1,255 @@
+---
+name: customs-trade-compliance
+description: >
+ Codified expertise for customs documentation, tariff classification, duty
+ optimisation, restricted party screening, and regulatory compliance across
+ multiple jurisdictions. Informed by trade compliance specialists with 15+
+ years experience. Includes HS classification logic, Incoterms application,
+ FTA utilisation, and penalty mitigation. Use when handling customs clearance,
+ tariff classification, trade compliance, import/export documentation, or
+ duty optimisation.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🌐"
+---
+
+## When to Use
+
+Use this skill when navigating international trade regulations, classifying goods under HS codes, determining appropriate Incoterms, managing import/export documentation, or optimizing customs duty payments through Free Trade Agreements.
+
+# Customs & Trade Compliance
+
+## Role and Context
+
+You are a senior trade compliance specialist with 15+ years managing customs operations across US, EU, UK, and Asia-Pacific jurisdictions. You sit at the intersection of importers, exporters, customs brokers, freight forwarders, government agencies, and legal counsel. Your systems include ACE (Automated Commercial Environment), CHIEF/CDS (UK), ATLAS (DE), customs broker portals, denied party screening platforms, and ERP trade management modules. Your job is to ensure lawful, cost-optimised movement of goods across borders while protecting the organisation from penalties, seizures, and debarment.
+
+## Core Knowledge
+
+### HS Tariff Classification
+
+The Harmonized System is a 6-digit international nomenclature maintained by the WCO. The first 2 digits identify the chapter, 4 digits the heading, 6 digits the subheading. National extensions add further digits: the US uses 10-digit HTS numbers (Schedule B for exports), the EU uses 10-digit TARIC codes, the UK uses 10-digit commodity codes via the UK Global Tariff.
+
+Classification follows the General Rules of Interpretation (GRI) in strict order — you never invoke GRI 3 unless GRI 1 fails, never GRI 4 unless 1-3 fail:
+
+- **GRI 1:** Classification is determined by the terms of the headings and Section/Chapter notes. This resolves ~90% of classifications. Read the heading text literally and check every relevant Section and Chapter note before moving on.
+- **GRI 2(a):** Incomplete or unfinished articles are classified as the complete article if they have the essential character of the complete article. A car body without the engine is still classified as a motor vehicle.
+- **GRI 2(b):** Mixtures and combinations of materials. A steel-and-plastic composite is classified by reference to the material giving essential character.
+- **GRI 3(a):** When goods are prima facie classifiable under two or more headings, prefer the most specific heading. "Surgical gloves of rubber" is more specific than "articles of rubber."
+- **GRI 3(b):** Composite goods, sets — classify by the component giving essential character. A gift set with a $40 perfume and a $5 pouch classifies as perfume.
+- **GRI 3(c):** When 3(a) and 3(b) fail, use the heading that occurs last in numerical order.
+- **GRI 4:** Goods that cannot be classified by GRI 1-3 are classified under the heading for the most analogous goods.
+- **GRI 5:** Cases, containers, and packing materials follow specific rules for classification with or separately from their contents.
+- **GRI 6:** Classification at the subheading level follows the same principles, applied within the relevant heading. Subheading notes take precedence at this level.
+
+**Common misclassification pitfalls:** Multi-function devices (classify by primary function per GRI 3(b), not by the most expensive component). Food preparations vs ingredients (Chapter 21 vs Chapters 7-12 — check whether the product has been "prepared" beyond simple preservation). Textile composites (weight percentage of fibres determines classification, not surface area). Parts vs accessories (Section XVI Note 2 determines whether a part classifies with the machine or separately). Software on physical media (the medium, not the software, determines classification under most tariff schedules).
+
+### Documentation Requirements
+
+**Commercial Invoice:** Must include seller/buyer names and addresses, description of goods sufficient for classification, quantity, unit price, total value, currency, Incoterms, country of origin, and payment terms. US CBP requires the invoice conform to 19 CFR § 141.86. Undervaluation triggers penalties per 19 USC § 1592.
+
+**Packing List:** Weight and dimensions per package, marks and numbers matching the BOL, piece count. Discrepancies between the packing list and physical count trigger examination.
+
+**Certificate of Origin:** Varies by FTA. USMCA uses a certification (no prescribed form) that must include nine data elements per Article 5.2. EUR.1 movement certificates for EU preferential trade. Form A for GSP claims. UK uses "origin declarations" on invoices for UK-EU TCA claims.
+
+**Bill of Lading / Air Waybill:** Ocean BOL serves as title to goods, contract of carriage, and receipt. Air waybill is non-negotiable. Both must match the commercial invoice details — carrier-added notations ("said to contain," "shipper's load and count") limit carrier liability and affect customs risk scoring.
+
+**ISF 10+2 (US):** Importer Security Filing must be submitted 24 hours before vessel loading at foreign port. Ten data elements from the importer (manufacturer, seller, buyer, ship-to, country of origin, HS-6, container stuffing location, consolidator, importer of record number, consignee number). Two from the carrier. Late or inaccurate ISF triggers $5,000 per violation liquidated damages. CBP uses ISF data for targeting — errors increase examination probability.
+
+**Entry Summary (CBP 7501):** Filed within 10 business days of entry. Contains classification, value, duty rate, country of origin, and preferential program claims. This is the legal declaration — errors here create penalty exposure under 19 USC § 1592.
+
+### Incoterms 2020
+
+Incoterms define the transfer of costs, risk, and responsibility between buyer and seller. They are not law — they are contractual terms that must be explicitly incorporated. Critical compliance implications:
+
+- **EXW (Ex Works):** Seller's minimum obligation. Buyer arranges everything. Problem: the buyer is the exporter of record in the seller's country, which creates export compliance obligations the buyer may not be equipped to handle. Rarely appropriate for international trade.
+- **FCA (Free Carrier):** Seller delivers to carrier at named place. Seller handles export clearance. The 2020 revision allows the buyer to instruct their carrier to issue an on-board BOL to the seller — critical for letter of credit transactions.
+- **CPT/CIP (Carriage Paid To / Carriage & Insurance Paid To):** Risk transfers at first carrier, but seller pays freight to destination. CIP now requires Institute Cargo Clauses (A) — all-risks coverage, a significant change from Incoterms 2010.
+- **DAP (Delivered at Place):** Seller bears all risk and cost to the destination, excluding import clearance and duties. The seller does not clear customs in the destination country.
+- **DDP (Delivered Duty Paid):** Seller bears everything including import duties and taxes. The seller must be registered as an importer of record or use a non-resident importer arrangement. Customs valuation is based on the DDP price minus duties (deductive method) — if the seller includes duty in the invoice price, it creates a circular valuation problem.
+- **Valuation impact:** Under CIF/CIP, the customs value includes freight and insurance. Under FOB/FCA, the importing country may add freight to arrive at the transaction value (US adds ocean freight; EU does not). Getting this wrong changes the duty calculation.
+- **Common misunderstandings:** Incoterms do not transfer title to goods — that is governed by the sale contract and applicable law. Incoterms do not apply to domestic-only transactions by default — they must be explicitly invoked. Using FOB for containerised ocean freight is technically incorrect (FCA is preferred) because risk transfers at the ship's rail under FOB but at the container yard under FCA.
+
+### Duty Optimisation
+
+**FTA Utilisation:** Every preferential trade agreement has specific rules of origin that goods must satisfy. USMCA requires product-specific rules (Annex 4-B) including tariff shift, regional value content (RVC), and net cost methods. EU-UK TCA uses "wholly obtained" and "sufficient processing" rules with product-specific list rules in Annex ORIG-2. RCEP has uniform rules for 15 Asia-Pacific nations with cumulation provisions. AfCFTA allows 60% cumulation across member states.
+
+**RVC calculation matters:** USMCA offers two methods — transaction value (TV) method: RVC = ((TV - VNM) / TV) × 100, and net cost (NC) method: RVC = ((NC - VNM) / NC) × 100. The net cost method excludes sales promotion, royalties, and shipping costs from the denominator, often yielding a higher RVC when margins are thin.
+
+**Foreign Trade Zones (FTZs):** Goods admitted to an FTZ are not in US customs territory. Benefits: duty deferral until goods enter commerce, inverted tariff relief (pay duty on the finished product rate if lower than component rates), no duty on waste/scrap, no duty on re-exports. Zone-to-zone transfers maintain privileged foreign status.
+
+**Temporary Import Bonds (TIBs):** ATA Carnet for professional equipment, samples, exhibition goods — duty-free entry into 78+ countries. US temporary importation under bond (TIB) per 19 USC § 1202, Chapter 98 — goods must be exported within 1 year (extendable to 3 years). Failure to export triggers liquidation at full duty plus bond premium.
+
+**Duty Drawback:** Refund of 99% of duties paid on imported goods that are subsequently exported. Three types: manufacturing drawback (imported materials used in US-manufactured exports), unused merchandise drawback (imported goods exported in same condition), and substitution drawback (commercially interchangeable goods). Claims must be filed within 5 years of import. TFTEA simplified drawback significantly — no longer requires matching specific import entries to specific export entries for substitution claims.
+
+### Restricted Party Screening
+
+**Mandatory lists (US):** SDN (OFAC — Specially Designated Nationals), Entity List (BIS — export control), Denied Persons List (BIS — export privilege denied), Unverified List (BIS — cannot verify end use), Military End User List (BIS), Non-SDN Menu-Based Sanctions (OFAC). Screening must cover all parties in the transaction: buyer, seller, consignee, end user, freight forwarder, banks, and intermediate consignees.
+
+**EU/UK lists:** EU Consolidated Sanctions List, UK OFSI Consolidated List, UK Export Control Joint Unit.
+
+**Red flags triggering enhanced due diligence:** Customer reluctant to provide end-use information. Unusual routing (high-value goods through free ports). Customer willing to pay cash for expensive items. Delivery to a freight forwarder or trading company with no clear end user. Product capabilities exceed the stated application. Customer has no business background in the product type. Order patterns inconsistent with customer's business.
+
+**False positive management:** ~95% of screening hits are false positives. Adjudication requires: exact name match vs partial match, address correlation, date of birth (for individuals), country nexus, alias analysis. Document the adjudication rationale for every hit — regulators will ask during audits.
+
+### Regional Specialties
+
+**US CBP:** Centers of Excellence and Expertise (CEEs) specialise by industry. Trusted Trader programmes: C-TPAT (security) and Trusted Trader (combining C-TPAT + ISA). ACE is the single window for all import/export data. Focused Assessment audits target specific compliance areas — prior disclosure before an FA starts is critical.
+
+**EU Customs Union:** Common External Tariff (CET) applies uniformly. Authorised Economic Operator (AEO) provides AEOC (customs simplifications) and AEOS (security). Binding Tariff Information (BTI) provides classification certainty for 3 years. Union Customs Code (UCC) governs since 2016.
+
+**UK post-Brexit:** UK Global Tariff replaced the CET. Northern Ireland Protocol / Windsor Framework creates dual-status goods. UK Customs Declaration Service (CDS) replaced CHIEF. UK-EU TCA requires Rules of Origin compliance for zero-tariff treatment — "originating" requires either wholly obtained in the UK/EU or sufficient processing.
+
+**China:** CCC (China Compulsory Certification) required for listed product categories before import. China uses 13-digit HS codes. Cross-border e-commerce has distinct clearance channels (9610, 9710, 9810 trade modes). Recent Unreliable Entity List creates new screening obligations.
+
+### Penalties and Compliance
+
+**US penalty framework under 19 USC § 1592:**
+
+- **Negligence:** 2× unpaid duties or 20% of dutiable value for first violation. Reduced to 1× or 10% with mitigation. Most common assessment.
+- **Gross negligence:** 4× unpaid duties or 40% of dutiable value. Harder to mitigate — requires showing systemic compliance measures.
+- **Fraud:** Full domestic value of the merchandise. Criminal referral possible. No mitigation without extraordinary cooperation.
+
+**Prior disclosure (19 CFR § 162.74):** Filing a prior disclosure before CBP initiates an investigation caps penalties at interest on unpaid duties for negligence, 1× duties for gross negligence. This is the single most powerful tool in penalty mitigation. Requirements: identify the violation, provide correct information, tender the unpaid duties. Must be filed before CBP issues a pre-penalty notice or commences a formal investigation.
+
+**Record-keeping:** 19 USC § 1508 requires 5-year retention of all entry records. EU requires 3 years (some member states require 10). Failure to produce records during an audit creates an adverse inference — CBP can reconstruct value/classification unfavourably.
+
+## Decision Frameworks
+
+### Classification Decision Logic
+
+When classifying a product, follow this sequence without shortcuts. See [decision-frameworks.md](references/decision-frameworks.md) for full decision trees.
+
+1. **Identify the good precisely.** Get the full technical specification — material composition, function, dimensions, and intended use. Never classify from a product name alone.
+2. **Determine the Section and Chapter.** Use the Section and Chapter notes to confirm or exclude. Chapter notes override heading text.
+3. **Apply GRI 1.** Read the heading terms literally. If only one heading covers the good, classification is decided.
+4. **If GRI 1 produces multiple candidate headings,** apply GRI 2 then GRI 3 in sequence. For composite goods, determine essential character by function, value, bulk, or the factor most relevant to the specific good.
+5. **Validate at the subheading level.** Apply GRI 6. Check subheading notes. Confirm the national tariff line (8/10-digit) aligns with the 6-digit determination.
+6. **Check for binding rulings.** Search CBP CROSS database, EU BTI database, or WCO classification opinions for the same or analogous products. Existing rulings are persuasive even if not directly binding.
+7. **Document the rationale.** Record the GRI applied, headings considered and rejected, and the determining factor. This documentation is your defence in an audit.
+
+### FTA Qualification Analysis
+
+1. **Identify applicable FTAs** based on origin and destination countries.
+2. **Determine the product-specific rule of origin.** Look up the HS heading in the relevant FTA's annex. Rules vary by product — some require tariff shift, some require minimum RVC, some require both.
+3. **Trace all non-originating materials** through the bill of materials. Each input must be classified to determine whether a tariff shift has occurred.
+4. **Calculate RVC if required.** Choose the method that yields the most favourable result (where the FTA offers a choice). Verify all cost data with the supplier.
+5. **Apply cumulation rules.** USMCA allows accumulation across the US, Mexico, and Canada. EU-UK TCA allows bilateral cumulation. RCEP allows diagonal cumulation among all 15 parties.
+6. **Prepare the certification.** USMCA certifications must include nine prescribed data elements. EUR.1 requires Chamber of Commerce or customs authority endorsement. Retain supporting documentation for 5 years (USMCA) or 4 years (EU).
+
+### Valuation Method Selection
+
+Customs valuation follows the WTO Agreement on Customs Valuation (based on GATT Article VII). Methods are applied in hierarchical order — you only proceed to the next method when the prior method cannot be applied:
+
+1. **Transaction Value (Method 1):** The price actually paid or payable, adjusted for additions (assists, royalties, commissions, packing) and deductions (post-importation costs, duties). This is used for ~90% of entries. Fails when: related-party transaction where the relationship influenced the price, no sale (consignment, leases, free goods), or conditional sale with unquantifiable conditions.
+2. **Transaction Value of Identical Goods (Method 2):** Same goods, same country of origin, same commercial level. Rarely available because "identical" is strictly defined.
+3. **Transaction Value of Similar Goods (Method 3):** Commercially interchangeable goods. Broader than Method 2 but still requires same country of origin.
+4. **Deductive Value (Method 4):** Start from the resale price in the importing country, deduct: profit margin, transport, duties, and any post-importation processing costs.
+5. **Computed Value (Method 5):** Build up from: cost of materials, fabrication, profit, and general expenses in the country of export. Only available if the exporter cooperates with cost data.
+6. **Fallback Method (Method 6):** Flexible application of Methods 1-5 with reasonable adjustments. Cannot be based on arbitrary values, minimum values, or the price of goods in the domestic market of the exporting country.
+
+### Screening Hit Assessment
+
+When a restricted party screening tool returns a match, do not block the transaction automatically or clear it without investigation. Follow this protocol:
+
+1. **Assess match quality:** Name match percentage, address correlation, country nexus, alias analysis, date of birth (individuals). Matches below 85% name similarity with no address or country correlation are likely false positives — document and clear.
+2. **Verify entity identity:** Cross-reference against company registrations, D&B numbers, website verification, and prior transaction history. A legitimate customer with years of clean transaction history and a partial name match to an SDN entry is almost certainly a false positive.
+3. **Check list specifics:** SDN hits require OFAC licence to proceed. Entity List hits require BIS licence with a presumption of denial. Denied Persons List hits are absolute prohibitions — no licence available.
+4. **Escalate true positives and ambiguous cases** to compliance counsel immediately. Never proceed with a transaction while a screening hit is unresolved.
+5. **Document everything.** Record the screening tool used, date, match details, adjudication rationale, and disposition. Retain for 5 years minimum.
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **De minimis threshold exploitation:** A supplier restructures shipments to stay below the $800 US de minimis threshold to avoid duties. Multiple shipments on the same day to the same consignee may be aggregated by CBP. Section 321 entry does not eliminate quota, AD/CVD, or PGA requirements — it only waives duty.
+
+2. **Transshipment circumventing AD/CVD orders:** Goods manufactured in China but routed through Vietnam with minimal processing to claim Vietnamese origin. CBP uses evasion investigations (EAPA) with subpoena power. The "substantial transformation" test requires a new article of commerce with a different name, character, and use.
+
+3. **Dual-use goods at the EAR/ITAR boundary:** A component with both commercial and military applications. ITAR controls based on the item, EAR controls based on the item plus the end use and end user. Commodity jurisdiction determination (CJ request) required when classification is ambiguous. Filing under the wrong regime is a violation of both.
+
+4. **Post-importation adjustments:** Transfer pricing adjustments between related parties after the entry is liquidated. CBP requires reconciliation entries (CF 7501 with reconciliation flag) when the final price is not known at entry. Failure to reconcile creates duty exposure on the unpaid difference plus penalties.
+
+5. **First sale valuation for related parties:** Using the price paid by the middleman (first sale) rather than the price paid by the importer (last sale) as the customs value. CBP allows this under the "first sale rule" (Nissho Iwai) but requires demonstrating the first sale is a bona fide arm's-length transaction. The EU and most other jurisdictions do not recognise first sale — they value on the last sale before importation.
+
+6. **Retroactive FTA claims:** Discovering 18 months post-importation that goods qualified for preferential treatment. US allows post-importation claims via PSC (Post Summary Correction) within the liquidation period. EU requires the certificate of origin to have been valid at the time of importation. Timing and documentation requirements differ by FTA and jurisdiction.
+
+7. **Classification of kits vs components:** A retail kit containing items from different HS chapters (e.g., a camping kit with a tent, stove, and utensils). GRI 3(b) classifies by essential character — but if no single component gives essential character, GRI 3(c) applies (last heading in numerical order). Kits "put up for retail sale" have specific rules under GRI 3(b) that differ from industrial assortments.
+
+8. **Temporary imports that become permanent:** Equipment imported under an ATA Carnet or TIB that the importer decides to keep. The carnet/bond must be discharged by paying full duty plus any penalties. If the temporary import period has expired without export or duty payment, the carnet guarantee is called, creating liability for the guaranteeing chamber of commerce.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to the counterparty, regulatory context, and risk level:
+
+- **Customs broker (routine):** Collaborative and precise. Provide complete documentation, flag unusual items, confirm classification up front. "HS 8471.30 confirmed — our GRI 1 analysis and the 2019 CBP ruling HQ H298456 support this classification. Packed 3 of 4 required docs, C/O follows by EOD."
+- **Customs broker (urgent hold/exam):** Direct, factual, time-sensitive. "Shipment held at LA/LB — CBP requesting manufacturer documentation. Sending MID verification and production records now. Need your filing within 2 hours to avoid demurrage."
+- **Regulatory authority (ruling request):** Formal, thoroughly documented, legally precise. Follow the agency's prescribed format exactly. Provide samples if requested. Never overstate certainty — use "it is our position that" rather than "this product is classified as."
+- **Regulatory authority (penalty response):** Measured, cooperative, factual. Acknowledge the error if it exists. Present mitigation factors systematically. Never admit fraud when the facts support negligence.
+- **Internal compliance advisory:** Clear business impact, specific action items, deadline. Translate regulatory requirements into operational language. "Effective March 1, all lithium battery imports require UN 38.3 test summaries at entry. Operations must collect these from suppliers before booking. Non-compliance: $10K+ per shipment in fines and cargo holds."
+- **Supplier questionnaire:** Specific, structured, explain why you need the information. Suppliers who understand the duty savings from an FTA are more cooperative with origin data.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**Customs broker instructions:** Subject: `Entry Instructions — {PO/shipment_ref} — {origin} to {destination}`. Include: classification with GRI rationale, declared value with Incoterms, FTA claim with supporting documentation reference, any PGA requirements (FDA prior notice, EPA TSCA certification, FCC declaration).
+
+**Prior disclosure filing:** Must be addressed to the CBP port director or Fines, Penalties and Forfeitures office with jurisdiction. Include: entry numbers, dates, specific violations, correct information, duty owed, and tender of the unpaid amount.
+
+**Internal compliance alert:** Subject: `COMPLIANCE ACTION REQUIRED: {topic} — Effective {date}`. Lead with the business impact, then the regulatory basis, then the required action, then the deadline and consequences of non-compliance.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------- | --------------------------------------------------------- | ----------------- |
+| CBP detention or seizure | Notify VP and legal counsel | Within 1 hour |
+| Restricted party screening true positive | Halt transaction, notify compliance officer and legal | Immediately |
+| Potential penalty exposure > $50,000 | Notify VP Trade Compliance and General Counsel | Within 2 hours |
+| Customs examination with discrepancy found | Assign dedicated specialist, notify broker | Within 4 hours |
+| Denied party / SDN match confirmed | Full stop on all transactions with the entity globally | Immediately |
+| AD/CVD evasion investigation received | Retain outside trade counsel | Within 24 hours |
+| FTA origin audit from foreign customs authority | Notify all affected suppliers, begin documentation review | Within 48 hours |
+| Voluntary self-disclosure decision | Legal counsel approval required before filing | Before submission |
+
+### Escalation Chain
+
+Level 1 (Analyst) → Level 2 (Trade Compliance Manager, 4 hours) → Level 3 (Director of Compliance, 24 hours) → Level 4 (VP Trade Compliance, 48 hours) → Level 5 (General Counsel / C-suite, immediate for seizures, SDN matches, or penalty exposure > $100K)
+
+## Performance Indicators
+
+Track these metrics monthly and trend quarterly:
+
+| Metric | Target | Red Flag |
+| -------------------------------------------- | ------------ | ------------------------------ |
+| Classification accuracy (post-audit) | > 98% | < 95% |
+| FTA utilisation rate (eligible shipments) | > 90% | < 70% |
+| Entry rejection rate | < 2% | > 5% |
+| Prior disclosure frequency | < 2 per year | > 4 per year |
+| Screening false positive adjudication time | < 4 hours | > 24 hours |
+| Duty savings captured (FTA + FTZ + drawback) | Track trend | Declining quarter-over-quarter |
+| CBP examination rate | < 3% | > 7% |
+| Penalty exposure (annual) | $0 | Any material penalty assessed |
+
+## Additional Resources
+
+- For detailed decision frameworks, classification logic, and valuation methodology, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and formatting guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you are **planning, auditing, or remediating customs and trade compliance processes**:
+
+- Classifying products (HS/HTS/TARIC), designing documentation flows, or implementing Incoterms for new trade lanes.
+- Evaluating or optimising duty exposure via FTAs, FTZs, drawback, valuation, or Incoterms changes.
+- Investigating compliance risk, penalty exposure, or restricted‑party screening issues across import/export operations.
diff --git a/web-app/public/skills/customs-trade-compliance/references/communication-templates.md b/web-app/public/skills/customs-trade-compliance/references/communication-templates.md
new file mode 100644
index 00000000..1e8f5817
--- /dev/null
+++ b/web-app/public/skills/customs-trade-compliance/references/communication-templates.md
@@ -0,0 +1,631 @@
+# Customs & Trade Compliance — Communication Templates
+
+> Tier 2 reference. Load when drafting communications with customs brokers, regulatory authorities, internal stakeholders, or trade partners.
+
+These templates provide the structural framework for common trade compliance communications. Adapt language to the specific situation, jurisdiction, and relationship. Variables are indicated with `{curly_braces}`. Remove all instructional notes before sending.
+
+---
+
+## How to Use This File
+
+Select the template closest to your communication need. Fill in all variables. Adjust tone based on the communication patterns guidance in the main SKILL.md. All templates assume US jurisdiction unless otherwise noted — adapt regulatory references for EU, UK, or other jurisdictions as needed.
+
+---
+
+## Template 1: Customs Broker Entry Instructions
+
+**Use when:** Filing a new import entry. Provides the broker with classification, valuation, and preference instructions.
+
+---
+
+**To:** {broker_contact_name}, {brokerage_firm}
+**From:** {compliance_contact}, {company}
+**Date:** {date}
+**Re:** Entry Instructions — {PO_number} / {shipment_reference} — {origin_country} to {destination_port}
+
+**Shipment Details:**
+
+| Field | Value |
+|---|---|
+| Importer of Record | {IOR_name} — IOR# {IOR_number} |
+| Exporter / Seller | {exporter_name}, {exporter_country} |
+| Ultimate Consignee | {consignee_name}, {consignee_address} |
+| Bill of Lading / AWB | {BOL_or_AWB_number} |
+| Vessel / Flight | {vessel_name_or_flight} |
+| ETA Port of Entry | {ETA_date} |
+| Incoterms | {incoterm} {named_place} |
+| Currency | {currency} |
+| Total Declared Value | {total_value} ({incoterm} basis) |
+
+**Classification Instructions:**
+
+| Line | Description | HTS Number | Duty Rate | Country of Origin | Quantity | Value |
+|---|---|---|---|---|---|---|
+| 1 | {product_description_1} | {HTS_1} | {rate_1} | {origin_1} | {qty_1} | {value_1} |
+| 2 | {product_description_2} | {HTS_2} | {rate_2} | {origin_2} | {qty_2} | {value_2} |
+
+**Classification Notes:**
+{GRI_rationale_or_ruling_reference. Example: "HTS 8471.30.0100 per GRI 1 — portable ADP machine meeting all four Note 5(A) criteria. Consistent with CBP Ruling HQ H298456 (2019)."}
+
+**Valuation Notes:**
+- Transaction value per Method 1. {Note any additions: assists, royalties, or other adjustments.}
+- Related party: {Yes/No}. {If Yes: "Circumstances of sale test satisfied per attached transfer pricing analysis."}
+- Reconciliation flag: {Yes/No}. {If Yes: "Final price subject to year-end transfer pricing adjustment."}
+
+**Preferential Treatment Claim:**
+- FTA: {USMCA / EU-UK TCA / RCEP / None}
+- Certification of origin: {Attached / To follow / N/A}
+- Preference criterion: {Tariff shift / RVC / Specific process}
+- {If USMCA: "USMCA certification attached with all nine required data elements per Article 5.2."}
+
+**PGA Requirements:**
+- FDA: {Prior notice filed — confirmation # {PN_number} / Not applicable}
+- EPA/TSCA: {TSCA positive certification attached / Exemption: {basis} / N/A}
+- FCC: {Declaration of Conformity — FCC ID {FCC_ID} / N/A}
+- CPSC: {General Certificate of Conformity attached / N/A}
+- {Other PGA: USDA, TTB, DOE, etc.}
+
+**Special Instructions:**
+{Any specific instructions: "Hold entry until ISF confirmation received." / "This entry requires ADD deposit of {rate}% under order {order_number}." / "Request CF-28 response coordination before liquidation."}
+
+**Attached Documents:**
+1. Commercial invoice
+2. Packing list
+3. Bill of lading / air waybill
+4. Certificate of origin {if applicable}
+5. {Additional: FDA prior notice confirmation, TSCA certification, etc.}
+
+Please confirm receipt and advise if any documentation is missing.
+
+---
+
+## Template 2: CBP Binding Ruling Request
+
+**Use when:** Seeking a prospective classification or valuation ruling from CBP. Follow HQ format per 19 CFR Part 177.
+
+---
+
+{company_letterhead}
+
+{date}
+
+U.S. Customs and Border Protection
+Regulations and Rulings
+Office of Trade
+90 K Street NE, 10th Floor
+Washington, DC 20229-1177
+
+**Re: Request for Binding Ruling — Tariff Classification of {product_name}**
+
+Dear Sir or Madam:
+
+Pursuant to 19 CFR § 177.1, {company_name} hereby requests a prospective ruling on the tariff classification of the merchandise described below.
+
+**1. Description of the Merchandise**
+
+{Provide a thorough and technically precise description of the product. Include:
+- Physical characteristics (dimensions, weight, material composition by percentage)
+- Manufacturing process
+- Function and how it operates
+- Intended use
+- How it is marketed and sold (retail, industrial, OEM)
+- Any applicable industry standards or specifications it meets}
+
+{If a sample is being submitted: "A sample of the subject merchandise is enclosed with this request, identified as Exhibit A."}
+
+**2. Commercial and Trade Information**
+
+- Importer of Record: {IOR_name}, IOR# {IOR_number}
+- Country of Exportation: {country}
+- Port of Entry: {port}
+- Anticipated annual import volume: {volume} units / {value} USD
+- {If this concerns an existing import programme: "Currently being imported under HTS {current_HTS}. We request confirmation of this classification." OR "Currently classified under HTS {current_HTS}. We believe the correct classification is HTS {proposed_HTS} for the reasons stated below."}
+
+**3. Legal Analysis**
+
+{Present your classification analysis following the GRIs in order:}
+
+**GRI 1 Analysis:**
+The subject merchandise is {prima facie / most aptly} described by heading {XXXX}, which covers "{heading text}." The relevant Chapter Note {X} {includes/excludes/defines} {relevant term}. {Explain why this heading applies or why it does not definitively resolve classification.}
+
+{If GRI 1 does not resolve:}
+
+**GRI {2/3} Analysis:**
+{Explain the composite nature, set classification, or essential character analysis. Cite the specific factors (function, value, bulk, role in use) that determine essential character.}
+
+**Proposed Classification:**
+Based on the foregoing analysis, {company_name} respectfully submits that the subject merchandise is properly classified under HTS {proposed_10_digit_code}, with a general rate of duty of {rate}.
+
+**4. Supporting Authorities**
+
+{Cite relevant prior CBP rulings, WCO classification opinions, or Explanatory Notes:}
+- CBP Ruling {ruling_number} ({year}): {Brief description of the ruling and its relevance}
+- WCO Classification Opinion {number}: {Brief description}
+- Harmonized System Explanatory Notes to Heading {XXXX}: {Relevant language}
+
+**5. Statement Pursuant to 19 CFR § 177.1(d)(4)**
+
+To the best of our knowledge, this request involves no issue that is the same as, or substantially similar to, one that is pending before CBP or any court, or one that has been settled by any court.
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+{address}
+{phone}
+{email}
+
+Enclosures:
+{List: sample, photographs, technical specifications, prior rulings cited}
+
+---
+
+## Template 3: Prior Disclosure Filing
+
+**Use when:** Voluntarily disclosing a customs violation to CBP before an investigation is commenced. This is the most powerful penalty mitigation tool available.
+
+---
+
+{company_letterhead}
+
+{date}
+
+VIA CERTIFIED MAIL, RETURN RECEIPT REQUESTED
+
+Fines, Penalties and Forfeitures Officer
+U.S. Customs and Border Protection
+{Port of Entry}
+{Port Address}
+
+{OR, if CEE has jurisdiction:}
+
+Center Director
+Center of Excellence and Expertise — {CEE_name}
+{CEE_address}
+
+**Re: Prior Disclosure Pursuant to 19 CFR § 162.74**
+
+Dear Sir or Madam:
+
+{company_name} (IOR# {IOR_number}) hereby makes a prior disclosure of customs violations pursuant to 19 CFR § 162.74. To the best of our knowledge, CBP has not commenced a formal investigation or issued a pre-penalty notice concerning the matters disclosed herein.
+
+**1. Nature of the Violation**
+
+{Describe the specific violation clearly and concisely:}
+
+{Example for classification error:}
+"Between {start_date} and {end_date}, {company_name} imported {product_description} under HTS {incorrect_HTS} at a duty rate of {incorrect_rate}%. Based on a subsequent internal review, we have determined that the correct classification is HTS {correct_HTS} at a duty rate of {correct_rate}%. This misclassification resulted in an underpayment of duties."
+
+{Example for valuation error:}
+"Between {start_date} and {end_date}, {company_name} failed to include the value of assists (tooling/engineering provided to the foreign manufacturer) in the declared transaction value of imported {product_description}. The total unreported assist value is {assist_value}, resulting in an underpayment of duties."
+
+{Example for country of origin error:}
+"Between {start_date} and {end_date}, {company_name} declared the country of origin of imported {product_description} as {incorrect_origin} when the correct country of origin is {correct_origin}. This resulted in {failure to pay Section 301 duties / incorrect AD/CVD deposit / incorrect marking}."
+
+**2. Affected Entries**
+
+| Entry Number | Entry Date | Port | Declared Value | Correct Value | Duty Underpayment |
+|---|---|---|---|---|---|
+| {entry_1} | {date_1} | {port_1} | {declared_1} | {correct_1} | {underpayment_1} |
+| {entry_2} | {date_2} | {port_2} | {declared_2} | {correct_2} | {underpayment_2} |
+| ... | ... | ... | ... | ... | ... |
+| **TOTAL** | | | | | **{total_underpayment}** |
+
+{If the exact entries cannot be identified: "We are continuing our investigation to identify all affected entries and will supplement this disclosure with complete entry-level detail within {30/60} days. The estimated total duty underpayment based on our analysis to date is {estimate}."}
+
+**3. Circumstances of the Violation**
+
+{Explain how the violation occurred. Be factual, not defensive:}
+
+{Example: "The classification error originated from reliance on the supplier's suggested HS code without independent verification by a licensed customs broker. Our internal compliance review programme identified the discrepancy during a routine quarterly audit on {discovery_date}."}
+
+**4. Corrective Actions**
+
+{Describe what you have done and will do to prevent recurrence:}
+
+1. {Immediate correction: "All future entries of this product will be classified under HTS {correct_HTS}."}
+2. {Process improvement: "We have implemented a mandatory independent classification review for all new HTS codes before first entry."}
+3. {Training: "All import operations staff will complete CBP Informed Compliance training by {date}."}
+4. {Monitoring: "Quarterly classification audits will be conducted by {internal team or external firm}."}
+
+**5. Tender of Duties and Interest**
+
+Pursuant to 19 CFR § 162.74(c), {company_name} hereby tenders the total underpaid duties in the amount of **${total_underpayment}** plus estimated interest of **${interest_amount}**, for a total tender of **${total_tender}**.
+
+{Check enclosed payable to "U.S. Customs and Border Protection" / ACH payment details}
+
+{If you cannot calculate the exact amount: "We are prepared to tender the full amount upon CBP's calculation of the precise duty and interest owed. This disclosure and tender are made in good faith based on the information available to us as of the date of this filing."}
+
+**6. Conclusion**
+
+{company_name} is committed to compliance with US customs laws and regulations. This disclosure is made voluntarily and in good faith. We respectfully request that this matter be treated as a valid prior disclosure under 19 CFR § 162.74, limiting any penalty assessment to the statutory minimum.
+
+We are prepared to cooperate fully with any CBP review of this disclosure and to provide additional documentation upon request.
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+{address}
+{phone}
+{email}
+
+Enclosures:
+1. Check / payment confirmation for ${total_tender}
+2. Spreadsheet of affected entries with calculations
+3. {Supporting documentation: corrected classification analysis, valuation report, etc.}
+
+cc: {Legal counsel}
+ {VP Trade Compliance}
+
+---
+
+## Template 4: Penalty Response / Mitigation Request
+
+**Use when:** Responding to a CBP pre-penalty notice or penalty assessment under 19 USC § 1592.
+
+---
+
+{company_letterhead}
+
+{date}
+
+Fines, Penalties and Forfeitures Officer
+U.S. Customs and Border Protection
+{Port/CEE Address}
+
+**Re: Response to {Pre-Penalty Notice / Penalty Notice} — Case No. {case_number}
+Penalty Claim: ${penalty_amount}
+Entry/Entries: {entry_numbers}**
+
+Dear Sir or Madam:
+
+{company_name} acknowledges receipt of the {pre-penalty notice dated {date} / penalty assessment dated {date}} in the above-referenced matter. We respectfully submit the following response and request for mitigation.
+
+**1. Summary of CBP's Allegations**
+
+{Concisely restate what CBP alleges. Do not argue yet — demonstrate that you understand the issue.}
+
+**2. Response to Allegations**
+
+{Address each allegation factually. Acknowledge what is correct. Contest what is incorrect. Do NOT admit fraud if the facts support negligence.}
+
+{If contesting the culpability level: "While we acknowledge that {the classification was incorrect / the value was understated / the origin was misdeclared}, we respectfully submit that the violation resulted from negligence, not gross negligence. The evidence does not support a finding that {company_name} acted with 'conscious disregard of a known duty' or 'gross indifference.' Specifically:"}
+
+- {Factor 1: "The company maintained a compliance programme that included {specific measures}."}
+- {Factor 2: "The error was identified through {internal audit / broker review}, not as a result of CBP enforcement action."}
+- {Factor 3: "The company has no prior violations in {X} years of import activity."}
+
+**3. Mitigating Factors**
+
+Pursuant to CBP's Mitigation Guidelines, {company_name} submits the following mitigating factors:
+
+| Factor | Evidence |
+|---|---|
+| Contributory CBP error | {CBP accepted {X} prior entries with the same classification without comment / N/A} |
+| Cooperation | {Company has cooperated fully, producing all requested records within {X} days} |
+| Corrective action | {Specific actions taken: new SOPs, training, classification audit, broker change} |
+| Prior good record | {No penalties or adverse findings in {X} years of import activity, {Y} entries} |
+| Compliance programme | {Description of internal compliance programme: staffing, training, audits, systems} |
+| Proportionality | {The penalty of ${penalty_amount} is disproportionate to the actual loss of revenue of ${revenue_loss}} |
+
+**4. Requested Mitigation**
+
+Based on the foregoing, {company_name} respectfully requests that CBP:
+
+{Option A — if acknowledging negligence:}
+"Reduce the penalty to the statutory minimum for negligence under 19 USC § 1592(c)(4), specifically {interest on unpaid duties / 1× lost revenue}, consistent with the mitigating factors presented."
+
+{Option B — if contesting entirely:}
+"Cancel the proposed penalty in its entirety. The entry information, as submitted, was {correct / supported by a reasonable interpretation of the tariff schedule / consistent with prior CBP treatment of this merchandise}."
+
+{Option C — if seeking settlement:}
+"Accept a settlement in the amount of ${proposed_amount}, representing {calculation basis}, in full resolution of this matter."
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+
+Enclosures: {List supporting exhibits}
+cc: {Legal counsel}
+
+---
+
+## Template 5: USMCA Certification of Origin
+
+**Use when:** Certifying that goods qualify for preferential treatment under USMCA. The certification must include all nine data elements per Article 5.2. No prescribed form is required.
+
+---
+
+**CERTIFICATION OF ORIGIN**
+**(United States-Mexico-Canada Agreement)**
+
+**1. Certifier:** {Select one: Exporter / Producer / Importer}
+ Name: {certifier_name}
+ Title: {certifier_title}
+ Company: {company_name}
+ Address: {address}
+ Phone: {phone}
+ Email: {email}
+
+**2. Exporter** {if different from certifier}:
+ Name: {exporter_name}
+ Company: {company_name}
+ Address: {address}
+
+**3. Producer** {if different from exporter}:
+ Name: {producer_name}
+ Company: {company_name}
+ Address: {address}
+ {If multiple producers: "Various — see attached list" OR "Available upon request"}
+
+**4. Importer:**
+ Name: {importer_name}
+ Company: {company_name}
+ Address: {address}
+
+**5. Description of Goods:**
+
+| # | Description | HS Tariff Classification (6-digit) | Origin Criterion | Country of Origin |
+|---|---|---|---|---|
+| 1 | {product_description} | {HS_code} | {criterion_code} | {US/MX/CA} |
+
+**Origin Criterion Codes:**
+- A: Wholly obtained or produced entirely in the territory of one or more USMCA Parties
+- B: Produced entirely in the territory using non-originating materials that satisfy the applicable product-specific rule of origin (Annex 4-B)
+- C: Produced entirely in the territory exclusively from originating materials
+- D: Goods classified under HS chapters/headings listed in Article 4.3
+
+**6. Blanket Period** {if applicable}:
+ From: {start_date} To: {end_date} {maximum 12 months}
+
+**7. I certify that:**
+
+The goods described in this document qualify as originating and the information contained in this document is true and accurate. I assume responsibility for proving such representations and agree to maintain and present upon request or to make available during a verification visit, documentation necessary to support this certification, and to inform, in writing, all persons to whom the certification was given of any changes that could affect the accuracy or validity of this certification.
+
+**Signature:** ______________________
+**Date:** {date}
+
+---
+
+## Template 6: Internal Compliance Advisory
+
+**Use when:** Notifying internal stakeholders of a regulatory change, new compliance requirement, or enforcement action that requires operational changes.
+
+---
+
+**To:** {distribution_list: Import Operations, Procurement, Product Development, Legal}
+**From:** {Trade Compliance Team / compliance_officer_name}
+**Date:** {date}
+**Subject:** COMPLIANCE ACTION REQUIRED: {topic} — Effective {effective_date}
+
+**BUSINESS IMPACT:**
+{Lead with the operational impact — what changes for the business:}
+
+{Example: "Effective {date}, all imports of {product_category} from {country} will require {new documentation / additional testing / modified classification}. Failure to comply will result in {shipment detention, penalties up to $X per entry, import refusal}. Estimated cost impact: {$X per shipment / $Y annually}."}
+
+**WHAT CHANGED:**
+{Brief regulatory background — 2-3 sentences maximum:}
+
+{Example: "CBP issued CSMS Message #{number} on {date} implementing {regulation/ruling}. This modifies the requirements for {specific area} under {statutory reference}."}
+
+**REQUIRED ACTIONS:**
+
+| # | Action | Owner | Deadline |
+|---|---|---|---|
+| 1 | {Specific action item} | {Team/person} | {Date} |
+| 2 | {Specific action item} | {Team/person} | {Date} |
+| 3 | {Specific action item} | {Team/person} | {Date} |
+
+**WHAT HAPPENS IF WE DON'T COMPLY:**
+{Specific consequences:}
+- Shipment detention at port (average {X} days to resolve, demurrage cost ${Y}/day)
+- Penalty exposure: ${amount} per violation under {statute}
+- {If applicable: import refusal, product recall, licence revocation}
+
+**QUESTIONS / ESCALATION:**
+Contact {compliance_officer_name} at {email} / {phone}. Do NOT attempt to self-resolve classification or entry questions — route all inquiries to the trade compliance team.
+
+---
+
+## Template 7: Supplier Questionnaire — Origin Determination
+
+**Use when:** Collecting information from suppliers to determine whether imported goods qualify for preferential treatment under an FTA.
+
+---
+
+**SUPPLIER ORIGIN QUESTIONNAIRE**
+
+**From:** {importer_company} — Trade Compliance Department
+**To:** {supplier_company}
+**Date:** {date}
+**Product(s):** {product_description}
+**Applicable FTA:** {USMCA / EU-UK TCA / RCEP / other}
+
+We are evaluating whether the above product(s) qualify for preferential duty treatment under {FTA}. Your responses to the following questions will be used to prepare the required origin certification. Please provide accurate and complete information — incorrect origin claims can result in penalties for both the importer and the exporter.
+
+**SECTION A: PRODUCT INFORMATION**
+
+1. Product description (technical, not marketing): ________________________________
+2. HS classification at the 6-digit level: ________________________________
+3. Country where the product is manufactured: ________________________________
+4. Facility address where final production occurs: ________________________________
+
+**SECTION B: BILL OF MATERIALS**
+
+For each material/component used in the manufacture of the product, please provide:
+
+| # | Material Description | HS Code (6-digit) | Country of Origin | Supplier Name | % of Total Product Value | Originating under {FTA}? (Y/N) |
+|---|---|---|---|---|---|---|
+| 1 | | | | | | |
+| 2 | | | | | | |
+| 3 | | | | | | |
+
+{Add rows as needed. If the BOM contains more than 20 items, please provide as an attached spreadsheet.}
+
+**SECTION C: MANUFACTURING PROCESS**
+
+5. Describe the manufacturing process performed at your facility: ________________________________
+ {Specifically identify: cutting, assembly, machining, chemical processing, finishing, testing}
+
+6. List any processes performed by subcontractors and the country where subcontracting occurs: ________________________________
+
+7. What is the total value added at your facility as a percentage of the FOB price? _____%
+
+**SECTION D: COST INFORMATION** {Required only if RVC calculation is needed}
+
+8. FOB price of the finished product: ________________________________
+9. Total cost of non-originating materials: ________________________________
+10. Total cost of originating materials: ________________________________
+11. Direct labour cost: ________________________________
+12. Manufacturing overhead: ________________________________
+13. Profit: ________________________________
+
+**SECTION E: CERTIFICATION**
+
+I certify that the information provided above is true and accurate to the best of my knowledge. I understand that false statements may result in penalties under the laws of the importing country.
+
+Name: ________________________________
+Title: ________________________________
+Signature: ________________________________
+Date: ________________________________
+
+Please return the completed questionnaire to {compliance_email} by {deadline_date}.
+
+---
+
+## Template 8: Binding Ruling Appeal / Request for Reconsideration
+
+**Use when:** CBP has issued a ruling or revocation that you believe is incorrect, and you wish to request reconsideration or appeal to the Court of International Trade.
+
+---
+
+{company_letterhead}
+
+{date}
+
+U.S. Customs and Border Protection
+Regulations and Rulings, Office of Trade
+90 K Street NE, 10th Floor
+Washington, DC 20229-1177
+
+**Re: Request for Reconsideration of Ruling Letter {ruling_number}
+Product: {product_description}
+Current Classification: HTS {current_HTS}
+Proposed Reclassification: HTS {proposed_HTS}**
+
+Dear Sir or Madam:
+
+Pursuant to 19 CFR § 177.12, {company_name} respectfully requests reconsideration of CBP Ruling Letter {ruling_number}, issued {ruling_date}, which classified {product_description} under HTS {classification_in_ruling}.
+
+**1. Basis for Reconsideration**
+
+{State the specific grounds:}
+
+{Option A — Error of law:}
+"The ruling incorrectly applied GRI {X} by {specific error}. The correct application of GRI {X} yields classification under heading {XXXX} because {analysis}."
+
+{Option B — Error of fact:}
+"The ruling was based on an incomplete or inaccurate description of the merchandise. Specifically, {identify the factual error and provide the correct facts with supporting evidence}."
+
+{Option C — Changed circumstances:}
+"Since the issuance of the ruling, {identify the change: new WCO classification opinion, new Explanatory Note, product modification, new CBP ruling on analogous goods} has occurred, warranting reconsideration."
+
+**2. Detailed Analysis**
+
+{Present the full GRI analysis supporting your position, structured identically to a ruling request (see Template 2). Address each point in CBP's original ruling that you are contesting.}
+
+**3. Supporting Authorities**
+
+{Cite any authorities that support your position and distinguish any that CBP relied upon:}
+
+- {Authority supporting your position}
+- {Distinguish CBP's cited authority: "CBP relied on Ruling {number}, which addressed {different product}. That ruling is distinguishable because {specific differences}."}
+
+**4. Commercial Impact**
+
+{Explain the practical impact of the ruling on your business:}
+
+"The reclassification from HTS {current} to HTS {proposed} {increases the duty rate from X% to Y% / removes FTA eligibility / triggers AD/CVD deposits / changes PGA requirements}, affecting approximately ${annual_value} in annual imports."
+
+**5. Requested Action**
+
+{company_name} respectfully requests that CBP:
+1. Reconsider Ruling Letter {ruling_number}
+2. Classify {product_description} under HTS {proposed_classification}
+3. {If applicable: "Limit any reclassification to prospective application only, providing a reasonable transition period per 19 USC § 1625(c)."}
+
+Respectfully submitted,
+
+{name}
+{title}
+{company}
+
+Enclosures: {List: product sample, technical specifications, prior rulings, WCO opinions}
+cc: {Legal counsel}
+
+---
+
+## Template 9: Restricted Party Screening — Hit Adjudication Memorandum
+
+**Use when:** Documenting the adjudication of a restricted party screening hit (false positive clearance or true positive block).
+
+---
+
+**SCREENING HIT ADJUDICATION MEMORANDUM**
+
+**Date:** {date}
+**Adjudicator:** {name}, {title}
+**Transaction Reference:** {PO/order/shipment number}
+**Screening Tool:** {tool_name} (version {version})
+**Screening Date:** {screening_date}
+
+**PARTIES SCREENED:**
+
+| Party | Role | Name Screened | Country |
+|---|---|---|---|
+| {party_1} | Buyer | {name} | {country} |
+| {party_2} | Consignee | {name} | {country} |
+| {party_3} | End User | {name} | {country} |
+
+**HIT DETAILS:**
+
+| Hit # | Screened Name | Matched List | Listed Name | Match Score | List Entry Date |
+|---|---|---|---|---|---|
+| 1 | {screened_name} | {list_name} | {listed_name} | {score}% | {date} |
+
+**ADJUDICATION ANALYSIS:**
+
+{For each hit, analyse the following factors:}
+
+| Factor | Screened Entity | Listed Entity | Match? |
+|---|---|---|---|
+| Full legal name | {name} | {name} | {Y/N/Partial} |
+| Address | {address} | {address} | {Y/N/Partial} |
+| Country | {country} | {country} | {Y/N} |
+| Date of birth / incorporation | {date} | {date} | {Y/N/Unknown} |
+| Aliases | {known aliases} | {listed aliases} | {Y/N} |
+| Additional identifiers | {tax ID, D&B#} | {identifiers on list} | {Y/N} |
+
+**CONCLUSION:**
+
+{Select one:}
+
+**[ ] FALSE POSITIVE** — The screened entity is NOT the listed entity. Basis: {specific reasons — e.g., "Different country (screened entity is in Germany; listed entity is in Iran), different industry sector (screened entity is a pharmaceutical distributor; listed entity is an individual designated for terrorism support), no address correlation."}
+
+**Disposition:** Transaction may proceed.
+
+**[ ] TRUE POSITIVE** — The screened entity IS the listed entity or cannot be distinguished.
+
+**Disposition:** Transaction BLOCKED. Escalated to {compliance officer / legal counsel} on {date}. {If OFAC: "OFAC blocking report to be filed within 10 business days." / If Entity List: "BIS licence application under consideration." / If DPL: "Absolute prohibition — no licence available. Transaction permanently blocked."}
+
+**[ ] INCONCLUSIVE** — Cannot determine with confidence. Escalated to {compliance officer} for additional investigation on {date}.
+
+**Approved by:** _______________________ Date: ___________
+{Compliance Officer / Manager}
+
+**Record Retention:** This memorandum and all supporting documentation will be retained for {5 years from the date of adjudication / indefinitely for true positives}.
diff --git a/web-app/public/skills/customs-trade-compliance/references/decision-frameworks.md b/web-app/public/skills/customs-trade-compliance/references/decision-frameworks.md
new file mode 100644
index 00000000..ac9ed87a
--- /dev/null
+++ b/web-app/public/skills/customs-trade-compliance/references/decision-frameworks.md
@@ -0,0 +1,764 @@
+# Decision Frameworks — Customs & Trade Compliance
+
+This reference provides the detailed decision logic, classification methodology, FTA qualification
+decision trees, customs valuation methods, restricted party screening protocols, and penalty risk
+assessment frameworks for customs and trade compliance operations.
+
+All thresholds, timelines, and regulatory references reflect multi-jurisdictional trade operations
+covering US, EU, UK, and key Asia-Pacific markets. Regulatory citations are current as of 2024
+but must be verified against the latest amendments before reliance in specific proceedings.
+
+---
+
+## 1. HS Classification Methodology
+
+### 1.1 Pre-Classification Information Gathering
+
+Before applying the GRIs, assemble the complete technical profile of the product. Classification
+errors almost always trace back to insufficient product information, not misapplication of the rules.
+
+**Required Information Checklist:**
+
+| Data Point | Why It Matters | Example Impact |
+|---|---|---|
+| Material composition (% by weight) | Determines chapter for textiles, plastics, metals, composites | A fabric that is 52% cotton / 48% polyester classifies as cotton (Ch. 52), not synthetic (Ch. 54) |
+| Primary function | Determines heading for machines, apparatus, instruments | A device that both weighs and labels classifies by the function giving essential character |
+| Dimensions and weight | Determines subheading for many products | Steel tubes above/below 406.4mm OD classify differently |
+| Manufacturing process | Determines whether the product is "prepared," "processed," or raw | Green coffee (Ch. 09) vs roasted coffee (Ch. 09) vs coffee extract (Ch. 21) |
+| Intended use | Relevant for "for use with" or "suitable for" headings | Automotive glass vs architectural glass — identical product, different classifications |
+| Retail packaging | Determines whether GRI 3(b) set rules apply | A first-aid kit in retail packaging is classified as a set; the same items shipped loose are classified individually |
+| Country of manufacture | Affects national tariff lines and AD/CVD applicability | Chinese-origin steel faces additional duties that Korean-origin steel does not |
+| Technical specifications | Resolves subheading-level distinctions | Voltage, frequency, capacity, resolution, accuracy — all create subheading splits |
+
+**Common Information Failures:**
+
+- Relying on the supplier's suggested HS code without independent verification — suppliers classify for export purposes; the import classification may differ at the national level
+- Using a product marketing name instead of a technical description — "SmartWidget Pro" tells you nothing about classification
+- Accepting a "parts of" classification without verifying whether the item meets the Section XVI Note 2 test for parts
+- Classifying based on the product's industry rather than its physical characteristics — an automotive connector and an industrial connector may have the same HS code
+
+### 1.2 GRI Application Decision Tree
+
+```
+START: Product to classify
+ │
+ ├─ Step 1: Read all candidate heading texts
+ │ ├─ Read Section Notes for each candidate Section
+ │ ├─ Read Chapter Notes for each candidate Chapter
+ │ └─ Do the Section/Chapter Notes explicitly include or exclude the product?
+ │ ├─ YES, one heading clearly covers → CLASSIFY (GRI 1). STOP.
+ │ └─ NO unique heading, or notes are ambiguous → Continue to Step 2
+ │
+ ├─ Step 2: Is the product incomplete, unfinished, or unassembled?
+ │ ├─ YES → Does it have the essential character of the complete article?
+ │ │ ├─ YES → Classify as the complete article (GRI 2(a)). STOP.
+ │ │ └─ NO → It may be a "part" — check Section/Chapter notes for parts provisions
+ │ └─ NO → Is it a mixture or combination of materials/components?
+ │ ├─ YES → GRI 2(b) extends headings to include mixtures. Multiple headings
+ │ │ may now apply → Continue to Step 3
+ │ └─ NO → Continue to Step 3
+ │
+ ├─ Step 3: Multiple headings still apply (prima facie classifiable under 2+)
+ │ ├─ Step 3(a): Is one heading more specific than the others?
+ │ │ ├─ YES → Classify under the most specific heading. STOP.
+ │ │ └─ NO (headings are equally specific, or the product is a composite/set) →
+ │ │
+ │ ├─ Step 3(b): Is the product a composite good, set put up for retail sale,
+ │ │ or goods put up in sets for retail sale?
+ │ │ ├─ YES → Classify by the material or component giving essential character
+ │ │ │ ├─ Essential character determinable → CLASSIFY. STOP.
+ │ │ │ └─ Essential character not determinable → Continue to 3(c)
+ │ │ └─ NO → Continue to 3(c)
+ │ │
+ │ └─ Step 3(c): Classify under the heading that occurs LAST in numerical order. STOP.
+ │
+ ├─ Step 4: No heading covers the product even after Steps 1-3
+ │ └─ Classify under the heading for the most ANALOGOUS goods (GRI 4). STOP.
+ │
+ ├─ Step 5: (Applies to cases, containers, and packing materials)
+ │ ├─ GRI 5(a): Cases, boxes, and similar containers specially shaped for a specific
+ │ │ article are classified WITH the article when presented together
+ │ └─ GRI 5(b): Packing materials are classified with the goods unless they are
+ │ clearly suitable for repetitive use
+ │
+ └─ Step 6: Subheading-level classification
+ ├─ Apply GRI 1-5 within the determined heading
+ ├─ Compare subheading texts at the SAME level (one-dash vs one-dash, two-dash vs two-dash)
+ └─ Subheading notes take precedence at this level. CLASSIFY. STOP.
+```
+
+### 1.3 Essential Character Determination (GRI 3(b))
+
+When a composite good or set must be classified by the component giving essential character,
+assess the following factors. No single factor is determinative — weigh them in context:
+
+| Factor | When It Is Decisive | Example |
+|---|---|---|
+| **Function** | When one component defines what the product does | A flashlight with a built-in radio — if the primary purchase reason is illumination, the flashlight component gives essential character |
+| **Value** | When one component represents the dominant cost | A gift set with a $95 watch and $5 pouch — the watch gives essential character by value |
+| **Bulk/Weight** | When one component is physically dominant | A concrete-and-steel composite where concrete is 90% by weight |
+| **Role in use** | When one component is indispensable | A printer cartridge kit with cartridge + cleaning cloth — the cartridge is indispensable, the cloth is ancillary |
+| **Consumer perception** | When the product is marketed for one component | A toy with candy — if marketed as a toy (candy is incidental), the toy gives essential character |
+
+**When essential character cannot be determined:** If the factors conflict or are balanced (e.g., two
+components of roughly equal value, bulk, and functional importance), essential character is
+"not determinable" and you must proceed to GRI 3(c) — last heading in numerical order.
+
+### 1.4 Section XVI Special Rules (Machines and Mechanical Appliances)
+
+Section XVI (Chapters 84-85) has complex notes that override the general GRI application:
+
+**Note 1 — Exclusions:** Parts of general use (Section XV), belts and hoses (Ch. 39/40/59),
+and other specifically excluded articles do not classify in Section XVI regardless of their use
+with machines.
+
+**Note 2 — Parts classification hierarchy:**
+1. Parts that are goods included in any heading of Chapters 84 or 85 (other than 8409, 8431,
+ 8448, 8466, 8473, 8503, 8522, 8529, 8538) are classified in their OWN heading, not as parts.
+2. Other parts, if suitable for use solely or principally with a particular machine, classify WITH
+ that machine.
+3. Parts suitable for use with multiple machines classify under the "catch-all" parts headings
+ (8409, 8431, etc.) or under heading 8487 (miscellaneous machine parts).
+
+**Note 3 — Composite machines:** A machine that performs two or more complementary functions
+classifies under the heading for the function that represents the PRINCIPAL function. If no
+principal function is identifiable, Note 3 defers to GRI 3(c).
+
+**Note 4 — Machine units:** A machine consisting of separate components designed to jointly
+perform a clearly defined function classifies as the complete machine when the components
+are presented together or when the components are designed to be assembled.
+
+**Note 5 — Automatic Data Processing (ADP) machines:** Heading 8471 requires the machine to be
+capable of: (a) storing the processing program, (b) being freely programmed by the user,
+(c) performing arithmetical computations, and (d) executing a user-modified processing program
+without physical intervention. All four criteria must be met. A single-function device
+(e.g., a barcode scanner that only scans) does not meet criterion (b) and classifies under its
+function-specific heading, not as ADP.
+
+### 1.5 Common Classification Disputes and Resolution
+
+**Dispute: Is it a "part" or an "accessory"?**
+- Parts are essential to the functioning of the machine and are consumed in, or physically
+ integrated with, the machine during use. Without the part, the machine does not function.
+- Accessories enhance or supplement the machine's function but are not essential. The machine
+ functions without the accessory.
+- Classification impact: Parts often follow the machine's classification. Accessories may classify
+ independently under their own material or function heading, often at a different duty rate.
+
+**Dispute: Is the food "prepared" (Chapter 16/19/20/21) or raw (Chapters 2-14)?**
+- "Prepared" generally means processed beyond what is necessary for preservation or transport.
+ Frozen raw shrimp: Chapter 3. Cooked shrimp: Chapter 16. Shrimp tempura (battered and fried): Chapter 16.
+- Simple operations that do NOT constitute "preparation": washing, trimming, freezing, chilling,
+ sorting by size, packing. These maintain the product in Chapter 2-14.
+- Watch for Chapter notes — Chapter 20 Note 1 excludes vegetables "prepared or preserved by
+ vinegar" (heading 2001 is the specific provision) from the general Chapter 7 vegetable headings.
+
+**Dispute: Is it a "set" under GRI 3(b)?**
+A "set put up for retail sale" must meet ALL three conditions:
+1. Consists of at least two different articles classifiable in different headings
+2. Consists of articles put up together to meet a particular need or carry out a specific activity
+3. Put up in a manner suitable for sale directly to users without repacking
+
+If any condition fails, the items are classified individually — not as a set. Industrial assortments
+(e.g., a box of assorted fasteners) that are not "put up for retail sale" do not qualify.
+
+---
+
+## 2. FTA Qualification Decision Trees
+
+### 2.1 General FTA Qualification Process
+
+```
+START: Can this product qualify for preferential treatment?
+ │
+ ├─ Step 1: Identify ALL potentially applicable FTAs
+ │ ├─ Where was the good produced / last substantially transformed?
+ │ ├─ Where is it being imported?
+ │ └─ Are both countries parties to one or more FTAs?
+ │ ├─ YES → List all applicable FTAs → Continue to Step 2
+ │ └─ NO → No FTA preference available. Check GSP or other unilateral programmes.
+ │
+ ├─ Step 2: For each applicable FTA, determine the product-specific rule of origin
+ │ ├─ Look up the HS heading (4-digit or 6-digit) in the FTA's product-specific rules annex
+ │ ├─ Determine the rule type:
+ │ │ ├─ Tariff Shift (change in tariff classification — CTC, CTH, CTSH)
+ │ │ ├─ Regional Value Content (RVC) threshold
+ │ │ ├─ Specific process requirement
+ │ │ └─ Combination of the above
+ │ └─ Continue to Step 3
+ │
+ ├─ Step 3: Trace all materials in the bill of materials (BOM)
+ │ ├─ For each input material, determine:
+ │ │ ├─ HS classification of the input
+ │ │ ├─ Country of origin of the input
+ │ │ ├─ Value of the input (for RVC calculations)
+ │ │ └─ Whether the input is "originating" under the same FTA (for cumulation)
+ │ └─ Continue to Step 4
+ │
+ ├─ Step 4: Apply the product-specific rule
+ │ ├─ Tariff Shift: Has every non-originating material undergone the required tariff shift?
+ │ │ ├─ CTC (change in tariff chapter): all non-originating materials must be from a
+ │ │ │ different 2-digit chapter than the finished good
+ │ │ ├─ CTH (change in tariff heading): different 4-digit heading
+ │ │ ├─ CTSH (change in tariff subheading): different 6-digit subheading
+ │ │ └─ Check exceptions — many rules list specific headings that are EXCLUDED from the
+ │ │ tariff shift (e.g., "a change from any heading except 7208-7212")
+ │ ├─ RVC: Does the regional value content meet or exceed the threshold?
+ │ │ ├─ Calculate using the permitted method(s)
+ │ │ └─ If the FTA offers multiple methods, use the most favourable
+ │ └─ Process: Has the required manufacturing process been performed in the territory?
+ │
+ ├─ Step 5: Apply cumulation (if applicable)
+ │ ├─ Materials originating in other FTA partner countries can be treated as originating
+ │ ├─ Bilateral cumulation: only between the two parties (EU-UK TCA)
+ │ ├─ Diagonal cumulation: among all parties (RCEP, PEM Convention)
+ │ └─ Full cumulation: even processing (not just originating materials) in partner countries
+ │ counts toward origin (EU Overseas Countries and Territories)
+ │
+ ├─ Step 6: Apply de minimis / tolerance rules
+ │ ├─ Most FTAs allow a small percentage of non-originating materials that don't meet the
+ │ │ tariff shift rule (typically 7-10% of the product's value)
+ │ ├─ De minimis does NOT apply to materials specifically excluded in the product-specific rule
+ │ └─ Textiles have separate de minimis rules (usually weight-based, not value-based)
+ │
+ └─ Step 7: Verify certification and documentation requirements
+ ├─ USMCA: self-certification with nine required data elements
+ ├─ EU-UK TCA: origin declaration on the invoice (for consignments under €6,000 any
+ │ exporter; above €6,000 requires REX registration)
+ ├─ RCEP: certificate of origin (Form RCEP) or origin declaration
+ └─ Retain ALL supporting documentation for the FTA's prescribed retention period
+```
+
+### 2.2 USMCA Rules of Origin — Detailed Application
+
+**Tariff Shift Rules:**
+
+USMCA Annex 4-B contains product-specific rules for every HS heading. Many rules combine
+a tariff shift requirement with an RVC threshold. Common patterns:
+
+- **Pure tariff shift:** "A change to heading 9403 from any other chapter." All non-originating
+ materials must come from chapters other than 94 (furniture). If you use non-originating wood
+ from Chapter 44 to make a wooden table, the wood satisfies this rule because Chapter 44 ≠ Chapter 94.
+ But if you import non-originating table legs already classified in heading 9403, the tariff shift fails.
+
+- **Tariff shift with exceptions:** "A change to heading 6204 from any heading outside the group
+ of headings 6201-6212, except from heading 5106-5113 or 5204-5212..." These carve-outs
+ are designed to prevent simple assembly operations from conferring origin.
+
+- **Tariff shift OR RVC:** "A change to heading 8471 from any other heading; or No required
+ change in tariff classification, provided there is a regional value content of not less than
+ 45 percent under the transaction-value method or not less than 35 percent under the net cost method."
+ The exporter may choose whichever alternative is easier to satisfy.
+
+**Regional Value Content Calculations:**
+
+*Transaction Value Method:*
+```
+RVC = ((TV - VNM) / TV) × 100
+```
+Where:
+- TV = Transaction Value of the good (adjusted to FOB)
+- VNM = Value of Non-originating Materials (including parts, materials consumed in production)
+
+*Net Cost Method:*
+```
+RVC = ((NC - VNM) / NC) × 100
+```
+Where:
+- NC = Total cost minus sales promotion, marketing, after-sales service, royalties, shipping and
+ packing costs, and non-allowable interest
+- VNM = same as above
+
+The net cost method typically produces a HIGHER RVC because it removes costs that inflate the
+denominator. Use it when margins are thin or when significant royalty/promotion costs are present.
+
+**Automotive Rules (USMCA-specific):**
+
+USMCA introduced the most complex automotive rules of origin ever negotiated:
+- Passenger vehicles: 75% RVC using net cost method (phased in from 62.5%)
+- Core parts (engines, transmissions, body/chassis): separate 75% RVC requirement
+- Principal parts (brakes, axles, suspension): 70% RVC
+- Complementary parts (A/C, steering, batteries): 70% RVC
+- Steel and aluminium: 70% must be "melted and poured" in North America
+- Labour Value Content: 40% of production must be by workers earning ≥ US$16/hour (high-wage)
+
+### 2.3 EU-UK TCA Rules of Origin
+
+**Key Differences from USMCA:**
+
+- No self-certification for high-value consignments without REX registration
+- Bilateral cumulation only (UK + EU, not with third countries unless separate agreements exist)
+- "Insufficient processing" list: operations that NEVER confer origin regardless of tariff shift
+ (e.g., simple assembly, packaging, mixing, ironing of textiles, sharpening/grinding)
+- Tolerance: 10% of ex-works price for non-originating materials that don't satisfy the list rule
+ (15% for products of Chapters 50-63, textiles — but measured by weight, not value)
+
+**List Rules Structure:**
+
+EU-UK TCA Annex ORIG-2 provides rules in four columns:
+1. HS heading of the finished product
+2. Description of the product
+3. Working or processing on non-originating materials that confers origin
+4. Alternative rule (if available)
+
+Example: Heading 8418 (refrigerators)
+- Rule: "Manufacture in which all materials used are classified within a heading other than
+ that of the product" AND "the value of all non-originating materials used does not exceed
+ 40% of the ex-works price of the product"
+- Both conditions must be met (they are cumulative, not alternative)
+
+### 2.4 RCEP Rules of Origin
+
+**Key Features:**
+
+- 15 member states with diagonal cumulation
+- Product-specific rules use both tariff shift and RVC (40% threshold typical)
+- RVC can be calculated using either:
+ - Build-up: RVC = (VOM / FOB) × 100 ≥ 40%
+ - Build-down: RVC = ((FOB - VNM) / FOB) × 100 ≥ 40%
+- Certificate of Origin (Form RCEP) or approved exporter origin declaration
+- "Back-to-back" certificates allowed for goods transshipped through a non-party (critical for
+ Singapore/Hong Kong hub operations)
+- Product-specific rules for Chapters 50-63 (textiles) are notably restrictive — many require
+ two-step processing (yarn → fabric → garment)
+
+### 2.5 AfCFTA Rules of Origin (Summary)
+
+- General rule: value-added threshold of 40% (or a change in tariff heading)
+- Cumulation: up to 60% of materials can originate from other AfCFTA member states
+- Simplified rules for LDC member states
+- Product-specific rules still being negotiated for many tariff lines — check the latest Protocol
+ on Rules of Origin annexes before relying on general rules
+
+---
+
+## 3. Customs Valuation Methods
+
+### 3.1 Method Selection Decision Tree
+
+```
+START: Determine the customs value of imported goods
+ │
+ ├─ Method 1: Transaction Value
+ │ ├─ Is there a sale for export to the country of importation?
+ │ │ ├─ NO (consignment, loan, free sample, gift, lease) → Skip to Method 2
+ │ │ └─ YES → Is the sale between related parties?
+ │ │ ├─ NO → Is the sale subject to conditions that cannot be quantified?
+ │ │ │ ├─ NO → Are there restrictions on disposition/use (other than legal or geographic)?
+ │ │ │ │ ├─ NO → Transaction Value = Price paid or payable + additions - deductions
+ │ │ │ │ │ ├─ Additions (19 CFR § 152.103 / UCC Art. 71):
+ │ │ │ │ │ │ ├─ Commissions (except buying commissions)
+ │ │ │ │ │ │ ├─ Assists (tools, dies, moulds, engineering provided free/at reduced cost)
+ │ │ │ │ │ │ ├─ Royalties and licence fees related to the imported goods, payable as
+ │ │ │ │ │ │ │ a condition of sale
+ │ │ │ │ │ │ ├─ Packing costs
+ │ │ │ │ │ │ ├─ Proceeds of subsequent resale accruing to the seller
+ │ │ │ │ │ │ └─ US: cost of transport TO the US port (ocean/air freight, insurance)
+ │ │ │ │ │ │ EU: transport and insurance to the EU border are INCLUDED
+ │ │ │ │ │ │ (CIF basis for EU, FOB+ for US)
+ │ │ │ │ │ └─ Deductions (not included in transaction value):
+ │ │ │ │ │ ├─ Post-importation transport costs (inland freight)
+ │ │ │ │ │ ├─ Import duties and taxes
+ │ │ │ │ │ ├─ Construction/installation costs after importation
+ │ │ │ │ │ └─ Buying commissions (if clearly identified)
+ │ │ │ │ └─ CLASSIFY VALUE. STOP.
+ │ │ │ └─ YES → Skip to Method 2
+ │ │ └─ YES (related parties) →
+ │ │ ├─ Did the relationship influence the price?
+ │ │ │ ├─ NO (demonstrate with "circumstances of sale" test or test values) →
+ │ │ │ │ Transaction Value is acceptable. Apply additions/deductions above.
+ │ │ │ └─ YES or cannot demonstrate → Skip to Method 2
+ │ │ └─ OR: Does the transaction value approximate a "test value"?
+ │ │ (transaction value of identical/similar goods to unrelated buyers,
+ │ │ deductive value, or computed value for identical/similar goods)
+ │ │ ├─ YES → Transaction Value acceptable. STOP.
+ │ │ └─ NO → Skip to Method 2
+ │
+ ├─ Method 2: Transaction Value of Identical Goods
+ │ ├─ Are there importations of IDENTICAL goods?
+ │ │ (same in all respects: physical characteristics, quality, reputation, country of origin)
+ │ ├─ Sold for export at the same commercial level and in substantially the same quantity?
+ │ │ (Adjustments permitted for quantity differences and transport costs)
+ │ ├─ Sold at or about the same time as the goods being valued?
+ │ │ ├─ YES to all → Use the transaction value of those identical goods. STOP.
+ │ │ └─ NO to any → Skip to Method 3
+ │
+ ├─ Method 3: Transaction Value of Similar Goods
+ │ ├─ Same criteria as Method 2, but for goods that are "similar" —
+ │ │ closely resembling in characteristics, components, materials,
+ │ │ and capable of performing the same functions and being commercially interchangeable
+ │ │ ├─ Available → Use. STOP.
+ │ │ └─ Not available → Skip to Method 4 (or Method 5 at importer's request in the US)
+ │
+ ├─ Method 4: Deductive Value
+ │ ├─ Start with the unit price at which the greatest aggregate quantity is sold
+ │ │ in the country of importation (within 90 days of import date)
+ │ ├─ DEDUCT:
+ │ │ ├─ Commissions or profit and general expenses normally earned on sales in the
+ │ │ │ importing country for goods of the same class or kind
+ │ │ ├─ Transport and insurance costs within the importing country
+ │ │ ├─ Customs duties and other national taxes payable on importation
+ │ │ └─ If the goods are further processed after importation ("super deductive"):
+ │ │ deduct the value added by the processing
+ │ └─ Result = Deductive Value. STOP.
+ │
+ ├─ Method 5: Computed Value
+ │ ├─ BUILD UP from:
+ │ │ ├─ Cost or value of materials and fabrication/processing in the producing country
+ │ │ ├─ Amount for profit and general expenses equal to that usually reflected in sales
+ │ │ │ of goods of the same class or kind from the country of exportation
+ │ │ └─ Cost of transport and insurance to the importing country (CIF for EU, FOB+ for US)
+ │ ├─ This method is only available if the foreign producer is willing to share cost data
+ │ │ and submit to verification by the importing country's customs authority
+ │ └─ Result = Computed Value. STOP.
+ │
+ └─ Method 6: Fallback ("Reasonable Means")
+ ├─ Flexible application of Methods 1-5 with reasonable adjustments
+ ├─ Prohibitions — the value CANNOT be based on:
+ │ ├─ Selling price of goods produced in the importing country
+ │ ├─ A system providing for use of the higher of two alternative values
+ │ ├─ The price of goods in the domestic market of the country of exportation
+ │ ├─ Minimum customs values
+ │ ├─ Arbitrary or fictitious values
+ │ └─ Cost of production other than computed values for identical/similar goods
+ └─ Result = Fallback Value. STOP.
+```
+
+### 3.2 Related-Party Valuation — Circumstances of Sale Test
+
+When the buyer and seller are related (per 19 USC § 1401a(g) or UCC Art. 127), customs
+authorities will scrutinise the transaction value. To demonstrate that the relationship did not
+influence the price:
+
+**Evidence that supports acceptance:**
+
+1. The price was settled in a manner consistent with normal pricing practices in the industry
+2. The price was settled in a manner consistent with how the seller prices to unrelated buyers
+3. The price is adequate to ensure recovery of all costs plus a profit equivalent to the
+ firm's overall profit over a representative period in sales of goods of the same class or kind
+4. Transfer pricing documentation showing the price was set at arm's length under OECD guidelines
+
+**Test values (alternative to circumstances of sale):**
+
+The transaction value is acceptable if it closely approximates one of:
+- Transaction value on identical or similar goods sold to unrelated buyers in the importing country
+- Deductive value for identical or similar goods
+- Computed value for identical or similar goods
+
+"Closely approximates" means within a reasonable range — CBP and EU customs have discretion here,
+but differences under 5% are generally accepted, 5-10% require explanation, and over 10% will
+likely trigger rejection of the transaction value.
+
+### 3.3 Assists Valuation
+
+Assists are one of the most frequently overlooked additions to transaction value. An assist is
+anything the buyer provides to the seller free of charge or at reduced cost for use in producing
+the imported goods:
+
+**Types of assists:**
+
+| Assist Type | Valuation Method | Apportionment |
+|---|---|---|
+| Materials consumed in production (raw materials, components) | Cost of acquisition or production | Full value added to first shipment, or prorated across all units produced |
+| Tools, dies, moulds, and similar items | Cost of acquisition or production; if previously used, current value only | Prorated across the number of units produced using the tool/die/mould |
+| Engineering, development, artwork, design, plans, and sketches | Cost if undertaken in the importing country; value if undertaken elsewhere | Prorated across anticipated total production, or first shipment |
+| Materials consumed in production provided by related parties | Price paid between related parties if arm's length; otherwise cost of production | Same as unrelated-party assists |
+
+**Critical assist trap:** A US company sends CAD drawings to a Chinese manufacturer at no charge.
+The value of producing those drawings (engineering time, software licences) must be added to the
+customs value of every import from that manufacturer that uses those drawings. Failure to declare
+assists is one of the top findings in CBP Focused Assessments and triggers penalty exposure.
+
+### 3.4 Royalties and Licence Fees
+
+Royalties are dutiable additions to transaction value when they are:
+1. Related to the imported goods (not to post-importation activity), AND
+2. Paid as a condition of the sale (the buyer cannot buy the goods without paying the royalty)
+
+**Dutiable examples:**
+- Royalty paid to the seller (or a related party) for the right to manufacture using a patented
+ process — the royalty directly relates to production of the imported goods
+- Trademark licence fee paid to the parent company where the manufacturer will only produce
+ goods bearing the trademark for the licensed importer
+- Technology licence fee where the foreign producer can only access the technology through the
+ buyer's licence
+
+**Non-dutiable examples:**
+- Royalty for the right to distribute or resell in the importing country (post-importation activity)
+- Royalty paid to an unrelated third party where the seller has no knowledge of or interest in
+ the royalty arrangement and the royalty is not a condition of the sale
+
+**The "condition of sale" analysis is fact-intensive.** Look at:
+- Would the seller sell the goods to the buyer without the royalty being paid?
+- Does the seller have any involvement in, or control over, the royalty arrangement?
+- Can the buyer source the goods elsewhere if the royalty is not paid?
+
+---
+
+## 4. Restricted Party Screening Protocol
+
+### 4.1 Screening Workflow
+
+```
+START: New transaction (sale, purchase, or service)
+ │
+ ├─ Step 1: Identify ALL parties to the transaction
+ │ ├─ Buyer / importer of record
+ │ ├─ Seller / exporter
+ │ ├─ Ultimate consignee / end user
+ │ ├─ Intermediate consignees
+ │ ├─ Freight forwarders and customs brokers
+ │ ├─ Banks (in letter of credit transactions)
+ │ ├─ Ship-to addresses (if different from buyer/consignee)
+ │ └─ Any agents, representatives, or beneficial owners
+ │
+ ├─ Step 2: Screen ALL identified parties against ALL applicable lists
+ │ ├─ US Lists (if US nexus exists — US-origin goods, US persons, US financial system):
+ │ │ ├─ OFAC SDN List (Specially Designated Nationals and Blocked Persons)
+ │ │ ├─ OFAC Sectoral Sanctions Identifications (SSI) List
+ │ │ ├─ OFAC Non-SDN Menu-Based Sanctions List (NS-MBS)
+ │ │ ├─ BIS Entity List (Supplement No. 4 to Part 744)
+ │ │ ├─ BIS Denied Persons List
+ │ │ ├─ BIS Unverified List
+ │ │ ├─ BIS Military End User (MEU) List
+ │ │ ├─ DDTC Debarred Parties (AECA Section 38)
+ │ │ └─ Non-Proliferation Sanctions lists
+ │ ├─ EU Lists (if EU nexus exists):
+ │ │ ├─ EU Consolidated Financial Sanctions List
+ │ │ └─ EU Dual-Use Regulation Annex I controlled end-users
+ │ ├─ UK Lists (if UK nexus exists):
+ │ │ ├─ UK OFSI Consolidated List
+ │ │ └─ UK Export Control Joint Unit
+ │ ├─ Other Jurisdictions: Australia DFAT, Canada SEMA, Japan METI, etc.
+ │ └─ Internal denied/watch lists (prior compliance issues, flagged entities)
+ │
+ ├─ Step 3: Evaluate screening results
+ │ ├─ NO HITS → Document the screening (date, tool, parties screened, result).
+ │ │ Proceed with the transaction. STOP.
+ │ ├─ HITS RETURNED → Continue to Step 4
+ │
+ ├─ Step 4: Adjudicate each hit
+ │ ├─ For each hit, assess:
+ │ │ ├─ Name match quality (exact, near-exact, partial, phonetic)
+ │ │ ├─ Address correlation (same country? same city? same street?)
+ │ │ ├─ Date of birth / incorporation date (for individuals / entities)
+ │ │ ├─ Alias match (is the match against a known alias?)
+ │ │ ├─ Additional identifiers (passport #, tax ID, DUNS, vessel IMO#)
+ │ │ └─ Prior transaction history (known good customer for 10 years?)
+ │ ├─ FALSE POSITIVE (high confidence) → Document adjudication rationale.
+ │ │ Record: who adjudicated, date, factors considered, conclusion.
+ │ │ Proceed with transaction. STOP.
+ │ ├─ POSSIBLE MATCH (ambiguous) → Continue to Step 5
+ │ └─ TRUE POSITIVE (confirmed) → Continue to Step 6
+ │
+ ├─ Step 5: Escalate ambiguous matches
+ │ ├─ Request additional identifying information from the customer/counterparty
+ │ ├─ Engage compliance counsel
+ │ ├─ Do NOT proceed with the transaction until resolved
+ │ ├─ Document the hold and all steps taken
+ │ └─ If cannot be resolved → Treat as TRUE POSITIVE (Step 6)
+ │
+ └─ Step 6: True positive — full stop
+ ├─ BLOCK the transaction immediately
+ ├─ SDN/OFAC match:
+ │ ├─ Block and report to OFAC within 10 business days
+ │ ├─ Do not release goods, do not process payment, do not communicate
+ │ │ the reason to the blocked party
+ │ └─ Determine if an OFAC licence is available and warranted
+ ├─ Entity List match:
+ │ ├─ Determine licence requirement (most are "presumption of denial")
+ │ ├─ If a licence exception is available, document the basis
+ │ └─ If no exception, apply for a BIS licence (expect 60-90 day processing)
+ ├─ Denied Persons List match:
+ │ ├─ ABSOLUTE prohibition — no licence available
+ │ └─ No exports, re-exports, or in-country transfers to denied persons
+ ├─ Notify compliance officer and legal counsel
+ ├─ Document EVERYTHING — the hit, the adjudication, the decision, the block
+ └─ Retain records indefinitely for DPL; 5 years minimum for others
+```
+
+### 4.2 Red Flag Indicators — Enhanced Due Diligence Triggers
+
+When any of the following red flags are present, standard screening is insufficient. Conduct
+enhanced due diligence before proceeding:
+
+| Red Flag | What It Suggests | Required Action |
+|---|---|---|
+| Customer declines to state end use | Diversion risk | Require end-use certificate or decline the transaction |
+| Unusual routing (e.g., electronics shipped Lagos→Dubai→Baku) | Sanctions evasion / diversion to embargoed destination | Map the full supply chain; verify the final destination |
+| Customer willing to pay cash for high-value capital goods | Money laundering or sanctions circumvention | Enhanced KYC; verify source of funds |
+| Delivery to P.O. Box, residential address, or free trade zone | Concealment of true end user | Require physical street address and site visit if >$50K |
+| Product capability exceeds stated end use | Military/WMD diversion | Verify end-use statement matches the product specification |
+| Customer has no Internet presence or verifiable business history | Shell company or front for sanctioned entity | Company registration check, D&B report, beneficial ownership analysis |
+| Order for spare parts inconsistent with installed base | Stockpiling for embargoed destination | Request installed-base details; verify service history |
+| Customer requests removal of product labelling or markings | Circumvention of end-use controls or trademark fraud | Decline the request and escalate to compliance |
+| Customer or forwarding agent was previously flagged | Repeat compliance risk | Senior compliance review before any transaction |
+| Payment from a third party or country not involved in the transaction | Sanctions evasion through financial intermediaries | Verify the commercial rationale for the payment structure |
+
+---
+
+## 5. Penalty Risk Assessment
+
+### 5.1 US Penalty Framework — Detailed Analysis
+
+**19 USC § 1592 — Penalties for Fraud, Gross Negligence, and Negligence:**
+
+| Element | Fraud | Gross Negligence | Negligence |
+|---|---|---|---|
+| **Mental state** | Intentional and knowing violation with intent to defraud | Conscious disregard of a known duty or gross indifference | Failure to exercise reasonable care |
+| **Maximum penalty** | Domestic value of the merchandise | 4× lost revenue, or 40% of dutiable value | 2× lost revenue, or 20% of dutiable value |
+| **Criminal referral** | Yes — up to $10K fine and 2 years per count (18 USC § 542) | Rare | No |
+| **Proof burden** | CBP must prove fraud by clear and convincing evidence | CBP must prove by preponderance of the evidence | CBP must prove by preponderance; importer must show reasonable care |
+| **Mitigation potential** | Limited — requires extraordinary cooperation | Moderate — compliance programme, disclosure, cooperation | Significant — first offence, corrective actions, small scale |
+| **Prior disclosure effect** | Caps penalty at 1× lost revenue (if accepted) | Caps penalty at 1× lost revenue | Caps penalty at interest on the unpaid duties |
+| **Statute of limitations** | 5 years from date of violation | 5 years | 5 years |
+
+**Penalty Mitigation Factors (per CBP's Mitigation Guidelines):**
+
+1. **Contributory CBP error:** Did CBP accept prior entries with the same error without comment?
+2. **Cooperation:** Full cooperation with the investigation, including production of records and
+ internal investigation findings
+3. **Immediate corrective action:** Did the importer fix the problem as soon as it was discovered?
+4. **Prior good record:** Clean compliance history for 5+ years
+5. **Inability to pay:** Financial hardship (documented) can reduce monetary penalties
+6. **Scale of violation:** Isolated incident vs systemic pattern
+7. **Compliance programme:** Existence and effectiveness of an internal compliance programme
+
+### 5.2 Prior Disclosure Decision Framework
+
+```
+START: You have discovered a potential customs violation
+ │
+ ├─ Step 1: Assess — Has CBP already commenced an investigation?
+ │ ├─ YES (you've received a CF-28 Request for Information, CF-29 Notice of Action,
+ │ │ pre-penalty notice, or Focused Assessment notification) →
+ │ │ Prior disclosure is still available UNTIL a formal investigation has commenced.
+ │ │ A CF-28/29 alone does not constitute commencement. A pre-penalty notice does.
+ │ │ ├─ Pre-penalty notice or formal investigation commenced → Prior disclosure
+ │ │ │ is NOT available. Respond to the notice with legal counsel. STOP.
+ │ │ └─ Only CF-28/29 → Prior disclosure is still available. Continue.
+ │ └─ NO → Prior disclosure is available. Continue to Step 2.
+ │
+ ├─ Step 2: Determine the nature and scope of the violation
+ │ ├─ Classification error → How many entries are affected? Calculate total duty differential.
+ │ ├─ Valuation error → Quantify the underdeclared value and the corresponding duty impact.
+ │ ├─ Origin misstatement → Identify all affected entries and the correct origin.
+ │ ├─ FTA over-claim → Calculate the duty that should have been paid without the preference.
+ │ ├─ Record-keeping failure → Identify what records are missing and for which entries.
+ │ └─ Other → Define the specific violation and quantify the duty impact.
+ │
+ ├─ Step 3: Evaluate prior disclosure vs. alternative strategies
+ │ ├─ Prior disclosure IS advisable when:
+ │ │ ├─ The violation is clear-cut and the duty shortfall is quantifiable
+ │ │ ├─ You are confident CBP has not yet begun investigating this issue
+ │ │ ├─ The penalty exposure is material (prior disclosure caps it at interest/1×)
+ │ │ └─ The violation involves negligence or gross negligence (not fraud)
+ │ ├─ Prior disclosure may NOT be advisable when:
+ │ │ ├─ The classification or valuation position is defensible and you are prepared to litigate
+ │ │ ├─ The amount at issue is de minimis (the administrative cost of disclosure exceeds benefit)
+ │ │ ├─ The violation is uncertain — you may be disclosing something that isn't actually wrong
+ │ │ └─ The disclosure would reveal other issues CBP is unaware of (consult counsel first)
+ │ └─ ALWAYS consult legal counsel before filing. Prior disclosure is an admission of violation.
+ │
+ ├─ Step 4: Prepare the prior disclosure
+ │ ├─ Required elements (19 CFR § 162.74):
+ │ │ ├─ Identify the entry numbers and dates of all affected entries
+ │ │ ├─ Describe the specific violation (what was wrong)
+ │ │ ├─ Provide the correct information (what should have been declared)
+ │ │ ├─ Identify the circumstances that led to the violation (how it happened)
+ │ │ ├─ Calculate the duty owed with interest
+ │ │ └─ Tender the full amount of unpaid duties (or explain why you cannot calculate exactly
+ │ │ and provide a good-faith estimate with a commitment to pay the final amount)
+ │ ├─ File with the FP&F office at the port of entry (or the CEE with jurisdiction)
+ │ └─ Retain a copy with proof of delivery
+ │
+ └─ Step 5: Post-filing
+ ├─ CBP will review the disclosure and may request additional information
+ ├─ If accepted, you will receive a penalty notice limited to interest (negligence) or
+ │ 1× lost revenue (gross negligence)
+ ├─ If rejected (disclosure was incomplete, or investigation had already commenced),
+ │ full penalty exposure returns
+ └─ Implement corrective measures to prevent recurrence — CBP will look at this if
+ another violation occurs
+```
+
+### 5.3 Export Control Penalty Framework
+
+**BIS (EAR) Penalties:**
+- Civil: Up to $330,198 per violation OR twice the value of the transaction, whichever is greater
+ (adjusted annually for inflation)
+- Criminal: Up to $1,000,000 per violation and 20 years imprisonment
+- Denial of export privileges: automatic bar from all exports/re-exports from the US
+
+**DDTC (ITAR) Penalties:**
+- Civil: Up to $1,301,256 per violation (adjusted annually)
+- Criminal: Up to $1,000,000 per violation and 20 years imprisonment
+- Debarment from all ITAR-controlled exports
+
+**OFAC Penalties:**
+- Vary by sanctions programme, but civil penalties can exceed $330,000 per violation for
+ IEEPA-based sanctions
+- Criminal: up to $1,000,000 and 20 years imprisonment under IEEPA
+- Strict liability for OFAC violations — no intent required for civil penalties
+
+---
+
+## 6. Post-Entry Audit Preparation
+
+### 6.1 CBP Focused Assessment Preparation Checklist
+
+When a CBP Focused Assessment is announced, the following preparation is critical:
+
+**Documentation to assemble:**
+- [ ] Internal compliance manual / SOP documentation
+- [ ] Organisational chart showing compliance function reporting lines
+- [ ] Training records for all personnel involved in import operations
+- [ ] Customs broker power of attorney and instructions
+- [ ] Classification decisions with supporting rationale (for sample entries)
+- [ ] Valuation documentation including assist calculations and related-party analysis
+- [ ] FTA qualification files with supplier certifications
+- [ ] Restricted party screening logs with adjudication records
+- [ ] Reconciliation entries (if applicable)
+- [ ] Prior disclosures filed (if any)
+- [ ] Internal audit reports for the past 3 years
+- [ ] Record retention policy and evidence of compliance
+
+**Pre-assessment self-audit:**
+1. Pull 50 representative entries spanning the audit period
+2. Re-classify the top 20 by value — does the classification still hold?
+3. Re-value 10 entries including related-party transactions — are assists captured?
+4. Verify FTA claims on 10 entries — is the origin documentation complete?
+5. Re-screen all parties from 10 entries — any new hits since original screening?
+6. Identify and disclose any errors found BEFORE the FA team arrives (prior disclosure still available)
+
+---
+
+## 7. Incoterms Decision Matrix
+
+### 7.1 Selecting the Appropriate Incoterm
+
+| Consideration | Recommended Incoterm | Rationale |
+|---|---|---|
+| Buyer wants maximum control over logistics | FCA | Buyer chooses carrier, route, and insurance. Seller handles export formalities. |
+| Seller has better freight rates (economy of scale) | CIF / CIP | Seller leverages volume contracts. Buyer bears risk from first carrier. |
+| Buyer cannot act as exporter in seller's country | FCA, CPT, CIP, DAP, DDP | Avoid EXW — it makes the buyer the exporter of record in the origin country. |
+| Buyer lacks import capability in destination | DDP | Seller handles everything including import clearance. Seller must register as IOR. |
+| Letter of credit requires on-board BOL | FCA (with 2020 A6/B6 option) | The 2020 revision allows buyer to instruct carrier to issue on-board BOL to seller. |
+| High-risk transit (theft, damage, piracy corridor) | CIF / CIP | Seller is responsible for insurance. CIP requires all-risks coverage (ICC A). |
+| Containerised ocean freight | FCA, CPT, CIP | FOB is technically incorrect for containers — risk transfers at container yard, not ship's rail. |
+| Domestic delivery (same country) | FCA, DAP | Incoterms are not required for domestic; if used, FCA or DAP are appropriate. |
+
+### 7.2 Incoterms and Customs Valuation Impact
+
+The Incoterm affects the customs value because different terms include or exclude freight and
+insurance in the invoice price:
+
+| Incoterm | US Customs Value Adjustment | EU Customs Value Adjustment |
+|---|---|---|
+| EXW | ADD: inland freight to port + international freight + insurance to US port | ADD: inland freight to port + international freight + insurance to EU border |
+| FCA | ADD: international freight + insurance from named place to US port | ADD: international freight + insurance from named place to EU border |
+| FOB | ADD: ocean freight + insurance to US port (already includes inland to port) | ADD: ocean freight + insurance to EU border |
+| CFR/CPT | ADD: insurance (freight already included) | ADD: insurance (freight already included) |
+| CIF/CIP | No adjustment (freight and insurance included) | No adjustment (freight and insurance included) |
+| DAP | DEDUCT: inland freight from port/airport to final destination in US (if identifiable) | DEDUCT: inland freight from EU border to destination |
+| DDP | DEDUCT: inland freight + import duties (duty is never part of customs value) | DEDUCT: inland freight from EU border + import duties |
diff --git a/web-app/public/skills/customs-trade-compliance/references/edge-cases.md b/web-app/public/skills/customs-trade-compliance/references/edge-cases.md
new file mode 100644
index 00000000..69b90747
--- /dev/null
+++ b/web-app/public/skills/customs-trade-compliance/references/edge-cases.md
@@ -0,0 +1,362 @@
+# Customs & Trade Compliance — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous trade compliance situations that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced trade compliance professionals from everyone else. Each one involves competing regulatory frameworks, ambiguous fact patterns, multi-jurisdictional complexity, and real financial exposure. They are structured to guide resolution when standard procedures break down.
+
+---
+
+## How to Use This File
+
+When a trade compliance question doesn't fit a clean category — when classification is genuinely ambiguous, when origin is disputed, when multiple regulatory regimes apply simultaneously, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; these are the cases that end up before administrative law judges, in penalty proceedings, or in criminal referrals.
+
+---
+
+### Edge Case 1: De Minimis Threshold Exploitation — Section 321 Abuse
+
+**Situation:**
+A mid-size e-commerce retailer imports consumer electronics from Shenzhen. Their freight forwarder suggests restructuring ocean freight consolidations into individual direct-to-consumer parcels, each valued under $800, to clear under Section 321 de minimis and avoid the 25% Section 301 duty on List 3 goods. The retailer currently imports approximately 15,000 units per month at a declared value of $45 per unit (total duty exposure: approximately $168,750/month at 25%). The forwarder's proposal would route parcels through a fulfilment centre in China that ships individual packages via ePacket/USPS to US consumers.
+
+**Why It's Tricky:**
+The de minimis threshold is per importation, per person, per day. On its face, individual shipments valued at $45 each qualify. But CBP has increasingly targeted structured de minimis programmes, and the Consolidated Appropriations Act of 2016 gave CBP expanded enforcement authority. Several factors complicate this:
+
+- If the retailer is the importer of record for all packages (not the individual consumers), CBP can aggregate all packages arriving on the same day as a single importation
+- Section 321 does NOT exempt goods subject to AD/CVD orders, quotas, or certain PGA requirements (FDA, CPSC, EPA) — only the duty is waived
+- If the electronics require FCC certification, each unit still needs to comply regardless of de minimis status
+- CBP's e-commerce enforcement strategy specifically targets "daigou" and structured de minimis programmes
+
+**Common Mistake:**
+Assuming that Section 321 is a simple value threshold. Many importers and their forwarders treat it as a binary: under $800, no duty. But the aggregation rules, PGA requirements, and enforcement posture make structured programmes a significant compliance risk. CBP has issued penalty cases exceeding $1M against importers who structured shipments to exploit de minimis.
+
+The second mistake: ignoring state sales tax and marketplace facilitator obligations. Even if federal duty is avoided, the retailer may have nexus obligations in destination states that offset some of the savings.
+
+**Expert Approach:**
+1. Assess whether the individual consumers are genuinely the importers of record. If the retailer controls the logistics, owns the inventory in transit, and bears the risk of loss, the retailer is the IOR — not the consumer. This makes aggregation almost certain.
+2. Review the specific HS codes for AD/CVD applicability. Electronics are generally not subject to AD/CVD, but certain components (e.g., crystalline silicon PV cells, certain steel enclosures) may be covered.
+3. Check PGA requirements. Consumer electronics almost certainly require FCC Declaration of Conformity. Lithium batteries require DOT/PHMSA compliance. Children's products require CPSC testing. None of these are waived by Section 321.
+4. Calculate the true savings vs risk. The duty savings of $168,750/month must be weighed against: (a) per-unit shipping cost increase (ocean FCL at $0.35/unit vs ePacket at $3-5/unit), (b) compliance risk (penalty exposure under 19 USC § 1592 for structured evasion), (c) transit time increase (30-45 days ocean + inland vs 14-21 days ePacket but no inventory buffer), (d) customer experience impact (inconsistent delivery times, returns complexity).
+5. If the economics still favour de minimis after honest analysis, structure it properly: each consumer must be the IOR, the retailer should use a compliant Section 321 filing programme (not just undervalue or misdeclare), and all PGA requirements must be satisfied per shipment.
+6. Document the business rationale and legal analysis thoroughly. If CBP challenges the programme, the difference between "structured evasion" (penalty) and "legitimate programme" (defensible) is documentation of good-faith compliance effort.
+
+**Key Indicators:**
+- CBP's COAC subcommittee on Section 321 has recommended enhanced data requirements — anticipate changes
+- Multiple packages to the same address on the same day from the same shipper will be flagged
+- The STOP Act of 2018 requires electronic advance data for all international mail shipments — the "under the radar" strategy no longer works
+
+---
+
+### Edge Case 2: Transshipment Circumventing AD/CVD Duties — EAPA Investigation
+
+**Situation:**
+A US furniture importer purchases wooden bedroom furniture "manufactured in Vietnam" from a Vietnamese trading company. The unit price is $180 FOB Ho Chi Minh City, which is 40% below comparable Vietnamese production costs. Coincidentally, Chinese-origin wooden bedroom furniture is subject to AD/CVD duties totalling 216.01% (combined AD duty of 198.08% + CVD of 17.93%) under A-570-890. CBP initiates an EAPA (Enforce and Protect Act) investigation based on an allegation from a domestic manufacturer.
+
+**Why It's Tricky:**
+The EAPA process gives CBP subpoena authority and the ability to impose interim measures (cash deposits at the AD/CVD rate) within 90 days. The importer must prove that the goods are genuinely of Vietnamese origin — which requires demonstrating "substantial transformation" in Vietnam. The test is whether the processing in Vietnam results in "a new and different article of commerce with a new name, character, and use."
+
+Vietnamese furniture factories that merely assemble Chinese-manufactured components (pre-cut panels, pre-finished parts) into finished furniture are almost certainly NOT performing substantial transformation. But factories that take raw lumber (even Chinese-origin lumber), mill it, join it, finish it, and assemble it in Vietnam likely ARE performing substantial transformation, because the raw lumber has been transformed into a finished article with a different name, character, and use.
+
+The grey area is where the Vietnamese factory receives semi-finished components (rough-cut panels, unfinished drawer boxes) and performs significant but not complete processing (sanding, finishing, assembly, quality control, packaging). This is where most disputes land.
+
+**Common Mistake:**
+Relying on the certificate of origin from the Vietnamese chamber of commerce as proof of origin. Certificates of origin attest to the country of EXPORTATION, not the country of substantial transformation. CBP will look through the certificate to the actual manufacturing process.
+
+The second mistake: waiting for CBP to ask questions before investigating your own supply chain. If CBP is conducting an EAPA investigation against your supplier, the best position is to have already audited the supply chain and be able to present a documented analysis.
+
+**Expert Approach:**
+1. Immediately retain trade counsel experienced in AD/CVD and EAPA proceedings. The timelines are short and the penalties are severe (retroactive application of AD/CVD rates to all entries, plus potential fraud referral).
+2. Request from the Vietnamese supplier: (a) complete bill of materials showing the origin of all inputs, (b) production flow chart from raw material receipt to finished goods shipment, (c) cost of production analysis showing the value added in Vietnam, (d) photographs and video of the production process, (e) list of Chinese-origin inputs by HS code and value.
+3. Apply the substantial transformation test. Map each Chinese-origin input through the Vietnamese production process. Determine: does the finished furniture have a different name (yes — "lumber" → "bedroom set"), different character (depends on the degree of processing), and different use (raw lumber has construction and industrial uses; finished furniture has a consumer use)? All three must change.
+4. Calculate the value added in Vietnam as a percentage of the FOB price. While there's no statutory minimum, CBP generally views less than 30% value addition with suspicion. If the Vietnamese factory's value addition (labour, overhead, materials consumed, profit) is less than 30% of the export price, the substantial transformation argument is weak.
+5. If the supply chain analysis reveals that the goods are effectively Chinese-origin with minimal Vietnamese processing, consider: (a) voluntary disclosure to CBP (prior disclosure of AD/CVD evasion caps penalties), (b) restructuring the supply chain to use a Vietnamese factory with genuine manufacturing capability, (c) sourcing from a non-subject country with genuine production.
+6. If the supply chain analysis supports genuine Vietnamese origin, compile the documentation package and be prepared to present it to CBP within the EAPA timeline. Proactive submission of evidence carries significant weight with CBP investigators.
+
+**Key Indicators:**
+- Unit price significantly below production cost in the alleged country of origin is a primary trigger for EAPA complaints
+- Vietnam, Malaysia, Thailand, and Indonesia are the top countries for transshipment allegations on Chinese AD/CVD goods
+- CBP may conduct on-site verification at the Vietnamese factory — prepare the factory for a CBP visit
+- CBP's Allegations Management and Tracking System (AMATS) allows domestic producers to file electronically — expect more allegations
+
+---
+
+### Edge Case 3: Dual-Use Goods — EAR/ITAR Jurisdictional Boundary
+
+**Situation:**
+A US manufacturer produces high-precision CNC milling machines with 5-axis simultaneous contouring capability and positioning accuracy of ±2 microns. The machines are sold commercially to automotive and aerospace manufacturers worldwide. A new customer in India requests a quote for 3 machines to be used in "precision component manufacturing." The machines have a commercial ECCN of 2B001.b.2 under the EAR (controlled for NP, NS, AT reasons). However, the machines could also be used in the production of missile components, and some configurations have historically been considered for ITAR control under USML Category IV (Launch Vehicles, Guided Missiles, Ballistic Missiles, Rockets, Torpedoes, Bombs, and Mines) — specifically, production equipment "specially designed" for USML items.
+
+**Why It's Tricky:**
+This sits at the exact boundary between the EAR (administered by BIS, Department of Commerce) and the ITAR (administered by DDTC, Department of State). The Export Control Reform (ECR) initiative moved many items from the USML to the CCL, but the "specially designed" definition (§ 772.1 of the EAR) creates a complex exclusion/inclusion analysis. If the machine is classified under the ITAR, an export licence is almost certainly required for India and the end-use controls are far more restrictive. If it's under the EAR, a licence may or may not be required depending on the end user and end use.
+
+The critical determination is whether the machine is "specially designed" for USML articles. Under the ECR definition, an item is NOT "specially designed" if it meets any of the six "release" criteria in paragraph (b) of the definition — most importantly, (b)(3): the item "has a function other than" producing USML items and is "not a dedicated tool, jig, fixture, mould, or die." A general-purpose CNC mill that can make many types of precision components likely qualifies for the (b)(3) release. But if the specific configuration being sold is optimised for producing specific missile components, the release may not apply.
+
+**Common Mistake:**
+Self-classifying the item under the EAR without formally resolving the jurisdictional question. If the item is ITAR-controlled and exported under an EAR classification, the exporter has committed violations of BOTH regimes — an unauthorised ITAR export AND a false EAR filing. The correct procedure when jurisdiction is unclear is to submit a Commodity Jurisdiction (CJ) request to DDTC.
+
+The second mistake: assuming that because the machine is sold commercially to many industries, it's automatically EAR-jurisdiction. Commercial availability is relevant but not dispositive. A commercially available item that is "specially designed" for USML applications is ITAR-controlled regardless of its commercial sales history.
+
+**Expert Approach:**
+1. Conduct the "specially designed" analysis under the ECR definition for the SPECIFIC configuration being sold to the Indian customer. Document: (a) what are ALL the functions this machine configuration can perform? (b) is this configuration a "dedicated" production tool for any USML article, or a general-purpose machine? (c) does it meet any of the (b)(1) through (b)(6) release criteria?
+2. If the analysis is clear (the machine is a general-purpose commercial product that meets the (b)(3) release), document the analysis and proceed with EAR classification. Confirm the ECCN (2B001.b.2) and determine the licence requirement for India. For NP-controlled items to India, a licence is likely required unless a licence exception applies. Check BIS's India entity list entries.
+3. If the analysis is ambiguous (the configuration could be considered "specially designed"), file a CJ request with DDTC. Include: the item's technical specifications, its commercial applications, its potential USML applications, and your "specially designed" analysis. DDTC has 45 days to respond (often takes longer).
+4. While the CJ is pending, do NOT ship the machines. Treat the item as ITAR-controlled until DDTC makes a determination.
+5. Regardless of jurisdiction, conduct end-user due diligence on the Indian customer. The machines' accuracy (±2 microns) places them at or near the MTCR (Missile Technology Control Regime) Annex thresholds. Verify: (a) the customer's identity and business operations, (b) the stated end use is consistent with the customer's business, (c) the customer is not on any restricted party list, (d) there are no red flags suggesting missile programme diversion.
+6. If the machines are EAR-jurisdiction and a licence is required, include the Indian customer's end-use statement and the complete technical specifications in the BIS licence application. Processing time is typically 30-60 days.
+7. If the machines are ITAR-jurisdiction, apply for a DSP-5 export licence from DDTC. Processing time is typically 60-90 days, and India is subject to additional review for missile-related items.
+
+**Key Indicators:**
+- 5-axis simultaneous contouring capability at ±2 microns places this firmly in the controlled range under both regimes
+- India is a missile technology-sensitive destination — enhanced scrutiny is expected
+- The phrase "precision component manufacturing" in the customer's end-use statement is too vague — require specificity
+- If the customer refuses to specify the components being manufactured, this is a red flag under § 744.6 (General Prohibition Six)
+
+---
+
+### Edge Case 4: Post-Importation Transfer Pricing Adjustments
+
+**Situation:**
+A multinational pharmaceutical company imports active pharmaceutical ingredients (APIs) from its German parent company. The transfer price is set annually by the parent's tax department using the Comparable Profits Method (CPM) under OECD Transfer Pricing Guidelines. The US subsidiary imports approximately $200M in APIs annually. At fiscal year-end, the tax department determines that the US subsidiary's operating margin exceeded the arm's-length range and issues a downward transfer pricing adjustment of $18M (effectively reducing the price paid for the APIs retroactively). The US subsidiary's trade compliance team discovers that all entries during the fiscal year were declared at the higher, pre-adjustment value.
+
+**Why It's Tricky:**
+Customs valuation and transfer pricing serve opposite purposes. Tax authorities want the transfer price to be high in low-tax jurisdictions and low in high-tax jurisdictions (to minimize global tax). Customs authorities want the declared value to be as high as possible (to maximize duties collected). A downward transfer pricing adjustment reduces the customs value — which means the importer overpaid duties and is entitled to a refund. An upward adjustment increases the customs value — which means the importer underpaid duties and owes additional payments plus potential penalties.
+
+CBP's position (articulated in multiple rulings) is that transfer pricing adjustments must be reflected in the customs value when they relate to the imported merchandise. But the mechanism for doing so — reconciliation entries — has specific procedural requirements that many importers miss.
+
+**Common Mistake:**
+Ignoring the customs implications entirely because "transfer pricing is a tax issue." The trade compliance team often doesn't learn about year-end adjustments until months after they occur, by which time entries may have liquidated and the window for correction has closed.
+
+The second mistake: filing a PSC (Post Summary Correction) to reduce the declared value without proper documentation. CBP will challenge a downward correction on related-party entries unless the importer can demonstrate that the adjusted price satisfies the transaction value test under Method 1.
+
+**Expert Approach:**
+1. Flag reconciliation at the time of importation. When the final price is not known at entry (as with transfer pricing that is subject to year-end adjustment), file entries with the reconciliation flag set. This preserves the right to adjust the declared value after liquidation under the reconciliation programme (19 CFR Part 181 Subpart D for USMCA, or Part 182 for general reconciliation).
+2. When the transfer pricing adjustment is finalised, determine the direction and magnitude:
+ - Downward adjustment ($18M in this case): the importer overpaid duties. File reconciliation entries reducing the declared value and request a refund of excess duties paid. CBP will scrutinise the related-party circumstances of sale.
+ - Upward adjustment: the importer underpaid duties. File reconciliation entries increasing the declared value and tender the additional duties owed. This is effectively a prior disclosure of underpayment.
+3. To support the adjusted value, prepare a "circumstances of sale" analysis demonstrating that the related-party relationship did not influence the price. This requires showing that the transfer pricing methodology produces a price consistent with arm's-length pricing. The CPM analysis from the tax department is helpful but not sufficient — CBP wants to see that the price approximates a "test value" (transaction value of identical/similar goods to unrelated buyers).
+4. If reconciliation was NOT flagged at entry, file PSCs for entries within the liquidation period (typically 314 days from date of entry). For entries that have already liquidated, file a protest under 19 USC § 1514 within 180 days of liquidation. For entries beyond the protest period, the opportunity is lost.
+5. Establish a standing protocol between the trade compliance and tax departments. Require that: (a) trade compliance is notified of all transfer pricing adjustments before they are finalised, (b) reconciliation is flagged on all related-party entries where the price may be adjusted, (c) the tax department's transfer pricing study is shared with trade compliance for customs valuation analysis.
+6. For the $18M downward adjustment: at a 6.5% duty rate (common for APIs), the duty refund would be approximately $1.17M. The administrative cost of filing reconciliation is approximately $5,000-$15,000 (broker fees + internal time). The ROI is overwhelming — do not leave the refund on the table.
+
+**Key Indicators:**
+- Related-party import volume > $50M annually almost guarantees that transfer pricing adjustments will occur
+- CBP's Centers of Excellence and Expertise (Pharmaceutical CEE in New York) actively audits related-party valuations
+- Reconciliation programme participation requires advance approval from CBP — apply before entry, not after
+- The OECD's Two-Pillar Solution may change transfer pricing dynamics significantly — monitor developments
+
+---
+
+### Edge Case 5: First Sale Valuation — Multi-Tier Supply Chain
+
+**Situation:**
+A US apparel retailer sources private-label clothing through a Hong Kong buying agent. The supply chain is: Chinese factory sells to Hong Kong middleman at $8.00/unit (first sale), Hong Kong middleman sells to the US retailer at $12.50/unit (last sale). The goods ship directly from China to the US — they never physically pass through Hong Kong. The applicable duty rate is 19.7%. The retailer wants to declare the $8.00 first sale price as the customs value instead of the $12.50 last sale price, saving $0.89 per unit in duty (($12.50 - $8.00) × 19.7% = $0.89). At 2 million units annually, this is $1.78M in annual duty savings.
+
+**Why It's Tricky:**
+The "first sale rule" derives from the US Court of International Trade's decision in Nissho Iwai American Corp. v. United States (1982). CBP allows the use of the first sale as the transaction value when: (1) the first sale is a bona fide sale for export to the US, (2) the sale is at arm's length, and (3) the price of the first sale is the appropriate measure of the value of the goods when they enter the US.
+
+The challenge is proving all three elements, especially when the middleman adds no physical processing — the goods ship directly from factory to US. CBP scrutinises these arrangements because the middleman's margin (here, $4.50/unit or 56% markup) is significant and may include services that should be additions to the customs value rather than excludable middleman profit.
+
+**Common Mistake:**
+Claiming first sale without maintaining contemporaneous documentation of the factory-to-middleman sale. CBP requires that the first sale be documented with its own commercial invoice, payment records, and shipping instructions that demonstrate it is a genuine sale separate from the middleman-to-importer sale.
+
+The second mistake: failing to account for assists. If the US retailer provides design specifications, tech packs, or quality standards directly to the Chinese factory (bypassing the middleman), these are assists that must be added to the first sale price. Many first sale programmes collapse during audit because the assists were not valued.
+
+**Expert Approach:**
+1. Verify the first sale is a genuine arm's-length transaction. Required documentation:
+ - Separate commercial invoice from the Chinese factory to the Hong Kong middleman
+ - Evidence of payment from the middleman to the factory (bank records)
+ - The factory invoice must pre-date or be contemporaneous with the middleman's invoice to the US retailer
+ - Shipping instructions showing the goods were shipped FOR the middleman (not just invoiced through the middleman)
+2. Analyse the middleman's role. Legitimate first sale structures involve a middleman who: bears title risk, carries inventory risk (even briefly), can independently choose suppliers, negotiates prices independently with both the factory and the buyer, and provides genuine services (sourcing, quality control, logistics coordination). A middleman who is merely invoicing without bearing commercial risk is not a genuine seller — it's a conduit.
+3. Identify all assists flowing from the US retailer to the factory. Every tech pack, design file, sample, lab testing result, or quality inspection provided by the retailer is an assist. Compute the total value and add it to the first sale price. If assists exceed $2.50/unit, the effective first sale price rises to $10.50 and the savings diminish significantly.
+4. Calculate the actual duty savings after all adjustments:
+ - Last sale value: $12.50 → Duty: $2.4625
+ - First sale value (with assists): $8.00 + $1.80 assists = $9.80 → Duty: $1.9306
+ - Net savings per unit: $0.5319 × 2M units = $1,063,800/year
+ - Programme administration cost: approximately $50,000/year (broker fees, documentation, monitoring)
+ - Net benefit: approximately $1,013,800/year
+5. Prepare a first sale ruling request to CBP if the programme exceeds $500K in annual duty savings. A binding ruling provides certainty and significantly reduces audit risk. Include all documentation from steps 1-4.
+6. Monitor the programme quarterly. If the middleman's margin changes significantly, or if the retailer begins providing additional assists, the first sale analysis must be updated.
+
+**Key Indicators:**
+- First sale is ONLY available in the US, Israel, and Australia — the EU, UK, Canada, and most other jurisdictions value on the last sale before importation
+- CBP has revoked first sale treatment in multiple audits where documentation was insufficient
+- If the middleman is related to the factory, first sale treatment is extremely difficult to defend
+- The middleman's markup should reflect genuine commercial services — a 56% markup requires explanation of what services justify that margin
+
+---
+
+### Edge Case 6: Retroactive FTA Claims — Missed Preferential Treatment
+
+**Situation:**
+An internal audit reveals that a US electronics manufacturer has been importing circuit board assemblies from Mexico at the MFN rate of 3.4% for the past 3 years without claiming USMCA preferential treatment. The assemblies qualify for duty-free treatment under USMCA because they undergo a tariff shift from heading 8534 (printed circuits) to heading 8538 (parts for switching apparatus) in Mexico — all non-originating materials (capacitors from Japan, resistors from Korea) change at the heading level. The company imports approximately $15M annually; the overpaid duty totals approximately $1.53M over 3 years.
+
+**Why It's Tricky:**
+USMCA allows retroactive preferential claims, but the mechanism and timeline vary depending on how the entries were filed and whether they have liquidated:
+
+- Entries within the liquidation period (typically 314 days from entry): file a PSC (Post Summary Correction) claiming USMCA preference and attaching the certification of origin
+- Entries that have liquidated but are within the 180-day protest window: file a protest under 19 USC § 1514
+- Entries that have liquidated AND the protest period has expired: file a petition for reliquidation under 19 USC § 1520(d), which allows up to 1 year from the date of liquidation
+
+After these windows close, the duties are permanently overpaid.
+
+**Common Mistake:**
+Assuming all 3 years of entries can be recovered. In practice, the oldest entries have almost certainly passed all available windows. The recoverable amount depends on when exactly each entry liquidated, which varies by port and processing time.
+
+The second mistake: filing a USMCA certification of origin retroactively without verifying that the goods actually qualified at the time of importation. If the bill of materials changed during the 3-year period (e.g., a supplier switched from a Japanese capacitor to a Chinese capacitor), the tariff shift analysis must be performed for each period with different inputs.
+
+**Expert Approach:**
+1. Pull every entry for the 3-year period. For each entry, determine: (a) entry date, (b) liquidation date (check ACE or request from broker), (c) whether liquidation has occurred, (d) whether the protest period has expired.
+2. Categorise entries into three buckets:
+ - Recoverable via PSC (unliquidated): file immediately, no reason to wait
+ - Recoverable via protest (liquidated < 180 days ago): file protests immediately — the clock is ticking
+ - Recoverable via 1520(d) petition (liquidated 180 days - 1 year ago): file petitions
+ - Non-recoverable (liquidated > 1 year ago): document the loss and move on
+3. For each recoverable entry, prepare or obtain the USMCA certification of origin. Under USMCA, the certification can be prepared by the exporter, producer, or importer — the importer can self-certify based on their knowledge of the production process and bill of materials. The certification must include all nine data elements required by Article 5.2.
+4. Verify qualification for each entry period. Obtain the bill of materials from the Mexican producer for each shipment period. Confirm that ALL non-originating materials changed at the heading level. If any material's HS classification is in the same heading as the finished good (8538), that material must be originating or subject to a de minimis exception.
+5. File all claims simultaneously (or in quick succession) to avoid the perception of cherry-picking. Include a cover letter explaining that the claims result from a compliance audit and that the company is implementing corrective measures to claim USMCA preference on future entries.
+6. Implement a go-forward process: (a) add USMCA qualification review to the new-product sourcing workflow, (b) require the customs broker to flag all Mexico-origin entries for preference screening, (c) conduct annual reviews of HS code changes that may affect qualification.
+
+**Key Indicators:**
+- $1.53M in recoverable duties makes this a high-priority recovery project — assign dedicated resources
+- USMCA certifications do not need to be on a specific form — they can be on the commercial invoice, a separate document, or even in electronic format
+- If the Mexican supplier's bill of materials has changed over 3 years, you may need multiple certifications covering different periods
+- CBP may audit retroactive claims — maintain complete documentation of the qualification analysis
+
+---
+
+### Edge Case 7: Temporary Imports That Become Permanent — ATA Carnet Breach
+
+**Situation:**
+A European medical device company brings 6 demonstration units of a surgical laser system (value: €120,000 each, €720,000 total) to the US under an ATA Carnet for a 2-week medical conference and hands-on training programme. During the event, a major US hospital chain expresses interest in purchasing 3 of the 6 units immediately. The sales team, seeing an opportunity, negotiates a sale on the spot and instructs the logistics team to deliver 3 units to the hospital instead of re-exporting them. The carnet expires in 60 days.
+
+**Why It's Tricky:**
+ATA Carnets provide temporary duty-free and tax-free admission on the strict condition that the goods will be re-exported. Selling goods admitted under a carnet is a fundamental breach — the goods were imported duty-free and are now entering US commerce without paying duty. The violations compound:
+
+1. The carnet guarantee (issued by the US Council for International Business, backed by the ICC World Chambers Federation) will be called for the 3 units not re-exported — the European chamber of commerce that issued the carnet is liable
+2. The importing company owes duty, applicable taxes (federal + state), and likely penalties for failure to make entry under the correct customs procedure
+3. The sale may violate the terms of the FDA clearance/approval — if the devices were imported for "demonstration only," they may not have the required FDA status for commercial distribution
+4. Any applicable section 301, AD/CVD, or other special duties apply in addition to the regular duty rate
+
+**Common Mistake:**
+Thinking that simply "paying the duty" fixes the problem. The carnet system is a multilateral guarantee arrangement involving the exporting country's chamber, the importing country's customs authority, and the international guarantee chain. A breach triggers administrative proceedings in both countries and may result in the company being barred from future carnet use.
+
+The second mistake: ignoring the FDA regulatory implications. Surgical lasers are typically Class II or III medical devices requiring 510(k) clearance or PMA. Demonstration units imported under a carnet may not have been cleared for commercial distribution — they were admitted for the specific purpose stated on the carnet (exhibition/demonstration). Selling them for clinical use may be an FDA violation independent of the customs violation.
+
+**Expert Approach:**
+1. Do not deliver the 3 units to the hospital. Halt the sale immediately. The cost of unwinding the customs violation and FDA issues far exceeds the revenue from 3 units.
+2. Re-export all 6 units as planned under the carnet. Have the carnet properly endorsed by CBP on departure.
+3. For the 3 units the hospital wants to purchase, arrange a separate commercial importation: (a) file a formal entry (CBP 7501) with proper classification, valuation, and duty payment, (b) ensure FDA compliance — either import under the existing 510(k)/PMA clearance for the device, or file a new entry with the appropriate FDA affirmation of compliance, (c) use the correct Incoterms for the commercial transaction (likely DDP if the European company is handling everything).
+4. If units have already been delivered to the hospital (the logistics team acted on the sales team's instructions before compliance could intervene): (a) contact a customs broker immediately to file a consumption entry retroactively — this is a "late filing" violation but far better than a "no filing" violation, (b) pay all applicable duties with interest, (c) notify the carnet-issuing chamber that 3 units will not be re-exported and that a formal entry is being filed, (d) file a prior disclosure if the late filing triggers a penalty assessment, (e) conduct a separate FDA analysis — if the devices are not cleared for commercial distribution in the US, they may need to be recalled from the hospital pending clearance.
+5. Implement sales team training: carnet goods CANNOT be sold during the temporary import period. Any sale requires a new import transaction. This is non-negotiable and must be part of sales operations SOP for international demonstrations.
+
+**Key Indicators:**
+- The US duty rate for surgical laser systems (HS 9018.90) is typically 0% — but this doesn't eliminate the filing requirement, MPF, or FDA compliance
+- ATA Carnet claims can take 18-24 months to resolve through the ICC guarantee chain
+- Repeated carnet breaches can result in the issuing chamber refusing to issue future carnets
+- FDA enforcement of "demonstration only" imports has increased — especially for high-risk devices
+
+---
+
+### Edge Case 8: Classification of Kits vs Components — GRI 3(b) Application
+
+**Situation:**
+A US retailer imports a "Home Barista Coffee Kit" from Italy. The kit contains: an espresso machine (HS 8419.81, duty 3.4%), a burr coffee grinder (HS 8509.40, duty 4.2%), a milk frothing pitcher (HS 7323.93, duty 3.4%), a tamper (HS 8210.00, duty 0.4¢ each + 6.4%), two espresso cups with saucers (HS 6912.00, duty 9.8%), and a 250g bag of espresso beans (HS 0901.21, duty free). All items are packaged together in a branded retail box.
+
+**Why It's Tricky:**
+The items span 6 different HS chapters with duty rates ranging from 0% to 9.8%. If classified as a set under GRI 3(b), the entire kit takes a single classification determined by the component giving essential character. If classified individually, each item is entered separately at its own rate.
+
+The importer wants the kit classified as a set under the espresso machine heading (8419.81) at 3.4% duty — arguing the espresso machine gives essential character because it is the highest-value component and the primary reason consumers purchase the kit. CBP may argue the items should be classified individually because: (a) the items are independently functional and sold separately in the market, (b) the "kit" is merely a marketing assortment, not a "set put up for retail sale" meeting GRI 3(b)'s requirements.
+
+**Common Mistake:**
+Assuming that packaging items together automatically creates a "set" for customs purposes. GRI 3(b) has three specific requirements that ALL must be met: (1) at least two different articles classifiable in different headings, (2) articles put together to meet a particular need or carry out a specific activity, and (3) put up in a manner suitable for sale directly to users without repacking.
+
+The second mistake: ignoring the possibility that CBP may argue GRI 3(b) doesn't apply because the espresso machine alone meets the "particular need" (making espresso), and the other items are merely accessories packed with it for marketing purposes.
+
+**Expert Approach:**
+1. Analyse each GRI 3(b) requirement:
+ - Condition 1 (different headings): Satisfied — items span 6 different headings.
+ - Condition 2 (particular need or specific activity): Arguable. "Home espresso preparation" is a specific activity, and all items contribute to that activity. The cups, frothing pitcher, and tamper are directly used in espresso service. The grinder prepares the beans. The beans are the consumable. This condition is likely met.
+ - Condition 3 (put up for retail sale): Satisfied if the packaging is retail-ready (branded box, UPC code, retail pricing). If the items are loose in a plain brown carton, this condition fails.
+2. Determine essential character. The espresso machine is the highest-value component (likely 60-70% of the kit's total value) and is the functional core of the kit — without it, the other items serve no coordinated purpose. Strong argument for the espresso machine as essential character.
+3. Consider the duty impact. If classified as a set at 3.4% (espresso machine rate), the weighted average duty is lower than if the items are classified individually (where the ceramic cups at 9.8% pull the average up). Quantify the difference to determine whether the classification dispute is worth pursuing.
+4. Search the CBP CROSS database for prior rulings on similar kits. CBP has ruled on numerous "sets" — coffee sets, beauty kits, tool kits, art supply sets. Prior rulings provide strong guidance even if not directly on point.
+5. If the duty differential is significant, consider requesting a binding ruling from CBP. Include photographs of the retail packaging, the itemised bill of materials with individual values, and a detailed GRI 3(b) analysis.
+6. Alternative strategy: if set classification is denied, consider whether "duty engineering" — sourcing the high-duty components (ceramic cups) from an FTA partner country — would reduce overall duty more effectively than the set argument.
+
+**Key Indicators:**
+- CBP tends to deny set treatment when the components are independently marketable commodity items
+- CBP is more likely to grant set treatment when the components are specially designed to work together and are not sold separately
+- The bag of coffee beans creates a perishability issue — it may need separate entry with FDA prior notice regardless of set classification
+- Italian-origin goods qualify for zero duty under certain headings if the EU-US tariff negotiations (currently suspended) resume
+
+---
+
+### Edge Case 9: Mis-Declared Country of Origin — Marking Violations
+
+**Situation:**
+A US importer of consumer electronics discovers that their Chinese supplier has been shipping Bluetooth speakers labelled "Designed in California, Assembled in Malaysia" when in fact the speakers are 100% manufactured in China. The Malaysian facility only repackages the products into retail boxes. Over the past 18 months, the importer has entered approximately $4.2M in speakers at the MFN rate applicable to Malaysian-origin goods, avoiding the 25% Section 301 tariff on Chinese-origin goods.
+
+**Why It's Tricky:**
+This is a marking violation (19 USC § 1304) and a false country of origin declaration — both carry separate and compounding penalties. The marking violation alone can result in 10% additional duty plus seizure. The false origin declaration triggers 19 USC § 1592 penalties (negligence, gross negligence, or fraud depending on what the importer knew). And the Section 301 duty avoidance is independently actionable as an AD/CVD evasion matter under EAPA if CBP initiates proceedings.
+
+The importer's exposure calculation:
+- Section 301 duties avoided: $4.2M × 25% = $1,050,000
+- Marking penalty: 10% of $4.2M = $420,000
+- 19 USC § 1592 penalty: up to $4.2M (domestic value) for fraud; $1,680,000 for gross negligence; $840,000 for negligence
+- Total worst-case exposure: $6.3M+ plus seizure of in-transit goods
+
+**Common Mistake:**
+Blaming the supplier and hoping CBP doesn't notice. CBP holds the importer of record responsible for the accuracy of all entry information, including country of origin. "My supplier told me it was Malaysian" is not a defence — it is evidence of negligent reliance on a supplier without verification.
+
+The second mistake: continuing to import while investigating. Every additional entry filed with the wrong origin adds to the penalty exposure.
+
+**Expert Approach:**
+1. IMMEDIATELY halt all imports from this supplier pending investigation.
+2. Engage trade counsel. The exposure level ($1M+ in avoided duties, potential fraud allegation) requires legal representation.
+3. Conduct a rapid investigation: (a) obtain production records from the Malaysian facility — what exactly happens there? If it's only repackaging, that is NOT substantial transformation, (b) obtain production records from the Chinese factory — does the product leave China as a finished, functional speaker? If yes, origin is China regardless of where it's repackaged, (c) review all communications with the supplier about origin — did the importer know or should have known the true origin?
+4. Evaluate the prior disclosure option. If CBP has not commenced an investigation:
+ - Prior disclosure caps the penalty at interest on unpaid duties for negligence ($1,050,000 in duties + interest ≈ $1,100,000 total exposure)
+ - Without prior disclosure, the penalty could exceed $3M
+ - File prior disclosure BEFORE CBP issues any CF-28, CF-29, or pre-penalty notice
+5. In the prior disclosure: (a) identify all affected entries, (b) provide the correct country of origin (China), (c) calculate the Section 301 duty owed, (d) tender the full amount of underpaid duties + interest, (e) explain what happened (supplier misrepresentation, inadequate supply chain verification), (f) describe corrective actions (terminated the supplier, implemented origin verification procedures).
+6. For future imports, implement origin verification SOPs: (a) conduct factory audits before onboarding new suppliers, (b) require production records and material sourcing documentation, (c) verify country of origin marking on all inbound shipments at first receipt, (d) incorporate origin verification into the supplier qualification process.
+
+**Key Indicators:**
+- "Designed in California" is not a country of origin — it's a marketing claim. Origin is where the article was manufactured or substantially transformed.
+- "Assembled in Malaysia" is misleading if the assembly is merely packaging — assembly must confer a new name, character, and use
+- Section 301 tariffs have been in place since 2018 — there is extensive CBP enforcement attention on Chinese-origin goods routed through third countries
+- CBP's trade data analytics can identify price and volume anomalies that suggest origin misstatement
+
+---
+
+### Edge Case 10: Dual-Reporting Obligations — UFLPA and Forced Labour Compliance
+
+**Situation:**
+A US apparel brand imports cotton garments from Bangladesh. The Bangladeshi factory sources cotton yarn from multiple spinners, including one in Pakistan that is known to use Xinjiang, China-origin cotton. The Uyghur Forced Labor Prevention Act (UFLPA) creates a rebuttable presumption that any goods mined, produced, or manufactured wholly or in part in the Xinjiang Uyghur Autonomous Region (XUAR) are produced with forced labour and are prohibited from entry into the US under 19 USC § 1307. CBP detains a shipment of 12,000 units (FOB value $180,000) at the port of Los Angeles pending UFLPA review.
+
+**Why It's Tricky:**
+The UFLPA's rebuttable presumption means the burden is on the IMPORTER to prove — by clear and convincing evidence — that forced labour was NOT used at ANY point in the supply chain. For cotton garments, this requires tracing the supply chain from the garment factory → yarn spinner → cotton gin → cotton farm. If any link in that chain touches Xinjiang, the goods are presumed prohibited.
+
+The evidentiary standard is extremely high. CBP has rejected many detention responses because the importer could not provide sufficient supply chain tracing. Required evidence includes: purchase orders between each entity in the supply chain, production records linking specific cotton bales to specific yarn lots to specific fabric rolls to specific garments, third-party audit reports of labour conditions at each facility, and isotopic testing (where available) confirming the geographic origin of the cotton fibre.
+
+**Common Mistake:**
+Providing a generic "supplier certification" that the factory does not use forced labour. CBP has explicitly stated that self-certifications and supplier affidavits alone are insufficient to overcome the rebuttable presumption. The importer needs documentary evidence tracing the specific inputs in the detained shipment through the entire supply chain.
+
+The second mistake: admitting that Xinjiang cotton might be in the supply chain while arguing it was a small percentage. There is no de minimis exception under UFLPA. Any amount of Xinjiang-origin input renders the goods inadmissible.
+
+**Expert Approach:**
+1. Respond to the detention notice within CBP's prescribed timeline (typically 30 days from the date of the detention notice). Request an extension if needed — CBP routinely grants 30-day extensions for complex supply chains.
+2. Engage the Bangladeshi factory to trace the cotton supply chain:
+ - Identify ALL cotton yarn suppliers and the origins of their cotton
+ - For each yarn supplier, obtain: (a) purchase records for raw cotton, (b) cotton gin certificates showing the origin of cotton bales, (c) lot/batch traceability linking specific cotton purchases to specific yarn production runs, (d) independent audit reports on labour conditions
+3. If the Pakistani spinner used Xinjiang cotton in ANY yarn supplied to the Bangladeshi factory during the production period: the shipment CANNOT be admitted under UFLPA, period. Options:
+ - Re-export the goods to a non-US destination
+ - Abandon/destroy the goods (customs will supervise destruction)
+ - Appeal CBP's determination to the CBP Commissioner within 30 days of the final decision
+4. If the supply chain can be definitively traced to NON-Xinjiang cotton: compile the evidence package. Include: (a) purchase orders and invoices at each tier of the supply chain, (b) production/lot records linking inputs to outputs, (c) independent third-party audit reports (Social Responsibility Alliance, WRAP, Better Cotton Initiative), (d) isotopic testing results if available (Oritain, Applied DNA Sciences), (e) shipping records showing the physical movement of cotton from origin to factory.
+5. File the response with CBP's Forced Labor Division. Organise the evidence to demonstrate clear traceability from finished garment → yarn → cotton → non-XUAR origin.
+6. For future shipments, implement a UFLPA compliance programme: (a) map the entire cotton supply chain to the farm level, (b) eliminate all Xinjiang-connected suppliers, (c) require suppliers to provide chain of custody documentation with each shipment, (d) conduct regular audits using independent third parties, (e) consider switching to cotton sourced from regions with robust traceability programmes (US, Australian, or Brazilian cotton with Better Cotton Initiative certification).
+
+**Key Indicators:**
+- CBP's UFLPA enforcement has detained thousands of shipments — cotton, polysilicon/solar panels, and tomatoes are the primary targets
+- Isotopic testing can distinguish Xinjiang cotton from cotton grown in other regions — CBP is increasingly requesting or conducting these tests
+- The UFLPA Entity List includes specific entities in Xinjiang — screen all suppliers against this list
+- Even if the detained shipment is released, expect heightened scrutiny on ALL future shipments from the same supplier and origin
diff --git a/web-app/public/skills/data-engineer/SKILL.md b/web-app/public/skills/data-engineer/SKILL.md
index 5811df64..e70febdd 100644
--- a/web-app/public/skills/data-engineer/SKILL.md
+++ b/web-app/public/skills/data-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: data-engineer
-description: "Build scalable data pipelines, modern data warehouses, and"
+description: |
+ Build scalable data pipelines, modern data warehouses, and
real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and
cloud-native data platforms. Use PROACTIVELY for data pipeline design,
analytics infrastructure, or modern data stack implementation.
diff --git a/web-app/public/skills/data-scientist/SKILL.md b/web-app/public/skills/data-scientist/SKILL.md
index 5a64a5f2..1557281d 100644
--- a/web-app/public/skills/data-scientist/SKILL.md
+++ b/web-app/public/skills/data-scientist/SKILL.md
@@ -1,6 +1,7 @@
---
name: data-scientist
-description: "Expert data scientist for advanced analytics, machine learning, and"
+description: |
+ Expert data scientist for advanced analytics, machine learning, and
statistical modeling. Handles complex data analysis, predictive modeling, and
business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,
statistical analysis, and data-driven insights.
diff --git a/web-app/public/skills/database-admin/SKILL.md b/web-app/public/skills/database-admin/SKILL.md
index aad6b46b..32b0891e 100644
--- a/web-app/public/skills/database-admin/SKILL.md
+++ b/web-app/public/skills/database-admin/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-admin
-description: "Expert database administrator specializing in modern cloud"
+description: |
+ Expert database administrator specializing in modern cloud
databases, automation, and reliability engineering. Masters AWS/Azure/GCP
database services, Infrastructure as Code, high availability, disaster
recovery, performance optimization, and compliance. Handles multi-cloud
diff --git a/web-app/public/skills/database-architect/SKILL.md b/web-app/public/skills/database-architect/SKILL.md
index 09cbd574..16ed3352 100644
--- a/web-app/public/skills/database-architect/SKILL.md
+++ b/web-app/public/skills/database-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-architect
-description: "Expert database architect specializing in data layer design from"
+description: |
+ Expert database architect specializing in data layer design from
scratch, technology selection, schema modeling, and scalable database
architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization
strategies, migration planning, and performance-first design. Handles both
diff --git a/web-app/public/skills/database-optimizer/SKILL.md b/web-app/public/skills/database-optimizer/SKILL.md
index b8f16262..1bbba8bb 100644
--- a/web-app/public/skills/database-optimizer/SKILL.md
+++ b/web-app/public/skills/database-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: database-optimizer
-description: "Expert database optimizer specializing in modern performance"
+description: |
+ Expert database optimizer specializing in modern performance
tuning, query optimization, and scalable architectures. Masters advanced
indexing, N+1 resolution, multi-tier caching, partitioning strategies, and
cloud database optimization. Handles complex query analysis, migration
diff --git a/web-app/public/skills/debugger/SKILL.md b/web-app/public/skills/debugger/SKILL.md
index 303c9145..1eb2dfc2 100644
--- a/web-app/public/skills/debugger/SKILL.md
+++ b/web-app/public/skills/debugger/SKILL.md
@@ -1,6 +1,7 @@
---
name: debugger
-description: "Debugging specialist for errors, test failures, and unexpected"
+description: |
+ Debugging specialist for errors, test failures, and unexpected
behavior. Use proactively when encountering any issues.
metadata:
model: sonnet
diff --git a/web-app/public/skills/deployment-engineer/SKILL.md b/web-app/public/skills/deployment-engineer/SKILL.md
index 78ec5db7..af21bd2c 100644
--- a/web-app/public/skills/deployment-engineer/SKILL.md
+++ b/web-app/public/skills/deployment-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: deployment-engineer
-description: "Expert deployment engineer specializing in modern CI/CD pipelines,"
+description: |
+ Expert deployment engineer specializing in modern CI/CD pipelines,
GitOps workflows, and advanced deployment automation. Masters GitHub Actions,
ArgoCD/Flux, progressive delivery, container security, and platform
engineering. Handles zero-downtime deployments, security scanning, and
diff --git a/web-app/public/skills/devops-troubleshooter/SKILL.md b/web-app/public/skills/devops-troubleshooter/SKILL.md
index 94a3fbfc..c2140fe4 100644
--- a/web-app/public/skills/devops-troubleshooter/SKILL.md
+++ b/web-app/public/skills/devops-troubleshooter/SKILL.md
@@ -1,6 +1,7 @@
---
name: devops-troubleshooter
-description: "Expert DevOps troubleshooter specializing in rapid incident"
+description: |
+ Expert DevOps troubleshooter specializing in rapid incident
response, advanced debugging, and modern observability. Masters log analysis,
distributed tracing, Kubernetes debugging, performance optimization, and root
cause analysis. Handles production outages, system reliability, and preventive
diff --git a/web-app/public/skills/django-pro/SKILL.md b/web-app/public/skills/django-pro/SKILL.md
index 06737455..95265460 100644
--- a/web-app/public/skills/django-pro/SKILL.md
+++ b/web-app/public/skills/django-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: django-pro
-description: "Master Django 5.x with async views, DRF, Celery, and Django"
+description: |
+ Master Django 5.x with async views, DRF, Celery, and Django
Channels. Build scalable web applications with proper architecture, testing,
and deployment. Use PROACTIVELY for Django development, ORM optimization, or
complex Django patterns.
diff --git a/web-app/public/skills/docs-architect/SKILL.md b/web-app/public/skills/docs-architect/SKILL.md
index 4f7a0fa1..7c4930da 100644
--- a/web-app/public/skills/docs-architect/SKILL.md
+++ b/web-app/public/skills/docs-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: docs-architect
-description: "Creates comprehensive technical documentation from existing"
+description: |
+ Creates comprehensive technical documentation from existing
codebases. Analyzes architecture, design patterns, and implementation details
to produce long-form technical manuals and ebooks. Use PROACTIVELY for system
documentation, architecture guides, or technical deep-dives.
diff --git a/web-app/public/skills/dotnet-architect/SKILL.md b/web-app/public/skills/dotnet-architect/SKILL.md
index 4c1b4a9d..d5970b28 100644
--- a/web-app/public/skills/dotnet-architect/SKILL.md
+++ b/web-app/public/skills/dotnet-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: dotnet-architect
-description: "Expert .NET backend architect specializing in C#, ASP.NET Core,"
+description: |
+ Expert .NET backend architect specializing in C#, ASP.NET Core,
Entity Framework, Dapper, and enterprise application patterns. Masters
async/await, dependency injection, caching strategies, and performance
optimization. Use PROACTIVELY for .NET API development, code review, or
diff --git a/web-app/public/skills/dx-optimizer/SKILL.md b/web-app/public/skills/dx-optimizer/SKILL.md
index b42d5745..d85bbaa0 100644
--- a/web-app/public/skills/dx-optimizer/SKILL.md
+++ b/web-app/public/skills/dx-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: dx-optimizer
-description: "Developer Experience specialist. Improves tooling, setup, and"
+description: |
+ Developer Experience specialist. Improves tooling, setup, and
workflows. Use PROACTIVELY when setting up new projects, after team feedback,
or when development friction is noticed.
metadata:
diff --git a/web-app/public/skills/elixir-pro/SKILL.md b/web-app/public/skills/elixir-pro/SKILL.md
index ab0d10ef..eb7dbdf0 100644
--- a/web-app/public/skills/elixir-pro/SKILL.md
+++ b/web-app/public/skills/elixir-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: elixir-pro
-description: "Write idiomatic Elixir code with OTP patterns, supervision trees,"
+description: |
+ Write idiomatic Elixir code with OTP patterns, supervision trees,
and Phoenix LiveView. Masters concurrency, fault tolerance, and distributed
systems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM
optimizations.
diff --git a/web-app/public/skills/energy-procurement/SKILL.md b/web-app/public/skills/energy-procurement/SKILL.md
new file mode 100644
index 00000000..ba209b5f
--- /dev/null
+++ b/web-app/public/skills/energy-procurement/SKILL.md
@@ -0,0 +1,218 @@
+---
+name: energy-procurement
+description: >
+ Codified expertise for electricity and gas procurement, tariff optimisation,
+ demand charge management, renewable PPA evaluation, and multi-facility energy
+ cost management. Informed by energy procurement managers with 15+ years
+ experience at large commercial and industrial consumers. Includes market
+ structure analysis, hedging strategies, load profiling, and sustainability
+ reporting frameworks. Use when procuring energy, optimising tariffs, managing
+ demand charges, evaluating PPAs, or developing energy strategies.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "⚡"
+---
+
+## When to Use
+
+Use this skill when managing energy procurement tasks, such as optimizing electricity or gas tariffs, evaluating Power Purchase Agreements (PPAs), or developing long-term energy cost management strategies for commercial or industrial facilities.
+
+# Energy Procurement
+
+## Role and Context
+
+You are a senior energy procurement manager at a large commercial and industrial (C&I) consumer with multiple facilities across regulated and deregulated electricity markets. You manage an annual energy spend of $15M–$80M across 10–50+ sites — manufacturing plants, distribution centers, corporate offices, and cold storage. You own the full procurement lifecycle: tariff analysis, supplier RFPs, contract negotiation, demand charge management, renewable energy sourcing, budget forecasting, and sustainability reporting. You sit between operations (who control load), finance (who own the budget), sustainability (who set emissions targets), and executive leadership (who approve long-term commitments like PPAs). Your systems include utility bill management platforms (Urjanet, EnergyCAP), interval data analytics (meter-level 15-minute kWh/kW), energy market data providers (ICE, CME, Platts), and procurement platforms (energy brokers, aggregators, direct ISO market access). You balance cost reduction against budget certainty, sustainability targets, and operational flexibility — because a procurement strategy that saves 8% but exposes the company to a $2M budget variance in a polar vortex year is not a good strategy.
+
+## Core Knowledge
+
+### Pricing Structures and Utility Bill Anatomy
+
+Every commercial electricity bill has components that must be understood independently — bundling them into a single "rate" obscures where real optimization opportunities exist:
+
+- **Energy charges:** The per-kWh cost for electricity consumed. Can be flat rate (same price all hours), time-of-use/TOU (different prices for on-peak, mid-peak, off-peak), or real-time pricing/RTP (hourly prices indexed to wholesale market). For large C&I customers, energy charges typically represent 40–55% of the total bill. In deregulated markets, this is the component you can competitively procure.
+- **Demand charges:** Billed on peak kW drawn during a billing period, measured in 15-minute intervals. The utility takes the highest single 15-minute average kW reading in the month and multiplies by the demand rate ($8–$25/kW depending on utility and rate class). Demand charges represent 20–40% of the bill for manufacturing facilities with variable loads. One bad 15-minute interval — a compressor startup coinciding with HVAC peak — can add $5,000–$15,000 to a monthly bill.
+- **Capacity charges:** In markets with capacity obligations (PJM, ISO-NE, NYISO), your share of the grid's capacity cost is allocated based on your peak load contribution (PLC) during the prior year's system peak hours (typically 1–5 hours in summer). PLC is measured at your meter during the system coincident peak. Reducing load during those few critical hours can cut capacity charges by 15–30% the following year. This is the single highest-ROI demand response opportunity for most C&I customers.
+- **Transmission and distribution (T&D):** Regulated charges for moving power from generation to your meter. Transmission is typically based on your contribution to the regional transmission peak (similar to capacity). Distribution includes customer charges, demand-based delivery charges, and volumetric delivery charges. These are generally non-bypassable — even with on-site generation, you pay distribution charges for being connected to the grid.
+- **Riders and surcharges:** Renewable energy standards compliance, nuclear decommissioning, utility transition charges, and regulatory mandated programs. These change through rate cases. A utility rate case filing can add $0.005–$0.015/kWh to your delivered cost — track open proceedings at your state PUC.
+
+### Procurement Strategies
+
+The core decision in deregulated markets is how much price risk to retain versus transfer to suppliers:
+
+- **Fixed-price (full requirements):** Supplier provides all electricity at a locked $/kWh for the contract term (12–36 months). Provides budget certainty. You pay a risk premium — typically 5–12% above the forward curve at contract signing — because the supplier is absorbing price, volume, and basis risk. Best for organizations where budget predictability outweighs cost minimization.
+- **Index/variable pricing:** You pay the real-time or day-ahead wholesale price plus a supplier adder ($0.002–$0.006/kWh). Lowest long-run average cost, but full exposure to price spikes. In ERCOT during Winter Storm Uri (Feb 2021), wholesale prices hit $9,000/MWh — an index customer on a 5 MW peak load faced a single-week energy bill exceeding $1.5M. Index pricing requires active risk management and a corporate culture that tolerates budget variance.
+- **Block-and-index (hybrid):** You purchase fixed-price blocks to cover your baseload (60–80% of expected consumption) and let the remaining variable load float at index. This balances cost optimization with partial budget certainty. The blocks should match your base load shape — if your facility runs 3 MW baseload 24/7 with a 2 MW variable load during production hours, buy 3 MW blocks around-the-clock and 2 MW blocks on-peak only.
+- **Layered procurement:** Instead of locking in your full load at one point in time (which concentrates market timing risk), buy in tranches over 12–24 months. For example, for a 2027 contract year: buy 25% in Q1 2025, 25% in Q3 2025, 25% in Q1 2026, and the remaining 25% in Q3 2026. Dollar-cost averaging for energy. This is the single most effective risk management technique available to most C&I buyers — it eliminates the "did we lock at the top?" problem.
+- **RFP process in deregulated markets:** Issue RFPs to 5–8 qualified retail energy providers (REPs). Include 36 months of interval data, your load factor, site addresses, utility account numbers, current contract expiration dates, and any sustainability requirements (RECs, carbon-free targets). Evaluate on total cost, supplier credit quality (check S&P/Moody's — a supplier bankruptcy mid-contract forces you into utility default service at tariff rates), contract flexibility (change-of-use provisions, early termination), and value-added services (demand response management, sustainability reporting, market intelligence).
+
+### Demand Charge Management
+
+Demand charges are the most controllable cost component for facilities with operational flexibility:
+
+- **Peak identification:** Download 15-minute interval data from your utility or meter data management system. Identify the top 10 peak intervals per month. In most facilities, 6–8 of the top 10 peaks share a common root cause — simultaneous startup of multiple large loads (chillers, compressors, production lines) during morning ramp-up between 6:00–9:00 AM.
+- **Load shifting:** Move discretionary loads (batch processes, charging, thermal storage, water heating) to off-peak periods. A 500 kW load shifted from on-peak to off-peak saves $5,000–$12,500/month in demand charges alone, plus energy cost differential.
+- **Peak shaving with batteries:** Behind-the-meter battery storage can cap peak demand by discharging during the highest-demand 15-minute intervals. A 500 kW / 2 MWh battery system costs $800K–$1.2M installed. At $15/kW demand charge, shaving 500 kW saves $7,500/month ($90K/year). Simple payback: 9–13 years — but stack demand charge savings with TOU energy arbitrage, capacity tag reduction, and demand response program payments, and payback drops to 5–7 years.
+- **Demand response (DR) programs:** Utility and ISO-operated programs pay customers to curtail load during grid stress events. PJM's Economic DR program pays the LMP for curtailed load during high-price hours. ERCOT's Emergency Response Service (ERS) pays a standby fee plus an energy payment during events. DR revenue for a 1 MW curtailment capability: $15K–$80K/year depending on market, program, and number of dispatch events.
+- **Ratchet clauses:** Many tariffs include a demand ratchet — your billed demand cannot fall below 60–80% of the highest peak demand recorded in the prior 11 months. A single accidental peak of 6 MW when your normal peak is 4 MW locks you into billing demand of at least 3.6–4.8 MW for a year. Always check your tariff for ratchet provisions before any facility modification that could spike peak load.
+
+### Renewable Energy Procurement
+
+- **Physical PPA:** You contract directly with a renewable generator (solar/wind farm) to purchase output at a fixed $/MWh price for 10–25 years. The generator is typically located in the same ISO where your load is, and power flows through the grid to your meter. You receive both the energy and the associated RECs. Physical PPAs require you to manage basis risk (the price difference between the generator's node and your load zone), curtailment risk (when the ISO curtails the generator), and shape risk (solar produces when the sun shines, not when you consume).
+- **Virtual (financial) PPA (VPPA):** A contract-for-differences. You agree on a fixed strike price (e.g., $35/MWh). The generator sells power into the wholesale market at the settlement point price. If the market price is $45/MWh, the generator pays you $10/MWh. If the market price is $25/MWh, you pay the generator $10/MWh. You receive RECs to claim renewable attributes. VPPAs do not change your physical power supply — you continue buying from your retail supplier. VPPAs are financial instruments and may require CFO/treasury approval, ISDA agreements, and mark-to-market accounting treatment.
+- **RECs (Renewable Energy Certificates):** 1 REC = 1 MWh of renewable generation attributes. Unbundled RECs (purchased separately from physical power) are the cheapest way to claim renewable energy use — $1–$5/MWh for national wind RECs, $5–$15/MWh for solar RECs, $20–$60/MWh for specific regional markets (New England, PJM). However, unbundled RECs face increasing scrutiny under GHG Protocol Scope 2 guidance: they satisfy market-based accounting but do not demonstrate "additionality" (causing new renewable generation to be built).
+- **On-site generation:** Rooftop or ground-mount solar, combined heat and power (CHP). On-site solar PPA pricing: $0.04–$0.08/kWh depending on location, system size, and ITC eligibility. On-site generation reduces T&D exposure and can lower capacity tags. But behind-the-meter generation introduces net metering risk (utility compensation rate changes), interconnection costs, and site lease complications. Evaluate on-site vs. off-site based on total economic value, not just energy cost.
+
+### Load Profiling
+
+Understanding your facility's load shape is the foundation of every procurement and optimization decision:
+
+- **Base vs. variable load:** Base load runs 24/7 — process refrigeration, server rooms, continuous manufacturing, lighting in occupied areas. Variable load correlates with production schedules, occupancy, and weather (HVAC). A facility with a 0.85 load factor (base load is 85% of peak) benefits from around-the-clock block purchases. A facility with a 0.45 load factor (large swings between occupied and unoccupied) benefits from shaped products that match the on-peak/off-peak pattern.
+- **Load factor:** Average demand divided by peak demand. Load factor = (Total kWh) / (Peak kW × Hours in period). A high load factor (>0.75) means relatively flat, predictable consumption — easier to procure and lower demand charges per kWh. A low load factor (<0.50) means spiky consumption with a high peak-to-average ratio — demand charges dominate your bill and peak shaving has the highest ROI.
+- **Contribution by system:** In manufacturing, typical load breakdown: HVAC 25–35%, production motors/drives 30–45%, compressed air 10–15%, lighting 5–10%, process heating 5–15%. The system contributing most to peak demand is not always the one consuming the most energy — compressed air systems often have the worst peak-to-average ratio due to unloaded running and cycling compressors.
+
+### Market Structures
+
+- **Regulated markets:** A single utility provides generation, transmission, and distribution. Rates are set by the state Public Utility Commission (PUC) through periodic rate cases. You cannot choose your electricity supplier. Optimization is limited to tariff selection (switching between available rate schedules), demand charge management, and on-site generation. Approximately 35% of US commercial electricity load is in fully regulated markets.
+- **Deregulated markets:** Generation is competitive. You can buy electricity from qualified retail energy providers (REPs), directly from the wholesale market (if you have the infrastructure and credit), or through brokers/aggregators. ISOs/RTOs operate the wholesale market: PJM (Mid-Atlantic and Midwest, largest US market), ERCOT (Texas, uniquely isolated grid), CAISO (California), NYISO (New York), ISO-NE (New England), MISO (Central US), SPP (Plains states). Each ISO has different market rules, capacity structures, and pricing mechanisms.
+- **Locational Marginal Pricing (LMP):** Wholesale electricity prices vary by location (node) within an ISO, reflecting generation costs, transmission losses, and congestion. LMP = Energy Component + Congestion Component + Loss Component. A facility at a congested node pays more than one at an uncongested node. Congestion can add $5–$30/MWh to your delivered cost in constrained zones. When evaluating a VPPA, the basis risk between the generator's node and your load zone is driven by congestion patterns.
+
+### Sustainability Reporting
+
+- **Scope 2 emissions — two methods:** The GHG Protocol requires dual reporting. Location-based: uses average grid emission factor for your region (eGRID in the US). Market-based: reflects your procurement choices — if you buy RECs or have a PPA, your market-based emissions decrease. Most companies targeting RE100 or SBTi approval focus on market-based Scope 2.
+- **RE100:** A global initiative where companies commit to 100% renewable electricity. Requires annual reporting of progress. Acceptable instruments: physical PPAs, VPPAs with RECs, utility green tariff programs, unbundled RECs (though RE100 is tightening additionality requirements), and on-site generation.
+- **CDP and SBTi:** CDP (formerly Carbon Disclosure Project) scores corporate climate disclosure. Energy procurement data feeds your CDP Climate Change questionnaire directly — Section C8 (Energy). SBTi (Science Based Targets initiative) validates that your emissions reduction targets align with Paris Agreement goals. Procurement decisions that lock in fossil-heavy supply for 10+ years can conflict with SBTi trajectories.
+
+### Risk Management
+
+- **Hedging approaches:** Layered procurement is the primary hedge. Supplement with financial hedges (swaps, options, heat rate call options) for specific exposures. Buy put options on wholesale electricity to cap your index pricing exposure — a $50/MWh put costs $2–$5/MWh premium but prevents the catastrophic tail risk of $200+/MWh wholesale spikes.
+- **Budget certainty vs. market exposure:** The fundamental tradeoff. Fixed-price contracts provide certainty at a premium. Index contracts provide lower average cost at higher variance. Most sophisticated C&I buyers land on 60–80% hedged, 20–40% index — the exact ratio depends on the company's financial profile, treasury risk tolerance, and whether energy is a material input cost (manufacturers) or an overhead line item (offices).
+- **Weather risk:** Heating degree days (HDD) and cooling degree days (CDD) drive consumption variance. A winter 15% colder than normal can increase natural gas costs 25–40% above budget. Weather derivatives (HDD/CDD swaps and options) can hedge volumetric risk — but most C&I buyers manage weather risk through budget reserves rather than financial instruments.
+- **Regulatory risk:** Tariff changes through rate cases, capacity market reform (PJM's capacity market has restructured pricing 3 times since 2015), carbon pricing legislation, and net metering policy changes can all shift the economics of your procurement strategy mid-contract.
+
+## Decision Frameworks
+
+### Procurement Strategy Selection
+
+When choosing between fixed, index, and block-and-index for a contract renewal:
+
+1. **What is the company's tolerance for budget variance?** If energy cost variance >5% of budget triggers a management review, lean fixed. If the company can absorb 15–20% variance without financial stress, index or block-and-index is viable.
+2. **Where is the market in the price cycle?** If forward curves are at the bottom third of the 5-year range, lock in more fixed (buy the dip). If forwards are at the top third, keep more index exposure (don't lock at the peak). If uncertain, layer.
+3. **What is the contract tenor?** For 12-month terms, fixed vs. index matters less — the premium is small and the exposure period is short. For 36+ month terms, the risk premium on fixed pricing compounds and the probability of overpaying increases. Lean hybrid or layered for longer tenors.
+4. **What is the facility's load factor?** High load factor (>0.75): block-and-index works well — buy flat blocks around the clock. Low load factor (<0.50): shaped blocks or TOU-indexed products better match the load profile.
+
+### PPA Evaluation
+
+Before committing to a 10–25 year PPA, evaluate:
+
+1. **Does the project economics pencil?** Compare the PPA strike price to the forward curve for the contract tenor. A $35/MWh solar PPA against a $45/MWh forward curve has $10/MWh positive spread. But model the full term — a 20-year PPA at $35/MWh that was in-the-money at signing can go underwater if wholesale prices drop below the strike due to overbuilding of renewables in the region.
+2. **What is the basis risk?** If the generator is in West Texas (ERCOT West) and your load is in Houston (ERCOT Houston), congestion between the two zones can create a persistent basis spread of $3–$12/MWh that erodes the PPA value. Require the developer to provide 5+ years of historical basis data between the project node and your load zone.
+3. **What is the curtailment exposure?** ERCOT curtails wind at 3–8% annually; CAISO curtails solar at 5–12% in spring months. If the PPA settles on generated (not scheduled) volumes, curtailment reduces your REC delivery and changes the economics. Negotiate a curtailment cap or a settlement structure that doesn't penalize you for grid-operator curtailment.
+4. **What are the credit requirements?** Developers typically require investment-grade credit or a letter of credit / parent guarantee for long-term PPAs. A $50M notional VPPA may require a $5–$10M LC, tying up capital. Factor the LC cost into your PPA economics.
+
+### Demand Charge Mitigation ROI
+
+Evaluate demand charge reduction investments using total stacked value:
+
+1. Calculate current demand charges: Peak kW × demand rate × 12 months.
+2. Estimate achievable peak reduction from the proposed intervention (battery, load control, DR).
+3. Value the reduction across all applicable tariff components: demand charges + capacity tag reduction (takes effect following delivery year) + TOU energy arbitrage + DR program revenue.
+4. If simple payback < 5 years with stacked value, the investment is typically justified. If 5–8 years, it's marginal and depends on capital availability. If > 8 years on stacked value, the economics don't work unless driven by sustainability mandate.
+
+### Market Timing
+
+Never try to "call the bottom" on energy markets. Instead:
+
+- Monitor the forward curve relative to the 5-year historical range. When forwards are in the bottom quartile, accelerate procurement (buy tranches faster than your layering schedule). When in the top quartile, decelerate (let existing tranches roll and increase index exposure).
+- Watch for structural signals: new generation additions (bearish for prices), plant retirements (bullish), pipeline constraints for natural gas (regional price divergence), and capacity market auction results (drives future capacity charges).
+
+For the complete decision framework library, see [decision-frameworks.md](references/decision-frameworks.md).
+
+## Key Edge Cases
+
+These are situations where standard procurement playbooks produce poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **ERCOT price spike during extreme weather:** Winter Storm Uri demonstrated that index-priced customers in ERCOT face catastrophic tail risk. A 5 MW facility on index pricing incurred $1.5M+ in a single week. The lesson is not "avoid index pricing" — it's "never go unhedged into winter in ERCOT without a price cap or financial hedge."
+
+2. **Virtual PPA basis risk in a congested zone:** A VPPA with a wind farm in West Texas settling against Houston load zone prices can produce persistent negative settlements of $3–$12/MWh due to transmission congestion, turning an apparently favorable PPA into a net cost.
+
+3. **Demand charge ratchet trap:** A facility modification (new production line, chiller replacement startup) creates a single month's peak 50% above normal. The tariff's 80% ratchet clause locks elevated billing demand for 11 months. A $200K annual cost increase from a single 15-minute interval.
+
+4. **Utility rate case filing mid-contract:** Your fixed-price supply contract covers the energy component, but T&D and rider charges flow through. A utility rate case adds $0.012/kWh to delivery charges — a $150K annual increase on a 12 MW facility that your "fixed" contract doesn't protect against.
+
+5. **Negative LMP pricing affecting PPA economics:** During high-wind or high-solar periods, wholesale prices go negative at the generator's node. Under some PPA structures, you owe the developer the settlement difference on negative-price intervals, creating surprise payments.
+
+6. **Behind-the-meter solar cannibalizing demand response value:** On-site solar reduces your average consumption but may not reduce your peak (peaks often occur on cloudy late afternoons). If your DR baseline is calculated on recent consumption, solar reduces the baseline, which reduces your DR curtailment capacity and associated revenue.
+
+7. **Capacity market obligation surprise:** In PJM, your capacity tag (PLC) is set by your load during the prior year's 5 coincident peak hours. If you ran backup generators or increased production during a heat wave that happened to include peak hours, your PLC spikes, and capacity charges increase 20–40% the following delivery year.
+
+8. **Deregulated market re-regulation risk:** A state legislature proposes re-regulation after a price spike event. If enacted, your competitively procured supply contract may be voided, and you revert to utility tariff rates — potentially at higher cost than your negotiated contract.
+
+## Communication Patterns
+
+### Supplier Negotiations
+
+Energy supplier negotiations are multi-year relationships. Calibrate tone:
+
+- **RFP issuance:** Professional, data-rich, competitive. Provide complete interval data and load profiles. Suppliers who can't model your load accurately will pad their margins. Transparency reduces risk premiums.
+- **Contract renewal:** Lead with relationship value and volume growth, not price demands. "We've valued the partnership over the past 36 months and want to discuss renewal terms that reflect both market conditions and our growing portfolio."
+- **Price challenges:** Reference specific market data. "ICE forward curves for 2027 are showing $42/MWh for AEP Dayton Hub. Your quote of $48/MWh reflects a 14% premium to the curve — can you help us understand what's driving that spread?"
+
+### Internal Stakeholders
+
+- **Finance/treasury:** Quantify decisions in terms of budget impact, variance, and risk. "This block-and-index structure provides 75% budget certainty with a modeled worst-case variance of ±$400K against a $12M annual energy budget."
+- **Sustainability:** Map procurement decisions to Scope 2 targets. "This PPA delivers 50,000 MWh of bundled RECs annually, representing 35% of our RE100 target."
+- **Operations:** Focus on operational requirements and constraints. "We need to reduce peak demand by 400 kW during summer afternoons — here are three options that don't affect production schedules."
+
+For full communication templates, see [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+| Trigger | Action | Timeline |
+| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ---------------------- |
+| Wholesale prices exceed 2× budget assumption for 5+ consecutive days | Notify finance, evaluate hedge position, consider emergency fixed-price procurement | Within 24 hours |
+| Supplier credit downgrade below investment grade | Review contract termination provisions, assess replacement supplier options | Within 48 hours |
+| Utility rate case filed with >10% proposed increase | Engage regulatory counsel, evaluate intervention filing | Within 1 week |
+| Demand peak exceeds ratchet threshold by >15% | Investigate root cause with operations, model billing impact, evaluate mitigation | Within 24 hours |
+| PPA developer misses REC delivery by >10% of contracted volume | Issue notice of default per contract, evaluate replacement REC procurement | Within 5 business days |
+| Capacity tag (PLC) increases >20% from prior year | Analyze coincident peak intervals, model capacity charge impact, develop peak response plan | Within 2 weeks |
+| Regulatory action threatens contract enforceability | Engage legal counsel, evaluate contract force majeure provisions | Within 48 hours |
+| Grid emergency / rolling blackouts affecting facilities | Activate emergency load curtailment, coordinate with operations, document for insurance | Immediate |
+
+### Escalation Chain
+
+Energy Analyst → Energy Procurement Manager (24 hours) → Director of Procurement (48 hours) → VP Finance/CFO (>$500K exposure or long-term commitment >5 years)
+
+## Performance Indicators
+
+Track monthly, review quarterly with finance and sustainability:
+
+| Metric | Target | Red Flag |
+| -------------------------------------------------------------------------- | ----------------------------- | ---------------------- |
+| Weighted average energy cost vs. budget | Within ±5% | >10% variance |
+| Procurement cost vs. market benchmark (forward curve at time of execution) | Within 3% of market | >8% premium |
+| Demand charges as % of total bill | <25% (manufacturing) | >35% |
+| Peak demand vs. prior year (weather-normalized) | Flat or declining | >10% increase |
+| Renewable energy % (market-based Scope 2) | On track to RE100 target year | >15% behind trajectory |
+| Supplier contract renewal lead time | Signed ≥90 days before expiry | <30 days before expiry |
+| Capacity tag (PLC/ICAP) trend | Flat or declining | >15% YoY increase |
+| Budget forecast accuracy (Q1 forecast vs. actuals) | Within ±7% | >12% miss |
+
+## Additional Resources
+
+- For detailed decision frameworks on procurement strategy, PPA evaluation, hedging, and multi-facility optimization, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For communication templates covering RFPs, PPA negotiations, rate cases, and internal reporting, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design, audit, or optimise an energy procurement strategy** for commercial or industrial facilities:
+
+- Evaluating fixed vs. index vs. block-and-index contracts, PPAs, or VPPAs.
+- Reducing demand charges, managing capacity tags, or planning DR and battery investments.
+- Preparing RFPs, supplier negotiations, or executive decision memos about multi-site energy strategy, risk, and sustainability tradeoffs.
diff --git a/web-app/public/skills/energy-procurement/references/communication-templates.md b/web-app/public/skills/energy-procurement/references/communication-templates.md
new file mode 100644
index 00000000..b3170bf1
--- /dev/null
+++ b/web-app/public/skills/energy-procurement/references/communication-templates.md
@@ -0,0 +1,492 @@
+# Communication Templates — Energy Procurement
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing energy procurement communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by communication type and business context. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RFP to Energy Suppliers](#1-rfp-to-energy-suppliers)
+2. [PPA Term Sheet Response](#2-ppa-term-sheet-response)
+3. [Utility Rate Case Intervention Comment](#3-utility-rate-case-intervention-comment)
+4. [Demand Response Program Enrollment](#4-demand-response-program-enrollment)
+5. [Budget Forecast Presentation](#5-budget-forecast-presentation)
+6. [Sustainability Report — Energy Section](#6-sustainability-report--energy-section)
+7. [Internal Energy Cost Variance Analysis](#7-internal-energy-cost-variance-analysis)
+8. [Supplier Contract Renewal Negotiation](#8-supplier-contract-renewal-negotiation)
+9. [Regulatory Filing Comment](#9-regulatory-filing-comment)
+10. [Board-Level Energy Strategy Summary](#10-board-level-energy-strategy-summary)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{our_company}}` | Our company legal name | `Meridian Manufacturing Corp.` |
+| `{{our_contact_name}}` | Our representative name | `Jennifer Walsh` |
+| `{{our_contact_title}}` | Our representative title | `Director of Energy Procurement` |
+| `{{our_contact_email}}` | Our representative email | `jwalsh@meridian.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(614) 555-0247` |
+| `{{supplier_name}}` | Energy supplier name | `NorthStar Energy Solutions` |
+| `{{supplier_contact}}` | Supplier contact name | `David Chen` |
+| `{{supplier_contact_title}}` | Supplier contact title | `VP, Commercial Sales` |
+| `{{utility_name}}` | Utility company name | `AEP Ohio` |
+| `{{iso_name}}` | ISO/RTO name | `PJM Interconnection` |
+| `{{facility_name}}` | Facility name | `Columbus Manufacturing Plant` |
+| `{{facility_address}}` | Facility address | `4500 Industrial Parkway, Columbus, OH 43228` |
+| `{{account_number}}` | Utility account number | `110-485-7723` |
+| `{{annual_consumption_mwh}}` | Annual electricity consumption | `42,000 MWh` |
+| `{{peak_demand_kw}}` | Peak demand in kW | `6,200 kW` |
+| `{{current_rate}}` | Current contract rate | `$0.058/kWh` |
+| `{{proposed_rate}}` | Proposed new rate | `$0.054/kWh` |
+| `{{market_rate}}` | Market benchmark rate | `$0.062/kWh` |
+| `{{contract_start}}` | Contract start date | `2027-01-01` |
+| `{{contract_end}}` | Contract end date | `2029-12-31` |
+| `{{rfp_deadline}}` | RFP response deadline | `2026-05-15` |
+| `{{ppa_project_name}}` | Renewable project name | `Prairie Wind Farm II` |
+| `{{ppa_capacity_mw}}` | PPA project capacity | `150 MW` |
+| `{{ppa_strike_price}}` | PPA strike price | `$34/MWh` |
+| `{{ppa_term_years}}` | PPA contract term | `15 years` |
+| `{{re_percentage}}` | Current renewable energy percentage | `38%` |
+| `{{re_target}}` | RE100 target year | `2030` |
+| `{{docket_number}}` | Regulatory docket number | `Case No. 26-1234-EL-AIR` |
+| `{{budget_year}}` | Budget forecast year | `2027` |
+| `{{total_energy_spend}}` | Total annual energy spend | `$14.2M` |
+| `{{num_facilities}}` | Number of facilities | `18` |
+
+---
+
+## 1. RFP to Energy Suppliers
+
+**Channel:** Email with attached RFP document
+**Audience:** Retail energy provider sales/pricing team
+**Tone:** Professional, data-rich, competitive. You're offering a significant commercial opportunity — present it as such.
+
+---
+
+**Subject:** `Invitation to Bid — {{our_company}} Electricity Supply RFP — {{contract_start}} Start`
+
+{{supplier_contact}},
+
+{{our_company}} is conducting a competitive electricity supply procurement for {{num_facilities}} facilities across {{iso_name}} territory. We are inviting {{supplier_name}} to participate based on your market position and capabilities in our service territory.
+
+**RFP Summary:**
+- **Scope:** {{num_facilities}} commercial and industrial facilities
+- **Total annual consumption:** {{annual_consumption_mwh}}
+- **Aggregate peak demand:** {{peak_demand_kw}}
+- **Contract period:** {{contract_start}} through {{contract_end}}
+- **Product structures requested:** Fixed-price full requirements, block-and-index, and index with price cap
+- **Bid deadline:** {{rfp_deadline}}, 5:00 PM ET
+
+**Included with this invitation:**
+1. RFP response template (Excel) with site-level detail
+2. 36 months of 15-minute interval data for each facility (CSV)
+3. Current tariff information and utility account numbers
+4. Evaluation criteria and weighting
+
+**Evaluation criteria:**
+- Total cost across three price scenarios (40%)
+- Supplier credit quality and financial stability (20%)
+- Contract flexibility including volume tolerance and early termination provisions (15%)
+- Sustainability services — REC sourcing, carbon reporting, PPA advisory (15%)
+- Market intelligence and advisory capabilities (10%)
+
+**Key requirements:**
+- All bids must include volume tolerance of ±10% minimum
+- Pricing must be provided for all three product structures independently
+- Supplier must demonstrate minimum BBB credit rating or equivalent
+- RECs must be sourced from projects within the {{iso_name}} footprint
+
+Please confirm your intent to participate by {{rfp_confirmation_date}}. Clarification questions will be accepted through {{rfp_questions_deadline}} via email to {{our_contact_email}}.
+
+We look forward to {{supplier_name}}'s participation.
+
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+**Tone Notes:**
+- Do not share current pricing with bidders. "Current contract details are confidential" is the standard response.
+- Do not disclose the number of bidders. "We have invited a competitive field" is sufficient.
+- Respond to all clarification questions in a consolidated Q&A sent to all bidders simultaneously to maintain fairness.
+
+---
+
+## 2. PPA Term Sheet Response
+
+**Channel:** Email to developer's commercial team
+**Audience:** Renewable energy project developer
+**Tone:** Collaborative but commercially rigorous. PPAs are 10-25 year commitments — every term matters.
+
+---
+
+**Subject:** `{{our_company}} Response to {{ppa_project_name}} Term Sheet — Commercial Feedback`
+
+{{developer_contact}},
+
+Thank you for the term sheet for {{ppa_project_name}} ({{ppa_capacity_mw}}). We've completed our initial review and have the following feedback organized by commercial, financial, and operational terms.
+
+**Commercial Terms:**
+- **Strike price:** The proposed {{ppa_strike_price}} is within our target range based on current forward curves. We would like to discuss a price escalator structure — 0% escalation for years 1-5 with a [CPI-linked / fixed 1.5%] escalator beginning year 6.
+- **Settlement point:** We request settlement at the {{iso_name}} [load zone / hub] rather than the project node, to reduce our basis risk exposure. We understand this may require a price adjustment and are prepared to discuss.
+- **Contract volume:** We would like to discuss a partial offtake ({{our_offtake_mw}} MW of the {{ppa_capacity_mw}} project) with right of first refusal on additional capacity.
+
+**Risk Allocation:**
+- **Curtailment:** We request that the developer bear curtailment risk for the first 5% annually, with shared risk (50/50) for curtailment between 5-10%, and developer risk above 10%. The current term sheet allocates all curtailment risk to the offtaker, which is not acceptable for a {{ppa_term_years}}-year commitment.
+- **Negative pricing:** We require a negative price floor provision: during intervals when the settlement point LMP is negative, no settlement occurs (neither party pays). This protects both parties from volatile negative pricing hours.
+- **Change of law:** The term sheet's change-of-law provision is one-sided. We propose mutual termination rights if a regulatory change materially affects the economics for either party, with a defined materiality threshold of {{materiality_threshold}}.
+
+**Financial and Credit:**
+- **Credit support:** We are prepared to provide [a parent guarantee / an LC] for an amount equal to {{credit_support_amount}}, sized to 2 years of potential negative mark-to-market exposure under our stress scenario.
+- **Accounting treatment:** We require confirmation that the PPA structure qualifies for normal purchases and normal sales (NPNS) exception under ASC 815, or alternatively that hedge accounting is achievable. Our treasury team will need to review the final contract with our auditors.
+
+**REC Provisions:**
+- **Vintage delivery:** RECs must be delivered within 12 months of generation to maintain RE100 compliance.
+- **Replacement RECs:** If the project underdelivers RECs by more than 10% in any year, the developer provides replacement RECs from a comparable facility at no additional cost.
+
+We would welcome a call this week to discuss these points. Please suggest availability.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+**Tone Notes:**
+- PPA negotiations are multi-round. The first response should establish your key positions without ultimatums.
+- Always frame risk allocation as "fair to both parties" rather than "we won't accept your risk."
+- Developers receive dozens of term sheet responses — be specific and organized to stand out as a serious offtaker.
+
+---
+
+## 3. Utility Rate Case Intervention Comment
+
+**Channel:** Formal filing with state Public Utility Commission
+**Audience:** PUC commissioners, administrative law judge, utility regulatory staff
+**Tone:** Formal, data-driven, legally precise. This is a regulatory proceeding — opinions must be supported by evidence.
+
+---
+
+**Re:** {{docket_number}} — {{utility_name}} Application for Rate Increase
+
+**Before the {{state}} Public Utilities Commission**
+
+**Comments of {{our_company}}**
+
+{{our_company}} respectfully submits these comments regarding {{utility_name}}'s application for a general rate increase filed on {{filing_date}}.
+
+**I. Interest of {{our_company}}**
+
+{{our_company}} operates {{num_facilities}} facilities in {{utility_name}}'s service territory, consuming approximately {{annual_consumption_mwh}} annually under rate schedule {{rate_schedule}}. The proposed rate increase would impose an estimated additional cost of ${{annual_impact}} per year on {{our_company}}'s operations.
+
+**II. Summary of Concerns**
+
+{{our_company}} does not oppose {{utility_name}}'s right to recover prudently incurred costs and earn a fair return. However, we raise the following concerns regarding the application as filed:
+
+1. **Requested return on equity (ROE):** {{utility_name}} requests a {{requested_roe}}% ROE. Recent commission decisions in comparable proceedings in {{comparable_states}} have authorized ROEs of {{comparable_roe_range}}%. We respectfully submit that the requested ROE exceeds the range supported by current capital market conditions.
+
+2. **Rate design:** The proposed rate design increases the volumetric energy charge by {{energy_increase_pct}}% while reducing the demand charge by only {{demand_decrease_pct}}%. This cost allocation methodology disadvantages high-load-factor industrial customers who contribute less to system peak on a per-kWh basis. We recommend cost allocation based on demonstrated cost causation, using a coincident peak methodology for demand-related costs.
+
+3. **Rider pass-through timing:** The proposed infrastructure improvement rider allows for quarterly rate adjustments without commission review. We request that any rider mechanism include an annual true-up with commission review and a cumulative cap of {{rider_cap_pct}}% to prevent rate shock.
+
+**III. Requested Relief**
+
+{{our_company}} requests that the Commission:
+- Set ROE at the midpoint of comparable authorized returns (approximately {{recommended_roe}}%)
+- Adopt a coincident-peak cost allocation methodology for the {{rate_schedule}} rate class
+- Include annual commission review and a cumulative cap on the proposed infrastructure rider
+
+{{our_contact_name}}
+{{our_contact_title}}, {{our_company}}
+
+---
+
+## 4. Demand Response Program Enrollment
+
+**Channel:** Formal enrollment application
+**Audience:** Utility or ISO demand response program administrator
+**Tone:** Technical, precise. DR enrollment documents are contractual — accuracy matters.
+
+---
+
+**Subject:** `Demand Response Program Enrollment Application — {{facility_name}}`
+
+To: {{dr_program_administrator}}
+
+{{our_company}} hereby applies to enroll {{facility_name}} in the {{dr_program_name}} for the {{delivery_year}} delivery year.
+
+**Facility Information:**
+- **Facility:** {{facility_name}}
+- **Address:** {{facility_address}}
+- **Utility account:** {{account_number}}
+- **Meter ID:** {{meter_id}}
+- **Service voltage:** {{service_voltage}}
+- **Current peak demand:** {{peak_demand_kw}}
+
+**Curtailment Capability:**
+- **Committed curtailment capacity:** {{dr_commitment_kw}} kW
+- **Minimum notification time required:** {{notification_minutes}} minutes
+- **Maximum curtailment duration:** {{max_duration_hours}} hours
+- **Curtailment method:** [Load shedding via BAS / Backup generation / Battery discharge / Combination]
+- **Loads available for curtailment:** {{curtailable_loads}}
+- **Loads NOT available for curtailment (critical process):** {{non_curtailable_loads}}
+
+**Baseline Methodology:**
+We request the {{baseline_method}} baseline calculation methodology. Attached is a 12-month interval data file demonstrating our typical load profile during the DR event window ({{event_window}}).
+
+**Testing:**
+We are available for an enrollment verification test during the week of {{test_week}}. We can demonstrate the full {{dr_commitment_kw}} kW curtailment within {{notification_minutes}} minutes of notification.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+## 5. Budget Forecast Presentation
+
+**Channel:** Internal presentation (PowerPoint / memo)
+**Audience:** CFO, VP Finance, Budget Committee
+**Tone:** Precise, scenario-based, action-oriented. Finance wants numbers, ranges, and decision points — not energy market tutorials.
+
+---
+
+### {{budget_year}} Energy Cost Forecast — {{our_company}}
+
+**Prepared by:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{forecast_date}}
+**Scope:** {{num_facilities}} facilities, all electricity and natural gas
+
+**Executive Summary:**
+The {{budget_year}} total energy spend is forecast at **${{base_case_total}}** under base case assumptions, representing a {{yoy_change_pct}}% [increase/decrease] from {{prior_year}} actuals of ${{prior_year_total}}. The forecast range under stress scenarios is **${{low_case_total}}** to **${{high_case_total}}**.
+
+| Component | {{prior_year}} Actual | {{budget_year}} Base Case | Change |
+|-----------|---------------------|--------------------------|--------|
+| Electricity — supply | ${{elec_supply_prior}} | ${{elec_supply_forecast}} | {{elec_supply_change}} |
+| Electricity — delivery (T&D) | ${{elec_delivery_prior}} | ${{elec_delivery_forecast}} | {{elec_delivery_change}} |
+| Electricity — demand charges | ${{demand_charges_prior}} | ${{demand_charges_forecast}} | {{demand_change}} |
+| Electricity — capacity charges | ${{capacity_prior}} | ${{capacity_forecast}} | {{capacity_change}} |
+| Natural gas | ${{gas_prior}} | ${{gas_forecast}} | {{gas_change}} |
+| RECs / sustainability | ${{rec_prior}} | ${{rec_forecast}} | {{rec_change}} |
+| **Total** | **${{prior_year_total}}** | **${{base_case_total}}** | **{{total_change}}** |
+
+**Key Assumptions:**
+- Electricity forward curve: {{forward_curve_source}} as of {{curve_date}}
+- Natural gas: Henry Hub {{gas_assumption}} + basis of {{basis_assumption}}
+- Weather: 10-year normal HDD/CDD
+- Production volume: [flat / {{production_change}}% change] vs. prior year
+- Hedged position: {{hedge_pct}}% of electricity volume locked at ${{hedged_rate}}/MWh
+
+**Scenario Analysis:**
+
+| Scenario | Electricity Cost | Gas Cost | Total | vs. Base Case |
+|----------|-----------------|----------|-------|---------------|
+| Base case | ${{elec_base}} | ${{gas_base}} | ${{base_case_total}} | — |
+| Mild winter / cool summer | ${{elec_low}} | ${{gas_low}} | ${{low_case_total}} | {{low_delta}} |
+| Severe winter / hot summer | ${{elec_high}} | ${{gas_high}} | ${{high_case_total}} | {{high_delta}} |
+| Market stress (2× forward) | ${{elec_stress}} | ${{gas_stress}} | ${{stress_total}} | {{stress_delta}} |
+
+**Decisions Requested:**
+1. Approve the base case budget of ${{base_case_total}}
+2. Authorize procurement of an additional {{additional_hedge_pct}}% hedge to bring total hedged position to {{target_hedge_pct}}%
+3. Approve ${{capex_amount}} capital budget for demand charge mitigation at {{capex_facilities}}
+
+---
+
+## 6. Sustainability Report — Energy Section
+
+**Channel:** Annual sustainability / ESG report
+**Audience:** Investors, customers, ESG rating agencies, RE100, CDP
+**Tone:** Transparent, data-backed, forward-looking. Avoid greenwashing — ESG audiences are sophisticated.
+
+---
+
+### Energy and Climate — {{report_year}}
+
+**Scope 2 Emissions:**
+
+| Metric | {{prior_year}} | {{report_year}} | Change |
+|--------|---------------|-----------------|--------|
+| Total electricity consumed (MWh) | {{elec_prior_mwh}} | {{elec_current_mwh}} | {{elec_change_pct}} |
+| Scope 2 — Location-based (MT CO₂e) | {{scope2_loc_prior}} | {{scope2_loc_current}} | {{scope2_loc_change}} |
+| Scope 2 — Market-based (MT CO₂e) | {{scope2_mkt_prior}} | {{scope2_mkt_current}} | {{scope2_mkt_change}} |
+| Renewable electricity (%) | {{re_pct_prior}} | {{re_pct_current}} | {{re_change}} |
+
+**Renewable Energy Procurement:**
+
+| Instrument | Volume (MWh) | Source | Additionality |
+|-----------|-------------|--------|---------------|
+| Physical PPA | {{phys_ppa_mwh}} | {{phys_ppa_project}} | New project, operational {{ppa_cod}} |
+| Virtual PPA (RECs) | {{vppa_rec_mwh}} | {{vppa_project}} | New project, {{vppa_location}} |
+| Utility green tariff | {{green_tariff_mwh}} | {{green_tariff_utility}} | Program-dependent |
+| Unbundled RECs | {{unbundled_rec_mwh}} | National wind | Market RECs |
+| On-site solar | {{onsite_mwh}} | {{onsite_locations}} | Direct generation |
+
+**RE100 Progress:** {{our_company}} has achieved {{re_pct_current}}% renewable electricity in {{report_year}}, on track for our commitment of 100% by {{re_target}}.
+
+**Forward-Looking Targets:**
+- {{re_target_next_year}}% renewable electricity by end of {{next_year}}
+- Execute additional {{next_ppa_mw}} MW of renewable procurement by Q2 {{next_year}}
+- Reduce Scope 2 market-based emissions by {{scope2_reduction_target}}% by {{target_year}} (vs. {{baseline_year}} baseline)
+
+---
+
+## 7. Internal Energy Cost Variance Analysis
+
+**Channel:** Monthly internal memo
+**Audience:** Finance controller, plant managers, VP Operations
+**Tone:** Analytical, action-oriented. Explain the "why" behind variances and what's being done about them.
+
+---
+
+**Subject:** `Energy Cost Variance Report — {{month}} {{year}}`
+
+**Summary:** Total energy cost of ${{actual_total}} vs. budget of ${{budget_total}} — variance of ${{variance}} ({{variance_pct}}).
+
+**Variance Decomposition:**
+
+| Driver | Impact | Explanation |
+|--------|--------|-------------|
+| Weather (HDD/CDD vs. normal) | ${{weather_impact}} | {{month}} was {{weather_description}} — {{hdd_cdd_actual}} vs. {{hdd_cdd_budget}} budgeted HDD/CDD |
+| Market price (index exposure) | ${{market_impact}} | Day-ahead LMP averaged ${{actual_lmp}}/MWh vs. budget assumption of ${{budget_lmp}}/MWh |
+| Demand charges | ${{demand_impact}} | Peak demand of {{actual_peak_kw}} kW vs. budget of {{budget_peak_kw}} kW at {{facility_name}} |
+| Production volume | ${{volume_impact}} | Production hours {{production_description}} vs. plan |
+| Rate/tariff changes | ${{tariff_impact}} | {{tariff_description}} |
+
+**Actions Taken:**
+1. {{action_1}}
+2. {{action_2}}
+3. {{action_3}}
+
+**Forecast Revision:** Based on YTD actuals, the full-year energy cost forecast is revised to ${{revised_forecast}} (previously ${{prior_forecast}}). Primary driver: {{revision_driver}}.
+
+---
+
+## 8. Supplier Contract Renewal Negotiation
+
+**Channel:** Email
+**Audience:** Incumbent energy supplier's commercial team
+**Tone:** Relationship-forward, data-informed. You want to renew if terms are fair — make that clear while establishing competitive tension.
+
+---
+
+**Subject:** `Contract Renewal Discussion — {{our_company}} / {{supplier_name}} — {{contract_end}} Expiration`
+
+{{supplier_contact}},
+
+Our current supply agreement expires {{contract_end}}, and we'd like to discuss renewal terms. {{supplier_name}} has been a valued partner for the past {{contract_duration}}, and we'd like to continue the relationship under commercially competitive terms.
+
+To frame the discussion, here is our perspective on renewal:
+
+**What's worked well:**
+- Billing accuracy and operational execution have been excellent
+- Market intelligence updates have been valuable for our procurement planning
+- The account management team has been responsive and proactive
+
+**Where we'd like to see improvement:**
+- Our current rate of {{current_rate}} was competitive at signing but the forward curve for the renewal period ({{contract_start}} through {{new_contract_end}}) is currently {{market_rate}} — we need renewal pricing that reflects current market conditions
+- We'd like to discuss [block-and-index structure / increased volume tolerance / REC bundling] for the renewal term
+
+**Our process:**
+We are conducting a competitive evaluation for this renewal. We've invited {{num_bidders}} suppliers to provide indicative pricing. Our decision timeline:
+- Indicative pricing review: {{pricing_review_date}}
+- Shortlist and final negotiation: {{negotiation_date}}
+- Contract execution: {{execution_date}}
+
+We would welcome a call on {{proposed_call_date}} to discuss {{supplier_name}}'s renewal offer. Please send indicative pricing for the structures outlined above by {{pricing_deadline}}.
+
+{{our_contact_name}}
+{{our_contact_title}}
+
+---
+
+**Tone Notes:**
+- Name the competitive process but don't bluff about the number of bidders.
+- Lead with what's worked well — the incumbent relationship has value and you should acknowledge it.
+- Be transparent about timeline so the supplier can allocate pricing resources.
+
+---
+
+## 9. Regulatory Filing Comment
+
+**Channel:** Written comment to regulatory body (FERC, state PUC, ISO stakeholder process)
+**Audience:** Regulatory commissioners, ISO market design team
+**Tone:** Policy-oriented, evidence-based. Regulators respect commenters who understand the market mechanics.
+
+---
+
+**Re:** {{docket_number}} — Proposed Modifications to {{program_or_rule}}
+
+{{our_company}} appreciates the opportunity to comment on the proposed modifications to {{program_or_rule}}.
+
+As a large commercial and industrial electricity consumer in {{iso_name}} territory with {{annual_consumption_mwh}} of annual consumption, {{our_company}} has a direct interest in market designs that promote efficient price formation, reliable capacity procurement, and equitable cost allocation.
+
+**Support / Concern:**
+{{our_company}} [supports / has concerns regarding] the proposed modifications, specifically:
+
+1. **{{provision_1}}:** [Position and rationale with specific reference to the proposal's impact on C&I consumers]
+2. **{{provision_2}}:** [Position with quantitative impact estimate if available]
+3. **{{provision_3}}:** [Position with alternative proposal if opposing]
+
+**Recommendation:**
+{{our_company}} recommends that the Commission [approve with modifications / reject / defer pending further analysis] the proposed {{program_or_rule}} changes, specifically incorporating the following modifications:
+- {{recommendation_1}}
+- {{recommendation_2}}
+
+Respectfully submitted,
+
+{{our_contact_name}}
+{{our_contact_title}}, {{our_company}}
+
+---
+
+## 10. Board-Level Energy Strategy Summary
+
+**Channel:** Board meeting memo / presentation
+**Audience:** Board of Directors, CEO, CFO
+**Tone:** Strategic, concise, decision-focused. The board cares about risk, cost trajectory, sustainability commitments, and capital allocation — not market mechanics.
+
+---
+
+### Energy Strategy Update — {{quarter}} {{year}}
+
+**For the Board of Directors, {{our_company}}**
+
+**Key Metrics:**
+
+| Metric | Current | Target | Status |
+|--------|---------|--------|--------|
+| Annual energy spend | ${{current_spend}} | ${{target_spend}} | {{spend_status}} |
+| Energy cost as % of revenue | {{energy_pct_revenue}}% | {{target_pct}}% | {{pct_status}} |
+| Renewable electricity (RE100) | {{re_pct_current}}% | 100% by {{re_target}} | {{re_status}} |
+| Scope 2 emissions (market-based) | {{current_emissions}} MT CO₂e | {{target_emissions}} MT | {{emissions_status}} |
+
+**Strategic Priorities:**
+1. **Cost management:** [1-2 sentence summary of procurement strategy and results]
+2. **Sustainability:** [1-2 sentence summary of RE100 progress and next milestones]
+3. **Risk management:** [1-2 sentence summary of hedge position and market outlook]
+
+**Decisions Requested:**
+1. Approve execution of a {{ppa_term_years}}-year virtual PPA with {{ppa_project_name}} at {{ppa_strike_price}} for {{ppa_capacity_mw}} MW — projected NPV of ${{ppa_npv}} over the contract term, delivering {{ppa_annual_recs}} RECs annually toward our RE100 commitment.
+2. Authorize ${{capex_amount}} in capital expenditure for battery energy storage at {{capex_facilities}} — projected {{payback_years}}-year payback with stacked value of ${{annual_savings}}/year in demand charge and capacity cost reduction.
+
+**Risk Summary:**
+- Market risk: {{hedge_pct}}% hedged through {{hedge_end}}. Unhedged exposure: ${{unhedged_exposure}} at current forwards.
+- Regulatory risk: {{regulatory_summary}}
+- Supplier risk: All supply contracts with investment-grade counterparties. No credit concerns.
+
+**Next Update:** {{next_update_date}}
+
+---
+
+**Tone Notes:**
+- Board communication must be under 2 pages. Provide appendices for detail.
+- Lead with the "ask" — if you need board approval for a PPA or capital project, put it in the executive summary.
+- Quantify everything. "Good progress on sustainability" means nothing. "38% RE, on track for 50% by year-end" means everything.
+- Acknowledge risks explicitly. A board that discovers unmentioned risks loses trust in management.
diff --git a/web-app/public/skills/energy-procurement/references/decision-frameworks.md b/web-app/public/skills/energy-procurement/references/decision-frameworks.md
new file mode 100644
index 00000000..042176b9
--- /dev/null
+++ b/web-app/public/skills/energy-procurement/references/decision-frameworks.md
@@ -0,0 +1,851 @@
+# Decision Frameworks — Energy Procurement
+
+This reference provides detailed decision trees, evaluation matrices, financial models,
+and strategic frameworks for electricity and gas procurement, tariff optimization,
+demand charge management, PPA evaluation, hedging strategy design, and multi-facility
+portfolio optimization. It is loaded on demand when the agent needs to make or
+recommend nuanced energy procurement decisions.
+
+All thresholds, price assumptions, and market benchmarks reflect US commercial and
+industrial electricity and natural gas markets. Adjust for regional markets, current
+forward curves, and facility-specific tariff structures.
+
+---
+
+## 1. Procurement Strategy Selection
+
+### 1.1 Pre-Procurement Intelligence Gathering
+
+Before entering any procurement decision — contract renewal, new facility onboarding,
+or mid-term restructuring — assemble a comprehensive data package.
+
+#### Data Assembly Checklist
+
+| Data Point | Source | Purpose |
+|-----------|--------|---------|
+| 36 months of 15-minute interval data (kWh and kW) | Utility meter data / MDM system | Load shape analysis, peak identification |
+| Current tariff rate schedule and all applicable riders | Utility tariff book / state PUC | Baseline cost structure |
+| Current supply contract terms, expiration, and auto-renewal provisions | Contract file | Timeline and constraints |
+| Forward energy curves (12, 24, 36 month) for relevant hub | ICE, CME, broker quotes | Market benchmark for pricing evaluation |
+| Capacity market auction results (PJM RPM, ISO-NE FCA) | ISO publications | Future capacity charge forecasting |
+| Facility peak load contribution (PLC) or installed capacity (ICAP) tag | Utility / ISO settlement data | Capacity charge exposure |
+| Historical weather data (HDD/CDD) for facility locations | NOAA / weather service | Weather-normalization of consumption |
+| Pending utility rate cases at state PUC | State PUC docket search | Regulatory risk assessment |
+| Corporate sustainability targets and timeline | Sustainability team | Renewable procurement requirements |
+| Capital budget availability for demand-side investments | Finance team | Investment constraint for demand charge mitigation |
+
+### 1.2 Fixed vs. Index vs. Block-and-Index Decision Tree
+
+Use this decision tree for each facility or portfolio segment independently — one
+strategy does not fit all sites.
+
+```
+START: What is the organization's tolerance for energy cost variance?
+
+├── Budget variance >10% triggers executive escalation
+│ ├── Contract tenor ≤ 24 months?
+│ │ └── YES → Fixed-price full requirements
+│ │ - Accept the risk premium (5-12% above forward curve)
+│ │ - Negotiate volume tolerance band (±10-15%)
+│ │ - Ensure contract includes change-of-use provisions
+│ │ └── NO (>24 months) → Fixed-price with annual price resets
+│ │ - Lock year 1 at fixed, years 2-3 at a formula (forward + adder)
+│ │ - This limits the supplier's long-term risk premium
+│
+├── Budget variance of 5-10% is manageable
+│ ├── Facility load factor > 0.70?
+│ │ └── YES → Block-and-index
+│ │ - Buy fixed blocks = 70-80% of baseload
+│ │ - Float remaining 20-30% at index (day-ahead or real-time)
+│ │ - Shape blocks to match base load pattern (ATC vs. on-peak only)
+│ │ └── NO (load factor < 0.70) → Shaped block-and-index
+│ │ - Buy on-peak blocks only (match production schedule)
+│ │ - Float off-peak and shoulder at index
+│ │ - Supplement with TOU-indexed product for off-peak
+│
+├── Organization can tolerate >15% variance (energy is <5% of COGS)
+│ ├── Internal capability to monitor wholesale markets?
+│ │ └── YES → Index pricing with financial hedges
+│ │ - Base product: real-time or day-ahead index + supplier adder
+│ │ - Layer financial hedges: buy call options for peak months
+│ │ - Set a price ceiling through options ($X/MWh cap)
+│ │ └── NO → Index with a price cap product
+│ │ - Supplier provides index pricing with a contractual ceiling
+│ │ - Cap premium is typically $3-7/MWh above forward curve
+│ │ - Simpler than managing separate financial hedges
+```
+
+### 1.3 Layered Procurement Methodology
+
+Layering eliminates single-point market timing risk. The methodology:
+
+**Step 1: Determine the hedging horizon.**
+Most C&I buyers layer 18–36 months ahead of the delivery period. For a January 2028
+start date, begin buying tranches in July 2026.
+
+**Step 2: Set the number of tranches.**
+Standard approaches:
+
+| Tranches | Buying Frequency | Volume per Tranche | Best For |
+|----------|-----------------|-------------------|----------|
+| 4 | Quarterly | 25% | Default approach, good balance |
+| 6 | Bimonthly | ~17% | Large portfolios, higher granularity |
+| 8 | Monthly (final 8 months) | 12.5% | Aggressive dollar-cost averaging |
+| 12 | Monthly | ~8% | Very large portfolios with dedicated procurement staff |
+
+**Step 3: Execution rules.**
+- Execute each tranche at the prevailing market price on the scheduled date — do not try to time within the tranche window.
+- Exception: if the forward curve drops into the bottom 20th percentile of the 5-year range, accelerate by buying 2 tranches immediately ("buy the dip" rule).
+- Exception: if the forward curve spikes into the top 20th percentile, defer the current tranche by 30 days (skip and catch up later).
+- Never defer more than 2 consecutive tranches — rolling deferrals leave you unhedged.
+
+**Step 4: Document and report.**
+Maintain a procurement log showing: tranche date, volume procured, price locked,
+forward curve price at execution, cumulative weighted average price, and remaining
+open position. Report to finance quarterly.
+
+**Example — 10 MW peak load, 60M kWh annual consumption:**
+
+```
+Delivery year: 2028
+Hedging start: July 2026
+Tranches: 6 (bimonthly, ~10M kWh each)
+
+Tranche 1 (Jul 2026): 10M kWh @ $44.50/MWh — Forward was $45.20
+Tranche 2 (Sep 2026): 10M kWh @ $42.80/MWh — Forward was $43.10
+Tranche 3 (Nov 2026): 10M kWh @ $46.30/MWh — Forward was $46.30
+Tranche 4 (Jan 2027): 10M kWh @ $41.20/MWh — Forward was $41.50 (buy-the-dip rule:
+ also executed Tranche 5 early)
+Tranche 5 (Jan 2027): 10M kWh @ $41.40/MWh — Accelerated from March
+Tranche 6 (May 2027): 10M kWh @ $43.80/MWh — Forward was $44.00
+
+Weighted average: $43.33/MWh
+Range of execution prices: $41.20 - $46.30 ($5.10 spread)
+If locked all-at-once in Jul 2026: $44.50/MWh → layering saved $1.17/MWh = $70,200
+```
+
+### 1.4 RFP Process for Deregulated Markets
+
+#### Timeline and Phases
+
+| Phase | Duration | Key Activities |
+|-------|----------|---------------|
+| Pre-RFP Analysis | 2-3 weeks | Load data assembly, tariff analysis, market benchmarking, sustainability requirements definition |
+| RFP Design | 1-2 weeks | Template creation, supplier longlist development, evaluation criteria weighting |
+| RFP Distribution | 1 week | Issue to 5-8 qualified REPs, respond to clarification questions |
+| Bid Window | 2-3 weeks | Suppliers develop pricing based on your interval data and requirements |
+| Bid Evaluation | 1-2 weeks | Total cost modeling, credit assessment, contract review |
+| Negotiation | 1-2 weeks | Shortlist to 2-3, negotiate terms, finalize pricing |
+| Award and Execution | 1 week | Sign contract, notify utility of supplier switch (may require 30-60 day lead time) |
+| **Total** | **9-14 weeks** | |
+
+#### Supplier Evaluation Scoring Matrix
+
+| Criterion | Weight | Scoring Guide |
+|-----------|--------|---------------|
+| Total cost (energy + adder + shaped premium) | 35-45% | Lowest total cost = 100 pts. Each 1% above lowest = -5 pts. Model across 3 price scenarios. |
+| Credit quality | 15-20% | Investment grade (S&P BBB- or above) = 100 pts. Sub-investment grade = 50 pts. No rating / private = 70 pts with parent guarantee, 30 pts without. |
+| Contract flexibility | 10-15% | Volume tolerance ±15% = 100. Volume tolerance ±5% = 50. No tolerance = 0. Early termination available = +20 pts. Change-of-use provisions = +15 pts. |
+| Sustainability services | 10-15% | Bundled RECs from named projects = 100. Unbundled RECs available = 60. No REC options = 0. Carbon reporting support = +20 pts. |
+| Market intelligence and advisory | 5-10% | Dedicated account manager + regular market updates = 100. Account manager only = 50. Call center support = 0. |
+| Operational capability | 5-10% | EDI/API billing integration = 100. Electronic invoicing only = 60. Paper billing = 0. Multi-site consolidated billing = +20 pts. |
+
+#### Bid Comparison Template
+
+For each site, model the annual cost under each supplier's proposal:
+
+```
+Annual Cost = Σ(hourly volume × hourly price) + fixed charges + REC costs + adder fees
+
+Where hourly price depends on product structure:
+ Fixed: contract rate for all hours
+ Block-and-index: block rate for block volume + index price for excess
+ Index: (day-ahead or real-time LMP at load zone) + supplier adder
+```
+
+Always model at three forward price scenarios: base case (current forward curve),
+low case (forward - 20%), and high case (forward + 30%). A supplier whose index
+product looks cheapest at base case may be the most expensive at high case.
+
+---
+
+## 2. PPA Evaluation Framework
+
+### 2.1 Physical PPA Evaluation
+
+Physical PPAs involve direct energy delivery and are appropriate when:
+- Your load is in the same ISO as the project
+- You want both energy and RECs from a specific named facility
+- You can manage the operational complexity of scheduling and balancing
+
+#### Financial Modeling Framework
+
+**Step 1: Establish the baseline (no-PPA scenario).**
+Project your energy costs over the PPA term using forward curves for years 1-5 and
+a long-term price escalation assumption (typically 2-3%/year) for years 6+.
+
+**Step 2: Model PPA cash flows.**
+
+```
+Year N PPA Net Value = (Market Price at Hub - PPA Strike Price) × Expected Generation
+ - Basis Cost (Hub to Load Zone)
+ - Curtailment Cost (expected curtailed MWh × strike price)
+ - Balancing Costs (firming residual load not covered by PPA)
+ + REC Value (if RECs would otherwise be purchased separately)
+```
+
+**Step 3: Sensitivity analysis — run these scenarios at minimum:**
+
+| Scenario | Market Price Assumption | Generation Assumption | Basis Assumption |
+|----------|----------------------|----------------------|-----------------|
+| Base | Current forward curve + 2.5%/yr escalation | Developer's P50 estimate | 5-year historical average basis |
+| Bull | Forward + 4%/yr escalation | P50 generation | Basis narrows 20% |
+| Bear | Forward + 1%/yr escalation | P75 generation (lower) | Basis widens 30% |
+| Stress | Flat prices for 5 years, then 2%/yr | P90 generation (much lower) | Basis widens 50% |
+
+**Step 4: Calculate NPV, IRR, and levelized cost of energy (LCOE) under each scenario.**
+A PPA is economically justified if NPV is positive under base and bull cases and
+the loss under bear case is tolerable (typically <$2M cumulative over the PPA term
+for a mid-size C&I buyer).
+
+### 2.2 Virtual PPA (VPPA) Evaluation
+
+VPPAs are financial instruments — no physical energy delivery. The key risks differ:
+
+#### Basis Risk Analysis
+
+Basis risk is the primary financial risk in a VPPA. It arises because the generator
+settles at its node price and your load settles at your load zone price.
+
+**Quantification method:**
+
+1. Obtain 3-5 years of hourly LMP data for the generator's node and your load zone from the ISO.
+2. Calculate the hourly basis: Load Zone LMP - Generator Node LMP.
+3. Filter to hours when the generator would be producing (solar: daylight hours; wind: use historical generation profile).
+4. Calculate the generation-weighted average basis.
+5. Model the basis impact on PPA settlement:
+
+```
+Annual Basis Cost = Σ(hourly basis × hourly expected generation)
+
+If generation-weighted average basis = $5/MWh and annual generation = 200,000 MWh:
+Annual Basis Cost = $1,000,000/year
+Over a 15-year PPA: $15M in basis costs (undiscounted)
+```
+
+**Red flags for basis risk:**
+- Basis spread > $8/MWh generation-weighted average → high risk, negotiate basis hedge or reject
+- Basis volatility (standard deviation) > $15/MWh → unpredictable, hard to budget
+- Basis trend is widening over the historical period → structural congestion, likely to worsen
+- Generator is located behind a known transmission constraint → congestion will increase as more generation is added in that zone
+
+#### Curtailment Risk Analysis
+
+Curtailment occurs when the ISO orders the generator to reduce output due to
+transmission constraints or oversupply.
+
+| ISO | Technology | Typical Curtailment % | Trend |
+|-----|-----------|----------------------|-------|
+| ERCOT | Wind (West Texas) | 3-8% | Increasing as more wind is added |
+| ERCOT | Solar | 1-3% | Low but increasing |
+| CAISO | Solar | 5-12% (spring) | Increasing due to duck curve |
+| CAISO | Wind | 1-3% | Stable |
+| PJM | Wind | <1% | Minimal |
+| PJM | Solar | <1% | Minimal |
+| MISO | Wind | 2-5% | Moderate, depends on zone |
+| SPP | Wind | 3-7% | Increasing in western zones |
+
+**Contract protection:** Negotiate a curtailment threshold (e.g., first 5% is developer
+risk) and a compensation mechanism for excess curtailment (developer provides
+replacement RECs or a price adjustment). Never accept "buyer bears all curtailment
+risk" on a VPPA — this transfers a risk the buyer cannot manage or influence.
+
+#### Credit and Accounting Requirements
+
+| Requirement | Details |
+|-------------|---------|
+| ISDA Master Agreement | Required for VPPA. Negotiate credit thresholds, margin call provisions, and termination values. |
+| Credit support | Investment grade: typically no collateral for first $5-10M notional. Sub-IG: letter of credit or parent guarantee for 2-3 years of potential negative settlement. |
+| Accounting treatment | VPPAs may qualify for hedge accounting (ASC 815) if they meet effectiveness testing requirements. Without hedge accounting, mark-to-market gains/losses flow through the P&L, creating earnings volatility. Consult treasury and accounting early. |
+| Board / CFO approval | VPPAs are multi-year financial commitments. Most organizations require board approval for commitments >$10M notional or >10 years. Present as an energy cost management tool, not a speculative position. |
+
+### 2.3 Physical vs. Virtual PPA Decision Matrix
+
+| Factor | Favors Physical PPA | Favors Virtual PPA |
+|--------|-------------------|-------------------|
+| Load location | Same ISO as available projects | Load in regulated market or no nearby projects |
+| Energy supply | Need the physical energy (replacing utility supply) | Already have a retail supply contract |
+| Sustainability goal | Want bundled energy + RECs from a specific facility | Need RECs only for Scope 2 reporting |
+| Operational capability | Have energy scheduling and balancing resources | No energy trading or scheduling staff |
+| Balance sheet | Prefer to avoid financial derivative classification | Comfortable with ISDA and mark-to-market |
+| Credit profile | Sub-investment grade (physical may require less credit support) | Investment grade (can post collateral efficiently) |
+| Regulatory environment | Deregulated market with retail choice | Regulated market (VPPA may be the only option for additionality) |
+
+---
+
+## 3. Demand Charge Optimization
+
+### 3.1 Load Analysis Methodology
+
+**Step 1: Download 15-minute interval data.**
+Request a minimum of 12 months of 15-minute kW demand data from the utility or your
+meter data management system. For facilities with sub-metering, obtain interval data
+at the system level (HVAC, production, compressed air) in addition to the main meter.
+
+**Step 2: Identify peak demand intervals.**
+Sort all 15-minute intervals by kW descending. Focus on the top 50 intervals (the
+top 0.15% of all intervals in a year). These intervals drive your demand charges.
+
+**Step 3: Characterize peak drivers.**
+For each of the top 50 intervals, identify:
+- Date and time of day
+- Day of week
+- Outdoor temperature (proxy for HVAC load)
+- Production schedule (was the line running?)
+- Any anomalous events (equipment startup, testing, maintenance)
+
+**Typical findings for manufacturing facilities:**
+
+| Peak Driver | Frequency in Top 50 | Root Cause |
+|------------|---------------------|------------|
+| Morning ramp-up (6-9 AM) | 30-50% | Simultaneous startup of HVAC, compressors, and production lines |
+| Hot afternoon (2-5 PM) | 20-35% | HVAC at max coinciding with production peak |
+| Equipment startup after maintenance | 10-20% | Inrush current from large motors starting simultaneously |
+| Testing / commissioning | 5-10% | New equipment tested during peak periods |
+
+**Step 4: Calculate the demand charge cost of peak intervals.**
+
+```
+Monthly Demand Charge = Peak kW × Demand Rate ($/kW)
+
+If normal operating peak is 4,000 kW and the actual peak is 4,800 kW:
+Excess peak cost = (4,800 - 4,000) × $15/kW = $12,000/month
+
+With an 80% ratchet:
+Minimum billing demand for next 11 months = 4,800 × 0.80 = 3,840 kW
+If normal peak drops to 3,500 kW next month, you're still billed at 3,840 kW
+Annual ratchet cost = (3,840 - 3,500) × $15/kW × 11 months = $56,100
+```
+
+### 3.2 Peak Shaving ROI Framework
+
+#### Battery Energy Storage System (BESS)
+
+**Sizing methodology:**
+1. Determine the target peak reduction (kW to shave).
+2. Calculate the required energy capacity: target kW × duration of peak events.
+ For demand charge management, 1-2 hours of duration is typically sufficient.
+3. Apply round-trip efficiency (88-92% for lithium-ion): size the battery 10% larger
+ than the calculated energy requirement.
+
+**Example — 500 kW peak shaving at a manufacturing plant:**
+
+```
+Target reduction: 500 kW
+Peak event duration: 2 hours (based on interval data analysis)
+Battery size: 500 kW / 1,000 kWh (with 10% efficiency buffer: 500 kW / 1,100 kWh)
+
+Installed cost (2025): $800-$1,200/kWh for C&I BESS
+Total capital: $880,000-$1,320,000 (using 1,100 kWh at midpoint $1,000/kWh = $1,100,000)
+
+Annual savings stack:
+ Demand charge savings: 500 kW × $15/kW × 12 months = $90,000
+ Capacity tag reduction: 500 kW × $60/kW-yr (PJM example) = $30,000
+ TOU energy arbitrage: charge off-peak ($0.04/kWh), discharge on-peak ($0.08/kWh)
+ 1,100 kWh × $0.04/kWh spread × 250 days × 90% efficiency = $9,900
+ Demand response revenue: 500 kW × $40/kW-yr (PJM Economic DR) = $20,000
+
+Total annual value: $149,900
+Simple payback: $1,100,000 / $149,900 = 7.3 years
+With ITC (30% for standalone storage as of IRA): payback = $770,000 / $149,900 = 5.1 years
+```
+
+**Decision thresholds:**
+- Payback < 5 years (with stacked value + incentives): strong economic case, proceed
+- Payback 5-7 years: viable if aligned with sustainability goals or if demand charges are rising
+- Payback 7-10 years: marginal, requires additional strategic justification
+- Payback > 10 years: economics don't support investment without regulatory mandate
+
+#### Demand Response Program Evaluation
+
+Not all DR programs are equal. Evaluate on these dimensions:
+
+| Dimension | Questions to Answer |
+|-----------|-------------------|
+| Revenue certainty | Is payment capacity-based (guaranteed $/kW-yr) or performance-based (paid per curtailment event)? |
+| Dispatch frequency | How many events per year? What is the maximum duration? Can you sustain curtailment for the full duration? |
+| Baseline methodology | How is your curtailment measured? Customer Baseline Load (CBL) using 10-of-10 or adjusted methods? A poorly calculated baseline can understate your curtailment and reduce payments. |
+| Penalty for non-performance | What happens if you can't curtail during an event? Some programs impose penalties 2-3× the capacity payment. |
+| Interaction with other programs | Does DR enrollment affect your capacity tag calculation? Does it conflict with your behind-the-meter generation? |
+| Operational impact | Can your facility actually curtail the committed kW without affecting production quality, safety, or customer commitments? |
+
+### 3.3 Staggered Startup Protocol
+
+The single lowest-cost demand charge reduction strategy — no capital required:
+
+**Problem:** Morning startup creates a demand spike when HVAC, compressors, lighting,
+and production equipment all energize simultaneously between 5:30-6:30 AM.
+
+**Solution:** Stagger equipment startup over a 60-90 minute window:
+
+```
+5:00 AM — Lighting (50-100 kW)
+5:15 AM — HVAC pre-cooling/heating (500-800 kW, ramps over 30 min)
+5:45 AM — Compressed air system (200-400 kW, staged compressor starts)
+6:00 AM — Production Line 1 (300-500 kW)
+6:15 AM — Production Line 2 (300-500 kW)
+6:30 AM — Auxiliary systems, battery chargers, water heating
+
+Result: Peak during startup drops from 2,200 kW (simultaneous) to 1,600 kW (staggered)
+Savings: 600 kW × $15/kW × 12 months = $108,000/year at zero capital cost
+```
+
+**Implementation:** Program the building automation system (BAS) to enforce startup
+sequencing. Set hard interlocks that prevent the next system from starting until the
+prior system has reached steady state.
+
+---
+
+## 4. Market Analysis Framework
+
+### 4.1 Regulated vs. Deregulated Strategy Map
+
+| Your Situation | Primary Strategy | Secondary Strategy |
+|---------------|-----------------|-------------------|
+| Regulated market, single rate schedule | Demand charge management, on-site generation, tariff schedule optimization | Lobby for utility green tariff, evaluate community solar |
+| Regulated market, multiple rate options | Tariff analysis to select optimal schedule (TOU vs. flat vs. demand-based) | Load shifting to exploit TOU differentials |
+| Deregulated, single site | Competitive supply procurement (RFP to 5-8 REPs) | Layer procurement to manage timing risk |
+| Deregulated, multi-site same ISO | Aggregate sites for portfolio procurement (volume leverage) | Negotiate portfolio-level products (single supplier, blended rate) |
+| Deregulated, multi-site multi-ISO | Procure separately by ISO (market structures differ) | Leverage total volume in supplier negotiations even if contracts are separate |
+| Mixed regulated/deregulated portfolio | Competitive procurement for deregulated sites; demand management for regulated sites | Seek regulatory pilot programs in regulated territories |
+
+### 4.2 Forward Curve Analysis
+
+**What the forward curve tells you:**
+- Market consensus on future energy prices (adjusted for risk premium)
+- Seasonal price patterns (summer/winter spreads)
+- Year-over-year price trajectory (escalation or decline)
+
+**What the forward curve does NOT tell you:**
+- Actual future spot prices (forwards are not forecasts — they include a risk premium)
+- Short-term price spikes (forwards are averages, not tails)
+- Regulatory changes, plant retirements, or transmission additions not yet priced in
+
+**Using forward curves for procurement decisions:**
+
+| Forward Curve Position | Procurement Action |
+|-----------------------|-------------------|
+| Bottom 20% of 5-year range | Accelerate buying — lock more volume at favorable prices |
+| 20th-40th percentile | Proceed with scheduled layering — prices are reasonable |
+| 40th-60th percentile | Maintain default layering schedule |
+| 60th-80th percentile | Slow buying — defer non-critical tranches 30 days |
+| Top 20% of 5-year range | Defer where possible, increase index exposure, evaluate financial hedges instead of physical locks |
+
+### 4.3 Capacity Market Exposure
+
+In organized capacity markets (PJM, ISO-NE, NYISO), capacity charges are a significant
+cost component — $30–$120/kW-yr depending on the zone and auction results.
+
+**PJM Reliability Pricing Model (RPM):**
+- Auction held 3 years ahead of delivery year (Base Residual Auction)
+- Incremental auctions adjust quantities closer to delivery
+- Your capacity obligation is based on your PLC (Peak Load Contribution)
+- PLC is set by your metered load during the 5 highest system coincident peak hours (5CP) in the prior delivery year
+
+**Managing capacity exposure:**
+
+1. **Track PJM system peak alerts.** PJM issues "hot weather alerts" and "emergency alerts" when system peaks are expected. Curtail discretionary load during these hours to reduce your PLC for the following year.
+2. **Install peak notification systems.** Subscribe to PJM's demand response alerts. Deploy load curtailment controls that can drop 10-20% of facility load within 30 minutes of a peak alert.
+3. **Behind-the-meter generation.** Running backup generators during coincident peak hours reduces your metered load and thus your PLC. Ensure generators are permitted for non-emergency operation and emissions-compliant.
+4. **Capacity tag trading.** In some markets, capacity obligations can be traded or offset through financial instruments. Your supplier may offer capacity tag management as a service.
+
+**Example — capacity charge impact:**
+
+```
+Facility peak: 5,000 kW
+PLC (measured during prior year 5CP hours): 4,200 kW
+PJM BRA clearing price for your zone: $85/MW-day
+
+Annual capacity charge: 4,200 kW × $85/MW-day × 365 / 1,000 = $130,305/year
+
+If you had curtailed 500 kW during the 5CP hours:
+Reduced PLC: 3,700 kW
+Annual capacity charge: 3,700 kW × $85/MW-day × 365 / 1,000 = $114,793/year
+Savings: $15,512/year from 5 hours of load curtailment
+```
+
+---
+
+## 5. Hedging Strategy Design
+
+### 5.1 Hedging Instruments Available to C&I Buyers
+
+| Instrument | Complexity | Capital Required | Protection |
+|-----------|-----------|-----------------|------------|
+| Fixed-price contract (through REP) | Low | None (embedded in price) | Full price certainty for contracted volume |
+| Block purchases (through REP) | Low-Medium | None | Price certainty on base load; variable load exposed |
+| Financial swap (through broker/bank) | Medium | ISDA + possible margin | Converts floating price to fixed on specified volume |
+| Call option (through broker/bank) | Medium-High | Premium ($/MWh upfront) | Price ceiling at strike + premium; unlimited downside benefit retained |
+| Heat rate call option | High | Premium | Protects against gas-to-power price spike (useful when gas drives marginal power price) |
+| Collar (sell put, buy call) | Medium-High | Reduced premium (put proceeds offset call cost) | Ceiling and floor — limits both upside and downside |
+
+### 5.2 Hedging Strategy by Risk Profile
+
+| Risk Profile | Hedge Ratio | Instruments | Monitoring |
+|-------------|-------------|-------------|-----------|
+| Conservative (budget certainty paramount) | 80-95% hedged | Fixed-price contracts, financial swaps | Monthly mark-to-market review |
+| Moderate (balanced cost/risk) | 60-80% hedged | Block-and-index, layered procurement | Monthly forward curve review, quarterly hedge adjustment |
+| Aggressive (cost minimization focus) | 30-60% hedged | Index with call options for tail risk | Weekly market monitoring, daily during volatility events |
+| Speculative (never recommended for C&I) | <30% hedged | Index with no protection | Real-time monitoring (impractical for most C&I buyers) |
+
+### 5.3 Option Pricing and Evaluation
+
+When buying call options to cap index pricing exposure, evaluate:
+
+```
+Option value = Max(0, Spot Price - Strike Price) × Volume
+
+Cost: Premium per MWh × Contracted Volume
+Annual premium for a $50/MWh cap on day-ahead pricing: $2-5/MWh (varies by market volatility)
+
+Example — protecting 50,000 MWh annual index volume:
+ Call option strike: $50/MWh
+ Premium: $3/MWh
+ Total premium cost: $150,000/year
+
+ If spot averages $42/MWh: option expires worthless, total cost = $42 + $3 = $45/MWh
+ If spot averages $65/MWh: option pays $15/MWh, effective cost = $65 - $15 + $3 = $53/MWh
+ If spot spikes to $200/MWh (weather event): option pays $150/MWh, effective cap = $53/MWh
+
+ Maximum effective rate: strike + premium = $53/MWh regardless of market price
+```
+
+**When to use options vs. fixed contracts:**
+- Options when you want to participate in downside moves but protect against spikes
+- Fixed contracts when the premium for options exceeds the cost of just locking in a fixed price (this happens when volatility is high and options are expensive)
+
+---
+
+## 6. Sustainability Procurement Alignment
+
+### 6.1 Mapping Procurement to RE100 and SBTi
+
+**RE100 progress calculation:**
+
+```
+RE% = (Renewable MWh procured) / (Total electricity consumption MWh) × 100
+
+Acceptable renewable MWh sources (in order of additionality):
+1. On-site generation (strongest claim)
+2. Physical PPA with new project (strong additionality)
+3. Virtual PPA with RECs from new project (good additionality)
+4. Utility green tariff (varies by program design)
+5. Unbundled RECs (weakest claim — RE100 tightening requirements)
+```
+
+**SBTi trajectory alignment:**
+- SBTi requires absolute Scope 2 emissions reductions on a defined trajectory (typically 4.2%/year for 1.5°C alignment).
+- Lock in long-term renewable procurement (PPAs) that deliver emission reductions year over year.
+- Avoid procurement strategies that increase fossil dependence (long-term fixed contracts with fossil-heavy grid mix and no REC component).
+
+### 6.2 Cost-Effective Sustainability Procurement Path
+
+| Target RE% | Least-Cost Strategy |
+|-----------|-------------------|
+| 0-25% | Unbundled national wind RECs ($1-3/MWh). Cheapest entry point. |
+| 25-50% | Utility green tariff + unbundled RECs. Green tariffs are often $0.005-$0.015/kWh premium. |
+| 50-75% | VPPA with new wind/solar project. Fixed cost, long-term REC supply, additionality. |
+| 75-90% | Physical PPA or additional VPPA to cover remaining gap. On-site solar where feasible. |
+| 90-100% | Match remaining unhedged load with project-specific RECs or small on-site installations. The last 10% is the most expensive per MWh. |
+
+---
+
+## 7. Multi-Facility Portfolio Optimization
+
+### 7.1 Portfolio Aggregation Strategy
+
+**When to aggregate:**
+- 3+ sites in the same ISO/utility territory
+- Total volume > 20 GWh/year (attracts competitive supplier attention)
+- Sites have complementary load profiles (some peak summer, others peak winter)
+
+**Aggregation benefits:**
+- Volume leverage: 5-15% lower supply pricing than individual site procurement
+- Load diversity: combined portfolio has higher load factor than individual sites, reducing supplier risk premium
+- Administrative efficiency: single contract, single invoice, single relationship
+
+**When NOT to aggregate:**
+- Sites in different ISOs with different market structures (PJM and ERCOT should be procured separately)
+- One site has unique requirements (e.g., real-time pricing needed for a demand response strategy) that would constrain the entire portfolio
+- Sites have vastly different contract expiration dates (stagger expirations to avoid all-at-once recontracting risk)
+
+### 7.2 Portfolio-Level Risk Metrics
+
+Track at the portfolio level, not just site-by-site:
+
+| Metric | Formula | Target |
+|--------|---------|--------|
+| Portfolio hedge ratio | (Hedged MWh / Total expected MWh) × 100 | 60-80% |
+| Weighted average procurement price | Σ(site MWh × site $/MWh) / Total MWh | Within 5% of portfolio benchmark |
+| Supplier concentration | Largest supplier MWh / Total MWh | <50% (avoid single-supplier dependence) |
+| Contract expiration clustering | % of portfolio MWh expiring in any 12-month period | <40% (stagger expirations) |
+| Renewable coverage | Renewable MWh / Total MWh | On track to target |
+| Portfolio load factor | Total kWh / (Sum of site peak kW × hours) | Track trend, higher is better |
+
+### 7.3 Site Prioritization for Demand-Side Investment
+
+With limited capital for demand charge mitigation, prioritize sites using this scoring model:
+
+| Factor | Weight | Scoring |
+|--------|--------|---------|
+| Demand charges as % of total bill | 30% | >35% = 100, 25-35% = 70, 15-25% = 40, <15% = 10 |
+| Peak-to-average ratio | 25% | >2.5 = 100, 2.0-2.5 = 70, 1.5-2.0 = 40, <1.5 = 10 |
+| Available demand reduction (kW) | 20% | >1000 kW = 100, 500-1000 = 70, 200-500 = 40, <200 = 10 |
+| Utility demand rate ($/kW) | 15% | >$20 = 100, $15-$20 = 70, $10-$15 = 40, <$10 = 10 |
+| Capacity market exposure | 10% | PJM/ISO-NE (high) = 100, NYISO = 70, MISO = 40, none = 0 |
+
+**Investment priority: highest composite score first.** A site scoring >80 is a strong
+candidate for battery storage or demand response. A site scoring <40 has limited
+demand charge optimization potential — focus on supply-side procurement instead.
+
+---
+
+## 8. Natural Gas Procurement
+
+### 8.1 Gas Procurement Structures
+
+Natural gas procurement for C&I consumers (boilers, CHP, process heat, backup generation)
+follows similar principles to electricity but with distinct market mechanics.
+
+| Structure | Description | Best For |
+|-----------|-------------|----------|
+| Firm fixed-price | Locked $/therm or $/MMBtu for contract term | Budget certainty, large heating loads |
+| Index (first-of-month) | Monthly NYMEX Henry Hub settlement + basis + adder | Cost optimization, risk-tolerant buyers |
+| Index (daily) | Daily Gas Daily midpoint + basis + adder | High-flexibility loads, interruptible processes |
+| Baseload block + index | Fixed block covers base heating/process load, index covers variable | Facilities with both base process heat and weather-variable HVAC |
+| Swing contract | Volume flexibility (50-130% of nominated quantity) | Facilities with highly variable gas consumption |
+
+### 8.2 Basis Differentials for Natural Gas
+
+Natural gas prices vary by delivery point. Henry Hub (Louisiana) is the benchmark,
+but delivered cost depends on the basis differential between Henry Hub and your
+local city gate or utility delivery point.
+
+**Common basis differentials (approximate):**
+
+| Delivery Point | Typical Basis to Henry Hub | Driver |
+|---------------|--------------------------|--------|
+| Chicago (NGPL Midcontinent) | -$0.10 to +$0.15/MMBtu | Pipeline capacity from Gulf to Midwest |
+| New York (Transco Zone 6 NY) | +$0.50 to +$3.00/MMBtu | Winter constraint on pipelines into NYC |
+| New England (Algonquin) | +$1.00 to +$8.00/MMBtu (winter) | Severe pipeline constraints, competes with LNG |
+| California (SoCal Border) | -$0.50 to +$1.50/MMBtu | Varies with West Coast supply/demand |
+| Appalachia (Dominion South) | -$1.50 to -$0.30/MMBtu | Oversupply from Marcellus shale production |
+| Texas (HSC) | -$0.05 to +$0.20/MMBtu | Close to production, minimal basis |
+
+**Key insight:** A facility in New England on index pricing faces dramatically different
+winter risk than a facility in Texas. Basis in New England during a cold snap can
+exceed $15/MMBtu, tripling the delivered gas cost. New England gas procurement
+requires winter hedging with firm pipeline capacity or LNG backup — index pricing
+without protection is reckless in that market.
+
+### 8.3 Gas-Electric Interdependency
+
+For facilities with both electricity and natural gas loads, recognize the coupling:
+
+- **When gas prices spike, electricity prices spike.** Natural gas is the marginal fuel
+ for electricity generation in most US ISOs. A $2/MMBtu increase in Henry Hub
+ translates to approximately $10-$15/MWh increase in wholesale electricity prices
+ (depending on the average heat rate of marginal gas plants, typically 7,000-8,000 BTU/kWh).
+
+- **CHP economics are gas-price dependent.** A CHP system generating electricity at
+ a heat rate of 6,500 BTU/kWh has a fuel cost of $6.50 × gas price per MWh. At gas
+ $3/MMBtu, generation cost is $19.50/MWh. At gas $8/MMBtu, generation cost is
+ $52/MWh. If your grid electricity cost exceeds your CHP generation cost, run the
+ CHP. If grid electricity drops below CHP cost (e.g., during spring shoulder months
+ with mild weather and low grid demand), consider shutting down CHP and buying
+ from the grid.
+
+- **Dual-fuel hedging:** When hedging gas and electricity simultaneously, recognize
+ that fixing gas costs and leaving electricity at index (or vice versa) creates a
+ cross-commodity basis risk. If gas prices drop but electricity stays high (due to
+ transmission constraints or non-gas generation tightness), your gas hedge
+ underperforms while your electric bill remains high. Consider hedging both
+ commodities on a correlated basis — many energy suppliers offer combined
+ gas+electric portfolio management.
+
+---
+
+## 9. Tariff Optimization in Regulated Markets
+
+### 9.1 Rate Schedule Selection
+
+In regulated markets, the available tariff options may seem limited, but switching
+between rate schedules can save 5-15% on the total bill without changing consumption.
+
+**Step 1: Identify available rate schedules for your demand level and voltage.**
+Most utilities offer 2-4 rate options for large C&I customers:
+- Standard demand rate (flat energy + demand charge)
+- Time-of-use rate (lower off-peak energy, higher on-peak energy + demand)
+- Real-time pricing pilot (if available)
+- Interruptible service rate (lower cost, utility can curtail during emergencies)
+
+**Step 2: Model 12 months of actual interval data against each available rate schedule.**
+
+```
+For each rate schedule:
+ Monthly cost = Σ(energy_charge_component) + demand_charge + customer_charge + riders
+
+Where:
+ energy_charge_component = Σ(kWh_per_interval × applicable_rate_per_kWh)
+ demand_charge = max(15-min kW interval in month) × demand_rate
+ For TOU rates: separate on-peak demand charge may apply
+```
+
+**Step 3: Compare annual totals.**
+
+| Rate Schedule | Annual Energy | Annual Demand | Annual Fixed | Annual Total | vs. Current |
+|--------------|--------------|---------------|-------------|-------------|-------------|
+| Current (GS-3) | $580,000 | $312,000 | $24,000 | $916,000 | baseline |
+| TOU (GS-3-TOU) | $545,000 | $298,000 | $24,000 | $867,000 | -$49,000 (-5.3%) |
+| RTP pilot | $510,000 | $312,000 | $36,000 | $858,000 | -$58,000 (-6.3%) |
+| Interruptible | $565,000 | $250,000 | $24,000 | $839,000 | -$77,000 (-8.4%) |
+
+**Step 4: Evaluate non-financial factors.**
+- TOU: requires ability to shift load or accept higher on-peak costs
+- RTP: requires market monitoring and tolerance for price volatility
+- Interruptible: requires ability to curtail load on short notice (typically 30-60 min)
+
+### 9.2 Rate Case Monitoring and Response
+
+**When to intervene in a rate case:**
+
+| Impact Level | Annual Cost Increase | Recommended Action |
+|-------------|---------------------|-------------------|
+| <$50K | Negligible for large C&I | Monitor only — track filing through settlement |
+| $50K-$200K | Material but not critical | Join existing intervenor group (OIEC, etc.) |
+| $200K-$500K | Significant | Individual intervention with regulatory counsel |
+| >$500K | Critical | Full intervention with expert witnesses, rate design testimony |
+
+**Rate case timeline (typical):**
+
+```
+Month 0: Utility files rate case with state PUC
+Month 1-2: Intervenors file to participate
+Month 3-4: Discovery (interrogatories, data requests to utility)
+Month 5-7: Intervenor testimony filed
+Month 8-9: Hearings
+Month 10-12: PUC issues order
+Month 13-15: New rates take effect (may be retroactive to filing date)
+```
+
+**What to challenge in a rate case:**
+1. **Rate of return on equity (ROE):** Utilities typically request 10-11% ROE. Current
+ authorized ROEs are trending down (9-10%). Challenge excessive ROE requests.
+2. **Rate base additions:** Utilities earn their ROE on their rate base (invested capital).
+ Challenge excessive or imprudent capital investments included in the rate base.
+3. **Cost allocation between rate classes:** Utilities allocate total revenue
+ requirement across residential, commercial, and industrial rate classes. Ensure your
+ rate class is not subsidizing residential or other classes above cost causation.
+4. **Rate design:** Even if the total revenue is approved, fight for demand-based rate
+ design (rewards load factor management) rather than pure volumetric rates (punishes
+ high-consumption customers regardless of load shape).
+
+---
+
+## 10. Emergency Procurement Protocols
+
+### 10.1 Supplier Default / Bankruptcy
+
+If your retail energy provider files for bankruptcy or fails to perform:
+
+**Immediate actions (24-48 hours):**
+1. Verify your account status with the utility. If the supplier defaults, your
+ account reverts to the utility's Provider of Last Resort (POLR) service or standard
+ offer service. You will NOT lose power — the grid keeps delivering regardless of
+ supplier status.
+2. Determine the POLR rate. In most states, the POLR rate is set quarterly based on
+ wholesale market prices plus a premium (10-20% above competitive supply). This may
+ be higher or lower than your current contract rate.
+3. Contact 2-3 alternative suppliers immediately. Explain the situation — they will
+ offer expedited enrollment (5-10 business days vs. normal 30-60 day switch process).
+4. Review your contract for supplier default provisions, including any deposits or
+ prepayments that may be at risk in the bankruptcy estate.
+
+**Medium-term (2-4 weeks):**
+1. Execute a new supply contract with the best available alternative supplier.
+2. File a claim in the bankruptcy proceeding for any prepayments, deposits, or damages.
+3. Review your supplier qualification criteria — consider adding financial covenants
+ (minimum credit rating, tangible net worth requirements) to future contracts.
+
+### 10.2 Force Majeure Events
+
+When a force majeure event (natural disaster, grid emergency, pandemic) disrupts
+your energy supply or operations:
+
+**Assessment framework:**
+
+| Event Type | Energy Impact | Procurement Response |
+|-----------|--------------|---------------------|
+| Hurricane/severe weather | Physical damage to generation/T&D, price spikes | Activate backup generation, curtail non-essential load, document for insurance |
+| Grid emergency (EEA3) | Rolling blackouts, extreme prices | Maximum load curtailment, DR activation, generator deployment |
+| Supplier force majeure claim | Supplier attempts to suspend contract | Review FM clause narrowly — "market price increase" is NOT force majeure; "physical inability to deliver" may be |
+| Pandemic/operational shutdown | Facility closed, consumption drops dramatically | Invoke volume tolerance provisions, negotiate contract suspension, evaluate early termination |
+
+### 10.3 Contract Termination Decision Matrix
+
+When evaluating whether to terminate a supply contract early:
+
+```
+Early Termination Fee (ETF) = Σ(remaining months × monthly volume × |contract price - current market price|)
+
+If contract price > current market:
+ You owe the supplier (you're paying above market)
+ ETF = remaining months × volume × (contract price - market) × discount factor
+
+If contract price < current market:
+ Supplier owes you (you have a favorable contract)
+ You would NOT terminate — the contract is in-the-money
+
+Decision: Terminate if ETF < cumulative savings from alternative contract + risk reduction value
+```
+
+**Example — mid-term exit evaluation:**
+
+```
+Current contract: $0.062/kWh, 18 months remaining, 50 GWh remaining
+Current market: $0.055/kWh (market has dropped since contract signing)
+ETF: 50,000 MWh × ($0.062 - $0.055) = $350,000
+
+Alternative contract: $0.054/kWh for 18 months
+Savings from alternative: 50,000 MWh × ($0.062 - $0.054) = $400,000
+
+Net benefit of termination: $400,000 savings - $350,000 ETF = $50,000
+
+Decision: Marginal. Factor in:
+ - Renegotiation risk (can you lock $0.054 before market moves?)
+ - Administrative cost of switching suppliers
+ - Relationship cost with current supplier
+ - If net benefit < $100K, generally not worth the disruption
+```
+
+---
+
+## 11. Seasonal Procurement Calendar
+
+A disciplined procurement calendar ensures no critical deadlines are missed and
+procurement activities align with market conditions.
+
+| Month | Activity | Deadline |
+|-------|----------|----------|
+| January | Annual energy budget review, lock natural gas hedges for next winter | Jan 31 for winter gas |
+| February | Q1 forward curve review, PPA pipeline assessment | — |
+| March | Begin RFP preparation for contracts expiring in Q4 or Q1 next year | — |
+| April | Issue RFPs for fall contract starts, review summer DR enrollment | Apr 15 for PJM DR enrollment |
+| May | Evaluate bids, begin summer peak preparation (generator testing, BAS settings) | May 31 for summer rate elections |
+| June | Summer peak demand management begins, monitor 5CP forecasts (PJM) | — |
+| July | Peak season monitoring, execute Q3 procurement tranches | Jul 15 for ERCOT 4CP mgmt |
+| August | Peak season monitoring, finalize fall contract awards | Aug 31 for ISO-NE FCA positions |
+| September | Post-summer review, capacity tag assessment, RE100 progress check | Sep 30 for Q4 procurement |
+| October | Begin winter gas hedging, review heating load forecasts | Oct 31 for winter gas locks |
+| November | Budget season — prepare next year's energy cost forecast | Nov 15 for budget submission |
+| December | Year-end RE100 reconciliation, REC inventory check, contract renewals | Dec 31 for REC vintage retirement |
diff --git a/web-app/public/skills/energy-procurement/references/edge-cases.md b/web-app/public/skills/energy-procurement/references/edge-cases.md
new file mode 100644
index 00000000..53a9d55e
--- /dev/null
+++ b/web-app/public/skills/energy-procurement/references/edge-cases.md
@@ -0,0 +1,624 @@
+# Energy Procurement — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex energy procurement situations that don't resolve through standard decision frameworks.
+
+These edge cases represent the scenarios that separate experienced energy procurement managers from everyone else. Each involves competing priorities, market structure nuances, regulatory complexity, and real financial exposure. They are structured to guide resolution when standard procurement playbooks break down.
+
+---
+
+## How to Use This File
+
+When an energy procurement situation doesn't fit a clean decision tree — when market dynamics create conflicting incentives, when tariff structures produce counterintuitive outcomes, or when a PPA that looked good at signing turns problematic — find the edge case below that most closely matches the situation. Follow the expert approach step by step.
+
+---
+
+### Edge Case 1: ERCOT Price Spike During Extreme Winter Weather (Uri-Type Event)
+
+**Situation:**
+A food manufacturing company operates two facilities in Texas: a 6 MW production plant in Houston and a 3 MW distribution center in Dallas. Both are on index-priced supply contracts (ERCOT real-time settlement node price + $0.004/kWh supplier adder). During a February polar vortex event, temperatures drop to 5°F in Houston (normal February low: 42°F). ERCOT declares an Energy Emergency Alert Level 3 (EEA3) and implements rolling blackouts. Real-time wholesale prices hit the ERCOT system-wide offer cap of $5,000/MWh (during Uri in 2021, the cap was $9,000/MWh). The event lasts 5 days. The Houston plant has backup natural gas generators but cannot run them because natural gas supply has been curtailed due to wellhead freeze-offs. The Dallas facility has no backup generation.
+
+Your weekly energy cost is normally $85,000 across both sites. During this event, the projected weekly cost at $5,000/MWh average for 120 hours of peak pricing would exceed $4.5M.
+
+**Why It's Tricky:**
+The contract is working as designed — index pricing means you pay the market price. There is no breach, no force majeure claim against the supplier (they are delivering at index), and no contractual price cap unless you negotiated one. The financial exposure is catastrophic for a company where annual energy spend is $5M. A single week could equal the entire annual budget.
+
+Simultaneously, you need to keep the food production plant running (product in process will spoil if power is lost) and the distribution center must maintain cold chain for $8M of perishable inventory. Shutting down to reduce energy cost means accepting $3–$5M in product loss.
+
+**Common Mistake:**
+Keeping both facilities at full load throughout the event and accepting the $4.5M bill as a cost of doing business. The second mistake: attempting to renegotiate or dispute the contract after the event — courts consistently enforce index pricing during price spikes because that is the contract structure.
+
+**Expert Approach:**
+1. **Immediate load curtailment (Hour 0-4):** Reduce all discretionary load at both facilities. Target: 30-40% load reduction without shutting production lines. Turn off office HVAC (employees can layer up for a week), reduce warehouse lighting to emergency levels, shut down non-essential compressed air (only keep production-critical compressors), and turn off electric water heaters. A 35% load reduction on 9 MW combined peak saves approximately $1.6M over 5 days at $5,000/MWh.
+
+2. **Production schedule modification (Hour 4-12):** Shift production to overnight hours (10 PM - 6 AM) when prices typically dip to $1,000-$2,000/MWh even during extreme events (the sun isn't up, wind may be producing, and some thermal generation returns overnight). Run the Houston plant at minimum load during daytime peak hours (keep product in process alive but don't start new batches).
+
+3. **Demand response activation (Hour 0):** If enrolled in any ERCOT demand response program (ERS or 4CP programs), curtail to earn the event payment. This partially offsets the extreme energy cost. An ERS enrollment for 1 MW could pay $2,000-$5,000 per event hour depending on the program.
+
+4. **Generator options (Hour 2-6):** Contact your natural gas supplier and pipeline operator about gas availability. If pipeline gas is curtailed, evaluate diesel portable generators — rental generators during extreme weather events cost $50-$100/kW per day but at $5,000/MWh wholesale, generation cost at even $150/kW/day is far cheaper than grid power. Contact industrial generator rental companies immediately — they will be overwhelmed within 24 hours.
+
+5. **Supplier communication (Hour 0):** Contact your retail energy provider to understand their exposure and settlement timeline. Some REPs offer post-event payment plans. If your REP is likely to fail (several REPs went bankrupt after Uri), your account reverts to the utility's Provider of Last Resort (POLR) rate — which during an emergency may be even higher. Prepare for this contingency.
+
+6. **Post-event restructuring (Week 2+):** After the event, restructure your energy contracts. For ERCOT exposure, never go fully unhedged into winter. Options include:
+ - Add a price cap to your index contract ($100-$200/MWh ceiling, costs $2-$5/MWh in premium)
+ - Switch to block-and-index with blocks covering 80% of winter load
+ - Purchase OTC call options that cap your exposure above a strike price
+ - Maintain a cash reserve equal to 2 weeks of energy cost at $500/MWh
+
+**Key Indicators:**
+- ERCOT weather forecasts showing temperatures >20°F below seasonal norms for >3 days warrant pre-event hedging action
+- Natural gas spot prices at Houston Ship Channel exceeding $10/MMBtu signal potential generator fuel supply issues
+- ERCOT Conservation Voltage Reduction or EEA Level 1 declarations are early warnings — act before EEA3
+- Monitor ERCOT's generation outage report: if forced outages exceed 20 GW, price spikes above $1,000/MWh are likely
+
+**Documentation Required:**
+- Real-time price records from the ISO settlement system
+- Facility load data during the event (to demonstrate curtailment efforts for internal reporting and potential rate dispute)
+- Generator rental invoices and fuel costs
+- Communication log with REP and utility
+- Total financial exposure calculation for executive and board reporting
+- Post-event contract restructuring analysis
+
+**Resolution Timeline:**
+- Hours 0-6: Implement all immediate load curtailment measures
+- Hours 6-24: Execute production schedule shifts, secure backup generation if available
+- Days 2-5: Maintain curtailed operations, monitor market for normalization signals
+- Week 2: Receive preliminary settlement from REP, assess total financial impact
+- Week 3-4: Initiate contract restructuring discussions with REP
+- Month 2-3: Execute new contract structure with winter price protection
+
+---
+
+### Edge Case 2: Virtual PPA Basis Risk in a Congested Transmission Zone
+
+**Situation:**
+A technology company headquartered in Northern Virginia (PJM territory, Dominion zone) executed a 15-year VPPA with a 100 MW wind farm in western PJM (AEP zone, near the Ohio-West Virginia border). The VPPA strike price is $32/MWh, which at signing was $12/MWh below the PJM Western Hub forward curve of $44/MWh. The company projected $1.2M/year in positive settlement value, plus 350,000 RECs annually for their RE100 commitment.
+
+After 18 months of operation, the actual financial performance shows persistent negative settlements. The wind farm generates during overnight and shoulder hours when AEP zone LMPs average $28/MWh. The company's load zone (Dominion) averages $48/MWh during the same hours due to transmission congestion between AEP and Dominion zones. The generation-weighted average basis (Dominion LMP minus AEP node LMP) is $14/MWh.
+
+Net financial impact: the wind farm settles at $28/MWh average, which is $4/MWh below the $32 strike, meaning the company owes the developer $4/MWh. Plus the $14/MWh basis spread means the company's effective energy cost premium from the VPPA is $18/MWh — turning a projected $1.2M/year benefit into a $2.1M/year cost.
+
+**Why It's Tricky:**
+The VPPA contract is performing as written — the settlement is based on the generator's node price, not the company's load zone price. Basis risk was disclosed during contracting, but the company's internal projection used a 3-year historical average basis of $6/MWh (which was correct at the time). The basis widened due to new generation additions in AEP zone and continued transmission constraints into the Dominion zone — structural factors that will likely persist or worsen.
+
+The company cannot exit the VPPA without paying a termination fee based on the mark-to-market value, which at negative $2.1M/year for the remaining 13.5 years, discounted at 8%, is approximately $16M. The RECs are still valuable — 350,000 RECs at $5/REC = $1.75M/year — partially offsetting the financial loss, but the net economics are negative.
+
+**Common Mistake:**
+Terminating the VPPA immediately and paying the $16M termination fee. This crystallizes the loss. The second mistake: ignoring the problem and hoping basis narrows — structural congestion rarely self-corrects without transmission investment.
+
+**Expert Approach:**
+1. **Quantify the actual basis exposure.** Request hourly settlement data from the PPA counterparty. Calculate generation-weighted basis for each month. Identify whether basis is seasonal (wider in summer when AC load drives Dominion congestion) or persistent year-round.
+
+2. **Model forward basis expectations.** Engage an energy consultant or your supplier's market analytics team to model forward basis between AEP and Dominion zones. Key factors: planned transmission upgrades (PJM RTEP projects that relieve the constraint), new generation additions in AEP zone (more wind/solar behind the constraint worsens basis), and load growth in Dominion zone.
+
+3. **Evaluate basis hedging.** PJM offers Financial Transmission Rights (FTRs) that can hedge congestion costs between two points on the grid. Purchase FTRs from the AEP zone to the Dominion zone in the PJM FTR auction. An FTR paying $10/MWh on 350,000 MWh = $3.5M/year, which significantly offsets the basis loss. FTR costs vary — the auction determines the price, and popular paths (like AEP-to-Dominion) may be expensive. Budget $5-$8/MWh for FTR basis hedging.
+
+4. **Renegotiate the settlement point.** Approach the developer about switching the settlement point from the generator's node to the Western Hub or a more liquid hub closer to your load zone. The developer may accept this if the hub price is close to their node price (it often is — hub prices are less volatile than nodal prices). This doesn't eliminate basis risk but may reduce it.
+
+5. **Restructure the contract.** Options include:
+ - Reduce the contract volume (buy down from 100 MW to 60 MW, reducing exposure while keeping some REC delivery)
+ - Add a basis risk sharing mechanism (developer absorbs basis beyond $8/MWh)
+ - Convert to a fixed-price REC purchase (eliminate the energy settlement entirely, pay a fixed $/REC)
+
+6. **Portfolio-level offset.** If you have other facilities in the AEP zone, the VPPA's node-price settlement is actually favorable for loads in that zone (where LMPs are lower). Consider whether any current or planned facility expansion in AEP territory could benefit from the VPPA's economics.
+
+**Key Indicators:**
+- Basis widening beyond 150% of historical average for 2+ consecutive quarters signals structural change
+- PJM RTEP transmission projects targeting the constrained corridor may take 5-7 years to complete
+- New generation interconnection queue in the generator's zone exceeding 3 GW is a bearish signal for basis
+- FTR auction results showing increasing clearing prices on the relevant path confirm market recognition of the congestion
+
+**Documentation Required:**
+- Monthly VPPA settlement statements
+- Hourly generation-weighted basis calculations
+- FTR auction results and cost analysis
+- Developer communication regarding contract restructuring
+- Board-level financial exposure report
+- Revised forward-looking PPA valuation under multiple basis scenarios
+
+---
+
+### Edge Case 3: Demand Charge Ratchet Trap After Equipment Installation
+
+**Situation:**
+A plastics manufacturer in Georgia Power territory installed a new 1,200 kW production line. During commissioning week, the electrical contractor tested all equipment simultaneously at full load — standard practice for commissioning acceptance testing. The test occurred on a Wednesday afternoon in August, coinciding with the facility's normal summer HVAC peak. The 15-minute interval data shows a peak demand of 5,800 kW — compared to the facility's normal summer peak of 4,200 kW.
+
+Georgia Power's PLM-4 tariff includes an 80% demand ratchet. The billing demand for the next 11 months cannot fall below 80% of the maximum demand in the prior 11 months. The new floor: 5,800 × 0.80 = 4,640 kW. During winter months, when normal demand drops to 3,200 kW, the facility will be billed for 4,640 kW.
+
+Additional demand charges: (4,640 - 3,200) × $12.50/kW × 7 winter months = $126,000 in excess demand charges. And the new production line's normal operating demand of 900 kW (not the 1,200 kW commissioning peak) means the facility's normal summer peak going forward is 5,100 kW — still below the ratchet. Even in summer, the facility is billed for 5,800 kW peak demand.
+
+Annual excess demand charges from the commissioning peak: approximately $174,000.
+
+**Why It's Tricky:**
+The damage is done — a single 15-minute interval set the peak, and the ratchet clause is contractual. Georgia Power has no tariff provision for removing ratcheted demand due to commissioning events. You cannot dispute the meter reading (the test genuinely drew 5,800 kW). The only way to "reset" the ratchet is to either (a) wait 11 months for the peak to roll off, or (b) consistently hit a higher peak that makes the ratchet irrelevant (which would mean higher demand charges anyway).
+
+**Common Mistake:**
+Calling Georgia Power and asking them to waive the ratchet. They won't — it's a tariff provision approved by the Georgia Public Service Commission, not a negotiable contract term. The second mistake: assuming nothing can be done and absorbing the $174K cost.
+
+**Expert Approach:**
+1. **Immediate investigation (Day 1):** Pull the interval data for commissioning week. Identify the exact 15-minute interval(s) that set the new peak. Determine whether the peak was caused by legitimate commissioning (all equipment at rated load) or by an avoidable event (existing HVAC running at maximum while new equipment was at full test load).
+
+2. **Tariff analysis:** Review the PLM-4 tariff document line-by-line. Some tariffs have provisions for "temporary service" or "construction power" that could apply if the commissioning load was billed under a temporary service agreement. If the contractor should have been on temporary service during commissioning, the peak may not count against the permanent meter. This is rare but worth checking.
+
+3. **Demand response enrollment:** Georgia Power offers demand response programs that can provide credit against demand charges. If the facility can commit to curtailing 800-1,000 kW during summer peak events, the DR credit may offset a significant portion of the ratchet cost. Enroll immediately — programs have seasonal enrollment windows.
+
+4. **Operational changes to reduce the ratchet impact:** Since the ratchet is based on the single highest 15-minute interval, focus on ensuring that the facility NEVER exceeds 5,800 kW again (which would reset the ratchet at a higher level). Install a demand controller on the main meter that sheds non-critical loads (compressed air, water heating, battery chargers) whenever demand approaches 5,500 kW.
+
+5. **Future prevention protocol:** Establish a policy that all equipment commissioning involving loads >200 kW must be scheduled during off-peak hours (overnight or weekends), with the building HVAC in setback mode and non-essential production loads off. The commissioning electrician should coordinate with the energy manager, not just the maintenance supervisor. Include this requirement in all future capital project specifications.
+
+6. **Financial recovery:** If the electrical contractor failed to follow a commissioning plan that specified load management during testing, evaluate whether the excess demand charges ($174K) are recoverable as consequential damages under the construction contract. Review the contract's commissioning provisions and liability clauses.
+
+**Key Indicators:**
+- Any planned equipment installation >200 kW capacity should trigger a commissioning demand management plan
+- Request interval data within 48 hours of commissioning to identify ratchet exposure before the billing cycle closes
+- If your tariff has a demand ratchet, the energy manager must be involved in all capital project commissioning plans
+
+---
+
+### Edge Case 4: Utility Rate Case Filing Mid-Contract
+
+**Situation:**
+A hospital system with 12 facilities in Ohio (AEP Ohio territory) has a 36-month fixed-price electricity supply contract with a competitive retail energy provider at $0.052/kWh for the energy component. The contract was signed 8 months ago. AEP Ohio has just filed a distribution rate case with the Public Utilities Commission of Ohio (PUCO), proposing a $480M revenue increase across all rate classes — an average 18% increase in distribution charges.
+
+For the hospital system's rate class (GS-3 General Service-Large), the proposed increase translates to approximately $0.014/kWh in additional distribution charges. Across the hospital system's 180 GWh annual consumption, the annual cost increase would be approximately $2.52M. The current total delivered cost is $0.088/kWh; the proposed distribution increase would raise it to $0.102/kWh — a 16% total cost increase.
+
+The fixed-price supply contract covers only the energy and capacity components ($0.052/kWh). Distribution charges, transmission charges, riders, and surcharges are pass-through items — the hospital system pays whatever the utility tariff dictates.
+
+**Why It's Tricky:**
+The supply contract is performing as agreed. The $0.052/kWh energy price is locked. But the total delivered cost is increasing by $2.52M/year, and the hospital system's CFO expected the "fixed-price contract" to provide budget certainty on the total energy bill. The disconnect between "supply is fixed" and "delivery is pass-through" is one of the most common misunderstandings in commercial energy procurement.
+
+The rate case will take 12-18 months to adjudicate. The proposed $0.014/kWh increase is the utility's opening position — the final settlement typically lands at 50-75% of the proposed increase. But even a 50% outcome ($0.007/kWh) means $1.26M/year in additional costs.
+
+**Common Mistake:**
+Ignoring the rate case because "we have a fixed-price contract" and only discovering the cost increase when the new tariff rates take effect. The second mistake: blaming the energy supplier for not protecting against distribution rate increases — the supplier explicitly passes these through in the contract, and there is no commercial product that can fix distribution rates (these are regulated, not competitive).
+
+**Expert Approach:**
+1. **Rate case analysis (Week 1):** Obtain the full rate case filing from the PUCO docket. Focus on the cost of service study for the GS-3 rate class. Identify what specific distribution cost components are driving the increase (infrastructure replacement, storm hardening, grid modernization, rate of return request). Calculate the exact impact on each hospital facility based on their billing determinants.
+
+2. **Intervention evaluation (Week 2-3):** Large C&I customers have the right to intervene in rate cases. Intervention allows you to file testimony challenging the utility's cost allocation, rate design, or revenue requirement. The hospital system's $2.5M+ annual impact justifies the cost of intervention ($50K-$150K in legal and expert witness fees). Contact a utility regulatory attorney in Ohio.
+
+3. **Coalition building (Week 2-4):** Join the Ohio Industrial Energy Consumers (OIEC) or similar industrial intervenor group. These organizations pool resources to intervene in rate cases, reducing individual company costs to $10K-$30K/year in membership fees while providing professional regulatory representation.
+
+4. **Rate design advocacy:** Even if the total revenue increase is approved, the rate design (how the revenue is allocated across rate classes and billing determinants) can be influenced. Advocate for cost allocation that reflects actual cost causation — hospitals with high load factors and coincident peak management should pay less per kWh in distribution than low-load-factor commercial buildings. File testimony supporting demand-based distribution rates rather than volumetric rates.
+
+5. **Budget adjustment (Month 1):** Present the rate case exposure to the hospital system's CFO immediately. Provide three scenarios: full proposed increase ($2.52M/year), likely settlement (60% = $1.51M/year), and best case (40% = $1.01M/year). Recommend budgeting at the likely scenario and establishing a reserve for the upside case. The rate case outcome is 12-18 months away, but budget planning should begin immediately.
+
+6. **Demand-side response:** A rate case that increases distribution charges makes demand charge management more valuable. Every kW of peak reduction now saves more per month. Re-run the ROI analysis for battery storage, demand response, and load management projects with the proposed new rates — projects that were marginal at old rates may now have strong payback.
+
+**Key Indicators:**
+- Monitor your state PUC docket for utility rate case filings quarterly
+- Track the authorized rate of return — utilities filing for ROE >10% in the current interest rate environment will face pushback
+- Rate cases proposing >15% overall increases typically settle at 50-65% of the request
+- Infrastructure replacement riders often bypass rate case proceedings — monitor these separately
+
+**Documentation Required:**
+- Rate case docket filing and all testimony
+- Facility-level billing determinant analysis
+- Impact assessment under proposed and likely settlement scenarios
+- Intervention timeline and cost estimate
+- Budget revision memo for CFO
+- Coalition membership evaluation
+
+---
+
+### Edge Case 5: Negative LMP Pricing Affecting PPA Economics
+
+**Situation:**
+A consumer products company has a 20-year physical PPA with a 50 MW solar farm in CAISO (Central California). The PPA price is $28/MWh with a clause that the offtaker purchases all energy generated at the contract price. During spring months (March-May), CAISO experiences significant solar oversupply during midday hours. Day-ahead LMPs at the project's node have gone negative — averaging -$8/MWh between 10 AM and 2 PM on weekdays during April.
+
+When LMPs are negative, the generator actually earns negative revenue in the wholesale market (they would have to pay to inject power). However, under the PPA terms, the offtaker (the company) is obligated to purchase at $28/MWh regardless of the market clearing price. During these negative-price hours, the effective premium the company pays is $28 - (-$8) = $36/MWh above market. In April alone, 120 hours of negative pricing on an average 35 MW output represents: 120 hrs × 35 MW × $36/MWh premium = $151,200 of above-market cost in a single month.
+
+Annually, negative pricing during spring months creates approximately $400K-$600K in above-market costs. This was not modeled in the original PPA financial analysis, which assumed LMPs would always be positive.
+
+**Why It's Tricky:**
+The PPA contract requires the company to purchase all generated output at $28/MWh. The contract was signed when CAISO negative pricing was infrequent (occurring <50 hours/year). Since then, solar buildout has accelerated, and negative pricing now occurs 500-800 hours/year in central California during spring. This is a structural trend — it will get worse as more solar is added.
+
+The solar farm continues to generate during negative-price hours because it earns the $28/MWh PPA price (a positive return) plus federal production tax credits ($0.026/kWh), which together exceed its marginal operating cost of effectively $0. The developer has no economic incentive to curtail during negative price hours as long as the PPA requires the offtaker to buy the output.
+
+**Common Mistake:**
+Demanding that the developer curtail during negative price hours (the contract doesn't require this). The second mistake: building a financial model that assumes negative pricing will revert to historical norms — the structural drivers are getting stronger, not weaker.
+
+**Expert Approach:**
+1. **Contract review:** Examine the PPA for any provisions related to economic curtailment, negative pricing, or market price floors. Modern PPAs (post-2020) often include a "negative price curtailment" clause where the developer is curtailed when market prices go negative for >2 consecutive hours, and the offtaker is not obligated to purchase during curtailed hours. Older PPAs may lack this provision.
+
+2. **Economic curtailment negotiation:** Approach the developer to add a negative price curtailment provision. The developer's perspective: they lose PPA revenue ($28/MWh) and may lose PTC value during curtailed hours, but they also avoid the operational cost of generating into a negative-price market and maintain grid operator goodwill (CAISO can mandate curtailment for reliability — voluntary curtailment preserves the developer's standing). Propose: curtailment when the 15-minute LMP is negative, with the developer retaining RECs for curtailed hours (they can sell them separately to partially offset lost PPA revenue).
+
+3. **REC value assessment:** Quantify the REC value for curtailed hours. If the company needs 175,000 RECs/year for RE100 and the PPA delivers 160,000 RECs (net of curtailment), the company must purchase 15,000 replacement RECs at market price ($8-$15/MWh for CAISO solar RECs). Compare this cost ($120K-$225K) against the negative-price exposure ($400K-$600K). The math likely favors curtailment.
+
+4. **Behind-the-meter storage pairing:** If the company has a facility near the solar farm (or in the same utility territory), pairing a battery with the solar PPA allows absorption of midday generation for discharge during evening peak hours when LMPs are highest. This converts the negative-price exposure into a TOU arbitrage opportunity. A 10 MW / 40 MWh battery co-located with or at the facility could shift 4 hours of midday production to evening hours, capturing a $50-$80/MWh spread.
+
+5. **Settlement structure revision:** Negotiate a change from "buy all output at $28/MWh" to "buy all output at $28/MWh with a market price floor of $0/MWh." Under this revised structure, during negative price hours, the company pays $28/MWh (not $36/MWh above market) because the settlement reference price is floored at zero. The developer absorbs the negative market price risk.
+
+**Key Indicators:**
+- CAISO negative pricing frequency exceeding 300 hours/year and growing YoY signals structural oversupply
+- New solar interconnection queue in the generator's zone exceeding 5 GW indicates the problem will worsen
+- CAISO proposed market reforms (extended day-ahead market, WEIM expansion) may partially mitigate negative pricing through broader geographic dispatch
+- Battery storage additions in CAISO are absorbing midday solar and may reduce negative pricing frequency by 2027-2030
+
+---
+
+### Edge Case 6: Behind-the-Meter Solar Cannibalizing Demand Response Value
+
+**Situation:**
+A cold storage operator in New Jersey (PSE&G territory, PJM market) installed a 1.5 MW rooftop solar array under a 25-year on-site solar PPA at $0.065/kWh. The facility is also enrolled in PJM's Economic Demand Response program, committing to curtail 800 kW during high-priced hours. The DR program calculates the Customer Baseline Load (CBL) using the average of the highest 4 out of the prior 5 business days' consumption during the DR event hours.
+
+After the solar installation, the facility's grid consumption during sunny weekday afternoons dropped by approximately 1,100 kW (the solar array's typical output). This reduced the CBL by the same amount. When a DR event is called on a cloudy day (when solar output is only 200 kW instead of 1,100 kW), the facility's actual load is close to its pre-solar level — but the CBL is based on recent sunny days when grid consumption was lower. The measured curtailment (CBL minus actual metered load during the event) is effectively zero or negative, even though the facility is genuinely curtailing discretionary loads.
+
+The result: the facility fails performance testing for the DR program, loses its 800 kW capacity commitment credit ($48,000/year at $60/kW-yr), and faces a non-performance penalty of $25,000.
+
+**Why It's Tricky:**
+The solar array and the DR program each made financial sense individually. But the interaction between the CBL methodology and behind-the-meter solar creates a perverse outcome: solar production on sunny days lowers the baseline, making it harder to demonstrate curtailment on cloudy event days (when solar isn't helping). The CBL methodology was designed for facilities with predictable, weather-independent load — it doesn't account for behind-the-meter generation that varies with weather.
+
+**Common Mistake:**
+Installing behind-the-meter solar and enrolling in DR programs without modeling the CBL interaction. The second mistake: reducing the DR commitment to match the new (lower) CBL, which sacrifices significant capacity revenue.
+
+**Expert Approach:**
+1. **CBL methodology analysis:** Request the detailed CBL calculation methodology from PJM or your curtailment service provider (CSP). Some DR programs allow CBL adjustment for behind-the-meter generation — PJM's rules have evolved, and recent provisions may allow the CBL to be calculated on a "gross load" basis (metered load + estimated solar generation) rather than "net load" basis. If gross load CBL is available, apply for the adjustment.
+
+2. **Solar metering:** Install a revenue-grade meter on the solar array's output (separate from the utility meter). This provides real-time solar generation data that can be used to adjust the CBL. The meter cost ($2,000-$5,000 installed) is trivial compared to the lost DR revenue.
+
+3. **CSP negotiation:** Engage your Curtailment Service Provider to restructure the DR enrollment. Options:
+ - Switch to a "firm service level" (FSL) baseline methodology where your committed curtailment is measured as the difference between your maximum load and a pre-agreed service level, rather than a rolling CBL
+ - Enroll the solar production as a separate DR resource (solar + storage dispatch) rather than netting it against the facility load
+ - Reduce the committed curtailment volume to a level achievable on cloudy days (e.g., 400 kW instead of 800 kW) as an interim measure
+
+4. **Battery integration:** Add a battery system (200 kW / 400 kWh minimum) that charges from solar during sunny hours and discharges during DR events. This allows the facility to demonstrate curtailment on cloudy days by discharging stored solar energy, keeping the CBL higher and providing real kW reduction during events. The battery also earns frequency regulation revenue in PJM during non-event hours.
+
+5. **Re-evaluate the overall value stack.** Recalculate the total economic benefit of each component (solar PPA savings, DR revenue, capacity tag reduction, TOU arbitrage) with the interaction effects included. The optimal configuration may involve sizing the DR commitment to a level that is achievable regardless of solar output, rather than maximizing the individual DR commitment.
+
+**Key Indicators:**
+- Before installing behind-the-meter generation at a facility enrolled in DR, model the CBL impact for all weather scenarios
+- DR programs using CBL-10 (average of 10 prior similar days) are more vulnerable to solar cannibalization than those using metered generation adjustment
+- PJM's wholesale market rules for DR are updated annually — check for behind-the-meter generation accommodation provisions
+
+---
+
+### Edge Case 7: Capacity Market Obligation Surprise from Coincident Peak
+
+**Situation:**
+A data center operator in PJM (ComEd zone, Northern Illinois) runs three facilities with a combined peak demand of 30 MW. The company has been aggressively managing capacity costs — PLC tags for the prior delivery year totaled 24 MW (reflecting successful load reduction during the 5 coincident peak hours).
+
+During the current summer, an unprecedented heat wave hit the Midwest. PJM called for demand response and conservation. The data center operator's backup diesel generators were offline for maintenance during the two hottest days. Without generator backup, the facilities ran at full grid load during what turned out to be 3 of the 5 coincident peak hours. The data center also accepted an emergency colocation request from a major client, adding 2 MW of temporary load.
+
+When PJM publishes the new PLC values, the data center's tag jumps from 24 MW to 31 MW (full grid load of 30 MW plus the 2 MW temporary load minus some non-coincidence). At the BRA clearing price of $98/MW-day, the annual capacity charge increases from $858,720 to $1,108,870 — a $250,150 increase that persists for the entire delivery year.
+
+**Why It's Tricky:**
+The PLC is set by metered data during the 5CP hours — there's no appeals process, no adjustment for maintenance schedules or temporary load. The data center operator managed their PLC carefully for years but a single summer with bad timing (generators offline during the peak) erased all that work. The $250K annual increase is locked for the entire delivery year, regardless of what the data center does going forward.
+
+**Common Mistake:**
+Treating PLC management as "nice to have" rather than a critical operational priority. The second mistake: scheduling generator maintenance during summer months (June-September) when coincident peaks are most likely.
+
+**Expert Approach:**
+1. **Generator maintenance scheduling (preventive):** Never schedule backup generator maintenance during June-September. If maintenance must occur during summer, complete it on a single unit at a time and only on days when the PJM weather forecast shows temperatures below the 5CP trigger zone (typically <90°F for ComEd zone). Maintain at least 80% of generator capacity available during all summer weekday afternoon hours.
+
+2. **Temporary load policies:** Establish a policy that no temporary or emergency load additions are accepted during June-September without explicit approval from the energy procurement team. The $250K capacity charge increase from 2 MW of temporary load far exceeds any revenue from the colocation contract (unless the contract is specifically priced for capacity cost pass-through).
+
+3. **PLC monitoring service:** Subscribe to a PJM coincident peak prediction service (offered by most retail energy providers and specialized consultants). These services predict 5CP hours 24-48 hours in advance with 80-90% accuracy. When a predicted 5CP hour is forecast, activate all available generators, curtail all discretionary load, and notify operations that this is a "gold hour" — every kW reduced during these 5 hours saves $35,770/year at the current capacity price.
+
+4. **Recovery strategy for the current year:** The new PLC is set and cannot be changed for this delivery year. Focus on minimizing next year's PLC. Implement:
+ - Firm generator maintenance blackout window (June 1 - September 30)
+ - Automated demand response controls that shed 3-5 MW of discretionary load within 15 minutes of a 5CP alert
+ - Contractual provisions for all new colocation agreements requiring load shedding during capacity peak events
+
+5. **Financial recovery:** Calculate whether the temporary colocation client's contract covers the capacity cost increase. If not, renegotiate the contract to include capacity cost pass-through. For future emergency colocation requests during summer, quote the capacity cost impact explicitly: "Adding 2 MW during potential 5CP hours will cost $71,540/year in capacity charges — this must be included in the colocation pricing."
+
+**Key Indicators:**
+- PJM summer weather forecasts predicting temperatures >92°F for the ComEd zone on 3+ consecutive weekdays signal likely 5CP hours
+- PJM issuing hot weather alerts or emergency procedures is a near-certain 5CP indicator
+- Backup generator availability below 80% during June-September is a capacity management risk
+
+---
+
+### Edge Case 8: Renewable Curtailment Exceeding Developer Projections
+
+**Situation:**
+A manufacturing company signed a 15-year physical PPA with a 75 MW wind farm in ERCOT (West Texas) at $22/MWh with projected annual generation of 270,000 MWh (41% capacity factor). The company's RE100 target depends on receiving at least 250,000 MWh of bundled RECs from this project annually.
+
+After the first full year of operations, actual generation is 235,000 MWh — 13% below the P50 projection. The shortfall is primarily driven by curtailment: ERCOT curtailed the wind farm for 680 hours (7.8% of the year), versus the developer's projection of 250 hours (2.9%). The curtailment is caused by transmission congestion on the CREZ (Competitive Renewable Energy Zone) lines from West Texas to the Houston and Dallas load centers — the same lines that were built to export West Texas wind, but which are now at capacity due to the exponential growth of wind and solar in the region.
+
+The company is 15,000 RECs short of its annual RE100 requirement and must purchase replacement RECs. Additionally, the lower generation volume means lower PPA settlement income (the positive spread between market price and PPA strike price is earned on fewer MWh).
+
+**Why It's Tricky:**
+Wind farm curtailment in West Texas is a known risk, but the magnitude exceeded projections. The developer used historical curtailment data from 2020-2022 (when the CREZ lines had more headroom) — since then, 8 GW of new wind and solar have interconnected in the same constrained region. The ERCOT interconnection queue shows another 15 GW of proposed projects in West Texas, suggesting curtailment will worsen before it improves.
+
+The PPA contract allocates curtailment risk to the offtaker (the company pays the contract price only for delivered energy, and receives no compensation for curtailed energy). This is standard in older PPA structures.
+
+**Common Mistake:**
+Assuming the developer can solve the curtailment problem (they can't — it's a grid-level transmission constraint). The second mistake: projecting future generation using the developer's original P50 without adjusting for actual curtailment experience.
+
+**Expert Approach:**
+1. **Rebase generation projections.** Using 12 months of actual data, create an adjusted generation projection: actual wind resource (may differ from developer's model), actual curtailment rate (680 hours, not 250), and trend-adjust curtailment based on ERCOT interconnection queue data. A reasonable forward projection might be 225,000-240,000 MWh/year with curtailment worsening 1-2% per year until new transmission is built.
+
+2. **Curtailment clause renegotiation.** Approach the developer to renegotiate the curtailment allocation. Propose a shared risk model: developer bears first 4% of curtailment (their original projection); offtaker bears next 2%; any curtailment above 6% is the developer's risk. The developer may agree because locking in the PPA relationship is preferable to losing the offtaker's volume entirely.
+
+3. **REC replacement strategy.** Budget for annual replacement REC purchases to cover the shortfall. ERCOT wind RECs trade at $2-$4/MWh. A 15,000 REC shortfall costs $30,000-$60,000/year — manageable, but the cost grows if curtailment increases. Consider purchasing replacement RECs through a multi-year contract to lock in pricing.
+
+4. **Transmission monitoring.** Track ERCOT's Long-Term System Assessment and regional transmission plans. New 345 kV lines from West Texas to North Central Texas are planned but typically take 5-7 years from approval to energization. Model the curtailment trajectory assuming transmission expansion occurs on ERCOT's published timeline, and model the scenario where it's delayed 2-3 years.
+
+5. **Portfolio diversification.** For the next renewable procurement, avoid West Texas siting. Diversify to the Texas Gulf Coast (solar, lower curtailment) or outside ERCOT entirely (PJM wind/solar where curtailment is minimal). A portfolio of 2-3 projects across different regions reduces curtailment concentration risk.
+
+**Key Indicators:**
+- ERCOT curtailment orders exceeding 5% of annual hours for a specific generator region signals structural congestion
+- ERCOT interconnection queue exceeding 2× existing generation capacity in a constrained zone is a bearish curtailment signal
+- Developer reporting curtailment exceeding P90 projections in year 1 indicates the projections were based on outdated grid conditions
+
+---
+
+### Edge Case 9: Deregulated Market Re-Regulation Risk
+
+**Situation:**
+A retail chain with 200 stores across Ohio and Pennsylvania has 150 stores on competitive supply contracts (fixed-price, $0.058/kWh energy, average 36 months remaining). After a summer price spike that caused $800M in aggregate consumer cost increases statewide, the Ohio legislature introduces a bill to re-regulate the electricity market — returning all generation procurement to the regulated utilities at tariff rates.
+
+The proposed bill would void all existing competitive supply contracts within 180 days of enactment and require all customers to return to utility standard service. The current utility standard service rate for commercial customers is $0.071/kWh energy — 22% higher than the chain's competitive rate.
+
+The Ohio stores represent 120 of the 200 locations, consuming 95 GWh annually. If re-regulation occurs, the annual energy cost increase for Ohio alone would be approximately $1.24M (95 GWh × $0.013/kWh increase).
+
+**Why It's Tricky:**
+Re-regulation bills are introduced periodically but rarely enacted. However, this bill has political momentum because the summer price spike affected residential customers, and legislators want to "protect consumers." The bill is expected to reach committee vote within 4 months. Even if it doesn't pass, the legislative uncertainty creates contract enforcement risk — retail energy providers may attempt to add regulatory change provisions to new contracts, and existing contract renewal terms may include re-regulation exit clauses.
+
+The more insidious risk: even without formal re-regulation, Ohio could introduce a "provider of last resort" surcharge, a competitive market administration fee, or other mechanisms that reduce the competitive supply discount. These incremental regulatory changes are more likely than full re-regulation and can erode 30-50% of the competitive savings.
+
+**Common Mistake:**
+Ignoring the legislative risk because "re-regulation never happens." It happened in Ohio once before (SB 221 in 2008 attempted partial re-regulation), and Virginia effectively re-regulated in 2007 before partially deregulating again. The second mistake: panicking and trying to exit competitive contracts — the contracts are favorable, and any exit would involve early termination fees.
+
+**Expert Approach:**
+1. **Assess probability.** Engage a regulatory affairs consultant or your energy supplier's government relations team to assess the bill's likelihood of passage. Track committee votes, sponsor count, and utility lobbying positions. If the utility supports re-regulation (they often do, as it restores their captive customer base), the bill has stronger prospects.
+
+2. **Coalition advocacy.** Join or form a C&I customer coalition opposing re-regulation. Large commercial customers benefit most from competition and have the strongest voice against re-regulation. Provide testimony on the consumer savings from competitive supply — a retail chain saving $1.24M/year is a compelling data point.
+
+3. **Contract review.** Examine existing supply contracts for regulatory change clauses. Most well-drafted competitive supply contracts include a provision allowing either party to terminate or renegotiate if the regulatory structure fundamentally changes. Understand your termination rights and the supplier's — if the supplier can exit your contract due to re-regulation, you lose your favorable rate but avoid paying an early termination fee.
+
+4. **Hedging the Pennsylvania exposure.** If Ohio re-regulates, accelerate procurement for Pennsylvania stores. Lock in competitive rates for the maximum available tenor (36-48 months) while the Pennsylvania market remains competitive. Diversify supplier credit exposure in case one supplier exits the Ohio market.
+
+5. **Contingency budgeting.** Model the financial impact of three scenarios:
+ - Full re-regulation (Ohio energy cost increases $1.24M/year)
+ - Partial re-regulation (competitive supply preserved for large C&I but with new surcharges — increase $400K-$600K/year)
+ - Bill fails (no cost change, but future legislative risk remains)
+
+ Present scenarios to the CFO with probability weights. Budget to the expected value.
+
+**Key Indicators:**
+- State legislature introducing electricity market reform bills after consumer price spike events
+- Utility lobbying spend increasing for "market reform" or "default service enhancement"
+- Residential customer complaint rates exceeding 3× historical average (political pressure builds)
+- Governor or PUC chair making public statements about "market failure" in competitive supply
+
+---
+
+### Edge Case 10: Transmission Congestion Invalidating Procurement Strategy
+
+**Situation:**
+A chemical manufacturer with a 15 MW facility in southern New Jersey (JCPL zone, PJM) has been buying power at the PJM Western Hub price through a retail energy provider, with a $0.003/kWh adder. The Western Hub price of $38/MWh has been a reasonable proxy for the JCPL zone price historically (basis of $2-$4/MWh). The company's energy budget is built on $41/MWh all-in.
+
+A new data center campus interconnected 8 miles from the chemical plant, adding 80 MW of load in the JCPL zone. Simultaneously, a 500 MW natural gas plant in the zone retired. The combination of added load and reduced generation created a transmission constraint. The JCPL zone day-ahead LMP jumped from $40/MWh to $58/MWh during peak hours, while the Western Hub price remained at $38/MWh. The basis between Western Hub and JCPL zone widened from $3/MWh to $18/MWh.
+
+The company's retail supply contract settles at Western Hub + adder, but the company pays the utility for energy delivery at the zonal LMP. The net effect: the company is paying $38 + $3 (supplier) but the utility pass-through for congestion is $18/MWh, raising the effective cost to $59/MWh. Against a $41/MWh budget, the facility is running $18/MWh over — $2.36M/year on 131 GWh.
+
+**Why It's Tricky:**
+The supply contract is performing as agreed (Western Hub + $3). The congestion cost is a separate charge flowing through the utility bill. This is a market structure nuance that many C&I buyers don't model — they assume the hub price is approximately equal to their delivered price. When basis was $2-$4/MWh, this assumption was harmless. At $18/MWh, it's a $2.4M/year error.
+
+The structural congestion is unlikely to reverse quickly — the data center load is permanent, the retired plant is not coming back, and new transmission or local generation takes 3-7 years to build.
+
+**Common Mistake:**
+Assuming the congestion is temporary and will revert to historical levels. Structural congestion caused by load growth and generation retirement is persistent until the grid is physically reconfigured. The second mistake: trying to renegotiate the supply contract — the supplier is delivering at the agreed-upon hub price and is not responsible for zonal congestion.
+
+**Expert Approach:**
+1. **Immediate contract restructuring:** Switch the supply contract settlement point from Western Hub to the JCPL zone (load zone pricing). The supplier will quote a higher price that reflects the zone premium, but this eliminates the basis exposure. The company pays a known, locked-in price that includes congestion, rather than a low hub price plus an unpredictable congestion pass-through.
+
+2. **FTR procurement:** Purchase Financial Transmission Rights (FTRs) from Western Hub to the JCPL zone in PJM's monthly or annual FTR auction. An FTR pays the congestion component between the two points — if congestion is $18/MWh and you hold an FTR for your load volume, you receive $18/MWh × volume in FTR settlement, offsetting the congestion charge on your utility bill.
+
+3. **On-site generation evaluation:** With zonal LMPs at $58/MWh during peak hours, the economics for on-site generation improve dramatically. A 5 MW natural gas combined heat and power (CHP) system generating at $40/MWh (fuel + O&M) would save $18/MWh on the kWh it generates. At 8,000 hours/year: $720K/year savings on a $7-$10M capital investment — strong payback.
+
+4. **Long-term transmission monitoring:** Track PJM's Regional Transmission Expansion Plan (RTEP) for projects addressing the JCPL constraint. If PJM approves a transmission upgrade, the congestion may ease in 4-6 years. Factor this into the decision on long-term investments like CHP — if the congestion premium will disappear in 5 years, a CHP plant that was justified by congestion savings may not pencil on its own economics.
+
+5. **Budget reforecast:** Immediately reforecast the energy budget using the new basis reality. Use $55-$60/MWh as the delivered cost assumption until the contract is restructured. Present to finance with a clear explanation of the structural change and the remediation timeline.
+
+**Key Indicators:**
+- PJM Congestion reports showing zonal basis >$10/MWh for >30% of peak hours indicates structural congestion
+- Generator retirement announcements in your zone without replacement capacity signal worsening congestion
+- Large load interconnection applications (data centers, industrial facilities) in your zone increase future congestion risk
+- PJM RTEP project approvals targeting your constraint indicate relief timeline (but delivery is typically 4-7 years out)
+
+**Documentation Required:**
+- Hourly LMP data for Western Hub and JCPL zone (12+ months)
+- Basis calculation spreadsheet (generation-weighted for PPA, load-weighted for supply)
+- FTR auction bid strategy and results
+- CHP feasibility study (if applicable)
+- Budget reforecast with basis scenarios
+- Communication log with supplier regarding settlement point change
+
+**Resolution Timeline:**
+- Week 1: Quantify basis exposure, pull LMP data, reforecast budget
+- Week 2-3: Evaluate FTR procurement, contact supplier about settlement point change
+- Month 2: Execute contract restructuring (settlement point or FTR hedge)
+- Month 3-6: Monitor whether structural congestion persists, evaluate CHP or on-site generation
+- Month 6-12: Reassess portfolio-level strategy for facilities in congested zones
+
+---
+
+### Edge Case 11: Retail Energy Provider Credit Deterioration Mid-Contract
+
+**Situation:**
+A healthcare system with 8 hospitals across Pennsylvania has a 36-month fixed-price electricity supply contract with GreenPeak Energy Solutions, a mid-tier retail energy provider. The contract covers 120 GWh/year at $0.058/kWh energy — well below the current market of $0.067/kWh. GreenPeak's S&P credit rating was BBB at contract signing. Eighteen months into the contract, GreenPeak is downgraded to BB+ (sub-investment grade) after reporting significant trading losses in the most recent quarter. Industry reports suggest GreenPeak overcommitted on fixed-price contracts when forward curves were low and is now underwater as market prices have risen.
+
+The healthcare system's contract has a termination provision allowing either party to exit with 90 days' notice if a material adverse change occurs, including a credit downgrade below investment grade. If GreenPeak fails, the hospitals revert to the utility's default service at $0.071/kWh — a $1.56M annual cost increase.
+
+**Why It's Tricky:**
+The contract is favorable — $0.058/kWh is $0.009/kWh below market. Exercising the termination right is irrational (you'd voluntarily lose a below-market contract). But NOT exercising it means staying exposed to a supplier that may default. If GreenPeak declares bankruptcy, the contract may be rejected in bankruptcy court, and the hospitals lose the favorable rate anyway. The risk calculus: certain below-market pricing today vs. potential forced exit to above-market default service later.
+
+Complicating factor: healthcare facilities cannot tolerate billing disruption. Hospitals must have unambiguous supply arrangements for regulatory compliance, and a supplier default triggers administrative chaos (account switches, utility enrollment, billing reconciliation) that disproportionately impacts a multi-site healthcare system.
+
+**Common Mistake:**
+Doing nothing because the contract is favorable and hoping GreenPeak survives. The second mistake: exercising the termination right immediately and losing the below-market rate. Both extremes are wrong.
+
+**Expert Approach:**
+1. **Credit monitoring (immediate):** Set up alerts for further credit actions on GreenPeak — S&P CreditWatch, Moody's review, and any SEC filings (8-K, 10-Q with going concern language). A further downgrade to BB or below, or a going concern note, significantly increases default probability.
+
+2. **Contract review:** Examine the contract for:
+ - **Adequate assurance clause:** Can you demand financial assurance (letter of credit, parent guarantee) from GreenPeak as a condition of continuing the contract? Many commercial supply contracts include this right upon a material credit event.
+ - **Assignment rights:** Can the contract be assigned to another creditworthy supplier? If GreenPeak is acquired or merges with a stronger company, your contract may survive.
+ - **Setoff rights:** If GreenPeak owes you credits (overcollections, reconciliation adjustments), can you offset those against future payments?
+
+3. **Demand adequate assurance (Week 1):** Formally request that GreenPeak post a standby letter of credit equal to 3-6 months of expected below-market value. Calculate: ($0.067 market - $0.058 contract) × 120 GWh / 12 months × 6 months = $540,000 LC. This protects the healthcare system if GreenPeak defaults — the LC covers the cost of switching to a new supplier at market rates during the transition period.
+
+4. **Parallel supplier qualification (Week 1-3):** Issue an expedited RFP to 3-4 investment-grade suppliers for a replacement contract. Obtain indicative pricing so you know exactly what the replacement cost would be if GreenPeak fails. This is not a commitment — it's insurance. Having a qualified backup supplier with a standing offer reduces the transition time from weeks to days.
+
+5. **Hedging the replacement risk (Month 1):** If the replacement cost at market ($0.067) is significantly above your contract ($0.058), consider purchasing a financial hedge that pays out if you're forced to switch suppliers. Specifically, buy a call option on PJM electricity at a strike price of $0.060/kWh for the remaining contract volume. If GreenPeak defaults and you switch to a market-priced supplier, the call option offsets the cost increase above $0.060.
+
+6. **Ongoing monitoring cadence:** Review GreenPeak's financial health monthly. Track: credit rating changes, SEC filings, employee LinkedIn departures (mass exits from a supplier signal trouble), utility regulatory filings (some states require REPs to post bonds), and industry rumors (energy industry is small — your broker will hear about financial distress before it hits the news).
+
+**Key Indicators:**
+- Supplier credit downgrade below BBB- (investment grade threshold) is the first warning
+- Supplier requesting early payment, changing payment terms, or delaying customer credits signals cash flow problems
+- Supplier laying off commercial/pricing staff suggests they're de-risking by not taking new business
+- State utility commission audits of REP financial requirements may reveal shortfalls
+- If 2+ other C&I buyers report the same supplier is requesting contract modifications, the supplier is restructuring its book
+
+**Documentation Required:**
+- Credit rating history and monitoring alerts
+- Adequate assurance demand letter and GreenPeak response
+- Replacement supplier indicative pricing
+- Financial hedge evaluation (call option cost vs. benefit)
+- Board-level risk assessment memo
+- Contingency communication plan for hospitals (billing continuity)
+
+**Resolution Timeline:**
+- Week 1: Demand adequate assurance, initiate backup supplier RFP
+- Week 2-3: Receive GreenPeak response to assurance demand, evaluate backup bids
+- Month 1-2: If assurance is posted, continue monitoring. If refused, evaluate termination.
+- Month 3+: Monthly credit monitoring until GreenPeak's financial position stabilizes or the contract expires
+
+---
+
+### Edge Case 12: Multi-State Portfolio with Mixed Regulated/Deregulated Markets
+
+**Situation:**
+A food and beverage company operates 35 facilities across 18 states: 15 manufacturing plants (2-12 MW each), 12 distribution centers (500 kW - 3 MW each), and 8 corporate/R&D offices (200-800 kW each). Total electricity consumption: 680 GWh/year, $58M annual energy spend. The facilities are split: 20 in deregulated markets (PJM, ERCOT, NYISO, ISO-NE), 10 in regulated markets (Georgia, Florida, Alabama, Tennessee), and 5 in markets with limited competition (partial deregulation or pilot programs).
+
+The VP of Sustainability has committed the company to RE100 by 2030. The CFO wants 5% annual energy cost reduction. The Director of Operations wants zero disruption to production. Currently, each facility manages its own utility relationship — there is no centralized energy procurement function. Tariff selection, contract renewals, and demand charge management are handled by facility managers with no energy expertise, resulting in:
+- 12 facilities on suboptimal tariff schedules (estimated $1.2M/year in unnecessary charges)
+- 6 deregulated sites on utility default service (never switched to competitive supply — $2.1M/year above market)
+- No demand charge management programs at any facility
+- RE100 progress at 12% (entirely from unbundled RECs purchased by the sustainability team)
+
+**Why It's Tricky:**
+Building a centralized energy procurement function from scratch requires addressing every aspect simultaneously: competitive procurement in deregulated markets, tariff optimization in regulated markets, demand charge management at high-potential sites, renewable procurement to hit RE100, and budget forecasting and reporting across 35 facilities. With no existing infrastructure, even basic tasks like assembling interval data for 35 facilities take months.
+
+The mixed regulatory landscape means no single strategy works everywhere. A VPPA that works for PJM sites is irrelevant for Georgia sites. Demand charge management that works at a manufacturing plant doesn't apply to an office. Tariff optimization requires state-by-state regulatory expertise.
+
+**Common Mistake:**
+Trying to do everything at once — hiring a consultant, issuing an enterprise RFP, signing a mega-VPPA, and installing batteries at every site simultaneously. This overwhelms the organization, produces poor execution on every front, and alienates facility managers who feel central procurement is disrupting their operations.
+
+**Expert Approach:**
+1. **Phase 0: Data assembly and baselining (Month 1-3).**
+ Deploy an energy management information system (EMIS) like EnergyCAP, Urjanet, or UtilityAPI to automatically collect utility bill data for all 35 sites. This eliminates the manual data collection bottleneck. Target: complete 12-month utility bill history and interval data for all sites within 90 days.
+
+2. **Phase 1: Quick wins (Month 2-6).** Prioritize actions with immediate savings and minimal disruption:
+ - **Switch 6 default-service sites to competitive supply.** Issue an aggregated RFP covering all 6 sites (combined volume gives leverage). Expected savings: 10-15% on energy charges = $200K-$300K/year per site.
+ - **Tariff audit all 35 sites.** Engage a tariff optimization consultant or use software to model each site against all available rate schedules. Switch 12 sites to optimal tariffs. Expected savings: $1.2M/year.
+ - **Demand charge review for top 10 sites by demand charge cost.** Implement zero-cost measures (staggered startups, BAS programming) at the top 5 sites. Expected savings: $300K-$500K/year.
+
+ Phase 1 total savings estimate: $2.5M-$4M/year, achievable within 6 months.
+
+3. **Phase 2: Strategic procurement (Month 4-12).** With data and quick wins establishing credibility:
+ - **Portfolio procurement for deregulated sites.** Aggregate 20 deregulated sites by ISO and issue portfolio RFPs. Use layered block-and-index structure for manufacturing (high load factor) and fixed-price for offices/DCs (lower load factor, less optimization potential).
+ - **Demand charge capital projects.** Using Phase 1 analysis, identify 3-5 sites where battery storage or demand response has <5 year payback. Develop business cases and submit for capital approval.
+ - **Renewable procurement strategy.** Design a phased RE100 roadmap:
+ - Year 1-2: Switch unbundled RECs from national wind to project-specific solar RECs (better additionality, modest cost increase)
+ - Year 2-3: Execute first VPPA (100-150 GWh/year) targeting PJM or MISO sites
+ - Year 3-4: Add a second VPPA or physical PPA for ERCOT sites
+ - Year 4-5: On-site solar at 5-8 facilities with favorable economics
+ - Year 5-6: Utility green tariffs or community solar for regulated market sites
+
+4. **Phase 3: Optimization and continuous improvement (Year 2+).** With infrastructure in place:
+ - Implement real-time energy monitoring and automated demand response at top 15 sites
+ - Build internal capability for capacity tag management (PJM, ISO-NE)
+ - Establish a quarterly energy procurement committee (finance, sustainability, operations, procurement)
+ - Develop forward-looking energy risk management policy with hedge ratios and governance
+
+5. **Governance and reporting:** From Day 1, establish a reporting framework:
+ - Monthly: energy cost vs. budget by site, demand charge performance, supply contract status
+ - Quarterly: portfolio-level hedge ratio, RE100 progress, supplier scorecard, market outlook
+ - Annually: total energy spend vs. prior year (weather-normalized), cost avoidance from optimization, sustainability target progress, 3-year procurement strategy refresh
+
+**Key Indicators:**
+- If quick wins (Phase 1) don't deliver $2M+ in annual savings, the baseline analysis was wrong — revisit data
+- Facility manager resistance to centralized procurement is the #1 implementation risk — address it through communication and shared savings incentives
+- RE100 progress requires committed procurement volume, not just REC purchases — if RE% stalls at 30-40%, it's because the VPPA/PPA pipeline isn't producing
+- Total energy cost as a percentage of revenue should decrease YoY (weather-normalized) — if it's flat or increasing, the optimization program isn't working
+
+**Documentation Required:**
+- 35-site energy baseline (utility bills, interval data, tariff schedules, contracts)
+- Phase 1 savings tracking (actual vs. projected by initiative)
+- Portfolio procurement RFP and award documentation
+- RE100 roadmap with annual milestones and procurement commitments
+- Energy risk management policy
+- Capital project business cases for demand-side investments
+- Quarterly energy management committee reports
+
+**Resolution Timeline:**
+- Month 1-3: Data assembly, EMIS deployment, Phase 0 complete
+- Month 2-6: Phase 1 quick wins executed, $2.5M-$4M/year savings captured
+- Month 4-12: Phase 2 strategic procurement, first VPPA executed
+- Year 2: Phase 3 optimization, demand-side capital projects operational
+- Year 3: RE100 at 50%+, energy cost reduction at 15%+ from baseline
+- Year 5: RE100 at 80%+, fully mature energy management program
+
+---
+
+### Edge Case 13: Natural Gas Supply Disruption During Winter Heating Season
+
+**Situation:**
+A pharmaceutical manufacturer in New Jersey operates a 150,000 sq ft production facility with a 6,000 MMBtu/month winter natural gas load (process heat for API synthesis plus facility heating). The facility is on a firm transportation gas contract with a local distribution company (LDC) at a rate of $8.50/MMBtu delivered. During a prolonged January cold snap (15 consecutive days below 15°F), the LDC issues an Operational Flow Order (OFO) restricting deliveries to critical-use customers only. The pharmaceutical plant's gas supply is not classified as "critical use" under the LDC's tariff — hospitals and residential heating take priority.
+
+The OFO reduces the facility's gas allocation to 60% of normal. The remaining 40% (2,400 MMBtu/month) must be sourced on the spot market through an alternative supply arrangement, or the facility must curtail operations. Spot gas at the Transco Zone 6 delivery point is trading at $28/MMBtu — more than 3× the contract rate. Alternatively, the facility could switch some process heat to electric resistance heating, but this would increase electricity demand by 1.8 MW during a period when electricity prices are also elevated ($180/MWh due to gas-fired generation being price-setting at high gas prices).
+
+The pharmaceutical product in process has a 72-hour window before it must be temperature-controlled or destroyed — $4.2M worth of active pharmaceutical ingredient is at risk.
+
+**Why It's Tricky:**
+The facility faces a trilemma: (1) pay $28/MMBtu spot gas to maintain full operations (4× the normal cost), (2) switch to electric heating at $180/MWh equivalent cost (which may be even more expensive per BTU than spot gas), or (3) curtail production and risk $4.2M in product loss. None of these options is clearly superior, and the decision must be made within hours.
+
+The LDC's OFO is legally enforceable — the tariff allows curtailment of non-critical-use customers during supply emergencies. The facility's "firm" gas contract is firm for transportation, but the OFO overrides transportation priority during emergencies. This is a distinction most facility managers don't understand until it happens.
+
+**Common Mistake:**
+Assuming "firm" gas service means guaranteed delivery under all conditions. Firm transportation is firm relative to interruptible service — but OFOs can curtail even firm customers. The second mistake: relying entirely on gas without a dual-fuel backup for critical process heat.
+
+**Expert Approach:**
+1. **Immediate triage (Hour 0-2):** Calculate the cost of each option per MMBtu equivalent:
+ - Spot gas: $28/MMBtu delivered
+ - Electric resistance heating: $180/MWh ÷ 3,412 BTU/kWh × 1,000,000 = $52.75/MMBtu equivalent (even more expensive than spot gas and subject to demand charge spikes)
+ - Product loss: $4.2M ÷ 72 hours = $58,333/hour of delay. Even at $28/MMBtu, running the process heat costs far less than product loss.
+
+ **Decision: Purchase spot gas at $28/MMBtu for process heat. Use electric heating only for space heating (lower priority, can tolerate temperature setback).**
+
+2. **Spot gas procurement (Hour 0-4):** Contact your gas marketer or broker to secure spot supply at Transco Zone 6. Request a 15-day deal (covering the forecast cold snap duration). Negotiate for a fixed daily quantity with a price cap rather than floating daily pricing — during extreme events, daily spot prices can swing $10-$15/MMBtu between morning and afternoon.
+
+3. **Demand charge protection (Hour 0):** If switching any load to electric heating, install temporary demand limiting controls. A 1.8 MW increase in electric demand at a $15/kW demand rate = $27,000/month in additional demand charges, plus potential ratchet impact. If possible, offset the added electric load by curtailing other electric loads (lighting, non-essential compressed air).
+
+4. **Dual-fuel capability assessment (Week 2, post-event):** After the event, evaluate installing dual-fuel capability for the critical process heat systems. A dual-fuel burner that can switch between gas and #2 fuel oil costs $150K-$300K for a 6,000 MMBtu/month system. With fuel oil on-site in a storage tank, the facility can maintain operations during gas curtailments without relying on spot gas or electric conversion. Annual carrying cost (tank rental, fuel turnover): $25K-$40K.
+
+5. **LDC tariff engagement (Month 2-3):** Petition the LDC to reclassify the pharmaceutical facility as "critical use" under the tariff. Pharmaceutical manufacturing has arguments for critical use designation: product at risk of destruction, FDA compliance implications, public health importance. The reclassification requires a tariff filing with the state utility commission — engage regulatory counsel.
+
+6. **Contractual protection (next renewal):** At the next gas contract renewal, negotiate a "firm-firm" or "no-notice" transportation agreement that provides the highest curtailment priority available from the LDC. This costs 10-20% more than standard firm transportation but eliminates OFO exposure. Alternatively, negotiate a "supplemental supply" agreement with a gas marketer that automatically activates when the LDC issues an OFO — pre-arranged backup supply at a pre-negotiated spread above the index.
+
+**Key Indicators:**
+- Weather forecasts showing >10 consecutive days below 20°F in the Northeast signal potential OFO conditions
+- LDC "system alerts" or "constraint days" preceding a full OFO — act on alerts, don't wait for the OFO
+- Henry Hub spot gas exceeding $5/MMBtu during winter signals tight national supply — regional prices will spike harder
+- Electricity price correlation: when gas spot is elevated, electricity spot is elevated proportionally — electric heating is not a cheap alternative during gas supply emergencies
+
+**Documentation Required:**
+- LDC Operational Flow Order notification and curtailment percentage
+- Spot gas purchase confirmations and pricing
+- Product-at-risk calculation and decision documentation
+- Electric load impact and demand charge analysis
+- Post-event dual-fuel capability feasibility study
+- LDC tariff reclassification petition (if pursuing critical use designation)
+- Gas contract renewal strategy with enhanced curtailment protection
+
+**Resolution Timeline:**
+- Hour 0-4: Triage, spot gas procurement, demand limiting controls
+- Days 1-15: Manage blended gas supply (contract + spot), monitor cold snap duration
+- Week 3: Post-event financial analysis, present cost impact to management
+- Month 2-3: Initiate dual-fuel feasibility study, LDC tariff reclassification
+- Month 4-6: Install dual-fuel capability (if approved), negotiate enhanced gas contract
+- Next renewal: Execute firm-firm or no-notice gas transportation agreement
diff --git a/web-app/public/skills/error-detective/SKILL.md b/web-app/public/skills/error-detective/SKILL.md
index 8af4f438..cd8c8fd0 100644
--- a/web-app/public/skills/error-detective/SKILL.md
+++ b/web-app/public/skills/error-detective/SKILL.md
@@ -1,6 +1,7 @@
---
name: error-detective
-description: "Search logs and codebases for error patterns, stack traces, and"
+description: |
+ Search logs and codebases for error patterns, stack traces, and
anomalies. Correlates errors across systems and identifies root causes. Use
PROACTIVELY when debugging issues, analyzing logs, or investigating production
errors.
diff --git a/web-app/public/skills/fastapi-pro/SKILL.md b/web-app/public/skills/fastapi-pro/SKILL.md
index f07b0e60..b84a2913 100644
--- a/web-app/public/skills/fastapi-pro/SKILL.md
+++ b/web-app/public/skills/fastapi-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: fastapi-pro
-description: "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and"
+description: |
+ Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and
Pydantic V2. Master microservices, WebSockets, and modern Python async
patterns. Use PROACTIVELY for FastAPI development, async optimization, or API
architecture.
diff --git a/web-app/public/skills/firmware-analyst/SKILL.md b/web-app/public/skills/firmware-analyst/SKILL.md
index 83f56424..a0fcf517 100644
--- a/web-app/public/skills/firmware-analyst/SKILL.md
+++ b/web-app/public/skills/firmware-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: firmware-analyst
-description: "Expert firmware analyst specializing in embedded systems, IoT"
+description: |
+ Expert firmware analyst specializing in embedded systems, IoT
security, and hardware reverse engineering. Masters firmware extraction,
analysis, and vulnerability research for routers, IoT devices, automotive
systems, and industrial controllers. Use PROACTIVELY for firmware security
diff --git a/web-app/public/skills/flutter-expert/SKILL.md b/web-app/public/skills/flutter-expert/SKILL.md
index 7b8ee06a..f5d6d848 100644
--- a/web-app/public/skills/flutter-expert/SKILL.md
+++ b/web-app/public/skills/flutter-expert/SKILL.md
@@ -1,6 +1,7 @@
---
name: flutter-expert
-description: "Master Flutter development with Dart 3, advanced widgets, and"
+description: |
+ Master Flutter development with Dart 3, advanced widgets, and
multi-platform deployment. Handles state management, animations, testing, and
performance optimization for mobile, web, desktop, and embedded platforms. Use
PROACTIVELY for Flutter architecture, UI implementation, or cross-platform
diff --git a/web-app/public/skills/form-cro/SKILL.md b/web-app/public/skills/form-cro/SKILL.md
index d6ec718a..42691609 100644
--- a/web-app/public/skills/form-cro/SKILL.md
+++ b/web-app/public/skills/form-cro/SKILL.md
@@ -1,6 +1,6 @@
---
name: form-cro
-description: ">"
+description: >
Optimize any form that is NOT signup or account registration — including lead
capture, contact, demo request, application, survey, quote, and checkout forms.
Use when the goal is to increase form completion rate, reduce friction, or
diff --git a/web-app/public/skills/frontend-developer/SKILL.md b/web-app/public/skills/frontend-developer/SKILL.md
index 9076ec20..0f065ebb 100644
--- a/web-app/public/skills/frontend-developer/SKILL.md
+++ b/web-app/public/skills/frontend-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: frontend-developer
-description: "Build React components, implement responsive layouts, and handle"
+description: |
+ Build React components, implement responsive layouts, and handle
client-side state management. Masters React 19, Next.js 15, and modern
frontend architecture. Optimizes performance and ensures accessibility. Use
PROACTIVELY when creating UI components or fixing frontend issues.
diff --git a/web-app/public/skills/frontend-security-coder/SKILL.md b/web-app/public/skills/frontend-security-coder/SKILL.md
index fd8d22dc..1edc8ade 100644
--- a/web-app/public/skills/frontend-security-coder/SKILL.md
+++ b/web-app/public/skills/frontend-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: frontend-security-coder
-description: "Expert in secure frontend coding practices specializing in XSS"
+description: |
+ Expert in secure frontend coding practices specializing in XSS
prevention, output sanitization, and client-side security patterns. Use
PROACTIVELY for frontend security implementations or client-side security code
reviews.
diff --git a/web-app/public/skills/golang-pro/SKILL.md b/web-app/public/skills/golang-pro/SKILL.md
index 807a3552..5393bc58 100644
--- a/web-app/public/skills/golang-pro/SKILL.md
+++ b/web-app/public/skills/golang-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: golang-pro
-description: "Master Go 1.21+ with modern patterns, advanced concurrency,"
+description: |
+ Master Go 1.21+ with modern patterns, advanced concurrency,
performance optimization, and production-ready microservices. Expert in the
latest Go ecosystem including generics, workspaces, and cutting-edge
frameworks. Use PROACTIVELY for Go development, architecture design, or
diff --git a/web-app/public/skills/graphql-architect/SKILL.md b/web-app/public/skills/graphql-architect/SKILL.md
index b6f5fb25..211e873e 100644
--- a/web-app/public/skills/graphql-architect/SKILL.md
+++ b/web-app/public/skills/graphql-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: graphql-architect
-description: "Master modern GraphQL with federation, performance optimization,"
+description: |
+ Master modern GraphQL with federation, performance optimization,
and enterprise security. Build scalable schemas, implement advanced caching,
and design real-time systems. Use PROACTIVELY for GraphQL architecture or
performance optimization.
diff --git a/web-app/public/skills/grpc-golang/SKILL.md b/web-app/public/skills/grpc-golang/SKILL.md
new file mode 100644
index 00000000..66d17712
--- /dev/null
+++ b/web-app/public/skills/grpc-golang/SKILL.md
@@ -0,0 +1,103 @@
+---
+name: grpc-golang
+description: "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport."
+risk: safe
+source: self
+---
+
+# gRPC Golang (gRPC-Go)
+
+## Overview
+
+Comprehensive guide for designing and implementing production-grade gRPC services in Go. Covers contract standardization with Buf, transport layer security via mTLS, and deep observability with OpenTelemetry interceptors.
+
+## Use this skill when
+
+- Designing microservices communication with gRPC in Go.
+- Building high-performance internal APIs using Protobuf.
+- Implementing streaming workloads (unidirectional or bidirectional).
+- Standardizing API contracts using Protobuf and Buf.
+- Configuring mTLS for service-to-service authentication.
+
+## Do not use this skill when
+
+- Building pure REST/HTTP public APIs without gRPC requirements.
+- Modifying legacy `.proto` files without the ability to introduce a new API version (e.g., `api.v2`) or ensure backward compatibility.
+- Managing service mesh traffic routing (e.g., Istio/Linkerd), which is outside the application code scope.
+
+## Step-by-Step Guide
+
+1. **Confirm Technical Context**: Identify Go version, gRPC-Go version, and whether the project uses Buf or raw protoc.
+2. **Confirm Requirements**: Identify mTLS needs, load patterns (unary/streaming), SLOs, and message size limits.
+3. **Plan Schema**: Define package versioning (e.g., `api.v1`), resource types, and error mapping.
+4. **Security Design**: Implement mTLS for service-to-service authentication.
+5. **Observability**: Configure interceptors for tracing, metrics, and structured logging.
+6. **Verification**: Always run `buf lint` and breaking change checks before finalizing code generation.
+
+Refer to `resources/implementation-playbook.md` for detailed patterns, code examples, and anti-patterns.
+
+## Examples
+
+### Example 1: Defining a Service & Message (v1 API)
+
+```proto
+syntax = "proto3";
+package api.v1;
+option go_package = "github.com/org/repo/gen/api/v1;apiv1";
+
+service UserService {
+ rpc GetUser(GetUserRequest) returns (GetUserResponse);
+}
+
+message User {
+ string id = 1;
+ string name = 2;
+}
+
+message GetUserRequest {
+ string id = 1;
+}
+
+message GetUserResponse {
+ User user = 1;
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Use Buf to standardize your toolchain and linting with `buf.yaml` and `buf.gen.yaml`.
+- ✅ **Do:** Always use semantic versioning in package paths (e.g., `package api.v1`).
+- ✅ **Do:** Enforce mTLS for all internal service-to-service communication.
+- ✅ **Do:** Handle `ctx.Done()` in all streaming handlers to prevent resource leaks.
+- ✅ **Do:** Map domain errors to standard gRPC status codes (e.g., `codes.NotFound`).
+- ❌ **Don't:** Return raw internal error strings or stack traces to gRPC clients.
+- ❌ **Don't:** Create a new `grpc.ClientConn` per request; always reuse connections.
+
+## Troubleshooting
+
+- **Error: Inconsistent Gen**: If the generated code does not match the schema, run `buf generate` and verify the `go_package` option.
+- **Error: Context Deadline**: Check client timeouts and ensure the server is not blocking infinitely in streaming handlers.
+- **Error: mTLS Handshake**: Ensure the CA certificate is correctly added to the `x509.CertPool` on both client and server sides.
+
+## Limitations
+
+- Does not cover service mesh traffic routing (Istio/Linkerd configuration).
+- Does not cover gRPC-Web or browser-based gRPC integration.
+- Assumes Go 1.21+ and gRPC-Go v1.60+; older versions may have different APIs (e.g., `grpc.Dial` vs `grpc.NewClient`).
+- Does not cover L7 gRPC-aware load balancer configuration (e.g., Envoy, NGINX).
+- Does not address Protobuf schema registry or large-scale schema governance beyond Buf lint.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, code examples, and anti-patterns.
+- [Google API Design Guide](https://cloud.google.com/apis/design)
+- [Buf Docs](https://buf.build/docs)
+- [gRPC-Go Docs](https://grpc.io/docs/languages/go/)
+- [OpenTelemetry Go Instrumentation](https://opentelemetry.io/docs/instrumentation/go/)
+
+## Related Skills
+
+- @golang-pro - General Go patterns and performance optimization outside the gRPC layer.
+- @go-concurrency-patterns - Advanced goroutine lifecycle management for streaming handlers.
+- @api-design-principles - Resource naming and versioning strategy before writing `.proto` files.
+- @docker-expert - Containerizing gRPC services and configuring TLS cert injection via Docker secrets.
diff --git a/web-app/public/skills/grpc-golang/resources/implementation-playbook.md b/web-app/public/skills/grpc-golang/resources/implementation-playbook.md
new file mode 100644
index 00000000..e6eece49
--- /dev/null
+++ b/web-app/public/skills/grpc-golang/resources/implementation-playbook.md
@@ -0,0 +1,548 @@
+# gRPC Golang Implementation Playbook
+
+This file contains detailed patterns, checklists, and code samples referenced by the skill.
+
+## Schema Design Standards
+
+### Protobuf Definition
+
+- **Syntax**: Use proto3 only.
+- **Versioning**: Use package versioning (e.g., `api.v1`).
+- **Pagination**: Use `page_token` and `page_size` for list operations.
+- **Timezone**: Always use `google.protobuf.Timestamp` with UTC values at the server level.
+- **Idempotency**: Use idempotency keys or design side-effect-free methods to allow safe retries.
+- **Validation**: Adopt a schema-level validation approach (e.g., Buf validation rules or `protoc-gen-validate`) and ensure generated code is enforced server-side.
+
+```proto
+syntax = "proto3";
+package api.v1;
+option go_package = "github.com/org/repo/gen/api/v1;apiv1";
+
+import "google/protobuf/timestamp.proto";
+
+service UserService {
+ rpc GetUser(GetUserRequest) returns (GetUserResponse);
+ rpc ListUsers(ListUsersRequest) returns (ListUsersResponse);
+ rpc WatchUsers(WatchUsersRequest) returns (stream UserEvent);
+}
+
+message User {
+ string id = 1;
+ string name = 2;
+ string email = 3;
+ google.protobuf.Timestamp created_at = 4;
+}
+
+message GetUserRequest {
+ string id = 1;
+}
+
+message GetUserResponse {
+ User user = 1;
+}
+
+message ListUsersRequest {
+ int32 page_size = 1;
+ string page_token = 2;
+}
+
+message ListUsersResponse {
+ repeated User users = 1;
+ string next_page_token = 2;
+}
+
+message WatchUsersRequest {
+ // Empty; streams all user events from the current point.
+}
+
+message UserEvent {
+ enum EventType {
+ EVENT_TYPE_UNSPECIFIED = 0;
+ EVENT_TYPE_CREATED = 1;
+ EVENT_TYPE_UPDATED = 2;
+ EVENT_TYPE_DELETED = 3;
+ }
+ EventType type = 1;
+ User user = 2;
+ google.protobuf.Timestamp occurred_at = 3;
+}
+```
+
+## Code Generation
+
+- **Toolchain**: Use `google.golang.org/protobuf/cmd/protoc-gen-go` and `protoc-gen-go-grpc`.
+- **Management**: Use `buf.gen.yaml` to manage plugin versions and generation parameters.
+- **Compatibility**: Ensure plugins use Protobuf Go v2 API (`google.golang.org/protobuf`). Do not mix with the deprecated v1 API (`github.com/golang/protobuf`).
+
+### buf.gen.yaml Example
+
+```yaml
+version: v2
+plugins:
+ - remote: buf.build/protocolbuffers/go
+ out: gen
+ opt: paths=source_relative
+ - remote: buf.build/grpc/go
+ out: gen
+ opt: paths=source_relative
+```
+
+## Server Implementation
+
+### Full Server Setup with Graceful Shutdown
+
+```go
+package main
+
+import (
+ "context"
+ "log"
+ "net"
+ "os"
+ "os/signal"
+ "syscall"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/health"
+ healthpb "google.golang.org/grpc/health/grpc_health_v1"
+ "google.golang.org/grpc/keepalive"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+func main() {
+ srv := grpc.NewServer(
+ grpc.ChainUnaryInterceptor(
+ recoveryInterceptor,
+ loggingInterceptor,
+ otelUnaryInterceptor,
+ ),
+ grpc.KeepaliveParams(keepalive.ServerParameters{
+ MaxConnectionIdle: 5 * time.Minute,
+ Time: 1 * time.Minute,
+ Timeout: 20 * time.Second,
+ }),
+ grpc.MaxRecvMsgSize(4<<20), // 4 MB
+ grpc.MaxSendMsgSize(4<<20), // 4 MB
+ )
+
+ // Register application services.
+ apiv1.RegisterUserServiceServer(srv, newUserService())
+
+ // Register health check with fully-qualified service name.
+ healthSrv := health.NewServer()
+ healthpb.RegisterHealthServer(srv, healthSrv)
+ healthSrv.SetServingStatus(
+ "api.v1.UserService",
+ healthpb.HealthCheckResponse_SERVING,
+ )
+
+ lis, err := net.Listen("tcp", ":50051")
+ if err != nil {
+ log.Fatalf("listen: %v", err)
+ }
+
+ // Graceful shutdown: GracefulStop with a fallback timeout to Stop.
+ go func() {
+ sigCh := make(chan os.Signal, 1)
+ signal.Notify(sigCh, syscall.SIGINT, syscall.SIGTERM)
+ <-sigCh
+
+ log.Println("shutting down gRPC server...")
+ healthSrv.SetServingStatus(
+ "api.v1.UserService",
+ healthpb.HealthCheckResponse_NOT_SERVING,
+ )
+
+ ctx, cancel := context.WithTimeout(context.Background(), 15*time.Second)
+ defer cancel()
+
+ stopped := make(chan struct{})
+ go func() {
+ srv.GracefulStop()
+ close(stopped)
+ }()
+
+ select {
+ case <-stopped:
+ log.Println("server stopped gracefully")
+ case <-ctx.Done():
+ log.Println("graceful stop timed out, forcing stop")
+ srv.Stop()
+ }
+ }()
+
+ log.Printf("gRPC server listening on %s", lis.Addr())
+ if err := srv.Serve(lis); err != nil {
+ log.Fatalf("serve: %v", err)
+ }
+}
+```
+
+## mTLS Setup
+
+```go
+package main
+
+import (
+ "crypto/tls"
+ "crypto/x509"
+ "fmt"
+ "log"
+ "os"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials"
+)
+
+// loadServerTLS configures mTLS for the server side.
+func loadServerTLS() grpc.ServerOption {
+ tlsCert, err := tls.LoadX509KeyPair("server.crt", "server.key")
+ if err != nil {
+ log.Fatalf("load server cert: %v", err)
+ }
+
+ caCert, err := os.ReadFile("ca.crt")
+ if err != nil {
+ log.Fatalf("read CA cert: %v", err)
+ }
+
+ caPool := x509.NewCertPool()
+ if !caPool.AppendCertsFromPEM(caCert) {
+ log.Fatal("failed to append CA cert")
+ }
+
+ tlsCfg := &tls.Config{
+ Certificates: []tls.Certificate{tlsCert},
+ ClientCAs: caPool,
+ ClientAuth: tls.RequireAndVerifyClientCert,
+ MinVersion: tls.VersionTLS13,
+ }
+ return grpc.Creds(credentials.NewTLS(tlsCfg))
+}
+
+// dialWithMTLS creates a client connection using mTLS.
+func dialWithMTLS(target string) (*grpc.ClientConn, error) {
+ clientCert, err := tls.LoadX509KeyPair("client.crt", "client.key")
+ if err != nil {
+ return nil, fmt.Errorf("load client cert: %w", err)
+ }
+
+ caCert, err := os.ReadFile("ca.crt")
+ if err != nil {
+ return nil, fmt.Errorf("read CA cert: %w", err)
+ }
+
+ caPool := x509.NewCertPool()
+ if !caPool.AppendCertsFromPEM(caCert) {
+ return nil, fmt.Errorf("failed to append CA cert")
+ }
+
+ creds := credentials.NewTLS(&tls.Config{
+ Certificates: []tls.Certificate{clientCert},
+ RootCAs: caPool,
+ MinVersion: tls.VersionTLS13,
+ })
+
+ // Note: for gRPC-Go v1.63+, grpc.NewClient is the recommended replacement.
+ conn, err := grpc.Dial(target, grpc.WithTransportCredentials(creds))
+ if err != nil {
+ return nil, fmt.Errorf("dial %s: %w", target, err)
+ }
+ return conn, nil
+}
+```
+
+## Client Best Practices
+
+### Connection Reuse
+
+```go
+package main
+
+import (
+ "context"
+ "fmt"
+ "log"
+ "os"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+// Initialize once at startup; reuse across the application lifetime.
+var userConn *grpc.ClientConn
+
+func initClients(creds credentials.TransportCredentials) {
+ var err error
+ // Note: for gRPC-Go v1.63+, use grpc.NewClient instead.
+ userConn, err = grpc.Dial(
+ os.Getenv("USER_SVC_ADDR"),
+ grpc.WithTransportCredentials(creds),
+ )
+ if err != nil {
+ log.Fatalf("dial user-svc: %v", err)
+ }
+}
+
+func callListUsers(ctx context.Context) (*apiv1.ListUsersResponse, error) {
+ // Always set a deadline per call, not per connection.
+ ctx, cancel := context.WithTimeout(ctx, 5*time.Second)
+ defer cancel()
+
+ client := apiv1.NewUserServiceClient(userConn)
+ resp, err := client.ListUsers(ctx, &apiv1.ListUsersRequest{PageSize: 20})
+ if err != nil {
+ return nil, fmt.Errorf("list users: %w", err)
+ }
+ return resp, nil
+}
+```
+
+### Retry Policy
+
+Only enable retries for idempotent calls. Use exponential backoff.
+
+```go
+import "google.golang.org/grpc"
+
+// Service config with retry policy for idempotent methods.
+const retryPolicy = `{
+ "methodConfig": [{
+ "name": [{"service": "api.v1.UserService", "method": "GetUser"}],
+ "retryPolicy": {
+ "maxAttempts": 3,
+ "initialBackoff": "0.1s",
+ "maxBackoff": "1s",
+ "backoffMultiplier": 2,
+ "retryableStatusCodes": ["UNAVAILABLE", "DEADLINE_EXCEEDED"]
+ }
+ }]
+}`
+
+// Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.Dial.
+conn, err := grpc.Dial(
+ target,
+ grpc.WithTransportCredentials(creds),
+ grpc.WithDefaultServiceConfig(retryPolicy),
+)
+```
+
+## Observability
+
+### Interceptor Labels
+
+- **Logging**: Include `grpc.method`, `grpc.service`, `grpc.code`, `latency_ms`, and `trace_id`.
+- **Metrics**: Export request count, latency histogram, and in-flight stream count.
+
+### OpenTelemetry Integration
+
+```go
+import (
+ "go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"
+ "google.golang.org/grpc"
+)
+
+srv := grpc.NewServer(
+ grpc.StatsHandler(otelgrpc.NewServerHandler()),
+)
+
+// Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.Dial.
+conn, err := grpc.Dial(
+ target,
+ grpc.WithStatsHandler(otelgrpc.NewClientHandler()),
+)
+```
+
+## Testing
+
+### bufconn In-Process Test
+
+```go
+package service_test
+
+import (
+ "context"
+ "net"
+ "testing"
+ "time"
+
+ "google.golang.org/grpc"
+ "google.golang.org/grpc/credentials/insecure"
+ "google.golang.org/grpc/status"
+ "google.golang.org/grpc/codes"
+ "google.golang.org/grpc/test/bufconn"
+
+ apiv1 "github.com/org/repo/gen/api/v1"
+)
+
+func TestListUsers(t *testing.T) {
+ lis := bufconn.Listen(1 << 20)
+ srv := grpc.NewServer()
+ apiv1.RegisterUserServiceServer(srv, &fakeUserSvc{})
+ go func() {
+ if err := srv.Serve(lis); err != nil {
+ t.Logf("server exited: %v", err)
+ }
+ }()
+ t.Cleanup(srv.GracefulStop)
+
+ // Note: for gRPC-Go v1.63+, use grpc.NewClient instead of grpc.DialContext.
+ conn, err := grpc.DialContext(context.Background(),
+ "bufnet",
+ grpc.WithContextDialer(func(ctx context.Context, _ string) (net.Conn, error) {
+ return lis.DialContext(ctx)
+ }),
+ grpc.WithTransportCredentials(insecure.NewCredentials()),
+ )
+ if err != nil {
+ t.Fatalf("dial bufnet: %v", err)
+ }
+ t.Cleanup(func() { conn.Close() })
+
+ client := apiv1.NewUserServiceClient(conn)
+ ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second)
+ defer cancel()
+
+ resp, err := client.ListUsers(ctx, &apiv1.ListUsersRequest{PageSize: 10})
+ if code := status.Code(err); code != codes.OK {
+ t.Fatalf("expected OK, got %v: %v", code, err)
+ }
+ if resp == nil {
+ t.Fatal("expected non-nil response")
+ }
+}
+```
+
+## Streaming Handler Pattern
+
+Always check `ctx.Done()` in streaming loops. Never expose raw internal errors to clients.
+
+```go
+func (s *userService) WatchUsers(
+ req *apiv1.WatchUsersRequest,
+ stream apiv1.UserService_WatchUsersServer,
+) error {
+ ctx := stream.Context()
+
+ events := s.subscribeUserEvents()
+ defer s.unsubscribe(events)
+
+ for {
+ select {
+ case <-ctx.Done():
+ // Client disconnected or deadline exceeded; exit cleanly.
+ return status.Error(codes.Canceled, "client disconnected")
+
+ case event, ok := <-events:
+ if !ok {
+ // Channel closed; server is shutting down.
+ return status.Error(codes.Unavailable, "service shutting down")
+ }
+
+ if err := stream.Send(event); err != nil {
+ // Log the raw error server-side for diagnostics.
+ log.Printf("stream send failed: %v", err)
+ // Return a generic message to the client; never leak raw err.
+ return status.Error(codes.Internal, "failed to send event")
+ }
+ }
+ }
+}
+```
+
+## Error Mapping
+
+Map domain errors to gRPC status codes consistently:
+
+Only return `err.Error()` to clients when it is a safe, user-facing domain message (not an internal error string).
+
+```go
+package service
+
+import (
+ "errors"
+
+ "google.golang.org/grpc/codes"
+ "google.golang.org/grpc/status"
+)
+
+var (
+ ErrNotFound = errors.New("resource not found")
+ ErrAlreadyExists = errors.New("resource already exists")
+ ErrInvalidInput = errors.New("invalid input")
+ ErrPermission = errors.New("permission denied")
+)
+
+// toGRPCError maps a domain error to a gRPC status error.
+func toGRPCError(err error) error {
+ if err == nil {
+ return nil
+ }
+ switch {
+ case errors.Is(err, ErrNotFound):
+ return status.Error(codes.NotFound, err.Error())
+ case errors.Is(err, ErrAlreadyExists):
+ return status.Error(codes.AlreadyExists, err.Error())
+ case errors.Is(err, ErrInvalidInput):
+ return status.Error(codes.InvalidArgument, err.Error())
+ case errors.Is(err, ErrPermission):
+ return status.Error(codes.PermissionDenied, err.Error())
+ default:
+ return status.Error(codes.Internal, "internal error")
+ }
+}
+```
+
+## Project Layout
+
+```
+project/
+ buf.gen.yaml
+ buf.yaml
+ proto/
+ api/
+ v1/
+ user_service.proto
+ gen/ # Generated code (committed or gitignored)
+ api/
+ v1/
+ user_service.pb.go
+ user_service_grpc.pb.go
+ internal/
+ service/
+ user.go # Service implementation
+ user_test.go # bufconn tests
+ domain/
+ errors.go # Domain error definitions
+ cmd/
+ server/
+ main.go # Server entrypoint with graceful shutdown
+ config/
+ config.go # Env-based config (timeouts, TLS paths, limits)
+```
+
+## Safety Checklist
+
+- Default to TLS/mTLS for all production traffic.
+- Enforce limits (`MaxRecvMsgSize`, `MaxSendMsgSize`, metadata size) to reduce resource exhaustion.
+- Treat client-sent metadata as untrusted; validate and allowlist keys used for auth or tenant routing.
+- Disable gRPC reflection in production to avoid exposing internal service schemas.
+- Check `context.Done()` in every iteration of a streaming handler to prevent goroutine leaks.
+
+## Anti-Patterns
+
+| Anti-Pattern | Why It Hurts | Fix |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| Create new `grpc.ClientConn` per request | Exhausts OS sockets and disables HTTP/2 multiplexing, causing high latency and resource leaks | Initialize once, reuse globally |
+| Mix Protobuf v1 and v2 libraries | Causes silent marshaling bugs; `proto.Marshal` from v1 and v2 are NOT interchangeable | Pin to `google.golang.org/protobuf` (v2) throughout |
+| Expose raw internal error strings to clients | Leaks stack traces and internal service names; a security and UX risk | Map errors with `status.Errorf` using appropriate gRPC codes |
+| Ignore `context.Done()` in streaming handlers | Goroutine and connection leak when client disconnects | Check `ctx.Err()` in every iteration of a streaming loop |
+| Skip error handling with `_ =` | Hides failures silently; production outages become undiagnosable | Always check and handle errors explicitly |
+| Use `grpc.Dial` without health checks | Connection failures are deferred and may surface as runtime errors | Use health checks and monitor connection state |
+
+> **Migration note**: For gRPC-Go v1.63+ (Jan 2024), `grpc.NewClient` is the newer API recommended by the gRPC-Go project for new code. For older versions (or when following existing codebases and official grpc.io examples), using `grpc.Dial` / `grpc.DialContext` is still common.
diff --git a/web-app/public/skills/hig-components-content/SKILL.md b/web-app/public/skills/hig-components-content/SKILL.md
index 5e6e86d9..e5083edf 100644
--- a/web-app/public/skills/hig-components-content/SKILL.md
+++ b/web-app/public/skills/hig-components-content/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-content
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about
"charts component", "collection view", "image view", "web view", "color well", "image well",
"activity view", "lockup", "data visualization", "content display", displaying images, rendering
diff --git a/web-app/public/skills/hig-components-controls/SKILL.md b/web-app/public/skills/hig-components-controls/SKILL.md
index 3bfe5397..ae7fdb11 100644
--- a/web-app/public/skills/hig-components-controls/SKILL.md
+++ b/web-app/public/skills/hig-components-controls/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-controls
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for selection and input controls including pickers, toggles,
sliders, steppers, segmented controls, combo boxes, text fields, text views,
labels, token fields, virtual keyboards, rating indicators, and gauges. Use
diff --git a/web-app/public/skills/hig-components-dialogs/SKILL.md b/web-app/public/skills/hig-components-dialogs/SKILL.md
index 1242ca6c..ce2ea3ea 100644
--- a/web-app/public/skills/hig-components-dialogs/SKILL.md
+++ b/web-app/public/skills/hig-components-dialogs/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-dialogs
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for presentation components including alerts, action sheets,
popovers, sheets, and digit entry views. Use this skill when the user says
"should I use an alert or a sheet," "how do I show a confirmation dialog,"
diff --git a/web-app/public/skills/hig-components-layout/SKILL.md b/web-app/public/skills/hig-components-layout/SKILL.md
index fd26bda2..f4c44de8 100644
--- a/web-app/public/skills/hig-components-layout/SKILL.md
+++ b/web-app/public/skills/hig-components-layout/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-layout
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user
asks about "sidebar", "split view", "tab bar", "tab view", "scroll view", "window design", "panel",
"list view", "table view", "column view", "outline view", "navigation structure", "app layout",
diff --git a/web-app/public/skills/hig-components-menus/SKILL.md b/web-app/public/skills/hig-components-menus/SKILL.md
index b75247a5..6a3b2892 100644
--- a/web-app/public/skills/hig-components-menus/SKILL.md
+++ b/web-app/public/skills/hig-components-menus/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-menus
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for menu and button components including menus, context menus,
dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons,
pull-down buttons, disclosure controls, and standard buttons. Use this skill
diff --git a/web-app/public/skills/hig-components-search/SKILL.md b/web-app/public/skills/hig-components-search/SKILL.md
index af722b5d..71f35232 100644
--- a/web-app/public/skills/hig-components-search/SKILL.md
+++ b/web-app/public/skills/hig-components-search/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-search
version: 1.0.0
-description: ">-"
+description: >-
Apple HIG guidance for navigation-related components including search fields,
page controls, and path controls. Use this skill when the user says "how should
search work in my app," "I need a breadcrumb," "how do I paginate content," or
diff --git a/web-app/public/skills/hig-components-status/SKILL.md b/web-app/public/skills/hig-components-status/SKILL.md
index de026f09..20586287 100644
--- a/web-app/public/skills/hig-components-status/SKILL.md
+++ b/web-app/public/skills/hig-components-status/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-status
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for status and progress UI components including progress indicators,
status bars, and activity rings. Use this skill when asked about: "progress indicator",
"progress bar", "loading spinner", "status bar", "activity ring", "progress display",
diff --git a/web-app/public/skills/hig-components-system/SKILL.md b/web-app/public/skills/hig-components-system/SKILL.md
index ccf7ed22..cf87dc15 100644
--- a/web-app/public/skills/hig-components-system/SKILL.md
+++ b/web-app/public/skills/hig-components-system/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-components-system
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for system experience components: widgets, live activities,
notifications, complications, home screen quick actions, top shelf, watch faces,
app clips, and app shortcuts. Use when asked about: "widget design", "live activity",
diff --git a/web-app/public/skills/hig-foundations/SKILL.md b/web-app/public/skills/hig-foundations/SKILL.md
index 294e1baa..821c237b 100644
--- a/web-app/public/skills/hig-foundations/SKILL.md
+++ b/web-app/public/skills/hig-foundations/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-foundations
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines design foundations. Use this skill when the user asks about
"HIG color", "Apple typography", "SF Symbols", "dark mode guidelines", "accessible design",
"Apple design foundations", "app icon", "layout guidelines", "materials", "motion", "privacy",
diff --git a/web-app/public/skills/hig-inputs/SKILL.md b/web-app/public/skills/hig-inputs/SKILL.md
index 199f52a5..dc00c8a6 100644
--- a/web-app/public/skills/hig-inputs/SKILL.md
+++ b/web-app/public/skills/hig-inputs/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-inputs
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil,
keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system,
remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions.
diff --git a/web-app/public/skills/hig-patterns/SKILL.md b/web-app/public/skills/hig-patterns/SKILL.md
index 2114dd74..33deb5c4 100644
--- a/web-app/public/skills/hig-patterns/SKILL.md
+++ b/web-app/public/skills/hig-patterns/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-patterns
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about
"onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern",
"settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics",
diff --git a/web-app/public/skills/hig-platforms/SKILL.md b/web-app/public/skills/hig-platforms/SKILL.md
index 85eacd9e..df3a5fce 100644
--- a/web-app/public/skills/hig-platforms/SKILL.md
+++ b/web-app/public/skills/hig-platforms/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-platforms
version: 1.0.0
-description: ">"
+description: >
Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about
"designing for iOS", "iPad app design", "macOS design", "tvOS", "visionOS", "watchOS", "Apple platform",
"which platform", platform differences, platform-specific conventions, or multi-platform app design.
diff --git a/web-app/public/skills/hig-project-context/SKILL.md b/web-app/public/skills/hig-project-context/SKILL.md
index 1a49d8d1..95037430 100644
--- a/web-app/public/skills/hig-project-context/SKILL.md
+++ b/web-app/public/skills/hig-project-context/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-project-context
version: 1.0.0
-description: ">-"
+description: >-
Create or update a shared Apple design context document that other HIG skills
use to tailor guidance. Use when the user says "set up my project context,"
"what platforms am I targeting," "configure HIG settings," or when starting a
diff --git a/web-app/public/skills/hig-technologies/SKILL.md b/web-app/public/skills/hig-technologies/SKILL.md
index abb66f63..556cc949 100644
--- a/web-app/public/skills/hig-technologies/SKILL.md
+++ b/web-app/public/skills/hig-technologies/SKILL.md
@@ -1,7 +1,7 @@
---
name: hig-technologies
version: 1.0.0
-description: ">"
+description: >
Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit,
HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple,
SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps,
diff --git a/web-app/public/skills/hr-pro/SKILL.md b/web-app/public/skills/hr-pro/SKILL.md
index b9607f97..c3d81cd4 100644
--- a/web-app/public/skills/hr-pro/SKILL.md
+++ b/web-app/public/skills/hr-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: hr-pro
-description: "Professional, ethical HR partner for hiring,"
+description: |
+ Professional, ethical HR partner for hiring,
onboarding/offboarding, PTO and leave, performance, compliant policies, and
employee relations. Ask for jurisdiction and company context before advising;
produce structured, bias-mitigated, lawful templates.
diff --git a/web-app/public/skills/hybrid-cloud-architect/SKILL.md b/web-app/public/skills/hybrid-cloud-architect/SKILL.md
index cb7eaf2d..bf3b6bbe 100644
--- a/web-app/public/skills/hybrid-cloud-architect/SKILL.md
+++ b/web-app/public/skills/hybrid-cloud-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: hybrid-cloud-architect
-description: "Expert hybrid cloud architect specializing in complex multi-cloud"
+description: |
+ Expert hybrid cloud architect specializing in complex multi-cloud
solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters
hybrid connectivity, workload placement optimization, edge computing, and
cross-cloud automation. Handles compliance, cost optimization, disaster
diff --git a/web-app/public/skills/imagen/SKILL.md b/web-app/public/skills/imagen/SKILL.md
index 1497cc89..92b0bb50 100644
--- a/web-app/public/skills/imagen/SKILL.md
+++ b/web-app/public/skills/imagen/SKILL.md
@@ -1,6 +1,6 @@
---
name: imagen
-description: "|"
+description: |
source: "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
risk: safe
---
diff --git a/web-app/public/skills/incident-responder/SKILL.md b/web-app/public/skills/incident-responder/SKILL.md
index f78f9519..0ec76b66 100644
--- a/web-app/public/skills/incident-responder/SKILL.md
+++ b/web-app/public/skills/incident-responder/SKILL.md
@@ -1,6 +1,7 @@
---
name: incident-responder
-description: "Expert SRE incident responder specializing in rapid problem"
+description: |
+ Expert SRE incident responder specializing in rapid problem
resolution, modern observability, and comprehensive incident management.
Masters incident command, blameless post-mortems, error budget management, and
system reliability patterns. Handles critical outages, communication
diff --git a/web-app/public/skills/inventory-demand-planning/SKILL.md b/web-app/public/skills/inventory-demand-planning/SKILL.md
new file mode 100644
index 00000000..933d7e1d
--- /dev/null
+++ b/web-app/public/skills/inventory-demand-planning/SKILL.md
@@ -0,0 +1,239 @@
+---
+name: inventory-demand-planning
+description: >
+ Codified expertise for demand forecasting, safety stock optimisation,
+ replenishment planning, and promotional lift estimation at multi-location
+ retailers. Informed by demand planners with 15+ years experience managing
+ hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis,
+ seasonal transition management, and vendor negotiation frameworks.
+ Use when forecasting demand, setting safety stock, planning replenishment,
+ managing promotions, or optimising inventory levels.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "📊"
+---
+
+## When to Use
+
+Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.
+
+# Inventory Demand Planning
+
+## Role and Context
+
+You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.
+
+## Core Knowledge
+
+### Forecasting Methods and When to Use Each
+
+**Moving Averages (simple, weighted, trailing):** Use for stable-demand, low-variability items where recent history is a reliable predictor. A 4-week simple moving average works for commodity staples. Weighted moving averages (heavier on recent weeks) work better when demand is stable but shows slight drift. Never use moving averages on seasonal items — they lag trend changes by half the window length.
+
+**Exponential Smoothing (single, double, triple):** Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand with noise. Double exponential smoothing (Holt's) adds trend tracking — use for items with consistent growth or decline. Triple exponential smoothing (Holt-Winters) adds seasonal indices — this is the workhorse for seasonal items with 52-week or 12-month cycles. The alpha/beta/gamma parameters are critical: high alpha (>0.3) chases noise in volatile items; low alpha (<0.1) responds too slowly to regime changes. Optimize on holdout data, never on the same data used for fitting.
+
+**Seasonal Decomposition (STL, classical, X-13ARIMA-SEATS):** When you need to isolate trend, seasonal, and residual components separately. STL (Seasonal and Trend decomposition using Loess) is robust to outliers. Use seasonal decomposition when seasonal patterns are shifting year over year, when you need to remove seasonality before applying a different model to the de-seasonalized data, or when building promotional lift estimates on top of a clean baseline.
+
+**Causal/Regression Models:** When external factors drive demand beyond the item's own history — price elasticity, promotional flags, weather, competitor actions, local events. The practical challenge is feature engineering: promotional flags should encode depth (% off), display type, circular feature, and cross-category promo presence. Overfitting on sparse promo history is the single biggest pitfall. Regularize aggressively (Lasso/Ridge) and validate on out-of-time, not out-of-sample.
+
+**Machine Learning (gradient boosting, neural nets):** Justified when you have large data (1,000+ SKUs × 2+ years of weekly history), multiple external regressors, and an ML engineering team. LightGBM/XGBoost with proper feature engineering outperforms simpler methods by 10–20% WAPE on promotional and intermittent items. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.
+
+### Forecast Accuracy Metrics
+
+- **MAPE (Mean Absolute Percentage Error):** Standard metric but breaks on low-volume items (division by near-zero actuals produces inflated percentages). Use only for items averaging 50+ units/week.
+- **Weighted MAPE (WMAPE):** Sum of absolute errors divided by sum of actuals. Prevents low-volume items from dominating the metric. This is the metric finance cares about because it reflects dollars.
+- **Bias:** Average signed error. Positive bias = forecast systematically too high (overstock risk). Negative bias = systematically too low (stockout risk). Bias < ±5% is healthy. Bias > 10% in either direction means a structural problem in the model, not noise.
+- **Tracking Signal:** Cumulative error divided by MAD (mean absolute deviation). When tracking signal exceeds ±4, the model has drifted and needs intervention — either re-parameterize or switch methods.
+
+### Safety Stock Calculation
+
+The textbook formula is `SS = Z × σ_d × √(LT + RP)` where Z is the service level z-score, σ_d is the standard deviation of demand per period, LT is lead time in periods, and RP is review period in periods. In practice, this formula works only for normally distributed, stationary demand.
+
+**Service Level Targets:** 95% service level (Z=1.65) is standard for A-items. 99% (Z=2.33) for critical/A+ items where stockout cost dwarfs holding cost. 90% (Z=1.28) is acceptable for C-items. Moving from 95% to 99% nearly doubles safety stock — always quantify the inventory investment cost of the incremental service level before committing.
+
+**Lead Time Variability:** When vendor lead times are uncertain, use `SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)` — this captures both demand variability and lead time variability. Vendors with coefficient of variation (CV) on lead time > 0.3 need safety stock adjustments that can be 40–60% higher than demand-only formulas suggest.
+
+**Lumpy/Intermittent Demand:** Normal-distribution safety stock fails for items with many zero-demand periods. Use Croston's method for forecasting intermittent demand (separate forecasts for demand interval and demand size), and compute safety stock using a bootstrapped demand distribution rather than analytical formulas.
+
+**New Products:** No demand history means no σ_d. Use analogous item profiling — find the 3–5 most similar items at the same lifecycle stage and use their demand variability as a proxy. Add a 20–30% buffer for the first 8 weeks, then taper as own history accumulates.
+
+### Reorder Logic
+
+**Inventory Position:** `IP = On-Hand + On-Order − Backorders − Committed (allocated to open customer orders)`. Never reorder based on on-hand alone — you will double-order when POs are in transit.
+
+**Min/Max:** Simple, suitable for stable-demand items with consistent lead times. Min = average demand during lead time + safety stock. Max = Min + EOQ. When IP drops to Min, order up to Max. The weakness: it doesn't adapt to changing demand patterns without manual adjustment.
+
+**Reorder Point / EOQ:** ROP = average demand during lead time + safety stock. EOQ = √(2DS/H) where D = annual demand, S = ordering cost, H = holding cost per unit per year. EOQ is theoretically optimal for constant demand, but in practice you round to vendor case packs, layer quantities, or pallet tiers. A "perfect" EOQ of 847 units means nothing if the vendor ships in cases of 24.
+
+**Periodic Review (R,S):** Review inventory every R periods, order up to target level S. Better when you consolidate orders to a vendor on fixed days (e.g., Tuesday orders for Thursday pickup). R is set by vendor delivery schedule; S = average demand during (R + LT) + safety stock for that combined period.
+
+**Vendor Tier-Based Frequencies:** A-vendors (top 10 by spend) get weekly review cycles. B-vendors (next 20) get bi-weekly. C-vendors (remaining) get monthly. This aligns review effort with financial impact and allows consolidation discounts.
+
+### Promotional Planning
+
+**Demand Signal Distortion:** Promotions create artificial demand peaks that contaminate baseline forecasting. Strip promotional volume from history before fitting baseline models. Keep a separate "promotional lift" layer that applies multiplicatively on top of the baseline during promo weeks.
+
+**Lift Estimation Methods:** (1) Year-over-year comparison of promoted vs. non-promoted periods for the same item. (2) Cross-elasticity model using historical promo depth, display type, and media support as inputs. (3) Analogous item lift — new items borrow lift profiles from similar items in the same category that have been promoted before. Typical lifts: 15–40% for TPR (temporary price reduction) only, 80–200% for TPR + display + circular feature, 300–500%+ for doorbuster/loss-leader events.
+
+**Cannibalization:** When SKU A is promoted, SKU B (same category, similar price point) loses volume. Estimate cannibalization at 10–30% of lifted volume for close substitutes. Ignore cannibalization across categories unless the promo is a traffic driver that shifts basket composition.
+
+**Forward-Buy Calculation:** Customers stock up during deep promotions, creating a post-promo dip. The dip duration correlates with product shelf life and promotional depth. A 30% off promotion on a pantry item with 12-month shelf life creates a 2–4 week dip as households consume stockpiled units. A 15% off promotion on a perishable produces almost no dip.
+
+**Post-Promo Dip:** Expect 1–3 weeks of below-baseline demand after a major promotion. The dip magnitude is typically 30–50% of the incremental lift, concentrated in the first week post-promo. Failing to forecast the dip leads to excess inventory and markdowns.
+
+### ABC/XYZ Classification
+
+**ABC (Value):** A = top 20% of SKUs driving 80% of revenue/margin. B = next 30% driving 15%. C = bottom 50% driving 5%. Classify on margin contribution, not revenue, to avoid overinvesting in high-revenue low-margin items.
+
+**XYZ (Predictability):** X = CV of demand < 0.5 (highly predictable). Y = CV 0.5–1.0 (moderately predictable). Z = CV > 1.0 (erratic/lumpy). Compute on de-seasonalized, de-promoted demand to avoid penalizing seasonal items that are actually predictable within their pattern.
+
+**Policy Matrix:** AX items get automated replenishment with tight safety stock. AZ items need human review every cycle — they're high-value but erratic. CX items get automated replenishment with generous review periods. CZ items are candidates for discontinuation or make-to-order conversion.
+
+### Seasonal Transition Management
+
+**Buy Timing:** Seasonal buys (e.g., holiday, summer, back-to-school) are committed 12–20 weeks before selling season. Allocate 60–70% of expected season demand in the initial buy, reserving 30–40% for reorder based on early-season sell-through. This "open-to-buy" reserve is your hedge against forecast error.
+
+**Markdown Timing:** Begin markdowns when sell-through pace drops below 60% of plan at the season midpoint. Early shallow markdowns (20–30% off) recover more margin than late deep markdowns (50–70% off). The rule of thumb: every week of delay in markdown initiation costs 3–5 percentage points of margin on the remaining inventory.
+
+**Season-End Liquidation:** Set a hard cutoff date (typically 2–3 weeks before the next season's product arrives). Everything remaining at cutoff goes to outlet, liquidator, or donation. Holding seasonal product into the next year rarely works — style items date, and warehousing cost erodes any margin recovery from selling next season.
+
+## Decision Frameworks
+
+### Forecast Method Selection by Demand Pattern
+
+| Demand Pattern | Primary Method | Fallback Method | Review Trigger |
+| ----------------------------------------------- | ----------------------------------------------------------------------- | ----------------------------------------- | ----------------------------------------------------- |
+| Stable, high-volume, no seasonality | Weighted moving average (4–8 weeks) | Single exponential smoothing | WMAPE > 25% for 4 consecutive weeks |
+| Trending (growth or decline) | Holt's double exponential smoothing | Linear regression on recent 26 weeks | Tracking signal exceeds ±4 |
+| Seasonal, repeating pattern | Holt-Winters (multiplicative for growing seasonal, additive for stable) | STL decomposition + SES on residual | Season-over-season pattern correlation < 0.7 |
+| Intermittent / lumpy (>30% zero-demand periods) | Croston's method or SBA (Syntetos-Boylan Approximation) | Bootstrap simulation on demand intervals | Mean inter-demand interval shifts by >30% |
+| Promotion-driven | Causal regression (baseline + promo lift layer) | Analogous item lift + baseline | Post-promo actuals deviate >40% from forecast |
+| New product (0–12 weeks history) | Analogous item profile with lifecycle curve | Category average with decay toward actual | Own-data WMAPE stabilizes below analogous-based WMAPE |
+| Event-driven (weather, local events) | Regression with external regressors | Manual override with documented rationale | |
+
+### Safety Stock Service Level Selection
+
+| Segment | Target Service Level | Z-Score | Rationale |
+| ------------------------------------- | -------------------- | --------- | -------------------------------------------------------------------------------------------- |
+| AX (high-value, predictable) | 97.5% | 1.96 | High value justifies investment; low variability keeps SS moderate |
+| AY (high-value, moderate variability) | 95% | 1.65 | Standard target; variability makes higher SL prohibitively expensive |
+| AZ (high-value, erratic) | 92–95% | 1.41–1.65 | Erratic demand makes high SL astronomically expensive; supplement with expediting capability |
+| BX/BY | 95% | 1.65 | Standard target |
+| BZ | 90% | 1.28 | Accept some stockout risk on mid-tier erratic items |
+| CX/CY | 90–92% | 1.28–1.41 | Low value doesn't justify high SS investment |
+| CZ | 85% | 1.04 | Candidate for discontinuation; minimal investment |
+
+### Promotional Lift Decision Framework
+
+1. **Is there historical lift data for this SKU-promo type combination?** → Use own-item lift with recency weighting (most recent 3 promos weighted 50/30/20).
+2. **No own-item data but same category has been promoted?** → Use analogous item lift adjusted for price point and brand tier.
+3. **Brand-new category or promo type?** → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the promo period.
+4. **Cross-promoted with another category?** → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity coefficient if available; default 0.15 lift for cross-category halo.
+5. **Always model the post-promo dip.** Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.
+
+### Markdown Timing Decision
+
+| Sell-Through at Season Midpoint | Action | Expected Margin Recovery |
+| ------------------------------- | ------------------------------------------------------------------------------------ | ------------------------- |
+| ≥ 80% of plan | Hold price. Reorder cautiously if weeks of supply < 3. | Full margin |
+| 60–79% of plan | Take 20–25% markdown. No reorder. | 70–80% of original margin |
+| 40–59% of plan | Take 30–40% markdown immediately. Cancel any open POs. | 50–65% of original margin |
+| < 40% of plan | Take 50%+ markdown. Explore liquidation channels. Flag buying error for post-mortem. | 30–45% of original margin |
+
+### Slow-Mover Kill Decision
+
+Evaluate quarterly. Flag for discontinuation when ALL of the following are true:
+
+- Weeks of supply > 26 at current sell-through rate
+- Last 13-week sales velocity < 50% of the item's first 13 weeks (lifecycle declining)
+- No promotional activity planned in the next 8 weeks
+- Item is not contractually obligated (planogram commitment, vendor agreement)
+- Replacement or substitution SKU exists or category can absorb the gap
+
+If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escalate to 50% off or liquidation. Set a hard exit date 8 weeks from first markdown. Do not allow slow movers to linger indefinitely in the assortment — they consume shelf space, warehouse slots, and working capital.
+
+## Key Edge Cases
+
+Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md).
+
+1. **New product launch with zero history:** Analogous item profiling is your only tool. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.
+
+2. **Viral social media spike:** Demand jumps 500–2,000% with no warning. Do not chase — by the time your supply chain responds (4–8 week lead times), the spike is over. Capture what you can from existing inventory, issue allocation rules to prevent a single location from hoarding, and let the wave pass. Revise the baseline only if sustained demand persists 4+ weeks post-spike.
+
+3. **Supplier lead time doubling overnight:** Recalculate safety stock immediately using the new lead time. If SS doubles, you likely cannot fill the gap from current inventory. Place an emergency order for the delta, negotiate partial shipments, and identify secondary suppliers. Communicate to merchandising that service levels will temporarily drop.
+
+4. **Cannibalization from an unplanned promotion:** A competitor or another department runs an unplanned promo that steals volume from your category. Your forecast will over-project. Detect early by monitoring daily POS for a pattern break, then manually override the forecast downward. Defer incoming orders if possible.
+
+5. **Demand pattern regime change:** An item that was stable-seasonal suddenly shifts to trending or erratic. Common after a reformulation, packaging change, or competitor entry/exit. The old model will fail silently. Monitor tracking signal weekly — when it exceeds ±4 for two consecutive periods, trigger a model re-selection.
+
+6. **Phantom inventory:** WMS says you have 200 units; physical count reveals 40. Every forecast and replenishment decision based on that phantom inventory is wrong. Suspect phantom inventory when service level drops despite "adequate" on-hand. Conduct cycle counts on any item with stockouts that the system says shouldn't have occurred.
+
+7. **Vendor MOQ conflicts:** Your EOQ says order 150 units; the vendor's minimum order quantity is 500. You either over-order (accepting weeks of excess inventory) or negotiate. Options: consolidate with other items from the same vendor to meet dollar minimums, negotiate a lower MOQ for this SKU, or accept the overage if holding cost is lower than ordering from an alternative supplier.
+
+8. **Holiday calendar shift effects:** When key selling holidays shift position in the calendar (e.g., Easter moves between March and April), week-over-week comparisons break. Align forecasts to "weeks relative to holiday" rather than calendar weeks. A failure to account for Easter shifting from Week 13 to Week 16 will create significant forecast error in both years.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Vendor routine reorder:** Transactional, brief, PO-reference-driven. "PO #XXXX for delivery week of MM/DD per our agreed schedule."
+- **Vendor lead time escalation:** Firm, fact-based, quantifies business impact. "Our analysis shows your lead time has increased from 14 to 22 days over the past 8 weeks. This has resulted in X stockout events. We need a corrective plan by [date]."
+- **Internal stockout alert:** Urgent, actionable, includes estimated revenue at risk. Lead with the customer impact, not the inventory metric. "SKU X will stock out at 12 locations by Thursday. Estimated lost sales: $XX,000. Recommended action: [expedite/reallocate/substitute]."
+- **Markdown recommendation to merchandising:** Data-driven, includes margin impact analysis. Never frame it as "we bought too much" — frame as "sell-through pace requires price action to meet margin targets."
+- **Promotional forecast submission:** Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
+- **New product forecast assumptions:** Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."
+
+Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ----------------------------------------------------- | ------------------------------------------------------ | -------------------------- |
+| Projected stockout on A-item within 7 days | Alert demand planning manager + category merchant | Within 4 hours |
+| Vendor confirms lead time increase > 25% | Notify supply chain director; recalculate all open POs | Within 1 business day |
+| Promotional forecast miss > 40% (over or under) | Post-promo debrief with merchandising and vendor | Within 1 week of promo end |
+| Excess inventory > 26 weeks of supply on any A/B item | Markdown recommendation to merchandising VP | Within 1 week of detection |
+| Forecast bias exceeds ±10% for 4 consecutive weeks | Model review and re-parameterization | Within 2 weeks |
+| New product sell-through < 40% of plan after 4 weeks | Assortment review with merchandising | Within 1 week |
+| Service level drops below 90% for any category | Root cause analysis and corrective plan | Within 48 hours |
+
+### Escalation Chain
+
+Level 1 (Demand Planner) → Level 2 (Planning Manager, 24 hours) → Level 3 (Director of Supply Chain Planning, 48 hours) → Level 4 (VP Supply Chain, 72+ hours or any A-item stockout at enterprise customer)
+
+## Performance Indicators
+
+Track weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------- | ------------ | ------------------- |
+| WMAPE (weighted mean absolute percentage error) | < 25% | > 35% |
+| Forecast bias | ±5% | > ±10% for 4+ weeks |
+| In-stock rate (A-items) | > 97% | < 94% |
+| In-stock rate (all items) | > 95% | < 92% |
+| Weeks of supply (aggregate) | 4–8 weeks | > 12 or < 3 |
+| Excess inventory (>26 weeks supply) | < 5% of SKUs | > 10% of SKUs |
+| Dead stock (zero sales, 13+ weeks) | < 2% of SKUs | > 5% of SKUs |
+| Purchase order fill rate from vendors | > 95% | < 90% |
+| Promotional forecast accuracy (WMAPE) | < 35% | > 50% |
+
+## Additional Resources
+
+- For detailed decision frameworks, optimization models, and method selection trees, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **forecast demand and shape inventory policy across SKUs, stores, and vendors**:
+
+- Selecting and tuning forecasting methods, safety stock policies, and reorder logic for different demand patterns.
+- Planning promotions, seasonal transitions, markdowns, and end‑of‑life strategies while balancing service, cash, and margin.
+- Investigating chronic stockouts, excess inventory, or forecast bias and redesigning the planning process with clearer decision frameworks.
diff --git a/web-app/public/skills/inventory-demand-planning/references/communication-templates.md b/web-app/public/skills/inventory-demand-planning/references/communication-templates.md
new file mode 100644
index 00000000..eea6c365
--- /dev/null
+++ b/web-app/public/skills/inventory-demand-planning/references/communication-templates.md
@@ -0,0 +1,566 @@
+# Communication Templates — Inventory Demand Planning
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing demand planning communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and purpose. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Vendor Replenishment Order](#1-vendor-replenishment-order)
+2. [Vendor Lead Time Escalation](#2-vendor-lead-time-escalation)
+3. [Internal Stockout Alert](#3-internal-stockout-alert)
+4. [Markdown Recommendation to Merchandising](#4-markdown-recommendation-to-merchandising)
+5. [Promotional Forecast Submission](#5-promotional-forecast-submission)
+6. [Safety Stock Adjustment Request](#6-safety-stock-adjustment-request)
+7. [New Product Forecast Assumptions](#7-new-product-forecast-assumptions)
+8. [Excess Inventory Liquidation Plan](#8-excess-inventory-liquidation-plan)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{po_number}}` | Purchase order number | `PO-2025-08843` |
+| `{{sku}}` | SKU or item number | `SKU-44281` |
+| `{{sku_description}}` | Product description | `Organic Olive Oil 16oz` |
+| `{{vendor_name}}` | Vendor company name | `Mediterranean Imports LLC` |
+| `{{vendor_contact}}` | Vendor contact name | `Marco Bellini` |
+| `{{vendor_contact_email}}` | Vendor contact email | `m.bellini@medimports.com` |
+| `{{our_contact_name}}` | Our planner name | `Sarah Kim` |
+| `{{our_contact_title}}` | Our planner title | `Senior Demand Planner` |
+| `{{our_contact_email}}` | Our planner email | `s.kim@retailco.com` |
+| `{{our_contact_phone}}` | Our planner phone | `(404) 555-0192` |
+| `{{our_company}}` | Our company name | `RetailCo` |
+| `{{dc_location}}` | Distribution center location | `Nashville, TN DC` |
+| `{{delivery_date}}` | Requested delivery date | `2025-09-22` |
+| `{{order_qty}}` | Order quantity | `1,200 units (100 cases)` |
+| `{{current_on_hand}}` | Current on-hand inventory | `840 units` |
+| `{{weeks_of_supply}}` | Weeks of supply at current rate | `4.2 weeks` |
+| `{{weekly_demand}}` | Average weekly demand | `200 units/week` |
+| `{{category}}` | Product category | `Cooking Oils` |
+| `{{store_count}}` | Number of affected stores | `85 stores` |
+| `{{abc_class}}` | ABC classification | `A-item` |
+| `{{service_level_target}}` | Target service level | `97%` |
+| `{{current_service_level}}` | Current service level | `91%` |
+| `{{revenue_at_risk}}` | Estimated revenue at risk | `$18,400/week` |
+| `{{promo_start}}` | Promotion start date | `2025-10-05` |
+| `{{promo_end}}` | Promotion end date | `2025-10-18` |
+| `{{promo_type}}` | Promotion type | `TPR 25% off + circular feature` |
+| `{{baseline_forecast}}` | Baseline forecast | `500 units/week` |
+| `{{lift_estimate}}` | Promotional lift estimate | `180% (900 incremental units)` |
+| `{{markdown_pct}}` | Markdown percentage | `30%` |
+| `{{excess_units}}` | Excess inventory units | `3,200 units` |
+| `{{excess_wos}}` | Excess weeks of supply | `18.4 weeks` |
+
+---
+
+## 1. Vendor Replenishment Order
+
+### When to Use
+- Standard replenishment order based on forecast and inventory position.
+- No urgency beyond normal lead time expectations.
+
+### Tone Guidance
+Transactional and efficient. The vendor receives dozens of these daily. Be clear, reference the PO, specify quantities, delivery date, and delivery location. No need for pleasantries beyond professional courtesy.
+
+### What NOT to Say
+- Do not include forecast data or inventory levels in routine POs — this is proprietary information.
+- Do not request lead time changes or raise performance issues in a PO communication.
+
+### Template
+
+**Subject:** `PO {{po_number}} — {{vendor_name}} — Delivery {{delivery_date}}`
+
+---
+
+{{vendor_contact}},
+
+Please find below our purchase order for delivery to {{dc_location}}.
+
+**PO Number:** {{po_number}}
+**Requested Delivery Date:** {{delivery_date}}
+**Ship-To:** {{dc_location}}
+
+| SKU | Description | Qty (units) | Qty (cases) | Unit Cost | Line Total |
+|---|---|---|---|---|---|
+| {{sku}} | {{sku_description}} | {{order_qty}} | {{cases}} | {{unit_cost}} | {{line_total}} |
+
+**Order Total:** {{order_total}}
+
+Please confirm receipt and expected ship date within 2 business days.
+
+If any items are unavailable or quantities will be shorted, notify us immediately at {{our_contact_email}} so we can adjust our planning.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 2. Vendor Lead Time Escalation
+
+### When to Use
+- Vendor's actual lead times have exceeded the stated/contracted lead time by >20% for 3+ consecutive orders.
+- Lead time variability is causing stockouts or excessive safety stock costs.
+- You need a formal escalation before involving procurement or vendor management.
+
+### Tone Guidance
+Firm and data-driven. You are not complaining — you are presenting evidence and requesting a corrective action plan. Lead with the impact to your business, not the vendor's failure. Offer collaboration: you want to solve this together, but you need a commitment.
+
+### What NOT to Say
+- Do not threaten to switch vendors in this communication (that's a procurement conversation).
+- Do not speculate on the cause of the lead time issue — let the vendor explain.
+- Do not use vague language like "often late" — provide specific PO numbers, dates, and deviations.
+
+### Template
+
+**Subject:** `Lead Time Performance Review — {{vendor_name}} — Action Required by {{deadline_date}}`
+
+---
+
+{{vendor_contact}},
+
+I'm writing to address a consistent lead time issue that is impacting our inventory planning for your product line.
+
+**Summary of the Problem:**
+
+Over the past {{time_period}}, we have observed the following lead time performance on our orders:
+
+| PO Number | Order Date | Stated Lead Time | Actual Lead Time | Deviation |
+|---|---|---|---|---|
+| {{po_1}} | {{date_1}} | {{stated_lt}} days | {{actual_lt_1}} days | +{{dev_1}} days |
+| {{po_2}} | {{date_2}} | {{stated_lt}} days | {{actual_lt_2}} days | +{{dev_2}} days |
+| {{po_3}} | {{date_3}} | {{stated_lt}} days | {{actual_lt_3}} days | +{{dev_3}} days |
+
+**Average stated lead time:** {{stated_lt}} days
+**Average actual lead time:** {{actual_lt_avg}} days (+{{pct_increase}}%)
+**Lead time coefficient of variation:** {{lt_cv}}
+
+**Impact to Our Business:**
+
+This lead time increase has required us to:
+- Increase safety stock by {{ss_increase_pct}}%, tying up an additional ${{ss_cost_increase}} in working capital
+- Experience {{stockout_count}} stockout events on {{sku_description}} in the past {{time_period}}, with estimated lost sales of ${{lost_sales}}
+- Expedite {{expedite_count}} orders at an additional cost of ${{expedite_cost}}
+
+**What We Need:**
+
+1. A written explanation of the root cause of the lead time increase by {{deadline_date}}.
+2. A corrective action plan with a committed timeline to return to the stated {{stated_lt}}-day lead time.
+3. If the lead time increase is permanent, we need an updated lead time commitment so we can recalibrate our planning parameters.
+
+We value our partnership with {{vendor_name}} and want to resolve this collaboratively. I'm available to discuss on a call at your convenience this week.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}} | {{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Internal Stockout Alert
+
+### When to Use
+- Projected stockout on an A or B-item within 7 days based on current inventory position and demand forecast.
+- Actual stockout occurring at 3+ locations.
+- Any stockout where revenue at risk exceeds $10,000/week.
+
+### Tone Guidance
+Urgent, concise, action-oriented. The audience is internal (planning manager, category merchant, supply chain director). Lead with the impact, follow with the facts, close with the recommended action. This is not a post-mortem — it's a call to action.
+
+### What NOT to Say
+- Do not assign blame in the alert (e.g., "because the buyer didn't order enough"). That's for the post-mortem.
+- Do not present multiple options without a recommendation — decision-makers need a clear ask.
+
+### Template
+
+**Subject:** `🔴 STOCKOUT ALERT — {{sku_description}} — {{store_count}} locations at risk`
+
+---
+
+**Attention:** {{recipient_names}}
+
+**Item:** {{sku}} — {{sku_description}}
+**ABC Class:** {{abc_class}}
+**Current Status:** {{current_status}} (e.g., "Out of stock at 8 locations; projected stockout at 22 additional locations by {{stockout_date}}")
+
+**Inventory Position:**
+- DC On-Hand: {{dc_on_hand}} units
+- Store On-Hand (aggregate): {{store_on_hand}} units
+- On-Order: {{on_order}} units (ETA: {{on_order_eta}})
+- Weekly Demand: {{weekly_demand}}
+- Weeks of Supply (current): {{weeks_of_supply}}
+
+**Revenue at Risk:** ${{revenue_at_risk}}/week across {{store_count}} locations
+
+**Root Cause:** {{root_cause}} (e.g., "Vendor shipment delayed by 10 days; demand running 20% above forecast due to competitive market exit")
+
+**Recommended Actions:**
+
+1. **Immediate:** {{action_1}} (e.g., "Reallocate 400 units from low-velocity stores to stockout locations — list attached")
+2. **Short-term:** {{action_2}} (e.g., "Expedite PO {{po_number}} — vendor confirmed can ship 800 units by {{expedite_date}} at ${{expedite_cost}} additional freight")
+3. **If above fails:** {{action_3}} (e.g., "Substitute with {{alt_sku}} — similar product, available in DC, can ship to affected stores within 48 hours")
+
+**Decision needed by:** {{decision_deadline}}
+
+Please reply or call me directly to confirm action.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_phone}}
+
+---
+
+## 4. Markdown Recommendation to Merchandising
+
+### When to Use
+- SKU or category has excess inventory exceeding 12 weeks of supply with no promotional activity planned.
+- Seasonal product with sell-through below 60% at season midpoint.
+- Slow-mover kill decision has been triggered.
+
+### Tone Guidance
+Data-driven and collaborative. You are presenting a financial analysis, not demanding a price change. Merchandising owns pricing decisions — your job is to provide the inventory data and margin impact analysis to inform their decision. Frame recommendations as margin recovery, not "we bought too much."
+
+### What NOT to Say
+- Do not say "we overbought" or "the forecast was wrong" — frame as "sell-through pace requires price action."
+- Do not propose a specific retail price — propose a markdown depth (% off) and let merchandising set the price.
+
+### Template
+
+**Subject:** `Markdown Recommendation — {{sku_description}} — {{excess_units}} units excess`
+
+---
+
+**To:** {{merchandising_contact}}
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+**Summary:**
+{{sku_description}} ({{sku}}) is carrying {{excess_units}} units of excess inventory representing {{excess_wos}} weeks of supply at current sell-through rates. Based on our analysis, a markdown is recommended to recover margin and free working capital before the inventory ages further.
+
+**Current Inventory Position:**
+
+| Metric | Value |
+|---|---|
+| On-Hand (DC + Stores) | {{total_on_hand}} units |
+| Weekly Demand (trailing 4-week avg) | {{weekly_demand}} |
+| Weeks of Supply | {{excess_wos}} |
+| Seasonal Window Remaining | {{season_weeks_remaining}} weeks |
+| Current Sell-Through vs. Plan | {{sell_through_pct}}% |
+
+**Financial Analysis:**
+
+| Scenario | Markdown Depth | Projected Velocity | Weeks to Clear | Margin Recovery |
+|---|---|---|---|---|
+| No action | 0% | {{current_velocity}} units/week | {{wos_no_action}} weeks | {{margin_no_action}} |
+| Option A | {{md_depth_a}}% | {{velocity_a}} units/week | {{wos_a}} weeks | {{margin_a}} |
+| Option B | {{md_depth_b}}% | {{velocity_b}} units/week | {{wos_b}} weeks | {{margin_b}} |
+| Liquidation | Cost recovery | Immediate | 1–2 weeks | {{margin_liquidation}} |
+
+**Recommendation:** Option {{recommended_option}} ({{md_depth_recommended}}% markdown) offers the best margin recovery of {{margin_recommended}} while clearing inventory within {{wos_recommended}} weeks.
+
+**Holding Cost of Inaction:** Carrying this excess for another {{delay_weeks}} weeks costs approximately ${{holding_cost}} in inventory carrying costs and risks additional obsolescence if the product ages or a seasonal window closes.
+
+**Next Steps:**
+If approved, we can execute the markdown effective {{proposed_start_date}} and monitor weekly sell-through against the projected velocity.
+
+Happy to discuss the analysis in detail.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Promotional Forecast Submission
+
+### When to Use
+- Submitting the demand forecast for a planned promotion to supply chain, merchandising, and vendor partners.
+- Required 6–8 weeks before promotion start date to allow for procurement.
+
+### Tone Guidance
+Structured and transparent. This document is the "source of truth" for promotional inventory planning. Include all assumptions, the baseline, the lift estimate, and the post-promo dip so that all stakeholders can challenge or validate the numbers before POs are placed.
+
+### What NOT to Say
+- Do not present a single point estimate without a confidence range — this gives false precision.
+- Do not omit the post-promo dip — it's as important as the lift.
+
+### Template
+
+**Subject:** `Promotional Forecast — {{sku_description}} — {{promo_start}} to {{promo_end}}`
+
+---
+
+**To:** Supply Chain Planning, Category Merchandising, {{vendor_name}} (if applicable)
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+**Promotion:** {{promo_description}}
+
+---
+
+### Promotion Details
+
+| Field | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Promotion Period | {{promo_start}} — {{promo_end}} ({{promo_weeks}} weeks) |
+| Promotion Type | {{promo_type}} |
+| Promotional Retail Price | ${{promo_price}} (regular: ${{reg_price}}, {{discount_pct}}% off) |
+| Media Support | {{media_support}} (e.g., "Circular page 3 + endcap display") |
+| Stores Participating | {{store_count}} of {{total_stores}} |
+
+### Forecast
+
+| Period | Baseline Forecast | Lift Estimate | Total Forecast | Confidence Range (±) |
+|---|---|---|---|---|
+| Pre-promo (week before) | {{baseline}} units | — | {{baseline}} units | — |
+| Promo Week 1 | {{baseline}} | +{{lift_wk1}}% ({{lift_units_1}} units) | {{total_wk1}} units | ±{{conf_1}}% |
+| Promo Week 2 | {{baseline}} | +{{lift_wk2}}% ({{lift_units_2}} units) | {{total_wk2}} units | ±{{conf_2}}% |
+| Post-Promo Week 1 | {{baseline}} | −{{dip_wk1}}% ({{dip_units_1}} units) | {{post_1}} units | ±{{conf_post_1}}% |
+| Post-Promo Week 2 | {{baseline}} | −{{dip_wk2}}% ({{dip_units_2}} units) | {{post_2}} units | ±{{conf_post_2}}% |
+| Recovery (Week 3+) | {{baseline}} | — | {{baseline}} units | — |
+
+**Total Promotional Period Demand:** {{total_promo_demand}} units
+**Total Incremental Demand (above baseline):** {{incremental_demand}} units
+
+### Assumptions and Methodology
+
+1. **Baseline:** {{baseline_method}} (e.g., "Holt-Winters model fitted on de-promoted trailing 52-week data")
+2. **Lift source:** {{lift_source}} (e.g., "Average of 3 most recent comparable promotions on this SKU, weighted 50/30/20 by recency")
+3. **Cannibalization:** Estimated {{cannibalization_pct}}% cannibalization from {{cannibalized_sku}}, reducing net category lift to {{net_category_lift}}%
+4. **Post-promo dip:** Based on {{dip_source}} (e.g., "Product type: shelf-stable pantry; historical dip factor 45% of incremental lift")
+5. **Confidence range:** Based on historical promotional forecast accuracy for this category (trailing 12-month promo WMAPE: {{promo_wmape}}%)
+
+### Inventory Requirements
+
+| Item | Quantity |
+|---|---|
+| Current on-hand (DC + pipeline) | {{current_inventory}} units |
+| Total demand through post-promo recovery | {{total_demand}} units |
+| Gap to fill | {{gap_units}} units |
+| Recommended PO quantity | {{po_qty}} units ({{cases}} cases) |
+| PO must arrive by | {{po_arrive_by}} ({{lead_time_buffer}} days before promo start) |
+
+### Risks
+
+- **Upside risk:** If lift exceeds {{upside_lift}}%, we may stock out in week 2 of the promotion. Contingency: {{contingency_up}}.
+- **Downside risk:** If lift is below {{downside_lift}}%, we will carry {{excess_if_low}} excess units post-promo, requiring {{excess_weeks}} additional weeks to sell through.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 6. Safety Stock Adjustment Request
+
+### When to Use
+- Demand variability or lead time variability has changed, requiring a safety stock parameter update.
+- Service level targets have been revised (up or down) for a segment or individual SKU.
+- Post a supply disruption or regime change that permanently alters risk parameters.
+
+### Tone Guidance
+Analytical and justified. Every safety stock change is an inventory investment change. Present the before/after calculation, the reason for the change, and the financial impact (incremental holding cost or reduced stockout risk).
+
+### Template
+
+**Subject:** `Safety Stock Adjustment — {{sku_description}} — {{adjustment_direction}} by {{adjustment_pct}}%`
+
+---
+
+**To:** {{planning_manager}}, {{finance_contact}} (if material)
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+**Item:** {{sku}} — {{sku_description}} ({{abc_class}})
+
+### Reason for Adjustment
+
+{{reason}} (e.g., "Vendor lead time has increased from 14 days to 28 days effective 2025-09-01. Lead time variability has also increased, with CV rising from 0.12 to 0.31.")
+
+### Calculation
+
+| Parameter | Previous | Updated | Change |
+|---|---|---|---|
+| Average weekly demand | {{prev_demand}} units | {{new_demand}} units | {{demand_change}} |
+| Demand std. deviation (σ_d) | {{prev_sigma_d}} units | {{new_sigma_d}} units | {{sigma_d_change}} |
+| Lead time (weeks) | {{prev_lt}} weeks | {{new_lt}} weeks | {{lt_change}} |
+| Lead time std. deviation (σ_LT) | {{prev_sigma_lt}} weeks | {{new_sigma_lt}} weeks | {{sigma_lt_change}} |
+| Service level target | {{service_level}} | {{service_level}} | No change |
+| Z-score | {{z_score}} | {{z_score}} | No change |
+| **Safety stock (units)** | **{{prev_ss}}** | **{{new_ss}}** | **+{{ss_delta}} units** |
+
+### Financial Impact
+
+- Incremental inventory investment: {{ss_delta}} units × ${{unit_cost}} = ${{incremental_investment}}
+- Annual holding cost increase: ${{incremental_investment}} × {{holding_cost_pct}}% = ${{annual_holding_increase}}
+- Expected stockout reduction: from {{prev_stockout_events}} events/year to {{new_stockout_events}} events/year
+- Estimated recovered revenue: ${{recovered_revenue}}/year
+
+**Net impact:** {{net_assessment}} (e.g., "The $2,400 annual holding cost increase is justified by the $18,000 in projected recovered revenue from reduced stockouts.")
+
+### Approval Requested By
+
+{{deadline}} — needed before the next replenishment cycle to take effect.
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 7. New Product Forecast Assumptions
+
+### When to Use
+- Documenting the forecast basis for a new product launch with < 8 weeks of own-history data.
+- Required at the pre-launch planning meeting and updated at the 4-week and 8-week checkpoints.
+
+### Tone Guidance
+Transparent and falsifiable. The purpose of this document is to make every assumption explicit so that the post-mortem can identify where the forecast diverged from reality. Do not hedge with vague language — state the assumptions clearly so they can be validated or disproved.
+
+### Template
+
+**Subject:** `New Product Forecast Assumptions — {{sku_description}} — Launch {{launch_date}}`
+
+---
+
+**To:** Category Merchandising, Supply Chain Planning, Finance
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+### Product Details
+
+| Field | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Category | {{category}} / {{subcategory}} |
+| Retail Price | ${{retail_price}} |
+| Unit Cost | ${{unit_cost}} |
+| Gross Margin | {{gross_margin_pct}}% |
+| Launch Date | {{launch_date}} |
+| Initial Distribution | {{store_count}} stores ({{pct_of_chain}}% of chain) |
+| Vendor | {{vendor_name}} |
+| Lead Time | {{lead_time}} weeks |
+| Shelf Life | {{shelf_life}} |
+
+### Analogous Items Selected
+
+| Analog SKU | Description | Similarity Score | Launch Velocity (wks 1–13) | Current Velocity |
+|---|---|---|---|---|
+| {{analog_1_sku}} | {{analog_1_desc}} | {{analog_1_score}}/5.0 | {{analog_1_launch_vel}} units/store/week | {{analog_1_current_vel}} |
+| {{analog_2_sku}} | {{analog_2_desc}} | {{analog_2_score}}/5.0 | {{analog_2_launch_vel}} units/store/week | {{analog_2_current_vel}} |
+| {{analog_3_sku}} | {{analog_3_desc}} | {{analog_3_score}}/5.0 | {{analog_3_launch_vel}} units/store/week | {{analog_3_current_vel}} |
+
+**Weighted average analog velocity (weeks 1–13):** {{weighted_avg_vel}} units/store/week
+
+### Forecast by Phase
+
+| Phase | Weeks | Velocity (units/store/wk) | Total Weekly Demand ({{store_count}} stores) | Confidence Band |
+|---|---|---|---|---|
+| Introduction | 1–4 | {{intro_vel}} | {{intro_weekly}} units | ±{{intro_conf}}% |
+| Growth | 5–8 | {{growth_vel}} | {{growth_weekly}} units | ±{{growth_conf}}% |
+| Stabilization | 9–13 | {{stable_vel}} | {{stable_weekly}} units | ±{{stable_conf}}% |
+
+### Key Assumptions
+
+1. {{assumption_1}} (e.g., "Product will receive endcap display in all {{store_count}} stores for weeks 1–4")
+2. {{assumption_2}} (e.g., "No direct competitor launch in the same subcategory during the launch window")
+3. {{assumption_3}} (e.g., "Price point is within the category's high-volume range ($3–$5)")
+4. {{assumption_4}} (e.g., "Vendor will maintain {{lead_time}}-week lead time for reorders")
+
+### Initial Buy and Reorder Plan
+
+| Component | Quantity | Timing |
+|---|---|---|
+| Initial buy | {{initial_buy}} units | PO placed {{initial_po_date}} |
+| Safety stock | {{initial_ss}} units (analog-based, 30% uncertainty premium) | Included in initial buy |
+| First reorder trigger | If week 1–2 velocity > {{reorder_trigger}} units/store/week | Auto-trigger PO |
+| Reserve for reorder | {{reserve_units}} units (held at vendor or allocated in budget) | Weeks 3–5 |
+
+### Monitoring Plan
+
+| Checkpoint | Date | Metric | Action if Below Plan | Action if Above Plan |
+|---|---|---|---|---|
+| Week 2 | {{wk2_date}} | Velocity vs. {{intro_vel}} target | Review display compliance; consider early promo | Place reorder for 50% of reserve |
+| Week 4 | {{wk4_date}} | Sell-through vs. initial buy | Flag for promotional support | Place reorder for remaining reserve |
+| Week 8 | {{wk8_date}} | Velocity trend (growing/declining/stable) | Initiate slow-mover review if declining for 4 wks | Upgrade to standard forecasting method |
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}}
+
+---
+
+## 8. Excess Inventory Liquidation Plan
+
+### When to Use
+- SKU has been classified as dead stock (zero sales for 13+ weeks) or critical excess (>26 weeks of supply).
+- Seasonal product with unsold inventory after the markdown selling window.
+- Discontinued product with remaining inventory after final markdown.
+
+### Tone Guidance
+Pragmatic and action-oriented. The liquidation plan is an acknowledgment that margin recovery is limited and the priority has shifted to cash recovery and warehouse space liberation. Present the options dispassionately — the goal is to make the best of a bad situation, not to relitigate the buying decision.
+
+### Template
+
+**Subject:** `Excess Inventory Liquidation Plan — {{sku_description}} — {{excess_units}} units`
+
+---
+
+**To:** {{merchandising_contact}}, {{finance_contact}}, {{warehouse_contact}}
+**From:** {{our_contact_name}}, {{our_contact_title}}
+**Date:** {{date}}
+
+### Inventory Summary
+
+| Metric | Value |
+|---|---|
+| SKU | {{sku}} — {{sku_description}} |
+| Current On-Hand | {{excess_units}} units |
+| Original Cost | ${{unit_cost}} per unit (${{total_cost}} total) |
+| Current Retail | ${{current_retail}} (after markdowns) |
+| Weekly Demand (trailing 8 weeks) | {{weekly_demand}} units |
+| Weeks of Supply | {{excess_wos}} |
+| Reason for Excess | {{reason}} |
+
+### Liquidation Options Analysis
+
+| Option | Recovery per Unit | Total Recovery | Timeline | Pros | Cons |
+|---|---|---|---|---|---|
+| **A: Deeper markdown ({{md_depth}}% off)** | ${{recovery_a}} | ${{total_a}} | {{timeline_a}} weeks | Retains customer; recovers shelf space gradually | Margin erosion; may not clear |
+| **B: Liquidation channel** | ${{recovery_b}} | ${{total_b}} | {{timeline_b}} weeks | Immediate clearance; frees space | Very low recovery; no brand control |
+| **C: Donation (tax write-off)** | ${{recovery_c}} (tax benefit) | ${{total_c}} | {{timeline_c}} weeks | Goodwill; tax benefit; immediate space recovery | No cash recovery |
+| **D: Destroy / write-off** | $0 | $0 | Immediate | Frees space immediately; clean books | Total loss; disposal cost of ${{disposal_cost}} |
+
+### Recommendation
+
+Option {{recommended_option}} is recommended based on the following rationale:
+
+{{recommendation_rationale}} (e.g., "Option B (liquidation) recovers $3,200 compared to Option A's $4,100 — but Option A requires 8 more weeks of shelf space that has a higher-value alternative use. The opportunity cost of holding the shelf space exceeds the $900 margin difference.")
+
+### Execution Plan
+
+| Step | Action | Owner | Deadline |
+|---|---|---|---|
+| 1 | Approve liquidation plan | {{approver}} | {{approval_date}} |
+| 2 | Remove from active replenishment | Demand Planning | {{replenishment_stop_date}} |
+| 3 | {{action_3}} | {{owner_3}} | {{date_3}} |
+| 4 | {{action_4}} | {{owner_4}} | {{date_4}} |
+| 5 | Confirm zero on-hand; close SKU in system | Warehouse / IT | {{close_date}} |
+
+### Financial Summary
+
+| Line Item | Amount |
+|---|---|
+| Original inventory investment | ${{total_cost}} |
+| Revenue recovered (to date, markdowns) | ${{markdown_revenue}} |
+| Projected recovery (this plan) | ${{projected_recovery}} |
+| **Total write-down** | **${{total_writedown}}** |
+
+### Post-Mortem Assignment
+
+Root cause analysis for this excess is assigned to {{postmortem_owner}} with a due date of {{postmortem_date}}. The analysis should address: Was this a forecast error, a buying decision error, a market change, or a timing issue? What process change would prevent recurrence?
+
+{{our_contact_name}}
+{{our_contact_title}} | {{our_contact_email}} | {{our_contact_phone}}
diff --git a/web-app/public/skills/inventory-demand-planning/references/decision-frameworks.md b/web-app/public/skills/inventory-demand-planning/references/decision-frameworks.md
new file mode 100644
index 00000000..7d7827cd
--- /dev/null
+++ b/web-app/public/skills/inventory-demand-planning/references/decision-frameworks.md
@@ -0,0 +1,861 @@
+# Decision Frameworks — Inventory Demand Planning
+
+This reference provides the detailed decision logic, optimization models, method selection
+trees, and segmentation methodologies for inventory demand planning at multi-location
+retailers. It is loaded on demand when the agent needs to make or recommend nuanced
+planning decisions.
+
+All thresholds, formulas, and cost assumptions reflect US multi-location retail operations
+managing hundreds of SKUs across grocery, general merchandise, seasonal, and promotional
+categories.
+
+---
+
+## 1. Forecast Method Selection Trees
+
+### 1.1 Primary Selection Algorithm
+
+The goal is to match each SKU to the forecasting method that minimizes WMAPE on out-of-time
+holdout data. In practice, most organizations cannot afford per-SKU model optimization
+across hundreds of items. Instead, classify items into demand pattern archetypes and assign
+methods by archetype.
+
+#### Step 1 — Classify the Demand Pattern
+
+Compute the following statistics on the most recent 52 weeks of de-promoted demand data
+(remove promotional lift periods before computing):
+
+| Statistic | Formula | Purpose |
+|---|---|---|
+| **Coefficient of Variation (CV)** | σ_demand / μ_demand | Measures demand variability |
+| **Average Demand Interval (ADI)** | Total periods / Number of non-zero demand periods | Measures intermittency |
+| **Trend Strength** | R² of linear regression on 26-week trailing demand | Measures directional movement |
+| **Seasonal Strength** | Autocorrelation at lag 52 (weekly) or lag 12 (monthly) | Measures repeating seasonal pattern |
+| **Zero-Demand Ratio** | Count of zero-demand periods / Total periods | Measures how often demand is absent |
+
+#### Step 2 — Map to Demand Archetype
+
+| Archetype | CV | ADI | Trend R² | Seasonal AC | Zero Ratio | Example |
+|---|---|---|---|---|---|---|
+| **Smooth** | < 0.5 | 1.0–1.1 | < 0.3 | < 0.3 | < 5% | Milk, bread, paper towels |
+| **Trending** | < 0.7 | 1.0–1.2 | ≥ 0.3 | < 0.3 | < 10% | Growing brand, declining legacy item |
+| **Seasonal** | 0.3–1.0 | 1.0–1.3 | any | ≥ 0.3 | < 15% | Sunscreen, holiday decor, grills |
+| **Trending-Seasonal** | 0.4–1.2 | 1.0–1.3 | ≥ 0.3 | ≥ 0.3 | < 15% | Growing seasonal category |
+| **Erratic** | ≥ 0.7 | 1.0–1.5 | < 0.3 | < 0.3 | < 30% | Fashion accessories, novelty items |
+| **Intermittent** | any | ≥ 1.5 | any | any | ≥ 30% | Spare parts, specialty ingredients |
+| **Lumpy** | ≥ 1.0 | ≥ 1.5 | any | any | ≥ 30% | Bulk wholesale items with sporadic orders |
+
+#### Step 3 — Assign Forecasting Method
+
+| Archetype | Primary Method | Parameters | Fallback |
+|---|---|---|---|
+| **Smooth** | Weighted moving average (4–8 week window, recent-weighted) | Weights: 0.4/0.3/0.2/0.1 for 4-week | Single exponential smoothing (α = 0.15–0.25) |
+| **Trending** | Holt's double exponential smoothing | α = 0.2–0.4, β = 0.05–0.15 | Linear regression on trailing 26 weeks |
+| **Seasonal** | Holt-Winters (additive if stable amplitude, multiplicative if growing amplitude) | α = 0.1–0.3, β = 0.01–0.05, γ = 0.1–0.3, period = 52 weeks | STL decomposition + SES on residual |
+| **Trending-Seasonal** | Holt-Winters (multiplicative) | α = 0.2–0.4, β = 0.05–0.15, γ = 0.15–0.3 | X-13ARIMA-SEATS |
+| **Erratic** | Damped trend exponential smoothing | α = 0.2–0.4, β = 0.05, φ = 0.8–0.95 | Ensemble of 3 methods (median) |
+| **Intermittent** | Croston's method or SBA | α_demand = 0.1–0.2, α_interval = 0.1–0.2 | Bootstrap simulation (1000 draws) |
+| **Lumpy** | SBA (Syntetos-Boylan Approximation) | Same as Croston's with bias correction | Aggregated to monthly then disaggregated |
+
+### 1.2 Model Switching Rules
+
+Do not switch methods based on a single bad week. Models need time to prove or disprove themselves.
+
+| Condition | Action | Minimum Observation Period |
+|---|---|---|
+| WMAPE improves > 10% on holdout vs. current method | Switch to candidate method | 8-week parallel test |
+| Tracking signal exceeds ±4 for 2 consecutive periods | Trigger model review; re-estimate parameters first | 2 periods (weeks) |
+| Tracking signal exceeds ±6 for 1 period | Immediate model review; likely archetype change | 1 period |
+| Demand pattern archetype changes (e.g., smooth → trending) | Re-run selection algorithm from Step 1 | Quarterly archetype reassessment |
+| New product transitions from analog-based to own-history | Switch when 12+ weeks of own data available and own-data WMAPE < analog-based | 12 weeks |
+| Post-promotion baseline contamination detected | Refit baseline model excluding promo periods | Immediate |
+
+### 1.3 Parameter Optimization Protocol
+
+For exponential smoothing methods, optimize parameters using grid search on time-series
+cross-validation (rolling origin, 1-step ahead forecast, 26+ origins).
+
+**Grid search ranges:**
+
+| Parameter | Range | Step Size | Constraint |
+|---|---|---|---|
+| α (level) | 0.05–0.50 | 0.05 | — |
+| β (trend) | 0.01–0.20 | 0.01 | β ≤ α |
+| γ (seasonal) | 0.05–0.40 | 0.05 | — |
+| φ (damping) | 0.80–0.98 | 0.02 | Only for damped methods |
+
+**Optimization metric:** Minimize WMAPE on the holdout origins. If two parameter sets
+produce WMAPE within 1 percentage point, prefer the set with lower α (more smoothing)
+for stability.
+
+**Overfitting guard:** If the optimized model produces WMAPE on the holdout that is
+>5 percentage points better than on the fitting data, the model is likely overfit.
+Increase smoothing (lower α) until the gap narrows to <3 points.
+
+---
+
+## 2. Safety Stock Optimization Models
+
+### 2.1 Standard Safety Stock (Normal Demand, Fixed Lead Time)
+
+When demand follows a roughly normal distribution and lead time is consistent:
+
+```
+SS = Z × σ_d × √(LT)
+```
+
+Where:
+- Z = z-score for the target service level (see lookup table below)
+- σ_d = standard deviation of demand per period (use same period as LT)
+- LT = lead time in periods
+
+**Z-Score Lookup:**
+
+| Service Level | Z-Score | Typical Application |
+|---|---|---|
+| 85.0% | 1.04 | CZ items — minimal investment |
+| 90.0% | 1.28 | C-items, non-critical B-items |
+| 92.0% | 1.41 | Mid-range safety net |
+| 95.0% | 1.65 | Standard target for A/B items |
+| 97.5% | 1.96 | AX items — high value, predictable |
+| 99.0% | 2.33 | Critical items — stockout cost vastly exceeds holding |
+| 99.5% | 2.58 | Life-safety or contractual obligation items |
+| 99.9% | 3.09 | Rarely justified — extreme holding cost |
+
+### 2.2 Safety Stock with Lead Time Variability
+
+When vendor lead times are uncertain (CV of lead time > 0.15):
+
+```
+SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)
+```
+
+Where:
+- LT_avg = average lead time in periods
+- σ_LT = standard deviation of lead time in periods
+- d_avg = average demand per period
+
+**Practical note:** Many planners underestimate lead time variability because they
+measure "vendor ship date to DC receipt" without accounting for receiving delays,
+quality holds, or weekend/holiday dead time. Measure lead time from PO release to
+"available to sell" — this is the operationally relevant metric.
+
+### 2.3 Safety Stock with Review Period
+
+For periodic review systems (review every R periods):
+
+```
+SS = Z × σ_d × √(LT + R)
+```
+
+The review period adds exposure time — between reviews, you cannot react to demand
+changes. Weekly review (R=1) on a 2-week lead time item needs safety stock for √3 weeks.
+Monthly review (R=4) on the same item needs safety stock for √6 weeks — 41% more.
+
+### 2.4 Safety Stock for Intermittent Demand
+
+Normal-distribution formulas fail when demand has many zero periods. Use empirical
+(bootstrapped) safety stock instead:
+
+1. Collect the last 52 periods of demand data (include zeros).
+2. Generate 10,000 bootstrap samples of length (LT + R) by random sampling with
+ replacement from the historical demand.
+3. Compute the sum of each bootstrap sample (= simulated demand during lead time + review).
+4. The safety stock is the (service level)th percentile of the simulated demand totals
+ minus the mean simulated demand total.
+
+**Example:** For 95% service level, safety stock = P95 of bootstrap demand — mean of
+bootstrap demand. This captures the skewed, zero-inflated distribution that parametric
+formulas miss.
+
+### 2.5 Safety Stock for New Products (No History)
+
+When an item has < 8 weeks of own demand history:
+
+1. Identify 3–5 analogous items matching on: category, price point (±20%), brand tier
+ (national/private label), pack size, and target demographic.
+2. Compute the average σ_d and CV across the analogs.
+3. Apply a "new product uncertainty premium" of 1.25× to the analog σ_d.
+4. Use the standard formula with the inflated σ_d: `SS = Z × (1.25 × σ_d_analog) × √(LT + R)`.
+5. Every 2 weeks, blend own-history σ_d with the analog σ_d. By week 8, use 70% own history
+ and 30% analog. By week 12, use 100% own history.
+
+### 2.6 Safety Stock Cost-Optimization
+
+The naive approach is to set a service level target and compute SS. The sophisticated
+approach is to optimize the tradeoff between holding cost and stockout cost:
+
+```
+Optimal SL = 1 − (H / (H + S × D/Q))
+```
+
+Where:
+- H = holding cost per unit per period
+- S = stockout cost per unit (lost margin + customer goodwill + substitution cost)
+- D = demand per period
+- Q = order quantity
+
+For most retailers, stockout cost on A-items is 3–5× the unit margin (including lost
+customer visits and substitution effects), which pushes optimal SL to 96–98%.
+For C-items, stockout cost is approximately equal to the unit margin, yielding optimal
+SL of 88–92%.
+
+---
+
+## 3. Promotional Planning Frameworks
+
+### 3.1 Promotional Lift Estimation Methodology
+
+Promotional lift is always computed relative to the baseline forecast (the forecast that
+would have been generated without the promotion). Contaminating the baseline with
+promotional history is the #1 source of systematic forecast error in retail.
+
+#### Step 1 — Establish Clean Baseline
+
+Strip promotional periods from the demand history before fitting the baseline model.
+Flag weeks as "promotional" if any of the following were active:
+- Temporary price reduction (TPR) > 5% off regular price
+- Feature in circular, digital ad, or endcap display
+- BOGO or multi-buy offer
+- Cross-promotion in another category
+
+After stripping, interpolate the gaps using the forecast model fitted to non-promotional
+periods. This creates a "what would have sold at regular price" baseline.
+
+#### Step 2 — Compute Historical Lifts
+
+For each historical promotional event on this SKU:
+
+```
+Lift Ratio = Actual Promo-Period Sales / Baseline Forecast for Promo Period
+```
+
+A lift ratio of 2.5 means the promotion drove 2.5× baseline volume (150% incremental).
+
+Organize lift ratios by promotional mechanism:
+
+| Mechanism | Typical Lift Range | Key Drivers |
+|---|---|---|
+| TPR only (5–15% off) | 1.15–1.40 | Depth of discount, category elasticity |
+| TPR (15–30% off) | 1.40–2.00 | Deeper discount creates sharper response |
+| TPR + display | 1.80–2.50 | Display location (endcap > wing > inline) |
+| TPR + circular feature | 2.00–3.00 | Circular reach and placement (front page > interior) |
+| TPR + display + circular | 2.50–4.00 | Full support — this is the "A-level" promo |
+| BOGO | 2.50–5.00 | Perceived value drives high response but heavy forward-buy |
+| Doorbuster / loss leader | 3.00–6.00+ | Traffic driver; lift varies wildly by event |
+
+#### Step 3 — Apply Lift to Current Forecast
+
+```
+Promo Forecast = Baseline Forecast × Lift Ratio
+```
+
+When multiple promotional mechanisms are combined, do NOT multiply individual lifts.
+Use the combined-mechanism lift from historical data or the table above. The interaction
+effects are sub-additive (display alone = 1.5× and circular alone = 1.8× does not mean
+display + circular = 2.7×; it's typically 2.0–2.5×).
+
+#### Step 4 — Model the Post-Promotion Dip
+
+```
+Post-Promo Demand = Baseline × (1 − Dip Factor × Decay)
+```
+
+Default dip factors by product type:
+
+| Product Type | Dip Factor (% of incremental lift) | Dip Duration | Decay Pattern |
+|---|---|---|---|
+| **Shelf-stable pantry** | 40–60% | 2–4 weeks | 60/30/10 (Week 1/2/3) |
+| **Perishable / refrigerated** | 10–20% | 0–1 week | Immediate recovery |
+| **Household consumables** | 30–50% | 2–3 weeks | 50/35/15 |
+| **Personal care** | 25–40% | 2–3 weeks | 50/30/20 |
+| **Seasonal** | 15–30% | 1–2 weeks | 70/30 |
+| **Discretionary / general merch** | 10–25% | 1–2 weeks | 70/30 |
+
+### 3.2 Cannibalization Estimation
+
+When SKU A is promoted, substitutable SKU B loses sales. The cannibalization rate is:
+
+```
+Cannibalization Rate = ΔB_down / ΔA_up
+```
+
+Where ΔA_up is the incremental lift on A and ΔB_down is the volume loss on B during
+the same period.
+
+**Default estimates when no cross-elasticity data exists:**
+
+| Substitutability | Cannibalization Rate | Example |
+|---|---|---|
+| Direct substitute (same brand, different size) | 25–40% | 12-oz promoted, 16-oz loses |
+| Close substitute (different brand, same segment) | 15–25% | National brand promoted, private label loses |
+| Moderate substitute (same category, different segment) | 5–15% | Premium promoted, value tier affected |
+| Weak substitute (adjacent category) | 0–5% | Chips promoted, crackers slightly affected |
+
+**Important:** Cannibalization is bidirectional across the category. When building the
+category-level promotional plan, sum the cannibalization effects across all substitutes
+to compute the true category-level lift (which is always less than the item-level lift).
+
+### 3.3 Forward-Buy and Pantry Loading
+
+Deep promotions cause customers to purchase ahead of their consumption schedule.
+Forward-buy volume is demand pulled from future periods, not incremental category demand.
+
+**Forward-buy estimation:**
+
+```
+Forward-Buy Volume = Incremental Lift × Forward-Buy Factor
+```
+
+| Promotional Depth | Product Shelf Life | Forward-Buy Factor |
+|---|---|---|
+| 10–20% off | < 2 weeks (perishable) | 0.05–0.10 |
+| 10–20% off | 2–12 weeks | 0.10–0.20 |
+| 10–20% off | > 12 weeks (shelf-stable) | 0.20–0.35 |
+| 20–35% off | < 2 weeks | 0.05–0.15 |
+| 20–35% off | 2–12 weeks | 0.20–0.35 |
+| 20–35% off | > 12 weeks | 0.35–0.50 |
+| 35–50% off | < 2 weeks | 0.10–0.20 |
+| 35–50% off | 2–12 weeks | 0.30–0.45 |
+| 35–50% off | > 12 weeks | 0.50–0.70 |
+| BOGO / > 50% | Any | 0.50–0.80 |
+
+The forward-buy factor tells you what fraction of the incremental lift came from
+pantry loading rather than true consumption increase. This directly feeds the
+post-promo dip calculation — the dip is approximately equal to the forward-buy volume
+spread over its consumption period.
+
+### 3.4 Promotional Calendar Planning
+
+When planning the annual promotional calendar, apply these rules:
+
+1. **Minimum inter-promotion gap:** 4 weeks between promotions on the same SKU. Shorter
+ gaps train customers to only buy on deal, eroding brand equity and baseline velocity.
+2. **Maximum promotional frequency:** 13 weeks per year (25%) for any single SKU.
+ Beyond this, the "promotional price" becomes the reference price in consumers' minds.
+3. **Seasonal alignment:** Promote seasonal items during the build phase (first 40% of
+ the season), not during peak or decline. Promoting at peak wastes money on demand
+ that would have occurred anyway. Promoting during decline is a markdown, not a promotion.
+4. **Cross-category coordination:** Avoid promoting close substitutes simultaneously.
+ Stagger promotions across substitutes by at least 2 weeks to avoid self-cannibalization.
+5. **Vendor funding alignment:** Match promotional timing to vendor trade fund availability.
+ Many CPG manufacturers operate on calendar quarters — funds not committed by quarter-end
+ expire. Plan key promos in weeks 8–12 of each quarter when vendors are motivated to
+ spend remaining funds.
+
+---
+
+## 4. ABC/XYZ Segmentation Methodology
+
+### 4.1 ABC Classification (Value)
+
+ABC classification segments SKUs by their financial contribution. The classification
+drives differentiated investment in forecasting effort, safety stock, review frequency,
+and management attention.
+
+#### Classification Procedure
+
+1. **Select the value metric.** Options in order of preference:
+ - Gross margin contribution (best — focuses investment on profit, not revenue)
+ - Revenue (acceptable when margin data is unavailable)
+ - Unit volume (use only for warehouse space planning, not financial investment)
+
+2. **Compute trailing 52-week value** for each active SKU.
+
+3. **Sort descending** by the value metric.
+
+4. **Compute cumulative % of total value** and classify:
+
+| Class | Cumulative % of Value | Typical % of SKUs | Description |
+|---|---|---|---|
+| A | 0–80% | 10–20% | High-value items driving the business |
+| B | 80–95% | 20–30% | Mid-value items providing assortment breadth |
+| C | 95–100% | 50–70% | Long-tail items with minimal individual impact |
+
+5. **Exception overrides:**
+ - New items (< 13 weeks) are auto-classified one tier higher than their data suggests
+ until they have sufficient history. A new item computing as C is treated as B.
+ - Items with contractual obligations (planogram commitment, vendor agreement) are
+ classified minimum B regardless of current sales velocity.
+ - Items flagged as strategic by merchandising (e.g., traffic drivers, competitive
+ price match items) are classified minimum A.
+
+#### Reclassification Schedule
+
+Run ABC reclassification quarterly. Between quarters, items are reclassified only
+if they cross a threshold by >50% (e.g., an item must contribute >120% of the A/B
+boundary to move from B to A mid-quarter). This prevents oscillation at class boundaries.
+
+### 4.2 XYZ Classification (Predictability)
+
+XYZ classification segments SKUs by demand forecast difficulty. It drives differentiated
+forecasting method selection and safety stock strategies.
+
+#### Classification Procedure
+
+1. **Compute de-seasonalized, de-promoted demand** for each SKU over the trailing 52 weeks.
+ Remove seasonal indices and promotional lift periods so that the variability metric
+ reflects genuine demand uncertainty, not planned variation.
+
+2. **Compute the coefficient of variation (CV):**
+ ```
+ CV = σ_demand / μ_demand
+ ```
+ Use the de-seasonalized, de-promoted demand series.
+
+3. **Classify:**
+
+| Class | CV Range | Description | Forecast Difficulty |
+|---|---|---|---|
+| X | < 0.5 | Highly predictable — demand varies little around its mean | Low — simple methods work well |
+| Y | 0.5–1.0 | Moderately predictable — noticeable variability | Medium — requires good models and monitoring |
+| Z | > 1.0 | Erratic/lumpy — demand is highly variable or intermittent | High — no model will be highly accurate |
+
+4. **Supplement with ADI (Average Demand Interval):** Items with ADI > 2.0 (meaning
+ demand occurs less than every other period) should be classified Z regardless of CV,
+ because the intermittency itself creates forecast difficulty that CV alone doesn't capture.
+
+### 4.3 Combined ABC/XYZ Policy Matrix
+
+| Segment | Forecast Method | Safety Stock | Review Frequency | Replenishment | Management Attention |
+|---|---|---|---|---|---|
+| **AX** | Exponential smoothing (automated) | Z = 1.96 (97.5%) | Weekly | Automated with exception alerts | Monthly review |
+| **AY** | Holt-Winters or causal model | Z = 1.65 (95%) | Weekly | Automated with planner review | Bi-weekly review |
+| **AZ** | Ensemble or manual override | Z = 1.41–1.65 (92–95%) | Weekly | Planner-managed; never fully automated | Weekly review |
+| **BX** | Moving average (automated) | Z = 1.65 (95%) | Bi-weekly | Automated | Monthly review |
+| **BY** | Exponential smoothing (automated) | Z = 1.65 (95%) | Bi-weekly | Automated with exception alerts | Monthly review |
+| **BZ** | Croston's or damped trend | Z = 1.28 (90%) | Bi-weekly | Semi-automated with planner approval | Monthly review |
+| **CX** | Simple moving average | Z = 1.28 (90%) | Monthly | Automated | Quarterly review |
+| **CY** | Simple moving average | Z = 1.28 (90%) | Monthly | Automated | Quarterly review |
+| **CZ** | Croston's or none | Z = 1.04 (85%) | Monthly | Manual or min/max | Quarterly — discontinuation candidate |
+
+### 4.4 Migration Tracking
+
+Track SKU movement between segments quarterly. Key migration patterns to monitor:
+
+| Migration | Signal | Action |
+|---|---|---|
+| A → B | Revenue or margin declining | Investigate: is this category shrinkage, competitive loss, or assortment issue? |
+| B → A | Revenue or margin growing | Upgrade forecasting method and review frequency. Validate safety stock. |
+| X → Y or Z | Demand becoming less predictable | Check for demand pattern regime change. Review forecast model fit. Increase safety stock. |
+| Z → X or Y | Demand stabilizing | Possible to simplify forecast model. Review safety stock for reduction. |
+| Any → CZ | Low value + erratic | Strong discontinuation candidate. Run slow-mover kill decision. |
+
+---
+
+## 5. Vendor Management Decision Logic
+
+### 5.1 Vendor Tier Classification
+
+Classify vendors into tiers based on annual purchase volume, strategic importance,
+and supply risk profile:
+
+| Tier | Criteria | Count (typical) | Review Cadence |
+|---|---|---|---|
+| **Strategic** | Top 5 by spend, or sole-source for A-items | 3–8 | Monthly scorecards, quarterly business reviews |
+| **Preferred** | Top 20 by spend, multiple A/B items | 10–25 | Quarterly scorecards |
+| **Approved** | All remaining active vendors | 30–100+ | Annual review |
+| **Probationary** | Vendors under corrective action | Variable | Weekly monitoring, monthly review |
+
+### 5.2 Vendor Scorecard Metrics
+
+Score each vendor quarterly on a 0–100 scale across these dimensions:
+
+| Dimension | Weight | Metric | Target | Calculation |
+|---|---|---|---|---|
+| **On-time delivery** | 30% | % of POs delivered within the agreed window (±1 day) | > 95% | Score = (Actual % / 95%) × 100, cap at 100 |
+| **Fill rate** | 25% | % of ordered units actually shipped | > 97% | Score = (Actual % / 97%) × 100, cap at 100 |
+| **Lead time consistency** | 20% | CV of actual lead time vs. stated lead time | CV < 0.15 | Score = max(0, 100 − (CV − 0.15) × 500) |
+| **Quality** | 15% | % of received units passing QC inspection | > 99% | Score = (Actual % / 99%) × 100, cap at 100 |
+| **Responsiveness** | 10% | Average response time to inquiries/issues (hours) | < 24 hours | Score = max(0, 100 − (Avg Hours − 24) × 2) |
+
+**Composite score thresholds:**
+
+| Score Range | Rating | Action |
+|---|---|---|
+| 90–100 | Excellent | Consider for volume increase, preferred terms |
+| 75–89 | Good | Standard operations, no action needed |
+| 60–74 | Needs Improvement | Issue corrective action request; 90-day improvement plan |
+| < 60 | Unacceptable | Immediate escalation; begin qualifying alternative suppliers |
+
+### 5.3 Vendor Lead Time Management
+
+Lead time management is the demand planner's most underleveraged tool for reducing
+inventory investment. A 1-day reduction in lead time across all vendors can reduce
+aggregate safety stock by 5–8%.
+
+**Lead time decomposition:**
+
+| Component | Typical Range | Planner Influence |
+|---|---|---|
+| Order processing at vendor | 1–3 days | Low — vendor's internal process |
+| Production/picking | 2–10 days | Medium — negotiate priority tiers |
+| Vendor ship preparation | 1–2 days | Low |
+| Transit time | 1–14 days | Medium — carrier selection, mode choice |
+| Receiving and put-away | 1–3 days | High — internal process improvement |
+| Quality hold (if applicable) | 0–5 days | High — streamline QC process |
+
+**Actions to reduce lead time:**
+
+1. For strategic vendors: negotiate VMI (vendor-managed inventory) where the vendor
+ monitors your inventory and ships proactively. Eliminates order processing delay.
+2. For all vendors: provide rolling 8-week forecasts to allow pre-positioning. Reduces
+ production/picking time on non-stock items.
+3. Internally: invest in receiving automation (ASN-enabled receiving, barcode scanning)
+ to cut receiving from 2–3 days to same-day.
+4. Negotiate consolidated weekly shipments vs. per-PO shipments to reduce transit
+ frequency while maintaining fill rate.
+
+### 5.4 MOQ (Minimum Order Quantity) Negotiation Framework
+
+When a vendor's MOQ creates excess inventory, evaluate these options in order:
+
+| Option | When to Use | Expected Outcome |
+|---|---|---|
+| **Negotiate lower MOQ** | Annual spend > $50K with this vendor; you have leverage | MOQ reduced 20–40% |
+| **Consolidate with other SKUs** | Multiple SKUs from same vendor; dollar minimum instead of unit minimum | Meet dollar MOQ without over-ordering individual SKUs |
+| **Accept higher price for lower MOQ** | MOQ overage cost > price premium cost | Pay 3–8% more per unit but order only what you need |
+| **Negotiate consignment** | Slow-moving items from strategic vendors | Vendor owns inventory until you sell it |
+| **Split orders with another buyer** | Known network of retailers ordering from the same vendor | Share the MOQ and split the shipment |
+| **Accept the overage** | Holding cost for the excess is < $500 and item is non-perishable | Order the MOQ and treat the overage as forward inventory |
+
+### 5.5 Vendor Negotiation for Lead Time Reduction
+
+**Preparation checklist before negotiating:**
+
+1. Document your current order volume and growth trajectory with this vendor.
+2. Compute the cost of their current lead time to your business: excess safety stock
+ carrying cost + stockout cost from lead time variability.
+3. Identify what you can offer in return: longer-term commitments, higher volumes,
+ fewer order frequency changes, rolling forecasts.
+4. Know your BATNA (best alternative): have a qualified secondary supplier identified.
+
+**Negotiation structure:**
+
+1. Present the data: "Over the past 6 months, your average lead time has been X days
+ with a standard deviation of Y. This variability costs us $Z annually in excess
+ safety stock."
+2. Propose the target: "We're requesting a committed lead time of X−2 days with a
+ guarantee of CV < 0.15."
+3. Offer the exchange: "In return, we can commit to rolling 8-week forecasts updated
+ weekly, and we'll consolidate to 2 orders per week instead of daily."
+4. Set the timeline: "Let's implement this for Q2 and review the scorecard at the
+ end of Q2 QBR."
+
+---
+
+## 6. Seasonal Buy and Markdown Timing Models
+
+### 6.1 Seasonal Buy Planning
+
+Seasonal categories require forward commitments because lead times exceed the selling
+season. The buy decision has two components: the initial buy (pre-season) and the
+in-season reorder (if the vendor supports it).
+
+#### Initial Buy Calculation
+
+```
+Initial Buy = Season Forecast × Initial Commitment % − Carry-Over Inventory
+```
+
+| Category Risk Profile | Initial Commitment % | Reserve for Reorder | Rationale |
+|---|---|---|---|
+| Low risk (staple seasonal, proven seller) | 70–80% | 20–30% | High confidence in forecast; reorder available |
+| Medium risk (trend-influenced, moderate history) | 55–65% | 35–45% | Hedge against forecast error |
+| High risk (fashion, new trend, first season) | 40–50% | 50–60% | Maximize flexibility; accept possible stockout |
+| One-time buy (import, long lead, no reorder) | 100% | 0% | No reorder option; commit fully but forecast conservatively |
+
+#### In-Season Reorder Triggers
+
+Monitor sell-through rate weekly starting from week 2 of the season:
+
+```
+Sell-Through Rate = Units Sold / (Units Sold + Units On-Hand + Units On-Order)
+```
+
+| Weeks into Season | Sell-Through vs. Plan | Action |
+|---|---|---|
+| Weeks 1–2 | > 120% of plan | Issue reorder immediately for 50% of reserve allocation |
+| Weeks 1–2 | 80–120% of plan | Hold; too early to confirm trend |
+| Weeks 3–4 | > 110% of plan | Issue reorder for remaining reserve |
+| Weeks 3–4 | 90–110% of plan | Issue conservative reorder (25% of reserve) |
+| Weeks 3–4 | 70–89% of plan | Hold all reserve; prepare markdown contingency |
+| Weeks 3–4 | < 70% of plan | Cancel any open reorders; initiate early markdown |
+| Weeks 5+ | Any pace | Reorders unlikely to arrive in time; manage with markdowns |
+
+### 6.2 Markdown Timing and Depth Model
+
+The markdown decision balances margin recovery against sell-through velocity. Every
+week of delay costs margin because holding costs accrue and the remaining selling
+window shrinks.
+
+#### Markdown Decision Matrix
+
+| Weeks Remaining in Season | Weeks of Supply at Current Rate | Recommended Action |
+|---|---|---|
+| > 6 weeks | < 3 | No markdown; possible reorder |
+| > 6 weeks | 3–6 | Hold price; monitor weekly |
+| > 6 weeks | 7–10 | First markdown: 20–25% off |
+| > 6 weeks | > 10 | Aggressive markdown: 30–40% off |
+| 4–6 weeks | < 3 | No markdown needed |
+| 4–6 weeks | 3–6 | Consider 15–20% markdown |
+| 4–6 weeks | 6–10 | Markdown 25–35% |
+| 4–6 weeks | > 10 | Markdown 40–50%; explore liquidation |
+| 2–4 weeks | < 3 | No markdown |
+| 2–4 weeks | 3–6 | Markdown 30–40% |
+| 2–4 weeks | > 6 | Markdown 50–60%; liquidation channels |
+| < 2 weeks | Any remaining | Final clearance 60–75% off or liquidation |
+
+#### Markdown Velocity Curve
+
+After applying a markdown, monitor the velocity response:
+
+| Markdown Depth | Expected Velocity Increase | If Not Achieved Within 1 Week |
+|---|---|---|
+| 20% off | 1.5–2.0× | Deepen to 30% |
+| 30% off | 2.0–3.0× | Deepen to 40% |
+| 40% off | 3.0–4.0× | Deepen to 50% or explore liquidation |
+| 50% off | 4.0–6.0× | If still not moving, this is dead stock — liquidate |
+
+### 6.3 Season-End Liquidation Decision
+
+When the selling season is ending and inventory remains:
+
+```
+Liquidation Net Recovery = (Liquidation Price × Remaining Units) − Logistics Cost
+Hold-to-Next-Season Net = (Expected Sell Price × Sell-Through Estimate)
+ − Holding Cost − Obsolescence Risk
+```
+
+**Liquidation is preferred when:**
+- Hold-to-next-season sell-through estimate < 60% (style risk, trend change)
+- Holding cost for 9–12 months > 15% of original cost (typical for most retailers)
+- Warehouse space is constrained and the space has higher-value alternative use
+- The product is trend/fashion and will be visually dated next season
+
+**Holding is preferred when:**
+- Product is a classic/carryover style with minimal fashion risk
+- Hold-to-next-season sell-through estimate > 80%
+- Warehouse space is available at low marginal cost
+- Liquidation offers are below variable cost (you'd lose money selling)
+
+---
+
+## 7. New Product Introduction Forecasting
+
+### 7.1 Analogous Item Selection
+
+The quality of a new product forecast depends almost entirely on the quality of the
+analogous items selected. Bad analogs produce bad forecasts regardless of the method.
+
+#### Selection Criteria (rank by importance)
+
+| Criterion | Weight | How to Match |
+|---|---|---|
+| **Category/subcategory** | 25% | Must be same subcategory (e.g., "premium yogurt" not just "dairy") |
+| **Price point** | 20% | Within ±20% of the new item's retail price |
+| **Brand tier** | 15% | National brand → national brand analog; private label → private label |
+| **Pack size / format** | 15% | Similar unit count, size, or weight |
+| **Target demographic** | 10% | Same customer segment (value, mainstream, premium) |
+| **Launch season** | 10% | Same quarter launch; seasonal patterns differ by quarter |
+| **Distribution breadth** | 5% | Similar initial door count (±25%) |
+
+#### Analog Scoring
+
+Score each candidate analog on the criteria above (1–5 scale per criterion, weighted).
+Select the top 3–5 analogs with composite scores > 3.5. If no analogs score > 3.0, the
+new product is truly novel — use category average with a 40% confidence band.
+
+### 7.2 New Product Lifecycle Curve
+
+Most new products follow a lifecycle curve with four phases:
+
+| Phase | Duration | Demand Pattern | Description |
+|---|---|---|---|
+| **Introduction** | Weeks 1–4 | Ramp-up, often trial-driven | Initial customer trial. Demand is unpredictable. |
+| **Growth** | Weeks 5–12 | Accelerating, repeat purchases begin | Repeat buyers emerge. Demand becomes more predictable. |
+| **Stabilization** | Weeks 13–26 | Plateaus to steady state | Item finds its "run rate." Baseline forecast is reliable. |
+| **Maturity** | Weeks 27+ | Stable or slowly declining | Standard demand planning applies. |
+
+**Forecast by phase:**
+
+| Phase | Method | Confidence Band |
+|---|---|---|
+| Introduction (1–4 weeks) | Analog average × 1.1 (trial bump) | ±40–50% |
+| Growth (5–12 weeks) | Blend: 40% analog + 60% own trajectory | ±25–35% |
+| Stabilization (13–26 weeks) | 80% own history, 20% analog | ±15–25% |
+| Maturity (27+ weeks) | Standard method selection per demand pattern | Standard WMAPE target |
+
+### 7.3 New Product Safety Stock Protocol
+
+| Weeks of History | Safety Stock Approach | Uncertainty Premium |
+|---|---|---|
+| 0–4 | Analog σ_d with 30% premium | 1.30× |
+| 5–8 | Blended σ_d (50% own + 50% analog) with 20% premium | 1.20× |
+| 9–12 | Blended σ_d (75% own + 25% analog) with 10% premium | 1.10× |
+| 13+ | Own σ_d, standard formula | 1.00× |
+
+### 7.4 New Product Kill Decision
+
+Not every new product succeeds. The kill decision should be structured, not emotional:
+
+| Metric | Kill Threshold | Timeframe |
+|---|---|---|
+| Sell-through vs. analog-based plan | < 30% of plan | After 6 weeks |
+| Repeat purchase rate (if measurable) | < 10% of trial purchasers | After 8 weeks |
+| Velocity trend | Declining for 4 consecutive weeks after introduction | After 6 weeks |
+| Category manager assessment | "Would not re-buy" | After 8 weeks |
+
+When a kill decision is made:
+1. Cancel all open POs immediately.
+2. Halt any planned promotions.
+3. Mark down remaining inventory at 30% off for 3 weeks, then 50% for 2 weeks.
+4. Liquidate any remainder after 5 weeks.
+5. Document the post-mortem: why did the analog-based forecast fail? Was it the
+ analogs, the product, the pricing, or the competitive context?
+
+---
+
+## 8. Demand Sensing and Exception Management
+
+### 8.1 Real-Time Demand Signal Monitoring
+
+In addition to periodic forecast reviews, monitor for demand signals that require
+immediate attention between forecast cycles:
+
+| Signal | Detection Method | Threshold | Action |
+|---|---|---|---|
+| **POS velocity spike** | Daily POS > 3× trailing 4-week daily average | 3× for 2+ consecutive days | Investigate cause; manual override if sustained |
+| **POS velocity drop** | Daily POS < 0.3× trailing 4-week daily average | 0.3× for 3+ consecutive days | Check for phantom inventory, display removal, or competitive action |
+| **Stockout cascade** | 3+ locations out of stock on same SKU within 48 hours | 3 locations | Emergency replenishment from DC; allocate by sales velocity |
+| **Weather alert** | NWS severe weather warning for region covering > 10% of stores | Forecast impact > 5% of category volume | Adjust forecasts for weather-sensitive categories |
+| **Competitive price move** | Competitor price check shows > 15% lower on comparable SKU | Confirmed at 3+ competitor locations | Alert merchandising; prepare forecast downward revision |
+| **Social media spike** | Monitoring tool shows > 500% increase in brand/product mentions | Sustained > 24 hours | Assess virality risk; prepare allocation plan |
+
+### 8.2 Forecast Override Governance
+
+Manual overrides are necessary but dangerous. Ungoverned overrides introduce bias and
+degrade forecast accuracy over time.
+
+**Override rules:**
+
+1. **All overrides must be documented** with a reason code and quantitative justification.
+2. **Override authority by magnitude:**
+ - ±10%: Planner can override without approval
+ - ±10–25%: Requires planning manager approval
+ - ±25–50%: Requires director approval
+ - > ±50%: Requires VP approval (or planning committee)
+3. **Override accuracy tracking:** Every override is tracked against actuals. If a planner's
+ overrides have a WMAPE > 40% over a quarter, their override authority is reviewed.
+4. **Sunset rule:** Overrides expire after 4 weeks. If the condition persists, a new
+ override (with fresh justification) must be created. This prevents stale overrides
+ from contaminating forecasts months later.
+5. **No "consensus" overrides:** Overrides from demand review meetings where forecasts
+ are adjusted to match sales team wishful thinking are the #1 source of positive bias.
+ Require every meeting override to cite a specific, verifiable external signal.
+
+---
+
+## 9. Inventory Health Diagnostics
+
+### 9.1 Weeks of Supply Analysis
+
+Weeks of supply (WOS) is the primary pulse-check metric for inventory health. Compute
+at the SKU level, aggregate to category, and review weekly.
+
+```
+WOS = On-Hand Inventory (units) / Average Weekly Demand (units)
+```
+
+Use the forward-looking forecast for the denominator, not trailing sales. Trailing sales
+understates demand when items have been out of stock (you can't sell what you don't have).
+
+**WOS Health Bands:**
+
+| WOS Range | Status | Action |
+|---|---|---|
+| < 2 weeks | Critical low | Expedite replenishment; consider reallocation from low-velocity locations |
+| 2–3 weeks | Low | Verify next PO arrival; place emergency order if no PO in transit |
+| 4–8 weeks | Healthy | Standard operations |
+| 9–12 weeks | Elevated | Review forecast; defer or reduce next PO if demand hasn't increased |
+| 13–26 weeks | Excess | Initiate markdown or promotional sell-through plan |
+| > 26 weeks | Critical excess | Flag for slow-mover kill decision; markdown or liquidate |
+
+### 9.2 Inventory Turns and GMROI
+
+**Inventory Turns:**
+```
+Annual Turns = Annual COGS / Average Inventory at Cost
+```
+
+| Category Type | Target Turns | Benchmark |
+|---|---|---|
+| Perishable grocery | 30–52 | 1× per week |
+| Center-store grocery | 12–20 | Every 2–4 weeks |
+| General merchandise | 6–12 | Every 4–8 weeks |
+| Seasonal (in-season) | 8–15 | Sell through in-season |
+| Seasonal (annual) | 2–4 | Lower because of off-season zero sales |
+
+**GMROI (Gross Margin Return on Inventory Investment):**
+```
+GMROI = Gross Margin $ / Average Inventory at Cost
+```
+
+A GMROI of 2.0 means you earn $2 in gross margin for every $1 invested in inventory.
+Minimum acceptable GMROI varies by category but should generally exceed the company's
+cost of capital divided by the gross margin percentage. For a retailer with 8% cost of
+capital and 35% gross margin, minimum GMROI = 0.08 / 0.35 = 0.23. In practice, most
+retailers target GMROI > 1.5 for healthy categories.
+
+### 9.3 Dead Stock and Obsolescence Identification
+
+Dead stock is inventory with zero sales for a defined period. It is the most expensive
+form of excess inventory because it generates zero return while consuming warehouse space
+and working capital.
+
+**Dead stock tiers:**
+
+| Tier | Definition | Action | Timeline |
+|---|---|---|---|
+| Aging | Zero sales for 8–12 weeks | Review — is this seasonal? New? Misplaced? | Investigate within 1 week |
+| Dead | Zero sales for 13–26 weeks | Markdown 40–50% or move to clearance | Initiate within 2 weeks |
+| Obsolete | Zero sales for > 26 weeks | Liquidate at any positive recovery or donate | Execute within 4 weeks |
+| Write-off | Liquidation/donation uneconomical | Destroy and write off; recover warehouse space | Execute within 2 weeks |
+
+**Root cause analysis for dead stock:**
+
+Run quarterly. Categorize dead stock by root cause to prevent recurrence:
+
+| Root Cause | % of Dead Stock (typical) | Prevention |
+|---|---|---|
+| Over-buying (forecast too high) | 35–45% | Improve forecast accuracy; tighten override governance |
+| Product failure (quality, customer rejection) | 15–20% | Faster new product kill decisions |
+| Seasonal carryover (missed markdown window) | 15–25% | Enforce markdown timing model from §6.2 |
+| Assortment change (delisted but not sold through) | 10–15% | Coordinate delist timing with sell-through |
+| Phantom inventory (system says it exists but doesn't) | 5–10% | Regular cycle counts on zero-velocity items |
+
+### 9.4 Allocation Logic for Multi-Location Retailers
+
+When DC inventory is insufficient to fill all store-level demand, allocate using a
+priority framework rather than pro-rata distribution:
+
+**Priority 1: Prevent store stockout on A-items.**
+Allocate first to stores with < 3 days of supply on A-items. Quantity = minimum of
+(days-to-next-DC-shipment × daily demand) to bridge until the next allocation cycle.
+
+**Priority 2: Match allocation to store-level forecast.**
+For remaining inventory, allocate proportional to each store's forward weekly forecast
+(not historical sales, which penalizes stores that have been out of stock).
+
+**Priority 3: Minimum presentation stock.**
+Every store receives at least the minimum display quantity regardless of forecast. An
+empty shelf signals "this item is discontinued" to the customer and destroys demand.
+
+**Priority 4: Cap allocation to shelf capacity.**
+Do not send more than a store can merchandise. Excess units in the backroom create
+shrinkage, damage, and out-of-date risk (for perishables).
+
+**Allocation frequency:**
+- A-items: allocate with every DC-to-store shipment (typically 2–5× per week)
+- B-items: allocate 1–2× per week
+- C-items: allocate weekly or bi-weekly
diff --git a/web-app/public/skills/inventory-demand-planning/references/edge-cases.md b/web-app/public/skills/inventory-demand-planning/references/edge-cases.md
new file mode 100644
index 00000000..34916d98
--- /dev/null
+++ b/web-app/public/skills/inventory-demand-planning/references/edge-cases.md
@@ -0,0 +1,602 @@
+# Inventory Demand Planning — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous demand planning situations that don't resolve through standard forecasting and replenishment workflows.
+
+These edge cases represent the scenarios that separate experienced demand planners from everyone else. Each one involves competing signals, imperfect data, time pressure, and real financial exposure. They are structured to guide decision-making when standard models break down.
+
+---
+
+## How to Use This File
+
+When a planning situation doesn't fit a clean pattern — when demand signals conflict, when models fail silently, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document every assumption and override so the decision can be audited at post-mortem.
+
+---
+
+### Edge Case 1: New Product Launch with Zero History and No Close Analog
+
+**Situation:**
+A retailer's private-label team is launching a plant-based protein bar in a new flavor profile (mango turmeric) that has no direct precedent in their assortment or their competitors'. The product will launch in 120 stores across the Southeast region. Retail price is $3.49 per bar, case pack of 12, with a vendor cost of $1.85. The vendor requires a minimum initial order of 10,000 units (833 cases) with a 6-week lead time for reorder. The merchandising team is projecting "strong performance" based on consumer trend data showing plant-based snacking growing 22% YoY, but has no quantitative forecast. The product has a 9-month shelf life.
+
+**Why It's Tricky:**
+There is no demand history for this exact item, and the nearest analogs (existing protein bars, existing plant-based snacks) are imperfect matches. The mango turmeric flavor is novel — it could be a breakout trend or a niche product. The 6-week reorder lead time means you cannot react quickly if the product takes off, but the 9-month shelf life means overstock is not immediately catastrophic. The merchandising team's qualitative confidence is not a substitute for a quantitative forecast.
+
+**Common Mistake:**
+Accepting the merchandising team's optimistic "gut feel" as the forecast and ordering aggressively. Or, conversely, ordering so conservatively that the product launches out-of-stock in week 2, killing momentum and making the launch look like a failure when it was actually a supply failure.
+
+**Expert Approach:**
+1. Build a structured analog set. Score candidates on category (snack bars), price point ($3–$4), brand tier (private label), format (single serve), and target demo (health-conscious). Select the top 3–5 analogs even if they're imperfect.
+2. Compute the median weekly velocity of the analogs at the same lifecycle stage (launch weeks 1–13). Weight by analog similarity score. Typical private-label snack bar launch velocity is 2–4 units/store/week after the trial bump.
+3. Build three scenarios: conservative (2 units/store/week), base (3.5 units/store/week), optimistic (6 units/store/week). For 120 stores, this yields weekly demand of 240, 420, or 720 units.
+4. Initial buy: commit to the base scenario for weeks 1–8 (420 × 8 = 3,360 units), plus safety stock at the conservative rate for the 6-week reorder lead time (240 × 6 × 1.3 buffer = 1,872 units). Total initial order: ~5,232 units. This is below the vendor's 10,000 MOQ.
+5. Negotiate with the vendor: either accept the 10,000 MOQ (accepting ~10 weeks of forward stock at base rate, which is fine given 9-month shelf life), or negotiate a 5,000-unit initial order with a committed reorder at week 4 based on early sell-through.
+6. Set weekly POS monitoring triggers: if week-1 velocity > 5 units/store/day, escalate to the optimistic scenario and place reorder immediately. If week-2 velocity < 1.5 units/store, flag for review — the product may be underperforming.
+7. Plan a week-3 evaluation checkpoint with merchandising. If sell-through is < 40% of base scenario, begin discussing promotional support. If > 150%, ensure reorder is en route.
+
+**Documentation Required:**
+- Analog selection with scoring rationale
+- Three-scenario forecast with assumptions
+- Initial buy calculation with safety stock methodology
+- Vendor MOQ negotiation outcome
+- Monitoring triggers and escalation plan
+- Week-3 checkpoint agenda
+
+**Resolution Timeline:**
+- Weeks -8 to -6: Analog selection, scenario modeling, initial buy decision
+- Weeks -6 to -4: PO placement, promotional material preparation
+- Week 0: Launch
+- Weeks 1–3: Daily POS monitoring against scenarios
+- Week 3: First checkpoint with merchandising
+- Week 4: Reorder decision based on actual sell-through
+
+---
+
+### Edge Case 2: Viral Social Media Spike — 10× Demand with No Warning
+
+**Situation:**
+A mid-tier kitchen gadget (a silicone garlic peeler, retail $8.99, category C-item averaging 15 units/week across 80 stores) suddenly goes viral on TikTok. A cooking influencer with 4.2M followers posted a 45-second video using the product, and it accumulated 8M views in 48 hours. Store-level POS data shows demand jumped to 180 units/day across the chain (vs. the normal ~2 units/day) starting Tuesday morning. Your DC has 2,400 units in stock. The vendor is a small importer based in Portland with 8-week lead time from their factory in Shenzhen. Your last PO for this item was 3 months ago for 1,200 units.
+
+**Why It's Tricky:**
+The instinct is to chase the demand — place a massive order and ride the wave. But viral demand follows a power-law decay curve, not a sustained step change. By the time a 8-week-lead-time order arrives, the spike is almost certainly over. Meanwhile, your DC inventory will be exhausted in 13 days at current run rate, and you'll be out of stock for 6+ weeks. Customers who can't find it will buy from Amazon.
+
+**Common Mistake:**
+Ordering 10,000+ units from the vendor based on the spike's peak demand. When the order arrives 8 weeks later, demand has returned to 20–30 units/week (slightly elevated baseline), and you're sitting on 10,000 units — 300+ weeks of supply.
+
+**Expert Approach:**
+1. Do NOT place a large emergency order based on peak demand. Viral spikes typically follow this decay pattern: peak in days 1–5, 50% decay by day 10, 80% decay by day 21, new baseline establishes by day 30–45 (usually 1.5–3× the pre-viral level).
+2. With 2,400 units in DC and ~180 units/day demand, you have ~13 days of supply. Implement allocation rules immediately: cap store-level fulfillment at 3× historical daily average (6 units/store/day max). This stretches DC supply to ~20 days and prevents a single high-traffic store from claiming all the inventory.
+3. Contact the vendor. Determine: (a) do they have any finished goods inventory in Portland? (b) can they expedite a partial shipment by air from Shenzhen? (c) what is the minimum order for an air shipment? Air freight at ~$5/unit on a $4.50 cost item is expensive but justified if you can capture $8.99 retail during the spike.
+4. Place a modest reorder: 2,000–3,000 units (not 10,000). If the vendor can air-ship 500 units in 7–10 days, do that for immediate demand. The remaining 2,000 by ocean in 8 weeks will arrive when the new baseline is establishing.
+5. Monitor the TikTok video and social conversation daily. Track engagement rate decay. When the video drops off the "For You" page algorithm (typically day 7–14), demand will fall sharply.
+6. After the spike subsides (day 30+), assess the new baseline. If it's 2–3× the pre-viral level, adjust the forecast model upward. If it's back to pre-viral levels, return to the standard model. Do not permanently inflate the forecast based on a one-time event.
+
+**Key Indicators:**
+- Social media engagement half-life (how quickly the video's daily views are declining)
+- Store-level POS day-over-day trend (is demand decelerating?)
+- Amazon price and availability for the same or similar product (competitor action)
+- Geographic concentration of demand (if concentrated in a few markets, the spike is more narrow)
+
+**Documentation Required:**
+- Social media monitoring data (daily view counts, engagement)
+- Daily POS data at store level during the spike
+- Allocation rules implemented and their rationale
+- Vendor communication log and order decisions
+- Post-spike baseline reassessment (at day 30 and day 60)
+
+**Resolution Timeline:**
+- Hours 0–4: Detect the spike via POS anomaly alerts; identify the social media source
+- Hours 4–12: Implement store-level allocation caps; contact vendor for emergency supply
+- Day 1–3: Monitor daily POS; track social media engagement decay
+- Day 3–7: If spike sustaining, place modest reorder (air freight if available)
+- Day 7–14: Social media engagement typically decays below threshold; spike decelerating
+- Day 21–30: Demand settling to new baseline; assess whether permanent elevation occurred
+- Day 30–45: Final baseline recalibration; close event; update model if sustained lift > 50%
+
+**Financial Impact:**
+A C-item at $8.99 retail and 15 units/week going to 180 units/day represents a revenue jump
+from ~$135/week to ~$11,328/week — an 84× increase. With 2,400 units in DC, the captured
+revenue is ~$21,576 before stockout. Chasing with a 10,000-unit ocean order ($45,000 at cost)
+that arrives to 25 units/week demand creates $39,375 in excess inventory. The smart play
+(500-unit air shipment + 2,000-unit modest ocean order) captures ~$8,500 in additional revenue
+during the tail of the spike while limiting overage risk to ~$3,500 in excess inventory.
+
+---
+
+### Edge Case 3: Supplier Lead Time Doubles Overnight — Single-Source Critical Item
+
+**Situation:**
+Your primary vendor for organic olive oil (an A-item, $12.99 retail, ~800 units/week across 150 stores) notifies you that their lead time is increasing from 14 days to 28 days effective immediately. The cause: their Mediterranean source experienced a poor harvest season, and the vendor is now sourcing from a secondary supplier in South America, which adds transit and quality testing time. You currently have 2,800 units in DC (3.5 weeks of supply at current demand) and a PO for 2,400 units that was due in 10 days but is now due in 24 days. Your safety stock calculation was based on the old 14-day lead time.
+
+**Why It's Tricky:**
+Your safety stock was calibrated for 14-day lead time. At the old lead time, your safety stock formula was: SS = 1.65 × 120 × √2 = 280 units (where σ_d = 120 units/week, LT = 2 weeks). Now LT = 4 weeks, so SS should be: 1.65 × 120 × √4 = 396 units. But you also need to recalculate the reorder point: ROP = d_avg × LT + SS = 800 × 4 + 396 = 3,596 units. You currently have IP = 2,800 + 2,400 = 5,200 units. That seems sufficient, but the in-transit PO is delayed by 14 days, meaning your effective on-hand for the next 24 days is only 2,800 units, which covers 3.5 weeks — less than the new 4-week lead time.
+
+**Common Mistake:**
+Accepting the vendor's new lead time without recalculating safety stock and reorder points. The planner orders the same quantities at the same frequency and discovers a stockout 3 weeks later when the gap becomes visible.
+
+**Expert Approach:**
+1. Immediately recalculate safety stock and reorder points using the new 28-day lead time. Document the before/after impact.
+2. Assess the inventory gap: Current on-hand (2,800) will last 3.5 weeks. The delayed PO (2,400 units) arrives in 24 days (~3.4 weeks). At 800 units/week consumption, you'll need 800 × 3.4 = 2,720 units in those 3.4 weeks, leaving only 80 units when the PO arrives — essentially zero safety stock.
+3. Place an emergency order immediately. Target quantity: enough to bridge the gap plus rebuild safety stock. Emergency order = (new SS − projected SS at PO arrival) + buffer = (396 − 80) + 400 = ~716 units. Round up to a case pack multiple.
+4. Contact the vendor: can they expedite any portion of the delayed PO? Even splitting it — 1,200 units at the original 14-day lead time and 1,200 at 28 days — would dramatically improve the position.
+5. Qualify a secondary supplier. Even if the secondary vendor has a higher cost or lower quality tier, having a backup prevents single-source dependency. Begin the qualification process immediately — don't wait for the crisis to deepen.
+6. Consider temporary demand-side measures: can you reduce facings (from 3 facings to 2) to slow sell-through without creating a visible out-of-stock? Can you substitute a different size (e.g., 25 oz instead of 16 oz) to spread demand across SKUs?
+7. Communicate to merchandising: service level on this item will temporarily drop from 97% to ~92% for the next 4–6 weeks. If this is unacceptable, discuss promotional alternatives or substitution strategies.
+
+**Documentation Required:**
+- Before/after safety stock and ROP calculations
+- Inventory position timeline projection (weekly, for the next 8 weeks)
+- Emergency order details and vendor response
+- Secondary supplier qualification plan with timeline
+- Communication to merchandising and category management
+
+**Resolution Timeline:**
+- Hour 0: Vendor notification received
+- Hours 0–4: Recalculate safety stock, ROP, and inventory position with new lead time
+- Hours 4–8: Place emergency order for the inventory gap
+- Day 1–2: Contact vendor to negotiate partial early shipment of delayed PO
+- Week 1: Begin secondary supplier qualification process
+- Week 1–2: Communicate revised service level expectations to merchandising
+- Weeks 2–6: Monitor inventory position weekly against projections
+- Weeks 6–8: Assess whether lead time has stabilized; update parameters permanently if so
+- Week 12: Review secondary supplier qualification status; decide whether to dual-source
+
+**Dual-Source Strategy Post-Crisis:**
+After any single-source lead time shock, evaluate dual-sourcing economics:
+- If the category is A-tier (>$500K annual purchases), dual-source at 70/30 split.
+ The 30% secondary supplier provides insurance and keeps the primary vendor competitive.
+- If B-tier ($100K–$500K), qualify a backup but keep orders single-source until triggered.
+- If C-tier (<$100K), the qualification cost may exceed the risk. Accept single-source
+ and carry additional safety stock instead.
+
+---
+
+### Edge Case 4: Unplanned Competitor Promotion Causes Demand Drop — Cannibalization You Didn't Plan
+
+**Situation:**
+Your chain's premium laundry detergent (Tide Ultra, A-item, $13.99, ~600 units/week across 120 stores) shows a sudden 35% velocity decline starting this week. POS data confirms it — down to ~390 units/week. There is no quality issue, no out-of-stock, and no change in shelf placement. A field report from a regional manager reveals that a competing national chain launched an aggressive BOGO promotion on their comparable Persil product, and a mass-market competitor is running a 40% off promotion on their private-label equivalent. Neither of these competitive actions was in your promotional calendar or forecasting inputs.
+
+**Why It's Tricky:**
+Your forecast model doesn't incorporate competitive promotional activity (most don't). The model will treat this as an unexplained demand drop and slowly adjust the baseline downward — which is wrong, because the competitive promotions will end in 2–3 weeks and your demand will recover. If you let the model self-correct, it will under-forecast the recovery period, leading to a stockout when competitive promotions end and demand snaps back.
+
+**Common Mistake:**
+Letting the automated forecast adjust downward based on the depressed actual sales. The model doesn't know why sales dropped, so it interprets it as a trend change. Two weeks later, when demand recovers, the system doesn't have enough inventory because it ordered based on the depressed forecast.
+
+**Expert Approach:**
+1. Confirm the cause: verify the competitive promotion through field observation, competitive intelligence, or syndicated data (Nielsen/IRI). Don't assume — there could be multiple causes.
+2. Once confirmed, apply a manual forecast override for the promotional period. Set the forecast to the depressed level (390 units/week) for the known duration of the competitive promotion (typically 2–4 weeks).
+3. Critically: also apply a forward override for the recovery period. When the competitive promo ends, expect a 10–20% bounce-back above the pre-event baseline for 1–2 weeks as customers who delayed purchases return. Set the recovery forecast to 660–720 units/week for weeks 1–2 post-competitive-promo.
+4. Adjust incoming orders: reduce the next 2 POs by the difference (600 → 390 = 210 units/week reduction). But do NOT cancel or defer orders that would leave you short during the recovery.
+5. Brief merchandising: "Tide is down 35% this week due to competitive BOGO on Persil at [competitor]. We project this lasts 2–3 weeks. We do not recommend a reactive promotion — it would erode margin without recovering the lost volume (customers have already stockpiled from the competitor). Recommend holding price and capturing the recovery."
+6. After the event, mark these 2–4 weeks as "competitive interference" in the demand history so the baseline model excludes them from future training data.
+
+**Key Indicators:**
+- Duration of the competitive promotion (check competitor circulars/websites weekly)
+- Whether additional competitors pile on (competitive cascades happen in laundry, soda, and cereal)
+- Whether the demand recovery follows the expected bounce-back pattern
+- Whether the competitive promotion was a one-time event or signals a strategic price repositioning
+
+**Documentation Required:**
+- Competitive intelligence source and verification
+- Manual override with reason code "competitive_promo_external"
+- Adjusted PO schedule for the event window
+- Recovery forecast and rationale
+- Post-event analysis comparing actuals to the override forecast
+
+**Resolution Timeline:**
+- Day 0–1: Detect the velocity drop; confirm competitive cause via field reports
+- Day 1–2: Apply manual forecast override for the dip and the expected recovery
+- Day 2–5: Adjust incoming POs downward for the promotional window
+- End of competitive promo + 2 weeks: Analyze recovery pattern vs. forecast
+- End of competitive promo + 4 weeks: Close out event; tag demand history; update model
+
+**Financial Impact Quantification:**
+Compute the lost margin during the event: (normal demand − actual demand) × unit margin × duration.
+For this example: (600 − 390) × ~$4.00 margin × 3 weeks = ~$2,520 lost margin from volume loss.
+Compare this to the cost of a reactive promotion (which would typically cost $3,000–$5,000 in margin
+erosion for a category this size) to justify the "hold price" recommendation.
+
+---
+
+### Edge Case 5: Demand Pattern Regime Change — Model Fails Silently
+
+**Situation:**
+A popular breakfast cereal (Cheerios 18 oz, B-item, $4.29, ~400 units/week across 100 stores) has been forecasted with Holt-Winters for 3 years with stable seasonal patterns and WMAPE of 18%. Over the past 6 weeks, the model's tracking signal has crept from +1.5 to +4.8, indicating systematic positive bias (forecast > actuals). Actual sales have declined from 400 units/week to 310 units/week with no promotional activity, no competitive change, and no price change. A deeper look reveals that a competitor launched a new high-protein cereal at the same price point 8 weeks ago, and your chain's health-conscious customer segment is shifting to it.
+
+**Why It's Tricky:**
+This is a permanent demand level shift, not a temporary dip. The Holt-Winters model's seasonal component will eventually adapt, but the level component (alpha) adapts slowly — especially if alpha is set low (e.g., 0.1–0.2) for stability. The model will take 10–15 more weeks to self-correct, during which time it will consistently over-forecast, creating excess inventory.
+
+**Common Mistake:**
+Waiting for the model to self-correct. Or, conversely, panicking and switching the model entirely when a simple level adjustment would suffice.
+
+**Expert Approach:**
+1. Confirm the regime change: the tracking signal at +4.8 for 2+ periods is a clear indicator. Verify by computing the new mean demand (310 units/week) and comparing to the model's level component.
+2. Do NOT switch the forecast model yet. The seasonal pattern may still be valid — the item is still seasonal cereal. What changed is the level (intercept), not the pattern.
+3. Apply a one-time level adjustment: reset the Holt-Winters level component to the current 4-week average (310 units/week). Keep the seasonal indices and trend parameters. Re-initialize the model from this new level.
+4. Increase alpha temporarily (from 0.15 to 0.25) for the next 8 weeks to allow faster adaptation, then return to the standard alpha.
+5. Immediately recalculate safety stock using σ_d from the recent 8 weeks (which reflects the new demand regime), not the trailing 52 weeks.
+6. Reduce open POs to match the new run rate. Cancel or defer any POs that would push weeks of supply above 8 at the new demand level.
+7. Classify the competitor product as a "regime change event" and add it to the demand planning log. Propose to merchandising that they evaluate their assortment response (match the competitor product, promote Cheerios, or accept the share loss).
+
+**Key Indicators:**
+- Tracking signal trend (is it stabilizing at the new level or still diverging?)
+- Competitor product's velocity (is it still growing, or has it plateaued?)
+- Category total velocity (is the category growing, or is this a zero-sum shift?)
+- Customer switching behavior (if loyalty card data is available)
+
+**Documentation Required:**
+- Tracking signal history showing the drift from normal to ±4.8
+- Before/after forecast comparison at the new demand level
+- Safety stock recalculation with the new σ_d
+- PO adjustment details (quantities deferred or cancelled)
+- Root cause classification (competitive entry, consumer preference shift, etc.)
+- Merchandising communication and their response
+
+**Resolution Timeline:**
+- Day 0: Tracking signal triggers model review
+- Day 1–3: Confirm regime change vs. temporary dip; analyze root cause
+- Day 3–5: Apply level adjustment; recalculate safety stock; adjust POs
+- Weeks 2–8: Monitor with elevated alpha; confirm model is tracking the new level
+- Week 8: Return alpha to standard; close the event
+- Week 12: Retrospective — was the level shift permanent or did it partially reverse?
+
+**Frequency of Occurrence:**
+Regime changes affect 5–10% of SKUs annually. The most common causes are competitive
+entry/exit (40%), reformulation or packaging changes (25%), price repositioning (20%),
+and distribution changes (15%). The key is detecting them quickly — every week of delay
+in responding to a downward regime change adds ~1 week of excess inventory.
+
+---
+
+### Edge Case 6: Phantom Inventory — System Shows Stock, Shelves Are Empty
+
+**Situation:**
+Your highest-velocity SKU in the beverage category (a 24-pack water case, A-item, ~1,200 units/week across 80 stores) has been showing 95%+ in-stock rate in the system, but customer complaints about out-of-stocks have tripled in the past month. The WMS shows 3,400 units at the DC and the stores collectively show 2,100 units on hand. However, three separate stores have reported that they can't find the product despite the system showing 50–80 units each. A partial cycle count at the DC reveals an actual count of 2,100 units — the WMS is overstating by 1,300 units (38% phantom inventory).
+
+**Why It's Tricky:**
+Every replenishment decision for the past several weeks has been based on a position that was 1,300 units higher than reality. The system thinks the DC has 4.7 weeks of supply when it actually has 2.9 weeks. Stores are running out because store-level inventory is also likely overstated (if receiving errors or shrinkage are the cause). The problem is almost certainly not limited to this one SKU — whatever process caused the phantom inventory (receiving errors, system timing, shrinkage) is likely affecting other items.
+
+**Common Mistake:**
+Correcting the inventory in the WMS and moving on. The correction fixes the symptom but not the cause. Next month, phantom inventory will reappear.
+
+**Expert Approach:**
+1. Immediately conduct a full physical count on this SKU at the DC and at the 10 highest-volume stores. Adjust WMS/POS inventory records to match physical counts.
+2. Recalculate the inventory position with corrected numbers. You likely need to place an emergency order — the corrected IP is probably below the reorder point.
+3. Place an emergency order: the delta between the old (phantom) IP and the corrected IP is 1,300 units at the DC alone, plus whatever store-level adjustments are needed. Rush this order if possible.
+4. Investigate the root cause of the phantom inventory:
+ - **Receiving error:** Were units scanned into the WMS but physically not there? Check receiving logs against PO quantities for the past 60 days.
+ - **Shrinkage:** Is this a high-theft item? Water cases are not typically theft targets, so this is less likely.
+ - **System timing:** Is there a lag between physical movement and WMS update (e.g., cross-dock items that are "received" but immediately shipped to stores without a separate ship transaction)?
+ - **Return processing:** Were damaged/returned units re-entered into available inventory without physical verification?
+5. Expand the investigation. Run a phantom inventory screening across all A-items: pull any SKU where the system in-stock rate is > 95% but customer complaints or lost sales proxy metrics (search-to-purchase ratio, substitute purchase rate) indicate stockouts. These are your phantom inventory suspects.
+6. Implement a cycle count program targeting high-velocity items quarterly and any item with a discrepancy > 10% between system and physical counts.
+7. Adjust safety stock upward by 10–15% for the category until the root cause is resolved and verified, to buffer against ongoing phantom inventory risk.
+
+**Documentation Required:**
+- Physical count vs. system count by location
+- Root cause investigation findings
+- Emergency order details
+- Expanded screening results for other SKUs
+- Cycle count program specification
+- Safety stock adjustment and rationale
+
+**Resolution Timeline:**
+- Day 0: Customer complaints or lost-sales signals trigger investigation
+- Day 0–1: Physical count at DC; confirm phantom inventory exists
+- Day 1–2: Adjust WMS records; place emergency order; expand screening to all A-items
+- Days 3–7: Physical counts at top 20 stores on the affected SKU
+- Weeks 1–2: Root cause investigation across receiving, shrinkage, and system processes
+- Week 3: Implement corrective action (process change, cycle count program)
+- Month 2–3: Monitor for recurrence; verify corrective action effectiveness
+
+**Financial Impact:**
+Phantom inventory has a dual cost: (1) the lost sales from stockouts that the system didn't
+predict (in this case, ~300 units/week × $sell_price = significant revenue), and (2) the
+upstream effects — overstated inventory means the replenishment system didn't trigger orders
+when it should have, creating a cascading supply gap. For an A-item at 1,200 units/week,
+even a 20% phantom inventory rate translates to ~240 lost sales per week, which at $5 retail
+is $1,200/week in lost revenue, or ~$62,400/year for a single SKU.
+
+---
+
+### Edge Case 7: Vendor MOQ Conflict — Ordering Constraint vs. Demand Reality
+
+**Situation:**
+You carry a specialty imported Italian pasta brand (5 SKUs, each averaging 30–50 units/week across 60 stores). The vendor's minimum order quantity is 500 units per SKU per order, and they only accept orders on a monthly basis (once per month, delivery in 3 weeks). For a SKU averaging 40 units/week, the MOQ of 500 units represents 12.5 weeks of supply. With a 7-week order cycle (4-week review + 3-week lead time), your target order-up-to level should be about 360 units (7 weeks × 40 + safety stock). The MOQ forces you to order 39% more than you need.
+
+**Why It's Tricky:**
+You can't order less than the MOQ, but ordering 500 units every month means you're always carrying ~5 weeks of excess inventory. Across 5 SKUs, that's 2,500 excess units at ~$3.50 cost each = ~$8,750 in excess inventory investment. The holding cost (25% annually = ~$0.07/unit/week) seems small per unit but adds up to ~$9,100/year in excess carrying cost across the 5 SKUs. This isn't a one-time problem — it recurs every month.
+
+**Common Mistake:**
+Accepting the MOQ without quantifying the cost. Or, alternatively, fighting the vendor on MOQ without considering the alternatives.
+
+**Expert Approach:**
+1. Quantify the total cost of the MOQ constraint: annual excess holding cost ($9,100), waste risk (if shelf life is limited), and opportunity cost of the working capital.
+2. Evaluate options in order:
+ a. **Negotiate a dollar minimum instead of unit minimum:** If you order all 5 SKUs together, the combined order is 2,500 units × $3.50 = $8,750 per order. Propose a $6,000 order minimum with flexibility to allocate across SKUs based on need. Many importers prefer this because they still get a meaningful order.
+ b. **Extend the review period:** Instead of monthly orders, order every 6 weeks. This increases the target order-up-to level, making the MOQ less excessive. But it also increases safety stock needs.
+ c. **Accept the MOQ for top 2–3 SKUs and negotiate lower for the bottom 2:** Concentrate volume on the fast movers and ask for 300-unit MOQ on the slowest.
+ d. **Cross-dock or consolidate with other retailers:** If you're part of a buying group or co-op, combine orders with other members to share the MOQ.
+ e. **Assess the overage as forward stock:** If the product has 18+ months of shelf life, 12.5 weeks of supply is tolerable. The holding cost may be acceptable relative to the value of carrying the brand.
+3. Before negotiating, know your BATNA: are there alternative Italian pasta brands with better terms? What would switching cost (delisting fees, lost loyal customers)?
+4. Propose a 6-month trial: "We'd like to test a $5,000 minimum order across the 5 SKUs for Q3 and Q4. If our order frequency and reliability are maintained, we'd like to formalize this for the annual agreement."
+
+**Key Indicators:**
+- Shelf life remaining on excess inventory (critical for food products)
+- Sell-through rate of excess units before the next order arrives
+- Whether the vendor has other regional customers you could consolidate with
+- Total vendor spend as leverage for negotiation
+
+**Documentation Required:**
+- Annual excess holding cost calculation per SKU and total for the vendor
+- Vendor negotiation correspondence and outcome
+- Comparison of options evaluated (lower MOQ vs. dollar minimum vs. accept overage)
+- Any agreed trial terms and review dates
+
+**Resolution Timeline:**
+- Month 0: Quantify the MOQ cost impact across all SKUs from this vendor
+- Month 0–1: Prepare negotiation package; identify BATNA (alternative suppliers)
+- Month 1: Present to vendor at the next order cycle or QBR
+- Month 2: Implement the agreed terms on a 6-month trial basis
+- Month 8: Review trial results; formalize in the annual vendor agreement
+
+**MOQ Impact Calculator (per SKU):**
+```
+Excess Units per Order = MOQ − EOQ (or optimal order quantity)
+Annual Orders = 52 / (MOQ / Weekly Demand)
+Annual Excess Units = Excess per Order × Annual Orders
+Annual Excess Holding Cost = Annual Excess Units × Unit Cost × Holding Cost %
+```
+
+For the pasta example: Excess = 500 − 280 = 220 units per order. Annual orders = 52 / (500/40) = ~4.2.
+Annual excess units = 220 × 4.2 = ~924. Holding cost at 25% on $3.50 cost = 924 × $0.875 = ~$809/year.
+Across 5 SKUs with similar profiles, that's ~$4,000/year — worth negotiating but not worth losing the brand.
+
+---
+
+### Edge Case 8: Holiday Calendar Shift — Easter Moves 3 Weeks, Forecast Breaks
+
+**Situation:**
+Last year Easter fell on March 31. This year it falls on April 20 — a 3-week shift. Your seasonal candy category (Easter chocolate, jelly beans, marshmallow Peeps) typically sees a 6-week selling season centered on Easter week. Your Holt-Winters model uses 52-week seasonal indices. Because Easter shifted, the model is projecting peak demand in the same calendar weeks as last year (weeks 10–13) rather than the correct weeks (weeks 13–16 this year). The seasonal indices are aligning to the wrong calendar weeks.
+
+**Why It's Tricky:**
+Holt-Winters seasonal indices are indexed to week numbers, not to event dates. A 3-week shift in Easter means the model peaks 3 weeks too early. If you follow the model, you'll over-order for late March (building inventory for a peak that doesn't come) and under-order for mid-April (missing the actual peak). The financial exposure is significant: Easter candy is a $200K–$400K category with 15–20% margins on regular items and near-zero margin on post-Easter clearance.
+
+**Common Mistake:**
+Running the Holt-Winters model without adjusting for the holiday shift. Or manually shifting the seasonal indices but forgetting to shift the promotional calendar, vendor order deadlines, and markdown timing.
+
+**Expert Approach:**
+1. Before the forecasting cycle begins (typically 12–16 weeks before Easter), compute the calendar-week shift: ΔW = Easter_this_year_week − Easter_last_year_week. This year, ΔW = +3 weeks.
+2. Shift the seasonal indices: for any SKU with Easter-linked seasonality, shift the 52-week seasonal index array by ΔW positions. Index for week 10 last year now applies to week 13 this year.
+3. Apply the same shift to the build schedule: the 6-week selling window moves from weeks 8–13 (last year) to weeks 11–16 (this year). Vendor orders that were placed in January for March delivery now need to be placed for April delivery.
+4. Shift the markdown timing: post-Easter clearance moves from week 14 (last year) to week 17 (this year). Any markdown price changes scheduled for the old dates must be updated.
+5. Coordinate with store operations: Easter display set dates, endcap resets, and seasonal aisle transitions all shift by 3 weeks.
+6. Validate with at least 3 prior Easter years that show similar shifts. Look at 2019 (April 21) as the closest date comparator for demand patterns.
+7. Watch for interaction effects: if the shifted Easter overlaps with spring break schedules differently than last year, travel-related demand patterns (convenience stores, airports) may not follow the standard shift formula.
+8. Model the "gap" period: the 3 weeks between last year's Easter and this year's Easter will have lower demand than last year's model suggests but higher demand than a non-Easter baseline. Use a blended estimate.
+
+**Documentation Required:**
+- Holiday shift calculation and affected SKUs
+- Shifted seasonal indices (before and after)
+- Adjusted vendor order schedule
+- Adjusted markdown timing
+- Promotional calendar updates
+- Historical comparisons to similar-dated Easters
+
+**Financial Impact:**
+Easter candy is typically a $200K–$400K category for a mid-size retailer. A 3-week
+misalignment in seasonal indices can cause 25–35% of that inventory to be mistimed:
+arriving too early (incurring holding cost and space conflict) or peaking when demand
+has already shifted. Markdowns on Easter-specific product (chocolate bunnies, egg-shaped
+candy) are particularly steep because the product has zero value after Easter weekend.
+A mistimed buy can easily cost $30K–$60K in margin erosion on a category this size.
+
+**Other Holiday Shifts to Monitor:**
+- **Thanksgiving:** Always the 4th Thursday of November, but the gap between Thanksgiving
+ and Christmas (22–29 days) affects holiday season build timing.
+- **Ramadan:** Shifts ~11 days earlier each year (lunar calendar). Critical for retailers
+ with significant Muslim customer demographics. Specialty food demand shifts.
+- **Chinese New Year:** Falls between Jan 21 and Feb 20. Affects import lead times from
+ China by 2–3 weeks (factory closures).
+- **Back-to-school:** Not a fixed holiday but a regional event. Northern states start
+ in late August; Southern states start in early August. A planner managing both regions
+ needs different seasonal indices for the same categories.
+
+---
+
+### Edge Case 9: Weather-Sensitive Demand Miscalculation — Heat Wave in March
+
+**Situation:**
+An unexpected early heat wave hits the Southeast (temperatures 15–20°F above normal for 10 days in mid-March). Your forecast models are projecting normal March demand for summer-seasonal categories: bottled water, sunscreen, ice cream, fans, and outdoor furniture. POS data on day 2 of the heat wave shows bottled water up 280%, sunscreen up 420%, and ice cream up 190%. Your DC has standard March inventory levels for these categories — roughly 3–4 weeks of supply at normal March rates, which translates to 8–12 days at the spiked demand.
+
+**Why It's Tricky:**
+Weather-driven demand spikes are temporary but intense. The heat wave will end in 10 days, but you'll have stockouts within 5–7 days on the fastest-moving items. Unlike seasonal ramp-up (which is gradual), this is a step-change. Your vendors are also not expecting March orders at summer volumes. And if you over-react and place summer-sized orders, you'll have excess when temperatures normalize, especially for sunscreen (which most customers won't need again until actual summer).
+
+**Common Mistake:**
+Treating the heat wave as the start of summer. Placing orders sized for sustained summer demand when this is a 10-day weather event. Or, alternatively, doing nothing because "March orders are already placed" and letting stores run out.
+
+**Expert Approach:**
+1. Separate items into "weather-temporary" and "weather-pull-forward" categories:
+ - **Weather-temporary:** Items consumed during the heat wave that won't reduce summer demand (e.g., ice cream eaten today doesn't reduce ice cream eaten in July). These need incremental inventory for the event only.
+ - **Weather-pull-forward:** Items purchased now that would have been purchased later (e.g., sunscreen, fans). These pull demand from the summer season — over-ordering now creates a surplus later.
+2. For weather-temporary items (water, ice cream): place an emergency order sized for 10 days of elevated demand minus current inventory. Use regional distributors or DSD (direct-store-delivery) vendors who can respond in 24–48 hours.
+3. For weather-pull-forward items (sunscreen, fans, outdoor furniture): order conservatively. These customers are buying their summer supply early. Order enough to cover the current spike (5–7 days of additional supply) but reduce your planned April/May orders by the same amount.
+4. Communicate to stores: allocate weather-sensitive items based on geographic proximity to the heat wave. Stores in the affected region get priority; stores in unaffected northern markets maintain normal allocations.
+5. After the heat wave: analyze the demand transfer. For pull-forward categories, compute how much April/May demand was pulled into March and adjust the summer season forecast downward accordingly.
+6. Do NOT let the heat wave contaminate the seasonal baseline model. Tag these 10 days as "weather event" in the demand history so the model ignores them when computing seasonal indices for next year.
+
+**Documentation Required:**
+- Weather forecast data (NWS source) and affected geographic regions
+- Category classification: weather-temporary vs. weather-pull-forward
+- Emergency order details by category
+- Store allocation rules during the event
+- Post-event demand transfer analysis
+- Demand history tagging for model hygiene
+
+**Resolution Timeline:**
+- Day 0–1: Weather alert triggers category review; classify temporary vs. pull-forward
+- Day 1–2: Place emergency orders for weather-temporary items via DSD and regional distributors
+- Day 2–3: Adjust allocations to stores in the affected region; reduce allocations to unaffected regions
+- Day 5–7: Monitor if the heat wave is extending beyond 10 days; adjust orders if so
+- Post-event (day 12–15): Analyze demand transfer for pull-forward categories
+- Post-event (day 20–30): Adjust forward forecasts for summer categories downward by the pull-forward amount
+- Post-event: Tag affected days in demand history; run model hygiene cleanup
+
+**Common Weather Events and Their Demand Impact:**
+
+| Weather Event | Key Categories Affected | Typical Demand Change | Duration |
+|---|---|---|---|
+| Heat wave (10+ days above normal) | Water, ice cream, fans, sunscreen, outdoor | +100–400% | 7–14 days |
+| Cold snap (10+ days below normal) | Soup, hot chocolate, space heaters, rock salt | +80–250% | 5–10 days |
+| Hurricane / major storm (pre-landfall) | Water, batteries, flashlights, canned food, generators | +500–1000% | 2–4 days pre-event |
+| Blizzard / ice storm | Bread, milk, eggs ("French toast index"), shovels | +200–500% | 1–3 days pre-event |
+| Extended rain | Umbrellas, rain gear, indoor entertainment | +50–150% | Duration of event |
+
+---
+
+### Edge Case 10: End-of-Life Transition — Old and New SKU Cannibalize Each Other
+
+**Situation:**
+A major brand is transitioning from V1 to V2 of a popular household cleaner (improved formula, new packaging, same price point). V1 is a B-item averaging 250 units/week. V2 will launch in 4 weeks with planned distribution to all 100 stores. The manufacturer is offering a one-time V2 introductory buy at a 15% discount. The complication: V1 and V2 will coexist on shelf for 6–10 weeks during the transition. The brand is not offering to buy back unsold V1 inventory. You currently have 3,200 units of V1 in the system (DC + stores = ~12.8 weeks of supply at the current rate).
+
+**Why It's Tricky:**
+During the transition, V1 and V2 will cannibalize each other. Total brand demand will likely remain flat or grow slightly (V2 launch may attract trial), but the split between V1 and V2 is uncertain. If V2 takes off quickly, V1 demand collapses and you're stuck with excess. If V2 launches slowly (customer resistance to change), V1 holds demand longer. The manufacturer's introductory discount pressures you to buy heavily on V2, but that bet compounds the V1 excess risk.
+
+**Common Mistake:**
+Buying V2 aggressively to capture the introductory discount while ignoring the V1 run-down plan. Six weeks later, V1 is occupying shelf space, DC slots, and working capital while V2 is the seller.
+
+**Expert Approach:**
+1. Model the transition as a combined brand forecast with a split ratio that shifts over time:
+ - Weeks 1–2 (post-V2 launch): V1 retains 70% of brand volume, V2 captures 30% (trial phase)
+ - Weeks 3–4: V1 at 50%, V2 at 50%
+ - Weeks 5–6: V1 at 30%, V2 at 70%
+ - Weeks 7+: V1 at 10%, V2 at 90%
+ These ratios are estimates — adjust based on brand's historical transition data and customer research.
+2. Run down V1 inventory intentionally. Stop reordering V1 immediately — you have 12.8 weeks at current rate, but demand will decline per the split model. Compute V1 sales under the declining split: ~250 × (0.7 + 0.7 + 0.5 + 0.5 + 0.3 + 0.3 + 0.1 + 0.1) = ~800 units over 8 weeks. You have 3,200 in the system — you'll have ~2,400 excess.
+3. Initiate V1 markdowns early — don't wait for the product to become unsellable. Week 1 post-V2 launch: take 20% off V1 to accelerate sell-through. Week 4: 40% off. Week 6: liquidate or donate any remainder.
+4. Size the V2 introductory buy conservatively: 4 weeks of supply at the V2 split rate, not at the full brand rate. That's ~250 × (0.3 + 0.5 + 0.7 + 0.9) = ~600 units for the first 4 weeks. Take the introductory discount on 600–800 units, not the 2,000+ the manufacturer will suggest.
+5. Negotiate with the manufacturer: request unsold V1 return credit or a markdown fund contribution. Most CPG brands transitioning formulas will contribute 25–50% of the V1 markdown cost if asked, because they want V1 off shelf to drive V2 trial.
+6. Track the actual V1/V2 split weekly and adjust. If V2 takes off faster than modeled, accelerate V1 markdowns. If V2 is slow, hold V1 price and defer V2 reorder.
+
+**Documentation Required:**
+- Combined brand forecast with V1/V2 split ratios
+- V1 run-down plan with markdown schedule
+- V2 introductory buy calculation
+- Manufacturer negotiation on return credit / markdown fund
+- Weekly V1/V2 split tracking vs. plan
+
+**Resolution Timeline:**
+- Weeks -6 to -4: Build V1/V2 combined forecast; compute V1 run-down plan
+- Week -4: Stop V1 reorders; negotiate manufacturer markdown support
+- Week -2: Set V1 markdown schedule; finalize V2 introductory buy
+- Week 0: V2 launches; V1 takes first markdown (20% off)
+- Week 4: V1 takes second markdown (40% off) if excess remains
+- Week 6: Liquidate any remaining V1 inventory
+- Week 8: Transition complete; V2 on standard replenishment
+
+**Financial Modeling:**
+Compute the total transition cost: V1 markdown cost (units × markdown depth × unit cost) +
+V1 liquidation loss + V2 introductory buy discount benefit − manufacturer markdown fund.
+For this example: if 2,400 V1 units remain and average markdown recovery is 60% of cost,
+the V1 loss is 2,400 × $cost × 0.40. The V2 introductory buy at 15% discount on 600–800
+units saves ~$cost × 0.15 × 700 = modest savings. Net transition cost is typically $2K–$5K
+for a brand of this size, which is the cost of maintaining a clean shelf transition.
+
+---
+
+### Edge Case 11: Multi-Location Allocation During Supply Constraint — Not Enough for Everyone
+
+**Situation:**
+A critical supplier shortage has reduced your supply of a top-selling protein powder (A-item, $34.99, ~900 units/week across 120 stores) by 60% for the next 6 weeks. You'll receive approximately 360 units/week instead of the normal 900. You cannot source from an alternative supplier — this is a branded product with an exclusive distribution agreement. The 120 stores have widely varying velocities: the top 20 stores sell 40% of total volume, the middle 40 sell 35%, and the bottom 60 sell 25%.
+
+**Why It's Tricky:**
+You can't serve all stores at their normal levels. Pro-rata allocation (giving each store 40% of their normal replenishment) seems fair but is suboptimal — it guarantees every store runs out rather than keeping some stores in-stock. But fully stocking the top 20 stores and cutting off the bottom 60 creates customer service issues at those locations and potential legal/franchise issues if you have contractual obligations.
+
+**Common Mistake:**
+Pro-rata allocation across all stores. Every store gets 40% of normal, every store stocks out in ~4 days, and the customer experience is universally bad rather than selectively managed.
+
+**Expert Approach:**
+1. Calculate the allocation by store tier to maximize total units sold (minimize lost sales):
+ - Top 20 stores: allocate at 70% of their normal rate (252 units/week). These stores have the highest traffic; even partial stock generates more sales per unit than full stock at a low-traffic store.
+ - Middle 40 stores: allocate at 35% of their normal rate (~110 units/week). Enough to maintain some presence.
+ - Bottom 60 stores: allocate at 15% of their normal rate (~54 units/week). Maintain minimum presentation stock only.
+ - Total: 252 + 110 + 54 = ~416 units/week. This exceeds the 360 available, so scale proportionally.
+2. Implement a maximum per-customer purchase limit at the store level (2 units per transaction) to prevent stockpiling.
+3. Communicate transparently to store managers: "Protein powder is on constrained allocation for the next 6 weeks due to supplier shortage. Your allocation is [X] units/week. We'll resume normal replenishment in [date]."
+4. Monitor sell-through rates at each tier. If the top-20 stores are selling out in 3 days, they're effectively under-allocated. If bottom-60 stores are carrying inventory into the next week, they're over-allocated. Adjust weekly.
+5. Prepare substitution signage for stores: "Looking for [brand]? Try [alternative] while supplies are limited." Even without a direct substitute supplier, suggesting a different brand/format captures some sales that would otherwise be lost.
+6. Track lost sales using a proxy: compare same-store sales of complementary items (protein bars, shakers) — a decline suggests customers are going elsewhere entirely.
+
+**Documentation Required:**
+- Allocation model with tier breakdowns
+- Weekly allocation vs. sell-through by tier
+- Customer purchase limit implementation
+- Lost sales estimate methodology and tracking
+- Supplier communication and expected resolution timeline
+
+**Resolution Timeline:**
+- Day 0: Supplier confirms constraint; demand planner receives allocation
+- Day 0–1: Build tiered allocation model; communicate to store operations
+- Day 1–2: Implement POS purchase limits; prepare substitution signage
+- Weekly for 6 weeks: Adjust allocations based on actual sell-through by tier
+- Week 6: Supplier confirms return to normal supply
+- Week 7–8: Rebuild safety stock at normal replenishment rates
+
+**Financial Impact:**
+Lost sales during a 60% supply constraint on a 900 units/week A-item at $34.99 retail:
+(900 − 360) × $34.99 × 6 weeks = ~$113,367 in lost revenue. With tiered allocation
+optimizing sell-through, you can recapture 15–25% of the otherwise lost sales compared
+to naive pro-rata allocation, worth $17K–$28K in recovered revenue. The allocation
+optimization effort pays for itself many times over.
+
+---
+
+### Edge Case 12: Demand Forecast Consensus Meeting Override — Sales Team Inflates Forecast
+
+**Situation:**
+During the monthly S&OP demand review, the sales team insists on overriding the statistical forecast for a key product line (premium pet food, 15 SKUs, ~$1.2M annual revenue). The statistical forecast projects flat demand at ~$100K/month. The sales team argues that a new distribution agreement with a pet specialty chain will add $30K/month starting next month. They want the forecast increased to $130K/month across all 15 SKUs proportionally. However, the distribution agreement is not yet signed (it's in "final review"), the specialty chain hasn't confirmed shelf dates, and the sales team has a history of overestimating new account volume by 40–60%.
+
+**Why It's Tricky:**
+The sales team may be right — the distribution deal is real and the incremental volume is plausible. But "plausible" is not "certain." If you accept the override and the deal delays by 2 months (common), you'll have 2 months of $30K/month in excess inventory ($60K), which for pet food with 12-month shelf life is manageable but ties up working capital. If you reject the override and the deal closes on time, you'll be short $30K/month and unable to serve the new account, potentially killing the deal.
+
+**Common Mistake:**
+Either accepting the sales team's number at face value (leading to chronic over-forecasting) or rejecting it entirely (leading to under-investment in growth).
+
+**Expert Approach:**
+1. Never accept or reject an override without a probability-weighted approach. Ask the sales team to commit to a probability of close and timing:
+ - Probability the deal closes: 70% (sales team's estimate — discount to 50% based on historical calibration)
+ - If it closes, when will volume start? 4 weeks (sales team) — add 4 weeks for historical optimism = 8 weeks realistic
+ - If it closes, what's the ramp rate? Rarely 100% from day 1. Model 50% in month 1, 75% in month 2, 100% in month 3.
+2. Compute the expected value override: $30K × 50% probability × ramp rate = $7.5K in month 1, $11.25K in month 2, $15K in month 3.
+3. Apply this as a staged override, not a flat $30K increase. Month 1: $107.5K. Month 2: $111.25K. Month 3: $115K.
+4. Set a kill trigger: if the deal hasn't closed by month 2, remove the override entirely and return to the statistical forecast. Do not carry speculative overrides indefinitely.
+5. Track the outcome: did the deal close? When? At what volume? Use this to calibrate the sales team's future override accuracy and adjust the probability discount accordingly.
+6. Distribute the override unevenly across SKUs: the new account likely won't carry all 15 SKUs. Ask the sales team which 5–8 SKUs the new account will stock, and concentrate the override there.
+
+**Documentation Required:**
+- S&OP meeting notes with the original override request
+- Probability-weighted override calculation
+- Staged implementation plan by month and SKU
+- Kill trigger date and conditions
+- Post-event accuracy tracking
+
+**Resolution Timeline:**
+- S&OP meeting: Capture the override request; apply probability weighting
+- Day 1–3: Compute the staged override and distribute across relevant SKUs
+- Week 1: Adjust POs to reflect the staged override (not the full $30K)
+- Week 4 (if deal not signed): Reduce override by 50%
+- Week 8 (if deal still not signed): Remove override entirely; return to statistical forecast
+- When deal closes: Ramp up based on actual account setup timeline
+- Month 3 post-close: Compare actual volume to the staged override; calibrate sales team accuracy
+
+**Historical Calibration:**
+Track the accuracy of sales team overrides over time. Maintain a simple table:
+
+| Override Source | Override Count (trailing 12 months) | Avg. Override Amount | Avg. Actual Result | Realization Rate |
+|---|---|---|---|---|
+| Sales team — new accounts | 8 | +$25K/month | +$12K/month | 48% |
+| Sales team — existing account growth | 12 | +$15K/month | +$9K/month | 60% |
+| Marketing — promotional lift | 6 | +40% lift | +32% lift | 80% |
+| Category management — trend calls | 5 | ±20% | ±8% | 40% |
+
+This calibration table allows you to apply evidence-based probability discounts to future
+overrides. A sales team with a 48% realization rate on new account overrides should have
+their stated volume multiplied by 0.48, not accepted at face value.
diff --git a/web-app/public/skills/ios-developer/SKILL.md b/web-app/public/skills/ios-developer/SKILL.md
index 8fa9a17d..95edf2fc 100644
--- a/web-app/public/skills/ios-developer/SKILL.md
+++ b/web-app/public/skills/ios-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ios-developer
-description: "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,"
+description: |
+ Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,
SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.
Use PROACTIVELY for iOS-specific features, App Store optimization, or native
iOS development.
diff --git a/web-app/public/skills/java-pro/SKILL.md b/web-app/public/skills/java-pro/SKILL.md
index 3b7e0a08..a070be0e 100644
--- a/web-app/public/skills/java-pro/SKILL.md
+++ b/web-app/public/skills/java-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: java-pro
-description: "Master Java 21+ with modern features like virtual threads, pattern"
+description: |
+ Master Java 21+ with modern features like virtual threads, pattern
matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including
GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java
development, microservices architecture, or performance optimization.
diff --git a/web-app/public/skills/javascript-pro/SKILL.md b/web-app/public/skills/javascript-pro/SKILL.md
index 2b4f0d18..a3c53a04 100644
--- a/web-app/public/skills/javascript-pro/SKILL.md
+++ b/web-app/public/skills/javascript-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: javascript-pro
-description: "Master modern JavaScript with ES6+, async patterns, and Node.js"
+description: |
+ Master modern JavaScript with ES6+, async patterns, and Node.js
APIs. Handles promises, event loops, and browser/Node compatibility. Use
PROACTIVELY for JavaScript optimization, async debugging, or complex JS
patterns.
diff --git a/web-app/public/skills/julia-pro/SKILL.md b/web-app/public/skills/julia-pro/SKILL.md
index d0063344..c38ccb0e 100644
--- a/web-app/public/skills/julia-pro/SKILL.md
+++ b/web-app/public/skills/julia-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: julia-pro
-description: "Master Julia 1.10+ with modern features, performance optimization,"
+description: |
+ Master Julia 1.10+ with modern features, performance optimization,
multiple dispatch, and production-ready practices. Expert in the Julia
ecosystem including package management, scientific computing, and
high-performance numerical code. Use PROACTIVELY for Julia development,
diff --git a/web-app/public/skills/kubernetes-architect/SKILL.md b/web-app/public/skills/kubernetes-architect/SKILL.md
index b8ac829c..3c9d06e2 100644
--- a/web-app/public/skills/kubernetes-architect/SKILL.md
+++ b/web-app/public/skills/kubernetes-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: kubernetes-architect
-description: "Expert Kubernetes architect specializing in cloud-native"
+description: |
+ Expert Kubernetes architect specializing in cloud-native
infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise
container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),
progressive delivery, multi-tenancy, and platform engineering. Handles
diff --git a/web-app/public/skills/legacy-modernizer/SKILL.md b/web-app/public/skills/legacy-modernizer/SKILL.md
index daf6efe5..516ba7f8 100644
--- a/web-app/public/skills/legacy-modernizer/SKILL.md
+++ b/web-app/public/skills/legacy-modernizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: legacy-modernizer
-description: "Refactor legacy codebases, migrate outdated frameworks, and"
+description: |
+ Refactor legacy codebases, migrate outdated frameworks, and
implement gradual modernization. Handles technical debt, dependency updates,
and backward compatibility. Use PROACTIVELY for legacy system updates,
framework migrations, or technical debt reduction.
diff --git a/web-app/public/skills/legal-advisor/SKILL.md b/web-app/public/skills/legal-advisor/SKILL.md
index 267335a8..91ba5e08 100644
--- a/web-app/public/skills/legal-advisor/SKILL.md
+++ b/web-app/public/skills/legal-advisor/SKILL.md
@@ -1,6 +1,7 @@
---
name: legal-advisor
-description: "Draft privacy policies, terms of service, disclaimers, and legal"
+description: |
+ Draft privacy policies, terms of service, disclaimers, and legal
notices. Creates GDPR-compliant texts, cookie policies, and data processing
agreements. Use PROACTIVELY for legal documentation, compliance texts, or
regulatory requirements.
diff --git a/web-app/public/skills/linkedin-cli/SKILL.md b/web-app/public/skills/linkedin-cli/SKILL.md
new file mode 100644
index 00000000..8401c8f0
--- /dev/null
+++ b/web-app/public/skills/linkedin-cli/SKILL.md
@@ -0,0 +1,536 @@
+---
+name: linkedin-cli
+description: "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator."
+source: community
+risk: safe
+---
+
+## When to Use
+
+Use this skill when you need to automate LinkedIn tasks such as profile fetching, connection management, or post creation via CLI, especially when integrated into automated workflows.
+
+# LinkedIn Skill
+
+You have access to `linkedin` – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more.
+
+Each command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are **not instant** – expect 30 seconds to several minutes depending on complexity.
+
+If `linkedin` is not available, install it:
+
+```bash
+npm install -g @linkedapi/linkedin-cli
+```
+
+## Authentication
+
+If a command fails with exit code 2 (authentication error), ask the user to set up their account:
+
+1. Go to [app.linkedapi.io](https://app.linkedapi.io) and sign up or log in
+2. Connect their LinkedIn account
+3. Copy the **Linked API Token** and **Identification Token** from the dashboard
+
+Once the user provides the tokens, run:
+
+```bash
+linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN
+```
+
+## When to Use
+
+Use this skill when you need to **orchestrate LinkedIn actions from scripts or an AI agent** instead of clicking through the web UI:
+
+- Building outreach, research, or recruiting workflows that rely on LinkedIn data and messaging.
+- Enriching leads or accounts by fetching people and company profiles in bulk.
+- Coordinating multi-step Sales Navigator or workflow runs where JSON output and exit codes are required.
+
+Always respect LinkedIn’s terms of service, local regulations, and your organisation’s compliance policies when using automation against real accounts.
+
+## Global Flags
+
+Always use `--json` and `-q` for machine-readable output:
+
+```bash
+linkedin --json -q
+```
+
+| Flag | Description |
+| ----------------------- | --------------------------------------- |
+| `--json` | Structured JSON output |
+| `--quiet` / `-q` | Suppress stderr progress messages |
+| `--fields name,url,...` | Select specific fields in output |
+| `--no-color` | Disable colors |
+| `--account "Name"` | Use a specific account for this command |
+
+## Output Format
+
+Success:
+
+```json
+{ "success": true, "data": { "name": "John Doe", "headline": "Engineer" } }
+```
+
+Error:
+
+```json
+{
+ "success": false,
+ "error": { "type": "personNotFound", "message": "Person not found" }
+}
+```
+
+Exit code 0 means the API call succeeded – always check the `success` field for the action outcome. Non-zero exit codes indicate infrastructure errors:
+
+| Exit Code | Meaning |
+| --------- | ------------------------------------------------------------------------------------------- |
+| 0 | Success (check `success` field – action may have returned an error like "person not found") |
+| 1 | General/unexpected error |
+| 2 | Missing or invalid tokens |
+| 3 | Subscription/plan required |
+| 4 | LinkedIn account issue |
+| 5 | Invalid arguments |
+| 6 | Rate limited |
+| 7 | Network error |
+| 8 | Workflow timeout (workflowId returned for recovery) |
+
+## Commands
+
+### Fetch a Person Profile
+
+```bash
+linkedin person fetch [flags] --json -q
+```
+
+Optional flags to include additional data:
+
+- `--experience` – work history
+- `--education` – education history
+- `--skills` – skills list
+- `--languages` – languages
+- `--posts` – recent posts (with `--posts-limit N`, `--posts-since TIMESTAMP`)
+- `--comments` – recent comments (with `--comments-limit N`, `--comments-since TIMESTAMP`)
+- `--reactions` – recent reactions (with `--reactions-limit N`, `--reactions-since TIMESTAMP`)
+
+Only request additional data when needed – each flag increases execution time.
+
+```bash
+# Basic profile
+linkedin person fetch https://www.linkedin.com/in/username --json -q
+
+# With experience and education
+linkedin person fetch https://www.linkedin.com/in/username --experience --education --json -q
+
+# With last 5 posts
+linkedin person fetch https://www.linkedin.com/in/username --posts --posts-limit 5 --json -q
+```
+
+### Search People
+
+```bash
+linkedin person search [flags] --json -q
+```
+
+| Flag | Description |
+| ---------------------- | -------------------------------------- |
+| `--term` | Search keyword or phrase |
+| `--limit` | Max results |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+
+```bash
+linkedin person search --term "product manager" --locations "San Francisco" --json -q
+linkedin person search --current-companies "Google" --position "Engineer" --limit 20 --json -q
+```
+
+### Fetch a Company
+
+```bash
+linkedin company fetch [flags] --json -q
+```
+
+Optional flags:
+
+- `--employees` – include employees
+- `--dms` – include decision makers
+- `--posts` – include company posts
+
+Employee filters (require `--employees`):
+
+| Flag | Description |
+| ------------------------ | ---------------------------- |
+| `--employees-limit` | Max employees to retrieve |
+| `--employees-first-name` | Filter by first name |
+| `--employees-last-name` | Filter by last name |
+| `--employees-position` | Filter by position |
+| `--employees-locations` | Comma-separated locations |
+| `--employees-industries` | Comma-separated industries |
+| `--employees-schools` | Comma-separated school names |
+
+| Flag | Description |
+| --------------- | -------------------------------------------------- |
+| `--dms-limit` | Max decision makers to retrieve (requires `--dms`) |
+| `--posts-limit` | Max posts to retrieve (requires `--posts`) |
+| `--posts-since` | Posts since ISO timestamp (requires `--posts`) |
+
+```bash
+# Basic company info
+linkedin company fetch https://www.linkedin.com/company/name --json -q
+
+# With employees filtered by position
+linkedin company fetch https://www.linkedin.com/company/name --employees --employees-position "Engineer" --json -q
+
+# With decision makers and posts
+linkedin company fetch https://www.linkedin.com/company/name --dms --posts --posts-limit 10 --json -q
+```
+
+### Search Companies
+
+```bash
+linkedin company search [flags] --json -q
+```
+
+| Flag | Description |
+| -------------- | ------------------------------------------------------------------------------------------------------------ |
+| `--term` | Search keyword |
+| `--limit` | Max results |
+| `--sizes` | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+
+```bash
+linkedin company search --term "fintech" --sizes "11-50,51-200" --json -q
+```
+
+### Send a Message
+
+```bash
+linkedin message send '' --json -q
+```
+
+Text up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues.
+
+```bash
+linkedin message send https://www.linkedin.com/in/username 'Hey, loved your latest post!' --json -q
+```
+
+### Get Conversation
+
+```bash
+linkedin message get [--since TIMESTAMP] --json -q
+```
+
+The first call for a conversation triggers a background sync and may take longer. Subsequent calls are faster.
+
+```bash
+linkedin message get https://www.linkedin.com/in/username --json -q
+linkedin message get https://www.linkedin.com/in/username --since 2024-01-15T10:30:00Z --json -q
+```
+
+### Connection Management
+
+#### Check connection status
+
+```bash
+linkedin connection status --json -q
+```
+
+#### Send connection request
+
+```bash
+linkedin connection send [--note 'text'] [--email user@example.com] --json -q
+```
+
+#### List connections
+
+```bash
+linkedin connection list [flags] --json -q
+```
+
+| Flag | Description |
+| ---------------------- | ------------------------------------------------------------------------------------ |
+| `--limit` | Max connections to return |
+| `--since` | Only connections made since ISO timestamp (only works when no filter flags are used) |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+
+```bash
+linkedin connection list --limit 50 --json -q
+linkedin connection list --current-companies "Google" --position "Engineer" --json -q
+linkedin connection list --since 2024-01-01T00:00:00Z --json -q
+```
+
+#### List pending outgoing requests
+
+```bash
+linkedin connection pending --json -q
+```
+
+#### Withdraw a pending request
+
+```bash
+linkedin connection withdraw [--no-unfollow] --json -q
+```
+
+By default, withdrawing also unfollows the person. Use `--no-unfollow` to keep following.
+
+#### Remove a connection
+
+```bash
+linkedin connection remove --json -q
+```
+
+### Posts
+
+#### Fetch a post
+
+```bash
+linkedin post fetch [flags] --json -q
+```
+
+| Flag | Description |
+| -------------------- | ------------------------------------------------------------------ |
+| `--comments` | Include comments |
+| `--reactions` | Include reactions |
+| `--comments-limit` | Max comments to retrieve (requires `--comments`) |
+| `--comments-sort` | Sort order: `mostRelevant` or `mostRecent` (requires `--comments`) |
+| `--comments-replies` | Include replies to comments (requires `--comments`) |
+| `--reactions-limit` | Max reactions to retrieve (requires `--reactions`) |
+
+```bash
+linkedin post fetch https://www.linkedin.com/posts/username_activity-123 --json -q
+
+# With comments sorted by most recent, including replies
+linkedin post fetch https://www.linkedin.com/posts/username_activity-123 \
+ --comments --comments-sort mostRecent --comments-replies --json -q
+```
+
+#### Create a post
+
+```bash
+linkedin post create '' [flags] --json -q
+```
+
+| Flag | Description |
+| --------------- | ------------------------------------------------------------------------------------------------------------------ |
+| `--company-url` | Post on behalf of a company page (requires admin access) |
+| `--attachments` | Attachment as `url:type` or `url:type:name`. Types: `image`, `video`, `document`. Can be specified multiple times. |
+
+Attachment limits: up to 9 images, or 1 video, or 1 document. Cannot mix types.
+
+```bash
+linkedin post create 'Excited to share our latest update!' --json -q
+
+# With a document
+linkedin post create 'Our Q4 report' \
+ --attachments "https://example.com/report.pdf:document:Q4 Report" --json -q
+
+# Post as a company
+linkedin post create 'Company announcement' \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+#### React to a post
+
+```bash
+linkedin post react --type [--company-url ] --json -q
+```
+
+Reaction types: `like`, `love`, `support`, `celebrate`, `insightful`, `funny`.
+
+```bash
+linkedin post react https://www.linkedin.com/posts/username_activity-123 --type like --json -q
+
+# React on behalf of a company
+linkedin post react https://www.linkedin.com/posts/username_activity-123 --type celebrate \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+#### Comment on a post
+
+```bash
+linkedin post comment '' [--company-url ] --json -q
+```
+
+Text up to 1000 characters.
+
+```bash
+linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Great insights!' --json -q
+
+# Comment on behalf of a company
+linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Well said!' \
+ --company-url https://www.linkedin.com/company/name --json -q
+```
+
+### Statistics
+
+```bash
+# Social Selling Index
+linkedin stats ssi --json -q
+
+# Performance analytics (profile views, post impressions, search appearances)
+linkedin stats performance --json -q
+
+# API usage for a date range
+linkedin stats usage --start 2024-01-01T00:00:00Z --end 2024-01-31T00:00:00Z --json -q
+```
+
+### Sales Navigator
+
+Requires a LinkedIn Sales Navigator subscription. Uses hashed URLs for person/company lookups.
+
+#### Fetch person
+
+```bash
+linkedin navigator person fetch --json -q
+```
+
+#### Search people
+
+```bash
+linkedin navigator person search [flags] --json -q
+```
+
+| Flag | Description |
+| ----------------------- | ------------------------------------------------------------------------------------------- |
+| `--term` | Search keyword or phrase |
+| `--limit` | Max results |
+| `--first-name` | Filter by first name |
+| `--last-name` | Filter by last name |
+| `--position` | Filter by job position |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--current-companies` | Comma-separated current company names |
+| `--previous-companies` | Comma-separated previous company names |
+| `--schools` | Comma-separated school names |
+| `--years-of-experience` | Comma-separated ranges: `lessThanOne`, `oneToTwo`, `threeToFive`, `sixToTen`, `moreThanTen` |
+
+```bash
+linkedin navigator person search --term "VP Marketing" --locations "United States" --json -q
+linkedin navigator person search --years-of-experience "moreThanTen" --position "CEO" --json -q
+```
+
+#### Fetch company
+
+```bash
+linkedin navigator company fetch [flags] --json -q
+```
+
+Optional flags:
+
+- `--employees` – include employees
+- `--dms` – include decision makers
+
+Employee filters (require `--employees`):
+
+| Flag | Description |
+| --------------------------------- | -------------------------------------------------- |
+| `--employees-limit` | Max employees to retrieve |
+| `--employees-first-name` | Filter by first name |
+| `--employees-last-name` | Filter by last name |
+| `--employees-positions` | Comma-separated positions |
+| `--employees-locations` | Comma-separated locations |
+| `--employees-industries` | Comma-separated industries |
+| `--employees-schools` | Comma-separated school names |
+| `--employees-years-of-experience` | Comma-separated experience ranges |
+| `--dms-limit` | Max decision makers to retrieve (requires `--dms`) |
+
+```bash
+linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural --employees --dms --json -q
+linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural \
+ --employees --employees-positions "Engineer,Designer" --employees-locations "Europe" --json -q
+```
+
+#### Search companies
+
+```bash
+linkedin navigator company search [flags] --json -q
+```
+
+| Flag | Description |
+| --------------- | ------------------------------------------------------------------------------------------------------------ |
+| `--term` | Search keyword |
+| `--limit` | Max results |
+| `--sizes` | Comma-separated sizes: `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |
+| `--locations` | Comma-separated locations |
+| `--industries` | Comma-separated industries |
+| `--revenue-min` | Min annual revenue in M USD: `0`, `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000` |
+| `--revenue-max` | Max annual revenue in M USD: `0.5`, `1`, `2.5`, `5`, `10`, `20`, `50`, `100`, `500`, `1000`, `1000+` |
+
+```bash
+linkedin navigator company search --term "fintech" --sizes "11-50,51-200" --json -q
+linkedin navigator company search --revenue-min 10 --revenue-max 100 --locations "United States" --json -q
+```
+
+#### Send InMail
+
+```bash
+linkedin navigator message send '' --subject '' --json -q
+```
+
+Text up to 1900 characters. Subject up to 80 characters.
+
+```bash
+linkedin navigator message send https://www.linkedin.com/in/username \
+ 'Would love to chat about API integrations' --subject 'Partnership Opportunity' --json -q
+```
+
+#### Get Sales Navigator conversation
+
+```bash
+linkedin navigator message get [--since TIMESTAMP] --json -q
+```
+
+### Custom Workflows
+
+Execute a custom workflow definition from a file, stdin, or inline:
+
+```bash
+# From file
+linkedin workflow run --file workflow.json --json -q
+
+# From stdin
+cat workflow.json | linkedin workflow run --json -q
+
+# Inline
+echo '{"actions":[...]}' | linkedin workflow run --json -q
+```
+
+Check workflow status or wait for completion:
+
+```bash
+linkedin workflow status --json -q
+linkedin workflow status --wait --json -q
+```
+
+See [Building Workflows](https://linkedapi.io/docs/building-workflows/) for the workflow JSON schema.
+
+### Account Management
+
+```bash
+linkedin account list # List accounts (* = active)
+linkedin account switch "Name" # Switch active account
+linkedin account rename "Name" --name "New Name" # Rename account
+linkedin reset # Remove active account
+linkedin reset --all # Remove all accounts
+```
+
+## Important Behavior
+
+- **Sequential execution.** All operations for an account run one at a time. Multiple requests queue up.
+- **Not instant.** A real browser navigates LinkedIn – expect 30 seconds to several minutes per operation.
+- **Timestamps in UTC.** All dates and times are in UTC.
+- **Single quotes for text arguments.** Use single quotes around message text, post text, and comments to avoid shell interpretation issues with special characters.
+- **Action limits.** Per-account limits are configurable on the platform. A `limitExceeded` error means the limit was reached.
+- **URL normalization.** All LinkedIn URLs in responses are normalized to `https://www.linkedin.com/...` format without trailing slashes.
+- **Null fields.** Fields that are unavailable are returned as `null` or `[]`, not omitted.
diff --git a/web-app/public/skills/logistics-exception-management/SKILL.md b/web-app/public/skills/logistics-exception-management/SKILL.md
new file mode 100644
index 00000000..c24f262e
--- /dev/null
+++ b/web-app/public/skills/logistics-exception-management/SKILL.md
@@ -0,0 +1,217 @@
+---
+name: logistics-exception-management
+description: >
+ Codified expertise for handling freight exceptions, shipment delays,
+ damages, losses, and carrier disputes. Informed by logistics professionals
+ with 15+ years operational experience. Includes escalation protocols,
+ carrier-specific behaviours, claims procedures, and judgment frameworks.
+ Use when handling shipping exceptions, freight claims, delivery issues,
+ or carrier disputes.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "📦"
+---
+
+## When to Use
+
+Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.
+
+# Logistics Exception Management
+
+## Role and Context
+
+You are a senior freight exceptions analyst with 15+ years managing shipment exceptions across all modes — LTL, FTL, parcel, intermodal, ocean, and air. You sit at the intersection of shippers, carriers, consignees, insurance providers, and internal stakeholders. Your systems include TMS (transportation management), WMS (warehouse management), carrier portals, claims management platforms, and ERP order management. Your job is to resolve exceptions quickly while protecting financial interests, preserving carrier relationships, and maintaining customer satisfaction.
+
+## Core Knowledge
+
+### Exception Taxonomy
+
+Every exception falls into a classification that determines the resolution workflow, documentation requirements, and urgency:
+
+- **Delay (transit):** Shipment not delivered by promised date. Subtypes: weather, mechanical, capacity (no driver), customs hold, consignee reschedule. Most common exception type (~40% of all exceptions). Resolution hinges on whether delay is carrier-fault or force majeure.
+- **Damage (visible):** Noted on POD at delivery. Carrier liability is strong when consignee documents on the delivery receipt. Photograph immediately. Never accept "driver left before we could inspect."
+- **Damage (concealed):** Discovered after delivery, not noted on POD. Must file concealed damage claim within 5 days of delivery (industry standard, not law). Burden of proof shifts to shipper. Carrier will challenge — you need packaging integrity evidence.
+- **Damage (temperature):** Reefer/temperature-controlled failure. Requires continuous temp recorder data (Sensitech, Emerson). Pre-trip inspection records are critical. Carriers will claim "product was loaded warm."
+- **Shortage:** Piece count discrepancy at delivery. Count at the tailgate — never sign clean BOL if count is off. Distinguish driver count vs warehouse count conflicts. OS&D (Over, Short & Damage) report required.
+- **Overage:** More product delivered than on BOL. Often indicates cross-shipment from another consignee. Trace the extra freight — somebody is short.
+- **Refused delivery:** Consignee rejects. Reasons: damaged, late (perishable window), incorrect product, no PO match, dock scheduling conflict. Carrier is entitled to storage charges and return freight if refusal is not carrier-fault.
+- **Misdelivered:** Delivered to wrong address or wrong consignee. Full carrier liability. Time-critical to recover — product deteriorates or gets consumed.
+- **Lost (full shipment):** No delivery, no scan activity. Trigger trace at 24 hours past ETA for FTL, 48 hours for LTL. File formal tracer with carrier OS&D department.
+- **Lost (partial):** Some items missing from shipment. Often happens at LTL terminals during cross-dock handling. Serial number tracking critical for high-value.
+- **Contaminated:** Product exposed to chemicals, odors, or incompatible freight (common in LTL). Regulatory implications for food and pharma.
+
+### Carrier Behaviour by Mode
+
+Understanding how different carrier types operate changes your resolution strategy:
+
+- **LTL carriers** (FedEx Freight, XPO, Estes): Shipments touch 2-4 terminals. Each touch = damage risk. Claims departments are large and process-driven. Expect 30-60 day claim resolution. Terminal managers have authority up to ~$2,500.
+- **FTL/truckload** (asset carriers + brokers): Single-driver, dock-to-dock. Damage is usually loading/unloading. Brokers add a layer — the broker's carrier may go dark. Always get the actual carrier's MC number.
+- **Parcel** (UPS, FedEx, USPS): Automated claims portals. Strict documentation requirements. Declared value matters — default liability is very low ($100 for UPS). Must purchase additional coverage at shipping.
+- **Intermodal** (rail + drayage): Multiple handoffs. Damage often occurs during rail transit (impact events) or chassis swap. Bill of lading chain determines liability allocation between rail and dray.
+- **Ocean** (container shipping): Governed by Hague-Visby or COGSA (US). Carrier liability is per-package ($500 per package under COGSA unless declared). Container seal integrity is everything. Surveyor inspection at destination port.
+- **Air freight:** Governed by Montreal Convention. Strict 14-day notice for damage, 21 days for delay. Weight-based liability limits unless value declared. Fastest claims resolution of all modes.
+
+### Claims Process Fundamentals
+
+- **Carmack Amendment (US domestic surface):** Carrier is liable for actual loss or damage with limited exceptions (act of God, act of public enemy, act of shipper, public authority, inherent vice). Shipper must prove: goods were in good condition when tendered, goods arrived damaged/short, and the amount of damages.
+- **Filing deadline:** 9 months from delivery date for US domestic (49 USC § 14706). Miss this and the claim is time-barred regardless of merit.
+- **Documentation required:** Original BOL (showing clean tender), delivery receipt (showing exception), commercial invoice (proving value), inspection report, photographs, repair estimates or replacement quotes, packaging specifications.
+- **Carrier response:** Carrier has 30 days to acknowledge, 120 days to pay or decline. If they decline, you have 2 years from the decline date to file suit.
+
+### Seasonal and Cyclical Patterns
+
+- **Peak season (Oct-Jan):** Exception rates increase 30-50%. Carrier networks are strained. Transit times extend. Claims departments slow down. Build buffer into commitments.
+- **Produce season (Apr-Sep):** Temperature exceptions spike. Reefer availability tightens. Pre-cooling compliance becomes critical.
+- **Hurricane season (Jun-Nov):** Gulf and East Coast disruptions. Force majeure claims increase. Rerouting decisions needed within 4-6 hours of storm track updates.
+- **Month/quarter end:** Shippers rush volume. Carrier tender rejections spike. Double-brokering increases. Quality suffers across the board.
+- **Driver shortage cycles:** Worst in Q4 and after new regulation implementation (ELD mandate, FMCSA drug clearinghouse). Spot rates spike, service drops.
+
+### Fraud and Red Flags
+
+- **Staged damages:** Damage patterns inconsistent with transit mode. Multiple claims from same consignee location.
+- **Address manipulation:** Redirect requests post-pickup to different addresses. Common in high-value electronics.
+- **Systematic shortages:** Consistent 1-2 unit shortages across multiple shipments — indicates pilferage at a terminal or during transit.
+- **Double-brokering indicators:** Carrier on BOL doesn't match truck that shows up. Driver can't name their dispatcher. Insurance certificate is from a different entity.
+
+## Decision Frameworks
+
+### Severity Classification
+
+Assess every exception on three axes and take the highest severity:
+
+**Financial Impact:**
+
+- Level 1 (Low): < $1,000 product value, no expedite needed
+- Level 2 (Moderate): $1,000 - $5,000 or minor expedite costs
+- Level 3 (Significant): $5,000 - $25,000 or customer penalty risk
+- Level 4 (Major): $25,000 - $100,000 or contract compliance risk
+- Level 5 (Critical): > $100,000 or regulatory/safety implications
+
+**Customer Impact:**
+
+- Standard customer, no SLA at risk → does not elevate
+- Key account with SLA at risk → elevate by 1 level
+- Enterprise customer with penalty clauses → elevate by 2 levels
+- Customer's production line or retail launch at risk → automatic Level 4+
+
+**Time Sensitivity:**
+
+- Standard transit with buffer → does not elevate
+- Delivery needed within 48 hours, no alternative sourced → elevate by 1
+- Same-day or next-day critical (production shutdown, event deadline) → automatic Level 4+
+
+### Eat-the-Cost vs Fight-the-Claim
+
+This is the most common judgment call. Thresholds:
+
+- **< $500 and carrier relationship is strong:** Absorb. The admin cost of claims processing ($150-250 internal) makes it negative-ROI. Log for carrier scorecard.
+- **$500 - $2,500:** File claim but don't escalate aggressively. This is the "standard process" zone. Accept partial settlements above 70% of value.
+- **$2,500 - $10,000:** Full claims process. Escalate at 30-day mark if no resolution. Involve carrier account manager. Reject settlements below 80%.
+- **> $10,000:** VP-level awareness. Dedicated claims handler. Independent inspection if damage. Reject settlements below 90%. Legal review if denied.
+- **Any amount + pattern:** If this is the 3rd+ exception from the same carrier in 30 days, treat it as a carrier performance issue regardless of individual dollar amounts.
+
+### Priority Sequencing
+
+When multiple exceptions are active simultaneously (common during peak season or weather events), prioritize:
+
+1. Safety/regulatory (temperature-controlled pharma, hazmat) — always first
+2. Customer production shutdown risk — financial multiplier is 10-50x product value
+3. Perishable with remaining shelf life < 48 hours
+4. Highest financial impact adjusted for customer tier
+5. Oldest unresolved exception (prevent aging beyond SLA)
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Pharma reefer failure with disputed temps:** Carrier shows correct set-point; your Sensitech data shows excursion. The dispute is about sensor placement and pre-cooling. Never accept carrier's single-point reading — demand continuous data logger download.
+
+2. **Consignee claims damage but caused it during unloading:** POD is signed clean, but consignee calls 2 hours later claiming damage. If your driver witnessed their forklift drop the pallet, the driver's contemporaneous notes are your best defense. Without that, concealed damage claim against you is likely.
+
+3. **72-hour scan gap on high-value shipment:** No tracking updates doesn't always mean lost. LTL scan gaps happen at busy terminals. Before triggering a loss protocol, call the origin and destination terminals directly. Ask for physical trailer/bay location.
+
+4. **Cross-border customs hold:** When a shipment is held at customs, determine quickly if the hold is for documentation (fixable) or compliance (potentially unfixable). Carrier documentation errors (wrong harmonized codes on the carrier's portion) vs shipper errors (incorrect commercial invoice values) require different resolution paths.
+
+5. **Partial deliveries against single BOL:** Multiple delivery attempts where quantities don't match. Maintain a running tally. Don't file shortage claim until all partials are reconciled — carriers will use premature claims as evidence of shipper error.
+
+6. **Broker insolvency mid-shipment:** Your freight is on a truck, the broker who arranged it goes bankrupt. The actual carrier has a lien right. Determine quickly: is the carrier paid? If not, negotiate directly with the carrier for release.
+
+7. **Concealed damage discovered at final customer:** You delivered to distributor, distributor delivered to end customer, end customer finds damage. The chain-of-custody documentation determines who bears the loss.
+
+8. **Peak surcharge dispute during weather event:** Carrier applies emergency surcharge retroactively. Contract may or may not allow this — check force majeure and fuel surcharge clauses specifically.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to situation severity and relationship:
+
+- **Routine exception, good carrier relationship:** Collaborative. "We've got a delay on PRO# X — can you get me an updated ETA? Customer is asking."
+- **Significant exception, neutral relationship:** Professional and documented. State facts, reference BOL/PRO, specify what you need and by when.
+- **Major exception or pattern, strained relationship:** Formal. CC management. Reference contract terms. Set response deadlines. "Per Section 4.2 of our transportation agreement dated..."
+- **Customer-facing (delay):** Proactive, honest, solution-oriented. Never blame the carrier by name. "Your shipment has experienced a transit delay. Here's what we're doing and your updated timeline."
+- **Customer-facing (damage/loss):** Empathetic, action-oriented. Lead with the resolution, not the problem. "We've identified an issue with your shipment and have already initiated [replacement/credit]."
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**Initial carrier inquiry:** Subject: `Exception Notice — PRO# {pro} / BOL# {bol}`. State: what happened, what you need (ETA update, inspection, OS&D report), and by when.
+
+**Customer proactive update:** Lead with: what you know, what you're doing about it, what the customer's revised timeline is, and your direct contact for questions.
+
+**Escalation to carrier management:** Subject: `ESCALATION: Unresolved Exception — {shipment_ref} — {days} Days`. Include timeline of previous communications, financial impact, and what resolution you expect.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------ | ---------------------------------------------- | ----------------- |
+| Exception value > $25,000 | Notify VP Supply Chain immediately | Within 1 hour |
+| Enterprise customer affected | Assign dedicated handler, notify account team | Within 2 hours |
+| Carrier non-response | Escalate to carrier account manager | After 4 hours |
+| Repeated carrier (3+ in 30 days) | Carrier performance review with procurement | Within 1 week |
+| Potential fraud indicators | Notify compliance and halt standard processing | Immediately |
+| Temperature excursion on regulated product | Notify quality/regulatory team | Within 30 minutes |
+| No scan update on high-value (> $50K) | Initiate trace protocol and notify security | After 24 hours |
+| Claims denied > $10,000 | Legal review of denial basis | Within 48 hours |
+
+### Escalation Chain
+
+Level 1 (Analyst) → Level 2 (Team Lead, 4 hours) → Level 3 (Manager, 24 hours) → Level 4 (Director, 48 hours) → Level 5 (VP, 72+ hours or any Level 5 severity)
+
+## Performance Indicators
+
+Track these metrics weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| -------------------------------------- | ------------------- | ------------- |
+| Mean resolution time | < 72 hours | > 120 hours |
+| First-contact resolution rate | > 40% | < 25% |
+| Financial recovery rate (claims) | > 75% | < 50% |
+| Customer satisfaction (post-exception) | > 4.0/5.0 | < 3.5/5.0 |
+| Exception rate (per 1,000 shipments) | < 25 | > 40 |
+| Claims filing timeliness | 100% within 30 days | Any > 60 days |
+| Repeat exceptions (same carrier/lane) | < 10% | > 20% |
+| Aged exceptions (> 30 days open) | < 5% of total | > 15% |
+
+## Additional Resources
+
+- For detailed decision frameworks, escalation matrices, and mode-specific workflows, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **triage and resolve logistics exceptions or design exception-handling playbooks**:
+
+- Handling delays, damages, shortages, misdeliveries, and claims across LTL, FTL, parcel, intermodal, ocean, or air.
+- Defining escalation rules, severity classification, and “eat‑the‑cost vs fight‑the‑claim” thresholds for your network.
+- Building SOPs, dashboards, or automation for OS&D, claims workflows, and customer communications during freight disruptions.
diff --git a/web-app/public/skills/logistics-exception-management/references/communication-templates.md b/web-app/public/skills/logistics-exception-management/references/communication-templates.md
new file mode 100644
index 00000000..99726782
--- /dev/null
+++ b/web-app/public/skills/logistics-exception-management/references/communication-templates.md
@@ -0,0 +1,1170 @@
+# Communication Templates — Logistics Exception Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing exception communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and escalation stage. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Initial Exception Notification to Carrier (Standard)](#1-initial-exception-notification-to-carrier-standard)
+2. [Initial Exception Notification to Carrier (Urgent)](#2-initial-exception-notification-to-carrier-urgent)
+3. [Customer Proactive Update — Delay](#3-customer-proactive-update--delay)
+4. [Customer Proactive Update — Damage](#4-customer-proactive-update--damage)
+5. [Customer Proactive Update — Loss](#5-customer-proactive-update--loss)
+6. [Escalation to Carrier Account Manager](#6-escalation-to-carrier-account-manager)
+7. [Escalation to Carrier VP/Director](#7-escalation-to-carrier-vpdirector)
+8. [Internal Escalation to VP Supply Chain](#8-internal-escalation-to-vp-supply-chain)
+9. [Claims Filing Cover Letter](#9-claims-filing-cover-letter)
+10. [Settlement Negotiation Response (Accepting)](#10-settlement-negotiation-response-accepting)
+11. [Settlement Negotiation Response (Rejecting)](#11-settlement-negotiation-response-rejecting)
+12. [Post-Resolution Summary](#12-post-resolution-summary)
+13. [Carrier Performance Warning](#13-carrier-performance-warning)
+14. [Customer Apology with Resolution](#14-customer-apology-with-resolution)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{pro_number}}` | Carrier PRO / tracking number | `PRO 1234-5678-90` |
+| `{{bol_number}}` | Bill of Lading number | `BOL-2025-04872` |
+| `{{po_number}}` | Customer purchase order number | `PO-88431` |
+| `{{shipment_id}}` | Internal shipment reference | `SHP-2025-11049` |
+| `{{carrier_name}}` | Carrier legal or DBA name | `Acme Freight, Inc.` |
+| `{{carrier_mc}}` | Carrier MC/DOT number | `MC-345678` |
+| `{{carrier_scac}}` | Carrier SCAC code | `ACMF` |
+| `{{origin_city_state}}` | Origin city and state | `Dallas, TX` |
+| `{{dest_city_state}}` | Destination city and state | `Columbus, OH` |
+| `{{ship_date}}` | Original ship date | `2025-09-14` |
+| `{{original_eta}}` | Original estimated delivery | `2025-09-17` |
+| `{{revised_eta}}` | Revised estimated delivery | `2025-09-19` |
+| `{{customer_name}}` | Customer company name | `Midwest Distribution Co.` |
+| `{{customer_contact}}` | Customer contact name | `Sarah Chen` |
+| `{{our_contact_name}}` | Our representative name | `James Petrovic` |
+| `{{our_contact_title}}` | Our representative title | `Transportation Manager` |
+| `{{our_contact_email}}` | Our representative email | `jpetrovic@company.com` |
+| `{{our_contact_phone}}` | Our representative phone | `(312) 555-0147` |
+| `{{our_company}}` | Our company name | `Consolidated Shippers LLC` |
+| `{{exception_date}}` | Date exception was identified | `2025-09-16` |
+| `{{commodity}}` | Freight commodity description | `Automotive brake assemblies` |
+| `{{weight}}` | Shipment weight | `12,400 lbs` |
+| `{{piece_count}}` | Piece/pallet count | `14 pallets` |
+| `{{freight_charge}}` | Freight charge amount | `$3,840.00` |
+| `{{cargo_value}}` | Declared cargo value | `$47,200.00` |
+| `{{claim_amount}}` | Claim dollar amount | `$47,200.00` |
+| `{{claim_number}}` | Carrier-assigned claim number | `CLM-2025-0398` |
+| `{{our_claim_ref}}` | Internal claim reference | `EXC-2025-1104` |
+| `{{deadline_date}}` | Response or action deadline | `2025-09-18 by 14:00 CT` |
+| `{{days_in_transit}}` | Days shipment has been moving | `5` |
+| `{{last_known_location}}` | Last scan or check-call location | `Indianapolis, IN terminal` |
+
+---
+
+## 1. Initial Exception Notification to Carrier (Standard)
+
+### When to Use
+- Exception identified through tracking, check-call miss, or OS&D report.
+- Severity is moderate — the shipment is delayed or has a discrepancy but is not in immediate jeopardy.
+- First outreach to carrier operations or dispatch regarding this specific issue.
+
+### Tone Guidance
+Keep this factual and collaborative. You are a professional notifying a partner of a discrepancy, not accusing anyone of failure. Assume good intent — the goal is to get information and a corrective plan, not to assign blame at this stage.
+
+### What NOT to Say
+- Do not threaten claims or contract consequences in the first contact.
+- Do not speculate on what caused the exception.
+- Do not use language like "you failed to" or "your driver caused" — you do not yet have confirmed root cause.
+- Do not copy the customer on carrier operational communications.
+
+### Subject Line
+
+```
+Exception Notice — PRO {{pro_number}} | {{origin_city_state}} to {{dest_city_state}} | BOL {{bol_number}}
+```
+
+### Body
+
+```
+Team,
+
+We are writing regarding a shipment exception on the following load:
+
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+ Commodity: {{commodity}}
+ Weight/Count: {{weight}} / {{piece_count}}
+
+EXCEPTION DETAILS:
+{{exception_description}}
+
+We identified this exception on {{exception_date}} at approximately {{exception_time}}.
+The last confirmed status was {{last_known_status}} at {{last_known_location}} on
+{{last_scan_date}}.
+
+We need the following from your team:
+
+ 1. Current physical location of the freight
+ 2. Updated ETA to the consignee
+ 3. Root cause of the delay or discrepancy
+ 4. Corrective action being taken
+
+Please respond by {{deadline_date}} so we can update our customer accordingly.
+
+If you have questions or need additional shipment details, contact me directly at
+{{our_contact_phone}} or {{our_contact_email}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}}
+```
+
+---
+
+## 2. Initial Exception Notification to Carrier (Urgent)
+
+### When to Use
+- Shipment is critical: production-down, store-opening, perishable, or high-value.
+- Exception creates immediate financial exposure (e.g., production line stoppage, contract penalty window).
+- Customer has already escalated or SLA breach is imminent (within 24 hours).
+
+### Tone Guidance
+Direct and time-bound. This is not hostile, but it communicates that the situation requires immediate action, not a callback tomorrow. Every sentence should drive toward a concrete next step. Use specific deadlines, not "as soon as possible."
+
+### What NOT to Say
+- Do not soften the urgency — "when you get a chance" undermines the entire message.
+- Do not issue ultimatums you cannot enforce at this stage.
+- Do not reference other shipments or unrelated performance issues — stay on this load.
+- Do not leave out the financial exposure figure; it justifies the urgency.
+
+### Subject Line
+
+```
+URGENT — Immediate Response Required | PRO {{pro_number}} | {{dest_city_state}} | ETA Miss
+```
+
+### Body
+
+```
+URGENT — IMMEDIATE RESPONSE REQUIRED
+
+This shipment requires your immediate attention. We need a substantive response
+by {{deadline_date}} — not an acknowledgment, but confirmed status and a recovery plan.
+
+SHIPMENT DETAILS:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+ Commodity: {{commodity}}
+ Weight/Count: {{weight}} / {{piece_count}}
+ Declared Value: {{cargo_value}}
+
+EXCEPTION:
+{{exception_description}}
+
+BUSINESS IMPACT:
+{{business_impact_description}}
+
+Estimated financial exposure if not resolved by {{resolution_deadline}}: {{financial_exposure}}.
+
+REQUIRED BY {{deadline_date}}:
+ 1. Confirmed physical location of the freight — verified, not last-scan
+ 2. Firm revised delivery date and time
+ 3. Name and direct phone number of the person managing recovery
+ 4. Written recovery plan
+
+If I do not have a response by the deadline above, I will escalate to your account
+management team and begin contingency planning, which may include diversion or
+re-tender.
+
+Contact me directly:
+{{our_contact_name}} | {{our_contact_phone}} | {{our_contact_email}}
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+```
+
+---
+
+## 3. Customer Proactive Update — Delay
+
+### When to Use
+- Transit delay confirmed or highly probable (revised ETA is beyond the committed window).
+- Send this before the customer discovers the delay on their own. Proactive communication preserves trust; reactive communication erodes it.
+- You have a revised ETA — even if approximate. If you have no ETA at all, say so and commit to a follow-up time.
+
+### Tone Guidance
+Honest and solution-forward. Acknowledge the delay plainly — do not bury it in qualifiers. Lead with the revised timeline, then explain briefly. The customer wants to know "when will I get my freight" before they want to know "what happened." Do not name the carrier or assign blame to any specific party.
+
+### What NOT to Say
+- Do not blame the carrier by name — say "our carrier partner," not "XYZ Trucking messed up."
+- Do not say "unforeseen circumstances" — be specific about the cause category (weather, equipment, routing).
+- Do not promise a revised ETA you cannot support. If uncertain, give a range.
+- Do not use "we apologize for any inconvenience" — it reads as form language. Be specific about the impact you understand.
+
+### Subject Line
+
+```
+Shipment Update — PO {{po_number}} | Revised ETA {{revised_eta}}
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I want to update you on PO {{po_number}} (our reference {{shipment_id}}) shipping
+from {{origin_city_state}} to {{dest_city_state}}.
+
+This shipment is experiencing a transit delay. The original estimated delivery was
+{{original_eta}}. Based on current status, the revised delivery estimate is
+{{revised_eta}}.
+
+CAUSE: {{delay_cause_customer_facing}}
+
+HERE IS WHAT WE ARE DOING:
+ - {{action_item_1}}
+ - {{action_item_2}}
+ - {{action_item_3}}
+
+I will send you another update by {{next_update_time}} with confirmed delivery
+details. If the timeline shifts further in either direction, you will hear from me
+immediately.
+
+If this delay impacts your operations and you need us to evaluate expedited
+alternatives, please let me know and I will have options to you within
+{{expedite_response_window}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+### Variant — Delay with No ETA Yet
+
+When you cannot provide a revised ETA, replace the ETA section:
+
+```
+This shipment is experiencing a transit delay. The original estimated delivery was
+{{original_eta}}. We do not yet have a confirmed revised delivery time, but I am
+working to get one and will update you by {{next_update_time}} today.
+```
+
+---
+
+## 4. Customer Proactive Update — Damage
+
+### When to Use
+- Carrier or consignee has reported visible damage at delivery or in transit.
+- Damage is confirmed or strongly suspected (e.g., photos from driver, consignee notation on POD).
+- Send before the customer calls you. If they are the consignee, send before they have to chase you for next steps.
+
+### Tone Guidance
+Lead with the resolution, not the problem. The customer's first question is "what are you going to do about it" — answer that before describing the damage. Be specific about the remediation path (replacement, credit, re-ship) and timeline. Express genuine concern for the business impact without being dramatic.
+
+### What NOT to Say
+- Do not lead with the damage description. The opening paragraph should be about the resolution path.
+- Do not say "these things happen in transit" — it minimizes the customer's loss.
+- Do not speculate on cause (packaging, handling, weather) until investigation is complete.
+- Do not ask the customer to file a claim — that is your job.
+
+### Subject Line
+
+```
+PO {{po_number}} — Delivery Update and Resolution Plan
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I am reaching out regarding PO {{po_number}} (our reference {{shipment_id}})
+delivered to {{dest_city_state}} on {{delivery_date}}.
+
+We have identified damage to a portion of this shipment and I want to walk you
+through the resolution we are putting in place.
+
+RESOLUTION:
+ {{resolution_description}}
+
+ Timeline: {{resolution_timeline}}
+
+DAMAGE DETAILS:
+ Items Affected: {{damaged_items_description}}
+ Extent: {{damage_extent}}
+ Pieces Affected: {{damaged_piece_count}} of {{piece_count}} total
+
+We are handling the carrier claim and investigation on our end — no action is
+needed from your team on that front.
+
+What we do need from you:
+ - Confirmation of the affected quantities once your receiving team completes
+ inspection
+ - Direction on whether you want us to {{resolution_option_a}} or
+ {{resolution_option_b}}
+
+I understand this impacts your {{customer_impact_area}} and I take that seriously.
+I will stay on this personally until it is fully resolved.
+
+Next update from me: {{next_update_time}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 5. Customer Proactive Update — Loss
+
+### When to Use
+- Shipment is confirmed lost — not just delayed or unlocated. A shipment is "lost" when the carrier has confirmed they cannot locate the freight after a thorough trace, OR when {{days_without_scan}} days have passed with no carrier response to trace requests.
+- This is the most sensitive exception communication. The customer is learning that their goods are gone. Do not send this template for a shipment that is merely late or temporarily unlocated.
+
+### Tone Guidance
+Empathetic, direct, and action-oriented. Do not hedge or use passive constructions — "your shipment has been lost" is clearer than "there appears to be a situation involving the non-delivery of your order." Immediately establish the action plan. The customer needs to know three things: (1) what happened, (2) what you are doing right now, and (3) when they will have resolution. Convey that you understand the severity.
+
+### What NOT to Say
+- Do not say "misplaced" or "misrouted" if the shipment is confirmed lost — it sounds like you are minimizing.
+- Do not say "we are still looking into it" without a concrete next step and deadline.
+- Do not blame the carrier by name.
+- Do not lead with the claims process — lead with the replacement or remediation plan. The customer needs their goods, not a claims education.
+- Do not use "unfortunately" more than once.
+
+### Subject Line
+
+```
+PO {{po_number}} — Shipment Status and Immediate Action Plan
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+I need to share a difficult update on PO {{po_number}} (our reference
+{{shipment_id}}), originally shipping {{origin_city_state}} to
+{{dest_city_state}} on {{ship_date}}.
+
+After an extensive trace with our carrier partner, we have confirmed that this
+shipment — {{piece_count}} of {{commodity}}, valued at {{cargo_value}} — has
+been lost in transit. I know this creates a real problem for your team and I want
+to lay out exactly what we are doing about it.
+
+IMMEDIATE ACTION PLAN:
+
+ 1. REPLACEMENT / RE-SHIP:
+ {{replacement_plan}}
+ Expected availability: {{replacement_date}}
+
+ 2. FINANCIAL REMEDIATION:
+ {{financial_remediation_plan}}
+ Timeline: {{financial_remediation_timeline}}
+
+ 3. CARRIER CLAIM:
+ We have filed a formal cargo claim against the carrier. This is our
+ responsibility to manage — you do not need to take any action on the
+ claim.
+ Claim reference: {{our_claim_ref}}
+
+ 4. PREVENTION:
+ {{prevention_steps}}
+
+I will call you at {{follow_up_call_time}} to discuss this directly and answer
+any questions. If you need to reach me before then, my cell is
+{{our_contact_phone}}.
+
+I take full ownership of making this right.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 6. Escalation to Carrier Account Manager
+
+### When to Use
+- Initial contact to carrier dispatch or operations has gone unanswered for 4+ hours on a standard exception, or 2+ hours on an urgent exception.
+- You have documented at least two prior outreach attempts (email, phone, or both) to the frontline contact.
+- The account manager is the next level of the carrier's organization who can apply internal pressure.
+
+### Tone Guidance
+Professional but firm. You are not angry — you are a business partner whose reasonable requests have been ignored, and you need the account manager to intervene. State the timeline of your attempts factually. Make the ask concrete. The account manager needs to know exactly what you need and by when so they can push their operations team.
+
+### What NOT to Say
+- Do not trash the frontline contact by name — say "your operations team" or "your dispatch."
+- Do not threaten to pull freight at this stage unless you mean it and have authority.
+- Do not pile on unrelated issues — stay on this shipment.
+
+### Subject Line
+
+```
+Escalation — No Response on PRO {{pro_number}} | Requires Your Intervention
+```
+
+### Body
+
+```
+{{carrier_account_manager_name}},
+
+I am escalating to you because I have been unable to get a substantive response
+from your operations team on a shipment exception that requires immediate
+attention.
+
+SHIPMENT:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ PO: {{po_number}}
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Original ETA: {{original_eta}}
+
+EXCEPTION:
+{{exception_description}}
+
+OUTREACH TIMELINE:
+ {{attempt_1_date_time}} — {{attempt_1_method}}: {{attempt_1_summary}}
+ {{attempt_2_date_time}} — {{attempt_2_method}}: {{attempt_2_summary}}
+ {{attempt_3_date_time}} — {{attempt_3_method}}: {{attempt_3_summary}}
+
+It has been {{hours_since_first_contact}} hours since our first outreach with no
+confirmed status or recovery plan.
+
+I need the following by {{deadline_date}}:
+ 1. Confirmed current location of the freight
+ 2. Firm revised ETA
+ 3. A direct contact managing the recovery who I can reach by phone
+
+My customer is waiting on this update and I cannot continue to respond with "we
+are working on it" without specifics.
+
+Please call me at {{our_contact_phone}} or reply to this email by the deadline
+above.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 7. Escalation to Carrier VP/Director
+
+### When to Use
+- Account manager has failed to resolve or respond within a reasonable window (typically 12–24 hours after account manager escalation).
+- The exception has significant financial exposure, or a pattern of similar failures exists.
+- You are prepared to reference contract terms, volume commitments, or documented performance history.
+- This is a formal escalation — send it knowing it may be shared with carrier executive leadership.
+
+### Tone Guidance
+Formal and data-driven. This is a business communication between senior professionals. No emotion, no sarcasm, no threats — but clear consequences stated as business realities. Reference specific contract provisions, dollar figures, and incident history. The VP needs to understand that this is not a one-off complaint; it is a business risk they need to manage.
+
+### What NOT to Say
+- Do not be sarcastic or condescending — "I'm sure you're very busy" undermines your credibility.
+- Do not make threats you cannot follow through on (e.g., "we will never use you again" when they are your only option for a lane).
+- Do not reference verbal promises or informal agreements — stick to what is documented.
+- Do not CC your customer. This is a carrier management conversation.
+
+### Subject Line
+
+```
+Executive Escalation — Unresolved Exception PRO {{pro_number}} | {{our_company}} Account
+```
+
+### Body
+
+```
+{{carrier_vp_name}},
+{{carrier_vp_title}}
+{{carrier_name}}
+
+I am writing to escalate a shipment exception that has not been resolved despite
+repeated engagement with your operations and account management teams.
+
+SHIPMENT DETAILS:
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Commodity: {{commodity}}
+ Shipment Value: {{cargo_value}}
+
+EXCEPTION SUMMARY:
+{{exception_description}}
+
+ESCALATION HISTORY:
+ {{escalation_timeline_summary}}
+
+ Total time without resolution: {{total_hours_unresolved}} hours.
+
+FINANCIAL EXPOSURE:
+ Direct cargo exposure: {{cargo_value}}
+ Customer penalty risk: {{customer_penalty_amount}}
+ Expedite/recovery costs: {{recovery_cost_estimate}}
+ Total potential exposure: {{total_financial_exposure}}
+
+CONTRACT REFERENCE:
+Per Section {{contract_section}} of our transportation agreement dated
+{{contract_date}}, {{relevant_contract_provision}}.
+
+{{#if pattern_exists}}
+PERFORMANCE PATTERN:
+This is not an isolated incident. Over the past {{pattern_period}}, we have
+logged {{incident_count}} exceptions on your loads, resulting in
+{{total_pattern_cost}} in direct costs. Specific incidents:
+ {{pattern_incident_list}}
+{{/if}}
+
+I need the following from your team by {{deadline_date}}:
+ 1. Full resolution of this specific shipment
+ 2. Written root cause analysis
+ 3. Corrective action plan to prevent recurrence
+
+I value the partnership between {{our_company}} and {{carrier_name}}, and I want
+to resolve this collaboratively. However, continued non-responsiveness will
+require us to reassess our routing and volume commitments on the
+{{origin_city_state}}–{{dest_city_state}} lane.
+
+I am available to discuss at {{our_contact_phone}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 8. Internal Escalation to VP Supply Chain
+
+### When to Use
+- Financial exposure exceeds your authority threshold (typically $25,000+ or customer-specific triggers).
+- Customer relationship is at risk and executive-to-executive communication may be required.
+- A decision is needed that is above your pay grade: re-tender, expedite at premium cost, authorize production-down recovery, or waive contractual terms.
+- You need VP awareness even if you do not need VP action — significant exceptions should not be surprises.
+
+### Tone Guidance
+Brief and structured. Your VP does not need the narrative — they need the numbers, the exposure, what you have already done, and what you need from them. Lead with the decision or awareness item. Use bullet points. This is an internal operational brief, not a customer communication.
+
+### What NOT to Say
+- Do not editorialize — "the carrier is terrible" adds nothing. State the facts.
+- Do not bury the financial number. It should be in the first three lines.
+- Do not present problems without proposed solutions.
+- Do not send this without having already exhausted the escalation steps within your authority.
+
+### Subject Line
+
+```
+[ACTION REQUIRED] Exception — {{customer_name}} PO {{po_number}} | ${{financial_exposure}} Exposure
+```
+
+### Body
+
+```
+{{vp_name}},
+
+Flagging an active exception that requires {{your_awareness / your_decision}}.
+
+BOTTOM LINE:
+ Customer: {{customer_name}}
+ Shipment: PO {{po_number}} / PRO {{pro_number}}
+ Exception Type: {{exception_type}}
+ Financial Exposure: ${{financial_exposure}}
+ Customer Risk: {{customer_risk_level}} — {{customer_risk_description}}
+
+SITUATION:
+ {{two_to_three_sentence_summary}}
+
+WHAT I HAVE DONE:
+ - {{action_taken_1}}
+ - {{action_taken_2}}
+ - {{action_taken_3}}
+
+WHAT I NEED FROM YOU:
+ {{decision_or_action_needed}}
+
+ Options:
+ A. {{option_a}} — Cost: ${{option_a_cost}} | Timeline: {{option_a_timeline}}
+ B. {{option_b}} — Cost: ${{option_b_cost}} | Timeline: {{option_b_timeline}}
+
+ My recommendation: Option {{recommended_option}} because {{rationale}}.
+
+I need a decision by {{decision_deadline}} to execute the recovery plan.
+
+—{{our_contact_name}}
+```
+
+---
+
+## 9. Claims Filing Cover Letter
+
+### When to Use
+- Decision has been made to file a formal freight claim against the carrier.
+- All supporting documentation has been gathered (BOL, POD, inspection reports, photos, invoice, packing list).
+- Claim is being sent within the filing window (9 months under Carmack Amendment for interstate; check state law or contract for intrastate or brokered freight).
+
+### Tone Guidance
+Formal and precise. This is a legal document. No emotion, no narrative, no relationship language. State the facts, cite the applicable law, list the enclosed documents, and demand payment. Every statement should be supportable with evidence. Use the carrier's legal name and MC number, not their DBA or sales contact's name.
+
+### What NOT to Say
+- Do not editorialize about the carrier's service or your frustration.
+- Do not include demands beyond the provable loss amount — consequential damages require separate analysis and legal review.
+- Do not omit the filing date or claim amount — these are jurisdictional requirements.
+- Do not reference settlement discussions or verbal admissions of fault.
+
+### Subject Line
+
+```
+Formal Freight Claim — PRO {{pro_number}} | Claim Amount: ${{claim_amount}}
+```
+
+### Body
+
+```
+ {{current_date}}
+
+VIA EMAIL AND CERTIFIED MAIL
+
+{{carrier_legal_name}}
+{{carrier_claims_address}}
+MC-{{carrier_mc}} / DOT-{{carrier_dot}}
+
+Attn: Claims Department
+
+RE: Formal Freight Claim
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Ship Date: {{ship_date}}
+ Origin: {{origin_city_state}}
+ Destination: {{dest_city_state}}
+ Our Reference: {{our_claim_ref}}
+ Claim Amount: ${{claim_amount}}
+
+Dear Claims Department:
+
+{{our_company}} hereby files this formal claim for {{claim_type}} against
+{{carrier_legal_name}} pursuant to the Carmack Amendment, 49 U.S.C. § 14706,
+and applicable regulations at 49 C.F.R. Part 370.
+
+FACTS:
+
+On {{ship_date}}, {{our_company}} tendered {{piece_count}} of {{commodity}},
+weighing {{weight}}, to {{carrier_legal_name}} at {{origin_facility}},
+{{origin_city_state}}, for transportation to {{dest_facility}},
+{{dest_city_state}}, under BOL {{bol_number}}.
+
+{{claim_facts_paragraph}}
+
+CLAIMED AMOUNT:
+
+The total claimed amount is ${{claim_amount}}, computed as follows:
+
+ {{claim_calculation_line_items}}
+
+ Total: ${{claim_amount}}
+
+This amount represents the {{value_basis}} of the goods at the time and place
+of shipment, supported by the enclosed invoice documentation.
+
+ENCLOSED DOCUMENTATION:
+
+ 1. Bill of Lading (BOL {{bol_number}})
+ 2. Delivery receipt / Proof of Delivery with consignee notations
+ 3. {{inspection_report_description}}
+ 4. Photographs of {{photo_description}}
+ 5. Commercial invoice(s) — Invoice No. {{invoice_numbers}}
+ 6. Packing list
+ 7. Shipper's certificate of value / weight
+ {{#if additional_documents}}
+ 8. {{additional_documents}}
+ {{/if}}
+
+DEMAND:
+
+{{our_company}} demands payment of ${{claim_amount}} within thirty (30) days
+of receipt of this claim, per 49 C.F.R. § 370.9. In the alternative, we
+request written acknowledgment within thirty (30) days and final disposition
+within one hundred twenty (120) days, as required by regulation.
+
+Please direct all claim correspondence to:
+
+ {{our_contact_name}}
+ {{our_contact_title}}
+ {{our_company}}
+ {{our_claims_address}}
+ {{our_contact_email}}
+ {{our_contact_phone}}
+
+ Claim Reference: {{our_claim_ref}}
+
+{{our_company}} reserves all rights and remedies available under applicable
+law, including the right to pursue this claim in a court of competent
+jurisdiction if not resolved within the regulatory timeframe.
+
+Respectfully,
+
+
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+```
+
+---
+
+## 10. Settlement Negotiation Response (Accepting)
+
+### When to Use
+- Carrier has offered a settlement amount and you have decided to accept it.
+- The settlement amount has been approved internally (check your authority level — partial settlements often require management sign-off).
+- You are ready to close the claim and release the carrier from further liability on this shipment.
+
+### Tone Guidance
+Professional and conclusive. You are closing a business matter, not doing the carrier a favor. Confirm the exact terms clearly — amount, payment method, timeline, and scope of release. Do not express gratitude for the settlement or suggest the amount was generous. It is a business resolution.
+
+### What NOT to Say
+- Do not say "thank you for your generous offer" — you are accepting fair compensation, not a gift.
+- Do not leave any ambiguity about what is being released — specify the PRO, BOL, and claim reference.
+- Do not agree to confidentiality clauses or broad releases without legal review.
+- Do not accept verbally — always confirm in writing.
+
+### Subject Line
+
+```
+Claim Settlement Acceptance — PRO {{pro_number}} | Claim {{our_claim_ref}}
+```
+
+### Body
+
+```
+{{carrier_claims_contact}},
+
+This letter confirms {{our_company}}'s acceptance of the settlement offer
+received on {{offer_date}} regarding the following claim:
+
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Our Reference: {{our_claim_ref}}
+ Your Reference: {{claim_number}}
+
+SETTLEMENT TERMS:
+
+ Settlement Amount: ${{settlement_amount}}
+ Payment Method: {{payment_method}}
+ Payment Due: Within {{payment_days}} business days of this acceptance
+ Scope of Release: Full and final settlement of all claims arising from PRO
+ {{pro_number}} / BOL {{bol_number}} for the shipment of
+ {{commodity}} from {{origin_city_state}} to
+ {{dest_city_state}} on {{ship_date}}
+
+Upon receipt of ${{settlement_amount}}, {{our_company}} releases
+{{carrier_legal_name}} (MC-{{carrier_mc}}) from any further liability related
+to the above-referenced shipment.
+
+This release does not extend to any other shipments, claims, or obligations
+between the parties.
+
+Please remit payment to:
+
+ {{our_company}}
+ {{our_remittance_address}}
+ {{our_payment_details}}
+
+ Reference: {{our_claim_ref}}
+
+Please confirm receipt of this acceptance and expected payment date.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 11. Settlement Negotiation Response (Rejecting)
+
+### When to Use
+- Carrier's settlement offer is below your documented loss amount and you have evidence to support a higher claim.
+- You are prepared to counter-offer with a specific amount backed by documentation.
+- You have reviewed the carrier's stated basis for the reduced offer and can address their objections.
+
+### Tone Guidance
+Firm and evidence-based. You are not offended by a low offer — you are correcting an inaccurate valuation. Walk through their reasoning, point out where it is wrong, and anchor your counter to specific evidence. Keep the door open for resolution but make clear that the documented loss supports your position.
+
+### What NOT to Say
+- Do not say "this is insulting" or express emotion about the offer amount.
+- Do not threaten litigation in the same sentence as a counter-offer — it contradicts the settlement posture.
+- Do not accept their framing if it is incorrect (e.g., if they depreciated new goods or excluded documented items).
+- Do not counter without supporting documentation — attach the evidence.
+
+### Subject Line
+
+```
+Claim {{our_claim_ref}} — Settlement Offer Declined | Counter-Offer Enclosed
+```
+
+### Body
+
+```
+{{carrier_claims_contact}},
+
+We have reviewed your settlement offer of ${{offered_amount}} dated
+{{offer_date}} for the following claim:
+
+ PRO Number: {{pro_number}}
+ BOL Number: {{bol_number}}
+ Our Reference: {{our_claim_ref}}
+ Your Reference: {{claim_number}}
+ Original Claim: ${{claim_amount}}
+
+We are unable to accept this offer. Our original claim of ${{claim_amount}} is
+supported by documented evidence, and the offered amount does not adequately
+compensate for the loss.
+
+RESPONSE TO YOUR STATED BASIS FOR REDUCTION:
+
+{{carrier_reduction_reason_1}}:
+ Our response: {{our_response_1}}
+ Supporting documentation: {{supporting_doc_1}}
+
+{{carrier_reduction_reason_2}}:
+ Our response: {{our_response_2}}
+ Supporting documentation: {{supporting_doc_2}}
+
+{{#if carrier_reduction_reason_3}}
+{{carrier_reduction_reason_3}}:
+ Our response: {{our_response_3}}
+ Supporting documentation: {{supporting_doc_3}}
+{{/if}}
+
+COUNTER-OFFER:
+
+{{our_company}} is willing to settle this claim for ${{counter_offer_amount}},
+which reflects {{counter_offer_basis}}.
+
+This counter-offer is supported by the following enclosed documentation:
+ {{counter_offer_documentation_list}}
+
+We request your response within {{response_days}} business days. We remain open
+to resolving this matter directly and would welcome a call to discuss if that
+would be productive.
+
+If we are unable to reach a fair resolution, we will need to evaluate our
+options under 49 U.S.C. § 14706, which provides a two-year statute of
+limitations from the date of claim denial.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## 12. Post-Resolution Summary
+
+### When to Use
+- Exception has been fully resolved — freight delivered, claim settled, or loss remediated.
+- Distribute to internal stakeholders: operations, account management, finance, and carrier procurement.
+- This becomes the permanent record of the exception and feeds carrier scorecard reviews.
+
+### Tone Guidance
+Neutral and analytical. This is a post-mortem, not a complaint. State what happened, what it cost, what was done, and what should change. Be specific about lessons learned — vague statements like "we need to communicate better" are worthless. Recommend concrete process changes.
+
+### What NOT to Say
+- Do not assign personal blame to individuals — focus on process and system failures.
+- Do not omit the financial impact even if the claim was settled favorably — the true cost includes staff time, expedite charges, and customer goodwill.
+- Do not skip the "prevention" section. If you cannot recommend a prevention step, say so and explain why.
+
+### Subject Line
+
+```
+[CLOSED] Exception Summary — {{customer_name}} / PRO {{pro_number}} | {{exception_type}}
+```
+
+### Body
+
+```
+EXCEPTION POST-RESOLUTION SUMMARY
+====================================
+
+Exception Reference: {{our_claim_ref}}
+Status: CLOSED — {{closure_date}}
+Prepared by: {{our_contact_name}}
+Distribution: {{distribution_list}}
+
+1. SHIPMENT DETAILS
+ Customer: {{customer_name}}
+ PO: {{po_number}}
+ PRO: {{pro_number}}
+ BOL: {{bol_number}}
+ Carrier: {{carrier_name}} (MC-{{carrier_mc}} / SCAC: {{carrier_scac}})
+ Route: {{origin_city_state}} → {{dest_city_state}}
+ Ship Date: {{ship_date}}
+ Commodity: {{commodity}}
+ Weight/Pieces: {{weight}} / {{piece_count}}
+
+2. EXCEPTION SUMMARY
+ Type: {{exception_type}}
+ Discovered: {{exception_date}}
+ Root Cause: {{confirmed_root_cause}}
+ Description: {{exception_narrative}}
+
+3. TIMELINE
+ {{exception_timeline}}
+
+4. FINANCIAL IMPACT
+ Cargo Loss/Damage: ${{cargo_loss_amount}}
+ Freight Charges (original): ${{freight_charge}}
+ Expedite / Recovery Costs: ${{recovery_costs}}
+ Customer Penalties / Credits: ${{customer_penalties}}
+ Internal Labor (est.): ${{internal_labor_cost}}
+ ─────────────────────────────────
+ Total Cost of Exception: ${{total_exception_cost}}
+
+ Claim Filed: ${{claim_amount}}
+ Settlement Received: ${{settlement_amount}}
+ Net Unrecovered Loss: ${{net_loss}}
+
+5. CUSTOMER IMPACT
+ {{customer_impact_summary}}
+ Customer Satisfaction Status: {{csat_status}}
+ Relationship Risk: {{relationship_risk_level}}
+
+6. CARRIER SCORECARD IMPACT
+ Carrier: {{carrier_name}}
+ Incidents (trailing 12 months): {{trailing_12_incident_count}}
+ On-Time Rate Impact: {{ot_rate_impact}}
+ Claims Ratio Impact: {{claims_ratio_impact}}
+ Recommended Action: {{carrier_recommended_action}}
+
+7. LESSONS LEARNED
+ {{lesson_1}}
+ {{lesson_2}}
+ {{lesson_3}}
+
+8. PROCESS IMPROVEMENTS
+ {{improvement_1}} — Owner: {{owner_1}} — Due: {{due_date_1}}
+ {{improvement_2}} — Owner: {{owner_2}} — Due: {{due_date_2}}
+ {{improvement_3}} — Owner: {{owner_3}} — Due: {{due_date_3}}
+
+====================================
+Filed in: {{document_management_location}}
+```
+
+---
+
+## 13. Carrier Performance Warning
+
+### When to Use
+- Carrier has a documented pattern of exceptions exceeding acceptable thresholds (e.g., on-time below 90%, claims ratio above 2%, multiple OS&D incidents in a quarter).
+- You have data from your TMS or scorecard to support the warning.
+- This is a formal notice — not a casual heads-up on a call. It creates a paper trail that supports future routing decisions or contract renegotiation.
+- Send after the pattern is established (typically 3+ incidents or a quarter of below-threshold performance), not after a single bad load.
+
+### Tone Guidance
+Data-first and dispassionate. Let the numbers make the case. You are not angry — you are a supply chain professional managing vendor performance. State the expectation, show where they fall short, and define the consequences clearly. Leave room for corrective action — you want them to improve, not just feel punished.
+
+### What NOT to Say
+- Do not make it personal — "your drivers don't care" is not professional.
+- Do not issue an ultimatum you are not prepared to enforce.
+- Do not send this during an active exception — wait until the current issue is resolved, then address the pattern.
+- Do not combine this with a new load tender or positive feedback — it dilutes the message.
+
+### Subject Line
+
+```
+Carrier Performance Notice — {{carrier_name}} (MC-{{carrier_mc}}) | {{performance_period}}
+```
+
+### Body
+
+```
+{{carrier_contact_name}},
+{{carrier_contact_title}}
+{{carrier_name}}
+
+This letter serves as a formal performance notice regarding {{carrier_name}}'s
+service on {{our_company}} freight during the period {{performance_period}}.
+
+PERFORMANCE SUMMARY:
+
+ Metric Target Actual Variance
+ ───────────────────── ──────── ──────── ────────
+ On-Time Delivery {{ot_target}} {{ot_actual}} {{ot_variance}}
+ Claims Ratio {{claims_target}} {{claims_actual}} {{claims_variance}}
+ Tender Acceptance {{ta_target}} {{ta_actual}} {{ta_variance}}
+ Check-Call Compliance {{cc_target}} {{cc_actual}} {{cc_variance}}
+ OS&D Incidents {{osd_target}} {{osd_actual}} {{osd_variance}}
+
+SPECIFIC INCIDENTS:
+
+ {{incident_date_1}} | PRO {{incident_pro_1}} | {{incident_type_1}} | ${{incident_cost_1}}
+ {{incident_date_2}} | PRO {{incident_pro_2}} | {{incident_type_2}} | ${{incident_cost_2}}
+ {{incident_date_3}} | PRO {{incident_pro_3}} | {{incident_type_3}} | ${{incident_cost_3}}
+ {{#if more_incidents}}
+ ({{additional_incident_count}} additional incidents detailed in attachment)
+ {{/if}}
+
+ Total Exception Cost ({{performance_period}}): ${{total_period_exception_cost}}
+
+VOLUME CONTEXT:
+
+During this period, {{carrier_name}} handled {{total_loads}} loads for
+{{our_company}} representing ${{total_freight_spend}} in freight spend. You are
+currently ranked {{carrier_rank}} of {{total_carriers}} carriers in our network
+for the lanes you serve.
+
+EXPECTATIONS:
+
+To maintain current volume and lane assignments, we require:
+ 1. {{expectation_1}}
+ 2. {{expectation_2}}
+ 3. {{expectation_3}}
+
+We require a written corrective action plan within {{corrective_plan_days}}
+business days of this notice.
+
+CONSEQUENCES:
+
+If performance does not improve to target levels within {{improvement_period}}:
+ - {{consequence_1}}
+ - {{consequence_2}}
+ - {{consequence_3}}
+
+We are committed to working with carrier partners who meet our service
+standards. I welcome a call to discuss this notice and develop a corrective plan
+together.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+
+CC: {{internal_cc_list}}
+```
+
+---
+
+## 14. Customer Apology with Resolution
+
+### When to Use
+- A significant exception has been fully resolved and the customer has received their freight, replacement, or credit.
+- The exception was severe enough to warrant a formal acknowledgment beyond the operational updates already sent.
+- You want to reinforce the relationship and demonstrate that systemic improvements are being made — not just a one-time fix.
+
+### Tone Guidance
+Genuine and specific. A good apology names the specific impact, describes what was done, and commits to specific prevention steps. It does not grovel or over-apologize — the customer is a business partner, not a victim. It should feel like it was written by a senior professional who understands their business, not a customer service script. End on a forward-looking note.
+
+### What NOT to Say
+- Do not use "we apologize for any inconvenience" — name the actual impact. "I know the two-day delay forced your team to reschedule the retail reset" is ten times more effective.
+- Do not blame the carrier or any third party. You own the customer relationship.
+- Do not make promises you cannot keep. "This will never happen again" is not credible. "Here are the three specific steps we are implementing" is.
+- Do not make this a sales pitch or segue into new services. Stay focused on the resolution.
+- Do not send this the same day as the resolution — wait 1–2 business days so the customer has confirmed the resolution is satisfactory.
+
+### Subject Line
+
+```
+PO {{po_number}} — Resolution Confirmed and Path Forward
+```
+
+### Body
+
+```
+{{customer_contact}},
+
+Now that PO {{po_number}} has been fully resolved, I want to close the loop
+personally.
+
+WHAT HAPPENED:
+On {{exception_date}}, {{exception_summary_one_sentence}}. This resulted in
+{{specific_customer_impact}}.
+
+WHAT WE DID:
+ - {{resolution_action_1}}
+ - {{resolution_action_2}}
+ - {{resolution_action_3}}
+ - Final resolution: {{final_resolution_summary}}
+
+WHAT WE ARE CHANGING:
+I do not want to repeat what you experienced. Here are the specific steps we
+are putting in place:
+
+ 1. {{prevention_step_1}}
+ 2. {{prevention_step_2}}
+ 3. {{prevention_step_3}}
+
+{{#if financial_goodwill}}
+GOODWILL:
+{{financial_goodwill_description}}
+{{/if}}
+
+I value your business and I value the trust your team places in us. I take it
+personally when we fall short of the standard you expect.
+
+If you have any remaining concerns about this shipment or anything else, I am
+always available at {{our_contact_phone}}.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_phone}} | {{our_contact_email}}
+```
+
+---
+
+## Usage Notes for AI Agents
+
+**Template Selection:** Match the template to the audience (carrier ops, carrier executive, customer, internal) and the stage of the exception lifecycle (detection, escalation, claims, resolution, post-mortem). When in doubt, start with the lowest-escalation template appropriate for the elapsed time and severity.
+
+**Variable Substitution:** All `{{variables}}` must be replaced before sending. If a value is unknown, do not leave the placeholder — either obtain the information or remove the section with a note that it will follow.
+
+**Conditional Sections:** Sections wrapped in `{{#if}}...{{/if}}` are optional and should be included only when the condition applies (e.g., `{{#if pattern_exists}}` in the VP escalation template).
+
+**Tone Calibration:** The tone guidance for each template reflects the appropriate register for that audience and situation. Do not soften escalation templates to be "nicer" or harden customer templates to be "tougher" — the calibration is deliberate.
+
+**Legal Disclaimers:** The claims filing cover letter references the Carmack Amendment (49 U.S.C. § 14706), which applies to interstate motor carrier shipments. For brokered freight, international shipments, or intrastate moves, verify the applicable legal framework before sending. When in doubt, route through legal review.
+
+**Timing:**
+- Initial carrier notification: within 1 hour of exception discovery.
+- Customer proactive update: within 2 hours of confirmed impact, or before the customer's next business-day start — whichever comes first.
+- Escalation to account manager: after 4 hours without response (2 hours for urgent).
+- Escalation to VP/Director: after 12–24 hours without account manager resolution.
+- Claims filing: as soon as documentation is assembled, within the 9-month statutory window.
+- Post-resolution summary: within 5 business days of closure.
+- Performance warning: after pattern is documented, not during an active exception.
+- Customer apology: 1–2 business days after resolution is confirmed.
\ No newline at end of file
diff --git a/web-app/public/skills/logistics-exception-management/references/decision-frameworks.md b/web-app/public/skills/logistics-exception-management/references/decision-frameworks.md
new file mode 100644
index 00000000..d96e3d12
--- /dev/null
+++ b/web-app/public/skills/logistics-exception-management/references/decision-frameworks.md
@@ -0,0 +1,1460 @@
+# Decision Frameworks — Logistics Exception Management
+
+This reference provides the detailed decision logic, scoring matrices, financial models,
+and mode-specific resolution workflows for logistics exception management. It is loaded
+on demand when the agent needs to make or recommend nuanced exception-handling decisions.
+
+All thresholds, timelines, and cost assumptions reflect US domestic and international
+freight operations across LTL, FTL, parcel, intermodal, ocean, and air modes.
+
+---
+
+## 1. Exception Severity Matrix
+
+### 1.1 Scoring Methodology
+
+Every incoming exception is scored across four dimensions. Each dimension produces a
+score from 1 to 5. The **composite severity** equals the **highest single-dimension
+score**, not the average — a shipment that scores 2/2/2/5 is a Level 5 exception
+because a single critical dimension governs urgency.
+
+After computing the raw composite, apply the **elevation modifiers** in §1.3 to
+arrive at the effective severity, which caps at Level 5.
+
+### 1.2 Full Severity Matrix
+
+#### Dimension A — Financial Impact
+
+| Level | Product Value at Risk | Expedite / Re-Ship Cost | Penalty Exposure | Typical Scenarios |
+|-------|----------------------|------------------------|-----------------|-------------------|
+| 1 — Minimal | < $1,000 | None or < $200 | None | Minor LTL shortage, single damaged carton, residential parcel delay |
+| 2 — Moderate | $1,000–$5,000 | $200–$1,500 | Informal customer credit request likely | Multi-carton LTL damage, regional FTL delay 1–2 days, parcel loss with declared value |
+| 3 — Significant | $5,000–$25,000 | $1,500–$8,000 | Contractual penalty triggers within 48 hrs | Full pallet damage, FTL delay into customer delivery window, ocean container shortage affecting production schedule |
+| 4 — Major | $25,000–$100,000 | $8,000–$35,000 | Active penalty clause or chargeback imminent | Multi-pallet loss, air freight failure on critical launch shipment, reefer failure on full trailer of produce |
+| 5 — Critical | > $100,000 | > $35,000 or no expedite option exists | Regulatory fine, contract termination risk, or litigation exposure | Full trailer loss/theft, ocean container of pharma with temp excursion, hazmat incident with EPA/DOT reporting obligation |
+
+#### Dimension B — Customer Impact
+
+| Level | Customer Tier | SLA Status | Business Impact to Customer | Typical Scenarios |
+|-------|-------------|-----------|---------------------------|-------------------|
+| 1 — Minimal | Standard / spot customer | No SLA or well within SLA window | Inconvenience only; customer has inventory buffer | Delay to distributor who carries 30-day stock |
+| 2 — Moderate | Regular account | SLA at risk but not yet breached | Customer will notice, may request credit | Delivery misses requested date but within contractual tolerance |
+| 3 — Significant | Key account (top 20%) | SLA breach within 24 hrs | Customer's operations impacted; regional stockout possible | Late delivery to DC feeding retail replenishment |
+| 4 — Major | Enterprise / strategic account | SLA already breached or will breach today | Customer's production line slowed, retail launch compromised, or their customer is impacted | Automotive JIT delivery failure, retail holiday launch delay |
+| 5 — Critical | Tier 1 enterprise or regulated customer | SLA breach + penalty clause triggered | Customer production shutdown, patient safety concern, or regulatory impact to customer | Pharma shipment to hospital, auto assembly plant line-down, government contract with liquidated damages |
+
+#### Dimension C — Time Sensitivity
+
+| Level | Available Recovery Window | Alternative Sourcing | Perishability | Typical Scenarios |
+|-------|--------------------------|---------------------|--------------|-------------------|
+| 1 — Minimal | > 5 business days before customer need-by | Multiple alternatives available | Non-perishable | Stock replenishment with safety stock in place |
+| 2 — Moderate | 2–5 business days | Alternatives available but at premium cost | Non-perishable, but inventory turn pressure | Promotional inventory needed before event window |
+| 3 — Significant | 24–48 hours | Limited alternatives, ground expedite still viable | Perishable with > 48 hrs remaining shelf life | Fresh produce with 5-day shelf life at day 3 |
+| 4 — Major | < 24 hours | Air expedite only option | Perishable with < 48 hrs remaining shelf life, or time-definite service commitment | Temperature-sensitive biotech, next-day surgical supplies |
+| 5 — Critical | No window — needed now | No alternative exists or product is custom/irreplaceable | Perishable with < 24 hrs, or already expired in transit | Transplant organs, custom-manufactured parts for shutdown line, court-ordered evidence delivery |
+
+#### Dimension D — Regulatory / Safety
+
+| Level | Regulatory Exposure | Safety Concern | Reporting Obligation | Typical Scenarios |
+|-------|-------------------|---------------|---------------------|-------------------|
+| 1 — None | No regulatory dimension | No safety concern | None | Standard dry freight, consumer goods |
+| 2 — Low | Regulatory dimension exists but no violation | Potential quality concern, no safety risk | Internal documentation only | Cosmetics with minor packaging damage, electronics with cosmetic dents |
+| 3 — Moderate | Potential regulatory inquiry if not documented properly | Quality compromise that could reach end consumer | Proactive notification to QA team; may require regulatory hold | Food products with cold chain deviation within acceptable range |
+| 4 — High | Regulatory violation likely if product reaches market | Potential safety risk to end consumer or handler | Mandatory internal reporting to quality/regulatory within 4 hrs; potential voluntary recall | Pharma with temp excursion beyond validated range, dietary supplements with contamination exposure |
+| 5 — Critical | Active regulatory violation; agency notification required | Immediate safety hazard | Mandatory external reporting (FDA, DOT, EPA, FMCSA) within hours; potential mandatory recall | Hazmat spill, pharma temp failure on life-saving medication, foodborne illness risk, leaking chemical container |
+
+### 1.3 Elevation Modifiers
+
+Apply these modifiers after computing the raw composite score. Elevation is additive
+but caps at Level 5.
+
+| Condition | Elevation |
+|-----------|-----------|
+| Customer is under active QBR (quarterly business review) period | +1 level |
+| This is the 3rd+ exception on the same lane in 30 days | +1 level |
+| Exception occurred on a shipment booked at premium/guaranteed service | +1 level |
+| Carrier involved is under corrective action plan | +1 level |
+| Shipment is for a new customer (first 90 days of relationship) | +1 level |
+| Media or public visibility risk (e.g., branded trailer, viral social media) | +2 levels |
+| Exception involves a shipment already recovering from a prior exception | +2 levels |
+
+### 1.4 Severity-to-Action Mapping
+
+| Effective Severity | Assigned To | Initial Response SLA | Customer Notification | Internal Notification | Review Cadence |
+|-------------------|-------------|---------------------|----------------------|----------------------|---------------|
+| Level 1 | Analyst (auto-assign) | 8 business hours | Only if customer inquires | None required | Daily batch review |
+| Level 2 | Analyst (auto-assign) | 4 business hours | Proactive if delivery date affected | Team lead dashboard | Daily batch review |
+| Level 3 | Senior analyst (manual assign) | 2 hours | Proactive with resolution timeline | Manager notification | Every 4 hours |
+| Level 4 | Senior analyst + team lead | 1 hour | Immediate proactive call, then written follow-up | Director notification; account team briefed | Every 2 hours |
+| Level 5 | Dedicated handler + manager direct oversight | 30 minutes | VP-to-VP or C-level communication path | VP notification within 1 hour; war-room if multiple Level 5s concurrent | Continuous until stabilized |
+
+---
+
+## 2. Financial Impact Calculation Model
+
+### 2.1 Total Exception Cost Formula
+
+```
+Total Exception Cost (TEC) = Product Loss (PL)
+ + Expedite / Re-Ship Cost (ERC)
+ + Customer Penalties (CP)
+ + Administrative Processing Cost (APC)
+ + Relationship Damage Estimate (RDE)
+ + Downstream Ripple Cost (DRC)
+```
+
+### 2.2 Component Definitions and Assumptions
+
+#### Product Loss (PL)
+
+PL equals the lesser of (a) replacement cost at current wholesale or (b) original
+invoice value, unless the customer contract specifies retail/resale valuation for
+chargeback purposes.
+
+- Damaged but salvageable: PL = invoice value × damage percentage. Use 25% for
+ cosmetic-only damage, 50% for functional-but-impaired, 100% for unsalvageable.
+- Shortage: PL = unit cost × units short.
+- Full loss: PL = full invoice value including freight-in if FOB Origin.
+- Temperature excursion: PL = full invoice value if excursion exceeds validated range.
+ No partial credit on regulated products — it is all or nothing.
+
+#### Expedite / Re-Ship Cost (ERC)
+
+Standard cost multipliers against base freight cost:
+
+| Expedite Method | Multiplier vs. Base Rate | Typical Lead Time | When to Use |
+|----------------|------------------------|------------------|-------------|
+| Ground re-ship (same mode) | 1.0–1.3× | Original transit time | Recovery window > 5 business days |
+| Ground expedite (team driver / exclusive-use) | 2.5–4.0× | 40–60% of standard transit | Recovery window 2–5 business days, shipment > 150 lbs |
+| LTL guaranteed (volume or guaranteed overnight) | 1.8–2.5× | Next-day to 2-day | Recovery window 1–3 days, shipment < 10,000 lbs |
+| Domestic air (next-flight-out, NFO) | 6–12× | Same day or next morning | Recovery window < 24 hrs, shipment < 2,000 lbs |
+| Domestic air charter | 15–30× | 4–8 hours | No commercial option fits; production shutdown imminent |
+| International air (ex. ocean recovery) | 8–15× ocean base rate | 2–5 days vs. 25–40 days ocean | Recovery window < 2 weeks on ocean lane |
+| Hotshot / sprinter van | Flat $2.50–$4.50 per mile | Depends on distance; ~500 mi/day | Small, urgent shipment (< 3,000 lbs); regional recovery |
+
+Example: Base FTL rate Chicago to Dallas = $2,800. Customer needs delivery in 18 hours
+instead of standard 2-day transit. Team driver expedite = $2,800 × 3.0 = $8,400.
+Air NFO for 800 lbs at $0.85/lb = $680 freight + $150 handling = $830. Air is cheaper
+if weight allows; FTL expedite is cheaper above roughly 4,000–5,000 lbs depending on lane.
+
+#### Customer Penalties (CP)
+
+| Penalty Type | Typical Range | Calculation |
+|-------------|--------------|-------------|
+| Retail chargeback (late delivery to DC) | $500 flat + $50–$150 per carton | Per retailer's vendor compliance guide |
+| Retail chargeback (ASN/labeling error from re-ship) | $200–$1,000 flat | Often triggered by rush re-ships that bypass EDI integration |
+| OTIF (On-Time In-Full) penalty | 3–8% of invoice value per occurrence | Walmart = 3% of COGS; other retailers vary |
+| Production downtime reimbursement | $5,000–$50,000 per hour of line stoppage | Per manufacturing customer contract; automotive lines often $25K+/hr |
+| Contractual SLA penalty | 1–5% of monthly freight spend per SLA breach | Cumulative; multiple breaches compound |
+| Ad-hoc customer credit / goodwill | 5–15% of invoice as credit memo | Discretionary; used to preserve relationship when no formal penalty exists |
+
+#### Administrative Processing Cost (APC)
+
+Internal labor cost to manage the exception from intake to closure:
+
+| Complexity Tier | Activities | Estimated Hours | Cost at $45/hr Fully Loaded |
+|----------------|-----------|----------------|---------------------------|
+| Tier 1 — Simple | Log, one carrier call, update customer, close | 1.5–2.5 hrs | $68–$113 |
+| Tier 2 — Standard | Log, multiple carrier contacts, file claim, gather docs, customer updates, close | 4–8 hrs | $180–$360 |
+| Tier 3 — Complex | All of Tier 2 + inspection coordination, multi-party dispute, escalation, legal review potential | 12–25 hrs | $540–$1,125 |
+| Tier 4 — Litigation track | All of Tier 3 + legal engagement, deposition prep, expert witnesses | 40–100+ hrs | $1,800–$4,500+ (plus external legal at $250–$450/hr) |
+
+#### Relationship Damage Estimate (RDE)
+
+This is the hardest component to quantify. Use these heuristics:
+
+- **New customer (< 6 months):** Exception during onboarding carries 3× the
+ relationship weight. A $2,000 failure can cost a $500K annual account. RDE = 10–20%
+ of estimated first-year revenue at risk of churn.
+- **Stable customer (> 2 years):** Single exception rarely causes churn. RDE = 0–2%
+ of annual revenue unless it is a pattern (3+ exceptions in 90 days, in which case
+ treat as new-customer risk).
+- **Customer under competitive bid:** Any exception during RFP evaluation period
+ from a competitor. RDE = 25–50% of annual revenue at risk.
+
+#### Downstream Ripple Cost (DRC)
+
+Costs that propagate beyond the immediate exception:
+
+- Inventory reorder disruption: If exception causes safety-stock depletion, the
+ replenishment order will be rushed. Estimate 1.5× standard inbound freight for
+ the replenishment cycle.
+- Warehouse receiving disruption: Unexpected returns, re-deliveries, or inspection
+ holds consume dock door time. Estimate $150–$300 per unplanned dock appointment.
+- Customer service call volume: Each exception generates 2–5 inbound customer
+ inquiries. At $8–$12 per call (including agent time and overhead), that is
+ $16–$60 per exception.
+- Reporting and analytics overhead: Carrier scorecards, root cause analysis
+ meetings, and corrective action documentation. Estimate 1–3 hours per qualifying
+ exception at $45/hr.
+
+### 2.3 Worked Examples
+
+#### Example A — LTL Damage, Mid-Value
+
+Shipment: 6 pallets of consumer electronics, Chicago to Atlanta.
+Invoice value: $18,500. One pallet fork-punctured at origin terminal.
+
+```
+PL = $18,500 × (1/6 pallets) × 100% (unsalvageable) = $3,083
+ERC = Re-ship 1 pallet via LTL guaranteed 2-day: $650 = $650
+CP = Retailer OTIF penalty: $18,500 × 3% = $555
+ (only if re-ship misses must-arrive-by date) = $555
+APC = Tier 2 standard claim: ~6 hrs × $45 = $270
+RDE = Stable customer, isolated incident: ~0% = $0
+DRC = 3 customer service calls × $10 = $30
+---
+TEC = $3,083 + $650 + $555 + $270 + $0 + $30 = $4,588
+```
+
+Decision: File claim for $3,083 product value + $650 re-ship cost = $3,733 carrier
+liability claim under Carmack. Customer penalty is shipper's loss unless carrier
+proximate cause can support consequential damages (unlikely under standard BOL terms).
+
+#### Example B — FTL Total Loss, High-Value
+
+Shipment: Full truckload of medical devices, Memphis to Los Angeles.
+Invoice value: $285,000. Shipment not delivered, no scans for 72 hours, presumed stolen.
+
+```
+PL = $285,000 (full invoice) = $285,000
+ERC = Air charter for replacement: $48,000 = $48,000
+CP = Hospital contract: 2 days production delay at $12,000/day = $24,000
+APC = Tier 4 (theft investigation + legal): ~60 hrs × $45
+ + external legal ~20 hrs × $350 = $9,700
+RDE = Strategic account in first year: 15% × $1.2M annual rev = $180,000
+DRC = Safety stock depletion replenishment, expedited inbound = $8,500
+---
+TEC = $285,000 + $48,000 + $24,000 + $9,700 + $180,000 + $8,500 = $555,200
+```
+
+Decision: Level 5 severity. Immediate VP notification. Law enforcement report filed.
+Carrier cargo insurance claim ($100K per occurrence typical — will not cover full
+loss). Shipper's all-risk cargo policy for excess. Customer air-chartered at shipper
+expense while claims are pursued. Consider consequential damages claim if carrier
+was negligent in vetting driver or equipment.
+
+#### Example C — Eat-the-Cost Decision
+
+Shipment: 2 cartons of office supplies, parcel ground, value $380.
+One carton crushed, contents destroyed.
+
+```
+PL = $190 (one carton) = $190
+ERC = Re-ship via ground: $12 = $12
+CP = None (internal office supply order) = $0
+APC = Tier 1 if filed: 2 hrs × $45 = $90
+RDE = N/A (internal) = $0
+DRC = None = $0
+---
+TEC = $190 + $12 + $0 + $90 + $0 + $0 = $292
+
+Potential claim recovery: $190 (carrier liability)
+Filing cost: $90 (internal processing)
+Net recovery: $190 - $90 = $100
+```
+
+Decision: Marginal. File only if parcel carrier has automated claims portal with < 15
+minutes processing time. Otherwise absorb and log for quarterly carrier review.
+
+---
+
+## 3. Carrier Response Decision Tree
+
+### 3.1 Path A — Cooperative Carrier
+
+The carrier acknowledges the exception, provides updates, and works toward resolution.
+This is the expected path with contracted carriers in good standing.
+
+| Checkpoint | Action | Expected Carrier Response | If Response is Inadequate |
+|-----------|--------|--------------------------|--------------------------|
+| 0 hrs (intake) | Send initial exception notice via carrier portal or email with PRO#, BOL#, description of exception, requested action, and response deadline | Acknowledgment within 1 hour during business hours | Move to Path B at 2 hrs |
+| 2 hrs | Verify carrier acknowledgment received; confirm they have assigned the exception internally | Carrier provides case/reference number and assigned handler name | Escalate to carrier's operations supervisor; send second notice with "Escalation" in subject |
+| 4 hrs | Request status update — what has the carrier done so far, what is the plan, what is the revised ETA or inspection timeline | Specific plan with timeline: "Driver ETA 6pm" or "Inspector scheduled tomorrow AM" | Call carrier's account representative (not just dispatch). Document that operational channel is unresponsive |
+| 8 hrs | Evaluate progress against carrier's stated plan. If delivery exception: is shipment moving? If damage: is inspection scheduled? | Tangible progress — updated tracking, inspection confirmed, driver checked in | Formal escalation email to carrier VP of Operations or regional director. CC your procurement/carrier management team |
+| 24 hrs | Full status review. For delays: confirm revised delivery date. For damage/loss: confirm claim documentation in progress | Delivery completed, or inspection done and claim packet received, or clear revised timeline with daily updates committed | If still unresolved: initiate backup carrier for re-ship (do not wait longer). File formal carrier complaint in carrier management system |
+| 48 hrs | Resolution or near-resolution expected for cooperative carriers | Claim acknowledged and in processing, or delivery completed with exception closed | Carrier performance review triggered. Procurement notified for quarterly scorecard impact |
+| 72 hrs | Any open delay or loss should be fully resolved or in active claim processing | Claim payment timeline provided (30/60/90 day), or shipment delivered and exception closed | Consider carrier probation for new shipments on this lane |
+
+### 3.2 Path B — Unresponsive Carrier
+
+The carrier is not intentionally difficult but is not responding — dispatch is
+overwhelmed, claims department is backed up, or the contact information is wrong.
+Common with smaller asset carriers and during peak season.
+
+| Checkpoint | Action | Objective | Escalation |
+|-----------|--------|-----------|-----------|
+| 0–2 hrs | Standard notice sent, no response received | Establish contact | Try all available channels: portal, email, phone. If broker-arranged shipment, contact broker AND underlying carrier |
+| 2 hrs | Call carrier dispatch directly. If no answer, leave voicemail with your callback number and shipment references. Send follow-up email with "URGENT — Response Required" subject | Get any human response | If broker-arranged: put broker on notice that their carrier is unresponsive. Broker has contractual obligation to manage their carrier |
+| 4 hrs | Second call to dispatch. Try driver's cell if available (from BOL or load confirmation). Contact carrier's safety/compliance department (different phone tree) as alternative entry point | Any status information | Notify your team lead. Begin contingency planning for re-ship or alternative resolution |
+| 8 hrs | Three-channel blitz: call dispatch, email operations manager (find on carrier's website or LinkedIn), send formal notice via certified email or fax referencing carrier's MC/DOT number | Formal documentation of non-response | Authorize re-ship or expedite without waiting for carrier. Send carrier a "Notice of Non-Response" documenting all contact attempts with timestamps |
+| 24 hrs | Final notice: "You have 24 hours to respond before we process this as an uncontested claim and adjust payment on open invoices" | Force response through financial leverage | Place freight payment hold on carrier's open invoices (coordinate with AP). File claim based on available documentation. Report to carrier management for immediate lane review |
+| 48 hrs | If still no response, treat as abandoned. Process claim against carrier's cargo insurance (contact their insurer directly if you have the policy info from onboarding). If shipment is still in transit/unknown: report to FMCSA for potential out-of-service carrier | Full recovery mode | Remove carrier from active routing guide. Escalate to your legal team if claim value > $10,000 |
+| 72 hrs | Formal demand letter from legal or via registered mail citing specific claim amount and legal basis (Carmack for domestic). 30-day response deadline per 49 CFR § 370.9 | Legal posture established | Begin preparation for small claims (< $10K) or federal court filing if value warrants |
+
+### 3.3 Path C — Adversarial Carrier
+
+The carrier denies liability, provides false information, disputes documentation,
+or acts in bad faith. This includes situations where the carrier's claims department
+issues a blanket denial without investigating.
+
+| Checkpoint | Action | Documentation Priority | Escalation |
+|-----------|--------|----------------------|-----------|
+| 0 hrs (denial received) | Review denial letter/email line by line. Identify the specific basis for denial (act of shipper, inherent vice, act of God, packaging, etc.) | Preserve all original documentation. Screenshot carrier portal status history before it can be altered | Assign to senior analyst or claims specialist, not junior staff |
+| 2 hrs | Draft point-by-point rebuttal addressing each denial reason with documentary evidence. Under Carmack, once shipper proves three elements (good condition at tender, damaged at delivery, damages amount), burden shifts to carrier | Organize evidence package: clean BOL, exception-noted POD, photos, packing specs, weight certificates, temperature logs | Brief team lead on denial and planned rebuttal strategy |
+| 4 hrs | Send formal rebuttal via email and carrier portal with all supporting evidence attached. Request "reconsideration of claim denial" and cite specific regulatory basis for carrier liability | Send via method that provides delivery confirmation. Keep copies of everything sent | If denial is clearly frivolous (e.g., "act of God" for a forklift puncture), notify carrier's account manager that denial is damaging the relationship |
+| 8 hrs | If carrier reaffirms denial: request the carrier's specific evidence supporting their defense. Under 49 CFR § 370.7, carrier must conduct a reasonable investigation before denying | Log all communications with exact timestamps. Note any inconsistencies between carrier's stated reasons and available evidence | Notify your manager and procurement. Begin calculating whether litigation cost is justified vs. claim value |
+| 24 hrs | Escalate to carrier's VP of Claims or General Counsel with a summary letter: claim facts, evidence, legal basis, prior communications timeline, and a settlement demand | Prepare a claim file that is litigation-ready even if you hope to settle: chronological narrative, evidence index, damages calculation, legal authority summary | Procurement to issue formal notice of dispute to carrier's sales team. Separate the business relationship discussion from the claims dispute |
+| 48 hrs | If no movement: engage third-party claims service or freight claims attorney for demand letter on legal letterhead. Cost: typically $500–$1,500 for demand letter, contingency fee of 25–33% if litigation needed | Provide complete file to outside counsel. Flag any potential weaknesses in your case (late filing, incomplete POD, packaging shortfalls) | Consider whether the carrier's business overall is worth preserving. If annual spend < claim value, this may be the last shipment regardless |
+| 72 hrs+ | Decision point: litigate, settle at a discount, or absorb. See §9 Eat-the-Cost Analysis for framework | Final evidence review and case assessment | VP-level decision on litigation vs. settlement vs. walk-away |
+
+### 3.4 Special Situation — Carrier Goes Dark Mid-Shipment
+
+When a carrier stops responding and the freight is in transit (not yet delivered):
+
+1. **Hour 0–1:** Attempt all contact channels (dispatch, driver cell, broker if applicable, carrier safety department). Check last known GPS/ELD position if available through your TMS integration or load-tracking platform.
+
+2. **Hour 1–4:** Contact the carrier's insurance company to verify the policy is active. If brokered, demand the broker provide proof of last contact with the driver and GPS coordinates. If no GPS data available and shipment is high-value (> $50K), consider engaging a freight recovery service.
+
+3. **Hour 4–8:** If high-value or theft indicators present (carrier is new, load was double-brokered, pickup was in a high-theft corridor like Los Angeles, Memphis, Dallas, or the I-10/I-95 corridors): file a report with local law enforcement in the jurisdiction of last known location. Notify CargoNet or FreightWatch if you have a subscription.
+
+4. **Hour 8–24:** If the carrier is a broker's carrier: put the broker on formal notice that they are liable for the full shipment value. If the carrier is your contracted carrier: activate your contingency carrier for the lane and begin re-shipping replacement product.
+
+5. **Hour 24+:** Treat as presumed theft/loss. File formal claim. Notify your cargo insurance underwriter. Do not wait for "certainty" — the claim clock starts ticking.
+
+---
+
+## 4. Claims Filing Decision Framework
+
+### 4.1 File vs. Absorb vs. Negotiate Pre-Claim
+
+The decision to file a formal claim is not automatic. Each path has costs and trade-offs.
+
+#### Decision Matrix
+
+| Scenario | Recommended Path | Rationale |
+|----------|-----------------|-----------|
+| Claim value < $250, carrier has self-service portal | File via portal (< 15 min effort) | Automated filing cost is near-zero; builds claims history for scorecard |
+| Claim value < $500, no portal, good carrier relationship | Absorb, log for scorecard | APC exceeds likely net recovery. Mention informally to carrier rep at next review |
+| Claim value $500–$2,500, clear carrier liability | Negotiate pre-claim: call carrier and propose a freight credit or invoice deduction | Faster resolution (days vs. months), preserves relationship, avoids formal claims overhead |
+| Claim value $500–$2,500, disputed liability | File formal claim with documentation | Dispute needs formal record; informal negotiation without documentation weakens your position |
+| Claim value $2,500–$10,000 | File formal claim regardless of circumstances | Value justifies APC and relationship friction. Negotiate settlement only above 75% of claimed amount |
+| Claim value > $10,000 | File formal claim + involve senior management + legal awareness | Financial materiality threshold. Full documentation package. Independent inspection for damage claims. Accept settlement only above 85% or with strong business justification |
+| Any amount, 3rd+ claim against same carrier in 90 days | File formal claim AND trigger carrier performance review | Pattern indicates systemic issue; formal filing creates the record needed for contract renegotiation or termination |
+| Any amount, possible fraud indicators | File formal claim + notify compliance + preserve all evidence | Even small-dollar fraud must be documented. Patterns emerge only when individual incidents are formally recorded |
+
+#### ROI Calculation for Filing
+
+```
+Net Claim ROI = (Claim Amount × Probability of Recovery) - APC
+
+where:
+ Claim Amount = documented loss value (PL + ERC if carrier-caused)
+ Probability of Recovery = see §4.2 below
+ APC = administrative processing cost from §2.2
+```
+
+File when Net Claim ROI > $0 and the ratio (Net Claim ROI / Claim Amount) > 15%.
+Below 15% net margin on the claim, the organizational cost-of-attention often
+exceeds the financial benefit unless the claim builds a needed pattern record.
+
+### 4.2 Probability of Recovery by Carrier Type and Claim Type
+
+These recovery rates reflect industry experience across hundreds of thousands of
+claims. Adjust ±10% based on your specific carrier relationships and documentation
+quality.
+
+| Carrier Type | Damage (visible, noted on POD) | Damage (concealed) | Shortage (noted at delivery) | Full Loss | Delay (service failure) |
+|-------------|-------------------------------|-------------------|----------------------------|----------|----------------------|
+| National LTL (FedEx Freight, XPO, Estes, ODFL) | 80–90% | 40–55% | 70–80% | 85–95% | 15–25% (unless guaranteed service) |
+| Regional LTL | 70–85% | 30–45% | 60–75% | 75–85% | 10–20% |
+| Asset FTL carrier (large fleet) | 75–90% | 35–50% | 65–80% | 80–90% | 20–35% |
+| Small FTL carrier (< 50 trucks) | 55–70% | 20–35% | 45–60% | 50–65% | 5–15% |
+| Broker-arranged FTL | 60–75% | 25–40% | 50–65% | 60–75% | 10–20% |
+| Parcel (UPS, FedEx, USPS) | 70–85% | 45–60% | 60–75% | 80–90% | 30–50% (guaranteed service) |
+| Ocean (FCL) | 30–50% | 15–25% | 40–55% | 60–75% | < 5% |
+| Ocean (LCL) | 25–40% | 10–20% | 30–45% | 50–65% | < 5% |
+| Air freight (direct with airline) | 65–80% | 35–50% | 55–70% | 75–85% | 20–35% |
+| Air freight (via forwarder) | 55–70% | 25–40% | 45–60% | 65–80% | 15–25% |
+
+### 4.3 Documentation Checklist by Claim Type
+
+#### Damage Claim — All Modes
+
+Required:
+- [ ] Original BOL (signed, showing clean receipt by carrier at origin)
+- [ ] Delivery receipt / POD (showing exception notation — "damaged," "crushed," specific description)
+- [ ] Photographs: minimum 4 views (overview of shipment, close-up of damage, packaging condition, label/PRO visible)
+- [ ] Commercial invoice showing product value
+- [ ] Packing list showing piece count and descriptions
+- [ ] Written description of damage (what is damaged, extent, whether repairable)
+- [ ] Repair estimate or replacement quote from vendor
+- [ ] Packaging specifications (demonstrates product was packaged appropriately for the mode)
+
+Strongly recommended:
+- [ ] Weight certificate at origin (proves correct weight tendered)
+- [ ] Inspection report from independent surveyor (required for claims > $10,000 or disputed claims)
+- [ ] Temperature recorder data (for any temperature-sensitive product)
+- [ ] Photos from origin showing product in good condition at loading
+- [ ] Carrier inspection report (request from carrier's OS&D department)
+
+#### Shortage Claim
+
+Required:
+- [ ] Original BOL showing piece count tendered
+- [ ] Delivery receipt showing piece count received (discrepancy noted)
+- [ ] Commercial invoice for shorted product
+- [ ] Packing list with serial numbers or lot numbers if available
+- [ ] Written description: how many pieces short, which items, value per item
+
+Strongly recommended:
+- [ ] Loading photos/video showing correct count at origin
+- [ ] Seal numbers (origin seal vs. delivery seal — different seal = carrier liability strong)
+- [ ] Weight certificate at origin vs. weight at delivery (weight discrepancy corroborates shortage)
+- [ ] Security camera footage from dock (if available and shipment is high-value)
+
+#### Loss Claim (Full Shipment)
+
+Required:
+- [ ] Original BOL (proves tender to carrier)
+- [ ] Carrier pickup confirmation / signed pickup receipt
+- [ ] Commercial invoice (full shipment value)
+- [ ] Packing list (complete contents)
+- [ ] Formal tracer request filed with carrier (with carrier's response or non-response documented)
+- [ ] Proof of non-delivery: customer confirmation that product was never received
+
+Strongly recommended:
+- [ ] GPS/tracking history showing last known position
+- [ ] Law enforcement report (if theft suspected)
+- [ ] Carrier's insurance certificate (to file directly against insurer if carrier is unresponsive)
+- [ ] Evidence of carrier tender acceptance and load confirmation
+
+#### Delay Claim (Service Failure)
+
+Required:
+- [ ] Original BOL showing agreed pickup and delivery dates
+- [ ] Service level documentation (rate confirmation, routing guide showing guaranteed service)
+- [ ] Tracking history showing actual delivery date/time
+- [ ] Proof of financial loss caused by delay (penalty invoice, expedite receipt, lost sales documentation)
+
+Strongly recommended:
+- [ ] Customer correspondence showing delivery commitment that was based on carrier's service
+- [ ] Evidence that delay was not caused by shipper or consignee (no appointment changes, dock available)
+- [ ] Documentation of mitigation efforts (you tried to minimize the loss)
+
+### 4.4 Mode-Specific Filing Requirements
+
+#### US Domestic Surface — Carmack Amendment (49 USC § 14706)
+
+- **Jurisdiction:** All domestic surface transportation by motor carriers and freight forwarders operating under FMCSA authority.
+- **Filing deadline:** 9 months from date of delivery (or reasonable delivery date for non-delivery claims).
+- **Statute of limitations for litigation:** 2 years from the date the carrier disallows the claim.
+- **Carrier liability standard:** Carrier is strictly liable for actual loss, damage, or injury to goods. Carrier defenses: act of God, public enemy, act of shipper, public authority, inherent nature of goods.
+- **Shipper's burden:** (1) Goods were in good condition when tendered. (2) Goods were damaged/lost/short at destination. (3) Amount of damages.
+- **Limitation of liability:** Carriers may limit liability via released rates (lower rate in exchange for lower liability cap). Check your rate confirmation and BOL for released value clauses. If you did not agree to a released rate, full actual value applies.
+- **Filing method:** Written claim in any reasonable form that (a) identifies the shipment, (b) asserts liability, and (c) demands payment of a specific amount. 49 CFR § 370.3.
+- **Carrier response obligation:** Must acknowledge within 30 days. Must pay, decline, or make a firm settlement offer within 120 days. 49 CFR § 370.9.
+
+#### Ocean — Carriage of Goods by Sea Act (COGSA) / Hague-Visby Rules
+
+- **Jurisdiction:** International ocean shipments to/from US ports (COGSA); most international ocean shipments (Hague-Visby).
+- **Filing deadline:** Written notice of damage within 3 days of delivery (visible damage) or 3 days after delivery ends (concealed damage) under COGSA. Failure to give notice creates a presumption that goods were delivered in good condition — it does not bar the claim, but shifts the burden of proof.
+- **Statute of limitations:** 1 year from delivery date (COGSA). This is a hard deadline — cannot be extended without carrier agreement.
+- **Carrier liability standard:** Carrier is liable unless they prove one of 17 enumerated exceptions (perils of the sea, act of God, insufficiency of packing, etc.). Burden of proof is complex and shifting.
+- **Liability limit:** $500 per package or customary freight unit (COGSA). SDR 666.67 per package or SDR 2 per kg gross weight, whichever is higher (Hague-Visby). Higher value must be declared on the bill of lading before shipment.
+- **Critical documentation:** Ocean bill of lading, survey report at discharge port (hire a marine surveyor — typical cost $800–$2,500 depending on port), container inspection report, seal integrity evidence, reefer download data for temperature-controlled.
+
+#### Air — Montreal Convention (International) / Air Cargo Act (Domestic US)
+
+- **Jurisdiction:** International air carriage (Montreal Convention); domestic US air freight is governed by the air waybill terms and applicable contract law.
+- **Notice deadline:** 14 days from receipt for damage claims. 21 days from delivery date for delay claims. These deadlines are strictly enforced — missing them is a complete bar to the claim.
+- **Statute of limitations:** 2 years from date of arrival or from the date the aircraft ought to have arrived.
+- **Liability limit:** 22 SDR per kilogram (~$30/kg, fluctuates with exchange rates). Higher value must be declared on the air waybill. Most airlines offer declared-value surcharges of 0.5–0.75% of excess value.
+- **Filing method:** Written complaint to the airline or handling agent. Include air waybill number, flight numbers, claim details, and damage documentation.
+- **Key nuance:** Ground handling agents (the companies that physically handle freight at airports) cause the majority of air freight damage, but the airline is liable to the shipper under Montreal Convention. The airline then has a subrogation claim against the handler.
+
+---
+
+## 5. Mode-Specific Resolution Workflows
+
+### 5.1 LTL Damage Resolution
+
+#### 5.1.1 Terminal-Caused Damage
+
+Damage occurring at carrier's terminal during cross-dock operations (forklift
+damage, stacking failures, improperly loaded onto delivery trailer).
+
+**Indicators:** Damage pattern consistent with handling (fork punctures, crush from
+top-loading, stretch wrap torn with product exposed). Often discovered at delivery
+terminal or by consignee.
+
+**Resolution Workflow:**
+
+1. **Consignee documents on POD** — specific notation: "2 of 6 pallets crushed,
+ product visible through torn packaging." Generic "damaged" is insufficient for
+ strong claims.
+2. **Photograph at delivery** — minimum 6 photos: overall shipment, each damaged
+ unit, packaging failure point, freight label/PRO visible in frame, floor of
+ trailer showing debris.
+3. **Request carrier terminal inspection** — call the delivering terminal directly
+ (not the 800-number). Ask for the OS&D clerk or terminal manager. Request that
+ damaged freight be held for inspection, not sent to salvage.
+4. **File claim within 48 hours** — terminal damage claims have highest recovery
+ rates (80–90%) because the carrier knows their terminal caused it. Do not delay.
+5. **If partial damage** — request carrier's salvage bid. Carriers sometimes offer
+ to sell damaged freight at auction and credit the difference. Evaluate whether the
+ salvage value is fair; reject lowball salvage bids (common tactic to reduce claim
+ payout).
+6. **Settlement expectation** — terminal-caused damage should settle at 85–100%
+ of invoice value within 60 days. If carrier offers less than 75%, escalate to
+ carrier's claims manager with terminal inspection evidence.
+
+#### 5.1.2 Transit Damage
+
+Damage occurring during over-the-road transit (shifting loads, hard braking, trailer
+accident, weather infiltration through damaged trailer roof/walls).
+
+**Indicators:** Product shifted within packaging, load bars displaced, multiple
+pallets damaged in the same direction (forward movement = hard stop).
+
+**Resolution Workflow:**
+
+1. **Determine if damage is from a known incident** — ask carrier dispatch: "Was
+ there any reported incident involving this trailer in transit?" Carriers are
+ required to log accidents, but minor incidents (hard braking, pothole impact)
+ often go unreported.
+2. **Document loading condition evidence** — if you have photos from loading dock
+ showing freight was properly loaded, secured with load bars/straps, and braced
+ appropriately, your claim is significantly stronger.
+3. **Weigh the shipment** — if you can get a weight ticket from a scale near the
+ delivery point, compare to the origin weight ticket. Significant discrepancy
+ combined with damage suggests freight shifted or fell off a pallet.
+4. **File claim within 5 business days** — transit damage is moderately strong for
+ the shipper (70–85% recovery). Carrier will investigate with the driver and
+ potentially dispute if they believe packaging was insufficient.
+5. **Common carrier defense** — "Inadequate packaging." Counter with: packaging
+ specifications from the manufacturer, ISTA or ASTM test results if available,
+ and evidence that the same packaging has shipped successfully on this lane before
+ without damage.
+6. **Settlement expectation** — 60–85% of invoice value within 90 days. Transit
+ damage claims often involve more back-and-forth than terminal damage.
+
+#### 5.1.3 Loading Damage (Origin)
+
+Damage caused during pickup when the carrier's driver or dock workers load the
+freight onto the trailer.
+
+**Indicators:** Driver signs clean BOL at origin. Damage discovered at first
+cross-dock terminal or at delivery. Damage pattern consistent with improper
+stacking, dropping during loading, or trailer incompatibility (e.g., product loaded
+in a trailer with protruding floor nails).
+
+**Resolution Workflow:**
+
+1. **Check for driver exception notations on pickup BOL** — if the driver noted
+ "shipper load and count" (SL&C), carrier will argue they are not liable for
+ how the product was loaded. SL&C is the shipper's enemy on damage claims. If
+ your dock loaded the trailer while the driver was in the office, this notation
+ is legitimate and weakens your claim.
+2. **If carrier's driver loaded** — your claim is strong. Document that your dock
+ staff witnessed proper product condition before loading and that the carrier's
+ driver conducted the loading.
+3. **First-terminal inspection** — if damage is discovered at the first terminal,
+ request photos from the terminal before freight is further handled. This narrows
+ the damage window to pickup-to-first-terminal.
+4. **File claim within 5 business days** — include the clean-signed BOL from origin
+ and the exception-noted delivery receipt.
+5. **Settlement expectation** — 70–85% if you can prove damage occurred during
+ carrier loading. Under 50% if SL&C was notated and you cannot prove carrier
+ handling caused the damage.
+
+### 5.2 FTL Delay Resolution
+
+#### 5.2.1 Driver-Caused Delay
+
+Late pickup, wrong routing, hours-of-service (HOS) violation forcing a rest stop,
+driver no-show.
+
+**Resolution Workflow:**
+
+1. **Hour 0 (delay identified):** Contact dispatch. Get the driver's current
+ location, reason for delay, and revised ETA. If driver no-showed at origin:
+ demand a replacement driver or tractor within 2 hours, or you are tendering
+ to backup carrier.
+2. **Hour 2:** If revised ETA is within customer tolerance, monitor. If not:
+ calculate whether a team driver can recover the schedule. Team driver cost adder
+ is typically $0.25–$0.40/mile on top of the base rate.
+3. **Hour 4:** If delay will cause a customer miss: authorize the team driver or
+ arrange backup carrier from the driver's current location. The original carrier
+ is responsible for the deadhead to the driver's current location (demand credit
+ or refuse to pay for the partial haul).
+4. **Hour 8+:** If carrier cannot recover the shipment and you have re-tendered to
+ a backup carrier: deduct the expedite cost difference from the original carrier's
+ open invoices. Document everything for the debit.
+5. **Post-resolution:** Record the service failure in the carrier scorecard. If
+ this is a pattern (2+ HOS-driven delays from same carrier in 60 days), their
+ fleet management and driver scheduling practices need review.
+
+#### 5.2.2 Mechanical Breakdown
+
+Tractor or trailer breakdown in transit.
+
+**Resolution Workflow:**
+
+1. **Hour 0:** Carrier should notify you proactively per contract terms. If you
+ discover via tracking: call dispatch immediately.
+2. **Assess repair timeline:** If carrier says "truck will be repaired in 2 hours"
+ — accept and monitor. If > 4 hours or uncertain: demand the carrier power-swap
+ (send a replacement tractor to the breakdown location). Major carriers can
+ power-swap within 2–4 hours in most metro areas.
+3. **Reefer breakdown:** If reefer unit fails on a temperature-sensitive load, this
+ becomes a product quality issue, not just a delay. Request the carrier download
+ the reefer unit data log immediately. If ambient temperature is > 40°F and
+ product is cold-chain: begin contingency for product replacement within 2 hours
+ of reefer failure confirmation.
+4. **Carrier liability for mechanical:** Carrier is generally liable for delays caused
+ by mechanical failure — it is not "act of God." However, contractual terms may
+ exclude or limit delay liability. Check your carrier agreement.
+5. **Cost allocation:** Carrier should absorb any power-swap costs and incremental
+ transit cost. If you had to re-tender to a backup carrier, deduct the cost
+ difference from the original carrier.
+
+#### 5.2.3 Weather Delay
+
+Legitimate severe weather (winter storms, hurricanes, flooding, tornado activity)
+that prevents safe transit.
+
+**Resolution Workflow:**
+
+1. **Verify the weather event** — check NOAA and FMCSA road condition reports for
+ the specific route. Carriers sometimes claim "weather" for a light rain. The
+ delay must be proportional to the actual event severity.
+2. **Determine if the delay was avoidable** — if the weather was forecasted 48+
+ hours in advance and the carrier could have routed around it or departed earlier:
+ this is a planning failure, not force majeure. Challenge the carrier's defense.
+3. **Customer communication** — notify immediately with the weather event details
+ and revised ETA. Customers generally understand weather delays if communicated
+ proactively. Do not wait until the delivery window expires to notify.
+4. **Cost allocation** — true force majeure: neither party at fault. Carrier is not
+ liable for delay. Shipper cannot deduct. Expedite costs after the weather clears
+ are negotiable — the carrier should prioritize your shipment for recovery without
+ charging a premium. If they try to charge expedite rates for post-weather recovery,
+ push back.
+5. **Pattern recognition** — if a lane experiences 3+ weather delays per season
+ (e.g., Denver to Salt Lake City in January), build weather buffers into your
+ transit time commitments for that lane rather than treating each as an exception.
+
+#### 5.2.4 Capacity-Driven Delay
+
+Carrier accepted the tender but cannot cover it — no driver available. Common during
+peak season and month-end volume spikes.
+
+**Resolution Workflow:**
+
+1. **Hour 0 (carrier notifies or fails to cover):** Do not wait. Immediately
+ re-tender to backup carriers. Do not give the primary carrier "until end of day"
+ — capacity tightens as the day progresses. Every hour of delay reduces your
+ options.
+2. **Hour 2:** If primary carrier has not confirmed a driver: they have effectively
+ rejected the tender. Re-tender to backup or spot market. The primary carrier
+ owes you nothing for the delay (they did not pick up the freight), but you should
+ record the service failure as a tender acceptance failure.
+3. **Spot market premium:** If you must go to the spot market, the premium over
+ contract rate is your loss. Track this as "tender rejection cost" in carrier
+ scorecards. Typical spot premiums: 15–40% in normal market, 50–150% during
+ peak events or regional disruptions.
+4. **Contractual leverage:** If your carrier contract has tender acceptance minimums
+ (e.g., 90% acceptance rate), document every failure. Aggregate for quarterly
+ review. Carriers who repeatedly accept tenders and then fail to cover are worse
+ than carriers who reject upfront — they destroy your ability to plan.
+
+### 5.3 Parcel Loss Resolution
+
+#### 5.3.1 Ground Parcel Loss
+
+**Resolution Workflow:**
+
+1. **Day 1 past expected delivery:** Check tracking. If status is "delivered" but
+ customer says not received: request proof of delivery (signature, GPS stamp, photo).
+ If no GPS/photo evidence, the carrier's "delivered" scan is insufficient.
+2. **Day 2:** File online tracer through carrier portal. UPS: 1 business day for
+ tracer investigation. FedEx: 1–2 business days. USPS: mail search request, allow
+ 5–10 business days.
+3. **Day 3–5:** If tracer comes back "unable to locate": file formal claim through
+ carrier portal.
+4. **Day 5–10:** Re-ship replacement to customer. Do not wait for claim resolution
+ to keep the customer whole.
+5. **Claim processing:** UPS and FedEx typically resolve parcel claims within 5–8
+ business days of filing. USPS: 30–60 days. Ensure declared value was purchased
+ at time of shipping — default coverage is $100 (UPS/FedEx) or $50 (USPS Priority).
+6. **If claim denied:** Most common denial reason is "insufficient declared value."
+ If you declared the correct value at shipping, escalate. If you did not declare
+ sufficient value, the recovery is capped at the default limit regardless of
+ actual product value. This is an expensive lesson — ensure high-value parcel
+ shipments always have declared value coverage.
+
+#### 5.3.2 Air Parcel Loss (Next-Day/2-Day)
+
+Same workflow as ground with these adjustments:
+- Tracer filing is faster: file same day as missed delivery. Guaranteed service
+ means the carrier prioritizes the investigation.
+- Money-back guarantee: for late delivery on guaranteed services, file for full
+ shipping cost refund regardless of whether the product arrives the next day. This
+ is separate from a loss claim.
+- UPS and FedEx each have automated money-back guarantee claim portals. For late
+ NDA (Next Day Air), the refund is the full air shipping cost. These refunds can
+ be significant on heavy or multi-package shipments.
+
+#### 5.3.3 International Parcel Loss
+
+- Customs holds are the most common cause of apparent "loss" in international parcel.
+ Check customs status before filing a tracer.
+- International parcel claims involve both the origin country carrier and the
+ destination country carrier (or postal service). Filing is through the origin
+ carrier.
+- Liability is governed by the Universal Postal Convention (for postal services)
+ or the carrier's tariff (for UPS/FedEx/DHL international). UPS international
+ declared value cap is $50,000.
+- Allow 30–90 days for international claim resolution due to multi-country
+ investigation requirements.
+- For DDP (Delivered Duty Paid) shipments, you are responsible for duties/taxes
+ as part of the shipment value. Include these in the claim amount.
+
+### 5.4 Ocean Container Shortage Resolution
+
+#### 5.4.1 FCL (Full Container Load) Shortage
+
+Container delivered with fewer pieces than the packing list, despite the container
+seal being intact (or seal being different from the origin seal).
+
+**Resolution Workflow:**
+
+1. **At container unload:** Count every piece before signing the delivery receipt.
+ If the container is being unloaded at a CFS (Container Freight Station), ensure
+ the CFS provides a tally sheet.
+2. **Check the seal:** Compare the seal number on the container door to the seal
+ number on the bill of lading. If they match and are intact: the shortage likely
+ occurred at the origin (stuffing error). Carrier liability is weak — this is
+ a shipper/origin warehouse issue. If the seal is broken or does not match: carrier
+ liability is strong. Photograph the seal immediately.
+3. **File notice of shortage within 3 days** (COGSA requirement for concealed
+ shortage). File with the ocean carrier AND the party who delivered the container
+ (drayage company or terminal).
+4. **Hire a marine surveyor** if the shortage value exceeds $5,000. The surveyor's
+ report is the gold standard evidence for ocean claims. Cost: $800–$2,500
+ depending on the port and survey complexity.
+5. **Claim filing:** File against the ocean carrier under the bill of lading terms.
+ If the BL incorporates COGSA, liability is capped at $500 per package (a "package"
+ in FCL is typically interpreted as each carton, not the container). If you declared
+ a higher value on the BL, the higher value applies.
+6. **Recovery expectation:** FCL shortages with matching intact seals: 20–35%
+ recovery (carrier argues origin stuffing error). FCL shortages with broken/mismatched
+ seals: 65–80% recovery.
+
+#### 5.4.2 LCL (Less than Container Load) Shortage
+
+Product consolidated with other shippers' freight in a shared container. Shortages
+are more common due to additional handling at CFS facilities at both origin and
+destination.
+
+**Resolution Workflow:**
+
+1. **At CFS pickup/delivery:** Verify piece count against the house bill of lading
+ (not the master BL, which covers the full container). Annotate any discrepancy
+ on the CFS tally sheet and delivery receipt.
+2. **Identify the shortage point:** Was the shortage at origin CFS (loaded fewer
+ pieces), in transit, or at destination CFS (pieces misallocated to another
+ consignee's lot)? Request the CFS tally reports from both origin and destination.
+3. **Check for cross-allocation:** In LCL, your cargo may have been mistakenly
+ delivered to another consignee in the same container. Request the destination
+ CFS check all lots from the same container for over-shipment.
+4. **File claim with the NVOCC or freight forwarder** who issued your house bill
+ of lading. They are your contracting party. They will subrogate against the ocean
+ carrier or CFS operator as appropriate.
+5. **Recovery expectation:** LCL shortage claims take longer (90–180 days) and
+ recover at lower rates (30–50%) due to the difficulty of proving where in the
+ multi-handler chain the shortage occurred.
+
+### 5.5 Air Freight Damage Resolution
+
+#### 5.5.1 Airline Handling Damage
+
+Damage caused by the airline's cargo handling team during loading, transit, or
+unloading of the aircraft.
+
+**Resolution Workflow:**
+
+1. **At pickup from airline cargo terminal:** Inspect all pieces before signing the
+ cargo release. Note any damage on the release form with specific descriptions:
+ "carton #3 crushed on north face, contents exposed." Do not accept shipment
+ without noting the damage — once you sign clean, your concealed damage notice
+ window is only 14 days under Montreal Convention.
+2. **File written notice within 14 days** — this is a hard deadline. Miss it and
+ the claim is barred. Send notice to the airline's cargo claims department and to
+ the handling agent at the arrival airport.
+3. **Document the chain of custody:** Air freight often moves through multiple
+ handlers: origin forwarder → origin ground handler → airline → destination ground
+ handler → destination forwarder. Identify which handler had custody when the
+ damage occurred. The airline's internal damage reporting ("damage noted during
+ build-up/breakdown") is helpful — request it from the airline's cargo
+ department.
+4. **Liability under Montreal Convention:** 22 SDR/kg (approximately $30/kg). For
+ a 500 kg shipment, the maximum recovery is roughly $15,000 regardless of product
+ value. If your product value significantly exceeds the weight-based limit, you
+ should have purchased declared-value surcharge at booking (typically 0.50–0.75%
+ of the excess value). If you did not, recovery is capped at the Convention limit.
+5. **Recovery expectation:** Airline direct claims with proper documentation:
+ 65–80% of the applicable liability limit within 60–90 days.
+
+#### 5.5.2 Ground Handler Damage
+
+Damage caused by the ground handling company (Swissport, Menzies, WFS, dnata, etc.)
+that operates on behalf of the airline at the airport.
+
+**Resolution Workflow:**
+
+1. **Shipper files against the airline** — under Montreal Convention, the airline
+ is liable to the shipper regardless of whether the airline or the ground handler
+ caused the damage. The shipper does not need to prove which party handled the
+ freight at the time of damage.
+2. **Provide evidence to the airline** — the airline will conduct its own
+ investigation and may pursue the ground handler for indemnification. Providing
+ the airline with clear evidence (time-stamped photos, handling records, warehouse
+ receipt stamps) speeds the process.
+3. **If the airline denies** — they may argue the damage was pre-existing or caused
+ by inadequate packaging. Counter with origin photos, packaging specifications,
+ and the air waybill special handling instructions (e.g., "fragile," "this side up")
+ that the handler failed to follow.
+4. **Direct claim against ground handler:** In some cases, especially when the
+ airline is uncooperative, filing a direct claim against the ground handler under
+ local tort law is viable. Consult with an air cargo attorney — this is a
+ specialized area.
+
+### 5.6 Intermodal Liability Resolution
+
+#### 5.6.1 Determining Liability Between Rail and Dray
+
+Intermodal shipments involve at least two carriers: a drayage company (trucker) that
+picks up the container/trailer at the rail terminal and delivers to the consignee,
+and a railroad (BNSF, UP, CSX, NS, etc.) that performs the linehaul.
+
+**Resolution Workflow:**
+
+1. **Obtain the interchange records.** When the container moves from rail to dray
+ (or dray to rail), an interchange inspection is supposed to occur. The interchange
+ report documents the condition of the container and chassis at handoff. This
+ document determines liability allocation.
+
+2. **If damage is noted on the interchange report at rail-to-dray handoff:**
+ Rail is liable. File the claim with the railroad or the intermodal marketing
+ company (IMC) that booked the rail leg. Railroad claims are governed by the
+ Carmack Amendment for domestic intermodal.
+
+3. **If the interchange report is clean at rail-to-dray handoff, and damage is
+ found at delivery:** Drayage company is liable. The damage occurred during
+ the dray leg (local trucking from rail terminal to consignee). File with the
+ dray carrier.
+
+4. **If no interchange report exists** (common — many terminals skip this step):
+ Liability is disputed. Both the railroad and the dray will point at each other.
+ In this situation:
+ - File claims against both parties simultaneously.
+ - Provide the same evidence package to both.
+ - The party with the weaker defense will typically settle first.
+ - If neither settles: your claim is against the contracting party (whoever is
+ on your bill of lading), and they can subrogate against the other.
+
+5. **Railroad-specific considerations:**
+ - Railroads have their own claims rules and are notoriously slow (90–180 days
+ for resolution).
+ - Impact damage (shifting during railcar coupling, hard stops, derailment) is
+ common. Railroads have internal impact recording devices — request the data.
+ - Temperature damage on reefer intermodal: the rail carrier is responsible for
+ maintaining the reefer unit during rail transit if GenSet service was purchased.
+ If you provided a self-powered reefer unit, the rail carrier may argue the
+ unit failed on its own.
+
+6. **Chassis damage vs. cargo damage:** If the chassis (the wheeled frame the
+ container sits on) was damaged, causing the container to tilt or drop, this is
+ typically a rail terminal or dray carrier issue depending on where the chassis
+ was sourced. Chassis pool operators (DCLI, TRAC, Flexi-Van) may also be liable.
+ This creates a three-party dispute — carrier, chassis pool, and terminal operator.
+
+---
+
+## 6. Escalation Matrix
+
+### 6.1 Internal Escalation — Who, When, How
+
+| Severity / Trigger | Escalation Target (Role) | Information Required | Channel | Expected Response Time | Follow-Up Cadence |
+|--------------------|--------------------------|---------------------|---------|----------------------|-------------------|
+| Level 1 exception, no resolution after 48 hrs | Exception Team Lead | Exception summary, carrier contact log, current status | Email (team queue) or Slack/Teams channel | 4 business hours | Daily until resolved |
+| Level 2 exception, no resolution after 24 hrs | Exception Team Lead | Exception summary, financial impact estimate, carrier response history | Email with priority flag + verbal heads-up | 2 business hours | Every 8 hours |
+| Level 3 exception at intake | Exception Manager | Full exception brief: financial impact, customer impact, timeline, carrier status, recommended action | Phone call + email follow-up within 30 min | 1 hour | Every 4 hours |
+| Level 4 exception at intake | Director of Logistics / Director of Customer Operations | Executive summary: TEC calculation, customer risk, recommended action with cost estimate, alternatives considered | Phone call first, then email to director + CC manager | 30 minutes | Every 2 hours |
+| Level 5 exception at intake | VP Supply Chain + VP Sales (if customer-facing) | One-page executive brief: situation, financial exposure, customer impact, recommended immediate action, resource needs | Phone call to VP, then email summary to VP + director + manager. Schedule war-room call within 1 hour | 15 minutes | Continuous (war room) until stabilized, then every hour |
+| Carrier non-response after 4 hrs | Procurement / Carrier Management Analyst | Carrier name, MC#, exception details, all contact attempts with timestamps | Email to carrier management team | 4 business hours | Once (they own the carrier relationship escalation) |
+| Carrier non-response after 24 hrs | Procurement Manager / Director of Transportation | All of above + recommended financial leverage (invoice hold, lane removal) | Phone + email | 2 business hours | Daily until resolved |
+| Carrier claims denial > $10,000 | Legal / Risk Management Counsel | Complete claim file: claim filing, carrier denial, rebuttal sent, all evidence, financial exposure | Email with claim file attached + meeting request within 48 hrs | 48 hours for initial review | Weekly until disposition decided |
+| Customer escalation (customer contacts their account manager or executive) | Sales Account Manager + Exception Manager | Current exception status, all actions taken, timeline of communications, what we need from the customer | Immediate phone call to account manager + email brief | 30 minutes | Match the customer's requested cadence (usually every 4–8 hours) |
+| Potential fraud or compliance concern | Compliance Officer / Internal Audit | All available evidence, basis for suspicion, parties involved, recommended hold actions | Confidential email to compliance (do not discuss on open channels) | 4 business hours | As directed by compliance |
+| Regulatory reporting event (hazmat, food safety, pharma) | Quality/Regulatory Affairs Manager + Legal | Product details, exception specifics, regulatory exposure assessment, recommended agency notifications | Phone call immediately + email within 30 min | 15 minutes | Continuous until regulatory obligations met |
+
+### 6.2 External Escalation — Carrier-Side Contacts
+
+| Escalation Level | Carrier Contact (Title) | When to Engage | What to Say | Expected Outcome |
+|-----------------|------------------------|---------------|-------------|-----------------|
+| Level 1 | Carrier Customer Service / Dispatch Agent | First contact for any exception | State the exception, provide references, request status and ETA | Information and initial action |
+| Level 2 | Operations Supervisor / Terminal Manager | When Level 1 is unresponsive (2 hrs) or unable to resolve | Reference the open case number, state the business impact, request supervisor intervention | Escalated attention, possible override of standard process |
+| Level 3 | Regional Operations Director or VP Operations | When 2+ business days with no resolution, or high-value exception | Formal email referencing all prior communications, stating financial exposure and expected resolution | Direct oversight, dedicated resource assigned |
+| Level 4 | Carrier Account Manager / Director of Sales | When operational channels have failed and you need a business relationship lever | Contact through your procurement team. Frame as "this unresolved exception is affecting our routing decisions for this carrier" | Carrier sales team pressures their operations to resolve, often yields fastest results |
+| Level 5 | Carrier CEO / General Counsel | Litigation-track only, or when all other paths exhausted on high-value claim | Formal demand letter from your legal counsel to carrier's registered agent or general counsel | Legal posture established, settlement negotiation begins |
+
+### 6.3 External Escalation — Third Parties
+
+| Party | When to Engage | Contact Method | Cost | Expected Outcome |
+|-------|---------------|---------------|------|-----------------|
+| Independent marine / cargo surveyor | Damage claim > $5,000, or any disputed damage | Engage through your insurance broker's surveyor network, or directly via NAMS (National Association of Marine Surveyors) | $800–$2,500 per survey (domestic); $1,500–$5,000 (international) | Independent damage assessment report admissible in claims and litigation |
+| Third-party claims management firm | When internal claims volume exceeds capacity, or for complex multi-modal claims | Contract through RFP or direct engagement. Major firms: CIS (Claims Information Services), TranSolutions, NovaTrans | Contingency fee 25–33% of recovery, or flat fee $200–$800 per claim depending on complexity | Professional claims handling with higher recovery rates (typically 10–15% higher than in-house for complex claims) |
+| Freight claims attorney | Denied claims > $25,000, or any claim heading to litigation | Engage through industry referral (Transportation Intermediaries Association, Transportation Lawyers Association) | Contingency 25–33%, or hourly $250–$450 for pre-litigation work | Legal demand, negotiation, or litigation |
+| FMCSA (Federal Motor Carrier Safety Administration) | Carrier safety violations, out-of-service carrier, registration issues | File complaint online at NCCDB (National Consumer Complaint Database) or call 1-888-368-7238 | Free | Investigation of carrier safety record; public record |
+| STB (Surface Transportation Board) | Rate disputes, service complaints against railroads, intermodal disputes that cannot be resolved commercially | File formal complaint with the STB | Filing fees vary; legal representation recommended | Regulatory review and potential order against carrier |
+| Cargo insurance underwriter | Any loss exceeding your self-insured retention (SIR), or any total loss on insured shipment | Notify per your policy terms (typically within 30 days of loss discovery). Contact your insurance broker first | Claim against your own policy; subject to deductible and SIR | Insurance recovery minus deductible. Insurer may subrogate against carrier |
+
+---
+
+## 7. Time-Based Decision Triggers
+
+### 7.1 Checkpoint Framework
+
+This framework defines what decisions must be made and what actions must be taken at
+specific time intervals from exception intake. "Intake" is when the exception is first
+identified, regardless of when it actually occurred.
+
+#### Checkpoint: 2 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Severity classified? | Must have a score. If insufficient information to score, default to one level above what you suspect and gather data to confirm/downgrade |
+| Carrier contacted? | Initial contact must be made. If unable to reach carrier at 2 hrs, this is now Path B (Unresponsive) |
+| Customer notification needed? | Level 3+: customer must be notified by this checkpoint. Level 1–2: only if customer has already inquired |
+| Expedite decision needed? | If time sensitivity is Level 4+, the expedite vs. wait decision cannot wait past this checkpoint. Authorize or decline |
+| Is this a pattern? | Quick check: same carrier, same lane, same customer in last 30 days? If yes, apply elevation modifier |
+
+#### Checkpoint: 4 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Carrier response received? | If no response: escalate to carrier operations supervisor. Switch to Path B protocol |
+| Resolution timeline established? | Carrier should have provided a plan and timeline. If not: this is a carrier performance failure in addition to the original exception |
+| Internal escalation needed? | Level 3+: manager should be aware by now. Level 4+: director must be briefed |
+| Customer update #2 | For Level 3+: provide update even if no new information — silence is worse than "we're still working on it" |
+| Backup plan activated? | For time-sensitive exceptions: backup carrier or expedite method should be identified and on standby |
+
+#### Checkpoint: 8 Hours Post-Intake (End of Business Day)
+
+| Decision | Detail |
+|----------|--------|
+| Will this resolve today? | Honest assessment. If not: set next-day actions and ensure overnight monitoring for Level 4+ |
+| Financial impact calculated? | Full TEC should be computed by this point for Level 3+ exceptions |
+| Documentation gathered? | Photos, POD, BOL — everything needed for a claim should be in hand or requested with a deadline |
+| Customer expectation set? | Customer should have a specific revised delivery date or resolution timeline. Do not give "TBD" past 8 hours |
+| After-hours coverage needed? | For Level 4+: assign after-hours on-call responsibility. Provide the on-call person with a complete brief |
+
+#### Checkpoint: 24 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Resolution achieved? | Level 1–2 exceptions should be resolved or near-resolution by 24 hrs. If not: why? |
+| Claim filing decision made? | For damage/shortage/loss: you should know by now whether you are filing a claim, negotiating, or absorbing |
+| Carrier accountability documented? | Regardless of resolution, the carrier's performance on this exception must be logged for scorecard purposes |
+| Customer satisfaction check | For Level 3+: brief check-in with the customer. Are they satisfied with the resolution or progress? Adjust if needed |
+| Aging alert set | If not resolved: ensure the exception is in the "aging" report and will be reviewed at the next team stand-up |
+
+#### Checkpoint: 48 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Escalation review | Any exception open 48 hrs without clear resolution path: escalate to the next level in the chain, regardless of severity |
+| Claim filed? | If claim was warranted, it should be filed by now. Every day of delay weakens the claim (evidence degrades, carrier disputes increase) |
+| Root cause identified? | Even if the exception is not fully resolved, the root cause should be understood. If not: dedicate analytical resource to determine it |
+| Carrier relationship impact assessed? | Procurement/carrier management should have a view on whether this carrier needs a corrective action discussion |
+
+#### Checkpoint: 72 Hours Post-Intake
+
+| Decision | Detail |
+|----------|--------|
+| Resolution or plan | Exception must be either resolved OR have a documented resolution plan with a specific completion date |
+| Management review | All exceptions open > 72 hrs should be on the manager's weekly review report |
+| Customer mitigation complete? | Any customer-facing mitigation (re-ship, credit, expedite) should be completed by this point. The customer should not be waiting |
+
+#### Checkpoint: 5 Business Days
+
+| Decision | Detail |
+|----------|--------|
+| Concealed damage window closing | 5 days is the industry-standard window for concealed damage claims. If damage was discovered post-delivery, the claim must be filed by this point |
+| Team lead review | Team lead should review any exception open 5 days and assess whether it is being handled efficiently or is stuck |
+
+#### Checkpoint: 10 Business Days
+
+| Decision | Detail |
+|----------|--------|
+| Claim acknowledgment received? | If claim was filed, carrier must acknowledge within 30 days (per 49 CFR § 370.9), but should acknowledge within 10 business days. If not: follow up formally |
+| Exception aging report | 10-day open exceptions should appear on the manager-level report with a status update required |
+
+#### Checkpoint: 30 Calendar Days
+
+| Decision | Detail |
+|----------|--------|
+| Claim acknowledgment mandatory deadline | 30 days is the carrier's regulatory deadline to acknowledge a domestic claim. If not acknowledged: send formal notice citing 49 CFR § 370.9 and state that failure to comply is a regulatory violation |
+| Financial write-off or reserve decision | For unresolved claims: finance team should either reserve the claim amount or write it off, depending on recovery probability assessment |
+| Carrier performance review trigger | Any carrier with an exception open 30 days without resolution should be in a formal performance review conversation |
+
+### 7.2 Checkpoint Failure Protocol
+
+When a checkpoint decision is not made or action not taken by the deadline:
+
+1. **Immediate notification** to the next level in the escalation chain.
+2. **Root cause of the miss:** Was it capacity (analyst overwhelmed), information
+ (waiting on carrier/customer), process (no clear owner), or judgment (analyst
+ unsure how to proceed)?
+3. **Recovery action:** Assign fresh eyes. A different analyst reviews the exception
+ and picks up from the current state. Stale exceptions tend to stay stale with
+ the same handler.
+4. **Process improvement:** If the same checkpoint is repeatedly missed across
+ multiple exceptions, this is a systemic issue requiring process or staffing
+ review.
+
+---
+
+## 8. Multi-Exception Triage Protocol
+
+### 8.1 When to Activate Triage Mode
+
+Activate formal triage when any of these conditions are met:
+
+- 5+ new exceptions in a single 4-hour window
+- 3+ Level 3+ exceptions active simultaneously
+- A widespread disruption event (weather system, carrier outage, port closure, major highway closure) is generating exceptions faster than the team can process individually
+- Peak season daily exception volume exceeds 150% of the 30-day rolling average
+
+### 8.2 Triage Commander Role
+
+Designate a single **triage commander** (typically the team lead or the most senior
+analyst available) who:
+
+- Stops working individual exceptions.
+- Takes ownership of triage decisions: who works what, in what order.
+- Provides a single point of status aggregation for management and customer-facing
+ teams.
+- Has authority to re-assign analyst workloads, authorize expedites up to a
+ pre-approved threshold ($10,000 per incident without additional approval), and
+ communicate directly with carrier account managers and customer account teams.
+
+### 8.3 Triage Scoring — Rapid Prioritization
+
+When volume overwhelms the standard severity matrix process, use this rapid
+triage scoring:
+
+| Factor | Score 3 (Highest Priority) | Score 2 | Score 1 (Lowest Priority) |
+|--------|---------------------------|---------|--------------------------|
+| Time to customer impact | < 8 hours | 8–48 hours | > 48 hours |
+| Product at risk | Perishable, hazmat, pharma | High-value non-perishable (> $25K) | Standard product < $25K |
+| Customer tier | Enterprise / penalty contract | Key account | Standard |
+| Resolution complexity | Requires multi-party coordination | Single carrier, single action needed | Self-resolving (e.g., weather clearing) |
+| Can it wait 4 hours? | No — irreversible damage if delayed | Probably, but will cost more | Yes, no penalty for delay |
+
+Sum the scores (max 15). Process exceptions in descending score order.
+Ties are broken by: (1) regulatory/safety always wins, (2) then highest dollar
+value, (3) then oldest exception.
+
+### 8.4 Triage Communication Protocol
+
+During a triage event:
+
+**Internal:**
+- Triage commander sends a status update to management every 2 hours (or more
+ frequently if Level 5 exceptions are active).
+- Status update format: total exceptions active, top 3 by priority with one-line
+ status each, resource utilization (analysts assigned / available), estimated
+ clearance timeline.
+- Each analyst provides a 2-sentence status on each assigned exception every 2
+ hours to the triage commander.
+
+**Customer-facing:**
+- For widespread events (weather, carrier outage): issue a single proactive
+ communication to all affected customers rather than individual reactive updates.
+ Template: "We are aware of [event]. [X] shipments are potentially affected.
+ We are actively working with carriers to reroute/recover. Your account team
+ will provide individual shipment updates within [X] hours."
+- For individual high-priority exceptions during triage: customer update cadence
+ does not change (per severity level). The triage commander ensures high-priority
+ customer updates are not missed because the analyst is overwhelmed.
+
+**Carrier:**
+- During widespread events, contact the carrier's account manager or VP of
+ Operations (not dispatch) to get a single point of contact for all affected
+ shipments. Working shipment-by-shipment through dispatch during a triage event
+ is inefficient.
+- Request a carrier-side recovery plan for all affected shipments as a batch.
+
+### 8.5 Resource Allocation During Triage
+
+| Exception Priority (Triage Score) | Analyst Allocation | Manager Involvement | Customer Communication |
+|-----------------------------------|--------------------|--------------------|-----------------------|
+| Score 13–15 (Critical) | Dedicated senior analyst, 1:1 ratio | Direct manager oversight | VP or account director handles |
+| Score 10–12 (High) | Senior analyst, up to 3:1 ratio | Manager briefed every 2 hours | Account manager handles |
+| Score 7–9 (Medium) | Analyst, up to 5:1 ratio | Included in batch status report | Standard proactive template |
+| Score 4–6 (Low) | Deferred or batch-processed | No individual oversight | Reactive only (respond if customer asks) |
+
+### 8.6 Triage Deactivation
+
+Deactivate triage mode when:
+- Active exception count drops below 5
+- No Level 3+ exceptions remain unresolved
+- New exception intake rate returns to within 120% of the 30-day rolling average
+- All high-priority customer impacts are resolved or mitigated
+
+Conduct a triage debrief within 48 hours of deactivation: what went well, what
+broke, what needs to change for next time.
+
+---
+
+## 9. Eat-the-Cost Analysis Framework
+
+### 9.1 Decision Model
+
+The eat-the-cost decision determines whether pursuing a claim or dispute recovery
+generates a positive return after all costs — financial, temporal, and relational —
+are considered.
+
+```
+Net Recovery Value (NRV) = (Claim Amount × Recovery Probability × Time-Value Discount)
+ - Processing Cost
+ - Opportunity Cost
+ - Relationship Cost
+
+If NRV > 0 and NRV / Claim Amount > 15%: FILE
+If NRV > 0 but NRV / Claim Amount < 15%: FILE only if pattern documentation needed
+If NRV ≤ 0: ABSORB and log for carrier scorecard
+```
+
+### 9.2 Component Calculations
+
+#### Processing Cost by Complexity Tier
+
+| Tier | Criteria | Internal Hours | External Cost | Total Estimated Cost |
+|------|----------|---------------|--------------|---------------------|
+| A — Automated | Parcel claim via portal, simple damage with clear POD notation | 0.5 hrs ($23) | $0 | $23 |
+| B — Simple | LTL damage with good documentation, cooperative carrier, value < $2,500 | 2–3 hrs ($90–$135) | $0 | $90–$135 |
+| C — Standard | FTL damage/loss, value $2,500–$10,000, standard claim process | 5–8 hrs ($225–$360) | $0 | $225–$360 |
+| D — Complex | Multi-party dispute, ocean/air with international filing, disputed liability | 12–20 hrs ($540–$900) | Surveyor $800–$2,500 | $1,340–$3,400 |
+| E — Litigation-track | Denied claim heading to legal, value > $25,000 | 30–60 hrs ($1,350–$2,700) | Attorney $5,000–$25,000+ | $6,350–$27,700+ |
+
+#### Recovery Probability Adjustments
+
+Start with the base recovery probabilities from §4.2 and adjust:
+
+| Factor | Adjustment |
+|--------|-----------|
+| Documentation is complete and clean (photos, clean BOL, noted POD) | +10% |
+| Documentation is incomplete (missing photos or POD unsigned) | -15% |
+| Carrier has a history of paying claims promptly | +5% |
+| Carrier has a history of denying or slow-walking claims | -10% |
+| Claim is filed within 7 days of delivery | +5% |
+| Claim is filed 30+ days after delivery | -10% |
+| Independent survey/inspection supports the claim | +15% |
+| Product is temperature-controlled with continuous logger data | +10% (if data supports excursion) or -25% (if data is ambiguous or missing) |
+
+#### Time-Value Discount
+
+Claims take time. The money recovered 120 days from now is worth less than money
+in hand today.
+
+```
+Time-Value Discount Factor = 1 / (1 + (annual_cost_of_capital × estimated_days_to_recovery / 365))
+
+Typical: annual cost of capital = 8-12%
+```
+
+| Estimated Days to Recovery | Discount Factor (at 10% annual) |
+|---------------------------|-------------------------------|
+| 30 days | 0.992 |
+| 60 days | 0.984 |
+| 90 days | 0.976 |
+| 120 days | 0.968 |
+| 180 days | 0.953 |
+| 365 days | 0.909 |
+
+For most claims, the time-value discount is small (1–5%) and rarely drives the
+decision. It matters most for large claims (> $50K) with long expected resolution
+timelines (> 180 days).
+
+#### Opportunity Cost
+
+Every hour an analyst spends on a low-value claim is an hour not spent on a
+higher-value exception. Estimate:
+
+```
+Opportunity Cost = Processing Hours × (Average Exception Value Recovered per Analyst Hour - $45 blended labor cost)
+
+Typical: An experienced analyst recovers ~$1,200 per hour of claims work (blended across all claim sizes).
+Opportunity Cost ≈ Processing Hours × ($1,200 - $45) = Processing Hours × $1,155
+```
+
+This is the most often overlooked component. Filing a $500 claim that takes 4 hours
+to process costs the organization 4 × $1,155 = $4,620 in recoveries NOT pursued
+on other higher-value exceptions.
+
+However, this applies only when the analyst has a backlog of higher-value work.
+During low-volume periods, opportunity cost approaches zero and the threshold for
+filing drops.
+
+#### Relationship Cost
+
+This is the qualitative overlay. Assign one of these values:
+
+| Carrier Relationship Status | Relationship Cost Factor |
+|----------------------------|------------------------|
+| New carrier (< 6 months), building relationship | $500 imputed cost — filing a claim this early sends a signal. Absorb small claims if possible and address in the quarterly review |
+| Established carrier (6+ months), good relationship | $0 — professional carriers expect claims as part of the business. Filing does not damage the relationship if done respectfully |
+| Strategic carrier (top 5 by spend, or sole-source on critical lanes) | $250 imputed cost — even though the relationship is strong enough to handle claims, there is a negotiation overhead and quarterly review complexity |
+| Carrier under corrective action or on probation | Negative cost: -$200 (i.e., filing the claim is relationship-positive because it creates the documentation trail needed for contract renegotiation or termination) |
+
+### 9.3 Worked Examples
+
+#### Example: Should We File This $850 LTL Damage Claim?
+
+```
+Claim Amount: $850
+Carrier: National LTL, established relationship (18 months)
+Documentation: Complete (clean BOL, noted POD, photos)
+Complexity: Tier B (Simple)
+Base Recovery Prob: 85% (national LTL, visible damage noted on POD)
+Adjustments: +10% (complete documentation) → 95% (cap at 95%)
+
+Processing Cost: 2.5 hrs × $45 = $113
+Opportunity Cost: During peak season, analyst backlog is high →
+ 2.5 hrs × $1,155 = $2,888
+ During slow season (January): $0
+
+Relationship Cost: $0 (established, good relationship)
+Time-Value: 60-day expected resolution → discount factor 0.984
+
+NRV (peak season) = ($850 × 0.95 × 0.984) - $113 - $2,888 - $0
+ = $794 - $113 - $2,888 = -$2,207 → DO NOT FILE
+
+NRV (slow season) = ($850 × 0.95 × 0.984) - $113 - $0 - $0
+ = $794 - $113 = $681 → FILE (NRV/Claim = 80%)
+```
+
+During peak season, the analyst's time is better spent on higher-value
+exceptions. During slow season, file it — the analyst has bandwidth.
+
+#### Example: Should We File This $3,200 FTL Shortage Claim Against a Small Carrier?
+
+```
+Claim Amount: $3,200
+Carrier: Small asset carrier (12 trucks), 8-month relationship
+Documentation: Incomplete — POD was signed clean (driver left before
+ count completed), shortage discovered 1 hour later
+Base Recovery Prob: 55% (small FTL carrier, shortage)
+Adjustments: -15% (clean POD) → 40%
+Complexity: Tier C (Standard)
+
+Processing Cost: 6 hrs × $45 = $270
+Opportunity Cost: 6 hrs × $1,155 = $6,930 (peak), $0 (slow)
+Relationship Cost: $500 (relatively new carrier)
+Time-Value: 120-day expected → 0.968
+
+NRV (peak) = ($3,200 × 0.40 × 0.968) - $270 - $6,930 - $500
+ = $1,239 - $270 - $6,930 - $500 = -$6,461 → DO NOT FILE
+
+NRV (slow) = ($3,200 × 0.40 × 0.968) - $270 - $0 - $500
+ = $1,239 - $270 - $500 = $469 → MARGINAL
+
+Filing Ratio = $469 / $3,200 = 14.7% → BELOW 15% threshold → ABSORB
+```
+
+Even in the slow season, the low recovery probability (due to the clean POD)
+makes this a marginal claim. Decision: absorb, but use this as a coaching
+moment with the consignee about never signing clean before completing the count.
+Log for carrier scorecard. If it happens again with the same carrier, the pattern
+changes the calculus — file the second claim and reference both incidents.
+
+---
+
+## 10. Seasonal Adjustment Factors
+
+### 10.1 Peak Season Adjustments (October–January)
+
+During peak season, carrier networks are strained, transit times extend, exception
+rates increase 30–50%, and claims departments slow down. Adjust decision frameworks
+accordingly.
+
+| Parameter | Standard Setting | Peak Season Adjustment | Rationale |
+|-----------|-----------------|----------------------|-----------|
+| Carrier response SLA (before escalation) | 2 hours | 4 hours | Carrier dispatch is overwhelmed; allow more time before declaring unresponsive |
+| Customer notification threshold | Level 3+ proactive | Level 2+ proactive | Customer expectations are already fragile during peak; proactive communication prevents inbound complaint calls |
+| Expedite authorization threshold | Manager approval > $5,000 | Manager approval > $10,000 | Expedite costs are inflated 50–100% during peak; air capacity is scarce. Raise the bar for what justifies a premium expedite |
+| Eat-the-cost threshold | < $500 absorb | < $750 absorb | APC increases during peak (analysts are juggling more exceptions). Internal cost of claims processing rises |
+| Claims filing timeline | Within 5 business days | Within 10 business days | Realistic given volume. Still well within the 9-month Carmack window |
+| Carrier scorecard impact weight | Standard | 0.75× weighting | Across-the-board service degradation during peak is industry-wide. Do not penalize carriers disproportionately for systemic conditions, but still document everything |
+| Triage mode activation threshold | 5+ simultaneous exceptions | 8+ simultaneous (expect a higher baseline) | Baseline exception volume is higher; activate triage based on deviation from the elevated baseline |
+| Customer communication frequency (active exceptions) | Every 4 hours for Level 3+ | Every 8 hours for Level 3+ | Volume requires longer update cycles. Communicate the adjusted cadence to customer upfront: "During the holiday shipping season, we'll provide updates every 8 hours unless there is a material change" |
+| Settlement acceptance threshold | > 75% for $500–$2,500 range | > 65% for $500–$2,500 range | Faster settlement frees capacity for higher-value claims. Accept slightly lower recoveries to close volume |
+
+### 10.2 Weather Event Adjustments
+
+Applied when a named weather system (winter storm, hurricane, tropical storm) or
+widespread severe weather (tornado outbreak, flooding) is actively disrupting a
+region.
+
+| Parameter | Standard Setting | Weather Event Adjustment | Duration |
+|-----------|-----------------|------------------------|----------|
+| Carrier response SLA | 2 hours | 8 hours (carrier dispatch may be evacuated or overwhelmed) | Until 48 hours after last weather advisory expires |
+| Force majeure acceptance | Require specific documentation | Accept carrier's force majeure claim if weather event is confirmed by NOAA for the route and timeframe | Event duration + 72 hours recovery |
+| Expedite decisions | Standard ROI calculation | Suspend expedite for affected lanes until roads/airports reopen. Redirect expedite spend to alternative routing | Until carrier confirms lane is clear |
+| Customer communication | Standard cadence per severity | Issue blanket proactive communication to all customers with shipments on affected lanes. Individual follow-ups only for Level 4+ | Until all affected shipments are rescheduled |
+| Exception severity scoring | Standard matrix | Reduce time-sensitivity dimension by 1 level for weather-affected shipments (customer tolerance is higher for force majeure events) | Event duration + 24 hours |
+| Claim filing | Standard timeline | Delay claim filing for weather events; focus on recovery and rerouting. File after the event when full impact is known | File within 30 days of delivery/non-delivery |
+| Carrier scorecard | Standard weighting | 0.5× weighting for weather-affected lanes. Document for pattern tracking but do not penalize individual events | Exceptions within the event window only |
+
+### 10.3 Produce / Perishable Season Adjustments (April–September)
+
+Temperature-sensitive shipments increase dramatically. Reefer capacity tightens.
+Temperature exceptions spike.
+
+| Parameter | Standard Setting | Produce Season Adjustment | Rationale |
+|-----------|-----------------|--------------------------|-----------|
+| Temperature excursion response time | 2 hours to contact carrier | 1 hour to contact carrier | Perishable shelf life is non-recoverable. Every hour of delay in response reduces the salvageable value |
+| Pre-trip inspection documentation | Recommended | Required — do not load without confirmed pre-trip on reefer unit | Carrier defense #1 is "reefer was fine at dispatch; product was loaded warm." Pre-trip eliminates this |
+| Continuous temperature logging | Required for pharma/biotech | Required for ALL perishable shipments including produce, dairy, frozen food | Carrier disputes on temperature are unresolvable without continuous data |
+| Reefer breakdown escalation | 4 hours before power-swap demand | 2 hours before power-swap demand | Product degradation accelerates with ambient temperature. In July, a reefer failure in Phoenix means product loss in under 2 hours |
+| Carrier reefer fleet age threshold | Accept carriers with reefer units < 10 years old | Prefer carriers with reefer units < 5 years old during peak produce season | Older reefer units fail at higher rates in extreme heat |
+| Claim documentation for temperature | Standard photo + logger | Add: pre-cool records, loading temperature readings (infrared gun logs), in-transit monitoring alerts, reefer unit download data | Temperature claims require more evidence than any other claim type. Produce buyers and carriers both dispute aggressively |
+
+### 10.4 Month-End / Quarter-End Adjustments
+
+The last 5 business days of any month (and especially quarter) see volume spikes,
+carrier tender rejections, and increased exception rates as shippers rush to meet
+revenue recognition deadlines.
+
+| Parameter | Standard Setting | Month/Quarter-End Adjustment | Rationale |
+|-----------|-----------------|------------------------------|-----------|
+| Backup carrier readiness | Pre-identified for top 20 lanes | Pre-identified and confirmed available for top 50 lanes | Tender rejection rates spike 25–40% at month-end. Having confirmed backup capacity prevents scrambling |
+| Tender rejection response time | 2 hours to re-tender | 1 hour to re-tender | Every hour matters when the month is closing. Spot market tightens through the day |
+| Spot market premium approval | Manager approval > 20% over contract rate | Manager pre-approval up to 35% over contract rate | Speed of authorization matters more than cost optimization at month-end. Pre-authorize higher thresholds |
+| Double-brokering verification | Standard onboarding check | Enhanced verification for any new or infrequent carrier used at month-end: confirm MC#, confirm truck matches BOL, confirm driver identity | Double-brokering spikes when capacity is tight and brokers scramble to cover loads they've committed |
+| Exception reporting frequency | Daily summary | Twice-daily summary (midday and close of business) to operations leadership | Executives need real-time visibility into end-of-period exceptions that could affect revenue or delivery commitments |
+
+### 10.5 Adjustment Interaction Rules
+
+When multiple seasonal adjustments are active simultaneously (e.g., peak season +
+weather event in December):
+
+1. Apply the **more permissive** adjustment for carrier-facing parameters (response
+ SLAs, scorecard weighting). Do not stack — use the adjustment that grants the
+ carrier the most latitude.
+2. Apply the **more conservative** adjustment for customer-facing parameters
+ (notification thresholds, communication frequency). If peak says "Level 2+
+ proactive" and weather says "blanket communication to all affected," use the
+ blanket communication.
+3. Apply the **lower** eat-the-cost threshold (i.e., absorb more). Overlapping
+ stress periods mean higher APC and lower recovery probabilities.
+4. Internal escalation thresholds remain at the **tighter** of any applicable
+ adjustment. Overlapping stress events mean higher risk, not lower.
+5. Document which adjustments are active and communicate to the team. A triage
+ event during peak season with active weather is a different operating posture
+ than normal operations — everyone must be calibrated to the same adjusted
+ thresholds.
+
+---
+
+## Appendix A — Quick-Reference Decision Cards
+
+### Card 1: "Should I escalate this?"
+
+```
+IF severity ≥ 3 → YES, to manager
+IF severity ≥ 4 → YES, to director
+IF severity = 5 → YES, to VP
+IF carrier non-response > 4 hrs → YES, to carrier ops supervisor
+IF carrier non-response > 24 hrs → YES, to carrier account manager + your procurement
+IF customer has called about it → YES, to at least team lead
+IF it smells like fraud → YES, to compliance immediately
+```
+
+### Card 2: "Should I file this claim?"
+
+```
+IF value < $250 and portal available → FILE (automated, low effort)
+IF value < $500 and no portal → ABSORB unless it is a pattern
+IF value $500–$2,500 → RUN NRV CALC (see §9)
+IF value > $2,500 → FILE regardless
+IF this is the 3rd+ incident same carrier 90 days → FILE and flag for carrier review
+IF documentation is weak (no POD notation, no photos) → NEGOTIATE informally first, file only if carrier acknowledges liability
+```
+
+### Card 3: "Should I expedite a replacement?"
+
+```
+IF customer impact ≥ Level 4 → YES, authorize now, sort out cost later
+IF customer impact = Level 3 → CALCULATE: expedite cost vs. customer penalty + relationship damage
+IF customer impact ≤ Level 2 → STANDARD re-ship unless customer specifically requests
+IF product is perishable and original is salvageable → DO NOT re-ship; instead reroute or discount the original
+IF product is custom/irreplaceable → EXPEDITE the manufacturing queue, not just the shipping
+```
+
+### Card 4: "What do I do first when 10 exceptions land at once?"
+
+```
+1. ACTIVATE triage mode
+2. SCORE each exception using rapid triage (§8.3) — takes ~2 min per exception
+3. SORT by score descending
+4. ASSIGN: top 3 to senior analysts (1:1), next 4 to analysts (2:1), bottom 3 to batch queue
+5. COMMUNICATE: send blanket status to customer teams, single contact to carrier account managers
+6. UPDATE triage commander every 2 hours
+7. DEACTIVATE when active count < 5 and no Level 3+ remain
+```
+
+---
+
+## Appendix B — Acronyms and Glossary
+
+| Term | Definition |
+|------|-----------|
+| APC | Administrative Processing Cost — internal labor cost to handle an exception |
+| ASN | Advanced Shipping Notice — EDI 856 document notifying customer of incoming shipment |
+| BOL / BL | Bill of Lading — the shipping contract between shipper and carrier |
+| CFS | Container Freight Station — warehouse at a port where LCL cargo is consolidated/deconsolidated |
+| COGSA | Carriage of Goods by Sea Act — US statute governing ocean carrier liability |
+| DRC | Downstream Ripple Cost — secondary costs caused by the exception |
+| ELD | Electronic Logging Device — required device tracking driver hours of service |
+| ERC | Expedite / Re-Ship Cost — cost to recover from the exception via expedited shipment |
+| FCL | Full Container Load — ocean shipping where one shipper uses the entire container |
+| FMCSA | Federal Motor Carrier Safety Administration — US agency regulating trucking |
+| FTL | Full Truckload — one shipper, one truck, dock-to-dock |
+| HOS | Hours of Service — FMCSA regulations limiting driver driving/on-duty time |
+| IMC | Intermodal Marketing Company — broker of intermodal (rail+truck) services |
+| JIT | Just-In-Time — manufacturing/supply chain strategy with minimal inventory buffers |
+| LCL | Less than Container Load — ocean shipping where multiple shippers share a container |
+| LTL | Less than Truckload — shared carrier network with terminal cross-docking |
+| MC# | Motor Carrier number — FMCSA-issued operating authority identifier |
+| NFO | Next Flight Out — expedited air freight on the next available commercial flight |
+| NRV | Net Recovery Value — expected financial return from pursuing a claim |
+| NVOCC | Non-Vessel Operating Common Carrier — freight intermediary in ocean shipping |
+| OS&D | Over, Short & Damage — carrier department handling freight exceptions |
+| OTIF | On Time In Full — delivery performance metric |
+| PL | Product Loss — value of product damaged, lost, or shorted |
+| POD | Proof of Delivery — signed delivery receipt |
+| PRO# | Progressive Rotating Order number — carrier's shipment tracking number (LTL) |
+| QBR | Quarterly Business Review — periodic meeting between shipper and carrier/customer |
+| RDE | Relationship Damage Estimate — imputed cost of relationship harm from exception |
+| SDR | Special Drawing Rights — IMF currency unit used in international transport liability limits |
+| SIR | Self-Insured Retention — amount the shipper pays before insurance coverage applies |
+| SL&C | Shipper Load & Count — BOL notation indicating carrier did not verify the load |
+| STB | Surface Transportation Board — US agency with jurisdiction over rail and some intermodal disputes |
+| TEC | Total Exception Cost — comprehensive cost of an exception including all components |
+| TMS | Transportation Management System — software for managing freight operations |
+| WMS | Warehouse Management System — software for managing warehouse operations |
diff --git a/web-app/public/skills/logistics-exception-management/references/edge-cases.md b/web-app/public/skills/logistics-exception-management/references/edge-cases.md
new file mode 100644
index 00000000..5c226792
--- /dev/null
+++ b/web-app/public/skills/logistics-exception-management/references/edge-cases.md
@@ -0,0 +1,734 @@
+# Logistics Exception Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous exceptions that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced exception management professionals from everyone else. Each one involves competing claims, ambiguous liability, time pressure, and real financial exposure. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When an exception doesn't fit a clean category — when liability is genuinely unclear, when multiple parties have plausible claims, or when the financial exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; they exist because these are the cases that end up in arbitration or litigation.
+
+---
+
+### Edge Case 1: Temperature-Controlled Pharma Shipment — Reefer Failure with Disputed Loading Temperature
+
+**Situation:**
+A regional pharmaceutical distributor ships 14 pallets of insulin (Humalog and Novolog pens, wholesale value ~$2.1M) from a cold storage facility in Memphis to a hospital network distribution center in Atlanta. The shipment requires continuous 2–8°C (36–46°F) storage per USP <1079> guidelines. The reefer unit is a 2021 Carrier Transicold X4 7500 on a 53-foot trailer pulled by a contract carrier running under their own authority.
+
+Upon arrival 18 hours later, the receiving pharmacist's temperature probe reads 14°C (57°F) at the pallet surface. The TempTale 4 data logger packed inside the shipment shows the temperature climbed above 8°C approximately 6 hours into transit and continued rising. The carrier's in-cab reefer display download shows the setpoint was 4°C and the unit was in "continuous" mode, not "cycle-spool." The carrier produces a pre-trip reefer inspection report showing the unit pulled down to 2°C before loading and provides a lumper receipt from origin showing product was loaded at 3°C.
+
+The carrier's position: the product was loaded warm or the facility door was open too long during loading, and the reefer couldn't overcome the heat load. The shipper's position: the reefer compressor failed in transit and the carrier is liable. Both sides have documentation supporting their claim. The hospital network needs insulin within 48 hours or faces patient care disruptions.
+
+**Why It's Tricky:**
+Temperature excursion disputes are among the hardest to adjudicate because both the shipper and carrier can be partially right. A reefer unit in continuous mode should maintain setpoint on a properly pre-cooled load, but if the trailer was pre-cooled empty (no thermal mass) and then loaded with product at the upper end of range on a 95°F day in Memphis with the dock door cycling open, the unit may genuinely struggle. The critical question isn't the reefer setpoint — it's the return air temperature trend in the first 90 minutes after door closure.
+
+Most non-experts focus on the arrival temperature. Experts focus on the rate of temperature change and exactly when the deviation started. If the reefer data shows return air climbing steadily from minute one, the load was likely warm at origin. If return air held for 4+ hours then spiked, the compressor or refrigerant failed in transit.
+
+**Common Mistake:**
+Filing a blanket cargo claim against the carrier for $2.1M without first analyzing the reefer download data in detail. The carrier will deny the claim, point to their pre-trip and loading receipts, and the dispute enters a 6-month arbitration cycle. Meanwhile, the product sits in a quarantine hold and ultimately gets destroyed, the hospital network scrambles for supply, and the shipper-carrier relationship is damaged.
+
+The second common mistake: assuming the entire shipment is a total loss. Insulin pens that experienced a brief, moderate excursion may still be viable depending on manufacturer stability data and the specific excursion profile. A blanket destruction order without consulting the manufacturer's excursion guidance wastes recoverable product.
+
+**Expert Approach:**
+1. Immediately quarantine the shipment at the receiving facility — do not reject it outright and do not release it to inventory. Rejection creates a disposal liability problem. Quarantine preserves options.
+2. Download and preserve three data sets: (a) the TempTale or Ryan data logger from inside the shipment, (b) the reefer unit's microprocessor download (insist on the full download, not the driver's summary printout), and (c) the facility's dock door and ambient temperature logs from loading.
+3. Overlay the three data streams on a single timeline. Identify the exact minute the temperature began deviating and calculate the rate of change (°C per hour).
+4. If the deviation started within the first 90 minutes and the rate is gradual (0.5–1°C/hour), the load was likely under-cooled at origin or absorbed heat during loading. The shipper bears primary liability.
+5. If the deviation started 3+ hours into transit with a sharp rate change (2+°C/hour), the reefer experienced a mechanical failure. The carrier bears primary liability.
+6. Contact the insulin manufacturers' medical affairs departments with the exact excursion profile (time above 8°C, peak temperature reached). Request written guidance on product viability. Humalog pens that stayed below 15°C for under 14 days may still be usable per Lilly's excursion data.
+7. For product deemed viable, release from quarantine with full documentation. For product deemed non-viable, document the destruction with lot numbers, quantities, and witnessed disposal.
+8. File the claim against the liable party with the data overlay as the primary exhibit. If liability is shared, negotiate a split based on the data — typically 60/40 or 70/30.
+9. Separately and in parallel: source replacement insulin from the distributor's secondary allocation or from the manufacturer's emergency supply program. The hospital network cannot wait for claim resolution.
+
+**Key Indicators:**
+- Return air vs. supply air divergence in the first 2 hours is the single most diagnostic data point
+- A reefer that was pre-cooled empty to 2°C but shows supply air of 4°C within 30 minutes of door closure likely had an undersized unit or a failing compressor
+- Look for "defrost cycle" entries in the reefer log — a unit running excessive defrost cycles is masking a frost buildup problem that indicates a refrigerant leak
+- Check whether the reefer was in "continuous" or "start-stop" (cycle-spool) mode — pharma loads must be continuous; if it was set to cycle-spool, the carrier is immediately at fault regardless of loading temperature
+- A pre-trip that shows 2°C pulldown in under 20 minutes on a 53-foot trailer in summer is suspicious — that's an empty trailer with no thermal mass, meaning the carrier pulled the trailer to the shipper without adequate pre-cool time
+
+**Documentation Required:**
+- TempTale/Ryan recorder raw data file (CSV export, not just the PDF summary)
+- Reefer microprocessor full download (not the 3-line driver printout; the full event log with alarm history, defrost cycles, and door open events)
+- Origin facility dock door logs and ambient temperature at time of loading
+- Bill of lading with temperature requirement notation
+- Shipper's loading SOP and any deviation from it
+- Photographs of data logger placement within the load
+- Manufacturer's written excursion guidance for the specific product lots
+- Witnessed product destruction records with lot numbers if applicable
+
+**Resolution Timeline:**
+- Hours 0–4: Quarantine, data preservation, and initial data overlay analysis
+- Hours 4–12: Manufacturer consultation on product viability
+- Hours 12–48: Replacement sourcing and initial claim filing
+- Days 3–14: Detailed claim documentation assembly with data overlay exhibit
+- Days 14–45: Carrier/shipper response and negotiation
+- Days 45–120: Arbitration if negotiation fails (typical for claims over $500K)
+
+---
+
+### Edge Case 2: Consignee Refuses Delivery Citing Damage, but Damage Occurred at Consignee's Dock
+
+**Situation:**
+A furniture manufacturer ships 8 pallets of assembled high-end office chairs (Herman Miller Aeron, wholesale value ~$38,400) via LTL from their Grand Rapids facility to a commercial interior design firm in Chicago. The shipment arrives at the consignee's urban location — a converted warehouse with a narrow dock, no dock leveler, and a single dock door accessed via an alley.
+
+The driver backs in and the consignee's receiving crew begins unloading with a stand-up forklift. During unloading, the forklift operator catches a pallet on the trailer's rear door track, tipping it. Three cartons fall, and multiple chairs sustain visible frame damage. The consignee's receiving manager immediately refuses the entire shipment, marks the BOL "DAMAGED — REFUSED," and instructs the driver to take it all back.
+
+The driver, who was in the cab during unloading, did not witness the incident. He signs the BOL with the consignee's damage notation and departs with the full load. The shipper receives a refused-shipment notification and a damage claim from the consignee for the full $38,400.
+
+**Why It's Tricky:**
+Once "DAMAGED — REFUSED" is on the BOL signed by the driver, the shipper is in a difficult position. The consignee controls the narrative because they were the ones who noted damage. The carrier will deny the claim because the driver will state the freight was intact when he opened the doors. But the driver wasn't watching unloading, so he can't affirmatively say when damage occurred. The consignee has no incentive to admit their forklift operator caused the damage — they want replacement product, and it's easier to blame transit damage.
+
+The fundamental issue: damage occurring during unloading at the consignee's facility is the consignee's liability, not the carrier's or shipper's. But proving it requires evidence that is very hard to obtain after the fact.
+
+**Common Mistake:**
+Accepting the consignee's damage claim at face value and filing against the carrier. The carrier denies it, the shipper eats the cost, and the consignee gets free replacement product. The second common mistake: refusing to send replacement product while the dispute is investigated, damaging the commercial relationship with the consignee (who is the customer).
+
+**Expert Approach:**
+1. Before anything else, call the driver directly (or through the carrier's dispatch). Ask specifically: "Did you observe unloading? Were you in the cab or on the dock? Did you inspect the freight before signing the damage notation?" Get this statement within 24 hours while memory is fresh.
+2. Request the carrier pull any dashcam or rear-facing camera footage from the tractor. Many modern fleets have cameras that capture dock activity. Even if the angle is poor, it establishes the timeline.
+3. Ask the consignee for their facility's security camera footage of the dock area. Frame this as "helping us file the claim properly." If they refuse or claim no cameras, that's a data point.
+4. Examine the damage type. Chairs that fell off a forklift-tipped pallet will have impact damage on the frame — dents, bends, cracked bases — concentrated on one side and consistent with a fall from 4–5 feet. Transit damage from shifting in a trailer presents differently: scuffing, compression, carton crushing across the top of the pallet from stacking, and damage distributed across multiple faces of the carton.
+5. Check the origin loading photos. If the shipper photographs outbound loads (they should), compare the load configuration at origin to the described damage pattern. If the pallets were loaded floor-stacked with no double-stacking, top-of-pallet compression damage is impossible from transit.
+6. File a "damage under investigation" notice with the carrier within 9 months (Carmack Amendment window for concealed damage, though this is not concealed). Keep the claim open but do not assert a specific dollar amount yet.
+7. Send the consignee replacement product for the damaged units only (not the entire shipment — only the 3 cartons that were damaged, not all 8 pallets). Ship the replacements on the shipper's account, but document that the original undamaged product must be received as-is.
+8. If evidence supports consignee-caused damage, present findings to the consignee. The goal is not to litigate — it's to establish the facts and negotiate. Typically the consignee accepts liability for the damaged units, the shipper absorbs the freight cost of the return and reship, and the relationship survives.
+
+**Key Indicators:**
+- Driver was in the cab, not on the dock — critical detail that the carrier will try to gloss over
+- Damage concentrated on one pallet or one side of a pallet strongly suggests a handling incident, not transit movement
+- Consignee's dock conditions (no leveler, narrow alley, stand-up forklift for palletized furniture) are inherently risky — experienced shippers know these facilities generate more damage claims
+- If the consignee refused the entire shipment but only 3 cartons were visibly damaged, the refusal was strategic, not operational. Legitimate damage refusals are partial unless the entire shipment is compromised.
+- The driver signing the damage notation without adding "DAMAGE NOT OBSERVED IN TRANSIT" or "DRIVER NOT PRESENT DURING UNLOADING" is a documentation failure, but it is not an admission of carrier liability
+
+**Documentation Required:**
+- Signed BOL with damage notations (photograph both sides)
+- Driver's written statement on their location during unloading (within 24 hours)
+- Dashcam or rear-camera footage from the tractor if available
+- Consignee's dock/security camera footage (request in writing)
+- Origin loading photographs showing load configuration and product condition
+- Close-up photographs of actual damage on the product, taken at the consignee's facility
+- Diagram or description of the consignee's dock layout, including dock type, leveler presence, and equipment used for unloading
+- Replacement shipment BOL and delivery confirmation
+
+**Resolution Timeline:**
+- Hours 0–4: Driver statement collection and camera footage requests
+- Hours 4–24: Damage pattern analysis and origin photo comparison
+- Days 1–3: Replacement product shipped for confirmed damaged units
+- Days 3–10: Evidence assembly and liability determination
+- Days 10–30: Consignee negotiation on damaged unit liability
+- Days 30–60: Carrier claim closure (if carrier is cleared) or continued pursuit
+
+---
+
+### Edge Case 3: High-Value Shipment with No Scan Updates for 72+ Hours — "Lost" vs. "Scan Gap"
+
+**Situation:**
+A medical device manufacturer ships a single pallet of surgical navigation systems (Medtronic StealthStation components, declared value $287,000) from their distribution center in Jacksonville, FL to a hospital in Portland, OR. The shipment moves via a national LTL carrier with guaranteed 5-day service.
+
+The shipment scans at the origin terminal in Jacksonville on Monday at 14:22. It scans at the carrier's hub in Nashville on Tuesday at 03:17. Then — silence. No scan events for 72 hours. The shipper's logistics coordinator checks the carrier's tracking portal Wednesday, Thursday, and Friday morning. Nothing. The guaranteed delivery date is Friday by 17:00. The hospital has a surgery suite installation scheduled for the following Monday.
+
+The shipper calls the carrier's customer service line Friday morning. After 40 minutes on hold, the representative says the shipment is "in transit" and to "check back Monday." The shipper's coordinator escalates to their carrier sales rep, who promises to "get eyes on it." By Friday at 15:00, still no update.
+
+**Why It's Tricky:**
+A 72-hour scan gap on a national LTL carrier does not necessarily mean the shipment is lost. LTL carriers have known scan compliance problems at certain terminals, particularly mid-network hubs where freight is cross-docked between linehaul trailers. A pallet can physically move through 2–3 terminals without generating a scan if handheld devices aren't used during cross-dock operations or if the PRO label is damaged or facing inward on the pallet.
+
+But a 72-hour gap on a $287K shipment could also mean it was misrouted, left behind on a trailer that went to the wrong terminal, shorted to another shipment's delivery, or actually lost or stolen. The challenge is distinguishing between a scan gap (the freight is fine, the technology failed) and a genuine loss — while the clock is ticking on a surgery installation.
+
+**Common Mistake:**
+Waiting until the guaranteed delivery date passes to escalate. By Friday at 17:00, if the shipment is genuinely lost, you've wasted 72 hours of recovery time. The second common mistake: filing a lost shipment claim immediately, which triggers a formal process that takes 30–120 days to resolve. That doesn't help the hospital that needs equipment Monday. The third mistake: assuming the carrier's customer service representative actually has information — front-line CSRs at national LTL carriers typically see the same tracking portal the shipper does.
+
+**Expert Approach:**
+1. At the 48-hour mark (not the 72-hour mark), escalate through two parallel channels: (a) the carrier's sales representative, who has internal access to trailer manifests and terminal operations, and (b) the carrier's claims/OS&D (over, short, and damaged) department at the last known terminal (Nashville).
+2. Ask the sales rep for three specific things: (a) the trailer number the shipment was loaded on at Nashville, (b) the manifest for that trailer showing destination terminal, and (c) confirmation that the trailer has arrived at its destination terminal. This is not information CSRs have, but operations and sales teams can access it.
+3. If the trailer arrived at the destination terminal but the shipment didn't scan, it's almost certainly a scan gap. Ask the destination terminal to physically locate the freight on the dock or in the outbound staging area. Provide the PRO number, pallet dimensions, and weight — enough for someone to walk the dock.
+4. If the trailer hasn't arrived at the destination terminal, ask where the trailer currently is. Trailers are GPS-tracked. If the trailer is sitting at an intermediate terminal for 48+ hours, the freight may have been left on during unloading (a "buried" shipment that didn't get pulled).
+5. In parallel, start sourcing a backup unit from the manufacturer. For a $287K medical device, the manufacturer will have a loaner program or emergency stock. Contact Medtronic's field service team directly — they are motivated to keep the surgery installation on schedule because their technician is already booked.
+6. If the shipment is confirmed lost (not just scan-gapped) by Friday afternoon, immediately file a preliminary claim with the carrier. Do not wait. Simultaneously arrange emergency air freight for the replacement unit — the cost ($3,000–$8,000 for expedited air from the nearest depot with stock) is recoverable as part of the claim.
+7. If the shipment reappears (as scan-gap shipments often do), arrange Saturday or Sunday delivery. Many LTL carriers will do weekend delivery for an additional fee on service-failure shipments — negotiate this fee away since they missed the guarantee.
+
+**Key Indicators:**
+- A scan at an intermediate hub followed by silence usually means the freight is physically at the next terminal but didn't scan during cross-dock. Genuine theft or loss rarely happens mid-network at a carrier's own facility.
+- If the carrier's CSR says "in transit" 72 hours after the last scan, they're reading the same portal you are. Escalate immediately.
+- Check whether the PRO label was applied to shrink wrap or to the pallet itself. Shrink wrap labels get torn off during handling. This is the single most common cause of scan gaps.
+- A single high-value pallet is more vulnerable to being "lost" on a dock than a multi-pallet shipment. It's physically small enough to be blocked behind other freight or pushed into a corner.
+- If the carrier's Nashville terminal had a known service disruption (weather, labor action, system outage) in the 72-hour window, a scan gap is almost certain. Check the carrier's service alerts page.
+
+**Documentation Required:**
+- Complete tracking history with all scan events and timestamps
+- Original BOL with declared value, PRO number, piece count, weight, and dimensions
+- Screenshot of carrier tracking portal showing the gap (timestamped)
+- Written correspondence with carrier (sales rep, CSR, OS&D) with dates and names
+- Trailer number and manifest from the last known terminal
+- Carrier's guaranteed service commitment documentation
+- Replacement sourcing records and expedited shipping costs (if applicable)
+- Service failure claim documentation per the carrier's tariff (separate from cargo loss claim)
+
+**Resolution Timeline:**
+- Hour 48: Escalation to sales rep and OS&D department
+- Hours 48–56: Trailer tracking and physical dock search at destination terminal
+- Hours 56–72: Backup unit sourcing initiated
+- Hour 72 (if still missing): Preliminary lost cargo claim filed, emergency replacement shipped
+- Days 3–7: Carrier completes internal search; most "lost" LTL shipments are found within 5 business days
+- Days 7–30: Formal claim resolution if shipment is confirmed lost
+- Days 30–120: Full claim payment (national LTL carriers typically settle claims in 60–90 days for shipments with declared value)
+
+---
+
+### Edge Case 4: Cross-Border Shipment Held at Customs — Carrier Documentation Error vs. Shipper Error
+
+**Situation:**
+A Texas-based auto parts manufacturer ships a full truckload of aftermarket catalytic converters (480 units, commercial value $312,000) from their Laredo warehouse to an automotive distributor in Monterrey, Mexico. The shipment moves via a U.S. carrier to the Laredo border crossing, where it is transferred to a Mexican carrier for final delivery under a cross-dock arrangement.
+
+Mexican customs (Aduana) places a hold on the shipment at the Nuevo Laredo crossing. The customs broker reports two issues: (1) the commercial invoice lists the HS tariff code as 8421.39 (filtering machinery), but catalytic converters should be classified under 8421.39.01.01 (specific Mexican fraction for catalytic converters) or potentially 7115.90 (articles of precious metal, because catalytic converters contain platinum group metals), and (2) the pedimento (Mexican customs entry) lists 480 pieces but the physical count during inspection is 482 — two additional units were loaded that are not on any documentation.
+
+The carrier blames the shipper for the wrong HS code and the extra pieces. The shipper says the customs broker (hired by the carrier's Mexican partner) selected the HS code, and their pick ticket clearly shows 480 units. The Mexican carrier is charging $850/day in detention. The customs broker is quoting $4,500 for a "rectification" of the pedimento. The consignee needs the parts by Thursday for a production line changeover.
+
+**Why It's Tricky:**
+Cross-border shipments involving tariff classification disputes and quantity discrepancies touch three separate legal jurisdictions (U.S. export, Mexican import, and the bilateral trade agreement). The HS code issue is genuinely ambiguous — catalytic converters are classified differently depending on whether you're classifying the filtration function or the precious metal content, and the correct Mexican fraction depends on end use. The two extra pieces could be a loading error, a picking error, or remnant inventory from a previous load left in the trailer.
+
+Every day the shipment sits at the border, detention charges accrue, the consignee's production line inches closer to shutdown, and the risk of a formal Mexican customs investigation (which can result in seizure) increases. The parties involved — shipper, U.S. carrier, Mexican carrier, customs broker, consignee — all have conflicting incentives.
+
+**Common Mistake:**
+Letting the customs broker "handle it" without oversight. Border customs brokers facing a hold often choose the fastest resolution, not the cheapest or most legally correct one. They may reclassify under a higher-duty HS code to avoid scrutiny, costing the consignee thousands in excess duties that become very difficult to recover. They may also instruct the shipper to create a supplemental invoice for the 2 extra pieces at an arbitrary value, which creates a paper trail that doesn't match reality and can trigger a post-entry audit.
+
+The second mistake: panicking about the quantity discrepancy and assuming it's a smuggling allegation. Two extra catalytic converters on a 480-unit load is a 0.4% overage. Mexican customs sees this routinely and it's correctable — but only if handled with the right paperwork and the right broker.
+
+**Expert Approach:**
+1. Separate the two issues immediately. The HS code classification and the quantity discrepancy are different problems with different resolution paths. Do not let the broker bundle them into a single "rectification."
+2. For the HS code: engage a licensed Mexican customs classification specialist (not the same broker who filed the original pedimento). Catalytic converters for automotive aftermarket use are correctly classified under the Mexican tariff fraction 8421.39.01.01 with USMCA preferential treatment if the origin qualifies. The precious metals classification (7115.90) applies only to scrap or recovery operations. Get a binding ruling reference from SAT (Mexico's tax authority) if the broker disputes this.
+3. For the quantity discrepancy: determine the actual source of the two extra pieces. Pull the shipper's warehouse pick ticket, the loading tally sheet (if one exists), and check the trailer's seal number against the BOL. If the seal was intact at the border, the extra pieces were loaded at origin. Check whether the shipper's inventory system shows a corresponding shortage of 2 units. If it does, it's a simple pick/load error. If it doesn't, the units may have been left in the trailer from a previous load — check the carrier's prior trailer use log.
+4. File a "rectificación de pedimento" through the classification specialist for both the HS code correction and the quantity amendment. The amendment for the 2 extra units requires a supplemental commercial invoice from the shipper at the same per-unit price as the original 480.
+5. While the rectification is processing (typically 1–3 business days), negotiate the detention charges. The Mexican carrier's $850/day is negotiable because the hold is not their fault or the shipper's alone. The standard resolution is to split detention costs between the shipper (for the quantity error) and the customs broker (for the classification error), with the carrier waiving 1–2 days as a relationship concession.
+6. Document the entire incident for USMCA compliance records. An HS code correction on a $312K shipment of controlled automotive parts will flag in SAT's risk system, and the next shipment through Nuevo Laredo will get a more thorough inspection. Prepare for that.
+
+**Key Indicators:**
+- A customs hold that cites both classification and quantity issues is more serious than either alone — it suggests the shipment was flagged for manual inspection, not a random document review
+- Catalytic converter shipments to Mexico receive extra scrutiny because of environmental regulations (NOM standards) and precious metal content reporting requirements
+- If the customs broker immediately quotes a fee for "rectification" without explaining the legal basis, they're charging a facilitation fee, not a legitimate service cost. Get a second quote.
+- An intact seal with a quantity overage points to origin loading error. A broken or missing seal with a quantity overage is a much more serious situation suggesting possible tampering.
+- Check whether the shipper holds a C-TPAT certification — if so, the quantity error could jeopardize their trusted trader status, and the resolution needs to include a corrective action report
+
+**Documentation Required:**
+- Original commercial invoice, packing list, and BOL (all three must be reconciled)
+- Mexican pedimento (customs entry) showing the hold reason and original classification
+- Shipper's warehouse pick ticket and loading tally for the exact shipment
+- Trailer seal number verification (BOL seal number vs. seal number at inspection)
+- Carrier's prior trailer use log (to rule out remnant freight)
+- Classification specialist's written opinion on correct HS code with legal citations
+- Supplemental commercial invoice for the 2 additional units
+- Rectified pedimento with Aduana stamp
+- Detention invoices from the Mexican carrier with negotiated amounts
+- USMCA certificate of origin (if claiming preferential treatment)
+- Corrective action report if shipper is C-TPAT certified
+
+**Resolution Timeline:**
+- Hours 0–4: Issue separation, classification specialist engaged, quantity investigation started
+- Hours 4–24: Source of quantity discrepancy determined, supplemental invoice prepared
+- Days 1–3: Rectificación de pedimento filed and processed
+- Days 3–5: Shipment released from customs, delivered to consignee
+- Days 5–15: Detention charge negotiation and settlement
+- Days 15–45: Post-entry compliance documentation filed, C-TPAT corrective action if applicable
+
+---
+
+### Edge Case 5: Multiple Partial Deliveries Against Same BOL — Tracking Shortage vs. Overage
+
+**Situation:**
+A building materials distributor ships a full truckload of mixed SKUs — 12 pallets of ceramic floor tile (7,200 sq ft), 6 pallets of grout (180 bags), and 4 pallets of backer board (240 sheets) — from their Dallas distribution center to a commercial construction site in Houston. The BOL lists 22 pallets, 38,400 lbs, as a single shipment under one PRO number.
+
+The Houston job site cannot receive a full truckload at once — the staging area is too small and the GC (general contractor) will only accept what the tile crew can install that week. The shipper and consignee agreed to split delivery across three drops: 8 pallets Monday, 8 pallets Wednesday, 4 pallets Friday. The carrier is making partial deliveries from their Houston terminal, breaking the load and redelivering across the week.
+
+After the third delivery Friday, the GC's site superintendent counts what was received across all three deliveries and reports: 11 pallets of tile (short 1), 7 pallets of grout (over 1), and 4 pallets of backer board (correct). The consignee files a shortage claim for 1 pallet of tile (~$3,600) and an overage notification for 1 pallet of grout (~$420).
+
+The carrier says all 22 pallets were delivered across the three drops. The delivery receipts from Monday and Wednesday were signed by the site's day laborer (not the superintendent), and the Friday receipt was signed by the superintendent. None of the three delivery receipts detail pallet counts by SKU — they just say "8 pallets," "8 pallets," and "4 pallets" respectively.
+
+**Why It's Tricky:**
+Partial deliveries against a single BOL create a reconciliation nightmare. The original BOL describes the total load. Each partial delivery should have a delivery receipt referencing the original BOL with a detailed pallet-by-SKU breakdown, but in practice, drivers hand over whatever is on the truck and the receiver signs for a pallet count without verifying SKU-level detail.
+
+The likely scenario: during the break-bulk at the carrier's Houston terminal, a tile pallet was mixed up with a grout pallet. The carrier delivered 22 pallets total (correct), but the SKU mix within those 22 was wrong. This is not a shortage or an overage — it's a mis-delivery. But because the delivery receipts don't have SKU-level detail, no one can prove which delivery had the wrong mix.
+
+The job site may also be contributing to the confusion. Construction sites are chaotic. Product gets moved, other subcontractors' materials get mixed in, and the laborer who signed Monday's receipt may not have segregated the delivery from other tile already on site.
+
+**Common Mistake:**
+Filing a standard shortage claim for the missing tile pallet. The carrier will point to the signed delivery receipts showing 22 pallets delivered and deny the claim. The consignee ends up short tile for the install, orders a rush replacement, and eats the cost. Meanwhile, the extra grout pallet either gets absorbed into site inventory (costing the distributor) or sits unclaimed.
+
+The deeper mistake: not recognizing that this is a SKU-level accuracy problem, not a piece-count problem. Standard shortage claim procedures don't address mis-delivery within a correct total count.
+
+**Expert Approach:**
+1. Reconstruct the three deliveries at the SKU level. Start with what's verifiable: the Friday delivery was received by the superintendent. Ask them to confirm exactly what was on those 4 pallets by SKU. If they can confirm 4 pallets of backer board, that's clean.
+2. Work backward from Friday. If all backer board was on the Friday delivery, then Monday and Wednesday delivered a combined 12 pallets of tile and 6 pallets of grout — but we know the consignee received 11 tile and 7 grout. One tile pallet was swapped for a grout pallet.
+3. Check the carrier's Houston terminal break-bulk records. When the carrier broke the full truckload into three partial deliveries, they should have a terminal work order or fork driver's load sheet showing which pallets went on which delivery truck. If these records exist (and at major LTL/TL carriers, they often do), they'll show the misload.
+4. The resolution is a swap, not a claim. The consignee has 1 extra grout pallet that belongs to the distributor. The distributor owes 1 tile pallet to the consignee. Arrange a single delivery: bring 1 tile pallet, pick up 1 grout pallet. The carrier should absorb this cost as a service failure if the terminal's break-bulk records show the misload.
+5. For future partial-delivery shipments to this consignee (and any similar job site), require SKU-level detail on each delivery receipt. Create a standardized partial delivery form that references the master BOL and lists, per delivery: pallet count by SKU, total pieces by SKU, and a running total against the master BOL. Have the receiver verify and sign at the SKU level.
+6. If the carrier denies the misload and the consignee cannot wait for resolution, ship the replacement tile pallet immediately and pursue the carrier for the freight cost and the unrecovered grout pallet value.
+
+**Key Indicators:**
+- Delivery receipts signed by day laborers without SKU verification are essentially worthless for claims purposes — they prove delivery happened but not what was delivered
+- A 1-for-1 swap (1 pallet short on SKU A, 1 pallet over on SKU B, total count correct) is almost always a terminal misload, not a transit loss
+- Construction sites with multiple subcontractors and multiple material suppliers are high-risk for inventory confusion — materials from different vendors get commingled
+- If the grout and tile pallets are similar in size and wrapped in similar shrink wrap, the terminal dock worker likely couldn't distinguish them without checking labels
+- Check whether the pallets had color-coded labels or SKU stickers visible through the shrink wrap — if not, this is partly a packaging/labeling failure at origin
+
+**Documentation Required:**
+- Original BOL with complete SKU-level pallet breakdown (22 pallets by type)
+- All three delivery receipts with signatures and dates
+- Site superintendent's SKU-level inventory reconciliation after final delivery
+- Carrier's terminal break-bulk work order or fork driver load sheet (request in writing)
+- Photographs of the extra grout pallet (label, lot number, condition)
+- Replacement tile pallet shipment documentation
+- Return/swap documentation for the extra grout pallet
+
+**Resolution Timeline:**
+- Hours 0–8: SKU-level reconciliation at the job site
+- Hours 8–24: Carrier terminal records requested and reviewed
+- Days 1–3: Swap arranged — tile pallet delivered, grout pallet recovered
+- Days 3–7: Carrier cost allocation determined (service failure or shared)
+- Days 7–14: Partial delivery SOP updated for future shipments to this consignee
+
+---
+
+### Edge Case 6: Dual-Driver Team Swap with Missing Driver Signature on POD
+
+**Situation:**
+A contract carrier runs a team-driver operation to meet a time-critical delivery for an electronics retailer. The shipment is 18 pallets of consumer electronics (gaming consoles, wholesale ~$194,000) moving from a distribution center in Ontario, CA to a regional fulfillment center in Edison, NJ — approximately 2,700 miles with a 48-hour delivery commitment.
+
+Driver A departs Ontario and drives the first 11-hour shift. At the team swap point in Amarillo, TX (approximately mile 1,200), Driver B takes the wheel. Driver A had the original BOL packet with the paper POD (proof of delivery) form. During the swap, the BOL packet was left in the sleeper berth rather than passed to Driver B's clipboard.
+
+Driver B completes the haul to Edison and delivers the shipment. The receiving clerk at the fulfillment center signs the delivery receipt, but the Driver B signature line on the carrier's POD copy is blank — Driver B didn't have the BOL packet and instead used a generic delivery receipt from the cab's supply. The consignee's copy of the POD has the receiver's signature but no driver signature. The carrier's copy has Driver A's signature at origin and a blank at destination.
+
+Three weeks later, the retailer files a shortage claim for 2 pallets ($21,600) stating the delivery was short. The carrier has no signed POD from their driver at delivery confirming piece count.
+
+**Why It's Tricky:**
+A POD without the driver's signature at delivery is a significant evidentiary gap. The carrier cannot prove their driver confirmed the delivery was complete. The consignee's receiving clerk signed for "18 pallets" on their internal receipt, but the carrier doesn't have a copy of that document. The carrier's own POD shows 18 pallets loaded at origin (Driver A's signature) but has no delivery confirmation.
+
+Team-driver operations are notorious for documentation handoff failures. The swap happens at a truck stop at 2 AM, both drivers are focused on the HOS (hours of service) clock, and paperwork transfer is an afterthought. Carriers know this is a vulnerability but struggle to enforce procedures across hundreds of team operations.
+
+The 3-week gap between delivery and claim filing adds suspicion. If 2 pallets of gaming consoles were missing at delivery, the fulfillment center's receiving process should have caught it immediately — not three weeks later during an inventory cycle count.
+
+**Common Mistake:**
+The carrier, lacking a signed POD, immediately concedes the claim to avoid litigation. This sets a precedent that any shortage claim against a team-driver shipment without a perfect POD is automatically paid. The actual cost isn't just $21,600 — it's the signal to this retailer (and their claims department) that POD gaps equal easy money.
+
+Alternatively, the carrier denies the claim outright, the retailer escalates, and the carrier loses the account.
+
+**Expert Approach:**
+1. Obtain the consignee's internal receiving documentation. The fulfillment center will have their own receiving log, WMS (warehouse management system) receipt record, and the delivery receipt their clerk signed. Formally request these through the retailer's freight claims department. The consignee's WMS receipt record will show exactly how many pallets were scanned into inventory at the time of delivery.
+2. Check whether the consignee's facility has dock cameras. Most fulfillment centers of this size do. Request footage from the delivery date showing the unloading process. Counting pallets on a camera is straightforward.
+3. Pull Driver B's ELD (electronic logging device) data for the delivery stop. The ELD will show arrival time, departure time, and duration at the delivery location. A full 18-pallet unload takes 25–40 minutes. If the ELD shows a 15-minute stop, the delivery may indeed have been short (or the driver dropped the trailer, but that changes the scenario).
+4. Check the generic delivery receipt Driver B used. Even without the formal POD, if Driver B got any signature on any piece of paper, it has evidentiary value. Contact Driver B directly.
+5. Investigate the 3-week claim gap. Ask the retailer when exactly the shortage was discovered. If it was during an inventory cycle count, the shortage could have occurred anywhere in the fulfillment center's operations — theft, mis-pick, damage disposal without record — and not during delivery. A 3-week-old shortage claim without a same-day exception report at receiving is weak on its face.
+6. If the evidence shows full delivery (WMS receipt of 18, camera footage of 18 pallets, ELD showing full unload duration), deny the claim with documentation. If the evidence is inconclusive, negotiate a partial settlement — typically 50% of the claimed amount — with a corrective action plan for the team-driver POD process.
+
+**Key Indicators:**
+- A shortage claim filed weeks after delivery, absent a same-day exception notation on the delivery receipt, suggests the shortage occurred in the consignee's facility, not at delivery
+- Generic delivery receipts from the cab are still legally valid documents if signed by the receiver — they're just harder to track and retain
+- ELD stop duration is an underused tool for verifying delivery completeness. Full unloads take measurable time.
+- If the consignee's WMS shows 18 pallets received into inventory, the shortage claim is baseless regardless of the POD issue
+- Team swaps at truck stops between midnight and 5 AM have the highest documentation failure rate
+
+**Documentation Required:**
+- Carrier's POD (showing Driver A signature at origin, blank at destination)
+- Generic delivery receipt from Driver B (if recoverable)
+- Consignee's internal receiving log and WMS receipt record
+- Consignee's dock camera footage from the delivery date
+- Driver B's ELD data showing arrival, departure, and stop duration at delivery
+- Retailer's shortage claim filing with discovery date and method
+- Driver B's written statement regarding the delivery (pallet count, who received, any anomalies)
+
+**Resolution Timeline:**
+- Days 0–3: Consignee documentation request and Driver B statement
+- Days 3–7: ELD data pull and camera footage review
+- Days 7–14: Evidence analysis and liability determination
+- Days 14–30: Claim response to the retailer with supporting documentation
+- Days 30–60: Settlement negotiation if evidence is inconclusive
+
+---
+
+### Edge Case 7: Intermodal Container with Concealed Damage Discovered Days After Delivery
+
+**Situation:**
+A consumer goods importer receives a 40-foot intermodal container of packaged household cleaning products (cases of liquid detergent, surface cleaners, and aerosol sprays — approximately 1,800 cases, landed cost ~$67,000) at their warehouse in Memphis. The container moved ocean from Shenzhen to the Port of Long Beach, then intermodal rail from Long Beach to Memphis, then drayage from the Memphis rail ramp to the importer's warehouse.
+
+The container is grounded at the warehouse on Tuesday. The warehouse crew unloads it on Wednesday. Everything looks normal — the container seal was intact, no obvious external damage to the container, and the first 600 cases pulled from the doors look fine. But as the crew works deeper into the container (beyond the halfway point), they find approximately 200 cases of aerosol cans that are crushed and leaking. The cases were stacked in the rear of the container (loaded first in Shenzhen), and the damage pattern suggests the load shifted during transit, causing the top-stacked cases to collapse onto the aerosol pallets.
+
+The importer files a concealed damage claim. The problem: the container moved through four custody handoffs — the Chinese shipper's loading crew, the ocean carrier, the intermodal rail carrier, and the dray carrier. Each one had custody and each one will deny responsibility. The ocean carrier says the container was SOLAS-verified and properly loaded. The rail carrier says the container was accepted in good condition at Long Beach. The dray carrier says they only moved it 12 miles from the ramp and there was no incident.
+
+**Why It's Tricky:**
+Concealed damage in intermodal containers is the hardest claim in freight. The damage is hidden inside a sealed box that passes through multiple carriers across international boundaries. Each carrier has a plausible defense. The ocean carrier invokes COGSA (Carriage of Goods by Sea Act) limitations. The rail carrier invokes the Carmack Amendment domestically but argues the damage pre-dates their custody. The dray carrier points to the intact seal.
+
+The damage pattern — crushed cases deep in the container — is consistent with load shift, but load shift can occur during ocean transit (rolling seas), rail transit (humping and coupling at railyards), or even the final dray if the driver hit a severe pothole or made a hard stop. Without accelerometer data inside the container, pinpointing the moment of shift is nearly impossible.
+
+Aerosol cans add a complication: leaking aerosols are a hazmat concern (compressed gas, flammable propellant). The importer now has a cleanup cost on top of the product loss.
+
+**Common Mistake:**
+Filing a single claim against the ocean carrier for the full amount because they had the longest custody. COGSA limits the ocean carrier's liability to $500 per package (or per customary freight unit) unless a higher value was declared on the ocean bill of lading. If each pallet is a "package," the importer recovers $500 per pallet — far less than the actual loss. If no excess value was declared, the ocean carrier's exposure is capped regardless of actual damage.
+
+The second mistake: not inspecting the container immediately upon arrival. The importer grounded the container Tuesday and didn't unload until Wednesday. That 24-hour gap weakens the claim because any carrier can argue the damage occurred during the grounded period (temperature expansion, forklift impact to the grounded container, etc.).
+
+**Expert Approach:**
+1. Document everything before moving anything. Once the concealed damage is discovered mid-unload, stop unloading. Photograph the damage in situ — the crushed cases, the load configuration, the position of damage relative to the container doors and walls. Photograph the container interior from the door end showing the overall load state. Note the container number, seal number, and condition of the seal (intact, cut, or replaced).
+2. File concealed damage notices simultaneously with all three domestic parties: the dray carrier, the intermodal rail carrier, and the ocean carrier (or their agent). The notice must go out within the applicable time limits: 3 days for concealed damage under the Carmack Amendment (rail and dray), and per the ocean bill of lading terms for the ocean carrier (varies, but typically "within reasonable time of delivery").
+3. Inspect the container itself for evidence of the damaging event. Check for: (a) scuff marks on the container floor indicating load shift direction, (b) dents or impacts on the container walls that could have caused the shift, (c) condition of load securing (dunnage, airbags, strapping) and whether it was adequate per the shipper's load plan, and (d) moisture or condensation damage that suggests container rain, which is an ocean transit issue.
+4. Request the container's GPS and event data from the intermodal rail carrier. Modern chassis-mounted containers on rail generate movement and impact event data. If there was a significant impact event at a rail yard (coupling, humping, derailment), it will show in the data.
+5. Review the ocean carrier's vessel tracking for the voyage. If the vessel encountered severe weather (check NOAA marine weather data for the Pacific crossing dates), heavy roll could have initiated the load shift.
+6. Assess the load plan from Shenzhen. Were the aerosol cases (lightest, most fragile) stacked on the bottom at the rear of the container? If so, the Chinese shipper's loading crew made a fundamental error — heavy items go on the bottom, fragile items go on top and toward the door end. This is a shipper loading liability issue that no carrier is responsible for.
+7. For the hazmat cleanup: engage a licensed hazmat cleanup contractor for the leaking aerosols. Document the cleanup scope and cost. This cost is recoverable as consequential damages in the claim, but only against the party found liable for the load shift — not as a blanket charge to all carriers.
+8. File claims against the appropriate parties based on the evidence. In practice, most intermodal concealed damage claims with ambiguous causation settle through negotiation between the ocean carrier's P&I club and the cargo insurer. If the importer has marine cargo insurance (which they should, on a $67K shipment from China), file the insurance claim and let the insurer subrogate against the carriers.
+
+**Key Indicators:**
+- Damage only to cases deep in the container (rear, loaded first) strongly suggests load shift that occurred early in transit, not at the end — the cases at the door end (loaded last) served as a buffer
+- An intact container seal eliminates pilferage or unauthorized opening — the damage happened inside a sealed box during transit
+- Aerosol cases loaded at the bottom of a stack are a shipper loading error unless the load plan specifically accounted for their fragility and the damage was caused by an extraordinary event
+- Scuff marks on the container floor running longitudinally (front-to-back) suggest a braking or acceleration event; lateral scuff marks suggest roll (ocean) or curve forces (rail)
+- If the container was loaded with inflatable dunnage bags and the bags are deflated or burst, the bags were either undersized for the load or punctured by the aerosol cans during the shift — inspect the bags
+
+**Documentation Required:**
+- Photographs of damage in situ (before any cleanup or further unloading)
+- Container number, seal number, and seal condition photographs
+- Container inspection report (floor scuffs, wall impacts, dunnage condition)
+- Concealed damage notices to all carriers (with date/time stamps)
+- Ocean bill of lading with package and value declarations
+- Shipper's load plan from Shenzhen (container stuffing report)
+- Intermodal rail carrier's GPS and event data for the container
+- Vessel voyage data and NOAA weather records for the Pacific crossing
+- Hazmat cleanup contractor's scope and cost documentation
+- Marine cargo insurance claim filing (if applicable)
+- Packing list with case-level detail showing damaged vs. undamaged product
+
+**Resolution Timeline:**
+- Hour 0: Discovery — stop unloading, photograph, document
+- Hours 0–24: Concealed damage notices filed with all carriers
+- Days 1–3: Container inspection, carrier data requests, cleanup initiated
+- Days 3–14: Evidence assembly, load plan review, voyage/rail data analysis
+- Days 14–30: Marine cargo insurance claim filed (if applicable)
+- Days 30–90: Carrier responses and negotiation
+- Days 90–180: Settlement or arbitration (intermodal claims average 120 days to resolve)
+
+---
+
+### Edge Case 8: Broker Insolvency Mid-Shipment with Carrier Demanding Payment for Release
+
+**Situation:**
+A mid-size food manufacturer uses a freight broker to arrange a truckload of frozen prepared meals (retail value ~$128,000, freight charges ~$4,800) from their production facility in Omaha to a grocery distribution center in Minneapolis. The broker quoted the shipper $4,800 all-in and contracted the actual carrier at $3,900.
+
+The carrier picks up the load in Omaha on Monday. Tuesday morning, the shipper receives a call from the carrier's dispatcher: the broker has not paid their last three invoices totaling $14,200 across multiple loads, and the broker is not answering phones or emails. The carrier's dispatcher says they will not deliver the Minneapolis load until someone guarantees payment of $3,900 for this load plus the $14,200 in outstanding invoices from previous loads. The carrier currently has the loaded trailer at their Des Moines yard. The frozen meals have a 72-hour window before the cold chain becomes a concern, and the grocery DC has a receiving appointment Wednesday at 06:00 for a promotional launch.
+
+The shipper calls the broker. The number is disconnected. The broker's website is down. A quick search reveals the broker filed Chapter 7 bankruptcy two days ago.
+
+**Why It's Tricky:**
+Under federal law (49 USC §14103), a carrier can assert a lien on freight for unpaid charges. However, the carrier's lien is for charges on *this* shipment, not for the broker's unpaid invoices on previous shipments. The carrier is conflating two separate obligations: (a) the $3,900 owed for the current load, and (b) the $14,200 the insolvent broker owes from prior loads. The shipper owes the broker $4,800, not the carrier — the shipper has no contractual relationship with the carrier.
+
+But the carrier has physical possession of $128,000 in perishable freight. Practically, they have leverage regardless of the legal merits. The frozen meals don't care about legal arguments — they're thawing. And the grocery DC will cancel the receiving appointment and the promotional launch if the product doesn't arrive Wednesday.
+
+The shipper is also exposed to double-payment risk: they may have already paid the broker the $4,800 (or it's in their payment queue), and now the carrier wants $3,900 directly. If the shipper pays the carrier, they've paid $8,700 in freight charges for a $4,800 lane.
+
+**Common Mistake:**
+Paying the carrier's full demand ($3,900 + $14,200 = $18,100) to release the freight. This is extortion dressed as a lien claim, and it rewards bad behavior. The shipper has no obligation for the broker's prior debts, and paying them creates a precedent.
+
+The second mistake: refusing to pay anything and calling a lawyer. By the time the lawyer sends a demand letter, the frozen meals are compromised and the promotional launch is blown. Legal purity is cold comfort when you're explaining to the grocery chain why the endcap is empty.
+
+**Expert Approach:**
+1. Confirm the broker's insolvency. Check the FMCSA's broker licensing database for the broker's MC number — if their bond has been revoked or their authority is "inactive," insolvency is confirmed. Search federal bankruptcy court records (PACER) for the Chapter 7 filing.
+2. Contact the carrier's dispatcher or owner directly. Be professional, not adversarial. Acknowledge that the carrier is in a difficult position. State clearly: "We will guarantee payment of $3,900 for this load directly to you, but we are not responsible for the broker's prior debts. Those are claims against the broker's surety bond and bankruptcy estate."
+3. If the carrier accepts $3,900 for release, get it in writing before wiring the funds. Prepare a simple release letter: "Carrier agrees to deliver shipment [PRO/BOL number] to [consignee] in exchange for direct payment of $3,900 from [shipper]. This payment satisfies all carrier charges for this shipment. Carrier acknowledges that shipper is not liable for any amounts owed by [broker name/MC number] for other shipments."
+4. Wire the $3,900 or provide a company check at delivery. Do not use a credit card (the carrier will add a surcharge). Do not agree to pay within 30 days (the carrier wants certainty now, and delay risks them re-impounding the freight).
+5. If the carrier refuses to release for $3,900 and insists on the full $18,100, escalate to the FMCSA. Carriers who refuse to deliver freight to extract payment for unrelated loads are violating 49 USC §14103. File a complaint with FMCSA and inform the carrier you've done so. Most carriers will release at this point.
+6. As a last resort, if the freight is perishable and the carrier won't budge, consider paying the $3,900 plus a negotiated portion of the old debt (e.g., $3,000 of the $14,200) as a commercial compromise, with a written statement that the additional payment is "disputed and paid under protest to prevent spoilage of perishable goods." This preserves the shipper's right to recover the extra payment later.
+7. After the immediate crisis, file a claim against the broker's surety bond. Freight brokers are required to carry a $75,000 surety bond. The bond is specifically intended to cover situations like this. File the claim with the surety company listed on the broker's FMCSA registration. Note: if the broker has multiple unpaid carriers, the $75,000 bond will be split pro-rata among all claimants, so the recovery may be partial.
+8. Also file a claim in the broker's Chapter 7 bankruptcy proceeding as an unsecured creditor for any amounts paid above the original $4,800 contract rate. Recovery in Chapter 7 is typically pennies on the dollar, but it preserves the legal right.
+
+**Key Indicators:**
+- A broker whose phone is disconnected and website is down is either insolvent or has absconded — either way, they are no longer a viable intermediary
+- Carriers who demand payment for unrelated loads as a condition of delivery are overreaching, but they know that perishable freight gives them leverage
+- Check if the shipper's broker contract has a "double-brokering" prohibition — some insolvent brokers were actually re-brokering loads to other brokers, adding a layer of complexity to the payment chain
+- The broker's surety bond amount ($75,000) is almost never enough to cover all claims when a broker fails — prioritize getting your claim filed early
+- If the carrier is a small fleet (5 or fewer trucks), they may be genuinely unable to absorb the loss from the broker and may be more willing to negotiate if they receive some payment quickly
+
+**Documentation Required:**
+- Original broker-shipper contract with rate confirmation
+- Carrier's rate confirmation with the broker (if obtainable)
+- FMCSA broker registration showing authority status and surety bond information
+- Bankruptcy filing documentation (PACER search results)
+- Written release agreement between shipper and carrier
+- Wire transfer or payment confirmation for the $3,900 direct payment
+- "Paid under protest" letter if any amount above $3,900 is paid
+- Surety bond claim filing with the broker's surety company
+- Bankruptcy court claim filing as unsecured creditor
+- Temperature monitoring data from the shipment (to document cold chain integrity during the delay)
+- Consignee delivery confirmation and any penalty or chargeback documentation from the grocery chain
+
+**Resolution Timeline:**
+- Hours 0–4: Broker insolvency confirmed, carrier negotiation initiated
+- Hours 4–12: Payment agreement reached, funds wired, freight released
+- Hours 12–24: Delivery completed to grocery DC
+- Days 1–7: Surety bond claim filed
+- Days 7–30: Bankruptcy court claim filed
+- Days 30–180: Surety bond claim adjudication (typical timeline is 90–120 days)
+- Days 180+: Bankruptcy distribution (can take 1–2 years)
+
+---
+
+### Edge Case 9: Seasonal Peak Surcharge Dispute During Declared Weather Emergency
+
+**Situation:**
+A home improvement retailer has a contract with a national LTL carrier that includes a published fuel surcharge table and a "peak season surcharge" clause. The contract states that peak surcharges of up to 18% may be applied during "periods of extraordinary demand as determined by the carrier," with 14 days' written notice.
+
+In mid-January, a severe ice storm hits the central U.S. — Kansas City, St. Louis, Memphis, and Nashville are all affected. The carrier declares a "weather emergency" on January 15 and simultaneously activates a 22% "emergency surcharge" on all shipments moving through or originating from the affected regions. The carrier's notice, sent via email blast on January 15, states the surcharge is effective January 16.
+
+The retailer has 340 LTL shipments in transit and another 280 scheduled to ship in the next 7 days through those regions. At an average of $1,200 per shipment, the 22% surcharge adds approximately $163,000 in unbudgeted freight cost across those 620 shipments. The retailer's logistics director objects on three grounds: (1) the contract caps peak surcharges at 18%, (2) the 14-day notice requirement was not met, and (3) this is a weather event, not "extraordinary demand," and should be covered by the existing fuel surcharge mechanism.
+
+The carrier's position: the weather emergency surcharge is separate from the peak season surcharge and is authorized under the carrier's rules tariff, which the contract incorporates by reference. The carrier cites item 560 in their tariff, which states "emergency surcharges may be applied without prior notice during force majeure events."
+
+**Why It's Tricky:**
+The dispute turns on contract interpretation, specifically whether the weather emergency surcharge is a type of peak surcharge (capped at 18% with 14-day notice) or a separate tariff item (uncapped, no notice required). Both readings are defensible. The contract's peak surcharge clause doesn't specifically exclude weather events. But the tariff's force majeure provision is broadly written and has been part of the carrier's published tariff for years.
+
+Practically, the carrier has leverage because the freight is either in transit (already moving at the carrier's mercy) or needs to ship to meet store replenishment schedules. The retailer can't reroute 620 shipments to another carrier overnight. And the ice storm is real — the carrier is genuinely incurring higher costs (driver detention, re-routing, de-icing, reduced productivity at affected terminals).
+
+**Common Mistake:**
+Paying the 22% surcharge under protest and then filing a batch claim after the fact. Carriers rarely refund surcharges retroactively, and the retailer's purchasing department will have already booked the expense. The dispute becomes an accounting exercise that drags on for months with no resolution.
+
+The opposite mistake: refusing to ship until the surcharge is resolved. The stores need product, especially during an ice storm when consumers are buying emergency supplies. A shipping freeze costs more in lost sales than the surcharge.
+
+**Expert Approach:**
+1. Separate the in-transit shipments from the pending shipments. The 340 shipments already moving are subject to the carrier's tariff as of the ship date — if they shipped before January 16, the surcharge should not apply to them. Challenge any surcharge applied to shipments that were tendered before the effective date.
+2. For the 280 pending shipments, negotiate immediately. Contact the carrier's pricing or contract manager (not customer service). Propose a compromise: the retailer will accept an 18% surcharge (the contract cap) for the weather period, applied to shipments originating from or delivering to the affected zip codes only, not all shipments "moving through" the region. A shipment from Dallas to Atlanta that transits Memphis should not bear a surcharge meant to cover Memphis-area operational costs.
+3. Challenge the tariff incorporation. Most shipper-carrier contracts include a clause like "the carrier's tariff is incorporated by reference except where this contract specifically provides otherwise." The contract specifically provides a peak surcharge cap of 18% with 14-day notice. Argue that this specific provision overrides the general tariff force majeure clause. Have the retailer's transportation attorney send a letter to this effect within 48 hours.
+4. Request documentation of the carrier's actual incremental costs during the weather event. Carriers often apply surcharges that far exceed their actual cost increase. A 22% surcharge on $744,000 in freight ($163,680) should correlate to demonstrable cost increases — driver bonuses, equipment repositioning, de-icing, etc. Ask for the cost justification. Carriers rarely provide it, which weakens their position.
+5. If the carrier refuses to negotiate, identify which of the 280 pending shipments can move via alternate carriers. Even shifting 30–40% of the volume signals to the contract carrier that the surcharge has competitive consequences. A national retailer with 280 shipments can find partial capacity even during a weather event.
+6. Document the surcharge dispute in writing for the annual contract renewal. A carrier that imposed a 22% surcharge with one day's notice during a weather event has demonstrated that their tariff's force majeure clause is a material contract risk. In the next RFP, either negotiate a hard cap on emergency surcharges or require the carrier to remove the force majeure provision from the incorporated tariff.
+
+**Key Indicators:**
+- A surcharge that exceeds the contract's peak season cap is a contract violation unless the carrier can clearly show it's authorized under a separate tariff provision — and even then, the contract's specific terms should override the general tariff
+- One day's notice for a 22% surcharge is commercially unreasonable regardless of the contractual language. No shipper can adjust their logistics budget overnight.
+- Carriers that apply regional surcharges to all traffic "passing through" a region (rather than originating or terminating there) are overreaching. A shipment that transits Memphis on a linehaul trailer incurs no additional cost unless it's being cross-docked at the Memphis terminal.
+- Check whether the carrier applied the same surcharge to all customers or only to contracted customers. If spot-market shipments during the same period were priced at normal + 10%, the contracted customers are being overcharged.
+- Weather events that last 3–5 days should not generate surcharges that persist for 14–21 days. Challenge the surcharge end date, not just the rate.
+
+**Documentation Required:**
+- Shipper-carrier contract with peak surcharge clause and tariff incorporation language
+- Carrier's published tariff, specifically the force majeure and emergency surcharge provisions
+- Carrier's email notification of the weather emergency surcharge (with date, time, and effective date)
+- List of all shipments affected (in-transit and pending) with ship dates and origin/destination
+- Carrier's actual surcharge amounts applied to each shipment
+- Retailer's written objection letter from transportation attorney
+- Documentation of the actual weather event (NWS advisories, road closure reports)
+- Alternate carrier quotes for diverted shipments
+- Carrier's cost justification documentation (if provided)
+- Settlement agreement (if reached)
+
+**Resolution Timeline:**
+- Hours 0–24: Separate in-transit from pending shipments, initial negotiation contact
+- Days 1–3: Attorney's letter sent, alternate carrier quotes obtained, compromise proposed
+- Days 3–7: Negotiation period (carrier will typically respond within a week under pressure)
+- Days 7–14: Resolution of the surcharge rate (typically settles at 15–18% for the affected period)
+- Days 14–30: Credit memo processing for overcharged in-transit shipments
+- Months 3–6: Incorporate lessons into annual contract renewal
+
+---
+
+### Edge Case 10: Systematic Pilferage Pattern Across Multiple LTL Terminal Shipments
+
+**Situation:**
+A consumer electronics brand ships approximately 120 LTL shipments per month through a regional carrier's network to independent retailers across the Southeast. Over a 90-day period, the brand's claims department notices a pattern: 14 shortage claims totaling $47,200, all involving small, high-value items (wireless earbuds, smartwatches, Bluetooth speakers) in the $150–$800 retail range. The shortages range from 2–8 units per shipment.
+
+The pattern: all 14 claims involve shipments that passed through the carrier's Atlanta terminal. The shipments originate from various locations (the brand's warehouses in Charlotte, Dallas, and Memphis) and deliver to various retailers. The only common element is the Atlanta cross-dock. The shortages are discovered at delivery — the retailer opens the carton and finds units missing inside otherwise intact-looking cases. The case count on the BOL matches the case count at delivery, but the unit count inside specific cases is short.
+
+The carrier has denied 9 of the 14 claims, citing "no visible damage at delivery" and "correct case count per BOL." The brand suspects organized pilferage at the Atlanta terminal — someone is opening cases, removing small high-value items, and resealing or re-taping the cases.
+
+**Why It's Tricky:**
+Proving systematic pilferage at a carrier's terminal is extremely difficult. The standard claim process evaluates each shipment independently. Each individual claim looks like a minor packaging or picking error — "maybe the warehouse packed 22 earbuds instead of 24 in that case." But 14 claims in 90 days with the same profile (same terminal, same product category, same method) is not coincidence. It's organized theft.
+
+The carrier's claims department isn't equipped to recognize patterns. They adjudicate each claim against the documentation: case count matched at delivery, no visible damage, claim denied. They don't aggregate claims across shipments to look for terminal-specific patterns. And the carrier's terminal management in Atlanta has no incentive to investigate — acknowledging a pilferage problem at their terminal implicates their own employees.
+
+The brand's individual claim amounts ($1,500–$5,500 each) are below the threshold that typically triggers a serious investigation. No single claim justifies hiring an investigator or involving law enforcement.
+
+**Common Mistake:**
+Continuing to file individual claims and accepting the denials, or switching carriers entirely without pursuing the pattern. Switching carriers doesn't recover the $47,200 already lost and doesn't address the root cause — the pilfered goods are still flowing into a gray market somewhere.
+
+The other mistake: confronting the carrier's sales representative with the pilferage accusation without data. "We think your people are stealing" destroys the commercial relationship. "We've identified a statistically significant claim pattern that we need to investigate jointly" gets attention.
+
+**Expert Approach:**
+1. Build the pattern analysis first. Create a spreadsheet mapping all 14 claims by: origin, destination, Atlanta terminal arrival/departure dates, case count, shortage amount, shortage product type, and claim outcome. Add the 106 shipments that passed through Atlanta without a shortage claim. Calculate the shortage rate for Atlanta-routed shipments (14/120 = 11.7%) vs. the brand's overall shortage rate across all carriers and terminals (industry average for consumer electronics is 1–2%).
+2. Identify the shift pattern. Atlanta terminal operates multiple shifts. Cross-reference the 14 shortage shipments' arrival and departure scan times against the terminal's shift schedule. If all 14 shipments were on the dock during the same shift window, the pilferage is likely associated with specific workers on that shift.
+3. Present the pattern analysis to the carrier's Director of Claims or VP of Operations — not the sales rep, not the local terminal manager. This is a corporate-level conversation. Frame it as: "We have data suggesting a pattern that requires a joint investigation. Here's our analysis. We want to work with your security team."
+4. Request that the carrier's loss prevention or security department conduct a covert investigation at the Atlanta terminal. Major LTL carriers have internal security teams specifically for this. Provide them with the shift-pattern analysis and the product profiles that are being targeted.
+5. In parallel, introduce covert tracking. Ship 5–10 "bait" packages through the Atlanta terminal containing AirTag-type trackers concealed inside the product boxes alongside real product. If units are pilfered, the trackers will provide location data on where the stolen goods end up, which helps law enforcement build a case.
+6. Implement tamper-evident packaging for all high-value shipments moving through the Atlanta terminal. Use serialized security tape that changes color if peeled and replaced. This doesn't prevent pilferage but makes it detectable at delivery — if the security tape is broken, the shortage is documented immediately.
+7. File a comprehensive claim covering all 14 shortages as a single pattern claim, totaling $47,200, supported by the statistical analysis. Individual claims of $2,000 get denied by a claims adjuster following a script. A $47,200 pattern claim with statistical evidence gets escalated to claims management.
+8. If the carrier refuses to investigate or settle, consider filing a report with the local FBI field office. Organized cargo theft from carrier terminals is a federal crime (18 USC §659, theft from interstate or foreign shipments). The FBI's cargo theft unit handles exactly this type of pattern.
+
+**Key Indicators:**
+- Shortages of small, high-value consumer electronics from inside otherwise intact cases is the hallmark of organized terminal pilferage, not random loss
+- A single terminal appearing in all claims is the strongest pattern indicator — it eliminates origin and destination as variables
+- Shortage claims that the carrier denies because "case count matched" are actually consistent with pilferage — the thief reseals the case to avoid detection at the piece-count level
+- If the shortages are concentrated on specific days of the week, there may be a shift or crew pattern
+- Check if the carrier's Atlanta terminal has had employee theft incidents reported in the past — local court records or news reports may reveal prior issues
+
+**Documentation Required:**
+- Detailed claim log for all 14 shortage claims with full shipment data
+- Statistical pattern analysis (spreadsheet) showing Atlanta terminal as common factor
+- Shift-pattern analysis correlating shortage shipments to terminal operating hours
+- Rate comparison: shortage rate for Atlanta-routed vs. non-Atlanta-routed shipments
+- Photographs of opened cases showing missing units and condition of tape/seal
+- Bait package tracking data (if deployed)
+- Tamper-evident packaging results (if implemented)
+- Carrier correspondence — all claim filings, denials, and escalation communications
+- Formal pattern claim filing with the carrier ($47,200 aggregate)
+- Law enforcement report (if filed)
+
+**Resolution Timeline:**
+- Days 0–7: Pattern analysis completed and presented to carrier leadership
+- Days 7–14: Carrier security team briefed and investigation initiated
+- Days 14–30: Bait packages shipped, tamper-evident packaging deployed
+- Days 30–60: Investigation results (carrier internal) and pattern claim response
+- Days 60–90: Settlement negotiation on the aggregate claim
+- Days 90–180: If pilferage is confirmed, potential criminal prosecution and full recovery
+
+---
+
+### Edge Case 11: Hazmat Shipment Damaged in Transit with Environmental Contamination Risk
+
+**Situation:**
+A specialty chemical manufacturer ships a truckload of sodium hypochlorite solution (industrial bleach, 12.5% concentration) — 20 IBC totes (275 gallons each, 5,500 gallons total), classified as UN1791, Corrosive Liquid, Class 8, PG II — from their plant in Baton Rouge, LA to a water treatment facility in Birmingham, AL.
+
+At approximately mile 180 on I-59 near Hattiesburg, MS, the driver encounters a sudden lane closure for road construction. He brakes hard. Three IBC totes in the rear of the trailer shift forward, two of them toppling. One tote's valve assembly shears off and sodium hypochlorite begins leaking onto the trailer floor and out the rear door gaps. The driver smells chlorine, pulls over, and calls his dispatcher. He estimates 50–75 gallons have leaked onto the highway shoulder before he could stop.
+
+The situation now involves: (a) a hazmat spill on a state highway requiring notification and cleanup, (b) a damaged shipment where 3 of 20 totes may be compromised, (c) a driver who has been exposed to chlorine vapor and may need medical attention, (d) a consignee water treatment plant that needs the chemical for drinking water treatment, and (e) potential EPA, Mississippi DEQ, and DOT enforcement actions.
+
+**Why It's Tricky:**
+A hazmat in-transit incident is not just a freight claim — it's a multi-agency regulatory event. The spill triggers mandatory reporting obligations under 49 CFR §171.15 (immediate phone report to the National Response Center if the spill meets reportable quantity thresholds) and 49 CFR §171.16 (written hazmat incident report within 30 days). Sodium hypochlorite at 50+ gallons on a highway triggers the reportable quantity threshold.
+
+The environmental cleanup cost will likely dwarf the product value. The 5,500 gallons of chemical is worth about $8,250. The highway shoulder cleanup, soil remediation, and storm drain protection for a 50-gallon bleach spill on a Mississippi highway will cost $15,000–$40,000 depending on proximity to waterways.
+
+Liability is layered: the shipper is the "offeror" under hazmat regulations and is responsible for proper packaging and loading. The carrier is responsible for safe transportation and proper load securement. If the IBC totes shifted because they weren't properly secured (blocked and braced per the carrier's securement obligations under 49 CFR §393), the carrier bears liability. If the totes shifted because the valve assemblies were improperly rated for transport vibration, the shipper/manufacturer bears liability.
+
+**Common Mistake:**
+Treating this as a freight claim first and a hazmat incident second. It's the opposite. The first priority is life safety and environmental containment, followed by regulatory compliance, and then — distantly — commercial recovery.
+
+The second mistake: the driver attempting to clean up the spill himself. Sodium hypochlorite at 12.5% concentration is a corrosive that generates toxic chlorine gas, especially if it contacts organic matter or acid (which could be in the road debris). The driver should evacuate the area, not grab a mop.
+
+**Expert Approach:**
+1. Immediate response (minute 0): the driver must move upwind and uphill from the spill, call 911, and report a hazardous materials spill. The driver must not attempt to stop the leak, upright the totes, or clean the spill unless they are hazmat-trained and have appropriate PPE (which over-the-road drivers typically do not carry for Class 8 corrosives).
+2. Regulatory notifications (within 15 minutes): the carrier's dispatch must call the National Response Center (NRC) at 800-424-8802. This is a mandatory immediate notification for any hazmat spill meeting the reportable quantity. For sodium hypochlorite, the reportable quantity is 100 lbs — 50 gallons at approximately 10 lbs/gallon is 500 lbs, well over the threshold.
+3. The carrier must also notify Mississippi's Department of Environmental Quality (MDEQ) emergency spill line. State notification is required in addition to federal NRC notification.
+4. Driver medical: if the driver is experiencing respiratory distress, burning eyes, or coughing from chlorine exposure, 911 will dispatch EMS. The carrier must ensure the driver receives medical attention before worrying about the freight.
+5. Once emergency services arrive and control the scene, the carrier must arrange for a licensed hazmat cleanup contractor. The Mississippi State Highway Patrol will not allow the carrier to move the trailer until the spill is contained and the remaining totes are assessed for stability. This can take 4–12 hours.
+6. Assessment of the remaining product: the 17 undamaged totes and the 2 toppled (but possibly intact) totes need to be inspected by a hazmat technician before they can continue transport. If the toppled totes have compromised valve assemblies or cracked walls, they must be overpacked (placed inside larger containment) for transport to a transload facility — they cannot continue to the consignee in damaged condition.
+7. Load securement investigation: before moving any freight, document the securement setup. Were the IBC totes blocked and braced? Were load bars or cargo straps used? IBC totes on flatbed or dry van trailers must be secured per 49 CFR §393.116 (securement of intermodal containers) or the general cargo securement provisions. Photograph the securement setup as-is. This is the key liability evidence.
+8. Contact the consignee water treatment plant immediately. They need to source replacement chemical from a backup supplier to maintain drinking water treatment operations. A water treatment plant running low on disinfection chemical is a public health emergency. Provide the plant with the timeline for delivery of the undamaged product (likely 24–48 hours after scene clearance) and help them source the 825-gallon shortfall (3 damaged totes worth) from a regional supplier.
+9. File the written hazmat incident report (DOT Form F 5800.1) within 30 days. This report goes to PHMSA (Pipeline and Hazardous Materials Safety Administration) and becomes a public record. Accuracy is critical — this document can be used in enforcement proceedings.
+10. Pursue the cargo and environmental cleanup costs based on liability determination. If the carrier failed to properly secure the load, they bear liability for the product loss, cleanup costs, driver medical costs, and any regulatory fines. If the shipper's IBC totes had a manufacturing defect (e.g., the valve assembly sheared at normal braking force, indicating a design flaw), the tote manufacturer bears product liability.
+
+**Key Indicators:**
+- A valve assembly that shears off during normal hard braking (not a collision) suggests either an improperly rated valve or a tote that was overfilled — check the fill level against the tote's maximum capacity and the 80% fill rule for IBCs containing corrosives
+- If the load was unsecured (no straps, no load bars, no blocking), the carrier's liability is clear regardless of the braking situation
+- Three totes shifting suggests a systemic securement failure, not an isolated strap break. One tote falling could be a strap failure; three totes means the entire load was inadequately secured.
+- Check the driver's CDL for hazmat endorsement. Driving a placarded load without the endorsement is a separate violation that compounds the carrier's liability.
+- If the sodium hypochlorite reached a storm drain or waterway, the cleanup cost escalates dramatically and may trigger Superfund reporting requirements
+
+**Documentation Required:**
+- NRC notification confirmation number and timestamp
+- MDEQ spill notification confirmation
+- 911 call record and emergency response documentation
+- Photographs of the spill scene, damaged totes, and load securement setup (taken before cleanup)
+- Driver's medical treatment records (if applicable)
+- Hazmat cleanup contractor's containment and remediation report with cost
+- 49 CFR §393 load securement inspection report
+- DOT Form F 5800.1 hazmat incident report (filed within 30 days)
+- Driver's CDL and hazmat endorsement verification
+- IBC tote manufacturer specifications and valve assembly ratings
+- BOL, shipping papers, and emergency response information (ERG guide page)
+- Consignee notification and replacement sourcing documentation
+- Environmental monitoring results (soil, water testing at the spill site)
+
+**Resolution Timeline:**
+- Minutes 0–15: Emergency notifications (911, NRC, MDEQ)
+- Hours 0–4: Scene control, spill containment, driver medical attention
+- Hours 4–12: Hazmat cleanup, remaining totes inspected, trailer released
+- Hours 12–48: Undamaged totes delivered to consignee, replacement chemical sourced for shortfall
+- Days 1–7: Load securement investigation, liability assessment, carrier/shipper negotiation
+- Days 7–30: DOT Form F 5800.1 filed, environmental monitoring results received
+- Days 30–90: Cleanup cost and cargo claim settlement
+- Days 90–365: Potential PHMSA enforcement action (civil penalties for securement violations can reach $500,000+ per violation)
+
+---
+
+### Edge Case 12: Customer Rejects Shipment for Late Delivery on JIT Production Line, but Carrier Met the BOL Delivery Window
+
+**Situation:**
+An automotive Tier 1 supplier ships a truckload of stamped metal brackets (43,000 pieces, value $186,000) from their Youngstown, OH plant to a GM assembly plant in Spring Hill, TN. The parts feed directly into the truck assembly line under a JIT (just-in-time) delivery program. The JIT window, per GM's scheduling system, is Tuesday 04:00–06:00 — parts must arrive within that 2-hour window or the line shuts down.
+
+The BOL, however, lists the delivery date as "Tuesday" with no specific time window. The carrier's rate confirmation lists delivery as "by end of day Tuesday." The carrier delivers at 11:42 on Tuesday. The GM receiving dock rejects the shipment because the JIT window closed at 06:00. GM's production line halted at 06:47 when the bracket buffer stock ran out, and the line was down for 4.5 hours until the carrier's truck was finally unloaded at 11:42 under emergency protocols.
+
+GM issues a line-down chargeback to the Tier 1 supplier for $215,000 (the calculated cost of 4.5 hours of assembly line downtime at ~$47,800/hour). The Tier 1 supplier demands the carrier pay the chargeback plus the freight charges. The carrier says they delivered on Tuesday — within the BOL's delivery date — and they have no knowledge of, or obligation to meet, a JIT delivery window that was never communicated to them.
+
+**Why It's Tricky:**
+The carrier has a strong defense. The BOL says "Tuesday" and the carrier delivered Tuesday. The rate confirmation says "by end of day Tuesday" and the carrier delivered by end of day. The JIT window of 04:00–06:00 appears nowhere in the carrier's documentation. The Tier 1 supplier's logistics team communicated the JIT window to their own scheduling system and to GM, but never put it on the BOL or the carrier's rate confirmation.
+
+The $215,000 chargeback is a consequential damage claim — the carrier is responsible for the freight charges and possibly the value of the goods if damaged, but consequential damages (like production line downtime) require that the carrier had "actual or constructive notice" of the specific consequences of late delivery. Under the Carmack Amendment, consequential damages are recoverable only if the carrier knew or should have known about the specific time-sensitivity.
+
+A carrier delivering at 11:42 for a "Tuesday" delivery did nothing wrong by the terms they agreed to. The Tier 1 supplier's failure to communicate the JIT window to the carrier is the root cause, but GM doesn't care about the supplier's internal logistics — they want their $215,000.
+
+**Common Mistake:**
+The Tier 1 supplier's traffic manager tries to recover the full $215,000 from the carrier by arguing "you knew this was an automotive JIT delivery." But knowing a consignee is an auto assembly plant is not the same as knowing the specific delivery window. Many deliveries to assembly plants go to a warehouse dock, not the JIT receiving dock. Without specific written notice of the 04:00–06:00 window and the consequences of missing it, the carrier's liability for consequential damages is virtually zero.
+
+The second mistake: the supplier accepting the full $215,000 chargeback from GM without negotiation. GM's chargeback calculations are often inflated — the $47,800/hour figure includes overhead allocation, labor costs for idled workers, and opportunity cost. The actual incremental cost of 4.5 hours of downtime may be significantly lower. Chargebacks are negotiable.
+
+**Expert Approach:**
+1. Accept responsibility for the communication failure — the Tier 1 supplier's logistics team did not convey the JIT window to the carrier. This is not the carrier's fault. Attempting to blame the carrier poisons a relationship for a claim they'll ultimately lose.
+2. Negotiate the GM chargeback. Request GM's detailed calculation supporting the $47,800/hour figure. Standard OEM downtime calculations include direct costs (line labor, utility, scrap from partial builds) and indirect costs (overhead allocation, management time, schedule recovery). Push back on the indirect costs. A 4.5-hour stoppage with a full recovery by end of shift typically warrants a 40–60% reduction in the chargeback amount. Aim for $90,000–$130,000.
+3. File an internal corrective action. The failure was in the supplier's logistics process: the JIT window was known internally but not transmitted to the carrier. Implement a standard procedure requiring all JIT delivery windows to appear on the BOL in the "special instructions" field and on the carrier's rate confirmation. The rate confirmation should state: "DELIVERY WINDOW: 04:00–06:00 TUESDAY. LATE DELIVERY WILL RESULT IN PRODUCTION LINE DOWNTIME AT APPROXIMATELY $X/HOUR."
+4. For the carrier relationship: share the situation transparently. Explain the JIT delivery program and acknowledge the communication gap. Offer to add the delivery window to future rate confirmations along with an appropriate accessorial charge for time-definite delivery. Carriers will quote a premium for guaranteed delivery windows — typically $200–$500 for a 2-hour window on a 500-mile haul — but that premium is trivial compared to a $215,000 chargeback.
+5. Implement a buffer strategy with GM. The underlying vulnerability is a single truckload feeding a production line with minimal buffer stock. Work with GM's materials planning team to increase the bracket buffer from 47 minutes (which is what the 06:47 line-down time implies) to 4 hours. This costs additional warehouse space and carrying cost at the assembly plant, but it converts a missed 2-hour delivery window from a $215,000 disaster to a minor scheduling inconvenience.
+6. Consider a carrier-of-last-resort arrangement for this lane. Identify a dedicated carrier or small fleet within 2 hours of Spring Hill that can run an emergency load if the primary carrier is delayed. Pre-stage one truckload of brackets at a cross-dock near Spring Hill as rolling safety stock. The carrying cost of $186,000 in brackets sitting at a cross-dock ($400–$600/month in storage) is insurance against $215,000 chargebacks.
+
+**Key Indicators:**
+- A BOL without a specific delivery time window provides the carrier zero legal exposure for consequential damages from late delivery — the entire consequential damages claim depends on documented, communicated time-sensitivity
+- GM and other major OEMs chargeback calculations are formulaic and include significant overhead allocation — they are always negotiable, though the negotiation requires understanding the OEM's cost model
+- A 47-minute buffer stock at an assembly plant is dangerously thin for a JIT delivery program — anything less than 2 hours of buffer for a 500+ mile lane is an organizational risk management failure
+- If the carrier has a history of on-time delivery for this lane (check their scorecard), this is an anomaly, not a pattern — that context helps in both the carrier conversation and the GM chargeback negotiation
+- Check whether the carrier experienced any en-route delays (weather, traffic, mechanical) that explain the 11:42 arrival. A documented en-route delay is a mitigating factor even though the carrier isn't technically liable.
+
+**Documentation Required:**
+- BOL showing delivery date without time window
+- Carrier rate confirmation showing "by end of day Tuesday"
+- GM's JIT scheduling system printout showing the 04:00–06:00 delivery window
+- GM's line-down notification and production stoppage report
+- GM's chargeback notice with detailed cost calculation
+- Carrier's delivery receipt showing 11:42 arrival and unloading
+- Carrier's ELD data showing en-route trip timeline
+- Internal corrective action report documenting the communication gap
+- Updated BOL and rate confirmation templates with JIT delivery window fields
+- Negotiated chargeback settlement agreement with GM
+- Carrier on-time performance scorecard for the lane (prior 12 months)
+
+**Resolution Timeline:**
+- Hours 0–4: Immediate crisis management — emergency unloading at GM, line restarted
+- Days 1–3: Root cause analysis, carrier conversation, GM chargeback received
+- Days 3–14: GM chargeback negotiation, internal corrective action drafted
+- Days 14–30: Corrective action implemented (BOL/rate confirmation process updates)
+- Days 30–45: GM chargeback settlement
+- Days 30–60: Buffer strategy and carrier-of-last-resort arrangement implemented
+- Ongoing: Monthly review of JIT delivery performance for all assembly plant lanes
+
+---
+
+## Cross-Cutting Lessons
+
+The edge cases above share several themes that experienced exception managers internalize:
+
+1. **Documentation at the moment of discovery is irreplaceable.** Photos, data downloads, witness statements, and physical evidence degrade or disappear within hours. The first responder's instinct should be to document, not to fix.
+
+2. **Separate the immediate crisis from the claim.** Getting the customer their product, containing the spill, or keeping the production line running is always the first priority. The claim can be filed for months afterward; the commercial or safety crisis cannot wait.
+
+3. **Liability is rarely 100% on one party.** Most complex exceptions involve shared fault — a shipper who didn't communicate, a carrier who didn't secure, a broker who didn't pay, a consignee who didn't inspect. Expert resolution is about finding the right allocation, not proving absolute fault.
+
+4. **Escalate through data, not emotion.** "Your driver broke our product" gets denied. "We have a pattern of 14 shortage claims correlating to your Atlanta terminal's second shift" gets investigated.
+
+5. **The carrier's front-line customer service sees the same portal you do.** For any exception involving real money or real urgency, go directly to the carrier's operations team, sales representative, or claims director. The 800-number is for routine inquiries, not for $200K exposures.
+
+6. **Contracts and tariffs are the battlefield.** Every surcharge dispute, every consequential damages claim, and every liability allocation ultimately comes down to what was written, what was communicated, and what was incorporated by reference. Read the tariff. Read the contract. Know what your counterparty actually agreed to.
+
+7. **Time is the most expensive variable.** Every day a perishable shipment sits at a carrier's yard, every hour an assembly line is down, every week a customs hold persists — these accrue costs that dwarf the underlying product value. Speed of resolution is not just a service metric; it's a financial imperative.
diff --git a/web-app/public/skills/m365-agents-dotnet/SKILL.md b/web-app/public/skills/m365-agents-dotnet/SKILL.md
index eb93c7eb..01b1885f 100644
--- a/web-app/public/skills/m365-agents-dotnet/SKILL.md
+++ b/web-app/public/skills/m365-agents-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-dotnet
-description: "|"
+description: |
Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "Microsoft.Agents", "AddAgentApplicationOptions", "AgentApplication", "AddAgentAspNetAuthentication", "Copilot Studio client", "IAgentHttpAdapter".
package: Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Authentication.Msal, Microsoft.Agents.CopilotStudio.Client
risk: unknown
diff --git a/web-app/public/skills/m365-agents-py/SKILL.md b/web-app/public/skills/m365-agents-py/SKILL.md
index 0583cd23..3ec3bbdf 100644
--- a/web-app/public/skills/m365-agents-py/SKILL.md
+++ b/web-app/public/skills/m365-agents-py/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-py
-description: "|"
+description: |
Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "microsoft_agents", "AgentApplication", "start_agent_process", "TurnContext", "Copilot Studio client", "CloudAdapter".
package: microsoft-agents-hosting-core, microsoft-agents-hosting-aiohttp, microsoft-agents-activity, microsoft-agents-authentication-msal, microsoft-agents-copilotstudio-client
risk: unknown
diff --git a/web-app/public/skills/m365-agents-ts/SKILL.md b/web-app/public/skills/m365-agents-ts/SKILL.md
index f62cadf7..b6ec66fe 100644
--- a/web-app/public/skills/m365-agents-ts/SKILL.md
+++ b/web-app/public/skills/m365-agents-ts/SKILL.md
@@ -1,6 +1,6 @@
---
name: m365-agents-ts
-description: "|"
+description: |
Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: "Microsoft 365 Agents SDK", "@microsoft/agents-hosting", "AgentApplication", "startServer", "streamingResponse", "Copilot Studio client", "@microsoft/agents-copilotstudio-client".
package: "@microsoft/agents-hosting, @microsoft/agents-hosting-express, @microsoft/agents-activity, @microsoft/agents-copilotstudio-client"
risk: unknown
diff --git a/web-app/public/skills/malware-analyst/SKILL.md b/web-app/public/skills/malware-analyst/SKILL.md
index d6737995..4b447911 100644
--- a/web-app/public/skills/malware-analyst/SKILL.md
+++ b/web-app/public/skills/malware-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: malware-analyst
-description: "Expert malware analyst specializing in defensive malware research,"
+description: |
+ Expert malware analyst specializing in defensive malware research,
threat intelligence, and incident response. Masters sandbox analysis,
behavioral analysis, and malware family identification. Handles static/dynamic
analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,
diff --git a/web-app/public/skills/market-sizing-analysis/SKILL.md b/web-app/public/skills/market-sizing-analysis/SKILL.md
index 0768dcd3..3ddc7dd0 100644
--- a/web-app/public/skills/market-sizing-analysis/SKILL.md
+++ b/web-app/public/skills/market-sizing-analysis/SKILL.md
@@ -1,6 +1,7 @@
---
name: market-sizing-analysis
-description: "This skill should be used when the user asks to \\\"calculate TAM\\\","
+description: |
+ This skill should be used when the user asks to \\\"calculate TAM\\\",
"determine SAM", "estimate SOM", "size the market", "calculate market
opportunity", "what's the total addressable market", or requests market sizing
analysis for a startup or business opportunity.
diff --git a/web-app/public/skills/mermaid-expert/SKILL.md b/web-app/public/skills/mermaid-expert/SKILL.md
index 424f298c..6e328913 100644
--- a/web-app/public/skills/mermaid-expert/SKILL.md
+++ b/web-app/public/skills/mermaid-expert/SKILL.md
@@ -1,6 +1,7 @@
---
name: mermaid-expert
-description: "Create Mermaid diagrams for flowcharts, sequences, ERDs, and"
+description: |
+ Create Mermaid diagrams for flowcharts, sequences, ERDs, and
architectures. Masters syntax for all diagram types and styling. Use
PROACTIVELY for visual documentation, system diagrams, or process flows.
metadata:
diff --git a/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md b/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
index e79459a7..d49dcee2 100644
--- a/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
+++ b/web-app/public/skills/microsoft-azure-webjobs-extensions-authentication-events-dotnet/SKILL.md
@@ -1,6 +1,6 @@
---
name: microsoft-azure-webjobs-extensions-authentication-events-dotnet
-description: "|"
+description: |
Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: "Authentication Events", "WebJobsAuthenticationEventsTrigger", "OnTokenIssuanceStart", "OnAttributeCollectionStart", "custom claims", "token enrichment", "Entra custom extension", "authentication extension".
risk: unknown
source: community
diff --git a/web-app/public/skills/minecraft-bukkit-pro/SKILL.md b/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
index e52acd91..f89b7668 100644
--- a/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
+++ b/web-app/public/skills/minecraft-bukkit-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: minecraft-bukkit-pro
-description: "Master Minecraft server plugin development with Bukkit, Spigot, and"
+description: |
+ Master Minecraft server plugin development with Bukkit, Spigot, and
Paper APIs. Specializes in event-driven architecture, command systems, world
manipulation, player management, and performance optimization. Use PROACTIVELY
for plugin architecture, gameplay mechanics, server-side features, or
diff --git a/web-app/public/skills/ml-engineer/SKILL.md b/web-app/public/skills/ml-engineer/SKILL.md
index f34b1020..4a816dc6 100644
--- a/web-app/public/skills/ml-engineer/SKILL.md
+++ b/web-app/public/skills/ml-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ml-engineer
-description: "Build production ML systems with PyTorch 2.x, TensorFlow, and"
+description: |
+ Build production ML systems with PyTorch 2.x, TensorFlow, and
modern ML frameworks. Implements model serving, feature engineering, A/B
testing, and monitoring. Use PROACTIVELY for ML model deployment, inference
optimization, or production ML infrastructure.
diff --git a/web-app/public/skills/mlops-engineer/SKILL.md b/web-app/public/skills/mlops-engineer/SKILL.md
index 97a59c63..511743e8 100644
--- a/web-app/public/skills/mlops-engineer/SKILL.md
+++ b/web-app/public/skills/mlops-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: mlops-engineer
-description: "Build comprehensive ML pipelines, experiment tracking, and model"
+description: |
+ Build comprehensive ML pipelines, experiment tracking, and model
registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated
training, deployment, and monitoring across cloud platforms. Use PROACTIVELY
for ML infrastructure, experiment management, or pipeline automation.
diff --git a/web-app/public/skills/mobile-developer/SKILL.md b/web-app/public/skills/mobile-developer/SKILL.md
index a347fb69..7c9de867 100644
--- a/web-app/public/skills/mobile-developer/SKILL.md
+++ b/web-app/public/skills/mobile-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: mobile-developer
-description: "Develop React Native, Flutter, or native mobile apps with modern"
+description: |
+ Develop React Native, Flutter, or native mobile apps with modern
architecture patterns. Masters cross-platform development, native
integrations, offline sync, and app store optimization. Use PROACTIVELY for
mobile features, cross-platform code, or app optimization.
diff --git a/web-app/public/skills/mobile-security-coder/SKILL.md b/web-app/public/skills/mobile-security-coder/SKILL.md
index 77e20219..d6756980 100644
--- a/web-app/public/skills/mobile-security-coder/SKILL.md
+++ b/web-app/public/skills/mobile-security-coder/SKILL.md
@@ -1,6 +1,7 @@
---
name: mobile-security-coder
-description: "Expert in secure mobile coding practices specializing in input"
+description: |
+ Expert in secure mobile coding practices specializing in input
validation, WebView security, and mobile-specific security patterns. Use
PROACTIVELY for mobile security implementations or mobile security code
reviews.
diff --git a/web-app/public/skills/network-engineer/SKILL.md b/web-app/public/skills/network-engineer/SKILL.md
index 3fc439d3..26cf7f66 100644
--- a/web-app/public/skills/network-engineer/SKILL.md
+++ b/web-app/public/skills/network-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: network-engineer
-description: "Expert network engineer specializing in modern cloud networking,"
+description: |
+ Expert network engineer specializing in modern cloud networking,
security architectures, and performance optimization. Masters multi-cloud
connectivity, service mesh, zero-trust networking, SSL/TLS, global load
balancing, and advanced troubleshooting. Handles CDN optimization, network
diff --git a/web-app/public/skills/observability-engineer/SKILL.md b/web-app/public/skills/observability-engineer/SKILL.md
index 6246773f..ac320312 100644
--- a/web-app/public/skills/observability-engineer/SKILL.md
+++ b/web-app/public/skills/observability-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: observability-engineer
-description: "Build production-ready monitoring, logging, and tracing systems."
+description: |
+ Build production-ready monitoring, logging, and tracing systems.
Implements comprehensive observability strategies, SLI/SLO management, and
incident response workflows. Use PROACTIVELY for monitoring infrastructure,
performance optimization, or production reliability.
diff --git a/web-app/public/skills/page-cro/SKILL.md b/web-app/public/skills/page-cro/SKILL.md
index cf1c1d80..bdb40688 100644
--- a/web-app/public/skills/page-cro/SKILL.md
+++ b/web-app/public/skills/page-cro/SKILL.md
@@ -1,6 +1,6 @@
---
name: page-cro
-description: ">"
+description: >
Analyze and optimize individual pages for conversion performance.
Use when the user wants to improve conversion rates, diagnose why a page
is underperforming, or increase the effectiveness of marketing pages
diff --git a/web-app/public/skills/payment-integration/SKILL.md b/web-app/public/skills/payment-integration/SKILL.md
index 5620721d..378ae43d 100644
--- a/web-app/public/skills/payment-integration/SKILL.md
+++ b/web-app/public/skills/payment-integration/SKILL.md
@@ -1,6 +1,7 @@
---
name: payment-integration
-description: "Integrate Stripe, PayPal, and payment processors. Handles checkout"
+description: |
+ Integrate Stripe, PayPal, and payment processors. Handles checkout
flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when
implementing payments, billing, or subscription features.
metadata:
diff --git a/web-app/public/skills/php-pro/SKILL.md b/web-app/public/skills/php-pro/SKILL.md
index 1bd59417..99fa90e7 100644
--- a/web-app/public/skills/php-pro/SKILL.md
+++ b/web-app/public/skills/php-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: php-pro
-description: "Write idiomatic PHP code with generators, iterators, SPL data"
+description: |
+ Write idiomatic PHP code with generators, iterators, SPL data
structures, and modern OOP features. Use PROACTIVELY for high-performance PHP
applications.
metadata:
diff --git a/web-app/public/skills/posix-shell-pro/SKILL.md b/web-app/public/skills/posix-shell-pro/SKILL.md
index 6e248286..b6c7824a 100644
--- a/web-app/public/skills/posix-shell-pro/SKILL.md
+++ b/web-app/public/skills/posix-shell-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: posix-shell-pro
-description: "Expert in strict POSIX sh scripting for maximum portability across"
+description: |
+ Expert in strict POSIX sh scripting for maximum portability across
Unix-like systems. Specializes in shell scripts that run on any
POSIX-compliant shell (dash, ash, sh, bash --posix).
metadata:
diff --git a/web-app/public/skills/production-scheduling/SKILL.md b/web-app/public/skills/production-scheduling/SKILL.md
new file mode 100644
index 00000000..02cd702d
--- /dev/null
+++ b/web-app/public/skills/production-scheduling/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: production-scheduling
+description: >
+ Codified expertise for production scheduling, job sequencing, line balancing,
+ changeover optimisation, and bottleneck resolution in discrete and batch
+ manufacturing. Informed by production schedulers with 15+ years experience.
+ Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response
+ frameworks, and ERP/MES interaction patterns. Use when scheduling production,
+ resolving bottlenecks, optimising changeovers, responding to disruptions,
+ or balancing manufacturing lines.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🏭"
+---
+
+## When to Use
+
+Use this skill when planning manufacturing operations, sequencing jobs to minimize changeover times, balancing production lines, resolving factory bottlenecks, or responding to unexpected equipment downtime and supply disruptions.
+
+# Production Scheduling
+
+## Role and Context
+
+You are a senior production scheduler at a discrete and batch manufacturing facility operating 3–8 production lines with 50–300 direct-labour headcount per shift. You manage job sequencing, line balancing, changeover optimization, and disruption response across work centres that include machining, assembly, finishing, and packaging. Your systems include an ERP (SAP PP, Oracle Manufacturing, or Epicor), a finite-capacity scheduling tool (Preactor, PlanetTogether, or Opcenter APS), an MES for shop floor execution and real-time reporting, and a CMMS for maintenance coordination. You sit between production management (which owns output targets and headcount), planning (which releases work orders from MRP), quality (which gates product release), and maintenance (which owns equipment availability). Your job is to translate a set of work orders with due dates, routings, and BOMs into a minute-by-minute execution sequence that maximises throughput at the constraint while meeting customer delivery commitments, labour rules, and quality requirements.
+
+## Core Knowledge
+
+### Scheduling Fundamentals
+
+**Forward vs. backward scheduling:** Forward scheduling starts from material availability date and schedules operations sequentially to find the earliest completion date. Backward scheduling starts from the customer due date and works backward to find the latest permissible start date. In practice, use backward scheduling as the default to preserve flexibility and minimise WIP, then switch to forward scheduling when the backward pass reveals that the latest start date is already in the past — that work order is already late-starting and needs to be expedited from today forward.
+
+**Finite vs. infinite capacity:** MRP runs infinite-capacity planning — it assumes every work centre has unlimited capacity and flags overloads for the scheduler to resolve manually. Finite-capacity scheduling (FCS) respects actual resource availability: machine count, shift patterns, maintenance windows, and tooling constraints. Never trust an MRP-generated schedule as executable without running it through finite-capacity logic. MRP tells you _what_ needs to be made; FCS tells you _when_ it can actually be made.
+
+**Drum-Buffer-Rope (DBR) and Theory of Constraints:** The drum is the constraint resource — the work centre with the least excess capacity relative to demand. The buffer is a time buffer (not inventory buffer) protecting the constraint from upstream starvation. The rope is the release mechanism that limits new work into the system to the constraint's processing rate. Identify the constraint by comparing load hours to available hours per work centre; the one with the highest utilisation ratio (>85%) is your drum. Subordinate every other scheduling decision to keeping the drum fed and running. A minute lost at the constraint is a minute lost for the entire plant; a minute lost at a non-constraint costs nothing if buffer time absorbs it.
+
+**JIT sequencing:** In mixed-model assembly environments, level the production sequence to minimise variation in component consumption rates. Use heijunka logic: if you produce models A, B, and C in a 3:2:1 ratio per shift, the ideal sequence is A-B-A-C-A-B, not AAA-BB-C. Levelled sequencing smooths upstream demand, reduces component safety stock, and prevents the "end-of-shift crunch" where the hardest jobs get pushed to the last hour.
+
+**Where MRP breaks down:** MRP assumes fixed lead times, infinite capacity, and perfect BOM accuracy. It fails when (a) lead times are queue-dependent and compress under light load or expand under heavy load, (b) multiple work orders compete for the same constrained resource, (c) setup times are sequence-dependent, or (d) yield losses create variable output from fixed input. Schedulers must compensate for all four.
+
+### Changeover Optimisation
+
+**SMED methodology (Single-Minute Exchange of Die):** Shigeo Shingo's framework divides setup activities into external (can be done while the machine is still running the previous job) and internal (must be done with the machine stopped). Phase 1: document the current setup and classify every element as internal or external. Phase 2: convert internal elements to external wherever possible (pre-staging tools, pre-heating moulds, pre-mixing materials). Phase 3: streamline remaining internal elements (quick-release clamps, standardised die heights, colour-coded connections). Phase 4: eliminate adjustments through poka-yoke and first-piece verification jigs. Typical results: 40–60% setup time reduction from Phase 1–2 alone.
+
+**Colour/size sequencing:** In painting, coating, printing, and textile operations, sequence jobs from light to dark, small to large, or simple to complex to minimise cleaning between runs. A light-to-dark paint sequence might need only a 5-minute flush; dark-to-light requires a 30-minute full-purge. Capture these sequence-dependent setup times in a setup matrix and feed it to the scheduling algorithm.
+
+**Campaign vs. mixed-model scheduling:** Campaign scheduling groups all jobs of the same product family into a single run, minimising total changeovers but increasing WIP and lead times. Mixed-model scheduling interleaves products to reduce lead times and WIP but incurs more changeovers. The right balance depends on the changeover-cost-to-carrying-cost ratio. When changeovers are long and expensive (>60 minutes, >$500 in scrap and lost output), lean toward campaigns. When changeovers are fast (<15 minutes) or when customer order profiles demand short lead times, lean toward mixed-model.
+
+**Changeover cost vs. inventory carrying cost vs. delivery tradeoff:** Every scheduling decision involves this three-way tension. Longer campaigns reduce changeover cost but increase cycle stock and risk missing due dates for non-campaign products. Shorter campaigns improve delivery responsiveness but increase changeover frequency. The economic crossover point is where marginal changeover cost equals marginal carrying cost per unit of additional cycle stock. Compute it; don't guess.
+
+### Bottleneck Management
+
+**Identifying the true constraint vs. where WIP piles up:** WIP accumulation in front of a work centre does not necessarily mean that work centre is the constraint. WIP can pile up because the upstream work centre is batch-dumping, because a shared resource (crane, forklift, inspector) creates an artificial queue, or because a scheduling rule creates starvation downstream. The true constraint is the resource with the highest ratio of required hours to available hours. Verify by checking: if you added one hour of capacity at this work centre, would plant output increase? If yes, it is the constraint.
+
+**Buffer management:** In DBR, the time buffer is typically 50% of the production lead time for the constraint operation. Monitor buffer penetration: green zone (buffer consumed < 33%) means the constraint is well-protected; yellow zone (33–67%) triggers expediting of late-arriving upstream work; red zone (>67%) triggers immediate management attention and possible overtime at upstream operations. Buffer penetration trends over weeks reveal chronic problems: persistent yellow means upstream reliability is degrading.
+
+**Subordination principle:** Non-constraint resources should be scheduled to serve the constraint, not to maximise their own utilisation. Running a non-constraint at 100% utilisation when the constraint operates at 85% creates excess WIP with no throughput gain. Deliberately schedule idle time at non-constraints to match the constraint's consumption rate.
+
+**Detecting shifting bottlenecks:** The constraint can move between work centres as product mix changes, as equipment degrades, or as staffing shifts. A work centre that is the bottleneck on day shift (running high-setup products) may not be the bottleneck on night shift (running long-run products). Monitor utilisation ratios weekly by product mix. When the constraint shifts, the entire scheduling logic must shift with it — the new drum dictates the tempo.
+
+### Disruption Response
+
+**Machine breakdowns:** Immediate actions: (1) assess repair time estimate with maintenance, (2) determine if the broken machine is the constraint, (3) if constraint, calculate throughput loss per hour and activate the contingency plan — overtime on alternate equipment, subcontracting, or re-sequencing to prioritise highest-margin jobs. If not the constraint, assess buffer penetration — if buffer is green, do nothing to the schedule; if yellow or red, expedite upstream work to alternate routings.
+
+**Material shortages:** Check substitute materials, alternate BOMs, and partial-build options. If a component is short, can you build sub-assemblies to the point of the missing component and complete later (kitting strategy)? Escalate to purchasing for expedited delivery. Re-sequence the schedule to pull forward jobs that do not require the short material, keeping the constraint running.
+
+**Quality holds:** When a batch is placed on quality hold, it is invisible to the schedule — it cannot ship and it cannot be consumed downstream. Immediately re-run the schedule excluding held inventory. If the held batch was feeding a customer commitment, assess alternative sources: safety stock, in-process inventory from another work order, or expedited production of a replacement batch.
+
+**Absenteeism:** With certified operator requirements, one absent operator can disable an entire line. Maintain a cross-training matrix showing which operators are certified on which equipment. When absenteeism occurs, first check whether the missing operator runs the constraint — if so, reassign the best-qualified backup. If the missing operator runs a non-constraint, assess whether buffer time absorbs the delay before pulling a backup from another area.
+
+**Re-sequencing framework:** When disruption hits, apply this priority logic: (1) protect constraint uptime above all else, (2) protect customer commitments in order of customer tier and penalty exposure, (3) minimise total changeover cost of the new sequence, (4) level labour load across remaining available operators. Re-sequence, communicate the new schedule within 30 minutes, and lock it for at least 4 hours before allowing further changes.
+
+### Labour Management
+
+**Shift patterns:** Common patterns include 3×8 (three 8-hour shifts, 24/5 or 24/7), 2×12 (two 12-hour shifts, often with rotating days), and 4×10 (four 10-hour days for day-shift-only operations). Each pattern has different implications for overtime rules, handover quality, and fatigue-related error rates. 12-hour shifts reduce handovers but increase error rates in hours 10–12. Factor this into scheduling: do not put critical first-piece inspections or complex changeovers in the last 2 hours of a 12-hour shift.
+
+**Skill matrices:** Maintain a matrix of operator × work centre × certification level (trainee, qualified, expert). Scheduling feasibility depends on this matrix — a work order routed to a CNC lathe is infeasible if no qualified operator is on shift. The scheduling tool should carry labour as a constraint alongside machines.
+
+**Cross-training ROI:** Each additional operator certified on the constraint work centre reduces the probability of constraint starvation due to absenteeism. Quantify: if the constraint generates $5,000/hour in throughput and average absenteeism is 8%, having only 2 qualified operators vs. 4 qualified operators changes the expected throughput loss by $200K+/year.
+
+**Union rules and overtime:** Many manufacturing environments have contractual constraints on overtime assignment (by seniority), mandatory rest periods between shifts (typically 8–10 hours), and restrictions on temporary reassignment across departments. These are hard constraints that the scheduling algorithm must respect. Violating a union rule can trigger a grievance that costs far more than the production it was meant to save.
+
+### OEE — Overall Equipment Effectiveness
+
+**Calculation:** OEE = Availability × Performance × Quality. Availability = (Planned Production Time − Downtime) / Planned Production Time. Performance = (Ideal Cycle Time × Total Pieces) / Operating Time. Quality = Good Pieces / Total Pieces. World-class OEE is 85%+; typical discrete manufacturing runs 55–65%.
+
+**Planned vs. unplanned downtime:** Planned downtime (scheduled maintenance, changeovers, breaks) is excluded from the Availability denominator in some OEE standards and included in others. Use TEEP (Total Effective Equipment Performance) when you need to compare across plants or justify capital expansion — TEEP includes all calendar time.
+
+**Availability losses:** Breakdowns and unplanned stops. Address with preventive maintenance, predictive maintenance (vibration analysis, thermal imaging), and TPM operator-level daily checks. Target: unplanned downtime < 5% of scheduled time.
+
+**Performance losses:** Speed losses and micro-stops. A machine rated at 100 parts/hour running at 85 parts/hour has a 15% performance loss. Common causes: material feed inconsistencies, worn tooling, sensor false-triggers, and operator hesitation. Track actual cycle time vs. standard cycle time per job.
+
+**Quality losses:** Scrap and rework. First-pass yield below 95% on a constraint operation directly reduces effective capacity. Prioritise quality improvement at the constraint — a 2% yield improvement at the constraint delivers the same throughput gain as a 2% capacity expansion.
+
+### ERP/MES Interaction Patterns
+
+**SAP PP / Oracle Manufacturing production planning flow:** Demand enters as sales orders or forecast consumption, drives MPS (Master Production Schedule), which explodes through MRP into planned orders by work centre with material requirements. The scheduler converts planned orders into production orders, sequences them, and releases to the shop floor via MES. Feedback flows from MES (operation confirmations, scrap reporting, labour booking) back to ERP to update order status and inventory.
+
+**Work order management:** A work order carries the routing (sequence of operations with work centres, setup times, and run times), the BOM (components required), and the due date. The scheduler's job is to assign each operation to a specific time slot on a specific resource, respecting resource capacity, material availability, and dependency constraints (operation 20 cannot start until operation 10 is complete).
+
+**Shop floor reporting and plan-vs-reality gap:** MES captures actual start/end times, actual quantities produced, scrap counts, and downtime reasons. The gap between the schedule and MES actuals is the "plan adherence" metric. Healthy plan adherence is > 90% of jobs starting within ±1 hour of scheduled start. Persistent gaps indicate that either the scheduling parameters (setup times, run rates, yield factors) are wrong or that the shop floor is not following the sequence.
+
+**Closing the loop:** Every shift, compare scheduled vs. actual at the operation level. Update the schedule with actuals, re-sequence the remaining horizon, and publish the updated schedule. This "rolling re-plan" cadence keeps the schedule realistic rather than aspirational. The worst failure mode is a schedule that diverges from reality and becomes ignored by the shop floor — once operators stop trusting the schedule, it ceases to function.
+
+## Decision Frameworks
+
+### Job Priority Sequencing
+
+When multiple jobs compete for the same resource, apply this decision tree:
+
+1. **Is any job past-due or will miss its due date without immediate processing?** → Schedule past-due jobs first, ordered by customer penalty exposure (contractual penalties > reputational damage > internal KPI impact).
+2. **Are any jobs feeding the constraint and the constraint buffer is in yellow or red zone?** → Schedule constraint-feeding jobs next to prevent constraint starvation.
+3. **Among remaining jobs, apply the dispatching rule appropriate to the product mix:**
+ - High-variety, short-run: use **Earliest Due Date (EDD)** to minimise maximum lateness.
+ - Long-run, few products: use **Shortest Processing Time (SPT)** to minimise average flow time and WIP.
+ - Mixed, with sequence-dependent setups: use **setup-aware EDD** — EDD with a setup-time lookahead that swaps adjacent jobs when a swap saves >30 minutes of setup without causing a due date miss.
+4. **Tie-breaker:** Higher customer tier wins. If same tier, higher margin job wins.
+
+### Changeover Sequence Optimisation
+
+1. **Build the setup matrix:** For each pair of products (A→B, B→A, A→C, etc.), record the changeover time in minutes and the changeover cost (labour + scrap + lost output).
+2. **Identify mandatory sequence constraints:** Some transitions are prohibited (allergen cross-contamination in food, hazardous material sequencing in chemical). These are hard constraints, not optimisable.
+3. **Apply nearest-neighbour heuristic as baseline:** From the current product, select the next product with the smallest changeover time. This gives a feasible starting sequence.
+4. **Improve with 2-opt swaps:** Swap pairs of adjacent jobs; keep the swap if total changeover time decreases without violating due dates.
+5. **Validate against due dates:** Run the optimised sequence through the schedule. If any job misses its due date, insert it earlier even if it increases total changeover time. Due date compliance trumps changeover optimisation.
+
+### Disruption Re-Sequencing
+
+When a disruption invalidates the current schedule:
+
+1. **Assess impact window:** How many hours/shifts is the disrupted resource unavailable? Is it the constraint?
+2. **Freeze committed work:** Jobs already in process or within 2 hours of start should not be moved unless physically impossible.
+3. **Re-sequence remaining jobs:** Apply the job priority framework above to all unfrozen jobs, using updated resource availability.
+4. **Communicate within 30 minutes:** Publish the revised schedule to all affected work centres, supervisors, and material handlers.
+5. **Set a stability lock:** No further schedule changes for at least 4 hours (or until next shift start) unless a new disruption occurs. Constant re-sequencing creates more chaos than the original disruption.
+
+### Bottleneck Identification
+
+1. **Pull utilisation reports** for all work centres over the trailing 2 weeks (by shift, not averaged).
+2. **Rank by utilisation ratio** (load hours / available hours). The top work centre is the suspected constraint.
+3. **Verify causally:** Would adding one hour of capacity at this work centre increase total plant output? If the work centre downstream of it is always starved when this one is down, the answer is yes.
+4. **Check for shifting patterns:** If the top-ranked work centre changes between shifts or between weeks, you have a shifting bottleneck driven by product mix. In this case, schedule the constraint _for each shift_ based on that shift's product mix, not on a weekly average.
+5. **Distinguish from artificial constraints:** A work centre that appears overloaded because upstream batch-dumps WIP into it is not a true constraint — it is a victim of poor upstream scheduling. Fix the upstream release rate before adding capacity to the victim.
+
+## Key Edge Cases
+
+Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md).
+
+1. **Shifting bottleneck mid-shift:** Product mix change moves the constraint from machining to assembly during the shift. The schedule that was optimal at 6:00 AM is wrong by 10:00 AM. Requires real-time utilisation monitoring and intra-shift re-sequencing authority.
+
+2. **Certified operator absent for regulated process:** An FDA-regulated coating operation requires a specific operator certification. The only certified night-shift operator calls in sick. The line cannot legally run. Activate the cross-training matrix, call in a certified day-shift operator on overtime if permitted, or shut down the regulated operation and re-route non-regulated work.
+
+3. **Competing rush orders from tier-1 customers:** Two top-tier automotive OEM customers both demand expedited delivery. Satisfying one delays the other. Requires commercial decision input — which customer relationship carries higher penalty exposure or strategic value? The scheduler identifies the tradeoff; management decides.
+
+4. **MRP phantom demand from BOM error:** A BOM listing error causes MRP to generate planned orders for a component that is not actually consumed. The scheduler sees a work order with no real demand behind it. Detect by cross-referencing MRP-generated demand against actual sales orders and forecast consumption. Flag and hold — do not schedule phantom demand.
+
+5. **Quality hold on WIP affecting downstream:** A paint defect is discovered on 200 partially complete assemblies. These were scheduled to feed the final assembly constraint tomorrow. The constraint will starve unless replacement WIP is expedited from an earlier stage or alternate routing is used.
+
+6. **Equipment breakdown at the constraint:** The single most damaging disruption. Every minute of constraint downtime equals lost throughput for the entire plant. Trigger immediate maintenance response, activate alternate routing if available, and notify customers whose orders are at risk.
+
+7. **Supplier delivers wrong material mid-run:** A batch of steel arrives with the wrong alloy specification. Jobs already kitted with this material cannot proceed. Quarantine the material, re-sequence to pull forward jobs using a different alloy, and escalate to purchasing for emergency replacement.
+
+8. **Customer order change after production started:** The customer modifies quantity or specification after work is in process. Assess sunk cost of work already completed, rework feasibility, and impact on other jobs sharing the same resource. A partial-completion hold may be cheaper than scrapping and restarting.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Daily schedule publication:** Clear, structured, no ambiguity. Job sequence, start times, line assignments, operator assignments. Use table format. The shop floor does not read paragraphs.
+- **Schedule change notification:** Urgent header, reason for change, specific jobs affected, new sequence and timing. "Effective immediately" or "effective at [time]."
+- **Disruption escalation:** Lead with impact magnitude (hours of constraint time lost, number of customer orders at risk), then cause, then proposed response, then decision needed from management.
+- **Overtime request:** Quantify the business case — cost of overtime vs. cost of missed deliveries. Include union rule compliance. "Requesting 4 hours voluntary OT for CNC operators (3 personnel) on Saturday AM. Cost: $1,200. At-risk revenue without OT: $45,000."
+- **Customer delivery impact notice:** Never surprise the customer. As soon as a delay is likely, notify with the new estimated date, root cause (without blaming internal teams), and recovery plan. "Due to an equipment issue, order #12345 will ship [new date] vs. the original [old date]. We are running overtime to minimise the delay."
+- **Maintenance coordination:** Specific window requested, business justification for the timing, impact if maintenance is deferred. "Requesting PM window on Line 3, Tuesday 06:00–10:00. This avoids the Thursday changeover peak. Deferring past Friday risks an unplanned breakdown — vibration readings are trending into the caution zone."
+
+Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------- |
+| Constraint work centre down > 30 minutes unplanned | Alert production manager + maintenance manager | Immediate |
+| Plan adherence drops below 80% for a shift | Root cause analysis with shift supervisor | Within 4 hours |
+| Customer order projected to miss committed ship date | Notify sales and customer service with revised ETA | Within 2 hours of detection |
+| Overtime requirement exceeds weekly budget by > 20% | Escalate to plant manager with cost-benefit analysis | Within 1 business day |
+| OEE at constraint drops below 65% for 3 consecutive shifts | Trigger focused improvement event (maintenance + engineering + scheduling) | Within 1 week |
+| Quality yield at constraint drops below 93% | Joint review with quality engineering | Within 24 hours |
+| MRP-generated load exceeds finite capacity by > 15% for the upcoming week | Capacity meeting with planning and production management | 2 days before the overloaded week |
+
+### Escalation Chain
+
+Level 1 (Production Scheduler) → Level 2 (Production Manager / Shift Superintendent, 30 min for constraint issues, 4 hours for non-constraint) → Level 3 (Plant Manager, 2 hours for customer-impacting issues) → Level 4 (VP Operations, same day for multi-customer impact or safety-related schedule changes)
+
+## Performance Indicators
+
+Track per shift and trend weekly:
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------------- | ------------------ | -------------- |
+| Schedule adherence (jobs started within ±1 hour) | > 90% | < 80% |
+| On-time delivery (to customer commit date) | > 95% | < 90% |
+| OEE at constraint | > 75% | < 65% |
+| Changeover time vs. standard | < 110% of standard | > 130% |
+| WIP days (total WIP value / daily COGS) | < 5 days | > 8 days |
+| Constraint utilisation (actual producing / available) | > 85% | < 75% |
+| First-pass yield at constraint | > 97% | < 93% |
+| Unplanned downtime (% of scheduled time) | < 5% | > 10% |
+| Labour utilisation (direct hours / available hours) | 80–90% | < 70% or > 95% |
+
+## Additional Resources
+
+- For detailed decision frameworks, scheduling algorithms, and optimisation methodologies, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design or adjust production schedules and constraint‑focused execution plans**:
+
+- Sequencing jobs, balancing lines, and optimising changeovers in discrete or batch manufacturing.
+- Responding to disruptions (machine breakdowns, shortages, quality holds, absenteeism) while protecting the bottleneck and customer commitments.
+- Building scheduling rules, KPIs, and communication patterns between planning, production, maintenance, and quality teams.
diff --git a/web-app/public/skills/production-scheduling/references/communication-templates.md b/web-app/public/skills/production-scheduling/references/communication-templates.md
new file mode 100644
index 00000000..827f6877
--- /dev/null
+++ b/web-app/public/skills/production-scheduling/references/communication-templates.md
@@ -0,0 +1,503 @@
+# Communication Templates — Production Scheduling
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing production scheduling communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and purpose. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [Production Schedule Publication](#1-production-schedule-publication)
+2. [Schedule Change Notification](#2-schedule-change-notification)
+3. [Disruption Alert](#3-disruption-alert)
+4. [Overtime Request](#4-overtime-request)
+5. [Customer Delivery Impact Notice](#5-customer-delivery-impact-notice)
+6. [Maintenance Coordination Request](#6-maintenance-coordination-request)
+7. [Quality Hold Notification](#7-quality-hold-notification)
+8. [Capacity Constraint Escalation](#8-capacity-constraint-escalation)
+9. [New Product Trial Run Request](#9-new-product-trial-run-request)
+10. [Cross-Functional Priority Alignment](#10-cross-functional-priority-alignment)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{date}}` | Date of communication | `2025-09-15` |
+| `{{shift}}` | Shift identifier | `Day Shift (06:00–14:00)` |
+| `{{line_id}}` | Production line identifier | `Line 3 — CNC Machining Cell` |
+| `{{work_order}}` | Work order number | `WO-2025-04823` |
+| `{{product}}` | Product name/number | `Valve Body Assembly VB-220` |
+| `{{customer}}` | Customer name | `Apex Automotive GmbH` |
+| `{{customer_po}}` | Customer purchase order | `APX-PO-88412` |
+| `{{qty}}` | Quantity | `500 units` |
+| `{{due_date}}` | Customer due date | `2025-09-22` |
+| `{{revised_date}}` | Revised delivery date | `2025-09-25` |
+| `{{scheduler_name}}` | Scheduler name | `Dave Morrison` |
+| `{{scheduler_title}}` | Scheduler title | `Senior Production Scheduler` |
+| `{{scheduler_email}}` | Scheduler email | `d.morrison@mfgco.com` |
+| `{{scheduler_phone}}` | Scheduler phone | `(513) 555-0147` |
+| `{{plant}}` | Plant name/location | `Cincinnati Plant — Building 2` |
+| `{{constraint_wc}}` | Constraint work centre | `CNC Horizontal Boring — WC 420` |
+| `{{oee_value}}` | OEE percentage | `72%` |
+| `{{downtime_hrs}}` | Downtime hours | `4.5 hours` |
+| `{{changeover_time}}` | Changeover duration | `45 minutes` |
+| `{{operator_name}}` | Operator name | `J. Rodriguez` |
+| `{{supervisor_name}}` | Shift supervisor | `Karen Phillips` |
+| `{{maintenance_lead}}` | Maintenance lead | `Tom Becker` |
+| `{{quality_lead}}` | Quality lead | `Dr. Sarah Chen` |
+
+---
+
+## 1. Production Schedule Publication
+
+**Audience:** Shift supervisors, operators, material handlers, quality inspectors
+**Frequency:** Published at shift start; updated only if disruption requires re-sequencing
+**Format:** Table-driven, no paragraphs. Shop floor reads tables, not prose.
+**Delivery:** Printed and posted at each work centre + emailed to supervisors + displayed on MES screens
+
+---
+
+**Subject:** Production Schedule — {{plant}} — {{shift}} — {{date}}
+
+**Schedule published by:** {{scheduler_name}} at {{date}} {{time}}
+
+**Priority Legend:** 🔴 Past-due or critical | 🟡 At risk (CR < 1.0) | 🟢 On schedule
+
+| Seq | Work Order | Product | Qty | Start Time | End Time | Work Centre | Operator | Priority | Notes |
+|---|---|---|---|---|---|---|---|---|---|
+| 1 | {{work_order}} | {{product}} | {{qty}} | 06:00 | 08:30 | {{line_id}} | {{operator_name}} | 🔴 | Rush — customer line-down |
+| 2 | WO-2025-04824 | Housing H-340 | 200 | 08:45 | 11:15 | {{line_id}} | {{operator_name}} | 🟢 | Std changeover at 08:30 |
+| 3 | WO-2025-04826 | Bracket BR-110 | 350 | 11:30 | 14:00 | {{line_id}} | {{operator_name}} | 🟡 | Material confirm by 10:00 |
+
+**Changeover Summary:**
+- 08:30–08:45: Changeover WO-04823 → WO-04824 (tooling pre-staged at machine)
+- 11:15–11:30: Changeover WO-04824 → WO-04826 (fixture change, 15 min)
+
+**Material Status:**
+- WO-04823: All material staged ✅
+- WO-04824: All material staged ✅
+- WO-04826: Bracket raw material pending — confirm with stores by 10:00 ⚠️
+
+**Labour Notes:**
+- {{operator_name}} certified on all three jobs
+- Relief operator for 10:00 break: M. Thompson
+
+**Constraint Status:** {{constraint_wc}} — current OEE {{oee_value}}. Buffer status: GREEN.
+
+**Do not deviate from this sequence without scheduler approval.**
+
+---
+
+**Tone guidance:** Directive, not conversational. The schedule is an instruction, not a suggestion. Use clear times, no approximations. Flag risks with symbols that are visible at a glance. Include material and labour status because the most common schedule disruption is "I didn't have the material" or "nobody told me I was on this job."
+
+---
+
+## 2. Schedule Change Notification
+
+**Audience:** Shift supervisors, affected operators, material handlers
+**Trigger:** Any change to the published schedule during the frozen zone
+**Delivery:** In-person verbal confirmation + written (posted + emailed)
+
+---
+
+**Subject:** ⚠️ SCHEDULE CHANGE — {{line_id}} — Effective {{effective_time}}
+
+**Change issued by:** {{scheduler_name}} at {{date}} {{time}}
+**Approved by:** {{supervisor_name}} (Production Manager approval required for frozen-zone changes)
+
+**Reason for change:** {{change_reason}}
+
+**What changed:**
+
+| | Before | After |
+|---|---|---|
+| Job sequence at {{line_id}} | WO-04824 → WO-04826 | WO-04826 → WO-04824 |
+| WO-04826 start time | 11:30 | 08:45 |
+| WO-04824 start time | 08:45 | 11:30 |
+| Changeover | Tooling → Fixture (15 min) | Fixture → Tooling (20 min) |
+
+**Why:** {{detailed_reason}} — e.g., "WO-04826 material (bracket raw stock) arrived early. WO-04826 due date is 1 day earlier than WO-04824. Swapping sequence saves 5 minutes of changeover time and improves on-time delivery for both orders."
+
+**Impact on other work centres:** None — downstream operations unaffected.
+
+**Action required:**
+- Material handler: Re-stage WO-04826 material at {{line_id}} by 08:30.
+- Operator: Confirm fixture change procedure for WO-04826 with setup technician.
+
+**No further changes to this shift's schedule unless a new disruption occurs.**
+
+---
+
+**Tone guidance:** Authoritative but explanatory. The "why" is important because frequent unexplained changes erode shop floor trust in the schedule. Always include who approved the change (accountability). End with a stability commitment — "no further changes" — to prevent the shop floor from anticipating constant flux.
+
+---
+
+## 3. Disruption Alert
+
+**Audience:** Production manager, maintenance manager, shift supervisors, planning
+**Trigger:** Any unplanned event affecting the constraint or customer deliveries
+**Delivery:** Immediate — phone/radio for constraint events, email for non-constraint
+
+---
+
+**Subject:** 🔴 DISRUPTION ALERT — {{disruption_type}} at {{line_id}} — {{date}} {{time}}
+
+**Reported by:** {{scheduler_name}}
+**Severity:** {{severity}} (Critical / Major / Minor)
+
+**What happened:**
+{{disruption_description}}
+Example: "Hydraulic pump failure on CNC Horizontal Boring Mill (WC 420) at 09:15. Machine stopped mid-cycle on WO-04823 (defence contract valve body, $38,000 piece in machine). Maintenance assessment: pump replacement required, 6–8 hour repair estimated."
+
+**Impact:**
+- **Constraint affected:** Yes / No
+- **Estimated downtime:** {{downtime_hrs}}
+- **Throughput loss:** {{throughput_loss}} (e.g., "$4,800 — 6 hours × $800/hr constraint throughput")
+- **Customer orders at risk:** {{at_risk_orders}} (e.g., "3 orders totalling $220,000, due dates within 2 weeks")
+- **Current buffer status:** {{buffer_status}} (e.g., "Buffer was GREEN, will reach RED in 4 hours if not resolved")
+
+**Immediate actions taken:**
+1. Machine isolated. Maintenance on-site.
+2. Replacement pump ordered from OEM distributor — ETA {{pump_eta}}.
+3. In-machine part assessed: datum offsets preserved, part likely salvageable on restart.
+4. Queued jobs reviewed for alternate routing — 3 of 14 can run on vertical CNC.
+
+**Decision needed from management:**
+- Authorise Saturday overtime (8 hours, estimated cost ${{overtime_cost}}) to recover lost capacity? Y/N
+- Approve subcontracting for {{subcontract_jobs}} to external shop (cost ${{subcontract_cost}})? Y/N
+- Customer notification: approve revised delivery dates for {{at_risk_customers}}? Y/N
+
+**Next update:** {{next_update_time}} or when repair status changes.
+
+---
+
+**Tone guidance:** Lead with impact, not description. The production manager needs to know "how bad is this?" before "what exactly happened." Quantify everything in hours and dollars. Present decisions as explicit Y/N choices — do not leave it ambiguous. Set a next-update cadence so management isn't chasing you for information.
+
+---
+
+## 4. Overtime Request
+
+**Audience:** Production manager (approval), HR/payroll (processing), affected operators
+**Trigger:** Capacity shortfall that can be recovered with additional hours
+**Delivery:** Email with formal cost justification; verbal pre-approval for urgency
+
+---
+
+**Subject:** Overtime Request — {{line_id}} — {{date_range}}
+
+**Requested by:** {{scheduler_name}}
+**Date of request:** {{date}}
+
+**Business justification:**
+{{business_case}}
+Example: "Constraint work centre (CNC Boring, WC 420) lost 20 hours due to unplanned hydraulic failure on 9/15. Recovery requires Saturday overtime shift to process queued customer orders and prevent 3 delivery misses totalling $220,000 in at-risk revenue."
+
+**Overtime details:**
+
+| Item | Detail |
+|---|---|
+| Work centre | {{constraint_wc}} |
+| Date(s) | {{overtime_dates}} (e.g., Saturday 9/20, 06:00–14:00) |
+| Duration | {{overtime_hours}} hours |
+| Personnel required | {{personnel_count}} (e.g., 2 CNC operators + 1 setup tech) |
+| Personnel names | {{personnel_names}} (voluntary — confirmed availability) |
+| Estimated cost | ${{overtime_cost}} ({{hours}} hrs × ${{rate}}/hr × {{multiplier}} OT premium) |
+| Union compliance | ✅ Voluntary. Offered by seniority per CBA Article 14.3. 8-hour rest observed. |
+
+**Revenue at risk without overtime:** ${{revenue_at_risk}}
+**Cost-to-benefit ratio:** {{ratio}} (e.g., "$1,200 OT cost to protect $220,000 revenue = 183:1 ROI")
+
+**Orders recovered with overtime:**
+
+| Work Order | Customer | Due Date | Status Without OT | Status With OT |
+|---|---|---|---|---|
+| WO-04825 | {{customer}} | {{due_date}} | 2 days late | On time |
+| WO-04827 | Nexus Defense | 9/26 | 1 day late | On time |
+| WO-04829 | Summit Aero | 9/28 | On time (barely) | Comfortable margin |
+
+**Approval requested by:** {{approval_deadline}} (e.g., "Thursday 5:00 PM to allow operator notification per CBA 48-hour notice requirement")
+
+---
+
+**Tone guidance:** Treat overtime requests as business cases, not pleas. Quantify both the cost and the benefit. Include union compliance confirmation proactively — the production manager should not have to ask. Provide the approval deadline because overtime notification requirements are contractual, not flexible.
+
+---
+
+## 5. Customer Delivery Impact Notice
+
+**Audience:** Sales/account manager (internal), then customer
+**Trigger:** Any order projected to miss its committed delivery date
+**Delivery:** Internal first (email + phone to account manager), then customer (via account manager or directly)
+
+---
+
+**Internal Version (to Sales/Account Manager):**
+
+**Subject:** Delivery Impact — {{customer}} — Order {{customer_po}} — Revised ETA {{revised_date}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Summary:**
+Order {{customer_po}} for {{customer}} ({{qty}} of {{product}}, original commit date {{due_date}}) will ship {{delay_days}} days late. Revised delivery date: {{revised_date}}.
+
+**Root cause:** {{root_cause_internal}}
+Example: "Unplanned constraint downtime on 9/15 (hydraulic failure, 20 hours lost) consumed the schedule buffer. Recovery overtime approved but insufficient to fully close the gap for all affected orders."
+
+**Recovery actions in progress:**
+- Saturday overtime shift authorised (recovers 8 hours)
+- 3 lower-priority jobs subcontracted to reduce constraint queue (recovers 6 hours)
+- Remaining gap: 6 hours, which pushes {{customer_po}} delivery from {{due_date}} to {{revised_date}}
+
+**Contractual exposure:** {{penalty_info}}
+Example: "Customer A framework agreement includes $25,000/day late delivery penalty. 3-day delay = $75,000 exposure. Recommend proactive notification and negotiation."
+
+**Recommended customer message:** See external version below. Please review and send by {{notification_deadline}}, or let me know if you'd like to adjust the messaging.
+
+---
+
+**External Version (to Customer):**
+
+**Subject:** Delivery Update — Order {{customer_po}}
+
+Dear {{customer_contact}},
+
+I am writing to update you on the delivery timeline for your order {{customer_po}} ({{qty}} of {{product}}).
+
+Due to {{root_cause_external}} (e.g., "an equipment issue at our machining facility"), we are revising the delivery date from {{due_date}} to {{revised_date}}.
+
+We have taken the following actions to minimise the delay:
+- Authorised additional production shifts dedicated to your order
+- Re-prioritised your order to the front of the production queue
+- Assigned our senior machining team to ensure quality and speed
+
+We understand the impact this may have on your operations and sincerely regret the inconvenience. If the revised date presents difficulties, please let us know and we will explore every option to accelerate further.
+
+{{scheduler_name}} is available at {{scheduler_phone}} for any questions about the production status.
+
+Regards,
+{{account_manager_name}}
+{{account_manager_title}}
+{{our_company}}
+
+---
+
+**Tone guidance — internal:** Factual, quantified, includes penalty exposure. The account manager needs the full picture to make the right call on messaging.
+
+**Tone guidance — external:** Proactive (before the customer discovers the delay), accountable (acknowledge the impact), action-oriented (show what you're doing), no blame (do not name internal equipment or personnel). Never use "we apologise for any inconvenience" — that phrase signals insincerity. Instead, acknowledge the specific impact on their operations.
+
+---
+
+## 6. Maintenance Coordination Request
+
+**Audience:** Maintenance manager/planner
+**Trigger:** Scheduling a preventive maintenance window, or requesting priority on corrective maintenance
+**Delivery:** Email + calendar invite for planned; phone/radio + email for urgent
+
+---
+
+**Subject:** Maintenance Window Request — {{line_id}} — {{requested_date_range}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Request type:** Preventive Maintenance / Corrective Maintenance / Calibration
+
+**Equipment:** {{equipment_id}} (e.g., "600-ton Stamping Press #2, Asset Tag SP-602")
+**Work centre:** {{constraint_wc}}
+
+**Requested window:** {{pm_start}} to {{pm_end}} (e.g., "Saturday 9/20, 06:00–16:00, 10 hours")
+
+**Business justification for this timing:**
+{{timing_justification}}
+Example: "Saturday window avoids impacting the Week 39 production plan, which is loaded at 94% Mon–Fri. Vibration readings on SP-602 are trending into the caution zone (0.28 in/s, threshold is 0.30). Deferring beyond Saturday increases the risk of an unplanned breakdown during the peak Monday–Wednesday production window."
+
+**Impact if deferred:**
+- Probability of unplanned failure in next 2 weeks: {{failure_probability}} (e.g., "estimated 35% based on vibration trend and historical MTBF data")
+- Cost of unplanned failure: {{failure_cost}} (e.g., "$16,000 lost throughput + $5,000 emergency repair + potential die damage")
+- Production orders at risk: {{at_risk_orders}}
+
+**Production impact of performing the PM:**
+- Lost production during the PM window: {{lost_production}} (e.g., "0 — Saturday is non-scheduled overtime; if OT was planned, 8 hours of production displaced")
+- Recovery plan: {{recovery_plan}} (e.g., "displaced OT production moved to Friday evening shift extension")
+
+**Coordination requirements:**
+- Maintenance personnel: {{maintenance_personnel}} (e.g., "1 millwright + 1 electrician, 10 hours each")
+- Parts/materials: {{parts_needed}} (e.g., "hydraulic seal kit #HS-602-A, confirm available in stores")
+- Production support: {{production_support}} (e.g., "Operator needed for first 2 hours to assist with die removal and last 1 hour for test run")
+
+---
+
+**Tone guidance:** Collaborative, not adversarial. Scheduling and maintenance are allies, not opponents. Provide the business case for the timing (so maintenance understands why this window matters) and the risk assessment for deferral (so maintenance can prioritise appropriately). Include all logistics so maintenance can plan their work order without back-and-forth.
+
+---
+
+## 7. Quality Hold Notification
+
+**Audience:** Quality manager, production manager, affected work centre supervisors, planning
+**Trigger:** In-process quality issue requiring quarantine of WIP
+**Delivery:** Immediate email + verbal to quality and production managers
+
+---
+
+**Subject:** 🔴 QUALITY HOLD — {{product}} — Batch {{batch_id}} — {{qty_affected}} units
+
+**Issued by:** {{scheduler_name}} in coordination with {{quality_lead}}
+**Date/Time:** {{date}} {{time}}
+
+**Defect summary:** {{defect_description}}
+Example: "Dimensional defect on stamped chassis frames — hole pattern shifted 2mm from specification due to suspected die wear. Discovered at weld inspection station."
+
+**Scope of hold:**
+
+| Production Stage | Quantity Affected | Location | Status |
+|---|---|---|---|
+| Stamping (completed) | 80 units | Welding station queue | QUARANTINED |
+| Welding (completed) | 60 units | Paint queue staging | QUARANTINED |
+| Paint (completed) | 60 units | Final assembly staging | QUARANTINED |
+| **Total** | **200 units** | | |
+
+**Customer impact:**
+- Customer: {{customer}}
+- Order: {{customer_po}}, {{qty}} units due {{due_date}}
+- 60 painted frames were scheduled to feed final assembly (constraint) starting {{date}}.
+- Constraint will be short material for {{impact_duration}} unless rework or replacement is expedited.
+
+**Schedule impact:**
+- Final assembly (constraint) schedule revised: {{revised_schedule_summary}}
+- Alternate work pulled forward to keep constraint running: {{alternate_work}}
+- Estimated delivery impact: {{delivery_impact}}
+
+**Disposition pending from Quality:**
+- Rework feasibility assessment requested by {{rework_assessment_deadline}}
+- If reworkable: estimated rework time = {{rework_time}} per unit
+- If not reworkable: replacement production order required — estimated lead time {{replacement_lead_time}}
+
+**Immediate actions taken:**
+1. All affected WIP physically segregated and tagged
+2. Die #{{die_number}} removed from service for inspection
+3. Production schedule revised — constraint fed from alternate work orders
+4. Customer notification drafted (pending quality disposition)
+
+---
+
+## 8. Capacity Constraint Escalation
+
+**Audience:** Plant manager, planning manager, production manager
+**Trigger:** MRP-generated load exceeds finite capacity by >15% for the upcoming week
+**Delivery:** Email with supporting data, presented at weekly S&OP or production meeting
+
+---
+
+**Subject:** Capacity Overload Alert — {{constraint_wc}} — Week {{week_number}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+**Date:** {{date}}
+
+**Summary:**
+MRP-generated load for {{constraint_wc}} in Week {{week_number}} exceeds available capacity by {{overload_pct}}%. Without intervention, {{overload_hours}} hours of work cannot be scheduled, affecting {{affected_orders}} customer orders.
+
+**Capacity analysis:**
+
+| Item | Hours |
+|---|---|
+| Available capacity ({{shifts}} shifts × {{hours_per_shift}} hrs, less {{pm_hours}} hrs planned maintenance) | {{available_hours}} |
+| MRP-required load | {{required_hours}} |
+| Overload | {{overload_hours}} ({{overload_pct}}%) |
+
+**Options for resolution:**
+
+| Option | Capacity Recovered | Cost | Risk | Recommendation |
+|---|---|---|---|---|
+| Saturday overtime (1 shift) | {{ot_hours}} hrs | ${{ot_cost}} | Low — voluntary OT available | ✅ Recommended |
+| Defer {{defer_count}} lower-priority orders to Week {{week_number + 1}} | {{defer_hours}} hrs | $0 | Medium — delivery impact on deferred orders | Acceptable if customers agree |
+| Subcontract {{subcontract_ops}} | {{subcontract_hours}} hrs | ${{subcontract_cost}} | Medium — quality and lead time | Last resort |
+| Reduce constraint changeovers (campaign scheduling) | {{co_hours}} hrs | $0 | Low — requires schedule restructuring | ✅ Recommended in combination |
+
+**Recommended plan:** Combine overtime ({{ot_hours}} hrs) + changeover reduction ({{co_hours}} hrs) to close the gap. Total gap closed: {{total_recovered}} hrs. Remaining gap: {{remaining_gap}} hrs — address by deferring {{defer_count}} Tier-3 orders with customer agreement.
+
+**Decision needed by:** {{decision_deadline}} (to allow operator notification and material staging)
+
+---
+
+## 9. New Product Trial Run Request
+
+**Audience:** Production manager, engineering, quality, scheduling
+**Trigger:** NPI (new product introduction) requiring constraint time for trial runs
+**Delivery:** Email with formal request; presented at production planning meeting
+
+---
+
+**Subject:** NPI Trial Run Request — {{npi_product}} — {{requested_dates}}
+
+**From:** {{scheduler_name}} in coordination with {{engineering_lead}}
+
+**Product:** {{npi_product}} (e.g., "EV Battery Enclosure — Part #BE-4400")
+**Customer:** {{customer}}
+**Qualification deadline:** {{qualification_deadline}}
+
+**Trial run requirements:**
+
+| Trial # | Date | Constraint Time (nominal) | Buffered Time (planned) | Changeover | Total Window |
+|---|---|---|---|---|---|
+| 1 | {{trial_1_date}} | 8 hrs | 14 hrs | 4 hrs | 18 hrs |
+| 2 | {{trial_2_date}} | 8 hrs | 12 hrs | 4 hrs | 16 hrs |
+| 3 | {{trial_3_date}} | 8 hrs | 10 hrs | 2 hrs | 12 hrs |
+
+**Capacity impact:**
+- Current constraint utilisation: {{current_util}}%
+- With NPI trials: {{projected_util}}%
+- Buffer reduction: constraint buffer shrinks from {{current_buffer}} hrs to {{projected_buffer}} hrs per week
+
+**Proposed scheduling approach:**
+- Schedule trials on Friday PM / Saturday AM to contain overrun risk
+- {{buffer_hours}} hrs/week reserved as "trial buffer" — converts to regular production if trial is cancelled or completes early
+- Existing customer commitments are not moved to accommodate trials
+
+**Risk mitigation:**
+- Most experienced setup technician assigned to all trials
+- First-article inspection protocol defined with quality
+- Trial time estimates will be updated after each run for the next trial
+
+**Approval required from:** Production Manager (capacity impact) + Quality (trial protocol) + Engineering (trial plan)
+
+---
+
+## 10. Cross-Functional Priority Alignment
+
+**Audience:** Sales, planning, production, quality, finance
+**Trigger:** Competing priorities require alignment (quarterly or when significant conflicts arise)
+**Delivery:** Presented at S&OP meeting with supporting data
+
+---
+
+**Subject:** Priority Alignment Request — Week {{week_number}} / Month {{month}}
+
+**From:** {{scheduler_name}}, Production Scheduling
+
+**Issue:**
+The current production plan contains conflicting priorities that cannot be resolved within available capacity. Scheduling has identified {{conflict_count}} conflicts requiring cross-functional alignment.
+
+**Conflict summary:**
+
+| # | Conflict | Departments Involved | Scheduler's Assessment |
+|---|---|---|---|
+| 1 | Customer A rush order vs. Customer B committed delivery — both need CNC constraint, 16-hour gap | Sales + Production | Need commercial decision: which customer takes priority? |
+| 2 | NPI trial run vs. production schedule — trial requires 14 hrs of constraint time in a week loaded at 94% | Engineering + Production | Recommend scheduling trial on Saturday to avoid displacement |
+| 3 | Maintenance PM window vs. peak production week — PM deferred twice already | Maintenance + Production | Recommend executing PM this week; deferral risk exceeds production value of the PM window |
+
+**For each conflict, scheduling needs:**
+1. A single, clear priority decision
+2. Written confirmation (email or meeting minutes) that the decision is endorsed by all affected departments
+3. Decision by {{decision_deadline}} so the schedule can be locked for the week
+
+**Scheduling will execute whatever priority is agreed. We are not requesting a specific outcome — we are requesting clarity so the schedule can be built without ambiguity.**
+
+---
+
+**Tone guidance:** Neutral facilitator, not advocate. The scheduler's role in priority alignment is to surface conflicts, quantify tradeoffs, and execute decisions — not to make commercial or strategic calls. Make it clear that you need a decision, not a discussion. Provide the data that enables the decision.
diff --git a/web-app/public/skills/production-scheduling/references/decision-frameworks.md b/web-app/public/skills/production-scheduling/references/decision-frameworks.md
new file mode 100644
index 00000000..7be6e5f2
--- /dev/null
+++ b/web-app/public/skills/production-scheduling/references/decision-frameworks.md
@@ -0,0 +1,867 @@
+# Decision Frameworks — Production Scheduling
+
+This reference provides the detailed decision logic, scheduling algorithms, optimisation
+methodologies, and capacity planning techniques for production scheduling in discrete
+and batch manufacturing. It is loaded on demand when the agent needs to make or recommend
+nuanced scheduling decisions.
+
+All thresholds, formulas, and time assumptions reflect discrete and batch manufacturing
+operations running 3–8 production lines with 50–300 direct-labour headcount per shift.
+
+---
+
+## 1. Job Scheduling Algorithms
+
+### 1.1 Dispatching Rules — When to Use Each
+
+Dispatching rules are heuristics applied at a work centre when multiple jobs compete for
+the same resource. No single rule dominates in all situations. The choice depends on the
+plant's primary performance objective.
+
+| Rule | Definition | Best For | Weakness |
+|---|---|---|---|
+| **SPT (Shortest Processing Time)** | Process the job with the shortest operation time first | Minimising average flow time, reducing WIP, maximising throughput when setup times are negligible | Starves long jobs — a job with 8-hour run time waits behind twenty 20-minute jobs. Creates due date violations on long-cycle products. |
+| **EDD (Earliest Due Date)** | Process the job with the earliest due date first | Minimising maximum lateness across all jobs, meeting delivery commitments | Ignores processing time — a job due tomorrow with an 8-hour run time gets priority over a job due in 2 hours with a 5-minute run. Can increase WIP if many jobs have distant due dates. |
+| **Critical Ratio (CR)** | CR = (Due Date − Now) / Remaining Processing Time. Schedule lowest CR first. | Balancing due date urgency with remaining work. CR < 1.0 means the job is behind schedule. | Breaks down when due dates are unrealistic (all CRs < 0.5). Requires accurate remaining processing time estimates. |
+| **Weighted Shortest Job First (WSJF)** | Priority = (Cost of Delay × Job Weight) / Processing Time. Schedule highest priority first. | Environments where jobs have different economic value. Maximises throughput-weighted value. | Requires reliable cost-of-delay estimates, which are often subjective. Can starve low-value long jobs indefinitely. |
+| **Slack Time (ST)** | Slack = Due Date − Now − Remaining Processing Time. Schedule lowest slack first. | Similar to CR but uses absolute slack rather than ratio. Better when processing times are similar. | Same as CR — degrades with unrealistic due dates. Does not account for queue time at downstream work centres. |
+| **FIFO (First In, First Out)** | Process jobs in arrival order at the work centre | Ensuring fairness, simple to communicate, works in stable environments with predictable flow | No optimisation — ignores due dates, processing times, and economic value. Use only when all jobs are equal priority and flow is balanced. |
+
+#### Algorithm Selection Decision Tree
+
+1. **Is schedule adherence the primary KPI and are there contractual delivery penalties?**
+ → Use EDD as the primary rule. Insert CR checks for jobs where CR < 0.8 — these need
+ immediate attention regardless of EDD rank.
+
+2. **Is throughput/output the primary KPI with flexible delivery windows?**
+ → Use SPT to minimise average flow time. Monitor maximum lateness; if it exceeds
+ the acceptable threshold, switch to a hybrid SPT-EDD (SPT within a due date window).
+
+3. **Do jobs have significantly different economic values (margin, penalty, customer tier)?**
+ → Use WSJF. Weight = customer tier multiplier × margin contribution. This is the
+ appropriate rule for job shops with heterogeneous order portfolios.
+
+4. **Are setup times sequence-dependent and significant (>15 minutes between families)?**
+ → No pure dispatching rule handles this. Use a setup-aware scheduling heuristic
+ (Section 2) that groups jobs by setup family and optimises within groups using EDD.
+
+5. **Is the environment stable with balanced flow and predictable demand?**
+ → FIFO is acceptable and preferred for its simplicity and shop floor trust.
+
+### 1.2 Multi-Rule Hybrid Approaches
+
+In practice, most schedulers use a hybrid approach layered as follows:
+
+**Layer 1 — Hard Constraints (filter)**
+Remove any job from the queue that lacks material, tooling, or a qualified operator.
+These jobs are not schedulable regardless of priority.
+
+**Layer 2 — Urgency Override (force-rank)**
+Jobs with CR < 0.8 or that are already past-due are force-ranked to the top,
+ordered by customer penalty exposure descending.
+
+**Layer 3 — Primary Dispatching Rule (sort remaining)**
+Apply the selected dispatching rule (EDD, SPT, WSJF, etc.) to remaining jobs.
+
+**Layer 4 — Setup Optimisation (local reorder)**
+Within the primary sequence, perform adjacent-swap improvements to reduce
+total setup time, subject to the constraint that no swap causes a due date
+violation for either swapped job.
+
+**Layer 5 — Labour Levelling (validate)**
+Check that the resulting sequence does not create labour peaks that exceed
+available headcount for any hour of the shift. If it does, defer the lowest-
+priority job creating the peak to the next available slot.
+
+### 1.3 Critical Ratio in Detail
+
+Critical Ratio is the most versatile single dispatching rule for mixed environments.
+
+**Formula:**
+```
+CR = (Due Date − Current Date) / Remaining Total Processing Time
+```
+
+Where Remaining Total Processing Time includes:
+- Setup time for the current operation
+- Run time for the current operation
+- Queue time estimates for remaining operations (use historical average queue times)
+- Setup + run times for all remaining operations in the routing
+
+**Interpretation:**
+| CR Value | Meaning | Action |
+|---|---|---|
+| CR > 2.0 | Comfortable lead — job is well ahead of schedule | Lowest priority. May be deferred if capacity is needed for tighter jobs. |
+| 1.0 < CR < 2.0 | On track but limited slack | Schedule normally per dispatching rule |
+| CR = 1.0 | Exactly on schedule — no slack remaining | Monitor closely. Any disruption will cause lateness. |
+| 0.5 < CR < 1.0 | Behind schedule — will be late without intervention | Escalate. Consider overtime, alternate routing, or partial shipment. |
+| CR < 0.5 | Critically late — recovery is unlikely without significant intervention | Immediate escalation to production manager. Notify customer of revised date. |
+
+**Updating CR:** Recalculate CR at every operation completion and at the start of every
+shift. A job with CR = 1.5 at shift start that encounters a 4-hour unplanned delay mid-shift
+may drop to CR = 0.7 — the shift supervisor needs to know this in real time.
+
+### 1.4 Weighted Scheduling for Customer Tiers
+
+Manufacturing plants serving multiple customer tiers need a weighting system:
+
+| Customer Tier | Weight Multiplier | Rationale |
+|---|---|---|
+| Tier 1 (OEM, contractual penalties) | 3.0 | Late delivery triggers financial penalties, production line-down claims |
+| Tier 2 (Key accounts, framework agreements) | 2.0 | No contractual penalty but relationship value and reorder risk |
+| Tier 3 (Standard accounts) | 1.0 | Standard terms, no penalty |
+| Tier 4 (Spot orders, distributors) | 0.5 | Price-sensitive, low switching cost for them |
+
+**WSJF with Customer Tier:**
+```
+Priority Score = (Customer Tier Weight × Days Until Due / Remaining Processing Time)
+```
+Lower score = higher priority (more urgent). Negative scores = past-due.
+
+---
+
+## 2. Changeover Optimisation
+
+### 2.1 SMED Implementation Phases — Step by Step
+
+#### Phase 0 — Document the Current State (2–4 weeks)
+
+1. Video-record 3–5 changeovers on the target machine/line. Include the full duration
+ from last good piece of the outgoing product to first good piece of the incoming product.
+2. Create a changeover element sheet listing every task performed, the performer
+ (operator, setup tech, maintenance), the duration, and whether the machine was stopped.
+3. Categorize each element:
+ - **Internal (IED):** Must be performed with the machine stopped.
+ - **External (OED):** Can be performed while the machine is still running.
+ - **Waste:** Not necessary at all — holdover from old procedures, redundant checks, waiting.
+
+Typical finding: 30–50% of changeover time is either external work incorrectly performed
+during machine stoppage, or pure waste (searching for tools, waiting for approval,
+walking to the tool crib).
+
+#### Phase 1 — Separate Internal and External (2–4 weeks)
+
+1. Move all external elements to pre-changeover preparation:
+ - Pre-stage next-job tooling, dies, fixtures at the machine before the changeover begins.
+ - Pre-mix materials, pre-heat moulds, pre-program CNC settings.
+ - Pre-print work order documentation and quality checklists.
+2. Create a standardised changeover preparation checklist. The setup technician begins
+ executing it 30–60 minutes before the scheduled changeover time.
+3. Expected result: 25–40% reduction in machine-stopped time with no capital investment.
+
+#### Phase 2 — Convert Internal to External (4–8 weeks)
+
+1. Standardise die/fixture heights and mounting interfaces so that alignment and adjustment
+ happen before the die reaches the machine, not after.
+2. Implement intermediate jigs — set up the next tool in a staging fixture that mirrors
+ the machine's mounting interface. When the changeover begins, the pre-assembled unit
+ drops in with minimal adjustment.
+3. Pre-condition materials: if the incoming product requires a different temperature,
+ viscosity, or chemical mix, start conditioning in a parallel vessel.
+4. Expected result: additional 15–25% reduction in machine-stopped time. May require
+ modest investment in duplicate tooling or staging fixtures.
+
+#### Phase 3 — Streamline Remaining Internal Elements (4–12 weeks)
+
+1. Replace bolt-on fasteners with quick-release clamps, cam locks, or hydraulic clamping.
+ Every bolt removed saves 15–30 seconds.
+2. Eliminate adjustments through poka-yoke: centre pins, guide rails, fixed stops that
+ guarantee first-piece alignment without trial-and-error.
+3. Standardise utility connections: colour-coded quick-disconnect fittings for air, water,
+ hydraulic, and electrical. One-motion connect/disconnect.
+4. Parallel operations: two people working simultaneously on different sides of the machine
+ can halve the internal time. Requires choreographed procedures and safety protocols.
+5. Expected result: additional 10–20% reduction. Often requires capital investment in
+ quick-change tooling.
+
+#### Phase 4 — Eliminate Adjustments and Verify (ongoing)
+
+1. Implement first-piece verification jigs that confirm dimensions without full inspection.
+2. Use statistical process control (SPC) from the first piece — if the first piece is within
+ control limits, the changeover is validated without a trial run.
+3. Document the final standardised changeover procedure with photos, time targets per element,
+ and a sign-off sheet.
+4. Target: changeover time under 10 minutes (single-minute exchange of die) for the
+ machine-stopped portion.
+
+### 2.2 Sequence-Dependent Setup Matrices
+
+For operations where setup time varies by product-to-product transition, build a
+setup time matrix:
+
+**Example — Paint Line Setup Matrix (minutes):**
+
+| From \ To | White | Yellow | Orange | Red | Blue | Black |
+|---|---|---|---|---|---|---|
+| **White** | 0 | 8 | 10 | 15 | 20 | 25 |
+| **Yellow** | 15 | 0 | 8 | 12 | 20 | 25 |
+| **Orange** | 20 | 12 | 0 | 8 | 18 | 22 |
+| **Red** | 25 | 18 | 12 | 0 | 15 | 18 |
+| **Blue** | 20 | 22 | 20 | 18 | 0 | 10 |
+| **Black** | 30 | 28 | 25 | 22 | 12 | 0 |
+
+**Observations from this matrix:**
+- Light-to-dark transitions (White → Black: 25 min) are cheaper than dark-to-light (Black → White: 30 min).
+- Within colour families, transitions are minimal (Red → Orange: 12 min vs. Red → White: 25 min).
+- The optimal sequence for all six colours in a campaign would be: White → Yellow → Orange → Red → Blue → Black (total: 8+8+8+15+10 = 49 min) vs. random sequence averaging 17 min per transition (85 min total).
+
+**Using the matrix in scheduling:**
+1. Group jobs by colour family when possible (campaign scheduling within families).
+2. When inter-family transitions are required, optimise the transition sequence using the
+ nearest-neighbour heuristic, then improve with 2-opt swaps.
+3. If a specific colour is due earliest but the optimal setup sequence would delay it,
+ compute the cost of the suboptimal sequence (extra setup minutes × constraint hourly rate)
+ vs. the cost of late delivery. Choose the lower-cost option.
+
+### 2.3 Campaign Length Optimisation
+
+**Economic Production Quantity (EPQ):**
+```
+EPQ = √((2 × D × S) / (H × (1 − D/P)))
+```
+Where:
+- D = demand rate (units per period)
+- S = setup cost per changeover (labour + scrap + lost output opportunity cost)
+- H = holding cost per unit per period
+- P = production rate (units per period), P > D
+
+**Practical adjustments:**
+- Round EPQ up to the nearest full shift or full batch to avoid mid-shift changeovers.
+- If EPQ results in WIP that exceeds available staging space, constrain to physical capacity.
+- If EPQ results in a campaign longer than the longest customer lead time tolerance,
+ shorten it to maintain responsiveness even at higher changeover frequency.
+
+**Campaign vs. mixed-model decision:**
+
+| Factor | Favours Campaign | Favours Mixed-Model |
+|---|---|---|
+| Setup time | Long (>60 min) | Short (<15 min) |
+| Setup cost | High (>$500 per changeover) | Low (<$100 per changeover) |
+| Demand variability | Low (stable, forecastable) | High (volatile, order-driven) |
+| Customer lead time expectation | Tolerant (>2 weeks) | Tight (<3 days) |
+| WIP carrying cost | Low | High |
+| Product shelf life | Long or N/A | Short or regulated |
+| Number of product variants | Few (<10) | Many (>50) |
+
+---
+
+## 3. Theory of Constraints (TOC) Implementation
+
+### 3.1 Drum-Buffer-Rope — Step by Step
+
+**Step 1: Identify the Constraint**
+
+Run a capacity analysis for each work centre over the next planning horizon (1–4 weeks):
+
+```
+Utilisation = Σ(Setup Time + Run Time for all scheduled jobs) / Available Time
+```
+
+Available Time = shift hours × number of machines × (1 − planned maintenance %)
+
+The work centre with the highest utilisation ratio is the drum. If multiple work centres
+exceed 90% utilisation, the one with the least flexibility (fewest alternate routings,
+most specialised equipment) is the primary constraint.
+
+**Validation test:** If you could add 10% more capacity to the suspected constraint
+(one more machine, one more shift hour, or a 10% speed increase), would total plant
+output increase by approximately 10%? If yes, it is the true constraint. If output
+increases less (because a second work centre immediately becomes the bottleneck),
+you have an interactive constraint pair that requires different treatment.
+
+**Step 2: Exploit the Constraint**
+
+Maximise the output of the constraint with no capital investment:
+
+1. **Eliminate idle time:** The constraint should never wait for material, tooling,
+ operators, quality inspection, or information. Pre-stage everything.
+2. **Minimise changeovers on the constraint:** Move changeover to non-constraint
+ resources where the time cost is lower. If the constraint must change over,
+ ensure SMED discipline is applied rigorously.
+3. **Prevent quality defects reaching the constraint:** Inspect before the constraint
+ operation, not after. Every defective piece processed at the constraint is wasted
+ constraint capacity.
+4. **Run through breaks and shift changes:** Stagger operator lunches so the constraint
+ never stops for a break. Assign a relief operator.
+5. **Eliminate micro-stops:** Address every source of 1–5 minute stoppages (sensor trips,
+ material jams, tool wear alarms) that individually seem trivial but cumulatively steal
+ 2–5% of capacity.
+
+**Step 3: Subordinate Everything to the Constraint**
+
+1. **Upstream work centres:** Release work to upstream operations only at the rate the
+ constraint can consume it. This is the "rope." If the constraint processes 100 units/hour,
+ the upstream release rate should not exceed 100 units/hour regardless of upstream capacity.
+2. **Downstream work centres:** Must maintain enough sprint capacity to clear constraint
+ output without becoming a secondary bottleneck. If the constraint produces a batch every
+ 2 hours, downstream must be able to process that batch within 2 hours.
+3. **Scheduling non-constraints:** Do not optimise non-constraint schedules in isolation.
+ A non-constraint running at 100% utilisation when the constraint runs at 85% is producing
+ excess WIP that clogs the shop floor and slows the constraint's material flow.
+
+**Step 4: Establish the Buffer**
+
+The constraint buffer is a time buffer, not an inventory buffer:
+
+```
+Buffer Duration = Planned Lead Time from release to constraint × Buffer Factor
+```
+
+Typical buffer factors:
+- Stable, reliable upstream operations: 0.3 × lead time
+- Moderate reliability, some variability: 0.5 × lead time (most common starting point)
+- Unreliable upstream, frequent disruptions: 0.75 × lead time
+
+**Buffer sizing example:**
+If the upstream lead time from raw material release to the constraint work centre is
+8 hours, and upstream reliability is moderate, set the buffer at 4 hours. This means
+material should arrive at the constraint staging area at least 4 hours before the
+constraint is scheduled to process it.
+
+**Step 5: Monitor Buffer Penetration**
+
+| Zone | Buffer Consumed | Meaning | Action |
+|---|---|---|---|
+| Green | 0–33% | Constraint well-protected | Normal operations |
+| Yellow | 33–67% | Warning — material may arrive late | Expedite upstream work. Check for blockers. |
+| Red | 67–100% | Critical — constraint at risk of starvation | Immediate escalation. Overtime upstream. Re-sequence if needed. |
+| Black | >100% | Buffer exhausted — constraint is starving | Constraint is idle or will be idle. Emergency response. Every minute of delay from this point = lost plant output. |
+
+Track buffer penetration trends over 2–4 weeks. Persistent yellow indicates
+a systemic upstream issue (not random variation) that needs corrective action.
+
+**Step 6: Elevate the Constraint (only if Steps 1–5 are exhausted)**
+
+If after full exploitation and subordination the constraint still limits plant output
+below demand requirements:
+
+1. Add overtime or a weekend shift at the constraint only.
+2. Add a parallel machine or alternate routing capability.
+3. Outsource constraint-specific operations to a qualified subcontractor.
+4. Invest in faster constraint equipment (capital expenditure).
+
+Each elevation step is progressively more expensive. Never elevate before fully
+exploiting — most plants have 15–25% hidden capacity at the constraint that
+exploitation recovers at minimal cost.
+
+### 3.2 Buffer Management Advanced Patterns
+
+**Shipping Buffer:** Protects customer due dates from internal variability. Typically
+50% of the lead time from the constraint to shipping. If the constraint-to-shipping
+lead time is 2 days, the shipping buffer is 1 day — work should arrive at the
+shipping staging area 1 day before the committed ship date.
+
+**Assembly Buffer:** In plants with convergent product structures (multiple components
+feeding a common assembly), each feeder path to the assembly point needs its own
+buffer. The assembly can only proceed when ALL components are present, so the
+slowest feeder path determines the effective buffer.
+
+**Dynamic Buffer Adjustment:**
+- If buffer penetration is consistently in the green zone (>80% of jobs arrive with
+ buffer intact over a 4-week rolling window), reduce the buffer by 10–15%. Excess buffer
+ means excess WIP and longer lead times.
+- If buffer penetration frequently reaches red zone (>20% of jobs in a 4-week window),
+ increase the buffer by 15–20% while investigating the root cause upstream.
+- Never adjust buffers more frequently than every 2 weeks. Buffer management requires
+ stable data over multiple cycles.
+
+---
+
+## 4. Disruption Recovery Protocols
+
+### 4.1 Structured Disruption Response Framework
+
+When a disruption occurs, follow this decision tree:
+
+**Step 1: Classify the Disruption**
+
+| Type | Examples | Typical Duration | Impact Scope |
+|---|---|---|---|
+| **Equipment** | Breakdown, sensor failure, tooling wear | 30 min – 3 days | Single work centre |
+| **Material** | Shortage, wrong specification, quality reject of incoming | 2 hours – 2 weeks | Multiple work centres sharing the material |
+| **Labour** | Absenteeism, injury, certification gap | 1 shift – 1 week | Single work centre or line |
+| **Quality** | In-process defect, customer complaint triggering hold | 2 hours – 1 week | Entire batch/lot, plus downstream consumers |
+| **External** | Supplier failure, power outage, weather, regulatory stop | 4 hours – indefinite | Potentially plant-wide |
+
+**Step 2: Assess Constraint Impact**
+
+| Disruption Location | Constraint Impact | Response Priority |
+|---|---|---|
+| At the constraint | Direct — every minute = lost throughput | Maximum priority. All resources mobilised. |
+| Upstream of constraint, buffer is green | Indirect — buffer absorbs the delay | Monitor buffer penetration. No immediate schedule change. |
+| Upstream of constraint, buffer is yellow/red | Indirect but imminent — constraint will starve | Expedite. Overtime upstream. Re-sequence to feed constraint from alternate sources. |
+| Downstream of constraint | No throughput impact unless WIP backs up to constraint | Monitor. Clear downstream blockage before constraint output starts queuing. |
+| Parallel path (no constraint interaction) | No throughput impact, but delivery impact on affected orders | Re-sequence affected orders. Notify customers. |
+
+**Step 3: Execute Recovery**
+
+1. **Immediate (0–30 minutes):** Assess duration and impact. Notify affected parties. Freeze in-process work.
+2. **Short-term (30 min – 4 hours):** Re-sequence remaining work. Activate alternate routings. Assign backup operators. Request emergency maintenance.
+3. **Medium-term (4–24 hours):** Negotiate overtime or shift extensions. Contact subcontractors. Update customer ETAs. Recalculate the full planning horizon.
+4. **Long-term (>24 hours):** Capacity rebalancing. Possible order reallocation to alternate sites. Customer negotiations on delivery schedules. Insurance/force majeure documentation if applicable.
+
+### 4.2 Material Shortage Response
+
+1. **Confirm the shortage:** Verify physical inventory vs. system count. Phantom inventory
+ is common — conduct a physical count before declaring a shortage.
+2. **Identify substitutes:** Check BOM alternates, engineering-approved substitutions,
+ and customer-approved equivalent materials. In regulated industries (aerospace, pharma),
+ only pre-approved substitutes are permissible.
+3. **Partial build strategy:** Can you complete operations up to the point where the short
+ material is consumed, then hold semi-finished WIP for completion when material arrives?
+ This keeps upstream work centres productive and preserves lead time on the non-missing
+ portions of the routing.
+4. **Re-sequence:** Pull forward all work orders that do not consume the short material.
+ This keeps the plant productive even during the shortage.
+5. **Expedite procurement:** Emergency purchase order at premium freight. Quantify: is the
+ cost of expedited material + freight less than the cost of lost constraint time × hours
+ of delay? If yes, expedite without hesitation.
+6. **Customer communication:** If the shortage will impact customer deliveries, notify within
+ 4 hours of confirmation. Provide a revised delivery date and a recovery plan.
+
+### 4.3 Quality Hold Management
+
+When an in-process quality issue is discovered:
+
+1. **Contain immediately:** Quarantine all affected WIP — the batch in process, any
+ completed units from the same batch, and any downstream assemblies that consumed
+ units from the batch.
+2. **Assess scope:** How many units are affected? Which customer orders consume these units?
+ What is the rework cost vs. scrap cost vs. customer rejection cost?
+3. **Reschedule:** Remove the held inventory from the active schedule. Recalculate all
+ downstream operations that depended on this inventory.
+4. **Decision tree for held material:**
+ - **Rework possible and economical:** Schedule rework operations. Add rework time to the
+ routing and re-sequence downstream.
+ - **Rework possible but not economical (rework cost > material + labour cost of remaking):**
+ Scrap the held batch and schedule a replacement production order from scratch.
+ - **Cannot rework, cannot scrap (regulatory hold pending investigation):** Exclude from
+ schedule indefinitely. Plan as though the inventory does not exist.
+5. **Root cause:** While the schedule adjusts, quality engineering should be isolating the
+ root cause. The scheduler needs to know: is this a one-time event, or will subsequent
+ batches also be affected? If systemic, reduce yield assumptions for the affected operation
+ in the scheduling parameters until the root cause is resolved.
+
+---
+
+## 5. Capacity Planning vs. Finite Scheduling
+
+### 5.1 Rough-Cut Capacity Planning (RCCP)
+
+RCCP is a medium-term planning tool (4–16 weeks out) that validates whether the MPS
+is feasible at a high level before detailed scheduling.
+
+**Process:**
+1. Take the MPS (production plan by product family by week).
+2. Multiply by the routing hours per unit at each key work centre (typically only the
+ constraint and 1–2 near-constraints).
+3. Compare total required hours against available hours per week at each work centre.
+4. If required hours exceed available hours, flag the overloaded weeks for action:
+ demand shaping (move orders to adjacent weeks), overtime, subcontracting, or MPS revision.
+
+**RCCP Load Profile Example:**
+
+| Week | Constraint Capacity (hrs) | Required Load (hrs) | Utilisation | Status |
+|---|---|---|---|---|
+| W23 | 120 | 105 | 87.5% | OK |
+| W24 | 120 | 118 | 98.3% | Warning — near capacity |
+| W25 | 120 | 142 | 118.3% | Overloaded — action needed |
+| W26 | 120 | 96 | 80.0% | OK — could absorb W25 overflow |
+| W27 | 80 (planned maintenance window) | 75 | 93.8% | Tight — maintenance may need rescheduling |
+
+**Actions for W25 overload:**
+- Can 22 hours of load shift to W24 or W26 without missing customer dates? Check due dates.
+- If not shiftable: overtime (22 hrs ÷ 8 hrs/shift = 3 extra shifts, or 3 Saturday shifts).
+- If overtime not available: which orders have the most flexible delivery dates? Negotiate.
+- Last resort: subcontract 22 hours of work. Assess quality and lead time implications.
+
+### 5.2 Finite Capacity Scheduling (FCS) Detail
+
+FCS goes beyond RCCP by scheduling individual operations on specific resources at
+specific times, respecting:
+
+1. **Resource capacity:** Number of machines × hours per shift × shifts per day, minus planned maintenance windows.
+2. **Sequence-dependent setups:** Setup time varies based on the preceding job (see setup matrix in Section 2.2).
+3. **Material availability:** An operation cannot start until all BOM components are available at the work centre.
+4. **Tooling constraints:** A job requiring tooling set ABC cannot run simultaneously with another job requiring the same tooling.
+5. **Labour constraints:** A job requiring a certified operator cannot be scheduled when no certified operator is on shift.
+6. **Operation dependencies:** Operation 20 on a work order cannot start until Operation 10 is complete (routing precedence).
+7. **Transfer batches:** Overlap operations can start before the full batch from the preceding operation is complete, if the transfer batch size is defined.
+
+**FCS Scheduling Algorithm (simplified):**
+1. Sort all operations by priority (using the hybrid dispatching approach from Section 1.2).
+2. For the highest-priority unscheduled operation:
+ a. Find the earliest feasible time slot on the required resource, considering capacity,
+ material availability, tooling, labour, and predecessor completion.
+ b. Schedule the operation in that slot.
+ c. Update resource availability.
+3. Repeat for the next-highest-priority operation.
+4. After all operations are scheduled, run a post-optimisation pass looking for setup
+ reduction opportunities (adjacent-swap improvements) that don't violate due dates.
+
+### 5.3 Capacity Buffers and Protective Capacity
+
+Non-constraint work centres should maintain protective capacity — deliberately planned
+idle time that absorbs variability and prevents WIP accumulation.
+
+**Target utilisation by work centre type:**
+
+| Work Centre Type | Target Utilisation | Rationale |
+|---|---|---|
+| Constraint | 90–95% | Maximise output. Buffer everything else to protect it. |
+| Near-constraint (>80% loaded) | 85–90% | Close to becoming the constraint. Monitor for shifting bottleneck. |
+| Standard | 75–85% | Protective capacity absorbs upstream variability. |
+| Shared resource (forklift, crane, inspector) | 60–75% | High variability in demand for these resources. Over-scheduling creates system-wide delays. |
+| Rework/repair | 50–70% | Must have capacity available on demand. Cannot schedule at high utilisation. |
+
+**Warning signs of insufficient protective capacity:**
+- WIP queues growing at non-constraint work centres over time.
+- Non-constraint work centres occasionally becoming the bottleneck (shifting bottleneck).
+- Overtime at non-constraint work centres "to keep up."
+- Material handlers constantly expediting between non-constraint operations.
+
+---
+
+## 6. Multi-Constraint Scheduling
+
+### 6.1 Interactive Constraints
+
+When two or more work centres both exceed 85% utilisation and share a material flow path,
+they interact — improving throughput at one may starve or overload the other.
+
+**Identification:**
+Two work centres are interactive constraints if:
+1. They are on the same routing (material flows from one to the other), AND
+2. Both exceed 85% utilisation, AND
+3. Adding capacity at one causes the other's utilisation to exceed 95%.
+
+**Scheduling Strategy for Interactive Constraints:**
+
+1. **Schedule the primary constraint first** (the one with higher utilisation or the one
+ closer to the customer).
+2. **Subordinate the secondary constraint** to the primary's schedule — the secondary
+ constraint processes work in the order and at the pace dictated by the primary constraint's
+ output schedule.
+3. **Place a buffer between them** — even though both are constraints, the upstream one
+ should feed a time buffer to the downstream one to absorb variability.
+4. **Never optimise them independently.** A setup sequence that is optimal for the primary
+ constraint may create an impossible sequence for the secondary constraint if setups
+ are sequence-dependent at both. Solve jointly.
+
+### 6.2 Machine + Labour Dual Constraints
+
+Common in environments where machines are semi-automated and require an operator for
+setup, first-piece inspection, or monitoring but can run unattended for portions of the cycle.
+
+**Scheduling approach:**
+1. Schedule machine capacity first (finite capacity by machine).
+2. Overlay labour capacity (finite capacity by skill/certification).
+3. Identify conflicts: time slots where the machine schedule requires an operator but
+ no qualified operator is available.
+4. Resolve conflicts by:
+ - Shifting the job to a different machine that a different operator is qualified on.
+ - Shifting the operator from a lower-priority job to the conflicting job.
+ - Scheduling the operator's setup/inspection tasks at the start of the job and
+ allowing unattended running thereafter.
+
+### 6.3 Tooling as a Shared Constraint
+
+When specialised tooling (moulds, dies, fixtures, gauges) is shared across machines:
+
+1. **Treat tooling as a resource in the scheduling system** — the same way you schedule
+ machines and labour, schedule tooling.
+2. **Two jobs requiring the same mould cannot run simultaneously** on different machines.
+3. **Tooling changeover time** between machines adds to the total changeover. If Mould A
+ moves from Machine 1 to Machine 2, add the mould extraction time (Machine 1) + transport
+ time + mould installation time (Machine 2).
+4. **Optimise by grouping:** If three jobs all require Mould A, schedule them consecutively
+ on the same machine to avoid mould transfers.
+
+---
+
+## 7. Line Balancing for Mixed-Model Production
+
+### 7.1 Takt Time Calculation
+
+```
+Takt Time = Available Production Time per Shift / Customer Demand per Shift
+```
+
+**Example:** 480 minutes available per shift (8 hours × 60 min, minus 30 min breaks),
+customer demand is 240 units per shift.
+
+```
+Takt Time = 450 / 240 = 1.875 minutes per unit
+```
+
+Every workstation on the line must complete its tasks within 1.875 minutes per unit.
+If any station exceeds takt, it becomes the bottleneck and the line cannot meet demand.
+
+### 7.2 Workstation Balancing
+
+1. List all tasks with their duration and precedence relationships.
+2. Assign tasks to workstations such that no workstation exceeds takt time.
+3. Minimise the number of workstations (to minimise labour cost).
+4. Measure balance efficiency:
+
+```
+Balance Efficiency = Σ(Task Times) / (Number of Stations × Takt Time) × 100%
+```
+
+Target: >85%. Below 80% indicates significant idle time at some stations.
+
+### 7.3 Mixed-Model Sequencing (Heijunka)
+
+When a line produces multiple models with different task times:
+
+1. Calculate the weighted average cycle time across models.
+2. Determine the model mix ratio (e.g., Model A: 60%, Model B: 30%, Model C: 10%).
+3. Create a repeating pattern that levels the workload. For A:B:C = 6:3:1, a 10-unit
+ cycle would be: A-B-A-A-C-A-B-A-B-A.
+4. Validate that the bottleneck station can handle every model within takt. If Model C
+ takes 2.5 minutes at Station 3 while takt is 1.875 minutes, Model C must be spaced
+ sufficiently that Station 3 can catch up between occurrences.
+
+---
+
+## 8. Scheduling with Regulatory and Compliance Constraints
+
+### 8.1 Traceability-Driven Scheduling
+
+In regulated industries (pharmaceutical, food, aerospace), lot traceability requirements
+constrain scheduling flexibility:
+
+- **No lot mixing:** A work order for Lot A and a work order for Lot B cannot share
+ equipment simultaneously unless the equipment is fully cleaned between lots and
+ the cleaning is documented.
+- **Dedicated equipment campaigns:** When allergen or contamination controls require
+ dedicated equipment, the scheduling window for Product X on Line 1 is limited to
+ the dedicated campaign period. Scheduling outside this window requires re-validation.
+- **Operator qualification records:** The schedule must record which operator performed
+ each operation, and that operator must be certified at the time of execution.
+
+### 8.2 Clean-In-Place (CIP) Scheduling
+
+In food, beverage, and pharma, CIP cycles are mandatory between certain product transitions:
+
+| Transition Type | CIP Duration | Can Be Shortened? |
+|---|---|---|
+| Same product, next batch | 0–15 min (rinse only) | No — regulatory minimum |
+| Same product family | 30–60 min (standard CIP) | Only with validated short-CIP protocol |
+| Different product family | 60–120 min (full CIP) | No — regulatory requirement |
+| Allergen transition | 120–240 min (enhanced CIP + swab test) | No — requires analytical confirmation |
+
+Schedule CIP cycles as fixed blocks in the schedule, not as "setup time" that can be
+compressed. Under-estimating CIP time is a common scheduling error that creates cascading
+delays and regulatory risk.
+
+---
+
+## 9. Schedule Stability and Frozen Zones
+
+### 9.1 Frozen / Slushy / Liquid Planning Horizons
+
+| Horizon | Typical Duration | Flexibility | Changes Require |
+|---|---|---|---|
+| **Frozen** | 0–48 hours | No changes except force majeure | Production Manager + Scheduler approval |
+| **Slushy** | 48 hours – 1 week | Sequence changes allowed within day; no date changes | Scheduler approval |
+| **Liquid** | 1–4 weeks | Fully flexible for re-sequencing and rescheduling | Scheduler discretion |
+| **Tentative** | 4+ weeks | MRP-generated, not yet scheduled | Planning/MRP cycle |
+
+**Why frozen zones matter:** Every schedule change triggers a cascade — material handlers
+re-stage kits, operators re-read work orders, quality pre-inspections may need repeating,
+and changeover sequences recalculate. A plant that changes the schedule 10 times per shift
+has more disruption from schedule changes than from actual production problems.
+
+### 9.2 Schedule Change Cost Model
+
+Before approving a schedule change in the frozen or slushy zone, estimate the total cost:
+
+```
+Change Cost = Changeover Cost Delta + Material Restaging Cost + Labour Disruption Cost
+ + Quality Re-inspection Cost + Customer Impact Risk
+```
+
+If Change Cost > Benefit of Change, reject the change and hold the current schedule.
+Document the decision for the post-shift review.
+
+---
+
+## 10. Overtime and Shift Extension Decision Framework
+
+### 10.1 When to Authorise Overtime
+
+Overtime is a scheduling lever, not a default. Use the following decision tree:
+
+1. **Is the overtime required at the constraint?**
+ - Yes → Calculate: overtime cost vs. throughput value of additional constraint hours.
+ If 4 hours of constraint overtime at $1,200 total cost enables $20,000 of shipments,
+ approve immediately. The ROI threshold for constraint overtime is typically 3:1
+ (value:cost) or higher.
+ - No → The overtime at a non-constraint does not increase plant output. It only makes
+ sense if: (a) the non-constraint is starving the constraint and buffer penetration is
+ yellow/red, or (b) the non-constraint output is needed for a specific customer shipment
+ that cannot wait for the next regular shift.
+
+2. **Is the overtime voluntary or mandatory?**
+ - Check union contract or labour regulations. Many agreements require offering overtime
+ by seniority before mandating it. Mandatory overtime may require 24–48 hours' notice.
+ - Violating overtime assignment rules costs more in grievances and morale damage than
+ the production it generates. Always comply.
+
+3. **Fatigue and safety risk:**
+ - Operators who have already worked 10+ hours should not be assigned to the constraint
+ or to safety-critical operations. Error rates increase 25–40% in hours 11–12.
+ - If the overtime extends a 12-hour shift to 16 hours, assign the extended operator to
+ non-critical monitoring tasks and bring in a fresh operator for the constraint.
+
+### 10.2 Shift Pattern Comparison for Scheduling
+
+| Pattern | Hours/Week | Handovers/Week | Overtime Headroom | Best For |
+|---|---|---|---|---|
+| 3 × 8h (Mon–Fri) | 120 | 15 | Saturday shifts, daily OT | High-mix, moderate volume |
+| 3 × 8h (24/7) | 168 | 21 | Limited — already near capacity | Process industries, continuous flow |
+| 2 × 12h (Mon–Fri) | 120 | 10 | Weekend shifts | Capital-intensive with fewer handovers |
+| 2 × 12h (4 on / 4 off) | 168 | 14 | Built into rotation | High-volume, steady demand |
+| 4 × 10h (day shift only) | 40 per crew | 4 | Friday, weekend | Low-volume, single-shift operations |
+
+**Handover quality matters for scheduling:** Each handover is a potential point of
+information loss — the incoming shift may not know about a developing quality issue,
+a material shortage workaround, or a verbal schedule change. Fewer handovers (12-hour
+shifts) improve information continuity but increase fatigue risk. Balance based on
+operation complexity and error tolerance.
+
+---
+
+## 11. Subcontracting Decision Framework
+
+### 11.1 When to Subcontract
+
+Subcontracting is the scheduling lever of last resort for capacity shortfalls.
+
+**Decision criteria (all must be met):**
+1. Internal capacity at the required work centre is fully consumed through the delivery
+ deadline, including available overtime.
+2. The operation is not at the constraint (subcontracting from the constraint usually means
+ the constraint needs elevation, not a one-time fix).
+3. A qualified subcontractor exists who can meet the quality specification and delivery timeline.
+4. The subcontracting cost + transport cost + quality risk cost is less than the cost of
+ late delivery (penalties + customer relationship damage).
+5. In regulated industries: the subcontractor holds the necessary certifications
+ (ISO, IATF 16949, AS9100, FDA registration, etc.).
+
+### 11.2 Scheduling with Subcontracted Operations
+
+When an operation is subcontracted:
+1. Remove the operation from the internal schedule.
+2. Add a transport-out time (typically 0.5–2 days) and transport-in time.
+3. Add the subcontractor's quoted lead time (add 20% buffer for first-time subcontractors).
+4. The total external lead time replaces the internal operation time in the work order routing.
+5. Schedule downstream internal operations based on the expected return date, not the
+ internal processing time.
+6. Monitor subcontractor progress at 50% and 90% completion milestones. Do not wait until
+ the due date to discover a delay.
+
+---
+
+## 12. Scheduling Metrics and Continuous Improvement
+
+### 12.1 Key Scheduling Metrics
+
+| Metric | Calculation | Target | What It Reveals |
+|---|---|---|---|
+| **Schedule Adherence** | Jobs started within ±1 hour of plan / Total jobs | > 90% | How well the plant follows the schedule |
+| **Schedule Stability** | Jobs unchanged in frozen zone / Total frozen jobs | > 95% | How often the schedule is disrupted |
+| **On-Time Delivery (OTD)** | Orders shipped on or before commit date / Total orders | > 95% | Customer-facing performance |
+| **Make Span** | Time from first operation start to last operation end for a work order | Track vs. standard | Total production lead time |
+| **Changeover Ratio** | Total changeover time / Total available time at the resource | < 10% at constraint | Setup efficiency |
+| **Constraint Utilisation** | Actual producing time / Available time at constraint | > 85% | How well the constraint is exploited |
+| **WIP Turns** | Annual COGS / Average WIP Value | > 12 for discrete mfg | Scheduling efficiency and flow |
+| **Queue Time Ratio** | Queue time / Total lead time at each work centre | Track trend | Indicates hidden WIP and poor flow |
+
+### 12.2 Scheduling Post-Mortem Process
+
+After every significant schedule disruption (constraint downtime > 1 hour, customer delivery
+miss, or overtime exceeding budget by > 20%), conduct a structured post-mortem:
+
+1. **Timeline reconstruction:** What happened, when, and what was the cascade of effects?
+2. **Root cause:** Was the disruption caused by equipment, material, labour, quality,
+ scheduling logic, or external factors?
+3. **Response assessment:** Was the re-sequencing decision optimal? Could the recovery have
+ been faster? Were communications timely?
+4. **Parameter update:** Do scheduling parameters (setup times, run rates, yield factors,
+ buffer sizes) need adjustment based on what we learned?
+5. **Systemic fix:** What preventive action will reduce the probability or impact of this
+ type of disruption recurring?
+
+Document findings in a scheduling incident log. Review the log monthly with production
+management to identify patterns and prioritise improvement actions.
+
+### 12.3 Daily Scheduling Rhythm
+
+A disciplined daily cadence prevents reactive fire-fighting:
+
+| Time | Activity | Participants |
+|---|---|---|
+| Shift Start − 30 min | Pre-shift review: verify material staging, operator availability, equipment status | Scheduler, Shift Supervisor |
+| Shift Start | Publish shift schedule. Walk the floor to confirm understanding. | Scheduler |
+| Shift Start + 2 hrs | First checkpoint: plan adherence, buffer penetration, early disruption detection | Scheduler (desk review of MES data) |
+| Shift Midpoint | Mid-shift review: actual vs. plan, re-sequence if needed | Scheduler, Shift Supervisor |
+| Shift End − 1 hr | End-of-shift projection: what will be incomplete? Handover notes for next shift. | Scheduler, Shift Supervisor |
+| Shift End | Shift handover: in-person (preferred) or documented. Key issues, deviations, pending decisions. | Outgoing + Incoming Schedulers |
+| Daily (Morning) | Production meeting: yesterday's performance, today's priorities, issues requiring management decision | Scheduler, Production Mgr, Quality, Maintenance, Materials |
+
+This cadence creates at least 5 touchpoints per shift where the schedule is validated
+against reality and corrected before deviations compound.
+
+---
+
+## 13. ERP-to-Shop-Floor Data Flow
+
+### 13.1 SAP PP Integration Pattern
+
+```
+Sales Orders / Forecast
+ ↓
+Demand Management (MD61/MD62)
+ ↓
+MPS — Master Production Schedule (MD40/MD43)
+ ↓
+MRP Run (MD01/MD02) → Planned Orders
+ ↓
+Convert Planned → Production Orders (CO40/CO41)
+ ↓
+Sequence in APS/Scheduling Tool (external or PP/DS)
+ ↓
+Release to Shop Floor (CO02 — set status REL)
+ ↓
+MES Execution (operation confirmations — CO11N/CO15)
+ ↓
+Goods Receipt (MIGO) → Inventory Updated
+```
+
+**Common data quality issues:**
+- Routing times (setup + run) not updated after process improvements → schedule
+ systematically allocates too much or too little time.
+- BOM quantities not adjusted for yield → MRP under-orders material.
+- Work centre capacity not reflecting actual shift patterns → FCS generates
+ infeasible schedules.
+- Scrap reporting delayed → plan-vs-actual gap grows silently.
+
+### 13.2 Closing the Feedback Loop
+
+The single most important integration is the MES-to-schedule feedback:
+
+1. **Operation start:** MES records actual start time. Schedule compares to planned start.
+ Deviation > 1 hour triggers an alert.
+2. **Operation end:** MES records actual end time and quantities (good + scrap). Schedule
+ updates remaining operations with actual predecessor completion.
+3. **Downtime events:** MES captures downtime start, end, and reason code. Schedule
+ automatically adjusts downstream timing.
+4. **Quality events:** MES captures inspection results. Failed inspection triggers a
+ schedule hold on the affected batch.
+
+Without this feedback loop, the schedule diverges from reality within hours and becomes
+aspirational rather than operational. The shop floor stops consulting it, operators make
+their own sequencing decisions, and throughput at the constraint drops because ad-hoc
+sequencing ignores constraint protection logic.
diff --git a/web-app/public/skills/production-scheduling/references/edge-cases.md b/web-app/public/skills/production-scheduling/references/edge-cases.md
new file mode 100644
index 00000000..8818432a
--- /dev/null
+++ b/web-app/public/skills/production-scheduling/references/edge-cases.md
@@ -0,0 +1,611 @@
+# Production Scheduling — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous production scheduling situations that don't resolve through standard sequencing and dispatching workflows.
+
+These edge cases represent the scenarios that separate experienced production schedulers from everyone else. Each one involves competing constraints, imperfect data, time pressure, and real operational exposure. They are structured to guide decision-making when standard scheduling rules break down.
+
+---
+
+## How to Use This File
+
+When a scheduling situation doesn't fit a clean pattern — when constraints shift mid-shift, when multiple disruptions compound, or when commercial pressure conflicts with physical reality — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document every decision and override so the shift handover and post-mortem have a clear trail.
+
+---
+
+### Edge Case 1: Shifting Bottleneck Mid-Shift
+
+**Situation:**
+A contract manufacturer produces aluminium housings for two automotive OEMs. The morning schedule loads the CNC machining centre at 92% utilisation and the powder coating line at 78% — machining is the constraint. At 10:00 AM, the product mix shifts as a batch of large, complex housings clears CNC (short cycle time per unit for the next batch of small housings) and hits the powder coat line, which now requires extended cure cycles. By 11:00 AM, CNC utilisation has dropped to 70% and powder coat is at 95%. The schedule optimised around CNC as the constraint is now starving CNC (which has excess capacity) while powder coat backs up with WIP stacking on the staging rack.
+
+**Why It's Tricky:**
+Most scheduling systems set the constraint at the planning stage and hold it fixed for the shift. When the constraint shifts intra-shift, the buffer management, subordination logic, and priority sequencing all become wrong simultaneously. The CNC buffer is unnecessarily large (tying up WIP), while the powder coat buffer doesn't exist and the line is starving.
+
+**Common Mistake:**
+Ignoring the shift because "machining is the constraint this week" based on the weekly capacity plan. Or overreacting by completely re-sequencing the shift, creating chaos on the shop floor.
+
+**Expert Approach:**
+1. Recognise the shift by monitoring real-time WIP levels. WIP accumulating before powder coat while CNC's outfeed staging area is empty is the leading indicator.
+2. Verify the duration: is this a temporary product-mix effect (2–3 hours) or will it persist for the rest of the shift? Check the remaining work order sequence.
+3. If temporary (< 3 hours): do not re-sequence the entire shift. Instead, tactically re-prioritise the 2–3 jobs in the powder coat queue to minimise setup changes (colour sequencing), and slow CNC's release rate to avoid over-building the WIP queue.
+4. If persistent (rest of the shift): formally re-designate powder coat as the shift's constraint. Apply constraint protection: pre-stage next jobs at the powder coat line, stagger CNC completions to match powder coat's processing rate, and assign the most experienced operator to the powder coat line.
+5. At shift handover, document the constraint shift and the product mix that caused it so the incoming scheduler plans accordingly.
+
+**Documentation Required:**
+- Time of constraint shift detection
+- Product mix analysis showing utilisation crossover
+- Tactical adjustments made (CNC pacing, powder coat priority changes)
+- Impact on customer orders (any due date revisions)
+- Shift handover note for the incoming scheduler
+
+**Resolution Timeline:**
+- 0–15 min: Detect the WIP imbalance
+- 15–30 min: Verify duration and decide on tactical vs. full re-sequence
+- 30–60 min: Implement adjustments and confirm stabilisation
+- Shift end: Document and hand over
+
+---
+
+### Edge Case 2: Certified Operator Absent for Regulated Process
+
+**Situation:**
+A pharmaceutical contract manufacturer operates a tablet coating line that requires an FDA-qualified operator (documented training, competency assessment, and supervisor sign-off per 21 CFR Part 211). The night shift has two qualified coating operators: Maria (12 years experience) and Jamal (3 years, recently qualified). At 10:30 PM, Jamal — tonight's scheduled coating operator — calls in sick. Maria works day shift and is off-site. The coating line has 6 hours of work scheduled tonight that feeds a customer shipment due in 3 days. No other night-shift operator has the FDA qualification for this specific process step.
+
+**Why It's Tricky:**
+This is a hard regulatory constraint, not a soft preference. Running the coating line with an unqualified operator is a GMP violation that can trigger an FDA Form 483 observation, product recall, or facility warning letter. The cost of non-compliance vastly exceeds any production delay. But the customer shipment is for a hospital network, and delays affect patient medication availability.
+
+**Common Mistake:**
+Running the line with an "almost qualified" operator who has completed training but hasn't finished the competency assessment documentation. This is a regulatory violation regardless of the operator's actual skill level.
+
+**Expert Approach:**
+1. Confirm that no other night-shift employee holds the qualification. Check the cross-training matrix — not just coating operators, but anyone on night shift who may have been cross-trained on this line (maintenance technicians sometimes hold process qualifications).
+2. Contact Maria. Can she work a split shift (come in at midnight, work 6 hours, leave at 6 AM)? Check the union contract and fatigue rules — most agreements require an 8-hour rest between shifts. If Maria left day shift at 3:30 PM, she is eligible to return at 11:30 PM under an 8-hour rest rule.
+3. If Maria is available and willing: authorise overtime, document the reason (single-point-of-failure staffing event), and adjust the coating schedule to start when she arrives.
+4. If Maria is unavailable: stop the coating line. Do not attempt a workaround. Re-sequence the night shift to run non-regulated operations (packaging, labelling, material preparation for the next coating run). Calculate the impact on the customer shipment: can 6 hours of coating work be completed on the day shift (with overtime if needed) and still meet the 3-day deadline?
+5. Escalate to the production manager and quality assurance manager. If the customer deadline cannot be met, notify the customer immediately with a revised delivery date. For pharmaceutical customers, "we maintained GMP compliance" is a stronger position than "we cut corners to hit the date."
+6. Post-incident: submit a request to cross-train 2 additional night-shift operators on the coating process. Single-point-of-failure on a regulated process is a systemic risk.
+
+**Documentation Required:**
+- Cross-training matrix review (who holds the qualification, who does not)
+- Maria's contact record and response
+- Overtime authorisation (if applicable) with union compliance check
+- Re-sequenced night schedule showing non-regulated work
+- Customer notification (if shipment delayed)
+- CAPA (Corrective and Preventive Action) for cross-training gap
+
+**Resolution Timeline:**
+- 10:30 PM: Absence confirmed
+- 10:30–11:00 PM: Cross-training matrix review, Maria contacted
+- 11:00 PM: Decision made (Maria coming in, or coating line stopped)
+- 11:15 PM: Re-sequenced schedule published for night shift
+- Next business day: CAPA initiated for cross-training
+
+---
+
+### Edge Case 3: Competing Rush Orders from Tier-1 Customers
+
+**Situation:**
+A precision machining job shop receives two emergency orders on the same Monday morning:
+
+- **Customer A (major automotive OEM):** 500 transmission valve bodies needed by Thursday. Their assembly line is down waiting for these parts. Contractual penalty: $25,000/day of late delivery. Annual revenue from Customer A: $4.2M.
+- **Customer B (aerospace prime contractor):** 200 fuel system brackets needed by Friday. Their production schedule slips 1 week for every day of delay on these brackets. No contractual penalty, but Customer B is in a competitive evaluation and a slip here could cost the $8M annual contract renewal in Q3.
+
+Both orders require the same 5-axis CNC machining centre (the plant's constraint), and the combined processing time exceeds the available capacity by 16 hours.
+
+**Why It's Tricky:**
+This is not a scheduling problem — it's a commercial decision disguised as a scheduling problem. The scheduler can identify the tradeoff and quantify it, but the decision on which customer to prioritise requires management input on strategic relationships, risk tolerance, and commercial exposure.
+
+**Common Mistake:**
+The scheduler makes the commercial decision unilaterally, typically defaulting to the contractual penalty (Customer A) without presenting the strategic risk (Customer B). Or the scheduler tries to split the capacity equally, resulting in both orders being late.
+
+**Expert Approach:**
+1. Quantify both scenarios precisely:
+ - **Prioritise A:** Customer A ships Thursday (on time). Customer B ships the following Monday (3 days late). Customer B cost: potential $8M contract risk, unquantifiable but real.
+ - **Prioritise B:** Customer B ships Friday (on time). Customer A ships Saturday (2 days late). Customer A cost: $50,000 in contractual penalties + relationship damage.
+ - **Split capacity:** Customer A ships Friday (1 day late, $25K penalty). Customer B ships Monday (3 days late, contract risk).
+2. Identify capacity recovery options:
+ - Saturday overtime on the CNC (8 hours, cost ~$3,200). If authorised, both orders can be completed on time: A by Thursday, B by Saturday.
+ - Subcontract the simpler machining operations for Customer B to a qualified external shop, freeing 8 hours of CNC capacity for Customer A. Cost: $4,500 for subcontracting + expedited freight.
+3. Present the tradeoff matrix to the production manager and sales director with recommended option (overtime or subcontracting, not splitting capacity). Include the cost comparison.
+4. Once the decision is made, re-sequence the entire CNC schedule for the week. Lock the frozen zone on the decided sequence. Communicate to both customers.
+
+**Documentation Required:**
+- Capacity analysis showing the 16-hour shortfall
+- Tradeoff matrix with financial exposure for each scenario
+- Recommended recovery options with cost estimates
+- Management decision record (who decided, which option, rationale)
+- Customer communication log
+
+**Resolution Timeline:**
+- Monday AM: Both rush orders received
+- Monday AM + 2 hours: Capacity analysis and tradeoff matrix completed
+- Monday AM + 4 hours: Management decision
+- Monday PM: Re-sequenced schedule published, customers notified
+
+---
+
+### Edge Case 4: MRP Phantom Demand from BOM Error
+
+**Situation:**
+The scheduler notices that MRP has generated a planned production order for 3,000 units of a sub-component (Part #SC-4420, a machined bracket) with a due date in 2 weeks. This is unusual — this part typically runs in batches of 500 for the two product families that consume it. A check of the current sales orders and forecast shows demand for only 800 units over the next 6 weeks. The MRP-generated demand of 3,000 appears to be phantom.
+
+Investigation reveals that an engineer updated the BOM for a new product variant (not yet released) and accidentally set the quantity-per of SC-4420 to 12 instead of 1 on the master BOM. The MRP explosion multiplied forecasted demand for the new variant (250 units) by 12, generating 3,000 units of phantom demand. The BOM error has not yet been caught by engineering.
+
+**Why It's Tricky:**
+Scheduling systems trust MRP output. If the scheduler blindly converts the planned order to a production order and schedules it, the plant will produce 2,200 units of unwanted inventory, consuming 44 hours of machining capacity that was needed for real customer demand. But if the scheduler ignores MRP output without proper verification, they risk missing legitimate demand.
+
+**Common Mistake:**
+Scheduling the MRP-generated order without questioning it ("the system says we need it"), or deleting it without notifying engineering about the BOM error (the error persists and generates phantom demand again in the next MRP run).
+
+**Expert Approach:**
+1. **Verify the anomaly:** Compare the MRP-generated demand to the trailing 6-month demand history for SC-4420. A 3× spike with no corresponding sales order or forecast increase is a red flag.
+2. **Trace the demand:** Use MRP pegging (SAP: MD04/MD09, Oracle: pegging inquiry) to trace the planned order back to the parent demand that generated it. This reveals which parent product's BOM is driving the demand.
+3. **Identify the root cause:** The pegging trace points to the new product variant BOM. Compare the BOM quantity-per to the engineering drawing — the drawing shows 1 unit per assembly, the BOM shows 12.
+4. **Do not schedule the phantom demand.** Place a hold on the planned order with a note explaining the suspected BOM error.
+5. **Notify engineering immediately.** Provide the specific BOM line, the quantity discrepancy, and the MRP impact. Request urgent correction.
+6. **Schedule the real demand:** Create a production order for the actual 800-unit requirement and sequence it normally.
+7. **Verify the fix:** After engineering corrects the BOM, re-run MRP for SC-4420 and confirm the planned orders now align with expected demand.
+
+**Documentation Required:**
+- Anomaly detection: what triggered the investigation (volume spike, capacity conflict)
+- MRP pegging trace results
+- BOM error details (parent item, line item, incorrect vs. correct quantity)
+- Engineering notification with correction request
+- Production order for actual demand
+- Verification after BOM correction
+
+**Resolution Timeline:**
+- Day 1: Anomaly detected during schedule review
+- Day 1 + 2 hours: Pegging trace and root cause identified
+- Day 1 + 4 hours: Engineering notified, phantom order held
+- Day 2–3: Engineering corrects BOM, MRP re-run
+- Day 3: Verified — phantom demand eliminated
+
+---
+
+### Edge Case 5: Quality Hold on WIP Inventory Affecting Downstream
+
+**Situation:**
+A metal fabricator discovers a dimensional defect on a batch of 200 stamped chassis frames at the weld inspection station. The defect — a hole pattern shifted 2mm from specification due to a worn die — affects the entire batch produced since the last die change 3 shifts ago. Of the 200 affected frames: 80 are in welding (current operation), 60 have completed welding and are in paint queue, and 60 have completed paint and are in final assembly staging. Final assembly is the plant's constraint, and these 60 painted frames were scheduled to feed the constraint starting tomorrow morning. The customer (a commercial HVAC manufacturer) has a firm delivery commitment for 150 assembled units on Friday.
+
+**Why It's Tricky:**
+The quality hold cascades across three production stages. Some units may be reworkable (the hole pattern might be re-drilled), but rework adds operations to the routing and consumes capacity. The constraint (final assembly) will starve tomorrow if the 60 painted frames are quarantined. And the die that caused the defect needs to be replaced before more frames can be stamped, adding a maintenance operation to the schedule.
+
+**Common Mistake:**
+Quarantining only the 80 frames at welding (the point of detection) and allowing the 60 painted frames to proceed to assembly. If the defect makes assembly impossible or causes field failures, the cost of rework/recall after assembly is 5–10× the cost of catching it now.
+
+**Expert Approach:**
+1. **Full containment:** Quarantine all 200 frames across all three stages immediately. Tag, segregate, and document. No exceptions — even frames that "look fine" at paint stage may have the shifted hole pattern.
+2. **Assess reworkability:** Can the 2mm shift be corrected? Options:
+ - Re-drill the hole pattern at the correct location (if material allows, the shifted holes will remain as cosmetic defects — check if customer spec allows).
+ - Weld-fill the incorrect holes and re-drill (expensive, time-consuming, may not pass NDT for structural components).
+ - Scrap all 200 and restart from raw material (if re-drilling is not viable).
+3. **Schedule the constraint feed:** The constraint (final assembly) needs 60 frames tomorrow. If rework is feasible and fast enough:
+ - Expedite rework of the 60 painted frames first (they are furthest along).
+ - Schedule rework as an additional operation in the routing with its own time estimate.
+ - If rework takes 0.5 hours per frame and you assign 2 rework operators, 60 frames = 15 hours = 2 shifts.
+ - The constraint will be short frames for tomorrow's day shift. Can you pull forward other work at the constraint (different product) to fill the gap? If yes, do that and push the HVAC assembly to tomorrow's night shift or Wednesday.
+4. **Fix the die:** Replace or re-sharpen the stamping die before producing any new frames. Add a first-piece dimensional inspection requirement after the die change. If the die is a custom tool with a 2-week replacement lead time, have tooling assess whether the current die can be ground and requalified as a temporary measure.
+5. **Customer communication:** If Friday delivery is at risk, notify the customer by end of business today. Provide a revised ETA based on the rework timeline.
+
+**Documentation Required:**
+- Defect description, quantity affected, production stages
+- Containment actions and quarantine locations
+- Rework assessment (feasibility, time, cost)
+- Revised schedule showing constraint feed plan
+- Die replacement/repair plan
+- Customer notification (if delivery impacted)
+- CAPA for die wear monitoring (preventive inspection schedule)
+
+**Resolution Timeline:**
+- Hour 0: Defect detected at weld inspection
+- Hour 0–1: Full containment across all stages
+- Hour 1–3: Rework feasibility assessment
+- Hour 3–4: Revised schedule published with rework operations
+- Hour 4: Customer notified if delivery impacted
+- Day 2–3: Rework completed, constraint fed
+- Week 1: Die replaced or requalified
+
+---
+
+### Edge Case 6: Equipment Breakdown at the Constraint
+
+**Situation:**
+The main CNC horizontal boring mill — the plant's constraint for large machining operations — suffers a hydraulic pump failure at 9:15 AM on a Wednesday. Maintenance assessment: pump replacement requires 6–8 hours, but the replacement pump must be sourced from the OEM distributor 4 hours away. Realistic return-to-service: Thursday 6:00 AM (20+ hours of constraint downtime). Current work in the machine: a $38,000 defence contract part, 6 hours into an 8-hour operation — incomplete, cannot be removed without scrapping. 14 additional jobs are queued behind it, representing $220,000 in customer orders due within 2 weeks.
+
+**Why It's Tricky:**
+Every hour of constraint downtime directly reduces plant throughput. 20 hours at a constraint generating $800/hour in throughput = $16,000 in lost output. The defence part in the machine presents a dilemma: can it be completed when the machine restarts (will the part datum be preserved?), or is it scrap?
+
+**Common Mistake:**
+Waiting for the repair to complete before re-planning. By then, 20 hours of schedule disruption have cascaded through the plant with no mitigation.
+
+**Expert Approach:**
+1. **Immediate (0–15 min):**
+ - Confirm maintenance's repair estimate. Ask: is there a faster temporary fix (bypass, rental equipment)? Can the OEM ship the pump by overnight freight instead of driving?
+ - Determine if the in-machine part can resume after repair. Consult the machinist: are the datum offsets preserved? If the machine can restart the interrupted operation from the last completed tool path, the part is salvageable. If not, it may need to be re-fixtured and re-qualified, adding 2–3 hours but saving the $38,000 part.
+2. **Short-term (15 min – 2 hours):**
+ - Identify alternate routings: which of the 14 queued jobs can be processed on a smaller vertical CNC? The tolerances may allow some jobs to run on alternate equipment, even if cycle times are longer. Move those jobs immediately.
+ - Re-sequence remaining jobs by customer priority (EDD + customer tier weighting). When the constraint restarts Thursday AM, the first job in the queue must be the highest-priority item.
+ - Calculate customer impacts: which of the 14 jobs will miss due dates? Prepare a customer notification for each affected order.
+3. **Medium-term (2–20 hours, while machine is down):**
+ - Pre-stage everything for the queued jobs: tooling, raw material, fixtures, programs, operator assignments. When the machine restarts, the first job should begin within 15 minutes of the machine's green light.
+ - Evaluate whether Saturday overtime (8–16 hours) can recover the lost production. Cost of overtime vs. cost of late deliveries.
+ - Contact qualified external machining shops for the most at-risk orders. Can they process any of the 14 jobs faster than your recovery schedule?
+4. **Recovery (Thursday AM onward):**
+ - Restart with the salvaged in-machine part (if viable) or load the highest-priority queued job.
+ - Run the constraint through all breaks and shift changes (stagger operators).
+ - Monitor recovery pace hourly against the recovery schedule.
+
+**Documentation Required:**
+- Breakdown time, root cause, repair timeline
+- In-machine part assessment (salvageable Y/N, additional cost)
+- Alternate routing analysis for queued jobs
+- Customer impact list with revised ETAs
+- Overtime/subcontracting cost analysis
+- Recovery schedule with hourly milestones
+
+**Resolution Timeline:**
+- 9:15 AM: Breakdown
+- 9:15–9:30 AM: Maintenance assessment and pump sourcing
+- 9:30–11:00 AM: Alternate routing analysis, re-sequencing, customer notifications
+- 11:00 AM – Thursday 6:00 AM: Pre-staging, subcontracting decisions, recovery planning
+- Thursday 6:00 AM+: Machine restarts, recovery schedule executed
+- Friday: Recovery progress assessment — overtime decision for Saturday
+
+---
+
+### Edge Case 7: Supplier Delivers Wrong Material Mid-Run
+
+**Situation:**
+A structural steel fabricator is midway through a production run of 100 beam assemblies for a commercial construction project. Each assembly requires Grade 350 structural steel plate (AS/NZS 3678). At 2:00 PM, the quality inspector checking the second material delivery of the day discovers the mill certificates show Grade 250 instead of Grade 350. The first delivery (Grade 350, correct) fed the first 40 assemblies. The second delivery (Grade 250, wrong) has been kitted into the staging area for assemblies 41–70, and 12 plates from this delivery have already been cut and are at the welding station.
+
+**Why It's Tricky:**
+Grade 250 steel has lower yield strength than Grade 350 — assemblies made from it could be structurally inadequate and unsafe. The 12 cut plates cannot be used. But 28 plates from the wrong delivery are still uncut and could be returned. The production line is currently running and operators are about to start welding the incorrect material.
+
+**Common Mistake:**
+Continuing production and hoping the customer won't notice (this is a structural integrity and safety issue — non-negotiable). Or shutting down the entire line when only assemblies 41–70 are affected — assemblies 71–100 can use material from a different source if available.
+
+**Expert Approach:**
+1. **Stop welding immediately** on any piece using the Grade 250 material. Pull the 12 cut plates from the welding station and quarantine them with clear "HOLD — WRONG MATERIAL" tags.
+2. **Segregate the remaining 28 uncut plates** from the wrong delivery. These can be returned to the supplier or used for non-structural orders that specify Grade 250.
+3. **Continue production on assemblies 71–100** using material from existing Grade 350 stock (check if there is sufficient on-hand inventory from other purchase orders or stock). If Grade 350 stock is available for assemblies 71–100, the line does not need to stop entirely.
+4. **Assemblies 41–70 are now blocked.** Contact the supplier for emergency replacement of 30 Grade 350 plates. Demand same-day or next-day delivery at the supplier's cost (this is a supplier error). If the supplier cannot respond fast enough, source from an alternative supplier.
+5. **The 12 cut plates** in Grade 250 are scrap for this project. Calculate the scrap cost (material + cutting labour) and include it in the supplier claim.
+6. **Reschedule assemblies 41–70** to start after replacement material arrives. In the meantime, sequence assemblies 71–100 first (if material is available) to keep the welding line productive.
+7. **Notify the customer** if the construction project delivery timeline is affected. For structural steel, customers prefer a delay over incorrect material grade — this is a safety issue.
+
+**Documentation Required:**
+- Material non-conformance report with mill certificate evidence
+- Quarantine records for the 12 cut plates and 28 uncut plates
+- Supplier notification and replacement delivery commitment
+- Revised production schedule showing assemblies 71–100 pulled forward
+- Scrap cost calculation for the supplier claim
+- Customer notification (if delivery impacted)
+
+---
+
+### Edge Case 8: Overtime Ban During Peak Demand
+
+**Situation:**
+A consumer electronics assembly plant is entering its busiest 6-week period (back-to-school and early holiday orders). The production plan requires 132% of standard capacity at the constraint (SMT pick-and-place line) to meet all customer commitments. Normally, 32% of capacity comes from Saturday overtime shifts. However, the union just notified management that it is invoking the collective agreement clause limiting overtime to 5 hours per employee per week (down from the usual 15-hour soft cap) due to a dispute over shift differential rates. Negotiations are expected to take 3–5 weeks.
+
+**Why It's Tricky:**
+The plant was counting on Saturday overtime as the primary capacity lever. Without it, 32% of demand is unfillable. But the 5-hour limit still allows some daily overtime (1 hour/day Mon–Fri = 5 hours/week), which partially offsets. The scheduler must find 20–25% additional effective capacity from other sources while respecting the union constraint.
+
+**Common Mistake:**
+Pressuring operators to work "off the books" (violates the collective agreement and exposes the company to legal liability). Or accepting a 20–25% shortfall without exploring all alternatives.
+
+**Expert Approach:**
+1. **Quantify the gap precisely:** Standard capacity at constraint = 120 hours/week. Required = 158.4 hours. Overtime now available = 1 hour/day × 5 days × number of qualified operators. If 4 operators run the SMT line and each can do 5 hours/week OT, that's 20 hours/week of overtime capacity, bringing effective capacity to 140 hours. Remaining gap: 18.4 hours/week.
+2. **Exploit the constraint (no capital):**
+ - Reduce changeovers on SMT: consolidate product families, campaign-schedule similar board types together. Target: recover 4–6 hours/week from reduced changeover time.
+ - Run through all breaks and shift changes with staggered relief operators. Target: recover 2–3 hours/week.
+ - Reduce micro-stops through preventive maintenance during non-production hours. Target: recover 1–2 hours/week.
+3. **Temporary labour:** Can temporary agency operators run non-constraint operations, freeing experienced operators to double up at the constraint? The SMT line requires certification, but downstream operations (manual assembly, testing, packaging) may accept temporary labour.
+4. **Subcontract non-constraint work:** If downstream operations (conformal coating, testing) can be subcontracted, the freed-up internal capacity can be redirected to support constraint throughput (material handling, staging, quality inspection at the SMT line).
+5. **Customer prioritisation:** If the gap cannot be fully closed, rank customer orders by value and contractual penalty exposure. Allocate constraint capacity to the highest-priority orders first. Negotiate delivery extensions with lower-priority customers before the original due date — proactive notification preserves the relationship.
+6. **Demand shaping:** Work with sales to shift some orders from the peak 6-week window to the 2 weeks before or after, if customers have flexibility. Even moving 5% of demand out of peak reduces the capacity gap significantly.
+
+**Documentation Required:**
+- Capacity analysis showing the gap (hours/week) with and without overtime
+- Constraint exploitation plan with estimated recovery per initiative
+- Temporary labour and subcontracting options with cost and timeline
+- Customer prioritisation matrix
+- Demand shaping proposals to sales
+- Weekly progress tracking against the gap closure plan
+
+---
+
+### Edge Case 9: Customer Order Change After Production Started
+
+**Situation:**
+A custom industrial equipment manufacturer is 60% through a production order for Customer X: 20 hydraulic press frames, each with a 3-week machining cycle. 12 frames are complete through machining and in welding. 4 frames are in machining. 4 frames have not started (raw material cut but not machined). Customer X contacts sales to change the specification: they now need 15 frames at the original spec and 5 frames at a modified spec (different mounting hole pattern, additional reinforcement welds). The modified spec requires re-programming the CNC, a different welding fixture, and a revised quality inspection plan. Delivery date is unchanged.
+
+**Why It's Tricky:**
+The 12 completed frames and 4 in-process frames are at the original spec. If the change applies to any of these, the rework cost is substantial (re-machining mounting holes, adding welds to finished frames). The 4 unstarted frames can be built to the new spec without rework. But the customer wants 5 modified frames, and only 4 are unstarted.
+
+**Common Mistake:**
+Accepting the change without quantifying the rework cost and schedule impact, or rejecting the change outright without exploring options.
+
+**Expert Approach:**
+1. **Analyse the change impact by production stage:**
+ - 4 unstarted frames: can be built to modified spec with no rework. CNC reprogramming takes 4 hours. Welding fixture modification takes 6 hours.
+ - 4 frames in machining: modification requires adding the new mounting holes, which can be done as an additional machining operation before the frames leave CNC. Added time: 2 hours per frame = 8 hours.
+ - 12 completed frames at welding: modification would require returning frames to CNC (re-fixturing, new hole pattern), then additional welding operations. Cost: $1,200 per frame rework + 4 hours per frame on the CNC constraint. This is expensive and uses 48 hours of constraint capacity.
+2. **Propose the least-cost solution:**
+ - Build 4 unstarted frames to modified spec.
+ - Modify 1 of the 4 in-machining frames (the one least progressed) to modified spec. This gives Customer X their 5 modified frames.
+ - Complete the remaining 15 frames at original spec as planned.
+ - Total added cost: CNC reprogramming (4 hrs) + welding fixture modification (6 hrs) + additional machining on the modified in-process frame (2 hrs) = 12 hours added to the schedule.
+3. **Price the change:** Calculate the total cost (labour, material, fixture modification, schedule disruption) and issue a change order cost estimate to Customer X before executing. The customer should approve the cost delta.
+4. **Schedule the change:** Insert the CNC reprogramming and fixture modification into the schedule. The 4 unstarted frames are re-routed to the modified spec routing. The 1 in-process frame gets an additional operation added to its routing.
+5. **Assess delivery impact:** 12 hours added to the critical path. Can this be absorbed within the original delivery date? If not, negotiate a 2-day extension or authorize overtime to recover the 12 hours.
+
+**Documentation Required:**
+- Engineering change analysis showing impact per production stage
+- Rework cost estimate per frame (by stage)
+- Recommended solution with minimum cost/disruption
+- Change order cost estimate for customer approval
+- Revised schedule showing added operations
+- Delivery impact assessment
+
+---
+
+### Edge Case 10: New Product Introduction Competing with Existing Orders
+
+**Situation:**
+A precision stamping company has been awarded a new contract for an automotive EV battery enclosure (a high-profile new product introduction, or NPI). The NPI requires 3 trial production runs over the next 6 weeks to qualify the tooling, validate the process, and produce samples for customer approval. Each trial run requires 8 hours on the 400-ton stamping press (the plant's constraint) plus 4 hours of changeover and die tryout between runs. The constraint is already running at 88% utilisation with existing customer orders. The NPI trial runs need 36 hours of constraint time over 6 weeks (6 hours/week average), which would push constraint utilisation to 93% — within capacity but with almost no buffer.
+
+**Why It's Tricky:**
+NPI trial runs are unpredictable: the first run may reveal tooling issues requiring extended die adjustment (adding 4–8 hours), scrap rates on trial runs are typically 10–30% (vs. 2–3% for production runs), and engineering may need to stop the trial for measurements, adjustments, and design iterations. A trial run scheduled for 8 hours may actually consume 12–16 hours when interruptions are factored in.
+
+**Common Mistake:**
+Scheduling NPI trials into standard production slots and expecting them to run on time. When the trial overruns, it displaces existing customer orders and creates cascading delays.
+
+**Expert Approach:**
+1. **Do not schedule NPI trials at scheduled utilisation.** The 8-hour nominal trial time should be planned as a 14-hour window (8 hours production + 4 hours changeover + 2 hours contingency for tooling issues). This is realistic, not pessimistic, for first and second trials.
+2. **Schedule trial runs at the end of the week** (Friday PM or Saturday) when any overrun pushes into the weekend rather than into Monday's committed production schedule. If the trial finishes early, the slot converts to weekend overtime production (recovering any capacity borrowed from the week).
+3. **Reserve a "trial buffer" in the weekly schedule:** Block 14 hours per week as tentatively reserved for NPI. If the trial proceeds on schedule, this time is used as planned. If the trial is cancelled or postponed (common for NPIs), the buffer converts to regular production or maintenance.
+4. **Protect existing customer commitments:** No existing order should have its due date moved to accommodate the NPI trial. If constraint capacity cannot accommodate both, escalate to management: the NPI trial schedule may need to extend beyond 6 weeks, or the plant may need Saturday overtime to create the capacity.
+5. **Assign the most experienced setup technician and stamping operator** to the NPI trials. Trial-run productivity is heavily dependent on operator skill in adjusting die settings and recognising incipient defects. A junior operator on a trial run will consume 30–50% more time.
+6. **After each trial run, update the time estimate** for the next trial. If Trial 1 took 14 hours and produced 15% scrap, plan Trial 2 at 12 hours (process should be improving) but keep the full 14-hour buffer until proven otherwise.
+
+**Documentation Required:**
+- NPI trial schedule with buffered time estimates
+- Constraint capacity analysis showing impact on existing orders
+- Contingency plan if trial overruns
+- Customer communication plan if existing orders are at risk
+- Trial results and time actuals for updating subsequent trial estimates
+- Post-trial tooling qualification report
+
+---
+
+### Edge Case 11: Simultaneous Material Shortage and Equipment Degradation
+
+**Situation:**
+A food processing plant producing canned soups faces two simultaneous problems: (1) the primary tomato paste supplier is 4 days late on a delivery that was supposed to arrive Monday, affecting all tomato-based soup production scheduled for this week, and (2) the retort (sterilisation vessel) — the plant's constraint — has developed a slow steam leak that reduces its effective cycle time by 12% (each batch takes 45 minutes instead of 40 minutes). Maintenance can fix the leak during a planned maintenance window on Saturday, but running the retort at reduced capacity all week compounds the supplier delay.
+
+**Expert Approach:**
+1. Re-sequence the week to run non-tomato soup products (chicken, vegetable, cream-based) first while waiting for the tomato paste delivery. This keeps the retort running even at reduced capacity.
+2. Calculate the effective capacity loss: 12% longer cycles = ~12% throughput reduction at the constraint. Over a 120-hour production week, this is 14.4 hours of lost capacity, equivalent to roughly 18 batches (at 48 min/batch effective).
+3. When the tomato paste arrives (projected Thursday), re-sequence tomato soups with the most urgent due dates first.
+4. Evaluate whether Saturday maintenance can be pulled forward to Wednesday night (sacrificing one night shift of production but restoring full capacity for Thursday–Friday).
+5. Calculate the net capacity impact of early maintenance vs. running degraded all week: early fix loses 8 hours of production but recovers 12% efficiency for remaining 40+ hours = net gain of ~4.8 hours.
+6. Customer priority: rank all orders by delivery date and penalty risk. Allocate retort capacity accordingly.
+
+---
+
+### Edge Case 12: ERP System Upgrade During Production Week
+
+**Situation:**
+IT has scheduled an ERP system upgrade (SAP ECC to S/4HANA migration cutover) for the upcoming weekend, with the system offline from Friday 6:00 PM to Monday 6:00 AM. The plant runs 24/7 production. During the outage, operators cannot confirm operations, material transactions cannot be posted, and work order status cannot be updated. The scheduling tool (which reads from SAP) will not receive real-time data.
+
+**Expert Approach:**
+1. Print all work orders, routings, BOMs, and the production schedule for Friday PM through Monday AM. Distribute physical copies to every shift supervisor and work centre.
+2. Pre-issue all materials needed for weekend production. Complete all goods issues in SAP before 6:00 PM Friday. Operators should not need to perform material transactions during the outage.
+3. Implement manual shop floor tracking: paper travellers accompanying each batch, operator log sheets recording start/end times, quantities, and scrap.
+4. Freeze the schedule for the weekend — no re-sequencing unless a genuine disruption (breakdown, quality hold) occurs. Without system support, ad-hoc schedule changes are extremely error-prone.
+5. Monday AM: enter all weekend transactions into the new system. This "catch-up" data entry will take 2–4 hours. Assign a dedicated team. Verify inventory balances match physical counts before releasing the Monday schedule.
+6. Have IT on standby for Monday morning to resolve any data migration issues that affect production records.
+
+**Documentation Required:**
+- Pre-printed schedule and work order packets
+- Material pre-issue verification checklist
+- Manual tracking forms and instructions
+- Monday catch-up data entry plan
+- IT escalation contacts for Monday morning
+
+**Resolution Timeline:**
+- Friday − 1 week: Print all production documentation, verify completeness
+- Friday − 2 days: Pre-issue all weekend materials in SAP
+- Friday 6:00 PM: System goes offline. Switch to manual tracking.
+- Saturday–Sunday: Manual operations with paper travellers
+- Monday 6:00 AM: System restored. Begin catch-up data entry.
+- Monday 10:00 AM: Inventory verification and schedule release for Monday production
+
+---
+
+### Edge Case 13: Batch Traceability Contamination — Product Recall Scenario
+
+**Situation:**
+A medical device manufacturer receives a supplier notification that a lot of surgical-grade stainless steel (Heat #A7742) may contain elevated levels of nickel beyond the ASTM F138 specification. The supplier is still testing, but has issued a precautionary advisory. The plant's records show Heat #A7742 was received 3 weeks ago and has been consumed across 14 production work orders for 3 different product families (hip implant stems, bone screws, and spinal rods). Some finished goods from these work orders have already shipped to 4 hospital systems.
+
+**Why It's Tricky:**
+Full traceability is mandatory under FDA 21 CFR Part 820 for medical devices. The scheduler must immediately identify every work order, every operation, every batch that consumed material from Heat #A7742. Some of this material may be in WIP across multiple production stages. A false-positive (the material is actually fine) means the quarantine was unnecessary but the disruption was real. A false-negative (failing to quarantine all affected units) could result in a Class I recall.
+
+**Common Mistake:**
+Quarantining only the known remaining raw material from Heat #A7742 and missing the WIP and finished goods. Or waiting for the supplier's final test results before acting (which could take 5–7 business days).
+
+**Expert Approach:**
+1. **Immediate lot trace (Hour 0–2):** Run a forward lot trace from Heat #A7742 through every production stage. In the ERP, trace the material receipt to every goods issue, then to every work order that consumed it, then to every finished goods batch, then to every shipment.
+2. **Quarantine all affected WIP (Hour 0–4):** Every work-in-process piece traceable to Heat #A7742 must be physically segregated and tagged with "QUALITY HOLD — SUPPLIER ADVISORY" status. Update work order status in the ERP to "blocked."
+3. **Identify shipped finished goods:** For units already shipped, prepare a device history record (DHR) extract for the quality team. They will assess whether a customer notification or field action is required.
+4. **Re-schedule all affected work orders:** These are now blocked. Remove them from the active schedule. Calculate the impact on customer deliveries. The 14 work orders represent significant production volume — their removal creates a capacity surplus at some work centres and a delivery shortfall.
+5. **Fill the capacity gap:** Pull forward work orders for unaffected product families. Keep the constraint running on unaffected work. The quarantine should not idle the constraint if other schedulable work exists.
+6. **Monitor the supplier investigation:** Request daily updates. If the material passes testing (false alarm), the quarantined WIP can be released and re-inserted into the schedule. If the material fails, transition from quarantine to scrap/rework disposition.
+7. **Schedule replacement production:** If the quarantined material is confirmed non-conforming, replacement raw material must be ordered and new work orders created. Calculate the lead time for replacement material + production to meet customer delivery obligations.
+
+**Documentation Required:**
+- Full forward lot trace from Heat #A7742
+- Quarantine records for all WIP and finished goods
+- Shipped goods report for quality team
+- Revised schedule excluding quarantined work orders
+- Replacement material purchase order
+- Customer notification drafts (for quality team review)
+- Daily supplier investigation status updates
+
+**Resolution Timeline:**
+- Hour 0: Supplier advisory received
+- Hour 0–2: Lot trace completed, scope of exposure quantified
+- Hour 2–4: All affected WIP quarantined, schedule revised
+- Hour 4–8: Customer delivery impact assessed, replacement material ordered
+- Day 2–7: Awaiting supplier test results, running unaffected production
+- Day 7+: Disposition decision (release or scrap), recovery schedule published
+
+---
+
+### Edge Case 14: Power Curtailment Order During Peak Production
+
+**Situation:**
+During a summer heat wave, the regional utility issues a mandatory curtailment order requiring the plant to reduce electrical consumption by 30% during peak hours (1:00 PM – 7:00 PM) for the next 5 business days. The plant's major electrical loads are: arc welding stations (35% of load), CNC machining (25%), HVAC/lighting (20%), and electric furnaces (20%). The constraint work centre is a CNC machining cell. Shutting down any production equipment during peak hours will reduce output. Non-compliance with the curtailment order carries fines of $50,000/day.
+
+**Expert Approach:**
+1. **Load analysis:** Identify which equipment can be shut down during peak hours with the least production impact. HVAC cannot be fully shut down (heat stress safety risk for operators), but setpoint can be raised by 3–4°F to reduce load by ~30% of HVAC consumption.
+2. **Shift heavy loads to off-peak:** Move arc welding operations to the early morning (5:00 AM – 1:00 PM) and evening (7:00 PM – 1:00 AM) shifts. Welding is labour-intensive but electrically heavy — shifting it avoids most of the curtailment window.
+3. **Protect the constraint:** CNC machining is the constraint. Calculate whether CNC can run during the curtailment window if welding and furnaces are offline. If CNC alone is within the 70% power allowance, keep CNC running and idle the other major loads.
+4. **Electric furnace scheduling:** Pre-heat and pre-melt in the morning. Hold molten metal in insulated vessels during the curtailment window (thermal mass carries 4–6 hours). Resume furnace operations at 7:00 PM.
+5. **Reschedule the week:** Create two sub-schedules:
+ - Off-peak (5:00 AM – 1:00 PM and 7:00 PM – 5:00 AM): Full production, all work centres operational.
+ - Peak curtailment (1:00 PM – 7:00 PM): Constraint (CNC) running, welding and furnaces offline, non-electrical operations (manual assembly, inspection, packaging, material prep) active.
+6. **Labour adjustment:** Operators who normally work day shift welding are reassigned to manual operations during curtailment hours, then brought back to welding on an adjusted schedule. Check overtime implications — some operators may need split shifts.
+7. **Customer impact:** Calculate the throughput reduction from 5 days of restricted production. If the constraint runs during curtailment but non-constraints do not, the throughput impact may be small (constraint is the bottleneck). Quantify and notify affected customers if any delivery dates slip.
+
+**Documentation Required:**
+- Load analysis by equipment and time window
+- Curtailment compliance plan (submitted to utility if required)
+- Revised daily schedules for the 5-day curtailment period
+- Labour reassignment plan
+- Customer delivery impact assessment
+- Cost analysis: compliance plan cost vs. $50K/day non-compliance fine
+
+---
+
+### Edge Case 15: Concurrent Preventive Maintenance and Rush Order
+
+**Situation:**
+A stamping plant's quarterly preventive maintenance (PM) on the 600-ton press (the constraint) is scheduled for this Saturday, requiring a full 10-hour shutdown for die inspection, hydraulic system service, and electrical control calibration. On Thursday afternoon, the plant receives a rush order from its largest customer: 5,000 brackets due Wednesday of next week. The 600-ton press is the only machine that can stamp these brackets. The job requires 18 hours of press time. Without the Saturday PM, the bracket run can start Friday evening and finish Sunday afternoon, meeting the Wednesday deadline easily. With the PM, the bracket run cannot start until Sunday afternoon and will finish Tuesday, cutting it dangerously close to the Wednesday ship deadline.
+
+**Why It's Tricky:**
+Skipping or deferring PM on the constraint is a high-risk gamble. The PM schedule exists because the 600-ton press has a history of hydraulic seal failures when PM intervals stretch beyond the quarterly cycle. A hydraulic failure during the bracket run would be catastrophic — potentially damaging the die (a $45,000 asset), scrapping in-process work, and causing multiple days of unplanned downtime.
+
+**Expert Approach:**
+1. **Do not skip the PM.** The expected cost of a hydraulic failure (die damage + scrap + 3–5 days unplanned downtime + customer penalties) far exceeds the cost of any workaround.
+2. **Can the PM be compressed?** Consult maintenance: can the 10-hour PM be reduced to 6 hours by parallelising activities (two maintenance crews working simultaneously on hydraulics and electrical)? If so, the press is available Saturday evening instead of Sunday morning, giving an extra 8+ hours for the bracket run.
+3. **Can the PM be moved earlier?** If PM starts Friday night instead of Saturday morning, the press is available by Saturday morning. Friday night PM means cancelling Friday night production — calculate the lost production (probably 1 shift of lower-priority work) vs. the benefit of earlier bracket availability.
+4. **Can the bracket run be accelerated?** Check if the die can be modified for a 2-out configuration (stamping 2 brackets per stroke instead of 1). If tooling supports this and first-piece quality validates, the 18-hour job drops to 10 hours. This is a production engineering question, not just a scheduling question.
+5. **Recommended plan:** Move PM to Friday 10:00 PM – Saturday 8:00 AM (compressed to 10 hours or less). Start bracket run Saturday 8:00 AM. At 18 hours, the run finishes Sunday 2:00 AM. Ship Monday for Wednesday delivery — comfortable margin.
+6. **Backup plan:** If PM cannot be compressed or moved earlier, start the bracket run Sunday afternoon, run through Sunday night and Monday day shift (18 hours completion by Monday evening), and ship Tuesday for Wednesday delivery. This is tight but feasible. Add an overtime shift Monday evening as insurance.
+
+**Documentation Required:**
+- PM schedule analysis showing compression/shift options
+- Bracket run time calculation and earliest-start-time scenarios
+- Risk assessment of PM deferral (not recommended, but documented to explain the decision)
+- Customer delivery confirmation with the chosen plan
+- Maintenance crew availability for compressed PM schedule
+
+**Resolution Timeline:**
+- Thursday PM: Rush order received
+- Thursday PM + 2 hours: PM compression/shift analysis completed
+- Thursday end-of-day: Decision made, revised schedule published
+- Friday night or Saturday AM: PM begins
+- Saturday AM or PM: Bracket run begins
+- Sunday or Monday: Bracket run complete
+- Monday–Tuesday: Ship for Wednesday delivery
+
+---
+
+### Edge Case 16: Multi-Site Load Balancing Under Capacity Crunch
+
+**Situation:**
+A packaging company operates two plants 90 miles apart. Plant A specialises in rigid plastic containers (thermoforming + printing) and Plant B specialises in flexible pouches (form-fill-seal). Both plants have secondary capability in the other's specialty, but at 30–40% lower throughput rates. Plant A's thermoforming constraint is at 97% utilisation for the next 3 weeks. Plant B's form-fill-seal line is at 72%. A key customer (national retailer) has just increased their Q4 order for rigid containers by 25%, pushing Plant A's projected utilisation to 122%.
+
+**Why It's Tricky:**
+Moving rigid container production to Plant B is technically possible but operationally complex: different tooling must be transferred, operator cross-training is limited, Plant B's rigid container quality history is weaker, and the customer has approved Plant A as the manufacturing site (switching sites may require customer re-qualification, especially for food-contact packaging).
+
+**Common Mistake:**
+Accepting all incremental volume at Plant A and planning to "make it work" with overtime. At 122% utilisation, even maximum overtime only reaches ~108%, creating an inevitable 14% shortfall. Or refusing the incremental order without exploring Plant B as an option.
+
+**Expert Approach:**
+1. **Quantify the overflow precisely:** Plant A needs 22% more capacity = 26.4 hours/week over 3 weeks = 79.2 total overflow hours.
+2. **Assess Plant A's maximum realistic capacity:** Standard (120 hrs/week) + Saturday OT (16 hrs) + reduced changeovers (estimated 4 hrs recovery through better sequencing) = 140 hrs/week max. At 122% requirement = 146.4 hrs needed. Plant A can deliver 140 hrs, shortfall = 6.4 hrs/week = 19.2 hours over 3 weeks.
+3. **Assess Plant B's absorption capacity:** Plant B's rigid container capability runs at 70% of Plant A's throughput. 19.2 hours of Plant A work = 27.4 hours at Plant B's rate. Plant B has 33.6 hours of available capacity (120 × 28% headroom) — it can absorb the overflow.
+4. **Customer qualification:** Contact the customer's quality team to determine whether a temporary site switch requires re-qualification. For food-contact packaging, the answer is usually yes for a new site, but may be waived if both plants hold the same certifications (SQF, BRC, FDA registration) and use identical raw materials.
+5. **Tooling transfer plan:** Which moulds and print plates need to move to Plant B? What is the transfer time (transport + setup + qualification runs at Plant B)? Plan for 2–3 days of transfer activity before Plant B can begin producing.
+6. **Quality safeguard:** Assign Plant A's quality supervisor to Plant B for the first 2 days of the overflow production run. First-article inspection with full dimensional check before releasing production quantities.
+7. **Logistics:** Coordinate shipping from Plant B to the customer's DC. If the customer expects a single point of shipment, Plant B's output may need to be consolidated at Plant A before shipping.
+
+**Documentation Required:**
+- Capacity analysis for both plants over the 3-week horizon
+- Overflow volume calculation and Plant B absorption plan
+- Customer qualification requirement assessment
+- Tooling transfer schedule
+- Quality plan for Plant B overflow production
+- Logistics coordination plan
+- Cost comparison: overtime at Plant A vs. transfer + production at Plant B
+
+---
+
+### Edge Case 17: Seasonal Product Transition with Shared Tooling
+
+**Situation:**
+A consumer goods manufacturer produces both summer products (portable fans, outdoor lighting) and winter products (space heaters, humidifiers) on shared injection moulding and assembly lines. The seasonal transition begins in August: summer products wind down while winter products ramp up. Both product families share 6 of the plant's 10 injection moulding machines, requiring complete mould changes (4–6 hours per machine). The transition must happen while simultaneously filling the last summer orders (end-of-season clearance orders from retailers, due by August 31) and beginning the winter build-up (first winter shipments due September 15).
+
+**Why It's Tricky:**
+During the transition period, the plant needs to produce both summer and winter products on the same machines. Every mould change consumes 4–6 hours of production capacity. If you transition all 6 machines at once, you lose 24–36 hours of capacity in a single week — during the highest-demand period. If you transition one machine at a time, you maintain more capacity but stretch the transition over 3+ weeks, during which the schedule is constantly in flux with different machines running different product families.
+
+**Expert Approach:**
+1. **Phase the transition by machine and demand priority:**
+ - Weeks 1–2 (Aug 1–14): Keep all 6 machines on summer products. Fill all remaining summer orders.
+ - Week 3 (Aug 15–21): Transition 2 machines to winter moulds. These begin producing the highest-priority winter products.
+ - Week 4 (Aug 22–28): Transition 2 more machines. Now 4 winter, 2 summer.
+ - Week 5 (Aug 29 – Sep 4): Transition final 2 machines. All 6 on winter products.
+2. **Priority sequencing during transition:**
+ - Summer machines in Weeks 3–4 focus exclusively on committed retailer orders with firm due dates. No speculative production.
+ - Winter machines in Weeks 3–4 focus on long-lead-time components that downstream assembly needs by September 15.
+3. **Mould change scheduling:** Schedule all mould changes for Friday PM or Saturday AM, when the changeover downtime has the least impact on committed production (assuming the plant runs Mon–Fri with Saturday overtime available).
+4. **Buffer management:** Build 1 week of safety stock on critical summer components before Week 3 begins. This buffers downstream assembly from any transition-related disruptions on the moulding machines.
+5. **Labour coordination:** Mould changes require skilled tooling technicians. Ensure technician availability matches the changeover schedule — do not schedule 4 mould changes on the same day with only 2 technicians.
+
+**Documentation Required:**
+- Phased transition schedule showing machine-by-product assignment per week
+- Summer order backlog with due dates and machine requirements
+- Winter build-up schedule with component lead times
+- Mould change schedule with technician assignments
+- Safety stock build plan for transition buffer
+- Post-transition capacity verification (all winter moulds qualified and running at standard rates)
+
+**Resolution Timeline:**
+- Aug 1: Transition plan published to all departments
+- Aug 1–14: Summer production, safety stock build
+- Aug 15: First 2 machines transition — winter production begins
+- Aug 22: Second pair transitions
+- Aug 29: Final pair transitions — full winter production
+- Sep 5: Post-transition review — all machines at standard winter rates
+- Sep 15: First winter shipments
+
+---
+
+## Summary: Edge Case Pattern Recognition
+
+Experienced production schedulers recognise recurring patterns across these edge cases:
+
+| Pattern | Key Indicator | First Response |
+|---|---|---|
+| **Constraint shift** | WIP moving from one queue to another unexpectedly | Re-identify the constraint. Don't re-sequence unless shift persists. |
+| **Single-point-of-failure** | One operator, one machine, one supplier | Cross-train, qualify alternates, dual-source before the failure occurs. |
+| **Commercial vs. physical conflict** | Multiple customers need the same scarce resource | Quantify the tradeoff. Present options. Let management decide. |
+| **Data integrity failure** | MRP generating implausible demand, phantom inventory | Verify at the source. Trace the data. Fix the root before acting on bad data. |
+| **Cascading quality issue** | Defect detected late, affecting multiple production stages | Full containment first, rework assessment second, schedule recovery third. |
+| **External constraint imposed** | Utility curtailment, regulatory stop, weather | Protect the constraint. Shift flexible operations around the restriction. |
+| **Transition complexity** | Product mix changing, seasonal changeover, NPI | Phase the transition. Buffer between old and new. Don't try to flip everything at once. |
+
+The common thread: **never sacrifice the constraint's output for a non-constraint problem.** Every decision should be evaluated through the lens of: "Does this protect or harm throughput at the constraint?" If a disruption does not affect the constraint (directly or through buffer penetration), it is lower priority regardless of how visible or noisy it is on the shop floor.
diff --git a/web-app/public/skills/programmatic-seo/SKILL.md b/web-app/public/skills/programmatic-seo/SKILL.md
index 28a2b0c1..dd0cf288 100644
--- a/web-app/public/skills/programmatic-seo/SKILL.md
+++ b/web-app/public/skills/programmatic-seo/SKILL.md
@@ -1,6 +1,6 @@
---
name: programmatic-seo
-description: ">"
+description: >
Design and evaluate programmatic SEO strategies for creating SEO-driven pages
at scale using templates and structured data. Use when the user mentions
programmatic SEO, pages at scale, template pages, directory pages, location pages,
diff --git a/web-app/public/skills/python-pro/SKILL.md b/web-app/public/skills/python-pro/SKILL.md
index 97430766..d4c64386 100644
--- a/web-app/public/skills/python-pro/SKILL.md
+++ b/web-app/public/skills/python-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: python-pro
-description: "Master Python 3.12+ with modern features, async programming,"
+description: |
+ Master Python 3.12+ with modern features, async programming,
performance optimization, and production-ready practices. Expert in the latest
Python ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY
for Python development, optimization, or advanced Python patterns.
diff --git a/web-app/public/skills/quality-nonconformance/SKILL.md b/web-app/public/skills/quality-nonconformance/SKILL.md
new file mode 100644
index 00000000..e0a2f8ef
--- /dev/null
+++ b/web-app/public/skills/quality-nonconformance/SKILL.md
@@ -0,0 +1,250 @@
+---
+name: quality-nonconformance
+description: >
+ Codified expertise for quality control, non-conformance investigation, root
+ cause analysis, corrective action, and supplier quality management in
+ regulated manufacturing. Informed by quality engineers with 15+ years
+ experience across FDA, IATF 16949, and AS9100 environments. Includes NCR
+ lifecycle management, CAPA systems, SPC interpretation, and audit methodology.
+ Use when investigating non-conformances, performing root cause analysis,
+ managing CAPAs, interpreting SPC data, or handling supplier quality issues.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🔍"
+---
+
+## When to Use
+
+Use this skill when investigating product defects or process deviations, performing root cause analysis (RCA), managing Corrective and Preventive Actions (CAPA), interpreting Statistical Process Control (SPC) data, or auditing supplier quality.
+
+# Quality & Non-Conformance Management
+
+## Role and Context
+
+You are a senior quality engineer with 15+ years in regulated manufacturing environments — FDA 21 CFR 820 (medical devices), IATF 16949 (automotive), AS9100 (aerospace), and ISO 13485 (medical devices). You manage the full non-conformance lifecycle from incoming inspection through final disposition. Your systems include QMS (eQMS platforms like MasterControl, ETQ, Veeva), SPC software (Minitab, InfinityQS), ERP (SAP QM, Oracle Quality), CMM and metrology equipment, and supplier portals. You sit at the intersection of manufacturing, engineering, procurement, regulatory, and customer quality. Your judgment calls directly affect product safety, regulatory standing, production throughput, and supplier relationships.
+
+## Core Knowledge
+
+### NCR Lifecycle
+
+Every non-conformance follows a controlled lifecycle. Skipping steps creates audit findings and regulatory risk:
+
+- **Identification:** Anyone can initiate. Record: who found it, where (incoming, in-process, final, field), what standard/spec was violated, quantity affected, lot/batch traceability. Tag or quarantine nonconforming material immediately — no exceptions. Physical segregation with red-tag or hold-tag in a designated MRB area. Electronic hold in ERP to prevent inadvertent shipment.
+- **Documentation:** NCR number assigned per your QMS numbering scheme. Link to part number, revision, PO/work order, specification clause violated, measurement data (actuals vs. tolerances), photographs, and inspector ID. For FDA-regulated products, records must satisfy 21 CFR 820.90; for automotive, IATF 16949 §8.7.
+- **Investigation:** Determine scope — is this an isolated piece or a systemic lot issue? Check upstream and downstream: other lots from the same supplier shipment, other units from the same production run, WIP and finished goods inventory from the same period. Containment actions must happen before root cause analysis begins.
+- **Disposition via MRB (Material Review Board):** The MRB typically includes quality, engineering, and manufacturing representatives. For aerospace (AS9100), the customer may need to participate. Disposition options:
+ - **Use-as-is:** Part does not meet drawing but is functionally acceptable. Requires engineering justification (concession/deviation). In aerospace, requires customer approval per AS9100 §8.7.1. In automotive, customer notification is typically required. Document the rationale — "because we need the parts" is not a justification.
+ - **Rework:** Bring the part into conformance using an approved rework procedure. The rework instruction must be documented, and the reworked part must be re-inspected to the original specification. Track rework costs.
+ - **Repair:** Part will not fully meet the original specification but will be made functional. Requires engineering disposition and often customer concession. Different from rework — repair accepts a permanent deviation.
+ - **Return to Vendor (RTV):** Issue a Supplier Corrective Action Request (SCAR) or CAR. Debit memo or replacement PO. Track supplier response within agreed timelines. Update supplier scorecard.
+ - **Scrap:** Document scrap with quantity, cost, lot traceability, and authorized scrap approval (often requires management sign-off above a dollar threshold). For serialized or safety-critical parts, witness destruction.
+
+### Root Cause Analysis
+
+Stopping at symptoms is the most common failure mode in quality investigations:
+
+- **5 Whys:** Simple, effective for straightforward process failures. Limitation: assumes a single linear causal chain. Fails on complex, multi-factor problems. Each "why" must be verified with data, not opinion — "Why did the dimension drift?" → "Because the tool wore" is only valid if you measured tool wear.
+- **Ishikawa (Fishbone) Diagram:** Use the 6M framework (Man, Machine, Material, Method, Measurement, Mother Nature/Environment). Forces consideration of all potential cause categories. Most useful as a brainstorming framework to prevent premature convergence on a single cause. Not a root cause tool by itself — it generates hypotheses that need verification.
+- **Fault Tree Analysis (FTA):** Top-down, deductive. Start with the failure event and decompose into contributing causes using AND/OR logic gates. Quantitative when failure rate data is available. Required or expected in aerospace (AS9100) and medical device (ISO 14971 risk analysis) contexts. Most rigorous method but resource-intensive.
+- **8D Methodology:** Team-based, structured problem-solving. D0: Symptom recognition and emergency response. D1: Team formation. D2: Problem definition (IS/IS-NOT). D3: Interim containment. D4: Root cause identification (use fishbone + 5 Whys within 8D). D5: Corrective action selection. D6: Implementation. D7: Prevention of recurrence. D8: Team recognition. Automotive OEMs (GM, Ford, Stellantis) expect 8D reports for significant supplier quality issues.
+- **Red flags that you stopped at symptoms:** Your "root cause" contains the word "error" (human error is never a root cause — why did the system allow the error?), your corrective action is "retrain the operator" (training alone is the weakest corrective action), or your root cause matches the problem statement reworded.
+
+### CAPA System
+
+CAPA is the regulatory backbone. FDA cites CAPA deficiencies more than any other subsystem:
+
+- **Initiation:** Not every NCR requires a CAPA. Triggers: repeat non-conformances (same failure mode 3+ times), customer complaints, audit findings, field failures, trend analysis (SPC signals), regulatory observations. Over-initiating CAPAs dilutes resources and creates closure backlogs. Under-initiating creates audit findings.
+- **Corrective Action vs. Preventive Action:** Corrective addresses an existing non-conformance and prevents its recurrence. Preventive addresses a potential non-conformance that hasn't occurred yet — typically identified through trend analysis, risk assessment, or near-miss events. FDA expects both; don't conflate them.
+- **Writing Effective CAPAs:** The action must be specific, measurable, and address the verified root cause. Bad: "Improve inspection procedures." Good: "Add torque verification step at Station 12 with calibrated torque wrench (±2%), documented on traveler checklist WI-4401 Rev C, effective by 2025-04-15." Every CAPA must have an owner, a target date, and defined evidence of completion.
+- **Verification vs. Validation of Effectiveness:** Verification confirms the action was implemented as planned (did we install the poka-yoke fixture?). Validation confirms the action actually prevented recurrence (did the defect rate drop to zero over 90 days of production data?). FDA expects both. Closing a CAPA at verification without validation is a common audit finding.
+- **Closure Criteria:** Objective evidence that the corrective action was implemented AND effective. Minimum effectiveness monitoring period: 90 days for process changes, 3 production lots for material changes, or the next audit cycle for system changes. Document the effectiveness data — charts, rejection rates, audit results.
+- **Regulatory Expectations:** FDA 21 CFR 820.198 (complaint handling) and 820.90 (nonconforming product) feed into 820.100 (CAPA). IATF 16949 §10.2.3-10.2.6. AS9100 §10.2. ISO 13485 §8.5.2-8.5.3. Each standard has specific documentation and timing expectations.
+
+### Statistical Process Control (SPC)
+
+SPC separates signal from noise. Misinterpreting charts causes more problems than not charting at all:
+
+- **Chart Selection:** X-bar/R for continuous data with subgroups (n=2-10). X-bar/S for subgroups n>10. Individual/Moving Range (I-MR) for continuous data with subgroup n=1 (batch processes, destructive testing). p-chart for proportion defective (variable sample size). np-chart for count of defectives (fixed sample size). c-chart for count of defects per unit (fixed opportunity area). u-chart for defects per unit (variable opportunity area).
+- **Capability Indices:** Cp measures process spread vs. specification width (potential capability). Cpk adjusts for centering (actual capability). Pp/Ppk use overall variation (long-term) vs. Cp/Cpk which use within-subgroup variation (short-term). A process with Cp=2.0 but Cpk=0.8 is capable but not centered — fix the mean, not the variation. Automotive (IATF 16949) typically requires Cpk ≥ 1.33 for established processes, Ppk ≥ 1.67 for new processes.
+- **Western Electric Rules (signals beyond control limits):** Rule 1: One point beyond 3σ. Rule 2: Nine consecutive points on one side of the center line. Rule 3: Six consecutive points steadily increasing or decreasing. Rule 4: Fourteen consecutive points alternating up and down. Rule 1 demands immediate action. Rules 2-4 indicate systematic causes requiring investigation before the process goes out of spec.
+- **The Over-Adjustment Problem:** Reacting to common cause variation by tweaking the process increases variation — this is tampering. If the chart shows a stable process within control limits but individual points "look high," do not adjust. Only adjust for special cause signals confirmed by the Western Electric rules.
+- **Common vs. Special Cause:** Common cause variation is inherent to the process — reducing it requires fundamental process changes (better equipment, different material, environmental controls). Special cause variation is assignable to a specific event — a worn tool, a new raw material lot, an untrained operator on second shift. SPC's primary function is detecting special causes quickly.
+
+### Incoming Inspection
+
+- **AQL Sampling Plans (ANSI/ASQ Z1.4 / ISO 2859-1):** Determine inspection level (I, II, III — Level II is standard), lot size, AQL value, and sample size code letter. Tightened inspection: switch after 2 of 5 consecutive lots rejected. Normal: default. Reduced: switch after 10 consecutive lots accepted AND production stable. Critical defects: AQL = 0 with appropriate sample size. Major defects: typically AQL 1.0-2.5. Minor defects: typically AQL 2.5-6.5.
+- **LTPD (Lot Tolerance Percent Defective):** The defect level the plan is designed to reject. AQL protects the producer (low risk of rejecting good lots). LTPD protects the consumer (low risk of accepting bad lots). Understanding both sides is critical for communicating inspection risk to management.
+- **Skip-Lot Qualification:** After a supplier demonstrates consistent quality (typically 10+ consecutive lots accepted at normal inspection), reduce frequency to inspecting every 2nd, 3rd, or 5th lot. Revert immediately upon any rejection. Requires formal qualification criteria and documented decision.
+- **Certificate of Conformance (CoC) Reliance:** When to trust supplier CoCs vs. performing incoming inspection: new supplier = always inspect; qualified supplier with history = CoC + reduced verification; critical/safety dimensions = always inspect regardless of history. CoC reliance requires a documented agreement and periodic audit verification (audit the supplier's final inspection process, not just the paperwork).
+
+### Supplier Quality Management
+
+- **Audit Methodology:** Process audits assess how work is done (observe, interview, sample). System audits assess QMS compliance (document review, record sampling). Product audits verify specific product characteristics. Use a risk-based audit schedule — high-risk suppliers annually, medium biennially, low every 3 years plus cause-based. Announce audits for system assessments; unannounced audits for process verification when performance concerns exist.
+- **Supplier Scorecards:** Measure PPM (parts per million defective), on-time delivery, SCAR response time, SCAR effectiveness (recurrence rate), and lot acceptance rate. Weight the metrics by business impact. Share scorecards quarterly. Scores drive inspection level adjustments, business allocation, and ASL status.
+- **Corrective Action Requests (CARs/SCARs):** Issue for each significant non-conformance or repeated minor non-conformances. Expect 8D or equivalent root cause analysis. Set response deadline (typically 10 business days for initial response, 30 days for full corrective action plan). Follow up on effectiveness verification.
+- **Approved Supplier List (ASL):** Entry requires qualification (first article, capability study, system audit). Maintenance requires ongoing performance meeting scorecard thresholds. Removal is a significant business decision requiring procurement, engineering, and quality agreement plus a transition plan. Provisional status (approved with conditions) is useful for suppliers under improvement plans.
+- **Develop vs. Switch Decisions:** Supplier development (investment in training, process improvement, tooling) makes sense when: the supplier has unique capability, switching costs are high, the relationship is otherwise strong, and the quality gaps are addressable. Switching makes sense when: the supplier is unwilling to invest, the quality trend is deteriorating despite CARs, or alternative qualified sources exist with lower total cost of quality.
+
+### Regulatory Frameworks
+
+- **FDA 21 CFR 820 (QSR):** Covers medical device quality systems. Key sections: 820.90 (nonconforming product), 820.100 (CAPA), 820.198 (complaint handling), 820.250 (statistical techniques). FDA auditors specifically look at CAPA system effectiveness, complaint trending, and whether root cause analysis is rigorous.
+- **IATF 16949 (Automotive):** Adds customer-specific requirements on top of ISO 9001. Control plans, PPAP (Production Part Approval Process), MSA (Measurement Systems Analysis), 8D reporting, special characteristics management. Customer notification required for process changes and non-conformance disposition.
+- **AS9100 (Aerospace):** Adds requirements for product safety, counterfeit part prevention, configuration management, first article inspection (FAI per AS9102), and key characteristic management. Customer approval required for use-as-is dispositions. OASIS database for supplier management.
+- **ISO 13485 (Medical Devices):** Harmonized with FDA QSR but with European regulatory alignment. Emphasis on risk management (ISO 14971), traceability, and design controls. Clinical investigation requirements feed into non-conformance management.
+- **Control Plans:** Define inspection characteristics, methods, frequencies, sample sizes, reaction plans, and responsible parties for each process step. Required by IATF 16949 and good practice universally. Must be a living document updated when processes change.
+
+### Cost of Quality
+
+Build the business case for quality investment using Juran's COQ model:
+
+- **Prevention costs:** Training, process validation, design reviews, supplier qualification, SPC implementation, poka-yoke fixtures. Typically 5-10% of total COQ. Every dollar invested here returns $10-$100 in failure cost avoidance.
+- **Appraisal costs:** Incoming inspection, in-process inspection, final inspection, testing, calibration, audit costs. Typically 20-25% of total COQ.
+- **Internal failure costs:** Scrap, rework, re-inspection, MRB processing, production delays due to non-conformances, root cause investigation labor. Typically 25-40% of total COQ.
+- **External failure costs:** Customer returns, warranty claims, field service, recalls, regulatory actions, liability exposure, reputation damage. Typically 25-40% of total COQ but most volatile and highest per-incident cost.
+
+## Decision Frameworks
+
+### NCR Disposition Decision Logic
+
+Evaluate in this sequence — the first path that applies governs the disposition:
+
+1. **Safety/regulatory critical:** If the non-conformance affects a safety-critical characteristic or regulatory requirement → do not use-as-is. Rework if possible to full conformance, otherwise scrap. No exceptions without formal engineering risk assessment and, where required, regulatory notification.
+2. **Customer-specific requirements:** If the customer specification is tighter than the design spec and the part meets design but not customer requirements → contact customer for concession before disposing. Automotive and aerospace customers have explicit concession processes.
+3. **Functional impact:** Engineering evaluates whether the non-conformance affects form, fit, or function. If no functional impact and within material review authority → use-as-is with documented engineering justification. If functional impact exists → rework or scrap.
+4. **Reworkability:** If the part can be brought into full conformance through an approved rework process → rework. Verify rework cost vs. replacement cost. If rework cost exceeds 60% of replacement cost, scrap is usually more economical.
+5. **Supplier accountability:** If the non-conformance is supplier-caused → RTV with SCAR. Exception: if production cannot wait for replacement parts, use-as-is or rework may be needed with cost recovery from the supplier.
+
+### RCA Method Selection
+
+- **Single-event, simple causal chain:** 5 Whys. Budget: 1-2 hours.
+- **Single-event, multiple potential cause categories:** Ishikawa + 5 Whys on the most likely branches. Budget: 4-8 hours.
+- **Recurring issue, process-related:** 8D with full team. Budget: 20-40 hours across D0-D8.
+- **Safety-critical or high-severity event:** Fault Tree Analysis with quantitative risk assessment. Budget: 40-80 hours. Required for aerospace product safety events and medical device post-market analysis.
+- **Customer-mandated format:** Use whatever the customer requires (most automotive OEMs mandate 8D).
+
+### CAPA Effectiveness Verification
+
+Before closing any CAPA, verify:
+
+1. **Implementation evidence:** Documented proof the action was completed (updated work instruction with revision, installed fixture with validation, modified inspection plan with effective date).
+2. **Monitoring period data:** Minimum 90 days of production data, 3 consecutive production lots, or one full audit cycle — whichever provides the most meaningful evidence.
+3. **Recurrence check:** Zero recurrences of the specific failure mode during the monitoring period. If recurrence occurs, the CAPA is not effective — reopen and re-investigate. Do not close and open a new CAPA for the same issue.
+4. **Leading indicator review:** Beyond the specific failure, have related metrics improved? (e.g., overall PPM for that process, customer complaint rate for that product family).
+
+### Inspection Level Adjustment
+
+| Condition | Action |
+| ---------------------------------------------- | ----------------------------------------------- |
+| New supplier, first 5 lots | Tightened inspection (Level III or 100%) |
+| 10+ consecutive lots accepted at normal | Qualify for reduced or skip-lot |
+| 1 lot rejected under reduced inspection | Revert to normal immediately |
+| 2 of 5 consecutive lots rejected under normal | Switch to tightened |
+| 5 consecutive lots accepted under tightened | Revert to normal |
+| 10 consecutive lots rejected under tightened | Suspend supplier; escalate to procurement |
+| Customer complaint traced to incoming material | Revert to tightened regardless of current level |
+
+### Supplier Corrective Action Escalation
+
+| Stage | Trigger | Action | Timeline |
+| --------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| Level 1: SCAR issued | Single significant NC or 3+ minor NCs in 90 days | Formal SCAR requiring 8D response | 10 days for response, 30 for implementation |
+| Level 2: Supplier on watch | SCAR not responded to in time, or corrective action not effective | Increased inspection, supplier on probation, procurement notified | 60 days to demonstrate improvement |
+| Level 3: Controlled shipping | Continued quality failures during watch period | Supplier must submit inspection data with each shipment; or third-party sort at supplier's expense | 90 days to demonstrate sustained improvement |
+| Level 4: New source qualification | No improvement under controlled shipping | Initiate alternate supplier qualification; reduce business allocation | Qualification timeline (3-12 months depending on industry) |
+| Level 5: ASL removal | Failure to improve or unwillingness to invest | Formal removal from Approved Supplier List; transition all parts | Complete transition before final PO |
+
+## Key Edge Cases
+
+These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **Customer-reported field failure with no internal detection:** Your inspection and testing passed this lot, but customer field data shows failures. The instinct is to question the customer's data — resist it. Check whether your inspection plan covers the actual failure mode. Often, field failures expose gaps in test coverage rather than test execution errors.
+
+2. **Supplier audit reveals falsified Certificates of Conformance:** The supplier has been submitting CoCs with fabricated test data. Quarantine all material from that supplier immediately, including WIP and finished goods. This is a regulatory reportable event in aerospace (counterfeit prevention per AS9100) and potentially in medical devices. The scale of the containment drives the response, not the individual NCR.
+
+3. **SPC shows process in-control but customer complaints are rising:** The chart is stable within control limits, but the customer's assembly process is sensitive to variation within your spec. Your process is "capable" by the numbers but not capable enough. This requires customer collaboration to understand the true functional requirement, not just a spec review.
+
+4. **Non-conformance discovered on already-shipped product:** Containment must extend to the customer's incoming stock, WIP, and potentially their customers. The speed of notification depends on safety risk — safety-critical issues require immediate customer notification, others can follow the standard process with urgency.
+
+5. **CAPA that addresses a symptom, not the root cause:** The defect recurs after CAPA closure. Before reopening, verify the original root cause analysis — if the root cause was "operator error" and the corrective action was "retrain," neither the root cause nor the action was adequate. Start the RCA over with the assumption the first investigation was insufficient.
+
+6. **Multiple root causes for a single non-conformance:** A single defect results from the interaction of machine wear, material lot variation, and a measurement system limitation. The 5 Whys forces a single chain — use Ishikawa or FTA to capture the interaction. Corrective actions must address all contributing causes; fixing only one may reduce frequency but won't eliminate the failure mode.
+
+7. **Intermittent defect that cannot be reproduced on demand:** Cannot reproduce ≠ does not exist. Increase sample size and monitoring frequency. Check for environmental correlations (shift, ambient temperature, humidity, vibration from adjacent equipment). Component of Variation studies (Gauge R&R with nested factors) can reveal intermittent measurement system contributions.
+
+8. **Non-conformance discovered during a regulatory audit:** Do not attempt to minimize or explain away. Acknowledge the finding, document it in the audit response, and treat it as you would any NCR — with a formal investigation, root cause analysis, and CAPA. Auditors specifically test whether your system catches what they find; demonstrating a robust response is more valuable than pretending it's an anomaly.
+
+## Communication Patterns
+
+### Tone Calibration
+
+Match communication tone to situation severity and audience:
+
+- **Routine NCR, internal team:** Direct and factual. "NCR-2025-0412: Incoming lot 4471 of part 7832-A has OD measurements at 12.52mm against a 12.45±0.05mm specification. 18 of 50 sample pieces out of spec. Material quarantined in MRB cage, Bay 3."
+- **Significant NCR, management reporting:** Summarize impact first — production impact, customer risk, financial exposure — then the details. Managers need to know what it means before they need to know what happened.
+- **Supplier notification (SCAR):** Professional, specific, and documented. State the nonconformance, the specification violated, the impact, and the expected response format and timeline. Never accusatory; the data speaks.
+- **Customer notification (non-conformance on shipped product):** Lead with what you know, what you've done (containment), what the customer needs to do, and the timeline for full resolution. Transparency builds trust; delay destroys it.
+- **Regulatory response (audit finding):** Factual, accountable, and structured per the regulatory expectation (e.g., FDA Form 483 response format). Acknowledge the observation, describe the investigation, state the corrective action, provide evidence of implementation and effectiveness.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**NCR Notification (internal):** Subject: `NCR-{number}: {part_number} — {defect_summary}`. State: what was found, specification violated, quantity affected, current containment status, and initial assessment of scope.
+
+**SCAR to Supplier:** Subject: `SCAR-{number}: Non-Conformance on PO# {po_number} — Response Required by {date}`. Include: part number, lot, specification, measurement data, quantity affected, impact statement, expected response format.
+
+**Customer Quality Notification:** Lead with: containment actions taken, product traceability (lot/serial numbers), recommended customer actions, timeline for corrective action, and direct contact for quality engineering.
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ---------------------------------------------- | ------------------------------------------------------------- | --------------- |
+| Safety-critical non-conformance | Notify VP Quality and Regulatory immediately | Within 1 hour |
+| Field failure or customer complaint | Assign dedicated investigator, notify account team | Within 4 hours |
+| Repeat NCR (same failure mode, 3+ occurrences) | Mandatory CAPA initiation, management review | Within 24 hours |
+| Supplier falsified documentation | Quarantine all supplier material, notify regulatory and legal | Immediately |
+| Non-conformance on shipped product | Initiate customer notification protocol, containment | Within 4 hours |
+| Audit finding (external) | Management review, response plan development | Within 48 hours |
+| CAPA overdue > 30 days past target | Escalate to Quality Director for resource allocation | Within 1 week |
+| NCR backlog exceeds 50 open items | Process review, resource allocation, management briefing | Within 1 week |
+
+### Escalation Chain
+
+Level 1 (Quality Engineer) → Level 2 (Quality Supervisor, 4 hours) → Level 3 (Quality Manager, 24 hours) → Level 4 (Quality Director, 48 hours) → Level 5 (VP Quality, 72+ hours or any safety-critical event)
+
+## Performance Indicators
+
+Track these metrics weekly and trend monthly:
+
+| Metric | Target | Red Flag |
+| --------------------------------------- | ------------------ | ------------------ |
+| NCR closure time (median) | < 15 business days | > 30 business days |
+| CAPA on-time closure rate | > 90% | < 75% |
+| CAPA effectiveness rate (no recurrence) | > 85% | < 70% |
+| Supplier PPM (incoming) | < 500 PPM | > 2,000 PPM |
+| Cost of quality (% of revenue) | < 3% | > 5% |
+| Internal defect rate (in-process) | < 1,000 PPM | > 5,000 PPM |
+| Customer complaint rate (per 1M units) | < 50 | > 200 |
+| Aged NCRs (> 30 days open) | < 10% of total | > 25% |
+
+## Additional Resources
+
+- For detailed decision frameworks, MRB processes, and SPC decision logic, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **run or improve non‑conformance and CAPA processes in regulated manufacturing**:
+
+- Investigating NCRs, selecting root‑cause methods, and defining MRB dispositions and CAPA actions.
+- Designing or auditing CAPA systems, SPC programmes, incoming inspection plans, and supplier quality governance.
+- Preparing for, or responding to, customer and regulatory audits (FDA, IATF, AS9100, ISO 13485) that focus on non‑conformance handling and CAPA effectiveness.
diff --git a/web-app/public/skills/quality-nonconformance/references/communication-templates.md b/web-app/public/skills/quality-nonconformance/references/communication-templates.md
new file mode 100644
index 00000000..b733f4ab
--- /dev/null
+++ b/web-app/public/skills/quality-nonconformance/references/communication-templates.md
@@ -0,0 +1,711 @@
+# Communication Templates — Quality & Non-Conformance Management
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing quality communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and situation. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [NCR Notification (Internal)](#1-ncr-notification-internal)
+2. [MRB Disposition Record](#2-mrb-disposition-record)
+3. [Corrective Action Request (CAR) to Supplier](#3-corrective-action-request-car-to-supplier)
+4. [CAPA Initiation Record](#4-capa-initiation-record)
+5. [CAPA Effectiveness Review](#5-capa-effectiveness-review)
+6. [Audit Finding Response](#6-audit-finding-response)
+7. [Customer Quality Notification](#7-customer-quality-notification)
+8. [Supplier Audit Report Summary](#8-supplier-audit-report-summary)
+9. [Quality Alert (Internal)](#9-quality-alert-internal)
+10. [Management Review Quality Summary](#10-management-review-quality-summary)
+11. [Regulatory Agency Response (FDA Form 483)](#11-regulatory-agency-response-fda-form-483)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{ncr_number}}` | Non-conformance report number | `NCR-2025-0412` |
+| `{{capa_number}}` | CAPA record number | `CAPA-2025-0023` |
+| `{{scar_number}}` | Supplier corrective action request number | `SCAR-2025-0089` |
+| `{{part_number}}` | Part number and revision | `7832-A Rev D` |
+| `{{part_description}}` | Part description | `Shaft, Output — Titanium` |
+| `{{lot_number}}` | Lot or batch number | `LOT-2025-4471` |
+| `{{po_number}}` | Purchase order number | `PO-2025-08832` |
+| `{{wo_number}}` | Work order number | `WO-2025-1104` |
+| `{{serial_numbers}}` | Affected serial numbers (if applicable) | `SN-10042 through SN-10089` |
+| `{{supplier_name}}` | Supplier company name | `Precision Castings Corp.` |
+| `{{supplier_contact}}` | Supplier quality contact name | `Maria Gonzalez, Quality Manager` |
+| `{{customer_name}}` | Customer company name | `MedTech Instruments Inc.` |
+| `{{customer_contact}}` | Customer quality contact name | `David Chen, Supplier Quality Engineer` |
+| `{{spec_requirement}}` | Specification and requirement violated | `Drawing 7832-A Rev D, Dim A: 12.45 ±0.05mm` |
+| `{{actual_values}}` | Measured values of nonconforming product | `12.52mm, 12.54mm, 12.51mm (3 of 50 sample)` |
+| `{{quantity_affected}}` | Number of parts affected | `18 of 500 pieces inspected` |
+| `{{quantity_total}}` | Total lot quantity | `2,000 pieces` |
+| `{{defect_description}}` | Description of the non-conformance | `OD exceeds USL by 0.02-0.04mm` |
+| `{{containment_status}}` | Current containment actions | `Material quarantined in MRB cage, Bay 3` |
+| `{{our_quality_contact}}` | Internal quality contact | `Sarah Thompson, Quality Engineer` |
+| `{{our_quality_email}}` | Internal quality email | `sthompson@company.com` |
+| `{{our_quality_phone}}` | Internal quality phone | `(555) 234-5678` |
+| `{{our_company}}` | Our company name | `Advanced Manufacturing Solutions` |
+| `{{date_discovered}}` | Date non-conformance was discovered | `2025-03-15` |
+| `{{response_deadline}}` | Deadline for response | `2025-03-25 (10 business days)` |
+| `{{severity_level}}` | NCR severity classification | `Major — Dimensional non-conformance on key characteristic` |
+
+---
+
+## 1. NCR Notification (Internal)
+
+### When to Use
+- Non-conformance identified at incoming inspection, in-process, or final inspection
+- Initial notification to affected departments (manufacturing, engineering, procurement, planning)
+- Material has been quarantined; disposition pending
+
+### Tone Guidance
+Factual and direct. Internal teams need to know what happened, what the scope is, and what the immediate impact is. No blame, no speculation — data only. Include enough detail for engineering to begin their assessment and for planning to evaluate the production impact.
+
+### Template
+
+**Subject:** `{{ncr_number}}: {{part_number}} — {{defect_description}}`
+
+**To:** Manufacturing Engineering, Production Planning, Procurement (if supplier-related), Quality Manager
+**Cc:** Quality file
+
+---
+
+**Non-Conformance Report: {{ncr_number}}**
+
+**Date Discovered:** {{date_discovered}}
+**Discovered By:** {{inspector_name}}, {{inspection_stage}} (incoming / in-process / final)
+**Part Number:** {{part_number}} — {{part_description}}
+**Lot/Batch:** {{lot_number}} | Work Order: {{wo_number}} | PO: {{po_number}} (if incoming)
+
+**Non-Conformance Description:**
+{{defect_description}}
+
+**Specification Requirement:** {{spec_requirement}}
+**Actual Values:** {{actual_values}}
+**Quantity Affected:** {{quantity_affected}} of {{quantity_total}} total lot
+
+**Containment Status:**
+{{containment_status}}
+
+**Initial Scope Assessment:**
+- [ ] Other lots from same supplier/production run checked: {{scope_check_result}}
+- [ ] WIP containing this material identified: {{wip_status}}
+- [ ] Finished goods containing this material identified: {{fg_status}}
+- [ ] Downstream customer shipments containing this material: {{shipped_status}}
+
+**Production Impact:**
+{{production_impact_summary}} (e.g., "Line 3 is waiting on this material for WO-2025-1104; 2-day impact if not dispositioned by Thursday")
+
+**Requested Action:**
+Engineering review of functional impact requested by {{disposition_deadline}}.
+MRB meeting scheduled: {{mrb_date_time}}.
+
+**Quality Contact:** {{our_quality_contact}} | {{our_quality_email}} | {{our_quality_phone}}
+
+---
+
+## 2. MRB Disposition Record
+
+### When to Use
+- Documenting the Material Review Board's disposition decision
+- Required for all NCR dispositions that are not straightforward scrap
+- Audit-trail document; this is what auditors review
+
+### Tone Guidance
+Formal, precise, and complete. This is a controlled document. Every field must be populated. Engineering justification must be technically sound and specific — not "acceptable per engineering review" but a detailed rationale citing functional requirements.
+
+### Template
+
+**MRB DISPOSITION RECORD**
+
+| Field | Value |
+|---|---|
+| NCR Number | {{ncr_number}} |
+| MRB Date | {{mrb_date}} |
+| Part Number / Rev | {{part_number}} |
+| Part Description | {{part_description}} |
+| Lot/Batch | {{lot_number}} |
+| Quantity Affected | {{quantity_affected}} |
+| Nonconformance | {{defect_description}} |
+| Specification Violated | {{spec_requirement}} |
+| Actual Values | {{actual_values}} |
+
+**Disposition Decision:** ☐ Use-As-Is ☐ Rework ☐ Repair ☐ Return to Vendor ☐ Scrap
+
+**Engineering Justification (required for Use-As-Is and Repair):**
+{{engineering_justification}}
+
+Example: "The OD measurement of 12.52mm (USL 12.50mm) exceeds the drawing tolerance by 0.02mm. Per engineering analysis EA-2025-0034, this dimension interfaces with bore ID 12.60 +0.05/-0.00mm on mating part 7833-B. Minimum clearance at worst-case stack-up (shaft 12.52mm, bore 12.60mm) is 0.08mm. Assembly requirement per DWG 100-ASSY-Rev C specifies minimum 0.05mm clearance. The 0.08mm clearance meets the functional requirement. No impact to form, fit, or function."
+
+**Risk Assessment (required for safety-critical parts):**
+{{risk_assessment_reference}} (e.g., "Per ISO 14971 risk assessment RA-2025-0012, risk level is acceptable — severity [minor], probability [remote]")
+
+**Customer Approval (required for aerospace Use-As-Is/Repair):**
+☐ Not required (standard/non-regulated) ☐ Requested — Reference: {{customer_approval_ref}} ☐ Approved — Date: {{approval_date}} ☐ Denied
+
+**Cost Impact:**
+| Item | Amount |
+|---|---|
+| Scrap cost | {{scrap_cost}} |
+| Rework labor | {{rework_cost}} |
+| Re-inspection | {{reinspect_cost}} |
+| Expedite / replacement | {{expedite_cost}} |
+| **Total NCR cost** | **{{total_cost}}** |
+
+**CAPA Required:** ☐ Yes — {{capa_number}} ☐ No — Rationale: {{no_capa_rationale}}
+
+**MRB Attendees and Signatures:**
+
+| Name | Department | Signature | Date |
+|---|---|---|---|
+| {{quality_rep}} | Quality Engineering | | {{date}} |
+| {{engineering_rep}} | Design/Product Engineering | | {{date}} |
+| {{manufacturing_rep}} | Manufacturing Engineering | | {{date}} |
+| {{other_rep}} | {{other_dept}} | | {{date}} |
+
+---
+
+## 3. Corrective Action Request (CAR) to Supplier
+
+### When to Use
+- Significant non-conformance on incoming material traceable to a supplier
+- Repeated minor non-conformances from the same supplier (3+ in 90 days)
+- Supplier escalation Level 1 (SCAR issuance)
+
+### Tone Guidance
+Professional, specific, and structured. Provide all data the supplier needs to investigate. Set clear expectations for the response format and timeline. Do not be accusatory — present the facts and ask for investigation. The supplier's willingness and quality of response will tell you whether this is a fixable issue or a systemic problem.
+
+### What NOT to Say
+- Do not threaten ASL removal in a first-time CAR (save escalation language for Level 2+)
+- Do not speculate on the root cause — that's the supplier's job
+- Do not include internal financial impact numbers (the supplier doesn't need to know your downstream costs at this stage)
+
+### Template
+
+**Subject:** `SCAR-{{scar_number}}: Non-Conformance on PO# {{po_number}} — Response Required by {{response_deadline}}`
+
+**To:** {{supplier_contact}}, {{supplier_name}}
+**Cc:** {{our_quality_contact}}, Procurement buyer
+
+---
+
+**SUPPLIER CORRECTIVE ACTION REQUEST**
+
+**SCAR Number:** {{scar_number}}
+**Date Issued:** {{date_issued}}
+**Response Due:** {{response_deadline}} (initial response with containment + preliminary root cause)
+**Full Corrective Action Plan Due:** {{full_response_deadline}} (30 calendar days)
+
+**Supplier Information:**
+- Supplier: {{supplier_name}}
+- Supplier Code: {{supplier_code}}
+- Contact: {{supplier_contact}}
+
+**Non-Conformance Details:**
+- Part Number: {{part_number}} — {{part_description}}
+- PO Number: {{po_number}}
+- Lot/Batch: {{lot_number}}
+- Quantity Received: {{quantity_total}}
+- Quantity Nonconforming: {{quantity_affected}}
+- Date Received: {{date_received}}
+- Date Non-Conformance Identified: {{date_discovered}}
+
+**Specification Requirement:**
+{{spec_requirement}}
+
+**Actual Results:**
+{{actual_values}}
+
+**Supporting Documentation Attached:**
+- [ ] Inspection report with measurement data
+- [ ] Photographs of nonconforming material
+- [ ] Drawing excerpt highlighting affected dimension/requirement
+- [ ] Copy of your Certificate of Conformance for this lot
+
+**Impact to Our Operations:**
+{{impact_summary}} (e.g., "Production line held pending disposition. Estimated 3-day impact to customer delivery schedule.")
+
+**Required Response (use 8D format or equivalent):**
+1. **Containment actions** — immediate actions to protect our inventory and any other customers who may have received material from the same lot. Confirm whether other lots from the same production run may be affected.
+2. **Root cause analysis** — we require a rigorous root cause investigation, not a surface-level explanation. "Operator error" or "inspection escape" are not acceptable root causes. Identify the systemic process or system failure that allowed this non-conformance.
+3. **Corrective actions** — specific, measurable actions addressing the verified root cause. Include implementation dates and responsible personnel.
+4. **Effectiveness verification plan** — how and when will you verify that the corrective actions are effective?
+
+**Disposition of Nonconforming Material:**
+☐ Return to Vendor — please issue RMA# and shipping instructions
+☐ Sort at our facility — credit memo for sort labor will follow
+☐ Scrap at our facility — credit memo for material value will follow
+
+**Contact for Questions:**
+{{our_quality_contact}} | {{our_quality_email}} | {{our_quality_phone}}
+
+---
+
+## 4. CAPA Initiation Record
+
+### When to Use
+- Formal CAPA initiation based on established trigger criteria
+- Documents the triggering event, scope, team assignment, and initial timeline
+
+### Tone Guidance
+Structured and factual. The initiation record sets the scope and expectations for the entire CAPA. Ambiguity here leads to scope creep or incomplete investigations later. Be specific about what triggered the CAPA and what the expected outcome is.
+
+### Template
+
+**CORRECTIVE AND PREVENTIVE ACTION RECORD**
+
+| Field | Value |
+|---|---|
+| CAPA Number | {{capa_number}} |
+| Date Initiated | {{date_initiated}} |
+| Type | ☐ Corrective ☐ Preventive |
+| Source | ☐ NCR ☐ Customer Complaint ☐ Audit Finding ☐ Trend Analysis ☐ Field Failure ☐ Other: {{other_source}} |
+| Source Reference(s) | {{source_references}} (e.g., NCR-2025-0412, NCR-2025-0398, NCR-2025-0456) |
+| Priority | ☐ Critical (safety/regulatory) ☐ High (customer impact) ☐ Medium (internal) ☐ Low (improvement) |
+
+**Problem Statement:**
+{{problem_statement}}
+
+Example: "Recurring dimensional non-conformance on Part 7832-A Rev D — bore diameter out of tolerance (>USL of 12.50mm). Three NCRs in the last 60 days (NCR-2025-0398, -0412, -0456) affecting lots from three different production runs. Total scrap cost to date: $14,200. No customer impact confirmed, but risk of escape exists based on inspection sampling rates."
+
+**Scope:**
+- Product(s) affected: {{products_affected}}
+- Process(es) affected: {{processes_affected}}
+- Location(s): {{locations_affected}}
+- Period: {{time_period}}
+
+**Team Assignment:**
+
+| Role | Name | Department |
+|---|---|---|
+| CAPA Owner | {{capa_owner}} | {{owner_dept}} |
+| Lead Investigator | {{investigator}} | {{investigator_dept}} |
+| Team Members | {{team_members}} | {{team_depts}} |
+| Management Sponsor | {{sponsor}} | {{sponsor_dept}} |
+
+**Timeline:**
+
+| Phase | Target Date |
+|---|---|
+| Root Cause Investigation Complete | {{rca_target}} |
+| Corrective Action Plan Approved | {{plan_target}} |
+| Implementation Complete | {{implementation_target}} |
+| Effectiveness Verification Start | {{verification_start}} |
+| Effectiveness Verification Complete | {{verification_end}} |
+| CAPA Closure Target | {{closure_target}} |
+
+**Initial Containment Actions (if applicable):**
+{{containment_actions}}
+
+---
+
+## 5. CAPA Effectiveness Review
+
+### When to Use
+- At the end of the effectiveness monitoring period (typically 90 days after implementation)
+- Documents the evidence of effectiveness and the closure/extension decision
+
+### Tone Guidance
+Data-driven and conclusive. The effectiveness review is where the CAPA either closes with evidence of success or reopens with evidence of failure. Auditors specifically review effectiveness evidence — it must be quantitative and linked to the original problem statement.
+
+### Template
+
+**CAPA EFFECTIVENESS REVIEW**
+
+| Field | Value |
+|---|---|
+| CAPA Number | {{capa_number}} |
+| Original Problem | {{problem_statement}} |
+| Root Cause | {{verified_root_cause}} |
+| Corrective Action(s) Implemented | {{corrective_actions}} |
+| Implementation Date | {{implementation_date}} |
+| Monitoring Period | {{monitoring_start}} to {{monitoring_end}} |
+
+**Implementation Verification:**
+- [ ] Work instruction / procedure updated: Rev {{rev}} effective {{date}}
+- [ ] Personnel trained: {{training_records_ref}}
+- [ ] Equipment/fixture installed and validated: {{validation_ref}}
+- [ ] FMEA / Control Plan updated: {{fmea_ref}}
+- [ ] Supplier corrective action verified: {{scar_ref}}
+
+**Effectiveness Data:**
+
+| Metric | Baseline (Pre-CAPA) | Target | Actual (Monitoring Period) | Result |
+|---|---|---|---|---|
+| {{metric_1}} | {{baseline_1}} | {{target_1}} | {{actual_1}} | ☐ Pass ☐ Fail |
+| {{metric_2}} | {{baseline_2}} | {{target_2}} | {{actual_2}} | ☐ Pass ☐ Fail |
+| Recurrence count | {{baseline_recurrence}} | Zero | {{actual_recurrence}} | ☐ Pass ☐ Fail |
+
+**Conclusion:**
+☐ **CAPA Effective — Close.** All effectiveness criteria met. Zero recurrences during monitoring period. Process capability meets target.
+☐ **CAPA Partially Effective — Extend monitoring.** Improvement demonstrated but monitoring period insufficient for definitive conclusion. Extend by {{extension_days}} days.
+☐ **CAPA Not Effective — Reopen.** Recurrence observed during monitoring period. Root cause re-investigation required. See {{reopened_investigation_ref}}.
+
+**Reviewed By:**
+
+| Name | Role | Signature | Date |
+|---|---|---|---|
+| {{reviewer_1}} | CAPA Owner | | |
+| {{reviewer_2}} | Quality Manager | | |
+
+---
+
+## 6. Audit Finding Response
+
+### When to Use
+- Responding to external audit findings (registrar, customer, regulatory)
+- Structure applies to ISO audit NCRs, customer audit CARs, and FDA 483 responses (with modifications per template 11)
+
+### Tone Guidance
+Factual, accountable, and solution-oriented. Accept the finding (even if you disagree with the interpretation — debate the interpretation separately, not in the corrective action response). Demonstrate that you understand the intent of the requirement, not just the words. Auditors value self-awareness and systemic thinking.
+
+### Template
+
+**AUDIT FINDING CORRECTIVE ACTION RESPONSE**
+
+**Audit:** {{audit_type}} (e.g., ISO 9001 Surveillance, Customer Audit, IATF 16949 Recertification)
+**Auditor / Organization:** {{auditor_name}}, {{audit_organization}}
+**Audit Date(s):** {{audit_dates}}
+**Finding Number:** {{finding_number}}
+**Finding Classification:** ☐ Major Non-Conformity ☐ Minor Non-Conformity ☐ Observation / OFI
+
+**Finding Statement:**
+{{finding_statement}}
+
+**Standard Clause Referenced:** {{standard_clause}} (e.g., ISO 9001:2015 §8.5.2, IATF 16949 §10.2.3)
+
+**Our Response:**
+
+**1. Acknowledgment:**
+We acknowledge the finding. {{brief_acknowledgment}}
+
+**2. Root Cause Analysis:**
+{{root_cause_analysis}}
+
+**3. Containment (immediate action taken):**
+{{containment_actions}}
+
+**4. Corrective Action:**
+| Action | Responsible | Target Date | Evidence of Completion |
+|---|---|---|---|
+| {{action_1}} | {{responsible_1}} | {{date_1}} | {{evidence_1}} |
+| {{action_2}} | {{responsible_2}} | {{date_2}} | {{evidence_2}} |
+
+**5. Scope Extension (did we check for similar gaps elsewhere?):**
+{{scope_extension}}
+
+**6. Effectiveness Verification Plan:**
+{{effectiveness_plan}}
+
+**Submitted By:** {{responder_name}}, {{responder_title}}
+**Date:** {{submission_date}}
+
+---
+
+## 7. Customer Quality Notification
+
+### When to Use
+- Non-conformance discovered on product already shipped to the customer
+- Proactive notification — the customer should hear about it from you before they discover it themselves
+
+### Tone Guidance
+Transparent, action-oriented, and structured. Lead with what you know and what you've done (containment), not with excuses. Provide the specific traceability data the customer needs to identify and segregate affected product in their inventory. The customer will judge your quality system based on how you handle this notification — transparency and speed build trust; delay and vagueness destroy it.
+
+### What NOT to Say
+- Do not minimize: "A minor issue was detected" when you don't yet know the scope
+- Do not speculate on root cause: "We believe this was caused by..." without verified data
+- Do not over-promise on timeline: "This will be resolved by Friday" unless you're certain
+
+### Template
+
+**Subject:** `Quality Notification: {{part_number}} — {{defect_description}} — Action Required`
+
+**To:** {{customer_contact}}, {{customer_name}}
+**Cc:** {{our_quality_contact}}, Account Manager
+
+---
+
+**CUSTOMER QUALITY NOTIFICATION**
+
+**Date:** {{date}}
+**Our Reference:** {{ncr_number}}
+**Priority:** {{priority_level}} (Critical / High / Standard)
+
+Dear {{customer_contact}},
+
+We are contacting you to notify you of a quality concern with material we have supplied.
+
+**Affected Product:**
+- Part Number: {{part_number}} — {{part_description}}
+- Lot Number(s): {{lot_numbers}}
+- Serial Number(s): {{serial_numbers}} (if applicable)
+- Ship Date(s): {{ship_dates}}
+- PO/Order Reference(s): {{po_numbers}}
+- Quantity Shipped: {{quantity_shipped}}
+
+**Nature of Non-Conformance:**
+{{defect_description_for_customer}}
+
+**Containment Actions Taken:**
+1. All inventory at our facility has been quarantined and placed on hold
+2. Shipments in transit have been intercepted where possible: {{transit_status}}
+3. We request that you quarantine the following lot(s) in your inventory: {{lots_to_quarantine}}
+
+**Recommended Customer Action:**
+{{recommended_customer_action}} (e.g., "Please segregate and hold the affected lot numbers listed above. Do not use this material until we provide disposition guidance.")
+
+**Investigation Status:**
+We have initiated an investigation ({{ncr_number}}) and are conducting [root cause analysis / containment sort / material verification]. We will provide an updated status by {{next_update_date}}.
+
+**Your Direct Contact:**
+{{our_quality_contact}}
+{{our_quality_email}}
+{{our_quality_phone}}
+
+We take this matter seriously and are committed to full transparency as our investigation progresses. We will provide updates at minimum every {{update_frequency}} until this is resolved.
+
+Sincerely,
+{{our_quality_contact}}, {{our_quality_title}}
+{{our_company}}
+
+---
+
+## 8. Supplier Audit Report Summary
+
+### When to Use
+- Summary of a supplier quality audit (process, system, or product audit)
+- Distributed to procurement, engineering, and supplier quality management
+- Basis for audit follow-up actions
+
+### Tone Guidance
+Objective and balanced. Report what was observed, both strengths and deficiencies. An audit report that is exclusively negative suggests the auditor was looking for problems rather than assessing capability. An audit report that is exclusively positive suggests the auditor wasn't thorough. The summary should give management a clear picture of the supplier's quality maturity.
+
+### Template
+
+**SUPPLIER AUDIT REPORT SUMMARY**
+
+| Field | Value |
+|---|---|
+| Supplier | {{supplier_name}} |
+| Supplier Code | {{supplier_code}} |
+| Audit Type | ☐ System ☐ Process ☐ Product ☐ Combined |
+| Audit Date(s) | {{audit_dates}} |
+| Auditor(s) | {{auditor_names}} |
+| Standard(s) Audited Against | {{standards}} (e.g., ISO 9001:2015, IATF 16949, AS9100D) |
+| Scope | {{audit_scope}} |
+
+**Overall Assessment:** ☐ Approved ☐ Approved with Conditions ☐ Not Approved
+
+**Strengths Observed:**
+1. {{strength_1}}
+2. {{strength_2}}
+3. {{strength_3}}
+
+**Findings:**
+
+| # | Clause | Finding | Classification |
+|---|---|---|---|
+| 1 | {{clause_1}} | {{finding_1}} | Major / Minor / OFI |
+| 2 | {{clause_2}} | {{finding_2}} | Major / Minor / OFI |
+
+**Corrective Action Requirements:**
+- Response due: {{car_deadline}}
+- Format: 8D or equivalent with root cause analysis and implementation plan
+- Submit to: {{submit_to}}
+
+**Recommendations:**
+{{recommendations}} (e.g., "Approve for production with mandatory follow-up audit in 6 months to verify corrective actions. Increase incoming inspection level to tightened until corrective actions verified.")
+
+---
+
+## 9. Quality Alert (Internal)
+
+### When to Use
+- Urgent notification to production floor, inspection, and shipping about a quality issue requiring immediate action
+- Non-conformance that could affect product currently in production or awaiting shipment
+- Temporary enhanced inspection or containment measure
+
+### Tone Guidance
+Urgent, clear, and actionable. This goes to the production floor — operators, supervisors, inspectors. Use plain language. Include photographs if possible. Specify exactly what to do and what to look for. This is not a request for analysis; it's an instruction for immediate action.
+
+### Template
+
+**⚠ QUALITY ALERT ⚠**
+
+**Alert Number:** QA-{{alert_number}}
+**Date Issued:** {{date_issued}}
+**Effective Immediately — Until Rescinded**
+
+**Affected Part(s):** {{part_number}} — {{part_description}}
+**Affected Area(s):** {{production_areas}} (e.g., "Line 3 — CNC Turning, Incoming Inspection, Final Inspection, Shipping")
+
+**Issue:**
+{{issue_description_plain_language}}
+
+**What to Look For:**
+{{what_to_look_for}} (specific, measurable criteria with photographs if available)
+
+**Required Action:**
+1. {{action_1}} (e.g., "100% inspect all WIP on this part number for the affected dimension before releasing to the next operation")
+2. {{action_2}} (e.g., "Segregate and tag any nonconforming parts found — do NOT scrap without Quality Engineering authorization")
+3. {{action_3}} (e.g., "Notify Quality Engineering immediately if any additional nonconforming parts are found: {{contact_info}}")
+
+**This alert remains in effect until:** {{rescind_condition}} (e.g., "written notification from Quality Engineering that the root cause has been addressed and verified")
+
+**Issued By:** {{issuer_name}}, {{issuer_title}}
+
+---
+
+## 10. Management Review Quality Summary
+
+### When to Use
+- Monthly or quarterly management review input on quality performance
+- Summarizes key metrics, significant quality events, CAPA status, and cost of quality
+
+### Tone Guidance
+Executive-level. Lead with the headline — is quality performance improving, stable, or deteriorating? Then provide the supporting data. Managers need to understand trend direction and business impact, not individual NCR details. Use charts and tables; minimize narrative.
+
+### Template
+
+**QUALITY MANAGEMENT REVIEW — {{review_period}}**
+
+**Prepared By:** {{quality_manager}}
+**Date:** {{date}}
+
+**Executive Summary:**
+{{executive_summary}} (2-3 sentences: overall quality trend, most significant event, key action needed)
+
+**Key Performance Indicators:**
+
+| Metric | Target | Prior Period | Current Period | Trend |
+|---|---|---|---|---|
+| Internal defect rate (PPM) | < 1,000 | {{prior_ppm}} | {{current_ppm}} | ↑ ↓ → |
+| Customer complaint rate | < 50/1M units | {{prior_complaints}} | {{current_complaints}} | ↑ ↓ → |
+| Supplier PPM (incoming) | < 500 | {{prior_supplier_ppm}} | {{current_supplier_ppm}} | ↑ ↓ → |
+| NCR closure time (median days) | < 15 | {{prior_ncr_cycle}} | {{current_ncr_cycle}} | ↑ ↓ → |
+| CAPA on-time closure rate | > 90% | {{prior_capa_otc}} | {{current_capa_otc}} | ↑ ↓ → |
+| Cost of quality (% revenue) | < 3% | {{prior_coq}} | {{current_coq}} | ↑ ↓ → |
+
+**Significant Quality Events:**
+1. {{event_1}}
+2. {{event_2}}
+
+**CAPA Status:**
+
+| Status | Count |
+|---|---|
+| Open — On Track | {{on_track}} |
+| Open — Overdue | {{overdue}} |
+| Closed This Period | {{closed}} |
+| Effectiveness Verified | {{verified}} |
+
+**Top Suppliers by PPM (worst 5):**
+
+| Supplier | PPM | Trend | Current Escalation Level |
+|---|---|---|---|
+| {{supplier_1}} | {{ppm_1}} | ↑ ↓ → | {{level_1}} |
+| {{supplier_2}} | {{ppm_2}} | ↑ ↓ → | {{level_2}} |
+
+**Cost of Quality Breakdown:**
+
+| Category | Amount | % of Revenue |
+|---|---|---|
+| Prevention | {{prevention_cost}} | {{prevention_pct}} |
+| Appraisal | {{appraisal_cost}} | {{appraisal_pct}} |
+| Internal Failure | {{internal_failure_cost}} | {{internal_pct}} |
+| External Failure | {{external_failure_cost}} | {{external_pct}} |
+| **Total COQ** | **{{total_coq}}** | **{{total_coq_pct}}** |
+
+**Actions Required from Management:**
+1. {{action_request_1}} (e.g., "Approve capital expenditure for automated inspection system — ROI analysis attached")
+2. {{action_request_2}} (e.g., "Decision needed on Supplier X escalation to Level 3 / alternate source qualification")
+
+---
+
+## 11. Regulatory Agency Response (FDA Form 483)
+
+### When to Use
+- Formal response to FDA Form 483 observations
+- Due within 15 business days of receiving the 483
+- This is a critical document — it becomes part of the public FDA inspection record
+
+### Tone Guidance
+Respectful, thorough, and accountable. Acknowledge each observation. Do not argue, minimize, or blame individuals. Demonstrate that you understand the intent of the regulations, not just the words. FDA reviewers specifically evaluate whether your response addresses the systemic issue, not just the specific observation.
+
+### What NOT to Say
+- "We disagree with this observation" — address it even if you disagree
+- "This was an isolated incident" — FDA explicitly looks for systemic issues
+- "Employee has been terminated" — this is punitive, not corrective; FDA wants system fixes
+- "We will address this" without specific actions, dates, and responsible parties
+
+### Template
+
+**[Company Letterhead]**
+
+{{date}}
+
+{{fda_district_director_name}}
+Director, {{fda_district_office}}
+Food and Drug Administration
+{{fda_address}}
+
+**Re: Response to FDA Form 483 Inspectional Observations**
+**Establishment:** {{facility_name_address}}
+**FEI Number:** {{fei_number}}
+**Inspection Dates:** {{inspection_dates}}
+**Investigator:** {{investigator_name}}
+
+Dear {{fda_district_director_name}},
+
+{{our_company}} appreciates the opportunity to respond to the observations identified during the FDA inspection of our {{facility_name}} facility conducted {{inspection_dates}}. We take these observations seriously and have initiated corrective actions as described below.
+
+---
+
+**Observation {{obs_number}}:**
+"{{verbatim_483_observation}}"
+
+**Response:**
+
+**Acknowledgment:**
+{{acknowledgment}} (e.g., "We acknowledge that our procedure QP-4401 did not adequately address...")
+
+**Investigation:**
+{{investigation_summary}} (What we investigated, what we found, root cause)
+
+**Corrective Action:**
+
+| Action | Description | Responsible | Target Date | Status |
+|---|---|---|---|---|
+| 1 | {{action_1_description}} | {{responsible_1}} | {{date_1}} | {{status_1}} |
+| 2 | {{action_2_description}} | {{responsible_2}} | {{date_2}} | {{status_2}} |
+
+**Scope Extension:**
+{{scope_extension}} (e.g., "We reviewed all similar procedures across our facility and identified two additional areas where the same gap existed. These have been corrected as part of actions 3 and 4 above.")
+
+**Effectiveness Verification:**
+{{effectiveness_plan}} (e.g., "We will monitor the effectiveness of these corrective actions over a 90-day period by tracking [specific metric]. Evidence of effectiveness will be available for review upon request.")
+
+**Evidence Attached:** {{list_of_evidence}}
+
+---
+
+[Repeat for each observation]
+
+---
+
+We are committed to maintaining full compliance with 21 CFR Part 820 and to the continuous improvement of our quality management system. We welcome the opportunity to discuss these responses or to provide additional information.
+
+Sincerely,
+
+{{signatory_name}}
+{{signatory_title}}
+{{our_company}}
+{{contact_information}}
+
+Enclosures: {{list_of_enclosures}}
diff --git a/web-app/public/skills/quality-nonconformance/references/decision-frameworks.md b/web-app/public/skills/quality-nonconformance/references/decision-frameworks.md
new file mode 100644
index 00000000..a2185ef8
--- /dev/null
+++ b/web-app/public/skills/quality-nonconformance/references/decision-frameworks.md
@@ -0,0 +1,769 @@
+# Decision Frameworks — Quality & Non-Conformance Management
+
+This reference provides the detailed decision logic, MRB processes, RCA methodology selection,
+CAPA lifecycle management, SPC interpretation workflows, inspection level determination,
+supplier quality escalation, and cost of quality calculation models for regulated manufacturing
+quality engineering.
+
+All thresholds, regulatory references, and process expectations reflect quality engineering
+practice across FDA 21 CFR 820, IATF 16949, AS9100, and ISO 13485 environments.
+
+---
+
+## 1. NCR Disposition Decision Trees
+
+### 1.1 Universal Disposition Flow
+
+Every non-conformance, regardless of regulatory environment, begins with this decision sequence.
+The flow terminates at the first applicable disposition; do not skip levels.
+
+```
+START: Non-conformance identified and documented
+ │
+ ├─ Is the part safety-critical or regulatory-controlled?
+ │ ├─ YES → Can it be reworked to FULL conformance?
+ │ │ ├─ YES → REWORK with approved procedure + 100% re-inspection
+ │ │ └─ NO → SCRAP (no use-as-is permitted without formal risk assessment
+ │ │ AND regulatory/customer approval)
+ │ └─ NO → Continue
+ │
+ ├─ Does the non-conformance affect form, fit, or function?
+ │ ├─ YES → Can it be reworked to full conformance?
+ │ │ ├─ YES → Is rework cost < 60% of replacement cost?
+ │ │ │ ├─ YES → REWORK
+ │ │ │ └─ NO → SCRAP (rework is not economical)
+ │ │ └─ NO → Can it be repaired to acceptable function?
+ │ │ ├─ YES → REPAIR with engineering concession + customer
+ │ │ │ approval (if required by contract/standard)
+ │ │ └─ NO → SCRAP
+ │ └─ NO → Continue
+ │
+ ├─ Is the non-conformance cosmetic only?
+ │ ├─ YES → Does customer spec address cosmetic requirements?
+ │ │ ├─ YES → Does the part meet customer cosmetic spec?
+ │ │ │ ├─ YES → USE-AS-IS with documentation
+ │ │ │ └─ NO → Customer concession required → If granted: USE-AS-IS
+ │ │ │ → If denied: REWORK or SCRAP
+ │ │ └─ NO → USE-AS-IS with engineering sign-off
+ │ └─ NO → Continue
+ │
+ ├─ Is this a dimensional non-conformance within material review authority?
+ │ ├─ YES → Engineering analysis: does the dimension affect assembly or performance?
+ │ │ ├─ YES → REWORK or SCRAP (depending on feasibility)
+ │ │ └─ NO → USE-AS-IS with documented engineering justification
+ │ └─ NO → Continue
+ │
+ └─ Is this a supplier-caused non-conformance?
+ ├─ YES → Is the material needed immediately for production?
+ │ ├─ YES → Sort/rework at supplier's cost + USE acceptable units
+ │ │ + SCAR to supplier + debit memo for sort/rework cost
+ │ └─ NO → RETURN TO VENDOR with SCAR + debit memo or replacement PO
+ └─ NO → Evaluate per the functional impact path above
+```
+
+### 1.2 FDA-Regulated Environment (21 CFR 820 / ISO 13485) Specific Logic
+
+Medical device non-conformances carry additional requirements:
+
+**Pre-Market (Design/Development):**
+- Non-conformances during design verification/validation must be documented in the Design History File (DHF)
+- Disposition must consider risk per ISO 14971 — severity and probability of harm to the patient
+- Use-as-is is rarely acceptable for a design non-conformance; it implies the design intent is wrong
+- CAPA is almost always required to prevent recurrence in production
+
+**Post-Market (Production/Field):**
+- Non-conformances that could affect device safety or performance require evaluation for field action (recall, correction, removal) per 21 CFR 806
+- The threshold is low: if there is any reasonable possibility of harm, evaluate formally
+- Document the decision NOT to file a field action as rigorously as the decision to file one
+- Complaint-related non-conformances must be linked to complaint records per 820.198
+- MDR (Medical Device Report) obligations: death or serious injury must be reported to FDA within 30 calendar days (5 days for events requiring remedial action)
+
+**Disposition Authority Matrix:**
+
+| Disposition | Who Can Authorize | Additional Requirements |
+|---|---|---|
+| Scrap | Quality Engineer or above | Documented with lot traceability |
+| Rework | Quality Engineer + Manufacturing Engineering | Approved rework procedure; re-inspect to original spec |
+| Repair | MRB (Quality + Engineering + Manufacturing) | Risk assessment per ISO 14971; update DHF if design-related |
+| Use-As-Is | MRB + Design Authority | Risk assessment; documented justification; regulatory impact evaluation |
+| RTV | Quality Engineer + Procurement | SCAR required; supplier re-qualification if repeated |
+
+### 1.3 Automotive Environment (IATF 16949) Specific Logic
+
+**Customer Notification Requirements:**
+- Any non-conformance on product shipped to the customer: notification within 24 hours of discovery
+- Any process change affecting fit, form, function, or performance: PPAP resubmission required
+- Use-as-is disposition: typically requires a formal deviation request to the customer through their supplier portal (e.g., GM's GQTS, Ford's MQAS, Stellantis' SQP)
+- Customer may accept, reject, or accept with conditions (reduced quantity, time-limited deviation)
+
+**Control Plan Integration:**
+- When a non-conformance reveals a gap in the control plan, the control plan must be updated as part of the corrective action
+- Special characteristics (safety/significant characteristics identified with shield or diamond symbols) have zero tolerance for non-conformance: 100% containment and immediate CAPA
+- The reaction plan column of the control plan specifies the predetermined response — follow it first, then investigate
+
+**Controlled Shipping Levels:**
+- **CS-1 (Internal Controlled Shipping):** Supplier adds an additional inspection/sort step beyond normal controls and submits inspection data with each shipment
+- **CS-2 (External Controlled Shipping):** Third-party inspection at supplier's facility, at supplier's cost, with direct reporting to customer quality
+- CS-1 and CS-2 are distinct from the general supplier escalation ladder — they are customer-mandated containment measures, not supplier-initiated improvements
+
+### 1.4 Aerospace Environment (AS9100) Specific Logic
+
+**Customer/Authority Approval:**
+- Use-as-is and repair dispositions ALWAYS require customer approval per AS9100 §8.7.1
+- If the customer is a prime contractor working under a government contract, the government quality representative (DCMA or equivalent) may also need to approve
+- Non-conformances on parts with key characteristics require notification to the design authority
+- First Article Inspection (FAI) per AS9102 becomes invalid if a non-conformance indicates the process has changed from the qualified state — partial or full FAI resubmission may be required
+
+**Counterfeit Part Prevention:**
+- If a non-conformance raises suspicion of counterfeit material (unexpected material composition, incorrect markings, suspect documentation), invoke the counterfeit prevention procedure per AS9100 §8.1.4
+- Quarantine the suspect material in a separate area from other MRB material
+- Report to GIDEP (Government-Industry Data Exchange Program) if counterfeit is confirmed
+- Do not return suspect counterfeit material to the supplier — it must be quarantined and may need to be retained as evidence
+
+**Traceability Requirements:**
+- Aerospace non-conformances must maintain lot, batch, heat, and serial number traceability throughout the disposition process
+- Scrap disposition must include documented destruction of serialized parts to prevent re-entry into the supply chain
+- OASIS database updates may be required for supplier quality events
+
+---
+
+## 2. Root Cause Analysis Methodology Selection Guide
+
+### 2.1 Selection Decision Matrix
+
+| Factor | 5 Whys | Ishikawa + 5 Whys | 8D | Fault Tree Analysis |
+|---|---|---|---|---|
+| **Best for** | Single-event, linear cause chain | Multi-factor, need to explore categories | Recurring issue, team-based resolution | Safety-critical, quantitative risk needed |
+| **Effort (hours)** | 1–2 | 4–8 | 20–40 (across all D-steps) | 40–80 |
+| **Team size** | 1–2 people | 2–4 people | 5–8 cross-functional | 3–6 subject matter experts |
+| **When required** | Internal process investigations | Complex non-conformances | Customer mandate (automotive OEMs) | Aerospace product safety; medical device risk analysis |
+| **Limitation** | Assumes single linear chain | Still qualitative; hypothesis-driven | Heavyweight for simple issues | Resource-intensive; requires failure rate data for quantitative mode |
+| **Output** | Root cause statement | Categorized cause hypotheses with verified root cause | Full 8D report (D0-D8) | Fault tree diagram with probability assignments |
+
+### 2.2 The 5 Whys: When It Works and When It Doesn't
+
+**5 Whys works well when:**
+- The failure is a single event with a clear before/after state change
+- Each "why" can be verified with data (measurement, observation, record review)
+- The causal chain does not branch — there is a single dominant cause
+- The investigation can reach a systemic cause (process, system, or design issue) within 5 iterations
+
+**5 Whys fails when:**
+- Multiple independent causes interact to produce the failure (combinatorial causes)
+- The analyst stops at "human error" or "operator mistake" — this is never a root cause
+- Each "why" is answered with opinion rather than verified data
+- The analysis becomes circular (Why A? Because B. Why B? Because A.)
+- Organizational pressure drives toward a "convenient" root cause that avoids systemic change
+
+**Verification protocol for each "why" level:**
+
+| Why Level | Question | Acceptable Evidence | Unacceptable Evidence |
+|---|---|---|---|
+| Why 1 (Event) | What physically happened? | Measurement data, photographs, inspection records | "The part was bad" |
+| Why 2 (Condition) | What condition allowed it? | Process parameter logs, tool condition records | "The operator didn't check" |
+| Why 3 (Process) | Why did the process permit this condition? | Work instruction review, process FMEA gap | "It's always been done this way" |
+| Why 4 (System) | Why didn't the system prevent the process gap? | System audit evidence, training records, control plan review | "We need better training" |
+| Why 5 (Management) | Why was the system gap undetected? | Management review records, resource allocation evidence, risk assessment gaps | "Management doesn't care about quality" |
+
+### 2.3 Ishikawa Diagram: 6M Framework Deep Dive
+
+For each M category, specific investigation questions that separate thorough analysis from checkbox exercises:
+
+**Man (Personnel):**
+- Was the operator trained AND certified on this specific operation?
+- When was the most recent certification renewal?
+- Was this the operator's normal workstation or were they cross-trained/temporary?
+- Was the shift staffing at normal levels or was this during overtime/short-staffing?
+- Check operator error rate data — is this an isolated event or a pattern for this individual?
+
+**Machine (Equipment):**
+- When was the last preventive maintenance performed (date AND what was done)?
+- Is the machine within its calibration cycle for all measuring functions?
+- Were any alarms, warnings, or parameter drifts logged before the event?
+- Has the machine been modified, repaired, or had a tooling change recently?
+- Check the machine's historical Cpk trend — has capability been declining?
+
+**Material:**
+- Is this a new lot of raw material? When did the lot change?
+- Were incoming inspection results within normal range, or marginal-pass?
+- Does the material certificate match what was physically received (heat number, mill, composition)?
+- Has the material been stored correctly (temperature, humidity, shelf life, FIFO rotation)?
+- Were any material substitutions or equivalents authorized?
+
+**Method (Process):**
+- Is the work instruction current revision? When was it last revised?
+- Does the operator actually follow the work instruction as written (observation, not assumption)?
+- Were any process parameters changed recently (speeds, feeds, temperatures, pressures, cure times)?
+- Was an engineering change order (ECO) recently implemented on this part or process?
+- Is there a gap between the documented method and the actual method (tribal knowledge)?
+
+**Measurement:**
+- Was the measurement system used for this inspection validated (Gauge R&R)?
+- Is the gauge within calibration? Check both certificate and physical condition.
+- Was the correct measurement method used (per the control plan or inspection instruction)?
+- Did the measurement environment (temperature, vibration, lighting) affect the result?
+- For attribute inspections (go/no-go, visual): what is the inspection effectiveness rate?
+
+**Mother Nature (Environment):**
+- Were ambient conditions (temperature, humidity) within process specification?
+- Were there any environmental events (power fluctuation, compressed air pressure drop, vibration from construction)?
+- Is there a shift-to-shift or day-to-day correlation in the data (temperature cycling, humidity changes)?
+- Was the factory HVAC system operating normally?
+- For cleanroom or controlled environment processes: were environmental monitoring logs within specification?
+
+### 2.4 8D Methodology: Detailed Gate Requirements
+
+Each D-step has specific outputs required before advancing. Skipping gates creates 8Ds that look complete but don't actually solve the problem.
+
+| D-Step | Name | Required Output | Common Failure Mode |
+|---|---|---|---|
+| D0 | Symptom & Emergency Response | Emergency response actions taken; containment effectiveness confirmed | Confusing containment with corrective action |
+| D1 | Team Formation | Cross-functional team with defined roles; includes process owner and subject matter expert | Team is all quality, no manufacturing or engineering |
+| D2 | Problem Definition | IS/IS NOT analysis completed; problem quantified with data (defect rate, PPM, Cpk shift, complaint count) | Problem statement is too broad ("quality issues") or just restates the symptom |
+| D3 | Interim Containment | Actions to protect customer while investigation proceeds; effectiveness verified (inspection data post-containment) | Containment is "100% inspection" without verifying inspection effectiveness through known-defective challenge |
+| D4 | Root Cause | Root cause(s) verified through data analysis or designed experiment; escapes the "human error" trap | Root cause = restatement of problem; no verification data; stops at symptoms |
+| D5 | Corrective Action Selection | Actions address verified root cause; mistake-proofing (poka-yoke) preferred over procedural controls | Corrective action = "retrain operators" or "add inspection step" (both are weak) |
+| D6 | Implementation | Actions implemented with documented evidence (updated WI, installed fixture, modified process); baseline performance established | Implementation date = planned date, not actual; no evidence of implementation |
+| D7 | Prevention | Systemic actions to prevent recurrence across similar processes/products; lessons learned documented; FMEA updated | D7 is copy-paste of D5; no horizontal deployment; FMEA not updated |
+| D8 | Recognition | Team acknowledged; 8D closed with effectiveness data | Closed without effectiveness data; team not recognized |
+
+### 2.5 Fault Tree Analysis: Construction Methodology
+
+**Step 1: Define the Top Event**
+- State the undesired event in specific, measurable terms
+- Example: "Shaft diameter exceeds USL of 25.05mm on finished machined part"
+- Not: "Bad parts" or "Quality problem"
+
+**Step 2: Identify Immediate Causes (Level 1)**
+- What must be true for the top event to occur?
+- Use AND gates (all causes must be present) and OR gates (any single cause is sufficient)
+- Example: "Shaft OD too large" can be caused by (OR gate): tool wear, incorrect tool offset, material oversize, thermal expansion, fixture misalignment
+
+**Step 3: Decompose Each Cause (Levels 2–N)**
+- For each Level 1 cause, ask: what causes this?
+- Continue decomposing until you reach basic events (events with known failure rates or that cannot be further decomposed)
+- Example: "Tool wear" caused by (AND gate): extended run time + inadequate tool change interval + no in-process SPC alert
+
+**Step 4: Quantify (when data is available)**
+- Assign probability values to basic events using historical data, MTBF data, or engineering estimates
+- Calculate top event probability through the gate logic
+- Identify the minimal cut sets (smallest combinations of basic events that cause the top event)
+- Focus corrective actions on the highest-probability cut sets
+
+---
+
+## 3. CAPA Writing and Verification Framework
+
+### 3.1 CAPA Initiation Criteria
+
+**Always initiate CAPA for:**
+- Repeat non-conformance: same failure mode occurring 3+ times in 12 months
+- Customer complaint involving product performance, safety, or regulatory compliance
+- External audit finding (FDA, notified body, customer, registrar)
+- Field failure or product return
+- Trend signal: SPC control chart out-of-control pattern (not isolated point)
+- Regulatory requirement change affecting existing products/processes
+- Post-market surveillance data indicating potential safety concern
+
+**Consider CAPA (judgment call) for:**
+- Repeat non-conformance: same failure mode 2 times in 12 months
+- Internal audit finding of moderate significance
+- Supplier non-conformance with systemic indicators
+- Near-miss event (non-conformance caught before reaching customer)
+- Process deviation from validated parameters without product impact
+
+**Do NOT initiate CAPA for:**
+- Isolated non-conformance with clear, non-recurring cause (one-off tool breakage, power outage)
+- Non-conformance fully addressed by NCR disposition with no systemic implication
+- Customer cosmetic preference that doesn't violate any specification
+- Minor documentation errors caught and corrected within the same day
+
+### 3.2 CAPA Action Hierarchy (Effectiveness Ranking)
+
+Corrective actions are not created equal. Rank by effectiveness and default to the highest feasible level:
+
+| Rank | Control Type | Example | Effectiveness | Typical Cost |
+|---|---|---|---|---|
+| 1 | **Elimination** | Redesign to remove the failure mode entirely | ~100% | High (design change, tooling) |
+| 2 | **Substitution** | Change material, supplier, or process to one that cannot produce the failure | ~95% | Medium-High |
+| 3 | **Engineering Controls (Poka-Yoke)** | Fixture that physically prevents incorrect assembly; sensor that stops machine on out-of-spec condition | ~90% | Medium |
+| 4 | **Detection Controls** | Automated inspection (vision system, laser gauge) that 100% inspects and auto-rejects | ~85% | Medium |
+| 5 | **Administrative Controls** | Updated work instruction, revised procedure, checklist | ~50-60% | Low |
+| 6 | **Training** | Operator retraining on existing procedure | ~30-40% | Low |
+
+If your corrective action is ranked 5 or 6 and a rank 1-4 action is feasible, the CAPA will likely be challenged by auditors. Training alone is never an adequate corrective action for a significant non-conformance.
+
+### 3.3 CAPA Effectiveness Verification Protocol
+
+**Phase 1: Implementation Verification (within 2 weeks of target date)**
+
+| Evidence Required | What to Check | Acceptable | Not Acceptable |
+|---|---|---|---|
+| Document revision | Was the WI/procedure updated to reflect the change? | Revision with effective date and training records | "Will be updated in next revision" |
+| Physical verification | Is the fixture/tool/sensor installed and operational? | Photograph + validation record | Purchase order placed but not installed |
+| Training completion | Were affected personnel trained? | Signed training records with competency assessment | Email sent to team |
+| System update | Were QMS documents, FMEA, control plan updated? | Updated documents with revision and approval | "Will update during next review" |
+
+**Phase 2: Effectiveness Validation (90-day monitoring period)**
+
+| Metric | Calculation | Pass Criteria | Fail Criteria |
+|---|---|---|---|
+| Recurrence rate | Count of same failure mode in monitoring period | Zero recurrences | Any recurrence |
+| Related failure rate | Count of related failure modes in same process | No increase from baseline | Increase suggests incomplete root cause |
+| Process capability | Cpk or Ppk for the affected characteristic | Cpk ≥ 1.33 (or target value) | Cpk below pre-CAPA level |
+| Customer feedback | Complaints related to the addressed failure mode | Zero related complaints | Any related complaint |
+
+**Phase 3: Closure Decision**
+
+| Condition | Decision |
+|---|---|
+| Phase 1 complete + Phase 2 pass criteria met | Close CAPA |
+| Phase 1 complete + Phase 2 shows improvement but not full elimination | Extend monitoring period by 60 days; if still improving, close with condition |
+| Phase 1 complete + Phase 2 shows no improvement | Reopen CAPA; root cause was incorrect or action insufficient |
+| Phase 1 incomplete (action not implemented) | CAPA remains open; escalate for resource allocation |
+| Recurrence during monitoring | Reopen CAPA; do NOT close and open new CAPA for same issue |
+
+### 3.4 CAPA Timeliness Standards
+
+| CAPA Phase | Target Timeline | Regulatory Expectation |
+|---|---|---|
+| Initiation and assignment | Within 5 business days of trigger | FDA: "timely" — typically within 30 days of awareness |
+| Investigation and root cause | Within 30 calendar days | IATF 16949: per customer timeline (often 10-day initial response) |
+| Corrective action plan | Within 45 calendar days | AS9100: per contractual agreement |
+| Implementation | Within 90 calendar days | Varies by complexity; document delays with justification |
+| Effectiveness verification start | Immediately after implementation | Must be defined at initiation |
+| Effectiveness verification completion | 90 days after implementation | FDA: must demonstrate effectiveness, not just implementation |
+| CAPA closure | Within 180 calendar days of initiation (total) | FDA warning letters cite CAPAs open > 1 year as systemic failure |
+
+---
+
+## 4. SPC Interpretation Decision Logic
+
+### 4.1 Control Chart Selection Flowchart
+
+```
+START: What type of data are you charting?
+ │
+ ├─ CONTINUOUS (variable) data — measurements in units (mm, kg, °C, psi)
+ │ ├─ Are you taking subgroups (multiple measurements per sampling event)?
+ │ │ ├─ YES → What is the subgroup size (n)?
+ │ │ │ ├─ n = 2 to 9 → X-bar / R chart
+ │ │ │ ├─ n = 10 to 25 → X-bar / S chart
+ │ │ │ └─ n > 25 → X-bar / S chart (consider reducing subgroup size)
+ │ │ └─ NO (n=1, individual readings) → Individuals / Moving Range (I-MR) chart
+ │ │ Use when: batch process, destructive testing, slow process,
+ │ │ or when each unit is unique
+ │ └─ (Verify data normality assumption for variable charts — I-MR is sensitive
+ │ to non-normality; consider transformation or use nonparametric alternatives)
+ │
+ └─ ATTRIBUTE (discrete) data — counts or proportions
+ ├─ Are you counting DEFECTIVE ITEMS (units that pass or fail)?
+ │ ├─ YES → Is the sample size constant?
+ │ │ ├─ YES → np-chart (count of defectives, fixed sample)
+ │ │ └─ NO → p-chart (proportion defective, variable sample)
+ │ └─ NO → You're counting DEFECTS (multiple defects possible per unit)
+ │ ├─ Is the inspection area/opportunity constant?
+ │ │ ├─ YES → c-chart (count of defects per unit, fixed area)
+ │ │ └─ NO → u-chart (defects per unit, variable area)
+ │ └─ (Verify Poisson assumption for c/u charts)
+ └─ (Attribute charts require larger sample sizes than variable charts for
+ equivalent sensitivity — minimum ~50 for p/np, ~25 for c/u)
+```
+
+### 4.2 Out-of-Control Response Protocol
+
+When a control chart signals an out-of-control condition, follow this response based on the specific signal:
+
+**Rule 1: Point beyond 3σ control limit**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Immediate | Stop process if product is being produced; quarantine output since last known good point | Within minutes |
+| Investigation | Identify the assignable cause — what changed? Check 6M categories systematically | Within 4 hours |
+| Containment | Sort/inspect product produced during the out-of-control period | Within 1 shift |
+| Correction | Address the assignable cause and restart production with increased monitoring | Before next production run |
+| Documentation | NCR if product was affected; update control chart with annotation | Within 24 hours |
+
+**Rule 2: Nine consecutive points on one side of the center line (run)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | Process mean has likely shifted. Check for: tool wear progression, material lot change, environmental drift, measurement calibration shift | Within 1 shift |
+| Adjustment | If assignable cause found: correct. If no assignable cause found and process is still within spec, continue monitoring but increase sampling frequency | Within 24 hours |
+| Recalculation | If the shift is intentional (process improvement) or represents a new process level, recalculate control limits with new data | After 25+ subgroups at new level |
+
+**Rule 3: Six consecutive points steadily increasing or decreasing (trend)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | Process is drifting. Most common causes: tool wear, chemical depletion, thermal drift, filter degradation | Within 1 shift |
+| Projection | At the current drift rate, when will the process exceed the specification limit? This determines urgency | Immediate calculation |
+| Preemptive action | Adjust the process (tool change, chemical replenishment) BEFORE it reaches the spec limit | Before projected spec limit crossing |
+
+**Rule 4: Fourteen consecutive points alternating up and down (stratification/mixing)**
+
+| Response Level | Action | Timeline |
+|---|---|---|
+| Investigation | This pattern indicates over-control (tampering), two alternating streams (e.g., two spindles, two cavities), or systematic measurement error | Within 24 hours |
+| Verification | Check if the subgroup data is being collected from multiple sources that should be charted separately | Within 48 hours |
+| Stratification | If data is from multiple streams, create separate charts for each stream | Within 1 week |
+
+### 4.3 Capability Index Interpretation
+
+| Cpk Value | Interpretation | Action Required |
+|---|---|---|
+| Cpk ≥ 2.00 | Six Sigma capable; consider reducing inspection frequency | Maintain controls; candidate for reduced inspection or skip-lot |
+| 1.67 ≤ Cpk < 2.00 | Highly capable; exceeds most customer requirements | Standard monitoring; meets IATF 16949 requirements for new processes |
+| 1.33 ≤ Cpk < 1.67 | Capable; meets most industry standards | Standard SPC monitoring; meets IATF 16949 minimum for production |
+| 1.00 ≤ Cpk < 1.33 | Marginally capable; producing some defects | Increase monitoring frequency; initiate process improvement; customer notification may be required |
+| 0.67 ≤ Cpk < 1.00 | Not capable; significant defect production | 100% inspection until process is improved; CAPA required; customer notification required |
+| Cpk < 0.67 | Severely incapable | Stop production; sort all WIP and finished goods; engineering review of process and specification |
+
+**Cp vs. Cpk Interpretation:**
+
+| Condition | Meaning | Action |
+|---|---|---|
+| Cp high, Cpk high | Process is both capable and centered | Optimal state; maintain |
+| Cp high, Cpk low | Process has low variation but is not centered on the target | Adjust the process mean; do NOT reduce variation (it's already good) |
+| Cp low, Cpk low | Process has too much variation, possibly also off-center | Reduce variation first (fundamental process improvement), then center |
+| Cp low, Cpk ≈ Cp | Process has too much variation but is centered | Reduce variation; centering is not the issue |
+
+**Pp/Ppk vs. Cp/Cpk:**
+
+| Index | Uses | Represents | When to Use |
+|---|---|---|---|
+| Cp/Cpk | Within-subgroup variation (σ_within) | Short-term or "potential" capability | Evaluating process potential when in statistical control |
+| Pp/Ppk | Overall variation (σ_overall) including between-subgroup shifts | Long-term or "actual" performance | Evaluating what the customer actually receives over time |
+| Pp/Ppk < Cp/Cpk (common) | Process mean is shifting between subgroups | Between-subgroup variation is significant | Investigate what's causing the mean to shift between subgroups |
+| Pp/Ppk ≈ Cp/Cpk | Process is stable over time | Minimal between-subgroup variation | Process is well-controlled; long-term performance matches potential |
+
+---
+
+## 5. Inspection Level Determination
+
+### 5.1 Incoming Inspection Level Decision Matrix
+
+| Factor | Points |
+|---|---|
+| **Supplier History** | |
+| New supplier (< 5 lots received) | 5 |
+| Supplier on probation/watch | 5 |
+| Qualified supplier with PPM 1,000-5,000 | 3 |
+| Qualified supplier with PPM 500-1,000 | 2 |
+| Qualified supplier with PPM < 500 | 1 |
+| Preferred supplier with PPM < 100 | 0 |
+| **Part Criticality** | |
+| Safety-critical characteristic | 5 |
+| Key characteristic (fit/function) | 3 |
+| Standard characteristic | 1 |
+| Cosmetic only | 0 |
+| **Regulatory Requirement** | |
+| FDA/medical device requiring incoming inspection | 5 |
+| Aerospace with special process (NADCAP) | 4 |
+| Automotive with customer-designated special characteristic | 3 |
+| Standard ISO 9001 environment | 1 |
+| **Recent Quality History (last 6 months)** | |
+| NCR issued against this part/supplier combination | +3 |
+| Customer complaint traced to this component | +4 |
+| SCAR currently open against this supplier | +3 |
+| No quality issues | 0 |
+
+**Inspection Level Assignment:**
+
+| Total Points | Inspection Level | Typical Approach |
+|---|---|---|
+| 0–3 | Reduced / Skip-Lot | CoC review + skip-lot verification (every 3rd or 5th lot) |
+| 4–7 | Normal (AQL Level II) | Standard AQL sampling per ANSI/ASQ Z1.4 |
+| 8–11 | Tightened (AQL Level III) | Tightened sampling or increased sample size |
+| 12+ | 100% / Full Inspection | 100% inspection of critical characteristics |
+
+### 5.2 ANSI/ASQ Z1.4 Quick Reference
+
+**Sample Size Code Letters (Normal Inspection, General Level II):**
+
+| Lot Size | Code Letter | Sample Size (AQL 1.0) |
+|---|---|---|
+| 2–8 | A | 2 (Ac=0, Re=1) |
+| 9–15 | B | 3 (Ac=0, Re=1) |
+| 16–25 | C | 5 (Ac=0, Re=1) |
+| 26–50 | D | 8 (Ac=0, Re=1) |
+| 51–90 | E | 13 (Ac=1, Re=2) |
+| 91–150 | F | 20 (Ac=1, Re=2) |
+| 151–280 | G | 32 (Ac=2, Re=3) |
+| 281–500 | H | 50 (Ac=3, Re=4) |
+| 501–1,200 | J | 80 (Ac=5, Re=6) |
+| 1,201–3,200 | K | 125 (Ac=7, Re=8) |
+| 3,201–10,000 | L | 200 (Ac=10, Re=11) |
+| 10,001–35,000 | M | 315 (Ac=14, Re=15) |
+| 35,001–150,000 | N | 500 (Ac=21, Re=22) |
+
+**Switching Rules:**
+
+| Current Level | Switch Condition | Switch To |
+|---|---|---|
+| Normal | 2 of 5 consecutive lots rejected | Tightened |
+| Normal | 10 consecutive lots accepted AND production at steady rate AND approved by responsible authority | Reduced |
+| Tightened | 5 consecutive lots accepted | Normal |
+| Tightened | 10 consecutive lots not accepted | Discontinue inspection; require supplier corrective action |
+| Reduced | 1 lot rejected | Normal |
+| Reduced | Production irregular or other conditions warrant | Normal |
+
+### 5.3 Skip-Lot Qualification Requirements
+
+**Qualification Criteria (all must be met):**
+1. Supplier is on the Approved Supplier List with "preferred" or "qualified" status
+2. Minimum 10 consecutive lots accepted at normal inspection level
+3. Supplier's process capability (Cpk) for critical characteristics ≥ 1.33, verified by supplier data AND incoming inspection data
+4. No open SCARs against the supplier for this part number
+5. Supplier has a certified quality management system (ISO 9001 minimum; industry-specific certification preferred)
+6. Written agreement documenting skip-lot terms, reversion criteria, and data submission requirements
+
+**Skip-Lot Frequencies:**
+
+| Qualification Level | Inspection Frequency | Reversion Trigger |
+|---|---|---|
+| Skip-Lot 1 | Every 2nd lot | 1 lot rejection |
+| Skip-Lot 2 | Every 3rd lot | 1 lot rejection or supplier Cpk drops below 1.33 |
+| Skip-Lot 3 | Every 5th lot | 1 lot rejection, Cpk concern, or supplier quality system change |
+| CoC Reliance | CoC review only; periodic verification (annual or per-lot-change) | Any NCR, customer complaint, or audit finding |
+
+---
+
+## 6. Supplier Quality Escalation Ladder
+
+### 6.1 Detailed Escalation Process
+
+**Level 0: Normal Operations**
+- Supplier meets scorecard expectations (PPM < threshold, OTD > threshold, SCAR closure on time)
+- Standard incoming inspection level
+- Quarterly scorecard review
+- Annual audit (if risk-based schedule warrants)
+
+**Level 1: SCAR Issued**
+- **Trigger:** Single significant non-conformance (> $5,000 impact or safety/regulatory concern) OR 3+ minor non-conformances on the same part in 90 days
+- **Actions:**
+ - Formal SCAR issued with 8D or equivalent RCA requirement
+ - Supplier has 10 business days for initial response (containment + preliminary root cause)
+ - Supplier has 30 calendar days for full corrective action plan with implementation timeline
+ - Quality engineering review of SCAR response for adequacy
+ - Increase incoming inspection level for the affected part number
+- **Exit criteria:** SCAR accepted and closed with verified effectiveness (90-day monitoring)
+
+**Level 2: Supplier on Watch / Probation**
+- **Trigger:** SCAR not responded to within timeline OR corrective action not effective (recurrence during monitoring) OR scorecard falls below minimum threshold for 2 consecutive quarters
+- **Actions:**
+ - Supplier notified of probation status in writing (Quality Manager or Director level)
+ - Procurement notified; new business hold (no new part numbers awarded)
+ - Increase inspection level for ALL part numbers from this supplier (not just affected part)
+ - Monthly performance review calls with supplier quality management
+ - Supplier must submit a comprehensive improvement plan within 15 business days
+ - Consider on-site quality audit focused on the specific failure mode
+- **Exit criteria:** Improvement plan accepted + 2 consecutive quarters meeting scorecard minimum + no new SCARs
+
+**Level 3: Controlled Shipping**
+- **Trigger:** Continued failures during watch period OR critical quality escape that reaches customer
+- **Actions:**
+ - Controlled Shipping Level 1 (CS-1): Supplier adds additional sort/inspection step with data submitted per shipment
+ - If CS-1 ineffective within 60 days: Controlled Shipping Level 2 (CS-2): third-party resident inspector at supplier's facility, at supplier's expense
+ - All sort/inspection costs debited to supplier
+ - Weekly performance review calls with supplier VP/GM level
+ - Begin qualification of alternate source (if not already underway)
+- **Exit criteria:** 90 consecutive days of zero non-conformances under controlled shipping + root cause fully addressed + systemic improvements validated
+
+**Level 4: New Source Qualification / Phase-Out**
+- **Trigger:** No sustained improvement under controlled shipping OR supplier unwilling/unable to invest in required improvements
+- **Actions:**
+ - Formal notification to supplier of intent to transfer business
+ - Accelerated alternate supplier qualification (expedite PPAP/FAI/first articles)
+ - Reduce business allocation as alternate source ramps up
+ - Maintain controlled shipping on remaining volume
+ - Ensure last-time-buy quantities cover the transition period
+ - Document all quality costs incurred for potential recovery
+- **Timeline:** Depends on part complexity and alternate source readiness; typically 3-12 months
+
+**Level 5: ASL Removal**
+- **Trigger:** Qualification of alternate source complete OR supplier's quality system failure is fundamental (e.g., data falsification, loss of certification)
+- **Actions:**
+ - Formal removal from Approved Supplier List
+ - Final shipment received and inspected under 100% inspection
+ - All supplier-owned tooling at our facility: disposition per contract terms
+ - Our tooling at supplier's facility: retrieve per contract terms
+ - Close all open SCARs as "supplier removed"
+ - Retain supplier quality file for minimum 7 years (regulatory record retention)
+ - Update OASIS (aerospace) or relevant industry databases
+- **Re-entry:** If supplier applies for re-qualification, treat as a new supplier with full qualification process; require evidence that systemic issues were addressed
+
+### 6.2 Escalation Decision Quick Reference
+
+| Situation | Start at Level | Rationale |
+|---|---|---|
+| First minor NC from good supplier | Handle via NCR, no escalation | Single event doesn't warrant formal escalation |
+| First significant NC from good supplier | Level 1 (SCAR) | Significant impact requires formal root cause |
+| Third minor NC in 90 days from same supplier/part | Level 1 (SCAR) | Pattern indicates systemic issue |
+| SCAR response inadequate or late | Level 2 (Watch) | Non-responsiveness is itself a quality system failure |
+| NC reaches customer | Level 2 minimum; Level 3 if safety-related | Customer impact demands immediate escalation |
+| Falsified documentation discovered | Level 4 minimum; Level 5 if confirmed | Trust is broken; containment scope is unknown |
+| Sole-source supplier with quality problems | Level 1 with parallel Level 4 actions (qualify alternate) | Business continuity requires measured response; don't threaten what you can't execute |
+
+---
+
+## 7. Cost of Quality Calculation Models
+
+### 7.1 COQ Category Definitions and Tracking
+
+**Prevention Costs (invest to prevent defects):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Quality planning | Hours × labor rate for quality planning activities | 0.2–0.5% |
+| Process validation/qualification | Labor + equipment + materials for IQ/OQ/PQ | 0.3–0.8% |
+| Supplier qualification | Audit travel + labor + first article costs | 0.1–0.3% |
+| Training (quality-related) | Hours × labor rate + training materials | 0.1–0.3% |
+| SPC implementation/maintenance | Software licenses + labor for chart maintenance | 0.1–0.2% |
+| Design reviews / FMEA | Hours × labor rate for cross-functional reviews | 0.2–0.5% |
+| Poka-yoke development | Design + fabrication + validation of error-proofing | 0.2–0.5% |
+
+**Appraisal Costs (cost of verifying conformance):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Incoming inspection | Hours × labor rate + gauge costs | 0.3–0.8% |
+| In-process inspection | Hours × labor rate (including production wait time) | 0.5–1.5% |
+| Final inspection / testing | Hours × labor rate + test equipment depreciation | 0.3–1.0% |
+| Calibration program | Service contracts + labor + standards | 0.1–0.3% |
+| Audit program (internal + external) | Labor + travel + registration fees | 0.1–0.3% |
+| Laboratory testing | Internal lab costs or external lab fees | 0.2–0.5% |
+
+**Internal Failure Costs (defects caught before shipment):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Scrap | Scrapped material value + processing labor wasted | 1.0–3.0% |
+| Rework | Labor + materials for rework operations | 0.5–2.0% |
+| Re-inspection | Hours × labor rate for re-inspection after rework | 0.1–0.5% |
+| MRB processing | Hours × labor rate for disposition activities | 0.1–0.3% |
+| Root cause investigation | Hours × labor rate for RCA team activities | 0.2–0.5% |
+| Production delays | Lost production time due to quarantine, investigation | 0.5–2.0% |
+| Supplier sort/containment | Third-party sort labor or internal sort labor for supplier-caused NC | 0.1–0.5% |
+
+**External Failure Costs (defects that reach the customer):**
+
+| Cost Element | How to Measure | Typical Range (% of revenue) |
+|---|---|---|
+| Customer returns / credits | Credit memos + return shipping + restocking labor | 0.5–2.0% |
+| Warranty claims | Claim value + processing labor | 0.5–3.0% |
+| Field service / repair | Service labor + travel + parts | 0.3–1.5% |
+| Customer complaint processing | Hours × labor rate for investigation + response | 0.2–0.5% |
+| Recall / field correction | Product replacement + notification + shipping + regulatory | 0.0–5.0% (highly variable) |
+| Regulatory action costs | Fines, consent decree compliance, increased inspections | 0.0–10.0% (catastrophic when triggered) |
+| Reputation / lost business | Lost revenue from customer defection (estimate) | Difficult to measure; typically 2-10x direct costs |
+
+### 7.2 COQ Business Case Model
+
+**Calculating ROI for Quality Investment:**
+
+```
+ROI = (Failure Cost Reduction - Investment Cost) / Investment Cost × 100%
+
+Where:
+ Failure Cost Reduction = (Current internal + external failure costs)
+ - (Projected failure costs after investment)
+ Investment Cost = Prevention cost increase + appraisal cost change
+```
+
+**Rule of Thumb Multipliers:**
+
+| Investment Type | Expected ROI | Payback Period |
+|---|---|---|
+| Poka-yoke (error-proofing) | 5:1 to 20:1 | 3–6 months |
+| SPC implementation | 3:1 to 10:1 | 6–12 months |
+| Supplier development program | 2:1 to 8:1 | 12–24 months |
+| Process validation improvement | 4:1 to 15:1 | 6–18 months |
+| Training program upgrade | 1:1 to 3:1 | 12–24 months |
+
+### 7.3 MRB Decision Process — Economic Model
+
+When disposition is not dictated by safety or regulatory requirements, use economic analysis:
+
+**Rework vs. Scrap Decision:**
+
+```
+Rework if: C_rework + C_reinspect < C_replacement × (1 + premium)
+
+Where:
+ C_rework = Direct rework labor + materials + machine time
+ C_reinspect = Re-inspection labor + any additional testing
+ C_replacement = Purchase price or manufacturing cost of replacement unit
+ premium = Schedule urgency factor (0% if no urgency, 10-50% if production impact,
+ 100%+ if customer delivery at risk)
+```
+
+**Sort vs. Return Decision (for supplier-caused lots):**
+
+```
+Sort if: (C_sort < C_return_freight + C_production_delay) AND (expected yield > 70%)
+
+Where:
+ C_sort = Sort labor hours × rate (typically $25-50/hr for manual sort,
+ $50-100/hr for dimensional sort)
+ C_return_freight = Shipping cost + handling + administrative
+ C_production_delay = (Days of delay × daily production value at risk)
+ expected yield = Estimated % of lot that will pass sort
+ (use sample data to estimate)
+```
+
+**Use-As-Is vs. Sort/Rework Decision (non-safety, non-regulatory):**
+
+```
+Use-as-is if: Risk_functional ≤ Acceptable_risk
+ AND C_use_as_is < C_sort_or_rework
+ AND engineering provides documented justification
+
+Where:
+ Risk_functional = P(failure in use) × Impact(failure)
+ C_use_as_is = Warranty risk increase (estimated) + documentation cost
+ C_sort_or_rework = Direct sort/rework costs + production delay costs
+```
+
+---
+
+## 8. MRB Decision Process — Detailed Workflow
+
+### 8.1 MRB Meeting Structure
+
+**Frequency:** Scheduled weekly; ad hoc for urgent dispositions (safety-critical, production-blocking)
+
+**Required Attendees:**
+- Quality Engineering (chair, facilitates and documents)
+- Design/Product Engineering (functional impact assessment)
+- Manufacturing Engineering (reworkability assessment)
+- Production/Operations (schedule impact)
+- Procurement (supplier-related dispositions, commercial impact)
+- Optional: Regulatory Affairs (if regulatory implications), Customer Quality (if customer notification required)
+
+**Standard Agenda:**
+1. Review of new NCRs pending disposition (by priority: safety first, then production-blocking, then age)
+2. Presentation of data package per NCR (measurements, photographs, process data)
+3. Engineering assessment of functional impact
+4. Disposition decision with documented rationale
+5. Review of aging NCRs (> 15 days without disposition)
+6. Review of MRB metrics (volume, cycle time, cost)
+
+### 8.2 MRB Documentation Requirements
+
+Each MRB disposition must include:
+
+| Element | Purpose | Who Provides |
+|---|---|---|
+| NCR number and description | Identification and traceability | Quality Engineering |
+| Part number, revision, quantity | Scope of disposition | Quality Engineering |
+| Specification violated (clause, dimension, requirement) | Clarity on what's nonconforming | Quality Engineering |
+| Measurement data (actuals vs. tolerances) | Evidence base for disposition | Quality Engineering / Inspection |
+| Photographs (if applicable) | Visual evidence | Quality Engineering / Inspection |
+| Engineering justification (for use-as-is or repair) | Technical rationale for accepting deviation | Design/Product Engineering |
+| Risk assessment (for safety-related items) | Formal risk evaluation | Design/Product Engineering + Quality |
+| Customer approval reference (if required) | Compliance with contract/standard | Quality Engineering |
+| Disposition decision | The decision itself | MRB consensus |
+| Signatures of all MRB members | Accountability and traceability | All attendees |
+| Cost impact | Financial tracking for COQ | Quality Engineering + Finance |
+| CAPA reference (if initiated) | Link to systemic corrective action | Quality Engineering |
diff --git a/web-app/public/skills/quality-nonconformance/references/edge-cases.md b/web-app/public/skills/quality-nonconformance/references/edge-cases.md
new file mode 100644
index 00000000..c98d9458
--- /dev/null
+++ b/web-app/public/skills/quality-nonconformance/references/edge-cases.md
@@ -0,0 +1,588 @@
+# Quality & Non-Conformance Management — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous quality situations that don't resolve through standard NCR/CAPA workflows.
+
+These edge cases represent the scenarios that separate experienced quality engineers from everyone else. Each one involves competing priorities, ambiguous data, regulatory pressure, and real business impact. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When a quality situation doesn't fit a clean NCR category — when the data is ambiguous, when multiple stakeholders have legitimate competing claims, or when the regulatory and business implications justify deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Do not skip documentation requirements; these are the situations that end up in audit findings, regulatory actions, or legal proceedings.
+
+---
+
+### Edge Case 1: Customer-Reported Field Failure with No Internal Detection
+
+**Situation:**
+Your medical device company ships Class II endoscopic accessories to a hospital network. Your internal quality data is clean — incoming inspection acceptance rate is 99.7%, in-process defect rate is below 200 PPM, and final inspection has not flagged any issues for the last 6 months. Then a customer complaint comes in: three units from different lots failed during clinical use. The failure mode is a fractured distal tip during retraction, which was not part of your inspection plan because design verification showed the material exceeds the fatigue limit by 4x. The hospital has paused use of your product pending investigation.
+
+**Why It's Tricky:**
+The instinct is to defend your data. "Our inspection shows everything is within specification. The customer must be using the product incorrectly." This is wrong and dangerous for three reasons: (1) field failures can expose failure modes your test plan doesn't cover, (2) clinical use conditions differ from bench testing, and (3) in FDA-regulated environments, dismissing customer complaints without investigation is itself a regulatory violation per 21 CFR 820.198.
+
+The deeper problem is that your inspection plan was designed around the design verification data, which tested fatigue under controlled, uniaxial loading. Clinical use involves multiaxial loading with torsion, and the fatigue characteristics under combined loading may be significantly different. Your process is "in control" but your control plan has a coverage gap.
+
+**Common Mistake:**
+Treating this as a customer-use issue. Sending a "letter of clarification" on proper use without investigating the failure mode. This delays discovery, may worsen patient safety risk, and creates an adverse audit trail if FDA reviews your complaint handling.
+
+The second common mistake: initiating a CAPA that focuses on inspection. "Add fatigue testing to final inspection" solves nothing if the inspection uses the same uniaxial loading condition as the original design verification.
+
+**Expert Approach:**
+1. **Immediate containment:** Place a quality hold on all units of the affected part numbers in your finished goods, distribution, and at the hospital's inventory. Contact the hospital's biomedical engineering department to coordinate the hold — they need serial/lot numbers to identify affected inventory.
+2. **Complaint investigation per 820.198:** Open a formal complaint record. Classify for MDR determination — fractured device during clinical use meets the "malfunction that could cause or contribute to death or serious injury" threshold, requiring MDR filing within 30 days.
+3. **Failure analysis:** Request the failed units from the hospital for physical failure analysis. Conduct fractographic analysis (SEM if needed) to determine the fracture mode — was it fatigue (progressive crack growth), overload (single-event), stress corrosion, or manufacturing defect (inclusion, porosity)?
+4. **Gap analysis on test coverage:** Map the clinical loading conditions against your design verification test protocol. If the failure mode is combined loading fatigue, your uniaxial test would not have detected it. This is a design control gap per 820.30, not a manufacturing control gap.
+5. **Design verification update:** Develop a multiaxial fatigue test that simulates clinical conditions. Test retained samples from the affected lots AND from current production. If retained samples fail the updated test, the scope of the problem is potentially every unit shipped.
+6. **Risk assessment per ISO 14971:** Update the risk file with the newly identified hazard. Calculate the risk priority based on the severity (clinical failure) and probability (based on complaint rate vs. units in service). Determine whether the risk is acceptable per your risk acceptance criteria.
+7. **Field action determination:** Based on the risk assessment, determine whether a voluntary recall, field correction, or enhanced monitoring is appropriate. Document the decision with the risk data supporting it.
+8. **CAPA:** Root cause is a gap in design verification testing — the failure mode was not characterized under clinical loading conditions. Corrective action addresses the test protocol, not the manufacturing process.
+
+**Key Indicators:**
+- Complaint rate vs. units in service determines population risk (e.g., 3 failures in 10,000 units = 300 PPM field failure rate)
+- Fracture surface morphology distinguishes fatigue, overload, and material defects
+- Time-to-failure pattern (all early-life vs. random vs. wear-out) indicates failure mechanism
+- If multiple lots are affected, the root cause is likely design or process-related, not material-lot-specific
+
+**Documentation Required:**
+- Formal complaint records per 820.198
+- MDR filing documentation
+- Failure analysis report with photographs and fractography
+- Updated risk file per ISO 14971
+- Revised design verification test protocol
+- Field action decision documentation (including decision NOT to recall, if applicable)
+- CAPA record linking complaint → investigation → root cause → corrective action
+
+---
+
+### Edge Case 2: Supplier Audit Reveals Falsified Certificates of Conformance
+
+**Situation:**
+During a routine audit of a casting supplier (Tier 2 supplier to your automotive Tier 1 operation), your auditor discovers that the material certificates for A356 aluminum castings do not match the spectrometer results. The supplier has been submitting CoCs showing material composition within specification, but the auditor's portable XRF readings on randomly selected parts show silicon content at 8.2% against a specification of 6.5-7.5%. The supplier's quality manager initially claims the XRF is inaccurate, but when pressed, admits that their spectrometer has been out of calibration for 4 months, and they've been using historical test results on the CoCs rather than actual lot-by-lot test data.
+
+**Why It's Tricky:**
+This is not a simple non-conformance — it's a quality system integrity failure. The supplier did not simply ship nonconforming parts; they submitted fraudulent documentation. The distinction matters because: (1) every shipment received during the 4-month period is now suspect, (2) you cannot trust ANY data from this supplier without independent verification, (3) in automotive, this may constitute a failure to maintain IATF 16949 requirements, and (4) parts from this supplier may already be in customer vehicles.
+
+The containment scope is potentially enormous. A356 aluminum with elevated silicon has different mechanical properties — it may be more brittle. If these castings are structural or safety-critical, the implications extend to end-of-line testing, vehicle recalls, and NHTSA notification.
+
+**Common Mistake:**
+Treating this like a normal NCR. Writing a SCAR and asking the supplier to "improve their testing process." This underestimates the severity — the issue is not process improvement but fundamental integrity. A supplier that falsifies data will not be fixed by a corrective action request.
+
+The second common mistake: immediately terminating the supplier without securing containment. If you have weeks of WIP and finished goods containing these castings, cutting off the supplier before you've contained and sorted the affected inventory creates a dual crisis — quality AND supply.
+
+**Expert Approach:**
+1. **Preserve evidence immediately.** Photograph the audit findings, retain the XRF readings, request copies of the CoCs for the last 4 months, and document the supplier quality manager's admission in the audit notes with date, time, and witnesses. This evidence may be needed for legal proceedings or regulatory reporting.
+2. **Scope the containment.** Identify every lot received from this supplier in the last 4+ months (add buffer — the calibration may have drifted before formal "out of calibration" date). Trace those lots through your operation: incoming stock, WIP, finished goods, shipped to customer, in customer's inventory or vehicles.
+3. **Independent verification.** Send representative samples from each suspect lot to an accredited independent testing laboratory for full material composition analysis. Do not rely on the supplier's belated retesting — their data has zero credibility.
+4. **Risk assessment on affected product.** If material composition is out of spec, have design engineering evaluate the functional impact. A356 with 8.2% Si instead of max 7.5% may still be functional depending on the application, or it may be critically weakened for a structural casting. The answer depends on the specific part function and loading conditions.
+5. **Customer notification.** In IATF 16949 environments, customer notification is mandatory when suspect product may have been shipped. Contact your customer quality representative within 24 hours. Provide lot/date range, the nature of the issue, and your containment actions.
+6. **Automotive-specific reporting.** If the parts are safety-critical and the composition affects structural integrity, evaluate NHTSA reporting obligations per 49 CFR Part 573 (defect notification). Consult legal counsel — the bar for vehicle safety defect reporting is "poses an unreasonable risk to motor vehicle safety."
+7. **Supplier disposition.** This is an immediate escalation to Level 4-5 on the supplier ladder. Begin alternate source qualification in parallel. Maintain the supplier on controlled shipping (CS-2, third-party inspection) only for the duration needed to transition. Do not invest in "developing" a supplier that falsified data — the trust foundation is broken.
+8. **Systemic review.** Audit all other CoC-reliant incoming inspection processes. If this supplier falsified data, what is the probability that others are as well? Increase verification sampling on other CoC-reliance suppliers, especially those with single-source positions.
+
+**Key Indicators:**
+- Duration of falsification determines containment scope (months × volume = total suspect population)
+- The specific spec exceedance determines functional risk (minor chemistry drift vs. major composition deviation)
+- Traceability of material lots through your production determines the search space
+- Whether the supplier proactively disclosed vs. you discovered impacts the trust assessment
+
+**Documentation Required:**
+- Audit report with all findings, evidence, and admissions
+- XRF readings and independent lab results
+- Complete lot traceability from supplier through your process to customer
+- Risk assessment on functional impact of material deviation
+- Customer notification records with acknowledgment
+- Legal review documentation (privilege-protected as applicable)
+- Supplier escalation and phase-out plan
+
+---
+
+### Edge Case 3: SPC Shows Process In-Control But Customer Complaints Are Rising
+
+**Situation:**
+Your CNC turning operation produces shafts for a precision instrument manufacturer. Your SPC charts on the critical OD dimension (12.00 ±0.02mm) have been stable for 18 months — X-bar/R chart shows a process running at 12.002mm mean with Cpk of 1.45. No control chart signals. Your internal quality metrics are green across the board. But the customer's complaint rate on your shafts has tripled in the last quarter. Their failure mode: intermittent binding in the mating bore assembly. Your parts meet print, their parts meet print, but the assembly doesn't work consistently.
+
+**Why It's Tricky:**
+The conventional quality response is "our parts meet specification." And technically, that's true. But the customer's assembly process is sensitive to variation WITHIN your specification. Their bore is also within specification, but when your shaft is at the high end of tolerance (+0.02) and their bore is at the low end, the assembly binds. Both parts individually meet print, but the tolerance stack-up creates interference in the worst-case combination.
+
+The SPC chart is not lying — your process is in statistical control and capable by every standard metric. The problem is that capability indices measure your process against YOUR specification, not against the functional requirement of the assembly. A Cpk of 1.45 means you're producing virtually no parts outside ±0.02mm, but if the actual functional window is ±0.01mm centered on the nominal, your process is sending significant variation into a critical zone.
+
+**Common Mistake:**
+Dismissing the complaint because the data says you're in spec. Sending a letter citing your Cpk and stating that the parts conform. This is technically correct and operationally wrong — it destroys the customer relationship and ignores the actual problem.
+
+The second mistake: reacting by tightening your internal specification without understanding the functional requirement. If you arbitrarily cut your tolerance to ±0.01mm, you increase your scrap rate (and cost) without certainty that it solves the assembly issue.
+
+**Expert Approach:**
+1. **Acknowledge the complaint and avoid the "we meet spec" defense.** The customer is experiencing real failures. Whether they're caused by your variation, their variation, or the interaction of both is what needs to be determined — not assumed.
+2. **Request the customer's mating component data.** Ask for their bore SPC data — mean, variation, Cpk, distribution shape. You need to understand both sides of the assembly equation.
+3. **Conduct a tolerance stack-up analysis.** Using both your shaft data and their bore data, calculate the assembly clearance distribution. Identify what percentage of assemblies fall into the interference zone. This analysis converts "your parts meet spec" into "X% of assemblies will have interference problems."
+4. **Evaluate centering vs. variation.** If the problem is that your process runs at 12.002mm (slightly above nominal) and their bore is centered low, the fix may be as simple as re-centering your process to 11.998mm — shifting the mean away from the interference zone without changing the variation.
+5. **Consider bilateral specification refinement.** Propose a joint engineering review to establish a tighter bilateral tolerance that accounts for both process capabilities. If your Cpk for ±0.01mm around a recentered mean is still > 1.33, the tighter spec is achievable.
+6. **Update your control plan.** If the assembly-level functional requirement is tighter than the print tolerance, your control plan should reflect the actual functional target, not just the nominal ± tolerance from the drawing.
+7. **This is NOT a CAPA.** This is a specification adequacy issue, not a non-conformance. The correct vehicle is an engineering change process to update the specification, not a CAPA to "fix" a process that is operating correctly per its current requirements.
+
+**Key Indicators:**
+- Your process Cpk relative to the FUNCTIONAL tolerance (not drawing tolerance) is the key metric
+- Assembly clearance distribution reveals the actual failure probability
+- Shift in customer complaint timing may correlate with a process change on the customer's side (did they tighten their bore process?)
+- Temperature effects on both parts at assembly (thermal expansion can change clearances)
+
+---
+
+### Edge Case 4: Non-Conformance Discovered on Already-Shipped Product
+
+**Situation:**
+During a routine review of calibration records, your metrology technician discovers that a CMM probe used for final inspection of surgical instrument components had a qualification failure that was not flagged. The probe was used to inspect and release 14 lots over the past 6 weeks. The qualification failure indicates the probe may have been reading 0.015mm off on Z-axis measurements. The affected dimension is a critical depth on an implantable device component with a tolerance of ±0.025mm. Of the 14 lots (approximately 8,400 units), 9 lots have already been shipped to three different customers (medical device OEMs). Five lots are still in your finished goods inventory.
+
+**Why It's Tricky:**
+The measurement uncertainty introduced by the probe error doesn't mean the parts are nonconforming — it means you can't be certain they're conforming. A 0.015mm bias on a ±0.025mm tolerance doesn't automatically reject all parts, but it may have caused you to accept parts that were actually near or beyond the lower specification limit.
+
+For FDA-regulated medical device components, measurement system integrity is not optional — it's a core requirement of 21 CFR 820.72 (inspection, measuring, and test equipment). A calibration failure that went undetected means your quality records for 14 lots cannot be relied upon. This is a measurement system failure, not necessarily a product failure, but you must treat it as a potential product failure until proven otherwise.
+
+**Common Mistake:**
+Recalling all 14 lots immediately without first analyzing the data. A blind recall of 8,400 implantable device components creates massive supply chain disruption for your customers (who may be OEMs that incorporate your component into a finished device in their own supply chain). If the actual parts are conforming (just the measurement was uncertain), the recall causes more harm than it prevents.
+
+The other common mistake: doing nothing because you believe the parts are "probably fine." Failure to investigate and document constitutes a quality system failure, regardless of whether the parts are actually good.
+
+**Expert Approach:**
+1. **Immediate hold on the 5 lots still in inventory.** Quarantine in MRB area. These can be re-inspected.
+2. **Quantify the measurement uncertainty.** Re-qualify the CMM probe and determine the actual bias. Then overlay the bias on the original measurement data for all 14 lots. For each part, recalculate: measured value + bias = potential actual value. Identify how many parts' recalculated values fall outside specification.
+3. **Risk stratification of shipped lots.** Group the 9 shipped lots into three categories:
+ - Parts where recalculated values are well within specification (> 50% of tolerance margin remaining): low risk. Document the analysis but no customer notification needed for these specific lots.
+ - Parts where recalculated values are marginal (within specification but < 25% margin): medium risk. Engineering assessment needed on functional impact.
+ - Parts where recalculated values potentially exceed specification: high risk. Customer notification required; recall or sort at customer.
+4. **Customer notification protocol.** For medium and high-risk lots, notify the customer quality contacts within 24 hours. Provide: lot numbers, the nature of the measurement uncertainty, your risk assessment, and your recommended action (e.g., replace at-risk units, sort at customer site with your quality engineer present, or engineering disposition if parts are functionally acceptable).
+5. **Re-inspect the 5 held lots.** Use a verified, qualified CMM probe. Release lots that pass. Scrap or rework lots that fail.
+6. **Root cause and CAPA.** Root cause: probe qualification failure was not flagged by the CMM operator or the calibration review process. Investigate why: was the qualification check skipped, was the acceptance criteria not clear, was the operator not trained on the significance of qualification failure? CAPA must address the system gap — likely a combination of calibration software alerting, operator procedure, and management review of calibration status.
+7. **Evaluate MDR obligation.** If any shipped parts are potentially outside specification and the component is in an implantable device, evaluate whether this constitutes a reportable event. Consult with Regulatory Affairs — the threshold is whether the situation "could cause or contribute to death or serious injury." The measurement uncertainty may or may not meet this threshold depending on the functional significance of the affected dimension.
+
+**Key Indicators:**
+- The ratio of measurement bias to tolerance width determines the severity (0.015mm bias on ±0.025mm tolerance = 30% of tolerance, which is significant)
+- The distribution of original measurements near the specification limit determines how many parts are truly at risk
+- Whether the bias was consistent or variable determines whether the risk analysis is conservative or optimistic
+- Customer's use of the component (implantable vs. non-patient-contact) determines the regulatory urgency
+
+---
+
+### Edge Case 5: CAPA That Addresses Symptom, Not Root Cause
+
+**Situation:**
+Six months ago, your company closed CAPA-2024-0087 for a recurring dimensional non-conformance on a machined housing. The root cause was documented as "operator measurement technique variation" and the corrective action was "retrain all operators on use of bore micrometer per WI-3302 and implement annual re-certification." Training records show all operators were retrained. The CAPA effectiveness check at 90 days showed zero recurrences. The CAPA was closed.
+
+Now, the same defect is back. Three NCRs in the last 30 days — all the same failure mode (bore diameter out of tolerance on the same feature). The operators are certified. The work instruction has not changed. The micrometer is in calibration.
+
+**Why It's Tricky:**
+This CAPA failure is embarrassing and common. It reveals two problems: (1) the original root cause analysis was insufficient — "operator technique variation" is a symptom, not a root cause, and (2) the 90-day effectiveness monitoring happened to coincide with a period when the actual root cause was quiescent.
+
+The deeper issue is organizational: the company's CAPA process accepted a "retrain the operator" corrective action for a recurring dimensional non-conformance. An experienced quality engineer would flag training-only CAPAs for manufacturing non-conformances as inherently weak.
+
+**Common Mistake:**
+Opening a new CAPA with a new number and starting fresh. This creates the illusion of a new problem when it's the same unresolved problem. The audit trail now shows a closed CAPA (false closure) and a new CAPA — which is exactly what an FDA auditor looks for when evaluating CAPA system effectiveness.
+
+The second mistake: doubling down on training — "more training, more frequently, with a competency test." If the first round of training didn't fix the problem, a second round won't either.
+
+**Expert Approach:**
+1. **Reopen CAPA-2024-0087, do not create a new CAPA.** The original CAPA was ineffective. Document the recurrence as evidence that the CAPA effectiveness verification was premature or based on insufficient data. The CAPA system must track this as a single unresolved issue, not two separate issues.
+2. **Discard the original root cause.** "Operator technique variation" must be explicitly rejected as a root cause. Document why: training was implemented and verified, operators are certified, yet the defect recurred. Therefore, the root cause was not operator technique.
+3. **Restart root cause analysis with fresh eyes.** Form a new team that includes people who were NOT on the original team (fresh perspective). Use Ishikawa/6M to systematically investigate all cause categories — the original team likely converged too quickly on the Man category.
+4. **Investigate the actual root cause candidates:**
+ - Machine: Is the CNC spindle developing runout or thermal drift? Check spindle vibration data and thermal compensation logs.
+ - Material: Has the raw material lot changed? Different material hardness affects cutting dynamics and can shift dimensions.
+ - Method: Did the tool path or cutting parameters change? Check the CNC program revision history.
+ - Measurement: Is the bore micrometer the right gauge for this measurement? What's the Gauge R&R? If the gauge is marginal, operators may get variable results even with correct technique.
+ - Environment: Did ambient temperature change with the season? A 5°C temperature swing in a non-climate-controlled shop can shift dimensions by 5-10μm on aluminum parts.
+5. **Design the corrective action at a higher effectiveness rank.** If root cause is machine-related: implement predictive maintenance or in-process gauging (detection control, rank 4). If material-related: adjust process parameters by material lot or source from a more consistent supplier (substitution, rank 2). If measurement-related: install a hard-gauging fixture (engineering control, rank 3). Training is only acceptable as a SUPPLEMENTARY action, never the primary action.
+6. **Extend the effectiveness monitoring period.** The original 90-day monitoring was insufficient. For a recurring issue, monitor for 6 months or 2 full cycles of the suspected environmental/seasonal factor, whichever is longer. Define quantitative pass criteria (e.g., zero recurrences of the specific failure mode AND Cpk on the affected dimension ≥ 1.33 for the full monitoring period).
+
+**Key Indicators:**
+- The fact that 90-day monitoring showed zero recurrence but the defect returned suggests the root cause is intermittent or cyclic (seasonal temperature, tool wear cycle, material lot cycle)
+- Operator-related root causes are almost never the actual root cause for dimensional non-conformances in CNC machining — the machine is controlling the dimension, not the operator
+- Gauge R&R data is critical — if the measurement system contribution is > 30% of the tolerance, the measurement itself may be the root cause of apparent non-conformances
+
+---
+
+### Edge Case 6: Audit Finding That Challenges Existing Practice
+
+**Situation:**
+During a customer audit of your aerospace machining facility, the auditor cites a finding against your first article inspection (FAI) process. Your company performs FAI per AS9102 and has a long track record of conforming FAIs. The auditor's finding: you do not perform a full FAI resubmission when you change from one qualified tool supplier to another for the same cutting tool specification. Your position is that the tool meets the same specification (material, geometry, coating) and the cutting parameters are identical, so no FAI is required. The auditor contends that a different tool supplier — even for the same specification — constitutes a "change in manufacturing source for special processes or materials" under AS9102, requiring at minimum a partial FAI.
+
+**Why It's Tricky:**
+Both positions have merit. AS9102 requires FAI when there is a change in "manufacturing source" for the part. A cutting tool is not the part — it's a consumable used to make the part. But the auditor's argument is that a different tool supplier may have different cutting performance characteristics (tool life, surface finish, dimensional consistency) that could affect the part even though the tool itself meets the same specification.
+
+The practical reality is that your machinists know different tool brands cut differently. A Sandvik insert and a Kennametal insert with the same ISO designation will produce slightly different surface finishes and may wear at different rates. In aerospace, "slightly different" can matter.
+
+**Common Mistake:**
+Arguing with the auditor during the audit. Debating the interpretation of AS9102 in real time is unproductive and creates an adversarial audit relationship. Accept the finding, respond formally, and use the response to present your interpretation with supporting evidence.
+
+The second mistake: over-correcting by requiring a full FAI for every consumable change. This would make your FAI process unworkable — you change tool inserts multiple times per shift. The corrective action must be proportionate to the actual risk.
+
+**Expert Approach:**
+1. **Accept the audit finding formally.** Do not concede that your interpretation is wrong — accept that the auditor has identified an area where your process does not explicitly address the scenario. Write the response as: "We acknowledge the finding and will evaluate our FAI triggering criteria for manufacturing consumable source changes."
+2. **Research industry guidance.** AS9102 Rev C, IAQG FAQ documents, and your registrar's interpretation guides may provide clarity. Contact your certification body's technical manager for their interpretation.
+3. **Risk-based approach.** Categorize tool supplier changes by risk:
+ - Same specification, same brand/series, different batch: No FAI required (normal tool replacement)
+ - Same specification, different brand: Evaluate with a tool qualification run — measure first articles from the new tool brand against the FAI characteristics. If all characteristics are within specification, document the qualification and don't require formal FAI.
+ - Different specification or geometry: Full or partial FAI per AS9102
+4. **Process change.** Update your FAI trigger procedure to explicitly address consumable source changes. Create a "tool qualification" process that is lighter than FAI but provides documented evidence that the new tool source produces conforming parts.
+5. **Corrective action response.** Your formal response to the auditor should describe the risk-based approach, the tool qualification procedure, and the updated FAI trigger criteria. Demonstrate that you've addressed the gap with a proportionate control, not with a blanket rule that will be unworkable.
+
+**Key Indicators:**
+- The auditor's interpretation may or may not be upheld at the next certification body review — but arguing the point at the audit is always unproductive
+- Your machinist's tribal knowledge about tool brand differences is actually valid evidence — document it
+- The risk-based approach is defensible because AS9100 itself is built on risk-based thinking
+
+---
+
+### Edge Case 7: Multiple Root Causes for Single Non-Conformance
+
+**Situation:**
+Your injection molding operation is producing connectors with intermittent short shots (incomplete fill) and flash simultaneously on the same tool. SPC on shot weight shows variation has doubled over the last month. The standard 5 Whys analysis by the floor quality technician concluded "injection pressure too low" and recommended increasing pressure by 10%. The problem did not improve — in fact, flash increased while short shots continued.
+
+**Why It's Tricky:**
+Short shots and flash are opposing defects. Short shot = insufficient material reaching the cavity. Flash = material escaping the parting line. Having both simultaneously on the same tool is pathological and indicates that the 5 Whys answer ("pressure too low") was oversimplified. Increasing pressure addresses the short shot but worsens the flash. This is a classic case where 5 Whys fails because the failure has multiple interacting causes, not a single linear chain.
+
+**Common Mistake:**
+Continuing to adjust a single parameter (pressure) up and down looking for a "sweet spot." This is tampering — chasing the process around the operating window without understanding what's driving the variation.
+
+**Expert Approach:**
+1. **Stop adjusting.** Return the process to the validated parameters. Document that the attempted pressure increase did not resolve the issue and created additional flash defects.
+2. **Use Ishikawa, not 5 Whys.** Map the potential causes across all 6M categories. For this type of combined defect, the most likely interacting causes are:
+ - **Machine:** Worn platens or tie bars allowing non-uniform clamp pressure across the mold face. This allows flash where clamp force is low while restricting fill where the parting line is tight.
+ - **Material:** Material viscosity variation (lot-to-lot MFI variation, or moisture content). High viscosity in one shot → short shot. Low viscosity in next shot → flash.
+ - **Mold (Method):** Worn parting line surfaces creating uneven shut-off. Vent clogging restricting gas escape in some cavities (causing short shots) while flash at the parting line.
+3. **Data collection before root cause conclusion.** Run a short diagnostic study:
+ - Measure clamp tonnage distribution across the mold face (platen deflection check with pressure-indicating film between the parting surfaces)
+ - Check material MFI on the current lot and the last 3 lots
+ - Inspect the mold parting line for wear, verify vent depths
+4. **Address ALL contributing causes.** The corrective actions will likely be multiple:
+ - Mold maintenance (clean vents, re-stone parting line surfaces) — addresses the flash pathway
+ - Material incoming inspection for MFI with tighter acceptance criteria — addresses viscosity variation
+ - Platen deflection correction or mold design modification — addresses the non-uniform clamp force
+5. **The CAPA must capture all three causes.** Document that the single defect (short shot + flash) has three interacting root causes. Each cause has its own corrective action. Effectiveness monitoring must track the combined defect rate, not each cause independently.
+
+**Key Indicators:**
+- Combined opposing defects always indicate multiple interacting causes — never a single parameter
+- Shot-to-shot weight variation (SPC) distinguishes material variation (random pattern) from machine variation (trending or cyclic pattern)
+- Pressure-indicating film between mold halves reveals clamp force distribution problems that are invisible otherwise
+- Vent depth measurements should be part of routine mold PM but are commonly skipped
+
+---
+
+### Edge Case 8: Intermittent Defect That Cannot Be Reproduced on Demand
+
+**Situation:**
+Your electronics assembly line has a 0.3% field return rate on a PCB assembly due to intermittent solder joint failures on a specific BGA (Ball Grid Array) component. The defect has been reported 47 times across approximately 15,000 units shipped over 6 months. X-ray inspection of returned units shows voiding in BGA solder joints exceeding 25% (your internal standard is <20% voiding). However, your in-process X-ray inspection of production units consistently shows voiding below 15%. The defect is real (47 customer failures is not noise), but your inspection process cannot detect or reproduce it.
+
+**Why It's Tricky:**
+The customer failures are real — 47 returns with consistent failure mode across multiple lots rules out customer misuse. But your production inspection shows conforming product. This means either: (1) your inspection is sampling the wrong things, (2) the voiding develops or worsens after initial inspection (during subsequent thermal cycling in reflow for other components, or during customer thermal cycling in use), or (3) the void distribution varies within the BGA footprint and your X-ray angle doesn't capture the worst-case joints.
+
+BGA solder joint voiding is particularly insidious because voids that are acceptable at room temperature can cause failure under thermal cycling — the void acts as a stress concentrator and crack initiation site. The failure mechanism is thermomechanical fatigue accelerated by voiding, which means the defect is present at the time of manufacture but only manifests after enough thermal cycles in the field.
+
+**Common Mistake:**
+Increasing the X-ray inspection frequency or adding 100% X-ray inspection. If your current X-ray protocol can't distinguish the failing population from the good population, doing more of the same inspection won't help — you're looking for the defect in the wrong way.
+
+**Expert Approach:**
+1. **Failure analysis on returned units.** Cross-section the BGA solder joints on failed returns. Map the void location, size, and the crack propagation path. Determine if the cracks initiate at voids (they almost always do in BGA thermomechanical fatigue).
+2. **X-ray protocol review.** Compare the X-ray imaging parameters (angle, magnification, algorithm) between production inspection and failure analysis inspection. Often, the production X-ray uses a top-down view that averages voiding across the entire joint, while the critical voiding is concentrated at the component-side interface where thermal stress is highest.
+3. **Process investigation using DOE.** Solder paste voiding is influenced by: stencil aperture design, paste-to-pad ratio, reflow profile (soak zone temperature and time), pad finish (ENIG vs. OSP vs. HASL), and BGA component pad finish. Run a designed experiment varying the controllable factors against voiding as the response. Use the optimized parameters to reduce the baseline voiding level below the failure threshold.
+4. **Reliability testing.** Subject production samples to accelerated thermal cycling (ATC) testing per IPC-9701 (-40°C to +125°C for SnPb, -40°C to +100°C for SAC305). Monitor for failure at intervals. This replicates the field failure mechanism in a controlled environment and allows you to validate that process improvements actually reduce the failure rate.
+5. **SPC on voiding.** Implement BGA voiding measurement as an SPC characteristic with limits set based on the reliability test data (not just the IPC-7095 generic guideline). The control limits should be set at the voiding level below which reliability testing shows acceptable life.
+
+**Key Indicators:**
+- 0.3% field return rate in electronics is unusually high for a solder defect — this is a systemic process issue, not random
+- Void location within the joint matters more than total void percentage — a 15% void concentrated at the interface is worse than 25% distributed throughout the joint body
+- Correlation between void levels and reflow profile parameters (especially time above liquidus and peak temperature) is typically the strongest process lever
+
+---
+
+### Edge Case 9: Supplier Sole-Source with Quality Problems
+
+**Situation:**
+Your sole-source supplier for a custom titanium forging (Ti-6Al-4V, closed-die forging with proprietary tooling) has been on SCAR for the third time in 12 months. The recurring issue is grain flow non-conformance — the microstructural grain flow does not follow the specified contour, which affects fatigue life. The forgings are for a landing gear component (aerospace, AS9100). The forgings cost $12,000 each, with 6-month lead time for tooling and 4-month lead time for production. You need 80 forgings per year. There is no other qualified supplier, and qualifying a new forging source would take 18-24 months including tooling, first articles, and customer qualification.
+
+**Why It's Tricky:**
+This is the sole-source quality trap. Your supplier quality escalation ladder says you should move to controlled shipping and begin alternate source qualification. But controlled shipping at a sole-source supplier is a paper exercise — you'll inspect the forgings, but if they fail, you have no alternative. And beginning alternate source qualification gives you 18-24 months of continued dependence on a problematic supplier.
+
+The business can't tolerate a supply disruption. Each forging is a $12,000 part with 6+ months of lead time, and you need 80 per year for an active production program. Shutting off the supplier shuts off your production.
+
+**Common Mistake:**
+Treating this like a normal supplier quality issue. Following the escalation ladder to the letter (controlled shipping → alternate source qualification → phase-out) without considering that the escalation ladder was designed for commodity parts with alternatives. For a sole-source strategic supplier, aggressive escalation can backfire — the supplier may deprioritize your business or increase prices.
+
+The opposite mistake: accepting the recurring non-conformance because you have no alternative. "Use-as-is because we're sole-sourced" is not an acceptable disposition for a safety-critical aerospace forging, regardless of supply constraints.
+
+**Expert Approach:**
+1. **Invest in the supplier, don't just punish them.** Propose a joint development program. Your metallurgical engineer works with their forging process engineer to optimize die design, forging temperature, and press force profile for the grain flow requirement. This is supplier development, not just supplier corrective action.
+2. **Root cause the grain flow issue properly.** Grain flow non-conformance in closed-die forging is typically caused by: incorrect billet pre-form shape (material doesn't flow where the die expects it), insufficient forging reduction ratio, incorrect forging temperature (too cold = surface cracking, too hot = grain growth), or die wear allowing material to flow outside the intended path. Which of these is it? Each has a different solution.
+3. **Begin alternate source qualification quietly.** Start the 18-24 month qualification process immediately, but do not use it as a threat. Frame it as "supply chain risk mitigation" — even if the supplier improves, having a second source is sound supply chain management for a safety-critical part.
+4. **Negotiate a quality improvement agreement.** Work with procurement to structure a commercial agreement: the supplier invests in process improvements (die refurbishment, process parameter optimization, enhanced in-process metallographic inspection), and you commit to volume or price stability over the investment payback period.
+5. **Increase your incoming inspection on these forgings.** Regardless of supplier performance, a safety-critical aerospace forging should have metallographic inspection at incoming — don't rely solely on the supplier's certification. The cost of a destructive test sample (one forging per lot) is small relative to the consequence of a grain flow non-conformance reaching the machined part.
+6. **MRB each non-conformance individually.** Just because the supplier is sole-sourced does not mean every non-conformance gets a use-as-is disposition. Each forging must be evaluated on its specific grain flow pattern against the design intent. Some deviations may be acceptable with engineering and customer concession; others are scrapped regardless of supply impact. Document the disposition rationale with metallographic evidence and engineering analysis.
+
+**Key Indicators:**
+- Grain flow pattern should be evaluated against the finished machined geometry, not just the forging geometry — material removal during machining can expose grain flow that was within the forging specification but becomes non-conforming in the machined part
+- A 3-sigma supply buffer (keep 6+ months of safety stock) is essential while working the quality improvement with a sole source
+- Die life tracking correlates with grain flow quality — quality typically degrades as the die wears
+
+---
+
+### Edge Case 10: Non-Conformance Discovered During Regulatory Audit
+
+**Situation:**
+During an FDA inspection of your medical device manufacturing facility, the investigator pulls a traveler for a recently completed production lot of surgical staplers. Reviewing the dimensional inspection data, the investigator notes that two of ten measured dimensions are recorded as "within tolerance" but the actual values are not recorded — only pass/fail. The investigator asks to see the actual measurement values. Your inspector explains that these two dimensions are measured with go/no-go gauges and the pass/fail result is all that's recorded. The investigator issues a Form 483 observation: "There is no procedure to ensure that manufacturing specifications have been met for two critical dimensions on [part number]. Actual measurement data is not recorded."
+
+The investigator's position: go/no-go gauging on a critical dimension of a Class II surgical device is insufficient because it doesn't provide trend data to detect process drift before the process goes out of specification. Your position: go/no-go gauges are an industry-accepted measurement method, the gauges are calibrated, and the control plan specified this method.
+
+**Why It's Tricky:**
+Both positions are defensible. Go/no-go gauging is a valid measurement method recognized by ASME and used across all manufacturing industries. For many applications, it's actually preferred because it eliminates measurement error — the gauge is either go or no-go, there's no subjective reading. However, the FDA investigator has a point: attribute data (pass/fail) from go/no-go gauges does not support trend analysis or SPC, which means you cannot detect a process drifting toward the specification limit until it actually exceeds the limit and the gauge rejects the part.
+
+For a critical dimension on a surgical device, the argument for variable data (actual measurements) that supports trend analysis has real merit. This is the tension between measurement practicality and quality system rigor.
+
+**Common Mistake:**
+Arguing with the investigator that go/no-go gauging is adequate. Even if you're technically right, arguing with an FDA investigator during an inspection almost never helps. The observation is written; your opportunity to respond is in the formal 483 response, not in the moment.
+
+The opposite mistake: immediately committing to variable gauging for every dimension. This may be impractical, expensive, and unnecessary for non-critical dimensions. Over-correcting in response to a 483 creates an unsustainable system.
+
+**Expert Approach:**
+1. **Accept the observation gracefully.** During the inspection: "Thank you. We'll evaluate our measurement methodology for these critical dimensions and respond in our 483 response." Do not argue, do not minimize, do not promise a specific corrective action on the spot.
+2. **483 response (due within 15 business days):** Structure the response in four parts:
+ - **Acknowledgment:** "We acknowledge the observation regarding [specific dimensions, specific part number]."
+ - **Investigation:** "We have reviewed the measurement methodology for critical dimensions on this part number. We concur that while go/no-go gauging provides conformance verification, it does not support the trend analysis needed to proactively detect process drift on critical dimensions."
+ - **Corrective action:** "We will implement variable measurement (calibrated digital calipers/micrometers with data recording) for all critical dimensions on Class II and Class III devices, effective [date]. Measurement data will be charted using SPC (X-bar/R) to enable trend detection. Go/no-go gauging will be retained as a secondary verification method."
+ - **Scope extension:** "We are reviewing all inspection plans for Class II and Class III devices to identify any other critical dimensions using attribute-only gauging and will convert to variable gauging as appropriate."
+3. **Implementation.** Actually implement the change before the FDA follow-up (which may be in 6-12 months). Have SPC charts running and demonstrating trend capability by the time of re-inspection. This is what FDA means by "evidence of effectiveness."
+4. **Don't over-correct.** Convert critical dimensions to variable gauging. Non-critical dimensions where go/no-go is practical and appropriate can remain as attribute gauging. Document the risk-based rationale for which dimensions require variable data and which do not.
+
+**Key Indicators:**
+- The investigator's observation is about system capability, not about a specific defective product
+- A strong 483 response demonstrates that you understand the intent of the observation, not just the letter
+- The FDA evaluates your CAPA system partly by how you respond to observations — a proportionate, well-reasoned response is valued over a panicked over-correction
+- Scope extension (looking beyond the specific finding to the systemic issue) is explicitly what FDA wants to see in a 483 response
+
+**Documentation Required:**
+- Copy of Form 483 observation
+- Formal 483 response with all four sections
+- Updated inspection plans showing conversion from attribute to variable gauging
+- SPC implementation records (chart setup, control limits, operator training)
+- Risk-based rationale document for gauging method selection by characteristic criticality
+- Evidence of scope extension review (list of all inspection plans reviewed, findings, and actions)
+
+---
+
+### Edge Case 11: Customer Rejects Lot That Passed Your Final Inspection
+
+**Situation:**
+Your automotive tier 2 plant ships stamped steel brackets to a tier 1 seat frame assembler. Your final inspection per the control plan checks 12 dimensions per AQL sampling (Level II, AQL 1.0). Lot 2025-0892 passed your inspection with zero rejects in the sample. The tier 1 customer's incoming inspection rejects the lot — their 100% automated vision system flagged 4.2% of pieces for a burr height exceeding 0.3mm on edge B. Your control plan does not include burr height on edge B as an inspection characteristic because the customer print specifies "deburr per shop practice" with no quantitative requirement.
+
+**Why It's Tricky:**
+The customer's rejection appears to add a requirement that isn't on the drawing. "Deburr per shop practice" is a qualitative, subjective call — there's no measurable specification. However, the customer has an automated system that quantifies what "shop practice" means operationally. From the customer's perspective, 4.2% of parts have burrs that interfere with their automated assembly process. From your perspective, you met all dimensioned requirements and the subjective "deburr" note cannot be objectively measured.
+
+This is a specification gap, not a quality failure — but you still have a rejected lot, a customer demanding corrective action, and a control plan that doesn't cover the issue.
+
+**Common Mistake:**
+Refusing the rejection because the requirement isn't quantified on the drawing. This is technically correct and commercially disastrous — the customer doesn't care about specification semantics; their assembly line is down.
+
+**Expert Approach:**
+1. **Accept the return or sort on-site.** Business continuity first. Offer to send a sort team to the customer's facility to 100% inspect and remove the nonconforming parts, or accept the return and sort at your facility. This gets the customer's line running while you address the systemic issue.
+2. **Request the quantitative requirement.** Contact the customer's quality engineering team and ask them to provide a measurable specification for burr height on edge B. "We need a quantified requirement to add this to our control plan and SPC program. Can you issue a drawing change or specification supplement with a maximum burr height?"
+3. **Interim control.** While the drawing change is in process, add burr height inspection to your control plan as a customer-specific requirement with the threshold from their vision system (0.3mm max).
+4. **Process investigation.** Why is burr height variable? Investigate stamping die condition — progressive die wear on the cutting edge increases burr height over the production run. Establish a die maintenance interval based on burr height progression, not just parts count.
+5. **PPAP update.** Once the customer issues a formal specification for burr height, submit a PPAP update (at minimum a control plan revision and MSA for the new characteristic).
+
+**Key Indicators:**
+- Burr height typically increases with die wear — plot burr height vs. parts since last die sharpen to establish the maintenance interval
+- "Deburr per shop practice" without quantification is a common specification deficiency — the corrective action is a drawing change, not a process change
+- The customer's 4.2% reject rate suggests your process is close to the threshold — a small process improvement (die maintenance interval) may reduce the rate below detection
+
+---
+
+### Edge Case 12: Cross-Contamination in Multi-Product Manufacturing
+
+**Situation:**
+Your pharmaceutical contract manufacturer runs tablet compression on Line 3 for both Product A (a controlled substance, Schedule III) and Product B (an over-the-counter supplement). Changeover between products follows your validated cleaning procedure (cleaning validation study CV-2023-011). During a routine post-cleaning swab analysis before starting Product B, the QC lab reports trace levels of Product A's active ingredient at 0.8 ppm — your validated cleaning limit is 1.0 ppm based on MACO (Maximum Allowable Carryover) calculation. The result is within specification, so the line is released for production.
+
+Two weeks later, the FDA requests your cleaning validation data during an inspection. The investigator points out that your MACO calculation used the maximum daily dose of Product B (the "contaminated" product) as 10 grams, but the actual maximum daily dose on the current label is 15 grams (the label was updated 6 months ago, but the MACO calculation was not revised). Recalculating with the correct maximum daily dose, the cleaning limit should be 0.67 ppm — and the 0.8 ppm result now exceeds the corrected limit.
+
+**Why It's Tricky:**
+The cleaning validation was "validated" but the underlying calculation is now incorrect. This means: (1) every batch of Product B produced since the label change may have been exposed to unacceptable levels of Product A (a controlled substance, adding regulatory severity), (2) your cleaning validation program has a gap — it doesn't trigger recalculation when the inputs change, and (3) the FDA investigator has identified a systemic quality system failure, not just an isolated event.
+
+**Common Mistake:**
+Arguing that 0.8 ppm is toxicologically insignificant. The FDA doesn't operate on "it's probably fine" — they operate on validated limits derived from documented calculations. If the calculation is wrong, the limit is wrong, and the validation is invalid.
+
+**Expert Approach:**
+1. **Acknowledge the finding.** Do not debate the arithmetic with the FDA investigator. The calculation error is factual.
+2. **Immediate containment.** Place a hold on all in-process and unreleased Product B lots manufactured since the label change. Review the cleaning verification results for every changeover in that period. For lots where the cleaning result exceeded the corrected 0.67 ppm limit, conduct a risk assessment on the actual patient exposure.
+3. **Toxicological risk assessment.** Engage your toxicologist or a qualified consultant to assess the actual risk. At 0.8 ppm of Product A in Product B with a maximum daily dose of 15g, the maximum daily exposure to Product A is 12 µg. Is this below the ADI (Acceptable Daily Intake) for Product A's active ingredient? If yes, document this as a secondary justification — but it doesn't fix the process gap.
+4. **Recalculate and revalidate.** Update the MACO calculation with the correct inputs. If the new limit (0.67 ppm) requires a different cleaning procedure, validate the new procedure. If the existing cleaning procedure can meet the new limit (review all historical data), document the cleaning verification with the new limit.
+5. **Systemic corrective action.** The root cause is not the arithmetic error — it's the absence of a change control linkage between product labeling changes and cleaning validation inputs. The CAPA must establish a formal review trigger: any change to maximum daily dose, therapeutic dose, or product formulation triggers a review of all affected MACO calculations.
+6. **Batch disposition.** For lots where Product B was produced with cleaning results between 0.67 and 1.0 ppm: if the toxicological assessment shows the exposure is within ADI, the lots may be dispositioned as acceptable with documentation. If exposure exceeds ADI, the lots must be rejected.
+
+**Key Indicators:**
+- The MACO calculation inputs (maximum daily dose, minimum daily dose of contaminating product, safety factor) must be traceable to current product documentation
+- A cleaning validation that hasn't been reviewed after a product change is not validated — it's out of date
+- Controlled substance cross-contamination adds DEA regulatory obligations on top of FDA obligations
+- The systemic fix (change control linkage) is more important than the specific calculation correction
+
+---
+
+### Edge Case 13: Supplier Ships Correct Part but Wrong Material Certification
+
+**Situation:**
+Your aerospace receiving inspection accepts a lot of 200 titanium fasteners (Ti-6Al-4V per AMS 4928) from a qualified supplier. The CoC shows the correct material specification. Your incoming dimensional inspection on a sample of 13 pieces passes. The parts are released into production. During assembly, one of your technicians notices the fasteners seem to machine differently during a modification step — they're cutting "easier" than expected for Ti-6Al-4V. You pull a part and send it for material verification via handheld XRF. The result shows the parts are commercially pure (CP) titanium (Grade 2), not Ti-6Al-4V. The CoC is for the correct material, but the actual parts are wrong.
+
+**Why It's Tricky:**
+CP titanium Grade 2 and Ti-6Al-4V are both titanium, and visually indistinguishable. The CoC was correct for the material the supplier intended to ship, but a lot mix-up at the supplier's warehouse resulted in the wrong material being shipped. Your incoming inspection checked dimensions (which happen to be identical between the two materials) but did not perform material verification testing.
+
+In aerospace, this is a potential counterfeit/suspect part situation per AS9100 §8.1.4, even if it was an innocent mix-up. CP Grade 2 has significantly lower yield and tensile strength than Ti-6Al-4V (345 MPa vs. 880 MPa yield) — a safety-critical difference on a structural fastener.
+
+**Common Mistake:**
+Assuming the parts can be sorted by XRF and the wrong material returned. While that's eventually the disposition, the immediate priority is containment: how many of the 200 fasteners have already been installed in assemblies? Those assemblies may need to be torn down and the fasteners replaced.
+
+**Expert Approach:**
+1. **Immediate quarantine of all remaining fasteners.** Mark as suspect; do not use for any purpose until material verification is complete.
+2. **Containment — trace forward.** How many of the 200 fasteners have been consumed in production? Which assemblies? Are any of those assemblies already shipped to the customer? Each installed CP titanium fastener in a structure designed for Ti-6Al-4V is a potential structural failure in service.
+3. **100% material verification on remaining stock.** XRF every remaining fastener. Separate confirmed Ti-6Al-4V (if any) from confirmed CP Grade 2.
+4. **Engineering assessment on installed fasteners.** For each assembly containing suspect fasteners, engineering must evaluate: (a) the specific loading condition on each fastener location, (b) whether CP Grade 2 meets the structural requirement at that location (it may for lightly loaded positions), and (c) whether the assembly can be reworked (remove and replace the fastener) without damaging the structure.
+5. **Customer notification.** For shipped assemblies, notify the customer immediately with traceability data. The customer must evaluate their own installation context and downstream assemblies.
+6. **Supplier investigation.** This is a material traceability failure at the supplier. Issue a SCAR demanding: (a) root cause of the lot mix-up, (b) containment of other orders that may have been affected by the same mix-up, (c) implementation of positive material identification (PMI) as a pre-shipment verification step. This is a Level 2 or Level 3 escalation depending on whether the supplier has had material-related non-conformances before.
+7. **GIDEP reporting.** If the investigation suggests the material substitution was anything other than an innocent warehouse mix-up, report to GIDEP per AS9100 counterfeit prevention requirements.
+8. **Incoming inspection update.** Add PMI (XRF or OES) to the incoming inspection plan for all structural material lots, regardless of supplier qualification level. CoC reliance without material verification is a known vulnerability for material mix-ups.
+
+**Key Indicators:**
+- The machinability difference noticed by the technician is a real and reliable indicator — CP titanium machines significantly differently from Ti-6Al-4V (lower cutting forces, different chip formation)
+- XRF can distinguish Grade 2 from Ti-6Al-4V quickly by the absence of aluminum and vanadium peaks
+- The safety risk depends entirely on the application — a CP Grade 2 fastener in a lightly loaded panel is probably fine; the same fastener in a primary structure fitting is a safety-of-flight concern
+- Lot traceability from the supplier's heat/melt lot number through their inventory system to your PO is the critical investigation path
+
+---
+
+### Edge Case 14: CAPA System Backlog Creating Systemic Risk
+
+**Situation:**
+Your quality management system currently has 147 open CAPAs. Of these, 62 are past their target closure date, with 23 overdue by more than 6 months. The quality team of 4 engineers is overwhelmed. Management's response has been to hire a temporary contractor to "clear the backlog." Your registrar audit is in 8 weeks, and the auditor will evaluate CAPA system effectiveness. FDA conducted an inspection 18 months ago and noted a 483 observation about CAPA timeliness; you committed to improvement in your response.
+
+**Why It's Tricky:**
+The backlog itself is a symptom, and the proposed solution (hire a contractor to "close" CAPAs) is likely to create a bigger problem than it solves. A contractor who doesn't understand your processes, products, and quality history will either (a) close CAPAs with superficial effectiveness evidence, or (b) take months to ramp up and not clear the backlog in time.
+
+The deeper issue: 147 open CAPAs in a 4-person quality team means the system is initiating too many CAPAs, not that the team is closing too few. If every NCR and every minor audit finding generates a CAPA, the system is undifferentiated — everything is treated the same, so nothing gets adequate attention.
+
+**Common Mistake:**
+Mass-closing CAPAs to reduce the count. Closing CAPAs without verified effectiveness is worse than having them open — it's a systemic falsification of the quality record. An auditor who sees 60 CAPAs closed in the last 2 weeks before an audit will investigate the closure quality, and finding superficial closures is a major finding.
+
+**Expert Approach:**
+1. **Triage the 147 open CAPAs.** Categorize each into one of four buckets:
+ - **Active and valid:** Root cause is systemic, corrective action is in progress or effective. These stay open and get prioritized.
+ - **Should not have been CAPAs:** Isolated non-conformances that were over-escalated to CAPA. These should be downgraded to NCR dispositions with documented rationale for why CAPA was not required. This is not "closing for convenience" — it's applying correct CAPA initiation criteria retroactively.
+ - **Duplicate or overlapping:** Multiple CAPAs addressing the same root cause from different trigger events. Consolidate into a single CAPA with all triggers linked.
+ - **Stale and no longer applicable:** Process or product has changed since the CAPA was initiated, making the original issue moot. Close with documented rationale that the original condition no longer exists.
+2. **Right-size the CAPA pipeline.** After triage, the active CAPA count should drop to 40-60 (manageable for a 4-person team at ~10-15 CAPAs per engineer). Prioritize by risk: safety and regulatory CAPAs first, customer-facing CAPAs second, internal improvement CAPAs third.
+3. **Fix the initiation criteria.** Update the CAPA initiation procedure with clear, documented criteria for what warrants a CAPA vs. what is handled at the NCR level. Train the quality team on the updated criteria. This is the actual corrective action for the backlog — preventing future over-initiation.
+4. **Demonstrate systemic improvement at audit.** Present the triage analysis, the updated initiation criteria, the prioritization methodology, and the current CAPA metrics (average closure time, effectiveness rate for closed CAPAs). An auditor who sees a thoughtful, risk-based approach to CAPA management will view this far more favorably than a frantic mass-closure.
+5. **Address the FDA commitment.** Your 483 response committed to improvement in CAPA timeliness. The triage and process change demonstrate systemic improvement, which is what FDA expects. Simply clearing the backlog without fixing the systemic cause would be repeating the same failure.
+
+**Key Indicators:**
+- CAPA count per engineer is the capacity metric — more than 15 active CAPAs per engineer indicates either over-initiation or under-resourcing
+- The ratio of CAPAs initiated to CAPAs closed per month shows whether the pipeline is growing or shrinking
+- Effectiveness rate (CAPAs closed with verified effectiveness, no recurrence) is more important than closure rate
+- Auditors assess CAPA system maturity, not CAPA count — a mature system has few, well-managed CAPAs
+
+**Documentation Required:**
+- CAPA triage register with categorization and rationale for each CAPA
+- Updated CAPA initiation procedure (before and after revision)
+- Management review presentation showing backlog analysis and improvement plan
+- Metrics dashboard showing CAPA pipeline health (open count, aging, closure rate, effectiveness rate)
+- Training records for quality team on updated initiation criteria
+- Communication to management on the root cause of the backlog (over-initiation, not under-performance)
+
+---
+
+### Edge Case 15: Process Validation Deviation During FDA-Regulated Production
+
+**Situation:**
+Your medical device manufacturing facility completed process validation (IQ/OQ/PQ) for an ultrasonic welding process 18 months ago. The validated parameters include a weld force of 800N ±50N, amplitude of 40µm, and weld time of 0.6 seconds. During routine production monitoring, the quality engineer notices that the weld force has been running at 760N for the last 3 production lots — technically within the validated range (750-850N), but at the very bottom. The process has not been formally changed. Upon investigation, the force transducer was recalibrated 4 weeks ago, and the calibration adjustment shifted the reading by approximately 40N. The actual physical weld force has likely been consistent — it's the measurement that shifted.
+
+But there's a catch: the process validation was performed with the old calibration. If the transducer was reading 40N high during validation, the actual weld force during PQ was 760-810N, not the documented 800-850N. This means the validation data may not represent what was actually validated.
+
+**Why It's Tricky:**
+This is not a simple calibration adjustment — it's a retroactive question about the validity of the process validation itself. If the force transducer was reading high during validation, the documented validated range (750-850N indicated) actually corresponded to 710-810N actual force. The question becomes: was the process validated at the range you thought it was validated at?
+
+For FDA 21 CFR 820.75, process validation must demonstrate that the process produces results consistently meeting predetermined specifications. If the validation data was collected with a biased instrument, the validation conclusion may be unsound.
+
+**Common Mistake:**
+Ignoring the implication because "the process hasn't changed." The process may not have changed, but your understanding of what was validated has changed. This matters for FDA because the validation must be scientifically sound, and a 40N measurement bias on an 800N nominal process (5% bias) is not trivial.
+
+The second mistake: invalidating the process and halting production for a full revalidation. This may be an overreaction if the product quality data (test results, field performance) supports that the process has been producing conforming product throughout.
+
+**Expert Approach:**
+1. **Quantify the calibration shift.** Review the calibration records — what was the as-found reading vs. the as-left reading during the last calibration? If the as-found was 40N high and the as-left is now correct, the shift is documented.
+2. **Retrospective data analysis.** Collect all product quality data (weld pull-test results, leak test results, or whatever the product-level test is that verifies weld integrity) from the entire period between calibrations. If the product quality data shows consistent, conforming results throughout, this is strong evidence that the process, regardless of the measurement bias, was producing acceptable product.
+3. **Impact assessment on validation.** Recalculate the process capability from the PQ study using the corrected force values (subtract the 40N bias from all documented force readings). If the corrected data still demonstrates capability (Cpk ≥ 1.33) within the specification range, the validation conclusion remains sound even with the adjusted values.
+4. **Protocol for validated range.** If the corrected data shifts the validated range, determine whether the current operating point (760N indicated = 760N actual with corrected calibration) falls within the corrected validated range. If yes, no action needed beyond documentation. If no, a bridging validation study may be required to extend the validated range.
+5. **Calibration program improvement.** The root cause is that the calibration program did not evaluate the impact of calibration adjustments on process validation status. The CAPA should establish a change control trigger: any calibration adjustment exceeding a defined threshold (e.g., > 2% of nominal) triggers a review of the impact on process validation.
+6. **Documentation.** File this as a deviation to the process validation protocol. Document the impact assessment, the retrospective data analysis, the conclusion on validation status, and the corrective action. This creates the audit trail that demonstrates you identified, evaluated, and resolved the issue — which is what FDA expects.
+
+**Key Indicators:**
+- The ratio of calibration shift to process tolerance determines severity (40N shift on a ±50N tolerance = 80% of tolerance, which is significant)
+- Product-level test data is the ultimate evidence of process acceptability — it measures the output, not the input
+- Calibration as-found/as-left data should always be evaluated for process validation impact, not just instrument accuracy
+
+**Documentation Required:**
+- Calibration certificate showing as-found and as-left values
+- Retrospective product quality data analysis with statistical summary
+- Impact assessment on process validation (corrected PQ data analysis)
+- Deviation report to process validation protocol
+- Updated calibration program procedure requiring validation impact assessment
+
+---
+
+## Quick Reference: Edge Case Pattern Recognition
+
+The edge cases above share common patterns. When you encounter a quality situation that feels complex, check which pattern(s) apply:
+
+### Pattern A: Specification Gap
+**Signature:** Parts meet the documented specification but fail in application.
+**Edge cases:** 3 (SPC in-control but complaints rising), 6 (audit finding challenging practice), 11 (customer rejects lot that passed inspection)
+**Key question:** Is the specification adequate for the functional requirement?
+**Default action:** Collaborate with the customer/user to quantify the real requirement.
+
+### Pattern B: Measurement System Integrity
+**Signature:** The quality data says everything is fine, but reality disagrees.
+**Edge cases:** 1 (field failure with no internal detection), 4 (shipped product with calibration issue), 8 (intermittent defect can't reproduce), 10 (go/no-go vs. variable gauging), 15 (calibration shift affects validation)
+**Key question:** Is the measurement system capable of detecting the actual failure mode?
+**Default action:** Evaluate measurement system against the failure mode, not just the specification.
+
+### Pattern C: Trust Breakdown
+**Signature:** Data or documentation cannot be relied upon.
+**Edge cases:** 2 (falsified CoCs), 13 (wrong material with correct cert)
+**Key question:** What is the full scope of potentially affected product?
+**Default action:** Independent verification; do not rely on the compromised data source.
+
+### Pattern D: Systemic Process Failure
+**Signature:** The corrective action treats a symptom; the problem recurs.
+**Edge cases:** 5 (CAPA addresses symptom not root cause), 7 (multiple root causes), 14 (CAPA backlog)
+**Key question:** Is the root cause analysis rigorous enough?
+**Default action:** Restart RCA with fresh team and more rigorous methodology.
+
+### Pattern E: Competing Priorities
+**Signature:** Quality requirements conflict with supply or business constraints.
+**Edge cases:** 9 (sole-source with quality problems), 12 (cross-contamination with supply implications)
+**Key question:** What is the minimum acceptable quality action that maintains regulatory compliance?
+**Default action:** Risk-based approach with parallel paths (fix the problem AND develop alternatives).
+
+### Cross-Referencing Edge Cases with Decision Frameworks
+
+| Edge Case | Primary Decision Framework | Secondary Framework |
+|---|---|---|
+| 1. Field failure no internal detection | CAPA initiation criteria | FDA reporting obligations |
+| 2. Falsified CoCs | Supplier escalation ladder (Level 4-5) | NCR disposition (containment scope) |
+| 3. SPC in-control, complaints rising | Cp/Cpk interpretation | Specification adequacy review |
+| 4. NC on shipped product | NCR disposition (containment) | Customer notification protocol |
+| 5. CAPA addresses symptom | RCA method selection (upgrade methodology) | CAPA effectiveness verification |
+| 6. Audit finding challenges practice | Audit response protocol | Risk-based process change |
+| 7. Multiple root causes | RCA method selection (Ishikawa/FTA) | CAPA action hierarchy |
+| 8. Intermittent defect | Measurement system evaluation | SPC chart selection |
+| 9. Sole-source quality problems | Supplier develop vs. switch | MRB economic model |
+| 10. NC during regulatory audit | Regulatory response protocol | CAPA timeliness standards |
+| 11. Customer rejects despite passing | Specification gap analysis | Control plan update |
+| 12. Cross-contamination | Cleaning validation | FDA field action determination |
+| 13. Wrong material, correct cert | Counterfeit prevention (AS9100) | Incoming inspection update |
+| 14. CAPA backlog | CAPA initiation criteria triage | Management review |
+| 15. Validation deviation | Process validation impact assessment | Calibration program improvement |
diff --git a/web-app/public/skills/quant-analyst/SKILL.md b/web-app/public/skills/quant-analyst/SKILL.md
index 9ce77053..c84d4b6f 100644
--- a/web-app/public/skills/quant-analyst/SKILL.md
+++ b/web-app/public/skills/quant-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: quant-analyst
-description: "Build financial models, backtest trading strategies, and analyze"
+description: |
+ Build financial models, backtest trading strategies, and analyze
market data. Implements risk metrics, portfolio optimization, and statistical
arbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or
risk analysis.
diff --git a/web-app/public/skills/reference-builder/SKILL.md b/web-app/public/skills/reference-builder/SKILL.md
index 83611fa8..d66d4b65 100644
--- a/web-app/public/skills/reference-builder/SKILL.md
+++ b/web-app/public/skills/reference-builder/SKILL.md
@@ -1,6 +1,7 @@
---
name: reference-builder
-description: "Creates exhaustive technical references and API documentation."
+description: |
+ Creates exhaustive technical references and API documentation.
Generates comprehensive parameter listings, configuration guides, and
searchable reference materials. Use PROACTIVELY for API docs, configuration
references, or complete technical specifications.
diff --git a/web-app/public/skills/returns-reverse-logistics/SKILL.md b/web-app/public/skills/returns-reverse-logistics/SKILL.md
new file mode 100644
index 00000000..fde9d64d
--- /dev/null
+++ b/web-app/public/skills/returns-reverse-logistics/SKILL.md
@@ -0,0 +1,231 @@
+---
+name: returns-reverse-logistics
+description: >
+ Codified expertise for returns authorisation, receipt and inspection,
+ disposition decisions, refund processing, fraud detection, and warranty
+ claims management. Informed by returns operations managers with 15+ years
+ experience. Includes grading frameworks, disposition economics, fraud
+ pattern recognition, and vendor recovery processes. Use when handling
+ product returns, reverse logistics, refund decisions, return fraud
+ detection, or warranty claims.
+license: Apache-2.0
+version: 1.0.0
+homepage: https://github.com/evos-ai/evos-capabilities
+risk: safe
+source: https://github.com/ai-evos/agent-skills
+metadata:
+ author: evos
+ clawdbot:
+ emoji: "🔄"
+---
+
+## When to Use
+
+Use this skill when managing the product return lifecycle, including authorization, physical inspection, making disposition decisions (e.g., restock vs. liquidator), detecting return fraud, or processing warranty claims.
+
+# Returns & Reverse Logistics
+
+## Role and Context
+
+You are a senior returns operations manager with 15+ years handling the full returns lifecycle across retail, e-commerce, and omnichannel environments. Your responsibilities span return merchandise authorisation (RMA), receiving and inspection, condition grading, disposition routing, refund and credit processing, fraud detection, vendor recovery (RTV), and warranty claims management. Your systems include OMS (order management), WMS (warehouse management), RMS (returns management), CRM, fraud detection platforms, and vendor portals. You balance customer satisfaction against margin protection, processing speed against inspection accuracy, and fraud prevention against false-positive customer friction.
+
+## Core Knowledge
+
+### Returns Policy Logic
+
+Every return starts with policy evaluation. The policy engine must account for overlapping and sometimes conflicting rules:
+
+- **Standard return window:** Typically 30 days from delivery for most general merchandise. Electronics often 15 days. Perishables non-returnable. Furniture/mattresses 30-90 days with specific condition requirements. Extended holiday windows (purchases Nov 1 – Dec 31 returnable through Jan 31) create a surge that peaks mid-January.
+- **Condition requirements:** Most policies require original packaging, all accessories, and no signs of use beyond reasonable inspection. "Reasonable inspection" is where disputes live — a customer who removed laptop screen protector film has technically altered the product but this is normal unboxing behaviour.
+- **Receipt and proof of purchase:** POS transaction lookup by credit card, loyalty number, or phone number has largely replaced paper receipts. Gift receipts entitle the bearer to exchange or store credit at the purchase price, never cash refund. No-receipt returns are capped (typically $50-75 per transaction, 3 per rolling 12 months) and refunded at lowest recent selling price.
+- **Restocking fees:** Applied to opened electronics (15%), special-order items (20-25%), and large/bulky items requiring return shipping coordination. Waived for defective products or fulfilment errors. The decision to waive for customer goodwill requires margin awareness — waiving a $45 restocking fee on a $300 item with 28% margin costs more than it appears.
+- **Cross-channel returns:** Buy-online-return-in-store (BORIS) is expected by customers and operationally complex. Online prices may differ from store prices. The refund should match the original purchase price, not the current store shelf price. Inventory system must accept the unit back into store inventory or flag for return-to-DC.
+- **International returns:** Duty drawback eligibility requires proof of re-export within the statutory window (typically 3-5 years depending on country). Return shipping costs often exceed product value for low-cost items — offer "returnless refund" when shipping exceeds 40% of product value. Customs declarations for returned goods differ from original export documentation.
+- **Exceptions:** Price-match returns (customer found it cheaper), buyer's remorse beyond window with compelling circumstances, defective products outside warranty, and loyalty tier overrides (top-tier customers get extended windows and waived fees) all require judgment frameworks rather than rigid rules.
+
+### Inspection and Grading
+
+Returned products require consistent grading that drives disposition decisions. Speed and accuracy are in tension — a 30-second visual inspection moves volume but misses cosmetic defects; a 5-minute functional test catches everything but creates bottleneck at scale:
+
+- **Grade A (Like New):** Original packaging intact, all accessories present, no signs of use, passes functional test. Restockable as new or "open box" with full margin recovery (85-100% of original retail). Target inspection time: 45-90 seconds.
+- **Grade B (Good):** Minor cosmetic wear, original packaging may be damaged or missing outer sleeve, all accessories present, fully functional. Restockable as "open box" or "renewed" at 60-80% of retail. May need repackaging ($2-5 per unit). Target inspection time: 90-180 seconds.
+- **Grade C (Fair):** Visible wear, scratches, or minor damage. Missing accessories that cost <10% of unit value. Functional but cosmetically impaired. Sells through secondary channels (outlet, marketplace, liquidation) at 30-50% of retail. Refurbishment possible if cost < 20% of recovered value.
+- **Grade D (Salvage/Parts):** Non-functional, heavily damaged, or missing critical components. Salvageable for parts or materials recovery at 5-15% of retail. If parts recovery isn't viable, route to recycling or destruction.
+
+Grading standards vary by category. Consumer electronics require functional testing (power on, screen check, connectivity) adding 2-4 minutes per unit. Apparel inspection focuses on stains, odour, stretched fabric, and missing tags — experienced inspectors use the "arm's length sniff test" and UV light for stain detection. Cosmetics and personal care items are almost never restockable once opened due to health regulations.
+
+### Disposition Decision Trees
+
+Disposition is where returns either recover value or destroy margin. The routing decision is economics-driven:
+
+- **Restock as new:** Only Grade A with complete packaging. Product must pass any required functional/safety testing. Relabelling or resealing may trigger regulatory issues (FTC "used as new" enforcement). Best for high-margin items where the restocking cost ($3-8 per unit) is trivial relative to recovered value.
+- **Repackage and sell as "open box":** Grade A with damaged packaging or Grade B items. Repackaging cost ($5-15 depending on complexity) must be justified by the margin difference between open-box and next-lower channel. Electronics and small appliances are the sweet spot.
+- **Refurbish:** Economically viable when refurbishment cost < 40% of the refurbished selling price, and a refurbished sales channel exists (certified refurbished program, manufacturer's outlet). Common for premium electronics, power tools, and small appliances. Requires dedicated refurb station, spare parts inventory, and re-testing capacity.
+- **Liquidate:** Grade C and some Grade B items where repackaging/refurb isn't justified. Liquidation channels include pallet auctions (B-Stock, DirectLiquidation, Bulq), wholesale liquidators (per-pound pricing for apparel, per-unit for electronics), and regional liquidators. Recovery rates: 5-20% of retail. Critical insight: mixing categories in a pallet destroys value — electronics/apparel/home goods pallets sell at the lowest-category rate.
+- **Donate:** Tax-deductible at fair market value (FMV). More valuable than liquidation when FMV > liquidation recovery AND the company has sufficient tax liability to utilise the deduction. Brand protection: restrict donations of branded products that could end up in discount channels undermining brand positioning.
+- **Destroy:** Required for recalled products, counterfeit items found in the return stream, products with regulatory disposal requirements (batteries, electronics with WEEE compliance, hazmat), and branded goods where any secondary market presence is unacceptable. Certificate of destruction required for compliance and tax documentation.
+
+### Fraud Detection
+
+Return fraud costs US retailers $24B+ annually. The challenge is detection without creating friction for legitimate customers:
+
+- **Wardrobing (wear and return):** Customer buys apparel or accessories, wears them for an event, returns them. Indicators: returns clustered around holidays/events, deodorant residue, makeup on collars, creased/stretched fabric inconsistent with "tried on." Countermeasure: black-light inspection for cosmetic traces, RFID security tags that customers aren't instructed to remove (if the tag is missing, the item was worn).
+- **Receipt fraud:** Using found, stolen, or fabricated receipts to return shoplifted merchandise for cash. Declining as digital receipt lookup replaces paper, but still occurs. Countermeasure: require ID for all cash refunds, match return to original payment method, limit no-receipt returns per ID.
+- **Swap fraud (return switching):** Returning a counterfeit, cheaper, or broken item in the packaging of a purchased item. Common in electronics (returning a used phone in a new phone box) and cosmetics (refilling a container with a cheaper product). Countermeasure: serial number verification at return, weight check against expected product weight, detailed inspection of high-value items before processing refund.
+- **Serial returners:** Customers with return rates > 30% of purchases or > $5,000 in annual returns. Not all are fraudulent — some are genuinely indecisive or bracket-shopping (buying multiple sizes to try). Segment by: return reason consistency, product condition at return, net lifetime value after returns. A customer with $50K in purchases and $18K in returns (36% rate) but $32K net revenue is worth more than a customer with $15K in purchases and zero returns.
+- **Bracketing:** Intentionally ordering multiple sizes/colours with the plan to return most. Legitimate shopping behaviour that becomes costly at scale. Address through fit technology (size recommendation tools, AR try-on), generous exchange policies (free exchange, restocking fee on return), and education rather than punishment.
+- **Price arbitrage:** Purchasing during promotions/discounts, then returning at a different location or time for full-price credit. Policy must tie refund to actual purchase price regardless of current selling price. Cross-channel returns are the primary vector.
+- **Organised retail crime (ORC):** Coordinated theft-and-return operations across multiple stores/identities. Indicators: high-value returns from multiple IDs at the same address, returns of commonly shoplifted categories (electronics, cosmetics, health), geographic clustering. Report to LP (loss prevention) team — this is beyond standard returns operations.
+
+### Vendor Recovery
+
+Not all returns are the customer's fault. Defective products, fulfilment errors, and quality issues have a cost recovery path back to the vendor:
+
+- **Return-to-vendor (RTV):** Defective products returned within the vendor's warranty or defect claim window. Process: accumulate defective units (minimum RTV shipment thresholds vary by vendor, typically $200-500), obtain RTV authorisation number, ship to vendor's designated return facility, track credit issuance. Common failure: letting RTV-eligible product sit in the returns warehouse past the vendor's claim window (often 90 days from receipt).
+- **Defect claims:** When defect rate exceeds the vendor agreement threshold (typically 2-5%), file a formal defect claim for the excess. Requires defect documentation (photos, inspection notes, customer complaint data aggregated by SKU). Vendors will challenge — your data quality determines your recovery.
+- **Vendor chargebacks:** For vendor-caused issues (wrong item shipped from vendor DC, mislabelled products, packaging failures) charge back the full cost including return shipping and processing labour. Requires a vendor compliance program with published standards and penalty schedules.
+- **Credit vs replacement vs write-off:** If the vendor is solvent and responsive, pursue credit. If the vendor is overseas with difficult collections, negotiate replacement product. If the claim is small (< $200) and the vendor is a critical supplier, consider writing it off and noting it in the next contract negotiation.
+
+### Warranty Management
+
+Warranty claims are distinct from returns and follow a different workflow:
+
+- **Warranty vs return:** A return is a customer exercising their right to reverse a purchase (typically within 30 days, any reason). A warranty claim is a customer reporting a product defect within the warranty coverage period (90 days to lifetime). Different systems, different policies, different financial treatment.
+- **Manufacturer vs retailer obligation:** The retailer is typically responsible for the return window. The manufacturer is responsible for the warranty period. Grey area: the "lemon" product that keeps failing within warranty — the customer wants a refund, the manufacturer offers repair, and the retailer is caught in the middle.
+- **Extended warranties/protection plans:** Sold at point of sale with 30-60% margins. Claims against extended warranties are handled by the warranty provider (often a third party). Retailer's role is facilitating the claim, not processing it. Common complaint: customers don't distinguish between retailer return policy, manufacturer warranty, and extended warranty coverage.
+
+## Decision Frameworks
+
+### Disposition Routing by Category and Condition
+
+| Category | Grade A | Grade B | Grade C | Grade D |
+| -------------------- | -------------------- | ---------------------- | ----------------------------------- | ---------------------------- |
+| Consumer Electronics | Restock (test first) | Open box / Renewed | Refurb if ROI > 40%, else liquidate | Parts harvest or e-waste |
+| Apparel | Restock if tags on | Repackage / outlet | Liquidate by weight | Textile recycling |
+| Home & Furniture | Restock | Open box with discount | Liquidate (local, avoid shipping) | Donate or destroy |
+| Health & Beauty | Restock if sealed | Destroy (regulation) | Destroy | Destroy |
+| Books & Media | Restock | Restock (discount) | Liquidate | Recycle |
+| Sporting Goods | Restock | Open box | Refurb if cost < 25% value | Parts or donate |
+| Toys & Games | Restock if sealed | Open box | Liquidate | Donate (if safety-compliant) |
+
+### Fraud Scoring Model
+
+Score each return 0-100. Flag for review at 65+, hold refund at 80+:
+
+| Signal | Points | Notes |
+| ---------------------------------------------------- | ------ | ---------------------------------------- |
+| Return rate > 30% (rolling 12 mo) | +15 | Adjusted for category norms |
+| Item returned within 48 hours of delivery | +5 | Could be legitimate bracket shopping |
+| High-value electronics, serial number mismatch | +40 | Near-certain swap fraud |
+| Return reason changed between initiation and receipt | +10 | Inconsistency flag |
+| Multiple returns same week | +10 | Cumulative with rate signal |
+| Return from address different than shipping address | +10 | Gift returns excluded |
+| Product weight differs > 5% from expected | +25 | Swap or missing components |
+| Customer account < 30 days old | +10 | New account risk |
+| No-receipt return | +15 | Higher risk of receipt fraud |
+| Item in category with high shrink rate | +5 | Electronics, cosmetics, designer apparel |
+
+### Vendor Recovery ROI
+
+Pursue vendor recovery when: `(Expected credit × probability of collection) > (Labour cost + shipping cost + relationship cost)`. Rules of thumb:
+
+- Claims > $500: Always pursue. The math works even at 50% collection probability.
+- Claims $200-500: Pursue if the vendor has a functional RTV programme and you can batch shipments.
+- Claims < $200: Batch until threshold is met, or offset against next PO. Do not ship individual units.
+- Overseas vendors: Increase minimum threshold to $1,000. Add 30% to expected processing time.
+
+### Return Policy Exception Logic
+
+When a return falls outside standard policy, evaluate in this order:
+
+1. **Is the product defective?** If yes, accept regardless of window or condition. Defective products are the company's problem, not the customer's.
+2. **Is this a high-value customer?** (Top 10% by LTV) If yes, accept with standard refund. The retention math almost always favours the exception.
+3. **Is the request reasonable to a neutral observer?** A customer returning a winter coat in March that they bought in November (4 months, outside 30-day window) is understandable. A customer returning a swimsuit in December that they bought in June is less so.
+4. **What is the disposition outcome?** If the product is restockable (Grade A), the cost of the exception is minimal — grant it. If it's Grade C or worse, the exception costs real margin.
+5. **Does granting create a precedent risk?** One-time exceptions for documented circumstances rarely create precedent. Publicised exceptions (social media complaints) always do.
+
+## Key Edge Cases
+
+These are situations where standard workflows fail. Brief summaries — see [edge-cases.md](references/edge-cases.md) for full analysis.
+
+1. **High-value electronics with firmware wiped:** Customer returns a laptop claiming defect, but the unit has been factory-reset and shows 6 months of battery cycle count. The device was used extensively and is now being returned as "defective" — grading must look beyond the clean software state.
+
+2. **Hazmat return with improper packaging:** Customer returns a product containing lithium batteries or chemicals without the required DOT packaging. Accepting creates regulatory liability; refusing creates a customer service problem. The product cannot go back through standard parcel return shipping.
+
+3. **Cross-border return with duty implications:** An international customer returns a product that was exported with duty paid. The duty drawback claim requires specific documentation that the customer doesn't have. The return shipping cost may exceed the product value.
+
+4. **Influencer bulk return post-content-creation:** A social media influencer purchases 20+ items, creates content, returns all but one. Technically within policy, but the brand value was extracted. Restocking challenges compound because unboxing videos show the exact items.
+
+5. **Warranty claim on product modified by customer:** Customer replaced a component in a product (e.g., upgraded RAM in a laptop), then claims a warranty defect in an unrelated component (e.g., screen failure). The modification may or may not void the warranty for the claimed defect.
+
+6. **Serial returner who is also a high-value customer:** Customer with $80K annual spend and a 42% return rate. Banning them from returns loses a profitable customer; accepting the behaviour encourages continuation. Requires nuanced segmentation beyond simple return rate.
+
+7. **Return of a recalled product:** Customer returns a product that is subject to an active safety recall. The standard return process is wrong — recalled products follow the recall programme, not the returns programme. Mixing them creates liability and reporting errors.
+
+8. **Gift receipt return where current price exceeds purchase price:** The gift recipient brings a gift receipt. The item is now selling for $30 more than the gift-giver paid. Policy says refund at purchase price, but the customer sees the shelf price and expects that amount.
+
+## Communication Patterns
+
+### Tone Calibration
+
+- **Standard refund confirmation:** Warm, efficient. Lead with the resolution amount and timeline, not the process.
+- **Denial of return:** Empathetic but clear. Explain the specific policy, offer alternatives (exchange, store credit, warranty claim), provide escalation path. Never leave the customer with no options.
+- **Fraud investigation hold:** Neutral, factual. "We need additional time to process your return" — never say "fraud" or "investigation" to the customer. Provide a timeline. Internal communications are where you document the fraud indicators.
+- **Restocking fee explanation:** Transparent. Explain what the fee covers (inspection, repackaging, value loss) and confirm the net refund amount before processing so there are no surprises.
+- **Vendor RTV claim:** Professional, evidence-based. Include defect data, photos, return volumes by SKU, and reference the vendor agreement section that covers defect claims.
+
+### Key Templates
+
+Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+
+**RMA approval:** Subject: `Return Approved — Order #{order_id}`. Provide: RMA number, return shipping instructions, expected refund timeline, condition requirements.
+
+**Refund confirmation:** Lead with the number: "Your refund of ${amount} has been processed to your [payment method]. Please allow [X] business days."
+
+**Fraud hold notice:** "Your return is being reviewed by our processing team. We expect to have an update within [X] business days. We appreciate your patience."
+
+## Escalation Protocols
+
+### Automatic Escalation Triggers
+
+| Trigger | Action | Timeline |
+| ------------------------------------------------------------------ | ---------------------------------------------------------------- | ----------------- |
+| Return value > $5,000 (single item) | Supervisor approval required before refund | Before processing |
+| Fraud score ≥ 80 | Hold refund, route to fraud review team | Immediately |
+| Customer has filed chargeback simultaneously | Halt return processing, coordinate with payments team | Within 1 hour |
+| Product identified as recalled | Route to recall coordinator, do not process as standard return | Immediately |
+| Vendor defect rate exceeds 5% for SKU | Notify merchandise and vendor management | Within 24 hours |
+| Third policy exception request from same customer in 12 months | Manager review before granting | Before processing |
+| Suspected counterfeit in return stream | Pull from processing, photograph, notify LP and brand protection | Immediately |
+| Return involves regulated product (pharma, hazmat, medical device) | Route to compliance team | Immediately |
+
+### Escalation Chain
+
+Level 1 (Returns Associate) → Level 2 (Team Lead, 2 hours) → Level 3 (Returns Manager, 8 hours) → Level 4 (Director of Operations, 24 hours) → Level 5 (VP, 48+ hours or any single-item return > $25K)
+
+## Performance Indicators
+
+| Metric | Target | Red Flag |
+| ----------------------------------------------------- | ---------- | ---------- |
+| Return processing time (receipt to refund) | < 48 hours | > 96 hours |
+| Inspection accuracy (grade agreement on audit) | > 95% | < 88% |
+| Restock rate (% of returns restocked as new/open box) | > 45% | < 30% |
+| Fraud detection rate (confirmed fraud caught) | > 80% | < 60% |
+| False positive rate (legitimate returns flagged) | < 3% | > 8% |
+| Vendor recovery rate ($ recovered / $ eligible) | > 70% | < 45% |
+| Customer satisfaction (post-return CSAT) | > 4.2/5.0 | < 3.5/5.0 |
+| Cost per return processed | < $8.00 | > $15.00 |
+
+## Additional Resources
+
+- For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md)
+- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
+
+## When to Use
+
+Use this skill when you need to **design, improve, or troubleshoot returns and reverse logistics operations**:
+
+- Defining or revising returns policies, grading standards, and disposition routes across channels.
+- Investigating high return rates, fraud patterns, or margin leakage in refunds and write‑offs.
+- Building SOPs, scorecards, or automation flows for RMAs, inspections, RTV, and warranty workflows in retail or e‑commerce environments.
diff --git a/web-app/public/skills/returns-reverse-logistics/references/communication-templates.md b/web-app/public/skills/returns-reverse-logistics/references/communication-templates.md
new file mode 100644
index 00000000..d769c3bf
--- /dev/null
+++ b/web-app/public/skills/returns-reverse-logistics/references/communication-templates.md
@@ -0,0 +1,532 @@
+# Communication Templates — Returns & Reverse Logistics
+
+> **Reference Type:** Tier 3 — Load on demand when composing or reviewing returns-related communications.
+>
+> **Usage:** Each template includes variable placeholders in `{{double_braces}}` for direct substitution. Templates are organized by audience and stage. Select the template matching your scenario, substitute variables, review tone guidance, and send.
+
+---
+
+## Table of Contents
+
+1. [RMA Approval Notification](#1-rma-approval-notification)
+2. [RMA Denial Notification](#2-rma-denial-notification)
+3. [Fraud Investigation Hold Notice](#3-fraud-investigation-hold-notice)
+4. [Vendor RTV Claim Submission](#4-vendor-rtv-claim-submission)
+5. [Customer Refund Confirmation](#5-customer-refund-confirmation)
+6. [Restocking Fee Explanation](#6-restocking-fee-explanation)
+7. [Warranty Claim Filing to Manufacturer](#7-warranty-claim-filing-to-manufacturer)
+8. [Disposition Report (Internal)](#8-disposition-report-internal)
+9. [Return Policy Exception Approval](#9-return-policy-exception-approval)
+
+---
+
+## Variable Reference
+
+Common variables used across templates:
+
+| Variable | Description | Example |
+|---|---|---|
+| `{{customer_name}}` | Customer's full name | `Sarah Chen` |
+| `{{customer_email}}` | Customer's email | `schen@email.com` |
+| `{{order_number}}` | Original order number | `ORD-2025-88431` |
+| `{{rma_number}}` | Return merchandise authorisation number | `RMA-2025-04872` |
+| `{{product_name}}` | Product name/description | `Sony WH-1000XM5 Wireless Headphones` |
+| `{{product_sku}}` | Product SKU | `SNY-WH1000XM5-BLK` |
+| `{{serial_number}}` | Product serial number | `SN-8834201` |
+| `{{purchase_date}}` | Original purchase date | `2025-09-14` |
+| `{{purchase_price}}` | Original purchase price | `$349.99` |
+| `{{refund_amount}}` | Refund amount to be issued | `$349.99` |
+| `{{restocking_fee}}` | Restocking fee amount | `$52.50` |
+| `{{payment_method}}` | Original payment method (masked) | `Visa ending in 4821` |
+| `{{return_reason}}` | Customer-stated return reason | `Product not as described` |
+| `{{return_window_end}}` | Last day for standard return | `2025-10-14` |
+| `{{rma_expiry}}` | RMA label/authorisation expiry date | `2025-10-28` |
+| `{{our_company}}` | Our company name | `Apex Commerce Inc.` |
+| `{{our_contact_name}}` | Returns team contact name | `Maria Gonzalez` |
+| `{{our_contact_title}}` | Contact's title | `Returns Operations Supervisor` |
+| `{{our_contact_email}}` | Contact email | `returns@apexcommerce.com` |
+| `{{our_contact_phone}}` | Contact phone | `(800) 555-0199` |
+| `{{vendor_name}}` | Vendor / manufacturer name | `Bose Corporation` |
+| `{{vendor_contact}}` | Vendor returns contact | `James Park, RTV Coordinator` |
+| `{{vendor_account}}` | Vendor account number | `APEX-VND-00342` |
+| `{{defect_description}}` | Description of the defect | `Left ear cup intermittent audio dropout` |
+| `{{inspection_grade}}` | Assigned condition grade | `Grade B` |
+| `{{disposition_route}}` | Disposition decision | `Open box resale` |
+| `{{business_days}}` | Processing time in business days | `5-7` |
+| `{{carrier_name}}` | Return shipping carrier | `UPS Ground` |
+| `{{tracking_number}}` | Return shipment tracking | `1Z999AA10123456784` |
+| `{{warranty_end_date}}` | Warranty expiration date | `2027-09-14` |
+| `{{claim_number}}` | Warranty or vendor claim reference | `WC-2025-11294` |
+
+---
+
+## 1. RMA Approval Notification
+
+### When to Use
+- Customer has initiated a return request and it has been approved under standard policy or an authorised exception.
+- Send immediately upon RMA approval to minimise the time the customer holds the product.
+
+### Tone Guidance
+Warm and efficient. The customer made a decision to return — make it easy. Lead with the actionable information (RMA number, shipping instructions), not the policy.
+
+### What NOT to Say
+- Do not ask "are you sure?" or attempt to dissuade the return at this stage.
+- Do not include language that implies the customer did something wrong.
+- Do not bury the shipping instructions below marketing content.
+
+### Template
+
+**Subject:** Your Return Has Been Approved — RMA# {{rma_number}}
+
+---
+
+Hi {{customer_name}},
+
+Your return for **{{product_name}}** (Order {{order_number}}) has been approved.
+
+**Your RMA Number:** {{rma_number}}
+
+**How to Return Your Item:**
+
+1. Pack the product in its original packaging with all accessories included.
+2. Print the prepaid return label attached to this email.
+3. Attach the label to the outside of the package.
+4. Drop off the package at any {{carrier_name}} location.
+
+**Important Details:**
+- Please ship your return by **{{rma_expiry}}** — the RMA expires after this date.
+- Once we receive and inspect your return, your refund of **{{refund_amount}}** will be processed to your {{payment_method}} within {{business_days}} business days.
+
+If you have any questions, reply to this email or call us at {{our_contact_phone}}.
+
+Best regards,
+{{our_company}} Returns Team
+
+---
+
+## 2. RMA Denial Notification
+
+### When to Use
+- The return request does not meet policy requirements (outside window, excluded category, condition not met).
+- Always provide specific reasons and alternative options.
+
+### Tone Guidance
+Empathetic but clear. The customer will be disappointed. Acknowledge their situation, explain the specific reason (not generic "per our policy"), and always offer at least one alternative path forward.
+
+### What NOT to Say
+- Do not use "unfortunately" more than once.
+- Do not cite policy section numbers or legalistic language.
+- Do not close the door completely — always provide an alternative or escalation path.
+- Never say "there's nothing we can do."
+
+### Template
+
+**Subject:** Regarding Your Return Request — Order {{order_number}}
+
+---
+
+Hi {{customer_name}},
+
+Thank you for contacting us about returning your **{{product_name}}** (Order {{order_number}}, purchased {{purchase_date}}).
+
+After reviewing your request, we're unable to process a standard return because **{{denial_reason}}**.
+
+**We understand this is frustrating, and we want to help. Here are your options:**
+
+{{#if warranty_eligible}}
+- **Warranty claim:** Your product is still covered under the manufacturer's warranty through {{warranty_end_date}}. We can help you file a warranty claim for repair or replacement. Just reply to this email and we'll get that started.
+{{/if}}
+
+{{#if exchange_eligible}}
+- **Exchange:** While we can't offer a refund, we can arrange an exchange for the same product or a similar item. A {{restocking_fee_pct}}% restocking fee would apply.
+{{/if}}
+
+- **Store credit:** We may be able to offer store credit on a case-by-case basis. If you'd like us to review this option, please reply with any additional details about your situation.
+
+- **Speak with a supervisor:** If you feel your situation warrants an exception, we're happy to have a supervisor review your case. Call us at {{our_contact_phone}} and ask for a returns supervisor.
+
+We value your business and want to find a solution that works for you.
+
+Sincerely,
+{{our_contact_name}}
+{{our_company}} Returns Team
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 3. Fraud Investigation Hold Notice
+
+### When to Use
+- A return has been flagged by the fraud scoring system (score ≥ 65) and requires review before the refund is processed.
+- The customer must be informed of the delay without revealing the fraud investigation.
+
+### Tone Guidance
+Neutral and professional. This is a "processing delay" notification. NEVER use the words "fraud," "suspicious," "investigation," or "flagged." The customer may be entirely legitimate — the hold is precautionary.
+
+### What NOT to Say
+- Never say "your return has been flagged."
+- Never reference fraud, theft, or abuse.
+- Never imply the customer has done something wrong.
+- Do not give an indefinite timeline — always commit to a specific review window.
+
+### Template
+
+**Subject:** Your Return is Being Processed — Order {{order_number}}
+
+---
+
+Hi {{customer_name}},
+
+Thank you for your return of **{{product_name}}** (RMA# {{rma_number}}).
+
+We've received your returned item and it is currently undergoing our quality review process. This review ensures we accurately assess the product's condition and process your refund correctly.
+
+**We expect to complete this review within {{review_days}} business days.**
+
+You don't need to do anything at this time. We'll send you a confirmation email once your refund has been processed.
+
+If you have questions in the meantime, you can reach us at {{our_contact_phone}} or reply to this email.
+
+Thank you for your patience,
+{{our_company}} Returns Team
+
+---
+
+### Internal Companion Note (Not Sent to Customer)
+
+**Fraud Review — RMA# {{rma_number}}**
+
+| Field | Detail |
+|---|---|
+| Customer | {{customer_name}} ({{customer_email}}) |
+| Fraud Score | {{fraud_score}} |
+| Primary Signals | {{fraud_signals}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Return Value | {{purchase_price}} |
+| Customer LTV | {{customer_ltv}} |
+| Action Required | {{review_action}} |
+| Review Deadline | {{review_deadline}} |
+| Assigned To | {{reviewer_name}} |
+
+**Review Instructions:** Complete inspection with photo documentation. Verify serial number against order record. Check product weight against expected weight. Compare physical product against product listing. Document findings in the fraud case management system. Recommend: process refund / partial refund / deny with escalation.
+
+---
+
+## 4. Vendor RTV Claim Submission
+
+### When to Use
+- Submitting a return-to-vendor claim for defective products, vendor-caused quality issues, or vendor compliance violations.
+- Attach all supporting documentation (photos, inspection reports, customer complaint data).
+
+### Tone Guidance
+Professional and evidence-based. Vendors respond to data, not complaints. Lead with the facts: SKU, quantity, defect description, return rate data. Reference the vendor agreement section that covers defect claims.
+
+### Template
+
+**Subject:** RTV Claim — {{vendor_account}} — {{claim_number}}
+
+---
+
+{{vendor_contact}},
+
+Please find below our return-to-vendor claim for defective merchandise received under account {{vendor_account}}.
+
+**Claim Reference:** {{claim_number}}
+**Date Submitted:** {{claim_date}}
+**RTV Authorisation #:** {{rtv_auth_number}} (if applicable)
+
+**Claim Details:**
+
+| SKU | Product Name | Qty Defective | Defect Description | Unit Cost | Extended |
+|---|---|---|---|---|---|
+| {{sku_1}} | {{product_1}} | {{qty_1}} | {{defect_1}} | {{cost_1}} | {{ext_1}} |
+| {{sku_2}} | {{product_2}} | {{qty_2}} | {{defect_2}} | {{cost_2}} | {{ext_2}} |
+
+**Total Claim Amount:** {{total_claim_amount}}
+
+**Supporting Documentation (attached):**
+- Defect photographs ({{photo_count}} images)
+- Inspection reports for each SKU
+- Customer return data by SKU (return rate, complaint summary)
+- Original purchase order(s): {{po_numbers}}
+
+**Defect Rate Analysis:**
+- SKU {{sku_1}}: {{defect_rate_1}}% return rate ({{period}}), versus category baseline of {{baseline_rate}}%
+- Excess returns above baseline: {{excess_units}} units
+
+Per Section {{agreement_section}} of our Vendor Agreement dated {{agreement_date}}, defective merchandise exceeding the {{defect_threshold}}% defect rate threshold is eligible for full credit including inbound freight and return processing costs.
+
+**Requested Resolution:** Full merchandise credit of {{total_claim_amount}} plus return processing costs of {{processing_costs}} and inbound freight of {{freight_costs}}, for a total claim of {{grand_total}}.
+
+Please confirm receipt and provide expected credit timeline. Per our agreement, vendor credits are due within {{credit_days}} days of claim submission.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 5. Customer Refund Confirmation
+
+### When to Use
+- Refund has been processed. This is the final communication for a standard return.
+- Send immediately when the refund is initiated (not when it clears the customer's bank).
+
+### Tone Guidance
+Warm and concise. Lead with the refund amount and timeline. The customer wants to know: how much and when.
+
+### Template
+
+**Subject:** Your Refund Has Been Processed — {{refund_amount}}
+
+---
+
+Hi {{customer_name}},
+
+Your refund for **{{product_name}}** (Order {{order_number}}) has been processed.
+
+**Refund Details:**
+- **Amount:** {{refund_amount}}
+- **Refunded to:** {{payment_method}}
+- **Expected arrival:** {{refund_timeline}}
+
+{{#if restocking_fee_applied}}
+A restocking fee of {{restocking_fee}} was applied per our return policy for opened {{product_category}} items. Your original purchase price was {{purchase_price}}.
+{{/if}}
+
+{{#if store_credit}}
+Your store credit of {{store_credit_amount}} has been added to your account and is available immediately.
+{{/if}}
+
+Thank you for shopping with us. If there's anything else we can help with, we're here.
+
+Best,
+{{our_company}} Customer Care
+
+---
+
+## 6. Restocking Fee Explanation
+
+### When to Use
+- When a restocking fee is applied and the customer questions it (either proactively at the time of return or in response to a complaint).
+
+### Tone Guidance
+Transparent and factual. Explain what the fee covers. Do not be apologetic about the policy, but do be clear about the specific dollar amounts.
+
+### Template
+
+**Subject:** Re: Your Return — Restocking Fee Details
+
+---
+
+Hi {{customer_name}},
+
+I understand you have a question about the restocking fee on your return of **{{product_name}}**.
+
+Here's a breakdown:
+
+| Item | Amount |
+|---|---|
+| Original purchase price | {{purchase_price}} |
+| Restocking fee ({{restocking_fee_pct}}%) | -{{restocking_fee}} |
+| **Your refund** | **{{refund_amount}}** |
+
+**Why a restocking fee is applied:**
+
+Our return policy includes a {{restocking_fee_pct}}% restocking fee for opened {{product_category}} products. This fee covers the cost of inspecting, testing, and repackaging the product so it can be offered to the next customer at a reduced "open box" price. Once an item has been opened and used, it can no longer be sold as new, and the restocking fee helps offset this value difference.
+
+**Please note:** Restocking fees are waived for defective products and fulfilment errors. If you believe your product was defective, please let us know and we'll review — if a defect is confirmed, we'll refund the restocking fee.
+
+If you'd like to discuss further, please call us at {{our_contact_phone}} or reply to this email.
+
+Regards,
+{{our_contact_name}}
+{{our_company}} Returns Team
+
+---
+
+## 7. Warranty Claim Filing to Manufacturer
+
+### When to Use
+- Filing a warranty claim with the manufacturer on behalf of the customer or for retailer-held defective inventory.
+
+### Tone Guidance
+Formal and thorough. Manufacturers process warranty claims based on documentation quality. Include everything upfront to avoid back-and-forth.
+
+### Template
+
+**Subject:** Warranty Claim — {{claim_number}} — {{product_name}}
+
+---
+
+To: {{manufacturer_warranty_dept}}
+
+**Warranty Claim Submission**
+
+| Field | Detail |
+|---|---|
+| Claim Reference | {{claim_number}} |
+| Retailer Account | {{retailer_account_number}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Serial Number | {{serial_number}} |
+| Purchase Date | {{purchase_date}} |
+| Warranty Expiration | {{warranty_end_date}} |
+| Defect Description | {{defect_description}} |
+| Date Defect Reported | {{defect_report_date}} |
+
+**Customer Information:**
+- Name: {{customer_name}}
+- Original Order: {{order_number}}
+- Customer has been provided interim resolution: {{interim_resolution}}
+
+**Defect Documentation:**
+- Photographs of defect: attached ({{photo_count}} images)
+- Functional test results: {{test_results}}
+- Customer description of defect: "{{customer_defect_statement}}"
+
+**Product Condition:**
+- Physical condition: {{physical_condition}}
+- Modifications: {{modifications_noted}}
+- Accessories present: {{accessories_status}}
+
+**Requested Resolution:** {{requested_resolution}} (repair / replacement / credit)
+
+Please confirm receipt and provide claim processing timeline. The customer is awaiting resolution.
+
+Regards,
+{{our_contact_name}}
+{{our_contact_title}}
+{{our_company}}
+{{our_contact_email}} | {{our_contact_phone}}
+
+---
+
+## 8. Disposition Report (Internal)
+
+### When to Use
+- Weekly or monthly summary of returns disposition outcomes for management review.
+- Used to track recovery rates, identify disposition efficiency opportunities, and monitor fraud trends.
+
+### Tone Guidance
+Data-first, concise. Management reads these for trends and exceptions, not prose.
+
+### Template
+
+**Subject:** Returns Disposition Report — {{report_period}}
+
+---
+
+## Summary
+
+| Metric | This Period | Prior Period | Trend |
+|---|---|---|---|
+| Total returns received | {{total_returns}} | {{prior_total}} | {{trend_total}} |
+| Total return value | {{total_value}} | {{prior_value}} | {{trend_value}} |
+| Average return value | {{avg_value}} | {{prior_avg}} | {{trend_avg}} |
+| Restock rate (Grade A) | {{restock_pct}}% | {{prior_restock}}% | {{trend_restock}} |
+| Open box / renewed rate (Grade B) | {{open_box_pct}}% | {{prior_open_box}}% | {{trend_ob}} |
+| Liquidation rate (Grade C) | {{liquidation_pct}}% | {{prior_liq}}% | {{trend_liq}} |
+| Destroy / recycle rate (Grade D) | {{destroy_pct}}% | {{prior_destroy}}% | {{trend_destroy}} |
+| Net recovery rate | {{recovery_pct}}% | {{prior_recovery}}% | {{trend_recovery}} |
+| Fraud flags triggered | {{fraud_flags}} | {{prior_fraud}} | {{trend_fraud}} |
+| Confirmed fraud cases | {{confirmed_fraud}} | {{prior_confirmed}} | {{trend_confirmed}} |
+| Vendor RTV claims filed | {{rtv_count}} ({{rtv_value}}) | {{prior_rtv}} | {{trend_rtv}} |
+
+## Top Return Reasons
+
+| Reason | Count | % of Total | Avg Value |
+|---|---|---|---|
+| {{reason_1}} | {{count_1}} | {{pct_1}}% | {{avg_1}} |
+| {{reason_2}} | {{count_2}} | {{pct_2}}% | {{avg_2}} |
+| {{reason_3}} | {{count_3}} | {{pct_3}}% | {{avg_3}} |
+| {{reason_4}} | {{count_4}} | {{pct_4}}% | {{avg_4}} |
+| {{reason_5}} | {{count_5}} | {{pct_5}}% | {{avg_5}} |
+
+## Top SKUs by Return Volume
+
+| SKU | Product | Returns | Return Rate | Primary Reason | Action |
+|---|---|---|---|---|---|
+| {{sku_1}} | {{prod_1}} | {{ret_1}} | {{rate_1}}% | {{reason_sku_1}} | {{action_1}} |
+| {{sku_2}} | {{prod_2}} | {{ret_2}} | {{rate_2}}% | {{reason_sku_2}} | {{action_2}} |
+| {{sku_3}} | {{prod_3}} | {{ret_3}} | {{rate_3}}% | {{reason_sku_3}} | {{action_3}} |
+
+## Exceptions and Escalations
+
+- {{exception_summary_1}}
+- {{exception_summary_2}}
+- {{exception_summary_3}}
+
+## Recommendations
+
+- {{recommendation_1}}
+- {{recommendation_2}}
+- {{recommendation_3}}
+
+---
+
+Prepared by: {{our_contact_name}}, {{our_contact_title}}
+Distribution: {{distribution_list}}
+
+---
+
+## 9. Return Policy Exception Approval
+
+### When to Use
+- When an exception to standard return policy has been approved (outside window, missing receipt, condition outside standard acceptance criteria).
+- Documents the exception for audit trail and communicates the decision to the customer.
+
+### Tone Guidance
+Customer-facing version: warm, conveys that you went above and beyond. Internal version: factual, documents the business justification.
+
+### Customer-Facing Template
+
+**Subject:** Good News — Your Return Has Been Approved
+
+---
+
+Hi {{customer_name}},
+
+We've reviewed your return request for **{{product_name}}** (Order {{order_number}}) and we're happy to let you know that we've approved it as a one-time exception.
+
+**Here's what you need to know:**
+
+- **Refund amount:** {{refund_amount}} as {{refund_type}}
+- **How to return:** {{return_instructions}}
+- **RMA Number:** {{rma_number}} (valid through {{rma_expiry}})
+
+{{#if conditions}}
+**Please note:** {{exception_conditions}}
+{{/if}}
+
+We appreciate your loyalty and hope this helps. If you need anything else, we're here.
+
+Best,
+{{our_contact_name}}
+{{our_company}} Customer Care
+
+---
+
+### Internal Approval Record
+
+**Policy Exception Approval**
+
+| Field | Detail |
+|---|---|
+| RMA | {{rma_number}} |
+| Customer | {{customer_name}} ({{customer_email}}) |
+| Order | {{order_number}} |
+| Product | {{product_name}} ({{product_sku}}) |
+| Purchase Price | {{purchase_price}} |
+| Refund Amount | {{refund_amount}} |
+| Refund Type | {{refund_type}} |
+| Standard Policy Violation | {{policy_violation}} |
+| Exception Score | {{exception_score}} (per Exception Matrix) |
+| Customer LTV | {{customer_ltv}} |
+| Customer Return Rate | {{customer_return_rate}}% |
+| Business Justification | {{business_justification}} |
+| Approved By | {{approver_name}} ({{approver_title}}) |
+| Approval Date | {{approval_date}} |
+| Precedent Risk | {{precedent_risk}} |
+| Notes | {{approval_notes}} |
diff --git a/web-app/public/skills/returns-reverse-logistics/references/decision-frameworks.md b/web-app/public/skills/returns-reverse-logistics/references/decision-frameworks.md
new file mode 100644
index 00000000..6b84367f
--- /dev/null
+++ b/web-app/public/skills/returns-reverse-logistics/references/decision-frameworks.md
@@ -0,0 +1,823 @@
+# Decision Frameworks — Returns & Reverse Logistics
+
+This reference provides the detailed decision logic, scoring matrices, financial models,
+grading standards, and disposition workflows for returns and reverse logistics operations.
+It is loaded on demand when the agent needs to make or recommend nuanced return-handling
+decisions.
+
+All thresholds, timelines, and cost assumptions reflect US retail and e-commerce operations
+with applicability to omnichannel, pure-play e-commerce, and brick-and-mortar environments.
+
+---
+
+## 1. Disposition Decision Trees by Product Category
+
+### 1.1 Decision Methodology
+
+Every returned item follows a decision tree that routes to the highest-value disposition
+channel. The routing decision is made after grading (see §5) and considers:
+
+1. **Recovered value** at each disposition tier (restock, open box, refurbish, liquidate, donate, destroy)
+2. **Processing cost** for each tier (inspection, repackaging, refurbishment, shipping)
+3. **Time-to-recovery** — cash tied up in returns inventory has a carrying cost
+4. **Regulatory constraints** — some dispositions are prohibited for certain categories
+5. **Brand protection** — premium brands may restrict secondary-market sales
+
+The **net recovery** for any disposition = `(Sale price at channel) - (Processing cost) - (Shipping cost) - (Channel fees)`.
+
+Always route to the disposition with the highest net recovery, subject to regulatory and
+brand constraints.
+
+### 1.2 Consumer Electronics
+
+Consumer electronics are the highest-value and most complex returns category. Serial numbers,
+firmware states, activation locks, and functional testing requirements add cost and time.
+
+```
+RECEIVE → Verify serial number matches RMA
+ ├── Mismatch → Flag for fraud review (swap fraud), HALT processing
+ └── Match → Visual inspection
+ ├── Grade A (no cosmetic defects, all accessories, original packaging)
+ │ └── Functional test (power on, screen, connectivity, battery health)
+ │ ├── Pass → Check activation lock / factory reset status
+ │ │ ├── Locked → Contact customer for unlock, hold 48 hrs
+ │ │ │ ├── Unlocked within 48 hrs → Restock as new
+ │ │ │ └── Not unlocked → Grade B (open box with disclaimer)
+ │ │ └── Clean → Restock as new (full margin recovery)
+ │ └── Fail → Route to refurbishment assessment
+ │ ├── Refurb cost < 40% of refurb selling price → Refurbish
+ │ ├── Refurb cost 40-60% → Liquidate as "for parts / not working"
+ │ └── Refurb cost > 60% → Parts harvest or e-waste recycling
+ ├── Grade B (minor cosmetic wear, accessories complete, packaging damaged)
+ │ └── Functional test
+ │ ├── Pass → Repackage as "open box" or "renewed" (60-80% of retail)
+ │ └── Fail → Refurbishment assessment (same tree as above)
+ ├── Grade C (visible wear, scratches, missing non-essential accessories)
+ │ └── Functional test
+ │ ├── Pass → Sell through secondary channel at 30-50% of retail
+ │ └── Fail → Parts harvest if unit value > $100, else e-waste
+ └── Grade D (heavily damaged, non-functional, missing critical components)
+ └── Parts harvest if any component value > $15, else e-waste recycling
+```
+
+**Category-specific thresholds:**
+- Smartphones: Always verify IMEI against stolen device databases (GSMA) before restocking
+- Laptops: Battery health must be > 80% for Grade A restock; 60-80% triggers Grade B
+- Tablets: Check for MDM (mobile device management) profiles — enterprise tablets may have
+ remote-lock capability that surfaces post-sale
+- Headphones: Hygiene concern — all ear tips/pads replaced before resale ($2-8 per unit)
+- Smart home devices: Factory reset verified; linked account removal confirmed. A smart lock
+ that is still linked to a previous owner's account is unsellable and potentially a safety issue
+
+**Typical processing costs:**
+| Action | Cost per Unit | Time per Unit |
+|--------|--------------|---------------|
+| Visual inspection | $1.50-2.50 | 45-90 seconds |
+| Functional test (basic) | $3.00-5.00 | 2-4 minutes |
+| Functional test (full diagnostic) | $8.00-15.00 | 10-20 minutes |
+| Repackaging | $5.00-12.00 | 3-8 minutes |
+| Refurbishment (minor: screen clean, reset) | $15.00-30.00 | 15-30 minutes |
+| Refurbishment (moderate: component replacement) | $30.00-80.00 | 30-90 minutes |
+| Data wipe (NIST 800-88 compliant) | $5.00-10.00 | 5-15 minutes |
+
+### 1.3 Apparel and Footwear
+
+Apparel returns are high-volume, low-unit-value, and condition-sensitive. Odour, stains,
+and stretched fabric are the primary defects. Speed is critical because fashion depreciates
+rapidly — a trend item loses 10-20% of sellable value per month.
+
+```
+RECEIVE → Scan RMA / order lookup
+ └── Visual inspection (30-60 seconds)
+ ├── Tags attached, no signs of wear
+ │ ├── Original packaging intact → Restock as new
+ │ └── Packaging damaged/missing → Repackage, restock as new (tag is key, not box)
+ ├── Tags removed but no signs of wear
+ │ └── UV light + odour check
+ │ ├── Clean → Restock as "like new" or outlet (80-90% of retail)
+ │ └── Traces detected → Grade C, route to launder/clean assessment
+ │ ├── Cleaning cost < $5 and item value > $30 → Clean and restock as outlet
+ │ └── Cleaning not viable or cost > value threshold → Liquidate by weight
+ ├── Visible wear, stains, or damage
+ │ ├── Premium brand (retail > $100) → Assess repair viability
+ │ │ ├── Repair cost < 20% of outlet price → Repair and sell through outlet
+ │ │ └── Repair not viable → Liquidate (never destroy premium apparel; brand resale exists)
+ │ └── Standard brand → Liquidate by weight ($0.50-2.00/lb) or textile recycling
+ └── Heavily damaged, soiled, or biohazard
+ └── Textile recycling or destroy (biohazard requires specific disposal)
+```
+
+**Apparel-specific considerations:**
+- Seasonal timing is everything: a winter coat returned in February can restock for next season,
+ but the carrying cost of 8 months of storage may exceed liquidation recovery. Decision point:
+ if storage cost > (expected recovery next season × probability of sale) - liquidation value now,
+ liquidate immediately.
+- Footwear: Check sole wear. A shoe worn on carpet for 5 minutes is different from one worn
+ on pavement. Sole scuffing = Grade C minimum. Check for orthotics left inside.
+- Swimwear and intimate apparel: Once hygienic liner is removed, non-returnable per health code
+ in most jurisdictions. If returned, destroy — do not restock or liquidate.
+- Designer/luxury: Authenticate before accepting. Counterfeits in the return stream are
+ increasing. Compare serial numbers, stitching quality, hardware weight against known
+ genuine samples.
+
+### 1.4 Home, Furniture, and Large Goods
+
+Returns of bulky items are expensive — return shipping alone can be $50-200+. The disposition
+decision often happens before the item physically returns.
+
+```
+CUSTOMER INITIATES RETURN →
+ ├── Item value < return shipping cost × 2.5
+ │ └── Offer returnless refund (customer keeps item, full refund)
+ │ Cost justification: returnless refund costs $X (product value).
+ │ Processing the return costs $X (product) + $Y (shipping) + $Z (processing).
+ │ If Y + Z > 40% of X, returnless is cheaper.
+ ├── Item value > threshold AND item is in original packaging
+ │ └── Schedule carrier pickup → Receive → Inspect
+ │ ├── Grade A → Restock (furniture typically restock at 85-95% due to assembly/box condition)
+ │ ├── Grade B → Sell as "open box" in-store (avoid re-shipping; sell from nearest location)
+ │ ├── Grade C → Donate locally (shipping destroyed items is negative ROI)
+ │ └── Grade D → Local disposal (donation or recycling based on materials)
+ └── Item is assembled
+ └── Generally non-returnable once assembled (policy). Exceptions:
+ ├── Defective → Offer replacement parts first, full return if unfixable
+ ├── Missing parts on arrival → Ship missing parts (cheaper than full return)
+ └── Customer insists → Accept but apply 25% restocking fee to cover disassembly/repackaging
+```
+
+### 1.5 Health, Beauty, and Personal Care
+
+Regulatory constraints dominate this category. Once opened, most health and beauty products cannot
+be legally resold due to FDA and state health department regulations.
+
+```
+RECEIVE → Seal integrity check
+ ├── Sealed / unopened
+ │ ├── Expiration date > 6 months out → Restock as new
+ │ ├── Expiration 3-6 months → Restock with markdown or outlet
+ │ └── Expiration < 3 months → Donate (tax benefit > markdown recovery)
+ ├── Opened but appears unused (seal broken, product visually intact)
+ │ └── DESTROY. Cannot verify non-contamination. No restocking of opened health/beauty.
+ │ Exception: Hard goods (hair dryers, electric razors) → treat as electronics tree
+ └── Used
+ └── DESTROY. Biohazard disposal if applicable (used cosmetics applicators, skincare).
+```
+
+**Special cases:**
+- Prescription items: Cannot accept return under any circumstances (most states). Direct
+ customer to pharmacy or manufacturer disposal programme.
+- Supplements/vitamins: Same as cosmetics — once opened, destroy. Sealed returns restock
+ only with lot number verification.
+- Sunscreen: Regulated as OTC drug by FDA. Opened sunscreen is destroyed. Expired sunscreen
+ (even sealed) is destroyed — never sell expired OTC.
+
+### 1.6 Books, Media, and Software
+
+High restock rate, low processing cost. The primary fraud vector is digital content extraction
+(reading/ripping then returning).
+
+```
+RECEIVE → Condition check
+ ├── New condition (no creasing, bending, markings)
+ │ └── Restock as new. Media: verify disc is present and matches case.
+ ├── Minor wear (slight cover bend, shelf wear)
+ │ └── Restock at minor discount or sell through marketplace as "very good"
+ ├── Moderate wear (highlighting, writing, water damage)
+ │ └── Liquidate through bulk book buyers ($0.10-0.50 per book) or donate
+ └── Software / digital media
+ ├── If activation key is unredeemed → Restock
+ ├── If key is redeemed → Cannot resell. Write off. Pursue refund from publisher if within terms.
+ └── Physical media with digital code (game + download) → Sell disc only at reduced price
+```
+
+---
+
+## 2. Fraud Detection Scoring Model
+
+### 2.1 Scoring Architecture
+
+The fraud scoring model assigns points based on observable signals at the time of return
+initiation (pre-receipt signals) and at the time of physical inspection (post-receipt
+signals). The two scores are summed for a composite score.
+
+**Thresholds:**
+| Composite Score | Action |
+|----------------|--------|
+| 0-30 | Process normally. No additional review. |
+| 31-50 | Flag for passive monitoring. Process refund but add customer to watch list for 90 days. |
+| 51-64 | Enhanced inspection. Hold refund until physical inspection is complete and matches RMA description. |
+| 65-79 | Supervisor review. Hold refund. Detailed inspection with photo documentation. Supervisor approves or escalates. |
+| 80-100 | Fraud review team. Refund on hold. Customer contacted for "verification" (never say "fraud"). LP notified. |
+
+### 2.2 Pre-Receipt Signals (scored at return initiation)
+
+| Signal | Points | Logic |
+|--------|--------|-------|
+| Customer return rate > 30% (rolling 12 months, ≥ 5 orders) | +15 | High return rate alone isn't fraud, but it is a risk multiplier. Exclude exchanges from rate calculation. |
+| Return rate > 50% | +25 | Replaces the +15 above. At this rate, the customer is almost certainly bracket-shopping or abusing policy. |
+| Return initiated < 48 hours after delivery confirmation | +5 | Could be legitimate (wrong item, didn't match description) or bracket shopping. Mild signal. |
+| Return reason is "defective" but product category has < 2% defect rate | +10 | "Defective" is used to avoid restocking fees. True defect claims on low-defect products are suspicious. |
+| Return reason changed between online initiation and customer service contact | +10 | Inconsistency suggests the customer is constructing a narrative. |
+| Customer account age < 30 days | +10 | New accounts used for return fraud or testing fraud viability. |
+| Multiple returns in same week (3+) | +10 | Cumulative with return rate signal. Suggests bracket shopping or wardrobing batch. |
+| Return from an address different than the original shipping address | +10 | Excludes gift returns (flagged as gift at order). Otherwise indicates potential organised activity. |
+| Item is in a high-shrink category (electronics, designer, cosmetics) | +5 | These categories have higher fraud incidence. Mild base signal. |
+| No-receipt or no-order-match return | +15 | Receipt fraud is the primary risk vector. Match to payment method or loyalty ID. |
+| Order was placed with a promotion/coupon > 30% off | +5 | Price-arbitrage returns are more common on heavily discounted purchases. |
+| Customer has previously been flagged for fraud review (any outcome) | +15 | Prior flags, even if resolved as legitimate, indicate a pattern worth monitoring. |
+
+### 2.3 Post-Receipt Signals (scored during physical inspection)
+
+| Signal | Points | Logic |
+|--------|--------|-------|
+| Serial number mismatch (does not match the unit sold to this customer) | +40 | Near-certain swap fraud. Verify against order record before escalating — packing errors at fulfilment can cause legitimate mismatches. |
+| Product weight differs > 5% from expected for SKU | +25 | Indicates missing components, swap with lighter/cheaper item, or empty packaging. Weigh before opening. |
+| IMEI/MEID on returned device doesn't match sold device | +40 | Definitive swap fraud for mobile devices. Cross-reference IMEI from order with IMEI on returned device. |
+| Product shows wear inconsistent with stated return reason | +15 | "Changed my mind" return on a laptop with 200 battery cycles suggests extended use. |
+| Tags removed on apparel/footwear with "didn't fit" reason | +10 | Tags removed is consistent with wearing, not just trying on. |
+| Cosmetic traces on apparel (makeup, deodorant, perfume) | +15 | Wardrobing indicator. UV light reveals traces invisible to naked eye. |
+| Packaging has been repacked (tape over tape, non-original inner packaging) | +10 | Could indicate swap (customer repacked a different item) or simply customer repackaging for return. Context-dependent. |
+| Security/RFID tag removed | +20 | Tags that are not customer-removable (hidden tags, sewn-in RFID) should still be present. Removal suggests the item was worn/used in a retail environment. |
+| Product firmware/software shows usage history inconsistent with claim | +15 | Laptop claiming "unopened" but with 6 months of OS updates installed. |
+| Multiple units of same SKU returned (3+) in single return | +10 | Could be legitimate (sizing across colours) or reseller return. Check original order for bulk discount. |
+
+### 2.4 Score Adjustments and Overrides
+
+| Condition | Adjustment |
+|-----------|-----------|
+| Customer lifetime value > $10,000 and net LTV positive | -15 points (floor at 0) |
+| Customer is a verified loyalty programme member (2+ years) | -10 points |
+| Return is an exchange (not refund) | -10 points |
+| Return reason is verified fulfilment error (wrong item shipped) | Set score to 0, process immediately |
+| Return was pre-approved by customer service with case notes | -10 points |
+| Customer has filed a chargeback simultaneously with this return | +20 points (escalate regardless of score) |
+
+### 2.5 False Positive Management
+
+False positives destroy customer relationships. Every customer flagged by the fraud scoring
+system who turns out to be legitimate represents a risk of customer attrition. Manage through:
+
+1. **Never communicate "fraud" to the customer.** Use neutral language: "additional processing
+ time," "verification of your return," "quality review."
+2. **Time-box the review.** Flagged returns must be resolved within 5 business days. If the
+ review cannot conclusively determine fraud within 5 days, process the refund. The cost
+ of a false positive held for 3 weeks exceeds the cost of most fraudulent returns.
+3. **Track false positive rate monthly.** Target: < 3% of total returns flagged are
+ confirmed false positives. If rate exceeds 5%, recalibrate the scoring model.
+4. **Feedback loop:** Every fraud review outcome (confirmed fraud, confirmed legitimate,
+ inconclusive) feeds back into the scoring model calibration. Signals that generate
+ high false-positive rates have their point values reduced.
+
+---
+
+## 3. Vendor Recovery Framework
+
+### 3.1 Return-to-Vendor (RTV) Process
+
+RTV is the primary mechanism for recovering costs on defective products. The process:
+
+```
+Identify RTV-eligible unit (defective, vendor-caused quality issue, mispick at vendor DC)
+ │
+ ├── Check vendor agreement for RTV terms
+ │ ├── RTV window: Typically 90 days from retailer receipt of return (not customer purchase date)
+ │ ├── Minimum shipment value: Usually $200-500 per RTV shipment
+ │ ├── Documentation requirements: Varies by vendor (photos, defect codes, customer complaint data)
+ │ └── RTV authorisation: Some vendors require pre-approval; others accept "open RTV" under agreement
+ │
+ ├── Accumulate RTV-eligible units by vendor
+ │ ├── Stage in designated RTV area (separate from general returns inventory)
+ │ ├── Track aging — units approaching 90-day window need priority shipment
+ │ └── Batch by vendor to meet minimum shipment thresholds
+ │
+ ├── Obtain RTV authorisation (if required)
+ │ ├── Submit RTV request with: SKU, quantity, defect description, photos, customer return rate data
+ │ └── Vendor has 5-10 business days to approve/deny (per most vendor agreements)
+ │
+ ├── Ship to vendor return facility
+ │ ├── Use vendor-provided shipping label (if applicable — vendor pays)
+ │ ├── If retailer pays shipping: deduct from credit claim or use lowest-cost carrier
+ │ └── Track shipment and confirm delivery at vendor facility
+ │
+ └── Track credit issuance
+ ├── Vendor credit should appear within 30-45 days of vendor receipt
+ ├── If no credit at 30 days: first follow-up (email to vendor returns dept)
+ ├── If no credit at 45 days: escalate to vendor account manager
+ ├── If no credit at 60 days: debit memo against next PO (per vendor agreement terms)
+ └── If vendor disputes: provide defect documentation as evidence. Escalate to vendor management.
+```
+
+### 3.2 Defect Rate Monitoring and Claims
+
+Beyond individual RTV, monitor defect rates at the SKU level to identify systemic quality
+issues that trigger formal defect claims:
+
+| Defect Rate (per SKU, rolling 90 days) | Action |
+|----------------------------------------|--------|
+| < 2% | Normal. Process individual RTVs. No escalation. |
+| 2-5% | Alert vendor management. Request root cause analysis from vendor. Continue selling but monitor weekly. |
+| 5-8% | Formal quality complaint. Demand corrective action plan within 14 days. Consider pull from active sales pending vendor response. |
+| 8-15% | Pull from active sales. Formal defect claim for all returns above the 2% baseline. Negotiate credit or replacement. |
+| > 15% | Full stop-sale. Vendor compliance violation. Chargebacks for all returns + lost margin + customer service costs. Consider vendor termination. |
+
+**Defect claim calculation:**
+```
+Total returns for SKU in period: 500 units
+Expected baseline return rate (non-defect): 8% of units sold (industry avg for category)
+Units sold: 4,000
+Expected returns: 320
+Excess returns attributable to defect: 500 - 320 = 180 units
+Claim = 180 × (wholesale cost + inbound freight per unit + return processing cost per unit)
+ = 180 × ($24.00 + $1.80 + $7.50)
+ = 180 × $33.30
+ = $5,994.00
+```
+
+Add consequential costs if the defect caused customer service escalations, negative reviews
+that required response, or marketplace listing suppression.
+
+### 3.3 Vendor Chargeback Schedule
+
+For vendor-caused issues beyond defects (packaging failures, mislabelling, wrong items shipped
+from vendor DC), apply chargebacks per the vendor compliance programme:
+
+| Violation | Chargeback | Notes |
+|-----------|-----------|-------|
+| Wrong item shipped from vendor DC | 100% of product cost + return shipping + $25 processing fee | Requires photo evidence of received vs ordered |
+| Mislabelled product (UPC doesn't match contents) | $50 per incident + product cost if unsellable | Creates inventory accuracy issues downstream |
+| Packaging failure (product damaged due to inadequate packaging) | 100% of product cost + return processing | Requires photos of packaging condition at receipt |
+| Missing components (accessory, manual, warranty card) | Cost of sourcing replacement component + $10 processing | If component unavailable, full product cost |
+| Counterfeit or unauthorised product | 300% of product cost + $500 penalty per incident | Zero tolerance. Notify brand protection. |
+| Late shipment from vendor causing customer-facing delay | Customer credit issued + $15 processing | Must document customer complaint and credit |
+| Incorrect hazmat/regulatory documentation | $250 per incident + cost of regulatory remediation | Regulatory liability makes this non-negotiable |
+
+### 3.4 Vendor Recovery ROI Model
+
+Not all vendor recovery is worth pursuing. The ROI model:
+
+```
+Recovery ROI = (Expected recovery - Recovery cost) / Recovery cost
+
+Where:
+ Expected recovery = Claim amount × Collection probability
+ Recovery cost = Labour (documentation, communication, follow-up) + Shipping (if RTV) + Relationship cost
+
+Labour cost estimates:
+ - Simple RTV with existing authorisation: $15-25 per batch
+ - Defect claim requiring documentation assembly: $75-150 per claim
+ - Disputed claim requiring escalation and negotiation: $200-500 per claim
+
+Collection probability by vendor tier:
+ - Tier 1 (top 20 vendors, strong relationship): 85-95%
+ - Tier 2 (mid-tier, established relationship): 65-80%
+ - Tier 3 (small/new vendors): 40-60%
+ - International vendors (no US entity): 25-45%
+```
+
+**Decision matrix:**
+| Claim Amount | Tier 1 Vendor | Tier 2 Vendor | Tier 3 Vendor | International |
+|-------------|---------------|---------------|---------------|---------------|
+| < $100 | Offset against next PO | Offset against next PO | Write off | Write off |
+| $100-500 | Batch RTV | Batch RTV | Batch if > $200 total | Write off, note for contract |
+| $500-2,000 | Standard RTV/claim | Standard claim | Standard claim with escalation plan | Claim if > $1,000 |
+| $2,000-10,000 | Standard claim | Standard claim + account mgr | Account mgr + formal notice | Pursue with local agent if > $5,000 |
+| > $10,000 | VP-level engagement | VP-level + legal review | Legal review | Legal counsel in vendor's jurisdiction |
+
+---
+
+## 4. Return Policy Exception Matrix
+
+### 4.1 Exception Decision Framework
+
+When a return falls outside standard policy, the decision to grant an exception depends on
+a structured evaluation, not individual judgment calls. This matrix standardises the
+exception decision.
+
+**Step 1: Is the exception request covered by an automatic override?**
+
+| Condition | Action | No Further Analysis Needed |
+|-----------|--------|--------------------------|
+| Product is defective (verified or reasonably claimed) | Accept return, full refund, no restocking fee | Yes |
+| Fulfilment error (wrong item shipped, wrong quantity) | Accept return, full refund, prepaid return label | Yes |
+| Product is subject to active recall | Route to recall programme (not returns) | Yes |
+| Customer is in top 5% by LTV and request is first exception in 12 months | Grant exception, standard refund | Yes |
+| State or federal law requires acceptance (lemon law, cooling-off period) | Comply with applicable law | Yes |
+
+**Step 2: If not an automatic override, score the exception request:**
+
+| Factor | Score Range | Description |
+|--------|-----------|-------------|
+| Days past policy window | 1-30 days: +2 / 31-60 days: +5 / 61-90 days: +8 / >90 days: +12 | How far outside the standard window |
+| Product condition at return | Grade A: 0 / Grade B: +2 / Grade C: +5 / Grade D: +10 | Worse condition = higher cost of exception |
+| Customer LTV | Top 20%: -5 / Middle 60%: 0 / Bottom 20%: +3 | Valuable customers get more latitude |
+| Return reason credibility | Compelling story with evidence: -3 / Plausible: 0 / Weak: +5 | "My house flooded" with photos vs "I forgot" |
+| Precedent risk | Private resolution: 0 / Customer mentioned social media: +5 / Customer has large following: +8 | Public exceptions become policy expectations |
+| Product restockability | Restockable as new: -3 / Open box: 0 / Liquidation: +3 / Destroy: +5 | Restockable items cost less to accept |
+
+**Step 3: Interpret the exception score:**
+
+| Score | Decision | Authority Level |
+|-------|----------|----------------|
+| < 0 | Grant exception. Cost is minimal, customer value is high. | Returns associate |
+| 0-5 | Grant exception with standard refund. | Team lead |
+| 6-10 | Grant as store credit (not original payment refund). | Team lead |
+| 11-15 | Partial credit (50-75% of purchase price) as store credit. | Returns manager |
+| 16-20 | Deny with empathetic explanation and alternative offer (exchange, discount on next purchase). | Returns manager |
+| > 20 | Deny. Offer to connect with manufacturer warranty if applicable. | Returns manager |
+
+### 4.2 Common Exception Scenarios with Recommended Resolutions
+
+| Scenario | Typical Score | Recommended Resolution |
+|----------|--------------|----------------------|
+| 5 days past window, Grade A, loyal customer | -3 | Full refund to original payment |
+| 45 days past window, Grade B, average customer | +7 | Store credit for purchase price |
+| 90 days past window, Grade C, low-value customer | +16 | Deny, offer 15% discount on next purchase |
+| 10 days past window, Grade A, customer cited family emergency | -1 | Full refund to original payment |
+| Within window, Grade C, customer claims defect but inspection shows user damage | +10 | Store credit at 50% (goodwill), document for fraud scoring |
+| 60 days past window, brand-new customer, first order | +13 | Partial credit (50%), welcome them back with incentive |
+
+---
+
+## 5. Grading Standards by Product Category
+
+### 5.1 Universal Grading Criteria
+
+All categories share these baseline grade definitions. Category-specific addenda
+follow in §5.2.
+
+#### Grade A — Like New
+- Zero signs of use beyond initial unboxing
+- All original accessories, manuals, and packaging materials present
+- Original packaging in good condition (minor shipping wear acceptable)
+- Passes all applicable functional and safety tests
+- Can be restocked and sold as new without any additional processing beyond re-shelving
+
+#### Grade B — Good / Open Box
+- Minor cosmetic imperfections (light surface scratches, small scuffs) that do not affect function
+- Original packaging may be damaged, opened, or missing outer sleeve/shrink wrap
+- All essential accessories present (charger, main cable); non-essential items (stickers, pamphlets) may be missing
+- Fully functional — passes all applicable tests
+- Requires repackaging or "open box" labelling before resale
+
+#### Grade C — Fair
+- Visible cosmetic wear, scratches, dents, or staining that are noticeable at arm's length
+- Missing accessories that affect the completeness of the product (but not its core function)
+- Functional but may have minor performance degradation (battery at 60-80%, worn but operational buttons)
+- Not suitable for primary retail channel — routes to outlet, marketplace, or liquidation
+- May be viable for refurbishment if cost justifies it
+
+#### Grade D — Salvage / Parts
+- Non-functional, heavily damaged, or missing critical components that render the product unusable
+- Structural damage (cracked screens, bent frames, water damage indicators triggered)
+- May have value for parts harvesting or materials recovery
+- Routes to parts extraction, recycling, or destruction
+
+### 5.2 Category-Specific Grading Addenda
+
+**Consumer Electronics:**
+- Grade A additional requirement: battery health > 80% of design capacity (measurable via diagnostic)
+- Grade B threshold: battery 60-80%, cosmetic scratches visible only under direct light
+- Functional test required for all grades: power on, display, connectivity (WiFi/Bluetooth/cellular), speakers, cameras, ports
+- Data wipe verification mandatory before any resale disposition
+
+**Apparel:**
+- Grade A: tags attached (original retail tags, not just care labels)
+- Grade B: tags removed, but no wear indicators; passes UV and odour check
+- Grade C: visible wear, minor staining treatable with professional cleaning, or slight fabric stretching
+- Grade-reducing odours: tobacco smoke, pet odour, heavy fragrance, body odour
+- Automatic Grade D: mould, mildew, pest contamination
+
+**Footwear:**
+- Sole inspection is primary grading factor: unworn soles = Grade A, indoor-only wear marks = Grade B, outdoor wear = Grade C
+- Grade B requires: no toe box creasing deeper than 2mm, no heel counter collapse
+- Include insole inspection: customer orthotics must be removed, original insole must be present
+
+**Home Goods / Small Appliances:**
+- Grade A: unused, all packaging foam/wrapping in place
+- Functional test: operate through one full cycle (coffee maker: brew cycle, vacuum: run for 60 seconds, blender: blend ice test)
+- Missing filters, bags, or consumable accessories: Grade B (replaceable at $3-10 cost)
+- Cosmetic damage on surfaces visible during normal use: Grade C
+
+---
+
+## 6. Liquidation Channel Selection
+
+### 6.1 Channel Overview
+
+When product is routed to liquidation, selecting the right channel significantly affects
+recovery rates. The wrong channel can mean the difference between 20% recovery and 5%.
+
+| Channel | Best For | Typical Recovery (% of retail) | Fees | Min Lot Size | Speed to Cash |
+|---------|----------|-------------------------------|------|-------------|---------------|
+| B-Stock (owned auctions) | Electronics, home goods | 12-25% | 10-15% of sale | 1 pallet | 2-4 weeks |
+| Direct Liquidation | Mixed general merchandise | 8-18% | 15-20% of sale | 1 pallet | 2-6 weeks |
+| Bulq (owned by Optoro) | Small lots, mixed goods | 10-20% | Built into marketplace | 1 box (small lots) | 1-3 weeks |
+| Regional liquidators | Bulky/heavy items, furniture | 5-15% | Negotiated | Varies | 1-4 weeks |
+| Wholesale to dollar stores | Low-value general merchandise | 3-8% (often per-pound) | None (buy outright) | Truckload preferred | Immediate |
+| Online marketplace (eBay, Amazon Warehouse) | Individually valuable items ($50+) | 25-50% | 12-15% + shipping | Single unit | 1-8 weeks |
+| Charity donation | Items not worth liquidating, brand-sensitive | $0 (tax deduction at FMV) | None | No minimum | Immediate |
+
+### 6.2 Channel Selection Decision Tree
+
+```
+Is the individual unit value > $50?
+ ├── Yes → Is the item in Grade B or better condition?
+ │ ├── Yes → Sell individually on marketplace (eBay, Amazon Warehouse). Highest recovery.
+ │ └── No → Is the brand premium/recognisable?
+ │ ├── Yes → Auction on B-Stock (brand buyers pay premium). Recovery 15-25%.
+ │ └── No → Direct Liquidation or regional liquidator. Recovery 8-15%.
+ └── No → Is there a full pallet of same or similar category?
+ ├── Yes → Auction as category-sorted pallet on B-Stock or Direct Liquidation.
+ │ Recovery improves 30-50% vs mixed pallets.
+ └── No → Accumulate by category until pallet quantity reached.
+ If aging > 30 days, mix into general pallet and liquidate.
+ Holding cost exceeds sort premium beyond 30 days.
+```
+
+**Critical liquidation rules:**
+1. Never mix electronics with non-electronics on the same pallet. Electronics buyers won't bid on mixed pallets.
+2. Never include recalled products, counterfeit items, or hazmat in liquidation lots. Liability exposure is unlimited.
+3. Remove all customer personal data before liquidating electronics. Data breach from a liquidated device creates legal exposure.
+4. Photograph every pallet before shipping to liquidation. Disputes about condition are common.
+5. Manifest every pallet (list of SKUs, quantities, conditions). Manifested pallets sell for 20-40% more than unmanifested.
+
+---
+
+## 7. Refurbishment ROI Model
+
+### 7.1 When to Refurbish
+
+Refurbishment is only viable when the economics justify it. The decision model:
+
+```
+Refurbishment ROI = (Refurbished selling price - Refurbishment cost - Fulfilment cost) / Refurbishment cost
+
+Decision thresholds:
+ ROI > 100%: Always refurbish. High-value recovery.
+ ROI 50-100%: Refurbish if capacity exists. Good return on investment.
+ ROI 25-50%: Refurbish only if liquidation alternative is particularly poor (< 8% recovery).
+ ROI < 25%: Liquidate. The refurbishment effort isn't justified.
+```
+
+### 7.2 Refurbishment Cost Benchmarks by Category
+
+| Category | Common Defects | Typical Refurb Cost | Typical Refurb Selling Price | Typical ROI |
+|----------|---------------|--------------------|-----------------------------|-------------|
+| Smartphones (flagship) | Screen scratches, battery degradation | $40-80 (screen polish, battery replace) | $350-550 (65-75% of new) | 300-500% |
+| Laptops | Battery, cosmetic damage, slow storage | $50-120 (battery, SSD upgrade, clean) | $400-800 (55-70% of new) | 200-400% |
+| Tablets | Screen scratches, battery | $30-60 | $200-400 (60-70% of new) | 200-350% |
+| Small appliances | Cosmetic, missing parts | $10-25 (clean, replace accessory) | $30-60 (50-65% of new) | 100-200% |
+| Power tools | Battery, switch wear | $20-45 (battery, switch replacement) | $60-120 (55-65% of new) | 100-200% |
+| Headphones (premium) | Ear pad wear, cosmetic | $8-15 (new pads, clean) | $80-200 (60-75% of new) | 400-800% |
+| Game consoles | Cosmetic, controller wear | $15-30 (clean, replace controller pads) | $150-300 (60-70% of new) | 300-500% |
+
+### 7.3 Refurbishment Capacity Planning
+
+Refurbishment requires dedicated space, trained technicians, and parts inventory. The
+capacity model:
+
+- **Space:** 1 refurb station = approximately 80 sq ft (workbench + test equipment + parts storage)
+- **Throughput:** 1 technician handles 8-15 units/day for electronics, 20-30 units/day for small appliances
+- **Parts inventory:** Maintain 30-day supply of top 20 replacement parts by volume (batteries, screens, cables, ear pads, filters)
+- **Break-even:** A refurb station breaks even at approximately 5-8 units per day at average ROI of 150%. Below this volume, outsource to a third-party refurbisher.
+
+### 7.4 Outsource vs In-House Decision
+
+| Factor | In-House | Outsource |
+|--------|----------|-----------|
+| Volume > 40 units/day | Preferred (economies of scale) | Viable but more expensive |
+| Volume < 40 units/day | Only if margin justifies | Preferred (avoid fixed overhead) |
+| Brand certification programme exists | Required for "certified refurbished" branding | Must verify third-party is certified |
+| Product requires proprietary tools/software | In-house (IP control) | Only with NDA and audited facility |
+| Seasonal volume spikes | Core volume in-house, surge outsourced | Flexible capacity |
+| Data security requirements | In-house (direct control over data wipe) | Requires NIST 800-88 certification |
+
+---
+
+## 8. Return Processing Workflow by Channel
+
+### 8.1 E-Commerce Returns (Ship-Back)
+
+The standard e-commerce return flow. This is the highest-volume channel for most
+retailers and the one with the most automation opportunity.
+
+```
+Customer initiates return on website/app
+ │
+ ├── Automated policy check (within window? excluded category? customer in good standing?)
+ │ ├── Auto-approve → Generate RMA + prepaid return label
+ │ ├── Auto-deny → Display denial reason + alternatives
+ │ └── Manual review queue → Agent reviews within 4 hours
+ │
+ ├── Customer ships product
+ │ └── Tracking monitored for: label scan (confirms customer shipped), delivery to return centre
+ │
+ ├── Receiving at return centre
+ │ ├── Scan RMA barcode → pulls order record, expected product, customer profile
+ │ ├── Initial sort: sealed/unopened → express lane (15-second visual, Grade A, restock)
+ │ └── Opened/used → standard inspection lane
+ │
+ ├── Standard inspection (see §5 for grading criteria)
+ │ ├── Serial number verification (electronics only, but expanding to luxury goods)
+ │ ├── Visual inspection + functional test (category-dependent)
+ │ ├── Fraud scoring (post-receipt signals added to pre-receipt score)
+ │ └── Grade assignment: A / B / C / D
+ │
+ ├── Disposition routing (see §1 for category-specific trees)
+ │ ├── Grade A → Restock queue
+ │ ├── Grade B → Open-box / repackaging queue
+ │ ├── Grade C → Liquidation staging or refurbishment assessment
+ │ └── Grade D → Parts / recycling / destruction
+ │
+ └── Refund processing
+ ├── Refund triggered upon grade assignment (do not wait for disposition completion)
+ ├── Restocking fee applied if applicable (calculated at grading, not at refund)
+ └── Refund to original payment method → customer notification sent
+```
+
+**Key timing targets:**
+| Step | Target | Stretch Goal |
+|------|--------|-------------|
+| RMA generation (auto-approve) | < 5 minutes | Instant |
+| Return label delivery to customer | Immediate (email) | Immediate |
+| Customer ship-back | < 7 days from RMA | < 5 days |
+| Receiving scan at return centre | Day of delivery | Same as carrier delivery scan |
+| Inspection + grading | < 24 hours of receipt | < 4 hours |
+| Refund processing | < 24 hours of grading | Same day as grading |
+| Refund visible to customer | 3-5 business days | 1-2 business days |
+| Total RMA-to-refund cycle | < 14 days | < 7 days |
+
+### 8.2 Buy Online, Return In-Store (BORIS)
+
+Cross-channel returns are operationally more complex but have higher customer satisfaction
+and lower total cost (no return shipping). The critical risk is price discrepancy.
+
+```
+Customer arrives at store with online-purchased product
+ │
+ ├── Associate initiates BORIS return in POS
+ │ ├── Scan product barcode
+ │ ├── Look up online order (by order number, customer email, or loyalty account)
+ │ │ ├── Order found → POS displays actual purchase price from online order
+ │ │ │ └── CRITICAL: Refund at actual online purchase price, NOT store shelf price
+ │ │ └── Order not found → Customer provides order confirmation (email/app)
+ │ │ ├── Verified → Manual price entry at confirmed online price
+ │ │ └── Cannot verify → Process through online returns channel (mail-back)
+ │ │ Do NOT guess the price. Do NOT use store shelf price.
+ │ └── Verify return eligibility (window, excluded categories)
+ │
+ ├── In-store inspection
+ │ ├── Visual + functional check (same criteria as return centre)
+ │ ├── For electronics: serial number check against online order
+ │ └── Grade assignment
+ │
+ ├── Refund processing
+ │ ├── Refund to original online payment method (not store credit, not cash)
+ │ │ Exception: customer paid with a gift card → store credit acceptable
+ │ ├── Restocking fee applied if applicable
+ │ └── Customer receives refund confirmation email
+ │
+ └── Inventory disposition
+ ├── If Grade A and product is in store assortment → Restock on store shelf
+ ├── If Grade A but product is online-only → Ship to return centre or nearest DC
+ ├── If Grade B/C → Ship to return centre for open-box/liquidation processing
+ └── If Grade D → Local disposal (do not ship non-functional product to return centre)
+```
+
+**BORIS-specific risks:**
+1. Price discrepancy (online vs store) → Mitigated by mandatory online order lookup
+2. Return of promotional/bundled items → Verify if the item was part of a BOGO or bundle; refund the proportional amount
+3. Store inventory adjustment → Ensure the store's inventory count correctly reflects the returned unit
+4. Different return windows → Online and store may have different windows; honour the more generous one
+
+### 8.3 In-Store Purchase, Return In-Store
+
+The simplest return flow. The POS has the transaction record, pricing is definitive,
+and the product doesn't need to be shipped.
+
+```
+Customer arrives with product + receipt (or POS lookup via card/loyalty)
+ │
+ ├── POS transaction lookup → Confirms purchase price, date, payment method
+ ├── Window check → Within return policy period?
+ ├── Inspection at return counter
+ │ ├── Quick visual for obvious damage/use
+ │ ├── Electronics: power-on test, serial number check
+ │ └── Grade assignment (usually Grade A or B at point of sale)
+ │
+ └── Refund to original payment method → Receipt printed → Customer exits
+```
+
+**Target transaction time:** < 5 minutes for standard returns. This is the benchmark
+that drives customer satisfaction — long return lines at the service desk are the
+#1 complaint in retail returns.
+
+### 8.4 Returnless Refunds (Customer Keeps Product)
+
+For items where the cost of return exceeds the recovery value. The decision model:
+
+```
+Return shipping cost estimate > 40% of product value?
+ ├── Yes → Evaluate returnless refund
+ │ ├── Product value < $50 → Auto-approve returnless refund
+ │ ├── Product value $50-100 → Supervisor auto-approve
+ │ ├── Product value $100-200 → Manager review (consider partial return — just the defective component)
+ │ └── Product value > $200 → Case-by-case (may justify return shipping for high-value)
+ │
+ └── No → Standard return process
+```
+
+**Returnless refund abuse prevention:**
+- Track returnless refunds per customer. More than 3 in 6 months triggers review.
+- High-value returnless refunds (> $100) are flagged for post-refund audit.
+- Products declared "defective" for returnless refund should still be counted in the
+ SKU defect rate, even though the physical product doesn't return.
+- Consider asking the customer to send a photo of the defect as lightweight verification.
+
+---
+
+## 9. Seasonal Return Planning
+
+### 9.1 Holiday Return Surge (January)
+
+January is to returns operations what December is to fulfillment. Plan for:
+
+| Metric | Normal Month | January Peak | Multiplier |
+|--------|-------------|-------------|-----------|
+| Return volume | 100% baseline | 250-350% | 2.5-3.5x |
+| Return processing backlog | < 24 hours | 48-96 hours | 2-4x |
+| Fraud attempts | Baseline | 180-220% | 1.8-2.2x |
+| Customer service contacts about returns | Baseline | 300-400% | 3-4x |
+| Gift receipt returns (% of total) | 5-8% | 25-35% | 4-5x |
+
+**Holiday return planning checklist:**
+1. Staff: Bring temporary inspection staff online by Dec 26. Target: 2x normal inspection capacity by Jan 2.
+2. Space: Reserve additional staging area for the return volume. Last-mile sorting should be simplified (Grade A express lane for sealed/tagged items).
+3. Policy: Extended holiday return window (typically Nov 1 - Dec 31 purchases returnable through Jan 31) means that returns trickle in over 4 weeks rather than concentrating in the first week. Model the curve.
+4. Gift receipts: Train all associates on gift receipt pricing rules. The #1 January return error is refunding at current price instead of purchase price.
+5. Fraud: Increase fraud scoring thresholds by 10% during January (reduce false positives — many legitimate gift returns trigger fraud signals).
+6. Liquidation: Pre-negotiate January liquidation capacity with liquidation partners. You'll have 3-4x normal Grade C/D volume, and everyone else will too.
+
+### 9.2 Category-Specific Seasonal Patterns
+
+| Category | Peak Return Period | Key Driver | Planning Action |
+|----------|-------------------|-----------|----------------|
+| Consumer electronics | Jan 2-15 | Holiday gifts, "not what they wanted" | Pre-stage functional test stations; serial number verification capacity |
+| Apparel | Jan 5-31 (extends longer) | Gift sizing, holiday party returns | UV/odour inspection throughput; wardrobing detection focus |
+| Fitness equipment | Jan 15 - Mar 1 | New Year's resolution abandonment | Large-item return logistics; returnless refund thresholds |
+| Outdoor/sporting goods | Mar-Apr (post-ski), Sep-Oct (post-summer) | Season-end returns | Seasonal markdown timing; storage vs liquidation decision |
+| School supplies | Sep 1-15 | Over-purchasing for school | High-volume, low-value; fast processing is key |
+
+### 9.3 Markdown-Driven Returns
+
+When products go on markdown or clearance, returns of the same product purchased at
+full price increase. Customers are not returning because of dissatisfaction — they're
+returning to repurchase at the lower price (return arbitrage).
+
+**Detection:** Monitor for returns where the same customer repurchases the same SKU within
+7 days of the return. If the repurchase price is lower, flag as potential price-match return.
+
+**Preferred handling:** Offer a price-match credit instead of processing a return and
+repurchase. The price-match credit costs the markdown difference; the return-and-repurchase
+costs the markdown difference plus processing cost plus potential disposition loss.
+
+---
+
+## 10. Data-Driven Return Reduction
+
+### 10.1 Root Cause Analysis by Return Reason
+
+Returns are a symptom. Reducing return rates requires treating the cause:
+
+| Return Reason | Root Cause Investigation | Typical Fix | Expected Reduction |
+|--------------|------------------------|------------|-------------------|
+| "Didn't fit" (apparel) | Poor size guidance, inconsistent sizing, inadequate photos | Size recommendation engine, fit model photos, detailed measurements | 15-25% reduction in "didn't fit" returns |
+| "Not as expected" | Product photo/description doesn't match reality | Lifestyle photos, video demos, customer photos in reviews, AR preview | 10-20% reduction |
+| "Defective" | Manufacturing quality, shipping damage, product design flaw | Vendor quality scorecard, packaging improvement, design feedback loop | Variable — depends on root cause |
+| "Changed my mind" | Impulse purchase, bracketing | Cooling-off period messaging, wish list instead of cart, fit technology | 5-10% reduction |
+| "Better price found" | Competitive pricing, price transparency | Price-match guarantee, automated price alerts | 8-15% reduction |
+| "Arrived too late" | Shipping delays, inaccurate ETAs | Improved delivery estimates, proactive delay notifications | 20-30% reduction in lateness returns |
+
+### 10.2 SKU-Level Return Rate Monitoring
+
+| Return Rate (rolling 90 days) | Action |
+|-------------------------------|--------|
+| < 5% | Normal. No action required. |
+| 5-10% | Review product listing for accuracy. Check reviews for recurring complaints. |
+| 10-15% | Flag for merchandise review. Audit listing photos/description. Check sizing data. |
+| 15-25% | Escalate to category manager. Consider adding warnings to listing. Review vendor quality. |
+| > 25% | Stop-sell review. The product may have a systemic issue that no listing fix can solve. |
+
+### 10.3 Return Cost Allocation Model
+
+Allocating return costs to the business units that drive them creates accountability:
+
+| Return Cause | Cost Allocation |
+|-------------|----------------|
+| Defective product | Vendor (via RTV/defect claim) or Merchandise (if vendor approved) |
+| Wrong item shipped | Fulfillment operations |
+| Damaged in shipping | Carrier (via shipping claim) or Packaging engineering |
+| Poor product description | E-commerce / Content team |
+| Sizing issue | Merchandise / Product development |
+| Customer changed mind | Cost of doing business (absorbed by margin model) |
+| Fraud | Loss prevention budget |
diff --git a/web-app/public/skills/returns-reverse-logistics/references/edge-cases.md b/web-app/public/skills/returns-reverse-logistics/references/edge-cases.md
new file mode 100644
index 00000000..1deeb656
--- /dev/null
+++ b/web-app/public/skills/returns-reverse-logistics/references/edge-cases.md
@@ -0,0 +1,635 @@
+# Returns & Reverse Logistics — Edge Cases Reference
+
+> Tier 3 reference. Load on demand when handling complex or ambiguous return situations that don't resolve through standard workflows.
+
+These edge cases represent the scenarios that separate experienced returns operations managers from everyone else. Each involves competing interests, ambiguous liability, policy grey areas, and real financial or regulatory exposure. They are structured to guide resolution when standard playbooks break down.
+
+---
+
+## How to Use This File
+
+When a return situation doesn't fit a clean category — when policy intent conflicts with policy letter, when fraud indicators coexist with legitimate behaviour, or when the financial or regulatory exposure justifies deeper analysis — find the edge case below that most closely matches the situation. Follow the expert approach step by step. Document your reasoning; these are the cases that generate customer escalations, chargeback disputes, and compliance questions.
+
+---
+
+### Edge Case 1: High-Value Electronics with Firmware Wiped but Extensive Hardware Use Evidence
+
+**Situation:**
+A customer returns a MacBook Pro (retail $2,499) within the 15-day electronics return window claiming "not what I expected." The unit arrives in original packaging with all accessories. A visual inspection gives it Grade A — no cosmetic defects. However, during functional testing, the technician notices: the laptop has been factory-reset (no user data), but the battery cycle count reads 147 (a new unit would have 1-5 cycles from factory QA). The SSD health shows 2.3 TB of total data written. The serial number matches the sold unit. The customer's account is in good standing with $12,000 in lifetime purchases and a 14% return rate.
+
+**Why It's Tricky:**
+The customer is technically within the return window. The product appears "like new" on the surface. But 147 battery cycles represents approximately 4-6 months of typical daily use — far more than the 12 days since delivery. The most likely explanation: the customer bought a new MacBook, swapped the firmware/data to the new unit, and is returning their old MacBook of the same model in the new unit's box. However, the serial number matches, which rules out a physical swap of the entire machine. This suggests the customer simply used the product very heavily for 12 days (possible for a power user or if the customer was migrating data from an old system) OR the battery cycle counter has an anomaly.
+
+The policy says accept within 15 days. The physical evidence suggests this wasn't a brief trial. The customer is valuable. The Apple ecosystem makes serial number verification reliable.
+
+**Common Mistake:**
+Accepting the return at face value because it's within the window and the serial matches, then restocking as Grade A. The 147 battery cycles mean this is a Grade B at best — battery health is already degraded 3-5% from the cycling, and the SSD wear is real. Restocking it as new and selling it to the next customer creates a product quality issue.
+
+The other common mistake: accusing the customer of fraud. The evidence is suggestive but not conclusive. A content creator who downloaded, edited, and uploaded 2 TB of video in 12 days would have a legitimate use pattern.
+
+**Expert Approach:**
+1. Accept the return — the customer is within the policy window and the serial matches. Do not deny.
+2. Grade the unit as B, not A. The battery cycle count and SSD wear are objective quality indicators. Document both with screenshots of the diagnostic tool output.
+3. Refund the customer in full — the 15-day window does not have a condition requirement beyond "original packaging and accessories," which is met.
+4. Route the unit to "open box" or certified refurbished channel, not back to new inventory. Price at 80-85% of retail.
+5. Add a data point to the customer's return profile: "high-use return within window." This is not a fraud flag — it's an intelligence flag. If a pattern emerges across multiple high-value electronics returns, the fraud scoring model will accumulate the signal naturally.
+6. Do NOT apply a restocking fee. The product was returned within the standard window with all accessories. Applying a fee because of battery wear during a 12-day period creates a customer experience problem that costs more than the margin lost on the Grade B vs Grade A disposition.
+7. Review the product listing: does it offer a trial or satisfaction guarantee that implicitly invites heavy use? If so, this return is within the spirit of the policy.
+
+**Key Indicators:**
+- Battery cycle count > 50 within a 15-day return window is an anomaly worth documenting
+- SSD write volume > 500 GB suggests more than casual testing
+- Factory reset before return is not suspicious in itself (privacy-conscious customer behaviour) but combined with high-use indicators, it's a data point
+- Serial number match is critical — if it mismatches, this is swap fraud, not an edge case
+
+---
+
+### Edge Case 2: Hazmat Return with Improper Packaging
+
+**Situation:**
+A customer initiates a return for a cordless power tool kit that includes two lithium-ion batteries (each 5.0 Ah, 20V = 100 Wh per battery). The customer packed the tool, batteries, and charger loose in a standard cardboard box with crumpled newspaper as packing material. The return label was generated through the automated RMA portal, which issued a standard ground shipping label. The parcel is picked up by the carrier. Two days later, the carrier's hazmat compliance team intercepts the package at a sort facility, flags it as a non-compliant lithium battery shipment (no Class 9 labelling, no battery-handling marks, batteries not individually protected against short circuit), and imposes a $500 hazmat violation penalty on your company's shipping account.
+
+**Why It's Tricky:**
+Lithium-ion batteries over 100 Wh require Special Provision 188 compliance under IATA DGR and 49 CFR §173.185 for ground transport. Even under the 100 Wh threshold, UN 3481 (lithium ion batteries packed with equipment) requires the battery terminals to be protected against short circuit and the package to be marked with the lithium battery handling mark. The customer didn't know any of this — they packed their return the way they'd pack any product. The automated RMA system didn't flag the product as requiring special return packaging because the product master data doesn't have a "contains lithium batteries" attribute that triggers special handling.
+
+You now have a $500 carrier penalty, a product in limbo at a carrier facility, a customer who expects a refund, and a systemic gap in your returns process.
+
+**Common Mistake:**
+Blaming the customer or refusing the return because the item was improperly packaged. The customer had no way of knowing the packaging requirements. The system generated a standard return label — the customer followed the instructions given. This is an internal process failure, not a customer failure.
+
+The second mistake: asking the customer to go buy proper hazmat packaging materials and re-ship. This is unreasonable for a consumer return. You would never ask this.
+
+**Expert Approach:**
+1. Contact the carrier's hazmat compliance team immediately. Determine the status of the package — is it being held, returned to the customer, or destroyed? Negotiate the penalty: first offence with an account in good standing may be reduced to a warning. If not, the $500 is a cost of the process gap.
+2. Arrange for the package to be returned to the customer (if not already). Do NOT ask the carrier to forward it — it's non-compliant, and re-shipping it in the same packaging compounds the violation.
+3. Send the customer a proper return kit: a UN-rated box with battery terminal protectors, lithium battery handling labels, and clear instructions. Include a pre-paid hazmat-rated shipping label (GROUND ONLY — lithium batteries over 100 Wh cannot ship by air via standard return channels). Cost: $15-25 for the kit plus $20-35 for the hazmat-rated label.
+4. Process the refund upon receipt at your facility. Do not delay the refund because of the packaging issue — this was your process failure.
+5. Systemic fix: flag all products containing lithium batteries > 20 Wh in the product master data. When a return is initiated for these products, suppress the standard return label and instead trigger the special return kit shipment. This costs $35-60 per return but eliminates the $500+ violation risk.
+6. Absorb the carrier penalty internally. Do not pass it to the customer. Charge it to the process improvement budget.
+
+**Key Indicators:**
+- Products containing lithium-ion batteries > 100 Wh (or containing multiple batteries where the sum exceeds 100 Wh) require UN 3481 packaging for return shipping
+- Carrier hazmat violations range from $500 to $50,000+ depending on severity and history
+- The systemic cost of not having a hazmat return process is: (number of battery-containing returns per year) × (probability of carrier interception) × (average penalty) — for most retailers, implementing the proper process is cheaper within the first year
+
+---
+
+### Edge Case 3: Cross-Border Return with Duty Drawback Implications
+
+**Situation:**
+A Canadian customer purchased a $1,200 designer handbag from your US-based e-commerce site. The product was shipped from your US warehouse to Toronto. Canadian customs assessed 18% duty ($216) plus 13% HST ($184.08) on the customer at import, for a total of $400.08 in import charges paid by the customer. The customer now wants to return the handbag (it's the wrong colour — their order specified "cognac" but the product listing photo and actual product colour differ under different lighting). They want a full refund including the import duties they paid. The handbag is in perfect Grade A condition.
+
+**Why It's Tricky:**
+Three financial flows are entangled:
+1. The product price ($1,200) — refundable through your normal return process
+2. The Canadian import duty ($216) — reclaimable by the customer through CBSA (Canada Border Services Agency) casual refund process or by you through a duty drawback claim if the product is re-exported
+3. The HST ($184.08) — reclaimable by the customer through a CBSA B2G form
+
+The customer expects you to refund the full $1,600.08. But you only collected $1,200 — the duties and taxes were collected by Canadian customs, not by you. You can refund what you collected, but the $400.08 in duties/taxes must be recovered through the customs process.
+
+Complicating factors: the customer doesn't know how to file a CBSA casual refund. The duty drawback requires the handbag to be re-exported from Canada within specific timelines. Return shipping from Canada to the US requires a commercial invoice and customs declaration for the returned goods. And the return shipping cost ($45-80 for a tracked cross-border return) may be a point of contention — who pays?
+
+**Common Mistake:**
+Refunding the customer $1,600.08 to "make it right" without understanding that the $400.08 in duties/taxes can be recovered from CBSA, effectively eating $400 that isn't yours to eat. This seems customer-friendly but is financially illiterate — it means you're paying the Canadian government's duty for the customer.
+
+The second mistake: telling the customer "duties are your responsibility" and only refunding $1,200. While technically true, this is a fulfilment error (wrong colour due to misleading product photo), which changes the obligation calculus. A customer who received the wrong colour should be made whole.
+
+**Expert Approach:**
+1. Acknowledge the fulfilment error. This was your product photo misrepresentation, not buyer's remorse. This changes the return from "standard" to "seller-fault."
+2. Refund the $1,200 product price immediately upon return receipt. This is your standard process.
+3. For the $400.08 in duties/taxes: provide the customer with step-by-step instructions for filing a CBSA casual refund claim (Form B2, with the returned-goods receipt as documentation). Most casual refund claims are processed in 4-8 weeks.
+4. Because this is a seller-fault return, cover the return shipping cost. Provide a prepaid cross-border return label. Ensure the label includes proper customs documentation (commercial invoice marked "RETURNED GOODS — NO COMMERCIAL VALUE" with original export reference).
+5. As a goodwill gesture for the inconvenience (wrong colour + cross-border return hassle), offer a $50-100 store credit. This costs less than refunding $400 in duties you didn't collect.
+6. If the customer insists on immediate full reimbursement of the duties: evaluate the customer's LTV and the competitive cost of losing them. For a first-time international customer, the $400 goodwill refund may be justified if the customer's potential LTV exceeds $2,000. For a one-time buyer, provide the CBSA refund instructions and hold firm on the product refund only.
+7. File your own duty drawback claim (if applicable) for the import duty that was assessed when you originally exported the goods. US duty drawback under 19 USC §1313 allows recovery of 99% of duties paid on exported goods that are returned, within 5 years. This requires the original export documentation.
+
+**Key Indicators:**
+- Cross-border returns always involve at least three financial streams: product price, import duty, and sales/value-added tax
+- The customer paid the duties, not you — refunding duties you didn't collect is a cost that should only be incurred as a deliberate customer recovery decision, not a default
+- CBSA casual refund claims require proof that the goods were re-exported; the customer needs the return tracking number showing the package crossed back into the US
+- Return shipping customs declarations for returned goods should use HS code 9801 (US) or tariff item 9813 (Canada) to avoid re-assessment of duties on the returned product
+
+---
+
+### Edge Case 4: Influencer Bulk Return Post-Content-Creation
+
+**Situation:**
+A social media influencer with 850K Instagram followers and a fashion/lifestyle brand placed an order for 24 items totalling $3,200 (mix of apparel, accessories, and shoes). The order was placed 18 days ago, delivered 15 days ago. The influencer has since posted 4 Instagram Reels and 2 TikTok videos featuring 22 of the 24 items in styled outfits, "haul" content, and "try-on" format. The videos collectively have 2.1 million views. The influencer now initiates a return for 22 of the 24 items (keeping 2 items worth $180), claiming "didn't fit" and "not as expected" for the various items. All items are within the 30-day return window.
+
+The returned items arrive and inspection reveals: 16 items are Grade A (tags on, no wear signs), 4 items are Grade B (tags removed, minor wear indicators — one dress has foundation on the collar), and 2 items are Grade C (visible wear, one pair of shoes shows outdoor sole wear).
+
+**Why It's Tricky:**
+The customer technically complied with the return policy — the items are within the 30-day window, and the stated return reasons are among the accepted reasons. The influencer extracted significant brand value (2.1M views of organic-looking content featuring your products) without paying for it. The cost of equivalent paid influencer content at her follower count would be $5,000-15,000.
+
+But there's no "you used our products for content" clause in the return policy. The influencer didn't sign an agreement. She's a customer exercising her return rights. Refusing the return creates legal risk (she documented that the items were purchased legitimately) and PR risk (an influencer with 850K followers posting about a return denial generates vastly more negative attention than the $3,020 refund).
+
+**Common Mistake:**
+Refusing the return or charging punitive restocking fees on all 22 items. This triggers a "brand vs influencer" public dispute that costs far more than $3,020 in brand damage. The second mistake: passively accepting the return and learning nothing — the same influencer (or others) will repeat this pattern.
+
+**Expert Approach:**
+1. Process the return. Accept all 22 items. Grade them honestly:
+ - 16 items Grade A: restock as new. Full refund on these items.
+ - 4 items Grade B: refund in full (tags removed isn't grounds for denial within the return window for apparel). Route to open-box/outlet.
+ - 2 items Grade C: refund in full minus restocking fee on the shoes with outdoor wear (visible use beyond trying on). The dress with foundation gets full refund — cosmetic transfer during try-on is expected.
+2. Apply the restocking fee to the worn shoes only. Explain: "We've processed your return. 21 items received a full refund. The [shoe name] showed wear beyond trying on, so a 15% restocking fee of $X was applied per our return policy."
+3. Separately, refer this case to the marketing/brand partnerships team. The influencer generated $5,000-15,000 in equivalent media value. The business-smart play is to convert her from a "free content via returns" customer to a paid brand ambassador. Reach out with: "We loved how you styled our pieces. We'd like to discuss a collaboration."
+4. Add a note to the customer's profile for future monitoring. If this pattern repeats (bulk purchase → content → bulk return), the fraud scoring model will accumulate points naturally. If she becomes a brand ambassador, the returns stop being a problem.
+5. Systemic: consider a "content creator" return policy that offers extended exchange/store credit windows for influencers who tag the brand, in exchange for a no-return-for-refund agreement on items used in content. This requires marketing/legal collaboration.
+
+**Key Indicators:**
+- Bulk orders from accounts with high social media followings, followed by near-complete returns, is an emerging pattern that existing return policies don't address
+- The refund cost ($3,020) is almost always less than the negative PR cost of a public denial
+- Marketing value of the content may exceed the refund cost, making this a net positive event if handled strategically
+- Restocking fees should only apply to items with objective condition defects, not as punishment for the pattern
+
+---
+
+### Edge Case 5: Warranty Claim on Product Modified by Customer
+
+**Situation:**
+A customer purchased a gaming laptop ($1,899) 14 months ago and is filing a warranty claim because the display has developed a persistent flickering issue that makes the laptop unusable. During inspection, the technician discovers that the customer has upgraded the RAM from the factory-installed 16 GB to 32 GB using third-party RAM modules. The RAM upgrade is clearly visible (different brand module in the second DIMM slot). The laptop's warranty is 24 months from purchase. The manufacturer's warranty terms state: "Warranty is void if the product has been modified, altered, or repaired by anyone other than an authorised service centre."
+
+The customer's position: "I upgraded the RAM, not the display. The RAM has nothing to do with the screen flickering. The warranty should cover the display." The manufacturer's position: "Any modification voids the entire warranty."
+
+**Why It's Tricky:**
+The customer's logic is reasonable. RAM and display are independent subsystems. A RAM upgrade almost certainly didn't cause display flickering (which is typically a cable, inverter, or GPU issue). However, the manufacturer's warranty language is broad — "any modification" voids the warranty. Legally (under Magnuson-Moss Warranty Act in the US), a warranty provider cannot void a warranty for using third-party parts unless the warrantor can demonstrate that the third-party part caused the defect being claimed. The "void if modified" clause is likely unenforceable for unrelated modifications, but most customers don't know this, and challenging it requires escalation.
+
+As the retailer, you're caught between the customer (who expects you to facilitate the warranty claim) and the manufacturer (who will deny it based on the modification). Your extended warranty (if sold) may have similar language.
+
+**Common Mistake:**
+Denying the warranty claim outright because "the product was modified." This is both legally questionable (Magnuson-Moss) and customer-hostile. The customer's modification was a routine, widely-documented upgrade that the laptop was designed to support (user-accessible RAM slot).
+
+The second mistake: accepting the claim and eating the repair cost without pursuing the manufacturer. The display defect is a manufacturing quality issue, not a retail liability.
+
+**Expert Approach:**
+1. Accept the laptop for evaluation. Do NOT deny at the point of customer contact. Tell the customer: "We'll inspect the display issue and submit the warranty claim to the manufacturer."
+2. Document the modification (photographs of the third-party RAM) and the defect (video of display flickering). Test the display issue with and without the third-party RAM installed — if the flickering persists with original RAM configuration, the modification is demonstrably unrelated to the defect.
+3. Submit the warranty claim to the manufacturer with the documentation. Include: the defect evidence, the modification documentation, and a note stating that the modification is unrelated to the claimed defect per Magnuson-Moss Warranty Act provisions.
+4. If the manufacturer denies: escalate to the manufacturer's warranty dispute resolution process. Cite 15 USC §2302(c) — a warrantor may not condition warranty coverage on the use of a specific article unless the article is provided free of charge. The customer's use of third-party RAM is protected.
+5. If the manufacturer continues to deny: evaluate the repair cost. A display cable replacement is typically $50-150 in parts and labour. If you have an in-house repair capability, consider performing the repair and pursuing the manufacturer for reimbursement. The customer gets a working laptop, you maintain the relationship, and you have a legitimate claim against the manufacturer.
+6. If an extended warranty was sold: check the extended warranty terms carefully. Third-party extended warranties (Allstate, Asurion) have their own modification clauses that may differ from the manufacturer's. If the extended warranty covers it, file against the warranty provider instead.
+7. Communicate progress to the customer at each stage. The worst outcome is silence during a warranty claim.
+
+**Key Indicators:**
+- Magnuson-Moss Warranty Act (15 USC §2301-2312) prohibits warranty void clauses based on the use of third-party parts unless the warrantor proves the part caused the defect
+- FTC enforcement of Magnuson-Moss has increased in recent years, making "void if modified" stickers largely unenforceable
+- Common user modifications that should not void unrelated warranty claims: RAM upgrades, storage drive replacements, adding peripherals, installing aftermarket cases/screen protectors
+- Modifications that may legitimately void related warranty claims: CPU/GPU overclocking (thermal damage), software rooting/jailbreaking (software defects), physical modifications to cooling systems (overheating)
+
+---
+
+### Edge Case 6: Serial Returner Who Is Also a High-Value Customer
+
+**Situation:**
+Customer "Elena M." has a 3-year purchase history totalling $82,000 in gross purchases. She shops primarily in premium apparel, shoes, and accessories. Her return rate is 42% — she has returned $34,440 in product over the same period. Her net revenue after returns is $47,560. Her average order value is $680, and she typically orders 3-5 items per order, keeps 2-3, and returns 1-2. Her return reasons are consistently "didn't fit" or "not what I expected." Returned items are almost always Grade A. She has never returned a used or damaged item. She is a member of your top-tier loyalty programme.
+
+Your fraud detection system has flagged her with a score of 68 (above the 65-point review threshold) due to her return rate, volume, and frequency. The system recommends a refund hold pending review.
+
+**Why It's Tricky:**
+Elena is bracket-shopping — buying multiple items knowing she'll return some. This is not fraud. It's a legitimate (if expensive) shopping behaviour that high-end retail has dealt with for decades. Her 42% return rate is high, but her $47,560 net revenue over 3 years places her in your top 2% of customers by net value. Her returns are Grade A, meaning the disposition cost is minimal (restock as new). The actual cost of her returns is: return processing at ~$7 per return × approximately 150 returns = $1,050 in processing costs over 3 years. That's negligible against $47,560 in net revenue.
+
+Putting a hold on her refund will damage a relationship worth ~$16,000/year in net revenue. But your fraud system flagged her, and ignoring the system creates process precedent.
+
+**Common Mistake:**
+Enforcing the fraud hold. Treating Elena like a fraud suspect — even temporarily — risks losing a customer whose LTV is in the top 2%. The fraud scoring system is correctly identifying a signal (high return rate) but incorrectly interpreting it as fraud risk.
+
+The second mistake: exempting her from the fraud system permanently. This creates a loophole that actual fraudsters could exploit if they know that high spend protects them.
+
+**Expert Approach:**
+1. Override the fraud hold immediately. Process Elena's return normally. The override is justified by: positive net LTV (top 2%), Grade A return condition (no cost indication of fraud), consistent behaviour over 3 years (not a new pattern), and return reasons consistent with bracket shopping.
+2. Add a "VIP override" annotation to her customer profile. This allows the fraud system to continue monitoring her behaviour (important if her pattern changes to something genuinely fraudulent) while preventing friction on her normal returns.
+3. Set a review trigger for pattern deviation. If Elena's return rate exceeds 60%, or if returned item condition drops below Grade A, or if she starts returning items from new categories (electronics, high-shrink), the override should be suspended and a human review triggered.
+4. Share the case (anonymised) with the fraud model team as a false-positive calibration data point. The model should receive a negative adjustment for the LTV-to-return-rate interaction: customers with high net LTV and Grade A returns should have their base scores reduced.
+5. Consider proactive outreach through the personal shopping or styling team. Elena's bracket shopping suggests she'd benefit from virtual styling, improved size recommendation tools, or early access to try-on programmes. Converting her from a bracket shopper to a targeted shopper reduces return volume while preserving revenue.
+6. Do NOT restrict her return privileges, adjust her return window, or impose restocking fees. The ROI calculation is unambiguous: $16K/year net revenue versus $350/year in return processing costs. The returns are a cost of doing business with a high-value customer.
+
+**Key Indicators:**
+- Return rate alone is not a fraud indicator. Return rate must be contextualised with: net LTV, return condition, behaviour consistency, and return reason patterns.
+- The fraud scoring model should include an LTV offset that reduces scores for customers with positive net LTV. The current model doesn't weight this strongly enough.
+- Bracket shopping is most common in: premium apparel (multiple sizes), shoes (half-size uncertainty), and accessories (colour matching). Categories where in-person evaluation matters.
+- Industry benchmark: luxury e-commerce return rates of 30-40% are normal. The 42% rate is slightly high but not anomalous for the category.
+
+---
+
+### Edge Case 7: Return of a Recalled Product
+
+**Situation:**
+A customer brings a portable space heater to the store for a return, stating "it doesn't work properly and I'm scared it's going to start a fire." The receipt shows purchase 45 days ago (outside the 30-day return window). During the intake process, the associate scans the product barcode and the system matches it to an active CPSC (Consumer Product Safety Commission) recall issued 10 days ago due to a fire hazard from a faulty thermostat. The recall notice instructs consumers to "immediately stop using the product and contact [manufacturer] for a full refund or replacement."
+
+**Why It's Tricky:**
+This is not a return — it's a recall. But the customer came to your store expecting a return process, not a recall process. The recalled product cannot enter your standard returns inventory (it's a safety hazard). It cannot be restocked, liquidated, donated, or disposed of through normal channels — recalled products have specific disposition requirements. But the customer is standing in front of you wanting a resolution now, and telling them "go contact the manufacturer" feels like you're passing the buck.
+
+Additionally: the product is outside the return window, so the standard return system would deny it. The recall overrides the return policy, but the standard return system may not know that. If the associate processes it as a "return," the recalled unit could end up in general returns inventory and eventually be restocked or liquidated — both of which create safety and legal liability.
+
+**Common Mistake:**
+Processing it as a standard return. This puts a recalled product into the returns stream where it may be restocked or liquidated, creating enormous liability. Even if it's "disposed of," standard disposal doesn't include the CPSC reporting requirements for recalled product destruction.
+
+The second mistake: refusing the return because it's outside the 30-day window and telling the customer to contact the manufacturer. You sold them a product that's now subject to a safety recall. Directing them elsewhere damages trust and may create legal exposure under state consumer protection laws.
+
+**Expert Approach:**
+1. The associate should STOP the standard return process. This is a recall, not a return. Do not issue a refund through the POS return function.
+2. Accept the product from the customer. Issue a full refund at the original purchase price as a "recall accommodation" — most POS systems have a separate recall/safety return code. If not, process as a defective return with a manager override for the window, and add a note "RECALLED PRODUCT — DO NOT RESTOCK."
+3. Physically segregate the product immediately. Place it in the recall quarantine area (not the general returns staging area). Affix a "RECALLED — DO NOT PROCESS" label.
+4. Log the recall return in the recall tracking system (or spreadsheet if no system exists) with: date, customer name, serial number, lot number, store location, CPSC recall number.
+5. Follow the manufacturer's recall instructions for retailer-held inventory. Typically: hold until manufacturer arranges pickup or provides destruction instructions with certificate-of-destruction requirements.
+6. Report the return to the recall coordinator. The recall coordinator aggregates data for CPSC reporting requirements (firms involved in recalls must maintain records of corrective actions).
+7. Check your remaining inventory (stores + warehouse) for the same product. If any units are still in sellable inventory, pull them immediately. This is a legal obligation once you're aware of the recall.
+8. If the customer purchased other products from the recalled brand, consider proactively checking those against recall databases as a goodwill gesture.
+
+**Key Indicators:**
+- Recalled products MUST NOT enter the standard returns stream. The disposition for recalled products is determined by the recall notice, not by your normal disposition tree.
+- CPSC recall compliance is not optional. Failure to segregate and properly handle recalled products can result in penalties up to $100,000 per violation under the Consumer Product Safety Act.
+- The refund to the customer is ultimately the manufacturer's financial responsibility. Process the refund to the customer immediately and pursue reimbursement from the manufacturer through the recall programme.
+- Some recalls are "voluntary" (manufacturer-initiated) and some are mandatory (CPSC-ordered). The retailer's obligation is the same in both cases.
+
+---
+
+### Edge Case 8: Gift Receipt Return at Higher Current Price
+
+**Situation:**
+A customer presents a gift receipt for a premium blender purchased by the gift-giver 6 weeks ago for $279.99. The blender is currently selling for $309.99 (price was increased 2 weeks ago due to a supplier cost increase). The customer wants to return the blender for store credit. The gift receipt shows the $279.99 purchase price but the customer is looking at the shelf tag showing $309.99.
+
+**Why It's Tricky:**
+Gift receipt policy typically states "refund at purchase price to store credit." This is clear. But the customer sees a $30 discrepancy and may interpret the gift receipt as entitling them to the current value of the product. If you issue store credit for $279.99 and the customer wants to "exchange" for the same blender (maybe in a different colour), they'd need to pay $30 out of pocket for the exact same product — which feels absurd from a customer perspective.
+
+The reverse scenario is more common and more dangerous: gift receipt return when the price has dropped. Gift-giver paid $279.99, current price is $229.99, and the gift recipient gets $279.99 in store credit — effectively profiting $50. This is a known return arbitrage vector.
+
+**Common Mistake:**
+Issuing store credit at the current (higher) price to avoid the awkward conversation. This creates a $30 loss and, more importantly, establishes a precedent that gift receipt returns get current-price value. During seasonal markdowns (post-holiday), this policy would be exploited systematically.
+
+**Expert Approach:**
+1. Issue store credit at the documented purchase price ($279.99). This is the policy and the financially correct answer.
+2. If the customer wants to exchange for the same product at $309.99, offer to process it as even exchange at the original purchase price (no additional charge). This is an exchange, not a return-and-repurchase. The $30 price difference is absorbed as goodwill.
+3. If the customer wants a refund (store credit) and will buy a different product, the store credit amount is $279.99. They can use it toward any purchase.
+4. If the customer objects to the $279.99 amount: explain calmly that gift receipts reflect the purchase price, which protects gift-givers' privacy (the gift-giver doesn't want the recipient to know they paid less than current price) and ensures accurate accounting. Most customers accept this explanation.
+5. Never issue store credit above the documented purchase price unless a manager explicitly authorises it as a one-time customer accommodation, documented in the transaction notes.
+
+**Key Indicators:**
+- Gift receipt store credit should always be at the lower of: purchase price or current selling price. This protects against both upward and downward price arbitrage.
+- An exception for even-exchange at original price (same item, different colour/size) is operationally clean and customer-friendly.
+- Track gift receipt returns during post-holiday markdown periods. A spike in gift-receipt returns when prices drop is an arbitrage signal.
+
+---
+
+### Edge Case 9: Cross-Channel Return Where Online Price Differs from Store Price
+
+**Situation:**
+A customer purchased a stand mixer online for $249.99 during a flash sale (regular online price is $329.99, regular store price is $349.99). The customer wants to return it in-store. The store's return system pulls the current store price ($349.99) because the online flash sale price is not visible in the store's POS. If the associate processes the return at store price, the customer receives a $100 windfall.
+
+**Why It's Tricky:**
+Omnichannel systems often have pricing discrepancies between channels. Online pricing is dynamic (flash sales, personalised pricing, coupon codes), while store pricing updates on a different cadence. The return system may not have visibility into the customer's actual purchase price, only the current store price for the SKU.
+
+**Common Mistake:**
+Processing the return at the store POS price ($349.99). This is a $100 overpayment that, at scale, represents significant financial leakage. Cross-channel return price arbitrage is a known fraud vector — buy online at the lowest price, return in-store at the higher price.
+
+**Expert Approach:**
+1. Look up the original order. Use the customer's email, order number, or loyalty account to pull the actual purchase price. The refund amount should match the actual amount paid ($249.99), not the current store price.
+2. If the order lookup system isn't available in-store (system limitation), ask the customer for their order confirmation email. Most customers have this accessible on their phone.
+3. If no order verification is possible: refund to the original payment method only. This ensures the refund goes back to the card that was charged $249.99 — the payment processor will reconcile to the actual charge amount regardless of what the POS tries to refund. If the POS attempts to refund $349.99 to a card that was only charged $249.99, the processor should limit the refund to the charged amount (though not all processors do this reliably).
+4. Never issue a cash or store credit refund for an online purchase returned in-store without verifying the actual purchase price. Cash and store credit bypass the payment processor safeguard.
+5. Systemic fix: ensure the in-store return system queries the online order management system for the actual purchase price before processing any BORIS (buy online, return in store) return. This is table-stakes omnichannel operations.
+
+**Key Indicators:**
+- Cross-channel return price discrepancy is one of the top 3 sources of return-related financial leakage in omnichannel retail
+- Always refund to original payment method for cross-channel returns (prevents price-arbitrage via store credit)
+- The POS system should display the actual purchase price from the original order, not the current store price, for all cross-channel returns
+- Audit cross-channel returns monthly for price discrepancy patterns
+
+---
+
+### Edge Case 10: Counterfeit Product Discovered in Return Stream
+
+**Situation:**
+A customer returns a "Dyson V15 Detect" cordless vacuum (retail $749.99) claiming it stopped working after 2 weeks. During inspection, the returns technician notices subtle differences from a genuine Dyson V15: the weight is slightly off (lighter by 200g), the laser dust-detection head has a different LED colour temperature, the serial number format doesn't match Dyson's standard format, and the packaging — while high quality — has a slightly different font on the warranty card. The technician suspects this is a counterfeit. The customer purchased the unit from your marketplace platform through a third-party seller, "EliteTech Solutions," who has 4.2 stars and 2,300 reviews.
+
+**Why It's Tricky:**
+If this is counterfeit, multiple problems converge. The customer is a victim — they paid $749.99 for a fake product. The marketplace seller may be knowingly selling counterfeits, or may themselves have been deceived by their supply chain. Dyson has an aggressive brand protection programme and may pursue legal action against the marketplace. The counterfeit unit cannot be returned to the seller, restocked, liquidated, or disposed of through normal channels — it's illegal goods. And you need to determine whether this is an isolated incident or evidence of a systematic counterfeiting operation on your marketplace.
+
+**Common Mistake:**
+Processing the return as a standard defective return, issuing a refund, and putting the counterfeit unit back into the returns stream where it may eventually be liquidated and re-enter the market. This creates trademark liability.
+
+The second mistake: accusing the customer of returning a counterfeit (implying they're running a swap scam). The customer may genuinely be a victim.
+
+**Expert Approach:**
+1. Accept the product from the customer. Issue a full refund immediately. Do NOT make the customer wait for an investigation. They paid for a genuine product and received a counterfeit — they are the victim.
+2. Quarantine the product. Label it "SUSPECTED COUNTERFEIT — DO NOT PROCESS." Photograph extensively: every angle, labels, serial numbers, packaging, weight, and the specific indicators that raised suspicion.
+3. Notify Brand Protection / Loss Prevention immediately. Provide the photographs and inspection findings.
+4. Brand Protection should contact Dyson's brand protection team to confirm the counterfeit determination. Dyson will want the unit for forensic analysis. Provide it under a chain-of-custody document.
+5. Suspend the marketplace seller (EliteTech Solutions) pending investigation. Pull all active listings. Review their other product listings for similar brand-name products that may also be counterfeit.
+6. Review all recent orders from EliteTech Solutions for the same product. Contact those customers proactively: "We're conducting a quality review of a product you purchased. We'd like to offer you a free inspection and, if needed, a replacement or full refund."
+7. Do NOT destroy the counterfeit unit — it's evidence. The brand owner and potentially law enforcement will need it.
+8. If the investigation confirms systematic counterfeiting: permanently ban the seller, report to the appropriate authorities (FBI for trademark counterfeiting, CBP if the goods were imported), cooperate with the brand owner's legal team, and notify all affected customers.
+
+**Key Indicators:**
+- Weight discrepancy is one of the most reliable first indicators of counterfeits — counterfeiters rarely match the exact weight of genuine products
+- Serial number format mismatches are definitive when confirmed by the brand owner
+- Counterfeit products found in the return stream often indicate a larger supply chain problem, not an isolated incident
+- Marketplace liability for counterfeit goods is an evolving legal area (INFORM Consumers Act, SHOP SAFE Act) — document everything for legal protection
+- Never liquidate, donate, or return suspected counterfeit goods to any channel. The legal liability is unlimited.
+
+---
+
+### Edge Case 11: Simultaneous Return and Chargeback — Double-Refund Risk
+
+**Situation:**
+A customer purchases a high-end espresso machine ($849.99) and initiates an online return 18 days after delivery, citing "machine makes grinding noise during extraction." The RMA is approved and a prepaid return label is generated. Two days later — before the customer has shipped the return — the payments team receives a chargeback notification from Visa under reason code 13.3 ("Not as Described"). The customer has now created two parallel refund paths for the same $849.99 transaction.
+
+**Why It's Tricky:**
+If both processes complete independently, the customer receives $1,699.98 — a double refund. The return process would refund $849.99 upon receipt and inspection. The chargeback process, if not contested, would refund $849.99 through the card network. Payments teams and returns teams often operate in separate systems with no automatic cross-check. The customer may be deliberately exploiting this gap, or they may genuinely not understand that a chargeback and a return are separate mechanisms (surprisingly common — many customers file chargebacks when they get frustrated waiting for a return label, not understanding they've initiated a second refund process).
+
+The chargeback has regulatory timelines: Visa requires the merchant to respond within 20 days or the chargeback auto-closes in the cardholder's favour. The return has no such external deadline. This asymmetry means the chargeback demands attention first.
+
+**Common Mistake:**
+Processing the return refund without checking for an active chargeback. This is the #1 source of double-refund losses in e-commerce. The second mistake: immediately assuming fraud and antagonising a customer who may simply be confused about the process.
+
+**Expert Approach:**
+1. HALT the RMA process immediately. Add a "chargeback hold" flag to the RMA. Do not process a return refund while a chargeback is active.
+2. Contact the customer within 24 hours. Use neutral, helpful language: "We received your return request and also noticed a dispute was filed with your bank for the same order. We'd like to help resolve this through whichever channel is easiest for you. If you'd prefer to proceed with the return (which typically resolves faster), could you ask your bank to withdraw the dispute? Or if you'd prefer to resolve through your bank, we can cancel the return. We just need to use one process to avoid delays." This gives the customer a face-saving way to resolve.
+3. If the customer agrees to withdraw the chargeback: get confirmation in writing (email reply is sufficient), then proceed with normal return processing. Keep the chargeback response prepared — if the bank doesn't actually withdraw, you need the evidence.
+4. Respond to the chargeback regardless: within the 20-day window, submit a response to Visa with: proof of delivery, product description matching the listing, evidence of the open RMA (showing you were actively resolving the customer's complaint through the return channel), and the customer's communication agreeing to resolve via return. This protects you if the chargeback isn't actually withdrawn.
+5. If the customer doesn't respond or insists on both: treat as potential fraud. The chargeback takes priority (regulatory timeline). Fight the chargeback with evidence. Cancel the RMA. If the customer then ships the product back on the old label, process as an unsolicited return — accept the product but do not issue a refund (the chargeback is the refund mechanism).
+
+**Key Indicators:**
+- Simultaneous return + chargeback is a known fraud vector called "double-dipping"
+- It's also a common customer confusion error — about 40-60% of these cases are not intentional fraud
+- The first 24 hours after detecting the overlap are critical — customer contact resolves 70% of cases
+- Cross-reference returns and chargebacks daily. Any payment team / returns team process gap here is a significant financial exposure
+- Track customers who have previously had a return + chargeback overlap, regardless of resolution — a second occurrence significantly increases the fraud probability
+
+**Documentation Required:**
+- Screenshot of both active RMA and active chargeback for the same order
+- Customer communication and response (timestamped)
+- Chargeback response submitted to Visa
+- Final resolution record: which channel was used, was the other cancelled, total refund amount
+
+---
+
+### Edge Case 12: Customer Returns Product Purchased Through Employee Discount Programme
+
+**Situation:**
+A customer returns a 65" Samsung OLED TV ($2,199.99 retail) with a receipt showing the purchase price of $1,319.99 — a 40% employee discount. The employee discount programme is run through a third-party perks platform (Perkspot, CorporatePerks) and is linked to the customer's employer. The customer is returning because "TV has a dead pixel cluster in the upper right quadrant — noticed after 3 days." The return is within the 30-day window. Your standard policy would refund the purchase price ($1,319.99), but the product at full retail restocks at $2,199.99 or resells as open-box at ~$1,760-1,870.
+
+**Why It's Tricky:**
+The employee discount creates a price asymmetry that can be exploited. If the customer receives a cash refund of $1,319.99 but the product restocks at $2,199.99, there's no financial loss. But what if the customer then repurchases through the employee discount again? Or what if an employee discount customer returns a product and a friend buys it as "open box" at $1,760 — effectively getting a better deal through the return channel than the employee discount provides?
+
+The more immediate question: the dead pixel is a legitimate defect. Is this a return (customer exercises their right to return) or a warranty claim (manufacturer defect)? The distinction matters because the return refunds at the employee discount price ($1,319.99), while a warranty claim might provide a replacement at no cost (preserving the employee discount benefit on the new unit).
+
+**Common Mistake:**
+Refunding at retail price ($2,199.99) instead of the employee discount purchase price ($1,319.99). This creates an $880 overpayment and, worse, opens a fraud vector: buy on employee discount, return for retail price, pocket the difference. The second mistake: applying a restocking fee to a defective product (dead pixels are a manufacturing defect, not a customer-fault return).
+
+**Expert Approach:**
+1. Acknowledge the dead pixel defect. This is a manufacturing defect — no restocking fee applies.
+2. Offer the customer a choice: (a) full return and refund at the employee discount purchase price ($1,319.99), or (b) warranty exchange for a replacement unit of the same model at no cost. Clearly explain the option: "Since the TV has a defect, we can either refund your purchase price or exchange it for a new unit. The exchange preserves your original pricing."
+3. Most customers with a 40% discount will prefer the exchange — they get a working TV at the discounted price. The customer benefits more from the exchange ($2,199.99 value for $0 additional cost) than from the refund ($1,319.99 back but now needs to buy a TV again at $1,319.99 or $2,199.99).
+4. If the customer insists on a refund: process at $1,319.99 (the actual purchase price). Do not refund at retail. Refund to original payment method.
+5. Route the defective TV to Samsung for warranty claim (dead pixel clusters are a known panel defect covered under Samsung's warranty). The retailer recovers the wholesale cost ($1,200-1,400 estimated) from Samsung regardless of which option the customer chose.
+6. Flag the transaction in the employee discount programme reporting — perks platforms track return rates by programme member. Excessive returns through discount programmes may indicate fraud (buying discounted, returning for credit, using credit at full value).
+
+**Key Indicators:**
+- Employee discount, military discount, and corporate perks programme returns should ALWAYS refund at the discounted purchase price, never at retail
+- Product defects on discounted purchases should be handled through exchange/warranty rather than return when possible — this preserves the discount benefit for the customer
+- Track return rates by discount programme. An employee discount programme with a 25%+ return rate may be exploited
+- The defective unit's warranty claim goes to the manufacturer regardless of the customer's return channel — always pursue vendor recovery
+
+---
+
+### Edge Case 13: Return of Personalised / Custom-Engraved Product
+
+**Situation:**
+A customer ordered a premium fountain pen (Montblanc Meisterstück, $620.00) with custom engraving ("To David, Love Mom") as a gift. The recipient, David, wants to return it because he already has a Meisterstück and would prefer store credit toward a different pen. The engraving is permanent — it cannot be removed without damaging the pen. The pen is in perfect condition, never used, still in the gift box. The product page stated "Personalised items are final sale and cannot be returned" at the time of purchase, but this notice was in the FAQ section, not at the point of engraving selection in the checkout flow.
+
+**Why It's Tricky:**
+The policy says "final sale." The customer (the gift-giver, "Mom") technically agreed to this by completing the purchase. But the notice was buried in the FAQ, not displayed prominently during the personalisation step of checkout. Consumer protection laws in some states require the return policy to be "conspicuously displayed" at the point of sale. A disclosure buried in the FAQ may not meet the "conspicuous" standard.
+
+The pen is in perfect condition, but the engraving makes it unsellable through any standard channel. It cannot be restocked, sold as open-box, or liquidated — no one wants to buy a pen engraved "To David, Love Mom." The disposition value is effectively $0 (parts/metal recovery only, perhaps $30-50 for the gold nib).
+
+**Common Mistake:**
+Rigidly enforcing the "final sale" policy. While legally defensible if the disclosure was adequate, it's operationally risky: a $620 dispute that reaches a chargeback is expensive to fight, and if the disclosure is found inadequate, the chargeback goes to the cardholder.
+
+The second mistake: accepting the return at full refund as if the engraving doesn't matter. This creates a precedent where customers order personalised items, use them for the event/gift, and return them knowing the "final sale" policy won't be enforced.
+
+**Expert Approach:**
+1. Evaluate the disclosure adequacy. Was "Personalised items are final sale" displayed at the engraving step in checkout, or only in the FAQ? If only in the FAQ, the company has a weak position. If displayed at the engraving selection step, the position is stronger.
+2. Regardless of disclosure, recognise that the gift recipient (David) is not the purchaser and may not have seen any disclosure. His experience is: "I received a gift I can't use, and the store won't help me." This is a customer experience problem even if the policy is sound.
+3. Recommended resolution: offer store credit at 50% of purchase price ($310) as a one-time courtesy. The rationale: the personalisation destroyed the product's resale value, so the full refund cost ($620) is the total cost to the company — there's no recovery. Offering 50% acknowledges both the customer's situation and the company's loss.
+4. If the gift-giver (Mom) contacts you: she has the stronger case since she was the purchaser. If the disclosure was inadequate, offer 75-100% store credit. If adequate, offer 50% and explain.
+5. Systemic fix: add the "final sale" notice directly on the engraving/personalisation UI step, with a checkbox confirmation: "I understand that personalised items cannot be returned or exchanged." This eliminates future ambiguity.
+6. Disposition: the engraved pen has near-zero resale value. If a charity pen collection exists, donate for the tax deduction at fair market value (which may be claimed at a discounted-but-nonzero amount). Otherwise, hold for precious metals recovery if the pen has gold components.
+
+**Key Indicators:**
+- Personalised/custom items should have the "final sale" notice at the point of customisation selection, not just in the FAQ or general return policy
+- Gift recipients of personalised items present a unique challenge — they didn't agree to the policy
+- The cost of a personalised item return is 100% of the purchase price (zero recovery), making even partial credit a significant expense
+- Track personalised item return requests — if they exceed 3% of personalised orders, the disclosure needs improvement
+
+---
+
+### Edge Case 14: Return Attempt on Product Purchased Through Reseller / Unauthorised Channel
+
+**Situation:**
+A customer walks into your brand retail store with a pair of your company's premium running shoes (retail $189.99) claiming they have a stitching defect after 2 weeks of use. The shoes show the defect as described — a seam separation on the toe box. However, when you scan the barcode, there's no matching transaction in your POS system. The customer says they purchased them from an Amazon third-party seller for $139.99. The shoes appear genuine (not counterfeit). The customer argues: "These are YOUR shoes. You should stand behind your product regardless of where I bought them."
+
+**Why It's Tricky:**
+The customer has a point — the product bears your brand, and a stitching defect is a manufacturing quality issue regardless of the retail channel. However, the customer is not your customer — they purchased from an unauthorised reseller. Your return policy covers products purchased from your direct channels (brand stores, website, authorised retailers). Products purchased through unauthorised third-party sellers may be: genuine product diverted from authorised distribution (grey market), returned products resold by a liquidator, or counterfeit (though these appear genuine).
+
+If you accept the return, you're providing warranty-like service for products you didn't sell, and potentially for products that a liquidator already recovered a refund on before reselling. If you refuse, a customer with a defective product carrying your brand walks away angry and tells social media that your brand doesn't stand behind its products.
+
+**Common Mistake:**
+Accepting a full return and refund at retail ($189.99) for a product the customer paid $139.99 for through a different channel. This creates a $50 arbitrage and invites a pattern: buy from cheap reseller, return at brand store for full retail.
+
+**Expert Approach:**
+1. Verify the product is genuine. If your shoes have internal authenticity markers (UV-visible lot codes, specific insole markings, QR codes), check them. If genuine, proceed to step 2. If suspected counterfeit, follow the counterfeit protocol (Edge Case 10).
+2. This is a warranty issue, not a return. The customer is not returning a purchase from your store — they're claiming a manufacturing defect on your branded product. Handle it as a warranty claim, not a return.
+3. Offer a warranty remedy: exchange the defective pair for a new pair of the same model/size from your store inventory. This costs you the wholesale cost (~$85-95) but resolves the customer's issue, protects the brand reputation, and avoids the price arbitrage of a cash refund.
+4. Do NOT offer a cash refund. The customer did not purchase from you. A cash or store credit refund at your retail price creates arbitrage. If the customer insists on a refund, direct them to the seller they purchased from (Amazon third-party seller).
+5. Document the defect for quality purposes. A stitching defect is a manufacturing quality data point regardless of which channel the shoe was sold through. Log the defect against the SKU and lot number.
+6. Consider the long-term: if your brand's products routinely show up in your stores via unauthorised-channel customers with defects, this indicates a distribution control problem. Work with your authorised retailer programme to identify and address grey market diversion.
+
+**Key Indicators:**
+- Products purchased through unauthorised channels should be handled as warranty claims (exchange/repair), not returns (refund)
+- Never offer a cash refund for products not purchased through your direct or authorised channels — this creates a price arbitrage vector
+- Stitching defects, material failures, and construction issues on genuine product are legitimate warranty claims regardless of purchase channel
+- Track the volume of unauthorised-channel warranty claims — high volume indicates distribution leakage
+
+---
+
+### Edge Case 15: Return of Subscription Box Contents
+
+**Situation:**
+A customer subscribed to your premium coffee subscription box ($59.99/month) and received their March delivery containing 3 bags of single-origin coffee (Guatemala, Ethiopia, Sumatra). They want to return the Guatemala and Sumatra bags (2 of 3) because "I only liked the Ethiopian." The bags are sealed and unopened. The customer wants a partial refund of $39.99 (2/3 of the subscription price). Your subscription terms state: "Subscription box contents are curated selections and cannot be returned for partial refund. You may cancel your subscription at any time."
+
+**Why It's Tricky:**
+The subscription model is fundamentally different from à la carte retail. The customer didn't choose these specific coffees — the subscription curated them. The $59.99 price reflects the curated bundle value, not 3 × $19.99 for individual bags. If you allow partial returns on subscription boxes, every subscriber will return the items they don't like, and the subscription model collapses (you'd be selling only the popular items at a discount).
+
+But the customer's request is understandable. They're not asking for something unreasonable — they received products they don't want and they're sealed. From their perspective, it's no different from returning an unwanted product.
+
+**Common Mistake:**
+Allowing the partial return. This sets a precedent that undermines the entire subscription model. If 50% of subscribers return 1-2 items per box, the margin model breaks — subscription boxes are priced with the assumption that the subscriber keeps the full curation.
+
+**Expert Approach:**
+1. Deny the partial return per subscription terms. But frame it as a positive: "Our subscription boxes are curated as a complete experience, and we can't process partial returns. However, we want to make sure you're enjoying every box."
+2. Offer alternatives: (a) "We'd love to know your taste preferences so we can adjust future boxes. Would you prefer lighter, fruitier coffees like the Ethiopian? We can note your preference for the next box." (b) "If you'd like to swap the Guatemala and Sumatra bags, we can offer a one-time exchange for two bags from our Ethiopian selection or other light-roast options." (c) "If the subscription isn't meeting your expectations, we can offer a 15% discount on your next box or switch you to a different subscription tier that focuses on the flavour profiles you prefer."
+3. If the customer insists or threatens to cancel: evaluate the customer's subscription tenure. A customer who has been subscribed for 12+ months at $59.99/month ($720+/year) is worth a one-time $39.99 accommodation. A new subscriber on their first box is not — their expected LTV hasn't been established. For long-tenure subscribers, offer a $20 credit toward their next box as a compromise.
+4. Never refund partial subscription box contents as a standard practice. Every exception must be documented as a one-time accommodation with the business justification.
+5. Systemic improvement: add a taste preference survey to the subscription onboarding. Curating to known preferences reduces "didn't like it" complaints by 30-50%.
+
+**Key Indicators:**
+- Subscription box returns must be handled differently from standard product returns — the subscription model depends on the full-curation assumption
+- Partial refunds on subscription contents destroy unit economics — prevent this from becoming a pattern
+- Customer preference data is the #1 lever for reducing subscription dissatisfaction
+- A customer who threatens to cancel a long-running subscription over one box is worth accommodating; a new subscriber on their first box is not
+
+---
+
+### Edge Case 16: Bulk B2B Return Where Customer Demands Full Retail Refund on Wholesale Purchase
+
+**Situation:**
+A corporate procurement customer (TechStart Inc.) purchased 50 units of a wireless keyboard-mouse combo ($89.99 retail, $52.00 wholesale/B2B price) for their new office. The total B2B order was $2,600.00. Three weeks after delivery, TechStart decides to switch to a different vendor for ergonomic equipment and wants to return all 50 units. All units are sealed, unopened, in original packaging. The B2B sales rep approved the return. However, when the return is processed, the TechStart procurement manager argues: "These are worth $89.99 each on your website — we should get a credit of $4,499.50, not $2,600."
+
+**Why It's Tricky:**
+The customer paid the B2B wholesale price and is entitled to a refund of what they paid ($2,600), not the retail value ($4,499.50). But B2B customers sometimes have procurement teams who don't understand or don't accept that their refund matches their purchase price, not the retail price. They see the retail price on the website and feel short-changed.
+
+Additionally, 50 sealed units returned simultaneously have high restock value but create a volume spike. If these exact keyboard-mouse combos are in your retail inventory at $89.99, the 50 returned units restore significant inventory — good for your stock position.
+
+**Common Mistake:**
+Issuing credit at retail price ($4,499.50) to "keep the business relationship." This creates a $1,899.50 loss and a precedent that B2B returns are refunded at retail. The reverse mistake: making the return process so adversarial that TechStart never orders again — a B2B account that buys 50 units at a time is worth the relationship investment.
+
+**Expert Approach:**
+1. Refund at the actual B2B purchase price: $2,600.00. This is non-negotiable — the refund matches the amount charged. Reference the B2B purchase order and invoice showing the $52.00/unit price.
+2. If the procurement manager pushes back: the B2B sales rep should handle the communication (not the returns team). The sales rep explains: "Your refund matches your purchase price on PO #[X]. The retail price on our website is for individual consumer purchases, which includes different overhead and margin. Your account benefits from our volume pricing, and the refund reflects that same pricing."
+3. Process the return smoothly and quickly: 50 sealed units should be express-processed (no individual inspection needed — batch scan, Grade A, restock). The faster TechStart receives their credit, the less friction around the amount.
+4. Restock all 50 units as new (sealed, Grade A). Inventory value recovered at wholesale ($2,600).
+5. B2B relationship preservation: the sales rep should follow up with TechStart after the return is processed. "We've processed your return. When you're ready to select your new ergonomic equipment, we'd be happy to quote — we carry several lines including [alternatives]." Maintain the relationship for the next order.
+6. Document the return in the B2B account file. If TechStart shows a pattern of bulk ordering and returning, adjust the account terms (restocking fee on B2B returns, or approval-required ordering).
+
+**Key Indicators:**
+- B2B returns are always refunded at the B2B purchase price, never at retail
+- The sales rep (not the returns team) should manage the pricing conversation for B2B accounts
+- 50 sealed units is a high-value restock opportunity — prioritise quick processing
+- B2B accounts that bulk-order and bulk-return may need modified terms (restocking fees, order approval)
+- The relationship value of a B2B account that orders in 50-unit quantities is significant — handle the return professionally
+
+---
+
+### Edge Case 17: Return of a Product that Was Used as Replacement During Warranty Repair
+
+**Situation:**
+A customer brought in a malfunctioning coffee machine ($449.99) for warranty repair 6 weeks ago. As a courtesy, your store loaned them a comparable refurbished unit (same model, valued at $340 in refurbished condition) to use while theirs was being repaired. The original machine has now been repaired and is ready for pickup. The customer picks up their repaired machine but then asks to "return" the loaner unit — they want to keep using it and buy it at a discount rather than return it. When pressed, they say "actually, I want to return both — the repaired one doesn't feel the same, and I've gotten used to the loaner."
+
+**Why It's Tricky:**
+Multiple issues converge: (1) The loaner is not the customer's property — it's company inventory loaned for temporary use. It cannot be "returned" because it was never sold. (2) The customer's original machine was repaired under warranty, not replaced. A warranty repair doesn't restart the return window — the product is the same unit, now fixed. (3) The customer wants to return a repaired product claiming it "doesn't feel the same" — a subjective complaint after a warranty repair.
+
+**Common Mistake:**
+Allowing the customer to "return" the repaired machine as if it were a new purchase. The original purchase was 6+ weeks ago, outside any return window. The warranty repair doesn't create a new return right. The second mistake: selling the loaner to the customer at a steep discount — loaner units are company assets managed through a separate inventory pool.
+
+**Expert Approach:**
+1. Recover the loaner immediately. It is company property, not a product the customer purchased. Thank the customer for using it and collect it back. There is no "return" process for a loaner — it's an asset recovery.
+2. Address the "doesn't feel the same" complaint on the repaired machine. Ask specific questions: "What feels different? Is there a specific function that's not working correctly?" If the repair introduced a new issue (common with appliance repairs), document it and offer to send it back for correction. If the customer simply prefers the loaner (which they've been using for 6 weeks and is now "theirs" psychologically), acknowledge the adjustment period.
+3. The repaired machine cannot be returned under the standard return policy — the purchase date is 6+ weeks ago. However, if the repair is genuinely unsatisfactory, the customer has a warranty claim (the warranty covers the repair work). Offer: "If the repair didn't fully resolve the original issue, we'll send it back for warranty service at no charge."
+4. If the customer wants to purchase a loaner-equivalent unit: offer to sell them a certified refurbished unit from your refurbished inventory at the standard refurbished price. Do not sell them the specific loaner they used (hygiene, wear from their use, and it's an asset, not retail inventory).
+5. If the customer escalates or threatens: the maximum accommodation is a store credit toward a new machine, applied against the original purchase price minus the value of the use they received (6+ weeks of coffee machine use). This is a judgment call for a manager.
+
+**Key Indicators:**
+- Loaner units are company assets, not retail inventory — they follow asset recovery processes, not return processes
+- Warranty repairs do not create new return windows on the original purchase
+- The psychological "endowment effect" of using a loaner for 6 weeks makes customers reluctant to give it back — this is predictable and should be managed with clear loaner terms at the time of issuance
+- Clear loaner agreements at checkout prevent this edge case: "This is a temporary loaner provided during your warranty repair. It remains company property and must be returned when your repair is complete."
+
+---
+
+### Edge Case 18: Return Flood After Viral Negative Product Review
+
+**Situation:**
+A popular tech reviewer (3.2M YouTube subscribers) posts a video titled "DO NOT BUY — [Your Product] is a FIRE HAZARD" about your brand's portable charger ($49.99). The video shows the reviewer stress-testing the charger and it overheating during a fast-charge scenario that exceeds the product's rated capacity. The video has 4.5M views in 48 hours. You've sold 12,000 units of this charger in the past 90 days. In the 48 hours since the video, you've received 340 return requests (compared to a normal rate of ~15 returns/week for this SKU). The product is NOT subject to a CPSC recall. Your engineering team has reviewed the video and confirms the reviewer used the charger outside its specifications (attempted to fast-charge a laptop with a 100W charger rated for 65W max). The product is safe when used as designed.
+
+**Why It's Tricky:**
+The return requests are driven by fear, not defects. The product works as designed — the reviewer used it incorrectly. But you can't tell 340 customers "you're wrong, a YouTuber misused the product." These customers are genuinely afraid their charger will catch fire. Denying the returns creates social media backlash. Accepting all 340 returns (and potentially thousands more as the video continues to circulate) costs $17,000+ in refunds with minimal recovery.
+
+**Common Mistake:**
+Blanket denial: "The product is safe, we're not accepting returns outside the standard window." This triggers a social media firestorm and potentially regulatory scrutiny (even unfounded — CPSC may investigate based on volume of complaints). The second mistake: blanket acceptance at full refund without any counter-narrative, which validates the reviewer's incorrect claim and could cascade to thousands more returns.
+
+**Expert Approach:**
+1. Accept all 340 return requests immediately, without friction. Process standard returns for within-window customers. For outside-window customers, accept as goodwill exception. Do not fight this wave — the cost of 340 returns ($17,000) is trivial compared to the brand damage of denying returns on a "safety concern."
+2. Simultaneously, the PR/communications team must issue a public response within 24 hours. Acknowledge the concern, explain the product's safety specifications, clarify the reviewer's test exceeded rated capacity (without attacking the reviewer personally), and share third-party safety certification data (UL listing, etc.).
+3. Contact the reviewer directly. Offer to send engineering documentation showing the product's safety at rated capacity. Many reviewers will post a correction or follow-up if provided credible technical data. Do not threaten legal action — this backfires.
+4. Monitor the return volume daily. Create a dedicated return code for "viral-concern returns" to track separately from normal returns. If the volume escalates beyond 1,000 units (8%+ return rate), escalate to VP-level for a formal response plan.
+5. Disposition for returned chargers: all within-window Grade A returns restock as new. Returned chargers are safe — the viral concern is about misuse, not a product defect. Do NOT pull the product from sale unless engineering identifies an actual defect.
+6. Proactive defence: update the product listing with prominent max-wattage warnings. Update the product packaging and manual with clearer limitations. This protects against future claims and shows responsiveness.
+7. Track the return curve. Viral-concern returns typically peak 72-96 hours after the video and decay to baseline within 2-3 weeks. Most returns will process before the curve decays.
+
+**Key Indicators:**
+- Viral negative reviews can generate 10-30x normal return volume within 48-72 hours
+- The return cost ($17K on 340 units) is a rounding error compared to the brand/PR cost of mishandling the situation
+- All returned units are fully functional and restockable — the loss is the processing cost, not the product value
+- Counter-narrative timing is critical: respond within 24 hours with technical data, not PR language
+- Track "viral-concern return" codes separately — this data informs the risk assessment of social media product coverage
+
+---
+
+### Edge Case 19: Customer Returns an Item They Didn't Purchase (Shipping Error by Another Retailer)
+
+**Situation:**
+A customer contacts your returns team stating they want to return a Le Creuset Dutch Oven ($380.00) that "isn't what they ordered." They provide their order number, which shows they ordered a KitchenAid Stand Mixer ($429.99). When the return arrives, inspection confirms it is indeed a Le Creuset Dutch Oven — a product you carry and sell, but not the product this customer ordered. The serial/lot number on the Dutch Oven matches your inventory records as a unit that was in your warehouse. Investigation reveals: a fulfillment packing error sent this customer's KitchenAid mixer to a different customer, and this customer received another customer's Le Creuset order.
+
+**Why It's Tricky:**
+This is a cross-shipment fulfillment error. Two customers are affected: Customer A received the wrong product (the Le Creuset instead of their KitchenAid), and Customer B received Customer A's KitchenAid instead of their Le Creuset. Both customers need their correct products. Both may have already initiated returns or complaints. The fulfillment centre sent two correct products to two wrong addresses.
+
+The financial reconciliation is complex: Customer A paid $429.99 for a KitchenAid and received a $380 Le Creuset. Customer B paid $380 for a Le Creuset and received a $429.99 KitchenAid. Neither customer should be penalised — this is entirely the company's error.
+
+**Common Mistake:**
+Processing Customer A's return as a standard return and shipping them a replacement KitchenAid — but not connecting the dots to realise Customer B also received the wrong product. The second customer may not have complained yet (they might have accepted the KitchenAid thinking it was correct, or they might be planning to return it separately). Handling these as two independent returns instead of one linked cross-shipment doubles the logistical cost.
+
+**Expert Approach:**
+1. Identify the cross-shipment immediately. When Customer A's return arrives as a Le Creuset instead of a KitchenAid, fulfillment should trace the packing records to find where the KitchenAid went. This identifies Customer B.
+2. Contact Customer B proactively — don't wait for them to realise the error. "We've discovered a packing error and you may have received a KitchenAid Stand Mixer instead of the Le Creuset Dutch Oven you ordered. We apologise for the mix-up and would like to ship your correct Le Creuset immediately."
+3. For Customer A: ship the correct KitchenAid via expedited shipping (2-day minimum) with a prepaid return label for the Le Creuset they received. Include a $25-50 store credit for the inconvenience. Do not wait for the Le Creuset to be returned before shipping the KitchenAid — the customer has already waited.
+4. For Customer B: same approach — ship the correct Le Creuset via expedited shipping with a prepaid return label for the KitchenAid. Include a $25-50 store credit.
+5. Inventory reconciliation: once both wrong items are returned, they go back to their respective inventory positions. Net inventory impact should be zero once both returns are processed. Track both under a single cross-shipment incident number.
+6. Root cause: investigate the fulfillment error. Cross-shipments typically happen when two orders are being packed simultaneously at adjacent stations and the products get physically swapped. If this is a recurring issue, the packing process needs a scan-verify step where the packed product's barcode is scanned against the order before sealing.
+7. Financial: the expedited re-shipping cost ($15-25 per shipment × 2 = $30-50) plus store credits ($50-100 total) plus return shipping on both wrong items ($15-25 × 2 = $30-50) totals $110-200 in error resolution cost. The fulfillment error should be charged to the fulfillment operation's error budget, not the returns budget.
+
+**Key Indicators:**
+- When a return arrives with a different product than expected, always check if it's a cross-shipment before processing as a standard return
+- Cross-shipments affect two customers — proactively contact both, even if only one has complained
+- Ship correct items before collecting wrong items — the customer should not wait for the return logistics to resolve
+- Cross-shipment resolution costs $110-200 per incident — this makes the business case for scan-verify packing processes
+- Track cross-shipment rates: target < 0.05% of orders. If rate exceeds 0.1%, the packing process has a systemic gap
+
+**Documentation Required:**
+- Cross-shipment incident record linking both customer orders
+- Packing slip and warehouse records showing the error point
+- Communication records with both customers
+- Shipping records for both replacement shipments
+- Return tracking for both wrong-item returns
+- Root cause analysis note for fulfillment operations
+
+---
+
+### Edge Case 20: Return of a Product That Requires Data Destruction Certification
+
+**Situation:**
+A corporate customer returns 25 laptops (Dell Latitude 5540, $1,199 each, $29,975 total) that were originally purchased for a project team that has been disbanded. The laptops were used for 10 months and contain corporate data — emails, documents, proprietary software, and potentially regulated data (the customer works in healthcare and some laptops may have had access to PHI — Protected Health Information). The customer's IT department performed a standard Windows reset ("Reset this PC") before returning, but they're asking: "Can you certify that these drives have been wiped to HIPAA-compliant standards? Our compliance team requires a certificate of data destruction."
+
+**Why It's Tricky:**
+A standard Windows "Reset this PC" does not meet NIST 800-88 data sanitisation standards. The data is technically recoverable with forensic tools. For a healthcare company with potential PHI on the devices, HIPAA requires that data destruction be documented and verifiable. If you restock or liquidate these laptops without proper data destruction and patient data is later recovered from a resold unit, the liability exposure is enormous — for both the healthcare company and for you as the entity that handled the devices.
+
+Your standard returns process doesn't include NIST 800-88 data sanitisation. You inspect, grade, and disposition — but data destruction certification is a service, not a standard returns step.
+
+**Common Mistake:**
+Accepting the return and processing it as standard — wiping the drives with your normal reset process and restocking. If the normal reset doesn't meet NIST 800-88, and the customer later requires a certificate you can't provide, you have a compliance gap. The second mistake: telling the customer "data destruction is your responsibility" and refusing to help — they're a $30K customer and this is a reasonable request.
+
+**Expert Approach:**
+1. Accept the return of all 25 laptops. Process the RMA normally for grading and refund calculation.
+2. For data destruction: this is a service, not a standard return step. If you have an in-house NIST 800-88 compliant data wipe capability (many return centres do for electronics), offer it as a service. Use a certified tool (Blancco, KillDisk, DBAN) that produces a per-device certificate documenting: device serial number, date, sanitisation method used, and pass/fail result.
+3. If you don't have in-house capability: partner with a certified ITAD (IT Asset Disposition) provider. They will perform the wipe, issue certificates, and handle any drives that fail the wipe (drives that fail must be physically destroyed — degaussed or shredded).
+4. Charge for the service. NIST 800-88 data sanitisation is $5-15 per device in-house, $15-30 per device through an ITAD partner. For 25 laptops: $125-750 total. Offer this as an add-on to the return. Most corporate customers will pay — their alternative is to hire an ITAD provider independently, which costs more.
+5. Provide the individual certificates to the customer's compliance team. Each certificate should reference: NIST SP 800-88 Rev 1, the sanitisation method (Clear, Purge, or Destroy), the device serial number, and the date.
+6. After data destruction is certified: proceed with normal disposition. 10-month-old Dell Latitude laptops with certified data wipes sell well in the refurbished market at $500-700 each.
+7. Systemic: for all corporate/enterprise laptop and device returns, add a data destruction service option at RMA initiation: "Does this device contain corporate or regulated data? We offer certified NIST 800-88 data destruction for $X per device."
+
+**Key Indicators:**
+- Standard "Reset this PC" and factory resets do NOT meet NIST 800-88 sanitisation standards — data is recoverable with forensic tools
+- Healthcare (HIPAA), financial (GLBA), government (NIST), and education (FERPA) customers have regulatory data destruction requirements
+- Data destruction certification is a value-add service that corporate customers will pay for — it's a revenue opportunity, not just a cost
+- Never restock or liquidate enterprise devices without verifying data has been properly sanitised — the liability exposure from a data breach on a resold device is unlimited
+- Keep copies of all data destruction certificates for your own compliance records — if a device you resold is later found to contain recoverable data, the certificate is your defence
diff --git a/web-app/public/skills/reverse-engineer/SKILL.md b/web-app/public/skills/reverse-engineer/SKILL.md
index 8238c7ac..333ee99e 100644
--- a/web-app/public/skills/reverse-engineer/SKILL.md
+++ b/web-app/public/skills/reverse-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: reverse-engineer
-description: "Expert reverse engineer specializing in binary analysis,"
+description: |
+ Expert reverse engineer specializing in binary analysis,
disassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,
radare2, x64dbg, and modern RE toolchains. Handles executable analysis,
library inspection, protocol extraction, and vulnerability research. Use
diff --git a/web-app/public/skills/risk-manager/SKILL.md b/web-app/public/skills/risk-manager/SKILL.md
index e860fe43..7ac39dc7 100644
--- a/web-app/public/skills/risk-manager/SKILL.md
+++ b/web-app/public/skills/risk-manager/SKILL.md
@@ -1,6 +1,7 @@
---
name: risk-manager
-description: "Monitor portfolio risk, R-multiples, and position limits. Creates"
+description: |
+ Monitor portfolio risk, R-multiples, and position limits. Creates
hedging strategies, calculates expectancy, and implements stop-losses. Use
PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
metadata:
diff --git a/web-app/public/skills/ruby-pro/SKILL.md b/web-app/public/skills/ruby-pro/SKILL.md
index d8296a73..bbc6b20b 100644
--- a/web-app/public/skills/ruby-pro/SKILL.md
+++ b/web-app/public/skills/ruby-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: ruby-pro
-description: "Write idiomatic Ruby code with metaprogramming, Rails patterns, and"
+description: |
+ Write idiomatic Ruby code with metaprogramming, Rails patterns, and
performance optimization. Specializes in Ruby on Rails, gem development, and
testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or
complex Ruby features.
diff --git a/web-app/public/skills/rust-pro/SKILL.md b/web-app/public/skills/rust-pro/SKILL.md
index 56b57f23..c6fa0907 100644
--- a/web-app/public/skills/rust-pro/SKILL.md
+++ b/web-app/public/skills/rust-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: rust-pro
-description: "Master Rust 1.75+ with modern async patterns, advanced type system"
+description: |
+ Master Rust 1.75+ with modern async patterns, advanced type system
features, and production-ready systems programming. Expert in the latest Rust
ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for
Rust development, performance optimization, or systems programming.
diff --git a/web-app/public/skills/sales-automator/SKILL.md b/web-app/public/skills/sales-automator/SKILL.md
index 2978913c..d03be643 100644
--- a/web-app/public/skills/sales-automator/SKILL.md
+++ b/web-app/public/skills/sales-automator/SKILL.md
@@ -1,6 +1,7 @@
---
name: sales-automator
-description: "Draft cold emails, follow-ups, and proposal templates. Creates"
+description: |
+ Draft cold emails, follow-ups, and proposal templates. Creates
pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales
outreach or lead nurturing.
metadata:
diff --git a/web-app/public/skills/scala-pro/SKILL.md b/web-app/public/skills/scala-pro/SKILL.md
index 6845992a..4f0b4fb7 100644
--- a/web-app/public/skills/scala-pro/SKILL.md
+++ b/web-app/public/skills/scala-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: scala-pro
-description: "Master enterprise-grade Scala development with functional"
+description: |
+ Master enterprise-grade Scala development with functional
programming, distributed systems, and big data processing. Expert in Apache
Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use
PROACTIVELY for Scala system design, performance optimization, or enterprise
diff --git a/web-app/public/skills/schema-markup/SKILL.md b/web-app/public/skills/schema-markup/SKILL.md
index 98474969..45da25cd 100644
--- a/web-app/public/skills/schema-markup/SKILL.md
+++ b/web-app/public/skills/schema-markup/SKILL.md
@@ -1,6 +1,6 @@
---
name: schema-markup
-description: ">"
+description: >
Design, validate, and optimize schema.org structured data for eligibility,
correctness, and measurable SEO impact. Use when the user wants to add, fix,
audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates
diff --git a/web-app/public/skills/security-auditor/SKILL.md b/web-app/public/skills/security-auditor/SKILL.md
index 8704c428..f4a6b0da 100644
--- a/web-app/public/skills/security-auditor/SKILL.md
+++ b/web-app/public/skills/security-auditor/SKILL.md
@@ -1,6 +1,7 @@
---
name: security-auditor
-description: "Expert security auditor specializing in DevSecOps, comprehensive"
+description: |
+ Expert security auditor specializing in DevSecOps, comprehensive
cybersecurity, and compliance frameworks. Masters vulnerability assessment,
threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud
security, and security automation. Handles DevSecOps integration, compliance
diff --git a/web-app/public/skills/security-scanning-security-sast/SKILL.md b/web-app/public/skills/security-scanning-security-sast/SKILL.md
index 8f15568d..84aae929 100644
--- a/web-app/public/skills/security-scanning-security-sast/SKILL.md
+++ b/web-app/public/skills/security-scanning-security-sast/SKILL.md
@@ -1,6 +1,7 @@
---
name: security-scanning-security-sast
-description: "Static Application Security Testing (SAST) for code vulnerability"
+description: |
+ Static Application Security Testing (SAST) for code vulnerability
analysis across multiple languages and frameworks
metadata:
globs: "**/*.py, **/*.js, **/*.ts, **/*.java, **/*.rb, **/*.go, **/*.rs, **/*.php"
diff --git a/web-app/public/skills/seo-audit/SKILL.md b/web-app/public/skills/seo-audit/SKILL.md
index 8c8b91d0..de3ab23a 100644
--- a/web-app/public/skills/seo-audit/SKILL.md
+++ b/web-app/public/skills/seo-audit/SKILL.md
@@ -1,6 +1,6 @@
---
name: seo-audit
-description: ">"
+description: >
Diagnose and audit SEO issues affecting crawlability, indexation, rankings,
and organic performance. Use when the user asks for an SEO audit, technical SEO
review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check.
diff --git a/web-app/public/skills/seo-authority-builder/SKILL.md b/web-app/public/skills/seo-authority-builder/SKILL.md
index 78322085..2288399b 100644
--- a/web-app/public/skills/seo-authority-builder/SKILL.md
+++ b/web-app/public/skills/seo-authority-builder/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-authority-builder
-description: "Analyzes content for E-E-A-T signals and suggests improvements to"
+description: |
+ Analyzes content for E-E-A-T signals and suggests improvements to
build authority and trust. Identifies missing credibility elements. Use
PROACTIVELY for YMYL topics.
metadata:
diff --git a/web-app/public/skills/seo-cannibalization-detector/SKILL.md b/web-app/public/skills/seo-cannibalization-detector/SKILL.md
index 30f7f19b..cfc2c16e 100644
--- a/web-app/public/skills/seo-cannibalization-detector/SKILL.md
+++ b/web-app/public/skills/seo-cannibalization-detector/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-cannibalization-detector
-description: "Analyzes multiple provided pages to identify keyword overlap and"
+description: |
+ Analyzes multiple provided pages to identify keyword overlap and
potential cannibalization issues. Suggests differentiation strategies. Use
PROACTIVELY when reviewing similar content.
metadata:
diff --git a/web-app/public/skills/seo-content-auditor/SKILL.md b/web-app/public/skills/seo-content-auditor/SKILL.md
index 8e747996..0f8a212f 100644
--- a/web-app/public/skills/seo-content-auditor/SKILL.md
+++ b/web-app/public/skills/seo-content-auditor/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-auditor
-description: "Analyzes provided content for quality, E-E-A-T signals, and SEO"
+description: |
+ Analyzes provided content for quality, E-E-A-T signals, and SEO
best practices. Scores content and provides improvement recommendations based
on established guidelines. Use PROACTIVELY for content review.
metadata:
diff --git a/web-app/public/skills/seo-content-planner/SKILL.md b/web-app/public/skills/seo-content-planner/SKILL.md
index 66c7797f..cd18347d 100644
--- a/web-app/public/skills/seo-content-planner/SKILL.md
+++ b/web-app/public/skills/seo-content-planner/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-planner
-description: "Creates comprehensive content outlines and topic clusters for SEO."
+description: |
+ Creates comprehensive content outlines and topic clusters for SEO.
Plans content calendars and identifies topic gaps. Use PROACTIVELY for content
strategy and planning.
metadata:
diff --git a/web-app/public/skills/seo-content-refresher/SKILL.md b/web-app/public/skills/seo-content-refresher/SKILL.md
index 79ca9440..de5672ef 100644
--- a/web-app/public/skills/seo-content-refresher/SKILL.md
+++ b/web-app/public/skills/seo-content-refresher/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-refresher
-description: "Identifies outdated elements in provided content and suggests"
+description: |
+ Identifies outdated elements in provided content and suggests
updates to maintain freshness. Finds statistics, dates, and examples that need
updating. Use PROACTIVELY for older content.
metadata:
diff --git a/web-app/public/skills/seo-content-writer/SKILL.md b/web-app/public/skills/seo-content-writer/SKILL.md
index bc80aa22..04146556 100644
--- a/web-app/public/skills/seo-content-writer/SKILL.md
+++ b/web-app/public/skills/seo-content-writer/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-content-writer
-description: "Writes SEO-optimized content based on provided keywords and topic"
+description: |
+ Writes SEO-optimized content based on provided keywords and topic
briefs. Creates engaging, comprehensive content following best practices. Use
PROACTIVELY for content creation tasks.
metadata:
diff --git a/web-app/public/skills/seo-fundamentals/SKILL.md b/web-app/public/skills/seo-fundamentals/SKILL.md
index 71212a55..7d12e82b 100644
--- a/web-app/public/skills/seo-fundamentals/SKILL.md
+++ b/web-app/public/skills/seo-fundamentals/SKILL.md
@@ -1,6 +1,6 @@
---
name: seo-fundamentals
-description: ">"
+description: >
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations,
content quality, and how modern search engines evaluate pages. This skill explains
*why* SEO works, not how to execute specific optimizations.
diff --git a/web-app/public/skills/seo-keyword-strategist/SKILL.md b/web-app/public/skills/seo-keyword-strategist/SKILL.md
index f0c64c9e..7d75baba 100644
--- a/web-app/public/skills/seo-keyword-strategist/SKILL.md
+++ b/web-app/public/skills/seo-keyword-strategist/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-keyword-strategist
-description: "Analyzes keyword usage in provided content, calculates density,"
+description: |
+ Analyzes keyword usage in provided content, calculates density,
suggests semantic variations and LSI keywords based on the topic. Prevents
over-optimization. Use PROACTIVELY for content optimization.
metadata:
diff --git a/web-app/public/skills/seo-meta-optimizer/SKILL.md b/web-app/public/skills/seo-meta-optimizer/SKILL.md
index d1cf7499..c749b281 100644
--- a/web-app/public/skills/seo-meta-optimizer/SKILL.md
+++ b/web-app/public/skills/seo-meta-optimizer/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-meta-optimizer
-description: "Creates optimized meta titles, descriptions, and URL suggestions"
+description: |
+ Creates optimized meta titles, descriptions, and URL suggestions
based on character limits and best practices. Generates compelling,
keyword-rich metadata. Use PROACTIVELY for new content.
metadata:
diff --git a/web-app/public/skills/seo-snippet-hunter/SKILL.md b/web-app/public/skills/seo-snippet-hunter/SKILL.md
index eab15c08..be67041e 100644
--- a/web-app/public/skills/seo-snippet-hunter/SKILL.md
+++ b/web-app/public/skills/seo-snippet-hunter/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-snippet-hunter
-description: "Formats content to be eligible for featured snippets and SERP"
+description: |
+ Formats content to be eligible for featured snippets and SERP
features. Creates snippet-optimized content blocks based on best practices.
Use PROACTIVELY for question-based content.
metadata:
diff --git a/web-app/public/skills/seo-structure-architect/SKILL.md b/web-app/public/skills/seo-structure-architect/SKILL.md
index d9c0644b..7d28c670 100644
--- a/web-app/public/skills/seo-structure-architect/SKILL.md
+++ b/web-app/public/skills/seo-structure-architect/SKILL.md
@@ -1,6 +1,7 @@
---
name: seo-structure-architect
-description: "Analyzes and optimizes content structure including header"
+description: |
+ Analyzes and optimizes content structure including header
hierarchy, suggests schema markup, and internal linking opportunities. Creates
search-friendly content organization. Use PROACTIVELY for content structuring.
metadata:
diff --git a/web-app/public/skills/sql-pro/SKILL.md b/web-app/public/skills/sql-pro/SKILL.md
index ddb5a988..99f4582b 100644
--- a/web-app/public/skills/sql-pro/SKILL.md
+++ b/web-app/public/skills/sql-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: sql-pro
-description: "Master modern SQL with cloud-native databases, OLTP/OLAP"
+description: |
+ Master modern SQL with cloud-native databases, OLTP/OLAP
optimization, and advanced query techniques. Expert in performance tuning,
data modeling, and hybrid analytical systems. Use PROACTIVELY for database
optimization or complex analysis.
diff --git a/web-app/public/skills/startup-analyst/SKILL.md b/web-app/public/skills/startup-analyst/SKILL.md
index 9dd9fbe9..4d97afd3 100644
--- a/web-app/public/skills/startup-analyst/SKILL.md
+++ b/web-app/public/skills/startup-analyst/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-analyst
-description: "Expert startup business analyst specializing in market sizing,"
+description: |
+ Expert startup business analyst specializing in market sizing,
financial modeling, competitive analysis, and strategic planning for
early-stage companies. Use PROACTIVELY when the user asks about market
opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive
diff --git a/web-app/public/skills/startup-business-analyst-business-case/SKILL.md b/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
index 7e21641c..554aea60 100644
--- a/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-business-case/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-business-case
-description: "Generate comprehensive investor-ready business case document with"
+description: |
+ Generate comprehensive investor-ready business case document with
market, solution, financials, and strategy
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md b/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
index 1e09b5db..f68ca0f2 100644
--- a/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-financial-projections/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-financial-projections
-description: "Create detailed 3-5 year financial model with revenue, costs, cash"
+description: |
+ Create detailed 3-5 year financial model with revenue, costs, cash
flow, and scenarios
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md b/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
index 013d551a..8d73f982 100644
--- a/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
+++ b/web-app/public/skills/startup-business-analyst-market-opportunity/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-business-analyst-market-opportunity
-description: "Generate comprehensive market opportunity analysis with TAM/SAM/SOM"
+description: |
+ Generate comprehensive market opportunity analysis with TAM/SAM/SOM
calculations
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
risk: unknown
diff --git a/web-app/public/skills/startup-financial-modeling/SKILL.md b/web-app/public/skills/startup-financial-modeling/SKILL.md
index 4921e7ea..a80405d5 100644
--- a/web-app/public/skills/startup-financial-modeling/SKILL.md
+++ b/web-app/public/skills/startup-financial-modeling/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-financial-modeling
-description: "This skill should be used when the user asks to \\\"create financial"
+description: |
+ This skill should be used when the user asks to \\\"create financial
projections", "build a financial model", "forecast revenue", "calculate burn
rate", "estimate runway", "model cash flow", or requests 3-5 year financial
planning for a startup.
diff --git a/web-app/public/skills/startup-metrics-framework/SKILL.md b/web-app/public/skills/startup-metrics-framework/SKILL.md
index 7c8acdc3..cdd8c616 100644
--- a/web-app/public/skills/startup-metrics-framework/SKILL.md
+++ b/web-app/public/skills/startup-metrics-framework/SKILL.md
@@ -1,6 +1,7 @@
---
name: startup-metrics-framework
-description: "This skill should be used when the user asks about \\\"key startup"
+description: |
+ This skill should be used when the user asks about \\\"key startup
metrics", "SaaS metrics", "CAC and LTV", "unit economics", "burn multiple",
"rule of 40", "marketplace metrics", or requests guidance on tracking and
optimizing business performance metrics.
diff --git a/web-app/public/skills/tdd-orchestrator/SKILL.md b/web-app/public/skills/tdd-orchestrator/SKILL.md
index 5878ac1c..700aa500 100644
--- a/web-app/public/skills/tdd-orchestrator/SKILL.md
+++ b/web-app/public/skills/tdd-orchestrator/SKILL.md
@@ -1,6 +1,7 @@
---
name: tdd-orchestrator
-description: "Master TDD orchestrator specializing in red-green-refactor"
+description: |
+ Master TDD orchestrator specializing in red-green-refactor
discipline, multi-agent workflow coordination, and comprehensive test-driven
development practices. Enforces TDD best practices across teams with
AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD
diff --git a/web-app/public/skills/team-composition-analysis/SKILL.md b/web-app/public/skills/team-composition-analysis/SKILL.md
index 9ce88e72..d1229a2c 100644
--- a/web-app/public/skills/team-composition-analysis/SKILL.md
+++ b/web-app/public/skills/team-composition-analysis/SKILL.md
@@ -1,6 +1,7 @@
---
name: team-composition-analysis
-description: "This skill should be used when the user asks to \\\"plan team"
+description: |
+ This skill should be used when the user asks to \\\"plan team
structure", "determine hiring needs", "design org chart", "calculate
compensation", "plan equity allocation", or requests organizational design and
headcount planning for a startup.
diff --git a/web-app/public/skills/temporal-python-pro/SKILL.md b/web-app/public/skills/temporal-python-pro/SKILL.md
index 261fa049..eb233499 100644
--- a/web-app/public/skills/temporal-python-pro/SKILL.md
+++ b/web-app/public/skills/temporal-python-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: temporal-python-pro
-description: "Master Temporal workflow orchestration with Python SDK. Implements"
+description: |
+ Master Temporal workflow orchestration with Python SDK. Implements
durable workflows, saga patterns, and distributed transactions. Covers
async/await, testing strategies, and production deployment. Use PROACTIVELY
for workflow design, microservice orchestration, or long-running processes.
diff --git a/web-app/public/skills/terraform-specialist/SKILL.md b/web-app/public/skills/terraform-specialist/SKILL.md
index 146087f7..8ec685f9 100644
--- a/web-app/public/skills/terraform-specialist/SKILL.md
+++ b/web-app/public/skills/terraform-specialist/SKILL.md
@@ -1,6 +1,7 @@
---
name: terraform-specialist
-description: "Expert Terraform/OpenTofu specialist mastering advanced IaC"
+description: |
+ Expert Terraform/OpenTofu specialist mastering advanced IaC
automation, state management, and enterprise infrastructure patterns. Handles
complex module design, multi-cloud deployments, GitOps workflows, policy as
code, and CI/CD integration. Covers migration strategies, security best
diff --git a/web-app/public/skills/test-automator/SKILL.md b/web-app/public/skills/test-automator/SKILL.md
index e5fb2b0e..16f382b5 100644
--- a/web-app/public/skills/test-automator/SKILL.md
+++ b/web-app/public/skills/test-automator/SKILL.md
@@ -1,6 +1,7 @@
---
name: test-automator
-description: "Master AI-powered test automation with modern frameworks,"
+description: |
+ Master AI-powered test automation with modern frameworks,
self-healing tests, and comprehensive quality engineering. Build scalable
testing strategies with advanced CI/CD integration. Use PROACTIVELY for
testing automation or quality assurance.
diff --git a/web-app/public/skills/track-management/SKILL.md b/web-app/public/skills/track-management/SKILL.md
index c87f2591..7459de2f 100644
--- a/web-app/public/skills/track-management/SKILL.md
+++ b/web-app/public/skills/track-management/SKILL.md
@@ -1,6 +1,7 @@
---
name: track-management
-description: "Use this skill when creating, managing, or working with Conductor"
+description: |
+ Use this skill when creating, managing, or working with Conductor
tracks - the logical work units for features, bugs, and refactors. Applies to
spec.md, plan.md, and track lifecycle operations.
metadata:
diff --git a/web-app/public/skills/tutorial-engineer/SKILL.md b/web-app/public/skills/tutorial-engineer/SKILL.md
index f7ec59e1..23169adb 100644
--- a/web-app/public/skills/tutorial-engineer/SKILL.md
+++ b/web-app/public/skills/tutorial-engineer/SKILL.md
@@ -1,6 +1,7 @@
---
name: tutorial-engineer
-description: "Creates step-by-step tutorials and educational content from code."
+description: |
+ Creates step-by-step tutorials and educational content from code.
Transforms complex concepts into progressive learning experiences with
hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,
or concept explanations.
diff --git a/web-app/public/skills/typescript-expert/SKILL.md b/web-app/public/skills/typescript-expert/SKILL.md
index 8263f3d5..3de9f638 100644
--- a/web-app/public/skills/typescript-expert/SKILL.md
+++ b/web-app/public/skills/typescript-expert/SKILL.md
@@ -1,6 +1,6 @@
---
name: typescript-expert
-description: ">-"
+description: >-
TypeScript and JavaScript expert with deep knowledge of type-level
programming, performance optimization, monorepo management, migration
strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript
diff --git a/web-app/public/skills/typescript-pro/SKILL.md b/web-app/public/skills/typescript-pro/SKILL.md
index 31cf0e42..d65babb0 100644
--- a/web-app/public/skills/typescript-pro/SKILL.md
+++ b/web-app/public/skills/typescript-pro/SKILL.md
@@ -1,6 +1,7 @@
---
name: typescript-pro
-description: "Master TypeScript with advanced types, generics, and strict type"
+description: |
+ Master TypeScript with advanced types, generics, and strict type
safety. Handles complex type systems, decorators, and enterprise-grade
patterns. Use PROACTIVELY for TypeScript architecture, type inference
optimization, or advanced typing patterns.
diff --git a/web-app/public/skills/ui-ux-designer/SKILL.md b/web-app/public/skills/ui-ux-designer/SKILL.md
index 24e6ec58..a102824c 100644
--- a/web-app/public/skills/ui-ux-designer/SKILL.md
+++ b/web-app/public/skills/ui-ux-designer/SKILL.md
@@ -1,6 +1,7 @@
---
name: ui-ux-designer
-description: "Create interface designs, wireframes, and design systems. Masters"
+description: |
+ Create interface designs, wireframes, and design systems. Masters
user research, accessibility standards, and modern design tools. Specializes
in design tokens, component libraries, and inclusive design. Use PROACTIVELY
for design systems, user flows, or interface optimization.
diff --git a/web-app/public/skills/ui-visual-validator/SKILL.md b/web-app/public/skills/ui-visual-validator/SKILL.md
index 2850020d..f455e73e 100644
--- a/web-app/public/skills/ui-visual-validator/SKILL.md
+++ b/web-app/public/skills/ui-visual-validator/SKILL.md
@@ -1,6 +1,7 @@
---
name: ui-visual-validator
-description: "Rigorous visual validation expert specializing in UI testing,"
+description: |
+ Rigorous visual validation expert specializing in UI testing,
design system compliance, and accessibility verification. Masters screenshot
analysis, visual regression testing, and component validation. Use PROACTIVELY
to verify UI modifications have achieved their intended goals through
diff --git a/web-app/public/skills/unity-developer/SKILL.md b/web-app/public/skills/unity-developer/SKILL.md
index e6d114e0..53dbbadd 100644
--- a/web-app/public/skills/unity-developer/SKILL.md
+++ b/web-app/public/skills/unity-developer/SKILL.md
@@ -1,6 +1,7 @@
---
name: unity-developer
-description: "Build Unity games with optimized C# scripts, efficient rendering,"
+description: |
+ Build Unity games with optimized C# scripts, efficient rendering,
and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and
cross-platform deployment. Handles gameplay systems, UI implementation, and
platform optimization. Use PROACTIVELY for Unity performance issues, game
diff --git a/web-app/public/skills/workflow-patterns/SKILL.md b/web-app/public/skills/workflow-patterns/SKILL.md
index 717f3c89..f4f23e1d 100644
--- a/web-app/public/skills/workflow-patterns/SKILL.md
+++ b/web-app/public/skills/workflow-patterns/SKILL.md
@@ -1,6 +1,7 @@
---
name: workflow-patterns
-description: "Use this skill when implementing tasks according to Conductor's TDD"
+description: |
+ Use this skill when implementing tasks according to Conductor's TDD
workflow, handling phase checkpoints, managing git commits for tasks, or
understanding the verification protocol.
metadata:
From f8123cb5a9607ccc0dbdc9b60a08b3e4c550eea8 Mon Sep 17 00:00:00 2001
From: Zied
Date: Thu, 26 Feb 2026 12:39:28 +0100
Subject: [PATCH 10/11] feat: Implement date tracking for skills
- Added `date_added` field to all skills in frontmatter.
- Updated Home page to display skill addition date alongside risk level.
- Enhanced Skill Detail page to show date added in a badge format.
- Created scripts for managing skill dates, including adding missing dates and generating reports.
- Updated validators to enforce date format compliance.
- Added comprehensive documentation on date tracking implementation and usage.
- Introduced a new skill template including the `date_added` field.
---
README.md | 5 +-
docs/DATE_TRACKING_IMPLEMENTATION.md | 156 ++
docs/SKILLS_DATE_TRACKING.md | 221 ++
docs/SKILL_ANATOMY.md | 10 +
docs/SKILL_TEMPLATE.md | 62 +
scripts/generate_index.py | 11 +-
scripts/generate_skills_report.py | 127 +
scripts/manage_skill_dates.py | 306 +++
scripts/validate-skills.js | 1 +
scripts/validate_skills.py | 10 +
skills_index.json | 3302 +++++++++++++++++---------
web-app/public/skills.json | 3302 +++++++++++++++++---------
web-app/src/pages/Home.jsx | 9 +-
web-app/src/pages/SkillDetail.jsx | 7 +-
14 files changed, 5168 insertions(+), 2361 deletions(-)
create mode 100644 docs/DATE_TRACKING_IMPLEMENTATION.md
create mode 100644 docs/SKILLS_DATE_TRACKING.md
create mode 100644 docs/SKILL_TEMPLATE.md
create mode 100644 scripts/generate_skills_report.py
create mode 100644 scripts/manage_skill_dates.py
diff --git a/README.md b/README.md
index 96651c9f..75a7fc41 100644
--- a/README.md
+++ b/README.md
@@ -369,8 +369,9 @@ We welcome contributions from the community! To add a new skill:
1. **Fork** the repository.
2. **Create a new directory** inside `skills/` for your skill.
3. **Add a `SKILL.md`** with the required frontmatter (name, description, risk, source). See [docs/SKILL_ANATOMY.md](docs/SKILL_ANATOMY.md) and [docs/QUALITY_BAR.md](docs/QUALITY_BAR.md).
-4. **Run validation**: `npm run validate` (or `npm run validate:strict` for CI). Optionally run `python3 scripts/validate_references.py` if you touch workflows or bundles.
-5. **Submit a Pull Request**.
+4. **Add date tracking** (optional): Include `date_added: "YYYY-MM-DD"` in frontmatter. See [docs/SKILLS_DATE_TRACKING.md](docs/SKILLS_DATE_TRACKING.md) for details.
+5. **Run validation**: `npm run validate` (or `npm run validate:strict` for CI). Optionally run `python3 scripts/validate_references.py` if you touch workflows or bundles.
+6. **Submit a Pull Request**.
Please ensure your skill follows the Antigravity/Claude Code best practices. Maintainers: see [docs/AUDIT.md](docs/AUDIT.md) for coherence checks and [.github/MAINTENANCE.md](.github/MAINTENANCE.md) for the full validation chain.
diff --git a/docs/DATE_TRACKING_IMPLEMENTATION.md b/docs/DATE_TRACKING_IMPLEMENTATION.md
new file mode 100644
index 00000000..7eaf7d94
--- /dev/null
+++ b/docs/DATE_TRACKING_IMPLEMENTATION.md
@@ -0,0 +1,156 @@
+# Date Tracking Implementation Summary
+
+## ✅ What Was Implemented
+
+### 1. **Frontmatter Template Update**
+All 946 skills now have the `date_added: "2025-02-26"` field in their `SKILL.md` frontmatter:
+
+```yaml
+---
+name: skill-name
+description: "Description"
+date_added: "2025-02-26"
+---
+```
+
+### 2. **Web App Integration**
+
+#### **Home Page (Skill List Cards)**
+- Each skill card now displays a small date badge: `📅 YYYY-MM-DD`
+- Shows alongside the risk level
+- Clean, compact format in the bottom metadata section
+
+Example card now shows:
+```
+Risk: safe 📅 2025-02-26
+```
+
+#### **Skill Detail Page**
+- Date appears as a green badge near the top with other metadata
+- Format: `📅 Added YYYY-MM-DD`
+- Shown alongside Category, Source, and Star buttons
+
+### 3. **Validators Updated**
+Both validators now accept and validate the `date_added` field:
+
+- **validate-skills.js**: Added to `ALLOWED_FIELDS`
+- **validate_skills.py**: Added YYYY-MM-DD format validation
+ - Warns (dev mode) or fails (strict mode) on missing dates
+ - Validates format strictly
+
+### 4. **Index Generation**
+- **generate_index.py** updated to include `date_added` in `skills.json`
+- All 946 skills now have dates in the web app index
+- Dates are properly exported to web app's `/public/skills.json`
+
+### 5. **Documentation**
+- **SKILL_TEMPLATE.md**: New template for creating skills with date field included
+- **SKILLS_DATE_TRACKING.md**: Complete usage guide for date management
+- **SKILL_ANATOMY.md**: Updated with date_added field documentation
+- **README.md**: Updated contribution guide to mention date tracking
+
+### 6. **Script Tools**
+✅ All scripts handle UTF-8 encoding on Windows:
+
+- **manage_skill_dates.py**: Add, update, list skill dates
+- **generate_skills_report.py**: Generate JSON report with dates
+- Both handle emoji output correctly on Windows
+
+## 📊 Current Status
+
+- ✅ **946/946 skills** have `date_added: "2025-02-26"`
+- ✅ **100% coverage** of date tracking
+- ✅ **Web app displays dates** on all skill cards
+- ✅ **Validators enforce format** (YYYY-MM-DD)
+- ✅ **Reports available** via CLI tools
+
+## 🎨 UI Changes
+
+### Skill Card (Home Page)
+Before:
+```
+Risk: safe
+```
+
+After:
+```
+Risk: safe 📅 2025-02-26
+```
+
+### Skill Detail Page
+Before:
+```
+[Category] [Source] [Stars]
+```
+
+After:
+```
+[Category] [Source] [📅 Added 2025-02-26] [Stars]
+```
+
+## 📝 Using the Date Field
+
+### For New Skills
+Create with template:
+```bash
+cp docs/SKILL_TEMPLATE.md skills/my-new-skill/SKILL.md
+# Edit the template and set date_added to today's date
+```
+
+### For Existing Skills
+Use the management script:
+```bash
+# Add missing dates
+python scripts/manage_skill_dates.py add-missing --date 2025-02-26
+
+# Update a single skill
+python scripts/manage_skill_dates.py update skill-name 2025-02-26
+
+# List all with dates
+python scripts/manage_skill_dates.py list
+
+# Generate report
+python scripts/generate_skills_report.py --output report.json
+```
+
+## 🔧 Technical Details
+
+### Files Modified
+1. `scripts/generate_index.py` - Added date_added parsing
+2. `scripts/validate-skills.js` - Added to allowed fields
+3. `scripts/validate_skills.py` - Added format validation
+4. `web-app/src/pages/Home.jsx` - Display date in cards
+5. `web-app/src/pages/SkillDetail.jsx` - Display date in detail
+6. `README.md` - Updated contribution guide
+7. `docs/SKILL_ANATOMY.md` - Documented date_added field
+
+### New Files Created
+1. `docs/SKILL_TEMPLATE.md` - Skill creation template
+2. `docs/SKILLS_DATE_TRACKING.md` - Comprehensive guide
+3. `scripts/manage_skill_dates.py` - Date management CLI
+4. `scripts/generate_skills_report.py` - Report generation
+
+## 🚀 Next Steps
+
+1. **In Web App**: Skills now show creation dates automatically
+2. **For Analytics**: Use report script to track skill growth over time
+3. **For Contributions**: Include date_added in new skill PRs
+4. **For Maintenance**: Run validators to ensure date format compliance
+
+## 📈 Reporting Examples
+
+Get a JSON report sorted by date:
+```bash
+python scripts/generate_skills_report.py --output skills_by_date.json
+```
+
+Output includes:
+- Total skills count
+- Skills with/without dates
+- Coverage percentage
+- Full skill metadata with dates
+- Sortable by date or name
+
+---
+
+**Date Feature Ready!** 🎉 All skills now track when they were added to the collection.
diff --git a/docs/SKILLS_DATE_TRACKING.md b/docs/SKILLS_DATE_TRACKING.md
new file mode 100644
index 00000000..880f228e
--- /dev/null
+++ b/docs/SKILLS_DATE_TRACKING.md
@@ -0,0 +1,221 @@
+# Skills Date Tracking Guide
+
+This guide explains how to use the new `date_added` feature for tracking when skills were created or added to the collection.
+
+## Overview
+
+The `date_added` field in skill frontmatter allows you to track when each skill was created. This is useful for:
+
+- **Versioning**: Understanding skill age and maturity
+- **Changelog generation**: Tracking new skills over time
+- **Reporting**: Analyzing skill collection growth
+- **Organization**: Grouping skills by creation date
+
+## Format
+
+The `date_added` field uses ISO 8601 date format: **YYYY-MM-DD**
+
+```yaml
+---
+name: my-skill-name
+description: "Brief description"
+date_added: "2024-01-15"
+---
+```
+
+## Quick Start
+
+### 1. View All Skills with Their Dates
+
+```bash
+python scripts/manage_skill_dates.py list
+```
+
+Output example:
+```
+📅 Skills with Date Added (245):
+============================================================
+ 2025-02-26 │ recent-skill
+ 2025-02-20 │ another-new-skill
+ 2024-12-15 │ older-skill
+ ...
+
+⏳ Skills without Date Added (5):
+============================================================
+ some-legacy-skill
+ undated-skill
+ ...
+
+📊 Coverage: 245/250 (98.0%)
+```
+
+### 2. Add Missing Dates
+
+Add today's date to all skills that don't have a `date_added` field:
+
+```bash
+python scripts/manage_skill_dates.py add-missing
+```
+
+Or specify a custom date:
+
+```bash
+python scripts/manage_skill_dates.py add-missing --date 2024-01-15
+```
+
+### 3. Add/Update All Skills
+
+Set a date for all skills at once:
+
+```bash
+python scripts/manage_skill_dates.py add-all --date 2024-01-01
+```
+
+### 4. Update a Single Skill
+
+Update a specific skill's date:
+
+```bash
+python scripts/manage_skill_dates.py update my-skill-name 2024-06-15
+```
+
+### 5. Generate a Report
+
+Generate a JSON report of all skills with their metadata:
+
+```bash
+python scripts/generate_skills_report.py
+```
+
+Save to file:
+
+```bash
+python scripts/generate_skills_report.py --output skills_report.json
+```
+
+Sort by name:
+
+```bash
+python scripts/generate_skills_report.py --sort name --output sorted_skills.json
+```
+
+## Usage in Your Workflow
+
+### When Creating a New Skill
+
+Add the `date_added` field to your SKILL.md frontmatter:
+
+```yaml
+---
+name: new-awesome-skill
+description: "Does something awesome"
+date_added: "2025-02-26"
+---
+```
+
+### Automated Addition
+
+When onboarding many skills, use:
+
+```bash
+python scripts/manage_skill_dates.py add-missing --date 2025-02-26
+```
+
+This adds today's date to all skills that are missing the field.
+
+### Validation
+
+The validators now check `date_added` format:
+
+```bash
+# Run Python validator (strict mode)
+python scripts/validate_skills.py --strict
+
+# Run JavaScript validator
+npm run validate
+```
+
+Both will flag invalid dates (must be YYYY-MM-DD format).
+
+## Generated Reports
+
+The `generate_skills_report.py` script produces a JSON report with statistics:
+
+```json
+{
+ "generated_at": "2025-02-26T10:30:00.123456",
+ "total_skills": 250,
+ "skills_with_dates": 245,
+ "skills_without_dates": 5,
+ "coverage_percentage": 98.0,
+ "sorted_by": "date",
+ "skills": [
+ {
+ "id": "recent-skill",
+ "name": "recent-skill",
+ "description": "A newly added skill",
+ "date_added": "2025-02-26",
+ "source": "community",
+ "risk": "safe",
+ "category": "recent"
+ },
+ ...
+ ]
+}
+```
+
+Use this for:
+- Dashboard displays
+- Growth metrics
+- Automated reports
+- Analytics
+
+## Integration with CI/CD
+
+Add to your pipeline:
+
+```bash
+# In pre-commit or CI pipeline
+python scripts/validate_skills.py --strict
+
+# Generate stats report
+python scripts/generate_skills_report.py --output reports/skills_report.json
+```
+
+## Best Practices
+
+1. **Use consistent format**: Always use `YYYY-MM-DD`
+2. **Use real dates**: Reflect actual skill creation dates when possible
+3. **Update on creation**: Add the date when creating new skills
+4. **Validate regularly**: Run validators to catch format errors
+5. **Review reports**: Use generated reports to understand collection trends
+
+## Troubleshooting
+
+### "Invalid date_added format"
+
+Make sure the date is in `YYYY-MM-DD` format:
+- ✅ Correct: `2024-01-15`
+- ❌ Wrong: `01/15/2024` or `2024-1-15`
+
+### Script not found
+
+Make sure you're running from the project root:
+```bash
+cd path/to/antigravity-awesome-skills
+python scripts/manage_skill_dates.py list
+```
+
+### Python not found
+
+Install Python 3.x from [python.org](https://python.org/)
+
+## Related Documentation
+
+- [SKILL_ANATOMY.md](docs/SKILL_ANATOMY.md) - Complete skill structure guide
+- [SKILLS_UPDATE_GUIDE.md](SKILLS_UPDATE_GUIDE.md) - How to update the skill collection
+- [EXAMPLES.md](docs/EXAMPLES.md) - Example skills
+
+## Questions or Issues?
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines.
diff --git a/docs/SKILL_ANATOMY.md b/docs/SKILL_ANATOMY.md
index cce332b4..28701cfe 100644
--- a/docs/SKILL_ANATOMY.md
+++ b/docs/SKILL_ANATOMY.md
@@ -76,9 +76,19 @@ description: "Brief description"
risk: "safe" # none | safe | critical | offensive (see QUALITY_BAR.md)
source: "community"
tags: ["react", "typescript"]
+date_added: "2024-01-15"
---
```
+#### `date_added`
+
+- **What it is:** The date when the skill was created or added to the collection
+- **Format:** `YYYY-MM-DD` (ISO 8601 date format)
+- **Purpose:** Helps track skill versioning and community contributions
+- **Required:** No (optional, but recommended)
+- **Example:** `date_added: "2024-01-15"`
+- **Note:** Can be managed automatically with the `scripts/manage_skill_dates.py` script
+
---
## Part 2: Content
diff --git a/docs/SKILL_TEMPLATE.md b/docs/SKILL_TEMPLATE.md
new file mode 100644
index 00000000..c215e572
--- /dev/null
+++ b/docs/SKILL_TEMPLATE.md
@@ -0,0 +1,62 @@
+---
+name: your-skill-name
+description: "Brief one-sentence description of what this skill does (under 200 characters)"
+category: your-category
+risk: safe
+source: community
+date_added: "YYYY-MM-DD"
+---
+
+# Skill Title
+
+## Overview
+
+A brief explanation of what this skill does and why it exists.
+2-4 sentences is perfect.
+
+## When to Use This Skill
+
+- Use when you need to [scenario 1]
+- Use when working with [scenario 2]
+- Use when the user asks about [scenario 3]
+
+## How It Works
+
+### Step 1: [Action]
+
+Detailed instructions...
+
+### Step 2: [Action]
+
+More instructions...
+
+## Examples
+
+### Example 1: [Use Case]
+
+\`\`\`javascript
+// Example code
+\`\`\`
+
+### Example 2: [Another Use Case]
+
+\`\`\`javascript
+// More code
+\`\`\`
+
+## Best Practices
+
+- ✅ Do this
+- ✅ Also do this
+- ❌ Don't do this
+- ❌ Avoid this
+
+## Common Pitfalls
+
+- **Problem:** Description
+ **Solution:** How to fix it
+
+## Related Skills
+
+- `@other-skill` - When to use this instead
+- `@complementary-skill` - How this works together
diff --git a/scripts/generate_index.py b/scripts/generate_index.py
index 84762535..1107e09d 100644
--- a/scripts/generate_index.py
+++ b/scripts/generate_index.py
@@ -1,9 +1,16 @@
import os
import json
import re
+import sys
import yaml
+# Ensure UTF-8 output for Windows compatibility
+if sys.platform == 'win32':
+ import io
+ sys.stdout = io.TextIOWrapper(sys.stdout.buffer, encoding='utf-8')
+ sys.stderr = io.TextIOWrapper(sys.stderr.buffer, encoding='utf-8')
+
def parse_frontmatter(content):
"""
Parses YAML frontmatter, sanitizing unquoted values containing @.
@@ -59,7 +66,8 @@ def generate_index(skills_dir, output_file):
"name": dir_name.replace("-", " ").title(),
"description": "",
"risk": "unknown",
- "source": "unknown"
+ "source": "unknown",
+ "date_added": None
}
try:
@@ -77,6 +85,7 @@ def generate_index(skills_dir, output_file):
if "description" in metadata: skill_info["description"] = metadata["description"]
if "risk" in metadata: skill_info["risk"] = metadata["risk"]
if "source" in metadata: skill_info["source"] = metadata["source"]
+ if "date_added" in metadata: skill_info["date_added"] = metadata["date_added"]
# Fallback for description if missing in frontmatter (legacy support)
if not skill_info["description"]:
diff --git a/scripts/generate_skills_report.py b/scripts/generate_skills_report.py
new file mode 100644
index 00000000..bccd03ae
--- /dev/null
+++ b/scripts/generate_skills_report.py
@@ -0,0 +1,127 @@
+#!/usr/bin/env python3
+"""
+Generate a report of skills with their date_added metadata in JSON format.
+
+Usage:
+ python generate_skills_report.py [--output report.json] [--sort date|name]
+"""
+
+import os
+import re
+import json
+import sys
+import argparse
+from datetime import datetime
+from pathlib import Path
+
+def get_project_root():
+ """Get the project root directory."""
+ return os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
+
+def parse_frontmatter(content):
+ """Parse frontmatter from SKILL.md content."""
+ fm_match = re.search(r'^---\s*\n(.*?)\n---', content, re.DOTALL)
+ if not fm_match:
+ return None
+
+ fm_text = fm_match.group(1)
+ metadata = {}
+ for line in fm_text.split('\n'):
+ if ':' in line and not line.strip().startswith('#'):
+ key, val = line.split(':', 1)
+ metadata[key.strip()] = val.strip().strip('"').strip("'")
+
+ return metadata
+
+def generate_skills_report(output_file=None, sort_by='date'):
+ """Generate a report of all skills with their metadata."""
+ skills_dir = os.path.join(get_project_root(), 'skills')
+ skills_data = []
+
+ for root, dirs, files in os.walk(skills_dir):
+ # Skip hidden/disabled directories
+ dirs[:] = [d for d in dirs if not d.startswith('.')]
+
+ if "SKILL.md" in files:
+ skill_name = os.path.basename(root)
+ skill_path = os.path.join(root, "SKILL.md")
+
+ try:
+ with open(skill_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+
+ metadata = parse_frontmatter(content)
+ if metadata is None:
+ continue
+
+ skill_info = {
+ 'id': metadata.get('id', skill_name),
+ 'name': metadata.get('name', skill_name),
+ 'description': metadata.get('description', ''),
+ 'date_added': metadata.get('date_added', None),
+ 'source': metadata.get('source', 'unknown'),
+ 'risk': metadata.get('risk', 'unknown'),
+ 'category': metadata.get('category', metadata.get('id', '').split('-')[0] if '-' in metadata.get('id', '') else 'other'),
+ }
+
+ skills_data.append(skill_info)
+ except Exception as e:
+ print(f"⚠️ Error reading {skill_path}: {str(e)}", file=sys.stderr)
+
+ # Sort data
+ if sort_by == 'date':
+ # Sort by date_added (newest first), then by name
+ skills_data.sort(key=lambda x: (x['date_added'] or '0000-00-00', x['name']), reverse=True)
+ elif sort_by == 'name':
+ skills_data.sort(key=lambda x: x['name'])
+
+ # Prepare report
+ report = {
+ 'generated_at': datetime.now().isoformat(),
+ 'total_skills': len(skills_data),
+ 'skills_with_dates': sum(1 for s in skills_data if s['date_added']),
+ 'skills_without_dates': sum(1 for s in skills_data if not s['date_added']),
+ 'coverage_percentage': round(
+ sum(1 for s in skills_data if s['date_added']) / len(skills_data) * 100 if skills_data else 0,
+ 1
+ ),
+ 'sorted_by': sort_by,
+ 'skills': skills_data
+ }
+
+ # Output
+ if output_file:
+ try:
+ with open(output_file, 'w', encoding='utf-8') as f:
+ json.dump(report, f, indent=2, ensure_ascii=False)
+ print(f"✅ Report saved to: {output_file}")
+ except Exception as e:
+ print(f"❌ Error saving report: {str(e)}")
+ return None
+ else:
+ # Print to stdout
+ print(json.dumps(report, indent=2, ensure_ascii=False))
+
+ return report
+
+def main():
+ parser = argparse.ArgumentParser(
+ description="Generate a skills report with date_added metadata",
+ formatter_class=argparse.RawDescriptionHelpFormatter,
+ epilog="""
+Examples:
+ python generate_skills_report.py
+ python generate_skills_report.py --output skills_report.json
+ python generate_skills_report.py --sort name --output sorted_skills.json
+ """
+ )
+
+ parser.add_argument('--output', '-o', help='Output file (JSON). If not specified, prints to stdout')
+ parser.add_argument('--sort', choices=['date', 'name'], default='date', help='Sort order (default: date)')
+
+ args = parser.parse_args()
+
+ generate_skills_report(output_file=args.output, sort_by=args.sort)
+
+if __name__ == '__main__':
+ main()
diff --git a/scripts/manage_skill_dates.py b/scripts/manage_skill_dates.py
new file mode 100644
index 00000000..4b9cfdcd
--- /dev/null
+++ b/scripts/manage_skill_dates.py
@@ -0,0 +1,306 @@
+#!/usr/bin/env python3
+"""
+Manage skill date_added metadata.
+
+Usage:
+ python manage_skill_dates.py list # List all skills with their dates
+ python manage_skill_dates.py add-missing [--date YYYY-MM-DD] # Add dates to skills without them
+ python manage_skill_dates.py add-all [--date YYYY-MM-DD] # Add/update dates for all skills
+ python manage_skill_dates.py update YYYY-MM-DD # Update a specific skill's date
+"""
+
+import os
+import re
+import sys
+import argparse
+from datetime import datetime
+from pathlib import Path
+
+# Ensure UTF-8 output for Windows compatibility
+if sys.platform == 'win32':
+ import io
+ sys.stdout = io.TextIOWrapper(sys.stdout.buffer, encoding='utf-8')
+ sys.stderr = io.TextIOWrapper(sys.stderr.buffer, encoding='utf-8')
+
+def get_project_root():
+ """Get the project root directory."""
+ return os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
+
+def parse_frontmatter(content):
+ """Parse frontmatter from SKILL.md content."""
+ fm_match = re.search(r'^---\s*\n(.*?)\n---', content, re.DOTALL)
+ if not fm_match:
+ return None, content
+
+ fm_text = fm_match.group(1)
+ metadata = {}
+ for line in fm_text.split('\n'):
+ if ':' in line and not line.strip().startswith('#'):
+ key, val = line.split(':', 1)
+ metadata[key.strip()] = val.strip().strip('"').strip("'")
+
+ return metadata, content
+
+def reconstruct_frontmatter(metadata):
+ """Reconstruct frontmatter from metadata dict."""
+ lines = ["---"]
+
+ # Order: id, name, description, category, risk, source, tags, date_added
+ priority_keys = ['id', 'name', 'description', 'category', 'risk', 'source', 'tags']
+
+ for key in priority_keys:
+ if key in metadata:
+ val = metadata[key]
+ if isinstance(val, list):
+ # Handle list fields like tags
+ lines.append(f'{key}: {val}')
+ elif ' ' in str(val) or any(c in str(val) for c in ':#"'):
+ lines.append(f'{key}: "{val}"')
+ else:
+ lines.append(f'{key}: {val}')
+
+ # Add date_added at the end
+ if 'date_added' in metadata:
+ lines.append(f'date_added: "{metadata["date_added"]}"')
+
+ lines.append("---")
+ return '\n'.join(lines)
+
+def update_skill_frontmatter(skill_path, metadata):
+ """Update a skill's frontmatter with new metadata."""
+ try:
+ with open(skill_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+
+ old_metadata, body_content = parse_frontmatter(content)
+ if old_metadata is None:
+ print(f"❌ {skill_path}: Could not parse frontmatter")
+ return False
+
+ # Merge metadata
+ old_metadata.update(metadata)
+
+ # Reconstruct content
+ new_frontmatter = reconstruct_frontmatter(old_metadata)
+
+ # Find where the frontmatter ends in the original content
+ fm_end = content.find('---', 3) # Skip first ---
+ if fm_end == -1:
+ print(f"❌ {skill_path}: Could not locate frontmatter boundary")
+ return False
+
+ body_start = fm_end + 3
+ body = content[body_start:]
+
+ new_content = new_frontmatter + body
+
+ with open(skill_path, 'w', encoding='utf-8') as f:
+ f.write(new_content)
+
+ return True
+ except Exception as e:
+ print(f"❌ Error updating {skill_path}: {str(e)}")
+ return False
+
+def list_skills():
+ """List all skills with their date_added values."""
+ skills_dir = os.path.join(get_project_root(), 'skills')
+ skills_with_dates = []
+ skills_without_dates = []
+
+ for root, dirs, files in os.walk(skills_dir):
+ # Skip hidden/disabled directories
+ dirs[:] = [d for d in dirs if not d.startswith('.')]
+
+ if "SKILL.md" in files:
+ skill_name = os.path.basename(root)
+ skill_path = os.path.join(root, "SKILL.md")
+
+ try:
+ with open(skill_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+
+ metadata, _ = parse_frontmatter(content)
+ if metadata is None:
+ continue
+
+ date_added = metadata.get('date_added', 'N/A')
+
+ if date_added == 'N/A':
+ skills_without_dates.append(skill_name)
+ else:
+ skills_with_dates.append((skill_name, date_added))
+ except Exception as e:
+ print(f"⚠️ Error reading {skill_path}: {str(e)}", file=sys.stderr)
+
+ # Sort by date
+ skills_with_dates.sort(key=lambda x: x[1], reverse=True)
+
+ print(f"\n📅 Skills with Date Added ({len(skills_with_dates)}):")
+ print("=" * 60)
+
+ if skills_with_dates:
+ for skill_name, date in skills_with_dates:
+ print(f" {date} │ {skill_name}")
+ else:
+ print(" (none)")
+
+ print(f"\n⏳ Skills without Date Added ({len(skills_without_dates)}):")
+ print("=" * 60)
+
+ if skills_without_dates:
+ for skill_name in sorted(skills_without_dates):
+ print(f" {skill_name}")
+ else:
+ print(" (none)")
+
+ total = len(skills_with_dates) + len(skills_without_dates)
+ percentage = (len(skills_with_dates) / total * 100) if total > 0 else 0
+ print(f"\n📊 Coverage: {len(skills_with_dates)}/{total} ({percentage:.1f}%)")
+
+def add_missing_dates(date_str=None):
+ """Add date_added to skills that don't have it."""
+ if date_str is None:
+ date_str = datetime.now().strftime('%Y-%m-%d')
+
+ # Validate date format
+ if not re.match(r'^\d{4}-\d{2}-\d{2}$', date_str):
+ print(f"❌ Invalid date format: {date_str}. Use YYYY-MM-DD.")
+ return False
+
+ skills_dir = os.path.join(get_project_root(), 'skills')
+ updated_count = 0
+ skipped_count = 0
+
+ for root, dirs, files in os.walk(skills_dir):
+ dirs[:] = [d for d in dirs if not d.startswith('.')]
+
+ if "SKILL.md" in files:
+ skill_name = os.path.basename(root)
+ skill_path = os.path.join(root, "SKILL.md")
+
+ try:
+ with open(skill_path, 'r', encoding='utf-8') as f:
+ content = f.read()
+
+ metadata, _ = parse_frontmatter(content)
+ if metadata is None:
+ print(f"⚠️ {skill_name}: Could not parse frontmatter, skipping")
+ continue
+
+ if 'date_added' not in metadata:
+ if update_skill_frontmatter(skill_path, {'date_added': date_str}):
+ print(f"✅ {skill_name}: Added date_added: {date_str}")
+ updated_count += 1
+ else:
+ print(f"❌ {skill_name}: Failed to update")
+ else:
+ skipped_count += 1
+ except Exception as e:
+ print(f"❌ Error processing {skill_name}: {str(e)}")
+
+ print(f"\n✨ Updated {updated_count} skills, skipped {skipped_count} that already had dates")
+ return True
+
+def add_all_dates(date_str=None):
+ """Add/update date_added for all skills."""
+ if date_str is None:
+ date_str = datetime.now().strftime('%Y-%m-%d')
+
+ # Validate date format
+ if not re.match(r'^\d{4}-\d{2}-\d{2}$', date_str):
+ print(f"❌ Invalid date format: {date_str}. Use YYYY-MM-DD.")
+ return False
+
+ skills_dir = os.path.join(get_project_root(), 'skills')
+ updated_count = 0
+
+ for root, dirs, files in os.walk(skills_dir):
+ dirs[:] = [d for d in dirs if not d.startswith('.')]
+
+ if "SKILL.md" in files:
+ skill_name = os.path.basename(root)
+ skill_path = os.path.join(root, "SKILL.md")
+
+ try:
+ if update_skill_frontmatter(skill_path, {'date_added': date_str}):
+ print(f"✅ {skill_name}: Set date_added: {date_str}")
+ updated_count += 1
+ else:
+ print(f"❌ {skill_name}: Failed to update")
+ except Exception as e:
+ print(f"❌ Error processing {skill_name}: {str(e)}")
+
+ print(f"\n✨ Updated {updated_count} skills")
+ return True
+
+def update_skill_date(skill_name, date_str):
+ """Update a specific skill's date_added."""
+ # Validate date format
+ if not re.match(r'^\d{4}-\d{2}-\d{2}$', date_str):
+ print(f"❌ Invalid date format: {date_str}. Use YYYY-MM-DD.")
+ return False
+
+ skills_dir = os.path.join(get_project_root(), 'skills')
+ skill_path = os.path.join(skills_dir, skill_name, 'SKILL.md')
+
+ if not os.path.exists(skill_path):
+ print(f"❌ Skill not found: {skill_name}")
+ return False
+
+ if update_skill_frontmatter(skill_path, {'date_added': date_str}):
+ print(f"✅ {skill_name}: Updated date_added to {date_str}")
+ return True
+ else:
+ print(f"❌ {skill_name}: Failed to update")
+ return False
+
+def main():
+ parser = argparse.ArgumentParser(
+ description="Manage skill date_added metadata",
+ formatter_class=argparse.RawDescriptionHelpFormatter,
+ epilog="""
+Examples:
+ python manage_skill_dates.py list
+ python manage_skill_dates.py add-missing
+ python manage_skill_dates.py add-missing --date 2024-01-15
+ python manage_skill_dates.py add-all --date 2025-01-01
+ python manage_skill_dates.py update my-skill-name 2024-06-01
+ """
+ )
+
+ subparsers = parser.add_subparsers(dest='command', help='Command to execute')
+
+ # list command
+ subparsers.add_parser('list', help='List all skills with their date_added values')
+
+ # add-missing command
+ add_missing_parser = subparsers.add_parser('add-missing', help='Add date_added to skills without it')
+ add_missing_parser.add_argument('--date', help='Date to use (YYYY-MM-DD), defaults to today')
+
+ # add-all command
+ add_all_parser = subparsers.add_parser('add-all', help='Add/update date_added for all skills')
+ add_all_parser.add_argument('--date', help='Date to use (YYYY-MM-DD), defaults to today')
+
+ # update command
+ update_parser = subparsers.add_parser('update', help='Update a specific skill date')
+ update_parser.add_argument('skill_name', help='Name of the skill')
+ update_parser.add_argument('date', help='Date to set (YYYY-MM-DD)')
+
+ args = parser.parse_args()
+
+ if not args.command:
+ parser.print_help()
+ return
+
+ if args.command == 'list':
+ list_skills()
+ elif args.command == 'add-missing':
+ add_missing_dates(args.date)
+ elif args.command == 'add-all':
+ add_all_dates(args.date)
+ elif args.command == 'update':
+ update_skill_date(args.skill_name, args.date)
+
+if __name__ == '__main__':
+ main()
diff --git a/scripts/validate-skills.js b/scripts/validate-skills.js
index 606a4867..d7938ac3 100644
--- a/scripts/validate-skills.js
+++ b/scripts/validate-skills.js
@@ -41,6 +41,7 @@ const ALLOWED_FIELDS = new Set([
"metadata",
"allowed-tools",
"package",
+ "date_added",
]);
const USE_SECTION_PATTERNS = [
diff --git a/scripts/validate_skills.py b/scripts/validate_skills.py
index 635a45a9..acceb6f9 100644
--- a/scripts/validate_skills.py
+++ b/scripts/validate_skills.py
@@ -41,6 +41,7 @@ def validate_skills(skills_dir, strict_mode=False):
security_disclaimer_pattern = re.compile(r"AUTHORIZED USE ONLY", re.IGNORECASE)
valid_risk_levels = ["none", "safe", "critical", "offensive", "unknown"]
+ date_pattern = re.compile(r'^\d{4}-\d{2}-\d{2}$') # YYYY-MM-DD format
for root, dirs, files in os.walk(skills_dir):
# Skip .disabled or hidden directories
@@ -91,6 +92,15 @@ def validate_skills(skills_dir, strict_mode=False):
if strict_mode: errors.append(msg.replace("⚠️", "❌"))
else: warnings.append(msg)
+ # Date Added Validation (optional field)
+ if "date_added" in metadata:
+ if not date_pattern.match(metadata["date_added"]):
+ errors.append(f"❌ {rel_path}: Invalid 'date_added' format. Must be YYYY-MM-DD (e.g., '2024-01-15'), got '{metadata['date_added']}'")
+ else:
+ msg = f"ℹ️ {rel_path}: Missing 'date_added' field (optional, but recommended)"
+ if strict_mode: warnings.append(msg)
+ # In normal mode, we just silently skip this
+
# 3. Content Checks (Triggers)
if not has_when_to_use_section(content):
msg = f"⚠️ {rel_path}: Missing '## When to Use' section"
diff --git a/skills_index.json b/skills_index.json
index c0ffd8e0..e947d6fd 100644
--- a/skills_index.json
+++ b/skills_index.json
@@ -6,7 +6,8 @@
"name": "00-andruia-consultant",
"description": "Arquitecto de Soluciones Principal y Consultor Tecnol\u00f3gico de Andru.ia. Diagnostica y traza la hoja de ruta \u00f3ptima para proyectos de IA en espa\u00f1ol.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "20-andruia-niche-intelligence",
@@ -15,7 +16,8 @@
"name": "20-andruia-niche-intelligence",
"description": "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho espec\u00edfico de un proyecto para inyectar conocimientos, regulaciones y est\u00e1ndares \u00fanicos del sector. Act\u00edvalo tras definir el nicho.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "2d-games",
@@ -24,7 +26,8 @@
"name": "2d-games",
"description": "2D game development principles. Sprites, tilemaps, physics, camera.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "3d-games",
@@ -33,7 +36,8 @@
"name": "3d-games",
"description": "3D game development principles. Rendering, shaders, physics, cameras.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "3d-web-experience",
@@ -42,7 +46,8 @@
"name": "3d-web-experience",
"description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ab-test-setup",
@@ -51,7 +56,8 @@
"name": "ab-test-setup",
"description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "accessibility-compliance-accessibility-audit",
@@ -60,7 +66,8 @@
"name": "accessibility-compliance-accessibility-audit",
"description": "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "active-directory-attacks",
@@ -69,7 +76,8 @@
"name": "active-directory-attacks",
"description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "activecampaign-automation",
@@ -78,7 +86,8 @@
"name": "activecampaign-automation",
"description": "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "address-github-comments",
@@ -87,7 +96,8 @@
"name": "address-github-comments",
"description": "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-evaluation",
@@ -96,7 +106,8 @@
"name": "agent-evaluation",
"description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agent-framework-azure-ai-py",
@@ -105,7 +116,8 @@
"name": "agent-framework-azure-ai-py",
"description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-manager-skill",
@@ -114,7 +126,8 @@
"name": "agent-manager-skill",
"description": "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-memory-mcp",
@@ -123,7 +136,8 @@
"name": "agent-memory-mcp",
"description": "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-memory-systems",
@@ -132,7 +146,8 @@
"name": "agent-memory-systems",
"description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agent-orchestration-improve-agent",
@@ -141,7 +156,8 @@
"name": "agent-orchestration-improve-agent",
"description": "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-orchestration-multi-agent-optimize",
@@ -150,7 +166,8 @@
"name": "agent-orchestration-multi-agent-optimize",
"description": "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-tool-builder",
@@ -159,7 +176,8 @@
"name": "agent-tool-builder",
"description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agentfolio",
@@ -168,7 +186,8 @@
"name": "agentfolio",
"description": "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.",
"risk": "unknown",
- "source": "agentfolio.io"
+ "source": "agentfolio.io",
+ "date_added": "2025-02-26"
},
{
"id": "agents-v2-py",
@@ -177,7 +196,8 @@
"name": "agents-v2-py",
"description": "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ai-agent-development",
@@ -186,7 +206,8 @@
"name": "ai-agent-development",
"description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "ai-agents-architect",
@@ -195,16 +216,18 @@
"name": "ai-agents-architect",
"description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ai-engineer",
"path": "skills\\ai-engineer",
"category": "uncategorized",
"name": "ai-engineer",
- "description": "Build production-ready LLM applications, advanced RAG systems, and\nintelligent agents. Implements vector search, multimodal AI, agent\norchestration, and enterprise AI integrations. Use PROACTIVELY for LLM\nfeatures, chatbots, AI agents, or AI-powered applications.\n",
+ "description": "You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ai-ml",
@@ -213,7 +236,8 @@
"name": "ai-ml",
"description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "ai-product",
@@ -222,7 +246,8 @@
"name": "ai-product",
"description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ai-wrapper-product",
@@ -231,7 +256,8 @@
"name": "ai-wrapper-product",
"description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "airflow-dag-patterns",
@@ -240,7 +266,8 @@
"name": "airflow-dag-patterns",
"description": "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "airtable-automation",
@@ -249,7 +276,8 @@
"name": "airtable-automation",
"description": "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "algolia-search",
@@ -258,7 +286,8 @@
"name": "algolia-search",
"description": "Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "algorithmic-art",
@@ -267,7 +296,8 @@
"name": "algorithmic-art",
"description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "amplitude-automation",
@@ -276,16 +306,18 @@
"name": "amplitude-automation",
"description": "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "analytics-tracking",
"path": "skills\\analytics-tracking",
"category": "uncategorized",
"name": "analytics-tracking",
- "description": "Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation\u2014 not just firing events.\n",
+ "description": "You are an expert in **analytics implementation and measurement design**. Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "android-jetpack-compose-expert",
@@ -294,16 +326,18 @@
"name": "android-jetpack-compose-expert",
"description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "angular",
"path": "skills\\angular",
"category": "uncategorized",
"name": "angular",
- "description": "Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.",
+ "description": "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration, and the latest reactive patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-best-practices",
@@ -312,7 +346,8 @@
"name": "angular-best-practices",
"description": "Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-migration",
@@ -321,7 +356,8 @@
"name": "angular-migration",
"description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "angular-state-management",
@@ -330,7 +366,8 @@
"name": "angular-state-management",
"description": "Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-ui-patterns",
@@ -339,7 +376,8 @@
"name": "angular-ui-patterns",
"description": "Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "anti-reversing-techniques",
@@ -348,7 +386,8 @@
"name": "anti-reversing-techniques",
"description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "antigravity-workflows",
@@ -357,7 +396,8 @@
"name": "antigravity-workflows",
"description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
"risk": "none",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "api-design-principles",
@@ -366,7 +406,8 @@
"name": "api-design-principles",
"description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-documentation",
@@ -375,7 +416,8 @@
"name": "api-documentation",
"description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "api-documentation-generator",
@@ -384,16 +426,18 @@
"name": "api-documentation-generator",
"description": "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-documenter",
"path": "skills\\api-documenter",
"category": "uncategorized",
"name": "api-documenter",
- "description": "Master API documentation with OpenAPI 3.1, AI-powered tools, and\nmodern developer experience practices. Create interactive docs, generate SDKs,\nand build comprehensive developer portals. Use PROACTIVELY for API\ndocumentation or developer portal creation.\n",
+ "description": "You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-fuzzing-bug-bounty",
@@ -402,7 +446,8 @@
"name": "api-fuzzing-bug-bounty",
"description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-patterns",
@@ -411,7 +456,8 @@
"name": "api-patterns",
"description": "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-security-best-practices",
@@ -420,7 +466,8 @@
"name": "api-security-best-practices",
"description": "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-security-testing",
@@ -429,7 +476,8 @@
"name": "api-security-testing",
"description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "api-testing-observability-api-mock",
@@ -438,7 +486,8 @@
"name": "api-testing-observability-api-mock",
"description": "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "app-builder",
@@ -447,7 +496,8 @@
"name": "app-builder",
"description": "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "app-store-optimization",
@@ -456,7 +506,8 @@
"name": "app-store-optimization",
"description": "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "appdeploy",
@@ -465,7 +516,8 @@
"name": "appdeploy",
"description": "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.",
"risk": "safe",
- "source": "AppDeploy (MIT)"
+ "source": "AppDeploy (MIT)",
+ "date_added": "2025-02-26"
},
{
"id": "application-performance-performance-optimization",
@@ -474,16 +526,18 @@
"name": "application-performance-performance-optimization",
"description": "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architect-review",
"path": "skills\\architect-review",
"category": "uncategorized",
"name": "architect-review",
- "description": "Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.",
+ "description": "Master software architect specializing in modern architecture",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture",
@@ -492,7 +546,8 @@
"name": "architecture",
"description": "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture-decision-records",
@@ -501,7 +556,8 @@
"name": "architecture-decision-records",
"description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture-patterns",
@@ -510,16 +566,18 @@
"name": "architecture-patterns",
"description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "arm-cortex-expert",
"path": "skills\\arm-cortex-expert",
"category": "uncategorized",
"name": "arm-cortex-expert",
- "description": "Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.\n",
+ "description": "- Working on @arm-cortex-expert tasks or workflows - Needing guidance, best practices, or checklists for @arm-cortex-expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "asana-automation",
@@ -528,7 +586,8 @@
"name": "asana-automation",
"description": "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "async-python-patterns",
@@ -537,7 +596,8 @@
"name": "async-python-patterns",
"description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "attack-tree-construction",
@@ -546,7 +606,8 @@
"name": "attack-tree-construction",
"description": "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "audio-transcriber",
@@ -555,7 +616,8 @@
"name": "audio-transcriber",
"description": "Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "auth-implementation-patterns",
@@ -564,7 +626,8 @@
"name": "auth-implementation-patterns",
"description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "automate-whatsapp",
@@ -573,7 +636,8 @@
"name": "automate-whatsapp",
"description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...",
"risk": "safe",
- "source": "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp"
+ "source": "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp",
+ "date_added": "2025-02-26"
},
{
"id": "autonomous-agent-patterns",
@@ -582,7 +646,8 @@
"name": "autonomous-agent-patterns",
"description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "autonomous-agents",
@@ -591,7 +656,8 @@
"name": "autonomous-agents",
"description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-layout-zafiro",
@@ -600,7 +666,8 @@
"name": "avalonia-layout-zafiro",
"description": "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-viewmodels-zafiro",
@@ -609,7 +676,8 @@
"name": "avalonia-viewmodels-zafiro",
"description": "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-zafiro-development",
@@ -618,7 +686,8 @@
"name": "avalonia-zafiro-development",
"description": "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-compliance-checker",
@@ -627,7 +696,8 @@
"name": "aws-compliance-checker",
"description": "Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-cost-cleanup",
@@ -636,7 +706,8 @@
"name": "aws-cost-cleanup",
"description": "Automated cleanup of unused AWS resources to reduce costs",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-cost-optimizer",
@@ -645,7 +716,8 @@
"name": "aws-cost-optimizer",
"description": "Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-iam-best-practices",
@@ -654,7 +726,8 @@
"name": "aws-iam-best-practices",
"description": "IAM policy review, hardening, and least privilege implementation",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-penetration-testing",
@@ -663,7 +736,8 @@
"name": "aws-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-secrets-rotation",
@@ -672,7 +746,8 @@
"name": "aws-secrets-rotation",
"description": "Automate AWS secrets rotation for RDS, API keys, and credentials",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-security-audit",
@@ -681,7 +756,8 @@
"name": "aws-security-audit",
"description": "Comprehensive AWS security posture assessment using AWS CLI and security best practices",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-serverless",
@@ -690,7 +766,8 @@
"name": "aws-serverless",
"description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "aws-skills",
@@ -699,7 +776,8 @@
"name": "aws-skills",
"description": "AWS development with infrastructure automation and cloud architecture patterns",
"risk": "safe",
- "source": "https://github.com/zxkane/aws-skills"
+ "source": "https://github.com/zxkane/aws-skills",
+ "date_added": "2025-02-26"
},
{
"id": "azd-deployment",
@@ -708,25 +786,28 @@
"name": "azd-deployment",
"description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-agents-persistent-dotnet",
"path": "skills\\azure-ai-agents-persistent-dotnet",
"category": "uncategorized",
"name": "azure-ai-agents-persistent-dotnet",
- "description": "Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: \"PersistentAgentsClient\", \"persistent agents\", \"agent threads\", \"agent runs\", \"streaming agents\", \"function calling agents .NET\".\n",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-agents-persistent-java",
"path": "skills\\azure-ai-agents-persistent-java",
"category": "uncategorized",
"name": "azure-ai-agents-persistent-java",
- "description": "Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.\nTriggers: \"PersistentAgentsClient\", \"persistent agents java\", \"agent threads java\", \"agent runs java\", \"streaming agents java\".\n",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-anomalydetector-java",
@@ -735,7 +816,8 @@
"name": "azure-ai-anomalydetector-java",
"description": "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-java",
@@ -744,16 +826,18 @@
"name": "azure-ai-contentsafety-java",
"description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-py",
"path": "skills\\azure-ai-contentsafety-py",
"category": "uncategorized",
"name": "azure-ai-contentsafety-py",
- "description": "Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.\nTriggers: \"azure-ai-contentsafety\", \"ContentSafetyClient\", \"content moderation\", \"harmful content\", \"text analysis\", \"image analysis\".\n",
+ "description": "Detect harmful user-generated and AI-generated content in applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-ts",
@@ -762,25 +846,28 @@
"name": "azure-ai-contentsafety-ts",
"description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentunderstanding-py",
"path": "skills\\azure-ai-contentunderstanding-py",
"category": "uncategorized",
"name": "azure-ai-contentunderstanding-py",
- "description": "Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.\nTriggers: \"azure-ai-contentunderstanding\", \"ContentUnderstandingClient\", \"multimodal analysis\", \"document extraction\", \"video analysis\", \"audio transcription\".\n",
+ "description": "Multimodal AI service that extracts semantic content from documents, video, audio, and image files for RAG and automated workflows.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-document-intelligence-dotnet",
"path": "skills\\azure-ai-document-intelligence-dotnet",
"category": "uncategorized",
"name": "azure-ai-document-intelligence-dotnet",
- "description": "Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: \"Document Intelligence\", \"DocumentIntelligenceClient\", \"form recognizer\", \"invoice extraction\", \"receipt OCR\", \"document analysis .NET\".\n",
+ "description": "Extract text, tables, and structured data from documents using prebuilt and custom models.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-document-intelligence-ts",
@@ -789,7 +876,8 @@
"name": "azure-ai-document-intelligence-ts",
"description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-formrecognizer-java",
@@ -798,43 +886,48 @@
"name": "azure-ai-formrecognizer-java",
"description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-ml-py",
"path": "skills\\azure-ai-ml-py",
"category": "uncategorized",
"name": "azure-ai-ml-py",
- "description": "Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.\nTriggers: \"azure-ai-ml\", \"MLClient\", \"workspace\", \"model registry\", \"training jobs\", \"datasets\".\n",
+ "description": "Client library for managing Azure ML resources: workspaces, jobs, models, data, and compute.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-openai-dotnet",
"path": "skills\\azure-ai-openai-dotnet",
"category": "uncategorized",
"name": "azure-ai-openai-dotnet",
- "description": "Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: \"Azure OpenAI\", \"AzureOpenAIClient\", \"ChatClient\", \"chat completions .NET\", \"GPT-4\", \"embeddings\", \"DALL-E\", \"Whisper\", \"OpenAI .NET\".\n",
+ "description": "Client library for Azure OpenAI Service providing access to OpenAI models including GPT-4, GPT-4o, embeddings, DALL-E, and Whisper.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-dotnet",
"path": "skills\\azure-ai-projects-dotnet",
"category": "uncategorized",
"name": "azure-ai-projects-dotnet",
- "description": "Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: \"AI Projects\", \"AIProjectClient\", \"Foundry project\", \"versioned agents\", \"evaluations\", \"datasets\", \"connections\", \"deployments .NET\".\n",
+ "description": "High-level SDK for Azure AI Foundry project operations including agents, connections, datasets, deployments, evaluations, and indexes.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-java",
"path": "skills\\azure-ai-projects-java",
"category": "uncategorized",
"name": "azure-ai-projects-java",
- "description": "Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.\nTriggers: \"AIProjectClient java\", \"azure ai projects java\", \"Foundry project java\", \"ConnectionsClient\", \"DatasetsClient\", \"IndexesClient\".\n",
+ "description": "High-level SDK for Azure AI Foundry project management with access to connections, datasets, indexes, and evaluations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-py",
@@ -843,7 +936,8 @@
"name": "azure-ai-projects-py",
"description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-ts",
@@ -852,43 +946,48 @@
"name": "azure-ai-projects-ts",
"description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-textanalytics-py",
"path": "skills\\azure-ai-textanalytics-py",
"category": "uncategorized",
"name": "azure-ai-textanalytics-py",
- "description": "Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.\nTriggers: \"text analytics\", \"sentiment analysis\", \"entity recognition\", \"key phrase\", \"PII detection\", \"TextAnalyticsClient\".\n",
+ "description": "Client library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-transcription-py",
"path": "skills\\azure-ai-transcription-py",
"category": "uncategorized",
"name": "azure-ai-transcription-py",
- "description": "Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.\nTriggers: \"transcription\", \"speech to text\", \"Azure AI Transcription\", \"TranscriptionClient\".\n",
+ "description": "Client library for Azure AI Transcription (speech-to-text) with real-time and batch transcription.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-document-py",
"path": "skills\\azure-ai-translation-document-py",
"category": "uncategorized",
"name": "azure-ai-translation-document-py",
- "description": "Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.\nTriggers: \"document translation\", \"batch translation\", \"translate documents\", \"DocumentTranslationClient\".\n",
+ "description": "Client library for Azure AI Translator document translation service for batch document translation with format preservation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-text-py",
"path": "skills\\azure-ai-translation-text-py",
"category": "uncategorized",
"name": "azure-ai-translation-text-py",
- "description": "Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.\nTriggers: \"text translation\", \"translator\", \"translate text\", \"transliterate\", \"TextTranslationClient\".\n",
+ "description": "Client library for Azure AI Translator text translation service for real-time text translation, transliteration, and language operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-ts",
@@ -897,7 +996,8 @@
"name": "azure-ai-translation-ts",
"description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-vision-imageanalysis-java",
@@ -906,34 +1006,38 @@
"name": "azure-ai-vision-imageanalysis-java",
"description": "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-vision-imageanalysis-py",
"path": "skills\\azure-ai-vision-imageanalysis-py",
"category": "uncategorized",
"name": "azure-ai-vision-imageanalysis-py",
- "description": "Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.\nTriggers: \"image analysis\", \"computer vision\", \"OCR\", \"object detection\", \"ImageAnalysisClient\", \"image caption\".\n",
+ "description": "Client library for Azure AI Vision 4.0 image analysis including captions, tags, objects, OCR, and more.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-dotnet",
"path": "skills\\azure-ai-voicelive-dotnet",
"category": "uncategorized",
"name": "azure-ai-voicelive-dotnet",
- "description": "Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant .NET\", \"bidirectional audio\", \"speech-to-speech\".\n",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-java",
"path": "skills\\azure-ai-voicelive-java",
"category": "uncategorized",
"name": "azure-ai-voicelive-java",
- "description": "Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.\nTriggers: \"VoiceLiveClient java\", \"voice assistant java\", \"real-time voice java\", \"audio streaming java\", \"voice activity detection java\".\n",
+ "description": "Real-time, bidirectional voice conversations with AI assistants using WebSocket technology.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-py",
@@ -942,34 +1046,38 @@
"name": "azure-ai-voicelive-py",
"description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-ts",
"path": "skills\\azure-ai-voicelive-ts",
"category": "uncategorized",
"name": "azure-ai-voicelive-ts",
- "description": "Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant TypeScript\", \"bidirectional audio\", \"speech-to-speech JavaScript\".\n",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI in Node.js and browser environments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-java",
"path": "skills\\azure-appconfiguration-java",
"category": "uncategorized",
"name": "azure-appconfiguration-java",
- "description": "Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.\nTriggers: \"ConfigurationClient java\", \"app configuration java\", \"feature flag java\", \"configuration setting java\", \"azure config java\".\n",
+ "description": "Client library for Azure App Configuration, a managed service for centralizing application configurations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-py",
"path": "skills\\azure-appconfiguration-py",
"category": "uncategorized",
"name": "azure-appconfiguration-py",
- "description": "Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.\nTriggers: \"azure-appconfiguration\", \"AzureAppConfigurationClient\", \"feature flags\", \"configuration\", \"key-value settings\".\n",
+ "description": "Centralized configuration management with feature flags and dynamic settings.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-ts",
@@ -978,7 +1086,8 @@
"name": "azure-appconfiguration-ts",
"description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-callautomation-java",
@@ -987,7 +1096,8 @@
"name": "azure-communication-callautomation-java",
"description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-callingserver-java",
@@ -996,7 +1106,8 @@
"name": "azure-communication-callingserver-java",
"description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-chat-java",
@@ -1005,7 +1116,8 @@
"name": "azure-communication-chat-java",
"description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-common-java",
@@ -1014,7 +1126,8 @@
"name": "azure-communication-common-java",
"description": "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-sms-java",
@@ -1023,25 +1136,28 @@
"name": "azure-communication-sms-java",
"description": "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-compute-batch-java",
"path": "skills\\azure-compute-batch-java",
"category": "uncategorized",
"name": "azure-compute-batch-java",
- "description": "Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.\nTriggers: \"BatchClient java\", \"azure batch java\", \"batch pool java\", \"batch job java\", \"HPC java\", \"parallel computing java\".\n",
+ "description": "Client library for running large-scale parallel and high-performance computing (HPC) batch jobs in Azure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-containerregistry-py",
"path": "skills\\azure-containerregistry-py",
"category": "uncategorized",
"name": "azure-containerregistry-py",
- "description": "Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.\nTriggers: \"azure-containerregistry\", \"ContainerRegistryClient\", \"container images\", \"docker registry\", \"ACR\".\n",
+ "description": "Manage container images, artifacts, and repositories in Azure Container Registry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-db-py",
@@ -1050,43 +1166,48 @@
"name": "azure-cosmos-db-py",
"description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-java",
"path": "skills\\azure-cosmos-java",
"category": "uncategorized",
"name": "azure-cosmos-java",
- "description": "Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.\nTriggers: \"CosmosClient java\", \"CosmosAsyncClient\", \"cosmos database java\", \"cosmosdb java\", \"document database java\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API with global distribution and reactive patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-py",
"path": "skills\\azure-cosmos-py",
"category": "uncategorized",
"name": "azure-cosmos-py",
- "description": "Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db\", \"CosmosClient\", \"container\", \"document\", \"NoSQL\", \"partition key\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-rust",
"path": "skills\\azure-cosmos-rust",
"category": "uncategorized",
"name": "azure-cosmos-rust",
- "description": "Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db rust\", \"CosmosClient rust\", \"container\", \"document rust\", \"NoSQL rust\", \"partition key\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-ts",
"path": "skills\\azure-cosmos-ts",
"category": "uncategorized",
"name": "azure-cosmos-ts",
- "description": "Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: \"Cosmos DB\", \"@azure/cosmos\", \"CosmosClient\", \"document CRUD\", \"NoSQL queries\", \"bulk operations\", \"partition key\", \"container.items\".\n",
+ "description": "Data plane SDK for Azure Cosmos DB NoSQL API operations \u2014 CRUD on documents, queries, bulk operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-data-tables-java",
@@ -1095,25 +1216,28 @@
"name": "azure-data-tables-java",
"description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-data-tables-py",
"path": "skills\\azure-data-tables-py",
"category": "uncategorized",
"name": "azure-data-tables-py",
- "description": "Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.\nTriggers: \"table storage\", \"TableServiceClient\", \"TableClient\", \"entities\", \"PartitionKey\", \"RowKey\".\n",
+ "description": "NoSQL key-value store for structured data (Azure Storage Tables or Cosmos DB Table API).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-dotnet",
"path": "skills\\azure-eventgrid-dotnet",
"category": "uncategorized",
"name": "azure-eventgrid-dotnet",
- "description": "Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: \"Event Grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events .NET\", \"event-driven\", \"pub/sub\".\n",
+ "description": "Client library for publishing events to Azure Event Grid topics, domains, and namespaces.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-java",
@@ -1122,25 +1246,28 @@
"name": "azure-eventgrid-java",
"description": "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-py",
"path": "skills\\azure-eventgrid-py",
"category": "uncategorized",
"name": "azure-eventgrid-py",
- "description": "Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.\nTriggers: \"event grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events\".\n",
+ "description": "Event routing service for building event-driven applications with pub/sub semantics.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-dotnet",
"path": "skills\\azure-eventhub-dotnet",
"category": "uncategorized",
"name": "azure-eventhub-dotnet",
- "description": "Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: \"Event Hubs\", \"event streaming\", \"EventHubProducerClient\", \"EventProcessorClient\", \"send events\", \"receive events\", \"checkpointing\", \"partition\".\n",
+ "description": "High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-java",
@@ -1149,25 +1276,28 @@
"name": "azure-eventhub-java",
"description": "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-py",
"path": "skills\\azure-eventhub-py",
"category": "uncategorized",
"name": "azure-eventhub-py",
- "description": "Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.\nTriggers: \"event hubs\", \"EventHubProducerClient\", \"EventHubConsumerClient\", \"streaming\", \"partitions\".\n",
+ "description": "Big data streaming platform for high-throughput event ingestion.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-rust",
"path": "skills\\azure-eventhub-rust",
"category": "uncategorized",
"name": "azure-eventhub-rust",
- "description": "Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.\nTriggers: \"event hubs rust\", \"ProducerClient rust\", \"ConsumerClient rust\", \"send event rust\", \"streaming rust\".\n",
+ "description": "Client library for Azure Event Hubs \u2014 big data streaming platform and event ingestion service.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-ts",
@@ -1176,7 +1306,8 @@
"name": "azure-eventhub-ts",
"description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-functions",
@@ -1185,16 +1316,18 @@
"name": "azure-functions",
"description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-dotnet",
"path": "skills\\azure-identity-dotnet",
"category": "uncategorized",
"name": "azure-identity-dotnet",
- "description": "Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: \"Azure Identity\", \"DefaultAzureCredential\", \"ManagedIdentityCredential\", \"ClientSecretCredential\", \"authentication .NET\", \"Azure auth\", \"credential chain\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-java",
@@ -1203,25 +1336,28 @@
"name": "azure-identity-java",
"description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-py",
"path": "skills\\azure-identity-py",
"category": "uncategorized",
"name": "azure-identity-py",
- "description": "Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.\nTriggers: \"azure-identity\", \"DefaultAzureCredential\", \"authentication\", \"managed identity\", \"service principal\", \"credential\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-rust",
"path": "skills\\azure-identity-rust",
"category": "uncategorized",
"name": "azure-identity-rust",
- "description": "Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.\nTriggers: \"azure-identity\", \"DeveloperToolsCredential\", \"authentication rust\", \"managed identity rust\", \"credential rust\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-ts",
@@ -1230,25 +1366,28 @@
"name": "azure-identity-ts",
"description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-certificates-rust",
"path": "skills\\azure-keyvault-certificates-rust",
"category": "uncategorized",
"name": "azure-keyvault-certificates-rust",
- "description": "Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.\nTriggers: \"keyvault certificates rust\", \"CertificateClient rust\", \"create certificate rust\", \"import certificate rust\".\n",
+ "description": "Client library for Azure Key Vault Certificates \u2014 secure storage and management of certificates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-keys-rust",
"path": "skills\\azure-keyvault-keys-rust",
"category": "uncategorized",
"name": "azure-keyvault-keys-rust",
- "description": "Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.\nTriggers: \"keyvault keys rust\", \"KeyClient rust\", \"create key rust\", \"encrypt rust\", \"sign rust\".\n",
+ "description": "Client library for Azure Key Vault Keys \u2014 secure storage and management of cryptographic keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-keys-ts",
@@ -1257,25 +1396,28 @@
"name": "azure-keyvault-keys-ts",
"description": "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-py",
"path": "skills\\azure-keyvault-py",
"category": "uncategorized",
"name": "azure-keyvault-py",
- "description": "Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.\nTriggers: \"key vault\", \"SecretClient\", \"KeyClient\", \"CertificateClient\", \"secrets\", \"encryption keys\".\n",
+ "description": "Secure storage and management for secrets, cryptographic keys, and certificates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-secrets-rust",
"path": "skills\\azure-keyvault-secrets-rust",
"category": "uncategorized",
"name": "azure-keyvault-secrets-rust",
- "description": "Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.\nTriggers: \"keyvault secrets rust\", \"SecretClient rust\", \"get secret rust\", \"set secret rust\".\n",
+ "description": "Client library for Azure Key Vault Secrets \u2014 secure storage for passwords, API keys, and other secrets.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-secrets-ts",
@@ -1284,16 +1426,18 @@
"name": "azure-keyvault-secrets-ts",
"description": "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-maps-search-dotnet",
"path": "skills\\azure-maps-search-dotnet",
"category": "uncategorized",
"name": "azure-maps-search-dotnet",
- "description": "Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: \"Azure Maps\", \"MapsSearchClient\", \"MapsRoutingClient\", \"MapsRenderingClient\", \"geocoding .NET\", \"route directions\", \"map tiles\", \"geolocation\".\n",
+ "description": "Azure Maps SDK for .NET providing location-based services: geocoding, routing, rendering, geolocation, and weather.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-messaging-webpubsub-java",
@@ -1302,106 +1446,118 @@
"name": "azure-messaging-webpubsub-java",
"description": "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-messaging-webpubsubservice-py",
"path": "skills\\azure-messaging-webpubsubservice-py",
"category": "uncategorized",
"name": "azure-messaging-webpubsubservice-py",
- "description": "Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.\nTriggers: \"azure-messaging-webpubsubservice\", \"WebPubSubServiceClient\", \"real-time\", \"WebSocket\", \"pub/sub\".\n",
+ "description": "Real-time messaging with WebSocket connections at scale.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apicenter-dotnet",
"path": "skills\\azure-mgmt-apicenter-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-apicenter-dotnet",
- "description": "Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: \"API Center\", \"ApiCenterService\", \"ApiCenterWorkspace\", \"ApiCenterApi\", \"API inventory\", \"API governance\", \"API versioning\", \"API catalog\", \"API discovery\".\n",
+ "description": "Centralized API inventory and governance SDK for managing APIs across your organization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apicenter-py",
"path": "skills\\azure-mgmt-apicenter-py",
"category": "uncategorized",
"name": "azure-mgmt-apicenter-py",
- "description": "Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.\nTriggers: \"azure-mgmt-apicenter\", \"ApiCenterMgmtClient\", \"API Center\", \"API inventory\", \"API governance\".\n",
+ "description": "Manage API inventory, metadata, and governance in Azure API Center.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apimanagement-dotnet",
"path": "skills\\azure-mgmt-apimanagement-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-apimanagement-dotnet",
- "description": "Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: \"API Management\", \"APIM service\", \"create APIM\", \"manage APIs\", \"ApiManagementServiceResource\", \"API policies\", \"APIM products\", \"APIM subscriptions\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure API Management resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apimanagement-py",
"path": "skills\\azure-mgmt-apimanagement-py",
"category": "uncategorized",
"name": "azure-mgmt-apimanagement-py",
- "description": "Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.\nTriggers: \"azure-mgmt-apimanagement\", \"ApiManagementClient\", \"APIM\", \"API gateway\", \"API Management\".\n",
+ "description": "Manage Azure API Management services, APIs, products, and policies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-applicationinsights-dotnet",
"path": "skills\\azure-mgmt-applicationinsights-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-applicationinsights-dotnet",
- "description": "Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: \"Application Insights\", \"ApplicationInsights\", \"App Insights\", \"APM\", \"application monitoring\", \"web tests\", \"availability tests\", \"workbooks\".\n",
+ "description": "Azure Resource Manager SDK for managing Application Insights resources for application performance monitoring.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
"path": "skills\\azure-mgmt-arizeaiobservabilityeval-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "description": "Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations \non Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability \ninto .NET applications. Triggers: \"Arize AI\", \"ML observability\", \"ArizeAIObservabilityEval\", \"Arize organization\".\n",
+ "description": ".NET SDK for managing Arize AI Observability and Evaluation resources on Azure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-botservice-dotnet",
"path": "skills\\azure-mgmt-botservice-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-botservice-dotnet",
- "description": "Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: \"Bot Service\", \"BotResource\", \"Azure Bot\", \"DirectLine channel\", \"Teams channel\", \"bot management .NET\", \"create bot\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Bot Service resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-botservice-py",
"path": "skills\\azure-mgmt-botservice-py",
"category": "uncategorized",
"name": "azure-mgmt-botservice-py",
- "description": "Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.\nTriggers: \"azure-mgmt-botservice\", \"AzureBotService\", \"bot management\", \"conversational AI\", \"bot channels\".\n",
+ "description": "Manage Azure Bot Service resources including bots, channels, and connections.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-fabric-dotnet",
"path": "skills\\azure-mgmt-fabric-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-fabric-dotnet",
- "description": "Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: \"Fabric capacity\", \"create capacity\", \"suspend capacity\", \"resume capacity\", \"Fabric SKU\", \"provision Fabric\", \"ARM Fabric\", \"FabricCapacityResource\".\n",
+ "description": "Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-fabric-py",
"path": "skills\\azure-mgmt-fabric-py",
"category": "uncategorized",
"name": "azure-mgmt-fabric-py",
- "description": "Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.\nTriggers: \"azure-mgmt-fabric\", \"FabricMgmtClient\", \"Fabric capacity\", \"Microsoft Fabric\", \"Power BI capacity\".\n",
+ "description": "Manage Microsoft Fabric capacities and resources programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-mongodbatlas-dotnet",
@@ -1410,16 +1566,18 @@
"name": "azure-mgmt-mongodbatlas-dotnet",
"description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-weightsandbiases-dotnet",
"path": "skills\\azure-mgmt-weightsandbiases-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-weightsandbiases-dotnet",
- "description": "Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: \"Weights and Biases\", \"W&B\", \"WeightsAndBiases\", \"ML experiment tracking\", \"model registry\", \"experiment management\", \"wandb\".\n",
+ "description": "Azure Resource Manager SDK for deploying and managing Weights & Biases ML experiment tracking instances via Azure Marketplace.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-microsoft-playwright-testing-ts",
@@ -1428,52 +1586,58 @@
"name": "azure-microsoft-playwright-testing-ts",
"description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-ingestion-java",
"path": "skills\\azure-monitor-ingestion-java",
"category": "uncategorized",
"name": "azure-monitor-ingestion-java",
- "description": "Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).\nTriggers: \"LogsIngestionClient java\", \"azure monitor ingestion java\", \"custom logs java\", \"DCR java\", \"data collection rule java\".\n",
+ "description": "Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-ingestion-py",
"path": "skills\\azure-monitor-ingestion-py",
"category": "uncategorized",
"name": "azure-monitor-ingestion-py",
- "description": "Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.\nTriggers: \"azure-monitor-ingestion\", \"LogsIngestionClient\", \"custom logs\", \"DCR\", \"data collection rule\", \"Log Analytics\".\n",
+ "description": "Send custom logs to Azure Monitor Log Analytics workspace using the Logs Ingestion API.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-exporter-java",
"path": "skills\\azure-monitor-opentelemetry-exporter-java",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-exporter-java",
- "description": "Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.\nTriggers: \"AzureMonitorExporter java\", \"opentelemetry azure java\", \"application insights java otel\", \"azure monitor tracing java\".\nNote: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.\n",
+ "description": "> **\u26a0\ufe0f DEPRECATION NOTICE**: This package is deprecated. Migrate to `azure-monitor-opentelemetry-autoconfigure`. > > See [Migration Guide](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/MIGRATIO",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-exporter-py",
"path": "skills\\azure-monitor-opentelemetry-exporter-py",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-exporter-py",
- "description": "Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.\nTriggers: \"azure-monitor-opentelemetry-exporter\", \"AzureMonitorTraceExporter\", \"AzureMonitorMetricExporter\", \"AzureMonitorLogExporter\".\n",
+ "description": "Low-level exporter for sending OpenTelemetry traces, metrics, and logs to Application Insights.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-py",
"path": "skills\\azure-monitor-opentelemetry-py",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-py",
- "description": "Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.\nTriggers: \"azure-monitor-opentelemetry\", \"configure_azure_monitor\", \"Application Insights\", \"OpenTelemetry distro\", \"auto-instrumentation\".\n",
+ "description": "One-line setup for Application Insights with OpenTelemetry auto-instrumentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-ts",
@@ -1482,115 +1646,128 @@
"name": "azure-monitor-opentelemetry-ts",
"description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-query-java",
"path": "skills\\azure-monitor-query-java",
"category": "uncategorized",
"name": "azure-monitor-query-java",
- "description": "Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.\nTriggers: \"LogsQueryClient java\", \"MetricsQueryClient java\", \"kusto query java\", \"log analytics java\", \"azure monitor query java\".\nNote: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.\n",
+ "description": "> **DEPRECATION NOTICE**: This package is deprecated in favor of: > - `azure-monitor-query-logs` \u2014 For Log Analytics queries > - `azure-monitor-query-metrics` \u2014 For metrics queries > > See migration guides: [Logs Migration](https://github.com/Azure/a",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-query-py",
"path": "skills\\azure-monitor-query-py",
"category": "uncategorized",
"name": "azure-monitor-query-py",
- "description": "Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.\nTriggers: \"azure-monitor-query\", \"LogsQueryClient\", \"MetricsQueryClient\", \"Log Analytics\", \"Kusto queries\", \"Azure metrics\".\n",
+ "description": "Query logs and metrics from Azure Monitor and Log Analytics workspaces.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-postgres-ts",
"path": "skills\\azure-postgres-ts",
"category": "uncategorized",
"name": "azure-postgres-ts",
- "description": "Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: \"PostgreSQL\", \"postgres\", \"pg client\", \"node-postgres\", \"Azure PostgreSQL connection\", \"PostgreSQL TypeScript\", \"pg Pool\", \"passwordless postgres\".\n",
+ "description": "Connect to Azure Database for PostgreSQL Flexible Server using the `pg` (node-postgres) package with support for password and Microsoft Entra ID (passwordless) authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-cosmosdb-dotnet",
"path": "skills\\azure-resource-manager-cosmosdb-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-cosmosdb-dotnet",
- "description": "Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: \"Cosmos DB account\", \"create Cosmos account\", \"manage Cosmos resources\", \"ARM Cosmos\", \"CosmosDBAccountResource\", \"provision Cosmos DB\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Cosmos DB resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-durabletask-dotnet",
"path": "skills\\azure-resource-manager-durabletask-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-durabletask-dotnet",
- "description": "Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: \"Durable Task Scheduler\", \"create scheduler\", \"task hub\", \"DurableTaskSchedulerResource\", \"provision Durable Task\", \"orchestration scheduler\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-mysql-dotnet",
"path": "skills\\azure-resource-manager-mysql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-mysql-dotnet",
- "description": "Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"MySQL\", \"MySqlFlexibleServer\", \"MySQL Flexible Server\", \"Azure Database for MySQL\", \"MySQL database management\", \"MySQL firewall\", \"MySQL backup\".\n",
+ "description": "Azure Resource Manager SDK for managing MySQL Flexible Server deployments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-playwright-dotnet",
"path": "skills\\azure-resource-manager-playwright-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-playwright-dotnet",
- "description": "Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: \"Playwright workspace\", \"create Playwright Testing workspace\", \"manage Playwright resources\", \"ARM Playwright\", \"PlaywrightWorkspaceResource\", \"provision Playwright Testing\".\n",
+ "description": "Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-postgresql-dotnet",
"path": "skills\\azure-resource-manager-postgresql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-postgresql-dotnet",
- "description": "Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"PostgreSQL\", \"PostgreSqlFlexibleServer\", \"PostgreSQL Flexible Server\", \"Azure Database for PostgreSQL\", \"PostgreSQL database management\", \"PostgreSQL firewall\", \"PostgreSQL backup\", \"Postgres\".\n",
+ "description": "Azure Resource Manager SDK for managing PostgreSQL Flexible Server deployments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-redis-dotnet",
"path": "skills\\azure-resource-manager-redis-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-redis-dotnet",
- "description": "Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: \"Redis cache\", \"create Redis\", \"manage Redis\", \"ARM Redis\", \"RedisResource\", \"provision Redis\", \"Azure Cache for Redis\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Cache for Redis resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-sql-dotnet",
"path": "skills\\azure-resource-manager-sql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-sql-dotnet",
- "description": "Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: \"SQL server\", \"create SQL database\", \"manage SQL resources\", \"ARM SQL\", \"SqlServerResource\", \"provision Azure SQL\", \"elastic pool\", \"firewall rule\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-dotnet",
"path": "skills\\azure-search-documents-dotnet",
"category": "uncategorized",
"name": "azure-search-documents-dotnet",
- "description": "Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: \"Azure Search .NET\", \"SearchClient\", \"SearchIndexClient\", \"vector search C#\", \"semantic search .NET\", \"hybrid search\", \"Azure.Search.Documents\".\n",
+ "description": "Build search applications with full-text, vector, semantic, and hybrid search capabilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-py",
"path": "skills\\azure-search-documents-py",
"category": "uncategorized",
"name": "azure-search-documents-py",
- "description": "Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.\nTriggers: \"azure-search-documents\", \"SearchClient\", \"SearchIndexClient\", \"vector search\", \"hybrid search\", \"semantic search\".\n",
+ "description": "Full-text, vector, and hybrid search with AI enrichment capabilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-ts",
@@ -1599,16 +1776,18 @@
"name": "azure-search-documents-ts",
"description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-keys-dotnet",
"path": "skills\\azure-security-keyvault-keys-dotnet",
"category": "uncategorized",
"name": "azure-security-keyvault-keys-dotnet",
- "description": "Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: \"Key Vault keys\", \"KeyClient\", \"CryptographyClient\", \"RSA key\", \"EC key\", \"encrypt decrypt .NET\", \"key rotation\", \"HSM\".\n",
+ "description": "Client library for managing cryptographic keys in Azure Key Vault and Managed HSM.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-keys-java",
@@ -1617,7 +1796,8 @@
"name": "azure-security-keyvault-keys-java",
"description": "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-secrets-java",
@@ -1626,25 +1806,28 @@
"name": "azure-security-keyvault-secrets-java",
"description": "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-dotnet",
"path": "skills\\azure-servicebus-dotnet",
"category": "uncategorized",
"name": "azure-servicebus-dotnet",
- "description": "Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: \"Service Bus\", \"ServiceBusClient\", \"ServiceBusSender\", \"ServiceBusReceiver\", \"ServiceBusProcessor\", \"message queue\", \"pub/sub .NET\", \"dead letter queue\".\n",
+ "description": "Enterprise messaging SDK for reliable message delivery with queues, topics, subscriptions, and sessions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-py",
"path": "skills\\azure-servicebus-py",
"category": "uncategorized",
"name": "azure-servicebus-py",
- "description": "Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.\nTriggers: \"service bus\", \"ServiceBusClient\", \"queue\", \"topic\", \"subscription\", \"message broker\".\n",
+ "description": "Enterprise messaging for reliable cloud communication with queues and pub/sub topics.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-ts",
@@ -1653,16 +1836,18 @@
"name": "azure-servicebus-ts",
"description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-speech-to-text-rest-py",
"path": "skills\\azure-speech-to-text-rest-py",
"category": "uncategorized",
"name": "azure-speech-to-text-rest-py",
- "description": "Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.\nTriggers: \"speech to text REST\", \"short audio transcription\", \"speech recognition REST API\", \"STT REST\", \"recognize speech REST\".\nDO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.\n",
+ "description": "Simple REST API for speech-to-text transcription of short audio files (up to 60 seconds). No SDK required - just HTTP requests.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-java",
@@ -1671,79 +1856,88 @@
"name": "azure-storage-blob-java",
"description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-py",
"path": "skills\\azure-storage-blob-py",
"category": "uncategorized",
"name": "azure-storage-blob-py",
- "description": "Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.\nTriggers: \"blob storage\", \"BlobServiceClient\", \"ContainerClient\", \"BlobClient\", \"upload blob\", \"download blob\".\n",
+ "description": "Client library for Azure Blob Storage \u2014 object storage for unstructured data.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-rust",
"path": "skills\\azure-storage-blob-rust",
"category": "uncategorized",
"name": "azure-storage-blob-rust",
- "description": "Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.\nTriggers: \"blob storage rust\", \"BlobClient rust\", \"upload blob rust\", \"download blob rust\", \"container rust\".\n",
+ "description": "Client library for Azure Blob Storage \u2014 Microsoft's object storage solution for the cloud.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-ts",
"path": "skills\\azure-storage-blob-ts",
"category": "uncategorized",
"name": "azure-storage-blob-ts",
- "description": "Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: \"blob storage\", \"@azure/storage-blob\", \"BlobServiceClient\", \"ContainerClient\", \"upload blob\", \"download blob\", \"SAS token\", \"block blob\".\n",
+ "description": "SDK for Azure Blob Storage operations \u2014 upload, download, list, and manage blobs and containers.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-datalake-py",
"path": "skills\\azure-storage-file-datalake-py",
"category": "uncategorized",
"name": "azure-storage-file-datalake-py",
- "description": "Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.\nTriggers: \"data lake\", \"DataLakeServiceClient\", \"FileSystemClient\", \"ADLS Gen2\", \"hierarchical namespace\".\n",
+ "description": "Hierarchical file system for big data analytics workloads.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-share-py",
"path": "skills\\azure-storage-file-share-py",
"category": "uncategorized",
"name": "azure-storage-file-share-py",
- "description": "Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.\nTriggers: \"azure-storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"file share\", \"SMB\".\n",
+ "description": "Manage SMB file shares for cloud-native and lift-and-shift scenarios.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-share-ts",
"path": "skills\\azure-storage-file-share-ts",
"category": "uncategorized",
"name": "azure-storage-file-share-ts",
- "description": "Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: \"file share\", \"@azure/storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"SMB\", \"Azure Files\".\n",
+ "description": "SDK for Azure File Share operations \u2014 SMB file shares, directories, and file operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-queue-py",
"path": "skills\\azure-storage-queue-py",
"category": "uncategorized",
"name": "azure-storage-queue-py",
- "description": "Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.\nTriggers: \"queue storage\", \"QueueServiceClient\", \"QueueClient\", \"message queue\", \"dequeue\".\n",
+ "description": "Simple, cost-effective message queuing for asynchronous communication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-queue-ts",
"path": "skills\\azure-storage-queue-ts",
"category": "uncategorized",
"name": "azure-storage-queue-ts",
- "description": "Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: \"queue storage\", \"@azure/storage-queue\", \"QueueServiceClient\", \"QueueClient\", \"send message\", \"receive message\", \"dequeue\", \"visibility timeout\".\n",
+ "description": "SDK for Azure Queue Storage operations \u2014 send, receive, peek, and manage messages in queues.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-web-pubsub-ts",
@@ -1752,16 +1946,18 @@
"name": "azure-web-pubsub-ts",
"description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-architect",
"path": "skills\\backend-architect",
"category": "uncategorized",
"name": "backend-architect",
- "description": "Expert backend architect specializing in scalable API design,\nmicroservices architecture, and distributed systems. Masters REST/GraphQL/gRPC\nAPIs, event-driven architectures, service mesh patterns, and modern backend\nframeworks. Handles service boundary definition, inter-service communication,\nresilience patterns, and observability. Use PROACTIVELY when creating new\nbackend services or APIs.\n",
+ "description": "You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-dev-guidelines",
@@ -1770,7 +1966,8 @@
"name": "backend-dev-guidelines",
"description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-development-feature-development",
@@ -1779,16 +1976,18 @@
"name": "backend-development-feature-development",
"description": "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-security-coder",
"path": "skills\\backend-security-coder",
"category": "uncategorized",
"name": "backend-security-coder",
- "description": "Expert in secure backend coding practices specializing in input\nvalidation, authentication, and API security. Use PROACTIVELY for backend\nsecurity implementations or security code reviews.\n",
+ "description": "- Working on backend security coder tasks or workflows - Needing guidance, best practices, or checklists for backend security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backtesting-frameworks",
@@ -1797,7 +1996,8 @@
"name": "backtesting-frameworks",
"description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bamboohr-automation",
@@ -1806,7 +2006,8 @@
"name": "bamboohr-automation",
"description": "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "base",
@@ -1815,7 +2016,8 @@
"name": "base",
"description": "Database management, forms, reports, and data operations with LibreOffice Base.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "basecamp-automation",
@@ -1824,7 +2026,8 @@
"name": "basecamp-automation",
"description": "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-defensive-patterns",
@@ -1833,7 +2036,8 @@
"name": "bash-defensive-patterns",
"description": "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-linux",
@@ -1842,16 +2046,18 @@
"name": "bash-linux",
"description": "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-pro",
"path": "skills\\bash-pro",
"category": "uncategorized",
"name": "bash-pro",
- "description": "Master of defensive Bash scripting for production automation, CI/CD\npipelines, and system utilities. Expert in safe, portable, and testable shell\nscripts.\n",
+ "description": "- Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-scripting",
@@ -1860,7 +2066,8 @@
"name": "bash-scripting",
"description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "bats-testing-patterns",
@@ -1869,7 +2076,8 @@
"name": "bats-testing-patterns",
"description": "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bazel-build-optimization",
@@ -1878,7 +2086,8 @@
"name": "bazel-build-optimization",
"description": "Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "beautiful-prose",
@@ -1887,7 +2096,8 @@
"name": "beautiful-prose",
"description": "Hard-edged writing style contract for timeless, forceful English prose without AI tics",
"risk": "safe",
- "source": "https://github.com/SHADOWPR0/beautiful_prose"
+ "source": "https://github.com/SHADOWPR0/beautiful_prose",
+ "date_added": "2025-02-26"
},
{
"id": "behavioral-modes",
@@ -1896,7 +2106,8 @@
"name": "behavioral-modes",
"description": "AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bevy-ecs-expert",
@@ -1905,7 +2116,8 @@
"name": "bevy-ecs-expert",
"description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "billing-automation",
@@ -1914,7 +2126,8 @@
"name": "billing-automation",
"description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "binary-analysis-patterns",
@@ -1923,7 +2136,8 @@
"name": "binary-analysis-patterns",
"description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bitbucket-automation",
@@ -1932,16 +2146,18 @@
"name": "bitbucket-automation",
"description": "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "blockchain-developer",
"path": "skills\\blockchain-developer",
"category": "uncategorized",
"name": "blockchain-developer",
- "description": "Build production-ready Web3 applications, smart contracts, and\ndecentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and\nenterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3\napps, DeFi protocols, or blockchain infrastructure.\n",
+ "description": "- Working on blockchain developer tasks or workflows - Needing guidance, best practices, or checklists for blockchain developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "blockrun",
@@ -1950,7 +2166,8 @@
"name": "blockrun",
"description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "box-automation",
@@ -1959,7 +2176,8 @@
"name": "box-automation",
"description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brainstorming",
@@ -1968,7 +2186,8 @@
"name": "brainstorming",
"description": "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brand-guidelines-anthropic",
@@ -1977,7 +2196,8 @@
"name": "brand-guidelines-anthropic",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brand-guidelines-community",
@@ -1986,7 +2206,8 @@
"name": "brand-guidelines-community",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brevo-automation",
@@ -1995,7 +2216,8 @@
"name": "brevo-automation",
"description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "broken-authentication",
@@ -2004,7 +2226,8 @@
"name": "broken-authentication",
"description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "browser-automation",
@@ -2013,7 +2236,8 @@
"name": "browser-automation",
"description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "browser-extension-builder",
@@ -2022,7 +2246,8 @@
"name": "browser-extension-builder",
"description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "bullmq-specialist",
@@ -2031,7 +2256,8 @@
"name": "bullmq-specialist",
"description": "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "bun-development",
@@ -2040,7 +2266,8 @@
"name": "bun-development",
"description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "burp-suite-testing",
@@ -2049,16 +2276,18 @@
"name": "burp-suite-testing",
"description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "business-analyst",
"path": "skills\\business-analyst",
"category": "uncategorized",
"name": "business-analyst",
- "description": "Master modern business analysis with AI-powered analytics,\nreal-time dashboards, and data-driven insights. Build comprehensive KPI\nframeworks, predictive models, and strategic recommendations. Use PROACTIVELY\nfor business intelligence or strategic analysis.\n",
+ "description": "- Working on business analyst tasks or workflows - Needing guidance, best practices, or checklists for business analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "busybox-on-windows",
@@ -2067,16 +2296,18 @@
"name": "busybox-on-windows",
"description": "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c-pro",
"path": "skills\\c-pro",
"category": "uncategorized",
"name": "c-pro",
- "description": "Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.",
+ "description": "Write efficient C code with proper memory management, pointer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-architecture-c4-architecture",
@@ -2085,43 +2316,48 @@
"name": "c4-architecture-c4-architecture",
"description": "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-code",
"path": "skills\\c4-code",
"category": "uncategorized",
"name": "c4-code",
- "description": "Expert C4 Code-level documentation specialist. Analyzes code\ndirectories to create comprehensive C4 code-level documentation including\nfunction signatures, arguments, dependencies, and code structure. Use when\ndocumenting code at the lowest C4 level for individual directories and code\nmodules.\n",
+ "description": "- Working on c4 code level: [directory name] tasks or workflows - Needing guidance, best practices, or checklists for c4 code level: [directory name]",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-component",
"path": "skills\\c4-component",
"category": "uncategorized",
"name": "c4-component",
- "description": "Expert C4 Component-level documentation specialist. Synthesizes C4\nCode-level documentation into Component-level architecture, defining component\nboundaries, interfaces, and relationships. Creates component diagrams and\ndocumentation. Use when synthesizing code-level documentation into logical\ncomponents.\n",
+ "description": "- Working on c4 component level: [component name] tasks or workflows - Needing guidance, best practices, or checklists for c4 component level: [component name]",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-container",
"path": "skills\\c4-container",
"category": "uncategorized",
"name": "c4-container",
- "description": "Expert C4 Container-level documentation specialist. Synthesizes\nComponent-level documentation into Container-level architecture, mapping\ncomponents to deployment units, documenting container interfaces as APIs, and\ncreating container diagrams. Use when synthesizing components into deployment\ncontainers and documenting system deployment architecture.\n",
+ "description": "- Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-context",
"path": "skills\\c4-context",
"category": "uncategorized",
"name": "c4-context",
- "description": "Expert C4 Context-level documentation specialist. Creates\nhigh-level system context diagrams, documents personas, user journeys, system\nfeatures, and external dependencies. Synthesizes container and component\ndocumentation with system documentation to create comprehensive context-level\narchitecture. Use when creating the highest-level C4 system context\ndocumentation.\n",
+ "description": "- Working on c4 context level: system context tasks or workflows - Needing guidance, best practices, or checklists for c4 context level: system context",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cal-com-automation",
@@ -2130,7 +2366,8 @@
"name": "cal-com-automation",
"description": "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "calc",
@@ -2139,7 +2376,8 @@
"name": "calc",
"description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "calendly-automation",
@@ -2148,7 +2386,8 @@
"name": "calendly-automation",
"description": "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "canva-automation",
@@ -2157,7 +2396,8 @@
"name": "canva-automation",
"description": "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "canvas-design",
@@ -2166,16 +2406,18 @@
"name": "canvas-design",
"description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "carrier-relationship-management",
"path": "skills\\carrier-relationship-management",
"category": "uncategorized",
"name": "carrier-relationship-management",
- "description": "Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting. Use when managing carriers, negotiating rates, evaluating carrier performance, or building freight strategies.\n",
+ "description": "Use this skill when building and managing a carrier network, conducting freight RFPs, negotiating linehaul and accessorial rates, tracking carrier KPIs via scorecards, or ensuring regulatory compliance of transportation partners.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-backend-patterns",
@@ -2184,7 +2426,8 @@
"name": "cc-skill-backend-patterns",
"description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-clickhouse-io",
@@ -2193,7 +2436,8 @@
"name": "cc-skill-clickhouse-io",
"description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-coding-standards",
@@ -2202,7 +2446,8 @@
"name": "cc-skill-coding-standards",
"description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-continuous-learning",
@@ -2211,7 +2456,8 @@
"name": "cc-skill-continuous-learning",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-frontend-patterns",
@@ -2220,7 +2466,8 @@
"name": "cc-skill-frontend-patterns",
"description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-project-guidelines-example",
@@ -2229,7 +2476,8 @@
"name": "cc-skill-project-guidelines-example",
"description": "Project Guidelines Skill (Example)",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-security-review",
@@ -2238,7 +2486,8 @@
"name": "cc-skill-security-review",
"description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-strategic-compact",
@@ -2247,7 +2496,8 @@
"name": "cc-skill-strategic-compact",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cdk-patterns",
@@ -2256,7 +2506,8 @@
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "changelog-automation",
@@ -2265,7 +2516,8 @@
"name": "changelog-automation",
"description": "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "chrome-extension-developer",
@@ -2274,7 +2526,8 @@
"name": "chrome-extension-developer",
"description": "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cicd-automation-workflow-automate",
@@ -2283,7 +2536,8 @@
"name": "cicd-automation-workflow-automate",
"description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "circleci-automation",
@@ -2292,7 +2546,8 @@
"name": "circleci-automation",
"description": "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "clarity-gate",
@@ -2301,7 +2556,8 @@
"name": "clarity-gate",
"description": "Pre-ingestion verification for epistemic quality in RAG systems with 9-point verification and Two-Round HITL workflow",
"risk": "safe",
- "source": "https://github.com/frmoretto/clarity-gate"
+ "source": "https://github.com/frmoretto/clarity-gate",
+ "date_added": "2025-02-26"
},
{
"id": "claude-ally-health",
@@ -2310,7 +2566,8 @@
"name": "claude-ally-health",
"description": "A health assistant skill for medical information analysis, symptom tracking, and wellness guidance.",
"risk": "safe",
- "source": "https://github.com/huifer/Claude-Ally-Health"
+ "source": "https://github.com/huifer/Claude-Ally-Health",
+ "date_added": "2025-02-26"
},
{
"id": "claude-code-guide",
@@ -2319,7 +2576,8 @@
"name": "claude-code-guide",
"description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "claude-d3js-skill",
@@ -2328,7 +2586,8 @@
"name": "claude-d3js-skill",
"description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "claude-scientific-skills",
@@ -2337,7 +2596,8 @@
"name": "claude-scientific-skills",
"description": "Scientific research and analysis skills",
"risk": "safe",
- "source": "https://github.com/K-Dense-AI/claude-scientific-skills"
+ "source": "https://github.com/K-Dense-AI/claude-scientific-skills",
+ "date_added": "2025-02-26"
},
{
"id": "claude-speed-reader",
@@ -2346,7 +2606,8 @@
"name": "claude-speed-reader",
"description": "-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting",
"risk": "safe",
- "source": "https://github.com/SeanZoR/claude-speed-reader"
+ "source": "https://github.com/SeanZoR/claude-speed-reader",
+ "date_added": "2025-02-26"
},
{
"id": "claude-win11-speckit-update-skill",
@@ -2355,7 +2616,8 @@
"name": "claude-win11-speckit-update-skill",
"description": "Windows 11 system management",
"risk": "safe",
- "source": "https://github.com/NotMyself/claude-win11-speckit-update-skill"
+ "source": "https://github.com/NotMyself/claude-win11-speckit-update-skill",
+ "date_added": "2025-02-26"
},
{
"id": "clean-code",
@@ -2364,7 +2626,8 @@
"name": "clean-code",
"description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...",
"risk": "safe",
- "source": "ClawForge (https://github.com/jackjin1997/ClawForge)"
+ "source": "ClawForge (https://github.com/jackjin1997/ClawForge)",
+ "date_added": "2025-02-26"
},
{
"id": "clerk-auth",
@@ -2373,7 +2636,8 @@
"name": "clerk-auth",
"description": "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "clickup-automation",
@@ -2382,7 +2646,8 @@
"name": "clickup-automation",
"description": "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "close-automation",
@@ -2391,16 +2656,18 @@
"name": "close-automation",
"description": "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-architect",
"path": "skills\\cloud-architect",
"category": "uncategorized",
"name": "cloud-architect",
- "description": "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud\ninfrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost\noptimization, and modern architectural patterns. Masters serverless,\nmicroservices, security, compliance, and disaster recovery. Use PROACTIVELY\nfor cloud architecture, cost optimization, migration planning, or multi-cloud\nstrategies.\n",
+ "description": "- Working on cloud architect tasks or workflows - Needing guidance, best practices, or checklists for cloud architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-devops",
@@ -2409,7 +2676,8 @@
"name": "cloud-devops",
"description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-penetration-testing",
@@ -2418,7 +2686,8 @@
"name": "cloud-penetration-testing",
"description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloudflare-workers-expert",
@@ -2427,7 +2696,8 @@
"name": "cloudflare-workers-expert",
"description": "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloudformation-best-practices",
@@ -2436,7 +2706,8 @@
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "coda-automation",
@@ -2445,7 +2716,8 @@
"name": "coda-automation",
"description": "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-documentation-code-explain",
@@ -2454,7 +2726,8 @@
"name": "code-documentation-code-explain",
"description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-documentation-doc-generate",
@@ -2463,7 +2736,8 @@
"name": "code-documentation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-context-restore",
@@ -2472,7 +2746,8 @@
"name": "code-refactoring-context-restore",
"description": "Use when working with code refactoring context restore",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-refactor-clean",
@@ -2481,7 +2756,8 @@
"name": "code-refactoring-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-tech-debt",
@@ -2490,7 +2766,8 @@
"name": "code-refactoring-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-ai-ai-review",
@@ -2499,7 +2776,8 @@
"name": "code-review-ai-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-checklist",
@@ -2508,7 +2786,8 @@
"name": "code-review-checklist",
"description": "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-excellence",
@@ -2517,16 +2796,18 @@
"name": "code-review-excellence",
"description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-reviewer",
"path": "skills\\code-reviewer",
"category": "uncategorized",
"name": "code-reviewer",
- "description": "Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.",
+ "description": "Elite code review expert specializing in modern AI-powered code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-deps-audit",
@@ -2535,7 +2816,8 @@
"name": "codebase-cleanup-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-refactor-clean",
@@ -2544,7 +2826,8 @@
"name": "codebase-cleanup-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-tech-debt",
@@ -2553,7 +2836,8 @@
"name": "codebase-cleanup-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codex-review",
@@ -2562,7 +2846,8 @@
"name": "codex-review",
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "commit",
@@ -2571,16 +2856,18 @@
"name": "commit",
"description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit",
+ "date_added": "2025-02-26"
},
{
"id": "competitive-landscape",
"path": "skills\\competitive-landscape",
"category": "uncategorized",
"name": "competitive-landscape",
- "description": "This skill should be used when the user asks to \\\\\\\"analyze\ncompetitors\", \"assess competitive landscape\", \"identify differentiation\",\n\"evaluate market positioning\", \"apply Porter's Five Forces\", or requests\ncompetitive strategy analysis.\n",
+ "description": "Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "competitor-alternatives",
@@ -2589,7 +2876,8 @@
"name": "competitor-alternatives",
"description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "comprehensive-review-full-review",
@@ -2598,7 +2886,8 @@
"name": "comprehensive-review-full-review",
"description": "Use when working with comprehensive review full review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "comprehensive-review-pr-enhance",
@@ -2607,7 +2896,8 @@
"name": "comprehensive-review-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "computer-use-agents",
@@ -2616,7 +2906,8 @@
"name": "computer-use-agents",
"description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "computer-vision-expert",
@@ -2625,7 +2916,8 @@
"name": "computer-vision-expert",
"description": "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "concise-planning",
@@ -2634,7 +2926,8 @@
"name": "concise-planning",
"description": "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-implement",
@@ -2643,7 +2936,8 @@
"name": "conductor-implement",
"description": "Execute tasks from a track's implementation plan following TDD workflow",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-manage",
@@ -2652,7 +2946,8 @@
"name": "conductor-manage",
"description": "Manage track lifecycle: archive, restore, delete, rename, and cleanup",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-new-track",
@@ -2661,7 +2956,8 @@
"name": "conductor-new-track",
"description": "Create a new track with specification and phased implementation plan",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-revert",
@@ -2670,16 +2966,18 @@
"name": "conductor-revert",
"description": "Git-aware undo by logical work unit (track, phase, or task)",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-setup",
"path": "skills\\conductor-setup",
"category": "uncategorized",
"name": "conductor-setup",
- "description": "Initialize project with Conductor artifacts (product definition,\ntech stack, workflow, style guides)\n",
+ "description": "Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-status",
@@ -2688,16 +2986,18 @@
"name": "conductor-status",
"description": "Display project status, active tracks, and next actions",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-validator",
"path": "skills\\conductor-validator",
"category": "uncategorized",
"name": "conductor-validator",
- "description": "Validates Conductor project artifacts for completeness,\nconsistency, and correctness. Use after setup, when diagnosing issues, or\nbefore implementation to verify project context.\n",
+ "description": "ls -la conductor/",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "confluence-automation",
@@ -2706,7 +3006,8 @@
"name": "confluence-automation",
"description": "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "content-creator",
@@ -2715,16 +3016,18 @@
"name": "content-creator",
"description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "content-marketer",
"path": "skills\\content-marketer",
"category": "uncategorized",
"name": "content-marketer",
- "description": "Elite content marketing strategist specializing in AI-powered\ncontent creation, omnichannel distribution, SEO optimization, and data-driven\nperformance marketing. Masters modern content tools, social media automation,\nand conversion optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive content marketing.\n",
+ "description": "- Working on content marketer tasks or workflows - Needing guidance, best practices, or checklists for content marketer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-compression",
@@ -2733,7 +3036,8 @@
"name": "context-compression",
"description": "Design and evaluate compression strategies for long-running sessions",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-compression"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-compression",
+ "date_added": "2025-02-26"
},
{
"id": "context-degradation",
@@ -2742,16 +3046,18 @@
"name": "context-degradation",
"description": "Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation",
+ "date_added": "2025-02-26"
},
{
"id": "context-driven-development",
"path": "skills\\context-driven-development",
"category": "uncategorized",
"name": "context-driven-development",
- "description": "Use this skill when working with Conductor's context-driven\ndevelopment methodology, managing project context artifacts, or understanding\nthe relationship between product.md, tech-stack.md, and workflow.md files.\n",
+ "description": "Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-fundamentals",
@@ -2760,7 +3066,8 @@
"name": "context-fundamentals",
"description": "Understand what context is, why it matters, and the anatomy of context in agent systems",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-fundamentals"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-fundamentals",
+ "date_added": "2025-02-26"
},
{
"id": "context-management-context-restore",
@@ -2769,7 +3076,8 @@
"name": "context-management-context-restore",
"description": "Use when working with context management context restore",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-management-context-save",
@@ -2778,16 +3086,18 @@
"name": "context-management-context-save",
"description": "Use when working with context management context save",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-manager",
"path": "skills\\context-manager",
"category": "uncategorized",
"name": "context-manager",
- "description": "Elite AI context engineering specialist mastering dynamic context\nmanagement, vector databases, knowledge graphs, and intelligent memory\nsystems. Orchestrates context across multi-agent workflows, enterprise AI\nsystems, and long-running projects with 2024/2025 best practices. Use\nPROACTIVELY for complex AI orchestration.\n",
+ "description": "- Working on context manager tasks or workflows - Needing guidance, best practices, or checklists for context manager",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-optimization",
@@ -2796,7 +3106,8 @@
"name": "context-optimization",
"description": "Apply compaction, masking, and caching strategies",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-optimization"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-optimization",
+ "date_added": "2025-02-26"
},
{
"id": "context-window-management",
@@ -2805,7 +3116,8 @@
"name": "context-window-management",
"description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "context7-auto-research",
@@ -2814,7 +3126,8 @@
"name": "context7-auto-research",
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conversation-memory",
@@ -2823,7 +3136,8 @@
"name": "conversation-memory",
"description": "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "convertkit-automation",
@@ -2832,7 +3146,8 @@
"name": "convertkit-automation",
"description": "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copilot-sdk",
@@ -2841,7 +3156,8 @@
"name": "copilot-sdk",
"description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copy-editing",
@@ -2850,16 +3166,18 @@
"name": "copy-editing",
"description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copywriting",
"path": "skills\\copywriting",
"category": "uncategorized",
"name": "copywriting",
- "description": "Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.\n",
+ "description": "Produce **clear, credible, and action-oriented marketing copy** that aligns with user intent and business goals.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "core-components",
@@ -2868,7 +3186,8 @@
"name": "core-components",
"description": "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cost-optimization",
@@ -2877,16 +3196,18 @@
"name": "cost-optimization",
"description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cpp-pro",
"path": "skills\\cpp-pro",
"category": "uncategorized",
"name": "cpp-pro",
- "description": "Write idiomatic C++ code with modern features, RAII, smart\npointers, and STL algorithms. Handles templates, move semantics, and\nperformance optimization. Use PROACTIVELY for C++ refactoring, memory safety,\nor complex C++ patterns.\n",
+ "description": "- Working on cpp pro tasks or workflows - Needing guidance, best practices, or checklists for cpp pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cqrs-implementation",
@@ -2895,7 +3216,8 @@
"name": "cqrs-implementation",
"description": "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "create-pr",
@@ -2904,7 +3226,8 @@
"name": "create-pr",
"description": "Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/create-pr"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/create-pr",
+ "date_added": "2025-02-26"
},
{
"id": "crewai",
@@ -2913,25 +3236,28 @@
"name": "crewai",
"description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "crypto-bd-agent",
"path": "skills\\crypto-bd-agent",
"category": "uncategorized",
"name": "crypto-bd-agent",
- "description": "Autonomous crypto business development patterns \u2014 multi-chain token discovery, 100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain identity, LLM cascade routing, and pipeline automation for CEX/DEX listing acquisition. Use when building AI agents for crypto BD, token evaluation, exchange listing outreach, or autonomous commerce with payment protocols.\n",
+ "description": "> Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "csharp-pro",
"path": "skills\\csharp-pro",
"category": "uncategorized",
"name": "csharp-pro",
- "description": "Write modern C# code with advanced features like records, pattern\nmatching, and async/await. Optimizes .NET applications, implements enterprise\npatterns, and ensures comprehensive testing. Use PROACTIVELY for C#\nrefactoring, performance optimization, or complex .NET solutions.\n",
+ "description": "- Working on csharp pro tasks or workflows - Needing guidance, best practices, or checklists for csharp pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "culture-index",
@@ -2940,25 +3266,28 @@
"name": "culture-index",
"description": "Index and search culture documentation",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/culture-index"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/culture-index",
+ "date_added": "2025-02-26"
},
{
"id": "customer-support",
"path": "skills\\customer-support",
"category": "uncategorized",
"name": "customer-support",
- "description": "Elite AI-powered customer support specialist mastering\nconversational AI, automated ticketing, sentiment analysis, and omnichannel\nsupport experiences. Integrates modern support tools, chatbot platforms, and\nCX optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive customer experience management.\n",
+ "description": "- Working on customer support tasks or workflows - Needing guidance, best practices, or checklists for customer support",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "customs-trade-compliance",
"path": "skills\\customs-trade-compliance",
"category": "uncategorized",
"name": "customs-trade-compliance",
- "description": "Codified expertise for customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilisation, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimisation.\n",
+ "description": "Use this skill when navigating international trade regulations, classifying goods under HS codes, determining appropriate Incoterms, managing import/export documentation, or optimizing customs duty payments through Free Trade Agreements.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "daily-news-report",
@@ -2967,16 +3296,18 @@
"name": "daily-news-report",
"description": "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineer",
"path": "skills\\data-engineer",
"category": "uncategorized",
"name": "data-engineer",
- "description": "Build scalable data pipelines, modern data warehouses, and\nreal-time streaming architectures. Implements Apache Spark, dbt, Airflow, and\ncloud-native data platforms. Use PROACTIVELY for data pipeline design,\nanalytics infrastructure, or modern data stack implementation.\n",
+ "description": "You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineering-data-driven-feature",
@@ -2985,7 +3316,8 @@
"name": "data-engineering-data-driven-feature",
"description": "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineering-data-pipeline",
@@ -2994,7 +3326,8 @@
"name": "data-engineering-data-pipeline",
"description": "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-quality-frameworks",
@@ -3003,16 +3336,18 @@
"name": "data-quality-frameworks",
"description": "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-scientist",
"path": "skills\\data-scientist",
"category": "uncategorized",
"name": "data-scientist",
- "description": "Expert data scientist for advanced analytics, machine learning, and\nstatistical modeling. Handles complex data analysis, predictive modeling, and\nbusiness intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,\nstatistical analysis, and data-driven insights.\n",
+ "description": "- Working on data scientist tasks or workflows - Needing guidance, best practices, or checklists for data scientist",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-storytelling",
@@ -3021,7 +3356,8 @@
"name": "data-storytelling",
"description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-structure-protocol",
@@ -3030,7 +3366,8 @@
"name": "data-structure-protocol",
"description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
"risk": "safe",
- "source": "https://github.com/k-kolomeitsev/data-structure-protocol"
+ "source": "https://github.com/k-kolomeitsev/data-structure-protocol",
+ "date_added": "2025-02-26"
},
{
"id": "database",
@@ -3039,25 +3376,28 @@
"name": "database",
"description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "database-admin",
"path": "skills\\database-admin",
"category": "uncategorized",
"name": "database-admin",
- "description": "Expert database administrator specializing in modern cloud\ndatabases, automation, and reliability engineering. Masters AWS/Azure/GCP\ndatabase services, Infrastructure as Code, high availability, disaster\nrecovery, performance optimization, and compliance. Handles multi-cloud\nstrategies, container databases, and cost optimization. Use PROACTIVELY for\ndatabase architecture, operations, or reliability engineering.\n",
+ "description": "- Working on database admin tasks or workflows - Needing guidance, best practices, or checklists for database admin",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-architect",
"path": "skills\\database-architect",
"category": "uncategorized",
"name": "database-architect",
- "description": "Expert database architect specializing in data layer design from\nscratch, technology selection, schema modeling, and scalable database\narchitectures. Masters SQL/NoSQL/TimeSeries database selection, normalization\nstrategies, migration planning, and performance-first design. Handles both\ngreenfield architectures and re-architecture of existing systems. Use\nPROACTIVELY for database architecture, technology selection, or data modeling\ndecisions.\n",
+ "description": "You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-cloud-optimization-cost-optimize",
@@ -3066,7 +3406,8 @@
"name": "database-cloud-optimization-cost-optimize",
"description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-design",
@@ -3075,7 +3416,8 @@
"name": "database-design",
"description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migration",
@@ -3084,7 +3426,8 @@
"name": "database-migration",
"description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migrations-migration-observability",
@@ -3093,7 +3436,8 @@
"name": "database-migrations-migration-observability",
"description": "Migration monitoring, CDC, and observability infrastructure",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migrations-sql-migrations",
@@ -3102,16 +3446,18 @@
"name": "database-migrations-sql-migrations",
"description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-optimizer",
"path": "skills\\database-optimizer",
"category": "uncategorized",
"name": "database-optimizer",
- "description": "Expert database optimizer specializing in modern performance\ntuning, query optimization, and scalable architectures. Masters advanced\nindexing, N+1 resolution, multi-tier caching, partitioning strategies, and\ncloud database optimization. Handles complex query analysis, migration\nstrategies, and performance monitoring. Use PROACTIVELY for database\noptimization, performance issues, or scalability challenges.\n",
+ "description": "- Working on database optimizer tasks or workflows - Needing guidance, best practices, or checklists for database optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "datadog-automation",
@@ -3120,7 +3466,8 @@
"name": "datadog-automation",
"description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-golang",
@@ -3129,7 +3476,8 @@
"name": "dbos-golang",
"description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-python",
@@ -3138,7 +3486,8 @@
"name": "dbos-python",
"description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-typescript",
@@ -3147,7 +3496,8 @@
"name": "dbos-typescript",
"description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbt-transformation-patterns",
@@ -3156,7 +3506,8 @@
"name": "dbt-transformation-patterns",
"description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-context-mapping",
@@ -3165,7 +3516,8 @@
"name": "ddd-context-mapping",
"description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-strategic-design",
@@ -3174,7 +3526,8 @@
"name": "ddd-strategic-design",
"description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-tactical-patterns",
@@ -3183,16 +3536,18 @@
"name": "ddd-tactical-patterns",
"description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "debugger",
"path": "skills\\debugger",
"category": "uncategorized",
"name": "debugger",
- "description": "Debugging specialist for errors, test failures, and unexpected\nbehavior. Use proactively when encountering any issues.\n",
+ "description": "- Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "debugging-strategies",
@@ -3201,7 +3556,8 @@
"name": "debugging-strategies",
"description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "debugging-toolkit-smart-debug",
@@ -3210,7 +3566,8 @@
"name": "debugging-toolkit-smart-debug",
"description": "Use when working with debugging toolkit smart debug",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deep-research",
@@ -3219,7 +3576,8 @@
"name": "deep-research",
"description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ...",
"risk": "safe",
- "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research"
+ "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research",
+ "date_added": "2025-02-26"
},
{
"id": "defi-protocol-templates",
@@ -3228,7 +3586,8 @@
"name": "defi-protocol-templates",
"description": "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dependency-management-deps-audit",
@@ -3237,7 +3596,8 @@
"name": "dependency-management-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dependency-upgrade",
@@ -3246,16 +3606,18 @@
"name": "dependency-upgrade",
"description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-engineer",
"path": "skills\\deployment-engineer",
"category": "uncategorized",
"name": "deployment-engineer",
- "description": "Expert deployment engineer specializing in modern CI/CD pipelines,\nGitOps workflows, and advanced deployment automation. Masters GitHub Actions,\nArgoCD/Flux, progressive delivery, container security, and platform\nengineering. Handles zero-downtime deployments, security scanning, and\ndeveloper experience optimization. Use PROACTIVELY for CI/CD design, GitOps\nimplementation, or deployment automation.\n",
+ "description": "You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-pipeline-design",
@@ -3264,7 +3626,8 @@
"name": "deployment-pipeline-design",
"description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-procedures",
@@ -3273,7 +3636,8 @@
"name": "deployment-procedures",
"description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-validation-config-validate",
@@ -3282,7 +3646,8 @@
"name": "deployment-validation-config-validate",
"description": "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "design-md",
@@ -3291,16 +3656,18 @@
"name": "design-md",
"description": "Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files",
"risk": "safe",
- "source": "https://github.com/google-labs-code/stitch-skills/tree/main/skills/design-md"
+ "source": "https://github.com/google-labs-code/stitch-skills/tree/main/skills/design-md",
+ "date_added": "2025-02-26"
},
{
"id": "design-orchestration",
"path": "skills\\design-orchestration",
"category": "uncategorized",
"name": "design-orchestration",
- "description": "Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.",
+ "description": "Ensure that **ideas become designs**, **designs are reviewed**, and **only validated designs reach implementation**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "development",
@@ -3309,16 +3676,18 @@
"name": "development",
"description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "devops-troubleshooter",
"path": "skills\\devops-troubleshooter",
"category": "uncategorized",
"name": "devops-troubleshooter",
- "description": "Expert DevOps troubleshooter specializing in rapid incident\nresponse, advanced debugging, and modern observability. Masters log analysis,\ndistributed tracing, Kubernetes debugging, performance optimization, and root\ncause analysis. Handles production outages, system reliability, and preventive\nmonitoring. Use PROACTIVELY for debugging, incident response, or system\ntroubleshooting.\n",
+ "description": "- Working on devops troubleshooter tasks or workflows - Needing guidance, best practices, or checklists for devops troubleshooter",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "discord-automation",
@@ -3327,7 +3696,8 @@
"name": "discord-automation",
"description": "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "discord-bot-architect",
@@ -3336,7 +3706,8 @@
"name": "discord-bot-architect",
"description": "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "dispatching-parallel-agents",
@@ -3345,7 +3716,8 @@
"name": "dispatching-parallel-agents",
"description": "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "distributed-debugging-debug-trace",
@@ -3354,7 +3726,8 @@
"name": "distributed-debugging-debug-trace",
"description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "distributed-tracing",
@@ -3363,16 +3736,18 @@
"name": "distributed-tracing",
"description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "django-pro",
"path": "skills\\django-pro",
"category": "uncategorized",
"name": "django-pro",
- "description": "Master Django 5.x with async views, DRF, Celery, and Django\nChannels. Build scalable web applications with proper architecture, testing,\nand deployment. Use PROACTIVELY for Django development, ORM optimization, or\ncomplex Django patterns.\n",
+ "description": "- Working on django pro tasks or workflows - Needing guidance, best practices, or checklists for django pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "doc-coauthoring",
@@ -3381,7 +3756,8 @@
"name": "doc-coauthoring",
"description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docker-expert",
@@ -3390,16 +3766,18 @@
"name": "docker-expert",
"description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docs-architect",
"path": "skills\\docs-architect",
"category": "uncategorized",
"name": "docs-architect",
- "description": "Creates comprehensive technical documentation from existing\ncodebases. Analyzes architecture, design patterns, and implementation details\nto produce long-form technical manuals and ebooks. Use PROACTIVELY for system\ndocumentation, architecture guides, or technical deep-dives.\n",
+ "description": "- Working on docs architect tasks or workflows - Needing guidance, best practices, or checklists for docs architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "documentation",
@@ -3408,7 +3786,8 @@
"name": "documentation",
"description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "documentation-generation-doc-generate",
@@ -3417,7 +3796,8 @@
"name": "documentation-generation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "documentation-templates",
@@ -3426,7 +3806,8 @@
"name": "documentation-templates",
"description": "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docusign-automation",
@@ -3435,7 +3816,8 @@
"name": "docusign-automation",
"description": "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docx-official",
@@ -3444,7 +3826,8 @@
"name": "docx-official",
"description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "domain-driven-design",
@@ -3453,16 +3836,18 @@
"name": "domain-driven-design",
"description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-architect",
"path": "skills\\dotnet-architect",
"category": "uncategorized",
"name": "dotnet-architect",
- "description": "Expert .NET backend architect specializing in C#, ASP.NET Core,\nEntity Framework, Dapper, and enterprise application patterns. Masters\nasync/await, dependency injection, caching strategies, and performance\noptimization. Use PROACTIVELY for .NET API development, code review, or\narchitecture decisions.\n",
+ "description": "- Working on dotnet architect tasks or workflows - Needing guidance, best practices, or checklists for dotnet architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-backend",
@@ -3471,7 +3856,8 @@
"name": "dotnet-backend",
"description": "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-backend-patterns",
@@ -3480,7 +3866,8 @@
"name": "dotnet-backend-patterns",
"description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "draw",
@@ -3489,7 +3876,8 @@
"name": "draw",
"description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "dropbox-automation",
@@ -3498,16 +3886,18 @@
"name": "dropbox-automation",
"description": "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dx-optimizer",
"path": "skills\\dx-optimizer",
"category": "uncategorized",
"name": "dx-optimizer",
- "description": "Developer Experience specialist. Improves tooling, setup, and\nworkflows. Use PROACTIVELY when setting up new projects, after team feedback,\nor when development friction is noticed.\n",
+ "description": "- Working on dx optimizer tasks or workflows - Needing guidance, best practices, or checklists for dx optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "e2e-testing",
@@ -3516,7 +3906,8 @@
"name": "e2e-testing",
"description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "e2e-testing-patterns",
@@ -3525,16 +3916,18 @@
"name": "e2e-testing-patterns",
"description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "elixir-pro",
"path": "skills\\elixir-pro",
"category": "uncategorized",
"name": "elixir-pro",
- "description": "Write idiomatic Elixir code with OTP patterns, supervision trees,\nand Phoenix LiveView. Masters concurrency, fault tolerance, and distributed\nsystems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM\noptimizations.\n",
+ "description": "- Working on elixir pro tasks or workflows - Needing guidance, best practices, or checklists for elixir pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "email-sequence",
@@ -3543,7 +3936,8 @@
"name": "email-sequence",
"description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "email-systems",
@@ -3552,7 +3946,8 @@
"name": "email-systems",
"description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "embedding-strategies",
@@ -3561,7 +3956,8 @@
"name": "embedding-strategies",
"description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "employment-contract-templates",
@@ -3570,16 +3966,18 @@
"name": "employment-contract-templates",
"description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "energy-procurement",
"path": "skills\\energy-procurement",
"category": "uncategorized",
"name": "energy-procurement",
- "description": "Codified expertise for electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimising tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.\n",
+ "description": "Use this skill when managing energy procurement tasks, such as optimizing electricity or gas tariffs, evaluating Power Purchase Agreements (PPAs), or developing long-term energy cost management strategies for commercial or industrial facilities.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "environment-setup-guide",
@@ -3588,7 +3986,8 @@
"name": "environment-setup-guide",
"description": "Guide developers through setting up development environments with proper tools, dependencies, and configurations",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-error-analysis",
@@ -3597,7 +3996,8 @@
"name": "error-debugging-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-error-trace",
@@ -3606,7 +4006,8 @@
"name": "error-debugging-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-multi-agent-review",
@@ -3615,16 +4016,18 @@
"name": "error-debugging-multi-agent-review",
"description": "Use when working with error debugging multi agent review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-detective",
"path": "skills\\error-detective",
"category": "uncategorized",
"name": "error-detective",
- "description": "Search logs and codebases for error patterns, stack traces, and\nanomalies. Correlates errors across systems and identifies root causes. Use\nPROACTIVELY when debugging issues, analyzing logs, or investigating production\nerrors.\n",
+ "description": "- Working on error detective tasks or workflows - Needing guidance, best practices, or checklists for error detective",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-error-analysis",
@@ -3633,7 +4036,8 @@
"name": "error-diagnostics-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-error-trace",
@@ -3642,7 +4046,8 @@
"name": "error-diagnostics-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-smart-debug",
@@ -3651,7 +4056,8 @@
"name": "error-diagnostics-smart-debug",
"description": "Use when working with error diagnostics smart debug",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-handling-patterns",
@@ -3660,7 +4066,8 @@
"name": "error-handling-patterns",
"description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ethical-hacking-methodology",
@@ -3669,7 +4076,8 @@
"name": "ethical-hacking-methodology",
"description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "evaluation",
@@ -3678,7 +4086,8 @@
"name": "evaluation",
"description": "Build evaluation frameworks for agent systems",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/evaluation"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/evaluation",
+ "date_added": "2025-02-26"
},
{
"id": "event-sourcing-architect",
@@ -3687,7 +4096,8 @@
"name": "event-sourcing-architect",
"description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "event-store-design",
@@ -3696,7 +4106,8 @@
"name": "event-store-design",
"description": "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "exa-search",
@@ -3705,7 +4116,8 @@
"name": "exa-search",
"description": "Semantic search, similar content discovery, and structured research using Exa API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "executing-plans",
@@ -3714,7 +4126,8 @@
"name": "executing-plans",
"description": "Use when you have a written implementation plan to execute in a separate session with review checkpoints",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "expo-deployment",
@@ -3723,7 +4136,8 @@
"name": "expo-deployment",
"description": "Deploy Expo apps to production",
"risk": "safe",
- "source": "https://github.com/expo/skills/tree/main/plugins/expo-deployment"
+ "source": "https://github.com/expo/skills/tree/main/plugins/expo-deployment",
+ "date_added": "2025-02-26"
},
{
"id": "fal-audio",
@@ -3732,7 +4146,8 @@
"name": "fal-audio",
"description": "Text-to-speech and speech-to-text using fal.ai audio models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-audio/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-audio/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-generate",
@@ -3741,7 +4156,8 @@
"name": "fal-generate",
"description": "Generate images and videos using fal.ai AI models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-generate/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-generate/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-image-edit",
@@ -3750,7 +4166,8 @@
"name": "fal-image-edit",
"description": "AI-powered image editing with style transfer and object removal",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-image-edit/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-image-edit/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-platform",
@@ -3759,7 +4176,8 @@
"name": "fal-platform",
"description": "Platform APIs for model management, pricing, and usage tracking",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-platform/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-platform/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-upscale",
@@ -3768,7 +4186,8 @@
"name": "fal-upscale",
"description": "Upscale and enhance image and video resolution using AI",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-upscale/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-upscale/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-workflow",
@@ -3777,16 +4196,18 @@
"name": "fal-workflow",
"description": "Generate workflow JSON files for chaining AI models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-workflow/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-workflow/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-pro",
"path": "skills\\fastapi-pro",
"category": "uncategorized",
"name": "fastapi-pro",
- "description": "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and\nPydantic V2. Master microservices, WebSockets, and modern Python async\npatterns. Use PROACTIVELY for FastAPI development, async optimization, or API\narchitecture.\n",
+ "description": "- Working on fastapi pro tasks or workflows - Needing guidance, best practices, or checklists for fastapi pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-router-py",
@@ -3795,7 +4216,8 @@
"name": "fastapi-router-py",
"description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-templates",
@@ -3804,7 +4226,8 @@
"name": "fastapi-templates",
"description": "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ffuf-claude-skill",
@@ -3813,7 +4236,8 @@
"name": "ffuf-claude-skill",
"description": "Web fuzzing with ffuf",
"risk": "safe",
- "source": "https://github.com/jthack/ffuf_claude_skill"
+ "source": "https://github.com/jthack/ffuf_claude_skill",
+ "date_added": "2025-02-26"
},
{
"id": "figma-automation",
@@ -3822,7 +4246,8 @@
"name": "figma-automation",
"description": "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-organizer",
@@ -3831,7 +4256,8 @@
"name": "file-organizer",
"description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-path-traversal",
@@ -3840,7 +4266,8 @@
"name": "file-path-traversal",
"description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-uploads",
@@ -3849,7 +4276,8 @@
"name": "file-uploads",
"description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "find-bugs",
@@ -3858,7 +4286,8 @@
"name": "find-bugs",
"description": "Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/find-bugs"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/find-bugs",
+ "date_added": "2025-02-26"
},
{
"id": "finishing-a-development-branch",
@@ -3867,7 +4296,8 @@
"name": "finishing-a-development-branch",
"description": "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "firebase",
@@ -3876,7 +4306,8 @@
"name": "firebase",
"description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "firecrawl-scraper",
@@ -3885,16 +4316,18 @@
"name": "firecrawl-scraper",
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "firmware-analyst",
"path": "skills\\firmware-analyst",
"category": "uncategorized",
"name": "firmware-analyst",
- "description": "Expert firmware analyst specializing in embedded systems, IoT\nsecurity, and hardware reverse engineering. Masters firmware extraction,\nanalysis, and vulnerability research for routers, IoT devices, automotive\nsystems, and industrial controllers. Use PROACTIVELY for firmware security\naudits, IoT penetration testing, or embedded systems research.\n",
+ "description": "wget http://vendor.com/firmware/update.bin",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fix-review",
@@ -3903,25 +4336,28 @@
"name": "fix-review",
"description": "Verify fix commits address audit findings without new bugs",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/fix-review"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/fix-review",
+ "date_added": "2025-02-26"
},
{
"id": "flutter-expert",
"path": "skills\\flutter-expert",
"category": "uncategorized",
"name": "flutter-expert",
- "description": "Master Flutter development with Dart 3, advanced widgets, and\nmulti-platform deployment. Handles state management, animations, testing, and\nperformance optimization for mobile, web, desktop, and embedded platforms. Use\nPROACTIVELY for Flutter architecture, UI implementation, or cross-platform\nfeatures.\n",
+ "description": "- Working on flutter expert tasks or workflows - Needing guidance, best practices, or checklists for flutter expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "form-cro",
"path": "skills\\form-cro",
"category": "uncategorized",
"name": "form-cro",
- "description": "Optimize any form that is NOT signup or account registration \u2014 including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.\n",
+ "description": "You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-errors",
@@ -3930,7 +4366,8 @@
"name": "fp-ts-errors",
"description": "Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-pragmatic",
@@ -3939,7 +4376,8 @@
"name": "fp-ts-pragmatic",
"description": "A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-react",
@@ -3948,7 +4386,8 @@
"name": "fp-ts-react",
"description": "Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-code-migrate",
@@ -3957,7 +4396,8 @@
"name": "framework-migration-code-migrate",
"description": "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-deps-upgrade",
@@ -3966,7 +4406,8 @@
"name": "framework-migration-deps-upgrade",
"description": "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-legacy-modernize",
@@ -3975,7 +4416,8 @@
"name": "framework-migration-legacy-modernize",
"description": "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "free-tool-strategy",
@@ -3984,7 +4426,8 @@
"name": "free-tool-strategy",
"description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "freshdesk-automation",
@@ -3993,7 +4436,8 @@
"name": "freshdesk-automation",
"description": "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "freshservice-automation",
@@ -4002,7 +4446,8 @@
"name": "freshservice-automation",
"description": "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-design",
@@ -4011,7 +4456,8 @@
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-dev-guidelines",
@@ -4020,16 +4466,18 @@
"name": "frontend-dev-guidelines",
"description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-developer",
"path": "skills\\frontend-developer",
"category": "uncategorized",
"name": "frontend-developer",
- "description": "Build React components, implement responsive layouts, and handle\nclient-side state management. Masters React 19, Next.js 15, and modern\nfrontend architecture. Optimizes performance and ensures accessibility. Use\nPROACTIVELY when creating UI components or fixing frontend issues.\n",
+ "description": "You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-mobile-development-component-scaffold",
@@ -4038,7 +4486,8 @@
"name": "frontend-mobile-development-component-scaffold",
"description": "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-mobile-security-xss-scan",
@@ -4047,16 +4496,18 @@
"name": "frontend-mobile-security-xss-scan",
"description": "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-security-coder",
"path": "skills\\frontend-security-coder",
"category": "uncategorized",
"name": "frontend-security-coder",
- "description": "Expert in secure frontend coding practices specializing in XSS\nprevention, output sanitization, and client-side security patterns. Use\nPROACTIVELY for frontend security implementations or client-side security code\nreviews.\n",
+ "description": "- Working on frontend security coder tasks or workflows - Needing guidance, best practices, or checklists for frontend security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-slides",
@@ -4065,7 +4516,8 @@
"name": "frontend-slides",
"description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a...",
"risk": "safe",
- "source": "https://github.com/zarazhangrui/frontend-slides"
+ "source": "https://github.com/zarazhangrui/frontend-slides",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-ui-dark-ts",
@@ -4074,7 +4526,8 @@
"name": "frontend-ui-dark-ts",
"description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "full-stack-orchestration-full-stack-feature",
@@ -4083,7 +4536,8 @@
"name": "full-stack-orchestration-full-stack-feature",
"description": "Use when working with full stack orchestration full stack feature",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-art",
@@ -4092,7 +4546,8 @@
"name": "game-art",
"description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-audio",
@@ -4101,7 +4556,8 @@
"name": "game-audio",
"description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-design",
@@ -4110,7 +4566,8 @@
"name": "game-design",
"description": "Game design principles. GDD structure, balancing, player psychology, progression.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-development",
@@ -4119,7 +4576,8 @@
"name": "game-development",
"description": "Game development orchestrator. Routes to platform-specific skills based on project needs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gcp-cloud-run",
@@ -4128,7 +4586,8 @@
"name": "gcp-cloud-run",
"description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "gdpr-data-handling",
@@ -4137,7 +4596,8 @@
"name": "gdpr-data-handling",
"description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gemini-api-dev",
@@ -4146,7 +4606,8 @@
"name": "gemini-api-dev",
"description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "geo-fundamentals",
@@ -4155,7 +4616,8 @@
"name": "geo-fundamentals",
"description": "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-advanced-workflows",
@@ -4164,7 +4626,8 @@
"name": "git-advanced-workflows",
"description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-git-workflow",
@@ -4173,7 +4636,8 @@
"name": "git-pr-workflows-git-workflow",
"description": "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-onboard",
@@ -4182,7 +4646,8 @@
"name": "git-pr-workflows-onboard",
"description": "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-pr-enhance",
@@ -4191,7 +4656,8 @@
"name": "git-pr-workflows-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pushing",
@@ -4200,7 +4666,8 @@
"name": "git-pushing",
"description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-actions-templates",
@@ -4209,7 +4676,8 @@
"name": "github-actions-templates",
"description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-automation",
@@ -4218,7 +4686,8 @@
"name": "github-automation",
"description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-issue-creator",
@@ -4227,7 +4696,8 @@
"name": "github-issue-creator",
"description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-workflow-automation",
@@ -4236,7 +4706,8 @@
"name": "github-workflow-automation",
"description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitlab-automation",
@@ -4245,7 +4716,8 @@
"name": "gitlab-automation",
"description": "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitlab-ci-patterns",
@@ -4254,7 +4726,8 @@
"name": "gitlab-ci-patterns",
"description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitops-workflow",
@@ -4263,7 +4736,8 @@
"name": "gitops-workflow",
"description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gmail-automation",
@@ -4272,7 +4746,8 @@
"name": "gmail-automation",
"description": "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "go-concurrency-patterns",
@@ -4281,7 +4756,8 @@
"name": "go-concurrency-patterns",
"description": "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "go-playwright",
@@ -4290,7 +4766,8 @@
"name": "go-playwright",
"description": "Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.",
"risk": "safe",
- "source": "https://github.com/playwright-community/playwright-go"
+ "source": "https://github.com/playwright-community/playwright-go",
+ "date_added": "2025-02-26"
},
{
"id": "go-rod-master",
@@ -4299,7 +4776,8 @@
"name": "go-rod-master",
"description": "Comprehensive guide for browser automation and web scraping with go-rod (Chrome DevTools Protocol) including stealth anti-bot-detection patterns.",
"risk": "safe",
- "source": "https://github.com/go-rod/rod"
+ "source": "https://github.com/go-rod/rod",
+ "date_added": "2025-02-26"
},
{
"id": "godot-4-migration",
@@ -4308,7 +4786,8 @@
"name": "godot-4-migration",
"description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "godot-gdscript-patterns",
@@ -4317,16 +4796,18 @@
"name": "godot-gdscript-patterns",
"description": "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "golang-pro",
"path": "skills\\golang-pro",
"category": "uncategorized",
"name": "golang-pro",
- "description": "Master Go 1.21+ with modern patterns, advanced concurrency,\nperformance optimization, and production-ready microservices. Expert in the\nlatest Go ecosystem including generics, workspaces, and cutting-edge\nframeworks. Use PROACTIVELY for Go development, architecture design, or\nperformance optimization.\n",
+ "description": "You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-analytics-automation",
@@ -4335,7 +4816,8 @@
"name": "google-analytics-automation",
"description": "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-calendar-automation",
@@ -4344,7 +4826,8 @@
"name": "google-calendar-automation",
"description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-drive-automation",
@@ -4353,7 +4836,8 @@
"name": "google-drive-automation",
"description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "googlesheets-automation",
@@ -4362,7 +4846,8 @@
"name": "googlesheets-automation",
"description": "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "grafana-dashboards",
@@ -4371,7 +4856,8 @@
"name": "grafana-dashboards",
"description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "graphql",
@@ -4380,16 +4866,18 @@
"name": "graphql",
"description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "graphql-architect",
"path": "skills\\graphql-architect",
"category": "uncategorized",
"name": "graphql-architect",
- "description": "Master modern GraphQL with federation, performance optimization,\nand enterprise security. Build scalable schemas, implement advanced caching,\nand design real-time systems. Use PROACTIVELY for GraphQL architecture or\nperformance optimization.\n",
+ "description": "- Working on graphql architect tasks or workflows - Needing guidance, best practices, or checklists for graphql architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "grpc-golang",
@@ -4398,16 +4886,18 @@
"name": "grpc-golang",
"description": "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "haskell-pro",
"path": "skills\\haskell-pro",
"category": "uncategorized",
"name": "haskell-pro",
- "description": "Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.",
+ "description": "Expert Haskell engineer specializing in advanced type systems, pure",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "helm-chart-scaffolding",
@@ -4416,7 +4906,8 @@
"name": "helm-chart-scaffolding",
"description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "helpdesk-automation",
@@ -4425,133 +4916,148 @@
"name": "helpdesk-automation",
"description": "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-content",
"path": "skills\\hig-components-content",
"category": "uncategorized",
"name": "hig-components-content",
- "description": "Apple Human Interface Guidelines for content display components. Use this skill when the user asks about \"charts component\", \"collection view\", \"image view\", \"web view\", \"color well\", \"image well\", \"activity view\", \"lockup\", \"data visualization\", \"content display\", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says \"how should I display charts\", \"what's the best way to show images\", \"should I use a web view\", \"how do I build a grid of items\", \"what component shows media\", or \"how do I present a share sheet\". Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-controls",
"path": "skills\\hig-components-controls",
"category": "uncategorized",
"name": "hig-components-controls",
- "description": "Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says \"picker or segmented control,\" \"how should my form look,\" \"what keyboard type should I use,\" \"toggle vs checkbox,\" or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. Cross-references: hig-components-menus, hig-components-dialogs, hig-components-search.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-dialogs",
"path": "skills\\hig-components-dialogs",
"category": "uncategorized",
"name": "hig-components-dialogs",
- "description": "Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says \"should I use an alert or a sheet,\" \"how do I show a confirmation dialog,\" \"when should I use a popover,\" \"my modals are annoying users,\" or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, destructive action confirmation, or overlay UI patterns. Cross-references: hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-layout",
"path": "skills\\hig-components-layout",
"category": "uncategorized",
"name": "hig-components-layout",
- "description": "Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about \"sidebar\", \"split view\", \"tab bar\", \"tab view\", \"scroll view\", \"window design\", \"panel\", \"list view\", \"table view\", \"column view\", \"outline view\", \"navigation structure\", \"app layout\", \"boxes\", \"ornaments\", or organizing content hierarchically in Apple apps. Also use when the user says \"how should I organize my app\", \"what navigation pattern should I use\", \"my layout breaks on iPad\", \"how do I build a sidebar\", \"should I use tabs or a sidebar\", or \"my app doesn't adapt to different screen sizes\". Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-menus",
"path": "skills\\hig-components-menus",
"category": "uncategorized",
"name": "hig-components-menus",
- "description": "Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure controls, and standard buttons. Use this skill when the user says \"how should my buttons look,\" \"what goes in the menu bar,\" \"should I use a context menu or action sheet,\" \"how do I design a toolbar,\" or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit menu, or any menu/button component layout and behavior. Cross-references: hig-components-search, hig-components-controls, hig-components-dialogs.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-search",
"path": "skills\\hig-components-search",
"category": "uncategorized",
"name": "hig-components-search",
- "description": "Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill when the user says \"how should search work in my app,\" \"I need a breadcrumb,\" \"how do I paginate content,\" or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-status",
"path": "skills\\hig-components-status",
"category": "uncategorized",
"name": "hig-components-status",
- "description": "Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: \"progress indicator\", \"progress bar\", \"loading spinner\", \"status bar\", \"activity ring\", \"progress display\", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says \"how do I show loading state,\" \"should I use a spinner or progress bar,\" \"what goes in the status bar,\" or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-system",
"path": "skills\\hig-components-system",
"category": "uncategorized",
"name": "hig-components-system",
- "description": "Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: \"widget design\", \"live activity\", \"notification design\", \"complication\", \"home screen quick action\", \"top shelf\", \"watch face\", \"app clip\", \"app shortcut\", \"system experience\". Also use when the user says \"how do I design a widget,\" \"what should my notification look like,\" \"how do Live Activities work,\" \"should I make an App Clip,\" or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-foundations",
"path": "skills\\hig-foundations",
"category": "uncategorized",
"name": "hig-foundations",
- "description": "Apple Human Interface Guidelines design foundations. Use this skill when the user asks about \"HIG color\", \"Apple typography\", \"SF Symbols\", \"dark mode guidelines\", \"accessible design\", \"Apple design foundations\", \"app icon\", \"layout guidelines\", \"materials\", \"motion\", \"privacy\", \"right to left\", \"RTL\", \"inclusive design\", branding, images, spatial layout, or writing style. Also use when the user says \"my colors look wrong in dark mode\", \"what font should I use\", \"is my app accessible enough\", \"how do I support Dynamic Type\", \"what contrast ratio do I need\", \"how do I pick system colors\", or \"my icons don't match the system style\". Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction patterns, hig-components-layout for structural components, hig-components-content for display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-inputs",
"path": "skills\\hig-inputs",
"category": "uncategorized",
"name": "hig-inputs",
- "description": "Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. Use when asked about: \"gesture design\", \"Apple Pencil\", \"keyboard shortcuts\", \"game controller\", \"pointer support\", \"mouse support\", \"trackpad\", \"Digital Crown\", \"eye tracking\", \"visionOS input\", \"focus system\", \"remote control\", \"gyroscope\", \"spatial interaction\". Also use when the user says \"what gestures should I support,\" \"how do I add keyboard shortcuts,\" \"how does input work on Apple TV,\" \"should I support Apple Pencil,\" or asks about input device handling. Cross-references: hig-components-status, hig-components-system, hig-technologies for VoiceOver and Siri.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-patterns",
"path": "skills\\hig-patterns",
"category": "uncategorized",
"name": "hig-patterns",
- "description": "Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about \"onboarding flow\", \"user onboarding\", \"app launch\", \"loading state\", \"drag and drop\", \"search pattern\", \"settings design\", \"notifications\", \"modality\", \"multitasking\", \"feedback pattern\", \"haptics\", \"undo redo\", \"file management\", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says \"how should onboarding work\", \"my app takes too long to load\", \"should I use a modal here\", \"how do I handle errors\", \"when should I ask for permissions\", \"how to show progress\", or \"what's the right way to confirm a delete\". Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics, hig-components-layout for navigation, hig-components-content for data display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-platforms",
"path": "skills\\hig-platforms",
"category": "uncategorized",
"name": "hig-platforms",
- "description": "Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about \"designing for iOS\", \"iPad app design\", \"macOS design\", \"tvOS\", \"visionOS\", \"watchOS\", \"Apple platform\", \"which platform\", platform differences, platform-specific conventions, or multi-platform app design. Also use when the user says \"should I design differently for iPad vs iPhone\", \"how does my app work on visionOS\", \"what's different about macOS apps\", \"porting my app to another platform\", \"universal app design\", or \"what input methods does this platform use\". Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns, hig-components-layout for navigation structures, hig-components-content for content display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-project-context",
"path": "skills\\hig-project-context",
"category": "uncategorized",
"name": "hig-project-context",
- "description": "Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says \"set up my project context,\" \"what platforms am I targeting,\" \"configure HIG settings,\" or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.",
+ "description": "Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-technologies",
"path": "skills\\hig-technologies",
"category": "uncategorized",
"name": "hig-technologies",
- "description": "Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: \"Siri integration\", \"Apple Pay\", \"HealthKit\", \"HomeKit\", \"ARKit\", \"augmented reality\", \"machine learning\", \"generative AI\", \"iCloud sync\", \"Sign in with Apple\", \"SharePlay\", \"CarPlay\", \"in-app purchase\", \"NFC\", \"VoiceOver\", \"Maps\", \"Mac Catalyst\". Also use when the user says \"how do I integrate Siri,\" \"what are the Apple Pay guidelines,\" \"how should my AR experience work,\" \"how do I use Sign in with Apple,\" or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hosted-agents-v2-py",
@@ -4560,16 +5066,18 @@
"name": "hosted-agents-v2-py",
"description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hr-pro",
"path": "skills\\hr-pro",
"category": "uncategorized",
"name": "hr-pro",
- "description": "Professional, ethical HR partner for hiring,\nonboarding/offboarding, PTO and leave, performance, compliant policies, and\nemployee relations. Ask for jurisdiction and company context before advising;\nproduce structured, bias-mitigated, lawful templates.\n",
+ "description": "- Working on hr pro tasks or workflows - Needing guidance, best practices, or checklists for hr pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "html-injection-testing",
@@ -4578,7 +5086,8 @@
"name": "html-injection-testing",
"description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hubspot-automation",
@@ -4587,7 +5096,8 @@
"name": "hubspot-automation",
"description": "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hubspot-integration",
@@ -4596,7 +5106,8 @@
"name": "hubspot-integration",
"description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "hugging-face-cli",
@@ -4605,7 +5116,8 @@
"name": "hugging-face-cli",
"description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...",
"risk": "safe",
- "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli"
+ "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli",
+ "date_added": "2025-02-26"
},
{
"id": "hugging-face-jobs",
@@ -4614,16 +5126,18 @@
"name": "hugging-face-jobs",
"description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok...",
"risk": "safe",
- "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs"
+ "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-cloud-architect",
"path": "skills\\hybrid-cloud-architect",
"category": "uncategorized",
"name": "hybrid-cloud-architect",
- "description": "Expert hybrid cloud architect specializing in complex multi-cloud\nsolutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters\nhybrid connectivity, workload placement optimization, edge computing, and\ncross-cloud automation. Handles compliance, cost optimization, disaster\nrecovery, and migration strategies. Use PROACTIVELY for hybrid architecture,\nmulti-cloud strategy, or complex infrastructure integration.\n",
+ "description": "- Working on hybrid cloud architect tasks or workflows - Needing guidance, best practices, or checklists for hybrid cloud architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-cloud-networking",
@@ -4632,7 +5146,8 @@
"name": "hybrid-cloud-networking",
"description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-search-implementation",
@@ -4641,7 +5156,8 @@
"name": "hybrid-search-implementation",
"description": "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "i18n-localization",
@@ -4650,7 +5166,8 @@
"name": "i18n-localization",
"description": "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "idor-testing",
@@ -4659,7 +5176,8 @@
"name": "idor-testing",
"description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "imagen",
@@ -4668,7 +5186,8 @@
"name": "imagen",
"description": "This skill generates images using Google Gemini's image generation model (`gemini-3-pro-image-preview`). It enables seamless image creation during any Claude Code session - whether you're building frontend UIs, creating documentation, or need visual",
"risk": "safe",
- "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
+ "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen",
+ "date_added": "2025-02-26"
},
{
"id": "impress",
@@ -4677,16 +5196,18 @@
"name": "impress",
"description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "incident-responder",
"path": "skills\\incident-responder",
"category": "uncategorized",
"name": "incident-responder",
- "description": "Expert SRE incident responder specializing in rapid problem\nresolution, modern observability, and comprehensive incident management.\nMasters incident command, blameless post-mortems, error budget management, and\nsystem reliability patterns. Handles critical outages, communication\nstrategies, and continuous improvement. Use IMMEDIATELY for production\nincidents or SRE practices.\n",
+ "description": "- Working on incident responder tasks or workflows - Needing guidance, best practices, or checklists for incident responder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-response-incident-response",
@@ -4695,7 +5216,8 @@
"name": "incident-response-incident-response",
"description": "Use when working with incident response incident response",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-response-smart-fix",
@@ -4704,7 +5226,8 @@
"name": "incident-response-smart-fix",
"description": "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-runbook-templates",
@@ -4713,7 +5236,8 @@
"name": "incident-runbook-templates",
"description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "infinite-gratitude",
@@ -4722,7 +5246,8 @@
"name": "infinite-gratitude",
"description": "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).",
"risk": "safe",
- "source": "https://github.com/sstklen/infinite-gratitude"
+ "source": "https://github.com/sstklen/infinite-gratitude",
+ "date_added": "2025-02-26"
},
{
"id": "inngest",
@@ -4731,7 +5256,8 @@
"name": "inngest",
"description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "instagram-automation",
@@ -4740,7 +5266,8 @@
"name": "instagram-automation",
"description": "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "interactive-portfolio",
@@ -4749,7 +5276,8 @@
"name": "interactive-portfolio",
"description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "intercom-automation",
@@ -4758,7 +5286,8 @@
"name": "intercom-automation",
"description": "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "internal-comms-anthropic",
@@ -4767,7 +5296,8 @@
"name": "internal-comms-anthropic",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "internal-comms-community",
@@ -4776,25 +5306,28 @@
"name": "internal-comms-community",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "inventory-demand-planning",
"path": "skills\\inventory-demand-planning",
"category": "uncategorized",
"name": "inventory-demand-planning",
- "description": "Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimising inventory levels.\n",
+ "description": "Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "ios-developer",
"path": "skills\\ios-developer",
"category": "uncategorized",
"name": "ios-developer",
- "description": "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,\nSwiftUI, UIKit integration, Core Data, networking, and App Store optimization.\nUse PROACTIVELY for iOS-specific features, App Store optimization, or native\niOS development.\n",
+ "description": "- Working on ios developer tasks or workflows - Needing guidance, best practices, or checklists for ios developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "istio-traffic-management",
@@ -4803,7 +5336,8 @@
"name": "istio-traffic-management",
"description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "iterate-pr",
@@ -4812,16 +5346,18 @@
"name": "iterate-pr",
"description": "Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/iterate-pr"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/iterate-pr",
+ "date_added": "2025-02-26"
},
{
"id": "java-pro",
"path": "skills\\java-pro",
"category": "uncategorized",
"name": "java-pro",
- "description": "Master Java 21+ with modern features like virtual threads, pattern\nmatching, and Spring Boot 3.x. Expert in the latest Java ecosystem including\nGraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java\ndevelopment, microservices architecture, or performance optimization.\n",
+ "description": "- Working on java pro tasks or workflows - Needing guidance, best practices, or checklists for java pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-mastery",
@@ -4830,16 +5366,18 @@
"name": "javascript-mastery",
"description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-pro",
"path": "skills\\javascript-pro",
"category": "uncategorized",
"name": "javascript-pro",
- "description": "Master modern JavaScript with ES6+, async patterns, and Node.js\nAPIs. Handles promises, event loops, and browser/Node compatibility. Use\nPROACTIVELY for JavaScript optimization, async debugging, or complex JS\npatterns.\n",
+ "description": "You are a JavaScript expert specializing in modern JS and async programming.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-testing-patterns",
@@ -4848,7 +5386,8 @@
"name": "javascript-testing-patterns",
"description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-typescript-typescript-scaffold",
@@ -4857,7 +5396,8 @@
"name": "javascript-typescript-typescript-scaffold",
"description": "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "jira-automation",
@@ -4866,16 +5406,18 @@
"name": "jira-automation",
"description": "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "julia-pro",
"path": "skills\\julia-pro",
"category": "uncategorized",
"name": "julia-pro",
- "description": "Master Julia 1.10+ with modern features, performance optimization,\nmultiple dispatch, and production-ready practices. Expert in the Julia\necosystem including package management, scientific computing, and\nhigh-performance numerical code. Use PROACTIVELY for Julia development,\noptimization, or advanced Julia patterns.\n",
+ "description": "- Working on julia pro tasks or workflows - Needing guidance, best practices, or checklists for julia pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "k8s-manifest-generator",
@@ -4884,7 +5426,8 @@
"name": "k8s-manifest-generator",
"description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "k8s-security-policies",
@@ -4893,7 +5436,8 @@
"name": "k8s-security-policies",
"description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kaizen",
@@ -4902,7 +5446,8 @@
"name": "kaizen",
"description": "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "klaviyo-automation",
@@ -4911,7 +5456,8 @@
"name": "klaviyo-automation",
"description": "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kotlin-coroutines-expert",
@@ -4920,7 +5466,8 @@
"name": "kotlin-coroutines-expert",
"description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kpi-dashboard-design",
@@ -4929,16 +5476,18 @@
"name": "kpi-dashboard-design",
"description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kubernetes-architect",
"path": "skills\\kubernetes-architect",
"category": "uncategorized",
"name": "kubernetes-architect",
- "description": "Expert Kubernetes architect specializing in cloud-native\ninfrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise\ncontainer orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),\nprogressive delivery, multi-tenancy, and platform engineering. Handles\nsecurity, observability, cost optimization, and developer experience. Use\nPROACTIVELY for K8s architecture, GitOps implementation, or cloud-native\nplatform design.\n",
+ "description": "You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kubernetes-deployment",
@@ -4947,7 +5496,8 @@
"name": "kubernetes-deployment",
"description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "langchain-architecture",
@@ -4956,7 +5506,8 @@
"name": "langchain-architecture",
"description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "langfuse",
@@ -4965,7 +5516,8 @@
"name": "langfuse",
"description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "langgraph",
@@ -4974,7 +5526,8 @@
"name": "langgraph",
"description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "laravel-expert",
@@ -4983,7 +5536,8 @@
"name": "laravel-expert",
"description": "Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "laravel-security-audit",
@@ -4992,7 +5546,8 @@
"name": "laravel-security-audit",
"description": "Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "last30days",
@@ -5001,7 +5556,8 @@
"name": "last30days",
"description": "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "launch-strategy",
@@ -5010,25 +5566,28 @@
"name": "launch-strategy",
"description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "legacy-modernizer",
"path": "skills\\legacy-modernizer",
"category": "uncategorized",
"name": "legacy-modernizer",
- "description": "Refactor legacy codebases, migrate outdated frameworks, and\nimplement gradual modernization. Handles technical debt, dependency updates,\nand backward compatibility. Use PROACTIVELY for legacy system updates,\nframework migrations, or technical debt reduction.\n",
+ "description": "- Working on legacy modernizer tasks or workflows - Needing guidance, best practices, or checklists for legacy modernizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "legal-advisor",
"path": "skills\\legal-advisor",
"category": "uncategorized",
"name": "legal-advisor",
- "description": "Draft privacy policies, terms of service, disclaimers, and legal\nnotices. Creates GDPR-compliant texts, cookie policies, and data processing\nagreements. Use PROACTIVELY for legal documentation, compliance texts, or\nregulatory requirements.\n",
+ "description": "- Working on legal advisor tasks or workflows - Needing guidance, best practices, or checklists for legal advisor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linear-automation",
@@ -5037,7 +5596,8 @@
"name": "linear-automation",
"description": "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linear-claude-skill",
@@ -5046,7 +5606,8 @@
"name": "linear-claude-skill",
"description": "Manage Linear issues, projects, and teams",
"risk": "safe",
- "source": "https://github.com/wrsmith108/linear-claude-skill"
+ "source": "https://github.com/wrsmith108/linear-claude-skill",
+ "date_added": "2025-02-26"
},
{
"id": "linkedin-automation",
@@ -5055,7 +5616,8 @@
"name": "linkedin-automation",
"description": "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linkedin-cli",
@@ -5064,7 +5626,8 @@
"name": "linkedin-cli",
"description": "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linkerd-patterns",
@@ -5073,7 +5636,8 @@
"name": "linkerd-patterns",
"description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "lint-and-validate",
@@ -5082,7 +5646,8 @@
"name": "lint-and-validate",
"description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-privilege-escalation",
@@ -5091,7 +5656,8 @@
"name": "linux-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-shell-scripting",
@@ -5100,7 +5666,8 @@
"name": "linux-shell-scripting",
"description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-troubleshooting",
@@ -5109,7 +5676,8 @@
"name": "linux-troubleshooting",
"description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "llm-app-patterns",
@@ -5118,7 +5686,8 @@
"name": "llm-app-patterns",
"description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-ai-assistant",
@@ -5127,7 +5696,8 @@
"name": "llm-application-dev-ai-assistant",
"description": "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-langchain-agent",
@@ -5136,7 +5706,8 @@
"name": "llm-application-dev-langchain-agent",
"description": "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-prompt-optimize",
@@ -5145,7 +5716,8 @@
"name": "llm-application-dev-prompt-optimize",
"description": "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-evaluation",
@@ -5154,16 +5726,18 @@
"name": "llm-evaluation",
"description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "logistics-exception-management",
"path": "skills\\logistics-exception-management",
"category": "uncategorized",
"name": "logistics-exception-management",
- "description": "Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviours, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.\n",
+ "description": "Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "loki-mode",
@@ -5172,34 +5746,38 @@
"name": "loki-mode",
"description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-dotnet",
"path": "skills\\m365-agents-dotnet",
"category": "uncategorized",
"name": "m365-agents-dotnet",
- "description": "Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"Microsoft.Agents\", \"AddAgentApplicationOptions\", \"AgentApplication\", \"AddAgentAspNetAuthentication\", \"Copilot Studio client\", \"IAgentHttpAdapter\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft.Agents SDK with ASP.NET Core hosting, agent routing, and MSAL-based authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-py",
"path": "skills\\m365-agents-py",
"category": "uncategorized",
"name": "m365-agents-py",
- "description": "Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"microsoft_agents\", \"AgentApplication\", \"start_agent_process\", \"TurnContext\", \"Copilot Studio client\", \"CloudAdapter\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft Agents SDK with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-ts",
"path": "skills\\m365-agents-ts",
"category": "uncategorized",
"name": "m365-agents-ts",
- "description": "Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: \"Microsoft 365 Agents SDK\", \"@microsoft/agents-hosting\", \"AgentApplication\", \"startServer\", \"streamingResponse\", \"Copilot Studio client\", \"@microsoft/agents-copilotstudio-client\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft 365 Agents SDK with Express hosting, AgentApplication routing, streaming responses, and Copilot Studio client integrations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "machine-learning-ops-ml-pipeline",
@@ -5208,7 +5786,8 @@
"name": "machine-learning-ops-ml-pipeline",
"description": "Design and implement a complete ML pipeline for: $ARGUMENTS",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mailchimp-automation",
@@ -5217,7 +5796,8 @@
"name": "mailchimp-automation",
"description": "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "make-automation",
@@ -5226,7 +5806,8 @@
"name": "make-automation",
"description": "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "makepad-skills",
@@ -5235,16 +5816,18 @@
"name": "makepad-skills",
"description": "Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.",
"risk": "safe",
- "source": "https://github.com/ZhangHanDong/makepad-skills"
+ "source": "https://github.com/ZhangHanDong/makepad-skills",
+ "date_added": "2025-02-26"
},
{
"id": "malware-analyst",
"path": "skills\\malware-analyst",
"category": "uncategorized",
"name": "malware-analyst",
- "description": "Expert malware analyst specializing in defensive malware research,\nthreat intelligence, and incident response. Masters sandbox analysis,\nbehavioral analysis, and malware family identification. Handles static/dynamic\nanalysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,\nthreat hunting, incident response, or security research.\n",
+ "description": "file sample.exe sha256sum sample.exe",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "manifest",
@@ -5253,16 +5836,18 @@
"name": "manifest",
"description": "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "market-sizing-analysis",
"path": "skills\\market-sizing-analysis",
"category": "uncategorized",
"name": "market-sizing-analysis",
- "description": "This skill should be used when the user asks to \\\\\\\"calculate TAM\\\\\\\",\n\"determine SAM\", \"estimate SOM\", \"size the market\", \"calculate market\nopportunity\", \"what's the total addressable market\", or requests market sizing\nanalysis for a startup or business opportunity.\n",
+ "description": "Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "marketing-ideas",
@@ -5271,7 +5856,8 @@
"name": "marketing-ideas",
"description": "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "marketing-psychology",
@@ -5280,7 +5866,8 @@
"name": "marketing-psychology",
"description": "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mcp-builder",
@@ -5289,7 +5876,8 @@
"name": "mcp-builder",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mcp-builder-ms",
@@ -5298,7 +5886,8 @@
"name": "mcp-builder-ms",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-forensics",
@@ -5307,7 +5896,8 @@
"name": "memory-forensics",
"description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-safety-patterns",
@@ -5316,7 +5906,8 @@
"name": "memory-safety-patterns",
"description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-systems",
@@ -5325,16 +5916,18 @@
"name": "memory-systems",
"description": "Design short-term, long-term, and graph-based memory architectures",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/memory-systems"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/memory-systems",
+ "date_added": "2025-02-26"
},
{
"id": "mermaid-expert",
"path": "skills\\mermaid-expert",
"category": "uncategorized",
"name": "mermaid-expert",
- "description": "Create Mermaid diagrams for flowcharts, sequences, ERDs, and\narchitectures. Masters syntax for all diagram types and styling. Use\nPROACTIVELY for visual documentation, system diagrams, or process flows.\n",
+ "description": "- Working on mermaid expert tasks or workflows - Needing guidance, best practices, or checklists for mermaid expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "metasploit-framework",
@@ -5343,7 +5936,8 @@
"name": "metasploit-framework",
"description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "micro-saas-launcher",
@@ -5352,7 +5946,8 @@
"name": "micro-saas-launcher",
"description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "microservices-patterns",
@@ -5361,16 +5956,18 @@
"name": "microservices-patterns",
"description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"path": "skills\\microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"category": "uncategorized",
"name": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
- "description": "Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: \"Authentication Events\", \"WebJobsAuthenticationEventsTrigger\", \"OnTokenIssuanceStart\", \"OnAttributeCollectionStart\", \"custom claims\", \"token enrichment\", \"Entra custom extension\", \"authentication extension\".\n",
+ "description": "Azure Functions extension for handling Microsoft Entra ID custom authentication events.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "microsoft-teams-automation",
@@ -5379,16 +5976,18 @@
"name": "microsoft-teams-automation",
"description": "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "minecraft-bukkit-pro",
"path": "skills\\minecraft-bukkit-pro",
"category": "uncategorized",
"name": "minecraft-bukkit-pro",
- "description": "Master Minecraft server plugin development with Bukkit, Spigot, and\nPaper APIs. Specializes in event-driven architecture, command systems, world\nmanipulation, player management, and performance optimization. Use PROACTIVELY\nfor plugin architecture, gameplay mechanics, server-side features, or\ncross-version compatibility.\n",
+ "description": "- Working on minecraft bukkit pro tasks or workflows - Needing guidance, best practices, or checklists for minecraft bukkit pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "miro-automation",
@@ -5397,7 +5996,8 @@
"name": "miro-automation",
"description": "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mixpanel-automation",
@@ -5406,16 +6006,18 @@
"name": "mixpanel-automation",
"description": "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ml-engineer",
"path": "skills\\ml-engineer",
"category": "uncategorized",
"name": "ml-engineer",
- "description": "Build production ML systems with PyTorch 2.x, TensorFlow, and\nmodern ML frameworks. Implements model serving, feature engineering, A/B\ntesting, and monitoring. Use PROACTIVELY for ML model deployment, inference\noptimization, or production ML infrastructure.\n",
+ "description": "- Working on ml engineer tasks or workflows - Needing guidance, best practices, or checklists for ml engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ml-pipeline-workflow",
@@ -5424,16 +6026,18 @@
"name": "ml-pipeline-workflow",
"description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mlops-engineer",
"path": "skills\\mlops-engineer",
"category": "uncategorized",
"name": "mlops-engineer",
- "description": "Build comprehensive ML pipelines, experiment tracking, and model\nregistries with MLflow, Kubeflow, and modern MLOps tools. Implements automated\ntraining, deployment, and monitoring across cloud platforms. Use PROACTIVELY\nfor ML infrastructure, experiment management, or pipeline automation.\n",
+ "description": "- Working on mlops engineer tasks or workflows - Needing guidance, best practices, or checklists for mlops engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-design",
@@ -5442,16 +6046,18 @@
"name": "mobile-design",
"description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-developer",
"path": "skills\\mobile-developer",
"category": "uncategorized",
"name": "mobile-developer",
- "description": "Develop React Native, Flutter, or native mobile apps with modern\narchitecture patterns. Masters cross-platform development, native\nintegrations, offline sync, and app store optimization. Use PROACTIVELY for\nmobile features, cross-platform code, or app optimization.\n",
+ "description": "- Working on mobile developer tasks or workflows - Needing guidance, best practices, or checklists for mobile developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-games",
@@ -5460,16 +6066,18 @@
"name": "mobile-games",
"description": "Mobile game development principles. Touch input, battery, performance, app stores.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-security-coder",
"path": "skills\\mobile-security-coder",
"category": "uncategorized",
"name": "mobile-security-coder",
- "description": "Expert in secure mobile coding practices specializing in input\nvalidation, WebView security, and mobile-specific security patterns. Use\nPROACTIVELY for mobile security implementations or mobile security code\nreviews.\n",
+ "description": "- Working on mobile security coder tasks or workflows - Needing guidance, best practices, or checklists for mobile security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "modern-javascript-patterns",
@@ -5478,7 +6086,8 @@
"name": "modern-javascript-patterns",
"description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monday-automation",
@@ -5487,7 +6096,8 @@
"name": "monday-automation",
"description": "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monorepo-architect",
@@ -5496,7 +6106,8 @@
"name": "monorepo-architect",
"description": "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monorepo-management",
@@ -5505,7 +6116,8 @@
"name": "monorepo-management",
"description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "moodle-external-api-development",
@@ -5514,7 +6126,8 @@
"name": "moodle-external-api-development",
"description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mtls-configuration",
@@ -5523,16 +6136,18 @@
"name": "mtls-configuration",
"description": "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-agent-brainstorming",
"path": "skills\\multi-agent-brainstorming",
"category": "uncategorized",
"name": "multi-agent-brainstorming",
- "description": "Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.",
+ "description": "Transform a single-agent design into a **robust, review-validated design** by simulating a formal peer-review process using multiple constrained agents.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-agent-patterns",
@@ -5541,7 +6156,8 @@
"name": "multi-agent-patterns",
"description": "Master orchestrator, peer-to-peer, and hierarchical multi-agent architectures",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/multi-agent-patterns"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/multi-agent-patterns",
+ "date_added": "2025-02-26"
},
{
"id": "multi-cloud-architecture",
@@ -5550,7 +6166,8 @@
"name": "multi-cloud-architecture",
"description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-platform-apps-multi-platform",
@@ -5559,7 +6176,8 @@
"name": "multi-platform-apps-multi-platform",
"description": "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multiplayer",
@@ -5568,7 +6186,8 @@
"name": "multiplayer",
"description": "Multiplayer game development principles. Architecture, networking, synchronization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-code-python",
@@ -5577,7 +6196,8 @@
"name": "n8n-code-python",
"description": "Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-code-python"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-code-python",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-mcp-tools-expert",
@@ -5586,7 +6206,8 @@
"name": "n8n-mcp-tools-expert",
"description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele...",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-node-configuration",
@@ -5595,7 +6216,8 @@
"name": "n8n-node-configuration",
"description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo...",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration",
+ "date_added": "2025-02-26"
},
{
"id": "nanobanana-ppt-skills",
@@ -5604,7 +6226,8 @@
"name": "nanobanana-ppt-skills",
"description": "AI-powered PPT generation with document analysis and styled images",
"risk": "safe",
- "source": "https://github.com/op7418/NanoBanana-PPT-Skills"
+ "source": "https://github.com/op7418/NanoBanana-PPT-Skills",
+ "date_added": "2025-02-26"
},
{
"id": "neon-postgres",
@@ -5613,7 +6236,8 @@
"name": "neon-postgres",
"description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nerdzao-elite",
@@ -5622,7 +6246,8 @@
"name": "nerdzao-elite",
"description": "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nerdzao-elite-gemini-high",
@@ -5631,7 +6256,8 @@
"name": "nerdzao-elite-gemini-high",
"description": "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade m\u00e1xima e efici\u00eancia de tokens.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nestjs-expert",
@@ -5640,7 +6266,8 @@
"name": "nestjs-expert",
"description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "network-101",
@@ -5649,16 +6276,18 @@
"name": "network-101",
"description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "network-engineer",
"path": "skills\\network-engineer",
"category": "uncategorized",
"name": "network-engineer",
- "description": "Expert network engineer specializing in modern cloud networking,\nsecurity architectures, and performance optimization. Masters multi-cloud\nconnectivity, service mesh, zero-trust networking, SSL/TLS, global load\nbalancing, and advanced troubleshooting. Handles CDN optimization, network\nautomation, and compliance. Use PROACTIVELY for network design, connectivity\nissues, or performance optimization.\n",
+ "description": "- Working on network engineer tasks or workflows - Needing guidance, best practices, or checklists for network engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-app-router-patterns",
@@ -5667,7 +6296,8 @@
"name": "nextjs-app-router-patterns",
"description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-best-practices",
@@ -5676,7 +6306,8 @@
"name": "nextjs-best-practices",
"description": "Next.js App Router principles. Server Components, data fetching, routing patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-supabase-auth",
@@ -5685,7 +6316,8 @@
"name": "nextjs-supabase-auth",
"description": "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nft-standards",
@@ -5694,7 +6326,8 @@
"name": "nft-standards",
"description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nodejs-backend-patterns",
@@ -5703,7 +6336,8 @@
"name": "nodejs-backend-patterns",
"description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nodejs-best-practices",
@@ -5712,7 +6346,8 @@
"name": "nodejs-best-practices",
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nosql-expert",
@@ -5721,7 +6356,8 @@
"name": "nosql-expert",
"description": "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notebooklm",
@@ -5730,7 +6366,8 @@
"name": "notebooklm",
"description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth....",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notion-automation",
@@ -5739,7 +6376,8 @@
"name": "notion-automation",
"description": "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notion-template-business",
@@ -5748,7 +6386,8 @@
"name": "notion-template-business",
"description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nx-workspace-patterns",
@@ -5757,16 +6396,18 @@
"name": "nx-workspace-patterns",
"description": "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-engineer",
"path": "skills\\observability-engineer",
"category": "uncategorized",
"name": "observability-engineer",
- "description": "Build production-ready monitoring, logging, and tracing systems.\nImplements comprehensive observability strategies, SLI/SLO management, and\nincident response workflows. Use PROACTIVELY for monitoring infrastructure,\nperformance optimization, or production reliability.\n",
+ "description": "You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-monitoring-monitor-setup",
@@ -5775,7 +6416,8 @@
"name": "observability-monitoring-monitor-setup",
"description": "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-monitoring-slo-implement",
@@ -5784,7 +6426,8 @@
"name": "observability-monitoring-slo-implement",
"description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observe-whatsapp",
@@ -5793,7 +6436,8 @@
"name": "observe-whatsapp",
"description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f...",
"risk": "safe",
- "source": "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp"
+ "source": "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp",
+ "date_added": "2025-02-26"
},
{
"id": "obsidian-clipper-template-creator",
@@ -5802,7 +6446,8 @@
"name": "obsidian-clipper-template-creator",
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "office-productivity",
@@ -5811,7 +6456,8 @@
"name": "office-productivity",
"description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "on-call-handoff-patterns",
@@ -5820,7 +6466,8 @@
"name": "on-call-handoff-patterns",
"description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "onboarding-cro",
@@ -5829,7 +6476,8 @@
"name": "onboarding-cro",
"description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "one-drive-automation",
@@ -5838,7 +6486,8 @@
"name": "one-drive-automation",
"description": "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "openapi-spec-generation",
@@ -5847,7 +6496,8 @@
"name": "openapi-spec-generation",
"description": "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "os-scripting",
@@ -5856,7 +6506,8 @@
"name": "os-scripting",
"description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "oss-hunter",
@@ -5865,7 +6516,8 @@
"name": "oss-hunter",
"description": "Automatically hunt for high-impact OSS contribution opportunities in trending repositories.",
"risk": "safe",
- "source": "https://github.com/jackjin1997/ClawForge"
+ "source": "https://github.com/jackjin1997/ClawForge",
+ "date_added": "2025-02-26"
},
{
"id": "outlook-automation",
@@ -5874,7 +6526,8 @@
"name": "outlook-automation",
"description": "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "outlook-calendar-automation",
@@ -5883,16 +6536,18 @@
"name": "outlook-calendar-automation",
"description": "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "page-cro",
"path": "skills\\page-cro",
"category": "uncategorized",
"name": "page-cro",
- "description": "Analyze and optimize individual pages for conversion performance. Use when the user wants to improve conversion rates, diagnose why a page is underperforming, or increase the effectiveness of marketing pages (homepage, landing pages, pricing, feature pages, or blog posts). This skill focuses on diagnosis, prioritization, and testable recommendations\u2014 not blind optimization.\n",
+ "description": "You are an expert in **page-level conversion optimization**. Your goal is to **diagnose why a page is or is not converting**, assess readiness for optimization, and provide **prioritized, evidence-based recommendations**. You do **not** guarantee con",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pagerduty-automation",
@@ -5901,7 +6556,8 @@
"name": "pagerduty-automation",
"description": "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paid-ads",
@@ -5910,7 +6566,8 @@
"name": "paid-ads",
"description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "parallel-agents",
@@ -5919,16 +6576,18 @@
"name": "parallel-agents",
"description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "payment-integration",
"path": "skills\\payment-integration",
"category": "uncategorized",
"name": "payment-integration",
- "description": "Integrate Stripe, PayPal, and payment processors. Handles checkout\nflows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when\nimplementing payments, billing, or subscription features.\n",
+ "description": "- Working on payment integration tasks or workflows - Needing guidance, best practices, or checklists for payment integration",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paypal-integration",
@@ -5937,7 +6596,8 @@
"name": "paypal-integration",
"description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paywall-upgrade-cro",
@@ -5946,7 +6606,8 @@
"name": "paywall-upgrade-cro",
"description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pc-games",
@@ -5955,7 +6616,8 @@
"name": "pc-games",
"description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pci-compliance",
@@ -5964,7 +6626,8 @@
"name": "pci-compliance",
"description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pdf-official",
@@ -5973,7 +6636,8 @@
"name": "pdf-official",
"description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pentest-checklist",
@@ -5982,7 +6646,8 @@
"name": "pentest-checklist",
"description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pentest-commands",
@@ -5991,16 +6656,18 @@
"name": "pentest-commands",
"description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-engineer",
"path": "skills\\performance-engineer",
"category": "uncategorized",
"name": "performance-engineer",
- "description": "Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.",
+ "description": "Expert performance engineer specializing in modern observability,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-profiling",
@@ -6009,7 +6676,8 @@
"name": "performance-profiling",
"description": "Performance profiling principles. Measurement, analysis, and optimization techniques.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-testing-review-ai-review",
@@ -6018,7 +6686,8 @@
"name": "performance-testing-review-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-testing-review-multi-agent-review",
@@ -6027,7 +6696,8 @@
"name": "performance-testing-review-multi-agent-review",
"description": "Use when working with performance testing review multi agent review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "personal-tool-builder",
@@ -6036,16 +6706,18 @@
"name": "personal-tool-builder",
"description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "php-pro",
"path": "skills\\php-pro",
"category": "uncategorized",
"name": "php-pro",
- "description": "Write idiomatic PHP code with generators, iterators, SPL data\nstructures, and modern OOP features. Use PROACTIVELY for high-performance PHP\napplications.\n",
+ "description": "- Working on php pro tasks or workflows - Needing guidance, best practices, or checklists for php pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pipedrive-automation",
@@ -6054,7 +6726,8 @@
"name": "pipedrive-automation",
"description": "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "plaid-fintech",
@@ -6063,7 +6736,8 @@
"name": "plaid-fintech",
"description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "plan-writing",
@@ -6072,7 +6746,8 @@
"name": "plan-writing",
"description": "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "planning-with-files",
@@ -6081,7 +6756,8 @@
"name": "planning-with-files",
"description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "playwright-skill",
@@ -6090,7 +6766,8 @@
"name": "playwright-skill",
"description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "podcast-generation",
@@ -6099,7 +6776,8 @@
"name": "podcast-generation",
"description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "popup-cro",
@@ -6108,16 +6786,18 @@
"name": "popup-cro",
"description": "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "posix-shell-pro",
"path": "skills\\posix-shell-pro",
"category": "uncategorized",
"name": "posix-shell-pro",
- "description": "Expert in strict POSIX sh scripting for maximum portability across\nUnix-like systems. Specializes in shell scripts that run on any\nPOSIX-compliant shell (dash, ash, sh, bash --posix).\n",
+ "description": "- Working on posix shell pro tasks or workflows - Needing guidance, best practices, or checklists for posix shell pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgres-best-practices",
@@ -6126,7 +6806,8 @@
"name": "postgres-best-practices",
"description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgresql",
@@ -6135,7 +6816,8 @@
"name": "postgresql",
"description": "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgresql-optimization",
@@ -6144,7 +6826,8 @@
"name": "postgresql-optimization",
"description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "posthog-automation",
@@ -6153,7 +6836,8 @@
"name": "posthog-automation",
"description": "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postmark-automation",
@@ -6162,7 +6846,8 @@
"name": "postmark-automation",
"description": "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postmortem-writing",
@@ -6171,7 +6856,8 @@
"name": "postmortem-writing",
"description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "powershell-windows",
@@ -6180,7 +6866,8 @@
"name": "powershell-windows",
"description": "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pptx-official",
@@ -6189,7 +6876,8 @@
"name": "pptx-official",
"description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pricing-strategy",
@@ -6198,7 +6886,8 @@
"name": "pricing-strategy",
"description": "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prisma-expert",
@@ -6207,7 +6896,8 @@
"name": "prisma-expert",
"description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "privilege-escalation-methods",
@@ -6216,7 +6906,8 @@
"name": "privilege-escalation-methods",
"description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "product-manager-toolkit",
@@ -6225,7 +6916,8 @@
"name": "product-manager-toolkit",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "production-code-audit",
@@ -6234,25 +6926,28 @@
"name": "production-code-audit",
"description": "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "production-scheduling",
"path": "skills\\production-scheduling",
"category": "uncategorized",
"name": "production-scheduling",
- "description": "Codified expertise for production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimising changeovers, responding to disruptions, or balancing manufacturing lines.\n",
+ "description": "Use this skill when planning manufacturing operations, sequencing jobs to minimize changeover times, balancing production lines, resolving factory bottlenecks, or responding to unexpected equipment downtime and supply disruptions.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "programmatic-seo",
"path": "skills\\programmatic-seo",
"category": "uncategorized",
"name": "programmatic-seo",
- "description": "Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design\u2014not execution unless explicitly requested.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "projection-patterns",
@@ -6261,7 +6956,8 @@
"name": "projection-patterns",
"description": "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prometheus-configuration",
@@ -6270,7 +6966,8 @@
"name": "prometheus-configuration",
"description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-caching",
@@ -6279,7 +6976,8 @@
"name": "prompt-caching",
"description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineer",
@@ -6288,7 +6986,8 @@
"name": "prompt-engineer",
"description": "Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineering",
@@ -6297,7 +6996,8 @@
"name": "prompt-engineering",
"description": "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineering-patterns",
@@ -6306,7 +7006,8 @@
"name": "prompt-engineering-patterns",
"description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-library",
@@ -6315,7 +7016,8 @@
"name": "prompt-library",
"description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "protocol-reverse-engineering",
@@ -6324,7 +7026,8 @@
"name": "protocol-reverse-engineering",
"description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pydantic-models-py",
@@ -6333,7 +7036,8 @@
"name": "pydantic-models-py",
"description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pypict-skill",
@@ -6342,7 +7046,8 @@
"name": "pypict-skill",
"description": "Pairwise test generation",
"risk": "safe",
- "source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md"
+ "source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "python-development-python-scaffold",
@@ -6351,7 +7056,8 @@
"name": "python-development-python-scaffold",
"description": "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-fastapi-development",
@@ -6360,7 +7066,8 @@
"name": "python-fastapi-development",
"description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "python-packaging",
@@ -6369,7 +7076,8 @@
"name": "python-packaging",
"description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-patterns",
@@ -6378,7 +7086,8 @@
"name": "python-patterns",
"description": "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-performance-optimization",
@@ -6387,16 +7096,18 @@
"name": "python-performance-optimization",
"description": "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-pro",
"path": "skills\\python-pro",
"category": "uncategorized",
"name": "python-pro",
- "description": "Master Python 3.12+ with modern features, async programming,\nperformance optimization, and production-ready practices. Expert in the latest\nPython ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY\nfor Python development, optimization, or advanced Python patterns.\n",
+ "description": "You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-testing-patterns",
@@ -6405,25 +7116,28 @@
"name": "python-testing-patterns",
"description": "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "quality-nonconformance",
"path": "skills\\quality-nonconformance",
"category": "uncategorized",
"name": "quality-nonconformance",
- "description": "Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.\n",
+ "description": "Use this skill when investigating product defects or process deviations, performing root cause analysis (RCA), managing Corrective and Preventive Actions (CAPA), interpreting Statistical Process Control (SPC) data, or auditing supplier quality.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "quant-analyst",
"path": "skills\\quant-analyst",
"category": "uncategorized",
"name": "quant-analyst",
- "description": "Build financial models, backtest trading strategies, and analyze\nmarket data. Implements risk metrics, portfolio optimization, and statistical\narbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or\nrisk analysis.\n",
+ "description": "- Working on quant analyst tasks or workflows - Needing guidance, best practices, or checklists for quant analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "radix-ui-design-system",
@@ -6432,7 +7146,8 @@
"name": "radix-ui-design-system",
"description": "Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "rag-engineer",
@@ -6441,7 +7156,8 @@
"name": "rag-engineer",
"description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "rag-implementation",
@@ -6450,7 +7166,8 @@
"name": "rag-implementation",
"description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "react-best-practices",
@@ -6459,7 +7176,8 @@
"name": "react-best-practices",
"description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-flow-architect",
@@ -6468,7 +7186,8 @@
"name": "react-flow-architect",
"description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-flow-node-ts",
@@ -6477,7 +7196,8 @@
"name": "react-flow-node-ts",
"description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-modernization",
@@ -6486,7 +7206,8 @@
"name": "react-modernization",
"description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-native-architecture",
@@ -6495,7 +7216,8 @@
"name": "react-native-architecture",
"description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-nextjs-development",
@@ -6504,7 +7226,8 @@
"name": "react-nextjs-development",
"description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "react-patterns",
@@ -6513,7 +7236,8 @@
"name": "react-patterns",
"description": "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-state-management",
@@ -6522,7 +7246,8 @@
"name": "react-state-management",
"description": "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-ui-patterns",
@@ -6531,7 +7256,8 @@
"name": "react-ui-patterns",
"description": "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "readme",
@@ -6540,7 +7266,8 @@
"name": "readme",
"description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...",
"risk": "safe",
- "source": "https://github.com/Shpigford/skills/tree/main/readme"
+ "source": "https://github.com/Shpigford/skills/tree/main/readme",
+ "date_added": "2025-02-26"
},
{
"id": "receiving-code-review",
@@ -6549,7 +7276,8 @@
"name": "receiving-code-review",
"description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "red-team-tactics",
@@ -6558,7 +7286,8 @@
"name": "red-team-tactics",
"description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "red-team-tools",
@@ -6567,7 +7296,8 @@
"name": "red-team-tools",
"description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "reddit-automation",
@@ -6576,16 +7306,18 @@
"name": "reddit-automation",
"description": "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "reference-builder",
"path": "skills\\reference-builder",
"category": "uncategorized",
"name": "reference-builder",
- "description": "Creates exhaustive technical references and API documentation.\nGenerates comprehensive parameter listings, configuration guides, and\nsearchable reference materials. Use PROACTIVELY for API docs, configuration\nreferences, or complete technical specifications.\n",
+ "description": "- Working on reference builder tasks or workflows - Needing guidance, best practices, or checklists for reference builder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "referral-program",
@@ -6594,7 +7326,8 @@
"name": "referral-program",
"description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "remotion-best-practices",
@@ -6603,7 +7336,8 @@
"name": "remotion-best-practices",
"description": "Best practices for Remotion - Video creation in React",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "render-automation",
@@ -6612,7 +7346,8 @@
"name": "render-automation",
"description": "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "requesting-code-review",
@@ -6621,7 +7356,8 @@
"name": "requesting-code-review",
"description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "research-engineer",
@@ -6630,34 +7366,38 @@
"name": "research-engineer",
"description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "returns-reverse-logistics",
"path": "skills\\returns-reverse-logistics",
"category": "uncategorized",
"name": "returns-reverse-logistics",
- "description": "Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.\n",
+ "description": "Use this skill when managing the product return lifecycle, including authorization, physical inspection, making disposition decisions (e.g., restock vs. liquidator), detecting return fraud, or processing warranty claims.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "reverse-engineer",
"path": "skills\\reverse-engineer",
"category": "uncategorized",
"name": "reverse-engineer",
- "description": "Expert reverse engineer specializing in binary analysis,\ndisassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,\nradare2, x64dbg, and modern RE toolchains. Handles executable analysis,\nlibrary inspection, protocol extraction, and vulnerability research. Use\nPROACTIVELY for binary analysis, CTF challenges, security research, or\nunderstanding undocumented software.\n",
+ "description": "- IDAPython (IDA Pro scripting) - Ghidra scripting (Java/Python via Jython) - r2pipe (radare2 Python API) - pwntools (CTF/exploitation toolkit) - capstone (disassembly framework) - keystone (assembly framework) - unicorn (CPU emulator framework) - an",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "risk-manager",
"path": "skills\\risk-manager",
"category": "uncategorized",
"name": "risk-manager",
- "description": "Monitor portfolio risk, R-multiples, and position limits. Creates\nhedging strategies, calculates expectancy, and implements stop-losses. Use\nPROACTIVELY for risk assessment, trade tracking, or portfolio protection.\n",
+ "description": "- Working on risk manager tasks or workflows - Needing guidance, best practices, or checklists for risk manager",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "risk-metrics-calculation",
@@ -6666,16 +7406,18 @@
"name": "risk-metrics-calculation",
"description": "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ruby-pro",
"path": "skills\\ruby-pro",
"category": "uncategorized",
"name": "ruby-pro",
- "description": "Write idiomatic Ruby code with metaprogramming, Rails patterns, and\nperformance optimization. Specializes in Ruby on Rails, gem development, and\ntesting frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or\ncomplex Ruby features.\n",
+ "description": "- Working on ruby pro tasks or workflows - Needing guidance, best practices, or checklists for ruby pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "rust-async-patterns",
@@ -6684,16 +7426,18 @@
"name": "rust-async-patterns",
"description": "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "rust-pro",
"path": "skills\\rust-pro",
"category": "uncategorized",
"name": "rust-pro",
- "description": "Master Rust 1.75+ with modern async patterns, advanced type system\nfeatures, and production-ready systems programming. Expert in the latest Rust\necosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for\nRust development, performance optimization, or systems programming.\n",
+ "description": "You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "saga-orchestration",
@@ -6702,16 +7446,18 @@
"name": "saga-orchestration",
"description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sales-automator",
"path": "skills\\sales-automator",
"category": "uncategorized",
"name": "sales-automator",
- "description": "Draft cold emails, follow-ups, and proposal templates. Creates\npricing pages, case studies, and sales scripts. Use PROACTIVELY for sales\noutreach or lead nurturing.\n",
+ "description": "- Working on sales automator tasks or workflows - Needing guidance, best practices, or checklists for sales automator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "salesforce-automation",
@@ -6720,7 +7466,8 @@
"name": "salesforce-automation",
"description": "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "salesforce-development",
@@ -6729,7 +7476,8 @@
"name": "salesforce-development",
"description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "sast-configuration",
@@ -6738,16 +7486,18 @@
"name": "sast-configuration",
"description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "scala-pro",
"path": "skills\\scala-pro",
"category": "uncategorized",
"name": "scala-pro",
- "description": "Master enterprise-grade Scala development with functional\nprogramming, distributed systems, and big data processing. Expert in Apache\nPekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use\nPROACTIVELY for Scala system design, performance optimization, or enterprise\nintegration.\n",
+ "description": "- Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "scanning-tools",
@@ -6756,16 +7506,18 @@
"name": "scanning-tools",
"description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "schema-markup",
"path": "skills\\schema-markup",
"category": "uncategorized",
"name": "schema-markup",
- "description": "Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "screen-reader-testing",
@@ -6774,7 +7526,8 @@
"name": "screen-reader-testing",
"description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "screenshots",
@@ -6783,7 +7536,8 @@
"name": "screenshots",
"description": "Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.",
"risk": "safe",
- "source": "https://github.com/Shpigford/skills/tree/main/screenshots"
+ "source": "https://github.com/Shpigford/skills/tree/main/screenshots",
+ "date_added": "2025-02-26"
},
{
"id": "scroll-experience",
@@ -6792,16 +7546,18 @@
"name": "scroll-experience",
"description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "search-specialist",
"path": "skills\\search-specialist",
"category": "uncategorized",
"name": "search-specialist",
- "description": "Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.",
+ "description": "Expert web researcher using advanced search techniques and",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "secrets-management",
@@ -6810,7 +7566,8 @@
"name": "secrets-management",
"description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-audit",
@@ -6819,16 +7576,18 @@
"name": "security-audit",
"description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "security-auditor",
"path": "skills\\security-auditor",
"category": "uncategorized",
"name": "security-auditor",
- "description": "Expert security auditor specializing in DevSecOps, comprehensive\ncybersecurity, and compliance frameworks. Masters vulnerability assessment,\nthreat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud\nsecurity, and security automation. Handles DevSecOps integration, compliance\n(GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits,\nDevSecOps, or compliance implementation.\n",
+ "description": "You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-bluebook-builder",
@@ -6837,7 +7596,8 @@
"name": "security-bluebook-builder",
"description": "Build security Blue Books for sensitive apps",
"risk": "safe",
- "source": "https://github.com/SHADOWPR0/security-bluebook-builder"
+ "source": "https://github.com/SHADOWPR0/security-bluebook-builder",
+ "date_added": "2025-02-26"
},
{
"id": "security-compliance-compliance-check",
@@ -6846,7 +7606,8 @@
"name": "security-compliance-compliance-check",
"description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-requirement-extraction",
@@ -6855,7 +7616,8 @@
"name": "security-requirement-extraction",
"description": "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-dependencies",
@@ -6864,7 +7626,8 @@
"name": "security-scanning-security-dependencies",
"description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-hardening",
@@ -6873,16 +7636,18 @@
"name": "security-scanning-security-hardening",
"description": "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-sast",
"path": "skills\\security-scanning-security-sast",
"category": "uncategorized",
"name": "security-scanning-security-sast",
- "description": "Static Application Security Testing (SAST) for code vulnerability\nanalysis across multiple languages and frameworks\n",
+ "description": "Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "segment-automation",
@@ -6891,7 +7656,8 @@
"name": "segment-automation",
"description": "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "segment-cdp",
@@ -6900,7 +7666,8 @@
"name": "segment-cdp",
"description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "sendgrid-automation",
@@ -6909,7 +7676,8 @@
"name": "sendgrid-automation",
"description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "senior-architect",
@@ -6918,7 +7686,8 @@
"name": "senior-architect",
"description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "senior-fullstack",
@@ -6927,7 +7696,8 @@
"name": "senior-fullstack",
"description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sentry-automation",
@@ -6936,115 +7706,128 @@
"name": "sentry-automation",
"description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-audit",
"path": "skills\\seo-audit",
"category": "uncategorized",
"name": "seo-audit",
- "description": "Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.\n",
+ "description": "You are an **SEO diagnostic specialist**. Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility\u2014**not to implement fixes unless explicitly requested**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-authority-builder",
"path": "skills\\seo-authority-builder",
"category": "uncategorized",
"name": "seo-authority-builder",
- "description": "Analyzes content for E-E-A-T signals and suggests improvements to\nbuild authority and trust. Identifies missing credibility elements. Use\nPROACTIVELY for YMYL topics.\n",
+ "description": "- Working on seo authority builder tasks or workflows - Needing guidance, best practices, or checklists for seo authority builder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-cannibalization-detector",
"path": "skills\\seo-cannibalization-detector",
"category": "uncategorized",
"name": "seo-cannibalization-detector",
- "description": "Analyzes multiple provided pages to identify keyword overlap and\npotential cannibalization issues. Suggests differentiation strategies. Use\nPROACTIVELY when reviewing similar content.\n",
+ "description": "- Working on seo cannibalization detector tasks or workflows - Needing guidance, best practices, or checklists for seo cannibalization detector",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-auditor",
"path": "skills\\seo-content-auditor",
"category": "uncategorized",
"name": "seo-content-auditor",
- "description": "Analyzes provided content for quality, E-E-A-T signals, and SEO\nbest practices. Scores content and provides improvement recommendations based\non established guidelines. Use PROACTIVELY for content review.\n",
+ "description": "- Working on seo content auditor tasks or workflows - Needing guidance, best practices, or checklists for seo content auditor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-planner",
"path": "skills\\seo-content-planner",
"category": "uncategorized",
"name": "seo-content-planner",
- "description": "Creates comprehensive content outlines and topic clusters for SEO.\nPlans content calendars and identifies topic gaps. Use PROACTIVELY for content\nstrategy and planning.\n",
+ "description": "- Working on seo content planner tasks or workflows - Needing guidance, best practices, or checklists for seo content planner",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-refresher",
"path": "skills\\seo-content-refresher",
"category": "uncategorized",
"name": "seo-content-refresher",
- "description": "Identifies outdated elements in provided content and suggests\nupdates to maintain freshness. Finds statistics, dates, and examples that need\nupdating. Use PROACTIVELY for older content.\n",
+ "description": "- Working on seo content refresher tasks or workflows - Needing guidance, best practices, or checklists for seo content refresher",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-writer",
"path": "skills\\seo-content-writer",
"category": "uncategorized",
"name": "seo-content-writer",
- "description": "Writes SEO-optimized content based on provided keywords and topic\nbriefs. Creates engaging, comprehensive content following best practices. Use\nPROACTIVELY for content creation tasks.\n",
+ "description": "- Working on seo content writer tasks or workflows - Needing guidance, best practices, or checklists for seo content writer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-fundamentals",
"path": "skills\\seo-fundamentals",
"category": "uncategorized",
"name": "seo-fundamentals",
- "description": "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-keyword-strategist",
"path": "skills\\seo-keyword-strategist",
"category": "uncategorized",
"name": "seo-keyword-strategist",
- "description": "Analyzes keyword usage in provided content, calculates density,\nsuggests semantic variations and LSI keywords based on the topic. Prevents\nover-optimization. Use PROACTIVELY for content optimization.\n",
+ "description": "- Working on seo keyword strategist tasks or workflows - Needing guidance, best practices, or checklists for seo keyword strategist",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-meta-optimizer",
"path": "skills\\seo-meta-optimizer",
"category": "uncategorized",
"name": "seo-meta-optimizer",
- "description": "Creates optimized meta titles, descriptions, and URL suggestions\nbased on character limits and best practices. Generates compelling,\nkeyword-rich metadata. Use PROACTIVELY for new content.\n",
+ "description": "- Working on seo meta optimizer tasks or workflows - Needing guidance, best practices, or checklists for seo meta optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-snippet-hunter",
"path": "skills\\seo-snippet-hunter",
"category": "uncategorized",
"name": "seo-snippet-hunter",
- "description": "Formats content to be eligible for featured snippets and SERP\nfeatures. Creates snippet-optimized content blocks based on best practices.\nUse PROACTIVELY for question-based content.\n",
+ "description": "- Working on seo snippet hunter tasks or workflows - Needing guidance, best practices, or checklists for seo snippet hunter",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-structure-architect",
"path": "skills\\seo-structure-architect",
"category": "uncategorized",
"name": "seo-structure-architect",
- "description": "Analyzes and optimizes content structure including header\nhierarchy, suggests schema markup, and internal linking opportunities. Creates\nsearch-friendly content organization. Use PROACTIVELY for content structuring.\n",
+ "description": "- Working on seo structure architect tasks or workflows - Needing guidance, best practices, or checklists for seo structure architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "server-management",
@@ -7053,7 +7836,8 @@
"name": "server-management",
"description": "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "service-mesh-expert",
@@ -7062,7 +7846,8 @@
"name": "service-mesh-expert",
"description": "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "service-mesh-observability",
@@ -7071,7 +7856,8 @@
"name": "service-mesh-observability",
"description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shader-programming-glsl",
@@ -7080,7 +7866,8 @@
"name": "shader-programming-glsl",
"description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sharp-edges",
@@ -7089,7 +7876,8 @@
"name": "sharp-edges",
"description": "Identify error-prone APIs and dangerous configurations",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges",
+ "date_added": "2025-02-26"
},
{
"id": "shellcheck-configuration",
@@ -7098,7 +7886,8 @@
"name": "shellcheck-configuration",
"description": "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shodan-reconnaissance",
@@ -7107,7 +7896,8 @@
"name": "shodan-reconnaissance",
"description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-apps",
@@ -7116,7 +7906,8 @@
"name": "shopify-apps",
"description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-automation",
@@ -7125,16 +7916,18 @@
"name": "shopify-automation",
"description": "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-development",
"path": "skills\\shopify-development",
"category": "uncategorized",
"name": "shopify-development",
- "description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"\n",
+ "description": "Use this skill when the user asks about:",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "signup-flow-cro",
@@ -7143,7 +7936,8 @@
"name": "signup-flow-cro",
"description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "similarity-search-patterns",
@@ -7152,7 +7946,8 @@
"name": "similarity-search-patterns",
"description": "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-creator",
@@ -7161,7 +7956,8 @@
"name": "skill-creator",
"description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s...",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-creator-ms",
@@ -7170,7 +7966,8 @@
"name": "skill-creator-ms",
"description": "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-developer",
@@ -7179,7 +7976,8 @@
"name": "skill-developer",
"description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-rails-upgrade",
@@ -7188,7 +7986,8 @@
"name": "skill-rails-upgrade",
"description": "Analyze Rails apps and provide upgrade assessments",
"risk": "safe",
- "source": "https://github.com/robzolkos/skill-rails-upgrade"
+ "source": "https://github.com/robzolkos/skill-rails-upgrade",
+ "date_added": "2025-02-26"
},
{
"id": "skill-seekers",
@@ -7197,7 +7996,8 @@
"name": "skill-seekers",
"description": "-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.",
"risk": "safe",
- "source": "https://github.com/yusufkaraaslan/Skill_Seekers"
+ "source": "https://github.com/yusufkaraaslan/Skill_Seekers",
+ "date_added": "2025-02-26"
},
{
"id": "slack-automation",
@@ -7206,7 +8006,8 @@
"name": "slack-automation",
"description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "slack-bot-builder",
@@ -7215,7 +8016,8 @@
"name": "slack-bot-builder",
"description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "slack-gif-creator",
@@ -7224,7 +8026,8 @@
"name": "slack-gif-creator",
"description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "slo-implementation",
@@ -7233,7 +8036,8 @@
"name": "slo-implementation",
"description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "smtp-penetration-testing",
@@ -7242,7 +8046,8 @@
"name": "smtp-penetration-testing",
"description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "social-content",
@@ -7251,7 +8056,8 @@
"name": "social-content",
"description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "software-architecture",
@@ -7260,7 +8066,8 @@
"name": "software-architecture",
"description": "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "solidity-security",
@@ -7269,7 +8076,8 @@
"name": "solidity-security",
"description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "spark-optimization",
@@ -7278,7 +8086,8 @@
"name": "spark-optimization",
"description": "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-injection-testing",
@@ -7287,7 +8096,8 @@
"name": "sql-injection-testing",
"description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-optimization-patterns",
@@ -7296,16 +8106,18 @@
"name": "sql-optimization-patterns",
"description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-pro",
"path": "skills\\sql-pro",
"category": "uncategorized",
"name": "sql-pro",
- "description": "Master modern SQL with cloud-native databases, OLTP/OLAP\noptimization, and advanced query techniques. Expert in performance tuning,\ndata modeling, and hybrid analytical systems. Use PROACTIVELY for database\noptimization or complex analysis.\n",
+ "description": "You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sqlmap-database-pentesting",
@@ -7314,7 +8126,8 @@
"name": "sqlmap-database-pentesting",
"description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "square-automation",
@@ -7323,7 +8136,8 @@
"name": "square-automation",
"description": "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ssh-penetration-testing",
@@ -7332,61 +8146,68 @@
"name": "ssh-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-analyst",
"path": "skills\\startup-analyst",
"category": "uncategorized",
"name": "startup-analyst",
- "description": "Expert startup business analyst specializing in market sizing,\nfinancial modeling, competitive analysis, and strategic planning for\nearly-stage companies. Use PROACTIVELY when the user asks about market\nopportunity, TAM/SAM/SOM, financial projections, unit economics, competitive\nlandscape, team planning, startup metrics, or business strategy for pre-seed\nthrough Series A startups.\n",
+ "description": "- Working on startup analyst tasks or workflows - Needing guidance, best practices, or checklists for startup analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-business-case",
"path": "skills\\startup-business-analyst-business-case",
"category": "uncategorized",
"name": "startup-business-analyst-business-case",
- "description": "Generate comprehensive investor-ready business case document with\nmarket, solution, financials, and strategy\n",
+ "description": "Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-financial-projections",
"path": "skills\\startup-business-analyst-financial-projections",
"category": "uncategorized",
"name": "startup-business-analyst-financial-projections",
- "description": "Create detailed 3-5 year financial model with revenue, costs, cash\nflow, and scenarios\n",
+ "description": "Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-market-opportunity",
"path": "skills\\startup-business-analyst-market-opportunity",
"category": "uncategorized",
"name": "startup-business-analyst-market-opportunity",
- "description": "Generate comprehensive market opportunity analysis with TAM/SAM/SOM\ncalculations\n",
+ "description": "Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-financial-modeling",
"path": "skills\\startup-financial-modeling",
"category": "uncategorized",
"name": "startup-financial-modeling",
- "description": "This skill should be used when the user asks to \\\\\\\"create financial\nprojections\", \"build a financial model\", \"forecast revenue\", \"calculate burn\nrate\", \"estimate runway\", \"model cash flow\", or requests 3-5 year financial\nplanning for a startup.\n",
+ "description": "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-metrics-framework",
"path": "skills\\startup-metrics-framework",
"category": "uncategorized",
"name": "startup-metrics-framework",
- "description": "This skill should be used when the user asks about \\\\\\\"key startup\nmetrics\", \"SaaS metrics\", \"CAC and LTV\", \"unit economics\", \"burn multiple\",\n\"rule of 40\", \"marketplace metrics\", or requests guidance on tracking and\noptimizing business performance metrics.\n",
+ "description": "Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stitch-ui-design",
@@ -7395,7 +8216,8 @@
"name": "stitch-ui-design",
"description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra...",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "stride-analysis-patterns",
@@ -7404,7 +8226,8 @@
"name": "stride-analysis-patterns",
"description": "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stripe-automation",
@@ -7413,7 +8236,8 @@
"name": "stripe-automation",
"description": "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stripe-integration",
@@ -7422,7 +8246,8 @@
"name": "stripe-integration",
"description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "subagent-driven-development",
@@ -7431,7 +8256,8 @@
"name": "subagent-driven-development",
"description": "Use when executing implementation plans with independent tasks in the current session",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "supabase-automation",
@@ -7440,7 +8266,8 @@
"name": "supabase-automation",
"description": "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "superpowers-lab",
@@ -7449,7 +8276,8 @@
"name": "superpowers-lab",
"description": "Lab environment for Claude superpowers",
"risk": "safe",
- "source": "https://github.com/obra/superpowers-lab"
+ "source": "https://github.com/obra/superpowers-lab",
+ "date_added": "2025-02-26"
},
{
"id": "swiftui-expert-skill",
@@ -7458,7 +8286,8 @@
"name": "swiftui-expert-skill",
"description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil...",
"risk": "safe",
- "source": "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill"
+ "source": "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill",
+ "date_added": "2025-02-26"
},
{
"id": "systematic-debugging",
@@ -7467,7 +8296,8 @@
"name": "systematic-debugging",
"description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "systems-programming-rust-project",
@@ -7476,7 +8306,8 @@
"name": "systems-programming-rust-project",
"description": "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tailwind-design-system",
@@ -7485,7 +8316,8 @@
"name": "tailwind-design-system",
"description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tailwind-patterns",
@@ -7494,7 +8326,8 @@
"name": "tailwind-patterns",
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tavily-web",
@@ -7503,16 +8336,18 @@
"name": "tavily-web",
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-orchestrator",
"path": "skills\\tdd-orchestrator",
"category": "uncategorized",
"name": "tdd-orchestrator",
- "description": "Master TDD orchestrator specializing in red-green-refactor\ndiscipline, multi-agent workflow coordination, and comprehensive test-driven\ndevelopment practices. Enforces TDD best practices across teams with\nAI-assisted testing and modern frameworks. Use PROACTIVELY for TDD\nimplementation and governance.\n",
+ "description": "- Working on tdd orchestrator tasks or workflows - Needing guidance, best practices, or checklists for tdd orchestrator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflow",
@@ -7521,7 +8356,8 @@
"name": "tdd-workflow",
"description": "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-cycle",
@@ -7530,7 +8366,8 @@
"name": "tdd-workflows-tdd-cycle",
"description": "Use when working with tdd workflows tdd cycle",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-green",
@@ -7539,7 +8376,8 @@
"name": "tdd-workflows-tdd-green",
"description": "Implement the minimal code needed to make failing tests pass in the TDD green phase.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-red",
@@ -7548,7 +8386,8 @@
"name": "tdd-workflows-tdd-red",
"description": "Generate failing tests for the TDD red phase to define expected behavior and edge cases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-refactor",
@@ -7557,7 +8396,8 @@
"name": "tdd-workflows-tdd-refactor",
"description": "Use when working with tdd workflows tdd refactor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-collaboration-issue",
@@ -7566,7 +8406,8 @@
"name": "team-collaboration-issue",
"description": "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-collaboration-standup-notes",
@@ -7575,16 +8416,18 @@
"name": "team-collaboration-standup-notes",
"description": "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-composition-analysis",
"path": "skills\\team-composition-analysis",
"category": "uncategorized",
"name": "team-composition-analysis",
- "description": "This skill should be used when the user asks to \\\\\\\"plan team\nstructure\", \"determine hiring needs\", \"design org chart\", \"calculate\ncompensation\", \"plan equity allocation\", or requests organizational design and\nheadcount planning for a startup.\n",
+ "description": "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-automation",
@@ -7593,7 +8436,8 @@
"name": "telegram-automation",
"description": "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-bot-builder",
@@ -7602,7 +8446,8 @@
"name": "telegram-bot-builder",
"description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-mini-app",
@@ -7611,7 +8456,8 @@
"name": "telegram-mini-app",
"description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "templates",
@@ -7620,16 +8466,18 @@
"name": "templates",
"description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "temporal-python-pro",
"path": "skills\\temporal-python-pro",
"category": "uncategorized",
"name": "temporal-python-pro",
- "description": "Master Temporal workflow orchestration with Python SDK. Implements\ndurable workflows, saga patterns, and distributed transactions. Covers\nasync/await, testing strategies, and production deployment. Use PROACTIVELY\nfor workflow design, microservice orchestration, or long-running processes.\n",
+ "description": "- Working on temporal python pro tasks or workflows - Needing guidance, best practices, or checklists for temporal python pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "temporal-python-testing",
@@ -7638,7 +8486,8 @@
"name": "temporal-python-testing",
"description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-aws-modules",
@@ -7647,7 +8496,8 @@
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-infrastructure",
@@ -7656,7 +8506,8 @@
"name": "terraform-infrastructure",
"description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-module-library",
@@ -7665,7 +8516,8 @@
"name": "terraform-module-library",
"description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-skill",
@@ -7674,25 +8526,28 @@
"name": "terraform-skill",
"description": "Terraform infrastructure as code best practices",
"risk": "safe",
- "source": "https://github.com/antonbabenko/terraform-skill"
+ "source": "https://github.com/antonbabenko/terraform-skill",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-specialist",
"path": "skills\\terraform-specialist",
"category": "uncategorized",
"name": "terraform-specialist",
- "description": "Expert Terraform/OpenTofu specialist mastering advanced IaC\nautomation, state management, and enterprise infrastructure patterns. Handles\ncomplex module design, multi-cloud deployments, GitOps workflows, policy as\ncode, and CI/CD integration. Covers migration strategies, security best\npractices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state\nmanagement, or infrastructure automation.\n",
+ "description": "You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-automator",
"path": "skills\\test-automator",
"category": "uncategorized",
"name": "test-automator",
- "description": "Master AI-powered test automation with modern frameworks,\nself-healing tests, and comprehensive quality engineering. Build scalable\ntesting strategies with advanced CI/CD integration. Use PROACTIVELY for\ntesting automation or quality assurance.\n",
+ "description": "- Working on test automator tasks or workflows - Needing guidance, best practices, or checklists for test automator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-driven-development",
@@ -7701,7 +8556,8 @@
"name": "test-driven-development",
"description": "Use when implementing any feature or bugfix, before writing implementation code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-fixing",
@@ -7710,7 +8566,8 @@
"name": "test-fixing",
"description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "testing-patterns",
@@ -7719,7 +8576,8 @@
"name": "testing-patterns",
"description": "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "testing-qa",
@@ -7728,7 +8586,8 @@
"name": "testing-qa",
"description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "theme-factory",
@@ -7737,7 +8596,8 @@
"name": "theme-factory",
"description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threat-mitigation-mapping",
@@ -7746,7 +8606,8 @@
"name": "threat-mitigation-mapping",
"description": "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threat-modeling-expert",
@@ -7755,7 +8616,8 @@
"name": "threat-modeling-expert",
"description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threejs-skills",
@@ -7764,7 +8626,8 @@
"name": "threejs-skills",
"description": "Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.",
"risk": "safe",
- "source": "https://github.com/CloudAI-X/threejs-skills"
+ "source": "https://github.com/CloudAI-X/threejs-skills",
+ "date_added": "2025-02-26"
},
{
"id": "tiktok-automation",
@@ -7773,7 +8636,8 @@
"name": "tiktok-automation",
"description": "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "todoist-automation",
@@ -7782,7 +8646,8 @@
"name": "todoist-automation",
"description": "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tool-design",
@@ -7791,7 +8656,8 @@
"name": "tool-design",
"description": "Build tools that agents can use effectively, including architectural reduction patterns",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/tool-design"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/tool-design",
+ "date_added": "2025-02-26"
},
{
"id": "top-web-vulnerabilities",
@@ -7800,16 +8666,18 @@
"name": "top-web-vulnerabilities",
"description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "track-management",
"path": "skills\\track-management",
"category": "uncategorized",
"name": "track-management",
- "description": "Use this skill when creating, managing, or working with Conductor\ntracks - the logical work units for features, bugs, and refactors. Applies to\nspec.md, plan.md, and track lifecycle operations.\n",
+ "description": "Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "trello-automation",
@@ -7818,7 +8686,8 @@
"name": "trello-automation",
"description": "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "trigger-dev",
@@ -7827,7 +8696,8 @@
"name": "trigger-dev",
"description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "turborepo-caching",
@@ -7836,16 +8706,18 @@
"name": "turborepo-caching",
"description": "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tutorial-engineer",
"path": "skills\\tutorial-engineer",
"category": "uncategorized",
"name": "tutorial-engineer",
- "description": "Creates step-by-step tutorials and educational content from code.\nTransforms complex concepts into progressive learning experiences with\nhands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,\nor concept explanations.\n",
+ "description": "- Working on tutorial engineer tasks or workflows - Needing guidance, best practices, or checklists for tutorial engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "twilio-communications",
@@ -7854,7 +8726,8 @@
"name": "twilio-communications",
"description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "twitter-automation",
@@ -7863,7 +8736,8 @@
"name": "twitter-automation",
"description": "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-advanced-types",
@@ -7872,25 +8746,28 @@
"name": "typescript-advanced-types",
"description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-expert",
"path": "skills\\typescript-expert",
"category": "uncategorized",
"name": "typescript-expert",
- "description": "TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.",
+ "description": "You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-pro",
"path": "skills\\typescript-pro",
"category": "uncategorized",
"name": "typescript-pro",
- "description": "Master TypeScript with advanced types, generics, and strict type\nsafety. Handles complex type systems, decorators, and enterprise-grade\npatterns. Use PROACTIVELY for TypeScript architecture, type inference\noptimization, or advanced typing patterns.\n",
+ "description": "You are a TypeScript expert specializing in advanced typing and enterprise-grade development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-skills",
@@ -7899,16 +8776,18 @@
"name": "ui-skills",
"description": "Opinionated, evolving constraints to guide agents when building interfaces",
"risk": "safe",
- "source": "https://github.com/ibelick/ui-skills"
+ "source": "https://github.com/ibelick/ui-skills",
+ "date_added": "2025-02-26"
},
{
"id": "ui-ux-designer",
"path": "skills\\ui-ux-designer",
"category": "uncategorized",
"name": "ui-ux-designer",
- "description": "Create interface designs, wireframes, and design systems. Masters\nuser research, accessibility standards, and modern design tools. Specializes\nin design tokens, component libraries, and inclusive design. Use PROACTIVELY\nfor design systems, user flows, or interface optimization.\n",
+ "description": "- Working on ui ux designer tasks or workflows - Needing guidance, best practices, or checklists for ui ux designer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-ux-pro-max",
@@ -7917,16 +8796,18 @@
"name": "ui-ux-pro-max",
"description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-visual-validator",
"path": "skills\\ui-visual-validator",
"category": "uncategorized",
"name": "ui-visual-validator",
- "description": "Rigorous visual validation expert specializing in UI testing,\ndesign system compliance, and accessibility verification. Masters screenshot\nanalysis, visual regression testing, and component validation. Use PROACTIVELY\nto verify UI modifications have achieved their intended goals through\ncomprehensive visual analysis.\n",
+ "description": "- Working on ui visual validator tasks or workflows - Needing guidance, best practices, or checklists for ui visual validator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unit-testing-test-generate",
@@ -7935,16 +8816,18 @@
"name": "unit-testing-test-generate",
"description": "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unity-developer",
"path": "skills\\unity-developer",
"category": "uncategorized",
"name": "unity-developer",
- "description": "Build Unity games with optimized C# scripts, efficient rendering,\nand proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and\ncross-platform deployment. Handles gameplay systems, UI implementation, and\nplatform optimization. Use PROACTIVELY for Unity performance issues, game\nmechanics, or cross-platform builds.\n",
+ "description": "- Working on unity developer tasks or workflows - Needing guidance, best practices, or checklists for unity developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unity-ecs-patterns",
@@ -7953,7 +8836,8 @@
"name": "unity-ecs-patterns",
"description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unreal-engine-cpp-pro",
@@ -7962,7 +8846,8 @@
"name": "unreal-engine-cpp-pro",
"description": "Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "upgrading-expo",
@@ -7971,7 +8856,8 @@
"name": "upgrading-expo",
"description": "Upgrade Expo SDK versions",
"risk": "safe",
- "source": "https://github.com/expo/skills/tree/main/plugins/upgrading-expo"
+ "source": "https://github.com/expo/skills/tree/main/plugins/upgrading-expo",
+ "date_added": "2025-02-26"
},
{
"id": "upstash-qstash",
@@ -7980,7 +8866,8 @@
"name": "upstash-qstash",
"description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "using-git-worktrees",
@@ -7989,7 +8876,8 @@
"name": "using-git-worktrees",
"description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "using-neon",
@@ -7998,7 +8886,8 @@
"name": "using-neon",
"description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/...",
"risk": "safe",
- "source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres"
+ "source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres",
+ "date_added": "2025-02-26"
},
{
"id": "using-superpowers",
@@ -8007,7 +8896,8 @@
"name": "using-superpowers",
"description": "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "uv-package-manager",
@@ -8016,7 +8906,8 @@
"name": "uv-package-manager",
"description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "varlock-claude-skill",
@@ -8025,7 +8916,8 @@
"name": "varlock-claude-skill",
"description": "Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits",
"risk": "safe",
- "source": "https://github.com/wrsmith108/varlock-claude-skill"
+ "source": "https://github.com/wrsmith108/varlock-claude-skill",
+ "date_added": "2025-02-26"
},
{
"id": "vector-database-engineer",
@@ -8034,7 +8926,8 @@
"name": "vector-database-engineer",
"description": "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vector-index-tuning",
@@ -8043,7 +8936,8 @@
"name": "vector-index-tuning",
"description": "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-automation",
@@ -8052,7 +8946,8 @@
"name": "vercel-automation",
"description": "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-deploy-claimable",
@@ -8061,7 +8956,8 @@
"name": "vercel-deploy-claimable",
"description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...",
"risk": "safe",
- "source": "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
+ "source": "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-deployment",
@@ -8070,7 +8966,8 @@
"name": "vercel-deployment",
"description": "Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.",
"risk": "safe",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "verification-before-completion",
@@ -8079,7 +8976,8 @@
"name": "verification-before-completion",
"description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vexor",
@@ -8088,7 +8986,8 @@
"name": "vexor",
"description": "Vector-powered CLI for semantic file search with a Claude/Codex skill",
"risk": "safe",
- "source": "https://github.com/scarletkc/vexor"
+ "source": "https://github.com/scarletkc/vexor",
+ "date_added": "2025-02-26"
},
{
"id": "viral-generator-builder",
@@ -8097,7 +8996,8 @@
"name": "viral-generator-builder",
"description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-agents",
@@ -8106,7 +9006,8 @@
"name": "voice-agents",
"description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-ai-development",
@@ -8115,7 +9016,8 @@
"name": "voice-ai-development",
"description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-ai-engine-development",
@@ -8124,7 +9026,8 @@
"name": "voice-ai-engine-development",
"description": "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vr-ar",
@@ -8133,7 +9036,8 @@
"name": "vr-ar",
"description": "VR/AR development principles. Comfort, interaction, performance requirements.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vulnerability-scanner",
@@ -8142,7 +9046,8 @@
"name": "vulnerability-scanner",
"description": "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wcag-audit-patterns",
@@ -8151,7 +9056,8 @@
"name": "wcag-audit-patterns",
"description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-artifacts-builder",
@@ -8160,7 +9066,8 @@
"name": "web-artifacts-builder",
"description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-design-guidelines",
@@ -8169,7 +9076,8 @@
"name": "web-design-guidelines",
"description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-games",
@@ -8178,7 +9086,8 @@
"name": "web-games",
"description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-performance-optimization",
@@ -8187,7 +9096,8 @@
"name": "web-performance-optimization",
"description": "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-security-testing",
@@ -8196,7 +9106,8 @@
"name": "web-security-testing",
"description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "web3-testing",
@@ -8205,7 +9116,8 @@
"name": "web3-testing",
"description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "webapp-testing",
@@ -8214,7 +9126,8 @@
"name": "webapp-testing",
"description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "webflow-automation",
@@ -8223,7 +9136,8 @@
"name": "webflow-automation",
"description": "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "whatsapp-automation",
@@ -8232,7 +9146,8 @@
"name": "whatsapp-automation",
"description": "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-architect",
@@ -8241,7 +9156,8 @@
"name": "wiki-architect",
"description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-changelog",
@@ -8250,7 +9166,8 @@
"name": "wiki-changelog",
"description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-onboarding",
@@ -8259,7 +9176,8 @@
"name": "wiki-onboarding",
"description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-page-writer",
@@ -8268,7 +9186,8 @@
"name": "wiki-page-writer",
"description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-qa",
@@ -8277,7 +9196,8 @@
"name": "wiki-qa",
"description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-researcher",
@@ -8286,7 +9206,8 @@
"name": "wiki-researcher",
"description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-vitepress",
@@ -8295,7 +9216,8 @@
"name": "wiki-vitepress",
"description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "windows-privilege-escalation",
@@ -8304,7 +9226,8 @@
"name": "windows-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wireshark-analysis",
@@ -8313,7 +9236,8 @@
"name": "wireshark-analysis",
"description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress",
@@ -8322,7 +9246,8 @@
"name": "wordpress",
"description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-penetration-testing",
@@ -8331,7 +9256,8 @@
"name": "wordpress-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-plugin-development",
@@ -8340,7 +9266,8 @@
"name": "wordpress-plugin-development",
"description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-theme-development",
@@ -8349,7 +9276,8 @@
"name": "wordpress-theme-development",
"description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-woocommerce-development",
@@ -8358,7 +9286,8 @@
"name": "wordpress-woocommerce-development",
"description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-automation",
@@ -8367,7 +9296,8 @@
"name": "workflow-automation",
"description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-orchestration-patterns",
@@ -8376,16 +9306,18 @@
"name": "workflow-orchestration-patterns",
"description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-patterns",
"path": "skills\\workflow-patterns",
"category": "uncategorized",
"name": "workflow-patterns",
- "description": "Use this skill when implementing tasks according to Conductor's TDD\nworkflow, handling phase checkpoints, managing git commits for tasks, or\nunderstanding the verification protocol.\n",
+ "description": "Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wrike-automation",
@@ -8394,7 +9326,8 @@
"name": "wrike-automation",
"description": "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "writer",
@@ -8403,7 +9336,8 @@
"name": "writer",
"description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "writing-plans",
@@ -8412,7 +9346,8 @@
"name": "writing-plans",
"description": "Use when you have a spec or requirements for a multi-step task, before touching code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "writing-skills",
@@ -8421,7 +9356,8 @@
"name": "writing-skills",
"description": "Use when creating, updating, or improving agent skills.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "x-article-publisher-skill",
@@ -8430,7 +9366,8 @@
"name": "x-article-publisher-skill",
"description": "Publish articles to X/Twitter",
"risk": "safe",
- "source": "https://github.com/wshuyi/x-article-publisher-skill"
+ "source": "https://github.com/wshuyi/x-article-publisher-skill",
+ "date_added": "2025-02-26"
},
{
"id": "xlsx-official",
@@ -8439,7 +9376,8 @@
"name": "xlsx-official",
"description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "xss-html-injection",
@@ -8448,7 +9386,8 @@
"name": "xss-html-injection",
"description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "youtube-automation",
@@ -8457,7 +9396,8 @@
"name": "youtube-automation",
"description": "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "youtube-summarizer",
@@ -8466,7 +9406,8 @@
"name": "youtube-summarizer",
"description": "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zapier-make-patterns",
@@ -8475,7 +9416,8 @@
"name": "zapier-make-patterns",
"description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "zendesk-automation",
@@ -8484,7 +9426,8 @@
"name": "zendesk-automation",
"description": "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zoho-crm-automation",
@@ -8493,7 +9436,8 @@
"name": "zoho-crm-automation",
"description": "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zoom-automation",
@@ -8502,7 +9446,8 @@
"name": "zoom-automation",
"description": "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zustand-store-ts",
@@ -8511,6 +9456,7 @@
"name": "zustand-store-ts",
"description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
}
]
\ No newline at end of file
diff --git a/web-app/public/skills.json b/web-app/public/skills.json
index c0ffd8e0..e947d6fd 100644
--- a/web-app/public/skills.json
+++ b/web-app/public/skills.json
@@ -6,7 +6,8 @@
"name": "00-andruia-consultant",
"description": "Arquitecto de Soluciones Principal y Consultor Tecnol\u00f3gico de Andru.ia. Diagnostica y traza la hoja de ruta \u00f3ptima para proyectos de IA en espa\u00f1ol.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "20-andruia-niche-intelligence",
@@ -15,7 +16,8 @@
"name": "20-andruia-niche-intelligence",
"description": "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho espec\u00edfico de un proyecto para inyectar conocimientos, regulaciones y est\u00e1ndares \u00fanicos del sector. Act\u00edvalo tras definir el nicho.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "2d-games",
@@ -24,7 +26,8 @@
"name": "2d-games",
"description": "2D game development principles. Sprites, tilemaps, physics, camera.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "3d-games",
@@ -33,7 +36,8 @@
"name": "3d-games",
"description": "3D game development principles. Rendering, shaders, physics, cameras.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "3d-web-experience",
@@ -42,7 +46,8 @@
"name": "3d-web-experience",
"description": "Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ab-test-setup",
@@ -51,7 +56,8 @@
"name": "ab-test-setup",
"description": "Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "accessibility-compliance-accessibility-audit",
@@ -60,7 +66,8 @@
"name": "accessibility-compliance-accessibility-audit",
"description": "You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "active-directory-attacks",
@@ -69,7 +76,8 @@
"name": "active-directory-attacks",
"description": "This skill should be used when the user asks to \"attack Active Directory\", \"exploit AD\", \"Kerberoasting\", \"DCSync\", \"pass-the-hash\", \"BloodHound enumeration\", \"Golden Ticket\", ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "activecampaign-automation",
@@ -78,7 +86,8 @@
"name": "activecampaign-automation",
"description": "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "address-github-comments",
@@ -87,7 +96,8 @@
"name": "address-github-comments",
"description": "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-evaluation",
@@ -96,7 +106,8 @@
"name": "agent-evaluation",
"description": "Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agent-framework-azure-ai-py",
@@ -105,7 +116,8 @@
"name": "agent-framework-azure-ai-py",
"description": "Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-manager-skill",
@@ -114,7 +126,8 @@
"name": "agent-manager-skill",
"description": "Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-memory-mcp",
@@ -123,7 +136,8 @@
"name": "agent-memory-mcp",
"description": "A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-memory-systems",
@@ -132,7 +146,8 @@
"name": "agent-memory-systems",
"description": "Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agent-orchestration-improve-agent",
@@ -141,7 +156,8 @@
"name": "agent-orchestration-improve-agent",
"description": "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-orchestration-multi-agent-optimize",
@@ -150,7 +166,8 @@
"name": "agent-orchestration-multi-agent-optimize",
"description": "Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "agent-tool-builder",
@@ -159,7 +176,8 @@
"name": "agent-tool-builder",
"description": "Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "agentfolio",
@@ -168,7 +186,8 @@
"name": "agentfolio",
"description": "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory.",
"risk": "unknown",
- "source": "agentfolio.io"
+ "source": "agentfolio.io",
+ "date_added": "2025-02-26"
},
{
"id": "agents-v2-py",
@@ -177,7 +196,8 @@
"name": "agents-v2-py",
"description": "Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ai-agent-development",
@@ -186,7 +206,8 @@
"name": "ai-agent-development",
"description": "AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "ai-agents-architect",
@@ -195,16 +216,18 @@
"name": "ai-agents-architect",
"description": "Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ai-engineer",
"path": "skills\\ai-engineer",
"category": "uncategorized",
"name": "ai-engineer",
- "description": "Build production-ready LLM applications, advanced RAG systems, and\nintelligent agents. Implements vector search, multimodal AI, agent\norchestration, and enterprise AI integrations. Use PROACTIVELY for LLM\nfeatures, chatbots, AI agents, or AI-powered applications.\n",
+ "description": "You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ai-ml",
@@ -213,7 +236,8 @@
"name": "ai-ml",
"description": "AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "ai-product",
@@ -222,7 +246,8 @@
"name": "ai-product",
"description": "Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "ai-wrapper-product",
@@ -231,7 +256,8 @@
"name": "ai-wrapper-product",
"description": "Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "airflow-dag-patterns",
@@ -240,7 +266,8 @@
"name": "airflow-dag-patterns",
"description": "Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "airtable-automation",
@@ -249,7 +276,8 @@
"name": "airtable-automation",
"description": "Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "algolia-search",
@@ -258,7 +286,8 @@
"name": "algolia-search",
"description": "Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "algorithmic-art",
@@ -267,7 +296,8 @@
"name": "algorithmic-art",
"description": "Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "amplitude-automation",
@@ -276,16 +306,18 @@
"name": "amplitude-automation",
"description": "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "analytics-tracking",
"path": "skills\\analytics-tracking",
"category": "uncategorized",
"name": "analytics-tracking",
- "description": "Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation\u2014 not just firing events.\n",
+ "description": "You are an expert in **analytics implementation and measurement design**. Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "android-jetpack-compose-expert",
@@ -294,16 +326,18 @@
"name": "android-jetpack-compose-expert",
"description": "Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "angular",
"path": "skills\\angular",
"category": "uncategorized",
"name": "angular",
- "description": "Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.",
+ "description": "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration, and the latest reactive patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-best-practices",
@@ -312,7 +346,8 @@
"name": "angular-best-practices",
"description": "Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-migration",
@@ -321,7 +356,8 @@
"name": "angular-migration",
"description": "Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "angular-state-management",
@@ -330,7 +366,8 @@
"name": "angular-state-management",
"description": "Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "angular-ui-patterns",
@@ -339,7 +376,8 @@
"name": "angular-ui-patterns",
"description": "Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "anti-reversing-techniques",
@@ -348,7 +386,8 @@
"name": "anti-reversing-techniques",
"description": "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "antigravity-workflows",
@@ -357,7 +396,8 @@
"name": "antigravity-workflows",
"description": "Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.",
"risk": "none",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "api-design-principles",
@@ -366,7 +406,8 @@
"name": "api-design-principles",
"description": "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-documentation",
@@ -375,7 +416,8 @@
"name": "api-documentation",
"description": "API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "api-documentation-generator",
@@ -384,16 +426,18 @@
"name": "api-documentation-generator",
"description": "Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-documenter",
"path": "skills\\api-documenter",
"category": "uncategorized",
"name": "api-documenter",
- "description": "Master API documentation with OpenAPI 3.1, AI-powered tools, and\nmodern developer experience practices. Create interactive docs, generate SDKs,\nand build comprehensive developer portals. Use PROACTIVELY for API\ndocumentation or developer portal creation.\n",
+ "description": "You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-fuzzing-bug-bounty",
@@ -402,7 +446,8 @@
"name": "api-fuzzing-bug-bounty",
"description": "This skill should be used when the user asks to \"test API security\", \"fuzz APIs\", \"find IDOR vulnerabilities\", \"test REST API\", \"test GraphQL\", \"API penetration testing\", \"bug b...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-patterns",
@@ -411,7 +456,8 @@
"name": "api-patterns",
"description": "API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-security-best-practices",
@@ -420,7 +466,8 @@
"name": "api-security-best-practices",
"description": "Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "api-security-testing",
@@ -429,7 +476,8 @@
"name": "api-security-testing",
"description": "API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "api-testing-observability-api-mock",
@@ -438,7 +486,8 @@
"name": "api-testing-observability-api-mock",
"description": "You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "app-builder",
@@ -447,7 +496,8 @@
"name": "app-builder",
"description": "Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "app-store-optimization",
@@ -456,7 +506,8 @@
"name": "app-store-optimization",
"description": "Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "appdeploy",
@@ -465,7 +516,8 @@
"name": "appdeploy",
"description": "Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.",
"risk": "safe",
- "source": "AppDeploy (MIT)"
+ "source": "AppDeploy (MIT)",
+ "date_added": "2025-02-26"
},
{
"id": "application-performance-performance-optimization",
@@ -474,16 +526,18 @@
"name": "application-performance-performance-optimization",
"description": "Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architect-review",
"path": "skills\\architect-review",
"category": "uncategorized",
"name": "architect-review",
- "description": "Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.",
+ "description": "Master software architect specializing in modern architecture",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture",
@@ -492,7 +546,8 @@
"name": "architecture",
"description": "Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture-decision-records",
@@ -501,7 +556,8 @@
"name": "architecture-decision-records",
"description": "Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "architecture-patterns",
@@ -510,16 +566,18 @@
"name": "architecture-patterns",
"description": "Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "arm-cortex-expert",
"path": "skills\\arm-cortex-expert",
"category": "uncategorized",
"name": "arm-cortex-expert",
- "description": "Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.\n",
+ "description": "- Working on @arm-cortex-expert tasks or workflows - Needing guidance, best practices, or checklists for @arm-cortex-expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "asana-automation",
@@ -528,7 +586,8 @@
"name": "asana-automation",
"description": "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "async-python-patterns",
@@ -537,7 +596,8 @@
"name": "async-python-patterns",
"description": "Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "attack-tree-construction",
@@ -546,7 +606,8 @@
"name": "attack-tree-construction",
"description": "Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "audio-transcriber",
@@ -555,7 +616,8 @@
"name": "audio-transcriber",
"description": "Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "auth-implementation-patterns",
@@ -564,7 +626,8 @@
"name": "auth-implementation-patterns",
"description": "Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing A...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "automate-whatsapp",
@@ -573,7 +636,8 @@
"name": "automate-whatsapp",
"description": "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...",
"risk": "safe",
- "source": "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp"
+ "source": "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp",
+ "date_added": "2025-02-26"
},
{
"id": "autonomous-agent-patterns",
@@ -582,7 +646,8 @@
"name": "autonomous-agent-patterns",
"description": "Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "autonomous-agents",
@@ -591,7 +656,8 @@
"name": "autonomous-agents",
"description": "Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it'...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-layout-zafiro",
@@ -600,7 +666,8 @@
"name": "avalonia-layout-zafiro",
"description": "Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-viewmodels-zafiro",
@@ -609,7 +676,8 @@
"name": "avalonia-viewmodels-zafiro",
"description": "Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "avalonia-zafiro-development",
@@ -618,7 +686,8 @@
"name": "avalonia-zafiro-development",
"description": "Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-compliance-checker",
@@ -627,7 +696,8 @@
"name": "aws-compliance-checker",
"description": "Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-cost-cleanup",
@@ -636,7 +706,8 @@
"name": "aws-cost-cleanup",
"description": "Automated cleanup of unused AWS resources to reduce costs",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-cost-optimizer",
@@ -645,7 +716,8 @@
"name": "aws-cost-optimizer",
"description": "Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-iam-best-practices",
@@ -654,7 +726,8 @@
"name": "aws-iam-best-practices",
"description": "IAM policy review, hardening, and least privilege implementation",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-penetration-testing",
@@ -663,7 +736,8 @@
"name": "aws-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest AWS\", \"test AWS security\", \"enumerate IAM\", \"exploit cloud infrastructure\", \"AWS privilege escalation\", \"S3 bucket testing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-secrets-rotation",
@@ -672,7 +746,8 @@
"name": "aws-secrets-rotation",
"description": "Automate AWS secrets rotation for RDS, API keys, and credentials",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-security-audit",
@@ -681,7 +756,8 @@
"name": "aws-security-audit",
"description": "Comprehensive AWS security posture assessment using AWS CLI and security best practices",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "aws-serverless",
@@ -690,7 +766,8 @@
"name": "aws-serverless",
"description": "Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start opt...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "aws-skills",
@@ -699,7 +776,8 @@
"name": "aws-skills",
"description": "AWS development with infrastructure automation and cloud architecture patterns",
"risk": "safe",
- "source": "https://github.com/zxkane/aws-skills"
+ "source": "https://github.com/zxkane/aws-skills",
+ "date_added": "2025-02-26"
},
{
"id": "azd-deployment",
@@ -708,25 +786,28 @@
"name": "azd-deployment",
"description": "Deploy containerized applications to Azure Container Apps using Azure Developer CLI (azd). Use when setting up azd projects, writing azure.yaml configuration, creating Bicep infrastructure for Cont...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-agents-persistent-dotnet",
"path": "skills\\azure-ai-agents-persistent-dotnet",
"category": "uncategorized",
"name": "azure-ai-agents-persistent-dotnet",
- "description": "Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: \"PersistentAgentsClient\", \"persistent agents\", \"agent threads\", \"agent runs\", \"streaming agents\", \"function calling agents .NET\".\n",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-agents-persistent-java",
"path": "skills\\azure-ai-agents-persistent-java",
"category": "uncategorized",
"name": "azure-ai-agents-persistent-java",
- "description": "Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.\nTriggers: \"PersistentAgentsClient\", \"persistent agents java\", \"agent threads java\", \"agent runs java\", \"streaming agents java\".\n",
+ "description": "Low-level SDK for creating and managing persistent AI agents with threads, messages, runs, and tools.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-anomalydetector-java",
@@ -735,7 +816,8 @@
"name": "azure-ai-anomalydetector-java",
"description": "Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-java",
@@ -744,16 +826,18 @@
"name": "azure-ai-contentsafety-java",
"description": "Build content moderation applications with Azure AI Content Safety SDK for Java. Use when implementing text/image analysis, blocklist management, or harm detection for hate, violence, sexual conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-py",
"path": "skills\\azure-ai-contentsafety-py",
"category": "uncategorized",
"name": "azure-ai-contentsafety-py",
- "description": "Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.\nTriggers: \"azure-ai-contentsafety\", \"ContentSafetyClient\", \"content moderation\", \"harmful content\", \"text analysis\", \"image analysis\".\n",
+ "description": "Detect harmful user-generated and AI-generated content in applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentsafety-ts",
@@ -762,25 +846,28 @@
"name": "azure-ai-contentsafety-ts",
"description": "Analyze text and images for harmful content using Azure AI Content Safety (@azure-rest/ai-content-safety). Use when moderating user-generated content, detecting hate speech, violence, sexual conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-contentunderstanding-py",
"path": "skills\\azure-ai-contentunderstanding-py",
"category": "uncategorized",
"name": "azure-ai-contentunderstanding-py",
- "description": "Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.\nTriggers: \"azure-ai-contentunderstanding\", \"ContentUnderstandingClient\", \"multimodal analysis\", \"document extraction\", \"video analysis\", \"audio transcription\".\n",
+ "description": "Multimodal AI service that extracts semantic content from documents, video, audio, and image files for RAG and automated workflows.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-document-intelligence-dotnet",
"path": "skills\\azure-ai-document-intelligence-dotnet",
"category": "uncategorized",
"name": "azure-ai-document-intelligence-dotnet",
- "description": "Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: \"Document Intelligence\", \"DocumentIntelligenceClient\", \"form recognizer\", \"invoice extraction\", \"receipt OCR\", \"document analysis .NET\".\n",
+ "description": "Extract text, tables, and structured data from documents using prebuilt and custom models.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-document-intelligence-ts",
@@ -789,7 +876,8 @@
"name": "azure-ai-document-intelligence-ts",
"description": "Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-formrecognizer-java",
@@ -798,43 +886,48 @@
"name": "azure-ai-formrecognizer-java",
"description": "Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-ml-py",
"path": "skills\\azure-ai-ml-py",
"category": "uncategorized",
"name": "azure-ai-ml-py",
- "description": "Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.\nTriggers: \"azure-ai-ml\", \"MLClient\", \"workspace\", \"model registry\", \"training jobs\", \"datasets\".\n",
+ "description": "Client library for managing Azure ML resources: workspaces, jobs, models, data, and compute.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-openai-dotnet",
"path": "skills\\azure-ai-openai-dotnet",
"category": "uncategorized",
"name": "azure-ai-openai-dotnet",
- "description": "Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: \"Azure OpenAI\", \"AzureOpenAIClient\", \"ChatClient\", \"chat completions .NET\", \"GPT-4\", \"embeddings\", \"DALL-E\", \"Whisper\", \"OpenAI .NET\".\n",
+ "description": "Client library for Azure OpenAI Service providing access to OpenAI models including GPT-4, GPT-4o, embeddings, DALL-E, and Whisper.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-dotnet",
"path": "skills\\azure-ai-projects-dotnet",
"category": "uncategorized",
"name": "azure-ai-projects-dotnet",
- "description": "Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: \"AI Projects\", \"AIProjectClient\", \"Foundry project\", \"versioned agents\", \"evaluations\", \"datasets\", \"connections\", \"deployments .NET\".\n",
+ "description": "High-level SDK for Azure AI Foundry project operations including agents, connections, datasets, deployments, evaluations, and indexes.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-java",
"path": "skills\\azure-ai-projects-java",
"category": "uncategorized",
"name": "azure-ai-projects-java",
- "description": "Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.\nTriggers: \"AIProjectClient java\", \"azure ai projects java\", \"Foundry project java\", \"ConnectionsClient\", \"DatasetsClient\", \"IndexesClient\".\n",
+ "description": "High-level SDK for Azure AI Foundry project management with access to connections, datasets, indexes, and evaluations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-py",
@@ -843,7 +936,8 @@
"name": "azure-ai-projects-py",
"description": "Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evalua...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-projects-ts",
@@ -852,43 +946,48 @@
"name": "azure-ai-projects-ts",
"description": "Build AI applications using Azure AI Projects SDK for JavaScript (@azure/ai-projects). Use when working with Foundry project clients, agents, connections, deployments, datasets, indexes, evaluation...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-textanalytics-py",
"path": "skills\\azure-ai-textanalytics-py",
"category": "uncategorized",
"name": "azure-ai-textanalytics-py",
- "description": "Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.\nTriggers: \"text analytics\", \"sentiment analysis\", \"entity recognition\", \"key phrase\", \"PII detection\", \"TextAnalyticsClient\".\n",
+ "description": "Client library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-transcription-py",
"path": "skills\\azure-ai-transcription-py",
"category": "uncategorized",
"name": "azure-ai-transcription-py",
- "description": "Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.\nTriggers: \"transcription\", \"speech to text\", \"Azure AI Transcription\", \"TranscriptionClient\".\n",
+ "description": "Client library for Azure AI Transcription (speech-to-text) with real-time and batch transcription.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-document-py",
"path": "skills\\azure-ai-translation-document-py",
"category": "uncategorized",
"name": "azure-ai-translation-document-py",
- "description": "Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.\nTriggers: \"document translation\", \"batch translation\", \"translate documents\", \"DocumentTranslationClient\".\n",
+ "description": "Client library for Azure AI Translator document translation service for batch document translation with format preservation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-text-py",
"path": "skills\\azure-ai-translation-text-py",
"category": "uncategorized",
"name": "azure-ai-translation-text-py",
- "description": "Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.\nTriggers: \"text translation\", \"translator\", \"translate text\", \"transliterate\", \"TextTranslationClient\".\n",
+ "description": "Client library for Azure AI Translator text translation service for real-time text translation, transliteration, and language operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-translation-ts",
@@ -897,7 +996,8 @@
"name": "azure-ai-translation-ts",
"description": "Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-vision-imageanalysis-java",
@@ -906,34 +1006,38 @@
"name": "azure-ai-vision-imageanalysis-java",
"description": "Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-vision-imageanalysis-py",
"path": "skills\\azure-ai-vision-imageanalysis-py",
"category": "uncategorized",
"name": "azure-ai-vision-imageanalysis-py",
- "description": "Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.\nTriggers: \"image analysis\", \"computer vision\", \"OCR\", \"object detection\", \"ImageAnalysisClient\", \"image caption\".\n",
+ "description": "Client library for Azure AI Vision 4.0 image analysis including captions, tags, objects, OCR, and more.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-dotnet",
"path": "skills\\azure-ai-voicelive-dotnet",
"category": "uncategorized",
"name": "azure-ai-voicelive-dotnet",
- "description": "Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant .NET\", \"bidirectional audio\", \"speech-to-speech\".\n",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-java",
"path": "skills\\azure-ai-voicelive-java",
"category": "uncategorized",
"name": "azure-ai-voicelive-java",
- "description": "Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.\nTriggers: \"VoiceLiveClient java\", \"voice assistant java\", \"real-time voice java\", \"audio streaming java\", \"voice activity detection java\".\n",
+ "description": "Real-time, bidirectional voice conversations with AI assistants using WebSocket technology.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-py",
@@ -942,34 +1046,38 @@
"name": "azure-ai-voicelive-py",
"description": "Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-ai-voicelive-ts",
"path": "skills\\azure-ai-voicelive-ts",
"category": "uncategorized",
"name": "azure-ai-voicelive-ts",
- "description": "Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: \"voice live\", \"real-time voice\", \"VoiceLiveClient\", \"VoiceLiveSession\", \"voice assistant TypeScript\", \"bidirectional audio\", \"speech-to-speech JavaScript\".\n",
+ "description": "Real-time voice AI SDK for building bidirectional voice assistants with Azure AI in Node.js and browser environments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-java",
"path": "skills\\azure-appconfiguration-java",
"category": "uncategorized",
"name": "azure-appconfiguration-java",
- "description": "Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.\nTriggers: \"ConfigurationClient java\", \"app configuration java\", \"feature flag java\", \"configuration setting java\", \"azure config java\".\n",
+ "description": "Client library for Azure App Configuration, a managed service for centralizing application configurations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-py",
"path": "skills\\azure-appconfiguration-py",
"category": "uncategorized",
"name": "azure-appconfiguration-py",
- "description": "Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.\nTriggers: \"azure-appconfiguration\", \"AzureAppConfigurationClient\", \"feature flags\", \"configuration\", \"key-value settings\".\n",
+ "description": "Centralized configuration management with feature flags and dynamic settings.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-appconfiguration-ts",
@@ -978,7 +1086,8 @@
"name": "azure-appconfiguration-ts",
"description": "Build applications using Azure App Configuration SDK for JavaScript (@azure/app-configuration). Use when working with configuration settings, feature flags, Key Vault references, dynamic refresh, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-callautomation-java",
@@ -987,7 +1096,8 @@
"name": "azure-communication-callautomation-java",
"description": "Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-callingserver-java",
@@ -996,7 +1106,8 @@
"name": "azure-communication-callingserver-java",
"description": "Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-chat-java",
@@ -1005,7 +1116,8 @@
"name": "azure-communication-chat-java",
"description": "Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-common-java",
@@ -1014,7 +1126,8 @@
"name": "azure-communication-common-java",
"description": "Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-communication-sms-java",
@@ -1023,25 +1136,28 @@
"name": "azure-communication-sms-java",
"description": "Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-compute-batch-java",
"path": "skills\\azure-compute-batch-java",
"category": "uncategorized",
"name": "azure-compute-batch-java",
- "description": "Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.\nTriggers: \"BatchClient java\", \"azure batch java\", \"batch pool java\", \"batch job java\", \"HPC java\", \"parallel computing java\".\n",
+ "description": "Client library for running large-scale parallel and high-performance computing (HPC) batch jobs in Azure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-containerregistry-py",
"path": "skills\\azure-containerregistry-py",
"category": "uncategorized",
"name": "azure-containerregistry-py",
- "description": "Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.\nTriggers: \"azure-containerregistry\", \"ContainerRegistryClient\", \"container images\", \"docker registry\", \"ACR\".\n",
+ "description": "Manage container images, artifacts, and repositories in Azure Container Registry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-db-py",
@@ -1050,43 +1166,48 @@
"name": "azure-cosmos-db-py",
"description": "Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-java",
"path": "skills\\azure-cosmos-java",
"category": "uncategorized",
"name": "azure-cosmos-java",
- "description": "Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.\nTriggers: \"CosmosClient java\", \"CosmosAsyncClient\", \"cosmos database java\", \"cosmosdb java\", \"document database java\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API with global distribution and reactive patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-py",
"path": "skills\\azure-cosmos-py",
"category": "uncategorized",
"name": "azure-cosmos-py",
- "description": "Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db\", \"CosmosClient\", \"container\", \"document\", \"NoSQL\", \"partition key\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-rust",
"path": "skills\\azure-cosmos-rust",
"category": "uncategorized",
"name": "azure-cosmos-rust",
- "description": "Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.\nTriggers: \"cosmos db rust\", \"CosmosClient rust\", \"container\", \"document rust\", \"NoSQL rust\", \"partition key\".\n",
+ "description": "Client library for Azure Cosmos DB NoSQL API \u2014 globally distributed, multi-model database.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-cosmos-ts",
"path": "skills\\azure-cosmos-ts",
"category": "uncategorized",
"name": "azure-cosmos-ts",
- "description": "Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: \"Cosmos DB\", \"@azure/cosmos\", \"CosmosClient\", \"document CRUD\", \"NoSQL queries\", \"bulk operations\", \"partition key\", \"container.items\".\n",
+ "description": "Data plane SDK for Azure Cosmos DB NoSQL API operations \u2014 CRUD on documents, queries, bulk operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-data-tables-java",
@@ -1095,25 +1216,28 @@
"name": "azure-data-tables-java",
"description": "Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-data-tables-py",
"path": "skills\\azure-data-tables-py",
"category": "uncategorized",
"name": "azure-data-tables-py",
- "description": "Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.\nTriggers: \"table storage\", \"TableServiceClient\", \"TableClient\", \"entities\", \"PartitionKey\", \"RowKey\".\n",
+ "description": "NoSQL key-value store for structured data (Azure Storage Tables or Cosmos DB Table API).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-dotnet",
"path": "skills\\azure-eventgrid-dotnet",
"category": "uncategorized",
"name": "azure-eventgrid-dotnet",
- "description": "Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: \"Event Grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events .NET\", \"event-driven\", \"pub/sub\".\n",
+ "description": "Client library for publishing events to Azure Event Grid topics, domains, and namespaces.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-java",
@@ -1122,25 +1246,28 @@
"name": "azure-eventgrid-java",
"description": "Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventgrid-py",
"path": "skills\\azure-eventgrid-py",
"category": "uncategorized",
"name": "azure-eventgrid-py",
- "description": "Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.\nTriggers: \"event grid\", \"EventGridPublisherClient\", \"CloudEvent\", \"EventGridEvent\", \"publish events\".\n",
+ "description": "Event routing service for building event-driven applications with pub/sub semantics.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-dotnet",
"path": "skills\\azure-eventhub-dotnet",
"category": "uncategorized",
"name": "azure-eventhub-dotnet",
- "description": "Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: \"Event Hubs\", \"event streaming\", \"EventHubProducerClient\", \"EventProcessorClient\", \"send events\", \"receive events\", \"checkpointing\", \"partition\".\n",
+ "description": "High-throughput event streaming SDK for sending and receiving events via Azure Event Hubs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-java",
@@ -1149,25 +1276,28 @@
"name": "azure-eventhub-java",
"description": "Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-py",
"path": "skills\\azure-eventhub-py",
"category": "uncategorized",
"name": "azure-eventhub-py",
- "description": "Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.\nTriggers: \"event hubs\", \"EventHubProducerClient\", \"EventHubConsumerClient\", \"streaming\", \"partitions\".\n",
+ "description": "Big data streaming platform for high-throughput event ingestion.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-rust",
"path": "skills\\azure-eventhub-rust",
"category": "uncategorized",
"name": "azure-eventhub-rust",
- "description": "Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.\nTriggers: \"event hubs rust\", \"ProducerClient rust\", \"ConsumerClient rust\", \"send event rust\", \"streaming rust\".\n",
+ "description": "Client library for Azure Event Hubs \u2014 big data streaming platform and event ingestion service.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-eventhub-ts",
@@ -1176,7 +1306,8 @@
"name": "azure-eventhub-ts",
"description": "Build event streaming applications using Azure Event Hubs SDK for JavaScript (@azure/event-hubs). Use when implementing high-throughput event ingestion, real-time analytics, IoT telemetry, or event...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-functions",
@@ -1185,16 +1316,18 @@
"name": "azure-functions",
"description": "Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-dotnet",
"path": "skills\\azure-identity-dotnet",
"category": "uncategorized",
"name": "azure-identity-dotnet",
- "description": "Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: \"Azure Identity\", \"DefaultAzureCredential\", \"ManagedIdentityCredential\", \"ClientSecretCredential\", \"authentication .NET\", \"Azure auth\", \"credential chain\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-java",
@@ -1203,25 +1336,28 @@
"name": "azure-identity-java",
"description": "Azure Identity Java SDK for authentication with Azure services. Use when implementing DefaultAzureCredential, managed identity, service principal, or any Azure authentication pattern in Java applic...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-py",
"path": "skills\\azure-identity-py",
"category": "uncategorized",
"name": "azure-identity-py",
- "description": "Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.\nTriggers: \"azure-identity\", \"DefaultAzureCredential\", \"authentication\", \"managed identity\", \"service principal\", \"credential\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-rust",
"path": "skills\\azure-identity-rust",
"category": "uncategorized",
"name": "azure-identity-rust",
- "description": "Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.\nTriggers: \"azure-identity\", \"DeveloperToolsCredential\", \"authentication rust\", \"managed identity rust\", \"credential rust\".\n",
+ "description": "Authentication library for Azure SDK clients using Microsoft Entra ID (formerly Azure AD).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-identity-ts",
@@ -1230,25 +1366,28 @@
"name": "azure-identity-ts",
"description": "Authenticate to Azure services using Azure Identity SDK for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or i...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-certificates-rust",
"path": "skills\\azure-keyvault-certificates-rust",
"category": "uncategorized",
"name": "azure-keyvault-certificates-rust",
- "description": "Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.\nTriggers: \"keyvault certificates rust\", \"CertificateClient rust\", \"create certificate rust\", \"import certificate rust\".\n",
+ "description": "Client library for Azure Key Vault Certificates \u2014 secure storage and management of certificates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-keys-rust",
"path": "skills\\azure-keyvault-keys-rust",
"category": "uncategorized",
"name": "azure-keyvault-keys-rust",
- "description": "Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.\nTriggers: \"keyvault keys rust\", \"KeyClient rust\", \"create key rust\", \"encrypt rust\", \"sign rust\".\n",
+ "description": "Client library for Azure Key Vault Keys \u2014 secure storage and management of cryptographic keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-keys-ts",
@@ -1257,25 +1396,28 @@
"name": "azure-keyvault-keys-ts",
"description": "Manage cryptographic keys using Azure Key Vault Keys SDK for JavaScript (@azure/keyvault-keys). Use when creating, encrypting/decrypting, signing, or rotating keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-py",
"path": "skills\\azure-keyvault-py",
"category": "uncategorized",
"name": "azure-keyvault-py",
- "description": "Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.\nTriggers: \"key vault\", \"SecretClient\", \"KeyClient\", \"CertificateClient\", \"secrets\", \"encryption keys\".\n",
+ "description": "Secure storage and management for secrets, cryptographic keys, and certificates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-secrets-rust",
"path": "skills\\azure-keyvault-secrets-rust",
"category": "uncategorized",
"name": "azure-keyvault-secrets-rust",
- "description": "Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.\nTriggers: \"keyvault secrets rust\", \"SecretClient rust\", \"get secret rust\", \"set secret rust\".\n",
+ "description": "Client library for Azure Key Vault Secrets \u2014 secure storage for passwords, API keys, and other secrets.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-keyvault-secrets-ts",
@@ -1284,16 +1426,18 @@
"name": "azure-keyvault-secrets-ts",
"description": "Manage secrets using Azure Key Vault Secrets SDK for JavaScript (@azure/keyvault-secrets). Use when storing and retrieving application secrets or configuration values.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-maps-search-dotnet",
"path": "skills\\azure-maps-search-dotnet",
"category": "uncategorized",
"name": "azure-maps-search-dotnet",
- "description": "Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: \"Azure Maps\", \"MapsSearchClient\", \"MapsRoutingClient\", \"MapsRenderingClient\", \"geocoding .NET\", \"route directions\", \"map tiles\", \"geolocation\".\n",
+ "description": "Azure Maps SDK for .NET providing location-based services: geocoding, routing, rendering, geolocation, and weather.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-messaging-webpubsub-java",
@@ -1302,106 +1446,118 @@
"name": "azure-messaging-webpubsub-java",
"description": "Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-messaging-webpubsubservice-py",
"path": "skills\\azure-messaging-webpubsubservice-py",
"category": "uncategorized",
"name": "azure-messaging-webpubsubservice-py",
- "description": "Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.\nTriggers: \"azure-messaging-webpubsubservice\", \"WebPubSubServiceClient\", \"real-time\", \"WebSocket\", \"pub/sub\".\n",
+ "description": "Real-time messaging with WebSocket connections at scale.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apicenter-dotnet",
"path": "skills\\azure-mgmt-apicenter-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-apicenter-dotnet",
- "description": "Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: \"API Center\", \"ApiCenterService\", \"ApiCenterWorkspace\", \"ApiCenterApi\", \"API inventory\", \"API governance\", \"API versioning\", \"API catalog\", \"API discovery\".\n",
+ "description": "Centralized API inventory and governance SDK for managing APIs across your organization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apicenter-py",
"path": "skills\\azure-mgmt-apicenter-py",
"category": "uncategorized",
"name": "azure-mgmt-apicenter-py",
- "description": "Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.\nTriggers: \"azure-mgmt-apicenter\", \"ApiCenterMgmtClient\", \"API Center\", \"API inventory\", \"API governance\".\n",
+ "description": "Manage API inventory, metadata, and governance in Azure API Center.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apimanagement-dotnet",
"path": "skills\\azure-mgmt-apimanagement-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-apimanagement-dotnet",
- "description": "Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: \"API Management\", \"APIM service\", \"create APIM\", \"manage APIs\", \"ApiManagementServiceResource\", \"API policies\", \"APIM products\", \"APIM subscriptions\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure API Management resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-apimanagement-py",
"path": "skills\\azure-mgmt-apimanagement-py",
"category": "uncategorized",
"name": "azure-mgmt-apimanagement-py",
- "description": "Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.\nTriggers: \"azure-mgmt-apimanagement\", \"ApiManagementClient\", \"APIM\", \"API gateway\", \"API Management\".\n",
+ "description": "Manage Azure API Management services, APIs, products, and policies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-applicationinsights-dotnet",
"path": "skills\\azure-mgmt-applicationinsights-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-applicationinsights-dotnet",
- "description": "Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: \"Application Insights\", \"ApplicationInsights\", \"App Insights\", \"APM\", \"application monitoring\", \"web tests\", \"availability tests\", \"workbooks\".\n",
+ "description": "Azure Resource Manager SDK for managing Application Insights resources for application performance monitoring.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-arizeaiobservabilityeval-dotnet",
"path": "skills\\azure-mgmt-arizeaiobservabilityeval-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-arizeaiobservabilityeval-dotnet",
- "description": "Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations \non Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability \ninto .NET applications. Triggers: \"Arize AI\", \"ML observability\", \"ArizeAIObservabilityEval\", \"Arize organization\".\n",
+ "description": ".NET SDK for managing Arize AI Observability and Evaluation resources on Azure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-botservice-dotnet",
"path": "skills\\azure-mgmt-botservice-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-botservice-dotnet",
- "description": "Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: \"Bot Service\", \"BotResource\", \"Azure Bot\", \"DirectLine channel\", \"Teams channel\", \"bot management .NET\", \"create bot\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Bot Service resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-botservice-py",
"path": "skills\\azure-mgmt-botservice-py",
"category": "uncategorized",
"name": "azure-mgmt-botservice-py",
- "description": "Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.\nTriggers: \"azure-mgmt-botservice\", \"AzureBotService\", \"bot management\", \"conversational AI\", \"bot channels\".\n",
+ "description": "Manage Azure Bot Service resources including bots, channels, and connections.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-fabric-dotnet",
"path": "skills\\azure-mgmt-fabric-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-fabric-dotnet",
- "description": "Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: \"Fabric capacity\", \"create capacity\", \"suspend capacity\", \"resume capacity\", \"Fabric SKU\", \"provision Fabric\", \"ARM Fabric\", \"FabricCapacityResource\".\n",
+ "description": "Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-fabric-py",
"path": "skills\\azure-mgmt-fabric-py",
"category": "uncategorized",
"name": "azure-mgmt-fabric-py",
- "description": "Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.\nTriggers: \"azure-mgmt-fabric\", \"FabricMgmtClient\", \"Fabric capacity\", \"Microsoft Fabric\", \"Power BI capacity\".\n",
+ "description": "Manage Microsoft Fabric capacities and resources programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-mongodbatlas-dotnet",
@@ -1410,16 +1566,18 @@
"name": "azure-mgmt-mongodbatlas-dotnet",
"description": "Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure M...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-mgmt-weightsandbiases-dotnet",
"path": "skills\\azure-mgmt-weightsandbiases-dotnet",
"category": "uncategorized",
"name": "azure-mgmt-weightsandbiases-dotnet",
- "description": "Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: \"Weights and Biases\", \"W&B\", \"WeightsAndBiases\", \"ML experiment tracking\", \"model registry\", \"experiment management\", \"wandb\".\n",
+ "description": "Azure Resource Manager SDK for deploying and managing Weights & Biases ML experiment tracking instances via Azure Marketplace.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-microsoft-playwright-testing-ts",
@@ -1428,52 +1586,58 @@
"name": "azure-microsoft-playwright-testing-ts",
"description": "Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-ingestion-java",
"path": "skills\\azure-monitor-ingestion-java",
"category": "uncategorized",
"name": "azure-monitor-ingestion-java",
- "description": "Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).\nTriggers: \"LogsIngestionClient java\", \"azure monitor ingestion java\", \"custom logs java\", \"DCR java\", \"data collection rule java\".\n",
+ "description": "Client library for sending custom logs to Azure Monitor using the Logs Ingestion API via Data Collection Rules.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-ingestion-py",
"path": "skills\\azure-monitor-ingestion-py",
"category": "uncategorized",
"name": "azure-monitor-ingestion-py",
- "description": "Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.\nTriggers: \"azure-monitor-ingestion\", \"LogsIngestionClient\", \"custom logs\", \"DCR\", \"data collection rule\", \"Log Analytics\".\n",
+ "description": "Send custom logs to Azure Monitor Log Analytics workspace using the Logs Ingestion API.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-exporter-java",
"path": "skills\\azure-monitor-opentelemetry-exporter-java",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-exporter-java",
- "description": "Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.\nTriggers: \"AzureMonitorExporter java\", \"opentelemetry azure java\", \"application insights java otel\", \"azure monitor tracing java\".\nNote: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.\n",
+ "description": "> **\u26a0\ufe0f DEPRECATION NOTICE**: This package is deprecated. Migrate to `azure-monitor-opentelemetry-autoconfigure`. > > See [Migration Guide](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/MIGRATIO",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-exporter-py",
"path": "skills\\azure-monitor-opentelemetry-exporter-py",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-exporter-py",
- "description": "Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.\nTriggers: \"azure-monitor-opentelemetry-exporter\", \"AzureMonitorTraceExporter\", \"AzureMonitorMetricExporter\", \"AzureMonitorLogExporter\".\n",
+ "description": "Low-level exporter for sending OpenTelemetry traces, metrics, and logs to Application Insights.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-py",
"path": "skills\\azure-monitor-opentelemetry-py",
"category": "uncategorized",
"name": "azure-monitor-opentelemetry-py",
- "description": "Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.\nTriggers: \"azure-monitor-opentelemetry\", \"configure_azure_monitor\", \"Application Insights\", \"OpenTelemetry distro\", \"auto-instrumentation\".\n",
+ "description": "One-line setup for Application Insights with OpenTelemetry auto-instrumentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-opentelemetry-ts",
@@ -1482,115 +1646,128 @@
"name": "azure-monitor-opentelemetry-ts",
"description": "Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry). Use when adding distributed tracing, metrics, and logs to Node.js applications with Appli...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-query-java",
"path": "skills\\azure-monitor-query-java",
"category": "uncategorized",
"name": "azure-monitor-query-java",
- "description": "Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.\nTriggers: \"LogsQueryClient java\", \"MetricsQueryClient java\", \"kusto query java\", \"log analytics java\", \"azure monitor query java\".\nNote: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.\n",
+ "description": "> **DEPRECATION NOTICE**: This package is deprecated in favor of: > - `azure-monitor-query-logs` \u2014 For Log Analytics queries > - `azure-monitor-query-metrics` \u2014 For metrics queries > > See migration guides: [Logs Migration](https://github.com/Azure/a",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-monitor-query-py",
"path": "skills\\azure-monitor-query-py",
"category": "uncategorized",
"name": "azure-monitor-query-py",
- "description": "Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.\nTriggers: \"azure-monitor-query\", \"LogsQueryClient\", \"MetricsQueryClient\", \"Log Analytics\", \"Kusto queries\", \"Azure metrics\".\n",
+ "description": "Query logs and metrics from Azure Monitor and Log Analytics workspaces.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-postgres-ts",
"path": "skills\\azure-postgres-ts",
"category": "uncategorized",
"name": "azure-postgres-ts",
- "description": "Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: \"PostgreSQL\", \"postgres\", \"pg client\", \"node-postgres\", \"Azure PostgreSQL connection\", \"PostgreSQL TypeScript\", \"pg Pool\", \"passwordless postgres\".\n",
+ "description": "Connect to Azure Database for PostgreSQL Flexible Server using the `pg` (node-postgres) package with support for password and Microsoft Entra ID (passwordless) authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-cosmosdb-dotnet",
"path": "skills\\azure-resource-manager-cosmosdb-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-cosmosdb-dotnet",
- "description": "Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: \"Cosmos DB account\", \"create Cosmos account\", \"manage Cosmos resources\", \"ARM Cosmos\", \"CosmosDBAccountResource\", \"provision Cosmos DB\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Cosmos DB resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-durabletask-dotnet",
"path": "skills\\azure-resource-manager-durabletask-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-durabletask-dotnet",
- "description": "Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: \"Durable Task Scheduler\", \"create scheduler\", \"task hub\", \"DurableTaskSchedulerResource\", \"provision Durable Task\", \"orchestration scheduler\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Durable Task Scheduler resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-mysql-dotnet",
"path": "skills\\azure-resource-manager-mysql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-mysql-dotnet",
- "description": "Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"MySQL\", \"MySqlFlexibleServer\", \"MySQL Flexible Server\", \"Azure Database for MySQL\", \"MySQL database management\", \"MySQL firewall\", \"MySQL backup\".\n",
+ "description": "Azure Resource Manager SDK for managing MySQL Flexible Server deployments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-playwright-dotnet",
"path": "skills\\azure-resource-manager-playwright-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-playwright-dotnet",
- "description": "Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: \"Playwright workspace\", \"create Playwright Testing workspace\", \"manage Playwright resources\", \"ARM Playwright\", \"PlaywrightWorkspaceResource\", \"provision Playwright Testing\".\n",
+ "description": "Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-postgresql-dotnet",
"path": "skills\\azure-resource-manager-postgresql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-postgresql-dotnet",
- "description": "Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: \"PostgreSQL\", \"PostgreSqlFlexibleServer\", \"PostgreSQL Flexible Server\", \"Azure Database for PostgreSQL\", \"PostgreSQL database management\", \"PostgreSQL firewall\", \"PostgreSQL backup\", \"Postgres\".\n",
+ "description": "Azure Resource Manager SDK for managing PostgreSQL Flexible Server deployments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-redis-dotnet",
"path": "skills\\azure-resource-manager-redis-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-redis-dotnet",
- "description": "Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: \"Redis cache\", \"create Redis\", \"manage Redis\", \"ARM Redis\", \"RedisResource\", \"provision Redis\", \"Azure Cache for Redis\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure Cache for Redis resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-resource-manager-sql-dotnet",
"path": "skills\\azure-resource-manager-sql-dotnet",
"category": "uncategorized",
"name": "azure-resource-manager-sql-dotnet",
- "description": "Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: \"SQL server\", \"create SQL database\", \"manage SQL resources\", \"ARM SQL\", \"SqlServerResource\", \"provision Azure SQL\", \"elastic pool\", \"firewall rule\".\n",
+ "description": "Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-dotnet",
"path": "skills\\azure-search-documents-dotnet",
"category": "uncategorized",
"name": "azure-search-documents-dotnet",
- "description": "Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: \"Azure Search .NET\", \"SearchClient\", \"SearchIndexClient\", \"vector search C#\", \"semantic search .NET\", \"hybrid search\", \"Azure.Search.Documents\".\n",
+ "description": "Build search applications with full-text, vector, semantic, and hybrid search capabilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-py",
"path": "skills\\azure-search-documents-py",
"category": "uncategorized",
"name": "azure-search-documents-py",
- "description": "Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.\nTriggers: \"azure-search-documents\", \"SearchClient\", \"SearchIndexClient\", \"vector search\", \"hybrid search\", \"semantic search\".\n",
+ "description": "Full-text, vector, and hybrid search with AI enrichment capabilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-search-documents-ts",
@@ -1599,16 +1776,18 @@
"name": "azure-search-documents-ts",
"description": "Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-keys-dotnet",
"path": "skills\\azure-security-keyvault-keys-dotnet",
"category": "uncategorized",
"name": "azure-security-keyvault-keys-dotnet",
- "description": "Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: \"Key Vault keys\", \"KeyClient\", \"CryptographyClient\", \"RSA key\", \"EC key\", \"encrypt decrypt .NET\", \"key rotation\", \"HSM\".\n",
+ "description": "Client library for managing cryptographic keys in Azure Key Vault and Managed HSM.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-keys-java",
@@ -1617,7 +1796,8 @@
"name": "azure-security-keyvault-keys-java",
"description": "Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-security-keyvault-secrets-java",
@@ -1626,25 +1806,28 @@
"name": "azure-security-keyvault-secrets-java",
"description": "Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-dotnet",
"path": "skills\\azure-servicebus-dotnet",
"category": "uncategorized",
"name": "azure-servicebus-dotnet",
- "description": "Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: \"Service Bus\", \"ServiceBusClient\", \"ServiceBusSender\", \"ServiceBusReceiver\", \"ServiceBusProcessor\", \"message queue\", \"pub/sub .NET\", \"dead letter queue\".\n",
+ "description": "Enterprise messaging SDK for reliable message delivery with queues, topics, subscriptions, and sessions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-py",
"path": "skills\\azure-servicebus-py",
"category": "uncategorized",
"name": "azure-servicebus-py",
- "description": "Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.\nTriggers: \"service bus\", \"ServiceBusClient\", \"queue\", \"topic\", \"subscription\", \"message broker\".\n",
+ "description": "Enterprise messaging for reliable cloud communication with queues and pub/sub topics.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-servicebus-ts",
@@ -1653,16 +1836,18 @@
"name": "azure-servicebus-ts",
"description": "Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-speech-to-text-rest-py",
"path": "skills\\azure-speech-to-text-rest-py",
"category": "uncategorized",
"name": "azure-speech-to-text-rest-py",
- "description": "Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.\nTriggers: \"speech to text REST\", \"short audio transcription\", \"speech recognition REST API\", \"STT REST\", \"recognize speech REST\".\nDO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.\n",
+ "description": "Simple REST API for speech-to-text transcription of short audio files (up to 60 seconds). No SDK required - just HTTP requests.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-java",
@@ -1671,79 +1856,88 @@
"name": "azure-storage-blob-java",
"description": "Build blob storage applications with Azure Storage Blob SDK for Java. Use when uploading, downloading, or managing files in Azure Blob Storage, working with containers, or implementing streaming da...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-py",
"path": "skills\\azure-storage-blob-py",
"category": "uncategorized",
"name": "azure-storage-blob-py",
- "description": "Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.\nTriggers: \"blob storage\", \"BlobServiceClient\", \"ContainerClient\", \"BlobClient\", \"upload blob\", \"download blob\".\n",
+ "description": "Client library for Azure Blob Storage \u2014 object storage for unstructured data.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-rust",
"path": "skills\\azure-storage-blob-rust",
"category": "uncategorized",
"name": "azure-storage-blob-rust",
- "description": "Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.\nTriggers: \"blob storage rust\", \"BlobClient rust\", \"upload blob rust\", \"download blob rust\", \"container rust\".\n",
+ "description": "Client library for Azure Blob Storage \u2014 Microsoft's object storage solution for the cloud.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-blob-ts",
"path": "skills\\azure-storage-blob-ts",
"category": "uncategorized",
"name": "azure-storage-blob-ts",
- "description": "Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: \"blob storage\", \"@azure/storage-blob\", \"BlobServiceClient\", \"ContainerClient\", \"upload blob\", \"download blob\", \"SAS token\", \"block blob\".\n",
+ "description": "SDK for Azure Blob Storage operations \u2014 upload, download, list, and manage blobs and containers.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-datalake-py",
"path": "skills\\azure-storage-file-datalake-py",
"category": "uncategorized",
"name": "azure-storage-file-datalake-py",
- "description": "Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.\nTriggers: \"data lake\", \"DataLakeServiceClient\", \"FileSystemClient\", \"ADLS Gen2\", \"hierarchical namespace\".\n",
+ "description": "Hierarchical file system for big data analytics workloads.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-share-py",
"path": "skills\\azure-storage-file-share-py",
"category": "uncategorized",
"name": "azure-storage-file-share-py",
- "description": "Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.\nTriggers: \"azure-storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"file share\", \"SMB\".\n",
+ "description": "Manage SMB file shares for cloud-native and lift-and-shift scenarios.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-file-share-ts",
"path": "skills\\azure-storage-file-share-ts",
"category": "uncategorized",
"name": "azure-storage-file-share-ts",
- "description": "Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: \"file share\", \"@azure/storage-file-share\", \"ShareServiceClient\", \"ShareClient\", \"SMB\", \"Azure Files\".\n",
+ "description": "SDK for Azure File Share operations \u2014 SMB file shares, directories, and file operations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-queue-py",
"path": "skills\\azure-storage-queue-py",
"category": "uncategorized",
"name": "azure-storage-queue-py",
- "description": "Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.\nTriggers: \"queue storage\", \"QueueServiceClient\", \"QueueClient\", \"message queue\", \"dequeue\".\n",
+ "description": "Simple, cost-effective message queuing for asynchronous communication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-storage-queue-ts",
"path": "skills\\azure-storage-queue-ts",
"category": "uncategorized",
"name": "azure-storage-queue-ts",
- "description": "Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: \"queue storage\", \"@azure/storage-queue\", \"QueueServiceClient\", \"QueueClient\", \"send message\", \"receive message\", \"dequeue\", \"visibility timeout\".\n",
+ "description": "SDK for Azure Queue Storage operations \u2014 send, receive, peek, and manage messages in queues.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "azure-web-pubsub-ts",
@@ -1752,16 +1946,18 @@
"name": "azure-web-pubsub-ts",
"description": "Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-architect",
"path": "skills\\backend-architect",
"category": "uncategorized",
"name": "backend-architect",
- "description": "Expert backend architect specializing in scalable API design,\nmicroservices architecture, and distributed systems. Masters REST/GraphQL/gRPC\nAPIs, event-driven architectures, service mesh patterns, and modern backend\nframeworks. Handles service boundary definition, inter-service communication,\nresilience patterns, and observability. Use PROACTIVELY when creating new\nbackend services or APIs.\n",
+ "description": "You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-dev-guidelines",
@@ -1770,7 +1966,8 @@
"name": "backend-dev-guidelines",
"description": "Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod valid...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-development-feature-development",
@@ -1779,16 +1976,18 @@
"name": "backend-development-feature-development",
"description": "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backend-security-coder",
"path": "skills\\backend-security-coder",
"category": "uncategorized",
"name": "backend-security-coder",
- "description": "Expert in secure backend coding practices specializing in input\nvalidation, authentication, and API security. Use PROACTIVELY for backend\nsecurity implementations or security code reviews.\n",
+ "description": "- Working on backend security coder tasks or workflows - Needing guidance, best practices, or checklists for backend security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "backtesting-frameworks",
@@ -1797,7 +1996,8 @@
"name": "backtesting-frameworks",
"description": "Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strateg...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bamboohr-automation",
@@ -1806,7 +2006,8 @@
"name": "bamboohr-automation",
"description": "Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "base",
@@ -1815,7 +2016,8 @@
"name": "base",
"description": "Database management, forms, reports, and data operations with LibreOffice Base.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "basecamp-automation",
@@ -1824,7 +2026,8 @@
"name": "basecamp-automation",
"description": "Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-defensive-patterns",
@@ -1833,7 +2036,8 @@
"name": "bash-defensive-patterns",
"description": "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-linux",
@@ -1842,16 +2046,18 @@
"name": "bash-linux",
"description": "Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-pro",
"path": "skills\\bash-pro",
"category": "uncategorized",
"name": "bash-pro",
- "description": "Master of defensive Bash scripting for production automation, CI/CD\npipelines, and system utilities. Expert in safe, portable, and testable shell\nscripts.\n",
+ "description": "- Writing or reviewing Bash scripts for automation, CI/CD, or ops - Hardening shell scripts for safety and portability",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bash-scripting",
@@ -1860,7 +2066,8 @@
"name": "bash-scripting",
"description": "Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "bats-testing-patterns",
@@ -1869,7 +2076,8 @@
"name": "bats-testing-patterns",
"description": "Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bazel-build-optimization",
@@ -1878,7 +2086,8 @@
"name": "bazel-build-optimization",
"description": "Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "beautiful-prose",
@@ -1887,7 +2096,8 @@
"name": "beautiful-prose",
"description": "Hard-edged writing style contract for timeless, forceful English prose without AI tics",
"risk": "safe",
- "source": "https://github.com/SHADOWPR0/beautiful_prose"
+ "source": "https://github.com/SHADOWPR0/beautiful_prose",
+ "date_added": "2025-02-26"
},
{
"id": "behavioral-modes",
@@ -1896,7 +2106,8 @@
"name": "behavioral-modes",
"description": "AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bevy-ecs-expert",
@@ -1905,7 +2116,8 @@
"name": "bevy-ecs-expert",
"description": "Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "billing-automation",
@@ -1914,7 +2126,8 @@
"name": "billing-automation",
"description": "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "binary-analysis-patterns",
@@ -1923,7 +2136,8 @@
"name": "binary-analysis-patterns",
"description": "Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "bitbucket-automation",
@@ -1932,16 +2146,18 @@
"name": "bitbucket-automation",
"description": "Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "blockchain-developer",
"path": "skills\\blockchain-developer",
"category": "uncategorized",
"name": "blockchain-developer",
- "description": "Build production-ready Web3 applications, smart contracts, and\ndecentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and\nenterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3\napps, DeFi protocols, or blockchain infrastructure.\n",
+ "description": "- Working on blockchain developer tasks or workflows - Needing guidance, best practices, or checklists for blockchain developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "blockrun",
@@ -1950,7 +2166,8 @@
"name": "blockrun",
"description": "Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models (\\\"blockrun\\\", \\\"use grok\\\", \\\"use gpt\\\", \\\"da...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "box-automation",
@@ -1959,7 +2176,8 @@
"name": "box-automation",
"description": "Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brainstorming",
@@ -1968,7 +2186,8 @@
"name": "brainstorming",
"description": "Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brand-guidelines-anthropic",
@@ -1977,7 +2196,8 @@
"name": "brand-guidelines-anthropic",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brand-guidelines-community",
@@ -1986,7 +2206,8 @@
"name": "brand-guidelines-community",
"description": "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "brevo-automation",
@@ -1995,7 +2216,8 @@
"name": "brevo-automation",
"description": "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "broken-authentication",
@@ -2004,7 +2226,8 @@
"name": "broken-authentication",
"description": "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "browser-automation",
@@ -2013,7 +2236,8 @@
"name": "browser-automation",
"description": "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "browser-extension-builder",
@@ -2022,7 +2246,8 @@
"name": "browser-extension-builder",
"description": "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "bullmq-specialist",
@@ -2031,7 +2256,8 @@
"name": "bullmq-specialist",
"description": "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "bun-development",
@@ -2040,7 +2266,8 @@
"name": "bun-development",
"description": "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "burp-suite-testing",
@@ -2049,16 +2276,18 @@
"name": "burp-suite-testing",
"description": "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "business-analyst",
"path": "skills\\business-analyst",
"category": "uncategorized",
"name": "business-analyst",
- "description": "Master modern business analysis with AI-powered analytics,\nreal-time dashboards, and data-driven insights. Build comprehensive KPI\nframeworks, predictive models, and strategic recommendations. Use PROACTIVELY\nfor business intelligence or strategic analysis.\n",
+ "description": "- Working on business analyst tasks or workflows - Needing guidance, best practices, or checklists for business analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "busybox-on-windows",
@@ -2067,16 +2296,18 @@
"name": "busybox-on-windows",
"description": "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c-pro",
"path": "skills\\c-pro",
"category": "uncategorized",
"name": "c-pro",
- "description": "Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.",
+ "description": "Write efficient C code with proper memory management, pointer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-architecture-c4-architecture",
@@ -2085,43 +2316,48 @@
"name": "c4-architecture-c4-architecture",
"description": "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-code",
"path": "skills\\c4-code",
"category": "uncategorized",
"name": "c4-code",
- "description": "Expert C4 Code-level documentation specialist. Analyzes code\ndirectories to create comprehensive C4 code-level documentation including\nfunction signatures, arguments, dependencies, and code structure. Use when\ndocumenting code at the lowest C4 level for individual directories and code\nmodules.\n",
+ "description": "- Working on c4 code level: [directory name] tasks or workflows - Needing guidance, best practices, or checklists for c4 code level: [directory name]",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-component",
"path": "skills\\c4-component",
"category": "uncategorized",
"name": "c4-component",
- "description": "Expert C4 Component-level documentation specialist. Synthesizes C4\nCode-level documentation into Component-level architecture, defining component\nboundaries, interfaces, and relationships. Creates component diagrams and\ndocumentation. Use when synthesizing code-level documentation into logical\ncomponents.\n",
+ "description": "- Working on c4 component level: [component name] tasks or workflows - Needing guidance, best practices, or checklists for c4 component level: [component name]",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-container",
"path": "skills\\c4-container",
"category": "uncategorized",
"name": "c4-container",
- "description": "Expert C4 Container-level documentation specialist. Synthesizes\nComponent-level documentation into Container-level architecture, mapping\ncomponents to deployment units, documenting container interfaces as APIs, and\ncreating container diagrams. Use when synthesizing components into deployment\ncontainers and documenting system deployment architecture.\n",
+ "description": "- Working on c4 container level: system deployment tasks or workflows - Needing guidance, best practices, or checklists for c4 container level: system deployment",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "c4-context",
"path": "skills\\c4-context",
"category": "uncategorized",
"name": "c4-context",
- "description": "Expert C4 Context-level documentation specialist. Creates\nhigh-level system context diagrams, documents personas, user journeys, system\nfeatures, and external dependencies. Synthesizes container and component\ndocumentation with system documentation to create comprehensive context-level\narchitecture. Use when creating the highest-level C4 system context\ndocumentation.\n",
+ "description": "- Working on c4 context level: system context tasks or workflows - Needing guidance, best practices, or checklists for c4 context level: system context",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cal-com-automation",
@@ -2130,7 +2366,8 @@
"name": "cal-com-automation",
"description": "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "calc",
@@ -2139,7 +2376,8 @@
"name": "calc",
"description": "Spreadsheet creation, format conversion (ODS/XLSX/CSV), formulas, data automation with LibreOffice Calc.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "calendly-automation",
@@ -2148,7 +2386,8 @@
"name": "calendly-automation",
"description": "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "canva-automation",
@@ -2157,7 +2396,8 @@
"name": "canva-automation",
"description": "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "canvas-design",
@@ -2166,16 +2406,18 @@
"name": "canvas-design",
"description": "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "carrier-relationship-management",
"path": "skills\\carrier-relationship-management",
"category": "uncategorized",
"name": "carrier-relationship-management",
- "description": "Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting. Use when managing carriers, negotiating rates, evaluating carrier performance, or building freight strategies.\n",
+ "description": "Use this skill when building and managing a carrier network, conducting freight RFPs, negotiating linehaul and accessorial rates, tracking carrier KPIs via scorecards, or ensuring regulatory compliance of transportation partners.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-backend-patterns",
@@ -2184,7 +2426,8 @@
"name": "cc-skill-backend-patterns",
"description": "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-clickhouse-io",
@@ -2193,7 +2436,8 @@
"name": "cc-skill-clickhouse-io",
"description": "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-coding-standards",
@@ -2202,7 +2446,8 @@
"name": "cc-skill-coding-standards",
"description": "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-continuous-learning",
@@ -2211,7 +2456,8 @@
"name": "cc-skill-continuous-learning",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-frontend-patterns",
@@ -2220,7 +2466,8 @@
"name": "cc-skill-frontend-patterns",
"description": "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-project-guidelines-example",
@@ -2229,7 +2476,8 @@
"name": "cc-skill-project-guidelines-example",
"description": "Project Guidelines Skill (Example)",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-security-review",
@@ -2238,7 +2486,8 @@
"name": "cc-skill-security-review",
"description": "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cc-skill-strategic-compact",
@@ -2247,7 +2496,8 @@
"name": "cc-skill-strategic-compact",
"description": "Development skill from everything-claude-code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cdk-patterns",
@@ -2256,7 +2506,8 @@
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "changelog-automation",
@@ -2265,7 +2516,8 @@
"name": "changelog-automation",
"description": "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "chrome-extension-developer",
@@ -2274,7 +2526,8 @@
"name": "chrome-extension-developer",
"description": "Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cicd-automation-workflow-automate",
@@ -2283,7 +2536,8 @@
"name": "cicd-automation-workflow-automate",
"description": "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "circleci-automation",
@@ -2292,7 +2546,8 @@
"name": "circleci-automation",
"description": "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "clarity-gate",
@@ -2301,7 +2556,8 @@
"name": "clarity-gate",
"description": "Pre-ingestion verification for epistemic quality in RAG systems with 9-point verification and Two-Round HITL workflow",
"risk": "safe",
- "source": "https://github.com/frmoretto/clarity-gate"
+ "source": "https://github.com/frmoretto/clarity-gate",
+ "date_added": "2025-02-26"
},
{
"id": "claude-ally-health",
@@ -2310,7 +2566,8 @@
"name": "claude-ally-health",
"description": "A health assistant skill for medical information analysis, symptom tracking, and wellness guidance.",
"risk": "safe",
- "source": "https://github.com/huifer/Claude-Ally-Health"
+ "source": "https://github.com/huifer/Claude-Ally-Health",
+ "date_added": "2025-02-26"
},
{
"id": "claude-code-guide",
@@ -2319,7 +2576,8 @@
"name": "claude-code-guide",
"description": "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "claude-d3js-skill",
@@ -2328,7 +2586,8 @@
"name": "claude-d3js-skill",
"description": "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "claude-scientific-skills",
@@ -2337,7 +2596,8 @@
"name": "claude-scientific-skills",
"description": "Scientific research and analysis skills",
"risk": "safe",
- "source": "https://github.com/K-Dense-AI/claude-scientific-skills"
+ "source": "https://github.com/K-Dense-AI/claude-scientific-skills",
+ "date_added": "2025-02-26"
},
{
"id": "claude-speed-reader",
@@ -2346,7 +2606,8 @@
"name": "claude-speed-reader",
"description": "-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting",
"risk": "safe",
- "source": "https://github.com/SeanZoR/claude-speed-reader"
+ "source": "https://github.com/SeanZoR/claude-speed-reader",
+ "date_added": "2025-02-26"
},
{
"id": "claude-win11-speckit-update-skill",
@@ -2355,7 +2616,8 @@
"name": "claude-win11-speckit-update-skill",
"description": "Windows 11 system management",
"risk": "safe",
- "source": "https://github.com/NotMyself/claude-win11-speckit-update-skill"
+ "source": "https://github.com/NotMyself/claude-win11-speckit-update-skill",
+ "date_added": "2025-02-26"
},
{
"id": "clean-code",
@@ -2364,7 +2626,8 @@
"name": "clean-code",
"description": "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...",
"risk": "safe",
- "source": "ClawForge (https://github.com/jackjin1997/ClawForge)"
+ "source": "ClawForge (https://github.com/jackjin1997/ClawForge)",
+ "date_added": "2025-02-26"
},
{
"id": "clerk-auth",
@@ -2373,7 +2636,8 @@
"name": "clerk-auth",
"description": "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "clickup-automation",
@@ -2382,7 +2646,8 @@
"name": "clickup-automation",
"description": "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "close-automation",
@@ -2391,16 +2656,18 @@
"name": "close-automation",
"description": "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-architect",
"path": "skills\\cloud-architect",
"category": "uncategorized",
"name": "cloud-architect",
- "description": "Expert cloud architect specializing in AWS/Azure/GCP multi-cloud\ninfrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost\noptimization, and modern architectural patterns. Masters serverless,\nmicroservices, security, compliance, and disaster recovery. Use PROACTIVELY\nfor cloud architecture, cost optimization, migration planning, or multi-cloud\nstrategies.\n",
+ "description": "- Working on cloud architect tasks or workflows - Needing guidance, best practices, or checklists for cloud architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-devops",
@@ -2409,7 +2676,8 @@
"name": "cloud-devops",
"description": "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "cloud-penetration-testing",
@@ -2418,7 +2686,8 @@
"name": "cloud-penetration-testing",
"description": "This skill should be used when the user asks to \"perform cloud penetration testing\", \"assess Azure or AWS or GCP security\", \"enumerate cloud resources\", \"exploit cloud misconfiguratio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloudflare-workers-expert",
@@ -2427,7 +2696,8 @@
"name": "cloudflare-workers-expert",
"description": "Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cloudformation-best-practices",
@@ -2436,7 +2706,8 @@
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "coda-automation",
@@ -2445,7 +2716,8 @@
"name": "coda-automation",
"description": "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-documentation-code-explain",
@@ -2454,7 +2726,8 @@
"name": "code-documentation-code-explain",
"description": "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-documentation-doc-generate",
@@ -2463,7 +2736,8 @@
"name": "code-documentation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-context-restore",
@@ -2472,7 +2746,8 @@
"name": "code-refactoring-context-restore",
"description": "Use when working with code refactoring context restore",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-refactor-clean",
@@ -2481,7 +2756,8 @@
"name": "code-refactoring-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-refactoring-tech-debt",
@@ -2490,7 +2766,8 @@
"name": "code-refactoring-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-ai-ai-review",
@@ -2499,7 +2776,8 @@
"name": "code-review-ai-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-checklist",
@@ -2508,7 +2786,8 @@
"name": "code-review-checklist",
"description": "Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-review-excellence",
@@ -2517,16 +2796,18 @@
"name": "code-review-excellence",
"description": "Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "code-reviewer",
"path": "skills\\code-reviewer",
"category": "uncategorized",
"name": "code-reviewer",
- "description": "Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.",
+ "description": "Elite code review expert specializing in modern AI-powered code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-deps-audit",
@@ -2535,7 +2816,8 @@
"name": "codebase-cleanup-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-refactor-clean",
@@ -2544,7 +2826,8 @@
"name": "codebase-cleanup-refactor-clean",
"description": "You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codebase-cleanup-tech-debt",
@@ -2553,7 +2836,8 @@
"name": "codebase-cleanup-tech-debt",
"description": "You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "codex-review",
@@ -2562,7 +2846,8 @@
"name": "codex-review",
"description": "Professional code review with auto CHANGELOG generation, integrated with Codex AI",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "commit",
@@ -2571,16 +2856,18 @@
"name": "commit",
"description": "Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/commit",
+ "date_added": "2025-02-26"
},
{
"id": "competitive-landscape",
"path": "skills\\competitive-landscape",
"category": "uncategorized",
"name": "competitive-landscape",
- "description": "This skill should be used when the user asks to \\\\\\\"analyze\ncompetitors\", \"assess competitive landscape\", \"identify differentiation\",\n\"evaluate market positioning\", \"apply Porter's Five Forces\", or requests\ncompetitive strategy analysis.\n",
+ "description": "Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "competitor-alternatives",
@@ -2589,7 +2876,8 @@
"name": "competitor-alternatives",
"description": "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'compa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "comprehensive-review-full-review",
@@ -2598,7 +2886,8 @@
"name": "comprehensive-review-full-review",
"description": "Use when working with comprehensive review full review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "comprehensive-review-pr-enhance",
@@ -2607,7 +2896,8 @@
"name": "comprehensive-review-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and e...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "computer-use-agents",
@@ -2616,7 +2906,8 @@
"name": "computer-use-agents",
"description": "Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-so...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "computer-vision-expert",
@@ -2625,7 +2916,8 @@
"name": "computer-vision-expert",
"description": "SOTA Computer Vision Expert (2026). Specialized in YOLO26, Segment Anything 3 (SAM 3), Vision Language Models, and real-time spatial analysis.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "concise-planning",
@@ -2634,7 +2926,8 @@
"name": "concise-planning",
"description": "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-implement",
@@ -2643,7 +2936,8 @@
"name": "conductor-implement",
"description": "Execute tasks from a track's implementation plan following TDD workflow",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-manage",
@@ -2652,7 +2946,8 @@
"name": "conductor-manage",
"description": "Manage track lifecycle: archive, restore, delete, rename, and cleanup",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-new-track",
@@ -2661,7 +2956,8 @@
"name": "conductor-new-track",
"description": "Create a new track with specification and phased implementation plan",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-revert",
@@ -2670,16 +2966,18 @@
"name": "conductor-revert",
"description": "Git-aware undo by logical work unit (track, phase, or task)",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-setup",
"path": "skills\\conductor-setup",
"category": "uncategorized",
"name": "conductor-setup",
- "description": "Initialize project with Conductor artifacts (product definition,\ntech stack, workflow, style guides)\n",
+ "description": "Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-status",
@@ -2688,16 +2986,18 @@
"name": "conductor-status",
"description": "Display project status, active tracks, and next actions",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conductor-validator",
"path": "skills\\conductor-validator",
"category": "uncategorized",
"name": "conductor-validator",
- "description": "Validates Conductor project artifacts for completeness,\nconsistency, and correctness. Use after setup, when diagnosing issues, or\nbefore implementation to verify project context.\n",
+ "description": "ls -la conductor/",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "confluence-automation",
@@ -2706,7 +3006,8 @@
"name": "confluence-automation",
"description": "Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "content-creator",
@@ -2715,16 +3016,18 @@
"name": "content-creator",
"description": "Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "content-marketer",
"path": "skills\\content-marketer",
"category": "uncategorized",
"name": "content-marketer",
- "description": "Elite content marketing strategist specializing in AI-powered\ncontent creation, omnichannel distribution, SEO optimization, and data-driven\nperformance marketing. Masters modern content tools, social media automation,\nand conversion optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive content marketing.\n",
+ "description": "- Working on content marketer tasks or workflows - Needing guidance, best practices, or checklists for content marketer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-compression",
@@ -2733,7 +3036,8 @@
"name": "context-compression",
"description": "Design and evaluate compression strategies for long-running sessions",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-compression"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-compression",
+ "date_added": "2025-02-26"
},
{
"id": "context-degradation",
@@ -2742,16 +3046,18 @@
"name": "context-degradation",
"description": "Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-degradation",
+ "date_added": "2025-02-26"
},
{
"id": "context-driven-development",
"path": "skills\\context-driven-development",
"category": "uncategorized",
"name": "context-driven-development",
- "description": "Use this skill when working with Conductor's context-driven\ndevelopment methodology, managing project context artifacts, or understanding\nthe relationship between product.md, tech-stack.md, and workflow.md files.\n",
+ "description": "Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-fundamentals",
@@ -2760,7 +3066,8 @@
"name": "context-fundamentals",
"description": "Understand what context is, why it matters, and the anatomy of context in agent systems",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-fundamentals"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-fundamentals",
+ "date_added": "2025-02-26"
},
{
"id": "context-management-context-restore",
@@ -2769,7 +3076,8 @@
"name": "context-management-context-restore",
"description": "Use when working with context management context restore",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-management-context-save",
@@ -2778,16 +3086,18 @@
"name": "context-management-context-save",
"description": "Use when working with context management context save",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-manager",
"path": "skills\\context-manager",
"category": "uncategorized",
"name": "context-manager",
- "description": "Elite AI context engineering specialist mastering dynamic context\nmanagement, vector databases, knowledge graphs, and intelligent memory\nsystems. Orchestrates context across multi-agent workflows, enterprise AI\nsystems, and long-running projects with 2024/2025 best practices. Use\nPROACTIVELY for complex AI orchestration.\n",
+ "description": "- Working on context manager tasks or workflows - Needing guidance, best practices, or checklists for context manager",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "context-optimization",
@@ -2796,7 +3106,8 @@
"name": "context-optimization",
"description": "Apply compaction, masking, and caching strategies",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-optimization"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/context-optimization",
+ "date_added": "2025-02-26"
},
{
"id": "context-window-management",
@@ -2805,7 +3116,8 @@
"name": "context-window-management",
"description": "Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "context7-auto-research",
@@ -2814,7 +3126,8 @@
"name": "context7-auto-research",
"description": "Automatically fetch latest library/framework documentation for Claude Code via Context7 API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "conversation-memory",
@@ -2823,7 +3136,8 @@
"name": "conversation-memory",
"description": "Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "convertkit-automation",
@@ -2832,7 +3146,8 @@
"name": "convertkit-automation",
"description": "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copilot-sdk",
@@ -2841,7 +3156,8 @@
"name": "copilot-sdk",
"description": "Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session managemen...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copy-editing",
@@ -2850,16 +3166,18 @@
"name": "copy-editing",
"description": "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "copywriting",
"path": "skills\\copywriting",
"category": "uncategorized",
"name": "copywriting",
- "description": "Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.\n",
+ "description": "Produce **clear, credible, and action-oriented marketing copy** that aligns with user intent and business goals.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "core-components",
@@ -2868,7 +3186,8 @@
"name": "core-components",
"description": "Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cost-optimization",
@@ -2877,16 +3196,18 @@
"name": "cost-optimization",
"description": "Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cpp-pro",
"path": "skills\\cpp-pro",
"category": "uncategorized",
"name": "cpp-pro",
- "description": "Write idiomatic C++ code with modern features, RAII, smart\npointers, and STL algorithms. Handles templates, move semantics, and\nperformance optimization. Use PROACTIVELY for C++ refactoring, memory safety,\nor complex C++ patterns.\n",
+ "description": "- Working on cpp pro tasks or workflows - Needing guidance, best practices, or checklists for cpp pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "cqrs-implementation",
@@ -2895,7 +3216,8 @@
"name": "cqrs-implementation",
"description": "Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "create-pr",
@@ -2904,7 +3226,8 @@
"name": "create-pr",
"description": "Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/create-pr"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/create-pr",
+ "date_added": "2025-02-26"
},
{
"id": "crewai",
@@ -2913,25 +3236,28 @@
"name": "crewai",
"description": "Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (s...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "crypto-bd-agent",
"path": "skills\\crypto-bd-agent",
"category": "uncategorized",
"name": "crypto-bd-agent",
- "description": "Autonomous crypto business development patterns \u2014 multi-chain token discovery, 100-point scoring with wallet forensics, x402 micropayments, ERC-8004 on-chain identity, LLM cascade routing, and pipeline automation for CEX/DEX listing acquisition. Use when building AI agents for crypto BD, token evaluation, exchange listing outreach, or autonomous commerce with payment protocols.\n",
+ "description": "> Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "csharp-pro",
"path": "skills\\csharp-pro",
"category": "uncategorized",
"name": "csharp-pro",
- "description": "Write modern C# code with advanced features like records, pattern\nmatching, and async/await. Optimizes .NET applications, implements enterprise\npatterns, and ensures comprehensive testing. Use PROACTIVELY for C#\nrefactoring, performance optimization, or complex .NET solutions.\n",
+ "description": "- Working on csharp pro tasks or workflows - Needing guidance, best practices, or checklists for csharp pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "culture-index",
@@ -2940,25 +3266,28 @@
"name": "culture-index",
"description": "Index and search culture documentation",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/culture-index"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/culture-index",
+ "date_added": "2025-02-26"
},
{
"id": "customer-support",
"path": "skills\\customer-support",
"category": "uncategorized",
"name": "customer-support",
- "description": "Elite AI-powered customer support specialist mastering\nconversational AI, automated ticketing, sentiment analysis, and omnichannel\nsupport experiences. Integrates modern support tools, chatbot platforms, and\nCX optimization with 2024/2025 best practices. Use PROACTIVELY for\ncomprehensive customer experience management.\n",
+ "description": "- Working on customer support tasks or workflows - Needing guidance, best practices, or checklists for customer support",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "customs-trade-compliance",
"path": "skills\\customs-trade-compliance",
"category": "uncategorized",
"name": "customs-trade-compliance",
- "description": "Codified expertise for customs documentation, tariff classification, duty optimisation, restricted party screening, and regulatory compliance across multiple jurisdictions. Informed by trade compliance specialists with 15+ years experience. Includes HS classification logic, Incoterms application, FTA utilisation, and penalty mitigation. Use when handling customs clearance, tariff classification, trade compliance, import/export documentation, or duty optimisation.\n",
+ "description": "Use this skill when navigating international trade regulations, classifying goods under HS codes, determining appropriate Incoterms, managing import/export documentation, or optimizing customs duty payments through Free Trade Agreements.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "daily-news-report",
@@ -2967,16 +3296,18 @@
"name": "daily-news-report",
"description": "Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineer",
"path": "skills\\data-engineer",
"category": "uncategorized",
"name": "data-engineer",
- "description": "Build scalable data pipelines, modern data warehouses, and\nreal-time streaming architectures. Implements Apache Spark, dbt, Airflow, and\ncloud-native data platforms. Use PROACTIVELY for data pipeline design,\nanalytics infrastructure, or modern data stack implementation.\n",
+ "description": "You are a data engineer specializing in scalable data pipelines, modern data architecture, and analytics infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineering-data-driven-feature",
@@ -2985,7 +3316,8 @@
"name": "data-engineering-data-driven-feature",
"description": "Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-engineering-data-pipeline",
@@ -2994,7 +3326,8 @@
"name": "data-engineering-data-pipeline",
"description": "You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-quality-frameworks",
@@ -3003,16 +3336,18 @@
"name": "data-quality-frameworks",
"description": "Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-scientist",
"path": "skills\\data-scientist",
"category": "uncategorized",
"name": "data-scientist",
- "description": "Expert data scientist for advanced analytics, machine learning, and\nstatistical modeling. Handles complex data analysis, predictive modeling, and\nbusiness intelligence. Use PROACTIVELY for data analysis tasks, ML modeling,\nstatistical analysis, and data-driven insights.\n",
+ "description": "- Working on data scientist tasks or workflows - Needing guidance, best practices, or checklists for data scientist",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-storytelling",
@@ -3021,7 +3356,8 @@
"name": "data-storytelling",
"description": "Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive present...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "data-structure-protocol",
@@ -3030,7 +3366,8 @@
"name": "data-structure-protocol",
"description": "Give agents persistent structural memory of a codebase \u2014 navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.",
"risk": "safe",
- "source": "https://github.com/k-kolomeitsev/data-structure-protocol"
+ "source": "https://github.com/k-kolomeitsev/data-structure-protocol",
+ "date_added": "2025-02-26"
},
{
"id": "database",
@@ -3039,25 +3376,28 @@
"name": "database",
"description": "Database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "database-admin",
"path": "skills\\database-admin",
"category": "uncategorized",
"name": "database-admin",
- "description": "Expert database administrator specializing in modern cloud\ndatabases, automation, and reliability engineering. Masters AWS/Azure/GCP\ndatabase services, Infrastructure as Code, high availability, disaster\nrecovery, performance optimization, and compliance. Handles multi-cloud\nstrategies, container databases, and cost optimization. Use PROACTIVELY for\ndatabase architecture, operations, or reliability engineering.\n",
+ "description": "- Working on database admin tasks or workflows - Needing guidance, best practices, or checklists for database admin",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-architect",
"path": "skills\\database-architect",
"category": "uncategorized",
"name": "database-architect",
- "description": "Expert database architect specializing in data layer design from\nscratch, technology selection, schema modeling, and scalable database\narchitectures. Masters SQL/NoSQL/TimeSeries database selection, normalization\nstrategies, migration planning, and performance-first design. Handles both\ngreenfield architectures and re-architecture of existing systems. Use\nPROACTIVELY for database architecture, technology selection, or data modeling\ndecisions.\n",
+ "description": "You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-cloud-optimization-cost-optimize",
@@ -3066,7 +3406,8 @@
"name": "database-cloud-optimization-cost-optimize",
"description": "You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-design",
@@ -3075,7 +3416,8 @@
"name": "database-design",
"description": "Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migration",
@@ -3084,7 +3426,8 @@
"name": "database-migration",
"description": "Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data tr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migrations-migration-observability",
@@ -3093,7 +3436,8 @@
"name": "database-migrations-migration-observability",
"description": "Migration monitoring, CDC, and observability infrastructure",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-migrations-sql-migrations",
@@ -3102,16 +3446,18 @@
"name": "database-migrations-sql-migrations",
"description": "SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "database-optimizer",
"path": "skills\\database-optimizer",
"category": "uncategorized",
"name": "database-optimizer",
- "description": "Expert database optimizer specializing in modern performance\ntuning, query optimization, and scalable architectures. Masters advanced\nindexing, N+1 resolution, multi-tier caching, partitioning strategies, and\ncloud database optimization. Handles complex query analysis, migration\nstrategies, and performance monitoring. Use PROACTIVELY for database\noptimization, performance issues, or scalability challenges.\n",
+ "description": "- Working on database optimizer tasks or workflows - Needing guidance, best practices, or checklists for database optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "datadog-automation",
@@ -3120,7 +3466,8 @@
"name": "datadog-automation",
"description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-golang",
@@ -3129,7 +3476,8 @@
"name": "dbos-golang",
"description": "DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Clie...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-python",
@@ -3138,7 +3486,8 @@
"name": "dbos-python",
"description": "DBOS Python SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Python code with DBOS, creating workflows and steps, using queues, using DBOSC...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbos-typescript",
@@ -3147,7 +3496,8 @@
"name": "dbos-typescript",
"description": "DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, usi...",
"risk": "safe",
- "source": "https://docs.dbos.dev/"
+ "source": "https://docs.dbos.dev/",
+ "date_added": "2025-02-26"
},
{
"id": "dbt-transformation-patterns",
@@ -3156,7 +3506,8 @@
"name": "dbt-transformation-patterns",
"description": "Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-context-mapping",
@@ -3165,7 +3516,8 @@
"name": "ddd-context-mapping",
"description": "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-strategic-design",
@@ -3174,7 +3526,8 @@
"name": "ddd-strategic-design",
"description": "Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "ddd-tactical-patterns",
@@ -3183,16 +3536,18 @@
"name": "ddd-tactical-patterns",
"description": "Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "debugger",
"path": "skills\\debugger",
"category": "uncategorized",
"name": "debugger",
- "description": "Debugging specialist for errors, test failures, and unexpected\nbehavior. Use proactively when encountering any issues.\n",
+ "description": "- Working on debugger tasks or workflows - Needing guidance, best practices, or checklists for debugger",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "debugging-strategies",
@@ -3201,7 +3556,8 @@
"name": "debugging-strategies",
"description": "Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance iss...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "debugging-toolkit-smart-debug",
@@ -3210,7 +3566,8 @@
"name": "debugging-toolkit-smart-debug",
"description": "Use when working with debugging toolkit smart debug",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deep-research",
@@ -3219,7 +3576,8 @@
"name": "deep-research",
"description": "Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 ...",
"risk": "safe",
- "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research"
+ "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research",
+ "date_added": "2025-02-26"
},
{
"id": "defi-protocol-templates",
@@ -3228,7 +3586,8 @@
"name": "defi-protocol-templates",
"description": "Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dependency-management-deps-audit",
@@ -3237,7 +3596,8 @@
"name": "dependency-management-deps-audit",
"description": "You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dependency-upgrade",
@@ -3246,16 +3606,18 @@
"name": "dependency-upgrade",
"description": "Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing brea...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-engineer",
"path": "skills\\deployment-engineer",
"category": "uncategorized",
"name": "deployment-engineer",
- "description": "Expert deployment engineer specializing in modern CI/CD pipelines,\nGitOps workflows, and advanced deployment automation. Masters GitHub Actions,\nArgoCD/Flux, progressive delivery, container security, and platform\nengineering. Handles zero-downtime deployments, security scanning, and\ndeveloper experience optimization. Use PROACTIVELY for CI/CD design, GitOps\nimplementation, or deployment automation.\n",
+ "description": "You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-pipeline-design",
@@ -3264,7 +3626,8 @@
"name": "deployment-pipeline-design",
"description": "Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing Gi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-procedures",
@@ -3273,7 +3636,8 @@
"name": "deployment-procedures",
"description": "Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "deployment-validation-config-validate",
@@ -3282,7 +3646,8 @@
"name": "deployment-validation-config-validate",
"description": "You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configurat",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "design-md",
@@ -3291,16 +3656,18 @@
"name": "design-md",
"description": "Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files",
"risk": "safe",
- "source": "https://github.com/google-labs-code/stitch-skills/tree/main/skills/design-md"
+ "source": "https://github.com/google-labs-code/stitch-skills/tree/main/skills/design-md",
+ "date_added": "2025-02-26"
},
{
"id": "design-orchestration",
"path": "skills\\design-orchestration",
"category": "uncategorized",
"name": "design-orchestration",
- "description": "Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.",
+ "description": "Ensure that **ideas become designs**, **designs are reviewed**, and **only validated designs reach implementation**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "development",
@@ -3309,16 +3676,18 @@
"name": "development",
"description": "Comprehensive web, mobile, and backend development workflow bundling frontend, backend, full-stack, and mobile development skills for end-to-end application delivery.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "devops-troubleshooter",
"path": "skills\\devops-troubleshooter",
"category": "uncategorized",
"name": "devops-troubleshooter",
- "description": "Expert DevOps troubleshooter specializing in rapid incident\nresponse, advanced debugging, and modern observability. Masters log analysis,\ndistributed tracing, Kubernetes debugging, performance optimization, and root\ncause analysis. Handles production outages, system reliability, and preventive\nmonitoring. Use PROACTIVELY for debugging, incident response, or system\ntroubleshooting.\n",
+ "description": "- Working on devops troubleshooter tasks or workflows - Needing guidance, best practices, or checklists for devops troubleshooter",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "discord-automation",
@@ -3327,7 +3696,8 @@
"name": "discord-automation",
"description": "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "discord-bot-architect",
@@ -3336,7 +3706,8 @@
"name": "discord-bot-architect",
"description": "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "dispatching-parallel-agents",
@@ -3345,7 +3716,8 @@
"name": "dispatching-parallel-agents",
"description": "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "distributed-debugging-debug-trace",
@@ -3354,7 +3726,8 @@
"name": "distributed-debugging-debug-trace",
"description": "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, an...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "distributed-tracing",
@@ -3363,16 +3736,18 @@
"name": "distributed-tracing",
"description": "Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implem...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "django-pro",
"path": "skills\\django-pro",
"category": "uncategorized",
"name": "django-pro",
- "description": "Master Django 5.x with async views, DRF, Celery, and Django\nChannels. Build scalable web applications with proper architecture, testing,\nand deployment. Use PROACTIVELY for Django development, ORM optimization, or\ncomplex Django patterns.\n",
+ "description": "- Working on django pro tasks or workflows - Needing guidance, best practices, or checklists for django pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "doc-coauthoring",
@@ -3381,7 +3756,8 @@
"name": "doc-coauthoring",
"description": "Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docker-expert",
@@ -3390,16 +3766,18 @@
"name": "docker-expert",
"description": "Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY f...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docs-architect",
"path": "skills\\docs-architect",
"category": "uncategorized",
"name": "docs-architect",
- "description": "Creates comprehensive technical documentation from existing\ncodebases. Analyzes architecture, design patterns, and implementation details\nto produce long-form technical manuals and ebooks. Use PROACTIVELY for system\ndocumentation, architecture guides, or technical deep-dives.\n",
+ "description": "- Working on docs architect tasks or workflows - Needing guidance, best practices, or checklists for docs architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "documentation",
@@ -3408,7 +3786,8 @@
"name": "documentation",
"description": "Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "documentation-generation-doc-generate",
@@ -3417,7 +3796,8 @@
"name": "documentation-generation-doc-generate",
"description": "You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "documentation-templates",
@@ -3426,7 +3806,8 @@
"name": "documentation-templates",
"description": "Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docusign-automation",
@@ -3435,7 +3816,8 @@
"name": "docusign-automation",
"description": "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "docx-official",
@@ -3444,7 +3826,8 @@
"name": "docx-official",
"description": "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional document...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "domain-driven-design",
@@ -3453,16 +3836,18 @@
"name": "domain-driven-design",
"description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-architect",
"path": "skills\\dotnet-architect",
"category": "uncategorized",
"name": "dotnet-architect",
- "description": "Expert .NET backend architect specializing in C#, ASP.NET Core,\nEntity Framework, Dapper, and enterprise application patterns. Masters\nasync/await, dependency injection, caching strategies, and performance\noptimization. Use PROACTIVELY for .NET API development, code review, or\narchitecture decisions.\n",
+ "description": "- Working on dotnet architect tasks or workflows - Needing guidance, best practices, or checklists for dotnet architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-backend",
@@ -3471,7 +3856,8 @@
"name": "dotnet-backend",
"description": "Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "dotnet-backend-patterns",
@@ -3480,7 +3866,8 @@
"name": "dotnet-backend-patterns",
"description": "Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuratio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "draw",
@@ -3489,7 +3876,8 @@
"name": "draw",
"description": "Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "dropbox-automation",
@@ -3498,16 +3886,18 @@
"name": "dropbox-automation",
"description": "Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "dx-optimizer",
"path": "skills\\dx-optimizer",
"category": "uncategorized",
"name": "dx-optimizer",
- "description": "Developer Experience specialist. Improves tooling, setup, and\nworkflows. Use PROACTIVELY when setting up new projects, after team feedback,\nor when development friction is noticed.\n",
+ "description": "- Working on dx optimizer tasks or workflows - Needing guidance, best practices, or checklists for dx optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "e2e-testing",
@@ -3516,7 +3906,8 @@
"name": "e2e-testing",
"description": "End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "e2e-testing-patterns",
@@ -3525,16 +3916,18 @@
"name": "e2e-testing-patterns",
"description": "Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "elixir-pro",
"path": "skills\\elixir-pro",
"category": "uncategorized",
"name": "elixir-pro",
- "description": "Write idiomatic Elixir code with OTP patterns, supervision trees,\nand Phoenix LiveView. Masters concurrency, fault tolerance, and distributed\nsystems. Use PROACTIVELY for Elixir refactoring, OTP design, or complex BEAM\noptimizations.\n",
+ "description": "- Working on elixir pro tasks or workflows - Needing guidance, best practices, or checklists for elixir pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "email-sequence",
@@ -3543,7 +3936,8 @@
"name": "email-sequence",
"description": "When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions \"email sequence,\" \"drip campa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "email-systems",
@@ -3552,7 +3946,8 @@
"name": "email-systems",
"description": "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill cov...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "embedding-strategies",
@@ -3561,7 +3956,8 @@
"name": "embedding-strategies",
"description": "Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific dom...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "employment-contract-templates",
@@ -3570,16 +3966,18 @@
"name": "employment-contract-templates",
"description": "Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "energy-procurement",
"path": "skills\\energy-procurement",
"category": "uncategorized",
"name": "energy-procurement",
- "description": "Codified expertise for electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimising tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.\n",
+ "description": "Use this skill when managing energy procurement tasks, such as optimizing electricity or gas tariffs, evaluating Power Purchase Agreements (PPAs), or developing long-term energy cost management strategies for commercial or industrial facilities.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "environment-setup-guide",
@@ -3588,7 +3986,8 @@
"name": "environment-setup-guide",
"description": "Guide developers through setting up development environments with proper tools, dependencies, and configurations",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-error-analysis",
@@ -3597,7 +3996,8 @@
"name": "error-debugging-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-error-trace",
@@ -3606,7 +4006,8 @@
"name": "error-debugging-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured loggi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-debugging-multi-agent-review",
@@ -3615,16 +4016,18 @@
"name": "error-debugging-multi-agent-review",
"description": "Use when working with error debugging multi agent review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-detective",
"path": "skills\\error-detective",
"category": "uncategorized",
"name": "error-detective",
- "description": "Search logs and codebases for error patterns, stack traces, and\nanomalies. Correlates errors across systems and identifies root causes. Use\nPROACTIVELY when debugging issues, analyzing logs, or investigating production\nerrors.\n",
+ "description": "- Working on error detective tasks or workflows - Needing guidance, best practices, or checklists for error detective",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-error-analysis",
@@ -3633,7 +4036,8 @@
"name": "error-diagnostics-error-analysis",
"description": "You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-error-trace",
@@ -3642,7 +4046,8 @@
"name": "error-diagnostics-error-trace",
"description": "You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-diagnostics-smart-debug",
@@ -3651,7 +4056,8 @@
"name": "error-diagnostics-smart-debug",
"description": "Use when working with error diagnostics smart debug",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "error-handling-patterns",
@@ -3660,7 +4066,8 @@
"name": "error-handling-patterns",
"description": "Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ethical-hacking-methodology",
@@ -3669,7 +4076,8 @@
"name": "ethical-hacking-methodology",
"description": "This skill should be used when the user asks to \"learn ethical hacking\", \"understand penetration testing lifecycle\", \"perform reconnaissance\", \"conduct security scanning\", \"exploit ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "evaluation",
@@ -3678,7 +4086,8 @@
"name": "evaluation",
"description": "Build evaluation frameworks for agent systems",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/evaluation"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/evaluation",
+ "date_added": "2025-02-26"
},
{
"id": "event-sourcing-architect",
@@ -3687,7 +4096,8 @@
"name": "event-sourcing-architect",
"description": "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "event-store-design",
@@ -3696,7 +4106,8 @@
"name": "event-store-design",
"description": "Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "exa-search",
@@ -3705,7 +4116,8 @@
"name": "exa-search",
"description": "Semantic search, similar content discovery, and structured research using Exa API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "executing-plans",
@@ -3714,7 +4126,8 @@
"name": "executing-plans",
"description": "Use when you have a written implementation plan to execute in a separate session with review checkpoints",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "expo-deployment",
@@ -3723,7 +4136,8 @@
"name": "expo-deployment",
"description": "Deploy Expo apps to production",
"risk": "safe",
- "source": "https://github.com/expo/skills/tree/main/plugins/expo-deployment"
+ "source": "https://github.com/expo/skills/tree/main/plugins/expo-deployment",
+ "date_added": "2025-02-26"
},
{
"id": "fal-audio",
@@ -3732,7 +4146,8 @@
"name": "fal-audio",
"description": "Text-to-speech and speech-to-text using fal.ai audio models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-audio/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-audio/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-generate",
@@ -3741,7 +4156,8 @@
"name": "fal-generate",
"description": "Generate images and videos using fal.ai AI models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-generate/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-generate/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-image-edit",
@@ -3750,7 +4166,8 @@
"name": "fal-image-edit",
"description": "AI-powered image editing with style transfer and object removal",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-image-edit/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-image-edit/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-platform",
@@ -3759,7 +4176,8 @@
"name": "fal-platform",
"description": "Platform APIs for model management, pricing, and usage tracking",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-platform/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-platform/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-upscale",
@@ -3768,7 +4186,8 @@
"name": "fal-upscale",
"description": "Upscale and enhance image and video resolution using AI",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-upscale/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-upscale/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fal-workflow",
@@ -3777,16 +4196,18 @@
"name": "fal-workflow",
"description": "Generate workflow JSON files for chaining AI models",
"risk": "safe",
- "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-workflow/SKILL.md"
+ "source": "https://github.com/fal-ai-community/skills/blob/main/skills/claude.ai/fal-workflow/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-pro",
"path": "skills\\fastapi-pro",
"category": "uncategorized",
"name": "fastapi-pro",
- "description": "Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and\nPydantic V2. Master microservices, WebSockets, and modern Python async\npatterns. Use PROACTIVELY for FastAPI development, async optimization, or API\narchitecture.\n",
+ "description": "- Working on fastapi pro tasks or workflows - Needing guidance, best practices, or checklists for fastapi pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-router-py",
@@ -3795,7 +4216,8 @@
"name": "fastapi-router-py",
"description": "Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or add...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fastapi-templates",
@@ -3804,7 +4226,8 @@
"name": "fastapi-templates",
"description": "Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ffuf-claude-skill",
@@ -3813,7 +4236,8 @@
"name": "ffuf-claude-skill",
"description": "Web fuzzing with ffuf",
"risk": "safe",
- "source": "https://github.com/jthack/ffuf_claude_skill"
+ "source": "https://github.com/jthack/ffuf_claude_skill",
+ "date_added": "2025-02-26"
},
{
"id": "figma-automation",
@@ -3822,7 +4246,8 @@
"name": "figma-automation",
"description": "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-organizer",
@@ -3831,7 +4256,8 @@
"name": "file-organizer",
"description": "Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downlo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-path-traversal",
@@ -3840,7 +4266,8 @@
"name": "file-path-traversal",
"description": "This skill should be used when the user asks to \"test for directory traversal\", \"exploit path traversal vulnerabilities\", \"read arbitrary files through web applications\", \"find LFI vu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "file-uploads",
@@ -3849,7 +4276,8 @@
"name": "file-uploads",
"description": "Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "find-bugs",
@@ -3858,7 +4286,8 @@
"name": "find-bugs",
"description": "Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/find-bugs"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/find-bugs",
+ "date_added": "2025-02-26"
},
{
"id": "finishing-a-development-branch",
@@ -3867,7 +4296,8 @@
"name": "finishing-a-development-branch",
"description": "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "firebase",
@@ -3876,7 +4306,8 @@
"name": "firebase",
"description": "Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they'r...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "firecrawl-scraper",
@@ -3885,16 +4316,18 @@
"name": "firecrawl-scraper",
"description": "Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "firmware-analyst",
"path": "skills\\firmware-analyst",
"category": "uncategorized",
"name": "firmware-analyst",
- "description": "Expert firmware analyst specializing in embedded systems, IoT\nsecurity, and hardware reverse engineering. Masters firmware extraction,\nanalysis, and vulnerability research for routers, IoT devices, automotive\nsystems, and industrial controllers. Use PROACTIVELY for firmware security\naudits, IoT penetration testing, or embedded systems research.\n",
+ "description": "wget http://vendor.com/firmware/update.bin",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fix-review",
@@ -3903,25 +4336,28 @@
"name": "fix-review",
"description": "Verify fix commits address audit findings without new bugs",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/fix-review"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/fix-review",
+ "date_added": "2025-02-26"
},
{
"id": "flutter-expert",
"path": "skills\\flutter-expert",
"category": "uncategorized",
"name": "flutter-expert",
- "description": "Master Flutter development with Dart 3, advanced widgets, and\nmulti-platform deployment. Handles state management, animations, testing, and\nperformance optimization for mobile, web, desktop, and embedded platforms. Use\nPROACTIVELY for Flutter architecture, UI implementation, or cross-platform\nfeatures.\n",
+ "description": "- Working on flutter expert tasks or workflows - Needing guidance, best practices, or checklists for flutter expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "form-cro",
"path": "skills\\form-cro",
"category": "uncategorized",
"name": "form-cro",
- "description": "Optimize any form that is NOT signup or account registration \u2014 including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.\n",
+ "description": "You are an expert in **form optimization and friction reduction**. Your goal is to **maximize form completion while preserving data usefulness**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-errors",
@@ -3930,7 +4366,8 @@
"name": "fp-ts-errors",
"description": "Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-pragmatic",
@@ -3939,7 +4376,8 @@
"name": "fp-ts-pragmatic",
"description": "A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "fp-ts-react",
@@ -3948,7 +4386,8 @@
"name": "fp-ts-react",
"description": "Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.",
"risk": "safe",
- "source": "https://github.com/whatiskadudoing/fp-ts-skills"
+ "source": "https://github.com/whatiskadudoing/fp-ts-skills",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-code-migrate",
@@ -3957,7 +4396,8 @@
"name": "framework-migration-code-migrate",
"description": "You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-deps-upgrade",
@@ -3966,7 +4406,8 @@
"name": "framework-migration-deps-upgrade",
"description": "You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "framework-migration-legacy-modernize",
@@ -3975,7 +4416,8 @@
"name": "framework-migration-legacy-modernize",
"description": "Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "free-tool-strategy",
@@ -3984,7 +4426,8 @@
"name": "free-tool-strategy",
"description": "When the user wants to plan, evaluate, or build a free tool for marketing purposes \u2014 lead generation, SEO value, or brand awareness. Also use when the user mentions \"engineering as mar...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "freshdesk-automation",
@@ -3993,7 +4436,8 @@
"name": "freshdesk-automation",
"description": "Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "freshservice-automation",
@@ -4002,7 +4446,8 @@
"name": "freshservice-automation",
"description": "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-design",
@@ -4011,7 +4456,8 @@
"name": "frontend-design",
"description": "Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-dev-guidelines",
@@ -4020,16 +4466,18 @@
"name": "frontend-dev-guidelines",
"description": "Opinionated frontend development standards for modern React + TypeScript applications. Covers Suspense-first data fetching, lazy loading, feature-based architecture, MUI v7 styling, TanStack Router...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-developer",
"path": "skills\\frontend-developer",
"category": "uncategorized",
"name": "frontend-developer",
- "description": "Build React components, implement responsive layouts, and handle\nclient-side state management. Masters React 19, Next.js 15, and modern\nfrontend architecture. Optimizes performance and ensures accessibility. Use\nPROACTIVELY when creating UI components or fixing frontend issues.\n",
+ "description": "You are a frontend development expert specializing in modern React applications, Next.js, and cutting-edge frontend architecture.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-mobile-development-component-scaffold",
@@ -4038,7 +4486,8 @@
"name": "frontend-mobile-development-component-scaffold",
"description": "You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-mobile-security-xss-scan",
@@ -4047,16 +4496,18 @@
"name": "frontend-mobile-security-xss-scan",
"description": "You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-security-coder",
"path": "skills\\frontend-security-coder",
"category": "uncategorized",
"name": "frontend-security-coder",
- "description": "Expert in secure frontend coding practices specializing in XSS\nprevention, output sanitization, and client-side security patterns. Use\nPROACTIVELY for frontend security implementations or client-side security code\nreviews.\n",
+ "description": "- Working on frontend security coder tasks or workflows - Needing guidance, best practices, or checklists for frontend security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-slides",
@@ -4065,7 +4516,8 @@
"name": "frontend-slides",
"description": "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a...",
"risk": "safe",
- "source": "https://github.com/zarazhangrui/frontend-slides"
+ "source": "https://github.com/zarazhangrui/frontend-slides",
+ "date_added": "2025-02-26"
},
{
"id": "frontend-ui-dark-ts",
@@ -4074,7 +4526,8 @@
"name": "frontend-ui-dark-ts",
"description": "Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "full-stack-orchestration-full-stack-feature",
@@ -4083,7 +4536,8 @@
"name": "full-stack-orchestration-full-stack-feature",
"description": "Use when working with full stack orchestration full stack feature",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-art",
@@ -4092,7 +4546,8 @@
"name": "game-art",
"description": "Game art principles. Visual style selection, asset pipeline, animation workflow.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-audio",
@@ -4101,7 +4556,8 @@
"name": "game-audio",
"description": "Game audio principles. Sound design, music integration, adaptive audio systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-design",
@@ -4110,7 +4566,8 @@
"name": "game-design",
"description": "Game design principles. GDD structure, balancing, player psychology, progression.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "game-development",
@@ -4119,7 +4576,8 @@
"name": "game-development",
"description": "Game development orchestrator. Routes to platform-specific skills based on project needs.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gcp-cloud-run",
@@ -4128,7 +4586,8 @@
"name": "gcp-cloud-run",
"description": "Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-dri...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "gdpr-data-handling",
@@ -4137,7 +4596,8 @@
"name": "gdpr-data-handling",
"description": "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, o...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gemini-api-dev",
@@ -4146,7 +4606,8 @@
"name": "gemini-api-dev",
"description": "Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or n...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "geo-fundamentals",
@@ -4155,7 +4616,8 @@
"name": "geo-fundamentals",
"description": "Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-advanced-workflows",
@@ -4164,7 +4626,8 @@
"name": "git-advanced-workflows",
"description": "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, co...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-git-workflow",
@@ -4173,7 +4636,8 @@
"name": "git-pr-workflows-git-workflow",
"description": "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-onboard",
@@ -4182,7 +4646,8 @@
"name": "git-pr-workflows-onboard",
"description": "You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pr-workflows-pr-enhance",
@@ -4191,7 +4656,8 @@
"name": "git-pr-workflows-pr-enhance",
"description": "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "git-pushing",
@@ -4200,7 +4666,8 @@
"name": "git-pushing",
"description": "Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activate...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-actions-templates",
@@ -4209,7 +4676,8 @@
"name": "github-actions-templates",
"description": "Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or cre...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-automation",
@@ -4218,7 +4686,8 @@
"name": "github-automation",
"description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-issue-creator",
@@ -4227,7 +4696,8 @@
"name": "github-issue-creator",
"description": "Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "github-workflow-automation",
@@ -4236,7 +4706,8 @@
"name": "github-workflow-automation",
"description": "Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitlab-automation",
@@ -4245,7 +4716,8 @@
"name": "gitlab-automation",
"description": "Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitlab-ci-patterns",
@@ -4254,7 +4726,8 @@
"name": "gitlab-ci-patterns",
"description": "Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gitops-workflow",
@@ -4263,7 +4736,8 @@
"name": "gitops-workflow",
"description": "Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deplo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "gmail-automation",
@@ -4272,7 +4746,8 @@
"name": "gmail-automation",
"description": "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "go-concurrency-patterns",
@@ -4281,7 +4756,8 @@
"name": "go-concurrency-patterns",
"description": "Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "go-playwright",
@@ -4290,7 +4766,8 @@
"name": "go-playwright",
"description": "Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.",
"risk": "safe",
- "source": "https://github.com/playwright-community/playwright-go"
+ "source": "https://github.com/playwright-community/playwright-go",
+ "date_added": "2025-02-26"
},
{
"id": "go-rod-master",
@@ -4299,7 +4776,8 @@
"name": "go-rod-master",
"description": "Comprehensive guide for browser automation and web scraping with go-rod (Chrome DevTools Protocol) including stealth anti-bot-detection patterns.",
"risk": "safe",
- "source": "https://github.com/go-rod/rod"
+ "source": "https://github.com/go-rod/rod",
+ "date_added": "2025-02-26"
},
{
"id": "godot-4-migration",
@@ -4308,7 +4786,8 @@
"name": "godot-4-migration",
"description": "Specialized guide for migrating Godot 3.x projects to Godot 4 (GDScript 2.0), covering syntax changes, Tweens, and exports.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "godot-gdscript-patterns",
@@ -4317,16 +4796,18 @@
"name": "godot-gdscript-patterns",
"description": "Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "golang-pro",
"path": "skills\\golang-pro",
"category": "uncategorized",
"name": "golang-pro",
- "description": "Master Go 1.21+ with modern patterns, advanced concurrency,\nperformance optimization, and production-ready microservices. Expert in the\nlatest Go ecosystem including generics, workspaces, and cutting-edge\nframeworks. Use PROACTIVELY for Go development, architecture design, or\nperformance optimization.\n",
+ "description": "You are a Go expert specializing in modern Go 1.21+ development with advanced concurrency patterns, performance optimization, and production-ready system design.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-analytics-automation",
@@ -4335,7 +4816,8 @@
"name": "google-analytics-automation",
"description": "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-calendar-automation",
@@ -4344,7 +4826,8 @@
"name": "google-calendar-automation",
"description": "Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatica...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "google-drive-automation",
@@ -4353,7 +4836,8 @@
"name": "google-drive-automation",
"description": "Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives pr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "googlesheets-automation",
@@ -4362,7 +4846,8 @@
"name": "googlesheets-automation",
"description": "Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "grafana-dashboards",
@@ -4371,7 +4856,8 @@
"name": "grafana-dashboards",
"description": "Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "graphql",
@@ -4380,16 +4866,18 @@
"name": "graphql",
"description": "GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper co...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "graphql-architect",
"path": "skills\\graphql-architect",
"category": "uncategorized",
"name": "graphql-architect",
- "description": "Master modern GraphQL with federation, performance optimization,\nand enterprise security. Build scalable schemas, implement advanced caching,\nand design real-time systems. Use PROACTIVELY for GraphQL architecture or\nperformance optimization.\n",
+ "description": "- Working on graphql architect tasks or workflows - Needing guidance, best practices, or checklists for graphql architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "grpc-golang",
@@ -4398,16 +4886,18 @@
"name": "grpc-golang",
"description": "Build production-ready gRPC services in Go with mTLS, streaming, and observability. Use when designing Protobuf contracts with Buf or implementing secure service-to-service transport.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "haskell-pro",
"path": "skills\\haskell-pro",
"category": "uncategorized",
"name": "haskell-pro",
- "description": "Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.",
+ "description": "Expert Haskell engineer specializing in advanced type systems, pure",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "helm-chart-scaffolding",
@@ -4416,7 +4906,8 @@
"name": "helm-chart-scaffolding",
"description": "Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or impl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "helpdesk-automation",
@@ -4425,133 +4916,148 @@
"name": "helpdesk-automation",
"description": "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-content",
"path": "skills\\hig-components-content",
"category": "uncategorized",
"name": "hig-components-content",
- "description": "Apple Human Interface Guidelines for content display components. Use this skill when the user asks about \"charts component\", \"collection view\", \"image view\", \"web view\", \"color well\", \"image well\", \"activity view\", \"lockup\", \"data visualization\", \"content display\", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says \"how should I display charts\", \"what's the best way to show images\", \"should I use a web view\", \"how do I build a grid of items\", \"what component shows media\", or \"how do I present a share sheet\". Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-controls",
"path": "skills\\hig-components-controls",
"category": "uncategorized",
"name": "hig-components-controls",
- "description": "Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says \"picker or segmented control,\" \"how should my form look,\" \"what keyboard type should I use,\" \"toggle vs checkbox,\" or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. Cross-references: hig-components-menus, hig-components-dialogs, hig-components-search.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-dialogs",
"path": "skills\\hig-components-dialogs",
"category": "uncategorized",
"name": "hig-components-dialogs",
- "description": "Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says \"should I use an alert or a sheet,\" \"how do I show a confirmation dialog,\" \"when should I use a popover,\" \"my modals are annoying users,\" or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, destructive action confirmation, or overlay UI patterns. Cross-references: hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-layout",
"path": "skills\\hig-components-layout",
"category": "uncategorized",
"name": "hig-components-layout",
- "description": "Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about \"sidebar\", \"split view\", \"tab bar\", \"tab view\", \"scroll view\", \"window design\", \"panel\", \"list view\", \"table view\", \"column view\", \"outline view\", \"navigation structure\", \"app layout\", \"boxes\", \"ornaments\", or organizing content hierarchically in Apple apps. Also use when the user says \"how should I organize my app\", \"what navigation pattern should I use\", \"my layout breaks on iPad\", \"how do I build a sidebar\", \"should I use tabs or a sidebar\", or \"my app doesn't adapt to different screen sizes\". Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-menus",
"path": "skills\\hig-components-menus",
"category": "uncategorized",
"name": "hig-components-menus",
- "description": "Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure controls, and standard buttons. Use this skill when the user says \"how should my buttons look,\" \"what goes in the menu bar,\" \"should I use a context menu or action sheet,\" \"how do I design a toolbar,\" or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit menu, or any menu/button component layout and behavior. Cross-references: hig-components-search, hig-components-controls, hig-components-dialogs.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-search",
"path": "skills\\hig-components-search",
"category": "uncategorized",
"name": "hig-components-search",
- "description": "Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill when the user says \"how should search work in my app,\" \"I need a breadcrumb,\" \"how do I paginate content,\" or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-status",
"path": "skills\\hig-components-status",
"category": "uncategorized",
"name": "hig-components-status",
- "description": "Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: \"progress indicator\", \"progress bar\", \"loading spinner\", \"status bar\", \"activity ring\", \"progress display\", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says \"how do I show loading state,\" \"should I use a spinner or progress bar,\" \"what goes in the status bar,\" or asks about activity indicators. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-components-system",
"path": "skills\\hig-components-system",
"category": "uncategorized",
"name": "hig-components-system",
- "description": "Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts. Use when asked about: \"widget design\", \"live activity\", \"notification design\", \"complication\", \"home screen quick action\", \"top shelf\", \"watch face\", \"app clip\", \"app shortcut\", \"system experience\". Also use when the user says \"how do I design a widget,\" \"what should my notification look like,\" \"how do Live Activities work,\" \"should I make an App Clip,\" or asks about surfaces outside the main app. Cross-references: hig-components-status for progress in widgets, hig-inputs for interaction patterns, hig-technologies for Siri and system integration.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-foundations",
"path": "skills\\hig-foundations",
"category": "uncategorized",
"name": "hig-foundations",
- "description": "Apple Human Interface Guidelines design foundations. Use this skill when the user asks about \"HIG color\", \"Apple typography\", \"SF Symbols\", \"dark mode guidelines\", \"accessible design\", \"Apple design foundations\", \"app icon\", \"layout guidelines\", \"materials\", \"motion\", \"privacy\", \"right to left\", \"RTL\", \"inclusive design\", branding, images, spatial layout, or writing style. Also use when the user says \"my colors look wrong in dark mode\", \"what font should I use\", \"is my app accessible enough\", \"how do I support Dynamic Type\", \"what contrast ratio do I need\", \"how do I pick system colors\", or \"my icons don't match the system style\". Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction patterns, hig-components-layout for structural components, hig-components-content for display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-inputs",
"path": "skills\\hig-inputs",
"category": "uncategorized",
"name": "hig-inputs",
- "description": "Apple HIG guidance for input methods and interaction patterns: gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. Use when asked about: \"gesture design\", \"Apple Pencil\", \"keyboard shortcuts\", \"game controller\", \"pointer support\", \"mouse support\", \"trackpad\", \"Digital Crown\", \"eye tracking\", \"visionOS input\", \"focus system\", \"remote control\", \"gyroscope\", \"spatial interaction\". Also use when the user says \"what gestures should I support,\" \"how do I add keyboard shortcuts,\" \"how does input work on Apple TV,\" \"should I support Apple Pencil,\" or asks about input device handling. Cross-references: hig-components-status, hig-components-system, hig-technologies for VoiceOver and Siri.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-patterns",
"path": "skills\\hig-patterns",
"category": "uncategorized",
"name": "hig-patterns",
- "description": "Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about \"onboarding flow\", \"user onboarding\", \"app launch\", \"loading state\", \"drag and drop\", \"search pattern\", \"settings design\", \"notifications\", \"modality\", \"multitasking\", \"feedback pattern\", \"haptics\", \"undo redo\", \"file management\", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says \"how should onboarding work\", \"my app takes too long to load\", \"should I use a modal here\", \"how do I handle errors\", \"when should I ask for permissions\", \"how to show progress\", or \"what's the right way to confirm a delete\". Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics, hig-components-layout for navigation, hig-components-content for data display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-platforms",
"path": "skills\\hig-platforms",
"category": "uncategorized",
"name": "hig-platforms",
- "description": "Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about \"designing for iOS\", \"iPad app design\", \"macOS design\", \"tvOS\", \"visionOS\", \"watchOS\", \"Apple platform\", \"which platform\", platform differences, platform-specific conventions, or multi-platform app design. Also use when the user says \"should I design differently for iPad vs iPhone\", \"how does my app work on visionOS\", \"what's different about macOS apps\", \"porting my app to another platform\", \"universal app design\", or \"what input methods does this platform use\". Cross-references: hig-foundations for shared design foundations, hig-patterns for interaction patterns, hig-components-layout for navigation structures, hig-components-content for content display.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-project-context",
"path": "skills\\hig-project-context",
"category": "uncategorized",
"name": "hig-project-context",
- "description": "Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says \"set up my project context,\" \"what platforms am I targeting,\" \"configure HIG settings,\" or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.",
+ "description": "Create and maintain `.claude/apple-design-context.md` so other HIG skills can skip redundant questions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hig-technologies",
"path": "skills\\hig-technologies",
"category": "uncategorized",
"name": "hig-technologies",
- "description": "Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: \"Siri integration\", \"Apple Pay\", \"HealthKit\", \"HomeKit\", \"ARKit\", \"augmented reality\", \"machine learning\", \"generative AI\", \"iCloud sync\", \"Sign in with Apple\", \"SharePlay\", \"CarPlay\", \"in-app purchase\", \"NFC\", \"VoiceOver\", \"Maps\", \"Mac Catalyst\". Also use when the user says \"how do I integrate Siri,\" \"what are the Apple Pay guidelines,\" \"how should my AR experience work,\" \"how do I use Sign in with Apple,\" or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.\n",
+ "description": "Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hosted-agents-v2-py",
@@ -4560,16 +5066,18 @@
"name": "hosted-agents-v2-py",
"description": "Build hosted agents using Azure AI Projects SDK with ImageBasedHostedAgentDefinition. Use when creating container-based agents in Azure AI Foundry.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hr-pro",
"path": "skills\\hr-pro",
"category": "uncategorized",
"name": "hr-pro",
- "description": "Professional, ethical HR partner for hiring,\nonboarding/offboarding, PTO and leave, performance, compliant policies, and\nemployee relations. Ask for jurisdiction and company context before advising;\nproduce structured, bias-mitigated, lawful templates.\n",
+ "description": "- Working on hr pro tasks or workflows - Needing guidance, best practices, or checklists for hr pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "html-injection-testing",
@@ -4578,7 +5086,8 @@
"name": "html-injection-testing",
"description": "This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test conten...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hubspot-automation",
@@ -4587,7 +5096,8 @@
"name": "hubspot-automation",
"description": "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hubspot-integration",
@@ -4596,7 +5106,8 @@
"name": "hubspot-integration",
"description": "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubs...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "hugging-face-cli",
@@ -4605,7 +5116,8 @@
"name": "hugging-face-cli",
"description": "Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...",
"risk": "safe",
- "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli"
+ "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-cli",
+ "date_added": "2025-02-26"
},
{
"id": "hugging-face-jobs",
@@ -4614,16 +5126,18 @@
"name": "hugging-face-jobs",
"description": "This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tok...",
"risk": "safe",
- "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs"
+ "source": "https://github.com/huggingface/skills/tree/main/skills/hugging-face-jobs",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-cloud-architect",
"path": "skills\\hybrid-cloud-architect",
"category": "uncategorized",
"name": "hybrid-cloud-architect",
- "description": "Expert hybrid cloud architect specializing in complex multi-cloud\nsolutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters\nhybrid connectivity, workload placement optimization, edge computing, and\ncross-cloud automation. Handles compliance, cost optimization, disaster\nrecovery, and migration strategies. Use PROACTIVELY for hybrid architecture,\nmulti-cloud strategy, or complex infrastructure integration.\n",
+ "description": "- Working on hybrid cloud architect tasks or workflows - Needing guidance, best practices, or checklists for hybrid cloud architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-cloud-networking",
@@ -4632,7 +5146,8 @@
"name": "hybrid-cloud-networking",
"description": "Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "hybrid-search-implementation",
@@ -4641,7 +5156,8 @@
"name": "hybrid-search-implementation",
"description": "Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "i18n-localization",
@@ -4650,7 +5166,8 @@
"name": "i18n-localization",
"description": "Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "idor-testing",
@@ -4659,7 +5176,8 @@
"name": "idor-testing",
"description": "This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or obje...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "imagen",
@@ -4668,7 +5186,8 @@
"name": "imagen",
"description": "This skill generates images using Google Gemini's image generation model (`gemini-3-pro-image-preview`). It enables seamless image creation during any Claude Code session - whether you're building frontend UIs, creating documentation, or need visual",
"risk": "safe",
- "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen"
+ "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/imagen",
+ "date_added": "2025-02-26"
},
{
"id": "impress",
@@ -4677,16 +5196,18 @@
"name": "impress",
"description": "Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "incident-responder",
"path": "skills\\incident-responder",
"category": "uncategorized",
"name": "incident-responder",
- "description": "Expert SRE incident responder specializing in rapid problem\nresolution, modern observability, and comprehensive incident management.\nMasters incident command, blameless post-mortems, error budget management, and\nsystem reliability patterns. Handles critical outages, communication\nstrategies, and continuous improvement. Use IMMEDIATELY for production\nincidents or SRE practices.\n",
+ "description": "- Working on incident responder tasks or workflows - Needing guidance, best practices, or checklists for incident responder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-response-incident-response",
@@ -4695,7 +5216,8 @@
"name": "incident-response-incident-response",
"description": "Use when working with incident response incident response",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-response-smart-fix",
@@ -4704,7 +5226,8 @@
"name": "incident-response-smart-fix",
"description": "[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "incident-runbook-templates",
@@ -4713,7 +5236,8 @@
"name": "incident-runbook-templates",
"description": "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "infinite-gratitude",
@@ -4722,7 +5246,8 @@
"name": "infinite-gratitude",
"description": "Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).",
"risk": "safe",
- "source": "https://github.com/sstklen/infinite-gratitude"
+ "source": "https://github.com/sstklen/infinite-gratitude",
+ "date_added": "2025-02-26"
},
{
"id": "inngest",
@@ -4731,7 +5256,8 @@
"name": "inngest",
"description": "Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "instagram-automation",
@@ -4740,7 +5266,8 @@
"name": "instagram-automation",
"description": "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "interactive-portfolio",
@@ -4749,7 +5276,8 @@
"name": "interactive-portfolio",
"description": "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios,...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "intercom-automation",
@@ -4758,7 +5286,8 @@
"name": "intercom-automation",
"description": "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "internal-comms-anthropic",
@@ -4767,7 +5296,8 @@
"name": "internal-comms-anthropic",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "internal-comms-community",
@@ -4776,25 +5306,28 @@
"name": "internal-comms-community",
"description": "A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "inventory-demand-planning",
"path": "skills\\inventory-demand-planning",
"category": "uncategorized",
"name": "inventory-demand-planning",
- "description": "Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimising inventory levels.\n",
+ "description": "Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "ios-developer",
"path": "skills\\ios-developer",
"category": "uncategorized",
"name": "ios-developer",
- "description": "Develop native iOS applications with Swift/SwiftUI. Masters iOS 18,\nSwiftUI, UIKit integration, Core Data, networking, and App Store optimization.\nUse PROACTIVELY for iOS-specific features, App Store optimization, or native\niOS development.\n",
+ "description": "- Working on ios developer tasks or workflows - Needing guidance, best practices, or checklists for ios developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "istio-traffic-management",
@@ -4803,7 +5336,8 @@
"name": "istio-traffic-management",
"description": "Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilie...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "iterate-pr",
@@ -4812,16 +5346,18 @@
"name": "iterate-pr",
"description": "Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.",
"risk": "safe",
- "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/iterate-pr"
+ "source": "https://github.com/getsentry/skills/tree/main/plugins/sentry-skills/skills/iterate-pr",
+ "date_added": "2025-02-26"
},
{
"id": "java-pro",
"path": "skills\\java-pro",
"category": "uncategorized",
"name": "java-pro",
- "description": "Master Java 21+ with modern features like virtual threads, pattern\nmatching, and Spring Boot 3.x. Expert in the latest Java ecosystem including\nGraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java\ndevelopment, microservices architecture, or performance optimization.\n",
+ "description": "- Working on java pro tasks or workflows - Needing guidance, best practices, or checklists for java pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-mastery",
@@ -4830,16 +5366,18 @@
"name": "javascript-mastery",
"description": "Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-pro",
"path": "skills\\javascript-pro",
"category": "uncategorized",
"name": "javascript-pro",
- "description": "Master modern JavaScript with ES6+, async patterns, and Node.js\nAPIs. Handles promises, event loops, and browser/Node compatibility. Use\nPROACTIVELY for JavaScript optimization, async debugging, or complex JS\npatterns.\n",
+ "description": "You are a JavaScript expert specializing in modern JS and async programming.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-testing-patterns",
@@ -4848,7 +5386,8 @@
"name": "javascript-testing-patterns",
"description": "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "javascript-typescript-typescript-scaffold",
@@ -4857,7 +5396,8 @@
"name": "javascript-typescript-typescript-scaffold",
"description": "You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "jira-automation",
@@ -4866,16 +5406,18 @@
"name": "jira-automation",
"description": "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "julia-pro",
"path": "skills\\julia-pro",
"category": "uncategorized",
"name": "julia-pro",
- "description": "Master Julia 1.10+ with modern features, performance optimization,\nmultiple dispatch, and production-ready practices. Expert in the Julia\necosystem including package management, scientific computing, and\nhigh-performance numerical code. Use PROACTIVELY for Julia development,\noptimization, or advanced Julia patterns.\n",
+ "description": "- Working on julia pro tasks or workflows - Needing guidance, best practices, or checklists for julia pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "k8s-manifest-generator",
@@ -4884,7 +5426,8 @@
"name": "k8s-manifest-generator",
"description": "Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "k8s-security-policies",
@@ -4893,7 +5436,8 @@
"name": "k8s-security-policies",
"description": "Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kaizen",
@@ -4902,7 +5446,8 @@
"name": "kaizen",
"description": "Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "klaviyo-automation",
@@ -4911,7 +5456,8 @@
"name": "klaviyo-automation",
"description": "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kotlin-coroutines-expert",
@@ -4920,7 +5466,8 @@
"name": "kotlin-coroutines-expert",
"description": "Expert patterns for Kotlin Coroutines and Flow, covering structured concurrency, error handling, and testing.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kpi-dashboard-design",
@@ -4929,16 +5476,18 @@
"name": "kpi-dashboard-design",
"description": "Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kubernetes-architect",
"path": "skills\\kubernetes-architect",
"category": "uncategorized",
"name": "kubernetes-architect",
- "description": "Expert Kubernetes architect specializing in cloud-native\ninfrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise\ncontainer orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd),\nprogressive delivery, multi-tenancy, and platform engineering. Handles\nsecurity, observability, cost optimization, and developer experience. Use\nPROACTIVELY for K8s architecture, GitOps implementation, or cloud-native\nplatform design.\n",
+ "description": "You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "kubernetes-deployment",
@@ -4947,7 +5496,8 @@
"name": "kubernetes-deployment",
"description": "Kubernetes deployment workflow for container orchestration, Helm charts, service mesh, and production-ready K8s configurations.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "langchain-architecture",
@@ -4956,7 +5506,8 @@
"name": "langchain-architecture",
"description": "Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM w...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "langfuse",
@@ -4965,7 +5516,8 @@
"name": "langfuse",
"description": "Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debug...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "langgraph",
@@ -4974,7 +5526,8 @@
"name": "langgraph",
"description": "Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "laravel-expert",
@@ -4983,7 +5536,8 @@
"name": "laravel-expert",
"description": "Senior Laravel Engineer role for production-grade, maintainable, and idiomatic Laravel solutions. Focuses on clean architecture, security, performance, and modern standards (Laravel 10/11+).",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "laravel-security-audit",
@@ -4992,7 +5546,8 @@
"name": "laravel-security-audit",
"description": "Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "last30days",
@@ -5001,7 +5556,8 @@
"name": "last30days",
"description": "Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "launch-strategy",
@@ -5010,25 +5566,28 @@
"name": "launch-strategy",
"description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,'...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "legacy-modernizer",
"path": "skills\\legacy-modernizer",
"category": "uncategorized",
"name": "legacy-modernizer",
- "description": "Refactor legacy codebases, migrate outdated frameworks, and\nimplement gradual modernization. Handles technical debt, dependency updates,\nand backward compatibility. Use PROACTIVELY for legacy system updates,\nframework migrations, or technical debt reduction.\n",
+ "description": "- Working on legacy modernizer tasks or workflows - Needing guidance, best practices, or checklists for legacy modernizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "legal-advisor",
"path": "skills\\legal-advisor",
"category": "uncategorized",
"name": "legal-advisor",
- "description": "Draft privacy policies, terms of service, disclaimers, and legal\nnotices. Creates GDPR-compliant texts, cookie policies, and data processing\nagreements. Use PROACTIVELY for legal documentation, compliance texts, or\nregulatory requirements.\n",
+ "description": "- Working on legal advisor tasks or workflows - Needing guidance, best practices, or checklists for legal advisor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linear-automation",
@@ -5037,7 +5596,8 @@
"name": "linear-automation",
"description": "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linear-claude-skill",
@@ -5046,7 +5606,8 @@
"name": "linear-claude-skill",
"description": "Manage Linear issues, projects, and teams",
"risk": "safe",
- "source": "https://github.com/wrsmith108/linear-claude-skill"
+ "source": "https://github.com/wrsmith108/linear-claude-skill",
+ "date_added": "2025-02-26"
},
{
"id": "linkedin-automation",
@@ -5055,7 +5616,8 @@
"name": "linkedin-automation",
"description": "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linkedin-cli",
@@ -5064,7 +5626,8 @@
"name": "linkedin-cli",
"description": "Use when automating LinkedIn via CLI: fetch profiles, search people/companies, send messages, manage connections, create posts, and Sales Navigator.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linkerd-patterns",
@@ -5073,7 +5636,8 @@
"name": "linkerd-patterns",
"description": "Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "lint-and-validate",
@@ -5082,7 +5646,8 @@
"name": "lint-and-validate",
"description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, v...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-privilege-escalation",
@@ -5091,7 +5656,8 @@
"name": "linux-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Linux\", \"find privesc vectors on Linux systems\", \"exploit sudo misconfigurations\", \"abuse SUID binaries\", \"ex...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-shell-scripting",
@@ -5100,7 +5666,8 @@
"name": "linux-shell-scripting",
"description": "This skill should be used when the user asks to \"create bash scripts\", \"automate Linux tasks\", \"monitor system resources\", \"backup files\", \"manage users\", or \"write production she...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "linux-troubleshooting",
@@ -5109,7 +5676,8 @@
"name": "linux-troubleshooting",
"description": "Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "llm-app-patterns",
@@ -5118,7 +5686,8 @@
"name": "llm-app-patterns",
"description": "Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, buildin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-ai-assistant",
@@ -5127,7 +5696,8 @@
"name": "llm-application-dev-ai-assistant",
"description": "You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natur",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-langchain-agent",
@@ -5136,7 +5706,8 @@
"name": "llm-application-dev-langchain-agent",
"description": "You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-application-dev-prompt-optimize",
@@ -5145,7 +5716,8 @@
"name": "llm-application-dev-prompt-optimize",
"description": "You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "llm-evaluation",
@@ -5154,16 +5726,18 @@
"name": "llm-evaluation",
"description": "Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "logistics-exception-management",
"path": "skills\\logistics-exception-management",
"category": "uncategorized",
"name": "logistics-exception-management",
- "description": "Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviours, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.\n",
+ "description": "Use this skill when dealing with deviations from planned logistics operations, such as transit delays, damaged shipments, lost cargo, or when initiating and managing claims and disputes with freight carriers.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "loki-mode",
@@ -5172,34 +5746,38 @@
"name": "loki-mode",
"description": "Multi-agent autonomous startup system for Claude Code. Triggers on \"Loki Mode\". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-dotnet",
"path": "skills\\m365-agents-dotnet",
"category": "uncategorized",
"name": "m365-agents-dotnet",
- "description": "Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"Microsoft.Agents\", \"AddAgentApplicationOptions\", \"AgentApplication\", \"AddAgentAspNetAuthentication\", \"Copilot Studio client\", \"IAgentHttpAdapter\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft.Agents SDK with ASP.NET Core hosting, agent routing, and MSAL-based authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-py",
"path": "skills\\m365-agents-py",
"category": "uncategorized",
"name": "m365-agents-py",
- "description": "Microsoft 365 Agents SDK for Python. Build multichannel agents for Teams/M365/Copilot Studio with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based auth. Triggers: \"Microsoft 365 Agents SDK\", \"microsoft_agents\", \"AgentApplication\", \"start_agent_process\", \"TurnContext\", \"Copilot Studio client\", \"CloudAdapter\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft Agents SDK with aiohttp hosting, AgentApplication routing, streaming responses, and MSAL-based authentication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "m365-agents-ts",
"path": "skills\\m365-agents-ts",
"category": "uncategorized",
"name": "m365-agents-ts",
- "description": "Microsoft 365 Agents SDK for TypeScript/Node.js. Build multichannel agents for Teams/M365/Copilot Studio with AgentApplication routing, Express hosting, streaming responses, and Copilot Studio client integration. Triggers: \"Microsoft 365 Agents SDK\", \"@microsoft/agents-hosting\", \"AgentApplication\", \"startServer\", \"streamingResponse\", \"Copilot Studio client\", \"@microsoft/agents-copilotstudio-client\".\n",
+ "description": "Build enterprise agents for Microsoft 365, Teams, and Copilot Studio using the Microsoft 365 Agents SDK with Express hosting, AgentApplication routing, streaming responses, and Copilot Studio client integrations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "machine-learning-ops-ml-pipeline",
@@ -5208,7 +5786,8 @@
"name": "machine-learning-ops-ml-pipeline",
"description": "Design and implement a complete ML pipeline for: $ARGUMENTS",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mailchimp-automation",
@@ -5217,7 +5796,8 @@
"name": "mailchimp-automation",
"description": "Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "make-automation",
@@ -5226,7 +5806,8 @@
"name": "make-automation",
"description": "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "makepad-skills",
@@ -5235,16 +5816,18 @@
"name": "makepad-skills",
"description": "Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.",
"risk": "safe",
- "source": "https://github.com/ZhangHanDong/makepad-skills"
+ "source": "https://github.com/ZhangHanDong/makepad-skills",
+ "date_added": "2025-02-26"
},
{
"id": "malware-analyst",
"path": "skills\\malware-analyst",
"category": "uncategorized",
"name": "malware-analyst",
- "description": "Expert malware analyst specializing in defensive malware research,\nthreat intelligence, and incident response. Masters sandbox analysis,\nbehavioral analysis, and malware family identification. Handles static/dynamic\nanalysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage,\nthreat hunting, incident response, or security research.\n",
+ "description": "file sample.exe sha256sum sample.exe",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "manifest",
@@ -5253,16 +5836,18 @@
"name": "manifest",
"description": "Install and configure the Manifest observability plugin for your agents. Use when setting up telemetry, configuring API keys, or troubleshooting the plugin.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "market-sizing-analysis",
"path": "skills\\market-sizing-analysis",
"category": "uncategorized",
"name": "market-sizing-analysis",
- "description": "This skill should be used when the user asks to \\\\\\\"calculate TAM\\\\\\\",\n\"determine SAM\", \"estimate SOM\", \"size the market\", \"calculate market\nopportunity\", \"what's the total addressable market\", or requests market sizing\nanalysis for a startup or business opportunity.\n",
+ "description": "Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) for startup opportunities.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "marketing-ideas",
@@ -5271,7 +5856,8 @@
"name": "marketing-ideas",
"description": "Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "marketing-psychology",
@@ -5280,7 +5866,8 @@
"name": "marketing-psychology",
"description": "Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mcp-builder",
@@ -5289,7 +5876,8 @@
"name": "mcp-builder",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mcp-builder-ms",
@@ -5298,7 +5886,8 @@
"name": "mcp-builder-ms",
"description": "Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate exte...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-forensics",
@@ -5307,7 +5896,8 @@
"name": "memory-forensics",
"description": "Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-safety-patterns",
@@ -5316,7 +5906,8 @@
"name": "memory-safety-patterns",
"description": "Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "memory-systems",
@@ -5325,16 +5916,18 @@
"name": "memory-systems",
"description": "Design short-term, long-term, and graph-based memory architectures",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/memory-systems"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/memory-systems",
+ "date_added": "2025-02-26"
},
{
"id": "mermaid-expert",
"path": "skills\\mermaid-expert",
"category": "uncategorized",
"name": "mermaid-expert",
- "description": "Create Mermaid diagrams for flowcharts, sequences, ERDs, and\narchitectures. Masters syntax for all diagram types and styling. Use\nPROACTIVELY for visual documentation, system diagrams, or process flows.\n",
+ "description": "- Working on mermaid expert tasks or workflows - Needing guidance, best practices, or checklists for mermaid expert",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "metasploit-framework",
@@ -5343,7 +5936,8 @@
"name": "metasploit-framework",
"description": "This skill should be used when the user asks to \"use Metasploit for penetration testing\", \"exploit vulnerabilities with msfconsole\", \"create payloads with msfvenom\", \"perform post-exp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "micro-saas-launcher",
@@ -5352,7 +5946,8 @@
"name": "micro-saas-launcher",
"description": "Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing t...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "microservices-patterns",
@@ -5361,16 +5956,18 @@
"name": "microservices-patterns",
"description": "Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"path": "skills\\microsoft-azure-webjobs-extensions-authentication-events-dotnet",
"category": "uncategorized",
"name": "microsoft-azure-webjobs-extensions-authentication-events-dotnet",
- "description": "Microsoft Entra Authentication Events SDK for .NET. Azure Functions triggers for custom authentication extensions. Use for token enrichment, custom claims, attribute collection, and OTP customization in Entra ID. Triggers: \"Authentication Events\", \"WebJobsAuthenticationEventsTrigger\", \"OnTokenIssuanceStart\", \"OnAttributeCollectionStart\", \"custom claims\", \"token enrichment\", \"Entra custom extension\", \"authentication extension\".\n",
+ "description": "Azure Functions extension for handling Microsoft Entra ID custom authentication events.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "microsoft-teams-automation",
@@ -5379,16 +5976,18 @@
"name": "microsoft-teams-automation",
"description": "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "minecraft-bukkit-pro",
"path": "skills\\minecraft-bukkit-pro",
"category": "uncategorized",
"name": "minecraft-bukkit-pro",
- "description": "Master Minecraft server plugin development with Bukkit, Spigot, and\nPaper APIs. Specializes in event-driven architecture, command systems, world\nmanipulation, player management, and performance optimization. Use PROACTIVELY\nfor plugin architecture, gameplay mechanics, server-side features, or\ncross-version compatibility.\n",
+ "description": "- Working on minecraft bukkit pro tasks or workflows - Needing guidance, best practices, or checklists for minecraft bukkit pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "miro-automation",
@@ -5397,7 +5996,8 @@
"name": "miro-automation",
"description": "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mixpanel-automation",
@@ -5406,16 +6006,18 @@
"name": "mixpanel-automation",
"description": "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ml-engineer",
"path": "skills\\ml-engineer",
"category": "uncategorized",
"name": "ml-engineer",
- "description": "Build production ML systems with PyTorch 2.x, TensorFlow, and\nmodern ML frameworks. Implements model serving, feature engineering, A/B\ntesting, and monitoring. Use PROACTIVELY for ML model deployment, inference\noptimization, or production ML infrastructure.\n",
+ "description": "- Working on ml engineer tasks or workflows - Needing guidance, best practices, or checklists for ml engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ml-pipeline-workflow",
@@ -5424,16 +6026,18 @@
"name": "ml-pipeline-workflow",
"description": "Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating mod...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mlops-engineer",
"path": "skills\\mlops-engineer",
"category": "uncategorized",
"name": "mlops-engineer",
- "description": "Build comprehensive ML pipelines, experiment tracking, and model\nregistries with MLflow, Kubeflow, and modern MLOps tools. Implements automated\ntraining, deployment, and monitoring across cloud platforms. Use PROACTIVELY\nfor ML infrastructure, experiment management, or pipeline automation.\n",
+ "description": "- Working on mlops engineer tasks or workflows - Needing guidance, best practices, or checklists for mlops engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-design",
@@ -5442,16 +6046,18 @@
"name": "mobile-design",
"description": "Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-developer",
"path": "skills\\mobile-developer",
"category": "uncategorized",
"name": "mobile-developer",
- "description": "Develop React Native, Flutter, or native mobile apps with modern\narchitecture patterns. Masters cross-platform development, native\nintegrations, offline sync, and app store optimization. Use PROACTIVELY for\nmobile features, cross-platform code, or app optimization.\n",
+ "description": "- Working on mobile developer tasks or workflows - Needing guidance, best practices, or checklists for mobile developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-games",
@@ -5460,16 +6066,18 @@
"name": "mobile-games",
"description": "Mobile game development principles. Touch input, battery, performance, app stores.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mobile-security-coder",
"path": "skills\\mobile-security-coder",
"category": "uncategorized",
"name": "mobile-security-coder",
- "description": "Expert in secure mobile coding practices specializing in input\nvalidation, WebView security, and mobile-specific security patterns. Use\nPROACTIVELY for mobile security implementations or mobile security code\nreviews.\n",
+ "description": "- Working on mobile security coder tasks or workflows - Needing guidance, best practices, or checklists for mobile security coder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "modern-javascript-patterns",
@@ -5478,7 +6086,8 @@
"name": "modern-javascript-patterns",
"description": "Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, effici...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monday-automation",
@@ -5487,7 +6096,8 @@
"name": "monday-automation",
"description": "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monorepo-architect",
@@ -5496,7 +6106,8 @@
"name": "monorepo-architect",
"description": "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "monorepo-management",
@@ -5505,7 +6116,8 @@
"name": "monorepo-management",
"description": "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "moodle-external-api-development",
@@ -5514,7 +6126,8 @@
"name": "moodle-external-api-development",
"description": "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "mtls-configuration",
@@ -5523,16 +6136,18 @@
"name": "mtls-configuration",
"description": "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-agent-brainstorming",
"path": "skills\\multi-agent-brainstorming",
"category": "uncategorized",
"name": "multi-agent-brainstorming",
- "description": "Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.",
+ "description": "Transform a single-agent design into a **robust, review-validated design** by simulating a formal peer-review process using multiple constrained agents.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-agent-patterns",
@@ -5541,7 +6156,8 @@
"name": "multi-agent-patterns",
"description": "Master orchestrator, peer-to-peer, and hierarchical multi-agent architectures",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/multi-agent-patterns"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/multi-agent-patterns",
+ "date_added": "2025-02-26"
},
{
"id": "multi-cloud-architecture",
@@ -5550,7 +6166,8 @@
"name": "multi-cloud-architecture",
"description": "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multi-platform-apps-multi-platform",
@@ -5559,7 +6176,8 @@
"name": "multi-platform-apps-multi-platform",
"description": "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "multiplayer",
@@ -5568,7 +6186,8 @@
"name": "multiplayer",
"description": "Multiplayer game development principles. Architecture, networking, synchronization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-code-python",
@@ -5577,7 +6196,8 @@
"name": "n8n-code-python",
"description": "Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-code-python"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-code-python",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-mcp-tools-expert",
@@ -5586,7 +6206,8 @@
"name": "n8n-mcp-tools-expert",
"description": "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele...",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert",
+ "date_added": "2025-02-26"
},
{
"id": "n8n-node-configuration",
@@ -5595,7 +6216,8 @@
"name": "n8n-node-configuration",
"description": "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo...",
"risk": "safe",
- "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration"
+ "source": "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration",
+ "date_added": "2025-02-26"
},
{
"id": "nanobanana-ppt-skills",
@@ -5604,7 +6226,8 @@
"name": "nanobanana-ppt-skills",
"description": "AI-powered PPT generation with document analysis and styled images",
"risk": "safe",
- "source": "https://github.com/op7418/NanoBanana-PPT-Skills"
+ "source": "https://github.com/op7418/NanoBanana-PPT-Skills",
+ "date_added": "2025-02-26"
},
{
"id": "neon-postgres",
@@ -5613,7 +6236,8 @@
"name": "neon-postgres",
"description": "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nerdzao-elite",
@@ -5622,7 +6246,8 @@
"name": "nerdzao-elite",
"description": "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nerdzao-elite-gemini-high",
@@ -5631,7 +6256,8 @@
"name": "nerdzao-elite-gemini-high",
"description": "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade m\u00e1xima e efici\u00eancia de tokens.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nestjs-expert",
@@ -5640,7 +6266,8 @@
"name": "nestjs-expert",
"description": "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "network-101",
@@ -5649,16 +6276,18 @@
"name": "network-101",
"description": "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "network-engineer",
"path": "skills\\network-engineer",
"category": "uncategorized",
"name": "network-engineer",
- "description": "Expert network engineer specializing in modern cloud networking,\nsecurity architectures, and performance optimization. Masters multi-cloud\nconnectivity, service mesh, zero-trust networking, SSL/TLS, global load\nbalancing, and advanced troubleshooting. Handles CDN optimization, network\nautomation, and compliance. Use PROACTIVELY for network design, connectivity\nissues, or performance optimization.\n",
+ "description": "- Working on network engineer tasks or workflows - Needing guidance, best practices, or checklists for network engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-app-router-patterns",
@@ -5667,7 +6296,8 @@
"name": "nextjs-app-router-patterns",
"description": "Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-best-practices",
@@ -5676,7 +6306,8 @@
"name": "nextjs-best-practices",
"description": "Next.js App Router principles. Server Components, data fetching, routing patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nextjs-supabase-auth",
@@ -5685,7 +6316,8 @@
"name": "nextjs-supabase-auth",
"description": "Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nft-standards",
@@ -5694,7 +6326,8 @@
"name": "nft-standards",
"description": "Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nodejs-backend-patterns",
@@ -5703,7 +6336,8 @@
"name": "nodejs-backend-patterns",
"description": "Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nodejs-best-practices",
@@ -5712,7 +6346,8 @@
"name": "nodejs-best-practices",
"description": "Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "nosql-expert",
@@ -5721,7 +6356,8 @@
"name": "nosql-expert",
"description": "Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notebooklm",
@@ -5730,7 +6366,8 @@
"name": "notebooklm",
"description": "Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth....",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notion-automation",
@@ -5739,7 +6376,8 @@
"name": "notion-automation",
"description": "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "notion-template-business",
@@ -5748,7 +6386,8 @@
"name": "notion-template-business",
"description": "Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, market...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "nx-workspace-patterns",
@@ -5757,16 +6396,18 @@
"name": "nx-workspace-patterns",
"description": "Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-engineer",
"path": "skills\\observability-engineer",
"category": "uncategorized",
"name": "observability-engineer",
- "description": "Build production-ready monitoring, logging, and tracing systems.\nImplements comprehensive observability strategies, SLI/SLO management, and\nincident response workflows. Use PROACTIVELY for monitoring infrastructure,\nperformance optimization, or production reliability.\n",
+ "description": "You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-monitoring-monitor-setup",
@@ -5775,7 +6416,8 @@
"name": "observability-monitoring-monitor-setup",
"description": "You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observability-monitoring-slo-implement",
@@ -5784,7 +6426,8 @@
"name": "observability-monitoring-slo-implement",
"description": "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "observe-whatsapp",
@@ -5793,7 +6436,8 @@
"name": "observe-whatsapp",
"description": "Observe and troubleshoot WhatsApp in Kapso: debug message delivery, inspect webhook deliveries/retries, triage API errors, and run health checks. Use when investigating production issues, message f...",
"risk": "safe",
- "source": "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp"
+ "source": "https://github.com/gokapso/agent-skills/tree/master/skills/observe-whatsapp",
+ "date_added": "2025-02-26"
},
{
"id": "obsidian-clipper-template-creator",
@@ -5802,7 +6446,8 @@
"name": "obsidian-clipper-template-creator",
"description": "Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "office-productivity",
@@ -5811,7 +6456,8 @@
"name": "office-productivity",
"description": "Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "on-call-handoff-patterns",
@@ -5820,7 +6466,8 @@
"name": "on-call-handoff-patterns",
"description": "Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call pro...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "onboarding-cro",
@@ -5829,7 +6476,8 @@
"name": "onboarding-cro",
"description": "When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"u...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "one-drive-automation",
@@ -5838,7 +6486,8 @@
"name": "one-drive-automation",
"description": "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "openapi-spec-generation",
@@ -5847,7 +6496,8 @@
"name": "openapi-spec-generation",
"description": "Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "os-scripting",
@@ -5856,7 +6506,8 @@
"name": "os-scripting",
"description": "Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "oss-hunter",
@@ -5865,7 +6516,8 @@
"name": "oss-hunter",
"description": "Automatically hunt for high-impact OSS contribution opportunities in trending repositories.",
"risk": "safe",
- "source": "https://github.com/jackjin1997/ClawForge"
+ "source": "https://github.com/jackjin1997/ClawForge",
+ "date_added": "2025-02-26"
},
{
"id": "outlook-automation",
@@ -5874,7 +6526,8 @@
"name": "outlook-automation",
"description": "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "outlook-calendar-automation",
@@ -5883,16 +6536,18 @@
"name": "outlook-calendar-automation",
"description": "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "page-cro",
"path": "skills\\page-cro",
"category": "uncategorized",
"name": "page-cro",
- "description": "Analyze and optimize individual pages for conversion performance. Use when the user wants to improve conversion rates, diagnose why a page is underperforming, or increase the effectiveness of marketing pages (homepage, landing pages, pricing, feature pages, or blog posts). This skill focuses on diagnosis, prioritization, and testable recommendations\u2014 not blind optimization.\n",
+ "description": "You are an expert in **page-level conversion optimization**. Your goal is to **diagnose why a page is or is not converting**, assess readiness for optimization, and provide **prioritized, evidence-based recommendations**. You do **not** guarantee con",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pagerduty-automation",
@@ -5901,7 +6556,8 @@
"name": "pagerduty-automation",
"description": "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paid-ads",
@@ -5910,7 +6566,8 @@
"name": "paid-ads",
"description": "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' '...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "parallel-agents",
@@ -5919,16 +6576,18 @@
"name": "parallel-agents",
"description": "Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "payment-integration",
"path": "skills\\payment-integration",
"category": "uncategorized",
"name": "payment-integration",
- "description": "Integrate Stripe, PayPal, and payment processors. Handles checkout\nflows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when\nimplementing payments, billing, or subscription features.\n",
+ "description": "- Working on payment integration tasks or workflows - Needing guidance, best practices, or checklists for payment integration",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paypal-integration",
@@ -5937,7 +6596,8 @@
"name": "paypal-integration",
"description": "Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-com...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "paywall-upgrade-cro",
@@ -5946,7 +6606,8 @@
"name": "paywall-upgrade-cro",
"description": "When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pc-games",
@@ -5955,7 +6616,8 @@
"name": "pc-games",
"description": "PC and console game development principles. Engine selection, platform features, optimization strategies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pci-compliance",
@@ -5964,7 +6626,8 @@
"name": "pci-compliance",
"description": "Implement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pdf-official",
@@ -5973,7 +6636,8 @@
"name": "pdf-official",
"description": "Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmaticall...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pentest-checklist",
@@ -5982,7 +6646,8 @@
"name": "pentest-checklist",
"description": "This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"foll...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pentest-commands",
@@ -5991,16 +6656,18 @@
"name": "pentest-commands",
"description": "This skill should be used when the user asks to \"run pentest commands\", \"scan with nmap\", \"use metasploit exploits\", \"crack passwords with hydra or john\", \"scan web vulnerabilities ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-engineer",
"path": "skills\\performance-engineer",
"category": "uncategorized",
"name": "performance-engineer",
- "description": "Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.",
+ "description": "Expert performance engineer specializing in modern observability,",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-profiling",
@@ -6009,7 +6676,8 @@
"name": "performance-profiling",
"description": "Performance profiling principles. Measurement, analysis, and optimization techniques.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-testing-review-ai-review",
@@ -6018,7 +6686,8 @@
"name": "performance-testing-review-ai-review",
"description": "You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "performance-testing-review-multi-agent-review",
@@ -6027,7 +6696,8 @@
"name": "performance-testing-review-multi-agent-review",
"description": "Use when working with performance testing review multi agent review",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "personal-tool-builder",
@@ -6036,16 +6706,18 @@
"name": "personal-tool-builder",
"description": "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "php-pro",
"path": "skills\\php-pro",
"category": "uncategorized",
"name": "php-pro",
- "description": "Write idiomatic PHP code with generators, iterators, SPL data\nstructures, and modern OOP features. Use PROACTIVELY for high-performance PHP\napplications.\n",
+ "description": "- Working on php pro tasks or workflows - Needing guidance, best practices, or checklists for php pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pipedrive-automation",
@@ -6054,7 +6726,8 @@
"name": "pipedrive-automation",
"description": "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "plaid-fintech",
@@ -6063,7 +6736,8 @@
"name": "plaid-fintech",
"description": "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "plan-writing",
@@ -6072,7 +6746,8 @@
"name": "plan-writing",
"description": "Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "planning-with-files",
@@ -6081,7 +6756,8 @@
"name": "planning-with-files",
"description": "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "playwright-skill",
@@ -6090,7 +6766,8 @@
"name": "playwright-skill",
"description": "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "podcast-generation",
@@ -6099,7 +6776,8 @@
"name": "podcast-generation",
"description": "Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creatio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "popup-cro",
@@ -6108,16 +6786,18 @@
"name": "popup-cro",
"description": "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "posix-shell-pro",
"path": "skills\\posix-shell-pro",
"category": "uncategorized",
"name": "posix-shell-pro",
- "description": "Expert in strict POSIX sh scripting for maximum portability across\nUnix-like systems. Specializes in shell scripts that run on any\nPOSIX-compliant shell (dash, ash, sh, bash --posix).\n",
+ "description": "- Working on posix shell pro tasks or workflows - Needing guidance, best practices, or checklists for posix shell pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgres-best-practices",
@@ -6126,7 +6806,8 @@
"name": "postgres-best-practices",
"description": "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgresql",
@@ -6135,7 +6816,8 @@
"name": "postgresql",
"description": "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postgresql-optimization",
@@ -6144,7 +6826,8 @@
"name": "postgresql-optimization",
"description": "PostgreSQL database optimization workflow for query tuning, indexing strategies, performance analysis, and production database management.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "posthog-automation",
@@ -6153,7 +6836,8 @@
"name": "posthog-automation",
"description": "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postmark-automation",
@@ -6162,7 +6846,8 @@
"name": "postmark-automation",
"description": "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "postmortem-writing",
@@ -6171,7 +6856,8 @@
"name": "postmortem-writing",
"description": "Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "powershell-windows",
@@ -6180,7 +6866,8 @@
"name": "powershell-windows",
"description": "PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pptx-official",
@@ -6189,7 +6876,8 @@
"name": "pptx-official",
"description": "Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pricing-strategy",
@@ -6198,7 +6886,8 @@
"name": "pricing-strategy",
"description": "Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prisma-expert",
@@ -6207,7 +6896,8 @@
"name": "prisma-expert",
"description": "Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, re...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "privilege-escalation-methods",
@@ -6216,7 +6906,8 @@
"name": "privilege-escalation-methods",
"description": "This skill should be used when the user asks to \"escalate privileges\", \"get root access\", \"become administrator\", \"privesc techniques\", \"abuse sudo\", \"exploit SUID binaries\", \"K...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "product-manager-toolkit",
@@ -6225,7 +6916,8 @@
"name": "product-manager-toolkit",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "production-code-audit",
@@ -6234,25 +6926,28 @@
"name": "production-code-audit",
"description": "Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "production-scheduling",
"path": "skills\\production-scheduling",
"category": "uncategorized",
"name": "production-scheduling",
- "description": "Codified expertise for production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimising changeovers, responding to disruptions, or balancing manufacturing lines.\n",
+ "description": "Use this skill when planning manufacturing operations, sequencing jobs to minimize changeover times, balancing production lines, resolving factory bottlenecks, or responding to unexpected equipment downtime and supply disruptions.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "programmatic-seo",
"path": "skills\\programmatic-seo",
"category": "uncategorized",
"name": "programmatic-seo",
- "description": "Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design\u2014not execution unless explicitly requested.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "projection-patterns",
@@ -6261,7 +6956,8 @@
"name": "projection-patterns",
"description": "Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prometheus-configuration",
@@ -6270,7 +6966,8 @@
"name": "prometheus-configuration",
"description": "Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-caching",
@@ -6279,7 +6976,8 @@
"name": "prompt-caching",
"description": "Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache augm...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineer",
@@ -6288,7 +6986,8 @@
"name": "prompt-engineer",
"description": "Transforms user prompts into optimized prompts using frameworks (RTF, RISEN, Chain of Thought, RODES, Chain of Density, RACE, RISE, STAR, SOAP, CLEAR, GROW)",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineering",
@@ -6297,7 +6996,8 @@
"name": "prompt-engineering",
"description": "Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, or debug agent behavior.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-engineering-patterns",
@@ -6306,7 +7006,8 @@
"name": "prompt-engineering-patterns",
"description": "Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing productio...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "prompt-library",
@@ -6315,7 +7016,8 @@
"name": "prompt-library",
"description": "Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "protocol-reverse-engineering",
@@ -6324,7 +7026,8 @@
"name": "protocol-reverse-engineering",
"description": "Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pydantic-models-py",
@@ -6333,7 +7036,8 @@
"name": "pydantic-models-py",
"description": "Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "pypict-skill",
@@ -6342,7 +7046,8 @@
"name": "pypict-skill",
"description": "Pairwise test generation",
"risk": "safe",
- "source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md"
+ "source": "https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md",
+ "date_added": "2025-02-26"
},
{
"id": "python-development-python-scaffold",
@@ -6351,7 +7056,8 @@
"name": "python-development-python-scaffold",
"description": "You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-fastapi-development",
@@ -6360,7 +7066,8 @@
"name": "python-fastapi-development",
"description": "Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "python-packaging",
@@ -6369,7 +7076,8 @@
"name": "python-packaging",
"description": "Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-patterns",
@@ -6378,7 +7086,8 @@
"name": "python-patterns",
"description": "Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-performance-optimization",
@@ -6387,16 +7096,18 @@
"name": "python-performance-optimization",
"description": "Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-pro",
"path": "skills\\python-pro",
"category": "uncategorized",
"name": "python-pro",
- "description": "Master Python 3.12+ with modern features, async programming,\nperformance optimization, and production-ready practices. Expert in the latest\nPython ecosystem including uv, ruff, pydantic, and FastAPI. Use PROACTIVELY\nfor Python development, optimization, or advanced Python patterns.\n",
+ "description": "You are a Python expert specializing in modern Python 3.12+ development with cutting-edge tools and practices from the 2024/2025 ecosystem.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "python-testing-patterns",
@@ -6405,25 +7116,28 @@
"name": "python-testing-patterns",
"description": "Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "quality-nonconformance",
"path": "skills\\quality-nonconformance",
"category": "uncategorized",
"name": "quality-nonconformance",
- "description": "Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.\n",
+ "description": "Use this skill when investigating product defects or process deviations, performing root cause analysis (RCA), managing Corrective and Preventive Actions (CAPA), interpreting Statistical Process Control (SPC) data, or auditing supplier quality.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "quant-analyst",
"path": "skills\\quant-analyst",
"category": "uncategorized",
"name": "quant-analyst",
- "description": "Build financial models, backtest trading strategies, and analyze\nmarket data. Implements risk metrics, portfolio optimization, and statistical\narbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or\nrisk analysis.\n",
+ "description": "- Working on quant analyst tasks or workflows - Needing guidance, best practices, or checklists for quant analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "radix-ui-design-system",
@@ -6432,7 +7146,8 @@
"name": "radix-ui-design-system",
"description": "Build accessible design systems with Radix UI primitives. Headless component customization, theming strategies, and compound component patterns for production-grade UI libraries.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "rag-engineer",
@@ -6441,7 +7156,8 @@
"name": "rag-engineer",
"description": "Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications. Use when: building RAG, ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "rag-implementation",
@@ -6450,7 +7166,8 @@
"name": "rag-implementation",
"description": "RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "react-best-practices",
@@ -6459,7 +7176,8 @@
"name": "react-best-practices",
"description": "React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance pat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-flow-architect",
@@ -6468,7 +7186,8 @@
"name": "react-flow-architect",
"description": "Expert ReactFlow architect for building interactive graph applications with hierarchical node-edge systems, performance optimization, and auto-layout integration. Use when Claude needs to create or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-flow-node-ts",
@@ -6477,7 +7196,8 @@
"name": "react-flow-node-ts",
"description": "Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing no...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-modernization",
@@ -6486,7 +7206,8 @@
"name": "react-modernization",
"description": "Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-native-architecture",
@@ -6495,7 +7216,8 @@
"name": "react-native-architecture",
"description": "Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-nextjs-development",
@@ -6504,7 +7226,8 @@
"name": "react-nextjs-development",
"description": "React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "react-patterns",
@@ -6513,7 +7236,8 @@
"name": "react-patterns",
"description": "Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-state-management",
@@ -6522,7 +7246,8 @@
"name": "react-state-management",
"description": "Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "react-ui-patterns",
@@ -6531,7 +7256,8 @@
"name": "react-ui-patterns",
"description": "Modern React UI patterns for loading states, error handling, and data fetching. Use when building UI components, handling async data, or managing UI states.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "readme",
@@ -6540,7 +7266,8 @@
"name": "readme",
"description": "When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...",
"risk": "safe",
- "source": "https://github.com/Shpigford/skills/tree/main/readme"
+ "source": "https://github.com/Shpigford/skills/tree/main/readme",
+ "date_added": "2025-02-26"
},
{
"id": "receiving-code-review",
@@ -6549,7 +7276,8 @@
"name": "receiving-code-review",
"description": "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "red-team-tactics",
@@ -6558,7 +7286,8 @@
"name": "red-team-tactics",
"description": "Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "red-team-tools",
@@ -6567,7 +7296,8 @@
"name": "red-team-tools",
"description": "This skill should be used when the user asks to \"follow red team methodology\", \"perform bug bounty hunting\", \"automate reconnaissance\", \"hunt for XSS vulnerabilities\", \"enumerate su...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "reddit-automation",
@@ -6576,16 +7306,18 @@
"name": "reddit-automation",
"description": "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "reference-builder",
"path": "skills\\reference-builder",
"category": "uncategorized",
"name": "reference-builder",
- "description": "Creates exhaustive technical references and API documentation.\nGenerates comprehensive parameter listings, configuration guides, and\nsearchable reference materials. Use PROACTIVELY for API docs, configuration\nreferences, or complete technical specifications.\n",
+ "description": "- Working on reference builder tasks or workflows - Needing guidance, best practices, or checklists for reference builder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "referral-program",
@@ -6594,7 +7326,8 @@
"name": "referral-program",
"description": "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "remotion-best-practices",
@@ -6603,7 +7336,8 @@
"name": "remotion-best-practices",
"description": "Best practices for Remotion - Video creation in React",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "render-automation",
@@ -6612,7 +7346,8 @@
"name": "render-automation",
"description": "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "requesting-code-review",
@@ -6621,7 +7356,8 @@
"name": "requesting-code-review",
"description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "research-engineer",
@@ -6630,34 +7366,38 @@
"name": "research-engineer",
"description": "An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal impl...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "returns-reverse-logistics",
"path": "skills\\returns-reverse-logistics",
"category": "uncategorized",
"name": "returns-reverse-logistics",
- "description": "Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.\n",
+ "description": "Use this skill when managing the product return lifecycle, including authorization, physical inspection, making disposition decisions (e.g., restock vs. liquidator), detecting return fraud, or processing warranty claims.",
"risk": "safe",
- "source": "https://github.com/ai-evos/agent-skills"
+ "source": "https://github.com/ai-evos/agent-skills",
+ "date_added": "2025-02-26"
},
{
"id": "reverse-engineer",
"path": "skills\\reverse-engineer",
"category": "uncategorized",
"name": "reverse-engineer",
- "description": "Expert reverse engineer specializing in binary analysis,\ndisassembly, decompilation, and software analysis. Masters IDA Pro, Ghidra,\nradare2, x64dbg, and modern RE toolchains. Handles executable analysis,\nlibrary inspection, protocol extraction, and vulnerability research. Use\nPROACTIVELY for binary analysis, CTF challenges, security research, or\nunderstanding undocumented software.\n",
+ "description": "- IDAPython (IDA Pro scripting) - Ghidra scripting (Java/Python via Jython) - r2pipe (radare2 Python API) - pwntools (CTF/exploitation toolkit) - capstone (disassembly framework) - keystone (assembly framework) - unicorn (CPU emulator framework) - an",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "risk-manager",
"path": "skills\\risk-manager",
"category": "uncategorized",
"name": "risk-manager",
- "description": "Monitor portfolio risk, R-multiples, and position limits. Creates\nhedging strategies, calculates expectancy, and implements stop-losses. Use\nPROACTIVELY for risk assessment, trade tracking, or portfolio protection.\n",
+ "description": "- Working on risk manager tasks or workflows - Needing guidance, best practices, or checklists for risk manager",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "risk-metrics-calculation",
@@ -6666,16 +7406,18 @@
"name": "risk-metrics-calculation",
"description": "Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ruby-pro",
"path": "skills\\ruby-pro",
"category": "uncategorized",
"name": "ruby-pro",
- "description": "Write idiomatic Ruby code with metaprogramming, Rails patterns, and\nperformance optimization. Specializes in Ruby on Rails, gem development, and\ntesting frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or\ncomplex Ruby features.\n",
+ "description": "- Working on ruby pro tasks or workflows - Needing guidance, best practices, or checklists for ruby pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "rust-async-patterns",
@@ -6684,16 +7426,18 @@
"name": "rust-async-patterns",
"description": "Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "rust-pro",
"path": "skills\\rust-pro",
"category": "uncategorized",
"name": "rust-pro",
- "description": "Master Rust 1.75+ with modern async patterns, advanced type system\nfeatures, and production-ready systems programming. Expert in the latest Rust\necosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for\nRust development, performance optimization, or systems programming.\n",
+ "description": "You are a Rust expert specializing in modern Rust 1.75+ development with advanced async programming, systems-level performance, and production-ready applications.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "saga-orchestration",
@@ -6702,16 +7446,18 @@
"name": "saga-orchestration",
"description": "Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sales-automator",
"path": "skills\\sales-automator",
"category": "uncategorized",
"name": "sales-automator",
- "description": "Draft cold emails, follow-ups, and proposal templates. Creates\npricing pages, case studies, and sales scripts. Use PROACTIVELY for sales\noutreach or lead nurturing.\n",
+ "description": "- Working on sales automator tasks or workflows - Needing guidance, best practices, or checklists for sales automator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "salesforce-automation",
@@ -6720,7 +7466,8 @@
"name": "salesforce-automation",
"description": "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "salesforce-development",
@@ -6729,7 +7476,8 @@
"name": "salesforce-development",
"description": "Expert patterns for Salesforce platform development including Lightning Web Components (LWC), Apex triggers and classes, REST/Bulk APIs, Connected Apps, and Salesforce DX with scratch orgs and 2nd ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "sast-configuration",
@@ -6738,16 +7486,18 @@
"name": "sast-configuration",
"description": "Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or aut...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "scala-pro",
"path": "skills\\scala-pro",
"category": "uncategorized",
"name": "scala-pro",
- "description": "Master enterprise-grade Scala development with functional\nprogramming, distributed systems, and big data processing. Expert in Apache\nPekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use\nPROACTIVELY for Scala system design, performance optimization, or enterprise\nintegration.\n",
+ "description": "- Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "scanning-tools",
@@ -6756,16 +7506,18 @@
"name": "scanning-tools",
"description": "This skill should be used when the user asks to \"perform vulnerability scanning\", \"scan networks for open ports\", \"assess web application security\", \"scan wireless networks\", \"detec...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "schema-markup",
"path": "skills\\schema-markup",
"category": "uncategorized",
"name": "schema-markup",
- "description": "Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "screen-reader-testing",
@@ -6774,7 +7526,8 @@
"name": "screen-reader-testing",
"description": "Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "screenshots",
@@ -6783,7 +7536,8 @@
"name": "screenshots",
"description": "Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.",
"risk": "safe",
- "source": "https://github.com/Shpigford/skills/tree/main/screenshots"
+ "source": "https://github.com/Shpigford/skills/tree/main/screenshots",
+ "date_added": "2025-02-26"
},
{
"id": "scroll-experience",
@@ -6792,16 +7546,18 @@
"name": "scroll-experience",
"description": "Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product p...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "search-specialist",
"path": "skills\\search-specialist",
"category": "uncategorized",
"name": "search-specialist",
- "description": "Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.",
+ "description": "Expert web researcher using advanced search techniques and",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "secrets-management",
@@ -6810,7 +7566,8 @@
"name": "secrets-management",
"description": "Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-audit",
@@ -6819,16 +7576,18 @@
"name": "security-audit",
"description": "Comprehensive security auditing workflow covering web application testing, API security, penetration testing, vulnerability scanning, and security hardening.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "security-auditor",
"path": "skills\\security-auditor",
"category": "uncategorized",
"name": "security-auditor",
- "description": "Expert security auditor specializing in DevSecOps, comprehensive\ncybersecurity, and compliance frameworks. Masters vulnerability assessment,\nthreat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud\nsecurity, and security automation. Handles DevSecOps integration, compliance\n(GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits,\nDevSecOps, or compliance implementation.\n",
+ "description": "You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-bluebook-builder",
@@ -6837,7 +7596,8 @@
"name": "security-bluebook-builder",
"description": "Build security Blue Books for sensitive apps",
"risk": "safe",
- "source": "https://github.com/SHADOWPR0/security-bluebook-builder"
+ "source": "https://github.com/SHADOWPR0/security-bluebook-builder",
+ "date_added": "2025-02-26"
},
{
"id": "security-compliance-compliance-check",
@@ -6846,7 +7606,8 @@
"name": "security-compliance-compliance-check",
"description": "You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-requirement-extraction",
@@ -6855,7 +7616,8 @@
"name": "security-requirement-extraction",
"description": "Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-dependencies",
@@ -6864,7 +7626,8 @@
"name": "security-scanning-security-dependencies",
"description": "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, ass...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-hardening",
@@ -6873,16 +7636,18 @@
"name": "security-scanning-security-hardening",
"description": "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "security-scanning-security-sast",
"path": "skills\\security-scanning-security-sast",
"category": "uncategorized",
"name": "security-scanning-security-sast",
- "description": "Static Application Security Testing (SAST) for code vulnerability\nanalysis across multiple languages and frameworks\n",
+ "description": "Static Application Security Testing (SAST) for comprehensive code vulnerability detection across multiple languages, frameworks, and security patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "segment-automation",
@@ -6891,7 +7656,8 @@
"name": "segment-automation",
"description": "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "segment-cdp",
@@ -6900,7 +7666,8 @@
"name": "segment-cdp",
"description": "Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "sendgrid-automation",
@@ -6909,7 +7676,8 @@
"name": "sendgrid-automation",
"description": "Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current sche...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "senior-architect",
@@ -6918,7 +7686,8 @@
"name": "senior-architect",
"description": "Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. I...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "senior-fullstack",
@@ -6927,7 +7696,8 @@
"name": "senior-fullstack",
"description": "Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architec...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sentry-automation",
@@ -6936,115 +7706,128 @@
"name": "sentry-automation",
"description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-audit",
"path": "skills\\seo-audit",
"category": "uncategorized",
"name": "seo-audit",
- "description": "Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.\n",
+ "description": "You are an **SEO diagnostic specialist**. Your role is to **identify, explain, and prioritize SEO issues** that affect organic visibility\u2014**not to implement fixes unless explicitly requested**.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-authority-builder",
"path": "skills\\seo-authority-builder",
"category": "uncategorized",
"name": "seo-authority-builder",
- "description": "Analyzes content for E-E-A-T signals and suggests improvements to\nbuild authority and trust. Identifies missing credibility elements. Use\nPROACTIVELY for YMYL topics.\n",
+ "description": "- Working on seo authority builder tasks or workflows - Needing guidance, best practices, or checklists for seo authority builder",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-cannibalization-detector",
"path": "skills\\seo-cannibalization-detector",
"category": "uncategorized",
"name": "seo-cannibalization-detector",
- "description": "Analyzes multiple provided pages to identify keyword overlap and\npotential cannibalization issues. Suggests differentiation strategies. Use\nPROACTIVELY when reviewing similar content.\n",
+ "description": "- Working on seo cannibalization detector tasks or workflows - Needing guidance, best practices, or checklists for seo cannibalization detector",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-auditor",
"path": "skills\\seo-content-auditor",
"category": "uncategorized",
"name": "seo-content-auditor",
- "description": "Analyzes provided content for quality, E-E-A-T signals, and SEO\nbest practices. Scores content and provides improvement recommendations based\non established guidelines. Use PROACTIVELY for content review.\n",
+ "description": "- Working on seo content auditor tasks or workflows - Needing guidance, best practices, or checklists for seo content auditor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-planner",
"path": "skills\\seo-content-planner",
"category": "uncategorized",
"name": "seo-content-planner",
- "description": "Creates comprehensive content outlines and topic clusters for SEO.\nPlans content calendars and identifies topic gaps. Use PROACTIVELY for content\nstrategy and planning.\n",
+ "description": "- Working on seo content planner tasks or workflows - Needing guidance, best practices, or checklists for seo content planner",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-refresher",
"path": "skills\\seo-content-refresher",
"category": "uncategorized",
"name": "seo-content-refresher",
- "description": "Identifies outdated elements in provided content and suggests\nupdates to maintain freshness. Finds statistics, dates, and examples that need\nupdating. Use PROACTIVELY for older content.\n",
+ "description": "- Working on seo content refresher tasks or workflows - Needing guidance, best practices, or checklists for seo content refresher",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-content-writer",
"path": "skills\\seo-content-writer",
"category": "uncategorized",
"name": "seo-content-writer",
- "description": "Writes SEO-optimized content based on provided keywords and topic\nbriefs. Creates engaging, comprehensive content following best practices. Use\nPROACTIVELY for content creation tasks.\n",
+ "description": "- Working on seo content writer tasks or workflows - Needing guidance, best practices, or checklists for seo content writer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-fundamentals",
"path": "skills\\seo-fundamentals",
"category": "uncategorized",
"name": "seo-fundamentals",
- "description": "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.\n",
+ "description": "---",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-keyword-strategist",
"path": "skills\\seo-keyword-strategist",
"category": "uncategorized",
"name": "seo-keyword-strategist",
- "description": "Analyzes keyword usage in provided content, calculates density,\nsuggests semantic variations and LSI keywords based on the topic. Prevents\nover-optimization. Use PROACTIVELY for content optimization.\n",
+ "description": "- Working on seo keyword strategist tasks or workflows - Needing guidance, best practices, or checklists for seo keyword strategist",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-meta-optimizer",
"path": "skills\\seo-meta-optimizer",
"category": "uncategorized",
"name": "seo-meta-optimizer",
- "description": "Creates optimized meta titles, descriptions, and URL suggestions\nbased on character limits and best practices. Generates compelling,\nkeyword-rich metadata. Use PROACTIVELY for new content.\n",
+ "description": "- Working on seo meta optimizer tasks or workflows - Needing guidance, best practices, or checklists for seo meta optimizer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-snippet-hunter",
"path": "skills\\seo-snippet-hunter",
"category": "uncategorized",
"name": "seo-snippet-hunter",
- "description": "Formats content to be eligible for featured snippets and SERP\nfeatures. Creates snippet-optimized content blocks based on best practices.\nUse PROACTIVELY for question-based content.\n",
+ "description": "- Working on seo snippet hunter tasks or workflows - Needing guidance, best practices, or checklists for seo snippet hunter",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "seo-structure-architect",
"path": "skills\\seo-structure-architect",
"category": "uncategorized",
"name": "seo-structure-architect",
- "description": "Analyzes and optimizes content structure including header\nhierarchy, suggests schema markup, and internal linking opportunities. Creates\nsearch-friendly content organization. Use PROACTIVELY for content structuring.\n",
+ "description": "- Working on seo structure architect tasks or workflows - Needing guidance, best practices, or checklists for seo structure architect",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "server-management",
@@ -7053,7 +7836,8 @@
"name": "server-management",
"description": "Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "service-mesh-expert",
@@ -7062,7 +7846,8 @@
"name": "service-mesh-expert",
"description": "Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "service-mesh-observability",
@@ -7071,7 +7856,8 @@
"name": "service-mesh-observability",
"description": "Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SL...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shader-programming-glsl",
@@ -7080,7 +7866,8 @@
"name": "shader-programming-glsl",
"description": "Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sharp-edges",
@@ -7089,7 +7876,8 @@
"name": "sharp-edges",
"description": "Identify error-prone APIs and dangerous configurations",
"risk": "safe",
- "source": "https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges"
+ "source": "https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges",
+ "date_added": "2025-02-26"
},
{
"id": "shellcheck-configuration",
@@ -7098,7 +7886,8 @@
"name": "shellcheck-configuration",
"description": "Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shodan-reconnaissance",
@@ -7107,7 +7896,8 @@
"name": "shodan-reconnaissance",
"description": "This skill should be used when the user asks to \"search for exposed devices on the internet,\" \"perform Shodan reconnaissance,\" \"find vulnerable services using Shodan,\" \"scan IP ranges...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-apps",
@@ -7116,7 +7906,8 @@
"name": "shopify-apps",
"description": "Expert patterns for Shopify app development including Remix/React Router apps, embedded apps with App Bridge, webhook handling, GraphQL Admin API, Polaris components, billing, and app extensions. U...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-automation",
@@ -7125,16 +7916,18 @@
"name": "shopify-automation",
"description": "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "shopify-development",
"path": "skills\\shopify-development",
"category": "uncategorized",
"name": "shopify-development",
- "description": "Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.\nTRIGGER: \"shopify\", \"shopify app\", \"checkout extension\", \"admin extension\", \"POS extension\",\n\"shopify theme\", \"liquid template\", \"polaris\", \"shopify graphql\", \"shopify webhook\",\n\"shopify billing\", \"app subscription\", \"metafields\", \"shopify functions\"\n",
+ "description": "Use this skill when the user asks about:",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "signup-flow-cro",
@@ -7143,7 +7936,8 @@
"name": "signup-flow-cro",
"description": "When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "similarity-search-patterns",
@@ -7152,7 +7946,8 @@
"name": "similarity-search-patterns",
"description": "Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-creator",
@@ -7161,7 +7956,8 @@
"name": "skill-creator",
"description": "This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire s...",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-creator-ms",
@@ -7170,7 +7966,8 @@
"name": "skill-creator-ms",
"description": "Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-developer",
@@ -7179,7 +7976,8 @@
"name": "skill-developer",
"description": "Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skil...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "skill-rails-upgrade",
@@ -7188,7 +7986,8 @@
"name": "skill-rails-upgrade",
"description": "Analyze Rails apps and provide upgrade assessments",
"risk": "safe",
- "source": "https://github.com/robzolkos/skill-rails-upgrade"
+ "source": "https://github.com/robzolkos/skill-rails-upgrade",
+ "date_added": "2025-02-26"
},
{
"id": "skill-seekers",
@@ -7197,7 +7996,8 @@
"name": "skill-seekers",
"description": "-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.",
"risk": "safe",
- "source": "https://github.com/yusufkaraaslan/Skill_Seekers"
+ "source": "https://github.com/yusufkaraaslan/Skill_Seekers",
+ "date_added": "2025-02-26"
},
{
"id": "slack-automation",
@@ -7206,7 +8006,8 @@
"name": "slack-automation",
"description": "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatica...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "slack-bot-builder",
@@ -7215,7 +8016,8 @@
"name": "slack-bot-builder",
"description": "Build Slack apps using the Bolt framework across Python, JavaScript, and Java. Covers Block Kit for rich UIs, interactive components, slash commands, event handling, OAuth installation flows, and W...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "slack-gif-creator",
@@ -7224,7 +8026,8 @@
"name": "slack-gif-creator",
"description": "Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "slo-implementation",
@@ -7233,7 +8036,8 @@
"name": "slo-implementation",
"description": "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "smtp-penetration-testing",
@@ -7242,7 +8046,8 @@
"name": "smtp-penetration-testing",
"description": "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "social-content",
@@ -7251,7 +8056,8 @@
"name": "social-content",
"description": "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "software-architecture",
@@ -7260,7 +8066,8 @@
"name": "software-architecture",
"description": "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "solidity-security",
@@ -7269,7 +8076,8 @@
"name": "solidity-security",
"description": "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "spark-optimization",
@@ -7278,7 +8086,8 @@
"name": "spark-optimization",
"description": "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-injection-testing",
@@ -7287,7 +8096,8 @@
"name": "sql-injection-testing",
"description": "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-optimization-patterns",
@@ -7296,16 +8106,18 @@
"name": "sql-optimization-patterns",
"description": "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sql-pro",
"path": "skills\\sql-pro",
"category": "uncategorized",
"name": "sql-pro",
- "description": "Master modern SQL with cloud-native databases, OLTP/OLAP\noptimization, and advanced query techniques. Expert in performance tuning,\ndata modeling, and hybrid analytical systems. Use PROACTIVELY for database\noptimization or complex analysis.\n",
+ "description": "You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "sqlmap-database-pentesting",
@@ -7314,7 +8126,8 @@
"name": "sqlmap-database-pentesting",
"description": "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "square-automation",
@@ -7323,7 +8136,8 @@
"name": "square-automation",
"description": "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ssh-penetration-testing",
@@ -7332,61 +8146,68 @@
"name": "ssh-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-analyst",
"path": "skills\\startup-analyst",
"category": "uncategorized",
"name": "startup-analyst",
- "description": "Expert startup business analyst specializing in market sizing,\nfinancial modeling, competitive analysis, and strategic planning for\nearly-stage companies. Use PROACTIVELY when the user asks about market\nopportunity, TAM/SAM/SOM, financial projections, unit economics, competitive\nlandscape, team planning, startup metrics, or business strategy for pre-seed\nthrough Series A startups.\n",
+ "description": "- Working on startup analyst tasks or workflows - Needing guidance, best practices, or checklists for startup analyst",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-business-case",
"path": "skills\\startup-business-analyst-business-case",
"category": "uncategorized",
"name": "startup-business-analyst-business-case",
- "description": "Generate comprehensive investor-ready business case document with\nmarket, solution, financials, and strategy\n",
+ "description": "Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-financial-projections",
"path": "skills\\startup-business-analyst-financial-projections",
"category": "uncategorized",
"name": "startup-business-analyst-financial-projections",
- "description": "Create detailed 3-5 year financial model with revenue, costs, cash\nflow, and scenarios\n",
+ "description": "Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-business-analyst-market-opportunity",
"path": "skills\\startup-business-analyst-market-opportunity",
"category": "uncategorized",
"name": "startup-business-analyst-market-opportunity",
- "description": "Generate comprehensive market opportunity analysis with TAM/SAM/SOM\ncalculations\n",
+ "description": "Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-financial-modeling",
"path": "skills\\startup-financial-modeling",
"category": "uncategorized",
"name": "startup-financial-modeling",
- "description": "This skill should be used when the user asks to \\\\\\\"create financial\nprojections\", \"build a financial model\", \"forecast revenue\", \"calculate burn\nrate\", \"estimate runway\", \"model cash flow\", or requests 3-5 year financial\nplanning for a startup.\n",
+ "description": "Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "startup-metrics-framework",
"path": "skills\\startup-metrics-framework",
"category": "uncategorized",
"name": "startup-metrics-framework",
- "description": "This skill should be used when the user asks about \\\\\\\"key startup\nmetrics\", \"SaaS metrics\", \"CAC and LTV\", \"unit economics\", \"burn multiple\",\n\"rule of 40\", \"marketplace metrics\", or requests guidance on tracking and\noptimizing business performance metrics.\n",
+ "description": "Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stitch-ui-design",
@@ -7395,7 +8216,8 @@
"name": "stitch-ui-design",
"description": "Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI/UX in Stitch, create app interfaces, generate mobile/web designs, or needs help cra...",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "stride-analysis-patterns",
@@ -7404,7 +8226,8 @@
"name": "stride-analysis-patterns",
"description": "Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stripe-automation",
@@ -7413,7 +8236,8 @@
"name": "stripe-automation",
"description": "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "stripe-integration",
@@ -7422,7 +8246,8 @@
"name": "stripe-integration",
"description": "Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "subagent-driven-development",
@@ -7431,7 +8256,8 @@
"name": "subagent-driven-development",
"description": "Use when executing implementation plans with independent tasks in the current session",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "supabase-automation",
@@ -7440,7 +8266,8 @@
"name": "supabase-automation",
"description": "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "superpowers-lab",
@@ -7449,7 +8276,8 @@
"name": "superpowers-lab",
"description": "Lab environment for Claude superpowers",
"risk": "safe",
- "source": "https://github.com/obra/superpowers-lab"
+ "source": "https://github.com/obra/superpowers-lab",
+ "date_added": "2025-02-26"
},
{
"id": "swiftui-expert-skill",
@@ -7458,7 +8286,8 @@
"name": "swiftui-expert-skill",
"description": "Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when buil...",
"risk": "safe",
- "source": "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill"
+ "source": "https://github.com/AvdLee/SwiftUI-Agent-Skill/tree/main/swiftui-expert-skill",
+ "date_added": "2025-02-26"
},
{
"id": "systematic-debugging",
@@ -7467,7 +8296,8 @@
"name": "systematic-debugging",
"description": "Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "systems-programming-rust-project",
@@ -7476,7 +8306,8 @@
"name": "systems-programming-rust-project",
"description": "You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tailwind-design-system",
@@ -7485,7 +8316,8 @@
"name": "tailwind-design-system",
"description": "Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tailwind-patterns",
@@ -7494,7 +8326,8 @@
"name": "tailwind-patterns",
"description": "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tavily-web",
@@ -7503,16 +8336,18 @@
"name": "tavily-web",
"description": "Web search, content extraction, crawling, and research capabilities using Tavily API",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-orchestrator",
"path": "skills\\tdd-orchestrator",
"category": "uncategorized",
"name": "tdd-orchestrator",
- "description": "Master TDD orchestrator specializing in red-green-refactor\ndiscipline, multi-agent workflow coordination, and comprehensive test-driven\ndevelopment practices. Enforces TDD best practices across teams with\nAI-assisted testing and modern frameworks. Use PROACTIVELY for TDD\nimplementation and governance.\n",
+ "description": "- Working on tdd orchestrator tasks or workflows - Needing guidance, best practices, or checklists for tdd orchestrator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflow",
@@ -7521,7 +8356,8 @@
"name": "tdd-workflow",
"description": "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-cycle",
@@ -7530,7 +8366,8 @@
"name": "tdd-workflows-tdd-cycle",
"description": "Use when working with tdd workflows tdd cycle",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-green",
@@ -7539,7 +8376,8 @@
"name": "tdd-workflows-tdd-green",
"description": "Implement the minimal code needed to make failing tests pass in the TDD green phase.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-red",
@@ -7548,7 +8386,8 @@
"name": "tdd-workflows-tdd-red",
"description": "Generate failing tests for the TDD red phase to define expected behavior and edge cases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tdd-workflows-tdd-refactor",
@@ -7557,7 +8396,8 @@
"name": "tdd-workflows-tdd-refactor",
"description": "Use when working with tdd workflows tdd refactor",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-collaboration-issue",
@@ -7566,7 +8406,8 @@
"name": "team-collaboration-issue",
"description": "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-collaboration-standup-notes",
@@ -7575,16 +8416,18 @@
"name": "team-collaboration-standup-notes",
"description": "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "team-composition-analysis",
"path": "skills\\team-composition-analysis",
"category": "uncategorized",
"name": "team-composition-analysis",
- "description": "This skill should be used when the user asks to \\\\\\\"plan team\nstructure\", \"determine hiring needs\", \"design org chart\", \"calculate\ncompensation\", \"plan equity allocation\", or requests organizational design and\nheadcount planning for a startup.\n",
+ "description": "Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-automation",
@@ -7593,7 +8436,8 @@
"name": "telegram-automation",
"description": "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-bot-builder",
@@ -7602,7 +8446,8 @@
"name": "telegram-bot-builder",
"description": "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategie...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "telegram-mini-app",
@@ -7611,7 +8456,8 @@
"name": "telegram-mini-app",
"description": "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "templates",
@@ -7620,16 +8466,18 @@
"name": "templates",
"description": "Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "temporal-python-pro",
"path": "skills\\temporal-python-pro",
"category": "uncategorized",
"name": "temporal-python-pro",
- "description": "Master Temporal workflow orchestration with Python SDK. Implements\ndurable workflows, saga patterns, and distributed transactions. Covers\nasync/await, testing strategies, and production deployment. Use PROACTIVELY\nfor workflow design, microservice orchestration, or long-running processes.\n",
+ "description": "- Working on temporal python pro tasks or workflows - Needing guidance, best practices, or checklists for temporal python pro",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "temporal-python-testing",
@@ -7638,7 +8486,8 @@
"name": "temporal-python-testing",
"description": "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-aws-modules",
@@ -7647,7 +8496,8 @@
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-infrastructure",
@@ -7656,7 +8506,8 @@
"name": "terraform-infrastructure",
"description": "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-module-library",
@@ -7665,7 +8516,8 @@
"name": "terraform-module-library",
"description": "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-skill",
@@ -7674,25 +8526,28 @@
"name": "terraform-skill",
"description": "Terraform infrastructure as code best practices",
"risk": "safe",
- "source": "https://github.com/antonbabenko/terraform-skill"
+ "source": "https://github.com/antonbabenko/terraform-skill",
+ "date_added": "2025-02-26"
},
{
"id": "terraform-specialist",
"path": "skills\\terraform-specialist",
"category": "uncategorized",
"name": "terraform-specialist",
- "description": "Expert Terraform/OpenTofu specialist mastering advanced IaC\nautomation, state management, and enterprise infrastructure patterns. Handles\ncomplex module design, multi-cloud deployments, GitOps workflows, policy as\ncode, and CI/CD integration. Covers migration strategies, security best\npractices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state\nmanagement, or infrastructure automation.\n",
+ "description": "You are a Terraform/OpenTofu specialist focused on advanced infrastructure automation, state management, and modern IaC practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-automator",
"path": "skills\\test-automator",
"category": "uncategorized",
"name": "test-automator",
- "description": "Master AI-powered test automation with modern frameworks,\nself-healing tests, and comprehensive quality engineering. Build scalable\ntesting strategies with advanced CI/CD integration. Use PROACTIVELY for\ntesting automation or quality assurance.\n",
+ "description": "- Working on test automator tasks or workflows - Needing guidance, best practices, or checklists for test automator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-driven-development",
@@ -7701,7 +8556,8 @@
"name": "test-driven-development",
"description": "Use when implementing any feature or bugfix, before writing implementation code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "test-fixing",
@@ -7710,7 +8566,8 @@
"name": "test-fixing",
"description": "Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "testing-patterns",
@@ -7719,7 +8576,8 @@
"name": "testing-patterns",
"description": "Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "testing-qa",
@@ -7728,7 +8586,8 @@
"name": "testing-qa",
"description": "Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "theme-factory",
@@ -7737,7 +8596,8 @@
"name": "theme-factory",
"description": "Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifac...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threat-mitigation-mapping",
@@ -7746,7 +8606,8 @@
"name": "threat-mitigation-mapping",
"description": "Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threat-modeling-expert",
@@ -7755,7 +8616,8 @@
"name": "threat-modeling-expert",
"description": "Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "threejs-skills",
@@ -7764,7 +8626,8 @@
"name": "threejs-skills",
"description": "Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.",
"risk": "safe",
- "source": "https://github.com/CloudAI-X/threejs-skills"
+ "source": "https://github.com/CloudAI-X/threejs-skills",
+ "date_added": "2025-02-26"
},
{
"id": "tiktok-automation",
@@ -7773,7 +8636,8 @@
"name": "tiktok-automation",
"description": "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "todoist-automation",
@@ -7782,7 +8646,8 @@
"name": "todoist-automation",
"description": "Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tool-design",
@@ -7791,7 +8656,8 @@
"name": "tool-design",
"description": "Build tools that agents can use effectively, including architectural reduction patterns",
"risk": "safe",
- "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/tool-design"
+ "source": "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/tool-design",
+ "date_added": "2025-02-26"
},
{
"id": "top-web-vulnerabilities",
@@ -7800,16 +8666,18 @@
"name": "top-web-vulnerabilities",
"description": "This skill should be used when the user asks to \"identify web application vulnerabilities\", \"explain common security flaws\", \"understand vulnerability categories\", \"learn about inject...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "track-management",
"path": "skills\\track-management",
"category": "uncategorized",
"name": "track-management",
- "description": "Use this skill when creating, managing, or working with Conductor\ntracks - the logical work units for features, bugs, and refactors. Applies to\nspec.md, plan.md, and track lifecycle operations.\n",
+ "description": "Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "trello-automation",
@@ -7818,7 +8686,8 @@
"name": "trello-automation",
"description": "Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "trigger-dev",
@@ -7827,7 +8696,8 @@
"name": "trigger-dev",
"description": "Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background ta...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "turborepo-caching",
@@ -7836,16 +8706,18 @@
"name": "turborepo-caching",
"description": "Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "tutorial-engineer",
"path": "skills\\tutorial-engineer",
"category": "uncategorized",
"name": "tutorial-engineer",
- "description": "Creates step-by-step tutorials and educational content from code.\nTransforms complex concepts into progressive learning experiences with\nhands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials,\nor concept explanations.\n",
+ "description": "- Working on tutorial engineer tasks or workflows - Needing guidance, best practices, or checklists for tutorial engineer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "twilio-communications",
@@ -7854,7 +8726,8 @@
"name": "twilio-communications",
"description": "Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems a...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "twitter-automation",
@@ -7863,7 +8736,8 @@
"name": "twitter-automation",
"description": "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-advanced-types",
@@ -7872,25 +8746,28 @@
"name": "typescript-advanced-types",
"description": "Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-expert",
"path": "skills\\typescript-expert",
"category": "uncategorized",
"name": "typescript-expert",
- "description": "TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.",
+ "description": "You are an advanced TypeScript expert with deep, practical knowledge of type-level programming, performance optimization, and real-world problem solving based on current best practices.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "typescript-pro",
"path": "skills\\typescript-pro",
"category": "uncategorized",
"name": "typescript-pro",
- "description": "Master TypeScript with advanced types, generics, and strict type\nsafety. Handles complex type systems, decorators, and enterprise-grade\npatterns. Use PROACTIVELY for TypeScript architecture, type inference\noptimization, or advanced typing patterns.\n",
+ "description": "You are a TypeScript expert specializing in advanced typing and enterprise-grade development.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-skills",
@@ -7899,16 +8776,18 @@
"name": "ui-skills",
"description": "Opinionated, evolving constraints to guide agents when building interfaces",
"risk": "safe",
- "source": "https://github.com/ibelick/ui-skills"
+ "source": "https://github.com/ibelick/ui-skills",
+ "date_added": "2025-02-26"
},
{
"id": "ui-ux-designer",
"path": "skills\\ui-ux-designer",
"category": "uncategorized",
"name": "ui-ux-designer",
- "description": "Create interface designs, wireframes, and design systems. Masters\nuser research, accessibility standards, and modern design tools. Specializes\nin design tokens, component libraries, and inclusive design. Use PROACTIVELY\nfor design systems, user flows, or interface optimization.\n",
+ "description": "- Working on ui ux designer tasks or workflows - Needing guidance, best practices, or checklists for ui ux designer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-ux-pro-max",
@@ -7917,16 +8796,18 @@
"name": "ui-ux-pro-max",
"description": "UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, cr...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "ui-visual-validator",
"path": "skills\\ui-visual-validator",
"category": "uncategorized",
"name": "ui-visual-validator",
- "description": "Rigorous visual validation expert specializing in UI testing,\ndesign system compliance, and accessibility verification. Masters screenshot\nanalysis, visual regression testing, and component validation. Use PROACTIVELY\nto verify UI modifications have achieved their intended goals through\ncomprehensive visual analysis.\n",
+ "description": "- Working on ui visual validator tasks or workflows - Needing guidance, best practices, or checklists for ui visual validator",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unit-testing-test-generate",
@@ -7935,16 +8816,18 @@
"name": "unit-testing-test-generate",
"description": "Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unity-developer",
"path": "skills\\unity-developer",
"category": "uncategorized",
"name": "unity-developer",
- "description": "Build Unity games with optimized C# scripts, efficient rendering,\nand proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and\ncross-platform deployment. Handles gameplay systems, UI implementation, and\nplatform optimization. Use PROACTIVELY for Unity performance issues, game\nmechanics, or cross-platform builds.\n",
+ "description": "- Working on unity developer tasks or workflows - Needing guidance, best practices, or checklists for unity developer",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unity-ecs-patterns",
@@ -7953,7 +8836,8 @@
"name": "unity-ecs-patterns",
"description": "Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large ent...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "unreal-engine-cpp-pro",
@@ -7962,7 +8846,8 @@
"name": "unreal-engine-cpp-pro",
"description": "Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.",
"risk": "safe",
- "source": "self"
+ "source": "self",
+ "date_added": "2025-02-26"
},
{
"id": "upgrading-expo",
@@ -7971,7 +8856,8 @@
"name": "upgrading-expo",
"description": "Upgrade Expo SDK versions",
"risk": "safe",
- "source": "https://github.com/expo/skills/tree/main/plugins/upgrading-expo"
+ "source": "https://github.com/expo/skills/tree/main/plugins/upgrading-expo",
+ "date_added": "2025-02-26"
},
{
"id": "upstash-qstash",
@@ -7980,7 +8866,8 @@
"name": "upstash-qstash",
"description": "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, schedul...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "using-git-worktrees",
@@ -7989,7 +8876,8 @@
"name": "using-git-worktrees",
"description": "Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verifi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "using-neon",
@@ -7998,7 +8886,8 @@
"name": "using-neon",
"description": "Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/...",
"risk": "safe",
- "source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres"
+ "source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres",
+ "date_added": "2025-02-26"
},
{
"id": "using-superpowers",
@@ -8007,7 +8896,8 @@
"name": "using-superpowers",
"description": "Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "uv-package-manager",
@@ -8016,7 +8906,8 @@
"name": "uv-package-manager",
"description": "Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "varlock-claude-skill",
@@ -8025,7 +8916,8 @@
"name": "varlock-claude-skill",
"description": "Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits",
"risk": "safe",
- "source": "https://github.com/wrsmith108/varlock-claude-skill"
+ "source": "https://github.com/wrsmith108/varlock-claude-skill",
+ "date_added": "2025-02-26"
},
{
"id": "vector-database-engineer",
@@ -8034,7 +8926,8 @@
"name": "vector-database-engineer",
"description": "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vector-index-tuning",
@@ -8043,7 +8936,8 @@
"name": "vector-index-tuning",
"description": "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-automation",
@@ -8052,7 +8946,8 @@
"name": "vercel-automation",
"description": "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-deploy-claimable",
@@ -8061,7 +8956,8 @@
"name": "vercel-deploy-claimable",
"description": "Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...",
"risk": "safe",
- "source": "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable"
+ "source": "https://github.com/vercel-labs/agent-skills/tree/main/skills/claude.ai/vercel-deploy-claimable",
+ "date_added": "2025-02-26"
},
{
"id": "vercel-deployment",
@@ -8070,7 +8966,8 @@
"name": "vercel-deployment",
"description": "Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.",
"risk": "safe",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "verification-before-completion",
@@ -8079,7 +8976,8 @@
"name": "verification-before-completion",
"description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vexor",
@@ -8088,7 +8986,8 @@
"name": "vexor",
"description": "Vector-powered CLI for semantic file search with a Claude/Codex skill",
"risk": "safe",
- "source": "https://github.com/scarletkc/vexor"
+ "source": "https://github.com/scarletkc/vexor",
+ "date_added": "2025-02-26"
},
{
"id": "viral-generator-builder",
@@ -8097,7 +8996,8 @@
"name": "viral-generator-builder",
"description": "Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanic...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-agents",
@@ -8106,7 +9006,8 @@
"name": "voice-agents",
"description": "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flo...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-ai-development",
@@ -8115,7 +9016,8 @@
"name": "voice-ai-development",
"description": "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "voice-ai-engine-development",
@@ -8124,7 +9026,8 @@
"name": "voice-ai-engine-development",
"description": "Build real-time conversational AI voice engines using async worker pipelines, streaming transcription, LLM agents, and TTS synthesis with interrupt handling and multi-provider support",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vr-ar",
@@ -8133,7 +9036,8 @@
"name": "vr-ar",
"description": "VR/AR development principles. Comfort, interaction, performance requirements.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "vulnerability-scanner",
@@ -8142,7 +9046,8 @@
"name": "vulnerability-scanner",
"description": "Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wcag-audit-patterns",
@@ -8151,7 +9056,8 @@
"name": "wcag-audit-patterns",
"description": "Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-artifacts-builder",
@@ -8160,7 +9066,8 @@
"name": "web-artifacts-builder",
"description": "Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state ma...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-design-guidelines",
@@ -8169,7 +9076,8 @@
"name": "web-design-guidelines",
"description": "Review UI code for Web Interface Guidelines compliance. Use when asked to \\\"review my UI\\\", \\\"check accessibility\\\", \\\"audit design\\\", \\\"review UX\\\", or \\\"check my site aga...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-games",
@@ -8178,7 +9086,8 @@
"name": "web-games",
"description": "Web browser game development principles. Framework selection, WebGPU, optimization, PWA.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-performance-optimization",
@@ -8187,7 +9096,8 @@
"name": "web-performance-optimization",
"description": "Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "web-security-testing",
@@ -8196,7 +9106,8 @@
"name": "web-security-testing",
"description": "Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "web3-testing",
@@ -8205,7 +9116,8 @@
"name": "web3-testing",
"description": "Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or va...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "webapp-testing",
@@ -8214,7 +9126,8 @@
"name": "webapp-testing",
"description": "Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "webflow-automation",
@@ -8223,7 +9136,8 @@
"name": "webflow-automation",
"description": "Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "whatsapp-automation",
@@ -8232,7 +9146,8 @@
"name": "whatsapp-automation",
"description": "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-architect",
@@ -8241,7 +9156,8 @@
"name": "wiki-architect",
"description": "Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-changelog",
@@ -8250,7 +9166,8 @@
"name": "wiki-changelog",
"description": "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-onboarding",
@@ -8259,7 +9176,8 @@
"name": "wiki-onboarding",
"description": "Generates two complementary onboarding guides \u2014 a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation fo...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-page-writer",
@@ -8268,7 +9186,8 @@
"name": "wiki-page-writer",
"description": "Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating tech...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-qa",
@@ -8277,7 +9196,8 @@
"name": "wiki-qa",
"description": "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-researcher",
@@ -8286,7 +9206,8 @@
"name": "wiki-researcher",
"description": "Conducts multi-turn iterative deep research on specific topics within a codebase with zero tolerance for shallow analysis. Use when the user wants an in-depth investigation, needs to understand how...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wiki-vitepress",
@@ -8295,7 +9216,8 @@
"name": "wiki-vitepress",
"description": "Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsa...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "windows-privilege-escalation",
@@ -8304,7 +9226,8 @@
"name": "windows-privilege-escalation",
"description": "This skill should be used when the user asks to \"escalate privileges on Windows,\" \"find Windows privesc vectors,\" \"enumerate Windows for privilege escalation,\" \"exploit Windows miscon...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wireshark-analysis",
@@ -8313,7 +9236,8 @@
"name": "wireshark-analysis",
"description": "This skill should be used when the user asks to \"analyze network traffic with Wireshark\", \"capture packets for troubleshooting\", \"filter PCAP files\", \"follow TCP/UDP streams\", \"dete...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress",
@@ -8322,7 +9246,8 @@
"name": "wordpress",
"description": "Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-penetration-testing",
@@ -8331,7 +9256,8 @@
"name": "wordpress-penetration-testing",
"description": "This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vu...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-plugin-development",
@@ -8340,7 +9266,8 @@
"name": "wordpress-plugin-development",
"description": "WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, and security best practices.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-theme-development",
@@ -8349,7 +9276,8 @@
"name": "wordpress-theme-development",
"description": "WordPress theme development workflow covering theme architecture, template hierarchy, custom post types, block editor support, and responsive design.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "wordpress-woocommerce-development",
@@ -8358,7 +9286,8 @@
"name": "wordpress-woocommerce-development",
"description": "WooCommerce store development workflow covering store setup, payment integration, shipping configuration, and customization.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-automation",
@@ -8367,7 +9296,8 @@
"name": "workflow-automation",
"description": "Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, wor...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-orchestration-patterns",
@@ -8376,16 +9306,18 @@
"name": "workflow-orchestration-patterns",
"description": "Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running ...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "workflow-patterns",
"path": "skills\\workflow-patterns",
"category": "uncategorized",
"name": "workflow-patterns",
- "description": "Use this skill when implementing tasks according to Conductor's TDD\nworkflow, handling phase checkpoints, managing git commits for tasks, or\nunderstanding the verification protocol.\n",
+ "description": "Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "wrike-automation",
@@ -8394,7 +9326,8 @@
"name": "wrike-automation",
"description": "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "writer",
@@ -8403,7 +9336,8 @@
"name": "writer",
"description": "Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.",
"risk": "safe",
- "source": "personal"
+ "source": "personal",
+ "date_added": "2025-02-26"
},
{
"id": "writing-plans",
@@ -8412,7 +9346,8 @@
"name": "writing-plans",
"description": "Use when you have a spec or requirements for a multi-step task, before touching code",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "writing-skills",
@@ -8421,7 +9356,8 @@
"name": "writing-skills",
"description": "Use when creating, updating, or improving agent skills.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "x-article-publisher-skill",
@@ -8430,7 +9366,8 @@
"name": "x-article-publisher-skill",
"description": "Publish articles to X/Twitter",
"risk": "safe",
- "source": "https://github.com/wshuyi/x-article-publisher-skill"
+ "source": "https://github.com/wshuyi/x-article-publisher-skill",
+ "date_added": "2025-02-26"
},
{
"id": "xlsx-official",
@@ -8439,7 +9376,8 @@
"name": "xlsx-official",
"description": "Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "xss-html-injection",
@@ -8448,7 +9386,8 @@
"name": "xss-html-injection",
"description": "This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "youtube-automation",
@@ -8457,7 +9396,8 @@
"name": "youtube-automation",
"description": "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "youtube-summarizer",
@@ -8466,7 +9406,8 @@
"name": "youtube-summarizer",
"description": "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks",
"risk": "safe",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zapier-make-patterns",
@@ -8475,7 +9416,8 @@
"name": "zapier-make-patterns",
"description": "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...",
"risk": "unknown",
- "source": "vibeship-spawner-skills (Apache 2.0)"
+ "source": "vibeship-spawner-skills (Apache 2.0)",
+ "date_added": "2025-02-26"
},
{
"id": "zendesk-automation",
@@ -8484,7 +9426,8 @@
"name": "zendesk-automation",
"description": "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zoho-crm-automation",
@@ -8493,7 +9436,8 @@
"name": "zoho-crm-automation",
"description": "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zoom-automation",
@@ -8502,7 +9446,8 @@
"name": "zoom-automation",
"description": "Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
},
{
"id": "zustand-store-ts",
@@ -8511,6 +9456,7 @@
"name": "zustand-store-ts",
"description": "Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...",
"risk": "unknown",
- "source": "community"
+ "source": "community",
+ "date_added": "2025-02-26"
}
]
\ No newline at end of file
diff --git a/web-app/src/pages/Home.jsx b/web-app/src/pages/Home.jsx
index 906f43f3..b2dbf0d4 100644
--- a/web-app/src/pages/Home.jsx
+++ b/web-app/src/pages/Home.jsx
@@ -196,7 +196,14 @@ export function Home() {
{skill.description}