Meta-tool for rapid adb-* skill creation from templates
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill adb-skill-generator80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.88xAgent success when using this skill
Validation for skill structure
Rapid adb- skill creation from production-tested templates*
What It Does: Automates creation of new adb-* skills by generating skill directory structure, SKILL.md metadata, script templates, and example workflows. Speeds up new skill development from hours to minutes.
Core Capabilities:
When to Use:
Generate new adb-* skill from templates.
# Minimal skill (1 launcher script)
uv run .claude/skills/adb-skill-generator/adb-skill-generator.py \
--skill-name banking \
--description "Banking app automation via Play Integrity bypass"
# Full skill (3 scripts + workflow)
uv run .claude/skills/adb-skill-generator/adb-skill-generator.py \
--skill-name fitness \
--description "Fitness app testing" \
--script-count 3 \
--with-workflow
# With category specification
uv run .claude/skills/adb-skill-generator/adb-skill-generator.py \
--skill-name streaming \
--description "Streaming app automation" \
--category adb-app-automation
# List available templates
uv run .claude/skills/adb-skill-generator/adb-skill-generator.py \
--list-templates
# JSON output
uv run .claude/skills/adb-skill-generator/adb-skill-generator.py \
--skill-name myapp \
--description "My app automation" \
--jsonParameters:
--skill-name (required): Name of skill (with or without adb- prefix)--description (required): Brief description of skill purpose--script-count (optional, default: 1): Number of scripts (1-4)--with-workflow (optional): Generate example TOON workflow--category (optional): Skill category (default: adb-app-automation)--list-templates: Show available templates--json: JSON output instead of human-readable--verbose: Detailed operation loggingExit Codes:
0: Success (skill created)1: Warning (partial creation)2: Error (skill creation failed)3: Critical (invalid parameters)Generated Structure:
.claude/skills/adb-{skillname}/
├── SKILL.md # Metadata + documentation
├── scripts/
│ ├── adb-{skillname}-launch.py # Launcher script
│ ├── adb-{skillname}-check.py # Checker script (if count >= 2)
│ ├── adb-{skillname}-test.py # Tester script (if count >= 3)
│ └── adb-{skillname}-validate.py # Validator script (if count >= 4)
├── workflows/
│ ├── {skillname}-basic.toon # Basic workflow example
│ └── {skillname}-advanced.toon # Advanced workflow example (if requested)
├── templates/ # (Empty - for user templates)
└── analysis/ # (Empty - for analysis results)uv run adb-skill-generator.py \
--skill-name twitter \
--description "Twitter app automation for testing"Creates:
adb-twitter/SKILL.mdadb-twitter/scripts/adb-twitter-launch.py (launcher)adb-twitter/workflows/twitter-basic.toon (basic example)uv run adb-skill-generator.py \
--skill-name instagram \
--description "Instagram app automation and testing" \
--script-count 3 \
--with-workflowCreates:
adb-instagram/SKILL.mdadb-instagram/scripts/adb-instagram-launch.py (launcher)adb-instagram/scripts/adb-instagram-check.py (checker)adb-instagram/scripts/adb-instagram-test.py (tester)adb-instagram/workflows/instagram-basic.toonadb-instagram/workflows/instagram-advanced.toonuv run adb-skill-generator.py \
--skill-name facebook \
--description "Facebook app automation" \
--jsonOutput:
{
"skill_name": "adb-facebook",
"success": true,
"skill_path": "/path/to/.claude/skills/adb-facebook",
"scripts_created": 1,
"skill_md_created": true,
"workflow_created": false,
"duration": 0.45,
"messages": [
"✅ Created skill directory: ...",
"✅ Created scripts/ subdirectory",
"✅ Created SKILL.md ...",
"✅ Created script: adb-facebook-launch.py"
],
"exit_code": 0
}All generated scripts follow the proven 9-section IndieDevDan template:
1. Docstring - Comprehensive description with examples
2. Imports - Required libraries
3. Constants - Configuration values
4. Project root - Auto-detection logic
5. Data models - Result dataclasses
6. Helpers - Utility functions (device selection, etc.)
7. Core logic - Primary automation implementation
8. Formatters - Human + JSON output formatting
9. CLI interface - Click command-line interface
10. Entry point - Main execution guardBenefits:
Generated workflows follow TOON format:
name: {skillname}-basic
description: Basic automation for {skillname}
parameters:
device: "127.0.0.1:5555"
timeout: 30
phases:
- id: phase-1
name: "Launch app"
steps:
- id: launch
action: {skillname}-launch
params:
device: "{{ device }}"
recovery:
- on_error: launch
action: retry
then: continueFeatures:
uv run adb-skill-generator.py \
--skill-name myapp \
--description "My app automation"Edit generated scripts to add actual automation logic:
scripts/adb-myapp-launch.py - App launch logicscripts/adb-myapp-check.py - State checking logicscripts/adb-myapp-test.py - Functional testingBuild TOON workflows using generated scripts:
uv run adb-run-workflow.py \
--workflow .claude/skills/adb-myapp/workflows/myapp-advanced.toon \
--verboseGenerated skill is immediately usable by others:
uv run .claude/skills/adb-myapp/scripts/adb-myapp-launch.py --device 127.0.0.1:5555The generator embodies ADB ecosystem design principles:
1. Convention over Configuration
2. Rapid Development
3. Quality by Default
4. Extensibility
This generator uses and integrates with:
All generated skills can depend on these foundation skills automatically.
# In generated script, change:
APP_PACKAGE = "kr.co.flo.karrot" # Replace with your app package# In launcher script, change:
result = launch_app_with_verification(
device_id,
wait_text="Custom Login Screen" # Your app's specific screen
)# In any script, change:
VERIFICATION_TIMEOUT = 45 # Slower apps need more timeQ: Script generation failed
# Ensure valid skill name (alphanumeric + hyphens)
uv run adb-skill-generator.py --skill-name valid-name --description "..."Q: How to see what will be generated?
# Use --verbose flag
uv run adb-skill-generator.py \
--skill-name myapp \
--description "..." \
--verboseQ: Can I use generated scripts immediately?
# Yes, scripts are immediately usable but may need customization
uv run .claude/skills/adb-myapp/scripts/adb-myapp-launch.py --device 127.0.0.1:5555This skill includes TOON-based workflow definitions for automation.
TOON (Task-Oriented Orchestration Notation) is a structured workflow definition language that pairs with Markdown documentation. Each workflow consists of:
This TOON+MD pairing approach is inspired by the BMAD METHOD pattern, adapted to use TOON instead of YAML for better orchestration support.
Workflow files are located in workflow/ directory:
Example Workflows (adb-skill-generator):
workflow/skill-generation.toon - Complete skill generation workflowworkflow/template-validation.toon - Validate and test generated skill templatesExecute any workflow using the ADB workflow orchestrator:
uv run .claude/skills/adb-workflow-orchestrator/scripts/adb-run-workflow.py \
--workflow .claude/skills/adb-skill-generator/workflow/skill-generation.toon \
--param skill_name="myapp"Each workflow includes comprehensive documentation in the corresponding .md file:
See the workflow/ directory for complete TOON file definitions and documentation.
To create custom workflows for this skill:
.toon file in the workflow/ directory.md file with comprehensive documentationFor more information, refer to the TOON specification and the workflow orchestrator documentation.
Version: 1.0.0 (Production Ready) Last Updated: 2025-12-02 Category: Meta-Automation (Tier 3)
2bbaa03
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.