计算机操作智能体
io.github.davila7/claude-code-templates/computer-use-agents
构建像人一样操作计算机的 AI 智能体——看屏幕、移动光标、点击按钮、输入文字。覆盖 Anthropic Computer Use、OpenAI Operator/CUA 及开源替代方案,重点关注沙箱化、安全以及基于视觉控制带来的独特挑战。触发场景:computer use、桌面自动化智能体、屏幕控制 AI、视觉智能体、GUI 自动化。
“Access Control” 共 223 个结果
io.github.davila7/claude-code-templates/computer-use-agents
构建像人一样操作计算机的 AI 智能体——看屏幕、移动光标、点击按钮、输入文字。覆盖 Anthropic Computer Use、OpenAI Operator/CUA 及开源替代方案,重点关注沙箱化、安全以及基于视觉控制带来的独特挑战。触发场景:computer use、桌面自动化智能体、屏幕控制 AI、视觉智能体、GUI 自动化。
io.github.google/skills/gke-platform-security
规划、配置并加固平台级的 Google Kubernetes Engine(GKE)集群安全。涵盖集群附加组件(启用 Secret Manager)、RBAC 加固(禁用不安全绑定、审计工具)、Binary Authorization、启用 Shielded Nodes、GKE Sandbox 集群启用、GKE IAM 角色,以及跨服务认证 IAM 模式。用于保障集群控制平面安全、加固 GKE RBAC、启用 Shielded Nodes、启用 GKE Sandbox 运行时、启用集群级安全附加组件,或管理 GKE IAM 角色时。不用于工作负载级安全(Workload Identity、SecretProviderClass、PSS、NetPol、gVisor pod runtimeClassName;改用 gke-workload-security)。
io.github.ruvnet/ruflo/music-connect
One-time setup — mint a Cognitum Music personal access token and register the cogmusic MCP server with Claude Code
io.github.garrytan/gbrain/postgres-adopt
Detect which gbrain engine is in use (PGLite vs Postgres), prefer Postgres for agent-harness installs, install/provision Postgres (Supabase discovery via SUPABASE_ACCESS_TOKEN, local Postgres, opt-in Docker), and move an existing PGLite brain to Postgres with its history (plan, ask, run). Detection is one engine-free command; the install ladder is one flag.
io.github.garrytan/gbrain/postgres-adopt
检测当前 gbrain 使用的是哪种引擎(PGLite 还是 Postgres),在智能体安装场景中优先选择 Postgres,并安装或开通 Postgres(通过 SUPABASE_ACCESS_TOKEN 发现 Supabase、本地 Postgres、需显式选择的 Docker),再用受保护的引擎迁移把已有的 PGLite brain 搬移过去。检测只需一条与引擎无关的命令,安装阶梯也只需一个参数。
io.github.K-Dense-AI/scientific-agent-skills/biopython
Provides Biopython workflows for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Supports batch processing, custom molecular-biology pipelines, BLAST automation, structure analysis, and motif analysis.
io.github.K-Dense-AI/scientific-agent-skills/imaging-data-commons
Queries and downloads public cancer imaging data from NCI Imaging Data Commons. Supports IDC collection discovery, DICOM access, radiology (CT, MR, PET) and pathology AI datasets, metadata SQL, visualization, licensing, and citations. Uses public metadata and download routes without authentication; optional BigQuery and Google Healthcare routes require Google credentials.
io.github.K-Dense-AI/scientific-agent-skills/datamol
RDKit 的 Pythonic 封装,接口更简单、默认值更合理。标准药物发现任务的首选:SMILES 解析、标准化、描述符、指纹、聚类、3D 构象、并行处理。返回原生 rdkit.Chem.Mol 对象。需要高级控制或自定义参数时直接使用 rdkit。
io.github.K-Dense-AI/scientific-agent-skills/paper-lookup
在 11 个学术文献 API 中检索论文、预印本、引用与开放获取全文,并返回可复现的溯源结果。覆盖 PubMed、PMC(全文)、Europe PMC(全文与预印本检索)、bioRxiv、medRxiv、arXiv、OpenAlex、Crossref、Semantic Scholar、CORE、Unpaywall。适用于检索论文、引用、DOI/PMID/arXiv、摘要、全文、开放获取 PDF、预印本、引用网络、作者发文或任何学术文献查询。提及任一受支持数据库,或“find papers on X”“look up this DOI”“who cites this paper”“get me the PDF”等请求会触发。
io.github.affaan-m/ECC/quarkus-patterns
Quarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing. Use for Java Quarkus backend work with event-driven architectures. Use when building or reviewing a Quarkus service, especially with Camel messaging or Panache data access.
io.github.affaan-m/ECC/springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work. Use when building or reviewing a Spring Boot backend — REST layer, services, data access, caching, or async work.
io.github.affaan-m/ECC/backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
io.github.n8n-io/n8n/create-agent-builder-eval
Authors and calibrates Instance AI evaluations that build standalone n8n Agents through Agent Builder. Use when a change under packages/cli/src/modules/agents affects build-agent routing, Agent setup, model or credential selection, tools, MCP servers, integrations, skills, tasks, testing, or user-facing build responses. Requires LangTracer access before authoring so each finished case can be published.
io.github.n8n-io/n8n/intent-recognition
通过两个判断对自动化请求分类:anchor(哪个原语掌握顶层控制流——工作流为锚、代理为锚、需澄清,或超出范围)与 embeds_other(另一原语是否内嵌出现——工作流中嵌入一个 agent 步骤,或代理把某个工作流当作工具调用)。每当当前轮次需要选定或重新判定某个自动化请求的意图时都必须使用,包括复合请求、构建过程中新引入的独立自动化、需要查询无法直接访问的外部系统的一次性提问或报告,以及在确定 anchor 前需要澄清的请求。当对话已明确面向某个工作流或 Agent 时,不要为常规编辑或扩展加载本技能。
io.github.affaan-m/ECC/healthcare-phi-compliance
Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak vectors such as logs, URLs, and browser storage. Use when code touches patient or clinician data, when implementing HIPAA or GDPR access controls, or when auditing a healthcare system for data exposure.
io.github.affaan-m/ECC/homelab-network-readiness
Readiness checklist for homelab VLAN segmentation, local DNS filtering (Pi-hole, AdGuard Home), and WireGuard-style remote access. Use when planning or reviewing home network changes — splitting a flat network into trusted, IoT, guest, or management VLANs, moving DHCP to a local resolver, or adding VPN access — before changing router, firewall, DHCP, or VPN configuration.
io.github.affaan-m/ECC/team-agent-orchestration
使用工作项、归属、代理看板、合并门槛与控制台交接,为代理小队运行基于团队的编排。在以工作项、归属、看板和合并门槛协调代理小队时使用。
io.github.odoo/odoo/odoo-security
Security audit of Odoo addon code: access control (ir.access, field groups, sudo), injection (SQL, domain, eval, XSS via Markup/markup()), untrusted public methods/RPC, controller auth/CSRF, file access, deserialization, returning complex objects, getattr/setattr, timing attacks. Use when auditing an addon, or judging whether a specific construct (a sudo, raw SQL, a route, ...) is safe.
io.github.odoo/odoo/odoo-guidelines
House rules for Odoo addon code: module structure, manifest, Python/ORM, fields, controllers, XML views and data, QWeb reports, access rights and record rules, performance, tests. Use when writing or reviewing any file in an Odoo addon outside static/ (for the JavaScript, Owl templates and SCSS under static/, see odoo-web-guidelines).
io.github.stablyai/orca/computer-use
通过 orca computer 对可见的本地应用窗口进行 OS/窗口级检视与输入:原生应用、外部浏览器窗口(Chrome、Edge、Safari)和应用 webview。不适用于 Orca 内置浏览器(用 orca-cli)或纯页面自动化(用 Playwright 或 CDP)。
io.github.affaan-m/ECC/backend-patterns
面向 Node.js、Express 和 Next.js API 路由的后端架构模式、API 设计、数据库优化与服务端最佳实践。当构建或审阅 Node.js、Express、Next.js 的 API 路由及其数据访问时使用。
io.github.CopilotKit/CopilotKit/react-core
@copilotkit/react-core——在 Next.js App Router / React Router v7 / TanStack Start / SPA 应用中挂载 CopilotKit provider(来自 @copilotkit/react-core/v2),接入 CopilotChat/CopilotPopup/CopilotSidebar(v2 聊天组件由 react-core/v2 提供,而非仅有 CSS 的 react-ui),通过 useAgent/useAgentContext/useCapabilities 访问和订阅 agent,在多个 agent 间切换,用 useThreads 管理持久的 Intelligence 会话线程,通过 useFrontendTool 注册浏览器端工具,用 useRenderTool/useComponent/useDefaultRenderTool 渲染工具调用,用 useHumanInTheLoop 做执行门控,用 useAttachments 接入文件附件,配置建议词,以及注册活动与自定义消息渲染器。publicLicenseKey 为正式字段(publicApiKey 是已废弃别名)。按任务加载 references/ 下对应的参考文件。
io.github.PostHog/posthog/modifying-taxonomic-filter
指导安全修改 TaxonomicFilter——PostHog 用于事件、action、属性、群组等的多标签选择器。先讲清经验性的产品现实(用户实际挑选和搜索什么)以及三个在用变体(legacy-control、藏在 TAXONOMIC_FILTER_CATEGORY_DROPDOWN 开关后的 legacy-pill、藏在 TAXONOMIC_FILTER_MENU_REBUILD 后的自选重构菜单),让改动以真实行为为评判标准并在多个界面镜像同步,而不是孤立地针对一支实现。在新增功能、修 bug 或重构 TaxonomicFilter、重构菜单或无头筛选面板时使用。
io.github.serverless/serverless/serverless-mcp
使用 Serverless Framework 内置的 MCP 支持,将 Model Context Protocol(MCP)服务器托管到 AWS——基于官方 SDK 的服务器模块,部署到 AWS Lambda 的流式 API Gateway REST 端点后,自带网关访问控制与 OAuth protected-resource 发现,打包和 elicitation 状态均已代为实现。当用户要在 AWS 或 Lambda 上部署、托管、加固或调试 MCP 服务器,编写或编辑 serverless.yml 中的 `mcp:` 配置块,通过 HTTP 向 Claude 或其他 AI 客户端暴露 tools、resources 或 prompts,或遇到 `MCP_*` 配置错误(MCP_UNSUPPORTED_NODE_RUNTIME、MCP_FUNCTION_NAME_COLLISION、MCP_INVALID_STATE_ARN 等)时使用。即使用户没有点名 Serverless Framework 或 MCP,只要描述把自有工具通过 HTTPS 端点提供给 AI 客户端,也应触发。