Compétences baseline-collector-34030

📦

baseline-collector-34030

Name: baseline-collector-34030
Author: silakge

Révision du contenu r1 Risque élevé 📁 Accès au système de fichiers⚙️ Commandes externes

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.

Prend en charge: Claude Codex Code(CC)

⚠️ 38 Médiocre

Maintain this Skill? Claim it ⚠️ 38 Médiocre

Arrêtez-vous et demandez confirmation avant l’installation.

Examinez le plan et obtenez le consentement explicite de l’utilisateur avant de modifier des fichiers.

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/silakge-baseline-collector-34030.md manifest signé GET /api/skills/silakge-baseline-collector-34030/manifest lockfile signé GET /api/skills/silakge-baseline-collector-34030/lockfile

Tester

Utilisation de « baseline-collector-34030 ». The configured trigger file is absent. What happens when the client runs?

Résultat attendu:

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

Utilisation de « baseline-collector-34030 ». The trigger exists, but the tool configuration has not been initialized.

Résultat attendu:

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

Utilisation de « baseline-collector-34030 ». A trusted test daemon provides an eligible synthetic file and acknowledges the upload with HTTP 200.

Résultat attendu:

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

Audit de sécurité

Risque élevé

v1 • 01/10/2026 Ouvrir le rapport versionné

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.

Fichiers analysés

196

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Préoccupations de sécurité confirmées (2)

Élevé

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.

Moyen

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.

Facteurs de risque

📁 Accès au système de fichiers (4)

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

⚙️ Commandes externes (6)

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

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

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

Badge 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)

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>

Carte intégrable

<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>

Citations académiques (APA · BibTeX · CFF)

Citation 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

Citation 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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

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.

Bonnes pratiques

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.

Éviter

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.

Foire aux questions

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.