Install
$ agentstack add skill-philoserf-claude-code-config-flowershow-cli Open-source listing — not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Pipes remote content directly into a shell (remote code execution).
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ 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.
About
Use fl to publish Markdown to Flowershow from the terminal. The CLI is the Go-based successor to the deprecated @flowershow/publish npm package — do not use npx/bunx/npm install -g; install the binary instead.
Install / upgrade
macOS and Linux — the install script auto-detects platform and drops fl into /usr/local/bin/:
curl -fsSL https://raw.githubusercontent.com/flowershow/flowershow/main/apps/cli/install.sh | sh
Re-run the same command to upgrade. Verify with fl --help or command -v fl.
For Windows or manual installs, see .
Authenticate
fl login # browser OAuth flow; stores token at ~/.flowershow/token.json
fl whoami # show current user
fl logout # remove token
Tokens use the fs_cli_ prefix and do not expire by default. Revoke from the dashboard or fl logout.
Publish (idempotent — same command creates or syncs)
fl ./my-note.md # single file
fl ./intro.md ./ch1.md ./ch2.md # multiple files (first filename → site name)
fl ./my-notes # folder
fl --name my-custom-site ./notes # explicit site name (only needed on first publish)
fl --yes ./notes # skip the confirmation prompt (scripts/CI)
On first publish: confirmation prompt shows site name + URL, the site is created, files upload to R2, and for folder mode a .flowershow config is written so subsequent runs auto-resolve the site. On subsequent runs: delta sync (new + modified uploaded, deleted removed).
Sites resolve at https://my.flowershow.app/@{username}/{project-name}. Project name comes from the first filename (file mode) or the folder name (folder mode).
Site management
fl list # list sites with names, URLs, timestamps
fl delete # destructive; removes site and all files
Before running fl delete: confirm the exact project name with the user first. It permanently removes the site and all its files with no undo. Never run it on a name you inferred — only one the user explicitly named.
File filtering
fl automatically skips .git/, node_modules/, .cache/, dist/, build/, .next/, .vercel/, .turbo/, .DS_Store, Thumbs.db, .env*, *.log. If a .gitignore is present in the published folder, its patterns are also applied.
Telemetry opt-out
export FLOWERSHOW_TELEMETRY_DISABLED=1
Do not use when
- The deprecated
@flowershow/publishnpm tool — out of support; do not invoke viabunx/npx.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: philoserf
- Source: philoserf/claude-code-config
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.