Tipus
Comprovació i generació de tipus
graceful-shutdown
dadbodgeoff
Clean shutdown with in-flight job tracking, signal handlers, and buffer draining. Prevent data loss and corrupted state on process termination.
multi-tenancy
dadbodgeoff
Implement multi-tenant architecture with tenant isolation, data separation, and per-tenant configuration. Supports shared database and schema-per-tenant models.
background-jobs
dadbodgeoff
Implement robust background job processing with dead letter queues, retries, and state machines. Use when building async workflows, scheduled tasks, or any work that shouldn't block the request/response cycle.
dead-letter-queue
dadbodgeoff
Store failed jobs for replay or manual inspection. Track failure patterns, enable manual intervention, and prevent data loss from processing errors.
cloud-storage
dadbodgeoff
Cloud storage integration with signed URLs, visibility control, multi-tenant path conventions, and presigned uploads for direct client uploads.
geographic-clustering
dadbodgeoff
Grid-based geographic clustering with O(n) performance, medoid finding for map markers, and multi-factor risk scoring from event density, sentiment, and recency.
python-development
skillcreatorai
Modern Python development with Python 3.12+, Django, FastAPI, async patterns, and production best practices. Use for Python projects, APIs, data processing, or automation scripts.
agent
treasure-data
Build LLM agents using tdx agent pull/push with YAML/Markdown config. Covers agent.yml structure, tools (knowledge_base, agent, web_search, image_gen), @ref syntax, and knowledge bases. Use for TD AI agent development workflow.
data-dictionary
treasure-data
Automate update and maintenance of data dictionaries in Treasure Data - generates 80-90% of column descriptions automatically, allowing users to review results, make changes, and fill in gaps. Orchestrates schema extraction, AI-powered description generation, human review, and write-back as single workflow.
rt-personalization-validation
treasure-data
Validates RT Personalization Entity payloads before creation to prevent common API errors. MUST be invoked proactively during rt-setup-personalization workflow at Step 9c before making the entity creation API call. Also use when encountering "Attribute payload can't be blank" errors or when reviewing personalization entity JSON.
parent-segment
treasure-data
Manages CDP parent segments using tdx ps commands with YAML configs. Covers master tables, attributes, behaviors, tdx ps validate for join validation, tdx ps preview for data preview, and schedule configuration (daily/hourly/cron). Use when creating customer master tables, validating join match rates, or troubleshooting parent segment workflows.
journey
treasure-data
Creates CDP journey definitions in YAML using tdx journey commands. Covers journey stages, steps (wait, activation, decision_point, ab_test, merge, jump, end), entry/exit criteria, goals, embedded segments, and versioning. Use when building customer journey orchestration workflows or managing journey YAML files.
rt-config-attributes
treasure-data
Configure RT 2.0 attributes - single, list, counter, and batch attributes for real-time profile enrichment
segment
treasure-data
Manages CDP child segments using tdx sg commands with YAML rule configs. Covers filtering with operators (Equal, In, Greater, TimeWithinPast, Contain), folder organization, and activations for Salesforce/Google Ads exports. Use when creating audience segments, validating with tdx sg push --dry-run, or listing fields with tdx sg fields.
validate-segment
treasure-data
Validates CDP segment YAML configurations against the TD CDP API specification. Use when reviewing segment rules for correctness, checking operator types and values, or troubleshooting segment configuration errors before pushing to Treasure Data.
connector-config
treasure-data
Writes connector_config for segment/journey activations using tdx connection schema <type> to discover available fields. Use when configuring activations - always run schema command first to see connector-specific fields.
rt-config
treasure-data
Configure RT 2.0 (Real-Time Personalization) for parent segments including event tables, key events, RT attributes, and ID stitching using tdx ps rt commands or API
parent-segment-analysis
treasure-data
Query and analyze CDP parent segment database data. Use tdx ps desc -o to get output database schema, then query customers and behavior tables. Use when exploring parent segment data, building reports, or analyzing customer attributes and behaviors.
validate-journey
treasure-data
Validates CDP journey YAML configurations against tdx schema requirements. Use when reviewing journey structure, checking step types and parameters, verifying segment references, or troubleshooting journey configuration errors before pushing to Treasure Data.
web-design-guidelines
skillcreatorai
Modern web design principles for responsive layouts, accessibility, and visual hierarchy.
dbt
treasure-data
dbt with TD Trino. Covers profiles.yml setup (method:none, user:TD_API_KEY), required override macros (no CREATE VIEW), TD_INTERVAL in models, and TD Workflow deployment.
rt-setup-personalization
treasure-data
Complete workflow to set up RT 2.0 personalization from scratch - validates parent segment RT status, discovers event tables and attributes, configures RT infrastructure (events, attributes, ID stitching), creates personalization service, and deploys the personalization entity with payload. Use when user wants to "create realtime setup and build personalization" or "set up RT personalization end-to-end". Includes automatic validation using rt-personalization-validation skill to prevent common API errors.
rt-journey-create
treasure-data
Create RT 2.0 Journeys (event-triggered) that activate when specific events occur, sending real-time data to external systems
code-documentation
skillcreatorai
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.