Token导航 LogoToken导航

Agent Skill · 研究检索

ln-810-performance-optimization-coordinator(ln 810 性能优化协调器)

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

ln-810-performance-optimization-coordinator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 45,111。

总安装 870周安装 37GitHub Stars 441下载 305核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ln-810-performance-optimization-coordinator(ln 810 性能优化协调器)
来源仓库:https://github.com/levnikolaevich/claude-code-skills
仓库路径:skills/ln-810-performance-optimization-coordinator
安装命令:
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-810-performance-optimization-coordinator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-810-performance-optimization-coordinator

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。ln-810-performance-optimization-coordinator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合根据关键词或任务场景快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围和维护状态。

注意是否会触发联网、命令执行或文件读写操作。

来源仓库内路径:skills/ln-810-performance-optimization-coordinator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-8…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

ln-810-performance-optimization-coordinator 怎么安装?

在终端执行 npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-810-perform…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ln-810-performance-optimization-coordinator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ln-810-performance-optimization-coordinator 需要什么权限?

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

ln-810-performance-optimization-coordinator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ln-810-performance-optimization-coordinator 用的人多吗?

公开数据是累计安装 870 次,近一周安装 37 次,下载 305 次,GitHub 441 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ln-810-performance-optimization-coordinator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ln-810-performance-optimization-coordinator

ln 810 性能优化协调器 · 本页

870441只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

ln-810-performance-optimization-coordinator

Type: L2 Domain Coordinator Category: 8XX Optimization

Coordinates performance optimization by delegating to L3 workers: ln-811 (algorithm), ln-812 (query), ln-813 (runtime). Workers run in parallel when inputs are independent.


Overview

AspectDetails
InputTarget file/module OR audit report (ln-650 output)
OutputOptimized code with verification proof
Workersln-811 (algorithm), ln-812 (query), ln-813 (runtime)

Workflow

Phases: Pre-flight → Analyze Input → Delegate → Collect → Verify → Report


Phase 0: Pre-flight Checks

CheckRequiredAction if Missing
Target file OR audit reportYesBlock optimization
Git clean stateYesBlock (need clean baseline for revert)
Test infrastructureYesBlock (workers need tests for keep/discard)

MANDATORY READ: Load shared/references/ci_tool_detection.md for test/build detection.


Phase 1: Analyze Input

Input Sources

SourceDetectionWorkers Activated
docs/project/persistence_audit.mdln-650 output existsln-812 (query) + ln-813 (runtime)
Target file + functionUser-specifiedln-811 (algorithm)
Full audit reportAll ln-65X sections presentAll three workers

Worker Selection

Conditionln-811ln-812ln-813
Target function specifiedYesNoNo
ln-651 findings presentNoYesNo
ln-653 findings presentNoNoYes
All audit findingsConditional*YesYes

*ln-811 activated only if specific algorithmic inefficiency identified in audit.


Phase 2: Delegate to Workers

CRITICAL: All delegations use Agent tool with subagent_type: "general-purpose" and isolation: "worktree" — each worker creates its own branch per shared/references/git_worktree_fallback.md.

Delegation Protocol

FOR each selected worker:
  Agent(description: "Optimize via ln-81X",
       prompt: "Execute optimization worker.

Step 1: Invoke worker:
  Skill(skill: \"ln-81X-{worker}\")

CONTEXT:
{delegationContext}",
       subagent_type: "general-purpose",
       isolation: "worktree")

Delegation Context

FieldTypeDescription
projectPathstringAbsolute path to project
auditReportstringPath to persistence_audit.md (if applicable)
targetFilestringTarget file path (if applicable)
targetFunctionstringTarget function name (if applicable)
options.runTestsboolRun tests after optimization
options.runLintboolRun lint after optimization

Parallelism

WorkersCan ParallelReason
ln-812 + ln-813YesDifferent files, different fix types
ln-811 + ln-812DependsOnly if targeting different files
ln-811 + ln-813DependsOnly if targeting different files

Rules:

  • If workers target the SAME file, run sequentially (ln-811 first, then ln-812/813).
  • Dependent workers share branch: If worker B depends on worker A's output (e.g., ln-813 needs ln-812's query changes), launch worker B in worker A's branch — so B sees A's changes.

Phase 3: Collect Results

Each worker produces an isolated branch. Coordinator aggregates branch reports.

Worker Branches

WorkerBranch PatternContents
ln-811optimize/ln-811-{function}-{ts}Algorithm optimizations with benchmarks
ln-812optimize/ln-812-{ts}Query optimizations
ln-813optimize/ln-813-{ts}Runtime optimizations

Result Schema

FieldTypeDescription
workerstringln-811, ln-812, or ln-813
statusenumsuccess, partial, failed
branchstringWorker's result branch name
fixes_appliedintNumber of kept optimizations
fixes_discardedintNumber of discarded attempts
detailsobjectWorker-specific report

Phase 4: Aggregate Reports

Each worker verified independently in its branch (tests, build, lint run by worker itself). Coordinator does NOT rerun verification or revert worker changes.

On Failure

  1. Branch with failing tests logged as "failed" in report
  2. User reviews failed branch independently

Phase 5: Report Summary

Report Schema

FieldDescription
input_sourceAudit report or target file
workers_activatedWhich workers ran
total_fixes_appliedSum across all workers
total_fixes_discardedSum across all workers
build_verifiedPASSED or FAILED
per_worker[]Individual worker reports
algorithm_improvementBenchmark improvement % (ln-811 only)

Configuration

Options:
  # Input
  audit_report: "docs/project/persistence_audit.md"
  target_file: ""
  target_function: ""

  # Workers
  enable_algorithm: true
  enable_query: true
  enable_runtime: true

  # Verification
  run_tests: true
  run_build: true
  run_lint: true

  # Safety
  revert_on_build_failure: true

Error Handling

Recoverable Errors

ErrorRecovery
Worker timeoutLog timeout, continue with other workers
Single worker failureRevert worker changes, report partial success
Build failureRevert last worker, re-verify

Fatal Errors

ErrorAction
No workers activatedReport "no optimization targets found"
All workers failedReport failures, suggest manual review
Dirty git stateBlock with "commit or stash changes first"

References

  • ../ln-811-algorithm-optimizer/SKILL.md
  • ../ln-812-query-optimizer/SKILL.md
  • ../ln-813-runtime-optimizer/SKILL.md
  • shared/references/ci_tool_detection.md

Definition of Done

  • Input analyzed (audit report or target file/function)
  • Appropriate workers selected based on input type
  • Workers delegated with worktree isolation (isolation: "worktree")
  • Each worker produces isolated branch, pushed to remote
  • Coordinator report aggregates per-worker results (branch, fixes, status)

Phase 6: Meta-Analysis

MANDATORY READ: Load shared/references/meta_analysis_protocol.md

Skill type: optimization-coordinator. Run after all phases complete. Output to chat using the optimization-coordinator format.


Version: 1.0.0 Last Updated: 2026-03-08

平台分布

Codex

34.37%
按下载量换算105

Claude

32.02%
按下载量换算98

Cursor

19.9%
按下载量换算61

Gemini CLI

9.29%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills