AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aipanel Installer

skill-simmzl-aipanel-openclaw-installer-skill · by simmzl

Create, continue, recover, and verify AIPanel installations through a conversational one-command flow. Use when a user wants to start creating AIPanel, deploy a new AIPanel instance, resume an interrupted installation, check installer progress, or finish the final setup inputs needed before deployment.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-simmzl-aipanel-openclaw-installer-skill

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-simmzl-aipanel-openclaw-installer-skill)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aipanel Installer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AIPanel Installer

Drive the AIPanel installer as a conversational workflow.

This skill is responsible for the instance creation path:

  • start a new AIPanel installation
  • continue a paused installation
  • report installer progress
  • collect the final user inputs
  • finish Vercel deployment
  • verify the deployed result

Do not use this skill for normal bookmark/category CRUD on an already-installed panel. That remains the job of aipanel-feishu-bitable.

Workflow

When a user says things like:

  • 开始创建 AIPanel
  • 创建 AIPanel
  • 安装 AIPanel
  • 继续 AIPanel 安装
  • 恢复 AIPanel 安装
  • 看看 AIPanel 装到哪一步了

follow this sequence:

  1. Prefer node scripts/installer/cli.mjs continue as the single orchestration entrypoint
  2. Use node scripts/installer/cli.mjs continue --execute when the flow needs to create real Feishu or Vercel resources
  3. Use node scripts/installer/cli.mjs status when you only need a conversational progress summary
  4. Use node scripts/installer/cli.mjs verify when you need to re-check the final deployment result

Final user inputs

The installer should minimize questions.

By default, only ask the user for:

  • ACCESS_PASSWORD
  • FEISHU_APP_SECRET

The installer should:

  • auto-generate JWT_SECRET
  • auto-detect FEISHU_APP_ID
  • auto-create FEISHU_BITABLE_APP_TOKEN
  • auto-create FEISHU_BITABLE_TABLE_ID
  • auto-create FEISHU_BITABLE_SOURCE_URL

Asking for Feishu App Secret

When asking for FEISHU_APP_SECRET, always include the detected FEISHU_APP_ID in the message.

Use wording equivalent to:

> 请提供与我自动识别到的 Feishu App ID cli_xxx 对应的 App Secret。

Never ask for an App Secret without naming the App ID it must match.

If FEISHU_APP_ID is not available, do not pretend the secret request is unambiguous. Report the block and ask the user to fix the local Feishu/Lark auth context first.

Progress reporting

Keep user-visible updates short and stage-based.

Good examples:

  • 前置检查通过,正在创建 Feishu 数据源。
  • Feishu 数据源已经创建完成,现在只差访问密码和 App Secret。
  • Vercel 部署已完成,正在验证面板是否可访问。

Avoid dumping raw CLI logs unless the user explicitly asks.

Recovery rules

Prefer resume over restart.

  • If Feishu app/table/source URL already exist in installer state, reuse them.
  • If only final inputs are missing, ask for them instead of re-running earlier stages.
  • If Vercel project info already exists, continue from deploy-related steps when possible.
  • If the user returns later and says “继续”, inspect state first and continue from the current stage.

Read details as needed:

  • references/flow.md
  • references/recovery.md
  • references/prompts.md

Success criteria

Before claiming completion, confirm at least:

  • a deployment URL exists
  • the deploy step succeeded
  • the installer state contains the final deployment URL

If verification is incomplete, say so explicitly rather than overstating success.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.