Skip to main content

ghostwriter-oplog

Use for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.

설치로 이동

소스 정보

저장소
SpecterOps/skills
최근 소스 활동
2026년 8월 14일 01:16
감지된 SKILL.md 언어
영어
스타
625
포크
68

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
4 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
ghostwriter-oplog
description
Use for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.
metadata
{"author":"GhostWorks"}
# Ghostwriter Oplog Use this skill when the user wants to create Ghostwriter operation log entries from Codex. ## Inputs Accept one of these actions: - `config` — show required environment variables and current expected names. - `quick <description> [--tags tag1,tag2]` — create a timestamped entry. - `evidence <file-path> <description> [--tags tag1,tag2]` — create an entry with file contents or a binary-file note. - `guided` — ask for entry type, description, optional evidence, destination, tool, and tags before logging. ## Environment Preferred variables: - `GHOSTWRITER_OPLOG_ID` - `GHOSTWRITER_OPERATOR` - `GHOSTWRITER_SOURCE_IP` optional Accepted legacy aliases: - `GW_OPLOG_ID` - `GW_OPERATOR_NAME` - `GW_SOURCE_IP` If required values are missing, do not guess. Tell the user to set the preferred variables in their shell or Codex environment and restart Codex if needed. ## Logging Workflow 1. Resolve `oplog_id` from `GHOSTWRITER_OPLOG_ID` or `GW_OPLOG_ID`. 2. Resolve `operator_name` from `GHOSTWRITER_OPERATOR` or `GW_OPERATOR_NAME`. 3. Resolve optional `source_ip` from `GHOSTWRITER_SOURCE_IP` or `GW_SOURCE_IP`. 4. Get a UTC timestamp with `date -u +"%Y-%m-%dT%H:%M:%SZ"`. 5. Use the Ghostwriter MCP `create_oplog_entry` tool with resolved fields. 6. Confirm the entry ID and summarize the fields recorded. ## Action Details ### quick Parse everything before `--tags` as the description. Parse tags as a comma-separated list. Submit `description`, `start_date`, optional `tags`, and resolved operator/source fields. ### evidence Read the provided file path. If it is text, include file contents as `output`. If it appears binary or cannot be decoded safely, set `output` to `[Binary file: <path>]` and include the file path in the description. ### guided Collect: - entry type: command execution, discovery, credential access, or evidence capture - description - optional evidence file path - optional destination IP/hostname - optional tool name - optional tags Then submit the completed entry through `create_oplog_entry`. ### config Show this minimum configuration: ```bash export GHOSTWRITER_OPLOG_ID=<oplog-id> export GHOSTWRITER_OPERATOR=<operator-name> export GHOSTWRITER_SOURCE_IP=<source-ip> # optional ``` If the user needs to discover projects or oplogs first, use the `ghostwriter-mcp` skill to verify the MCP connection and list projects/oplogs.
GitHub에서 보기