Results for “capa”

Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.

The English summary is being prepared. Showing the original description.

Forecast infrastructure and application metrics using Prophet or statsmodels for capacity planning, cost optimization, and proactive scaling. Visualize predictions in Grafana and set up alerts for projected resource exhaustion. Use when forecasting infrastructure capacity needs for CPU, memory, or disk, planning hardware procurement for next quarter, predicting cost trends to optimize cloud spending, or setting up proactive scaling policies based on predicted load.

The English summary is being prepared. Showing the original description.

Design an A2A Agent Card (.well-known/agent.json) manifest describing agent capabilities, skills, authentication requirements, and supported content types. Use when building an agent that must be discoverable by other A2A-compliant agents, exposing capabilities for multi-agent orchestration, migrating an existing agent to the A2A protocol, defining the public contract for an agent before implementation, or integrating with agent registries that consume Agent Cards.

The English summary is being prepared. Showing the original description.

Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydantic_ai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents from YAML, or test agent behavior.

The English summary is being prepared. Showing the original description.

Assesses agent capabilities by analyzing agent files and determining what tasks they can handle. Use when you need to evaluate if an existing agent can handle a task or if a new agent is needed. Reviews agent descriptions, skills, and workflows to determine capability match.

The English summary is being prepared. Showing the original description.

"Apply the Dynamic Capabilities framework (Teece et al., 1997) — sensing, seizing, and transforming — to analyze how firms adapt, integrate, and reconfigure competences in rapidly changing environments. Use this skill when the user needs to explain why some firms sustain advantage while others decline, evaluate organizational agility, distinguish operational from strategic capabilities, or when they ask 'how do we stay competitive as the market shifts', 'why did this firm fail to adapt', or 'what capabilities do we need to build'.".

The English summary is being prepared. Showing the original description.

"Calculate Cpk process capability index to assess whether a process meets specification requirements. Use this skill when the user needs to evaluate process capability, compare processes, or determine if quality targets are achievable — even if they say 'can our process meet spec', 'process capability', or 'Cpk calculation'.".

The English summary is being prepared. Showing the original description.

Analyzes a PE file's import and export tables to infer capability: mapping imported APIs to behaviors (networking, crypto, injection, persistence), spotting dynamic-resolution stubs, and reading exports of malicious DLLs. Activates for requests to analyze PE imports, inspect the IAT/exports, or infer capability from API usage.

The English summary is being prepared. Showing the original description.

Analyzes remote access trojan command-and-control by mapping the RAT command set, identifying the C2 transport and beacon parameters, and cataloging operator capabilities from static strings and config. Activates for requests to analyze RAT C2, map a trojan command handler, or identify remote-access capabilities and C2 transport.

The English summary is being prepared. Showing the original description.

Research one agent harness's release (docs, source, runtime) and fill its capability cells in scripts/harness_capabilities.py with cited evidence. Use after a harness version bump, when just harness-probe reports re-research, or when capability cells read unknown.

The English summary is being prepared. Showing the original description.

Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.

The English summary is being prepared. Showing the original description.

Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.

The English summary is being prepared. Showing the original description.

Designs, reconciles, and reviews an end-to-end Drydock program for safely staging agent runtimes: immutable worktree provenance, disposable VM containment, typed effect brokerage, global body accounting, resurrection, subscription-capacity economics, context compaction, operator control, evidence, and promotion. Use when several Drydock contracts must compose into one architecture, implementation hypertree, diagram set, or release plan. NOT for launching Port Daddy, running an untrusted subject, replacing focused containment/resurrection/capacity audits, or treating a design packet as runtime authority.

The English summary is being prepared. Showing the original description.

Ranks eligible skill candidates with explicit retrieval evidence, capability coverage, and uncertainty. NOT for discovery, authorization, or execution planning.

The English summary is being prepared. Showing the original description.

Design discovery, directories, and guilds for agent swarms at scale. Use when agents need to find each other on a shared surface: capability indices, yellow-pages directories, whois/phonebook routing, reputation-aware discovery, and guild structures that scope trust. Covers the canonical prior art (FIPA Directory Facilitator, Contract Net, Chord/DHT, DNS-SD/Consul, EigenTrust, Greif's merchant guilds) and the failure modes (read-poverty, Sybil reset, Goodhart on rank, directory staleness, cold-start). Triggers: "agents can't find each other", "who owns this file/skill", "route a question to the right agent", "capability registry", "agent reputation", "guild / federation of fleets". NOT for issuing identities, granting authority, or automatically assigning work from a directory entry.

The English summary is being prepared. Showing the original description.

Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.

The English summary is being prepared. Showing the original description.

Investigate queued or slow OpenClaw CI jobs, the automated checks run during development. Use measured evidence to adjust runner capacity, registration budgets, parallel job limits, test grouping, and placement between GitHub-hosted runners and Blacksmith.

• Investigate why OpenClaw CI jobs are queued
• Estimate runner registrations during a burst
• Adjust parallel limits and test grouping

Audit repository settings, connected tools, and the agent's runtime setup to show what is usable now. Identify missing workflows and integrations, then recommend prioritized ECC skills, automation hooks, agents, or tool connections.

• Reviewing the current setup before configuring Claude Code
• Listing connected tools and available capabilities
• Checking whether more plugins are needed

Turn product requests and planning documents into a concrete development plan. Document business rules, data ownership, service interfaces, and unresolved decisions so teams can see what must be settled before implementation begins.

• Turning a product requirements document into development requirements
• Aligning requirements for a feature spanning multiple services
• Documenting assumptions that repeatedly surface in reviews

Coordinate a new feature from research and planning through tests, implementation, review, and commit. Assign phases to matching ECC agents, write failing tests before implementation, and pause for approval of the plan and before committing.

• Adding a capability that does not exist yet
• Implementing a feature with tests written first
• Reviewing an authentication feature for security

Check live H100 or H200 GPU availability, request fixed-rate quotes, and review procurement status through the canonical Itô client. It also supports device credential revocation and explicitly authorized node checks; quote requests do not reserve capacity.

• Checking H100 or H200 availability
• Requesting a fixed-rate compute quote
• Reviewing quote and procurement status

Define success criteria before AI coding, then assess new capabilities and check that existing behavior still works using code, rules, models, or human review. Track repeated-attempt success metrics and reports to compare prompt changes, agent changes, or model versions.

• Defining success criteria before AI implementation
• Checking existing behavior after prompt or agent changes
• Measuring reliability across repeated attempts

Turn an unclear feature idea into a structured specification with goals, boundaries, and testable success criteria. Split broader requests into independent modules when needed, then move through planning, task breakdown, and implementation with human review.

• Clarify an idea before coding
• Draft requirements with testable completion criteria
• Split a broad request into independent modules

Prepare media assets required by an existing OD Next plan. Reuse verified capabilities and suitable assets, acquire files, measure dimensions, and retrieve background job results while preserving required content, licensing constraints, and quality conditions.

• Preparing all media assets required by an existing plan
• Reusing suitable user assets across multiple pages
• Measuring asset dimensions for layout sizing