Communitygithub.com

Patrones de consulta Dasel para InstallAnywhere .iap_xml

Patrones de consulta Dasel v3 para definiciones de instaladores InstallAnywhere en formato .iap_xml, útiles para auditar secuencias de acciones, descubrir variables, resolver condiciones de plataforma, navegar paneles o comparar variantes del instalador.

¿Qué es Patrones de consulta Dasel para InstallAnywhere .iap_xml?

Esta habilidad proporciona un repertorio completo de patrones de consulta con Dasel v3 para analizar archivos .iap_xml generados por InstallAnywhere. Dado que estos archivos suelen superar los 2.5 MB y las 65.000 líneas, es inviable leerlos directamente en el contexto de un agente de IA; en su lugar, se emplean consultas estructurales con Dasel. La habilidad cubre la navegación por la estructura raíz (Insta​llAnywhere.project), el análisis de secuencias de acciones, el descubrimiento de variables, la identificación de condiciones específicas de plataforma (Windows vs. Linux), la comparación entre variantes del mismo instalador (p. ej., RA vs. NON_RA), la extracción de operaciones de copia de archivos y la navegación por paneles. También incluye una referencia de sintaxis para atributos XML en Dasel. Es aplicable a cualquier agente que trabaje con archivos .iap_xml y necesite extraer información de forma eficiente y reproducible, siempre escribiendo los resultados intermedios en /tmp/ y usando explícitamente el flag -i xml.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/enterprise-installanywhere

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Patrones de consulta para archivos .iap_xml de InstallAnywhere

<when_to_use>

Cargue esta habilidad cuando trabaje con cualquier archivo .iap_xml — para auditar acciones de instalación, listar operaciones de copia de archivos, descubrir variables, encontrar ramas específicas de una plataforma o comparar dos variantes del instalador (p. ej., compilaciones RA vs. NON_RA).

</when_to_use>

Restricciones operativas

  • Siempre pase -i xml explícitamente — la detección automática falla con la extensión .iap_xml
  • Escriba todos los resultados intermedios en /tmp/ — nunca en el árbol fuente
  • Los archivos ocupan 2.5–2.6 MB, 65 000+ líneas — use consultas estructurales con dasel, nunca lea el archivo completo en el contexto

Estructura raíz

Los archivos .iap_xml de InstallAnywhere tienen una ruta raíz fija: InstallAnywhere.project.

# Nombres de elementos de primer nivel en la raíz del documento
cat install.iap_xml | dasel -i xml 'keys($this)'

# Navegar a la secuencia de acciones de instalación
cat install.iap_xml | dasel -i xml 'InstallAnywhere.project.installSequence'

# Hijos del nodo project
cat install.iap_xml | dasel -i xml 'InstallAnywhere.project.keys($this)'

Descenso recursivo — encuentra elementos a cualquier profundidad sin necesidad de conocer la ruta completa:

# Todos los elementos llamados "action" a cualquier profundidad
cat install.iap_xml | dasel -i xml '..action'

# Todos los elementos llamados "panel" a cualquier profundidad
cat install.iap_xml | dasel -i xml '..panel'

# Cualquier nodo a cualquier profundidad donde exista un atributo específico
cat install.iap_xml | dasel -i xml 'search(has("-name"))'

..elementName desciende recursivamente. search(predicate) coincide con nodos a cualquier profundidad.

Análisis de la secuencia de acciones

# Todos los nombres de acciones en orden de ejecución
cat install.iap_xml | dasel -i xml '..action.map("-name")'

# Todos los tipos de acciones
cat install.iap_xml | dasel -i xml '..action.map("-type")'

# Contar todos los elementos action
cat install.iap_xml | dasel -i xml 'len(..action)'

# Escribir para análisis
cat install.iap_xml | dasel -i xml '..action.map("-name")' > /tmp/action_names.txt
cat install.iap_xml | dasel -i xml '..action.map("-type")' > /tmp/action_types.txt

Descubrimiento de variables

# Todas las definiciones de variables
cat install.iap_xml | dasel -i xml '..variable.map("-name")' > /tmp/installer_vars.txt

Condiciones de plataforma

# Todas las condiciones de plataforma (ramas Windows vs. Linux)
cat install.iap_xml | dasel -i xml 'search(has("-platform")).map("-platform")' > /tmp/platforms.txt

Comparación entre variantes

Al comparar dos compilaciones del mismo instalador (p. ej., RA vs. NON_RA, variante Windows vs. Linux):

# Comparar conjuntos de acciones entre dos archivos de instalador
cat installer_a.iap_xml | dasel -i xml '..action.map("-name")' | sort > /tmp/actions_a.txt
cat installer_b.iap_xml | dasel -i xml '..action.map("-name")' | sort > /tmp/actions_b.txt
diff /tmp/actions_a.txt /tmp/actions_b.txt > /tmp/installer_diff.txt

# Comparar conjuntos de paneles
cat installer_a.iap_xml | dasel -i xml '..panel.map("-name")' | sort > /tmp/panels_a.txt
cat installer_b.iap_xml | dasel -i xml '..panel.map("-name")' | sort > /tmp/panels_b.txt
diff /tmp/panels_a.txt /tmp/panels_b.txt

Operaciones de copia de archivos

# Todos los orígenes de copia de archivos
cat install.iap_xml | dasel -i xml '..installFile.map("-source")' > /tmp/file_copies.txt

Navegación por paneles

# Nombres de paneles y su cantidad
cat install.iap_xml | dasel -i xml '..panel.map("-name")'
cat install.iap_xml | dasel -i xml 'len(..panel)'

Referencia de sintaxis de atributos

Los atributos XML usan el prefijo - en el modo friendly de dasel:

# Acceder a un atributo específico en la primera coincidencia
cat install.iap_xml | dasel -i xml '..action[0].-name'

# Descubrir atributos e hijos de un nodo
cat install.iap_xml | dasel -i xml '..action[0].keys($this)'

# Extraer valores de atributos en todos los nodos coincidentes
cat install.iap_xml | dasel -i xml '..elementName.map("-attributeName")'

# Contar elementos coincidentes
cat install.iap_xml | dasel -i xml 'len(..elementName)'

# Buscar con predicado de atributo a cualquier profundidad
cat install.iap_xml | dasel -i xml 'search(has("-attributeName"))'

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/dasel-reference

Use when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/data-transformation

Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-maven-pom

Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.

Jamie-BitFlight/enterprise-spring-xml

Dasel v3 selectors for Spring bean factory XML — use when querying any Spring ApplicationContext XML for bean discovery, dependency wiring, JMS destination mapping, property injection extraction, or cross-bean reference tracing. Load this skill before writing dasel selectors against Spring bean XML files (applicationContext.xml, *_beans.xml, spring-*.xml).

Skills relacionados