An automation workflow that guides developers through implementing and verifying a dynamic account dropdown filter based on the chosen payment method.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install filter-account-dropdown-entry-workflow-122817
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install filter-account-dropdown-entry-workflow-122817 using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The Filter Account Dropdown Entry Workflow skill is a structured implementation guide designed for Openclaw Skills users. It assists developers and maintainers in executing front-end enhancements—specifically filtering available financial accounts based on a user's selected payment method in a new entry form. This technical framework ensures that complex UI data dependencies are handled seamlessly without manual overhead.
By deploying this skill within the Openclaw Skills ecosystem, teams can reduce form submission errors, eliminate invalid account-method combinations, and streamline the overall data entry user experience. It provides context-aware guidance from planning through validation, eliminating the need to cross-reference fragmented issue threads.
To activate this workflow within your environment, ensure it is registered in your Openclaw Skills configuration directory. Trigger the skill by calling its specific identifier or using descriptive keyword phrases.
# Trigger the workflow directly using the skill identifier
openclaw run filter-account-dropdown-entry-workflow --prompt "Help me implement the dropdown filter"
You can also trigger it implicitly by referencing key architectural phrases like enhancement, filter account dropdown, or new entry form based on selected payment method in your agent prompts.
The skill manages its execution lifecycle and references external source evidence using the following structured taxonomy:
| Data Component | Format / Path | Description |
|---|---|---|
| Source Evidence | references/requirement-plan.md |
Contains planning details, raw criteria, and core evidence for the enhancement. |
| Tailored Artifact | Markdown / Code Blocks | The immediate situational answer, code snippet, or UI architectural plan. |
| Reusable Checklist | Markdown Unordered List | A repeatable validation checklist for ensuring form logic consistency. |
| Verification Note | Markdown Section | A summary proving the result addresses the requirement and can be acted upon independently. |
Loading
An AI-powered knowledge base orchestrator that automates data ingestion, querying, linting, and synthesis for Obsidian wikis.

An AI-powered planning skill designed to help founders and operators emigrate to the USA, launch a business, and execute wealth-building strategies for Q3 2026.

An automated helper to analyze, plan, and generate actionable documentation for resolving furnished apartment disputes, specifically tailored for Hello Landing issues.

An AI-powered validation assistant that helps creators craft structured workflows, checklists, and strategic briefs for product planning on Hacker News and beyond.

An AI-powered nutrition analysis tool equipped with a 2,000+ entry Chinese food database, designed to parse natural language meal descriptions and track goal-oriented macro targets.

An intelligent travel agent that generates optimized day-by-day itineraries, custom budgets, transport routing, and contingency plans based on user preferences.








































