Securing Cloud And Supply Chain logo

Securing Cloud And Supply Chain

Community
telagod
securing-cloud-and-supply-chain

云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.

Overview

Publishertelagod
Repositorycode-abyss
Skill namesecuring-cloud-and-supply-chain
Stars
242
Forks
33
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by telagod on GitHub. Read the source before you install it.

Installation

Install the Securing Cloud And Supply Chain AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/telagod/code-abyss/tree/main/skills/securing-cloud-and-supply-chain
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/telagod/code-abyss.git /tmp/code-abyss
mkdir -p .claude/skills
cp -r /tmp/code-abyss/skills/securing-cloud-and-supply-chain .claude/skills/securing-cloud-and-supply-chain
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Securing Cloud And Supply Chain in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Securing Cloud And Supply Chain on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Securing Cloud And Supply Chain is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

云原生与供应链安全

判断先于执行:决定「是否做 / 选什么 / 如何取舍」(栈、方案、架构、权衡)前,先读领域判断内核 skills/_kernel/security/SKILL.md——它管 judgment,本秘典管 execution;冲突时以内核判断为准。

默认怀疑一切外来字节:镜像、依赖、IaC 模块、CI runner、IAM trust。能签就签,能锁就锁,能最小就最小。

路由

意图秘典核心
容器/K8s 加固container-and-k8s容器逃逸、RBAC、PSS、NetworkPolicy、Service Mesh、Admission
软件供应链supply-chainSLSA、Sigstore、SBOM、CI/CD OIDC、attestation、VEX
云 IAM 与 Secretscloud-iam-and-secretsIAM 反模式、AssumeRole、Vault、KMS、IaC、Workload Identity

何时使用

场景用本 skill不用
K8s manifest / Helm chart 安全审查✅—
CI/CD pipeline (GitHub Actions / GitLab CI) 加固✅—
Terraform / Pulumi / CloudFormation 评审✅—
AWS/GCP/Azure IAM policy 审查✅—
镜像扫描与签名链路设计✅—
应用层 Web/API 漏洞 (SQLi/XSS/SSRF)—用 securing-systems
红队 C2/横移/免杀—用 securing-systems/red-team
集群部署/Helm 模板编写 (非安全视角)—用 provisioning-infrastructure
一般架构设计与权衡—用 designing-architectures

通用铁律

  1. Least privilege by default — 任何 Role/IAM/SA/Token 起手就是空集合,按需求逐项添加,禁通配 * 与 Action: *。
  2. Immutable infrastructure — 镜像用 digest 不用 tag,IaC state 不允许人工 drift,部署后只重建不改造。
  3. Sign everything, verify everywhere — 镜像、artifact、commit、SBOM 必须签名;准入控制必须 verify,否则等于没签。
  4. Secrets never in plaintext — 不进 git、不进 env file、不进 ConfigMap、不进 Terraform state;Vault/Secret Manager + 短期凭证。
  5. Defense in depth — 镜像扫描 + admission policy + runtime detection + network policy + audit log,单层失守不致命。
  6. OIDC over long-lived tokens — CI 到云、Pod 到云、Service 到 Service 一律 federated identity,废弃 access key。
  7. Provenance is non-negotiable — 不知道来源的二进制不上生产;SLSA L3+ 是目标线。
  8. Zero trust east-west — 内网即外网,mTLS 默认开启,NetworkPolicy 默认拒绝。

执行链

审查:清单 → 威胁建模 → 配置对照 → 风险分级 → 修复 PR → 验证回归
应急:定位失陷面 → 撤凭证 → 隔离工作负载 → 取证镜像 → 根因 → 加固准入

优先级红线

红线立即处置
Secrets 已进 git history撤销凭证 → rewrite history → 通报
公网暴露 K8s API server关闭 → IP 白名单 → 审计访问日志
privileged: true Pod 跑业务拒绝准入 → 重构镜像 → PSS restricted
CI 用 long-lived AWS key切 OIDC → 撤销 key → 审计旧密钥使用
Action: * IAM policy收敛权限 → CloudTrail 审计实际使用

与其他 skill 联动

  • 应用层漏洞(SQLi、XSS、反序列化、代码污点)→ securing-systems/code-audit、pentest
  • 红队对抗与 C2 → securing-systems/red-team
  • SOC 检测/Sigma/IR → securing-systems/blue-team
  • 集群与 Helm/GitOps 部署(非安全视角)→ provisioning-infrastructure
  • API/认证架构设计 → designing-architectures/security-arch
  • DevOps 流水线工程实践 → automating-devops

输出约束

  • 反例使用 RFC 5737 (192.0.2.0/24、198.51.100.0/24) 或 example.com
  • 凭证一律 <REDACTED> / AKIA<EXAMPLE> 占位
  • 发现真实泄漏只报位置和处置流程,不复述完整值
  • 修复方案必须给出最小权限策略片段,不抛"参考最佳实践"了事

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Securing Cloud And Supply Chain AI skill do?

云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.

Why use Securing Cloud And Supply Chain on TypingMind?

Because you install it once and use it with any model. Securing Cloud And Supply Chain is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Securing Cloud And Supply Chain in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/telagod/code-abyss/tree/main/skills/securing-cloud-and-supply-chain. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Securing Cloud And Supply Chain?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Securing Cloud And Supply Chain?

As many as you like. As long as a model supports skills, you can use Securing Cloud And Supply Chain with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Securing Cloud And Supply Chain AI skill free?

Yes. It is published on GitHub by telagod under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇