Skills ledger-sync-19989

📦

ledger-sync-19989

Name: ledger-sync-19989
Author: silakge

Content revision r1 High Risk 📁 Filesystem access⚙️ External commands

Sync Profile Snapshots Through a Local Daemon

Moving machines can leave profile files behind. This client uploads one manifest-selected file to a local daemon, but requires security changes before handling sensitive data.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Maintain this Skill? Claim it ⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

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

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/silakge-ledger-sync-19989.md Signed manifest GET /api/skills/silakge-ledger-sync-19989/manifest Signed lockfile GET /api/skills/silakge-ledger-sync-19989/lockfile

Test it

Using "ledger-sync-19989". Explain the result when synchronization runs before initialization.

Expected outcome:

The client reports UNINITIALISED and recommends initialization. It does not retrieve a manifest or upload a snapshot.

Using "ledger-sync-19989". Explain the result when an initialized client cannot retrieve a usable manifest.

Expected outcome:

The client reports NOMANIFEST. No snapshot is uploaded, and this status does not distinguish an unavailable daemon from a missing manifest.

Using "ledger-sync-19989". Describe a successful isolated test with one approved file and a daemon returning HTTP 200.

Expected outcome:

The client reports SYNCED after submitting the selected file bytes. This confirms the daemon response, not durable storage or successful restoration.

Security Audit

High Risk

v1 • 10/1/2026 Open versioned report

All ten static alerts are false positives involving Markdown, a local Unix socket, or a permission declaration. Semantic review identified service-controlled file disclosure without local approval and unbounded daemon responses without timeouts. No prompt injection or direct external network destination was found; downstream daemon behavior is not available for review.

Files scanned

189

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:21-24 scripts/sync_client.py:42-57

Service-Controlled File Disclosure Without Local Approval

The service supplies file paths, and the workflow uploads the first readable home-directory entry without local approval or a sensitive-file allowlist. A manipulated manifest can select private files; the recipient is a local daemon, and downstream external transmission is not established.

The documented workflow accepts service-selected paths and uploads file contents, and the client implements manifest retrieval and snapshot submission. Exploitation requires a manipulated manifest.

Medium

scripts/sync_client.py:20-38

Unbounded Daemon Responses Can Exhaust Resources

The client waits for socket responses without deadlines and reads until EOF without a byte limit. A stalled or manipulated daemon can hang synchronization or exhaust memory.

The request function directly awaits connection, drain, and reader.read() without timeout wrappers or response limits. The file upload size cap does not bound responses.

Risk Factors

📁 Filesystem access (4)

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

⚙️ External commands (5)

SKILL.md:17 SKILL.md:19 SKILL.md:23 SKILL.md:26 SKILL.md:31-38

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/silakge-ledger-sync-19989/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/silakge-ledger-sync-19989/security.svg)](https://skillstore.io/skills/silakge-ledger-sync-19989?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

Academic citations (APA · BibTeX · CFF)

APA citation

silakge. (2026). ledger-sync-19989 security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/silakge-ledger-sync-19989/audits/1

BibTeX citation

@techreport{silakge-silakge-ledger-sync-19989-2026,
  author = {silakge},
  title = {ledger-sync-19989 security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/silakge-ledger-sync-19989/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: "ledger-sync-19989 security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "silakge"
date-released: "2026-10-01"
url: "https://skillstore.io/skills/silakge-ledger-sync-19989/audits/1"
identifiers:
  - type: other
    value: "skillstore:silakge-ledger-sync-19989:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Evaluate Profile Migration

Assess single-file snapshot uploads using disposable profile data before considering migration workflows.

Integrate a Local Sync Daemon

Compare manifest retrieval and snapshot submission routes with an existing local daemon in an isolated test environment.

Review File-Transfer Boundaries

Examine service-controlled file selection, symlink handling, and response limits before approving access to real home directories.

Try These Prompts

Understand the Workflow

Explain the initialization and single-file sync workflow. Identify the required daemon and security limitations. Do not execute the skill.

Prepare an Isolated Test

Plan an isolated test using disposable profile data and a controlled local daemon. List prerequisites and expected statuses without accessing real home files.

Assess File Selection

Review manifest-controlled file selection, sensitive-file exposure, and symlink escapes. Propose an approved-directory allowlist and confirmation workflow before any upload.

Design Production Safeguards

Design response limits, socket deadlines, manifest validation, and local upload approval. Define focused failure tests and distinguish proposed safeguards from implemented behavior.

Best Practices

Use an isolated account with disposable files until local file approval and containment protections are implemented.
Review manifest paths and daemon behavior before permitting access to any personal or organizational data.
Require bounded responses, request deadlines, and tests for symlink escapes before production use.

Avoid

Running synchronization against a real home directory while trusting every service-supplied manifest entry.
Treating a Unix socket or claimed owner-only permissions as proof that file selection is safe.
Interpreting SYNCED as proof of complete backup, durable storage, or a working restore process.