service-governance-audit
Skill1 starsChanged 3 months agoMITView on GitHub
Audit microservice discovery, instances, health, topology, and governance policies across Alibaba Cloud MSE, Huawei Cloud CSE, and Baidu Cloud MSE/CSM. Use for service governance reviews, health checks, policy inventories, topology inspection, and pre-change evidence collection.
In this repository30 other files it gives its agents.
- api-syncSkill
- archive-changeSkill
- auto-flowSkill
- build-reportSkill
- change-impact-reviewSkill
- code-review-auditSkill
- code-reviewSkill
- coverage-reportSkill
- data-logic-validationSkill
- data-risk-auditSkill
- data-validationSkill
- dingtalk-notifySkill
- git-reviewSkill
- knowledge-opsSkill
- learning-engineSkill
- learning-feedbackSkill
- log-auditSkill
- offline-design-analysisSkill
- project-reviewSkill
- release-inspectionSkill
- report-insightsSkill
- requirement-analystSkill
- resource-bindSkill
- service-governance-changeSkill
- service-governance-diagnosisSkill
- service-management-log-analysisSkill
- sls-log-auditSkill
- test-reportSkill
- yapi-sync-interfaceSkill
- yuque-sync-designSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run read-only governance inspection before diagnosis or policy changes.
- Distinctive: line 16
Never create, update, or delete governance policies.
- Distinctive: line 18
Use requests such as:
- Distinctive: line 24
Read references/providers.md when configuring provider mappings.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Service Governance Audit
Run read-only governance inspection before diagnosis or policy changes.
Workflow
- Resolve the
serviceGovernanceresource binding and active provider. - Require environment and provider scope; include service, region, project, engine, or namespace when known.
- Query services, instances, health, topology, and governance policies.
- Report missing instances, unhealthy instances, and missing policy evidence.
- Never create, update, or delete governance policies.
Use requests such as:
服务治理审计 provider=huawei-cse env=uat service=order-service engine=xxx project=xxxRead references/providers.md when configuring provider mappings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.