Навыки baseline-collector-34030
📦

baseline-collector-34030

Ревизия содержимого 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)
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-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Протестировать

Использование «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.

Аудит безопасности

Высокий риск

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.

5
Просканировано файлов
196
Проанализировано строк
0
Пункты проверки
0
Ложные срабатывания проигнорированы

Подтверждённые проблемы безопасности (2)

Высокий
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.
Средний
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.

Факторы риска

Аудитор:: 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

Почему такая оценка Достоверность доказательств: Средний
45
Архитектура
85
Сопровождаемость
87
Контент
65
Сообщество
91
Соответствие спецификации

Что вы можете построить

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.

Сведения для разработчиков

Автор

silakge

Лицензия

Apache-2.0

Ревизия Skillstore

r1

Примечание о версии

Автор не указал версию.

Ссылка

171c0d4efb8b9775cc0ac857be32a63489772870

Актуальность поддержки

01.10.2026

Использование

0 загрузок · 0 просмотров

Структура файлов