How do I install the Input skill?

Run npx skillmds@latest add gabrielmoreira/input in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Input safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Input?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Input free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Input by gabrielmoreira — Agent Skill

Name: Input
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

Input Resolution — Instructions

Scope: Resolve the required CodeQL alert metadata before remediation begins

Objective

Extract the following values from the user input whenever they are available:

OrganizationName
ProjectName
RepositoryName
AlertFilePath
QueryId
LineNumber
JobId
AlertId
AlertUrl

Some values may be missing. Use cluster('1es').database('Liquid').CodeQL_Issues_Extended() to look up missing metadata. Always resolve OrganizationName, ProjectName, and RepositoryName before proceeding. Make sure matching is case-insensitive.
Always set IsDefaultBranch to true and State to Active.
AlertId and AlertUrls are always unique.
JobId (aka CodeQLJobId) is not unique. One CodeQL job can contain multiple alerts or AlertIds.
Narrowing down search results. Start with orgName, projectName, repoName, then use alertFilePath, queryId, and lineNumber to further narrow down results.
Still, if you fail to get a unique match(es), report failure and exit.

Relevant Lookup Schema

Use CodeQL_Issues_Extended() with at least the following fields:

Column Name	Type	Description
Id	guid	AlertId. Unique identifier for the issue.
JobId	guid	CodeQLJobId. Unique identifier for the CodeQL analysis job that generated the alert. One CodeQL job can contain multiple alerts or `AlertId` values.
QueryId	string	CodeQL query identifier such as `cs/sql-injection`.
QueryName	string	Human-readable query name such as `KQL query built from user-controlled sources`.
RepoId	string	Repository identifier in the format `OrganizationName/ProjectName/RepositoryName`.
RepositoryUrl	string	URL of the repository where the issue is found.
AlertFilePath	string	File path relative to the repository root where the issue is found.
RevisionId	string	Git revision SHA of the analyzed commit.

Completion Checks

After resolving missing values, confirm that you have:

The CodeQL Job ID. If you cannot locate the alert later, assume the Job ID may be wrong and re-check it.
The alert information, or the full list of alerts to remediate.

---name: inputdescription: Extract and resolve required CodeQL alert metadata from user input before remediation--- # Input Resolution — Instructions > Scope: Resolve the required CodeQL alert metadata before remediation begins --- ## Objective Extract the following values from the user input whenever they are available: - OrganizationName - ProjectName - RepositoryName - AlertFilePath - QueryId - LineNumber - JobId - AlertId - AlertUrl 1. Some values may be missing. Use `cluster('1es').database('Liquid').CodeQL_Issues_Extended()` to look up missing metadata. Always resolve `OrganizationName`, `ProjectName`, and `RepositoryName` before proceeding. Make sure matching is case-insensitive. 2. Always set `IsDefaultBranch` to true and `State` to Active. 3. AlertId and AlertUrls are always unique. 4. JobId (aka CodeQLJobId) is not unique. One CodeQL job can contain multiple alerts or AlertIds. 5. Narrowing down search results. Start with orgName, projectName, repoName, then use alertFilePath, queryId, and lineNumber to further narrow down results. 6. Still, if you fail to get a unique match(es), report failure and exit. ## Relevant Lookup Schema Use `CodeQL_Issues_Extended()` with at least the following fields: | Column Name | Type | Description | |---|---|---| | Id | guid | AlertId. Unique identifier for the issue. | | JobId | guid | CodeQLJobId. Unique identifier for the CodeQL analysis job that generated the alert. One CodeQL job can contain multiple alerts or `AlertId` values. | | QueryId | string | CodeQL query identifier such as `cs/sql-injection`. | | QueryName | string | Human-readable query name such as `KQL query built from user-controlled sources`. | | RepoId | string | Repository identifier in the format `OrganizationName/ProjectName/RepositoryName`. | | RepositoryUrl | string | URL of the repository where the issue is found. | | AlertFilePath | string | File path relative to the repository root where the issue is found. | | RevisionId | string | Git revision SHA of the analyzed commit. | --- ## Completion Checks After resolving missing values, confirm that you have: 1. The CodeQL Job ID. If you cannot locate the alert later, assume the Job ID may be wrong and re-check it. 2. The alert information, or the full list of alerts to remediate.

Frequently asked questions

Input