timetopost-social-scheduler
Draft and Schedule Social Posts with TimeToPost
Managing platform-specific posts requires consistent wording, account selection, and approval. This skill guides TimeToPost MCP drafting, timing recommendations, and scheduling after explicit user approval.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "timetopost-social-scheduler" from https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler.md and its manifest at https://skillstore.io/api/skills/melmayssonowen-timetopost-social-scheduler/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「timetopost-social-scheduler」を使用しています。 Draft separate LinkedIn and X announcements for our new Monday community workshop. Keep both pending review.
期待される結果:
- LinkedIn draft: Our community workshop starts Monday. What would you like us to cover in the first session?
- X draft: New community workshop starts Monday. Which topic should we explore first?
- Review status: Both versions remain pending approval. Nothing is scheduled.
「timetopost-social-scheduler」を使用しています。 Suggest a time for my draft when no account history is available. Use America/Los_Angeles.
期待される結果:
- Timing basis: No account-specific recommendation is available.
- Proposed time: Tuesday at noon, America/Los_Angeles. This is a generic heuristic, not an account-based result.
- Approval status: Scheduling awaits your approval of the exact draft, account, and time.
セキュリティ監査
安全All 18 static findings are false positives involving Markdown tool names, legitimate service URLs, or ordinary writing guidance. The workflow verifies workspace permissions and requires explicit approval before scheduling. No evidence found of prompt injection, credential exfiltration, or malicious shell execution in the reviewed files.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/melmayssonowen-timetopost-social-scheduler/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/melmayssonowen-timetopost-social-scheduler.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形式の引用
melmayssonowen. (2026). timetopost-social-scheduler security audit report (audit version 1) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler/audits/1BibTeX形式の引用
@techreport{melmayssonowen-melmayssonowen-timetopost-social-scheduler-2026,
author = {melmayssonowen},
title = {timetopost-social-scheduler security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler/audits/1},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "timetopost-social-scheduler security audit report (audit version 1)"
version: "1.0.0"
type: report
authors:
- name: "melmayssonowen"
date-released: "2026-10-22"
url: "https://skillstore.io/skills/melmayssonowen-timetopost-social-scheduler/audits/1"
identifiers:
- type: other
value: "skillstore:melmayssonowen-timetopost-social-scheduler:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare a Product Announcement
Create distinct announcement drafts for connected accounts and review copy, destination accounts, and suggested times before scheduling.
Review Client Approval Queues
Inspect pending drafts in the intended workspace and schedule only the specific versions approved by the client.
Maintain a Consistent Publishing Voice
Use recent posts to prepare account-specific content while checking facts and adapting wording for each platform.
これらのプロンプトを試す
Check my TimeToPost workspace, connected accounts, and publishing permissions. Do not create drafts or schedule anything.
Draft separate LinkedIn and X posts about [announcement] for [audience]. Match my recent posts. Ask for missing facts and keep everything pending review.
Prepare three distinct posts about [topic] for [account IDs]. Suggest times in [time zone] using available history. Show every draft without scheduling.
Show draft [draft ID], its exact copy, account ID, and proposed time in [time zone]. Wait for my explicit confirmation before scheduling. Then verify status.
ベストプラクティス
- Confirm the workspace, publishing permission, and connected account IDs before creating or approving drafts.
- Review exact copy, destination accounts, time zone, and proposed times before authorizing scheduling.
- Check current platform capabilities and review campaign attribution before using tagged links.
回避
- Scheduling a draft based on implied approval or approval of an earlier version.
- Posting identical text across platforms or inventing unsupported product claims.
- Treating generic timing suggestions or bundled platform limits as verified account-specific information.
よくある質問
Do I need a TimeToPost account?
Does creating a draft publish it?
Can a draft-only connection schedule posts?
How are posting times selected?
Where should I provide authentication credentials?
Are campaign link tools available on every connection?
開発者情報
作成者
melmayssonowenライセンス
MIT
作者バージョン
v1.0.0
Skillstore リビジョン
r1
参照
aacb61f7f2826e1d8c8e9e7aff6f39dd3ba53df4
メンテナンスの新しさ
2026/10/22
利用状況
0 ダウンロード · 0 閲覧
ファイル構成