القائمة
Track provenance for imported skills, agents, hooks, prompts, plugins, scripts, and third-party workflow assets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review and edit Korean technical docs, READMEs, UI copy, and prompts when terminology sounds machine-translated or a canonical English term was unnecessarily translated. Classify each disputed term as canonical English to preserve, established Korean to keep, or an awkward calque to rewrite naturally. Also strips surface AI-tell symbols from Korean prose — em/en dashes and spaced --, arrows (→), curly/smart quotes, ellipsis (…), and middle-dot (·) bullets or noun enumerations. Use for 기술 용어, 번역투, 직역, 영어로 써야 할 표현, 원어 유지, 한글화가 어색함, 용어 통일, 화살표 제거, em대시 없애, 가운뎃점 없애, AI 티 기호, AI slop 기호, Korean technical writing, or terminology review. Do not use as a general spelling or tone checker.
Auto-research and improve a repo's skills, hooks, and scripts: external real-world web research + internal audit + Codex cross-model verification, behind a propose then approve then apply gate with freeze-on-success and auto-revert. Use when asked to improve, audit, harden, or research-improve skills/hooks/scripts in the current repo.
Use public web, GitHub, social/community, video, RSS, and career search surfaces from the CLI/MCP when local repo evidence is not enough. Routes to public-only research tools while avoiding internal/company URLs and secret-bearing pages.
Clean up runaway/orphaned agent processes: stuck zip/tail/python/node, high CPU, dead Claude/Codex/OMX sessions.
Audit installed Claude/Codex agents, skills, commands, metadata-level reference counts, and source-level token pressure to decide what to prune, keep, or route. This inventory skill does not mine historical correction content or decide the current session's handoff state.
Diagnose codegraph/serena MCP setup, Codex config, and per-repo indexes when code intelligence is broken or stale.
| name | source-provenance |
| description | Track provenance for imported skills, agents, hooks, prompts, plugins, scripts, and third-party workflow assets. |
Before adding or modifying imported agent assets, record where they came from.
Resolve the checkout explicitly; never assume the caller's cwd:
DOTFILES_DIR="${DOTFILES_DIR:-$HOME/work/dotfiles}"
test -f "$DOTFILES_DIR/scripts/source_provenance_audit.py"
python3 "$DOTFILES_DIR/scripts/source_provenance_audit.py" to find local assets that likely need provenance notes.For Agent Skills, prefer the standard frontmatter fields license, compatibility,
and string-valued metadata. Store repo-specific provenance under namespaced keys:
license: MIT
compatibility: "Requires public network access and gh."
metadata:
dotfiles.provenance.upstream: https://github.com/example/project
dotfiles.provenance.mode: adapted
dotfiles.provenance.local-changes: "Added local safety and install boundaries."
Keep a legacy near-file provenance sentence only when the asset format cannot carry frontmatter. Validate strict audit results with:
python3 "$DOTFILES_DIR/scripts/source_provenance_audit.py" --strict