Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

assess-completeness

Estrelas0

Forks6

Atualizado1 de julho de 2026 às 19:47

Check if an issue has all required information for action

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

fullsend-ai

fullsend-ai/experiments

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	assess-completeness
description	Check if an issue has all required information for action
allowed-tools	Bash(curl *), WebFetch

Read the issue via the GitHub REST server:

curl -s http://host.docker.internal:8081/repos/$OWNER/$REPO_NAME/issues/$ISSUE_NUMBER

Evaluate whether the issue contains sufficient information.

For bugs: steps to reproduce, expected vs actual behavior, environment info.
For features: use case description, acceptance criteria.
For questions: enough context to provide a useful answer.
If the issue references external links (logs, pastebins, docs), fetch them to verify the information is actually there.

Respond ONLY with a JSON object:

{
  "issue_type": "bug" | "enhancement" | "question" | "other",
  "complete": true | false,
  "missing": ["<missing item 1>", "<missing item 2>"],
  "external_context": "<summary of relevant information gathered from external links, or null if none>"
}

Mais deste repositório

mesmo repositório

detect-duplicates

fullsend-ai/experiments

Search for and identify duplicate issues in a repository

2026-07-010

triage-coordination

fullsend-ai/experiments

Coordinate triage of a GitHub issue by orchestrating sandboxed analysis subagents and applying labels

2026-07-010

verify-reproducibility

fullsend-ai/experiments

Verify whether a reported bug is reproducible by inspecting the codebase

2026-07-010

code-implementation

fullsend-ai/experiments

Step-by-step procedure for implementing a GitHub issue. Gathers context, discovers repo conventions, plans the change, implements, verifies with tests and linters, and commits to a feature branch.

2026-07-010

baked-instructions-builder

fullsend-ai/experiments

Hardcoded endpoint documentation for the container builder API.

2026-07-010

baked-instructions-provisioner

fullsend-ai/experiments

Hardcoded endpoint documentation for the repo provisioner API.

2026-07-010

name	assess-completeness
description	Check if an issue has all required information for action
allowed-tools	Bash(curl *), WebFetch

Read the issue via the GitHub REST server:

curl -s http://host.docker.internal:8081/repos/$OWNER/$REPO_NAME/issues/$ISSUE_NUMBER

Evaluate whether the issue contains sufficient information.

For bugs: steps to reproduce, expected vs actual behavior, environment info.
For features: use case description, acceptance criteria.
For questions: enough context to provide a useful answer.
If the issue references external links (logs, pastebins, docs), fetch them to verify the information is actually there.

Respond ONLY with a JSON object:

{
  "issue_type": "bug" | "enhancement" | "question" | "other",
  "complete": true | false,
  "missing": ["<missing item 1>", "<missing item 2>"],
  "external_context": "<summary of relevant information gathered from external links, or null if none>"
}