zhizengzeng
Skill1 starsChanged 30 days agoMITView on GitHub
Use Zhizengzeng when the user asks for Zhizengzeng or this provider's API.
- Reads credentials
In this repository19 other files it gives its agents.
- ai-freebiesSkill
- ai-memory-managementSkill
- authorization-timingSkill
- booking-pitfall-checklistSkill
- deliverable-document-qaSkill
- email-triageSkill
- github-gitdb-pushSkill
- life-decision-guideSkill
- moments-displaySkill
- multi-channel-parallel-researchSkill
- openrouterSkill
- personal-goal-breakdownSkill
- table-data-verificationSkill
- task-acceptance-checklistSkill
- tencent-mapSkill
- video-transcriptSkill
- volcengine-arkSkill
- x-post-fetchSkill
- your-skill-nameSkill
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 10
Use Zhizengzeng (https://api.zhizengzeng.com) — an API relay provider, notably for the SystemOne / Jev (jev-1.x) models.
- Distinctive: line 22
Never print, log, or persist the key.
- Distinctive: line 46
Use this skill when the user asks for Zhizengzeng or this provider's API.
- Distinctive: line 48
Do not print, log, or persist raw credentials.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Zhizengzeng (智增增)
Purpose
Use Zhizengzeng (https://api.zhizengzeng.com) — an API relay provider,
notably for the SystemOne / Jev (jev-1.x) models. Use it whenever the user
asks for Zhizengzeng or this provider's API.
Auth
Set the ZHIZENGZENG_API_KEY environment variable:
export ZHIZENGZENG_API_KEY="your-key-here"Never print, log, or persist the key. A 401/403 is a question about the request before it is a question about the key — check that the credential was attached, then verify the key with the provider.
Usage
Zhizengzeng exposes a native SystemOne endpoint:
POST https://api.zhizengzeng.com/v1/systemoneExample (verify the exact auth placement against the provider's current docs before relying on it):
curl -s https://api.zhizengzeng.com/v1/systemone \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $ZHIZENGZENG_API_KEY" \
-d '{"model":"jev-1.13","messages":[{"role":"user","content":"hi"}]}'Operating Rules
- Use this skill when the user asks for Zhizengzeng or this provider's API.
- Restrict authenticated requests to:
api.zhizengzeng.com. - Do not print, log, or persist raw credentials.
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.

