Results for “agent reach”

Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "agent auth", "streaming", "VPC", "VPC connectivity", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "migration issue", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "add payments capability to my agent", "wire payments plugin", "integrate x402 payments with the agent I'm building", "add MPP payments", "Machine Payments Protocol". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI/dev-server errors: use agents-debug. Runtime x402/MPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.

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

Cross-framework enhancement overlay for choosing a multi-agent topology BEFORE writing any agent. A binary-question rubric — is single-agent + tools enough? do agents need to know about each other? does the output need one voice? — maps the answer to single-agent / supervisor / swarm / sequential / hierarchical. Activates when a coder agent is tempted to "split the work into roles" or reaches for a multi-agent framework. Encodes the *selection rubric* that the per-framework skills assume but never surface. Search keywords: when to use multi-agent, single vs multi agent, do I need multiple agents, supervisor vs swarm, multi-agent vs single agent, agent team design.

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

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.

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

Create and audit the files and routines that guide coding agents across sessions. It organizes instructions, progress tracking, verification, scope boundaries, and handoffs, with scripts for setup, structural checks, and shareable assessment reports.

• Creating AGENTS.md or CLAUDE.md and supporting files
• Preserving progress between agent sessions
• Defining checks required before work is marked complete

Integrate Java business systems with ReachAI SDK registration, SDK instance heartbeat, gateway/embed access, and optional API Management handoff. Use when asked to connect a Spring Boot service to ReachAI, add reachai-capability-sdk or reachai-spring-boot2-starter, configure reachai.registry/reachai.project/reachai.capability, prepare @ReachCapability metadata for later manual SDK sync, or verify SDK onboarding from a ReachAI manifest.

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

🇺🇸 KOL Outreach & Influencer Marketing Playbook — Complete SOP from discovery to ROI tracking. Battle-tested with 200+ KOL campaigns at AFFiNE (60k stars). Includes pricing benchmarks, email templates, content packages, platform algorithm guides, and data-driven evaluation frameworks. 🇨🇳 KOL 外联与红人营销实战手册 — 从发现筛选到 ROI 追踪的完整 SOP。基于 AFFiNE（60k stars）200+ 次 KOL 合作实战验证。包含报价基准、邮件模板、内容包模板、各平台算法指南、数据评估体系。 🇯🇵 KOLアウトリーチ＆インフルエンサーマーケティング実践ガイド — 発見からROI追跡までの完全SOP。AFFiNE（60k stars）での200回以上のKOLキャンペーン実績。価格ベンチマーク、メールテンプレート、コンテンツパッケージ、プラットフォームアルゴリズムガイド。 🇰🇷 KOL 아웃리치 & 인플루언서 마케팅 플레이북 — 발굴부터 ROI 추적까지 완전한 SOP. AFFiNE(60k stars) 200+ KOL 캠페인 실전 검증. 가격 벤치마크, 이메일 템플릿, 콘텐츠 패키지, 플랫폼 알고리즘 가이드. Triggers: "KOL outreach" | "influencer marketing" | "KOL campaign" | "influencer outreach" | "creator partnership" | "KOL strategy" | "red人" | "红人营销" | "KOL合作" | "达人合作" | "influencer pricing" | "KOL ROI" | "content creator outreach" | "KOL筛选"

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

Audits GitHub Actions workflows that run AI coding agents. Traces how attacker-controlled content reaches prompts, checks permissions and sandbox settings, and reports evidence, severity, and fixes for prompt injection and related configuration risks.

• Reviewing workflows that run AI coding agents
• Tracing issue and PR content into agent prompts
• Checking sandbox settings and user allowlists

Coordinate multiple AI agents in a mesh, a network where peers communicate directly. It guides shared decisions, task assignment based on skills and workload, network monitoring, and recovery when agents fail or connections break.

• Coordinating agents through direct peer communication
• Redistributing work from overloaded agents
• Planning recovery from agent failures

Review GitHub Actions workflows that run AI agents, tracing how external input reaches prompts and tools. Produce findings with evidence, severity, impact, and remediation guidance through static analysis, which examines configuration without running attacks.

• Auditing AI agent integrations in GitHub Actions
• Tracing issue and PR text into agent prompts
• Reviewing sandbox settings and tool permissions

Plan personalized sales emails to prospects you have not contacted before. This skill covers prospect selection, contact research, email drafts, follow-up sequences, inbox delivery, and reply handling, with guidance on tools and campaign improvements.

• Drafting personalized sales emails for new prospects
• Planning a sequence of emails and follow-ups
• Investigating low reply rates or spam placement

Audit whether an AI agent follows its intended purpose, business rules, and permission boundaries. The skill guides setup discovery, test configuration, execution against an agent endpoint or substitute model, and interpretation of scores from selected judging models.

• Auditing an agent's compliance with business rules
• Testing permission boundaries and dangerous tools
• Evaluating an agent through its HTTP endpoint

Plan personalized video outreach for prospective customers, from useful sample deliverables and short scripts to tool selection and follow-up sequences. Use viewing data to guide next steps and design product demos prospects can watch independently.

• Add personalized videos to cold outreach
• Choose video tools for sales volume and budget
• Plan recorded demos prospects can watch independently

Inspect production AI agents in FailproofAI Cloud using the fp CLI. Review errors, run histories, quality scores, and usage, then manage issues, audits, user access, and scoped API keys for the team's deployment.

• Investigating failed agent runs
• Checking for drops in quality scores
• Running audits and triaging findings

Instrument Python or TypeScript agents to record runs for Failproof AI, verify local event files, and troubleshoot missing sessions. The skill also guides building evaluator workers that score completed runs on your own infrastructure.

• Planning where an agent should record events
• Adding run logging to an existing agent
• Troubleshooting missing events or sessions

Switch the Manager Agent's primary language model with a script that checks connectivity before saving configuration. You can also set how much context the model accepts and whether extended thinking is enabled.

• Change the Manager's saved primary model
• Correct a model's context window setting
• Disable extended thinking for a model

Gather web pages, social discussions, job listings, video subtitles, and other online material across 16 platforms. The skill checks available connections and guides the agent to suitable command-line tools or APIs for retrieving content.

• Collecting discussions about a topic across social platforms
• Retrieving articles and RSS content
• Finding job listings on LinkedIn and Boss直聘

Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.

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

Ready-to-use KOL cold outreach templates — DM scripts for Twitter, email pitches, and follow-up sequences designed to get replies from busy influencers. Tested across 500+ creator partnerships. By @WeiYipei.

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

Create and troubleshoot Ocana agents. Use when creating a new Ocana agent, refreshing/repairing management token auth, diagnosing `ocana_agent_create` failures, checking `gatewayReachable`, handling agents stuck in `provisioning`, debugging `226/NAMESPACE` or missing `/usr/bin/openclaw`, or testing lifecycle/reprovision flows for a newly created agent.

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

Audit a compliance-ladder design (C0-C6) and transcript-fidelity ladder (T0-T5) plus their adapter conformance fixtures — Codex, Claude Code, Cloudflare, Ollama/LM Studio, custom stdio/HTTP agents — for the two failure modes that make a C-badge or T-fidelity label a lie: the ladder disagreeing with itself across doc/schema/ui/probe surfaces, and a level being reachable by self-report because no daemon-witnessed negative probe actually tries to forge it. Use when designing or freezing a compliance ladder, wiring an adapter conformance probe suite, deciding whether a numeric C-badge or T-label is safe to ship, or investigating a self-attestation or observed-to-controlled bypass risk. NOT for auditing a cryptographic protocol or whitepaper for adversarial soundness (`redteam-review`), writing TLA+/formal invariants for a daemon monitor (`runtime-verification-for-agents`), or agent identity, successor linkage, and reputation across restarts (`agent-identity-continuity-reputation`).

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

Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.

• Verify adapter behavior after code changes
• Test task execution and team recovery
• Check that skills reach child tasks

Use the CopilotKit CLI to check app connections, credentials, and agent responses before investigating code. It also guides project creation, integration into existing apps, hosted project selection, typed agent identifier generation, and thread history imports.

• Diagnosing CopilotKit connection and authentication failures
• Creating a new CopilotKit project
• Adding CopilotKit to an existing app

Guide an agent's work in Rowboat Spaces, a team chat for people and agents. Covers reading and replying to threads, notifying members, handing off tasks, and editing shared files through the service's tools.

• Responding to requests in team chat
• Handing tasks to people or agents
• Finding past conversations and shared files

Run CARLA routes with a driving agent through ScenarioRunner, including scenarios available only in route mode. Inspect route contents, execute one or all routes, and obtain reports on completion, collisions, traffic lights, and other criteria.

• Test a driving agent on a specific route
• Find routes containing accident or obstacle scenarios
• Run Leaderboard scenarios without its scoring