Add a robust auto-update mechanism to the Web App launcher and introduce the Interactive Prompt Builder.
This commit is contained in:
Zied
@@ -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
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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 <PR_NUMBER> --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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 <absolute_path_to_target_workspace>
|
||||
```
|
||||
|
||||
Access at: `http://localhost:3333`
|
||||
|
||||
## When to Use
|
||||
This skill is applicable to execute the workflow or actions described in the overview.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
174
web-app/public/skills/ai-agent-development/SKILL.md
Normal file
174
web-app/public/skills/ai-agent-development/SKILL.md
Normal file
@@ -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
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
253
web-app/public/skills/ai-ml/SKILL.md
Normal file
253
web-app/public/skills/ai-ml/SKILL.md
Normal file
@@ -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
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
- 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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
152
web-app/public/skills/android-jetpack-compose-expert/SKILL.md
Normal file
152
web-app/public/skills/android-jetpack-compose-expert/SKILL.md
Normal file
@@ -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<UserUiState> = _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<Home> {
|
||||
HomeScreen(onNavigateToProfile = { id ->
|
||||
navController.navigate(Profile(userId = id))
|
||||
})
|
||||
}
|
||||
composable<Profile> { 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.
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
---
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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:
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
164
web-app/public/skills/api-documentation/SKILL.md
Normal file
164
web-app/public/skills/api-documentation/SKILL.md
Normal file
@@ -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
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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 <project_path>` |
|
||||
|
||||
|
||||
## When to Use
|
||||
This skill is applicable to execute the workflow or actions described in the overview.
|
||||
|
||||
@@ -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
|
||||
|
||||
172
web-app/public/skills/api-security-testing/SKILL.md
Normal file
172
web-app/public/skills/api-security-testing/SKILL.md
Normal file
@@ -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
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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:
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
309
web-app/public/skills/aws-cost-cleanup/SKILL.md
Normal file
309
web-app/public/skills/aws-cost-cleanup/SKILL.md
Normal file
@@ -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 <<EOF
|
||||
{
|
||||
"Rules": [
|
||||
{
|
||||
"Id": "Archive old objects",
|
||||
"Status": "Enabled",
|
||||
"Transitions": [
|
||||
{
|
||||
"Days": 90,
|
||||
"StorageClass": "STANDARD_IA"
|
||||
},
|
||||
{
|
||||
"Days": 180,
|
||||
"StorageClass": "GLACIER"
|
||||
}
|
||||
],
|
||||
"NoncurrentVersionExpiration": {
|
||||
"NoncurrentDays": 30
|
||||
},
|
||||
"AbortIncompleteMultipartUpload": {
|
||||
"DaysAfterInitiation": 7
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
EOF
|
||||
|
||||
aws s3api put-bucket-lifecycle-configuration \
|
||||
--bucket my-bucket \
|
||||
--lifecycle-configuration file://lifecycle-policy.json
|
||||
```
|
||||
|
||||
## Cost Impact Calculator
|
||||
|
||||
```python
|
||||
#!/usr/bin/env python3
|
||||
# calculate-savings.py
|
||||
|
||||
import boto3
|
||||
from datetime import datetime, timedelta
|
||||
|
||||
ec2 = boto3.client('ec2')
|
||||
|
||||
# Calculate EBS volume savings
|
||||
volumes = ec2.describe_volumes(
|
||||
Filters=[{'Name': 'status', 'Values': ['available']}]
|
||||
)
|
||||
|
||||
total_size = sum(v['Size'] for v in volumes['Volumes'])
|
||||
monthly_cost = total_size * 0.10 # $0.10/GB-month for gp3
|
||||
|
||||
print(f"Unattached EBS Volumes: {len(volumes['Volumes'])}")
|
||||
print(f"Total Size: {total_size} GB")
|
||||
print(f"Monthly Savings: ${monthly_cost:.2f}")
|
||||
|
||||
# Calculate Elastic IP savings
|
||||
addresses = ec2.describe_addresses()
|
||||
unused = [a for a in addresses['Addresses'] if 'AssociationId' not in a]
|
||||
|
||||
eip_cost = len(unused) * 3.65 # $0.005/hour * 730 hours
|
||||
print(f"\nUnused Elastic IPs: {len(unused)}")
|
||||
print(f"Monthly Savings: ${eip_cost:.2f}")
|
||||
|
||||
print(f"\nTotal Monthly Savings: ${monthly_cost + eip_cost:.2f}")
|
||||
print(f"Annual Savings: ${(monthly_cost + eip_cost) * 12:.2f}")
|
||||
```
|
||||
|
||||
## Automated Cleanup Lambda
|
||||
|
||||
```python
|
||||
import boto3
|
||||
from datetime import datetime, timedelta
|
||||
|
||||
def lambda_handler(event, context):
|
||||
ec2 = boto3.client('ec2')
|
||||
|
||||
# Delete unattached volumes older than 7 days
|
||||
volumes = ec2.describe_volumes(
|
||||
Filters=[{'Name': 'status', 'Values': ['available']}]
|
||||
)
|
||||
|
||||
cutoff = datetime.now() - timedelta(days=7)
|
||||
deleted = 0
|
||||
|
||||
for vol in volumes['Volumes']:
|
||||
create_time = vol['CreateTime'].replace(tzinfo=None)
|
||||
if create_time < cutoff:
|
||||
try:
|
||||
ec2.delete_volume(VolumeId=vol['VolumeId'])
|
||||
deleted += 1
|
||||
print(f"Deleted volume: {vol['VolumeId']}")
|
||||
except Exception as e:
|
||||
print(f"Error deleting {vol['VolumeId']}: {e}")
|
||||
|
||||
return {
|
||||
'statusCode': 200,
|
||||
'body': f'Deleted {deleted} volumes'
|
||||
}
|
||||
```
|
||||
|
||||
## Cleanup Workflow
|
||||
|
||||
1. **Discovery Phase** (Read-only)
|
||||
- Run all describe commands
|
||||
- Generate cost impact report
|
||||
- Review with team
|
||||
|
||||
2. **Validation Phase**
|
||||
- Verify resources are truly unused
|
||||
- Check for dependencies
|
||||
- Notify resource owners
|
||||
|
||||
3. **Execution Phase** (Dry-run first)
|
||||
- Run cleanup scripts with dry-run
|
||||
- Review proposed changes
|
||||
- Execute actual cleanup
|
||||
|
||||
4. **Verification Phase**
|
||||
- Confirm deletions
|
||||
- Monitor for issues
|
||||
- Document savings
|
||||
|
||||
## Safety Checklist
|
||||
|
||||
- [ ] Run in dry-run mode first
|
||||
- [ ] Verify resources have no dependencies
|
||||
- [ ] Check resource tags for ownership
|
||||
- [ ] Notify stakeholders before deletion
|
||||
- [ ] Create snapshots of critical data
|
||||
- [ ] Test in non-production first
|
||||
- [ ] Have rollback plan ready
|
||||
- [ ] Document all deletions
|
||||
|
||||
## Example Prompts
|
||||
|
||||
**Discovery**
|
||||
- "Find all unused resources and calculate potential savings"
|
||||
- "Generate a cleanup report for my AWS account"
|
||||
- "What resources can I safely delete?"
|
||||
|
||||
**Execution**
|
||||
- "Create a script to cleanup unattached EBS volumes"
|
||||
- "Delete all snapshots older than 90 days"
|
||||
- "Release unused Elastic IPs"
|
||||
|
||||
**Automation**
|
||||
- "Set up automated cleanup for old snapshots"
|
||||
- "Create a Lambda function for weekly cleanup"
|
||||
- "Schedule monthly resource cleanup"
|
||||
|
||||
## Integration with AWS Organizations
|
||||
|
||||
```bash
|
||||
# Run cleanup across multiple accounts
|
||||
for account in $(aws organizations list-accounts \
|
||||
--query 'Accounts[*].Id' --output text); do
|
||||
|
||||
echo "Checking account: $account"
|
||||
aws ec2 describe-volumes \
|
||||
--filters Name=status,Values=available \
|
||||
--profile account-$account
|
||||
done
|
||||
```
|
||||
|
||||
## Monitoring and Alerts
|
||||
|
||||
```bash
|
||||
# Create CloudWatch alarm for cost anomalies
|
||||
aws cloudwatch put-metric-alarm \
|
||||
--alarm-name high-cost-alert \
|
||||
--alarm-description "Alert when daily cost exceeds threshold" \
|
||||
--metric-name EstimatedCharges \
|
||||
--namespace AWS/Billing \
|
||||
--statistic Maximum \
|
||||
--period 86400 \
|
||||
--evaluation-periods 1 \
|
||||
--threshold 100 \
|
||||
--comparison-operator GreaterThanThreshold
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
- Schedule cleanup during maintenance windows
|
||||
- Always create final snapshots before deletion
|
||||
- Use resource tags to identify cleanup candidates
|
||||
- Implement approval workflow for production
|
||||
- Log all cleanup actions for audit
|
||||
- Set up cost anomaly detection
|
||||
- Review cleanup results weekly
|
||||
|
||||
## Risk Mitigation
|
||||
|
||||
**Medium Risk Actions:**
|
||||
- Deleting unattached volumes (ensure no planned reattachment)
|
||||
- Removing old snapshots (verify no compliance requirements)
|
||||
- Releasing Elastic IPs (check DNS records)
|
||||
|
||||
**Always:**
|
||||
- Maintain 30-day backup retention
|
||||
- Use AWS Backup for critical resources
|
||||
- Test restore procedures
|
||||
- Document cleanup decisions
|
||||
|
||||
## Kiro CLI Integration
|
||||
|
||||
```bash
|
||||
# Analyze and cleanup in one command
|
||||
kiro-cli chat "Use aws-cost-cleanup to find and remove unused resources"
|
||||
|
||||
# Generate cleanup script
|
||||
kiro-cli chat "Create a safe cleanup script for my AWS account"
|
||||
|
||||
# Schedule automated cleanup
|
||||
kiro-cli chat "Set up weekly automated cleanup using aws-cost-cleanup"
|
||||
```
|
||||
|
||||
## Additional Resources
|
||||
|
||||
- [AWS Resource Cleanup Best Practices](https://aws.amazon.com/blogs/mt/automate-resource-cleanup/)
|
||||
- [AWS Systems Manager Automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-automation.html)
|
||||
- [AWS Config Rules for Compliance](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html)
|
||||
192
web-app/public/skills/aws-cost-optimizer/SKILL.md
Normal file
192
web-app/public/skills/aws-cost-optimizer/SKILL.md
Normal file
@@ -0,0 +1,192 @@
|
||||
---
|
||||
name: aws-cost-optimizer
|
||||
description: Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer
|
||||
risk: safe
|
||||
source: community
|
||||
---
|
||||
|
||||
# AWS Cost Optimizer
|
||||
|
||||
Analyze AWS spending patterns, identify waste, and provide actionable cost reduction strategies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when you need to analyze AWS spending, identify cost optimization opportunities, or reduce cloud waste.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
**Cost Analysis**
|
||||
- Parse AWS Cost Explorer data for trends and anomalies
|
||||
- Break down costs by service, region, and resource tags
|
||||
- Identify month-over-month spending increases
|
||||
|
||||
**Resource Optimization**
|
||||
- Detect idle EC2 instances (low CPU utilization)
|
||||
- Find unattached EBS volumes and old snapshots
|
||||
- Identify unused Elastic IPs
|
||||
- Locate underutilized RDS instances
|
||||
- Find old S3 objects eligible for lifecycle policies
|
||||
|
||||
**Savings Recommendations**
|
||||
- Suggest Reserved Instance/Savings Plans opportunities
|
||||
- Recommend instance rightsizing based on CloudWatch metrics
|
||||
- Identify resources in expensive regions
|
||||
- Calculate potential savings with specific actions
|
||||
|
||||
## AWS CLI Commands
|
||||
|
||||
### Get Cost and Usage
|
||||
```bash
|
||||
# Last 30 days cost by service
|
||||
aws ce get-cost-and-usage \
|
||||
--time-period Start=$(date -d '30 days ago' +%Y-%m-%d),End=$(date +%Y-%m-%d) \
|
||||
--granularity MONTHLY \
|
||||
--metrics BlendedCost \
|
||||
--group-by Type=DIMENSION,Key=SERVICE
|
||||
|
||||
# Daily costs for current month
|
||||
aws ce get-cost-and-usage \
|
||||
--time-period Start=$(date +%Y-%m-01),End=$(date +%Y-%m-%d) \
|
||||
--granularity DAILY \
|
||||
--metrics UnblendedCost
|
||||
```
|
||||
|
||||
### Find Unused Resources
|
||||
```bash
|
||||
# Unattached EBS volumes
|
||||
aws ec2 describe-volumes \
|
||||
--filters Name=status,Values=available \
|
||||
--query 'Volumes[*].[VolumeId,Size,VolumeType,CreateTime]' \
|
||||
--output table
|
||||
|
||||
# Unused Elastic IPs
|
||||
aws ec2 describe-addresses \
|
||||
--query 'Addresses[?AssociationId==null].[PublicIp,AllocationId]' \
|
||||
--output table
|
||||
|
||||
# Idle EC2 instances (requires CloudWatch)
|
||||
aws cloudwatch get-metric-statistics \
|
||||
--namespace AWS/EC2 \
|
||||
--metric-name CPUUtilization \
|
||||
--dimensions Name=InstanceId,Value=i-xxxxx \
|
||||
--start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%S) \
|
||||
--end-time $(date -u +%Y-%m-%dT%H:%M:%S) \
|
||||
--period 86400 \
|
||||
--statistics Average
|
||||
|
||||
# Old EBS snapshots (>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)
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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 <app> -g <rg> --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 <app> -g <rg> --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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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=<your-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.
|
||||
|
||||
@@ -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=<your-api-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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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=<your-api-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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user