service-governance-change
Skill1 starsChanged 3 months agoMITView on GitHub
Preview and apply guarded microservice governance policy creation or updates across Alibaba Cloud MSE, Huawei Cloud CSE, and Baidu Cloud MSE/CSM. Use for throttling, circuit breaking, routing, degradation, retry, fault-tolerance, and allowlist policy changes that require dry-run review and approval-token execution.
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-auditSkill
- 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, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Call provider preview when executionMode is not execute.
- Distinctive: line 17
Stop on provider errors and preserve execution evidence for audit.
- Distinctive: line 19
Use requests such as:
- Distinctive: line 25
Read references/providers.md before binding a provider or overriding MCP tool names.
≈ “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 Change
Apply governance mutations only through FlowMind's guarded workflow.
Workflow
- Resolve provider, environment, service, engine/project scope, policy kind, and policy body.
- Reject delete operations.
- Call provider preview when
executionModeis notexecute. - Return a
service-governance-changenext action for dry-run review. - Execute create or update only after the workflow approval token matches the reviewed input.
- Stop on provider errors and preserve execution evidence for audit.
Use requests such as:
更新治理策略 provider=huawei-cse env=uat service=order-service kind=rate-limit policy='{"qps":100}'Read references/providers.md before binding a provider or overriding MCP tool names.
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.