affaan-m/ECC

agent-sort

通过将技能、命令、规则、钩子和额外内容并行进行仓库感知审查，为特定仓库构建基于证据的 ECC 安装计划，将其分为 DAILY 和 LIBRARY 两类。当 ECC 应精简为项目实际所需而非加载完整包时使用。

67Collecting

See how to use it View GitHub source

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/agent-sort"

Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn agent-sort's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 当仓库需要项目特定的 ECC 表面而非默认完整安装时，使用此技能。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/agent-sort"

Check the pinned source

Best fit

通过将技能、命令、规则、钩子和额外内容并行进行仓库感知审查，为特定仓库构建基于证据的 ECC 安装计划，将其分为 DAILY 和 LIBRARY 两类。当 ECC 应精简为项目实际所需而非加载完整包时使用。

Bring this context

A concrete task that matches the documented purpose of agent-sort.
The files, examples, or context the task depends on.
Your constraints, target environment, and definition of done.

Expected outputs

A result that follows the pinned agent-sort instructions.
A concise record of assumptions, inputs used, and unresolved questions.
A final check against the source workflow and relevant permission signals.

Key source sections

Read agent-sort through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

何时使用

项目只需要 ECC 的子集，完整安装过于嘈杂仓库技术栈明确，但无人希望逐个手动筛选技能团队希望获得基于 grep 证据而非主观意见的可重复安装决策需要将始终加载的日常工作流表面与可搜索的库/参考表面分离仓库已偏离至错误的语言、规则或钩子集，需要清理

SKILL.md · 何时使用

项目只需要 ECC 的子集，完整安装过于嘈杂仓库技术栈明确，但无人希望逐个手动筛选技能团队希望获得基于 grep 证据而非主观意见的可重复安装决策

不可协商的规则

以当前仓库为事实来源，而非通用偏好每个 DAILY 决策必须引用具体的仓库证据 LIBRARY 并不意味着"删除"；它意味着"保持可访问但不默认加载" 不要安装当前仓库无法使用的钩子、规则或脚本优先使用 ECC 原生表面；不要引入第二个安装系统

SKILL.md · 不可协商的规则

以当前仓库为事实来源，而非通用偏好每个 DAILY 决策必须引用具体的仓库证据LIBRARY 并不意味着"删除"；它意味着"保持可访问但不默认加载"

输出

1. DAILY 清单 2. LIBRARY 清单 3. 安装计划 4. 验证报告 5. 可选的路由器（如果项目需要）

SKILL.md · 输出

DAILY 清单LIBRARY 清单安装计划

分类模型

DAILY 应为该仓库的每个会话加载与仓库的语言、框架、工作流或操作者表面强匹配 LIBRARY 保留有用，但不值得默认加载应通过搜索、路由器技能或选择性手动使用保持可访问

SKILL.md · 分类模型

DAILY应为该仓库的每个会话加载与仓库的语言、框架、工作流或操作者表面强匹配

证据来源

文件扩展名包管理器和锁文件框架配置 CI 和钩子配置构建/测试脚本导入和依赖清单明确描述技术栈的仓库文档

SKILL.md · 证据来源

文件扩展名包管理器和锁文件框架配置

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use agent-sort to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned agent-sort source to [task]. Pay particular attention to these source sections: “何时使用”, “不可协商的规则”, “输出”, “分类模型”, “证据来源”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current agent-sort result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “何时使用” has been checked.

The source section “不可协商的规则” has been checked.

The source section “输出” has been checked.

The source section “分类模型” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

agent-sort

並行リポジトリ対応のレビューパスを使用して、スキル、コマンド、ルール、フック、エクストラを DAILY と LIBRARY のバケットに分類することで、特定のリポジトリ向けのエビデンスに基づいた ECC インストール計画を構築します。プロジェクトが完全なバンドルをロードする代わりに実際に必要なものに ECC をトリミングする必要がある場合に使用します。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does agent-sort do?

当仓库需要项目特定的 ECC 表面而非默认完整安装时，使用此技能。

How do I start using agent-sort?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/agent-sort". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars

234,327

Repository forks

35,711

Quality

67/100

Source repository last pushed

2026-07-27

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

67/100

Documentation21/30

Specificity14/25

Maintenance20/20

Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

agent-sort by affaan-m

ab-testing by coreyhaines31

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

技能分类

当仓库需要项目特定的 ECC 表面而非默认完整安装时，使用此技能。

目标不是猜测"什么感觉有用"。目标是根据实际代码库中的证据对 ECC 组件进行分类。

何时使用

项目只需要 ECC 的子集，完整安装过于嘈杂
仓库技术栈明确，但无人希望逐个手动筛选技能
团队希望获得基于 grep 证据而非主观意见的可重复安装决策
需要将始终加载的日常工作流表面与可搜索的库/参考表面分离
仓库已偏离至错误的语言、规则或钩子集，需要清理

不可协商的规则

以当前仓库为事实来源，而非通用偏好
每个 DAILY 决策必须引用具体的仓库证据
LIBRARY 并不意味着"删除"；它意味着"保持可访问但不默认加载"
不要安装当前仓库无法使用的钩子、规则或脚本
优先使用 ECC 原生表面；不要引入第二个安装系统

输出

按顺序生成以下工件：

DAILY 清单
LIBRARY 清单
安装计划
验证报告
可选的路由器（如果项目需要）

分类模型

仅使用两个分类：

DAILY
- 应为该仓库的每个会话加载
- 与仓库的语言、框架、工作流或操作者表面强匹配
LIBRARY
- 保留有用，但不值得默认加载
- 应通过搜索、路由器技能或选择性手动使用保持可访问

证据来源

在进行任何分类之前，使用仓库本地证据：

文件扩展名
包管理器和锁文件
框架配置
CI 和钩子配置
构建/测试脚本
导入和依赖清单
明确描述技术栈的仓库文档

有用的命令包括：

rg --files
rg -n "typescript|react|next|supabase|django|spring|flutter|swift"
cat package.json
cat pyproject.toml
cat Cargo.toml
cat pubspec.yaml
cat go.mod

并行审查轮次

如果并行子代理可用，将审查分为以下轮次：

代理
- 分类 agents/*
技能
- 分类 skills/*
命令
- 分类 commands/*
规则
- 分类 rules/*
钩子和脚本
- 分类钩子表面、MCP 健康检查、辅助脚本和操作系统兼容性
额外项
- 分类上下文、示例、MCP 配置、模板和指导文档

如果子代理不可用，则按顺序运行相同的轮次。

核心工作流

1. 读取仓库

在分类任何内容之前，确定实际技术栈：

使用的语言
使用的框架
主要包管理器
测试技术栈
代码检查/格式化技术栈
部署/运行时表面
已存在的操作者集成

2. 构建证据表

对于每个候选表面，记录：

组件路径
组件类型
建议的分类
仓库证据
简短理由

使用此格式：

skills/frontend-patterns | skill | DAILY | 84 个 .tsx 文件，存在 next.config.ts | 核心前端技术栈
skills/django-patterns   | skill | LIBRARY | 无 .py 文件，无 pyproject.toml       | 此仓库中未激活
rules/typescript/*       | rules | DAILY | 存在 package.json + tsconfig.json            | 活跃的 TS 仓库
rules/python/*           | rules | LIBRARY | 零个 Python 源文件             | 仅保持可访问

3. 决定 DAILY 还是 LIBRARY

提升至 DAILY 当：

仓库明确使用匹配的技术栈
组件足够通用，有助于每个会话
仓库已依赖相应的运行时或工作流

降级至 LIBRARY 当：

组件与技术栈不匹配
仓库可能以后需要，但不是每天
它增加了上下文开销而无直接相关性

4. 构建安装计划

将分类转化为行动：

DAILY 技能 -> 安装或保留在 .claude/skills/
DAILY 命令 -> 仅当仍然有用时保留为显式 shim
DAILY 规则 -> 仅安装匹配的语言集
DAILY 钩子/脚本 -> 仅保留兼容的
LIBRARY 表面 -> 通过搜索或 skill-library 保持可访问

如果仓库已使用选择性安装，则更新该计划而非创建另一个系统。

5. 创建可选的路由器

如果项目需要可搜索的库表面，创建：

.claude/skills/skill-library/SKILL.md

该路由器应包含：

DAILY 与 LIBRARY 的简短说明
分组的触发关键词
库参考的存放位置

不要在路由器内重复每个技能的主体。

6. 验证结果

应用计划后，验证：

每个 DAILY 文件存在于预期位置
未保留过时的语言规则
未安装不兼容的钩子
最终安装确实匹配仓库技术栈

返回一个简洁的报告，包含：

DAILY 数量
LIBRARY 数量
移除的过时表面
未解决的问题

交接

如果下一步是交互式安装或修复，交接至：

configure-ecc

如果下一步是重叠清理或目录审查，交接至：

skill-stocktake

如果下一步是更广泛的上下文修剪，交接至：

strategic-compact

输出格式

按此顺序返回结果：

栈
- 语言/框架/运行时摘要

日常
- 始终加载的条目及证据

库
- 可搜索/参考的条目及证据

安装计划
- 应安装、移除或路由的内容

验证
- 已运行的检查及剩余差距

Source repo: affaan-m/ECC
Skill path: docs/zh-CN/skills/agent-sort/SKILL.md
Commit SHA: 4e973d3eaf92
Repository license: MIT
Data collected: Jul 28, 2026