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

skill-refresh技能刷新

Agent Skill

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

总安装

225

周安装

9

GitHub Stars

437

下载量

73
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/benbrastmckie/nvim --skill skill-refresh

简介

用于查找、检索和筛选最新技术资料或社区动态。

  • 适合在持续学习或技术更新跟踪类任务中使用。
  • 通过 GitHub 仓库安装,支持 Codex、Claude 等宿主调用。
  • 检索时效性取决于上游数据源更新频率。
  • 建议定期手动校验关键信息的准确性。skill-refresh 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Refresh Skill (Direct Execution)

Direct execution skill for managing Claude Code resources. Performs two operations:

  1. Process cleanup: Identify and terminate orphaned Claude Code processes
  2. Directory cleanup: Clean up accumulated files in ~/.claude/

This skill executes inline without spawning a subagent.

Execution

Step 1: Parse Arguments

Extract flags from command input:

  • --dry-run: Preview mode
  • --force: Skip confirmation, use 8-hour default
# Parse from command input
dry_run=false
force=false
if [[ "$*" == *"--dry-run"* ]]; then
  dry_run=true
fi
if [[ "$*" == *"--force"* ]]; then
  force=true
fi

Step 2: Run Process Cleanup

Execute process cleanup script:

.claude/scripts/claude-refresh.sh $( [ "$force" = true ] && echo "--force" )

Store process cleanup output for display.

Step 3: Clean Orphaned Postflight Markers

Clean any orphaned postflight coordination files from the specs directory. These files should normally be cleaned up by skills after postflight completes, but may be left behind if a process is interrupted.

echo ""
echo "=== Cleaning Orphaned Postflight Markers ==="
echo ""

# Find orphaned postflight markers (older than 1 hour)
orphaned_pending=$(find specs -maxdepth 3 -name ".postflight-pending" -mmin +60 -type f 2>/dev/null)
orphaned_guard=$(find specs -maxdepth 3 -name ".postflight-loop-guard" -mmin +60 -type f 2>/dev/null)

# Also check for legacy global markers
legacy_pending=""
legacy_guard=""
if [ -f "specs/.postflight-pending" ]; then
    legacy_pending="specs/.postflight-pending"
fi
if [ -f "specs/.postflight-loop-guard" ]; then
    legacy_guard="specs/.postflight-loop-guard"
fi

if [ -n "$orphaned_pending" ] || [ -n "$orphaned_guard" ] || [ -n "$legacy_pending" ] || [ -n "$legacy_guard" ]; then
    if [ "$dry_run" = true ]; then
        echo "Would delete the following orphaned markers:"
        [ -n "$orphaned_pending" ] && echo "$orphaned_pending"
        [ -n "$orphaned_guard" ] && echo "$orphaned_guard"
        [ -n "$legacy_pending" ] && echo "$legacy_pending"
        [ -n "$legacy_guard" ] && echo "$legacy_guard"
    else
        # Delete orphaned task-scoped markers
        find specs -maxdepth 3 -name ".postflight-pending" -mmin +60 -delete 2>/dev/null
        find specs -maxdepth 3 -name ".postflight-loop-guard" -mmin +60 -delete 2>/dev/null

        # Delete legacy global markers
        rm -f specs/.postflight-pending 2>/dev/null
        rm -f specs/.postflight-loop-guard 2>/dev/null

        echo "Cleaned orphaned postflight markers."
    fi
else
    echo "No orphaned postflight markers found."
fi

Step 4: Clean Stale Backup Files

Scan for and remove any .backup files left over from the deprecated backup mechanism in .claude/:

echo ""
echo "=== Cleaning Stale Backup Files ==="
echo ""

# Find .backup files in .claude/ directory
backup_files=$(find .claude/ -name "*.backup" -type f 2>/dev/null)

if [ -n "$backup_files" ]; then
    backup_count=$(echo "$backup_files" | wc -l)
    if [ "$dry_run" = true ]; then
        echo "Would delete $backup_count .backup file(s):"
        echo "$backup_files"
    else
        echo "$backup_files" | xargs rm -f
        echo "Deleted $backup_count stale .backup file(s)."
    fi
else
    echo "No stale .backup files found."
fi

Step 5: Run Directory Survey

Show current directory status without cleaning yet:

.claude/scripts/claude-cleanup.sh

This displays:

  • Current ~/.claude/ directory size
  • Breakdown by directory
  • Space that can be reclaimed

Step 6: Execute Based on Mode

Dry-Run Mode

If --dry-run is set:

echo ""
echo "=== DRY RUN MODE ==="
echo "Showing 8-hour cleanup preview..."
echo ""
.claude/scripts/claude-cleanup.sh --dry-run --age 8

Exit after showing preview.

Force Mode

If --force is set:

echo ""
echo "=== EXECUTING CLEANUP (8-hour default) ==="
echo ""
.claude/scripts/claude-cleanup.sh --force --age 8

Show results and exit.

Interactive Mode (Default)

If neither flag is set:

  1. Check if cleanup candidates exist (claude-cleanup.sh exits with code 1 if candidates found)
  2. If no candidates, display message and exit:
No cleanup candidates found within default thresholds.
All files are either protected or recently modified.
  1. If candidates exist, prompt user for age selection:
{
  "question": "Select cleanup age threshold:",
  "header": "Age Threshold",
  "multiSelect": false,
  "options": [
    {
      "label": "8 hours (default)",
      "description": "Remove files older than 8 hours - aggressive cleanup"
    },
    {
      "label": "2 days",
      "description": "Remove files older than 2 days - conservative cleanup"
    },
    {
      "label": "Clean slate",
      "description": "Remove everything except safety margin (1 hour)"
    }
  ]
}
  1. Map user selection to age parameter:

- "8 hours (default)" → --age 8 - "2 days" → --age 48 - "Clean slate" → --age 0

  1. Execute cleanup with selected age:
case "$selection" in
  "8 hours (default)")
    .claude/scripts/claude-cleanup.sh --force --age 8
    ;;
  "2 days")
    .claude/scripts/claude-cleanup.sh --force --age 48
    ;;
  "Clean slate")
    .claude/scripts/claude-cleanup.sh --force --age 0
    ;;
esac
  1. Display cleanup results

Example Execution Flows

Interactive Flow

# User runs: /refresh

# Output:
Claude Code Refresh
===================

No orphaned processes found.
All 3 Claude processes are active sessions.

---

Claude Code Directory Cleanup
=============================

Target: ~/.claude/

Current total size: 7.3 GB

Scanning directories...

Directory                   Total    Cleanable    Files
----------                -------   ----------    -----
projects/                  7.0 GB       6.5 GB      980
debug/                   151.0 MB     140.0 MB      650
...

TOTAL                      7.3 GB       6.7 GB     5577

Space that can be reclaimed: 6.7 GB

# Prompt appears:
[Age Threshold]
Select cleanup age threshold:
  1. 8 hours (default) - Remove files older than 8 hours
  2. 2 days - Remove files older than 2 days
  3. Clean slate - Remove everything except safety margin

# User selects option 1

# Cleanup executes:
Cleanup Complete
================
Deleted: 5577 files
Failed:  0 files
Space reclaimed: 6.7 GB

New total size: 600.0 MB

Dry-Run Flow

# User runs: /refresh --dry-run

# Shows survey, then:
=== DRY RUN MODE ===
Showing 8-hour cleanup preview...

Would delete: 5577 files
Would reclaim: 6.7 GB

Dry Run Summary
===============
No changes made.

Force Flow

# User runs: /refresh --force

# Shows survey, then immediately:
=== EXECUTING CLEANUP (8-hour default) ===

Cleanup Complete
================
Deleted: 5577 files
Space reclaimed: 6.7 GB

Safety Measures

Protected Files (Never Deleted)

  • sessions-index.json (in each project directory)
  • settings.json
  • .credentials.json
  • history.jsonl

Safety Margin

Files modified within the last hour are never deleted, regardless of age threshold.

Process Safety

  • Only targets orphaned processes (TTY = "?")
  • Never kills active sessions
  • Excludes current process tree

Error Handling

Scripts Not Found

If scripts don't exist:

Error: Cleanup scripts not found at .claude/scripts/
Please ensure claude-refresh.sh and claude-cleanup.sh are installed.

Permission Denied

If kill/delete fails due to permissions:

Warning: Some operations failed due to insufficient permissions.
Failed files: 5
Successfully deleted: 5572 files

No ~/.claude/ Directory

If directory doesn't exist:

Error: ~/.claude/ directory not found.
Nothing to clean up.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

34.44%
按下载量换算25

Claude

29.82%
按下载量换算22

Cursor

18.8%
按下载量换算14

Gemini CLI

9.64%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills