Review PR
PrefectHQ/fastmcp
Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict.
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
Install File A Task
$ npx skills add no-human-ai/no_human --skill file-a-task -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install no-human-ai/no_human file-a-task --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .claude/skills/file-a-task && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .claude/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-taskType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add no-human-ai/no_human --skill file-a-task -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install no-human-ai/no_human file-a-task --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .agents/skills/file-a-task && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .agents/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add no-human-ai/no_human --skill file-a-task -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install no-human-ai/no_human file-a-task --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .cursor/skills/file-a-task && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .cursor/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/no-human-ai/no_human.git --path plugins/no-human/skills/file-a-task--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add no-human-ai/no_human --skill file-a-task -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install no-human-ai/no_human file-a-task --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .gemini/skills/file-a-task && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .gemini/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install no-human-ai/no_human file-a-taskInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add no-human-ai/no_human --skill file-a-task -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .github/skills/file-a-task && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .github/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add no-human-ai/no_human --skill file-a-task -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install no-human-ai/no_human file-a-task --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/no-human-ai/no_human.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/no-human/skills/file-a-task .opencode/skills/file-a-task && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "file-a-task" agent skill from https://github.com/no-human-ai/no_human/tree/main/plugins/no-human/skills/file-a-task into .opencode/skills/file-a-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-a-task", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
file-a-task- GitHub stars
- 324
- Token cost
- ~1k tokens
- SKILL.md length
- 578 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
- Tasks that involve Pull requests
- SKILL.md covers When to use, Prerequisite: the local server…, Tool: task_add and Tool: task_status, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
File A Task is an agent skill from no-human-ai/no_human. File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. It works with Model Context Protocol. The repository describes itself as: From ticket to reviewed pull request. Free and open-source, on your machine. The licence is MIT.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/file-a-task”
What it can do on your machine
Read from SKILL.md and the folder at commit cdcbd0a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
File A Task loads about 1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 578 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from no-human-ai/no_human at commit cdcbd0a, republished under its MIT licence (© no-human-ai). 578 words, ~1,042 tokens.
Download SKILL.mdSave it as
.claude/skills/file-a-task/SKILL.md (or your agent's skills folder).- name
- file-a-task
- description
- File work into no_human (task_add) and check on it (task_status) via the no_human MCP bridge, instead of doing the work inline.
File a task into no_human
Use the two MCP tools this plugin exposes — task_add and task_status — to
hand off work that should become a reviewed pull request, instead of making
the change yourself in this conversation.
When to use
- The work is substantial enough to deserve its own branch, its own tests, and independent review — not a one-line edit you can just make inline.
- You want no_human to plan, code, test, have the result reviewed by a second model, and open a pull request, while you keep doing something else.
- Do not use this for small edits you can make directly in the current conversation — that is strictly slower and adds no value.
Prerequisite: the local server must already be running
Both tools call the existing no_human HTTP API at http://127.0.0.1:8420.
The bridge does not retry or fall back if that address is unreachable —
it refuses to start at all (SystemExit, no auto-retry). Before using either
tool, make sure the server is running:
nh start(The desktop app starts this for you automatically.) If a tool call fails with a connection error, the fix is to start the server, not to retry the call.
Tool: task_add
Creates a new no_human task via POST /api/tasks.
Parameters (all required strings):
| Name | Type | Description |
|---|---|---|
title | string | Short task title. |
description | string | Full task description — inline the concrete context here (exact file paths, exact acceptance criteria), rather than referencing this conversation, since no_human cannot see it. |
repo_path | string | Absolute path to the target repo checkout the task should run against. |
You do not pass source — the bridge sets it to "mcp" on every call it
makes, server-side, before the request is sent.
Returns: compact JSON with the new task's id and the source the server
actually stored (first-class alongside "board"/"jira"), e.g.:
{"task_id":"task-abc123","source":"mcp"}Show full SKILL.md (283 more words)Show less
Tool: task_status
Fetches a task's current full state via GET /api/tasks/{id}.
Parameters (required string):
| Name | Type | Description |
|---|---|---|
task_id_or_external_id | string | Either the task's own id (or a unique prefix of it) or its external id. |
Resolution order: first tries the value as a task id (or id prefix); if that
404s, falls back to a client-side scan of GET /api/tasks for a matching
external_id, then re-fetches by the real id. If nothing matches either way,
the call raises — a nonexistent id is an error, not an empty result.
Returns: the complete task object as compact JSON, including at least
id, external_id, source, title, description, status,
created_at, updated_at, e.g.:
{"id":"task-abc123","external_id":null,"source":"mcp","title":"Fix thing","description":"...","status":"in_progress","created_at":"2026-08-20T12:00:00Z","updated_at":"2026-08-20T12:05:00Z"}task_status is read-only polling — call it again later to check progress;
it never changes the task.
Writing a good ticket
Inline everything the coding agent will need directly into description:
exact file paths, exact acceptance criteria, any commands to run. Do not
reference "the conversation above" or anything in your own context — the
task runs in its own fresh session and cannot see it.
Product boundary — no_human opens a PR and stops
no_human plans, codes, tests, has the work reviewed by a second model,
opens the pull request, and stops there. Merge is always the human's
action — this skill must never instruct or attempt a merge, an approval, or
a push to a protected branch. There is no tool exposed here that can merge
or approve anything, and none should be sought or improvised — do not run any
merge or approval command on the agent's behalf. Once task_status reports a
PR link, your job is to report that link back to the human — not to merge it,
approve it, or push further changes to it yourself.
© no-human-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/no-human/skills/file-a-task of no-human-ai/no_human.
Open the folder on GitHubat commit cdcbd0a
Compare with similar skills
File A Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| File A Task this skillno-human-ai/no_human | 324 | — | ~1k | Automated safety check: Pass | MIT | |
| Review PRPrefectHQ/fastmcp | 28k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| ObservalObserval/Observal | 4.3k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewimbenrabi/Financial-Modeling-Prep-MCP-Server | 150 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Fix IssuePrefectHQ/fastmcp | 28k | — | ~842 | Automated safety check: Pass | Apache-2.0 | |
| Project Pull Requestswimmwatch/cloakbrowser-mcp | 164 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Observal
Observal/Observal
A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…
Code Review
imbenrabi/Financial-Modeling-Prep-MCP-Server
Review a PR or working diff against this repo's intent layer (the AGENTS.md hierarchy), toolception pitfalls, and core invariants.
Fix Issue
PrefectHQ/fastmcp
Carry a selected FastMCP bug from reproduction through a scoped fix, compatibility review, validation, and a monitored pull request.
Project Pull Request
swimmwatch/cloakbrowser-mcp
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
Contributing To Awesome Claude
JSONbored/awesome-claude
A skill your agent uses when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP…
More from no-human-ai/no_human
Release Notes
no-human-ai/no_human
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release.
Review This Branch
no-human-ai/no_human
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the…
Related
Works with
Categories
Questions about File A Task
What does File A Task do?
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline. File A Task is an agent skill from no-human-ai/no_human. File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
When should I use File A Task?
File A Task fits situations like: tasks that involve Pull requests.
How do I install File A Task in Claude Code?
Run `npx skills add no-human-ai/no_human --skill file-a-task -a claude-code`. Or copy the skill folder (plugins/no-human/skills/file-a-task in no-human-ai/no_human) into .claude/skills/file-a-task in your project. Claude Code loads it when a task matches its description.
How do I install File A Task in Codex?
Run `npx skills add no-human-ai/no_human --skill file-a-task -a codex`. Or copy the skill folder (plugins/no-human/skills/file-a-task in no-human-ai/no_human) into .agents/skills/file-a-task in your project. Codex loads it when a task matches its description.
Can I use File A Task in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add no-human-ai/no_human --skill file-a-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/file-a-task, .gemini/skills/file-a-task, .github/skills/file-a-task and .opencode/skills/file-a-task in your project.
What does File A Task need to run?
SKILL.md names no scripts, command-line tools or credentials: File A Task is instructions for the agent only.
Does File A Task access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is File A Task safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does File A Task use?
File A Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does File A Task use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to File A Task?
Skills that share tags, products or a category with File A Task: Review PR (PrefectHQ/fastmcp, 28k stars), Observal (Observal/Observal, 4.3k stars), Code Review (imbenrabi/Financial-Modeling-Prep-MCP-Server, 150 stars) and Fix Issue (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains File A Task?
no-human-ai (a GitHub organization) maintains it in no-human-ai/no_human, which has 324 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.
Source: no-human-ai/no_human on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.