Communitygithub.com

Jamie-BitFlight/enterprise-installanywhere

InstallAnywhere .iap_xml インストーラ定義ファイルに対する Dasel v3 クエリパターン集。アクションシーケンスの調査、変数の発見、プラットフォーム条件の解決、パネルナビゲーション、インストーラバリアントの比較に使用します。ファイルサイズは 2.5MB 以上、65,000 行以上でコンテキスト読み込みには大きすぎるため、構造的な Dasel クエリが必要です。

enterprise-installanywhere とは？

このスキルは、Flexera InstallAnywhere が生成する大規模な .iap_xml インストーラ定義ファイルを効率的に解析・比較するための Dasel v3 クエリパターンを提供します。ファイルは 2.5～2.6 MB、65,000 行を超えるため、直接コンテキストに読み込むことは不可能であり、構造的な Dasel クエリが必須です。アクションシーケンスの抽出、変数定義の一覧表示、プラットフォーム条件（Windows/Linux）の検出、ファイルコピー操作の調査、パネルナビゲーションの確認、さらに RA ビルドと NON_RA ビルドの比較など、クロスバリアント差分分析をサポートします。XML 属性にはダッシュ接頭辞を用い、再帰的降下 (..) や search() 述語関数を活用することで、任意の深さのノードにアクセスできます。結果は常に /tmp/ に書き出し、ソースツリーを変更しません。

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/enterprise-installanywhere
オリジナルを見る→すべてのスキルを見る

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

ドキュメント

InstallAnywhere .iap_xml クエリパターン

<when_to_use>

このスキルは、.iap_xml ファイルを扱う際にロードしてください — インストールアクションの監査、ファイルコピー操作の一覧表示、変数の発見、プラットフォーム固有の分岐の検索、または 2 つのインストーラバリアント（例: RA ビルドと NON_RA ビルド）の比較を行います。

</when_to_use>

運用上の制約

  • 常に -i xml を明示的に指定 — .iap_xml 拡張子では自動検出が失敗します
  • すべての中間結果は /tmp/ に書き込む — ソースツリーには決して書き込まないでください
  • ファイルサイズは 2.5～2.6 MB、65,000 行以上 — 構造的な Dasel クエリを使用し、ファイルをコンテキストに読み込まないでください

ルート構造

InstallAnywhere .iap_xml ファイルのルートパスは固定で InstallAnywhere.project です。

# ドキュメントルート直下のトップレベル要素名
cat installer.iap_xml | dasel -i xml 'keys($this)'

# インストールアクションシーケンスに移動
cat installer.iap_xml | dasel -i xml 'InstallAnywhere.project.installSequence'

# プロジェクトノードの子要素
cat installer.iap_xml | dasel -i xml 'InstallAnywhere.project.keys($this)'

再帰的降下 — 完全なパスを知らなくても任意の深さの要素を見つけます:

# 任意の深さの "action" という名前の全要素
cat installer.iap_xml | dasel -i xml '..action'

# 任意の深さの "panel" という名前の全要素
cat installer.iap_xml | dasel -i xml '..panel'

# 特定の属性を持つ任意の深さのノード
cat installer.iap_xml | dasel -i xml 'search(has("-name"))'

..elementName は再帰的に降下します。search(predicate) は任意の深さのノードにマッチします。

アクションシーケンス解析

# 実行順の全アクション名
cat installer.iap_xml | dasel -i xml '..action.map("-name")'

# 全アクションタイプ
cat installer.iap_xml | dasel -i xml '..action.map("-type")'

# action 要素の総数
cat installer.iap_xml | dasel -i xml 'len(..action)'

# 分析用に書き出し
cat installer.iap_xml | dasel -i xml '..action.map("-name")' > /tmp/action_names.txt
cat installer.iap_xml | dasel -i xml '..action.map("-type")' > /tmp/action_types.txt

変数発見

# 全ての変数定義
cat installer.iap_xml | dasel -i xml '..variable.map("-name")' > /tmp/installer_vars.txt

プラットフォーム条件

# 全てのプラットフォーム条件（Windows と Linux の分岐）
cat installer.iap_xml | dasel -i xml 'search(has("-platform")).map("-platform")' > /tmp/platforms.txt

クロスバリアント比較

同じインストーラの 2 つのビルド（例: RA vs NON_RA、Windows バリアント vs Linux バリアント）を比較する場合:

# 2 つのインストーラファイル間でアクションセットを比較
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

# パネルセットを比較
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

ファイルコピー操作

# 全てのファイルコピー元
cat installer.iap_xml | dasel -i xml '..installFile.map("-source")' > /tmp/file_copies.txt

パネルナビゲーション

# パネル名と数
cat installer.iap_xml | dasel -i xml '..panel.map("-name")'
cat installer.iap_xml | dasel -i xml 'len(..panel)'

属性構文リファレンス

Dasel のフレンドリーモードでは、XML 属性に - 接頭辞を使用します:

# 最初のマッチの特定の属性にアクセス
cat installer.iap_xml | dasel -i xml '..action[0].-name'

# ノードの属性と子要素を確認
cat installer.iap_xml | dasel -i xml '..action[0].keys($this)'

# マッチする全ノードから属性値を抽出
cat installer.iap_xml | dasel -i xml '..elementName.map("-attributeName")'

# マッチする要素の数をカウント
cat installer.iap_xml | dasel -i xml 'len(..elementName)'

# 任意の深さで属性述語を用いて検索
cat installer.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).

関連スキル

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community