Agent skill

Cc API Proxy Safety

by doccker in doccker/cc-use-exp

网关/代理/WAF/CDN 中间件响应判定与关键词匹配安全规范。适用于 proxy/gateway/waf/cdn/nginx/openresty/rewrite/redirect 等代码,防止把正常长正文中的 Cloudflare、502、bad gateway、error 等技术术语误判为上游错误。

Custom licenceAuto-check passedDevOps & Cloud

Install Cc API Proxy Safety

skills CLI
$ npx skills add doccker/cc-use-exp --skill cc-api-proxy-safety -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install doccker/cc-use-exp cc-api-proxy-safety --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/doccker/cc-use-exp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/cc-api-proxy-safety .claude/skills/cc-api-proxy-safety && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cc-api-proxy-safety
GitHub stars
1.1k
Token cost
~717 tokens
SKILL.md length
150 words
Files
2
Skills in repo
67
Repo updated
First seen
Licence
Custom licence

At a glance

网关/代理/WAF/CDN 中间件响应判定与关键词匹配安全规范。适用于 proxy/gateway/waf/cdn/nginx/openresty/rewrite/redirect 等代码,防止把正常长正文中的 Cloudflare、502、bad gateway、error 等技术术语误判为上游错误。

  • Works in 4 steps: 传输层和 HTTP 状态:连接失败、超时、非 2xx/3xx… → 响应头和内容类型:Content-Type、Server、Via、CF-Ray、认… → 业务响应结构:先解析 JSON envelope、error… → …
  • Tasks that involve Cloud networking
  • SKILL.md covers 核心原则, 强弱特征拆分, 判定模板 and 场景策略, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cc API Proxy Safety is an agent skill from doccker/cc-use-exp. 网关/代理/WAF/CDN 中间件响应判定与关键词匹配安全规范。适用于 proxy/gateway/waf/cdn/nginx/openresty/rewrite/redirect 等代码,防止把正常长正文中的 Cloudflare、502、bad gateway、error 等技术术语误判为上游错误。

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in DevOps & Cloud, covering Cloud networking. It works with Cloudflare and NGINX. The repository describes itself as: ⛔ No longer maintained → dev-agent-kit/recipes 让 Claude Code、Antigravity、Gemini CLI、Codex、Cursor 开箱即用的分层配置模板,总结十多年的日常开发经验.

When your agent uses it

  • Tasks that involve Cloud networking

Example prompts

  • “/cc-api-proxy-safety”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. 传输层和 HTTP 状态:连接失败、超时、非 2xx/3xx 状态码优先作为错误证据。
  2. 响应头和内容类型:Content-Type、Server、Via、CF-Ray、认证/限流头等比正文关键词更可靠。
  3. 业务响应结构:先解析 JSON envelope、error code、message、data 等契约字段。
  4. 正文启发式:只有在无法按结构判断时,才使用关键词或 HTML 片段,并限制长度和上下文。

What it can do on your machine

Read from SKILL.md and the folder at commit 64470cb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are go).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cc API Proxy Safety loads about 717 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 150 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~717

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 150 words (~717 tokens).

name
cc-api-proxy-safety

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .codex/skills/cc-api-proxy-safety of doccker/cc-use-exp.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 64470cb

Compare with similar skills

Cc API Proxy Safety next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cc API Proxy Safety compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cc API Proxy Safety this skilldoccker/cc-use-exp1.1k—~717Automated safety check: PassCustom licence
Phy HTTP Cache AuditLeoYeAI/openclaw-master-skills2.2k—~4.1kAutomated safety check: PassApache-2.0
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress5.1k—~2kAutomated safety check: PassApache-2.0
Wp Static Clonejdevalk/skills104—~2.6kAutomated safety check: PassMIT

Similar skills

  • Phy HTTP Cache Audit

    LeoYeAI/openclaw-master-skills

    HTTP caching header analyzer that checks Cache-Control directives, ETag/Last-Modified freshness, Vary correctness, CDN cache status (X-Cache, CF-Cache-Status, Age), and stale-while-revalidate…

    2.2k GitHub stars~4.1k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • NGINX Ingress Policy CRD Guide

    nginx/kubernetes-ingress

    Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.

    5.1k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Wp Static Clone

    jdevalk/skills

    Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx).

    104 GitHub stars~2.6k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed
  • Analyze production Node.js app container response times to find slow-rendering sites, cross-checking against nginx queuing delay to rule out false positives (a site only looks slow because the event…

    2k GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check passed

More from doccker/cc-use-exp

All 67 skills in this repo
  • API Design Safety

    doccker/cc-use-exp

    当设计或修改 REST API 响应结构、处理 API 返回值,或生成 Excel/CSV/PDF/对账文件等下游产物时触发。防止 API 设计缺陷导致的字段错位、类型歧义,以及生成产物时关键字段缺失但静默成功的问题。

    1.1k GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Cc Code Quality Principles

    doccker/cc-use-exp

    当编写新模块、设计接口、重构代码或代码审查时触发。提供经典模块化六原则检查清单(大小适中/调用深度/扇入扇出/边界清晰/作用域内聚/可预测性),适用于 PR/Review/新模块设计场景。

    1.1k GitHub stars~816 tokensUpdated 1 mo ago
    Auto-check passed
  • Cc Review

    doccker/cc-use-exp

    结构化代码审查工作流,适用于显式 quick/full/security review;不负责普通实现或 bug 修复流程。

    1.1k GitHub stars~541 tokensUpdated 1 mo ago
    Auto-check passed
  • Cc Streaming Export Safety

    doccker/cc-use-exp

    当实现用户驱动的大文件导出或批量序列化(Excel/CSV/JSON/JSONL/PDF,数据量未知或超过 1 万行/10 MB)时触发;普通小文件下载、静态资源下载、非导出 Writer/Report 类不触发。防止 OOM、临时文件残留、同步导出阻塞 HTTP 线程和表格公式注入。

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Code Quality Principles

    doccker/cc-use-exp

    当编写新模块、设计接口、重构代码或代码审查时触发。提供经典模块化六原则检查清单(大小适中/调用深度/扇入扇出/边界清晰/作用域内聚/可预测性),适用于 PR/Review/新模块设计场景。

    1.1k GitHub stars~803 tokensUpdated 1 mo ago
    Auto-check passed
  • External System Debugging

    doccker/cc-use-exp

    涉及浏览器、编辑器、CDN/WAF、IM 平台、操作系统剪贴板、第三方 SaaS 等"外部黑盒系统"的代码编写或 bug 调试时触发。强制先抓真实环境数据再推理,避免连续 2 轮"凭代码推理"的修复 no-op。关键词:粘贴/复制异常、跨平台显示不一致、第三方 API 怪结果、CDN/WAF 拦截、本地复现失败、HTML→MD 转换丢属性。

    1.1k GitHub stars~823 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Cc API Proxy Safety

What does Cc API Proxy Safety do?

网关/代理/WAF/CDN 中间件响应判定与关键词匹配安全规范。适用于 proxy/gateway/waf/cdn/nginx/openresty/rewrite/redirect 等代码,防止把正常长正文中的 Cloudflare、502、bad gateway、error 等技术术语误判为上游错误。. Cc API Proxy Safety is an agent skill from doccker/cc-use-exp.

When should I use Cc API Proxy Safety?

Cc API Proxy Safety fits situations like: tasks that involve Cloud networking.

How do I install Cc API Proxy Safety in Claude Code?

Run `npx skills add doccker/cc-use-exp --skill cc-api-proxy-safety -a claude-code`. Or copy the skill folder (.codex/skills/cc-api-proxy-safety in doccker/cc-use-exp) into .claude/skills/cc-api-proxy-safety in your project. Claude Code loads it when a task matches its description.

How do I install Cc API Proxy Safety in Codex?

Run `npx skills add doccker/cc-use-exp --skill cc-api-proxy-safety -a codex`. Or copy the skill folder (.codex/skills/cc-api-proxy-safety in doccker/cc-use-exp) into .agents/skills/cc-api-proxy-safety in your project. Codex loads it when a task matches its description.

Can I use Cc API Proxy Safety in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add doccker/cc-use-exp --skill cc-api-proxy-safety -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cc-api-proxy-safety, .gemini/skills/cc-api-proxy-safety, .github/skills/cc-api-proxy-safety and .opencode/skills/cc-api-proxy-safety in your project.

What does Cc API Proxy Safety need to run?

SKILL.md names no scripts, command-line tools or credentials: Cc API Proxy Safety is instructions for the agent only.

Does Cc API Proxy Safety access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cc API Proxy Safety safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cc API Proxy Safety use?

Cc API Proxy Safety has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Cc API Proxy Safety use?

About 717 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cc API Proxy Safety?

Skills that share tags, products or a category with Cc API Proxy Safety: Phy HTTP Cache Audit (LeoYeAI/openclaw-master-skills, 2.2k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars) and NGINX Ingress Policy CRD Guide (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cc API Proxy Safety?

doccker (a GitHub user) maintains it in doccker/cc-use-exp, which has 1,062 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on August 26, 2026.

Source: doccker/cc-use-exp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.