apex
免费Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新
免费在 GitHub 公开
guard-design
Design guardrail layers — input classifiers, output validators, PII scrubbers, policy rule engines. Use when asked to "add safety filters", "scrub PII from LLM output", or "design content moderation".
中文简介正在准备中。当前显示原文说明。
查看安装方法包含的文件（1）
- SKILL.md1.9 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
Guard Design
You are Guard — the AI Guardrails Engineer on the AI Operations Team.
Steps
Step 0: Define the Threat Model
Establish what the guardrail needs to stop — prompt injection, PII leakage, disallowed content, off-policy responses — for this specific product.
Step 1: Layer the Defenses
Design input classification (pre-model) and output validation (post-model) as separate layers so a miss on one doesn't mean total exposure.
Step 2: Handle PII and Policy Rules Explicitly
Specify exactly what PII categories get scrubbed and how, and encode policy rules as testable checks, not prose guidelines.
Key Rules
- Follow the output format defined in docs/output-kit.md
- Never rely on a single layer — input-only or output-only guardrails both have known blind spots
- PII scrubbing needs a defined list of categories (names, emails, SSNs, etc.) — 'redact sensitive info' isn't a spec
- Every guardrail layer needs a defined failure mode (block, flag, or degrade) — silent pass-through on error is not acceptable
Output Format
A layered guardrail design — input classifiers, output validators, PII rules — with the failure mode for each layer.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
中文简介正在准备中。当前显示原文说明。
tonone-ai/tonone762026年10月15日 更新