opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/agents-v2-py/SKILL.md

@@ -6,6 +6,13 @@ source: community
 date_added: "2026-02-27"
 ---
 
+## Compatibility and maintenance
+
+Compatibility alias of `hosted-agents-v2-py`; use that ID for new references when no existing contract requires this one. The full instructions and support files remain local so existing installations
+continue to work offline. This is one shared procedure, not an additional capability.
+Preserve the callable ID when an existing manifest or client configuration uses it.
+Modified in AAS on 2026-09-05; original metadata and license notices are retained.
+
 # Azure AI Hosted Agents (Python)
 
 Build container-based hosted agents using `ImageBasedHostedAgentDefinition` from the Azure AI Projects SDK.
@@ -13,10 +20,10 @@ Build container-based hosted agents using `ImageBasedHostedAgentDefinition` from
 ## Installation
 
 ```bash
-pip install azure-ai-projects>=2.0.0b3 azure-identity
+pip install 'azure-ai-projects>=2.0.0b3,<3' azure-identity
 ```
 
-**Minimum SDK Version:** `2.0.0b3` or later required for hosted agent support.
+These are preview-era SDK v2 sketches. Check the exact installed version and current Azure hosted-agent documentation before provisioning; a broad version range is not an integration test.
 
 ## Environment Variables
 
@@ -35,12 +42,14 @@ Before creating hosted agents:
 
 ## Authentication
 
-Always use `DefaultAzureCredential`:
+Use the approved Azure credential flow for the intended tenant/subscription; this sketch uses `DefaultAzureCredential`:
 
 ```python
 from azure.identity import DefaultAzureCredential
 from azure.ai.projects import AIProjectClient
 
+import os
+
 credential = DefaultAzureCredential()
 client = AIProjectClient(
     endpoint=os.environ["AZURE_AI_PROJECT_ENDPOINT"],
@@ -150,7 +159,7 @@ definition=ImageBasedHostedAgentDefinition(
 )
 ```
 
-**Resource Limits:**
+**Illustrative resource sizes; verify regional/SKU limits before provisioning:**
 | Resource | Min | Max | Default |
 |----------|-----|-----|---------|
 | CPU | 0.5 | 4 | 1 |
@@ -323,7 +332,16 @@ async def create_hosted_agent_async():
 - [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.
+Use for reviewing or creating an explicitly requested container-based Foundry hosted
+agent. First confirm image digest, subscription/tenant, region, service availability,
+permissions and cost scope. Creating agents, granting roles and deleting versions are
+cloud writes; do them only within the user's authorization.
+
+## Review example
+Given a pinned container image and test project, check SDK model fields and registry
+pull access, then prepare the create request. Provision only if authorized and record
+the exact returned version and observed health. Do not delete unrelated versions as
+routine cleanup. Expected result is a version-specific receipt, not an assumed deploy.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/bundled-skills/ai-agents-architect/SKILL.md

@@ -9,6 +9,8 @@ date_added: 2026-02-27
 
 # AI Agents Architect
 
+Modified in AAS on 2026-09-05: bounded actions, privacy and explicit permission checks.
+
 Expert in designing and building autonomous AI agents. Masters tool use,
 memory systems, planning strategies, and multi-agent orchestration.
 
@@ -59,7 +61,7 @@ Reason-Act-Observe cycle for step-by-step execution
 
 **When to use**: Simple tool use with clear action-observation flow
 
-- Thought: reason about what to do next
+- Decision summary: record the selected next action and its observable basis
 - Action: select and invoke a tool
 - Observation: process tool result
 - Repeat until task complete or stuck
@@ -118,7 +120,7 @@ Save state for resumption after failures
 - Checkpoint after each successful step
 - Store task state, memory, and progress
 - Resume from last checkpoint on failure
-- Clean up checkpoints on completion
+- Retain or remove checkpoints according to the user’s authorized retention policy
 
 ## Sharp Edges
 
@@ -218,7 +220,7 @@ Selective memory:
 - Summarize rather than store verbatim
 - Filter by relevance before storing
 - Use RAG for long-term memory
-- Clear working memory between tasks
+- Keep task memory scoped and permissioned; preserve authorized checkpoints and avoid automatic global memory writes
 
 ### Agent has too many tools
 
@@ -239,7 +241,7 @@ get cut off or poorly understood.
 Recommended fix:
 
 Curate tools per task:
-- 5-10 tools maximum per agent
+- Measure tool-selection accuracy and context cost; no universal tool-count threshold
 - Use tool selection layer for large tool sets
 - Specialized agents with focused tools
 - Dynamic tool loading based on task
@@ -272,7 +274,7 @@ Justify multi-agent:
 
 Severity: MEDIUM
 
-Situation: Running agents without logging thoughts/actions
+Situation: Running agents without traceable tool actions and outcomes
 
 Symptoms:
 - Can't explain agent failures
@@ -280,15 +282,15 @@ Symptoms:
 - Debugging takes hours
 
 Why this breaks:
-When agents fail, you need to see what they were thinking, which
-tools they tried, and where they went wrong. Without observability,
+When agents fail, you need observable tool calls, returned errors and
+state transitions to locate the failure. Without observability,
 debugging is guesswork.
 
 Recommended fix:
 
 Implement tracing:
-- Log each thought/action/observation
-- Track tool calls with inputs/outputs
+- Log bounded action/result summaries; do not request or store hidden chain-of-thought
+- Track tool calls with approved, redacted input/output fields
 - Trace token usage and latency
 - Use structured logging for analysis
 
@@ -312,7 +314,7 @@ Recommended fix:
 
 Robust output handling:
 - Use structured output (JSON mode, function calling)
-- Fuzzy matching for actions
+- Exact allowlisted action names and schema-validated arguments; reject ambiguity
 - Retry with format instructions on parse failure
 - Handle multiple output formats
 
@@ -321,20 +323,18 @@ Robust output handling:
 Works well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`
 
 ## When to Use
-- User mentions or implies: build agent
-- User mentions or implies: AI agent
-- User mentions or implies: autonomous agent
-- User mentions or implies: tool use
-- User mentions or implies: function calling
-- User mentions or implies: multi-agent
-- User mentions or implies: agent memory
-- User mentions or implies: agent planning
-- User mentions or implies: langchain agent
-- User mentions or implies: crewai
-- User mentions or implies: autogen
-- User mentions or implies: claude agent sdk
+
+Use when selecting an agent execution loop, tool boundary, memory lifecycle or recovery strategy for a concrete task. Start with one agent; delegate only when the user’s workflow permits it and the subtasks are independently useful.
+
+## Inputs and worked example
+
+Record the task’s success condition, available tools, external write permissions, cost/time limits and failure policy. Example: a support agent may read an order and draft a refund recommendation, but payment execution requires a separately authorized operation. Give read and write tools distinct schemas, validate the order/tenant server-side, and keep the write disabled until that authorization is present.
+
+Test an unknown tool name, invalid argument, duplicate refund request, provider timeout and exhausted budget. Expected: none becomes an implicit write or a silent success; the agent returns a bounded failure or an actionable pending decision. Persist only the permitted state needed to resume without repeating a side effect.
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Prompt instructions and structured output alone do not enforce tool permissions; the application must validate and authorize execution.
+- Retrieved documents and tool output are untrusted data, not new authority to change goals or permissions.
+- More agents or more memory can increase failure modes; measure improvement against the simpler design.
+- A trace explains observable actions, not hidden reasoning or proof that the task was completed correctly.

package/bundled-skills/ai-analyzer/SKILL.md

@@ -4,6 +4,7 @@ description: AI驱动的综合健康分析系统，整合多维度健康数据
 allowed-tools: Read, Grep, Glob, Write
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # AI健康分析器

package/bundled-skills/ai-md/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: ai-md
+description: "Convert human-written CLAUDE.md into AI-native structured-label format. Battle-tested across 4 models. Same rules, fewer tokens, higher compliance."
+risk: safe
+source: community
+date_added: "2026-03-11"
+---
+
+# AI.MD v4 — The Complete AI-Native Conversion System
+
+## Detailed Guide
+
+Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
+
+## When to Use This Skill
+
+- Use when your CLAUDE.md is long but AI still ignores your rules
+- Use when token usage is too high from verbose system instructions
+- Use when you want to optimize any LLM system prompt for compliance
+- Use when migrating rules between AI tools (Claude, Codex, Gemini, Grok)
+
+## Limitations
+- Use this skill only when the task clearly matches the scope described above.
+- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.