verifying-easyconfig-parameters

name	verifying-easyconfig-parameters
description	verify software and toolchain parameters extracted using "finding-easyconfig-parameters" skill.

Verifying EasyConfig parameters

IMPORTANT:

• Assumptions are FORBIDDEN.
• Interpret RULES line by line and in order. Each line is important.
• For extra information perform a web search.

Verification RULES (IN ORDER)

1. ACTION: MUST be equal to GENERATE or TEST or DEBUG.

2. SW_NAME: The value MUST EXACTLY match the name of an existing software, with correct capitalization (upper‑ and lower‑case letters).

   • Call mcp__web__agent to use web_search to verify its existence AND correctness. If it does NOT exist, return an error. If it is different, fix it.
   • It is possible that multiple softwares with the same name exists. Choose the correct one based on the reference easyconfig on next steps (using homepage or source_urls parameters).

3. Search for the easyconfigs of the requested software to find the template that is closest to the user's request (Use mcp__eb_tools__search_local_easyconfigs and mcp__eb_tools__search_upstream_easyconfigs tools with search_term = SW_NAME).

   • Easyconfigs follow a fixed strict naming scheme: <name>-<version>[-<toolchain>][<versionsuffix>].eb ([] means that part is optional).
     • <name> is the softwar name.
     • <version> is the software version.
     • [<toolchain>] is both toolchain name and version (either <toolchain_name>-<toolchian_version> or empty when TC_NAME is SYSTEM).
     • [<versionsuffix>] is versionsuffix (same as SW_SUFFIX) which is basically anything after <toolchain>(can be empty).
   • Find an easyconfig template to define these placeholders <name>, <version>, <toolchain>, and <versionsuffix>
   • If no easyconfig found for the verified software name, the cause MUST be either an incorrect software name or failure to follow the required naming schema.

4. TC_NAME:

   • If <toolchain> is empty:
     • You MUST set TC_NAME to SYSTEM and TC_VERSION to SYSTEM.
   • Otherwise:
     • If TC_NAME is included in <toolchain> of the template: Do nothing.
     • Otherwise: set TC_NAME to the <toolchain> name of the template.
   • You MUST OVERRIDE TC_NAME to the minimal required toolchain for the software and TC_VERSION to its corresponding version
     • Exception: Unless all easyconfigs for the same software are using larger toolchains. In this case, use the latest toolchain.
     • Call mcp__web__agent to use web_search to find the minimal required toolchain.

5. TC_VERSION:

   1. If TC_VERSION is SYSTEM: Do nothing.
   2. Based on ./TOOLCHAINS.md content, TC_VERSION MUST be a corresponding version of TC_NAME.

6. If TC_NAME can be replaced by a smaller valid component, set TC_NAME to the smaller component and use ./TOOLCHAINS.md to set TC_VERSION to its corresponding version.

7. SW_VERSION:

   • If <TC_VERSION> does NOT have the (latest) tag:
     • Call mcp__web__agent to use web_search to verify the version exists. If not tell user requested version does notr exists and STOP.
   • Otherwise, If <TC_VERSION> has the (latest) tag AND you found easyconfigs for the software where <toolchain> value of the easyconfig is EXACTLY <TC_NAME>-<TC_VERSION>:
     • Set SW_VERSION to the latest <version> in those existing easyconfigs.
   • Otherwise:
     • Do nothing

8. SW_SUFFIX:

   • If feature's version does NOT have the (latest) tag:
     • Do nothing
   • Otherwise, If feature's version has the (latest) tag AND you found easyconfigs for the SW_NAME where <toolchain> value of the easyconfig is EXACTLY <TC_NAME>-<TC_VERSION>:
     • set SW_SUFFIX to <versionsuffix>.
     • If multiple easyconfigs exist, use the one closest to the user request.
   • Otherwise:
     • Call mcp__web__agent to use web_search to check if SW_NAME requires features in SW_SUFFIX (SW_SUFFIX can be empty OR a list of features with their versions).
     • For each required feature, call mcp__web__agent to use web_search to find the latest version of the feature.