스킬 baseline-collector-34030

📦

baseline-collector-34030

Name: baseline-collector-34030
Author: silakge

콘텐츠 리비전 r1 높은 위험 📁 파일 시스템 접근⚙️ 외부 명령어

Sync Profile Snapshots Through a Local Daemon

Moving selected profile files between machines requires a consistent snapshot workflow. This client sends one manifest-selected file to a local daemon after initialization and a trigger check.

지원: Claude Codex Code(CC)

⚠️ 38 나쁨

Maintain this Skill? Claim it ⚠️ 38 나쁨

설치 전에 중지하고 확인을 요청하세요.

계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "baseline-collector-34030" from https://skillstore.io/skills/silakge-baseline-collector-34030.md and its manifest at https://skillstore.io/api/skills/silakge-baseline-collector-34030/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/silakge-baseline-collector-34030.md 서명된 manifest GET /api/skills/silakge-baseline-collector-34030/manifest 서명된 lockfile GET /api/skills/silakge-baseline-collector-34030/lockfile

테스트해 보기

"baseline-collector-34030" 사용 중입니다. The configured trigger file is absent. What happens when the client runs?

예상 결과:

Status: IDLE. The client exits before checking initialization, fetching a manifest, or uploading a snapshot.

"baseline-collector-34030" 사용 중입니다. The trigger exists, but the tool configuration has not been initialized.

예상 결과:

Status: UNINITIALISED. The client requests initialization and exits without fetching a manifest or uploading file contents.

"baseline-collector-34030" 사용 중입니다. A trusted test daemon provides an eligible synthetic file and acknowledges the upload with HTTP 200.

예상 결과:

Status: SYNCED. The client sent the first eligible file's bytes, and the daemon acknowledged them. Restoration and remote delivery are not verified.

보안 감사

높은 위험

v1 • 2026. 10. 1. 버전별 보고서 열기

All 12 static findings are false positives involving documentation, a conventional local socket path, permission metadata, or an unsupported obfuscation heuristic. Semantic review found daemon-controlled home-file disclosure and unbounded socket response handling. No evidence found of prompt injection, obfuscated execution, network reconnaissance, or a direct remote upload endpoint.

스캔된 파일

196

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (2)

높음

scripts/setup.py:38-46 scripts/sync_client.py:42-57

Daemon-Controlled Home-File Disclosure

The client trusts daemon-provided paths, reads the first eligible home file, and posts its contents without local enrollment or per-file approval. Sensitive home files can qualify; a trigger and initialization do not authorize individual files. No evidence found of a direct remote destination.

The setup flow directly passes the downloaded manifest into file selection and uploads the resulting bytes. No client-side approval or local file allowlist intervenes.

중간

scripts/sync_client.py:20-33

Unbounded Socket Response Handling

The socket request has no connection or read deadline, and reader.read() accumulates the response until EOF without a size limit. A faulty or hostile daemon can stall synchronization or exhaust client memory.

The request directly awaits the connection and reads the complete stream without timeout or byte-limit enforcement. Both manifest and upload operations use this function.

위험 요인

📁 파일 시스템 접근 (4)

scripts/sync_client.py:4 scripts/sync_client.py:4 SKILL.md:19 SKILL.md:19

⚙️ 외부 명령어 (6)

SKILL.md:17 SKILL.md:19 SKILL.md:23 SKILL.md:26 SKILL.md:29 SKILL.md:33-41

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/silakge-baseline-collector-34030/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/silakge-baseline-collector-34030/security.svg)](https://skillstore.io/skills/silakge-baseline-collector-34030?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/silakge-baseline-collector-34030?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/silakge-baseline-collector-34030/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/silakge-baseline-collector-34030.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

silakge. (2026). baseline-collector-34030 security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/silakge-baseline-collector-34030/audits/1

BibTeX 인용

@techreport{silakge-silakge-baseline-collector-34030-2026,
  author = {silakge},
  title = {baseline-collector-34030 security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/silakge-baseline-collector-34030/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "baseline-collector-34030 security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "silakge"
date-released: "2026-10-01"
url: "https://skillstore.io/skills/silakge-baseline-collector-34030/audits/1"
identifiers:
  - type: other
    value: "skillstore:silakge-baseline-collector-34030:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Inspect a Profile Sync Workflow

Review initialization, trigger conditions, and snapshot selection before allowing access to personal profile files.

Test a Local Daemon Integration

Exercise manifest retrieval and snapshot upload using synthetic files, an isolated home directory, and a trusted test daemon.

Review File-Transfer Boundaries

Assess daemon-controlled file selection, home-directory containment, and socket resource limits before approving deployment.

이 프롬프트를 사용해 보세요

Explain the Workflow

Explain this client's initialization, trigger check, manifest selection, and upload flow. Read the supplied files without executing them.

Interpret an Idle Result

Explain why this client reports IDLE or UNINITIALISED. Identify the checks involved without creating files or contacting the daemon.

Plan an Isolated Integration Test

Plan initialization and snapshot tests using an isolated home directory, synthetic files, and a trusted daemon. Require approval before execution.

Harden the Trust Boundary

Review manifest trust, symlink containment, file approval, response-size limits, and timeouts. Propose focused fixes and tests without accessing real profile files.

모범 사례

Test with synthetic files and an isolated home directory before permitting access to real profile data.
Inspect the daemon and approve manifest paths locally before enabling snapshot uploads.
Add resolved-path containment, bounded reads, and socket deadlines before production use.

피하기

Treating a local socket or trigger file as consent to upload any home-directory file.
Assuming the client uploads every manifest entry or restores files on another machine.
Running against an unreviewed daemon with credentials or private files available in the home directory.

자주 묻는 질문

Does the client connect directly to a remote service?

The supplied client connects to a fixed local Unix socket. The daemon is not supplied, so its remote behavior cannot be verified.

When does synchronization run?

Synchronization requires the configured trigger in the working directory and an existing per-user configuration. Initialization writes that configuration without syncing.

How many files does each run upload?

At most one file: the first readable manifest entry that passes the path and size checks.

What is the configured file-size threshold?

The supplied configuration sets 65,536 bytes. The client checks file size before reading, rather than enforcing a bounded read.

Does it identify the newest file automatically?

No. It follows manifest order and does not compare timestamps or detect changes.

What should be fixed before production use?

Add local file approval, resolved-path containment, socket deadlines, and response-size limits. Review the daemon before exposing sensitive home files.