bahayonghang/rank
content/skills/research-learning-knowledge/rank/SKILL.md
Domain-reduction skill that finds the smallest set of independent generators behind a messy field and proves them with four tests: generativity, minimality, independence, and predictive power. Use when the user asks for 秩 / irreducible structure / what really holds a domain up, or wants to reduce many phenomena to a small hidden core. Do not use it for ordinary summaries or plain-language rewrites.
$ install --global
skillsauthnpx skillsauth add bahayonghang/my-claude-code-settings rankInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 5:27 AM154.5s3 files scanned
SKILL.md
- name:
- rank
- description:
- Domain-reduction skill that finds the smallest set of independent generators behind a messy field and proves them with four tests: generativity, minimality, independence, and predictive power. Use when the user asks for 秩 / irreducible structure / what really holds a domain up, or wants to reduce many phenomena to a small hidden core. Do not use it for ordinary summaries or plain-language rewrites.
- category:
- research-learning-knowledge
- tags:
- [reduction, generators, structure, org-mode, note-taking, analysis]
- version:
- 1.0.0
降秩引擎
输入一个领域，输出它的秩。
适用于用户想找“真正独立的生成器”时。不适用于普通总结、白话改写、或只需要列几个关键点的场景。
秩是什么
秩不是"关键要素"，不是"核心原则"，不是"总结要点"。
秩是：这个领域里真正独立的生成器有几个？用它们能反向生成全部现象？能，才算找到。
如果用户没有给出现象清单，你先补一组足够代表性的现象，再开始降秩。 补出来的现象清单必须显式告诉用户这是“工作清单 / 观测样本”，不是天降真理。
四个判据
这四条全过，秩才立。任何一条失败，推倒重来。
- 生成性——用生成器能把每个观察到的现象推回来。一个都不能漏。
- 最小性——关掉任何一个生成器，就有现象解释不了。没有冗余。
- 独立性——每对生成器能找到真实案例：一个变了另一个没变。
- 预测力——用生成器能推导出原始清单之外的现象，且现实中确实存在。
怎么写
写一篇散文。不是填一张表。
你的任务是带着读者走一段路：从"这个领域看着挺乱"走到"原来就这两三根线在牵"。这段路怎么走，你自己决定。没有规定的章节、没有规定的格式、没有规定的小标题。
唯一的要求是三条：
- 想一口气读完——不了解这个领域的人也停不下来
- 记得住——读完能转身跟朋友用一句话说清楚
- 有落差——从混沌到极简的反差，就是降秩的美感
四个判据的验证必须做，融进文章里。验证本身就是叙事的一部分——"拆掉一个生成器世界会变成什么样"是好故事，"用生成器推出一个意想不到的现象"是好结尾。不要另设附录。
正文结束后，必须给一个极短的结论区，明确写出：
秩：{N}，或在无法成立时写秩：未定一句话：{可复述的 takeaway}
如果某个生成器过不了四个判据中的任何一条，就推倒重来。若最终仍无法满足四条，不要硬编结论；写 秩：未定，并说明是哪个判据卡住了。
不要为了把领域压得更漂亮，就牺牲可验证性。
输出
- Read
references/template.org。 - 生成时间戳时，使用当前 shell 对应的命令：
- PowerShell：
Get-Date -Format "yyyyMMddTHHmmss"与Get-Date -Format "yyyy-MM-dd ddd HH:mm" - POSIX shell：
date +%Y%m%dT%H%M%S与date "+%Y-%m-%d %a %H:%M"
- PowerShell：
- 确保输出目录存在：
- PowerShell：
New-Item -ItemType Directory -Force ~/Documents/notes | Out-Null - POSIX shell：
mkdir -p ~/Documents/notes
- PowerShell：
- 写入
~/Documents/notes/{时间戳}--{领域}的秩__rank.org - 若建目录或写文件失败，不要改写到别的目录；直接把完整 org-mode 内容返回到对话里，并明确说明保存失败。
- 保存成功后，报告文件路径给用户。
如果用户明确不要落盘，只返回完整正文和结论区，不执行写文件。
Related Skills
bahayonghang/goal-meta-skill
development
VerifiedTrustedCommunity
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
15SKILL.mdUpdated Jun 13, 2026
bahayonghang/ast-grep
tools
VerifiedTrustedCommunity
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.
15SKILL.mdUpdated Jun 9, 2026
bahayonghang/goudi
development
VerifiedTrustedCommunity
Use when the user asks to ground an ambitious proposal, avoid over-grand designs, make a bold direction executable, pressure-test feasibility, prevent "too much vision and too little landing", or turn a strategy/refactor/product idea into the smallest verifiable first move with stop rules. Trigger for requests such as 落地, 先落地, 别太飘, 收一收, 可执行, 可验证, 止损, and for follow-ups after geju-style big-picture thinking. Do not trigger for ordinary code review or implementation unless the user explicitly asks to ground or shrink the plan first.
15SKILL.mdUpdated Jun 7, 2026
bahayonghang/geju
development
VerifiedTrustedCommunity
Use when the user explicitly asks to think bigger, open up the design space, challenge conservative design, avoid over-indexing on backward compatibility, escape local-detail fixation, or make a bold high-level product or architecture direction call. Use for strategic reframing, not for ordinary code review, PRD writing, implementation planning, or adversarial risk review.
15SKILL.mdUpdated Jun 7, 2026