Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计提醒

adversusadversus 搜索

Agent Skill

adversus 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

674

周安装

27

GitHub Stars

31

下载量

218
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:adversus(adversus 搜索)
来源仓库:https://github.com/membranedev/application-skills
仓库路径:skills/adversus
安装命令:
npx skills add https://github.com/membranedev/application-skills --skill adversus
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/membranedev/application-skills --skill adversus

简介

adversus 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词、任务场景或来源线索进行信息检索的研究与数据收集场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态,注意是否涉及联网、命令执行或文件读写操作。
  • adversus 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Adversus

Adversus is a competitive intelligence platform. It helps businesses monitor and analyze their competitors' strategies, marketing efforts, and overall market presence. This allows product managers and marketing teams to make data-driven decisions.

Official docs: https://www.adversus.io/api-documentation

Adversus Overview

  • Case

- Case Note

  • Contact
  • Task
  • User
  • Template
  • Document
  • Billing Rate
  • Expense
  • Invoice
  • Payment
  • Time Entry
  • Product and Service
  • Trust Request
  • Email
  • Phone Number
  • Address
  • Firm Setting
  • Integration
  • Role
  • Permission
  • Note
  • Journal Entry
  • Account
  • Tax Rate
  • Vendor
  • Client Request
  • Lead
  • Referral
  • Activity
  • Marketing Campaign
  • Form
  • Form Submission
  • Automation
  • Tag
  • Checklist
  • Checklist Template
  • Court
  • Judge
  • Opposing Party
  • Settlement
  • Medical Record
  • Insurance Policy
  • Property
  • Vehicle
  • Will
  • Trust
  • Power of Attorney
  • Healthcare Directive
  • Contract
  • Intellectual Property
  • Financial Account
  • Safe Deposit Box
  • Digital Asset
  • Pet
  • Personal Property
  • Life Insurance Policy
  • Retirement Account
  • Document Template
  • Email Template
  • SMS Template
  • Report
  • Dashboard
  • Workflow
  • Workflow Template
  • Stage
  • Stage Template
  • Custom Field
  • Custom Field Template
  • Relationship
  • Relationship Type
  • Matter Type
  • Task Template
  • Event
  • Event Template
  • User Group
  • Goal
  • Key Result
  • Scorecard
  • Survey
  • Survey Template
  • Question
  • Question Template
  • Answer
  • Answer Template
  • Clause
  • Clause Library
  • Fee Schedule
  • Fee
  • Tax
  • Discount
  • Credit
  • Escrow Account
  • Escrow Transaction
  • User Subscription
  • Plan
  • Add-on
  • Coupon
  • Integration Setting
  • Notification
  • Audit Log
  • Data Import
  • Data Export
  • Firm User
  • Firm
  • Office
  • Department
  • Practice Area
  • Source
  • Language
  • Country
  • State
  • City
  • Zip Code
  • Area Code
  • Phone Type
  • Email Type
  • Address Type
  • Note Type
  • Task Status
  • Task Priority
  • Event Type
  • Relationship Status
  • Payment Type
  • Invoice Status
  • Case Status
  • Lead Status
  • Referral Status
  • Trust Request Status
  • Client Request Status
  • Marketing Campaign Status
  • Form Status
  • Automation Status
  • Checklist Status
  • Workflow Status
  • Stage Status
  • Goal Status
  • Key Result Status
  • Survey Status
  • Question Type
  • Answer Type
  • Custom Field Type
  • Document Category
  • Email Category
  • SMS Category
  • Report Category
  • Dashboard Category
  • Workflow Category
  • Stage Category
  • Task Category
  • Event Category
  • Goal Category
  • Key Result Category
  • Survey Category
  • Question Category
  • Answer Category
  • Clause Category
  • Fee Category
  • Tax Category
  • Discount Category
  • Credit Category
  • Escrow Account Category
  • User Subscription Category
  • Plan Category
  • Add-on Category
  • Coupon Category
  • Integration Setting Category
  • Notification Category
  • Activity Type
  • Activity Category
  • Product and Service Category
  • Template Category
  • Document Template Category
  • Email Template Category
  • SMS Template Category
  • Report Template Category
  • Dashboard Template Category
  • Workflow Template Category
  • Stage Template Category
  • Task Template Category
  • Event Template Category
  • Goal Template Category
  • Key Result Template Category
  • Survey Template Category
  • Question Template Category
  • Answer Template Category
  • Clause Template Category
  • Fee Template Category
  • Tax Template Category
  • Discount Template Category
  • Credit Template Category
  • Escrow Account Template Category
  • User Subscription Template Category
  • Plan Template Category
  • Add-on Template Category
  • Coupon Template Category
  • Integration Setting Template Category
  • Notification Template Category

Use action names and parameters as needed.

Working with Adversus

This skill uses the Membrane CLI to interact with Adversus. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run membrane from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add --json to any command for machine-readable JSON output.

Agent Types: claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Adversus

Use membrane connection ensure to find or create a connection by app URL or domain:

membrane connection ensure "https://adversus.io" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has state: "READY", skip to Step 2.

1b. Wait for the connection to be ready

If the connection is in BUILDING state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

The resulting state tells you what to do next:

  • READY — connection is fully set up. Skip to Step 2.
  • CLIENT_ACTION_REQUIRED — the user or agent needs to do something. The clientAction object describes the required action: After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get <id> --json to check if the state moved to READY.

- clientAction.type — the kind of action needed: - "connect" — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections. - "provide-input" — more information is needed (e.g. which app to connect to). - clientAction.description — human-readable explanation of what's needed. - clientAction.uiUrl (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present. - clientAction.agentInstructions (optional) — instructions for the AI agent on how to proceed programmatically.

  • CONFIGURATION_ERROR or SETUP_FAILED — something went wrong. Check the error field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

NameKeyDescription
Add Activity to Leadadd-activity-to-leadAdd an activity to a lead in Adversus
Add Note to Leadadd-note-to-leadAdd a note to a lead in Adversus
Assign Lead to Campaignassign-lead-to-campaignAssign a lead to a campaign in Adversus
Change Lead Statuschange-lead-statusChange the status of a lead in Adversus
Get Leadget-leadRetrieve a lead by ID from Adversus
Update Leadupdate-leadUpdate an existing lead in Adversus
Create Leadcreate-leadCreate a new lead in Adversus
List Campaignslist-campaignsRetrieve a list of campaigns for the authenticated user
Get Organizationget-organizationRetrieve organization details for the authenticated user

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Adversus API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

membrane request CONNECTION_ID /path/to/endpoint

Common options:

FlagDescription
-X, --methodHTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
-H, --headerAdd a request header (repeatable), e.g. -H "Accept: application/json"
-d, --dataRequest body (string)
--jsonShorthand to send a JSON body and set Content-Type: application/json
--rawDataSend the body as-is without any processing
--queryQuery-string parameter (repeatable), e.g. --query "limit=10"
--pathParamPath parameter (repeatable), e.g. --pathParam "id=123"

Best practices

  • Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
  • Discover before you build — run membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
  • Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.25%
按下载量换算72

Claude

29.67%
按下载量换算65

Cursor

17.89%
按下载量换算39

Gemini CLI

9.71%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills