技能 founder-brand-kickoff
📦
founder-brand-kickoff
內容修訂 r1 安全 ⚙️ 外部命令
Plan Your Next Founder-Brand Task
Founders can lose time deciding between brand setup and weekly content work. This skill checks readiness and posting progress to recommend the next task.
支援: Claude Codex Code(CC)
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "founder-brand-kickoff" from https://skillstore.io/skills/cmj-hub-founder-brand-kickoff.md and its manifest at https://skillstore.io/api/skills/cmj-hub-founder-brand-kickoff/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「founder-brand-kickoff」。 Where do I start? My brand configuration is missing.
預期結果:
- Status: Brand configuration is missing.
- Next: Begin founder-brand onboarding.
- Prepare your voice profile, four topic pools, and posting cadence.
- Ready to begin?
正在使用「founder-brand-kickoff」。 All setup checks pass. My cadence is four posts weekly, two are logged, and Process is the next slot.
預期結果:
- This week: Two of four posts logged.
- Next pillar: Process.
- Suggested pool topic: How we review customer feedback.
- Alternatives: Our weekly planning routine; How we prioritize product fixes.
- Would you like a draft?
正在使用「founder-brand-kickoff」。 All setup checks pass, and I have logged four posts against a weekly cadence of four.
預期結果:
- This week: Four of four posts logged.
- The weekly queue is complete.
- Return on Monday for the next rotation.
安全審計
安全v1 • 2026/10/3 開啟版本化報告
All 17 static findings are false positives caused by Markdown inline backticks and code fences, not Ruby or shell execution. The file describes state checks, routing, and example responses for a founder-brand workflow. No evidence found of prompt injection, credential access, data exfiltration, or malicious commands in the reviewed file.
1
已掃描檔案
96
分析行數
0
複核項目
0
已忽略的誤報
風險因素
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/cmj-hub-founder-brand-kickoff/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/cmj-hub-founder-brand-kickoff?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/cmj-hub-founder-brand-kickoff?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-founder-brand-kickoff/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/cmj-hub-founder-brand-kickoff.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 引用
cmj-hub. (2026). founder-brand-kickoff security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-founder-brand-kickoff/audits/1BibTeX 引用
@techreport{cmj-hub-cmj-hub-founder-brand-kickoff-2026,
author = {cmj-hub},
title = {founder-brand-kickoff security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-founder-brand-kickoff/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: "founder-brand-kickoff security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-founder-brand-kickoff/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-founder-brand-kickoff:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 55
架構
85
可維護性
87
內容
65
社群
83
規範符合度
你可以打造什麼
Start a founder-brand program
Identify missing configuration and begin the onboarding route before planning weekly posts.
Prepare a weekly writing session
Review posting progress and select a topic from the next content pillar.
Review a client setup
Check topic pools, voice phrases, stories, and cadence to identify the next preparation task.
試試這些提示
Find the starting point
Where do I start with founder-brand? Check whether my brand setup is ready and recommend the first task.
Review program status
/founder-brand status. Summarize my configuration, topic pools, voice phrases, stories, cadence, and posts logged this week.
Choose the next weekly topic
What is next for my content this week? Use my cadence and logged posts to suggest the next pillar topic and alternatives.
Audit readiness before drafting
Review all four topic pools, voice phrases, stories, cadence, and weekly completion. Identify the first unmet routing condition before recommending a draft.
最佳實務
- Keep configuration and weekly post records current before requesting the next task.
- Prepare at least three topics per pillar, five voice phrases, and three anonymized stories.
- Review suggested topics and confirm drafting before continuing to downstream skills.
避免
- Expecting this router to replace the full onboarding or drafting skill pack.
- Treating example status values as measurements of your own progress.
- Using confidential emails or identifiable customer stories without permission and anonymization.
常見問題
What does this skill do?
It checks founder-brand readiness and weekly progress, then recommends the next setup or content task.
How is it activated?
The parent founder-brand skill loads it on bare invocation. It also lists questions about getting started or choosing the next content task.
What information does it need?
It expects brand configuration, a SOUL voice profile, topic pools, stories, cadence, and weekly posting records.
What readiness thresholds does it use?
It checks four pillars with three topics each, five voice phrases, three stories, and a positive weekly posting cadence.
Does it publish posts automatically?
No publishing integration is provided. Weekly mode suggests a topic and asks whether to draft it.
What happens when the weekly target is complete?
It reports that the queue is complete and recommends returning on Monday for the next rotation.