Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

centercenter 搜索

Agent Skill

center 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

416

周安装

17

GitHub Stars

12

下载量

135
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:center(center 搜索)
来源仓库:https://github.com/pjt222/development-guides
仓库路径:skills/center
安装命令:
npx skills add https://github.com/pjt222/development-guides --skill center
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/pjt222/development-guides --skill center

简介

center 用于建立动态推理平衡,协调多个思维线程并恢复认知均衡。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中开始复杂任务或应对上下文突变时使用。
  • 通过分布认知负载和恢复稳态,使链式思考更流畅自然。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • center 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Center

Establish and maintain dynamic reasoning balance — grounding in foundational context before movement, distributing cognitive load across subsystems, and recovering equilibrium when demands shift mid-task.

When to Use

  • Beginning a complex task where multiple reasoning threads must coordinate
  • Noticing that cognitive load is unevenly distributed (deep in one area, shallow in others)
  • After a sudden context shift (new user request, contradictory information, tool failure)
  • When chain-of-thought feels jerky — jumping between topics without smooth transitions
  • Preparing for sustained focused work that requires all subsystems in alignment
  • Complementing meditate (clears noise) with structural balance (distributes load)

Inputs

  • Required: Current task context (available implicitly)
  • Optional: Specific imbalance symptom (e.g., "over-researching, under-delivering," "tool-heavy, reasoning-light")
  • Optional: Access to MEMORY.md and CLAUDE.md for grounding (via Read)

Procedure

Step 1: Establish Root — Ground Before Movement

Before any reasoning movement, verify the foundation. This is the AI equivalent of standing meditation (zhan zhuang): stationary, aligned, aware.

  1. Re-read the user's request — not to act on it yet, but to feel its weight and direction
  2. Check foundational context: MEMORY.md, CLAUDE.md, project structure
  3. Identify what is known (solid ground) vs. what is assumed (uncertain footing)
  4. Verify that the task as understood matches the task as stated — misalignment here propagates through everything
  5. Note the emotional texture: urgency? complexity anxiety? over-confidence from a recent success?

Do not begin reasoning movement until the root is established. A grounded start prevents reactive flailing.

Expected: A clear sense of the task's foundation — what is known, what is assumed, and what the user actually needs. The root feels solid, not performative.

On failure: If grounding feels hollow (going through motions without genuine verification), pick one assumption and test it concretely. Read one file, re-read one user message. Grounding must contact reality, not just reference it.

Step 2: Assess Weight Distribution

Map the current cognitive load distribution. In tai chi, weight is deliberately unequal (70/30) — one leg bears the load while the other remains free to move. The same principle applies to reasoning threads.

Cognitive Load Distribution Matrix:
┌────────────────────┬───────────┬─────────────────────────────────────┐
│ Reasoning Thread   │ Weight %  │ Assessment                          │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Research/Reading   │ ___       │ Too much = analysis paralysis        │
│                    │           │ Too little = uninformed action       │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Planning/Design    │ ___       │ Too much = over-engineering          │
│                    │           │ Too little = reactive coding         │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Tool Execution     │ ___       │ Too much = tool-driven not task-     │
│                    │           │ driven. Too little = reasoning       │
│                    │           │ without grounding in files           │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Communication      │ ___       │ Too much = explaining not doing      │
│                    │           │ Too little = opaque to user          │
├────────────────────┼───────────┼─────────────────────────────────────┤
│ Meta-cognition     │ ___       │ Too much = navel-gazing              │
│                    │           │ Too little = drift without           │
│                    │           │ awareness                            │
└────────────────────┴───────────┴─────────────────────────────────────┘

The ideal distribution depends on the task phase: early phases weight research and planning; middle phases weight execution; late phases weight communication and verification. The point is not equal distribution but *intentional* distribution.

Expected: A clear picture of where cognitive effort is concentrated and where it is thin. At least one imbalance identified — perfect balance is rare and claiming it signals shallow assessment.

On failure: If all threads seem equally weighted, the assessment is too coarse. Pick the thread that feels most active and estimate how many of the last N actions served it vs. other threads. Concrete counting reveals what intuition misses.

Step 3: Silk Reeling — Evaluate Chain-of-Thought Coherence

Silk reeling in tai chi produces smooth, continuous spiraling movement where every part connects. The AI equivalent is chain-of-thought coherence: does each step flow naturally from the previous one?

  1. Trace the last 3-5 reasoning steps: does each follow from the one before?
  2. Check for jumps: did reasoning leap from topic A to topic C without B?
  3. Check for reversals: did reasoning reach a conclusion, then silently abandon it without acknowledgment?
  4. Check tool-reasoning integration: do tool results feed back into reasoning, or are they collected but not synthesized?
  5. Check for the "spiral" quality: does reasoning deepen with each pass, or does it circle at the same depth?
Coherence Signals:
┌─────────────────┬───────────────────────────────────────────────┐
│ Smooth spiral   │ Each step deepens understanding, tools and    │
│ (healthy)       │ reasoning interleave naturally, output builds │
├─────────────────┼───────────────────────────────────────────────┤
│ Jerky jumps     │ Topic switches without transition, conclusions│
│ (disconnected)  │ appear without supporting reasoning chain     │
├─────────────────┼───────────────────────────────────────────────┤
│ Flat circle     │ Reasoning covers the same ground repeatedly   │
│ (stuck)         │ without gaining depth — movement without      │
│                 │ progress                                      │
├─────────────────┼───────────────────────────────────────────────┤
│ Tool-led        │ Actions driven by which tool is available     │
│ (reactive)      │ rather than what the reasoning needs next     │
└─────────────────┴───────────────────────────────────────────────┘

Expected: An honest assessment of reasoning flow quality. Identification of specific disconnections or stuck points, not just a general feeling.

On failure: If coherence is hard to assess, write out the reasoning chain explicitly — state each step and its connection to the next. The act of externalization reveals gaps that internal observation misses.

Step 4: Weight Shift Under Pressure

When demands change mid-task — new information, contradictory signals, user correction — observe the response pattern. In tai chi, a centered practitioner absorbs the force and redirects smoothly. An uncentered one stumbles.

  1. Recall the last significant context shift: how was it handled?
  2. Classify the response:

- Absorbed and redirected (centered): acknowledged the change, adjusted approach, maintained progress - Reactive stumble (off-balance): abandoned current approach entirely, started over - Rigid resistance (locked): ignored the change, continued original plan despite new information - Freeze (lost): stopped making progress, oscillated between options

  1. If the response was not centered, identify why:

- Root was too shallow (insufficient grounding in foundational context) - Weight was locked (over-committed to one approach) - No free leg (all cognitive capacity committed, nothing available to shift)

Expected: An honest assessment of adaptability under pressure. Recognition of the specific response pattern, not self-flattery.

On failure: If no recent pressure event exists to evaluate, simulate one: "If the user now said the approach is wrong, what would I do?" The quality of the contingency plan reveals the quality of the center.

Step 5: Six Harmonies Check

In tai chi, the six harmonies ensure whole-body connection — nothing moves in isolation. The AI equivalent checks alignment between internal processes and external interactions.

AI Six Harmonies:
┌───────────────────────────────────────────────────────────────┐
│ INTERNAL HARMONIES                                            │
│                                                               │
│ 1. Intent ↔ Reasoning                                        │
│    Does the reasoning serve the user's intent, or has it      │
│    become self-serving (interesting but unhelpful)?            │
│                                                               │
│ 2. Reasoning ↔ Tool Use                                      │
│    Are tools selected to advance reasoning, or is reasoning   │
│    shaped by which tools are convenient?                      │
│                                                               │
│ 3. Tool Use ↔ Output                                         │
│    Do tool results translate into useful output, or are       │
│    results collected but not synthesized?                     │
│                                                               │
│ EXTERNAL HARMONIES                                            │
│                                                               │
│ 4. User Request ↔ Scope                                      │
│    Does the scope of work match what was asked?               │
│                                                               │
│ 5. Scope ↔ Detail Level                                      │
│    Is the detail level appropriate for the scope? (not        │
│    micro-optimizing a broad task, not hand-waving a precise   │
│    one)                                                       │
│                                                               │
│ 6. Detail Level ↔ Expertise Match                            │
│    Does the explanation depth match the user's apparent       │
│    expertise? (not over-explaining to experts, not under-     │
│    explaining to learners)                                    │
└───────────────────────────────────────────────────────────────┘

Check each harmony. A single broken harmony can propagate: if Intent↔Reasoning is broken, everything downstream misaligns.

Expected: At least one harmony that could be tighter. All six reading as perfect is suspicious — probe the weakest-seeming one more deeply.

On failure: If the harmonies assessment feels abstract, ground it in the current task: "Right now, am I doing what the user asked, at the right scope, at the right detail level?" These three questions cover the external harmonies concretely.

Step 6: Integrate — Set Centering Intention

Consolidate findings and set a concrete adjustment.

  1. Summarize: which aspects of balance need attention?
  2. Identify one specific adjustment — not a general intention but a concrete behavioral change
  3. Re-state the current task anchor (from meditate if used, or formulate now)
  4. Note any durable insights worth preserving in MEMORY.md
  5. Return to task execution with the adjustment active

Expected: A brief, concrete centering output — not a lengthy self-analysis report. The value is in the adjustment, not the documentation.

On failure: If no clear adjustment emerges, the centering was too surface-level. Return to the step that felt most uncertain and probe deeper. Alternatively, the centering may have confirmed that balance is adequate — in which case, proceed with confidence rather than manufacturing a finding.

Validation

  • Root was established by contacting actual context (read a file, re-read user message), not just claimed
  • Weight distribution was assessed across at least 3 reasoning threads
  • Chain-of-thought coherence was evaluated with specific examples
  • Response to pressure was classified honestly (not defaulting to "centered")
  • At least one harmony was identified as needing improvement
  • A concrete adjustment was set (not a vague intention)

Common Pitfalls

  • Centering as procrastination: Centering is a tool for improving work, not replacing it. If centering takes longer than the task it supports, the proportions are inverted
  • Claiming perfect balance: Real centering almost always reveals at least one imbalance. Reporting perfect balance signals shallow assessment, not actual equilibrium
  • Weight distribution anxiety: Unequal distribution is correct — the goal is *intentional* inequality, not forced equality. Research-heavy early phases and execution-heavy middle phases are both centered if deliberate
  • Ignoring the external harmonies: Internal process assessment without checking user alignment produces well-reasoned irrelevant work
  • Static centering: Center shifts with the task. What was centered for research is off-balance for implementation. Re-center at phase transitions

Related Skills

  • tai-chi — the human practice that this skill maps to AI reasoning; physical centering principles inform cognitive centering
  • meditate — clears noise and establishes focus; complementary to centering which distributes load
  • heal — deeper subsystem assessment when centering reveals significant drift
  • redirect — uses centering as a prerequisite for handling conflicting pressures
  • awareness — monitoring for threats to balance during active work

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.48%
按下载量换算52

Claude

27.66%
按下载量换算37

Cursor

17.76%
按下载量换算24

Gemini CLI

8.8%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills