self-hosted-funnel-launch
Launch a Self-Hosted Sales Funnel
Launching a production funnel requires coordinated infrastructure, integrations, pages, and testing. This skill provides a practical Autonnel workflow for deployment and agent-driven operation.
安裝前請停止並請求確認。
請審查安裝計畫,並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "self-hosted-funnel-launch" from https://skillstore.io/skills/autonnel-self-hosted-funnel-launch.md and its manifest at https://skillstore.io/api/skills/autonnel-self-hosted-funnel-launch/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「self-hosted-funnel-launch」。 Compare deployment options for a small campaign with limited operations support.
預期結果:
- Recommendation: Cloudflare Workers for low server maintenance and efficient static delivery.
- Prerequisites: managed Postgres, Cloudflare account, domain, secrets, and a backup plan.
- Watch first: daily cache write limits and database provider limits.
正在使用「self-hosted-funnel-launch」。 Create a launch checklist for a funnel with checkout, upsell, and advertising tracking.
預期結果:
- Configure the product catalog and payment provider before writing landing page claims.
- Publish each page and the funnel binding separately.
- Test a purchase, accepted and declined upsells, refund, receipt, error page, and conversion events.
正在使用「self-hosted-funnel-launch」。 Plan a controlled MCP update to a live headline.
預期結果:
Read the current page, change only the headline property in the draft, verify the result, publish separately, and confirm the rendered landing page.
安全審計
高風險Most static alerts are false positives caused by Markdown syntax, prose, placeholders, and bounded deployment examples. Confirmed risks involve secret generation, command-line credential exposure, an unpinned package installer, and an insufficiently constrained server-side media fetch.
已確認的安全問題 (2)
能力複核項目 (4)
這些是真實的本機能力,對此技能而言可能是預期行為,因此需要複核,但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (50)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/autonnel-self-hosted-funnel-launch/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/autonnel-self-hosted-funnel-launch?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/autonnel-self-hosted-funnel-launch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/autonnel-self-hosted-funnel-launch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/autonnel-self-hosted-funnel-launch.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 引用
autonnel. (2026). self-hosted-funnel-launch security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/autonnel-self-hosted-funnel-launch/audits/1BibTeX 引用
@techreport{autonnel-autonnel-self-hosted-funnel-launch-2026,
author = {autonnel},
title = {self-hosted-funnel-launch security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/autonnel-self-hosted-funnel-launch/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: "self-hosted-funnel-launch security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "autonnel"
date-released: "2026-08-08"
url: "https://skillstore.io/skills/autonnel-self-hosted-funnel-launch/audits/1"
identifiers:
- type: other
value: "skillstore:autonnel-self-hosted-funnel-launch:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Deploy a Production Funnel
Choose Workers or Docker, configure infrastructure, and prepare a secure Autonnel instance for launch.
Validate Revenue Tracking
Connect commerce, payments, email, and advertising systems, then test purchases, refunds, and conversion events.
Automate Funnel Operations
Connect an agent through MCP and create, verify, publish, and update funnel pages with controlled write access.
試試這些提示
Compare Cloudflare Workers and Docker for [traffic], [budget], and [operations capacity]. Recommend one path and list its prerequisites.
Create a deployment checklist for [chosen platform] using [database provider] and [domain]. Include secrets, storage, backups, health checks, and rollback preparation.
Plan a funnel with [offer], [checkout product], [upsell], and [tracking platforms]. Specify page order, integrations, publishing steps, and prelaunch transaction tests.
Design an MCP workflow to update [page] in [funnel]. Require read-before-write, draft verification, explicit publishing, error checks, and least-privilege credentials.
最佳實務
- Pin deployment artifacts and verify current provider limits before production use.
- Use separate read-only and write-enabled API keys, with one credential assigned to each agent.
- Complete real purchase, refund, failure, tracking, and background-job tests before increasing traffic.
避免
- Do not expose development secrets or pass production credentials through command arguments.
- Do not regenerate an entire page document when changing one property.
- Do not treat a successful HTTP status as proof that an MCP tool call succeeded.