Bankr Agent - Token Deployment
This skill should be used when the user asks to "deploy token", "create token", "launch token", "Clanker", "claim fees", "token metadata", "update token", "mint new token", or any token deployment operation. Provides guidance on deploying ERC20 tokens via Clanker.
What this skill does
# Bankr Token Deployment Deploy and manage ERC20 tokens using Clanker. ## Supported Chains - **Base**: Primary deployment chain, full Clanker support - **Unichain**: Secondary option ## Deployment Parameters | Parameter | Required | Description | |-----------|----------|-------------| | Name | Yes | Token name (e.g., "MyToken") | | Symbol | Yes | Ticker, 3-5 chars (e.g., "MTK") | | Description | No | Token description | | Image | No | Logo URL or upload | | Website | No | Project website | | Twitter | No | Twitter/X handle | | Telegram | No | Telegram group | ## Prompt Examples **Deploy tokens:** - "Deploy a token called BankrFan with symbol BFAN" - "Create a memecoin: name=DogeKiller, symbol=DOGEK" - "Deploy token with website myproject.com and Twitter @myproject" **Claim fees:** - "Claim fees for my token MTK" - "Check my Clanker fees" - "Claim legacy Clanker fees" **Update metadata:** - "Update description for MyToken" - "Add Twitter link to my token" - "Update logo for MyToken" ## Rate Limits | User Type | Daily Limit | |-----------|-------------| | Standard Users | 1 token/day | | Bankr Club Members | 10 tokens/day | ## Fee Structure - Small fee on each trade, accumulated for token creator - Claimable anytime via "Claim fees for my token" - Legacy fees (older Clanker versions) claimed separately ## Common Issues | Issue | Resolution | |-------|------------| | Rate limit reached | Wait 24 hours or upgrade | | Name taken | Choose different name | | Symbol exists | Use unique symbol | | Image upload failed | Check format/size | ## Best Practices - Choose unique, memorable name and symbol - Add description and social links immediately - Upload quality logo - Claim fees regularly
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.