← Browse

@majiayu000/dotfiles

B

Use when managing dotfiles repository. Triggers: (1) checking dotfiles structure or package list, (2) adding or removing packages, (3) setting up dotfiles on new machine, (4) syncing changes from other machines, (5) stow command usage questions.

skillclaude

Install

agr install @majiayu000/dotfiles --target claude

Writes 2 files into .claude/skills/, pinned to git-73ccb3cc.

  • .claude/skills/dotfiles/SKILL.md
  • .claude/skills/dotfiles/metadata.json

Document


name: dotfiles description: Use when managing dotfiles repository. Triggers: (1) checking dotfiles structure or package list, (2) adding or removing packages, (3) setting up dotfiles on new machine, (4) syncing changes from other machines, (5) stow command usage questions.

dotfiles 管理スキル

実行方法

パッケージ操作やセットアップはsubagentを起動して実行すること。 構成調査が必要な場合はGemini MCPに委託する。

関連ドキュメント

  • @structure.md - リポジトリ構成
  • @maintenance.md - メンテナンス方針
  • @sync.md - 更新の取り込み
  • @setup.md - 新規PCセットアップ

クイックリファレンス

よく使うコマンド

# 全パッケージをインストール
./install.sh

# 特定パッケージのみ
./install.sh shell nvim

# ドライラン(変更確認)
./install.sh -n

# パッケージ削除
./install.sh -D shell

# MCPサーバーインストール
~/.claude/scripts/install-mcp.sh

パッケージ追加手順

  1. packages/<name>/ ディレクトリ作成
  2. ホームディレクトリからの相対パスで配置
  3. ./install.sh <name> で適用

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-73ccb3cc38892026-07-31