安全vibeccc

SKILL运维和基础设施
运维和基础设施 未标注权限 许可证不明确
安装这个技能

Resolve company IP ownership and usage type across internal infrastructure systems, including batch IP queries grouped by server IP, VIP, SNAT, and office egress results. Use when asked to identify whether one or more IPs are server IPs, VIPs, or load-balancer SNAT pool addresses; determine business ownership; route queries by /24 network; explain CMDB/LBM exact hits; or add ES access/link records as relationship evidence without treating ES as ownership truth.

一句话选型结论

按资料字段整理

安全vibeccc是运维和基础设施类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类运维和基础设施 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_39b26c07/securityzzzz
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

运维和基础设施
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_39b26c07仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 1791619580
正文体量8.9 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
查服务与日志

按现象定位服务状态与日志线索。

写部署与巡检脚本

把重复的部署、巡检写成脚本。

故障排查

按步骤排查网络、依赖与配置。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在运维和基础设施场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
安全vibeccc当前 未标注权限 未标注 未标注 未标注 有
Azure 部署 调用外部服务 GitHub 仓库 664.2 万 Codex、Claude、Cursor 有
Azure diagnostics 问题管理 调用外部服务 GitHub 仓库 657.6 万 Codex、Claude、Cursor 有
Azure aigateway 部署 调用外部服务 GitHub 仓库 655.3 万 Codex、Claude、Cursor 有
Azure AI 搜索 调用外部服务 GitHub 仓库 651.4 万 Codex、Claude、Cursor 有
Azure Cloud migrate 部署 调用外部服务 GitHub 仓库 650.7 万 Codex、Claude、Cursor 有

SKILL.md 全文

8.9 KB
模型实际读到的说明书原文,来自技能仓库

Query Company IP Info

Use this skill to answer company IP questions with a fixed ownership pipeline:

CMDB server IP -> LBM VIP -> LBM SNAT pool -> Office egress IP

For two or more IPs, use scripts/query_ips.py first. It queries CMDB, LBM VIP, and LBM SNAT in batch where supported, then groups the output into server IP, VIP, SNAT/load-balancer address, office egress fallback, conflict/multi-use, and not-found sections. Use the single-source scripts only when debugging one source or when the user explicitly asks for raw source output.

Before running the default sequence, match the IP against references/ip-routing.md. A CIDR match only chooses the first system to query. Never use a CIDR match as final ownership without an exact record from CMDB or LBM.

First Step

Before any CMDB or LBM query, remind the user to inject their own Yunwei platform credentials when the current environment does not already provide them:
URL: https://yunwei.eastmoney.com/account/password

export YUNWEI_API_KEY=...
export YUNWEI_API_SECRET=...

Use this shared key/secret pair for both CMDB and LBM. CMDB signs request parameters with _key/_secret; LBM sends the same pair as Authorization: Bearer <key>:<secret>. Do not ask users to configure separate CMDB and LBM credentials unless their environment explicitly requires service-specific overrides.

Required Output Tables

Always present ownership results as Markdown tables with the exact section names and column names below. Do not replace these tables with bullet summaries, and do not rename columns. For batch queries, keep one section per result type; if a batch contains both machine IPs and VIPs, show both sections.

Server IPs - CMDB exact hits:

| CI | 内网IP | IDC | 部门 | 开发负责人 | 运维负责人 |
| --- | --- | --- | --- | --- | --- |

VIPs - LBM exact hits:

| vip | port | isp | department | idc | server_room | device_name | device_type |
| --- | --- | --- | --- | --- | --- | --- | --- |

SNAT/LB addresses - LBM exact hits:

| ip | isp | idc | server_room | purpose | device_type |
| --- | --- | --- | --- | --- | --- |

Office egress fallback:

| 查询IP | 出口IP/网段 | 名称 | 备注 |
| --- | --- | --- | --- |

When an IP has exact records in more than one authoritative source, show it in every matching section and add a conflict or multi-use note. Office egress is a fallback table only after CMDB server, LBM VIP, and LBM SNAT have no exact hit.

Render LBM IP links with these URLs:

VIP:  https://yunwei.eastmoney.com/lbm2/platform/vs-board?vip=<vip>
SNAT: https://yunwei.eastmoney.com/lbm2/lb-address/list?ip=<ip>

Query Workflow

  1. Check whether YUNWEI_API_KEY and YUNWEI_API_SECRET are available before CMDB/LBM queries. If not, tell the user to export them first.
  2. Normalize the input as a single IP, CIDR, hostname/link, business name, or time-bounded access question.
  3. If the input contains multiple IPs, run:
    bash python3 scripts/query_ips.py <ip1> <ip2> ...
    Then present the grouped sections directly, preserving conflicts when an IP has both machine and VIP/SNAT exact records.
  4. If the input contains one IP, match it against references/ip-routing.md.
  5. Query the routed source first when a route exists:
    - cmdb_server for physical or virtual server IPs.
    - lbm_vip for internal or external VIPs.
    - lbm_snat for HA/F5/load-balancer SNAT pool addresses.
  6. If the routed source has no exact hit, still fall back through the remaining default sequence:
    text CMDB server IP -> LBM VIP -> LBM SNAT pool -> Office egress IP
  7. If ES evidence is requested or useful, query ES only for access/link relationships. Treat ES as behavior evidence, not ownership evidence.
  8. After a CMDB exact server hit, let scripts/query_cmdb.py or scripts/query_ips.py auto-learn that IP's /24 as a cmdb_server route in references/ip-routing.md, unless --no-update-routes is used.
  9. After an LBM VIP exact hit, let scripts/query_lbm_vip.py or scripts/query_ips.py auto-learn that IP's /24 as an lbm_vip route, unless --no-update-routes is used.
  10. After an LBM SNAT exact hit, let scripts/query_lbm_snat.py or scripts/query_ips.py auto-learn that IP's /24 as an lbm_snat route, unless --no-update-routes is used.
  11. If a learned route conflicts with an existing route for the same CIDR, do not overwrite it; report that manual confirmation is required.
  12. If CMDB and LBM have no exact hit, query scripts/query_office_egress.py as the final local shared source. This script refreshes the office egress cache first when the local cache is missing or older than its TTL.
  13. Merge exact ownership hits and relationship evidence into the standard answer format in references/output-format.md.

Ownership Rules

  • Use CMDB as the ownership source for server IPs, including physical machines and virtual machines.
  • Use LBM as the ownership source for VIPs, including internal VIPs and external VIPs.
  • Use LBM as the ownership source for SNAT pool addresses, including HA and F5 SNAT IPs.
  • Use references/office-egress-ips.md as the shared local cache for office egress IPs and CIDRs.
  • Present office egress hits as fixed Markdown tables, matching the CMDB virtual server display style. Do not summarize office egress hits as loose bullets.
  • Treat /24 or other CIDR routes as query hints only.
  • Do not auto-learn office egress entries into ip-routing.md; update them through scripts/update_office_egress.py or the company source.
  • Treat ES records as relationship evidence only: source IP, destination IP/VIP, URL/link, port, timestamp, and counts.
  • When ES contains an IP whose ownership matters, resolve that IP through CMDB or LBM before stating ownership.
  • If more than one ownership system has an exact hit, report all exact hits as a conflict or multi-use condition; do not silently pick one.
  • If only a CIDR route matches and no exact record is found, report the IP as "unconfirmed" or "expected type only".

References

Read only the files needed for the current question:

  • references/ip-routing.md: Maintain /24 or more specific CIDR routes to choose the first query source.
  • references/office-egress-ips.md: Shared local cache for office egress IPs and CIDRs.
  • references/query-playbooks.md: Follow the detailed playbooks for single-IP, VIP, SNAT, and access-relationship questions.
  • references/data-sources.md: Fill in CMDB, LBM, and ES query/authentication details as they become available.
  • references/output-format.md: Use the standard response format and confidence wording.

Scripts

  • scripts/signed_api.py: Shared Yunwei key/secret configuration helper. CMDB uses the pair for _key/_secret signing; LBM uses the same pair in the Bearer authorization header.
  • scripts/query_ips.py: Batch query multiple IPs across CMDB, LBM VIP, LBM SNAT, and office egress fallback; group exact hits by server IP, VIP, SNAT/load-balancer address, conflict/multi-use, and not-found sections.
  • scripts/route_ip.py: Match an IP against the YAML route table in references/ip-routing.md. Use it to verify route-table edits or to quickly see which source should be queried first.
  • scripts/query_cmdb.py: Query one or more CMDB server IP ownership records with the company key/secret signature scheme. Successful exact hits update references/ip-routing.md with the IP's /24 route by default.
  • scripts/query_lbm_vip.py: Query LBM VIP ownership using the VIP-LBM workflow Authorization header. Supports direct VIP lookup and backend/member IP reverse lookup. Successful exact hits update references/ip-routing.md with the IP's /24 route by default.
  • scripts/query_lbm_snat.py: Query LBM SNAT/load-balancer address ownership using the same workflow Authorization header. Successful exact hits update references/ip-routing.md with the IP's /24 route by default.
  • scripts/route_learning.py: Shared route-table update helper. Adds new routes, updates same-type routes, and refuses to overwrite conflicting routes.
  • scripts/query_office_egress.py: Query the shared office egress IP/CIDR cache as the last fallback source. By default it auto-updates the cache before querying when references/office-egress-ips.md is missing or older than 24 hours.
  • scripts/update_office_egress.py: Refresh references/office-egress-ips.md from the default company source URL, an override URL, or a local source file.

常见问题

5 问
答案由本站依据条目字段整理
安全vibeccc怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_39b26c07/securityzzzz。安装方式为未标注。装完刷新技能列表或重开客户端。

安全vibeccc支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

安全vibeccc权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

安全vibeccc收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

安全vibeccc用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。