Agent Skills › zhaoxuya520/reverse-skill › competition-linux-credential-pivot

competition-linux-credential-pivot

GitHub

用于CTF沙箱中追踪Linux凭证、令牌及密钥的接受与复用，分析本地提权或横向移动路径。

CTF-Sandbox-Orchestrator/competition-linux-credential-pivot/SKILL.md zhaoxuya520/reverse-skill

触发场景

用户询问Linux认证痕迹追踪需要解释跨节点横向移动

安装

npx skills add zhaoxuya520/reverse-skill --skill competition-linux-credential-pivot -g -y

更多选项

非标准路径

npx skills add https://github.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-linux-credential-pivot -g -y

不安装直接使用

npx skills use zhaoxuya520/reverse-skill@competition-linux-credential-pivot

指定 Agent (Claude Code)

npx skills add zhaoxuya520/reverse-skill --skill competition-linux-credential-pivot -a claude-code -g -y

安装 repo 全部 skill

npx skills add zhaoxuya520/reverse-skill --all -g -y

预览 repo 内 skill

npx skills add zhaoxuya520/reverse-skill --list

SKILL.md

Frontmatter

{
    "name": "competition-linux-credential-pivot",
    "description": "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Linux credential artifacts, service tokens, SSH material, cloud and container secrets, socket-level trust, and host-to-host pivot chains. Use when the user asks to trace Linux auth artifacts, accepted token or key replay, socket or service-account trust edges, sudo or capability abuse, or explain lateral movement across Linux challenge nodes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here."
}

Competition Linux Credential Pivot

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive edge is Linux credential material and where that material is accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

Separate credential storage from accepted privilege.
Record user, process, namespace, socket, key file, and service trust boundary before conclusions.
Keep artifact recovery, replay path, and resulting capability in one chain.
Distinguish local escalation from lateral host pivot.
Reproduce one minimal artifact-to-accepted-access path.

Workflow

1. Map Credential And Trust Artifacts

Record SSH keys, agent sockets, kubeconfigs, cloud tokens, service-account secrets, env vars, config files, and process memory clues.
Note sudoers rules, capabilities, setuid binaries, systemd unit context, and namespace boundaries.
Keep each artifact tied to owner, scope, and expected accepting service.

2. Prove Replay And Pivot

Show where key, token, socket, or secret is accepted: SSH, API, Unix socket, container runtime, or control-plane endpoint.
Record host target, protocol, principal, and resulting session or privilege.
Distinguish authentication success from useful capability gain.

3. Reduce To Decisive Linux Pivot Chain

Compress to: recovered artifact -> accepted replay path -> pivot host or privilege transition -> resulting capability.
State whether root cause is weak key handling, token leakage, socket trust, sudo or capability abuse, or namespace crossover.
If the chain pivots into kernel exploit boundaries, hand off to kernel container escape skill.