Token导航 LogoToken导航

Agent Skill · 效率

comonyx-admin(comonyx 管理员)

comonyx-admin 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

comonyx-admin 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在效率类的 21,003 个 Skill 里排第 3,353。

总安装 17,870周安装 730GitHub Stars 公开资料未说明下载 5,782核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.1

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:comonyx-admin(comonyx 管理员)
来源仓库:https://github.com/waqas-orcalo/comonyx-admin
安装命令:
openclaw skills install comonyx-admin
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install comonyx-admin

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

登录 Cosmonyx、获取公司、过滤/导出(PDF 或 Excel)、可选择通过电子邮件发送导出或向过滤的公司发送提醒电子邮件的管理技能。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install comonyx-admin;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

comonyx-admin 怎么安装?

在终端执行 openclaw skills install comonyx-admin。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

comonyx-admin 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

comonyx-admin 需要什么权限?

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

comonyx-admin 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

comonyx-admin 用的人多吗?

公开数据是累计安装 17,870 次,近一周安装 730 次,下载 5,782 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

comonyx-admin 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
comonyx-admin

comonyx 管理员 · 本页

17,870—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
comonyx-admin
description
Admin skill to sign into Cosmonyx, fetch companies, filter/export (PDF or Excel), optionally email the export, or send reminder emails to filtered companies.
metadata
{"openclaw":{"emoji":"🛠️"}}

Cosmonyx Admin – Sign in, Fetch Companies, Export as PDF or Excel

This skill lets an admin sign in to Cosmonyx, fetch all company records using the same endpoints as the Cosmonyx gateway API, then choose to export those records as PDF or Excel, or send reminder emails. Email is sent by this skill’s own script (scripts/send-email.py); see TOOLS.md.

You must run all HTTP requests yourself (no external repos). For structured config (endpoints, run order) you can also load SKILL.yaml from this directory if present, but this SKILL.md is the source of truth for behavior.


Step 0 – Prompt for admin credentials

Before calling any API:

  • Ask once:

- "Please provide your Cosmonyx admin email." - "Please provide your Cosmonyx admin password."

  • Do not echo the password back in any reply. Treat it as sensitive.
  • Use the provided email/password as the sign-in payload.

If the user has already given both an email and password in their initial request, reuse those and do not ask again.


Step 1 – Sign in (admin)

  • POST https://gateway-dev.cosmonyx.co/auth/signin
  • Headers: Content-Type: application/json
  • Body: JSON with the admin credentials you obtained in Step 0, e.g.:

- {"email":"<ADMIN_EMAIL>","password":"<ADMIN_PASSWORD>"}

  • From the response, take the auth token from whichever field exists first:

- accessToken, token, data.token, or data.accessToken

  • Keep this token in memory only and never print it in any reply.

If sign-in fails (4xx/5xx or missing token), stop, explain the error briefly, and ask the user to correct the credentials instead of proceeding.


Step 2 – Fetch all company records

  • GET https://gateway-dev.cosmonyx.co/companies
  • Headers: Authorization: Bearer <TOKEN> where <TOKEN> is from Step 1.
  • Fetch the full list of companies. If the API is paginated:

- Detect pagination from response fields like page, totalPages, links.next, etc. - Request all pages until there are no more, concatenating results.

  • The list may be in:

- data, companies, or the root.

  • Extract the complete list of company objects into an in-memory structure (array of objects).

If there are zero companies, still continue to the export choice but clearly state that the dataset is empty.


Step 3 – Choose action on the records

After fetching all companies, prompt the admin to choose what they want to do:

"What would you like to do with the Cosmonyx company records? 1) List records where complianceStatus is Not Started 2) List records with riskType = Low 3) List records where the primary user’s sumsubVerificationStatus is under_review 4) Send reminder emails to records where complianceStatus is Not Started 5) Send reminder emails to records whose expiryDate is before a given date 6) Work with all records (no filter)"

Step 3A – Filtering logic

Apply filters in memory over the full company list from Step 2:

  • Option 1: compliance not started

- Filter: company.complianceStatus === "Not Started".

  • Option 2: low risk

- Filter: company.riskType === "Low".

  • Option 3: KYC under review

- Filter: company.primaryUser?.sumsubVerificationStatus === "under_review".

  • Option 4: compliance not started (for email)

- Same filter as option 1.

  • Option 5: expiry date before a given date

- Ask once: "Please provide a cutoff date (YYYY-MM-DD). Records with expiryDate earlier than this date will be selected." - Parse the cutoff into a date and filter records where expiryDate is non-null and < cutoff.

  • Option 6: all records

- No extra filter; use the full dataset.

If the filter results in zero records, report that to the user and stop (no export and no emails).

Step 3B – Branching: export vs email

  • If the admin chose 1, 2, 3, or 6, proceed to Step 4 – Export filtered records (PDF or Excel).
  • If the admin chose 4 or 5, proceed to Step 5 – Send reminder emails to the filtered companies.

Step 4 – Export filtered records (PDF or Excel)

Step 4A – Ask export format (PDF vs Excel)

For actions 1, 2, 3, or 6, after filtering:

"I selected N matching companies. How would you like to export these records? 1) PDF file 2) Excel (.xlsx) file"

Interpret the user’s reply:

  • If they answer with "1", "pdf", or similar → choose PDF.
  • If they answer with "2", "excel", "xlsx", or similar → choose Excel.
  • If unclear, ask once for clarification and then proceed.

Step 4B – Generate PDF file (if user chose PDF)

If the user selected PDF:

  • Create a PDF file summarizing all filtered company records (not the full list).
  • At minimum, include a table or clearly formatted list with columns such as:

- id, name, status, country, and any other key fields returned.

  • Save the file into the current user’s Downloads folder so it appears in your normal download location, e.g.:

- $HOME/Downloads/comonyx-companies.pdf

  • Ensure the file contains all filtered companies from Step 3 (not truncated).

When done, reply with:

  1. A short confirmation that admin sign-in succeeded.
  2. A brief summary of how many companies were selected by the filter.
  3. The path and name of the generated PDF file (e.g. $HOME/Downloads/comonyx-companies.pdf) so the user (or tools) can retrieve it.

Then proceed to Step 4D – Optional: Email the exported file.

Do not ask what to do next.


Step 4C – Generate Excel file (if user chose Excel)

If the user selected Excel:

  • Create an Excel .xlsx file listing all filtered company records in a sheet named Companies.
  • Include columns for key fields such as:

- id, name, status, country, email, and any other important fields present in the API response.

  • Each company should be one row.
  • Save the file into the current user’s Downloads folder:

- $HOME/Downloads/comonyx-companies.xlsx

  • Ensure the file contains all filtered companies from Step 3.

When done, reply with:

  1. A short confirmation that admin sign-in succeeded.
  2. A brief summary of how many companies were selected by the filter.
  3. The path and name of the generated Excel file (e.g. $HOME/Downloads/comonyx-companies.xlsx).

Then proceed to Step 4D – Optional: Email the exported file.

Do not ask what to do next.


Step 4D – Optional: Email the exported file (PDF or Excel)

After Step 4B or 4C (once the export file path is known):

  1. Ask once: "Would you like this file emailed to someone? If yes, provide the email address." If the user says no or does not provide an address, skip sending and go to the final reply (Step "Reply format").
  2. If the user provides an email address:

- Use TOOLS.md in this skill directory. Set EMAIL_TO to the address they gave and ATTACHMENT_PATH to the exact path of the generated file (e.g. $HOME/Downloads/comonyx-companies.pdf or $HOME/Downloads/comonyx-companies.xlsx). Expand $HOME to the actual home path if needed (e.g. /home/musawir). - Write the body file: echo "Cosmonyx companies export attached." > /tmp/companies_body.txt - Run the one-line send command from TOOLS.md in a single exec (with EMAIL_TO and ATTACHMENT_PATH set). Use the script in this skill’s scripts/send-email.py (TOOLS.md uses <skill-dir> for the path; resolve that to this skill’s directory). - If send succeeds, confirm in your final reply: "The export was emailed to \<address\>." - If send fails, report the error and still mention where the file was saved.

Do not ask what to do next after sending (or after declining).


Step 5 – Send reminder emails to filtered companies (options 4 and 5)

If the admin chose option 4 or 5 in Step 3:

  1. Use the filtered list from Step 3A.
  2. For each company, determine the email recipient:

- Prefer company.email if non-empty. - Otherwise use company.primaryUser?.email if present. - Skip records that have no email at all.

  1. Ask the admin once for:

- The email subject, e.g. "Compliance onboarding reminder". - The email body template, which may include placeholders like {companyName}, {status}, {expiryDate} – you can do simple string replacements for these placeholders per company.

  1. For each selected company with a recipient address:

- Fill in the template with that company’s values. - Write the final body to a temp file (e.g. /tmp/comonyx-admin-email-body.txt). - Use the email script in this skill’s scripts/send-email.py and the SMTP/recipient settings in this skill’s TOOLS.md. Set EMAIL_TO to that company’s recipient address (and no attachment for reminder emails) before running the send command.

  1. Keep track of how many emails were successfully attempted vs skipped (no email address).

If sending fails due to SMTP issues, report the error and remind the user to configure SMTP_* environment variables (host, port, user, password).


Reply format (final response)

After completing the chosen action (export or sending emails), send one final reply that includes:

  1. Sign-in result – e.g. "Signed in to Cosmonyx as admin successfully."
  2. Filter summary – what option was chosen and how many companies matched (e.g. "Selected 24 companies where complianceStatus is Not Started.").
  3. Outcome:

- For exports: - PDF: "Generated PDF export at $HOME/Downloads/comonyx-companies.pdf." - Excel: "Generated Excel export at $HOME/Downloads/comonyx-companies.xlsx." - If the user asked to email the file and you sent it: "The export was emailed to \<address\>." - For reminder emails (options 4/5): - E.g. "Attempted to send reminder emails to 24 companies; 22 emails sent, 2 skipped due to missing email address."

Do not add follow-up offers like "let me know if you need anything else" or questions about next steps. End after confirming the outcome.

平台分布

OpenClaw

94.46%
按下载量换算5,462

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

未展示

权限和风险

接触敏感数据

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills