Skip to main content

structured-artifact-inspection

Use for unknown-size, large, generated, or high-output structured artifacts; avoid for small known config files or jq-style queries.

소스 정보

저장소
Rycen7822/Structured-Artifact-Viewer
최근 소스 활동
2026년 5월 9일 05:26
감지된 SKILL.md 언어
영어
스타
1
포크
0

설치 방법

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

소스 파일 검토

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

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
structured-artifact-inspection
description
Use for unknown-size, large, generated, or high-output structured artifacts; avoid for small known config files or jq-style queries.
# Structured Artifact Inspection Use this skill only for bounded inspection of structured artifacts when raw output could waste context: unknown-size or large JSON, JSONL/NDJSON, CSV/TSV, Parquet metadata, and generated tool artifact files. Do not use this for search, transformation, calculation, validation, editing, or precise jq-style querying. This plugin is a compact viewer, not a jq replacement. For small known files, especially ordinary config files, read them directly unless they contain long records or large fields. Prefer the MCP tool `structured_artifact_viewer` when available. Use the CLI `codex-view` only as a fallback or when the user explicitly asks for shell commands. Workflow: 1. Inspect the file shape with `op: "sniff"` or `codex-view sniff FILE`. 2. Summarize structure with `op: "summary"` or `codex-view summary FILE`. 3. Preview selected fields with `op: "select"` or `codex-view select FILE --fields name,status,score --limit 10`. 4. Never print full JSONL records by default; one record may be tens of kilobytes. 5. If exact full content is required, first prove the file is small or write raw output to a file and report only the path plus a short summary. Avoid raw `cat`, `head`, `tail`, `sed`, `nl`, and `python -m json.tool` on these files unless the user explicitly asks for raw content.
GitHub에서 보기