Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Make Bot Ui

ASecurity

Build a local control page that submits validated actions to an authenticated webhook, with optional private-network access.

2 stars
0 votes
0 copies
0 views
Added 10/1/2026
ai-agentsrust

Security Analysis

A100/100

Scanned 10/1/2026

$npx -y skills add williamwue/oh-my-stack --skill make-bot-ui --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Make Bot Ui?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Make Bot Ui
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/williamwue-make-bot-ui/badge)](https://www.skillsdirectory.com/skills/williamwue-make-bot-ui)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: make-bot-ui
description: "Build a local control page that submits validated actions to an authenticated webhook, with optional private-network access."
disable-model-invocation: true
---

# Make bot UI

Use when the user asks for a page or dashboard that wakes an existing bot or
automation through a webhook. Confirm that the target runtime exposes a
supported webhook trigger, a documented authentication mechanism, and a safe
way to store the credential. If a required capability is absent, stop at a
reviewable local UI and name the missing integration; a fabricated endpoint
must never be called live.

Define a small JSON action schema. Treat incoming form data and webhook bodies
as untrusted. Keep the credential server-side in a runtime-supported secret
store or a restricted local config file; never put it in browser code, source
control, chat, logs, or diagnostic output. Where a host offers a secret-request
flow, use it; otherwise ask the user to set the secret through the host's
secure mechanism without pasting it into conversation.

Build a page that posts to a local server, which validates the action and
forwards it to the configured webhook with the provider's documented headers,
timeout, and retry semantics. Never infer authentication headers or delivery
guarantees from another provider. Match field names in the UI, server, and
webhook consumer. A successful HTTP response proves only acceptance unless the
provider gives a separate completion signal. Probe with a harmless action and
verify both local response and target readback before saying the bot is live.

Default to a local loopback binding. If the user asks for private-network
access, use an existing approved network path and confirm its interface and
access controls before binding beyond loopback. Installing network software,
changing device login, or exposing the server requires explicit scope. Avoid
logging payloads that contain secrets or personal data; any delivery queue
needs bounded retention and deduplication before retries.

Return the local page path/URL, action schema, secret setup method without its
value, actual webhook proof, and network reachability. Mark absent target
confirmation or private-network checks as unverified.

Attribution

williamwuewilliamwue
View sourceSee grades on GitHubMore from williamwue →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →