create-technical-terms

Generate missing technical terms for tables and columns in Stratio Governance domains.

4|10|Updated Feb 20, 2026

Search Tags:#automation #governance #generate #technical-terms #semantic-layer #domain-documentation

Ready to run

npx skills add https://github.com/Stratio/genai-agents --skill create-technical-terms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-technical-terms
Source: https://github.com/Stratio/genai-agents/tree/main/shared-skills/create-technical-terms
Command: npx skills add https://github.com/Stratio/genai-agents --skill create-technical-terms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or regenerate technical descriptions (tables and columns) for a technical domain in Stratio Governance. Phase 1 of the semantic-layer pipeline.

Core Features & Use Cases

Resolves the technical domain (search/list) and reports current state: total tables, tables with descriptions, and pending tables.
Seeds the collection description automatically when missing and supports scope options: all, specific, regenerate all, and regenerate specific.
Builds user_instructions through the Glossary Instruction Enrichment Workflow and executes create_technical_terms, with safeguards like idempotent behavior unless regeneration is requested.

Quick Start

Specify a technical domain to generate or regenerate all technical terms for that domain.

Frequently Asked Questions about create-technical-terms

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

FAQPage Schema

How do I generate missing technical terms for tables and columns in a data governance domain?▼

Generate missing technical terms by specifying a technical domain to resolve tables and columns, automatically seeding collection descriptions, enriching glossary instructions, and executing term creation within Stratio Governance.

What is the best way to document undocumented domain tables and columns in governance?▼

Document undocumented domain tables and columns by running a semantic-layer pipeline phase that discovers the technical domain, inspects the current state of pending tables, and creates technical terms through an enriched glossary instruction workflow.

How does domain state inspection work before generating technical descriptions?▼

Domain state inspection resolves the technical domain via search or list, then reports total tables, tables with existing descriptions, and pending tables needing technical term generation before execution begins.

Can I regenerate existing technical terms for specific tables in a governance domain?▼

Regenerate existing technical terms for specific tables or entire domains using scope selection options, which enforce explicit confirmation before executing destructive regeneration to overwrite current descriptions via the MCP tool.

Does the technical term generation process support idempotent behavior for existing descriptions?▼

Technical term generation supports idempotent behavior by default, preserving existing descriptions unless explicit regeneration is requested, preventing unintended overwrites of domain table and column documentation.

What glossary instruction enrichment is needed before creating technical terms?▼

Glossary instruction enrichment builds enriched user_instructions through a dedicated workflow before invoking the create_technical_terms MCP tool, ensuring generated domain documentation matches the required semantic-layer scope and quality.