---

name: github-issue-metadata-triage description: "Find an existing GitHub issue and apply a reviewed metadata or status update."

GitHub Issue Metadata Triage

Find an existing GitHub issue and apply a reviewed metadata or status update.

Required Aident Actions

• <action-tag>composio:github_tools:github_search_issues</action-tag> (required inputs: q): Searches GitHub issues and pull requests using a flexible query with qualifiers, sorting, and pagination. Use this action when you need to find issues or pull requests across repositories using search criteria like...
• <action-tag>composio:github_tools:github_update_an_issue</action-tag> (required inputs: repo, owner, issue_number): Updates an existing GitHub issue's title, body, state, milestone, labels, or assignees; state_reason is only processed if state also changes, and use null or [] to clear applicable fields.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the rAction · Search Issueslable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constrAction · Update An Issuebelow to create a concrete plan. Resolve ambiguity before invoking an Action.
2. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
3. Inspect the current schema and prepare the minimum valid input for each selected Action.
4. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
5. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Use repository, state, and keyword qualifiers to identify one exact issue.
• Present the current and proposed fields before updating title, body, state, labels, milestone, or assignees.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.