drupal-content-modeller--create-ticket

Fill empty Drupal content-model ticket cells with default field types, widgets, and permissions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/richardgaunt/drupal-content-modeller --skill drupal-content-modeller-create-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drupal-content-modeller--create-ticket
Source: https://github.com/richardgaunt/drupal-content-modeller/tree/main/.claude/skills/drupal-content-modeller--create-ticket
Command: npx skills add https://github.com/richardgaunt/drupal-content-modeller --skill drupal-content-modeller-create-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Partially-filled Drupal-ticket templates can stall handoffs between discovery and build. This skill fills in missing field types, machine names, widgets, cardinality, and permissions using sensible Drupal defaults without overwriting user-provided values.

Core Features & Use Cases

  • Applies Drupal-default field types, widget mappings, and permission presets to blank cells in a ticket.
  • Preserves user-filled cells and leaves placeholders intact for review.
  • Supports entity types: node, paragraph, media, taxonomy_term, block_content, and their common fields.

Quick Start

Provide a partially-filled ticket Markdown file and let the skill populate the remaining blanks with safe defaults.

Frequently Asked Questions about drupal-content-modeller--create-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-fill missing fields in a Drupal content model ticket template?

You can auto-fill missing fields in a Drupal content model ticket by applying a skill that injects sensible defaults for machine names, field types, and widgets without overwriting your existing data. It targets partially-filled Markdown ticket templates generated during discovery workflows.

What sensible defaults are applied to Drupal ticket fields during auto-completion?

Drupal ticket auto-completion applies defaults using a defined mapping that includes field_n_ prefixes for machine names, string or text field types, standard Drupal widgets, and preset permission rows for blank cells in your ticket template.

Does the Drupal ticket auto-completion overwrite existing field values I have already provided?

No, Drupal ticket auto-completion preserves user-filled cells and only populates empty cells with default values. It leaves existing data and placeholders intact so you can review the applied defaults before proceeding to the build phase.

Can I use this ticket auto-completion for Drupal paragraph and media bundles?

Yes, ticket auto-completion supports common Drupal entity types including node, paragraph, media, taxonomy_term, and block_content bundles. It fills in missing cardinalities, field types, and widget mappings for these specific bundle templates.

What is the best way to populate blank cardinality and permission rows in a Drupal content ticket?

The best way to populate blank cardinality and permission rows is to use a ticket auto-completion process that derives safe Drupal defaults for empty cells. This ensures your content model ticket has complete permission and cardinality definitions before handoff.