published-vs-planned
Verify Published Content Against Your Plan
Scheduler confirmations do not prove that posts are live or uploads are accessible. This skill guides evidence-based checks against approved plans and produces timestamped reconciliation tables.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "published-vs-planned" from https://skillstore.io/skills/rabbitdesigns22-published-vs-planned.md and its manifest at https://skillstore.io/api/skills/rabbitdesigns22-published-vs-planned/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «published-vs-planned». Illustrative check: two cross-posted items were planned for 10:00 UTC. Both scheduler entries exist, but only Facebook is live.
Ожидаемый результат:
- Checked 4 November, 10:10 UTC: one of two items verified live.
- Instagram reel: planned 10:00 UTC; scheduled ok; live missing. Likely cause: cross-post failure. Fix: request approval to republish, then verify.
- Facebook post: planned 10:00 UTC; scheduled ok; live ok. No gap found.
Использование «published-vs-planned». Illustrative delivery check: launch.pdf opens in the destination folder, but budget.xlsx cannot be checked because access expired.
Ожидаемый результат:
- Checked 4 November, 15:00 UTC: one file verified; one file not checked.
- budget.xlsx: destination not checked because access expired. Fix: restore authorized access and repeat verification.
- launch.pdf: correct destination and filename; size greater than zero; opens successfully.
Аудит безопасности
БезопасноAll seven static findings are false positives involving Markdown status labels, ordinary publication questions, and a report timestamp. No evidence found of command execution, system reconnaissance, prompt injection, or data exfiltration in the reviewed file. The skill describes publication verification and permits corrective actions with owner approval where required.
Факторы риска
⚙️ Внешние команды (2)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/rabbitdesigns22-published-vs-planned/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/rabbitdesigns22-published-vs-planned?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/rabbitdesigns22-published-vs-planned?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/rabbitdesigns22-published-vs-planned/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/rabbitdesigns22-published-vs-planned.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
rabbitdesigns22. (2026). published-vs-planned security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/rabbitdesigns22-published-vs-planned/audits/1Цитата BibTeX
@techreport{rabbitdesigns22-rabbitdesigns22-published-vs-planned-2026,
author = {rabbitdesigns22},
title = {published-vs-planned security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/rabbitdesigns22-published-vs-planned/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: "published-vs-planned security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "rabbitdesigns22"
date-released: "2026-11-11"
url: "https://skillstore.io/skills/rabbitdesigns22-published-vs-planned/audits/1"
identifiers:
- type: other
value: "skillstore:rabbitdesigns22-published-vs-planned:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Reconcile client publishing
Compare approved client calendars with scheduler queues and live profiles, separating Facebook and Instagram results.
Confirm campaign launch posts
Check launch assets, captions, accounts, and timing after scheduled slots, then report missing or incorrect items.
Verify shared file deliveries
Confirm expected files appear in destination folders, have nonzero sizes, and open successfully before reporting delivery.
Попробуйте эти промпты
Check whether [post] is live on [account]. Use [planned time and timezone]. Report the evidence and check time; mark unavailable access as not checked.
Compare [approved calendar] with [scheduler] entries. Check each account, network, format, timezone, asset, and caption. Return the reconciliation table with gaps first.
Audit [campaign plan] across [networks] and [destination folder]. Verify due posts and uploaded files. Mark future slots not yet due. Request approval before changes.
Compare [previous timestamped table] with current evidence for [plan]. Report changed rows, unresolved gaps, and the current timezone. Request approval before corrective actions.
Лучшие практики
- Start from the approved calendar and record a timezone for every planned item.
- Verify scheduler entries independently from live posts, and check each network separately.
- Timestamp each report, retain the previous table, and obtain required approval before corrective actions.
Избегать
- Calling an item published solely because a tool, toast, log, or earlier report says it succeeded.
- Treating a successful cross-post on one network as proof that all destinations are live.
- Marking inaccessible, delayed, expired, or incorrectly filtered content as missing without checking the relevant context.
Часто задаваемые вопросы
Does this skill publish posts automatically?
Which scheduling platforms does it cover?
Can it verify private accounts?
How are timezone differences handled?
Can it verify uploaded files?
Does it measure engagement or run background checks?
Сведения для разработчиков
Автор
rabbitdesigns22Лицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
f38ac41a6255e57978dd6f276aec539d5e9b5255
Актуальность поддержки
12.11.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md